Moving documentation to PowerShell Docs

During the community call I raised the question if we could move (bit by bit) the resource documentation to PowerShell Docs repo. I couldn't find the issue I raised this in so I writing a new issue. :)
This would then be instead of having the documentation on GitHub Wiki.
With resource documentation I mean all the documentation for the resource module, like descriptions what a resource does, it's parameters with their descriptions, examples and so on. Document it much like how a cmdlet is documented today in PowerShell Docs, something like Get-Service. Of course there probably need to be a different layout for documenting a resource.
I also see a demand for step-by-step guides (issue https://github.com/PowerShell/xSQLServer/issues/176) which for xSQLServer means we need to incorporate other resources like xFailoverCluster in that guide. We have a lot of examples over at xSQLServer which should be documented more in a blog style (issue https://github.com/PowerShell/xSQLServer/issues/462), which got me thinking again of PowerShell Docs.
Having these in PowerShell Docs we could use all knownledge of the PowerShell community to keep these up-to-date.
It would be harder for the community to find these, and update these, in the module folder or in GitHub wiki when there is a new good looking doc site with "all other" PowerShell documentation on it. :)
So the first question is. Is it possible for us to start moving/creating documentation on PowerShell Docs?
And if that is a yes, then we need to figure out how to do that practically, or if it is even practically.
Will it mean that we need to ask the contributor to send in a PR to the PowerShell Docs repo when there is a need for a change in the current documentation? Or can we automate that?
Can we have control over deploy to the Docs site, so instead of the DocumentHelper documenting on GitHub Wiki it updates the Docs site? Or maybe it sends in a PR to the PowerShell Docs repo?
Either way PowerShell Docs repo will become the source from which all updates must be based upon.
I see there would be much potential have the documentation in the PowerShell Docs. To get out to a broader community, with even more knowledge.

I agree with @johlju - this sounds like it could be a pretty good idea.
But I'd suggest we'd only want to do this with the repos that currently support Wiki/Autodocumentation (once this PR has been merged). We'd also want to completely automate the process of copying the Wiki content over when the module is published to the PSGallery - this should be reasonably easy to automate as part of the release process (but would require the PS Team @kwirkykat / @mbreakey3 to create the process I'd expect).
So tl;dr:

Wiki repos only (I'm working on changing other repos to Wiki)
Publish docs by automation only.

My 2c!

Sorry, I missed the community call due to the PowerShell summit and then I was out sick for a few days.
I'm the doc owner for PowerShell and the right person to investigate and come back with answers.

So the first question is. Is it possible for us to start moving/creating documentation on PowerShell Docs?

Great question. We think about docs in two categories  - "reference" (basically what you would get via get-help and API docs, etc), and "conceptual" (your example of SQL server)
Right now, our reference content only covers PowerShell core cmdlets that we publish and maintain. Having community module reference content would be a change, so let me talk to doc writers and see what we come up with. I agree we have a particularly fragmented story on the DSC side of things right now and some action is needed.
For the conceptual content, I think it would be great to have stuff like the step-by-step guide to setting up SQL on our docs page. We badly need more guides of this nature. cc @eslesar as he's investigating conceptual content right now - I'll also talk to him in person.
I have some minor concerns about having community stuff listed on the Official Microsoft Documentation, but I'll dig around to see what other communities (Chef, Puppet, etc) do and what a good best practice would be in this instance.

Follow-up as we discussed this in the community call:
We are moving towards a model of PowerShell where each module should live on its own where possible and include its own documentation.
As a result, my reccomendation is to keep documentation in the same repo as the module and link to it from e.g. the gallery when necessary. This is similar to what Chef and Puppet do.

Closing this as per comment from @zjalexander. On top of his comment, we are also moving towards adding resource modules that are maintained inside the community's own repositories.


Fluentd pods fail to start

A generic install on the IONOS Cloud managed k8s platform yields a mostly green deployment except for the fluend-es DaemonSet. Its pods give the following error:
Unable to attach or mount volumes: unmounted volumes=[varlibdockercontainers], unattached volumes=[configd varlibdockercontainers varlog varlogbuffers varlogpos fluentd-es-token-6zh54 config]: timed out waiting for the condition

Since many nodes have switched to containerd and the path just needs to exist (according to https://github.com/bitnami/kube-prod-runtime/issues/1005), could an init container be written that ensure this path is available?

On eks v1.18 and high, when set up bkpr on aws nodes with ami family bottlerocket, fluentd stay "container creating"


[stable/prometheus-blackbox-exporter] add option to store config as a Secret

What this PR does / why we need it:
This adds the ability to store blackbox config as a Secret, which is a more appropriate place if the blackbox config includes http credentials.
Checklist

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md

/ok-to-test

@alice-sawatzky can you add a test that uses the secret instead of the configmap?

oh yes good call. time for me to learn how tests work in this repo!

well e2e tests are now passing with improved coverage, any idea why the linter is stuck?

@alice-sawatzky Can you please rebase.

/lgtm


Researcher role + dashboard

https://www.pivotaltracker.com/story/show/150112113

added new Researcher role
added new Research Dashboard ('/research')

only available to those with Researcher role
includes header/gil links to new page, for those with the role

moved 'Export Questionnaire Data' functionality to new /research page
moved data export population logic into admin.js

@pbugni good point - added in that redirect from /home for researchers (happens AFTER the potential redirect check for staff/intervention_staff)

@OptimusRhine github shows a merge conflict -- would you mind resolving?

@pbugni should be resolved now


undefined method `parent_ids' for nil:NilClass

Using mongoid (3.0.9)
Using mongoid-tree (1.0.1)
Rails Method is throwing
def rebuild_path
MassTopic.all.each do |topic|
  puts "Buliding Path: " + topic.name
  topic.path = topic.ancestors_and_self.collect{ |item| "#{item.name}||#{item.id}"}.join("$$")

  topic.save

end
respond_to do |format|
  format.html { render :text => "Done"}
end

end

[2012-11-05 21:28:24] ERROR NoMethodError: undefined method parent_ids' for nil:NilClass     /home/ec2-user/.rvm/gems/ruby-1.9.3-p286/gems/mongoid-tree-1.0.1/lib/mongoid/tree.rb:420:inrearrange'
/home/ec2-user/.rvm/gems/ruby-1.9.3-p286/gems/mongoid-tree-1.0.1/lib/mongoid/tree.rb:95:in block (3 levels) in <module:Tree>'     /home/ec2-user/.rvm/gems/ruby-1.9.3-p286/gems/activesupport-3.2.8/lib/active_support/callbacks.rb:403:in_run__2708834019810802991__rearrange__21207758887223718__callbacks'
/home/ec2-user/.rvm/gems/ruby-1.9.3-p286/gems/activesupport-3.2.8/lib/active_support/callbacks.rb:405:in __run_callback'     /home/ec2-user/.rvm/gems/ruby-1.9.3-p286/gems/activesupport-3.2.8/lib/active_support/callbacks.rb:385:in_run_rearrange_callbacks'
/home/ec2-user/.rvm/gems/ruby-1.9.3-p286/gems/activesupport-3.2.8/lib/active_support/callbacks.rb:81:in run_callbacks'     /home/ec2-user/.rvm/gems/ruby-1.9.3-p286/gems/mongoid-3.0.9/lib/mongoid/callbacks.rb:114:inrun_callbacks'
/home/ec2-user/.rvm/gems/ruby-1.9.3-p286/gems/mongoid-tree-1.0.1/lib/mongoid/tree.rb:95:in block (2 levels) in <module:Tree>'     /home/ec2-user/.rvm/gems/ruby-1.9.3-p286/gems/activesupport-3.2.8/lib/active_support/callbacks.rb:407:in_run__2708834019810802991__validation__21207758887223718__callbacks'
/home/ec2-user/.rvm/gems/ruby-1.9.3-p286/gems/activesupport-3.2.8/lib/active_support/callbacks.rb:405:in __run_callback'     /home/ec2-user/.rvm/gems/ruby-1.9.3-p286/gems/activesupport-3.2.8/lib/active_support/callbacks.rb:385:in_run_validation_callbacks'
/home/ec2-user/.rvm/gems/ruby-1.9.3-p286/gems/activesupport-3.2.8/lib/active_support/callbacks.rb:81:in run_callbacks'     /home/ec2-user/.rvm/gems/ruby-1.9.3-p286/gems/mongoid-3.0.9/lib/mongoid/callbacks.rb:114:inrun_callbacks'
/home/ec2-user/.rvm/gems/ruby-1.9.3-p286/gems/activemodel-3.2.8/lib/active_model/validations/callbacks.rb:53:in run_validations!'     /home/ec2-user/.rvm/gems/ruby-1.9.3-p286/gems/activemodel-3.2.8/lib/active_model/validations.rb:194:invalid?'
/home/ec2-user/.rvm/gems/ruby-1.9.3-p286/gems/mongoid-3.0.9/lib/mongoid/validations.rb:78:in valid?'     /home/ec2-user/.rvm/gems/ruby-1.9.3-p286/gems/activemodel-3.2.8/lib/active_model/validations.rb:202:ininvalid?'
/home/ec2-user/.rvm/gems/ruby-1.9.3-p286/gems/mongoid-3.0.9/lib/mongoid/persistence/modification.rb:22:in prepare'     /home/ec2-user/.rvm/gems/ruby-1.9.3-p286/gems/mongoid-3.0.9/lib/mongoid/persistence/operations/update.rb:43:inpersist'
/home/ec2-user/.rvm/gems/ruby-1.9.3-p286/gems/mongoid-3.0.9/lib/mongoid/persistence.rb:139:in update'     /home/ec2-user/.rvm/gems/ruby-1.9.3-p286/gems/mongoid-3.0.9/lib/mongoid/persistence.rb:81:insave'
/home/ec2-user/apps/testtree/app/controllers/homes_controller.rb:48:in block in rebuild_path'     /home/ec2-user/.rvm/gems/ruby-1.9.3-p286/gems/mongoid-3.0.9/lib/mongoid/contextual/mongo.rb:644:inyield_document'
/home/ec2-user/.rvm/gems/ruby-1.9.3-p286/gems/mongoid-3.0.9/lib/mongoid/contextual/mongo.rb:134:in block (2 levels) in each'     /home/ec2-user/.rvm/gems/ruby-1.9.3-p286/gems/moped-1.2.7/lib/moped/query.rb:78:inblock in each'
/home/ec2-user/.rvm/gems/ruby-1.9.3-p286/gems/moped-1.2.7/lib/moped/cursor.rb:26:in block in each'     /home/ec2-user/.rvm/gems/ruby-1.9.3-p286/gems/moped-1.2.7/lib/moped/cursor.rb:26:ineach'
/home/ec2-user/.rvm/gems/ruby-1.9.3-p286/gems/moped-1.2.7/lib/moped/cursor.rb:26:in each'     /home/ec2-user/.rvm/gems/ruby-1.9.3-p286/gems/moped-1.2.7/lib/moped/query.rb:77:ineach'
/home/ec2-user/.rvm/gems/ruby-1.9.3-p286/gems/moped-1.2.7/lib/moped/query.rb:77:in each'     /home/ec2-user/.rvm/gems/ruby-1.9.3-p286/gems/mongoid-3.0.9/lib/mongoid/contextual/mongo.rb:133:inblock in each'
/home/ec2-user/.rvm/gems/ruby-1.9.3-p286/gems/mongoid-3.0.9/lib/mongoid/contextual/mongo.rb:603:in selecting'     /home/ec2-user/.rvm/gems/ruby-1.9.3-p286/gems/mongoid-3.0.9/lib/mongoid/contextual/mongo.rb:132:ineach'
/home/ec2-user/.rvm/gems/ruby-1.9.3-p286/gems/mongoid-3.0.9/lib/mongoid/contextual.rb:18:in each'     /home/ec2-user/apps/testtree/app/controllers/homes_controller.rb:37:inrebuild_path'
/home/ec2-user/.rvm/gems/ruby-1.9.3-p286/gems/actionpack-3.2.8/lib/action_controller/metal/implicit_render.rb:4:in send_action'     /home/ec2-user/.rvm/gems/ruby-1.9.3-p286/gems/actionpack-3.2.8/lib/abstract_controller/base.rb:167:inprocess_action'
/home/ec2-user/.rvm/gems/ruby-1.9.3-p286/gems/actionpack-3.2.8/lib/action_controller/metal/rendering.rb:10:in process_action'     /home/ec2-user/.rvm/gems/ruby-1.9.3-p286/gems/actionpack-3.2.8/lib/abstract_controller/callbacks.rb:18:inblock in process_action'
/home/ec2-user/.rvm/gems/ruby-1.9.3-p286/gems/activesupport-3.2.8/lib/active_support/callbacks.rb:414:in _run__1342489903615171212__process_action__184040716227805675__callbacks'     /home/ec2-user/.rvm/gems/ruby-1.9.3-p286/gems/activesupport-3.2.8/lib/active_support/callbacks.rb:405:in__run_callback'
/home/ec2-user/.rvm/gems/ruby-1.9.3-p286/gems/activesupport-3.2.8/lib/active_support/callbacks.rb:385:in _run_process_action_callbacks'     /home/ec2-user/.rvm/gems/ruby-1.9.3-p286/gems/activesupport-3.2.8/lib/active_support/callbacks.rb:81:inrun_callbacks'
/home/ec2-user/.rvm/gems/ruby-1.9.3-p286/gems/actionpack-3.2.8/lib/abstract_controller/callbacks.rb:17:in process_action'     /home/ec2-user/.rvm/gems/ruby-1.9.3-p286/gems/actionpack-3.2.8/lib/action_controller/metal/rescue.rb:29:inprocess_action'
/home/ec2-user/.rvm/gems/ruby-1.9.3-p286/gems/actionpack-3.2.8/lib/action_controller/metal/instrumentation.rb:30:in block in process_action'     /home/ec2-user/.rvm/gems/ruby-1.9.3-p286/gems/activesupport-3.2.8/lib/active_support/notifications.rb:123:inblock in instrument'
/home/ec2-user/.rvm/gems/ruby-1.9.3-p286/gems/activesupport-3.2.8/lib/active_support/notifications/instrumenter.rb:20:in instrument'     /home/ec2-user/.rvm/gems/ruby-1.9.3-p286/gems/activesupport-3.2.8/lib/active_support/notifications.rb:123:ininstrument'
/home/ec2-user/.rvm/gems/ruby-1.9.3-p286/gems/actionpack-3.2.8/lib/action_controller/metal/instrumentation.rb:29:in process_action'     /home/ec2-user/.rvm/gems/ruby-1.9.3-p286/gems/actionpack-3.2.8/lib/action_controller/metal/params_wrapper.rb:207:inprocess_action'
/home/ec2-user/.rvm/gems/ruby-1.9.3-p286/gems/actionpack-3.2.8/lib/abstract_controller/base.rb:121:in process'     /home/ec2-user/.rvm/gems/ruby-1.9.3-p286/gems/actionpack-3.2.8/lib/abstract_controller/rendering.rb:45:inprocess'
/home/ec2-user/.rvm/gems/ruby-1.9.3-p286/gems/actionpack-3.2.8/lib/action_controller/metal.rb:203:in dispatch'     /home/ec2-user/.rvm/gems/ruby-1.9.3-p286/gems/actionpack-3.2.8/lib/action_controller/metal/rack_delegation.rb:14:indispatch'
/home/ec2-user/.rvm/gems/ruby-1.9.3-p286/gems/actionpack-3.2.8/lib/action_controller/metal.rb:246:in block in action'     /home/ec2-user/.rvm/gems/ruby-1.9.3-p286/gems/actionpack-3.2.8/lib/action_dispatch/routing/route_set.rb:73:incall'
/home/ec2-user/.rvm/gems/ruby-1.9.3-p286/gems/actionpack-3.2.8/lib/action_dispatch/routing/route_set.rb:73:in dispatch'     /home/ec2-user/.rvm/gems/ruby-1.9.3-p286/gems/actionpack-3.2.8/lib/action_dispatch/routing/route_set.rb:36:incall'
/home/ec2-user/.rvm/gems/ruby-1.9.3-p286/gems/journey-1.0.4/lib/journey/router.rb:68:in block in call'     /home/ec2-user/.rvm/gems/ruby-1.9.3-p286/gems/journey-1.0.4/lib/journey/router.rb:56:ineach'
/home/ec2-user/.rvm/gems/ruby-1.9.3-p286/gems/journey-1.0.4/lib/journey/router.rb:56:in call'     /home/ec2-user/.rvm/gems/ruby-1.9.3-p286/gems/actionpack-3.2.8/lib/action_dispatch/routing/route_set.rb:600:incall'
/home/ec2-user/.rvm/gems/ruby-1.9.3-p286/gems/mongoid-3.0.9/lib/rack/mongoid/middleware/identity_map.rb:33:in block in call'     /home/ec2-user/.rvm/gems/ruby-1.9.3-p286/gems/mongoid-3.0.9/lib/mongoid/unit_of_work.rb:39:inunit_of_work'
/home/ec2-user/.rvm/gems/ruby-1.9.3-p286/gems/mongoid-3.0.9/lib/rack/mongoid/middleware/identity_map.rb:33:in call'     /home/ec2-user/.rvm/gems/ruby-1.9.3-p286/gems/sass-3.2.1/lib/sass/plugin/rack.rb:54:incall'
/home/ec2-user/.rvm/gems/ruby-1.9.3-p286/gems/actionpack-3.2.8/lib/action_dispatch/middleware/best_standards_support.rb:17:in call'     /home/ec2-user/.rvm/gems/ruby-1.9.3-p286/gems/rack-1.4.1/lib/rack/etag.rb:23:incall'
/home/ec2-user/.rvm/gems/ruby-1.9.3-p286/gems/rack-1.4.1/lib/rack/conditionalget.rb:25:in call'     /home/ec2-user/.rvm/gems/ruby-1.9.3-p286/gems/actionpack-3.2.8/lib/action_dispatch/middleware/head.rb:14:incall'
/home/ec2-user/.rvm/gems/ruby-1.9.3-p286/gems/actionpack-3.2.8/lib/action_dispatch/middleware/params_parser.rb:21:in call'     /home/ec2-user/.rvm/gems/ruby-1.9.3-p286/gems/actionpack-3.2.8/lib/action_dispatch/middleware/flash.rb:242:incall'
/home/ec2-user/.rvm/gems/ruby-1.9.3-p286/gems/rack-1.4.1/lib/rack/session/abstract/id.rb:205:in context'     /home/ec2-user/.rvm/gems/ruby-1.9.3-p286/gems/rack-1.4.1/lib/rack/session/abstract/id.rb:200:incall'
/home/ec2-user/.rvm/gems/ruby-1.9.3-p286/gems/actionpack-3.2.8/lib/action_dispatch/middleware/cookies.rb:339:in call'     /home/ec2-user/.rvm/gems/ruby-1.9.3-p286/gems/actionpack-3.2.8/lib/action_dispatch/middleware/callbacks.rb:28:inblock in call'
/home/ec2-user/.rvm/gems/ruby-1.9.3-p286/gems/activesupport-3.2.8/lib/active_support/callbacks.rb:405:in _run__1883085759501563229__call__21207758887223718__callbacks'     /home/ec2-user/.rvm/gems/ruby-1.9.3-p286/gems/activesupport-3.2.8/lib/active_support/callbacks.rb:405:in__run_callback'
/home/ec2-user/.rvm/gems/ruby-1.9.3-p286/gems/activesupport-3.2.8/lib/active_support/callbacks.rb:385:in _run_call_callbacks'     /home/ec2-user/.rvm/gems/ruby-1.9.3-p286/gems/activesupport-3.2.8/lib/active_support/callbacks.rb:81:inrun_callbacks'
/home/ec2-user/.rvm/gems/ruby-1.9.3-p286/gems/actionpack-3.2.8/lib/action_dispatch/middleware/callbacks.rb:27:in call'     /home/ec2-user/.rvm/gems/ruby-1.9.3-p286/gems/actionpack-3.2.8/lib/action_dispatch/middleware/remote_ip.rb:31:incall'
/home/ec2-user/.rvm/gems/ruby-1.9.3-p286/gems/actionpack-3.2.8/lib/action_dispatch/middleware/debug_exceptions.rb:16:in call'     /home/ec2-user/.rvm/gems/ruby-1.9.3-p286/gems/actionpack-3.2.8/lib/action_dispatch/middleware/show_exceptions.rb:56:incall'
/home/ec2-user/.rvm/gems/ruby-1.9.3-p286/gems/railties-3.2.8/lib/rails/rack/logger.rb:26:in call_app'     /home/ec2-user/.rvm/gems/ruby-1.9.3-p286/gems/railties-3.2.8/lib/rails/rack/logger.rb:16:incall'
/home/ec2-user/.rvm/gems/ruby-1.9.3-p286/gems/actionpack-3.2.8/lib/action_dispatch/middleware/request_id.rb:22:in call'     /home/ec2-user/.rvm/gems/ruby-1.9.3-p286/gems/rack-1.4.1/lib/rack/methodoverride.rb:21:incall'
/home/ec2-user/.rvm/gems/ruby-1.9.3-p286/gems/rack-1.4.1/lib/rack/runtime.rb:17:in call'     /home/ec2-user/.rvm/gems/ruby-1.9.3-p286/gems/activesupport-3.2.8/lib/active_support/cache/strategy/local_cache.rb:72:incall'
/home/ec2-user/.rvm/gems/ruby-1.9.3-p286/gems/rack-1.4.1/lib/rack/lock.rb:15:in call'     /home/ec2-user/.rvm/gems/ruby-1.9.3-p286/gems/actionpack-3.2.8/lib/action_dispatch/middleware/static.rb:62:incall'
/home/ec2-user/.rvm/gems/ruby-1.9.3-p286/gems/railties-3.2.8/lib/rails/engine.rb:479:in call'     /home/ec2-user/.rvm/gems/ruby-1.9.3-p286/gems/railties-3.2.8/lib/rails/application.rb:223:incall'
/home/ec2-user/.rvm/gems/ruby-1.9.3-p286/gems/rack-1.4.1/lib/rack/content_length.rb:14:in call'     /home/ec2-user/.rvm/gems/ruby-1.9.3-p286/gems/railties-3.2.8/lib/rails/rack/log_tailer.rb:17:incall'
/home/ec2-user/.rvm/gems/ruby-1.9.3-p286/gems/rack-1.4.1/lib/rack/handler/webrick.rb:59:in service'     /home/ec2-user/.rvm/rubies/ruby-1.9.3-p286/lib/ruby/1.9.1/webrick/httpserver.rb:138:inservice'
/home/ec2-user/.rvm/rubies/ruby-1.9.3-p286/lib/ruby/1.9.1/webrick/httpserver.rb:94:in run'     /home/ec2-user/.rvm/rubies/ruby-1.9.3-p286/lib/ruby/1.9.1/webrick/server.rb:191:inblock in start_thread'

+1

@macbury Can you please share a few details about your problem? Usually this happens when there is a node missing, but it is still referenced by another node.

Is this still unresolved?

@prcongithub This is most likely a problem with the data and not a problem with the code. Can you share more details of your particular case?

Saw this error too and had to patch it by overriding rearrange.
Couldn't implement a normal validation because of current handling.
Problem is i'm getting a non-existing parent_id and the rearrange method only checks if a parent_id is set, then just calls parent_parent_ids.
My local fix:
  def rearrange
    if parent.nil? && parent_id.present?
      self.parent_id = nil
      errors.add(:parent_id, :invalid)
    end
    super
  end


smokin sarina

i'm trying - is there no consideration for artists? - i've never used githud before. - bitister was nice enough to provide json files from my listing at ordynals.com --
i'd really like to get these listed, but i just don't understand how to do this.
i just have 2 small collections that I'm trying to list. a 12 piece & a 29 piece

Created a second sarina account because i couldn't figure out how to delete any files or forks from the first one. - But it looks like the pr failed again. -- this is my 4th day of trying to submit these collections.
Is there some point where you offer to assist? -- please!

bitister had said that maybe you require a .png instead of .jpg file for the icon pic.
Is that maybe the problem? --if so, I can open a 3rd GitHub account and try again with .png icons.


404 redirect is almost usable

Visiting a malformed FTM URL, like https://findthemasks.com/godevsgo.html
redirects to https://findthemasks.com/godevsgo.html/
Which looks like this (note missing flag image):

And attempts but fails to load donation pages like this:

A redirect to a functioning site like the US, or to a global directory of FTM pages, might help to get the reader where they need to go?

pretty sure the problem is this line in server.js: app.use('/:countryCode', router);
Essentially this is matching as a "country code" and trying to grab the svg / markers for godevsgo.html.


Tiles overlapping instead of snaping on besides them

The tiles are overlapping eachother when you hold in left click and draging while they should snap on to the side of the tiles.

The latest drag action now has some sort of "proper" tiling implemented. If you do not feel like it works the way it should do then please feel free to reopen this report!


SASS-1482 - 422 Business validation rules error crystallisation page

Description
Creation of business validation rules error page for crystallisation when a HTTP 422 error occurs
Add a link to the relevant story in Jira
SASS-1482
Checklist PR Reviewer
Before Reviewing

[ ]  Have you pulled the branch down?
[ ]  Have you assigned yourself to the PR?
[ ]  Have you moved the task to “in review” on JIRA?
[ ]  Have you checked to ensure all dependencies are up to date?
[ ]  Have you checked to ensure its been rebased against the current version of main?

Whilst Reviewing

[ ]  Have you run the tests?
[ ]  Have you run the journey tests?
[ ]  Have you looked at the JIRA story to make sure all Acceptance Criteria has been met?

After Reviewing

[ ]  Have you checked for merge conflicts or any changes in the current main that may affect the current pull request? i.e. does it need another rebase?
[ ]  Have you checked to make sure there are no builds in the pipeline before you merge?
[ ]  Have you moved the task to “in pipeline” on Jira?

[x]  Have you rebased against the current version of main?
[x]  Have you checked code coverage isn’t lower than previously?

After PRs been raised

[ ]  Have you checked the PR Builder passes?

test this please


For iOS want to reduce default 200 Mtrs.  stationary geofence to 50 Mtrs.

Your Environment

Plugin version: "@transistorsoft/capacitor-background-fetch": "^1.0.2" , "@transistorsoft/capacitor-background-geolocation": "^4.9.4"
Platform: iOS
Device OS version: All
Device manufacturer / model: Apple
XCode version: All
Capacitor info (npx cap doctor) :
@capacitor/cli: 4.6.1
@capacitor/core: 4.6.1
@capacitor/ios: 4.6.1
@capacitor/android: 4.6.1
Plugin config provided to #ready:

       {
              desiredAccuracy: BackgroundGeolocation.DESIRED_ACCURACY_HIGH,
              distanceFilter: 10,
              stationaryRadius: 50,
              url:`${webAdmin.apiAdminUrl}firebase_api/location.php`,
              extras:{email: userId, uid:uid, token: token},
              debug: true,
              logLevel: BackgroundGeolocation.LOG_LEVEL_VERBOSE,
              stopOnTerminate: false,
              startOnBoot: true
        }

Expected Behavior

It should reduce geofence from 200 meters to 50 meters. As user will corss that 50 meters geofence will get his location for further processing.
Actual Behavior

Build which was generated with above configuration is not sending any type location data to our back end system api, Other build in which only StationaryRadius is removed from configuration working fine.
Steps to Reproduce

Install app
Grand Permissions
Kill App

Context

Trying to reduce 200 meters stationary geofence to 50 meters so will get location updates after crossing 50 meters instead of 200
Debug logs

Logs
NA....

Trying to reduce 200 meters stationary geofence to 50 meters so will get location updates after crossing 50 meters instead of 200

This is impossible.  The native iOS / Android APIs do not respond to geofences less than 200 meters.


fix: Restore prometheus metrics in Metrics Server

Checklist

[x] Tests have been added
[x] Changelog has been updated and is aligned with our changelog requirements
[x] Commits are signed with Developer Certificate of Origin (DCO - learn more)

Fixes #4776

/run-e2e

/skip-e2e

/run-e2e

Could we do a 2.11.2 release with this? We are blocked on the upgrade for this

Could we do a 2.11.2 release with this? We are blocked on the upgrade for this

Yes, we plan to cut a release soon (next week or 2 weeks max) with this and other fixes, but just to clarify, this PR doesn't restore all the metrics (including the deprecated metrics), this PR restores the expected metrics for v2.11 (operator-sdk metrics)
Are you using keda_metrics_adapter* metrics? If yes, those metrics won't be restored as they were deprecated and removed based on our deprecation policy

Could we do a 2.11.2 release with this? We are blocked on the upgrade for this

Yes, we plan to cut a release soon (next week or 2 weeks max) with this and other fixes, but just to clarify, this PR doesn't restore all the metrics (including the deprecated metrics), this PR restores the expected metrics for v2.11 (operator-sdk metrics)
Are you using keda_metrics_adapter* metrics? If yes, those metrics won't be restored as they were deprecated and removed based on our deprecation policy. If that's your case, you have to migrate to the new metrics (scrapped from the operator pod)

The blocker is the alert for the target down for the metrics server on the upgrade. Migrating the alerts to use the new metrics vs the old ones is work we already done.

The blocker is the alert for the target down for the metrics server on the upgrade. Migrating the alerts to use the new metrics vs the old ones is work we already done.

Nice, then the fill will be available soon 😄


Unable to trigger a job

I was giving the fastlane-ci a try and setup with an existing fastlane android project. When I trigger a job in fastlane ci, it crashes with the following error.
web_1  | fatal: refusing to merge unrelated histories
web_1  | 	from /usr/local/bundle/bundler/gems/ruby-git-166273eac44a/lib/git/lib.rb:749:in `pull'
web_1  | 	from /usr/local/bundle/bundler/gems/ruby-git-166273eac44a/lib/git/base.rb:351:in `pull'
web_1  | 	from /usr/src/app/app/shared/models/git_repo.rb:456:in `block in pull'
web_1  | 	from /usr/src/app/app/shared/models/git_repo.rb:442:in `block in perform_block'
web_1  | 	from /usr/local/bundle/bundler/gems/TaskQueue-5b3f459be5c4/lib/queue_worker.rb:82:in `block in process'

Do you know what I might be doing wrong?

Is this build happening from a commit_trigger type? Might be related to this


[Feature Request]scopes为空数组时，scope期望默认选中empty

💭 Describe the feature
现有配置如下：
    scopes: [],
    allowCustomScopes: true,
    allowEmptyScopes: true,

没有默认的scope但是还想要能自定义scope，现在默认选中的是custom，实际场景是大多数情况下scope为空，想要默认选中empty。
💡 Proposed Solution
No response

When the scope is empty, the default empty pin the top

Mainly because customScopesAlign default is bottom. Logical judgment can be added on this basis.

Yeah. I solved it by setting customScopesAlign to top at now.
handleCustomTemplate function In until.ts：
 if (!Array.isArray(target) || target.length === 0) {
    return result;
  }

I think this will solve the problem.

The latest version 🌟(v1.3.5)🌟 should be resolve this issue request , please have a try. 💪
👀 Let me know if there are still any issues. Thanks for you work! 🎉


change Show all e-books query on a button

replace the uri encoded characters for human readable ones, from the queries in the quick access buttons on the frontsite
after releasing https://github.com/inveniosoftware/react-searchkit/issues/74

not valid after changes due to the user testing


Feature/react16

Add react 16 support
Add travis CI support

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@c3b9fd8). Click here to learn what that means.
The diff coverage is 100%.

@@            Coverage Diff            @@
##             master       #6   +/-   ##
=========================================
  Coverage          ?   92.75%
=========================================
  Files             ?        2
  Lines             ?       69
  Branches          ?       21
=========================================
  Hits              ?       64
  Misses            ?        5
  Partials          ?        0

Impacted Files
Coverage Δ

src/components/ProgressCircle.ts
91.8% <100%> (ø)

src/components/Alert.ts
100% <100%> (ø)

Continue to review full report at Codecov.

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


setItemToCraft (crash fix)

Fixes GTNewHorizons/GT-New-Horizons-Modpack#16769 for change GTNewHorizons/Applied-Energistics-2-Unofficial#523

CI is failing because it's using a prerelease build of AE2, the commits from GTNewHorizons/Applied-Energistics-2-Unofficial#523


Update UseDotNet@2 availability

When you change the selected server version of the docs to Azure DevOps Server 2019, the website says that the feature is not available with this version of Azure DevOps Server:

As discussed in https://github.com/microsoft/azure-pipelines-tasks/issues/12733#issuecomment-618710907, this is inaccurate. The task is actually not available with 17.143.28621.4, but after upgrading to 17.153.29522.3, it can be used. (Unfortunately, this isn't mentioned in the release notes.) Therefore, the docs should probably differentiate between Azure DevOps Server 2019, Azure DevOps Server 2019 Update 1, and Azure DevOps Server 2019 Update 1.1 to indicate availability of this task.

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

ID: f9660c58-3366-f1be-8380-d6cf1d3c0150
Version Independent ID: 226a4fd8-bce8-3333-d8d6-7af933c7b060
Content: Use .NET Core task - Azure Pipelines
Content Source: docs/pipelines/tasks/tool/dotnet-core-tool-installer.md
Product: devops
Technology: devops-cicd-tasks
GitHub Login: @pulkitaggarwl
Microsoft Alias: puagarw

@hangy Thank you for providing this feedback.
The documentation has been updated and changes will be released in the next publish cycle.


Add a AlphaDAO::getCountOfOldVersions() method

We already added the ActiveRecord::getHistoryCount() method which takes care of this: https://github.com/alphadevx/alpha/blob/2.0.0/Alpha/Model/ActiveRecordProviderInterface.php#L303


Why use memory_layer in all cases?

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): No
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): ubuntu 14.04
TensorFlow installed from (source or binary): binary
TensorFlow version (use command below): 1.2

In current AttentionWrapper, both BahdanauAttention and LuongAttention enforce to use a memory_layer. According to my understanding, it is needed only when the depth of memory is not matched with that of query_layer. Is it intended to be in this manner?
@ebrevdo , would you mind having a look at this?

Nagging Assignee: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @ebrevdo: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @ebrevdo: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @ebrevdo: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @ebrevdo: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.


Secure additional funding for the team.

Currently, we are funded primarily through IEEE (student government and E-council appropriations), but I think it's time we set up our own funds especially since the club is expanding so much.
New members who want to get involved, I think this is a great task to get involved in if you're interested in project management
We also receive sponsorship from Eaglecad in the form of free licences, and from Adcanced Circuits in the form of free PCB printing, but we also need cash rewards.
@jasteve4 is currently looking into setting up a wells fargo student group account, in the meantime we should also look into other sources of funding.
Current ideas:

Ask TI for sponsorship via free BeagleBones.
Ask Redhat for money. I remember last year they actually came to us to ask for a sponsorship package, and I don't believe we ever followed through with this. We need ideas for how we can carry this out. Things like "For $X we'll put redhat stickers on the robot, for $Y we'll let them name it". So we need ideas for that. @dfarrell07 do you still have those contacts?
Fundraisers etc in general.

One idea from yesterday, contacting sparkfun to see about getting them to supply parts at a discount

Something to ask for, getting a professional license from MATLAB for free

The Underwater robotics team said that a member from their team is in touch with Heather Daughtridge (director of external relations for ECE) who helps them network and find companies that might potentially sponsor them. It might be worth talking to her just to find out if she knows any companies that might be interested in sponsoring our team.
http://www.ncsu.edu/directory/moreinfo.php?username=hmdaught


refactor engine selection interface to enabled_engines

Session interface changed to
sess = graphscope.session(enabled_engines="analytical,interactive,learning")

or
sess = graphscope.session(enabled_engines="gae,gie,gle")

Codecov Report

Merging #2410 (060ed72) into main (c0c014f) will increase coverage by 26.81%.
The diff coverage is 28.57%.

Additional details and impacted files

@@             Coverage Diff             @@
##             main    #2410       +/-   ##
===========================================
+ Coverage   39.95%   66.76%   +26.81%
===========================================
  Files          88       88
  Lines        9757     9760        +3
===========================================
+ Hits         3898     6516     +2618
+ Misses       5859     3244     -2615

Impacted Files
Coverage Δ

python/graphscope/deploy/kubernetes/cluster.py
23.41% <ø> (-52.78%)
:arrow_down:

...on/graphscope/tests/kubernetes/test_demo_script.py
0.00% <0.00%> (-81.16%)
:arrow_down:

python/graphscope/client/session.py
72.52% <30.00%> (+7.10%)
:arrow_up:

python/graphscope/config.py
100.00% <100.00%> (ø)

python/graphscope/deploy/kubernetes/utils.py
12.31% <0.00%> (-52.22%)
:arrow_down:

...n/graphscope/deploy/kubernetes/resource_builder.py
25.20% <0.00%> (-46.75%)
:arrow_down:

...thon/graphscope/tests/kubernetes/test_with_mars.py
0.00% <0.00%> (-43.75%)
:arrow_down:

python/graphscope/interactive/query.py
69.51% <0.00%> (-14.64%)
:arrow_down:

... and 47 more

Continue to review full report at Codecov.

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


[incubator/etcd] tidy up

Some non-breaking tidy-ups of the chart.

/ok-to-test
/assign

/retest

CI is failing as the stateful set is not up in 3 mins.

That's weird, since I didn't really change anything that would affect it...
On 13 Aug. 2017 15:47, "Dhilip"<EMAIL_ADDRESS>wrote:

CI is failing as the stateful set is not up in 3 mins.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes/charts/pull/1721#issuecomment-322023425,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABONY634cXaEq7heHZRwn05zqqNCYYOOks5sXo4EgaJpZM4O1P6s
.

the CI needs to be fixed for Statefulset, I don't think it's because of the changes.
/test pull-charts-e2e

The pods don't come up because storage class "anything" won't work with the beta annotation. How about leaving the storage class update to a separate PR and then do it like so: https://github.com/kubernetes/charts/pull/1332

Marking this as stale PR, not activity from the author

I'm hoping to get time to make the changes soon. 😅
On 13 Sep. 2017 19:42, "Dhilip"<EMAIL_ADDRESS>wrote:

Marking this as stale PR, not activity from the author
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes/charts/pull/1721#issuecomment-329115496,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABONYxNJ5zOoOkvza_c0Ev9j01PbyIWpks5sh6OYgaJpZM4O1P6s
.

/retest

@dhilipkumars I've updated it, and looks like it's passing now 😀

/ok-to-test


add tests for resolver

Ticket Link

Related Links

Description

Steps to Reproduce / Test

Request

Response

Codecov Report

Merging #79 (ade866c) into master (533a705) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #79   +/-   ##
=======================================
  Coverage   82.80%   82.80%
=======================================
  Files          27       27
  Lines         954      954
=======================================
  Hits          790      790
  Misses        124      124
  Partials       40       40

Continue to review full report at Codecov.

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


Is there "open" source code?

I see the MIT license. Is there source code? I checked all branched, tags and archives.
OSCPoint is a PowerPoint add-in that allows Open Sound Control (OSC) control of PowerPoint on Windows
Is this only documentation?

Unfortunately the add-in uses some code snippets and techniques we've developed as part of our OctoCue and DeckTrack add-in products, so I'm not able to open-source the code.
Thanks for asking, though.


segfault caused by annotating staticmethod with forward

@TypeFunction
def makeClass(T):
    class A(Class):
        @staticmethod
        def f() -> makeClass(T):
            return makeClass(T)()
    return A

makeClass(int)()

produces a segfault. Maybe it should produce an exception, maybe it should actually run, but it shouldn't segfault. It runs if you remove the staticmethod and give f a 'self' argument.

It also runs if you leave off the type annotation from f (but keep f static).


Possibility to not watch discoveries after init discovery

It will be useful for cases when discovered server itself has service discovery mechanism and discovered value is needed only for initialize client. Redis and Kafka for example.

Resolved by #5


Add shields to README

See https://github.com/open-horizon-services/service-homeassistant for an example of shields to add

I also like the "Contributor" shield - example in https://github.com/open-horizon-services/service-node-red-hello-world

can I work on this one?

Fixed by #4

@oskurtt The issue was resolved. We reviewed the steps to fix the problem on a call with some students.


Format code

Use ESlint for code linting and Prettier for formatting
TODO:

[x] setup eslint
[x] use airbnb styleguide
[x] support typescript
[x] support yarn v2 and vs code
[x] make prettier and eslint work together
[x] format code and fix errors from eslint
[x] add script(s) to package.json
[x] changes to prettier config (to match airbnb styleguide)
[x] setup stylelint
[ ] fix styles

Or maybe use only eslint without prettier, hm 🤔

As fixing style warning and errors (from eslint) needs a huge refactoring (or even complete code rewrite), it'll be done in other (next) PR


Feature Request: Support csv output files from browser-history python package

What type of suggestion are you making?
Proposing a new feature
What is the problem that your feature request solves?
The export_history script seems to be broken for me and I cannot get it to run for firefox.
What is your proposed solution?
The browser-history python package works nicely. It would be easier to support importing its output instead of maintaining a script.
The csv format is simple: just datetime, link, title
Example
2024-11-13 20:00:00-05:00,https://www.youtube.com/,YouTube
What hacks or alternative solutions have you tried to solve the problem?
 Warning: Missing 4 recommended dependencies
    ! SINGLEFILE_BINARY: single-file (unable to detect version)
      Hint: To install all packages automatically run: archivebox setup
            or to disable it and silence this warning: archivebox config --set SAVE_SINGLEFILE=False

    ! READABILITY_BINARY: readability-extractor (unable to detect version)
      Hint: To install all packages automatically run: archivebox setup
            or to disable it and silence this warning: archivebox config --set SAVE_READABILITY=False

    ! MERCURY_BINARY: postlight-parser (unable to detect version)
      Hint: To install all packages automatically run: archivebox setup
            or to disable it and silence this warning: archivebox config --set SAVE_MERCURY=False

    ! YOUTUBEDL_BINARY: yt-dlp (unable to detect version)
      Hint: To install all packages automatically run: archivebox setup
            or to disable it and silence this warning: archivebox config --set SAVE_YOUTUBEDL=False

How badly do you want this new feature?

[ ] It's an urgent deal-breaker, I can't live without it
[ ] It's important to add it in the near-mid term future
[ ] It would be nice to have eventually
[ ] I'm willing to work on a PR to develop this myself
[ ] I have donated money to go towards fixing this issue

Mini Survey

[ ] I like ArchiveBox so far / would recommend it to a friend
[ ] I've had a lot of difficulty getting ArchiveBox set up
[ ] I would pay $10/mo for a hosted version of ArchiveBox if it had this feature

In the meantime you can use this quick script to convert the CSV to a JSONL format that archviebox can ingest:
# pip install pytz

import csv
import json
from datetime import datetime
import pytz

def convert_csv_to_jsonl(input_file, output_file):
    # Open files for reading and writing
    with open(input_file, 'r') as csv_file, open(output_file, 'w') as jsonl_file:
        # Read CSV without headers since they weren't provided in the example
        csv_reader = csv.reader(csv_file)

        for row in csv_reader:
            # Parse the timestamp and convert to UTC
            local_dt = datetime.fromisoformat(row[0])
            utc_dt = local_dt.astimezone(pytz.UTC)

            # Create dictionary with required structure
            record = {
                "url": row[1],
                "title": row[2],
                "created_at": utc_dt.strftime("%Y-%m-%dT%H:%M:%S+0000")
            }

            # Write the JSON line to output file
            jsonl_file.write(json.dumps(record) + '\n')

if __name__ == "__main__":
    convert_csv_to_jsonl('example_input_urls.csv', 'output.jsonl')  # edit this to point it to your input file

Then pipe the JSONL into archivebox like so:
archivebox add --parser=jsonl < output.jsonl

There is no jsonl parser, would the json one work?


Carthage support

Hi,
For iOS projets it's will be great to make your component Carthage compatible
Take a look at these articles:

Ruthlessly Simple Dependency Management with Carthage
Carthage Tutorial: Getting Started
Making Carthage-compatible Frameworks with Swift
Creating Cross-Platform Swift Frameworks for iOS, watchOS, and tvOS via Carthage and CocoaPods 👍

On your README.md add   on top and add section for the installation with Carthage.

Good thought I will get it supported ASAP.

@willpowell8 any news about carthage compatibility?

Hi Will, do you know when Carthage will be supported?
Thanks in advance.

Sorry this has taken me so long. I needed to get round to restructuring the project. Now you should be able to use with Carthage:
github "willpowell8/LocalizationKit_iOS


Error opening connection to to <IP_ADDRESS> port 3875 >No route to host

icscf      | 28(65) INFO: cdp [peerstatemachine.c:526]: I_Snd_Conn_Req(): I_Snd_Conn_Req(): Peer hss.ims.mnc001.mcc001.3gppnetwork.org
scscf      | 28(66) INFO: cdp [peerstatemachine.c:526]: I_Snd_Conn_Req(): I_Snd_Conn_Req(): Peer hss.ims.mnc001.mcc001.3gppnetwork.org
icscf      |
scscf      |
scscf      | 28(66) INFO: cdp [receiver.c:874]: peer_connect(): peer_connect(): Trying to connect to <IP_ADDRESS> port 3875
scscf      |
icscf      | 28(65) INFO: cdp [receiver.c:874]: peer_connect(): peer_connect(): Trying to connect to <IP_ADDRESS> port 3875

errorLog.txt

I would suggest the following.

Pull the latest changes from master branch

Drop the mysql docker volume (docker volume rm docker_open5gs_dbdata)

Rebuild pyHSS docker image (docker-compose -f 4g-volte-deploy.yaml --no-cache pyhss)

Re-deploy all containers


[system] Minimize color scheme script

To reduce HTML size, the script returns from getInitColorSchemeScript should be minified.
This PR:

Move the logic to scripts/colorSchemeScript (source of truth)
Run yarn system:minify-color-scheme-script to read the source and minify via terser
Put the minified code back to src/cssVars/getInitColorSchemeScript

All the tests are passed, so I believe that the minification is done correctly.

[x] I have followed (at least) the PR section of the contributing guide.

Is this really an issue? I mean how much did we save in bites? Is it worth the complexity added in the code?

It comes from community suggestion.
Other libraries that minify the script

https://github.com/pacocoursey/next-themes/blob/main/src/index.tsx#L184
https://github.com/chakra-ui/chakra-ui/blob/e98db2cc02e530c980997353dd4f093da9064593/packages/color-mode/src/color-mode-script.tsx#L18
https://github.com/gregberge/xstyled/blob/c35d470656820f7c9cc749eb33e02cf5cea24d26/packages/core/src/colorModes.tsx#L387

Will find out how much it saves.

It comes from a https://github.com/mui/material-ui/issues/27651#issuecomment-1123258293.

I was missing this in the PR description.


Error Plugin Load Failed

I'm starting a hexo blog and followed the installation instructions.
I copied the following into the __config.yml.
generator_amp:
  templateDir:  amp-template
  assetDistDir: amp-dist
  logo:
    path:   sample/sample-logo.png
    width:  600
    height: 60
  substituteTitleImage:
    path:   sample/sample-substituteTitleImage.png
    width:  1024
    height: 800
  warningLog: false   # If you want to validate, please set true.

Then if I run hexo generate, I get an error.

ERROR Plugin load failed: hexo-generator-amp

I'm running Windowx 10 x64 using node v6.9.4.
Any help would be appreciated!

@getrisedotio
Thank you for using this plugin .
About this issue , I tried it in this environment. But the same error did not occur.

Mac OSX 10.11 (Sorry , I can't tried windows. )
node v6.9.4
npm  v4.1.1
<EMAIL_ADDRESS>
$ nvm install v6.9.4
$ nvm use v6.9.4
$ npm install -g npm
$ npm install -g hexo-cli
$ hexo init hexo694
$ cd hexo694
$ npm install hexo-generator-amp --save

I copied the following into the ./_config.yml .
# The following settings is the quick start options.
generator_amp:
  templateDir:  amp-template
  assetDistDir: amp-dist
  logo:
    path:   sample/sample-logo.png
    width:  600
    height: 60
  substituteTitleImage:
    path:   sample/sample-substituteTitleImage.png
    width:  1024
    height: 800
  warningLog: false   # If you want to validate, please set true.

I started a local server.
$ hexo s

Next , I opend http://localhost:4000/2017/01/24/hello-world/amp/#development=1.  But the same error did not occur.
Windows user , do the same problem occur ? Please give me advice.

@getrisedotio
Please refer to the follow. Can you solve it the same way ?
https://github.com/hexojs/hexo/issues/1057

Thanks tea3! I did a clean install of of hexo in a new directory and followed your instructions, and it worked!
$ nvm install v6.9.4
$ nvm use v6.9.4
$ npm install -g npm
$ npm install -g hexo-cli
$ hexo init hexo694
$ cd hexo694
$ npm install hexo-generator-amp --save

I went back and saw that my old hexo directory was missing the amp-template directory and the amp-dist directory (in public). I'm not sure how that came to be, but if anyone else has the same issue, take a look to make sure the directories and present!


Add resizable panes to Trading UI

Let's try using @johnwalley's Allotment library.

Tested this : following the video for guidance, all together a pleasant experience where i as the user feel in full control of the sizing, very intuitive, some slight ugly wrapping with the middle pane field values when at minimum, but thats to be expected.


Benchmarking size of un-applied Scripts

Added functions to plutarch-benchmark which measure the size of an 'unapplied' version of a script, and some helpers for creating benchmarks with arguments applied in various ways.
I haven't incorporated it into the plutarch-test golden tests API, as I'm not sure it's necessary.
Closes #269 , Merge after #276 #267

cc: @srid on whether it's worth incorporating into the plutarch-test golden benchmarking

Wait, had we been doing this wrong all along? This is problematic.

Should be ready to merge after #267

Accidentally puashed the fixes to #267 to this branch instead

I have to be honest, I'm not sure what this PR is trying to do.

I have to be honest, I'm not sure what this PR is trying to do.

See #269 benchmarking the size of scripts without arguments applied, since they would otherwise throw the measurement off.


Testing the main with SNAPSHOT Fabric8 Client builds

In order to give faster feedback to fabric8 client and see if there are any problems with the updates to it we should cover testing with snapshot builds of fabric8 client.

This could be a nightly build or triggered by commits into fabric8 client.

This PR canbe used:
https://github.com/java-operator-sdk/java-operator-sdk/pull/1856
We need also to produce a SNAPSHOT build for QOSDK.

implementation can be seen here:
https://github.com/java-operator-sdk/java-operator-sdk/pull/1856


Version 2.0

There's a lot of pod stuff going on here, but it alphabetizes nicely above all the non-pod changes—non-pod changes start with HttpFileParsingTests.m and total fewer than 500 lines changed, I think.
This is a "big" change in that it changes the way some mock data files are named, so it's not backward-compatible and hence is a major version bump.  There's now a document describing the mock data naming convention.  VOKMockUrlProtocol is now dependent on VOKBenkode as a result of the naming convention.  I've added AFNetworking/Serializers to the test target of the example app to facilitate constructing test requests.
@vokalinteractive/ios-developers Code review?

Just curious about falling back on the SHA-256 hex. I don't see a test for that, but I might've missed it.
Otherwise good to pull.

There is a test that hits the fallback hash-based name, testPostJsonDictionaryHash.

Good to pull

Could you tag this as 2.0.0 please?

Already tagged, but pod trunk push is returning an error :disappointed:
Unable to find a specification for VOKBenkode (~> 0.1.1) depended upon by VOKMockUrlProtocol (2.0.0).

That's because it's tagged as 2.0, not 2.0.0, I think?

changed the tag to 2.0.0, but still no luck

Hmm... I'm getting a different error:
[!] The platform of the target `Pods` (iOS 6.0) is not compatible with `VOKBenkode (0.1.1)` which has a minimum requirement of iOS 7.0.

I guess I'll have to fix that.


Multi-arch builds are broken due to unsatisfied yq base image dep in one of the architectures

The yq base image is not built for s390x see https://github.com/konveyor/analyzer-lsp/actions/runs/7503597149
We need to fix this to unblock builds on main

Fixed via #487


Fixed NPE getting Stack Trace if Throwable is null

Coverage increased (+0.0003%) to 94.937% when pulling 37f79d32981faf7d830ba2ad24ccf1e3d1a1a906 on arturobernalg:feature/npe_getStackTrace into 69c9593cc1da760bb4dbcf32f4ae755c54376b77 on apache:master.


Per-request vars?

Describe your question
I wonder where I can set some per-request vars.
I would basically want to do something like this:
before("/api", ctx -> ...check credentials and store "currentUser" in context)

get("/api/users/me", ctx -> return serialize(<UserModel>ctx.getVar("currentUser"))

So that I can do jwt parsing and those things once, and then use that in all of my http handlers (or in following before-handlers).
I know there's "session" to store stuff. But I don't want to store these things in some kind of session storage or so. Just want to persist it for the request lifespan

ctx.attribute(key, value) will store attributes on the request, which will be cleaned up at the end of the request lifecycle (after app.after()).

Ok thank you! It would be great the signature attribute(key, value) could be added to the Context section of https://javalin.io/documentation#after-handlers .
I see now that it's covered under the "WsContext"

I have no idea why that isn't there, that's a weird oversight. I'll add it now, thanks :)

It's there now @lulzmachine !


Weekly tests against older Micropython versions

As noted in this discussion different Micropython versions may have differences in their async support.
It's probably too expensive to run tests against all versions on every pull request, but a weekly regression test against a bunch of different versions probably makes sense.

Closed by #30 and #31.


docs: add registration part to collator docs

Summary

Added t0rn faucet
Added some necessary steps to register_as_candidate
Changed version to match the latest one

Good to go after resolving @chiefbiiko's points


ninja: make reproducible

See https://github.com/ninja-build/ninja/pull/1529
Motivation for this change
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Assured whether relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

12:29 <qyliss> gchristensen: do you still agree with https://github.com/NixOS/nixpkgs/pull/55421#issuecomment-461623918, considering it's been over a year and 2 of the 20 broken packages on r13y.com are Nix and the Nix manual?
12:29 <qyliss> *NixOS manual
12:30 <gchristensen> well...yes, because the IDs are really bad. I'd rather a build-time test that looks for bad IDs and fails
12:30 <gchristensen> following the principle of https://www.w3.org/Provider/Style/URI


[V3]: SSR with NextJs - undefined cannot be serialized as JSON

Hey,
I've been trying to update a NextJs repo which uses hydration to V3 and got the following error:

Quickly looking at the code and there's indeed a fetchMeta state property set by default to undefined.
https://github.com/tannerlinsley/react-query/blob/4d01e1fd543d304d2b07defcd4cda55e089db88b/src/core/query.ts#L442

:tada: This issue has been resolved in version 3.2.0-beta.33 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

This seems NextJS specific as usually undefined will just be dropped when serializing to JSON:
JSON.stringify({ prop: undefined })
// {}

Yeah, it must be next specific. I ran into it yesterday nonetheless. Not a big deal though.

Now version 3.21 but I still have to use JSON.stringify to solve the above problem.


Add metric "benchmark points per $"

The metrics already contain a value "benchmark". We found a metric "benchmark points per $" really useful while evaluating which instance type to pick.
Do you think it would be easy to add such a (virtual) metric?
Thank you very much for your awesome project! It really makes our life easier! 😍

Good idea. I added benchmark divided by price per hours (https://github.com/Cyclenerd/google-cloud-compute-machine-types/commit/62a4f76784c59658f48fd4356e8d44b5f4b3f850). You can also make further evaluations with the SQL or CSV export.
The T2D family has a good price per CPU performance ratio.

I would also be happy if you give the repo a star :)

Thank you very much for adding it so quickly! Unfortunately, I can't find the new values on https://gcloud-compute.com/instances.html
The build ran without a problem, right? I'm confused. :)

You can find it in the Instance Picker (gcloud-compute.com/grid.html).


link hosted https://www.jslint.com/help.html

fixes #289

thx @matkoniecz ! in future, try to make pull-requests to beta branch ; )

ops, sorry
Maybe put it into CONTRIBUTING.md file? See https://github.blog/2012-09-17-contributing-guidelines/

i've decided to make branch-beta the default-branch.  that will default all pr's to it (w/o requireing ppl to read the instructions first ; )


[docs] Document the new BindingsBuilder

This were added on this pull request

Closed by https://github.com/jonataslaw/getx/pull/535


Checkbox checked flag in onCheck callback is different on Android and iOS

Problem description
render () {
            const checkbox = <Checkbox
              onCheck={this.handleOverlayChange(asset.file)}
              checked={!!this.props.overlays![asset.file]}
            />

            return <ListItem
              key={asset.file}
              leftCheckbox={checkbox}
              primaryText={primaryText}
              secondaryText={secondaryText}
            />
}

  handleOverlayChange = (x) => {
    return (event, isChecked) => {
      console.log([x, isChecked])
    }
  }

Link to minimal working code that reproduces the issue

Versions

Material-UI: 0.18.1
React: 15.5.4
Browser: Chrome / Mobile Safari

The ripple also plays twice on Android when tapping the checkbox.

It does work if you treat the check box as an uncontrolled input using defaultChecked.

We have been porting the component on the next branch. We reimplemented it from the ground-up. While we haven't tested it, I think that the issue is most likely fixed on that branch. Hence, I'm closing it.


HOTFIX: set timestamp in SinkNode

@guozhangwang
Setting the timestamp in produced records in SinkNode. This forces the producer record's timestamp same as the context's timestamp.

LGTM. Merged to trunk.


Wallet Labels are not saved | 1.7.1 | OSX (Apple M1/M2)

Hope you could help with the following.
For some of my wallet files I have the following strange behavior:

I open the wallet (.mv.db) and retrieve new TXs
I adjust the wallet labels
I close the mv.db file
I open it again
It again needs to retrieve the same TXs as retrieved in step 1) and the wallet labels are gone

Looking in the folder where my wallet files are stored I observe that for the wallets with this strange behavior there is no mv.db.tempFile (anymore?), while for the other wallets which are working properly there is.
Any thoughts on why this is happening and how to fix?
Thanks,
CM

What version of Sparrow?

Hi Craig,
1.7.1 for OSX (Apple M1/M2) i.e. latest version.

What server are you connecting to? Sparrow should not "need to retrieve the same TXs as retrieved in step 1". There's something strange going on if it is.
What happens if you take Sparrow offline using the bottom right toggle and then restart it? Are labels still lost?

Thanks Craig. I am connecting to an Electrum Server (electrs).
I performed the following steps:

Opened the wallet and retrieve the new TXs
Gave the TXs the correct label
Switched off the connection with my Electrum Server by switching off the toggle at the right bottom
Closed the wallet
Reopened the wallet

The TXs that I had labelled at step 2. are now missing at all and are obviously not retrieved (again), since I still have the toggle switched off. Please note this issue only persists for some of my wallets, while for others I have no whatsoever.
Furthermore, I made an export of this wallet, i.e., 1:1 copy of this wallet, and tried to reproduce the issue. For this 1:1 copy I strangely do not encounter this issue anymore. What's striking is that the file size of this 1:1 copy is also significantly smaller in size (~40%) than the original one. Could it be that the original wallet file somehow got irreparably damaged/corrupted and the only fix if that happens is to export the information inside this wallet into a new version via the "Export Wallet" functionality within Sparrow?

Are there any relevant errors in the Sparrow log? (Help menu).

I did some additional tests on my side. When using the wallet file from within my Downloads folder, there is no unusual behavior. Everything works as expected.
However, when I try to save the wallet files on a mounted decrypted volume, I observe errors like:
General error: "org.h2.mvstore.MVStoreException: Could not sync file /Volumes/XXX/YYY/ZZZ.mv.db [2.1.214/2]" [50000-214]
ERROR [H2-save] h2database [null:-1] ZZZ:database flush
org.h2.message.DbException: General error: "org.h2.mvstore.MVStoreException: Could not sync file /XXX/YYY/ZZZ.mv.db [2.1.214/2]" [50000-214]
Any thoughts on why this synchronization to the mounted decrypted volume causes these errors?

Ensure that the mounted decrypted volume is correctly formatted and mounted. Check the file permissions on the mounted decrypted volume to ensure that the wallet has sufficient permissions to write to the file. Check the disk and file system for errors or corruption. You can do this by running a disk check or file system check on the mounted decrypted volume. Make sure that the mounted decrypted volume has sufficient free space to accommodate the wallet file. If none of these steps resolve the issue, it may be helpful to try running the wallet on a different volume or on a different machine to see if the problem persists.

It's fairly clear (from reading the database code) that this error was caused by an IO error writing to the mounted volume, so I'm going to close this off.


Merge RailsAdmin config

I am developing a gem that installs RailsAdmin into a main application. The gem defines a document type (models) with basic attributes and RailsAdmin configuration. Other (yet to be developed) gems may define additional document types, such as invoice, order, ... - that require different attributes and, consequently, different RailsAdmin configuration.
The basic document type comes as a module, additional document types include the basic document type. If calling rails_admin do ... end multiple times, both in the module and the actual document class, configuration options will be overwritten. How can I merge different RailsAdmin configurations?
I need to be able to to this, for example:
module Base
  extend ActiveSupport::Concern
  included do
    rails_admin do
      parent Document
    end
  end
end

class Invoice
  include Base
  rails_admin do
    navigation_icon 'icon-file'
  end
end

After that, Invoice should have Document defined as its parent in RailsAdmin.
Can RailsAdmin do this? If not, how would I go about implementing this in RailsAdmin in a smart way and without reinventing the wheel?
Thanks...
PS This has been asked before, but never answered.

#2670 made it possible.


Teamnado 3337 with new ammends per AC updates, request to merge to main

Codecov Report
Base: 89.51% // Head: 89.54% // Increases project coverage by +0.03% :tada:

Coverage data is based on head (b7d4932) compared to base (fda0ad4).
Patch coverage: 100.00% of modified lines in pull request are covered.

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

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #107      +/-   ##
==========================================
+ Coverage   89.51%   89.54%   +0.03%
==========================================
  Files          42       42
  Lines         658      660       +2
  Branches      119      122       +3
==========================================
+ Hits          589      591       +2
  Misses         69       69

Impacted Files
Coverage Δ

src/components/SCAStatusSwitch/SCAStatusSwitch.tsx
100.00% <100.00%> (ø)

.../SatelliteManifestPanel/SatelliteManifestPanel.tsx
75.73% <100.00%> (+0.36%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

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

I have made suggestions changes for clean up , let me know if you see anything else


ENH: Prefer scipy.fft to scipy.fftpack in scipy.signal

Change scipy.signal to prefer scipy.fft over scipy.fftpack and scipy.fft.rfft over np.fft.rfft.
Have not tested locally, let's see if this works. Will push commits to fix when it inevitably doesn't.

https://github.com/scipy/scipy/blob/a9dab60b053ab21da792aacace7a1b157cee9932/scipy/signal/signaltools.py#L487 should be re-tuned for the new fft implementation

https://github.com/scipy/scipy/blob/a9dab60b053ab21da792aacace7a1b157cee9932/scipy/fft/_helper.py#L53
also add a real or complex parameter to next_fast_len() and handle the higher radix sizes?

should be re-tuned for the new fft implementation

Ahh yes I'll probably need to look at the old PR to figure out how to tune it. If you have time to check and/or remember how, feel free.

also add a real or complex parameter to next_fast_len() and handle the higher radix sizes?

I think @peterbell10 might already have an issue about this, if not feel free to open one

I think @peterbell10 might already have an issue about this, if not feel free to open one

There was some related discussion in #10240, it may deserve it's own issue though.

Ahh yes I'll probably need to look at the old PR to figure out how to tune it. If you have time to check and/or remember how, feel free.

Yeah I have the script around somewhere

Turned the updating into a new issue.
Our implementation in this PR should be at least as fast as what was done before, so at worst we are performing as well as we were before (when using time-domain) and better than before (when using freq-domain), so a follow-up PR to further tune stuff should be fine, and not a blocker for this PR.
@endolith okay with you?

Yes that's fine

@peterbell10 it might be best to merge this one first. I'll push a commit to remove the thread locking comment, then I think it should be good to merge if you're happy.

@peterbell10 do you want to click the green button? It's already a single commit so any of the three merge options are fine but I usually do "rebase and merge"

I’m getting a status 500 server error when I try to open this specific PR…


Is a step missing?

Perhaps a step is missing? I'm running a dev container that doesn't have azd and I want to add azd. The page goes from prereqs to updating.

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

ID: 2f283f7f-dc6c-e976-8994-7b685852b701
Version Independent ID: 2f283f7f-dc6c-e976-8994-7b685852b701
Content: Install the Azure Developer CLI
Content Source: articles/azure-developer-cli/install-azd.md
Service: azure-dev-cli
GitHub Login: @alexwolfmsft
Microsoft Alias: alexwolf

Thanks, this will be resolved in the next docs publish.
#please-close


Return null if config is not found

Before:
try {
  const config = await context.config('foobar.yml');
  // do stuff with the config
} catch (err) {
  if(err.code !== 404) {
    throw err;
  } else {
    // config was not found
  }
}

After:
const config = await context.config('foobar.yml');

if (config) {
    // do stuff with the config
} else {
    // config was not found
}

cc @hiimbex

I would actually say that before looked more like:
let config;
try {
  const config = await context.config('foobar.yml');
} catch (err) {
  if(err.code !== 404) {
    throw err;
  } else {
    // config was not found
  }
if (config) {
  //do stuff
}
}

Because if any of your later code had the chance to error, you wouldn't want it in the same catch block. So that just makes this change even better! 🎉

I like this a lot! Removing that try/catch from my own probot code will make me very happy. @bkeepers, when a default object is passed should it return that default object or still null?
There are pros and cons each way, the biggest con I can think of is not knowing whether or not it error-ed, but that may not be relevant if you're still getting that default object. It would also likely remove the need for that if (config) in a lot of cases. If people needed to be more granular, like requiring a non-defaultable API key in a config, they could still do if (!config.APIKey).

@bkeepers, when a default object is passed should it return that default object or still null?

That's a great question. I think it makes sense to return the default.

:sparkles: @bkeepers I'll go ahead and make a separate PR for that.


feat: Add timestamp option to set property names

Closes #142
We facilitate this change by returning the full TOptions from schema construction rather than just TDefaults. We can then access the default values from TOptions when needed. With full access to the options config we can appropriately se the timestamp property names.
This also adds a $timestamps property on the schema return value which is ultimately removed in updateSchema. This gives us runtime access to the timestamp property names.
Diff best viewed with --ignore-space-change.
BREAKING CHANGE: Changes the return type for schema and the generic arguments for model and various utils

I don't expect a lot of changes in performance from this PR, but given how many changes it contains, would you mind posting some results from running yarn benchmark on main vs this PR?

@avaly

PR benchmark results
mongodb.insert ~ 1036.25 ops/sec
papr.insert ~ 1025.58 ops/sec
mongoose.insert ~ 587.50 ops/sec
---
mongodb.find ~ 894.48 ops/sec
papr.find ~ 846.84 ops/sec
mongoose.find ~ 571.47 ops/sec
---
mongodb.update ~ 1096.22 ops/sec
papr.update ~ 1051.26 ops/sec
mongoose.update ~ 942.88 ops/sec

main benchmark results
mongodb.insert ~ 1047.50 ops/sec
papr.insert ~ 1041.87 ops/sec
mongoose.insert ~ 578.04 ops/sec
---
mongodb.find ~ 900.91 ops/sec
papr.find ~ 878.20 ops/sec
mongoose.find ~ 563.92 ops/sec
---
mongodb.update ~ 1004.04 ops/sec
papr.update ~ 975.30 ops/sec
mongoose.update ~ 883.93 ops/sec

As expected, nothing out of the ordinary 👍

ping @avaly - any feedback from internal testing? I've just rebased this to catch up with recent changes

@joshuat Sorry for the delay, we've been blocked a bit on this testing due to mongodb v4.9.0 which introduced a regression. Now that v4.9.1 is out, I'll give this a try next week.


Consider adding more information about how Hot Patching differs from traditional patching

The 'How hotpatching' section is very sparse on details.  A reader might expect a terse technical summary of how Hot Patching is able to work and why reboots aren't needed, where traditional windows needed to reboot to apply a patch.

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

ID: bc698477-83d9-7411-f504-8d485377be73
Version Independent ID: 9cce0660-efaf-2bd3-c6da-bd9475487b9e
Content: Hotpatch for Windows Server Azure Edition (preview)
Content Source: articles/automanage/automanage-hotpatch.md
Service: virtual-machines
Sub-service: automanage
GitHub Login: @ju-shim
Microsoft Alias: jushiman

@1RedOne
Thanks for the feedback! I have assigned the issue to content author to check and update the document as appropriate.

@ju-shim
Can you please check and add your comments on this doc update request as applicable.

I created a work item for this feedback on my end and started the conversation with the PM team. They're done recent work around this doc, so it's much better. It will be up to them to make further improvements, but know your comments were passed along and I support these recs. Thank you for your help! #please-close


[Bug] import * as echarts from 'echarts/core' get error: export * from './lib/export/core.js';

Version
5.4.3
Link to Minimal Reproduction
no
Steps to Reproduce
1、import * as echarts from 'echarts/core'
2、get error:
export * from './lib/export/core.js';
^^^^^^
SyntaxError: Unexpected token 'export'
at Object.compileFunction (node:vm:352:18)
at wrapSafe (node:internal/modules/cjs/loader:1033:15)
at Module._compile (node:internal/modules/cjs/loader:1069:27)
at Object.Module._extensions..js (node:internal/modules/cjs/loader:1159:10)
Current Behavior
export * from './lib/export/core.js';
^^^^^^
SyntaxError: Unexpected token 'export'
at Object.compileFunction (node:vm:352:18)
at wrapSafe (node:internal/modules/cjs/loader:1033:15)
at Module._compile (node:internal/modules/cjs/loader:1069:27)
at Object.Module._extensions..js (node:internal/modules/cjs/loader:1159:10)
Expected Behavior
no error
Environment
- OS:
- Browser:
- Framework:

Any additional comments?
No response

Hi. This is a typical JavaScript question (where you should use import * from instead of export * from) and does not relate to ECharts. So I'm going to close this issue.

Hi, I have encountered the same issue, node.js version: 18.12
to @Ovilia Please  :
that the code written by the user is
import * as echarts from 'echarts/core'

while the code written by eccharts is
export * from './lib/export/core.js';

https://github.com/apache/echarts/blob/fa231d37fe2788f5c8dfa5a86299ea8339d60897/build/template/core.js#L20

where you should use import * from instead of export * from

So, it seems to be related to Echarts

@Ovilia It is related to Echarts. It seems that something is wrong with JS modules in ECharts.

嗨。这是一个典型的 JavaScript 问题（您应该使用 import * from 而不是 export * from），与 ECharts 无关。所以我要关闭这个问题。

✓ Creating an optimized production build
✓ Compiled successfully
Collecting page data ../Users/acme/Desktop/project/WorkGPT/node_modules/.pnpm/echarts@5.4.3/node_modules/echarts/core.js:20
export * from './lib/export/core.js';
^^^^^^
SyntaxError: Unexpected token 'export'
这不是你组件里面的export问题吗？


Implement ordinal regression GLM (ordered_logistic_glm_lpmf)

Summary
This implements ordinal regression GLM (ordered_logistic_glm_lpmf) for CPU.
Tests
New tests are in rev/mat/prob/ordered_logistic_glm_lpmf_test.cpp.
Side Effects
None.
Checklist

[x] Math issue #1251

[x] Copyright holder: Tadej Ciglarič, University of Ljubljana
The copyright holder is typically you or your assignee, such as a university or company. By submitting this pull request, the copyright holder is agreeing to the license the submitted work under the following licenses:
- Code: BSD 3-clause (https://opensource.org/licenses/BSD-3-Clause)
- Documentation: CC-BY 4.0 (https://creativecommons.org/licenses/by/4.0/)

[ ] the basic tests are passing

unit tests pass (to run, use: ./runTests.py test/unit)
header checks pass, (make test-headers)
docs build, (make doxygen)
code passes the built in C++ standards checks (make cpplint)

[x] the code is written in idiomatic C++ and changes are documented in the doxygen

[x] the new changes are tested

I measured speedups of this compared to using ordered_logistic_lpmf(). Benchmark code is here. Here are results:

Whether multiplication is expensive or not depends on the context.  It's slower than addition, but faster than exponentiation and much faster than a cache miss on memory.
Doesn't evaluating .(cut > 0) require branching.  I can imagine it's better at allow vectorization than a literal branch in the code.
If you know how to do it, it would be great to speed up Stan's vectorized functions.  As is, they're vectorized naively by just calling the function repeatedly.  Not in this PR, of course!

cut>0 is just a comparison, not a branch. I am not sure, but I think comparisons can be vectorized.
Explicitely vectorizing code requires use of intrinsics, which is tedious and not portable. Luckily Eigen does it, so we do not have to. I just assume all Eigen expression will produce vectorized binary code. While there might be exceptions, Eigen expessions seem to always results in equivalent or faster calculations than doing things element-wise.

On May 28, 2019, at 2:54 PM, t4c1<EMAIL_ADDRESS>wrote:
cut>0 is just a comparison, not a branch. I am not sure, but I think comparisons can be vectorized.

That would be cool if they could be vectorized.  It's not a branch in the if/then structure, but internally, it has to be doing a comparison and taking different behavior based on the result as that's the semantics.  But it may be encapsulated such that it doesn't look like a branch to the compiler.  That's why I was asking.  My compiler knowledge isn't that deep.

Explicitely vectorizing code requires use of intrinsics, which is tedious and not portable. Luckily Eigen does it, so we do not have to. I just assume all Eigen expression will produce vectorized binary code. While there might be exceptions, Eigen expessions seem to always results in equivalent or faster calculations than doing things element-wise.

That seems to imply we should redo our vectorization to lean on whatever Eigen's using to do it.  I'm not saying we should write our own proper vectorization library, just that we might be able to lean on Eigen's.  You seem to be writing faster versions of our vectorized functions using Eigen.  I'd like to expose that to users as elementwise application of functions happens everywhere.

taking different behavior
That is not true. Comparisons are basic CPU instructions, just like for example adition. Just the result is either 0 or 1. Comparisons without if/loop are not branches.

I think I see what you're getting at.  Just because comparison has an intrinsically branching behavior, it doesn't entail generating branching instructions.  Is the relevant feature here whether you need to jump for one of the branches?
On a side note, do you know if the ternary conditional operator (a ? b : c) generates branches?
There's a lot of bad folk wisdom around all this stuff and I've never dug into it deeply enough or found it made enough of a difference to show up in end-to-end profiling.  So thanks for bearing with.

On May 28, 2019, at 5:03 PM, t4c1<EMAIL_ADDRESS>wrote:
taking different behavior
That is not true. Comparisons are basic CPU instructions, just like for example adition. Just the result is either 0 or 1. Comparisons without if/loop are not branches.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

Sorry, I don't understant, what do you mean with the first question. Ternary operator is a branch.
On a side note I assume we want this GLM to have similar input types as softmax regression.

Let me elaborate with an example.  Let's say I have a naive implementation of absolute value using the ternary operator.
a > 0 : a ? -a

The question is whether this generates branching instructions or not.  How would that compare to the
(a > 0) * a + (1 - (a > 0)) * -a

which shouldn't generate any branching.  I saw a Stack Overflow discussion about this recently which said the first version's faster on modern compilers, but now I can't find it.

FIrst one would generate a branch and second would not. However, both might be optimized by a compiler.

This test failure was expected and will disappear once PR1249 gets merged.

Do we have any volunteers to review this? Bob's and my intial comments were addressed so this is definitely ready for a proper review.

@andrjohns This is ready for next review.


Secure Comparator example

Can you please create a sample project to demonstrate Secure Comparator usage? While I'm a mobile developer I'm having hard times to implement server part. Your sample project https://github.com/cossacklabs/theswiftalpsdemo is very useful and it would be nice to see a similar one for Secure Comparator. Or at least simple instructions how to modify it to add Secure Comparator functionality. Thanks!

Sure, will try to add some example.
Do you prefer HTTP of websockets as transport layer?

HTTP sound good. Thanks a lot!
On Mon, Nov 19, 2018 at 2:20 PM vixentael<EMAIL_ADDRESS>wrote:

Sure, will try to add some example.
Do you prefer HTTP of websockets as transport layer?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/cossacklabs/themis/issues/341#issuecomment-439874833,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKzMPz_9CDn2GKCHjRwJ7xYdo_OAmhPoks5uwqH8gaJpZM4YoIHx
.


Fix the guid in the README  file

Actual Behavior
As the guid in the README, the version of JDK is 1.5.0, but there is something wrong when use the package io.dapr.Rule;
and it's used in example file also。
when configure the 1.5.0 version, can't find the package but 1.6.0 is ok.
RELEASE NOTE: FIX README guid content

If the Rule is for pubusb routing, that is only there from 1.6.

Can you check master branch now? I think that it was fixed with release of 1.6 and updating README in master branch.

yes, it's already fixed in the master


Cant create a vault (BadRequest 400)

What happened:
Cant create a vault. Failed to convert UTXO (Error Code: 0 400 BadRequest):

What you expected to happen:
Can create a vault.
How to reproduce it (as minimally and p
recisely as possible):
Try to create a vault.
Anything else we need to know?:
iPhone 13

@7schlaefer Hi, can you check if you have at least 3 DFI (UTXO)?

@thedoublejay had only 2,099 UTXO but 130 Token. I converted 5 tokens. Now it works. But isn't that exactly what the conversion is supposed to do?

@7schlaefer Yes, but in this case, you might have been in the boundary of 2 UTXO (vault fee) and TX fee. So the automatic conversion will fail


rolling update: skip pg check if num_pgs = 0

In our test case we don't have any pgs, thus the check fails. The check
always returns an empty array, which makes the comparaison failing.
Signed-off-by: Sébastien Han<EMAIL_ADDRESS>

jenkins test luminous-ansible2.3-update_cluster

jenkins test  luminous-ansible2.3-update_docker_cluster

jenkins test luminous-ansible2.3-update_docker_cluster

jenkins test luminous-ansible2.3-update_docker_cluster

jenkins test luminous-ansible2.3-update_docker_cluster

jenkins test luminous-ansible2.3-update_cluster

CI is green, I'm going to remove the debug task and merge right away. There is no need to wait again for the CI to run.


Bug 2124597: Datasource Typo

Signed-off-by: Matan Schatzman<EMAIL_ADDRESS>
📝 Description
With Form => With form
🎥 Demo

Please add a video or an image of the behavior/changes

@pcbailey @upalatucci @hstastna  PTAL :)

/bugzilla refresh

/lgtm


Describe the timeout when the scripts are executed  via Power Automate

The script which is successful via Excel is sometimes failed via Power Automate due to timeout. #504 GatewayTimeout
Could you describe it as a limitation?

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

ID: 4085c6ff-856c-4704-8d72-5ef0ca1f64c1
Version Independent ID: 92eda514-0e20-3add-4b61-62d82d210549
Content: Platform limits and requirements with Office Scripts - Office Scripts
Content Source: docs/testing/platform-limits.md
Product: excel
Technology: scripts
GitHub Login: @o365devx
Microsoft Alias: o365devx

Thanks for reaching out. @AlexJerabek, could you help to take a look?

Thank you for reporting this documentation gap @MiyukiAmino. I will begin investigating and work on updating the documentation accordingly.

Hi @MiyukiAmino,
I've created PR https://github.com/OfficeDev/office-scripts-docs/pull/443 to highlight this timeout. If you'd like specific advice about optimizing your script to avoid the timeout, I'd recommend posting on Stack Overflow with the tag office-scripts. Stack Overflow is a good forum our team and members of the community to help with specific issues.
Please let me know if you have any concerns with the PR or any other questions. Otherwise, this issue will close when the PR is checked in.


Image Operation: tint

This would tint the image towards the specified color and density.
density defines how much (in percentage) the tint color is applied over the original image.
I think this is a fundamental feature.

Can this be achieved by pasting a semi-transparent colored canvas on top of the image?


ERROR: ld.so: object 'libcaffe2_gpu.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.

Describe the bug

ERROR: ld.so: object 'libcaffe2_gpu.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.

Steps to Reproduce the Problem

execute the command cd carla_apollo_bridge/docker && ./build_docker.sh && ./run_docker.sh
enter cyber container : docker exec -ti carla_cyber_0.9.13 bash

Screenshots or Video

Environments (please complete the following information):

System info: Linux jia 5.15.0-69-generic #76~20.04.1-Ubuntu SMP Mon Mar 20 15:54:19 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
Cuda version: NVIDIA-SMI 525.105.17   Driver Version: 525.105.17   CUDA Version: 12.0
Docker version: Docker version 20.10.17, build 100c701
Docker-compose version: Docker Compose version v2.0.1

Hi @NavyHub , Have you solved this issue? I meet this problem too.

I also encountered this problem, but it does not seem to affect the normal operation, let's troubleshoot this problem together.
root@f0a9ff4d588e:/apollo# ./apollo.sh build_cyber opt
ERROR: ld.so: object 'libcaffe2_gpu.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object 'libcaffe2_gpu.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object 'libcaffe2_gpu.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object 'libcaffe2_gpu.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object 'libcaffe2_gpu.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object 'libcaffe2_gpu.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object 'libcaffe2_gpu.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
System check passed. Build continue ...
ERROR: ld.so: object 'libcaffe2_gpu.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object 'libcaffe2_gpu.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object 'libcaffe2_gpu.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object 'libcaffe2_gpu.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
[WARNING] ESD CAN library supplied by ESD Electronics does not exist. If you need ESD CAN, please refer to third_party/can_card_library/esd_can/README.md.
ERROR: ld.so: object 'libcaffe2_gpu.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
Running build under CPU mode. No GPU is required to run the build.
[INFO] Start building, please wait ...
INFO: Reading 'startup' options from /apollo/tools/bazel.rc: --batch_cpu_scheduling --host_jvm_args=-XX:-UseParallelGC
Extracting Bazel installation...
.......
____Downloading file:/home/tmp/v1.14.2.tar.gz: 9,158,656 bytes
____Loading package: cyber/examples
[INFO] Building on x86_64...
[INFO] Building with --jobs=12 --ram_utilization_factor 80 for x86_64
INFO: Reading 'startup' options from /apollo/tools/bazel.rc: --batch_cpu_scheduling --host_jvm_args=-XX:-UseParallelGC
INFO: (05-10 02:52:32.147) Found 547 targets...
Slow read: a 35277032-byte read from /root/.cache/bazel/_bazel_root/540135163923dd7d5820f3ee4b306b32/external/fastrtps/lib/libfastrtps.so.1.5.0 took 5115ms.
INFO: (05-10 02:54:47.015) Elapsed time: 136.972s, Critical Path: 34.37s
[INFO] Skipping revision recording
============================
[ OK ] Build passed!
[INFO] Took 882 seconds
============================

Hi @NavyHub , Have you solved this issue? I meet this problem too.

The same problem can be found here:https://github.com/ApolloAuto/apollo/issues/8833
You can modify the /apollo/apollo_base.sh file and comment out the following configuration line of code
  export LD_PRELOAD="$PRELOAD"

Hi @NavyHub , Have you solved this issue? I meet this problem too.

@JasonBourne1998 We have fixed this error, you can pull the code, delete the carla_cyber_0.9.13 image of this machine, and build.

It looks like this issue hasn’t been active in longer than a few weeks. In the absence of more information, we will close it, If you find that this is still a problem, please feel free to reopen it.


Filtering, multiple SNMP exporters

Hey !
Just read your blog post regarding Prometheus and Netbox, thanks, very interesting!
I plan to use your project, and I want to add filtering of retrieved devices (including auto-filtering of the master device of Virtual-Chassis devices) based on any field (tenant, region, ...)
We're using Blackboxes as SNMP exporter on each site location, which means the target_label: __address__ replacement should be dynamic based on the device site. I think there is no other solution than multiple jobs.
I would like to include snmp module selection based on device_type + role instead of __snmp_module__ in Netbox prom_labels field
I was considering using jinja templates before I found your more elegant solution.
And also, I want to have the prometheus jobs config file generated automatically, probably the only way if I want 1 job per site / role
What do you think about this?
I'll share my achievements in the following weeks

Hi Yannis!

I plan to use your project, and I want to add filtering of retrieved devices (including auto-filtering of the master device of Virtual-Chassis devices) based on any field (tenant, region, ...)

Filtering can be implemented using the Prometheus relabeling feature with the "drop" action. Details here: https://prometheus.io/docs/prometheus/latest/configuration/configuration/#relabel_config. Is this helps you? It would avoid to implement something complex into the project.

We're using Blackboxes as SNMP exporter on each site location, which means the target_label: address replacement should be dynamic based on the device site. I think there is no other solution than multiple jobs.

A solution I imagined (but never implemented) to address this problem is a kind of inheritance of the target_label custom field. The target_label custom field would be also created on tenant / parent / rack / pop / site and precedence between duplicate labels is made on a "most specific" basis (eg: label defined on rack take precedence on the one defined on the site) . This way, you can override the __address__ label for all devices located on a site and all the data (including the SNMP targets IPs) are stored in Netbox and not the Prometheus config.

I would like to include snmp module selection based on device_type + role instead of snmp_module in Netbox prom_labels field

I'm not sure to understand what you want to achieve here, but I prefer to avoid to implement a behavior specific to an exporter or an usage. Is this can be implemented using the relabeling feature?
Antoine

Thanks for your answer!
For the filtering, using 'drop' might help but as our Netbox database is quite big, I would prefer to filter when gathering rather than processing. I don't think it will be too hard to implement, either using argparse or a separated "config file".
The "hard" part is to translate the args to filters but the only line that will change (L.19) is
devices = netbox.dcim.devices.filter(manufacturer=manufacturers, has_primary_ip=True, tenant=filterTenant, status=1)

A solution I imagined (but never implemented) to address this problem is a kind of inheritance of the target_label custom field.

This could be great, we currently "extrapolate" the target_label replacement from site (pop) slug with a template name, but a custom_field can be good too

I'm not sure to understand what you want to achieve here, but I prefer to avoid to implement a behavior specific to an exporter or an usage. Is this can be implemented using the relabeling feature?

The idea is to be able to specify a module name extrapolated from other values than the prom_labels custom field like: {$device_manufacturer}_{$device_role}
I understand you prefer to avoid implementing this kind of specific behavior, it was just an idea to increase flexibility in usage but I'm not sure there is a good way to implement it, I'll let you know.
To help you understand my need, I attached the script we wrote internally
cfgGenerator.zip

Hi Yannis, really sorry for my silence. Hard to find time to work on this project right now. Do not hesitate to propose a PR, I'll take time to review and merge it.


Simplify UUID hash specialization

Just a quick note I wanted to call out after watching the UUID video which popped up on my feed the other day.
The purpose of std::hash is to create a uniformly distributed value from some type. std::hash<uint64_t> exists because arbitrary uint64_t values aren't inherently uniformly distributed. However, the uint64_t generated for Hazel::UUID is uniformly distributed. Because of this there is no need to hash it, it can simply be returned.
Additionally including <xhash> directly isn't advisable. It is an internal header to the Microsoft STL implementation and therefore is not portable and can even be changed or removed. std::hash can just be forward declared anyway so you don't have to include (the very heavy) <functional> either.
Last note, which I did not make a change for, is that the uint64_t value should be casted to size_t when returned. Compiling for 32-bit will cause warning otherwise as it is an implicit narrowing conversion. Although size_t is generally the same basic type as uint64_t it isn't guaranteed by the standard so a static_cast would be appropriate for portability.
I'm glad people are gravitating to your channel for this content, its cool to see someone walking through making a game engine in a way non-engine devs can understand. Dropping these notes here just in case they are helpful for others who pass by.

Great point! 😅


Cluster jobs fail claiming mamba is missing, even though mamba is present, and even if conda backend is specified

Snakemake version
6.4.0 (not present in 6.3.0)
Describe the bug
Cluster jobs fail with an error saying mamba is not found. Mamba works for the workflow up until submission, and the error is still present when using --conda-frontend conda. I am using FISH as my main shell, but the rules are running in BASH. Both my config.fish and .bashrc load conda envs that have mamba.
Logs
The following error shows up in the cluster log:
Error: mamba package manager is not available. The mamba package manager (https://github.com/mamba-org/mamba) is an extremely fast and robust conda replacement. It is the recommended way of using Snakemake's conda integration. It can be installed with `conda install -n base -c conda-forge mamba.If you still prefer to use conda, you can enforce that by setting `--conda-frontend conda`.

Minimal example
Mamba works for generating the environments, but it breaks when it tries to run the rules. I'm using the following command:  snakejob -pj 600 --use-conda
snakejob looks like this:
#!/usr/bin/env bash

set -e

if [ ! -d ".snakejob" ]; then
  mkdir .snakejob
fi

curdir="$(pwd)"
jname="$(basename $curdir)"

bsub=("bsub -K -J $jname:{rule}:{wildcards}"
"-P {cluster.project} -q {cluster.queue}"
"-n {cluster.cores} -R \"span[hosts=1] select[mem>{cluster.mem}]"
"rusage[mem={cluster.mem}]\" -W {cluster.time} -L /bin/bash"
"-oo .snakejob/{rule}:{wildcards}.stdout"
"-eo .snakejob/{rule}:{wildcards}.stderr < ")

snakemake -u cluster.yaml --cluster-sync "${bsub[*]}" \
  --local-cores 4 --max-jobs-per-second 5 "$@"

It's basically a script that allows me to use a cluster config file on lsf. I know this behavior is technically deprecated, but we have not been able to implement profiles to our satisfaction.

Also, as an aside @BEFH - there is an LSF profile already https://github.com/Snakemake-Profiles/lsf

Is there an update on this bug? The LSF profile does not work with our cluster.

Please raise an issue on the LSF profile if it isn't working on your cluster, all bugs are very much appreciated.
Regarding this issue, could you provide an example of one of the rules that uses a conda environment that is failing to run?

I fixed this by switching from the anaconda base provided by the cluster admins to my own installation. My theory is that it was due to a problem with incorrect order of paths in the PATH variable. Snakemake shouldn't be susceptible to that since it supposedly passes the conda path (and I confirmed this in the cluster logs), but I have no way of properly debugging this at this point.
It happened both with bash shell rules with conda environments and without, as long as --use-conda was specified.
It also happened on Snakemake 6.7.0 and 6.8.0.

I'm having the same problem. When I run  snakemake --use-conda -k -j 8 I get:
Error: mamba package manager is not available. .....
and when I run
snakemake --use-conda -k -j 8 --conda-frontend conda
I get:
CreateCondaEnvironmentException:
The 'conda' command is not available in the shell /usr/bin/bash that will be used by Snakemake. You have to ensure that it is in your PATH, e.g., first activating the conda base environment with `conda activate base`.

outside of snakemake, mamba and conda work just fine, so they are definitely available. Snakemake for some reason does not find them?

@slambrechts, what shell are you using as your login shell and what are you using as your Snakemake shell? That might have something to do with it.

I'm getting the same issue. The fix from #1019 only works if mamba is installed on the base environment.