CreateAudioOutputAttached broken

Alt.OnPlayerEnterVehicle += (vehicle, seat) =>
        {

              var outA = Alt.CreateAudioOutputAttached(Alt.Hash("radio"), vehicle);
              var webview = Alt.CreateWebView("https://www.youtube.com/embed/IOoyQFsjkW4?autoplay=1&fs=0&controls=0&disablekb=1%22%20width=%22560%22%20height=%22315%22%20title=%22Monoir%20&%20Osaka%20feat.%20Brianna%20-%20The%20Violin%20Song%20(Official%20Video)");
              webview.Visible = true;
              webview.Focused = true;

              Alt.ShowCursor(true);
              webview.AddOutput(outA);
              outA.Volume = 1;
};

This code doesn't play any audio on the vehicle. Tested with OutputFrontend, and OutputWorld and those 2 work like they should.
Tried this code on the JS module, and CreateAudioOutputAttached is working like it should.
Tested on latest RC version.
alt.on('enteredVehicle', (vehicle, seat) => {
    var outA = new alt.AudioOutputAttached(vehicle, alt.hash("radio"));
    var webview = new alt.WebView("https://www.youtube.com/embed/IOoyQFsjkW4?autoplay=1&fs=0&controls=0&disablekb=1%22%20width=%22560%22%20height=%22315%22%20title=%22Monoir%20&%20Osaka%20feat.%20Brianna%20-%20The%20Violin%20Song%20(Official%20Video)");
    webview.isVisible = true;
    webview.focused = true;

    alt.showCursor(true);
    webview.addOutput(outA);
    outA.volume = 1;
})

It's fixed.


Error loading nokogiri when starting compiled binary

I am having troubles packing new rails application (generated just with rails new) which has dependency to nokogiri . I have tried configuring bundler options in compiler.rb with no success, tried any combinations of those:
      @utils.run(local_toolchain_env, @bundle, 'config', 'build.nokogiri', '--use-system-libraries', "true")
      @utils.run(local_toolchain_env, @bundle, 'config', 'set', 'deployment', "true")
      @utils.run(local_toolchain_env, @bundle, 'config', 'set', 'without', "'development test'")

Log message:
/__enclose_io_memfs__/local/vendor/ruby/2.7.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/dependencies.rb:324:in `require': cannot load such file -- nokogiri/nokogiri (LoadError)

Note: If I dont use change bundler config I get the same error for sqlite3 gem.
Env info:
rubyc - latest master
os - 20.04.1-Ubuntu
ruby - 2.7.1 (rbenv)
rails - <IP_ADDRESS>

@tonchev-ivan did you remove bootsnap from your rails app?
Bootsnap doesnt work in ruby packer and it breaks native extensions loading.

@omohokcoj I have removed bootsnap but I'm still getting an error on macOS.
Traceback (most recent call last):
	33: from /__enclose_io_memfs__/local/bin/rails:4:in `<main>'
	32: from /__enclose_io_memfs__/local/bin/rails:4:in `require'
	31: from /__enclose_io_memfs__/lib/ruby/gems/2.7.0/bundler/gems/rails-396a51ad8196/railties/lib/rails/commands.rb:18:in `<top (required)>'
	30: from /__enclose_io_memfs__/lib/ruby/gems/2.7.0/bundler/gems/rails-396a51ad8196/railties/lib/rails/command.rb:46:in `invoke'
	29: from /__enclose_io_memfs__/lib/ruby/gems/2.7.0/bundler/gems/rails-396a51ad8196/railties/lib/rails/command/base.rb:69:in `perform'
	28: from /__enclose_io_memfs__/lib/ruby/gems/2.7.0/gems/thor-1.0.1/lib/thor.rb:392:in `dispatch'
	27: from /__enclose_io_memfs__/lib/ruby/gems/2.7.0/gems/thor-1.0.1/lib/thor/invocation.rb:127:in `invoke_command'
	26: from /__enclose_io_memfs__/lib/ruby/gems/2.7.0/gems/thor-1.0.1/lib/thor/command.rb:27:in `run'
	25: from /__enclose_io_memfs__/lib/ruby/gems/2.7.0/bundler/gems/rails-396a51ad8196/railties/lib/rails/commands/server/server_command.rb:138:in `perform'
	24: from /__enclose_io_memfs__/lib/ruby/gems/2.7.0/bundler/gems/rails-396a51ad8196/railties/lib/rails/commands/server/server_command.rb:138:in `tap'
	23: from /__enclose_io_memfs__/lib/ruby/gems/2.7.0/bundler/gems/rails-396a51ad8196/railties/lib/rails/commands/server/server_command.rb:141:in `block in perform'
	22: from /__enclose_io_memfs__/lib/ruby/gems/2.7.0/bundler/gems/rails-396a51ad8196/activesupport/lib/active_support/dependencies.rb:324:in `require'
	21: from /__enclose_io_memfs__/lib/ruby/gems/2.7.0/bundler/gems/rails-396a51ad8196/activesupport/lib/active_support/dependencies.rb:291:in `load_dependency'
	20: from /__enclose_io_memfs__/lib/ruby/gems/2.7.0/bundler/gems/rails-396a51ad8196/activesupport/lib/active_support/dependencies.rb:324:in `block in require'
	19: from /__enclose_io_memfs__/lib/ruby/gems/2.7.0/bundler/gems/rails-396a51ad8196/activesupport/lib/active_support/dependencies.rb:324:in `require'
	18: from /__enclose_io_memfs__/local/config/application.rb:12:in `<top (required)>'
	17: from /__enclose_io_memfs__/lib/ruby/gems/2.7.0/bundler/gems/rails-396a51ad8196/activesupport/lib/active_support/dependencies.rb:324:in `require'
	16: from /__enclose_io_memfs__/lib/ruby/gems/2.7.0/bundler/gems/rails-396a51ad8196/activesupport/lib/active_support/dependencies.rb:291:in `load_dependency'
	15: from /__enclose_io_memfs__/lib/ruby/gems/2.7.0/bundler/gems/rails-396a51ad8196/activesupport/lib/active_support/dependencies.rb:324:in `block in require'
	14: from /__enclose_io_memfs__/lib/ruby/gems/2.7.0/bundler/gems/rails-396a51ad8196/activesupport/lib/active_support/dependencies.rb:324:in `require'
	13: from /__enclose_io_memfs__/lib/ruby/gems/2.7.0/bundler/gems/rails-396a51ad8196/actiontext/lib/action_text/engine.rb:8:in `<top (required)>'
	12: from /__enclose_io_memfs__/lib/ruby/gems/2.7.0/bundler/gems/rails-396a51ad8196/activesupport/lib/active_support/dependencies.rb:324:in `require'
	11: from /__enclose_io_memfs__/lib/ruby/gems/2.7.0/bundler/gems/rails-396a51ad8196/activesupport/lib/active_support/dependencies.rb:291:in `load_dependency'
	10: from /__enclose_io_memfs__/lib/ruby/gems/2.7.0/bundler/gems/rails-396a51ad8196/activesupport/lib/active_support/dependencies.rb:324:in `block in require'
	 9: from /__enclose_io_memfs__/lib/ruby/gems/2.7.0/bundler/gems/rails-396a51ad8196/activesupport/lib/active_support/dependencies.rb:324:in `require'
	 8: from /__enclose_io_memfs__/lib/ruby/gems/2.7.0/bundler/gems/rails-396a51ad8196/actiontext/lib/action_text.rb:6:in `<top (required)>'
	 7: from /__enclose_io_memfs__/lib/ruby/gems/2.7.0/bundler/gems/rails-396a51ad8196/activesupport/lib/active_support/dependencies.rb:324:in `require'
	 6: from /__enclose_io_memfs__/lib/ruby/gems/2.7.0/bundler/gems/rails-396a51ad8196/activesupport/lib/active_support/dependencies.rb:291:in `load_dependency'
	 5: from /__enclose_io_memfs__/lib/ruby/gems/2.7.0/bundler/gems/rails-396a51ad8196/activesupport/lib/active_support/dependencies.rb:324:in `block in require'
	 4: from /__enclose_io_memfs__/lib/ruby/gems/2.7.0/bundler/gems/rails-396a51ad8196/activesupport/lib/active_support/dependencies.rb:324:in `require'
	 3: from /__enclose_io_memfs__/lib/ruby/gems/2.7.0/gems/nokogiri-1.12.4-x86_64-darwin/lib/nokogiri.rb:11:in `<top (required)>'
	 2: from /__enclose_io_memfs__/lib/ruby/gems/2.7.0/gems/nokogiri-1.12.4-x86_64-darwin/lib/nokogiri.rb:11:in `require_relative'
	 1: from /__enclose_io_memfs__/lib/ruby/gems/2.7.0/gems/nokogiri-1.12.4-x86_64-darwin/lib/nokogiri/extension.rb:7:in `<top (required)>'
/__enclose_io_memfs__/lib/ruby/gems/2.7.0/gems/nokogiri-1.12.4-x86_64-darwin/lib/nokogiri/extension.rb:7:in `require_relative': cannot load such file -- /__enclose_io_memfs__/lib/ruby/gems/2.7.0/gems/nokogiri-1.12.4-x86_64-darwin/lib/nokogiri/2.7/nokogiri (LoadError)
	37: from /__enclose_io_memfs__/local/bin/rails:4:in `<main>'
	36: from /__enclose_io_memfs__/local/bin/rails:4:in `require'
	35: from /__enclose_io_memfs__/lib/ruby/gems/2.7.0/bundler/gems/rails-396a51ad8196/railties/lib/rails/commands.rb:18:in `<top (required)>'
	34: from /__enclose_io_memfs__/lib/ruby/gems/2.7.0/bundler/gems/rails-396a51ad8196/railties/lib/rails/command.rb:46:in `invoke'
	33: from /__enclose_io_memfs__/lib/ruby/gems/2.7.0/bundler/gems/rails-396a51ad8196/railties/lib/rails/command/base.rb:69:in `perform'
	32: from /__enclose_io_memfs__/lib/ruby/gems/2.7.0/gems/thor-1.0.1/lib/thor.rb:392:in `dispatch'
	31: from /__enclose_io_memfs__/lib/ruby/gems/2.7.0/gems/thor-1.0.1/lib/thor/invocation.rb:127:in `invoke_command'
	30: from /__enclose_io_memfs__/lib/ruby/gems/2.7.0/gems/thor-1.0.1/lib/thor/command.rb:27:in `run'
	29: from /__enclose_io_memfs__/lib/ruby/gems/2.7.0/bundler/gems/rails-396a51ad8196/railties/lib/rails/commands/server/server_command.rb:138:in `perform'
	28: from /__enclose_io_memfs__/lib/ruby/gems/2.7.0/bundler/gems/rails-396a51ad8196/railties/lib/rails/commands/server/server_command.rb:138:in `tap'
	27: from /__enclose_io_memfs__/lib/ruby/gems/2.7.0/bundler/gems/rails-396a51ad8196/railties/lib/rails/commands/server/server_command.rb:141:in `block in perform'
	26: from /__enclose_io_memfs__/lib/ruby/gems/2.7.0/bundler/gems/rails-396a51ad8196/activesupport/lib/active_support/dependencies.rb:324:in `require'
	25: from /__enclose_io_memfs__/lib/ruby/gems/2.7.0/bundler/gems/rails-396a51ad8196/activesupport/lib/active_support/dependencies.rb:291:in `load_dependency'
	24: from /__enclose_io_memfs__/lib/ruby/gems/2.7.0/bundler/gems/rails-396a51ad8196/activesupport/lib/active_support/dependencies.rb:324:in `block in require'
	23: from /__enclose_io_memfs__/lib/ruby/gems/2.7.0/bundler/gems/rails-396a51ad8196/activesupport/lib/active_support/dependencies.rb:324:in `require'
	22: from /__enclose_io_memfs__/local/config/application.rb:12:in `<top (required)>'
	21: from /__enclose_io_memfs__/lib/ruby/gems/2.7.0/bundler/gems/rails-396a51ad8196/activesupport/lib/active_support/dependencies.rb:324:in `require'
	20: from /__enclose_io_memfs__/lib/ruby/gems/2.7.0/bundler/gems/rails-396a51ad8196/activesupport/lib/active_support/dependencies.rb:291:in `load_dependency'
	19: from /__enclose_io_memfs__/lib/ruby/gems/2.7.0/bundler/gems/rails-396a51ad8196/activesupport/lib/active_support/dependencies.rb:324:in `block in require'
	18: from /__enclose_io_memfs__/lib/ruby/gems/2.7.0/bundler/gems/rails-396a51ad8196/activesupport/lib/active_support/dependencies.rb:324:in `require'
	17: from /__enclose_io_memfs__/lib/ruby/gems/2.7.0/bundler/gems/rails-396a51ad8196/actiontext/lib/action_text/engine.rb:8:in `<top (required)>'
	16: from /__enclose_io_memfs__/lib/ruby/gems/2.7.0/bundler/gems/rails-396a51ad8196/activesupport/lib/active_support/dependencies.rb:324:in `require'
	15: from /__enclose_io_memfs__/lib/ruby/gems/2.7.0/bundler/gems/rails-396a51ad8196/activesupport/lib/active_support/dependencies.rb:291:in `load_dependency'
	14: from /__enclose_io_memfs__/lib/ruby/gems/2.7.0/bundler/gems/rails-396a51ad8196/activesupport/lib/active_support/dependencies.rb:324:in `block in require'
	13: from /__enclose_io_memfs__/lib/ruby/gems/2.7.0/bundler/gems/rails-396a51ad8196/activesupport/lib/active_support/dependencies.rb:324:in `require'
	12: from /__enclose_io_memfs__/lib/ruby/gems/2.7.0/bundler/gems/rails-396a51ad8196/actiontext/lib/action_text.rb:6:in `<top (required)>'
	11: from /__enclose_io_memfs__/lib/ruby/gems/2.7.0/bundler/gems/rails-396a51ad8196/activesupport/lib/active_support/dependencies.rb:324:in `require'
	10: from /__enclose_io_memfs__/lib/ruby/gems/2.7.0/bundler/gems/rails-396a51ad8196/activesupport/lib/active_support/dependencies.rb:291:in `load_dependency'
	 9: from /__enclose_io_memfs__/lib/ruby/gems/2.7.0/bundler/gems/rails-396a51ad8196/activesupport/lib/active_support/dependencies.rb:324:in `block in require'
	 8: from /__enclose_io_memfs__/lib/ruby/gems/2.7.0/bundler/gems/rails-396a51ad8196/activesupport/lib/active_support/dependencies.rb:324:in `require'
	 7: from /__enclose_io_memfs__/lib/ruby/gems/2.7.0/gems/nokogiri-1.12.4-x86_64-darwin/lib/nokogiri.rb:11:in `<top (required)>'
	 6: from /__enclose_io_memfs__/lib/ruby/gems/2.7.0/gems/nokogiri-1.12.4-x86_64-darwin/lib/nokogiri.rb:11:in `require_relative'
	 5: from /__enclose_io_memfs__/lib/ruby/gems/2.7.0/gems/nokogiri-1.12.4-x86_64-darwin/lib/nokogiri/extension.rb:4:in `<top (required)>'
	 4: from /__enclose_io_memfs__/lib/ruby/gems/2.7.0/gems/nokogiri-1.12.4-x86_64-darwin/lib/nokogiri/extension.rb:30:in `rescue in <top (required)>'
	 3: from /__enclose_io_memfs__/lib/ruby/gems/2.7.0/bundler/gems/rails-396a51ad8196/activesupport/lib/active_support/dependencies.rb:324:in `require'
	 2: from /__enclose_io_memfs__/lib/ruby/gems/2.7.0/bundler/gems/rails-396a51ad8196/activesupport/lib/active_support/dependencies.rb:291:in `load_dependency'
	 1: from /__enclose_io_memfs__/lib/ruby/gems/2.7.0/bundler/gems/rails-396a51ad8196/activesupport/lib/active_support/dependencies.rb:324:in `block in require'
/__enclose_io_memfs__/lib/ruby/gems/2.7.0/bundler/gems/rails-396a51ad8196/activesupport/lib/active_support/dependencies.rb:324:in `require': cannot load such file -- nokogiri/nokogiri (LoadError)

@kritik it looks like you need to remove the following lines from the complile.rb file:
https://github.com/omohokcoj/ruby-packer/commit/dd10cc2bf83d5089d46e1755b76b14167f33cc2f#diff-a67b64a1d376c4e42cc056616662c72abd161952b3799ced47c68a4a0c05db0aR332
You can try my working ruby-packer fork https://github.com/motor-admin/ruby-packer - https://github.com/motor-admin/motor-admin has been packed into a single binary with it without any issues.

@ericbeland sure, feel free to reuse those monkey patches


getParentTemplate is not a function error on payment create

When creating a payment in a sandbox environment the getParentTemplate function us not defined, causing the following error:
TypeError: _this20.getParentTemplate is not a function
    at Object.onSuccess (https://www.paypalobjects.com/api/checkout.js?ver=4.7.4:9346:40)
    at _loop2 (https://www.paypalobjects.com/api/checkout.js?ver=4.7.4:1077:62)
    at SyncPromise.dispatch (https://www.paypalobjects.com/api/checkout.js?ver=4.7.4:1107:29)
    at SyncPromise.then (https://www.paypalobjects.com/api/checkout.js?ver=4.7.4:1125:18)
    at Function.syncPromiseTry [as try] (https://www.paypalobjects.com/api/checkout.js?ver=4.7.4:1170:42)
    at DelegateComponent.openContainer (https://www.paypalobjects.com/api/checkout.js?ver=4.7.4:9342:55)
    at Object.onSuccess (https://www.paypalobjects.com/api/checkout.js?ver=4.7.4:8556:35)
    at _loop2 (https://www.paypalobjects.com/api/checkout.js?ver=4.7.4:1077:62)
    at SyncPromise.dispatch (https://www.paypalobjects.com/api/checkout.js?ver=4.7.4:1107:29)
    at SyncPromise.then (https://www.paypalobjects.com/api/checkout.js?ver=4.7.4:1125:18)
    at Object._RECEIVE_MESSAGE_TYPE.(anonymous function) [as postrobot_message_response] (https://www.paypalobjects.com/api/checkout.js:2021:118)
    at receiveMessage (https://www.paypalobjects.com/api/checkout.js:1928:73)
    at messageListener (https://www.paypalobjects.com/api/checkout.js:1948:13)"

Can you let me know:

Browser version
paypal.version in your console

Could you also try without ?ver=4.7.4 on the checkout.js url, as this is going to affect our server-side caching.

Browser version: 57.0.2987.133
paypal.version: 4.0.47
Removing ?ver=4.7.4 did it. It's standard, read: sometimes annoying, WP behavior.

Cool, glad that fixed it. I'm going to try to make sure adding query params don't result in getting old versions of checkout.js, gotta figure out that change out in our caching layer.


Pandas Panel objects are deprecated. Need to update code to replace these.

Created hotfix for initial data download and processing. Still need to fix the Excel output and PHREEQC processing in WQXtoPandas. Also need to search systematically for any other panel usage.

Excel outputs are now written out and basic PHREEQC calculations work. Forced charge balancing seems not to work for some reason. Could this be a change in PHREEQC?

Alkalinity is getting lost in PHREEQC init files.


Please invite me to the community

Name
Rot
Additional Context
Hi,
I'd like to join your organization.
Thanks.

Invitation sent to join the GitHub Organization. Welcome to Infraform 🎉Please check your mail to accept the invitation sent by GitHub! 🤖About usInfraform is an open source solution for serverless platforms, it is designed for developing solutions and enhancing creators to create their infrastructure 💻 Great to have you in our community ✨ Looking forward to your valuable contributions! 🤓 You can also check our community ✨ Github ✨ LinkedIn 💜 You can also share our community with other folks who want to learn about development, DevOps, tech, and contribute together and with us 👉💜👈


Add unit tests for io.seata.common.util CompressUtil, DurationUtil, ReflectionUtil

I've analysed your codebase and noticed that io.seata.common.util CompressUtil, DurationUtil, ReflectionUtil is not fully tested.
I've written some tests for the methods in this class with the help of Diffblue Cover.
Hopefully, these tests will help you detect any regressions caused by future code changes. If you would find it useful to have additional tests written for this repository, I would be more than happy to look at other classes that you consider important.

Codecov Report

Merging #1232 into develop will increase coverage by 1.03%.
The diff coverage is n/a.

@@              Coverage Diff              @@
##             develop    #1232      +/-   ##
=============================================
+ Coverage      43.93%   44.96%   +1.03%
- Complexity      1451     1488      +37
=============================================
  Files            253      253
  Lines          10272    10272
  Branches        1335     1335
=============================================
+ Hits            4513     4619     +106
+ Misses          5176     5068     -108
- Partials         583      585       +2

Impacted Files
Coverage Δ
Complexity Δ

...server/store/file/FileTransactionStoreManager.java
47.38% <0%> (+1.39%)
19% <0%> (ø)
:arrow_down:

...main/java/io/seata/common/util/ReflectionUtil.java
90.19% <0%> (+90.19%)
14% <0%> (+14%)
:arrow_up:

...c/main/java/io/seata/common/util/CompressUtil.java
96.42% <0%> (+96.42%)
7% <0%> (+7%)
:arrow_up:

...c/main/java/io/seata/common/util/DurationUtil.java
100% <0%> (+100%)
16% <0%> (+16%)
:arrow_up:

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 eeb1dbe...cabd8e1. Read the comment docs.

Good!Thanks!


Contact Tracing Protocol seems not to get checked ever

Hello,
looking at "Einstellung"/"Datenschutz"/"Health"/"COVID-19-Kontakprotokoll" there is a counter that states that the app was doing zero (0) checks in the last 24 hours. It has been like this ever since I installed the app Tuesday morning.

The app on the other hand states that it checks every 24 hours and suggested it did actually so.

So do I have a false understanding of how it should work? Are the Corona-Warn servers not actually up and running and serving yet? Is there a bug in Apple's framework or in the App itself?
I posted this as a question, well because I can only ask for enlightenment. Thank you!
Best regards!

I forgot to mention: On my wife's phone, which is the most recent phone, the situation is the same.

As there are haven´t been any diagnosis keys submitted, there aren´t any to check :)
See https://github.com/corona-warn-app/cwa-app-ios/issues/671#issuecomment-645942587 & https://github.com/corona-warn-app/cwa-app-ios/issues/675

I just wanted to post the same issue. Had already everythin ready. But have the red the informations
from IOS regarding this feature twice. When there is risk that you have been affected then the apps asks yout to give the IDs free and then contact protcol is accessed. As long as you are not expected to be infected only the random keys are exchanged with server. May be the documentation for the end user and also the achitecture documentation can be actualized to reflect this more better as we have several issues regarding this.

Thanks for all your comments. This is a similar question to #675 and corona-warn-app/cwa-documentation#311 and as stated, the reason is just that there are no diagnosis keys to check against. We'll add that to the FAQs in the near future

Thanks for the super quick replies.
So I understand the reason but I do not understand Apple's choice to show 0 there. I mean "no news is good news". But when it DOES check there are no news, it should +1 that counter. So as the developers of the app you might choose to file a radar at apple.
Will that counter suddenly show 1 (exactly and constantly 1) when the framework receives the first "infected" IDs? (My assumption is 1 exactly because the App says it is checking once in 24h)?

@stahlfabrik: No, the detailed help of the Contact Protocol feature in IOS explains: the diagnosis keys
related to phones are exchanged with an infrastrcture. E.g. the app exchanges the diagnosis keys related to the phones with the RKI servers. The RKI servers check the diagnosis keys against the data of diagnosis keys in the infected people database, when a key is found the app is informed about this and requests from you that you share the IDs of your phone with RKI database to inform the people that they might be infected via the app. When the app has requested to share ids and you committed, then you in IOS "Datenschutz, Health..." x access to the contact tracing protocol.
As this protocol is reset every 14 days and the app is check the infection every day you can have as maxium 14 access to the contact tracing protocol - assuming that you meet every day new people which might be infected and the app is requesting everday that you share the IDs and you allow it every day.

@msdvMarcus I´m not quite sure, if this is correct 🤔
The diagnosis keys are not shared with the RKI as long as you aren´t tested positive and agreed sharing your diagnosis keys. The app regularly downloads any "positive keys" from the server and passes them to the Exposure Notification Framework (by Apple and Google) to check for any matches. If a key matches (and fulfills the other criteria, e.g. duration, distance, etc.) the app will let you know that you have a higher risk. If you are then tested positive, you can upload your keys for other users to check, if they had captured your keys.
@stahlfabrik I agree with you! According to Apples Documentation this is the "number of diagnostic key checks", so in the case of this app, one every 24 hours (if data is available soon) 👍

Thank you both!
I will read the docs from Apple. Or at least skim over them. Meanwhile I watch the other issue that shall be closed after the FAQ gets updated to explain this issue

Since diagnostic keys are being made available now by the server, this issue should soon be "solved" in that it should show most of the time that the IDs have been checked once in the last 24 hours.


[Task] Add ballerina unit test cases onto source gen tests

Description:
To properly tests source gen functionality add ballerina unit test cases on to source gen tests and run it with the build.

This has been completed and pushed in to master with the new source gen impl hence closing this issue.


Getting error with simple json select

Hi all, I'm get this error:
panic: reflect: call of github.com/jmoiron/sqlx/reflectx.(*Mapper).TraversalsByNameFunc on string Value [recovered]
        panic: reflect: call of github.com/jmoiron/sqlx/reflectx.(*Mapper).TraversalsByNameFunc on string Value

with:
query := "SELECT id FROM usr WHERE raw_usr->>'email' = ':email'"
args :=<EMAIL_ADDRESS>db.conn.NamedQuery(query, args)

this select working fine in psql console:
appdb=# SELECT id FROM usr WHERE raw_usr->>'email' =<EMAIL_ADDRESS> id
----
  1
(1 row)

oh... sorry... I must use " map[string]interface{}{"email": email} " with :email in query... pls remove this issue.

@scippio please push the "Close issue" button under the comment form


Ultracraft crash on startup

Mod Name
ULTRACRAFT 1.20.1-2.1.3
Mod Homepage
https://modrinth.com/mod/absolute-ultracraft/version/1.20.1-2.1.3
Minecraft version
1.20.1
Describe the bug
crash on startup
Steps to reproduce
crash on startup
Logs
https://pastebin.com/r2tjeGsf
Additional context
No response

Please read the issue template more carefully. For modpack related issues, use the support channel on our discord server.

Before reporting, please ensure that:

You've installed a minimal set of mods required to reproduce the issue.
Issues with modpacks and excessive amount of mods will not be accepted, as they take a long time to diagnose.
Knowing which mods are causing problems allows us to focus on fixing the issue as soon as possible.
If you're unsure which mods might be at fault, try using binary search - removing half of installed mods
repeatedly until the faulty mod is found.

Please read the issue template more carefully. For modpack related issues, use the support channel on our discord server.

Before reporting, please ensure that:

You've installed a minimal set of mods required to reproduce the issue.
Issues with modpacks and excessive amount of mods will not be accepted, as they take a long time to diagnose.
Knowing which mods are causing problems allows us to focus on fixing the issue as soon as possible.
If you're unsure which mods might be at fault, try using binary search - removing half of installed mods
repeatedly until the faulty mod is found.

Classic


Slightly refactor group/file structure

List of changes:

Removed explicit "YES" from ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES property in TestingApp (was causing CocoaPods warning)
Moved operator-typing-indicator.json from the root project folder to GliaWidgets/Resources
Moved CallButtonBar folder from GliaWidgets/Component/Bar up one folder (removed Bar because it contained a single folder - redundant)
Moved OperatorTypingIndicatorView and ~Style from GliaWidgets/View/Chat to GliaWidgets/Component/OperatorTypingIndicator (more consistent with where other components, like unread messages indicator or badge view, are located)
Renamed GliaWidgets/Component/NewMessageIndicator to ~/UnreadMessageIndicator (name was changed at some point, the folder name did not reflect that change)
Moved everything related to choice cards into a GliaWidgets/View/Chat/Content/ChoiceCard folder (files were spread a bit, now all in one place)

If you have any other suggestions on the folder structure of the project, now is probably a good time to add them to this PR :)


Removed php version constraint

Removed php version constraint as requirements will be derived from
the packages and they seem to support php 8 already.
twig-extra has the strictest version constraint allowing ^7.1.3|^8.0 where twig and the twig-bundle are allowing  "php": ">=7.2.5"

Thank you @peterrehm


(hostsman) Not the last version.

On official website, last version of Hostsman is 4.7.105 but when you download the "No Installer" version of this soft, you can see that the version number is 4.7.106.
Could you update this package with the last version ?

We can't make this work.
Its not available on typical location: http://hostsman2.it-mate.co.uk
Site doesn't work.
Upstream problem. Author needs to fix it and provide downloads via usual means or provide new place.
This is automatic package and requires stable download location.

But it's not offcial website ?
http://www.abelhadigital.com/hostsman/

Yes, its official, site works now. I'll add this for up for grabs.

Thanks a lot and thanks for your work.


Work calendar export

Originally created by Tom Smyth at 2018-01-17 15:44, migrated from redmine-#7834

Priority changed from ? to 4

By Tom Smyth at 2018-03-16 13:18

Tags set to work

By Tom Smyth at 2018-01-17 20:45

Version set to 6.1

By Tom Smyth at 2018-11-06 21:24

Status changed from New to Closed

By Tom Smyth at 2018-11-21 14:58


[BEAM-9615] finish standardizing proto import names

I noticed that there were several stranglers that were not following the import name conventions, and this PR completes that work.
pipepb, fnpb, jobpb for the Pipeline protos, Fn Execution protos, and Job Management protos respectively, and v1pb for the internal serialization representation for types the Go SDK uses.
This PR is a rote find/replace.

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

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] 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.

R: @tysonjh
cc: @youngoli

Run Go PostCommit

Run Java PreCommit

Run Java PreCommit

@lukecwik There probably is, but I'm not shaving that yak today. The gradle commands don't meaningfully work for Go, and not when I'm ripping them apart in the next two months to be replaced with something better.
In practice this is only a problem for very few packages, and only when those packages get new files.

Consider cutting a jira to not lose track of this please.

@lukecwik  I'm 100% certain that the Java PreCommit failure here is unrelated to the change. 1. The short names are for programmer convenience and don't change the boot binary at all.
That test doesn't even run the boot binary.
@tysonjh Filed it as https://issues.apache.org/jira/browse/BEAM-10206


DRAFT: Update to work with latest zig

I started this a little bit ago, submitting a pull request so it doesn't get lost. Still needs some work, can't remember what ATM. I will edit this description when I have time to work on this again.

Thanks! We still have to vendor the ZAT as a submodule until build packages can be imported from the build script

Spent a bit of time working on this update today. The code is a bit a hack-ish but I've got APK files generating again. The last issue that needs tackling at the moment is due to the add to zip step. Since it modifies the zip file in place it is not thread safe and there is no way for the caching system to detect if the step has already been run. This makes apksigner complain about an invalid header (due to multiple entries with the same name) on subsequent runs.
My plan to fix the add to zip step is to change it to a WriteFilesToZip step that takes all of the files to be added to the zip and writes each of them sequentially to a copy of the original zip file.

I change the zip_add step a bit to make it work better with the cache. Instead of adding files to the original zip file, it takes an input zip and copies it to a new location. I also made it take multiple file entries to add so the writes to the file could be batched. With this change ZigAndroidTemplate builds correctly with zig 0.11.0-dev.2461+fde05b10b, and I am comfortable with letting this PR to be merged. I installed the resulting APK on my tablet and it successfully runs, as expected.


Build a more consumable quickstart/demo that showcases the functionality of the dashboard

Readme with a walkthrough
Sample app & automation

Writing script to deploy pipeline containers. Finishing up the script for review. ETA End Of Week

[ ] Determine Apps to use for demo, focused on nginx for now
[ ] Fork their repos from redat-cop and remove promote gates and verify stages (since apps get hung on them sometimes) from pipelines
[ ] Create a script that will deploy the app, add a change,commit the change then redeploy app

[ ] Deploy apps using a script running ansible applier
[ ] Add commit messages to html file in niginx and commit
[ ] Redeploy the pipeline


[VAULT] Add Moo Beets Smoking Fantoms

https://github.com/beefyfinance/beefy-api/pull/1011
Moo Beets Smoking Fantoms
Vault: 0xFAfd5bb9a5a9c589C121B4B26dD7618Fc8AD01F3
Strategy: 0x9960A62Aec2F09abbB50438200928E9509f0cb57
chefPoolId: 82

i guess we should change FTM token to actual yearn bb-yv-FTM or something, same here https://app.beefy.finance/vault/beets-overnight-pulse

Can you rebase plz


curious if this plugin works with vue and typescript?

seems to have issues finding typescript classes in .vue files.
wondering if this is a known issue?

I'm working on a PR for this. I'm hoping to finish by tomorrow.

This actually can be accomplished by overriding default host behavior with host.resolveModuleNames (just like it is already being done in host.getSourceFile in the source here). Since the .vue file is not going to be processed through vue-loader, I'm using a parser to get the AST and strip out the typescript. This might need to be optimized later, but the PR should get it working for everyone eagerly waiting vue support!
Stay tuned, PR coming tomorrow-ish!

Thanks. When PR is ready, I will will include it as soon as possible in my vue webpack template fork https://github.com/Toilal/vue-webpack-template to test this.

Hi @Toilal
You can see the PR here: https://github.com/Realytics/fork-ts-checker-webpack-plugin/pull/72
For a quick test, I created a temp branch with the built lib folder included. So you can install like this:
npm install git://github.com/prograhammer/fork-ts-checker-webpack-plugin.git#temp --save-dev
If you are testing in Webpack, you'll need something like this in your rules:
  {
    test: /\.ts$/,
    loader: 'ts-loader',
    include: [resolve('src'), resolve('test')],
    options: {
      appendTsSuffixTo: [/\.vue$/],
      transpileOnly: true
    }
  },
  {
    test: /\.vue$/,
    loader: 'vue-loader',
    options: vueLoaderConfig
  },

I also currently use tslint-config-standard so my tslint.json looks something like:
{
    "defaultSeverity": "error",
    "extends": [
      "tslint-config-standard"
    ]
}

If you are working in VSCode, you'll need extensions Vetur and TSLint Vue (a forked extension which I also currently maintain) and the editor will match the output you get from fork-ts-checker-webpack-plugin.

For anyone else following this thread, you can use this plugin right away with npm install git://github.com/prograhammer/fork-ts-checker-webpack-plugin.git#temp --save-dev. Check back in a week and we'll have the PR merged or I'll just put it on npm so we can all just get back to writing Vue apps!

I just found a critical problem that I'm working to fix. It looks like the .vue file has to be referenced somewhere in the import dependency chain that leads back to the entry point (ie. main.ts). It is also having problems with relative path imports of .vue files. I somehow missed this before PR. Working on it...

Alright! I found how to get it to work on .vue files (without need to go the route of .vue.ts).
It's working in my vscode extension fork here: TSLint Vue. So now I can release a new working PR here. Stay tuned!

Exciting!!

The new PR is up and waiting feedback/approval: https://github.com/Realytics/fork-ts-checker-webpack-plugin/pull/77
For a quick install into your current Vue project (to see it working): npm install git://github.com/prograhammer/fork-ts-checker-webpack-plugin.git#temp --save-dev


Firefox showing "insecure connection"

Hi. I have the cert generated by anyproxy trusted in keychain. I am intercepting requests sucessfully on Chrome and Safari. However, in Firefox I get the error.  Any idea?

Your connection is not secure

The owner of reddit.com has configured their website improperly. To protect your information from being stolen, Firefox has not connected to this website.

reddit.com uses an invalid security certificate. The certificate is not trusted because the issuer certificate is unknown. The server might not be sending the appropriate intermediate certificates. An additional root certificate may need to be imported. Error code: SEC_ERROR_UNKNOWN_ISSUER

Maybe Firefox does not use the cert config in your system. I got this document from google , about how to install root certificate : https://wiki.wmtransfer.com/projects/webmoney/wiki/Installing_root_certificate_in_Mozilla_Firefox
hope that may help you.


React 18 support

Hi there!
Is there any plan / are you working on supporting React 18?
Thanks!

@masiulis amazing, thanks! Is there any way we can collaborate / help?

Thanks for the offer, but this task can get tricky. Upgrading the react-data-grid library is complicated - it has no documentation. I would also need to debug why, in latest chrome, table scroll became so janky. And webpack/storybook will also need an upgrade to support new versions.
I'll try to find some time for the version upgrade soon.

Any update?

any update?

any update?

any update?

any update?

Release with >4.0.0


Did receive UST over bridge - Please assist

Send wallet: 0x7d4EaD9cBB7cfeCD44E5912b6425950083e3C29C
tx hash: https://moonscan.io/tx/0xdf5e4e3f9f08a1fa537add4e64809f913e9e6b061e4d89dcb9af9b5491bd964a
Receive wallet:
terra1wvpr9z476j0wzk6yzupvx9ypyeeuadnq9ve5lr

Send wallet: 0x7d4EaD9cBB7cfeCD44E5912b6425950083e3C29C tx hash: https://moonscan.io/tx/0xdf5e4e3f9f08a1fa537add4e64809f913e9e6b061e4d89dcb9af9b5491bd964a
Receive wallet: terra1wvpr9z476j0wzk6yzupvx9ypyeeuadnq9ve5lr

Hello, A support ticket has been opened for you with Support ticket number BJS467BS. You should talk to a Terra money Dev on the LIVE SUPPORT PAGE So that your issue can be looked into. Thank you. CLICK HERE


Validate accounts retrieved from keychain

Theres a chance that a recovered account will have a token that is revoked, we should probably validate this token. Applies to both GitHub oauth and user-pass login.
https://github.com/HackIllinois/iOS/blob/df83a7d9c8da00d99e995cd40c1047cf98fcf398/HackIllinois/Controllers/FlowControllers/HILoginFlowController.swift#L175

Outdated issue.


Adding animations to the header

The headline looks very plain and simple. It can be enhanced with a background gradient animation as shown in screenshots below. I can work on it.

Hye @rudranshg This looks great! I have assigned the issue to you.
Thank you for contributing 😀

assign me this issue

can I work on this?


About Visual Explanations

Hi
You've done an excellent job.I have a problem if I want to visualize the heat map as the grad-cam works. Do you have any recommended methods

Hi! We do not conduct feature visualization in our paper. Maybe you can find some helo in other mamba paper~


Turn off auto translate for some editor controls

Follow-up to #75012
Editor controls now auto translate by default. So we need to opt out some controls manually, e.g. controls that display user specified texts.

Scene tab
Animation name list in Animation panel
Feature profile name list in Editor Feature Profile dialog
Layout names in editor layout menu
Subresource list in Inspector dock
Resource type shown in EditorResourcePicker
Enum dropdowns in inspectors: We'll eventually allow auto translating these after implementing a way to opt out auto translation on a property-by-property basis and a way to extract enumerators.

Cherry-picked for 4.0.4.


Fix sample code for Delegate slots

Summary
Fixes #622 (the code samples for that section of the docs raised errors)

Thanks for the contribution! ❤


Refactor RF function to read part info

Description
All parts that are directly related to ReadPartInfo() have been refactored (e.g. with Span()or the new SPI initialization function). Magic numbers related to timings have been replaced in non-related parts out of convenience.
Fixes #225

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (2759332) 87.15% compared to head (d9223e7) 87.15%.

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #251   +/-   ##
=======================================
  Coverage   87.15%   87.15%
=======================================
  Files          18       18
  Lines         514      514
=======================================
  Hits          448      448
  Misses         66       66

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


Hotfix 1: CtcSegment successive calls.

CtcSegments was not working as expected if the same instance of the contract was called several times.
This problem was forbidding the use of this contract with CtcFixPoint, for instance.

Thank !

^^
Guilherme Schvarcz Franco
Técnico em Geoprocessamento
Analista de Sistemas
Desenvolvedor
On Sat, Nov 5, 2016 at 9:31 PM, Benoit DESROCHERS<EMAIL_ADDRESS>wrote:

Thank !
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/benEnsta/ibex-geometry/pull/2#issuecomment-258638666,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABrp3JsGB4-PqObWvPgu40MXklEQLGXHks5q7Oe0gaJpZM4KoeoT
.


Addition of Roadmap for Web Development

Can you please add labels to this issue.

@jfmartinz Please add labels to this issue .


"invalid http POST response" and later crash

What is the bug?
we found that out testnet server was down.
Additional context
LWD logs
{"app":"lightwalletd","level":"info","msg":"Waiting for block: 2057199","time":"2022-09-29T07:30:54Z"}
lightwalletd_1     | 2022-09-29T07:31:25.170377206Z {"app":"lightwalletd","error":"invalid http POST response (nil), method: getbestblockhash, id: 494636, last error=Post \"http://zcashd:38232\": dial tcp: lookup zcashd on <IP_ADDRESS>:53: no such host","level":"fatal","msg":"error zcashd getbestblockhash rpc","time":"2022-09-29T07:31:25Z"}
lightwalletd_1     | 2022-09-29T07:31:25.170436128Z Lightwalletd died with a Fatal error. Check logfile for details.

appending logfiles for lightwalletd
Zcashd Logs
cashd_1           | 2022-09-29T07:30:35.348777431Z 2022-09-29T07:30:35.348590Z  INFO main: keypool reserve 1
zcashd_1           | 2022-09-29T07:30:35.348897797Z 2022-09-29T07:30:35.348691Z  INFO main: keypool return 1
zcashd_1           | 2022-09-29T07:30:52.699171626Z 2022-09-29T07:30:52.698897Z  INFO ProcessNewBlock: main: UpdateTip: new best hash=0027e9c247ea67c458c9fd51750fbab56ecf72231338189a29f19b0cba0cc1a3 height=2057198 bits=523969164 log2_work=37.287206 tx=2595076 date=2022-09-29 07:30:35 progress=1.000000 cache=0.0MiB(1tx)

Solution
I wish I knew it! 😅

It looks like lightwalletd is configured to talk connect to zcashd via the hostname zcashd, but that hostname didn't exist when it tried to do so. It's most likely a configuration error in the deployment side of things or something went haywire in the Docker/GKE networking.

We could certainly improve the error message! I can make a PR.

This area is messy right now. What I think happened is that zcashd died while lightwalletd had a getbestblockhash rpc outstanding. (It calls that rpc every 2 seconds in normal operation in order to detect a new block.) I was able to reproduce it once:
{"app":"lightwalletd","level":"info","msg":"getblock 1813132 failed, will retry: error requesting block: invalid http POST response (nil), method: getblock, id: 2381, last error=Post \"http://<IP_ADDRESS>:8232\": dial tcp <IP_ADDRESS>:8232: connect: connection refused","time":"2022-10-20T11:00:07-06:00"}
{"app":"lightwalletd","error":"invalid http POST response (nil), method: getbestblockhash, id: 2382, last error=Post \"http://<IP_ADDRESS>:8232\": dial tcp <IP_ADDRESS>:8232: connect: connection refused","level":"fatal","msg":"error zcashd getbestblockhash rpc","time":"2022-10-20T11:00:37-06:00"}
Lightwalletd died with a Fatal error. Check logfile for details.

One solution is to always restart lightwalletd if zcashd has died.
The lightwalletd server (lwd) does a series of retries when an rpc to zcashd fails, but it's not consistent and you'll get timing-dependant variations in behavior. For example, if you start zcashd when it has many blocks to sync, and start lwd right after starting zcashd, lwd will try to execute rpcs a limited number of times and then will give up. But if zcashd happens to already be synced to the tip (or close to it), then it will -- usually! -- become responsive to rpcs before lwd's retries hit the limit.
I think a better design is to make lightwalletd retry rpcs forever. The only possible problem I can imagine is if some monitor process is watching that lwd is running (starting it if it isn't) -- but it's not also monitoring the local zcashd. But it or some other process should be monitoring zcashd and restarting it if necessary. I'd think that would be required since zcashd can die for a wide variety of reasons. So I think making this "infinite retry" change to lightwalletd would be a good idea. It would also simplify its code, and make its behavior more understandable and consistent. It would have prevented this issue from occurring.
This would also make lightwalletd more available to its clients (although of course some gRPCs could hang until they timeout, if zcashd is taking a long time to restart).
While infinitely retrying rpcs, lwd should log the failures, but it should be careful not to log too much (which would increase the danger of running the filesystem out of space). Probably it should log only the first failure, then log again when successful.
The other way to get consistent behavior is if lwd always dies when zcashd dies, but it's not possible to ensure that -- it's possible that lwd attempts no rpcs across a (fast) zcashd restart. So really the only way to get fully-consistent lwd behavior is for it to retry rpcs infinitely.
Maybe @defuse has some thoughts on this?


The file sizes are twice as big when using LA-ICQ vs ICQ for AVC/H.264

The file sizes are still twice as big when using LA-ICQ vs ICQ for AVC/H.264 QuickSync.  Just tested this using "QSVEnc" and "Handbrake" programs. File sizes should be similar.
Do you know why issue #989 is closed??

Hi @ukmark62 , please specify versions of media stack components(msdk/media-driver/gmm/libva), HW type, command lines (ideally via sample or ffmpeg) so that we can reproduce it quickly.

If you refer back to the original issue #989, steps were detailed how to reproduce the problem. If somebody could verify by simply re-running that example, it would determine if the problem is still present in the 'master' branch.

I think it's better to ask a reporter why he closed the issue.

Using the QSVEnc CLI from rigaya on Windows 10 (https://github.com/rigaya/QSVEnc/), this is a template command how to reproduce the issue. ICQ with LA has double file size of ICQ for the same quality.
ICQ
**D:\StaxRip\Apps\Encoders\QSVEnc\QSVEncC64.exe --quality best --icq 24 -i "input.mkv" -o "output.h264"
ICQ with lookahead
D:\StaxRip\Apps\Encoders\QSVEnc\QSVEncC64.exe --quality best --la-depth 30 --la-icq 24 -i "input.mkv" -o "output.h264"**

For ffmpeg use:-
ICQ
ffmpeg -i input.mp4 -c:v h264_qsv -global_quality 24 output.mp4
ICQ & Lookahead
ffmpeg -i input.mp4 -c:v h264_qsv -global_quality 24 -look_ahead 1 -look_ahead_depth 30 output.mp4

@DenWolf , any news?

@pgribov  - could you please take a look at this issue ?

Hi, @ukmark62 . I have looked to this issue. At the moment, LA_ICQ gives higher quality with an increase in bitrate, so a file oversize compared to ICQ is expected.
How important is it for LA_ICQ to give a smaller file size? And in what use cases will you use it?

Thanks for looking.  I don't use AVC much - nearly always use HEVC. However, a doubling of file size seems extreme. I appreciate quality (and therfore bitrate) should be higher with lookahead enabled and it is difficult to estimate how much larger the files would be, but I would have thought that in the majority of cases the file sizes would be between 5-20% higher.
If the current code is working as expected, then the documentation should clearly state that lookahead will increase file sizes very significantly.

Normal LA is based on VBR (it controls bitrate), in this case it reduces bitrate with maintaining quality. ICQ is based on CQP (it does not control bitrate), LA_ICQ algorithm is completely different from the normal LA. So, the file size increasing in this mode is acceptable.

If the current code is working as expected, then the documentation should clearly state that lookahead will increase file sizes very significantly.

@dmitryermilov , do you think we need to add this information?


fix(study): clear search text from participant when text box is cleared

Create study
Go to participants tab
Search for a participant in the box, wait for the autocomplete to suggest something
Press ESC, the cursor moves back to the beginning to imply that the text box is "cleared", but it still contains the text you wrote previously. The text should be removed as well. It almost seems as if the previous written text becomes the "caption" of the text box

That is somewhat intentionally, but it does look weird. It was so user can write free text there to add account that is not in the dropdown list


🧠 Logic: 🏦 Bank spendable-coins predicate

Purpose
In the logic module, provide a predicate allowing to retrieve the set of coins that are spendable (i.e. not locked), through the bank module.
(related to #263)
Expected behavior
The predicate is expected to unify the given terms with the list of coins of the given account which are spendable (see bank#viewkeeper). The signature is a follow:
bank_spendable_coins(?Account, ?Balances)

Where:

Account represents the account address (in Bech32 format).
Balances represents the balances of the account as a list of pairs of coin denomination and amount which are spendable (i.e. not locked).

Exemple
okp4d query logic ask "bank_spendable_coins(X, Y)."

Acceptance Criteria

The predicate is implemented according to the described behavior and examples
The predicate passes all test cases
Any related documentation is updated

:tada: This issue has been resolved in version 3.1.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version 4.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Convert mappers to use templates instead of instance variables

After #42 is accomplished, update the static mapper classes (like Linear and Clamper) to use templated values for better compiler optimization.
This cannot be done for some mappers, like Lookup Table, but this is okay

Decided to use const instance variables instead of not-type template parameters


Revert cache busting

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.06%) to 69.549%

Totals

Change from base Build<PHONE_NUMBER>:
0.06%

Covered Lines:
12868

Relevant Lines:
18502

💛  - Coveralls


Background stop when app is killed

Hello:
I'm testing the connector and when the app is open in the foreground and in the background it works fine, but if I remove the app from my running app manager, the background stops working and I don't keep getting coordinates.
What's going on? Isn't the service supposed to stay active?
I am using Capacitor v3 and my Android version is 9 on my smartphone.

I've tried to address this in #19.


fix(curriculum): adjusted code comment in css-grid challenge to enable current validation checks

Checklist:

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] All the files I changed are in the same world language, for example: only English changes, or only Chinese changes, etc.

Closes #38310

The code comment is not handled in the regex. I thought it would be better to simply position the comment as suggested in the issue to get it to work.

Blocked by #38308

This PR https://github.com/freeCodeCamp/freeCodeCamp/pull/38256 moved the comment.
Here is the diff https://github.com/freeCodeCamp/freeCodeCamp/commit/41718abf76a6b6c53b893291cbb2d1466e364a67#diff-bccda97cc24e5954eef61a0918673dd1
Not sure if we just move it back or fix the regex.
@RandellDawson What do you think?

Why is this merged block ? Currently there is an open issue #38310 which is blocking me to complete my to get Responsive Web Design Certification

@tsabunkar We are still reviewing.  There is currently a code freeze for this section, so it may be a bit before the challenge is fixed.
FYI - You do not have to complete any of the challenges to get the certification.   There is currently a code freeze for this section, so it may be a bit before the challenge is fixed.
FYI - You do not have to complete any of the challenges to get the certification.

Thanks for response, I wan't aware about it, Sure I will be completeing my projects !!

@hassaanp This fix is just a band-aid.  The true fix is ignoring the comments during the tests.  I have a PR that does this using a helper function that will be introduced in another PR very soon.  Once I have the helper function available globally, you can create another PR which uses it in the testString.  I am going to close this PR for now, but the issue will remain open.


Vault auto-refresh:

After sending the Vault should auto-refresh.

Vault auto-refresh is not happening.
Tested on keeper app v 1.1.5(243)

De-prioritizing this since there are performance issues with auto refresh on navigation at this point.


Adding Armada Job Submission Code

Closes #39
Closes #50
Closes #41
Closes #45
Closes #19
Closes #10

Should we close this?

Moving to draft as I am going to add the issues into this one that will be needed for the MVP, as they will require significant testing.
#50
#41
#51

Going to split this PR into a docs PR and a code PR


fix: remove item may changed clone btree; (i+1) children has new cow,…

… but do not copy

bug flow
new btree t1
clone btree t2
remove item and need merge i + 1 children.
now, i + 1 children has new cow, but no copy;
t1 modiyf i + 1 children item, t2 follow modify (bug happen).
fix:
when merge i + 1 children, copy it


Custom Format for datepicker combined with ngRequired causing issues with binding

Libraries:
Angular JS: v1.4.7
Angular JS animate: v1.4.7
Angualr ui: 0.14.2
Here's the plnkr
So far, I have seen this issue only when format is provided with uib-datepicker-popup and it also includes a ngRequired expression. As you can see in the plnkr, the date field disappears from the model.
So, the snippet will work properly if you remove
ng-required="data.config.dob.isRequired"
or, change
uib-datepicker-popup="MM/dd/yyyy" to uib-datepicker-popup
One more observation was that this affects all other datepickers on the page whether or not they have the format and ngRequired combination.
This might be related to: #4607

Currently evaluating options here, but as noted, the demo is working fine.  The issue appears to be setting  a hard-coded string in uib-datepicker-popup vs. setting via a scope variable.  For now, you can use that as a work around.

@codenewa, this was fixed in #4635.  To get all the fixed goodness, you can do a snapshot build of master by running the npm install and grunt commands.

Duplicate  of #4616 and #4607.


Bug in add default classes for each HTML element wiki page

https://github.com/showdownjs/showdown/wiki/Add-default-classes-for-each-HTML-element
regex: new RegExp(`<${key}(.*)>`, 'g'),
replace: `<${key} class="${classMap[key]}" $2>

According to : https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/RegExp#

The capturing groups are numbered according to the order of left parentheses of capturing groups, starting from 1.

The regex only has 1 capturing group. Therefore, in replace, the $2 ought to be $1.

Thank you. Fixed


Logging 3/5: filtering by log level

Best case: 1 days, Most likely: 1 days, Worst Case: 1 days
Filtering by log level

[x] ifdef (filter at pony compile)
[x] if (filter at pony func)

hard to set level? No globals

[x] environment var (filter at c func)

** w_process_category_overrides, process any env var overrides
**
** If the environment variable WALLAROO_THRESHOLDS exists, then
** parse that string and apply a set of overrides to the
** _cat2sev_thresholds.
**
** The string should contain a list of zero or more
** category.severity pairs, e.g, "22.5" for category 23 and
** severity 5 (which corresponds to Log.notice()).  The string
** "*" can be used to specify all categories.
**
** Items in the list are separated by commas and are processed
** in order.  The "*" for all categories, if used, probably ought
** to be first in the list.  For example, "*.1,22.5,3.7,4.0".
*/```

A simple logging example is:

        @logf(Log.info(), Log.checkpoint(), "Message goes here".cstring())


PCB

do You have a PCB Board files ?

I'm making a PCB for this.

I'm making a PCB for this.

Do you have the PCB progress documented anywhere? I'd love to see a simple and inexpensive system based on the rp2040 or pi pico.

I ran into problems with mine, I think because I made a mistake when copying the circuit over to my PCB. Which is too bad, because I have 10 of those PCBs lying around.
Here is what I had: https://oshwlab.com/andrew_3060/picotnc-tnc-board
I think the pico_tnc project has an updated schematic in the readme now. If someone wants to collaborate on this using EasyEDA, please let me know and I will add you as a contributor on the project.


Replace request with isomorphic-unfetch

request has been deprecated since Feb 2020. And I want to use openapi-to-graphql on client-side. However, I can't because request uses fs. So I make and open this pr.

@JsonKim This is a very important change! Thank you very much!
I'm not familiar with request alternatives. Could you give us some insight into why this particular library was selected?

@JsonKim @Alan-Cha I guess one starting point is to look at the list of alternative libraries that the request team itself compiled: https://github.com/request/request/issues/3143

@ErikWittern Thanks! @Alan-Cha unfetch is lighter and simpler than other alternatives. And it can be used in both server-side and client-side because it supports polyfill. If you suggest another alternative, I can work on that as well.


scheduler forward packets

Problem

swqos was built with the assumption that transactions are forwarded by validator nodes
without swqos being used, forwarding was in process of being deprecated since behavior (without swqow stuff) was useless
major push in past weeks has led to operators adopting swqos forwarding side-deals
the new scheduler does not support forwarding for above reasons
the lack of support would make operators need to make a choice between swqos side deals and the new scheduler, which is less than ideal under the current circumstances

Summary of Changes

Add support for forwarding transactions in the new scheduler

Fixes #

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

Project coverage is 81.9%. Comparing base (f121f73) to head (65ad46b).
Report is 18 commits behind head on master.

Additional details and impacted files
@@           Coverage Diff            @@
##           master     #898    +/-   ##
========================================
  Coverage    81.9%    81.9%
========================================
  Files         853      853
  Lines      231779   231951   +172
========================================
+ Hits       189829   190027   +198
+ Misses      41950    41924    -26

Local cluster summary looks fine:
mean_tps: 17282
max_tps: 52559
mean_confirmation_ms: 2978
max_confirmation_ms: 13360
99th_percentile_confirmation_ms: 11896
max_tower_distance: 32
last_tower_distance: 31
slots_per_second: 2.705


Swapchains should have a create method and create themselves

https://github.com/Devsh-Graphics-Programming/Nabla/pull/160#discussion_r690749735

done a long time ago


[10.x] Prepend table name to dynamic whereSomething clauses when using joins

Prevents "ambiguous column" errors when using joins and dynamic clauses in the same query. Existing functionality is not affected, but the change allows to use or keep existing dynamic where clauses when using joins.

Don't want to cause any breaking changes. I don't think we document dynamic where clauses anymore.


Custom html/template rendering on nuxt server error

What problem does this feature solve?
If an unhandled Error occurs during ssr, an end user will see "Nuxt.js Internal Server Error" message. It would be great to have an ability to render layouts/error.vue template or at least custom html. It is not possible to catch all the application errors with context.error() func, moreover an error may occur right after that call or somewhere else.
Why is it important? "Nuxt.js Internal Server Error" message means nothing to the end user, it is confusing, we could provide more detailed explanation. It is also inconvenient to wrap everything with try/catch block even though you know you cannot handle it, but show the error template.
What does the proposed changes look like?
Why don't we use try/catch and error() call only when we want to handle it differently than showing the error template, and make a single point of catching errors from all the app at the top level to show that template.

This feature request is available on Nuxt community (#c10702)

Hey @Atinux, any thoughts?

Here is what I've figured out so far:

You need to create app/views/error.html file inside your base dir in order to override the default error template.
The "Nuxt.js Internal Server Error" message appears because app/views/error.html file is not copied into dist folder during build (I wonder why). So you HAVE TO manually copy .nuxt/views/error.html during build in addition to dist folder.
app/views/error.html isn't static html, it is template file, error object is passed into it.

Is there still a problem? Yes, the points is nuxt forces us to use error() func everywhere we can, even though we cannot catch everything, runtime errors are possible. In case of uncaught error spa and ssr act differently: spa shows layouts/error.vue, ssr shows app/views/error.html. It is inconsistent, we want to show the same layouts/error.vue when possible without having to wrap everything with try catch.
I don't have deep knowledge about nuxt.js, but I suppose there is a way or code point where we can still render ayouts/error.vue. Otherwise render app/views/error.html. This is how I would handle some "user endpoint" in asyncData, expecting error() func to be called somewhere in internals:
try {
    const user = await this.$userRepository.findById(params.userId);
    ...
} catch(e) {
    if (e.response && e.response.status === 404) {
        error({statusCode: 404, message: 'User not found'});
        return;
    }

    throw e;
}

Or event described this behaviour in one single place of catching exceptions.

This is now possible in Nuxt 3 via ~/error.vue. A second (internal) request is made to render an error page in the event of an error rendering the initially requested route.


Add link to GraphQL cookbook from GraphQL overview page

This adds a link to the cookbook from the overview page.
Something weird is happening when I try build and test this - even though it just worked last week. I'll try get back to that to figure it out soon

@jradtilbrook yes, there were some issues with the test deployment. It builds fine now. I checked the PR. Merging now.


Showing operator card in the device but showing No operator error

Sometimes it shows "No operator" error though in the device there are operator. It may occurs because of always last message showing issue. After punching, error is dismissed

Fixed issue


Update to .NET 4.5.

Since many people will not be able to have .NET 3.5 on Windows 8 now, here is a patch to make the samples work with .NET 4.5 (it consists in using: <Reference Include="System.Xaml" />).

Fixed in the latest release


Documentation on importing classes to CL

Hi @shawntanzk, as discussed offline, kindly review, edit where necessary, and add the following to central docs...
How to add (import) a class to the Cell Ontology (CL) from another ontology
1. Follow steps 1 - 5 under the heading Protege-based declaration.
NB: Even though the instructions state that this workflow is to be avoided, the other solutions in the current documentation are out of date.
Example
Request:
Update the equivalence axiom for a term in CL to:
'epithelial cell' and ('part of' some 'glomerular visceral epithelium’)
Problem:
glomerular visceral epithelium (UBERON:0006852) does not yet exist in CL. It needs to be imported from the UBERON ontology to the CL ontology.
Solution:
The editor would create a new class in CL for UBERON:0006852 by following steps 1 - 5 from the link above and proceed with one of the options below.
2. The editor then has several options (a or b or c):
(a) Construct logical axioms using the newly declared ID, create a
pull request, merge the changes and check back after the imports have
been refreshed (@shawntanzk: do refreshes happen on a regular basis or just ad hoc?).
If viewing the ontology in Protégé, in addition to seeing the newly
imported class with all associated metadata, the label should replace
the ID in axioms if the view is set to “Render by label (rdfs:label)”.
Example
Write the equivalence axiom as:
'epithelial cell' and ('part of' some UBERON:0006852)
Proceed with a pull request and merge.
Once the imports have been refreshed, the equivalence axiom should appear as:
'epithelial cell' and ('part of' some 'glomerular visceral epithelium’)

(b) Ask a developer (@shawntanzk: how to identify devs? Is there a directory?) to refresh the imports. Once refreshed, return to Protégé, add the logical axioms and create a pull request per standard procedure.
Example
After the developer confirms the refresh has been completed, return to Protégé and write the equivalence axiom as:
‘epithelial cell' and ('part of' some 'glomerular visceral epithelium’)

(c) Refresh the imports, return to Protégé, add the logical axioms and create a pull request per standard procedure. Note that refreshing the imports requires Docker and sufficient computational power (> 8GB RAM). To refresh the imports, open Docker so it is running in the background. Then open Terminal, navigate to src/ontology directory in the cell-ontology repository and run:
sh run.sh make imports/merged_import.owl
Contact a developer if there is an issue with the refresh. Once refreshed, return to Protégé, add the logical axioms and create a pull request per standard procedure. Note that the import refresh process seems to be quite laborious/computationally expensive as-is, and a centralised database approach may be an improved longterm solution.

yes! found it! it's here https://github.com/INCATools/ontology-development-kit/edit/master/template/_dynamic_files.jinja2 - let me go through the above, edit it, and see if you can give a go on editing that file -> that should distribute it to all ontologies

actually I'm looking at it now, and it might take a bit of reworking to get it in the main docs. For now, if you want, you can add it to CL internal docs: https://github.com/obophenotype/cell-ontology/tree/master/docs

Comments on docs:

Example
Request:
Update the equivalence axiom for a term in CL to:
'epithelial cell' and ('part of' some 'glomerular visceral epithelium’)
Problem:
glomerular visceral epithelium (UBERON:0006852) does not yet exist in CL. It needs to be imported from the UBERON ontology to the CL ontology.
Solution:
The editor would create a new class in CL for UBERON:0006852 by following steps 1 - 5 from the link above and proceed with one of the options below.

The above section is not really needed imo

Construct logical axioms using the newly declared ID, create a
pull request, merge the changes and check back after the imports have
been refreshed

This is dangerous as unsatisfiable axioms might happen and break if merge is done before imports - I would remove this as an option in docs
I think it should be just try to run imports, if you run into error (write something about requiring quite a bit of memory on your local machine), create a ticket that requests for a certain term to be imported and someone will pick it up and do it for you. That would probably be the best :)


Add -e and retry to install python script

Testing: test_install_on_wrong_os_offline_installer
@cawallin

looks good

Ship it.


refacoring elastic search query template by building json objects

Remove error prone string concat for query template
Use ObjectNode/ArrayNode to build query template instead
remove unnecessary empty spaces in the old query
new query is compared using text comparision
Regression test on dataset, flows, metrics, filters, auto complete are all tested in local:9001

Coverage remained the same at 26.266% when pulling daecd672d8d90d3a073cc53a3e12c5f4c646ad6c on camelliazhang:master into 01f30b92e766b9522f340861efd385e81f5bb374 on linkedin:master.

Changes made to read json files instead of creading json nodes which is not easy to read. Mars, could you please review it when you get a chance? If it works, I will make changes in wherehows frontend mp configurations accordingly. Thanks~

Coverage remained the same at 28.545% when pulling 04d6dc597325defd194f6a1191c39157725b298d on camelliazhang:master into f2c90c57bd1f95583afc5795b03e5cdf4e35e202 on linkedin:master.


More complex expression in test confuses the counter

Describe the bug
My metrics section defines two table level sql metrics. My last test then combines these metrics with row_count. The actor table in the data set (the sample postgres dvdrental) has 200 rows. 113 of the actors have last name longer than first name and 60 vice versa. Exactly 27 actors have a first name with the same length as their last name. Anyway, the last test works. It will pass if I change the condition to 27 and fails if I make it 26. Just the reporting, as you see in the screenshot says that the value of the metrics is 200, which it is not. It should say 27.
table_name: actor
metrics:
  - row_count
sql_metrics:
  - sql:
      select count(*) as long_name_count from actor where char_length(first_name)>char_length(last_name)
  - sql:
      select count(*) as long_surname_count from actor where char_length(first_name)<char_length(last_name)
tests:
  table_not_empty: row_count > 0
  "some people have first name longer than surname": long_name_count > 5
  "some people have first name shorter than surname": long_surname_count > 5
  "exactly 27 people have equal first and last name char count": row_count - long_name_count - long_surname_count == 26
columns:
  first_name:
    metrics:
      - invalid_percentage
      - min_length
      - avg_length
      - max_length
    valid_regex: ^[A-Z][a-z]+$
    tests:
      - invalid_percentage == 0
      - min_length > 1

Here goes the screenshot with the defect:

Context
Include your scan.yml or warehouse.yml when relevant
OS: Linux Miny
Python Version: 3.8
Soda SQL Version: 2.0.0b26
Warehouse Type: postgres

Thanks for the report, soda-sql now evaluates the left-side of the test expression and sends the result to the cloud, i.e. in your case it will send and show 27 as expected.


Handle Fragmented messages

I know its not pretty but not bad for first attempt.
It looks for the frag maker if F (fragment) is found its stored until C is found (Cont) and joins them together. if K is found it just continues as usual

Sorry dude, keep meaning to look at this then get pulled away to other things :) I'll push a few changes soon, but this is pretty awesome for first touch of node 😁

Oh, just had a thought - need to include a case for people on the pre 0.8.7 version of multimon, where the KFC key doesn't exist, otherwise this would just ignore messages for them :)

I think making the latest version of multimon a prerequisite would be best.  Otherwise fragmented messages can't be handled at all. Other option is make a branch for older versions of multimon.

@davidmckenzie are you able to make the changes as this goes a bit beyond my scope :)
For the first time since running this on my PC ive had only one fragmented message not marry up correctly or close to what it should be +/- a few letters. i think this will be the best we can do

Yeah all G dude, I'll put something in for this on the weekend probably, just a little time poor at the moment :)


Mathematical inequivalence introduced by GLT Sampler vs. DGL Sampler?

🐛 Describe the bug
We observe that there are some differences in samplers that leads to computational / mathematical inequivalences between GLT's implementation of IGBH training vs. IGB's "official" implementation, when running the training code. More specifically, we observe that, compared to IGB's DGL sampler, GLT/PyG sampler leads to unnecessary message passing & aggregation and therefore results in different computation results.
In a high level, there are two differences that leads to the computational inequivalence here:

Given a path a->b->c, at each layer, GLT is updating all nodes at this layer and higher layer. For instance, at layer 0, we need to update node embeddings for both b and c. However, in DGL, only node b's embedding will be updated. Therefore, if we consider the final embedding generated for node c, GLT computes it as h_2(c) = h_1(c) + h_1(b) = (h_0(c) + h_0(b)) + (h_0(b) + h_0(a)), while DGL computes it as h_2(c) = h_1(c) + h_1(b) = h_0(c) + (h_0(b) + h_0(a)).
When creating blocks for layer $i-1$, DGL not only uses the destination nodes from layer $i$ as seed nodes, but also includes all subsequent $i+1\cdots n$ destination nodes as seed nodes.

Take the following graph as an example:
3 -> 9, 9 -> 12, 8 -> 12

If the path 3 -> 9 -> 12 is being sampled, then the message passing path in GLT is:

at first layer, we compute 3 -> 9 and 9 -> 12
at second layer, we compute 9 (value updated with node 3's feature) -> 12

Thus, from the above computation, we see that feature 9 is included twice.
However, in DGL, the sampling process is a bit different:

We start with a seed node set containing only our target node 12: [12, ]
At first hop (corresponding to the model's second layer), we add 9, since 9 is randomly chosen as 12's source node, added to the seed node set: [12, 9]
At second hop (corresponding to the model's first layer), we add:
node 8, since node 12 is in the seed node set
node 3, since node 9 is in the seed node set
And therefore we results in [12, 9, 8, 3] nodes, with graph 3 -> 9 -> 12 <- 8.

Therefore, in the first layer, we compute 3 -> 9 and 8 -> 12; and in the second layer, we additionally compute 9 -> 12. This computation is the algorithm that is implemented in the paper (IGB's official repository), and is mathematically different from GLT's current implementation.
Environment

GLT version: latest, built from main branch.
PyG version: 2.3.1
PyTorch version: 1.14.0
OS: Linux
Python version: 3.8.10
CUDA/cuDNN version: 11.8
Any other relevant information

To reproduce the issue, we run the following code snippet in GLT:
import graphlearn_torch as glt
import torch
import torch_geometric as pyg

# We consider a simplified version of GATConv here.
# GATConv computes the destination nodes' embedding from both its embedding and its source nodes' embedding
# we simplify it here so that only an addition operation is performed
# between destination nodes' embedding and the source nodes' embedding.
class DummyLayer(pyg.nn.MessagePassing):
    def __init__(self):
        super().__init__(aggr="add")

    def forward(self, x, edge_index):
        return self.propagate(edge_index, x=x)

    def message(self, x_i, x_j):
        return x_i + x_j

# to simplify the discussion, we create a tree for generating the samples.
u = torch.tensor([0, 1, 2, 3,  4,  5,  6,  7,  8,  9, 10, 11])
v = torch.tensor([8, 8, 9, 9, 10, 10, 11, 11, 12, 12, 13, 13])
edge_index = torch.stack([u, v], dim=0)

# and to trace which node is involved in the computation,
# the features are assigned as 2^i for node i
x = torch.stack([2**torch.tensor(range(14)) for _ in range(4)], dim=1).to(torch.float32)

# GLT IGBH's dataloading code
dataset = glt.data.Dataset(edge_dir="in")
dataset.init_graph(edge_index, graph_mode="CPU")
dataset.init_node_features(node_feature_data=x, with_gpu=False)
loader = glt.loader.NeighborLoader(
    dataset,
    [1, 1],
    torch.tensor([12, 13]),
    batch_size=2
)
data = next(iter(loader))

x = data.x
edge_index = data.edge_index
# At start, the edge index could be:
# 2 -> 9 -> 12
# 5 -> 10 -> 13
# and the corresponding features could be:
# tensor([[4096, 4096, 4096, 4096], # node 12's feature
#         [8192, 8192, 8192, 8192], # node 13's feature
#         [ 512,  512,  512,  512], # node 9's feature
#         [1024, 1024, 1024, 1024], # node 10's feature
#         [   4,    4,    4,    4], # node 2's feature
#         [  32,   32,   32,   32]], dtype=torch.int32) # node 5's feature

h1 = DummyLayer()(x, edge_index)
# after we apply the first transformation, the features now are updated as:
# tensor([[4608, 4608, 4608, 4608], # node 12, h_1(12) = h_0(12) + h_0(9)
#         [9216, 9216, 9216, 9216], # node 13, h_1(13) = h_0(13) + h_0(10)
#         [ 516,  516,  516,  516], # node 9, h_1(9) = h_0(9) + h_0(2)
#         [1056, 1056, 1056, 1056], # node 10, h_1(10) = h_0(10) + h_0(5)
#         [   0,    0,    0,    0], # node 2, no update since there are no incoming edges
#         [   0,    0,    0,    0]], dtype=torch.int32) # node 5, no update since there are no incoming edges

h2 = DummyLayer()(h1, edge_index)
# after we apply the second transformation, the features now are updated as:
# tensor([[ 5124,  5124,  5124,  5124], # node 12, h_2(12) = h_1(12) + h_1(9)
#         [10272, 10272, 10272, 10272], # node 13, h_2(13) = h_1(13) + h_1(10)
#         [  516,   516,   516,   516],
#         [ 1056,  1056,  1056,  1056],
#         [    0,     0,     0,     0],
#         [    0,     0,     0,     0]], dtype=torch.int32)

# for node 12, the message passing path is:
# 9 -> 12
# 2 -> 9 (value updated with node 2's feature) -> 12
# thus, 9 is updated twice.

# this is different from DGL's implementation
# in DGL, if we have a path 2 -> 9 -> 12,
# then the value will be: (2**12 + 2**9 + 2**2)
# verified:
# (2**12 + 2**9 + (2**9 + 2**2)) == 5124

And we run the following code for DGL:
import dgl
import torch

class DummyLayer(torch.nn.Module):
    def __init__(self):
        # Takes in source and destination nodes, adds them according to the edges, and returns it
        super(DummyLayer, self).__init__()

    def forward(self, graph, hidden):
        graph = graph.local_var()
        graph.srcdata['temp_src'] = hidden
        graph.dstdata['temp_dst'] = hidden[:graph.number_of_dst_nodes()]
        graph.update_all(
            dgl.function.u_add_v('temp_src', 'temp_dst', 'temp'),
            dgl.function.sum("temp", "result")
        )
        new_hidden = graph.dstdata['result']
        return new_hidden

u = torch.tensor([0, 1, 2, 3,  4,  5,  6,  7,  8,  9, 10, 11])
v = torch.tensor([8, 8, 9, 9, 10, 10, 11, 11, 12, 12, 13, 13])
g = dgl.graph((u, v))

g.ndata['feat'] = torch.stack(
    [2**g.nodes(), 2**g.nodes(), 2**g.nodes(), 2**g.nodes()],
    dim=1).to(torch.float32)

sampler = dgl.dataloading.NeighborSampler([1, 1])
loader = dgl.dataloading.DataLoader(g, torch.tensor([12, 13]), sampler, batch_size=2)
input_nodes, destination_nodes, blocks = next(iter(loader))

x = blocks[0].srcdata['feat']
# here, if we examine the edges in block 0, we might see:
# 8->12
# 10->13
# 2->9
# 4->10
# only these destination nodes' information are being updated.
# and we examine the features:
# tensor([[4096, 4096, 4096, 4096], # node 12
#         [8192, 8192, 8192, 8192], # node 13
#         [ 512,  512,  512,  512], # node 9
#         [1024, 1024, 1024, 1024], # node 10
#         [ 256,  256,  256,  256], # node 8
#         [   4,    4,    4,    4], # node 2
#         [  16,   16,   16,   16]], dtype=torch.int32) # node 4

h1 = DummyLayer()(blocks[0], x)
# After applying the transformation along edges defined in block 0, we see the information is updated as:
# tensor([[4352, 4352, 4352, 4352], # node 12, as a sum of node 8 and node 12
#         [9216, 9216, 9216, 9216], # node 13, as a sum of node 10 and node 13
#         [ 516,  516,  516,  516], # node 9, as a sum of node 2 and node 9
#         [1040, 1040, 1040, 1040]], dtype=torch.int32) # node 10, as a sum of node 4 and node 10

# Now, if we examine block 1, we should see edges:
# 9->12
# 10->13

h2 = DummyLayer()(blocks[1], h1)
# After applying the transformation along edges defined in block 1, we see the information is updated as:
# tensor([[ 4868,  4868,  4868,  4868], # final result for node 12
#         [10256, 10256, 10256, 10256]], dtype=torch.int32) # final result for node 13

# for node 12, the sampling is:
# we start with [12]
# at first hop, we add 9: [12, 9]
# at second hop, we add:
#     8, since 12 is in the collection of seed node (this feature is discussed in DGL thread)
#     2, since 9 is in the collection of seed node
# so we have [12, 9, 2, 8]
# and the message passing path that DGL takes is:
# 2 -> 9 -> 12 <- 8
# so, the information that we get, should be all information that nodes 2, 8, 9, and 12 have:

# verified
# (2**9 + 2**12 + 2**8 + 2**2) == 4868

Hi @Elnifio，
Yes, this difference is caused by the different approaches of sampling and message passing in PyG and DGL.

I believe the two sampling approaches (GLT's and DGL's) would lead to mathematically equivalent outputs at the seed nodes in the top layer. See this thread on the PyG discussions: https://github.com/pyg-team/pytorch_geometric/discussions/5303  .
GLT's NeighborLoader introduces some redundant nodes in each layer that are not needed for producing the output at the seed nodes. The GNNs applied to GLT's sampled graphs would thus require more FLOPs/memory accesses than the GNNs applied to DGL's sampled blocks.  I modified the code above to show the equivalence in the produced outputs:

import graphlearn_torch as glt
import torch
import torch_geometric as pyg
import dgl

# to simplify the discussion, we create a tree for generating the samples.
u = torch.tensor([0, 1, 2, 3,  4,  5,  6,  7,  8,  9, 10, 11])
v = torch.tensor([8, 8, 9, 9, 10, 10, 11, 11, 12, 12, 13, 13])
edge_index = torch.stack([u, v], dim=0)

# and to trace which node is involved in the computation,
# the features are assigned as 2^i for node i
x = torch.stack([2**torch.tensor(range(14)) for _ in range(4)], dim=1).to(torch.float32)

class DummyLayerDGL(torch.nn.Module):
    def __init__(self):
        # Takes in source and destination nodes, adds them according to the edges, and returns it
        super().__init__()

    def forward(self, graph, hidden):
        graph = graph.local_var()
        graph.srcdata['temp_src'] = hidden[:graph.number_of_src_nodes()]
        graph.dstdata['temp_dst'] = hidden[:graph.number_of_dst_nodes()]
        graph.update_all(
            dgl.function.u_add_v('temp_src', 'temp_dst', 'temp'),
            dgl.function.sum("temp", "result")
        )
        new_hidden = graph.dstdata['result']
        return new_hidden

class DummyLayerGLT(pyg.nn.MessagePassing):
    def __init__(self):
        super().__init__(aggr="add")

    def forward(self, x, edge_index):
        return self.propagate(edge_index, x=x)

    def message(self, x_i, x_j):
        return x_i + x_j

# GLT
dataset = glt.data.Dataset(edge_dir="in")
dataset.init_graph(edge_index, graph_mode="CPU")
dataset.init_node_features(node_feature_data=x, with_gpu=False)
loader = glt.loader.NeighborLoader(
    dataset,
    [-1, -1],
    torch.tensor([12, 13]),
    batch_size=1
)
data = next(iter(loader))

h1_glt = DummyLayerGLT()(x, edge_index)
h2_glt = DummyLayerGLT()(h1_glt, edge_index)

#DGL
g = dgl.graph((u,v))
g.ndata['feat'] = x
sampler = dgl.dataloading.NeighborSampler([-1, -1])
loader = dgl.dataloading.DataLoader(g, torch.tensor([12, 13]), sampler, batch_size=2)
input_nodes, destination_nodes, blocks = next(iter(loader))

h1_dgl = DummyLayerDGL()(blocks[0],x[input_nodes])
h2_dgl = DummyLayerDGL()(blocks[1],h1_dgl)

#equivalence
assert torch.allclose(h2_dgl,h2_glt[[12,13]])


[bot] [main] Automated dependencies update

Looks like some of our dependencies got updated upstream!
This is an automated PR updating those dependencies.
Configuration of the workflow is located in .github/workflows/dep-update.yaml

had to revert this PR :( see https://github.com/gitpod-io/observability/issues/60 for details.


[Discussion] Upon saving, GitHub Configuration node doesn't update the setting, but should it?

We should probably update the configuration node when someone saves it.  Assuming that they change a setting in there, I think that they might expect that it would also update in the tree node
Repro steps:

Make a change in the workflow.yml
Save it
Nothing updates until you manually refresh

Closing as per offline feedback, we don't think it should update.


pack.yaml dependencies not working for gt\lt only for eq

Trying to install a pack with one dependency:
st2 3.4.1, on Python 3.6.9
dependencies in pack.yaml:
dependencies:
  - some_pack>=1.1.1

Full output:
{
  "output": {
    "packs_list": [
      "main_pack"
    ],
    "message": "",
    "conflict_list": [],
    "warning_list": null
  },
  "errors": [
    {
      "type": "error",
      "message": "Execution failed. See result for details.",
      "task_id": "download_pack",
      "result": {
        "stdout": "",
        "stderr": "Traceback (most recent call last):\n  File \"/opt/stackstorm/st2/lib/python3.6/site-packages/python_runner/python_action_wrapper.py\", line 334, in <module>\n    obj.run()\n  File \"/opt/stackstorm/st2/lib/python3.6/site-packages/python_runner/python_action_wrapper.py\", line 193, in run\n    output = action.run(**self._parameters)\n  File \"/opt/stackstorm/packs/packs/actions/pack_mgmt/download.py\", line 89, in run\n    return self._validate_result(result=result, repo_url=pack_url)\n  File \"/opt/stackstorm/packs/packs/actions/pack_mgmt/download.py\", line 110, in _validate_result\n    raise Exception(message)\nException: The pack has not been downloaded from \"None\".\n\nErrors:\nNo record of the \"some_pack>\" pack in the index.\n",
        "exit_code": 1,
        "result": "None"
      }
    }
  ]
}

Full output in CLI:
        [ succeeded ] init_task
        [ succeeded ] download_pack
        [ succeeded ] make_a_prerun
        [ succeeded ] get_pack_dependencies
        [ succeeded ] check_dependency_and_conflict_list
        [  failed   ] download_pack

id: 610ab23bb9c6ebf292ba7a83
action.ref: packs.install
parameters:
  packs:
  - main_pack=dependencies_check
status: failed
start_timestamp: Wed, 04 Aug 2021 15:28:58 UTC
end_timestamp: Wed, 04 Aug 2021 15:29:16 UTC
result:
  errors:
  - message: Execution failed. See result for details.
    result:
      exit_code: 1
      result: None
      stderr: "Traceback (most recent call last):
  File "/opt/stackstorm/st2/lib/python3.6/site-packages/python_runner/python_action_wrapper.py", line 334, in <module>
    obj.run()
  File "/opt/stackstorm/st2/lib/python3.6/site-packages/python_runner/python_action_wrapper.py", line 193, in run
    output = action.run(**self._parameters)
  File "/opt/stackstorm/packs/packs/actions/pack_mgmt/download.py", line 89, in run
    return self._validate_result(result=result, repo_url=pack_url)
  File "/opt/stackstorm/packs/packs/actions/pack_mgmt/download.py", line 110, in _validate_result
    raise Exception(message)
Exception: The pack has not been downloaded from "None".

Errors:
No record of the "some_pack>" pack in the index.
"
      stdout: ''
    task_id: download_pack
    type: error
  output:
    conflict_list: []
    message: ''
    packs_list:
    - main_pack
    warning_list: null
+--------------------------+------------------------+----------------------+----------------------+------------------+
| id                       | status                 | task                 | action               | start_timestamp  |
+--------------------------+------------------------+----------------------+----------------------+------------------+
| 610ab2419daca84b6f154059 | succeeded (0s elapsed) | init_task            | core.noop            | Wed, 04 Aug 2021 |
|                          |                        |                      |                      | 15:29:05 UTC     |
| 610ab2429daca84b6f154069 | succeeded (5s elapsed) | download_pack        | packs.download       | Wed, 04 Aug 2021 |
|                          |                        |                      |                      | 15:29:06 UTC     |
| 610ab2479daca84b6f154079 | succeeded (1s elapsed) | make_a_prerun        | packs.virtualenv_pre | Wed, 04 Aug 2021 |
|                          |                        |                      | run                  | 15:29:11 UTC     |
| 610ab2489daca84b6f154089 | succeeded (1s elapsed) | get_pack_dependencie | packs.get_pack_depen | Wed, 04 Aug 2021 |
|                          |                        | s                    | dencies              | 15:29:12 UTC     |
| 610ab2499daca84b6f154099 | succeeded (1s elapsed) | check_dependency_and | core.noop            | Wed, 04 Aug 2021 |
|                          |                        | _conflict_list       |                      | 15:29:13 UTC     |
| 610ab24a9daca84b6f1540a9 | failed (2s elapsed)    | download_pack        | packs.download       | Wed, 04 Aug 2021 |
|                          |                        |                      |                      | 15:29:14 UTC     |
+--------------------------+------------------------+----------------------+----------------------+------------------+

Do we support version operators other than equality? I thought we did but I'm not finding any tests for that, and I'm digging through the code and haven't yet found where we parse individual dependency specifiers. My search is ongoing.

Nope, it looks like we only support equality operators for specifying pack dependencies:

https://github.com/StackStorm/st2/blob/911e2e16d7a356df1bb3992bb9d06829db36ab05/st2common/st2common/constants/pack.py#L48
https://github.com/StackStorm/st2/blob/911e2e16d7a356df1bb3992bb9d06829db36ab05/contrib/packs/actions/pack_mgmt/get_pack_dependencies.py#L113

@DavidMeu Sorry for misleading you!
I'm naïvely going to say: this shouldn't be super duper difficult to implement, and I think it would have a good deal of benefit for users.


Research and test modules for social media publishing from COD site

@alisonjo2786 Want to look into this?

Marking for 2016, unless Alison wants to look into it.

2016 works for me :)


Cache JsonGeneratorFactory

Currently a new JsonGeneratorFactory is created for every log record.
This can quickly get quite expensive as it uses ServiceLoader to find
possible implementations that does resource lookup through JBoss VFS.
JsonGeneratorFactory instances are by specification safe for access by
multiple threads and can therefore easily be cached.

cache JsonGeneratorFactory
create a new JsonGeneratorFactory every time the configuration is
changed
remove no longer needed synchronization for creating a JsonGenerator

Thanks! I need to take a closer look at this, but I definitely think something like this should be done.


Add zero checking to Unweighted for CPU code

No changes to the GPU code (apart from some restructuring), would not have been beneficial.

The runtime for EMP unweighted_fp32 on a AMD EPYC 7302
is reduced from ~270s to ~175s.

CC @wasade

All seems reasonable from what I can grok :)


system dependent file handling

In some routines path-separators are hard-coded and therefore not system-independent.
Mainly occurring in:
ogs5py/reader/reader.py
ogs5py/ogs.py

Solved by: https://github.com/MuellerSeb/ogs5py/commit/ce02db89909f8ccc24cfcafa14cedab72870f095
Closed!


Documentation feedback on /docs/getting-started/first-use.rst

Documentation feedback

Page title: First use
Page URL: https://cratedb.com/docs/crate/howtos/en/latest/getting-started/first-use.html
Source: https://github.com/crate/crate-howtos/blob/master/docs/getting-started/first-use.rst

The first link behind "installed and running" doesn't make a lot of sense to me. Shouldn't that maybe link to https://cratedb.com/docs/crate/tutorials/en/latest/ instead?

Hi Michael,
thanks for your report. While I don't know what is wrong over there, at the new location, the link is apparently correct, see https://cratedb.com/docs/guide/getting-started/introduction.html.
With kind regards,
Andreas.

Hi Andreas,
I had a look at it on Friday last week and was confused since it showed the same content on both locations, and I wasn't sure what the plan was there. Now the legacy version is offline and results in a 404 error message. Shouldn't there be redirects created in order to avoid that happening?

Hi again,

I had a look at it on Friday last week and was confused since it showed the same content on both locations, and I wasn't sure what the plan was there.

cratedb-guide will be the new thing.

Now the legacy version is offline and results in a 404 error message.

I don't see where the legacy version isn't available. The corresponding spot on the new location has been refactored and is now located at https://cratedb.com/docs/guide/getting-started.html.

Shouldn't there be redirects created in order to avoid that happening?

The new version isn't live, yet, so refactoring work on it does not require any updates to web server redirects.
With kind regards,
Andreas.

Sorry, I've must have confused the links. But to summarize, did I understand it correctly this way?

https://cratedb.com/docs/crate/howtos/en/latest/getting-started/first-use.html is live but contains the wrong link
https://cratedb.com/docs/guide/getting-started.html is the new version and is not live yet
https://cratedb.com/docs/guide/getting-started/introduction.html is a 404 on my end.

If so, when is the plan that 2 is going to be live? Depending on the timeline, would it make sense to simply correct the link on 1 in the meantime since this has already been reported 3 months ago?

All yes! Going live is around the corner, but any fixes are always appreciated!


chore: accessibility improvement

Small accessibility defect in CSS when using "outline: none" was fixed. Made simple changes following best practices to prevent users with higher contrasts from experiencing bugs when using the tab key to select buttons, inputs, etc. Reference: https://www.youtube.com/shorts/4B_4WLpbyp8

Thank you very much!


feature: add vim bindings

It would be great for us transitioning from fzf to get the following features:

VIM bindings for item navigation
Override item navigationhishtory keybindings.

fzf bindings:

ctrl+k: up
ctrl+j: down

Since hishtory binds ctrl+k to delete item, overriding that would be a requirement for adopting VIM bindings.
related: https://github.com/ddworken/hishtory/issues/55

Thanks for filing this! The core code for this is actually already in place since we already use a keymap to store configurable key bindings, it just isn't wired up to the config to enable actually customizing this. I'll try to take this on relatively soon, but if anyone is looking to make a contribution, I think this could be a good starter one. :)

This is now fully released and available, if you run hishtory update you can now customize the key bindings. Check out the README for information on how to do this. If you run into any issues, please re-open this issue to let me know. :)


Bump filepath upper version bounds

Allow packunused to build with filepath-<IP_ADDRESS> (and GHC 7.10, moreover).

thanks; in the meantime I've edited the .cabal file on the latest packunused release to get this change public quickly


refactor Remove IntAtomicCounter & CoreLocal #45742

cherry pick from #45742

run buildall

Thank you for your contribution to Apache Doris.
Don't know what should be done next? See How to process your PR.
Please clearly describe your PR:

What problem was fixed (it's best to include specific error reporting information). How it was fixed.
Which behaviors were modified. What was the previous behavior, what is it now, why was it modified, and what possible impacts might there be.
What features were added. Why was this function added?
Which code was refactored and why was this part of the code refactored?
Which functions were optimized and what is the difference before and after the optimization?


Hello, how i can run the code on multiple cuda cards?

i am not exactly sure that this one is correct
python app.py --device cuda:0

Hello, thanks for your interest. Currently, TAM cannot run on multiple GPUs. This command is correct and would run TAM on the first GPU card. Thanks.


Added support for ML

Closes #112

:exclamation: I see a lot of newly introduced "SHOULD", "MUST", "MUST NOT" introduced in XML documentations.
If there are such rules, then a xs:restriction is to be formulated, or else we would end up like SPDX where a lot of text describes the format, but nothing machine-readable makes this clear.
I'd recommend creating a followup-task that takes care of this, after this PR was merged.

@stevespringett  - what is the best way to reference model versioning? In case data, the version information i assume would be in its BOM?


Generate multiple svg graphs

This work is based on #530 and should be merged in after that PR.
Example Usage:
import graph_render

graph1 = graph_render.GraphData(['Time (ms)'], 'graph1.csv', 'First Graph')
graph2 = graph_render.GraphData(['Demographic', 'Currency'], 'graph2.csv', 'Second Graph')

graph_render.gen_graphs([graph1, graph2])

I'm on this, thanks @glinesbdev !

Done in https://github.com/gbdev/pandocs/blob/master/src/imgs/src/preproc.py (PR https://github.com/gbdev/pandocs/pull/530)


Update README.md

Current coverage is 91.55%

Merging #34 into master will not affect coverage as of 2e49e11

@@            master     #34   diff @@
======================================
  Files           19      19
  Stmts          521     521
  Branches         0       0
  Methods        120     120
======================================
  Hit            477     477
  Partial          0       0
  Missed          44      44

Review entire Coverage Diff as of 2e49e11

Powered by Codecov. Updated on successful CI builds.