Attributes matcher no longer supports full rspec matcher interface (like composability)

Prior to v3, the attributes matcher was defined using the Rspec DSL (RSpec::Matchers.define) which meant that the resulting matcher(s) was a subclass of rspec's built-in matcher hierarchy.
This meant that the matchers were chainable, composable, diffable, and recursive.
Now with v3, the pundit-matchers base matcher does not inherit from the core rspec matchers, and thus breaks the interfaces that rspec matchers support.
Most notably for this issue, chaining:
Before, the following worked:
it { is_expected.to permit_attributes(%w[
         actual_custom_rate
         estimated_custom_rate
       ])
         .and forbid_attributes(%w[
           estimated_inside_dimensions
           estimated_outside_dimensions
           actual_inside_dimensions
           actual_outside_dimensions
           estimated_cube
}

Now, it generates an error:
NoMethodError:
       undefined method `and' for #<Pundit::Matchers::PermitAttributesMatcher:0x00007f2c96d26a08 @expected_attributes=[:actual_custom_rate, :estimated_custom_rate], @options={}>

                 .and forbid_attributes(%w[
                 ^^^^

I think including the Composable module may be all that's necessary?
https://github.com/rspec/rspec-expectations/blob/main/lib/rspec/matchers/composable.rb

Hi @jasonkarns, any chance to giva a try to #108?

This meant that the matchers were chainable, composable, diffable, and recursive.

I've tried and and it works, I don't know what else I can try

I've been OOO for a bit, so I can give the new releases a try, thank you!!!

Updated and confirmed, the new release with these changes works a treat! thank you, @chrisalley @tagliala !


Switch from nose to pytest

Nose hasn't been updated in a couple years. In addition, it is LGPL, which can pose problems for some licensing requirements. Let's switch to pytest, which has everything we need and more.

Coverage decreased (-0.2%) to 98.813% when pulling 90b3c1c15a63c03a86f66041e452c72ea44e6d39 on toddpalino:use-pytest into 21caec2078373e23f17724b061b4ad758ef96542 on linkedin:master.

Codeclimate issues are not actually in this PR


redirect_url not working?

Maybe I am misunderstanding how this should work, but, I thought that the redirect_url would be visited after signup.
In config/initializers/clearance.rb I have set:
Clearance.configure do |config|
  config.routes = false
  config.mailer_sender =<EMAIL_ADDRESS>  config.rotate_csrf_on_sign_in = true
  config.redirect_url = "/thank_you"
end

But /thank_you is never visited after a signup (or any time).
I also created app/controllers/users_controller.rb with:
class UsersController < Clearance::UsersController

  private

  def url_after_create
    "/thank_you"
  end
end

Yet still /thank_you is never visited.
What needs to be done to actually get new users sent to a new page so we can track them in analytics?

Hi @philsmy, thanks for the question. After a user signs up, Clearance redirects using redirect_back_or
https://github.com/thoughtbot/clearance/blob/fbaf5cf368bc6512c11251559c5ecb655276994f/lib/clearance/authorization.rb#L80-L83
This will redirect back to the URL the user was originally attempting to access if they were attempting to access an action protected by require_login. If the user did not try and access an action protected by require_login, they will be redirected to the redirect_url.
If your application uses require_login for the entire application then the user will always be redirected back to the URL they initially attempted to visit.

Ok. How can we direct a person to a thankyou page after signup, regardless of what will happen after a non signup login? Seems odd to me that 'url after create' does nothing!

The most straightforward way would likely be to override  the UsersController create action and change
redirect_back_or url_after_create

to
redirect_to url_after_create


fix: settings from env

Overview
Problem
Fix for issue #992
Solution
Describe the implemented solution. Add external references if needed.
Screenshot/Demo
A picture is worth a thousand words. Please highlight the changes if applicable.
How to test

Steps to be followed to verify the solution or code changes
Mention if there is any settings configuration added/changed/deleted

Checklist

[ ] I have run this code and it appears to resolve the stated issue
[ ] README.md updated and added information about my change

integrated.terminal.env will be tricky. There can be multiple terminal and each terminal have different value for same env var. Also not sure about whether the value be retained after reload?


Add a thin wrapper around otel Span object

Follow up to the one of the comments in https://github.com/containerd/containerd/pull/7453#discussion_r1012470485
This PR wraps the otel Span object and implements related methods which is used during tracing instrumentation.
Also, adds a new SpanName method as discussed in https://github.com/containerd/containerd to add a common seaprator in span names /pull/7453#discussion_r1012469550
Signed-off-by: Swagat Bora<EMAIL_ADDRESS>

/cc @mxpv


Intermittent issue PA2ErrorDomain Code: 4 on custom activation (iOS)

Some instances of the custom activation on iOS fail with the PA2ErrorDomain Code: 4. We are currently not able to reproduce the issue and it happens to a very small fraction of the user base, but we should investigate it anyway.

Our code has several rooms for improvement:

We should be checking the output of JSON parsing for errors in custom activation method, so that we can differentiate JSON parsing related errors better.
We should be checking for HTTP status code - while the server should technically return only status codes handled by SDK, we are unable to assure this in case of the custom activation, since the back-end code is implemented by the bank API provider (not part of our SDK).

This is a kind of improvement. When there's an error during the activation, the application has usually only one option how to react on that situation and must restart the activation process. So, the actual goal is make our SDK more friendly for debugging.
I agree that we need to improve our error reporting. Here's my additional list of ideas:

It's unfortunate that SDK is hiding some error states reported from low level code or reinterprets them to more vague meaning. We should just extend "core" error codes with values needed in high level code.
We should add textual description to reported NSErrors. That might improve debugging a lot.

Just for note. I've created a separate tickets (#49 #50) for that error reporting improvements.

Not a bug. An error reported back to customer's application is correct, but not very descriptive. We'll address this reporting enhancements in separate issues.


Make Sweeper config variable names consistent

We have one setting name prefixed with "sweeper." and some other ones starting with "riak_kv.sweep." All the sweeper options should probably start with the same prefix.
Additionally, since "Riak KV" means "Riak, the KV store database" to the general public, we shouldn't be prefixing settings with "riak_kv" (especially since we could merge the sweeper over to Riak TS at some point ;-)
Using the "sweeper." prefix everywhere is succinct and helpful, since Cuttlefish is meant to be user-friendly, and customers will think of the Sweeper as its own distinct component. Whichever application it happens to be located in is probably irrelevant to them, hence my decision to kill the "riak_kv." prefix.

:+1:

+1


Need Some delay before showing new container

var MenuTransition = Barba.BaseTransition.extend({

	  start: function() {
	    Promise
	      .all([this.newContainerLoading, this.createBox()])
	      .then(
========================================
 I need Some delay here, the page loades to fast , so the effects end within ms.
so is it possible to add some delay after new container loaded but end when the efects end
========================================

	      this.hideBox.bind(this)
	      );
	  },
		createBox: function(){
		// Box effect
		},
		hideBox: function(){
		// hide the box
		}
});

I am using gasp to animate elements but the page load too fast and my effects ends before fully completing the effect.
can i add some delay on promise.

Why not create the box before the page transitions? Then you can add a promise to the box animation that resolves on the animation complete method, then trigger the container to load. I'm using anime.js so I'm not sure about GSAP, but I do it like this:
  var MaskTransition = Barba.BaseTransition.extend({
    start: function() {
      Promise
        .all([this.newContainerLoading, this.maskOut()])
        .then(this.maskIn.bind(this));
    },
    maskOut: function() {
      // Create the promise here, so that nothing else runs until this promise is resolved.
      return new Promise((resolve, reject) => {
        anime({
          targets: '.cover',
          clipPath: [initial, show],
          webkitClipPath: [initial, show],
          duration: duration,
          easing: 'easeInOutQuart',
          complete: () => {
            // Resolve the promise.
            resolve();
          }
        })
      });
    },
    maskIn: function() {
      var _this = this;
      var $el = $(this.newContainer);

      $(this.oldContainer).hide();

      $el.css({
        visibility: 'visible',
        opacity: 1
      });

      anime({
        targets: '.cover',
        clipPath: [show, hide],
        webkitClipPath: [show, hide],
        duration: duration,
        delay: 250,
        easing: 'easeInOutQuart',
        complete: function(anim) {
         // Complete the transition
          _this.done();
        }
      })

    }
  });

  Barba.Pjax.getTransition = function() {
    return MaskTransition;
  };

    var PortFolioTransition = Barba.BaseTransition.extend({
        start: function() {
            this.originalThumb = lastElementClicked;
            this.immediateRender = false;

            Promise
                .all([this.newContainerLoading, this.enlargeThumb()])
                .then(this.showNewPage.bind(this));
        },

        enlargeThumb: function() {
            var deferred = Barba.Utils.deferred();
            var thumbPosition = this.originalThumb.getBoundingClientRect();
            var image = $(this.originalThumb).find("img");
            var tl = new TimelineLite({ onComplete: deferred.resolve() });

            tl
                .set(image, {
                    autoAlpha: 1,
                    "z-index": "9999999"
                })
                .fromTo(image, 3, {
                    scale: 1,
                    immediateRender: this.immediateRender,
                    ease: Power2.easeOut

                }, {
                    scale: 6,
                    top: 0,
                    ease: Power2.easeOut
                }), deferred.resolve

            return deferred.promise;
        },

        showNewPage: function() {

            // var TTLite = new TimelineLite({
            //            onCompleteScope: this,
            //            onComplete: function() {
            //               this.done() , afterDomReloaded()
            //            }
            //        });

            var _this = this;
            var $el = $(this.newContainer);

            $(this.oldContainer).hide();

            $el.css({
                visibility: 'visible',
                opacity: 0,
            });

            $el.animate({
                opacity: 1
            }, 400, function() {
                _this.done();
            });
        }

    });

on my code.fromTo(image, 3, {  you can see i give duration value 3 but the animation ends before completing full cycle , can you point out where i am doing wrong

I would maybe try adding a delay to your next animation to account for a page loading quicker than the animation. If you look at the maskIn animation on my transition you'll notice it has a little delay to account for this.
Unfortunately without seeing your transition in action, it's hard to dissect the issue.

You can just use delay on your gsap animation, no?


Extension issue

Issue Type: Bug
Extension Name: code-settings-sync
Extension Version: 3.4.3
OS Version: Windows_NT x64 10.0.19042
VS Code version: 1.55.2

:warning: We have written the needed data into your clipboard. Please paste! :warning:

Same happens to me with C# Extensions.


[dev] Updated README.md to state bot status

Added bot status to top of README.md to limit issue posts.

Can you use the same message as this PR: https://github.com/PokemonGoF/PokemonGo-Bot/pull/2590

Done.

👍

👍

:+1:


[$250] mWeb - Chat - Before emoji picker box opens, a seperate compose box with cursor is shown briefly

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 1.4.63
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/4499507
Issue reported by: Applause - Internal Team
Action Performed:

Go to https://staging.new.expensify.com/home
Tap on a report
Tap emoji picker in compose box
Select an emoji
Note size of emoji in compose box is bigger compare to production
Select one more emoji
Send the message
Long press the sent message amd tap edit comment
Tap emoji picker from edit compose box

Expected Result:
Before emoji picker box opens, a separate compose box with cursor must not be shown briefly while edit comment
Actual Result:
Before emoji picker box opens, a separate compose box with cursor is shown briefly while edit comment
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

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

Screenshots/Videos
Add any screenshot/video evidence

https://github.com/Expensify/App/assets/78819774/73d3db0c-d2a4-4595-a609-40a192b7df4e
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01030e7a0cab136f03
Upwork Job ID:<PHONE_NUMBER>291671552
Last Price Increase: 2024-04-22
Automatic offers:

s77rt | Reviewer | 0
bernhardoj | Contributor | 0

@puneetlath  FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors

We think that this bug might be related to #vip-vsp

Proposal
Please re-state the problem that we are trying to solve in this issue.
The main composer is shown when opening the edit composer emoji picker.
What is the root cause of that problem?
When we focus on an edit composer, the main composer will be hidden. But when the edit composer is blurred, the main composer will shown again. In this case, when we press the emoji picker button, the edit composer will be blurred.
But actually, we already prevent the main composer from showing when we press the emoji picker button as shown here.
https://github.com/Expensify/App/blob/305f12c52ef228e7ed4845735a1794942a2b8d87/src/pages/home/report/ReportActionItemMessageEdit.tsx#L449-L457
The way it works is, that if the pressed element is an emoji picker button ID, then don't show the main composer yet. However, the emoji picker button element doesn't have the ID set.
We already pass the ID here,
https://github.com/Expensify/App/blob/305f12c52ef228e7ed4845735a1794942a2b8d87/src/pages/home/report/ReportActionItemMessageEdit.tsx#L469
However, the pressable component accepts nativeID prop instead of id.
https://github.com/Expensify/App/blob/305f12c52ef228e7ed4845735a1794942a2b8d87/src/components/Pressable/GenericPressable/index.tsx#L19
https://github.com/Expensify/App/blob/305f12c52ef228e7ed4845735a1794942a2b8d87/src/components/Pressable/GenericPressable/index.tsx#L26
What changes do you think we should make in order to solve the problem?

Rename the props from id to nativeID specifically in EmojiPickerButton (or we can rename the pressable props to id, but we need to rename it for many components too).
we may need to check for messageEditInput ID too
Note: in native, the main composer will still appear (even though covered by the modal) because it's blurred when the modal shows. To further improve it, we can ignore the blur when the emoji picker modal is active.
if (relatedTargetId && [messageEditInput, emojiButtonID].includes(relatedTargetId) || EmojiPickerAction.isActive(action.reportActionID)) {
    return;
}

But there are currently 2 issues with EmojiPickerAction.isActive. EmojiPickerAction.isActive compares the active ID and the passed ID.
https://github.com/Expensify/App/blob/305f12c52ef228e7ed4845735a1794942a2b8d87/src/components/EmojiPicker/EmojiPicker.tsx#L150
The active ID is set after calculating the anchor position, but we need to set it immediately when calling showEmojiPicker.
https://github.com/Expensify/App/blob/305f12c52ef228e7ed4845735a1794942a2b8d87/src/components/EmojiPicker/EmojiPicker.tsx#L88-L100
Second, we never clear the active ID when closing the emoji picker, so we need to do that.

@s77rt FYI there is already a proposal above.

@bernhardoj Thanks for the proposal. Your RCA is correct. This looks to be a regression from https://github.com/Expensify/App/pull/24482/commits/822efb502d1442bcbe5a7a9e3c504a90b0ca07c7. Regarding the web solution, we should use id since nativeID is deprecated. Regarding native, did you try clearing the active action? I remember we had some tricky bugs on that area and a lengthy issue https://github.com/Expensify/App/issues/23908

Yes, I tried it. The isActive issue of emoji picker is also mentioned in the proposal there

but instead of clearing it when other edit message is focused, we should clear it when the emoji picker hides.
btw, the 3rd case in the linked issue happens on main

@bernhardoj

but instead of clearing it when other edit message is focused, we should clear it when the emoji picker hides

That was the first attempt but didn't work well when a message is deleted from another device while the emoji picker for that message is still open. Let's test that scenario as well as other cases where EmojiPickerAction.isActive is used.
🎀 👀 🎀 C+ reviewed
Link to proposal

Not overdue. @puneetlath ^

PR is ready
cc: @s77rt

PR was deployed to production 2 weeks ago

Whoops, right you are. Can you complete the checklist @s77rt?

@bernhardoj has been paid.
@s77rt payment just pending checklist above.

The PR that introduced the bug has been identified: https://github.com/Expensify/App/pull/24482
The offending PR has been commented on: https://github.com/Expensify/App/commit/822efb502d1442bcbe5a7a9e3c504a90b0ca07c7#r142442593
A discussion in #expensify-bugs has been started: I don't feel we have much to discuss, the bug was caused by conflicts
Determine if we should create a regression test for this bug: No

@puneetlath Done!

kk all paid. Thanks everyone and sorry for the delay!


[BEAM-11943] Fix wrong Klio logo being displayed

The logo for Klio was pointing to the Scio logo on the start page. This PR changes it to the correct Klio path. The Klio logo is already in the repository, so it's a simple path change.

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.

GitHub Actions Tests Status (on master branch)

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

Reviewer: @TheNeuralBit
Adding you since I saw you merged the PR that introduced the Klio text :smile:
See: https://github.com/apache/beam/pull/13596


Using pqc-kyber NPM

I would really like to try and use the NPM package with the WASM implementation but am having issues
This relative module was not found:
This relative module was not found:
* ./pqc_kyber_bg.js in ./node_modules/pqc-kyber/pqc_kyber_bg.wasm

Is there an example implementation around anywhere with the wasm exports being used?
I've also tried building it myself from this repo but am met with the "js" feature issue below. Unfortunately this was my first interaction with rust and I am unable to solve.
wasm-pack build -- --features wasm
[INFO]: Checking for the Wasm target...
[INFO]: Compiling to Wasm...
   Compiling proc-macro2 v1.0.27
   Compiling unicode-xid v0.2.2
   Compiling syn v1.0.72
   Compiling wasm-bindgen-shared v0.2.74
   Compiling log v0.4.14
   Compiling cfg-if v1.0.0
   Compiling bumpalo v3.7.0
   Compiling lazy_static v1.4.0
   Compiling cc v1.0.68
   Compiling wasm-bindgen v0.2.74
   Compiling getrandom v0.2.3
error: the wasm32-unknown-unknown target is not supported by default, you may need to enable the "js" feature. For more information see: https://docs.rs/getrandom/#webassembly-support
   --> /home/altfreq/.cargo/registry/src/github.com-1ecc6299db9ec823/getrandom-0.2.3/src/lib.rs:219:9
    |
219 | /         compile_error!("the wasm32-unknown-unknown target is not supported by \
220 | |                         default, you may need to enable the \"js\" feature. \
221 | |                         For more information see: \
222 | |                         https://docs.rs/getrandom/#webassembly-support");
    | |_________________________________________________________________________^

error[E0433]: failed to resolve: use of undeclared crate or module `imp`
   --> /home/altfreq/.cargo/registry/src/github.com-1ecc6299db9ec823/getrandom-0.2.3/src/lib.rs:246:5
    |
246 |     imp::getrandom_inner(dest)
    |     ^^^ use of undeclared crate or module `imp`

error: aborting due to 2 previous errors

For more information about this error, try `rustc --explain E0433`.
error: could not compile `getrandom`

To learn more, run the command again with --verbose.
warning: build failed, waiting for other jobs to finish...
error: build failed
Error: Compiling your crate to WebAssembly failed
Caused by: failed to execute `cargo build`: exited with exit code: 101
  full command: "cargo" "build" "--lib" "--release" "--target" "wasm32-unknown-unknown" "--features" "wasm"

add this in Cargo
getrandom = { version = "0.2.7", features = ["js"] }

There was some API changes from  0.1 so you will also have to modify the wasm module to accommodate that.
When I get some time this week I'll patch it up and publish to npm. Will bump the crates version with a zeroise feature also.

There was some API changes from 0.1 so you will also have to modify the wasm module to accommodate that.
When I get some time this week I'll patch it up and publish to npm. Will bump the crates version with a zeroise feature also.

btw, awesome library works like a charm, running it here , great work (WASM binary on the client executing without a hitch)
https://zkbitcoin.com/qm?algorithm=Kyber

New version published: https://www.npmjs.com/package/pqc-kyber
Also added:

Readme with js examples in pkg/
Runnable demo in www/


fix urlib opener bug

CATEGORY
Choose one

[x] Bug Fix
[ ] Enhancement (new features, refinement)
[ ] Refactor
[ ] Add tests
[ ] Build / Development Environment
[ ] Documentation

SUMMARY
urllib opener does not have any method called content and for getting the content of the response should invoke read() method.
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TEST PLAN

ADDITIONAL INFORMATION

[x] Has associated issue: #8784 #8286
[ ] Changes UI
[ ] Requires DB Migration.
[ ] Confirm DB Migration upgrade and downgrade tested.
[ ] Introduces new feature or API
[ ] Removes existing feature or API

REVIEWERS

Codecov Report

Merging #8788 into master will increase coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #8788      +/-   ##
==========================================
+ Coverage   65.83%   65.83%   +<.01%
==========================================
  Files         482      482
  Lines       24155    24156       +1
  Branches     2770     2770
==========================================
+ Hits        15903    15904       +1
  Misses       8074     8074
  Partials      178      178

Impacted Files
Coverage Δ

superset/tasks/schedules.py
80% <100%> (+0.1%)
: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 ed3944e...4c4b4d3. Read the comment docs.

This feature was community contributed and isn't actively used by the committers. Merging

It's really a good feature


README instructions usage

Refined instructions on how to use with Linode :D

Accepting PRs, is there a specific question you have?


Failed to verify bitcode in Alamofire

I am getting this error and no idea why. I have tried with bitcode both on and off, and went down from v3.0 beta 3 to version 2 just to see if that would help. This only happened after i started use xcode 7. I already converted project to swift 2.0 as well, app works fine when i install it from xcode. I use carthage to build build the framework. Any help would be greatly appreciated, as i was supposed to pass along a build and i have been very delayed because of it. Here is the full error:
Failed to verify bitcode in Alamofire.framework/Alamofire:
error: Bundle only contains bitcode-marker /var/folders/r3/j_762c094837jhnv929gq1mw0000gn/T/XCodeDistPipeline.TvV/Root/Payload/my.app/Frameworks/Alamofire.framework/Alamofire (armv7)
bitcode stripping fails as well.

The carthage build works properly on 3.0.0-beta.3.
cnoon:~/Desktop/CarthageTester$ carthage update --platform iOS
*** Fetching Alamofire
*** Checking out Alamofire at "3.0.0-beta.3"
*** xcodebuild output can be found in /var/folders/s7/qpm0b2pn3d56rjlpl7g3_4fh0000gn/T/carthage-xcodebuild.eI0AZs.log
*** Building scheme "Alamofire iOS" in Alamofire.xcworkspace
cnoon:~/Desktop/CarthageTester$

Support questions like this are better suited for Stack Overflow. If you do end up finding an actual issue in the Alamofire project, please comment back on this issue and I'll be happy to re-open if necessary.
Best of luck!

I never said the issue was compiling, it was with creating an adhoc dstribution. I found this about the issue:
A framework with bitcode enabled requires the following flag to create and fill the bitcode section, -fembed-bitcode. However, this flag is available only in archive builds, not in normal builds where it's used the flag -fembed-bitcode-marker which creates a bitcode section but has a size of 1.
Carthage doesn't use archive action to build frameworks which means the resulting framework will contain a bitcode section but not properly filled as expected, leading to some issues in the submission of apps to TestFlight for example.
it is from https://github.com/thoughtbot/Argo/pull/260

A user-defined-setting of "BITCODE_GENERATION_MODE" set to "bitcode" is what is needed in the framework project before it will be able to work from a carthage compilation.

Thanks for adding more detail @silver619. You original question simply did not have enough info to go on.
After digging in to understand what's going on, I tracked down Carthage #535 which contains quite a few details about the required change. It appears that bitcode support is compiled differently between normal builds and archived builds. To allow Carthage to work properly, I have added the BITCODE_GENERATION_MODE user defined setting with a value of bitcode to all three framework targets in f6e19674.
This should fix up the issue. If you could possibly test this @silver619, I'd really appreciate it. Thanks again!

I have actually already tested it myself with a test project where i had  manually added it into the checkout. I am manually adding it to all the other projects i have got downloaded from carthage and in the process of building it for my main project.
If i want to test your latest change with the test project how can i do that with carthage? Do i use "head" in the cartfile?

You would use:
github "Alamofire/Alamofire" "master"

It works now.

@cnoon please note that you don't need to set BITCODE_GENERATION_MODE=bitcode to both release and debug configurations, only release configurations requires this for posterior submission. For debug configurations you can simply set ``BITCODE_GENERATION_MODE=marker`.

Yeah that makes sense. Updated all frameworks in 4a213ebe and 373293c0.

:+1:


Add warn log level, importUrl argument for device drivers, and fix signal strength attribute

It looks like the build on this is failing because it is trying to push the artifacts?

Yeah, publishing is not even supposed to be run automatically. I'm not sure how to stop github from triggering it though. I'm new at this )

Sweet, well in that case, I think this is good to go


Interacting with Cloud Monitoring API V3 - Got an unexpected keyword argument "interval"

We are trying to call this method: https://cloud.google.com/monitoring/api/ref_v3/rest/v3/projects.timeSeries/list through python client and got execution complaining 'Got an unexpected keyword argument "interval"'
Below is the sample code
from googleapiclient import discovery
import datetime
from datetime import timedelta

monitor_client = discovery.build('monitoring', 'v3', cache_discovery=False)
service_list_parent = "projects/123456"
montioring_filter = """
metric.type="serviceruntime.googleapis.com/quota/allocation/usage" resource.type="consumer_quota"
"""
now = datetime.datetime.now(datetime.timezone.utc)
one_hour_ago = now - timedelta(hours=1)
now = now.isoformat()
one_hour_ago = one_hour_ago.isoformat()
interval = {
     "endTime": now,
     "startTime": one_hour_ago
}

metric = monitor_client.projects().timeSeries().list(name=service_list_parent, filter=montioring_filter, interval=interval).execute()

Hi,
If possible, please use google-cloud-monitoring as that client is more modern and should generally be easier to use. Differences between google-cloud-* clients and this library are described in https://github.com/googleapis/google-api-python-client#other-google-api-libraries. You can also find code samples for google-cloud-monitoring at  https://cloud.google.com/monitoring/docs/samples.
It looks like list expects separate args interval_endTime and interval_startTime rather than one interval.
https://googleapis.github.io/google-api-python-client/docs/dyn/monitoring_v3.projects.timeSeries.html#list
If you need to look up other methods the directory for generated reference documents is at https://googleapis.github.io/google-api-python-client/docs/dyn/.

Thanks @busunkim96 , interval_endTime worked for me! I think it is just the official api documentation a bit misleading because it is requesting a 'interval' object.


spec: simplify handling of  --ulimit host

it seems enough to not specify any ulimit block to maintain the host
limits.
Signed-off-by: Giuseppe Scrivano<EMAIL_ADDRESS>

I'm always in favor of simplification... LGTM, but your tests are red

LGTM

@giuseppe, the only diff I found with the hosts limit is the soft limit for open files (host=1024, ctr=524288=hard limit). The behaviour is the same prior to this change.

that happens because we bump immediately the limit in main_local.go.

/lgtm


K8SPS-367: delete-mysql-pvc finalizer

CHANGE DESCRIPTION
Problem:
Add support for delete-mysql-pvc finalizer.
CHECKLIST
Jira

[x] Is the Jira ticket created and referenced properly?
[x] Does the Jira ticket have the proper statuses for documentation (Needs Doc) and QA (Needs QA)?
[x] Does the Jira ticket link to the proper milestone (Fix Version field)?

Tests

[x] Is an E2E test/test case added for the new feature/change?
[x] Are unit tests added where appropriate?

Config/Logging/Testability

[x] Are all needed new/changed options added to default YAML files?
[x] Did we add proper logging messages for operator actions?
[x] Did we ensure compatibility with the previous version or cluster upgrade process?
[x] Does the change support oldest and newest supported PS version?
[x] Does the change support oldest and newest supported Kubernetes version?

Test name
Status

version-service
skipped

async-ignore-annotations
skipped

auto-config
skipped

config
skipped

config-router
skipped

demand-backup
skipped

gr-demand-backup
skipped

gr-demand-backup-haproxy
skipped

gr-finalizer
skipped

gr-haproxy
skipped

gr-ignore-annotations
skipped

gr-init-deploy
skipped

gr-one-pod
skipped

gr-recreate
skipped

gr-scaling
skipped

gr-scheduled-backup
skipped

gr-security-context
skipped

gr-self-healing
skipped

gr-tls-cert-manager
skipped

gr-users
skipped

haproxy
skipped

init-deploy
skipped

limits
skipped

monitoring
skipped

one-pod
skipped

operator-self-healing
skipped

recreate
skipped

scaling
skipped

scheduled-backup
skipped

service-per-pod
skipped

sidecars
skipped

smart-update
skipped

tls-cert-manager
skipped

users
skipped

We run 0 out of 34

commit: https://github.com/percona/percona-server-mysql-operator/pull/726/commits/e6566579448ad08d10a60f6acf6690b6a7d6b4ef
image: perconalab/percona-server-mysql-operator:PR-726-e6566579

Test name
Status

version-service
failure

async-ignore-annotations
passed

auto-config
passed

config
passed

config-router
passed

demand-backup
passed

gr-demand-backup
passed

gr-demand-backup-haproxy
passed

gr-finalizer
passed

gr-haproxy
passed

gr-ignore-annotations
passed

gr-init-deploy
passed

gr-one-pod
passed

gr-recreate
passed

gr-scaling
passed

gr-scheduled-backup
passed

gr-security-context
passed

gr-self-healing
passed

gr-tls-cert-manager
passed

gr-users
passed

haproxy
passed

init-deploy
passed

limits
passed

monitoring
passed

one-pod
passed

operator-self-healing
passed

recreate
passed

scaling
passed

scheduled-backup
passed

service-per-pod
passed

sidecars
passed

smart-update
passed

tls-cert-manager
passed

users
passed

We run 34 out of 34

commit: https://github.com/percona/percona-server-mysql-operator/pull/726/commits/3fcf4e06d51d241d4aad26f4679219ac1fca62cc
image: perconalab/percona-server-mysql-operator:PR-726-3fcf4e06

Test name
Status

version-service
passed

async-ignore-annotations
passed

auto-config
passed

config
passed

config-router
passed

demand-backup
passed

gr-demand-backup
passed

gr-demand-backup-haproxy
passed

gr-finalizer
passed

gr-haproxy
passed

gr-ignore-annotations
passed

gr-init-deploy
passed

gr-one-pod
passed

gr-recreate
passed

gr-scaling
passed

gr-scheduled-backup
passed

gr-security-context
passed

gr-self-healing
passed

gr-tls-cert-manager
passed

gr-users
passed

haproxy
passed

init-deploy
passed

limits
passed

monitoring
passed

one-pod
passed

operator-self-healing
passed

recreate
passed

scaling
passed

scheduled-backup
passed

service-per-pod
passed

sidecars
passed

smart-update
passed

tls-cert-manager
passed

users
passed

We run 34 out of 34

commit: https://github.com/percona/percona-server-mysql-operator/pull/726/commits/3fcf4e06d51d241d4aad26f4679219ac1fca62cc
image: perconalab/percona-server-mysql-operator:PR-726-3fcf4e06

Test name
Status

version-service
failure

async-ignore-annotations
passed

auto-config
passed

config
passed

config-router
passed

demand-backup
passed

gr-demand-backup
passed

gr-demand-backup-haproxy
passed

gr-finalizer
passed

gr-haproxy
passed

gr-ignore-annotations
passed

gr-init-deploy
passed

gr-one-pod
passed

gr-recreate
passed

gr-scaling
passed

gr-scheduled-backup
passed

gr-security-context
passed

gr-self-healing
passed

gr-tls-cert-manager
passed

gr-users
passed

haproxy
passed

init-deploy
passed

limits
passed

monitoring
passed

one-pod
passed

operator-self-healing
passed

recreate
passed

scaling
passed

scheduled-backup
passed

service-per-pod
passed

sidecars
passed

smart-update
passed

tls-cert-manager
passed

users
passed

We run 34 out of 34

commit: https://github.com/percona/percona-server-mysql-operator/pull/726/commits/22d3d2d9c52a75291190b82b4ec2ed30e2b82969
image: perconalab/percona-server-mysql-operator:PR-726-22d3d2d9

Test name
Status

version-service
failure

async-ignore-annotations
passed

auto-config
passed

config
passed

config-router
passed

demand-backup
passed

gr-demand-backup
passed

gr-demand-backup-haproxy
passed

gr-finalizer
passed

gr-haproxy
passed

gr-ignore-annotations
passed

gr-init-deploy
passed

gr-one-pod
passed

gr-recreate
passed

gr-scaling
passed

gr-scheduled-backup
passed

gr-security-context
passed

gr-self-healing
passed

gr-tls-cert-manager
passed

gr-users
passed

haproxy
passed

init-deploy
passed

limits
passed

monitoring
passed

one-pod
passed

operator-self-healing
passed

recreate
passed

scaling
passed

scheduled-backup
passed

service-per-pod
passed

sidecars
passed

smart-update
passed

tls-cert-manager
passed

users
passed

We run 34 out of 34

commit: https://github.com/percona/percona-server-mysql-operator/pull/726/commits/11d1ad49932d164839df323f9b1e139060e83823
image: perconalab/percona-server-mysql-operator:PR-726-11d1ad49

Test name
Status

version-service
passed

async-ignore-annotations
passed

auto-config
passed

config
passed

config-router
passed

demand-backup
passed

gr-demand-backup
passed

gr-demand-backup-haproxy
passed

gr-finalizer
passed

gr-haproxy
passed

gr-ignore-annotations
passed

gr-init-deploy
passed

gr-one-pod
passed

gr-recreate
passed

gr-scaling
passed

gr-scheduled-backup
passed

gr-security-context
passed

gr-self-healing
passed

gr-tls-cert-manager
passed

gr-users
passed

haproxy
passed

init-deploy
passed

limits
passed

monitoring
passed

one-pod
passed

operator-self-healing
passed

recreate
passed

scaling
passed

scheduled-backup
passed

service-per-pod
passed

sidecars
passed

smart-update
passed

tls-cert-manager
passed

users
passed

We run 34 out of 34

commit: https://github.com/percona/percona-server-mysql-operator/pull/726/commits/11d1ad49932d164839df323f9b1e139060e83823
image: perconalab/percona-server-mysql-operator:PR-726-11d1ad49

Test name
Status

version-service
passed

async-ignore-annotations
passed

auto-config
passed

config
passed

config-router
passed

demand-backup
passed

gr-demand-backup
passed

gr-demand-backup-haproxy
passed

gr-finalizer
passed

gr-haproxy
passed

gr-ignore-annotations
passed

gr-init-deploy
passed

gr-one-pod
passed

gr-recreate
passed

gr-scaling
passed

gr-scheduled-backup
passed

gr-security-context
passed

gr-self-healing
failure

gr-tls-cert-manager
passed

gr-users
passed

haproxy
passed

init-deploy
passed

limits
passed

monitoring
passed

one-pod
passed

operator-self-healing
passed

recreate
passed

scaling
passed

scheduled-backup
passed

service-per-pod
passed

sidecars
passed

smart-update
passed

tls-cert-manager
passed

users
passed

We run 34 out of 34

commit: https://github.com/percona/percona-server-mysql-operator/pull/726/commits/e730d4f7013d11e8cf931801667b496504ebfabe
image: perconalab/percona-server-mysql-operator:PR-726-e730d4f7

Test name
Status

version-service
passed

async-ignore-annotations
passed

auto-config
passed

config
passed

config-router
passed

demand-backup
passed

gr-demand-backup
passed

gr-demand-backup-haproxy
passed

gr-finalizer
passed

gr-haproxy
passed

gr-ignore-annotations
passed

gr-init-deploy
passed

gr-one-pod
passed

gr-recreate
passed

gr-scaling
passed

gr-scheduled-backup
passed

gr-security-context
passed

gr-self-healing
passed

gr-tls-cert-manager
passed

gr-users
passed

haproxy
passed

init-deploy
passed

limits
passed

monitoring
passed

one-pod
passed

operator-self-healing
passed

recreate
passed

scaling
passed

scheduled-backup
passed

service-per-pod
passed

sidecars
passed

smart-update
passed

tls-cert-manager
passed

users
passed

We run 34 out of 34

commit: https://github.com/percona/percona-server-mysql-operator/pull/726/commits/e730d4f7013d11e8cf931801667b496504ebfabe
image: perconalab/percona-server-mysql-operator:PR-726-e730d4f7

Test name
Status

version-service
passed

async-ignore-annotations
passed

auto-config
passed

config
passed

config-router
passed

demand-backup
passed

gr-demand-backup
passed

gr-demand-backup-haproxy
passed

gr-finalizer
passed

gr-haproxy
passed

gr-ignore-annotations
passed

gr-init-deploy
passed

gr-one-pod
passed

gr-recreate
passed

gr-scaling
passed

gr-scheduled-backup
passed

gr-security-context
passed

gr-self-healing
passed

gr-tls-cert-manager
passed

gr-users
passed

haproxy
passed

init-deploy
passed

limits
passed

monitoring
passed

one-pod
passed

operator-self-healing
passed

recreate
passed

scaling
passed

scheduled-backup
passed

service-per-pod
passed

sidecars
passed

smart-update
passed

tls-cert-manager
passed

users
passed

We run 34 out of 34

commit: https://github.com/percona/percona-server-mysql-operator/pull/726/commits/8397b7e3067c48222fea9b9e7009377f2e31ace0
image: perconalab/percona-server-mysql-operator:PR-726-8397b7e3

Test name
Status

version-service
failure

async-ignore-annotations
passed

auto-config
passed

config
passed

config-router
passed

demand-backup
passed

gr-demand-backup
passed

gr-demand-backup-haproxy
passed

gr-finalizer
passed

gr-haproxy
failure

gr-ignore-annotations
passed

gr-init-deploy
passed

gr-one-pod
passed

gr-recreate
passed

gr-scaling
passed

gr-scheduled-backup
passed

gr-security-context
passed

gr-self-healing
failure

gr-tls-cert-manager
passed

gr-users
passed

haproxy
passed

init-deploy
passed

limits
passed

monitoring
passed

one-pod
passed

operator-self-healing
passed

recreate
passed

scaling
passed

scheduled-backup
failure

service-per-pod
passed

sidecars
passed

smart-update
passed

tls-cert-manager
passed

users
passed

We run 34 out of 34

commit: https://github.com/percona/percona-server-mysql-operator/pull/726/commits/6f9bcaa5e9815ae479c6a99631863cd1c247e987
image: perconalab/percona-server-mysql-operator:PR-726-6f9bcaa5

Test name
Status

version-service
failure

async-ignore-annotations
passed

auto-config
passed

config
passed

config-router
passed

demand-backup
passed

gr-demand-backup
passed

gr-demand-backup-haproxy
passed

gr-finalizer
passed

gr-haproxy
passed

gr-ignore-annotations
passed

gr-init-deploy
passed

gr-one-pod
passed

gr-recreate
passed

gr-scaling
passed

gr-scheduled-backup
passed

gr-security-context
passed

gr-self-healing
failure

gr-tls-cert-manager
passed

gr-users
passed

haproxy
passed

init-deploy
passed

limits
passed

monitoring
passed

one-pod
passed

operator-self-healing
passed

recreate
passed

scaling
passed

scheduled-backup
failure

service-per-pod
passed

sidecars
passed

smart-update
passed

tls-cert-manager
passed

users
passed

We run 34 out of 34

commit: https://github.com/percona/percona-server-mysql-operator/pull/726/commits/6f9bcaa5e9815ae479c6a99631863cd1c247e987
image: perconalab/percona-server-mysql-operator:PR-726-6f9bcaa5

Test name
Status

version-service
passed

async-ignore-annotations
passed

auto-config
passed

config
passed

config-router
passed

demand-backup
passed

gr-demand-backup
passed

gr-demand-backup-haproxy
passed

gr-finalizer
passed

gr-haproxy
passed

gr-ignore-annotations
passed

gr-init-deploy
passed

gr-one-pod
passed

gr-recreate
passed

gr-scaling
passed

gr-scheduled-backup
passed

gr-security-context
passed

gr-self-healing
passed

gr-tls-cert-manager
passed

gr-users
passed

haproxy
passed

init-deploy
passed

limits
passed

monitoring
passed

one-pod
passed

operator-self-healing
passed

recreate
passed

scaling
passed

scheduled-backup
passed

service-per-pod
passed

sidecars
passed

smart-update
passed

tls-cert-manager
passed

users
passed

We run 34 out of 34

commit: https://github.com/percona/percona-server-mysql-operator/pull/726/commits/6f9bcaa5e9815ae479c6a99631863cd1c247e987
image: perconalab/percona-server-mysql-operator:PR-726-6f9bcaa5


Disappearing Attachments

I was playing around with the attachment location plugin and now certain attachment images seem to have disappeared. I get a box where the attachment was. Any suggestions?

Can you create a new vault with the attachment location plugin only to help reproduce the bug?


stacker info fails with traceback

Using newly released stacker 1.0.3 (rev 60694300bc05c2c1).
$ stacker info env config.yml
Traceback (most recent call last):
  File "/home/danielkza/cobli/deploy/cloudformation/venv/bin/stacker", line 8, in <module>
    stacker.configure(args)
  File "/home/danielkza/cobli/deploy/cloudformation/venv/lib/python2.7/site-packages/stacker/commands/stacker/__init__.py", line 24, in configure
    super(Stacker, self).configure(options, **kwargs)
  File "/home/danielkza/cobli/deploy/cloudformation/venv/lib/python2.7/site-packages/stacker/commands/stacker/base.py", line 105, in configure
    tail=options.tail)
AttributeError: 'Namespace' object has no attribute 'tail'

Should be fixed in 1.0.4 (just released) - thanks @danielkza


Dependency on substack's node-buffers

Long-standing deprecation on Array.get has expired, node v6 no longer
supports this.
Upstream project has not yet merged #17, therefore we must fork and
change this project's dependency.

Coverage remained the same at 100.0% when pulling 8de9d91ee925a820a7f088c57ff8bd4832b8610e on kleetus:master into 7bb9afd416ee0033afd3a06bcc3afc151f27fc11 on bitpay:master.


Properly quote MySQL passwords

I don't think we'd have any issues, but I just wanted to make sure.

what does this even do, and why are passwords involved..

So, maintain_dump requires duplicating a database, and if the source database is on a different host, it's easiest to just use mysqldump and mysql to dump the source and create the local copy. Passing passwords on the command line is a bad idea, so I chose to use a (temporary) config file instead. The syntax is weird, so I didn't realize at first that you have to put double quotes around the password if there are weird characters in it (can't remember which characters, though). This pull request puts the double quotes in the config file so that any password (even one containing double quotes!) can be used.

This works even if the password contains '"'

wow


feat: Make eth_call gas limit configurable

Component
Anvil
Describe the feature you would like
Using a multicall contract to read a lot of data at once is a common use case. Anvil caps the gas limit of eth_call to the maximum gas limit of a block. I'm running into EVM error CallerGasLimitMoreThenBlock when trying to read lots of data from a multicall contract (> 100 calls)
Additional context
For any eth_call, set the gas limit to<PHONE_NUMBER>3709551615 (the maximum possible value)

there's the --gas-limit argument to set this to any value.
      --gas-limit <GAS_LIMIT>
          The block gas limit

I guess we could add an alias for max?

@mattsse this argument is very useful when calling evm_mine to create new block, I don't think the same limit should apply to eth_call

eth_call is executed without creating a transaction on the chain, and instead returns the result as it would if included in a block. So we don't want to return a success if the call would actually fail if mined.
but I'm not sure if the same applies to hardhat.
there's also anvil_setBlockGasLimit that you can use to set the block gaslimit an the fly.

anvil doesn't seem to respect the block gas limit for eth_call because setting the gas limit to<PHONE_NUMBER>3709551615 still results in CallerGasLimitMoreThenBlock (which has a misspelling by the way). This issue from a month ago reports the same bug and is also still open. Will this be fixed?

I think that setting the env var mentioned here will probably fix it. I'm not a rust dev though, so I'm not sure how to do this exactly. Can someone weigh in?

Same behaviour here. I made a mainnet fork using anvil and changed the gas limit to 100M, but when I cast call my contract's view function (contract which needed the --via-ir flag btw), I get the CallerGasLimitMoreThenBlock, error when I put a gas limit higher than 30M (which iirc is the original block gas limit)

I think that setting the env var mentioned here will probably fix it. I'm not a rust dev though, so I'm not sure how to do this exactly. Can someone weigh in?

@sewinter did you manage to resolve this? I'm having the same issue and not sure where to add the env var.

I get the CallerGasLimitMoreThenBlock error when I put a gas limit higher than 30M (which iirc is the original block gas limit)

can't reproduce this, sorry.
This issue is a bit difficult for me to understand, because:

block gas limit
call gas limit
are configurable

and CallerGasLimitMoreThanBlock is a constraint violation, so I'm actually not sure what the issue here is.
If you set the tx gas limit > block gas limit, it should fail even in eth_call, no?
that being set, I'll enable the optional_block_gas_limit feature and add a new flag.


How to install the software?

I installed the QDMS server installer
I have also installed mySQL
After setup of QDMS, theres a pop up which lets e test my connection to the SQL database. But after that nothing loads

Hello ??? any help is greatly appreciated?


Deprecated option optimize_cuda_cache warning on import of trl

When you just import trl, we get the following warning:
$ python3
Python 3.10.8 (main, Nov 24 2022, 14:13:03) [GCC 11.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import trl
/opt/conda/lib/python3.10/site-packages/trl/trainer/ppo_config.py:141: UserWarning: The `optimize_cuda_cache` arguement will be deprecated soon, please use `optimize_device_cache` instead.
  warnings.warn(

Unless this is left on purpose, I believe that this line https://github.com/huggingface/trl/blob/main/trl/trainer/ppo_config.py#L107, should be changed from:
optimize_cuda_cache: bool = False

to:
optimize_cuda_cache: Optional[bool] = None

to get rid of the warning.
I can open a PR if this warning is not needed on default config creation.

Indeed, that's correct! A PR would be great, thank you!


unable to get local issuer certificate

Hello,
I have the following issue:
? Would you like to run myst start now? Yes
🔍 Querying template metadata from https://api.mystmd.org/templates/site/myst/book-theme
request to https://api.mystmd.org/templates/site/myst/book-theme failed, reason: unable to get local issuer certificate
To list valid templates, try the command "myst templates list"
Myst CLI Versions:

node                         20.7.0     Required: >= 16.0.0
npm                          10.1.0     Required: >=7
myst                         1.1.16

I am not able to download the templates. Please help

Hi @ghostgrin thanks for reporting this!
I'm not able to reproduce either in node 16 or 20 - as it seems to be a certificate issue and that API is still accessible and seems to have a valid certificate. I wonder if it is transient? if you try again do you stil reproduce the error?

Closing this as we haven't been able to replicate. Feel free to reopen it if the issue continues to persist.


maintain / upgrade pineone-client to v3

Description
pinecone-client library was outdated and didn't support the serverless deploymeyments. upgraded the library  and applied the changes suggested here: https://canyon-quilt-082.notion.site/Pinecone-Python-SDK-v3-0-0-Migration-Guide-056d3897d7634bf7be399676a4757c7b#a21aff70b403416ba352fd30e300bce3

Related Issues
Solution and Design
Just maintaining the dependent libraray.
Test Plan
I have tested with Pinecone and it was okay. Since naming conventions applied to other vector databases it is also better to  check those before merging.
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Docs update
[x ]  Maintaining

Checklist

[ ] My pull request is atomic and focuses on a single change.
[ ] I have read the contributing guide and my code conforms to the guidelines.
[ ] I have documented my changes clearly and comprehensively.
[ ] I have added the required tests.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Functional tests fail due to XML serialization differences w/ CLR / x64

follow up to #1878.  looks like we have the XmlAssert capability to ignore XML serialization differences but are not using this in XmlOutputFormatterTests.
current failures with CLR runtime and x64 architecture (other combinations seem to work fine):
   Microsoft.AspNet.Mvc.FunctionalTests.XmlOutputFormatterTests.XmlSerializerOutputFormatterIsCalled [FAIL]
      Assert.Equal() Failure
                                    ↓ (pos 20)
      Expected: <DummyClass xmlns:xsi="http://www.w3.org/2001/XMLSchema-insta···
      Actual:   <DummyClass xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmln···
                                    ↑ (pos 20)
      Stack Trace:
         XmlOutputFormatterTests.cs(55,0): at Microsoft.AspNet.Mvc.FunctionalTests.XmlOutputFormatterTests.<XmlSerializerOutputFormatterIsCalled>d__4.MoveNext()
         --- End of stack trace from previous location where exception was thrown ---
            at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
            at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
         --- End of stack trace from previous location where exception was thrown ---
            at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
            at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
         --- End of stack trace from previous location where exception was thrown ---
            at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
            at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   Microsoft.AspNet.Mvc.FunctionalTests.XmlOutputFormatterTests.XmlSerializerOutputFormatter_WhenDerivedClassIsReturned [FAIL]
      Assert.Equal() Failure
                                    ↓ (pos 20)
      Expected: <DummyClass xmlns:xsi="http://www.w3.org/2001/XMLSchema-insta···
      Actual:   <DummyClass xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmln···
                                    ↑ (pos 20)
      Stack Trace:
         XmlOutputFormatterTests.cs(96,0): at Microsoft.AspNet.Mvc.FunctionalTests.XmlOutputFormatterTests.<XmlSerializerOutputFormatter_WhenDerivedClassIsReturned>d__6.MoveNext()
         --- End of stack trace from previous location where exception was thrown ---
            at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
            at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
         --- End of stack trace from previous location where exception was thrown ---
            at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
            at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
         --- End of stack trace from previous location where exception was thrown ---
            at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
            at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
Finished:    Microsoft.AspNet.Mvc.FunctionalTests

fixed in 689f5bf


Publish a GitHub release and attach ccm.phar on version-like tags

Closes #8
PS: for simplicity, #10 is included in this PR (so, you should first review it).
Here's how it works:

I pushed the tag 0.3.0-rc1 to https://github.com/mlocati/console, and create-release.yml started automatically and published the v0.3.0-rc1 pre-release
next I pushed the tag v0.3.0 to https://github.com/mlocati/console, and create-release.yml started automatically and published the v0.3.0 release

Please remark that the release notes are filled-in automatically (but in these examples they are not available because no changes were detected - I had no prior tags)

Very nice 👌

I've got a replacement that's almost ready, but we have to merge #12 before that


fix(mdjs-viewer): fix styling mdjs-viewer

What I did

Fix styling in darkmode
Make [slot="content"] selector more specific

thanks for the fix 🙇♂  and thx benny for reviewing it 🙇♂


Information regarding Charm++/OpenMP hybrid programs is lacking some details

Original author: Nicolas Bock
Original issue: https://charm.cs.illinois.edu/redmine/issues/278

I have added some text to Chapter 24 explaining a bit in more detail how hybrid Charm++/OpenMP programs need to be built and run.

Original author: Harshitha Menon
Original date: 2015-09-15 15:14:21

I looked at the patch. The patch makes updates to the ckloop section of charm++ manual to say that openmp can be used with Charm++ only in smp mode, which is not true. We can launch 1 charm process on one node and use openmp on other idle cores. But if there are no idle cores, then openmp thread may contend with charm PE.

Original date: 2015-10-27 21:48:33

~~https://charm.cs.illinois.edu/gerrit/884~~ https://github.com/UIUC-PPL/charm/commit/03e15b521cb54510e4fbf7c1b7133b48c5cf2d6e


Ceral with robin-map

Hi,
I'd like to use tsl::robin_map everywhere instead of the std maps, however I can't figure out how to serialize them with Cereal.  I saw your post about sparse_map but don't see the same serialize functions in robin - am I missing something?
Thanks for your help!

Hello,
Unfortunately it isn't yet implemented in robin-map. I have added it to my TODO list but it may take some time as I have some other things to work on beforehand.
Thibaut

Hi,
Sorry for the quite long delay. I started the implementation in the serialization branch. I still need to add some documentation before merging it to the master but everything should work.
Thibaut

awesome work! thanks for working on this and updating the thread!

I merged the changes, let me know if there is any problem.


ntr  increased pyknosis

wikepedia
Pyknosis, or karyopyknosis, is the irreversible condensation of chromatin in the nucleus of a cell undergoing necrosis or apoptosis.
PMID:18653539
Progressive pyknosis and karyorhexis in TAG-deficient mutants in rich medium
To better understand the cell-death process in TAG-deficient mutants, we sought simple yet reliable markers with which to monitor cell death. To this end, we observed progressive pyknosis (condensation of chromatin),.......
This was accompanied by chromatin condensation in the vast majority of the population, with some cells also showing nuclear- envelope breakdown (Fig. 1D). The chromatin condensation that was detected in DKO cells was readily distinguishable from that of the metaphasic chromosomes by its higher intensity and multi- focal nature (Fig. 1H), which is probably similar to that observed in another case, in which it is referred to as hypercondensation (Demeter et al., 1995).

Should probably add
"during stationary phase"

would be described as some sort of "apoptotic process"?

also Karyorhexis during stationary phase
Karyorrhexis (from Greek κάρυον karyon, "kernel, seed or nucleus", and ῥῆξις rhexis, "bursting") is the destructive fragmentation of the nucleus of a dying cell whereby its chromatin is distributed irregularly throughout the cytoplasm.
Upon reaching early stationary phase (6􏰀107-8􏰀107 cells/ml), extensive chromatin condensation and fragmentation ensued with the concomitant breakdown of the nuclear envelope into membrane- enclosed compartments (Fig. 1E). Advanced breakdown and rupture of the nuclear envelope and dispersion of the hypercondensed chromatin into the cytoplasm were generally observed when DKO cells had reached the saturation density (8􏰀107-10􏰀107 cells/ml, compare to the wild-type saturation density of >12􏰀107 cells/ml) for 24 hours or more (Fig. 1F). The nucleus of the wild-type cells remained intact throughout the above time frame (Fig. 1G).

increased pyknosis during stationary phase FYPO:0006275
increased karyorrhexis during stationary phase FYPO:0006276
edit file: 28e285e0e8631e06b6fcd3fc5bf7e23e770e0862
release: 6bcbf3d5135c0ce57ad9c75473590874a12a25e7


500 internal error when calling Azure OpenAI GPT4 with dspy

Hello all!
Currently experiencing 500 internal errors when using DSPY with Azure OpenAI gpt-4.
I have been using the Azure OpenAI client to ping a gpt-4 deployment, and am consistently getting: Internal service error 500.  I've also pinged using litellm for a manual prompting pipeline I've set up alongside it and have not seen any issues / errors returned. indicating it's not an Azure side issue - nor a ratelimit issue since I did them right back to back but not together.
I've checked that both dspy's azure openai client and my litellm pipeline correctly sends a message with keys 'role' and 'content'.. I can't seem to find the issue.
The signature and module setup I have is as follows:
class QuestionAnswerSignature(dspy.Signature):
    context: str = dspy.InputField()
    question: str = dspy.InputField()
    choices: list[str] = dspy.InputField(format=list)
    answer: QA_output = dspy.OutputField(desc="key-value pairs")

class QuestionAnswer(dspy.Module):
    def __init__(self):
        super().__init__()
        self.pick_answer = dspy.Predict(QuestionAnswerSignature)

    def forward(self, context, question, choices):

        output = self.pick_answer(
            context = context,
            question=question,
            choices=choices
        )

        # suggest that length should be less than 5 tokens
        dspy.Assert(len(output) < 100)

        return output

And the actual instantiation of the client I have is as shown below.
gpt_dspy = AzureOpenAI(
            model=model_name,
            api_base = gpt_client.api_base,
            api_version = gpt_client.api_version,
            api_key = gpt_client._get_token(),
            model_type = 'chat',
)
dspy.settings.configure(lm=gpt_dspy)

The request is sent correctly to the right address, as can be seen by the 500 + the logs also indicate the right URL is being used.
The only other thing I can think of is that either certain keyword arguments are missing (which I would assume would give a 400...) or that the prompt text generated by dspy somehow throws an error on the gpt side.
Is there currently known behavior of Azure openai GPT4 not working with DSPY?

You need to also provide deployment_id="your deployment name" in the instantiation of the client

@excubo-jg hey thanks for the response. I believe the 'model' parameter does that for me, mostly because deployment id is only used if model doesn't exist in the inputs or if I'm using openai version below 1?

Regardless I'll give it a shot and let you know!

@okhat Hi Omar. This issue is making me consider not adopting DSPY for some of my experiments... not sure if you believe I should open an issue on the Azure / OpenAI side, but currently all my other setups with Azure OpenAI have been working (with litellm) and I just wanted to flag that DSPY object for azure openai seems incompatible with Azure. Do you suggest we close this?

Well, I am running DSPy with Azure Open AI...

@excubo-jg could you share the version of openai you're using, as well as info on what parameters are you using? Also, which model type are you using?

@excubo-jg I also looked into the code and deployment_id is removed if "model" parameter is provided, which it is in my case. I'm  curious as to how you're getting it to work.

I'm curious as to how you're getting it to work.
https://github.com/stanfordnlp/dspy/issues/686#issuecomment-2021561999

@excubo-jg I've answered that point that "model" parameter works as a viable replacement for deployment_id( in fact deployment_id gets deleted from kwargs in the dspy.AzureOpenAI module when 'model' exists) What otehr parameters do you use, and what versions of openai library are you using?

Hi @dkimmunichre
I am currently testing dspy with an Azure setup.
After initial problems it works now fine for me.
Params:
"api_base"
"api_version"
"api_key"
"model"

Package-versions:
dspy-ai                   2.4.0
openai                    1.16.1

@franperic hey! Thank you for responding. What were your issues? I'm having no issues pinging... it just errors out for some reason with a 500. What method are you using for your api_key? AD credentials?

@excubo-jg I've answered that point that "model" parameter works as a viable replacement for deployment_id( in fact deployment_id gets deleted from kwargs in the dspy.AzureOpenAI module when 'model' exists) What otehr parameters do you use, and what versions of openai library are you using?

We do agree on the fact that I am running DSPy with Azure OpenAI and you are not, don't we?
And if I do not send the deployment_id, I don't have access to Azure OpenAI.
Which is to be expected. If you were to have a look here (you are using model_type = 'chat'): https://learn.microsoft.com/en-us/azure/ai-services/openai/reference#chat-completions

I am also attempting the same setup. The logic in this script shows that what happens with your input parameters get determined by whether you're using legacy openai version, or what parameters you pass. deployment_id in this case is the same as model, and is in fact replaced by "model" before being passed into the openai library. So no that's not the fix. I've also tried it and no change in error behavior was observed

If "model" or "deployment_id" were handled differently, my error wouldn't be a 500, but a 400 or the request wouldn't even return anything because the URL would be wrong.

In my set-up a value for model is sent and it is different from the deployment_id. Openai is 1.16.2 e.g. not legacy. Per your analysis this set-up cannot work but it does. The only difference between your initial post and my set-up I can see is that I am sending a deployment_id. I do not see a problem with DSPy here.

Let me see if I can get that replicate that setup. Even if somehow it works, I would say the statement "not see a problem with DSPy here" to be a bit strong if the "wrong setup" is the correct setup :D

At the very least there should be an update in the documentation or a more detailed guide to using Azure OpenAI object, which I'm willing to do once I figure this out.

Update: @excubo-jg I retried with deployment_id and it did not work. There must be other differences that allow your setup to work correctly but mine not.

Should be resolved in 2.5 if you migrate: https://github.com/stanfordnlp/dspy/blob/main/examples/migration.ipynb


Jagged lists for AgentData

Use Case
It would be nice if a user with custom data could provide jagged lists to AgentData instead of only numpy arrays, which cannot be jagged.
Acceptance Criteria
AgentData can be constructed with jagged lists instead of numpy arrays.

this script has some code that could be useful here


Provide a PowerShell example

Many Office 365 administrators aren't yet comfortable working directly with REST APIs. I suggest you update your instructions with a PowerShell based example, such as:
#requires -module Microsoft.Graph.Authentication

Connect-MgGraph -TenantId hsus.org -ContextScope Process -Scopes Policy.ReadWrite.AuthenticationMethod

$uri = "beta/authenticationMethodsPolicy/authenticationMethodConfigurations/MicrosoftAuthenticator"
$request = Invoke-MgGraphRequest -Uri $uri

#Display Current State:
$request.featureSettings.companionAppAllowedState.state

#Disable the feature
$request.featureSettings.companionAppAllowedState.state = "disabled"

Invoke-MgGraphRequest -Method PATCH -Uri $uri -Body $request

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

ID: 02a21275-1d7a-8ddf-6cb3-14f5352c79bb
Version Independent ID: 329dd91b-f4a3-7bd5-61ad-6f6de1a7a025
Content: How to enable Microsoft Authenticator Lite for Outlook mobile (preview) - Microsoft Entra
Content Source: articles/active-directory/authentication/how-to-mfa-authenticator-lite.md
Service: active-directory
Sub-service: authentication
GitHub Login: @sabina-smith
Microsoft Alias: justinha

Issue is moot due to this other doc bug
https://github.com/MicrosoftDocs/azure-docs/issues/107318

@Mike-Crowley
It looks like your issue is resolved since you closed this thread.
If there are further questions regarding this matter, please tag me in a comment. I will reopen it and we will gladly continue the discussion. Thanks!!!


[WIP] compose box: Rotate drafts in compose box.

The only thing left here is to add a test.
Testing plan:
GIFs or screenshots:
https://user-images.githubusercontent.com/63820270/121369763-c3d94300-c959-11eb-826e-94fde4528b4f.mov

In this push,

Solved the issue of showing multiple "Saved to Draft" tooltips.
Fixed the issue of compose box placeholder text was not updating.
Combine the rotate_draft_up_in_compose_box and rotate_draft_down_in_compose_box functions, as most of the code was similar.

In this push,

Update the function to only load draft if the compose state recipient matches the draft's recipient.
Cleaned up a code.

Not sure what I did wrong, but it's looking like this conflicts with #19046 . Trying to fix the merge conflicts now, TBD.

Not sure what I did wrong, but it's looking like this conflicts with #19046 . Trying to fix the merge conflicts now, TBD.

@aldeka, This is not possible because it is not merged yet unless you rebased your branch to this PR?

Oh, you're right. Not sure what the issue was, then, but I've got the merge sorted out on my side!


Can not add, edit, view, read on Tags

Users were able to read tags in version 3.0.0 but it is permission issues to read the tags in 3.0.1.
The big thing is even "admin" user is also not able to read it.
How to reproduce the bug

Go to Dashboards landing page
Click on edit button for any dashboard
Try to add a new tag
See error as shown in screenshot

Expected results
User should be able to read, add tags based on permission provided in a particular role.
Actual results
what actually happens.
Screenshots

Environment
Feature Flag
TAGGING_SYSTEM=True
Additional information
Roles do not have the permissions listed related to tags like read on Tags, delete on Tags, add on Tags, edit on Tags which was actually present earlier in 3.0.0

Hi @pankajsoni22. Tags were not officially released yet. You can check https://www.youtube.com/watch?v=tWmDlSbNeQA for more information about the feature development. What's in 3.0.1 is only a partially developed feature behind a feature flag.
Tags will be available in 3.1.

Hi @pankajsoni22. Tags were not officially released yet. You can check https://www.youtube.com/watch?v=tWmDlSbNeQA for more information about the feature development. What's in 3.0.1 is only a partially developed feature behind a feature flag.
Tags will be available in 3.1.
@michael-s-molina Thanks for response but if this is not released yet, why it is working in 3.0.0, The release video on youtube also includes TAGGING_SYSTEM in the discussion. Also check the feature changelog of 3.0.0 that also says it is involved.

@pankajsoni22 Maybe your specific use case was working on 3.0.0 but the feature was half completed and behind a feature flag. If you compare what's currently on master you'll see that the tags in 3.0.0 contain many bugs and poor UX. Since 3.0.0 many PRs were merged to finish the feature, which is not finished yet as you can see by the presentation link that I shared.


[Extensions] Bug log42j overriding

Description
Fix to bug
824
Steps to fix
https://github.com/opensearch-project/opensearch-sdk-java/issues/824#issuecomment-1636226463
Issues Resolved
List any issues this PR will resolve, e.g. Closes [...].
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

The change is failing the integ test though:
 org.opensearch.sdk.sample.helloworld.rest.TestHelloWorldIT > testInitializeExtension FAILED
    java.lang.NoClassDefFoundError: org/slf4j/LoggerFactory

The change is failing the integ test though. You can remove the logger from IT test

That logger is log4j.  The problem is in the next line in the stack trace:
org.opensearch.sdk.sample.helloworld.rest.TestHelloWorldIT > testInitializeExtension FAILED
    java.lang.NoClassDefFoundError: org/slf4j/LoggerFactory
        at org.apache.hc.client5.http.ssl.AbstractClientTlsStrategy.<clinit>(AbstractClientTlsStrategy.java:64)

We are forced to import SLF4J logger here: https://hc.apache.org/httpcomponents-client-5.1.x/current/httpclient5/xref/org/apache/hc/client5/http/ssl/AbstractClientTlsStrategy.html#L64
We are forced to import LOG4J2 logger here:  https://github.com/opensearch-project/OpenSearch/blob/675acdb4b92d862ccec3ebd10f390f333d81291f/server/src/main/java/org/opensearch/common/settings/Settings.java#L857
We can therefore not exclude either API dependency from SDK without either:

removing any usage of the Settings class, or
removing any usage of Apache Client SSL classes

My original concern of forcing debug logging is resolved by moving the config file.
Downstream users end up with two logging APIs but they can at least configure them and sort it out themselves.


on_publish 3xx redirect using HLS doesn't change the name of the segments or directory name BUG

If you run a Livestream type site and allow users to stream by giving them a pubkey to stream you need a mechanism to protect the pubkey during playback or else anybody will be able to stream.
Example:
STREAMING USER: streams with below
rtmp://example.com/live   pubkey: 382hki8
file names become 382hki8-(n).ts under /tmp/hls
but.. if I return a different stream name 98ke8i it still doesn't change the name of the file names

You can try passing token as query paramter, so user will stream to example.com/live/user?token=382hki8 and fragments generated should be named user-(n).ts. on_publish will get that query parameter, so you can still authorize users.

You need to redirect to a different stream name in your on_publish endpoint.
Example:
Streamer streams to: `rtmp://example.com:1935/app/
on_publish endpoint: /stream/on_publish
Should return a redirect header:
Location: foo

HLS files are now accessible under foo, not <secret>.

there is a bug with HLS, it doesn't create a new folder/file.ts with new redirect name

This is happening still, though @misiek08's solution worked brilliantly.  I wouldn't use that in a production service, though!

@techkid6 that's the easiest and production ready solution - just rotate tokens of you have paid service.
Dynamic channel names works great too and the code to handle it is almost exactly the same.


VT52 waiting for valid escape sequence

Hi,
First of all, I'm very pleased to see that VT52 was turned into a loadable driver. Very nice!
The question was asked how to print escape from Altirra BASIC. That can be done with chr$(). For example:
? chr$(27);"H";chr$(27);"J"

To home the cursor and clear screen.
I noticed that when an invalid escape sequence is encountered, it keeps waiting for a valid one. ? chr$(27) <enter> and nothing gets echoed to the screen anymore (but Altirra's input routine does receive the characters). After typing H it "escapes" from that state and everything turns to normal again.
@davidgiven How does one exit atbasic? I can't get out of it! :)

Thank you for reporting this.
I missed to handle the invalid escape sequence case in the driver code, I will fix this and submit a pull request.


Remove ign-tools from CMakeLists.txt. Not used

🦟 Bug fix
Summary
Code is looking for ign-tools while I can not find any place where it is used.
Checklist
Note to maintainers: Remember to use Squash-Merge

That line was added in https://github.com/ignitionrobotics/ign-plugin/pull/32/files, and it seems that it was used at least in https://github.com/ignitionrobotics/ign-plugin/blob/ign-plugin1/loader/CMakeLists.txt#L7 to decide if to include src/ign_TEST.cc in the compiled tests.

That line was added in https://github.com/ignitionrobotics/ign-plugin/pull/32/files, and it seems that it was used at least in https://github.com/ignitionrobotics/ign-plugin/blob/ign-plugin1/loader/CMakeLists.txt#L7 to decide if to include src/ign_TEST.cc in the compiled tests.

see https://github.com/ignitionrobotics/ign-plugin/pull/57


Update Dutch translation

Related to https://github.com/newsboat/newsboat/pull/1762

Coverage remained the same at 59.277% when pulling e17aa93fc8e7f76e08267926c08f71dd47f6c1ff on dennisschagt:Feature/nl-translation-update into b62e131e44a885d028db5a4fc5a263f3e456e875 on newsboat:master.

Looks good to me too, thanks @dennisschagt!


[WIP] Add linux target

Hello,
This is a WIP, but I'm submitting it because I need some feedback:

a linux version of the example-app would help test the created packages
I'm not satisfied with the conf handling, and I would like some inputs/opinions about what's important
I need to handle icons

I'll add commits to this PR according to your advices.
Regards

Heyo - I'll have a look at it tomorrow. But so far it's looking really promising. :+1:

So I had a quick look.

a linux version of the example-app would help test the created packages

Do you want me to provide an app? I simply checked this one in https://github.com/stefanjudis/blocky packed for given platform. Can you provide with it if you wish. :bowtie:

I'm not satisfied with the conf handling, and I would like some inputs/opinions about what's important

I'm not sure I understand that one.... We have on the roadmap to improve config handling in general by providing default values - is this what you mean?
Overall.... Thanks a lot for doing this. I really appreciate it.
If I can help you with anything - I'm glad to support.
And sorry upfront that it might take a day or two ( feel always free to ping me when I'm lacking response ). :)

Hello @stefanjudis,
About the example app, I'll handle myself since I now know which one it is.
About the conf handling, I mean that I would like to have other pple feedback to know what they would like to see here.  But providing a first set of options would be OK. It would be easy to add more later.
But in a more general perspective, I feel that relying on package.json for stuff such as name and version would be nice to keep stuff aligned.
Finally, I'll include your comments in the next commit, and I'll double check the issue I have with tests.
Best regards,
Xavier

@xseignard

But in a more general perspective, I feel that relying on package.json for stuff such as name and version would be nice to keep stuff aligned.

Will be tackled in an issues by its own. :)
What's the current state here? ready for a final check round and CR?

Hello the current state is that .deb works, I hadn't the chance to test for .rpm.
I agree that relying on package.json is an issue on its own.
Before merging, I would love to have at least one feedback about the produced .deb, e.g. does it meet the expectations you have for a .deb?
Regards

Before merging, I would love to have at least one feedback about the produced .deb, e.g. does it meet the expectations you have for a .deb?

Puuh - I'm not sure I can help with that as I'm total noob in linux land... So I'd trust you completely. ;)
But I can check with some linux folks I know if you wish.

I'm not an expert too, but since the backbone of the functionality is done, it's now only a matter of configuring it. So if one of your linux folk can have a look, we could provide better .debs.
Regards

This comes at a good time since I'm looking at how to package up an app for Linux. How would I go about testing this? Or how else could I help get this to a release? I could confirm if a deb works.

@jronallo Great!!!
I think if we would have an additional ( your ) opinion we can push it out. :bowtie:
How to test:

check out the project and check out the code of this open PR
go into project
run npm i
run npm link -> now you should have the electron-builder executable available in your environment
test it by building a linux app

If you have any questions let me know. :)

@stefanjudis Created a deb, installed it, and the app worked fine. Looking forward to this being merged!
I can't tell you whether this is a very good deb as I'm not very familiar with packaging, but I'll say that it works. Yes, the window icon doesn't show up, but this is  good start and I'd certainly rather this get merged and released and then get the icon issue and anything else worked out.
@xseignard Thank you very much!

@jronallo
Okay agree. :)
I'll prepare a release tomorrow then.
Thanks for having a look. :bowtie:

Hello @stefanjudis and @jronallo
Great to hear! The .deb creation works, but need improvements. This could be merged and be improved over the time.
I'll try to find some time to tackle the icon issue. And the rpm packaging.
Regards


Always sectors missing, when reading 5,25" IBM disks

Hello keirf, i am quite new with your great hardware. Trying to read my old IBM DOS 5,25" Floppy disks. From 10 disks i was able to read only 1 without any problems. the others shows me always, that sectors are missing...
maybe i do something wrong, ore all my disks are all broken?

  Turns out the 3½″ drive I salvaged was dusty.

Another possibility is density select on floppy pin 2 eg gw pin set 2 L

Thanks for the answers guys. Already purchased a cleaning disk on ebay.
@keirf My Floppy is Mitsumi D509V2.

Can i change the density with correct Jumper settings ?

I don't know but usually the drive is told the density by the host, via signalling on pin 2. Also the HD drive usually spins at 360rpm regardless of density (DD media is notionally accessed at 300rpm) but FlashFloppy should automatically fix that up these days.
Hence the suggestion to set pin 2 Low via gw pin set 2 L. And then retry your read.

gw pin set 2 L unfortunately = the same result. Looks like the drive head is really dirty :(

You can also try adding --rpm 300 to the gw read command line.

--rpm 300 is not recognized as command unfortunately, also rpm=300 is not recognized....hm..

Sorry the parameter now is --adjust-speed 300

I see that early on you say the one disk at least did read correctly. Does it still read correctly? As well as being themselves unreadable, really dirty disks can also dirty or even damage your drive heads.

I see that early on you say the one disk at least did read correctly. Does it still read correctly? As well as being themselves unreadable, really dirty disks can also dirty or even damage your drive heads.

I was able to read a disk with a very odd format. It was 5,25" disk with 720KB. (really odd), but i could read it correctly. afterwards i tried multiple times to read the same and other disks - always with the same error.
So i think, the drive is dirty or bad. Need to find another 5,25 Floppy to test with them
Thank you @keirf for your help!


back to py2

Hi,
I would need to have Prince working with python2. too bad ...
I saw that the @ operator is not supported in py2. like in ca.py
data=X @ sparse.diags(self.row_masses_ ** -0.5) @ self.U_
I am not familiar with that @.
Is it possible to rewrite it using np.matmul?
Like
data=np.matmul(np.matmul(X, sparse.diags(self.row_masses_ ** -0.5)), self.U_)
I looked into going back to an old version, but I am using it also in py3, and like the way it works now.

Sorry but Python 2 won't be supported.


这个跟直接调用官方api有什么区别嘛 ，另外报错超时443是怎么回事？

Describe the feature
这个跟直接调用官方api有什么区别嘛 ，另外报错超时443是怎么回事

帮你维护聊天记录，官方的要你自己每次发送整个聊天记录。

This project is undergoing a major revamp; closing out old issues as part of the prep process.
The chatgpt package is pretty outdated at this point. I recommend that you use the openai package or the openai-fetch package instead.


Handle exceptions gracefully

Description
Currently if an error occurs in an external call to the watcher or the root chain omg-js does not handle the exception but crashes with a stack trace.
Suggested solution
Handle errors gracefully and return them to the user. Especially calls to external systems should be handled and it should be clear to the user where they happen. For example the following request crashes during start SE.
(node:95381) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'transactionHash' of undefined
    at main (/Users/gerhard/research/omg-js-cli/src/index.js:104:63)
(node:95381) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 10)
(node:95381) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
Revert reason: Exit has already started
(node:95381) UnhandledPromiseRejectionWarning: Error: Transaction has been reverted by the EVM:
{
  "blockHash": "0x5927df319f217f464a2a9aa32103152de1629410a829c3c8a8eb03a71d8a8377",
  "blockNumber": 5511883,
  "contractAddress": null,
  "cumulativeGasUsed": 567802,
  "from": "0xd42b31665b93c128541c8b89a0e545afb08b7dd8",
  "gasUsed": 125848,
  "logs": [],
  "logsBloom": "0x00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000",
  "status": false,
  "to": "0x0822cf5de60c5a4b1925a05057e06002e1359fa2",
  "transactionHash": "0x9fa70ad4f479a90d5483028e0750e6e30b80616f9193a2f0fc4cbf4a121c5cbc",
  "transactionIndex": 7
}
    at /Users/gerhard/research/omg-js-cli/node_modules/web3-core-method/src/index.js:412:37
    at process._tickCallback (internal/process/next_tick.js:68:7)
(node:95381) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 11)

Instead of printing a stack trace omg-js could return an error object. Something like this:
{
   "succes": "false",
   "backend": "Root chain",
   "function": "startStandardExit(),
   "message": " Exit has already started"
}

I'd concur.
Specifically, when polling for a transaction that has been generated but not been mined yet, "throw" isn't a great response.
    childChain.getTransaction(tx)       .then((trans) => {         resolve(trans)       })       .catch((e) => {         reject("Loggedy Schmoggedy"); // log pollution       })
Further, the solution presented in
omg-js/packages/omg-js-util/src/waitForChildchainBalance.js
seems contrived and not scalable for an account that will receive lots of transactions.

Thinking about this recently I disagree with this approach. omg-js is a promise based library and should embrace that construct as it's natural to the language. A promise rejection signaling a failed outcome is the same as having to check a success boolean. IMO a rejected promise feels more natural to the language. Whether the client has to check for this flag or catch the promise rejection, the handling of the response is still necessary and doesn't make the developer experience any better. Also, since library calls are permanently promises, having to handle unexpected promise rejections and handle a response object feels very awkward to me.
ie.
const result = await omgjs.startStandardExit() // promise still needs to be handled if the client is defensive
if (result.success) {
  // handle success
}
if (!result.success) {
  // handle failure
}

vs.
const result = await omgjs.startStandardExit().catch(e => {
  // handle failure
})

// handle success

in both cases, if the client does not handle the response gracefully then the application will crash, also illustrated in the example of the issue.
This is like returning a REST 200 with a success: false. I feel that embracing the construct is more natural.
@snowkidind  whether getTransaction should return null instead of a rejection is a valid but separate issue I think.


ConcurrentBag-like data structure for parallel appends

I'm writing an @njit(parallel=True) decorated function which runs a prange loop. The intent was to define a data structure outside the loop, and append to it from within, like so:
@njit(parallel=True)
def parallel_append():
    thing_to_append_to = ConcurrentBag()
    for i in prange(100):
        thing_to_append_to.append(i)

The order of insertion is unimportant; naturally, it cannot be guaranteed anyway. Unfortunately, replacing the imaginary ConcurrentBag() with a TypedList, set or any other data structure seems to return:
Process finished with exit code 134 (interrupted by signal 6: SIGABRT)

Or similar SIG* errors. Presumably because it's not thread safe. A concurrent bag-like data structure would be super helpful because it is not always efficient to preallocate a NumPy array (In my case, the expected number of appends are orders of magnitude less than the maximum number). Not only that, but one can append namedtuples and other useful structures to a list, while NumPy arrays are limited to primitives for now.

For anyone looking to do something similar in the mean time: chunking manually followed by np.prange works reasonably well. Instead of a list, use a dynamically growing array (like a C++ std::vector), as long as your data is something that can be stored easily in a basic numpy array.
Something like:
import numpy as np
import numba

@numba.njit(inline="always")
def grow(array: np.ndarray) -> np.ndarray:
    """Double storage capacity."""
    n = len(array)
    new_shape = (2 * n,) + array.shape[1:]
    new = np.empty(new_shape, dtype=array.dtype)
    new[:n] = array[:]
    return new

@numba.njit(inline="always")
def push(array, value, size):
    if size >= len(array):
        array = grow(array)
    array[size] = value
    return array, size + 1

@numba.njit(inline="always")
def pop(array, size):
    return array[size - 1], size - 1

@numba.njit
def f(out: np.ndarray, size: int):
    """Randomly "appends" between 0 and 10 values"""
    n_return =  np.random.choice(10, 1)[0]
    for _ in range(n_return):
        out, size = push(out, 1, size)
    return out, size

@numba.njit
def f_helper(input_array: np.ndarray):
     # initialize with capacity 2
     out = np.empty(2, dtype=np.int32)
     size = 0
     for item in input_array:
          out, size = f(out, size)
     return out, size

@numba.njit
def concat(out: list[np.ndarray], sizes: np.ndarray) -> np.ndarray:
    """numba is also unhappy with numpy.concatenate."""
    total_size = sum(sizes)
    merged = np.empty(total_size, dtype=np.int32)
    start = 0
    for part, size in zip(out, sizes):
        end = start + size
        merged[start: end] = part[:size]
        start = end
    return merged

@numba.njit
def f_parallel(input_array: np.ndarray, n_chunks: int):
     chunks = np.array_split(input_array, n_chunks)
     out = [np.empty(0, dtype=np.int32) for _ in range(n_chunks)]
     sizes = np.empty(n_chunks, dtype=np.int32)
     for i in numba.prange(n_chunks):
          out[i], sizes[i] = f_helper(chunks[i])
     return concat(out, sizes)

In my case, I was better off at only resizing the array outside of my particular f and retrying f, so a little trial and error benchmarking might be worthwhile.


Bi-di bindings: missing operation fix

This PR assigns the operation from the user request to the bindings function.

/ok-to-test


don't show an enter button for own giveaways

Is your enhancement request related to a problem? Please describe.
Currently the enter button is also there for own giveaways e.g. when you create a giveaway on the confirmation page or on your own profile page. Of course the button don't work there since you cannot enter your own giveaways.
Describe the solution you'd like.
Don't show an enter button for giveaways you've created.

I simply filter giveaways created by myself from all the listings using Created - false. That also does the trick.

Probably a bug, it used to do this.

Hi, is this still an issue?

yes

Weird, I don't have it.

Maybe my settings help you to reproduce the bug:
esgst_settings.zip
Have you tried making a giveaway for a game you could enter if you see it on a user page? If it is already on the filtered list, you already own the/won the game, level is too high or region restriction prevents you from entering there's no enter button. Also for invite only there's no enter button but for public and group giveaways. Starting time needs to be now to see the enter button directly on the confirmation page.


[vendor] (DO NOT MERGE) Bring XKCP (of Keccak.team) for KMAC vector generation

Please do not merge yet (pending licensing confirmation).
I'm trying to vendor-in a library so that I can generate varying-size SHAKE/cSHAKE/KMAC vectors. cSHAKE and KMAC vectors are especially hard to come by, so having this library will be handy. This is also one of the items on the list #16410.
I also thought about adding these to wycheproof, but I am not sure if they are too active (last commit on 2019, and there are pending PRs from 2020.).
Few questions:

I couldn't make util/vendor.py accept both mapping and global patch_dir at the same time. So, after vendoring, I had to patch it manually:

./util/vendor.py sw/vendor/xkcp.vendor.hjson -v
git apply --directory sw/vendor/xkcp -p1 sw/vendor/patches/xkcp/add_example_build.patch

Is the target dir sw/vendor correct for vendoring?
Is it OK to keep the original Makefile-based build files? Do we need to migrate this to bazel?

Yes, agreed with @alphan. Here is an example how to vendor in FreeRTOS with Bazel (instead of the vendor tool). It applies patches to the Bazel-vendored-in code too.

Thanks @alphan, I will close this and try to vendor it with bazel. And thanks @timothytrippel for the example, that will indeed be useful.


HV-1064 Add Travis support

I added a comment to HV-1064 itself. I am kind of wondering what we gain here.

Anything missing from this? I think it's good to go, right?

I think we wanted to add some more info into the README

I added something along the lines of what we discussed to the README.md.

Rebased and applied. Thanks, @gsmet!


Cycled RLO objects with cause RCascadeType.PERSIST infinite loop and stuck

Is your feature request related to a problem? Please describe.
I have about 100,000 redis object should be persist into Redis.
And they are of several data types. each data type will associate with others.
In other word, they form a cycle.
If I use RCascadeType.PERSIST, the program will stuck. Because it is gone into an infinite loop.
Describe the solution you'd like

regisiter rlo class method should record all the classes that user need to persist
add a new method to calculate the class's adjacencyArrays.
persist vertex classes
construct relationships according to adjacencyArrays.

Describe alternatives you've considered

@mrniko  I have submit my PR, pls review it, thanks

sorry, the PR fail to pass style check , I will cancel it and submit latter.

this is the PR.
But it fail to pass github auto build due to timeout error, I think the error is nothing deal with my code.
I don't know how to trigger auto build again, maybe your can trigger it.
I copy the github build error here:
Transfer failed for https://repo.maven.apache.org/maven2/org/hibernate/hibernate-testing/5.4.5.Final/hibernate-testing-5.4.5.Final.jar 503 Backend unavailable, connection timeout


[Android][UnsatisfiedLinkError] [dlopen failed for libadaptivecards-native-lib.so file]

Platform
What platform is your issue or question related to? (Delete other platforms).

Android

Author or host
Microsoft Teams
Version of SDK
Adaptive card sdk version 2.2.0
Details
Upgrading to the adaptive card sdk version from 2.1.0 to 2.2.0 is leading to this issue. When a call is made to the adaptive card native library there is an error which says failed to dlopen the libadaptivecards-native-lib.so file and the app crashes.
The error observed is as below:
java.lang.UnsatisfiedLinkError: dlopen failed: cannot locate symbol "_Unwind_Resume" referenced by "/data/app/com.microsoft.skype.teams.dev-GgORJFzm38OEBdFRaSYDzQ==/lib/arm64/libadaptivecards-native-lib.so"...
This error is NOT observed while upgrading to 2.1.0 and something which has been introduced with 2.2.0.
Additional Info: Teams uses the adaptive card sdk by downloading the maven package through maven feeds and artifacts offered by azure devops.

@shalinijoshi19 Please help with this one.

@almedina-ms I've gone ahead and assigned this over to you. Please take a look with high priority ! thanks

Unable to repro on our end using a sample project while consuming the adaptivecards-android library from maven. Tested both 2.1.0 and 2.2.0, neither of which presented this error for us.


[New App] FileDrop (app req #109)

let me know if i can make a fix :)

linked to this app req : https://github.com/IceWhaleTech/CasaOS-AppStore/issues/109#event-10291705674

@raller1028

@Noe-Favier Sorry for validating your pull request so late, this app is so cool, thanks for submitting!


Check for blank session token

Not sure how to tell whether this is the real cause or how to test it.
@mmaxim

@patrickxb Is there a better error we should be throwing in this case?

hmm, you could make more checks in the LocalSession block.
if s.IsLoggedIn() { token = ...; uid = ... }
then once you get out if token is empty you could return LoginRequiredError?
But I'm not sure what you're trying to fix exactly.

Goal is to stop all the authentication requests to Gregor with blank session tokens.

I thought since we had all the logged in checks for trying to connect to Gregor that we would never make it this far.

yeah, I'm confused how it could be empty.

I'm not sure this ever does happen. My thinking was that if this doesn't hurt, and we deploy it, then we'll know a bit more based on whether the blanks disappear from the gregor logs.
Only other idea I've thought of is to get the IPs of the offending requests and figure which users they are and see if there happen to be log sends. Seems hard.

Ok, in that case use whatever error you'd like to that will be easy to find in the log.

Can we have the text be like "blank session would have been sent to gregor" or something?

sure, done