unstable results

Hi,
I am getting different scene results in different machines. even though I have installed the same version of packages(including all dependencies) in both machines
Version of packages installed in both machines:
scenedetect | <IP_ADDRESS> | <IP_ADDRESS>
ffmpeg-python | 0.2.0 | 0.2.0
imageio | 2.5.0 | 2.6.1
imageio-ffmpeg | 0.3.0 | 0.3.0
opencv-python | <IP_ADDRESS> | <IP_ADDRESS>
result i got in machine 1:

| Scene # | Start Frame |  Start Time    |  End Frame  |     End Time   |

|        1  |           0 | 00:00:00.000 |           4 | 00:00:00.133 |
|        2  |           4 | 00:00:00.133 |          19 | 00:00:00.634 |
|        3  |          19 | 00:00:00.634 |          34 | 00:00:01.134 |
|        4  |          34 | 00:00:01.134 |          49 | 00:00:01.635 |
|        5  |          49 | 00:00:01.635 |          64 | 00:00:02.135 |
|        6  |          64 | 00:00:02.135 |          79 | 00:00:02.636 |
|        7  |          79 | 00:00:02.636 |          94 | 00:00:03.136 |
|        8  |          94 | 00:00:03.136 |         109 | 00:00:03.637 |
|        9  |         109 | 00:00:03.637 |         125 | 00:00:04.171 |
|       10  |         125 | 00:00:04.171 |         140 | 00:00:04.671 |
|       11  |         140 | 00:00:04.671 |         155 | 00:00:05.172 |
|       12  |         155 | 00:00:05.172 |         180 | 00:00:06.006 |
|       13  |         180 | 00:00:06.006 |         184 | 00:00:06.139 |
in machine 2:

| Scene # | Start Frame |  Start Time    |  End Frame  |     End Time   |

|        1  |           0 | 00:00:00.000 |           4 | 00:00:00.133 |
|        2  |           4 | 00:00:00.133 |          19 | 00:00:00.634 |
|        3  |          19 | 00:00:00.634 |          34 | 00:00:01.134 |
|        4  |          34 | 00:00:01.134 |          49 | 00:00:01.635 |
|        5  |          49 | 00:00:01.635 |          64 | 00:00:02.135 |
|        6  |          64 | 00:00:02.135 |          79 | 00:00:02.636 |
|        7  |          79 | 00:00:02.636 |          94 | 00:00:03.136 |
|        8  |          94 | 00:00:03.136 |         109 | 00:00:03.637 |
|        9  |         109 | 00:00:03.637 |         125 | 00:00:04.171 |
|       10  |         125 | 00:00:04.171 |         140 | 00:00:04.671 |
|       11  |         140 | 00:00:04.671 |         155 | 00:00:05.172 |
|       12  |         155 | 00:00:05.172 |         180 | 00:00:06.006 |
can anyone please help me

Hi @peratchi;
Indeed this is a very interesting result.  Have you confirmed that you are using a bit-for-bit identical copy of the same video on both machines?  Can you share more information about the two machines?  Do they have the same hardware/operating system, or is it different?  Can you replicate this behaviour in a virtual machine?  What version of Python are you using?
Lastly, how are you running and comparing the output?  It seems like on machine #2 it detected the same scenes except for the last one.  This indicates that the detection matched on both machines until that point, at which one process appears to have prematurely terminated.
Can you provide an output debug log as well?  Add -v debug -l BUG_REPORT.txt to the beginning of the command, then re-run PySceneDetect and attach the generated BUG_REPORT.txt` file for both machines.
Thank you for your report.

Hi @Breakthrough ,
PFB content of BUG_REPORT.txt which i got on both machines.
Machine 1: (OpenCV = <IP_ADDRESS>, OS = Ubuntu 18.04.3 LTS, 8 Core /16GB RAM)
INFO: init.scenedetect_cli(): Version: v0.5.1
INFO: init.scenedetect_cli(): Info Level: debug
DEBUG: context.parse_options(): Parsing program options.
DEBUG: context._init_video_manager(): Initializing VideoManager.
INFO: video_manager.init(): Loaded 1 video, framerate: 24.00 FPS, resolution: 1280 x 720
INFO: video_manager.set_downscale_factor(): Downscale factor set to 5, effective resolution: 256 x 144
DEBUG: context.parse_options(): VideoManager initialized.
DEBUG: init.detect_content_command(): Detecting content, parameters:
threshold: 30, min-scene-len: 15
INFO: context.list_scenes_command(): Scene list CSV file name format:
$VIDEO_NAME-Scenes.csv
DEBUG: context.process_input(): Processing input...
INFO: context.process_input(): Detecting scenes...
INFO: context.process_input(): Processed 14308 frames in 48.6 seconds (average 294.45 FPS).
INFO: context.process_input(): Detected 130 scenes, average shot length 4.6 seconds.
INFO: context.process_input(): Writing scene list to CSV file:
BigBuckBunny-Scenes.csv
INFO: context.process_input(): Scene List:
Machine 1: (OpenCV = <IP_ADDRESS>, OS = Ubuntu 18.04.4 LTS, 16 Core /32GB RAM)
INFO: init.scenedetect_cli(): Version: v0.5.1
INFO: init.scenedetect_cli(): Info Level: debug
DEBUG: context.parse_options(): Parsing program options.
DEBUG: context._init_video_manager(): Initializing VideoManager.
INFO: video_manager.init(): Loaded 1 video, framerate: 24.00 FPS, resolution: 1280 x 720
INFO: video_manager.set_downscale_factor(): Downscale factor set to 5, effective resolution: 256 x 144
DEBUG: context.parse_options(): VideoManager initialized.
DEBUG: init.detect_content_command(): Detecting content, parameters:
threshold: 30, min-scene-len: 15
INFO: context.list_scenes_command(): Scene list CSV file name format:
$VIDEO_NAME-Scenes.csv
DEBUG: context.process_input(): Processing input...
INFO: context.process_input(): Detecting scenes...
INFO: context.process_input(): Processed 14300 frames in 37.3 seconds (average 382.95 FPS).
INFO: context.process_input(): Detected 131 scenes, average shot length 4.6 seconds.
INFO: context.process_input(): Writing scene list to CSV file:
BigBuckBunny-Scenes.csv

Can you verify that the file size (and hash) is the exact same on both machines?  Is the behaviour repeatable?  If you run this on a third machine, which does it agree with (or can you share the video)?  The fact that just the number of frames it was able to decode makes me think it's either due to a corrupted or nonstandard video stream, or the actual version of ffmpeg that's installed on the systems differ (not the package for Python but the system libraries that OpenCV uses).
Are both systems the same machine architecture (32 vs 64 bit OS)?

Hi @peratchi;
Are you still experiencing this issue?  I would like to close it if not - could you perhaps try on a new version of PySceneDetect?
Thanks!


[FLINK-19520][configuration] Add randomization of checkpoint config.

What is the purpose of the change
With the larger refactoring of checkpoint alignment and the additional of more unaligned checkpoint settings, it becomes increasingly important to provide a large test coverage.
Unfortunately, adding sufficient test cases in a test matrix appears to be unrealistic: many of the encountered issues were subtle, sometimes caused by race conditions or unusual test configurations and often only visible in e2e tests.
Hence, we like to rely on all existing Flink tests to provide a sufficient coverage for checkpointing. However, as more and more options in unaligned checkpoint are going to be implemented in this and the upcoming release, running all Flink tests - especially e2e - in a test matrix is prohibitively expensive, even for nightly builds.
Thus, we want to introduce test randomization for all tests that do not use a specific checkpointing mode. In a similar way, we switched from aligned checkpoints by default in tests to unaligned checkpoint during the last release cycle.
To not burden the developers of other components too much, we set the following requirements:

Randomization should be seeded in a way that both builds on Azure pipelines and local builds will result in the same settings to ease debugging and ensure reproducibility.
Randomized options should be shown in the test log.
Execution order of test cases will not influence the randomization.
Randomization is hidden, no change on any test is needed.
Randomization only happens during local/remote test execution. User deployments are not affected.
Test developers are able to avoid randomization by explicitly providing checkpoint configs.

Brief change log

Add generic method to choose random values for checkpoint config.
Use it for uninitialized "execution.checkpointing.unaligned".
Adds flag to enable randomization in root pom. User code will not trigger randomization but chooses constant default values.

Verifying this change

Not covered (yet)

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (yes / no)
The serializers: (yes / no / don't know)
The runtime per-record code paths (performance sensitive): (yes / no / don't know)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: (yes / no / don't know)
The S3 file system connector: (yes / no / don't know)

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

The randomization here only applies to tests that use MiniClusterResource, right?
I think this is a significant limitation.
Can we overcome it by reading some system property at the time of ConfigOption creation?
	public static final ConfigOption<Boolean> ENABLE_UNALIGNED =
		ConfigOptions.key("execution.checkpointing.unaligned")
			.booleanType()
			.defaultValue(System.getProperty("execution.checkpointing.unaligned", false)) // <-- here

The property can be set either
* by maven/CI at the very beginning to a random value (seed="nanoTime")

* or by the developer or to a fixed value

I think it will be easier to reason about if it's set for the whole build (and logged in the beginning).
WDYT?

That was the very first approach but we didn't like that this means that all tests run only with that particular configuration, which has two issues:

For a large enough test matrix, a certain configuration may happen very rarely. Assuming we have 10 different configuration options (aligned, unaligned with 0, 10s, 1m timeout x 0, 1kb, 1m size limit), then we have 10% chance for a particular combination to occur. But even when running 10 tests, you have 3.4% chance of a specific combination not occurring. If you add that to rarely occurring instabilities that are even now hard to detect, the overall goal of having a good coverage is probably not reached. It becomes worse if we have more interdependent value combinations related to checkpointing like different DSTL settings.
Even for more commonly occurring issues that happen while refactoring/new feature, it's disadvantage to just have one configuration for all tests. You have to manually cycle through the relevant settings through setting the system property to "force" your luck. Here having more or less all combinations being executed by the same AZP run on your feature branch will probably already find you quite a few issues.

Btw (but this is an orthogonal discussion), I'd like to bind the randomization seed to commit id instead of timestamp, such that it's easy for us to debug into any issue (checkout particular commit and go). However, the current implementation might not be ideal in that regard (EnvironmentalInformation might not be updated without a full build).

Assuming that the priorities are:

increase probability of detecting an error
in particular, before merging - i.e. by committer either locally or remotely
improve the usability

The "MiniClusterResource" approach compared to the "properties" approach:

is worse for (1) because a smaller subset of tests is randomized
is better for (2) as you mention above
is worse for (3) because it's not easy to see what else tests fail with a certain configuration (when I already know that some fail)

It also seems more complex though I haven't thought through how to set the property globally.
Additionally, I can imagine a "mandatory" set of combinations that must pass (in several runs) in order to release or be sure to merge.

Can we overcome it by reading some system property at the time of ConfigOption creation?

We didn't like this idea, as it would require to modify the production code.

various drawbacks
Could you elaborate?

For one thing, that's a public api, so we wouldn't be able to easily change it. We could maybe mark it partially as @Internal, but I don't know how to do it in a clear way. Additionally it could just create confusion for the users, in the worst case they can start using it. Apart from that, if you need to modify production code for testing purposes, it usually means something is wrong with the design (having a testing mini cluster that randomly sets configuration options is a cleaner design). And also relaying on the System.getProperty is not the cleanest way.

but via for example adding a temporary log message somewhere in the StreamTask or network stack what alignment option was used after all? I mean there could be a potential problem where for some (or all?) tests, the randomly selected value is still unintentionally overridden to some static value, yielding this change a no-op.

Good point, I have actually completely relied on the log message to check for the result. I'd repeat your suggestion.
Btw, it is my intention that an explicit value for the random options always take precedence. But I assume you want me to check for unintentional overrides.

AZP failure unrelated (https://issues.apache.org/jira/browse/FLINK-21103), merging.


NO-ISSUE: Add range and enum DMN Runner validation for the time, date, date-time and duration types of the new Type Constraint property

The new DMN editor uses the new type constraints property to set the Item Definition/Item Components constraint. This new property is mapped to the  JSON Schema x-dmn-type-constraints keyword. This PR adds the property to the AJV validator. This PR also break the file constants into multiple specific ones.
Before:

After:

Apparently, the string is converted to a Date class after a new edit, and I'm not sure why. I've added a new line to handle this case. @jomarko Thanks for spotting this one.


[FEATURE] Support more advanced POJO/JSON extraction features

See https://github.com/LizeRaes/feedback-analyzer/blob/main/src%2Fmain%2Fjava%2Fengineering%2Fepic%2FAtomicFeedback.java
For example, possible values of Tag in List<Tag> tags are not propagated in the prompt

Hi I am taking a look at this

Hi @LizeRaes, the link does not work any more :(
Do you still remember what was the problem with List<Tag> tags?
Thanks!

@LizeRaes thanks!


Create third_party directory and add yapps to it

Is the yappsrt file in this directory the same as this one? https://github.com/nicksay/spitfire/blob/master/yappsrt.py
If so we should remove the one in the base directory and depend on the one in third_party.

The yappsrt in this directory is the original, and the one in the base directory is our modified copy.  I will move the base directory one here in a second change.

Lgtm


Replicate periodic evoked inputs with rhythmic inputs

Moving this to hnn-core from hnn
From @rythorpe in https://github.com/jonescompneurolab/hnn/issues/208

I currently have a param file with evoked inputs that have periodic spacing. My goal is to replicate the simulation with only rhythmic inputs, however, there seems to be a discrepancy in how synaptic weights are assigned for evoked vs. rhythmic inputs. The following screenshots demonstrate this issue and their corresponding param files are attached. Note that, according to the param files, the synaptic conductancies for proximal and distal inputs are congruent across simulations.

I just transferred the original issue. Closing this in favor of #115


Enable R8 optimization

Blocked by:

~https://issuetracker.google.com/issues/111080693~
~https://issuetracker.google.com/issues/124267873~
~https://issuetracker.google.com/issues/124181030~
~https://issuetracker.google.com/issues/124357885~

Still not working on master though...

#177


Send metrics to a personnal posthog (AND to actual posthog)

Validations

[X] I believe this is a way to improve. I'll try to join the Continue Discord for questions
[X] I'm not able to find an open issue that requests the same enhancement

Problem
Metrics are send to a general posthog.
It could be great to send metrics into our own posthog instance to evaluate teams adoption/usage.
Solution
Add a new custom posthog url in plugin settings
send metrics to actual posthog AND to custom posthog (defined in plugin settings)

We would use this as well

+1 we'd love have this feature as well!

we'd love to have this feature too!


⚠ SceneTime has degraded performance

In d653d5e, SceneTime ($ST) experienced degraded performance:

HTTP code: 200
Response time: 1929 ms

Resolved: SceneTime performance has improved in 7c18662 after 7 minutes.


Pressing tab inside a comment always adds a tab character

When inside a comment block, pressing tab will always add a \t character even with the editor set up to indent with spaces.
To reproduce, just press tab within a comment.
/**
 * 	test
 * 		test 2
 **/
function doSomething() {
    "use strict";
}

Expected:
/**
 *\s\stest
 *\s\s\s\s\s\stest 2
 **/
function doSomething() {
\s\s\s\s"use strict";
}

Actual:
/**
 *\s\ttest
 *\s\t\ttest 2
 **/
function doSomething() {
\s\s\s\s"use strict";
}

Is there any way to configure this?

After update to 0.7.4 problem still exist


[PackageTool] Add update cli for new resolver

It is still hidden behind the --enable-new-resolver flag which is
expected to be removed once we make the switch to the new dep resolver.

this should be ok to merge just need a sanity review

something wrong with commits in this PR


Exclude dont seem to work when using with describe.all

When using describe.all I get error that I need to use args, which is fine.
root@ip-10-27-56-243:~# salt-run describe.all frode
[ERROR   ] Missing positional arg paths for describe.file
[ERROR   ] Missing positional arg sysctl_items for describe.sysctl

But if I try to use exclude, it doesnt seem to work for me.
Unless I am doing something wrong.
root@ip-10-27-56-243:~# salt-run describe.all frode exclude='["file", "sysctl"]'

Passed invalid arguments: argument of type 'NoneType' is not iterable

Usage:

    Run all describe methods against target.

    One of either a exclude or include can be given to specify
    which functions to run.  These can be either a string or python list.

    CLI Example:

    .. code-block:: bash

        salt-run describe.all minion-tgt exclude='["file", "user"]'

    You can supply args and kwargs to functions that require them as well.
    These are passed as explicit kwargs.

    CLI Example:

    .. code-block:: bash

        salt-run describe.all minion-tgt include='["file", "pip"]' paths='["/tmp/testfile", "/tmp/testfile2"]'

    If two functions take an arg or kwarg of the same name, you can differentiate them
    by prefixing the argument name.

    CLI Example:

    .. code-block:: bash

        salt-run describe.all minion-tgt include='["file", "pip"]' file_paths='["/tmp/testfile", "/tmp/testfile2"]'

root@ip-10-27-56-243:~#

I can't get include to work correctly either when using it with describe.all

This one is resolved by handling additional error cases for Salt modules that are unavailable.


Rename _main symbol when linking snippets

Snippets are also a kind of executable, so need the same _main aliasing
logic that executables have.

@swift-ci Please smoke test


No feedback to user when context window is exceeded

The following transcript stopped responding:
https://chatbots.dimagi.com/a/dimagi/experiments/e/f395d3b0-f63f-4b11-827b-dbc990e11735/s/740fee5c-1475-4b02-b0ff-a938fb833987/view/
Based on the length, I assume we've exceeded the context window. This is not urgent in that we reset the chat and all is well. However, I would have expected Sentry to catch an error with the context window length or (better) to alert the user in some way.

I just noticed #206 . @snopoke this might be related?

I don't see any error handling in our code so we can use this ticket to track that.


q

Hello, I don't know if you has any research involving NLP, I want to ask if there is any better pre-training model now, or how to improve Bert

For NLP there are some subsequent work of BERT like RoBERTa/DeBERTa/Electra, and I would recommend a try.


Exception if resources is missing

If statements is used instead of resources, kappa throws a KeyError.
Stacktrace:
deploying
...deploying policy ses_send_mail_dev
Traceback (most recent call last):
  File "/Library/Frameworks/Python.framework/Versions/2.7/bin//kappa", line 9, in <module>
    load_entry_point('kappa==0.3.1', 'console_scripts', 'kappa')()
  File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/click/core.py", line 716, in __call__
    return self.main(*args, **kwargs)
  File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/click/core.py", line 696, in main
    rv = self.invoke(ctx)
  File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/click/core.py", line 1060, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/click/core.py", line 889, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/click/core.py", line 534, in invoke
    return callback(*args, **kwargs)
  File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/click/decorators.py", line 64, in new_func
    return ctx.invoke(f, obj, *args[1:], **kwargs)
  File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/click/core.py", line 534, in invoke
    return callback(*args, **kwargs)
  File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/kappa/scripts/cli.py", line 58, in deploy
    ctx.deploy()
  File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/kappa/context.py", line 222, in deploy
    self.policy.deploy()
  File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/kappa/policy.py", line 138, in deploy
    document = self.document()
  File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/kappa/policy.py", line 52, in document
    for resource in self.config['policy']['resources']:
KeyError: 'resources'

Kappa config:
 dev:
    profile: default
    region: eu-west-1
    policy:
        statements:
            - Effect: Allow
              Resource: "*"
              Action:
                - "logs:*"
            - Effect: Allow
              Resource: "*"
              Action:
                - "ses:Send*"

I see it has been just fixed :)


drop Foreman 2.4 and Katello 4.0

contains #157 for easier rebasing

cc @upadhyeammit - 2.4 is "dead" by now, right? we don't plan any more releases there?
cc @jjeffers - 4.0 is "dead" by now, right? we don't plan any more releases there?

Yeah 4.0 is dead, AFAIK
On Fri, Dec 3, 2021 at 1:59 AM Evgeni Golov @.***>
wrote:

cc @upadhyeammit https://github.com/upadhyeammit - 2.4 is "dead" by
now, right? we don't plan any more releases there?
cc @jjeffers https://github.com/jjeffers - 4.0 is "dead" by now, right?
we don't plan any more releases there?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/theforeman/jenkins-jobs/pull/158#issuecomment-985264421,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACBEA4TTV52TAX4A6EV32LUPBTD7ANCNFSM5JI6ZOWQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

cc @upadhyeammit - 2.4 is "dead" by now, right? we don't plan any more releases there? cc @jjeffers - 4.0 is "dead" by now, right? we don't plan any more releases there?

Considering we can still do the release of 2.4.2 if required before or by 3.1 GA. However if I see the fixes in 2.4.2 as of now then those are not high priority apart from #14409 which is not reproducible all time. As per this we are not doing 2.4.2. But do we need 2.4 to test upgrades to 3.0.z? If I remember then we try the upgrades from N-2 in release pipelines or that has changed?

This is only for building/releasing, n-2 for upgrades is not affected by these changes.

This is only for building/releasing, n-2 for upgrades is not affected by these changes.

Then go ahead!


Visual update and conceptual refinement of left nav in Authoring canvas

@vivekkshankar
(FYI @sangwoohaan )
Today, the scope of the menu bar is bot-(bot project) focused and provides a user with the ability to switch modes and get a 'canvas'/UI catered to that mode: a visual canvas for authoring, a list based view for editing content etc.
Each of the modes have a sub-nav. For most of them they include an 'all' (aggregated view across all) as well as folders/dialogs to allow the user to 'filter' down to a specific scope : the particular dialog (and in the 'Publish' case: the publish profile).
The issue:

In the Authoring canvas, in addition to dialogs, we show 'triggers' or more appropriately: the event handlers that initiate the dialogs. While this is technically accurate (the handlers live at the top level of the dialog, it results in an awkward view for the canvas: the top level dialog is 'empty' and, while reasonably nice looking, basically the 'Select a trigger on the left
navigation to see actions' feels like an error message. We can and should do better.

While PVA has 'trigger phrases' associate to it's topics, they do not have the concept of trigger, event handler or events (other than user input). The more PVA and Composer will be integrated, the more glaring and problematic this issue will become. Our current nav is learnable for devs, but currently does not easily map to existing mental models of navigation or hierarchical structures that people are familiar with (Windows, websites, Mac OS, iOS, Android etc).
To increase impact and set ourselves up to scale, we'll want to align to and build upon familiar patterns and metaphors

Enabling Bot projects that include a bot core with dialogs, KBs and local and remote skills, has led to additional requirements about how to communicate the content of the project in the nav. The functional design was inspired by the 'explorer' view in Visual Studio and Emulator. This functionality is familiar to the MSF developer audience and has not yet been updated to reflect Fluent guidelines and best practices. It would be worth following up with the visual studio team to learn if and when they plan to apply Fluent and to take a look at the workflow of conversation AI development teams, which likely includes using and switching between multiple apps  (composer, visual studio, emulator, pva, webchat etc.

--
@vivekkshankar  As I know you had comments & thoughts about how to improve the navigation (left panel, not the menu bar (gray panel)) - could you take a pass at the following;

Review the requirements above

Review the history of Composer navigation | [Sangwoo's figma is here] | other designs and explorations are here

Collect examples across msft /fluent for (semi) hierarchical navs - which ones we can leverage/build on other than Visual Studio (which is not Fluent-based and is in the process of getting updated)

review most recent functional designs by Sangwoo

Create a handful options to improve the interaction model, ease-of-use (aka leverage more familiar concepts and patterns)

Apply Fluent visuals and design patterns

Love it - I'll take a stab at this :)

Design has been provided and we're building it out. Closing as complete (the design part)


Pulling new FTC changes

Before issuing a pull request, please see the contributing page.

beginning of new season


Dockable widget

Mention in Readme that it is possible to use local storage and create a dockable controller for the widget, thus expanding the possibilities even more.

If you'd like to provide information about how to do that, then I will consider it.

I'll drag out a small example. I'll set an reminder for it.

Here is a minimal example of BroadcastChannel in javascript. One controller.html and a viewer.html: The "controller.html" goes into a "Docakable Panel" (OBS->View->Docks->Custom Browser Docks...". The viewer goes into a browser source in a scene.
The zip-file is complete. Unpack and use the URL from your filesystem inside OBS.
BroadcastChannelAndLocalStorage.zip
e

PS: Had to use the BroadcastChannel because I can't get the dockable widget to connect to the socket. There are differences in the code using websockets from Kruize Control Master to Kruize Control Dockable Widget Master.


allow extensions to StandardMaterial

Objective
allow extending the StandardMaterial with custom vertex/fragment shaders and additional data, to easily get pbr lighting with custom modifications.
Solution

added ExtendedMaterial<M: Material> which contains a standard material and a user-defined material.
added example extended_material showing how to use it
modified AsBindGroup to have "unprepared" functions that return raw resources / layout entries so that the extended material can combine them

note: doesn't currently work with array resources, as i can't figure out how to make the OwnedBindingResource::get_binding() work, as wgpu requires a &'a[&'a TextureView] and i have a Vec<TextureView>.
Migration Guide
manual implementations of AsBindGroup will need to be adjusted, the changes are pretty straightforward and can be seen in the diff for e.g. the skybox example.

Not sure if the PR description is not using the same formatting the CI check expects, but please ignore that comment.

Does this provide an easy way to do something like "use shader code to generate a random color, feed that into the base color of the pbr shader"? Or can we only modify the output, not the input?

Does this provide an easy way to do something like "use shader code to generate a random color, feed that into the base color of the pbr shader"? Or can we only modify the output, not the input?

you can modify the vertex output / pbr_fragment input, so for that particular case i guess you could use vertex colors and override the generated vertex color.
you can't more generally change the material bindings since the pbr_fragment function reads them directly. for that you would have to go one level deeper and construct a PbrInput and use the pbr function directly (you'd also have to duplicate the tonemapping, fog etc as well)...
I could introduce another function so that there's an entry point which takes a PbrInput and calls pbr plus does all the in-shader postprocessing as well. i think that sounds like a good idea.

you can't more generally change the material bindings since the pbr_fragment function reads them directly. for that you would have to go one level deeper and construct a PbrInput and use the pbr function directly (you'd also have to duplicate the tonemapping, fog etc as well)...

I could introduce another function so that there's an entry point which takes a PbrInput and calls pbr plus does all the in-shader postprocessing as well. i think that sounds like a good idea.
Yeah, exactly. I'm thinking of the use case where you want to make procedurally generated materials, but have them work with PBR lighting with proper material information. Like how blender lets you build a shader graph with inputs for the PBR parameters.

you can modify the vertex output / pbr_fragment input

What would be some use cases for modifying the outputs there as opposed to the inputs?
I can see use cases for hooking in before the vertex shader (e.g. heightmapping) and before the fragment shader (e.g. animated texture) but I can't immediately think of anything I would want do that would come at those stages specifically.

What would be some use cases for modifying the outputs there as opposed to the inputs?

vertex output is fragment input, so this is the right place to do animated textures if you want smooth non-linear adjustments between vertexes.
if you meant the fragment output, in the example i modified the output to do some kind of rough cell-shading type thing. i imagine some other mesh-specific (not full screen) post-processing could also fit here.

This looks fantastic! 2 👍's up

Theoretically it would also make sense to extend a Material2d

that's theoretically true, but in practice it's easy enough to make your own material for 2d.
The built in 2d frag shader is only 10 lines long so you can copy/paste it without much drama. pbr.wgsl's frag shader is more than a thousand lines over a dozen files so it's hard to copy/paste and keep in sync over bevy versions, etc, so this extension is more useful there.

I could introduce another function so that there's an entry point which takes a PbrInput and calls pbr plus does all the in-shader postprocessing as well. i think that sounds like a good idea.

Yeah, this could (eventually) enable all sorts of interesting effects, such as decals and procedural water surfaces with parallax mapping.
Maybe we could also have a “inversion of control” pattern, where instead of the extended shader owning the “true” entrypoint, there are multiple “hook”/"override" points that are called back by the main PBR shader in specific places, for example:

After preparing PbrInput (your proposal above)
After fetching each light
After fetching each light's shadows (could be useful for creating “fake” shadows, like in some 3d platformers)
Before combining direct / indirect lights, etc
After the PBR output is produced (the one in the current PR)

Isn't this going to behave differently depending on whether tone mapping happens in the PBR shader (non-HDR camera) or in a separate pass later (HDR camera)?

Isn't this going to behave differently depending on whether tone mapping happens in the PBR shader (non-HDR camera) or in a separate pass later (HDR camera)?

yes it will. i'm not sure that's a huge issue since i would expect the user to use hdr or not exclusively (not mix them and expect the same results). and if necessary the shader defs could be used in the top-level frag shader as well to alter the behaviour.
but i do agree that it would be nice to inject user functionality before the "post-processing" section of the main shader sequence (fog, debanding, etc as well as tonemapping). that, plus jasmine's suggestion about altering inputs, suggests that maybe we should have a handful of core pbr functions (create_pbr_input, apply_lighting, apply_processing) that the standard shader calls in order, and the user could pick and mix / modify intermediate results as appropriate.
i'll try and bring this up to date and try that approach as well in the next week or so.

Moving to 0.12. Seems useful but needs more reviews (and I'd like to consider the design a bit).

i updated this a couple of weeks ago but forgot to comment. i added the ability to intercept and modify the pbrInput struct before lighting is applied, and ability to modify before (or skip) in-shader post-processing (fog, tonemapping, debanding).
it doesn't allow for more fine-grained intercepting (per light, e.g). i'm not sure there's a good way to do that without using virtual functions, which would definitely be a separate pr.

AsBindGroup should imo not create buffers (my material data in arrays in buffers stuff will take care of that) and not create bind groups, as in this PR. So perhaps it needs renaming to AsBindable or something?

Agreed, but lets leave it to a future PR (after 0.12 releases).


Requires a EULA Agreement

Running this module I get the following:
Error: creating EC2 Instance: OptInRequired: In order to use this AWS Marketplace product you need to accept terms and subscribe. To do so please visit https://aws.amazon.com/marketplace/pp?sku=cvugziknvmxgqna9noibqnnsy
│ 	status code: 401, request id: 6784aa53-790a-470c-b3a8-28ebd23a433c
│
│   with module.minikube.aws_instance.minikube,
│   on .terraform/modules/minikube/main.tf line 155, in resource "aws_instance" "minikube":
│  155: resource "aws_instance" "minikube" {

Is there any alternative supported image that does not require agreeing to a EULA?

And what imaged did you configured to be used? Or do you use just the default one? TBH, I do not remember if I ever did any EULA. It uses the regular CentOS image by default. So if it needs something, it is probably some AWS requirement.

@scholzj  thank you so much for the quick response!  I used the default one, it seems it is an AWS requirement.  It can be viewed at https://aws.amazon.com/marketplace/server/procurement?productId=d9a3032a-921c-4c6d-b150-bde168105e42 .  The EULA reads:
CentOS-7 EULA

CentOS-7 comes with no guarantees or warranties of any sorts,
either written or implied.

The Distribution is released as GPLv2. Individual packages in the
distribution come with their own licences.

This is acceptable for our use which is dev testing.  It is probably enough to give users a heads up that this is required nowadays.  Thanks again!


Change nightly build to use main branch

What needs to happen?
We need to switch the nightly build to use the main branch rather than the released version.
We use github actions to run nightly builds. The nightly builds are published using github-pages to public websites. We need to make sure that the "main" branch is being used to create those builds, so that it picks up any merged PRs as they come in.
We also should put the nightly build url someplace discoverable, such as the readme?
QUESTION:
Key detail is that there are situations when we would like simularium-website to use simularium-viewer's main branch as well, but sometimes that may cause breakage. This probably needs to be discussed - could we have two flavors of nightly for simularium-website?
Why should we do this?
Allows us to use merged PRs when doing new dev work without a release.
When does this need to get done?
By end of sprint 7/26

We use github actions to run nightly builds.  The nightly builds are published using github-pages to public websites.  We need to make sure that the "main" branch is being used to create those builds, so that it picks up any merged PRs as they come in.

staging: still use released viewer
github pages: use dev head viewer

Two things went wrong with this once I merged the action in and could run it:

The react router makes the two subdirectories a little broken. My thinking here is that we just make two repos that just host the two folders. https://simularium.github.io/simularium-website/
I installed the viewer using npm i https://github.com/simularium/simularium-viewer.git, but the repo doesn't contain any of the build artifacts (because we ignore them). I made a branch were I un-ignored the build artifacts so I could confirm that was the issue, but I think we should just publish a #dev version of the app on npm instead of using github to host the build artifacts


[DependencyCollector] Add optional reproducer callback

The clang importer in Swift uses its own subclass of the clang
dependency collector. Because it is completely hidden in the clang
importer's implementation, we cannot subclass it from LLDB.
This is an issue for reproducers, because LLDB needs to be informed of
all the files used by clang through the Swift compiler. To solve this, I
added the ability to register a custom callback in the dependency
collector. LLDB can use this callback to be notified, without needing
access to the dependency collector's implementation.

Can this go upstream?

I want to check more thoroughly potential lifetime issues.
Are there other approaches you've considered? So far this extra callback to me looks awkward and I'm curious if we can do better.

Closing this because I plan a different approach.


JavaScript runtime error: Unable to set property 'className' of undefined or null reference.

Unable to set property 'className' of undefined or null reference.
When i click the selected row in a grid i am getting the following error. It should fire gridview_selectedIndexChanged() event. but  it will not fire anything. rather than it will shoe the below error.
Error : JavaScript runtime error: Unable to set property 'className' of undefined or null reference.
Error Line :
    function RowReset(rowIndex) {

        var gridviewID = "<%=grdSearchResult.ClientID%>";
        $('#' + gridviewID)[0].rows[rowIndex + 1].className = 'GridviewScrollItem';

    }

my Requirment is :
When i selecte the particular row, it should highlight the row in diff color at the same time the index value should get display in another gridview
pls. help me to solve this problem. i am unable to find out exact solution for this.

no reply...


How Can I Disable Foreign Key?

Problem
My DB can't use foreign key，If I specify the relation, Prisma will create foreign constraint  automatically.
Suggested solution
I wonder how can I disable the foreign key constraint? All I need is the relation between two tables
So, is it possible
Some Info
here is the schema and sql created by prisma
model Post {
  id          Int           @id @default(autoincrement())
  updateAt    DateTime      @default(now())
  title       String
  type        String
  url         String        @unique
  tags        String
  authorId    Int?
  likes       Int           @default(0)
  isDelete    Boolean       @default(false)
  user        User?         @relation(fields: [authorId], references: [id])
  weeklyPosts WeeklyPosts[]

  @@index([authorId], name: "authorId")
}

CREATE TABLE `Post` (
  `id` int(11) NOT NULL AUTO_INCREMENT,
  `updateAt` datetime(3) NOT NULL DEFAULT CURRENT_TIMESTAMP(3),
  `title` varchar(191) COLLATE utf8mb4_unicode_ci NOT NULL,
  `type` varchar(191) COLLATE utf8mb4_unicode_ci NOT NULL,
  `url` varchar(191) COLLATE utf8mb4_unicode_ci NOT NULL,
  `tags` varchar(191) COLLATE utf8mb4_unicode_ci NOT NULL,
  `authorId` int(11) DEFAULT NULL,
  `likes` int(11) NOT NULL DEFAULT '0',
  `isDelete` tinyint(1) NOT NULL DEFAULT '0',
  PRIMARY KEY (`id`),
  UNIQUE KEY `Post.url_unique` (`url`),
  KEY `authorId` (`authorId`),
  CONSTRAINT `post_ibfk_1` FOREIGN KEY (`authorId`) REFERENCES `user` (`id`) ON DELETE SET NULL ON UPDATE CASCADE
) ENGINE=InnoDB AUTO_INCREMENT=2 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;

Hi @linxixuan — what database are you using? We are discussing how we tackle this internally and want to work on an option to make migrate ignore relations (-> create no foreign keys) soon. In the meantime, you can add previewFeatures = ["planetScaleMode] to your generator and planetScaleMode = true in your datasource and it should do what you want. But these options are for sure going to change soon.

DB is mysql, our DBA suggest us do not use foreign key for some performance reason ;)

@tomhoule hello, your solution is not work. Here is my env
bug

my code
generator client {
  provider = "prisma-client-js"
  previewFeatures = ["planetScaleMode"]
}

datasource db {
  provider = "mysql"
  url      = env("DATABASE_URL")
  planetScaleMode = true
}

env
$ npx prisma -v
prisma               : 2.23.0
@prisma/client       : 2.23.0
Current platform     : darwin
Query Engine         : query-engine adf5e8cba3daf12d456d911d72b6e9418681b28b (at ../../node_modules/@prisma/engines/query-engine-darwin)
Migration Engine     : migration-engine-cli adf5e8cba3daf12d456d911d72b6e9418681b28b (at ../../node_modules/@prisma/engines/migration-engine-darwin)
Introspection Engine : introspection-core adf5e8cba3daf12d456d911d72b6e9418681b28b (at ../../node_modules/@prisma/engines/introspection-engine-darwin)
Format Binary        : prisma-fmt adf5e8cba3daf12d456d911d72b6e9418681b28b (at ../../node_modules/@prisma/engines/prisma-fmt-darwin)
Default Engines Hash : adf5e8cba3daf12d456d911d72b6e9418681b28b
Studio               : 0.393.0

Ah, I think your prisma version is a bit too old, it probably was released around 2.24

@linxixuan Did you try with the latest version to confirm we can close this issue?
Thank you

Can you please open a new issue @sam-bunger? I think your problem is different. Thanks.

Hey @janpio, the problems are different, but the ability to disable foreign key constraints would solve both of them.

The current solution is described above: https://github.com/prisma/prisma/issues/8108#issuecomment-874575155

Hi @sam-bunger – did you manage to figure out how to solve your use-case? I'm hoping to achieve the same where I have a Postgres DB and need to set up a relation that does not have a foreign key constraint.

Hey @bryanc208, I couldn't figure it out. We ended up deciding to stop using prisma for our project, so I haven't had the chance to look around and test if this solution really works, but from this looks of it this PR may have fixed the issue: prisma/prisma-engines#2221

for anyone searching for this and using planetscale in the future foreign key mode .
datasource db {
  provider     = "mysql"
  url          = env("DATABASE_URL")
  relationMode = "prisma"
}


Can you add some documentation about deploying?

Is your feature request related to a problem? Please describe.
We have a decent documentation about developing with Drogon. But not about deploying. Can we run it with reverse proxies? FastCGI? How to make it?
Thanks.

Basically deployment is an application level thing. You can deploy your drogon application like a linux background service. The specific plan depends on everyone's preference.
Of course, you can run it as the back end of a reverse proxy (E.g. nginx), and the configuration of the reverse proxy is no different from other web servers (E.g spring web app).
Drogon is not developed for FastCGI, so I don't think you can call it through FastCGI.

@rbugajewski What do you think about this?

@an-tao I think deployment depends heavily on the rest of the environment.  Do you run it in a Docker container? Is the service part of a Kubernetes cluster? There are so many deployment options that it would be hard to cover all of them, and in the most easiest cases you can either deploy a Drogon-backed service either directly or behind a reverse proxy like nginx, but this isn’t different compared to other applications. Furthermore there are small differences between operating system flavors if you want to run your application as a service / background daemon. There would be so many permutations that documentation would be hard to maintain. I also don’t see a “sanctioned” way, like the one true way to deploy Drogon, because it is so versatile and works great in different environments.
I would say that unless Dragon gets specific deployment functionality (e. g. drogon deploy), there is no need for specific documentation as it is already widely available for the generic case.

@rbugajewski Thanks so much. I agree with you.


Provider's Terraform Registry entry doesn't exist

Describe the bug
The Terraform Registry shows a 404 when trying to access the documentation of the provider.
To Reproduce
Steps to reproduce the behavior:

Go to https://registry.terraform.io/providers/dynatrace-oss/dynatrace/latest/docs
See error

Expected behavior
See the provider documentation

Hello @iuliancristea
I can reach that page without problems.
Any chance it was a temporary problem on the terraform.io server?
Or are you still experiencing the 404 error?

Hello @iuliancristea
I can reach that page without problems. Any chance it was a temporary problem on the terraform.io server? Or are you still experiencing the 404 error?

@Dynatrace-Reinhard-Pilz It's not temporary. It's the same across all networks I've tried with (home, office, VPN) and I'm pretty sure nothing is cached for me in particular. I believe it may be worth reaching out to HashiCorp.

@rpionke @Dynatrace-Reinhard-Pilz I have found the issue. For some reason, I only get the 404 when using Brave. Works fine on Safari (haven't tried other browsers)


[mvn] Update maven wrapper

Build change only to use official maven wrapper as it migrated to maven ownership.

For reproducibility, the update is achieved by running:
mvn -N org.apache.maven.plugins:maven-wrapper-plugin:wrapper -Dtype=source -Dmaven=3.8.4

in the root of the project.


Add DontForce

Add a newtype wrapper whose rnf is a no-op, forcing
nothing at all.
Fixes #1

Should I add a record accessor? Also, what do you think of the name?

It seems to me that there are a family of related type constructors, and we should probably define them all. This might help suggest a better naming scheme.
How rnf acts on them:

rnf is no-op
rnf is seq (this is sufficient for any other evaluation strategy because you can build it using the no-op tc plus an extra thing seq'd on)

And also how to construct:

Constructor rnfs input
Constructor seqs input (automatically given by any newtype)
Constructor does nothing to input (automatically given by data)

And how to destruct (assuming NF a is in whnf)

Destructor returns rnf data
Destructor returns whnf data (automatically given by any newtype)
No guarantee (automatically given by data)

I'm not quite sure what you're getting at. Can you suggest situations where
deconstruction/elimination should do anything at all? On the construction
side, we have (for your three choices, respectively): Identity, NF, and
whatever we want to call DontForce.
On Thu, Jul 21, 2016 at 6:16 PM, Edward Z. Yang<EMAIL_ADDRESS>wrote:

It seems to me that there are a family of related type constructors, and
we should probably define them all. This might help suggest a better naming
scheme.
How rnf acts on them:

rnf is no-op
rnf is seq (this is sufficient for any other evaluation strategy
because you can build it using the no-op tc plus an extra thing seq'd
on)

And also how to construct:

Constructor rnfs input
Constructor seqs input (automatically given by any newtype)
Constructor does nothing to input (automatically given by data)

And how to destruct (assuming NF a is in whnf)

Destructor returns rnf data
Destructor returns whnf data (automatically given by any newtype)
No guarantee (automatically given by data)

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ezyang/nf/pull/2#issuecomment-234401108, or mute the
thread
https://github.com/notifications/unsubscribe-auth/ABzi_fGfhCKFZz6MQx-DUa3_YAXB_4e3ks5qX-_VgaJpZM4JLyZB
.

@treeowl I just updated the comment above to do something more equational.

@ezyang, I've only reviewed parts of your analysis above, but it's interesting anyway. I know it's weird for rnf to do less than seq; it's a dirty trick! But it's a nice trick from an efficiency standpoint, because I can coerce (for free!) a whole container of stuff to a container of stuff that likely won't be touched by rnf (there's really no good reason for an rnf implementation to seq polymorphic stuff that its rnfing anyway). One pattern you've likely seen (I think due to the other Edward) is Once:
data Once a = Once () a

-- Deconstruct
getOnce (Once _ a) = a

instance NFData (Once a) where
  rnf (Once forced _) = forced

-- Construct
once :: NFData a => a -> Once a
once a = Once (rnf a) a

Somewhat humorous names:
newtype BubbleWrap a = BubbleWrap { popBubbles :: a }

instance NFData (BubbleWrap a) where
  rnf _ = ()

data ArmoredBubbleWrap a =
  ArmoredBubbleWrap { crackArmor :: BubbleWrap a }

instance NFData (ArmoredBubbleWrap a)

What's a bit unclear is whether rnf should force the wrapper of armored bubble wrap.


Mixcloud

> pip freeze | grep youtube-dl
youtube-dl==2015.12.9
> youtube-dl https://www.mixcloud.com/Pedestrian/dance-music-for-home-listening-vol1
[mixcloud] Pedestrian-dance-music-for-home-listening-vol1: Downloading webpage
[mixcloud] Pedestrian-dance-music-for-home-listening-vol1: Trying mp3 URL
[mixcloud] Pedestrian-dance-music-for-home-listening-vol1: Trying m4a URL
ERROR: Unable to extract track url; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.

Post the full output of youtube-dl when run with --verbose option.

Apologies for not finding the --verbose flag. Nothing to see here :+1


Questions about soft and hard constraints

Hi @onclave,
we are doing a roster optimization project using GA for our lecture. We have found your project, which is very interesting. But we would like to add some hard and soft constraints to influence the fitness results, unfortunately, we haven't found that concept in the code (but is stated in the research paper).
Where would you add these Constraints, in Service.calculateFitness or Service.decodeGeneticCode or do you have a more enlightened idea with your eventual knowledge of the C code base?
If you want we will do a Pull request with our changes on your codebase.
Thanks for the response.

Hello @sgirardin it’s great that you found this repository useful. So, yes, by default you could just implement you own method to calculate the fitness of every chromosome by changing / implementing the Service#calculateFitness() method. You can directly provide your constraints there.
You can also share with me how you intend to put these constraints around the calculated fitness values and I can directly make it part of the repository too.
One thing is that this codebase was intended to be a POC for NSGA-II for my own research. But since it is gaining traction, I am already working on converting this repository into a package for easier use, while keeping the POC part intact since it is easier to teach the algorithm to others this way. I’m almost done converting it to a usable package. You can share how you intend to put the constraints and I can include it right away. Otherwise the repository is also welcome to pull requests.

Hi @onclave
thanks for your quick response. We have just chosen our Objective functions and the constraints (hard or soft) we want to enforce.
We still need to generate our sets (train service and train drivers) accordingly.
As soon as we have a clearer vision on the needed modifications I'll let you know with pleasure.
Thanks
Simon

Hello @sgirardin
I've pushed an update to the repository which brings major changes to it. I've converted into a fully working package with much more flexibility and customisability in terms of usage. I'm still in the process of publishing to maven central, but you can take a look into the documentation and getting started. While there is more work to do on the documentation, the getting started section shall help you a lot. Do let me know if you need more help.

Hi @onclave
I'm still looking at your changes seems very nice. The documentation seems complete. I'll let you if it's the case :-).
I'll start working on our project and let you know if something may interest you.


Lite basemap parcel lines not lining up with parcel boundaries

The parcel boundaries depicted in the Lite basemap do not line up perfectly with the actual parcel feature service. Why?
The larges offset I've found is in the Vernal area.

Good question. I wonder if @stdavis or @ZachBeck did something goofy with the mxd's when making that cache.

They sure do look funny.

I wonder if it's a transformation method issue. @steveoh What transformation method did you use when reprojecting the data for this service?

I used
Name: GCS_WGS_1984
Angular Unit: Degree (0.0174532925199433)
Prime Meridian: Greenwich (0.0)
Datum: D_WGS_1984
  Spheroid: WGS_1984
    Semimajor Axis: 6378137.0
    Semiminor Axis: 6356752.314245179
    Inverse Flattening:<PHONE_NUMBER>63

I am unsure as to what transformation method was used since arcpy probably chose that for me. What transformation should I explicitly be using?

I haven't ever passed a geographic transformation either. The docs say that it chooses the default one which I'm not sure is correct for Utah. I'm going to ask Sean which one we should be using. Then if we can standardize on one I'm thinking that this issue will go away.

It was a geographic transformation issue and forklift has solved this issue. Things should be lined up now.


fix(tools): move connected to mongo log

Checklist:

[x] I have read and followed the contribution guidelines.
[x] I have read and followed the how to open a pull request guide.
[x] My pull request targets the main branch of freeCodeCamp.
[x] I have tested these changes either locally on my machine, or GitPod.

Closes #51676

This pull request relocates the log function into the run function. However, the connect script is executed first, potentially causing it to throw errors before the log function has a chance to run.

Thank you for taking the time to contribute.
This looks good to me 👍

Thanks, More to come.

Hi @papidb  Congrats on your first pull request (PR)! 🎉
Thank you for your contribution to the page! 👍
We are happy to accept these changes and look forward to future contributions. 📝


coco datasets

train_data_name = 'train.data'
val_data_name = 'val_test.data'
May I ask if you can provide 'train. data' and 'val_test. data'？

These should be located here: https://www.cs.virginia.edu/yanjun/jack/vision/coco.tar.gz


ValidationObserver - Rule Object Syntax

vee-validate: 2.1.7
vue: 2.6.6
Using the ValidationObserver component w/ ValidationProvider it doesn't seem like the object syntax shown for is/is_not rules is fully supported. Can you confirm that this is or is not supported when using validation components and specifically w/ ValidationObservers slot-scope?
For example when I pass an object like :rules="{ is: fieldname }" my forms completely stop rendering IF (and only if) I'm using ValidationObserver's slot scope; and it doesn't seem isolated to any particular rule because :rules="{ required: true }" produces the same results. This is confusing since the object syntax works fine so long as I'm not using ValidationObserver w/ slot-scope="{...}".
Thanks for any additional info on this.

Seems like there is an infinite render loop causing this, I will check it out.


ComposableArchitecture.xcworkspace does not show up in list of recents

Describe the bug
ComposableArchitecture.xcworkspace does not show up in list of recents.
Would love to know if there's something weird with our workspace or if there is a workaround.
To Reproduce
If you open ComposableArchitecture.xcworkspace and close it, you will see that it does not show up in the list of recent projects in Xcode's initial screen or in File > Open Recent.
Expected behavior
ComposableArchitecture.xcworkspace should show up in list of recents.
Environment

Xcode [e.g. 11.4.1]

@mbrandonw It seems related to the fact that the workspace is -inside- the package. If I move it out (see the image below), then it starts showing up in the recents.

Nice! Thanks for that tip.
I think that means we can put the ComposableArchitecture.xcworkspace inside the Examples directory to work around this issue.
I'm giving it a shot right now...

FYI, @mbrandonw It seems Xcode takes the name of the Swift Package the workspace is in, and opens that instead.  If there's a package definition defined, then that becomes the name that shows up in recents, not the actual workspace. I suspect the only 'fix' is to have the workspace be -not- in a swift package folder.

Oh huh. Do you also see ComposableArchitecture.xcworkspace show up there? Or just Examples?
We don't want to pull the workspace out of the package directory because then that means everything would need to be nested another level.

Unfortunately I only see the examples and not the workspace
-Paul

On May 9, 2020, at 5:13 PM, Brandon Williams<EMAIL_ADDRESS>wrote:

Oh huh. Do you also see ComposableArchitecture.xcworkspace show up there? Or just Examples?
We don't want to pull the workspace out of the package directory because then that means everything would need to be nested another level.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

Dang ok. I think it was working for me for a brief moment because I created a blank ComposableArchitecture.xcworkspace and then added everything back to it.

A potential workaround is to rename the examples package to compostable architecture examples so at least that’s in the list, because right now the only thing that’s in the recent list is the compostable architecture library package itself
-Paul

On May 9, 2020, at 5:38 PM, Brandon Williams<EMAIL_ADDRESS>wrote:

Dang ok. I think it was working for me for a brief moment because I created a blank ComposableArchitecture.xcworkspace and then added everything back to it.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

Yeahhh gonna revert and re-open this issue :/

I filed FB7700969 ("Xcode doesn’t remember workspace as a recent project") with Apple.

Here is a way to do it:

Create a blank SwiftComposableArchitecture project
Add a dummy swift-composable-architecture module
Close xcode
move the SwiftComposableArchitecture.proj to a clone of swift-composable-architecture
edit the project file and change the path of the swift-composable-architecture to '.'
open *proj
open manage scheme and add the two targets
convert project to workspace
add case study projects, etc to the workspace

TCA can be accessed from recent, playgrounds can be easily added, etc.

@mycroftcanner Awesome find if this works! Would you like to submit a PR?

Gonna close this out for now since there hasn't been much activity!


Why no directed graph for FloydWarshall, Dijkstra, BFS and BellmanFord

Hi,
What is the reason that you chose to use undirected graphs for the algorithms mentioned in the title? As far as I see, they should all be able to support directed graphs as well.
Thanks!

Hi Simon,
Your point is correct. We chose, as a matter of preference, to write undirected generators whenever such inputs were plausible.
But there should be no restriction on making directed datasets for those tasks. We see CLRS as a dataset generator rather than a fixed dataset, and encourage experimentation on diverse input distributions.
Thanks,
Petar

Hi Petar,
thanks for the quick response and thank you for clarifying! I have not checked all generators in detail, but I think it should be basically setting the flag directed=True. I hope that I will not run into any (silent) issues, but the algorithm implementations seem general at first sight.
Simon


Edit move descriptions for Primal abilities

I'm not sure this is necessary.......

Should I close this, then?

Maybe "if the weather is rainy (Rain Dance, Drizzle, Primordial Sea)"?
A lot of them just say "Rain Dance" instead of mentioning both Rain Dance and Drizzle.

This seems fine, but what about Sunny Day? Would "The sunlight is harsh" be okay?

Updated

"rainy weather" and "sunny weather" seems to cover it

@Marty-D?

I'll wait for @Marty-D to respond before updating, if that is fine.

I'm not sure this is necessary.......

Very much this.
When it says for example, "weather is Rain Dance", it means the weather caused by the move Rain Dance and not the move itself. Since Drizzle uses Rain Dance and Primordial Sea has all of the effects of Rain Dance plus more, and that is mentioned in those descriptions, this is unneeded. Not to mention your short description changes don't actually fit the teambuilder.

I felt that since Rain Dance and Drizzle are being mentioned in the tooltips

Where? What tooltips?


Install R kernel

Install R kernel in Jupyterlab.
Find how to do that (write down steps)

Before we can install the R kernel, we need to have an R version installed.

If that is the case, we can install the IRKernel with conda as follows:

conda install -c r r-irkernel.

To make it available in Jupyter (and in the Launcher) run the command R -e "IRKernel::installspec()

This should work (tested it locally).


Update dependency dagster-postgres to v0.23.8

This PR contains the following updates:

Package
Type
Update
Change
Pending

dagster-postgres (source)
project.dependencies
patch
==0.23.7 -> ==0.23.8
0.23.9

Release Notes

dagster-io/dagster (dagster-postgres)
v0.23.8
New

Backfills created via GQL can have a custom title and description.
Definitions now has a get_all_asset_specs method, which allows iterating over properties of the defined assets
[ui] In filter dropdowns, it’s now possible to submit before all the suggestions have been loaded (thanks @bmalehorn!)
[ui] Performance improvements when loading the Dagster UI for asset graphs with thousands of partition keys.
[dagster-dbt] Dbt asset checks now emit execution duration and the number of failing rows as metadata
[dagster-embedded-elt] Added support for partitioning in dlt assets (thanks @edsoncezar16!)
[dagster-embedded-elt] Added ability to set custom metadata on dlt assets (thanks @edsoncezar16!)
[dagster-graphql] Added a terminate_runs method to the Python GraphQL Client. (thanks @baumann-t!)
[dagster-polars] dagster-polars IO managers now emit dagster/row_count metadata (thanks @danielgafni!)
[dagster-dbt] DbtCliInvocation now has a .get_error() method that can be useful when using dbt.cli(..., raise_on_error=False).

Bugfixes

Fix a bug with legacy DynamicPartitionsDefinition (using partitions_fn) that caused a crash during job backfills.
[ui] On the asset graph, filtering to one or more code locations via the Filter dropdown now works as expected.
[ui] On the asset overview page, viewing an asset with no definition in a loaded code location no longer renders a clipped empty state.

Experimental

The new build_metadata_bounds_checks API creates asset checks which verify that numeric metadata values on asset materializations fall within min or max values. See the documentation for more information.

Documentation

Added details and links to the Schedules and Sensors API documentation
Removed leftover mention of Dagster Cloud from the Dagster+ Hybrid architecture documentation

Dagster Plus

Fixed an incompatibility between build_sensor_for_freshness_checks and Dagster Plus. This API should now work when used with Dagster Plus.
[ui] Billing / usage charts no longer appear black-on-black in Dagster’s dark mode.
[ui] The asset catalog is now available for teams plans.
[ui] Fixed a bug where the alert policy editor would misinterpret the threshold on a long-running job alert.
[kubernetes] Added a dagsterCloudAgent.additionalPodSpecConfig to the Kubernetes agent Helm chart allowing arbitrary pod configuration to be applied to the agent pod.
[ECS] Fixed an issue where the ECS agent would sometimes raise a “Too many concurrent attempts to create a new revision of the specified family” exception when using agent replicas.

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

cf https://github.com/robert-koch-institut/mex-extractors/pull/94


Adding Raku

Just a few changes, can you move the languages into a version directory as like all the other packages.
You will also need to move the v from the version field, other than that all looks good!
Closes #281

Just a few changes, can you move the languages into a version directory as like all the other packages.
You will also need to move the v from the version field, other than that all looks good!
Closes #281

ok I fixed it check the newest commit

one last thing, in the build script you don't need to create a bin dir at the beginning since the archive already contains a bin dir for the prebuilt binaries.
and also the semver check will complain about "6.d" because of the letter in the minor and a missing patch number. I'm not sure what makes sense to use here, but I was thinking "6.0.0-d" instead. It would capture the "d" as a prerelease.

i changed the 6.d thing but for the first thing you mentioned do you just want me to delete the
mkdir -p bin cd bin/
part?

correct. you can delete cd ../ at the end too.
also, I just realized that the "-d" at the end of the version will cause a different issue with building and another for satisfying semver - both of which should probably be fixed if we intend to support prereleases in the future.
but for this, is there just a normal version we can use that follows the semver convention of #.#.# ?

the only other one i could find is by using the date format for example 2021.05 or something for may 2021 but ill try looking more

maybe i can use the ascii value of d which would be 6.100.0 or something lol

works for me

nice


Add k+1 testing

Test k+1th data after k training and find accuracy

https://machinelearningmastery.com/k-fold-cross-validation/


Default signature version changed

Default signature version changed from 2 to 4. Some signature problems have been fixed.

Thanks, @sertangulveren. Does this PR fix #83 if I understand correctly?

Yes, I use it in my own apps. Signature errors have been resolved.

Eline sağlık @sertangulveren


Identity Purification evaluating both 1 and 0 to NULL

Expected Behavior
Identity Purification returns 1 when 1 is passed
Actual Behavior
Identity Purification returns NULL when 1 is passed.
Steps to Reproduce the Problem

Draw Numerical Reflection 1 (Or any logical operation that returns 1)
Draw Identity Purification

Specifications

Mod Verion: 0.9.1
Forge Version: 40.1.69
Minecraft Version: 1.18.2

No longer an issue as of 0.9.4


UUID's in a smart cell chart do not work

Current behavior

query a simple table with UUID's with, say, a count and grouping by the id field
Create a chart that tries to use UUID's on the x axis
Get Error Failed to serialize initial widget data, invalid byte 0xC0 in <<uuid binary redacted>>

Expected behavior
No Error

Notice this happens both on Kino.VegaLite but also on Kino.DataTable.

@josevalim we can't serialize arbitrary binaries into JSON, so isn't this expect for UUIDs in the raw binary format?

@jonatanklosko we can actually encode, but I think the client really dislikes it:
iex(2)> Jason.encode <<0, 1, 2>>
{:ok, "\"\\u0000\\u0001\\u0002\""}

iex> Jason.encode(Ecto.UUID.bingenerate())
{:error,
 %Jason.EncodeError{
   message: "invalid byte 0xAA in <<170, 141, 85, 72, 103, 180, 79, 91, 166, 160, 104, 128, 6, 179, 246, 193>>"
 }}

Oh, I see. And because of #180 the error only happens later, so it is a bit harder to provide earlier feedback?

I think #180 doesn't change much in this specific case as there is no struct involved, so we would get the same error on either side. If we want a more specific error message we would need to match on %Jason.EncodeError{message: "invalid byte" <> _}.

With #180 I was thinking we would at least get an error from Kino and have it show up with stacktrace?

In any case, this can be closed. We might improve things with #180.

With https://github.com/livebook-dev/kino/issues/180 I was thinking we would at least get an error from Kino and have it show up with stacktrace?

Note that the serialization happens on demand, when someone connects to the component and it would be inside the Kino.JS.Live server, so I'm not sure if the stacktrace will be helpful. But maybe there's a way to show more relevant information, we can revisit :)

@the-destro did you manage to work around this issue?
This is practically the only page that comes up when searching for this error message so for anyone interested I solved this by explicitly casting the UUID to varchar in the kino_db smartcell query. Unfortunately it forced me to be explicit in the select statement and not just select * but rather select id::varchar, relation_id::varchar, inserted_at etc...
Hope this helps.


Update java-jwt to 3.18.3

About this PR
📦 Updates com.auth0:java-jwt from 3.18.2 to 3.18.3
📜 GitHub Release Notes - Changelog - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.auth0", artifactId = "java-jwt" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "com.auth0", artifactId = "java-jwt" }
}]

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

Part of

#66
already

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 94.464%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1365

Relevant Lines:
1445

💛  - Coveralls


[BUG] Incorrect context merging when context is passed via get[...]Details/Value()

Observed behavior
When a targetingKey is set on an OpenAPIClient, a subsequent context passed via any of the get[...]Details/Value functions is not being correctly merged and the requested flagKey is evaluated with the context set initially.
Expected Behavior
When a targetingKey is passed as $context for flag evaluation via any of the get[...]Details/Value functions, it should updated a previously set client context. The requested flagKey should then be evaluated with the updated context.
Steps to reproduce
To reproduce, we can consider a simple targetingKey-test flag definition in a flags.json file.
{
  "flags": {
    "targetingKey-test": {
      "state": "ENABLED",
      "variants": {
        "false": false,
        "true": true
      },
      "targeting": {
      "if": [
        {"in": [
          {"var": "targetingKey"},
          ["correct_key"]
          ]
        }, false]
      },
      "defaultVariant": "true"
    }
}

We can then build a new OpenAPIClient and pass it a default string context.
use GuzzleHttp\Client;
use OpenFeature\OpenFeatureAPI;
use OpenFeature\OpenFeatureClient;
use OpenFeature\Providers\Flagd\FlagdProvider;
use OpenFeature\Providers\Flagd\config\HttpConfig;
use OpenFeature\implementation\flags\MutableEvaluationContext;

$api = OpenFeatureAPI::getInstance();
$client = new Client();
$httpFactory = new HttpFactory();

$provider = new FlagdProvider(
  [
    'hostname' => 'localhost',
    'port' => 8013,
    'protocol' => 'http',
    'secure' => false,
    'httpConfig' => new HttpConfig(
      $client,
      $httpFactory,
      $httpFactory,
    ),
  ],
);

$api->setProvider($provider);
$apiClient = $api->getClient('test-client', '1.0');
$apiClient->setEvaluationContext(new MutableEvaluationContext("default"));

We can perform the targetingKey-test evaluation by passing a targetingKey directly in the getBooleanDetails() function.
$flagKey = "targetingKey-test";
$defaultValue = "true";
$updatedContext = new MutableEvaluationContext($targetingKey);

$details = $apiClient->getBooleanDetails($flagKey, $defaultValue, $updatedContext);

We can finally inspect the contents of $details.
var_dump($details);

In the output, we can observe that the value field of the EvaluationDetails object is set to bool(true), whilst it should be set to bool(false).

A fix can be applied by modifying the EvaluationContextMerger.php merge function. Currently, the newTargetingKey from an updated Context is calculated as follows:
$newTargetingKey = null;
if (!is_null($calculatedTargetingKey) && strlen($calculatedTargetingKey) > 0) {
  $newTargetingKey = $calculatedTargetingKey;
} elseif (!is_null($additionalTargetingKey) && strlen($additionalTargetingKey) > 0) {
  $newTargetingKey = $additionalTargetingKey;
}

To compute the $newTargetingKey, it first performs checks on the $calculatedTargetingKey from the $initialContext. However, the if-else blocks should be reversed, as otherwise valid incoming $additionalTargetingKeys are never considered as $newTargetingKeys.
$newTargetingKey = null;
if (!is_null($additionalTargetingKey) && strlen($additionalTargetingKey) > 0) {
  $newTargetingKey = $additionalTargetingKey;
} elseif (!is_null($calculatedTargetingKey) && strlen($calculatedTargetingKey) > 0) {
  $newTargetingKey = $calculatedTargetingKey;
}

Hey @tcarrio, could you please take a look when you have a moment?


Unlicensed?

Since you've put this on Github, I assume you want this to be open source. But I can't see any licensing information anywhere.
Code without a license is covered by normal copyright, and therefore I'm not allowed to copy it or use it in my own projects.
You can get help picking the license you want at https://choosealicense.com/.

An MIT license has now been explicitly called out in the repo.


Partially revert "Pass target type to /search request (#55)"

This partially reverts commit 62350157
We accidentally renamed metricFindQuery() and changed its signature.
Fixes #60

@andig I'll be merging this, feel free to do post-merge review.

 Can't reproduce how I got the notion that was safe to do.
This comment here https://github.com/simPod/grafana-json-datasource/pull/63/files#diff-04c6e90faac2675aa89e2176d2eec7d8R58 seems unrelated- I guess it can be empty if nothing's chosen in the Grafana UI and it doesn't apply a default?

@andig the /search request can be issued through Settings -> Variables and there's no way to select type.
https://github.com/simPod/grafana-json-datasource/pull/63/files#diff-d08c5e2aaf65d640a9e2fce1af5b062cR95-R97
But we should handle it better so it's not part of the request when value is undefined. WDYT?

Either undefined or we assume timeseries? Kinda funny way the grafana api is designed...

Well, I have no idea what the use case for it might be 😄But generally, I'd not try assume things.
@denisidoro @csanz91 would you be able to tell us what you use /search request through Variables for?
@andig do you think it's better to send undefined for type rather than omitting it?

@andig do you think it's better to send undefined for type rather than omitting it?

I really wouldn't care, both should work.


remove stray quotation marks in question_full.jsonll

Why are these changes needed?
There is a stray quotation mark in JSON format in question_full.jsonl so that one raises error on json.load()
Related issue number (if applicable)
none
Checks

[ ] I've run format.sh to lint the changes in this PR.
[x] I've included any doc changes needed.
[x] I've made sure the relevant tests are passing (if applicable).

@polm-stability @leemengtw
Could you review this PR? 🙏

Sorry for never replying to this! Not sure how I missed either the initial issue with the quote or this PR. It looks like a good fix to me :+1:


Add hazards

Could be interesting to also include hazards into the mix. Might me out of scope and could be hard to fit into the existing table due to different columns (e.g., complexity, hazard type)

I think this could be only done by having a sort of checkbox like
[x] Hazard
And then the backend will return strings representing the hazard, stored in the be database without being reflected in the frontend table


Mapper gets lost after filtering

Not sure if this is an intended behaviour, but i was suprised:
    DATA:
      BEGIN OF ls_test,
        text TYPE string VALUE `ABC`,
      END OF ls_test.

    DATA(test) = zcl_ajson=>create_empty( ii_custom_mapping = zcl_abapgit_ajson_mapping=>create_upper_case( ) ).

    test->set(
        iv_path = `/`
        iv_val  = ls_test ).

    DATA(lv_result) = test->stringify( ). "{"TEXT":"ABC"}

    DATA(test_filtered) = test->filter( zcl_abapgit_ajson_filter_lib=>create_empty_filter( ) ).

    test_filtered->set(
        iv_path = `/`
        iv_val  = ls_test ).

    DATA(lv_result2) = test_filtered->stringify( ). "{"text":"ABC"}

    "expected:  "{"TEXT":"ABC"} -> mapper got lost?

The returning object of the filter fucntion does not get the mapping of the original object:

But maybe my understanding of the API was just wrong and everything is fine like this.

Sorry for late response. Well ... looks like a bug on the one hand. But on the other the ii_custom_mapping is a deprecated feature - https://github.com/sbcgua/ajson?tab=readme-ov-file#mapping-via-to_abap-and-to_json-deprecated - in favor of filter method. So I'd better not rely on this particular feature but use the filter approach instead.

ah thank you for the hint, overlooked that this is deprecated, in my specific situation i use now the following APIs and it works as i would expect:
        DATA(lo_json) =  CAST z2ui5_if_ajson( z2ui5_cl_ajson=>new( ) ).
        lo_json->set( iv_path = `/` iv_val = val ).

        IF config-custom_mapper IS BOUND.
          lo_json = lo_json->map( config-custom_mapper ).
        ELSE.
          lo_json = lo_json->map( z2ui5_cl_ajson_mapping=>create_upper_case( ) ).
        ENDIF.

        IF config-custom_filter IS BOUND.
          lo_json = lo_json->filter( config-custom_filter ).
        ELSE.
          lo_json = lo_json->filter( z2ui5_cl_ajson_filter_lib=>create_empty_filter( ) ).
        ENDIF.

Good to know! So the issue can be closed?

yes thanks for the help!


Generate vk_dispatch_table_helper.h files using vk.xml

Generating these header files was done via vk-generate.py based on parsing the header or hand-edited API metadata scripts.  Moved to using standard codegen.  Def files are next (will remove the vk-generate script after all functionality is migrated and trunk merges are complete).

Cody verified, pushed to Master.


Changes to model in beforeUpdate hooks not persisting to model when saved

Consider password encryption per : Basic Example
Works perfectly using beforeCreate hook
However, when using beforeUpdate hook, with the same hook method, the unencrypted password is persisted to the db when using using model.save() from the controller, even though this.password in the hook shows encrypted value
// controller
const user = yield User.findBy('id', 1)
user.password = 'password_1'
yield user.save()

// hook, which DOES get called
User.encryptPassword = function * (next) {
  if (this.password) {
    this.password = yield Hash.make(this.password)
  }
  console.log('encryptPassword', this.password) // '$2a$10$s8K2HOKlSISYTxvPpRJRJOmBZzZWIWfx7k1Tx6bC7r/MCRROGa7jm'
  yield next
}

// password persisted to the db = 'password_1'

Hi @tremendus !
Which version of adonis-lucid are you using?

package.json:
    "adonis-ace": "^3.0.1",
    "adonis-auth": "^1.0.0",
    "adonis-commands": "^2.1.0",
    "adonis-fold": "^3.0.2",
    "adonis-framework": "^3.0.0",
    "adonis-lucid": "^3.0.1",
    "adonis-mail-provider": "^2.0.0",
    "adonis-middleware": "^1.0.6",

looks like it pulled 3.0.1, from lucid package.json "_id"<EMAIL_ADDRESS>

Oh, I see where you're going. let me update and see.

@tremendus Yes this issue was reported earlier https://github.com/adonisjs/adonis-lucid/issues/44 and fixed in version 3.4 https://github.com/adonisjs/adonis-lucid/releases/tag/v3.0.4

Ok, confirming this update does fix it. Thanks.


Looking forward to get involved and contribute to the community 🎉

First Name
Rutvik
Last Name
J
Discord Username (if applicable)
Rutvik J#6028
Let us understand your motive.
I have been part of SidHacks from Day 1 and find it amazing to share and gain valuable insights. I can contribute my knowledge in various domains of Blockchain, Quantum computing and everything I am learning so far.

Hey @RutvikJ77 👋🏻
Thanks for requesting an invite! Welcome to SidHacks Community 🎉
Before going ahead, I would want you to complete the below To-Do list.
Your To-Do List ✔

Accept the invitation sent to you via mail.
Change the appearance of this organization to "Public" from the people list here.
Join our Discord Server here.

Accept the Rules from #📓〡rules channel.
Introduce yourself to our community in 👋〡introduction channel.

Feel free to share your excitement on socials with #SidHacksCommunity. You can also tag me @siddharth_hacks.

Close this issue once you complete all the above points.

Looking forward to interacting with you in our community! Welcome once again! 🤓


requester pays on a dask gateway cluster?

Does anyone have a working example of using requester_pays=True on a dask gateway cluster?
The requester pays notebook works, but doesn't really use a gateway cluster.  The cell at the end purports to show how to pass the env to the dask workers, but the env is not a dict -- I don't think it works?

I eventually figured this out, and I didn't need to use the rasterio Env object.    Here's a notebook showing a Dask Gateway cluster running on Qhub, accessing requester-pays Landsat data, extending the Landsat example from the Element84 Geo-Notebooks repo

cc @scottyhq !


Allow Debian8 as an option to vmDestroy.sh

Signed-off-by: Stewart Addison<EMAIL_ADDRESS>

I was planning on doing this yesterday when I saw it didn't work- I'm probably going to try and do it like the vagrantPlaybookCheck.sh is done, so we don't have to keep changing it :-)


Fix elasticsearch query and index

Fixes #1162

Codecov Report

Merging #1167 into 2017.10 will increase coverage by 0.3%.
The diff coverage is 98%.

@@            Coverage Diff            @@
##           2017.10   #1167     +/-   ##
=========================================
+ Coverage    68.89%   69.2%   +0.3%
=========================================
  Files          113     114      +1
  Lines         6163    6212     +49
  Branches       751     754      +3
=========================================
+ Hits          4246    4299     +53
+ Misses        1746    1744      -2
+ Partials       171     169      -2

Impacted Files
Coverage Δ

saleor/search/backends/elasticsearch.py
0% <ø> (ø)
:arrow_up:

saleor/product/models.py
89.27% <ø> (ø)
:arrow_up:

saleor/settings.py
87.06% <ø> (ø)
:arrow_up:

saleor/search/backends/dashboard.py
0% <0%> (ø)
:arrow_up:

saleor/core/templatetags/shop.py
90% <100%> (+10%)
:arrow_up:

saleor/product/filters.py
100% <100%> (ø)

saleor/core/permissions.py
100% <100%> (ø)
:arrow_up:

saleor/core/utils/random_data.py
81.57% <0%> (-0.38%)
:arrow_down:

saleor/product/utils.py
85.36% <0%> (+2.43%)
:arrow_up:

... and 1 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 cbfd8bd...7b7d934. Read the comment docs.


A new flipper

I hope this works with archibot, and that I'm allowed to add new maps, don't know if I need to specify path to map better.

I'll merge it later today, sorry for delay :+1:


Is there currently a way to support HTML5 and touch backends at the same time?

I know that react-dnd-touch-backend exists, but is there a way for that and the HTML5 backend to be in effect simultaneously?  I'm thinking of the fact that touchscreen laptops exist.

I know that react-dnd-touch-backend exists, but is there a way for that and the HTML5 backend to be in effect simultaneously? I'm thinking of the fact that touchscreen laptops exist.

You can write a backend that performs some kind of check for touch support and delegates processing to either one or the other backend.
For example see supportsTouch() in this old proof of concept PR: https://github.com/gaearon/react-dnd/pull/143/files

Oh - that PR handles either/or, but not both/and -- I'm thinking of some kind of that responds to both HTML5 DnD and touch events, even if it just delegates to the existing HTML5 and touch backends.

Yes, you can create a backend that will call the appropriate backends' functions.
Take a look at backends/Test to get an idea of backend's minimal API.

Cool, I made a backend to call these methods of the backends it wraps, and it appears to work well so far!  Adding some basic DnD to my app has been pretty easy so far, thanks for this library!
setup
teardown
connectDragSource
connectDragPreview
connectDropTarget

I'm glad!

@jedwards1211 is that code you can share?

Yeah it's here: https://github.com/jcoreio/react-dnd-multi-backend
I never published it to npm though because I didn't spend enough time digging into the code of react-dnd to be confident that it would work in all situtations, and then someone else beat me to the punch with a package of the same name 😄  which is here and has seen more development effort: https://github.com/LouisBrunner/react-dnd-multi-backend

https://www.npmjs.com/package/react-dnd-multi-backend i use this ,as @jedwards1211  says


GitHub Actions Concurrency

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


import WeibullAFTFitter shows: No module named 'future.utils'

I'm trying to experiment the WeibullAFTFitter. I upgraded lifelines to 0.20.4 using pip. However, when I tried to import WeibullAFTFitter, it reported ImportError: No module named 'future.utils'
I checked my environment, there is future package (0.17.1) installed.

hm, thanks for the report. Let me investigate a bit. Can you post the entire stacktrace?
What version of pandas do you have installed? pip freeze will show you.

Can you confirm that 0.20.3 doesn't have this problem, also?

Hi, thanks for getting back to me. My pandas==0.24.2
the full stack of error is as follows. I tried 0.20.3 and it has the same problem.

from lifelines import WeibullAFTFitter
Traceback (most recent call last):
File "", line 1, in
File "C:\Anaconda3\envs\experiment_env\lib\site-packages\lifelines_init_.py", line 4, in
from lifelines.fitters.weibull_fitter import WeibullFitter
File "C:\Anaconda3\envs\experiment_env\lib\site-packages\lifelines\fitters_init_.py", line 16, in
import autograd.numpy as anp
File "C:\Anaconda3\envs\experiment_env\lib\site-packages\autograd_init_.py", line 2, in
from .differential_operators import (
File "C:\Anaconda3\envs\experiment_env\lib\site-packages\autograd\differential_operators.py", line 12, in
import autograd.numpy as np
File "C:\Anaconda3\envs\experiment_env\lib\site-packages\autograd\numpy_init_.py", line 2, in
from .numpy_wrapper import *
File "C:\Anaconda3\envs\experiment_env\lib\site-packages\autograd\numpy\numpy_wrapper.py", line 6, in
import autograd.builtins as builtins
File "C:\Anaconda3\envs\experiment_env\lib\site-packages\autograd\builtins.py", line 2, in
from future.utils import with_metaclass
ImportError: No module named 'future.utils'

hm, I can't see why it would fail. Can you confirm
conda install -c anaconda future

runs without failing?

Hi Cam, I figured it out. It's the problem with the pip installed version of future. I uninstalled it and reinstalled with conda. Now it is working. Thank you!

I have the same problem.


Create a differentially private victim model

Is your feature request related to a problem? Please describe.
This would increase the variety of victim models for quick prototyping. Presently, PrivacyRaven only provides a three layer classifier trained on the MNIST dataset as a victim model.
Describe the solution you'd like.
A lightweight model written using Opacus is preferable.
Describe alternatives you've considered.
The model can also be built with TensorFlow Privacy or PySyft.
Detail any additional context.
This victim model could also be used inside of examples, reinforcing and/or extending the results from this paper among others. Multiple people can work on this issue.

Assigned!


Some flags on tsconfig.json not read

Hello, just want to follow up on issue #158 which you closed earlier. There is no problem with my tsconfig.json. The same config worked, all I had to do is run npm install typescript on the local project folder. Guess the bundled typescript in this extension emits the weird behavior as it's not reading config file properly.

Can't reproduce, please check https://github.com/neoclide/coc-tsserver/blob/master/Readme.md#troubleshooting


RT-8: Singleton with breakouts

Initial commit of RT-8: Singleton with breakouts .
Resolves https://github.com/openconfig/featureprofiles/issues/2391

Pull Request Functional Test Report for #2516 / 78fbd408af21b91cd1020eedfee4f60c1f6646ef
Virtual Devices

Device
Test
Test Documentation
Job
Raw Log

Arista cEOS

RT-8: Singleton with breakouts

Cisco 8000E

RT-8: Singleton with breakouts

Cisco XRd

RT-8: Singleton with breakouts

Juniper cPTX

RT-8: Singleton with breakouts

Juniper ncPTX

RT-8: Singleton with breakouts

Nokia SR Linux

RT-8: Singleton with breakouts

Openconfig Lemming

RT-8: Singleton with breakouts

Hardware Devices

Device
Test
Test Documentation
Raw Log

Arista 7808

RT-8: Singleton with breakouts

Cisco 8808

RT-8: Singleton with breakouts

Juniper PTX10008

RT-8: Singleton with breakouts

Nokia 7250 IXR-10e

RT-8: Singleton with breakouts

Help

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 52.141%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1668

Relevant Lines:
3199

💛  - Coveralls


Fix snippets testing

@bot-gradle test RFM

OK, I've already triggered ReadyForMerge build for you.


$PSStyle cause issues in the PowerShell  Console

Simple repro
Write-Verbose -verbose "verbose";Write-Output "out"

expected output

Actual results

VSCode reproduce
$PSVersionTable

$PSStyle.Formatting.Warning = $PSStyle.Background.Magenta + $PSStyle.Foreground.Yellow + $PSStyle.Bold + $PSStyle.Italic
Write-Warning "Colours!"

Expected behavior

and something like this:

Actual behavior
Notice the yellow:

Environment data

Name                           Value
----                           -----
PSVersion                      7.2.0-preview.2
PSEdition                      Core
GitCommitId                    7.2.0-preview.2
OS                             Microsoft Windows 10.0.19042
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

Also worth looking at .NET Interactive - another pshost.

Hmm I can't repro the color leaking.  As for the style not taking effect, yeah every custom host will need to implement this themselves.
It would be nice if ConsoleHost was redesigned somewhat to be inheritable. That doesn't really help PSES and such right now unless it's polyfilled but it would save a lot of headache in the future.

As for the style not taking effect, yeah every custom host will need to implement this themselves.

I think we need a bit more platform-oriented thinking here

I think we need a bit more platform-oriented thinking here

Yeah I'm with ya there. I'm not really sure how though, those streams don't make it to anything like the formatter where this could be processed in a host agnostic way.  In most cases MshCommandRuntime.WriteVerbose goes directly to PSHostUserInterface.WriteVerboseLine.
Another challenge is that escape sequences do not do much to describe what a GUI host should do.  I didn't see the PR at the time, but if I did I would have recommended removing the customizations of the other streams until this was fleshed out a little bit more.

This seems to be working fine with 7.2-preview.8

I think this is a dupe of https://github.com/PowerShell/PowerShell/issues/14506 which was already fixed

$PSStyle.Formatting.Warning = $PSStyle.Background.Magenta + $PSStyle.Foreground.Yellow + $PSStyle.Bold + $PSStyle.Italic
Write-Warning "Colours!"

This doesn't produce the magenta background, but otherwise things seem to be working.


AKTable Crash

Occasionally when creating an AKTable my app will crash with the following error: Thread 1: EXC_BAD_INSTRUCTION (code=EXC_I386_INVOP, subcode=0x0)
Here is my code:
let file = try AKAudioFile(forReading: url)   let table = AKTable(file: file)
Attached is one of the audio files that is causing a crash
Criminal.wav.zip

Hmm, I don't know how actionable this issue is. Thanks for the wav, but a project or playground that demonstrates the error would be what we would need. I'll re-open this issue if you can get a demo or more info.


Changing to Opaque, Premultiplied doesn't exist for metal I think

this was crashing when I tried to run it for the first time.  Simple change.  Thanks for making this repo.

Thank you.


Array query parameter support

Let's say I have a query parameter called names that takes an array: [john,jane,james]
When I try to specify this array in swagger (with hapi-swagger) it outputs this format which doesn't work for me: %5Bjohn%2Cjane%2Cjames%5D
The server expects the format to look more like:
names[]=john&names[]=jane&names[]=james
I think we have to turn on collectionFormat=multi to make this work. See this issue: https://github.com/swagger-api/swagger-spec/issues/49
Do we support this functionality?

Thanks for pointing out the issue.  I believe the issue: https://github.com/swagger-api/swagger-spec#49 you mention, relates to the latest version of the Swagger spec v2.x
Unfortunately hapi-swagger is still on an earlier version for the Swagger spec v1.2. I am waiting for another bug to be fixed https://github.com/swagger-api/swagger-js/issues/189 to make it worthwhile upgrading hapi-swagger plug-in to the latest spec v2.x
Hopefully once I have upgraded to the newest version of the spec we can fix this problem.

Thanks for looking into this. :+1:

This seems to still be an issue, are there any immediate plans to fix this?

Was hoping to do this at the beginning of the summer, but I have been working on some open source stuff for Mozilla which has taken up all my time. Its still on my list, but getting dates out of Mozilla for when the current project will finish seem almost impossible. Doing two large side projects once it not a goer.
So sorry I cannot commit to a timeframe, but its on the list.

HI the plug-in moved to v2.x of Swagger UI in December 2015 and now supports collectionFormat = multi which means you can now collect arrays query parameters. If you create a route as in the example below:
{
    method: 'GET',
    path: '/store/',
    config: {
        handler: function(){},
        tags: ['api'],
        validate: {
            query: {
                numbers: Joi.array().items(Joi.number())
            },
        }
    }
}

you should be able to call it with http://localhost:3000/store/?numbers=6&numbers=7&numbers=8 and the Swagger Ui will provide a interface to add more than one number.
Sorry it has taken so long the fix this issue


When will you Upload the re-implementation code of baselines discussed in the paper

Hi @JohnnyPeng18 ,
Thank you very much for open-sourcing!
As indicated in the README, I wonder when you will Upload the re-implementation code of baselines discussed in the paper. Thank you.

+1, I'm also curious about the code of baseline in this exciting work. When would u upload it to this repo @JohnnyPeng18 ?
Thx a lot 🤣~