ExpressRoute - About FastPath - update reference link

#sign-off

@duongau Merged is complete. Please proceed. Thanks!


Improve EC2 metadata tests

The test coverage for EC2 metadata endpoints needs evaluating as it seems incomplete. This was identified when refactoring code in https://github.com/tinkerbell/hegel/pull/139

Addressed with the refactor in #156 and #157.


ManagedNameHelper.GetManagedMethodName returns managedMethodName with unexpected single quote escape characters

Expected:<TestClasses.IImplementation.ImplMethod>
Actual:<'TestClasses.IImplementation.ImplMethod'>.

FYI @Haplois

@Haplois I believe this is fixed through PR #3704 (see these tests https://github.com/microsoft/vstest/pull/3704/files#diff-59cd2a534d129b12a0f316a0f618a8b1d2ad513bc9bd92952404385fe90af109R453). Could you confirm?


Jade+BEM support

markup section now supports jade
BEM support included (kizu/bemto)
JADE markup section added to doc

Ok, got it, will digg into it later(

I have no idea, why this tests are failed:
index.html
  1) "before all" hook for "should include css from the all specified sources"
overview.html
  2) "before all" hook for "should include css from the all specified sources"

Could you provide test? I want to try it out and debug, but I can no idea what your generateJadeMarkup function is supposed to do.

The problem is that you are trying to process all kinds of markups as Jade. At the normal HTML it gives error like that:
Error: /Users/varya/WebDev/SC5/sc5-styleguide/lib:3
    1| include ./node_modules/bemto.jade/bemto.jade
    2|   <div class="sg action-footer">
  > 3|     <button class="sg button sg-primary">Primary action</button>
    4|     <button class="sg button sg-secondary">Secondary action</button>
    5|   </div>

To avoid this you should introduce an option, with which a users may declare that they want this Jade processor. Let's name is enableJade. So, when calling your function, you use
options.enableJade && generateJadeMarkup(styleguide);

Don't forget to describe this option in the README.
Also, the proposed code is not aligned with codestyle, this will not pass continuous integration unless you fix this. Run gulp jscs to see the errors. There are not very many, just some spaces missing.
Anyway, great job!

@varya thank you!
I will fix it soon and implement few more features)


Refactor Event wait() method for simplified code

This pull request refactors the wait() method of the Event struct to simplify the code and improve readability.
In the original implementation, the method used a loop to check for receiver updates by cloning the receiver and invoking receiver.changed().await.unwrap() within the loop. However, this can be simplified by directly invoking self.receiver.clone().changed().await.unwrap() in a single line.
The refactored code eliminates the need for the loop and makes the intention of waiting for receiver changes clearer. It reduces unnecessary code complexity while maintaining the functionality of the wait() method.

Are you aware that those changes are only for a test, not for the

Are you aware that those changes are only for a test, not for the actual library?

Certainly, only integration test need Event struct.

Is there something wrong with the existing implementation? Especially as your rework now isn't compatible with multiple wait calls any more ...

The failing CI isn't your mistake, btw, it seems that clippy added a new check.

Closed due to inactivity.


Minor modification of test result specification

Instead of a single ignore value which would always report
pass allow using any of the supported test result values.

@lukaszachy, @thrix, @dkarpele, @RHEmployee, the test result spec modified as agreed on the hacking session. Please, have a look.

LGTM

Thanks for this. Looks good.

nice, lgtm, when implemeting we should somehow indicate this result was forced

when implemeting we should somehow indicate this result was forced

Good idea, I think this should be included in the note field.


Support distinguishing between development vs production dependencies

Use Case
I have some dependencies that I want tea to install when I'm developing the app locally (e.g. minikube for a local kubernetes cluster and kubectl to interact with it), but then in CI/CD I only need a subset of those dependencies (I wouldn't need minikube in CI/CD but I still need kubectl for updating the live kubernetes cluster).
Right now, all these dependencies (including development-only dependencies) are specified in one tea.yaml file in the root of my repository and there doesn't seem to be a way to make tea filter out certain dependencies to skip in production, or to install dependencies from a separate YAML file on CI/CD (e.g. a tea.prod.yaml file) that I'd specify production-only dependencies in.

This is an interesting idea. One option might be something like this:
git add tea.dev.yaml tea.prod.yaml
...
git clone foo
ln -s tea.dev.yaml tea.yaml
cd .

You loose some of the automaticality[wordmark pending], but you'd get finer-grained control. You could also use a tea-script in the language of your choice to manage that for you. In theory, extra deps are harmless but not costless; this isn't always true, but it should be true in your scenario. You could also compose your environments manually, say, by having a file like setup-dev-env.sh:
#!/bin/sh

tea +kubernetes.io/minikube sh

To allow loading your richer dev-env.

Good call. I'm surprised this hasn't come up before.
So one file would be:
dependencies:
   foo.com: ^1

production:
  dependencies:
    bar.org: ^2

development:
  dependencies:
   baz.com: ^3

Which seems to allow for everything.
Multifiles is a possibility, but it always seemed messy to me.


javax.servlet.ServletException: org.glassfish.jersey.server.ContainerException: java.lang.UnsatisfiedLinkError: org.usb4java.LibUsb.init(Lorg/usb4java/Context;)

Hi. I tried add to my src folder but still Im not be able to use this library.
I have tried to use MS32 but i got other error which saying not supported. here is the screenshot of my project's structure:  https://imgur.com/a/2oBeZuT
can  anyone help me please. thank you

According to your screenshot you placed the libusb.dll library in your project. This can't work. You have to use the libusb4java.dll library.


Connect to JabRef online

fixes #30

For the errors you need to probably install eslint-plugin-jest


Tracing (Edinburgh Roadmap Item)

Tracing is a stretch goal task for the Edinburgh release.  Tracing is the ability to trace a system API request inside and across EdgeX services for the purpose of debugging and performance metrics tracking.  Tracing is provided by frameworks such as GoKit, but EdgeX has not yet adopted such a framework and needs a solution that is language independent (for use across non-Go services like C based Device Services).

Most likely for Edinburgh we will have to be satisfied with a "poor man's solution" to tracing. This is predicated on the inclusion of the GoKit style logging current pending in PR #787. Simply put, every request handler will need to do the following:
1.) Interrogate HTTP headers on the incoming request to see if the "correlation-id" header is present. If not, create a correlation-id value (should be UUID format)
2.) Put the correlation-id value into the current context
3.) If a call to another service is made (like core-data to core-metadata) the correlation-id should be pulled from the context and its value used to set the header on the outgoing request
4.) When the request handler completes, regardless of success or failure, the correlation-id must be logged via the GoKit logger with its own key/value.

@SteveOss @cloudxxx8 Please note, there's a device service work item here in that every call to the core services will need to contain a custom HTTP header
"correlation-id":

@tsconn23
Since device-sdk-go is calling LogginClient to send requests, I thought we need to add an optional parameter to pass correlation-id and put the "X-Correlation-ID HTTP header" logic into LoggingClient.  What do you think?

@cloudxxx8 Well, yes in the case where the support-logging service is involved. But every client needs this same capability.

@tsconn23
You are right.  I will make device-sdk-go supports it once this capability of each clients is ready.

Closing. Replaced by issue #1014. Work is being done in PR #1067.


⚠ Bofrost.de has degraded performance

In 1677c32, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1045 ms

Resolved: Bofrost.de performance has improved in 9052aef after 8 hours, 29 minutes.


增加Clusterfile示例文件中的ssh相关注释

Describe what this PR does / why we need it
增加文档的可读性
Does this pull request fix one issue?
No

Describe how you did it
在README.md文件中的Clusterfile的配置示例中添加了ssh的注释。
说明了ssh的配置如何使用
Describe how to verify it
无需验证
Special notes for reviews

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.若谷 seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending?


Add Ed25519 to Curve25519 conversion

Issue #19

Please let me know if there is anything I can improve.

Bump. This is still relevant.

@benma overall the PR looks good, but I added some suggestions.

@blavenie I really appreciate you taking the time to make this patch. However like we discussed, there are some changes to be done. I'm going to close this, but would love to see you open a new PR with the changes that take the direction we discussed. Thank you!


ENYO-6096: Fix VirtualList to retain proper scroll position after upd…

…ating item size-spacing
Checklist

[x] I have read and understand the contribution guide

[x] A CHANGELOG entry is included

[ ] At least one test case is included for this feature or bug fix

[x] Documentation was added or is not needed

[ ] This is an API breaking change

Issue Resolved / Feature Added
After updating the item layout of a VirtualList (or VirtualGridList) via the spacing and/or itemSize props (where the amount of items are the same), the scroll position can appear to be incorrect, depending on where the scroller position was prior to the update. It will then "sync" back to its correct position once you begin to scroll the list contents. This can result in an instant and unexpected "jump" from item 0 to wherever the scroll position should be.
The scroll position is actually correct (as the scroll buttons and thumb reflect the correct position). It's the viewport that appears incorrect.
Resolution
We can update the viewport to scroll to the scroll position after such an update, where the list content sizes have changed.

I fixed the CHANGELOG.md conflict.

LGTM
But I'd like to note one thing.
When updating spacing or itemSize, we try to restore the previous scroll position in this PR. But when updating dataSize, clientWidth and clientHeight, we tried to reset the scroll position to 0. So there are two different policies to adjust the scroll position when changing the metrics of a list or items.
To reset the scroll position when changing a spacing or itemSize prop, VirtualList should request Scrollable to do it and it makes the code complex. Changing those props is not the common case in real apps. So I'm find with the current implementation.


MacOS 10.14: Did not boot until I selected 2 CPU

During first boot from iso, boot always stopped at a certain time "Dawin bootstrap 6.0.0....".
After changing number of processors from 1 to 2, boot continued. Don't know if this is only an issue for my Macbook Air 2014 (MacBookAir6,2).

I can confirm this for 10.14 (Mojave). Following the instructions exactly but then also allocating 2 CPUs under System -> Processor -> Processor(s) fixed the bootstrapping. Startup paused at a different spot for me though, something about "Creating RAM disk...". (I'm on a 2013 MacBook Pro)


The master project is not compiling anymore

Describe the bug
Since this new version 7.0.5 my project (and also the github example project) is not compiling anymore. I'm getting this 3 errors bellow:
: Error: Method 'insert' cannot be called on 'OverlayState?' because it is potentially null.
package:searchfield/src/searchfield.dart:348
- 'OverlayState' is from 'package:flutter/src/widgets/overlay.dart' ('../../flutter/packages/flutter/lib/src/widgets/overlay.dart').
package:flutter/…/widgets/overlay.dart:1
Try calling using ?. instead.
          Overlay.of(context).insert(_overlayEntry!);
                              ^^^^^^

: Error: No named parameter with the name 'padding'.
package:searchfield/src/searchfield.dart:532
                padding: EdgeInsets.zero,
                ^^^^^^^
: Context: Found this candidate, but the arguments don't match.
../…/widgets/scrollbar.dart:917

  const RawScrollbar({
        ^^^^^^^^^^^^
: Error: The method 'TextFieldTapRegion' isn't defined for the class '_SearchFieldState<T>'.
package:searchfield/src/searchfield.dart:448
- '_SearchFieldState' is from 'package:searchfield/src/searchfield.dart' ('../lib/src/searchfield.dart').
package:searchfield/src/searchfield.dart:1
Try correcting the name to the name of an existing method, or defining a method named 'TextFieldTapRegion'.

            itemBuilder: (context, index) => TextFieldTapRegion(

To Reproduce
Just download the master code on Github and try to compile
Expected behavior
Compile and run
Actual behavior
Not compiling.

@esmlima You need to be on the latest flutter version 3.7 to make use of the new version of this package.

This is mentioned in the changelog https://pub.dev/packages/searchfield/changelog in release v0.7.5


New package: PlutoUI v0.1.0

Registering package: PlutoUI
Repository: https://github.com/fonsp/PlutoUI.jl
Created by: @fonsp
Version: v0.1.0
Commit: 4fe6335622a82e134517ed1b97d636f52065465b
Reviewed by: @fonsp
Reference: https://github.com/fonsp/PlutoUI.jl/commit/4fe6335622a82e134517ed1b97d636f52065465b#commitcomment-38524641

Thanks! I will add a Compat entry for Julia; the double uppercase was intended.


Published resources not found

Several resources that have been "published" via admin back end are not actually showing up in the front end.  For example, the Interdisciplinary Graduate Certificate in Sustainability academic program and the publications entitled "Key competencies in sustainability: a reference framework for academic program development," and "Harnessing the Sun: A Case Study of Solar Energy Deployment at Agnes Scott College," all show up as published on the admin side. However, they do not appear in the appropriate topic or content type on the front end. Clicking "View on site" button in admin takes me to this page not found error:

They don't show up because the status is New and not Published.

@juliandsmith please post here a link to either the resource or the related admin site, rather than the title. Later with thousands of entries it will be hard to find those.

The 'published' timestamp is automatically filled out once the status becomes 'Published'. To avoid confusion I made this field read only and added a help text.

It would be useful to continue to be able to edit the timestamp - but I do like that by default, the time that the change to Published is made shows up. Is there a way to add this back in?


can't start container which has been run

when I start my container "hello", the result is "please create it first".But when I create container "hello", hyperctl output the words ""/hello" is already in use". when  I use hyperctl list cmd , there did't outpur anything.  It's a bug or hyper not support as docker container? Item /var/lib/hyper/ has the same files as docker.
hyperctl start hello
hyperctl ERROR: Error from daemon's response: The pod(hello) can not be found, please create it first
hyperctl run -d --name hello a7c41708ef58
hyperctl ERROR: Error from daemon's response: Conflict. The name "/hello" is already in use by container 20d8fea07a87785aced03c1e7be26f4fb5b268f958f287619dfce5a2becfea70. You have to remove (or rename) that container to be able to reuse that name.
hyperctl list -p hello
POD ID              POD Name            VM name             Status

looks like some bugs in rollback procedures.
What is the a7c41708ef58?

a7c41708ef58 is my docker image which pull form my registry
hyperctl images
REPOSITORY                        TAG                 IMAGE ID            CREATED               VIRTUAL SIZE
<IP_ADDRESS>:5000/linhaidong/hello   v1                  a7c41708ef58        2018-01-16 15:50:14   122.8 MB

could you try hyperctl run with another name?
and could you try list all pod and containers? Looks the message shows there is no pod named as hello, but there has already been a container named with /hello

when hyperd runing, all operation is normal. When I restart hyperd, the hyperctl list cmd can't list container which I create by running  hyperctl run cmd.
#hyperd runing:
$ hyperctl list
POD ID              POD Name            VM name             Status
hello3              hello3              vm-EcbpSCOwia       running
hello4              hello4              vm-TpUJhFLJsC       running
$ hyperctl stop hello3
Successfully shutdown the POD: hello3!
$ hyperctl list
POD ID              POD Name            VM name             Status
hello3              hello3                                  failed
hello4              hello4              vm-TpUJhFLJsC       running
$ hyperctl start hello3
Successfully started the Pod(hello3)
#hyperd restart:
$ hyperctl list
POD ID              POD Name            VM name             Status
$hyperctl start hello3
hyperctl ERROR: Error from daemon's response: The pod(hello3) can not be found, please create it first
$hyperctl run -d --name hello3 a7c41708ef58
hyperctl ERROR: Error from daemon's response: Conflict. The name "/hello3" is already in use by container 88390a41f913fc76518d18292f26bb2aa113d13da890530e5aca3fabe837d347. You have to remove (or rename) that container to be able to reuse that name.

I had a similar issue with container name conflicts appearing in the hyperd INFO, WARNING and ERROR logs (/var/log/hyper/hyperd.*).
It turned out to be some orphan hosts (/var/lib/hyper/hosts/) and containers (/var/lib/hyper/containers/) hanging around after a hyperd service restart. These were enough to trigger the errors and cause contracts to fail, but would never appear in the POD list (hyperctl list)... just like you're describing.
After I deleted everything from the hosts and containers directories, and restarted hyperd, everything worked fine.
It would be good if a hyperd service restart somehow triggered a graceful stop of any active PODs, and then started them again afterwards. Theory needs testing, but I think this would avoid creating the orphans.

@joelmcdonald which version of hyperd are you working on? master branch or a binary package?

good question, it was installed by remote script as part of setting up a codius host... https://codius.s3.amazonaws.com/hyper-bootstrap.sh
'hyperctl info' shows Library Version: 1.02.146-RHEL7 (2018-01-22)

After the release, there are quite a few fixes landed in master branch, and we are going to release a new package in a week (some of the PRs have not been merged), before that, would you mind try built with the latest master?

Happy to try, I'll come back with the results

@gnawux I'm having trouble with the make... returns lots of "cannot use description in field value" type errors
Pre-requisites all installed ok, though I did have to add a symlink to resolve a failed file path.
Below path looks very circular... I get 10+ of these on screen, then make [2] fails with error 2, and make [1] fails with error 1.
Have I missed something?
[root@auscodius hyperd]# make Making all in cmd make[1]: Entering directory /src/github.com/hyperhq/hyperd/cmd'
Making all in hyperd
make[2]: Entering directory /src/github.com/hyperhq/hyperd/cmd/hyperd' go build -gcflags="if [ "" != "" ]; then echo "-N -l"; else echo ""; fi" -tags "static_build    exclude_graphdriver_btrfs libdm_no_deferred_remove" -ldflags "-X github.com/hyperhq/hyperd/utils.VERSION=1.0.0 -X github.com/hyperhq/hyperd/utils.GITCOMMIT=git describe --dirty --always --tags 2> /dev/null || true`" hyperd.go
github.com/hyperhq/hyperd/vendor/github.com/hyperhq/hyperd/daemon/pod
/usr/lib/golang/src/github.com/hyperhq/hyperd/vendor/github.com/hyperhq/hyperd/daemon/pod/persist.go:359:11: cannot use c.descript (type *"github.com/hyperhq/hyperd/vendor/github.com/hyperhq/hyperd/vendor/github.com/hyperhq/runv/api".ContainerDescription) as type *"github.com/hyperhq/hyperd/vendor/github.com/hyperhq/hyperd/vendor/github.com/hyperhq/hyperd/vendor/github.com/hyperhq/runv/api".ContainerDescription in field value`

Installed OK, service started OK...
I'll load a pod, restart and see if it errors
`[root@auscodius centos]# systemctl status hyperd
hyperd.service - hyperd
Loaded: loaded (/usr/lib/systemd/system/hyperd.service; enabled; vendor preset: disabled)
Active: active (running) since Tue 2018-07-10 08:47:11 UTC; 11s ago
Docs: http://docs.hypercontainer.io
Main PID: 12671 (hyperd)
CGroup: /system.slice/hyperd.service
└─12671 /usr/bin/hyperd --log_dir=/var/log/hyper
Jul 10 08:47:11 auscodius.com systemd[1]: Started hyperd.
Jul 10 08:47:11 auscodius.com systemd[1]: Starting hyperd...
Jul 10 08:47:11 auscodius.com hyperd[12671]: time="2018-07-10T08:47:11Z" level=warning msg="devmapper: Usage of loopback devices is strongly discouraged for production use. Please use --storage-opt dm.thinpooldev or us...pooldev section."
Jul 10 08:47:11 auscodius.com hyperd[12671]: time="2018-07-10T08:47:11Z" level=warning msg="devmapper: Base device already exists and has filesystem xfs on it. User specified filesystem  will be ignored."
Jul 10 08:47:11 auscodius.com hyperd[12671]: time="2018-07-10T08:47:11Z" level=info msg="[graphdriver] using prior storage driver "devicemapper""
Jul 10 08:47:11 auscodius.com hyperd[12671]: time="2018-07-10T08:47:11Z" level=info msg="Graph migration to content-addressability took 0.00 seconds"
Jul 10 08:47:11 auscodius.com hyperd[12671]: time="2018-07-10T08:47:11Z" level=info msg="Firewalld running: true"
Jul 10 08:47:11 auscodius.com hyperd[12671]: time="2018-07-10T08:47:11Z" level=info msg="Loading containers: start."
Jul 10 08:47:11 auscodius.com hyperd[12671]: time="2018-07-10T08:47:11Z" level=info msg="Loading containers: done."
Hint: Some lines were ellipsized, use -l to show in full.`

Unfortunately, the issue is still there in the new rpms.

upgraded and started hyperd
successfully loaded test POD
hyperctl list showed POD active
restarted hyperd
hyperctl list showed nothing
hosts and containers were still present in /var/lib/hyper/hosts/ and /var/lib/hyper/containers/
logs confirm name conflict error (below)

[root@auscodius centos]# more /var/log/hyper/hyperd.INFO Log file created at: 2018/07/10 08:52:36 Running on machine: auscodius Binary: Built with gc go1.8 for linux/amd64 Log line format: [IWEF]mmdd hh:mm:ss.uuuuuu threadid file:line] msg I0710 08:52:36.477023   13221 config.go:39] config file: %!(EXTRA string=/etc/hyper/config) I0710 08:52:36.477346   13221 config.go:74] [/etc/hyper/config] config items: &types.HyperConfig{ConfigFile:"/etc/hyper/config", Root:"/var/lib/hyper", Host:"", GRPCHost:"", StorageDriver:"", StorageBaseSize:"", VmFactoryPolicy:"", Driver:" ", Kernel:"/var/lib/hyper/kernel", Initrd:"/var/lib/hyper/hyper-initrd.img", Bridge:"", BridgeIP:"", DisableIptables:false, EnableVsock:false, DefaultLog:"", DefaultLogOpt:map[string]string{}, logPrefix:"[/etc/hyper/config] "} I0710 08:52:36.631031   13221 daemon.go:225] The hypervisor's driver is I0710 08:52:36.653608   13221 migration.go:23] Migrate lagecy persistent pod data, found: 0, migrated: 0 I0710 08:52:36.653858   13221 persist.go:57] layout loading finished E0710 08:52:36.654224   13221 persist.go:100] Pod[l2xvchk27rbrnh3mc3y4p3iaeoonjzur2u24qxuod2iaqd5mlioa] failed to load inf info of : leveldb: not found W0710 08:52:36.654536   13221 daemon.go:82] Got a unexpected error when creating(load) pod l2xvchk27rbrnh3mc3y4p3iaeoonjzur2u24qxuod2iaqd5mlioa, leveldb: not found I0710 08:52:36.654706   13221 hyperd.go:189] Hyper daemon: 1.0.0 I0710 08:52:44.537987   13221 list.go:94] got list request for pod (pod: , vm: ) E0710 08:53:15.119353   13221 server.go:170] Handler for GET /pod/info returned error: Can not get Pod info with pod ID(l2xvchk27rbrnh3mc3y4p3iaeoonjzur2u24qxuod2iaqd5mlioa) I0710 08:53:15.122847   13221 vm_states.go:301] SB[vm-YhvXsEcVAg] startPod: &json.Pod{Hostname:"l2xvchk27rbrnh3mc3y4p3iaeoonjzur2u24qxuod2iaqd5mlioa", DeprecatedContainers:[]json.Container(nil), DeprecatedInterfaces:[]json.NetworkInf(nil), Dns:[]string(nil), DnsOptions:[]string(nil), DnsSearch:[]string(nil), DeprecatedRoutes:[]json.Route(nil), ShareDir:"share_dir", PortmappingWhiteLists:(*json.PortmappingWhiteList)(0xc4208195f0)} I0710 08:53:19.510273   13221 vm_states.go:304] SB[vm-YhvXsEcVAg] pod start successfully I0710 08:53:19.510309   13221 provision.go:285] Pod[l2xvchk27rbrnh3mc3y4p3iaeoonjzur2u24qxuod2iaqd5mlioa] sandbox init result: <nil> E0710 08:53:19.512929   13221 container.go:411] Pod[l2xvchk27rbrnh3mc3y4p3iaeoonjzur2u24qxuod2iaqd5mlioa] Con[(l2xvchk27rbrnh3mc3y4p3iaeoonjzur2u24qxuod2iaqd5mlioa__app)] Conflict. The name "/l2xvchk27rbrnh3mc3y4p3iaeoonjzur2u24qxuod2iaqd5m lioa__app" is already in use by container 0931f8ea35412777a4bd22e76a50f52ccd760383d55dc91cc4b3eb6df2583e6a. You have to remove (or rename) that container to be able to reuse that name. I0710 08:53:19.512963   13221 vm_states.go:332] SB[vm-YhvXsEcVAg] poweroff vm based on command: vm.Kill() E0710 08:53:19.512982   13221 run.go:34] l2xvchk27rbrnh3mc3y4p3iaeoonjzur2u24qxuod2iaqd5mlioa: failed to add pod: Conflict. The name "/l2xvchk27rbrnh3mc3y4p3iaeoonjzur2u24qxuod2iaqd5mlioa__app" is already in use by container 0931f8ea3541277 7a4bd22e76a50f52ccd760383d55dc91cc4b3eb6df2583e6a. You have to remove (or rename) that container to be able to reuse that name. E0710 08:53:19.512997   13221 server.go:170] Handler for POST /pod/create returned error: Conflict. The name "/l2xvchk27rbrnh3mc3y4p3iaeoonjzur2u24qxuod2iaqd5mlioa__app" is already in use by container 0931f8ea35412777a4bd22e76a50f52ccd76038 3d55dc91cc4b3eb6df2583e6a. You have to remove (or rename) that container to be able to reuse that name. I0710 08:53:19.513193   13221 qemu_process.go:93] kill Qemu... 13334 I0710 08:53:19.513243   13221 context.go:199] SB[vm-YhvXsEcVAg] VmContext Close() I0710 08:53:19.513277   13221 qmp_handler.go:344] quit QMP by command QMP_QUIT E0710 08:53:19.513293   13221 qmp_handler.go:141] QMP exit as got error: read unix @->/var/run/hyper/vm-YhvXsEcVAg/qmp.sock: use of closed network connection I0710 08:53:19.513335   13221 decommission.go:536] Pod[l2xvchk27rbrnh3mc3y4p3iaeoonjzur2u24qxuod2iaqd5mlioa] got vm exit event I0710 08:53:19.513342   13221 etchosts.go:97] cleanupHosts /var/lib/hyper/hosts/l2xvchk27rbrnh3mc3y4p3iaeoonjzur2u24qxuod2iaqd5mlioa, /var/lib/hyper/hosts/l2xvchk27rbrnh3mc3y4p3iaeoonjzur2u24qxuod2iaqd5mlioa/hosts E0710 08:53:19.513395   13221 json.go:601] SB[vm-YhvXsEcVAg] get hyperstart API version error: hyperstart closed E0710 08:53:19.513427   13221 json.go:141] read init data failed E0710 08:53:19.513439   13221 json.go:601] SB[vm-YhvXsEcVAg] get hyperstart API version error: hyperstart closed W0710 08:53:19.513450   13221 hypervisor.go:47] SB[vm-YhvXsEcVAg] keep-alive test end with error: hyperstart closed E0710 08:53:19.513482   13221 json.go:401] read tty data failed E0710 08:53:19.513496   13221 json.go:458] SB[vm-YhvXsEcVAg] tty socket closed, quit the reading goroutine: read unix @->/var/run/hyper/vm-YhvXsEcVAg/tty.sock: use of closed network connection I0710 08:53:19.517880   13221 server.go:388] getting image: calerobertson/test-manifest@sha256:7c8b236c5f01e5abc78c9500cce7c974ffcedd980e60c2d3a5f1a44c8455ae2d: I0710 08:53:19.519579   13221 decommission.go:578] Pod[l2xvchk27rbrnh3mc3y4p3iaeoonjzur2u24qxuod2iaqd5mlioa] pod stopped I0710 08:53:22.206354   13221 server.go:406] got image: calerobertson/test-manifest@sha256:7c8b236c5f01e5abc78c9500cce7c974ffcedd980e60c2d3a5f1a44c8455ae2d I0710 08:53:22.207930   13221 server.go:388] getting image: docker.coil.com/codius-moneyd@sha256:4c02fc168e6b4cfde90475ed3c3243de0bce4ca76b73753a92fb74bf5116deef: I0710 08:53:23.005769   13221 server.go:406] got image: docker.coil.com/codius-moneyd@sha256:4c02fc168e6b4cfde90475ed3c3243de0bce4ca76b73753a92fb74bf5116deef I0710 08:53:23.007600   13221 vm_states.go:301] SB[vm-njySycyLVm] startPod: &json.Pod{Hostname:"l2xvchk27rbrnh3mc3y4p3iaeoonjzur2u24qxuod2iaqd5mlioa", DeprecatedContainers:[]json.Container(nil), DeprecatedInterfaces:[]json.NetworkInf(nil), Dns:[]string(nil), DnsOptions:[]string(nil), DnsSearch:[]string(nil), DeprecatedRoutes:[]json.Route(nil), ShareDir:"share_dir", PortmappingWhiteLists:(*json.PortmappingWhiteList)(0xc42083b1d0)} I0710 08:53:27.387600   13221 vm_states.go:304] SB[vm-njySycyLVm] pod start successfully I0710 08:53:27.387630   13221 provision.go:285] Pod[l2xvchk27rbrnh3mc3y4p3iaeoonjzur2u24qxuod2iaqd5mlioa] sandbox init result: <nil> E0710 08:53:27.390305   13221 container.go:411] Pod[l2xvchk27rbrnh3mc3y4p3iaeoonjzur2u24qxuod2iaqd5mlioa] Con[(l2xvchk27rbrnh3mc3y4p3iaeoonjzur2u24qxuod2iaqd5mlioa__app)] Conflict. The name "/l2xvchk27rbrnh3mc3y4p3iaeoonjzur2u24qxuod2iaqd5m lioa__app" is already in use by container 0931f8ea35412777a4bd22e76a50f52ccd760383d55dc91cc4b3eb6df2583e6a. You have to remove (or rename) that container to be able to reuse that name. I0710 08:53:27.390330   13221 vm_states.go:332] SB[vm-njySycyLVm] poweroff vm based on command: vm.Kill() E0710 08:53:27.390345   13221 run.go:34] l2xvchk27rbrnh3mc3y4p3iaeoonjzur2u24qxuod2iaqd5mlioa: failed to add pod: Conflict. The name "/l2xvchk27rbrnh3mc3y4p3iaeoonjzur2u24qxuod2iaqd5mlioa__app" is already in use by container 0931f8ea3541277 7a4bd22e76a50f52ccd760383d55dc91cc4b3eb6df2583e6a. You have to remove (or rename) that container to be able to reuse that name. E0710 08:53:27.390358   13221 server.go:170] Handler for POST /pod/create returned error: Conflict. The name "/l2xvchk27rbrnh3mc3y4p3iaeoonjzur2u24qxuod2iaqd5mlioa__app" is already in use by container 0931f8ea35412777a4bd22e76a50f52ccd76038 3d55dc91cc4b3eb6df2583e6a. You have to remove (or rename) that container to be able to reuse that name. I0710 08:53:27.390481   13221 qemu_process.go:93] kill Qemu... 13348 I0710 08:53:27.390529   13221 context.go:199] SB[vm-njySycyLVm] VmContext Close() I0710 08:53:27.390555   13221 qmp_handler.go:344] quit QMP by command QMP_QUIT E0710 08:53:27.390571   13221 qmp_handler.go:141] QMP exit as got error: read unix @->/var/run/hyper/vm-njySycyLVm/qmp.sock: use of closed network connection I0710 08:53:27.390611   13221 decommission.go:536] Pod[l2xvchk27rbrnh3mc3y4p3iaeoonjzur2u24qxuod2iaqd5mlioa] got vm exit event I0710 08:53:27.390618   13221 etchosts.go:97] cleanupHosts /var/lib/hyper/hosts/l2xvchk27rbrnh3mc3y4p3iaeoonjzur2u24qxuod2iaqd5mlioa, /var/lib/hyper/hosts/l2xvchk27rbrnh3mc3y4p3iaeoonjzur2u24qxuod2iaqd5mlioa/hosts I0710 08:53:27.390626   13221 etchosts.go:101] cannot find /var/lib/hyper/hosts/l2xvchk27rbrnh3mc3y4p3iaeoonjzur2u24qxuod2iaqd5mlioa/hosts I0710 08:53:27.390671   13221 decommission.go:578] Pod[l2xvchk27rbrnh3mc3y4p3iaeoonjzur2u24qxuod2iaqd5mlioa] pod stopped E0710 08:53:27.390682   13221 json.go:601] SB[vm-njySycyLVm] get hyperstart API version error: hyperstart closed E0710 08:53:27.390706   13221 json.go:401] read tty data failed E0710 08:53:27.390714   13221 json.go:458] SB[vm-njySycyLVm] tty socket closed, quit the reading goroutine: read unix @->/var/run/hyper/vm-njySycyLVm/tty.sock: use of closed network connection E0710 08:53:27.390730   13221 json.go:141] read init data failed E0710 08:53:27.390737   13221 json.go:601] SB[vm-njySycyLVm] get hyperstart API version error: hyperstart closed W0710 08:53:27.390744   13221 hypervisor.go:47] SB[vm-njySycyLVm] keep-alive test end with error: hyperstart closed

could you purge your old pods and try again with the new binaries?

Pretty sure that's what I did... stopped and removed all PODs, stopped hyperd, deleted all hosts and containers, installed new rpms with --force option, started hyperd, etc per above
Did I miss anything?

sorry... just read the second half of your message. I'll purge those files, apply the new binaries and retest

OK, purged /var/lib/hyper/* but left kernel and hyper-initrd.img, reinstalled new binaries, started service and retested...
The issue is still there. Logs report container name conflict, old containers and host are still present, but nothing shows in hyperctl list

Weird, as it report name conflict, the old leveldb file should still be there.

No rush, it will be 24 hours before I have a chance to retest any further updates.
What's the path for leveldb file?

it should under /var/lib/hyper/lib/

Within /var/lib/hyper/lib/hyper.db I have 3 .ldbv files, 1 .log file, and a CURRENT, LOCK, LOG and MANIFEST-000010 file.
Only the log file has been updated since the service was restarted.
hyperd service status
hyperd:     active (running) since Tue 2018-07-10 10:11:02 UTC; 1h 13min ago
file list of hyper.db
[root@auscodius hyper.db]# ls -la total 36 drwxr-xr-x 2 root root  139 Jul 10 10:11 . drwxr-xr-x 3 root root   50 Jul 10 09:57 .. -rw-r--r-- 1 root root 4205 Jul 10 10:01 000002.ldb -rw-r--r-- 1 root root  192 Jul 10 10:08 000005.ldb -rw-r--r-- 1 root root 5790 Jul 10 10:11 000008.ldb -rw-r--r-- 1 root root  152 Jul 10 10:12 000009.log -rw-r--r-- 1 root root   16 Jul 10 10:11 CURRENT -rw-r--r-- 1 root root    0 Jul 10 09:57 LOCK -rw-r--r-- 1 root root 2301 Jul 10 10:11 LOG -rw-r--r-- 1 root root  657 Jul 10 10:11 MANIFEST-000010

Any luck on this?

@1maginarium @linengier @joelmcdonald We have recently release v1.1.0 and it contains several bugfix on resource management. Would you please see if the problem still exists?

hyper-container.x86_64               1.1.0-1.el7                     installed   hyperstart.x86_64                    1.1.0-1.el7                     installed   qemu-hyper.x86_64                    2.4.1-3.el7.centos              installed
This program is very easily reproduced by simply stopping or restarting hyperd / the server while a pod is running.
Then they turn into stale, zombie pods, that cannot be seen in hyperctl list only hyperctl info under pods. They also show up in systemctl status hyperd -l as to their pod names, but can not be found or deleted under any circumstance. Then they just stay, and keep you failing your self-test until you delete your codius server and restart it from scratch.

hyper-container.x86_64 1.1.0-1.el7 installed hyperstart.x86_64 1.1.0-1.el7 installed qemu-hyper.x86_64 2.4.1-3.el7.centos installed
This program is very easily reproduced by simply stopping or restarting hyperd / the server while a pod is running.
Then they turn into stale, zombie pods, that cannot be seen in hyperctl list only hyperctl info under pods. They also show up in systemctl status hyperd -l as to their pod names, but can not be found or deleted under any circumstance.


fix(report): coverage update for xsl:where-populated

This pull request makes xsl:where-populated follow the Use Child Data rule and adds test cases for the "unknown" status. that can result from that rule.
Note: This pull request does not include the changes in the open pull request #1978. Eventually, everything will get merged together, but I didn't want to make this simpler pull request depend on that more complicated one.
Fixes #1946.

Cc: @birdya22

Looks good to me.

Thanks for the quick code review. I'm going to merge this and use xsl:where-populated in some new test cases for fixing bug #1980.


run_tests.py FAILED while PASSED running the tests one by one from command line

What version of gRPC and what language are you using?
From a pull request #17939
What operating system (Linux, Windows, …) and version?
MacOS 10.14.3
What runtime / compiler are you using (e.g. python version or version of gcc)
$ clang --version
Apple LLVM version 10.0.0 (clang-1<IP_ADDRESS>)
Target: x86_64-apple-darwin18.2.0
Thread model: posix
InstalledDir: /Library/Developer/CommandLineTools/usr/b

What did you do?
Ran tests:
python tools/run_tests/run_tests.py -l c++ -c asan
What did you expect to see?
Tests passed
What did you see instead?
Some of the tests failed. Part of results:
$ python tools/run_tests/run_tests.py -l c++ -c asan
PASSED: make [time=221.9sec, retries=0:0]2019-02-09 13:13:45,882 detected port server running version 20
2019-02-09 13:13:45,992 my port server is version 20

==53671==AddressSanitizer: detect_leaks is not supported on this platform.
FAILED: bins/asan/ref_counted_ptr_test --gtest_filter=RefCountedPtr.RefCountedWithTracing  GRPC_POLL_STRATEGY=poll [ret=-6, pid=53671, time=0.0sec]

==53679==AddressSanitizer: detect_leaks is not supported on this platform.
FAILED: bins/asan/status_metadata_test --gtest_filter=GetStatusCodeFromMetadata.Unparseable  GRPC_POLL_STRATEGY=none [ret=-6, pid=53679, time=0.0sec]
...
...
...
FAILED: bins/asan/time_change_test --gtest_filter=TimeChangeTest.TimeJumpForwardBeforeServerConnect  GRPC_POLL_STRATEGY=poll
FAILED: bins/asan/time_change_test --gtest_filter=TimeChangeTest.TimeJumpForwardBeforeStreamCreated  GRPC_POLL_STRATEGY=poll
FAILED: bins/asan/time_change_test --gtest_filter=TimespecTest.GprNowInvalidClockType  GRPC_POLL_STRATEGY=poll
FAILED: bins/asan/time_change_test --gtest_filter=TimespecTest.GprTimeAddNegativeNs  GRPC_POLL_STRATEGY=poll
FAILED: bins/asan/time_change_test --gtest_filter=TimespecTest.GprTimeSubNegativeNs  GRPC_POLL_STRATEGY=poll
FAILED: bins/asan/time_change_test --gtest_filter=TimespecTest.GrpcNegativeMillisToTimespec  GRPC_POLL_STRATEGY=poll
FAILED: bins/asan/transport_pid_controller_test GRPC_POLL_STRATEGY=poll
FAILED: bins/asan/transport_security_common_api_test GRPC_POLL_STRATEGY=poll
FAILED: bins/asan/writes_per_rpc_test --gtest_filter=WritesPerRpcTest.UnaryPingPong  GRPC_POLL_STRATEGY=poll
FAILED: Some tests failed

But tests PASSED when I tried running some of the failed tests from command line
$ bins/asan/time_change_test --gtest_filter=TimeChangeTest.TimeJumpForwardBeforeStreamCreated  GRPC_POLL_STRATEGY=poll
D0209 13:18:50.473819000<PHONE_NUMBER> test_config.cc:391]                test slowdown factor: sanitizer=3, fixture=1, poller=1, total=3
Note: Google Test filter = TimeChangeTest.TimeJumpForwardBeforeStreamCreated
[==========] Running 1 test from 1 test case.
[----------] Global test environment set-up.
[----------] 1 test from TimeChangeTest
[ RUN      ] TimeChangeTest.TimeJumpForwardBeforeStreamCreated
Server listening on localhost:1954
[       OK ] TimeChangeTest.TimeJumpForwardBeforeStreamCreated (1027 ms)
[----------] 1 test from TimeChangeTest (1027 ms total)

[----------] Global test environment tear-down
[==========] 1 test from 1 test case ran. (1027 ms total)
[  PASSED  ] 1 test.

$ bins/asan/time_change_test --gtest_filter=TimespecTest.GrpcNegativeMillisToTimespec  GRPC_POLL_STRATEGY=poll
D0209 13:19:10.968830000<PHONE_NUMBER> test_config.cc:391]                test slowdown factor: sanitizer=3, fixture=1, poller=1, total=3
Note: Google Test filter = TimespecTest.GrpcNegativeMillisToTimespec
[==========] Running 1 test from 1 test case.
[----------] Global test environment set-up.
[----------] 1 test from TimespecTest
[ RUN      ] TimespecTest.GrpcNegativeMillisToTimespec
[       OK ] TimespecTest.GrpcNegativeMillisToTimespec (0 ms)
[----------] 1 test from TimespecTest (0 ms total)

[----------] Global test environment tear-down
[==========] 1 test from 1 test case ran. (0 ms total)
[  PASSED  ] 1 test.

$ bins/asan/bm_arena --benchmark_filter=BM_Arena_Batch/4096/8/64$  GRPC_POLL_STRATEGY=none
The number of inputs is very large. BM_Arena_Batch will be repeated at least 105 times.
Run on (8 X 2900 MHz CPU s)
2019-02-09 13:22:01
***WARNING*** Library was built as DEBUG. Timings may be affected.
----------------------------------------------------------------
Benchmark                         Time           CPU Iterations
----------------------------------------------------------------
BM_Arena_Batch/4096/8/64       1424 ns       1423 ns     476408

$ bins/asan/cxx_slice_test --gtest_filter=SliceTest.StaticBuf  GRPC_POLL_STRATEGY=none
Note: Google Test filter = SliceTest.StaticBuf
[==========] Running 1 test from 1 test case.
[----------] Global test environment set-up.
[----------] 1 test from SliceTest
[ RUN      ] SliceTest.StaticBuf
[       OK ] SliceTest.StaticBuf (0 ms)
[----------] 1 test from SliceTest (0 ms total)

[----------] Global test environment tear-down
[==========] 1 test from 1 test case ran. (0 ms total)
[  PASSED  ] 1 test.

I've figured out when I run one of the tests with ASAN_OPTIONS defined, it failed.
So, the issue is caused by my environment mentioned here.
$ ASAN_OPTIONS=detect_leaks=1 bins/asan/time_change_test --gtest_filter=TimespecTest.GrpcNegativeMillisToTimespec  GRPC_POLL_STRATEGY=poll
==39220==AddressSanitizer: detect_leaks is not supported on this platform.
Abort trap: 6

I'll going to close this issue.


BearSSL SSL certificate has expired

when doing git clone --recursive https://github.com/Superhouse/esp-open-rtos.git I get the following error:
Cloning into '/Volumes/case-sensitive/esp-open-sdk/esp-open-rtos/extras/bearssl/BearSSL'...
fatal: unable to access 'https://www.bearssl.org/git/BearSSL/': SSL certificate problem: certificate has expired

The cert is good and valid until Feb 24th. You may want to check the local time/date on your host.

I know, I've checked both. That's weird.
date "+DATE: %Y-%m-%d%nTIME: %H:%M:%S"
DATE: 2022-01-19
TIME: 03:22:57
MITM?

I don't think it's MITM, must be something silly.
Here is what I see when I query for the cert:
$ echo Q | openssl s_client -connect www.bearssl.org:443 | openssl x509 -noout -dates
depth=2 C = US, O = Internet Security Research Group, CN = ISRG Root X1
verify return:1
depth=1 C = US, O = Let's Encrypt, CN = R3
verify return:1
depth=0 CN = bearssl.org
verify return:1
DONE
notBefore=Nov 26 07:56:32 2021 GMT
notAfter=Feb 24 07:56:31 2022 GMT

What do you see when you execute the same command? I wonder if "has expired" is just an incorrect error message.

Tried it here:
echo Q | openssl s_client -connect www.bearssl.org:443 | openssl x509 -noout -dates
depth=2 C = US, O = Internet Security Research Group, CN = ISRG Root X1
verify error:num=20:unable to get local issuer certificate
verify return:0
DONE
notBefore=Nov 26 07:56:32 2021 GMT
notAfter=Feb 24 07:56:31 2022 GMT

The dates are good, it's your chain which could not be verified (see your "verify error" message).
I suspect this is your CA Root got expired or missing. Check this one: https://letsencrypt.org/docs/dst-root-ca-x3-expiration-september-2021/

verify returned 0 instead of 1.
do you suggest upgrading OS on my obsolete macbook?

If upgrading OS is an option, that would do it.
If you can't do it for any reason, get the proper CA cert into your KeyChain on OSX: https://www.tenseg.net/blog/2021/10/10/installing-the-new-lets-encrypt-root-certificate/

thanks, but it didn't work - probably, a different keychain (and a different certificate chain?) is used by browser and wget (or whatever) - that would explain that my browser initially has no problems with opening that website.
is there another workaround, like cloning that git manually?

btw, when I open https://www.bearssl.org/git/BearSSL in chrome, I seee 404 error

Getting 404 is ok as you are not accessing Git repo in your browser. But at least your updated CA root is readable by your browser. Now you need to make it working using Git client.
Try this under sudo/root on your OSX:
% cd /etc/ssl
% sudo mv cert.pem cert.pem.orig
% sudo wget -O cert.pem https://curl.se/ca/cacert.pem

That will make a backup copy of your original cert.pem file and grab online one of the latest ones.
As a verification, you can do either one:
% echo Q | openssl s_client -connect www.bearssl.org:443 | openssl x509 -noout -dates
You should see "verify return:1" and no errors.
or
% git clone https://www.bearssl.org/git/BearSSL
You should get Git repo cloned successfully.

once again: I had no issues accessing that site with my browser.
after these commands, I still get the same error: echo Q | openssl s_client -connect www.bearssl.org:443 | openssl x509 -noout -dates depth=2 C = US, O = Internet Security Research Group, CN = ISRG Root X1 verify error:num=20:unable to get local issuer certificate verify return:0 DONE notBefore=Nov 26 07:56:32 2021 GMT notAfter=Feb 24 07:56:31 2022 GMT
old version of openssl?
openssl version -a LibreSSL 2.2.7 built on: date not available platform: information not available options:  bn(64,64) rc4(ptr,int) des(idx,cisc,16,int) blowfish(idx)  compiler: information not available OPENSSLDIR: "/private/etc/ssl"


make juicefs.ceph failed

What happened:
When  exec make juicefs.ceph,it throws "/opt/mygo/pkg/mod/github.com/ceph/go-ceph@v0.4.0/rados/command.go:106:9: could not determine kind of name for C.rados_mgr_command"
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?
Environment:

JuiceFS version (use juicefs --version) or Hadoop Java SDK version: 0.17.5
Cloud provider or hardware configuration running JuiceFS: ardware configuration running JuiceFS
OS (e.g cat /etc/os-release): CentOS Linux release 7.3.1611 (Core)
Kernel (e.g. uname -a): 4.4.146-1.el7.elrepo.x86_64
Object storage (cloud provider and region, or self maintained): Ceph RADOS
Metadata engine info (version, cloud provider managed or self maintained):
Network connectivity (JuiceFS to metadata engine, JuiceFS to object storage):
Others: go version :1.16   gcc version gcc-7

JuiceFS use go-ceph v0.4.0 to access rados. go-ceph v0.4.0 support ceph versions: luminous, mimic, nautilus, octopus (version 12~15) as noted here.
This means JuiceFS doesn't support accessing rados older than luminous(version 12)
On CentOS 7, I installed librados development files from official yum repository:
# yum search librados
已加载插件：fastestmirror
Loading mirror speeds from cached hostfile
=========================================================================== N/S matched: librados ===========================================================================
librados2.i686 : RADOS distributed object store client library
librados2.x86_64 : RADOS distributed object store client library
librados2-devel.i686 : RADOS headers
librados2-devel.x86_64 : RADOS headers

# yum install -y librados2-devel.x86_64
.....
....
已安装:
  librados2-devel.x86_64 1:10.2.5-4.el7

作为依赖被安装:
  boost-iostreams.x86_64 0:1.53.0-28.el7       boost-random.x86_64 0:1.53.0-28.el7       boost-system.x86_64 0:1.53.0-28.el7       boost-thread.x86_64 0:1.53.0-28.el7
  librados2.x86_64 1:10.2.5-4.el7

完毕！

The make juicefs.ceph can reproduce your problem. You can check your librados-devel version like this:
# rpm -qa | grep librados
librados2-10.2.5-4.el7.x86_64
librados2-devel-10.2.5-4.el7.x86_64

Here on my server, version 10, older than luminous.

Our Ceph version is octopus, rpm -qa |grep  librados in my server shows:
[root@xxxxx-xxx ~]# rpm -qa |grep librados
librados2-10.2.5-4.el7.x86_64
librados2-devel-10.2.5-4.el7.x86_64

down librados2-15.2.10-0.el7.x86_64.rpm and librados-devel-15.2.10-0.el7.x86_64.rpm  from http://fr.ceph.com/rpm-15.2.10/el7/x86_64/ ,Then exec  yum install -y *.rpm can resolve this probelm


Updated to Level-1

Updated dependencies.
I suggest we bump this to 1.0.0.
However, it does not include the latest levelup because of https://github.com/Level/packager/issues/20.

+1

@ralphtheninja can you please re-review? So I can get this out.
I used ~ for all deps.

cc @juliangruber

@mcollina Yep. Checking.

@mcollina Let me add a commit on top of this branch. Want to update .travis.yml.

+1 for 1.0.0.

λ npm publish

<EMAIL_ADDRESS>


Bump patch version of Go

This PR bumps Go 1.17.8 -> 1.17.11 to get latest security fixes.
(We are not aware of any of the security issues actually affecting cert-manager. See https://github.com/cert-manager/cert-manager/issues/5161 for context)
Bumps Go 1.17.8 -> 1.17.11 to get latest security fixes

/kind cleanup

/test

/test pull-cert-manager-e2e-v1-19
/test pull-cert-manager-e2e-v1-20
/test pull-cert-manager-e2e-v1-21
/test pull-cert-manager-e2e-v1-22

/test pull-cert-manager-e2e-v1-19
/test pull-cert-manager-e2e-v1-20
/test pull-cert-manager-e2e-v1-21

Thanks a lot @SgtCoDFish  ❤
Hopefully it'll get better over the weekend!!

/test pull-cert-manager-make-test


Prevented crash due to array mutation

I believe this will fix issue #182

@yannickl Would love to get this merged in!

@ApoorvKhatreja thanks for pinging me. I'm not really active anymore and I can easily miss important information.

Hello @yannickl, could you please help to make a new release version for this MR? Really appreciated it!

we are still waiting for a release.


feat(CLI): Adding Backfill feature in Cronworkflow Closes #4209

Checklist:

[ ] Either (a) I've created an enhancement proposal and discussed it with the community, (b) this is a bug fix, or (c) this is a chore.
[ ] The title of the PR is (a) conventional, (b) states what changed, and (c) suffixes the related issues number. E.g. "fix(controller): Updates such and such. Fixes #1234".
[ ] My organization is added to USERS.md.
[ ] I've signed the CLA.
[ ] I have written unit and/or e2e tests for my change. PRs without these are unlikely to be merged.
[ ] My builds are green. Try syncing with master if they are not.

Fixes #4209

Bump! Close or continue?

@sarabala1979 to set up meeting to dome feature.

Appears abandoned 😀

Appears abandoned 😀


Create de.json

first draft for the German translation for Pubby.Club

OK thank you.  I'll just ask you to remove the comments.  I will publish this translation so you can test and see the context of each sentence.


config: Update jekyll.yml(on: trace; off: incremental

Because github-pages >= 178 depends on jekyll-sass-converter = 1.5.2
and Gemfile depends on github-pages ~> 232,
jekyll-sass-converter = 1.5.2 is required.
So, because Gemfile depends on jekyll-sass-converter ~> 3.0,
version solving has failed.
Error: The process '/opt/hostedtoolcache/Ruby/3.3.4/x64/bin/bundle' failed with exit code 6

Because github-pages >= 231 depends on jekyll-relative-links = 0.6.1
and Gemfile depends on github-pages ~> 232,
jekyll-relative-links = 0.6.1 is required.
So, because Gemfile depends on jekyll-relative-links ~> 0.7.0,
version solving has failed.
Error: The process '/opt/hostedtoolcache/Ruby/3.3.4/x64/bin/bundle' failed with exit code 6


pixelmon.tree

Tree file for Pixelmon mod (https://reforged.gg/)

It's not sorting TMs for me, any idea why? I have "pixelmon.tree" in .minecraft/config/InvTweaks/trees.

It's not sorting TMs for me, any idea why? I have "pixelmon.tree" in .minecraft/config/InvTweaks/trees.

Only TMs are not being sorted? Or all Pixelmon items are not being sorted?
Try putting the tree file in both .minecraft/config/InvTweaks/trees and .minecraft/config/InvTweaks then restarting minecraft.
For some reason, the custom sort rules only work for me when putting the tree file in both folders.

Try putting the tree file in both .minecraft/config/InvTweaks/trees and .minecraft/config/InvTweaks then restarting minecraft.

Seems to have fixed it for me, thanks friend. Keep up the good work :)


Add local emulator backend

Description
Add a new backend IBMQLocalEmulatorBackend which uses AerBackend with the noise model and characteristics of the real device. This is similar to IBMQEmulatorBackend except that it does all emulation locally. The only outward difference is that it does not support contextual optimization (because AerBackend doesn't).
Related issues
Closes #65 .
Checklist

[x] I have performed a self-review of my code.
[x] I have commented hard-to-understand parts of my code.
[x] I have made corresponding changes to the public API documentation.
[x] I have added tests that prove my fix is effective or that my feature works.
[x] I have updated the changelog with any user-facing changes.

Would be good to add the IBMQLocalEmulatorBackend to the table of available backends .

Would be good to add the IBMQLocalEmulatorBackend to the table of available backends .

I think I did that as part of this PR, or did I miss something?

Would be good to add the IBMQLocalEmulatorBackend to the table of available backends .

I think I did that as part of this PR, or did I miss something?

Ah yes you did but I changed the formatting of the table in #265 . Sorry about that.

Would be good to add the IBMQLocalEmulatorBackend to the table of available backends .

I think I did that as part of this PR, or did I miss something?

Ah yes you did but I changed the formatting of the table in #265 . Sorry about that.

No problem, I'll merge and fix it up.


paket init should pin itself

Description
paket.exe init should pin the version of itself into paket.dependencies
Scenario
Given paket.exe is available in version 1.2.3
When one wants to initialize its repository
Then paket.exe init is called
Expected behavior
The command generates paket.dependencies file with this content
version 1.2.3
source https://www.nuget.org/api/v2

Actual behavior
The command generates paket.dependencies file with this content
source https://www.nuget.org/api/v2

Two possibilities
A. Introduce an option, e.g. --pin. The behavior is backward compatibility.
B. Make it as the standard behavior. The behavior is a "breaking change"
I prefer B, because one of the many advantage of paket is pinning the version of the (transitive) dependencies. So it is only logical to pin the version of paket itself.
I can submit a PR.

@matthid here you go :smirk:

I think it's reasonable.

Honestly I'd go for B.
In fact I think this might introduce some problems for new people where they will never notice that they need an update. To compensate for this I feel like paket update should update its own version. But I have that opinion for ages ;)

We would love to see a PR for that.
Matthias Dittrich<EMAIL_ADDRESS>schrieb am Di., 31. Juli 2018,
19:29:

Honestly I'd go for B.
In fact I think this might introduce some problems for new people where
they will never notice that they need an update. To compensate for this I
feel like paket update should update its own version. But I have that
opinion for ages ;)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/fsprojects/Paket/issues/3320#issuecomment-409302787,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AADgNIht4DIlDCQD7wJOeS4ukfDp8ZBoks5uMJPpgaJpZM4VojOF
.

Option A or B?


Re-evaluate chosen keywords and symbols

Many of ours are just lox's with no deliberate thought given to them. e.g. super.

Trying out https://www.patrick-wied.at/projects/heatmap-keyboard/ with the sample scripts is interesting

Fun vs proc, would open up fun to mean pure if desired.

closed duplicate #153
test and testcase don't make sense,
fun, pure, local, are a bit messy, consider proc, vs fn, vs meth


correct handling of deletion

Description
We use the deletion for user and groups.
The result are incorrect on a ansible view.
If a group was there and we try to delete, there should the "changed" be true (not false like current).
If a group does not exists and we try to delete, the "changed" result should be false (and not failed like current).
Expected behavior

Environment
Ansible version:

Module version:

OS:

Configuration Files

How to Reproduce

Error and Debug Output

Additional Notes

References

please reopen - group are just one part - missing user

Hello!
We fixed the user deletion too, but in another PR: https://github.com/ionos-cloud/module-ansible/pull/33
The new version will be available in a few minutes in Ansible Galaxy too.
Please let me know if there is still the need to reopen the issue.
Thank you!


Using Mizan for Argos Translate

I'm using Mizan to train an Argos Translate Persian model thanks!

Glad to hear that!


Move EmailAddress & UserRedirect into models/user/

As title

Codecov Report

Merging #17607 (b127999) into main (30515f2) will increase coverage by 0.01%.
The diff coverage is 48.27%.

:exclamation: Current head b127999 differs from pull request most recent head ee36699. Consider uploading reports for the commit ee36699 to get more accurate results

@@            Coverage Diff             @@
##             main   #17607      +/-   ##
==========================================
+ Coverage   45.48%   45.50%   +0.01%
==========================================
  Files         793      795       +2
  Lines       88846    88861      +15
==========================================
+ Hits        40416    40433      +17
+ Misses      41918    41912       -6
- Partials     6512     6516       +4

Impacted Files
Coverage Δ

models/db/error.go
0.00% <0.00%> (ø)

models/error.go
38.47% <ø> (-1.04%)
:arrow_down:

models/issue_comment.go
51.60% <0.00%> (ø)

models/issue_dependency.go
63.76% <0.00%> (ø)

models/issue_reaction.go
82.87% <0.00%> (ø)

models/lfs_lock.go
57.14% <0.00%> (ø)

models/notification.go
64.71% <0.00%> (-1.44%)
:arrow_down:

models/repo_avatar.go
35.78% <0.00%> (ø)

models/repo_collaboration.go
57.89% <0.00%> (ø)

models/repo_generate.go
15.00% <0.00%> (ø)

... and 126 more

Continue to review full report at Codecov.

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

make L-G-T-M work


Add UIViewController+UIStoryboardExtensions tests

Checklist

[X] I checked the Contributing Guidelines before creating this request.
[X] I have only one commit in this pull request.
[] New extensions support iOS 8 or later.
[] New extensions are written in Swift 3.
[] I have added tests for new extensions, and they passed.
[X] Pull request was created to master head branch.
[] All extensions have a clear comments explaining their functionality, all parameters and return type in English.
[] All comments headers have the word SwifterSwift: before description.

Summary of Pull Request:

Adds complete testing for UIViewControllerExtensions & UIStoryboardExtensions
Added a new file TestStoryboard to the SwifterSwiftTests target

T~T I tried to cheat. I'll fix it. I'm curious why my tests always pass in Xcode and fail in Travis.

@omaralbeik What's up with UIImageViewExtensions being impacted files here?


AgileConfig does not take effect automatically.

I used agileconfig to implement the gateway by referencing the ABP demo. When agileconfig configuration items were updated, the gateway would automatically take effect. Now, with the Carp gateway, it doesn't automatically take effect, and I need to restart the service. Is it possible to add this functionality?

Version 0.4.8 can dynamically refresh Carp by monitoring IConfiguration changes

Please give us feedback if the problem is solved

I've just updated to version 0.5.7, and after testing, it's confirmed to support the synchronization of gateway configurations after AgileConfig updates. Great job!

When I updated to version 1.0.1, this issue reappeared. A restart is required to reload. The code used for the configuration center is as follows:
builder.Host.ConfigureAppConfiguration((context, config) =>
   {
       //Injection AgileConfig Configuration Provider
       var configuration = config.Build();
       var agileConfigEnabled = configuration["AgileConfig:IsEnabled"];
       if (string.IsNullOrEmpty(agileConfigEnabled) || bool.Parse(agileConfigEnabled))
       {
           config.AddAgileConfig(new AgileConfig.Client.ConfigClient(configuration));
       }
   });

When I updated to version 1.0.1, this issue reappeared. A restart is required to reload. The code used for the configuration center is as follows:
builder.Host.ConfigureAppConfiguration((context, config) =>
   {
       //Injection AgileConfig Configuration Provider
       var configuration = config.Build();
       var agileConfigEnabled = configuration["AgileConfig:IsEnabled"];
       if (string.IsNullOrEmpty(agileConfigEnabled) || bool.Parse(agileConfigEnabled))
       {
           config.AddAgileConfig(new AgileConfig.Client.ConfigClient(configuration));
       }
   });

I will trigger a hot update when using appsetters. json on my end
Using Apollo testing, it was found that there is a delay in triggering hot updates due to the difference in Apollo polling time
Please observe if there is also a delay in triggering hot updates in AgileConfig
Please confirm if AgileConfig triggered Configuration- ChangeToken.OnChange

After my testing, using apppresets.json will trigger a hot update

When using Apollo, it was found that there was a delay in triggering hot updates due to the difference in Apollo polling time

Please observe if there is also a delay in triggering hot updates in AgileConfig

Please confirm if AgileConfig triggered Configuration- ChangeToken.OnChange

After testing AgileConfig, it also triggered a hot update

Please upgrade the AgileConfig client to the latest version

If it still doesn't work, please send me a demo

I retested and found that it has indeed taken effect. It's likely that there was a delay as you described, and the previous configuration changes hadn't updated in time for the test. Thank you.


Ruby 2.x compatability?

I saw this at the top of the README:
"Note: This gem only runs on Ruby version 1.9.+"
Is this still true?  What is the nature of the incompatibility, and do you know if it is going to get fixed soon?  I'd really like to use this gem, but we run Ruby 2.1.1.

I verified that this gem works with MRI 2.2. I also added a few non-critical currency updates as  #11.

Thanks nerab!  I added TravisCI and verified that the gem works with MRI 2.2.


[404] Add fragments page specific to 404

Is this a BUG REPORT or FEATURE REQUEST?:
feature
What happened:
Currently the 404 fragment isn't showcased or documented within exampleSite.
What you expected to happen:
Showcase and document 404.

404 page can't be shown anywhere except /404.html which is not a good place to showcase it. We can put a screenshot though. What do you think?

Explanation + screenshot + code should be ok I guess.


:seedling: bump catalogd to v0.11.0

Description

Bumps catalogd --> v0.11.0
Bumps kind to v0.20.0 and ensures we are using a 1.28 node image for testing

Reviewer Checklist

[ ] API Go Documentation
[ ] Tests: Unit Tests (and E2E Tests, if appropriate)
[ ] Comprehensive Commit Messages
[ ] Links to related GitHub Issue(s)

/hold to give @joelanford a chance to reply to comments.


NullPointException when deserializing null responses using Pipeline

Description
When calling syncAndReturnAll() on a pipeline with a get call to a non-existing key, the following exception is thrown:
Caused by: java.lang.NullPointerException
  at java.lang.String.<init>(String.java:515)
  at redis.clients.util.SafeEncoder.encode(SafeEncoder.java:28)
  at redis.clients.jedis.BuilderFactory$5.build(BuilderFactory.java:55)
  at redis.clients.jedis.BuilderFactory$5.build(BuilderFactory.java:58)
  at redis.clients.jedis.Response.get(Response.java:27)
  at redis.clients.jedis.Pipeline.syncAndReturnAll(Pipeline.java:42)

Cause
The basic type builders on BuilderFactory are missing a null check before converting the data.
Quickfix
A not-so-elegant quick fix can be made on Response.get() (as opposed to adding the null checks):
public T get() {
    // ...
    if (!built) {
        response = data == null ? null : builder.build(data); // don't convert unless we have data
        this.data = null;
        built = true;
    }
    return response;
}

Code to reproduce
Jedis connection = ...

// key "poo" must not exist
Pipeline p = connection.pipelined();
p.get("poo");
p.sync(); // works nicely, since response is not read

connection.set("poo", "pie");
p = connection.pipelined();
p.get("poo");
p.syncAndReturnAll(); // Works, since key is set

connection.del("poo");
p = connection.pipelined();
p.get("poo");
p.syncAndReturnAll(); // Throws NPE building result

Other info
Using 2.0.0 from maven central repo.

thanks a lot for reporting this.
this was fixed by #158


changing error message and error code

Description
[changing error message and error code. Currently error message is default to the 500 error which is not ideal. So we need to set the correct error which we are receiving from the downstream. ]
Issues Resolved
[List any issues this PR will resolve]
Check List

[ ] New functionality includes testing.

[ ] All tests pass

[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[ ] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@ylwu-amzn can you please make sure to fill in the fields in the PR description? e.g. Description, Issues resolved etc..

@dhrubo-os can you please make sure to fill in the fields in the PR description? e.g. Description, Issues resolved etc..

Added description.


Unable to use clear() method from ExperimentClient

Hi team, we want to integrate Experiment in our project but noticed that we cannot clear the cache for the experiments.
In the docs it says:
/// You can call clear after user logout to clear the variants in cache and storage.
experiment.clear()

But the clear() method is not present in the ExperimentClient protocol definition.
It's just in the DefaultExperimentClient implementation, which is internal in the package and unable to access from the consumer.
Can you do a fix to make it available for the consumer?
Thanks in advance

Fixed in version 1.9.1, thanks!


first version of OperationalInsights swagger based on the hydra spec

This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.
@fearthecowboy , @olydis , @amarzavery , just submitted a new iteration. Could you guys take a look?
PR information

[x ] The title of the PR is clear and informative.
[x ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
[x ] Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
[ ] If applicable, the PR references the bug/issue that it fixes.
[x ] Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

[x ] I have read the contribution guidelines.
[ x] My spec meets the review criteria:

[x ] The spec conforms to the Swagger 2.0 specification.
[x ] Validation errors from the Linter extension for VS Code have all been fixed for this spec. (Note: for large, previously checked in specs, there will likely be many errors shown. Please contact our team so we can set a timeframe for fixing these errors if your PR is not going to address them).
[x ] The spec follows the patterns described in the Swagger good patterns document unless the service API makes this impossible.

This change is

Hi @xizhamsft, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

It looks like you're working at Microsoft (xizha). If you're full-time, we DON'T require a contribution license agreement.

If you are a vendor, DO please sign the electronic contribution license agreement. It will take 2 minutes and there's no faxing! https://cla.azure.com.

TTYL, AZPRBOT;

Greetings @xizhamsft!
Joahannes (@olydis), Deepak (@dsgouda) and I (@fearthecowboy) are the assigned reviewers for your swagger spec. (we're taking over for the great and powerful @amarzavery, who is really busy :D )
You can think of as your sherpas to guide your journey to acceptance thru this process :D
If you have any questions or need some help with our review, feel free to ask us anything.

Hey @xizhamsft
We're going to end up doing this review in several passes. Since it's a new spec, we'll find lots and lots of things that we can do to make the quality of code for the SDK and the quality of documentation a great experience for our customers.
Currently, there's a lot of issues that we've marked on a few items, where it really applies to a lot of the swagger spec. (things like min/max values or lengths, or regex patterns for parameter validation, and much better documentation text)
Rather than be terribly pedantic on all the fields, we'll give you a bit of time to resolve some of this and then we can continue the review a bit deeper.
thanks!

Note that I have added further comments:

https://github.com/Azure/azure-rest-api-specs/pull/662#discussion_r94628685
https://github.com/Azure/azure-rest-api-specs/pull/662#discussion_r94629554

No modification for Ruby

No modification for Python

No modification for NodeJS


Map base is counting plain as layer to be sent to windshaft

https://github.com/CartoDB/cartodb.js/blob/c8d237cd2c9b009b011853016e08e5a375dd53fa/src/windshaft/map-base.js#L232
Adding plain there should do it. Would fix https://github.com/CartoDB/d3.cartodb/issues/177

Fixed in #1252


[Menu] zDepth - hide in docs, add warning, remove usages

[x] PR has tests / docs demo, and is linted.
[x] Commit and PR titles begin with [ComponentName], and are in imperative form: "[Component] Fix leaky abstraction".
[x] Description explains the issue / use-case resolved, and auto-closes the related issue(s) (http://tr.im/vFqem).

Paper was removed from Menu in #3559, but zDepth remained in the prop docs with its current (incorrect) description. This PR hides the prop, updates the (now internal) comment, adds a warning, and removes unneeded zDepth={0} usage from other components.

Thanks. :mag_right: Fixed.

Looks good, thanks a lot :grin:


Session: Make multi-tab aware

Describe the feature you would like to see added
Add a setting that makes Session multitab away similar to IdlePoller in PrimeFaces.
Use localStorage as the share variable that all the tabs look at.
cc @fcorneli

Got it working!

@melloware Reviewed your code. Perfect as usual.

@melloware Where do you find the time? :) Tell me the secret please? You live in another universe where you have more than 24 hours in a day? :)

I always tell people "I am good at multi-tasking"

Why not enable it per default? I see little reason why you won't want this per default.

I only followed the IdlePoller's example of it false by default but it seems like it should be the default! I will update


packZpk is adding deployment scripts into scripts/scripts directory

It is creating scripts directory inside another scripts directory which makes Zend Server unable to unpack and execute deployment scripts like post_stage.php
This issue is probably caused by pack method of ZpkInvokable where it calls
$zpk->addFile($fullPath, $this->fixZipPath($baseDir.$path));
For scripts directory it tries to do
$zpk->addFile($fullPath, $this->fixZipPath('scripts/'.'scripts/post_stage.php'));

I created a pull request for this issue and it now works for me..
I didn't see a fix in the latest release or dev version, so I'm not sure if this was fixed yet
https://github.com/zend-patterns/ZendServerSDK/pull/56


Any way to make this working for other phones?

For example my girlfriend has a Huawaii Honor Holly and alo got the deadzone now.
Would there be a way you release a fix for those?

I'm sorry, but this repository is no longer maintained and the problem with this particular phone could be anything unrelated to N4's issue.


Update protect-personal-data-azure.md

Delete reference to medical information and reverse order of "customer and employee" at the request of Eric Tierling.

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot

@v-debshi : Thanks for your contribution to the Azure documentation! The author, @Barclayn, has been notified to review your proposed change.

#sign-off


"App settings" is now "Settings"

https://docs.microsoft.com/en-us/powerapps/developer/component-framework/component-framework-for-canvas-apps#enable-powerapps-component-framework-feature
At step 6, "App settings" is now "Settings" on the UI.

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

ID: e8124234-fccb-85af-9ee8-13729326c727
Version Independent ID: d53c2fc1-dd63-eee4-26a7-22715f27b943
Content: PowerApps component framework for canvas apps - PowerApps
Content Source: powerapps-docs/developer/component-framework/component-framework-for-canvas-apps.md
Service: powerapps
GitHub Login: @Nkrb
Microsoft Alias: nabuthuk

@KoBe321  Thanks for the feedback. We have updated the docs with the correct information and pushed to live. Closing the issue.


APM server does not start with default configuration

Describe the bug
While setting up elastdocker today, I noticed that the recently added APM server logs an error about the config file having the wrong permissions. I was able to fix this by running chmod g-w apm-server/data/apm-server.yml, this command could be included into the setup scripts. There is an alternative method via env var described in https://github.com/elastic/beats/issues/18858.
To Reproduce
Spin up the default v3.2.0 elastdocker stack.
Expected behavior
APM server starts without errors.
Screenshots
$ sudo docker compose up -d && sudo docker compose logs -f
[+] Running 6/6
 ⠿ Network elastic                      Created                                                                                0.1s
 ⠿ Volume "elastic_elasticsearch-data"  Created                                                                                0.0s
 ⠿ Container elastic-apm-server-1       Started                                                                                1.8s
 ⠿ Container elastic-elasticsearch-1    Started                                                                                1.2s
 ⠿ Container elastic-kibana-1           Started                                                                                1.6s
 ⠿ Container elastic-logstash-1         Started                                                                                1.9s
elastic-logstash-1       | Using bundled JDK: /usr/share/logstash/jdk
elastic-logstash-1       | OpenJDK 64-Bit Server VM warning: Option UseConcMarkSweepGC was deprecated in version 9.0 and will likely be removed in a future release.
elastic-apm-server-1     | Exiting: error loading config file: config file ("apm-server.yml") can only be writable by the owner but the permissions are "-rw-rw-r--" (to fix the permissions use: 'chmod go-w /usr/share/apm-server/apm-server.yml')
elastic-apm-server-1 exited with code 0
elastic-apm-server-1     | Exiting: error loading config file: config file ("apm-server.yml") can only be writable by the owner but the permissions are "-rw-rw-r--" (to fix the permissions use: 'chmod go-w /usr/share/apm-server/apm-server.yml')
elastic-apm-server-1     | Exiting: error loading config file: config file ("apm-server.yml") can only be writable by the owner but the permissions are "-rw-rw-r--" (to fix the permissions use: 'chmod go-w /usr/share/apm-server/apm-server.yml')
elastic-apm-server-1     | Exiting: error loading config file: config file ("apm-server.yml") can only be writable by the owner but the permissions are "-rw-rw-r--" (to fix the permissions use: 'chmod go-w /usr/share/apm-server/apm-server.yml')
elastic-apm-server-1 exited with code 1
[...]

Additional context
I'm running on Ubuntu Server 20.04, Docker version 20.10.21, Docker Compose version 2.12.2.

Hello @dama-de ,
Thanks for reporting, unfortunately, I was not able to reproduce it as per the attached logs.
I tested it by cloning the repository and executing make setup then docker compose up -d

Is there anything missing in your steps that could help us reproduce the issue and identify the root cause?

I'm getting the same error. I also ran make setup prior to running docker compose up
`PS C:\Projects\elastdocker> docker compose up
[+] Running 5/5

Network elastic                    Created                                                          0.0s
Container elastic-apm-server-1     Created                                                          0.2s
Container elastic-kibana-1         Created                                                          0.2s
Container elastic-elasticsearch-1  Created                                                          0.2s
Container elastic-logstash-1       Created                                                          0.2s
Attaching to elastic-apm-server-1, elastic-elasticsearch-1, elastic-kibana-1, elastic-logstash-1
elastic-logstash-1       | Using bundled JDK: /usr/share/logstash/jdk
elastic-logstash-1       | OpenJDK 64-Bit Server VM warning: Option UseConcMarkSweepGC was deprecated in version 9.0 and will likely be removed in a future release.
elastic-apm-server-1     | Exiting: error loading config file: config file ("apm-server.yml") can only be writable by the owner but the permissions are "-rwxrwxrwx" (to fix the permissions use: 'chmod go-w /usr/share/apm-server/apm-server.yml')
elastic-apm-server-1 exited with code 1
elastic-apm-server-1     | Exiting: error loading config file: config file ("apm-server.yml") can only be writable by the owner but the permissions are "-rwxrwxrwx" (to fix the permissions use: 'chmod go-w /usr/share/apm-server/apm-server.yml')
elastic-apm-server-1 exited with code 1
elastic-apm-server-1     | Exiting: error loading config file: config file ("apm-server.yml") can only be writable by the owner but the permissions are "-rwxrwxrwx" (to fix the permissions use: 'chmod go-w /usr/share/apm-server/apm-server.yml')
elastic-apm-server-1 exited with code 1
elastic-apm-server-1     | Exiting: error loading config file: config file ("apm-server.yml") can only be writable by the owner but the permissions are "-rwxrwxrwx" (to fix the permissions use: 'chmod go-w /usr/share/apm-server/apm-server.yml')
elastic-apm-server-1 exited with code 1
elastic-apm-server-1     | Exiting: error loading config file: config file ("apm-server.yml") can only be writable by the owner but the permissions are "-rwxrwxrwx" (to fix the permissions use: 'chmod go-w /usr/share/apm-server/apm-server.yml')
elastic-apm-server-1 exited with code 1
elastic-apm-server-1     | Exiting: error loading config file: config file ("apm-server.yml") can only be writable by the owner but the permissions are "-rwxrwxrwx" (to fix the permissions use: 'chmod go-w /usr/share/apm-server/apm-server.yml')
elastic-apm-server-1 exited with code 1
elastic-apm-server-1     | Exiting: error loading config file: config file ("apm-server.yml") can only be writable by the owner but the permissions are "-rwxrwxrwx" (to fix the permissions use: 'chmod go-w /usr/share/apm-server/apm-server.yml')
elastic-apm-server-1 exited with code 1`

Have you tried to fix the permission on the local config file as the error message suggests?

@mostafahussein cannot update the permissions of local config
i tried
docker compose exec apm-server bash
or
docker compose exec apm-server ps aux
it responds with:
Error response from daemon: Container 7d427a3cdbc4c5efd69df1b770bfd3d790ba604b9c7d30c99c9bb2c006390c71 is restarting, wait until the container is running
the container status is Restarting (1) x seconds ago forever

By the local config, I mean this file https://github.com/sherifabdlnaby/elastdocker/blob/main/apm-server/config/apm-server.yml, you don't need to enter the container to update the permission, just modify the original file and it will be mounted by docker compose, lets see if this will fix the issue or not

Fixed
Thank you ya @mostafahussein

I tried modifying the original file by adding a benign white-space on windows, and that didn't work
Needles to say, I can't modify the file permission by running 'chmod go-w /usr/share/apm-server/apm-server.yml' because that's not possible in windows.
So this is still an issue for me.

So I think found a workaround... I was able to resolve this error by adding command: --strict.perms=false for the apm-server service. Read this post for more info: https://github.com/elastic/apm-server/issues/3042
So for example:
apm-server:
    image: elastdocker/apm-server:${ELK_VERSION}
    build:
      context: apm-server/
      args:
        ELK_VERSION: $ELK_VERSION
    command: --strict.perms=false
    restart: unless-stopped
    ports:
      - "8200:8200"
    volumes:
      - ./apm-server/config/apm-server.yml:/usr/share/apm-server/apm-server.yml:r
    environment:
      ELASTIC_USERNAME: ${ELASTIC_USERNAME}
      ELASTIC_PASSWORD: ${ELASTIC_PASSWORD}
      ELASTICSEARCH_HOST_PORT: https://${ELASTICSEARCH_HOST}:${ELASTICSEARCH_PORT}
      ELASTIC_APM_SECRET_TOKEN: ${ELASTIC_APM_SECRET_TOKEN}
    secrets:
      - source: elastic.ca
        target: /certs/ca.crt
      - source: apm-server.certificate
        target: /certs/apm-server.crt
      - source: apm-server.key
        target: /certs/apm-server.key


Fix conflicting shortcut commands between PearAI submodule

I encountered one so far.
Cmd+T should open a window to type within the text editor (but it opens a command pallete item instead). I believe cursor changed this to Cmd+K
We should also default to prioritizing submodule / extensions shortcut definitions above the core one

Yeah this should be fine actually


Staking. Incorrect value on the max button

Available WARD 0.99

Fixed in https://github.com/warden-protocol/wardenprotocol/pull/882


Usage of magic values to specify known metadata instead of static types

Specifying magic strings like "HashKey" to populate data strike me as an odd choice. Why not expose compile-time types to encode this (and other special types) rather than requiring they be hashed to a map all the time? In addition, it looks like the implementation uses a vanilla map as opposed to an unordered map.

Most of the hard coded strings in individual service clients are from code that is generated from the models. Do you have a specific file in mind that we could have a more fruitful conversation about?
As to using a hash map instead of an RB Tree, that is a whole other long optimization argument that probably wouldn't be productive on this forum. We did think about it and decided against it. We will certainly reevaluate this decision as the api grows and changes.

Closing pending more info.

Now that I think about it this may be a more actionable issue. Is your concern that the metadata for S3 is a string string map instead of keyed by some constants?
If so, the reason that is what it is, is that s3 has not defined an enumeration of acceptable metadata types for the generator to pick up and use. If that is the case, then I can see if we can update the service definitions for you. I'll make some inquiries.

Yea that's right, and this is true for other services like DynamoDB as well.

One thing to remember, is that these definitions come straight off of the api definition. The clients are "dumb" low-level clients. I think these concerns would be more workable in some higher-level apis. For example, we could add easily add some metadata constants to the transfer client.


fix(web): use bearer token instead of sas token for downloads

Describe your changes
Instead of creating a SAS token, use the bearer token from the user identity to download the blob content. We need to do this through the SDK rather than the public URL since the public URL only supports SAS tokens in query strings.
This was an issue because SAS tokens have to be scoped to a storage account (not just a container), but the AD groups which CAT team belong to only have RBAC roles assigned at the container level. More detail in the comments on JIRA.
Issue ticket number and link
BOAS-834
Type of change 🧩

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation update
[ ] Other (please explain in the description section above)

Checklist before requesting a review

[ ] I have performed a self-review of my own code
[ ] I have double checked this work does not include any hardcoded secrets or passwords
[ ] I have made corresponding changes to the documentation
[ ] I have provided details on how I have tested my code
[ ] I have referenced the ticket number above
[ ] I have provided a description of the ticket
[ ] I have included unit tests to cover any testable code changes

lgtm!


Replace old macros with consistent NGEN_WITH_FOO

Resolves #813
Additions

Removals

Changes

Testing

Screenshots
Notes

Todos

Checklist

[ ] PR has an informative and human-readable title
[ ] Changes are limited to a single goal (no scope creep)
[ ] Code can be automatically merged (no conflicts)
[ ] Code follows project standards (link if applicable)
[ ] Passes all existing automated tests
[ ] Any change in functionality is tested
[ ] New functions are documented (with a description, list of inputs, and expected output)
[ ] Placeholder code is flagged / future todos are captured in comments
[ ] Project documentation has been updated (including the "Unreleased" section of the CHANGELOG)
[ ] Reviewers requested with the Reviewers tool :arrow_right:

Testing checklist (automated report can be put here)

Target Environment support

[ ] Linux

Grrr, builds failing due to include paths for much of the codebase not reaching NGenConfig.h. Gotta play with CMake more to figure that out.


One-Attestation-API Lab Proposal

This lab proposes to create a single API to handle attestations.
Attestations are a crucial mechanism to establish trust in hardware-based trusted execution environments (TEEs).
Today, multiple attestation mechanisms are available (e.g., SGX-EPID, SGX-DCAP, TDX-DCAP).
This proposal aims to create a single abstraction for the generation and verification of hardware-based attestations.
The abstraction can benefit, and avoid redundant implementations in, multiple projects (e.g., Fabric Private Chaincode, Private Data Objects)
that use TEEs to enhance software integrity and confidentiality.
--
@mbrandenburger Please acknowledge sponsorship.

The PR seems to be in "Draft" stage, it seems it is still in progress.

How this lab is related to Fabric private chaincode & Private data objects? Is this lab going to support these labs projects ? Also, we had Avalon project(This project is currently in end of life  state) how it will  be helpful for that projetc as well

@bvavala this needs to be moved from draft to ready for review so we can move forward.

@bvavala this needs to be moved from draft to ready for review so we can move forward.

@ryjones there is still some compliance work in progress. I expect this will take a couple more weeks, before I can move forward and answer the questions that were raised. Meanwhile, I am ok to keep this PR open, or to close it and reopen it later.

We decided not to move forward with this lab proposal. The work will continue in existing repos.


Thread 5: Fatal error: Unable to bridge NSNumber to Int

I'm getting the following error on WeatherDemo.

Fixed.


Adding Open Router inference Example

Simple example utlizes Openrouter API to access Open source models for inference. Utilizing Json mode within Instructor, we can get Json structured output.
OpenRouter - https://openrouter.ai/

Summary by CodeRabbit

New Features

Integrated an AI client for enhanced user interaction within the app.
Introduced user detail validation to ensure accurate user data handling.

Refactor

Streamlined the configuration of the AI client by setting global variables for API key and base URL.

Documentation

Added code comments for clarity on the new AI client integration process.

Take a look at #225 maybe we shuold add some tests or change the conftest to detect open router too

no reason it shouldnt just look like this
https://github.com/jxnl/instructor/blob/main/examples/patching/patching.py
but with client = instructor.patch(OpenAI(...), mode=Mode.JSON)


ci: add release please

What does this pull request change?
Why is this pull request needed?
Issues related to this change
closes #120

TODO test if publishing to pypi works


the progrom crash unexpectly

Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (go version)?
go version go1.9 linux/386
Does this issue reproduce with the latest release?
no reproduce in go 1.7.3 linux/386
What operating system and processor architecture are you using (go env)?
GOARCH="386"
GOBIN=""
GOEXE=""
GOHOSTARCH="386"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/usr/local/gowork:/root/italk_go"
GORACE=""
GOROOT="/usr/local/go"
GOTOOLDIR="/usr/local/go/pkg/tool/linux_386"
GCCGO="gccgo"
GO386="sse2"
CC="gcc"
GOGCCFLAGS="-fPIC -m32 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build129125825=/tmp/go-build -gno-record-gcc-switches"
CXX="g++"
CGO_ENABLED="1"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
What did you do?
package main
import (
"fmt"
"sync/atomic"
)
type simple_service_manager struct {
round_index        uint16
peer_idx_base     uint64
}
func (sm *simple_service_manager) get_service_idx(offset uint16) uint64 {
return atomic.AddUint64(&sm.peer_idx_base, uint64(1<<16)) + uint64(offset)
}
func main() {
sm := &simple_service_manager{}
var port int = 9900
fmt.Println(sm.get_service_idx(uint16(port)))
}
if put peer_idx_base to the first member of simple_service_manager,  it can run normally
What did you expect to see?
Program run and exist normally
What did you see instead?
The program is crash

Read the last paragraph on this page: https://golang.org/pkg/sync/atomic/

On both ARM and x86-32, it is the caller's responsibility to arrange for 64-bit alignment of 64-bit words accessed atomically. The first word in a variable or in an allocated struct, array, or slice can be relied upon to be 64-bit aligned.


show_with_html in list-view on aggregation.sum gives no option to enter the HTML anywhere.

Describe the bug
show_with_html in list-view gives no option to enter the HTML anywhere for a Aggretation>Sum amount .
It works okay in on string fields where there appears a textbox to enter the HTML-code.
But I want to add a Euro sign tot the aggregation result.

It seems that #2311 does not solve this. Is is even worse. All options - like ratings-  etc have dissapeared in the new list builder

Ok, i need to add fieldviews to aggregations in the builder. i guess we used to have this for List but never for Show

@HFolkertH aggregation fieldview configuration implemented in #2342. It should also be more correct now because Count aggregation fieldviews are chosen as Integers. I have updated saltcorn.com.

It works. Thanks!

I thougt it worked fine but I made a mistake.
Show-with-html only works for the Aggregation.Count but not for sum/avg/max/min of a floating number (like  amounts )

Show-with-HTML in the list-builder for aggregation sum/min/max/avg does not work. When i open the list-view the HTML is totaly ignored. If it maters: the total fiels is a floating number.

It should display some stupid text on the Total column but it shows the correct aggregated value instead.

But when I change the aggregate from sum to count the  HTML text is correctly shown!

yes

fixed in #2351

Confirmed. Thanks


Better solved the dropout problem on the latent space to still apply …

…dropout to further layers

Version control issue, merging aborted


Singularity Fixes, Part 3

About the PR
This may or may not fix shader intensity issues.
It should properly fix issues with the singularity deciding to wander off into a corner.
Screenshots
This is the state of the singularity at level 3 under this PR.
I've also worked out a way that should let me sanely adjust these settings - get the singulo to a particular level, then delete the singularity component (to keep it in the current state) and install a "toy singularity" client component to control the intensity and falloff values.

Changelog
:cl:

fix: Render scale (low viewport resolution) will no longer alter singularity intensity. This might reduce effect intensity, I am not sure.
fix: Singularity should actually not wander off into a corner this time.
fix: Singularity generators and substations should be easier to pull around through single-tile spaces.

So I'm turning this into a general singulo 'stage 2' fixes thing because there were apparently a >1 amount of issues with the fixes

so, apparently, you can get radiation damage in the PA room.
Do I fix it in this PR by moving the singularity containment further away from the PA room, or...?

so, apparently, you can get radiation damage in the PA room.
Do I fix it in this PR by moving the singularity containment further away from the PA room, or...?

I mean, that's how it should really be. We should start working on something to protect against/block rad damage instead imo

Another issue that has cropped up is that the singularity generator doesn't fit through various places. Same issue occurs with substations. Bounding boxes are too big.

this probably now covers all the issues, unless I get made aware of any more of them

If you want you could add the BaseMachine parent to the SMES and Substation so that we can get less bugs happening from missing components.
Then also tweak BaseMachine to be small enough to fit through doors.

BaseMachine pulls in PowerReceiver, which I'm not sure is a great idea. Do I split it up to have a base prototype with no PowerReceiver?

See: https://github.com/20kdc/space-station-14/pull/1

BaseMachine pulls in PowerReceiver, which I'm not sure is a great idea. Do I split it up to have a base prototype with no PowerReceiver?

Yeah, maybe split it into BaseMachine and BaseMachinePowered.

To be clear, I have a commit where the split is between BaseMachine and BaseMachineUnpowered Is that acceptable or do I explicitly need to use BaseMachinePowered instead?

It doesn't matter too much but i prefer having things that add components add to the name and not the other way around.


Astronomy ENUM value undefined

The server is returning an error while using ENUMS. When I try to access MyEnum.FOO it just throws an undefined error. I console.log the class and it was printed out, the importing is also fine.
The ENUM
import { Enum } from 'meteor/jagi:astronomy';

const PlaceholderTypes = Enum.create({
  name: 'PlaceholderTypes',
  identifiers: { NORMAL: 1, SYNC: 2 }
});

module.exports = {
  PlaceholderTypes
}

The implementation (with the imported class)
Placeholder = Class.create({
  name: 'Placeholder',
  fields: {
    // ...
    type: {
      type: PlaceholderTypes,
      default () {
        return PlaceholderTypes.SYNC
      }
    }
  },
});

The error
TypeError: ["Placeholder" class]["fields" property]["type" field] Type does not exist

Any help would be much appreciated.

Maybe it's has something to do with the field name which is type. I don't think that I reserved this keyword but it might be a bug. Please check out if changing field's name helped. If not please create simple reproduction with what you've posted here and I will take a look at it.

Hey, Jagi. You were right. The type: {...} keyword was reserved. This would be a nice-to-have feature if we can use type as a field name in future releases. Thank you for taking the time to look into it.

Ok, so I will probably have to fix it because it shouldn't be reserved. In fact the type field used for inheritance is only a default value and any field can be used for inheritance. So there is no need for making it reserved. So I will fix it in the next bugfix version.

I've been trying to solve the problem and I've noticed that the type keyword is not reserved. Actually you have a bug in your code in type exports. It should be:
import { Enum } from 'meteor/jagi:astronomy';

const PlaceholderTypes = Enum.create({
  name: 'PlaceholderTypes',
  identifiers: { NORMAL: 1, SYNC: 2 }
});

export default PlaceholderTypes;

and later in the class definition:
import PlaceholderTypes from './path/to/type/file/PlaceholderTypes';

// Class definition goes here...


Optionally resize images client-side before uploading

See:
https://stackoverflow.com/questions/23945494/use-html5-to-resize-an-image-before-upload#24015367

Added to v0.4.x


Create custom-configuration.md

Adding public documentation for how to provide custom config files to customize AppCAT code analysis
Summary
Fixes #Issue_Number (if available)

Internal previews

📄 File
🔗 Preview link

docs/azure/migration/appcat/custom-configuration.md
How to customize analysis with run config

ping @alexwolfmsft @CamSoper for review

I'll give this a review Friday. Thanks, @mckennabarlow!


check-aggregate as a plugin

Currently check-aggregate.rb is in the deprected repo, and as far as I can tell it's the only decent aggregate check plugin. Can we build a gem for it? I'm happy to help if we can get a repo set up.

@jaxxstorm It's in https://github.com/sensu-plugins/sensu-plugins-sensu