Writing specs for routes defined with authenticated

Greetings,
I'm trying to use the method "authenticated" when defining a route only for authenticated users and is working. I'm having something like this in my routes:
authenticated :users do
resources :client-leads, :controller => 'authenticated/coach_match_leads'
end
However, I'm trying to write test for these routes and is not working. The test is the following:
{:get => "/client-leads"}.should route_to("authenticated/coach_match_leads#index")
But I'm getting I'm exception:
NoMethodError Exception: undefined method `authenticate?' for nil:NilClass
Do you have any ideas why is this happening? Is important to notice that this is happening only for the routes defined with authenticated. All the other specs for the routes are working properly (even the ones for other devise routes).
Thanks in advanced for your help.

This is a rails limitation. the only way for you to test this is via integration tests.

@waterlink stubbing methods on NilClass is a bad idea—you can easily break something later and your tests might be green where an object or logic was missing/bad.

@seanknox Yes, you are right. That was a very bad workaround. Stubbing methods on NilClass can be compared to switching to dark side of force. Powerful but comes with a huge price.
I highly don't recommend using my workaround from 1 year ago.

This worked for me, @seanknox.
  let(:warden) do
    instance_double('Warden::Proxy').tap do |warden|
      allow(warden).to receive(:authenticate!).with(scope: :user)
        .and_return(authenticated?)
      allow(warden).to receive(:user).with(:user).and_return(user)
    end
  end
  let(:user) { instance_double(User) }
  let(:authenticated?) { true }

  def simulate_running_with_devise
    stub_const(
      'Rack::MockRequest::DEFAULT_ENV',
      Rack::MockRequest::DEFAULT_ENV.merge('warden' => warden),
    )
  end

I had to change ":authenticate!" in @ClayShentrup 's answer to ":authenticate?" to get it working, like this:
let(:warden) do
    instance_double('Warden::Proxy').tap do |warden|
        allow(warden).to receive(:authenticate?).with(scope: :user)
            .and_return(authenticated?)
        allow(warden).to receive(:user).with(:user).and_return(user)
    end
end
let(:user) { instance_double(User) }
let(:authenticated?) { true }

def simulate_running_with_devise
    stub_const(
        'Rack::MockRequest::DEFAULT_ENV',
        Rack::MockRequest::DEFAULT_ENV.merge('warden' => warden),
    )
end

this kinda helped me:
module DeviseRoutingHelpers
  # workaround for this issue https://github.com/plataformatec/devise/issues/1670
  def mock_warden_for_route_tests!
    warden = double
    allow_any_instance_of(ActionDispatch::Request).to receive(:env).
      and_wrap_original { |orig, *args|
      env = orig.call(*args)
      env['warden'] = warden
      env
    }
    allow(warden).to receive(:authenticate!).and_return(true)
  end
end

RSpec.configure do |config|
  config.include DeviseRoutingHelpers, type: :routing

  config.before(:each, type: :routing) do
    mock_warden_for_route_tests!
  end
end


modify docs with configure kerberos

Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


Option to generate separate types that are reused

Is your feature request related to a problem?
I'm currently using StrawberryShake to retrieve data from a GraphQL endpoint, than map it to another object model, serialize it to XML to provide it to another service.
The object model and the query response contain quite a few types that are reused on several levels in the object model.
But StrawBerryShake generated the type names in a hierarchical way. Like IMyQueryName_RootObject_ChildObject.
This makes IMyQueryName_RootObject_ChildObject and IMyQueryName_RootObject_OtherNode_ChildObject two different types, although they are the same.
This causes my mapping to require more duplicate methods that only differ in incoming type name.
The solution you'd like
I know this hierarchical way of generating type names is safer to prevent type clashes.
That's why I would like to see the option to generate types in a way that types with the same name are considered the same.
So they are reused in the generated client code.
So I have an easier time mapping.
Product
Strawberry Shake

Can you post your GraphQL query?

I made it a bit smaller and translated to english:
query Fetch($personId: UUID!) {     getPersonByPersonID(personID: $personId)     {         personID         name         startdate         enddate         contactPerson         {               id               organisation               name               contactInfo               {                     address                     {                         addressType                         streetName                         houseNumber                         postalCode                         city                         countryCode                         startdate                        enddate                     }                     telephone                     {                         telephoneNumber                         countryPrefix                         startdate                        enddate                     }                     email                     {                         emailaddress                         startdate                         enddate                     }                 }             }             contactInfo             {                 address                     {                         addressType                         streetName                         houseNumber                         postalCode                         city                         countryCode                         startdate                        enddate                     }                     telephone                     {                         telephoneNumber                         countryPrefix                         startdate                        enddate                     }                     email                     {                         emailaddress                         startdate                         enddate                     }                 }             }         }         comments     } }
As you can see the whole contactInfo element is part of person type and contactPerson type, and are really the same elements. But generated as 2 different classes.

It looks like if you use GraphQL fragments, the code generator will turn those into interfaces. Those can be reused and might help with your mappings. I just discovered this, so there may be gotchas, but you can check it out if you are still stuck on this (or anyone else finds this issue).
fragment FullAddress on address {
  addressType
  streetName
  houseNumber
  postalCode
  city
  countryCode
  startdate
  enddate
}

I think this will make a CLR interface called IFullAddress. Then you refer to that fragment in your query:
query Fetch($personId: UUID!) {
    getPersonByPersonID(personID: $personId)
    {
        personID
        name
        startdate
        enddate
        contactPerson
        {
              id
              organisation
              name
              contactInfo
              {
                    address
                    {
                      ...FullAddress
                    }
.
.
.

So now that contact info object will have address class in it that implements the interface IFullAddress. And anywhere else you use that address fragment will get the same interface.
You can also have a fragment inside another one and the generator will make them inherited interfaces:
fragment ShortAddress on address {
  addressType
  streetName
}

fragment FullAddress on address {
  ...ShortAddress
  houseNumber
  postalCode
  city
  countryCode
  startdate
  enddate


Mock Kafka Factory types

Hoping to add some support to make Kafka connectivity optional for our application.
Our app specifies a series of sinks for events/messages such as Kafka or our local disk. When running locally it's often helpful to forgo the Kafka sink to test other parts of the app that are less Kafka-centric.
Currently the Kafka Producers/Consumers connect to their respective configured cluster immediately on start up and the DW app will fail to boot if no connection is available. I wasn't sure how to go about adding this optional behavior but a Mock class seems like it could also be useful for testing purposes.
What do you think, is there another way I could achieve this functionality currently?
Thanks again for taking a look!

That's very true I should have caught that initially, thanks for taking a look.
I went ahead and used some handy Mock classes Kafka already provides for us which actually makes this class seemingly more relevant than I initially thought. Appreciate the code read and please let me know if I've missed anything else!

@mzamani1 this may not be the best place to ask but any chance of a new release this week?

@PeterGroesbeck yes, sorry for the delay. I was hoping another open PR could be merged in, but I’ll go ahead and cut a release today. Give me an hour or two.

@PeterGroesbeck Ok, released 1.3.14-1

🙏 very much appreciated!


[d3d9] Keep reference to D3D9 module around

Some games check if d3d9.dll is loaded in their WindowProc and use that to make decisions.
Some of these apps FreeLibrary after calling Direct3DCreate9 which is bad to start with... but ends up with them getting very confused and they constantly remake the device in the window proc we hooked causing a stack overflow.
I wonder if D3D11/DXGI should do the same here, needs testing.

Seems like this solution is a red herring.


How about a DLL?

Excellent, it works. I am about to replace my old approach (https://www.codeproject.com/Articles/5359576/WinUI3-in-Existing-Win32-Applications) with this one.
Question: Can I make a DLL instead? I 'm trying to but since (I assume) it calls GetModuleHandle(0) which means the handle of my EXE instead of the DLL is taken, it doesn't work.
Great work.

I think the easiest way is to create Windows Runtime components as .winmd and .dll. So what you need to do is defining the classes in MIDL, generate stubs and implement them , and then generate header files with cppwinrt tool. See https://learn.microsoft.com/en-us/windows/uwp/winrt-components/create-a-windows-runtime-component-in-cppwinrt

By the way, it is written in standard C++, so you may be able to create a DLL in normal way. Make sure that you call init_apartment and Application::start to instantiate Application class in context of calling the DLL. Please try it!

If you want to call the DLL from existing Win32 app, it is recommended to use xaml islands for WinUI 3 which is being developed now.


Vim plugin

My VIM doesn't recognize that a project is Standard.
Is the presence of standard in package.json's devDependencies enough to flag that the package is Standard?
Perhaps both ESLint and JSCS should be patched to recognize the presence of Standard and then automatically look for the RC files in the right place?
Then, when used from within the editor, it just happens automagically—well, at least with some editors, who rely on external tools like that.

JSCS will not be patching itself to recognize standard. The correct way to do this would be to make standard a jscs plugin and an eslint plugin, rather than something that uses both of those tools.

@mikesherov and @nzakas,
Thank you for commenting.
Perhaps JSCS and ESLint can be patched to recognize to look for something other than an rcfile in the current directory? Are you open for that?
I'm thinking perhaps a property in package.json, which provides paths to rcfiles:
{
  "name": "my-package",
  "rcfiles": ["node_modules/standard/rc"]
}

In Standard, I'm looking for the least amount of actions for setting it up.
Editing package.json (to prefix the test script with standard && ) is probably already part of the workflow of setting Standard up, so adding the rcfiles property/value is just another step in the same file.
Perhaps addition of rcfiles can be made automagical, using standard's npm postinstall script?

You can already run jscs with an file using the config option.

Ditto ESLint using the -c option.

I'm looking for a way that will not require anyway to alter the way that ESLint & JSCS are called.
For example, ESLint is called automatically from my VIM plugin.
The current existing way of providing rules is the presence of rcfiles.
But that is not flexible enough for my purpose because that requires Standard to put such files in place in the repo where it is used and that is not such a great possibility, as you can imagine.
The little addition of a property to package.json is an acceptable, pleasant, non–destructive alteration.
If only ESLint and JSCS will follow such a property, it will be one possible solution. Are you open to anything like this?

ESLint already allows you to have configuration in package.json: http://eslint.org/docs/configuring/

A better approach might be to create a vim plugin specifically for standard. It may be worth getting this added to syntastic.
It looks like someone opened an issue for it already: scrooloose/syntastic/issues/1314

The correct approach is to create a vim plugin for standard.
@Flet already wrote a Sublime Text plugin. It's quite easy to do, since the output is easily parseable. You can see the regex to use here.
Ideally, a dedicated vim user would step up and write this plugin! I use vim as my secondary editor (only when I'm ssh'd into a server, and usually without syntax highlighting).

I'll use VIM so I'll benefit. But what about all the other editors?
@nzakas it allows configuration in package.json but it doesn't allow a directive/rule that allows us to provide a path to an rcfile, right? An include rule would be perfect. Would you be open to an include rule?

If we do this at the lower, ESLint&JSCS level, we don't need any editors to recognize Standard.

@mightyiam Please take your feature request directly to the jscs or eslint issue trackers.
Let's use this issue to track progress on a vim plugin. If someone writes this, let me know and we can link it from the README.

@feross Syntastic maintainer here.  Writing a syntastic checker for standard would be mostly trivial, provided that you fix this. :) As it is now, running
:echo system('standard file.js')

from Vim yields nothing, since stdin as seen by standard is not a TTY.

@lcd047 Hey, fixed the issue in 2.6.1. Care to give it a try?

@feross Excellent!  It works now, and I added a syntastic checker for it in c1a2098.
Unrelated however, error highlighting in syntastic seem to imply column numbers for eslint, except the ones referring to semicolons, are off by one.

Thank you very much, @feross and @lcd047.


[BUG] - Exporting figures from the Overview tap

Describe the bug
wanted to report a known issue for exporting figures from the Overview tap. It gives me the Model metab A figure even I have selected to export the diff. figure. To resolve this issue, put a break point at the beginning of the osp_plotMeanSpec.m and then manually change the input argument which_spec to Model metab diff1.

Thanks for reporting @shui5.
I have implemented a bug fix that allows the correct export of all spectra from within the GUI (#666 ).


Can only play on the same platform as recorded on.

Version of react-native-audio-recorder-player
2.0.8
Platforms you faced the error (IOS or Android or both?)
Both
Expected behavior
Files are playable on both platforms.
Actual behavior
Audio file only playable on the platform it was recorded on.
Steps to reproduce the behavior
Standard path records .m4a on ios and .mp4 on Android, but they are only playable on that same platform (if uploaded to a server and downloaded to the other platform's app).
Is there any universal sound format that can work across platforms?

Well. As I said in medium blog I only supported default extension in each platform. To achieve what you are willing to, I'd prefer you to convert the audio extension in your backend server with some beautiful packages like ffmpeg.

change line 90 in node_modules/react-native-audio-recorder-player/android/src/main/java/com/dooboolab/RNAudioRecorderPlayerModule.java  to
mediaRecorder.setAudioEncoder(MediaRecorder.AudioEncoder.AAC);
and line 124 in node_modules/react-native-audio-recorder-player/ios/RNAudioRecorderPlayer.m to
[NSNumber numberWithInt: kAudioFormatMPEG4AAC],AVFormatIDKey,
and it will work on both platforms


Design Time Instantiation Finbuckle V9 MultiTenantIdentityDbContext

In Finbuckle V8 the MultiTenantIdentityDbContext had a constructor that accepted an ITenantInfo object. In V9 the constructors for MultiTenantIdentityDbContext only accept IMultiTenantContextAccessor<> objects, which broke my design time instantiation.
Do you have any examples of design time instantiation with MultiTenantIdentityDbContext for V9? If not I am sure I will get something working later today...

Hi, there is now a factory Create method on MultiTenatDbContext that should let you spin up an instance easily for an IDesignTimeDbContextFactory<T> implementation. Does that work for you?

Hi Andrew...
It sure did... Should have looked at the updated documentation...
public sealed class IdentityApiDbContextDesignFactory : IDesignTimeDbContextFactory<MultiTenantIdentityDbContext>
{
    public MultiTenantIdentityDbContext CreateDbContext(string[] args)
    {
        const string connectionString = "Server=.; THE REST OF THE CONNECTION STRING;";
        var optionsBuilder = new DbContextOptionsBuilder<IdentityApiDbContext>();
        optionsBuilder.UseSqlServer(connectionString);

        var dbContext = MultiTenantDbContext.Create<MultiTenantIdentityDbContext, AppTenantInfo>(new AppTenantInfo(), optionsBuilder.Options);

        return dbContext;
    }
}

I was then able to build a migration and apply it


⚠ Bofrost.lu has degraded performance

In 7256e89, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 922 ms

Resolved: Bofrost.lu performance has improved in 73042e7 after 6 minutes.


RGB image export from Plot2D with original resolution

On the one hand the ability of silx/Plot2D to directly export greyscale tiffs from the Plot2D window is great for further data processing and on the other the export of png and jpg snapshots from the current graph is handy for electronic logbooks etc.
It would be great to also have the possibility to export a false color image in the resolution of the original data without any axes or labels (just using the colormap as used in the plot window applied to the data as exported in the tiff/edf export). This would be great to have for images that one wants to use in publications and would give the option to later on add separate overlay layers to the exported image as the experimental resolution of the raster-data is usually known.

I guess you mean to export it from the GUI.
Probably the method to_rgba in http://matplotlib.org/api/cm_api.html can do the job.

This can be added to the supported outputs.
Yes, internally, it means giving access to matplotlib through the silx API up to the save dialog.

Yes, intentionally I meant an export from the GUI and I still think that would be the best.
However, I have played around with to_rgba() from matplotlib but I could not figure out how to use the silx colormaps dictionary that I can get via getDefaultColormap() from a Plot2D within matplotlib.cm as cmap (e.g. in combinatation with ScalarMappable.set_cmap() which I would need in order to use to_rgba() ).

silx plot colormap description is different from matplotlib.
Here is a sample code to convert silx colormap (all but the 'name') to a matplotlib ScalarMappable:
import numpy

from matplotlib.colors import LogNorm, Normalize
from matplotlib import cm

silx_colormap = {
    'name': 'gray',
    'normalization': 'linear',
    'autoscale': True,
    'vmin': 0.0,
    'vmax': 1.0}

# Conversion to matplotlib normalization
if silx_colormap['autoscale']:
    vmin, vmax = None, None
else:
    vmin, vmax = silx_colormap['vmin'], silx_colormap['vmax']

if silx_colormap['normalization'] == 'linear':
    norm = Normalize(vmin, vmax)
else:
    norm = LogNorm(vmin, vmax)

# Converting the name is not direct
# Some silx plot colormaps are defined internally:
# See https://github.com/silx-kit/silx/blob/master/silx/gui/plot/BackendMatplotlib.py#L765
# There is equivalent colormap in matplolib, see http://matplotlib.org/users/colormaps.html
cmap = cm.gray

scalar_mappable = cm.ScalarMappable(norm, cmap)

# 2D data to convert to RGBA
data = numpy.arange(100).reshape(10, 10)

rgba_image = scalar_mappable.to_rgba(data)

Addressed in PR #526, see remark in PR https://github.com/silx-kit/silx/pull/526#issuecomment-272869532


Dropbox links for pre-built indices not accessible

Hi
I am unable to access the links provided to download pre-built indices. I was wondering if it is possible to get access.

Hey @gnkitaa - can you please indicate which ones? From which page? We'll update.

Hearing no follow-up, closing.


how do you convert the wallets so they can be seen for the btc.BF file

im not to sure how to convert the addresses for that file I have tried hash 160 but I am just not 100% sure how to add more addresses

HI You need CBloom.py which converts a txt database to a bloomfilter database. You can find a copy here https://github.com/Mizogg/Tkinter-Power/blob/main/files/Cbloom.py or Join Telegram for more information. https://t.me/CryptoCrackersUK
Or if you want Bloomfilter database for all type, a group here creates them all https://t.me/Blockchain_BTC_ETH_DUMPS


Fixes for Barbican with Vault plugin

Currently gives the error below, as the default field is not being applied to the varriable.
TASK [Write barbican Approle ID to file if requested] *************************************************************************
Monday 30 October 2023  09:57:48 +0000 (0:00:00.075)       0:00:07.517 ********
fatal: [controller01 -> localhost]: FAILED! =>
  msg: |-
    The conditional check 'stackhpc_write_barbican_role_id_to_file | bool | default(false)' failed. The error was: error while evaluating conditional (stackhpc_write_barbican_role_id_to_file | bool | default(false)): 'stackhpc_write_barbican_role_id_to_file' is undefined

    The error appears to be in '/var/lib/home/stackhpc/mattc/src/kayobe-config/etc/kayobe/ansible/vault-deploy-barbican.yml': line 80, column 7, but may
    be elsewhere in the file depending on the exact syntax problem.

    The offending line appears to be:

        - name: Write barbican Approle ID to file if requested
          ^ here

Also included another fix for the SSL with Barbican Vault Plugin. Needed to specify the cert path

I've also proposed another fix. The conditional check for the Barbican AppRole secret ID being present in vault would not work. Firstly, because the "when" statement was matching on it being present, when it should have been when it is not present.
However, the module hashivault_approle_role_secret_list also does not return a useful output. It lists the vault-uuids for the secrets, rather than the actual approle id which we would want to match for.
I've instead changed to use a different module, which can check for the presence of the secret specifically.


feat: Stock Management System [Java, Java Swing]

Please assign this issue to me and add the relevant labels.
This is a full-fledged project.

Please assign this issue to me and add the relevant labels. This is a full-fledged project.

assigned @RoshanMhatre

Raised a PR to fix this issue. Please review here: #57

Raised a PR to fix this issue. Please review here: #57

@RoshanMhatre just sync fork before opening a new PR


Optional flattening of the output pdf

As of now the filled output pdf is flattened and this results in a new PDF with the form fields filled but not further editable. I suppose this has been a design choice.
Being not very knowledgable about PDFs, are there specific reason to flatten a filled PDF forms before saving it to disk?
I'd like to propose a PR where the flattening is optional so that the end user is still able to perform modifications if needed before printing and\or archiving.
It is my understanding that it would simply be needed to edit this section of the code like (on the spot brainstorming):
// Create the pdftk command line arguments.
args := []string{
    formPDFFile,
    "fill_form", fdfFile,
    "output", outputFile,
}

// Borrowing the setup used for the optional overwrite at line 106
if len(flatten) == 0 || !flatten[0]{
    args = append (args, "flatten")
}

Being not very knowledgable about PDFs, are there specific reason to flatten a filled PDF forms before saving it to disk?

Yes, this was a design choice.

It is my understanding that it would simply be needed to edit this section of the code like (on the spot brainstorming):

Did you test to run pdftk without the flatten argument? Did it result into the desired output? If so, my proposal is following:

Break syntax and replace overwrite with an optional Options struct containing the overwrite and flatten boolean flag.
add go module support
initial tag to v1

Did you test to run pdftk without the flatten argument? Did it result into the desired output?

I did some tests with the fillable PDFs I have at hand with no issue, if there are edge cases I'm not aware of them.

Alright. Willing to work on a pull request?

Alright. Willing to work on a pull request?

I'll see what I can manage. I found an issue thought, unrelated to the flattening and it isn't a bug with this package but rather either with pdftk or how fillpdf invokes it so I'm not opening a new ticket as of now until I can get further infos.
Accented letters (àèéòù maybe more) are not printed to the final document. Were you aware of this issue\are there workarounds?

I'll see what I can manage.

Cool!

Accented letters (àèéòù maybe more) are not printed to the final document. Were you aware of this issue\are there workarounds?

Values are written here. Try setting accented letters and examine the final FDF file. If they are present, then this is a pdftk problem. Could also be a problem with your OS and UTF8 handling... Which OS do you use?

The values are correctly written to the FDF file. So it's indeed a pdftk issue. I've found this relevant question on stack overflow and I'll see if there is anything doable to "sanitize" the strings or change the FDF header as suggested there.
Honestly I know nothing about the FDF file and its configuration so if you have any idea or suggestion it would be more than welcome.

Implemented with #8

Thanks. I adjusted the options handling. Never write to a global variable. This could lead to a race.

The values are correctly written to the FDF file. So it's indeed a pdftk issue. I've found this relevant question on stack overflow and I'll see if there is anything doable to "sanitize" the strings or change the FDF header as suggested there.

Thanks for the link. I added Latin-1 support. This seams to be supported by pdftk. Could you give it a try?

I adjusted the options handling. Never write to a global variable. This could lead to a race.

I understand the change but the why is unclear, could you elaborate or link me relevant info to learn more about the issue?

I'll keep you posted about the accents.

I understand the change but the why is unclear, could you elaborate or link me relevant info to learn more about the issue?

The Fill function might be called concurrently by multiple goroutines. Assigning to a global variable by multiple routines causes a race. For more info see: https://golang.org/doc/articles/race_detector

I'll keep you posted about the accents. Thanks for giving it a shot!

It works with German umlauts. Should also work for french symbols...


New Prowjobs to validate changes in ACK core libraries.

Currently ACK deals with following two problems:
a) Late side-effects of code-generation changes: If a bug was introduced in code-generator, we do not catch it until a service team regenerates their controller and the controller uses the buggy part of code-generator.
b) Keeping service controllers up to date: Currently It is very easy for service controllers to go out of date because on every release of code-generator/runtime We have to manually regenerate controller and raise PRs.
To solve the above problem, There should be
a) A PreSubmit prowjob to AUTOMATICALLY validate code-generator changes using multiple service controller generation. Unit testing and basic lint of helm/kustomize files would be a decent start for validation. But it can be further extended to e2e testing and validating helm/kustomize artifacts as well.
b) PostSubmit prowjobs to update, regenerate service-controller whenever a new runtime, code-generator release is made respectively. Raising PRs from this process should also be automated.

Sometimes we want to introduce changes to the code-generator that break the existing configuration (see changes to print columns). In these cases, the presubmit jobs would fail, but the changes are still valid. Is there a mechanism to introduce these changes safely?

Sometimes we want to introduce changes to the code-generator that break the existing configuration (see changes to print columns). In these cases, the presubmit jobs would fail, but the changes are still valid. Is there a mechanism to introduce these changes safely?

Excellent point. Hopefully such changes are very rare and we can treat them like exception cases/work around them. (Ignore auto-regeneration PRs/UnitTest failures for these exceptional scenarios.)
Initial implementation can be kept simpler and faster to rollout by ignoring this part during design.

/close


Add support for TargetDir to React.MSBuild

I added React.MSBuild and added
<UsingTask AssemblyFile="$(OutputPath)\React.MSBuild.dll" TaskName="TransformBabel" />
  <Target Name="TransformBabel">
  <TransformBabel SourceDir="$(MSBuildProjectDirectory)" />
</Target>

to the .csproj file and tried to restart the Visual Studio and reload the project. Building the project after all those steps doesn't seems to compile any jsx to js. Am I missing any step?

You need to actually call the TransformBabel target. Try running msbuild foo.csproj /t:TransformBabel and see if that works. If it does, you should be able to change the target to <Target Name="TransformBabel" BeforeTargets="Build"> which will automatically run it before the build target.

Thanks, it works.
FYI, I have to change to command to msbuild foo.csproj /t:TransformBabel /p:Platform=x64 /p:Configuration=Debug in order to try out the transform. Once I got that working, I added BeforeTargets="Build" in the foo.csproj to transform before build.
However, is there any way to specify the output of the transform? it seems like it used to have the option of TargetDir to target the output I assume.

Currently the output is always in the same directory as the input file, with a .generated.js suffix: https://github.com/reactjs/React.NET/blob/master/src/React.Core/Babel.cs#L318-L329. That's a good feature request though, maybe create a separate issue for it :)

In that case I think the document on MSBuild needs to be updated before the feature is completed, namely the TargetDir="" options is invalid.
Do you want me to create a separate issue about the output path and close out this one?

I'll keep this task open for adding TargetDir support. Sorry for the delay in replying!

Since it's been over a year, I'm closing issues for future tasks like this that aren't actively being worked on, but would be open to adding support for this!
#655


Provider initiated negotiations are not implementable

Bug Report
The contract negotiation state machine allows providers to initiate a negotiation by sending an offer message. However, this sequence is not well-defined and has several implementation issues.
Flow description
An offer flow is only defined in the binding specification. This needs to be pulled out to the abstract negotiation spec document.
Consumers cannot decide which offer notifications to receive
There is no way for the consumer to decide which offer notifications it is interested in. In the current approach, the provider would have to indiscriminately send all new offers, which is not desirable. There is also a major scalability concern as all notifications must be done unicast by the provider to consumers.
Proposal
These issues and the complexity supporting provider-initiated negotiations indicate that the initial requirement prompting this feature may not be modeled correctly. That requirement is to provide a way for providers to notify consumers about an offer. This could be handled in two ways:

Catalogs are designed to be crawled periodically. The consumer could perform a diff of the new and previous catalog to determine new offers
An event stream dataset could be created by the provider that the consumer negotiates a contract for and opens a transfer process. The event stream provides notifications of new offers.

Either of these approaches addresses the initial requirement, significantly simplifies the DSP design, and allows the consumer to decide which offers it would like to be notified about.
The proposal is to remove provider-initiated negotiations and provide a recommendation to use one of the two approaches in a separate best practices document.

to be further discussed


Orchard.Layouts/Widgets [Feature request]:

To have the ability to provide a custom display type for a widget being rendered. In my case, a widget contained within a Layout-->Projection.Element, contained within another Layout-->Projection.Element.
Sipke suggested:
"This could be done as a simple property we would add to the widget elements, which would be quite easy to do."
That would be great to achieve via the Layouts designer, but the real power would stem from being able to create Queries that use a Layout with 'Custom display type' to effect widgets [and other elements?] contained within the resultant recursive layouts. I believe if no displayType is supplied, and/or, is not recognized, orchard by convention defaults to 'Detail', so this shouldn’t affect existing scenarios, only enhance Drivers that are coded to recognise the Custom DisplayType.
The above relates to: http://orchardpros.net/tickets/10775

What is the relationship between Queries and Widgets here? I don't understand the scenario. Are you querying widgets?

Is this PR fixing your isue: https://github.com/OrchardCMS/Orchard/pull/7074

Yes, #7074 would immediately fix that issue - thanks @jtkech and @sebastienros


Update composer.json

fix guzzle/guzzle guzzle http is outdated

https://github.com/ratchetphp/Ratchet/search?q=abandoned&type=Issues&utf8=✓
This is resolved in the upcoming 0.4 release


zookeeper check and graphite metrics

@piavlo Have you had a chance to make the change to use the Check::CLI class as @jperville suggested.  If you need assistance feel free to drop a line here and we can see about helping you.
Thanks


Refresh object command is not refreshing the object

The "refresh object" command will either:

Diff between the current file and the object in the server
Open the object in a temp file

When I want to refresh the object, I would like the server version of the object that has been updated outside VSCode.
This "refresh object" should be split in 3 commands:

"Diff" with server version
"Open the current object" that would open the object in a temp file
"Refresh" that would actually update the content of the current file

Otherwise, you have to:

Execute the "Refresh the object" command
Should to not diff
Copy the content of the temp file
Paste to the current file

Yeah, I to me the "refresh object" is basically the same a "get object" with an option to display the diff.
So like you mentioned, your scenario would be covered by doing some extra copy/paste step.
I rarely use the scenario (if ever) so if I do need it, I don't mind doing that extra step.
If you use it a lot, it would probably make sense for you to include that extra option (maybe disabled by default but available with options) so yeah, feel free to create a PR.


Authentication component

Overview
Allows authentication of users so that they are able to send authenticated requests to the graph
Notes
Current implementation is done via popup, redirect for now causes loss of all data including the access token provided on the url after login is successful
Testing Instructions

Spin up the app
Send requests as Megan Bowen
Hit the sign in button and authenticate
Send requests using your logged in account

The sign in button still shows after signing in.


moved gas limit above the send button

/kind ui-change
Fixes #855

@puncsky  updated requested changes please have a look thanks


Fix compilation errors of "compress_weights" target

This PR fixes the error:
error: cannot pass object of non-trivial type 'DistortionStats' through variadic method; call will abort at runtime [-Wnon-pod-varargs]

Thank you, I faced similar error when I was compiling this on Mac. Should we rather have an overload of this function?

@jonpsy Currently, there should be no need to add an overload. This function only accepts a DistortionStats parameter, just like in the COMPRESS_STATS conditional block.

What's weird is, this feature already exists, see L401. Weirdly enough, #define COMPRESS_STATS has been manually set to 0 in e29cd56.
@austinvhuang can you comment on this?


Is there any way to support .flv format

Hi,
This component is really great, is there any way to add .flv format videos files.
I am getting video can't be played in this browser error.

This component is only intended to simply add custom controls to a HTML5 video. FLV videos are not supported in many/any browsers and I don't intend to do anything with flash I'm afraid. You might want to look at video.js (which uses flash) or look at converting your video to a more browser friendly format.


Synthesis failed for Google.Cloud.SecurityCenter.Settings.V1Beta1

Hello! Autosynth couldn't regenerate Google.Cloud.SecurityCenter.Settings.V1Beta1. :broken_heart:
Here's the output from running synth.py:
Cloning into 'working_repo'...
Switched to a new branch 'autosynth-Google.Cloud.SecurityCenter.Settings.V1Beta1'
Cloning into '/tmpfs/tmp/tmp4t4_im1k/googleapis'...
Note: checking out '88316b63a486002727e14032d104690541179fc9'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b <new-branch-name>

HEAD is now at 88316b63a Generated synth.py files with multiple commits enabled
Note: checking out '7be2811ad17013a5ea24cd75dfd9e399dd6e18fe'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b <new-branch-name>

HEAD is now at 7be2811a fix: Update gapic-generator version to pickup discogapic fixes
Switched to a new branch 'autosynth-Google.Cloud.SecurityCenter.Settings.V1Beta1-2'
Running synthtool
['/tmpfs/src/git/autosynth/env/bin/python3', '-m', 'synthtool', '--metadata', 'synth.metadata', 'synth.py', '--']
2020-03-30 07:27:36,352 synthtool > Executing /tmpfs/src/git/autosynth/working_repo/apis/Google.Cloud.SecurityCenter.Settings.V1Beta1/synth.py.
Contents of preconfig file:
{"preclonedRepos": {"https://github.com/googleapis/google-cloud-dotnet.git": "/tmpfs/src/git/autosynth/working_repo", "https://github.com/googleapis/googleapis.git": "/tmpfs/tmp/tmp4t4_im1k/googleapis"}}Extracted repo location: /tmpfs/tmp/tmp4t4_im1k/googleapis
generateapis.sh: line 40: declare: GOOGLEAPIS: readonly variable
2020-03-30 07:27:36,401 synthtool > Failed executing /bin/bash generateapis.sh --check_compatibility Google.Cloud.SecurityCenter.Settings.V1Beta1:

None
2020-03-30 07:27:36,402 synthtool > Wrote metadata to synth.metadata.
Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/git/autosynth/env/lib/python3.6/site-packages/synthtool/__main__.py", line 102, in <module>
    main()
  File "/tmpfs/src/git/autosynth/env/lib/python3.6/site-packages/click/core.py", line 829, in __call__
    return self.main(*args, **kwargs)
  File "/tmpfs/src/git/autosynth/env/lib/python3.6/site-packages/click/core.py", line 782, in main
    rv = self.invoke(ctx)
  File "/tmpfs/src/git/autosynth/env/lib/python3.6/site-packages/click/core.py", line 1066, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/tmpfs/src/git/autosynth/env/lib/python3.6/site-packages/click/core.py", line 610, in invoke
    return callback(*args, **kwargs)
  File "/tmpfs/src/git/autosynth/env/lib/python3.6/site-packages/synthtool/__main__.py", line 94, in main
    spec.loader.exec_module(synth_module)  # type: ignore
  File "<frozen importlib._bootstrap_external>", line 678, in exec_module
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "/tmpfs/src/git/autosynth/working_repo/apis/Google.Cloud.SecurityCenter.Settings.V1Beta1/synth.py", line 22, in <module>
    hide_output = False)
  File "/tmpfs/src/git/autosynth/env/lib/python3.6/site-packages/synthtool/shell.py", line 39, in run
    raise exc
  File "/tmpfs/src/git/autosynth/env/lib/python3.6/site-packages/synthtool/shell.py", line 33, in run
    encoding="utf-8",
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 438, in run
    output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '('/bin/bash', 'generateapis.sh', '--check_compatibility', 'Google.Cloud.SecurityCenter.Settings.V1Beta1')' returned non-zero exit status 1.
Synthesis failed
Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/git/autosynth/autosynth/synth.py", line 482, in <module>
    main()
  File "/tmpfs/src/git/autosynth/autosynth/synth.py", line 334, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/git/autosynth/autosynth/synth.py", line 429, in _inner_main
    branch,
  File "/tmpfs/src/git/autosynth/autosynth/synth.py", line 135, in synthesize_loop
    metadata_path, extra_args, deprecated_execution, environ, synthesize_py_path,
  File "/tmpfs/src/git/autosynth/autosynth/synth.py", line 278, in synthesize
    synth_proc.check_returncode()  # Raise an exception.
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 389, in check_returncode
    self.stderr)
subprocess.CalledProcessError: Command '['/tmpfs/src/git/autosynth/env/bin/python3', '-m', 'synthtool', '--metadata', 'synth.metadata', 'synth.py', '--']' returned non-zero exit status 1.

Google internal developers can see the full log here.

Autosynth passed, closing! :green_heart:


Change names to be consistent

Change folder names.
Change file names.
Change elementno to Elementno
Delete /test folder as it is not actually used for now.

Please do the check the code again. It fails during production build

I have added a new commit, I think it is solved.
Is there a way to test the production build before making a pull request?

@hazemtarekelaswad  Your PR is failing again please do check the code before raising a pr


Improve table sorting

Switch to DataTables, which is designed for sorting and searching tables.
It's not small, but it gets the job done well.

@hayfield would you be able to look at resolving conflicts (might be because I merged things in the wrong order, sorry) then I will review.

Conflicts resolved.


[CP] [Impeller] Limit blur kernel to 1000x1000 pixels

issue_link
https://github.com/flutter/flutter/issues/127151
Commit Hash
https://github.com/flutter/engine/commit/3267fa29491a2a6715d2b53e0b5f9b452572ad30
Target
stable
pr_link
https://github.com/flutter/engine/pull/42217
Impacted Users
Impeller users
Impact Description
There is no upper bound for the blur kernel size, which can trigger the blur filter to allocate arbitrarily large textures. This results in at best failure to render frames, and at worst a crash.
Workaround
Users can work around this by bounding blur sigmas to a reasonable size in the framework.
Risk
low
Test Coverage
yes
Validation Steps
Run the new playground/golden test in https://github.com/flutter/engine/pull/42154, or the reproduction app in https://github.com/flutter/flutter/issues/127151.

LGTM


"maturin init" should be "maturin new"

Bug Description
In:
https://pyo3.rs/v0.18.2/#using-rust-from-python
It says "Still inside this string_sum directory, now run maturin init. "
According to
https://github.com/PyO3/maturin#usage
This should be "maturin new" instead.
Steps to Reproduce
Check docs
Backtrace
No response
Your operating system and version
Windows 11
Your Python version (python --version)
3.11
Your Rust version (rustc --version)
rustc 1.68.2 (9eb3afe9e 2023-03-27)
Your PyO3 version
latest
How did you install python? Did you use a virtualenv?
python.org
Additional Info
No response

maturin init does exist and is the intended command for that particular sequence; it's like maturin new but doesn't create the directory (just like cargo).
https://github.com/PyO3/maturin/blob/684b6c93c2914459087ac1f3a075037ee1e6519a/src/main.rs#L123


Create a "roocs-utils" package

daops and dachar should use same common root dirs.
We should remove root_dir from the operation function parameters in daops. But it should be possible to override their values somewhere, e.g. in a python object or an environment variable.
daops needs clisops:: all
dachar needs clisops:: general xarray utils
daops needs dachar:: root dirs
roocs-utils - must be lightweight and have no dependencies except xarray

Components for roocs-utils:

root_dir - for each project:

in-package config file
or ROOCS_CONFIG environment variable is a path to a local config file to override content
used by dachar and daops

sub-package: xarray_utils, to include:

is_longitude, etc.
get_coords, get_longitude etc.
anything else generic and likely to be used by multiple packages

parameter classes: parameter module or package:

base class, with signature:

.__init__() constructor calls ._validate()
._validate()
.as_<format>() converter, e.g. as_tuple(), as_string(), as_datetime()

alternatively, have properties, such as: <parameter>.str or <parameter>.dt

.__unicode__, __repr__, __str__ - all point to a single representation string for the parameter
.raw - returns the raw input
might have individual parameter-specific properties, such as:

TimeParameter.start - only if these are useful when our packages are trying to access the value of a parameter.

classes for AreaParameter, CollectionParameter, TimeParameter
called by: rook, daops and maybe even clisops.
usage would be:

for each parameter received by a rook.subset, daops.subset, clisops.subset?:

if value is already an instance of a Parameter class, then use it
else: instantiate a suitable parameter class - which would automatically validate.

!NOTE! roocs-utils - must be lightweight and have (almost) no dependencies except xarray.


Remove dependency of Home page on members.

Replace filtering on Membership by filtering on permissions.
Use a method from History/notifications to get the most recently modified boards instead of directly querying from component.

Fixed in #121


PolySwarm Results Table Incomplete

Describe the bug
Results do not always appear in the PolySwarm Results table despite the counter increasing in the "PolySwarm Results" on the left-hand side tree.
To Reproduce

submit eicar.com.txt
submit ChromeSetup.exe
close Autopsy
re-open Autopsy
Submit desktop.ini

This is what I did at least, guessing it's nondeterministic.

Screenshot attached. Note the inconsistency between the left hand side tree and the results table.

Also worth noting: the module thinks desktop.ini was already submitted, refused duplicate submission.


Cannot find module '_isMockFunction'

Description
Starting with VS Code 1.74.1, I get the following error when running tests using Jest. It works with VS Code 1.73.1
 Cannot find module '_isMockFunction'
    Require stack:
    - /Users/Rebecca.Vest/dev/vs-code-prettier-eslint/.vscode-test/vscode-darwin-arm64-1.74.1/Visual Studio Code.app/Contents/Resources/app/out/bootstrap-amd.js
    - /Users/Rebecca.Vest/dev/vs-code-prettier-eslint/.vscode-test/vscode-darwin-arm64-1.74.1/Visual Studio Code.app/Contents/Resources/app/out/bootstrap-fork.js

Reproduction

Clone https://www.github.com/idahogurl/vs-code-prettier-eslint
Run yarn to install node modules
Run yarn test

This may be a VS Code issue.

@idahogurl downgrading to Jest 27.5.1 fixed this for me, I don't know specifically what version this got added in but a revert does fix it.

I put together a PR to work around this for jest: https://github.com/jestjs/jest/pull/14188
I also have a workaround you can do locally. In your start.ts (or whatever script you point to with --extensionTestsPath), add the following lines to the run function:
if (globalThis._VSCODE_NODE_MODULES) {
    globalThis._VSCODE_NODE_MODULES = new Proxy(saved__VSCODE_NODE_MODULES, {
        get(target, p, receiver) {
            if (p === "_isMockFunction") return undefined;
            return Reflect.get(target, p, receiver);
        }
    });
}

This wraps the _VSCODE_NODE_MODULES proxy with one that simply returns undefined for _isMockFunction.

Did this get fixed in jest or is this still an issue?

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


Update temperate-longtree-forest.json

I think this color would stick more in the temperate region
What do you think?

i like the deeper contrast


Integration: TestContainerPTY occasionally fails on windows due to expected \x00 in output

Description
TestContainerPTY occasionally fails on windows due to expected \x00 in output.
https://github.com/containerd/containerd/blob/fdd1be6734acd11c1dbda14b032a67643352c410/integration/client/container_test.go#L2699-L2702
https://github.com/containerd/containerd/actions/runs/4701717798/jobs/8338201800?pr=8393#step:16:49
https://github.com/containerd/containerd/actions/runs/4750205702/jobs/8438224967?pr=8418#step:16:50
Steps to reproduce the issue

Describe the results you received and expected
The state of TestContainerPTY can be stabilized.
What version of containerd are you using?
main@fdd1be6734acd11c1dbda14b032a67643352c410
Any other relevant information
No response
Show configuration if it is related to CRI plugin.
No response

@gabriel-samfira Hi,I don't have a windows environment to reproduce it, do you have time to help look at it. Thanks

Hi @Iceber
Yup. I'll have a look!

I have not forgotten about this. While reproducing this, it seems that the container exits normally, but there's nothing in the stdout buffer. Will debug further and see why that is.

While I am unsure of the cause yet, I've run the workflow with only the flaky test on repeat a dozen times or so to see how it behaves.
TL;DR:

more likely on 2022 than 2019, but affects both at less than 2% from my testing.
does not seem to be a race condition or conflict with other tests. (I ran TestContainerPTY by itself)
seems to occur per go test command (i.e. running one go test -count 1000 command will either see it failing instantly or working all 1k runs), so might be a test setup issue?
sandboxed 2019 seems immune but may be just "good luck" on it not flaking.

The runs on my fork, done over this containerd commit, can be broken down as follows:

single-command runs with go test -run TestContainerPTY -count 1000 (run numbers 60-65)

all tests happened to run fine (a couple were killed for exceeding the time limit on GH actions though)

re-executing go test -run TestContainerPTY every time (run numbers 66-75) yielded these results:

Host OS
Failed test#
average first fail

2019 non-sandboxed
449, ✅, 342, ✅, ✅, ✅, ✅, ✅, ✅, ✅
395

2019 sandboxed
all worked
-

2022 non-sandboxed
6, 39, 95, 277, 40, 48, 142, ✅, 3, 40
68

2022 sandboxed
57, 4, 255, 127, 61, 77, 58, 44, 4, ✅
76

At this stage I suspect it may be related to either how the tests are set up, or it really is a random I/O failure in HCS, but will be investigating further...


Refactor event list

What kind of change does this PR introduce?

Does this PR introduce a breaking change?

What needs to be documented once your changes are merged?

👷 Deploy Preview for linneaslustgard processing.

Name
Link

🔨 Latest commit
52a8970cababfe93034813df37049403675d9c32

🔍 Latest deploy log
https://app.netlify.com/sites/linneaslustgard/deploys/6284031dd716380008c65dfa


Please see extended comments

This is committing the changes I made locally: added node_modules to gitignore, set up entire MVC folder structure with related files, added .env file with db called art_db.
I did not add the config folder with connection.js OR server.js in the root folder because I saw Mohamed added those files already in his own feature.

The gitignore file that was merged from Mohamed had the .env and .DS_store so that was kept. Node_modules was listed lower in the file.


Bump Bundler SDK version

Bump Bundler SDK version

Codecov Report
Patch and project coverage have no change.

Comparison is base (2f6f8fe) 51.81% compared to head (6e1650d) 51.81%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@           Coverage Diff            @@
##           develop     #862   +/-   ##
========================================
  Coverage    51.81%   51.81%
========================================
  Files          199      199
  Lines         8006     8006
  Branches      1654     1654
========================================
  Hits          4148     4148
  Misses        3857     3857
  Partials         1        1

Flag
Coverage Δ

coverage
51.81% <ø> (ø)

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

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


lower accuracy on OMD(Obama-McCain Debate twitter sentiment dataset)

I run the classification task with BERT pretrianed model, but while it's much lower than other methods on OMD dataset, which has 2 labels. The final accuracy result is only 62% on binary classification task!

We need more informations on the parameters you use to run this training in order to understand what might be wrong.

We need more informations on the parameters you use to run this training in order to understand what might be wrong.

THANK YOU! Because of limited mermory, the batch_size is 8 and epoch is 6, and the content is short, so set the max_length is 50, other parameters are default.


LSTM's forward function not work with null hidden and cell state

Hi, I'm implementing an example of using LSTM, however, I found that if I pass null h0_c0 to 'LSTM.forward' there will raise an exception like:

Unhandled exception. System.Runtime.InteropServices.ExternalException (0x80004005): Expected hidden[0] size 1 128 512, got [0]

@Leo-LiHao -- can you paste the code of the model (not the whole training code) here?

@Leo-LiHao -- can you paste the code of the model (not the whole training code) here?

No need -- this was easily reproduced: just go with the defaults... :-)


using alloydb-auth-proxy as k8s sidecar is not terminating with exit code 0

Bug Description
This happens in lots of cases, but the easiest way to reproduce this is through a k8s job:
apiVersion: batch/v1
kind: Job
metadata:
  name: test-alloydb-auth-proxy
  namespace: default
spec:
  template:
    metadata:
      labels:
        app: test-alloydb-auth-proxy
    spec:
      containers:
      - name: test-alloydb-auth-proxy
        image: hello-world:latest
        imagePullPolicy: IfNotPresent
        ports:
        - containerPort: 80
      initContainers:
      - name: alloydb-auth-proxy
        image: gcr.io/alloydb-connectors/alloydb-auth-proxy:1.11.2-bullseye
        imagePullPolicy: IfNotPresent
        restartPolicy: Always
        args:
        - --structured-logs
        - --prometheus
        - --address=<IP_ADDRESS>
        - --max-sigterm-delay=30s
        - --http-port=9130
        - --health-check
        - --http-address=<IP_ADDRESS>
        # connection string
        - projects/<project>/locations/<location>/clusters/<cluster-id>/instances/<instance-id>
        resources:
          limits:
            memory: 64Mi
          requests:
            cpu: 50m
            memory: 64Mi
        securityContext:
          allowPrivilegeEscalation: false
          readOnlyRootFilesystem: true
          runAsNonRoot: true
        startupProbe:
          httpGet:
            path: /startup
            port: 9130
          periodSeconds: 1
          timeoutSeconds: 5
          failureThreshold: 20
        livenessProbe:
          httpGet:
            path: /liveness
            port: 9130
          initialDelaySeconds: 10
          periodSeconds: 60
          timeoutSeconds: 30
          failureThreshold: 5
        readinessProbe:
          httpGet:
            path: /readiness
            port: 9130
          initialDelaySeconds: 10
          periodSeconds: 10
          timeoutSeconds: 10
          successThreshold: 1
          failureThreshold: 6
      restartPolicy: Never
      serviceAccountName: testsa
      terminationGracePeriodSeconds: 30
  backoffLimit: 4

status of pod from job:
  containerStatuses:
  - containerID: containerd://05dd9afe90387d7ee9e2f4f1987fd62bdd5b69ed759cca57edaf899979e87d63
    image: docker.io/library/hello-world:latest
    imageID: docker.io/library/hello-world@sha256:305243c734571da2d100c8c8b3c3167a098cab6049c9a5b066b6021a60fcb966
    lastState: {}
    name: test-alloydb-auth-proxy
    ready: false
    restartCount: 0
    started: false
    state:
      terminated:
        containerID: containerd://05dd9afe90387d7ee9e2f4f1987fd62bdd5b69ed759cca57edaf899979e87d63
        exitCode: 0
        finishedAt: "2024-11-28T17:00:39Z"
        reason: Completed
        startedAt: "2024-11-28T17:00:39Z"
  initContainerStatuses:
  - containerID: containerd://9b3721ce694ae4328cdebbaf3624ac27ee1c7457c6756f76915b89f91228ec13
    image: gcr.io/alloydb-connectors/alloydb-auth-proxy:1.11.2-bullseye
    imageID: gcr.io/alloydb-connectors/alloydb-auth-proxy@sha256:8aa6a3dd67efc929923eeec5f5057898f1a4bf7767a05bd36639b4c3d7a321dc
    lastState: {}
    name: alloydb-auth-proxy
    ready: false
    restartCount: 0
    started: false
    state:
      terminated:
        containerID: containerd://9b3721ce694ae4328cdebbaf3624ac27ee1c7457c6756f76915b89f91228ec13
        exitCode: 143
        finishedAt: "2024-11-28T17:00:40Z"
        reason: Error
        startedAt: "2024-11-28T17:00:36Z"

This seems that sigterm received by container that it terminates is not handled correctly. This is not happening with cloudsql proxy.
Example code (or command)
// paste your code here

Stacktrace
logs from stern:

~ stern test-alloydb-auth-proxy
+ test-alloydb-auth-proxy-qn58r › alloydb-auth-proxy
test-alloydb-auth-proxy-qn58r alloydb-auth-proxy {"severity":"INFO","timestamp":"2024-11-28T17:00:36.761Z","message":"Authorizing with Application Default Credentials"}
test-alloydb-auth-proxy-qn58r alloydb-auth-proxy {"severity":"INFO","timestamp":"2024-11-28T17:00:37.377Z","message":"[xyz.us-central1.xyz.xyz-default] Listening on [::]:5432"}
test-alloydb-auth-proxy-qn58r alloydb-auth-proxy {"severity":"INFO","timestamp":"2024-11-28T17:00:37.378Z","message":"The proxy has started successfully and is ready for new connections!"}
test-alloydb-auth-proxy-qn58r alloydb-auth-proxy {"severity":"INFO","timestamp":"2024-11-28T17:00:37.378Z","message":"Starting health check server at <IP_ADDRESS>:9130"}
test-alloydb-auth-proxy-qn58r alloydb-auth-proxy {"severity":"INFO","timestamp":"2024-11-28T17:00:40.279Z","message":"SIGTERM signal received. Shutting down..."}
+ test-alloydb-auth-proxy-qn58r › test-alloydb-auth-proxy
test-alloydb-auth-proxy-qn58r test-alloydb-auth-proxy
test-alloydb-auth-proxy-qn58r test-alloydb-auth-proxy Hello from Docker!
test-alloydb-auth-proxy-qn58r test-alloydb-auth-proxy This message shows that your installation appears to be working correctly.
test-alloydb-auth-proxy-qn58r test-alloydb-auth-proxy
test-alloydb-auth-proxy-qn58r test-alloydb-auth-proxy To generate this message, Docker took the following steps:
test-alloydb-auth-proxy-qn58r test-alloydb-auth-proxy  1. The Docker client contacted the Docker daemon.
test-alloydb-auth-proxy-qn58r test-alloydb-auth-proxy  2. The Docker daemon pulled the "hello-world" image from the Docker Hub.
test-alloydb-auth-proxy-qn58r test-alloydb-auth-proxy     (amd64)
test-alloydb-auth-proxy-qn58r test-alloydb-auth-proxy  3. The Docker daemon created a new container from that image which runs the
test-alloydb-auth-proxy-qn58r test-alloydb-auth-proxy     executable that produces the output you are currently reading.
test-alloydb-auth-proxy-qn58r test-alloydb-auth-proxy  4. The Docker daemon streamed that output to the Docker client, which sent it
test-alloydb-auth-proxy-qn58r test-alloydb-auth-proxy     to your terminal.
test-alloydb-auth-proxy-qn58r test-alloydb-auth-proxy
test-alloydb-auth-proxy-qn58r test-alloydb-auth-proxy To try something more ambitious, you can run an Ubuntu container with:
test-alloydb-auth-proxy-qn58r test-alloydb-auth-proxy  $ docker run -it ubuntu bash
test-alloydb-auth-proxy-qn58r test-alloydb-auth-proxy
test-alloydb-auth-proxy-qn58r test-alloydb-auth-proxy Share images, automate workflows, and more with a free Docker ID:
test-alloydb-auth-proxy-qn58r test-alloydb-auth-proxy  https://hub.docker.com/
test-alloydb-auth-proxy-qn58r test-alloydb-auth-proxy
test-alloydb-auth-proxy-qn58r test-alloydb-auth-proxy For more examples and ideas, visit:
test-alloydb-auth-proxy-qn58r test-alloydb-auth-proxy  https://docs.docker.com/get-started/
test-alloydb-auth-proxy-qn58r test-alloydb-auth-proxy
- test-alloydb-auth-proxy-qn58r › test-alloydb-auth-proxy
- test-alloydb-auth-proxy-qn58r › alloydb-auth-proxy

### Steps to reproduce?

1. provided in the description of the bug
2. ?
3. ?
...

### Environment

1. OS type and version: debian & default docker image
2. AlloyDB Proxy version: 1.11.2 & 1.11.3 reproduced
3. Proxy invocation command (for example, `./alloydb-auth-proxy --port 6000 <INSTANCE_URI>`):

### Additional Details

_No response_

I've seen that there is a flag added in 1.11.3 --exit-zero-sigterm that fixes this. Maybe you can adjust docs/examples to reflect it.

Sorry for the late reply. Yes, you'll need to use --exit-zero-sigterm. We're working on surfacing the Proxy's help message in the README here: https://github.com/GoogleCloudPlatform/alloydb-auth-proxy/issues/709.


Backing up master filer and all volumes

Hello, Chris.
First of all thanks for this awesome tool. It's heart of our whole system.
As you know we have 1 master and 3 volumes servers running and we have planned to backup everything, on GDrive. I am uploading all volumes to Drive. starting from Master Volume.
Question: On Master Filer there many other folders too as filer and snapshot, etc, But I am only backing up the volume files (.dat) only. is this Okay? Someday when we will download these .dat files and start master volume with that, with filer true. then Everything will work fine? or you suggest something else?

.dat files are enough for volume servers. but preferably also .idx files.
master servers do not need anything.
filer server need the filer database file

Thanks for the answer Chris.
The folder where we have started weed server, there are
ida and idx files..
and
1302.dat  1608.dat  1913.dat  2241.dat  38.dat     695.dat  9.dat
1302.idx  1608.idx  1913.idx  2241.idx  38.idx     695.idx  9.idx
1303.dat  1609.dat  1914.dat  2242.dat  390.dat    696.dat  backup
1303.idx  1609.idx  1914.idx  2242.idx  390.idx    696.idx  conf
1304.dat  160.dat   1915.dat  2244.dat  391.dat    697.dat  config.json
1304.idx  160.idx   1915.idx  2244.idx  391.idx    697.idx  filer
1305.dat  1610.dat  1916.dat  2245.dat  392.dat    698.dat  log
1305.idx  1610.idx  1916.idx  2245.idx  392.idx    698.idx  snapshot

and filer folder
065665.ldb  114753.ldb   160692.ldb   210512.ldb  262976.ldb  LOCK
065666.ldb  114754.ldb   160693.ldb   210513.ldb  262977.ldb  LOG
065667.ldb  114755.ldb   160694.ldb   210542.ldb  263002.ldb  LOG.old
065668.ldb  1147707.ldb  160715.ldb   210543.ldb  263003.ldb  MANIFEST-157424

So I was asking there is backup, conf, config.json, filer and log, snapshot folder here..
and in filer folder there is lock , log, log.old, Manifest file. Now can you tell me what to backup?
I am backing up .dat files, (I will backup idx as well). but filer db file ? These all seems to be filer db files.

the whole filer folder should be replicated.


Show buffering progress on scrubbar

It would be great to show how much of the video has been already buffered. Such information should be shown on seekbar. You know, just like in YouTube :-)

You have a directive called vg-scrub-bar-buffer.
You can see it working on the homepage.


New Release =D

Hi ESanchez,
When are you planning on making a new release? (for spring boot 2 with the last PR`s merged)
I'm migration an application currently using vanilla java to Spring Boot and this starter fits perfectly (good job =D ).
Speaking about it, is there any todo list that you wanna share? I might help improve this starter.
Thank you!

I will try to release it today or tomorrow.
For the things to do I will gather a list and will share but the main areas to improve are:

Provide a mechanism to register event listeners for the MessgeCracker through annotations, provide default listener beans that can be extended- Improve health endpoints information - Improve documentation - Create more example apps - Create configurable mock acceptor- Create configurable mock initiator - Create starters for different message stores with the required dependencies ...
Thanks for your help MarceloRegards, Eduardo
Sent from Yahoo Mail on Android
On Wed, 24 Oct 2018 at 23:39, Marcelo<EMAIL_ADDRESS>wrote:
Hi ESanchez,

When are you planning on making a new release? (for spring boot 2 with the last PR`s merged)
I'm migration an application currently using vanilla java to Spring Boot and this starter fits perfectly (good job =D ).
Speaking about it, is there any todo list that you wanna share? I might help improve this starter.
Thank you!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Great, thank you!!
Gonna work with these todos.

I think 2.0.x should now be master, I will add another TODO in the list to move master into a 1.x branch

Hi Marcelo, I'm going to make the 2.0.x branch into master, please let me know if you want me to hold for a bit longer.

Absolutely, no need to hold =D

Done


fix(utils): support chaining with promise

Types of changes

[x] Bug fix (a non-breaking change which fixes an issue)
[ ] New feature (a non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Description

Fixing #8037
Checklist:

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly. (PR: #)
[ ] I have added tests to cover my changes (if not applicable, please state why)
[ ] All new and existing tests are passing.

Codecov Report

Merging #8038 into dev will increase coverage by 0.08%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##              dev    #8038      +/-   ##
==========================================
+ Coverage   68.87%   68.96%   +0.08%
==========================================
  Files          91       91
  Lines        3849     3837      -12
  Branches     1044     1042       -2
==========================================
- Hits         2651     2646       -5
+ Misses        971      967       -4
+ Partials      227      224       -3

Flag
Coverage Δ

#unittests
68.96% <100.00%> (+0.08%)
:arrow_up:

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

Impacted Files
Coverage Δ

packages/utils/src/task.js
100.00% <100.00%> (ø)

packages/config/src/load.js
75.28% <0.00%> (-2.63%)
:arrow_down:

packages/webpack/src/config/base.js
64.45% <0.00%> (-0.18%)
:arrow_down:

packages/webpack/src/config/client.js
69.44% <0.00%> (+6.94%)
:arrow_up:

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 0bafd77...9a4a97e. Read the comment docs.


Expose endpoint from SdkConfig

Describe the feature
For now, AwsEndpoint's Endpoint doesn't expose uri. it's only set-able, not get-able. I hope Endpoint has a function that return reference of uri.
Use Case
I tried to return public object url not using presigned url.
Proposed Solution
rust  // endpoint.rs impl Endpoint {   fn uri(&self) -> &Uri {     &self.uri   } }
Other Information
No response
Acknowledgements

[ ] I may be able to implement this feature request
[ ] This feature might incur a breaking change

A note for the community

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 "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue, please leave a comment

For your use-case, do you want the top-level endpoint (e.g., s3.us-east-1.amazonaws.com), or the full unsigned URL to the object?

I'm interested in taking on this issue, might have some questions on it

@namse - I think Endpoint actually does have a getter here: https://docs.rs/aws-smithy-http/0.48.0/aws_smithy_http/endpoint/struct.Endpoint.html#method.uri
Were you looking for something else?
@kastolars - I really appreciate the offer! However, endpoints might not be the best place to contribute right now as we're doing a pretty large overhaul of the endpoint component of the SDK right now. If you're interested in contributing in general, you can take a look at our contribution guide, and there's also a list of good first issues in our smithy-rs code generator. Contributions are welcome and I'm happy to help out!

@jdisanti I found that uri getter is new at 0.48, and I used 0.47..! Thank you for information, I close this issue.


Firefox: Kudo all not working

Using Version: <IP_ADDRESS> (666512b646)
And Firefox Version: 134.0b10 (64-bit)
The "Kudo All" button just turns to "Everything Kudoed" after clicking without doing much of anything.
Tested with all addons disabled.

Related to #219


Create pylint.yml (linter)

Forcing pull request despite linter fails so that the linter is actually added to main. Will fix issues in upcoming commits.


Unable to call vault behind forwarding Proxy

Somehow the communication is with vault behind a proxy is not possible.
After debugging and fiddeling around it seems that the https_proxy env variable is just ignored.
When I set the proxy in the transport struct manually like this:
transport := &http.Transport{
	TLSClientConfig: tlsClientConfig,
}
transport.Proxy = http.ProxyFromEnvironment

It works just fine.

I think we want to use https://golang.org/pkg/net/http/#ProxyFromEnvironment instead, but yea, this wasn't something I considered when writing this.

@sethvargo I created a pullrequest for you.

@sethvargo A you already merged it. Do you create a new container version?

0.3.0 is out


⚠ Bofrost.lu has degraded performance

In dcdfda4, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1152 ms

Resolved: Bofrost.lu performance has improved in 0722f09 after 8 minutes.


Add the Endo Monoid

An INSIDE  joke ?!?

This replaces the old Compose Monoid with this one. I went back and forth on throwing if the types did not match up, and in the end, it seemed to add a lot of overhead, and you were not aware until the function was run. So I figured we would go with the name anyway as the user can only be screamed at when run (ohhh JS, you cad)
This PR addresses Issue#90.
May revisit with some other ideas I had, but this will do for now.

Coverage remained the same at 100.0% when pulling 25a760d5350da1c70d17945b9bc98994237fc3dc on add-endo into 89acc97cd6ca8ceb86a85fefd72232810ec7f98c on master.


Preload Component

How preload component in next transition?

Hi there! Please post these questions to http://stackoverflow.com/


How do we build this?

There is this tool/build.dart file mentioned, but how do we use it? While we try to build it normally, we get compiler crashing. Specifically this error:
The compiler crashed: Crash when compiling: type 'InterfaceType' is not a subtype of type 'FunctionType' in type cast
Also, this build script calls web/popup.dart file? What is that?

The tool/build.dart script in the readme is an example to show how to write a script that compile the flutter entry point (web/popup.dart would be where your main() => runApp() would be) and all the other non-flutter entry points.

Basically, you can replace it with a shell script like that:
build.sh:
flutter build web -t web/popup.dart --csp --web-renderer=canvaskit --no-web-resources-cdn
dart compile js web/background.dart --output build/web/background.js
dart compile js web/content_script.dart --output build/web/content_script.js
dart compile js web/options.dart --output build/web/options.js

Thank you for the answer Xavier, I will try it 🙏


Error when running joe u

With latest 1.0.0, when running joe u, I get the following error :
$ joe u
Updating gitignore files..
2016/04/04 09:54:01 rename /tmp/gitignore-master /home/arthur/.joe-data: invalid cross-device link

I guess that joe is trying to make a hard link from my home to my tmp dir. That won't work as this two dirs are not on the same partition...
I suggest making a real copy instead.

After a quick look, I think the line to fix is https://github.com/karan/joe/blob/master/utils.go#L83

But it is kinda strange that the renmae fonction from go does not work between two different partitions...

Yeah my assumption was that Rename works across partitions since it's considered "safe". But I guess not. If you have the time to change it to actual copy, please do send a PR. Or I'll fix it when I get the time.


CoRoutines in cppwinnrt?

Earlier we were offered here some sample code for a coroutine in cppwinrt, which I wanted to use for enumerating MIDI devices.  I've tried plugging this into my project's main page just as it stands (without InitApartment, however, which would be duplicative), as an experiment, and it hangs up in the .get() call - never returns, so the app will not progress. I've tried various implementations, generally moved into my MIDIHandler class,  but cannot find a way to call DeviceInformation::FindAllAsync() that does not get lost in the call. This is not a MIDI issue I think; it's a general issue regarding the proper use of IAsyncAction and co_await. Something is wrong here - something missing, or a project setting, I don't know. The project I am testing this on is built on the XamlButton sample code, so I should think the project settings would be right. Does anyone know of a code illustration in straight C++ winrt that would illustrate a complete proper coroutine setup for GetDevicesAsync? Here's the sample code as it was provided, with my thanks (please pardon the formatting)
:
`#include "winrt/Windows.Devices.Midi.h"
#include "winrt/Windows.Devices.Enumeration.h"
using namespace winrt;
using namespace Windows::Foundation;
using namespace Windows::Devices::Enumeration;
using namespace Windows::Devices::Midi;
IAsyncAction Sample()
{
auto port = MidiOutPort::GetDeviceSelector();
auto devices = co_await DeviceInformation::FindAllAsync(port);
for (auto&& device : devices)
{
    printf("%ls\n", device.Name().c_str());
}

}
int main()
{
init_apartment();
Sample().get();
}`

Here's an example of using coroutines from within a UI app.
https://github.com/kennykerr/cppwinrt/blob/master/Store/XamlCode/App.cpp

That was fast! Thanks, I'll take a look.

It seems there is some deeper issue here. If I create a fire_and_forget method like that in the example, and substitute it for the device enumeration I had in my MIDIHandler, it again hangs up. Shows that this is nothing to do with MIDI enumeration in particular. Here's what I did, just for testing: I declared a method in my MIDIHandler, file_and_forget FindMIDIPorts(); In the implementation I simply tried to bring up the filepicker as described in that sample:
file_and_forget MIDIHandler::FIndMIDIPorts() {        winrt::Windows::Storage::Pickers::FileOpenPicker picker; 	picker.FileTypeFilter().Append(L".png"); 	picker.SuggestedStartLocation(PickerLocationId::PicturesLibrary); 	auto file = co_await picker.PickSingleFileAsync(); }
Then I wait until the app is fully presented with an active interface, and trigger this call with a button press: MIDIHandler->FindMIDIPorts().  Here it actually hangs up upon the declaration of the picker - never gets to the second line at all. So, though the rest of the app seems to function beautifully, nice interface, animated transitions, etc., there must be some basic flaw that is eluding me.

Perhaps it's a thread issue? On the Mac I'd use dispatch_async(dispatch_get_main_queue() and make that call in a Lambda to ensure being on the main thread.

This must be a clue. Leaving all the other stuff aside. I find that I can't even declare a FileOpenPicker without the program hanging up. This is all it takes, added at the end of my main page initialization:
FileOpenPicker filePicker;
or, alternatively,
FileOpenPicker filePicker = FileOpenPicker();
Either one of those will cause the program to get lost - it will not proceed to the next instruction. I suspect that whatever is causing that is the same thing that causes all the previous problems. Can you imagine what could cause that simple line of code to compile but not execute?

jevansAN, it looks like you're running into an issue that affected a few insider flights, where GetActivationFactoryByPCWSTR never returns from activation within FileOpenPicker, when VS is attached for debugging (e.g. see this other issue).  If you update to a recent flight, it should resolve this issue.

Scott - thanks, you're right about FileOpenPicker - finally found that reference to a bug in that, and I see that updating to the current flight fixed it. Next thing is to see if that update also fixed the other mysterious-but-similar behavior regarding enumerating devices async. Seems clearly related.

Progress: having updated to 17074, the call to DeviceInformation::FindAllAsync(port) no longer gets lost; now it just crashes with an assert failure at
template <typename Async>     void blocking_suspend(Async const& async) noexcept.     {         WINRT_ASSERT(!is_sta());
It looks as if there may be some invalid pointers referenced there. Will have to keep experimenting, but currently this is using what appears to be the exact procedure recommended in Kenny's sample.

Did you remember to resume on the UI thread before accessing any controls?
co_await ui_thread;
On Sat, Feb 3, 2018 at 2:45 PM, jevansAN<EMAIL_ADDRESS>wrote:

Progress: having updated to 17074, the call to DeviceInformation::FindAllAsync(port)
no longer gets lost; now it just crashes with an assert failure at
template  void blocking_suspend(Async const& async)
noexcept. { WINRT_ASSERT(!is_sta());
It looks as if there may be some invalid pointers referenced there. Will
have to keep experimenting, but currently this is using what appears to be
the exact procedure recommended in Kenny's sample.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/cppwinrt/issues/324#issuecomment-362861658,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ALyMIxhTmN_yAPw5cu5AbJBw6hqZMzCpks5tROGhgaJpZM4R3wUf
.

--
Scott Jones<EMAIL_ADDRESS>The Flip Flop http://scottjones.me/
"One Bit at a Time"

If the assertion is failing it means that you're calling .get() on a UI thread. That is not allowed. You may use .get() on a background thread (or any non-STA thread). For UI threads, you must use co_await rather than .get(). Calling .get() is considered a blocking wait whereas co_await is a non-blocking or cooperative wait that will not cause your UI to become unresponsive if the async operation takes a noticeable amount of time.

Thanks to both of you. I didn't know there was a thread restriction for this. But there is something I don't get about the sample code provided earlier: it uses co_await and also uses .get() to call the method containing the co_await. It looked like this (I expect the formatting will be off):
`IAsyncAction Sample()
{
auto port = MidiOutPort::GetDeviceSelector();
auto devices = co_await DeviceInformation::FindAllAsync(port);
for (auto&& device : devices)
{
    printf("%ls\n", device.Name().c_str());
}

}
int main()
{
init_apartment();
Sample().get();
}`

Thanks again for your help - this is now solved,  by just skipping the .get() part. The co_await successfully enumerated the available devices, I think (it appeared to find one output device that I will examine next). And it returned home! Makes my day.


failed to reload config: couldn't load configuration open /etc/prometheus/prometheus.yml: no such file or directory

For this POST reload to work, I have to go to the container, and do an "ls" from command line and then it works
What did you do?
xemacs@samaruc ~ $ curl -k  -X POST https://prometheus.test.mydomain.com/-/reload
What did you expect to see?
xemacs@samaruc ~ $ curl -k  -X POST https://prometheus.test.mydomain.com/-/reload
xemacs@samaruc ~ $
What did you see instead? Under which circumstances?
failed to reload config: couldn't load configuration (-config.file=/etc/prometheus/prometheus.yml): open /etc/prometheus/prometheus.yml: no such file or directory
Environment
latest docker images

System information:
insert output of uname -srm here
/etc/prometheus # uname -srm
Linux 4.4.0-78-generic x86_64

Prometheus version:

/etc/prometheus # prometheus -version
prometheus, version 1.6.3 (branch: master, revision: c580b60c67f2c5f6b638c3322161bcdf6d68d7fc)
build user:       root@a6410e65f5c7
build date:       20170522-09:15:06
go version:       go1.8.1
/etc/prometheus #

Alertmanager version:

/alertmanager # alertmanager -version
alertmanager, version 0.6.2 (branch: master, revision: b011c0a32ce887c1a10f7d34d52fd8cce485c1cf)
build user:       root@e3ca4de32142
build date:       20170509-08:56:14
go version:       go1.8.1
/alertmanager #

Prometheus configuration file:

deploy@dock-test01:/nfs/prometheus_monitoring$ cat prometheus/prometheus.yml
# my global config
global:
  scrape_interval:     30s # By default, scrape targets every 15 seconds.
  evaluation_interval: 30s # By default, scrape targets every 15 seconds.
  # scrape_timeout is set to the global default (10s).

  # Attach these labels to any time series or alerts when communicating with
  # external systems (federation, remote storage, Alertmanager).
  external_labels:
      monitor: 'dock-test'

# Load and evaluate rules in this file every 'evaluation_interval' seconds.
rule_files:
  - "alert.rules"
  - "host.rules"
#  - "container.rules"

# A scrape configuration containing exactly one endpoint to scrape:
# Here it's Prometheus itself.
scrape_configs:
  # The job name is added as a label `job=<job_name>` to any timeseries scraped from this config.
  - job_name: 'prometheus'
    scrape_timeout: 30s
    dns_sd_configs:
    - names:
      - 'tasks.prometheus'
      type: 'A'
      port: 9090

  - job_name: 'cadvisor'
    dns_sd_configs:
    - names:
      - 'tasks.cadvisor'
      type: 'A'
      port: 8080

  - job_name: 'node-exporter'
    dns_sd_configs:
    - names:
      - 'tasks.node-exporter'
      type: 'A'
      port: 9100

  - job_name: 'mysqld-exporter'
    dns_sd_configs:
    - names:
      - 'tasks.mysqld-exporter'
      type: 'A'
      port: 9104

  - job_name: 'postgres-exporter'
    dns_sd_configs:
    - names:
      - 'tasks.postgres-exporter'
      type: 'A'
      port: 9187

Alertmanager configuration file:

global:
    smtp_smarthost: smtp.gmail.com:587
    smtp_from<EMAIL_ADDRESS>route:
    receiver: 'mail-test'
    group_wait: 10s

receivers:
    - name: 'mail-test'
      email_configs:
      - to<EMAIL_ADDRESS>        from<EMAIL_ADDRESS>        smarthost: smtp.gmail.com:587
        auth_username<EMAIL_ADDRESS>        auth_identity<EMAIL_ADDRESS>        auth_password: "asdf"

Logs:

time="2017-05-26T07:16:29Z" level=error msg="Error reloading config: couldn't load configuration (-config.file=/etc/prometheus/prometheus.yml): scrape timeout greater than scrape interval for scrape config with job name \"prometheus\"" source="main.go:179"
time="2017-05-26T07:17:44Z" level=info msg="Loading configuration file /etc/prometheus/prometheus.yml" source="main.go:251"
time="2017-05-26T07:17:44Z" level=error msg="Error reloading config: couldn't load configuration (-config.file=/etc/prometheus/prometheus.yml): open /etc/prometheus/prometheus.yml: no such file or directory" source="main.go:179"
time="2017-05-26T07:18:06Z" level=info msg="Loading configuration file /etc/prometheus/prometheus.yml" source="main.go:251"
time="2017-05-26T07:18:06Z" level=error msg="Error reloading config: couldn't load configuration (-config.file=/etc/prometheus/prometheus.yml): open /etc/prometheus/prometheus.yml: no such file or directory" source="main.go:179"
time="2017-05-26T07:18:41Z" level=info msg="Loading configuration file /etc/prometheus/prometheus.yml" source="main.go:251"

Support questions should be asked at https://groups.google.com/forum/#!forum/prometheus-users