Scholarship Winner Not Appearing on Naughty or Nice Closed State

Current Behavior
Despite having all the necessary winner fields filled out on the run node (6601), the front end of the closed state is still saying that we are sifting through applications.
Desired Behavior
When a campaign has a number in the incentive field of the /edit view of the campaign node and has winner information filled out on the associated run node, the front end of the closed state should show the scholarship winner. Working example: https://www.dosomething.org/us/campaigns/thumb-wars
Steps to Replicate
This seems to only be happening on Naughty or Nice on production and Thor. Other campaigns are working fine. The one difference for this campaign is that the original language for the campaign was GL EN.
I can't replicate on another campaign that had the original language as GL EN -- I tried: https://thor.dosomething.org/campaigns/happy-scrappy-holidays, and it worked. I could totally be missing something, but I have no other ideas about what to try.
Why This Matters
We want to fame scholarship winners on the closed state for the individual, but also to let other members know that we do actually give out scholarships. :)
Relevant Screenshots + Links
https://www.dosomething.org/us/campaigns/naughty-or-nice

@namimody is this only on one specific campaign or all campaigns?

Only on this specific campaign @angaither. @mikefantini and I can't figure out why.

@namimody is there other content that should be getting pulled in that isn't, or is it just winner content?

@namimody the winner content is pulling from the run node referenced in the global english version of the campaign
I think this might be because en global is the default language of the node, so it's pulling form the run in that language
see https://thor.dosomething.org/node/6153
I'm going to close this issue out, and we can open a different one if we find runs aren't working across multiple languages (they may not be)

Ooof thanks @angaither. This is fun: there are two "Naughty or Nice run 1"s with very similar time frames. The two translations of the campaign are associated with different runs. Both runs are translated.

For now, I added the scholarship winner information to the run associated with the GL EN translation of the site.
However, we need to:
a) figure out which run signups/reportbacks are associated with and then delete the other one
b) fix this issue with runs -- @angaither doesn't this scenario indicate that the campaigns default language trumps associations of campaign translations with runs?


Update sbt-header to 5.6.5

Updates de.heikoseeberger:sbt-header from 5.6.0 to 5.6.5.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "de.heikoseeberger", artifactId = "sbt-header" } ]

labels: sbt-plugin-update, early-semver-patch, semver-spec-patch, commit-count:1

Codecov Report

Merging #147 (2fddaa2) into master (020cfae) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #147   +/-   ##
=======================================
  Coverage   97.73%   97.73%
=======================================
  Files          23       23
  Lines         265      265
  Branches       11       11
=======================================
  Hits          259      259
  Misses          6        6


Updated stk link.

Reference Issue

What does this implement/fix? Explain your changes.
Fixes broken link to stk docs, due to domain change.
Any other comments?

Thanks @lukasturcani !


Own library on Android/Shield causes exception

If I enable the own library in the options and try to open the plugin afterwards I get this exception on Android on Nvidia Shield:
12:57:19.702 T:138159989840   ERROR: EXCEPTION Thrown (PythonToCppException) : -->Python callback/script returned the following error<--
                                             - NOTE: IGNORING THIS CAN LEAD TO MEMORY LEAKS!
                                            Error Type: <type 'exceptions.OSError'>
                                            Error Contents: [Errno 30] Read-only file system: 'special:'
                                            Traceback (most recent call last):
                                              File "/storage/emulated/0/Android/data/org.xbmc.kodinerds/files/.kodi/addons/plugin.video.netflix/addon.py", line 23, in <module>
                                                log_fn=kodi_helper.log
                                              File "/storage/emulated/0/Android/data/org.xbmc.kodinerds/files/.kodi/addons/plugin.video.netflix/resources/lib/Library.py", line 57, in __init__
                                                self.series_label: self.tvshow_path
                                              File "/storage/emulated/0/Android/data/org.xbmc.kodinerds/files/.kodi/addons/plugin.video.netflix/resources/lib/Library.py", line 73, in setup_local_netflix_library
                                                os.makedirs(source[label])
                                              File "/opt/dev/kodi/android/kodinerds-master-aarch64/tools/depends/xbmc-depends/aarch64-linux-android-android-21-release/lib/python2.7/os.py", line 150, in makedirs
                                              File "/opt/dev/kodi/android/kodinerds-master-aarch64/tools/depends/xbmc-depends/aarch64-linux-android-android-21-release/lib/python2.7/os.py", line 150, in makedirs
                                              File "/opt/dev/kodi/android/kodinerds-master-aarch64/tools/depends/xbmc-depends/aarch64-linux-android-android-21-release/lib/python2.7/os.py", line 150, in makedirs
                                              File "/opt/dev/kodi/android/kodinerds-master-aarch64/tools/depends/xbmc-depends/aarch64-linux-android-android-21-release/lib/python2.7/os.py", line 150, in makedirs
                                              File "/opt/dev/kodi/android/kodinerds-master-aarch64/tools/depends/xbmc-depends/aarch64-linux-android-android-21-release/lib/python2.7/os.py", line 157, in makedirs
                                            OSError: [Errno 30] Read-only file system: 'special:'
                                            -->End of Python script error report<--

@maniacgit What path did you choose for storing the files?

I've tried it with the defalut path special://profile/addon_data/plugin.video.netflix

Should be fixed in version 0.11.24


Add secondary actions when swiping down on iPadOS

The native iOS keyboard has swipe support for its buttons, which means that you can have two actions on the same button. This should be added to KeyboardKit as well.

You mean for iPad? I'm currently thinking on how to create a feasible native-like iPad style for your keyboard. Any ideas?

Yeah, I was thinking about the secondary actions that you have on iPad, where you can swipe down to perform another action. I think I'll halt this until SwiftUI matures enough to make it easier to achieve.

This will be implemented as a SwiftUI exclusive feature later in 3.x or 4.x.

I will not make this in 3.5 and probably not even in 3.6 so I remove this for now.

I will not make this in 3.5 and probably not even in 3.6 so I remove this for now.

+1 for adding this feature.

I realized that I will have to plan this after the new gesture engine is done.

Trigger that action on swipe down (iPad only?)

I think adding a swipe down trigger for the action would be useful not only on iPad but also on iPhone. It could serve as an alternative method to trigger keys with a single callout option in certain scenarios (e.g., a letter is only available as a callout character). For me personally, any default behavior is fine as long as it's customizable :)

@digitalheir @f-person @lvandal @nikans I'm going to look at this after 9.0 is out 👍


First pass through NsOneProvider

This is a quick pass through adding basic record support for NS1.

[x] Tests

@weyrick tests have been fleshed out and a few fixes put in place. If you want to 👀  it again and give a 👍  / 👎  I think it's ready for it.

👍  thanks!

What level of geo support is included in this version of the NS1 provider?

What level of geo support is included in this version of the NS1 provider?

There's currently no geo support in Ns1Provider. This PR was just a first pass to get basic record support in place. Working with the geo dns apis of providers is usually quite a bit more involved and testing all of the edge cases takes a bit of work as well. That's not something I'll be able to tackle in the near-term as since its more time that I can spare for the purpose in nights & weekends.

@ross That's too bad but I totally understand.
@weyrick Any chance NS1 can contribute geo support? Understanding it will be a limited application of filter chains to achieve that. NS1 keeps banging on us to go multi-DNS everytime there's an outage, so this would help that a lot.

See also ns1/nsone-python#28


Not working in Laravel 7.0 - Translate Route

I update to version 1.0.3 and show this message:
In AbstractRouteCollection.php line 210:
Unable to prepare route [admin/user/{user_id}/comment/ajax/{id}/translate/{lang}] for serialization. Another route has already been assigned name [comment.translateItem].
Thanks!

Hi @PiahDoNeumann,
Sorry, I had not checked that route.
I have fixed it therefor, please update the package via composer update.
Thanks,

Thanks @onkbear


Single sign-on required for AAD group writeback?

In the page mentioned below it is described that single sign-on is required for AAD Connect group writeback.
Is it a pre-requisite for enabling group writeback or an optional feature only?

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

ID: cba137cc-67ca-2766-b436-54e3634f0c2f
Version Independent ID: 2f185fba-dcf2-04f5-17a1-b641dc104edd
Content: Azure AD Connect: Group writeback
Content Source: articles/active-directory/hybrid/how-to-connect-group-writeback.md
Service: active-directory
Sub-service: hybrid
GitHub Login: @billmath
Microsoft Alias: billmath

Hello @heikobischoff, thanks for the question! We are taking a look into this and will get back to you soon.

No, SSO is not required for group write back itself, but it would be needed for the use case for which it was designed - “as an on premise user I can interact in O365 with Office groups”.   We do not support any other use cases for group write back at the moment .


AttributeError: 'G' object has no attribute 'landmarks'

!python test.py molo2 --pretrained_models_path "/content/ID-disentanglement/stylegan_G_256x256_synthesis/" \
    --load_checkpoint "/content/drive/MyDrive/checkpoint" \
    --input_dir "/content/id" \
    --output_dir "/content/out" \
    --test_func interpolate

/usr/local/lib/python3.6/dist-packages/tensorflow/python/keras/engine/base_layer.py:2281: UserWarning: `layer.add_variable` is deprecated and will be removed in a future version. Please use `layer.add_weight` method instead.
  warnings.warn('`layer.add_variable` is deprecated and '
Wrong data format for .ipynb_checkpoints
Traceback (most recent call last):
  File "test.py", line 45, in <module>
    main()
  File "test.py", line 41, in main
    test_func()
  File "/content/ID-disentanglement/inference.py", line 115, in interpolate
    const_img = self.G(const_img, const_img)[0]
  File "/usr/local/lib/python3.6/dist-packages/tensorflow/python/keras/engine/base_layer.py", line 1012, in __call__
    outputs = call_fn(inputs, *args, **kwargs)
  File "/usr/local/lib/python3.6/dist-packages/tensorflow/python/eager/def_function.py", line 828, in __call__
    result = self._call(*args, **kwds)
  File "/usr/local/lib/python3.6/dist-packages/tensorflow/python/eager/def_function.py", line 871, in _call
    self._initialize(args, kwds, add_initializers_to=initializers)
  File "/usr/local/lib/python3.6/dist-packages/tensorflow/python/eager/def_function.py", line 726, in _initialize
    *args, **kwds))
  File "/usr/local/lib/python3.6/dist-packages/tensorflow/python/eager/function.py", line 2969, in _get_concrete_function_internal_garbage_collected
    graph_function, _ = self._maybe_define_function(args, kwargs)
  File "/usr/local/lib/python3.6/dist-packages/tensorflow/python/eager/function.py", line 3361, in _maybe_define_function
    graph_function = self._create_graph_function(args, kwargs)
  File "/usr/local/lib/python3.6/dist-packages/tensorflow/python/eager/function.py", line 3206, in _create_graph_function
    capture_by_value=self._capture_by_value),
  File "/usr/local/lib/python3.6/dist-packages/tensorflow/python/framework/func_graph.py", line 990, in func_graph_from_py_func
    func_outputs = python_func(*func_args, **func_kwargs)
  File "/usr/local/lib/python3.6/dist-packages/tensorflow/python/eager/def_function.py", line 634, in wrapped_fn
    out = weak_wrapped_fn().__wrapped__(*args, **kwds)
  File "/usr/local/lib/python3.6/dist-packages/tensorflow/python/eager/function.py", line 3887, in bound_method_wrapper
    return wrapped_fn(*args, **kwargs)
  File "/usr/local/lib/python3.6/dist-packages/tensorflow/python/framework/func_graph.py", line 977, in wrapper
    raise e.ag_error_metadata.to_exception(e)
AttributeError: in user code:

    /content/ID-disentanglement/model/generator.py:42 call  *
        lnds = self.landmarks(x2)

    AttributeError: 'G' object has no attribute 'landmarks'

Same issue, is there any fix yet?

The issue is due to the landmarks attribute is not instantiated properly when in test mode (the train flag is False). A quick workaround to the issue is to set the lnds variable to None in the call method.
# lnds = self.landmarks(x2)
lnds = None

Hi,
As @NTU-P04922004  suggested, indeed in test mode the landmarks network should not be called. I have pushed a fix.


1.27.0: netlify host with tracker script name environment variable

Since v1.27.0, my custom tracker script name is not available on Netlify but still works on Heroku.
Its the same repository with the same environments variables.

Without env variable, everything work well with umami.js file (which always seems to be accessible, even with the environment variable).
https://portfolio-unami.herokuapp.com/statistics.js
https://unami.duboiss.fr/statistics.js
I think its related to #731  & #977

I'm not that familiar with Netlify, but I'm guessing it can't run the new Next.js middleware, which is how the tracker script name is handled. We may need to come up with a static solution for Netlify.

No schema changes were made.

I have the same issue as this but on Heroku! Not sure what could be causing it.

I did a few prints to try and debug as well. I set the env variable to "something_cool".
Modified function:

Netlify logs:

And when running locally with npm run dev

But when I check the network logs on the netlify build, it looks like it tries to get the umami.js properly. But somehow returns 404 instead of 200.
I wonder if the href of the url object needs to be updated as well? I'll test it out.

I opened an issue w/ netlify, but I have a feeling it is something with dev vs prod in next... as the netlify cli runs fine.
https://github.com/netlify/netlify-plugin-nextjs/issues/1266


Designated initializers restrictions in Xcode 11.4

Hi!
We did a rollback to version 2.0.1 because after migration to Xcode 11.4 the initializers we had access before are not available and doesn't allow us to subclass EasyTipView with the changes added in the last 2.0.4.
This is because a new restriction in Xcode 11.4 as you can see in the release notes:
https://developer.apple.com/documentation/xcode_release_notes/xcode_11_4_release_notes

Convenience initializer inheritance for subclasses defined outside the module that defines the base class now comes with additional restrictions. When these subclasses have a base class with non-public designated initializers, they no longer automatically inherit convenience initializers from their superclasses. To restore this automatic inheritance behavior, the base class must ensure that all of its designated initializers are public or open. (51249311)

Is there any chance to get back subclassing again?
Thanks.

Please check  version 2.1.0  🚀

Please check  version 2.1.0  🚀


Async to promises. writeGltf, writeBinaryGltf, writeFile -- callbacks -> Promises

Not ready for review.
I am currently switching some files to be Promises instead of using callbacks, but I've hit a few snags which have resulted in me doing some anti-patterns that I wanted to ask a few questions about to resolve.
I'll be adding inline comments so it is easier to see what I am talking about.

@JoshuaStorm This branch should be clean again

I'm seeing errors in Travis, but this is clean locally for me

Ignore the most recent commit, it was off-base
I'll look more into this

I have resolved the Travis failure that occurred due to attempting to write to a directory without the directory first being made.
However, this solution is a bit hacky:
I want to use both synchronous and asynchronous fs-extra functions. As such, I cannot just promisifyAll of fs-extra since that results in an error being thrown when a synchronous function is called.
A simple solution would be just to require('fs-extra) and promisify the individual functions I want to use as promises, but this causes an issue where I cannot spy on the individual function (there may be a simple resolution to this that I am unaware of)
For example, if I do
var fsExtra = require('fs-extra');
var outputJson = Promise.promisify(fsExtra.outputJson);

and attempt to do spyOn(fsExtra, 'outputJson'), the spy does not seem to be triggered by calling the promisified outputJson
My current solution is a bit clunky, and inefficient: I use both var fsExtra = require('fs-extra') and var fsPromise = Promise.promisifyAll(require('fs-extra')) so I can use the synchronous and asynchronous functions, while also being able to spyOn(fsPromise, 'outputJson')

@JoshuaStorm do the following:
fsExtra.outputJsonAsync = Promise.promisify(fsExtra.outputJson);
...
spyOn(fsExtra, 'outputJsonAsync')

I knew I had to be forgetting something straight forward like that.
Thanks!

This should be good for review now!

Async tests should use
expect(promise, done).toResolve();

https://github.com/AnalyticalGraphicsInc/agi-cesium-people/tree/node-coding-guide/NodeCodingGuide#testing-differences-from-cesium

@lasalvavida Good catch, I forgot about that.
Just to make sure I do these properly:
This
        writeGltf(gltf, options)
            .then(function() {
                expect(gltf.shaders.CesiumTexturedBoxTest0FS.extras).not.toBeDefined();
                expect(gltf.shaders.CesiumTexturedBoxTest0FS.uri).toEqual('CesiumTexturedBoxTest0FS.glsl');
                return fsReadFile(outputFragmentShaderPath);
            })
            .then(function(outputData) {
                expect(bufferEqual(outputData, fragmentShaderData)).toBe(true);
                done();
            });

should become
        var promise = writeGltf(gltf, options)
            .then(function() {
                expect(gltf.shaders.CesiumTexturedBoxTest0FS.extras).not.toBeDefined();
                expect(gltf.shaders.CesiumTexturedBoxTest0FS.uri).toEqual('CesiumTexturedBoxTest0FS.glsl');
                return fsReadFile(outputFragmentShaderPath);
            })
            .then(function(outputData) {
                expect(bufferEqual(outputData, fragmentShaderData)).toBe(true);
                done();
            });
        expect(promise, done).toResolve();

Right?
Thanks!

Make sure you don't call done like in your example.
I would also write it a little more compactly, like this:
expect(writeGltf(gltf, options)
    .then(function() {
        expect(gltf.shaders.CesiumTexturedBoxTest0FS.extras).not.toBeDefined();
        expect(gltf.shaders.CesiumTexturedBoxTest0FS.uri).toEqual('CesiumTexturedBoxTest0FS.glsl');
        return fsReadFile(outputFragmentShaderPath);
    })
    .then(function(outputData) {
        expect(bufferEqual(outputData, fragmentShaderData)).toBe(true);
    }), done).toResolve();

I think bin/gltf-pipeline.js may need updating since processFileToDisk is a promise now.

If node already waits for all promises to terminate, it may be as simple as putting a comment that says that so there's no confusion.

Those are my last few comments; this looks awesome @JoshuaStorm!

@lilleyse This does change the public API; do we want to merge this now or wait until after the first alpha release?

@lilleyse This does change the public API; do we want to merge this now or wait until after the first alpha release?

I was thinking about this too. It's probably best to wait.
I have another question though. Should our public API return promises at all, or should those functions take callbacks? Internally the callback would just wrap around the promises. It seems like callbacks are still the standard for most other node libraries. @mramato do you have thoughts on this?

Our public API should absolutely return promises.  There are two ways to go here:

Return promises and not provide callbacks at all. (The ideal solution)
Support both, which is what I've seen other libraries do.  Basically, any public function that normally returns a promise would take an optional callback function as it's final argument.  Passing in the callback will cause it to act like a traditional callback function and not return a promise.  We could easily write a single promiseToCallback utility function that handles this for us and we would have to call it wherever we return a promise from the public API.

While 2 wouldn't be a ton of code, it does add some additional overhead and clutter the API a bit.  We would also have to add an extra test for every public API function to cover it.  My gut says to go with 1 until enough people ask for 2.  It would be a non-breaking change to add later.
@pjcozzi What do you think?

My gut says to go with 1 until enough people ask for 2

Big +1

Thanks @lasalvavida and @JoshuaStorm


[gardening] Standardize include guard in SILSuccessor.h

2nd to last gardening commit from vacation.

@swift-ci Please smoke test and merge

@shahmishal I triggered the smoke test an hour or two ago... whats going on?

@swift-ci Please smoke test and merge

@swift-ci Please test and merge

@gottesmm Fixed, network issue.


Multicluster setup (n > 2)

change the Makefile targets so that they run in a for loop
add tests for terratest for round-robin @ 3 clusters (failover is still pending)
change the helm chart to be able to set up more than one hostAlias entry for a pod
add simple script that generates the yaml configs for k3d clusters so that we are DRY

to verify the change locally i suggest:
# deploy 5 clusters
make deploy-full-local-setup CLUSTERS_NUMBER=5

# do some testing
for i in {0..20} ; do make test-round-robin | grep mess ; done

# cleanup
make destroy-full-local-setup CLUSTERS_NUMBER=5

another consequence of this PR is that when trying to incorporate a change in local helm chart (that hasn't been published yet), one can do make deploy-full-local-setup CHART=./chart/k8gb
Signed-off-by: Jirka Kremser<EMAIL_ADDRESS>

please consider native iterators (see example):

I know about it, but I wanted to avoid 'dynamic targets' or pattern rules, or what is it called to make it simple. I like the way how you combine two strings together and then allow for "random access" in it so I've borrowed that for the geo tags to have it as one-liner (space separated) instead of those 10 lines and 10 different variables

We probably should fail fast in make terratest target if CLUSTER_NUMBER !=3 with a clear message that tests are expecting 3 clusters to avoid confusion in future.

it's there

Thanks for reviews!
terrascan & CodeQL checks are being stucked, but these were passing before, so merging..


Fixed NDMS for latest firmware.

Fixed NDMS for latest firmware.
Now using telnet instead of Web Interface
Description:
Since latest Keenetic firmware totally changed the UI and introduced cookie-based authorization old code does not work anymore. The updated solution switched to telnet since it's expected to be more stable in terms of interface.
Pull request in home-assistant.github.io with documentation (if applicable): home-assistant/home-assistant.github.io#5813
Checklist:

[x] The code change is tested and works locally.
[x] Local tests pass with tox. Your PR cannot be merged unless tests pass

If user exposed functionality or configuration variables are added/changed:

[x] Documentation added/updated in home-assistant.github.io

If the code communicates with devices, web services, or third-party tools:

[x] New dependencies have been added to the REQUIREMENTS variable (example).
[x] New dependencies are only imported inside functions that use them (example).
[x] New or updated dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[ ] New files were added to .coveragerc.

If the code does not interact with devices:

[ ] Tests have been added to verify that the new code works.

@MartinHjelmare, I don't think it should be the case when we just fix an integration.
Do we want a refactoring session here?
BTW, the pypi package that has only one call also looks useless for me.

I don't think we should accept any (big) changes to this module until it has been refactored to use a standalone interface library. After that we can take further changes.

@MartinHjelmare , updated.

I'm adding breaking change label due to the change of interface to telnet.

@foxel please open a new PR for the docs. Your earlier PR was merged too soon by mistake and later reverted. Sorry about the inconvenience.
Ping me when that is done and you've added a link to that PR in the description of this PR. Then I'll merge.

@MartinHjelmare the new docs PR is 5933


As a home bakery owner, I want to be able to add tasks associated with each supplier, such as ordering ingredients,

... so that I can keep track of my to-do list.

#20


DAC-292 Delete single test campaign

https://input-output.atlassian.net/browse/DAC-292
Imp: To be merged in only after PR #44

It's very hard to review it since in the comparison window there is a tone of code already reviewed from other PRs.
In order to highlight the real changes, the target branch can be changed (at least temporarily) as its base PR

@bogdan-manole PR #44  is merged, and this should be review-able now


Allow for controlling quote style when exporting to YAML

Is your feature request related to a problem? Please describe.
This builds on the conversation in 1368.
When using CUE to export to YAML, there are times when controlling the quote style is required. In this playground example, the wildcard entry is always export wrapped in single quotes ('*.exmaple.com'). In our use case, there are downstream tools which require double quotes ("*.example.com").
Describe the solution you'd like
Allow some way to control quote style. In 1368 there were some discussions about controlling this at the file level, but even some sort of field-level controls would would in our case.
Describe alternatives you've considered
As far as I'm aware, there are no ways to control this using CUE itself. There are some recommendations in Slack to implement some sort of post processing: find and replace on magic strings, use another format.
Additional context
N/A

In our use case, there are downstream tools which require double quotes ("*.example.com").

Can you please expand on this a bit? If there's a program that takes in YAML, are you saying that it only accepts double quotes and not single quotes? I don't think I've heard of partial YAML support like that before.
In #1368, Marcel also suggests eporting as JSON - it always double quotes strings, and YAML is a superset of JSON, so presumably that could be enough to satisfy another program which only knows how to consume double-quoted YAML strings.

@mvdan yeah, in our case the tool downstream is setup with a linter to only allow a specific sub-set of YAML.
To be clear: I don't think CUE is doing anything "wrong", but I suspect there will continue to be edge cases as long as there's no control over quote style. #2720 is another example where the fix was editing a specific regex within CUE to enforce quotes.
In our case we followed Marcel's advice and changed our tooling to export JSON, so we have a workaround for now.

I am having the same issue. My use case is a regex that OpenTelemetry interprets different when the quotes are removed from the regex used in https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/fc363988211d90ee2ae7c75eda6ce90c04bae868/processor/redactionprocessor/config.go#L25

In our case we followed Marcel's advice and changed our tooling to export JSON, so we have a workaround for now.

I would suggest this as the better approach for naive consumers/parsers on the other side which don't actually know how to parse YAML correctly. JSON is a much simpler syntax, so it fits that use case better, and it is a valid subset of YAML so it shouldn't break any valid YAML parsers either.


Fix getPortfolio function in Binance

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

Bugfix

What is the current behavior? (You can also link to an open issue here)

getPortfolio always returns 0 due to an incorrect use of _.first(...)

What is the new behavior (if this is a feature change)?

Function now returns the 'free' balance, replaced _.first with _.find.

Other information:

Should fix issue #1356

Hey @cmroche, it now throws the following;
TypeError: Cannot read property 'free' of undefined
at Trader.setBalance (/root/gekko/exchanges/binance.js:127:7)
at bound (/root/gekko/node_modules/lodash/dist/lodash.js:729:21)
at Request.request [as _callback] (/root/gekko/node_modules/binance/lib/rest.js:61:21)
at Request.self.callback (/root/gekko/node_modules/request/request.js:188:22)
at emitTwo (events.js:125:13)
at Request.emit (events.js:213:7)
at Request. (/root/gekko/node_modules/request/request.js:1171:10)
at emitOne (events.js:115:13)
at Request.emit (events.js:210:7)
at IncomingMessage. (/root/gekko/node_modules/request/request.js:1091:12)
Thanks for your quick response on the last issue!

@ms121 Fixing bindings, try now please.

Seems to be working ill let it run and see how it goes!
I changed line 181 to; var result = _.first(data, function(ticker) {
and err.message was returning
'TypeError: Cannot read property 'message' of null
at Trader.setTicker (/root/gekko/exchanges/binance.js:192:18)
at bound (/root/gekko/node_modules/lodash/dist/lodash.js:729:21)
at Request.request [as _callback] (/root/gekko/node_modules/binance/lib/rest.js:61:21)
at Request.self.callback (/root/gekko/node_modules/request/request.js:188:22)
at emitTwo (events.js:125:13)
at Request.emit (events.js:213:7)
at Request. (/root/gekko/node_modules/request/request.js:1171:10)
at emitOne (events.js:115:13)
at Request.emit (events.js:210:7)
at IncomingMessage. (/root/gekko/node_modules/request/request.js:1091:12)'
Fixed it by changing it to just err.

@ms121 Thanks for your help :) Same problem with getPortfolio, I used the wrong function... the update I just pushed should fix it. Thanks again.

@cmroche
As the bot tried to buy the following happened;
2017-12-03` 03:24:38 (INFO):	Attempting to BUY 1.1992578439197714 NEO at binance price: 0.077
2017-12-03 03:24:38 (DEBUG):	[binance.js] (addOrder) BUY 1.1992578439197714 NEO @ 0.077 ETH
2017-12-03 03:24:38 (DEBUG):	[binance.js] entering "getTicker" callback after api call, err: { code: -1102,
msg: 'Mandatory parameter 'timestamp' was not sent, was empty/null, or malformed.' }  data: { code: -1102,
msg: 'Mandatory parameter 'timestamp' was not sent, was empty/null, or malformed.' }
2017-12-03 03:24:38 (ERROR):	[binance.js] unable to buy { code: -1102,
msg: 'Mandatory parameter 'timestamp' was not sent, was empty/null, or malformed.' }
/root/gekko/exchanges/binance.js:35
if (!error || !error.message.match(recoverableErrors)) {
^
TypeError: Cannot read property 'match' of undefined
at Trader.retry (/root/gekko/exchanges/binance.js:35:32)
at Trader.bound [as retry] (/root/gekko/node_modules/lodash/dist/lodash.js:729:21)
at Trader.setOrder (/root/gekko/exchanges/binance.js:232:19)
at bound (/root/gekko/node_modules/lodash/dist/lodash.js:729:21)
at Request.request [as _callback] (/root/gekko/node_modules/binance/lib/rest.js:52:21)
at Request.self.callback (/root/gekko/node_modules/request/request.js:188:22)
at emitTwo (events.js:125:13)
at Request.emit (events.js:213:7)
at Request. (/root/gekko/node_modules/request/request.js:1171:10)
at emitOne (events.js:115:13)

@ms121 The binance node module normally automatically adds the timestamp to any authenticated queries, but look at the source it doesn't in the case of addOrder. Probably a bug on their side, but the fix is as simple as adding it to the query parameters so I've pushed a fix for it.
Also the comments said "getTicker" but actually that was a copy and paste error on my side, it was actually "addOrder" that was triggering it :)
Thank again, and let me know how it goes. I think we're pretty close now thanks to your help.

Thanks again @cmroche next error is the following; Going to double check it isn't because my trade is too small, although it might be to do with how many decimal places we are sending to binance.
2017-12-04 01:00:08 (DEBUG):	[binance.js] entering "setOrder" callback after api call, err: { code: -1013, msg: 'Filter failure: LOT_SIZE' }  data: { code: -1013, msg: 'Filter failure: LOT_SIZE' }
2017-12-04 01:00:08 (ERROR):	[binance.js] unable to buy { code: -1013, msg: 'Filter failure: LOT_SIZE' }

@ms121 It's because the min order was wrong, the info wasn't readily available at the time I put this together but found it now. THe markets have been cleaned up, and the min orders fixed.

Tested still throwing the same error;
2017-12-04 01:55:41 (INFO):	Attempting to BUY 59.90620811174061 POWR at binance price: 0.00154501
2017-12-04 01:55:41 (DEBUG):	[binance.js] (addOrder) BUY 59.90620811174061 POWR @ 0.00154501 ETH
2017-12-04 01:55:42 (DEBUG):	[binance.js] entering "setOrder" callback after api call, err: { code: -1013, msg: 'Filter failure: LOT_SIZE' }  data: { code: -1013, msg: 'Filter failure: LOT_SIZE' }
2017-12-04 01:55:42 (ERROR):	[binance.js] unable to buy { code: -1013, msg: 'Filter failure: LOT_SIZE' }

@cmroche @ms121

[binance.js] entering "setOrder" callback after api call, err: { code: -1013, msg: 'Filter failure: LOT_SIZE' } data: { code: -1013, msg: 'Filter failure: LOT_SIZE' }
2017-12-04 01:55:42 (ERROR):	[binance.js] unable to buy { code: -1013, msg: 'Filter failure: LOT_SIZE' }

LOT_SIZE errors in binance have to do with the rounding of either the amount of the volume, which is different per market. In binance there are 2 checks for minimal orders:

is the amount above the minimum (for some small coins it needs be 1+)?
is the total amount (rate * amount) above another minimum (I think: 0.001 for BTC pairs and 0.01 for ETH pairs)?

After that the amount and the rate are checked for rounding: the amount and the rate both need to be rounded according to some rounding, else you get this error. I am pretty sure this is not handled by the lib we are using.

@askmike All of the currency pairs specific use 8 decimals places for input, are you saying that Gekko will attempt to use more decimal places than that? If so I can push a fix tonight.

@ms121 @askmike After a bit of research on this issue, it looks like Binance uses minOrder as the precision for the asset, and tickSize as the precision for the currency. I've added a rounding function for both of these now, hopefully that addresses the issue.

Thanks again @cmroche, problem now is the Price is being calculated the same as the amount by the looks of it;
2017-12-05 01:09:47 (DEBUG):	[binance.js] (addOrder) BUY 60 POWR @ 60 ETH
2017-12-05 01:09:48 (DEBUG):	[binance.js] entering "setOrder" callback after api call, err: { code: -2010,
msg: 'Account has insufficient balance for requested action.' }  data: { code: -2010,
msg: 'Account has insufficient balance for requested action.' }
2017-12-05 01:09:48 (ERROR):	[binance.js] unable to buy { code: -2010,
msg: 'Account has insufficient balance for requested action.' }

Ooof :S That was a nasty copy and paste error, I'm glad it didn't work.
Fixed now.

HAHA I thought so as well!

@askmike The build errors are related to using an older npm version, I don't think I can fix this on my side.

No problem, I'll work on upgrading dependencies. I'll merge this for now and if more problems arise we can address them in new PRs. Thanks a lot @cmroche!

@cmroche after 10 hours of running (bought a sold 5 times no problems) it decided to throw this out;
2017-12-06 02:02:12 (DEBUG): [binance.js] entering "setOrder" callback after api call, err: { code: -1013, msg: 'Filter failure: MIN_NOTIONAL' }  data: { code: -1013, msg: 'Filter failure: MIN_NOTIONAL' }
It was trying to use under 1 BNB to ETH.
Looking at line 492 It looks to be correctly set to 1 not sure why it decided to try and buy.

Did it terminate the process, or continue?
Either way, if it continued to buy, then there is probably a bug in the Binance API... unless the buy you saw was not related, and perhaps there are rounding errors bringing it just slightly under the minimal amount? I could throw a Math.max in there and see if it fixes it, would be a bit of a guess though unless you could catch the error and print out the amount it is trying to request.

Ended up terminating the process. It might have actually been a rounding issue. I believe it might have round up thinking it was over 1 but was in fact just under.

Refer to PR #1427 now please.


unable to change date format

In the file 'single.html' of a theme layout directory, the file format was changed:
{{ .Date.Format "Mon, 2 Jan 2006" }}
The blog posts show dates incorrect format mm-dd-yy, the correct format is dd-mm-yy
How to change please?

Please use https://discourse.gohugo.io/ for questions/troubleshooting. Also see  Hugo Documentation.


Make GIF for readme

write a justfile
list recipes
run a recipe

Thoughts on gif vs something like asciinema?

asciinema would be great, although I'm not sure it can be embedded in playable form in a readme. I've seen asciinema videos linked from readmes, but you have to click on them and go to another page to play them. It's might be possible to convert an asciinema to a gif though.


Adding 2022-03-01 version for Microsoft.Capacity with new changes

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Changelog
Add a changelog entry for this PR by answering the following questions:

What's the purpose of the update?

[ ] new service onboarding
[x] new API version
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month.
When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.
If updating an existing version, please select the specific language SDKs and CLIs that must be refreshed after the swagger is published.

[x] SDK of .NET (need service team to ensure code readiness)
[x] SDK of Python
[ ] SDK of Java
[ ] SDK of Js
[ ] SDK of Go
[x] PowerShell
[x] CLI
[ ] Terraform
[ ] No refresh required for updates in this PR

Contribution checklist:

[x] I commit to follow the Breaking Change Policy of "no breaking changes"
[x] I have reviewed the documentation for the workflow.
[x] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

Applicability: :warning:
If your changes encompass only the following scenarios, you should SKIP this section, as these scenarios do not require ARM review.

Change to data plane APIs
Adding new properties
All removals

Otherwise your PR may be subject to ARM review requirements. Complete the following:

[x] Check this box if any of the following apply to the PR so that label "WaitForARMFeedback" will be added automatically to begin ARM API Review. Failure to comply may result in delays to the manifest.

Adding a new service
Adding new API(s)
Adding a new API version
-[ ] To review changes efficiently, ensure you are using OpenAPIHub to initialize the PR for adding a new version. More details, refer to the wiki.

[x] Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If any of the following scenarios apply to the PR, request approval from the Breaking Change Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in a stable version
[ ] Removing properties in a stable version
[ ] Removing API version(s) in a stable version
[ ] Updating API in a stable or public preview version with Breaking Change Validation errors
[ ] Updating API(s) in public preview over 1 year (refer to Retirement of Previews)

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.

@gaoyp830 - Your PR isn't ready for ARM review yet.
For new API versions, you need to make your PR with a base commit of the unchanged files from the current API version copied to the new API version folder. Then apply your changes for the new API version (including changing the version in the files) in subsequent commits. This allows reviewers to see exactly what is changing from the current API to the new one in your PR.
You can also use OpenAPIHub: it will build the PR correctly for you automatically.

@gaoyp830 - Your PR isn't ready for ARM review yet.
For new API versions, you need to make your PR with a base commit of the unchanged files from the current API version copied to the new API version folder. Then apply your changes for the new API version (including changing the version in the files) in subsequent commits. This allows reviewers to see exactly what is changing from the current API to the new one in your PR.
You can also use OpenAPIHub: it will build the PR correctly for you automatically.

Closing this one and opened a new PR to add new properties to existing api version https://github.com/Azure/azure-rest-api-specs/pull/18247


Chipmunk2 d

Can you help me to merge the conflicts (overwriting is ok)

I will try the merge (learning Github ;))


Fix #4260 : Allow trailing arguments that accept void to be omitted

Fixes #4260

@typescript-bot test this

@jack-williams FYI I expect the test run from the bot to fail so don't get worried if it comes back red

No worries! Thanks for picking it up

@jack-williams I don't find that example super compelling given that it potentially requires multiple iterations of reasoning, e.g.
type MaybeVoid = T extends void ? void : object;
declare function foo<T = void>(x: T, y: MaybeVoid<T>);
foo();

Tags: void parameters void-typed parameters optional


Use GCM sink if SINK=gcm is specified.

Default is influxdb which mirrors today's behavior.
Fixes #117.

Tested on a new cluster and it comes up as expected.

I think its time to rewrite run.sh in golang. May be after this PR.

+1, this logic can probably live in the Heapster binary itself. We don't need a wrapper per say.

LGTM except for the one nit. If we are moving to a dynamic configuration model, we can get rid of this logic completely.

@vmarmol: Feel free to self merge after fixing the nit.

Thanks @vishh! Will merge on green.


how to print PDF width pdfjs-dist

Attach (recommended) or Link to PDF file here:
Configuration:

Web browser and its version:
Operating system and its version:
PDF.js version:
Is a browser extension:

Steps to reproduce the problem:

cant find any doc about print

What is the expected behavior? (add screenshot)
What went wrong? (add screenshot)
Link to a viewer (if hosted on a site other than mozilla.github.io/pdf.js or as Firefox/Chrome extension):

Duplicate of #10307; please note in particular https://github.com/mozilla/pdf.js/issues/10307#issuecomment-442254159.


Parser fails to recognise error identifier

Describe the bug
Parser fails to recognise error identifier.
To Reproduce
solang-parser = "=0.2.2"
let content = r#"
contract Contract {
    function test() internal {
        bytes memory error = bytes("");
        if (error.length > 0) {}
    }
}
"#;
solang_parser::parse(content, 0).expect("can parse");

Expected behavior
Parser successfully recognizes error identifier.
Screenshots

Include the complete solidity source code
Please include all the Solidity source so we can reproduce the issue.
contract Contract {
  function test() internal {
    bytes memory error = bytes("");
    if (error.length > 0) {}
  }
}

Additional Context
https://github.com/foundry-rs/foundry/issues/4403

Yes, this is a problem. error is a keyword in other contexts so this is causing problems. The grammar will need fixing, this will be a tough one. :disappointed:


[mesheryctl] Add command to register dynamic k8s components.

See mesheryctl Command Tracker for current status of commands.
Current Behavior

Desired Behavior

Please refer to issue for additional details.
Add support for mesheryctl accordingly.
Implementation

Acceptance Tests

Mockups

Contributor Resources

⌨ mesheryctl Contributing Guide
Beginner's guide to contributing to Meshery and mesheryctl
mesheryctl Command Tracker
Meshery CLI Commands and Documentation
🙋🏾🙋🏼 Questions: Layer5 Discussion Forum and Layer5 Community Slack

Hi, @MUzairS15 I would like to work on this issue! But would have many doubts to ask .. as this would be my first DevOps issue, Can I start?


Reorganize and clean up core/ directory

Removed FuncRef, since Callable makes it obsolete
Removed int_types.h as its obsolete in c++11+
Changed color names code

The new file structure looks like this.

Thanks!


Preprocessing datasets

Hello,
I'm unclear on the pretraining procedures, in particular the preprocessing of the datasets.
Unless I'm mistaken https://github.com/mlpen/Nystromformer/blob/main/data-preprocessing/preprocess_data_512.py suggest we just put segments of size 512. I'm not sure I understand how SOP is defined in this case? Actually SOP doesn't seem to be used at all in the pretrain script.

@thomasw21, the preprocessing of the datasets is to segment the sequence into sequences with a fixed number of tokens. The preprocessed datasets have been put in the docker. You do not have to redo it on your own. @mlpen did not add the sentence order prediction (SOP) part in preprocess_data_512.py. He will include it when he is available.

We reorganized the code implementation for experiments. The data processing code for BERT (MLM and SOP) is on https://github.com/mlpen/Nystromformer/blob/main/reorganized_code/BERT/dataset.py

Thank you ! I'll take a look when I get the chance. I'll close this issue and re-open another one if I have more questions.


Perpetual jitter/contact clip bouncing with angular velocity

Minimal reproduction
I think there might be some scheduling weirdness with the default rapier3d setup, it seems that angular velocity is being applied to rotation after contact resolution for that frame, or maybe i misunderstand how render updates vs physics updates are being run. the behavior i am observing is that
Setup
A dynamic convex hull resembling a ball is a few units above a flat static floor. A dynamic cone is a few units above the hull, a bit off-center. Gravity will pull both objects down towards the floor.
Expected behavior
There is an initial linear impact of the hull against the floor. The hull is perfectly balanced on its tip. The cone falls and hits the hull off-axis. The hull topples as it gains angular velocity. Another side of the hull hits the floor and does not visibly clip into the floor because contact resolution is complete before the frame is rendered. Some of the hull's energy is lost in the process. Eventually both the hull and the cone lose all energy and stop moving, and get marked asleep.
Observed behavior
Initial linear impact behaves correctly. The hull topples over as the cone hits it off-axis and gains angular velocity. The hull momentarily clips into the floor and renders that way for at least a frame before bouncing back out and correcting, with as much or more energy as before. The hull gets stuck in an infinite micro-angular-bouncing loop and jitters perpetually. Neither the cone nor the hull get marked asleep.
No combination or Restitution/Friction/Dampening or erp value adjustments seems to fix this.

This repro could be even simpler by spawning the hull with an initial angular velocity and getting rid of the cone setup.
The behavior is also easier to observe with an orthographic camera.

The linked reproduction no longer reachable, is it still an issue ?

I changed my username, the url is now https://gist.github.com/atlv24/1c524f734cc109946f12a4294a2f5b5e


Pandas-ta multiprocessing not working

Which version are you running? The lastest version is on Github. Pip is for major releases.
import pandas_ta as ta
print(ta.version)

0.2.28b0

Upgrade.
$ pip install -U git+https://github.com/twopirllc/pandas-ta

Describe the bug
The following line is not using any multiprocessing. Instead the whole calculation takes place on a single core although the message output says that it is using 128 CPUs. Please see the screen snapshot showing that this is clearly not happening. I couldn't get it to use all of my CPUs.
inputs.ta.strategy(exclude=["tema", "t3", "supertrend", "natr", "percent_return", "ichimoku", "ppo", "roc", "dpo", "vwma", "wma", "zlma", "hilo", "nvi","qqe", "pvi" , "qstick", "squeeze", "ttm_trend","rvgi", "log_return", "psar", "pvt", "cdl_doji", "cdl_inside", "bop", "adosc", "cksp", "decay", "kc", "hl2", "hlc3", "ha", "donchian", "accbands", "massi"], verbose=True, timed=True)
To Reproduce
import pandas_ta as ta

def talib_new(input_ds,symbol_list,window_size):

    critical_columns_index=len(input_ds.columns) # do not remove these initial set of columns since they contain pricing information

    for symboll in symbol_list:

        print(symboll)

        print('Adding columns for subsymbol ',symboll)
        inputs = pd.DataFrame()

        inputs['open'] = input_ds[f'OpenPrice{str("_")+symboll}'].astype(float)
        inputs['high'] = input_ds[f'OpenPrice{str("_")+symboll}'].astype(float)
        inputs['low'] = input_ds[f'OpenPrice{str("_")+symboll}'].astype(float)
        inputs['close'] = input_ds[f'OpenPrice{str("_")+symboll}'].astype(float)
        inputs['volume'] = input_ds[f'OpenPrice{str("_")+symboll}'].astype(float)

        inputs.ta.mp = True

        inputs.ta.strategy(exclude=["tema", "t3", "supertrend", "natr", "percent_return", "ichimoku", "ppo", "roc", "dpo", "vwma", "wma", "zlma", "hilo", "nvi","qqe", "pvi" , "qstick", "squeeze", "ttm_trend","rvgi", "log_return", "psar", "pvt", "cdl_doji", "cdl_inside", "bop", "adosc", "cksp", "decay", "kc", "hl2", "hlc3", "ha", "donchian", "accbands", "massi"], verbose=True, timed=True)

        smoothing_features = ['MIDPRICE_2', 'DEMA_10', 'EMA_10', 'FWMA_10', 'HMA_10', 'KAMA_10_2_30', "WCP"]

        for name in smoothing_features:
            inputs[name] = (inputs[name]-inputs['close'])/inputs['close']*100

        #inputs['AD'] = inputs['AD'].pct_change(periods=window_size)
        inputs['OBV'] = inputs['OBV'].pct_change(periods=window_size)
        inputs['LOGRET'] = inputs.ta.log_return()
        inputs['PCTRET'] = inputs.ta.percent_return()
        inputs['ROC'] = inputs.ta.roc()
        inputs['NATR'] = inputs.ta.natr()
        inputs = inputs.drop(columns = ['open', 'high', 'low', 'volume', 'close', 'AR_26', 'AD','OBV_min_2', 'OBV_max_2', 'OBV_EMA_4', 'OBV_EMA_12', 'ABER_ZG_5_15', 'ABER_SG_5_15', 'ABER_XG_5_15', 'BBL_5_2.0', 'BBM_5_2.0', 'BBU_5_2.0'])

        for i in inputs.columns:

            input_ds[i+f'{str("_")+symboll}'] = inputs[i]

        input_ds=input_ds.drop(columns = [f'OpenPrice{str("_")+symboll}',f'HighPrice{str("_")+symboll}',f'LowPrice{str("_")+symboll}',f'ClosePrice{str("_")+symboll}',f'TotalVolume{str("_")+symboll}'], axis=1)

    input_ds.dropna(inplace=True)

    return input_ds

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.
Thanks for using Pandas TA!

Hello @myilmazhaubtech,

The following line is not using any multiprocessing. Instead the whole calculation takes place on a single core although the message output says that it is using 128 CPUs. Please see the screen snapshot showing that this is clearly not happening. I couldn't get it to use all of my CPUs.

That is weird. I do not know why it is not utilizing all the CPUs available despite what Pandas TA says. With your hardware and software specs found at scikit-learn Issue, hopefully someone else has encountered an Issue with Python not utilizing all the core on Ubuntu.
First, I would check out the following Linux Python Multiprocessing Issue and see if that may resolve the Issue. I would also continue trying other solutions listed from the following Google Search that are Linux specific and try it out. Unfortunately, I do not have a high powered Linux machine to test with so you will need to help out and give me details.
Should the provided Linux specific solutions, from the links above, not work nor improve performance, I will look into it. At that point I will need your assistance to test development code, with you testing on your system.
Unfortunately, I do not have an expected time frame on resolving this Issue as I am backlogged on outstanding Issues and package enhancements. However, this can be expedited with your help as I can not do this alone nor do I have a similar machine to test on. Your assistance would be greatly appreciated.
Kind Regards,
KJ

Hello @myilmazhaubtech,

The following line is not using any multiprocessing. Instead the whole calculation takes place on a single core although the message output says that it is using 128 CPUs. Please see the screen snapshot showing that this is clearly not happening. I couldn't get it to use all of my CPUs.

That is weird. I do not know why it is not utilizing all the CPUs available despite what Pandas TA says. With your hardware and software specs found at scikit-learn Issue, hopefully someone else has encountered an Issue with Python not utilizing all the core on Ubuntu.
First, I would check out the following Linux Python Multiprocessing Issue and see if that may resolve the Issue. I would also continue trying other solutions listed from the following Google Search that are Linux specific and try it out. Unfortunately, I do not have a high powered Linux machine to test with so you will need to help out and give me details.
Should the provided Linux specific solutions, from the links above, not work nor improve performance, I will look into it. At that point I will need your assistance to test development code, with you testing on your system.
Unfortunately, I do not have an expected time frame on resolving this Issue as I am backlogged on outstanding Issues and package enhancements. However, this can be expedited with your help as I can not do this alone nor do I have a similar machine to test on. Your assistance would be greatly appreciated.
Kind Regards,
KJ

meet the same problem...

@Qiu-INJ,
I can not help you with such a minimal description of your issue.
So what version of Pandas TA are you running? Where is your reproducible code and applicable screenshots? What time of system are you running on? Have you tried code from the links in the prior comment?
Kind Regards, KJ

Sorry!!! my fault!
pandas ta: 0.3.14b0
system: ubuntu 18.04
code :
TestStrategy = ta.Strategy(
    name = "test",
    ta = [
        {'kind':'td_seq'}
    ]
)
data.ta.strategy(TestStrategy, cores=0, timed=True)

data.tail()
![2021-10-14 21-57-13 的屏幕截图](https://user-images.githubusercontent.com/85727393/137332168-bd85ed0b-e5ce-4c1a-bd60-11aea0910f6a.png)


Add Python 3.8 to Travis

@KevinHock would you also be interested in a PR removing 2.7?
https://devguide.python.org/#status-of-python-branches

Yes we would be very interested @gliptak 😀
One of us made a PR to detect-secrets-server for this, but we haven't yet done it for detect-secrets 👍


unable to enable ssl

I am unable to enable https.
proxy.yml
version: "3"

services:

  proxy:
    image: vfarcic/docker-flow-proxy
    ports:
      - 80:80
      - 443:443
      - 8080:8080
    networks:
      - proxy
    environment:
      - LISTENER_ADDRESS=swarm-listener
      - MODE=swarm
      - DEFAULT_PORTS=80,443:ssl
      - DEBUG=true
    deploy:
      replicas: 2

  swarm-listener:
    image: vfarcic/docker-flow-swarm-listener
    networks:
      - proxy
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
    environment:
      - DF_NOTIFY_CREATE_SERVICE_URL=http://proxy:8080/v1/docker-flow-proxy/reconfigure
      - DF_NOTIFY_REMOVE_SERVICE_URL=http://proxy:8080/v1/docker-flow-proxy/remove
    deploy:
      placement:
        constraints: [node.role == manager]

networks:
  proxy:
    external: true

I have attempted 2 different approaches. Creating my own image
First approach
Dockerfile
FROM vfarcic/docker-flow-proxy
COPY my-host1.pem /certs/my-host1.pem
COPY my-host2.pem /certs/my-host2.pem

Second approach
docker secret create cert-my-host1.pem my-host1.pem
docker service update --secret-add cert-my-host1.pem proxy_proxy
docker service inspect proxy_proxy # confirmed the secret was added to the service

In both cases my config does not include a 'crt' entry @ /v1/docker-flow-proxy/config
 frontend services bind *:80 bind *:443 mode http acl

Attempting to test via openssl
openssl s_client -debug -connect mysite.com:443                                                                                1 master!?
CONNECTED(00000003)
write to 0x7fef40416ee0 [0x7fef4080c600] (130 bytes => 130 (0x82))
0000 - 80 80 01 03 01 00 57 00-00 00 20 00 00 39 00 00   ......W... ..9..
0010 - 38 00 00 35 00 00 16 00-00 13 00 00 0a 07 00 c0   8..5............
0020 - 00 00 33 00 00 32 00 00-2f 00 00 9a 00 00 99 00   ..3..2../.......
0030 - 00 96 03 00 80 00 00 05-00 00 04 01 00 80 00 00   ................
0040 - 15 00 00 12 00 00 09 06-00 40 00 00 14 00 00 11<EMAIL_ADDRESS>0050 - 00 00 08 00 00 06 04 00-80 00 00 03 02 00 80 00   ................
0060 - 00 ff 75 5c cc b5 7b d5-b3 03 63 5b a7 b9 75 0e   ..u\..{...c[..u.
0070 - 63 64 d9 be 8f d5 b6 b0-ec ff 28 a4 da af 57 33   cd........(...W3
0080 - 38 1a                                             8.
read from 0x7fef40416ee0 [0x7fef40811c00] (7 bytes => 7 (0x7))
0000 - 48 54 54 50 2f 31 2e                              HTTP/1.
36418:error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol:/BuildRoot/Library/Caches/com.apple.xbs/Sources/OpenSSL098/OpenSSL098-59.60.1/src/ssl/s23_clnt.c:618:

resolved...image appeared to be out-of-date


Use one global context for TileDB

This prevents from creating a large number of contexts which have to be cleaned up and might cause thread contention if a large number of notebooks are opened.

Uses sparse array until TileDB-Cloud-Py is linked against TileDB 2.1.2


Ignore unofficial subclasses

This fixes #801 for me. I am still not quite sure what the intention is but having the two places use similar handling seems reasonable. The change has been in Home Assistant for a couple of months with no reported issues.
While at it, I have added handling of unofficial # subclasses (in addition to .#), originally implemented in https://github.com/swehog/pysonos/commit/6f78223d8d292d3179ba69eb4d0fd64906018506. This has also been in Home Assistant for a long time.

Coverage increased (+0.01%) to 54.346% when pulling 837bb19e075aa63f7ff17a31a5b227d35cf0a3b3 on amelchio:unofficial-upnp-class into 43c2d50018012933c3545de3590abdc9905c7784 on SoCo:master.

LGTM -- thanks.

Cherry-picked to v0.22.fixes.


Exclude verify from workspace

The verify crate is a dev tool and should not have been included in the workspace because it has no lock file requirements.
Exclude verify from the workspace and update the lock files.

We can do this, but FYI if you remove stuff from the workspace I will never test it again because it's effectively invisible to me.

hmm, I'll put some thought into whether we want to actually run verify in CI or whether it being invisible is ok.

Gotta run, if this goes red don't waist your time on in @apoelstra I'll come back.


Feature/sdk additional functions

I added several functions to rAPId SDK and created relevant test function:

create_user
delete_user
list_subjects
list_layers
list_protected_domains
delete_dataset

I compiled and tested sdk package locally. I didn't find any issues.

Now functions I added handle all error I was able to notice. However, there are some issues with errors/codes returned by API.
in remove_dataset - function returns status code 202 when dataset doesn't exists, but layer is correct
in create_user - function returns status code 400 for two types of error


We don't need DeclareUnicodeCharacter when compiling with XeTeX

Here's the first of a couple of changes I made to let the Vakidioot class compile under XeTeX, the others mostly concern font loading and are in the vakidioot.cls file.

Thanks!


Gradle error while building with whitelisted self signed certificates

I'm trying to build a Nativescript application while whitelisting self-signed certificates for android.
It use to work I'm pretty sure, but now I'm getting the following Gradle error :
`Platform android successfully added. v3.4.2
Support for Node.js 12.22.6 is not verified. NativeScript CLI might not install or run properly.
Executing before-prepare hook from /home1/local/jenkins/workspace/myApp/hooks/before-prepare/nativescript-dev-typescript.js
Found peer TypeScript 2.6.2
Preparing project...
Successfully prepared plugin nativescript-angular for android.
Successfully prepared plugin nativescript-audio for android.
Successfully prepared plugin nativescript-barcodescanner for android.
Successfully prepared plugin nativescript-couchbase for android.
Successfully prepared plugin nativescript-ripple for android.
Successfully prepared plugin nativescript-sqlite for android.
Successfully prepared plugin nativescript-theme-core for android.
Successfully prepared plugin nativescript-toast for android.
Successfully prepared plugin nativescript-toolbox for android.
Successfully prepared plugin nativescript-ui-sidedrawer for android.
nativescript-vibrate 5.2.0 for android is not compatible with the currently installed framework version 3.4.2.
Successfully prepared plugin nativescript-vibrate for android.
Successfully prepared plugin tns-core-modules for android.
Successfully prepared plugin nativescript-intl for android.
Successfully prepared plugin nativescript-permissions for android.
Successfully prepared plugin nativescript-ui-core for android.
Successfully prepared plugin tns-core-modules-widgets for android.
Project successfully prepared (android)
Building project...
Gradle build...
+ applying user-defined configuration from /home1/local/jenkins/workspace/myApp/app/App_Resources/Android/app.gradle
Applying settings from /home1/local/jenkins/workspace/myApp/app/App_Resources/Android/settings.json
+ creating include.gradle for plugin /home1/local/jenkins/workspace/myApp/platforms/node_modules/nativescript-audio
+ creating include.gradle for plugin /home1/local/jenkins/workspace/myApp/platforms/node_modules/nativescript-barcodescanner
+ add include.gradle from /home1/local/jenkins/workspace/myApp/node_modules/nativescript-couchbase/platforms/android/include.gradle
+ add include.gradle from /home1/local/jenkins/workspace/myApp/node_modules/nativescript-ripple/platforms/android/include.gradle
+ add include.gradle from /home1/local/jenkins/workspace/myApp/node_modules/nativescript-vibrate/platforms/android/include.gradle
+ creating include.gradle for plugin /home1/local/jenkins/workspace/myApp/platforms/node_modules/nativescript-ui-core
+ applying plugin configuration from /home1/local/jenkins/workspace/myApp/platforms/android/app/build/configurations/nativescript-audio/include.gradle
+ applying plugin configuration from /home1/local/jenkins/workspace/myApp/platforms/android/app/build/configurations/nativescript-barcodescanner/include.gradle
+ applying plugin configuration from /home1/local/jenkins/workspace/myApp/platforms/android/app/build/configurations/nativescript-couchbase/include.gradle
+ applying plugin configuration from /home1/local/jenkins/workspace/myApp/platforms/android/app/build/configurations/nativescript-ripple/include.gradle
+ applying plugin configuration from /home1/local/jenkins/workspace/myApp/platforms/android/app/build/configurations/nativescript-vibrate/include.gradle
+ applying plugin configuration from /home1/local/jenkins/workspace/myApp/platforms/android/app/build/configurations/nativescript-ui-core/include.gradle
+ adding nativescript runtime package dependency: nativescript-optimized
+ adding aar plugin dependency: /home1/local/jenkins/workspace/myApp/node_modules/nativescript-audio/platforms/android/nativescript_audio.aar
+ adding aar plugin dependency: /home1/local/jenkins/workspace/myApp/node_modules/nativescript-barcodescanner/platforms/android/barcodescanner-release-2.1.6.aar
+ adding aar plugin dependency: /home1/local/jenkins/workspace/myApp/node_modules/nativescript-ui-sidedrawer/platforms/android/TNSSideDrawer-release.aar
+ adding aar plugin dependency: /home1/local/jenkins/workspace/myApp/node_modules/nativescript-vibrate/platforms/android/nativescript_vibrate.aar
+ adding aar plugin dependency: /home1/local/jenkins/workspace/myApp/node_modules/nativescript-ui-core/platforms/android/TNSCore-release.aar
+ adding aar plugin dependency: /home1/local/jenkins/workspace/myApp/node_modules/tns-core-modules-widgets/platforms/android/widgets-release.aar
false
/home1/local/jenkins/workspace/myApp/platforms/android/app/src/main/res/xml/network_security_config.xml:5:32-53: AAPT: No resource found that matches the given name (at 'src' with value '@raw/digicert_egs.pem').
/home1/local/jenkins/workspace/myApp/platforms/android/app/src/main/res/xml/network_security_config.xml:6:32-50: AAPT: No resource found that matches the given name (at 'src' with value '@raw/a7848a7ee.pem').
/home1/local/jenkins/workspace/myApp/platforms/android/app/build/intermediates/res/merged/F0F1F2F3F4F5/debug/xml/network_security_config.xml:5: error: Error: No resource found that matches the given name (at 'src' with value '@raw/digicert_egs.pem').
/home1/local/jenkins/workspace/myApp/platforms/android/app/build/intermediates/res/merged/F0F1F2F3F4F5/debug/xml/network_security_config.xml:6: error: Error: No resource found that matches the given name (at 'src' with value '@raw/a7848a7ee.pem').
FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':app:processF0F1F2F3F4F5DebugResources'.

com.android.ide.common.process.ProcessException: Failed to execute aapt`

nativescript version : 3.4.2
node version : 12.7.7
my network_security_config.xml file (in myApp/app/App_Resources/Android/res/xml/..) :
<?xml version="1.0" encoding="utf-8"?> <network-security-config>     <base-config>         <trust-anchors>             <certificates<EMAIL_ADDRESS>           <certificates<EMAIL_ADDRESS>           <certificates src="system"/>         </trust-anchors>     </base-config> </network-security-config>
with my two certificates inside myApp/app/App_Resources/Android/res/raw/..
and I updated AndroidManifest.xml with application tag attribute : android:networkSecurityConfig="@xml/network_security_config"
Did something changed or are my paths uncorrect ? (I tried other paths without success, either I get error for the certificates or for my network_security_config.xml file)

It seems the files are not being copied, is it possible to try using an newer version of nativescript ?

Upgrade to a newer version of {N} to fix this issue


Failed to connect to the server... Seems like you are using the custom OpenAI provider...

Describe the bug
After install when I go to the url http://localhost:3000/ I get two errors:
"Failed to connect to the server. Please try again later."
and
"Seems like you are using the custom OpenAI provider, please open the settings and configure the API key and base URL"
To Reproduce
Steps to reproduce the behavior: go to the url http://localhost:3000/

Go to the url http://localhost:3000/

Expected behavior
I expected perplexica screen to load.
Screenshots

Additional context
Ollama is not installed in docker but is running and working http://<IP_ADDRESS>:11434/
Searxng is running in docker and is running and working http://<IP_ADDRESS>:32768/
I am running on ubuntu PopOS

Please follow: https://github.com/ItzCrazyKns/Perplexica?tab=readme-ov-file#ollama-connection-errors

Thank for the response.
I have previously tried your suggestions from reading similar issues here.
Linux: Use http://<private_ip_of_host>:11434
Inside /etc/systemd/system/ollama.service, added Environment="OLLAMA_HOST=<IP_ADDRESS>"
I know the port isnt blocked since Im using open-webui in docker and it connects to ollama on http://<IP_ADDRESS>:11434

Please remove the / from the end of the URL. If that doesn't work can you show the output of sending a curl request at the same URL.

Removing the slash didnt work. Here is the result of the curl request:
`$ curl -i http://<IP_ADDRESS>:11434
HTTP/1.1 200 OK
Content-Type: text/plain; charset=utf-8
Date: Sun, 17 Nov 2024 14:05:47 GMT
Content-Length: 17
Ollama is running(base)`

Did you pressed the blue save button after removing the / from the URL?

Yes, I did save it.

Had similar issue, but on windows. Hope this helps.

 Had similar issue, but on windows. After changing the"Chat Model provider" it worked. Hope this helps.

Thank you for the response. However, I have no options for chat model provider, only the default.

@digitalenterprises I have the same issue, did you manage to fix this?

No unfortunately I am still unable to get it working. Please let me know if you come up with something.

@digitalenterprises I have the same issue, did you manage to fix this?

No unfortunately I am still unable to get it working. Please let me know if you come up with something.

will do

same issue.

I ran into the same issue. Using the Docker installation on a MacBook M1 Pro. I'm running Ollama natively on my MacBook. Once I updated the Ollama address in the configuration file, I was about to set my Chat Model Provider to Ollama, resolving the error. Looks like it may be a two step configuration process if doing this through the UI since I had to configure the Ollama URL, Save, then go back in and change the chat model. Hope this helps.


grpc-sys 0.4.2 fails to build - but 0.4.1 builds fine

Describe the bug
0.4.2 fails to build for us with CentOS 7.
To Reproduce
On CentOS 7 run cargo build against a crate which depends on either grpc-sys 0.4.2, or grpc-sys 0.4.1
With grpc-sys 0.4.2, the following is seen:
error: failed to run custom build command for `grpcio-sys v0.4.2`
process didn't exit successfully: `/target/debug/build/grpcio-sys-840781b2e44e9c86/build-script-build` (exit code: 101)
--- stdout
cargo:rerun-if-changed=grpc_wrap.cc
cargo:rerun-if-changed=grpc
cargo:rerun-if-env-changed=GRPCIO_SYS_USE_PKG_CONFIG
cargo:rerun-if-env-changed=CARGO_CFG_TARGET_OS
running: "cmake" "/opt/rust/registry/src/github.com-1ecc6299db9ec823/grpcio-sys-0.4.2/grpc" "-DGO_EXECUTABLE=fake-go-nonexist" "-DgRPC_INSTALL=false" "-DgRPC_BUILD_CSHARP_EXT=false" "-DgRPC_BUILD_CODEGEN=false" "-DCMAKE_INSTALL_PREFIX=.../target/debug/build/grpcio-sys-f45f9c164b4a8726/out" "-DCMAKE_C_FLAGS= -ffunction-sections -fdata-sections -fPIC -m64" "-DCMAKE_C_COMPILER=/usr/local/bin/cc" "-DCMAKE_CXX_FLAGS= -ffunction-sections -fdata-sections -fPIC -m64" "-DCMAKE_CXX_COMPILER=/usr/bin/c++" "-DCMAKE_BUILD_TYPE=Debug"
-- The C compiler identification is GNU 4.8.5
-- The CXX compiler identification is GNU 4.8.5
-- Check for working C compiler: /usr/local/bin/cc
-- Check for working C compiler: /usr/local/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Looking for sys/types.h
-- Looking for sys/types.h - found
-- Looking for stdint.h
-- Looking for stdint.h - found
-- Looking for stddef.h
-- Looking for stddef.h - found
-- Check size of off64_t
-- Check size of off64_t - done
-- Looking for fseeko
-- Looking for fseeko - found
-- Looking for unistd.h
-- Looking for unistd.h - found
-- Renaming
--     /opt/rust/registry/src/github.com-1ecc6299db9ec823/grpcio-sys-0.4.2/grpc/third_party/zlib/zconf.h
-- to 'zconf.h.included' because this file is included with zlib
-- but CMake generates it automatically in the build directory.
-- Looking for res_servicename in resolv
-- Looking for res_servicename in resolv - not found
-- Looking for gethostbyname in nsl
-- Looking for gethostbyname in nsl - found
-- Looking for gethostbyname in socket
-- Looking for gethostbyname in socket - not found
-- Looking for clock_gettime in rt
-- Looking for clock_gettime in rt - found
-- Looking for include file sys/socket.h
-- Looking for include file sys/socket.h - found
-- Looking for include file arpa/inet.h
-- Looking for include file arpa/inet.h - found
-- Looking for include file arpa/nameser_compat.h
-- Looking for include file arpa/nameser_compat.h - found
-- Looking for include file arpa/nameser.h
-- Looking for include file arpa/nameser.h - found
-- Looking for include file assert.h
-- Looking for include file assert.h - found
-- Looking for include file errno.h
-- Looking for include file errno.h - found
-- Looking for include file fcntl.h
-- Looking for include file fcntl.h - found
-- Looking for include file inttypes.h
-- Looking for include file inttypes.h - found
-- Looking for include file limits.h
-- Looking for include file limits.h - found
-- Looking for include file malloc.h
-- Looking for include file malloc.h - found
-- Looking for include file memory.h
-- Looking for include file memory.h - found
-- Looking for include file netdb.h
-- Looking for include file netdb.h - found
-- Looking for include file netinet/in.h
-- Looking for include file netinet/in.h - found
-- Looking for include file netinet/tcp.h
-- Looking for include file netinet/tcp.h - found
-- Looking for include file net/if.h
-- Looking for include file net/if.h - found
-- Looking for include file signal.h
-- Looking for include file signal.h - found
-- Looking for include file socket.h
-- Looking for include file socket.h - not found
-- Looking for include file stdbool.h
-- Looking for include file stdbool.h - found
-- Looking for include file stdlib.h
-- Looking for include file stdlib.h - found
-- Looking for include file strings.h
-- Looking for include file strings.h - found
-- Looking for include file string.h
-- Looking for include file string.h - found
-- Looking for include file stropts.h
-- Looking for include file stropts.h - not found
-- Looking for include file sys/ioctl.h
-- Looking for include file sys/ioctl.h - found
-- Looking for include file sys/param.h
-- Looking for include file sys/param.h - found
-- Looking for include file sys/select.h
-- Looking for include file sys/select.h - found
-- Looking for include file sys/stat.h
-- Looking for include file sys/stat.h - found
-- Looking for include file sys/time.h
-- Looking for include file sys/time.h - found
-- Looking for include file sys/uio.h
-- Looking for include file sys/uio.h - found
-- Looking for include file time.h
-- Looking for include file time.h - found
-- Looking for include file dlfcn.h
-- Looking for include file dlfcn.h - found
-- Looking for include file unistd.h
-- Looking for include file unistd.h - found
-- Looking for include files winsock2.h, windows.h
-- Looking for include files winsock2.h, windows.h - not found
-- Looking for 3 include files winsock2.h, ..., windows.h
-- Looking for 3 include files winsock2.h, ..., windows.h - not found
-- Looking for include files winsock.h, windows.h
-- Looking for include files winsock.h, windows.h - not found
-- Looking for include file windows.h
-- Looking for include file windows.h - not found
-- Performing Test HAVE_SOCKLEN_T
-- Performing Test HAVE_SOCKLEN_T - Success
-- Performing Test HAVE_TYPE_SOCKET
-- Performing Test HAVE_TYPE_SOCKET - Failed
-- Performing Test HAVE_BOOL_T
-- Performing Test HAVE_BOOL_T - Success
-- Performing Test HAVE_SSIZE_T
-- Performing Test HAVE_SSIZE_T - Success
-- Performing Test HAVE_LONGLONG
-- Performing Test HAVE_LONGLONG - Success
-- Performing Test HAVE_SIG_ATOMIC_T
-- Performing Test HAVE_SIG_ATOMIC_T - Success
-- Performing Test HAVE_STRUCT_ADDRINFO
-- Performing Test HAVE_STRUCT_ADDRINFO - Success
-- Performing Test HAVE_STRUCT_IN6_ADDR
-- Performing Test HAVE_STRUCT_IN6_ADDR - Success
-- Performing Test HAVE_STRUCT_SOCKADDR_IN6
-- Performing Test HAVE_STRUCT_SOCKADDR_IN6 - Success
-- Performing Test HAVE_STRUCT_SOCKADDR_STORAGE
-- Performing Test HAVE_STRUCT_SOCKADDR_STORAGE - Success
-- Performing Test HAVE_STRUCT_TIMEVAL
-- Performing Test HAVE_STRUCT_TIMEVAL - Success
-- Looking for AF_INET6
-- Looking for AF_INET6 - found
-- Looking for O_NONBLOCK
-- Looking for O_NONBLOCK - found
-- Looking for FIONBIO
-- Looking for FIONBIO - found
-- Looking for SIOCGIFADDR
-- Looking for SIOCGIFADDR - found
-- Looking for MSG_NOSIGNAL
-- Looking for MSG_NOSIGNAL - found
-- Looking for PF_INET6
-- Looking for PF_INET6 - found
-- Looking for SO_NONBLOCK
-- Looking for SO_NONBLOCK - not found
-- Looking for CLOCK_MONOTONIC
-- Looking for CLOCK_MONOTONIC - found
-- Performing Test HAVE_SOCKADDR_IN6_SIN6_SCOPE_ID
-- Performing Test HAVE_SOCKADDR_IN6_SIN6_SCOPE_ID - Success
-- Performing Test HAVE_LL
-- Performing Test HAVE_LL - Success
-- Looking for bitncmp
-- Looking for bitncmp - not found
-- Looking for closesocket
-- Looking for closesocket - not found
-- Looking for CloseSocket
-- Looking for CloseSocket - not found
-- Looking for connect
-- Looking for connect - found
-- Looking for fcntl
-- Looking for fcntl - found
-- Looking for freeaddrinfo
-- Looking for freeaddrinfo - found
-- Looking for getaddrinfo
-- Looking for getaddrinfo - found
-- Looking for getenv
-- Looking for getenv - found
-- Looking for gethostbyaddr
-- Looking for gethostbyaddr - found
-- Looking for gethostbyname
-- Looking for gethostbyname - found
-- Looking for gethostname
-- Looking for gethostname - found
-- Looking for getnameinfo
-- Looking for getnameinfo - found
-- Looking for getservbyport_r
-- Looking for getservbyport_r - found
-- Looking for gettimeofday
-- Looking for gettimeofday - found
-- Looking for if_indextoname
-- Looking for if_indextoname - found
-- Looking for inet_net_pton
-- Looking for inet_net_pton - not found
-- Looking for inet_ntop
-- Looking for inet_ntop - found
-- Looking for inet_pton
-- Looking for inet_pton - found
-- Looking for ioctl
-- Looking for ioctl - found
-- Looking for ioctlsocket
-- Looking for ioctlsocket - not found
-- Looking for IoctlSocket
-- Looking for IoctlSocket - not found
-- Looking for recv
-- Looking for recv - found
-- Looking for recvfrom
-- Looking for recvfrom - found
-- Looking for send
-- Looking for send - found
-- Looking for setsockopt
-- Looking for setsockopt - found
-- Looking for socket
-- Looking for socket - found
-- Looking for strcasecmp
-- Looking for strcasecmp - found
-- Looking for strcmpi
-- Looking for strcmpi - not found
-- Looking for strdup
-- Looking for strdup - found
-- Looking for stricmp
-- Looking for stricmp - not found
-- Looking for strncasecmp
-- Looking for strncasecmp - found
-- Looking for strncmpi
-- Looking for strncmpi - not found
-- Looking for strnicmp
-- Looking for strnicmp - not found
-- Looking for writev
-- Looking for writev - found
-- Found Perl: /usr/bin/perl (found version "5.16.3")
-- The ASM compiler identification is GNU
-- Found assembler: /usr/local/bin/cc
-- Configuring done
-- Generating done
-- Build files have been written to: .../target/debug/build/grpcio-sys-f45f9c164b4a8726/out/build

--- stderr
CMake Warning at cmake/protobuf.cmake:48 (message):
  gRPC_PROTOBUF_PROVIDER is "module" but PROTOBUF_ROOT_DIR is wrong
Call Stack (most recent call first):
  CMakeLists.txt:140 (include)

CMake Warning at cmake/gflags.cmake:26 (message):
  gRPC_GFLAGS_PROVIDER is "module" but GFLAGS_ROOT_DIR is wrong
Call Stack (most recent call first):
  CMakeLists.txt:142 (include)

CMake Warning at cmake/benchmark.cmake:26 (message):
  gRPC_BENCHMARK_PROVIDER is "module" but BENCHMARK_ROOT_DIR is wrong
Call Stack (most recent call first):
  CMakeLists.txt:143 (include)

CMake Error at CMakeLists.txt:738 (target_compile_options):
  Error evaluating generator expression:

    $<COMPILE_LANGUAGE:CXX>

  Expression did not evaluate to a known generator expression

CMake Error at CMakeLists.txt:6171 (target_compile_options):
  Error evaluating generator expression:

    $<COMPILE_LANGUAGE:CXX>

  Expression did not evaluate to a known generator expression
....
thread 'main' panicked at '
command did not execute successfully, got: exit code: 1

build script failed, must exit now', /opt/rust/registry/src/github.com-1ecc6299db9ec823/cmake-0.1.35/src/lib.rs:778:5
note: Run with `RUST_BACKTRACE=1` for a backtrace.

warning: build failed, waiting for other jobs to finish...
error: failed to verify package tarball

Caused by:
  build failed

Expected behavior
grpc-sys to build successfully.
System information

CPU architecture: x86-64
Distribution and kernel version: CentOS 7 under Docker on Core OS.
SELinux on?:
Any other system details we should know?:

Additional context
Add any other context about the problem here.

Find same error message in docker image.
Docker image: rust:latest
cmake version (install by apt-get install cmake in Docker container): 3.13.4
binutils version: 2.31.1-16
Do I miss anything need to install?
Thank you

You missed the reproduction instruction

I make a new issue with more information I got:
https://github.com/pingcap/grpc-rs/issues/364

You are welcome


Issue #74 Remove future pregnancy concerns from recommendation

Update ManageRareAbnormality I1, I2.2 and I6 to generate separate recommendation text when patient > 50 years. This removed the text regarding future pregnancy concerns and fertility sparing management options.

This PR resolves Issue #74.


Add withResolution to <Layout>

Layout components are not wrapped with the withResolution HOC and they should be, that will make Reflex behavior more consistent.
Most Layout properties should also handle the object format. Once implemented, update https://github.com/obartra/reflex/wiki/Layout

Also include innerRef. Basically the APIs should match as much as possible


build(lint): start using cspell for grammar in code

Utilsing cSpell to prevent common spelling mistakes in code.
This is implemented as part of the npm lint script, which gets executed both
on a commit and during the CI pipeline. Parameters for this are defined in .cspell.json
Resolve #321

@travis-payne Looks like this CI failure is legit (at a quick glance) it claims there are 4 more cspell errors.

@travis-payne Squash and rebase please


Update .travis.yml

It's not necessary to drop 0.4 at this point, as METADATA hasn't been frozen for 0.4-enabled packages.

Coverage remained the same at 100.0% when pulling 86a45f1f2598058dca91960a6dcf9f900b9b4faf on musm:patch-2 into d7e294131823c3723148d745497b0f8b028ded91 on JuliaLang:master.

Coverage remained the same at 100.0% when pulling 86a45f1f2598058dca91960a6dcf9f900b9b4faf on musm:patch-2 into d7e294131823c3723148d745497b0f8b028ded91 on JuliaLang:master.

Coverage remained the same at 100.0% when pulling 86a45f1f2598058dca91960a6dcf9f900b9b4faf on musm:patch-2 into d7e294131823c3723148d745497b0f8b028ded91 on JuliaLang:master.

Coverage remained the same at 100.0% when pulling 86a45f1f2598058dca91960a6dcf9f900b9b4faf on musm:patch-2 into d7e294131823c3723148d745497b0f8b028ded91 on JuliaLang:master.

Coverage remained the same at 100.0% when pulling 86a45f1f2598058dca91960a6dcf9f900b9b4faf on musm:patch-2 into d7e294131823c3723148d745497b0f8b028ded91 on JuliaLang:master.

fxd

G2g? Or did I miss something


Docker compose installation failing

Steps To Reproduce
Following the instructions from https://docs.counterparty.io/docs/basics/getting-started/.
git clone https://github.com/CounterpartyXCP/counterparty-core.git
cd counterparty-core
mkdir ~/.local/share/counterparty-docker-data
docker-compose up -d

Then in the middle of the process, getting this:
57d7718a02a0: Pull complete
Digest: sha256:cbd15da7e8945070fb2fd0b012391139cb869716eb44c2de9238a73d6983db64
Status: Downloaded newer image for counterparty/counterparty:v10.1.0
Creating counterparty-core_bitcoind_1 ... error

ERROR: for counterparty-core_bitcoind_1  Cannot start service bitcoind: error while mounting volume '/var/lib/docker/volumes/counterparty-core_data/_data': failed to mount local volume: mount /root/counterparty-core/${XDG_DATA_HOME:-~/.local/share}/counterparty-docker-data:/var/lib/docker/volumes/counterparty-core_data/_data, flags: 0x1000: no such file or directory

ERROR: for bitcoind  Cannot start service bitcoind: error while mounting volume '/var/lib/docker/volumes/counterparty-core_data/_data': failed to mount local volume: mount /root/counterparty-core/${XDG_DATA_HOME:-~/.local/share}/counterparty-docker-data:/var/lib/docker/volumes/counterparty-core_data/_data, flags: 0x1000: no such file or directory
ERROR: Encountered errors while bringing up the project.

What version did you initially run in Docker? This looks like it was from a pre-release version, when the directories weren't stable.

I'll try a new server... will follow up soon.

It looks like there was a previous installation of a pre-release version of v10.1.0. Can you remove all of /var/docker and try again?

Getting weird errors now:
docker-compose up -d

Creating network "counterparty-core_default" with the default driver
ERROR: failed to update bridge store for object type *bridge.networkConfiguration: open /var/lib/docker/network/files/local-kv.db: no such file or directory

Got this, then reinstalled docker-compose just in case the deleting of all those files messed it up, but still getting the same error.

Is this on the fresh server? It looks like there's an issue with your installation of Docker. You should rm -rf /var/docker I think.

Same exact error from a fresh server.

Hm, looks like a potential incompatibility between the OS and the Docker Compose file. What OS are you running and what's the output of $ mount?

I've already tried all of those. I see there is a new v10.1.1 release, anything here that could have fixed the issue?
FYI, my server ran the v10.0 docker-compose installation just fine. Have you been able to run this installation with the most recent versions?

@jotapea nothing in v10.1.1 would fix it, and I'm pretty sure that v10.1.0 is the same as v10.0.0 vis à vis Docker.
We run everything in Docker Compose as part of our continuous integration to make sure this always works (see https://github.com/CounterpartyXCP/counterparty-core/actions/workflows/test_compose.yml).
It looks to me like there's a problem with some directory not existing in your installs (because of user configuration or something), and Docker is failing to create the necessary mounts because of it.

I wanted to make sure that you ran them in that order.  Sounds like you already have.

My v10.0.0-rc1 node is at commit 005dad64, with a docker-compose.yml with the following last line:
device: ${COUNTERPARTY_DOCKER_DATA:-~/counterparty-docker-data}/

Which is different from the current. Then, my node also has this ~/counterparty-docker-data folder.
Replicating these over the current master fixes this issue, but now https://github.com/CounterpartyXCP/counterparty-core/issues/1722 happens.

@jotapea, going to close this out given that it seems updating the docker compose file to latest solved the volume mount issue for you.  Feel free to re-open if this assumption is incorrect.

The latest docker compose didn't work for me, what worked was reverting it.

I just did a clean install on a fresh VM without issues.
This error message doesn't look right to me:
 failed to mount local volume: mount /root/counterparty-core/${XDG_DATA_HOME:-~/.local/share}/counterparty-docker-data:/var/lib/docker/volumes/counterparty-core_data/_data, flags: 0x1000: no such file or directory
I would expect to see the actual path there, rather than the unevaluated expression.  What version of docker are you using?

To that end, could you try running docker compose instead of docker-compose

I was using sudo apt install docker-compose as it was documented previously. But let me try it with the following instructions instead https://docs.docker.com/desktop/install/ubuntu/...

Got it working with this Docker installation:
https://docs.docker.com/engine/install/ubuntu/#install-using-the-convenience-script
Thank you @mattmarcello for the follow ups! Closing.

Nice.  It's a good catch because I think our docs still reference docker-compose.

Yes they do (at least indirectly).


Food Scraps And Walkie playing audio globally

Hey, I noticed that the food scrap items in your Food Scraps And Walkie Lethal Company mod have global audio. Meaning if someone picks up or drops one of the food scrap items everyone can hear the sounds for anywhere in the map.
To fix this, in the AudioSource for each food scrap item, you need to set the Spatial Blend to 1, set the AudioRolloffMode to either Linear or Custom, and set the Min/Max distance. If you have a decompiled version of Lethal Company as a Unity project you could reference one of the vanilla scraps AudioSource. You could also reference the values of the walkie AudioSource since that one seems to work as intended.

@hoffor I'm saying that your food scrap items have global audio since the Spatial Blend and Volume Rolloff is set incorrectly on the AudioSources.
While I was on the ship, I had a crewmate pick up and drop the Bread, Burger, Cake, Coffee, and Cookie scrap items while they were inside the facility and I could hear the sounds of those items being picked up and dropped.
 This should not be happening!

[!NOTE] The Cursed Walkie scrap item works perfectly fine.

To fix this issue:
For each of your food scrap items, on the AudioSource component, you need to set Spatial Blend to 1 and Volume Rolloff to Linear Rolloff. Then you need to set the Min Distance and Max Distance.

I decompiled your mods' AssetBundle to a Unity project and checked the properties of each scrap item.

Vanilla item for reference


added pricing for Lucidchart

verbal pricing for Lucidchart from inside sales; 107/year per seat.

This one was fun to look into. It looks like the current pricing for a single user seat in the Teams plan (non-individual) is $9 per u/m. At $107 per u/y for SSO, that would be $8.91, so you save 9 cents?

Clobbering with #198


Add tags for lobbies

I want lobbies to have an array of tags which can be used to filter them. Currently we have flags like locked and passworded but I'd want more customised options.

One of the things that would be useful is the ability to filter by ranked/unranked matches. So having such a tag would allow this. Currently this information is not sent to Chobby for non participants.


VS Code GitHub Codespaces extension 'get codespace request failed with status 401'

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.65.2
OS Version: OS X 10.13.6

Steps to Reproduce:

While logged into github codespaces, under 'your codespaces' select 3 dot menu near codespace, 'open in Visual Studio Code'
2.Visual Studio opens and attempts to connect to codespace, resulting in the following error. Was previously working until this morning.

[ProtocolHandler I] Connecting to codespace mmtrent-code50-10188961-p7jw5q5gh769g
[Command:Connect I] Decorator starting: ErrorNotification
[Command:Connect I] Decorator starting: Telemetry
[API:retries-left-2 I] making GET request for "https://api.github.com/user/codespaces/mmtrent-code50-10188961-p7jw5q5gh769g"
[API:retries-left-2 E] getCodespace error. Correlation ID: C0A9:2F76:547D3:5A0A5:6230DDE9
[API:retries-left-1 I] making GET request for "https://api.github.com/user/codespaces/mmtrent-code50-10188961-p7jw5q5gh769g?internal=true&refresh=true"
[API:retries-left-1 E] getCodespace error. Correlation ID: C0AD:5A3E:B0D17:B79AD:6230DDEA
[API:retries-left-0 I] making GET request for "https://api.github.com/user/codespaces/mmtrent-code50-10188961-p7jw5q5gh769g?internal=true&refresh=true?internal=true&refresh=true"
[API:retries-left-0 E] getCodespace error. Correlation ID: C0AF:6844:BA147:C0B70:6230DDEA
[Command:Connect E] Command [Connect to Codespace]: Connect to Codespace Failure: get codespace request failed with status 401 (1199ms)

In this case though I believe this should be reported to Codespace team and then we see if it ends up here again.


Invalid tasks in the kafka ansible playbook and invalid region specified

The first two tasks in the ansible playbook https://github.com/confluentinc/openmessaging-benchmark/blob/master/driver-kafka/deploy/deploy.yaml appear to be invalid
Namely the - name: Collect profiles and the  - name: Heap allocation profile are both invalid since they seem to refer to files in /tmp. Not exactly sure where these files come from.
In addition, the region specified on line 70 in https://github.com/confluentinc/openmessaging-benchmark/blob/master/driver-kafka/deploy/provision-kafka-aws.tf needs to be changed to us-west-2a as 2b is not supported per the CLI output.

The profile tasks are to be run post-deployment. We don't have any use for that for the purpose of running the benchmark. You could skip those tasks by excluding those tags
# Note: We are using the terraform inventory here to populate the inventory list from Terraform
TF_STATE=. ansible-playbook -vv deploy.yaml --inventory `which terraform-inventory` --user 'ec2-user' --skip-tags 'profile'

In addition, the region specified on line 70 in https://github.com/confluentinc/openmessaging-benchmark/blob/master/driver-kafka/deploy/provision-kafka-aws.tf needs to be changed to us-west-2a as 2b is not supported per the CLI output.

We have not had any issues in provisioning the setup in us-west-2b. What is the error from the CLI output specifically?

Thanks for the prompt feedback. Yes you are right - us-west-2b does not result an error for me anymore. May have been an account specific issue wrt limits.


[Suggestion] Inverted-color icons

[x] I'm sure this issue is not a duplicate.

This is specifically about the Crystal icon, although I think it extends to all black/almost-black icons.
The Crystal icon is literally impossible to see on High Contrast (my preferred theme, due to a visual impairment). It would be nice if there was a way to invert the color of an icon (or if there was a light version of the Crystal icon)
In the meantime, how would I go about changing the icon for dark themes only? The wiki is a bit impenetrable :(
Screenshot:

This seems like a bug to me.
cc @JimiC

Indeed I should have made a dark version icon. As soon as find some time I'll provide one.
Regarding the API you have a point. We haven't documented the supported object  properly. We'll see about adjusting that.

Thanks @JimiC @jens1o :)


Fix documentation for create/perist.

create/persist do not assign the id to the entity passed as parameter.
Instead they return a copy of the entity with id assigned.

:+1:

:+1:


Addon dont load on new geyser versions

The plugin does not work with the new versions of geyser (the new great update that added the 1.17 in geyser) to be more specific to the version: 1.4.0-Snapshot(1.17.0 bedrock, Java 1.17), It does not detect the floodgate plugin name that is written as Floodgate-Spigot in the new update

This project does support the latest Floodgate version under the Floodgate 2.0 branch. Sometime soon I will publish a new release, but for now it is possible to compile to support it.

Resolved.


[SUPPORT] Allow re-inviting user without assigning to org/space

What
When re-inviting a user (eg because they've forgotten their password),
we don't need to specify an org because they'll already be assigned to
the orgs/spaces then need access to. In this case it's desirable to not
touch the orgs/spaces.
This therefore allows this script to run without an org specified when
re-inviting a user.
How to review
Test that the script works against a dev environment (the --no-email flag is useful here) for the following:

Creating a user assigned to an org
Re-inviting a user without an org specified

Who can review
Not me.

Closing because this breaks when it comes to email the user. The email template includes the org at present.

I've addressed the issue with the email template. I've additionally modified the behaviour when --no-email is specified so that the email contents are printed, which makes testing easier.

Used and works 👍