Choose defaultDate without setting Value

It would be great if there was an option to set the default date that the calender opens up on so that it doesn't start today, without changing the HTML value with the current defaultDate option.
My use case - setting a date of birth. I know that no users are allowed to be less than 13 so I can set the maxDate to 13 years ago, then to change where my pop-up starts, I set the defaultDate to 13 years ago, however this sets the HTML value to the date 13 years ago and thus overrides my "placeholder" text which reads "Date of birth"

there's a workaround for this 'bug', if anyone interested:
you can set the datetimepicker with it's set() function, and then set the bound element back to its original value. thus, you'll have the picker opening up with the wished datetime.
if you modify the enabled/disabled dates, redo this procedure.

if I add a check for a placeholder value on the input field does that solve all of your issues?

you mean data-placeholder=""? I think yes.

I mean if you did <input type="text" class="form-control" placeholder="put a date here"/>

The issue for me is that if I require this field then if a user simply clicks on the datetimepicker button by mistake then I don't want it to populate the input unless they actually pick a date.  Meaning they actually haven't chosen a date. That way I can leave the input readonly or disabled.

what would be the point of setting the defaultDate at that point?
You can use useCurrent:false to not auto populate the input

I believe this was version 3 and I was looking for functionality similar to conorot where it would default the selection to that date but not populate the input unless it chosen.  I'm really after a way so that when the user clicks the calendar it doesn't just through a date in there until a date is picked. But might have a way of picking the default day the calendar opens up on.

perhaps an new feature of defaultViewDate or something similar would be better. To me, your goal changes the functionality of defaultDate

That would make sense but I'm really after a better way to force the user to use the datetimepicker button and not set a date until one is chosen.  That way I can keep the input as readonly and not have to worry about a user clicking a button and populating the input when they didn't want to.  Perhaps I should have made a separate issue.

the placeholder check is go into dev in a little bit.
You can make a separate issue. The defaultViewDate option would change the picker's view to whatever was passed in without actually setting the date

Please check the dev branch. Should be a fix in there for you. Assuming no other major issue with the dev branch come up this week, dev will be promoted to master March 7th.
@iancmuir your feature request will go into the next release. I don't want to make any more feature changes so that dev can settle for a bit.

How to make datetimepicker textbox as readonly. I just want to enter date while selecting in calendar only. I dont want the manual entry. How to do this?

@ssathishkumar540 please see the ignorereadonly function.


prompt keeps spitting out additional information?

I'm not sure what's happening but zsh keeps printing out what it's doing everytime I run a command and it's really distracting.
Any ideas?
The closest guess I can come up with is a variable that my shell might be overwriting that breaks this.
➜  ~
+omz_termsupport_precmd:1> emulate -L zsh
+omz_termsupport_precmd:3> [[ '' == true ]]
+omz_termsupport_precmd:7> title '%15<..<%~%<<' '%n@%m: %~'
+title:1> emulate -L zsh
+title:2> setopt prompt_subst
+title:4> [[ '' == *term* ]]
+title:8> : '%n@%m: %~'
+title:10> case xterm-256color (cygwin|xterm*|putty*|rxvt*|ansi)
+title:12> print -Pn '\e]2;%n@%m:\ %~\a'
+title:13> print -Pn '\e]1;%15\<..\<%~%\<\<\a'
+zsh:6> git_prompt_info
+git_prompt_info:1> local ref
+git_prompt_info:2> [[+git_prompt_info:2> [[ '' != 1 ]]
+git_prompt_info:3> ref=+git_prompt_info:3> ref=''
+git_prompt_info:4> ref=+git_prompt_info:4> ref=''
+git_prompt_info:4> return 0
➜  ~
+omz_termsupport_precmd:1> emulate -L zsh
+omz_termsupport_precmd:3> [[ '' == true ]]
+omz_termsupport_precmd:7> title '%15<..<%~%<<' '%n@%m: %~'
+title:1> emulate -L zsh
+title:2> setopt prompt_subst
+title:4> [[ '' == *term* ]]
+title:8> : '%n@%m: %~'
+title:10> case xterm-256color (cygwin|xterm*|putty*|rxvt*|ansi)
+title:12> print -Pn '\e]2;%n@%m:\ %~\a'
+title:13> print -Pn '\e]1;%15\<..\<%~%\<\<\a'
+zsh:7> git_prompt_info
+git_prompt_info:1> local ref
+git_prompt_info:2> [[+git_prompt_info:2> [[ '' != 1 ]]
+git_prompt_info:3> ref=+git_prompt_info:3> ref=''
+git_prompt_info:4> ref=+git_prompt_info:4> ref=''
+git_prompt_info:4> return 0
➜  ~

This happened to me also but I can confirm that only when I run a bash script that does set -x and that returns error.
This means that the verbose mode affects the execution of git_prompt_info scripts, making them verbose too, which is clearly not desired.
I am not sure how to avoid this and the fact that I observed this only recently, I assume some kind of regression happened recently.

same issue here. It has something to do with the function omz_termsupport_preexec in the termsupport.zsh file. If you set the variable DISABLE_AUTO_TITLE = true in your .zshrc file, the problem goes away. Also, the problem does not exist if you start TMUX.

When you enable tracing mode that's what you get. If you haven't enabled it yourself (by running set -x, setopt xtrace or similar), then there is some other place in your config that does that.
To disable it, run set +x or unsetopt xtrace.

By the way, this happens with other set directives as well. Be careful to avoid using set -x, -e, -u, or -f in shell configuration scripts.


isBlank snippet is wrong

Looks like the following snippet has wrong content: https://github.com/dirajkumar/sublime-apex-snippets/blob/master/snippets/isBlank.sublime-snippet
Please take a look.

Good catch! Fixed


Border radius not working

Ask your Question

Could you provide some more information? Version, platform etc?
Im not at my desk at the moment but you may need to wrap the modal inside of an empty view and set the border radius there. Let me know if that works for you.

I've added a borderRadius to the modal and to its child <ScrollView>.
as you scroll, the border becomes squared and seems like only the top and end of the <ScrollView> shows the border radius but not as you scroll.
Also how can I change the backgroundColor of the modal? The empty dark transparent space behind the modal is what I mean
<Modal
  style={styles.modalStyle}
  isVisible={true}
  scrollHorizontal={true}
  propagateSwipe={true}
>
  <ScrollView
    contentContainerStyle={styles.scrollViewStyle}
    showsVerticalScrollIndicator={false}
  >
    <View>
      <Text>text</Text>
      <Text>text</Text>
      <Text>text</Text>
      <Text>text</Text>
      <Text>text</Text>
      <Text>text</Text>
      <Text>text</Text>
      <Text>text</Text>
      <Text>text</Text>
      <Text>text</Text>
      <Text>text</Text>
      <Text>text</Text>
      <Text>text</Text>
      <Text>text</Text>
      <Text>text</Text>
      <Text>text</Text>
      <Text>text</Text>
      <Text>text</Text>
      <Text>text</Text>
      <Text>text</Text>
      <Text>text</Text>
      <Text>text</Text>
      <Text>text</Text>
      <Text>text</Text>
      <Text>text</Text>
      <Text>text</Text>
      <Text>text</Text>
      <Text>text</Text>
      <Text>text</Text>
      <Text>text</Text>
      <Text>text</Text>
      <Text>text</Text>
    </View>
  </ScrollView>
</Modal>

const styles = StyleSheet.create({
  modalStyle: {
    marginTop: 18,
    marginLeft: "auto",
    marginRight: "auto",
    borderRadius: 20,
    height: "90%",
    width: "90%",
    shadowColor: "#000",
    shadowOffset: {
      width: 0,
      height: 2,
    },
    shadowOpacity: 0.25,
    shadowRadius: 4,
    elevation: 5,
  },
  scrollViewStyle: {
    borderRadius: 20,
    width: "100%",
    justifyContent: "center",
    alignItems: "center",
    backgroundColor: "white",
  },
});

Also how can I change the backgroundColor of the modal? The empty dark transparent space behind the modal is what I mean

Use backdropColor and backdropOpacity

I think what you want here is to add borderRadius to both contentContainerStyle and style. What you are seeing is clipping from the parent container.
Here is a snack -> https://snack.expo.io/@nathanbeesley/react-native-modal-sv-border-radius


Scarlet X - Sapping Arrow can destroy character cards

Sapping arrow is a bit OP against Omnitron right now, might want to make it unable to destroy character cards.

I'm actually very bad about forgetting Omnitron is a Device as well lol

I'm actually very bad about forgetting Omnitron is a Device as well lol


Use BigInteger to avoid overflow (Fixes #331)

Description
Fixed issue #331
There are other PRs floating around for this one but they are all messy or abandoned or both.
This is a very focused change that changes the use of the existing native API calls (which are deprecated but also work back to the react-native supported API16) so that they are computed with protection against integer overflow per this comment from @knot123: https://github.com/rebeccahughes/react-native-device-info/issues/331#issuecomment-428848892
There are valid reasons why you might want to use different native API calls to total up space in Android but you could also argue those are all behavior changes for this module API, so this just fixes the overflow and leaves it at that
Checklist

[X] I have tested this on a device/simulator for android (it's an android fix)
[ ] I added the documentation in README.md.
[ ] I mentioned this change in CHANGELOG.md.

@machour this should be good to go - I'd like for the numbers to be more meaningful but that's different native calls and first we should just stop overflowing...

Published in 0.26.5, thank you!


docs: add workflow docs

closes #225

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

4 of 4 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 87.494%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1952

Relevant Lines:
2231

💛  - Coveralls


Initiating release of 0.10.0-rc1

Initiating release of 0.10.0-rc1

@mkolesnik The bot's comment above is broken.
It seems that everything worked though, checking the verifications here:
https://submariner.io/development/release-process/#step-1-create-shipyard-release

Just to make sure it's clear here too (also discussed in Slack), it doesn't seem like things worked as expected:
https://app.slack.com/client/T09NY5SBT/C010RJV694M/thread/C010RJV694M-1627912530.007500


Not working

I have followed the steps in the README step by step, but when I type:
rails generate scaffold post title body:text published:boolean
I still get the old scaffolfing, with class="field" instead class="form-group", even though the file lib/templates/erb/scaffold/_form.html.erb looks alright. There is actually not one class="field" inside my whole project folder, but I still get the other class.
What is going on???

+1 Experience the same problem on Rails 4.2.5.

It seems the problem was caused by Spring: after running rails generate bootstrap:install you need to restart application for it to see templates in lib/templates. Because Spring was always running, the app didn't see the templates.

+1 on Spring Issue

I couldn't get this working on Rails 4.2.5 initially either - even if I made sure to restart my application after running the rails generate bootstrap:install command (as per the comments above)... Then I realised that I still had the line: gem 'bootstrap-sass', '~> 3.3', '>= 3.3.6' in my Gemfile.
It would seem that adding the bootstrap-generators gem isn't enough
gem 'bootstrap-generators', '~> 3.3.4'

We also need to remove the boostrap-sass gem
gem 'bootstrap-sass', '~> 3.3', '>= 3.3.6'

Confirmation / correction of this would be welcome :)

@coreyaus you don't need to remove bootstrap-sass, just kill spring with
spring stop

Legend - that makes sense. Thanks @duleorlovic


Swift 2.2.1 code fails to parse

I have a swift file with a protocol followed by protocol extensions. There are some comments in the file, including // MARK: - declarations.
When I run cuckoo console utility, parsing fails with errors
Unknown kind: source.lang.swift.syntaxtype.comment.mark Unknown kind: source.lang.swift.decl.extension
As a result, the generated file, contains public without any declaration following it. The generated protocol mock looks ok, though.

Seems like we have to add option to skip unknown tokens or ignore comment tokens. Thanks for the report.

I wasn't able to reproduce your problem. Could you please try it with new version (0.5.0) and send us the file which causes this error?

Unfortunately, same happens with 0.5.0 version.
The problematic source code is
import UIKit
/**
 *  This is the protocol for the repeatable UI elements that can be reused.
 */
public protocol Reusable {
    /**
     *  The reuse identifier of the element.
     */
    var reuseIdentifier: String? { get }
}

// MARK: - UITableViewCell

public extension Reusable where Self: UITableViewCell {
}

I use the generator command
Pods/Cuckoo/run generate --testable MyProj --output out.swift Reusable.swift

and get the
Unknown kind: source.lang.swift.syntaxtype.comment.mark
Unknown kind: source.lang.swift.decl.extension

The out.swift looks like this (notice public declaration above import Cuckoo):
// MARK: - Mocks generated from file: Reusable.swift at 2016-06-16 09:54:23 +0000

import UIKit

/**
 *  This is the protocol for the repeatable UI elements that can be reused.
 */
public
import Cuckoo
@testable import MyProj

public class MockReusable: Reusable, Cuckoo.Mock {
    public let manager: Cuckoo.MockManager<__StubbingProxy_Reusable, __VerificationProxy_Reusable> = Cuckoo.MockManager()

    private var observed: Reusable?

    public required init() {
        observed = nil
    }

    public required init(spyOn victim: Reusable) {
        observed = victim
    }
    public var reuseIdentifier: String? {
        get {
            return manager.getter("reuseIdentifier", original: observed.map { o in return { () -> String? in o.reuseIdentifier } })()
        }
    }

    public struct __StubbingProxy_Reusable: Cuckoo.StubbingProxy {
        let handler: Cuckoo.StubbingHandler

        public init(handler: Cuckoo.StubbingHandler) {
            self.handler = handler
        }
        var reuseIdentifier: ToBeStubbedReadOnlyProperty<String?> {
            return handler.stubReadOnlyProperty("reuseIdentifier")
        }

    }

    public struct __VerificationProxy_Reusable: Cuckoo.VerificationProxy {
        let handler: Cuckoo.VerificationHandler

        public init(handler: Cuckoo.VerificationHandler) {
            self.handler = handler
        }
        var reuseIdentifier: VerifyReadOnlyProperty<String?> {
            return handler.verifyReadOnlyProperty("reuseIdentifier")
        }

    }
}

@FilipDolnik  Seems to be a bug in FileHeaderHandler.

Problem is with the public modificator. So this is raw code which won`t work.
public protocol Reusable {
}

All attributes like @objc causes this as well. Temporary workaround is to use --no-header parameter.

Should be fixed in 0.5.1. Please try it out! :)


Standby command and power on

Hello how to issue standby by uvc and then poweron? I send standby command camera stops but can't get it back to work. I have firmware 1.0.0

有一个xxCPU.C

I don't understand

Anyone please? Ty


Firmware update

Can we get the latest bcf-sdk/bcl/src/bc_cmwx1zzabz.c into new firmware. Also big clown Lora is still branded in the old firmware.

Thanks I've fixed text in the menu
https://github.com/hardwario/bcf-lora-tester-lcd-gps-ttnmapper/blob/master/app/application.c#L99
I do not understand this, can you elaborate more?
Can we get the latest bcf-sdk/bcl/src/bc_cmwx1zzabz.c into new firmware.
If you would like latest SDK, just call make update and sdk/ git submodule folder is updated to the latest version.
https://tower.hardwario.com/en/latest/firmware/basic-overview/?highlight="make update"#sdk-integration


[ConfigTransformer] Keep imported bundle config for routing

Fixes https://github.com/symplify/symplify/pull/4289

Should be fixed :)


Local cache not working as expected when executing get, put and get operations on the same key

This is a extension of the issue #3966 because we could not reproduce the problem with the provided test.
So, we are trying to provide a new test trying to reproduce the actual issue that we observed on our application.
Expected behavior
We execute these operations on a local cache that points to a redis map already initialized:

get initial value
put new value
get new value

We expect to receive the new value on the third operation.
Actual behavior
Sometimes we get the initial value on the third operation.
Steps to reproduce or test case
A test to reproduce the issue:
@Test
public void testLocalCacheGetAndPut() {
    int numberOfKeys = 5_000;

    initializeRedis(numberOfKeys);

    RMap<String, String> localCachedMap = redisson.getLocalCachedMap("test", LocalCachedMapOptions.defaults());
    for (int i = 0; i < numberOfKeys; i++) {
        localCachedMap.get("key" + i);
        localCachedMap.put("key" + i, "value-" + i);
        String cachedValue = localCachedMap.get("key" + i);
        assertThat(cachedValue).isEqualTo("value-" + i);
    }
}

private void initializeRedis(int numberOfKeys) {
    RMap<String, String> map = redisson.getMap("test");
    for (int i = 0; i < numberOfKeys; i++) {
        map.put("key" + i, "initial-value");
    }
}

It fails on different iterations when you execute the test more than once:
org.opentest4j.AssertionFailedError:
expected: "value-377"
 but was: "initial-value"

(...)

org.opentest4j.AssertionFailedError:
expected: "value-1109"
 but was: "initial-value"

(...)

org.opentest4j.AssertionFailedError:
expected: "value-0"
 but was: "initial-value"

Redis version
Redis 5.0.7
Redisson version
3.16.5-SNAPSHOT
Redisson configuration
Default configuration

I'm afraid your test is incorrect since you use getMap() in initializeRedis. Please use same type of object for same name.

I'm afraid your test is incorrect since you use getMap() in initializeRedis method. Please use same type of object for same name.

We only want to show that redis should have some data before starting the test.
If you know how to initialize redis before starting the test, could you tell us how to do it?
It is mandatory not to use the localCachedMap to initialize the data because the initialization process could interfere with the test. That is why we used a map to initialize the data.

@mrniko I've reimplemented the test to avoid initializing redis from the test code.
Now it waits 20 seconds for a manual redis initialization executing this command (replacing the redis port with the current port) with this file: redis_data.txt:
cat redis_data.txt | redis-cli --pipe -p port

All data transferred. Waiting for the last reply...
Last reply received from server.
errors: 0, replies: 1001

The test:
@Test
public void testLocalCacheGetAndPut() throws InterruptedException {
    System.out.println("waiting for manual redis initialization: \"cat redis_data.txt | redis-cli --pipe -p port\"");
    Thread.sleep(20_000);
    System.out.println("testing local cache");

    RMap<String, String> localCachedMap = redisson.getLocalCachedMap("test", new StringCodec(), LocalCachedMapOptions.defaults());
    for (int i = 0; i < 1_000; i++) {
        localCachedMap.get("key" + i);
        localCachedMap.put("key" + i, "value-" + i);
        String cachedValue = localCachedMap.get("key" + i);
        assertThat(cachedValue).isEqualTo("value-" + i);
    }
}

It fails on different iterations:
waiting for manual redis initialization: "cat redis_data.txt | redis-cli --pipe -p port"
testing local cache

org.opentest4j.AssertionFailedError:
expected: "value-363"
 but was: "initialvalue"

waiting for manual redis initialization: "cat redis_data.txt | redis-cli --pipe -p port"
testing local cache

org.opentest4j.AssertionFailedError:
expected: "value-0"
 but was: "initialvalue"

waiting for manual redis initialization: "cat redis_data.txt | redis-cli --pipe -p port"
testing local cache

org.opentest4j.AssertionFailedError:
expected: "value-534"
 but was: "initialvalue"

Fixed! Thanks for report

Thank you @mrniko, it looks very promising!
Would it be possible to release the 3.16.5 PRO version on the current month?
We are eagerly waiting for the local cache fixes included in that release.

@ipalbeniz
I'll release it during next week.


bump version to 1.32.0

related to #197

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

Project coverage is 83.81%. Comparing base (94b8b9f) to head (a7f5e89).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #206   +/-   ##
=======================================
  Coverage   83.81%   83.81%
=======================================
  Files          19       19
  Lines         791      791
=======================================
  Hits          663      663
  Misses        102      102
  Partials       26       26

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

🚨 Try these New Features:

Flaky Tests Detection - Detect and resolve failed and flaky tests


Update copyright year

Description
I looked for calendar years 2022, 2021, and 2020 in search of any copyright years we still haven't updated yet.

SFMLBuildMaster: Build this please.

Thanks! 🙂


Generic's Generic planet lobby BG

Description

Changelog
<!--
Here you can fill out a changelog that will automatically be added to the game when your PR is merged.
There are 4 icons for changelog entries: add, remove, tweak, fix.

You can put your name after the :cl: symbol to change the name that shows in the changelog.
Like so:
:cl: PJB

Generally, only put things in changelogs that players actually care about.
Stuff like "Refactored X system, no changes should be visible" shouldn't be on a changelog.

:cl: Generic
- add: Added fun
- remove: Removed fun!
- add: Added planets lobby screen was added
- tweak: Froze earth

You should edit the PR name and description to uh
Be something :P

Edit the PR description to be something basic, it gets saved in the commit history.

Don't merge this until the pr description is like, anything. A changelog isn't needed, a checklist isn't needed, but just state what it does, please.

Don't merge this until the pr description is like, anything. A changelog isn't needed, a checklist isn't needed, but just state what it does, please.

you have permission to edit it

Don't merge this until the pr description is like, anything. A changelog isn't needed, a checklist isn't needed, but just state what it does, please.

you have permission to edit it

I am well aware.


[Bug]: Add workflows to verify all expected maven artifacts are published for a release

Describe the bug
Coming from: https://github.com/opensearch-project/job-scheduler/issues/374
Few maven publish workflows within a component changed and published artifacts in a different location.
This caused problems.
We identified the problem by manually looking at maven co-ordinates and these should be written as automated workflows and a pre-check for gating the release.
Proposal
Lets add workflows to verify all expected maven co-ordinates have expected artifacts before we officially release OpenSearch distribution.
This should help us automate and verify this doesn't happen for any component within the distribution.

Issue is vlaid, we will need brain stone session to finalize the design before moving forward.

Related: https://github.com/opensearch-project/opensearch-build/issues/2928

I think this is duplicated with https://github.com/opensearch-project/opensearch-build/issues/2928 @saratvemulapalli is it ok we close this issue and sync the comment to the old one?
Thanks.

Thanks folks. Yup the issue #2928 captures it.

Dup #2928


Simulation Drag Model not Receiving Correct Link Velocity

The drag plugin, simulation/src/gazebo_model_plugin_drag/gazebo_model_plugin_drag.cc, is receiving incorrect inertial frame velocity values for the body link. It seems to always get a unit vector, resulting in large computed drag values equivalent to Astrobee zooming around at 1 m/s all the time, ~0.05 N, (~1/3 of typical per-axis thruster input, for reference). Normal drag values should be about 3 orders of magnitude lower for typical Astrobee speeds, so pretty negligible. We initially noticed this when using a mass parameter estimator that was having trouble converging and always estimating high in simulation---when removing the drag plugin altogether it converges perfectly.
I've gotten this to happen locally for both my FSW 15.1 workspace and a clean develop workspace pulled today. I'm still waiting for someone else on our team to confirm this isn't just a weird local problem I'm having.
To pinpoint the issue, line 82 of that file above is giving bad velocity values for GetRelativeLinearVel(). Here are some typical values I'm seeing in sim:

I can take a look at this deeper it we confirm it's not just me seeing the issue. (Also note that the drag bounces around between negative and positive when Astrobee's actual velocity is low, which is why it's not running off from a constant drag force being applied.)

@Pedro-Roque In case he gets the chance to check it out.

Thanks @albee for finding this out! I'll check it on my system by the end of the week too

Yeah, thanks @albee, nice catch!
A couple of minor followup points:

This particular issue could be especially problematic because it accidentally provides a strong artificial stabilizing force for holding position, which could mask controller instability.
As a non-urgent suggestion, we might want to include a term for air flow. The ISS requirement for cabin air flow is 15-40 feet per minute, and most USOS modules have overhead-to-deck as the nominal flow direction. A very simple improvement to the drag model would be to add a steady flow rate from overhead to deck at 20 feet per minute (7.6 cm/s). The real air flow is of course more complicated and variable, but even a simple term like that would provide qualitatively more realistic behavior when the robot idles propulsion--it won't hold position but instead will systematically drift, usually toward the deck.

Yeah, thanks @albee, nice catch!
A couple of minor followup points:

This particular issue could be especially problematic because it accidentally provides a strong artificial stabilizing force for holding position, which could mask controller instability.
As a non-urgent suggestion, we might want to include a term for air flow. The ISS requirement for cabin air flow is 15-40 feet per minute, and most USOS modules have overhead-to-deck as the nominal flow direction. A very simple improvement to the drag model would be to add a steady flow rate from overhead to deck at 20 feet per minute (7.6 cm/s). The real air flow is of course more complicated and variable, but even a simple term like that would provide qualitatively more realistic behavior when the robot idles propulsion--it won't hold position but instead will systematically drift, usually toward the deck.

@trey0 , on the ReSWARM session #2 I noticed a significant difference between simulation and ISS behavior, that now I believe could come from this problem. I will check on my code if the bug is present (since I use the same stack as @albee , most likely it will). I also have / can have bags from Simulation and ISS Deployment for unit tests in case they are helpful for anything?

Hi @Pedro-Roque,
You can ask Jose Benavides about data availability in general. In very recent news, the Astrobee Facility has just publicly released Astrobee ISS telemetry bags for the first time [1]. So far it covers two ISS activities, hopefully with more on the way. It's a work in progress.
[1] https://www.nasa.gov/content/guest-science-resources - follow the "Data" link at the bottom

I tested in noetic and while moving at max speed:
drag_.Length(): 0.168776
drag_.Normalize(): 0.058454 0.996875 0.053141

I can confirm this problem on kinetic:
drag_.GetLength(): 1
drag_.Normalize(): 0.891642 -0.327231 -0.31288

@marinagmoreira Thanks, @Pedro-Roque and I are going to look for a fix next week. @trey0 we should be able to add in that constant airflow term too, we'd just have to differentiate between the ISS and granite sim worlds.

we should be able to add in that constant airflow term too, we'd just have to differentiate between the ISS and granite sim worlds.

Gotcha. You may have more insight here than I do, but maybe we need not bother to differentiate? I assume/hope that a slight downdraft in the granite sim would not cause the robot to push through the granite table!

Hi @marinagmoreira,
I've tested the drag model on 20.04, and the problem persists - the drag is much higher than what we believe it should be. Here is a print of the debug points:

and here is a print of the output, with the Astrobee being static in the station, after undocking:

So it seems that some of the constants are, then, not great? I'll investigate a bit more...

So you think the velocity is fine, but the coefficient/area/density might be off? Or is the velocity also wrong?

@marinagmoreira I believe the issue is the in-situ modification of drag_.Normalize(), which then drag_.Length() picks-up as "1" and not as the real velocity.
Adding an extra variable for the velocity fixed the issue, as far as we can see.

Yep, thanks @albee !! :smile:

Fixed by #462.
Thanks @marinagmoreira  @Pedro-Roque @trey0 !


Global + per-validator verifications dashboard improvements

(possibly more info from /status endpoints, responses to questions, clarification of cancel/app closed/etc, histogram of attempt counts broken down by user abandonment/cancelation method to differentiate and filter out test users)

histogram of attempt counts broken down by user abandonment/cancelation method to differentiate and filter out test users

https://github.com/celo-org/clabs-pipeline/pull/34

histogram of attempt counts broken down by user abandonment/cancelation method to differentiate and filter out test users

https://github.com/celo-org/clabs-pipeline/pull/34


SQLitePCLRaw.bundle_winsqllite3 cases a UWP ARM64 app to fail to start

The app fails to start with the error 'The program '[15380] SQLLiteTestApp.exe' has exited with code<PHONE_NUMBER> (0xc0000139) 'Entry Point Not Found'.   The e_sqlite3 bundle seems to at least load.

Can you post a minimal repro sample project?

SQLLiteArmSample.zip
Here you go, I left x64 and Arm64 in the sample.  All you have to do is use remote debugger on an Arm64 device and deploy the Arm64 Debug build to it.  It will fail to start with the error above.  x64 works fine.   No code other than a Blank UWP sample auto generated from VS and the inclusion of the latest stable build of your package from Nuget

Hmmm.  Sorry for the slow response on this one.
Yeah, the repro is pretty simple.
I don't have an ARM device for testing, so I'm just looking for things that might be wrong.
The repro sample doesn't even call SQLitePCL to initialize it.  Are we sure the error is coming from SQLitePCLRaw?  Do you have the full error message?
So, er, Windows on ARM does have a SQLite library, right?

Let me see if I can get an Arm device setup for you to access remotely.  No promises
"Are you sure....",   Never sure but if I remove that package on arm64 the app starts successfully.
Yes there is a winsqlite3.dll in Windows on ARM.  Here is a directory listing of c:\windows

One other thing of note is if I build for x64 and deploy that to the Arm device it runs.  I even added the sample database creation code from your wiki that creates an in memory db and creates a table.  And it runs
Gary

OK. One theory is that even if the SQLitePCLRaw code is not called, the assembly is being loaded, and it is trying to resolve DllImports, and one of them is not found, thus resulting in the entry point not found error.
BTW, that exception. Did it give the name of the entry point which was not found?
The most likely cause for this would be an older version of SQLite.
Would it be possible for you to figure what version of SQLite is used in winsqlite3.dll ?

@ericsink I have a remote Arm64 machine ready for you to remotely connect to and debug.  Please send me a message at<EMAIL_ADDRESS>and I can share connection information.

@GaryCaldwell Before we do that, please address the questions I asked in the previous comment.

@ericsink, The name of the entry point is not listed that I can see.  The fileversion for winsqlite3.dll is 3.34.1.
Same as my x64 Win11 box.  Does that help?

Humph. It would've been MORE helpful if the version on ARM was different.
This still feels like an attempt to load an entry point that got introduced after 3.34. But the fact that it only happens on ARM doesn't fit very well with that theory.
I need to know the name of the missing entry point. I'll get back to you about setting up the remote thing.


CloudConfig client doesn't get config from ConfigServer after upgrading spring-cloud from 1.0.0.RELEASE to 1.0.1.RELEASE

I have a working microservice build against 1.0.0.RELEASE and are getting my properties from a remote cloud config server. After upgrading the microservice to 1.0.1.RELEASE the service doesn't start anymore because of not resolvable property placeholders:
Caused by: java.lang.IllegalArgumentException: Could not resolve placeholder 'cassandra.seeds' in string value "${cassandra.seeds}"
at org.springframework.util.PropertyPlaceholderHelper.parseStringValue(PropertyPlaceholderHelper.java:174)

When reverting back to 1.0.0.RELEASE the service again starts.
Maybe related:
 ConfigClientAutoConfiguration.ConfigServerHealthIndicatorConfiguration
      - @ConditionalOnClass classes found: org.springframework.boot.actuate.health.HealthIndicator (OnClassCondition)
      - matched (OnPropertyCondition)
      - @ConditionalOnBean (types:     org.springframework.cloud.config.client.ConfigServicePropertySourceLocator; SearchStrategy: all) found no beans (OnBeanCondition)

Is any additional action necessary when upgrading to 1.0.1?

@DirkLachowski We separated the starters, so config is not auto-included anymore.  Do you have spring-cloud-starter-config included?

@spencergibb Much better, that fixed it. Thanks for your help.


chore: skip flakey IBM PPC test

Description
https://issues.redhat.com/browse/KFLUXBUGS-1179
Issue ticket number and link
https://issues.redhat.com/browse/KFLUXBUGS-1179
Type of change

[x] Test disabling

How Has This Been Tested?
N/A
Checklist:

[X] I have performed a self-review of my code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added meaningful description with JIRA/GitHub issue key(if applicable), for example HASSuiteDescribe("STONE-123456789 devfile source")
[ ] I have updated labels (if needed)

/lgtm


J F: Watch multicoinhodler

J F requests the watch of the watch_keyword multicoinhodler. See the MS search here and the Stack Exchange search here.

!!/approve


docs: add PR template

I have renamed the file and also make the parent folder as .github. I am not getting where it is going wrong

I have renamed the file and also make the parent folder as .github. I am not getting where it is going wrong

Rename the file with PULL_REQUEST_TEMPLATE.md

Please adjust the content and Markdown correctly. You can take inspiration from https://github.com/web3community/web3community.github.io/blob/main/.github/PULL_REQUEST_TEMPLATE.md


Fix Mempool TransactionRegister Deadlock

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#1242  👈
#1241
feature/proof-of-stake

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @tholonious and the rest of your teammates on  Graphite


feat: get operation info from context

Adds huma.GetOperationInfo(ctx) to get things like the operation ID for logging/metrics/auditing/etc.

Codecov Report

Merging #23 (10b2049) into main (c54a214) will increase coverage by 0.13%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main      #23      +/-   ##
==========================================
+ Coverage   83.30%   83.44%   +0.13%
==========================================
  Files          20       20
  Lines        1366     1377      +11
==========================================
+ Hits         1138     1149      +11
  Misses        168      168
  Partials       60       60

Impacted Files
Coverage Δ

operation.go
75.20% <100.00%> (+2.23%)
:arrow_up:

router.go
65.06% <100.00%> (+0.24%)
: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 c54a214...10b2049. Read the comment docs.


Do environment deployments respect the ##vso[build.updatebuildnumber] command?

If you use:
echo ##vso[build.updatebuildnumber]<IP_ADDRESS>
Either in the same or previous stage as a deployment job in some pipeline, it appears the environment still uses the 'original' build number of something like 20200501.1 rather than a custom one of something like <IP_ADDRESS> when showing the little "label" in the deployment summary list page for the environment. If you click on the label, it will take you to the pipeline, which has the correct custom build number displayed.

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

ID: 77d95db6-9983-7346-d0eb-4b7443e4e252
Version Independent ID: 0a22cccc-318d-592f-d1ab-09ec01d88087
Content: Environment - Azure Pipelines
Content Source: docs/pipelines/process/environments.md
Product: devops
Technology: devops-cicd-process
GitHub Login: @juliakm
Microsoft Alias: jukullam

Thanks for your question. It looks like you're working through an issue with your scenario or implementation, rather than an issue with the documentation. Here are a couple of options where you might consider asking your question:

Azure DevOps Support Bot
Azure DevOps on Stack Overflow

Also, you may have encountered an issue with the product itself. To make sure it gets in front of the right people, please submit your bug here.


Since update to 12.5 I get error with amplify codegen

How did you install the Amplify CLI?
Configuring in Amplify BuildSettings
If applicable, what version of Node.js are you using?
No response
Amplify CLI Version
12.5.1 and 12.5
What operating system are you using?
aws build image
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
I only use amplify for the frontend and create the aws-export during frontend installation
frontend:
  phases:
    preBuild:
      commands:
        - python3 --version
        - yum -y install python3-pip
        - pip3 install boto3 --user
        - pip3 install pandas --user
        - python3 ../scripts/create_aws_exports.py
        - mv aws-exports.js src/aws-exports.js
        - cp cdk_infrastructure/graphql/schema.graphql .
        - python3 ../scripts/create_amplify_config.py
        - amplify codegen
        - rm schema.graphql
        - npm install --legacy-peer-deps

Describe the bug
With version 12.4 it works fine
Expected behavior
codgen is working with version 12.5
Reproduction steps

Run with build setting 12.5.0 or 12.5.1 -> failure will be shown when using codegen
Run with buildsetting Amplify CLI 12.4.0 -> codegen will work

Project Identifier
No response
Log output

# Put your logs below this line

Additional information
Output Version 12.5
2023-09-27T17:25:54.307Z [INFO]: # Executing command: amplify codegen
2023-09-27T17:25:56.110Z [INFO]: User: arn:aws:sts::xxxxxxxxx:assumed-role/xxxxxxxxxxxx-1DVW5K6N191RK/BuildSession is not authorized to perform: appsync:GetGraphqlApi on resource: arn:aws:appsync:eu-central-1:xxxxxxx:apis/xxx
Output version 12.4
2023-09-27T16:44:03.332Z [INFO]: # Executing command: amplify codegen
2023-09-27T16:44:04.916Z [WARNING]: - Generating GraphQL operations
2023-09-27T16:44:05.051Z [WARNING]: ✔ Generated GraphQL operations successfully and saved at src/graphql
2023-09-27T16:44:05.052Z [WARNING]: - Generating
2023-09-27T16:44:05.064Z [WARNING]: ✔ Code generated successfully and saved in file src/API.ts
Before submitting, please confirm:

[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.

Hi @chkrause, do you have your apiId set in .graphqlconfig.yml? (projects.<project-name>.extensions.amplify.apiId).
If that is the case, because you are outside of an Amplify project and you have your apiId, the CLI is attempting to download your schema from AppSync. It looks like you are already obtaining your schema through other means. If you remove apiId the CLI will not attempt to download the schema.

@alex-mozolevsky-c that appears to be a different issue. Can you open a new issue with your GraphQL schema or minimum reproduction schema?

Hi @chkrause, do you have your apiId set in .graphqlconfig.yml? (projects.<project-name>.extensions.amplify.apiId).
If that is the case, because you are outside of an Amplify project and you have your apiId, the CLI is attempting to download your schema from AppSync. It looks like you are already obtaining your schema through other means. If you remove apiId the CLI will not attempt to download the schema.

@dpilch I have set appId because I remember correctly it was mandatory, I will try to remove it and test again.

Hi @chkrause, do you have your apiId set in .graphqlconfig.yml? (projects.<project-name>.extensions.amplify.apiId).
If that is the case, because you are outside of an Amplify project and you have your apiId, the CLI is attempting to download your schema from AppSync. It looks like you are already obtaining your schema through other means. If you remove apiId the CLI will not attempt to download the schema.

@dpilch I have set appId, If I remember correctly it was mandatory, I will try to remove it and test again.

Thx, I could fix it with removing appid from .graphqlconfig.yml


ARM32 support

Maven artefacts does not seems to support non 64bits ARM architecture.
ZStandard library does, is it possible to build zstd-jni for ARM 32 bits architectures like ARM7 ? How ?
Thanks

Ok thanks, I will look into it.
2018-02-01 0:03 GMT+01:00 luben karavelov<EMAIL_ADDRESS>
Hi,
just pushed the script that I use to compile the native part on the hosts
that lack JDK. Please take a look at https://github.com/luben/zstd-
jni/blob/master/make_so.sh for inspiration.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/luben/zstd-jni/issues/53#issuecomment-362100768, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAJIdtJN34DUYIar4qNT42_m90SKpHycks5tQPFLgaJpZM4RymUu
.

Hi,
If you prefer there is now a fully functional cmake build that can compile the native lib, to be included in the JAR.
Regards,
luben


Add new Sponsor for topic "Encapsulation / Structuring of Code / MVC Concept"

Unfortunately, no contributor was found for the topic "Encapsulation / Structuring of Code / MVC Concept".
This issue should find a sponsor for it and be linked to the pull request

created with #27


[Bug]: IMPORT ERROR

Bug Description
So suddenly my project stopped working complaining it could not find SimpleDirectoryReader.
I created a virtual environment , you can see the versions displayed in pip list.
Then the import statement: from llama_index.core import VectorStoreIndex, SimpleDirectoryReader
Is throwing the error you can see below. I tried downgrading and reinstalling but I am getting this issue.

Any idea why this is happening? I tried this on another system and this error isn't happening but just on my system.
Version
0.10.7
Steps to Reproduce
Created a FRESH VIRTUAL environment.
Did a pip install llama-index
Relevant Logs/Tracbacks
No response

@kindler-king did you mix legacy imports with normal imports? Need to be all legacy or all new imports (similar to pydantic v1/v2, if you ever had to deal with that)

Hello @logan-markewich , thanks for the quick response.
I was trying to upgrade my 0.9.13 to 0.1.7 the latest version and played around with different import statements, where I might have been trying to import the wrong stuff.
But currently all I want to do (as a test) is to try and import this line:
from llama_index.core import VectorStoreIndex, SimpleDirectoryReader
I tried this on my PC with the same exact dependencies in a virtual environment and it works, but when I reproduce the environment on my laptop, and try the above import statement, it returns that error.

@kindler-king do you maybe have it installed globally outside of a venv?
Try this in a fresh terminal
pip uninstall llama-index. # remove any global
python -m venv venv
source venv/bin/activate
pip install llama-index

Hey @logan-markewich , you were right, it was a clash between legacy imports and new imports.
I set up a virtual environment, installed llama-index and then migrated to the new imports by following the docs, 1 at a time.
Most of the imports are working, however the only one I haven't been able to resolve is this one:

Any idea why from llama_index.llms.openai import OpenAI is raising this error?
Thanks a lot :D

Try pip install -U llama-index-core llama-index-llms-openai llama-index-embeddings-openai


Support non default repositories in chart generator

Honor "track-repository" property, along side the track property,
while generating charts.

Did you mean to say "Honor the track-repository property"?

Right, I've changed it.


404 after deployment of piplineCI

Hi All,
I am trying to install pipeline api server on aws, from instructions here. But i am trying to access pipeline manager of api i am getting 404.
curl http://x.x.x.x/pipeline/api/v1
404 page not found

when i try it in browser its redirects to {public ip}\authorize and return 404 as well. I can see app registered in my Github
Any Help is appreciated!
Thanks!
Bobby

BTW  prometheus and grafana seems to work

Hi @bobbych,
First of all, thank you for trying out the Pipeline!
http://x.x.x.x/pipeline/api/v1 is just a subpath in our API and currently doesn't return anything (however I have just created an issue to return our API map at this endpoint as just like Kubernetes does, see https://github.com/banzaicloud/pipeline/issues/257).
You can find the possible valid path postfixes currently here (our Swagger documentation is in the making): https://github.com/banzaicloud/pipeline/blob/master/main.go#L107
So for example to list your clusters you have to call: http://x.x.x.x/pipeline/api/v1/clusters
To get and API token you have to call: http://x.x.x.x/pipeline/api/v1/token
I hope this helps.

I forgot to mention that on Wednesday we will have a new release where we will have OAuth enabled for the whole Pipeline API and things will be probably more straightforward. ;-)

@bonifaido thanks for the tip, got a little further with this, i was able to deploy to aws using cloud formation (using "latest" tag) and pass the auth part . I started using postman examples using Bear token shown in UI,  made request to
http://x.x.x.x/api/v1/clusters
Response 200

<!DOCTYPE html>
<html>
    <head>
        <meta charset="utf-8">
        <meta name="version" content="0.8.2">
        <script>
	window.DRONE_USER = {"id":1,"login":"xxxx","email":"","avatar_url":"https://avatars3.githubusercontent.com/u/xxxxxxx?v=4","active":true,"synced":1521058449};
	window.DRONE_SYNC =  false ;
</script>
        <script>
	window.DRONE_CSRF = " <token is printed here> "
</script>
        <link rel="shortcut icon" href="/favicon.png">
    </head>
    <body>
        <script type="text/javascript" src="/static/vendor.083efb00670e0f927f32.js"></script>
        <script type="text/javascript" src="/static/bundle.d1a94d49a07c34299724.js"></script>
    </body>
</html>

and also tried making requested using pipeline endpoint, i am getting
http://x.x.x.x/pipeline/api/v1/clusters
{
    "code": 401,
    "message": "Invalid token",
    "error": "Error making API request.\n\nURL: GET http://dapper-tortoise-vault:8200/v1/secret/accesstokens\nCode: 403. Errors:\n\n* permission denied"
}

@bonifaido thanks for your response. I was able to get it to go past auth and have ui working, btw i deployed to aws using cloud formation template (latest tag. Tag 0.3.0 as documented on pipeline-cp-launcher does not exist yet). When i tried to use postman examples to create clusters, with Bearer token displayed on UI
POST http://x.x.x.x/api/v1/clusters

body: {
  "name":"awscluster-bobby-1",
    "location": "eu-west-1",
    "cloud": "amazon",
    "nodeInstanceType": "m4.xlarge",
    "properties": {
        "amazon": {
            "node": {
                "spotPrice": "0.2",
                "minCount": 1,
                "maxCount": 2,
                "image": "ami-06d1667f"
            },
            "master": {
                "instanceType": "m4.xlarge",
                "image": "ami-06d1667f"
            }
        }
    }
}

Response:

<!DOCTYPE html>
<html>
    <head>
        <meta charset="utf-8">
            <meta name="version" content="0.8.2">
                <script>
	window.DRONE_USER = {"id":1,"login":"xxxxx","email":"","avatar_url":"https://avatars3.githubusercontent.com/u/xxxxxx?v=4","active":true,"synced":1521058449};
	window.DRONE_SYNC =  false ;
</script>
                <script>
	window.DRONE_CSRF = "<token printed here>"
</script>
                <link rel="shortcut icon" href="/favicon.png">
                </head>
                <body>
                    <script type="text/javascript" src="/static/vendor.083efb00670e0f927f32.js"></script>
                    <script type="text/javascript" src="/static/bundle.d1a94d49a07c34299724.js"></script>
                </body>
            </html>

Also tried with pipeline endpoint
POST http://x.x.x.x/pipeline/api/v1/clusters

body: {
  "name":"awscluster-bobby-1,
    "location": "eu-west-1",
    "cloud": "amazon",
    "nodeInstanceType": "m4.xlarge",
    "properties": {
        "amazon": {
            "node": {
                "spotPrice": "0.2",
                "minCount": 1,
                "maxCount": 2,
                "image": "ami-06d1667f"
            },
            "master": {
                "instanceType": "m4.xlarge",
                "image": "ami-06d1667f"
            }
        }
    }
}

Response:

{
    "code": 401,
    "message": "Invalid token",
    "error": "Error making API request.\n\nURL: GET http://dapper-tortoise-vault:8200/v1/secret/accesstokens\nCode: 403. Errors:\n\n* permission denied"
}

@bobbych we are in the middle of the release and because of this the documentation is a bit out of sync with the exact git tags. Could you please try the master branch from https://github.com/banzaicloud/pipeline-cp-launcher to start a cluster? I just tried now with the latest master and I successfully managed to call the API http://34.xxx.xxx.xx/pipeline/api/v1/clusters

@bobbych sorry for the inconvenience. The postman collection referred in the README wasn't refreshed thus was pointing to an outdated one.
Can you try the updated postman collection from https://github.com/banzaicloud/pipeline#create-and-scale-your-cluster ?
Also you'll need to pass an bearer access token to the REST API call which you can obtain from https://github.com/banzaicloud/pipeline/blob/master/docs/github-app.md#acquiring-the-access-token

Hi @bobbych !
I'm happy to inform you that our 0.3.0 release just went out yesterday, so could you please try out with that new version?

@bonifaido seems to work now, thank you!


UDM Pro not updating DNS for my cloudflare

Hi,
I followed all the steps but somehow its not updating. Do i need to create specific kind of worker? i selected default "HTTP Handler" worker and not the "HTTP Router" kind.
Beyond that i have reched everything still no update. Only thing is that earlier i had dyndns configured to update my google domain. Which i removed and added new one. Might be its not triggering dyndns in unifi?

I just set this up for first time 5min ago and I used the "HTTP router" worker type and it worked right off the bat, so that could be the issue?

i did that too. it still doesnt do anything. I even added "A" record for "home" under my domain thinking that it might not be able to create "A" record. but ip didnt update.

I'm also having this problem. I'm not sure where to look for any logs or error messages.

I had the same issue and it was because I had included https:// in the start of the server address. Just like the readme says it should be <worker-name>.<worker-subdomain>.workers.dev/update?ip=%i&hostname=%h

As @ansman has noted, the solution is specifying only the FQDN and path for your worker endpoint. Do not include either http:// or https://


Shortcut key guide after the text can switch between Chinese and English.

Description of the new feature / enhancement
Shortcut key guide after the text can switch between Chinese and English. Keyboard shortcuts are great for me, but my English is very limited. thank you
Scenario when this would be used?
Shortcut key guide after the text can switch between Chinese and English. Keyboard shortcuts are great for me, but my English is very limited. thank you
Supporting information
Shortcut key guide after the text can switch between Chinese and English. Keyboard shortcuts are great for me, but my English is very limited. thank you

Known issue for shortcut guide. Will be fixed via /dup #890


Flaky VR test: visual-regression/pages/pages-single-result.spec.ts:32:15 › image rtl single-result page snapshots

Description

This test failed on main, as well as in other PRs (https://github.com/WordPress/openverse/actions/runs/4850898382/jobs/8644256809), so maybe it's not flaky but the snapshot is incorrect?
The following tests are flaky in  visual-regression/pages/pages-single-result.spec.ts:
ltr/rlt - lg/2xl
The problem is in the top margin of the "licenses" section:

Additional context

Marking this as critical to fix the Playwright CI as soon as possible.
I've rebased all my open PRs onto main to make sure that they use the updated Playwright navigation utilities. A couple of PRs passed the CI:
https://github.com/WordPress/openverse/pull/1889
https://github.com/WordPress/openverse/pull/1158
https://github.com/WordPress/openverse/pull/1888
Several others failed. I'll list all the failed PRs to make sure that we fix all of them.
Failing tests
https://github.com/WordPress/openverse/actions/runs/4851053078/jobs/8644722405?pr=1004
playwright_1  |     visual-regression/pages/pages-single-result.spec.ts:32:15 › image ltr single-result page snapshots › screen at breakpoint 2xl with width 1536 › from search results
https://github.com/WordPress/openverse/actions/runs/4851412123/jobs/8645267500?pr=1141
playwright_1  |     visual-regression/pages/pages-single-result.spec.ts:32:15 › image rtl single-result page snapshots › screen at breakpoint 2xl with width 1536 › from search results
playwright_1  |     visual-regression/pages/pages-single-result.spec.ts:32:15 › image rtl single-result page snapshots › screen at breakpoint lg with width 1024 › from search results
https://github.com/WordPress/openverse/actions/runs/4850933584/jobs/8644347536?pr=1188
playwright_1  |     visual-regression/pages/pages-single-result.spec.ts:32:15 › image ltr single-result page snapshots › screen at breakpoint 2xl with width 1536 › from search results

I'm closing this issue as critical because #1960 fixed failing CI. I will, however, open an issue for exploring how we can fix the test without maxDiffPixelRatio.


Small type improvements

A few opportunistic fixes to Pyright warnings in the client. Lots more to fix; this is just some low-hanging fruit (making client.stub resolve properly yields some nice IDE QOL improvements though!)

@prbot approve

👍


Fix: Check for webContents.isDestroyed before hooking for breadcrumbs

Descriptions
Hey, I am running to an error caused by an attempt to access a destroyed web contents. According to the error logged to Sentry, it originates from this line of code. See:

The cause
First of all, we have snippet of code intended as a security measure recommended by electron documentation. See:
https://electronjs.org/docs/tutorial/security#13-disable-or-limit-creation-of-new-windows
app.on('web-contents-created', (event, webContents) => {
  webContents.on('new-window', (event) => {
    event.preventDefault();

    // do global custom behavior if needed.
  });
});

The electron integrations is hooking into the same web-contents-created to collect breadcrumbs on the web contents. However, due to the use of setImmediate, there will be a race condition between when the webContents gets destroyed and the code within the setImmediate gets executed and will try to access an already destroyed webContents.
This PR
Adds a check through contents.isDestroyed() method and returns early if returns true.

Heya @HazAT, I noticed from a couple of other PRs that you're the one reviewing them. It would be great if you can have a look at this PR 👍

🏓 Anyone left in this project?

Sorry for the delay, thx!

No worries, was just wondering because last activity on this repo was a couple of monts ago!
Thanks for merging this :+1:


Bug/accessibility 1

This PR aims to fix these 5 accessibility bugs
Local impact:
File type combo box name in NVDA reader: https://github.com/microsoft/azuredatastudio/issues/6732

Backup file control name in NVDA reader: https://github.com/microsoft/azuredatastudio/issues/6725

Restore plan table name: https://github.com/microsoft/azuredatastudio/issues/6690

Wider impact:
Button color contrast with white text: https://github.com/microsoft/azuredatastudio/issues/6667
Old:

New:

Moving between dialog tabs: https://github.com/microsoft/azuredatastudio/issues/6695
Old :
Tab key used to move from one header to other when header are no more then it will go to current tabs contents
New:
Tab key from header will take user to content.
Right and left arrow keys will move between tab headers

Regarding button contrast, part of what's contributing to the contrast failure is that the background color is 80% opacity against a light gray background. So the flattened color fails. Ok to proceed with VSCode alignment as a stop gap on the goal to have full alignment with Azure Portal buttons which pass accessibility requirements. Regardless of solution, we should move away from the 80%/100% background color for rest/hover/etc. states as this will introduce possible failure for colors that normally pass against a white background when placed over a different color background.


ng-cloak not working (also not working on codepen examples)

Heya, raised the issue about ng-cloak not working a few days back in a month-old issue. Thought I'd re-raise it here. The ng-cloak doesn't appear to be working, neither in the examples here: http://iamisti.github.io/mdDataTable/
The angular curly braces are seen for a brief moment, and the same happens when you createa a $http post/delete onto the table.
I've tried adding ng-cloak everywhere, on top of my angular app, in your node_module html files, hardcoding it onto css, but to no avail. Any chance you can take a look at it?

Hey @jackywhlee , sure! I'm sorry I just forgot this ng-cloak thingy.
It might take a while since I don't have too much time, probably will fix it on the weekend.

Hey @iamisti . Understand that you're a busy person, but was hoping to remind you about the ngcloak bug :+1:


Landsat Collection - Missing Items

When comparing the Landsat Archive from microsoft planetary computer and earth-search it seems like a lot of items are missing.
Earth Search Return:

Microsoft PC:

Is this expected ?

Hello Julian, the landsat collection at Earth-search is incomplete, and it's also Collection 1 do is deprecated now.
For Landsat data, use the official USGS Landsat STAC API now, which can be considered the source of truth for Landsat:
https://landsatlook.usgs.gov/stac-server


[QUESTION]Using response_model to get long json is extremely slow

First check

[x] I used the GitHub search to find a similar issue and didn't find it.
[x] I searched the FastAPI documentation, with the integrated search.
[x] I already searched in Google "How to X in FastAPI" and didn't find any information.

TL;DR
When trying to get long (~200-300 items) list of entity with it's relationships using response_model the request is extremely slow (10-20 seconds). How can I avoid it?
Description
In ML ploject I have an entity "intent" with examples of user's requests representing this intent.
My current database model looks so:
class Intent(Base):
    __tablename__ = 'intent'
    id = Column(GUID(), primary_key=True, default=uuid.uuid4, unique=True, nullable=False, index=True)
    name = Column(String, unique=True)
    examples = relationship("IntentExample", back_populates="intent", cascade="all, delete-orphan")

class IntentExample(Base):
    __tablename__ = 'intent_example'
    text = Column(String, primary_key=True)
    intent_id = Column(GUID(), ForeignKey('intent.id'))
    intent = relationship("Intent", back_populates="examples")

I try to get full list of intents with following code (using crud_base.py from full-stack-fastapi-postgresql project):
@router.get("/", response_model=List[Intent])
def get_intents(db: Session = Depends(get_db)):
    data = crud.intent.list(db)
    print(data)
    return data

I see that data is selected from postgres in a second and printed to stdout in upper example code.
After that something inside fastapi / pydantic / ??? is converting response to response_model and it takes a lot of time.
If I do just @router.get("/") without response_model the response is returned very fast, but it doesn't contain list of examples which I need.
Pydantic schemas for Intent:
class IntentExample(BaseModel):
    text: str

    class Config:
        orm_mode = True

class Intent(BaseModel):
    id: UUID4
    name: str
    examples: List[IntentExample] = []

    class Config:
        orm_mode = True

Please help me to find a correct way to do this using fastapi.
Thanks in advance!

You could profile the code to get specifics on where it’s slow, but usually the answer is the database. This looks like SQLAlchemy models. My guess is that you are lazy-loading the relationship in your crud function. This means that when you initially query, it only selects the Intent and not the IntentExample.
Then, when Pydantic tries to fill in the examples, SQLAlchemy lazy-loads the relationship for each record. This is known as the N+1 problem (query once initially then again for each example).
There are a couple ways to solve it. If you always want to include examples every time you load any Intent then you can put lazy=False in your relationship declaration. See this documentation for more info.
The other option is to tell SQLAlchemy to load the examples in your query inside crud.intent.list. You can do this by adding something like .options(joinedload(Intent.examples)) to the end of your query. See these docs for more info.

@dbanty, thank you! First option worked fine for me.

Thanks a lot for the help here @dbanty ! :clap: :bow:
Thanks for reporting back and closing the issue @Ezhvsalate :+1:


feat(rebuild_history): add list api with record limit per nexus

This PR adds rebuild list Api which will allow control plane to get rebuild history of all nexus on io engine using single rpc. Caller can set maximum number of rebuild records per nexus as well.

bors try

bors merge

bors merge

bors try

bors try

bors merge

bors merge

bors merge

bors try

bors merge

Replaced by https://github.com/openebs/mayastor/pull/1408


What is the fate of the Halogen.HTML.Events.onContextMenu event in v4.0.0?

I'm not sure yet. It's not part of the W3C spec for HTML5, but is listed in the "living standard". We haven't figured out -web libraries to covers those kinds of things.


iOS in-progress branch?

I'd be interested in an ios branch, even if it's still in-progress. 😄

@aleclarson haven't started working on iOS just yet. Still exploring the API and making many changes there, so until it stabilises I think it doesn't make any sense to start with iOS (I think I'd need 2-3 more weeks for that)

Will just close this as iOS support has landed few weeks ago.


If cannot parse the upstream response

Just pass the response through, untouched

Coverage increased (+1.3%) to 78.906% when pulling b34c2f4cf27e7cf9f38c048416e892dc26e469b1 on gmile:throw-original-exception-if-any into 3cf0e92b251f8e42c9f530403ff0520c6a445e96 on Nebo15:master.

Coverage increased (+1.3%) to 78.906% when pulling a8ae939c93cfc5c38c89d97fe128ec5fc44d72e3 on gmile:throw-original-exception-if-any into 3cf0e92b251f8e42c9f530403ff0520c6a445e96 on Nebo15:master.


Make it easy

I'd like the part of our readme about setup to be only
install package X

No extra steps.
From an OpenSource perspective... It's very important for adoption that its easy to adopt, if you dont make things easy, people wont use your stuff and you project will die.
From an InnerSource perspective... Within a company you can have a central team that "owns" libraries and pushes out PRs and deals with breaking changes, etc. But you need to ask yourself, is it easier to just "make it easy" for other teams to use your stuff (similar to the open source approach) and they wont mind updating the package themselves, "make it easy" and the dependabot updates can be merged without concern.
I think there's a Hungarian term like this that someone told me once where this one came from, but let's just "Make it Easy" :)

Closed by PR #14


feat(wash): add support for Rust wasm32-wasip2 target

Feature or Problem
Now that wasm32-wasip2 is a tier 2 target in rust, we can support it natively in wash build! So, now, when a Rust component has a wasm_target of wasm32-wasip2, we'll use the native target instead of adapting the core module/p1 module.
I considered making wasm32-wasip2 the default here instead of the unknown module, but that would be a significant breaking change for the wasmcloud.tomls that don't specify a target. I'll file a followup issue instead to make this a default after the next release of wash.
Related Issues

Release Information
wash 0.36
Consumer Impact

Testing

Unit Test(s)

Acceptance or Integration

Manual Verification

@rvolosatovs looks like https://github.com/nix-community/fenix#fenix might not have support for wasm32-wasip2 yet, or at least just isn't quite on 1.82. I ran a nix flake update locally and gave this a try, to no avail:
diff --git a/flake.nix b/flake.nix
index 6d495e83..48d3fa04 100644
--- a/flake.nix
+++ b/flake.nix
@@ -97,6 +97,7 @@
         targets.s390x-unknown-linux-gnu = false;
         targets.wasm32-unknown-unknown = false;
         targets.wasm32-wasip1 = false;
+        targets.wasm32-wasip2 = false;

         build.packages = [
           "wash-cli"

@rvolosatovs looks like https://github.com/nix-community/fenix#fenix might not have support for wasm32-wasip2 yet, or at least just isn't quite on 1.82. I ran a nix flake update locally and gave this a try, to no avail:
diff --git a/flake.nix b/flake.nix
index 6d495e83..48d3fa04 100644
--- a/flake.nix
+++ b/flake.nix
@@ -97,6 +97,7 @@
         targets.s390x-unknown-linux-gnu = false;
         targets.wasm32-unknown-unknown = false;
         targets.wasm32-wasip1 = false;
+        targets.wasm32-wasip2 = false;

         build.packages = [
           "wash-cli"

I'm working on updating Rust deps in nixify https://github.com/rvolosatovs/nixify/pull/278, meanwhile we can override fenix and rust-overlay to use more recent versions

I pushed a commit pinning nixify to rev from https://github.com/rvolosatovs/nixify/pull/278 while CI is building that PR and switched to https://github.com/oxalica/rust-overlay, since https://github.com/nix-community/fenix was last updated 3 days ago and so does not have the most recent Rust version yet

Golang component build failures are unrelated and addressed in a commit in #3298.
dog-fetcher seems to be failing with not being able to link a 0.2.0 stream type 🤔 digging

Confirmed dog-fetcher works manually with:
cargo install --path ./crates/wash-cli
wash up
cd examples/rust/components/dog-fetcher
wash build
wash app deploy wadm.yaml


Getting error when trying to write .txt file from local fs to webhdfs.

Getting the following error when trying to write a text file from local to webhdfs:
TypeError: can only concatenate str (not "bytes") to str
Hoping that I am just doing something wrong. My code is as follows:
from smart_open import open

def smart_copy(source_file, sync_file):
    with open(source_file, 'rb') as source:
        with open(sync_file, 'wb') as sync:
            for line in source:
                sync.write(line)

smart_copy('./test_file.txt', 'webhdfs://{username}@{host}:{port}/user/XXXX/smart_copy/test_file.txt')

The stack trace for the error is:
---------------------------------------------------------------------------
TypeError                                 Traceback (most recent call last)
<ipython-input-40-b63bd711d13c> in <module>
----> 1 smart_copy('./test_file.txt', 'webhdfs://XXXX@XXX.XXX.XXX.XXX:XXXXX/user/XXXX/smart_copy/test_file.txt')

<ipython-input-38-694f70cf0776> in smart_copy(source_file, sync_file)
      3     '''
      4     with open(source_file, 'rb') as source:
----> 5         with open(sync_file, 'wb') as sync:
      6             for line in source:
      7                 sync.write(line)

~/Github/tools/.venv/lib/python3.7/site-packages/smart_open/smart_open_lib.py in open(uri, mode, buffering, encoding, errors, newline, closefd, opener, ignore_ext, transport_params)
    346     except KeyError:
    347         binary_mode = mode
--> 348     binary, filename = _open_binary_stream(uri, binary_mode, transport_params)
    349     if ignore_ext:
    350         decompressed = binary

~/Github/tools/.venv/lib/python3.7/site-packages/smart_open/smart_open_lib.py in _open_binary_stream(uri, mode, transport_params)
    560         elif parsed_uri.scheme == "webhdfs":
    561             kw = _check_kwargs(smart_open_webhdfs.open, transport_params)
--> 562             return smart_open_webhdfs.open(parsed_uri.uri_path, mode, **kw), filename
    563         elif parsed_uri.scheme.startswith('http'):
    564             #

~/Github/tools/.venv/lib/python3.7/site-packages/smart_open/webhdfs.py in open(uri, mode, min_part_size)
     40         return BufferedInputBase(uri)
     41     elif mode == 'wb':
---> 42         return BufferedOutputBase(uri, min_part_size=min_part_size)
     43     else:
     44         raise NotImplementedError('webhdfs support for mode %r not implemented' % mode)

~/Github/tools/.venv/lib/python3.7/site-packages/smart_open/webhdfs.py in __init__(self, uri_path, min_part_size)
    129                                      params=payload, allow_redirects=False)
    130         if not init_response.status_code == httplib.TEMPORARY_REDIRECT:
--> 131             raise WebHdfsException(str(init_response.status_code) + "\n" + init_response.content)
    132         uri = init_response.headers['location']
    133         response = requests.put(uri, data="", headers={'content-type': 'application/octet-stream'})

TypeError: can only concatenate str (not "bytes") to str

test_file.txt is just an ascii text file. Using python 3.7.
Any guidance that you could provide would be awesome. End use case is copying files from s3 to webHDFS and back again.
Thanks!!!

Looking at this further, it looks like init_response.content on line 131 of webhdfs.py is returning a byte string instead of a string which is causing the error. I changed this to 'init_response.text' and now I am seeing the intended error message. Happy to open a PR to address this issue. Looks like it may occur again on 135 of the same module.

Hmm, how come the unit tests pass?
@andrewrobertmadsen a PR will be welcome of course. But let's include a unit test(s), to avoid such regressions in the future: something that fails now, and passes after your PR.

That’s a good question. I’m guessing the tests pass because it still raises an exception, just not the informative one that was intended. I will have to look first to verify and then I’ll submit a PR. Thanks for looking at this!

@andrewrobertmadsen Ping. Are you able to work on this? Hacktoberfest started today ;)

Can I work on this?

@sachinmukherjee Sure, go ahead

@mpenkov Hi, can I work on this parallely along with @sachinmukherjee  too?

@EinKaiser I'd prefer to avoid doubling up on a small ticket like this, so I encourage you to look through the issue list and pick another ticket. There are plenty to go around. Ping me if you can't find anything suitable.

@mpenkov How to reproduce this error?

@sachinmukherjee are you still working on this? If not, I can pick it up.

@wadleo I got struck in reproducing the error. You can take this up.

I'm having a similar issue which I think is related.
smart_open 1.9.0
python 3.6
Code:
destination = f"webhdfs://<host>:<port>/etl/test.csv"
with open(destination, 'wb') as landing_file:
    pass

Stacktrace:
  File "example.py", line 32
    with open(destination, 'wb') as landing_file:
  File "/usr/local/lib/python3.6/dist-packages/smart_open/smart_open_lib.py", line 352, in open
    binary, filename = _open_binary_stream(uri, binary_mode, transport_params)
  File "/usr/local/lib/python3.6/dist-packages/smart_open/smart_open_lib.py", line 566, in _open_binary_stream
    return smart_open_webhdfs.open(parsed_uri.uri_path, mode, **kw), filename
  File "/usr/local/lib/python3.6/dist-packages/smart_open/webhdfs.py", line 42, in open
    return BufferedOutputBase(uri, min_part_size=min_part_size)
  File "/usr/local/lib/python3.6/dist-packages/smart_open/webhdfs.py", line 131, in __init__
    raise WebHdfsException(str(init_response.status_code) + "\n" + init_response.content)
TypeError: must be str, not bytes

Just putting this here as an FYI, since the bug is still open and I think they might be related

Yeah, same issue, I dug into it and made the changes that Andrew made and they helped. I made a pull request. #382

@canada11 ups, we duplicated work a bit :) While testing I've found & fixed few other issues, take a look on description of my PR.

Awesome, yours looks better. I'll close mine so that just your pull gets merged.


ekf: Add override specifiers

Simply add the override specifier whenever possible.

Build failures PX4/Firmware side. http://ci.px4.io:8080/blue/organizations/jenkins/PX4_misc%2FFirmware-compile_mac/detail/ecl_PR-658/1/pipeline
You should get roughly the same results on linux with clang.
CC=clang CXX=clang++ make px4_sitl_default

@dagar Thanks, I had to add -Werror=suggest-override in the CMakeLists of ecl to throw the error.

@dagar Done, can you check again please?

It's not tightly integrated, but PX4Buildbot automatically creates branches off of PX4/Firmware to test PX4/ecl.
https://github.com/PX4/Firmware/branches/active

In https://github.com/PX4/Firmware/tree/ecl_PR-658 everything is now passing (except an unrelated intermittent catkin failure).

@dagar Cool, I didn't know that


Cascade breadth should be different from max(in_degree)?

My understanding from the code is that the method cascade_mesurements.get_cascade_breadth is returning the maximum in-degree in the tree. However, according to Soroush Vosoughi, Deb Roy, Sinan Aral. The spread of true and false news online. Science. 2018 this is not the case.
For example, in the figure below, the max in-degree is 3, but the max-breadth is 4:

We've updated the implementation of cascade_breadth in the most recent update.  Now, breadth should return as the maximum number of nodes at the same depth.


Unable to upgrade to beta 7 with brew

Hi,
I tried to upgrade to the latest beta and got the issue:

Fixed.


Publish cellular signal strength metrics to apps

Provided that device has at least one cellular modem visible to EVE (i.e. not assigned directly to an application),
JSON-formatted WWAN metrics are made available to all applications on the /eve/v1/wwan-metrics.json endpoint.
This includes packets counters as recorded by modems as well as cellular signal strength info.
Additionally, as a separate commit, cellular metrics were added to RadioStatus proto message, published by EVE to "/api/v1/radio" endpoint of the Local Profile Server (LPS).

@eriknordmark I'm also considering to create a meta-data server endpoint with ALL LTE-related information, i.e. not just metrics, but also info about the modem hardware, firmware, SIM cards, etc. - just like what we publish to LPS under /api/v1/radio
So maybe instead of /eve/v1/wwan-metrics.json there could be something like /eve/v1/radio.json with status info + metrics, which would make the API similar to that of LPS. WDYT?

@eriknordmark I'm also considering to create a meta-data server endpoint with ALL LTE-related information, i.e. not just metrics, but also info about the modem hardware, firmware, SIM cards, etc. - just like what we publish to LPS under /api/v1/radio So maybe instead of /eve/v1/wwan-metrics.json, there could be something like /eve/v1/radio.json with status info + metrics (cellular, later also WiFi), which would make the API similar to that of LPS. WDYT?

If we think the metrics (whether LTE or WiFi) will see significantly more use than the info then maybe we should have /eve/v1/radio/{info,metrics}.json. But it makes sense to look at how cloud-init (whether AWS or openstack) tends to structure the URLs they use on 169.254

If we think the metrics (whether LTE or WiFi) will see significantly more use than the info then maybe we should have /eve/v1/radio/{info,metrics}.json. But it makes sense to look at how cloud-init (whether AWS or openstack) tends to structure the URLs they use on 169.254

It seems that your suggestion is in line with the AWS approach of structuring URLs, so I'm going to make the changes and mark the PR as draft for the time being.

@eriknordmark I have split the metrics and status info into separate metadata server endpoints.


Also transform height / width to block-size / inline-size

This plugin is awesome!
Could it get rules for these transforms, too?
height → block-size
min-height → min-block-size
max-height → max-block-size
width → inline-size
min-width → min-inline-size
max-width → max-inline-size

I guess the same goes for border properties: https://drafts.csswg.org/css-logical/#border-properties

I guess the same goes for border properties: https://drafts.csswg.org/css-logical/#border-properties

@johan  i'll add them in over the weekend. I'll go and check the specs out too incase I'm missing anything else.

@johan  i'll add them in over the weekend. I'll go and check the specs out too incase I'm missing anything else.

If you want to be super kind to mongolian folk, you might also change so the logical directive gets prepended to inset / margin / padding rules for everything but the values.length === 1 case. 🙂

If you want to be super kind to mongolian folk, you might also change so the logical directive gets prepended to inset / margin / padding rules for everything but the values.length === 1 case. 🙂

@johan  Added in 3.20 which is now available sorry for the delay


bump packages for 0.72

Changelog: [Internal]
Publishing to check CI if bumping and aligning in the same commit will work, since these new versions are not available on npm yet, but maybe our new monorepo setup will resolve this

@hoxyq do you mean for 0.73? 🤔


Revert "[ZK filter] Add per-opcode decoder error metrics (#31138)"

Commit Message: Revert "[ZK filter] Add per-opcode decoder error metrics (#31138)"
Additional Description: This is the prerequisite of reverting https://github.com/envoyproxy/envoy/pull/30438 in order to fix the ZK proxy filter "Uncaught Exception" issue.
Risk Level: Low
Testing: Unit test
Docs Changes: Revert doc changes in https://github.com/envoyproxy/envoy/pull/31138
Release Notes: Revert release notes in https://github.com/envoyproxy/envoy/pull/31138
Platform Specific Features: N/A

/retest

/lgtm api


Add rtgtools

PR checklist
Addresses https://github.com/nf-core/raredisease/issues/250

[ ] This comment contains a description of changes (with reason).
[ ] If you've fixed a bug or added code that should be tested, add tests!
[ ] If you've added a new tool - have you followed the pipeline conventions in the contribution docs
[ ] If necessary, also make a PR on the nf-core/raredisease branch on the nf-core/test-datasets repository.
[ ] Make sure your code lints (nf-core lint).
[ ] Ensure the test suite passes (nextflow run . -profile test,docker --outdir <OUTDIR>).
[ ] Ensure the test suite passes (nextflow run . -profile test_one_sample,docker --outdir <OUTDIR>).
[ ] Usage Documentation in docs/usage.md is updated.
[ ] Output Documentation in docs/output.md is updated.
[ ] CHANGELOG.md is updated.
[ ] README.md is updated (including new tool citations and authors/contributors).

Could you also update the documentation on how to use this


do not merge - test comment PR

Apollo Federation Subgraph Compatibility Results

title: Federation-compatible subgraph implementations
hide:

navigation

The following open-source GraphQL server libraries and other solutions support acting as a subgraph in a federated supergraph.


Implement control to NOT overflow the variable dividend and dividend_uint256

Description
From code:
func FUNCTION{syscall_ptr: felt*, pedersen_ptr: HashBuiltin*, range_check_ptr}(
        token_total_deposited: Uint256, total_amount: felt, address_token_amount: felt
    ) -> (amount: Uint256) {
        let dividend = total_amount * address_token_amount;
        let dividend_uint256 = Uint256(low=dividend, high=0);

Problem: This will result in a range_check on dividend and can overflow.
Solution: Need to make sure the product is not too large (an doesn't overflow)
Acceptance Criteria

[ ] Product  of total_amount * address_token_amount is not too large
[ ] Can not do an overflow of the variable.

A reasonable solution could be to convert felts to Uint256 before to operate the product.
func FUNCTION{syscall_ptr: felt*, pedersen_ptr: HashBuiltin*, range_check_ptr}(
        token_total_deposited: Uint256, total_amount: felt, address_token_amount: felt
    ) -> (amount: Uint256) {
        total_amount_uint256 = Uint256(low=total_amount, high=0);
        address_token_amount_uint256 = Uint256(low=address_token_amount, high=0);
        let dividend_uint256 = SafeUint256.mul(total_amount_uint256, address_token_amount_uint256);

@tekkac do you think it makes the job?

Not relevant anymore


new submission: binjago

I've been writing a plugin that to assist with CTF's (and other general static analysis tasks) that I figure I'd submit in hope that it can also help someone else. It's more of a suite of plugins that I use personally, but may also be useful to others. I plan to continue to add more and more functionality as I encounter problems that I feel can be solved through static analysis using BN. Currently this plugin contains the following:

a ROP gadget locator for x86 and x86-64 (soon to support multiple archs hopefully by using BN IL)
a plugin that finds and applies comments on calls to certain libc/OS API functions to help enumerate function args (using BN IL)
a plugin that finds x86 and ARM function prologues in firmware flat files. (I hope to build this out to support enumeration of many file header signatures (similar to binwalk))
a plugin that finds direct and indirect recursion using BN IL

many more to come..
Here's the link: https://github.com/zznop/binjago

I'm assuming it's pronounced like ninjago? :-P

Also, looks good. Minor suggestion: maybe add the description from here into the plugin.json so there is a better description in the repo readme? I'll pull it as soon as I get my laptop out either way.

Yes, pronounced liked Ninjago (I Dad). And thanks, I plan on building out this framework to the point where it needs its own documentation. In the meantime though I’ll be sure to make the README more descriptive and include some screenshots.


automate split valid gait cycle

[x] Treadmill auto split with percentage 1435ffd
[ ] Walking auto split algorithm


Crash found. - SplashActivity.kt line 44 (5af2da8a11e9fa0aa5f69268)

This is test body.\n\n  \n\n  ### Application Info:\n\n  Application name: Green Build, version 1.1.1 (5) on android

Test issue for firebase crashalytics.


"Error in function call"

I'm running into problems when attempting to use the module:
Error: Error in function call

  on .terraform/modules/postgresql-db/GoogleCloudPlatform-terraform-google-sql-db-9c7727a/modules/postgresql/main.tf line 22, in locals:
  22:     disabled = "${map()}"

Call to function "map" failed: map requires an even number of two or more
arguments, got 0.

See hashicorp/terraform#20372 for more info

I see #36 is pending with the necessary changes, but this is broken as it stands until that PR is merged

@aodj Can you try using one of the submodules instead?

I was only using submodules:
For example:
module "postgresql-db" {
  #   source           = "github.com/GoogleCloudPlatform/terraform-google-sql-db//modules/postgresql?ref=v1.2.0"
  source           = "GoogleCloudPlatform/sql-db/google//modules/postgresql"
  version          = "1.2.0"
  project_id       = "${var.project}"
  region           = "${var.region}"
  zone             = "a"
...

Ok. I assume you're using Terraform v0.12?
Terraform 0.12 is not yet supported by this module.


[RFC][Java] Implement a highly optimized String compressioner

Is your feature request related to a problem? Please describe.
Currently utf8 encoding in jdk are not efficient enough and write it to fury MemoryBuffer needs an extra copy since those encoder return a byte array:

java.lang.String#encodeUTF8/java.lang.String#encodeUTF8_UTF16
sun.nio.cs.UTF_8.Encoder#encodeArrayLoop

We need a highly optimized encoder for fury to avoid the cost of string serialization.
Describe the solution you'd like

Detect latin length first using superword, then encode those chars by latin, encode remaining chars using utf8
Latin length encoded in coder too, remaining utf8 chars length encoded using varint.

hello,I am new in there,please assign me,thanks~


Update to ophyd-async 0.6.0

Fixes #794
Instructions to reviewer on how to test:

Do thing x
Confirm thing y happens

Checks for reviewer

[ ] Would the PR title make sense to a scientist on a set of release notes
[ ] If a new device has been added does it follow the standards
[ ] If changing the API for a pre-existing device, ensure that any beamlines using this device have updated their Bluesky plans accordingly
[ ] Have the connection tests for the relevant beamline(s) been run via dodal connect ${BEAMLINE}

Given the tests are on 3.10 only and mention timeouts I'm going to bet that they're to do with TimeoutError and asyncio.TimeoutError being different in 3.10. Probably caused by https://github.com/bluesky/ophyd-async/pull/573

TimeoutError and asyncio.TimeoutError being different in 3.10. Probably caused by bluesky/ophyd-async#573

For now I've imported TimeoutError from asyncio: in 3.10 this will be the asyncio.TimeoutError, in >3.10 this returns the builting TimeoutError. Either TypeChecking will shout at us or there's this ticket to remove the import after 3.10


⚠ Jurnal has degraded performance

In 17a6c39, Jurnal (https://jurnal.unmer.ac.id) experienced degraded performance:

HTTP code: 200
Response time: 16953 ms

Resolved: Jurnal performance has improved in 4f14cfd.


Cocoapods support, changed project structure and added all pods requirements

Restructured the project to fit default cocoapods default structure for libraries.
Kept the current example in sample folder.
Moved source code to src directory
Added project dependancies, license, and all necessary details to the podspec file

@salah-ghanim can you resolve the conflicts?

Closing for now. Let me know if you would like to revisit this.
:sweat_smile:

hey @dkhamsing sorry that I didn't respond earlier. I've been meaning to fix the conflict for a while.
Its just been a while since I did these changes, and the conflict size is quit big.
Anyway, I can get them done this weekend.

Oh cool, will reopen

@dkhamsing
Once you merge with master you can modify the repo's url inside the podspec file to point to your rep
so
  s.source = { :git => "https://github.com/salah-ghanim/FHSTwitterEngine.git", :tag => s.version.to_s }

should become
  s.source = { :git => "https://github.com/fhsjaagshs/FHSTwitterEngine.git", :tag => s.version.to_s }

PS also double check the tags/versions

Will take a look thank you

Note update_with_media deprecated #92


57 graph blocks

Adds the "line" creation block and "plot" block as discussed in #57

@dube1503
it seems to be working pretty well on my machine. There is something a little odd with the option 'none'. After you make several variables it seems to appear at the top and bottom of the options. I'm not sure if that is a big enough deal to need to be fixed before we merge.
That being said can you move graphs up near shapes on the toolbox before we add this to the development branch. I want to keep 'our' blocks together.

Found the problem with the 'none' options being appended with more variable creations and was able to fix. Also moved to just under the shapes category.
I was attempting to create an onchange function that would reset the Plot blocks current variable selection if the selection was no longer a line variable but was unsuccessful in getting it to update the shapes dropdown menu selection. Left the code commented out as the plot is functional and it is more of what i would classify as UX than actual usability problem.


gx use <repo>

Alright, so heres something moderately interesting.
I want to be able to have a gx repo (see the readme, nobody uses them yet) full of all my dependencies, that I keep updated, and run all sorts of checks on, etc.
Then, I want to be able to just tell my package to use deps from it. When it does this, it should mark the exact hash of the repo at the point its using it. From there, I can easily update all the deps in the repo at once. This also opens the door to having less strict versioning that i'm okay with. If the deps in your repo get updated, then your package could automatically use the latest. This is a strictly better model because you are explicitly trusting the source of the packages (via the configured repo)
I'm gonna keep thinking about this, and fill it out with more info later. Comments and questions welcome.

moving my comments from #160 here for deduplication:
having worked with tool now for a month or so, as a user - one thing that stands out is that I don't have a convenient way to decide which versions of the dependancies I want: the package owner has to do a release with a named version (sure I can publish custom versions on my own, but it's freaking hard to then navigate the tree and republish all the parents that would be required to depend on those customs cuts, and their parents etc.).  If the dependency tree is deep and wide (as we see in libp2p projects) this results in a lot of constraints between compatible versions.  Recently, I've been building the un-gxified version of my project without any dependency management, and its more reliable in the sense that I can usually get it to build, whereas if I add a dep or update something i'm in deep trouble with gx.  One idea I have is that there could be a command to "freeze" and "update" deps.
In this model, when you "freeze", it cuts a brand new version for each dependency - exactly as it is at that moment in your $GOPATH - by following all the package.jsons from the top down, recursively to the bottom (lib with no deps using gx), and then back from leaves to root.  As you walk back up, the deps need to each be published for this to work - but that seems doable, and if you have to make actual changes in the files that imply causality. Maybe it can be avoided if you -f publish and don't permanently mess with the package.json files.  Such changes could maybe be undone afterwards in order to avoid mass chaos in your $GOPATH.
The payoff is, I as a user, can adjust my regular un-rewritten libs the way I want for my deps, caring only about the golang compatibility of interfaces, not the full version locking stuff, then run a single command to freeze them, or unfreeze and refreeze as required without any worries about when the package owners/maintainers cut releases. I don't care about interdependencies at all - and I don't need a crummy vendor directory with a full copy of everything and can rely on ipfs to deduplicate content. Every release can be a custom release.
One possible catch is that, as a user, I have to run ipfs and take responsibility for making sure my custom versions of code are well replicated for the team I am working with - which I do anyway.

@jvsteiner Thanks a lot for your input! I think we're pretty close to being on the same page here.
Could you provide maybe an example or two of the workflow (in terms of hypothetical commands to run) that you think would be good?
Semi-related, have you seen gx-workspace? The docs in the readme are out of date, but the tool allows you to fairly easily update a dependency throughout an entire tree of gx deps (it handles all the gx updates and commits and publishes). Currently it iterates through the tree, updates things, runs tests, and prompts the user if they want to stop and investigate or continue to the next step. If that tooling was really fast and reliable, would that solve the issues you run into?

@whyrusleeping - I took a look at gx-workspace. I didn't manage to get it to work right off the bat, but I'm going to spend some more time investigating it.  It does look like it aims to solve the same problem domain, and if it were fast and reliable, I agree it would be really useful, and would solve a number of issues I've had.
That said, the approach I was thinking about above is slightly different one, and I'm still thinking what I describe might be useful in other situations. Perhaps, it could be a different command under gx-workspace even.
As I understand it, gx-workspace attempts to resolve the duplicates in dependancies, so in the end you get a top level package.json file that refers to released versions of your deps.
My proposal is that instead of trying to rely on released versions of packages, the tool looks in the regular directories for each of the packages, runs gx publish (-f) then takes the hash and uses it everywhere that dependency is used.  In case the dependency repositories happen to be on released commits, then the hashed used will end up being released hashes, but it's not required.  In fact, one would be free to modify a dependency, commit on a local branch, and the resulting package would use that instead.  So there could be custom, non-official releases baked in, which wouldn't be replicated anywhere except the users machine, at least until someone else installed the package.json file.


PEP 585 "callable" not supported?

Hi everyone,
because beartype told me so in a BeartypeDecorHintPep585DeprecationWarning, I changed my type hint from typing.Callable to the generic "callable". However, this now returns the following error:
BeartypeDecorHintNonpepException: @beartyped Model.init() parameter "_Y" type hint  either PEP-noncompliant or currently unsupported by @beartype.
Is the generic type hint unsupported at the moment, or did I do something wrong?
Edit: This problem got solved by using the beartype.typing module, however I would rather prefer being able to use the PEP 585 syntax.

Hi, Max! Everybody say "Hi, Max!", please. :teacher:
Okay. So, let's see if we can't get you sorted here...

I changed my type hint from typing.Callable to the generic callable.

Ah-ha. There's your problem. Python is confusing. We can all admit that. I do to my wife every evening. Sadly, she just rolls her eyes and tells me to get back to work.
What's happening here is that the callable() builtin is actually a function rather than a type in Python. callable() returns True if and only if the passed object is callable (i.e., can be called like a function or method, which obviously includes functions and methods but also classes defining the __call__() dunder method):
$ python3
>>> type(callable)
<class 'builtin_function_or_method'>
>>> callable(callable)
True
>>> callable("I swear this string is callable. You gotta believe me!")
False

Clearly, callable() is not a valid type hint. Right? That's what @beartype is awkwardly complaining about there.
Instead, you want the collections.abc.Callable abstract base class (ABC). If you don't care about backward compatibility with Python 3.7 or 3.8, ...you probably don't @beartype will happily accept collections.abc.Callable[...] type hints under Python ≥ 3.9:
$ python3.9
>>> from beartype import beartype
>>> from collections.abc import Callable
>>> def init(_Y: Callable[[], bool]) -> bool:
...        return _Y()
>>> init(bool)
False

Or you can simply pass collections.abc.Callable unsubscripted if your Model.init() method can permissively accept any possible callable. In that case, collections.abc.Callable is semantic shorthand for the more explicit collections.abc.Callable[..., typing.Any] type hint. Additionally, you can do this under any Python version – including Python 3.7 and 3.8:
$ python3.8
>>> from beartype import beartype
>>> from collections.abc import Callable
>>> def init(_Y: Callable) -> bool:
...        return _Y()
>>> init(bool)
False

Does that answer your question?
One Last Thing I Gotta Say
Oh – and please note that @beartype doesn't yet support deep type-checking of Callable[...] type hints. We do shallowly type-check that the passed or returned object is actually callable... but that's it for the moment. With any luck (and ample funding, please Money Gods ample funding), we'll support deep type-checking of Callable[...] type hints by the end of the year.
Thanks for your profound interest in @beartype. May the QA be with you always.

Ah, I misread the PEP 585 wrongly and thought that collections.abc.Callable is deprecated as well as typing.Callable when it was just the latter. Thank you very much for your detailed help and explanation, and thank you even more for beartype.

Oh, you're most welcome. And thanks so much for the kind words! @beartype is here for the community; so, just let us know if you hit any further snags. :smiley_cat: