Open DrawerNavigator content with "hamburger" icon

Hi, I've been a while trying to success with this but I can't find the solution. What I want is basically to show the "hamburger" icon at the top of the header to open the DrawerNavigator menu.
I have a DrawerNavigator which contains 2 options, each of them is loading a StackNavigator component.
I've managed to show the icon and get the onPress event fired, but I don't know how to fire from the onPress event the function to open the navigator (navigation.navigate('DrawerOpen'))
const SchedulesStack = StackNavigator({
  Schedules: {
    screen: SchedulesScreen,
    navigationOptions: {
      title: 'Schedules`,  // Title to appear in status bar
      headerLeft: <Icon name="menu" size={35} onPress={ () => /** Here should be the magic **/ } />
    }
  }
});

const Homestack = StackNavigator({
  Home: {
    Screen: Home
    navigationOptions: {
      title: 'Home',  // Title to appear in status bar
      headerLeft: <Icon name="menu" size={35} onPress={ () => /** Here should be the magic **/ } />
    }
  }
});

const Root = DrawerNavigator({
  Home: {
    screen: HomeStack,
    navigationOptions: {
      title: 'Home' // Text shown in left menu
    }
  },
  Schedules: {
    screen: SchedulesStack,
    navigationOptions: {
      title: 'Schedules',  // Text shown in left menu
    }
  }
  }
})

software
version

react-navigation
^1.0.0-beta.9

react-native
0.44.0

node
6.10.1

npm or yarn
6.10.1 / 0.23.4

Thank you

Ok, I've found the solution and I respond to myself, what I had to do is to convert the whole navigationOptions key into a function with the navigation as an argument, then I was able to access the naigation property to open the drawer.
const SchedulesStack = StackNavigator({
  Schedules: {
    screen: SchedulesScreen,
    navigationOptions: ({ navigation }) => ({
      title: 'Schedules',  // Title to appear in status bar
      headerLeft: <Icon name="menu" size={35} onPress={ () => navigation.navigate('DrawerOpen') } />
    })
  }
});

const Homestack = StackNavigator({
  Home: {
    Screen: Home
    navigationOptions: ({ navigation }) => ({
      title: 'Home',  // Title to appear in status bar
      headerLeft: <Icon name="menu" size={35} onPress={ () => navigation.navigate('DrawerOpen') } />
    })
  }
});

const Root = DrawerNavigator({
  Home: {
    screen: HomeStack,
    navigationOptions: {
      title: 'Home' // Text shown in left menu
    }
  },
  Schedules: {
    screen: SchedulesStack,
    navigationOptions: {
      title: 'Schedules',  // Text shown in left menu
    }
  }
  }
})

thanks @davidrojo your example was helpful

Guys, there is a typo in the above code. I used it and spent an hour to just debug the issue and finally found a typo. I don't want someone else to waste their time. So, the correct code is:
`const SchedulesStack = StackNavigator({
Schedules: {
screen: SchedulesScreen,
navigationOptions: ({ navigation }) => ({
title: 'Schedules',  // Title to appear in status bar
headerLeft: <Icon name="menu" size={35} onPress={ () => navigation.navigate('DrawerOpen') } />
})
}
});
const Homestack = StackNavigator({
Home: {
screen: Home
navigationOptions: ({ navigation }) => ({
title: 'Home',  // Title to appear in status bar
headerLeft: <Icon name="menu" size={35} onPress={ () => navigation.navigate('DrawerOpen') } />
})
}
});
const Root = DrawerNavigator({
Home: {
screen: HomeStack,
navigationOptions: {
title: 'Home' // Text shown in left menu
}
},
Schedules: {
screen: SchedulesStack,
navigationOptions: {
title: 'Schedules',  // Text shown in left menu
}
}
}
})`

What if someone has to navigate to another screen from the stack navigator, how should I do that?

@jiggylepcha - you might have better luck asking the question on one of the suggested places here https://reactnavigation.org/en/help.html

Updated code which works with new version of react-navigation:
const SchedulesStack = StackNavigator({
  Schedules: {
    screen: SchedulesScreen,
    navigationOptions: ({ navigation }) => ({
      title: 'Schedules',  // Title to appear in status bar
      headerLeft: <Icon name="menu" size={35} onPress={ () => navigation.toggleDrawer() } />
    })
  }
});

const Homestack = StackNavigator({
  Home: {
    screen: Home
    navigationOptions: ({ navigation }) => ({
      title: 'Home',  // Title to appear in status bar
      headerLeft: <Icon name="menu" size={35} onPress={ () => navigation.toggleDrawer() } />
    })
  }
});

const Root = DrawerNavigator({
  Home: {
    screen: HomeStack,
    navigationOptions: {
      title: 'Home' // Text shown in left menu
    }
  },
  Schedules: {
    screen: SchedulesStack,
    navigationOptions: {
      title: 'Schedules',  // Text shown in left menu
    }
  }
  }
})


"Could not locate the pip command. at 45:" @CentOS 6.7

looks like something is wrong here?!
Error: Could not set 'present' on ensure: Could not locate the pip command. at 45:/etc/puppet/modules/awscli/manifests/init.pp Error: Could not set 'present' on ensure: Could not locate the pip command. at 45:/etc/puppet/modules/awscli/manifests/init.pp Wrapped exception: Could not locate the pip command. Error: /Stage[main]/Awscli/Package[awscli]/ensure: change from absent to present failed: Could not set 'present' on ensure: Could not locate the pip command. at 45:/etc/puppet/modules/awscli/manifests/init.pp
Thanks for your help.

Seems like your host is missing python-pip.

unfortunately it is installed
Installed Packages Name        : python-pip Arch        : noarch Version     : 7.1.0 Release     : 1.el6 Size        : 6.6 M Repo        : installed From repo   : epel
still the awscli-module cannot find the pip command.
Any suggestions?

Maybe pip is not in your $PATH?

pip command is located under /usr/bin/pip
So, it is available via $PATH

fixed it by adding a symlink
`  file { '/usr/bin/pip-python':
ensure => 'link',
target => '/usr/bin/pip',
}
class { 'awscli':
require => File[ '/usr/bin/pip-python' ],
}`


fix: Menu scroll size

:tada: This PR is included in version 1.0.0 :tada:
The release is available on:

GitHub release
v1.0.0

Your semantic-release bot :package::rocket:


add general purpose allocator to standard library

We have std.mem.IncrementingAllocator but we also should have a general purpose allocator.

Before engaging in writing block allocator from scratch Zig could wrap one or more existing C allocators. The one I use is Doug Lea's malloc ( http://g.oswego.edu/dl/html/malloc.html ). The code had been maintained for some 30 years. Its API is feature rich and targets high performance use.
It is implemented as one file library, joy to use.
Sometimes the internet claims there are more modern and/or faster allocators. These claims are not accompanied by benchmarks, but could be correct in some situations: DL malloc doesn't use separate per-thread heaps.
Several other allocators are based on DL malloc, e.g. nedmalloc:  http://www.nedprod.com/programs/portable/nedmalloc/ .

See also #480

Duplicate of #480.


assertDoesNotCompile won't compile with -Xfatal-warnings

When compiling with -Xfatal-warnings, assertDoesNotCompile fails to compile if the code passed emits compiler warnings.
object Foo { type Type = Any with Tag { type Refine } ; trait Tag extends Any }
assertDoesNotCompile("(1: Any) match { case x: Foo.Type => x }")
// a pattern match on a refinement type is unchecked

Alternatively, it would be nice if there was a way to assertCompilerWarning, but since folks prefer to compile with -Xfatal-warnings anyway it's probably better to find a way to support asserting on warnings generated with that compiler flag passed.

@carymrobbins Referring to my comment here:
https://github.com/scalatest/scalatest/issues/1317#issuecomment-390901698
I believe the approach to invoke the compiler directly should fix your issue (assertCompilerWarning is an interesting idea and I believe it is possible with the new approach also).  It would be great if you can share your opinion with us on the new approach.

I think assertCompilerWarning might be nice, but since I always use -Xfatal-warnings I'm not sure how useful it will be. One thing I'm always wanting to do is assert on the compiler error message itself, which I usually do by doing assertCompile, catching the exception, then asserting on the exception message. Since we're looking at adding new functionality, I'd recommend something like -
def assertCompilerErrorMessage(code: String, regex: Regex) = ???
def assertCompilerErrorMessage(code: String, msgPred: String => Boolean) = ???
def getCompilerErrorMessage(code: String): String = ???


Platform no longer instantiable

The following:
<EMAIL_ADDRESS>
import 'dart:io';

void main() {
  var p = Platform();
  print(p);
}

is failing with:
Error: The class 'Platform' is abstract and can't be instantiated.
  var p = Platform();
          ^^^^^^^^

Shouldn't this work if the lang version is 2.19?  I thought the SDK exception would kick in.
@mit-mit was hitting this as well.
@lrhn @leafpetersen

Marking Dart 3 for now.

As @munificent noted offline, this doesn't have anything to do with new class modifier work.  abstract was always there, we recently changed Platform to abstract.

@bsutton - the only usage of this we found (so far) is in dcli.  We could revert, but checking if this is an easy change on your side?
fyi - @brianquinlan

Marking this a P1 as we need to resolve quickly if Platform needs to be instantiatable, if the answer is yes then we need a cherry pick of a change that drops the 'abstract' modifier from Platform.

So looks like my singular usage is in my Platform extension function.
String get eol => DCliPlatform().isWindows ? '\r\n' : '\n';

While its not an egregious change, it is part of the DCli public api and I'm then left with the problem of where to place the eol function so that it  is still obvious and easy to find.
Now if you where to add an eol method to the Platform interface my problem goes away :D

For now I'll remove the abstract modifier. Then we can remove eol as an extension method (one way or another). And then readd the abstract modifier.

Did we check if we added abstract to any other core library types than Platform?

Consider making DCliPlatform not extend Platform. There is no advantage in extending a class with only static members (and Platform will still be final in the future, so also not extensible when you migrate dcli to Dart 3.0).
I'd prefer to keep Platform abstract if at all possible.
If we don't, consider adding @Deprecated("Do not instantiate this class") Platform(); as a constructor, to warn about using it in a way that it's very much not intended.

@mit-mit

Did we check if we added abstract to any other core library types than Platform?

A quick check (RegExp based inspection of git diff 3.0.0-0.0.dev beta) shows:
We added abstract to:

BigInt - factory constructors only. Safe.
Capability - factory constructors only. Safe.
Platform - This.
ProcessInfo - Static only members.
Timeline - Static only members.

So two more classes that are similar to Platform. I'd keep them abstract if at all possible. There was never any reason to instantiate a static-only class.
If nobody tells us about an issue, I'd prefer to not change anything.
We also removed abstract from class HttpProfiler. It's now just final, but it's all statics, and there is no obvious reason to remove the abstract or allow instantiation, so it should probably stay abstract too.
I'll create a CL.

Creating an instance of a class with only static members has no advantage

I have to disagree with this.
If I can't remember the name of a function how do I find it?
If I at least know it has something to do with 'Platform' then I can type
Platform.
and the auto complete will give me the list of methods associated with platform operations.
I've taken the same approach with the Strings package.
I want to convert a string to upper case. Is the method toUppercase, asUppercase, uppercase or some other aberration.
By typing 'Strings.' I can scroll through the list of methods and at the same time I can see what other handy string functions are available.
Its all about making it easy to find the function you are looking for.
I used the same principle for the 'eol' function.
Where would I expect to find a platform specific function to be, in the Platform package.

So looks like my singular usage is in my Platform extension function.
...
If I can't remember the name of a function how do I find it?
If I at least know it has something to do with 'Platform' then I can type Platform.

Platform. will show all static members, and extension methods are not static. So not sure I understand that:

Am I missing something?

So looks like my singular usage is in my Platform extension function.
...
If I can't remember the name of a function how do I find it?
If I at least know it has something to do with 'Platform' then I can type Platform.

Platform. will show all static members, and extension methods are not static. So not sure I understand that:

Am I missing something?

I've reported this as a bug:
https://github.com/Dart-Code/Dart-Code/issues/4524

Actually my mistake:
The method that DCLI uses is:
extension PlatformEx on Platform {
  String get eol => DCliPlatform().isWindows ? '\r\n' : '\n';
}

In vs-code this allows you to type:
Platform().eol;

Which does auto complete and is why I placed eol in the PlatformEx extension and why I would like to see Platform remain instantiatable.

In vs-code this allows you to type: Platform().eol;

Sure, it will auto-complete from Platform(). to Platform().aol, but given this class is 100% static in the core libraries, do you think developers are likely to type Platform() and then invoke complete? I guess they may try just exploring the API surface, but if they do that a few times (prior to your extension) they'll learn it's all static and there are zero completions, and stop doing that. I think you are optimizing for a use case that happens very, very rarely (it ever)...

I filed a bug to create a constant containing the platform line ending: https://github.com/dart-lang/sdk/issues/52379


Rebase onto upstream

I've tried to rebase this onto the latest changes from PeteGoo/tcSlackBuildNotifier.
It was a bit hairy, so I'd like to do some testing before merging this in (and updating my PR to merge our changes into the upstream.
May have to grab some help for that, since I can't quite remember how we tested this before :)

OK, I made a right mess of this. Canning this PR and trying again.


Constraints shouldn't be in transactions with queries

Don't know how hard this would be, but I'm getting "Cannot perform schema updates in a transaction that has performed data updates." from Neo4j and I'm not quite sure how to fix it.  I'll get it in the end, but don't want this to bite users

Is eager_load enabled in the app?
On Friday, October 16, 2015, Brian Underwood<EMAIL_ADDRESS>wrote:

Don't know how hard this would be, but I'm getting "Cannot perform schema
updates in a transaction that has performed data updates." from Neo4j and
I'm not quite sure how to fix it. I'll get it in the end, but don't want
this to bite users
—
Reply to this email directly or view it on GitHub
https://github.com/neo4jrb/neo4j/issues/991.

It isn't, but I'm running in development mode.  We shouldn't have to enable eager_load to fix things, right?
Also I should make clear that this was happening because I was starting from a fresh database.  The reason it was particularly a problem for me is because I wanted to create a Rails app that people could checkout and run the rake task (where this was happening) on a fresh DB

What about just adding a rake task to load the app so the schema changes
can take place? We can compare it to rake db:migrate and offer it as a
solution for this if/when it occurs.
On Friday, October 16, 2015, Brian Underwood<EMAIL_ADDRESS>wrote:

It isn't, but I'm running in development mode. We shouldn't have to enable
eager_load to fix things, right?
Also I should make clear that this was happening because I was starting
from a fresh database. The reason it was particularly a problem for me is
because I wanted to create a Rails app that people could checkout and run
the rake task (where this was happening) on a fresh DB
—
Reply to this email directly or view it on GitHub
https://github.com/neo4jrb/neo4j/issues/991#issuecomment-148706876.

Sure, I can certainly see that.  I think DataMapper has a task that migrates SQL database to fit the schema specified in the model.  It feels like there's got to be a way to execute a separate schema change query in a separate transaction, though, first.  Maybe when the models are first loaded

I'm getting the same error when running the db:seed rake task.  I'm working on upgrading our app from a really old version of the gem to the latest.  Eager load is enabled.  Any ideas?

@veetow try opening the app once from the Rails console. It will connect to the server and build the schema, then you can run tasks and no more changes will be needed.

That did it, and it entirely makes sense to me now.  Adding a rake task to pre-load the schema as you suggested above would go a long way to prevent confusion for a lot of people.

I've also been working on a refactor of some things for the upcoming 7.0 release and I think that this issue will be resolved as part of that


Fix docker container shutdown issue

Signed-off-by: Hai Yan<EMAIL_ADDRESS>Description
Use exec command to run application so that data prepper is run on the container's primary process (PID 1) and be able to respond to Ctrl+c.
On 2.0, data prepper is launched through a bash script, /bin/bash takes PID 1 in the container and it doesn't forward shutdown signals to data prepper, which is on a child process.
With exec, data prepper will replace /bin/bash process and runs on PID 1 so it is able to receive signal and respond to Ctrl+c.
Issues Resolved
Closes #1816
Check List

[ ] New functionality includes testing.
[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[ ] Commits are signed with a real name per the DCO

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #1847 (80c7e40) into main (1aff0e6) will decrease coverage by 0.22%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##               main    #1847      +/-   ##
============================================
- Coverage     94.17%   93.95%   -0.23%
+ Complexity     1526     1522       -4
============================================
  Files           192      192
  Lines          4465     4465
  Branches        363      363
============================================
- Hits           4205     4195      -10
- Misses          179      190      +11
+ Partials         81       80       -1

Impacted Files
Coverage Δ

...opensearch/dataprepper/pipeline/ProcessWorker.java
73.07% <0.00%> (-19.24%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

How does the exec command affect running the script directly from the .tar.gz directory? (ie. not from Docker).

I was able to pass tarball smoke tests without issues.
I expect exec to just change which process data prepper is run in:
Without exec, the processes are like this:

With exec, it's like this:

I'm not sure if it has other side effect though.

Thanks for the additional explanation!


Installer Will Not Work With Buster

Hi,
As the title says the installer will not work with the latest Raspbian Buster Release.
php7.0 needs to be replaced with php7.3 (Remove the option for 5 as its no longer available?) and libav-tools needs to be replaced with ffmpeg.
I have not tested but I think the command line syntax for avconv and ffmpeg should be the same, when I was researching time-lapse I found I could interchange the arguments. So maybe a just find-replace will do to correct things.
I cant really drive git, but can happily test if someone can...

After installing this on Jessie I did a dist-upgrade to buster.  So far everything seems to be fine.  The only issue I ran into was the /etc/passwd was changed to the following (probably by apache?):
www-data:x:33:33:www-data:/var/www:/usr/sbin/nologin
I changed it back to:
www-data:x:33:33:www-data:/var/www:/bin/bash
Everything seems to be working now.   I can't speak to your install issue.

Thanks for the comments.
I have just returned from vacation and will be trying out Buster over the next few days and making any amendments as needed. I also have to be careful about just removing things like php version support as some users don't want to upgrade OS.

Hi,
@jinksto
If you did an update you will probably find that you still have php7.0, not 7.3, I saw this and and a post in the forums saying the same.
@roberttidey
True, I was stuck looking forward :) I have a couple of redundant cam setups I can trial stuff on if you need any assistance..

I have made some changes to installer for Buster / php (defaults to 7.3)
I have tested on Apache. nginx might need further changes

I'll have a play later, I did see feedback on the forums that the installer now no longer works on older releases....

Hi,
Apache on Buster works as expected so far.
I tried Lighttpd, the install worked however, the Cam subfolder does not seem to be working as it does in Apache.
For example I want "mycam" as the sub folder...
Files are installed in /var/www/mycam however if I point my browser at http://myip.addr/mycam I get a 404 , I have to go to http://myip.addr/

Not sure at the moment what is causing the lighttpd issue.
Can you try installing in mycam as before and checking that say the file loading.jpg exists in the /var/www/mycam folder? Then browse to http://myip.addr/mycam/loading.jpg should bring up a simple 'loading' image. This just tests the lighttpd is responding.
If that doesn't work it probably means the lighttpd.conf file format has changed.
Check /etc/lighttpd/lighttpd.conf
That should have a line server.document-root  =
and this should point the path for the web files.
If it doesn't could you zip and attach your lighttpd.conf file

Hi Bob,
I'm fairly certain the sub-folder was being used with respect to the local path, as I said /var/www/mycam contained all the usual files and folders, however using the sub-dir in the URL didnt work.
If I get 5 tonight I'll flash another SD and try again with lighttpd, I wanted to get something running so reverted to Apache.

Having looked at the set up more closely, I think the lighttpd may behave differently to the apache.
The apache set up expects the sub-dir in the URL as the web root is left alone. This can make it easier if Apache is being used for other web apps as well. However, the lighttpd part of the install sets the web root up to include the sub-dir so that an access to the ip works without the sub-dir.
The difference is a bit confusing so I'll either clarify in the documentation or take out the sub-dir for lighttpd.
If you wanted to try out the latter case then you could try changing line 253 of install.sh to
sudo sed -i "s/^server.document-root.*/server.document-root  = "/var/www"/g" /etc/lighttpd/lighttpd.conf
before running it

Sorry Bob, have I lead you up the garden path here ? I've not used the other servers before only Apache, I had assumed they would all work in the same fashion, should have checked first, I do apologize.
Ref the PHP version, can you chose 7.0/7.3 in the script ? The text in the script requester only shows 7.3. Not a lot of room but a note could be handy Deb 9=7 Deb 10=7.3 ?

You should be able to enter any php version in the parameters at the start of the install. It defaults to 7.3 but you can change it to 7.0,7.1,7.2


Window resize

First thanks for great component, problem is component dont react to window resize, its possible to fix this?

Hey @patie, thank you for giving me an issue. Actually, It react to the window resizing. But you should scroll over it once again. Try it please ._.

https://github.com/BosNaufal/vue2-scrollbar


feat: Basic Windows support

[x] https://github.com/txpipe/oura/pull/19
[X] Make Oura builable on Windows (b50290692f8d3f947820f098e264b72dbaaad8a8)
[x] Add Windows to CI
[x] Add basic documentation

@scarmuega this should be now ready to be merged in...

@scarmuega this should be now ready to be merged in...


[BUG] Mipmap dropped - Lowers overall textures - Important - 1.20.1 Fabric

[Worker-ResourceReload-0/WARN]: Texture beautify:block/trellis_weeping_vines_hanging with size 20x16 limits mip level from 4 to 2
Version: Fabric 1.20.1
Beautify: 1.0.0+1.20

Just change the textures to 32x16 like so:

Sorry for taking so long to see this,  thank you very much


Make swap_validator_set test reuse a different set of nodes

The swap_validator_set test used to reset and reuse nodes 1-3. However, these also happen to be all the known peers of node 1. So when nodes 1-3 is restarted, node 1 has no known peer that would have the full knowledge of the chain, which might prevent it from syncing properly. This is an edge case that isn't very realistic, which is why this PR makes the test reuse nodes 1, 4 and 5 instead. This way nodes 2 and 3 won't be reset and node 1 will have 2 known peers from which it will be able to sync.

bors r+


Scheduler Page - showing connection count zero on every scheduler

Describe the bug

scheduler has some count but in list view it does not show

https://www.berrycast.com/conversations/4efe0471-6c59-5421-9071-3a62d227ad76

https://www.berrycast.com/conversations/20d3165c-fcfa-53a1-a31e-3bcb63b46789


Pattern: Table of Contents Design QA testing

User Story

As a [user role below]:
DDS Designer and Developer

I need to:
test the Table of Contents

so that I can:
be sure the developer's code correctly works as designed

Additional Information

Design specs issue (#2008  )
Functional specs issue (#1827  ) and (#2052)
Design and Functional specs Box link
Functional Specs updates:
Added Link List — text as optional 3 annotations
shifted sticky/fixed behavior to table of content 2 in annotations
Dev issue (#1851)
Prod QA testing issue (#2259 )

Tasks
Ensure the Callout pattern has been tested and reviewed by design + dev.
Acceptance criteria

[ ] Pattern is reviewed by designer and design defects are identified
[ ] New issues are opened to log individual defects
[ ] Screenshots of as-is and to-be design should be added to the issue when needed
[ ] Developer associated with building the pattern is assigned to the new issues
[ ] Appropriate labels are added to the issue  eg.  bug, dev

@wonilsuhibm @RobertaJHahn
The update for TableOfContents got merged in and it's ready for review,
Thank you!

@RaphaelAmadeu @RobertaJHahn Can you please provide the storybook link for testing?

https://ibmdotcom-react-canary.mybluemix.net/?path=/story/patterns-sub-patterns-table-of-contents--with-heading-content

@RobertaJHahn Design QA is completed for this pattern. Shixie has logged the following issues:

[ToC] Children and optional rule should scroll away, not sticky https://github.com/carbon-design-system/ibm-dotcom-library/issues/2516

[ToC] Blue bar on selected item should slide up and down the rail, not fading on and off  https://github.com/carbon-design-system/ibm-dotcom-library/issues/2520

[ToC] mobile scrolling page vibrates to the position of ToC dropdown https://github.com/carbon-design-system/ibm-dotcom-library/issues/2545

[ToC] Buggy scrolling and state change
https://github.com/carbon-design-system/ibm-dotcom-library/issues/2559

[ToC] Styling issues
https://github.com/carbon-design-system/ibm-dotcom-library/issues/2557


Normalize makefiles for windows compatibility

This PR normalizes the makefiles  so they are compatible with windows.

I'm closing this one. The source tree and Makefiles have changed a lot. I'll revisit this again and submit a new PR


edge types when passing messages

Hello,
Is it possible to have multiple types of edges and/or is it possible to distinguish edge types during message passing phase (in model_description)?
thanks in advance.

Dear @guelfaure,
Thank you for reaching out!
Regarding your question about having multiple types of edges and distinguishing between them during the message-passing phase, currently, IGNITION differentiates edges based on their source/destination nodes. Therefore, in cases where you have a Multigraph (graphs with one node pair having more than one edge), there's no explicit way on how to tell IGNITION to differentiate between them.
However, to address this limitation, one potential workaround could be to transform the edges into nodes. These nodes would simultaneously connect their respective source/destination nodes and define a new message-passing mechanism between them. While this solution may not be optimal, it could serve as a means to overcome the current limitation.
I want to assure you that we are actively working to enhance IGNITION, and your feedback will be valuable in shaping future versions to better accommodate such requirements.
Having said that, we will work to take this into account in future versions of IGNNITION.
Best regards,
Miquel


No instructions to set CF org and space

When I try to do my first cf push, I get an error:
$ cf push
FAILED
No org and space targeted, use 'cf target -o ORG -s SPACE' to target an org and space

The issue was that I hadn't fully set up my PWS account.  After verifying my email address, there wasn't any indication that there was still more configuration to do (e.g. create an organization).


[WIP] Build refactor

This is some work for project cleanup

[x] Split the Makefile
[ ] Add mixed build type for both wasm and legacy support;
[ ] Migrate from autotools to meson, to reduce patches and the build time by ≈25%;
[ ] Add support for build flags (DEBUG, ENABLE_PTHREADS, ENABLE_LTO);

e.g.: make ENABLE_LTO=true DEBUG=true

I merged most of the small commits unrelated to the build system changes.
As for the git clean change, not removing untracked files from our root repo makes a lot of sense to me, but the benefit isn't as clear to me for the submodules. Do you have an actual use for untracked files in the submodules? Stray files there may taint the licensecheck results and cause issues on commit updates if they collide with newly added files.
I'll write more regarding the build system changes at a later date, but I can already see that this commit does too many unrelated things at once.

I'll split this into multiple PR, for better review the changes.

Multiple commits in one PR is probably sufficient. If you prefer, feel free to use multiple PRs though.

Next, some remarks from my notes on the initial version and not contained in the current commits:

Please do not require bash specifically if nothing specific to bash is being used. And iinm we currently do not use any bashisms in our build, so unless there’s a good reason we should probably continue to work with any POSIX shell.

The old commit message the primary goal of the switch to Meson was to “reduce the number of patches.”. It doesn't appear those two are correlated at all:

The harfbuzz/00002 patch seemed superfluous regardless of which build system is used
According to #103 the Fontconfig fcstat patch is supposedly unneeded only after we bump our vendored Fontconfig version. If I didn't miss something, you did not bump the version but were removing the patch.
I did test bumping fontconfig and removing the patch a couple of weeks ago: while it built, at runtime I was getting errors regarding fcstat, but hadn't yet have time to investigate further. Have you checked for runtime errors after you removed this patch?
Other than the two patches above it appears that the only patch which can be removed maybe because of meson is freetype/0001-disable-exports. In my testing removing the patch without changing to Meson, did not cause any build problems. What issues did this try to fix?

Now regarding the switch the benefits and drawbacks of switching many subprojects to Meson in the context of JSO.
There are some time-savings in Meson using Ninja as a backend and that it compared to autotools from git, only does one configuration step and likely does it quicker. However, I suspect the bulk of the speed improvement you measured comes from the hardcoded eight jobs being replaced by ninja’s default behaviour of using as many jobs as there are logical CPUs available.
Eight jobs are too much for GitHub Action runners, which advertise two logical CPUs, and in local builds it may be either too much or too little. And in some cases, like FriBidi, our build always only uses one(!) thread (probably the -j 8 parameter was forgotten, something which could be avoided by using macros to avoid copy-paste).
This by itself could also be easily achieved with Make, but sure using Meson also gives the other benefits listed before, so why not.
However, regarding speed there’s one thing that would be even better than using a more appropiate job count for each project separately and which is possible with Make but not Ninja (and therefore Meson if it cannot do a “mega-build” in which all projects use Meson): parallelise not only the individual (sub)project builds but also across all targets by using a jobserver. This means if one project no longer needs all the threads, another target can already be executed.
I started an attempt at this a few months ago, but it seemed like (probably) the emmake wrapper interfered with the relevant jobserver arguments. I had the idea of removing all the emmakes in the Makefile and instead calling the root Makefile with emmake, but never actually did because other things came up which took precedence.
If the jobserver can be made to play nicely with emmake the gains from it may possibly outperform the Ninja and configure related gains from Meson. The catch is HarfBuzz having deprecated its autotools build, so once we switch HB to Meson, it either will consume more threads than we’d like or we need to ensure HarfBuzz specifically is not run in parallel with other builds.
There also is a patch series (ninja-build/ninja/#1140) to add jobserver support to Ninja since almost 6 years which is still maintained and updated. The last response from a Ninja dev is from 2 years ago though, which doesn't exactly inspire confidence in this getting merged anytime soon.
Since we have multiple CMake-only, at least one autotools-only with prospective two more additional projects, a Meson-and-ninja-only “mega-build” seems unlikely to happen. Using top-level meson with experimental non-Meson subprojects will also suffer from not being able to parallelise across projects (in addition to it being experimental and the warnings from the docs).

Which are the cmake-only projects?
freetypeand harfbuzz both support Meson, cmake, and configure+make all at once, very dedicated of them.
fontconfig and fribidi both support meson and configure+make
expat and brotli both support cmake and configure+make
libass is autotools only, but has work on porting to meson.
None of those seem to be cmake-only, and only libass itself is configure+make only.

Btw, since JSO compiles from git not from a tarball, the difference between a proper standard autotools setup (e.g. libass) and custom config+make systems (in FreeType’s case a thin but required wrapper around autools) is relevant as the configuration steps differ.

expat and brotli both support cmake and configure+make

I missed them supporting an autotools build; then it’s 2× CMake-or-autotools not CMake-only. Doesn't make much of a difference though, since both have a Make backend and are not Meson.
WrapDB doesn't seem suitable as explained in another comment.

libass is autotools only, but has work on porting to meson.

That port only aims for Meson as a second-class system missing some features and e.g. X32, possibly enough for JSO though. Also not certain when this comes to a conclusion. But then still, libunibreak and libiconv also use Make-based systems and might be added in the future.
If I understood your explanation correctly, with a Meson-at-toplevel build using the experimental “external project” feature, the individual external projects and those controlled by Meson will use distinct thread pools which together can exceed the user-chosen limit. If so, using it does not seem desirable.
Our options then would be about if we want cross-(sub)project parallelisation. If yes, we should avoid ninja-backed systems when possible (and take a look if HarfBuzz’s CMake system will continued to be supported or is also deprecated). If not, using Meson when provided as a first-class build-system is likely slightly faster than using a Make-based system. In both cases we would stick to GNU Make at top-level.
If at some point in the future Ninja gains jobserver-client support, we can with GNU Make at the toplevel still get both Meson for the subprojects and cross-project parallelisation.

and take a look if HarfBuzz’s CMake system will continued to be supported or is also deprecated

Eh... it was removed once already, and then reverted and re-added with the rationale that "there is no need to rush" to remove it, to prevent people being caught off guard. They state in various PRs that they're not keeping it around forever.

If at some point in the future Ninja gains jobserver-client support, we can with GNU Make at the toplevel still get both Meson for the subprojects and cross-project parallelisation.

But you can use Kitware's ninja fork which does have jobserver-client support, but not jobserver support -- this can generally be worked around even for a ninja-first build with a simple Makefile:
all:
	@+ninja

It is true that at the rate things are going, the ninja devs will likely never merge it -- but, Kitware regularly rebases that patchset for new releases and this is e.g. where pip install ninja is sourced from. There are people very invested in that feature. Just don't bother with the one from Debian's repository in that case.


Received unexpected response from YouTube.

Can you help me? I got an error
{
  playlistInfo: {},
  exception: {
    severity: 'SUSPICIOUS',
    message: 'Received unexpected response from YouTube.'
  },
  loadType: 'LOAD_FAILED',
  tracks: []
}

problem has been solved in discord. im closed


Externalize authentication

Is your feature request related to a problem? Please describe.
Thanks for this great work. I'm using my google account to authenticate though their mobile app to the Anova APIs. The current implementation only supports username/password.
Describe the solution you'd like
Would it be possible to move the authentication part out of this library and let an external config flow (e.g. in Home Assistant) deal with authentication and token refresh?  Thus just passing the token to this library.
Additional context

The approach I would rather take is that Anova appears to have a code login. So using that as a means to login would bypass these different authentication methods theoretically


Fix bug image field with disk

If you set a disk on image field, the old value of image was broken.
It appended the entire url to the $value which generated wrong image link(http://localhost/http://localhost/imagename.jpg).
I don't know if it is the best way to fix it, but, for me, was a fast fix.

A new inspection was created.

The inspection completed: No new issues

@teamupdivision @pxpm I do think it not needed to change many line, base on my Quick fix after i change from local to using disk on s3. the problem lie on the condition disk they check
from this (in disk condition they didn't provide old value but direct url)
    $value = $value
        ? preg_match('/^data\:image\//', $value)
            ? $value
           : (isset($field['disk'])
                ? Storage::disk($field['disk'])->url($prefix.$value) // This line
                : url($prefix.$value))
        :''; // if validation failed, tha value will be base64, so no need to create a URL for it

to this (the problem duplicate disk url solve in validate error)
    $value = $value
        ? preg_match('/^data\:image\//', $value)
            ? $value
            : (isset($field['disk'])
                ? (
                    old(square_brackets_to_dots($field['name']))
                    ? old(square_brackets_to_dots($field['name']))
                    : Storage::disk($field['disk'])->url($prefix.$value)
                )
                : url($prefix.$value))
        :''; // if validation failed, tha value will be base64, so no need to create a URL for it

perhaps url($prefix.$value)) also need to check the old value as well because it not in my use case.

Hi everyone!
Besides the broken URL on form validation errors, image field had other issues related with disks.
We decided to takle everything together on https://github.com/Laravel-Backpack/CRUD/pull/3449.
Let's move further conversations there 🙌

Hi everyone!
Besides the broken URL on form validation errors, image field had other issues related with disks.
We decided to takle everything together on https://github.com/Laravel-Backpack/CRUD/pull/3449.
Let's move further conversations there 🙌


bug report ...

Note: for support questions, please join our Discord server

I'm submitting a ...
[ ● ] bug report
[ ] feature request
[ ] question about the decisions made in the repository

Action taken (what you did)

binance 1.3.3
https://gist.github.com/askmike/2c4b8e9201c380503ac347ff69c199d5

Expected result (what you hoped would happen)

I think the calculation seems to be wrong.

Actual result (unexpected outcome)

Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, etc)

what do you mean with sell timing?

@askmike I thought I should sell, but he tried to buy. (Sorry my English is very poor.) ^^

I thought I should sell

Your strategy told Gekko to (try to) sell. Note that Gekko actually didn't sell since you had insufficient funds. Unless you have logs showing that your strategy actually triggered a LONG advice and Gekko still tried to sell I am assuming this is an issue with your strategy (or with your understanding of the strategy).
Please post this here instead: https://forum.gekko.wizb.it/forum-12.html
Since this is the bug tracker for the project (not third party strategies).
Note that it will be very hard to debug the strategy if it doesn't include any logging. People on that forum can help you add that to the strat.

@askmike thank you~


How to show progress while creating a squashfs image?

I'm trying to show progress in a way similar to mksquashfs does. With mksquashfs is shows each byte as it's being written, but I'm unsure how I'd do that with this crate.

I guess what I'm looking for is a way to figure out what the resulting image's size will be before calling FilesystemWriter::write. I'm not sure how mksquashfs does it, but is there any way to calculate that ahead of time if that's what's needed?

I pushed https://github.com/wcampbell0x2a/backhand/pull/274, which should ( I haven't tested this enough) give the amount of uncompressed bytes that are compressed into the image.
I think squashfs-tools/unsquashfs just gives the amount of uncompressed bytes that it read, as it's almost impossible (?) to know how many bytes the compressed size will be before you compress the bytes. It then increments the progress bar as it compressed those bytes.
Time willing, I want to create my own mksquashfs: https://github.com/wcampbell0x2a/backhand/issues/21
As far as the progress bar as you write bytes, you will just need to have your own wrapper around Write, which understands and increments the progress bar as you call the wrapper around write().

I'm a bit confused on how I'd use that to get a progress bar going @wcampbell0x2a. Sorry if I'm overlooking something, but I'd need to know how many uncompressed bytes have already been written in order to do what I'm needing, right? I've tried wrapping Write, but getting buf.len() from Write::write appears to be showing the number of compressed bytes that are about to be written out, not the number of uncompressed.
You mentioned that FilesystemWriter::uncompressed_size would list the size of uncompressed files, but that doesn't include (among other things) the bytes to store the compression used, right?
The way I'm thinking it'd be done is that FilesystemWriter::write could support specifying a closure (maybe even under FilesystemWriter::write_callback if that'd be better too), which will get called every time the Write trait object is called internally. The closure could be passed how many uncompressed bytes have been written, and what the total number of uncompressed bytes that will be in the SquashFS image (including things like the bytes for compression info).
Let me know if I'm just overlooking something too, I was just throwing out some ideas from what I saw.

Honestly I don't even need to know the size of compression info, I think it's a good enough metric to know the total size of all files and the size of all files that have been written. I'm planning on just providing a percentage of progress done anyway, so it doesn't really matter to me.
I'm looking at the output of mksquash and it doesn't look like they use any specific things for the numbers used in the progress bars anyway, so leaving out miscellaneous squashfs metadata is more than fine by me.

I stepped away from my computer again, havent really read your reply thoroughly.
Instead of wrapping the Write, I think you could wrap the Read instead. Read at the point of being used by my DataWriter should be only the uncompressed bytes.

I didn't think about that, I could definitely just see as bytes are read and then total it up like that.
I've just got two questions though:

Is there any guarantee that Read calls will only happen when FilesystemWriter::write is called?
Is there any guarantee that a call to the Read object won't try to read the file more than once?

I'm assuming that might be how it's done already, but I think it might be good to document that as otherwise I think it'd be easy to not assume, and then not know how to implement some kind of progress reporting.

Can confirm my custom Read wrapper works as intended, I just read file sizes when opening up the files and then have a separate Arc<Mutex<u64>> that I track the number of bytes read in.
This issue's effectively fixed for me, as long as those two questions I had can be confirmed then it'll be good to get closed :)

Is there any guarantee that Read calls will only happen when FilesystemWriter::write is called?

I think once FilesystemWriter is created all Read calls will be correctly counted. But if you are dealing with FilesystemReader and Squashfs they will be using that same reader.

Is there any guarantee that a call to the Read object won't try to read the file more than once?

Yes, it's allowed to Seek around but items should be only read once and reading more would be a bug if found. Having said that, I don't have a mksquashfs so I don't know for certain this is a thing!

Interestingly, this progress bar library has a wrap_read already: https://docs.rs/indicatif/latest/indicatif/struct.ProgressBar.html#method.wrap_read
I'll close this unless you have more questions.

Oh cool, I didn't realize that library had that. My use case actually uses indicatif, so I'll look into porting my code over to that. I'm all good on my end though, thanks a ton for helping me get this resolved!


Add terminfo for Alacritty

I use Alacritty as my terminal, and a program I use that utilizes this library doesn't work because of the lack of terminfo for Alacritty. Running ./mkinfo -go term_alacritty.go and using my local version with that added file works. Running go test passes.
I'm still unfamiliar with Go and its ecosystem, so if there's something more I need to do to verify this works properly, or something else I need to change, please let me know.

All done. Sorry it took a while.


Does not build Test project running under Windows SDK 1.1 release

Attempting to compile test project based on these templates produces the following error.
Packaged .NET applications with an app host exe cannot be ProcessorArchitecture neutral. Please specify a RuntimeIdentifier or a Platform other than AnyCPU.	C:\Users\neil.nuget\packages\microsoft.windowsappsdk\1.1.0\buildTransitive\Microsoft.Build.Msix.Packaging.targets	1016
Fails this condition in .targets file...

Version 0.3.0 was just released to the marketplace, could you see if that fixes the issue you have? If not, can you share what your project setup is?

Closing due to staleness, if you are still encountering this issue feel free to reopen this issue.


Add a TConnectionInitializer optional callback for sql_database and sql_table resources

Feature description
I would like the ability to configure the SQLAlchemy connection at a lower level before TableLoader._load_rows() begins reading data. Specifically, I need more flexibility than just exposing execution options (as done with execution_options). This includes the ability to execute raw SQL statements to set various PostgreSQL session-level configurations.
The current implementation exposes some options via execution_options, as shown below:
def _load_rows(self, query: SelectAny, backend_kwargs: Dict[str, Any]) -> TDataItem:
    with self.engine.connect() as conn:
        result = conn.execution_options(yield_per=self.chunk_size).execute(query)
        ...

While this approach is helpful for setting execution options (like yield_per or isolation_level), it does not provide a mechanism to execute raw SQL statements at the connection level before data loading. The ability to influence the connection itself before query execution is essential for certain use cases, such as setting specific transaction isolation levels, adjusting session-specific parameters, or executing SET commands (e.g., SET TRANSACTION SNAPSHOT).
The feature would allow the use of session parameters essential for data retrieval tasks, such as:

Transaction settings: default_transaction_isolation, to control the isolation level during read operations (e.g., REPEATABLE READ or SERIALIZABLE for consistency).
Timeouts: Session timeouts like statement_timeout to prevent long-running queries from consuming excessive resources.
Client connection parameters: client_encoding to ensure correct encoding for reading non-ASCII data.

Yes, I'm already a dlt user.
Use case
I frequently need to configure transaction isolation and other session parameters when reading data from PostgreSQL. For instance, setting SET default_transaction_isolation = 'REPEATABLE READ' would allow maintaining consistent reads throughout a transaction. Additionally, statement_timeout can help mitigate long-running queries in environments with large datasets by capping execution time.
Proposed solution
Introducing an additional parameter that allows a callback function to be passed, which can modify the SQLAlchemy Connection object before the query is executed. For example, something like this:
from sqlalchemy.engine.base import Connection
TConnectionInitializer = Callable[[Connection], Connection]
conn_init_callback: Optional[TConnectionInitializer] = None

This conn_init_callback could then be added as an optional parameter to sql_database or sql_table so that users can apply custom connection-level settings before any data is read. It would be passed as part of the configuration and invoked within the connection context, allowing users to set session-specific behaviors dynamically.
Related issues
Currently, there are no related issues as I have already forked the source and implemented the required changes within my own codebase. However, now that the sql_database component has been integrated into the core library, it would be beneficial to avoid having to replicate the entire codebase just to introduce this one additional parameter.

There's a related PR for similar mechanism for Engine #1919
@steinitzu let's take a look at this. we may need some better user interface than a list of callbacks in the arguments which is constantly growing. maybe people should be able to import a hook module into our code? we are adding pluggy into our code base so that could be used to customize this thing.
it is clear that we need to let some of our users to interact "almost" on the code level.

@rudolfix I'm going to close this since I've found my workaround now that I've figured out how I can customize the sqlalchemy Engine. It's not ideal but this is what I'm doing...
engine = _configure_engine(credentials, rep_conn)

@event.listens_for(engine, "begin")
def on_begin(conn: ConnectionSqla) -> None:
    cur = conn.connection.cursor()
    if slot is None:
        # Using the same isolation level that pg_backup uses
        cur.execute(
            "SET TRANSACTION ISOLATION LEVEL SERIALIZABLE, READ ONLY, DEFERRABLE"
        )
    else:
        cur.execute("SET TRANSACTION ISOLATION LEVEL REPEATABLE READ")
        cur.execute(f"SET TRANSACTION SNAPSHOT '{slot['snapshot_name']}'")
...
sql_table(  # type: ignore[name-defined]
    credentials=engine,
    table=table_name,
    schema=schema,
    included_columns=include_columns.get(table_name),
)

Not exactly ideal but it'll do for now :sweat_smile:

@neuromantik33 in the meantime we added engine adapter in #2070


Export Resume not working

Exporting to single page, multipage is not working for my resume.
When I go to the preview link and press Cmd + P, then the content of the resume overflows from 1st page to 2nd page.

Can you provide an example?

https://rxresu.me/r/hxk2k6
Try this one I created. cmd + P, makes the content overflow to 2nd page.

The only problem I could find is that when converting to pdf the new document has slightly bigger side margins which lead to unexpected behavior. The resume you provided is on the verge of overflowing and this small margin difference causes some of the text to wrap sooner than it is supposed to as seen in the screenshots.

Pdf:

Your resume:

To fix this could you try shortening just that part and see if the issue persists?

@HristovCodes Could you try exporting as single page/multi page now?


Removed references to unused event stream collate type.

Closes #81

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 63.77%. Comparing base (2a94993) to head (32845f5).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@                  Coverage Diff                   @@
##           55_dataset_cleanup      #85      +/-   ##
======================================================
- Coverage               64.17%   63.77%   -0.41%
======================================================
  Files                      10       10
  Lines                     723      715       -8
======================================================
- Hits                      464      456       -8
  Misses                    259      259

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

I believe the test failures here will be solved by #88, so we can wait to merge this until that goes in.


"form-control-has-label" should take into account aria-hidden

I think it would make sense to not report "form-control-has-label" when the given element or one of its parents have aria-hidden="true" set since in those cases accessibility doesn't apply to that element.
This issue might apply to other rules also (maybe all?).

makes sense to me

but anyway, what would be the use case of a aria-hidden input?

Here we have a statement from MDN that says that no focusable element should have a aria-hidden property into it, and it kinda makes sense.

According to the fourth rule of ARIA, aria-hidden="true" should not be used on a focusable element. Additionally, since this attribute is inherited by an element's children, it should not be added onto the parent or ancestor of a focusable element
https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/ARIA_Techniques/Using_the_aria-hidden_attribute

In the specific case that prompted me to file this, the input was a hidden file input used for uploading an avatar image in a programmatic way.

but isn't there a replacement UI element for interacting with this input[type=file]?

maybe you could only point the aria-labelled-by to the UI element that interacts with the input

but isn't there a replacement UI element for interacting with this input[type=file]?

There might be but I would guess is more modern and maybe less backward-compatible (which might not matter anymore I guess).
But when we think about this issue in more generic terms, wouldn't it always make sense to ignore aria issues on elements that have aria-hidden set (on itself or ancestor and irrespective of specific use-cases)?

I guess it does make sense... :thinking:

Hi! Sorry I'm finally getting back around to these issues. Could you give some example HTML of what would be valid/invalid here? Want to make sure I'm understanding correctly.

Hi! Sorry I'm finally getting back around to these issues. Could you give some example HTML of what would be valid/invalid here? Want to make sure I'm understanding correctly.

Valid

  <input value="1" type="text" />

Invalid

  <input value="1" type="text" />


fix(event): uses Object.prototype.toString.call on objects

Description:
Objects created with a null prototype do not have a toString method.

Coverage increased (+0.0004%) to 97.686% when pulling 1c02451f22c65c6458712d984d19370b2565fd08 on estobbart:master into 836fb1f9e99dfa9a86e9d180d0b50c73dee78b50 on ReactiveX:master.

Coverage increased (+0.0004%) to 97.686% when pulling 1251c10dc1c49b105a274b709920e8bf83b406e2 on estobbart:master into 836fb1f9e99dfa9a86e9d180d0b50c73dee78b50 on ReactiveX:master.

For completeness, can you give a real world example of why someone would listen to events on an object without a prototype?

If you create a WebKit browser, for example GTK, and then use JavaScriptCore to add a custom JSObjectRef that fires events, JSObjectMake accepts a JSClassRef structure, to be used as the prototype.

Seems legit. Thanks.
LGTM


To include or not to include the text from the initial and final tweets

Another one from @dkiesow
The current behavior is to include in the text file the final tweet (sans the @TweetsToText mention), but not the initial tweet.
This does feel asymmetric and non-intuitive to me.
The behavior is based on the endpoint of Twitter's API that we use to get the tweets, which returns every tweet after since_id the initial one up to and including the max_id.
But it occurs to me as I'm writing this...since we are storing the initial tweet, it could be easily popped into the set of tweets that's processed into the text file.
So which is more intuitive:

Include text from the first and final tweets?
Include only text from all the tweets in between?

One election night user told me, unprompted, that he expected to see his first tweet in the text file.
Currently, I'm thinking it's better to give them tweets they don't want (which they can delete) than to exclude tweets they do want (which they would have to re-type or copy/paste).


CostModel data definition has non-strict fields and wrong NoThunks instance

I ran the db-analyser noThunks check and found one thunk, here:
https://github.com/input-output-hk/cardano-ledger/blob/51d97a7faeec32f3825a21d775ca70b6a05fd092/eras/alonzo/impl/src/Cardano/Ledger/Alonzo/Scripts.hs#L206
I don't think this is cause for alarm, since it's not involved in any iteration or risks retaining much, as far as I anticipate. However, we should fix it, if only so the noThunks test passes.

Would it be fine to mark the parameters Map and the EvaluationContext as strict?

This instance need not use InspectHeap: you should instead deriving (Generic) on CostModel and just write instance NoThunks CostModel.

https://github.com/input-output-hk/cardano-ledger/blob/51d97a7faeec32f3825a21d775ca70b6a05fd092/eras/alonzo/impl/src/Cardano/Ledger/Alonzo/Scripts.hs#L241

Moreover, if the Map and/or EvaluationContext thunks are intentional, then we'll need to handwrite the wNoThunks in that instance to not check those arguments for thunks.

@Jasagredo kindly pointed out that there still seems to be an unexpected thunk in the EvaluationContext. I'll re-open this issue.

See https://github.com/input-output-hk/plutus/issues/4687


helm_resource did not wait for resource_deps on helm_repo

Hi all, I bumped into a race condition recently in a CI run where helm_resource was supposed to wait for helm_repo to finish but did not. Here are some logs from what happened:
vm-charts │ Initial Build
grafana-char… │
grafana-char… │ Initial Build
grafana-char… │ Running cmd: helm repo add grafana-charts https://grafana.github.io/helm-charts --force-update
    vm-charts │ Running cmd: helm repo add vm-charts https://victoriametrics.github.io/helm-charts --force-update
ingress-char… │
ingress-char… │ Initial Build
ingress-char… │ Running cmd: helm repo add ingress-charts https://kubernetes.github.io/ingress-nginx --force-update
    vm-charts │ "vm-charts" has been added to your repositories
   vmoperator │
   vmoperator │ Initial Build
   vmoperator │ STEP 1/1 — Deploying
   vmoperator │      Running cmd: python3 /home/runner/.local/share/tilt-dev/tilt_modules/github.com/tilt-dev/tilt-extensions/helm_resource/helm-apply-helper.py
   vmoperator │      Running cmd: ['helm', 'upgrade', '--install', 'vmoperator', 'vm-charts/victoria-metrics-operator']
   vmoperator │      Release "vmoperator" does not exist. Installing it now.
ingress-char… │ "ingress-charts" has been added to your repositories
      grafana │
      grafana │ Initial Build
      grafana │ STEP 1/1 — Deploying
      grafana │      Running cmd: python3 /home/runner/.local/share/tilt-dev/tilt_modules/github.com/tilt-dev/tilt-extensions/helm_resource/helm-apply-helper.py --values grafana/values.yaml
      grafana │      Running cmd: ['helm', 'upgrade', '--install', '--values', 'grafana/values.yaml', 'grafana', 'grafana-charts/grafana']
      grafana │      Release "grafana" does not exist. Installing it now.
      grafana │      Error: repo grafana-charts not found
      grafana │      Traceback (most recent call last):
      grafana │        File "/home/runner/.local/share/tilt-dev/tilt_modules/github.com/tilt-dev/tilt-extensions/helm_resource/helm-apply-helper.py", line 66, in <module>
      grafana │          subprocess.check_call(install_cmd, stdout=sys.stderr)
      grafana │        File "/usr/lib/python3.10/subprocess.py", line [36](https://github.com/lacework/agent/actions/runs/5081096334/jobs/9137856036#step:7:37)9, in check_call
      grafana │          raise CalledProcessError(retcode, cmd)
      grafana │      subprocess.CalledProcessError: Command '['helm', 'upgrade', '--install', '--values', 'grafana/values.yaml', 'grafana', 'grafana-charts/grafana']' returned non-zero exit status 1.
      grafana │
      grafana │ ERROR: Build Failed: apply command exited with status 1

The Tiltfile section that caused that is
# Install Grafana Helm Charts
helm_repo(name='grafana-charts',
          url='https://grafana.github.io/helm-charts')
helm_resource(name='grafana',
              chart='grafana-charts/grafana',
              flags=['--values', './dev/grafana/values.yaml'],
              port_forwards=[3000])
watch_file('./dev/grafana/values.yaml')

Here, grafana has a dependency on grafana-charts, but in the logs above, the chart was not found!
I went ahead and did some triaging in the hopes that it would be useful. My suspicion for what happened:

helm_repo uses the Tiltfile local_resource API (https://github.com/tilt-dev/tilt-extensions/blob/13280048812f95896150b6fcf23462bb501d250d/helm_resource/Tiltfile#L158)
However, local_resource returns "ready" to Tilt only when the process is started (and not when it is finished!), ctx: https://docs.tilt.dev/local_resource.html#readiness_probe.
That means there is a potential race where:

helm_repo is called and starts the helm repo add
helm_resource, which is dutifully waiting on helm_repo to signal "ready", gets the all-clear from Tilt as the process was started
helm_resource attempts to install the chart
helm_resource crashes when it does not find the chart
helm_repo finishes installing the chart, alas too late

I propose that helm_repo's call to local_resource adds a new readiness_probe which uses an exec_action of helm repo list -o json | jq -e 'map(select(.name == <name-of-chart>)) != []' to determine success of chart installation.
Let me know if this all makes sense please!

I think you're misreading the docs.
local_resource readiness checks apply to the serve_cmd, not the build cmd. The helm_repo function uses the build cmd. I didn't see anything in your logs to suggest grafana deployed before grafana-charts finished.

Gotcha, thanks for the clarification -- could there be another reason why this would be flaky / racy?

You say you expected it to wait on resource_deps, but I don't see any resource_deps in the code snippet you posted?

I'm not 100% confident 'helm repos add' is concurrency safe. From your logs, it looks like two repo-adds (repos-add?) ran at the same time, but only one printed, which is a bit suspicious. Maybe we could try removing the allow_parallel param from helm_repo and see if that helps?

I'm not sure how to force the race, but I added the problematic code to the test Tiltfile in helm_resource in the hopes of reproducing. Let me know how that PR looks!


Catkin fix v2

Supersedes PR: #376
Related issues: #331 #380
See this for a rough outline of the functionalities added (the issue relating to the missing libraries has been addressed).

Can you comment on the few TODO notes left in the commit? The travis CI reports that two patches do not have a Upstream-Status; do you have plans to adjust the upstream ROS packages to be cross-compilable, or are you already in discussion with the ROS maintainers?

The TODO is not critical. It is a nice to have feature. Currently, it's also necessary to either create a setup script or add the relevant environment configuration as stated in the README.md. So, there is no loss of functionality; I just added it as a reminder.
I haven't made a decision yet whether I should try to push the two patches upstream. It is not a very clean solution to start with, i.e., initially I had a different approach in mind, but it would require bigger changes to catkin.
Also the current approach relies on the fact that gcc will prepend the configured sysroot automatically if the search path for header files are specified like this: -I=/usr/include. So, if a compiler different from gcc is used I'm not sure it will work. This might be a problem in general for this PR, not just for the suitability for an upstream PR.

From reviewing the changes, there are no further concerns from my side. The travis script still reports the two failures: Upstream-Status lines in patches are a good practice in the overall Yocto project, which is relatively easy to live up to and maintain.
On Monday or Tuesday, I will have time to actually run and build some test images with this PR and check if there are some issues on my local setup.

Just for the record: I was able to compile an image and also create a catkin package on the target machine. I haven't tested yet the cross-compilation.

Note: There is an issue with the dependencies of the catkin package. The package should only be necessary if one wants to compile code on the target machine (otherwise catkin-runtime should be suffienent). It should, therefore, depend on the *-dev of gcc, etc. to install the header files, etc. However, we had this QA error when doing that -- I'm not sure how this should be handled.

@dominiquehunziker I hope that you can and will provide a new pull request with this feature. It is a good idea to get the feature running; unfortunately, I just did not have the spare time to test the pull request yet. Next time, I hope to find the time to do some minimal testing and merge the pull request.

Yes, didn't realize that deleting the branch closed the PR. I'm working on a new version, but I'm also a bit short on time.
In the meanwhile I'm trying to push the necessary changes to catkin itself; though the changes will only affect kinetic-devel and probably won't be available in indigo.

@bulwahn I don't know whether I should create a new PR for this, but here is the newest version of the catkin fix. It would be great if you could add your opinion on the catkin PR, which is the same patch as applied in the meta-ros fork.


add persian (fa) locale

add persian language support

@mohammadjavad948 Please add the language along with it's flag emoji to LanguageSelector.tsx component.

@ermalsh ok

@ermalsh  can i create another pull request ?

@mohammadjavad948 yes

thanks


Certificate equality

equals() does not work as intended for X509Certificate, see https://github.com/a-sit-plus/kmp-crypto/blob/5900fa719c63e05d17a42129b61310dbd48d178c/datatypes/src/jvmTest/kotlin/at/asitplus/crypto/datatypes/X509CertificateJvmTest.kt#L137

invalid


notify: update notify/wechat

Accoding to WeChat Work API, we will get response such as:
{
   "errcode": 0,
   "errmsg": "ok",
   "access_token": "accesstoken000001",
   "expires_in": 7200
}

instead of:
{
   "code": 0,
   "error": "ok",
   "access_token": "accesstoken000001",
}

And sometimes the request fails because it uses an expired token
So I did these things to update the code:

Update weChatResponse and tokenResponse;
Use expireIn instead of 2 * time.Hour;
Record the time before we send the request, not after we receive the response;

For test, I wrote the following code:
func TestNotify(t *testing.T) {
        // Use `*` to protect information
	secret := "d2mS-c3*********************************dwKLMbDI"
	u, err := url.Parse("https://qyapi.weixin.qq.com/cgi-bin/")
	require.NoError(t, err)
	n, err := New(
		&config.WechatConfig{
			APIURL:      &config.URL{URL: u},
			HTTPConfig:  &commoncfg.HTTPClientConfig{},
			ToUser:      "binacs",
			AgentID:     "*********",
			CorpID:      "******************",
			MessageType: "text",
			Message:     "binacs: send from prometheus/alertmanager unit test",
			APISecret:   config.Secret(secret),
		},
		test.CreateTmpl(t),
		log.NewJSONLogger(os.Stdout),
	)
	require.NoError(t, err)
	ok, err := n.Notify(context.Background(), []*types.Alert{
		&types.Alert{
			Alert: model.Alert{
				Labels: model.LabelSet{
					"lbl1": "val1",
				},
				StartsAt: time.Now(),
				EndsAt:   time.Now().Add(time.Hour),
			},
		},
	}...)
	t.Log(ok, err)
}

And it works:

Thanks for your review.

Thank you very much for your advice!
I have submitted the latest code. Could you please review it again? @simonpasquier
And the unit test works like this:


Fix #9759 SSMTP sendmail wrapper

Motivation for this change
Fix #9759 in the same way as services.postfix.setSendmail.
Things done

[x] Tested using sandboxing
(nix.useChroot on NixOS,
or option build-use-chroot in nix.conf
on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] OS X
[ ] Linux

[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

@domenkozar @wmertens care for a review? :)

Looks great! Merging.


latest/recent rev appears to break ahash/compile-time-rng usage

We've been using hashbrown in an embedded environment (no os rng) with:
hashbrown = { version = "0.11", features = ["ahash-compile-time-rng"] }
recent (maybe) changes removed the "ahash-compile-time-rng" feature. The current hashbrown Cargo.toml depends on ahash with:
ahash = { version = "0.8.0", default-features = false, optional = true }
which causes ahash to use fixed entropy to generate keys. I don't see how to configure hashbrown so that it depends on ahash with compile-time-rng? (w/o forking/patching the crate)
Am I missing something?

Hashbrown doesn't make any guarantees about the hasher and opts for the fastest performance. If you have specific requirements for a random seed then you should use the ahash crate directly.

Yes, this is not your issue (and thank you for the subtle pointer to the
_with_capacity_and_hasher api). I've tracked this down to the  latest rev
of the const-random crate that ahash depends on--it breaks my no_std usage.
On Mon, Oct 23, 2023 at 4:05 PM Amanieu @.***> wrote:

Hashbrown doesn't make any guarantees about the hasher and opts for the
fastest performance. If you have specific requirements for a random seed
then you should use the ahash crate directly.
—
Reply to this email directly, view it on GitHub
https://github.com/rust-lang/hashbrown/issues/478#issuecomment-1776163507,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABRM7IP7S4657UHBU4L7OKLYA3Z5HAVCNFSM6AAAAAA6MZHRI6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONZWGE3DGNJQG4
.
You are receiving this because you authored the thread.Message ID:
@.***>


Could not open .\linear_regression.pbtxt: Data loss: not an sstable (bad magic number): perhaps your file is in a different file format and you need to use a different restore operator? Traceback (most recent call last):

Please go to Stack Overflow for help and support:
If you open a GitHub issue, here is our policy:

System information
TensorFlow 1.9
Windows 10
Python 3.6 64
You can collect some of this information using our environment capture script:
2018-09-12 19:55:49.880076: I C:\tf_jenkins\workspace\rel-win\M\windows\PY\36\tensorflow\core\platform\cpu_feature_guard.cc:140] Your CPU supports instructions that this TensorFlow binary was not compiled to use: AVX2
2018-09-12 19:55:49.898198: W C:\tf_jenkins\workspace\rel-win\M\windows\PY\36\tensorflow\core\util\tensor_slice_reader.cc:95] Could not open .\linear_regression.pbtxt: Data loss: not an sstable (bad magic number): perhaps your file is in a different file format and you need to use a different restore operator?
Traceback (most recent call last):
  File "C:/Users/vlad/Downloads/Linear_Regression_Model/Freeze_Graph.py", line 7, in <module>
    initializer_nodes='', variable_names_blacklist=''
  File "C:\Python36\lib\site-packages\tensorflow\python\tools\freeze_graph.py", line 244, in freeze_graph
    saved_model_tags.split(","), checkpoint_version=checkpoint_version)
  File "C:\Python36\lib\site-packages\tensorflow\python\tools\freeze_graph.py", line 119, in freeze_graph_with_def_protos
    reader = pywrap_tensorflow.NewCheckpointReader(input_checkpoint)
  File "C:\Python36\lib\site-packages\tensorflow\python\pywrap_tensorflow_internal.py", line 254, in NewCheckpointReader
    return CheckpointReader(compat.as_bytes(filepattern), status)
  File "C:\Python36\lib\site-packages\tensorflow\python\framework\errors_impl.py", line 516, in __exit__
    c_api.TF_GetCode(self.status.status))
tensorflow.python.framework.errors_impl.DataLossError: Unable to open table file .\linear_regression.pbtxt: Data loss: not an sstable (bad magic number): perhaps your file is in a different file format and you need to use a different restore operator?

Describe the problem
Describe the problem clearly here. Be sure to convey here why it's a bug in TensorFlow or a feature request.
Source code / logs
import tensorflow as tf
from tensorflow.python.tools import freeze_graph, optimize_for_inference_lib

freeze_graph.freeze_graph(input_graph='linear_regression.pbtxt', input_saver='', input_binary=True, input_checkpoint='linear_regression.pbtxt', output_node_names='y_output',
                          restore_op_name='save/restore_all',
                          filename_tensor_name='save/Const:0', output_graph='frozen_linear_regression.pb', clear_devices= True,
                          initializer_nodes='', variable_names_blacklist=''
                          )
input_graph_def = tf.GraphDef()
with tf.gfile.Open('frozen_linear_regression.pb', 'rb') as f:
    data = f.read()
    input_graph_def.ParseFromString(data)

output_graph_def = optimize_for_inference_lib.optimize_for_inference(input_graph_def=input_graph_def, input_node_names=['x'],
                                                                     output_node_names=['y_output'],
                                                                     placeholder_type_enum=tf.float32.as_datatype_enum)

f = tf.gfile.FastGFile(name='optimized_frozen_linear_regression.pb', mode='w')

f.write(file_content=output_graph_def.SerializeToString())

Can you help me guys?

Nagging Assignee @jart: It has been 15 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @jart: It has been 30 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @jart: It has been 45 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @jart: It has been 60 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @jart: It has been 75 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.


Incomplete font-lock in REPLs

Some keywords aren't being font-locked in the REPL buffers.
I believe there's a missing (font-lock-add-keywords 'geiser-repl-mode (geiser-syntax--keywords)).

it's working for me.  do you have an example of keywords that are not fontified? (fontification is handled in an auxiliary buffer in scheme mode that inherits all the font lock keywords defined for the mode, so there's no font lock keywords for geiser-repl-mode).

hmm, i take that back: i've found cases where we don't fontify correctly.  investigating...

@fice-t i've pushed a patch that should fix the issue.  please give it a try when you can, thanks!

@jaor That fixes the implementation-specific keywords, thanks.
Though I should have specified which keywords weren't being highlighted. The keywords in geiser-syntax--builtin-keywords still aren't being highlighted in the REPL.

right.  shared keywords should be highlighted now too.

Yep, thanks.


Fix contrast after mint

I've made mint within classic mint and seems like text is hardly readable

👋


GetSupplierOrderById: in ver. 3.0.0

GetSupplierOrderById:

supplierOrderStatus: Optional? Should be required
purchaseOrderStatus is required in GetPurchaseOrderById:  ver 2.0.0

 salesOrderNumber: is on purchaseOrderLineIitem in ver.2.00
  Now in the header for the supplierOrder?

  confirmedShipToLocation:
  Property partyIdentifiers: should be change to property locationIdentifiers:, i.e. the same as in toLocation: and fromLocation:

 the same issue for locations regarding uuid in locationIdentifiers: as for partyIdentifiers:, issue #104

  modeType:
    The following enumerations can be removed for Paper and Pulp businesses:
    Air, Floating, Mail, OffRoad and Other.

 unitType:
    The following enumerations can be removed for Paper and Pulp businesses:
    ForestryForwarderUnit, Wagon and Other.

Done in commit 47ffffd.
Already done in commit bcda087 according to issue #105.
Done in commit 47ffffd.
Corrected in commit 47ffffd.
Done in commit 47ffffd.
Done in commit 47ffffd.

We closed this issue with @larsolofsson, @bengtwentus and @MrNordenberg.


tests: check exception policy stats counters - v6

Edit the existing exception policy tests to check for the new exception policy stats counters.
Add one more test, to showcase behavior for exception policy stats counters when set up to log zero-valued counters and counters for each app-proto error.
Ticket #5816
Previous PR: #https://github.com/OISF/suricata-verify/pull/1674/files
Changes from previous PR:

add checks for new exception policy app-layer error counter in exception-policy-applayer-01 test
add check for no existence of such counters when value is 0, to showcase hiding zero valued stats counters
add a README for exception-policy-applayer-01 test, to explain above things
add a test for hiding eve stats counters that are 0 (ticket 5976)

Ticket
Redmine ticket:
https://redmine.openinfosecfoundation.org/issues/5816
https://redmine.openinfosecfoundation.org/issues/5976

Suricata PR: https://github.com/OISF/suricata/pull/10756

Replaced by: https://github.com/OISF/suricata-verify/pull/1746


Issue with threading

Hi,
I am trying to use this framework instead of my flask framework, as the current framework handles the connections very good , on the other hand I am facing the issue with the multi threading,
I have created two threads, consumer and producer with one shared object between them, which is of type python dictionary, the issue is rather than creating a second thread, it is creating a second process, I am posting it here, because same code is running in flask framework properly, so I don't think it is something related to the code I have written, is there a multi threading support in proper manner ?
I have chose this framework considering the better network connections handling, but on the other hand I am facing this threading related issue.
Please help.
Thanks

It's hard to speculate without an actual example but you are probably creating your threads at the import time and then trying to share something with the request handler that is run in a separate process (since japronto is a fork abusing server).
You can circumvent by creating both of your threads in the request handler lazily.


Allow user to make backups

Thank you for your submission. It will be reviewed soon and submitted for processing in CI.

Jenkins Build Summary
Built from this commit
Built at 20190731 - 18:35:26
Test Results

Build Type
Log
Result
Status

msvc.Debug
logfile
1178 cases, 0 failed, t: 576s
PASS :white_check_mark:

msvc.Debug, NINJA_BUILD=true
logfile
1178 cases, 0 failed, t: 612s
PASS :white_check_mark:

msvc.Debug -Dunity=OFF
logfile
1177 cases, 0 failed, t: 1108s
PASS :white_check_mark:

msvc.Release
logfile
1178 cases, 0 failed, t: 406s
PASS :white_check_mark:

gcc.Release -Dassert=ON, MANUAL_TESTS=true
logfile
915 cases, 0 failed, t: 5m1s
PASS :white_check_mark:

gcc.Debug -Dcoverage=ON, TARGET=coverage_report, SKIP_TESTS=true
logfile
1178 cases, 0 failed, t: 16m50s
PASS :white_check_mark:

docs, TARGET=docs
logfile
1 cases, 0 failed, t: 0m1s
PASS :white_check_mark:

clang.Debug
logfile
1178 cases, 0 failed, t: 2m57s
PASS :white_check_mark:

clang.Debug -Dunity=OFF
logfile
1177 cases, 0 failed, t: 11m14s
PASS :white_check_mark:

gcc.Debug
logfile
1178 cases, 0 failed, t: 2m56s
PASS :white_check_mark:

gcc.Debug -Dunity=OFF
logfile
1177 cases, 0 failed, t: 11m45s
PASS :white_check_mark:

clang.Release -Dassert=ON
logfile
1178 cases, 0 failed, t: 5m8s
PASS :white_check_mark:

gcc.Release -Dassert=ON
logfile
1178 cases, 0 failed, t: 4m59s
PASS :white_check_mark:

gcc.Debug -Dstatic=OFF
logfile
1178 cases, 0 failed, t: 2m55s
PASS :white_check_mark:

gcc.Debug -Dstatic=OFF -DBUILD_SHARED_LIBS=ON
logfile
1178 cases, 0 failed, t: 2m57s
PASS :white_check_mark:

gcc.Debug, NINJA_BUILD=true
logfile
1178 cases, 0 failed, t: 2m50s
PASS :white_check_mark:

clang.Debug -Dunity=OFF -Dsan=address, PARALLEL_TESTS=false, DEBUGGER=false
logfile
1177 cases, 0 failed, t: 11m42s
PASS :white_check_mark:

clang.Debug -Dunity=OFF -Dsan=undefined, PARALLEL_TESTS=false
logfile
1177 cases, 0 failed, t: 12m51s
PASS :white_check_mark:

I'm not sure I follow what exactly is happening here. Can you explain the problem this is solving, or provide a list of steps that will "replicate" it so we can understand what this is solving?

@nbougalis
I installed the rippled to my desktop completely and run it. After rippled synced, i wanted to change my rippled path so i moved rippled to another place then old path and i get that message:
$ ./rippled
Loading: "/Users/myuser/Desktop/rippled/build/rippled.cfg"
2019-Aug-01 04:39:40.033744 SHAMapStore:ERR state db error:
  writableDbExists false archiveDbExists false
  writableDb '/users/myuser/desktop/rippled/build/blockchain/testnet/db/rocksdb/rippledb.f59f' archiveDb '/users/myuser/desktop/rippled/build/blockchain/testnet/db/rocksdb/rippledb.03f1'

To resume operation, make backups of and remove the files matching /users/myuser/desktop/rippled/build/data/testnet/db/state* and contents of the directory /users/myuser/desktop/rippled/build/data/testnet/db/rocksdb

libc++abi.dylib: terminating with uncaught exception of type std::runtime_error: state db error
Abort trap: 6

rippled didn't find the database files and gave me that message. As you can see rippled said:

To resume operation, make backups of and remove the files...

But after i got that message my blockchain folders (writableDb and archiveDb) in the rocksdb (my db type) folder already was gone because of deleted codes in the commit was worked so i actually can't make backups. After this i build my rippled like that commit and tried same scenario then that problem was fixed, my folders not deleted.
Also these deleted codes are working when there is a folder that has no dbPrefix_ in the rocksdb (my db type) folder. So if i want to create a folder at rocksdb (my db type) folder that has no dbPrefix_; writableDb and archiveDb folder contents gone again. If this is for security or something that i dont know, that problem can be fixed with using multiple conditions in comparing dbPrefix_ but i think that these codes are working at that wrong time.

@yusufsahinhamza Please be careful with changes to rippled's database directories. The initial error you saw was caused because the data rippled thought it had was missing and it didn't know how to proceed. If you need to move the data from one hard drive partition to another, then stop rippled and move the contents of the entire data directory, and configure rippled so that it knows to find it's data in the new location when it starts again. Any other kind of change to the data will cause problems. If you feel the need to move the data around, it is a good idea to stop rippled and then to fully back up the data before you move it. That was if there is a problem, you can roll back to your original situation and try again. In no circumstances should you expect rippled or any other application to work well if its data is modified by some other process.

@mtrippled

If you need to move the data from one hard drive partition to another, then stop rippled and move the contents of the entire data directory, and configure rippled so that it knows to find it's data in the new location when it starts again.

That's what i am talking about, rippled deletes the database files instead of find it's data in the new location and gaving a error that says make backups when these data's already was gone.

@mtrippled

If you need to move the data from one hard drive partition to another, then stop rippled and move the contents of the entire data directory, and configure rippled so that it knows to find it's data in the new location when it starts again.

That's what i am talking about, rippled deletes the database files instead of find it's data in the new location and gaving a error that says make backups when these data are already was gone because rippled think that data are still in the old location.

I have created a pull request to clarify the error message when this happens: https://github.com/ripple/rippled/pull/3016
Also, @mDuo13, is it reasonable to add to the operations or trouble-shooting guide the specific steps to migrate data  from one filesystem location to another? (https://xrpl.org/server-wont-start.html)

Also, @yusufsahinhamza, if you wish to implement a feature for rippled to automatically know how to move data when the database path configuration changes, you can submit another pull request and it will be reviewed. I'm not sure how that would be best implemented, but if you've thought about it then maybe you have a better idea. In the meanwhile, thank you for pointing out that our error messages and troubleshooting instructions could be more clear.


[~] updated version to 1.1.11

Hi,
I have implemented all the necessary changes for version 1.21. Unfortunately, so much has changed that you have to be careful which ProtocolLib version you use.
Up to and including 1.20.4 you have to use ProtocolLib 5.2.0. From 1.20.6 you have to use the latest dev build (5.3.0)
Oh, and I failed in the commit message with the version xD
I have tested Minecraft versions 1.19.4, 1.20.1, 1.20.4, 1.20.6 and 1.21

Thanks for your contribution!
I would not be able to upload the new version to SpigotMC because they have banned my IP. I'll publish it to the Releases section.


To add a specific marker shape for still not included modifications in the AlphaMap

Feature:
If the modification is not present in the list of known modifications in AlphaMap, add an assigned form of the marker for it that is shown on the plot.

This was already implemented and should work :-)


ZEVA - Maintain Correct Name of User Who Submitted Status Update in History Component

Describe the task
Ensure the history component maintains the name of the user who submitted the status update, even when the comment or status is changed.
Purpose
To provide accurate and consistent information on the history component, making it easier to track and audit changes made by different users.
Acceptance Criteria

[ ] Investigate the current implementation of the create_user function and how records are being handled
[ ] Identify the root cause of the issue with the name being changed
[ ] Change compliance history for when a reassessment is saved for the first time to say Created instead of saved.
[ ] Implement a fix to maintain the correct name of the user who submitted the status update, regardless of comment or - status changes
[ ] Verify that the fix works and the history component displays the correct name

Additional context
Ensure that the fix does not negatively impact other parts of the application or data storage
Test the fix thoroughly to ensure it doesn't introduce new issues or negatively impact the user experience

Hey team! Please add your planning poker estimate with Zenhub @AlexZorkin @emi-hi @JulianForeman @tim738745


[bug] Spurious CPU usage with PoolExecutor

Using PoolExecutor incurs strangely high CPU usage.  The MWE below shows 40% cpu on both the process that runs it as well as the mpipool.py process spawned in the background. After the futures are ready the main process blocks a full core until the executor shuts down. It sounds as if processes are spinning on the ZMQ socket or there are extra messages sent back and forth all the time, because I can make the CPU usage go down while the futures are running by adding sleeps or prints into the main loop of mpipool.py.  CPU usage remains high until the executor shuts down though even in that case.  I haven't figured out yet how to monitor the ZMQ socket though, so I cannot confirm that hypothesis.
Using the ProcessPoolExecutor from the standard library this does not happen.
import time
from pympipool import PoolExecutor

def calc(n):
    time.sleep(30)
    return n**2

exe = PoolExecutor(max_workers=4)
f1 = exe.submit(calc, 42)
f2 = exe.submit(calc, 84)
f1.add_done_callback(print)
f2.add_done_callback(print)
time.sleep(60)  # workaround #94
exe.shutdown(wait=True)

@pmrv While I am still looking into #94 Can you check if the CPU load is decreased when applying https://github.com/pyiron/pympipool/pull/98 ?

The issue is the continuous synchronization of the futures objects between the serial python process and the MPI parallel python process. This is now moved to a single function https://github.com/pyiron/pympipool/blob/main/pympipool/share/serial.py#L140 still the issue remains, this function is called very frequently. The background is that futures objects can either be cancelled by the user in the serial process or completed by the MPI parallel process. In both cases the results have to be communicated to the corresponding other process.

@pmrv in https://github.com/pyiron/pympipool/pull/105 I added a sleep function to reduce the synchronization frequency. the default is 0.1 seconds which at least on my system does not result in a notable CPU spike. But the parameter is user adjustable to fine tune the synchronization. Can you take a look at the pull request and give me some feedback if it addresses your concerns?


add "inline" to get_array, color_bar, axvline

These 3 fucntions cause runtime errors like

multiple definition of `matplotlibcpp::detail::get_array(std::vector<std::__cxx11::basic_string<char, std::char_traits, std::allocator >, std::allocator<std::__cxx11::basic_string<char, std::char_traits, std::allocator > > > const&)'

To avoid these errors, "inline" descriptor is valid.
If these errors are specific for my environment, I'm terribly sorry for bothering you.

There's no example/test currently to detect errors when linking multiple translation units which include matplotlibcpp.h, so that's why I keep breaking it accidentally, sorry for that :D But these fixes are probably valuable for other users as well, so thanks for contributing them!


Add a description of a condition whether it has an actual active effect or not

So the following conditions, when applied will show in the chat window for easy reference for the DM -
Blinded
A blinded creature can't see and automatically fails any ability check that requires sight.
Attack rolls against the creature have advantage, and the creature's attack rolls have disadvantage.
Charmed
A charmed creature can't attack the charmer or target the charmer with harmful abilities or magical effects.
The charmer has advantage on any ability check to interact socially with the creature.
Deafened
A deafened creature can't hear and automatically fails any ability check that requires hearing.
Frightened
A frightened creature has disadvantage on ability checks and attack rolls while the source of its fear is within line of sight.
The creature can't willingly move closer to the source of its fear.
Grappled
A grappled creature's speed becomes 0, and it can't benefit from any bonus to its speed.
The condition ends if the grappler is incapacitated
The condition also ends if an effect removes the grappled creature from the reach of the grappler or grappling effect, such as when a creature is hurled away by the Thunderwave spell.
Incapacitated
An incapacitated creature can't take actions or reactions.
Invisible
An invisible creature is impossible to see without the aid of magic or a special sense. For the purpose of hiding, the creature is heavily obscured. The creature's location can be detected by any noise it makes or any tracks it leaves.
Attack rolls against the creature have disadvantage, and the creature's attack rolls have advantage.
Paralyzed
A paralyzed creature is incapacitated (see the condition) and can't move or speak.
The creature automatically fails Strength and Dexterity saving throws. Attack rolls against the creature have advantage.
Any attack that hits the creature is a critical hit if the attacker is within 5 feet of the creature.
Petrified
A petrified creature is transformed, along with any nonmagical object it is wearing or carrying, into a solid inanimate substance (usually stone). Its weight increases by a factor of ten, and it ceases aging.
The creature is incapacitated (see the condition), can't move or speak, and is unaware of its surroundings.
Attack rolls against the creature have advantage.
The creature automatically fails Strength and Dexterity saving throws.
The creature has resistance to all damage.
The creature is immune to poison and disease, although a poison or disease already in its system is suspended, not neutralized.
Poisoned
A poisoned creature has disadvantage on attack rolls and ability checks.
Prone
A prone creature's only movement option is to crawl, unless it stands up and thereby ends the condition.
The creature has disadvantage on attack rolls.
An attack roll against the creature has advantage if the attacker is within 5 feet of the creature. Otherwise, the attack roll has disadvantage.
Restrained
A restrained creature's speed becomes 0, and it can't benefit from any bonus to its speed.
Attack rolls against the creature have advantage, and the creature's attack rolls have disadvantage.
The creature has disadvantage on Dexterity saving throws.
Stunned
A stunned creature is incapacitated (see the condition), can't move, and can speak only falteringly.
The creature automatically fails Strength and Dexterity saving throws.
Attack rolls against the creature have advantage.
Unconscious
An unconscious creature is incapacitated (See the condition) can't move or speak, and is unaware of its surroundings.
The creature drops whatever its holding and falls prone (See the condition).
The creature automatically fails Strength and Dexterity saving throws.
Attack rolls against the creature have advantage.
Any attack that hits the creature is a critical hit if the attacker is within 5 feet of the creature.
All the above is from the PHB in D&D 5e.

Thanks for giving me these. I'll add them when I can... Should be by next week since I've been on vacation. Just wanted to give you the heads up!

Added in v2.7.0

This is amazing thank you.
Garry Miller (Abourious)

On 17 Jul 2022, at 20:03, DFreds @.***> wrote:

Closed #156 as completed.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.


bug:  Update spell check test

Describe the bug
Need to enable the test and update the word list
Steps To Reproduce
Look at the actions
Expected Behavior
Spell test passes
Additional Context
No response

This seems to have been done.


ember-cli 1.13.8

Update to ember-cli 1.13.8/ember 1.13.9
Upgrade other deps
Add version number to package.json
Add ember observer badge

awesome.  @Robdel12  can this get merged?

Ah yes! I forgot about this. I can merge this, but we're not interested in keeping this repo. Would anyone like to become the new champion for this?

I would be interested @Robdel12

@Dhaulagiri Take good care of it! Can you send me your username on NPM so we can transfer the package as well?

Also @Dhaulagiri, you'll have to delete your own fork before we can transfer ownership.

Done @cowboyd.  My npm username is dhaulagiri as well.

Done and done!