Add support for hardware entropy source on x86-64.

This allows no_std builds to use the rdrand instruction on x86
to generate a random seed for the random number generators.
An example invocation to enable it be:
cargo +nightly run --example fib --features alloc --features unstable --features hardware-rng --no-default-features

Is this something the maintainers would be interested in merging or out of scope for the project (we're using this patch for a project so if I could merge it upstream into proptest I don't have to maintain a fork anymore)?


[hotfix] Fix modification conflict between FLINK-35465 and FLINK-35359

What is the purpose of the change
As title said, fix the compile error cause by modification conflict between FLINK-35465 and FLINK-35359.
Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving):(no)
The serializers: (no)
The runtime per-record code paths (performance sensitive): (no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: (no)
The S3 file system connector: (no)

Documentation

Does this pull request introduce a new feature?  (no)

The change is trivial. Will merge it right now to unblock others.


Visual artifacts / Packet loss even with 5 GHz Wi-Fi

Since a week ago I'm getting visual artifacts every few seconds and packet loss. I'm using a 5 GHz Wi-Fi. I checked for collisions, but there is no jamming. I play close to the router (usually two meters, but I also tried less than one meter). Things I tried:
-Decreasing bitrate
-Increasing buffer
-Using H.264 instead of H.265
-Decreasing resolution
-Updating NVIDIA drivers to the latest version. ALVR worked fine when I had a GTX 970, but now I have a RTX 2080. I wonder if it's a problem with the new GPU.
Any ideas? Thanks in advace.

Is your router connected to your PC with a Ethernet patch cable? cat 5 or 6 works well.
Also check to see if the 5 ghz channel you're using does not have other router traffic on it.
Rarely I get a few seconds of artifact/packet loss and my router is the only device on the channel I use. I attribute that to some random strong RF interference in the area
My settings
H.265
55 Mbps
1183Kb buffer
3072x1536 resolution

You should completely delete steam vr and reinstalling all software. Its resolve this problem for me.
Really strange bug.

wow, now its happen again. Every 6 seconds this https://clip2net.com/clip/m11339/4dd2b-clip-42kb.jpg?nocache=1

can't able to fix it, i think its client problem on the smartphone side


[HUDI-5628] Fixing log record reader scan V2 config name

Change Logs
We introduced a new way to scan log blocks in LogRecordReader and have named it as "hoodie.log.record.reader.use.scanV2". Fixing the config name to be elegant: "hoodie.optimized.log.blocks.scan.enable". Metadata config also has an entry for the same. So, fixing that as well.
Impact
Good/Understandable config names.
Risk level (write none, low medium or high below)
no.
Documentation Update
Config docs will automatically be generated during release.
Contributor's checklist

[ ] Read through contributor's guide
[ ] Change Logs and Impact were stated clearly
[ ] Adequate tests were added if applicable
[ ] CI passed

@hudi-bot run azure

CI failed due to known flaky tests.

CI failed due to known flaky tests.


Fix error of __list_find

The node on the linked list should follow the ordering by its key. However, the function list_insert doesn't actually do this because of the wrong implementation of __list_find.
There are three main fixes in this patch. First, once we should do synchronization, we have to iterate the list again but not return from the function. Second, the while loop should iterate until the last node but not the second last one. Finally,
under the normal situation that the tail node with key UINTPTR_MAX should not be deleted (unless the end of the program), some codes are never executed which can be removed.

I would expect the following comments:

On a CAS failure, the search function, "__list_find",  will simply have to
go backwards in the list until an unmarked element is found from which
he search in increasing key order can be started.

For the implementation to be correct, the predecessor pointers only
have to fulfill that any item always has a path back to the head of the
list. When a new item is inserted into the list, the predecessor pointer
of the successor is set with an atomic store to point to the new element.
Likewise, when an item is removed, the predecessor pointer of the
successor item is updated to skip the removed item. This suffices to
maintain the invariant, but through long sequences of concurrent
insertions and deletions, backwards pointers can become imprecise
in that they skip many items that are actually in the list.

My implementation was a functional rewriting of paper A more Pragmatic Implementation of the Lock-free, Ordered, Linked List. You can check its implementations and benchmark programs: lockfree-linked-list.

Thanks for the information. I changed the comment according to yours.


Until not in scope

Running the following specification
import quickstrom;

let ~proposition = false until true;

check proposition with * when loaded?;

with the following command
docker run --rm -v $PWD:/spec quickstrom/quickstrom:0.5.0 quickstrom -I/spec check spec https://www.google.com

produces the following error
Check was aborted:

/spec/spec.strom:3:25: Variable not in scope:
  _until_

Adding an import ltl;
produces the following error
Check was aborted:

/nix/store/xradz0aav0ijajw91x1vqfqsprgipfhx-specstrom/share/ulib/ltl.strom:1:1: syntax already declared:

Thanks for the nice bug report! Hoping I can find a moment to fix this soon. @liamoc might have some clue as to why this happens?


Fix user-resizable embedded window in Reaper Mac

This will inhibit applying the auto-resize mask until
the initial size has been set in the PuglView. Initially,
DPF would set this size to (1, 1).
It's a very simple solution for #198, too simple maybe.
It needs to verify if it hasn't broken something else.

Looks fine, being a sorta hack and all.
Thanks


Show the amount of snapshots

When viewing the list of snapshots I'd like to see the total amount of them too.

Codecov Report

Merging #1304 into master will decrease coverage by 5.68%.
The diff coverage is 42.85%.

@@            Coverage Diff             @@
##           master    #1304      +/-   ##
==========================================
- Coverage   52.14%   46.46%   -5.69%
==========================================
  Files         134      134
  Lines       13043    13056      +13
==========================================
- Hits         6801     6066     -735
- Misses       5410     6217     +807
+ Partials      832      773      -59

Impacted Files
Coverage Δ

cmd/restic/cmd_snapshots.go
31.66% <0%> (-0.54%)
:arrow_down:

cmd/restic/table.go
50% <50%> (-2.64%)
:arrow_down:

internal/backend/b2/b2.go
0% <0%> (-79.93%)
:arrow_down:

internal/backend/azure/azure.go
0% <0%> (-75.35%)
:arrow_down:

internal/backend/swift/swift.go
0% <0%> (-73.9%)
:arrow_down:

internal/backend/gs/gs.go
0% <0%> (-65.6%)
:arrow_down:

internal/backend/swift/config.go
34.37% <0%> (-56.25%)
:arrow_down:

internal/checker/checker.go
68.19% <0%> (-3.84%)
:arrow_down:

internal/backend/s3/s3.go
59.87% <0%> (+1.27%)
: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 3afd974...2f10e25. Read the comment docs.


[UX] Register view enhancement | Round 2

Describe the enhancement
|     |     |
Implementation
Priority 1

[x] Update the spacing between the HH member and the ID to match the design
[x] Header on scroll

[x] When the user scrolls up, the header should contain the HH name on the Household profile.
[x] When the user scrolls down, the header should expand back to show the HH name and Community
[ ] both headers on scroll have a dropdown shadow

Priority 2

[ ] Update the following items on the patient register component

[x] Update the patient name color to match the designs
[ ] The HH linked to the patient is not included
[ ] Remove the vertical dividers that are not part of the designs
[ ] Update the margin left and right to match the designs

[ ] Last HH member list

[ ] The container of a HH member has a top-bottom padding of 24px
[ ] The last HH member in the members' list should always be above the Add member floating button as shown in the attached design. This is to allow the user to be able to click any actions related to patient

Priority 3

[x] Pagination

[x] The pagination row should be part of the list and not always on the bottom of the screen.
[x] Pagination should show when the user scrolls to the end of the screen

[x] Floating button on scroll

[x] When the user scrolls up, the floating button should collapse into an only icon
[x] When the user scrolls down, the floating button should return to the full button

Links to the designs for attached issues:
Implementation
Priority 1

[ ] Update the spacing between the HH member and the ID to match the design - link
[ ] Header on scroll - link

[ ] When the user scrolls up, the header should contain the HH name of the Household profile. - link
[ ] When the user scrolls down, the header should expand back to show the HH name and Community - link
[ ] both headers on scroll have a dropdown shadow

Priority 2

[ ] Update the following items on the patient register component - link

[ ] Update the patient name color to match the designs
[ ] The HH linked to the patient is not included
[ ] Remove the vertical dividers that are not part of the designs
[ ] Update the margin left and right to match the designs

[ ] Last HH member list

[ ] The container of a HH member has a top-bottom padding of 24px - link
[ ] The last HH member in the members' list should always be above the Add member floating button as shown in the attached design. This is to allow the user to be able to click any actions related to patient

Priority 3

[ ] Pagination - link

[ ] The pagination row should be part of the list and not always on the bottom of the screen.
[ ] Pagination should show when the user scrolls to the end of the screen

[ ] Floating button on scroll - link

[ ] When the user scrolls up, the floating button should collapse into an only icon
[ ] When the user scrolls down, the floating button should return to the full button

cc: @dubdabasoduba

@ellykits I am reopening this since it seems like some things have not been checked. Feel free to close it this was intentional.

@ellykits I am reopening this since it seems like some things have not been checked. Feel free to close it this was intentional.

This is accurate and needs to be reassigned for completion

Pointing out some specs for HH Member component here as well:

The different font, color, spacing and padding properties are defined here

Task button properties (must follow same font/slightly smaller sizes and weights so the labels can fit as much as possible)
I possible technically, Truncating with ellipses should start when the label can't fit in a given text width since in some cases we may have labels that can fit in the task button with more characters than the defined.

Task button guide (for devs and PMs that define the task names)

How different task and patient names show on the HH member component

@HenryRae Can you review the latest apk to verify the applied UI enhancements/fixes? We can create new issues if there are more concerns and close this one.


Rename workflow

Current workflows don't actually create a release, they just bump
the tag version (based on the release/* label on PR). Thus, call it
a tag and not a release, because it becomes misleading.
Fix: remove github_token input variable from action-release-label
action

Closing this in favor of #51


RFE: team_number does not yet support the optional team argument

Avg response time

Request for Enhancement (RFE)

OpenCoarrays Version: 2.0.0
Fortran Compiler: GNU Fortran (GCC) 8.0.1 20180225 (experimental)
C compiler used for building lib: gcc (GCC) 8.0.1 20180225 (experimental)
Installation method: install.sh
Output of uname -a: Linux 3.13.0-144-generic #193-Ubuntu SMP Thu Mar 15 17:03:53 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
MPI library being used: MPICH 3.2.1
Machine architecture and number of physical cores: laptop computer, 4 cores
Version of CMake: 3.4.0

Observed Behavior
With OpenCoarrays 2.0.0, the Fortran 2018 intrinsic function team_number does not yet support the optional team argument. This should be a known issue because the runtime does give an appropriate runtime error message: Fortran runtime error on image 1: team_number does not yet support the optional team argument.  MainTeam **************************************
!************************************************
!
! split the 15 images of the initial team into 3 child teams consisting of 5 images each:
  if (this_image() <= 5) then
    intTeamNumber = 1
  else if (this_image() >= 6 .and. this_image() <= 10) then
    intTeamNumber = 2
  else if (this_image() >= 11) then
    intTeamNumber = 3
  end if
  !
form team (intTeamNumber, MainTeam) ! this creates the 3 child teams in MainTeam
!
change team (MainTeam)
!
! important: the following gets executed on the images of all the 3 newly created child teams:
!
!************************************************
! SubTeam ***************************************
!************************************************
!
! split the 5 images of the MainTeam's child teams into two distinct teams resp.:
  if (this_image() < 3) then
    intTeamNumber = 1
  else
    intTeamNumber = 2
  end if
!
form team (intTeamNumber, SubTeam) ! this generates 6 teams (2 new sub teams in the 3 main teams resp.)
                                   ! within the change team (MainTeam) construct
change team (SubTeam)
!
SubTeam_select: select case (team_number())
!
case (1) SubTeam_select
  ! codes for child team 1 of SubTeam:
  write(*,*) 'image number: ', this_image(), ' of team number: ', team_number(), &
             ' in SubTeam, of MainTeam''s child team number:', team_number(MainTeam)
              !Fortran runtime error on image 1: team_number does not yet support the optional team argument
  !
!*******************
case (2) SubTeam_select
  ! codes for child team 2 of SubTeam:
  write(*,*) 'image number: ', this_image(), ' of team number: ', team_number(), &
             ' in SubTeam, of MainTeam''s child team number:', team_number(MainTeam)
              !Fortran runtime error on image 1: team_number does not yet support the optional team argument
!
end select SubTeam_select
!
end team !(SubTeam)
!
!*************
!*************
!*************
!
end team !(MainTeam)
!
end program Main

Expected Behavior
Just to give an indication of the importance of the optional team argument:
As the above example program can already show (it does not fail if compiled with team_number not using the optional team argument), if we execute the same form team statement on all images within a change team construct (that comprises a set of teams), that single form team statement does not only form one set of new teams but instead can form several sets of new teams: For each team in MainTeam a new set of teams is created in SubTeam; Since MainTeam comprises 3 teams, and the form team statement in SubTeam does form 2 new teams, that single form team statement does actually form 6 new teams.
With such nested teams, the team argument should allow to use the team_number intrinsic to get information about the nesting and the belonging of the images of a nested team with respect to their parent team. This could be helpful for the development of new kinds of parallel algorithms later on.

@MichaelSiehl Thanks for submitting this issue and especially for the code example. If you have any interest, the best way to get this feature added is to dive in.  Going forward, OpenCoarrays is going to be mostly a community effort with only small amounts of related project funding.  In case it helps, I have long considered the possibility of replacing some of the C code in OpenCoarrays with Fortran code as a way to increase the likelihood that the Fortran community will contribute code to OpenCoarrays.  As a simple example of what this would look like, take a look at the partial implementation of this_image() in Fortran inside the opencoarrays module:
  ! Return the image number (MPI rank + 1)
  function this_image()  result(image_num)
#ifdef MPI_WORKING_MODULE
    use mpi, only : MPI_Comm_rank
#endif
    integer(c_int) :: image_num,ierr
   !image_num = opencoarrays_this_image(unused)
    call MPI_Comm_rank(CAF_COMM_WORLD,image_num,ierr)
    if (ierr/=0) call error_stop
    image_num = image_num + 1
  end function

The commented line makes a call to the C implementation of this_image().  It's commented because I had originally planned for the above procedure to wrap C, but had trouble getting that to work and so decided that the function is suffiiciently simple that I just wrote it in Fortran rather than wrapping it.  A similar approach could be tried with team_number().  If we go this route and also give the procedure the bind(C) attribute, then some of the C procedures could eventually be replaced with Fortran procedures without any impact on user code.  Would this make it more likely that you would consider implementing the requested feature?

Hi Damian,
the ability to use Fortran for implementing new features sounds great and
yes, it could make it more likely to try implementing features by myself
(without any guaranty of success yet ;-). Still, the team_number intrinsic
function (as well as num_images, which does not support team variables at
compile time yet) is not on top of my wishing list of missing features. (We
can circumvent the missing optional team argument easily by using a local
variable to store team values – since using any of the team-related
statements has no impact to the values of local variables). There are
probably other missing features (e.g. allocatable derived type coarrays at
the team level) that I would consider to be more important yet, but still
NO single missing feature that does prevent from highly sophisticated use
of the Fortran 2018 team features with OpenCoarrays yet.
Further, and considering that upcoming ifort 19 (beta yet) will not already
support Fortran 2018 team features, I do suppose that OpenCoarrays will
continue stay way ahead for quite a long time.
Furthermore, right now I am full of enthusiasm about the working team
features and will prefer to focus on the working features and do further
research using them. I did already succeed with encapsulating F18 team
features into a (yet simple) customized create_team procedure (similar to a
customized synchronization procedure). At this early stage of testing, I
can not fully tell what the opportunities of this will be, but do still
believe that we can easily increase the possibilities of the basic (but
powerful) team features of Fortran 2018 using current OpenCoarrays already.
If things work out well, I will give working example codes in the coming
weeks and month.
My Best Regards
2018-04-25 23:32 GMT+02:00 Damian Rouson<EMAIL_ADDRESS>
@MichaelSiehl https://github.com/MichaelSiehl Thanks for submitting
this issue and especially for the code example. If you have any interest,
the best way to get this feature added is to dive in. Going forward,
OpenCoarrays is going to be mostly a community effort with only small
amounts of related project funding. In case it helps, I have long
considered the possibility of replacing some of the C code in OpenCoarrays
with Fortran code as a way to increase the likelihood that the Fortran
community will contribute code to OpenCoarrays. As a simple example of what
this would look like, take a look at the partial implementation of
this_image()
https://github.com/sourceryinstitute/OpenCoarrays/blob/master/src/extensions/opencoarrays.F90#L760
in Fortran inside the opencoarrays module
https://github.com/sourceryinstitute/OpenCoarrays/blob/master/src/extensions/opencoarrays.F90
:
! Return the image number (MPI rank + 1)
function this_image()  result(image_num)
#ifdef MPI_WORKING_MODULE
use mpi, only : MPI_Comm_rank
#endif
integer(c_int) :: image_num,ierr
!image_num = opencoarrays_this_image(unused)
call MPI_Comm_rank(CAF_COMM_WORLD,image_num,ierr)
if (ierr/=0) call error_stop
image_num = image_num + 1
end function
The commented line makes a call to the C implementation of this_image().
It's commented because I had originally planned for the above procedure to
wrap C, but had trouble getting that to work and so decided that the
function is suffiiciently simple that I just wrote it in Fortran rather
than wrapping it. A similar approach could be tried with team_number().
If we go this route and also give the procedure the bind(C) attribute,
then some of the C procedures could eventually be replaced with Fortran
procedures without any impact on user code. Would this make it more likely
that you would consider implementing the requested feature?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/sourceryinstitute/OpenCoarrays/issues/524#issuecomment-384441118,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AQUQ_F1cgIoQ0WB4djUXmBxvMqCXBPziks5tsOtjgaJpZM4Tigxr
.

Fixed in #631 and in release 2.5.0. Thanks @nathanweeks for implementing the fix!
And thanks to @MichaelSiehl for reporting the bug!


several custom functions for data preprocessing

create custom preprocess function

initial commit

No conflict with the base branch. Okay to merge.


Not all NA should be converted to <minCellCount

how do we want to deal with this issue? @edward-burn @nmercadeb

how about only converting to <minCellCount if estimate_type is numeric, integer, percentage or proportion?


Team colours swapped on panels?

Is that repeatable? Does it happen every time?
What needs to happen to break the bottom panel?
Can you send me the replay?
I have ideas how that could be fixed. But I would require a reliable way to test this.

Yeah, im not sure. It was happening on the twitch channel and I noticed it and took a quick screen grab so not to forget.

Okay! I found another occurrence when trying to find the original one. Here is the link to where the replay will be loaded. https://www.twitch.tv/videos/850626484?t=46h7m1s

I dont know which replay it is, but i have a large collection of them I can send you...not sure how helpful. you'd have to find out which one it is because im not sure... :( HOWEVER, it seems to be when values are all currently still set to 0 and when the game starts and panels cycle.

The slots restored themselves later in that match when Muradin finishes his quest: https://www.twitch.tv/videos/850626484?t=46h19m42s
The camera is focused on Cassia during that. She is using Fend as seen in the progress bar.
Is the bottom panel opened before the heroes are created? There were issues in the past with it. Also the player slots could be weird. There were issues with opening the bottom panel in player vision many years ago, too. But I have not seen an issue like this in the past few years... =/

I was able to recreate it via spamming red team's player slot number at the map start and then opening the bottom panel. But that does not explain how it changed in the videos


Clean up pseudo-private member usage and simplify passes/techmap/abc.cc

This also eliminates many explicit RTLIL::SigSpec constructions, which IMO are just clutter.  I think the changed code is now much more readable.

This also eliminates many explicit RTLIL::SigSpec constructions, which IMO are just clutter

I agree re extraneous RTLIL::SigSpec constructions; feel free to remove the ones that are left.

@eddiehung Can you please review this again when you get a chance?


[RPGF-7] Add Badgeholder Metrics Section

Introducethe new section “badgeholder's metrics” in Rettro Funding 4 explore page for by able to view ballot details such as badgeholder details, metrics preference, and weight

Summary by CodeRabbit

New Features

Introduced the BadgeholderTab component for managing and displaying badgeholder data with filtering, sorting, and pagination.
Added DialogDetail for displaying detailed metrics in a modal format.
Introduced CheckBoxFilterBadgeholder for managing checkbox states related to badgeholders.
Added the SortBadgeholder component for dynamic sorting options.
Added new data retrieval function for badgeholder metrics.

Improvements

Enhanced the Cpage component to accept and manage new badgeholder data.
Updated UI components for improved readability and user experience.
Reorganized import paths and file structures for better maintainability.

Bug Fixes

Adjusted logic in ProjectTab to ensure correct evaluation of conditions.

Documentation

Updated text labels in the Text.ts file for better clarity.

One last thing is fine a better banner placeholder

Force white theme on table component is needed, seems like right now it depends on the user's preferences theme

LGTM 🚀


Should st2timersengine default to local timezone?

SUMMARY
Curious why it's necessary to configure the timezone of the timers engine, instead of simply defaulting to the timezone of the local system?
Looking at the code, it doesn't seem to matter what the timezone is, because the timers are using the timezone from the rule definition.
I'm asking for puppet-st2. Is this an essential config option, or is it OK to be defaulted to America/Los_Angeles everywhere?
ISSUE TYPE:

Feature Idea

STACKSTORM VERSION
2.9dev

ansible-st2 leaves the default America/Los_Angeles unless the playbook user explicitly changes it via the st2_config.timer*.local_timezone vars.

cc @Kami which as I remember is in favor of UTC everywhere.

Yes, I believe all the services should always use UTC internally.
Local / custom timezone option should only be available for user facing stuff (CLI, WebUI, itd.). This way there is no confusion and potential date time conversion related issues when different objects are saved with different timezones, etc.
As far as this specific setting goes - it's there for backward compatibility reasons since we already supported this option before splitting timers engine into a separate service.
Having said that, I also think this value should default to UTC to avoid confusion.

Does the timezone even matter?
It looks like each rule specifies its own timezone. I'm confused, not sure what this setting actually affects?

grepping the code, it looks like "local" timezone is a misnomer. It is the timezone used by the scheduler.
https://github.com/StackStorm/st2/blob/0245a18198babafe2ab0abde31791cf526435234/st2reactor/st2reactor/cmd/timersengine.py#L58-L60
https://github.com/StackStorm/st2/blob/f71f9b1ca03db1f9b916336f33be46a099900788/st2reactor/st2reactor/timer/base.py#L19
https://github.com/StackStorm/st2/blob/f71f9b1ca03db1f9b916336f33be46a099900788/st2reactor/st2reactor/timer/base.py#L40-L46
The APScheduler docs refer to this as:

In conjunction with upgrading from 2.7.0 to 2.9.1, I just switched my production st2 instance from US/Central to UTC. I will report back if I notice anything weird. I suspect timers will work just as they did before - triggering at the appropriate timezone-specific time.

Still an issue

Still an issue.

I've had my system in UTC for a long time without issue.
Next step: an internal st2 discussion to decide which way to take this:

do nothing
remove the config option and always use utc (my preferred option)
remove the option and always use local system timezone


Keep best CP pokemon after merging all changes.

Former pull:
https://github.com/PokemonGoF/PokemonGo-Bot/pull/880

can you push in updated config.json.example(s) please

Added

Please, merge current dev into your PR and resolve all conflicts. I would like to have this PR merged 👍

We need to filter by Pokemon ID than by name...This will ensure all Pokemon get checked. Besides this, the functionality doesn't seem to be working.

@koper89 your code doesnt read specific configured pokemons, but you have included it into config example.
I like this feature, could you please correct your code, also as @Nihisil said. merge down current dev in order to resolve conflicts :)

Oh, no, conflict again...

@surfaace Correct me If I'm wrong but this line:
release_config = self._get_release_config_for(pokemon_name)
Is reading config based of pokemon if exists if not then goes to any. So it does take specific pokemons as well.

I think PR can be closed, because we pulled a little bit general version of it to the dev https://github.com/PokemonGoF/PokemonGo-Bot/pull/1302


struct.error: integer out of range for 'Q' format code in pokemongo_bot/cell_workers/utils.py

[2016-07-26 18:10:24] [x] Coordinates found in passed in location, not geocoding.
[2016-07-26 18:10:24]
[2016-07-26 18:10:24] [x] Address found: 37.322149,-122.002152
[2016-07-26 18:10:24] [x] Position in-game set as: (37.322149, -122.002152, 0.0)
[2016-07-26 18:10:24]
...
[2016-07-26 18:10:26] [x] Starting PokemonGo Bot....
[2016-07-26 18:10:26] [#] Scanning area for objects (1 / 25)
Traceback (most recent call last):
File "pokecli.py", line 220, in
main()
File "pokecli.py", line 211, in main
bot.take_step()
File "/Users/.../Downloads/PokemonGo-Bot/pokemongo_bot/init.py", line 36, in take_step
self.stepper.take_step()
File "/Users/.../Downloads/PokemonGo-Bot/pokemongo_bot/stepper.py", line 53, in take_step
self._walk_to(self.config.walk, *position)
File "/Users/.../Downloads/PokemonGo-Bot/pokemongo_bot/stepper.py", line 67, in _walk_to
i2f(self.api._position_lat), i2f(self.api._position_lng), lat, lng)
File "/Users/.../Downloads/PokemonGo-Bot/pokemongo_bot/cell_workers/utils.py", line 98, in i2f
return struct.unpack('<d', struct.pack('<Q', int))[0]
struct.error: integer out of range for 'Q' format code
Removed some stuff to stay anonymous, but anyone know whats happening here?

{
"location": "37.322149,-122.002152",
"max_steps": 5,
"mode": "all",
"walk": 4.16,
"debug": false,
"test": false,
"initial_transfer": 0,
"location_cache": true,
"distance_unit": "km",
"item_filter": "101,102,103,104",
"evolve_all": "NONE"
}

Please run this command: git log -n 1 --pretty=format:"%H" and tell me your result.

893483778366075aa9f3b80e090b448088439b93

The problem is i2f function takes unsigned long long and tries to convert it to double. unsigned long long range is >0. Your longitudinal cordinate is -122

Is there another format that I'm not familiar with:
37.322393, -122.001461
Thats my location according to google maps.

stepper.py needs to be modified:
dist = distance(
i2f(self.api._position_lat), i2f(self.api._position_lng), lat, lng)

How am I the first person to run into this? It seems that a many many using this would have a negative long cord.

You need to update your requirements.txt

https://github.com/PokemonGoF/PokemonGo-Bot/issues/1042

in the main fold type:
type git pull
Then when that has completed,
type pip install --upgrade -r requirements.txt
This will resolve your issues.

Duplicate of https://github.com/PokemonGoF/PokemonGo-Bot/issues/1042

updating pgo api to 1.1.0 fixed this for me. thanks

Since this is a duplicate of https://github.com/PokemonGoF/PokemonGo-Bot/issues/1042 I'm closing this.
/closed


Bors rejecting valid merge commands

See https://github.com/tock/libtock-rs/pull/226. @hudson-ayers, a member of the Tock core WG (and therefore a libtock-rs owner), tried to merge the PR using bors r+. Bors gave him a permission denied error. @hudson-ayers, and other Tock core WG members, should be able to merge PRs into libtock-rs.
I'm unable to see the Bors control panel, as I am unwilling to grant Bors the "act on my behalf" GitHub permission that it requests. I do not know where Bors is getting its permissions list from.
According to the Bors documentation, the only config option that seems relevant is use_codeowners. Unfortunately, Bors doesn't document how the CODEOWNERS file is used if use_codeowners is enabled. Additionally, the CODEOWNERS file is for automatically requesting owner review, not for access control. It doesn't appear that use_codeowners is the correct solution to our permissions issues.
@torfmaster, do you have any insight in how Bors is configured, or why it is acting the way it is?

I was just informed this was an issue with the GitHub permissions for Hudson, and that Bors pulled its permissions from GitHub.


Onlyoffice not work in version 2

Bug
Using Onlyoffice with any version of traefik > 2.0
seem to work but when i open document nextcloud hung in "loading document"
With version < 2.0 , work correctly
  - traefik.http.routers.onlyoffice_2000net_it-https.rule=Host(`test.test.it`)
  - traefik.http.routers.onlyoffice_2000net_it-https.EntryPoints=https
  - traefik.http.routers.onlyoffice_2000net_it-https.tls.certresolver=letsencrypt-http
  - traefik.http.routers.onlyoffice_2000net_it-https.tls.options=

traefik.yml
entryPoints:
http:
address: ":80"
https:
address: ":443"
certificatesResolvers:
letsencrypt-http:
acme:
email<EMAIL_ADDRESS>storage: acme.json
httpChallenge:
entryPoint: http
Docker configuration backend
providers:
docker:
endpoint: "unix:///var/run/docker.sock"
exposedByDefault: false
API and dashboard configuration
api:
dashboard: true
insecure: true

Hi! I'm Træfiker :robot: the bot in charge of communication regulation.
Thanks for your interest in Traefik!
We dedicate the issue tracker to bug reports and feature requests only. My advanced AI has spotted that your issue might be a configuration problem or relates to something that doesn't look like a bug.
To confirm this, please join our Community Forum and reach out to us on the Traefik section.
In case I'm wrong (well, that would be embarrassing :sweat_smile:), my developers will re-open the issue and fix me!
In the meantime, you can double check Traefik's documentation.


Fix memory problems

Resolves #4
Having noticed and poked at the memory problems earlier, it only seemed fair to go the whole way. The problem was in the design where each pipe blockstate has its own unique model instance, each of which had their own map from all attachments to a transformation for all 6 directions. There's 2^12 * 13 pipe blockstates to start with, and with all those duplicate attachment maps each containing 6 TransformationMatrixes per attachment it's no wonder it took a lot of memory.
This reduces it down so there's now only 13 pipe models (one for each type) which are then applied to all the blockstates which match the type. TrsrBakedModel is gone completely as there's no need to hang onto data like that when it's really only the matrix which is of value (for the pipe models at least) and even that is only unique in each of the 6 cardinal directions.

Thank you, I will check this out asap.

This is a great PR and definitely a learning experience, I didn't realize it was taking this much memory. I will release this now.


Inline code actions

fixed #388

yes yes! reviewing now :+1:

alt+enter no longer pops up the codeactions
Uncaught TypeError: Cannot read property 'call' of undefined
/Users/mpdreamz/Projects/omnisharp-atom/node_modules/rx/dist/rx.js:579
Hide Stack Trace
TypeError: Cannot read property 'call' of undefined
  at CodeActionsView.setItems (/Users/mpdreamz/Projects/omnisharp-atom/lib/omnisharp-atom/views/code-actions-view.js:39:24)
  at Object.default_1 [as default] (/Users/mpdreamz/Projects/omnisharp-atom/lib/omnisharp-atom/views/code-actions-view.js:15:20)
  at AnonymousObserver._onNext (/Users/mpdreamz/Projects/omnisharp-atom/lib/omnisharp-atom/features/code-action.js:20:64)
  at AnonymousObserver.Rx.AnonymousObserver.AnonymousObserver.next (/Users/mpdreamz/Projects/omnisharp-atom/node_modules/rx/dist/rx.js:1962:12)
  at AnonymousObserver.Rx.internals.AbstractObserver.AbstractObserver.onNext (/Users/mpdreamz/Projects/omnisharp-atom/node_modules/rx/dist/rx.js:1894:35)
  at AnonymousObserver.tryCatcher (/Users/mpdreamz/Projects/omnisharp-atom/node_modules/rx/dist/rx.js:567:29)
  at AutoDetachObserverPrototype.next (/Users/mpdreamz/Projects/omnisharp-atom/node_modules/rx/dist/rx.js:5018:51)
  at AutoDetachObserver.Rx.internals.AbstractObserver.AbstractObserver.onNext (/Users/mpdreamz/Projects/omnisharp-atom/node_modules/rx/dist/rx.js:1894:35)
  at Subject.Rx.Subject.addProperties.onNext (/Users/mpdreamz/Projects/omnisharp-atom/node_modules/rx/dist/rx.js:5138:19)
  at Subject.tryCatcher (/Users/mpdreamz/Projects/omnisharp-atom/node_modules/rx/dist/rx.js:567:29)
  at AutoDetachObserverPrototype.next (/Users/mpdreamz/Projects/omnisharp-atom/node_modules/rx/dist/rx.js:5018:51)
  at AutoDetachObserver.Rx.internals.AbstractObserver.AbstractObserver.onNext (/Users/mpdreamz/Projects/omnisharp-atom/node_modules/rx/dist/rx.js:1894:35)
  at AutoDetachObserver.tryCatcher (/Users/mpdreamz/Projects/omnisharp-atom/node_modules/rx/dist/rx.js:567:29)
  at AutoDetachObserverPrototype.next (/Users/mpdreamz/Projects/omnisharp-atom/node_modules/rx/dist/rx.js:5018:51)
  at AutoDetachObserver.Rx.internals.AbstractObserver.AbstractObserver.onNext (/Users/mpdreamz/Projects/omnisharp-atom/node_modules/rx/dist/rx.js:1894:35)
  at InnerObserver.onNext (/Users/mpdreamz/Projects/omnisharp-atom/node_modules/rx/dist/rx.js:3552:90)
  at InnerObserver.tryCatcher (/Users/mpdreamz/Projects/omnisharp-atom/node_modules/rx/dist/rx.js:567:29)
  at AutoDetachObserverPrototype.next (/Users/mpdreamz/Projects/omnisharp-atom/node_modules/rx/dist/rx.js:5018:51)
  at AutoDetachObserver.Rx.internals.AbstractObserver.AbstractObserver.onNext (/Users/mpdreamz/Projects/omnisharp-atom/node_modules/rx/dist/rx.js:1894:35)
  at MapObserver.onNext (/Users/mpdreamz/Projects/omnisharp-atom/node_modules/rx/dist/rx.js:4595:19)
  at MapObserver.tryCatcher (/Users/mpdreamz/Projects/omnisharp-atom/node_modules/rx/dist/rx.js:567:29)
  at AutoDetachObserverPrototype.next (/Users/mpdreamz/Projects/omnisharp-atom/node_modules/rx/dist/rx.js:5018:51)
  at AutoDetachObserver.Rx.internals.AbstractObserver.AbstractObserver.onNext (/Users/mpdreamz/Projects/omnisharp-atom/node_modules/rx/dist/rx.js:1894:35)
  at AnonymousObserver._onNext (/Users/mpdreamz/Projects/omnisharp-atom/node_modules/rx/dist/rx.aggregates.js:591:11)
  at AnonymousObserver.Rx.AnonymousObserver.AnonymousObserver.next (/Users/mpdreamz/Projects/omnisharp-atom/node_modules/rx/dist/rx.js:1962:12)
  at AnonymousObserver.Rx.internals.AbstractObserver.AbstractObserver.onNext (/Users/mpdreamz/Projects/omnisharp-atom/node_modules/rx/dist/rx.js:1894:35)
  at AnonymousObserver.tryCatcher (/Users/mpdreamz/Projects/omnisharp-atom/node_modules/rx/dist/rx.js:567:29)
  at AutoDetachObserverPrototype.next (/Users/mpdreamz/Projects/omnisharp-atom/node_modules/rx/dist/rx.js:5018:51)
  at AutoDetachObserver.Rx.internals.AbstractObserver.AbstractObserver.onNext (/Users/mpdreamz/Projects/omnisharp-atom/node_modules/rx/dist/rx.js:1894:35)
  at FilterObserver.onNext (/Users/mpdreamz/Projects/omnisharp-atom/node_modules/rx/dist/rx.js:4899:34)
  at Subject.Rx.Subject.addProperties.onNext (/Users/mpdreamz/Projects/omnisharp-atom/node_modules/rx/dist/rx.js:5138:19)
  at AnonymousObserver._onNext (/Users/mpdreamz/Projects/omnisharp-atom/node_modules/omnisharp-client/lib/clients/client-base.js:204:35)
  at AnonymousObserver.Rx.AnonymousObserver.AnonymousObserver.next (/Users/mpdreamz/Projects/omnisharp-atom/node_modules/rx/dist/rx.js:1962:12)
  at AnonymousObserver.Rx.internals.AbstractObserver.AbstractObserver.onNext (/Users/mpdreamz/Projects/omnisharp-atom/node_modules/rx/dist/rx.js:1894:35)
  at AnonymousObserver.tryCatcher (/Users/mpdreamz/Projects/omnisharp-atom/node_modules/rx/dist/rx.js:567:29)
  at AutoDetachObserverPrototype.next (/Users/mpdreamz/Projects/omnisharp-atom/node_modules/rx/dist/rx.js:5018:51)
  at AutoDetachObserver.Rx.internals.AbstractObserver.AbstractObserver.onNext (/Users/mpdreamz/Projects/omnisharp-atom/node_modules/rx/dist/rx.js:1894:35)
  at AnonymousObserver._onNext (/Users/mpdreamz/Projects/omnisharp-atom/node_modules/rx/dist/rx.time.js:602:20)
  at AnonymousObserver.Rx.AnonymousObserver.AnonymousObserver.next (/Users/mpdreamz/Projects/omnisharp-atom/node_modules/rx/dist/rx.js:1962:12)
  at AnonymousObserver.Rx.internals.AbstractObserver.AbstractObserver.onNext (/Users/mpdreamz/Projects/omnisharp-atom/node_modules/rx/dist/rx.js:1894:35)
  at AsyncSubject.Rx.AsyncSubject.addProperties.onCompleted (/Users/mpdreamz/Projects/omnisharp-atom/node_modules/rx/dist/rx.js:5228:17)
  at StdioDriver.handlePacketResponse (/Users/mpdreamz/Projects/omnisharp-atom/node_modules/omnisharp-client/lib/drivers/stdio.js:189:22)
  at StdioDriver.handlePacket (/Users/mpdreamz/Projects/omnisharp-atom/node_modules/omnisharp-client/lib/drivers/stdio.js:173:18)
  at StdioDriver.handleData (/Users/mpdreamz/Projects/omnisharp-atom/node_modules/omnisharp-client/lib/drivers/stdio.js:167:18)
  at Interface.<anonymous> (/Users/mpdreamz/Projects/omnisharp-atom/node_modules/omnisharp-client/lib/drivers/stdio.js:115:54)
  at emitOne (events.js:77:13)
  at Interface.emit (events.js:166:7)
  at Interface._onLine (readline.js:195:10)
  at Interface.<anonymous> (readline.js:325:12)
  at Array.forEach (native)
  at Interface._normalWrite (readline.js:324:11)
  at Socket.ondata (readline.js:71:10)
  at emitOne (events.js:77:13)
  at Socket.emit (events.js:166:7)
  at readableAddChunk (_stream_readable.js:146:16)
  at Socket.Readable.push (_stream_readable.js:109:10)
  at Pipe.onread (net.js:517:20)

eurgh... chad saw this error too.
I had it at one point also but couldn't understand what was going on. It failed on this line https://github.com/OmniSharp/omnisharp-atom/blob/inline-code-actions/lib/omnisharp-atom/views/code-actions-view.ts#L38 which makes no sense at all to me. Seems like some sort of typescript bug.
It went away for me but I have no idea why. :( Maybe @david-driscoll can help

Just looked at this again.. If I run npm install the problem is there... but if I generate js using atom-typescript, the problem goes away.
Seems that atom-typescript is on a different version

:sparkles: :shipit:


mu4e: account-specific gmail flag

Describe the feature
Currently, the +gmail feature flag applies to the whole mu4e module. I am trying to setup mu4e with an outlook account for a University email, then a Gmail account for personal use. The changes made by the +gmail feature work great for my actual gmail account but cause duplicate emails in outlook when I delete or refile. I propose using a per-context variable to determine whether that context should use the gmail integration code.
This snippet does some of the work but requires gmail contexts to contain "gmail" in the name:
  (defun my-mu4e-mark-seen (orig docid msg target)
    (if (string-match "gmail" target)
        (funcall orig docid msg target)
      (mu4e~proc-move docid
                      (mu4e~mark-check-target target)
                      "-N")))
  (advice-add '+mu4e--mark-seen :around #'my-mu4e-mark-seen)

  (defun my-mu4e-gmail-fix (orig mark msg)
    (when (string-match "gmail" (mu4e-context-name (mu4e-context-determine msg 'pick-first)))
      (funcall orig mark msg)))
  (advice-add '+mu4e-gmail-fix-flags-h :around #'my-mu4e-gmail-fix)

System information

SYSTEM  type       gnu/linux
        config     x86_64-pc-linux-gnu
        shell      /run/current-system/sw/bin/fish
        uname      Linux 5.4.62 #1-NixOS SMP Thu Sep 3 09:27:11 UTC 2020 x86_64
        path       (~/dotfiles/emacs/.config/emacs/bin/ ~/.netlify/helper/bin ~/.config/emacs/bin ~/.go/bin ~/.cargo/bin ~/.npm/bin ~/bin /run/wrappers/bin ~/.nix-profile/bin /etc/profiles/per-user/$USER/bin /nix/var/nix/profiles/default/bin /run/current-system/sw/bin /nix/store/p0h2193gnsczaahqzz1zlz85ixmjfig6-emacs-27.1/libexec/emacs/27.1/x86_64-pc-linux-gnu/)
EMACS   dir        ~/dotfiles/emacs/.config/emacs/
        version    27.1
        build      Sep 14, 2020
        buildopts  --prefix=/nix/store/p0h2193gnsczaahqzz1zlz85ixmjfig6-emacs-27.1 --disable-build-details --with-modules --with-x-toolkit=gtk3 --with-xft --with-cairo CFLAGS=-DMAC_OS_X_VERSION_MAX_ALLOWED=101200
        features   XPM JPEG TIFF GIF PNG RSVG CAIRO SOUND DBUS GSETTINGS GLIB NOTIFY INOTIFY LIBSELINUX GNUTLS LIBXML2 FREETYPE HARFBUZZ M17N_FLT LIBOTF ZLIB TOOLKIT_SCROLL_BARS GTK3 X11 XDBE XIM MODULES THREADS LIBSYSTEMD JSON PDUMPER GMP
        traits     (server-running envvar-file)
DOOM    dir        ~/dotfiles/emacs/.config/doom/
        version    2.0.9
        build      HEAD -> develop, origin/develop, origin/HEAD 1456108d5 2020-09-10 18:03:32 -0400
        elc-files  0
        modules    (:input chinese :desktop (&user window-manager) :completion (company +childframe) (ivy +childframe +prescient +icons) :ui doom doom-dashboard hl-todo hydra ophints (popup +defaults) ligatures treemacs unicode vc-gutter window-select workspaces :editor (evil +everywhere) file-templates fold (format +onsave) multiple-cursors :emacs (dired +icons) electric (undo +tree) vc :term eshell vterm :checkers (syntax +childframe) (spell +aspell +everywhere) :tools direnv editorconfig (eval +overlay) lookup lsp (magit +forge) make pdf terraform :lang (cc +lsp) data emacs-lisp (go +lsp) (json +lsp) (javascript +lsp) kotlin (latex +lsp) lua markdown nix (org +dragndrop +pomodoro) php (python +lsp) racket rest (rust +lsp) scheme (sh +fish +lsp) (swift +lsp) (web +lsp) (yaml +lsp) :email (mu4e +gmail) :config (default +bindings +smartparens))
        packages   ((tree-sitter :recipe (:host github :repo ubolonton/emacs-tree-sitter :files (lisp/*.el src Cargo.toml Cargo.lock))) (tree-sitter-langs :recipe (:host github :repo ubolonton/emacs-tree-sitter :files (langs/*.el langs/queries))) (emojify) (theme-changer :pin 61945695a30d678e6a5d47cbe7c8aff59a8c30ea) (ewal) (ewal-doom-themes) (bazel-mode :disable t) (graphql-mode) (polymode) (poly-markdown) (poly-org) (org-fragtog :disable t) (literate-calc-mode) (magit-delta :disable t) (evil-owl) (flycheck-inline :recipe (:host github :repo loafofpiecrust/flycheck-inline :branch moving-point)) (valign :disable t :recipe (:host github :repo casouri/valign)) (explain-pause-mode :disable t :recipe (:host github :repo lastquestion/explain-pause-mode)) (flycheck-posframe :disable t) (flycheck-popup-tip :disable t) (org-msg :disable t) (mu4e-alert) (mu4e-send-delay :disable t :recipe (:host github :repo bennyandresen/mu4e-send-delay)) (olivetti) (org-ref) (citeproc-org) (transmission :disable t) (exwm-edit :recipe (:no-native-compile t)) (desktop-environment) (mini-modeline) (anzu) (evil-anzu) (mini-frame :disable t) (mount-mode :recipe (:host github :repo zellerin/mount-mode)) (ivy-posframe :recipe (:no-native-compile t)) (org-cv :recipe (:host gitlab :repo Titan-C/org-cv)) (highlight-numbers :disable t) (fcitx :disable t) (bitwarden :recipe (:host github :repo seanfarley/emacs-bitwarden)))
        unpin      (n/a)
        elpa       (n/a)

This issue will be resolved when #3971 merges into master.


[T4A3][T09-B1]Bey Hao Yun

ready for review

Accepting this PR without a review because another of your PRs
for this tutorial was reviewed in detail.


Cleanup old files

After we fix #10 and #9, I think we can remove all the python files that aren't swiftbulkuploader.py, unless @Petahhh would like to keep them around. Maybe as a separate command?

No we would delete them. If I ever needed them I can go back through the history. Thanks for the consideration though!

I'd only consider removing them once we got the new tool working well in your context (lots and lots of files).


✨ Decorating regular Python functions as PythonJob API

From a recent discussion with @superstar54 and @GeigerJ2: I would like to be able to just decorate a regular Python function and run it as a PythonJob inside a WorkGraph, e.g.:
from aiida_workgraph import task
from functions import generate_structures. # This is the regular Python function I want to run with AiiDA

decorated_function = task.pythonjob()(generate_structures)

wg = WorkGraph("first_workflow")
wg.tasks.new(decorated_function)

Some notes:

What if the user inputs an AiiDA node type? I.e. the input specified for the structure is an orm.StructureData? In this case, what should the variable contain inside the function body execution? If it is a StructureData, this will most likely fail. But how do we know what mutable Python type to convert the StructureData to? We could (1) read the function signature and see if the type hinting is there, or if not (2) use some configurable default, but this is always somewhat fragile. Ideally there would be a clear bijection between mutable Python types and AiiDA node types, so there is never any confusion on what mutable type to use inside the function body.

Ideally there would be a clear bijection between mutable Python types and AiiDA node types, so there is never any confusion on what mutable type to use inside the function body.

For the moment, this is how PythonJob handles data conversion.

mutable Python data -> AiiDA Data, WorkGraph will search in the aiida.data entry point. If not found, use Pickle. If multiple entry points are found, it will use the one from the config file. If not found in the config file, raise an error.
AiiDA data -> mutable Python data, all the AiiDA data passed to the PythonJob should have a value attribute, which should return the mutable Python data.


no

What you were trying to do
What actually happened
How to reproduce

Step 1
Step 2
Step 3

Log details and game version
Computer details

@samirthapasrt, your issue lacks details somehow. This makes it a bit difficult to deal with whatever problem you wanted to raise. Let us know if there is something specific you want us to look at.


Patch to print version in statusbar

Since I have to run pter in a Docker container, I can't easily run pter -v (the container is deliberately set up a certain way). I also sometimes jump between versions as there could be a serious bug or a regression in one of them.
Anyway, I thought putting version in the welcome message would be an easy fix. Here's a small patch I made -- take it or leave it, but I guess it doesn't hurt and it does provide some useful info to users.
I would certainly appreciate a merge so I won't have to maintain the patch on my end :)
95-version-statusbar.diff.gz

Darn, I missed this before I pushed out 3.15.2 just now. Sorry! :sweat_smile: Next version will have it in!

It'll be in the next release, but you can preview it from the stuff on codeberg.


Updates to Spanish Site

Fixes #1555

You can review the Spanish translations here: http://usds-geoplatform-justice40-website.s3-website-us-east-1.amazonaws.com/justice40-tool/1585-3f5645/en/?flags=sp#3/33.47/-97.5
@katherinedm-usds would it be useful to send this link to State?


Inference on videos

Thank you for this project. It's amazing!
Do you think it's possible to use a video instead of a reference image?

I think video2video is a simpler task because it only involves face swapping instead of generation. I remember there is an interesting face swapping project in insightface.


Unable to update workloads in v1.9.10 which were deployed in <=v1.9.9 due to resourcetracker controller guid

Describe the bug
I upgraded 2 separate clusters - one AKS, one GKE - from v1.9.9 to v1.9.10 using "helm upgrade --install ...."
"vela up --wait ..." deploys of new builds of existing workloads exhibit the same behaviour in both clusters - vela up hangs (aborted it after an hour!).
To Reproduce

On a cluster with v1.9.9 installed via helm, deploy (using vela-cli v1.9.9) an Application, in my case a webservice component, with vela up.
All works ok.
Update cluster to v1.9.10 with "helm upgrade --install"
Deploy (using vela-cli v1.9.10)  a new version of the application (e.g. with newer container image tag)
"vela deploy" hangs - abort with ctrl-c
doing "vela status" it reports e.g.

$ vela status -n my-ns my-app
About:

  Name:         my-app
  Namespace:    my-ns
  Created at:   2024-03-27 11:32:59 +0000 GMT
  Status:
$

trying to delete application with "vela delete" the response was that the application did not exist despite "kubectl get application ..." succeeding
observed an error shown in application describe:

$ kubectl get application -n my-ns my-app
...
Status:
  Conditions:
    Last Transition Time:  2024-03-27T12:38:37Z
    Message:               failed to create resourceKeeper: failed to load resourcetrackers: resourcetracker my-app-v25-my-ns exists but controlled by another application (uid: 161a9675-33f1-4360-81e9-3580142bf26a), this could probably be cased by some mistakes while garbage collecting outdated resource. Please check this resourcetrakcer and delete it manually
    Reason:                ReconcileError
    Status:                False
    Type:                  Synced
...

Expected behavior
vela up should proceed as normal without resourcetracker controller issues after upgrade to kubevela v1.9.10
KubeVela Version
problem controller and cli - v1.9.10
revert to v1.9.9 (and resourcetracker cleanup) fixed the issue.
Cluster information
GKE cluster - Kubernetes v1.27.7-gke.1121002
AKS cluster - Kubernetes v1.28.5
Additional context
I've had to revert both clusters to v1.9.9 in order to support the business.  I don't have a test cluster to perform further investigation.
In one case the resourcetracker was still hanging around after deleting the application with "kubectl delete application ..." as above, "vela delete ..." could not find app.
Delete of resourcetracker also hung, presumably due to finalizer.  Did "kubectl edit resourcetracker ..." and changed finalizers: [] then resourcetracker was deleted.  Without this, deploy did not succeed even back to v1.9.9.
Once this was done all back to working fine under v1.9.9.

I believe it's caused by pkg upgration. I saw the error logs of in controller:
 "Could not capability in ConfigMap" err="cannot create or update capability replication in ConfigMap: the server could not find the requested resource (post configmaps)"

It seems related to the client change in pkg, after I revert the pkg upgration commit, the controller works.
Might related to kubevela/pkg#69 or kubevela/pkg#83

Here I don't think we need to revert the pkg, it's the same for users to use 1.9.9 directly.
ping @Somefive, could you please help look into it to see if we have some cheap solution for the fix? Thanks.

Here I don't think we need to revert the pkg, it's the same for users to use 1.9.9 directly.

It's not quite the same though @wonderflow @Somefive, as v1.9.10 includes my PR https://github.com/kubevela/kubevela/pull/6477 allowing service reuse/different service and container port on gateway - which I could really do with :-)


Ability to provide custom resource naming to Service Registry

As discussed in the March CAS developers meeting, this PR provides a ResourceNamingStrategy interface and a DefaultResourceNamingStrategy implementation providing the same functionality that is coded in AbstractResourceBasedServiceRegistry.  This then allows the ability for users to provide their own custom naming strategy in place of the default.

Test failures should be accounted for:
:support:cas-server-support-yaml-service-registry:compileTestJava/home/travis/build/apereo/cas/support/cas-server-support-yaml-service-registry/src/test/java/org/apereo/cas/services/YamlServiceRegistryTests.java:22: error: no suitable constructor found for YamlServiceRegistry(ClassPathResource,boolean,ApplicationEventPublisher,NoOpRegisteredServiceReplicationStrategy)
            this.dao = new YamlServiceRegistry(RESOURCE, false,
                       ^
    constructor YamlServiceRegistry.YamlServiceRegistry(Path,boolean,ApplicationEventPublisher,RegisteredServiceReplicationStrategy,RegisteredServiceResourceNamingStrategy) is not applicable
      (actual and formal argument lists differ in length)
    constructor YamlServiceRegistry.YamlServiceRegistry(Resource,boolean,ApplicationEventPublisher,RegisteredServiceReplicationStrategy,RegisteredServiceResourceNamingStrategy) is not applicable
      (actual and formal argument lists differ in length)
1 error
 FAILED
:autoLintGradle

@tsschmidt I'd like to get this one merged, but I see there are still a few pending changes needed. Would you mind if I took over and completed those, or would you rather resume on your own as time permits?


NIFI-12101: Fixed bugs that caused StatelessBasicsIT.testChangeFlowVe…

…rsion to fail. There were a couple of related issues. Firstly, for Stateless Groups we were not waiting for the group to fully stop before attempting to update the flow but were waiting only for child/descendant groups to stop. This was due to misleading naming in the ProcessGroupUpdateStrategy enum. Renamed enum values to more clearly convey what they mean. Additionally, renamed the enum to more clearly convey what how it is used, since it is used not only for updating groups but also for retrieving groups. Additionally, when waiting for stateless groups to stop, we inadvertently checked the Set of affectedComponents' IDs against Process Group IDs so addressed the logic there and also ensured that we were consistent in setting the AffectedComponentEntity's ProcessGroup (i.e., its ProcessGroupNameDTO) as we were inconsistently setting it across the codebase.

Summary
NIFI-00000
Tracking
Please complete the following tracking steps prior to pull request creation.
Issue Tracking

[ ] Apache NiFi Jira issue created

Pull Request Tracking

[ ] Pull Request title starts with Apache NiFi Jira issue number, such as NIFI-00000
[ ] Pull Request commit message starts with Apache NiFi Jira issue number, as such NIFI-00000

Pull Request Formatting

[ ] Pull Request based on current revision of the main branch
[ ] Pull Request refers to a feature branch with one commit containing changes

Verification
Please indicate the verification steps performed prior to pull request creation.
Build

[ ] Build completed using mvn clean install -P contrib-check

[ ] JDK 21

Licensing

[ ] New dependencies are compatible with the Apache License 2.0 according to the License Policy
[ ] New dependencies are documented in applicable LICENSE and NOTICE files

Documentation

[ ] Documentation formatting appears as expected in rendered files

Of note, in order to verify the fix, you can update the AbstractPort class such that the shutdown method sleeps before making the port as stopped:
    @Override
    public void shutdown() {
        try { Thread.sleep(5000L); } catch (final Exception e) {}

        scheduledState.set(ScheduledState.STOPPED);
        logger.info("{} shutdown", this);
    }

This will cause the system test to fail consistently with the patch applied, as NiFi will attempt to update the group before the ports have stopped. Once applying the patch, NiFi will appropriately wait for the ports to stop before attempting to update the flow.

Yeah, sorry about that @exceptionfactory I did push without running through all of the system tests. I ran only the ones that I thought were affected, but I've updated the PR and ensured that all pass now.
Also - good call on the support line. I had overlooked that. But there are a few things different between the two, so I think it's best to leave this PR as-is and generate a new PR for the support line. I'll push up a new PR for that one in a bit.

Actually @exceptionfactory nevermind about the support branch - this fix does not need to go to the support branch, as it affects 2.0 only. The issue is in the StatelessBasicsIT, which tests running a Process Group using the Stateless Execution Engine. So it does not apply to the 1.x line.

@exceptionfactory if you're close to merging go ahead but i'm doing a local build and will also run sys tests. Github CI looks great so at this point we're clear to fire.  I'll take it unless you're already done

@exceptionfactory if you're close to merging go ahead but i'm doing a local build and will also run sys tests. Github CI looks great so at this point we're clear to fire. I'll take it unless you're already done

Thanks @joewitt, the system test changes themselves look good, but I just noted that JavaScript UI code changes are also necessary to align with renaming the enum values.

Thanks @exceptionfactory just realized that I didn't push that change. Will push another commit in one moment

Thanks @exceptionfactory just realized that I didn't push that change. Will push another commit in one moment

Thanks for the quick turnaround @markap14, that looks like that should cover the necessary changes. I will wait for one more system test run and then plan to merge!

@exceptionfactory sorry i was already well into this.  merged to main!

@exceptionfactory sorry i was already well into this. merged to main!

No problem, latest run looks good, thanks @joewitt and @markap14!


Fix the generate_stream crash in concurrent query

The requests number is different with the new batch size after concat. Need append the dummy parameters for the dummy requests.
What does this PR do?

Fixes # (issue)
Before submitting

[ ] This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
[ ] Did you read the contributor guideline,
Pull Request section?
[ ] Was this discussed/approved via a Github issue or the forum? Please add a link
to it if that's the case.
[ ] Did you make sure to update the documentation with your changes? Here are the
documentation guidelines, and
here are tips on formatting docstrings.
[ ] Did you write any new necessary tests?

Who can review?
Anyone in the community is free to review the PR once the tests have passed. Feel free to tag
members/contributors who may be interested in your PR.

@yuanwu2017 looks good to me. However, can you describe the scenario when this error occurs?
@jkaniecki @mszutenberg please review

@kdamaszk tested - approved, This solves issue with tensor dim's mismatch, It appears when using some non-default request parameters (like temperature != 1.0 etc) and setting do_sample inside next_token_chooser, That path uses HeterogeneousSampling , which was not validated before.

@regisss Please, review

@jkaniecki is right. The failed case used some parameters as following.
Parameters:
generate{parameters=GenerateParameters { best_of: None, temperature: Some(0.01), repetition_penalty: Some(1.03), top_k: Some(10), top_p: Some(0.95), typical_p: Some(0.95), do_sample: false, max_new_tokens: Some(32), return_full_text: Some(false), stop: [], truncate: None, watermark: false, details: false, decoder_input_details: false, seed: Some(42), top_n_tokens: None }}
terminate called after throwing an instance of 'c10::Error'
  what():  The size of tensor a (8) must match the size of tensor b (2) at non-singleton dimension 0
Exception raised from infer_size_impl at /npu-stack/pytorch-fork/aten/src/ATen/ExpandUtils.cpp:31 (most recent call first):
frame #0: c10::Error::Error(c10::SourceLocation, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >) + 0xae (0x7fc267b9fd1e in /usr/local/lib/python3.10/dist-packages/torch/lib/libc10.so)
frame #1: c10::detail::torchCheckFail(char const*, char const*, unsigned int, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&) + 0xf3 (0x7fc267b54b39 in /usr/local/lib/python3.10/dist-packages/torch/lib/libc10.so)
frame #2: at::infer_size(c10::ArrayRef<long>, c10::Ar

If you want to reproduce it, you can use this script


Review

###In this issue page, I am writing requesting for a review in setting up react app for the first time.

Hi Kazaneza,
While you made a great effort in this project, unfortunately, I cannot proceed to review your code.
Invalid Code Review Request
Kindly ensure to submit this activity for a review using the Pull Request of this project, which should have title and a description that corresponds to your project,
and ensure that the appropriate linters required for this project (see in the project requirement document)  are properly added and that linters checks are showing green on the Pull Request.
You need to also ensure that a professional ReadMe via this link is used for your project.
Your Code Review Request will be marked as invalid in your Dashboard, so please submit a new one once you are ready 🙏
Cheers and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, remember to tag me in your question so I can receive the notification.
Please, do not open a new Pull Request for re-reviews. You should use the same Pull Request submitted for the first review, either valid or invalid unless it is requested otherwise.

Invalid Code Review Request does not count into the code reviews limit.


Cannot install version<EMAIL_ADDRESS>on windows.

I've tried both node  v0.12.7 and node v4.2.1.  And on node v4.2.1 even<EMAIL_ADDRESS>no longer works.  Any ideas?
npm ERR! node v4.2.1
npm ERR! npm  v3.3.8
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>install: node lifecycleScripts/install
npm ERR! Exit status 13
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script 'node lifecycleScripts/install'.

It should be downloading pre-built binaries. Can you post a gist of the full log?

gist of npm install nodegit failure on windows 10  -> https://gist.github.com/jtraband/8aa8509d529b66c7a5d9

You need python 2 installed and configured in the path https://gist.github.com/jtraband/8aa8509d529b66c7a5d9#file-gistfile1-txt-L493

Ok, this is with python 2.7.1 and MS Visual studio 2013 installed.  Different errors now but ...
https://gist.github.com/jtraband/620d53c0ad71ec2d0e1f

Same here, Windows 7 32Bit, NW.js 0.12.3, msvs 2013, iojs 1.2.0
Please help

exact same errors here as jtraband's latest update (2 days ago), with node v4.2.1 /<EMAIL_ADDRESS>

@jtraband Weird that it's not downloading a binary for you.I'll look into that now.
@metasanjaya I'm betting our nw-gyp is out of date, I'll look into that as well.

Even if I install the newest nw-gyp with npm install -g nw-gyp, it always use nw-gyp from dependencies, so I don't think it's about nw-gyp is out of date. and then always throw error.
Looking forward for update.

I am having the same issue, with logs similar to https://github.com/nodegit/nodegit/issues/756#issuecomment-150046405 (python installed, error on msbuild.exe). It seems that the binary not being downloaded is at the core of it.
I'm running win10, node v4.2.1, npm 2.14.7. Any workaround possible while binaries at not available?

We're well past this now and these issues should be resolved :+1:. Please file a new issue if you have the problem on latest.


⚠ Bofrost.lu has degraded performance

In 2ab3f23, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1788 ms

Resolved: Bofrost.lu performance has improved in a1b7352 after 15 minutes.


Update Index file

Codecov Report

Merging #161 (9ace8e0) into master (0944af9) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #161   +/-   ##
=========================================
  Coverage     62.03%   62.03%
  Complexity      533      533
=========================================
  Files           104      104
  Lines          2028     2028
  Branches        220      220
=========================================
  Hits           1258     1258
  Misses          697      697
  Partials         73       73

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 0944af9...9ace8e0. Read the comment docs.


sync: Add tests for exclude paths, exclude upload paths & exclude download paths

Done with pull request #186


[Backport]ifconfig: fix regex matching interface name with hyphen

Signed-off-by: dheerajd-msys<EMAIL_ADDRESS>
Description

Backport https://github.com/chef/chef/pull/8756 to Chef 14

Related Issue
Fixes https://github.com/chef/chef/issues/9392
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Chore (non-breaking change that does not add functionality or fix an issue)

Checklist:

[x] I have read the CONTRIBUTING document.
[ ] I have run the pre-merge tests locally and they pass.
[ ] I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.
[x] All commits have been signed-off for the Developer Certificate of Origin.

As I can see test case changes which was added during ifconfig fix is there already in chef-14 here https://github.com/chef/chef/blob/chef-14/spec/unit/provider/ifconfig_spec.rb#L97 so no modification required.
Other changes are also there here https://github.com/chef/chef/blob/chef-14/lib/chef/provider/ifconfig.rb#L119 &  https://github.com/chef/chef/blob/chef-14/lib/chef/provider/ifconfig.rb#L124 in chef-14.
So it is good to go.

If you delete the kitchen test for travis.org that'll fix a few of the remaining Test Kitchen failures.


Fix a possible memleak in cms_main

Feel free to change all other sk_push call sites

It would be just better to fix sk_push() to never return -1.

It would be just better to fix sk_push() to never return -1.

See #22930 for that change.

This pull request is ready to merge

Merged to the master, 3.2, 3.1, and 3.0 branches. Thank you for your contribution.


Unclosed  tag breaks tag balance

This is a contrived example of some wild HTML that broke sanitize-html:
> sanitizeHTML('
Hey! Here is a broken link tag: <a href="http://www.example.com/lel...')
'
Hey! Here is a broken link tag: '

I thought this was because it was in the middle of a string, but it actually triggers if the string ends in the middle of any part of the attribute. But not if the tag doesn't have attributes yet!
> sanitizeHTML('
lel  sanitizeHTML('
lel <a href')
'
lel '  // bad!
> sanitizeHTML('
lel <a href=""')
'
lel '  // bad!

This is an upstream bug in htmlparser2, there is probably no sensible workaround so I've reported it there.

Okay, thank you :)

What's the story with this bug?

Upstream bug, no fix yet:
https://github.com/fb55/htmlparser2/issues/156

It's more dangerous than just closing allowed tags. It works with any tag, including malformed tag names like this:
<html


Use the new image prom/mysql-exporter image: v0.12.1

With version v0.11.0 we detect in the metric logs many connection problems to the MariaDB instance. This results in a non-rise of the metrics at Promotheus.
We no longer have these problems with image v0.12.1

Example have been changed, but remember, it is an example, not a recommandation or something forced by the galleria operator design. You are free to use your own images and the versions that fit your needs.


How to dimiss a modal navigation stack with a new Route

Imagine a navigation controller which gets presented and contains multiple viewcontrollers, which are pushed because of a Route constructed out of Route identifiers with respect to some user navigation flow, e.g. the route might be; [root, nav, vcA, vcB, vcC].
Popping one viewcontroller is achieved by dispatching a  SetRouteAction, with for example a new route, e.g.  [root, nav, vcA, vcB].
This works fine, but if for example the user wants to dismiss the presented viewcontroller, the route should be for this example; [root].
However doing so, will just pop (animated) each viewcontroller and then dismiss the presented viewcontroller.
What will be a good way to get the presented viewcontroller dismissed in one time with a route action? I was thinking of using the SpecificRouteData option... but maybe it is better to just dismiss the presented viewcontroller and then update the route path..
any ideas?

Facing the same issue. Will post here if I find a solution.

Same issue here, any updates on it?

ReSwift (4.0.1)
ReSwiftRouter (0.6.0):

This also has been an issue for us.

I'm not using the Router; what do you think could be a solution here?


[v1.4] Turning off opacity in corePlugins config still generates CSS variables

The generated CSS file has increased substantially in size (~40%) as a result and I can't seem to turn it off.
tailwind.config.js
corePlugins: {
    divideOpacity: false,
    backgroundOpacity: false,
    borderOpacity: false,
    placeholderOpacity: false,
    textOpacity: false
}

Generated CSS
a {
  --text-opacity: 1;
  color: rgba(255, 128, 153, var(--text-opacity));
}

.divide-black > :not(template) ~ :not(template){
  --divide-opacity: 1;
  border-color: rgba(51, 51, 51, var(--divide-opacity));
}

.bg-black{
  --bg-opacity: 1;
  background-color: rgba(51, 51, 51, var(--bg-opacity));
}

Same here.
Disabling the core-modules only removes the corresponding classes .bg-opacity-*, .text-opacity-* and so on.

I think we can improve this for sure by adding some API to the plugin system to allow checking if a given plugin is enabled. For now I'd recommend what @emptynick suggested and use the ie11 target mode for the color plugins:
target: ['relaxed', {
  backgroundColor: 'ie11',
  textColor: 'ie11',
  borderColor: 'ie11',
  placeholderColor: 'ie11',
  divideColor: 'ie11',
}]

Where is target documented? I'm not seeing it on the Configuration page.

In the release notes and in the PR.
Its experimental and (I guess) therefore not yet documented

Question: for the browserslist target, I've tried the following approaches that all evaluate to these browser versions, but I still get custom properties in the output:

browserslist key in package.json.
.browserslistrc config file.
browserslist config file.

The only thing that works is using target: 'ie11'. Is the browserslist target not in 1.4.1?

Fixed in v1.4.3 👍

@ryanfitzer Crap good catch, it was only working using the tuple syntax (['browserslist', {...}]). I've just published a fix in v1.4.4 👍


Amplicon support #1

Updated scikit-learn dependency to install properly for mg-scripts and metapool packages.
Prep-file generation support needed.

@antgonza This package is a dependency of mg-scripts. If this PR can be reviewed as-is and merged then mg-scripts can be reviewed and merged with the reference in setup.py pointing to the proper master fork and branch. I can issue an additional PR for the prep-files support.

Thank you.


With heroku/heroku:18, gem install bundler fails

With the release of bundler version 2, it started to fail.
% docker run -it heroku/heroku:18
root@xxxxxxxxxxxx:/# gem install bundler
Fetching: bundler-2.0.0.gem (100%)
ERROR:  Error installing bundler:
        The last version of bundler (>= 0) to support your Ruby & RubyGems was 1.17.3. Try installing it with `gem install bundler -v 1.17.3`
        bundler requires RubyGems version >= 3.0.0. The current RubyGems version is 2.7.6. Try 'gem update --system' to update RubyGems itself.

I can just do as the error message says, but just let you folks know.

I think you'll have to use an older Bundler version.
Ruby is available in our stack image for scripting purposes. The one available, version 2.5.1 (see our Ubuntu Packages article), is the one Canonical provides for Ubuntu 18.04. They're unlikely to upgrade either Ruby, any gems or other packages to backwards incompatible versions because that's a change in contract for everyone using that distribution. The same applies on Heroku; if we patch these, we risk taking down running apps.
However, if you use Ruby on Heroku, the buildpack will install your desired Ruby version separately along with a compatible Bundler version. This is to give you full control over which runtime you use and to decouple that from stack image upgrades (so you in a couple years can upgrade to Heroku-20 without also having to change your app to the Ruby version that happens to be included with Ubuntu 20.04).
Can you explain your use case?

I went with gem install bundler -v 1.17.3 path.
I figured out why and how this happened immediately, so it was not a problem to me, but the code used to work suddenly stopped working was a bit of surprise to me. I assume this happens to some other folks too, so I decided to post it here. Thanks for your explanation.


node12 deprecated for actions

Using compose-action result in following warning:
Node.js 12 actions are deprecated. For more information see: https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/. Please update the following actions to use Node.js 16: isbang/compose-action, isbang/compose-action

I tested just changing to node16 in action.yml. The warning goes away and I don't see anything breaking.

https://github.com/isbang/compose-action/pull/16

Thank you for your contribution :)
Could you please check if version v1.4.0 fixes this warning?

Our e2e pipeline using v1.4.0 release just finished without the warning. I trust the release to be working as it should.
For reference, this is what I use in the workflow yml
      - uses<EMAIL_ADDRESS>        with:
          compose-file: './docker-compose.ci.yml'
          down-flags: '--volumes'

So nothing fancy.
Thanks for the quick response. Much appreciated.


Streaming IP camera using example code.

Hi Team,
I am willing to use this sdk-js for access KVSWebRTC for our onsite camera video streaming. I want to run this code on the server which is reading the camera stream (rtsp) from a port. While i was porting this code to be run on server side, i came to know that we are using a lot of browser APIs for access web cameras. Can you suggest me how can i stream rtsp camera using this code? I am currently struggling with how to get stream out of rtsp camera so that i can integrate it with this code?

JS SDK really is about the signaling client. The actual webrtc implementation is inside the browser. You might need to look into the browsers implementation.
Alternatively, you could use our own implementation of C-based webrtc for your service.
Please close this issue if you have no further questions about the code itself. For more generic solution architecture questions you can reach out to your AWS technical account management team.

Closing based on tag


Made root permission check work for setuid bit (EUID)

Hi
Thanks for this code!
I wrote a simple logger program using your library, but i wanted it to be run with the setuid bit set.
Currently, the checkRoot() function only checks for a UID of 0 (root). This means that the check will fail when the binary is run as setuid root. i updated the checkRoot() function to handle the case when the EUID (effective UID) is 0 as well as when the UID is 0.
I think it's a small improvement so i thought you might want to add it.
Example below using this code:
package main

import (
	"github.com/MarinX/keylogger"
)

func main() {
	_, err := keylogger.NewDevices()
	if err != nil {
		println(err.Error())
	}
}

Behaivour before this PR:
$ go build main.go
$ sudo chown root main
$ sudo chmod u+s main
$ ./main
Cannot read device files. Are you running as root?
$

Behaivour after this PR:
$ go build main.go
$ sudo chown root main
$ sudo chmod u+s main
$ ./main
$

Great notice! Thank you 👍


Problem with Julia v1.9

A fresh environment and trying to add AbstractFFTs:
(@v1.9) pkg> activate .
  Activating new project at `C:\Users\user\Documents\test`

(test) pkg> add AbstractFFTs
   Resolving package versions...
ERROR: `AbstractFFTs=621f4979-c628-5d54-868e-fcf4e3e8185c` depends on `ChainRulesCore=d360d2e6-b24c-11e9-a2a3-2a2ae2dbcce4`, but no such entry exists in the manifest.

(test) pkg> st
ERROR: `AbstractFFTs=621f4979-c628-5d54-868e-fcf4e3e8185c` depends on `ChainRulesCore=d360d2e6-b24c-11e9-a2a3-2a2ae2dbcce4`, but no such entry exists in the manifest.

(test) pkg> resolve
ERROR: `AbstractFFTs=621f4979-c628-5d54-868e-fcf4e3e8185c` depends on `ChainRulesCore=d360d2e6-b24c-11e9-a2a3-2a2ae2dbcce4`, but no such entry exists in the manifest.

bricks the environment, and I have to delete the Manifest.toml
The faulty Manifest:
# This file is machine-generated - editing it directly is not advised

julia_version = "1.9.0"
manifest_format = "2.0"
project_hash = "9c7389bc788da64ffc77a207bbc270cbe7a6b775"

[[deps.AbstractFFTs]]
git-tree-sha1 = "16b6dbc4cf7caee4e1e75c49485ec67b667098a0"
uuid = "621f4979-c628-5d54-868e-fcf4e3e8185c"
version = "1.3.1"

    [deps.AbstractFFTs.deps]
    ChainRulesCore = "d360d2e6-b24c-11e9-a2a3-2a2ae2dbcce4"
    LinearAlgebra = "37e2e46d-f89d-539d-b4ee-838fcccc9c8e"

[[deps.Artifacts]]
uuid = "56f22d72-fd6d-98f1-02f0-08ddc0907c33"

[[deps.CompilerSupportLibraries_jll]]
deps = ["Artifacts", "Libdl"]
uuid = "e66e0078-7015-5450-92f7-15fbd957f2ae"
version = "1.0.2+0"

[[deps.Libdl]]
uuid = "8f399da3-3557-5675-b5ff-fb832c97cbdb"

[[deps.LinearAlgebra]]
deps = ["Libdl", "OpenBLAS_jll", "libblastrampoline_jll"]
uuid = "37e2e46d-f89d-539d-b4ee-838fcccc9c8e"

[[deps.OpenBLAS_jll]]
deps = ["Artifacts", "CompilerSupportLibraries_jll", "Libdl"]
uuid = "4536629a-c528-5b80-bd46-f80d51c5b363"
version = "0.3.21+4"

[[deps.libblastrampoline_jll]]
deps = ["Artifacts", "Libdl"]
uuid = "8e850b90-86db-534c-a0d3-1478176c7d93"
version = "5.7.0+0"

If I first add ChainRulesCore it works:
julia_version = "1.9.0"
manifest_format = "2.0"
project_hash = "2bb9064b8db2c2c5d350b6ef1f4b9442d46dcddd"

[[deps.AbstractFFTs]]
deps = ["ChainRulesCore", "LinearAlgebra"]
git-tree-sha1 = "16b6dbc4cf7caee4e1e75c49485ec67b667098a0"
uuid = "621f4979-c628-5d54-868e-fcf4e3e8185c"
version = "1.3.1"

Can't reproduce:
(@v1.9) pkg> activate --temp
  Activating new project at `/tmp/jl_clzZdQ`

(jl_clzZdQ) pkg> add AbstractFFTs
    Updating registry at `~/.julia/registries/General`
    Updating git-repo `https://github.com/JuliaRegistries/General.git`
   Resolving package versions...
    Updating `/tmp/jl_clzZdQ/Project.toml`
  [621f4979] + AbstractFFTs v1.3.1
    Updating `/tmp/jl_clzZdQ/Manifest.toml`
  [621f4979] + AbstractFFTs v1.3.1
  [56f22d72] + Artifacts
  [8f399da3] + Libdl
  [37e2e46d] + LinearAlgebra
  [e66e0078] + CompilerSupportLibraries_jll v1.0.2+0
  [4536629a] + OpenBLAS_jll v0.3.21+4
  [8e850b90] + libblastrampoline_jll v5.7.0+0

(jl_clzZdQ) pkg> st
Status `/tmp/jl_clzZdQ/Project.toml`
  [621f4979] AbstractFFTs v1.3.1

(jl_clzZdQ) pkg> resolve
  No Changes to `/tmp/jl_clzZdQ/Project.toml`
  No Changes to `/tmp/jl_clzZdQ/Manifest.toml`

sry, I updated the faulty Manifest

(@v1.9) pkg> activate --temp
  Activating new project at `C:\Users\LOCAL_~1\Temp\jl_HAyEBj`

(jl_HAyEBj) pkg> add AbstractFFTs
   Resolving package versions...
ERROR: `AbstractFFTs=621f4979-c628-5d54-868e-fcf4e3e8185c` depends on `ChainRulesCore=d360d2e6-b24c-11e9-a2a3-2a2ae2dbcce4`, but no such entry exists in the manifest.

I removed my whole .julia folder, now it works. I'm uncertain if this is related to this package at all or just a coincidence. Nevertheless, the upgrade experience to v1.9 was not that great.


fix: assume controller always as listening

Fixes #739

Pull Request Test Coverage Report for Build 614261854

0 of 1 (0.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 18.796%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

lib/ZwaveClient.js
0
1
0.0%

Totals

Change from base Build 614046274:
0.0%

Covered Lines:
2004

Relevant Lines:
10943

💛  - Coveralls


Update to release 4.1 and download release from github where code is …

…now hosted.

Checklist

[ ] Used a fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.
I do have some suggestions for making it better though...
For recipe:

License is not an SPDX identifier (or a custom LicenseRef) nor an SPDX license expression.

@conda-forge-admin, please rerender

Hi @petebunting great that there will be a new version!
BTW I think that the recommended way to pin versions these days is to create a conda_build_config.yaml in the recipe dir with something like this (not in meta.yaml), then re-render:
geos:
  - 3.7.2
cgal-cpp:
  - 4.14

I'm not much of an expert though...

@conda-forge-admin, please rerender

@conda-forge-admin, please rerender

Hi @petebunting great that there will be a new version!
BTW I think that the recommended way to pin versions these days is to create a conda_build_config.yaml in the recipe dir with something like this (not in meta.yaml), then re-render:
geos:
  - 3.7.2
cgal-cpp:
  - 4.14

I'm not much of an expert though...

Thanks @gillins (hope all is well with you guys in these rather strange times!), tried that and it then got in a mess saying it couldn't find geos 3.7.2 as it was using gdal 3.0.4 (rather than 3.0.1) which is built against geos 3.8.1. I used the geos c++ api in rsgislib and that is the problem here.
They've since recommended that the geos c api is used and the c++ is not as the interface won't be stable. Much of the code which is using geos is not being used or to be honest, really maintained, so I think the answer here is to remove geos as a direct rsgislib dependency and where needed use through ogr. I'll try and get this building on all the platforms now - still have an odd windows error where it builds but then cannot import rsgislib when it runs the tests. I'll then look at removing direct imports of geos from rsgislib over the next week or so.
The issue with cgal seems to be related to the compile version (i think) as the error is related to the stl. I'll put pulled this over from my dev builds on my local machine so now it's re-rendered this might have been solved and I might not need to pin the version - hopefully!

@gillins and @danclewley, it now builds for all the python versions and platforms. However, I've had to pin geos and cgal versions. I wasn't able to use conda_build_config.yaml as it didn't pull appropriate versions.
Going forward, I think I will remove geos as a dependency to rsgislib. CGAL, I haven't been able to work out all the errors with the latest version. The original error was being unable to find std::enable_if_t, which was introduced in c++14. I have, therefore, moved to use c++14 but now the most recent version of cgal gives an error about being unable the library.
Are you happy if I merge this pull request? I'll then work on removing geos for the next release hopefully in the next month or so as until this is done it won't compile against the most up to date version of GDAL. Hopefully, I can also work out what is going on with CGAL as well.

Sounds good to me!


Renamed the binding to document as wbg_document

When wasm-bindgen-test is used to test user code which declares bindings to static document, duplicate js bindings to it are generated. It is caused due to internal bindings used in wasm-bindgen-test.
Fixes #714

Thanks for the PR! I think it's probably best to fix the internal bug though which hopefully isn't too hard, so I'm gonna close this in favor of that PR.


Fix if prop is equal to transition

If prop value was transition then you will get:
ERROR in ./node_modules/weex-vue-loader/lib/style-loader.js!./node_modules/weex-vue-loader/lib/style-rewriter.js?id=data-v-55edf017!./node_modules/weex-vue-loader/lib/selector.js?type=styles&index=0!./resources/assets/js/components/layout/App.vue
    Module build failed: TypeError: Cannot read property 'toLowerCase' of undefined

As the script would try to make lowercase of undefined. I happens because transition is being replaced with nothing and realProp will become empty string. If it is empty string then you cannot get first element of it because it will be undefined.

Thanks for your contribution. This PR fixes the #19.


@types/graphql conflicts

Describe the bug
When using graphql-tools to perform schema stitching with a schema generated from type-graphql and another schema not coming from type-graphql, then you get errors of Invalid Schema Passed.
It appears this is due to the fact that @types/graphql is a dependency and not a dev dependency in both type-graphql and apollo-link projects. Apollo-link is using 0.12.6 where as type-graphql is using 0.13.3.
Is there a reason this is a dependency and not a devDependency?
To Reproduce
Create a simple type-graphql schema and run buildSchema on it, then create a standard schema using makeExecutableSchema from graphql-tools. Once done, merge the schemas using mergeSchemas from graphql-tools.
The version in use of graphql-tools is<EMAIL_ADDRESS>Expected behavior
type-graphql should be combinable with existing schemas using graphql-tools schema stitching.

Do you have an compilation error or runtime error?
@types/graphql is a devDep of graphql-tools so it's not downloaded by npm at all.
If you have runtime error, try npm dedupe and npm prune as graphql-tools has peerDependency "graphql": "^0.12.0 || ^0.13.0" so it should accept "graphql": "^0.13.2" that comes with TypeGraphQL and be merged into one package in node_modules.

I get a runtime error of "Invalid Schema Passed" because if is trying to check if my schema is typeof GraphQLSchema, which comes from @types/graphql. That type has changed between 0.12 and 0.13.
GraphQLTools has a a peerDependency of "graphql", but I am talking about "@types/graphql".
It has a dependency of "apollo-link": "1.2.2"
https://github.com/apollographql/graphql-tools/blob/master/package.json#L51
which has a dependency of:
https://github.com/apollographql/apollo-link/blob/master/packages/apollo-link/package.json#L41
See related open bug for apollo-link.
https://github.com/apollographql/apollo-link/issues/601

get a runtime error (...) which comes from @types/graphql

nope, types are pruned on compilation and have no affect on runtime

it has a dependency of "apollo-link": "1.2.2"
which has a dependency of "@types/graphql": "0.12.6",

So there's nothing I can do - I use graphql-js 0.13 with types for 0.13, you need to ignore the types conflict with skipLibCheck and ping guys from apollo to update their types :wink:

Hi @pablocarreraest!
No it's not possible. Please describe your use case in more details.

Sure, makeExecutableSchema you must know is from Apollo and also do a slightly different things than buildSchema. I found this stackoverflow
The main reason I search for this difference is because I have one project using makeExecutableSchema and with that it handles the relationships independently (also using typeorm).
I just give the functions to get all and by id. here's an example:
// Repository of User
public findAll$ (): Observable<User[]> {
   return from(this.manager.find(User))
            .pipe(catchError((error) => Observable.throw(error)));
}
// Repository of Photo
public findById$ (id: string): Observable<Photo> {
    return from(this.manager.findOne(Photo, {id}))
            .pipe(catchError((error) => Observable.throw(error)));
}

// Query Resolvers
users (root, args, ctx): Promise<Movie[]> {
    const repository: MovieRepository = ctx.db.getCustomRepository(MovieRepository);
    return repository.findAll$().toPromise();
},
photo (root, args, ctx): Promise<Photo> {
    const repository: PhotoRepository = ctx.db.getCustomRepository(PhotoRepository);
    return repository.findById$(args.id).toPromise();
},

with that when I query they give me the relationships with no problema using makeExecutableSchema (magic 🧚♀).
query {
  users {
    photos {
      id
      format
    }
  }
}

now in other project that I was playing with this library (that's amazing 😎).
I define the same way as above but to get the relationships I have to specify in the repository or I will get null.
// Repository of User
public findAll$ (): Observable< User[]> {
   return from(this.manager.find(User, {relations: ['photos']))
            .pipe(catchError((error) => Observable.throw(error)));
}

And for get more inner relationship inside the photos.types in other words you have to put the relationship by hand ✍. using buildSchema
Tell me what do you thing... about it. ✌

I will blow your mind once more time: TypeGraphQL is not using buildSchema from graphql-js, only new GraphQLSchema:
https://github.com/19majkel94/type-graphql/blob/7cf044c84939fef854437b1c7a62d0bc99ddbf5d/src/schema/schema-generator.ts#L86-L91
And makeExecutableSchema is a helper from apollo that allows you to decouple types definitions (using SDL) from their implementations (resolvers map).
It doesn't make any magic with automatically resolving TypeORM entities relations. The only framework that do this is vesper 😉
And why you asked this question here? Please continue the discussion on gitter or create a separate issue.


Chrome extension buttons bug

Describe the bug
The buttons text is not displayed correctly.
To Reproduce
Tested on:

Trust Wallet Extension 2.26.0
Chrome 130.0.6723.70 (Official Build) (64-bit)
Windows 10

Screenshots

Hi @mrgharabaghi, this issue is not related to the wallet core repository, please create a ticket here if u believe there is a bug in the application: https://support.trustwallet.com/en/support/tickets/new

@satoshiotomakan
I submitted my request, but every time a bot responds to my request.

https://github.com/user-attachments/assets/c03d0cb6-8762-47de-8611-365bab190cd6

The issue has been resolved.
There was a problem with my VPN.