map issue

I seem to be getting this strange error once I try to run map in sim or direclty as a command:
bey@ubuntu:~/zenbot$ zenbot map --backfill
09/07/2016 03:36:25 PM EDT [    launcher] cmd `map` booting
/home/bey/zenbot/utils/get_products.js:6
      if (c.assets.indexOf(product.asset) === -1) return false
                  ^

TypeError: Cannot read property 'indexOf' of undefined
    at /home/bey/zenbot/utils/get_products.js:6:19
    at Array.filter (native)
    at get_products (/home/bey/zenbot/utils/get_products.js:5:23)
    at mapper (/home/bey/zenbot/plugins/gdax/backfiller.js:12:20)
    at /home/bey/zenbot/node_modules/run-parallel/index.js:41:7
    at Array.forEach (native)
    at module.exports (/home/bey/zenbot/node_modules/run-parallel/index.js:40:11)
    at mapper (/home/bey/zenbot/node_modules/zenbrain/core/mapper/mapper.js:9:5)
    at Object.<anonymous> (/home/bey/zenbot/node_modules/zenbrain/core/launcher/launcher.js:76:11)
    at Immediate._onImmediate (/home/bey/zenbot/node_modules/sosa/api.js:15:12)

I looked around and there are no open or closed issues related to this.
Does anybody know whats going on here?

I had this issue, you have to specify the configuration file with the flag
--config
A qua, 7/09/2016, 20:37, Beyondem<EMAIL_ADDRESS>escreveu:

I seem to be getting this strange error once I try to run map in sim or
direclty as a command:
bey@ubuntu:~/zenbot$ zenbot map --backfill
09/07/2016 03:36:25 PM EDT [    launcher] cmd map booting
/home/bey/zenbot/utils/get_products.js:6
if (c.assets.indexOf(product.asset) === -1) return false
^
TypeError: Cannot read property 'indexOf' of undefined
at /home/bey/zenbot/utils/get_products.js:6:19
at Array.filter (native)
at get_products (/home/bey/zenbot/utils/get_products.js:5:23)
at mapper (/home/bey/zenbot/plugins/gdax/backfiller.js:12:20)
at /home/bey/zenbot/node_modules/run-parallel/index.js:41:7
at Array.forEach (native)
at module.exports (/home/bey/zenbot/node_modules/run-parallel/index.js:40:11)
at mapper (/home/bey/zenbot/node_modules/zenbrain/core/mapper/mapper.js:9:5)
at Object. (/home/bey/zenbot/node_modules/zenbrain/core/launcher/launcher.js:76:11)
at Immediate._onImmediate (/home/bey/zenbot/node_modules/sosa/api.js:15:12)
I looked around and there are no open or closed issues related to this.
Does anybody know whats going on here?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/carlos8f/zenbot/issues/61, or mute the thread
https://github.com/notifications/unsubscribe-auth/ABmOhNr5lVyqSke42UwTcRHgJU533xScks5qnxKMgaJpZM4J3Rrx
.

Thanks! I just caught that at the same time!
Will close this issue off now too


Make biber survive calls to strip

It would be great if the biber binary survived
strip biber

just as a safety measure.  Alternatively, biber could ask the user at a fatal error at the very beginning of execution whether the binary was accidentally stripped.
As an example, biber --help showed
Perl lib version (5.26.3) doesn't match executable
  'perl' version (5.26.1) at
  /opt/local/lib/perl5/5.26/darwin-thread-multi-2level/Config.pm line 62.
Compilation failed in require at /opt/local/lib/perl5/site_perl/5.26/PAR.pm line 7.

after accidental stripping – I wasn't aware that biber comes with its own Perl interpreter, and after hours of investigation I was still not able to find out why my installed PAR bundle reports issues due to different perl versions...

I think this is unlikely - biber isn't a normal .exe (it is a PAR exe) and is also specially modified to allow it to be signed on OSX. I might be able to design a warning about stripping but this is the first time in years anyone has tried to strip it ...


Should this not be min?

https://github.com/KULeuven-MICAS/stream/blob/ae7ed828baeb1d557f3874032737e3f613de9107/stream/classes/hardware/architecture/accelerator.py#L321

No. The links variable represents the links needed to transfer from Core A to core B. If one of these links has a lower bandwidth, we assume the worst-case transfer time across all of them.
Hope that clarifies your concern.

Bandwidth is inversely proportional to duration. You should either take the max of link.bandwidth or the min of duration. Here you are taking max of duration.

Oh nvm, I re-read your comment, now it makes sense. You are considering the worst-case transfer time.


Compact menuBarVisibility's icon doesn't exist/appear.

"window.menuBarVisibility": "compact"

I fixed it, thanks for reporting the issue 👍 I already published a new version on the marketplace.


Temporal: Propose educated guess on whether Temporal can meet our requirements; identify any red flags

Please bring up red flags asap -- during stand-ups or on slack. Thanks!


[PR/Fixes] Agent Service / Dual Stack Socket

What type of PR is this?

Uncomment only one  /kind <> line, press enter to put that in a new line, and remove leading whitespace from that line:
/kind breaking
/kind bug

/kind cleanup

/kind documentation
/kind feature
/kind hotfix

What this PR does / Why we need it:
This fixes #744 so it passes tests, and does some other small cleanup.
This includes:

Dual stack UdpSocket
Update Agent code to use Dual Stack Socket
Fix shutdown channel in Agent test
Upgrade to 50ms delay on ping test (sometimes failed for me after compilation at 10ms)

Which issue(s) this PR fixes:

Also foundational work on #666.
Special notes for your reviewer:
Once this is merged, I can move on to using the DualStackLocalSocket throughout Quilkin, so we can finish #666.
Also, I rebased against main, so it created some mess (but I also fixed up the conflicts in #744) - apologies for that.

Looks like https://developers.google.com/protocol-buffers now redirects to https://protobuf.dev/ - I'll file a separate PR  to fix.

@XAMPPRocky I cleaned up the commits on both PRs, rebased #744 against main, and rebased this one as well.
Assuming it passes CI, this should be good to approve and merge into your PR, and then we can approve your PR, and everything should bubble up nicely.


Reports unsupported methods in Newtonsoft & SharpZip

Te tool is listing the following errors:

T:ICSharpCode.SharpZipLib.Zip.ZipFile
T:ICSharpCode.SharpZipLib.Zip.ZipFile

T:ICSharpCode.SharpZipLib.Zip.ZipFile
M:ICSharpCode.SharpZipLib.Zip.ZipFile.#ctor(System.IO.FileStream)

T:Newtonsoft.Json.Linq.JObject
T:Newtonsoft.Json.Linq.JObject

T:Newtonsoft.Json.Linq.JObject
M:Newtonsoft.Json.Linq.JObject.Parse(System.String)

But the code compiles just fine (see attached). Is this a false positive? Or is Visual Studio incorrectly compiling it without an error? (Or do I not understand something about all this?)
ApiPortAnalysis.xlsx
SampleApp.ZIP

@DavidThi808 The ApiPort tool currently has the limitation of only reporting if APIs are available in .NET Core core package. In these cases, doesn't analyze other NuGet packages beyond .NET Core core packages. Both ICSharpCode and Newtonsoft have .NET Core supported Nuget packages, but they are not released as part of .NET Core framework meta packages, but they were part of the .NET Core or Mono framework in some previous .NET versions. This is why they showed up on the report as not supported on .NET Core 3.*+ . I know it is very confusing to customer, and it is something we need to better define and resolve moving forward. Thank you for reporting the issue.

Closing as API Port was deprecated in favor of binary analysis in .NET Upgrade Assistant.


add perf smoketests

Something should fail the travis build if dot.rkt regresses substantially relative to Racket.

Fixed at least with ae8152


validateFullMetadata

Hi,
can somebody explains me why this method in ChainDriver is empty and when it is triggered?
I would be also gratefull for short description general purpose (or working example) of this method because I cant get the point of it from code comments.
I didn't know where to post this question so sorry if it should not be an issue.

Hi, if you use Mapping extension. documentation with example is here validateFullMetadata is an interface method, and is used to ensure collected metadata is valid. This is usable in cases where metadata is merged from MappedSupperclass and maybe some inherited classes.
This method is triggered only when it has parsed all parent classes and current one.
The best example would be, if you have tree metadata fields in mappedsupperclass and there is a tree class which extends this mappedsuperclass, in that case all metadata needs to be validated in the when tree class is being mapped.

Thanks for answer! Last question.
So if my class metadata are independant from other there is no need to use this method?

yes, you can leave it empty, its just for validation, and required as an interface method. Because extension triggers it for all metadata drivers.

Ok now its clear. But why validateFullMetadata() method from driver Chain (file: Gedmo/Mapping/Driver/Chain.php) its not simillar to readExtendedMetadata() method? Shouldnt there be a loop through all drivers that call validateFullMetadata at each driver?

Hm, thats a good catch, I guess this method could be removed at all. And all classes which are not a mapped superclass validaded


OOM errors and saved explanations

Hello,
I was trying to run your code and ran into some issues, and was hoping you could clarify some things.
My GPU is throwing OOM errors, specifically on the EmberNN experiments while generating the explanations using the shap library. The full dataset is too large to load into memory, how much memory did your GPU have that you used to run the experiments?
Also, I was wondering if you could release the explanations used in the paper, as they might be quite cumbersome to generate (given that they do not fit on a single Tesla V100 GPU).
Cheers!

Hi @hiddely, yes unfortunately computing the SHAP values for the NN is quite computationally expensive. I think for most experiments I only used CPUs.
I'll check if I have a SHAP file for EmberNN saved somewhere


I'm unable to locate a "Required Permissions blade"

I'm unable to locate a "Required Permissions blade" to assign a role which is set as application. There's a great example on user assignment but none for application roles. I'm wanting to assign a Logic App with System assigned identity enabled access to a role on an App Service resource.

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

ID: 9939fc33-8762-3104-eae0-08250c508100
Version Independent ID: 9c6fa664-df37-40aa-f46e-9e59f79ae215
Content: Add app roles and get them from a token - Microsoft identity platform
Content Source: articles/active-directory/develop/howto-add-app-roles-in-azure-ad-apps.md
Service: active-directory
Sub-service: develop
GitHub Login: @kalyankrishna1
Microsoft Alias: kkrishna

@BeMor  Thank you for your feedback . We will investigate and update the thread further.

Hello @BeMor, we appreciate your question and thank you for reaching out to us.
I added a dummy Application role (ConsumerApps) in Manifest -

The line When available to applications, app roles appear as application permissions in the Required Permissions blade. in the documentation means that you will be able to see the App Roles of Applications in Application Permissions as shown below -

We will propose a change in documentation as appropriate and raise a PR.
Do let us know if this helps and if there are any more queries around this.

Reopening as awaiting an acknowledgement from @BeMor.

@BeMor, we will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


CI: Cilium L4LB XDP: error: timed out waiting for the condition on pods/cilium

Found quite a few failed tests due to timeout while waiting for cilium to be ready. For example https://github.com/cilium/cilium/runs/6127187169?check_suite_focus=true:
+ nsenter -t 12806 -n /bin/sh -c 'tc qdisc add dev eth0 clsact && tc filter add dev eth0 ingress bpf direct-action object-file ./test_tc_tunnel.o section decap'
++ kubectl -n kube-system get pod -l k8s-app=cilium '-o=jsonpath={.items[0].metadata.name}'
+ CILIUM_POD_NAME=cilium-lgs5v
+ kubectl -n kube-system wait --for=condition=Ready pod cilium-lgs5v --timeout=5m
error: timed out waiting for the condition on pods/cilium-lgs5v

Checking cilium-agent logs revealed:
2022-04-22T11:06:00.638312597Z level=info msg="Auto-disabling \"enable-bpf-clock-probe\" feature since KERNEL_HZ cannot be determined" error="Cannot probe CONFIG_HZ" subsys=daemon
2022-04-22T11:06:00.638775616Z level=info msg="Using autogenerated IPv4 allocation range" subsys=node v4Prefix=<IP_ADDRESS>/16
2022-04-22T11:06:00.638791503Z level=info msg="Initializing daemon" subsys=daemon
2022-04-22T11:06:00.639197134Z level=fatal msg="Error when enabling sysctl parameters" error="could not open the sysctl file /proc/sys/net/ipv4/ip_forward: open /proc/sys/net/ipv4/ip_forward: read-only file system" subsys=daemon

Cilium was running on KIND.

Is there any update on the above issue? also getting the same error while running the tests-l4lb.yaml file.

@odidev Are you hitting Error when enabling sysctl parameters" error="could not open the sysctl file /proc/sys/net/ipv4/ip_forward: open /proc/sys/net/ipv4/ip_forward: read-only file system" subsys=daemon?

Is there any update on the above issue?

Noup, I haven't hit it / haven't looked closer into it.


fix(useTransferToL1/2): use promise instead of contract event

Description of the Changes
Contract events are sometimes not dispatched - until this will be investigated and resolved, use promise as the indication for tx completed.
Checklist

[ ] Changes have been done against master branch, and PR does not conflict
[ ] New unit / functional tests have been added (whenever applicable)
[ ] Test are passing in local environment
[ ] Docs have been updated
[ ] PR title is follow the Conventional Commits convention: <type>[optional scope]: <description>, e.g: fix: prevent racing of requests

This change is

:tada: This PR is included in version 1.5.1-dev.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.6.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Split the k8s playbook into 2 files

Issue : #152

Split the k8s playbook into 2 files
Allow to execute the misc roles using command : ansible-playbook kubernetes/ansible/k8s-misc.yml --limit ${VM_NAME} --tag "docker_registry"

I think all role invocations in the k8s_misc playbook should also have the never tag, otherwise if the playbook is executed without tags all roles will be applied, WDYT @cmoulliard ?

all roles will be applied

We will not apply all the roles but some only

playbook should also have the never tag

Why ? What is the purpose of the tag never ?

playbook should also have the never tag

Why ? What is the purpose of the tag never ?

Without the never tag, it you execute the playbook without tags the roles will be executed whereas with the never tag the role is only executed if the tag is explicitly added to the command line.

Without the never tag, it you execute the playbook without tags the roles will be executed whereas with the never tag the role is only executed if the tag is explicitly added to the command line.

So we will then keep the playbook as it has been defined as we will specify when needed the misc role(s) to be applied ?


feat: Milvus bump up to 2.4

Description
milvus launched 2.4 version in yesterday
it enables Multi-vector Search for Simplified Multimodal Searches and also added support for re-rank model
these updates is very useful for our current RAG design
https://milvus.io/blog/milvus-2-4-nvidia-cagra-gpu-index-multivector-search-sparse-vector-support.md
Motivation and Context
close #481

[ ] I have raised an issue to propose this change (required for new features and bug fixes)

Types of changes
What types of changes does your code introduce? Put an x in all the boxes that apply:

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds core functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Documentation (update in the documentation)
[ ] Example (update in the folder of example)

Implemented Tasks

[ ] Subtask 1
[ ] Subtask 2
[ ] Subtask 3

Checklist
Go over all the following points, and put an x in all the boxes that apply.
If you are unsure about any of these, don't hesitate to ask. We are here to help!

[ ] I have read the CONTRIBUTION guide. (required)
[ ] My change requires a change to the documentation.
[ ] I have updated the tests accordingly. (required for a bug fix or a new feature)
[ ] I have updated the documentation accordingly.

lucky me, I merged the old version of Milvus right on the day they released a shiny new one version...

Haven't update all new capabilities yet since it's still in milvus's beta version , will do it later when we need further multi-modal support


As discussed here, it would be good to manage the number of stale PRs we have.
Having a dashboard that makes it easy to review the various kinds of stale PRs we have would help us keep the number low. Reviewers would use this dashboard to easily find PRs that need updating or closing.

I have a branch with a stale PR dash implemented on my fork, but I haven't addressed hanging or abandoned PRs yet.
What is considered a reviewer in the above definitions? (committer, not a bot, not the submitter?)

I think that's a good definition of a reviewer for starters.

@nchammas which are you referring to as a good definition? Committer, not a bot, or not the submitter? Because filtering on bots is already in the code, and filtering the submitter is mostly trivial but filtering on the Spark committers list is not trivial (though it may still be straight forward, I haven't tried yet)

Oh, I meant the combination of all 3 conditions. But actually, just having reviewer = committer accomplishes the goal here and is simpler.
There might be a file in the main Spark repo that tracks the GitHub usernames of all the committers. @srowen or @rxin, would you happen to know something about this?
If we had an up-to-date list that tracked this, the PR dashboard could use it to generate reports as described in this issue.

I don't think there is a list of committer github handles. There's a list of JIRA usernames somehow somewhere in the ASF infra. But for purposes here, I'd take anyone that's not the submitter as a reviewer. And not Jenkins / the ASF bot.


is this plugin support push notification through Google GCM in iOS devices

Is this plugin support push notification through Google GCM in iOS devices?

@Mirodil this is a duplicate of #115


Failing with error "Cannot read properties of null"

I am running Chrome Version 100.0.4896.60 (Official Build) (64-bit)
I noticed that just a few hours ago the extension stopped working. The console shows the following error:
Error in event handler: TypeError: Cannot read properties of null (reading 'setAttribute')
at chrome-extension://bcjindcccaagfpapjjmafapmmgkkhgoa/js/content.js:77:64

I ran into the same issue.
This is due to #191 not checking if the "meta" "color-scheme" property is actually set or exists, which is not the case on many browsers, and trying to invoke setAttribute on it anyway.

I had this issue as well on chrome version 100.0.4896, but just updated to 101.0.4951.67 and it is resolved.

I'm also encountering this issue with Microsoft Edge 100.0.1185.44 (Official build) (64-bit)

Me Too

Same issue here.

just submitted a PR https://github.com/callumlocke/json-formatter/pull/195
fixes it for me

Now fixed in v0.6.2


Clicking on the active tab hides tab content in v4.

I noticed that when you click on an active tab, the tab panel will hide (I'm using Chrome and bootstrap.native@2.0.21). This behavior is also present on the demo page.

I can reproduce this bug in my projects.


Join qunitjs organisation

Hi @kof,
Would you be interested in having this repository join the @qunitjs organisation? I'd be happy to accept a transfer consider node-qunit a more official part of the QUnit family.
Let me know what you think,
– Timo
/cc @leobalter @jzaefferer
PS: Note that in case of transfer, GitHub will maintain full redirects for all urls and git interaction.

sure!

@kof Okay. GitHub only allows transfer from an org member. Assuming you'll want to join yourself as well, I've invited you to the org. From there you can transfer the repo.


iOS only BluetoothCharacteristic.read returns munged / duplicated data when data is 'large'. Android works perfectly.

  I did this in attempt to verify that I was not munging the data somehow in my code.
At one point we were getting correct responses. I'm not sure where to go to debug this. Did I somehow get a new protobuf library that is broken? Did the iOS update from 14.0 to 14.0.1 and break this? etc...
Any clues on how to debug this would be appreciated.

This has been reported multiple times. Try this PR: https://github.com/pauldemarco/flutter_blue/pull/850/files
#525
#840

This has been reported multiple times. Try this PR: https://github.com/pauldemarco/flutter_blue/pull/850/files
#525
#840

That looks like a totally different bug. This involves reading in individual characteristic and getting duplicated data inside one read. The others look like reading streams of data. Do you still think it's the same?

I added the following NSLog line into didUpdateValueForCharacteristic delegate method
- (void)peripheral:(CBPeripheral *)peripheral didUpdateValueForCharacteristic:(CBCharacteristic *)characteristic error:(NSError *)error {
  NSLog(@"didUpdateValueForCharacteristic after uuid: %@ value: %@", [characteristic.UUID fullUUIDString], [characteristic value]);

The returned value is 552 bytes when it should be 491 bytes. So as far as I can tell readValueForCharacteristic is sending the wrong data to the delegate method.

I am closing out this issue. I currently believe that our hardware is incorrectly returning the wrong data if the mtu < 512 bytes. That is why is works on Android and not on iOS.


MatMomentDateModule: year is not filled with actual year

What is the expected behavior?
When I enter 1.1.5 in the datapicker, the date should be 01.01.2005. This works with the native date adapter but not with the moment date adapter.
What is the current behavior?
1.1.5 -> 01.01.0005
What are the steps to reproduce?
Test it with 1.1.5 on the angular matrial page: https://material.angular.io/components/datepicker/overview
under: Datepicker that uses Moment.js dates
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Version 6 and above
Is there anything else we should know?

Material doesn't really do anything to the date. It just takes the value, passes it to Moment, and renders the result. If you want to customize the logic for how it is formatted, you can create your own date adapter that extends the MatMomentDateAdapter.


Update README.md

Closes #
📑 Description

✅ Checks

[ ] My pull request adheres to the code style of this project
[ ] My code requires changes to the documentation
[ ] I have updated the documentation as required
[ ] All the tests have passed

☢ Does this introduce a breaking change?

[ ] Yes
[ ] No

ℹ Additional Information

Summary by Sourcery
Documentation:

Expand the README.md to include detailed sections on project features, getting started instructions, and contribution guidelines.

Description by Korbit AI
What change is being made?
Revamp the README.md to provide detailed information about the project, including project features, setup instructions, additional resources for learning Flutter, and contribution guidelines.
Why are these changes being made?
The previous README.md was sparse and lacked detailed information necessary for newcomers to understand the purpose, setup, and contribution process for the project. The enhanced README.md aims to make the repository more accessible and informative, thereby improving the learning experience for new users interested in Flutter development.

Is this description stale? Ask me to generate a new description by commenting /korbit-generate-pr-description

Summary by CodeRabbit

Documentation

Enhanced clarity and organization of the README.md file.
Updated introductory line to emphasize exploration in Flutter development.
Added a new section describing Flutter as an open-source framework.
Reformatted badges for improved readability.
Introduced a "Features" section outlining key project aspects.
Expanded "Getting Started" section with detailed setup instructions.
Improved organization of learning resources, contribution guidelines, and licensing sections.

@gstraccini create labels


Add quick code for cognate detection and workflow

we lack these still, they shoudl be added by myself, so the workflow is clearer.

yes please!


Resolve issue #11 prevent return of -1 ( 255 ) code

Introduce help flag on initial executor test to prevent invalid code from being returned.

thanks!


search-box input field not hided on startup if  is inside a non first mat-tab

Do you want to request a feature or report a bug?
bug
Screenshots or link to CodePen/Plunker/JSfiddle
https://covalent-uteg3e.stackblitz.io   (icons are not showing but the abnormal behavior can be spotted)
Bug
The search-box input field is not properly hidden (width: 0) when the search-box is inside a mat-tab that is initially hided (any tab that is not the first one)
What is the expected behavior?
the search-box input field should be hided
What is the motivation / use case for changing the behavior?
Using  inside a
Which version of Angular and Material, and which browser and OS does this issue affect?
Angular 5.2.7
Material 5.2.3
Chrome 64
Did this work in previous versions of Angular / Material?
No

I can confirm that issue, the width is not correctly set to 0.

I'm experiencing that issue too


[Feature Request] Add notification when app is trying to re-log in

Explain in detail what your suggested feature would be used for.
When the VRChat token expires for some reason, and the credentials are saved into the app, pop-up a notification on the system tray saying they need the 2FA code sent to the email.
Describe how it would look if it requires a UI.
It would not require an in-app UI, but rather a notification, maybe saying "Your account X session has expired, further action is required".
Explain why people would want to use it.
I kept receiving daily emails about someone trying to log in into my account on my email, and it scared the hell out of me because I thought someone had my password, but when I opened VRCX I noticed it was asking me to introduce the email 2FA code.
So basically: first, to not scare users who do not open the app daily but have it running on background; and second, to let know users that they will not receive notifications about this account because the session expired.

This is a good idea. Honestly just having a notification informing you that your token expired would be great in general. I don't often notice VRCX needs to be relogged in for some time until I happen to recheck.

I've gone with the simple solution of focusing the window whenever a email or 2FA code is required.

Haha nice, tysm! <3


AMBARI-23127. Allow default value of number of parallel tasks run during Upgrade to be customizable. (swagle)

What changes were proposed in this pull request?
Add a new flag to server configuration in order to override default max parallelism.
How was this patch tested?
Ran related unit tests.
Manual test pending.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/919/
Test PASSed.


Game-breaking UPS drain when running a prospector scan on Nauvis

Having a prospector scanner fill it's progress bar causes it to render an ungodly amount of indicators (or whatever) on the six chunk radius it covers, slogging down the game to a creeping halt (I ran into 3 FPS/5 UPS), and even suspected a crash several times from lagging that much.
running /c render.clear("Subsurface") fixed it (with help of _CodeGreen).
Please implement a fix for preventing the prospector to work on the standard surface layer.

How does the corresponding subsurface look? Are there resources where the
prospector showed indicators?
Divine Ray @.***> schrieb am Sa. 29. Juni 2024 um 18:01:

Having a prospector scanner fill it's progress bar causes it to render an
ungodly amount of indicators (or whatever) on the six chunk radius it
covers, slogging down the game to a creeping halt (I ran into 3 FPS/5 UPS),
and even suspected a crash several times from lagging that much.
running /c render.clear("Subsurface") fixed it (with help of _CodeGreen).
Please implement a fix for preventing the prospector to work on the
standard surface layer.
—
Reply to this email directly, view it on GitHub
https://github.com/NathaU/factorio-subsurface/issues/29, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARG36M4F4GATNOHYBFCK72TZJ3K4HAVCNFSM6AAAAABKDJTDJKVHI2DSMVQWIX3LMV43ASLTON2WKOZSGM4DCOBSG44DSOI
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

The respective subsurface was not dug (iirc) at that time, and from what i can tell the now-dug subsurface is chock-full of py's Bitumen Seeps (which i believe replace vanilla oil patches)

amendment: not just oil, apparently any of the big ore deposits. I accumulated 3.3bil aluminium reserve now...

But this means that the prospector is working properly, there are issues in resource placement. They are mirrored so thats map gen setting related.
Could you provide a savegame?

PyAE Subsurface.zip
Said resource patches just pop up when expanding the cave, not from what i could tell be related to the prospector.


ValueError: dtype inference failed in map_blocks.

After upgrading to dask 0.13 from 0.11 I am getting errors relating to failed dtype inference within map_blocks. Here's an example:
Python 3.6.0 | packaged by conda-forge | (default, Jan 13 2017, 23:17:12)
[GCC 4.8.2 20140120 (Red Hat 4.8.2-15)] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import dask.array as da
>>> import dask
>>> dask.__version__
'0.13.0'
>>> import numpy as np
>>> np.__version__
'1.11.3'
>>> x = np.ones((5, 3))
>>> y = np.ones((5, 3))
>>> dx = da.from_array(x, chunks=(2, None))
>>> dy = da.from_array(y, chunks=(2, None))
>>> def f(a, b):
...     return a + b[:, 1, None]
...
>>> dz = da.map_blocks(f, dx, dy, dtype=x.dtype)
>>> dz.compute()
array([[ 2.,  2.,  2.],
       [ 2.,  2.,  2.],
       [ 2.,  2.,  2.],
       [ 2.,  2.,  2.],
       [ 2.,  2.,  2.]])
>>> dz = da.map_blocks(f, dx, dy)
Traceback (most recent call last):
  File "/home/aliman/miniconda3/envs/dev-scikit-allel-py36/lib/python3.6/site-packages/dask/array/core.py", line 457, in apply_infer_dtype
    o = func(*args, **kwargs)
  File "<stdin>", line 2, in f
IndexError: index 1 is out of bounds for axis 1 with size 1

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/aliman/miniconda3/envs/dev-scikit-allel-py36/lib/python3.6/site-packages/dask/array/core.py", line 629, in map_blocks
    dtype = apply_infer_dtype(func, args, kwargs2, 'map_blocks')
  File "/home/aliman/miniconda3/envs/dev-scikit-allel-py36/lib/python3.6/site-packages/dask/array/core.py", line 470, in apply_infer_dtype
    raise ValueError(msg)
ValueError: `dtype` inference failed in `map_blocks`.

Original error is below:
------------------------
IndexError('index 1 is out of bounds for axis 1 with size 1',)

Traceback:
---------
  File "/home/aliman/miniconda3/envs/dev-scikit-allel-py36/lib/python3.6/site-packages/dask/array/core.py", line 457, in apply_infer_dtype
    o = func(*args, **kwargs)
  File "<stdin>", line 2, in f

I.e., it works when I explicitly provide a dtype, but if not then dtype inference fails. I can work around this by providing an explicit dtype but thought I'd raise an issue because this didn't used to be a problem in dask 0.11.

This is due to the recent change to mandatory dtypes in dask.array. Previously we allowed dtypes to be unknown, and would compute them as needed. This sometimes led to unpredictable performance, and was harder to reason about. As such, we switched to mandatory known dtypes for all arrays (fixed in https://github.com/dask/dask/pull/1755).
To infer dtypes, we create dummy data using np.ones((1,) * arg.ndim, dtype=arg.dtype) (see https://github.com/dask/dask/blob/master/dask/array/core.py#L461-L462), and then apply the function. For many functions that don't rely on the shape of the blocks, these arguments broadcast and work nicely. However, your function assumes a shape >= 2 for axis 1. In this case, there's not much we cant do.
The only thing I think we could maybe do better here is improve the error message. I've addressed this in #1951, please let me know if it could be better.

Thanks, the error message is much better.
So do I understand this right that previously dtype inference was done by
computing one block of the result, but in general that could take time and
complicates things if a task scheduler is involved? Hence opting for a
simpler attempt to infer dtype by applying the function on some dummy data?
FWIW I'm surprised the dummy data inference works in many cases. I think it
would be ok to just require the user to provide a dtype.
On Tuesday, January 31, 2017, Jim Crist<EMAIL_ADDRESS>wrote:

This is due to the recent change to mandatory dtypes in dask.array.
Previously we allowed dtypes to be unknown, and would compute them as
needed. This sometimes led to unpredictable performance, and was harder to
reason about. As such, we switched to mandatory known dtypes for all arrays
(fixed in #1755 https://github.com/dask/dask/pull/1755).
To infer dtypes, we create dummy data using np.ones((1,) * arg.ndim,
dtype=arg.dtype) (see https://github.com/dask/dask/
blob/master/dask/array/core.py#L461-L462), and then apply the function.
For many functions that don't rely on the shape of the blocks, these
arguments broadcast and work nicely. However, your function assumes a shape

= 2 for axis 1. In this case, there's not much we cant do.

The only thing I think we could maybe do better here is improve the error
message. I've addressed this in #1951
https://github.com/dask/dask/pull/1951, please let me know if it could
be better.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/dask/dask/issues/1949#issuecomment-276452198, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAq8QnXMj8810N5JTIyN5feCasQ80bmTks5rX4A5gaJpZM4LyZpg
.

--
Alistair Miles
Head of Epidemiological Informatics
Centre for Genomics and Global Health http://cggh.org
The Wellcome Trust Centre for Human Genetics
Roosevelt Drive
Oxford
OX3 7BN
United Kingdom
Email<EMAIL_ADDRESS>Web: http://purl.org/net/aliman
Twitter: https://twitter.com/alimanfoo
Tel: +44 (0)1865 287721

Previously we'd store None for dtype if not provided (stored on the object as _dtype), and the dtype property would compute a single element from one of the blocks if ever requested. This would lead to unexpected computation, so a simpler static method was applied. This is similar to how metadata is inferred in dask.dataframe as well, and seems to work fairly well.
For many applications, the mapped functions are simple elementwise broadcasting functions, so applying them to single element arrays of the proper ndims works in most (but not all) cases. For robustness, it's recommended to provide the dtype if known, but the inference works fairly well if your function isn't shape dependent.

Thanks for following up.
On Tuesday, January 31, 2017, Jim Crist<EMAIL_ADDRESS>wrote:

Previously we'd store None for dtype if not provided (stored on the
object as _dtype), and the dtype property would compute a single element
from one of the blocks if ever requested. This would lead to unexpected
computation, so a simpler static method was applied. This is similar to how
metadata is inferred in dask.dataframe as well, and seems to work fairly
well.
For many applications, the mapped functions are simple elementwise
broadcasting functions, so applying them to single element arrays of the
proper ndims works in most (but not all) cases. For robustness, it's
recommended to provide the dtype if known, but the inference works fairly
well if your function isn't shape dependent.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/dask/dask/issues/1949#issuecomment-276519562, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAq8QjumfGvfF06qQafusinI8yusNLCGks5rX7szgaJpZM4LyZpg
.

--
Alistair Miles
Head of Epidemiological Informatics
Centre for Genomics and Global Health http://cggh.org
The Wellcome Trust Centre for Human Genetics
Roosevelt Drive
Oxford
OX3 7BN
United Kingdom
Email<EMAIL_ADDRESS>Web: http://purl.org/net/aliman
Twitter: https://twitter.com/alimanfoo
Tel: +44 (0)1865 287721


How run docker in workflow?

Previously i run step with docker image for build docker image in container. And have error ERROR: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running? How fix this?
MY CONFIGURATION
    container:
      securityContext:
        privileged: true
      image: docker:latest
      command: [sh, -c]

Closing since this is unrelated to workflows but a general question to Docker.


Added a way to load angular apps dynamical

With this pull request all OpenSlides apps are loaded dynamical into angular.
This can not be done with gulp, because there has to be a way to install plugins without node and gulp.

Rebase and check Travis again.

@normanjaeckel all done, please merge


Remove version: Tableau.Public version 24.2.931

[Automated] It returns code over 400 in all urls
Microsoft Reviewers: Open in CodeFlow

URL: https://downloads.tableau.com/public/TableauPublicDesktop-64bit-2024-2-2.exe
Response status code does not indicate success: 403 (Forbidden).
(Automated message - build 896)