Registry my micros Service with euraka failed. pls i need help i have been on this issue for 2 days

2016-07-20 10:02:42.165 ERROR 10476 --- [pool-4-thread-1] com.netflix.discovery.DiscoveryClient    : DiscoveryClient_BOOKMARK-SERVICE/<IP_ADDRESS> - was unable to refresh its cache! status = java.net.UnknownHostException: registry @dsyer pls help

com.sun.jersey.api.client.ClientHandlerException: java.net.UnknownHostException: registry
        at com.sun.jersey.client.apache4.ApacheHttpClient4Handler.handle(ApacheHttpClient4Handler.java:184)
        at com.sun.jersey.api.client.filter.GZIPContentEncodingFilter.handle(GZIPContentEncodingFilter.java:120)
        at com.netflix.discovery.EurekaIdentityHeaderFilter.handle(EurekaIdentityHeaderFilter.java:28)
        at com.sun.jersey.api.client.Client.handle(Client.java:648)
        at com.sun.jersey.api.client.WebResource.handle(WebResource.java:680)
        at com.sun.jersey.api.client.WebResource.access$200(WebResource.java:74)
        at com.sun.jersey.api.client.WebResource$Builder.get(WebResource.java:507)
        at com.netflix.discovery.DiscoveryClient.getUrl(DiscoveryClient.java:1567)
        at com.netflix.discovery.DiscoveryClient.makeRemoteCall(DiscoveryClient.java:1113)
        at com.netflix.discovery.DiscoveryClient.makeRemoteCall(DiscoveryClient.java:1060)
        at com.netflix.discovery.DiscoveryClient.getAndStoreFullRegistry(DiscoveryClient.java:835)
        at com.netflix.discovery.DiscoveryClient.fetchRegistry(DiscoveryClient.java:746)
        at com.netflix.discovery.DiscoveryClient.access$1400(DiscoveryClient.java:105)
        at com.netflix.discovery.DiscoveryClient$CacheRefreshThread.run(DiscoveryClient.java:1723)
        at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
        at java.util.concurrent.FutureTask.run(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)
Caused by: java.net.UnknownHostException: registry
        at java.net.Inet6AddressImpl.lookupAllHostAddr(Native Method)
        at java.net.InetAddress$2.lookupAllHostAddr(Unknown Source)
        at java.net.InetAddress.getAddressesFromNameService(Unknown Source)
        at java.net.InetAddress.getAllByName0(Unknown Source)
        at java.net.InetAddress.getAllByName(Unknown Source)
        at java.net.InetAddress.getAllByName(Unknown Source)
        at org.apache.http.impl.conn.SystemDefaultDnsResolver.resolve(SystemDefaultDnsResolver.java:44)
        at org.apache.http.impl.conn.DefaultClientConnectionOperator.resolveHostname(DefaultClientConnectionOperator.java:259)
        at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:159)
        at org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java:144)
        at org.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java:131)
        at org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:611)
        at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:446)
        at org.apache.http.impl.client.AbstractHttpClient.doExecute(AbstractHttpClient.java:863)
        at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:115)
        at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:57)
        at com.sun.jersey.client.apache4.ApacheHttpClient4Handler.handle(ApacheHttpClient4Handler.java:170)
        ... 18 common frames omitted

my service Configure
server:
  port: ${vcap.application.port:8761}

spring:
  application:
    name: registry
  cloud:
    config:
      uri: http://localhost:8888
      fail-fast: true
      password: 37c31fd6-6f09-49fb-bb23-6c72ba668f99
      username: user

eureka:
  instance:
    prefer-ip-address: false
    hostname: localhost

  client:
    registerWithEureka: false
    fetchRegistry: false
    service-url:
       defaultZone: http://${eureka.instance.hostname}:${server.port}/eureka/

  server:
    waitTimeInMsWhenSyncEmpty: 0
  dashboard:
    enabled: true

pls i need help i have  been on this issue for 2 days can someone Help.

Sorry, you lost me. You showed the config from your eureka server. Is that where the log comes from too? It looks like the log is from a client trying to connect to a service on a host called "registry". I guess you might have a problem with the client?

Yes the log is from the client that that is try to connect. I keep getting that error.  @dsyer help.

Maybe the config from the client is more relevant then, if that's where the error is?

thanks it is the configuration from the client. i got it working . i appreciate

hey @seyijava could you maybe remeber what was it that got you running?


Map 2023 Sharepoint Duplicate Fields

User story
As a user, I want duplicate fields (anaesthesia, recovery time, instrument id) to be mapped completely. These fields are procedure-agnostic in the database (with 2 backend fields each) but we want to map them to procedure-specific fields (anaesthesia, recovery time, instrument id).
Acceptance criteria

[ ] Figure out how duplicate fields (ex: Iso_x0020_On, FirstInjectionIsoDuration for anaesthesia duration) map to separate procedures
- [ ] anaesthesia duration: Iso_x0020_On, FirstInjectionIsoDuration
- [ ] anaesthesia level: HPIsoLevel, Round1InjIsolevel
- [ ] workstation_id:  HpWorkStation, WorkStation1stInjection
- [ ] recovery_time : HPRecovery, FirstInjRecovery
- [ ] instrument_id (Nano): NanojectNumberInj10, NanojectNumberInj2
- [ ] instrument_id (Ionto): IontoNumberInj1, IontoNumberInj2
[ ] Is the order of surgeries tracked in a response? and if so, how?
[ ] map for all procedures (injections and fiber implants in burr hole methods, craniotomies, headframes)

Sprint Ready Checklist

[ ] 1. Acceptance criteria defined
[ ] 2. Team understands acceptance criteria
[ ] 3. Team has defined solution / steps to satisfy acceptance criteria
[ ] 4. Acceptance criteria is verifiable / testable
[ ] 5. External / 3rd Party dependencies identified
[ ] 6. Ticket is prioritized and sized

Notes
will need to meet with sharepoint engineers to answer some of these questions

fields to define whether something was during initial or followup surgery added to NSB


[Bug]: perform-action with notify.persistent_notification not work

Requirements

[X] I checked the troubleshooting section in the README to verify that I have the latest Mushroom version.
[X] I did a search to see if there is a similar issue or if a pull request is open.
[X] I have read the state of card mod support (in pin issues) and understand card mod support is not provided in this repository.

Current Behavior
The error is new. It has worked before

Expected Behavior
No response
Steps To Reproduce

Context
/homeassistant/custom_templates/geburtstag.jinja
YAML state
{%- macro gruss() -%}
{{ [
 "Test1",
 "Test2",
 "Test3" ] | random -}}
{% endmacro %}
{{ gruss() }}

Environment
- Browser: Firefox or Chrome
- HA Version: 2024.10.1
- Mushroom: 4.0.7

Anything else?
No response

It's a Home Assistant limitation, template are not supported for perform-action. You can use a script as a workaround.

Is this restriction new? The same code ran before without restriction.

With the exact same code? Using a tap action in the dashboard?

I just checked, and you right, it worked before and it was removed with the latest update : https://github.com/home-assistant/core/pull/122820
This was deprecated for a long time, the proper way to do it is to create a script and call it from the dashboard.


which model weights do you use? gpt-neox slim weights or full weights

Thanks for sharing your great research.
To reproduce the experimental results of KERPLE paper, I want to re-run the kerple code.
I have a question, which model weights do you use? gpt-neox slim weights or full weights. thank you.

Hi,
Thank you for your interest in our work!
We trained the model from scratch. You can refer to this section for details.
Thanks.

Thank you for your reply. Now I know how to get table 3 results of paper
You mentioned that we trained the model from scratch. I have another question.
You mean just download the dataset, and run train.sh to train model from scratch? we do not need download gpt-neox model?(in README_gpt_neox.md, it need download neox model)
thanks very much

Hi,
Sorry for the confusion. To reproduce the results in our paper, you can download the model checkpoints we released here and run test.sh.

Sorry.  I express it not clearly

The first question, I got the answer. Now I know how to  reproduce the table 3 results of paper. Just run test.sh, download checkpoint.
I have another question, the second question.
run train.sh file to train model. This step need download  gpt-neox model ? if need, which model weights should I download ? silm weights or full weights?

thank you very very much

thanks very much.
kerple is a very great research.


TextualInterface: print __conuming before accessors

rdar://80535144

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test

It looks like there's some duplicate logic and we might need to add __consuming in a few more places (or factor out the duplication). In PrintAST::printAccessors():
  // We sometimes want to print the accessors abstractly
  // instead of listing out how they're actually implemented.
...

    if (mutatingGetter) printWithSpace("mutating");

...

and
auto PrintAccessor = [&](AccessorKind Kind) -> bool {
...
if (!PrintAccessorBody) {
...
printMutabilityModifiersIfNeeded(Accessor);

@slavapestov My previous attempt to refactor this into printMutabilityModifiersIfNeeded had failed several tests and fixing them introduces perplexing logics into the common function.


Allow GOAWAY to be sent from handlers after the Http2MultiplexCodec

Motivation:
When a server is load-shedding or preparing to shut-down gracefully, it would be nice to be able to issue a GOAWAY so that existing requests can finish, but new requests are turned away. The Http2FrameCodec seems to have all the correct handling for this, but the Http2MultiplexCodec does not allow for anything other than an Http2StreamFrame to be written. As far as I can tell server developers have no way to send a GOAWAY without extending the Http2MultiplexCodec itself which doesn't seem ideal.
Modification:
Update the write() functionality of the the Http2MultiplexCodec to allow Http2GoAwayFrame and Http2StreamFrame to be written.
Added one test, but feel like there may need to be more, just not sure at which level they need to be added.
My read through of the spec indicates that this shouldn't violate any rules.

LGTM... @Scottmitch @nmittler PTAL

Also maybe @buchgr

Changes Committed.

4.1 (52aecab)
Thanks @exell-christopher !

FYI: I think this was previously possible by writing the GOAWAY to the Channel.parent().


Attempt to making Hashing.swift test deterministic with fixed seed.

What's in this pull request?
Make Hashing.swift deterministic by fixing the seed.

@swift-ci Please test

Apparently I need to investigate this more.  Closing for now.


Remove the n_adapts field from StanHMCAdaptor

I think it's possible to remove the n_adapts field from StanHMCAdaptor to make the interface neater.

Closed by https://github.com/TuringLang/AdvancedHMC.jl/pull/139


Crash with VSCode Insiders on M1 (Extension host terminated unexpectedly)

Please include the language you are using, a screenshot, and copy/pastable example.
With / without open a file, always crash. but disabled the Bracket-Pair-Colorizer-2 extension. it will ok.
My Environment

VS Code Insider 1.53.0
MacBook Air M1

Screenshots

I am also on M1 MacBook and I experience the very same issue with crashing Extension host. The log I was able to record follows:

/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:2084 [[object Object]]Cannot read property 'getRuleStack' of undefined
$onExtensionRuntimeError @ /Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:2084
/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:2084 TypeError: Cannot read property 'getRuleStack' of undefined
	at DocumentDecoration.onDidChangeTextDocument (/Users/[redacted]/.vscode-insiders/extensions/coenraads.bracket-pair-colorizer-2-0.2.0/out/src/documentDecoration.js:42)
	at DocumentDecorationManager.onDidChangeTextDocument (/Users/[redacted]/.vscode-insiders/extensions/coenraads.bracket-pair-colorizer-2-0.2.0/out/src/documentDecorationManager.js:47)
	at /Users/[redacted]/.vscode-insiders/extensions/coenraads.bracket-pair-colorizer-2-0.2.0/out/src/extension.js:30
	at p.fire (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:57)
	at T.$acceptModelChanged (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:87)
	at u._doInvokeHandler (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:90)
	at u._invokeHandler (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:90)
	at u._receiveRequest (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:90)
	at u._receiveOneMessage (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:90)
	at /Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:90
	at p.fire (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:57)
	at g.fire (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:65)
	at /Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:106
	at p.fire (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:57)
	at g.fire (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:65)
	at t._receiveMessage (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:65)
	at /Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:65
	at p.fire (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:57)
	at l.acceptChunk (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:65)
	at /Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:65
	at Socket.E (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:106)
	at Socket.emit (/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/events.js:315)
	at addChunk (/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/_stream_readable.js:295)
	at readableAddChunk (/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/_stream_readable.js:271)
	at Socket.Readable.push (/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/_stream_readable.js:212)
	at Pipe.onStreamRead (/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/internal/stream_base_commons.js:186)
$onExtensionRuntimeError @ /Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:2084


Question: Using a coroutine function within an exception handling statement within a stackful coroutine function

BOOST_BEAST_VERSION 330
MSVC 2022 CMake Project

I am using stackful coroutines.
boost::asio::spawn(
                    acceptor.get_executor(),
                        std::bind(
                            &do_session,
                            boost::beast::tcp_stream(std::move(socket)),
                            doc_root,
                            std::placeholders::_1));

I put an invalid format (non-json string) into boost::json::parse() and threw an exception.
using namespace boost::json;

	try {
		value jsonObj = parse(body);
		myHandler(); // It is not called now because of an exception.
	}
	catch (std::exception e) {
     		send(bad_request(R"({"msg":"bad parameter"})"));  //  --> Crash when calling coroutine function.
     		send(bad_request(R"({"msg":"bad parameter"})"), true);  //  --> This function is fine.
	}

Inside the original send() a coroutine function is used. When I added the ability to use a synchronous function rather than a coroutine and used it, there was no crash.
template<bool isRequest, class Body, class Fields>
        void
            operator()(boost::beast::http::message<isRequest, Body, Fields>&& msg) const
        {
            // Determine if we should close the connection after
            close_ = msg.need_eof();

            // We need the serializer here because the serializer requires
            // a non-const file_body, and the message oriented version of
            // http::write only works with const messages.
            boost::beast::http::serializer<isRequest, Body, Fields> sr{ msg };
            boost::beast::http::async_write(stream_, sr, yield_[ec_]);
        }

        template<bool isRequest, class Body, class Fields>
        void
            operator()(boost::beast::http::message<isRequest, Body, Fields>&& msg, const bool syncParam) const
        {
            close_ = msg.need_eof();

            boost::beast::http::serializer<isRequest, Body, Fields> sr{ msg };
            // boost::beast::http::async_write(stream_, sr, yield_[ec_]);
            boost::beast::http::write(stream_, sr, ec_);   // When I called this it was fine.
        }

I have a feeling this may not be the right way to do it.
I tried changing options in '/GL', '/EHsc' or 'EHs', but it didn't make a difference.

Can you provide the definition of the send function?

Can you provide the definition of the send function?

send() used the code provided in the example.
// This is the C++11 equivalent of a generic lambda.
// The function object is used to send an HTTP message.
    struct send_lambda
    {
        boost::beast::tcp_stream& stream_;
        bool& close_;
        boost::beast::error_code& ec_;
        boost::asio::yield_context yield_;

        send_lambda(
            boost::beast::tcp_stream& stream,
            bool& close,
            boost::beast::error_code& ec,
            boost::asio::yield_context yield)
            : stream_(stream)
            , close_(close)
            , ec_(ec)
            , yield_(yield)
        {
        }

        template<bool isRequest, class Body, class Fields>
        void
            operator()(boost::beast::http::message<isRequest, Body, Fields>&& msg) const
        {
            // Determine if we should close the connection after
            close_ = msg.need_eof();

            // We need the serializer here because the serializer requires
            // a non-const file_body, and the message oriented version of
            // http::write only works with const messages.
            boost::beast::http::serializer<isRequest, Body, Fields> sr{ msg };
            boost::beast::http::async_write(stream_, sr, yield_[ec_]);
        }

        template<bool isRequest, class Body, class Fields>
        void
            operator()(boost::beast::http::message<isRequest, Body, Fields>&& msg, const bool syncParam) const
        {
            // Determine if we should close the connection after
            close_ = msg.need_eof();

            // We need the serializer here because the serializer requires
            // a non-const file_body, and the message oriented version of
            // http::write only works with const messages.
            boost::beast::http::serializer<isRequest, Body, Fields> sr{ msg };
            boost::beast::http::write(stream_, sr, ec_);
        }
    };

Exceptions are thrown in parse() as if you didn't write a try~catch statement. The response is properly delivered to the client who sent the request.

When I tried running the same source on Ubuntu in a docker environment, the problem did not occur.
Below are my options specific to msvc.
if(MSVC)
    ADD_DEFINITIONS(/bigobj)
    ADD_DEFINITIONS(-DCMAKE_TOOLCHAIN_FILE=C:/local/vcpkg/scripts/buildsystems/vcpkg.cmake)
    SET(CMAKE_CXX_FLAGS                "/EHs ${CMAKE_CXX_FLAGS}")
endif(MSVC)

It's possible this is an MSVC issue, can you change the boost.context impl used to fibers? That will of course be much slower, but would help us figure out where the issues comes from.

@lazychase Is this still open?


Permissions are repeatedly reset during project repo clone

Describe the bug
When deploying apps on PUL infrastructure, the beginning of the build_project_repo role takes significantly longer than other tasks, and reports changed:  each time it is run. The slow part is this step, where we recursively set permissions on the deploy directory to prevent permissions errors when cloning:
https://github.com/Princeton-CDH/cdh-ansible/blob/9a3839cde80c0d77113c170a1c142a0900f098a5/roles/build_project_repo/tasks/main.yml#L18-L27
this is a large recursive operation, so it could potentially take a long time, but it appears to be running (and changing permissions) every time, which doesn't seem right.
Expected behavior
The permissions should be set correctly once, and then ansible should detect that there's no need to make a change and report skipped: , making the step quicker.

This was resolved at some point and is no longer an issue


chore: release 0.1.0-beta prep

Description of changes:

Added initial changelog for the 3 new packages
Updated Readme to add NuGet package badge and GitHub build status badge

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Can you remove this as well, and the equivalent line in the Lambda and OTel readmes? https://github.com/awslabs/aws-dotnet-messaging/blob/598dabd92b0baa29b6c9cad68c08c35657811945/README.md?plain=1#L25
as well
Docs too: https://github.com/awslabs/aws-dotnet-messaging/blob/598dabd92b0baa29b6c9cad68c08c35657811945/docs/docs/getting-started.md?plain=1#L3
Can you add the badges to the Lambda and OTel readmes?

Fixed


Alias completion of git commands works with or without setopt completealiases in commits past that one.
Solution
Make sure the git plugin fully works even when completealiases is set.
Or even better, that aliases completion like gco<tab> works only when completealiases is set...

I can reproduce on OS X 10.9, and expect it will be the same on all platforms: this is normal behavior for complete_aliases.
Yeah, this is from #2790 and the commit 5b75cc7880de1931a0507800d90eb77ed659fa46 you identified. The current implementation assumes complete_aliases is off, which is the default for OMZ since 8883ace767997d1a629c165780af303f715ee78d. See this comment.
To fix it to work with complete_aliases, those compdefs need to be added back in.
Many other plugins and core aliases will also be affected by complete_aliases, since they generally do not explicitly define compdefs to go with the alias definitions. (Although it won't matter for many of them, since they take files as arguments and the default completion will work.) Maybe a more experienced OMZ developer can comment on interaction between OMZ and complete_aliases, and whether it's supported?

As an aside, why do you have complete_aliases set?

Yep, just read c3a58b000400 too.
I kind of feel that this issue has more to do with the standardization of completions of (I guess) most plugins or the fact that the git plugin is non standard among all others (is there even a standard?...)?
Pretty much the reason for completealiases is because several other plugins do not work fully without it. And it makes sense (in some cases):
no completealiases => no alias completion, completealiases => alias completion.
Some examples with rake and debian plugins:
unsetopt completealiases

Enter some ruby/rails project.
cd somerails
rake db:<tab>

No completion.
Let's try the debian plugin.
ai zs<tab>

No completion, while
aptitude (or apt-get) install zs<tab>
zsh-antigen   zsh-beta-doc  zsh-dbg       zsh-doc       zsh-static    zssh
zsh-beta      zshdb         zsh-dev       zsh-lovers    zsnes-dbg     zsync

works as intended.
Now with completealiases on:
setopt completealiases

the rake plugin
rake db:<tab>
db:create                -- creates the database from database_url or config/database.yml for the current rails_
db:drop                  -- drops the database from database_url or config/database.yml for the current rails_en
db:fixtures:load         -- load fixtures into the current environment's database
db:migrate               -- migrate the database (options: version=x, verbose=false, scope=blog)
...

completes correctly, and the debian plugin too:
ai zs<tab>
zsh-antigen   zsh-beta-doc  zsh-dbg       zsh-doc       zsh-static    zssh
zsh-beta      zshdb         zsh-dev       zsh-lovers    zsnes-dbg     zsync

Yeah, I think you're right that it's about standardization of how plugins do completion.
In my opinion, if a plugin requires complete_aliases at this point, that's a bug in the plugin. The default options after the core OMZ code loads are "authoritative", and plugins should be written to work under that state. It's probably a historical accident that some of them require it: they were probably written back when complete_aliases was the default in OMZ and didn't get updated when that changed.
You're right, we should standardize all the plugins to work with one setting or the other. But I think the correct one is "off": going with complete_aliases on would require extra, possibly tricky, configuration work for every alias we define (about 1,200 of them in all of OMZ), and would force users to do so as well for aliases they define themselves. If you leave complete_aliases off, you get completion for many aliases "for free".
On the flip side, if you have a case where you have an alias and you do want a distinct completion behavior for it (as opposed to the completion that would happen for the expanded alias), you can easily fix that on a per-command basis by converting the alias to a function.
The debian plugin is a good example. There's an open issue for it #3686. Check out the extra code it used to get working with complete_aliases enabled. And it is still buggy (e.g. it's using the apt-get completion when it should be using the aptitude completion).
I don't use rails, so I don't know why the db:... completion for rake requires complete_aliases. (Can you point me at an example rails project I can use to reproduce it?) But check out the flip side: that plugin also defines srake, brake, and other commands. Getting completion for them needs no_complete_aliases: if I do srake -<tab>, it will complete the options for me; if complete_aliases is on, it won't.
Let's fix the plugins to work under no_complete_aliases. I'll work through debian and rake with you. Let me know if you see others that are broken.

When you mentioned the rake command you must have been referring to the rails plugin, which is already protected against nocompletealiases because they are functions: https://github.com/robbyrussell/oh-my-zsh/blob/6d143d42ea2e16610855e5b1e912b2962d44d9ab/plugins/rails/rails.plugin.zsh#L30-L31
As per the debian plugin, there is already issue #3686 open, so I'm closing this issue unless there are other plugins that should be fixed as well.


[Doc] privilege faq, set catalog behavior change, grant/revoke format

add privilege faq and toc
add set catalog behavior change to release notes 3.1.2
update privilege req to set catalog, show catalogs
add privilege on set catalog to best practices in grant and user privilege
formatting revoke and grant
add finebi integrations

Fixes #issue
What type of PR is this:

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

Does this PR entail a change in behavior?

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

If yes, please specify the type of change:

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

Checklist:

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

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

Bugfix cherry-pick branch check:

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

[x] 3.1
[ ] 3.0
[ ] 2.5
[ ] 2.4

[FE Incremental Coverage Report]
:heart_eyes: pass : 0 / 0 (0%)

[BE Incremental Coverage Report]
:heart_eyes: pass : 0 / 0 (0%)

[FE Incremental Coverage Report]
:heart_eyes: pass : 0 / 0 (0%)

[BE Incremental Coverage Report]
:heart_eyes: pass : 0 / 0 (0%)

[FE Incremental Coverage Report]
:heart_eyes: pass : 0 / 0 (0%)

[BE Incremental Coverage Report]
:heart_eyes: pass : 0 / 0 (0%)

[FE Incremental Coverage Report]
:heart_eyes: pass : 0 / 0 (0%)

[BE Incremental Coverage Report]
:heart_eyes: pass : 0 / 0 (0%)

@mergify backport branch-3.1


Update faq for class not found / method not found

Docs for #2183
Rendered: https://github.com/GoogleContainerTools/jib/blob/loosebazooka-patch-1/docs/faq.md

Looks good to me. @TadCordle?


update readme

I am very interested in this project and would like to make contributions.

You are sure welcome to fork the project and customize it to your liking. This repository is mostly kept for archive purpose as I do not have the time anymore to maintain it.


compiler should helps to infer type

class Bla
  def initialize(s)
    @it = s.each_byte
  end
end

Bla.new("bla")

Error in ./1.cr:7: instantiating 'Bla:Class#new(String)'

Bla.new("bla")
    ^~~

instantiating 'Bla#initialize(String)'

in ./1.cr:3: Can't infer the type of instance variable '@it' of Bla

The type of a instance variable, if not declared explicitly with
`@it : Type`, is inferred from assignments to it across
the whole program.

The assignments must look like this:

  1. `@it = 1` (or other literals), inferred to the literal's type
  2. `@it = Type.new`, type is inferred to be Type
  3. `@it = Type.method`, where `method` has a return type
     annotation, type is inferred from it
  4. `@it = arg`, with 'arg' being a method argument with a
     type restriction 'Type', type is inferred to be Type
  5. `@it = arg`, with 'arg' being a method argument with a
     default value, type is inferred using rules 1, 2 and 3 from it
  6. `@it = uninitialized Type`, type is inferred to be Type
  7. `@it = LibSome.func`, and `LibSome` is a `lib`, type
     is inferred from that fun.
  8. `LibSome.func(out @it)`, and `LibSome` is a `lib`, type
     is inferred from that fun argument.

Other assignments have no effect on its type.

Can't infer the type of instance variable '@it' of Bla

    @it = s.each_byte
    ^~~

it hard to infer for human, i need to run something like this, to set correct type:
$ crystal eval 'p typeof("bla".each_byte)'
Indexable::ItemIterator(Slice(UInt8), UInt8)

why compiler can't help with actual variable type? in the stage when writing this message?

Starting from 0.19.0 you can write:
class Bla
  @it : Iterator(UInt8)

  def initialize(s)
    @it = s.each_byte
  end
end

Bla.new("bla")

@kostya It can't help with the correct type because the compiler didn't even analyze the Bar.new("bla") part. This error happens much earlier in the compiler's pipeline.

may be allow something like this?
class Bla
  @it : typeof("".each_byte)
end

@kostya No, typeof needs full type inference and we don't want to do that for determining the type of instance vars (it can get recursive, what if that method needs the type of another instance var?)

hm, but what about generics?
class Bla(T)
  @it : T
  def initialize(val : T)
  end
end

Bla.new("bla".each_byte)

The type of @it is the type parameter T, there's no need to run semantic analysis for thus.
Regardless of that, you have a point that generics have kind of a trick there, and in fact are a problem that is blocking me (I say "me" because I didn't sat down with @waj and others to think about it) from understanding how we'll implement incremental compilation with generics in the language.


Non-GUI version and logs

Great initiative and tool!
It is also good to have a  terminal non-gui version and execution logging for better issues tracking

I'll implement a command line version, which can be integrated with some other tools.


default user/pass invalid credentials

Describe the Issue (If applicable)
Default username password (ark/ark) does not authenticate through filebrowser web frontend or ssh
How can the issue be reproduced? (If applicable)
Enter username: ark and password: ark at ssh password prompt or http://[ip address]:80
What device are you using?
RG353V
What version of ArkOS are you on?
ArkOS 2.0 (022320244)
Anything else you'd like to include that may help to review this issue or feature request?
Using the password reset (Change Password) function in the Configuration menu results in "Password change failed". For all intents, it appears that either the username ark, or the password ark is not the documented default.  I have never changed the password to my knowledge, I've never successfully authenticated via ssh or web. I found reference to the combo root/351elec somewhere but that doesn't authenticate either, naturally.

user ark: and passwd: ark are always the default authentication.  Unless the image you're using was one not obtained from the wiki linked downloads.  If the image is one that you obtained through some other unsupported means, I can't help you.

thank you for the kind response, the fault was completely mine, I had changed the password and forgotten that I even did it.
apologies for wasting your time mate


document.execCommand

document.execCommand

This issue was imported from Google Moderator
Moderator votes: +3
Issue added by dave ͤͮͣͩ on 2014-08-19
To vote this issue up or down, simply include +1 or -1 in your comment.

http://www.quirksmode.org/dom/execCommand.html

+1

+1
https://developer.mozilla.org/en-US/docs/Web/API/document/execCommand

+1

+1

+1

+1

+1

Now available at http://caniuse.com/#feat=document-execcommand


Nested type support branch

@emmenko would you mind having a look at my pull request? I have troubles understanding why result is undefined in line 247 of product-type-generator.coffee.
It seems like even though promise is used, it's not waiting till the HTTP request is returned.
thanks

@sebbulon can we have a look on wednesday?


Segmentation fault when Map is used with IteratorIterator (v1.3.0)

On php 7.2 (specifically PHP 7.2.34) with version v1.3.0 this example code:
<?php

//require __DIR__ . '/vendor/autoload.php';

use Ds\Map;

class Messages implements IteratorAggregate
{
    private $messages;

    public function __construct()
    {
        $this->messages = new Map;
    }

    public function addMessage(string $key, string $message)
    {
        $this->messages->put($key, (object) ['key' => $key, 'message' => $message]);
    }

    public function getIterator(): Iterator
    {
        return new IteratorIterator($this->messages);
    }
}

$messages = new Messages();

$messages->addMessage('first', 'message');

foreach ($messages as $message) {
    print_r($message);
}

Results in a Segmentation fault (core dumped).
Using polyfill php-ds/php-ds (with the require uncommented)
Results in
stdClass Object
(
    [key] => first
    [message] => message
)

As expected.
We found a server that still had v1.2.9 on, so can confirm this issue was introduced with v1.3.0.

Slightly related to #166 - I think that fixing that issue might fix this as well as a side-effect.

Updated to confirm that this does not occur on v1.2.9.
This may be a duplicate of https://github.com/php-ds/ext-ds/issues/159.

I just tested this on 1.4.0:
stdClass Object
(
    [key] => first
    [message] => message
)

Since this commit, the base collection class implements IteratorAggregate, not Traversable.
https://github.com/php-ds/ext-ds/commit/f4fee1adf17c26d9514254f660d70e1016893237#diff-20e6612cc8f192e2682cdb770c6da2266df5566a636974e2cdc87227eda5e89d


Refactor table.hpp

Move static members out of Table class.

Completed for https://github.com/cylondata/cylon/releases/tag/0.2.0


fix: fix exports of components blocks

Hello,
I do again a PR for the exports of blocks components. It seems to not work with the "/dist"  path. It works when I do a "yarn link-external" but not when I retrieve from npm package. When I build the project it says it doesn't find the PasswordInput module.
In the node_modules folder I have this package.json in the @codegouv/react-dsfr package:

Only blocks have the /dist folder so it's why I removed it from the exports but I am not sure of this, if it is the best way to do it, can you take a look, please ?

Sorry about the scripts that prepare the NPM bundle wasn't up to date,
We need a solution that works both in local linking and when once published on NPM.
I'm releasing a new version, it should work.

No problem, it's my bad, I had to test more last time when I did the first fix.
Thank you for your reactivity, it's works well now

No no, don't be. You had no way to test that.
It's my CI script that was out of date.
Happy it works, thanks for the notice.


conflict of library names for tecnical replicates

Description of the bug
Technical replicates must have different FastQ file names for the pipeline to work. In my case the same pool of libraries was sequenced on two flow cells and had the exact same file names. The pipeline then tries to cat the files together (I think this was the step that failed) but nextflow can't produce the symlinks in the work directory because the multiple files have the same file name.
In the meantime I have changed the file name of the FastQ so that I have _00{1,2}.fastq.gz to distinguish the flow cells on which the libraries were sequenced and the pipeline seems happy with that.

Will be fixed when the changes here are merged and re-installed into the pipeline https://github.com/nf-core/modules/pull/1107


I broke the pip package during rebase

I broke the pip package. @nishadsingh1 can you double check to make sure I fixed it right?

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Clipper-PRB/327/
Test PASSed.

This LGTM.
The only use of cur_dir I'm seeing is in identifing the location of the check_and_write_deps.py script. With this PR, that's now happening correctly. Let me know if there are other things to test.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Clipper-PRB/328/
Test PASSed.

Cool. Let me finish testing it again on my end then I'll ping you to merge it.

okay this should be working again

merge when the tests pass

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Clipper-PRB/329/
Test PASSed.

Okay merge this


Adds a board-attribute to the widgets for board template overrides

Widget-directives will look for a board specific html-file that is placed in the templates/your-board-slug/ directory in your cyboard project.

Can you please squash these commits?

Done


Refs 184: add ouia ID for name and url

Hello
Add more ouia IDs, this time for name and  URL fields
Thank you

https://issues.redhat.com/browse/HMSCONTENT-184

⚠ This task currently requires qe-approval, but this PR does not fully resolve the task.  Please contact QE to determine appropriate testing required.

As mike suggested +1 for a shorter ouaid name

As mike suggested +1 for a shorter ouaid name

names updated

Thank you all.


Please document jobs.<job_id>.defaults.run.working-directory because it's important

Code of Conduct

[X] I have read and agree to the GitHub Docs project's Code of Conduct

What article on docs.github.com is affected?
https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_iddefaultsrun
What part(s) of the article would you like to see updated?
There should be a jobs.<job_id>.defaults.run.working-directory
https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_iddefaultsrun
Says:

Use jobs.<job_id>.defaults.run to provide default shell and working-directory to all run steps in the job. This keyword can reference several contexts. For more information, see "Contexts."

That should be visible in the ToC on the right, and have proper paragraphs. I shouldn't have to read the entire document ot discover this.
Additional information
It should explain how it interacts with previous levels.
There's a workflow that uses a global:
defaults:
  run:
    working-directory: ruby

I have no idea how to reset the working directory to the default in one job.

@jsoref Thank you for opening an issue! I'll get this triaged for review ✨

Fwiw, jobs.<job_id>.defaults.run.working-directory does indeed work. But I shouldn't have had to guess.

@jsoref Thank you for your patience while we reviewed this! 👋
The team agrees documenting jobs.<job_id>.defaults.run.working-directory would be valuable. You, or anyone else,  are welcome to submit a PR with this fix 💛


Update lesson fails, even with correct solution

Hey,
While working on the update lesson, I wasn't able to get my code to pass, so I tried your solution and still had no luck.
I not sure if it has something to do with the versions of Node or Mongodb.
Let me know if this is enough information:
Mongodb version v3.2.1
Node v4.2.3
My solution: https://github.com/icodejs/nodeschool/blob/master/learnyoumongo/06-UPDATE/solution.js
Your solution: https://github.com/evanlucas/learnyoumongo/blob/master/exercises/update/solution/solution.js
Thanks!

I have the same problem:
Mongodb v2.1.7
Node v5.1.0

I have the same problem. I resorted to using the "correct solution" but it didn't pass.
Mongodb v2.6.11
Node v4.1.1
Error message:
  db.collection('parrots').remove({}, function(err) {
    ^

TypeError: Cannot read property 'collection' of undefined
    at Exercise.<anonymous> (/home/ubuntu/.nvm/versions/node/v4.1.1/lib/node_modules/learnyoumongo/exercises/find/exercise.js:37:5)
    at next (/home/ubuntu/.nvm/versions/node/v4.1.1/lib/node_modules/learnyoumongo/node_modules/workshopper-exercise/exercise.js:260:17)
    at Exercise.end (/home/ubuntu/.nvm/versions/node/v4.1.1/lib/node_modules/learnyoumongo/node_modules/workshopper-exercise/exercise.js:266:5)
    at Workshopper.end (/home/ubuntu/.nvm/versions/node/v4.1.1/lib/node_modules/learnyoumongo/node_modules/workshopper/workshopper.js:191:12)
    at Workshopper.done (/home/ubuntu/.nvm/versions/node/v4.1.1/lib/node_modules/learnyoumongo/node_modules/workshopper/workshopper.js:323:19)
    at Exercise.<anonymous> (/home/ubuntu/.nvm/versions/node/v4.1.1/lib/node_modules/learnyoumongo/node_modules/workshopper-exercise/exercise.js:149:14)
    at /home/ubuntu/.nvm/versions/node/v4.1.1/lib/node_modules/learnyoumongo/node_modules/workshopper-exercise/exercise.js:136:16
    at Exercise.<anonymous> (/home/ubuntu/.nvm/versions/node/v4.1.1/lib/node_modules/learnyoumongo/node_modules/workshopper-exercise/filecheck.js:10:14)
    at FSReqWrap.oncomplete (fs.js:82:15)

My solution didn't  pass the tests. I saw these comments and doubted the test. So, I pimped out my solution to log tinas record before and after I updated it. I saw her age change from 30 to 40 and when I ran verify, it worked!
I thought I would share my working solution.
var mongo = require('mongodb').MongoClient
var url = "mongodb://localhost:27017/" + process.argv[2];
mongo.connect(url, function(err, db) {
    if (err) throw err;
    docs =  db.collection('users')
    tina = {
          username: "tinatime"
        }
    docs.find(tina).toArray(function(err, data) {
            if (err) throw err;
            console.log(data);
            docs.update(tina, { $set: {age: 40 }}, function(err
                    if (err) throw err;
                    docs.find(tina).toArray( function(err, data) {
                            if (err) throw err;
                            db.close()
                            console.log(data);
                        })
                })
    })
})

Doing the problem on cloud9 server. The solution for UPDATE which is to change the age of 'tinatime' to 40 is not working for me either. Here's my solution which seems to be correct but doesnt work:
`var mongo = require('mongodb').MongoClient;
var url = 'mongodb://localhost:27017/learnyoumongo';
mongo.connect(url, function(err, process.argv[2]) {
var user = db.collection('users');
    if (err) throw err;

    user.update({
            username: 'tinatime'
    }, {
            $set: {
                    age: 40
            }
    }, function(err, data) {
            if(err) throw err;
            console.log(data);
    });

    db.close();

})`
Still getting this error: 'Document has incorrect age property.Expected: 40 Actual: 30'


Deprecate ingress.status.LoadBalancer

There are three LB status in ingress.status, LoadBalancer, PublicLoadBalancer and PrivateLoadBalancer.
https://github.com/knative/networking/blob/f8dacf70c1e8a7daa7dd8847f42f3eb70fc5496a/pkg/apis/networking/v1alpha1/ingress_types.go#L304-L315
PublicLoadBalancer and PrivateLoadBalancer make sense but LoadBalancer does not in the status field.
some research in the current KIngress implementations
net-istio and net-kourier

external LB or internal LB is assigned in the LoadBalancer based on ingress.Spec.Visibility. But ingress.Spec.Visibility was deprecated.

net-contour

net-contour does not use it and always set LoadBalancer to nil.

/cc @mattmoor @ZhiminXiang @davidor

/cc @tcnghia


GoSublime Install

Trying to install GoSublime now is a pita. Isn't easier to just leave it in package control?

see #855


Fix backport for bpo-31078 (keeping use_rawinput)

Codecov Report

Merging #169 into master will increase coverage by 3.14%.
The diff coverage is 14.28%.

@@            Coverage Diff             @@
##           master     #169      +/-   ##
==========================================
+ Coverage   24.22%   27.36%   +3.14%
==========================================
  Files           2        2
  Lines        1701     1955     +254
  Branches      156      256     +100
==========================================
+ Hits          412      535     +123
- Misses       1275     1393     +118
- Partials       14       27      +13

Impacted Files
Coverage Δ

pdb.py
32.06% <0%> (+5.24%)
:arrow_up:

testing/test_pdb.py
21.94% <25%> (+0.01%)
:arrow_up:

Continue to review full report at Codecov.

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


Accept: Item Entry Management

Description
Acceptance Test for #36
Ability to create an entry which attaches a magic item to a particular character
UAT Environment for executing the acceptance flow
see #313 for automation of this flow.
Acceptance flow

User Logs in
User Navigates to a character
User clicks Entry to add a new entry
User fills out required information for an entry
User skips to the "items" step in the form
User clicks "add item" and fills the details of said item in
User Observes that the item has been created and is attached to both the character and the entry

Everything works perfectly! Approved!
-Kate Ruscito


Added in substitution tag limit

Description of the change:  Added in substitution tag limit to SMTP doc page
Reason for the change:  Character limit was  not specified anywhere in documentation
Link to original source: #2852
@ksigler7

 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.You have signed the CLA already but the status is still pending? Let us recheck it.

Hello @shovanch,Thanks again for the PR! We want to show our appreciation by sending                                              you some swag. Could you please fill out                                              this form so we can send it to you? Thanks!                                             Team SendGrid DX


Install Jackson ParameterNamesModule module by default

This builds on https://github.com/airlift/airbase/pull/163

cc @electrum

@tdcmeehan indeed, the problem occurs when class has: @JsonValue and single-arg static @JsonCreator.
The question is, shouldn't we upgrade straight to newest jackson (2.9.7)? (https://github.com/airlift/airlift/pull/692)


Bug: Failed checks are reported twice

When using checkov github action, failed checks are reported twice.
This issue is reproducible every time.

version: 2.0.977
Github action part
    - name: Analyze infra code with Checkov
      uses: bridgecrewio/checkov-action@master
      with:
        directory: ./terraform
        framework: terraform

Test resource in terraform
resource "google_storage_bucket" "my_terraform_bucket" {
  name          = "my-terraform-bucket"
  location      = "EU"
  force_destroy = true

  uniform_bucket_level_access = true
  versioning {
    enabled = true
  }
}

Action logs
2022-03-20T15:50:03.6271686Z checkov -d ./terraform     --output sarif      --framework terraform
2022-03-20T15:50:07.0771132Z
2022-03-20T15:50:07.0771668Z        _               _
2022-03-20T15:50:07.0772064Z    ___| |__   ___  ___| | _______   __
2022-03-20T15:50:07.0775188Z   / __| '_ \ / _ \/ __| |/ / _ \ \ / /
2022-03-20T15:50:07.0775835Z  | (__| | | |  __/ (__|   < (_) \ V /
2022-03-20T15:50:07.0776461Z   \___|_| |_|\___|\___|_|\_\___/ \_/
2022-03-20T15:50:07.0776957Z
2022-03-20T15:50:07.0777328Z By bridgecrew.io | version: 2.0.977
2022-03-20T15:50:07.0777718Z terraform scan results:
2022-03-20T15:50:07.0777973Z
2022-03-20T15:50:07.0778175Z Passed checks: 2, Failed checks: 1, Skipped checks: 0
2022-03-20T15:50:07.0778459Z
2022-03-20T15:50:07.0785654Z Check: CKV_GCP_29: "Ensure that Cloud Storage buckets have uniform bucket-level access enabled"
2022-03-20T15:50:07.0786275Z 	PASSED for resource: google_storage_bucket.my_terraform_bucket
2022-03-20T15:50:07.0786808Z 	File: /main.tf:22-31
2022-03-20T15:50:07.0787224Z 	Guide: https://docs.bridgecrew.io/docs/bc_gcp_gcs_2
2022-03-20T15:50:07.0787738Z Check: CKV_GCP_78: "Ensure Cloud storage has versioning enabled"
2022-03-20T15:50:07.0788224Z 	PASSED for resource: google_storage_bucket.my_terraform_bucket
2022-03-20T15:50:07.0788999Z 	File: /main.tf:22-31
2022-03-20T15:50:07.0789386Z Check: CKV_GCP_62: "Bucket should log access"
2022-03-20T15:50:07.0790735Z 	FAILED for resource: google_storage_bucket.my_terraform_bucket
2022-03-20T15:50:07.0807017Z ##[error]	File: /main.tf:22-31
2022-03-20T15:50:07.0838109Z 	Guide: https://docs.bridgecrew.io/docs/bc_gcp_logging_2
2022-03-20T15:50:07.0839206Z
2022-03-20T15:50:07.0839524Z 		22 | resource "google_storage_bucket" "my_terraform_bucket" ***
2022-03-20T15:50:07.0841661Z 		23 |   name          = "my-terraform-bucket"
2022-03-20T15:50:07.0842186Z 		24 |   location      = "EU"
2022-03-20T15:50:07.0845079Z 		25 |   force_destroy = true
2022-03-20T15:50:07.0845415Z 		26 |
2022-03-20T15:50:07.0845749Z 		27 |   uniform_bucket_level_access = true
2022-03-20T15:50:07.0846151Z 		28 |   versioning ***
2022-03-20T15:50:07.0846479Z 		29 |     enabled = true
2022-03-20T15:50:07.0846794Z 		30 |   ***
2022-03-20T15:50:07.0847090Z 		31 | ***
2022-03-20T15:50:07.0847255Z
2022-03-20T15:50:07.0847285Z
2022-03-20T15:50:07.0847291Z
2022-03-20T15:50:07.0847636Z Wrote output in SARIF format to the file 'results.sarif'
2022-03-20T15:50:07.0848536Z        _               _
2022-03-20T15:50:07.0848889Z    ___| |__   ___  ___| | _______   __
2022-03-20T15:50:07.0849274Z   / __| '_ \ / _ \/ __| |/ / _ \ \ / /
2022-03-20T15:50:07.0849594Z  | (__| | | |  __/ (__|   < (_) \ V /
2022-03-20T15:50:07.0849951Z   \___|_| |_|\___|\___|_|\_\___/ \_/
2022-03-20T15:50:07.0850271Z
2022-03-20T15:50:07.0850615Z By bridgecrew.io | version: 2.0.977
2022-03-20T15:50:07.0850982Z terraform scan results:
2022-03-20T15:50:07.0851188Z
2022-03-20T15:50:07.0851379Z Passed checks: 2, Failed checks: 1, Skipped checks: 0
2022-03-20T15:50:07.0851636Z
2022-03-20T15:50:07.0852075Z Check: CKV_GCP_29: "Ensure that Cloud Storage buckets have uniform bucket-level access enabled"
2022-03-20T15:50:07.0853310Z 	PASSED for resource: google_storage_bucket.my_terraform_bucket
2022-03-20T15:50:07.0853848Z 	File: /main.tf:22-31
2022-03-20T15:50:07.0854252Z 	Guide: https://docs.bridgecrew.io/docs/bc_gcp_gcs_2
2022-03-20T15:50:07.0854750Z Check: CKV_GCP_78: "Ensure Cloud storage has versioning enabled"
2022-03-20T15:50:07.0855233Z 	PASSED for resource: google_storage_bucket.my_terraform_bucket
2022-03-20T15:50:07.0855682Z 	File: /main.tf:22-31
2022-03-20T15:50:07.0856058Z Check: CKV_GCP_62: "Bucket should log access"
2022-03-20T15:50:07.0856752Z 	FAILED for resource: google_storage_bucket.my_terraform_bucket
2022-03-20T15:50:07.0857715Z ##[error]	File: /main.tf:22-31
2022-03-20T15:50:07.0858546Z 	Guide: https://docs.bridgecrew.io/docs/bc_gcp_logging_2
2022-03-20T15:50:07.0858825Z
2022-03-20T15:50:07.0859078Z 		22 | resource "google_storage_bucket" "my_terraform_bucket" ***
2022-03-20T15:50:07.0859595Z 		23 |   name          = "my-terraform-bucket"
2022-03-20T15:50:07.0859965Z 		24 |   location      = "EU"
2022-03-20T15:50:07.0860304Z 		25 |   force_destroy = true
2022-03-20T15:50:07.0860628Z 		26 |
2022-03-20T15:50:07.0860953Z 		27 |   uniform_bucket_level_access = true
2022-03-20T15:50:07.0861316Z 		28 |   versioning ***
2022-03-20T15:50:07.0861636Z 		29 |     enabled = true
2022-03-20T15:50:07.0861946Z 		30 |   ***
2022-03-20T15:50:07.0862234Z 		31 | ***
2022-03-20T15:50:07.0862410Z
2022-03-20T15:50:07.0862416Z
2022-03-20T15:50:07.0862423Z
2022-03-20T15:50:07.0862700Z Wrote output in SARIF format to the file 'results.sarif'

Actually everything is reported twice, no matter if there are failed checks.
2022-03-20T16:08:14.8165149Z checkov -d ./terraform/  --skip-check CKV_GCP_38,CKV_GCP_62   --output sarif      --framework terraform
2022-03-20T16:08:18.9955179Z
2022-03-20T16:08:18.9955879Z        _               _
2022-03-20T16:08:18.9956286Z    ___| |__   ___  ___| | _______   __
2022-03-20T16:08:18.9956914Z   / __| '_ \ / _ \/ __| |/ / _ \ \ / /
2022-03-20T16:08:18.9957465Z  | (__| | | |  __/ (__|   < (_) \ V /
2022-03-20T16:08:18.9959884Z   \___|_| |_|\___|\___|_|\_\___/ \_/
2022-03-20T16:08:18.9960616Z
2022-03-20T16:08:18.9960983Z By bridgecrew.io | version: 2.0.977
2022-03-20T16:08:18.9961360Z terraform scan results:
2022-03-20T16:08:18.9961603Z
2022-03-20T16:08:18.9962566Z Passed checks: 2, Failed checks: 0, Skipped checks: 0
2022-03-20T16:08:18.9963060Z
2022-03-20T16:08:18.9973413Z Check: CKV_GCP_29: "Ensure that Cloud Storage buckets have uniform bucket-level access enabled"
2022-03-20T16:08:18.9974303Z 	PASSED for resource: google_storage_bucket.my_terraform_bucket
2022-03-20T16:08:18.9974879Z 	File: /main.tf:22-31
2022-03-20T16:08:18.9975320Z 	Guide: https://docs.bridgecrew.io/docs/bc_gcp_gcs_2
2022-03-20T16:08:18.9975855Z Check: CKV_GCP_78: "Ensure Cloud storage has versioning enabled"
2022-03-20T16:08:18.9976332Z 	PASSED for resource: google_storage_bucket.my_terraform_bucket
2022-03-20T16:08:18.9976938Z 	File: /main.tf:22-31
2022-03-20T16:08:18.9977188Z
2022-03-20T16:08:18.9977267Z
2022-03-20T16:08:18.9977626Z Wrote output in SARIF format to the file 'results.sarif'
2022-03-20T16:08:18.9986760Z        _               _
2022-03-20T16:08:18.9987037Z    ___| |__   ___  ___| | _______   __
2022-03-20T16:08:18.9987440Z   / __| '_ \ / _ \/ __| |/ / _ \ \ / /
2022-03-20T16:08:18.9987696Z  | (__| | | |  __/ (__|   < (_) \ V /
2022-03-20T16:08:18.9987952Z   \___|_| |_|\___|\___|_|\_\___/ \_/
2022-03-20T16:08:18.9989962Z
2022-03-20T16:08:18.9990303Z By bridgecrew.io | version: 2.0.977
2022-03-20T16:08:18.9990592Z terraform scan results:
2022-03-20T16:08:18.9990744Z
2022-03-20T16:08:18.9990919Z Passed checks: 2, Failed checks: 0, Skipped checks: 0
2022-03-20T16:08:18.9991129Z
2022-03-20T16:08:18.9991611Z Check: CKV_GCP_29: "Ensure that Cloud Storage buckets have uniform bucket-level access enabled"
2022-03-20T16:08:18.9992557Z 	PASSED for resource: google_storage_bucket.my_terraform_bucket
2022-03-20T16:08:18.9992978Z 	File: /main.tf:22-31
2022-03-20T16:08:18.9993335Z 	Guide: https://docs.bridgecrew.io/docs/bc_gcp_gcs_2
2022-03-20T16:08:18.9993760Z Check: CKV_GCP_78: "Ensure Cloud storage has versioning enabled"
2022-03-20T16:08:18.9994164Z 	PASSED for resource: google_storage_bucket.my_terraform_bucket
2022-03-20T16:08:18.9995975Z 	File: /main.tf:22-31
2022-03-20T16:08:18.9996147Z
2022-03-20T16:08:18.9996154Z
2022-03-20T16:08:18.9996431Z Wrote output in SARIF format to the file 'results.sarif'

@gruebel Could it be due to a change we did in the SARIF output?

This also happens on version 2.0.1037

the output changes to SARIF are much longer ago. this looks like a complete different issue, because in the provided logs the banner is shown twice, which is super weird.

I noticed something peculiar. When using checkov --config-file .checkov.yaml relating to the output. For every entry under directory in the checkov config file, you will get checkov output + the previous output.

I troubleshooted this a bit more.
Last version without this bug<EMAIL_ADDRESS>2022-04-12T18:54:36.1366588Z        _               _
2022-04-12T18:54:36.1366985Z    ___| |__   ___  ___| | _______   __
2022-04-12T18:54:36.1367520Z   / __| '_ \ / _ \/ __| |/ / _ \ \ / /
2022-04-12T18:54:36.1367727Z  | (__| | | |  __/ (__|   < (_) \ V /
2022-04-12T18:54:36.1367947Z   \___|_| |_|\___|\___|_|\_\___/ \_/
2022-04-12T18:54:36.1368162Z
2022-04-12T18:54:36.1368384Z By bridgecrew.io | version: 2.0.422

First version with this bug<EMAIL_ADDRESS>2022-04-12T19:05:46.9026717Z        _               _
2022-04-12T19:05:46.9080076Z    ___| |__   ___  ___| | _______   __
2022-04-12T19:05:46.9082666Z   / __| '_ \ / _ \/ __| |/ / _ \ \ / /
2022-04-12T19:05:46.9084841Z  | (__| | | |  __/ (__|   < (_) \ V /
2022-04-12T19:05:46.9087007Z   \___|_| |_|\___|\___|_|\_\___/ \_/
2022-04-12T19:05:46.9089161Z
2022-04-12T19:05:46.9094160Z By bridgecrew.io | version: 2.0.423

I hope that this helps you track down and fix this bug.

Hey @nimrodkor have you noticed the info regarding versions in which this bug was introduced?

Hey @nimrodkor, any updates?

Only thing that change between them is:
https://github.com/bridgecrewio/checkov-action/compare/v12.880.0...v12.881.0
e.g. from docker://bridgecrew/checkov:2.0.422 to docker://bridgecrew/checkov:2.0.423
But comparing them doesn't show any change:
https://hub.docker.com/layers/checkov/bridgecrew/checkov/2.0.423/images/sha256-fb93440138d99fbf28c7ed37e1cb8eb0ed27024f8b59c091d5ead2b43620b428?context=explore
https://hub.docker.com/layers/checkov/bridgecrew/checkov/2.0.423/images/sha256-fb93440138d99fbf28c7ed37e1cb8eb0ed27024f8b59c091d5ead2b43620b428?context=explore
@hulkk are you sure the duplication appeared at that time?

Only thing that change between them is: v12.880.0...v12.881.0 e.g. from docker://bridgecrew/checkov:2.0.422 to docker://bridgecrew/checkov:2.0.423
But comparing them doesn't show any change: https://hub.docker.com/layers/checkov/bridgecrew/checkov/2.0.423/images/sha256-fb93440138d99fbf28c7ed37e1cb8eb0ed27024f8b59c091d5ead2b43620b428?context=explore
https://hub.docker.com/layers/checkov/bridgecrew/checkov/2.0.423/images/sha256-fb93440138d99fbf28c7ed37e1cb8eb0ed27024f8b59c091d5ead2b43620b428?context=explore
@hulkk are you sure the duplication appeared at that time?

Both of the links are the same, that's why there isn't any difference?

My bad:

2.0.422: https://hub.docker.com/layers/checkov/bridgecrew/checkov/2.0.422/images/sha256-cab838718265e9344ca08d972cb57b5b1a36b529fcb9a2abbf33e5412a8978d9?context=explore
2.0.423: https://hub.docker.com/layers/checkov/bridgecrew/checkov/2.0.423/images/sha256-fb93440138d99fbf28c7ed37e1cb8eb0ed27024f8b59c091d5ead2b43620b428?context=explore

Actually, silly me * 2, the difference is:
COPY file:6150c0110c292cab96554d00bf3e3d039c629da3bfe54677cd3640f1db06115a in /entrypoint.sh
COPY file:4811d77e91328eeacef11417a9299e16f5c8e54168af78c0ce0b2586491f7276 in /entrypoint.sh
So something different in the entrypoint.sh

This is also the checkov diff between 2.0.422 and 2.0.423:
https://github.com/bridgecrewio/checkov/compare/2.0.422...2.0.423

https://github.com/bridgecrewio/checkov/commit/9eca41c4c120de7244ed6bd8189ae9df739a7817

I think that entrypoint should check if environment variable "GITHUB_ACTION" exists before echoing with the "::set-output..."
See: https://docs.github.com/en/actions/learn-github-actions/environment-variables

@nimrodkor I think this issue is not resolved until github action is updated to use newer version of the container.

hey @hulkk if release a new checkov version, we automatically create the corresponding GitHub Action version, so with the latest version v12.1619.0 the fix should be inside. Feel free to leave some feedback, if it solved your issue.

Oh, true. There is a new tag. I happened to just check the releases which haven't been updated in months.


Update resources in services instead of components

See title.
Depends on #266.

Did you already have time to look over it @TimoBbz?


Point official domains to AWS

Once things are verified to be working in AWS for our sandbox domains, we should work on getting our domains to point to AWS and not Netlify.
Acceptance criteria:

[ ] https://design-system.alpha.canada.ca points to AWS amplify app
[ ] https://systeme-design.alpha.canada.ca points to AWS amplify app

Steps to complete this:

Create two hosted zones on the Design System Production AWS Account. We can do this by changing the names of the domains from *.cdssandbox.xyz to *.alpha.canada.ca

design-system.alpha.canada.ca
systeme-design.alpha.canada.ca

Move cdn.design-system.alpha.canada.ca as a record inside design-system.alph.canada.ca hosted zone

Hosting migration done; domains are now pointing to AWS nameservers


WAP Federation Service Name - Internal or Public DNS

When configuring the proxy, should I use the public DNS name? Isn't this just resolving back to the Proxy? I can resolve the public DNS name from proxy, certificates are in their proper stores, and have walked through the steps again, yet the config wizard leaves me with this error:
An error occurred when attempting to establish a trust relationship with the federation service. Error: Unable to connect to the remote server

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

ID: 2a0b3f11-8f84-f015-82db-5f0d049e1a76
Version Independent ID: 949d1ec8-4335-4827-83d7-3f67bb9a26fa
Content: Federated identity for your Office 365 dev/test environment
Content Source: Enterprise/federated-identity-for-your-office-365-dev-test-environment.md
Service: o365-solutions
GitHub Login: @JoeDavies-MSFT
Microsoft Alias: josephd

The example PowerShell is misleading for this step:
"$testZone="<the FQDN of your testlab domain from phase 1, example: testlab.contoso.com>"
should be:
"$testZone="testlab., example: testlab.contoso.com>"
The way I read the example was to use the internal FQDN of the domain from step 1:
fs.corp.contoso.com

@huzzeytech - Thank you for submitting feedback.
I will get this issue over to the Enterprise writing team for investigation.
Thank you for reporting and making the docs better. Much appreciated.
I made a note to request the team to update this when the work is complete.

@huzzeytech You are correct. The PowerShell commands are using the external federation service FQDN, not the internal FQDN. I have corrected the commands to reflect this. Sorry for the inconvenience. Thanks so much for letting us know.


[Podman] CI attached to podman branch only create the bundle but not run with crc

As of now the CI on the podman branch is just create the bundle but doesn't run it using crc so even if CI is green that mean bundle creation doesn't have issue but there is no test around created bundle able to run using crc. We should expand this and might use the same test which QE folks are trying with podman preset.

It is fixed now.


Update README to for aws_ec2_register

This informs the user that his function should be placed after AWS settings have been set.

Thanks, was this your issue in https://github.com/fernandocarletti/capistrano-aws/issues/7 É

Yep. I meant to close the issue and got sidetracked. I'll go do that now. :)


[Bug] Disable new signups still not possible

Is there an existing issue for this?

[X] Yes, I have searched the existing issues and none of them match my problem.

Product Variant
Self-Hosted
Current Behavior
Hello and thank you for this great tool!
Can you please check it again?
Another user confirmed it in the closed issue  here  : https://github.com/AmruthPillai/Reactive-Resume/issues/1592
and provided a thorough feedback of why this is happening.
Thank you
Expected Behavior
No response
Steps To Reproduce
No response
What browsers are you seeing the problem on?
No response
What template are you using?
None
Anything else?
No response

Can confirm, setting NODE_ENV=development and sign ups are disabled, but I can't log in with an existing account anymore. NODE_ENV=production and I can sign in again, but VITE_DISABLE_SIGNUPS is ignored and signups are re-enabled.

Can we get an update on this issue?

@AmruthPillai  is there any fix for this? finding that I can not disable sign up which is weird

For me, I just need to git clone this project, and then add the VITE_DISABLE_SIGNUPS="true" environment variable during the build stage in the Dockerfile. After using this modified Dockerfile to build the image, I can disable signup when NODE_ENV=production.

Dockerfile example
...
# --- Build Image ---
FROM base AS build

ENV NX_CLOUD_ACCESS_TOKEN=$NX_CLOUD_ACCESS_TOKEN
ENV VITE_DISABLE_SIGNUPS="true"

COPY .npmrc package.json pnpm-lock.yaml ./
RUN --mount=type=cache,id=pnpm,target=/pnpm/store pnpm install --frozen-lockfile

COPY . .

RUN pnpm run build
...

@AmruthPillai This issue has been unresolved for almost two months now. I cannot start my instance, and therefore am without a resume, without this fix. Can we please get a fix for this, or at least an update?

I found a workaround

I created a resume and copied the shareable link for me to access it later

Then i recreated the stack with the below
-- Email (Optional) --
DISABLE_EMAIL_AUTH: true
VITE_DISABLE_SIGNUPS: true
SKIP_STORAGE_BUCKET_CHECK: false

Post this no login sections is visible in the login page, however the resume with the sharable link generated earlier is accessible via the link generated earlier.

To edit the resumes, I recreated the stack updating my docker compose with the below values.
-- Email (Optional) --
#DISABLE_EMAIL_AUTH: true
#VITE_DISABLE_SIGNUPS: true
SKIP_STORAGE_BUCKET_CHECK: false


improve uri completion when uri path is relative

Regardless of referer uri, uri scheme is completed with "http" when uri path is relative.
It should be "https" when referer uri's scheme is "https".

fixed #11


[BUG] Setuptools is including test files in its own wheel

setuptools version
main branch: 464568d
Python version
Python 3.8
OS
Ubuntu 20.04.3 LTS
Additional environment information
No response
Description
Setuptools own wheel contain some test files, which is undesirable.
Moreover it indicates that either:

find_namespace_packages is struggling to handle the exclude patterns, OR
the exclude pattern configuration is insufficient
https://github.com/pypa/setuptools/blob/464568d64469fb1ca9794ef26fe2288f16c15598/setup.cfg#L30-L37

Side Note
This issue appeared when I was investigating the failures in #3015 for PyPY.
I am speculating the following:

When tox install setuptools from sdist, the build artifact contains a setuptools/tests folder

I suspect that works as an implicit namespace.

When pytest tries to import things there is a path manipulation (or some importlib shenanigans), and suddenly setuptools/tests has a __init__.py file, which I suspect conflicts with the previous installed implicit namespace

Expected behavior
Setuptools should not include test files in the final wheel distribution.
These files should not be installed in the end user environment.
How to Reproduce
cd /tmp
git clone --depth=1 https://github.com/pypa/setuptools.git
cd setuptools
virtualenv .venv -p python3.8

.venv/bin/python setup.py egg_info
.venv/bin/python setup.py bdist_wheel
unzip -l dist/setuptools*.whl | grep tests
      104  2022-01-09 00:19   pkg_resources/tests/data/my-test-package-source/setup.py
        0  2022-01-09 00:19   setuptools/tests/integration/__init__.py
     2134  2022-01-09 00:19   setuptools/tests/integration/helpers.py
     7938  2022-01-09 00:19   setuptools/tests/integration/test_pip_install_sdist.py

rm -rf dist build setuptools.egg-info
.venv/bin/python -m pip install build
.venv/bin/python -m build
unzip -l dist/setuptools*.whl | grep tests
      104  2022-01-09 00:19   pkg_resources/tests/data/my-test-package-source/setup.py
        0  2022-01-09 00:19   setuptools/tests/integration/__init__.py
     2134  2022-01-09 00:19   setuptools/tests/integration/helpers.py
     7938  2022-01-09 00:19   setuptools/tests/integration/test_pip_install_sdist.py

cd /tmp
wget https://files.pythonhosted.org/packages/eb/53/0dd4c7960579da8be13fa9b2c2591643d37f323e3d79f8bc8b1b6c8e6217/setuptools-60.5.0-py3-none-any.whl
unzip -l setuptools*.whl | grep tests
      104  2021-12-20 16:48   pkg_resources/tests/data/my-test-package-source/setup.py
        0  2022-01-08 01:39   setuptools/tests/integration/__init__.py
     2134  2022-01-08 01:39   setuptools/tests/integration/helpers.py
     7938  2022-01-08 01:39   setuptools/tests/integration/test_pip_install_sdist.py

Output
Both distributions built locally and the file on PyPI contain the following files:
pkg_resources/tests/data/my-test-package-source/setup.py
setuptools/tests/integration/__init__.py
setuptools/tests/integration/helpers.py
setuptools/tests/integration/test_pip_install_sdist.py

Code of Conduct

[X] I agree to follow the PSF Code of Conduct

Currently the code for the package finder has the following comment:
# Keep searching subdirectories, as there may be more packages
# down there, even if the parent was excluded.

So I assume that if the exclude matches a parent module, its children are not automatically excluded... (this is a bit confusing, but definetely intentional)
Therefore the solution would be adding *.tests.* to the exclude patterns.

@jaraco I am curious now...
What was the factor motivating the decision of not excluding "children" packages whose parents where excluded. Do you have any thoughts about that?
I understand that it brings more flexibility... but it is also more error prone.
Is it something we would like to change? (In terms of implementation, it all boils down to the indentation level of this code block)

When pytest tries to import things there is a path manipulation (or some importlib shenanigans), and suddenly setuptools/tests has a __init__.py file, which I suspect conflicts with the previous installed implicit namespace

pytest emulates this through import hooks and rewriting bytecode IIRC


Repository

Ktor uses its own repository and Kotlinx, so the wiki and README should update and add another maven repository for getting integrity dependencies.

Do you use gradle?

Yes. May I miss any configuration?

No, you are right: additional repository is specified but gradle doesn't support importing repositories from external pom's. This is why it doesn't work.

fixed in 4e4ccf080ae90663f4f444b5cbdc02ea53892ffa, see README.md


why doesn't my single node testnet produce blocks

I start my single node testnet with command
/usr/local/bin/nodeos --enable-stale-production true --producer-name eosio --signature-provider=EOS6ttqSHFAtVoQgc6d9VPTCvAVU4sFCwdYHojbzjoTX6wV8fwLyW=KEY:5HwPk4pD1Tf1VGXW77rjE6AGLj9E7VUTzjgmgGRPoK886UEyS5y --http-server-address <IP_ADDRESS>:8888 --p2p-listen-endpoint <IP_ADDRESS>:9876 --p2p-server-address <IP_ADDRESS>:9876 --agent-name eosio --p2p-max-nodes-per-host 1000 --plugin eosio::producer_plugin --plugin eosio::chain_api_plugin --plugin eosio::http_plugin --plugin eosio::history_api_plugin --plugin eosio::net_plugin --plugin eosio::net_api_plugin --plugin eosio::bnet_plugin --plugin eosio::wallet_api_plugin --config-dir /root/.nodes/eosio --data-dir /root/.nodes/eosio --genesis-json /root/.nodes/eosio/genesis.json --delete-all-blocks

The test net is supposed to start producing blocks. But the output stops. The json file refered in the command is shown as follows

{                                                                                "initial_timestamp": "2018-06-09T10:58:49",                                                                                "initial_key": "EOS6ttqSHFAtVoQgc6d9VPTCvAVU4sFCwdYHojbzjoTX6wV8fwLyW",                                                                                "initial_chain_id": "0000000000000000000000000000000000000000000000000000000000000000",                                                                               "initial_configuration": {                                                                                "max_block_net_usage": "1048576",                                                                                "target_block_net_usage_pct": "1000",                                                                                "max_transaction_net_usage": "524288",                                                                                "base_per_transaction_net_usage": "12",                                                                                "net_usage_leeway": "500",                                                                                "context_free_discount_net_usage_num": "20",                                                                                "context_free_discount_net_usage_den": "100",                                                                                "max_block_cpu_usage": "100000",                                                                                "target_block_cpu_usage_pct": "500",                                                                                "max_transaction_cpu_usage": "50000",                                                                                "min_transaction_cpu_usage": "100",                                                                                "max_transaction_lifetime": "3600",                                                                                "deferred_trx_expiration_window": "600",                                                                                "max_transaction_delay": "3888000",                                                                                "max_inline_action_size": "4096",                                                                                "max_inline_action_depth": "4",                                                                                "max_authority_depth": "6",                                                                                "max_generated_transaction_count": "16"                                                                                }
}

what is the problem with my launching command?

You need --private-key "["EOS6ttqSHFAtVoQgc6d9VPTCvAVU4sFCwdYHojbzjoTX6wV8fwLyW","corresponding_private_key"] as well.  The genesis.json initial_keypair needs to be available soeosio` can sign blocks.

push action eosio.token issue {"to":"eosio","quantity":"2000000000.0000 SYS","memo":"issue all system coin to eosio"} -p eosio
ERROR: ExtrasError: [quantity:2000000000.0000 SYS memo:issue all system coin to eosio]
Push a transaction with a single action
Usage: /home/eos-sources/eos/build/programs/cleos/cleos push action [OPTIONS] account action data
Positionals:
account TEXT                The account providing the contract to execute (required)
action TEXT                 A JSON string or filename defining the action to execute on the contract (required)
data TEXT                   The arguments to the contract (required)
Options:
-h,--help                   Print this help message and exit
-x,--expiration             set the time in seconds before a transaction expires, defaults to 30s
-f,--force-unique           force the transaction to be unique. this will consume extra bandwidth and
remove any protections against accidently issuing the same transaction multiple times
-s,--skip-sign              Specify if unlocked wallet keys should be used to sign transaction
-j,--json                   print result as json
-d,--dont-broadcast         don't broadcast transaction to the network (just print to stdout)
-r,--ref-block TEXT         set the reference block num or block id used for TAPOS (Transaction as Proof-of-Stake)
-p,--permission TEXT ...    An account and permission level to authorize, as in 'account@permission'
--max-cpu-usage-ms UINT     set an upper limit on the milliseconds of cpu usage budget, for the execution of the transaction (defaults to 0 which means no limit)
--max-net-usage UINT        set an upper limit on the net usage budget, in bytes, for the transaction
(defaults to 0 which means no limit)


[TEVA-4385] Amend start dates question

Jira ticket URL
https://dfedigital.atlassian.net/browse/TEVA-4385
Changes in this PR:
This PR makes the "Date job starts" part of the "Important dates" section in the vacancy listing process mandatory.
The question now has three radio buttons, from which one must be selected, setting the start_date_type enum for the vacancy. When selected, each radio button reveals the following input(s):

"Specific date" reveals a date field, saved to starts_on
"Date range" reveals two date fields, for earliest_starting_date and latest_starting_date.
"Other" reveals a text field for other_start_date_details

The same questions in the "Extend deadline" form and "Copy vacancy" form are also changed to this format.
Jobs to be run on the production database are included in this PR which set the appropriate start_date_type and as well as the corresponding field(s) for existing vacancies.
The starts_asap boolean field is to be removed from the vacancy model and database following integration of this PR.
Screenshots of UI changes:
Before

After

Next steps:

[ ] Run jobs to set start_date_type and corresponding fields for existing vacancies
[ ] Run migration to remove starts_asap field from database

Hi @robyoung91 .  I've come across a missing translation when setting some dates in the date range field.
It looks like it's caused when you set the earliest start date after the latest start date.


[Android/iOS][Controls - Button] Slow displayed of press state for enabled buttons

Steps to Reproduce:

Launch app
From Burger menu select Controls > Button
Tap Default / Contained / Outlined buttons
Notice the press state is not visible
Tap and hold on Default / Contained / Outlined buttons
Notice press state is displayed

Current behaviour
Slow displayed of press state for enabled buttons
Expected behaviour
Press state should be displayed when the button is tapped
Repro rate
100%
Affected platform(s):
Android
iOS
Version & devices
1.0.0 (655)
iPhone 6S - 14.0.1
Samsung S8 - 7

linked to #497


Add Named Pipe option to DockerClientConfiguration

It seems that remote api is not enabled for docker for windows (#109). Since at least for me socat didn't much work for Win10 and I ended up using "Named Pipe TCP Proxy" to get the client working, I think it's rather unnecessarily complicated. we should have something along the line like this:
DockerClient dockerClient = new DockerClientConfiguration(new NamedPipeClientStream(".", "docker_engine", PipeDirection.In));

We don't control how the Docker for Windows connects in the guest. If it was to connect via tcp then it would be remotely addressable without any proxy mappings. You can already connect via a named pipe stream via Docker.DotNet its just that the client on the 'host' and the daemon in the 'guest' are not on the same 'os' to my knowledge. I believe this would be a change to Docker for Windows not Docker.DotNet.
Am I missing something?

You can already connect via a named pipe stream via Docker.DotNet its just that the client on the 'host' and the daemon in the 'guest' are not on the same 'os' to my knowledge.

I'm not sure what you meant here. First, looking at the code I'm not saying a way to connect to initialize a DockerClient object via a named pipe stream. Second I didn't quite follow the 'os' and on the client and daemon - do you mean different versions of windows on containers on windows host? or linux containers on windows host? or the same thing just on linux hosts?

The URI you pass to the client configuration dynamically chooses the base stream. So passing:
npipe://./... will and calling CreateClient() will create a NamedPipeClientStream in the DockerClient. We don't expose it directly but we allow you to do this via the URI passed. If you wanted TCP you could do tcp://localhost:4589 to connect.
Docker for Windows (note this is a product it is not the same as Docker on Windows) runs in a Linux VM on a Windows host. So the reason that the 2nd level redirection is needed is because you are exposing the connection outside of the VM if I remember correctly. If you didnt want this 2nd level redirection you would need to run the Docker daemon (in the VM) with -m tcp://... and open that tcp port on the VM. Then from any host (including the hosting computer) you could use a DockerClientConfiguration(tcp://<ip-of-vm>:<port>) URI to get to the Docker daemon. Make sense?

The URI you pass to the client configuration dynamically chooses the base stream. So passing:
npipe://./... will and calling CreateClient() will create a NamedPipeClientStream in the DockerClient. We don't expose it directly but we allow you to do this via the URI passed. If you wanted TCP you could do tcp://localhost:4589 to connect.

I wasn't aware that was even possible! that's exactly what I was looking for. I do believe it should be mentioned on the README though as an additional way of creating the DockerClient object on Windows.
Regarding Docker for windows I think what you said applies for Linux containers running on a windows host, because if I switch to Windows containers then that VM you were talking about it switch to off on my system. Regardless I think the matter is closed - thank you for your help!


chore(deps): upgrade dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-k8s-23-main" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 1222

Questions ?
Please refer to the Backport tool documentation


Support pluralization

https://developer.mozilla.org/en-US/docs/Localization_and_Plurals
__(count, ["one item", "#1 items"], "nItems").replace("#1", count)

{ // German
  nItems: ["Ein Element", "#1 Elemente"]
}

I will try to combine current loader with external solution http://i18next.com/pages/doc_features.html

That might be a great solution.

@ronkorving It will be available on this weekends. Only small improvements left.

Are you saying you almost have a radically new version of i18-webpack-plugin ready? That depends on i18next-node?

@ronkorving Yes. Webpack generate bundle for each language using i18next-node. Static text already replaced completely as in current plugin but with additional i18next options. Plurals we must left as expression and replace dynamically on client side, Now I working on including language files and i18next module to the bundles. Unfortunately webpack doesn't has documentation for that.

Yeah, Webpack documentation on authoring plugins is very limited. I really appreciate your work on this, and can't wait to see the result! Thanks a lot, really.

Is this being worked on anymore?

@martyphee simple language bundles generation done, plurals must work only dynamic with i18next module. At this point I stop development of this feature. I can create gist with example

Sure that would be great.
On Friday, January 22, 2016, Max Mykhailenko<EMAIL_ADDRESS>wrote:

@martyphee https://github.com/martyphee simple language bundles
generation done, plurals must work only dynamic with i18next module. At
this point I stop development of this feature. I can create gist with
example
—
Reply to this email directly or view it on GitHub
https://github.com/webpack/i18n-webpack-plugin/issues/1#issuecomment-174068500
.

@max-mykhailenko I'd also like to see a gist of this

Sorry for delay https://gist.github.com/max-mykhailenko/64ce006f9febe4f0dbe6

Thank you for the Gist.  It's very helpful
On Wed, Feb 17, 2016 at 8:53 PM, Max Mykhailenko<EMAIL_ADDRESS>wrote:

Sorry for delay
https://gist.github.com/max-mykhailenko/64ce006f9febe4f0dbe6
—
Reply to this email directly or view it on GitHub
https://github.com/webpack/i18n-webpack-plugin/issues/1#issuecomment-185398203
.

Thanks for the gist. Are you planning on opening a pull request to add this to the plugin? Or do you have your own version of the plugin that you'll release?

@karlhorky Actually I don't understand how I can combine json generating and webpack building process. Maybe it's loader for files .php .twig .js' and than using I18nPlugin`. I will appreciate if you help me with architecture if you have experience with that.

I'm not sure you need to generate the json yourself - that can be part of a different plugin, loader, etc. For instance, take a look at the i18n example. This plugin just reads in an existing json file.

I took a quick look at the plugin code, and it seems to me the correct way to go about it would be this:

Define a new function (maybe called ngettext?) near the top that will accept the arguments for plural translations. Maybe take inspiration from libraries like Jed
Define a new parser.plugin block to call the function and define behavior like the existing one.
Refactor: see if the existing parser.plugin function shares enough with the new function defined in the previous step that some of the code can be shared. Move any shared things out into their own standalone functions.

The question would be if i18next-node can help with step 2 or 3 above, or if the code would be simple enough that you just write your own implementation.

Or, @sokra @jhnns? Would this be a good way of doing it?

Alternately, the __() function could be reused (polymorphic based on the number and type of arguments passed to it). This is already being done here. Not sure if this would make the function do too much though.

@karlhorky I think, the i18n plugin should support Jed style functions. Personally, I'd expect it to handle proper pluralization and contexts. Contexts are an important feature, because translations might be totally different based on the context they occur. That's probably something that native speaker tend to underestimate.
So, basically we should provide these functions:
gettext = function ( key )
dgettext = function ( domain, key )
ngettext = function ( singular_key, plural_key, value )
dngettext = function ( domain, singular_ley, plural_key, value )
pgettext = function ( context, key )
dpgettext = function ( domain, context, key )
npgettext = function ( context, singular_key, plural_key, value )
dnpgettext = function ( domain, context, singular_key, plural_key, value )

I know, the function names are kind of weird, but they are already well-known across different languages.
I think that should be doable with the current implementation. To simplify the implementation, that should probably be a breaking change.

that should be doable with the current implementation

So as to my proposal above, we would:

Define multiple new functions (along with keeping __() for backwards compatibility?)
Define parser.plugin blocks for each of them?
Refactor: In your opinion, could any of them share any code? Or is that what you meant by "breaking change"?

Would you leverage a library such as i18next-node or Jed for use in any of the plugin.parser functions or would you suggest we reimplement these functions ourselves?

I would suggest i18next since it can handle more formats.  Jed does work
well.  We currently use that.
On Fri, Feb 19, 2016 at 11:15 AM, Karl Horky<EMAIL_ADDRESS>wrote:

that should be doable with the current implementation
So as to my proposal above
https://github.com/webpack/i18n-webpack-plugin/issues/1#issuecomment-185642294,
we would:

Define multiple new functions (along with keeping __() for
backwards compatibility?)
Define parser.plugin blocks for each of them?
Refactor: In your opinion, could any of them share any code? Or is
that what you meant by "breaking change"?

Would you leverage a library such as i18next-node or Jed for use in any
of the plugin.parser functions or would you suggest we reimplement these
functions ourselves?
—
Reply to this email directly or view it on GitHub
https://github.com/webpack/i18n-webpack-plugin/issues/1#issuecomment-186175787
.

What's the status of this issue? Any progress since last year?


fix: more update readme testing

Description
This pull request changes the following:

more update readme testing

Related Issues

Closes #594

:tada: This PR is included in version 0.30.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Monitoring R2 at train time

Hi!
In the paper you mention that "the stopping criterion monitored was the ‘r-squared’ value".
However, when I run the training notebook, I get the following warning: "Early stopping conditioned on metric val_r_square which is not available".
After checking the documentation, it seems that the R Squared is available in Tensorflow Addons, however tfa not compatible with tf1.14? Could you please let me know what I am missing?
Thank you very much! :)

Hi,
Although the link to the training notebook above isn't accessible to me, I do remember the 'r-squared' computation being quite finicky.
The function you likely want to use can be accessed on line 1500, in the rr_aux.py file. Note that K refers to the variable imported in line 36 (from tensorflow.keras import backend as K). You should be able to adapt this function to compute R-squared for any version of tensorflow.
If you have further issues with tensorflow, a more straightforward (but maybe also more 'hacky') way of doing this would be to simply compute r-squared using the sklearn implementation that you can access here, for each model epoch. You could simply run training for a few epochs, save the model for each epoch, compute r-squared (or any other metric of your choice) using the sklearn implementation at the end of training for each epoch on the validation data, and pick your preferred model depending on your criterion.
Good luck!

Thank you very much for your reply! I am plotting R2 at train time and find that it is very stochastic - is that the expected behaviour?

If you are plotting it out for each batch, the stochasticity is to be expected.
If you are running it at the end of each epoch on just the validation set, it should stabilize after a couple of epochs.


Add OpenGL ES support

Would be great, if we could see in a future version support for OpenGL ES.

This would be feasible I think but there are a few different issues to unpack:

Supporting GLES 1.0 is likely never going to happen, but I believe it's not really relevant anymore so that's probably OK.
GLES 2.0 is certainly still relevant but it's more possible to support. AFAIK from a very loose understanding its deprecation of old functionality brings it close to a small subset of core profile GL 3.2, rather than still having loads of old compatibility profile features. The lack of features though might make some operations in renderdoc more difficult to implement.
GLES 3.0 and above is probably much easier as it's comparable to desktop GL, but you still might run into some features that are more difficult to implement without compute in 3.1 for example.
You could possibly get around the above issues with feature-lack by having some kind of emulation/shim layer that would actually create a desktop GL4.3 context and then just running the same commands with modifications to emulate GLES semantics. That depends a lot on how different GLES and GL are...
So while I think most of the hard implementation work is likely already done, the most time consuming part of supporting GLES would be going through the specs to find out where it differs from GL. If there's already a comprehensive 'semantic diff' like this between GLES and any desktop GL version, that would save a lot of time.
Using GLES on desktop is non-trivial I believe, relying on vendor extensions and such. Probably it's possible to support, but I don't know if anyone actually seriously uses GLES on desktop. So GLES support in RenderDoc would really only be a worthwhile investment when it supports mobiles. After that, possibly supporting desktop as well would be easy enough that you might as well.
The one place GLES is relevant on desktop is WebGL. Supporting it isn't impossible, but would need some careful consideration and a bunch of legwork to hook up to the browser as necessary.

Thanks a lot for the analysis.
Actually I was thinking of OpenGL ES 2.0 and OpenGL ES 3.x. Did not think about ES 1.x. And probably OpenGL ES 3.x would be sufficient.
It would be great using renderdoc on mobile and/or embedded devices.
Does renderdoc need a minimum feature set from the GPU to work (without workarounds)?

Yeh I figured people these days wouldn't be interested in ES 1.x, I just wanted to clarify :smile:. I know from Unity at least, ES 2 is still a large concern, but yeh potentially ES 3.x would make sense to start off with, then expand backwards as makes sense.
Support for mobile/embedded is definitely on the TODO list but it's lower down the priorities for me to get to. I think it's something that others might be looking into implementing support for. RenderDoc already has the concept of capturing and replaying remotely, so you could have a desktop host machine running the UI and doing the bulk of the work, and the remote target running ES just doing the basic replay.
RenderDoc uses compute for some analysis, transform feedback for fetching vertex outputs, and it will use SSBOs for pixel history/shader debugging when they are implemented. I also require some extensions like ARB_buffer_storage and EXT_direct_state_access but that's mostly for convenience rather than a hard requirement. There might be other things I'm using without consciously considering but in general those are the obvious things it requires over and above whatever the captured application uses.
It's worth noting though that the remote target architecture means that some of those features are only required on the desktop machine doing the analysis, so they wouldn't need to be implemented on GLES in the desktop-mobile scenario.

I was thinking of the host and target scenario.
I will have a deeper look at the source code and architecture of renderdoc.
Again, thanks a lot for clarifying things!

There's a presentation I wrote up that covers the high level architecture. It should still be pretty accurate, and it also describes how the remote host and target organisation works. Good places to start in the code are replay_driver.h for the interfaces implemented, and replay_proxy.cpp for the implementation that runs the host/target bridge over the network.
If you have any questions, feel free to ask. Either here or drop me an email or something :smile:.

Just a quick notification on this thread...
We have a preliminary OpenGL ES (2,3x)/EGL implementation for Android under evaluation currently.
It works in a similar fashion to the Android Vulkan support in terms of RenderDoc work flow and UI.
We hope to have it up for review soon (early next week).

RenderDoc for webgl (and webgl2 which should be on by default in chrome starting this month i believe?) would be amazing.

Looks like this hasn't been bumped in a while, and #445 was closed without comment. Is there an update on this?

Yeh I hadn't updated here since it's not a small/simple thing that can just get marked as 'done' easily. However it's looking like the next release of renderdoc will have GLES support.
To clarify: #445 was closed due to being unmanageable, and instead the authors of that code at Samsung worked on making smaller changes to the shared GL codebase over the past year or so. At this point GLES3 capture and replay is looking to be in good shape, and I believe that is both on desktop and android but this is primarily aimed at android dev.
More updates will follow as v1.x gets stabilised into v1.0 hopefully soon.

v1.0 has now been released, adding support for GLES2 and 3 on Android and Linux.


Fix HTML tag formatting

Fixes https://github.com/dotnet/razor-tooling/issues/6411
This fix was surprising :D

Posted it in teams this arvo :)

Sure thing, will add a test. If you have a specific use case in mind, feel free to post it here, or push up a test, or create a new issue, or whatever is easiet.
I'm pretty confident though - the fact that the start tag indented correctly proves that we know where the indent should be, its just that the old code literally skipped over the entire second line of the tag. Which actually makes me think, I should add a test for a tag spread over more than 2 lines too :)