Confusion About data available and Code Structure

Thank you for your wonderful work!
I have access to the EndoSLAM dataset, and I am trying to replicate your published results. I have found that the code seems to point (by default) to KITTI and cityscapes data (which are not the subject of the study conducted).
Am I missing something? How do use the code on the EndoSLAM dataset - specifically, the data loaders? Or do I have to write a new data loader?
Thank you very much.

I have a same question with this.
I've found kitti raw dataset & other open datasets that can be prepared for reproducing your published results.
But still cannot found EndoSLAM dataset to reproduce your results.
Did I missed something?

I have a same question with this. I've found kitti raw dataset & other open datasets that can be prepared for reproducing your published results. But still cannot found EndoSLAM dataset to reproduce your results. Did I missed something?

Have you solved this problem? Thanks for your reply.


Undefined method `read_nonblock' for string

I'm getting random errors when using webmock, loading raw responses from files, like this one:
  1) MetaInspector should get the title from the head section
     Failure/Error: stub_request(:get, "http://alazan.com/websolution.asp").to_return(fixture_file("alazan_websolution.response"))

     NoMethodError:
       undefined method `read_nonblock' for #<String:0x007ff205b16850>
     # /Users/jaime/.rvm/gems/ruby-2.4.0/gems/webmock-3.3.0/lib/webmock/response.rb:124:in `read_raw_response'
     # /Users/jaime/.rvm/gems/ruby-2.4.0/gems/webmock-3.3.0/lib/webmock/response.rb:18:in `initialize'
     # /Users/jaime/.rvm/gems/ruby-2.4.0/gems/webmock-3.3.0/lib/webmock/response.rb:10:in `new'
     # /Users/jaime/.rvm/gems/ruby-2.4.0/gems/webmock-3.3.0/lib/webmock/response.rb:10:in `response_for'
     # /Users/jaime/.rvm/gems/ruby-2.4.0/gems/webmock-3.3.0/lib/webmock/request_stub.rb:21:in `block in to_return'
     # /Users/jaime/.rvm/gems/ruby-2.4.0/gems/webmock-3.3.0/lib/webmock/request_stub.rb:21:in `map'
     # /Users/jaime/.rvm/gems/ruby-2.4.0/gems/webmock-3.3.0/lib/webmock/request_stub.rb:21:in `to_return'
     # ./spec/spec_helper.rb:17:in `block (2 levels) in <top (required)>'

Most specs run fine but then it crashes into that, and all the next specs will fail exactly like that.
This fails both in my dev machine, as in Travis:
https://travis-ci.org/jaimeiniesta/metainspector/jobs/337621342
This issue seems related to https://github.com/bblimke/webmock/issues/558

You can see the error happening in this branch:
https://github.com/jaimeiniesta/metainspector/tree/failing-mocks

@jaimeiniesta could you please run rspec with -b option, to get the full stacktrace.

@bblimke sure, here it goes:
  1) MetaInspector should get the title from the head section
     Failure/Error: stub_request(:get, "http://alazan.com/websolution.asp").to_return(fixture_file("alazan_websolution.response"))

     NoMethodError:
       undefined method `read_nonblock' for #<String:0x007fdfb1b03c48>
     # /Users/jaime/.rvm/rubies/ruby-2.4.0/lib/ruby/2.4.0/net/protocol.rb:172:in `rbuf_fill'
     # /Users/jaime/.rvm/rubies/ruby-2.4.0/lib/ruby/2.4.0/net/protocol.rb:154:in `readuntil'
     # /Users/jaime/.rvm/rubies/ruby-2.4.0/lib/ruby/2.4.0/net/protocol.rb:164:in `readline'
     # /Users/jaime/.rvm/rubies/ruby-2.4.0/lib/ruby/2.4.0/net/http/response.rb:40:in `read_status_line'
     # /Users/jaime/.rvm/rubies/ruby-2.4.0/lib/ruby/2.4.0/net/http/response.rb:29:in `read_new'
     # /Users/jaime/.rvm/gems/ruby-2.4.0/gems/webmock-3.3.0/lib/webmock/response.rb:124:in `read_raw_response'
     # /Users/jaime/.rvm/gems/ruby-2.4.0/gems/webmock-3.3.0/lib/webmock/response.rb:18:in `initialize'
     # /Users/jaime/.rvm/gems/ruby-2.4.0/gems/webmock-3.3.0/lib/webmock/response.rb:10:in `new'
     # /Users/jaime/.rvm/gems/ruby-2.4.0/gems/webmock-3.3.0/lib/webmock/response.rb:10:in `response_for'
     # /Users/jaime/.rvm/gems/ruby-2.4.0/gems/webmock-3.3.0/lib/webmock/request_stub.rb:21:in `block in to_return'
     # /Users/jaime/.rvm/gems/ruby-2.4.0/gems/webmock-3.3.0/lib/webmock/request_stub.rb:21:in `map'
     # /Users/jaime/.rvm/gems/ruby-2.4.0/gems/webmock-3.3.0/lib/webmock/request_stub.rb:21:in `to_return'
     # ./spec/spec_helper.rb:17:in `block (2 levels) in <top (required)>'
     # /Users/jaime/.rvm/gems/ruby-2.4.0/gems/rspec-core-3.7.1/lib/rspec/core/example.rb:447:in `instance_exec'
     # /Users/jaime/.rvm/gems/ruby-2.4.0/gems/rspec-core-3.7.1/lib/rspec/core/example.rb:447:in `instance_exec'
     # /Users/jaime/.rvm/gems/ruby-2.4.0/gems/rspec-core-3.7.1/lib/rspec/core/hooks.rb:350:in `run'
     # /Users/jaime/.rvm/gems/ruby-2.4.0/gems/rspec-core-3.7.1/lib/rspec/core/hooks.rb:509:in `block in run_owned_hooks_for'
     # /Users/jaime/.rvm/gems/ruby-2.4.0/gems/rspec-core-3.7.1/lib/rspec/core/hooks.rb:508:in `each'
     # /Users/jaime/.rvm/gems/ruby-2.4.0/gems/rspec-core-3.7.1/lib/rspec/core/hooks.rb:508:in `run_owned_hooks_for'
     # /Users/jaime/.rvm/gems/ruby-2.4.0/gems/rspec-core-3.7.1/lib/rspec/core/hooks.rb:595:in `block in run_example_hooks_for'
     # /Users/jaime/.rvm/gems/ruby-2.4.0/gems/rspec-core-3.7.1/lib/rspec/core/hooks.rb:594:in `reverse_each'
     # /Users/jaime/.rvm/gems/ruby-2.4.0/gems/rspec-core-3.7.1/lib/rspec/core/hooks.rb:594:in `run_example_hooks_for'
     # /Users/jaime/.rvm/gems/ruby-2.4.0/gems/rspec-core-3.7.1/lib/rspec/core/hooks.rb:464:in `run'
     # /Users/jaime/.rvm/gems/ruby-2.4.0/gems/rspec-core-3.7.1/lib/rspec/core/example.rb:494:in `run_before_example'
     # /Users/jaime/.rvm/gems/ruby-2.4.0/gems/rspec-core-3.7.1/lib/rspec/core/example.rb:253:in `block in run'
     # /Users/jaime/.rvm/gems/ruby-2.4.0/gems/rspec-core-3.7.1/lib/rspec/core/example.rb:500:in `block in with_around_and_singleton_context_hooks'
     # /Users/jaime/.rvm/gems/ruby-2.4.0/gems/rspec-core-3.7.1/lib/rspec/core/example.rb:457:in `block in with_around_example_hooks'
     # /Users/jaime/.rvm/gems/ruby-2.4.0/gems/rspec-core-3.7.1/lib/rspec/core/hooks.rb:466:in `block in run'
     # /Users/jaime/.rvm/gems/ruby-2.4.0/gems/rspec-core-3.7.1/lib/rspec/core/hooks.rb:604:in `run_around_example_hooks_for'
     # /Users/jaime/.rvm/gems/ruby-2.4.0/gems/rspec-core-3.7.1/lib/rspec/core/hooks.rb:466:in `run'
     # /Users/jaime/.rvm/gems/ruby-2.4.0/gems/rspec-core-3.7.1/lib/rspec/core/example.rb:457:in `with_around_example_hooks'
     # /Users/jaime/.rvm/gems/ruby-2.4.0/gems/rspec-core-3.7.1/lib/rspec/core/example.rb:500:in `with_around_and_singleton_context_hooks'
     # /Users/jaime/.rvm/gems/ruby-2.4.0/gems/rspec-core-3.7.1/lib/rspec/core/example.rb:251:in `run'
     # /Users/jaime/.rvm/gems/ruby-2.4.0/gems/rspec-core-3.7.1/lib/rspec/core/example_group.rb:628:in `block in run_examples'
     # /Users/jaime/.rvm/gems/ruby-2.4.0/gems/rspec-core-3.7.1/lib/rspec/core/example_group.rb:624:in `map'
     # /Users/jaime/.rvm/gems/ruby-2.4.0/gems/rspec-core-3.7.1/lib/rspec/core/example_group.rb:624:in `run_examples'
     # /Users/jaime/.rvm/gems/ruby-2.4.0/gems/rspec-core-3.7.1/lib/rspec/core/example_group.rb:590:in `run'
     # /Users/jaime/.rvm/gems/ruby-2.4.0/gems/rspec-core-3.7.1/lib/rspec/core/runner.rb:118:in `block (3 levels) in run_specs'
     # /Users/jaime/.rvm/gems/ruby-2.4.0/gems/rspec-core-3.7.1/lib/rspec/core/runner.rb:118:in `map'
     # /Users/jaime/.rvm/gems/ruby-2.4.0/gems/rspec-core-3.7.1/lib/rspec/core/runner.rb:118:in `block (2 levels) in run_specs'
     # /Users/jaime/.rvm/gems/ruby-2.4.0/gems/rspec-core-3.7.1/lib/rspec/core/configuration.rb:1926:in `with_suite_hooks'
     # /Users/jaime/.rvm/gems/ruby-2.4.0/gems/rspec-core-3.7.1/lib/rspec/core/runner.rb:113:in `block in run_specs'
     # /Users/jaime/.rvm/gems/ruby-2.4.0/gems/rspec-core-3.7.1/lib/rspec/core/reporter.rb:79:in `report'
     # /Users/jaime/.rvm/gems/ruby-2.4.0/gems/rspec-core-3.7.1/lib/rspec/core/runner.rb:112:in `run_specs'
     # /Users/jaime/.rvm/gems/ruby-2.4.0/gems/rspec-core-3.7.1/lib/rspec/core/runner.rb:87:in `run'
     # /Users/jaime/.rvm/gems/ruby-2.4.0/gems/rspec-core-3.7.1/lib/rspec/core/runner.rb:71:in `run'
     # /Users/jaime/.rvm/gems/ruby-2.4.0/gems/rspec-core-3.7.1/lib/rspec/core/runner.rb:45:in `invoke'
     # /Users/jaime/.rvm/gems/ruby-2.4.0/gems/rspec-core-3.7.1/exe/rspec:4:in `<top (required)>'
     # /Users/jaime/.rvm/gems/ruby-2.4.0/bin/rspec:22:in `load'
     # /Users/jaime/.rvm/gems/ruby-2.4.0/bin/rspec:22:in `<main>'
     # /Users/jaime/.rvm/gems/ruby-2.4.0/bin/ruby_executable_hooks:15:in `eval'
     # /Users/jaime/.rvm/gems/ruby-2.4.0/bin/ruby_executable_hooks:15:in `<main>'

And here's a fail from Travis:
  1) MetaInspector should get the title from the head section
     Failure/Error: stub_request(:get, "http://alazan.com/websolution.asp").to_return(fixture_file("alazan_websolution.response"))

     NoMethodError:
       undefined method `read_nonblock' for #<String:0x00000003d6dcd0>
     # /home/travis/.rvm/rubies/ruby-2.2.9/lib/ruby/2.2.0/net/protocol.rb:153:in `rbuf_fill'
     # /home/travis/.rvm/rubies/ruby-2.2.9/lib/ruby/2.2.0/net/protocol.rb:134:in `readuntil'
     # /home/travis/.rvm/rubies/ruby-2.2.9/lib/ruby/2.2.0/net/protocol.rb:144:in `readline'
     # /home/travis/.rvm/rubies/ruby-2.2.9/lib/ruby/2.2.0/net/http/response.rb:39:in `read_status_line'
     # /home/travis/.rvm/rubies/ruby-2.2.9/lib/ruby/2.2.0/net/http/response.rb:28:in `read_new'
     # /home/travis/.rvm/gems/ruby-2.2.9/gems/webmock-3.3.0/lib/webmock/response.rb:124:in `read_raw_response'
     # /home/travis/.rvm/gems/ruby-2.2.9/gems/webmock-3.3.0/lib/webmock/response.rb:18:in `initialize'
     # /home/travis/.rvm/gems/ruby-2.2.9/gems/webmock-3.3.0/lib/webmock/response.rb:10:in `new'
     # /home/travis/.rvm/gems/ruby-2.2.9/gems/webmock-3.3.0/lib/webmock/response.rb:10:in `response_for'
     # /home/travis/.rvm/gems/ruby-2.2.9/gems/webmock-3.3.0/lib/webmock/request_stub.rb:21:in `block in to_return'
     # /home/travis/.rvm/gems/ruby-2.2.9/gems/webmock-3.3.0/lib/webmock/request_stub.rb:21:in `map'
     # /home/travis/.rvm/gems/ruby-2.2.9/gems/webmock-3.3.0/lib/webmock/request_stub.rb:21:in `to_return'
     # ./spec/spec_helper.rb:17:in `block (2 levels) in <top (required)>'
     # /home/travis/.rvm/gems/ruby-2.2.9/gems/rspec-core-3.7.1/lib/rspec/core/example.rb:447:in `instance_exec'
     # /home/travis/.rvm/gems/ruby-2.2.9/gems/rspec-core-3.7.1/lib/rspec/core/example.rb:447:in `instance_exec'
     # /home/travis/.rvm/gems/ruby-2.2.9/gems/rspec-core-3.7.1/lib/rspec/core/hooks.rb:350:in `run'
     # /home/travis/.rvm/gems/ruby-2.2.9/gems/rspec-core-3.7.1/lib/rspec/core/hooks.rb:509:in `block in run_owned_hooks_for'
     # /home/travis/.rvm/gems/ruby-2.2.9/gems/rspec-core-3.7.1/lib/rspec/core/hooks.rb:508:in `each'
     # /home/travis/.rvm/gems/ruby-2.2.9/gems/rspec-core-3.7.1/lib/rspec/core/hooks.rb:508:in `run_owned_hooks_for'
     # /home/travis/.rvm/gems/ruby-2.2.9/gems/rspec-core-3.7.1/lib/rspec/core/hooks.rb:595:in `block in run_example_hooks_for'
     # /home/travis/.rvm/gems/ruby-2.2.9/gems/rspec-core-3.7.1/lib/rspec/core/hooks.rb:594:in `reverse_each'
     # /home/travis/.rvm/gems/ruby-2.2.9/gems/rspec-core-3.7.1/lib/rspec/core/hooks.rb:594:in `run_example_hooks_for'
     # /home/travis/.rvm/gems/ruby-2.2.9/gems/rspec-core-3.7.1/lib/rspec/core/hooks.rb:464:in `run'
     # /home/travis/.rvm/gems/ruby-2.2.9/gems/rspec-core-3.7.1/lib/rspec/core/example.rb:494:in `run_before_example'
     # /home/travis/.rvm/gems/ruby-2.2.9/gems/rspec-core-3.7.1/lib/rspec/core/example.rb:253:in `block in run'
     # /home/travis/.rvm/gems/ruby-2.2.9/gems/rspec-core-3.7.1/lib/rspec/core/example.rb:500:in `block in with_around_and_singleton_context_hooks'
     # /home/travis/.rvm/gems/ruby-2.2.9/gems/rspec-core-3.7.1/lib/rspec/core/example.rb:457:in `block in with_around_example_hooks'
     # /home/travis/.rvm/gems/ruby-2.2.9/gems/rspec-core-3.7.1/lib/rspec/core/hooks.rb:466:in `block in run'
     # /home/travis/.rvm/gems/ruby-2.2.9/gems/rspec-core-3.7.1/lib/rspec/core/hooks.rb:604:in `run_around_example_hooks_for'
     # /home/travis/.rvm/gems/ruby-2.2.9/gems/rspec-core-3.7.1/lib/rspec/core/hooks.rb:466:in `run'
     # /home/travis/.rvm/gems/ruby-2.2.9/gems/rspec-core-3.7.1/lib/rspec/core/example.rb:457:in `with_around_example_hooks'
     # /home/travis/.rvm/gems/ruby-2.2.9/gems/rspec-core-3.7.1/lib/rspec/core/example.rb:500:in `with_around_and_singleton_context_hooks'
     # /home/travis/.rvm/gems/ruby-2.2.9/gems/rspec-core-3.7.1/lib/rspec/core/example.rb:251:in `run'
     # /home/travis/.rvm/gems/ruby-2.2.9/gems/rspec-core-3.7.1/lib/rspec/core/example_group.rb:628:in `block in run_examples'
     # /home/travis/.rvm/gems/ruby-2.2.9/gems/rspec-core-3.7.1/lib/rspec/core/example_group.rb:624:in `map'
     # /home/travis/.rvm/gems/ruby-2.2.9/gems/rspec-core-3.7.1/lib/rspec/core/example_group.rb:624:in `run_examples'
     # /home/travis/.rvm/gems/ruby-2.2.9/gems/rspec-core-3.7.1/lib/rspec/core/example_group.rb:590:in `run'
     # /home/travis/.rvm/gems/ruby-2.2.9/gems/rspec-core-3.7.1/lib/rspec/core/runner.rb:118:in `block (3 levels) in run_specs'
     # /home/travis/.rvm/gems/ruby-2.2.9/gems/rspec-core-3.7.1/lib/rspec/core/runner.rb:118:in `map'
     # /home/travis/.rvm/gems/ruby-2.2.9/gems/rspec-core-3.7.1/lib/rspec/core/runner.rb:118:in `block (2 levels) in run_specs'
     # /home/travis/.rvm/gems/ruby-2.2.9/gems/rspec-core-3.7.1/lib/rspec/core/configuration.rb:1926:in `with_suite_hooks'
     # /home/travis/.rvm/gems/ruby-2.2.9/gems/rspec-core-3.7.1/lib/rspec/core/runner.rb:113:in `block in run_specs'
     # /home/travis/.rvm/gems/ruby-2.2.9/gems/rspec-core-3.7.1/lib/rspec/core/reporter.rb:79:in `report'
     # /home/travis/.rvm/gems/ruby-2.2.9/gems/rspec-core-3.7.1/lib/rspec/core/runner.rb:112:in `run_specs'
     # /home/travis/.rvm/gems/ruby-2.2.9/gems/rspec-core-3.7.1/lib/rspec/core/runner.rb:87:in `run'
     # /home/travis/.rvm/gems/ruby-2.2.9/gems/rspec-core-3.7.1/lib/rspec/core/runner.rb:71:in `run'
     # /home/travis/.rvm/gems/ruby-2.2.9/gems/rspec-core-3.7.1/lib/rspec/core/runner.rb:45:in `invoke'
     # /home/travis/.rvm/gems/ruby-2.2.9/gems/rspec-core-3.7.1/exe/rspec:4:in `<top (required)>'
     # /home/travis/.rvm/gems/ruby-2.2.9/bin/rspec:23:in `load'
     # /home/travis/.rvm/gems/ruby-2.2.9/bin/rspec:23:in `<main>'
     # /home/travis/.rvm/gems/ruby-2.2.9/bin/ruby_executable_hooks:15:in `eval'
     # /home/travis/.rvm/gems/ruby-2.2.9/bin/ruby_executable_hooks:15:in `<main>'

Here's the Travis build:
https://travis-ci.org/jaimeiniesta/metainspector/builds/339822348

@jaimeiniesta the problem is due to the redirections state, leaving a dirty state https://github.com/jaimeiniesta/metainspector/blob/400d71ba680c48c5c2df29688c68b3d68c3c8435/spec/meta_inspector/redirections_spec.rb#L22-L23 with WebMock being disabled.
It looks like WebMock doesn't handle creating stubbed responses from raw responses,
when WebMock is disabled, which has probably not been spotted by anyone before.
In the specs that fail, WebMock is simply disabled.

Ah! Sorry, I forgot to remove these lines - we were previously using FakeWeb for our suite, but we used WebMock for the redirections specs only, that's why they're enabled and then disabled. But now our entire suite uses WebMock, so it should always be enabled.
I'll close this issue now, maybe this detail can be added to WebMock, like being able to define stubs even when it's disabled, or rejecting them with a more meaningful response, but regarding this case it's all green now, thanks!


!!! FEATURE: Get rid of EventStoreManager and "bounded context"

Reworks the EventStoreManager to a simle EventStoreFactory, getting
rid of all the magic (getEventStoreForStreamName(), getEventStoreForEventListener()
and getEventStoreForBoundedContext()).
This is a breaking change only if you used an Event Store other than default:
Neos:
  EventSourcing:
    EventStore:
      stores:
        'some_custom_store':
          storage: 'Neos\EventSourcing\EventStore\Storage\Doctrine\DoctrineEventStorage'
          storageOptions:
            eventTableName: 'some_table'

In this case, a custom event listener to event store configuration is now required:
Neos:
  EventSourcing:
    EventListener:
      listeners:
        'Some\Package\SomeCustomListener':
          eventStore: 'some_custom_store'

Resolves: #212

I'm not 100% confident about the configuration format, especially because it requires 2 lines for every listener.. If a package contains a lot of them it might be useful to add support for some "wildcard" syntax.
And in that case it would probably make more sense to turn it around and configure the listeners at the event store like:
Neos:
  EventSourcing:
    EventStore:
      stores:
        'some_custom_store':
          storage: 'Neos\EventSourcing\EventStore\Storage\Doctrine\DoctrineEventStorage'
          # ...
          listeners:
            'Some\Package.*': true

turn it around and configure the listeners at the event store

Mind though, that the eventstore might be configured/declared in a completely different package, and you just reference it by it's configuration-name. With that, you could end up with creating a new (empty) configuration for a store, if that was renamed.
i.e. it would then only look like this
Neos:
  EventSourcing:
    EventStore:
      stores:
        'some_custom_store':
          listeners:
            'Some\Package.*': true

When only referencing, we could in theory add a validation pass when parsing config, if the referenced store is actually configured.

you could end up with creating a new (empty) configuration for a store

yes, good point..
Another problem is that you could create a n:n configuration and we'd have to check for this.
And lastly we would have to iterate over all event store configurations every time we want to catchup an event listener.

@albe Should we merge this one as is for now? We can always come up with some wildcard support lateron

Fine with that, have looked through the code again and I have no major issues.


[python-flask] Ensure liveness port is exposed

Expose the liveness port in the application docker file (it was only being exposed in the stack docker file). Without this,  k8s  would consider the pod to be dead.
Fixes #461

@Kamran64 Which k8s are you deploying to?

@henrynash I was using the Docker for Desktop version of k8s.

@henrynash I was using the Docker for Desktop version of k8s.

Me too! Hmm. I think there is still something wrong here, since I too have from time to time seen something that I can't explain in terms of not connecting. Let me dig further

It's happened to me several times before as well so I wasn't sure if it was an issue with the stack or a problem on my end. I'll try again using Minikube and see if I get a different result.

It's happened to me several times before as well so I wasn't sure if it was an issue with the stack or a problem on my end. I'll try again using Minikube and see if I get a different result.

So I am on the trail. I know WHAT is going wrong, I just can't explain WHY. First, my original fix is wrong.....we don't want to expose 5678...since that isn't what the python server is listening on. In fact, what IS happening is that somehow appsody deploy is thinking that the main APPSODY_PORT is 5678 (and not 8080 that is exposed)....which is why both the liveness is failing AND the regular url is not being served. I just can't explain WHY appsody deploy is doing this right now....

Ok, I think I have this resolved. appsody deploy creates that app-config.yaml PORTS based on the stack image NOT the Dockerfile for the application! This seems wrong to me, and I have raised a separate issue for this.
Since I did not have an ENV PORT=8080 statement in Dockerfile-stack, it picked one of the ports (the wrong one!).


add launchd configuration to support brew services

Add a launchd configuration so that brew services can manage a single-node Cockroach cluster, if so desired.
Fixes cockroachdb/cockroach#9438.

This supersedes #1, which is inexplicably ignoring my force pushes. @bdarnell, I've updated the formula to serve the admin on port 26256, as discussed, and added a caveat reminding users to only use this configuration in development. The full caveats read:
==> Caveats
CockroachDB is a distributed database intended for multi-server deployments.
For local development only, this formula ships a launchd configuration to
start an insecure single-node cluster that stores its data under:
  /usr/local/var/cockroach/
Instead of the default port of 8080, the node serves its admin UI at:
  http://localhost:26256

To run CockroachDB in production, please see:
  https://www.cockroachlabs.com/docs/recommended-production-settings.html

To have launchd start cockroachdb/cockroach/cockroach now and restart at login:
  brew services start cockroachdb/cockroach/cockroach
Or, if you don't want/need a background service you can just run:
  cockroach start

The last four lines are added automatically when a plist is present.

This change is

Review status: 0 of 1 files reviewed at latest revision, 1 unresolved discussion.

Formula/cockroach.rb, line 36 at r1 (raw file):

    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
    <plist version="1.0">

if you put this below test, would that produce easier diff to review? just wondering.

Comments from Reviewable

Perhaps a little bit, but I actually adapted the plist from Postgres's so any similarity with the commented-out one is purely incidental. Plus this is the standard order of Homebrew formulae: install, caveats, plist, test do.

Reviewed 1 of 1 files at r1.
Review status: all files reviewed at latest revision, 1 unresolved discussion.

Comments from Reviewable

LGTM, but I think the insecurity needs to be called out prominently in the caveats. "Don't use this mode for data you care about".

How's this? Updated caveats:
==> Caveats
CockroachDB is a distributed database intended for multi-server deployments.
For local development only, this formula ships a launchd configuration to
start a single-node cluster that stores its data under:
  /usr/local/var/cockroach/
Instead of the default port of 8080, the node serves its admin UI at:
  http://localhost:26256

Do NOT use this cluster to store data you care about; it runs in insecure
mode and may expose data publicly in e.g. a DNS rebinding attack. To run
CockroachDB securely in production, please see:
  https://www.cockroachlabs.com/docs/recommended-production-settings.html

To have launchd start cockroachdb/cockroach/cockroach now and restart at login:
  brew services start cockroachdb/cockroach/cockroach
Or, if you don't want/need a background service you can just run:
  cockroach start

recommended-production-settings.html doesn't talk about security. Link to https://www.cockroachlabs.com/docs/secure-a-cluster.html

Good call, thanks. Done.
==> Caveats
CockroachDB is a distributed database intended for multi-server deployments.
For local development only, this formula ships a launchd configuration to
start a single-node cluster that stores its data under:
  /usr/local/var/cockroach/
Instead of the default port of 8080, the node serves its admin UI at:
  http://localhost:26256

Do NOT use this cluster to store data you care about; it runs in insecure
mode and may expose data publicly in e.g. a DNS rebinding attack. To run
CockroachDB securely, please see:
  https://www.cockroachlabs.com/docs/secure-a-cluster.html

To have launchd start cockroachdb/cockroach/cockroach now and restart at login:
  brew services start cockroachdb/cockroach/cockroach
Or, if you don't want/need a background service you can just run:
  cockroach start


Nothing is rendered on Ubuntu on Parallels on OSX

go-gl/example works though. Looks like a thread problem?

https://github.com/hajimehoshi/ebiten/commit/6e98e0716d75b707f1079b00aa5a1bb3150c959e fixed this problem, the rendering is not perfect though.


Fix logic of finalization through exit() call (#228)

The fix for "exit() function bypasses END probe processing" #228 (#661)
introduced a bug which can cause bpftrace to never stop with a script
like this:
bpftrace -e 'i:ms:1 { cat("/proc/uptime"); exit();}'
This commit fixes the finalization logic:

When finalize_ is set the function should return independently of the
ready value, the remaining data will be read via the drain=true call.

Could you please add some runtime tests (maybe one for this case, and another one for the original commit) so we don't regress here? :)

@javierhonduco I added a runtime test for the original problem.
I think for the "introduced bug" there is no need for a specific test because a lot of other tests can catch the bug.
The problem is that CI is not running the runtime tests...

@caringi Awesome, thanks!

Tricky edge case...
LGTM


[Event Request] Table 5901 - Service Item Line

Hi,
we would like the following Event/Code added to Table 5901 "Service Item Line".

[IntegrationEvent(false, false)]
local procedure OnBeforeCheckFaultReportingCodes(var ServiceItemLine: Record "Service Item Line"; xServiceItemLine: Record "Service Item Line"; var IsHandled: Boolean)
begin
end;
The goal is to send a custom message/disable it.
I know it's version 14.x and we can just add it to the code but we would like to use it in newer versions as well.
Thank you.

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

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


fix: handle ppr error message refactor

Description
in a pull request introduced last january in next.js (dynamic-rendering.ts:153), the message passed in React.unstable_postpone thrown for PPR bailout was changed, meaning the check implemented by #2518 was not enough anymore, and the bailout was not being rethrown anymore, breaking next.js builds using ppr, and probably other issues.
i've updated it to match the latest version, but kept the old check for the sake of not causing a breaking change.
to test:

run a next.js build on an app that uses ppr with the latest version of @clerk/nextjs (should fail)
run another build with this pr (shouldn't fail anymore)

Checklist

[x] npm test runs as expected.
[x] npm run build runs as expected.
[ ] (If applicable) JSDoc comments have been added or updated for any package exports
[ ] (If applicable) Documentation has been updated

Type of change

[x] 🐛 Bug fix
[ ] 🌟 New feature
[ ] 🔨 Breaking change
[ ] 📖 Refactoring / dependency upgrade / documentation
[ ] other:

Nice work @ceIia 🎉  and thank you for the contribution!

is there something i can do to fix the failing check @dimkl? i'm not 100% sure of why it broke

@ceIia we are facing an issue with the integration tests failing for a forked PR because the GH secrets are not shared. I will let you know about the progress in the next couple of hours.


command not found on mac os x

when i enter  $ sudo pip install pcapy
$ brew install libdnet
$ brew install scapy
that doesn't work
"command not found"

Did you install homebrew?

Hi there. In a recent commit, we changed the whole scanning process in order to improve usability and resolve issues previously raised. Please try following the new installation procedure.
If this error still occurs, please let us know and we'll re-open the issue.
Thank you.


Biallelic SNP calls and diplotypes

Resolves #448

Adds a new method biallelic_snp_calls() which builds a dataset of SNP calls at sites which are biallelic within the selected samples. Note these do not necessarily have to include the reference allele, i.e., sites are included if there are only two alleles observed, regardles of which alleles.
Adds a new method biallelic_diplotypes() which computes alternate allele counts per genotype call, generating a 2-dimensional array suitable for use with PCA, neighbour-joining trees, admixture, etc.
Refactors pca() to use biallelic_diplotypes() internally.
N.B., because the set of input SNPs to PCA will be slightly different as a result of this change, I have bumped the results cache version number for the pca() function. Also the next release of malariagen_data should be a major version bump I would suggest - the API has not changed so code will still be backwards compatible, but analysis results could change slightly and so it would probably help to communicate that.

Going to merge but happy to follow up if any questions or suggestions.


Add arguments for non-ASCII encoding in header

This is a fix for issue #46, tried to keep everything as simple as possible, for splits with split.py one can add "header_encoding: ENC_TYPE" to options in the .yaml file, for rominfo.py one can pass --encoding ENC_TYPE, all of these will default to ASCII if no encoding type is provided.

Awesome! Thank you for your work on this :)

Awesome! Thank you for your work on this :)


[CI] Fix CI build issues

@ani-sha @uidoyen @indraraj Could you have a look too?

LGTM, leaving it to any other review to merge it. Thx, @rk3rn3r!

Thx @gunnarmorling! I promise I can't describe how happy I am now that we finally solved the CI errors. :sweat:

Yes, definitely, that's great news!


Support for GitHub Enterprise (Take 2)

While trying to release to a GitHub Enterprise host, the create release task fails, since the GitHub API Client has a hard coded host (api.github.com), while Enterprise requires host/api/v3

Should be resolved with #75.


 Please follow the instructions below. Reminder that you are bound to abide by the Code of Conduct
Description
Describe the purpose of this PR
Submission Checklist :pencil:

[ ] Add x
[ ] Fix y
[ ] Check z

Overall looks good to me so far. How do you plan to manage the differences between Erc721 and Erc1155?

It seems like the Nft interface will have to be extended a bit to match the ERC1151 functionality.


Can you reupload?

Can you reupload?

BTW i can install all of them by manually

What's the issue ?

There is no problem, you wrote Server are down in the readme section. But looks like it is fixed.

I mentioned this because someone is literally trying to brutforce my server but I fixed the issue and forgot to remove that


Reduce log level for many messages and ensure not to pass pointers to…

… logrus

Current coverage is 55.79% (diff: 35.27%)

Merging #91 into master will increase coverage by 1.10%

@@             master        #91   diff @@
==========================================
  Files            19         19
  Lines          3143       2957   -186
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
- Hits           1719       1650    -69
+ Misses         1307       1190   -117
  Partials        117        117

Powered by Codecov. Last update 34eb34e...826ec75


normalize_estimator function trying to access non-existent attribute

See thread here: dask/dask-ml#667
Proposing a change to subclass AttributeError to make it clear that you're accessing a non-existent attribute when calling the normalize_estimator function before training.

Em.. is there any specification for that?

@trivialfis , is there enough specification at https://github.com/dask/dask-ml/issues/667  ?

Surely I can do that.  I'm just thinking about what's the easiest and future proof way to be fully compatible with scikit learn as situations like this comes up a lot.

OK, let me know if I can provide further information.

I'm just thinking about what's the easiest and future proof way to be fully compatible with scikit learn as situations like this comes up a lot.

You might try running sklearn.utils.estimator_checks.check_estimator on the XGBoost estimators: https://scikit-learn.org/stable/modules/generated/sklearn.utils.estimator_checks.check_estimator.html

Thanks!  Work on this is already on the way.  There are some tests in there we might not be able to pass without making a breaking change.  But I succeeded at passing most of the other tests.

@trivialfis, did you manage to pass the tests? I'm just asking because my team is using the function so we're waiting for it to be fixed before we continue.

Yes, except for kwargs in init.  Will submit a PR this week.

A few of them are already mainlined actually, including the use of 'NotFittedError'.

I think the exception type is already fixed in master branch with NotFittedError replacing XGBoostError.  Let's open new issues for different errors.  I will also reply on https://github.com/dask/dask-ml/issues/667 when needed.


Installation failure

Hello,
I have to install pivy for a Freecad workbench, but I have some trouble:
Ubuntu 17.10, fresh install:
I install freecad-daily.
Then:
pip install https://github.com/FreeCAD/pivy/archive/master.zip gives the following error:
` ~~~ HISSSSSSSSSS ~~~
Welcome to Pivy 0.6.3!
Building Pivy has never been so much fun!
Platform...linux2
Python version...2.7.14
Checking for swig...
not found.
Checking for swig3.0...
not found.

----------------------------------------

Command "/usr/bin/python -u -c "import setuptools, tokenize;file='/tmp/pip-JRYOeQ-build/setup.py';f=getattr(tokenize, 'open', open)(file);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, file, 'exec'))" install --record /tmp/pip-oYhwod-record/install-record.txt --single-version-externally-managed --compile --user --prefix=" failed with error code 1 in /tmp/pip-JRYOeQ-build/
`
Obviously, swig is missing, I install it, but then:
`Installing collected packages: Pivy
Running setup.py install for Pivy ... error
Complete output from command /usr/bin/python -u -c "import setuptools, tokenize;file='/tmp/pip-tPN9u6-build/setup.py';f=getattr(tokenize, 'open', open)(file);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, file, 'exec'))" install --record /tmp/pip-Cn1XBM-record/install-record.txt --single-version-externally-managed --compile --user --prefix=:
running install
running build
                            _____
                        .-'`     '.
                     __/  __       \
                    /  \ /  \       |    ___
                   | /`\| /`\|      | .-'  /^\/^\
                   | \(/| \(/|      |/     |) |)|
                  .-\__/ \__/       |      \_/\_/__..._
          _...---'-.                /   _              '.
         /,      ,             \   '|  `\                \
        | ))     ))           /`|   \    `.       /)  /) |
        | `      `          .'       |     `-._         /
        \                 .'         |     ,_  `--....-'
         `.           __.' ,         |     / /`'''`
           `'-.____.-' /  /,         |    / /
               `. `-.-` .'  \        /   / |
                 `-.__.'|    \      |   |  |-.
                    _.._|     |     /   |  |  `'.
              .-''``    |     |     |   /  |     `-.
           .'`         /      /     /  |   |        '.
         /`           /      /     |   /   |\         \
        /            |      |      |   |   /\          |
       ||            |      /      |   /     '.        |
       |\            \      |      /   |       '.      /
       \ `.           '.    /      |    \        '---'/
        \  '.           `-./        \    '.          /
         '.  `'.            `-._     '.__  '-._____.'--'''''--.
           '-.  `'--._          `.__     `';----`              \
              `-.     `-.          `.''```                     ;
                 `'-..,_ `-.         `'-.                     /
                        '.  '.           '.                 .'

                            ~~~ HISSSSSSSSSS ~~~
                           Welcome to Pivy 0.6.3!
                 Building Pivy has never been so much fun!

Platform...linux2
Python version...2.7.14
Checking for swig...
'/usr/bin/swig'
Checking for SWIG version...
3.0.10
calling: cmake .
error: [Errno 2] No such file or directory

----------------------------------------

Command "/usr/bin/python -u -c "import setuptools, tokenize;file='/tmp/pip-tPN9u6-build/setup.py';f=getattr(tokenize, 'open', open)(file);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, file, 'exec'))" install --record /tmp/pip-Cn1XBM-record/install-record.txt --single-version-externally-managed --compile --user --prefix=" failed with error code 1 in /tmp/pip-tPN9u6-build/
`

thanks for reporting. I guess the problem is that you are running the install not from the source dir. I pushed a fix for this issue. Maybe you can try.

I tried right now, and the error message changed:
calling: cmake /tmp/pip-FcTt6n-build
error: [Errno 2] No such file or directory
----------------------------------------

Command "/usr/bin/python -u -c "import setuptools, tokenize;file='/tmp/pip-FcTt6n-build/setup.py';f=getattr(tokenize, 'open', open)(file);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, file, 'exec'))" install --record /tmp/pip-DRVzGy-record/install-record.txt --single-version-externally-managed --compile --user --prefix=" failed with error code 1 in /tmp/pip-FcTt6n-build/

what do you mean by

also note that coin has to be build with cmake.

?

maybe cmake is missing:
sudo apt-get install cmake

regarding coin: coin3d offers cmake as build-system. To support qt5 I updated pivy to work with coin build with cmake. Therefor it's not possible anymore to build pivy with older versions of coin.
If you don' care about qt5 /cmake you can try the following:
pip install https://github.com/FreeCAD/pivy/archive/0.6.2.tar.gz


Initial configuration

I wanted to create something that we can easily include in each repo using:
{
  "remarkConfig": {
    "plugins": ["preset-lint-stylelint"]
  }
}

Like we already do with our ESLint configuration.
The npm run lint:md command in this repo is set up to dogfood the configuration.

This looks great, just a question though, if we going to begin using scoped packages should this be published and named @styleintt/remark-config instead?

This looks great, just a question though, if we going to begin using scoped packages should this be published and named @styleintt/remark-config instead?

I wasn't sure. I figured I'd stick without a scoped package for consistency to eslint-config-stylelint. I'm easy either way.

Let's go with a scoped package. They are the way forward.
We can have:

@stylelint/prettier-config
@stylelint/eslint-config
@stylelint/remark-preset

As these only affect the org.
Whether we, like babel, move to @stylelint/stylelint, @stylelint/config-recommended, @stylelint/config-standard is a discussion for another time :)

I'll rename the repo to remark-preset once this is merged.

jeddy3@UNKNOWN remark-preset-lint-stylelint % npm publish --dry-run
npm notice
npm notice 📦<EMAIL_ADDRESS>npm notice === Tarball Contents ===
npm notice 214B  index.js
npm notice 1.3kB package.json
npm notice 41B   CHANGELOG.md
npm notice 643B  README.md
npm notice === Tarball Details ===
npm notice name:          @stylelint/remark-preset
npm notice version:       1.0.0
npm notice package size:  1.1 kB
npm notice unpacked size: 2.2 kB
npm notice shasum:        f86ec52f58dfed4b74f81c04906b429e412bc8cc
npm notice integrity:     sha512-7BmGB9TQuFI5n[...]1SwEnDpNI3aew==
npm notice total files:   4
npm notice
+<EMAIL_ADDRESS>
The dry-run looks good.


Package resource is hardcoded to gzipped tar files

Cookbook version
2.1.1
Latest commit b420a8f  on Sep 1
Chef-client version
latest
Platform Details
Any
Scenario:
Package resource is hardcoded to gzipped tar files.
Steps to Reproduce:
use tar_package resource
Expected Result:
I'd expect it to work with other file extensions like tar_extract such as .xz
Actual Result:
Resource fails with no such directory.
See:
https://github.com/chef-cookbooks/tar/blob/master/resources/package.rb#L39
https://github.com/chef-cookbooks/tar/blob/master/resources/package.rb#L56
tar -xf should automatically extract gz, bz2, and xz files without supplying the compression character z, j, or J. These are only required during compression.

Yes need to lose the z parameter from tar_extract:

tar_flags: Array of additional flags to be passed to tar xzf command.
I'm failing to use this cookbook to extract bz2 archives.

Also for example if you want to use zstd you have to unset compress_char:
compress_char ''
tar_flags [ '-I zstd' ]

And there is this hacky work-around too: https://github.com/chef-cookbooks/tar/blob/master/resources/extract.rb#L50

Why not default to compress_char "a"? (for automatic from extension)

@tpdownes It's more about decompression. The default command should be generic enough to uncompress any valid format using file magic numbers to determine the correct type automatically. The functionality is already built into the tar utility.
Lines like https://github.com/chef-cookbooks/tar/blob/master/resources/package.rb#L61 would therefore read
command "#{r.tar_binary} xf #{basename}"
for two important reasons. First is that it works with all supported tarballs regardless of format or extension and second is that the file name should really be directly after the f because it's technically the value passed to -f 😄
Same issue here: https://github.com/chef-cookbooks/tar/blob/master/resources/extract.rb#L91 compression character is not needed plus it's in the wrong spot.

You are certainly describing how I run the command in my personal life. :) One might reasonably wager that the author(s) don't care or only respond to PRs.


utils: normalize zip file path

It is possible for a link to use a relative path and thus have .. within it.
In such a scenario, the current implementation will throw an error file not found because it simply performs string comparison against the absolute path, e.g., because a/b/../c is considered different from a/c.
This PR updates ZipPathUtils.combine to always normalize the path.

@stevenwjy thanks for your contribution!


Publish layer to more regions

Is your feature request related to a problem? Please describe.
I can't use the official layer in my Lambda functions because it is not published in the af-south-1 region. The problem is even worse for the ARM64 layer as it is published to fewer regions
Describe the solution you'd like

Publish the official AMD64 layer to these regions:

af-south-1
eu-south-1

Publish the official ARM64 layer to these regions:

us-west-1
eu-west-3
eu-north-1
eu-south-1
ca-central-1
af-south-1
sa-east-1

Describe alternatives you've considered

Build from source and publish as a custom layer
Publish a copy of an official layer in another region as a custom layer in the desired region

To publish a copy of the official layer as a custom layer:

Get the S3 URL for the custom layer
Get the ARN for the custom layer in a supported region
- AMD64: arn:aws:lambda:us-east-1:901920570463:layer:aws-otel-nodejs-amd64-ver-1-6-0:1
- ARM64: arn:aws:lambda:us-east-1:901920570463:layer:aws-otel-nodejs-arm64-ver-1-6-0:1
Get the S3 URL for the layer: aws --region us-east-1 lambda get-layer-version-by-arn --arn <arn> --query Content.Location --output text
Download the layer: curl -o layer.zip <url>
Publish the layer in your own account in the desired region: aws --region <desired-region> lambda publish-layer-version --layer-name "aws-otel-nodejs-<arch>" --compatible-runtimes nodejs12.x nodejs14.x nodejs16.x --compatible-architectures <arch> --zip-file fileb://layer.zip

Is it possible to publish layer to cn-north-1 region also?

Thank you for creating this issue, we are currently working to support more regions and shall update the correspondence here with any developments.


[ENH] Add switch to test and report out both APIs

Add switch to test and report out both APIs
A lot of time installing and testing new frameworks/integrations is often spent initially on getting API Access, Keys, Proxies, et al sorted out.

It would great if there were an API Test feature we could invoke to enumerate and test all aspects of both CrowdStrike and MISP APIs.
This would include creating a Test Event, Attributes, and some Tags on the MISP side.  Option for the Deletion or Retention of these artifacts after the fact would be great.
Detailed logging/error messages please!

The current form of logs are less than helpful.
[2022-11-09 11:24:42,361] CRITICAL config  authentication                              Invalid API credentials provided

This should be doable.  It'll be configured to execute only if the related argument is provided. (Whereas the config check tests will run every execution.)
Adding this to the punch list.


Unit of Measure not returned in API

During testing we recognized the Unit of Measure, although defined is not returned in the API.
It would be very welcomed if it was returned.
Regards,
PeterK

unit is part of ConceptDescription with data specification IEC61360 and specified as such
So far there is not other data specification (in former versions there was a data specification for physical units as well but not in V3.0, it is planned)
I consider this issue to be invalid


Disable a few cops

Style/AsciiComments (because why limit comments to only ASCII?)
Style/ParallelAssignment (because @a, @b = a, b in initializers is awesome)
Style/MultilineBlockChain (because having a block within a method chain seems perfectly reasonable to me)

Looks like Rubocop's latest config doesn't enable AsciiComments, so that's cool. The other two are now disabled in v0.3.


Update dependency 'vis'

You are still using a very outdated version 4.21 of vis.
This version is not supported anymore!
Please update to the new libraries:
https://github.com/visjs
Feel free to contact us if you need any support during the transition :-)

Hi, thanks for the issue.
Should be done with this commit: dhttps://github.com/ES-Community/nsecure/commit/d0db811234ebe5b40f0aa0035cd2bdd4d7c51d84


doc column type mapping for map&struct types

Proposed changes
Add column type mapping for map&struct types.
Checklist(Required)

[ ] Does it affect the original behavior
[ ] Has unit tests been added
[x] Has document been added or modified
[ ] Does it need to update dependencies
[ ] Is this PR support rollback (If NO, please explain WHY)

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

run buildall

run P0


Info.Blockchain.API.Client.ClientApiException

fail: Microsoft.AspNetCore.Diagnostics.ExceptionHandlerMiddleware[0]
An unhandled exception has occurred: In order to create wallets, you must
provide a valid service_url to BlockchainApiHelper
Info.Blockchain.API.Client.ClientApiException: In order to create wallets, you m
ust provide a valid service_url to BlockchainApiHelper
at Info.Blockchain.API.Client.BlockchainApiHelper.InitializeWallet(String ide
ntifier, String password, String secondPassword)
do i need to host the app, before testing the api?

Can you please comment the code that throws this?

To use the wallet methods you must run service-my-wallet-v3 locally.

how can i run service-my-wallet-v3 locally, Please
On Mon, Oct 16, 2017 at 8:44 PM, Assaf Yossifoff<EMAIL_ADDRESS>wrote:

To use the wallet methods you must run service-my-wallet-v3
https://github.com/blockchain/service-my-wallet-v3 locally.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/blockchain/api-v1-client-csharp/issues/34#issuecomment-337013517,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ANlYrVwkSD_nzx8ASRj1frN_-r3IB8dVks5ss7IPgaJpZM4P3P9s
.

You need nodejs and npm installed, then run
npm install -g blockchain-wallet-service
then
blockchain-wallet-service start
The full instructions can be found here.

i did that, it was still giving this error " you m
ust provide a valid service_url to BlockchainApiHelper".
here is the code:
public async Task generateWallet()
{
using (BlockchainApiHelper apiHelper = new BlockchainApiHelper(apiCode:
"1770d5d9-bcea-4d28-ad21-6cbd5be018a8", serviceUrl: "http://<IP_ADDRESS>:3000"
))
{
var wallet = apiHelper.InitializeWallet(
"96b33067-12e0-4375-b8b8-2776445632a2f8", "fgdfhfgh");
BitcoinValue totalBalance = await wallet.GetBalanceAsync();
return Ok(totalBalance.GetBtc());
}
}
On Tue, Oct 17, 2017 at 9:38 AM, Assaf Yossifoff<EMAIL_ADDRESS>wrote:

You need nodejs and npm installed, then run
npm install -g blockchain-wallet-service
then
blockchain-wallet-service start
The full instructions can be found here
https://github.com/blockchain/service-my-wallet-v3#installation.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/blockchain/api-v1-client-csharp/issues/34#issuecomment-337159912,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ANlYrVFslEQK8ptszUIc4ctC_SxwR2Bbks5stGd-gaJpZM4P3P9s
.

how can i track payments?

How can i implement payment receiver?
On Tue, Oct 17, 2017 at 11:16 PM, Oyerinde abolaji taoheed <
<EMAIL_ADDRESS>wrote:

i did that, it was still giving this error " you m
ust provide a valid service_url to BlockchainApiHelper".
here is the code:
public async Task generateWallet()
{
using (BlockchainApiHelper apiHelper = new BlockchainApiHelper(apiCode:
"1770d5d9-bcea-4d28-ad21-6cbd5be018a8", serviceUrl: "http://<IP_ADDRESS>:3000
"))
{
var wallet = apiHelper.InitializeWallet("96b33067-12e0-4375-b8b8-
2776445632a2f8", "fgdfhfgh");
BitcoinValue totalBalance = await wallet.GetBalanceAsync();
return Ok(totalBalance.GetBtc());
}
}
On Tue, Oct 17, 2017 at 9:38 AM, Assaf Yossifoff<EMAIL_ADDRESS>
wrote:

You need nodejs and npm installed, then run
npm install -g blockchain-wallet-service
then
blockchain-wallet-service start
The full instructions can be found here
https://github.com/blockchain/service-my-wallet-v3#installation.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/blockchain/api-v1-client-csharp/issues/34#issuecomment-337159912,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ANlYrVFslEQK8ptszUIc4ctC_SxwR2Bbks5stGd-gaJpZM4P3P9s
.

The same problem. It continues throwing exception from my app, even when i send request trough my browser, and localhost server ANSWERS! Nodejs is running well
What could it be?

Omg, code of API Helper is a really strange thing. All params appears optional, but to make it all work, i had to add serviceHttpClient and apiCode.
But in code example was showed, that only serviceUrl and api_code are required.

Pls, how can i integrate ethereum or BCH using blockchain


Add new 'yaml_file' resource

A resource for writing out YAML files would replace many of the use of templates or the file resource to write these out from strings. It would be an extension of the file resource, replacing the content with a hash and keeping all the existing properties.
Motivation
As a user, I want to pass a hash of attributes to a yaml_file resource and have it render them appropriately.
Specification
a = {
    'golf': 'hotel',
    'kilo': ['lima', 'mike', 'november'],
    'india': {
        'juliett': true
        },
    'alpha': {
        'charlie': 'delta',
        'bravo': 10,
        },
    'echo': 'foxtrot'
    }

yaml_file '/tmp/file.yaml do
    content a
end

produces the file /tmp/file.yaml
---
golf: hotel
kilo:
- lima
- mike
- november
india:
  juliett: true
alpha:
  charlie: delta
  bravo: 10
echo: foxtrot

Example implementation with tests here: https://github.com/mattray/yaml-cookbook

closing to track in #9911

a new helper for handling this has been added for 17.3


feat(documentation): restructurs components folder now contains subfolders Forms, Ions, Internet and Intranet Header

Alternative Version to #2172 .
Was chosen and as discussed the headers and the icons documentation are now also subfolders of components.

To prevent manually maintaining order we could think about renaming "Getting Started" stories to "_Getting Started" or sth similar that way we could have the components folder sort without interferance. The way it is right now the previwe.ts fille needs to ne manually updated every time a story with a lower asci value than "Intranet Header" is added.


STORM-2131: Add blob command to worker-launcher, make stormdist directory not writeable by topo owner

Re-opening this, as I reverted the last one to fix a typo (#1723)

Leaving a note: #1697 needs to pull this to apply the change for 1.x.

@kishorvpatil @revans2 @jerrypeng

+1

+1 looks good


ReferenceError: FOO is not defined

Description
When trying to add a const in my mdx and use that in my component I get ReferenceError: FOO is not defined. But the const is being used in my component.
Reproduce
Button.jsx
import React from 'react';
import PropTypes from 'prop-types';

const Button = ({ text }) => (<button type="submit">{text}</button>);
Button.propTypes = {
  text: PropTypes.string.isRequired,
};
export default Button;

Button.mdx
---
name: Button
route: /Components/Button
menu: Components
---

import { Playground, PropsTable } from 'docz'
import Button from './Button'
const FOO = 'HELLO'

# Button

<PropsTable of={Button} />

## Basic usage

<Playground>
  <Button text={FOO}></Button>
</Playground>

Result

There's no possible to use declarations like const, functions inside mdx, just import from another files. What you can do to declare variables is pass a function as a children for your Playground or use getInitialData to attribute something on document scope:
---
name: Button
route: /Components/Button
menu: Components
---

import { Playground, PropsTable } from 'docz'
import Button from './Button'

# Button

<PropsTable of={Button} />

## Basic usage

<Playground>
  {() => {
    const foo = 'foo'
    return <Button text={foo}></Button>
  }}
</Playground>

or
---
name: Button
route: /Components/Button
menu: Components
---

import { Playground, PropsTable } from 'docz'
import Button from './Button'

export const getInitialData = () => ({
  foo: 'FOO'
})

# Button

<PropsTable of={Button} />

## Basic usage

<Playground>
  <Button text={props.data.foo}></Button>
</Playground>


[ABORTED] v2 - App rewriting

v2
Main changes:

New UI
Use a single app window for multiple connections, this way the app requires less memory to run all the connections
Dark and Light themes
Make the app more stable
A decent test coverage
Basic analytics

This branch will be used for the v2 implementation while all these required features have not been implemented yet:

[ ] Test coverage 80% minimum
[ ] Themes

[ ]  Dark theme (in progress)
[ ]  Light theme (will be done after dark theme is complete)

[ ]  Basic analytics
[ ]  Settings page
[ ]  Manage server connection

[ ]  Basic form
[ ]  Import connection from URI
[ ] Duplicate connection

[ ] Connection

[x]  Connect to a server database
[ ]  SSH Connection
[ ]  Open a new database connection from an open server connection
[ ]  Multiple server connections open in the same window
[ ]  Passphrase connection prompt
[ ] Refresh connection

[ ]  Logs bottombar panel
[ ]  Toggle sidebar panels
[ ] Connection left sidebar panel

[x]  List tables
[ ]  List functions

[ ]  Content main panel (table records)
[ ]  Structure main panel (columns, indexes)
[ ]  Query main panel

[x]  wysiwyg SQL editor (monaco editor)
[x] Auto complete SQL keywords
[ ] Auto complete tables and columns
[ ]  Multiple query tabs
[ ]  Export to CSV and JSON
[ ]  Copy to clipboard as CSV and JSON
[ ]  Auto save query

[ ]  Table info main panel
[ ] Selected row right sidebar panel
[x]  Resizable panes

Develop

Pull project

Switch to this branch

Install deps yarn

Start the project yarn start

While the connections management has not been implemented yet, it will require an existing ~/.sqlectron.json file to list and connect to databases.

Next
List of features that won't make into v2, but are being considered for future releases:

Store passwords in the key chain
Update fields from selected rows

I aborted the rewriting from scratch because it would take too long to do it. I still plan to do those improvements but in batches over the existing codebase. I am keeping this PR around for now just because there is some work that I did here which I intend to copy.

Could you make issues for the discrete bits of work you were planning or have done in the branch? Just to make it easier to track and so possibly others might be able to contribute / comment.


[BUG]: convert from MP4 to M4A reducing quality

Which tool
tidal-gui
Version
<IP_ADDRESS>
Platform
Windows
Describe the bug
When using the convert mp4 to m4a, it seems you are using ffmpeg to actually re-encode the audio to a lower quality.
Instead, you can use ffmpeg to just extract the audio stream as-is without re-encoding, using the "-acodec copy" option.
This keeps it at full quality & also takes much less time.
Depending on the player... just renaming the file will probably work too...
Relevant log output
No response
Add screenshots
No response

Indeed!
But on the other hand you probably don't loose too much quality as both are capped at 17Khz and pretty much similar in quality.

Audio
ID                                       : 1
Format                                   : AAC LC
Format/Info                              : Advanced Audio Codec Low Complexity
Codec ID                                 : mp4a-40-2
Duration                                 : 2 min 44 s
Duration_LastFrame                       : -18 ms
Bit rate mode                            : Constant
Bit rate                                 : 320 kb/s
Channel(s)                               : 2 channels
Channel layout                           : L R
Sampling rate                            : 44.1 kHz
Frame rate                               : 43.066 FPS (1024 SPF)
Compression mode                         : Lossy
Stream size                              : 6.29 MiB (96%)
Default                                  : Yes
Alternate group                          : 1```

![image](https://github.com/yaronzz/Tidal-Media-Downloader-PRO/assets/17104473/b84f6ad4-c5de-4899-9437-0ff1a9523f5f)

The best thing is to download the flac Edition and convert into mp3 V0 yourself!
Here is a V0 mp3 and Quality 5 AAC
![image](https://github.com/yaronzz/Tidal-Media-Downloader-PRO/assets/17104473/6669c25d-7c73-49d7-822c-48b15918f8a1)


Change method of dark mode for jacksonchen666.com

It's using color-scheme, which technically isn't a media query.

Website (if applicable): https://jacksonchen666.com
This PR is:

[ ] Adding a new domain
[x] Updating existing domain
[ ] Changing domain name
[ ] Removing existing domain from list
[ ] Website code changes (darktheme.club site)
[ ] Other not listed

[x] The domain is in the correct alphabetical order
[x] The following information is filled identical to the data file

I confirm that I have read the FAQ page, particularly the red section about inappropriate content, and I attest that this site is appropriate based on those criteria.

[x] Check to confirm

- domain:
  url:
  method:
  last_checked:

Wow, I didn't know about this property yet! Might be worth adding a new category for this.🤔


"no-unused-prop-types" inside async functions (include arrow)

Hi!
I think there is a bug with async functions.
property: "no-unused-prop-types"
parser<EMAIL_ADDRESS>where: "async functions"
example:
{
  code: [
    'export class Example extends Component {',
    '  static propTypes = {',
    '    failed: PropTypes.func.isRequired,',
    '    loadUserProfile: PropTypes.func.isRequired,',
    '  }',
    '  handleLogin = async () => {',
    '    await this.props.failed();',
    '    await this.props.loadUserProfile();',
    '  };',
    '}'
  ].join('\n'),
  parser: 'babel-eslint'
},

Some additional info which might help:
this will error:
onSubmit = async (e) => {
    this.setState({loggingIn: true, success: false, message: null})

    const {email, password} = this.state
    const {login, setAuthenticated} = this.props // not detected by eslint

    const {success, message} = await login(email, password)

    this.setState({loggingIn: false, success, message})
    setAuthenticated(success)

    if (success) {
        const {router, location: {state: {nextPathname} = {}}} = this.props

        setTimeout(() => {
            router.push(nextPathname || '/')
        }, 1000)
    }
}

this will not error:
onSubmit = async (e) => {
    this.setState({loggingIn: true, success: false, message: null})

    const {email, password} = this.state
    // properly detected by eslint
    const {login, setAuthenticated, router, location: {state: {nextPathname} = {}}} = this.props

    const {success, message} = await login(email, password)
    this.setState({loggingIn: false, success, message})
    setAuthenticated(success)

    if (success) {
        setTimeout(() => {
            router.push(nextPathname || '/')
        }, 1000)
    }
}

The only difference between these snippets is how this.props is destructured. In the first example, location and router props are destructured separately, and in the second example all props are accessed together. This is probably not the whole solution, since @isnifer isn't destructuring at all. But mabe you can try and see if this works;
{
  code: [
    'export class Example extends Component {',
    '  static propTypes = {',
    '    failed: PropTypes.func.isRequired,',
    '    loadUserProfile: PropTypes.func.isRequired,',
    '  }',
    '  handleLogin = async () => {',
    '    const {failed, loadUserProfile} = this.props;',
    '    await failed();',
    '    await loadUserProfile();',
    '  };',
    '}'
  ].join('\n'),
  parser: 'babel-eslint'
},

export default class Users extends Component {

  static propTypes = {
    ...
    onLoad: PropTypes.func.isRequired,
  };

  async componentWillMount() {
    const onLoad = this.props.onLoad;
    ...
  }

  ...

}

''onLoad' PropType is defined but prop is never used (react/no-unused-prop-types)'

@TrevorSayre similar for me — using<EMAIL_ADDRESS>


Update to 0.9.0

Can we please add Keptn 0.9 here and default to this version?

Keptn 0.9.x tutorial installs old Keptn version

Link is broken

goes to https://deploy-preview-182--keptn-tutorials.netlify.app/tutorials/keptn-quality-gates-prometheus-09/index.html?index=..%2F..keptn09x

Deployment preview for reference: https://deploy-preview-182--keptn-tutorials.netlify.app/keptn09x

Quite an outdated screenshot ;)

Outdated example repository

The link is broken (it refers to 0.9.x which is not yet available but this is not the root cause).
Is the command keptn onboard service still available in 0.9?

looks good in general :)
one minor thing that should be adapted is the following screenshot


[BUG]: TypeError: Cannot read properties of undefined (reading 'match')

Issue/Experience
I just discovered this course. So i followed step to build docker and to run course
The problem is that, from 'homepage' , when click on first link I got this

In the console I can see  this
root@49b33d235a9f:/workspace/solana-curriculum# cd . && NODE_ENV=production node ./.freeCodeCamp/tooling/server.js
🔵 INFO:  2022-11-11 07:20:01 Listening on port 8080
🔵 INFO:  2022-11-11 07:20:03 Watching for file changes on /workspace/solana-curriculum
file:///workspace/solana-curriculum/.freeCodeCamp/tooling/parser.js:200
  const mat = lesson.match(
                     ^

TypeError: Cannot read properties of undefined (reading 'match')
    at parseMarker (file:///workspace/solana-curriculum/.freeCodeCamp/tooling/parser.js:200:22)
    at getLessonDescription (file:///workspace/solana-curriculum/.freeCodeCamp/tooling/parser.js:62:23)
    at runLesson (file:///workspace/solana-curriculum/.freeCodeCamp/tooling/lesson.js:35:23)

Node.js v18.12.1

I already tried to shutdown the course and the restart.
This time, the home immediately changed into the server error page.
The first time, It 'waited' for one my click, I think.
Output of running node tooling/camper-info.js from the workspace root
🔵 INFO:   Project:  learn-how-to-set-up-solana-by-building-a-hello-world-smart-contract
🔵 INFO:   Lesson Number:  1
🔵 INFO:   Curriculum Version:  0.1.1
🔵 INFO:   freeCodeCamp - Courses<EMAIL_ADDRESS>🔵 INFO:   Commit:  5cb8211 fix(deps): update rust crate solana-program to 1.14.7
🔵 INFO:   OS Info:
Architecture: x64
Platform: linux
Release: 5.15.49-linuxkit
Type: Linux

Same problem on home pc and on work pc, 2 different pc, always windows 11, always docker in Hyper-V mode.
I am rebuilding and retrying. Then I'll post the esit of the command

Nothing changed (I also noticed your team pushed 2 commits, I was hoping but ... nothing changed)

root@d41076afcf7e:/workspace/solana-curriculum# cd . && NODE_ENV=production node ./.freeCodeCamp/tooling/server.js
🔵 INFO:  2022-11-11 12:45:57 Listening on port 8080
🔵 INFO:  2022-11-11 12:46:01 Watching for file changes on /workspace/solana-curriculum
file:///workspace/solana-curriculum/.freeCodeCamp/tooling/parser.js:200
  const mat = lesson.match(
                     ^

TypeError: Cannot read properties of undefined (reading 'match')
    at parseMarker (file:///workspace/solana-curriculum/.freeCodeCamp/tooling/parser.js:200:22)
    at getLessonDescription (file:///workspace/solana-curriculum/.freeCodeCamp/tooling/parser.js:62:23)
    at runLesson (file:///workspace/solana-curriculum/.freeCodeCamp/tooling/lesson.js:35:23)
    at async FSWatcher.<anonymous> (file:///workspace/solana-curriculum/.freeCodeCamp/tooling/hot-reload.js:47:7)

Node.js v18.12.1

Note: the output is the same when executing develop course
root@d41076afcf7e:/workspace/solana-curriculum# NODE_ENV=development node ./.freeCodeCamp/tooling/server.js
🔵 INFO:  2022-11-11 12:48:34 Listening on port 8080
🔵 INFO:  2022-11-11 12:48:36 Watching for file changes on /workspace/solana-curriculum
file:///workspace/solana-curriculum/.freeCodeCamp/tooling/parser.js:200
  const mat = lesson.match(
                     ^

TypeError: Cannot read properties of undefined (reading 'match')
    at parseMarker (file:///workspace/solana-curriculum/.freeCodeCamp/tooling/parser.js:200:22)
    at getLessonDescription (file:///workspace/solana-curriculum/.freeCodeCamp/tooling/parser.js:62:23)
    at runLesson (file:///workspace/solana-curriculum/.freeCodeCamp/tooling/lesson.js:35:23)

Node.js v18.12.1
root@d41076afcf7e:/workspace/solana-curriculum#

If needed:

I add that after updating repo ad rebuilding the freecodecamp extension is no more installed.
something is broken

Thank you for all of the information. However, I am still unable to reproduce any issue.
The most likely cause for that message is a failure to copy the workspace contents during the docker build. That is, Docker did not successfully copy the necessary files from your local fs to the container.
You might have success running this course in Gitpod:
https://user-images.githubusercontent.com/51722130/201417516-cc902319-fa48-453d-89dc-2e730ee426ae.mp4

I am closing this as stale. I have been unable to reproduce this issue, and there does not seem to be many more coming into this problem.


feat: add embed limitations in the embed tag

Is your feature request related to a problem? Please describe.
The embed tag does nit give information about limitations in an embed.
Describe the solution you'd like
I was thinking about writing the character limitations on the embed
Describe alternatives you've considered
.
Additional context
.
Note : I'm working on it

added in 4ffb485


Save demo state in localStorage

This restores the save-state behavior of the old editor rather than reverting to the default state every time.

Updated to merge options rather than replacing.
I added lodash as a script dependency for this because it seems like writing our own recursive merge function probably isn't worthwhile. I can remove it if anyone has objections to doing this.

I think we need to extract just defaultsDeep function from lodash. All of the dependencies have to be downloaded by the client on every demo load. And lodash is 25k minified and gziped, which is not a small amount at all. Also, could you add checks around localStorage access? I think localStorage is not available for privacy browsing.

I think localStorage is not available for privacy browsing.

I'm pretty sure it's still available, it just uses a separate storage instance.

I believe Safari in private browsing mode will throw an error if you try to write to localStorage: https://stackoverflow.com/questions/14555347/html5-localstorage-error-with-safari-quota-exceeded-err-dom-exception-22-an
This is the method I've used to check whether it's available: https://gist.github.com/paulirish/5558557#stronger-full-capability-test-for-localstorage-with-ios-private-browsing-protection

Huh, that's odd. Ok, I'll add a check for it.


Datetime arithmetic

Now that 67021bc7c19b17ef4db99b491d0dfa488d3f2586 has landed, precise Datetime arithmetic should be implemented. The API will offer high precision operator (read: leap second will be correctly handled) as well as higher construct (e.g. add a month).
I'm aiming at implementing the API so that the following snippet is possible:
let utc = tzdata::Timezone::utc();
let t = utc.datetime(2015, 6, 30, 0, 0, 0, 0);

let add_86400_secs = t + tzdata::Deltatime::seconds(86400);

assert_eq!(add_86400_secs.date(), (2015, 6, 30));
assert_eq!(add_86400_secs.time(), (23, 59, 60, 0));

Feature added in 4f581c2ebbbf4e377bbbe3d76dbf7e8cf72e7f7e


include column_sizes in stats columns

this is for Issue #269
My understand is that column_sizes was calculated by ParquetUtil.footerMetrics or ParquetUtil.fileMetrics but calling table.newScan().includeColumnStats() is still not populating.
@aokolnychyi if you want to review, please.

LGTM. Thanks, @manishmalhotrawork!

@rdblue please see, if we can merge it. thanks !

Looks great, thanks for fixing this @manishmalhotrawork!

@aokolnychyi @rdblue for review and all the help !


Not using the word 'topics'

What do you need?
We probably need a content style guide entry to instruct against using the word 'topic/s' and why – especially in navigational areas, and potentially in body text too.
What is the problem?
I've asked Donna to add more info to this ticket when she can. In the meantime...
The words 'topic' and 'topics' are problematic and could create user confusion between topic in the general sense and topic as a kind of system noun.
In general, we don't label a topic (system noun) as a 'topic'. We've also been avoiding referring to other topics.
Which entry/section is this related to?
I'm not sure – it might need it's own entry.
Good example
We've been experimenting with terms like 'Information and services', 'Related information', 'More information', 'You might also like/need' etc (but those ones may need further discussions too).

The basic reason is that 'topic' is our jargon. For us a topic is a hierarchy of information pages on a single thing. The word is used differently in general use and by similar organisations like uk.gov (to them a topic is a page). However, it will be easy for us, and for authors in the future, to slip it into the interface. Users won't know what it relates to :) When we are tempted to use it in the interface, think about what we are trying to tell people - are we trying to differentiate between different types of resources (gov.au and external resources), label a set of tags on a news story, label a set of related links - then think of how better to help them understand what they are looking at.

Come back to with Michael

Hi @joolswood, do you need more from me? Does the above not cover it?

@michaelhugill not necessarily; I was just assigning issues for discussion at the next CC to the people who created the ticket so they could talk to the item.

@joolswood Sounds good. Let's discuss at next CC.

We decided this is an internal content issue - not for content guide at the present.


Update Slack bridge dependency and make it work on macOS.

Merged, thanks @rht!  Can you follow up with the original issue reporter to confirm whether this fixes it for them on their macOS system?

@chrisbobbe said it worked on his macOS system.


Units: mois/an & points/point… don't simplify automatically

Repro case:
const myRules = `euros: 1 €
points: 5 points
point: 5 point
mois: 24 mois
an: 2 an`

const myEngine = new Engine(myRules)

// Returns a nodeValue of 12 instead of 1, and a complex unit like €.points.mois/point.an
myEngine.evaluate('euros * points / point * mois / an')

Same goes with the following:
engine.evaluate({valeur: 'euros * points / point * mois / an', unité: '€'})

By the way, in the last case, it seems "unité" is not validated for correctness against the inferred unit).
We would expect both evaluations above to yield a nodeValue of 1 and a unit of €.

Seems fixed
https://publi.codes/studio/bug?code=euros%3A+1+€
points%3A+5+point
point%3A+5+point
mois%3A+24+mois
an%3A+2+an

bug%3A+euros+*+points+%2F+point+*+mois+%2F+an


Adds quotes to source pip install

This PR adds quotes to the pip install from the "Install from Source" section of the docs

Looks good to me.  Thanks @jrbourbeau !


Best way to prevent arithmetic overflow/underflows during rewriting?

Hi !
In this example I have a simple constant folding rule:
(datatype Math
  (Num i64)
  (Add Math Math)
)
(rewrite (Add (Num x) (Num y)) (Num (+ x y)))
(let expr (Add (Num<PHONE_NUMBER>854775807) (Num<PHONE_NUMBER>854775807)))
(run 4)
(extract expr 2)

I can trigger  overflows on i64 addition
(
   (Add (Num<PHONE_NUMBER>854775807) (Num<PHONE_NUMBER>854775807))
   (Num -2)
)

It seems like egglog does not try to detect overflows/underflows on either i64 or rationals (which are pairs of i64), or occurences of nans/+inf on f64.
I'm trying to use egglog to simplify mathematical expressions over mathematical Ints and Rationals, so to ensure soundness I'd like to either (from worst to best):
.1 detect overflows during rewriting and trigger panics
.2 guard against applying constant folding rules if they would trigger overflows/underflows
.3 replace the i64, rationals and f64 with arbitrary precision equivalents (think GMP, MPFR, etc. )
I know that .3 is not possible without modifying the egglog source code, but would either 1 or 2 be possible as of today ?
How do people usually ensure soundness with that type of constant propagation rules ?
Thanks !

Great question!
2 is certainly possible today by adding conditions to the rule.
1 and 3 require changing the primitive implementation, as you said. I think that you don't actually have to change egglog though, there are public rust APIs for adding new primitives (not well documented unfortunately)

2 is certainly possible today by adding conditions to the rule.
Can that be done from the egglog DSL or do we need to do that through the Rust API ? The overflow conditions would require disjunctions and references to i64::MAX or i64::MIN. It seems like the DSL only supports conjunctions as guards.

there are public rust APIs for adding new primitives (not well documented unfortunately)
Do you have a pointer to the API in question ?

Here's the API I was thinking of:
https://docs.rs/egglog/latest/egglog/struct.EGraph.html#method.add_primitive
Let us know if there are problems with it or things that we forgot to make public!

I was imagining doing 2 from the egglog DSL, defining a max and min int yourself using globals
There is a boolean or in egglog, defined here: https://github.com/egraphs-good/egglog/blob/main/src/sort/bool.rs
We could really use some documentation of the primitive operators!

There's also a bool-> here: https://github.com/egraphs-good/egglog/blob/ecc3be54fd7a073d0bd052bdbc7788009e53c635/src/sort/i64.rs#L58
It produces a boolean instead of an egglog filter

Thank you !

If there was a way to add over/underflow protection to the builtins here as well I could see that being useful generally!

egglog has BigInt and BigRat now.

Great!

Also https://github.com/egraphs-good/egglog/pull/502 just changed primitive i64 ops to at least not panic on overflow, but just consistently fail.


Barricade welding parity

About the PR

Barricades now use the RMCRepairableSystem, which has been worked on to include what they need:
They take 5 seconds with 2 construction skill and 10 with anything lower.
They use 2 fuel on repair.
They heal only 200 health.
You can only weld 1 at once.
Why / Balance

parity! Fixes #3437, addresses parts of #4460. Boilers can't be avoided with a single ComTech :p
Technical details

Added fuel support to RMCRepairableSystem. Comp has it at 0 as alot of things in CM check it for if a welder is on and has ANY fuel.
Added skill defs for construction as that's whats used for barricade welding.
Media

Requirements

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

https://github.com/user-attachments/assets/258e98a4-756b-4a8a-9857-33e716683002
https://github.com/user-attachments/assets/1f56f0ca-13a1-4f3e-9bda-2e17afaadbb0
(First is with con skill 2 and second is with none)
Breaking changes

Changelog

:cl:

fix: Fix being able to repair multiple cades at once. Welders also use the proper amount of fuel for this, and isn't canceled by damage.
fix: Cades now heal 200 health on weld instead of all their health. They also now take 5 seconds to weld with construction skill 2 and 10 with 1 or 0 skill.
fix: You can no longer weld sentries with a turned off or empty welder.

xenos are so back no more instantly fixing 10 cades at once in a second


Can't boot into Windows (INACCESSIBLE_BOOT_DEVICE)

After deploying the latest version of Windows, it brings up a BSOD that has the error "INACCESSIBLE_BOOT_DEVICE"... any suggestions?
Image
Edit: I just remembered I can use older versions of windows, so I'm trying 1803

just deployed a fresh 1903, booted fine


Feedback for: Setting Up the Labs [en]

https://github.com/google/WebFundamentals/blob/master/src/content/en/ilt/pwa/setting-up-the-labs.md
@petele
The "Set up Node and install the lab repository" section has multiple formatting issues. The bullets & numbers are messed up, and code is not in code blocks. There might be one issue early on that is propagating down the rest of the section/doc?
Source reference:
https://google-developer-training.gitbooks.io/progressive-web-apps-ilt-codelabs/content/docs/setting_up_the_labs.html#set-up-node-and-install-the-lab-repository

Merging to #4261


PC-489: Change supplier portal session duration to 15 minutes

Extends session duration from 10 to 15 minutes

I'm a bit surprised we're doing 10 => 15; feels kinda insignificant. But if that's what people are happy with then change looks fine.

Yeah, I think a few complaints around session duration were received from suppliers around being logged out, but this is the maximum we can increase it to while still adhering to national cyber-security guidelines.


Grafana variable queries do not work(Grafana 8.0.2 +grafana-sqlite-datasource 1.2.1)

Hello Sergei,
i need your help.
Today I have installed new Grafana version 8.0.2 with grafana-sqlite-datasource 1.2.1 and since then the Grafana variable queries do not work.
With Grafana version 7.4.3 + grafana-sqlite-datasource 0.2.7 everything works.
It also does not work with Grafana version 8.0.2 + grafana-sqlite-datasource 0.2.7.
Did you get an idea ahead of it?
Grafana version 7.4.3 + grafana-sqlite-datasource 0.2.7: everything is okay

Grafana version 8.0.2 + grafana-sqlite-datasource 1.2.0: does not function

Grafana 8 is simply not supported yet.
I'll try to get a version out that supports Grafana v8 and earlier versions to but until then the only reliable way to use the plugin is with Grafana >=7.3.3 & <8.0.0

Hello Sergej,
thank you for the information.

Grafana 8 is simply not supported yet.

Ok, above statement was in relation to grafana-sqlite-datasource 1.2.0.
What about grafana-sqlite-datasource 2.0.0  ?  Does it support Grafana 8 ?

v2.0.0 of the plugin was also still developed without v8 of Grafana in mind.
I improved the tests a bit yesterday and with that, I should be able to support different versions of Grafana more easily.
I'll try to get a new version of the plugin out with support for Grafana v8 soonish but as of right now there is no plugin version, which I tested against v8 and therefore I cannot say anything about compatibility 🤷🏻

Thanks..... and no problem....and no rush
Will roll Grafana back to V7 and try again.
Would be good to add some hints here that Grafana8 is not supported

More people encounter the issue: discussed at grafana forum.
Looking forward to a plugin version that supports Grafana v8.

Can you try this release: https://github.com/fr-ser/grafana-sqlite-datasource/releases/tag/v2.0.2
It should be fixed but it takes a while for the plugin to be available on the grafana page
You can try this installation: https://github.com/fr-ser/grafana-sqlite-datasource#installing-the-newest-plugin-version-on-an-existing-grafana-with-the-cli

Seems to be working now.
Thanks for the fix!


The written voxel GRO file is not aligned (scaled) with the atomgroup

It would be super nice if the voxel grid GRO files and the molecular structure files would be super imposable.

Indeed! That would be very useful for visualization. :)

It appears this was already a feature that was more or less supported as one could give a scaling factor. To make this more easier we now also support giving a universe to the voxels_to_gro function, which autoscales to make the voxel grid match the dimensions of the input point cloud.


How to programmatically Invoke a Command with Custom Context

I’m trying to figure out how to invoke a command programmatically. Is there a relatively simple way to do this currently, or would I need to create a workaround?
Use Case Example:
Let’s say I have a command that allows users to create buttons. When a user clicks a button, it should invoke a specified command. I’d like to be able to pass in the relevant context programmatically (e.g., the channel, user, etc.) so the command can execute with that context.
Is there a built-in way to do this, or should I consider hacking something together?

Lets not open multiple issues for one thing please.


Feature Request: Support for Clickhouse Dictionary

Hi! Are there any plans to support Clickhouse Dictionaries?

Hi @RuiLoureiro,
We released support for dictionary yesterday. You can find the documentation here.
Thank you for requesting this! Let us know if you encounter any issues.


Multiple repo display should be altered

Hi, love this app. There's a feature request:
When I add multiple repos, and if I haven't worked some of the repos, it shows the message:
Seems like %username% did nothing! for each blank repo. However I have commits overall 😢
It's ok to tell me that if I haven't worked in any of the repos but current behaviour is somehow heart-breaking and makes me feel like a lazy person 😞
This issue can be related to #17, since you said you plan to add a parent directory feature. It would be awesome.
Related image (5 repos, 1 new commit in 1 repo):

Awwww I'm sorry about that! That error actually comes from git-standup, not me :(

Could we maybe intercept this output and make it say something like, No history found for %user%. And only say it once instead of repeated.
I'll look into that if it sounds reasonable.

Already fixed this -- skipped the repo altogether.


jsPsych.randomization.getRandomInt

a getRandomInt function I end up using a lot, so thought it might be a good addition to the randomization module. I understand that users can create their own array of integers (or numbers) to sample and then use jsPsych.randomziation.sampleWithoutReplacement but creating an array on the fly is cumbersome in javascript (unlike list comprehensions in python, say).
Is it worth expanding it to include other distributions as well?

Thanks @nikbpetrov - this does look useful. And I agree that dynamically creating an array of numbers between two values is annoying in JavaScript!
I'm guessing that a uniform sampling distribution is the main one that people might want/need (if that's what you mean about expanding to other distributions). Or maybe you know of common-ish use cases for other sampling distributions?

Circling way back to this. There are some js libraries for sampling distributions, e.g., jStat. Someone could use that in their project. So I guess the question is how much of an extra convenience is it to have these functions just available in jsPsych.randomization? I'd be open to the idea of including at least some of the most common needs, like the random int, or samples from a normal distribution.

 Thanks for the suggestion @nikbpetrov !


Related to #134

Same thing with reg as with wire.
module task_bug ( in_data, do );

   input [15:0] in_data;
   output [15:0]  do;
   reg [15:0] out_data;

   assign do = out_data;

   always @ (*)
     begin

    Test_task(in_data, out_data);
         // out_data = in_data; // This works but above task doesn't

     end

   task Test_task;
      input [15:0]  in_d;
      output [15:0] out_data;

      begin
        out_data = in_d;
      end
   endtask

endmodule

Are you sure that this is not fixed by 5328a851490588d6162ca0edaad5ed713bc75401, which fixed #134? I for one cannot reproduce any problem in this code with current git head. I'm closing this now. Please re-open if you think there is still a problem.


Tweak logging in NIOSessionParser + subclasses

Forces NIOSessionParser subclasses to log using their class name,
to make it clear which class the message originate from.
make the logger in NIOSessionParser private
add a logger for FillingNIOParser, SimpleNioParser
added a debug message to indicate when FillingNIOParser is going into
chunk mode.

Is this intended to fix #10? FYI, If you put "Fix #10" in the log message, it will automatically close the referenced issue when the PR is merged to the master branch.

Yep this is intended to fix #10, and although I meant to add that to the commit message, completely spaced it. Will update. Thx.


37% of the time is spent allocating/freeing memory

I've run /usr/bin/time target/release/jxl-oxide decode on the attached image and noticed that the time spent in the kernel is very high: 0.90user 0.54system 0:00.53elapsed 271%CPU
Measured on commit c8d528ddde518507d4889cb15318be76b879550a
Test image: Puente_de_Don_Luis_I,_Oporto,_Portugal,_2019-06-02,_DD_29-31_HDR.jxl.gz
So I used perf to investigate, here's the profile: https://share.firefox.dev/4a42u7I
The yellow parts are in userspace, the orange parts are in the kernel. You can see that the main thread does almost nothing but deallocate memory. And worker threads all end up spending a lot of time allocating it - not all at once, it gets provisioned gradually so it is spread out across the execution, but lots of functions bottom out in the kernel's memory management code.
Reusing allocations to avoid calling into the memory allocator all the time would dramatically improve performance.

Oh, and this was measured on x86_64-unknown-linux-gnu with its pretty good glibc memory allocator. The x86_64-unknown-linux-musl target with its Musl libc allocator is far worse: 0.95user 1.13system 0:00.81elapsed
And Apple targets are going to be as slow as musl if not slower. Their memory allocator is really slow.

I've just realized I was measuring an older commit. I've re-measured on 7ec630c1c0103f86631458cbb01498349dbacd04 and the results are not as skewed towards the system time this time around, while the total elapsed time is unchanged: 1.11user 0.26system 0:00.54elapsed
Updated profile: https://share.firefox.dev/3QukLUL
Still a lot of allocating and freeing memory on the profile.

Thanks for the investigation! I'm aware of allocation overhead and it's what I'm recently looking into. Hopefully I can come up with better buffer management...


Gmail and Less Secure Apps

On May 30th, Gmail will remove support for apps not supporting OAuth 2.0. Turning off less secure apps was the only way I could use Himalaya for my gmail account. Is there a plan to support Gmail after this change?

:thinking:  I access my account on Himalaya with App passwords and I cannot see any discontinuation notice over there?
https://myaccount.google.com/apppasswords

Interesting, that link leads me to Google telling me "The setting you are looking for is not available for your account."

Looks like it's a 2-step verification issue. Thanks and sorry for the confusion!

No worries :)
Hopefully this will work out for you. If it does, don't forget to close the issue :+1:

Is there any timeline or thought into using oauth? I'd like to incorporate office 365 but without oauth that won't be possible.

Looks like it's a 2-step verification issue. Thanks and sorry for the confusion!

Let us now if it fixed your issue!

Is there any timeline or thought into using oauth? I'd like to incorporate office 365 but without oauth that won't be possible.

This is a different issue, I invite you to open a dedicated issue for this feature :wink:


Annotating a ManyToOne relationship with {nullable:false} seems to not actually mark the column as NOT NULL in the database schema.

First of all, thanks for this brilliant lib! Really takes the edge off of working with large nested entities.
Describe the bug
Annotating a ManyToOne relationship with {nullable:false} seems to not actually mark the column as NOT NULL in the database schema.
I get the following debug output. I have indicated where I expect the ORM to mark the column as NOT NULL.
[discovery] ORM entity discovery started, using ReflectMetadataProvider
[discovery] - processing entity Author
[discovery] - processing entity Book
[discovery] - entity discovery finished, found 2 entities, took 10 ms
[info] MikroORM successfully connected to database :memory:
[query] select name as table_name from sqlite_master where type = 'table' and name != 'sqlite_sequence' and name != 'geometry_columns' and name != 'spatial_ref_sys' union all select name as table_name from sqlite_temp_master where type = 'table' order by name [took 1 ms]
[query] pragma foreign_keys = off; [took 0 ms]
[query] create table `author` (`id` integer not null primary key autoincrement, `name` varchar not null); [took 0 ms]
[query] create table `book` (`id` integer not null primary key autoincrement, `name` varchar not null); [took 1 ms]
---> [query] alter table `book` add column `author_id` integer null; [took 0 ms]
[query] create index `book_author_id_index` on `book` (`author_id`); [took 1 ms]
[query] pragma foreign_keys = on; [took 0 ms]

To Reproduce
Run the below and note MikroORM's debug output.
import { Entity, ManyToOne, MikroORM, PrimaryKey, Property } from "@mikro-orm/core"

@Entity()
class Author {
    @PrimaryKey()
    id!: number

    @Property({ type: 'varchar' })
    name!: string
}

@Entity()
class Book {
    @PrimaryKey()
    id!: number

    @Property({ type: 'varchar' })
    name!: string

    @ManyToOne(() => Author, { nullable: false, eager: true })
    author!: Author
}

const test = async () => {
    const connection = await MikroORM.init({
        entities: [
            Author,
            Book
        ],
        dbName: ':memory:',
        type: 'sqlite',
        debug: true,
        discovery: {
            disableDynamicFileAccess: true,
            requireEntitiesArray: true,
            alwaysAnalyseProperties: true,
            warnWhenNoEntities: true
        }
    })

    const generator = connection.getSchemaGenerator()
    await generator.updateSchema()
}

test().catch(console.log)

Expected behavior
I expect the ORM to make the ManyToOne relationship non-nullable on the database level.
Versions

Dependency
Version

node
v14.1.0

typescript
4.0.5

mikro-orm
4.2.3

mikro-orm/sqlite
4.2.3

sqlite3
5.0.0

Sqlite does not support adding not null columns via alter statements.

@B4nan thanks for your reply. Ah yes that makes perfect sense!
So i take it that mikroORM also doesnt support setting not null in the CREATE TABLE statements?

It is supported for create table statements, but FKs are always added via alter statements currently (unless it is a PK), to support circular references. I am planning to rework this a bit as there were some issues with ongoing mssql support so want to do it this way only when actually needed (when we know there is a cycle in the graph).

Great! Thanks for clearing that up. I can work without them just fine. It's just good to know that it is working as intended currently. Thanks again for this great lib!


Rename changeset to changeSet

Codecov Report

Merging #102 (cfd2b7e) into main (80f2347) will not change coverage.
The diff coverage is 100.00%.

@@             Coverage Diff             @@
##                main      #102   +/-   ##
===========================================
  Coverage     100.00%   100.00%
+ Complexity       442       437    -5
===========================================
  Files             34        34
  Lines           1160      1162    +2
===========================================
+ Hits            1160      1162    +2

Impacted Files
Coverage Δ

src/Token/Tokenizer.php
100.00% <ø> (ø)

src/Report/SniffViolation.php
100.00% <100.00%> (ø)

src/Runner/Fixer.php
100.00% <100.00%> (ø)

src/Sniff/BlankEOFSniff.php
100.00% <100.00%> (ø)

src/Sniff/EmptyLinesSniff.php
100.00% <100.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


KeyVaultCertificate.cer property returns bytesarray instead of bytes

Package Name:
azure-keyvault-certificates
Package Version:
4.6.0
Operating System:
Windows
Python Version:
3.9.6

Describe the bug
I'm trying to fetch imported certificate from Azure Key Vault. According to source code property cer of KeyVaultCertificate should return bytes object  or None:
    @property
    def cer(self):
        # type: () -> Optional[bytes]
        """The CER contents of the certificate.

        :rtype: bytes or None
        """
        return self._cer

But in reality if throw pdb and try to read type of KeyVaultCertificate.cer you will get byteaaray:
(Pdb++) type(cert.cer)
<class 'bytearray'>

To Reproduce

Import certificate to Azure Key Vault
Load certificate using code below:

from azure.identity import DefaultAzureCredential
from azure.keyvault.certificates import CertificateClient

KEY_VAULT_NAME = "kv-test"  # replace with your key vault name
CERTIFICATE_NAME = "example"  # replace with your imported certificate name
key_client = CertificateClient(
      vault_url=f"https://{KEY_VAULT_NAME}.vault.azure.net/",
      credential=DefaultAzureCredential(),
)
cert = key_client.get_certificate(CERTIFICATE_NAME )
print(type(cert.cer))

Expected behavior
KeyVaultCertificate.cer should be of type Optional[bytes]

Thank you for the feedback @deepaerial . We will investigate and get back to you asap.

Hi @deepaerial, thank you for opening an issue! I just double-checked, and you're correct about the discrepancy. I'll open a PR to fix this right away and link it to this issue.


Modify conditional example

The conditional example wasn't working, the proposed solution works.

Thank you!


Set default value for HOSTNAME for python3-http templates

The HOSTNAME environment variable is not available in faasd, which makes any function using the python3-http template fail with the following error with a KeyError exception.
Setting a default value should fix this issue
Signed-off-by: Mehdi Yedes<EMAIL_ADDRESS>

Thank you @mehyedes
Just to note for anyone who lands here, this issue was seen with faasd and when running the template directly on MacOS outside of a container where HOSTNAME wasn't available as an env-var.