Revisited add-admin action

Overview

Rationale

Juju Events Changes

Module Changes

Library Changes

Checklist

[ ] The charm style guide was applied
[ ] The contributing guide was applied
[ ] The changes are compliant with ISD054 - Manging Charm Complexity
[ ] The documentation is generated using src-docs
[ ] The documentation for charmhub is updated.
[ ] The PR is tagged with appropriate label (urgent, trivial, complex)

There were a few methods that needed to be considered. In the end, after discussion with @nrobinaubertin and @amandahla I have decided to create a new rake patch -
This approach was chosen for a few reasons:

This does not append to the end of a pre-existing file. This is a more robust solution as it is not dependent on replacing some code. Can lead to less conflicts, as all additional processes are in one file.
Clear to see all (non-merged upstream) rake commands we have written
Clearly defines a user:create and admin:promote endpoints. Although technically, we could use the admin:create endpoint and pass in different parameters, to create a user and input n to not grant admin privileges, this does not seem entirely clear in the code without referencing the upstream definition of the method. Additionally, both me and Amanda agree that such methods, especially the user:create, should exist in the user rake commands. I want to submit a PR to discourse to attempt to have these supported upstream.

Additionally, the previous rake patch to add user:anonymize has been removed, since this has been merged to discourse in version 3.2.0, which is what we use in rockcraft.

rather places additional rake commands in a canonical.rake file

I would name it something like discourse-charm.rake to avoid tying it directly to the Canonical name (it's not a patch specifically for our needs but for the charm's needs)


Add link to top of README noting newer version

@johnagan - as discussed in Twitter DM, feel free to wordsmith this addition to the top of the README to direct folks to an alternative and newer version of this code base.
Thanks!

Thanks @marks!


publish<EMAIL_ADDRESS>

Requested by: @lobsterkatie
Merge target: 7.x
Quick links:

View changes
View check runs

Assign the accepted label to this issue to approve the release.
Leave the #retract comment under this issue to retract the release (original issuer only).
Targets

[ ] aws-lambda-layer
[ ] gcs
[ ] github
[ ] npm
[ ] registry

Targets marked with a checkbox have already been executed.  Administrators can manually tick a checkbox to force craft to skip it.

We want to skip AWS since this is a beta.

#retract
There have been branch updates in the meantime, and even though we're trying to skip AWS here, it's still messing things up. Will try again after we do some more work on it.

#retract


SDXL to SD 1.5

If I train a SDXL Lora and decide to use it on a SD 1.5 model, will it work using X-Adapter?

Unfortunately that the otherway that it's working 1.5 to SDXL models.
 I'm sorry... I apologise for my rudeness up to now.

Unfortunately that the otherway that it's working 1.5 to SDXL models.
Would also love the possibility to use SDXL Lora on 1.5 (because most of my trained lora are on SDXL but Animatediff sucks with SDXL :<)

So that's a no?

@Nebuluss I wonder if there are ways to fit between different types of SDXL (Pony v Illustrious for example) and also towards SD1.5 finetunes into a 3-way system... Not sure A-to-B implies B-to-A
In the future maybe Flux and AuraFlow can also provide some help


Fix test failure on JDK 15+

Built on top of https://github.com/hibernate/hibernate-reactive/pull/429

OK,  adding the JDK 8 is not as straightforward as I thought.
I will have a better look tomorrow

@DavideD @Sanne The default build already uses JDK8. I don't see the point of adding it again in the JDK matrix?

@DavideD Also, it looks like you're having trouble to add JDK8 because... for some reason Gradle is producing Java 11 bytecode. I'm investigating.

@DavideD Got it. I fixed the problem and added a build that tests with JDK8 to the JDK matrix. It's probably a waste of resources, but I suppose we've got plenty at the moment :)

(@DavideD Beware: I force-pushed to your branch)

@yrodiere That won't work

OK, forget what I said.
My comment refers to the fact that I'm sure yesterday I've sent the same change and the build failed.
But it was late and I suspect my commit wasn't exactly the same.
Thanks @yrodiere

@DavideD As discussed, I pushed a few more commits:

When testing against JDK15 for example, we don't just run tests with JDK15: we also compile tests with JDK15 and use -release 15. That way, we really simulate an application using JDK15 for everything, while relying on our own binaries built for JDK8.
When testing against JDK 11 / 15 / 16, we now build the main code with JDK 8, not 11. That way, the produced binaries are identical to what we will actually release.
Simplify the Gradle code. Not strictly necessary, but I think it's clearer that way, and more importantly it will be easier to adapt in the future. That's important because I intend to port this code to ORM (next week).

I think @Sanne will be pleased with item 2 in particular.

LGTM

Really nice

Merged https://github.com/hibernate/hibernate-reactive/pull/430

this is great! thanks again


Add Footer for Homepage

What is in a footer?
It typically contains a copyright notice, link to a privacy policy, sitemap, logo, contact information, social media icons, and an email sign-up form.


Inferschema

The following are the issues with Infer schema:

It will help if the class can be passed as the parameter and spark-csv uses the custom class to Infer the schema.
There is no support for Date, DateTime with a custom format
Number formats should have a option to specify the thousand separator, as well as negative formats

I've recently added some support for basic Date formats to my fork of spark-csv. Tests are still needed before I'd be comfortable submitting a pull request but is this something that would be useful in the master branch?

Yes, please feel free to submit your PR.

No worries. We are not using spark-csv I have written a schema inferred
which generates a parquet schema. I am sotastically identifying the sample
based on history and using to identify the schema
On 16 Feb 2016 15:28, "Matthew Stafford"<EMAIL_ADDRESS>wrote:

I've recently added some support for basic Date formats to my fork of
spark-csv. Tests are still needed before I'd be comfortable submitting a
pull request but is this something that would be useful in the master
branch?
—
Reply to this email directly or view it on GitHub
https://github.com/databricks/spark-csv/issues/266#issuecomment-184728912
.

@m-stafford @falaki Could I try if you guys are not working on this?

Sure. I think the most important one for now is Date and time format.

I will submit a PR within tomorrow.

@falaki @m-stafford @saritseal  Could we maybe close this? This is just fixed in #280.


Difference between TF2.4 and TF2.2[MKL]

I am working on project and we are trying to make TF use functions that we have written, these functions are there in the form of a .so file, we managed to get Tensorflow2.2 to use our MatMul function, but it stopped working for TF2.4. We achieved our aim in TF2.2 by using LD_PRELOAD, Any guesses as to why this has happened. An important detail is that both of these TF environments we built from source with MKL support (--config=mkl)
Also these are the function defined inside our .so file (nm command on the .so file, screenshot)

I am working on project and we are trying to make TF use functions that we have written, these functions are there in the form of a .so file, we managed to get Tensorflow2.2 to use our MatMul function, but it stopped working for TF2.4. We achieved our aim in TF2.2 by using LD_PRELOAD, Any guesses as to why this has happened. An important detail is that both of these TF environments we built from source with MKL support (--config=mkl)
Also these are the function defined inside our .so file (nm command on the .so file, screenshot)

@penpornk can you help please?

I am assuming you are providing your own implementation of cblas_gemm. We made some changes between 2.2 and 2.3 and no longer call clbas_gemm, instead we use dnnl_sgemm.  If you want to TF+MKL to use cblas_gemm you have to change the code.
https://github.com/tensorflow/tensorflow/blob/master/tensorflow/core/kernels/mkl/mkl_matmul_op.cc#L174  and recompile. Note, we will removing the cblas calls soon.

If you will be removing Cblas, then what will it be repalced by?.... Thanks! for the reply

@agramesh1

@electricSamarth
auto eigen_tp = MklDnnThreadPoolWrapper::GetInstance().CreateThreadPoolPtr(ctx);
what does this bit here do?
A: it's used for thread pool.
what is the difference b/w dnnl_sgemm and dnnl_sgemm_tp
A: not use thread pool or use.

ThankYou @NeoZhangJianyu ! :)


undefined is not an object (evaluating 'RNFetchBlob.DocumenDir

This error continues, even doing the react-native-fetch-blob-expo import, did you have any fixes?

Sorry for late reply, I am using expo sdk 22 and it is working fine for me.
Please make sure you have link your project correctly


Improve ATS example

@SentinelWarren Can't we just do this?
val () = println! "Hello World"

We can't, will actually need foo main () for the code execution just like in C. Where as implement is the keyword for defining the function main0. ATS programs starts at main0 function.
That said implement main0 () = println! "Hello World" could be near the val () = println! "Hello World" outcome in this case where as we will just pass the value of println! function direct to the function main0 without pre defining the value using val keyword.

@SentinelWarren Can't we just do this?
val () = println! "Hello World"

We can't, will actually need main () function for the code execution just like in C. Where as implement is the keyword for defining the function main0. ATS programs starts at main0 function.
That said implement main0 () = println! "Hello World" could be near the val () = println! "Hello World" outcome in this case where as we will just pass the value of println! function direct to the function main0 without pre defining the value using val keyword.

@SentinelWarren So you mean we can do this?
implement main0 () = println! "Hello World"

@SentinelWarren So you mean we can do this?
implement main0 () = println! "Hello World"

@Richienb Yes ofcourse we can.


[JENKINS-49506] Whitelisting classes used by BuildImageStepExecution.BuildImageTask

Compatibility with https://github.com/jenkinsci/jenkins/pull/3120. Better would be to return plain types if possible.
BTW BuildImageStepExecution is a AbstractSynchronousStepExecution which is wrong. It should be a SynchronousNonBlockingStepExecution, as its run method can block on the network.
@reviewbybees

Created https://issues.jenkins-ci.org/browse/JENKINS-49506 as a follow-up.
@reviewbybees done

@iocanel did you have a chance to take a look at this pull request? Thanks in advance


Issue #2064 - Bootstrap PSIRT

Bootstrap Vulnerabilities
Primary Source: https://snyk.io/vuln/npm:bootstrap
There are a handful of bootstrap components which have XSS vulnerabilities.   These are almost all due to attribute values not being properly sanitized before being used as a selector (which can cause the scripts/html to be executed).
For each of the below, teams that are already on the 3.3.x series of bootstrap can simply upgrade to 3.4.1+ to fix this.
With that issue being reported, we would need to update Fuel3 in general since it relies on Bootstrap 3.x.
More information along with a list of vulnerabilities can be found on the snyk website.

Could one of you please review this?  This is for the bootstrap PSIRT that has been raised.
@bohawi @tweettypography @jacobroschen

A small concern with this is that the bootstrap upgrade will enable sanitization mode by default for tooltips.  If a consumer is using certain HTML in tooltips this could start to break their functionality with the next bower update or npm update.  We ran into this issue in the Content Builder application which has a tooltip that contains a <form>

Agreed.   We would just need a way to just inform everyone about this so they are made aware of it and what to expect.   sanitize: false would simply be necessary when html: true in that case i think


Ability to give relative date as a prop for DatePicker

It would be nice to give a prop to a DatePicker for setting the relative date range. For instance, one could choose to give a default range when rendering the DatePicker.

Pull request: https://github.com/tremorlabs/tremor/pull/131


Give markers another option to update the popup layout after loading compiled content without ngInclude

I do have the problem that after compiling the marker popup content, the size of the popup is not re-calculated. Afaik the popup size is only updated when the message includes the string "ngInclude".
In my eyes, that's not enough since I use a custom directive for the message (which of course does not have "ngInclude" in it), but loads a template anyway. Like:
  message: '<my-directive-that-includes-a-template param="' + param + '"></my-directive-that-includes-a-template>',

I'd love to be able to set "marker.watchForContentLoad = true" and have the angular leaflet directive also watch for the "$includeContentLoaded" event as well. Only looking for "ngInclude" in the message string looks promising, but is not enough.

#800

Thanks for fixing it! Just a small question: how long does it take to bower recognize the new version 0.8.4? Bower install still has 0.8.3. Hope you can give me a small hint. Thx :)

Seems like the 0.8.4 tag is missing at the release commit. Has nothing to do with this issue, so will open another one. Thanks again :+1:

you can specify master until a release is made.

Its resolved.


Frontend: include the SILModule header

The smart pointer implementation in the C++ standard library may require a
complete definition for the type being deleted.  This is the case for SILModule.
Replace the forward declaration with a complete interface declaration from the
SILModule.h header.  This is needed to repair the build on Windows with MSVC.

Replace this paragraph with a description of your changes and rationale. Provide links to external references/discussions if appropriate.

Resolves SR-NNNN.

@swift-ci please test

CC: @jrose-apple

Hm. Frontend.h is included a lot, and CompilerInstance's destructor is specifically out-of-line so that we don't have to do this. What's the actual requirement here?

If getSILModule / takeSILModule / hasSILModule are the problem, can we move them out of line instead? They're not hot.

The actual requirement is the smart pointer on SILModule requires a complete definition (at least for Microsoft's C++ runtime).

But what's requiring that? Is it purely the member that's defined with unique_ptr type, or is it the use of that member in inline functions?

Oh, its the template instantiation of the std::unique_ptr<SILModule> that requires the complete definition since the runtime is free to (and actually does) a sizeof application to the type when constructing the default deleter.  The runtime is ensuring that the default deleter sees the complete type definition.  I suppose that we could extern template the default deleter ...

I suppose citing the standard won't magically fix MS's C++ library. :-( I don't think we can extern template the deleter because std::unique_ptr needs to know its size.

Hm, you sure about all this? https://godbolt.org/z/eCJvGz

Looks like it's takeSILModule's fault. Can you try moving that out-of-line instead? https://godbolt.org/z/KQNkIP

Sure, will do!

out-of-line in the header seems to work, which allows users to still inline, so going to go with that.

@swift-ci please test and merge

…that really shouldn't work. Also, don't forget inline.

@swift-ci please test

Build failed
Swift Test OS X Platform
Git Sha - 13c31b90bdc3be8873aa2ccc313b12d83d0e1b12

Build failed
Swift Test Linux Platform
Git Sha - 13c31b90bdc3be8873aa2ccc313b12d83d0e1b12


docs($compile): update preAssignBindingsEnabled description

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Docs update
What is the current behavior? (You can also link to an open issue here)
The changelog and migration guide does not mention the fact that this only applies to controllers which are part of a directive/component.
What is the new behavior (if this is a feature change)?
The changelog and migration guide does mention it.
Does this PR introduce a breaking change?
No
Please check if the PR fulfills these requirements

[x] The commit message follows our guidelines: https://github.com/angular/angular.js/blob/master/CONTRIBUTING.md#commit-message-format
[ ] Tests for the changes have been added (for bug fixes / features)
[] Docs have been added / updated (for bug fixes / features)

Other information:
https://github.com/angular/angular.js/issues/15740

The migration guide doesn't mention that pre-assignment is about the bindings being available inside the component/directive's controller constructor. Would it make sense to explicitly mention it aswell ?

I am fine with the current content, but if you want to add that to the migration guide, I will wait 😛

Updated 🙈


The Getting Started example has a hard-coded region - should be a variable?

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

What is the outcome that you are trying to reach?
When running the Getting Started example, it's not obvious how to change the region that it uses. In a corporate environment this can be locked down by policy, and the error message isn't clear.
Describe the solution you would like
Break out the hard-coded region into a variable. Can default to the current region. Update Getting Started doc to include the option.
Describe alternatives you have considered
No other alternatives to speak of.
Additional context
None.

see comment https://github.com/aws-ia/terraform-aws-eks-blueprints/pull/954#issuecomment-1272330068


Ecto "Parametrized" breaking change

The example in the README fails with latest ecto with the following error:
** (TryClauseError) no try clause matching: {:parameterized, {PolymorphicEmbed, %{default: nil, on_replace: :update, types_metadata: [%{module: MyApp.Channel.SMS, type: :sms, identify_by_fields: []}, %{module: MyApp.Channel.Email, type: :email, identify_by_fields: []}], type_field: "__type__", on_type_not_found: :raise, type_field_atom: :__type__}}}
    (polymorphic_embed 3.0.7) lib/polymorphic_embed.ex:443: PolymorphicEmbed.get_field_options/2
    (polymorphic_embed 3.0.7) lib/polymorphic_embed.ex:117: PolymorphicEmbed.cast_polymorphic_embed/3
    #cell:brjcaekzmw6iuns3:25: MyApp.Reminder.changeset/2
    #cell:brjcaekzmw6iuns3:67: (file)

gist:
https://gist.github.com/frozencap/76e0dc3eb3d4d1e39182461680b56d1f
EDIT: looks like the fix here just hasn't been released yet https://github.com/mathieuprog/polymorphic_embed/commit/a92bea891996073d28d4ec40d78ee1dd08ab82f8

EDIT: looks like the fix here just hasn't been released yet https://github.com/mathieuprog/polymorphic_embed/commit/a92bea891996073d28d4ec40d78ee1dd08ab82f8
just use in mix.exs > deps
      {:polymorphic_embed,
       github: "mathieuprog/polymorphic_embed", branch: "master", override: true},


Error: Build profile cloud not be found (Command Line)

Hi
I want to build my project from the command line, But I have 2 problems.

On my windows PC run build with command line and got these log:

command:
Unity.exe  -quit -batchmode -nographics -logFile e:/stdout.log -projectPath "E:\Working_Projects\xTests\unity\livekit\LiveKit\LiveKit" -executeMethod sttz.Trimmer.Editor.BuildManager.Build -profileName Build_Profile_1
Log:
...
Unloading 113 Unused Serialized files (Serialized files now loaded: 0)
Unloading 158 unused Assets / (0.7 MB). Loaded Objects now: 3993.
Memory consumption went from 87.7 MB to 87.0 MB.
Total: 4.958900 ms (FindLiveObjects: 0.362500 ms CreateObjectMapping: 0.307800 ms MarkObjects: 3.922300 ms  DeleteObjects: 0.365100 ms)

Building Build_Profile_1, selected from command line.
UnityEngine.StackTraceUtility:ExtractStackTrace ()
UnityEngine.DebugLogHandler:LogFormat (UnityEngine.LogType,UnityEngine.Object,string,object[])
UnityEngine.Logger:Log (UnityEngine.LogType,object)
UnityEngine.Debug:Log (object)
sttz.Trimmer.Editor.BuildManager:Build (sttz.Trimmer.Editor.IBuildsCompleteListener) (at Library/PackageCache/ch.sttz.trimmer@5799f29bc7/Editor/BuildManager.cs:352)
sttz.Trimmer.Editor.BuildManager:Build () (at Library/PackageCache/ch.sttz.trimmer@5799f29bc7/Editor/BuildManager.cs:310)

(Filename<EMAIL_ADDRESS>Line: 352)

Batchmode quit successfully invoked - shutting down!
...

On the Linux server pull the project from git and then:

command:
/home/Unity/2021.3.6f1/Editor/Unity  -quit -batchmode -nographics -projectPath /home/gitlab-runner/builds/2vyUksym/0/landrocker-workflow/livekit-test -executeMethod sttz.Trimmer.Editor.BuildManager.Build -profileName Build_Profile_1
Log:
...
Application.AssetDatabase Initial Refresh End
Scanning for USB devices : 2.021ms
Initializing Unity extensions:
UpdateMenuTitleForLanguage: 10
[MODES] ModeService[none].Initialize
[MODES] ModeService[none].LoadModes
[MODES] Loading mode Default (0) for mode-current-id-livekit-test
Unloading 5120 Unused Serialized files (Serialized files now loaded: 0)
Unloading 5236 unused Assets / (0.5 MB). Loaded Objects now: 3996.
Memory consumption went from 207.8 MB to 207.3 MB.
Total: 10.478980 ms (FindLiveObjects: 0.918570 ms CreateObjectMapping: 0.590435 ms MarkObjects: 5.236009 ms  DeleteObjects: 3.731601 ms)

Build profile named 'Build_Profile_1' cloud not be found.
UnityEngine.StackTraceUtility:ExtractStackTrace () (at /home/bokken/buildslave/unity/build/Runtime/Export/Scripting/StackTrace.cs:37)
UnityEngine.DebugLogHandler:LogFormat (UnityEngine.LogType,UnityEngine.Object,string,object[])
UnityEngine.Logger:Log (UnityEngine.LogType,object)
UnityEngine.Debug:LogError (object)
sttz.Trimmer.Editor.BuildManager:Build (sttz.Trimmer.Editor.IBuildsCompleteListener) (at Library/PackageCache/ch.sttz.trimmer@5799f29bc7/Editor/BuildManager.cs:347)
sttz.Trimmer.Editor.BuildManager:Build () (at Library/PackageCache/ch.sttz.trimmer@5799f29bc7/Editor/BuildManager.cs:310)

(Filename<EMAIL_ADDRESS>Line: 347)

Batchmode quit successfully invoked - shutting down!
Setting up 2 worker threads for Enlighten.
AcceleratorClientConnectionCallback - disconnected - :0
Cleanup mono
...

How can I fix these problems on those platforms?

Oh, sorry, I need to update the documentation.
Since 1.3.0 and f19ca220, Trimmer switches the active build target and waits for the domain reload before doing a build. You need to remove the "-quit" or Unity will exit before the domain reload and builds cannot start, Trimmer will quit Unity itself once the builds are complete.
Not sure why the build profile cannot be found on Linux. Trimmer uses the asset database to search for build profiles, maybe there's an issue if the project is imported for the first time?
I also just found an issue where Trimmer will not properly quit Unity in batchmode if the profile cannot be found, will hopefully fix that soon.

@sttz  Hi
Is there a way to temporarily solve the problem of not finding the build profile in Linux? For example, the address is hard-coded.
Because I really need this.

Could you try importing the project once first and then running the build in a separate invocation? Just to see if the issue is related to the project being imported for the first time (i.e. running Unity once without -executeMethod and then again with).
As a workaround, you could write your own method that loads the profile with a path, e.g.
using System;
using sttz.Trimmer.Editor;
using UnityEditor;
using UnityEngine;

public class CustomBuild
{
    const string PROFILE_PATH = "Assets/My_Build_Profile.asset";

    public static void Build()
    {
        var profile = AssetDatabase.LoadAssetAtPath<BuildProfile>(PROFILE_PATH);
        if (profile == null) {
            throw new Exception($"Build Profile not found at path: {PROFILE_PATH}");
        }

        var onComplete = ScriptableObject.CreateInstance<BuildManager.CommandLineBuildsCompleteListener>();
        BuildManager.Build(profile, onComplete);
    }
}

Ok, I will definitely do this and let you know the result.
Thank you for your follow up


Feat request - remove search limit by 5 shoes

Allow user to set the limits. E.g. by shoes count, maximum/minimum price

#9 will be implemented with the PR for this issue


Add unlim dims for h5netcdf

[x] Closes #1636
[ ] Tests added / passed
[x] Passes git diff upstream/master | flake8 --diff
[ ] Fully documented, including whats-new.rst for all changes and api.rst for new API

(these tests will fail until conda-forge get's an updated version of h5netcdf)

@shoyer - all tests are passing here. The resize issue required a small refactor of the set_dimension method in the scipy/netcdf4 backends.


[Website] Guidelines Style models

V2

Technically Docs model is not accurate / possible today, but we plan to add
Jeannie to follow up with new grid docs at a later date
Option to hide this page on launch

@oliviaflory

see how you feel about cutting all of the screen region stuff

i don't like the name "Product and docs model" — shixie originally had "Documentation model" but literally like ALL OF PRODUCT uses the left hand alignment, docs is just an outlier on IBM.com... I think we should call it the Product model for clarity

https://www.figma.com/file/3txRSZaAvAIYpB4xyEP5KD/Style_model_docs?type=design&node-id=10%3A363&mode=design&t=xEi6iC1cgDpTDYR1-1


Source maps do not work when using Chrome

Chrome's stack traces return relative urls where possible, breaking the assumption about fully qualified URLs that the error handler is making here
  var URL_REGEXP = new RegExp('http:\\/\\/[^\\/]*\\/' +
                              '(base|absolute)' + // prefix
                              '((?:[A-z]\\:)?[^\\?\\s\\:]*)' + // path
                              '(\\?\\w*)?' +      // sha
                              '(\\:(\\d+))?' +    // line
                              '(\\:(\\d+))?' +    // column
                              '', 'g');

Example trace from Chrome:
AssertionError: expected 'sign in' to equal 'sign in '
    at Assertion.assertEqual (base/test/karma.js?0adcb45a8697cfec3516857891cf7c4efe377f43:8311:13)
    at Assertion.ctx.(anonymous function) [as equal] (base/test/karma.js?0adcb45a8697cfec3516857891cf7c4efe377f43:16731:26)
    at Context.<anonymous> (base/test/karma.js?0adcb45a8697cfec3516857891cf7c4efe377f43:6356:53)

Changing the first component of the regex to the following seems to resolve the issue, but this might be too permissive:
'(?:http:\\/\\/[^\\/]*\\/)?' +

@kpdecker What version of Chrome you use?
And how look your karma.config.js?
Thanks!

Chrome 42.0.2311 (Mac OS X 10.10.3)
'use strict';

var webpackConfig = require('./webpack.config');

module.exports = function(config) {
  config.set({
    basePath: '',
    frameworks: ['mocha', 'phantomjs-shim'],
    files: [
      'test/karma.js'
    ],
    preprocessors: {
      'test/karma.js': ['webpack', 'sourcemap']
    },
    webpack: {
      cache: true,
      watch: false,
      devtool: 'cheap-inline-module-source-map',
      module: webpackConfig.module,
      resolve: webpackConfig.resolve,
      plugins: webpackConfig.plugins
    },
    webpackServer: {
      noInfo: true,
      stats: {
        colors: true,
        reasons: false
      }
    },

    exclude: [],
    port: 8080,
    logLevel: config.LOG_INFO,
    colors: true,
    autoWatch: true,
    browsers: ['Chrome'],
    reporters: ['mocha'],
    captureTimeout: 60000
  });
};


Set ApexDoc as commenting standard

Current CFPB Salesforce standards set the comment blocks like:
/*------------------------------------------------------------
Author:       Joe Somebody
Company:       Salesforce.com
Description:   A utility class for the contact trigger
Inputs:        "customers" - Contact objects that are being triggered
               "oldCustomers" - Contacts object values before trigger event
               "ta" - Trigger action that is occurring
Test Class:    CustomerManagementTest
History
<Date>      <Authors Name>     <Brief Description of Change>
------------------------------------------------------------*/

Instead, it seems preferable to follow https://github.com/SalesforceFoundation/ApexDoc, which follows familiar javadoc and jsdoc syntax (in use in other CFPB projects) and provides a tool to aggregate documentation.

The specific section and file that needs updating is: https://github.com/cfpb/salesforce-docs/blob/master/_pages/Source-code-and-configuration-management.md#commenting

Closing as this is in the docs now.

I think @author and @date can be made optional as those are included as part of the git commit

Yeah, if author is making the commit. It's less clear if Jenkins is making the commit.


Stress Testing on Kong  seems not good enough, how to improve it

we use 24 instances for kong cluster. when push on 800 concurrency，kong has a obvious fluctuates and not going up，does kong have any optimize to change it

Hi, can you give us more details about your setup and the issues you are experiencing?

What version of Kong, with what database?
What do you mean by "fluctuates" and "not going up"?
How are you deploying (is this a Kubernetes setup? Docker? Native?)
Are you running any plugins?


Wrong connection url

I try using your library with typescript, so I have the following angular factory:
export class ChatFactory implements IChatFactory {

    public hub: ngSignalr.Hub;

    $inject = ["$rootScope", "Hub"];

    static factory($rootScope: angular.IRootScopeService, Hub: ngSignalr.HubFactory) {
        return new ChatFactory($rootScope, Hub);
    }

    constructor($rootScope: angular.IRootScopeService, Hub: ngSignalr.HubFactory) {

        var options: ngSignalr.HubOptions = {
            // options
        };
        this.hub = new Hub("chat", options);
    }
}

This results in an error, because the url isn't correct:

But the default way to initialize a hub works:
var chat = $.connection.chat;
$.connection.hub.start({ transport: 'auto'}, function () {
    chat.server.join()
        .done(function (success) {
            if (success === false) {
            }
        });
});

If I have to pass in the url, I have to pass it from the view through ng-init to the controller, to the service, and then initialize the hub with the given rootUrl. This still doesn't work though, with the same error message. What am I doing wrong here?
EDIT
Postfixing the given rooturl with 'signalr/' does work, but I still don't know why the library would pick a different rooturl than the $.connection.hub

Hey @Devqon looking at signalR's src, on line 2746 it appears the default url is '/signalr', since this module uses $.hubConnection to create a connection, it sets the url for signalR to that default.
I would suggest just setting the rootUrl in the options like you discovered in your edit.

Yeah that works, but the real issue is that the 'normal' connection uses /OrchardLocal/signalr/negotia.. as default (which is correct, because /OrchardLocal is the baseurl), and through the angular-signalr-hub it uses /signalr/negotia.. (without the OrchardLocal part)


offsetfix and TGRSIRootIO diagnostics

Looks like all of the TGRSIRootIO::Get()->GetDiagnostics()->BadFragment(EventFrag->DetectorType) lines in GriffinDataToFragment in TDataParser.cxx are causing errors when you run offsetfix, but not when you sort the fragment file.
Suggestions? Is there an initialization line that needs to be added to offsetfix?

Yes, unless TGRSIRootIO::SetupDiagnostics has been called, GetDiagnostics() will return a null pointer and thus the line creates an error. Of course we could add a check whether the diagnostic has been created and otherwise create it inside the GetDiagnostics, or check if the function returned a null pointer within the GriffinDataToFragment before using it, but that probably wouldn't help the performance much.

Has this been solved? Another option might be to use the (newly implemented) TDataParser::SetRecordDiag(false) to disable writing the diagnostics?

I fixed this locally by modifying the GetDiagnostics function, but am having some difficulty getting my repo aligned with the "emplace" error still in place (Pull request #621).

How is the gcc update coming?

On Dec 1, 2015, at 1:46 PM, SmithJK<EMAIL_ADDRESS>wrote:
I fixed this locally by modifying the GetDiagnostics function, but am having some difficulty getting my repo aligned with the "emplace" error still in place (Pull request #621).
—
Reply to this email directly or view it on GitHub.

I've just updated the grifuser account to the latest version of the code, and had to change the emplace back to insert for that one too. I've included that change in the commit, that way everyone can compile it, and those with newer compilers can simply comment out the insert line and uncomment the emplace line. Once TRIUMF has the newer compiler we can switch to emplace.

I'll pull that and change the Get Diagnostics function after the meeting.
On Dec 1, 2015 10:56 AM, "Vinzenz Bildstein"<EMAIL_ADDRESS>wrote:

I've just updated the grifuser account to the latest version of the code,
and had to change the emplace back to insert for that one too. I've
included that change in the commit, that way everyone can compile it, and
those with newer compilers can simply comment out the insert line and
uncomment the emplace line. Once TRIUMF has the newer compiler we can
switch to emplace.
—
Reply to this email directly or view it on GitHub
https://github.com/GRIFFINCollaboration/GRSISort/issues/624#issuecomment-161062021
.

Resolved with PR #633.


fuzzing: inflate fuzz suite for catching UB

This suite is mainly intended to catch memory safety bugs and undefined behavior on the inflate code path. To that end it eschews the correctness checks present in other fuzz targets.
It also supports easily running Miri against the generated corpus, to catch any Rust-specific UB that wouldn't be caught by the other LLVM sanitizers.

Sorry, this needs more work on CI.

can you share how you run this locally (and how we might run it with e.g. ossfuzz). I'm assuming you allow generating larger input sizes, and potentially other settings?

I fleshed out the documentation a bit more to have the command I've been using.
The exercise of getting a corpus of gzip files is left to the reader. My strategy was to clumsily assemble a corpus by downloading a bunch of random gzips in GitHub public respositories.
Here's what I did roughly with the gh CLI.
# I think this starts failing earlier than 40 iterations, due to github search limits.
for i in $(seq 40); do gh api "search/code?page=${i}&per_page=100&q=extension%3A.gz+size%3A%3C%3D1048576" | jq -r '.items[].url' >>files.txt; sleep 30; done

# Prune out one gzip file per github organization, since people seem to upload duplicate files.
cat files.txt | sort -u -t/ -k5,5 >files2.txt

# Actually download the files, using your auth token so that you don't get rate limited.
for f in $(cat files2.txt); do curl -O -H"Authorization: Bearer $(gh auth token)" "$(curl -H"Authorization: Bearer $(gh auth token)" -H "Accept: application/vnd.github+json" "$f" | jq -r '.download_url')"; sleep 2; done

If you start with the initial corpus, -max_len isn't necessary, otherwise you'll probably want to do -max_len=some number of bytes because it defaults to 4096 bytes.

and how we might run it with e.g. ossfuzz

I haven't looked at integration with ossfuzz too much, but it looks fairly straightforward. Though I think for coverage purposes we might want to rewrite fuzz targets as C programs and submit it as a C project.
I haven't looked into it deeply since they say they'll only accept new projects if they "have a significant user base and/or be critical to the global IT infrastructure". Which I don't think qualifies zlib-rs at this precise moment, so I didn't see a reason to complicate running the fuzzer just yet.


portico: Extend proper background gradients to /plans.

This applies the same structures and now more-generalized CSS from /hello to the /plans page, ensuring the correct gradient display while also masking any color shifts from top and bottom overscrolling.
Screenshots and screen captures:

Light mode, before
Light mode, after

Dark mode, before
Dark mode, after

Merged, thanks @karlstolley!


Image Perspective Transformation

Sorry to bother you again, I saw that you have performed perspective transformation on the stitched image. Is the purpose of the perspective transformation to map with the bowl model? If so, why are the four coordinate points in the configuration file a very strange one? shape, thank you
The following code comes from SVStitcher.cpp
    WPTSfout["tl"] >> tl; WPTSfout["tr"] >> tr;
          WPTSfout["bl"] >> bl; WPTSfout["br"] >> br;
          WPTSfout["res_size"] >> resSize;
          const auto width_ = resSize.width;
          const auto height_ = resSize.height;

          std::vector<cv::Point_<float>> src {tl, tr, bl, br};
          std::vector<cv::Point_<float>> dst {cv::Point(0, 0), cv::Point(width_, 0),
                                              cv::Point(0, height_), cv::Point(width_, height_)};
          cv::Mat transformM = cv::getPerspectiveTransform(src, dst);

          cv::cuda::buildWarpPerspectiveMaps(transformM, false, resSize, warpXmap, warpYmap);

          row_range = cv::Range(tl.y, height_);
          col_range = cv::Range(0,  width_);
    }

Hi! The idea is follow - tripod-mounted cameras have uneven heights(different heights). That mean I don't have pure rotation(This strange because they anyway don't have only rotations even if they set with the same heights), therefore I get much more offset of frames when I place them in one coordinate system and stitch.
Figure 1 (below) is an explanation of what this code does. I'm trying to find(automatically) 4 angle points of a stitched image (code here) and then I make perspective transform(warping) on full size of panorama figure 2. This is just texture preparing for pass to OpenGL and render on bowl mesh.

Thanks for your answer, I got it


Assessment - Lyris list updates through db connection

We aim to send generic notifications to those users, who set this option on their notification settings page.
We need to be able to update Lyris email lists through database connection.
According to the attached Lyris documentation ODBC connection might be possible, however this needs further assessment and exploration.
Please  find out, if it really works and how it works.
Thanks!
lyris_maillist-10_manual (1).pdf

I've found the relevant database query and could run it to gather our Lyris users.
select count(*) from members_ where list_='ifrc_go_users';
8430


The default value of disablereuse of roxyPass is off. When the DNS on the back-end is updated, it cannot be detected immediately。

Expected Behavior
Provides apis to refresh DNS cache in real time.
Current Behavior
The DNS update on the back-end is not immediately perceived. If disablereuse is set to true, it is immediately perceived, but performance deteriorates for subsequent requests.
Possible Solution
Use disablereuse=on，but the performance is not expected.
Steps to Reproduce (for bugs)

Change the DNS to a new IP
Visti the apache httpd, but still proxyed to the olf IP

This sounds like an issue with your environment/system, not one with httpd.
Unfortunately, we do not have the bandwidth to provide in-depth integration/deployment/environment debugging or support here; these sorts of questions/requests would be more appropriately posted to a dedicated support forum, such as the Docker Community Slack, Server Fault, Unix & Linux, or Stack Overflow.


Brew hangs when downloading but system curl works

brew config output
HOMEBREW_VERSION: 3.4.11
ORIGIN: https://github.com/Homebrew/brew
HEAD: 30e3d8883cde265cbc16ff94b49a3ac14137590e
Last commit: 4 weeks ago
Core tap ORIGIN: https://github.com/Homebrew/homebrew-core
Core tap HEAD: fad558d9b8286c1b60903c7d5bbfd9c93385a45f
Core tap last commit: 32 minutes ago
Core tap branch: master
HOMEBREW_PREFIX: /home/linuxbrew/.linuxbrew
HOMEBREW_CASK_OPTS: []
HOMEBREW_CORE_GIT_REMOTE: https://github.com/Homebrew/homebrew-core
HOMEBREW_DISPLAY: <IP_ADDRESS>:0
HOMEBREW_MAKE_JOBS: 8
Homebrew Ruby: 2.6.8 => /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.8/bin/ruby
CPU: octa-core 64-bit skylake
Clang: 13.0.1
Git: 2.36.1 => /home/linuxbrew/.linuxbrew/bin/git
Curl: 7.68.0 => /bin/curl
Kernel: Linux <IP_ADDRESS>-microsoft-standard-WSL2 x86_64 GNU/Linux
OS: Ubuntu 20.04.4 LTS (focal)
Host glibc: 2.31
/usr/bin/gcc: 9.4.0
/usr/bin/ruby: N/A
glibc: N/A
gcc@5: N/A
xorg: N/A

brew doctor output
Please note that these warnings are just used to help the Homebrew maintainers
with debugging if you file an issue. If everything you use Homebrew for is
working fine: please don't worry or file an issue; just ignore this. Thanks!

Warning: You have unlinked kegs in your Cellar.
Leaving kegs unlinked can lead to build-trouble and cause formulae that depend on
those kegs to fail to run properly once built. Run `brew link` on these:
<EMAIL_ADDRESS>  openjdk

Verification

[X] I ran brew update and am still able to reproduce my issue.
[X] I have resolved all warnings from brew doctor and that did not fix my problem.

What were you trying to do (and why)?
Run brew upgrade
What happened (include all command output)?

* Connected to pkg-containers.githubusercontent.com (<IP_ADDRESS>) port 443 (#0)
* ALPN: offers h2
* ALPN: offers http/1.1
} [5 bytes data]
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
} [512 bytes data]
^CO=-#     #        #         #

However, command succeeds with double verbose -vv flag:

Output
/home/linuxbrew/.linuxbrew/bin/curl --disable --cookie /dev/null --globoff --show-error --user-agent Linuxbrew/3.4.11\ \(Linux\;\ x86_64\ Ubuntu\ 20.04.4\ LTS\)\ curl/7.68.0 --header Accept-Language:\ en --fail --progress-bar --retry 3 --location --remote-time --output /home/jmigual/.cache/Homebrew/downloads/c1e38eade543c17322427af4afe96c387b7b6bb6ddb60f46dfa08628b4f6f194--libxml2--2.9.14.x86_64_linux.bottle.tar.gz.incomplete https://pkg-containers.githubusercontent.com/ghcr1/blobs/sha256:29b5f1488808a5f626ab1a4ec38acf1ea8399c13e2c4fe15be9b178020bf517d\?se\=2022-06-04T07\%3A15\%3A00Z\&sig\=NGPG2pQprmUCMf\%2B5tu8qoZVBLl8mE1o2Vf\%2FfwJ3lJkM\%3D\&sp\=r\&spr\=https\&sr\=b\&sv\=2019-12-12 -vvv
*   Trying <IP_ADDRESS>:443...
* Connected to pkg-containers.githubusercontent.com (<IP_ADDRESS>) port 443 (#0)
* ALPN: offers h2
* ALPN: offers http/1.1
} [5 bytes data]
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
} [512 bytes data]
* TLSv1.3 (IN), TLS handshake, Server hello (2):
{ [122 bytes data]
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
{ [19 bytes data]
* TLSv1.3 (IN), TLS handshake, Certificate (11):
{ [3052 bytes data]
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
{ [264 bytes data]
* TLSv1.3 (IN), TLS handshake, Finished (20):
{ [52 bytes data]
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
} [1 bytes data]
* TLSv1.3 (OUT), TLS handshake, Finished (20):
} [52 bytes data]
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN: server accepted h2
* Server certificate:
*  subject: C=US; ST=California; L=San Francisco; O=GitHub, Inc.; CN=*.github.com
*  start date: Apr  7 00:00:00 2022 GMT
*  expire date: Apr  7 23:59:59 2023 GMT
*  subjectAltName: host "pkg-containers.githubusercontent.com" matched cert's "*.githubusercontent.com"
*  issuer: C=US; O=DigiCert Inc; CN=DigiCert TLS RSA SHA256 2020 CA1
*  SSL certificate verify ok.

I expected brew upgrade to download and upgrade my packages
Step-by-step reproduction instructions (by running brew commands)
- Running behind VPN (but it shouldn't be an issue as system curl can connect)
- `brew upgrade`

Please file this in Homebrew/discussions, this is not something that is reproducible by others.


Move RowKeySample to a separate file.

I'm going to need it in a file which is going to be included in table.h.

This change is

Crap, it's the second time I've done it. I think we need some sort of a check, so that I don't repeat that mistake in the future.
One easy way that came to my mind is to make the macro also contain the "namespace" keyword in it. That way, if you didn't define it, the code wouldn't compile. What do you think?


Upgrade default image version from 2.7.1 to 2.8.1

Includes changes from releases 2.8.0 and 2.8.1, which mostly contain bugfixes:

https://github.com/distribution/distribution/releases/tag/v2.8.0
https://github.com/distribution/distribution/releases/tag/v2.8.1

cc @ddelange I'm not sure the PR diff action is doing the correct thing here -- the diff doesn't look right, and the refs being compared seem to be the same. I'll look into it.


Add Prospect notebook

This notebook demonstrates obtaining SDSS spectra from the spectrum service and displaying it with Prospect.
Important note: I developed this on the user-facing, production notebook server, which does not yet have prospect installed, so I still have to load prospect from a checkout.  This will be a one-line change when prospect is finally installed.

@rnikutta, thank you for the comments.  I'm working on these now, please read on:

Suggest using "Astro Data Lab" in lieu of "Data Lab" where possible (e.g. NB title, Goals, Summary)
In the Imports cell, please add from getpass import getpass
In Authentication: "require a login (i.e. you will need a registered user account." --> closing parens is missing

Done

Forgive my ignorance here: "All spPlate files have a common wavelength solution, so a spPlate file can be represented by a Spectrum1D object." --> Is it "all spPlate files have a common wavelength solution", or "all spectra from the same plate have a common wavelength solution"? (or is each spectrum a seperate spPlate file, i.e. the two statements are equivalent?)

Sorry for the confusion.  The correct phrasing should be "all spectra in an individual spPlate file have a common wavelength solution."  I have updated the text.

"so a spPlate file can be represented by a Spectrum1D object. This object is an input to the visualization system, so we need to get outputs from the spectrum service that match the inputs to the visualization." --> I don't understand the last sentence. What do you mean by "the outputs from the service [must] match the inputs to the viz"?

That phrasing is left over from a time when this notebook was extracting spectra in a very different object representation.  It should say "the Spectrum1D object is a format accepted by the prospect visualization package".

"SDSS plates are circular, so we'll do a cone search around the nominal plate center. This gets us the spectrum identifiers we need to retrieve the spectra themselves." --> I thought spec.query() could fetch all IDs from a single plate given as an argument. But it doesn't seem so. Was this option removed? (or maybe I just mis-remember it..)

From the documentation I've seen spec.query() does require some form of coordinates as input.  @mjfitzpatrick , can you comment here?  There are examples of using qc.query(sql='...', ...), but not spec.query(sql='...', ...).

First code cell below "Redshift and other Metadata" --> Not questioning Prospect, but curious why it expects Z_ERR, and all field names in capitals?
Same issue: "we need to reformat it to match the expectations of Prospect" --> If these are documented somewhere, maybe add a link to these Prospect definitions?

The spectral metadata provided by SDSS has these fields capitalized.  Prospect expects the input data to match that.  This is also important in certain cases for distinguishing SDSS metadata from DESI metadata.  I can add more explanatory text, but there is not much else I can do here.

The NB currently does: ...

Well, I thought from all the discussion of specClient that finding the spectrum IDs is a critical step.  So by having that separate, that step is highlighted.  This also clearly separates the very important step of finding the IDs from the step of finding the metadata.  I could be convinced otherwise, but I have a slight preference for that separation of functionality.

This very long cell has no intro or post-execution info; it's quite opaque to understand what's being done:
The code cell under "Launch the Visualization" has many unexplained arguments. Not all are obvious; some (simple) explanatory text could help.

I will add more explanation for these.

After the Bokeh widget is loaded, it'd be good to add a few pointers about what one can now do....

OK, but would you prefer that text above or below the Bokeh cell?  On many displays, especially laptop-size, the Bokeh widget will take up the entire display, so do you prefer scrolling up or scrolling down for that?

The second code cell under "SDSS Spectra and Redshifts from Files" fails for me (this is on dltest):

This works for me on gp12/production.  I notice that requests is involved.  Wasn't there an issue with that on dltest?

On Thu, Feb 11, 2021 at 9:11 AM Benjamin Alan Weaver <
<EMAIL_ADDRESS>wrote:

"SDSS plates are circular, so we'll do a cone search around the
nominal plate center. This gets us the spectrum identifiers we need to
retrieve the spectra themselves." --> I thought spec.query() could
fetch all IDs from a single plate given as an argument. But it doesn't seem
so. Was this option removed? (or maybe I just mis-remember it..)

From the documentation I've seen spec.query() does require some form of
coordinates as input. @mjfitzpatrick https://github.com/mjfitzpatrick ,
can you comment here? There are examples of using qc.query(sql='...', ...),
but not spec.query(sql='...', ...).

You're confusing query() and getSpec():  In getSpec() you can pass in a
template identifier like "[(1963,54331)]" as a plate/mjd tuple and it will
expand the fibers automatically.  For query(), you would need to use the
constraint query with no positional arguments, e.g.
"query(constraint='plateid = 1963 and mjd = 54331')".
Note also there is a difference between queryClient.query() and
spec.query() as relates to specobjid:  The latter will automatically cast
specobjid to a uint64 whereas the qc.query() returns a possibly signed
integer as stored in the DB.
-Mike

Thanks @weaverba137

The NB currently does: ...

Well, I thought from all the discussion of specClient that finding the spectrum IDs is a critical step. So by having that separate, that step is highlighted. This also clearly separates the very important step of finding the IDs from the step of finding the metadata. I could be convinced otherwise, but I have a slight preference for that separation of functionality.

Understood, makes sense.

After the Bokeh widget is loaded, it'd be good to add a few pointers about what one can now do....

OK, but would you prefer that text above or below the Bokeh cell? On many displays, especially laptop-size, the Bokeh widget will take up the entire display, so do you prefer scrolling up or scrolling down for that?

Maybe just a sentence above (something with "We will initialize the spectral viewer. It allows browse through spectra, has zoom and pan capabilities, and other functions."
And under the widget, one could explain a bit more.
All other points you and Mike have clarified, thank you.

Notebook is updated, please review.

Prospect is a really cool tool!
Here my 2nd round:

Update version string in first cell before PR is merged
Clean up (remove)

# What the heck? Can't use a semicolon any longer?
# q = "SELECT ra, dec FROM sdss_dr16.platex WHERE plate = %d;" % plate

"Here we find spectra corresponding to SDSS plate 2955, but using the spectrum service instead of reading the spectra from a file."
--> But the query cell just below finds RA and Dec of a plate, not spectra.
Cell with:
sdss_ids = spec.query(r[0], r[1], 1.5, fmt='array', out='', constraint='plate=2955 ORDER BY specobjid LIMIT 50')
--> Why hard-code 2995 here? It has been defined in the previous section as the 'plate' variable.
Cell with:
sdss = spec.getSpec(sdss_ids, fmt='Spectrum1D', align=True)
--> Say one sentence what 'align=True' does?
"In the cells below, we wil extract ..." --> will
"this changes the numerical scale factor on the flux unit not the flux unit itself"
--> add comma: "... on the flux unit, not the flux unit itself"
"but will change in future vresions of prospect"
--> versions, Prospect
"Spectrum slider (< / >): Use these buttons or the slider page through the loaded spectra."
--> "to page through"
Cell with:
 os.environ['SPECTRO_REDUX'] = ...
--> Why the choice to set an env variable, rather than a simple NB variable? (it's only used in this very cell)
Could not review the final cells, from cell

%%time
sdss_file = read_spPlate(sc.get(sdss_spectra, mode='fileobj'), limit=50)
sdss_file

because it throws an error (please see Slack #notebook channel).

Updated after second round of comments.  Note: the HTML file is out of sync with the notebook.  Remind me to update that before merging.

Update version string in first cell before PR is merged

Done

Clean up (remove)

# What the heck? Can't use a semicolon any longer?
# q = "SELECT ra, dec FROM sdss_dr16.platex WHERE plate = %d;" % plate

I still can't use a semicolon in a SQL query on production.  Why is that not fixed?  Note that this is queryClient.query() not specClient.query() in this cell.

"Here we find spectra corresponding to SDSS plate 2955, but using the spectrum service instead of reading the spectra from a file."

Rephrased.

Why hard-code 2995 here? It has been defined in the previous section as the 'plate' variable.

Agreed, fixed.

Say one sentence what 'align=True' does?

Done.

"In the cells below, we wil extract ..." --> will

Done.

add comma:

Done.

"but will change in future vresions of prospect"

Done.

to page through

Done.

Why the choice to set an env variable, rather than a simple NB variable? (it's only used in this very cell)

Hmmm, historical reasons; not needed by Prospect.  Changed to a simple variable.

Could not review the final cells, from cell

Still works for me on production, so must be an issue with dltest.

On Fri, Feb 19, 2021 at 12:11 PM Benjamin Alan Weaver <
<EMAIL_ADDRESS>wrote:

I still can't use a semicolon in a SQL query on production. Why is that
not fixed?

It is already fixed, Seems to be pending a PR merge and deployment....

@mjfitzpatrick, thanx, I thought that had already been done.

Just pinged second reviewer.

I did a full test run now, looks good. Only three things from my side to update before merging:

add back in semicolon in query (once that capability has been deployed at DL production)
Remove the related comment from the NB
Update the HTML render as well

Pinging @stephjuneau to please test as well, as 2nd reviewer.

This should be ready for final check and merge now.

Thank you! Will test & merge this afternoon (after a bunch of meetings)

Hi @weaverba137 I tested the NB on prod and it looks good and runs well. Would you mind doing just one more commit to this PR? The rendered HTML has no outputs. But the HTML is best for a quick preview of a NB, so it would be good to have the output in the rendered HTML as well. Thanks!

OK, how much do you want rendered?  I don't know now a bokeh plot will render to an HTML file.  In principle it is mostly JavaScript, but it's very complex.  And there are actually two places where bokeh is used, the specClient and the equivalent test using files.

I think it's fine if the Prospect widget  is not rendered. It's static HTML after all. Can you give it a try?

OK, done.

Merged. Many thanks!


Address validation address_local not implemented

Hello 👋
I am about to use this gem for email validation (thanks for all your work here! you really did a lot of good things here, especially saving me from manually doing the punycode conversion).
While going through the configuration docs in your README, I noticed that you advertise the following setting:

address_local: false, Allow localhost, no domain, or local subdomains.

However, after testing it, I found it to not function. After reading through the source code of this gem, I couldn't find any place where you implement this setting.
This is how I use it:
EmailAddress.new(
  email_string,
  host_validation: :syntax,
  host_encoding: :punycode,
  local_format: :standard,
  local_encoding: :unicode,
  address_local: false
)

Maybe I am using the gem wrong, but to me it looks like this feature is not implemented.
We could either:

remove it's description from the README
implement the feature

cheers,
tessi

Thanks for bringing this up! I would lean to removing it, at least until a it is better defined. It also is ambiguous with expanding Fully Qualified Domain Names and allowing them.


Fix sentry ammo crate req name

About the PR

Title
Why / Balance

wrong
Technical details

Media

Requirements

[ ] I have read and I am following the Pull Request Guidelines. I understand that not doing so may get my pr closed at maintainer’s discretion
[ ] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Breaking changes

Changelog

no cl

you are the CO's strongest rifleman, thank you

Woke up and missed this PR oops
Fixed in https://github.com/RMC-14/RMC-14/commit/47e427aedc750adaac57448967e6b72006b63bc3 but I merged it anyways


ViroSurface Fix

@khaledJabari-90 @oraneedwards Thanks for the contribution. Can you confirm that is ok now.

@khaledJabari-90 @oraneedwards Thanks for the contribution. Sorry for the delay. Can you confirm that is ok?


Safari Experimental Feature "Dialog Element" doesn't fire "close" event

There is an experimental feature "Dialog Element" in Safari 14.
Mac: Develop -> Experimental Features -> Dialog Element
iOS: Settings -> Safari -> Advanced -> Experimental Features -> Dialog Element
When enabled, the dialog-polyfill doesn't load. But Safari's experimental dialog element lacks support for the "close" event which caused our dialog to misbehave.
I have come up with the following workaround for this issue:
if (!('onclose' in dialog) && !window.dialogPolyfill) {
    var observer = new MutationObserver(function(mutationsList) {
        for (var i = 0; i < mutationsList.length; i++) {
            if (mutationsList[i].attributeName === 'open' && !dialog.open) {
                dialog.dispatchEvent(new CustomEvent('close', {
                    bubbles: false,
                    cancelable: false
                }));
            }
        }
    });
    observer.observe(dialog, {attributes: true});
}

(The !window.dialogPolyfill is only necessary because the dialog-polyfill doesn't create the "onclose" property. Maybe that should be fixed independently of this issue?)
I'm not sure whether this is something you consider to be "in-scope" for the dialog-polyfill. There are probably not many Safari users out there who have enabled the experimental feature "Dialog Element" (though we got one such report from a user). But no matter what you decide, I think it's useful to fill this report because until about an hour ago I didn't even know that the experimental dialog element feature exists at all and furthermore found zero mentions of it on the web.

Safari also fails to submit <form method="dialog">, nor does it provide a backdrop. For now, it's so incomplete as to be unusable. My suggestion is, don't go out of your way to support users who enable experimental code.

Safari also fails to submit <form method="dialog">, nor does it provide a backdrop. For now, it's so incomplete as to be unusable. My suggestion is, don't go out of your way to support users who enable experimental code.

I'm incredibly glad Safari is adding this feature, but I agree that while it's experimental it may not be worth supporting.

When enabled, the dialog-polyfill doesn't load.

That's for the best.
I'm eager to see what they come up with, and I would be open to making this polyfill monkeypatch missing functionality, but since it doesn't have ::backdrop (which is, you know, a hard thing to polyfill since it implies all the weird focus management) I think I'm going to wait to see what they finally release.

I'm incredibly glad Safari is adding this feature, but I agree that while it's experimental it may not be worth supporting.

When enabled, the dialog-polyfill doesn't load.

That's for the best.
I'm eager to see what they come up with, and I would be open to making this polyfill monkeypatch missing functionality, but since it doesn't have ::backdrop (which is, you know, a hard thing to polyfill since it implies all the weird focus management) I think I'm going to wait to see what they finally release.

Ok, thank you for your input! :slightly_smiling_face:

Ok, thank you for your input! :slightly_smiling_face:


docs: remove fntlnz

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind design

/kind documentation

/kind failing-test

/kind feature

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area build

/area cmd

/area pkg

/area docs

/area tests

What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

NONE

Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits.
:memo: Please follow instructions in the contributing guide to update your commits with the DCO
Full details of the Developer Certificate of Origin can be found at developercertificate.org.
The list of commits missing DCO signoff:

8d131b2 docs: remove fntlnz

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: fntlnz
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [fntlnz]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Please see 👉🏼  https://github.com/falcosecurity/driverkit/pull/179#issuecomment-1184191306

Hey @fntlnz, my understanding is that you're voluntarily stepping down all repositories, but similarly to other repositories as for https://github.com/falcosecurity/falco/issues/2122, this PR can't proceed with the DCO due to your commit not being signed-off. This has been blocked for ~10 days, so I'm gonna open another PR with the same changes.

Closed in favor of #188
/close

@FedeDP: Closed this PR.

In response to this:

Closed in favor of #188
/close

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.


move_from_several not set up for moving several units onto a location owned by moving player. no reason this should not be the case.

make sure to change documentation in Player.move_from_several when this is closed.


Colinearity and PlanarityConstraint derivatives incorrect for exactly zero input values

Description
The way the Colinearity and PlanarityConstraints compute derivatives causes incorrect / spurious nonzero derivative values to appear if inputs (e.g. points, axes) contain true zero values.
The problem is this line which appears in two places in DVConstraints
/(2.0*numpy.sqrt(tmpX[i]))
Steps to reproduce issue
Turn derivative checking back on in test_DVConstraints tests 9 and 13b. It is currently turned off in the baseline case because the derivatives will contain different values depending on whether pyspline is compiled using Intel or GCC (produces near-zero floats in different places which causes the derivatives to be different)
Proposed fix
Instead of checking whether tmpX is exactly zero, check if it is nearly zero to within some tol
Or deprecate these constraints if nobody is using them.

Tests 9 and 13b currently fail finite difference checks


Added Firebase to Android

Fixes #10
added Android app to the Firebase project friday-683ad
added firebase_core: ^0.5.3 to pubspec.yaml
initialized firebase app in main
updated minSdkVersion to 21 from 16

I have added "Friday IOS" and "Friday Android" apps to the Firebase Project.  Please have a look and let me know if anything else is needed.

I have added "Friday IOS" and "Friday Android" apps to the Firebase Project.  Please have a look and let me know if anything else is needed.

Reviewed !! @avinashkranjan You are good to go with this PR.
But GitGuardian might raise an issue with the Google Services Json and Plist file. Need to do the necessary for that.

Reviewed !! @avinashkranjan You are good to go with this PR.
But GitGuardian might raise an issue with the Google Services Json and Plist file. Need to do the necessary for that.

@all-contributors please add @HimeshNayak  for code

@all-contributors please add @HimeshNayak  for code


[Design] Syntax to represent module namespace object in dynamic import

Another half of dynamic import #14774 is to enable users to be able to describe the shape of the module namespace object return by dynamic import. This is needed because

TypeScript currently can only resolve module if the specifier is a string literal (recall syntax of dynamic import import(specifier)) and Promise<any> will be returned...Therefore we need a way for users to be able to specify the module shape in type argument of the Promise and escape noImplicitAny (Note if dynamic import is used as expression statement. we won't issue noImplicitAny)

When we emit declaration file, we need a syntax to indicate that this is a Promise of some module. Currently compiler will give an error as reference external module is not the same as the module of containing file (or lack of one)

🚲 🏠 There are two ares which need to be discuss:

Syntax to bring in the dynamic loaded module so compiler can load during compile time
Syntax to specifier the return value of dynamic load (e.g just as a cast, or type argument to dynamic import etc.)

Proposes for (1) - bring in the module (This assume that we will use casting syntax but it doesn't have)

use namespace import, (this will get elided anyway if just used as type)

import * as MyModule1 from "./MyModule1"
import * as MyModule12 from "./MyModule2"
var p = import(somecondition ? "./MyModule1" : "./MyModule2") as Promise<typeof MyModule1 | typeof MyModule2>;

introduce new keyword ,moduleof....when collecting module reference we will also collect from moduleof as well

var p = import(somecondition ? "./MyModule1" : "./MyModule2") as Promise<moduleof "./MyModule1" | moduleof "./MyModule2">;

Proposes for (2) - indicate the return type

Since dynamic import is parsed as call expression, we can reused the mechanism of specifying type argument

var p = import<Promise<moduleof "./MyModule1" | moduleof "./MyModule2">>(somecondition ? "./MyModule1" : "./MyModule2");

Contextual Type

var p: <Promise<moduleof "./MyModule1" | moduleof "./MyModule2">> = import(somecondition ? "./MyModule1" : "./MyModule2");

Just use casting

allow all of the above.

Design meeting update #14853
In addition to be able to simply refer to shape of module namespace object, it is also desirable to use as a QualifiedName (e.g var x: <some syntax to indicate that we refer to module object>.namespace.interface) and to have syntax that can easily allow users to be able to do so is crucial.
Candidates we are currently considered:
declare var m: module("./foo").namespace.Interface   // this one seems to be the most popular
declare var m: (moduleof "./module").namespace.Interface;
declare var m: (importof "./module").namespace.Interface;
declare var m: (module "./module").namespace.Interface;

I will want to discuss some performance/incremental parsing related to this area and see if we think it will be desirable to consider top-level type import like import type * as ns from "./a.js".

Why not just like?
var p = import<typeof MyModule1 | typeof MyModule2>(somecondition ? "./MyModule1" : "./MyModule2");

@cevek two things with that syntax: 1)  it won't be clear that the output is a Promise of typeof Module1 or typeof Module2 or typeof Module1 or typeof Module2  2) during design meeting we decided to go with using casting syntax and allow contextual type because as you can see the type arguments syntax get pretty ugly with import<Promise<moduleof MyModule1 | moduleof MyModule2>>

So looking at the proposed snippets above:
import * as MyModule1 from "./MyModule1";
import * as MyModule12 from "./MyModule2";
var p = import(somecondition ? "./MyModule1" : "./MyModule2") as Promise<typeof MyModule1 | typeof MyModule2>;

var p = import(somecondition ? "./MyModule1" : "./MyModule2") as Promise<moduleof MyModule1 | moduleof MyModule2>;

I don't see how typeof and moduleof differ... Moreover, in the second snippet, where does the MyModule1 identifier come from? Is it just imported (like by import * as MyModule1 from "./MyModule1";) or is there some entirely distinct mechanicism I'm not picking up on?
My hope is that this is some huge typo and that the moduleof './MyModule1' syntax that @mhegazy suggested in #14495 is what you meant.

@rozzzly  it is a typo for this one.... Copy and paste mistake here 😭 I have updated the original post.

Update

The top candidate for syntax is module(...)
nuance semantic : should the syntax bring in type of module as well as namespace?

// 0.ts
export interface foo {}
export class C {}
// 1.ts
var p: module("./0");

is module(...) bring both type of module and namespace so you can do p.foo as well as p.C ?

or is module(...) only bring namespace side and therefore to get type of module one will have to do var anotherP: typeof module("./0");

If we go with (2.) then for dynamic import, to express the shape of import module will be
var d = import(blah)  as Promise<typeof module("blah")>;  // very verbose

Another syntax that comes up for using with dynamic import is
var d = import<"blah">(blah);
var d = import(<"blah">blah);

In both casting syntax, type argument must be string literal.,
Conclusion

Possible use short hand to specify shape of dynamic import separately  like

var d = import<"blah">(blah);
var d = import(<"blah">blah);

May be being able to bring just type of module should be treat in other issues so we can discuss syntax and semantic in details. So we won't have to worry about how such syntax plays with dynamic import (e.g. it may be a long verbose syntax like var d = import(blah)  as Promise<typeof module("blah")>; )

This is a subset of this larger issue #13231

I definitely like the type operator for looking up modules, since it would probably be nice if import could just be a function(like) in the appropriate lib.d.ts typed like
declare function import<T extends string>(path: T): Promise<typeof module(T)>;

where module(T) behaves like the type indexing operator with respect to unions of string literal types, but looks up the symbol associated with the module that string type indicates, rather than indexing off a specific type (and behaved like it has an indexer to an implicit any to catch cases where a string literal could not be inferred). I would almost like to use square brackets for module like a map, except that the string literal needs to be treated as a path and resolved from the containing file (probably? configuration dependent?), and that transformation makes it more like a function than a straight map. The new syntax also simultaneously allows one to type require and any other module-loader-specific lookup in a similar way to import, which would be excellent.
Oh, and this is unrelated but oddly unsatisfying: The import spec as currently written allows something like this:
export default (x) => import(x);

But not this:
export default import;

since it's not really a function.
This seems.... bad. Unnecessarily confusing. If the engine can record where the call-site for the ImportCall is, I don't (as not a JS-engine-author) see why it couldn't just add ImportKeyword to the list of expressions and make its reference (a la a getter, but in the global scope) return an annotated importing function keyed to the file the reference was in. But that's not about the TS syntax for looking up modules.

Unfortunately we can not do the general type operator; given the way the compiler is architected today all file-system interactions happen at the very beginning when we are collecting files to compile; whereas resolving types happens at a later stage where new files are not expected to be added, nor are file-system operations expected. so it has to be module("literal") and not module(T).

wouldn't the typeof module("foo") syntax conflict with the potential syntax for arbitrary typeof expressions (
https://github.com/microsoft/typescript/issues/6606)?
e.g.
declare function foo(a: boolean): string;
type Q = typeof foo(true); // Q is string

What is the final syntax?
A module instance is required to avoid repeating the same import('module') and deal with await/Promise every time a module reference is needed. Even though the module loaded only once, it require the calling function to be async or wrap the bottom one with .then().
I came across where there is a conditional import to only add hardware specific module, load the module to get an initialization side effect and doing some cleanup before exit. Currently I keep a variable of required function within the module instead of the module itself.
In my opinion

The top candidate for syntax for describing shape of module is module(...)

module(...) is awesome.

nuance semantic : should the syntax bring in type of module as well as namespace?

I vote for the module(...) not to bring in type but just namespace to make it similar with import * as a from "a" because module(...) may refer to default property.

var p: typeof module("a");
p = import<typeof module("a")>(a);
type moduleA = typeof module("a");

I like implicit type parameter above (without the Promise) instead of casting because it is well documented in IntelliSense instead of casting from any. Any concern to have something like function import<T>(module: string): Promise<T>?

I prefer to avoid typeof Module because it require import * as Module from "Module", the static import may produce side effect.

This seems like something that this feature request of mine could solve quite elegantly...
TL;DR: it'd reify types as pseudo-properties (transparent to the runtime) and allow them to be passed around and defined like so. Support for this would fall out fairly naturally.

Discussed this in  #22445, and conclusion is to go with import(<StringLiteral>)

Sorry if I'm missing something, but what is wrong with this, which is already possible?
import * as _foo from './foo'

let foo: typeof _foo

Also want to point to this piece from the DT "common mistakes" readme why import() shouldn't get a type parameter that I strongly agree with:

getMeAT<T>(): T:
   If a type parameter does not appear in the types of any parameters, you don't really have a generic function, you just have a disguised type assertion.
   Prefer to use a real type assertion, e.g. getMeAT() as number.
   Example where a type parameter is acceptable: function id<T>(value: T): T;.
   Example where it is not acceptable: function parseJson<T>(json: string): T;.
   Exception: new Map<string, number>() is OK.

@felixfbecker The string isn't a type parameter. import(...) in JS is a call-like syntactic expression much like super(...). For similar reasons, you can't do list.map(import) or list.map(super).

@isiahmeadows I am aware - like import is call-like, this proposal definitely looks type-parameter-like, so the argument still applies:
var p = import<Promise<moduleof "./MyModule1" | moduleof "./MyModule2">>(somecondition ? "./MyModule1" : "./MyModule2");

@felixfbecker why would you not just cast there?

@weswigham that's my point

This seems to not work with export default class
foo.js
export default class Foo {
  constructor() {
    this.name = 'bar';
  }
}

Fails: Property 'name' does not exist on type 'typeof import("/test/foo")'.
/** @typedef {typeof import('./foo').Foo} Foo */

/**
 * @param {Foo} foo
 * @return {string}
 */
function getName(foo) {
  return foo.name;
}

If I change foo.js to use  export class Foo {, then /** @typedef {import('./foo').Foo} Foo */ works fine.


Spring Data Geode vs Spring Data Gemfire

Whats is the relationship between Spring Data Geode vs Spring Data Gemfire? Are they completely standalone with independent lifecyles?

The answer to this question can be found here.


Add subscript() and superscript() functions

Add superscript() and subscript() functions to convert regular numbers and letters into superscripts or subscripts.  Basically will be a character mapping.

These will be put in the common package, not here.


BUG: Input fields on addIngredient aren't cleared when Modal window is closed

I decided that this is alright!


Schema validation through sequencer

This PR is just about doing the validation and generating the resulting SCHEMA output lines.  I'll likely tackle the "and so what then" in another PR.

Current output is something like https://github.com/grafnu/udmi/actions/runs/5158002651/jobs/9291129797#step:10:12


Socks/Tor proxy not working via sttp/okhttp, but fine in okhttp by itself

https://gist.github.com/fancellu/eba17511fc1cba273355f939bc886e29
val sttpversion="2.0.0-RC2"
"com.softwaremill.sttp.client" %% "okhttp-backend" % "2.1.2"
"SOCKS server general failure"
Any idea why?
Thanks

No idea - do I read the gist output correctly that it works when directly suing okhttp's client, but not when through sttp?
That would be quite weird. I would try to compare the request created by hand, and the one coverted from sttp to okhttp. Maybe there's something different there. But that would require some work with the debugger :)

Yes. okhttp works fine, I then plug the same client instance into sttpbackend, and it errors
I'm happy to use okhttp raw, but thought you'd like to know it has "surprising behaviour" when plugged into sttp
This issue with http clients and SOCKS handling (plus proper DNS resolution) is quite common, which is why I was happy when I found okhttp handled it properly
JDK11 HttpClient doesn't work with SOCKS, and neither does AsyncHttpClient (and by extension play-ws)

Yeah, though the weird thing is that sttp should do more or less what you are doing in your "direct" code. But to debug what exactly happens, would require a local env to reproduce :)

You can either install Tor cli directly, or just the Tor browser, and point the code to 9150 instead of 9050.
When you start Tor browser it kicks off a SOCKS proxy for you
https://www.torproject.org/download/

Thanks, I'll try that when I get some time to debug this :)

@fancellu I'm don't know much about SOCKS but I managed to "fix" your gist by changing scheme to http from https.
When https is used with plain OkHttp client exception is same.

Gah, you're right, I must have put the https by mistake.
Consider this closed


Redis::CannotConnectError in cache:update

Error in Event Data Backend
Redis::CannotConnectError in cache:update
Error connecting to Redis on redis1.ec2.datacite.org:6379 (Redis::TimeoutError)
View on Bugsnag
Stacktrace
lib/tasks/cache.rake:5 - block (2 levels) in <top (required)>
lib/tasks/cron.rake:7 - block (2 levels) in <top (required)>

View full stacktrace

An error linked to this issue has been marked as fixed in Bugsnag
Redis::CannotConnectError in cron:hourly


0078 - Subsets

Description of the Problem
Given a set of distinct integers, nums, return all possible subsets (the power set).
Note: The solution set must not contain duplicate subsets.
Link To The LeetCode Problem
LeetCode

Linked a PR with this issue #296 which will close this issue, thank you.


Run command help text still mentions running with a specific function

Description:
$title.
$ ballerina run -h

Says

The function to run [:function]
could also be specified, and if no function is specified and a
function named 'main' would be considered the function to run if
such a function exists.

Runs the function ('main' or specified function) in the given
program or module.

Affected Versions:
$ ballerina -v
Ballerina 1.0.0-beta
Language specification 2019R3
Ballerina tool 1.0.0

Fixed with https://github.com/ballerina-platform/ballerina-lang/pull/18588


getting a below issue while running the playbook after creating callback_plugins with datadog_callback.py and datadog_callback.yml

error/warning:
Couldn't send metric "task.ignored" to Datadog
API key is not set. Please run 'initialize' method first.
Couldn't send metric "task.skipped" to Datadog
API key is not set. Please run 'initialize' method first.
Couldn't send metric "task.ok" to Datadog
API key is not set. Please run 'initialize' method first.
Couldn't send metric "task.failures" to Datadog
API key is not set. Please run 'initialize' method first.
Couldn't send metric "task.unreachable" to Datadog
API key is not set. Please run 'initialize' method first.
Couldn't send metric "task.rescued" to Datadog
API key is not set. Please run 'initialize' method first.
Couldn't send metric "task.changed" to Datadog
API key is not set. Please run 'initialize' method first.
Couldn't send metric "elapsed_time" to Datadog
API key is not set. Please run 'initialize' method first.
Couldn't send event "Ansible playbook "ping" completed in 1 second successfully" to Datadog
API key is not set. Please run 'initialize' method first.
We had the datadog_callback.yml with api key set and also I tried it doing with env variables. Both of them didn't work. Please let me know what I need to do here to eliminate this errors. Thanks.

Hi 👋 thanks for opening this issue. Could you provide some more information so I could debug?

Is the datadog_callback.yml file in the same directory as datadog_callback.py?
Was it a proper yaml containing api_key: <the_actual_key>?
Is ANSIBLE_DATADOG_CALLBACK_CONF_FILE environment variable set?
What environment variables did you try using? Was it DATADOG_API_KEY?

After some offline communication, we figured out this was partially an environment problem, but I also made couple changes which helped identifying the issues and fix them:

https://github.com/DataDog/ansible-datadog-callback/commit/9fcae368d51f61af88160c1ab8daa8a03efd2c98
https://github.com/DataDog/ansible-datadog-callback/commit/25721d10ece37c3e0aa7e7e01750fccbb2b81629
https://github.com/DataDog/ansible-datadog-callback/commit/4d4301d36b3cb0fcf829ffb6e79ce3218e665a2e

Closing this issue now.

Thanks.
On Tue, Oct 5, 2021 at 2:48 AM Slavek Kabrda @.***>
wrote:

After some offline communication, we figured out this was partially an
environment problem, but I also made couple changes which helped
identifying the issues and fix them:

9fcae36
https://github.com/DataDog/ansible-datadog-callback/commit/9fcae368d51f61af88160c1ab8daa8a03efd2c98
25721d1
https://github.com/DataDog/ansible-datadog-callback/commit/25721d10ece37c3e0aa7e7e01750fccbb2b81629
4d4301d
https://github.com/DataDog/ansible-datadog-callback/commit/4d4301d36b3cb0fcf829ffb6e79ce3218e665a2e

Closing this issue now.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/DataDog/ansible-datadog-callback/issues/63#issuecomment-934116513,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJTCPE5M5VU5UF24W2ANY43UFKNSXANCNFSM5D6DLE2A
.
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.


Add css modal

Add HTML/CSS-only modal. This uses the <input type="checkbox />` trick to toggle the Modal.
Modal with text content:

Modal with form/login:

Thanksm this is really cool.
Just one thing: we have a Storybook entry for a login form. Can you add this sign in form there and re-use that component in this story ? ( I guess this should be Sign up, otherwise Login and Sign in is redundant.)

Sure, let me get to that. Will push some changes when it's done.

Btw, is it the same trick that could be used for a mobile menu ?

@noteed You're right, I think it's similar—we can make a mobile menu with the same technique. Let's do that?

Sure!
Le jeu. 28 mai 2020 à 09:57, Andy Ngo<EMAIL_ADDRESS>a écrit :

@noteed https://github.com/noteed You're right, I think it's similar—we
can make a mobile menu with the same technique. Let's do that?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/hypered/design-system/pull/57#issuecomment-635180992,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAMILGLKSEQXOIO3C26WL3RTYKQJANCNFSM4MN4TWBQ
.


"videos_to_keep": "10" on HUB doesn't work (just deleted 30GB+, 1500 videos)

"video_recording_options": {
  "height": "768",
  "frameSeconds": "1",
  "idle_video_timeout": "120",
  "frames": "5",
  "title_frame_font_color": "129,182,64,128",
  "lower_third_background_color": "0,0,0,200",
  "width": "1024",
  "lower_third_font_color": "255,255,255,255",
  "video_output_dir": "video_output",
  "record_test_videos": "true",
  "videos_to_keep": "10"
},

@cktech529 Is this still an issue with the latest version (1.10.0)?

i am seeing this behavior on the hub with 1.10.1

Gotcha will take a look soon
Sent via Payphone

On Aug 8, 2015, at 6:43 PM, Jacob Rosenberg<EMAIL_ADDRESS>wrote:
i am seeing this behavior on the hub with 1.10.1
—
Reply to this email directly or view it on GitHub.


ERROR: gpuview does't show anything when GPU does not support processes monitoring

In the list of GPU information sent from gpustat, if processes is not supported, an exception will be raised and an error will occur. In that case, nothing will be displayed in the dashboard.

why tee: /etc/supervisor/conf.d/gpuview.conf: No such file or directory

Did you run gpuview as a service?

Yes, I deployed eight services and six of them were fine, but two of them had problems and ended up with 22 Gpus on the dashboard, but those two had errors and I had to give up run gpuview as a service.can only gpuview run to show the dashboard

Please indicate the environment in which you ran gpuview.
Also show us what errors you got.
This is already a closed issue.
If there are new errors, you should open a new issue.


HPE_INVALID_HEADER_TOKEN error while fetching an image

Steps to reproduce:
var request = require('request')
request('https://facestore.pt/images/11522/products/10_1_20151002092830_img_b.jpg')

I receive the following error:
{ [Error: Parse Error] bytesParsed: 152, code: 'HPE_INVALID_HEADER_TOKEN' }

Stack trace:
Error: Parse Error
   at Error (native)
   at TLSSocket.socketOnData (_http_client.js:305:20)
   at emitOne (events.js:77:13)
   at TLSSocket.emit (events.js:169:7)
   at readableAddChunk (_stream_readable.js:146:16)
   at TLSSocket.Readable.push (_stream_readable.js:110:10)
   at TLSWrap.onread (net.js:523:20)

curl -IS 'https://facestore.pt/images/11522/products/10_1_20151002092830_img_b.jpg'
returns
HTTP/1.1 200 OK
Server: nginx
Date: Mon, 09 Nov 2015 02:58:16 GMT
Content-Type: image/jpeg
Content-Length: 69633
Connection: close
X-Frame-Options="ALLOW-FORM: facebook.com"
Access-Control-Allow-Origin: *
Access-Control-Allow-Methods: POST, GET, OPTIONS, DELETE, PUT
Access-Control-Max-Age: 1000
Access-Control-Allow-Headers: x-requested-with, Content-Type, origin, authorization, accept, client-security-token
Last-Modified: Fri, 02 Oct 2015 08:28:30 GMT
ETag: "aa08cc-11001-5211af2ce60c3"
Accept-Ranges: bytes
Strict-Transport-Security: max-age=31536000; includeSubdomains

I'm guessing that the X-Frame-Options="ALLOW-FORM: facebook.com" is what is causing it in node's http parser.

@evanlucas, good point! Should we address this issue in the node's tracker?

I would probably open an issue at https://github.com/nodejs/http-parser/issues.

https://github.com/creationix/http-parser-js fixed the issue for me


Outlets for components

I'm thinking of a better concept for outlets. Our current ContentPanel implementation knows what to render as content by looking up a registered "content-container" component. Whatever is registered there will be displayed. However, this is a bit unusual in app building terms. It's fine if we use the component registry for node components but for the content panel it struggles me a bit.. also I want to be able to instantiate two ContentPanels side by side (e.g. one showing a different doc than another), which would not be possible using the DI approach.
So this would be better i think:
LensWriter.js render method.
    $$(ContentPanel).append(
      $$(EditableBodyContent, {doc: this.props.doc})
    )

And in ContentPanel.js
  $$(Scrollbar,...),
  $$('div').addClass('panel-content').append(
    $$('div').addClass('panel-content-inner').append(this.props.children);
  )

So this would be prett fine already. However it's a bit confusing since I would expect that what i .append() will be a direct children to ContentPanel. Maybe we just provide an explicit outlet API.
    $$(ContentPanel).outlet(
      $$(EditableBodyContent, {doc: this.props.doc})
    )

You could pass multiple components to outlet, however if the parent call outlet again, we would replace the outlet content, rather then adding to it.
In ContentPanel.js we would provide something like this.props.outlet, hence:
    $$('div').addClass('panel-content-inner').append(this.props.outlet);

Would this somehow affect rendering and incremental updating etc? I mean we would have the functionality to replace an outlet.. without wiping the surrounding elements. So we would not need to rerender everything, but only what is inside the outlet. Let me know your opinions please.. i'm not sure I'm aware of all implications this would have.

I think it's not needed. Turned out utilising this.props.children works for all the cases we need currently.