[Event Request] Codeunit 86 "Sales-Quote to Order".OnTransferQuoteToOrderLinesOnBeforeUpdatePrepaymentPct

Describe the request
Please do variable Customer with var
    [IntegrationEvent(false, false)]
    // ---------------------------------------------------------------OnTransferQuoteToOrderLinesOnBeforeUpdatePrepaymentPct:BEGIN
    //local procedure OnTransferQuoteToOrderLinesOnBeforeUpdatePrepaymentPct(var SalesQuoteLine: Record "Sales Line"; var SalesQuoteHeader: Record "Sales Header"; var SalesOrderLine: Record "Sales Line"; var SalesOrderHeader: Record "Sales Header"; Customer: Record Customer)
    local procedure OnTransferQuoteToOrderLinesOnBeforeUpdatePrepaymentPct(var SalesQuoteLine: Record "Sales Line"; var SalesQuoteHeader: Record "Sales Header"; var SalesOrderLine: Record "Sales Line"; var SalesOrderHeader: Record "Sales Header"; var Customer: Record Customer)
    // ---------------------------------------------------------------OnTransferQuoteToOrderLinesOnBeforeUpdatePrepaymentPct:END
    begin
    end;

Additional context
We would like change customer prepayments % before use.
Internal work item: AB#558155

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 27498.


Added support for negative nthreads and resp. documentation.

Description
This makes nthreads accept negative numbers to mean m_pool->size() + nthreads. I.e. on a 16 core machine specifying nthreads as -2 would make OIIO use 14 cores.
If m_pool->size() < -nthreads the result is clamped at 1. I.e. a single thread would be used.
On that note: the original resolve() does not have a check for the case where m_maxthreads > m_pool->size() and should possibly be clamped to the latter, if so. I kept it that way. Is that intended/a feature or an oversight?
Tests
Checklist:

[x] I have read the contribution guidelines.
[x] I have updated the documentation, if applicable.
[ ] I have ensured that the change is tested somewhere in the testsuite
(adding new test cases if necessary).
[ ] If I added or modified a C++ API call, I have also amended the
corresponding Python bindings (and if altering ImageBufAlgo functions, also
exposed the new functionality as oiiotool options).
[x] My code follows the prevailing code style of this project. If I haven't
already run clang-format before submitting, I definitely will look at the CI
test that runs clang-format and fix anything that it highlights as being
nonconforming.

Why this can be better than
std::thread::hardware_concurrency() - 2
?

Why this can be better than
std::thread::hardware_concurrency() - 2 ?

Because it means 2 less than the pool size, not the HW threading size.
Because it can get passed from all sorts of places where it's not convenient to call C++ std::thread_hardware_concurrency(). Like Python? Or from command line args?

I think that your changes only alter the meaning of the nthreads parameter to IBA functions. It is worth noting that there are a few other places where number of threads are passed:

The setting of the thread pool size with OIIO::attribute("threads", n)
ImageInput/ImageOutput::threads()
ImageBuf::threads()
Utility functions such as parallel_convert_image()
The paropt structure used by parallel loops and such in parallel.h

Do we want to change those also? If we don't, will this create confusion?
Do those other places misbehave if passed negative thread counts? That's something we may never have considered before because... why would anybody do that? But now, we're giving people a reason to pass negative thread counts, at least in some places, which means we should expect people to do it inadvertently it in any of the other places.


Create custom token using a service account ID

Hi, I'm trying to create custom token for specified service account from different service account. I'm following this guide: https://firebase.google.com/docs/auth/admin/create-custom-tokens#using_a_service_account_json_file (Using a service account ID).
When I configure it like that and try to generate a token, that token is invalid. So I started debugging:
https://github.com/firebase/firebase-admin-dotnet/blob/5397e845fef87124940ba99cb1225e6c04210ba2/FirebaseAdmin/FirebaseAdmin/Auth/FirebaseTokenFactory.cs#L74-L95
If I set debugger on here and set serviceAccount value to null, I get a valid token. So it seems like it's using wrong service account.
Can app.Options.Credential.ToServiceAccountCredential() be null? You cannot even initialize FirebaseApp without setting Credential = GoogleCredential.GetApplicationDefault().
Shouldn't the logic be that it should first check if a service account ID is specified and invoke the IAM service, and only if not it should go for other cases?

When I configure it like that and try to generate a token, that token is invalid.

What do you mean by that? The SDK cannot generate an "invalid" token as long as the service account used to sign it is valid. Unless you're using a service account from project A and using the resulting token to sign into project B.

Can app.Options.Credential.ToServiceAccountCredential() be null?

Yes, some application default credential implementations are not of the ServiceAccountCredential type -- especially the ones that are auto discovered in managed cloud environments. See https://github.com/googleapis/google-api-dotnet-client/tree/master/Src/Support/Google.Apis.Auth/OAuth2

Shouldn't the logic be that it should first check if a service account ID is specified and invoke the IAM service, and only if not it should go for other cases?

The SDK prefers ServiceAccountCredential over service account ID, as that is the fastest way to sign tokens. This is the established priority order in all Admin SDK implementations.
I'll keep this open in case you want to follow up on that "invalid token" issue. But as it stands, I don't see any direct action items for this repo.

Unless you're using a service account from project A and using the resulting token to sign into project B.

Yes. That's what I'm trying to achieve. I'm using service account from project A, I set ServiceAccountId from another project B and expect to generate token with which I could sign into project B.

That's not allowed. When you're setting a service account ID, the SDK has to invoke the Cloud IAM API to sign the token remotely with that service account ID: https://cloud.google.com/iam/reference/rest/
That API call is authorized with the credentials you have specified (or application default credentials if unspecified). You cannot authorize an IAM API call with credentials from project A, and ask it to sign a token using a service account in project B.

But it's possible, @hiranya911 ? because if I set serviceAccount to null (debugging) it sets signer as that: signer = new FixedAccountIAMSigner(app.Options.HttpClientFactory, app.Options.Credential, app.Options.ServiceAccountId); in that case at first I get this error:

Permission iam.serviceAccounts.signBlob is required to perform this operation
on service account projects/-/serviceAccounts/{your-service-account-id}.

this error is documentated here https://firebase.google.com/docs/auth/admin/create-custom-tokens
But if I add Service Account Token Creator role for service account from project A to project B IAM it works fine.

Yes, but this cross pollination of projects and service accounts is not something we wish to support or advertise. It's often very confusing to reason about the permissions of projects this way. Also this works today because we don't put the project ID in the IAM endpoint (notice the /projects/-/ part in the error message). That might change in the future, or IAM might change how the project ID inference works. At very least we want to retain the flexibility to change such details in future implementations.
You should look into using one of the following options to implement your use case.
Option 1: Init the SDK with credentials for project B
As it stands, I don't see why you use a service account from project A while trying to create custom tokens for project B. Just use credentials for project B if at all possible.
Option 2: Use two FirebaseApp instances:
var project_A_app = FirebaseApp.Create(new AppOptions
{
   // Service account for project A
});

var project_B_app = FirebaseApp.Create(new AppOptions
{
   // Service account or ADC for project B
   // Service Account ID
}, "CustomTokenApp");

Use the latter for creating tokens and the former for interacting with project A.
Option 3: Implement a custom GoogleCredential implementation
Wrap project A's service account credential inside a custom GoogleCredential so it doesn't get picked for local token signing. You will likely have to wrap the service account in an ICredential first. See how the AccessTokenCredential is implemented to get an idea: https://github.com/googleapis/google-api-dotnet-client/blob/master/Src/Support/Google.Apis.Auth/OAuth2/GoogleCredential.cs#L143


Overlapping accesses to 'result', but modification requires exclusive access; considering copying to a local variable

I was attempting to port this FFT exampling into my project but received a compile time error.
fft.swift:186:41: Overlapping accesses to 'result', but modification requires exclusive access; consider copying to a local variable

should be fixed with the PR


[Feature] Support dynamic modification of datacache.enable

Supports dynamic modification of table and partition level datacache.enable attributes:

Synchronously modify the datacache.enable of the shardGroup in StarManager through StarManager's updateShardGroup rpc.
Through the heartbeat detection of the starlet worker, asynchronously modify the cache enable status of the starlet worker.

Why I'm doing:
What I'm doing:
Fixes #issue
What type of PR is this:

[ ] BugFix
[X] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Does this PR entail a change in behavior?

[x] Yes, this PR will result in a change in behavior.
[ ] No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

[ ] Interface/UI changes: syntax, type conversion, expression evaluation, display information
[X] Parameter changes: default values, similar parameters but with different default values
[ ] Policy changes: use new policy to replace old one, functionality automatically enabled
[ ] Feature removed
[ ] Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

[ ] This is a backport pr

Bugfix cherry-pick branch check:

[X] I have checked the version labels which the pr will be auto-backported to the target branch

[X] 3.2
[X] 3.1
[ ] 3.0
[ ] 2.5

replace #33877


How to prolong the logged-in time in webmail?

By default, it's around 2 weaks, right? How to prolong it?

A session expires after 24 hours inactivity. It is extended each time it is used. The idea is that if you use the webmail every day, you won't have to login again.
The 24 hours is configured here:
https://github.com/mjl-/mox/blob/v0.0.11/store/session.go#L22
Which is being called through the webauth package:
https://github.com/mjl-/mox/blob/v0.0.11/webauth/webauth.go
By the way, the admin interface has sessions that aren't extended, and aren't persisted.
Perhaps this would already help you prevent getting expired sessions? Or perhaps we can find an other good (and still safe) heuristic for extending sessions.

That's ok. I check it daily, but sometimes I may be on the road.
Other than making it configurable, with the default value of 24h, how else could it be done?

I've got the same, once in a while it turns out I didn't read email for a day (in the webmail). I see it as a good signal I may be relaxing a bit. (:
We could make it a per-account setting (override of the default 24h) if it's really important enough. But I prefer to keep configurable options down. Perhaps it would help (with expectations, possibly letter user adjust behaviour) if we explain in the UI that sessions are automatically extended, only expiring after 24h inactivity.

@ally9335 FYI, the commit just now causes the "session expired" message (shown above the login form when using a session fails) to show why that may have happened. Hopefully this helps other users discover what the behaviour is.


Animate artist follow

Closes https://github.com/artsy/eigen/issues/1440

          1 Warning

:warning:
The following files do not have tests: lib/components/artist/header.js, lib/components/buttons/inverted_button.js, lib/components/home/artist_rails/artist_card.js & lib/components/home/artist_rails/artist_rail.js

  Generated by :no_entry_sign: danger

@mennenia @sarahscott Whoever gets to it first, and has the time, can go ahead and review.

using all the review features ;)

hrm, this is going to require somehow telling the deploy script ( https://github.com/artsy/emission/blob/master/scripts/deploy_apphub.sh ) that is needs to use that specific scheme

@orta It needs to use the Deploy configuration, not scheme. That can’t be hard right? Setting configurations is a very normal thing to do.

For Cocoa dev, these are not the kind of things RN people commonly do, will have a look through the tools, otherwise this breaks the deploy from master stuff

I'll do my research now

Looks like I was wrong, this will only affect us when we upload emission.app - not the app hub JS deploys

Considering those are not automated, that's fine


Support themes

Define at runtime some colors and characters used for special effects (border, highlight, shadow, ...).
Probably provide a default theme that looks like the blue interface used by classic ncurses dialog applications.

Initial theme support. Using non-standard colors breaks compatibility with TTY terminals, so we may want to check for support before doing that (and fallback to default colors when we have to).
Better theme support would enable to:

Disable shadows
Change default padding
(maybe) Change layout for default views

A dummy theme example file shows what the options could be. No parser exist for it yet, though.

Latest commit rework how themes work, and correctly parse the example theme file.
Still left to do: shadows and borders.

Themes are currently properly applied and affect the way views are drawn.
They don't currently affect their layout though. This means disabling shadows or borders doesn't actually make the views smaller.
Changing that would require either:

Modifying the get_min_size and layout methods to accept a theme as parameter
Add a global variable with the current theme

I'm not a big fan of either... :(
We'll probably go with the first solution, unless I find something better.

With "real" full-screen views now available (independantly of the shadow style), having the theme affect the layout is not as important anymore.
The other candidate for styled layout would be a Dialog with horizontal/vertical buttons, but dealing with this at the Dialog level looks easier.
So I think themes are complete for now.


chore: update data explorer scaler to fix deprecation

Signed-off-by: Jorge Turrado<EMAIL_ADDRESS>Checklist

[x] Commits are signed with Developer Certificate of Origin (DCO - learn more)

Fixes https://github.com/kedacore/keda/issues/2989

/run-e2e azure-data*

/run-e2e azure-data*

/run-e2e azure-data*


added generic pointer type to variant

Now that the DLScript module is in master it would be nice to have a way to pass generic pointers between DLScripts or a DLScript and a module.
This new Variant field is not intended to be used in GDScript, you can't interact with it. (only like you can with null, but even less since null can be casted to a number).
This is great for datatypes that have no proper representation in Godots Variant type.
For example, I once made a small OpenCL module for Godot. There was no way I could easily pass a cl_mem object to GDScript. GDScript used this cl_mem object only as a handle. This is what this PR is about.
You can't create a pointer from GDScript, you can't get the value of that pointer. You can't cast it to anything. It's only possible in C++/DLScript, so when using it in a script there's no danger of using it in unintended ways.

I also added a function to the C API that lets you retrieve the pointer to the userdata for a ScriptInstance.

I am unconvinced of the usefulness of this.. cant an integer be used
instead? Variant integer is 64 bits, you should be able to cast.
On Apr 4, 2017 12:47 PM, "Thomas Herzog"<EMAIL_ADDRESS>wrote:

Now that the DLScript module is in master it would be nice to have a way
to pass generic pointers between DLScripts or a DLScript and a module.
This new Variant field is not intended to be used in GDScript, you can't
interact with it. (only like you can with null, but even less since null
can be casted to a number).
This is great for datatypes that have no proper representation in Godots
Variant type.
For example, I once made a small OpenCL module for Godot. There was no way
I could easily pass a cl_mem object to GDScript. GDScript used this cl_mem
object only as a handle. This is what this PR is about.
You can't create a pointer from GDScript, you can't get the value of that
pointer. You can't cast it to anything. It's only possible in C++/DLScript,
so when using it in a script there's no danger of using it in unintended
ways.
I also added a function to the C API that lets you retrieve the pointer to
the userdata for a ScriptInstance.
You can view, comment on, or merge this pull request online at:
https://github.com/godotengine/godot/pull/8262
Commit Summary

added generic pointer type to variant

File Changes

M core/variant.cpp
https://github.com/godotengine/godot/pull/8262/files#diff-0 (15)
M core/variant.h
https://github.com/godotengine/godot/pull/8262/files#diff-1 (6)
M modules/dlscript/dl_script.h
https://github.com/godotengine/godot/pull/8262/files#diff-2 (2)
M modules/dlscript/godot.cpp
https://github.com/godotengine/godot/pull/8262/files#diff-3 (10)
M modules/dlscript/godot.h
https://github.com/godotengine/godot/pull/8262/files#diff-4 (2)
M modules/dlscript/godot/godot_variant.cpp
https://github.com/godotengine/godot/pull/8262/files#diff-5 (15)
M modules/dlscript/godot/godot_variant.h
https://github.com/godotengine/godot/pull/8262/files#diff-6 (4)

Patch Links:

https://github.com/godotengine/godot/pull/8262.patch
https://github.com/godotengine/godot/pull/8262.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/godotengine/godot/pull/8262, or mute the thread
https://github.com/notifications/unsubscribe-auth/AF-Z22Ii20k8xu5AbruU6UPUjdra7ynSks5rsmYWgaJpZM4MzDf6
.

@karroffel Actually, you should add casts into TYPE_BOOL and TYPE_STRING, just in case someone uses it in an if or print

It also makes variant more error prone IMO. I insist that it's simply
better to cast the pointer to integer.
On Apr 4, 2017 2:20 PM, "Bojidar Marinov"<EMAIL_ADDRESS>wrote:
@karroffel https://github.com/karroffel Actually, you should add casts
into TYPE_BOOL and TYPE_STRING, just in case someone uses it in an if or
print
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/godotengine/godot/pull/8262#issuecomment-291570743,
or mute
the thread
https://github.com/notifications/unsubscribe-auth/AF-Z267CkLfFBwyubTBetrzwUUTE1TBaks5rsnv1gaJpZM4MzDf6
.

Alright, my intention was to make it less error prone than using an integer, since you can modify that integer, you can't modify a pointer.
But I get it for the point of simplicity.
I'll make a new PR with just the DLScript changes.


Fix name in POMs

The name in the POM was incorrect.  Was picking up the name from under the issue management config.
Reviewer checklist

[ ] Read the contributing guide
[ ] PR should be motivated, i.e. what does it fix, why, and if relevant, how
[ ] Ensure relevant issues are linked (description should include text like "Fixes #")
[ ] Ensure any appropriate documentation has been added or amended

Coverage: 98.238%. Remained the same when pulling 6d7d3882888c9ad11688a643eed87bdff890de93 on pom into 502c1c1fe539b6a5bc86086327a92465047cfe71 on main.


BrDot - HIP19 third party manufacturer application

HIP19 process - this is the BrDot application as a third-party manufacturer.
Thank you very much in advance for your review.

Hm I am unable to access the source repository to repair the deleted TEMPLATE.md file – @Sophi we might have to do some surgery on this to get it merged in

I'm unable to access the original repo to push changes and can't merge due to conflicts. Merged manually with 61f26462881fa9121e0c92b2dd4d60d884daa9fd -- closing this


Compatible with 3.0?

Has anyone tried to upgrade to Firebase API v 3 (released today 5/18/2016) ?  With ember-simple-auth still work with the changes?

Please use this for issues and refer to stackoverflow.com for questions.


Just Found Out This Tool Silently Deletes Client.txt - Please Rename it Instead

While looking at the code I was very surprised to find out that it deletes the user's Client.txt outright, without ever asking or mentioning this. All this time I had no idea that my Client.txt was being flushed every run and long gone.
While this isn't a huge deal in the grand scheme of things, it bothers me that I can no longer dig through my Client.txt to find previous messages and whatnot. Especially since this behavior was never listed anywhere that I know of.
My suggestion is to rename the file (based on timestamp & date) instead of deleting. The user can then delete the file(s) at their leisure, similar to how the game normally works.

I delete the client.txt file because GGG never uses it or rotates it based on timestamp and date. Mine had grown to almost a gig and took over 15 minutes to open! While I understand the attachment to the log and the desire to look back in it, I'm not going to take time this league to code in a rotating log that GGG should have done in the first place.
I left notes in the script on how to disable the deletion of the client.txt file if you would like to keep yours. However, over time, this will greatly slow down the script as it has to load that file every couple seconds to check for new entries.
You can also backup the file yourself by renaming it before launching my script. It only deletes on script launch, so if you leave the script running your file is safe.
I apologize for not listing that I delete the client.txt file more clearly, I did not think it would affect most people and I didn't want to scare people by announcing I delete a file. (I clearly state it in the code for anyone reading it, I just didn't announce it in the readme).
Perhaps in my next update I'll code something in that protects that file, but again, it will grow forever and take up space on your hard drive you don't even know about. Let me know if that's really something you want and I'll consider it.

Instructions are in this commit: 2d337e40729746d4e827942192bd8fb892b0124e
I'll leave this open for a response from you.

I'm not personally affected (nor most people, I'm sure), but I was surprised when I found out. At the end of the day I don't really care that much. It's just a philosophical position I hold, that a program should never modify third party files without asking or notifying the user.

I now only delete the file if it's over 10Mb, and I give a clear warning before doing it. I also allow the user to cancel if they want to keep the file.
Thanks again for pointing out issues.

Ohhh nice, thanks for that!


Please expose methods for changing backgroundColor, shadowColor, elevation etc..

Please expose methods for changing backgroundColor, shadowColor, elevation.. and for all the XML attributes, so that we can programmatically set those properties at runtime

Hi!
Sorry for being so late, I rarely check my github notifications lol. I will add what you said, meanwhile you can copy the library class to your project and add the needed stuff =)

Good to hear that. Thanks @4inodev 😃


Multiple view of cameras in a render window simultaneously.

Hi,
I'm a student and I'm trying to use MuJoCo for RL based robot control tasks .
I'm looking for some help about plot camera views.
I want to add camera image on render window. So, I wish the main camera and sub-camera could be simultaneously plotted in the window.
(I can do some simple add geoms. But I can't find add image or view in rendering window.)

Like the picture above in the gazebo.
Here is a screenshots in Gazebo, illustrating my question:
I'd really appreciate your help.

Hi @joonhyung-lee, this is definitely possible.
See this side PR I worked on a few months ago to add a depth camera overlay in the simulate executable.

Side note: if you are using the Python bindings, you can simply do 2 calls to the render function with different camera_id values and potentially height/width values and then do stacking/overlaying logic in python.

Thank you very much for your answer with very detailed information.
I checked all the contents of the links.
However, I wonder how I can perform the stacking/overlaying part in the render window using the python code.
I can get the depth image, and I wonder how I can overlay this image on rendering window. Could you help me?
(I know how to simply overlay the text, but I can't apply it to the image.)

@joonhyung-lee What rendering window are you using?

@kevinzakka I meant the render window that is output when using the mujoco library.
    every_second = 1 # (second)
    if (tick % int(every_second/dt/nstep)) == 0:
        img = np.zeros((viewer.viewport.height,viewer.viewport.width,3),dtype=np.uint8)
        depth_img = np.zeros((viewer.viewport.height,viewer.viewport.width, 1), dtype=np.float32)

        mujoco.mjr_render(viewer.viewport, viewer.scn, viewer.ctx)
        mujoco.mjr_readPixels(img, depth_img, viewer.viewport, viewer.ctx) # this makes a little delay

        img = np.flipud(img) # flip image
        depth_img = np.flipud(depth_img) # flip image

        imgs.append(img)
        depth_imgs.append(depth_img)
        img_ticks.append(tick)

@jwcho0609 Thanks to kevinzakka's instructions I was able to get it working. Check out my simple implementation: https://github.com/dtorre38/mujoco_opencv.git

I don't recognize that window, is that a third party viewer library? In any case, the code link I sent you has all the ingredients necessary to overlay a second camera view in this window.

Create a rectangular viewport in the upper right corner for example.
Specify a different camera view by updating the scene with mjv_updateScene.
Render the scene in the offscreen buffer with mjr_render.
Read the pixels with mjr_readPixels.
Call mjr_drawPixels using the rectangular viewport you created in step 1.

Here i am sharing part of the code, that i wrote following the instructions to add an overlay cam by @kevinzakka.
# Create a viewport in the upper right corner
self.viewport_width, self.viewport_height = self.glfw.get_framebuffer_size(self.window)
camera_width, camera_height = 320, 240
self.camera_buffer = mj.MjrRect(self.viewport_width - camera_width, self.viewport_height - camera_height, camera_width, camera_height)
# Create a separate camera object for rendering the sensor feed
self.cam_sensor_id = self.data.cam("add-your-cam-name").id
self.camera_sensor_view = mj.MjvCamera()
self.camera_sensor_view.fixedcamid = self.cam_sensor_id
self.camera_sensor_view.type = mj.mjtCamera.mjCAMERA_FIXED
# ...
# in the sim loop add this
while not self.glfw.window_should_close(self.window):
            # ...
            # sim logic
            # ...
            # Render the camera view to the offscreen buffer (NOT the main simulation window)
            mj.mjv_updateScene(self.model, self.data, self.opt, None, self.camera_sensor_view, mj.mjtCatBit.mjCAT_ALL.value, self.scene)
            mj.mjr_render(self.camera_buffer, self.scene, self.context)

I don't recognize that window, is that a third party viewer library? In any case, the code link I sent you has all the ingredients necessary to overlay a second camera view in this window.

Create a rectangular viewport in the upper right corner for example.
Specify a different camera view by updating the scene with mjv_updateScene.
Render the scene in the offscreen buffer with mjr_render.
Read the pixels with mjr_readPixels.
Call mjr_drawPixels using the rectangular viewport you created in step 1.

Here i am sharing the code i wrote following @kevinzakka instructions to add a cam overlay.
Create a viewport in the upper right corner
self.viewport_width, self.viewport_height = self.glfw.get_framebuffer_size(self.window)
camera_width, camera_height = 320, 240
self.camera_buffer = mj.MjrRect(self.viewport_width - camera_width, self.viewport_height - camera_height, camera_width, camera_height)
Create a separate camera object for rendering the sensor feed
self.cam_sensor_id = self.data.cam("add-your-cam-name").id
self.camera_sensor_view = mj.MjvCamera()
self.camera_sensor_view.fixedcamid = self.cam_sensor_id
self.camera_sensor_view.type = mj.mjtCamera.mjCAMERA_FIXED
...
in the sim loop add this
while not self.glfw.window_should_close(self.window):
# ...
# sim logic
# ...
# Render the camera view to the offscreen buffer (NOT the main simulation window)
mj.mjv_updateScene(self.model, self.data, self.opt, None, self.camera_sensor_view, mj.mjtCatBit.mjCAT_ALL.value, self.scene)
mj.mjr_render(self.camera_buffer, self.scene, self.context)

@dtorre38 Have you been able to fix the depth overlay issue? It seems that the current version of Mujoco does not support overwriting the rendered window's pixel values via mjr_drawPixels.
I copy-pasted @jwcho0609 's code into 3.2.5 simulate.cc, with the same placement and all, and then I try to set the value of the final depth8 array all to 0, since that should render the small window to all black. But it seems that the window ignores everything after mjr_render is called.
I've made sure that there is no additional mjr_render calls that refers to this overlay viewport either.
// show depth overlay
void ShowDepth(mj::Simulate* sim, mjrRect rect) {
  // constant width with and without profiler
  int width = sim->profiler ? rect.width/3 : rect.width/4;

  // render figure in the top right
  mjrRect viewport = {
    rect.left + rect.width - width,
    rect.bottom + rect.height - rect.height/3,
    width,
    rect.height/2
  };

  /*
  // render scene in offscreen buffer
  */
  mjr_render(viewport, &sim->scn, &sim->platform_ui->mjr_context());

  int total = viewport.width*viewport.height;

  // read depth buffer, values are in range [0, 1]
  std::unique_ptr<float []> depth(new float[total]);
  mjr_readPixels(nullptr, depth.get(), viewport, &sim->platform_ui->mjr_context());

  // convert to meters
  float extent = sim->m_->stat.extent;
  float near = sim->m_->vis.map.znear * extent;
  float far = sim->m_->vis.map.zfar * extent;
  for (int i=0; i<total; ++i) {
    depth[i] = near / (1.0f - depth[i] * (1.0f - near/far));
  }

  // convert to a 3-channel 8-bit image
  std::unique_ptr<unsigned char[]> depth8(new unsigned char[3*viewport.width*viewport.height]);
  for (int i=0; i<viewport.width*viewport.height; i++) {
    unsigned char depth_value = (unsigned char)((1.0f - depth[i]) * 255.0f);
    depth8[3*i]     = depth_value;
    depth8[3*i + 1] = depth_value;
    depth8[3*i + 2] = depth_value;

  }
 // Simple test pattern (black image) for debugging
  // std::unique_ptr<unsigned char[]> depth8(new unsigned char[3 * viewport.width * viewport.height]);
  memset(depth8.get(), 0, 3 * viewport.width * viewport.height);  // Set all pixels to black

  // This does not do anything; original color image is rendered no matter what
  mjr_drawPixels(depth8.get(), nullptr, viewport, &sim->platform_ui->mjr_context());
}

@tenfoldpaper My issue was solved via https://github.com/dtorre38/mujoco_opencv/issues/2#issuecomment-2239438569. It turns out that glClear(GL_DEPTH_BUFFER_BIT) must be called before mjr_drawPixels().

@tenfoldpaper My issue was solved via dtorre38/mujoco_opencv#2 (comment). It turns out that glClear(GL_DEPTH_BUFFER_BIT) must be called before mjr_drawPixels().

That's amazing, it worked without the hack!
For reference, in C++, this requires the following:
# In the CMakeLists.txt for simulate
...
find_package(OpenGL REQUIRED)
...
# in the executable
target_link_libraries(
    simulate
    libsimulate
    mujoco::mujoco
    glfw
    OpenGL::GL # <-- add this
    Threads::Threads
    lodepng
  )
...

// in the simulate.h header
#include <GL/gl.h>
...

// in the simulate.cc, depthshow function:
  ...
  // render colorized depth
  glClear(GL_DEPTH_BUFFER_BIT);
  mjr_drawPixels(depth8.get(), nullptr, viewport, &sim->platform_ui->mjr_context());


Juggle context param with event maps

When using event maps, it's a little nicer to specify the context parameter as the second argument. This keeps backwards compatibility with 1.1.2, though the feature wasn't documented.
obj.on({
    a: method,
    b: other
}, context);

When you explicitly pass a context, we don't override.
obj.on({
    a: function() { ok(this === context); },
}, otherContext, context);

:+1:

As it turns out this also explained the call stack error I was getting earlier.  I was using a backbone.radio channel and setting the context of a hash of events as in this issue, but one of the events listened to was all.  It was then attempting to trigger an event on the object using the radio channel, but since the context was wrong it was triggering on itself.
Here's a simple example: http://codepen.io/paulfalgout/pen/pJypOb
var channel = new Backbone.Model();

$(window).on('mousedown', function(){
  channel.trigger('something');
});

var Service = Backbone.Model.extend({
  initialize: function(){
    // This works
    //channel.on('all', this.triggerActivity, this);

    // This doesn't
    channel.on({ 'all': this.triggerActivity }, this);
  },
  triggerActivity: function(){
    console.log('about to trigger');
    // in bb 1.2.0 this == channel causing the callstack exceeded bug
    // in bb 1.1.2 this == Service
    this.trigger('activity');
  }
});

new Service();

Is this not something that'd go out with 1.2.1?  @jashkenas

I'll merge this tomorrow unless there are objections.


Possible to use this with a self-signed certificate?

Thanks for your work on this.  I've been able to connect successfully to NAV using NTLM authentication.
Recently we switched the NAV instance to use HTTPS with a self-signed certificate.
Now I'm getting:
PHP Fatal error:  SOAP-ERROR: Parsing WSDL: Couldn't load from 'https://<url scrubbed>' : failed to load external entity "https://<url scrubbed>/Page/Item"
 in <scrubbed>/vendor/matejsvajger/ntlm-soap-client/src/NTLMSoap/Model/BaseClient.php on line 39

For test purposes, I tried adding
  curl_setopt($this->ch, CURLOPT_SSL_VERIFYPEER, false);
to both places in the code where a curl handle is created, but I'm still getting the same error.
If you have any ideas, I would be be happy to hear them!

I have implemented HTTPS support in this PR:
https://github.com/matejsvajger/ntlm-soap-client/pull/4
Closing this ticket.


add new alert for AAP

Add new alerts to monitor AAP:

AAPMetricMissing: make sure the AAP metrics are valid
AAPEndpointAddressNotReady: make sure the AAP endpoint is ready

Signed-off-by: Song Song Li<EMAIL_ADDRESS>

/hold

TODO: add the runbook for this new alerts

lgtm, thanks!

/unhold


Error building Standalone Application

Dear,
I am referring to instructions given on BUILDING.md page.
I get error when I try to build Standalone application.
Error Description:
../../src/include/Weave/Support/crypto/WeaveRNG.h:33:2: error: #error "INVALID WEAVE CONFIG: OpenSSL RNG implementation enabled but OpenSSL not available (WEAVE_CONFIG_RNG_IMPLEMENTATION_OPENSSL == 1 && WEAVE_WITH_OPENSSL == 0)."
#error "INVALID WEAVE CONFIG: OpenSSL RNG implementation enabled but OpenSSL not available (WEAVE_CONFIG_RNG_IMPLEMENTATION_OPENSSL == 1 && WEAVE_WITH_OPENSSL == 0)."
^~~~~
I am using Ubuntu 18.
Screenshot of error: Please open the link: https://goo.gl/iPzw4e
One more suggestion: OpenWeave TAG on StackOverFlow is not active. No users are actively commenting on it. Please make it active.

Hi raupune,
Thank you for your interest in OpenWeave.
From the error message you posted, it looks like you don't have the openssl development package installed.  Try installing libssl-dev using the following command:
sudo apt-get install libssl-dev
If that doesn't work, it would be useful for us to see the contents of your configure log file.  By default this file is located at build/x86_64-unknown-linux-gnu/config.log within your source directory.  If you can attach this file to the issue we can investigate further.
Regarding establishing an openweave tag on StackOverflow, tags are generally created as people ask questions.  However we will look into expressly requesting the openweave tag to be created.
--Jay

Thanks. Issue solved.


Full build checks for the master branch PRs are getting hanged intermittently

Description
Due to $subject, there has been a huge queue for the workflow jobs with the platform repos. Refer to https://github.com/ballerina-platform/ballerina-lang/actions/runs/3369201951 as an example scenario, where 4 out of 8 jobs for ballerina-lang:Full build pipeline is hanging and consuming resources for 6 hrs each.
The related workflow (https://github.com/ballerina-platform/ballerina-lang/actions/workflows/pull_request_full_build.yml) is manually disabled until getting fixed.
Steps to Reproduce
No response
Affected Version(s)
No response
OS, DB, other environment details and versions
No response
Related area
-> CICD
Related issue(s) (optional)
No response
Suggested label(s) (optional)
No response
Suggested assignee(s) (optional)
No response

One more check we can introduce is to reduce timeouts to 2 hrs max.

Hanging for distribution is reproducible in FBP https://github.com/ballerina-platform/ballerina-release/actions/runs/3372000434/jobs/5594915567

Reopening as the issue of distribution dev tools tests hanging still needs to be identified and fixed

@NipunaMadhushan Seems the timeout option is not applying to the other builds in the matrix,
https://github.com/ballerina-platform/ballerina-lang/actions/runs/3391545211

Noticed concurrency setting not being applied for jobs in the matrix. @NipunaMadhushan FYA

Noticed that every PR check for ballerina-distribution hanged from project-api-tests.
Executing: /home/runner/work/ballerina-lang/ballerina-lang/project-api-tests/build/test-distribution/ballerina-2201.3.0-SNAPSHOT-swan-lake/bin/bal push /tmp/bal-test-integration-packaging-workspace-8631619587375541510/disttestpackbeta6/bctestorg-disttestpackbeta6-any-1.1.0.bala


Docker fails to create network bridge on start up

Description of problem:
When freshly installing the docker 1.9.0 daemon, it sometimes fails to create the network bridge at startup and thus fails to start the daemon. It seems to fail about 50% of the time and I'm not sure why. Here's some of the log output:
time="2015-11-20T05:32:35.395996380Z" level=info msg="API listen on /var/run/docker.sock"
time="2015-11-20T05:32:35.415570660Z" level=info msg="Firewalld running: false"
time="2015-11-20T05:32:35.441312772Z" level=info msg="Default bridge (docker0) is assigned with an IP address <IP_ADDRESS>/16. Daemon option --bip can be used to set a preferred IP address"
time="2015-11-20T05:32:35.445369505Z" level=fatal msg="Error starting daemon: Error initializing network controller: Error creating default \"bridge\" network: failed to allocate gateway (<IP_ADDRESS>): No available addresses on this pool"
time="2015-11-20T05:32:35.562979814Z" level=info msg="API listen on /var/run/docker.sock"
time="2015-11-20T05:32:35.581794400Z" level=info msg="Firewalld running: false"
time="2015-11-20T05:32:35.672030288Z" level=info msg="Default bridge (docker0) is assigned with an IP address <IP_ADDRESS>/16. Daemon option --bip can be used to set a preferred IP address"
time="2015-11-20T05:32:35.677536533Z" level=fatal msg="Error starting daemon: Error initializing network controller: Error creating default \"bridge\" network: failed to allocate gateway (<IP_ADDRESS>): No available addresses on this pool"

docker version:
Client:
 Version:      1.9.0
 API version:  1.21
 Go version:   go1.4.2
 Git commit:   76d6bc9
 Built:        Tue Nov  3 17:43:42 UTC 2015
 OS/Arch:      linux/amd64
Cannot connect to the Docker daemon. Is the docker daemon running on this host?

docker info:
Containers: 0
Images: 0
Server Version: 1.9.0
Storage Driver: overlay
 Backing Filesystem: extfs
Execution Driver: native-0.2
Logging Driver: json-file
Kernel Version: 4.2.0-18-generic
Operating System: Ubuntu 14.04.3 LTS
CPUs: 1
Total Memory: 2.045 GiB
Name: vagrant
ID: 253M:O5XT:BJQK:AHRB:U5MI:OQZL:UUK4:YZAR:6XIH:XHV2:62QQ:3BET
WARNING: No swap limit support

Cannot connect to the Docker daemon. Is the docker daemon running on this host?
uname -a:
Linux default-ubuntu-1404 4.2.0-18-generic #22~14.04.1-Ubuntu SMP Fri Nov 6 22:20:11 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
Environment details (AWS, VirtualBox, physical, etc.):
I've ran into this issue on both AWS and Virtualbox with the latest ubuntu 14.04 images with the linux-virtual-lts-wily kernels installed (4.2.0)
How reproducible:
It seems to be about a 50% chance that the install will fail due to not being able to create the network bridge interface at start up
Steps to Reproduce:

Install the linux-virtual-lts-wily package onto an ubuntu 14.04 virtual box or AWS server
Install Docker 1.9.0, and enable the daemon with -s overlay
Sometimes it will fail, sometimes it will succeed

Actual Results:
Docker does not run
Expected Results:
Docker daemon should be running
Additional info:
I dont get this error if I use the linux-virtual-lts-vivid kernel (3.19) instead.

@Chili-Man this seems like a dupe of https://github.com/docker/docker/issues/17939. Can you pls make sure if there are multiple docker daemons running (either natively in the host or via dind using the same root directory as indicated in https://github.com/docker/docker/issues/17939).

@mavenugo  At first I thought that the issue was that there were multiple docker daemons running, but that is not that case. I've checked all the processes running on the host machine, and there was no docker daemon running at all.

@Chili-Man do you know why the log indicates the daemon is launched multiple times within the same second (2015-11-20T05:32:35) as indicated by the logs ?
Also, it is interesting to see this is specific to kernel v4.2.

yeah its within the same second because docker fails fast and upstart attempts a couple of times to restart it after it fails to start; I also manually tried starting the docker daemon after upstart gave up on trying with:
sudo docker daemon -s overlay

but it still produced the same error.  I made sure that no other docker daemon was running when I issued the above command.
It is strange that I haven’t been able to reproduce that issue with the 3.19 kernel, only on the 4.2.0 kernel.

@Chili-Man are you still having this issue? 1.9.1 was released recently; wondering if that release solved the issue for you, or if it's still unresolved.

I haven't had a chance to try it out with 1.9.1, I'll try it over this weekend and update back here when I do.

@Chili-Man thanks! Not sure if there's anything changed in 1.9.1 for this particular case, but there were quite some changes, so interested to hear if it's still an issue

I'm having the same issue with 1.9.1.  It's intermittent across my organization.  I've put some information below along the lines of Chili-Man's supplied information.
Linux 3.19.0-33-generic #38~14.04.1-Ubuntu SMP Fri Nov 6 18:17:28 UTC 2015 x86_64         x86_64 x86_64 GNU/Linux
$ docker version
Client:
 Version:      1.9.1
 API version:  1.21
 Go version:   go1.4.3
 Git commit:   a34a1d5
 Built:        Fri Nov 20 17:56:04 UTC 2015
 OS/Arch:      linux/amd64
Cannot connect to the Docker daemon. Is the docker daemon running on this host?

time="2015-12-01T17:30:05.109681982Z" level=debug msg="vagrant group found. gid: 1000"
time="2015-12-01T17:30:05.109774478Z" level=debug msg="Server created for HTTP on unix (/var/run/docker.sock)"
time="2015-12-01T17:30:05.110093715Z" level=debug msg="[graphdriver] trying provided driver \"btrfs\""
time="2015-12-01T17:30:05.112235021Z" level=debug msg="Using graph driver btrfs"
time="2015-12-01T17:30:05.112264108Z" level=debug msg="Using default logging driver json-file"
time="2015-12-01T17:30:05.112334572Z" level=debug msg="Creating images graph"
time="2015-12-01T17:30:05.113769728Z" level=debug msg="Restored 12 elements"
time="2015-12-01T17:30:05.113899603Z" level=debug msg="Creating repository list"
time="2015-12-01T17:30:05.113971500Z" level=debug msg="Option DefaultDriver: bridge"
time="2015-12-01T17:30:05.114014208Z" level=debug msg="Option DefaultNetwork: bridge"
time="2015-12-01T17:30:05.115306982Z" level=info msg="API listen on /var/run/docker.sock"
time="2015-12-01T17:30:05.118348751Z" level=info msg="Firewalld running: false"
time="2015-12-01T17:30:05.119903980Z" level=debug msg="/sbin/iptables, [--wait -t nat -D PREROUTING -m addrtype --dst-type LOCAL -j DOCKER]"
time="2015-12-01T17:30:05.120908447Z" level=debug msg="/sbin/iptables, [--wait -t nat -D OUTPUT -m addrtype --dst-type LOCAL ! --dst <IP_ADDRESS>/8 -j DOCKER]"
time="2015-12-01T17:30:05.121839720Z" level=debug msg="/sbin/iptables, [--wait -t nat -D OUTPUT -m addrtype --dst-type LOCAL -j DOCKER]"
time="2015-12-01T17:30:05.122916651Z" level=debug msg="/sbin/iptables, [--wait -t nat -D PREROUTING]"
time="2015-12-01T17:30:05.124121042Z" level=debug msg="/sbin/iptables, [--wait -t nat -D OUTPUT]"
time="2015-12-01T17:30:05.125459750Z" level=debug msg="/sbin/iptables, [--wait -t nat -F DOCKER]"
time="2015-12-01T17:30:05.126623895Z" level=debug msg="/sbin/iptables, [--wait -t nat -X DOCKER]"
time="2015-12-01T17:30:05.128540151Z" level=debug msg="/sbin/iptables, [--wait -t nat -n -L DOCKER]"
time="2015-12-01T17:30:05.129601103Z" level=debug msg="/sbin/iptables, [--wait -t nat -N DOCKER]"
time="2015-12-01T17:30:05.130786984Z" level=debug msg="/sbin/iptables, [--wait -t filter -n -L DOCKER]"
time="2015-12-01T17:30:05.132208778Z" level=debug msg="Registering ipam provider: default"
time="2015-12-01T17:30:05.132674076Z" level=warning msg="Could not get list of networks during endpoint cleanup: could not find endpoint count key docker/network/v1.0/endpoint_count/c13b96014f7f75ddc5e7aa856acafbadcaeb585fd0e9b0c5b598cc41c67f3367/ for network bridge while listing: Key not found in store"
time="2015-12-01T17:30:05.133080964Z" level=error msg="could not find endpoint count key docker/network/v1.0/endpoint_count/c13b96014f7f75ddc5e7aa856acafbadcaeb585fd0e9b0c5b598cc41c67f3367/ for network bridge while listing: Key not found in store"
time="2015-12-01T17:30:05.133284564Z" level=debug msg="Allocating IPv4 pools for network bridge (21cccc31f30fb5767a9011101dfac808fdc32b55304eb40543a496390bbbae13)"
time="2015-12-01T17:30:05.133331905Z" level=debug msg="RequestPool(LocalDefault, <IP_ADDRESS>/24, , map[], false)"
time="2015-12-01T17:30:05.136452128Z" level=debug msg="RequestAddress(LocalDefault/<IP_ADDRESS>/24, <IP_ADDRESS>, map[])"
time="2015-12-01T17:30:05.136523345Z" level=debug msg="Retrieving bitmask (LocalDefault/<IP_ADDRESS>/24, <IP_ADDRESS>/24)"
time="2015-12-01T17:30:05.136669772Z" level=debug msg="ReleasePool(LocalDefault/<IP_ADDRESS>/24)"
time="2015-12-01T17:30:05.152949577Z" level=debug msg="Cleaning up old shm/mqueue mounts: start."
time="2015-12-01T17:30:05.153170368Z" level=fatal msg="Error starting daemon: Error initializing network controller: Error creating default \"bridge\" network: failed to allocate gateway (<IP_ADDRESS>): No available addresses on this pool"

I am also experiencing this issue
Client:
Version:      1.9.1
API version:  1.21
Go version:   go1.4.2
Git commit:   a34a1d5
Built:        Fri Nov 20 13:12:04 UTC 2015
OS/Arch:      linux/amd64
INFO[0000] API listen on /var/run/docker.sock
INFO[0000] [graphdriver] using prior storage driver "overlay"
INFO[0000] Firewalld running: false
INFO[0000] Default bridge (docker0) is assigned with an IP address <IP_ADDRESS>/16. Daemon option --bip can be used to set a preferred IP address
FATA[0000] Error starting daemon: Error initializing network controller: Error creating default "bridge" network: failed to allocate gateway (<IP_ADDRESS>): No available addresses on this pool

ping @aboch

Most likely something is messing the /var/lib/docker/network/files/local-kv.db files content.
@mavenugo https://github.com/docker/libnetwork/pull/687 would help give some clarity on where the failure is, as I have said https://github.com/docker/docker/issues/17939#issuecomment-156168542

@Chili-Man @dvanbuskirk @sheldonkwok
When you experience the issue, can you please copy your
/var/lib/docker/network/files/local-kv.db in some place where I can download it.
I want to take a look at it.
A possible work-around, please check, could be delete that file before starting the daemon.

Deleting the file worked... Thanks!
Where can I email it?

@sheldonkwok Thanks for confirming.
To share the file, I think dropbox or any similar service would do it.

I have it on s3. There's nothing sensitive in it right? I glanced through it and it looked fine

Yeah, nothing sensitive in it. Mostly Network, Endpoint and Sandbox ids and their configurations.
 I will contact you via email for that.
Thanks.

Sure<EMAIL_ADDRESS>

Thanks @sheldonkwok for sending the file, it was very helpful.
In your case the issue was because the local store file had some inconsistent states, due to a sequence of ungraceful daemon shutdown.
We were able to reproduce and end up our local store file in the same state.
https://github.com/docker/libnetwork/pull/794 was pushed to restrict the chances of ending in such inconsistent file state.
Next libnetwork vendoring will bring it to docker/docker.

Great thanks for the quick response and the temporary solution on my end

I have this problem intermittently as well.

Now that  docker/libnetwork#687 is merged on master, at least for some cases, the no "No available addresses on this pool" error would now look more like "internal failure while setting the bit: boltdb bucket doesn't exist " (I just hit this master).
This means the local-kv.db file got somehow overwritten probably by another daemon instance.
A way to say you are hitting this issue is to check the o/p of
strings /var/lib/docker/network/files/local-kv.db, it will be empty.

@aboch, I just hit this issue when upgrading our 1.9.0 machines to 1.9.1 on Ubuntu 14.04.
"Fix" was to delete the /var/lib/docker/network/files/local-kv.db file.
If you guys need another local-kv.db file to look at, I can send it to you.

Had same problem with ubuntu 15.04 and docker version 1.9.1
deleting local-kv.db fixed it

Deleting the file solved it for me too with 14.04 and docker 1.9.1

Deleting files was a workaround on docker 1.9.1 for me as well. Major issue as I cannot count on the system to automatically recover after a reboot.  Scripting the automatic deletion of the file on reboot for now.

Server Version: 1.9.1
Storage Driver: aufs
Root Dir: /var/lib/docker/aufs
Backing Filesystem: extfs
Dirs: 36
Dirperm1 Supported: true
Execution Driver: native-0.2
Logging Driver: json-file
Kernel Version: 3.16.0-4-amd64
Operating System: Debian GNU/Linux 8 (jessie)
CPUs: 1

Deleting the file works for me, but it is also a serious issue as I can't trust on new systems coming up correctly.  Hopefully this gets addressed at some point.

I also have this problem with Docker 1.9.1, CentOS 7. Deleting the networking files fixes it for me: rm -rf /var/lib/docker/network/files/*

@brianbianco I agree with you. Removing the local db file is a just a workaround and not a viable solution.
To make it clear, the root cause is fixed in 1.10. With a clean (no local-kv.db file) boot of docker 1.10 issue will no longer happen.
FYI, I am working to a change with which docker will automatically fix the corrupted db and leave the rest of the data unaltered. This way a docker upgrade from 1.9.1 to 1.10 can be done without user touching internal files.

@aboch Wow.  Thanks very much.  Look forward to it.

Hello.
I had the same symptoms.
removing local-kv.db file did not help.
finally found a workaround:
modprobe -r br_netfilter
that's the name of the bridge module on my system that I had to unload before starting docker daemon.
The latter reloads the module upon startup.
for me the problem is solved

Hi, I have docker 1.10.1 running on 4.4.2. I still have problem mentioned  above. Non of suggested steps helped. In my log is:
time="2016-02-18T19:35:38.071941209+01:00" level=info msg="[graphdriver] using prior storage driver "overlay""
time="2016-02-18T19:35:38.072402194+01:00" level=info msg="Graph migration to content-addressability took 0.00 seconds"
time="2016-02-18T19:35:38.077121935+01:00" level=info msg="Firewalld running: false"
time="2016-02-18T19:35:38.123266732+01:00" level=info msg="Default bridge (docker0) is assigned with an IP address <IP_ADDRESS>/16. Daemon option --bip can be used to set a preferred IP address"
time="2016-02-18T19:35:38.163126043+01:00" level=fatal msg="Error starting daemon: Error initializing network controller: Error creating default "bridge" network: Failed to program NAT chain: Failed to inject docker in PREROUTING chain: iptables failed: iptables --wait -t nat -A PREROUTING -m addrtype --dst-type LOCAL -j DOCKER: iptables: No chain/target/match by that name.\n (exit status 1)"
Any hint is appreciated. thanks Dodo

@dodiak
The problem you are facing is not the same for which this issue was opened, whic was time="2015-11-20T05:32:35.677536533Z" level=fatal msg="Error starting daemon: Error initializing network controller: Error creating default \"bridge\" network: failed to allocate gateway (<IP_ADDRESS>): No available addresses on this pool"

I confirm that this bug went away with upgrade to docker 1.10.0.

I have this bug too in 1.10.x

Maybe you just have a custom kernel with not all needed option on. As I had. Look at: https://github.com/docker/docker/issues/20489

I'm using Ubuntu 15.10 with offical kernel in main repos. This only happen when I upgrade to docker 1.10.x.. Older version 1.9.x still ok

Same Problem here on 4.4.1-2-ARCH and Docker version 1.10.2, build c3959b1

I had this issue on Centos 7 host.
I figured out that firewalld and docker don't play well nicely together.
If docker is started after firewalld, we get this error.
Solution was to restart docker after firewalld.
and then run docker
here is a sample output
case 1: Docker already running, then firewalld staretd
[ali@docker-host ~]# docker run -d -p 80:80  nginx
24363b48c4acc63ea8cf43b82ee0827e5ac020606a1da478210383de6badf05b
docker: Error response from daemon: failed to create endpoint admiring_carson on network bridge: COMMAND_FAILED: '/sbin/iptables -w2 -t nat -A DOCKER -p tcp -d 0/0 --dport 80 -j DNAT --to-destination <IP_ADDRESS>:80 ! -i docker0' failed: iptables: No chain/target/match by that name..

case 2. docker running, firewalld started , docker restarted
[ali@docker-host ~]# systemctl restart docker
[ali@docker-host ~]# docker run -d -p 80:80  nginx
3d64557729d78d503ecaf2baa70e0a7a7136153f82236d449d7f8386552bb563
[ali@docker-host ~]# docker ps
CONTAINER ID        IMAGE               COMMAND                  CREATED             STATUS              PORTS                         NAMES
3d64557729d7        nginx               "nginx -g 'daemon off"   13 seconds ago      Up 10 seconds       <IP_ADDRESS>:80->80/tcp, 443/tcp   modest_dubinsky
[ali@docker-host ~]#

Hitting the same issue here:
root@master-ubuntu-1404:~# docker --version
Docker version 1.10.3, build 20f81dd

root@master-ubuntu-1404:~# tail -f /var/log/upstart/docker.log
INFO[0000] Graph migration to content-addressability took 0.00 seconds
INFO[0000] Firewalld running: false
INFO[0000] Default bridge (docker0) is assigned with an IP address <IP_ADDRESS>/16. Daemon option --bip can be used to set a preferred IP address
FATA[0000] Error starting daemon: Error initializing network controller: Error creating default "bridge" network: failed to allocate gateway (<IP_ADDRESS>): Address already in use

root@master-ubuntu-1404:~# ifconfig
docker0   Link encap:Ethernet  HWaddr 02:42:67:f1:da:1f
          inet addr:<IP_ADDRESS>  Bcast:<IP_ADDRESS>  Mask:<IP_ADDRESS>
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

eth0      Link encap:Ethernet  HWaddr 08:00:27:98:31:17
          inet addr:<IP_ADDRESS>  Bcast:<IP_ADDRESS>  Mask:<IP_ADDRESS>
          inet6 addr: fe80::a00:27ff:fe98:3117/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:588917 errors:0 dropped:0 overruns:0 frame:0
          TX packets:299834 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:560916355 (560.9 MB)  TX bytes:19426435 (19.4 MB)

eth1      Link encap:Ethernet  HWaddr 08:00:27:1a:3d:68
          inet addr:<IP_ADDRESS>  Bcast:<IP_ADDRESS>  Mask:<IP_ADDRESS>
          inet6 addr: fe80::a00:27ff:fe1a:3d68/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:32 errors:0 dropped:0 overruns:0 frame:0
          TX packets:42 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:8074 (8.0 KB)  TX bytes:7905 (7.9 KB)

Deleting the files not working.

@scalp42 I see there's some more changes made for the 1.11 release; https://github.com/docker/docker/issues/20312, not sure if it's related to your case, but worth checking

Docker on production system (ubuntu 14.04) not working anymore :-(
docker daemon
INFO[0000] [graphdriver] using prior storage driver "aufs"
INFO[0000] Graph migration to content-addressability took 0.01 seconds
INFO[0000] Firewalld running: false
FATA[0000] Error starting daemon: Error initializing network controller: Error creating default "bridge" network: failed to parse pool request for address space "LocalDefault" pool "" subpool "": could not find an available predefined network
Tried to delete the files. Did not work. manual start throws the error above. Any ideas or workarounds out there? Can i downgrade to a specific version and how?
Docker version 1.10.3, build 20f81dd
ii  docker-engine                       1.10.3-0~trusty                  amd64        Docker: the open-source application container engine

@DominicBoettger
This is not the same issue this PR was opened for.
Regarding your issue, can you confirm you deleted the file /var/lib/docker/network/files/local-kv.db, before starting the daemon.

Yes, i can confirm this!

@DominicBoettger
Please post the o/p of ip route

@DominicBoettger The reason I am asking for the routes is because I think you are hitting this issue https://github.com/docker/libnetwork/issues/779

I was experiencing this issue, but @DominicBoettger's tip to set --bip did the trick for me. I noticed the problem with a VPN connection before docker started, so docker/libnetwork#779 is my real problem.

Hi,
I have the issue of docker service failing:
May 06 07:37:44 node-8cdcd4a9c0b4 dockerd[12413]: time="2016-05-06T07:37:44.352994589Z" level=fatal msg="Error starting daemon: Error initializing network controller: Error creating default "bridge" network: failed to allocate gateway (<IP_ADDRESS>): No available addresses on this pool"
My docker info details:
Client:
Version:      1.9.1
API version:  1.21
Go version:   go1.4.3
Git commit:   9894698
Built:
OS/Arch:      linux/amd64
An error occurred trying to connect: Get http:///var/run/docker.sock/v1.21/version: read unix /var/run/docker.sock: connection reset by peer
Deleting /var/lib/docker/network/files/local-kv.db file worked for me and docker service is in active state.
I guess I need to upgrade to my docker to 1.10 to fix this issue.

I am too running into this problem on docker 1.11.1 with docker-compose 1.7.1.
Deleting /var/lib/docker/network/files/local-kv.db leaves my docker instance in an unusable state, because already created containers now give errors and newly created containers don't have a proper networks setting.
So long and thanks for all the fish... -.-

I am also running into this issue with docker 1.11.1 on raspberry pi. The issue seems to arise quite rarely when power is cut to the pi. (Ungraceful shutdown) Then deleting /var/lib/docker/network/* will fix the issue until it comes up again.

Likewise running docker 1.11.1 on raspberry pi. I am unable to build a container, having tried many of the options on this thread.

Same error on MacOs Version 1.12.1-rc1-beta23 (build: 11375)
time="2016-08-23T21:09:06.368055633Z" level=debug msg="Revoking external connectivity on endpoint my_docker_image (ac7becabec56e68b949038d740b6668121a3c09e75d03379c128ccb12826e5c9)"
time="2016-08-23T21:09:06.371134549Z" level=warning msg="driver failed revoking external connectivity on endpoint my_docker_image (ac7becabec56e68b949038d740b6668121a3c09e75d03379c128ccb12826e5c9): network not found: 05807ea9c6a73c24112f92b6795d18994c85ca90a885cdaa248046c590e7127b"
time="2016-08-23T21:09:06.465919398Z" level=debug msg="libcontainerd: received containerd event: &types.Event{Type:\"exit\", Id:\"e3d97a98ffb0a6571c855082d80b0b474925a64a43b6773558f7104d15437911\", Status:0x89, Pid:\"init\", Timestamp:(*timestamp.Timestamp)(0xc8219b34d0)}"
time="2016-08-23T21:09:06.467110450Z" level=debug msg="Revoking external connectivity on endpoint my_docker_image (0f10417e3f4dcce2dd5e8264ee2e6ec2606874b0600f992315e205c21ee13fbf)"
time="2016-08-23T21:09:06.467798571Z" level=warning msg="driver failed revoking external connectivity on endpoint my_docker_image (0f10417e3f4dcce2dd5e8264ee2e6ec2606874b0600f992315e205c21ee13fbf): network not found: 05807ea9c6a73c24112f92b6795d18994c85ca90a885cdaa248046c590e7127b"

I couldn't try deleting local-kv.db b/c I don't know where that file is on MacOS
My only "solution" was reset to factory defaults :S

Deleteing /var/lib/docker/network/files/local-kv.db worked for me

I was experiencing the same problem. Removing /var/lib/docker/network/files/local-kv.db didn't help. Turn out that I had already created a network with that IP range, so docker network rm <my-network> solved it for me.

Removing  /var/lib/docker/network/files/local-kv.db as root did not work for me for those errors:

ERROR: for jhipster-registry  Cannot start service jhipster-registry: service endpoint with name dev_jhipster-registry already exists

ERROR: for gateway-app  Cannot start service gateway-app: failed to update store for object type *libnetwork.endpointCnt: Key not found in store
ERROR: for onboarding-app  Cannot start service onboarding-app: failed to update store for object type *libnetwork.endpointCnt: Key not found in store
ERROR: for hb-rabbitmq  Cannot start service hb-rabbitmq: service endpoint with name dev_hb-rabbitmq_1 already exists
ERROR: for hb-mongodb  Cannot start service hb-mongodb: failed to update store for object type *libnetwork.endpointCnt: Key not found in

Just ran into the same issue with docker 1.11.2
sudo systemctl status docker gave me:
`docker.service - Docker Application Container Engine
Loaded: loaded (/usr/lib/systemd/system/docker.service; disabled; vendor preset: disabled)
Active: failed (Result: start-limit) since Wed 2016-10-26 11:52:30 UTC; 6s ago
Docs: https://docs.docker.com
Process: 22946 ExecStart=/usr/bin/docker daemon -s overlay --registry-mirror=https://mirror.gcr.io --host=fd:// $DOCKER_OPTS (code=exited, status=1/FAILURE)
Process: 22940 ExecStartPre=/bin/sh -x -c if [ ! -s /var/lib/docker/repositories-overlay ]; then rm -f /var/lib/docker/repositories-overlay; fi (code=exited, status=0/SUCCESS)
Main PID: 22946 (code=exited, status=1/FAILURE)
Memory: 16.5M
CPU: 142ms
CGroup: /system.slice/docker.service
Oct 26 11:52:29 gke-tk-uat1-uat-pool-13756537-7eu5 sh[22940]: + [ ! -s /var/lib/docker/repositories-overlay ]
Oct 26 11:52:29 gke-tk-uat1-uat-pool-13756537-7eu5 sh[22940]: + rm -f /var/lib/docker/repositories-overlay
Oct 26 11:52:30 gke-tk-uat1-uat-pool-13756537-7eu5 docker[22946]: time="2016-10-26T11:52:30.215930217Z" level=fatal msg="Error starting daemon: Error initializing network controller: Error creating default "bridge" network: failed to allocate gatewa...ss already in use"`
deleting /var/lib/docker/network/files/local-kv.db fixed the problem and allowed me to start up docker successfully.
This is quite a serious issue, it's taking down production machines on our Google Container Engine.

Removing /var/lib/docker/network/files/local-kv.db allowed me to start docker again.

Encountered same problem with docker 1.9.1 and CentOS 7 with Linux kernal 3.18.27

+1, deleting /var/lib/docker/network/files/local-kv.db solved this for me.

Had this problem too; Ubuntu 14.04 and 1.12.6, exactly as described by the previous comment.
Removing /var/lib/docker/network/files/local-kv.db allowed me to start docker containers again.

Same with Ubuntu 16.04.1 and Docker 1.11.2 -> Deleting local-kv.db safed the day...

This fixed it for me:
head -n -1 /etc/resolv.conf | sudo tee /etc/resolv.conf
(https://sdujancourt.me/2017/02/07/dockerd-error-initializing-network-controller-list-bridge-addresses-failed-no-available-network/)

docker 1.13.0 cannot start if I have an IPv6 nameserver in /etc/resolv.conf !?!

All the solution tried, still face this error:
Error starting daemon: Error initializing network controller: list bridge addresses failed: no available network

Yes, I found programster's conclusion is right. If the VPN is working, the Docker installation process will fail. After disabling the VPN, it works. So it means when the VPN is working, Docker's installation logic couldn't correctly handle the network status.

Remove all ipv6 nameservers from /etc/resolv.conf!
clockzhong<EMAIL_ADDRESS>ezt írta (időpont: 2017. márc. 3., P
5:43):

All the solution tried, still face this error:
Error starting daemon: Error initializing network controller: list bridge
addresses failed: no available network
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/docker/docker/issues/18113#issuecomment-283864029,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAPoSvKCeIncEpGKSLQbrTx58I62YOoOks5rh5pigaJpZM4GmJnl
.

What I've found is that if there's a n ipv6 nameserver in /etc/resolv.conf,
then docker won't start.
This can be a result of a started VPN, though.
clockzhong<EMAIL_ADDRESS>ezt írta (időpont: 2017. márc. 3., P
5:46):

Yes, I found programster's conclusion is right. If the VPN is working, the
Docker installation process will fail. After disabling the VPN, it works.
So it means when the VPN is working, Docker's installation logic couldn't
correctly handle the network status.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/docker/docker/issues/18113#issuecomment-283864412,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAPoSoJwxPVPCW44CMjy5E4tIVqdVG9rks5rh5sxgaJpZM4GmJnl
.

Tgulacsi, my failure doesn't relate to the /etc/resolv.conf. Even this file doesn't have the IPV6 nameserver in my envriroment, it still fails when my VPN is enabling. It seems this is a multiple-root-causes bug in Docker's installation process.

What I've found is that if there's a n ipv6 nameserver in /etc/resolv.conf,
then docker won't start

@tgulacsi If the nameserver contains a zone id (i.e., the %ens33 in nameserver fe80::e23f:49ff:fe09:fd38%ens33), you're probably running into https://github.com/docker/docker/issues/30295#issuecomment-275315635, which was fixed in docker 1.13.1 and up

I experienced the same problem with Docker 17.06, Ubuntu 16 (Linux kernel 4.4.0), on a Docker swarm worker node. Removing /var/lib/docker/network/files/local-kv.db and restarting the Docker daemon fixed the problem. Yay!
me@myhost:~$ sudo docker version
Client:
 Version:      17.06.2-ce
 API version:  1.30
 Go version:   go1.8.3
 Git commit:   cec0b72
 Built:        Tue Sep  5 20:00:17 2017
 OS/Arch:      linux/amd64

Server:
 Version:      17.06.2-ce
 API version:  1.30 (minimum version 1.12)
 Go version:   go1.8.3
 Git commit:   cec0b72
 Built:        Tue Sep  5 19:59:11 2017
 OS/Arch:      linux/amd64
 Experimental: false
me@myhost:~$ uname -a
Linux docker.myhost.com 4.4.0-93-generic #116-Ubuntu SMP Fri Aug 11 21:17:51 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

This is happening with a worker node. The container fails to start with this inspect log:
me@myhost:~$ sudo docker inspect xqdw4ne0z4gp
[
    {
        "ID": "xqdw4ne0z4gpakhdpz5ybfo07",
        "Version": {
            "Index": 10537402
        },
        "CreatedAt": "2017-11-01T21:47:45.031782214Z",
        "UpdatedAt": "2017-11-01T21:48:52.028210273Z",
        "Labels": {},
        "Spec": {
            "ContainerSpec": {
                "Image": "my-amazon-image-path",
                "Labels": {
                    "com.docker.stack.namespace": "my-stack"
                },
                "Command": [
                    "pypy",
                    "/app/main.py"
                ],
                "Env": [
                    "log_level=INFO"
                ],
                "Privileges": {
                    "CredentialSpec": null,
                    "SELinuxContext": null
                },
                "Hosts": [
                    "<IP_ADDRESS> myhost1",
                    "<IP_ADDRESS> myhost2"
                ]
            },
            "Resources": {
                "Limits": {
                    "MemoryBytes":<PHONE_NUMBER>
                }
            },
            "RestartPolicy": {
                "Condition": "any",
                "Delay":<PHONE_NUMBER>0,
                "MaxAttempts": 0
            },
            "Placement": {
                "Platforms": [
                    {
                        "Architecture": "amd64",
                        "OS": "linux"
                    }
                ]
            },
            "Networks": [
                {
                    "Target": "c0jvj7s8yaiu5soc1sv1hsq04",
                    "Aliases": [
                        "my-alias"
                    ]
                }
            ],
            "LogDriver": {
                "Name": "awslogs",
                "Options": {
                    "awslogs-group": "my-group",
                    "awslogs-region": "us-west-1",
                    "awslogs-stream": "my-stream"
                }
            },
            "ForceUpdate": 0
        },
        "ServiceID": "rmifpooavorrgxxr4oh7wb8nq",
        "Slot": 1,
        "NodeID": "ubkmi3ua2ri97qfq7l8thh2f7",
        "Status": {
            "Timestamp": "2017-11-01T21:48:51.33548237Z",
            "State": "failed",
            "Message": "starting",
            "Err": "starting container failed: failed to get network during CreateEndpoint: network c0jvj7s8yaiu5soc1sv1hsq04 not found",
            "ContainerStatus": {
                "ContainerID": "e9da66fdf0094003932fea61eb9b1821c6a2a831cf31d56b7b449508797b814e",
                "ExitCode": 128
            },
            "PortStatus": {}
        },
        "DesiredState": "shutdown",
        "NetworksAttachments": [
            {
                "Network": {
                    "ID": "c0jvj7s8yaiu5soc1sv1hsq04",
                    "Version": {
                        "Index": 10252930
                    },
                    "CreatedAt": "2017-09-24T23:31:48.64028447Z",
                    "UpdatedAt": "2017-11-01T01:15:49.580929009Z",
                    "Spec": {
                        "Name": "cjj-stack_default",
                        "Labels": {
                            "com.docker.stack.namespace": "my-stack"
                        },
                        "DriverConfiguration": {
                            "Name": "overlay"
                        },
                        "Scope": "swarm"
                    },
                    "DriverState": {
                        "Name": "overlay",
                        "Options": {
                            "com.docker.network.driver.overlay.vxlanid_list": "4097"
                        }
                    },
                    "IPAMOptions": {
                        "Driver": {
                            "Name": "default"
                        },
                        "Configs": [
                            {
                                "Subnet": "<IP_ADDRESS>/24",
                                "Gateway": "<IP_ADDRESS>"
                            }
                        ]
                    }
                },
                "Addresses": [
                    "<IP_ADDRESS>/24"
                ]
            }
        ]
    }
]

@osman-masood please open a new issue with details; the original issue is from 2015, at which time the Swarm-managed overlay networks didn't even exist, so your issue may well be unrelated (but similar outcome)

On MacOS, Restarting the docker daemon did it for me.

sudo rm -rf /var/lib/docker -- destroy all Docker internal files (sometimes Docker gets into an invalid state and, unfortunately, this is the only way to correct it)

sudo systemctl restart docker - restart the Docker system service (turn it off and turn it back on

will fix it

As there are several tickets written by people claming that IPv6 is broken, here is the solution how to configure it corretly. Someone should change the documentation accordingly.
Docker IPv6 is working perfectly, it's just the documentation that doesn't tell people what to do in order to set it up correctly.
Docker will not do SLAAC (Stateless Address Autoconfiguration), nor will it use DHCPv6. As it also won't do NATv6 (thank god!), you will have to assign ipv6 prefixes to your networks manually. The default bridge network has to be assigned a network, you can do this by adding the following to daemon.json:
{
"ipv6": true,
"fixed-cidr-v6": "2001:db8::/64",
}

For any other network you might have, you can decide wether or not it will be ipv6 capable. To create an IPv6 capable network, do the following:
docker network create --ipv6 --subnet "2001:db8:1::/64" testnet
Also remember, that this is not NATv6 (thank god!). Therefor you will have to have a route from your router to your docker host!

@hr1232 if you know which page(s) of the documentation contain the incorrect information, could you perhaps open a ticket in the documentation repository (or, even better; if you're interested in contributing, open a pull request 😅). If the incorrect information is in the daemon reference page, or one of the CLI reference pages, the markdown file for that file can be found in the cli repository; https://github.com/docker/cli/blob/master/docs/reference/commandline/dockerd.md, other pages are built from the documentation repository; https://github.com/docker/docker.github.io/


[BUG] Can't select .exes to add to liabry on Steam Deck

Describe the bug
The selector for the game on Steam Deck is not recognising .exe types of files, so I can't add them into the launcher
To Reproduce
Steps to reproduce the behavior:

Add any game to your libary (not installed from Hydra)
Click on it and click on play
Try to go to game's folder and apply the .exe file to it
Can't apply

Expected behavior
Reaching the folder and being able to select .exe file
Screenshots

Additional context

OS: Steam Deck
Hydra Version: 1.1.0

It seems that there is no support for non-windows OS's files here.
  const selectGameExecutable = async () => {
    return window.electron
      .showOpenDialog({
        properties: ["openFile"],
        filters: [
          {
            name: "Game executable",
            extensions: window.electron.platform === "win32" ? ["exe"] : [],
          },
        ],
      })
      .then(({ filePaths }) => {
        if (filePaths && filePaths.length > 0) {
          return filePaths[0];
        }

        return null;
      });
  };

This seems strongly related to #279 because we would need this to be able to run Proton/Wine games.

FYI, I was wrong. extensions: window.electron.platform === "win32" ? ["exe"] : [], means that any file will be accepeted. Hoewever, for some reason, it's not working properly.

See #232 to understand better why the expected behaviour is not happening

These should be fixed in the lastest version, if not. Feel free to reopen this issue


hub doesn't work with custom github

We have our company github server installed for internal use.
The server name is github..corp
I follow the documentation provided here: https://hub.github.com
I run the following commands:
$ git clone git@internal-git-repo-url
$ hub fork --remote-name=origin
$ git push origin feature
$ hub pull-request
and get the following error:
Aborted: could not find any git remote pointing to a GitHub repository
however, when i run git remote, I see:
$ git remote
origin
Is there a setting that I can do to enable hub to work on  my internal git server?
If it is an administrative task, I can ask the admin to do it- but I would need information regarding what to do- internet hasn't been kind so far. :(
Sahil Bawa

Same here:
$> tail -4 ~/.gitconfig
[user]
        name = aemonge
[hub]
        host = github.*******.corp
~/wsr/catalog (master)
$> hub clone aem-media
github.com username: ********
github.com password for ******* (never stored): ******
Error cloning repository: Unauthorized (HTTP 401)
Bad credentials
~/wsr/sgt-omnichannel-proyects/API_usa_global_api/catalog (master)

Same here:
$> tail -4 ~/.gitconfig
[user]
        name = aemonge
[hub]
        host = github.*******.corp
~/wsr/catalog (master)
$> hub clone aem-media
github.com username: ********
github.com password for ******* (never stored): ******
Error cloning repository: Unauthorized (HTTP 401)
Bad credentials

This isn't the same, this is an entirely different problem.  This probably means that your GitHub Enterprise instance is using OAuth or SAML or some other external authentication system.  If that's the case then you can't use passwords to authenticate (because GHE doesn't have access to the passwords to verify it).  You have to create a Personal Access Token and use that instead of the password.

Well......
I got confused since the out-put is asking for a githbub.com credentials, not my github.****.corp credentials.
But I'll try your solution and you know.
Thanks !

@aemonge hub clone will always try to clone from github.com by default, even if you've correctly configured another GHE host. This is because hub clone doesn't not know from which host do you intend to clone a repo, so it defaults to github.com.
Use GITHUB_HOST=github.***.corp hub clone to set another default.


Handling Severity of PVs

Discussed in https://github.com/sasaki77/archiverappliance-datasource/discussions/155

Originally posted by LowriJenkins August 23, 2023
Is there a way to make use of the severity of the PVs being used in this? The data retrieved from getData on the archiver itself does contain the severity of the PVs, and it would be helpful to be able to manipulate the data e.g. if the severity is invalid, returning null so that the graph does not display values when it was in an invalid state.
I have found a way to achieve the above, but it's very hacky, and relies on having another PV scan the severities in question and archiving that PV.
thanks for any help.

the plugin uses the getData.qw format instead of the getData.json format.  That's because getData.qw has waveform metadata and the millisecs time format. Those are convenient for the plugin. The getData.qw format doesn't have severity meta data. If we want to handle severity, the plugin should be migrated to use the getData.json format.
The source code for the getData.qw format says that please don't use this for integration purpose.
https://github.com/slacmshankar/epicsarchiverap/blob/9aeb9b536749805dccd5abc19a9709d6b505bcd2/src/main/org/epics/archiverappliance/retrieval/mimeresponses/QWResponse.java
When I have a chance to migrate to the getData.json format, I'll consider to handle the severity.

I would like to see this feature, too. It would be great to be able to add some kind of information to dashboards that informs the user about the validity of the data.

@greyghost509, @LowriJenkins
I have migrated the data retrieval format from getData.qw to getData.raw (#167). The plugin can now get the severity of the PV.
I'm considering to implementing this feature with the new function called fieldName. The fieldName function returns the values of the field that specified in fieldName.
The following screenshot shows an example of using the fieldName function. There are two queries in the example, A and B. The same PV is specified for both A and B.
The function is not applied to query A. Therefore the values of the PV are shown for query A. On the other hand, the fieldName function with SEVR argument is applied to query B. So, the values of SEVR field are shown for query B.
Does this function meet your requirement? Any comments are welcome.

I'm merging the fieldName function and will consider implementing the function that hides invalid data next time. The plugin can't return null for now, it needs more time to hide invalid data with null values.

I have implemented hideInvalid feature to return null if a severity of a data sample is invalid. The display on the Time series panel will look like this when there are null values.

This feature can be enabled/disabled in the data source settings for the default setting and the hideInvalid function for each query.
Data source settings

Query

Please note that this feature is only available if you are using the backend data retrieval and data is not string or array.
I hope this feature matches what you want to do.

This looks perfect

I closed the issue. Please reopen the issue or create a new issue if there is a problem.

v2.0.0 has been released with these features.


Emulator: "Sign in with Azure" sign in flow does not appear with File > Sign in

Windows build 4.0.0-preview-.39773
Attempting to sign with Azure with File > Sign in or the link on the Welcome page opens the intro modal screen (that tells you about signing in) but not the subsequent modals for actually signing in to Azure. However, signing in via adding a service from the services pane does open the sign in flow.
Repro steps for File > Sign in (or using the link the Welcome page):
(1) cleared cookies

(2) opened Emulator

(3) clicked on File >Sign in with Azure and the intro modal opened:

(4) Clicking the primary button in the intro modal closed the modal, but then nothing happened:

Repro step for signing in through the services pane:
(1) open a bot
(2) open the Bot Explorer pane, next to the Services group, click the + button to add a service:

(3) modal appears asking if you'd like to sign in to azure:

(4) sign in flow starts:

(Not sure why sign in failed, was looking in the Microsoft tenant? I was using a non-Microsoft Azure account.)

#913  fixes this as well here

fixed with #913


Underscore 1.8.3

I ONLY added the underscore.create(...) func. I am new to the open source world an dI want to try. I couldn't push a feature branch in your repository (permission denied for me). So I created a fork on my remote.
Thanks, Olli

NOTE: http://underscorejs.org/#create

Thank you for your contribution.
Can you please fix the failing Travis CI tests and update the PR!

Hello and thank you for your contribution!
Due to an excessively long queue of pull requests that have become stale, we are "declaring bankruptcy" and closing all PRs opened before May 1, 2016. If you'd still like to merge this code in, please open a new PR that has been merged and rebased with the master branch.
Going forward, we are committing to review or merge all PRs on a regular basis so this bankruptcy will not occur again. We apologize for the incovenience and hope you will continue to contribute to DefinitelyTyped in the future.
Thanks
The TypeScript and DefinitelyTyped teams


[BACKEND] Update LLVM version to https://github.com/llvm/llvm-project/commit/9ddfe62f5c11e3f65f444209f514029ded2d58b9

Closing this, we can start a fresh LLVM upgrade now that the problem is fixed.


This repository is rather dated, many dependencies are deprecated.

Care to instruct beginners on how to upgrade the repo?

nothing on the VS setup instructions is as the visual-code website establishes. It is so confusing for beginners.


Support for accented characters

Fixed Montreal crash by defining utf-8 encoding in the first line of the script

Good catch, this will allow the character to print correctly but still breaks colorama =/


Add WMC Token

In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:

[x] Filename in the lowercase format
[x] Image format: png
[x] Image size: 256 by 256 px

Added here https://github.com/TrustWallet/tokens/commit/98b8835db409147a65cf322070b466a36eee1f49
Also, you can use these graphics to say that your ERC20 token fully compatible with Trust Wallet (https://trustwalletapp.com/logo-assets). Tokens will show up automatically once the user receives them.
Feel free to share this on social media and tag Trust Wallet:

Twitter: @trustwalletapp

Facebook: @trustwalletapp


stickybits element width in IE

Hi
When position: fixed is applied to the sticky element (in IE) it doesn't preserve it's width see bellow:

Thanks!

@aitboudad thanks for the demo! Could you provide a quick Codepen example? I think/hope we can add a little css and make it all better 🙏

@yowainwright see https://codepen.io/anon/pen/BZgVrz

@aitboudad https://codepen.io/yowainwright/pen/BZgeWN
max-width: inherit;
width: 100%;

I think that is on the right path ...?
Could you hack at it a bit? 🙏

@yowainwright That's not fixing it (Tested on IE11, Edge 14 & 15).
Only way i've managed it was applying your fix + max-width set on parent.

@cyr-x awesome!
Unrelated to @cyr-x's comment—there are probably many ways to solve this issue. Keep 'em coming. 🙌

it doesn't solve my issue as in my app I use the grid system (parent doesn't have a specific width).
IMO the better approach is to set the width using js.

@aitboudad if you could post your solution here that would be awesome.
I DO think this issue is very valuable for Stickybits to have s people can reference their solutions.
Thanks for sharing!

just tested with another alternative lib stickyfill and  it appear that handle that issue by setting width to auto and add left + right to the sticky element see https://github.com/wilddeer/stickyfill/blob/master/src/stickyfill.js#L179-L183

@aitboudad thanks for sharing. Those styles can be added be added with css:
.js-is-sticky[style="postion: fixed"] {
  left: <left val>;
  top: <top val>;
  bottom: <bottom val>;
  width: <width val>;
}

The benefit of not assuming what an interface needs (aka not position: sticky polyfill 🙂 ) is that styles and javascript can be added to create the desired affect.
If the interface requires the sticky element to be positioned at the bottom or not directly at the top of the browser window (see readme examples) there are a few issues with a full polyfill approach:

The plugin file size is larger for a feature that should questionably just default to position: static for non-supported browsers (b/c position: sticky has growing support and a position: static is not broken—users probably wouldn't know or care).
Along with the plugin's larger file size, the interface is more locked into 1 approach for sticky elements however often the interface requires sticky elements directly not to be at the top of the browsers. To achieve that desired affect the developer has to write css or javascript to override the plugin defaults which means even more code!

make sense and I'm totally agree with all arguments, I'll try to find a better approach to my use-cases.
Anyway thanks for all!

Hi all! For IE when sticky element is position: fixed i used
width: 100%
max-width: ...px

Looks like workaround however anybody knows better solution?


Fix the dev console links

Coverage remained the same at 92.365% when pulling 0d6803fd1ec66d075d473f26780047a12ed23299 on mortonfox:patch-1 into 6f9838e7931899804ab4254cbb5d97dcad0f82f1 on google:master.

LGTM


Mark semVerLevelKey=2 for packages on NuGet.org that are already SemVer 2.0.0

These break old clients. Once the SemVerLevelKey migration has been run in production, we should perform a data fix on these packages.
SemVer 2.0.0 package versions

ID
Normalized Version
Value

prototest
1.2.0
1.2.0+git.unspecified

protobuild
16.1119.5842
16.1119.5842+git.unspecified

protobuild.testinstall
16.1120.60313
16.1120.60313+git.unspecified

semvera
1.0.0
1.0.0+metadata

astarpathfinder
1.0.0
1.0.0+git.unspecified

protobuild
16.1119.145207
16.1119.145207+git.unspecified

protogame
6.0.1
6.0.1+git.unspecified

protobuild
16.1117.224729
16.1117.224729+git.unspecified

ndesk.options.redpoint
0.2.1
0.2.1+git.unspecified

ffmpeg.nuget
1.0.0
1.0.0+git.unspecified

protogame
6.0.0
6.0.0+git.unspecified

protobuild
16.1119.13506
16.1119.13506+git.unspecified

prototest
1.1.0
1.1.0+git.unspecified

protoinject
1.0.0
1.0.0+git.unspecified

prototest
1.1.3
1.1.3+git.unspecified

semvernumeric
1.0.0
1.0.0+-

SemVer 2.0.0 version range minimums

ID
Normalized Version
Value

snowflake.framework
0.2.0-pre-alpha-build1038
0.2.0-pre-alpha.1038

snowflake.framework.utility
0.2.0-pre-alpha-build1038
0.2.0-pre-alpha.1038

snowflake.framework.services
0.2.0-pre-alpha-build1038
0.2.0-pre-alpha.1038

SemVer 2.0.0 version range maximums
(none)

These packages should also be reflowed once update feed2catalog, catalog2registration, catalog2dnx, and catalog2lucene have been deployed.

It looks like API push did not block SemVer 2.0.0 until: https://github.com/NuGet/NuGetGallery/commit/0b7007b8b08dc6f7b781be0e0438ce10d448d719
Which was deployed on March 1st, I think.

This requires the db schema change (part of deployment https://github.com/NuGet/NuGetGallery/issues/3718) to be in place first.


Add WSDM 2022

ACM International Conference on Web Search and Data Mining (WSDM, pronounced “wisdom”) is one of the premier conferences on web-inspired research involving search and data mining. The 15th ACM International WSDM Conference will take place in Phoenix, Arizona, 2/21 – 2/25, 2022.
H-index reference: link
WSDM 2022 webset: link

Thanks!


First entry of the SubstructLibrary module

What does this implement/fix? Explain your changes.
Adds a multithreaded substructure library implementation.
Features:

Multithreaded searches
Large libraries can easily be searched using cached molecules and pattern fingerprints.

Example:
slib = rdSubstructLibrary.SubstructLibrary()
for mol in mols:
  slib.AddMol(mol)

indices = slib.GetMatches(query)
for index in indices:
  slib.GetMol(index)

For large datasets, the CachedMolHolder or CachedSmilesMolHolder can be used in conjunction with a fingerprint filter:
molHolder = rdSubstructLibrary.CachedMolHolder()
fingerprints = rdSubstructLibrary.PatternHolder()
slib = rdSubstructLibrary.SubstructLibrary(molHolder, fingerprints)
for mol in mols:
  slib.AddMol(mol)
  ...

Any other comments?

@greglandrum I think I have your changes.
To-do

Add options testing (recursive/stereo)
Add trustedSmiles code and tests
add tests for raw binary

Anything else?

I'm going to take one more pass through this, but I think it's really close.

Give me a day, I'm adding docstrings and fixing up the Python API a bit to add functionality ( and trusted smiles support )

Brian Kelley

On Jul 18, 2017, at 11:51 AM, Greg Landrum<EMAIL_ADDRESS>wrote:
I'm going to take one more pass through this, but I think it's really close.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Looks good. Builds on Windows too.
I'm ready to merge unless you want to make additional changes.

I'm good!

Brian Kelley

On Jul 19, 2017, at 1:49 AM, Greg Landrum<EMAIL_ADDRESS>wrote:
Looks good. Builds on Windows too.
I'm ready to merge unless you want to make additional changes.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Then a'merging I will go. Thanks!


event: Add Key

This also renames event names from Key* to KeyboardKey*.
Updates #926
@beoran , please take a look.

Thank you for your reviewing!


Publishing while new (to Azure)

Describe the bug
When publishing to a newly minted Azure subscription, the user may run into scenarios that seem related to first-time user of various Azure services
Version
            Bot Framework Composer

            Version:  1.3.0
            Electron: 8.2.4
            Chrome: 80.0.3987.165
            NodeJS: 12.13.0
            V8: 8.0.426.27-electron.0

Browser

[ ] Electron distribution
[* ] Chrome
[ ] Safari
[ ] Firefox
[ ] Edge

OS

[ ] macOS
[ *] Windows
[ ] Ubuntu

To Reproduce
Steps to reproduce the behavior:

Create a new Azure subscription
[Never user it for anything else in the portal, save a Cognitive services resource for LUIS]
Go to 'Publish'
Create a new publish profile
Sign in
Attempt to publish

Expected behavior
Bot and associated resources get created in Azure
Screenshots
"The subscription is not registered to use namespace 'Microsoft.Web'"

Workaround:
Execute: az provider register --namespace Microsoft.Web in cloud shell
"The subscription is not registered to user namespace 'Microsoft.BotService"

Workaround:
Execute: az provider register --namespace Microsoft.BotService in cloud shell
"The subscription is not registered to user namespace 'Microsoft.DocumentDB"

Execute: az provider register --namespace Microsoft.DocumentDB in cloud shell
"The subscription is not registered to user namespace 'Microsoft.Insights"

Execute: az provider register --namespace Microsoft.Insights in cloud shell
"The subscription is not registered to user namespace 'Microsoft.Search"

Execute: az provider register --namespace Microsoft.Search in cloud shell
Additional context
Having run all the service registrations manually, the bot was successfully published.

@dmvtech Can you help the customer here?

hi @irwinwilliams I am attempting to reproduce this. Thank you for sharing, I'll let you know if I have any questions.

I was able to reproduce this.
Interestingly, after getting the failure in Composer, I tried creating a simple Web App Bot in the portal, and got the following:

I then created a basic Web App (not a bot) in the Azure portal. That was successful. Then I was able to finish/continue creating the Web App Bot in the portal.
After doing that, I re-ran the publish and then failed on DocumentDB and Search. After creating those in the portal (which obviously sets up the providers), then I could publish.
@cwhitten I can share more thoughts/findings with you and the team.

Let's look to address in R13.
Questions to understand, and we need to connect with ABS to understand:

Why are these registrations not happening at the outset?
Can we do this registration for users on their behalf without introducing unnecessary side-affects
Are the operations idempotent? Will we need to infer the need to do this registration? Do we have the heuristic to do the correct inference?

To be resolved with #7257