ENH: Add image writer

Aims to fix https://github.com/InsightSoftwareConsortium/napari-itk-io/issues/7. It will also be helpful for the elastix-napari plugin to write the result image from the registration (https://github.com/SuperElastix/elastix_napari/tree/main).
It is pretty barebones right now. @thewtex any ideas what else should be added? Should it support writing dicoms?

Codecov Report
Patch coverage: 100.00% and project coverage change: +3.01 :tada:

Comparison is base (cc08680) 88.05% compared to head (36bdf60) 91.07%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff             @@
##             main       #9      +/-   ##
==========================================
+ Coverage   88.05%   91.07%   +3.01%
==========================================
  Files           5        5
  Lines         134      168      +34
==========================================
+ Hits          118      153      +35
+ Misses         16       15       -1

Impacted Files
Coverage Δ

src/napari_itk_io/_tests/test_writer.py
100.00% <100.00%> (ø)

src/napari_itk_io/_writer.py
87.50% <100.00%> (+31.94%)
:arrow_up:

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

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

Thanks @thewtex, I rebased it. Let me know if I should anything else here!

Re-running the failed jobs for that commit did not help. The error message is:
Run GabrielBB/xvfb-action@v1
  with:
    run: python -m tox
  env:
    pythonLocation: /Users/runner/hostedtoolcache/Python/3.9.16/x64
    PLATFORM: macos-latest
/Users/runner/hostedtoolcache/Python/3.9.16/x64/bin/python -m tox
py39-macos: install_deps> python -I -m pip install itk-io itk-napari-conversion napari numpy pyqt5 pytest pytest-cov pytest-qt qtpy
ERROR: THESE PACKAGES DO NOT MATCH THE HASHES FROM THE REQUIREMENTS FILE. If you have updated the package versions, please update the hashes. Otherwise, examine the package contents carefully; someone may have tampered with them.
    itk-io from https://files.pythonhosted.org/packages/[2](https://github.com/InsightSoftwareConsortium/napari-itk-io/actions/runs/4801366500/jobs/8543472595#step:7:2)d/9a/d66ef998dada9c4797c9b8be57a171cf01[3](https://github.com/InsightSoftwareConsortium/napari-itk-io/actions/runs/4801366500/jobs/8543472595#step:7:3)61ebb1cb77699ab8306c[4](https://github.com/InsightSoftwareConsortium/napari-itk-io/actions/runs/4801366500/jobs/8543472595#step:7:4)fc84/itk_io-[5](https://github.com/InsightSoftwareConsortium/napari-itk-io/actions/runs/4801366500/jobs/8543472595#step:7:5).3.0-cp39-cp39-macosx_10_9_x8[6](https://github.com/InsightSoftwareConsortium/napari-itk-io/actions/runs/4801366500/jobs/8543472595#step:7:6)_64.whl:
        Expected sha256 888c1a58[7](https://github.com/InsightSoftwareConsortium/napari-itk-io/actions/runs/4801366500/jobs/8543472595#step:7:8)e7f11796d9a6[8](https://github.com/InsightSoftwareConsortium/napari-itk-io/actions/runs/4801366500/jobs/8543472595#step:7:9)0a23a713[9](https://github.com/InsightSoftwareConsortium/napari-itk-io/actions/runs/4801366500/jobs/8543472595#step:7:10)29928c22daf4af216199ced181f34d8e7
             Got        fc62d5b67b3064d0429599f93e36804e78a14fb8076e33f7b42e66e52e3ab94f

Collecting itk-io
  Downloading itk_io-5.3.0-cp39-cp39-macosx_[10](https://github.com/InsightSoftwareConsortium/napari-itk-io/actions/runs/4801366500/jobs/8543472595#step:7:11)_9_x86_64.whl (24.3 MB)
     ━━━━━━━━━━━━━━━━━━━━━━━━                 14.7/24.3 MB 1.9 MB/s eta 0:00:06
py39-macos: exit 1 (7.51 seconds) /Users/runner/work/napari-itk-io/napari-itk-io> python -I -m pip install itk-io itk-napari-conversion napari numpy pyqt5 pytest pytest-cov pytest-qt qtpy pid=[11](https://github.com/InsightSoftwareConsortium/napari-itk-io/actions/runs/4801366500/jobs/8543472595#step:7:12)22
  py39-macos: FAIL code 1 (8.34 seconds)
  evaluation failed :( (8.47 seconds)
::error::The process '/Users/runner/hostedtoolcache/Python/3.9.[16](https://github.com/InsightSoftwareConsortium/napari-itk-io/actions/runs/4801366500/jobs/8543472595#step:7:17)/x64/bin/python' failed with exit code 1

I guess a new update is needed. I don't know whether package releases are fully automated in this repository.


stats: use internal context to support StatsClient stats

Moving to an internal context would allow us to avoid contention and reduce memory usage whenever we record stats. One such example may be found here:
https://github.com/envoyproxy/envoy/blob/master/source/common/http/user_agent.h
Note that the context itself would need to be guarded by a mutex, but stats artifacts it produced could theoretically then be used safely from any thread, avoiding needless dispatch.
Thank you to @jmarantz for graciously sharing his thoughts and insight on this topic.

The context would only need to be guarded by a mutex if it was r/w during operation. If you set up all the known names in the context at init, no mutex-guarding is needed.
Further, if you do need r/w access, the value of having the context becomes somewhat diminished as one of the goals is to avoid contention by needing to take locks in the hot path.


Last Week in Pony - April 7, 2024

Version 0.6.1 of ponylang/http_server has been released.
See the release notes for more details.

recording of sync: https://vimeo.com/930073049


Enable chef setting for tcp_listen linger option

@jjasghar could you please review this ?
Reference - https://www.rabbitmq.com/networking.html
grep for "linger".

I'll take a look at this, and do some research on this.
@michaelklishin any thoughts on this option? This is the first i've heard of it.

@michaelklishin fyi...I had sent out an email to openstack-operators mailing list as well.
Here is the email - http://lists.openstack.org/pipermail/openstack-operators/2015-November/008878.html

Thanks @jjasghar

Socket lingering is primarily useful to clients but I have no objections to this. Keep in mind that as of 3.6.0 we will be using a TCP acceptor library called Ranch, which has sensible defaults for most, and is fairly strict about rejecting options it doesn't support (in general, the options are nearly identical to gen_tcp, though).

@michaelklishin  do we know for sure that linger {true, 0} is always the default setting in rabbitmq config ?
This documentation [1] does say so.
[1] - https://www.rabbitmq.com/networking.html

@mgosalia see for yourself:

in master
in stable

Thanks @michaelklishin.
@jjasghar  is it good to go ? This change will help us at Yahoo to configure the value.

I'm going to run this through our testing today. Any chance you can create an integration/unit test for this? I really don't like adding things to this cookbook without test coverage.

@jjasghar sure...will add unit tests. I tried to look for existing tests related to rabbitmq config and did not find any. So, had skipped it. Let me dig more.

Sounds good, just Unit tests are probably fine. When you get them added I'll go through my release process and get this pushed out.

@jjasghar have updated the change with unit tests. Could you please review it again ? Thanks.

Awesome, thanks. I'll run some final tests and push out a new version ASAP.


LandmarkBasedTransformInitializerFilter does not accept BSplineTransform

error.zip
RuntimeError: Exception thrown in SimpleITK LandmarkBasedTransformInitializerFilter_Execute: /opt/miniconda2/conda-bld/simpleitk_1491578024069/work/build/ITK-prefix/include/ITK-4.11/itkLandmarkBasedTransformInitializer.hxx:75:
itk::ERROR: LandmarkBasedTransformInitializer(0x31204f0): Unsupported Transform Type BSplineTransform

It's better to provide the sample code inline like this:
import SimpleITK as sitk
import numpy as np

img = sitk.GetImageFromArray(np.random.rand(10,10))
fixed_pts = np.array([0, 0, 3, 2, 2, 1, 6, 7])
moving_pts = np.array([1, 1, 4, 1, 1, 3, 5, 8])

ix = sitk.BSplineTransformInitializer(img, (2, 2), 1)
landmarkTx = sitk.LandmarkBasedTransformInitializerFilter()
landmarkTx.SetFixedLandmarks(fixed_pts)
landmarkTx.SetMovingLandmarks(moving_pts)
landmarkTx.SetBSplineNumberOfControlPoints(8)
landmarkTx.SetReferenceImage(img)
initialTx = landmarkTx.Execute(ix)

The third parameter for the BSplineTransformInitializer is the spline order. It defaults to 3. The ITK LandmarkBasedTransformInitializer only works with spline orders of 3. Please try changing to the following:
ix = sitk.BSplineTransformInitializer(img, (2, 2), order=3)

We'll add a special check for the spline order to produce a better error message.


chore: Dockerfile restructure

Description
Clean up existing docker container utiltiies and provide a docker file which replicates our master branch development environment.
Type of change
Please delete options that are not relevant and/or add your own.

Bug fix (non-breaking change which fixes an issue)
New feature (non-breaking change which adds functionality)
Breaking change (fix or feature that would cause existing functionality to not work as expected)
This change requires a documentation update

Checklist:

[ ] My code follows the style guidelines of this project (You can use the linters)
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas and hacks
[ ] I have made corresponding changes to the documentation
[ ] I have added tests to verify my fix or my feature
[ ] New and existing unit tests pass locally with my changes
[ ] I have added the relevant labels to my PR in so that relevant reviewers are notified

@peri044 is there some way to build these in CI for people to just download?


Doc - Arangorestore - Number-of-shards and replication-factor…

… for system collections are server-controlled, as per @KVS85
Also fix some formatting issues.
To be backported to 3.4 and 3.3.

What is this actually supposed to mean?

arangorestore --input-directory "dump"
This will connect to an ArangoDB server and reload structural information and
documents found in the input directory dump.

Shouldn't it be **restore structure**? It could also mention that --create-collection and --import-data are true by default and thus the structure is created and data imported.


PowerBI GetMemberProperties without ElementAttributesCube

Describe the bug
It is not possible to retrieve only the consolidations for a hierarchy/dimension if there exists no attribute cube.
To Reproduce
    tm1_dim_chartofaccounts = tm1.power_bi.get_member_properties(
            dimension_name="d1",
            hierarchy_name="d1",
            skip_consolidations=True,
            attributes="")

Expected behavior
Retrieval of hierarchy should always be possible. even if no attributes are defined.

The }ElementAttributes_ cubes must exist because we query the parent information from each element through calculated members.
In order to execute this query, a cube must exist.
The MDX query looks kinda like this:

        WITH
                    MEMBER [}ElementAttributes_plan_department].[level001]
                    AS [plan_department].CurrentMember.Parent.Name

                    MEMBER [}ElementAttributes_plan_department].[level000]
                    AS [plan_department].CurrentMember.Parent.Parent.Name

        SELECT
        { [plan_department].[plan_department].[105],[plan_department].[plan_department].[110],[plan_department].[plan_department].[115],[plan_department].[plan_department].[200],[plan_department].[plan_department].[300],[plan_department].[plan_department].[405],[plan_department].[plan_department].[410],[plan_department].[plan_department].[415] } ON ROWS,
        { {Tm1SubsetAll([}ElementAttributes_plan_department])} + {[}ElementAttributes_plan_department].[level001],[}ElementAttributes_plan_department].[level000]} } ON COLUMNS
        FROM [}ElementAttributes_plan_department]

Just a create the cube :)

Unfortunately the customer has only read access to the system and certain cubes. For some dimension there are no attributes defined. Couldn't we find another workaround here?

You do not know the kind of tm1 instances we have here. ;-) We have some large dimensions without any attributes but very complex custom rollups.
For now I convinced them to create an empty attributes cube. But maybe for the future there is a better way.

We will look into this but not short term. If you need this short term, I'm happy to accept a PR :)


Onboarding pull request

Onboarding pull request

Coverage remained the same at 35.984% when pulling e73da6987011b4a84c3d705ede11d28419b2dfa2 on dev/t-karora/onboarding-check-in into a4539daa622ed4f1f3fa91632fa3f49f889d002d on main.

Nice to see this! :)


Cannot unset Icon.ToolbarAndroid::navIconName

In a Redux-connected environment, I could not define my navbar in this – declaratively correct – fashion:
export const Navbar = (props) => {
  const sharedProps = {... // irrelevant here}
  if (props.canGoBack) {
    return <MaterialIcons.ToolbarAndroid navIconName='keyboard-backspace' onIconClicked={props.goBack}{...sharedProps} />
  } else {
    return <MaterialIcons.ToolbarAndroid {...sharedProps} />
  }
}

The "back button" would not go away, once visible. I believe I can trace this to the line https://github.com/oblador/react-native-vector-icons/blob/master/lib/create-icon-set.js#L254 – the navIcon is only set when navIconName is set.
Iirc, with React.ToolbarAndroid there is the opposite problem: once navIcon has been set and then unset, it cannot be set again. So maybe, this is not easily fixable.
I'm on RN 21 and react-native-vector-icons 1.3.2.

I can work around this issue by wrapping one of the toolbars in a View:
<View>
  <MaterialIcons.ToolbarAndroid {...navbarProps} />
</View>

I believe this works because this forces a different instance of MaterialIcons.ToolbarAndroid out of RN.

Didn't test the code, but try out this branch and see if it solves your problem: https://github.com/oblador/react-native-vector-icons/compare/toolbarandroid-props-change-fix

@alexbepple: Did the branch solve your problem?

@alexbepple: Bro?

I ran into the same problem. It's fixing this problem, but other is created - when it's hidden, it can't be shown again.

@NoWay1201: That seems to be a bug in RN core, that I believe is fixed by this commit: https://github.com/facebook/react-native/commit/8aa83a2d93fe4dba746cb03bb24604dc1ab859b6. I'll merge this branch.

Released in [1.3.3](https://github.com/oblador/react-native-vector-icons/releases/tag/v1.3.3]


backport: Fix negative xsd range edge cases (#178)

This backports 7369d2ec7bec0bb0c873b367ffd1a833d01b6bdc to v2.0.1:

The current implementation uses the abs() function to check that the value is inside the range.
However, the range is not symmetric.
For example, for a byte, which is between [-128, 127],
the value of
maxInclusive should be 127,
and minInclusive
should be -128.

LGTM


Rearchitecting skpro on skbase - part 2: metrics and examples

This PR is a major rearchitecting of skpro based on skbase and the sktime probabilistic prediction framework.
Part 2 of #10.
Contents:

probabilistic performance metrics and tests, adapted from sktime
simple notebook examples with the base vignette

@frthjf, any idea why the missing init file check is failing?

(@yarnabrina fixed it!)


Create shortcut, binary, or install

how to create a shortcut that other people can use, possibly create a new binary, or a system install
I followed your instructions to download your git repository and use npm to install and a run the application. This all works perfectly and i love it. I currently am running on fedora/korora 25 and now that nodejs 6 is in the repos by default it is easy to do this. But, this is not easy for say my wife to do. So how can i install this, create a new binary to install, create a universal shortcut, or any other alternatives and ideas? Or can you update the binary downloads you currently make available?
Thanks again for your work on this, and sorry if posted this in the wrong spot.
System versions:
nodejs: v6.9.2
npm: 3.10.9
libusb: 0.1.12

Let me update the binary with the most recent updates, currently having issues with repackaging the electron app

Could you do this:
git pull
rm -rf node_modules
npm install
sudo npm start

Just published a release: https://github.com/stevelacy/msi-keyboard-gui/releases/tag/0.1.3
Can you confirm that the binary does run correctly, and if not the errors it produces?
Thanks

Binary runs correctly using sudo.  When exiting the app, i'm not sure if if fully terminates the process though because i then have to ctrl+c on my terminal to get back to a working command prompt.  No big deal. I might try and make a policy and later try with pkexec. Do you think that is normal? I tried nohup and disown, but i'm not sure if i had the correct usage with sudo and those commands.
Thanks again for working on this.
I assume your previous comment was for the other issue?

When closing the app down, should it end all processes and return to normal bash prompt? I'm currently using sudo -b nohup to get around this issue.

It should end the process when it closes, might be an electron thing.


Code actions for migration from Xtext

We should implement code actions that ease the migration from Xtext:

Add returns string to datatype rules.
Support metamodel::EClass type reference syntax (mark with an error when used) and offer to replace ecore::EString with string (same for other primitives).
Ensure we have validations forbidding unsupported features such as with grammar references.

@spoenemann Since we have had this thing for quite a while now, I'm not sure we actually need much more on this front. I'd be in favor of closing this issue.

Yes but we should still do

Ensure we have validations forbidding unsupported features such as with grammar references.
or at least remove those parts from the Langium grammar.

Another irritating case is the ability to re-define the hidden tokens for a parser rule. We should add a warning/error for that.
MyRule hidden(WS):
    // some calls
;


Fix some (trivial) tests, remove copy & paste mistakes

One might also argue to remove these existance tests, as they aren't super useful.
Please review.

Thanks!


Add tests for node/http.go

The functionality in node/http.go is very user-facing, and it should work flawlessly. To avoid errors like the one fixed in this PR.

Can I attempt this issue?


DBZ-7570/#133: started to add workaround using SO_LINGER with 0 timeout

…ut if use.nongraceful.disconnect=true

@jpechane rebase done ...
Just to mention it here too, workaround from this PR inspired by this https://bugs.openjdk.org/browse/JDK-8241239?focusedId=14646711&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-14646711
Related PR in binlog client https://github.com/osheroff/mysql-binlog-connector-java/pull/142, the "Update Dependencies" job is failing since com.zendesk:mysql-binlog-connector-java:jar:0.29.2 has not been released yet

@Naros updated binlog client PR

Superseded by #5517 as this needed a rebase.  Lets continue there.


Should remove vercel integration since deploy workflow do the same thing.

Should remove the vercel and related things, as now we are using the GitHub Actions to do the such thing.

https://github.com/koishijs/koishi-plugin-booru/commit/7a682596d944ad84d014fc8f5a11f4d1f9f7c364


[WIP] Solve memory leak in Promise::fromObservable

Work in progress, don't merge yet. Going to commit in stages

Seems like I'm running into the same issue. @WyriHaximus Is this a problem that has to get fixed or is this eventually caught by GC?

@bartvanhoutte I utterly forgot about this, well you have two kinds of memory leaks in PHP, the ones that the GC will clean up and the ones that the GC doesn't clean up. The ones the GC will clean up are ignorable until a certain point. The otherones aren't. So the question is, is the GC cleaning up what you are seeing? I'll get on this PR again soon and get it ready for review and merging :+1:


Write out dependence of active_support in all_names_with_codes

Currently you are left with the following if you
$ gem install countries
$ irb
irb(main):001:0> require 'countries/global'
=> true
irb(main):003:0> ISO3166::Country.all_names_with_codes
NoMethodError: undefined method 'html_safe' for "Andorra":String

The proposed patch writes out the dependency for active_support by removing the use of html_safe with backwards compatibility, although I am unsure it was needed in the first place.
Hope it can be considered as not everyone use active_support all the time.
Regards
Subfusc

Looks good.


Update dependencies to latest versions

sinon is not updated to 2.0.0 yet, because of migration problems with unit tests

Codecov Report

Merging #611 into master will increase coverage by 0.14%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #611      +/-   ##
==========================================
+ Coverage   86.36%   86.51%   +0.14%
==========================================
  Files          27       27
  Lines        2457     2588     +131
  Branches      218      218
==========================================
+ Hits         2122     2239     +117
- Misses        335      349      +14

Impacted Files
Coverage Δ

browser/model/hyperv.js
92.68% <0%> (-2.19%)
:x:

browser/directives/breadcrumb.js
10% <0%> (-1.12%)
:x:

browser/services/request.js
20% <0%> (-0.84%)
:x:

browser/services/platform.js
86.39% <0%> (-0.38%)
:x:

browser/pages/start/controller.js
44.79% <0%> (-0.04%)
:x:

browser/model/virtualbox.js
71.75% <0%> (-0.03%)
:x:

browser/model/helpers/version.js
100% <0%> (ø)
:white_check_mark:

browser/model/cygwin.js
100% <0%> (ø)
:white_check_mark:

browser/services/data.js
100% <0%> (ø)
:white_check_mark:

browser/pages/location/controller.js
100% <0%> (ø)
:white_check_mark:

... and 15 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update b1fb62a...7238b2b. Read the comment docs.


Refactor and improve Avian Flight Plans (AFP)

This PR refactors and adds new feature to AFP. This is a draft PR since new changes and ideas can be added in future.
Current changes:

afp: Add help message for "flightplans" option
afp: Remove use of marco to get path
afp: Add list_flightplans RPC method
afp: Remove weblib (web3 lib from AFP is being removed because it is insecure and not done.)

If you have any idea that can added to AFP, feel free to comment them or raise a PR!

This PR is being blocked by #71 and #72 and needs to rebased against 4.1 once said PRs get merged.

PR #71 has been merged, rebasing this PR against 4.1 branch to run CodeQL analysis on AFP code for security check.


Added Nullcheck on maintenanceIcon to prevent Exceptions

Prevent exceptions coming up, when no maintenanceIcon is present.

For what case-scenario is this useful? This variable is never supposed to be null as the maintenance_icon.png file is created if not found.

havent really watched it out, but saw a NullPointerException in this line on a friends server. Dont know why the icon was not created. Maybe the user has no write permission or there was another error before. Just wanted to remove the exceptions, because it somehow spams the console.

I am not maintaining this project anymore, please fork if you want to apply some changes.


docs: update GEDI L4B V2.1 Summary

@lauraduncanson, I think everything on the dashboard regarding GEDI v2 has to be updated to v2.1...this includes the description on the CEOS web page (https://ceos.org/gst/GEDI-biomass.html). Who prepared this text, who can we ask to update it?

Stephen Ward ! And yes, agreedSent from my iPhoneOn Nov 12, 2023, at 1:58 PM, nehahunka @.***> wrote:
@lauraduncanson, I think everything on the dashboard regarding GEDI v2 has to be updated to v2.1...this includes the description on the CEOS web page (https://ceos.org/gst/GEDI-biomass.html). Who prepared this text, who can we ask to update it?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

@nehahunka @lauraduncanson, if the summary looks okay then we can merge - or if you have comments/suggestions then feel free to add them here, thanks!


Can we use compatible release spec in environment.yml?

Hello all,
My usual practice with environment.yml is to use compatible release spec to make upgrades easier, and a lockfile for reproducibility. Since this repository has a lockfile, what do you think about modifying the environment.yml to not pin dependencies as strictly? This article speaks to the different use cases of these two types of spec files: One focuses on specifying a human-curated environment optimized for upgradeability, while the other optimizes for reproducibility and is generated by machine from a real environment.
Compatible release spec allows specifying an arbitrary number of version digits, e.g. ~=1, ~=1.2, or ~=1.2.3. The last digit specified is allowed to "move", and others are not. If you specify ~=1.2.3, version 1.2.4 would be allowed, but 1.3 would not. This provides some advantage over greater/less-than spec because in my experience a spec like >=3.0,<4.0 can allow a 4.0.0alpha1 package to be installed. Perhaps this issue has been long-since resolved, but it's the reason I stopped using that style.
In PR #45 I used compatibility spec out of habit and then realized the inconsistency. Happy to change it or not (or, if desired, overhaul the entire environment.yml file to use compat spec) depending on discussion outcome :)
Thanks all!

Thanks Matt for raising this issue! In general, I'm in agreement with you on having a loosely pinned conda environment.yml file and a specifically pinned conda-lock-64.lock file (which needs to be improved in #14). That is generally what conda-lock is working towards in the conda ecoystem, much less so in the PyPI ecosystem.
On whether using ~= compatible release spec or >= minimum pinning is preferred, that depends on the situation. The general disagreement is that we can't predict what happens to a package in the future, see e.g. https://prefix.dev/blog/the_python_packaging_debate. If people followed semantic versioning perfectly, then ~= would be a good idea, but in practice, it can be a source of pain when people want the latest version 4.0 of some library and they know it works, but some maintainer in the past decided to pin to >=3.0, <4.0. Another example is when packages like xarray switched from semver to calver (e.g. 0.19.0 to 2023.0.1) and all those libraries that set an upper bound or compatible release spec to >=0.16.0, <1.0.0 couldn't handle it. And yes, ~= doesn't really work so well with CalVer for that matter since you'd be stuck with yearly versions.
To be fair, I'm not against using ~=, I've actually used https://python-poetry.org/docs/dependency-specification/#tilde-requirements quite a bit with past projects. The key factor is that someone needs to actively maintain these pinnings, and with a long-term project like CryoCloud, it depends on whether someone can do that in 2 or 3 years time. This is perhaps just a long winded way of me saying, do you want to become a maintainer for this repo? :wink:

https://prefix.dev/blog/the_python_packaging_debate
:point_up: Excellent article! @betolink shared this with me earlier this week.
I don't like calver, personally; there's no specification method (aside from e.g. ~= 2023.01.01 would allow patch updates only) that protects you from breaking changes :(

The key factor is that someone needs to actively maintain these pinnings, and with a long-term project like CryoCloud, it depends on whether someone can do that in 2 or 3 years time.

This is always the challenge with complex environments. Sometimes I'm away from a project from 3 years and cleaning up the mess at that point is always a nightmare.

This is perhaps just a long winded way of me saying, do you want to be added to this repo to implement and maintain this? wink

Edit: Sorry, I just realized you're part of the cryoclouduser team already! In that case, I should ask if you're keen to help review future issues/PRs related to dependency upgrades.

I'm absolutely willing to help out with environment-related changes. I'm feeling fairly comfortable with the tools you're using for this repo after doing these two PRs today!

Cool, we've decided to go ahead to relax the dependency pinnings, beginning with a few packages in #56. Currently the ~= compatible release spec is used, but we could also use >= for packages using CalVer if needed. Thanks again @MattF-NSIDC for the useful discussion, closing this issue now :D


Empty QuerySet Fix

Codecov Report

Merging #73 (b0613b1) into master (7f0015e) will not change coverage.
The diff coverage is n/a.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@            Coverage Diff            @@
##            master       #73   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           46        46
  Lines         1988      1988
=========================================
  Hits          1988      1988

Files Changed
Coverage Δ

ninja_extra/schemas/response.py
100.00% <ø> (ø)


Upgrade Datastore to use v1beta3

Hey @JustinBeckwith, thanks for the issue! The Google Cloud Datastore docs are still showing v1beta2. Is v1beta3 available? If not, do you know when it will be generally available?

@pcostell, can you link us to the v1beta3 docs?

v1beta3 is in alpha/pre-alpha(?). The protos live here: https://github.com/google/googleapis/tree/master/google/datastore/v1beta3. I can email anyone the release docs (we are waiting until v1beta3 is available for everyone to actually stage them). Also, let me know if you need an app whitelisted for testing.

How long will v1beta2 be supported during the transition to v1beta3?

Here are the release notes: https://cloud.google.com/datastore/docs/release-notes.
We don't have any plans for the timeline for deprecating v1beta2. v1beta3 should be significantly more performant so it is probably good for users to transition as quickly as possible. Once the gcloud-* libraries move over we'll have a better sense of how long we should give people to transition.

Great! So if we switch now will all users be able to use v1beta3? Is it generally available? Or will they need to request access?

No it is not yet available. We'll update everyone as soon as it is. I can get Google developers early access, but we don't have a public early access program.

@pcostell Can you allow access to v1beta3 to helical-zone-771 and nodal-almanac-725?

You're all set.

@blowmage any progress here?

In discussions with @jgeewax we decided to hold off on upgrading to v1beta3 until it was publicly available. I hope this will be soon because I'd love to get this change made. :)

The protobuf files for v1beta3 are available here.

What is left for this? The code is in a separate branch right now, what needs to happen to get it merged into master and deployed?

@pcostell Thanks for asking! We are blocked by google/protobuf#1204, a known issue in Google's Protobuf library's support of oneof used in the datastore proto3 definitions. The issue is supposed to be fixed in PR google/protobuf#1139, which has been merged into master, but has not yet been released. As you can see if you scroll down the comments in google/protobuf#1204, @blowmage has asked a couple of times about the release. We have also asked @jgeewax to look into it.


 AND language=? ORDER BY RANDOM()", [category, language])
it‘s OK

@MingleChang Try to use $category instead of :category and tell me if it works.


Cant seem to connect to Smart tinQ server

Describe the bug
When i try to log into the integration service i get connection errors.
I think the log file says enough to the experts?
Please help me resolve this issue
Error retrieving login URL from ThinQ
Traceback (most recent call last):
File "/usr/local/lib/python3.10/site-packages/aiohttp/connector.py", line 986, in _wrap_create_connection
return await self._loop.create_connection(*args, **kwargs)  # type: ignore[return-value]  # noqa
File "/usr/local/lib/python3.10/asyncio/base_events.py", line 1089, in create_connection
transport, protocol = await self._create_connection_transport(
File "/usr/local/lib/python3.10/asyncio/base_events.py", line 1119, in _create_connection_transport
await waiter
File "/usr/local/lib/python3.10/asyncio/sslproto.py", line 534, in data_received
ssldata, appdata = self._sslpipe.feed_ssldata(data)
File "/usr/local/lib/python3.10/asyncio/sslproto.py", line 188, in feed_ssldata
self._sslobj.do_handshake()
File "/usr/local/lib/python3.10/ssl.py", line 975, in do_handshake
self._sslobj.do_handshake()
ssl.SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: certificate is not yet valid (_ssl.c:997)
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/config/custom_components/smartthinq_sensors/init.py", line 102, in get_login_url
return await ClientAsync.get_oauth_url(
File "/config/custom_components/smartthinq_sensors/wideq/core_async.py", line 1330, in get_oauth_url
gateway = await Gateway.discover(
File "/config/custom_components/smartthinq_sensors/wideq/core_async.py", line 661, in discover
gw_info = await core.gateway_info()
File "/config/custom_components/smartthinq_sensors/wideq/core_async.py", line 354, in gateway_info
return await self.thinq2_get(V2_GATEWAY_URL)
File "/config/custom_components/smartthinq_sensors/wideq/core_async.py", line 269, in thinq2_get
async with self._get_session().get(
File "/usr/local/lib/python3.10/site-packages/aiohttp/client.py", line 1138, in aenter
self._resp = await self._coro
File "/usr/local/lib/python3.10/site-packages/aiohttp/client.py", line 535, in _request
conn = await self._connector.connect(
File "/usr/local/lib/python3.10/site-packages/aiohttp/connector.py", line 542, in connect
proto = await self._create_connection(req, traces, timeout)
File "/usr/local/lib/python3.10/site-packages/aiohttp/connector.py", line 907, in _create_connection
_, proto = await self._create_direct_connection(req, traces, timeout)
File "/usr/local/lib/python3.10/site-packages/aiohttp/connector.py", line 1206, in _create_direct_connection
raise last_exc
File "/usr/local/lib/python3.10/site-packages/aiohttp/connector.py", line 1175, in _create_direct_connection
transp, proto = await self._wrap_create_connection(
File "/usr/local/lib/python3.10/site-packages/aiohttp/connector.py", line 988, in _wrap_create_connection
raise ClientConnectorCertificateError(req.connection_key, exc) from exc
aiohttp.client_exceptions.ClientConnectorCertificateError: Cannot connect to host route.lgthinq.com:46030 ssl:True [SSLCertVerificationError: (1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: certificate is not yet valid (_ssl.c:997)')

I think the log file says enough to the experts?

No, it's not. May be exists an issue template for some reason? And, by the way, I assumed that you read readme with attention before posting this issue.

Hi Ollo,
First thanks for you quick reply and sorry for the bad problem description. Yes i read the readme and this forum to try to find a fix for this problem.
I downloaded the app from HACS, restarted HA and made a new account to wich i connected the device.
I just somehow cant find away to log in via the "devices and services"  (if it is called this way) tab in HA.
tried rebooting couple of times more.

Looks like a certificate problem, but because I don't have detail of your environment I cannot provide more info.  Check that date time and time zone are correct, if not solve start providing details requested by issue template.

Hi Ollo,
I think you can close this thread, after a full power cycle of the HA host and running the software update for HA i can now log into SmartTinQ. Thanks for the quick reply


[Proposal] Add a new command "tag" for embedding arbitrary data

Something I often do with SVGs is to have a "master SVG" that has named objects and groups, then selectively change the style of some of these groups during rendering. Thinking about TinyVG use cases, imagine a "Checkbox" SVG. It might look something like this:
<svg>
<rect ...>
<path id="checkmark" d="..." fill="green">
<path id="cross" d="..." fill="red">
</svg>

The renderer can then select any of the styles by rendering with an override of `fill="none" for one of the IDs.
I don't think that explicitly specifying this type of CSS-like behavior makes sense as part of a format like TinyVG. However, it would be nice if it would be possible to uniquely identify individual elements or groups of elements in a TinyVG file from the outside.
One way of doing this could be to have "id start" and "id end" commands in between graphical commands. These would have no effect on the actual graphical rendering and can be ignored during rendering since in contrast to SVG groups they do not change graphical state such as style or transform. IDs could be variable-length strings, which would not make implementing a parser worse since there are already variable-length integers and lists anyway. Example TinyVG file structure for the checkmark example above:
[header]
[color table]
<outline rect ...>
<start id "checkmark>
<fill path ... color=green>
<end id "checkmark>
<start id "cross">
<fill path ... color=red>
<fill path ... color=red>
<end id cross>
[EOF]

I accept a slightly modified variant of this:
A new command tag(string) will be added. There will be no specification about how the tag content is formed, it is just an arbitrarily sized byte stream that can be used to identify or control custom renderers. Tags can be ignored by conforming renderers.

I think that's a really neat solution.

Something like this would also be useful to e.g. have an entire icon theme in just one image file. Then you pick the group of the icon you need, which could itself build on top of some base icon. I can imagine this being useful for especially websites, giving you all your icons in just one request.

As it's requested right now:
The new command will be called tag and has command index 11. The layout will be like this:
command-name:  "tag"
command-index: 11
layout:
  length: varuint
  data:   [length]u8

Nice!
What’s the spec on the u8 payload? UTF-8? /[a-zA-Z0-9]+/? UUID? Any random blob of no assumptions?

The last thing:
data is an arbitrary blob without assumptions for now. As it's an application specific command so all implementations are free to ignore the blob.


Add transparency information to social preview documentation

Code of Conduct

[X] I have read and agree to the GitHub Docs project's Code of Conduct

What article on docs.github.com is affected?
Customizing your repository's social media preview
What part(s) of the article would you like to see updated?
Github social preview supports using transparent PNGs, but this does not seem to be documented. Adding a small subsection about transparency would be welcome. Usage of transparent PNGs can be helpful for branding as many platforms support dark/light themes and transparent PNGs can work well with multiple themes.
Additional information
You can read my general GitHub feedback here https://github.com/github/feedback/discussions/13109#discussion-3951682, for more information.


README priority test

Test that this is closed automatically.

README.md has priority over README and README.txt, however .github/README.md has priority over README.md.


PR under Issue #97 - Change the mission, vision and plan data upon clicking

I have added functionality to change text dynamically to the relevant heading of VISION/MISSION/PLAN, even added relevant text to the headings instead of filler text.
Please do also add a hacktoberfest tag. Thanks.
https://github.com/user-attachments/assets/8062be7c-7cdc-4293-8974-0c457df7489f

Ensure you pull all the latest changes before pushing your feature/bug fixes to the main branch. After resolving the conflicts, please open a new PR for review.
Thank you!


BIC-188 # refactor Pending queue

model-application: Extendable pending-queue view placeholder
moved pending queue related moustache templates in template folder
view/form/pending: split pending queue view specific functions from view-interaction to separate view class
added tests in view-interaction that confirms preparePendingQueueSubView() functions correctly
-- and picks correct view
md file that shows what variables are available for pending queue default view

LGTM :+1:


artik5 bootloader does not get written to emmc

After booting the resin flasher image, after the board shutsdown, when powering on again the uboot output on the serial console shows that the old uboot is running, and not the one that should have been written by the flashing procedure.

Fixed by https://github.com/resin-os/resin-artik/pull/87

Fix merged in master. Will be available in the next release (most likely v2.0.7)


[StaticDateRangePicker] not reFocusing  on set date if changed programmatically

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Current behavior 😯
Hey Guys.
It seems that setting up a new Date value to the StaticDateRangePicker programmatically (as with changing the value prop dynamically  without touching the picker ui by hands)
not refocusing the picker to the new value.
The actual date does being selected, but you have to go to the targeted month by hand.
My Case Scenario :

I would like to render a "Popular Occasions" by the calendar , so  a user wouldn't have to travel  a lot by ui gestures related to changing the pickers month.
Expected behavior 🤔
The StaticDateRangePicker should switch rendered month to the targeted dynamically changed Date, even if not changed by the input textbox / ui Gesture (left/right month arrows)
Steps to reproduce 🕹
Steps:
1.Add a new StaticDateRangePicker
2. Change the value prop dynamically by any method you like (button, function etc), to a date which happens in a month other than the current rendered month
3. See that the other month you set not being rendered as should
4.
Context 🔦
No response
Your environment 🌎

`npx @mui/envinfo`
  Don't forget to mention which browser you used.
  Output from `npx @mui/envinfo` goes here.

System:
OS: macOS 11.6
Binaries:
Node: 15.14.0 - ~/.nvm/versions/node/v15.14.0/bin/node
Yarn: 1.22.10 - /opt/homebrew/bin/yarn
npm: 8.1.3 - ~/.nvm/versions/node/v15.14.0/bin/npm
Browsers:
Chrome: 97.0.4692.71
Edge: Not Found
Firefox: Not Found
Safari: 15.0
npmPackages:
@emotion/react: ^11.6.0 => 11.7.1
@emotion/styled: ^11.6.0 => 11.6.0
@mui/base:  5.0.0-alpha.63
@mui/icons-material: ^5.1.1 => 5.2.5
@mui/lab: ^5.0.0-alpha.55 => 5.0.0-alpha.63
@mui/material: ^5.1.0 => 5.2.7
@mui/private-theming:  5.2.3
@mui/styled-engine:  5.2.6
@mui/system:  5.2.6
@mui/types:  7.1.0
@mui/utils:  5.2.3
@types/react: ^16.9.0 => 16.14.21
react: ^17.0.2 => 17.0.2
react-dom: ^17.0.2 => 17.0.2
typescript: ~4.1.5 => 4.1.6

Hi.
Please provide a CodeSandbox (https://material-ui.com/r/issue-template-latest), a link to a repository on GitHub, or provide a minimal code example that reproduces the problem.
Here are some tips for providing a minimal example: https://stackoverflow.com/help/mcve

I  just had a look over this and somehow if i comment this
if (disableAutoMonthSwitching || !open) {
      return;
    }

The whole thing works out, Not sure if this would be right way

@BuntyBru  Looks interesting to me. good catch
I don't know why from first place ones would like to disable autoMonthSwitching . it's a bad UX decision if you think about it. looks like this if clause needs to be removed (or the whole disbaleAutoMonthSwitching prop)

I think it is being used for something , But i am not sure what open is being taken out from a hook.
I guess contributors can throw some light on it


npm WARN deprecated<EMAIL_ADDRESS>

The following warning appears while installing current find-my-iphone:
npm WARN deprecated<EMAIL_ADDRESS>ReDoS vulnerability parsing Set-Cookie https://nodesecurity.io/advisories/130

This issue was moved to iobroker-community-adapters/ioBroker.find-my-iphone-community#6


Initial suggested itinerary

Feedback welcome 😊

Shouldn't the content be in a markdown file?

Great job @BasThomas! You almost sound like a portuguese and if you ever need a place to cook, please let me know! 🙇

Shouldn't the content be in a markdown file?

I (for now) copied the style I saw in other files. @pcardoso?

Thanks for merging!


refactor: adapt chromatic check imports

With the new patch release of the chromatic package, the imports from chromatic/isChromatic no longer work and need to be changed to chromatic, due to the exports configuration in the chromatic package.

Codecov Report

Merging #1811 (e5c72aa) into master (ab917b0) will decrease coverage by 15.94%.
The diff coverage is 34.52%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@             Coverage Diff             @@
##           master    #1811       +/-   ##
===========================================
- Coverage   54.85%   38.91%   -15.94%
===========================================
  Files          49      251      +202
  Lines        1659     9191     +7532
  Branches      406     1927     +1521
===========================================
+ Hits          910     3577     +2667
- Misses        671     5369     +4698
- Partials       78      245      +167

Impacted Files
Coverage Δ

...ts/sbb-accordion-item/sbb-accordion-item.events.ts
100.00% <ø> (ø)

.../sbb-accordion-item/sbb-accordion-item.stories.tsx
0.00% <0.00%> (ø)

...mponents/sbb-accordion-item/sbb-accordion-item.tsx
0.00% <0.00%> (-37.21%)
:arrow_down:

...components/sbb-accordion/sbb-accordion.stories.tsx
0.00% <0.00%> (ø)

...ents/sbb-action-group/sbb-action-group.stories.tsx
0.00% <0.00%> (ø)

...onents/sbb-alert-group/sbb-alert-group.stories.tsx
0.00% <0.00%> (ø)

src/components/sbb-alert/sbb-alert.stories.tsx
0.00% <0.00%> (ø)

...onents/sbb-autocomplete/sbb-autocomplete.events.ts
100.00% <ø> (ø)

...ents/sbb-autocomplete/sbb-autocomplete.stories.tsx
0.00% <0.00%> (ø)

src/components/sbb-button/sbb-button.stories.tsx
0.00% <0.00%> (ø)

... and 58 more

... and 195 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


datetime is parsed irrespective of the given format

Description of the Issue and Steps to Reproduce:
this gives a weird result 0004-08-30T15:00:00+08:00
moment.locale('zh-cn');
moment.tz.setDefault('Asia/Shanghai');
moment(`4、公告时间：2018/8/30 15:00:00`, 'YYYY/M/D hh:mm:ss').format()

while this gives the expected result 2018-08-30T15:00:00+08:00
moment.locale('zh-cn');
moment.tz.setDefault('Asia/Shanghai');
moment(`4、公告时间：2018/8/30 15:00:00`, '：YYYY/M/D hh:mm:ss').format()

Could someone please tell me why the colon is needed here to parse the datetime text? Is this an expected behavior?
Environment:
Chrome 68.0.3440.106 on OSX
If you are reporting an issue, please run the following code in the environment you are using and include the output:
console.log( (new Date()).toString())
console.log((new Date()).toLocaleString())
console.log( (new Date()).getTimezoneOffset())
console.log( navigator.userAgent)
console.log(moment.version)

output:
Mon Sep 17 2018 00:50:26 GMT+0800 (中国标准时间)
2018/9/17 上午12:50:26
-480
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.106 Safari/537.36
2.10.6

You're parsing the date using lenient or forgiving mode, which doesn't have clearly defined behaviour.  (You'd get more consistent and predictable behaviour using strict mode if you can)
A rough description of 'forgiving mode' would be that the parser works from left-to-right, skipping over any numbers or noise that don't match the format string (which is also being processed from left to right.)
So, in your first example the parser is looking for something matching 'YYYY', and finds 4, then looks for /, causing it to skip over 、公告时间：2018, and then proceeds to match M against 8 and process the rest of the string.
In the second case, the parser starts looking for :, so skips straight over 4、公告时间, and then proceeds to process the rest of the string as you expected.


Name of Transaction method

My OCD wants to rename the method Transaction to CreateTransaction to be more inline with CreateOrder and AddItem, etc. since it feels a little weird to be doing siftClient.Transaction(new Transaction { ... });
Obviously this would be a breaking change though. Thoughts?

Eh...not worth it. I know it's just following their documentation. Better keep it that way I guess.


TCP connection

We need to connect to the TWS api using TCP.
The connection docs are here.

GenServer to manage connection.
Handle sending and receiving messages: functions to send requests and receive messages from TWS.
Process incoming messages: Decode and process messages received from TWS according to the protocol specified in the TWS API documentation.

The docs from IBKR:
Connectivity
A socket connection between the API client application and TWS is established with the IBApi.EClientSocket.eConnect function. TWS acts as a server to receive requests from the API application (the client) and responds by taking appropriate actions. The first step is for the API client to initiate a connection to TWS on a socket port where TWS is already listening. It is possible to have multiple TWS instances running on the same computer if each is configured with a different API socket port number. Also, each TWS session can receive up to 32 different client applications simultaneously. The client ID field specified in the API connection is used to distinguish different API clients.
Establishing an API connection
Once our two main objects have been created, EWrapper and ESocketClient, the client application can connect via the IBApi.EClientSocket object:
    m_client.eConnect("<IP_ADDRESS>", 7497, 2);

eConnect starts by requesting from the operating system that a TCP socket be opened to the specified IP address and socket port. If the socket cannot be opened, the operating system (not TWS) returns an error which is received by the API client as error code 502 to IBApi.EWrapper.error (Note: since this error is not generated by TWS it is not captured in TWS log files). Most commonly error 502 will indicate that TWS is not running with the API enabled, or it is listening for connections on a different socket port. If connecting across a network, the error can also occur if there is a firewall or antivirus program blocking connections, or if the router's IP address is not listed in the "Trusted IPs" in TWS.
After the socket has been opened, there must be an initial handshake in which information is exchanged about the highest version supported by TWS and the API. This is important because API messages can have different lengths and fields in different versions and it is necessary to have a version number to interpret received messages correctly.
For this reason it is important that the main EReader object is not created until after a connection has been established. The initial connection results in a negotiated common version between TWS and the API client which will be needed by the EReader thread in interpreting subsequent messages.
After the highest version number which can be used for communication is established, TWS will return certain pieces of data that correspond specifically to the logged-in TWS user's session. This includes (1) the account number(s) accessible in this TWS session, (2) the next valid order identifier (ID), and (3) the time of connection. In the most common mode of operation the EClient.AsyncEConnect field is set to false and the initial handshake is taken to completion immediately after the socket connection is established. TWS will then immediately provides the API client with this information.
Important: The IBApi.EWrapper.nextValidID callback is commonly used to indicate that the connection is completed and other messages can be sent from the API client to TWS. There is the possibility that function calls made prior to this time could be dropped by TWS.
There is an alternative, deprecated mode of connection used in special cases in which the variable AsyncEconnect is set to true, and the call to startAPI is only called from the connectAck() function. All IB samples use the mode AsyncEconnect = False.
The EReader Thread
API programs always have at least two threads of execution. One thread is used for sending messages to TWS, and another thread is used for reading returned messages. The second thread uses the API EReader class to read from the socket and add messages to a queue. Everytime a new message is added to the message queue, a notification flag is triggered to let other threads now that there is a message waiting to be processed. In the two-thread design of an API program, the message queue is also processed by the first thread. In a three-thread design, an additional thread is created to perform this task. The thread responsible for the message queue will decode messages and invoke the appropriate functions in EWrapper. The two-threaded design is used in the IB Python sample Program.py and the C++ sample TestCppClient, while the 'Testbed' samples in the other languages use a three-threaded design. Commonly in a Python asynchronous network application, the asyncio module will be used to create a more sequential looking code design.
The class which has functionality for reading and parsing raw messages from TWS is the IBApi.EReader class.
    final EReader reader = new EReader(m_client, m_signal);

    reader.start();
    //An additional thread is created in this program design to empty the messaging queue
    new Thread(() -> {
        while (m_client.isConnected()) {
            m_signal.waitForSignal();
            try {
                reader.processMsgs();
            } catch (Exception e) {
                System.out.println("Exception: "+e.getMessage());
            }
        }
    }).start();

Now it is time to revisit the role of IBApi.EReaderSignal initially introduced in The EClientSocket Class. As mentioned in the previous paragraph, after the EReader thread places a message in the queue, a notification is issued to make known that a message is ready for processing. In the (C++, C#/.NET, Java) APIs, this is done via the IBApi.EReaderSignal object we initiated within the IBApi.EWrapper's implementer. In the Python API, it is handled automatically by the Queue class.
The client application is now ready to work with the Trader Workstation! At the completion of the connection, the API program will start receiving events such as IBApi.EWrapper.nextValidId and IBApi.EWrapper.managedAccounts. In TWS (not IB Gateway) if there is an active network connection, there will also immediately be callbacks to IBApi::EWrapper::error with errorId as -1 and errorCode=2104,2106, errorMsg = "Market Data Server is ok" to indicate there is an active connection to the IB market data server. Callbacks to IBApi::EWrapper::error with errorId as -1 do not represent true 'errors' but only notifications that a connection has been made successfully to the IB market data farms.
IB Gateway by contrast will not make connections to market data farms until a request is made by the IB client. Until this time the connection indicator in the IB Gateway GUI will show a yellow color of 'inactive' rather than an 'active' green indication.
When initially making requests from an API application it is important that the verifies that a response is received rather than proceeding assuming that the network connection is ok and the subscription request (portfolio updates, account information, etc) was made successfully.
Accepting an API connection from TWS
For security reasons, by default the API is not configured to automatically accept connection requests from API applications. After a connection attempt, a dialogue will appear in TWS asking the user to manually confirm that a connection can be made:
conn_prompt.png
To prevent the TWS from asking the end user to accept the connection, it is possible to configure it to automatically accept the connection from a trusted IP address and/or the local machine. This can easily be done via the TWS API settings:
tws_allow_connections.png
Note: you have to make sure the connection has been fully established before attempting to do any requests to the TWS. Failure to do so will result in the TWS closing the connection. Typically this can be done by waiting for a callback from an event and the end of the initial connection handshake, such as IBApi.EWrapper.nextValidId or IBApi.EWrapper.managedAccounts.
In rare cases in which IB Gateway or TWS has a momentarily delay in establishing connecting to the IB servers, messages sent immediately after receiving the nextValidId could be dropped and would need to be resent. If the API client has not receive the expected callbacks from issued requests, it should not proceed assumming the connection is ok.
Broken API socket connection
If there is a problem with the socket connection between TWS and the API client, for instance if TWS suddenly closes, this will trigger an exception in the EReader thread which is reading from the socket. This exception will also occur if an API client attempts to connect with a client ID that is already in use.
The socket EOF is handled slightly differently in different API languages. For instance in Java, it is caught and sent to the client application to IBApi::EWrapper::error with errorCode 507: "Bad Message". In C# it is caught and sent to IBApi::EWrapper::error with errorCode -1. The client application needs to handle this error message and use it to indicate that an exception has been thrown in the socket connection. Associated functions such as IBApi::EWrapper::connectionClosed and IBApi::EClient::IsConnected functions are not called automatically by the API code but need to be handled at the API client-level*.
This has been changed in API version 973.04

The first commit:
https://github.com/malloryerik/ibex/commit/d948bd4afd9023a883178db86624af70b7a73799
Next Steps
Sending and Receiving Messages: Extend this module to include functions for sending requests to TWS and handling responses. Format the messages according to the TWS API specification and parse incoming messages.
Handling EWrapper Interface: Implement the logic to handle callbacks from TWS (e.g., market data, order updates). This may involve decoding the messages received over the TCP connection and invoking the appropriate Elixir functions in response.
Error Handling: Implement robust error handling, especially for scenarios like connection loss or receiving malformed messages.

Connection works. Supervised genserver handles TCP connection lifecycle. Still needs enhancements.


can't unjail

5002.672 0.00% 200bps Inactive Unbonded penumbravalid14clrf3u5y63939pw5a0u9eqx8femp4m69naujg77avse3m9t2v8qe5sv4t   XPool
I have unjail  10 hours ago,but it's Inactive

this sounds like a question about using a Penumbra testnet. i would recommend asking over in the Discord server, which has dedicated channels for questions about running a validator. see the getting involved section of the readme.


Request: add option to open loclist when there are errors

Hi, thanks for ale, I'm finding it to be a great way to run linting without any UI lag. One option that I miss from neomake is g:neomake_open_list, which will automatically open the location list if there are errors (the option to preserve focus in the buffer you're editing is also nice). Any chance of something like this being added to ale?
The neomake description of this option is here:
https://github.com/neomake/neomake/blob/master/doc/neomake.txt#L242

Yeah, I'm totally in favour of that. I'd leave the option off by default, but if someone can make a decent pull request for it, I'll add that. I suppose the challenge is to not make it too annoying, as ALE will probably show errors more often.
I also opened an issue a while ago for populating the quick fix list. I think that should be done at some point.

It would be nice if it was an option to show on save if there are errors, but not during textchanged events.

@amadeus I only just noticed this comment. That option exists.
let g:ale_lint_on_save = 1
let g:ale_lint_on_text_changed = 0

@w0rp my interpretation of @amadeus's comment was to automatically show the loclist if there are errors, once you've stopped typing

This has been implemented now, and it is off by default. See :help g:ale_open_list.

Awesome, thank you!


[133] Clone Graph

Codecov Report

Merging #78 (618f929) into master (2676c38) will increase coverage by 0.6%.
The diff coverage is 94.0%.

Impacted Files
Coverage Δ

src/problem/p0133_clone_graph.rs
94.0% <94.0%> (ø)


Fastify SSR plugin

Siteup should offer an alternative way to build a site: fastify plugin.

Register a siteup plugin with fastify
On server start, scan a src or web folder
The cache folder would be reset
Static files and location are noted. Served statically in place.
CSS is pre-built into a cache folder. Served statically.
JS entry points are discovered and build into a cache folder. Served statically.
Static pages are build into the cache folder. Served statically.
JS pages that export some kind of api similar to next's getServerProps are served in place dynamically.

Full static builds cannot support getServerProps pages.

Closing till there is a concrete need.


Fix NicoNico Regex

Some NicoNico video IDs do not start with "sm" (e.g. https://www.nicovideo.jp/watch/nm14296458)

Misunderstood what you meant by cherry pick, sorry!

since we squashed your previous pr your main branch has way more commits than ours, that's we usually develop in so called feature branches.
I recommend you force push our main branch to your & apply the changes again in a new feature branch based of your main branch then & reopen the pr from said branch

Tried force pushing but ended up keeping it all in my main - hope that's ok

works for me as long as I have one commit


feat: Add EnvironmentParameters struct for improved environment initialization

Give an overview of the tasks completed
Introduced a new struct EnvironmentParameters to streamline the process of initializing environments in the Manager. This refactoring effort encapsulates block_rate and seed parameters within the new struct, making the code more readable and scalable for future additions.
Link to issue(s) that this PR closes
Closes #449

Looks like we gotta get the tests passing. @alikonuk1 do you need any help with that?


Error on ingesting samples with different value and the prometheus log does not show

Just like the issue on this page :
https://github.com/prometheus/prometheus/issues/2493
But I did not see the log that indicate the error metric?
I've noticed the log in prometheus should be like this?

This is the part of prometheus logs
time="2017-06-16T08:47:51Z" level=info msg="Indexing metrics in memory." source="crashrecovery.go:502"  time="2017-06-16T08:47:51Z" level=info msg="10000 metrics queued for indexing." source="crashrecovery.go:507"  time="2017-06-16T08:47:51Z" level=info msg="20000 metrics queued for indexing." source="crashrecovery.go:507"  time="2017-06-16T08:47:51Z" level=info msg="30000 metrics queued for indexing." source="crashrecovery.go:507"  time="2017-06-16T08:47:51Z" level=info msg="Indexing archived metrics." source="crashrecovery.go:510"  time="2017-06-16T08:47:51Z" level=info msg="40000 metrics queued for indexing." source="crashrecovery.go:523"  time="2017-06-16T08:47:51Z" level=info msg="50000 metrics queued for indexing." source="crashrecovery.go:523"  time="2017-06-16T08:47:51Z" level=info msg="60000 metrics queued for indexing." source="crashrecovery.go:523"  time="2017-06-16T08:47:51Z" level=info msg="70000 metrics queued for indexing." source="crashrecovery.go:523"  time="2017-06-16T08:47:52Z" level=info msg="80000 metrics queued for indexing." source="crashrecovery.go:523"  time="2017-06-16T08:47:52Z" level=info msg="90000 metrics queued for indexing." source="crashrecovery.go:523"  time="2017-06-16T08:47:52Z" level=info msg="100000 metrics queued for indexing." source="crashrecovery.go:523"  time="2017-06-16T08:47:52Z" level=info msg="110000 metrics queued for indexing." source="crashrecovery.go:523"  time="2017-06-16T08:47:52Z" level=info msg="120000 metrics queued for indexing." source="crashrecovery.go:523"  time="2017-06-16T08:47:52Z" level=info msg="All requests for rebuilding the label indexes queued. (Actual processing may lag behind.)" source="crashrecovery.go:529"  time="2017-06-16T08:47:52Z" level=info msg="Checkpointing fingerprint mappings..." source="persistence.go:1480"  time="2017-06-16T08:47:52Z" level=info msg="Done checkpointing fingerprint mappings in 1.537957ms." source="persistence.go:1503"  time="2017-06-16T08:47:52Z" level=warning msg="Crash recovery complete." source="crashrecovery.go:152"  time="2017-06-16T08:47:52Z" level=info msg="30673 series loaded." source="storage.go:378"  time="2017-06-16T08:47:52Z" level=info msg="Starting target manager..." source="targetmanager.go:61"  time="2017-06-16T08:47:52Z" level=info msg="Listening on :9090" source="web.go:259"  time="2017-06-16T08:47:53Z" level=warning msg="Error on ingesting samples with different value but same timestamp" numDropped=8 source="scrape.go:520"  time="2017-06-16T08:47:53Z" level=warning msg="Error on ingesting samples with different value but same timestamp" numDropped=7 source="scrape.go:520"  time="2017-06-16T08:47:55Z" level=warning msg="Error on ingesting samples with different value but same timestamp" numDropped=6 source="scrape.go:520"  time="2017-06-16T08:48:05Z" level=warning msg="Error on ingesting samples with different value but same timestamp" numDropped=7 source="scrape.go:520"  time="2017-06-16T08:48:06Z" level=warning msg="Error on ingesting samples with different value but same timestamp" numDropped=8 source="scrape.go:520"  time="2017-06-16T08:48:07Z" level=warning msg="Error on ingesting samples with different value but same timestamp" numDropped=8 source="scrape.go:520"  time="2017-06-16T08:48:08Z" level=warning msg="Error on ingesting samples with different value but same timestamp" numDropped=8 source="scrape.go:520"  time="2017-06-16T08:48:08Z" level=warning msg="Error on ingesting samples with different value but same timestamp" numDropped=7 source="scrape.go:520"  time="2017-06-16T08:48:10Z" level=warning msg="Error on ingesting samples with different value but same timestamp" numDropped=6 source="scrape.go:520"  time="2017-06-16T08:48:20Z" level=warning msg="Error on ingesting samples with different value but same timestamp" numDropped=7 source="scrape.go:520"  time="2017-06-16T08:48:21Z" level=warning msg="Error on ingesting samples with different value but same timestamp" numDropped=8 source="scrape.go:520"  time="2017-06-16T08:48:22Z" level=warning msg="Error on ingesting samples with different value but same timestamp" numDropped=8 source="scrape.go:520"  time="2017-06-16T08:48:23Z" level=warning msg="Error on ingesting samples with different value but same timestamp" numDropped=8 source="scrape.go:520"  time="2017-06-16T08:48:23Z" level=warning msg="Error on ingesting samples with different value but same timestamp" numDropped=7 source="scrape.go:520"  time="2017-06-16T08:48:25Z" level=warning msg="Error on ingesting samples with different value but same timestamp" numDropped=6

It makes more sense to ask questions like this on the prometheus-users mailing list rather than in a GitHub issue. On the mailing list, more people are available to potentially respond to your question, and the whole community can benefit from the answers provided.


AK -> CCS merge - 03 june 2019

The merge needed to be applied manually, since there was a version bump in AK to 2.7.0-SNAPSHOT.
Merge conflicts resolved for following files -
gradle.properties
tests/kafkatest/__init__.py
tests/kafkatest/version.py

Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

Created with target as master, closing this one.


listener (.on) to connection and disconnect events, and get peer id in server

Are these supported ? (in server)

@mm44 can you explain your problems/questions in more detail? I'm not sure I understand what the issue is.

Like https://github.com/peers/peerjs-server?tab=readme-ov-file#events


added playback_pos.sequence + playback_pos.line

as per Raul's request, added playback_pos.sequence + playback_pos.line & description of what pos_beats is.

These properties are already explained in the renoise.SongPos part.
I think it's a bad idea, as we would need to duplicate this information in other places as well (I'm counting 7 other places atm)

@bjorn-nesby
I modified this PR to only add one line of comments above pos_beats
--Playback position of the line at the given the beat position.
Hope that's fine


Anglican calendar

I'm adding https://github.com/martinellison/anglican_calendar (non Romanum sed Anglicanum).

Seems to be broken martinellison/anglican_calendar#1

you could add
http://gcarzino.cappellanigenova.it/programmi.html
The first is relative to a liturgical calendar for Romanum Liturgy
no code availabe (to now) for this link:
https://www.favrin.net/misc/calendario_liturgico/
both in Italian.
Regards,
Sergio Martino


Provide IPermit2 interface that extends from IAllowanceTransfer and ISignatureTransfer.sol

Projects that need to use both IAllowanceTransfer and ISignatureTransfer cannot do so because of the frozen version issue (the Permit2 contract is frozen to 0.8.17).
To address this use case, Permit2 should come with an IPermit2 interface that extends from IAllowanceTransfer and ISignatureTransfer.sol.

Closed via #225.


Open occurrences isn’t accurate in Dashboard Alarms grid

Type of issue

[x ] Bug
[ ] New feature
[ ] Improvement

Description

Open occurrences isn’t accurate in the Alarms grid (deep linking shows many alarms for the rule, the grid always shows just 1 occurrence)

dep: https://github.com/Azure/device-telemetry-dotnet/issues/50

Closing as a dup https://github.com/Azure/device-telemetry-dotnet/issues/50. Not a UI issue.


ElasticSearch errors with Action/metadata line [1] contains an unknown parameter [_type] status:400

I am trying to setup EFK (ElasticSearch 8, FluentD and Kibana) stack on K8S cluster (on-premises)
I followed this link to install elasticsearch and installed it using helm charts and followed this link to install fluentd
Log output of fluentd pod
2021-10-18 18:23:52 +0000 [info]: reading config file path="/fluentd/etc/fluent.conf"
2021-10-18 18:23:52 +0000 [info]: starting fluentd-0.12.43
2021-10-18 18:23:52 +0000 [info]: gem 'fluent-plugin-elasticsearch' version '1.18.0'
2021-10-18 18:23:52 +0000 [info]: gem 'fluent-plugin-kubernetes_metadata_filter' version '1.2.1'
2021-10-18 18:23:52 +0000 [info]: gem 'fluent-plugin-record-reformer' version '0.9.1'
2021-10-18 18:23:52 +0000 [info]: gem 'fluent-plugin-rewrite-tag-filter' version '1.6.0'
2021-10-18 18:23:52 +0000 [info]: gem 'fluent-plugin-secure-forward' version '0.4.5'
2021-10-18 18:23:52 +0000 [info]: gem 'fluentd' version '0.12.43'
2021-10-18 18:23:52 +0000 [info]: adding match pattern="fluent.**" type="null"
2021-10-18 18:23:52 +0000 [info]: adding filter pattern="kubernetes.**" type="kubernetes_metadata"
2021-10-18 18:23:53 +0000 [info]: adding match pattern="**" type="elasticsearch"

Output of fluentd and elasticsearch pods
[root@ctrl01 ~]#  kubectl get pods
NAME                                                     READY   STATUS    RESTARTS   AGE
elasticsearch-master-0                                   1/1     Running   0          136m

[root@ctrl01 ~]#  kubectl get pods -n kube-system
NAME                                                            READY   STATUS    RESTARTS   AGE
fluentd-cnb7p                                                   1/1     Running   0          107m
fluentd-dbxjk                                                   1/1     Running   0          107m

However, elasticsearch log was piled up with the following warning messages
2021-10-18 12:13:12 +0000 [warn]: temporarily failed to flush the buffer. next_retry=2021-10-18 12:13:42 +0000 error_class="Elasticsearch::Transport::Transport::Errors::BadRequest" error="[400] {\"error\":{\"root_cause\":[{\"type\":\"illegal_argument_exception\",\"reason\":\"Action/metadata line [1] contains an unknown parameter [_type]\"}],\"type\":\"illegal_argument_exception\",\"reason\":\"Action/metadata line [1] contains an unknown parameter [_type]\"},\"status\":400}" plugin_id="out_es"
2021-10-18 12:13:12 +0000 [warn]: suppressed same stacktrace

Conf file (tailored output)
2021-10-18 12:09:10 +0000 [info]: using configuration file: <ROOT>
  <match fluent.**>
    @type null
  </match>
  <match **>
    @type elasticsearch
    @id out_es
    @log_level info
    include_tag_key true
    host <IP_ADDRESS>
    port 9200
    scheme http
    ssl_verify true
    reload_connections true
    logstash_prefix logstash
    logstash_format true
    type_name fluentd
    buffer_chunk_limit 2M
    buffer_queue_limit 32
    flush_interval 5s
    max_retry_wait 30
    disable_retry_limit
    num_threads 8
  </match>

I am not sure why '@type elasticsearch' was not recognized.  Kindly let me know the reason for the issue or let me know whether am I doing something wrong

It seems that this issue is the same as https://github.com/uken/fluent-plugin-elasticsearch/issues/847.

Fix: Add "Suppress_Type_Name On" to Elastic Search output plugin:
[OUTPUT]
Name es
Match kube.*
Host elastic-search-REDACTED
......................REDACTED LINES
Logstash_Format On
Retry_Limit False
Suppress_Type_Name On


Allow filters to do a preorder traversal of the document tree

Setting the field preorder in a filter to a truthy value causes the
traversal of the subtree to be preorder. I.e., parent nodes are handled
first, even if they have a different type.
One use-case for this is to check whether a subtree is below a specific
element.

The code is a bit crude and slightly ugly; but as the topic of traversal order seems to come up frequently, it might still be useful to have this.

In Text.Pandoc.Generic we have bottomUp and topDown.  To me, that terminology is more intuitive than preorder. (What I associate with "preorder" is the mathematical meaning -- a binary relation that is reflexive and transitive.)
So, what about topdown or something like that?

topdown is much better, thanks.
The feature would probably be most useful if users could opt-out of automatic traversal of subnodes. E.g., to prevent the children of a refs div from being traversed, one might write
local my_filter
local function handle_refs(div)
  if div.identifier == 'refs' then
    return div
  else
    return div:walk(my_filter)
  end
end
my_filter = {
  traversal = 'truncating'  -- one of 'topdown', 'truncating', 'typewise'
  Div = handle_refs,
  -- more functions
}
return {my_filter}

Not sure though if that's the most intuitive interface.

I added a commit with a proof of concept for a third walk variant: If there is a Lua filter function for an element, then it's that function's responsibility to filter the subtree. If there is no function, then traversal will continue normally.

Or maybe cutting the traversal short should happen at the filter-function/element level. As in, if false is returned as a second return value, then don't process the element any further.

I like this last idea (second return value).  Would it also apply to regular bottom-up walks?

I had briefly considered bottom-up, but then decided to postpone anything related to them.

I'm a little scared of the necessary code changes.
The use-case is less clear to me.
There should probably be an "all-in-one" bottom-up traversal instead of the type-wise walking we currently do.
The semantics appear less clear: is a node not processed if one of its subtrees signals a processing stop, or only if all of them do so? It should probably be the former, so the rest of the doc would remain unprocessed.

So no real reason against it, just me being avoidant. Do you consider it important to include it? If so, then I'd add a bottomup traversal method and see if I can retrofit type-wise-walking as well.

No, I was just idly wondering. It's harder to think of real uses for stopping the bottom-up traversal.

Thanks for all the feedback! Merging now, but might require some more fine-tuning.


Support Windows platform

Feature Request
I would love this module to work with react-native-windows (0.61+).
I've tried to build a simple version of it following their documentation, but I'm not skilled enough in C# or C++ to do it. (But I'd be very glad to help if someone helps me get started).

I'd recommend reaching out to https://github.com/RedMadRobot/. This is a simple wrapper, if they supported the native platform, we could add RN support pretty easily


Can you update the code with kapre3.0? I feel that the change of kapre3.0 is very large, especially get_ melspectrogram_ Layer and Melspectrogram are very different

def Conv1D(N_CLASSES=6, SR=16000, DT=0.5):
i = layers.Input(shape=(1, int(SR*DT)), name='input')
x = Melspectrogram(n_dft=512, n_hop=160,
padding='same', sr=SR, n_mels=128,
fmin=0.0, fmax=SR/2, power_melgram=2.0,
return_decibel_melgram=True, trainable_fb=False,
trainable_kernel=False,
name='melbands')(i)

Having the same issue here...

Took a look at this today. The code should be updated to use kapre==0.3.4.


Usersync: Support undeleting a user

Since we use soft deletes in Gorm, a removed remote user will soft-delete the local user. If the remote user appears again at a later stage the user syncer will have an issue undeleting the soft-deleted user.

Not really an isse any more as soft deletes was removed in d7b2d5a4614426df139fe9bc44a404cd99caa7a8.


Get messages: filtering by channel or direct message

At the moment, there isn't a filter when a message arrives to the node.
It could be a nice feature filtering by a channel or a list of channel or DM to the bot

Feature added on @mindofbeholder PR


pulseaudio: Don't depend on systemd when doing libonly

Description of changes
This issue is part of a series of bugfixes to improve the i686 cross-compilation pipeline.
Tracking issue: https://github.com/NixOS/nixpkgs/issues/195967
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

This has to target staging due to the mass rebuilds

libOnly already means that systemd isn't a dep
https://github.com/NixOS/nixpkgs/blob/042598f1989709751cab749a94dffdba9e926593/pkgs/servers/pulseaudio/default.nix#L76-L80


Does yunikorn support Hadoop-mapreduce workload on k8s?

Does yunikorn support Hadoop-mapreduce workload on k8s?

Hi @wongxingjun
YuniKorn is a scheduler, it should be general enough to support MR workloads, which spawns a large number of small-batch tasks. However, to run MR on K8s, there is some more work to be done at 2nd level scheduling, like the MR-app-master in YARN. In K8s world, it can be a controller. This is out of the scope of YuniKorn.

Thanks for your reply.  Acctually, a complex k8s controller or a customized operator is needed to figure out this problem.


llvmPackages: improve gcc compatibility

Description of changes
As recommended by @tomberek, add common flags to prevent many issues that LLVM would have but GCC wouldn't have.

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

This commit breaks firefox and thunderbird
error: builder for '/nix/store/slax6bvi346jmqjpbh3ixizjgs4bhir5-thunderbird-unwrapped-115.13.0.drv' failed with exit code 1;
last 10 log lines:
>  0:09.06(B DEBUG: |   ;(B(B
>  0:09.06(B DEBUG: |   return 0;(B(B
>  0:09.06(B DEBUG: | }(B(B
>  0:09.06(B DEBUG: Executing: /nix/store/jl7pn7ahvq0kyr86pf0w2c2h9ca1pn94-wasm32-unknown-wasi-clang-wrapper-18.1.8/bin/wasm32-unknown-wasi-cc -std=gnu99 /build/conftest.4mv9xe3w.c --sysroot=/nix/store/6mqf2cb15b436zgwc84dgjpv5vbawih0-wasi-sysroot(B(B
>  0:09.06(B DEBUG: The command returned non-zero exit status 1.(B(B
>  0:09.06(B DEBUG: Its error output was:(B(B
>  0:09.06(B DEBUG: | wasm-ld: error: unknown argument: --undefined-version(B(B
>  0:09.06(B DEBUG: | clang: error: linker command failed with exit code 1 (use -v to see invocation)(B(B
>  0:09.06(B ERROR: Cannot find wasi libraries or problem with the wasm linker. Please fix the problem. Or build with --without-wasm-sandboxed-libraries.(B(B
> *** Fix above errors and then restart with "./mach build"
For full logs, run 'nix log /nix/store/slax6bvi346jmqjpbh3ixizjgs4bhir5-thunderbird-unwrapped-115.13.0.drv'.
error: 1 dependencies of derivation '/nix/store/cv3r6hwbxhrkq50f060q3c4ajqb2dmfv-thunderbird-115.13.0.drv' failed to build
note: keeping build directory '/tmp/nix-build-firefox-unwrapped-128.0.3.drv-2/build'
error: builder for '/nix/store/4asrnhz2i3whvapghmalk1cpjsn3rja1-firefox-unwrapped-128.0.3.drv' failed with exit code 1;
last 10 log lines:
>  0:10.50(B DEBUG: |   ;(B(B
>  0:10.50(B DEBUG: |   return 0;(B(B
>  0:10.50(B DEBUG: | }(B(B
>  0:10.50(B DEBUG: Executing: /nix/store/jl7pn7ahvq0kyr86pf0w2c2h9ca1pn94-wasm32-unknown-wasi-clang-wrapper-18.1.8/bin/wasm32-unknown-wasi-cc -std=gnu99 /build/conftest.muc6eb2g.c --sysroot=/nix/store/6mqf2cb15b436zgwc84dgjpv5vbawih0-wasi-sysroot(B(B
>  0:10.50(B DEBUG: The command returned non-zero exit status 1.(B(B
>  0:10.50(B DEBUG: Its error output was:(B(B
>  0:10.50(B DEBUG: | wasm-ld: error: unknown argument: --undefined-version(B(B
>  0:10.50(B DEBUG: | clang: error: linker command failed with exit code 1 (use -v to see invocation)(B(B
>  0:10.50(B ERROR: Cannot find wasi libraries or problem with the wasm linker. Please fix the problem. Or build with --without-wasm-sandboxed-libraries.(B(B
> *** Fix above errors and then restart with "./mach build"
For full logs, run 'nix log /nix/store/4asrnhz2i3whvapghmalk1cpjsn3rja1-firefox-unwrapped-128.0.3.drv'.

Sorry about that @spiage, #332170 should fix it.

Thank you! =)
I'll tell you the result if you want

Can you add me as a reviewer on PRs like this in future?
I'm not convinced this is a good idea — compiler authors turn things into errors for a reason, and as a distribution we have our part to play in getting problematic things fixed.  It's fine to disable the errors for packages where it's not reasonably possible to get them fixed, but doing it globally means even packages that would be simple to fix properly don't get fixed.

To expand a bit, the problem with this sort of thing is that it's very difficult later to tell when it can be removed.  By setting this globally instead of setting it for individual packages that need it, we're effectively stuck with it forever, because it's impossible to tell if removing it is going to break any packages.  If we mark packages individually, it's very easy to tell in future when those markings can be removed.
This isn't a theoretical concern: something similar was done for pkgsMusl — some compatibility headers were added globally, instead of fixing individual affected packages, and now, even though we've discovered that the presence of those headers actually causes problems for other packages, it's impossible to know what the fallout would be of removing it.  Let's not repeat this mistake.

Now I get ld: unknown option: --undefined-version when I switched to nixos-unstable for macOS and using llvmPackages_17.

Now I get ld: unknown option: --undefined-version when I switched to nixos-unstable for macOS and using llvmPackages_17.

In nixos-24.05 everything works.

@RossComputerGuy


not get the images when extract optical_flow

when run bash scripts/extraction_optical_flow.sh UCF101 result 2
I get 13320 empty folder in result  and  no provide me error
my opencv support videoIO
please give me some suggestion,thank you!

opencv 3.0.0

See #28

@yjxiong Thank you for your reply. When run bash scripts/extract_optical_flow.sh UCF-101 result 2, but I  got 13320 empty folders.
No error feedback，so I do not how to solve.

You can run extract_flow_gpu on one video and see what happens to know the problem.

This error has occurred：
sugon@sugon-W580-G20:~/TSNCode/temporal-segment-networks/lib/dense_flow/build$ ./extract_gpu 1.avi
2017-07-30 15:02:18,634 FATAL [default] Check failed: [video_stream.isOpened()] Cannot open video stream "ex2.avi" for optical flow extraction.
2017-07-30 15:02:18,634 WARN  [default] Aborting application. Reason: Fatal log at [/home/sugon/TSNCode/temporal-segment-networks/lib/dense_flow/src/dense_flow_gpu.cpp:15]
------------------ 原始邮件 ------------------
发件人<EMAIL_ADDRESS>发送时间: 2017年7月30日(星期天) 下午2:43
收件人<EMAIL_ADDRESS>抄送<EMAIL_ADDRESS><EMAIL_ADDRESS>主题: Re: [yjxiong/temporal-segment-networks] not get the images whenextract optical_flow (#118)
You can run extract_flow_gpu on one video and see what happens to know the problem.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

I have updated my Nvidia-drivers, now I get the image. I have solved this problem. Thank you very much.

Good to know. Happy experimenting.

hello,I got the same issue,and i run extract_flow_gpu on one video still got one empty file and no error.
my opencv is 2.4.9
any suggestion?thx a lot

See #28

@yjxiong  i docker pull the image you provided, then i run build_all.sh and 'happy experimenting' appeared, but when i run scripts/extract_optical_flow.sh, i meet the same question as @milkcat0904
, i sure the path is right, i don't think the extract_gpu worked. any suggestion? thank u
你好，我通过docker下载了你的镜像，并成功运行了build_all.sh,出现了 'happy experimenting'<EMAIL_ADDRESS>cmd = os.path.join(df_path + 'build/extract_gpu')+' -f {} -x {} -y {} -i {} -b 20 -t 1 -d {} -s 1 -o {} -w {} -h {}'.format(quote(vid_path), quote(flow_x_path), quote(flow_y_path), quote(image_path), dev_id, out_format, new_size[0], new_size[1])
os.system(cmd)
这两句好像没起作用，因此想询问一下是什么原因，能给我一些建议吗？ 谢谢

See #28

@yjxiong i docker pull the image you provided, then i run build_all.sh and 'happy experimenting' appeared, but when i run scripts/extract_optical_flow.sh, i meet the same question as @wcj021312
, i sure the path is right, i don't think the extract_gpu worked. any suggestion? thank u
你好，我通过docker下载了你的镜像，并成功运行了build_all.sh,出现了 'happy experimenting' ，但是当我运行scripts/extract_optical_flow.sh的时候，出现了和@wcj021312 相同的问题，在提取UCF视频集的时候，在输出文件夹中出现了13000多个空的文件夹，我看了build_of.py的源码，感觉
cmd = os.path.join(df_path + 'build/extract_gpu')+' -f {} -x {} -y {} -i {} -b 20 -t 1 -d {} -s 1 -o {} -w {} -h {}'.format(quote(vid_path), quote(flow_x_path), quote(flow_y_path), quote(image_path), dev_id, out_format, new_size[0], new_size[1])
os.system(cmd)
这两句好像没起作用，因此想询问一下是什么原因，能给我一些建议吗？ 谢谢

Try this command instead:  cmd = os.path.join(df_path + 'build/extract_gpu')+' -f={} -x={} -y={} -i={} -b=20 -t=1 -d={} -s=1 -o={} -w={} -h={}'.format(quote(vid_path), quote(flow_x_path), quote(flow_y_path), quote(image_path), dev_id, out_format, new_size[0], new_size[1])

@ymxv @sousoul Hello, I met the same problem, have you solved it?


Upgrading to annual member doesn't set upgrading account's own referrer

Account's referrer should be set here but it is not.
We should have a test case to prove this.

Also need to test that the referrer is reset correctly when membership expires.  NB resetting is lazy (i.e. only reset when annual member would have gotten additional fees).

Lucky us, we can still sync with the above patch.  Very similar to #453 : None of the incorrectly allocated funds have been withdrawn from their VBO, so we can simply reinterpret the history to compute the balances correctly without invalidating any tx's.


added ensureTrailingSlashOnParentUri to endpoints

Hi Basti,
here is the pullrequest as discussed in #1.
Cheers,
Andy

Awesome, thanks! Merged.
I moved the test logic from EndpointBaseTest to CustomEndpointTest.TestEnsureTrailingSlashOnParentUri() in an additional commit (03ef352).


Parsing error in runtime IBMBackend page

URL to the relevant documentation
https://docs.quantum.ibm.com/api/qiskit-ibm-runtime/qiskit_ibm_runtime.IBMBackend#run
Select all that apply

[ ] typo
[X] code bug
[ ] out-of-date content
[ ] broken link
[ ] other

Describe the fix.
Look like the API docs are being parsed incorrectly (see "or" / "to")

It seems like the problem was in the HTML. I created a PR in the runtime repo to fix it :+1:


[WIP] Conversion to Godot 4.1.1

Complete conversion to Godot 4.1.1.
It's in pretty good shape and usable, but still a work in progress because I want to take advantage of the new static properties.
Will update this PR as I go.

@ephread Amazing work! Regarding the open issue:

I want to take advantage of the new static properties

Is this just an internal refactor or does it materially affect a game's integration with inkgd? If it's the former, would there be value in already merging your work to the main branch and make it the default work stream so folks can start using it in their games?
I think this would help getting more eyes on functionality and code earlier, and regressions can be found more quickly. WDYT?
I haven't personally started migrating my game to Godot 4 yet because inkgd is the primary logic driver in my game so it's a bit of a catch-22 for me.
Has anyone else already started integrating against this branch? I think @francoisdlt has already?

Yes I have started using the godot4 branch in production. So far so good !


ImplementContentModelAttribute vs PublishedContentModelAttribute

See [#4] - ImplementContentModelAttribute (belongs to ModelsBuilder) and PublishedContentModelAttribute (belongs to Umbraco) should more or less do the same / be merged / whatever.

ImplementContentModelAttribute has (is going to have) many more options than just specifying the alias, and is used by the builder to determine how to implement a content type. The two attributes have different usages and are not exclusive.
Closing, won't do.


Project 1 Feedback (Scapsulators)

Just ran your project, and I have a couple of comments and suggestions -
Build time took around 12-14 minutes, was easy to follow from the readme files.

Implementation of CircleCI for continous builds on commits
Using docker-hub instead of individually building each microservice in your main repo
Time slot selection doesn't seem so intuitive at all
Could've explored more properties instead of just reflectivity
Also not sure how you're handling the error when there's no data for the querry

Rest great work! Loved your project as such
Reviewed by Team Scapsulators (https://github.com/airavata-courses/scapsulators)

Thanks @shubhpatr much appreciated.
We would try to cover the mentioned points in the next sprint.


Is this repo still mantained?

Is this repo still mantained?

Not really, and I'm sorry for that!
I'd be happy if someone would be willing to take over maintainership.

Would you be open for that, @theigl? Not sure about the current state of Kryo and how kryo-serializers still fit.

Hi @magro! kryo-serializers is still relevant for Kryo 5 because there are no built in serializers for unmodifiable and synchronized collections. Also Guava and JodaTime are still widely used. I think I can take over maintaining this library. I'm currently on vacation and will get back to you in 2 weeks.

Sounds great, @theigl! I've invited you as collaborator now. Enjoy your vacation! :v:

@magro: Thanks a lot!
What permissions do I need to perform a release? I guess you will need to add me somewhere? Is the release process the same as for Kryo?

Exactly, you need to get push permissions for sonatype for the related groupId. What's you sonatype username, @theigl?

I just created https://issues.sonatype.org/browse/OSSRH-93213

@theigl As https://issues.sonatype.org/browse/OSSRH-93213 is resolved you could try to publish something...

Thanks @magro!


No Network Traffic

I'm having the same issue as here: https://github.com/scoutapp/scout_realtime/issues/10
I posted there but no response, maybe since it was already closed...
Running on a CentOS 6.5 machine. The main interface is eth1 and I get no activity in the network traffic graph.
I have server_metrics-1.2.7 and scout_realtime-1.0.5 gems
cat /proc/net/dev
Inter-|   Receive                                                |  Transmit
 face |bytes    packets errs drop fifo frame compressed multicast|bytes    packets errs drop fifo colls carrier compressed
    lo:8440299585 20368570    0    0    0     0          0         0<PHONE_NUMBER> 20368570    0    0    0     0       0          0
  eth0:       0       0    0    0    0     0          0         0        0       0    0    0    0     0       0          0
  eth1:60071239046 278737597    6    0    0     6          0   7983469<PHONE_NUMBER>28 401901559    0    0    0     0       0          0

ruby -e "puts RbConfig::CONFIG['target_os']"
linux

Any help?

Same issue here on Archlinux with kernel 3.14.33-1-lts with scout realtime v1.0.5

Same on Fedora 22. This is so cool. I so hope someone is still developing this forward.

If you have Docker installed alongside Scout Runtime see this post.


Add Brotli4J submodule

The official brotli JVM implementation only supports decompression. In order to support compression we introduce a new module that uses Brotli4J(https://github.com/hyperxpro/Brotli4j) instead. See also discussion: https://github.com/lhns/fs2-compress/pull/151
Solves: https://github.com/lhns/fs2-compress/issues/105

released in v2.2.0


Keep Getting "failed to initialize services: D8E06406"

I keep getting the error message
failed to initialize services: D8E06406
every time I launch the app in Homebrew Launcher

Make sure you're using the latest version, and run a kernel exploit like fasthax before FBI.

👍


Add Tests

for testing file name with spaces
verifying url pattern for blobs

@maxandersen  for file names with spaces I am using java.net.URLDecoder.decode function to decode and use that . I need suggestion from you on this on how to test . One way could be to have a function in code that process the filePath(using java.net.URLDecoder.decode) and then I add the normal unit tests to that function .

For blobs it's simple. I can simply match valid and invalid URL patterns .


Changing import statements to require.

For use without babel.
Description
Changing import statements to require statements for use without babel.
Tests
Ran yarn test in modzy instance.
Checklist

[ x] I read the Contributing guide.
[ x] I update the documentation and if the case the README.md file.
[ x] I am willing to follow-up on review comments in a timely manner.

Thank you!