DEVEXP-41: Use QueryMarkLogic with consistent behavior

Thank you for submitting a contribution to marklogic-community/marklogic-nifi-incubator.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[ ] Is there a github ticket associated with this PR? Is it referenced
in the commit message?

[ ] Has your PR been rebased against the latest commit within the target branch (typically master)?

[ ] Is your initial contribution a single, squashed commit?

For code changes:

[ ] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
[ ] Have you written or updated unit tests to verify your changes?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
[ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
[ ] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

[ ] Have you ensured that format looks appropriate for the output in which it is rendered?

I managed to fix everything based on comments but I have an error in apply transform that I cannot see where is coming.

I can't see what error you're getting in that screenshot, but on your branch, I ran all the tests and ApplyTransformMarkLogicIT failed with an error message of "this relationship original is not known". That means that a FlowFile is being sent to a relationship that the processor doesn't know about. Odds are you'll need to make part of the fix that's identified in DEVEXP-43, which is that the Apply processor isn't registering the "Original" relationship in its "init" method.

I can't see what error you're getting in that screenshot, but on your branch, I ran all the tests and ApplyTransformMarkLogicIT failed with an error message of "this relationship original is not known". That means that a FlowFile is being sent to a relationship that the processor doesn't know about. Odds are you'll need to make part of the fix that's identified in DEVEXP-43, which is that the Apply processor isn't registering the "Original" relationship in its "init" method.

So I'll fix it in DEVEXP-43. In that case if you are ok with the update let me know

Failing test is commented out and will be fixed in DEVEXP-43. All commits are not stashed.


Support byte array constructor

This also allows for case-insensitive matching on the type and value properties for TypeSpecified configurations.

fine by me after Brian's questions are addressed

Looks good. 👍


tighten package requirements for HTFA Docker image

Recent updates to some third-party modules introduced a few bugs in the HTFA notebook.  Pinned various MPI & plotting packages to ensure a working combination of dependency versions are installed.

to give some additional background: i had my students for this class go through the HTFA tutorial and some of them ran into trouble running the notebook due to changes in the packages @paxtonfitzpatrick mentioned above.  this pull request pins the version numbers of some additional packages to provide more "future proofing" for the docker image and notebook associated with the HTFA tutorial.


rustfmt panics: failed to emit error: operation not supported by the terminal

Why does rustfmt panic?
> rustfmt foo.rs
thread 'main' panicked at 'failed to emit error: operation not supported by the terminal', C:\Users\appveyor\.cargo\registry\src\github.com-1ecc6299db9ec823\rustc-ap-rustc_errors-29.0.0\emitter.rs:1300:23
stack backtrace:
   0: <unknown>
   1: <unknown>
   2: <unknown>
   3: <unknown>
   4: <unknown>
   5: <unknown>
   6: <unknown>
   7: <unknown>
   8: <unknown>
   9: <unknown>
  10: <unknown>
  11: <unknown>
  12: <unknown>
  13: <unknown>
  14: <unknown>
  15: <unknown>
  16: <unknown>
  17: <unknown>
  18: <unknown>
  19: <unknown>
  20: <unknown>
  21: <unknown>
  22: <unknown>
  23: <unknown>
  24: <unknown>
  25: <unknown>
  26: <unknown>
  27: <unknown>
  28: <unknown>
  29: <unknown>
  30: <unknown>
  31: <unknown>
  32: <unknown>
  33: <unknown>
  34: <unknown>
  35: <unknown>
  36: <unknown>
  37: <unknown>
  38: <unknown>
  39: <unknown>
  40: <unknown>
  41: <unknown>
  42: <unknown>
  43: <unknown>
  44: <unknown>
  45: <unknown>
  46: <unknown>
  47: <unknown>
  48: <unknown>
  49: <unknown>
  50: <unknown>
  51: BaseThreadInitThunk
  52: RtlUserThreadStart
> rustfmt --version
0.3.8-nightly (346238f4 2018-02-04)

What are you doing to trigger the panic? It would be very helpful if you could build from source to see if this is still a problem with current master and to get a better backtrace (by using a debug build).

I would assume this is due to something like trying to emit coloured output to a terminal which does not support colours.


[WIP] UpdateLog tests

This introduces UpdateLog tests. UpdateLog is a data structure which contains a description of mutations to the instance tree in order to get to the desired state.
The most important part is subTreeChange which highlights the type of subtree change.

Nested means that the underlying subtree did change but it was an element deep down the tree.
NoChange means that the tree has not changed.
ReplaceElements means that a subtree should be replaced
PrependElement means that an element should be prepended

Todos:

[ ] Improve formatting in tests. I want to handle this first since poor readability affects productivity a lot
[x] Determine why the existing test is failing :)
[x] Implement tests which verify the UpdateLog step by step. It's important since we can determine that the minimal amount of steps is indeed in the UpdateLog.
[x] Test applyUpdateLog. The tree from applyUpdateLog should be the same as newly returned element.
[x] Introduce side effects in applyUpdateLog
[ ] applyUpdateLog should perform mutations to the tree and invoke render-cycle lifecycle functions. In order to test that we should build a list of all mutations and lifecycle function invocations and assert if they happen. Similar to what we do with UpdateLog. The RenderUpdateLog however will only be a part of tests. Also, in order to test it properly we need to introduce mutations to the TestRenderer because currently the hostView is immutable.

jbuilder build -x ios should work but it doesn't.
In order to build currently you need to do:
jbuilder build -x ios
ocamlfind -toolchain ios ocamlopt -I ./_build/default.ios/src/lib -I ./_build/default.ios/src/flex/.flex.objs -I ./_build/default.ios/src/lib/.r2n2.objs -I ./_build/default.ios/src/flex -package unix -linkpkg -output-complete-obj flex.cmxa r2n2.cmxa -impl ./_build/default.ios/src/bin/react_ios.re.ml -o react_ios.o

and then proceed with the Xcode build.


Pull Request previews not getting generated

Environment information
n/a

Description
Looking at https://docs.aws.amazon.com/amplify/latest/userguide/pr-previews.html it says... "On the Manage preview settings page, turn on Pull request previews. Then choose Confirm." but I can't find the "Manage preview settings page" page.

Hi @chrowe 👋 , thanks for reaching out! You can access the web previews feature as follows:

Login to the Amplify console and select the target Amplify app

From the Overview pane, select Hosting

Next, select Previews. Attached a screenshot for reference:

Select the branch and click on Edit settings

Lastly, toggle the pull request previews button to enable the feature and select Confirm. Attached a screenshot for reference:

Please note that for security purposes, previews are disabled for public repositories with Amplify backend templates.

Ok, I guess I missed the fact that there is a "Manage preview settings" for each branch. It is enabled for the main branch, but we still are not getting builds for all PRs applied to the main branch.
It looks like maybe the PRs we are having issues with were originally created against another branch and then changed to main. Does the that not trigger a build?

@chrowe If a pull request is initially created against a different base branch, such as staging, and later if the base branch is changed to main, it will not trigger a new build in Amplify. This is an expected behavior and the only workaround is to close the existing pull request and open a new one targeting the main branch.

Closing this thread since the described behavior is expected. I'll recommend raising a feature request on the hosting repository for triggering a new build in Amplify when the base branch is changed for an existing pull request.


VR52 repeater support

Before requesting a new feature / a new sensor

[x] The feature I'm requesting exists in the myVAILLANT app, and I attached a screenshot
[x] I tested the latest release, and it's missing there
[ ] I've attached exported data of my system

Describe the feature you want
I have a VR52 repeater and wonder if the integration could display some info (repeated devices?). If needed, I can create test data with my setup.
Screenshot
Attach a screenshot of the functionality in the myVAILLANT app.

Export data
Attach exported test data here

Test data would help, indeed!

Could you try the home assistant service? That should be easier to use.


feat(backend): adding mvc folder structure

Related Issue

MVC FOLDER STRUCTURE ADDED

Closes: #59
adding MVC folder structure: user controller  and routes are made for proper folder structure
Screenshots / Videos / Gif

@apeksha235 Please review my PR on issue #59

hey @JainPriya1234 please change the title of the pr according to the naming convention in contribution.md also have you tested this?

yes @apeksha235 I tested it and please let me know now is PR title  correct

@apeksha235 please help me out with pr-title

@JainPriya1234 you will have to add "feat(backend)" as well like given in the instructions

@apeksha235 please review it

@apeksha235 please review this pr

@apeksha235 please check this PR format as i updated it

@JainPriya1234 Can you resolve the merge conflicts please?

@jain-rishabh-21 I tried to resolve it but someone has done the same work as what is assigned to me that's why it is creating conflicts so I discarded my commits


Wigner function

Coverage decreased (-0.1%) to 98.64% when pulling 227b055ba6ec742c2fd4679c3629d8090cd14293 on wigner into b89e216ec61575541c2d67a3c1b0278813e32511 on master.

Coverage increased (+0.02%) to 98.795% when pulling 8dbd1090f873e76ca70315d6ac996ded4da8d845 on wigner into b89e216ec61575541c2d67a3c1b0278813e32511 on master.

Coverage increased (+0.02%) to 98.795% when pulling d36eeab50a4d04a8f98b868270498df65644b4b4 on wigner into b89e216ec61575541c2d67a3c1b0278813e32511 on master.


feat(storage): Add optional write-through cache to sql store

Summary

This adds the ability to enable a write-through cache for storage of type sqlite and postgres.
Checklist

[X] Tested and/or added tests to validate that the changes work as intended, if applicable.
[ ] Added the documentation in README.md, if applicable.

Codecov Report

Merging #314 (b7185dc) into master (262d436) will decrease coverage by 0.57%.
The diff coverage is 45.76%.

@@            Coverage Diff             @@
##           master     #314      +/-   ##
==========================================
- Coverage   83.60%   83.02%   -0.58%
==========================================
  Files          54       54
  Lines        3818     3859      +41
==========================================
+ Hits         3192     3204      +12
- Misses        489      512      +23
- Partials      137      143       +6

Impacted Files
Coverage Δ

storage/store/sql/sql.go
80.35% <42.85%> (-3.47%)
:arrow_down:

storage/store/memory/memory.go
72.13% <100.00%> (-1.31%)
:arrow_down:

storage/store/store.go
89.36% <100.00%> (+3.90%)
:arrow_up:

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


Diagram missing vnets and subnets

Ran this script for a client and it appears to have mapped all vnets correctly. Ran it on another client and it only shows one of the 3 virtual networks. They have a couple of vnets with a ton of subnets, just wondering if there's a limitation on this for the diagram portion. The Excel file does contain the proper data from the subscription.

Found the fix in another Issue post.
Edit DrawIODiagram.ps1 at the line 23 and change:
$Global:FullEnvironment = $false
to
$Global:FullEnvironment = $true


Wrong version number on readthedocs.io

Long story short
0.21.5 docs got pushed out to http://aiohttp.readthedocs.io/en/v0.24.5/
Expected behaviour
http://aiohttp.readthedocs.io/en/v0.21.5/ should work
Actual behaviour
http://aiohttp.readthedocs.io/en/v0.21.5/ shows 404

Fixed. Also 0.24.6 released


Menu raises console warning

Describe the bug
My code (simplified) is this:
<button
  ref={setAnchorEl}
  onClick={() => {
    setShowMenu(!showMenu)
  }}
>
  Click here!
</button>
<Menu
  open={showMenu}
  onClose={() => setShowMenu(false)}
  anchorEl={anchorEl}
>
  <Menu.Item>Pressure</Menu.Item>
</Menu>

Gives the error message MouseEvent.mozInputSource is deprecated. Use PointerEvent.pointerType instead.
Steps to reproduce the bug

Click the button
When the menu pops up, click at a point outside the menu
Check the console

Expected behavior
Specifications

Version: 0.32.4
Browser: Firefox
OS: Mac

Additional context

Closing as this is only a console warning outside of our control


Is this a bug ?

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

VS Code Version:
OS Version:

Steps to Reproduce:

how do i fix this ? (sorry i dont really know how to use github)

See my #132161 issue. Something wrong with the terminal this update.

@AdhTri-001 I think your issue is different.

Can you provide the vscode version and os info, thanks!

my vs code version is 1.60.0 and this thing happened right after i updated it OS is windows student

Can you launch with code --user-data-dir <dir> --verbose and provide the output. Replace <dir> with some absolute writable directory path.

Can you launch with code --user-data-dir <dir> --verbose and provide the output. Replace <dir> with some absolute writable directory path.

sorry im kinda new to all that stuff, where do i enter this code. thanks for the help btw

Open any console on the system, command prompt or powershell or windows terminal
Enter the above command
Wait for application to load and then copy the data from the terminal output

Error: Cannot find module 'C:\Users\Sun Bilgisayar\AppData\Local\Programs\Microsoft VS Code\resources\app\out\cli.js'
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:934:15)
at Module._load (internal/modules/cjs/loader.js:779:27)
at Function.f._load (electron/js2c/asar_bundle.js:5:12913)
at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:72:12)
at internal/main/run_main_module.js:17:47 {
code: 'MODULE_NOT_FOUND',
requireStack: []
this is the terminal output, sry i looked what does --user-data-dir means thats why it taked too long

Looks like a corrupted install, can you reinstall and try again.

I installed an older version and it solved thanks for your help : )

Can you perform and update to see if the issue persists with newer updates.


Version 2.7.7 - rc

'Rate Limiter - new settings to prevent DDOS',
'Monitoring - new metrics on notifications'

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: ClaudeROSSI:x: mahdibenromdhanemahdibenromdhane seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Feature/arm experimental

First draft of an small article about early access to our arm64 images

https://deploy-preview-558--stackable-docs.netlify.app/home/nightly/concepts/arm64-support current WIP
Currently deployed:
https://docs.stackable.tech/home/nightly/concepts/arm64-support


RFC: compressor, transfer: add metrics about oldest non-uploaded backup data [BF-962]

This is a draft, PoC implementation.
While trying to solve BF-962 we thought that the actual metric we'd like is not the time since the latest upload of some chunk of our backups, but the time since the oldest non-uploaded backup chunk, because large backup parts could be non-working if we've got gaps.
Backup Label: as defined in PGHoard, this is a (start-wal-segment, start-time) tuple
This PoC (not configured to work currently, null implementation in place to run tests) would work this way:

When we see a backup label for a segment on the machine side, keep track of it
When we see a backup label that was correctly uploaded to our external object storage, stop keeping track of it
Periodically, send a metric about the oldest backup label we're keeping track of

FIXMEs, TODOs, THINKABOUTs

keep seend sorted someway / use a sorted set so we shouldn't re-sort everytime we manipulate the set
consider whether we want to send metrics only on seen, only on uploaded, or in both cases, or periodically
refactor/remove duplication (just copypasted right now)
check if our actual Metrics implementations are blocking (are we slowing down/indirectly synchronizing
threads with this kind of implementation) and threadsafe (but if they aren't we have other problems as well).
since we rely heavily on a couple of info that are currently metadata (start-wal-segment and start-time) maybe
those should become actual event attributes
For this draft I signaled the "seen" when handling the compression event, but this could actually be moved to
the places where the CompressionEvent is added to the compression queue
Naming:  ThreadSafeCompressorMetadataNotifier should be something like "BackupLabelNotifier"
Make sure the notify* methods never throw, and never block (unless lock is held)

I think we should minimize complexity and in general avoid storing any state or have to rely on logic to have a correct metric meant to ensure reliability.
I'd go for something simpler, like "at regular interval, independent from other events, send the age of the oldest file in the folder where files are stored, just do a stat on all files every time we have to compute that metric, don't care about optimizing until we have proof that it is a problem"

I think we should minimize complexity and in general avoid storing any state or have to rely on logic to have a correct metric meant to ensure reliability.
I'd go for something simpler, like "at regular interval, independent from other events, send the age of the oldest file in the folder where files are stored, just do a stat on all files every time we have to compute that metric, don't care about optimizing until we have proof that it is a problem"

Is this a comment on the initial implementation or on Roman's proposal?
If it's on the original proposal, I see a problem: sometimes, for reasons that I should investigate (but the option is definitely here in the code), pghoard deletes the file it's required to upload once the upload is done. Sometimes it doesn't. With your suggestion, we'd lose track of the important distinction between "it was uploaded" and "it was not uploaded".
By the way: I think this change requires its own ticket, it's not an "easy thing to do away with a couple of basic commits".

"it was uploaded but not deleted" is also a bug that should raise an alert if it persists (if the file age is old enough):
if old files keep existing and nothing deletes them, this leads to a full disk and eventually the inability to make backups or keep postgres running.

"it was uploaded but not deleted" is also a bug that should raise an alert if it persists (if the file age is old enough): if old files keep existing and nothing deletes them, this leads to a full disk and eventually the inability to make backups or keep postgres running.

But it's entirely possible that some other process cleans that up, and that such logic is not time-based but size-based - e.g. when the disk starts filling up, older files are deleted. And if the disk is big enough, they may never get deleted. I don't think that making too many assumptions on how pghoard is run (even because it can run outside of Aiven's infrastructure, being an OSS project) is wise, we can encounter other, different, issues.
Incidentally, my first idea was to create a simpler metric, something more similar to what you said (I was thinking about something like "send the oldest time for what I see in compression queue for the last X minutes"), but I ultimately think it wasn't good enough; I wanted to create a metric that has an high SnR.
Anyway, I think this deserves its own ticket. It's not a quick & dirty commit. So, I'm closing this now (but everyone, feel free to comment further)

Did we consider not changing anything in the code and just adding immediate escalation when the existing compressor_run_critical metric data point is emitted? Should be rare case and possibly not worth anything fancier until we've gathered more information on when this happens exactly and can possibly change the code to somehow deal with the situation in more automatic manner.

@rikonen we're actually going to start tracking compressor_run_critical in a dashboard (it's not actually shown anywhere right now), and then we'll decide what to do when we see actual data. Triggering an alarm is possible, but we're unsure what the resolution for that alarm would be


Issues with explicitely ack() messages remaining in queue

Environment details

OS: Mac OS Sonoma
Node.js version: 18.18.1
npm version: 9.8.1
@google-cloud/pubsub version: 4.0.7

Steps to reproduce

I'm using the library locally to develop and I have a development environnement on PubSub.
I have a Post endpoint n my app that emits one event myEvent to a given topic foo on PubSub.
For this topic I have a bar subscription that is supposed to change a field in my database
When the DB operation is done, I call message.ack() and then the function finishes.
I kill the app locally and relaunch it, re-subscribing to the topic
I receive the same message even though it was already acked in the previous session
Messages are never acked and keep piling up in the Pubsub dashboard

There is likely something that I'm missing, I don't have exactly once delivery enabled but I don't understand why a message that I explicitely ack remains in the queue and is sent again when I add my subscription again to the topic by relaunching the app.
My PubSub options:
import { PubSub } from "@google-cloud/pubsub";

export const getDefaultSubscriptionOptions = (): Parameters<PubSub["createSubscription"]>[2] => ({
    ackDeadlineSeconds: 60,
    retryPolicy: {
        maximumBackoff: {
            seconds: 180,
        },
        minimumBackoff: {
            seconds: 60,
        },
    },
    flowControl: {
        maxMessages: 1,
    },
    deadLetterPolicy: {
        deadLetterTopic: `projects/dev/topics/deadletter`,
        maxDeliveryAttempts: 5,
    },
});

Thanks!

@PILLOWPET Did you try await sub.close() on your Subscription object before shutting down? It's likely the ack is queued but not sent in time.

Hello @feywind,
I work with @PILLOWPET  on the same project and I managed to narrow down the issue. Even without shutting down the app we can see that the message is not removed from the subscription. Actually in our tests we only shut down the app to make sure that all the messages in the queue are pulled again.

Hello @feywind,
I work with @PILLOWPET on the same project and I managed to narrow down the issue. Even without shutting down the app we can see that the message is not removed from the subscription. Actually in our tests we only shut down the app to make sure that all the messages in the queue are pulled again.
I noticed that this issue occurs depending on the number of active subscriptions we have in our app (which is hosted on GCP) , if we have a number of 20 or above active subscriptions in our app the acknowledgment does not work as expected, if we have a number 19 or under active subscriptions it works fine. It may be also worth to mention that we currently for this app have one subscription - one topic.

Looks like this: #1705  and this behaviour is also mentioned here https://cloud.google.com/nodejs/docs/reference/pubsub/latest/pubsub/subscription-class
We will try to implement a fix using the links mentioned above to see if it fixes our issue but if that is the case I believe that the library should raise a warning or an error when the maximum number of stream is reached or exeeded.

I agree that that's annoying. I'll have to check with the other language authors, because we're trying to keep them more in sync going forward, but it seems like a reasonable request.

Closed in favour of https://github.com/googleapis/nodejs-pubsub/issues/1917


Document integration framework - charts

https://github.com/rancher/rancher/issues/28630
Point of contact: Brenda

Closing because it's an internal tool. No need to document it


[BUG] Could not pass event AsyncPlayerChatEvent

What is the bug?
I'm getting a error from BetterTeams randomly on the console.
Expected Behaviour
BetterTeams works fine, but it gives an error for some reason.
How to Reproduce
Not sure how really. We use Bungeecord I guess and the error is randomly sent sometimes. I can't figure out what it means.
Error message
Could not pass event AsyncPlayerChatEvent to BetterTeams v4.6.4 java.lang.IllegalStateException: Player *RUST1974 is registered to be in a team, yet has no playerdata associated with that team         at com.booksaw.betterTeams.events.ChatManagement.onChat(ChatManagement.java:51) ~[BetterTeams.jar:?]         at com.destroystokyo.paper.event.executor.asm.generated.GeneratedEventExecutor416.execute(Unknown Source) ~[?:?]         at org.bukkit.plugin.EventExecutor.lambda$create$1(EventExecutor.java:75) ~[paper-api-1.19.2-R0.1-SNAPSHOT.jar:?]         at co.aikar.timings.TimedEventExecutor.execute(TimedEventExecutor.java:76) ~[paper-api-1.19.2-R0.1-SNAPSHOT.jar:git-Paper-260]         at org.bukkit.plugin.RegisteredListener.callEvent(RegisteredListener.java:70) ~[paper-api-1.19.2-R0.1-SNAPSHOT.jar:?]         at org.bukkit.plugin.SimplePluginManager.callEvent(SimplePluginManager.java:670) ~[paper-api-1.19.2-R0.1-SNAPSHOT.jar:?]         at io.papermc.paper.adventure.ChatProcessor.post(ChatProcessor.java:381) ~[paper-1.19.2.jar:git-Paper-260]         at io.papermc.paper.adventure.ChatProcessor.process(ChatProcessor.java:96) ~[paper-1.19.2.jar:git-Paper-260]         at net.minecraft.server.network.ServerGamePacketListenerImpl.chat(ServerGamePacketListenerImpl.java:2403) ~[?:?]         at jdk.internal.reflect.GeneratedMethodAccessor154.invoke(Unknown Source) ~[?:?]         at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:?]         at java.lang.reflect.Method.invoke(Method.java:568) ~[?:?]         at com.loohp.interactivechat.utils.PlayerUtils.chatAsPlayer(PlayerUtils.java:130) ~[InteractiveChat-<IP_ADDRESS>.jar:?]         at com.loohp.interactivechat.listeners.RedispatchSignedPacket$1.lambda$onPacketReceiving$4(RedispatchSignedPacket.java:92) ~[InteractiveChat-<IP_ADDRESS>.jar:?]         at org.bukkit.craftbukkit.v1_19_R1.scheduler.CraftTask.run(CraftTask.java:101) ~[paper-1.19.2.jar:git-Paper-260]         at org.bukkit.craftbukkit.v1_19_R1.scheduler.CraftAsyncTask.run(CraftAsyncTask.java:57) ~[paper-1.19.2.jar:git-Paper-260]         at com.destroystokyo.paper.ServerSchedulerReportingWrapper.run(ServerSchedulerReportingWrapper.java:22) ~[paper-1.19.2.jar:?]         at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) ~[?:?]         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) ~[?:?]         at java.lang.Thread.run(Thread.java:833) ~[?:?]
Output of /teama version
[14:12:05 INFO]: [Teams] Storage Method: com.booksaw.betterTeams.team.storage.storageManager.SeparatedYamlStorageManager
[14:12:05 INFO]: [Teams] Minecraft Version: git-Paper-260 (MC: 1.19.2)
[14:12:05 INFO]: [Teams] Language Selected: messages
[14:12:05 INFO]: [Teams] Current plugin version: 4.6.4
Additional Information
No response

Set rebuildLookups to true in config.yml and restart your server, let me know if the issue persists once you have done that.

This issue is being closed for inactivity. If you are still having problems feel free to open a new issue linking this one, make sure you answer any questions asked in the new issue.


Create a Flintrock repository to host Hadoop and Spark releases

Since its creation, Flintrock has sourced Spark releases from s3://spark-related-packages, an S3 bucket hosted by the AMPLab and kept up-to-date by the Apache Spark project. As of Spark 2.2.1, the Spark committers have confirmed that this bucket will no longer receive updates (alternate reference).
This is a big change for Flintrock's out-of-the-box experience. Users today can configure Flintrock to download Spark from a custom location via the --spark-download-source option, but by default Flintrock downloads Spark from s3://spark-related-packages. This gives users a fast, reliable, and convenient source of Spark releases to use with Flintrock without users needing to do any work. Now that the bucket is being retired, we're stuck with the Apache mirror network as a default download source. Flintrock already uses Apache mirrors as a default source for Hadoop, and as Flintrock users know, they are slow and often unreliable (#66).
To preserve a strong out-of-the-box experience for Flintrock, I have begrudgingly decided to maintain a repository of Spark and Hadoop releases on S3 for use with Flintrock. I am loath to maintain new infrastructure, but in the absence of a fast CDN hosting public Spark and Hadoop releases, I think this is the only way.
To summarize the changes I plan to make:

How Flintrock works today:

By default, Flintrock downloads Spark from s3://spark-related-packages.
By default, Flintrock downloads Hadoop from the Apache mirror network.
Users can customize where Flintrock downloads Spark and Hadoop from using --spark-download-source and --hdfs-download-source.

How Flintrock will work after the change proposed here is complete:

By default, Flintrock will download both Spark and Hadoop from an S3 bucket maintained by me / the Flintrock project.

The bucket will be a Requester Pays bucket, meaning that users will pay the cost of data transfer from S3 to their Flintrock clusters on EC2.
The Flintrock project will only maintain a rolling window of select, recent releases of Spark and Hadoop in this repository.

As before, users can continue to customize where Flintrock downloads Spark and Hadoop from.

When this change is complete, Flintrock will no longer depend on external sources for Spark and Hadoop, and clusters that use Hadoop will launch faster by default since they will now download Hadoop from S3 as opposed to the Apache mirror network.
Thank you to the AMPLab and to the Apache Spark project for graciously hosting Spark releases on S3 for as long as they did (and footing the bill!), and to Matei for the suggestion to use a Requester Pays bucket with Flintrock.

Working with Requester Pays S3 buckets turned out to be more difficult than expected. Using Requester Pays means all requests need to be authenticated and authorized through IAM. This implies a number of things:

On the bucket owner side: The ACL on each object in a Requester Pays bucket needs to be set to public-read or authenticated-read, otherwise no-one other than the bucket owner will be able to read those objects. It's not enough to just make the bucket a Requester Pays bucket.
On the bucket reader side: The person trying to access objects needs to be given explicit permission to access those objects. So if I'm offering Spark and Hadoop releases in an S3 bucket called flintrock-resources, then any Flintrock user who wants to download from this bucket needs to explicitly grant themselves access to the flintrock-resources bucket, either specifically, or via some wildcard. This is regardless of the fact that object ACLs are set to public-read or authenticated-read.
For Flintrock itself: When Flintrock downloads Spark and Hadoop from this Requester Pays bucket, it can't do it anymore using plain curl or wget. We would need to a) use the AWS CLI along with the --request-payer requester option, and b) the instances downloading from the bucket need credentials to be available, either via an attached IAM role or as an access key and secret.

To make this all work without requiring users to make a bunch of manual changes related to IAM, Flintrock would need to do some extra work whenever a user tries to launch a cluster without providing explicit download sources for Spark and Hadoop:

Create and maintain an IAM policy that grants access to the Flintrock resources bucket hosting Spark and Hadoop releases.
Create and maintain an IAM role that Flintrock instances get assigned by default. The role has the aforementioned policy attached.
Add the aforementioned policy to any user-provided IAM role that the user wants to launch their Flintrock cluster with.

It's a fair bit of work, unfortunately. And this is on top of needing to maintain the repository of Spark and Hadoop releases itself.
The alternative to doing all this is to stick to the Apache mirror network as a default download source for both Hadoop and Spark. Flintrock can provide a warning about the performance and reliability of Apache mirrors and simply leave it up to users to setup their own alternate download sources if they choose.
For the sake of expediency, I'm now thinking of pursuing this less exciting strategy first. It will enable Flintrock users to launch Spark 2.3 clusters and it takes much less work. Once that's in place, I can revisit this grander strategy of maintaining a repository of Spark and Hadoop releases.
If you're reading along and have some questions or suggestions, please chime in. I wish there was a better solution. Short of Apache hosting Spark and Hadoop releases on a fast and modern CDN, this is the best I could come up with.

I have constant failures to launch a cluster. With 2 slaves, I get an ssh timeout on one or more machines. Unfortunately the machines are actually created and so end up costing me--even if I tell flintrock to destroy them.
Does this intermittent timeout have something to do with the speed of Apache mirrors? This issue is hte only one mentioned with the --debug switch. BTW I use the Ubuntu AMI and "ubuntu" user.

Please try launching clusters with Amazon Linux. Flintrock doesn't support Ubuntu (#95). If you still have problems, please open a separate issue with the details of what you're seeing.

Doing so now, but still get timeouts.
Maclaurin:govtribe pat$ flintrock --config govtribe-poc.yaml --debug launch govtribe-poc
2019-01-02 17:06:14,954 - flintrock.flintrock - WARNING - Warning: Downloading Spark from an Apache mirror. Apache mirrors are often slow and unreliable, and typically only serve the most recent releases. We strongly recommend you specify a custom download source. For more background on this issue, please see: https://github.com/nchammas/flintrock/issues/238
2019-01-02 17:06:24,773 - flintrock.ec2       - INFO  - Launching 3 instances...
2019-01-02 17:06:38,275 - flintrock.ec2       - DEBUG - 3 instances not in state 'running': 'i-021a99dfe4b144639', 'i-097f5ce577f2bd1d3', 'i-05924e8c036bf6046', ...
2019-01-02 17:06:44,184 - flintrock.ssh       - DEBUG - [<IP_ADDRESS>] SSH exception: [Errno None] Unable to connect to port 22 on <IP_ADDRESS>
2019-01-02 17:06:45,083 - flintrock.ssh       - DEBUG - [<IP_ADDRESS>] SSH timeout.
2019-01-02 17:06:45,084 - flintrock.ssh       - DEBUG - [<IP_ADDRESS>] SSH timeout.
2019-01-02 17:06:49,948 - flintrock.ssh       - INFO  - [<IP_ADDRESS>] SSH online.
2019-01-02 17:06:50,182 - flintrock.ssh       - DEBUG - [<IP_ADDRESS>] SSH exception: [Errno None] Unable to connect to port 22 on <IP_ADDRESS>
2019-01-02 17:06:51,007 - flintrock.ssh       - INFO  - [<IP_ADDRESS>] SSH online.
2019-01-02 17:06:51,229 - flintrock.core      - INFO  - [<IP_ADDRESS>] Configuring ephemeral storage...
2019-01-02 17:06:52,208 - flintrock.core      - INFO  - [<IP_ADDRESS>] Configuring ephemeral storage...
2019-01-02 17:06:52,536 - flintrock.core      - INFO  - [<IP_ADDRESS>] Installing Java 1.8...
2019-01-02 17:06:53,559 - flintrock.core      - INFO  - [<IP_ADDRESS>] Installing Java 1.8...
2019-01-02 17:06:55,993 - flintrock.ssh       - INFO  - [<IP_ADDRESS>] SSH online.
2019-01-02 17:06:57,484 - flintrock.core      - INFO  - [<IP_ADDRESS>] Configuring ephemeral storage...
2019-01-02 17:06:58,788 - flintrock.core      - INFO  - [<IP_ADDRESS>] Installing Java 1.8...
2019-01-02 17:07:05,087 - flintrock.services  - INFO  - [<IP_ADDRESS>] Installing Spark...
2019-01-02 17:07:08,206 - flintrock.services  - INFO  - [<IP_ADDRESS>] Installing Spark...
2019-01-02 17:07:09,574 - flintrock.services  - INFO  - [<IP_ADDRESS>] Installing Spark...
w2019-01-02 17:07:22,939 - flintrock.services  - INFO  - [<IP_ADDRESS>] Configuring Spark master...
^R
2019-01-02 17:08:55,996 - flintrock.services  - DEBUG - Timed out waiting for Spark master to come up. Trying again...
2019-01-02 17:10:28,973 - flintrock.services  - DEBUG - Timed out waiting for Spark master to come up. Trying again...
2019-01-02 17:12:02,133 - flintrock.services  - DEBUG - Timed out waiting for Spark master to come up.
Do you want to terminate the 3 instances created by this operation? [Y/n]: Y
Terminating instances...
Traceback (most recent call last):
  File "/usr/local/bin/flintrock", line 11, in <module>
    load_entry_point('Flintrock==0.10.0', 'console_scripts', 'flintrock')()
  File "/usr/local/Cellar/flintrock/0.10.0/libexec/lib/python3.7/site-packages/flintrock/flintrock.py", line 1185, in main
    cli(obj={})
  File "/usr/local/Cellar/flintrock/0.10.0/libexec/lib/python3.7/site-packages/click/core.py", line 722, in __call__
    return self.main(*args, **kwargs)
  File "/usr/local/Cellar/flintrock/0.10.0/libexec/lib/python3.7/site-packages/click/core.py", line 697, in main
    rv = self.invoke(ctx)
  File "/usr/local/Cellar/flintrock/0.10.0/libexec/lib/python3.7/site-packages/click/core.py", line 1066, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/usr/local/Cellar/flintrock/0.10.0/libexec/lib/python3.7/site-packages/click/core.py", line 895, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/usr/local/Cellar/flintrock/0.10.0/libexec/lib/python3.7/site-packages/click/core.py", line 535, in invoke
    return callback(*args, **kwargs)
  File "/usr/local/Cellar/flintrock/0.10.0/libexec/lib/python3.7/site-packages/click/decorators.py", line 17, in new_func
    return f(get_current_context(), *args, **kwargs)
  File "/usr/local/Cellar/flintrock/0.10.0/libexec/lib/python3.7/site-packages/flintrock/flintrock.py", line 456, in launch
    tags=ec2_tags)
  File "/usr/local/Cellar/flintrock/0.10.0/libexec/lib/python3.7/site-packages/flintrock/ec2.py", line 53, in wrapper
    res = func(*args, **kwargs)
  File "/usr/local/Cellar/flintrock/0.10.0/libexec/lib/python3.7/site-packages/flintrock/ec2.py", line 955, in launch
    identity_file=identity_file)
  File "/usr/local/Cellar/flintrock/0.10.0/libexec/lib/python3.7/site-packages/flintrock/core.py", line 651, in provision_cluster
    cluster=cluster)
  File "/usr/local/Cellar/flintrock/0.10.0/libexec/lib/python3.7/site-packages/flintrock/services.py", line 407, in configure_master
    raise Exception("Timed out waiting for Spark master to come up.")
Exception: Timed out waiting for Spark master to come up.
Maclaurin:govtribe pat$

In this case there were 2 slaves and one connected to the master. I was able to see the GUI with one "worker"


Include completion files instead of generating them on the fly

Describe the problem you are trying to solve
I am working on packaging rustup for openSUSE and generating completion files on the fly cannot guarantee reproducible builds (because the generated completion files could differ).
Describe the solution you'd like
I would like that the completion files are included in the source, so they are always the same and are also easily packaged. This is the usual way to do it. Having to redirect the output of commands in a package build system is somewhat weird and unusual.
Notes
The package: https://build.opensuse.org/package/show/home:dmarcoux/rustup.rs

The way that rustup does it is apparently the same way npm completion does it and the way cargo wants to do it too: https://github.com/rust-lang/cargo/issues/6645
Rather than revert back to flat files, could can we continue to generate them in a way that guarantees reproducibility?  How does packaging on openSUSE deal with other resources being generated on the fly and reproducibility concerns?

From the reproducible builds perspective, it is OK to generate files on the fly as long as this happens in a deterministic way. From echo foo > output to gcc -o output $input it is all fine.
https://github.com/bmwiedemann/theunreproduciblepackage lists 10 known ways of introducing non-determinism. I'll test and report back if any of them applies here - and which.

Test done: all outputs of the home:dmarcoux/rustup.rs package are reproducible.

Thank you very much @bmwiedemann.
I'm closing this issue.

Excellent news.  Thank you, both.


Min-height is not working correctly

Min-height is not working correctly when applying dReadMore to an element which contains more then one <p> tag.
Is there a way to solve this?

hi, is there an example?

check out the new version 2.1.5

Please see this example:
https://codepen.io/meteorit/pen/NWYJajK

I have an idea where the tags and text inside will work, but with an exception. Only tags of the type , , ,  and so on should be inside.


[Win] Change text and OS version in pre-install form

typo
third paragraph not needed..
askat [1:22 PM]

Is x64 => Processor architecture: x64
OS version => OS Windows version
ATTENTION => Attention!
Virtual Box => VirtualBox
... and restart windows => and restart Windows
also, seems the phrase "Press Next button to proceed" is redundant. there is already similar one with green color (left from the button).

changed, form not needed now


Drupal Console task fails since update to drupalconsole.com

drupalconsole.com updated today, which is probably responsible for the following error on vagrant up:
==> downfalldev: TASK: [geerlingguy.drupal-console | Install Drupal Console into the current directory.] ***
==> downfalldev: changed: [localhost]
==> downfalldev:
==> downfalldev: TASK: [geerlingguy.drupal-console | Move Drupal Console into globally-accessible location.] ***
==> downfalldev: failed: [localhost] => {"changed": true, "cmd": "mv console.phar /usr/local/bin/drupal", "delta": "0:00:00.002762", "end": "2015-12-
==> downfalldev: 07 06:58:12.193093", "rc": 1, "start": "2015-12-07 06:58:12.190331", "warnings": []}
==> downfalldev: stderr: mv: cannot stat ���console.phar���: No such file or directory
==> downfalldev:
==> downfalldev: FATAL: all hosts have already failed -- aborting

I think this may be a critical issue since there is no way to disable Drupal Console through config.yml.

I have a similar issue:
TASK: [geerlingguy.drupal-console | Update Drupal Console to latest version (if configured).] ***
failed: [drupalvm] => {"changed": false, "cmd": "php /usr/local/bin/drupal self-update", "delta": "0:00:00.628784", "end": "2015-12-07 17:03:47.425685", "rc": 1, "start": "2015-12-07 17:03:46.796901", "stdout_lines": [], "warnings": []}
stderr:

  [Herrera\Json\Exception\FileException]
  file_get_contents(http://drupalconsole.com/manifest.json): failed to open stream: HTTP request failed! HTTP/1.1 404 Not Found

self-update

FATAL: all hosts have already failed -- aborting

I'm going to take a look at this today, asap.
I've already committed a fix for https://github.com/geerlingguy/drupal-vm/issues/278, so technically, if you leave your config.yml file the same and re-provision, everything should work now. If you want Drupal Console installed and updated, you need to add drupalconsole to the list of installed extras.

@geerlingguy: This is related to our site update, I am working on have it fixed.

Okay, thanks!

@geerlingguy: Must by fixed now.

@illepic  @robdecker this issue is fixed now, may you try again, to confirm is working for you?

Confirmed to be working. All drupal-console related tasks are completing properly.

@jmolivas this is my output from a fresh clone of this repo about 30 minutes ago:
==> downfalldev:
==> downfalldev: TASK: [geerlingguy.drupal-console | Ensure curl is installed (Debian).] *******
==> downfalldev: ok: [localhost]
==> downfalldev:
==> downfalldev: TASK: [geerlingguy.drupal-console | Install Drupal Console into the current directory.] ***
==> downfalldev: failed: [localhost] => {"changed": true, "cmd": "curl -LSs http://drupalconsole.com/installer | php", "delta": "0:00:02.695129", "end": "2015-12-07 20:56:29.328773", "rc": 255, "start": "2015-12-07 20:56:26.633644", "war
==> downfalldev: nings": ["Consider using get_url module rather than running curl"]}
==> downfalldev: stderr: PHP Warning:  Phar::mapPhar(-): failed to open stream: No such file or directory in - on line 9
==> downfalldev: PHP Fatal error:  Uncaught PharException: unable to open phar for reading "-" in -:9
==> downfalldev: Stack trace:
==> downfalldev: #0 -(9): Phar::mapPhar('console.phar')
==> downfalldev: #1 {main}
==> downfalldev:   thrown in - on line 9
==> downfalldev: stdout: #!/usr/bin/env php
==> downfalldev:
==> downfalldev: FATAL: all hosts have already failed -- aborting
==> downfalldev:
==> downfalldev: PLAY RECAP ********************************************************************
==> downfalldev:            to retry, use: --limit @/root/playbook.retry
==> downfalldev:
==> downfalldev: localhost                  : ok=84   changed=37   unreachable=0    failed=1

Doesn't look like it was successful.

@jmolivas I can confirm that I am getting the same error as @illepic above just moments ago. (on a different project).

This is related to the installer instructions, new installer instructions are => https://github.com/geerlingguy/drupal-vm/issues/335

Closing in favor of #335 — I'll take a look at this later. Issues may need to be filed against the upstream geerlingguy.drupal-console role instead.


Genetic optimization

Created this issue for tracking the genetic optimization
https://github.com/chrisdk2015/LeanOptimization
It uses the GAF framework and is currently for running on the command line.
Howto parallize this would be nice to know. Maybe one needs to change the GAF framework.

@chrisdk2015
I got the genetic algorithm running without blurring by on the console.   However, after 1723 trials, it blows up my Visual Studio.  I mean VS just quits with no notice or anything.  It has happened twice, once with console blur and once without.  It seems to happen in the same place but I cannot catch an Exception.
I was wondering how many trials were needed to resolve the genetic algorithm.  And also did your crash like that.  Of course, if you were waiting 40 seconds between trials, it would have taken all night.  My current version did the 1723 trials in 1:09:22 or 2-3 seconds per trial and only shows the 1 line per trial in the console.
I copied ConsoleResultsHandler and modified it into OptimizationResutsHandler.  I also commented out line 62 in JobQueue because it was Log.Trace("dodah") before the Log.Handler was set to a FileLogHandler.
Here is a link to a dropbox folder with the log.txt and log.csv files for the 1723 trials.
https://www.dropbox.com/sh/zm19bgmuo1t5os0/AACt4pHp6zbE1KNmWxnhlO7wa?dl=0
I am pushing the complete project to https://github.com/bizcad/LeanOpto
On line 89 of Program, I set

            Log.LogHandler = (ILogHandler)new FileLogHandler();
            Log.DebuggingEnabled = true;
            Log.DebuggingLevel = 2;

so that Log output is only sent to a file.  Then I replace all the Console.WriteLines (except for 2) to Log.Trace, Debug or Error.
I also commented the parts that refer to writing chart files.  We do not need them.
Nick

@bizcad
I think there is a memory leak somewhere.
At least here when I run start running it the memory usage keeps going up.
Maybe you can put the memory usage in the log file to see if that is the reason.
I tried to do a profiling here with mono but I just get segfaults so it is of no help. Maybe you could profile it in VS? I think the profile there is better.
With the OptimizationResultHandler it goes a bit faster.
For the termination criteria you could use the following
private static double oldFitness = Double.NaN;

public static bool Terminate(Population population,
			int currentGeneration, long currentEvaluation)
		{
			var fittest = population.GetTop(1)[0];
			if (oldFitness != Double.NaN) {
				var diff = System.Math.Abs (fittest.Fitness - oldFitness);
				if (diff < 1E-02)
					return true;
			}
			oldFitness = fittest.Fitness;
			return false;
			//return currentGeneration > 10;
		}

instead of using the generation number to stop.
Also to avoid running that many times the number of chromosomes and genes per chromosome could be lowered
//create the chromosomes
			for (var p = 0; p < 10; p++)
			{

				var chromosome = new Chromosome();
				for (int i = 0; i < 10; i++) {
					ConfigVars v = new ConfigVars ();
					v.vars ["EMA_VAR1"] = RandomNumberBetweenInt (0, 20);
					v.vars ["EMA_VAR2"] = RandomNumberBetweenInt (0, 100);

					chromosome.Genes.Add (new Gene (v));
				}
				chromosome.Genes.ShuffleFast();
				population.Solutions.Add(chromosome);
			}

The question is how big the default population should be? I don't know.
By the way the code in my github has a solution for multiple variables using the ConfigVars class.

@chrisdk2015 I am not experienced with the Microsoft profiler, but I tried running it.  The data file filled up what was left of my C:\ drive.  :o(  I deleted the file and ran again stopping after about 200 iterations.  The resulting report did not tell me anything useful.  I dumped the profiler and ran the Program.cs.
I watched the Task manager for memory usage and it did not grow for 2.5 hours.  So I do not believe there is a memory leak.
  I changed the {1} to {0}.  Now I need to run it again to get to the stop point.  It is taking about 2.5 seconds per iteration so it is a 2.5 hour wait.
After I get there I will try integrating your new code.  It will probably be tomorrow before I have something.
Nick

Been trying to get this running the past two days, I keep crashing on line 356 in Program.cs:
var res = (double)rc.Run (val);
On the terminal, I get this error:

20151103 08:52:34 ERROR:: Loader.TryCreateILAlgorithm(2): Sequence contains no matching element
20151103 08:52:34 Trace:: Initializing...
20151103 08:52:34 ERROR:: Engine.Main(): Error running algorithm: Object reference not set to an instance of an object >>   at QuantConnect.Lean.Engine.Results.ConsoleResultHandler.RuntimeError (System.String message, System.String stacktrace) [0x0000f] in /home/gene/Downloads/Lean/Engine/Results/ConsoleResultHandler.cs:248
at QuantConnect.Lean.Engine.Engine.Run (QuantConnect.Packets.AlgorithmNodePacket job, System.String assemblyPath) [0x00305] in /home/gene/Downloads/Lean/Engine/Engine.cs:249

In my IDE (mono-develop), I get:

System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.

20151103 08:52:34 ERROR:: Loader.TryCreateILAlgorithm(2): Sequence contains
no matching element
This message sounds like the Loader was unable to find the algorithm
specified in configuration.
The function _multipleTypeNameResolverFunction gets invoked with all type
names resolved from the assembly to select a single algorithm type to
instantiate. In many places in the code, the Loader is initialized to force
exactly one match on the type name via the LINQ .Single() call.
Check config.json 'algorithm-type-name' matches properly. Also, try
stepping through the invocation of the '_multipleTypeNameResolverFunction'
function from within the TryCreateILAlgorithm method in the Loader class.
-Michael
On Tue, Nov 3, 2015 at 11:59 AM, gururise<EMAIL_ADDRESS>wrote:

Been trying to get this running the past two days, I keep crashing on line
356 in Program.cs:
var res = (double)rc.Run (val);
On the terminal, I get this error:
20151103 08:52:34 ERROR:: Loader.TryCreateILAlgorithm(2): Sequence
contains no matching element
20151103 08:52:34 Trace:: Initializing...
20151103 08:52:34 ERROR:: Engine.Main(): Error running algorithm: Object
reference not set to an instance of an object >> at
QuantConnect.Lean.Engine.Results.ConsoleResultHandler.RuntimeError
(System.String message, System.String stacktrace) [0x0000f] in
/home/gene/Downloads/Lean/Engine/Results/ConsoleResultHandler.cs:248
at QuantConnect.Lean.Engine.Engine.Run
(QuantConnect.Packets.AlgorithmNodePacket job, System.String assemblyPath)
[0x00305] in /home/gene/Downloads/Lean/Engine/Engine.cs:249
In my IDE (mono-develop), I get:
System.Collections.Generic.KeyNotFoundException: The given key was not
present in the dictionary.
—
Reply to this email directly or view it on GitHub
https://github.com/QuantConnect/Lean/issues/190#issuecomment-153417254.

@gururise If you copied the code from @chrisdk2015 Optimization project on github, my guess is your problem is on line 154 of Program.cs
154 			_resultshandler = new DesktopResultHandler ();
Try changing all the DesktopResultHandler to ConsoleResultHandler.  DesktopResultHandler expects a Desktop application to write results to.  In the console application there is no desktop.
Also take a look at my take on a complete solution including Lean and all it's sub-projects.  This link is also in my reply above.  I changed DesktopResultHandler in three places to an OptimizationResultHandler with some commented lines next for ConsoleResultHandler.  If you want to see the results flash by in the console comment out the OptimizationResultsHandler and uncomment the ConsoleResultsHandler.
The code for the OptimizationResultsHandler is in the Engine\Results folder and is based upon ConsoleResultsHandler.
I run in Windows/VisualStudio, so I place a breakpoint about line 75 of Program.cs at the top of the LaunchLean function and step from there to find my error.

            Config.Set("environment", "backtesting");
            string algorithm = "EMATest";       // put this algorithm is QuantConnect.Algorithm.CSharp folder
            Config.Set("algorithm-type-name", algorithm);

I hope this helps.
Bizcad aka Nick Stein

This is a fairly old ticket and it appears work has stalled. I have recently overhauled the LeanOptimization project here:
https://github.com/jameschch/LeanOptimization
Anyone still interested in this functionality please feel free to provide feedback, open issues etc.

Just and update: Lean supports optimization since some time now https://github.com/QuantConnect/Lean/pull/4923 , genetic optimizer is not yet implemented though


fix: Restructure the project and fix some bugs

Improve the usage of development mode
Fix compilation warnings
Remove redundant docusaurus built-in files
Mark documents in default locale as placeholder so we don't need to update them
Fix some i18n and image display issues

Please DO NOT merge this PR before https://github.com/higress-group/higress-group.github.io/pull/98.


Trying to get started

I'm trying to get this installed and running, but having some issues.  My Linux is good, but not great ;)
When I run run_tracker.sh I'm getting:
will crop
Traceback (most recent call last):
File "/home/pi/OverPutney-main/tracker.py", line 141, in
display = datasource.get_map_source()
File "/home/pi/OverPutney-main/datasource.py", line 33, in get_map_source
return get_driver()'map'
File "/home/pi/OverPutney-main/screenshot.py", line 66, in init
self.loadmap()
File "/home/pi/OverPutney-main/screenshot.py", line 111, in loadmap
browser = webdriver.Chrome('/usr/bin/chromedriver', desired_capabilities=capabilities, options=options)
File "/usr/local/lib/python3.9/dist-packages/selenium/webdriver/chrome/webdriver.py", line 70, in init
super(WebDriver, self).init(DesiredCapabilities.CHROME['browserName'], "goog",
File "/usr/local/lib/python3.9/dist-packages/selenium/webdriver/chromium/webdriver.py", line 93, in init
RemoteWebDriver.init(
File "/usr/local/lib/python3.9/dist-packages/selenium/webdriver/remote/webdriver.py", line 269, in init
self.start_session(capabilities, browser_profile)
File "/usr/local/lib/python3.9/dist-packages/selenium/webdriver/remote/webdriver.py", line 360, in start_session
response = self.execute(Command.NEW_SESSION, parameters)
File "/usr/local/lib/python3.9/dist-packages/selenium/webdriver/remote/webdriver.py", line 425, in execute
self.error_handler.check_response(response)
File "/usr/local/lib/python3.9/dist-packages/selenium/webdriver/remote/errorhandler.py", line 247, in check_response
raise exception_class(message, screen, stacktrace)
selenium.common.exceptions.SessionNotCreatedException: Message: session not created: This version of ChromeDriver only supports Chrome version 98
Current browser version is 95.0.4638.78 with binary path /usr/bin/chromium-browser
Stacktrace:
#0 0x0055855ea568
#1 0x00558538263c
#2 0x0055853a3e58
#3 0x0055853a08c0
#4 0x00558539d9a0
#5 0x0055853cf064
#6 0x0055853a6660
#7 0x005585617edc
#8 0x00558562c470
#9 0x0055856199cc
#10 0x00558562cc94
#11 0x00558560e144
#12 0x005585644df0
#13 0x005585644f58
#14 0x00558565d07c
#15 0x007f839e2628
#16 0x007f8350f01c

Your webdriver version needs to match the version of the browser.
selenium.common.exceptions.SessionNotCreatedException: Message: session not created: This version of ChromeDriver only supports Chrome version 98
Current browser version is 95.0.4638.78 with binary path /usr/bin/chromium-browser

This is letting you know that you're using v98 of the webdriver with v95 of the browser. Update both of those to the current release and you should be good to go.


ISPN-6954 Stabilize LiveRunningTest.liveRun

https://issues.jboss.org/browse/ISPN-6954
@belaban @Sanne - Hey! I'm trying to stabilize LiveRunningTest. As you can see the test uses loopback and up to 5 slaves. Unfortunately I didn't manage to reproduce the failure locally but I think JGroups were operating on very low timeout values. I tried to make them a bit higher and use more defaults. Could you please have a look if proposed changes make sense? Thanks!

The config change doesn't really change anything :-) So +1 from me...

Running some more tests: http://ci.infinispan.org/viewType.html?buildTypeId=bt9&branch_Infinispan=4514%2Fhead&tab=buildTypeStatusDiv

@slaskawi Do you have TRACE logs of the failure? Sometimes timeouts happens because something went wrong in the receiver side of the RPC

@gustavonalle There's only one failure but probably not very helpful: http://ci.infinispan.org/viewLog.html?tab=buildLog&logTab=tree&filter=debug&expand=all&buildId=40101#_focus=13093

@gustavonalle @Sanne - Any other comments?

This test sometimes fails with other reasons than timeout:
junit.framework.AssertionFailedError: expected:<12> but was:<11> at junit.framework.Assert.fail(Assert.java:57) at junit.framework.Assert.failNotEquals(Assert.java:329)

liveRun(org.infinispan.hibernate.search.LiveRunningTest)  Time elapsed: 8.726 sec  <<< ERROR!
org.hibernate.search.exception.SearchException: Unable to reopen IndexReader

@gustavonalle Could you please share a link to CI job?

http://ci.infinispan.org/viewLog.html?buildId=38317&tab=buildResultsDiv&buildTypeId=Infinispan_MasterHotspotJdk8&guest=1#testNameId-6124278935670372534&guest=1

To reproduce it locally, run in a loop:
taskset -c 0,1 mvn -Dtest=LiveRunningTest test

Any luck reproducing the failure @slaskawi ?

Unfortunately not, but @gustavonalle is right... you can reproduce it by running taskset -c 0,1 mvn -Dtest=LiveRunningTest test

I think I found the root cause... the order of closing nodes was wrong..
Now we stop all slaves and then the master. After this change, it behaves really stable on my local environment.

@slaskawi If it doesn't work properly that's the fault of Infinispan, not the fault of the test. Otherwise we'd have to say in the docs that we don't support stopping the master node before all the other nodes, which kind of defeats the point of using Infinispan.

I guess you're right @danberindei...
@gustavonalle, @Sanne - may I ask you to also have a look into this issue? Maybe I didn't diagnose it properly (I'm unfamiliar with this code, so I can not really tell if the test or the production code needs to be fixed)?

This is not a proper fix... closing.


mz.auto.Tuner , Validator not satifised.

Describe the Question
Please provide a clear and concise description of what the question is.
I am on matchzoo-py1.1.1 and when I try to play with the codemz.auto.Tuner , i get an error when trying to tune the model.
Describe your attempts

[x] I walked through the tutorials
please provide model_tuning tutorial for match-py ,when i use mz.auto.Tuner() to tune my model,i get an error as follow:

tuner = mz.auto.Tuner(
params=model.params,
train_data=train,
test_data=test,
num_runs=5
)
ValueError: Validator not satifised.
The validator's definition is as follows:
validator=lambda x: isinstance(x, np.ndarray)

[x] I checked the documentation
[ ] I checked to make sure that this is not a duplicate question

You may also provide a Minimal, Complete, and Verifiable example you tried as a workaround, or StackOverflow solution that you have walked through. (e.g. cosmic radiation).
In addition, figure out your MatchZoo version by running import matchzoo; matchzoo.__version__.

.


[CLOSED] pull initial messages from db instead of having them hardcoded

 Issue by WestleyArgentum
Wednesday Jun 22, 2016 at 20:01 GMT
Originally opened as https://github.com/buzzfeed-openlab/convention-bot/pull/15

WestleyArgentum included the following code: https://github.com/buzzfeed-openlab/convention-bot/pull/15/commits

 Comment by WestleyArgentum
Wednesday Jun 22, 2016 at 21:12 GMT

fixes #14


Official Dockerhub image

Is your feature request related to a problem? Please describe.
For CI pipelines it can be convenient to run a linting/checking tool from a Docker image.  For example, Pyup provides their safety tool as a Docker image that you can run in a CI pipeline with:
cat requirements.txt | docker run -i --rm pyupio/safety safety check --stdin

This is useful so that instead of ensuring that safety is installed on a CI worker, you just pull the image and run.
It would be great to have a similar image for Bandit.  There's a handful of ones I see in Dockerhub that have been created by random people and haven't been updated in some time, so it'd be great to have an official supported image that's kept up to date.
Describe the solution you'd like
A Docker image in Dockerhub that contains Bandit, tagged with the version that is installed in the image (latest always being the most recently released version of Bandit)
Describe alternatives you've considered
Currently I build my own image and install bandit into it, but it'd be nice to not have to maintain that and have an official image that can be used by the community at large.
Additional context
N/A

For those looking for something in the interim before this issue is addressed, In the absence of an official PyCQA endorsed image, this one works: https://github.com/cytopia/docker-bandit

Good idea @pzelnip , I will look into this.

Let me know if you want help @lukehinds!

Started getting a repo and org setup on dockerhub:
https://hub.docker.com/repository/docker/pycqa/bandit/general


(PUP-4527) Add MigrationChecker method to provide available migrations

Befoe this, reflection had to be used to see what a version of a
MigrationChecker implements.
This is now changed so all versions of puppet after 3.8.0 has a method
that returns the migration checks that are implemented. This makes it
possible to have newer versions of the migration checker support older
versions of puppet (>= 3.8.0).

CLA signed by all contributors.


Add a system to bulk import from a manifest file

In kolibri-explore-plugin, add a system to discover content manifest files placed in a directory named content/bulk-import, and import them when Kolibri is initializing. This is specified as part of https://github.com/endlessm/endless-key-content-private/issues/102. This system will make it easier for us to produce deployments of Endless Key with pre-loaded content.

I support your 2 day exploration here but please keep it limited to that as we need to shift to new projects better aligned with our new strategy.  (I am assuming that #899 will be an adequate solution for now)
Would the approach you are exploring here also require significant work on the image builder front?


MM-44921_First admin signup in new server briefly flashes error screen

Summary
In a brand new server with no users, after the signup completes and before redirecting to the create team screen, there should not be a brief flash of an error of “No signups allowed”.
Ticket Link
https://mattermost.atlassian.net/browse/MM-44921
Screenshots
https://user-images.githubusercontent.com/79058848/188728681-c5cd1de0-69f0-46cf-a55b-0ed6405ae9bf.mp4
Release Note
NONE

/e2e-test

E2E tests not automatically triggered, because PR has no approval yet. Please ask a developer to review and then try again to attach the QA label.


External command instrument

If something uses the web api it could be implemented in something else. Print stdout to the dedicated instrument log window

more of an idea bucket than issue that we care about solving


Fix fractfact_opt for Python3

Resolves #9

@jvailius, your example fractfac_opt(4, 1) returns now ('a b c abc', ['a = bcd', 'b = acd', 'c = abd', 'd = abc', 'ab = cd', 'ac = bd', 'ad = bc', 'abcd'], array([0., 0., 3., 4., 0., 0., 0., 0., 0., 0.]))
Does it make sense to you? I can add an assertion on the return value but I am not familiar with the function so just to check it is ok for you.

Does it make sense to you?

I have not the faintest idea to be honest :D I am relatively new to DOE but this looks like an interesting function and I will further explore it. The result is identical what I get with my fix. Thank you.


elasticsearch 2

does this work with es 2?

Unfortunately not, not least because this was written when facets were the norm, and these have been fully replaced with aggregations as of ElasticSearch 2.0.
For our earlier response to the aggregation issue, please see https://github.com/CottageLabs/facetview2/issues/13#issuecomment-153448469.


Basic implementation of URLCredentialStorage

A basic implementation of URLCredentialStorage, mainly oriented to
credentials for the session. It is an in-memory storage and ignores any
usage of permantent or synchronizable persistency. This should cover
many usage cases, and should allow to built on top of it.
Includes tests.
Known differences with macOS:
I tried to run the set of test against macOS (10.14.5) and found a couple of weird results (I run the tests in a playground, so that might cause interesting behaviours).

.permanent credentials are only stored in-memory (so they are equivalent to .forSession). Each operating system might have their own permanent storage, so each implementation might be different (or not exist at all). This can be tackled after this basic implementation is reviewed, and in a per-OS strategy.
Seems that URLCredentialStorage() in macOS will not return a storage that can store credentials (not even .forSession ones). In the tests I decided to use URLCredentialStorage.shared since it will work on macOS, but makes the tests harder to read, because you have to implicitely clean.
Seems that setting a credential for a protection space, even if it is not through setDefaultCredential(…), sets it as default.
I could not get the change notifications to happen in macOS. I added the notifications nonetheless where I think they should happen.
I could not add a .synchronizable credential in macOS. I imagine the playground I was using might not have the right permissions for the iCloud Keychain. However, in the implementation, the .synchronizable credentials are added to the in-memory storage, and are removed only when providing the special key.

@swift-ci please test linux

Yeah, you need to have an entitled client (i.e., an App Store or Developer ID app) to access iCloud Keychain.
I'd rather that we don't add .synchronizable credentials. When we accept doing a thing, we may risk introducing people who rely on it, or port existing code that relies on it, and make assumptions about the way it works. Since no process is entitled on Linux, we should just fail to save the way macOS does.

I'm fine with everything else! Unless someone wants to contribute persistency to actual secure storage (say, the GNOME keyring).
Fixes https://bugs.swift.org/browse/SR-10375 (which we're repurposing for both the storage and the credentials)

OK. I will do some changes to make very obvious that .synchronizable credentials are not supported. It is not clear if I should do the same with .permanent, though.
Another difference I forgot in the initial summary: I have not implemented the methods that receive URLSessionTask. The documentation is not very clear, but from some clues they might be intended for subclasses. I will provide simple implementations for the base class.

@swift-ci please test linux
@millenomi: I also can keep working in #2312, if you want, I would love to have NSCache more or less working.

@swift-ci please test linux

I've been working on a parallel implementation that also has disk support.

@swift-ci please test linux platform

@swift-ci please test linux platform

@swift-ci please test Linux platform

@swift-ci please test Linux platform


Update README.md

Fix the link to 'limited set of ONNX operators'
Pull Request Template
Checklist

[x] Confirmed that run-checks all script has been executed.
[x] Made sure the book is up to date with changes in this PR.

Related Issues/PRs
Provide links to relevant issues and dependent PRs.
Changes
Summarize the problem being addressed and your solution.
Testing
Describe how these changes have been tested.

Thank you!


Add Fade In Animations

Things that could be faded in:

Error Messages
Screen skeletons
Data
Form Fields

List items in All Vettes could fade in staggered


[FEATURE REQ] Spring - Add health indicator for Event Hub stream binder

Goal
We need to add a health indicator for azure-spring-cloud-stream-binder-eventhubs, this will show the status of the EH binder in /actuator/health endpoint:

Counterparts
Kafka binder
The Kafka binder's health indicator creates a metadataConsumer and uses this consumer to check whether a partition is alive:
https://github.com/spring-cloud/spring-cloud-stream-binder-kafka/blob/e2eca34e4b8f7fc0dab2f19a19094cce0dfda2e4/spring-cloud-stream-binder-kafka/src/main/java/org/springframework/cloud/stream/binder/kafka/KafkaBinderHealthIndicator.java#L115-L167
AWS Kinesis binder
Similiar to the Kafka implementation:
https://github.com/spring-cloud/spring-cloud-stream-binder-aws-kinesis/blob/cd64d8918b073b3b3ddfbf4b8747c16fcffc231d/spring-cloud-stream-binder-kinesis/src/main/java/org/springframework/cloud/stream/binder/kinesis/KinesisBinderHealthIndicator.java#L44-L70
Rabbit binder
https://github.com/spring-cloud/spring-cloud-stream-binder-rabbit/blob/e39487a4ce6c121d74c0e2778393d827cfc509bb/spring-cloud-stream-binder-rabbit/src/main/java/org/springframework/cloud/stream/binder/rabbit/config/RabbitServiceAutoConfiguration.java#L206-L215
Conclusion
They all use the underlying SDK to test whether the connection to the broker is alive or whether the broker is in a healthy state.
How to implement
The ideal way to implement this is to:

Get the instance of the EH client used by a binder.
Perform a low-cost operation on the client and try to determine the liveness of the EH client

However, our EH SDK doesn't provide such functions, take the EventProcessorClient for example, it only has an isRunning() method. We can't get the raw EH client via an EventProcessorClient object.
https://github.com/Azure/azure-sdk-for-java/blob/5672b860b15aa32d1dd5b559f47c3cb1058f0166/sdk/eventhubs/azure-messaging-eventhubs/src/main/java/com/azure/messaging/eventhubs/EventProcessorClient.java#L173-L175
So the first step to implement the health indicator is to call the isRunning method, and for the next step, we need to work with the EH sdk to see whether we could get more info through the EventProcessorClient.

Hi @conniey, @srnagar, @yijunxiems
As we're going to add the health indicator for our EH binder, which uses the EventProcessorClient as the consumer, but we find out that we can't get sufficient information from the EventProcessorClient, such as whether the client is alive.
Is it possible that the EventProcessorClient could expose an API to get the status of the underlying eventHubAsyncClient and perform some low-cost operations on it?

This sounds similar to https://github.com/Azure/azure-sdk-for-java/issues/19391.
Can you give a more concrete scenario of the metrics you want? (ie. I want to know how many partitions I own")

Adding more related issues: https://github.com/microsoft/spring-cloud-azure/issues/521

It's a little different from the metrics, the health indicator is used to indicate the health condition of the application components. So for the event hubs stream binder, the health indicator should indicate these:

The connectivity of the event hub client
The health conditions of each partition

@saragluna
As far as I know, Event Hubs does not expose any "health condition" of each partition information. @JamesBirdsall may know more.
We can say if the Event Hub client is connected or not though.
Is that the information you need?

@conniey, I think for the moment to tell whether the EH client is connected is what we need.

Closing this issue now.


[instancer] Should bake in rvrn

Discussed in https://github.com/fonttools/fonttools/discussions/3057
Some shapers would not process rvrn for static fonts. The instancer should either bake in the rvrn lookups into the cmap, or easier, move the rvrn lookups to a feature like ccmp or loca.
Ugly, yes.

I think we should change the feature tag to ccmp and hope for the best.


Force the reload of the page with a nuxt-link

What problem does this feature solve?
I would like to use the <nuxt-link> component to benefit from the classes such as .nuxt-link-exact-active, but need to reload the window to reset a hidden incheckbox input value.
I need to make it work even with javacript disabled. Basically, to make that work I'd use a simple <a> element, it will reload the page, but not have the active link classes.
What does the proposed changes look like?
This link will benefit from the classes, but will reload the window !

This feature request is available on Nuxt community (#c10663)

Nevermind, altough I found an alternative to my problem, I don't know if there are other use cases to this options.
As I said, I wanted it to work without javascript, then I remembered that without javascript, <nuxt-link> is just an anchor element, and that without javascript it will by default reload the page. To uncheck my input I used a @click event listener. Letting this open as maybe it might help others

Thanks for updating the request, closing it to cleanup our backlog

I just replaced <nuxt-link> or<button @click=""> with a simple <a href="/"> and works like a charm :)

For the record: This doesn't work on production when router.base is different from "/"

This would be a good adition on a very specific case i'm dealing with, I'm sending the user to a i18n route, so I can't use in a simple <a> tag, and the reason that I need to perform the reload is to deal with Google Tag Manager properly, I'm trying to trigger an action once the url is loaded, since it doesn't reload the event is not triggered.


Fix default for validate_cert in example

Codecov Report

Merging #44 (4a59393) into master (616bd90) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #44   +/-   ##
=======================================
  Coverage   85.17%   85.17%
=======================================
  Files           9        9
  Lines        1140     1140
=======================================
  Hits          971      971
  Misses        111      111
  Partials       58       58

Flag
Coverage Δ

unittests
85.17% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Continue to review full report at Codecov.

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


XSPEC models cannot be retrieved by load_analysis_results

XSPEC models provided by xspec-modelsonly aren't initialized through FunctionMeta in function.py and thereby are not added to the _known_functions dictionary. This dictionary is used to assemble the expression of a saved analysis_results in load_analysis_results (which is done through get_function in function.py).
Steps to reproduce the behavior:

Create a model which includes XSPEC functions (composite or otherwise)
Run a fit
Save results object as .fits using analysis_results.write_to()
Use load_analysis_results() to recover results object -- error occurs because XSPEC function is not found in _known_functions

Example of returned error:
in _parse_function_expression     "probably missing the data file" % (unique_function, function_specification)) astromodels.functions.function.UnknownFunction: Function XS_diskbb in expression (TbAbs{1} * XS_diskbb{2}) is unknown. If this is a template model, you are probably missing the data file

Hi @xboluna quick question. You do have xspec initialized when you reload the model?

@xboluna I just added a new test in a branch of astromodels that should cover this issue:
https://github.com/threeML/astromodels/pull/164/files
So in principle it should be ok..

Hi @xboluna quick question. You do have xspec initialized when you reload the model?

Oops! This was my mistake -- I had thought it would initialize with from astromodels import *. Thanks for looking into this!

No worries @xboluna this was a good test to add in astromodels. You never know when something else might make this fail.


Fix LakeFS startup with Azure storage type

LakeFS is not able to start after a restart if using Azure Blob storage as it returns https as storage class and lakeFS uses azure as storage class.

Fixed in #2250

We would like to handle it in a more generic way, and fix this bug in LinkPhysicalAddress in controller.go as well.


Rewriting homepage info into contents/_index.md

Hi!
I think this setup could be made portable if the homepage info which is written to config.toml be written instead to contents/_index.md (which is usually the case for most themes).
Or is there a possibility to make this optional? Thanks!

Hi @paniash
Thanks for your proposal. I recently refactored the code and made this change for flexibility both in terms of technical development and usage. I am looking for spare time to make the final changes and push the result.


Update readme codeblocks

https://github.com/github/linguist/pull/6086 is in so this PR just replace uses of ```make ``` with ```just ``` in the READMEs.
Closes : #1372

Nice, thanks for the PR!


Handle HUP on UART

The tty we are using can generate a HUP (EPOLLIN | EPOLLERR | EPOLLHUP) in which case we should a) stop using that fd and b) probably try reopening it just like we try to reconnect to TCP.
@fnoop I think this is the remaining issue for you... One way to verify that is to search for "serial" in /proc/interrupts. Once the device goes away you will notice:
a) you will no longer see "serial" on the correspondent irq and
b) strace -p $(pidof mavlink-routerd) will should epoll_wait returning EPOLLIN | EPOLLERR | EPOLLHUP
I think there's something bad going on on your kernel/device, but we should deal with it nonetheless

btw... the only way I've got to reproduce is by (accidentally) having 2 different process (mavlink-routerd and getty) fighting for the UART.

@lucasdemarchi  This makes a lot of sense, thanks.  I'll try and test it as soon as I can.


base option not working

Vue.js / vue-router versions
2.1.2 / 2.1.1
Reproduction Link

http://jsfiddle.net/xgrjzsup/1352/
http://stackoverflow.com/questions/42664712/how-base-option-works-in-vue-router
Steps to reproduce
add base in route:
const router = new VueRouter({
  base: "/app/",
  routes
})

What is Expected?
It should had added /app/ in all the routes when hitting from the browsers.
What is actually happening?
When I do /app/foo in the browser, it is not going to corresponding route of /foo.

As they told you on the SO post, the base doesn't have to be part of the link


[WIP] Initial Version 2 Commit

This adds the metadata classes and attributes necessary
to start creating a feature in code. Also created an InMemoryStore.
The next steps are creating the integrations into asp.net core for
features, stores, and conditions.

Remind @billbogaiv that the IStore implementation probably still needs a Get method to support the UI and other mechanisms to change features without instantiating the feature itself.

Global conditionals registered... globally and apply to all features.
Think DisableInProduction condition or EnableForThisEnvironment condition.

@khalidabuhakmeh: IStore.Get: https://github.com/ritterim/RimDev.FeatureFlags/blob/f5d5e2fcfa83f104e89a766c2c8c26bf0cff4cbd/src/RimDev.AspNetCore.FeatureFlags/Stores/InMemoryStore.cs#L12-L23


[WATT]New Page Wizard can't see the "Accept", "Cancel" button

Technical
WATT
Description
Chrome Zoom is 100% or more large, New Page Wizard can't see the "Accept", "Cancel" button.
So the user can't close the New Page wizard.
Steps to reproduce

Create a new project in Design Editor
Enlarge Chrome Zoom value
Open the New Page Wizard

Expected behaviour
See the  "Accept", "Cancel" button
Actual behaviour
Can't see the Accept", "Cancel" button

PR was merged. Please check if it works

ok. It's good working. It can be closed


OneDrive

You shouldn't be referring to this as OneDrive.  The Office 365 group has a SharePoint site collection behind it.  OneDrive is a personal space for users (which runs on SharePoint).

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

ID: 11357d2a-97f6-c5d6-2a62-0d5cae1a1c3d
Version Independent ID: 51900b79-f5ed-25b8-ee89-9078129bdb15
Content: Create the new workspaces - Power BI - Power BI
Content Source: powerbi-docs/service-create-the-new-workspaces.md
Service: powerbi
Sub-service: powerbi-service
GitHub Login: @maggiesMSFT
Microsoft Alias: maggies

Hi, @danmyhre -- thanks for your feedback! I'll check to see what would be better wording.

Maybe add clarification then until they fix the product.


Output spam when running code from command line

VSCode Version: Code 1.3.1 (e6b4afa53e9c0f54edef1673de9001e9f0f547ae, 2016-07-12T13:35:06.227Z)
OS Version: Windows_NT ia32 6.1.7601

Steps to Reproduce:

type name of .yaml file on command line
opens but cmd window has this:

D:\temp\CasportMock\Casport\App_Data>
[12328:15996:0728/130946:VERBOSE1:crash_service_main.cc(68)] Session start. cmdl
ine is [--reporter-url=https://ticinocrashreporter.azurewebsites.net/crash --app
lication-name=VSCode --v=1]
[12328:15996:0728/130946:VERBOSE1:crash_service.cc(142)] window handle is 002107
D4
[12328:15996:0728/130946:VERBOSE1:crash_service.cc(290)] pipe name is .\pipe\V
SCode Crash Service
dumps at c:\Temp\VSCode Crashes
[12328:15996:0728/130946:VERBOSE1:crash_service.cc(294)] checkpoint is c:\Temp\V
SCode Crashes\crash_checkpoint.txt
server is https://ticinocrashreporter.azurewebsites.net/crash
maximum 128 reports/day
reporter is electron-crash-service
[12328:15996:0728/130946:VERBOSE1:crash_service_main.cc(84)] Ready to process cr
ash requests
[12328:4872:0728/130946:VERBOSE1:crash_service.cc(323)] client start. pid = 6984
[12328:4872:0728/130947:VERBOSE1:crash_service.cc(323)] client start. pid = 1474
4
[23748:23240:0728/130947:VERBOSE1:crash_service_main.cc(68)] Session start. cmdl
ine is [--reporter-url=https://ticinocrashreporter.azurewebsites.net/crash --app
lication-name=VSCode --v=1]
[23748:23240:0728/130947:VERBOSE1:crash_service.cc(142)] window handle is 00510F
D6
[23748:23240:0728/130947:VERBOSE1:crash_service.cc(290)] pipe name is .\pipe\V
SCode Crash Service
dumps at c:\Temp\VSCode Crashes
[23748:23240:0728/130947:VERBOSE1:crash_service.cc(294)] checkpoint is c:\Temp\V
SCode Crashes\crash_checkpoint.txt
server is https://ticinocrashreporter.azurewebsites.net/crash
maximum 128 reports/day
reporter is electron-crash-service
[23748:23240:0728/130947:ERROR:crash_service.cc(301)] could not start dumper

@gstar42 can you please clarify the first step? Does that mean that you start vscode with code myfile.yaml ?

yes

From: Kai Maetzel<EMAIL_ADDRESS>Sent: Monday, August 1, 2016 6:42 PM
To: Microsoft/vscode
Cc: garry; Mention
Subject: Re: [Microsoft/vscode] Crash when opening .yaml file (#9920)
@gstar42https://github.com/gstar42 can you please clarify the first step? Does that mean that you start vscode with code myfile.yaml ?

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/vscode/issues/9920#issuecomment-236767466, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AB7LZddQHlUfMqjbIxQg46b5QtDx77ehks5qbqCDgaJpZM4JXmLH.

Can't reproduce. @bpasero does the stack trace indicate that the electron crash reporter could not launch correctly?

I don't know. This is what I type and I get the messages in that dos window. Meanwhile, the file opens in VSCode.
D:\temp\CasportMock\Casport\App_Data>casport_data.yaml
D:\temp\CasportMock\Casport\App_Data>
[9600:2184:0802/142753:VERBOSE1:crash_service_main.cc(68)] Session start. cmdlin
e is [--reporter-url=https://ticinocrashreporter.azurewebsites.net/crash --appli
cation-name=VSCode --v=1]
[9600:2184:0802/142753:VERBOSE1:crash_service.cc(142)] window handle is 000C11E8
[9600:2184:0802/142753:VERBOSE1:crash_service.cc(290)] pipe name is \.\pipe\VSC
ode Crash Service
dumps at c:\Temp\VSCode Crashes
[9600:2184:0802/142753:VERBOSE1:crash_service.cc(294)] checkpoint is c:\Temp\VSC
ode Crashes\crash_checkpoint.txt
server is https://ticinocrashreporter.azurewebsites.net/crash
maximum 128 reports/day
reporter is electron-crash-service
[9600:2184:0802/142753:VERBOSE1:crash_service_main.cc(84)] Ready to process cras
h requests
[9600:16172:0802/142753:VERBOSE1:crash_service.cc(323)] client start. pid = 1536
8
[9600:16172:0802/142754:VERBOSE1:crash_service.cc(323)] client start. pid = 1629
2
[1028:12028:0802/142754:VERBOSE1:crash_service_main.cc(68)] Session start. cmdli
ne is [--reporter-url=https://ticinocrashreporter.azurewebsites.net/crash --appl
ication-name=VSCode --v=1]
[1028:12028:0802/142754:VERBOSE1:crash_service.cc(142)] window handle is 0002121
6
[1028:12028:0802/142754:VERBOSE1:crash_service.cc(290)] pipe name is \.\pipe\VS
Code Crash Service
dumps at c:\Temp\VSCode Crashes
[1028:12028:0802/142754:VERBOSE1:crash_service.cc(294)] checkpoint is c:\Temp\VS
Code Crashes\crash_checkpoint.txt
server is https://ticinocrashreporter.azurewebsites.net/crash
maximum 128 reports/day
reporter is electron-crash-service
[1028:12028:0802/142754:ERROR:crash_service.cc(301)] could not start dumper

From: Kai Maetzel<EMAIL_ADDRESS>Sent: Tuesday, August 2, 2016 2:17 PM
To: Microsoft/vscode
Cc: garry; Mention
Subject: Re: [Microsoft/vscode] Crash when opening .yaml file (#9920)
Can't reproduce. @bpaserohttps://github.com/bpasero does the stack trace indicate that the electron crash reporter could not launch correctly?

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/vscode/issues/9920#issuecomment-237046960, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AB7LZaG0yTIHt85w1vrdUE2w57LgfYLXks5qb7P8gaJpZM4JXmLH.

The issue is that there is output showing up in the console even though our code script should prevent that. Moving to @joaomoreno

@gstar42 Can you show me your %PATH% variable?

C:>path
PATH=D:\app\gstar\product\11.2.0\client_1;D:\app\gstar\product\11.2.0\client_1\b
in;C:\Program Files (x86)\Intel\iCLS Client;C:\Program Files\Intel\iCLS Client
;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Program Files (x86)
Intel\OpenCL SDK\2.0\bin\x86;C:\Program Files (x86)\Intel\OpenCL SDK\2.0\bin\x64
;d:\bin;C:\Program Files (x86)\Microsoft Team Foundation Server 2015 Power Tools
;%BPADir%;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Program Files (x86)\Mi
crosoft ASP.NET\ASP.NET Web Pages\v1.0;C:\Program Files\Microsoft SQL Server\11
0\Tools\Binn;D:\cpe\database\bin;D:\cpe\DLLs;D:\Program Files\Microsoft Network
Monitor 3;D:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE;C:\W
indows\System32\WindowsPowerShell\v1.0;D:\Program Files (x86)\Windows Resource
Kits\Tools;C:\Program Files (x86)\Windows Kits\8.0\Windows Performance Toolkit
;D:\Telos\DM;C:\Program Files (x86)\Windows Kits\8.1\Windows Performance Toolkit
;C:\Program Files\Intel\Intel(R) Management Engine Components\DAL;C:\Program Fi
les\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files (x86)\Intel
\Intel(R) Management Engine Components\DAL;C:\Program Files (x86)\Intel\Intel(R)
Management Engine Components\IPT;C:\Program Files (x86)\Microsoft SDKs\TypeScri
pt\1.0;C:\Program Files\Microsoft SQL Server\120\Tools\Binn;C:\Program Files (
x86)\Microsoft SQL Server\110\Tools\Binn;C:\Program Files\Microsoft SQL Server
110\DTS\Binn;C:\Program Files (x86)\Microsoft SQL Server\110\Tools\Binn\Managem
entStudio;C:\Program Files (x86)\Microsoft SQL Server\110\DTS\Binn;C:\Program
Files (x86)\Windows Kits\10\Windows Performance Toolkit;C:\Program Files\Micros
oft SQL Server\130\Tools\Binn;C:\Program Files (x86)\Common Files\Acronis\SnapA
PI;c:\Program Files\Microsoft\Web Platform Installer;C:\Program Files\Git\cmd;
D:\Telos\Amhs\Bin;;D:\bin\Sysinternals;C:\Users\GStar.AMHSCENTRAL\AppData\Local
\Code\bin;D:\Program Files\7-Zip;d:\Program Files (x86)\Microsoft VS Code\bin;c:
\PROGRA~2\MI1FF4~1;;C:\Program Files (x86)\Common Files\Acronis\TibMounter64
C:>

From: João Moreno<EMAIL_ADDRESS>Sent: Monday, August 8, 2016 2:39 AM
To: Microsoft/vscode
Cc: garry; Mention
Subject: Re: [Microsoft/vscode] Output spam when running code from command line (#9920)
@gstar42https://github.com/gstar42 Can you show me your %PATH% variable?

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/vscode/issues/9920#issuecomment-238188399, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AB7LZdfw44citqGSWbBl6NpvHmt0aDemks5qdvllgaJpZM4JXmLH.

Which command line are you using? Command Prompt, PowerShell? Can you try the latest version, 1.4.0?

Win 7 command prompt.
I'm off the rest of the week so ask me again on Monday...

From: João Moreno<EMAIL_ADDRESS>Sent: Tuesday, August 9, 2016 12:39 AM
To: Microsoft/vscode
Cc: garry; Mention
Subject: Re: [Microsoft/vscode] Output spam when running code from command line (#9920)
Which command line are you using? Command Prompt, PowerShell? Can you try the latest version, 1.4.0?

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/vscode/issues/9920#issuecomment-238477092, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AB7LZTIhCN4mnyRNj5omu5AhEKfx6J_pks5qeC6igaJpZM4JXmLH.

@gstar42 ping

BTW, it still happens. Used it yesterday from WIn7 command line

From: João Moreno<EMAIL_ADDRESS>Sent: Wednesday, September 28, 2016 1:30 AM
To: Microsoft/vscode
Cc: garry; Mention
Subject: Re: [Microsoft/vscode] Output spam when running code from command line (#9920)
@gstar42https://github.com/gstar42 ping

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/vscode/issues/9920#issuecomment-250104533, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AB7LZQ9ago2KibJK8jmXevn85xt4VvxFks5quiWUgaJpZM4JXmLH.

Which version? Can you try the latest?

I updated a few days ago
Sent from my tablet
-------- Original message --------
From: João Moreno<EMAIL_ADDRESS>Date: 9/28/16 7:30 AM (GMT-08:00)
To: Microsoft/vscode<EMAIL_ADDRESS>Cc: garry<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [Microsoft/vscode] Output spam when running code from command line (#9920)
Which version? Can you try the latest?

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/vscode/issues/9920#issuecomment-250183293, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AB7LZXvgs60I2d9zb8VnZUNWPGrCEGBkks5qunoEgaJpZM4JXmLH.

Please give me a version number.

[cid:977cfe3d-0aaf-497d-a370-aa0232384fd0]

From: João Moreno<EMAIL_ADDRESS>Sent: Wednesday, September 28, 2016 8:04 AM
To: Microsoft/vscode
Cc: garry; Mention
Subject: Re: [Microsoft/vscode] Output spam when running code from command line (#9920)
Please give me a version number.

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/vscode/issues/9920#issuecomment-250193975, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AB7LZSk4ndwiLuho3JNz4TLvzIgVO9F3ks5quoHggaJpZM4JXmLH.

Let's try again: what is your current VS Code version?

Didn't you get my last email? 1.5.3

From: João Moreno<EMAIL_ADDRESS>Sent: Friday, September 30, 2016 12:30 AM
To: Microsoft/vscode
Cc: garry; Mention
Subject: Re: [Microsoft/vscode] Output spam when running code from command line (#9920)
Let's try again: what is your current VS Code version?

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/vscode/issues/9920#issuecomment-250678774, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AB7LZTVgyvaGErdHQm9o2F64R5LmlSQOks5qvLqjgaJpZM4JXmLH.

This seems fixed.


Issue with k8s.io/zh/docs/concepts/scheduling-eviction/scheduler-perf-tuning/

https://github.com/kubernetes/website/issues/21285

@npu21 Still working on this?

@npu21 pls confirm you are still interested in revising this?

I'm gonna close this because it has been there for 3 months. Pls feel free to reopen.
/close


Bug integrating Cesium into a vite-plugin-ssr application

Description
I have been working to integrate a CesiumJS viewer into an existing vite-plugin-ssr application, via Macrostrat's Cesium viewer module. I am early in the debugging process of this (it's a major change in bundling strategy from Webpack, as well. But I encountered the below error and am reporting it here as asked! Any insights are appreciated.
Error<EMAIL_ADDRESS>You stumbled upon a bug in vite-plugin-ssr's source code. Go to https://github.com/brillout/vite-plugin-ssr/issues/new and copy-paste this error; a maintainer will fix the bug (usually under 24 hours).
    at getFilePathVite (file:///Users/Daven/Projects/Macrostrat/Software/web/.yarn/__virtual__/vite-plugin-ssr-virtual-ea735fca57/0/cache/vite-plugin-ssr-npm-0.4.142-bb82084716-b89f194747.zip/node_modules/vite-plugin-ssr/dist/esm/utils/getFilePathAbsolute.js:57:5)
    at getPrettyErrorWithCodeSnippet (file:///Users/Daven/Projects/Macrostrat/Software/web/.yarn/__virtual__/vite-plugin-ssr-virtual-ea735fca57/0/cache/vite-plugin-ssr-npm-0.4.142-bb82084716-b89f194747.zip/node_modules/vite-plugin-ssr/dist/esm/node/plugin/shared/loggerNotProd/errorWithCodeSnippet.js:49:24)
    at logErr (file:///Users/Daven/Projects/Macrostrat/Software/web/.yarn/__virtual__/vite-plugin-ssr-virtual-ea735fca57/0/cache/vite-plugin-ssr-npm-0.4.142-bb82084716-b89f194747.zip/node_modules/vite-plugin-ssr/dist/esm/node/plugin/shared/loggerNotProd.js:83:29)
    at logViteErrorContainingCodeSnippet (file:///Users/Daven/Projects/Macrostrat/Software/web/.yarn/__virtual__/vite-plugin-ssr-virtual-ea735fca57/0/cache/vite-plugin-ssr-npm-0.4.142-bb82084716-b89f194747.zip/node_modules/vite-plugin-ssr/dist/esm/node/plugin/shared/loggerNotProd.js:61:5)
    at Object.config.logger.<computed> [as error] (file:///Users/Daven/Projects/Macrostrat/Software/web/.yarn/__virtual__/vite-plugin-ssr-virtual-ea735fca57/0/cache/vite-plugin-ssr-npm-0.4.142-bb82084716-b89f194747.zip/node_modules/vite-plugin-ssr/dist/esm/node/plugin/shared/loggerVite.js:37:13)
    at file:///Users/Daven/Projects/Macrostrat/Software/web/.yarn/__virtual__/vite-virtual-23cbd68f33/0/cache/vite-npm-4.4.9-e845c1bbf8-c511024cea.zip/node_modules/vite/dist/node/chunks/dep-df561101.js:42035:43

Does DEBUG=vike:error as described at https://vike.dev/errors#verbose solve the situation?

Can you provide a reproduction? That'd be the best for this particular bug.

I will check!

I did the due diligence on my side to ensure that the app worked in Vite sans Vike, and discovered that in fact there were quite a few underlying compilation errors due to ESM module difficulties. Once I solved those outside of the SSR context, this error was resolved.
This clearly is not an internal issue with Vike, but I wonder if the Vike-specific compilation steps are swallowing errors they should instead forward, perhaps in the service of this "user-friendly" warning. It'd help if the default was a little more verbose, probably.

I had a closer look at this: it actually is an internal issue with Vike.
I've pre-released a new version<EMAIL_ADDRESS>which includes debug logs for this issue.
Can you give me the error again Error<EMAIL_ADDRESS>You stumbled upon a bug in ... using that version? This time, the error message will include debug information which will allow me to get to the bottom of this.


Oxygen Project XPR conflict

It seems that there was a syn issue with the swiML.xpr file. On my local computer I am now pushed to used the file in the archive folder swiML (Christoph Bartneck's conflicted copy 2023-11-02).xpr. Do we each need to have a separate project file or should we try to bring them back together. If so, how?

Christoph has to resolve the sync issue at home

resolved.