Do not warn about private link to private symbols

The following:
module Private (
  bar,
  Foo(a),
  ) where

-- | 'foo' is really great, and uses 'bar'. This reference to 'foo'
-- will triggers a warning when it is actually never used in the final
-- document, because this documentation is private.
foo = undefined

bar = undefined

class Foo t where
  a :: t
  b :: t

Leads to the following warnings when using haddock Private.hs:
Warning: Private: could not find link destinations for:
    b foo

The link to foo cannot be resolved because the documentation for foo won't be exported. However the link to foo is inside an unexported piece of documentation, so this is not an issue. I then consider that this warning can be discarded.
The link to b will appear in the minimal complete definition exported for Foo. I agree that b appears on the minimal complete definition (see #330), but a warning should not be generated. I also think that the documentation must explicitly say that b is not exported, with something such as Minimal complete definition: a, b (private).

These warnings are especially annoying in continuous integration where we want to fail if haddock returns any warning. See for example the work of #927.
This was tested with ghc 8.8.1 (currently in rc status). Similar results appears with ghc 8.6.5.

cc @ghorn

Note that due to these bugs, it is close to impossible to build a warning free documentation because a few base elements triggers theses warnings.

Thanks for the bug report! I agree with everything you pointed out.

Note that an easy workaround is to:

export the missing symbols
Do not make any link to the hidden symbol in hidden documentation (or do not write hidden haddock). This does not work for the class functions.

I've been thinking about this a bit more.

The minimal complete definition is a bit of an edge case. We can fix it with some custom code and maybe we should.

The link to the hidden symbol is an interesting manifestation of another problem: Haddock doesn't have a good way of keeping track of which docs will somehow get used, so it processes every docstring (and during renaming, warns about there not being a link destination).
I think we should figure out how to filter out docstrings for "private" names earlier. We shouldn't have to do any work on docstrings (including the link resolution that triggers the warning from this issue) if they aren't even used. Fun fact: although the hidden docstrings don't show up in the docs, they show up in the *.haddock interface files!

Do shout if this was closed without properly resolving all the issues. After the PR that closed this issue, I see no more link warnings for the initial test case.
$ haddock Private.hs --html
Haddock coverage:
Warning: Package name is not available.
   0% (  0 /  3) in 'Private'
  Missing documentation for:
    Module header
    bar (Private.hs:11)
    Foo (Private.hs:13)

@harpocrates This bug seems to have reappeared:
$ haddock --html Private.hs
   0% (  0 /  3) in 'Private'
  Missing documentation for:
    Module header
    bar (Private.hs:11)
    Foo (Private.hs:13)
Warning: Private: could not find link destinations for:

	- Private.foo

$ haddock --version
Haddock version 2.25.1, (c) Simon Marlow 2006
Ported to use the GHC API by David Waern 2006-2008
$ ghc --version
The Glorious Glasgow Haskell Compilation System, version 9.0.2


Workflow documentation

there is a </code> left in the workflow documentation:

PS: are there any use cases for pc-segmentation ? As far as I remember this was the worst of all options a year ago during my tests.

are there any use cases for pc-segmentation ? As far as I remember this was the worst of all options a year ago during my tests.

Yes, and the dependencies were becoming too difficult to handle, that's why we disabled this by default in ocrd_all a while ago.

there is a </code> left in the workflow documentation:

You can make changes to the WF guide here on the Wiki BTW – it gets synced back from time to time.


plugin fall into endless loop

1、Current vite-plugin-vue-devtools version: 7.0.5
2、Call stack

3、the route may have circular reference

Can you provide a mini repo or share the routes config? Thank you.

I have the same problem again！and there are issues with the development environment!!!!

  I have the same problem again！and there are issues with the development environment!!!!

Can you provide a mini repo or share the routes config? Thank you.

Fixed in v7.0.10


Styling: Changing $nav-text doesn't change toc text, only search bar

Operating system: macOS Sierra
Last upstream commit: @17b259a40da6ef3e0561db76371754b6620e1e43
Browser version(s): Firefox Nightly, 58.0a1
Ruby version (run ruby -v): ruby 2.4.2p198

I'm trying to style the sidebar to have a white background and grey text. I changed $nav-bg and $nav-text.
The change to $nav-text only seems to affect the search box though, the toc nav links are still  hardcoded to be #fff at https://github.com/lord/slate/blob/bdb693031027c2e5af77cb709cb86836c3e2e74c/source/stylesheets/screen.css.scss#L208.
Screenshots:

I think that changing the line I mentioned to use $nav-text should do the trick. Let me know if that sounds good, I'll send in a PR

:+1: would love a PR, thanks!


cases add negative case for agg table and fix agg table support replace typ…

…e and fix test output
Proposed changes

add negative case for agg table
fix agg table support replace agg type for complex type
fix test output
Issue Number: close #xxx

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

run buildall


Fixing SalesGPT.from_llm to accept both json and boolean args

It's a simple implementation that fix one line I forgot to change in the last fix. I also refactored tests to make sure it's working.

@chemik-bit is this done? I think I saw this somewhere merged. Thx!


New function request: changes to 'get_custom_effort'

@damianooldoni following our meeting of 09/09/'24, @jimcasaer and I suggest the following changes to the get_custom_effort function:
inputs: no changes required
outputs:

[ ] return the effort per group: one of "day", "week", "month", "year" and per deploymentID
[ ] add a column deploymentID to the output data.frame
[ ] add a column locationName to the output data.frame

This allows users to seamlessly calculate the total effort over all deployments (current default behaviour), effort per location or effort per deployment. (We could also add a new input parameter level that is one of: "overall", "location", "deployment" that acts as a switch between the desired output -- total effort - effort per location - effort per deployment. Then users do not have to calculate this themselves).

I worked out an example of the function (extract the R-script in the zip-file and run locally): get_custom_effort2.zip

This issue is strictly linked to existent one: https://github.com/inbo/camtraptor/issues/280. More or less same conclusions.
I will implement this soon and so updating to camtraptor 0.26.0.
Notice that I will think more about the future of get_effort() and get_custom_effort() (see #236) while working on camtraptor 1.0.0.


[WIP] Add HKT support

This is a long-term WIP, but it's probably good to open for early feedback.
The relevant RFC is here.

I have no clue why I'm listed as a co-author on 9399 and 6c3b 😬 I rebased, but my commits got interleaved.

Hi @erip,
Are you still working on this, should we close the PR?


[C++] Update vendored double-conversion

Describe the bug, including details regarding any error messages, version, and platform.
The current bundled double-conversion can't be built on LoongArch:
-- Configuring incomplete, errors occurred!
See also "/home/loongson/tmp/aa/arrow/cpp/build/CMakeFiles/CMakeOutput.log".

loongson@loongson-pc:~/tmp/arrow/cpp/build$ make
In file included from /home/loongson/tmp/aa/arrow/cpp/src/arrow/vendored/double-conversion/double-conversion.h:31,
                 from /home/loongson/tmp/aa/arrow/cpp/src/arrow/util/double_conversion.h:20,
                 from /home/loongson/tmp/aa/arrow/cpp/src/arrow/util/formatting.h:35,
                 from /home/loongson/tmp/aa/arrow/cpp/src/arrow/pretty_print.cc:41:
/home/loongson/tmp/aa/arrow/cpp/src/arrow/vendored/double-conversion/utils.h:118:2: error: #error Target architecture was not detected as supported by Double-Conversion.
 #error Target architecture was not detected as supported by Double-Conversion.
  ^~~~~
make[2]: *** [src/arrow/CMakeFiles/arrow_objlib.dir/build.make:466：src/arrow/CMakeFiles/arrow_objlib.dir/pretty_print.cc.o] 错误 1
make[1]: *** [CMakeFiles/Makefile2:684：src/arrow/CMakeFiles/arrow_objlib.dir/all] 错误 2
make: *** [Makefile:141：all] 错误 2

If we update vendored double-conversion to a version that includes https://github.com/google/double-conversion/pull/162 , we can fix the build error.
Component(s)
C++

Duplicated: #34792


add tessella

tessella is a lightweight Node.js Mapbox Vector Tiles server

@mikelmaron can you find someone to hit the merge button on these PRs? They're pretty much 'on the green' so to speak, all one has to do is merge and this repo will continue to be useful.

@tmcw looking into it

@mapsam will grab maintenance of this repo, thanks @mapsam 🙇

Thanks for the PR @stepankuzmin!
(and apologies for the delay!)
((and double thanks for the bump @tmcw))!
(((and triple thanks @mikelmaron for flaggin!)))


Improve Job Listing

Previously listing jobs handled pagination internally in a manner that was not fully in the spirit of reactor. This commit revises the code to use the scheduler client's built-in pagination, making the code more idiomatic and hopefully more robust.

Codecov Report

Merging #27 into master will decrease coverage by 0.07%.
The diff coverage is 100%.

@@             Coverage Diff              @@
##             master      #27      +/-   ##
============================================
- Coverage     98.14%   98.07%   -0.08%
+ Complexity       52       50       -2
============================================
  Files             3        3
  Lines           162      156       -6
  Branches          5        4       -1
============================================
- Hits            159      153       -6
  Misses            3        3

Impacted Files
Coverage Δ
Complexity Δ

...ler/spi/cloudfoundry/CloudFoundryAppScheduler.java
97.72% <100%> (-0.1%)
37 <11> (-2)

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 d63c983...840d082. Read the comment docs.

Closing this until when we revive the Scheduler for PCF efforts on the latest PCF stack. We need to rework it then anyway.


Appveyor releases expired

Just wanted to point out that it's now impossible to get the release from appveyor for the module extractor.
It would be much appreciated if you could get at least one release working.

I'd appreciate this as well. I unfortunately cannot build it at this point. Maybe host it on Mega or something instead of AppVeyor?

https://www.mediafire.com/file/te0fzrvpn0hftc5/Module_Extractor.rar/file
Working ModuleExtractor build, you're welcome :D

Perfect, thank you :D


FEATURE - Cashflow Statement

Are you a Fivetran customer?
yes, Christoph, Sustain.life
Is your feature request related to a problem? Please describe.
No visibility into cashflow situation based on current models
Describe the solution you'd like
We would like to see a cashflow report similar to the balance sheet etc.
Describe alternatives you've considered
using the report available in the Quickbooks UI
Additional context
Please indicate the level of urgency and business impact of this request
**Provide us context so that we can prioritize accordingly. -->
Are you interested in contributing to this package?
Yes, happy to help
implement this feature? -->

[ ] Yes, I can do this and open a PR for your review.
[ x] Possibly, but I'm not quite sure how to do this. I'd be happy to do a live coding session with someone to get this work implemented.
[ ] No, I'd prefer if someone else did this.  I don't have the time and/or don't know how to incorporate the changes necessary.

Hey @leinemann thanks so much for opening this Feature Request!
We have actually received a few other requests from users of this package to build out a cash flow statement as a final model. This will be a report we would like to integrate into the package in the near future. I imagine this will be a feature our team will work to integrate next quarter. It would be great to keep the conversation here once we start working on this feature as well!
I will have to re-jog my memory of all those cash flow statements I had to do in my accounting classes years ago. Because of that, it would be great to collaborate with you to validate the model once we have developed it! 😃

that is great, thanks @fivetran-joemarkiewicz! Yes, although far from being a finance expert, I can help to validate as I can compare against the reports that quickbooks offer where I can see things like balance sheet and PnL tying up already.

Hi @leinemann ! We've added the cash flow statement in the 0.7.0 release of our package. Can you update your packages.yml, test it out and let us know your thoughts and feedback?
We've also added some interesting configurability to customize your cash flow types and ordering! Read more about it in our Fivetran Community post.
Since this is resolved, we're going to close this issue, but please respond here if you have any thoughts or questions. Cheers!


Remove yarn.lock - stick to single source of truth (package-lock.json)

@Andarist I'm going to close this one only because of the changes coming with the move to
the plugins monorepo (hopefully this week or next). Thanks for putting this together though :beer:


Add Paper Citations to Repos

To help keep track of how MLPerf is being used, we should ask people to cite our work. I already created PRs for the training and inference repos.

Training paper (Please review and approve)
Inference paper

Similar PRs would also be good for the following:

https://github.com/mlcommons/tiny
https://github.com/mlcommons/mlcube
https://github.com/mlcommons/hpc

You could even include the "MLPerf: An Industry Standard Benchmark Suite for Machine Learning Performance" paper on the policies repo.

@TheKanter


Support Microsoft Edge

User Agent's from Microsoft Edge are currently unrecognized:
https://cdn.polyfill.io/v1/polyfill.js?ua=Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/42.0.2311.135 Safari/537.36 Edge/12.10240
Bit of background to their odd UA string: http://blogs.windows.com/msedgedev/2015/06/17/building-a-more-interoperable-web-with-microsoft-edge/

OK, no problem.  I'm going to give Edge the browser name ie, meaning "I am Edge".

Fixed in https://github.com/Financial-Times/polyfill-service/commit/9257d34b891bb4b1c579c8dc13c705696226f6e3


Screen not found in 'vnodes'

I can try use vnodes in Nuxt project. My code:
import { Screen, Node, Edge, graph } from 'vnodes'
But I get error message

duplicate https://github.com/ripbizz/vnodes/issues/13


WebView deprecated

Hi, works fine, just WebView is gonna be deprecated, could you please fix it?
Thanks

+1

Hi!
The react native doc say about WebView component:

Warning Please use the react-native-community/react-native-webview fork of this component instead. To reduce the surface area of React Native,  is going to be removed from the React Native core. For more information, please read The Slimmening proposal.

The
WebView component is used to render the iFrames.
waiting for the fix you can try this:
npm install --save react-native-webview
react-native link react-native-webview

then in the plugin folder, go to src/HTMLRenderers.js, remove WebView in {..} 'react-native';
and add this line
import {WebView} from 'react-native-webview';

works, but is their any plan to make change in the component??

works, but is their any plan to make change in the component??

i created PR #247  2 months ago, still waiting for merge
if you don't want to edit the files you can use the package directly from my fork
in package.json change
"react-native-render-html": "^4.1.2",

to
"react-native-render-html": "git+https://github.com/chr314/react-native-render-html.git",

I don't have enough time on my hands to maintain this plugin as I should.
I will have to find maintainers at some point, I'll keep you posted on that.

Hey @Exilz
if you can please review the #247 because webview will be extracted from react-native in the next version 0.60 https://github.com/facebook/react-native/releases
the change is very small, have a look when you have time
thanks

The related PR has been merged into master. Until it's properly reviewed and released on NPM by my colleague, you can make your package.json point towards the latest commit of this repo.

This is still an issue. On RN 0.60 if you try to embed an iframe, it will crash, as WebView is no longer part of RN.

This bug was fixed from react-native-webview 5 days ago here https://github.com/react-native-community/react-native-webview/releases/tag/v7.0.1
@Exilz Pleas update your version of react-native-webview asap.

@chr314 Thanks for the fork and the PR. I pulled from the latest master branch and attempted to pull from your fork but on both occasions when I need to render a webview from inside an HTML tag (what I use for react-native-render-html), it still throws an error.
"RNCWKWebView" was not found in the UIManager
I'm on React Native 61.1
Any thoughts on what might be happening? Are you able to render webviews successfully?

To solve my problem above, I just wrote a custom renderer for any iframe tags that came in.

I am closing because this issue has been resolved in a recent release.


Readme syntax highlighting

Noticed that the first few examples in README don't have PHP syntax highlighting.

Thanks for help)


Use websocketpp_02 namespace.

My change that did both the move and rename got recreated for some reason - and without these changes.
So here they are again.
Reviewers: @vinniefalco @josh-ripple

That's a lot of whitespace changes…
:+1:


Create a list of users to ignore (or automatically ignore bots based on an API call)

Done.

At least partially. It doesn't prevent bots from typing in commands and triggering sound effects, but it does avoid welcoming them to the channel.


SPDK - Storage performance development kit

Are any of the libraries spdk depends on ones that we should consider adding to vcpkg?

Are any of the libraries spdk depends on ones that we should consider adding to vcpkg?
This package depends on uuid, openssl, rdma and python packages provided by OS's package manager. As vcpkg does not provide python it shouldnt provide the rest. openssl may be an outstanding case, however, since the SPDK build system is based on GNU make, there is not way (I'm aware of) to have openssl installed via vcpkg and being used by make.
Correct me if I wrong

@Rastaban, any news?


https://github.com/google/styleguide/issues/656#issuecomment-997473119

This repository publishes copies of Google's internal style guides to
assist developers working on Google owned and originated open source
projects. Development on these guides does not take place here.
Substantive changes to the style rules and suggested new rules should
not be submitted as issues in this repository. Material changes must be
proposed, discussed, and approved on the internal forums first.
If an issue points out a simple mistake — a typo, a broken link, etc. —
then a correction might be made. However there is no commitment to do
so. Issues are normally closed without comment.

#637


quickstart.py: Client secrets must be for a web or installed app.

Steps to Reproduce the Problem

Create Service account and download JSON file with credentials
Run quickstart.py

Expected Behavior
The script works just fine, everything works from the box.
Actual Behavior
The traceback:
    Traceback (most recent call last):
  File "google_docs.py", line 46, in <module>
    main()
  File "google_docs.py", line 31, in main
    'credentials.json', SCOPES)
  File "/usr/local/lib/python3.7/site-packages/google_auth_oauthlib/flow.py", line 199, in from_client_secrets_file
    return cls.from_client_config(client_config, scopes=scopes, **kwargs)
  File "/usr/local/lib/python3.7/site-packages/google_auth_oauthlib/flow.py", line 159, in from_client_config
    'Client secrets must be for a web or installed app.')
ValueError: Client secrets must be for a web or installed app.

Specifications

Python version
Python 3.7.4
OS: Mac

Workaround:
The workaround I've found for this issue:
https://stackoverflow.com/a/61892378/7856072
(this workaround proves that credentials.json is the correct file for authorization and account has all necessary rights).

Hi there!
I followed all steps to run quickstart.py but it shows this output:
Traceback (most recent call last):
  File "C:\Users\aleon\Documents\lab\python\CRM_SUB\script\quickstart.py", line 57, in <module>
    main()
  File "C:\Users\aleon\Documents\lab\python\CRM_SUB\script\quickstart.py", line 30, in main
    flow = InstalledAppFlow.from_client_secrets_file(
  File "C:\Users\aleon\Documents\lab\python\CRM_SUB\script\venv\lib\site-packages\google_auth_oauthlib\flow.py", line 201, in from_client_secrets_file
    return cls.from_client_config(client_config, scopes=scopes, **kwargs)
  File "C:\Users\aleon\Documents\lab\python\CRM_SUB\script\venv\lib\site-packages\google_auth_oauthlib\flow.py", line 159, in from_client_config
    raise ValueError("Client secrets must be for a web or installed app.")
ValueError: Client secrets must be for a web or installed app.

Where could I download the credentials.json from?

I am getting the same error I have downloaded the service account from my project and trying to delete my older emails. Can someone help me understand what I am doing wrong here ?


Erroneous data format for unserializing error on PHP 7.2

Bug report
Preconditions
1. framework Version- 1.1.0, 1.1.1 ,1.1.2
2. php version 7.2

Actual result

Finally it's resolved.
I fixed it by running composer install by deleting vendor folder and then remove the cache files using rm -fr bootstrap/cache/*.


Laraval 5.1 verseion

First very nice project!
Second is there any plan / timeframe / roadmap for a Laravel 5.1 version of Bumble?

Thank you! There should be a 5.1-compatible version in the next few days. :-)


enable development on macOS

Resolves https://github.com/HakCat-Tech/USB-Nugget/issues/71
This PR enables developers running macOS to build and flash the code to the USBNugget devkit.
Developer documentation has been moved to src/README.md because it's not necessary for those just looking to flash the latest release using the webflasher.

@angelina-tsuboi would you mind testing the following when you get a chance? During your dev setup, one step involving curl didn't work (I think you have an older version), so I've used curl flags that I'm guessing are a bit older...

clone a fresh repo, then cd into it
curl --version && cd src/ && make scripts/arduino-cli (shouldn't take long)
Paste the output here


iptables v1.8.2 (legacy): unknown option "--to-ports"

Cookbook version
[Version of the cookbook where you are encountering the issue]
I don't know what the 'cookbook' is referencing too
Chef-client version
[Version of chef-client in your environment]
iptables v1.8.2(legacy) [1:1.8.2-1 according to my pkg manager]
Platform Details
[Operating system distribution and release version. Cloud provider if running in the cloud]
ArchLinux - 5.1.7-arch1-1-ARCH
Scenario:
[What you are trying to achieve and you can't?]
NAT redirection for mitmproxy
Steps to Reproduce:
[If you are filing an issue what are the things we need to do in order to repro your problem? How are you using this cookbook or any resources it includes?]

use current version of iptables
use latest archlinx kernel (default kernel)
issue command such as: sudo iptables -t nat -A PREROUTING -i eth0 -p tcp --dport 80 -j REDIRECT --to-port 8080

Expected Result:
[What are you expecting to happen as the consequence of above reproduction steps?]
putting my computer between the router and the server to view incoming and outgoing data on my device
Actual Result:
[What actually happens after the reproduction steps? Include the error output or a link to a gist if possible.]
iptables v1.8.2 (legacy): unknown option "--to-ports"
Try `iptables -h' or 'iptables --help' for more information.
I also can't find the '--to-port' option on the man page for my version of iptables
Just in case this needs to be clarified, this happens for '--to-port' and '--to-ports'
After some googling I did stumble accross this however leading me to believe the kernel I'm running may be to blame: https://github.com/sshuttle/sshuttle/issues/286

fixed after a system update and reboot
Now @ 5.1.15-arch1-1-ARCH


Broken install

To reproduce:

From a blank repo/machine, add jshint to the Gemfile.
bundle exec jshint

Error message:
/Library/Ruby/Gems/2.0.0/gems/jshint-1.3.1/lib/jshint/configuration.rb:86:in `initialize': No such file or directory - /Users/carl/Google Drive/Documents/W2015/ECSE 428/mcbuddy/config/jshint.yml (Errno::ENOENT)
from /Library/Ruby/Gems/2.0.0/gems/jshint-1.3.1/lib/jshint/configuration.rb:86:in `open'
from /Library/Ruby/Gems/2.0.0/gems/jshint-1.3.1/lib/jshint/configuration.rb:86:in `read_config_file'
from /Library/Ruby/Gems/2.0.0/gems/jshint-1.3.1/lib/jshint/configuration.rb:90:in `parse_yaml_config'
from /Library/Ruby/Gems/2.0.0/gems/jshint-1.3.1/lib/jshint/configuration.rb:15:in `initialize'
from /Library/Ruby/Gems/2.0.0/gems/jshint-1.3.1/lib/jshint/lint.rb:20:in `new'
from /Library/Ruby/Gems/2.0.0/gems/jshint-1.3.1/lib/jshint/lint.rb:20:in `initialize'
from /Library/Ruby/Gems/2.0.0/gems/jshint-1.3.1/lib/jshint/cli.rb:4:in `new'
from /Library/Ruby/Gems/2.0.0/gems/jshint-1.3.1/lib/jshint/cli.rb:4:in `run'
from /Library/Ruby/Gems/2.0.0/gems/jshint-1.3.1/bin/jshint:12:in `<top (required)>'
from /usr/bin/jshint:23:in `load'
from /usr/bin/jshint:23:in `<main>'

Based on your error message, it appears that your missing the jshint.yml configuration file that's documented as part of the installation process.
You can run the following generator to give you this configuration file in your codebase:
bundle exec rake jshint:install_config

I did try that, but this is what happens:
wpa151018:mcbuddy carl$ bundle exec rake jshint:install_config
rake aborted!
No Rakefile found (looking for: rakefile, Rakefile, rakefile.rb, Rakefile.rb)

(See full trace by running task with --trace)
wpa151018:mcbuddy carl$ bundle exec rake jshint:install_config --trace
rake aborted!
No Rakefile found (looking for: rakefile, Rakefile, rakefile.rb, Rakefile.rb)
/Library/Ruby/Gems/2.0.0/gems/rake-10.4.2/lib/rake/application.rb:684:in `raw_load_rakefile'
/Library/Ruby/Gems/2.0.0/gems/rake-10.4.2/lib/rake/application.rb:94:in `block in load_rakefile'
/Library/Ruby/Gems/2.0.0/gems/rake-10.4.2/lib/rake/application.rb:176:in `standard_exception_handling'
/Library/Ruby/Gems/2.0.0/gems/rake-10.4.2/lib/rake/application.rb:93:in `load_rakefile'
/Library/Ruby/Gems/2.0.0/gems/rake-10.4.2/lib/rake/application.rb:77:in `block in run'
/Library/Ruby/Gems/2.0.0/gems/rake-10.4.2/lib/rake/application.rb:176:in `standard_exception_handling'
/Library/Ruby/Gems/2.0.0/gems/rake-10.4.2/lib/rake/application.rb:75:in `run'
/Library/Ruby/Gems/2.0.0/gems/rake-10.4.2/bin/rake:33:in `<top (required)>'
/usr/bin/rake:23:in `load'
/usr/bin/rake:23:in `<main>'

Hi @lilred,
It sounds like your missing a Rakefile from the root of your Rails project, it should contain the following:
# Add your own tasks in files placed in lib/tasks ending in .rake,
# for example lib/tasks/capistrano.rake, and they will automatically be available to Rake.

require File.expand_path('../config/application', __FILE__)

Rails.application.load_tasks

Thanks for the update. I guess the issue is that the Rakefile doesn't get created+updated if it doesn't already exist.

That's correct. When you scaffold a new Rails project it generates a Rakefile for you, along with a bunch of other files / directories e.g.
Gemfile      README.rdoc  app          config       db           log          test         vendor
Gemfile.lock Rakefile     bin          config.ru    lib          public       tmp

So what if I want to use this in a non-Rails project :o

At present I'd hazard a guess that this gem isn't compatible with a non-Rails project. But I don't think it'd take too much work / refactoring to loosen this coupling so that it could be less Rails agnostic.
I've made a separate issue to loosen this dependency based on your feedback, as this is something that I'd like to see. If your able to chime in on that, with some requirements / thoughts that'd be great.

I added the Rakefile you provided and it worked fine for a non-Rails project.

Hehe happy days! :+1:


Capture cursor on preview 3d interaction

@escargot-sans-gluten I know it's not a common use case, but the behavior is weird if you hold both left and right mouse buttons.

BTW, those automated builds are wonderful. I can directly test the result before merging. :)


calling plot_weight_heatmap multiple times adds 1 to sum column of weight_table each time

hi just a minor detail, I found out that calling plot_weight_heatmap N times would increase the sum column by N times. For example running in jupyter notebook:
weight_table = generate_weights_table(network, dataloader_test, device=device)

print(weight_table)

      asset_A    asset_B ... asset_Z
day_1   0.54       0.21   ...  0.002
day_2   0.45       0.32   ...  0.01

plot_weight_heatmap(weight_table, add_sum_column=True, time_format=None, time_skips=None)

print(weight_table)

      asset_A    asset_B ... asset_Z *sum*
day_1   0.54       0.21   ...  0.002  1.0
day_2   0.45       0.32   ...  0.010  1.0

# calling plot_weight_heatmap() again

plot_weight_heatmap(weight_table, add_sum_column=True, time_format=None, time_skips=None)

# printing weight_table again

print(weight_table)

      asset_A    asset_B ... asset_Z *sum*
day_1   0.54       0.21   ...  0.002  2.0   <--- I think this behaviour was not intended
day_2   0.45       0.32   ...  0.010  2.0

Very nice find! This is a bug! Really appreciate all this help and questions!:)


No didClose/didOpen event when rename Java file to different cases

When renaming a Java file in file explorer, if old file name is App.java and new name is App1.java, Java language server will receive textDocument/didClose for old uri, then textDocument/didOpen for new uri, which is what we expected.
However, if we try to rename App.java to ApP.java, these two events will not be triggered, which may cause problems when Java language server try to update Java model.
Environment

VSCode Version: 1.50.1
OS Version: Windows 10
JDK version: 11
Language Support for Java version: 0.69.0

Steps to Reproduce:
1.Rename Java filename to different cases in file explorer (e.g App->ApP, ApP->App...)
2.Monitor Java language server's output and search for corresponding events, no search result found
3.Try other filename (e.g. App->App1), events triggered correctly.
Current Result:
No didClose/didOpen events in language server output

Expected Result:
Like rename file to a different name (App.java->App1.java), two events are triggered

Forwarding to @jrieken and @bpasero since this comes from the WorkginFilesService if I am not mistaken

You have to use vscode.workspace.onDidRenameFiles API to detect that a rename happened. Looking for text document events does not work. We have no way of renaming the URI of a text model unless you close all editors and restart. This is a consequence of introducing canonical URIs to fix https://github.com/microsoft/vscode/issues/12448
We will not go back because even though the current solution has its own set of issues, the other one was worse imho.


Update API for Enums{EMode, EInterpolationType}

Seems like due to updates to the FBX (Python) SDK, the API has changed and causes segmentation fault errors
Changes were made for the Enums according to the docs here
Tested using the following versions:
Package    Version
---------- --------
Python     3.10.11
fbx SDK    2020.3.4
numpy      1.25.0
packaging  23.1
pip        23.1.2
ply        3.11
scipy      1.10.1
setuptools 68.0.0
sip        6.6.2
toml       0.10.2
tqdm       4.65.0
wheel      0.38.4

May I know what version of FBX Python SDK you're using? I use 2020.0.1 with python 3.7 and do not have segmentation fault.

I use the latest version  2020.3.4 from the AutoDesk website - "Get FBX SDK" which directs to the latest version.

May I know what version of FBX Python SDK you're using and where to download it? I use 2020.0.1 downloaded from here: https://www.autodesk.com/developer-network/platform-technologies/fbx-sdk-2020-0 with python 3.7 and do not have segmentation fault.

In the version of FBX Python SDK 2020.0.1, there is only Python27 and no Python37, as you can see link. However, if I use FBX Python SDK 2020.3.4 + Python37, segmentation fault errors will occur. What should I do?

I use the latest version FBX Python SDK 2020.3.4 from the AutoDesk website - "Get FBX SDK" which directs to the latest version.

Excuse me, I would like to ask how you solved this problem？


Use labels to restrict pod to nodes

Is there any quick way to create a clickhouse installation where the clickhouse pods are restricted to particular nodes based on labels?  I'd like to setup an EKS cluster with a nodegroup for clickhouse and another nodegroup for zookeeper and use labels to allocate the pods to the appropriate nodes, but I can't find any documentation about how to set this up.
Here's the relevant portions of my current manifest:
kind: "ClickHouseInstallation"
metadata:
  name: "the-cluster-installation"
spec:
  configuration:
    clusters:
      - name: "main"
        layout:
          shards:
            - replicas:
              - templates:
                  podTemplate: clickhouse-az1
              - templates:
                  podTemplate: clickhouse-az2
            - replicas:
              - templates:
                  podTemplate: clickhouse-az1
              - templates:
                  podTemplate: clickhouse-az2
            - replicas:
              - templates:
                  podTemplate: clickhouse-az1
              - templates:
                  podTemplate: clickhouse-az2

  templates:
    podTemplates:
      - name: clickhouse-az1
        zone:
          values:
            - "us-west-2a"
        podDistribution:
          - type: ClickHouseAntiAffinity
      - name: clickhouse-az2
        zone:
          values:
            - "us-west-2b"
        podDistribution:
          - type: ClickHouseAntiAffinity
      - name: clickhouse-az3
        zone:
          values:
            - "us-west-2c"
        podDistribution:
          - type: ClickHouseAntiAffinity

@fiddlerwoaroof , this looks correct. You may use full affinity/anti-affinity syntax in order to attach pod to the nodegroup:
    podTemplates:
      - name: clickhouse-az1
        spec:
          affinity:
            nodeAffinity:
              requiredDuringSchedulingIgnoredDuringExecution:
                nodeSelectorTerms:
                  - matchExpressions:
                      - key: "eks.amazonaws.com/nodegroup"
                        operator: In
                        values:
                          - "my-NG"
                      - key: "failure-domain.beta.kubernetes.io/zone"
                        operator: In
                        values:
                          - "us-west-2a"

Another way is to use nodeSelector.
    podTemplates:
      - name: clickhouse-az1
         spec:
          nodeSelector:
            failure-domain.beta.kubernetes.io/zone: "us-west-2a"


Faulty alignment in plugin.StandardMessageCodec

Hello I am trying to port the audioplayers plugin to go-flutter and have been facing some problems that I can no longer solve alone.
When I call the play method on the plugin, I receive the following error:
go-flutter: handling message on channel xyz.luan/audioplayers failed: failed to decode incomming message: failed decoding method arguments: invalid message value type

I have tried looking into go-flutter source code, and it looks like some arguments that are sent from the dart is breaking the conversion function of go-flutter. That is my guess, but I am a total novice on Go so I may be very much wrong.
Flutter version
Flutter 1.6.7 • channel dev • https://github.com/flutter/flutter.git
Framework • revision cba41ca2ec (5 days ago) • 2019-05-30 12:04:01 -0700
Engine • revision 58eff77ef2
Tools • Dart 2.3.2 (build 2.3.2-dev.0.0 fee615c5a5)

Steps to Reproduce
I have committed the things I did so far:
This is our example app of the audioplayers plugin with the go-flutter already inited by hover: https://github.com/luanpotter/audioplayers/tree/go-flutter-desktop
Here is my fork of the plugins repository with the initial implementation of the audioplayers in go: https://github.com/erickzanardo/plugins/tree/audioplayers (so far it is just a bunch of printf calls and some tests with audio libs in go)
Just running the example app of the audioplayers repository and hitting play on any of the test players makes the error happen.
Thanks a lot for your time.

From what I can tell, the volume value from the map is causing the standard-message-codec to fail.
When debugging, I found out that the readFloat64 method was the one causing the misinterpretation of the platform message.
When reading/writing a Float value, the flutter putFloat64 dart code is prefixing multiple alignment bytes.
The number of alignment bytes seems to be miss calculated. I can't tell by who and why!
The number of alignment bytes calculated by  go-flutter seems to be miss by 2 bytes.

Again, why????
flutter-rs is doing it.
Android shell is doing it.
FDE MacOS is doing it.
FDE Linux/Windows is doing it.

Here is a visual:

I've put a ?bugfix? in a new branch bugfix/standart-message-codec, this skips 2 more bytes before reading the Float64.
You can test it by running:
hover run -b '@bugfix/standart-message-codec'

This will allow you to carry on the plugin development.
BTW:  It's fantastic to see work happening in the porting existing plugins. Also, it's even more fantastic to have feedback. Thanks. :1st_place_medal:

Thanks for the quick response @Drakirus , I will test this tonight and report back here :)

@GeertJohan Adding the buff.Next(2) breaks the unit test. We will need your help on this one.

@Drakirus just reporting back, the branch you asked me to use work like a charm! thanks

Auch, thats odd! I have scheduled some time to take a proper look at this bug next monday.
And @erickzanardo, really awesome to see go-flutter plugins come to life! :rocket:

Thanks for sharing all this information and a working example. It helped me to identify the issue really fast.
You see, the problem is not directly with standard message codec, it works fine on it's own and the unit tests are happy. The problem is introduced when using the message codec from the standard method codec.
The standard method is a bit strange, it encodes a string as method name, directly followed by a single arguments value. The arguments value is a single value but it may be a string, int, float (etc) or a complex type such as a list or map, which allows passing "multiple arguments".
So, the method call data structure is as follows:
<methodName><arguments>
It is decoded by two separate calls to the standard message codec. First call to decode the methodName string from the buffer. Then a second call to decode the arguments value.
You probably see where this is going...
When decoding the arguments, the standard message codec has no knowledge of any values preceding the arguments in the buffer, which were decoded in the first call. So if a methodName of length != 8 is used, there is an offset that isn't properly compensated for.
I'm now working on a fix :)

I've created a PR that includes proper unit tests for this situation: Simple unit test with several scenario's and a unit text containing a replica of the MethodCall that this issue was opened for. The PR also fixes the issue. ;)

The fixe made by @GeertJohan solves the bug, the branch @bugfix/standart-message-codec is deleted.
The tag: v0.19.0 is includes the fix.

Thanks for the quick fix!


Adapters

Adds some additional adapter components for ion channels, as well as documentation.

@VahidGh If you can give my code a quick look-over and merge it I'd greatly appreciate it!
We can then make a PR from dev to master :)

@travs, looks great. We could also add those tests, and the intention to the doc related to testing workflow.


Add option to show the reference docs in the monaco editor

Add an option in the context menu to load the reference docs of a specific highlighted function or namespace in the side bar.

Isn't that what the "Help" menu option does?
Get Outlook for iOShttps://aka.ms/o0ukef

From: Sam El-Husseini<EMAIL_ADDRESS>Sent: Tuesday, November 22, 2016 9:51:47 AM
To: Microsoft/pxt
Subject: [Microsoft/pxt] Add option to show the reference docs in the monaco editor (#799)
Add an option in the context menu to load the reference docs of a specific highlighted function or namespace in the side bar.

You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoft%2Fpxt%2Fissues%2F799&data=02|01|jhalleux%40microsoft.com|0bd1557be60f4360d56008d413003c41|72f988bf86f141af91ab2d7cd011db47|1|0|636154339114516884&sdata=zXI4JSGVTKlSI0NnoTJtu9j8S35znIf1Z6J%2F6sPMbJQ%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAD-4KYb8HZYB2LyBKlLxs7hVcS87yo4uks5rAyuzgaJpZM4K5voI&data=02|01|jhalleux%40microsoft.com|0bd1557be60f4360d56008d413003c41|72f988bf86f141af91ab2d7cd011db47|1|0|636154339114516884&sdata=sizdBsrJAfqaA%2B%2BuVlNM1DHKcWnCZn5onUmJEYQG%2FCE%3D&reserved=0.


regex for checking output path correctness

Bug report

What is the current behavior?
I'm using upath to work with path'es, so it converts all the windows style slashes "\" to the "/", the schema check for the configuration.output.path however fails, saying that provided path is not correct i.e. if i provide path like "C:/my/awesome/project" it says "the provided path is not absolute path"
If the current behavior is a bug, please provide the steps to reproduce.
I am not sure if this behavior can be reproducible on windows only, but as i mentioned above you can just put an absolute path with "/" slashes as an output path. The rest of config does not matter i believe.
I found that the "validness" of the path is checked via regex in schemas/ajv.absolutePath.js, this regex fails to match absolute path with "/" slashes for me, if i trying to test it via regex101.com. I believe it should be smth like ^(?:[A-Za-z]:[\\|\/]). If this is a bug, i would be happy to make a pr.

What is the expected behavior?
It should accept path with "/" slashes on windows

Other relevant information:
webpack version:  4.16.1
Node.js version: 8.11.2
Operating System: Windows 10
Additional tools: i'm using conemu but checked the regex via regex101.com

Out of curiosity, i checked how it works from the WLS, and it works without error as expected, so i think this problem occurs only on windows.


Change default labels layer to int16.

Description
This PR changes default type for labels created with new labels button to int16.
Currently, it is int that defaults to int64 on lLnux and MacOs and int32 on Windows.
During development of #6467 I have found that defaulting to int may create some performance problems. Because of this, I suggest this change.
This change still allows to use of negative values (maybe it is not important and we should default to uint16).
This change reduces memory usage by half on Windows and four times on Linux and MacOS.

Fast check do not show part of docs that needs to be updated, but maybe I miss something.

@Czaki while thinking about this I had the following idea: when people make a new layers label in this way, it is typically to paint labels, and usually that means very small values. They could almost always fit in uint8. So my suggestion is:

we change to uint8 by default
we only update the dtype when the user selects a negative label or a larger-than-dtype label in the selection box. (Potentially, we can display a warning when that happens.)

Ultimately, I am very supportive of this change. We've seen some very significant performance issues with higher dtypes, and the choice to use int dates back to a time when users didn't have a quick way to change the data type of a layer. Now, it is just a right-click away, so I think we should use a small dtype to begin with and expand just-in-time.

But we could just update the documentation to highlight right click menu?

You mean this?
https://napari.org/dev/tutorials/fundamentals/viewer.html#right-click-menu
(note I just noticed the fix to the Change dtype got over-written by my other merge. I've made a PR)
Maybe worth mentioning dtype here too https://napari.org/dev/howtos/layers/labels.html

You mean this?

yes. To increase visibility

The button uses this method afaik:

I even modify it here.
The question is how to distinguish such created label and suggest change type, and labels added in different ways to not suggest then.

Sorry, answered quickly without reading further. You could use the layer source? I don't know if we have a "button" source specifically, but any plugin-created layer should have a different source.

Yeah, source is a good idea! (I was going to suggest unstructured metadata but source is so much better! 😂)

After rethink and check the code. Did we should do both changes in one PR?
We currently set limits of label selectors based on data type. The PR for proper handling conversion will not be small.
Maybe we could just make a small PR to reduce the default type, to be cherry-picked to 0.4.19, and make a separate PR with a convert suggestion somehow later?

THe Source is defined here:
https://github.com/napari/napari/blob/dbafdd08e0202bf78fcec9dcc73ead6742a2cf39/napari/layers/_source.py#L14-L36
I do not see a proper field to use. And do not know how to name new generic field.

Yeah I'm happy to do two (or more) different PRs. But then I would do the following PRs:

change default to uint8 (this one)
warn when trying to change selected label to out-of-range value, and warning points out how to convert layer dtype using right-click
run the dtype change automatically. (another idea: this could happen on the second click, after the warning)
right click on the new labels button has menu to select new labels dtype

Ok. I have updated dtype to uint8. I have also fixed bug in Qt layer controls to update the range of label selectors with and add a test for such a scenario.

I have created #6479 which should be merged before this.

I have created #6479 which should be merged before this.

I think you can do Depends on #6479 in the OP? Or does that only work in the docs repo

I think you can do Depends on #6479 in the OP? Or does that only work in the docs repo

It works only in docs repo, we may think to add it the main repo also

I think it makes sense if we want big PRs broken down into smaller chunks. Makes the dependency of them easier.

Ok, #6479 has now been merged so I've merged in main and added the ready-to-merge label here. Since this has already been sitting for a while I suggest that it can be merged as soon as all the checks are green. Thanks @Czaki!


Nested object structure in loops

<!-- BEGIN object.property -->

Forgot that this issue was open, closed earlier.


As a CIF user, I want the statuses displayed in the task list to be clear, so that I can see the state of the project at a glance

Description:
The TaskList component has received some design upgrades. Suha has provided a great description in figma of what should be shown when.
https://www.figma.com/file/PzOY8RyQnVXnjZJdSv2AqQ/Wireframing_Figma?node-id=1415%3A2663
Note:
The overall statuses displayed in the TaskList component will need a new computed_column (or maybe a few?) on project_revision that calculates and returns the overall status. We can't have form_change fragments in the TaskList or else we end up with an adjacency issue and overwriting data in the relay store.
Something like project_revision_overall_report_status(cif.project_revision, report_type) for reports that would return on_track, late, etc when in view/edit mode.
In create mode, we may also need another computed column like project_revision_overall_form_completion_status(cif.project_revison, record_type). Records that we're currently handling with their own special computed columns (Milestones, Managers) may need their own computed column again here.
Acceptance Criteria:
See figma
https://www.figma.com/file/PzOY8RyQnVXnjZJdSv2AqQ/Wireframing_Figma?node-id=1415%3A2663
Development Checklist:

[ ] All items in figma wireframe are complete
[ ] Meets the DOD

Definition of Ready (Note: If any of these points are not applicable, mark N/A)

[ ] User story is included
[ ] User role and type are identified
[ ] Acceptance criteria are included
[ ] Wireframes are included (if required)
[ ] Design / Solution is accepted by Product Owner
[ ] Dependencies are identified (technical, business, regulatory/policy)
[ ] Story has been estimated (under 13 pts)

·Definition of Done (Note: If any of these points are not applicable, mark N/A)

[ ] Acceptance criteria are tested by the CI pipeline
[ ] UI meets accessibility requirements
[ ] Configuration changes are documented, documentation and designs are updated
[ ] Passes code peer-review
[ ] Passes QA of Acceptance Criteria with verification in Dev and Test
[ ] Ticket is ready to be merged to main branch
[ ] Can be demoed in Sprint Review
[ ] Bugs or future work cards are identified and created
[ ] Reviewed and approved by Product Owner

Notes:

Hey team! Please add your planning poker estimate with ZenHub @BCerki @dleard @gurjmatharu @mikevespi @Sepehr-Sobhani

We would also need to support extra filters in project_revision_overall_report_status(cif.project_revision, report_type, **filters) to be able to differentiate quarterly, annual reports, milestones, ...

Based on CIF prioritization session on Aug 16, 2022, this ticket needs further review. Low priority for the program area.

Removing from CIF Project Lists Enhancements due to priority.


Poll: Any need to disable certain keywords?

Do you need to selectively disable certain keywords?
An API such as this:
engine.disable_keywords(&[ "while", "break", "return" ]);

disables the while, break and return keywords.  Essentially, these texts will not be recognized as keywords at all, but will be parsed as variable. The net result is surgically disabling certain types of statements.
So bam, no more while loops, and no breaking out/returning from blocks.

Closing this as there doesn't seem to be interest.


[BUG]There are no options in the model names in all models, and they are not allowed to be entered.

Describe the bug
In the latest version of the model, there is no option in the model name, and it is not allowed to be entered.

it's the same for me when using OpenAI

oh strange, in the latest version we pull the model list from this file here
There might be some issues to access the file, can you try deleting the old node, and create from scratch? If not you can create a models.json file and specify the env variable - https://docs.flowiseai.com/configuration/environment-variables#models

also please share how are you running Flowise. There might be company proxy that blocks the access to fetch the file from Github

In order to test, I reinstalled the win11 system and all related environments, but the situation is still the same. This is a locally running program and should not be associated with the network. In particular this should be designed as a local configuration file. I strongly hope this bug can be resolved soon.

I changed the proxy and tested it, and the options can be displayed. But the previous version did not have this problem. It's hard for me to understand why this parameter should be designed to be so closely related to the network? If so, using flowise will be very limited.

I changed the proxy and tested it, and the options can be displayed. But the previous version did not have this problem. It's hard for me to understand why this parameter should be designed to be so closely related to the network? If so, using flowise will be very limited.
Hello, I'm having the same problem, how did you modify the proxy?

created a PR now to fallback to fetch the local models.json file if the link is not accessible - https://github.com/FlowiseAI/FlowiseCloud/pull/397


Implements async functions

Coverage remained the same at 100.0% when pulling 559de6f91d4672b73fc7af0d19f57c3e42342d98 on Team1772:async-await into 80646c3dd2f0b0b1d860a97aa1eac406e5da7704 on 4alltecnologia:async-await.


[Spell Suggestion] Hex Hand

Inspiration.
A spell of the form entity, location ->  that does two things (in order of priority):

If entity is an item stack and location is an inventory, insert item stack into inventory.
Right-click location with item. If item is NULL, right click with empty hand.

As per the inspiration spell from D&D, it costs a negligible amount of media (original spell is level 0), and the item entity must be within 10 blocks of whatever it is applied to.
Some applications for this:

Item-sorting spell circles.
Crop farming/replanting spell circles.
Remotely activate contraptions using a sentinel.

Happy to implement this and submit a PR!

Sort of implemented by Hexal's mote spells - not sure if this needs to be in base Hex.


[Q2] Regl + WebGL vs. SVG Transform Layer

Context:
https://docs.google.com/document/d/1URHq2EQ94BRrtnfKklUhl_mcPmVvPpkYpjIKewaIBPY/edit?disco=AAABFWOprjk
We want to compare PoC Emanuele's regl + webGL vs. the existing SVG transform layer and see which one will perform better with tiling in Q2
DoD:

Come up with a recommendation after the spike

Might not be needed if Openseadragon will handle the image layer

No longer needed, since we use OSD!


luarocks install loadcaffe

jishan@jishan-B85M-HD3:~/torch$ luarocks install loadcaffe
Warning: Failed searching manifest: Failed fetching manifest for https://raw.githubusercontent.com/torch/rocks/master - Failed downloading https://raw.githubusercontent.com/torch/rocks/master/manifest - /home/jishan/.cache/luarocks/https___raw.githubusercontent.com_torch_rocks_master/manifest
Warning: Failed searching manifest: Failed fetching manifest for https://raw.githubusercontent.com/rocks-moonscript-org/moonrocks-mirror/master - Failed downloading https://raw.githubusercontent.com/rocks-moonscript-org/moonrocks-mirror/master/manifest - /home/jishan/.cache/luarocks/https___raw.githubusercontent.com_rocks-moonscript-org_moonrocks-mirror_master/manifest
I already install torch in ubuntu. How can i fix this problem..?please help

Hello ,
This is related to  download package since  your getting  "Failed downloading ".
I also face this problem , after that I have modified my firewall setting . than I can able to install loafcaffe with out any error.

Hello ,
This is related to download package since your getting "Failed downloading ".
I also face this problem , after that I have modified my firewall setting . than I can able to install loafcaffe with out any error.


Create quality check spec for leftover debugging/development mechanisms

Example mechanisms that are screened for:

sleep

binding.pry

debugger

focused rspec tests via fit

Related to discussion at https://github.com/bundler/bundler/pull/4439#issuecomment-210091297

Good call. Broke it into a more readable multi-line regex.

@homu r+

:pushpin: Commit d1eafee has been approved by segiddins

:hourglass: Testing commit d1eafee with merge e167039...

Fixed the formatting rubocop error and re-ran the flaky Travis build job.

@homu r+

:pushpin: Commit c359410 has been approved by segiddins

:zap: Test exempted - status


Support ARM64EC on Windows

Arm64EC is a new arm64 calling convention in Windows 11 to make mixing x64 and arm64 code easier. Theoretically, this should just be as easy as adding a new configuration copying the existing arm64 windows configuration. I'm working on testing this now, and if it works I'll PR it.
This should be looked at as a candidate to backport to 1.1.1. Similar to the arm64 osx discussion, it requires no code changes, just a configuration change.

OpenSSL has a lot of assembly code, which is written to the standard AAPCS64 calling convention. How does this new calling convention interact those? Do assembly function prototypes need to be marked so that ARM64EC -> AAPCS64 transitions work correctly? Is there any documentation on what exactly the ARM64EC calling convention is (which arguments in which registers, etc.)?

Based on what I was looking at, it doesn't actually look like the windows targets in Openssl currently use any of the arm64 assembly code.
As for the ABI itself, I'll try to see if I can find some external documentation. But generally, its designed to be a 1 to 1 mapping matching the x64 ABI.

Based on what I was looking at, it doesn't actually look like the windows targets in Openssl currently use any of the arm64 assembly code.

I don't believe that's true in OpenSSL 3.0. Though, sure, one could always say ARM64EC does not get the benefit of assembly optimizations, due to its non-standard calling convention. Short work like something below, that's probably the most practical answer.

But generally, its designed to be a 1 to 1 mapping matching the x64 ABI.

Right, I've seen that before, but that doesn't describe a calling convention. It's just a vague description of the design goals. Documentation should tell you exactly which registers are used where, etc., otherwise no one can write code to that calling convention.
Although, to avoid imposing unreasonable costs on the rest of the ecosystem (supporting two calling conventions in one assembly file is a significant maintenance burden), I would encourage you all to make ARM64EC -> AAPCS64 calls work. Assembly functions are typically internal to a library, rather than exposed directly. That means, you don't need to worry about calls from emulated-x64, only ARM64EC. With suitable attributes in your compiler, you could have assembly functions stick to the standard calling convention, and then the non-standard callers can bridge that accordingly.

I'm not part of the compiler team at all. I just work on our QUIC library, and am trying to get it to build for arm64ec. I can attempt to pass that information off to the right compiler teams however.

Marking as inactive, to be closed at the end of 3.4 dev, barring further input

Is this issue resolved? Do we have support for ARM64EC platform ?

I would love some support on this as well

I can compile openssl v3.4.0 to ARM64EC successfully with the configuration 'no-asm'. But I think it will impact the openssl performance obviously. Hope can support ARM64EC officially with assembly code enabled.
Here has the detailed information about calling convention of ARM64EC:
https://learn.microsoft.com/en-us/windows/arm/arm64ec-abi


Use watchdog for a more robust file watching for mesop/bin

Closes #150.
Note: this doesn't work with Python relative imports which seems relatively less popular than Python absolute imports.

Thanks for the review


running on MacOS-M2 GPUs

Hi
Is it possible to run Aria on Mac-M2 GPUs?

@atanudasgupta Due to lack of a Mac-M2 machine, we are not sure it will fit in that kind of chip. Theoretically, it takes around 50 GB of vRAM to load a whole Aria model into it. If you have any experience of how to run Aria on M2, we are glad to have it and discuss with you.

Hi
Is it possible to run Aria on Mac-M2 GPUs?

Waiting for this great developer's adaptation
https://github.com/Blaizzy/mlx-vlm/issues/39


Default width error

@AhmedLSayed9 Hello, I have a small question/remark. If you do not set the width of the button and dropdownlist, then the width of the button is taken as the maximum width of the child element from the list (correct me if I'm wrong). But at the same time, the dropdownlist has some paddings or margins (I did not find their variables) that are not added to this width.
As a result, it turns out that this element does not completely fit into the dropdown and is cut off. If the list of items is static, then this is easily solved by setting specific sizes, but if the list for the dropdown comes from the server and can change, then a problem appears.

Hello ihorkozar,
That's right. If you don't set buttonWidth or dropdownWidth, then the width of the button & menu is taken as the maximum width of the child element from the list or the hint text.
The padding that your dropdownlist has is the itemPadding which by default is _kMenuItemPadding = EdgeInsets.symmetric(horizontal: 16.0) if you didn't use the itemPadding parameter.
To make your dropdownlist's width dynamic and your elements fit into the dropdown, use itemPadding: EdgeInsets.zero.
In this case, To add padding to your elements wrap your Text widget that you pass to items parameter with padding. I think this will solve your issue.

@AhmedLSayed9 Thanks, your advice helped a lot.
It may be worth passing these additional indents immediately in the library, this would be a good default solution.

The problem is if we add padding to the width immediately in the library, then static width won't be accurate. I'll try to find if we could make it work without changing static width


expose ports_map

useful for components with electrical ports you might want to expose

LGTM,
i just fixed the tests by running pytest --force-regen -s --lf


Change order of processing in fit model to fail earlier with bad design

Currently a fair amount of signal processing happens before building the design matrix, with the consequence that crashes related to the design (which are not uncommon) take a while to happen, wasting time.

Closed by #175


[Amazon AWS] ... Add Support for MFA profiles

Extension
https://www.raycast.com/Falcon/aws
Description
Accessing AWS resources via the Raycast API is fantastic. However, for multi-user or role-based accounts, it is often the case that an MFA step is required. Would it be possible to add MFA validation to this extension?
Who will benefit from this feature?
Anyone using this extension who needs to use MFA to access their account.
Anything else?
No response

@zachcp I have been trying to do this for a while (and spent many hours on it). I do think it's possible, but it isn't trivial. I haven't given up on it, though.
relates to #3022


Proxy option

With combination Nette + Docker + Webpack I need to tell browser for a different assets URL. I added a proxy URL setting.

Hello, thanks for your contribution, but I'm confused about it. Why can't you just change the devServer.url? Introducing another config option, especially in this way, seems a bit redundant 🤔

We can't just change devServer.url, because then Nette wouldn't see webpack-dev-server. We need to make webpack-dev-server accessible from two different locations/urls.

Ah, now I understand, thanks! I've left a few review comments, so if you could please take a look at them and rebase the branch, and then I believe it's good to go.


Collab fixes.

Here will be fixes for current collab protocol.

Codecov Report

Merging #1104 into develop will not change coverage.
The diff coverage is 0%.

@@           Coverage Diff            @@
##           develop    #1104   +/-   ##
========================================
  Coverage    60.96%   60.96%
========================================
  Files          372      372
  Lines        13666    13666
========================================
  Hits          8331     8331
  Misses        5335     5335

Impacted Files
Coverage Δ

collab/CollabSession.js
0% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

@oliver---- pls review one line

Will do

Looks like it was a regression. 👍


alternative way to install on mac

As the homebrew is providing a formula not overwriting Mac OS default library, I thinks this method should be more effortless to install :)

Current coverage is 75.25% (diff: 100%)

Merging #8 into master will not change coverage

@@             master         #8   diff @@
==========================================
  Files            22         22
  Lines          2890       2890
  Methods         110        110
  Messages          0          0
  Branches        535        535
==========================================
  Hits           2175       2175
  Misses          363        363
  Partials        352        352

Powered by Codecov. Last update cf784a2...08ac3d9

My knowledge of Mac OS X and brew is superficial at best, so thank you for your help. I tested it manually, and you were right, it's much painless to install this way. I've got some ongoing development, but I'll merge your pull request as soon as possible.


services homeassistant.stop and homeassistant.restart don't work anymore

Make sure you are running the latest version of Home Assistant before reporting an issue.
You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum:
Home Assistant release (hass --version):
0.29.0.dev0 (latest github pull as of today)
Python release (python3 --version):
Python 3.4.3
Component/platform:
Homeassistant (services)
Description of problem:
Calling the services homeassistant.stop or homeassistant.restart from the ui services "tab" do not stop / restart home assistant.
I see for example the following being logged in the console:
INFO:homeassistant.core:Bus:Handling <Event call_service[L]: domain=homeassistant, service_call_id=64192720-10, service_data=description=, fields=, service=stop>
INFO:homeassistant.core:Bus:Handling <Event service_executed[L]: service_call_id=64192720-10>

but there is no indication it stopping or restarting it just keeps running, it doesn't hang either, it's just as if it never acts on it.
Expected:
that it stops / restarts
Problem-relevant configuration.yaml entries and steps to reproduce:

goto the service "tab"
click on homeassistant.stop
click on call service

Traceback (if applicable):

Additional info:
i asked on gitter for someone else besides me to test (Lewis Juggins @lwis) and he had the same problem.

May be related - I am no longer able to properly shutdown HA running the dev branch, and I have to kill -9 the process (SIGTERM is not sufficient).  Running Python 3.4.5 and dev branch - been seeing this since after the 0.28.2 release.  Nothing in the log files for me at info level, have not yet collected debug logs.

Oh good, it's not just me.
When I run "sudo systemctl status home-assistant@scott -l" I get:
Sep 23 13:34:24 debian systemd[1]: Stopping Home Assistant...
Sep 23 13:34:29 debian hass[1378]: Config directory: /home/scott/.homeassistant
Sep 23 13:36:07 debian systemd[1]<EMAIL_ADDRESS>stop-sigterm timed out. Skipping SIGKILL.
scott@debian:~$ sudo systemctl status home-assistant@scott -l
●<EMAIL_ADDRESS>- Home Assistant
   Loaded: loaded<EMAIL_ADDRESS>enabled)
   Active: deactivating (stop-sigterm) since Fri 2016-09-23 13:38:24 EDT; 4s ago
 Main PID: 1748 (hass)
   CGroup<EMAIL_ADDRESS>           ├─ 461 /usr/bin/python3 /usr/local/bin/hass
           ├─1078 /usr/bin/python3 /usr/local/bin/hass
           ├─1378 /usr/bin/python3 /usr/local/bin/hass
           └─1748 /usr/bin/python3 /usr/local/bin/hass

Same here running dev head@1b9d867

I have this same issue running the latest dev docker image.

Same issue here (running latest dev from git).

@bbangert Related issue to async and/or #3453?

Having this issue for the first time on the latest release version 29.0.  Prior to that, restart would work but then disappear from the dev services page unless manually refreshed.  Once refreshed though, the service would still work properly from the GUI.  Now it doesn't work at all.

Could this be related to #3572? I was also having trouble using systemd to stop and using SIGINT instead fixed my issue. It didn't fix my issue with homeassistant/restart & stop

Fixed for me by #3690 on 0.29.7


gofabric8 pull not working

Using 0.4.1:
If I try and pull docker images as below, I get no progress bars and an immediate return without actually downloading anything:
[vagrant@vagrant ~]$ gofabric8 pull cd-pipeline logging

Downloading docker images for template cd-pipeline
Download Docker images........................................................✔
Downloading docker images for template logging
Download Docker images........................................................✔

Fixed in 0.4.2 - releasing now.


Bump SBT version to 1.2.7

SBT 1.2.7 fixes the issue where Javadocs do not generate correctly in Java 9+

DAFFODIL-2002

So we have a few things that are annoying given the proliferation of projects. One is this number, the other is the scala compiler version number. These need to be centralized, or mostly so. Can one just set this in one place?

Do you mean how all the different DFDL schemas also need to include an sbt and scala version number? I don't think there is a great way around that. The sbt version number definiately can't be centralized, since the build.properties file has a very simple format and is parsed very earily in the sbt startup process.
The scala version can be a little more dynamic, but I don't think there is a way to query the scala version that Daffodil uses. The best we could probably do is create an SBT plugin that the DFDL Schema projects use, and that plugin could be manually updated to match the Daffodil version. Then it just becomes a matter of updating that plugin. But that's kindof odd behavior for a plugin. It doesn't really do anything, just sets a bunch of default parameters. And it still requires people to update the plugin version to get the new settings. So still a somewhat manual process.
I'm not sure there's a great solution to that problem. When probably just need to remember to update scala and sbt versions when we update the daffodil dependency.


Format for title field

Most often, people will have this as title tag: [Value] - [Brand Name] or [Brand Name] - [Value].
While this is possible to achieve in the current build, it must be done through code. Ideally we provide the ability to change the format with 'magic' strings included. So something like: '%Value% - [Brand Name]' would then use the value gathered from the settings. If format is not provided, we'll just expect it to be '%Value%'

Until this is supported with the proposed formatting in the title tag, this could be handled by the Notifications if they passed along the IPublishedContent as a property - this way it would be possible to fetch the root and then just get the name from there to prefix or suffix the generated title.
Alternatively the AfterMetaTagsNotification could pass along all the title fields with the resolved values, eg:

Would give us the values of both the Page Name and the Inherited Value; this way we could string those values together ourselfs, $"{pageName} - {inheritedValue}" or $"{notification.MetaTags.Title} - {inheritedValue}".
In my example the inherited value is the title of the front page, which is want we want to display on all pages as a suffix.


Wrong target framework for current build?

Hi,
We would like to use your SDK in our project which targets the .NET 4.5.0 framework. According to your specification the SDK should be compatible and thus can be added via Nuget. However, when building the project Visual Studio reports that the SDK is build against .NET 4.5.2 and thus not compatible:

The primary reference "OneSignal.CSharp.SDK, Version=<IP_ADDRESS>, Culture=neutral, processorArchitecture=MSIL" could not be resolved because it was built against the ".NETFramework,Version=v4.5.2" framework. This is a higher version than the currently targeted framework ".NETFramework,Version=v4.5".

Would it be possible to release a version that builds against .NET 4.5.0?
Thanks

Of course, please send to us the pull request.


Can't succesfully configure action

I seem to be having issues with the action in generating a coverage report and am wondering if there are any suggestion to get it to work.
The action does successfully make a comment, but seems to fail in uploading an artifact to be used later. The "Store Pull Request comment to be posted" step does not seem to get executed.
Under Actions settings, GITHUB_TOKEN does have read/write permissions. The repo is set to private.
The error:
Run py-cov-action/python-coverage-comment-action@v3
/usr/bin/docker run --name bedb48eb8588bfd474f5aab19b4cd5187c8db_d2e0e6 --label 5bedb4 --workdir /github/workspace --rm -e "INPUT_GITHUB_TOKEN" -e "INPUT_GITHUB_PR_RUN_ID" -e "INPUT_COMMENT_TEMPLATE" -e "INPUT_COVERAGE_DATA_BRANCH" -e "INPUT_COVERAGE_PATH" -e "INPUT_COMMENT_ARTIFACT_NAME" -e "INPUT_COMMENT_FILENAME" -e "INPUT_MINIMUM_GREEN" -e "INPUT_MINIMUM_ORANGE" -e "INPUT_MERGE_COVERAGE_FILES" -e "INPUT_ANNOTATE_MISSING_LINES" -e "INPUT_ANNOTATION_TYPE" -e "INPUT_VERBOSE" -e "GITHUB_TOKEN" -e "GITHUB_PR_RUN_ID" -e "COMMENT_TEMPLATE" -e "COVERAGE_DATA_BRANCH" -e "COVERAGE_PATH" -e "COMMENT_ARTIFACT_NAME" -e "COMMENT_FILENAME" -e "MINIMUM_GREEN" -e "MINIMUM_ORANGE" -e "MERGE_COVERAGE_FILES" -e "ANNOTATE_MISSING_LINES" -e "ANNOTATION_TYPE" -e "VERBOSE" -e "HOME" -e "GITHUB_JOB" -e "GITHUB_REF" -e "GITHUB_SHA" -e "GITHUB_REPOSITORY" -e "GITHUB_REPOSITORY_OWNER" -e "GITHUB_REPOSITORY_OWNER_ID" -e "GITHUB_RUN_ID" -e "GITHUB_RUN_NUMBER" -e "GITHUB_RETENTION_DAYS" -e "GITHUB_RUN_ATTEMPT" -e "GITHUB_REPOSITORY_ID" -e "GITHUB_ACTOR_ID" -e "GITHUB_ACTOR" -e "GITHUB_TRIGGERING_ACTOR" -e "GITHUB_WORKFLOW" -e "GITHUB_HEAD_REF" -e "GITHUB_BASE_REF" -e "GITHUB_EVENT_NAME" -e "GITHUB_SERVER_URL" -e "GITHUB_API_URL" -e "GITHUB_GRAPHQL_URL" -e "GITHUB_REF_NAME" -e "GITHUB_REF_PROTECTED" -e "GITHUB_REF_TYPE" -e "GITHUB_WORKFLOW_REF" -e "GITHUB_WORKFLOW_SHA" -e "GITHUB_WORKSPACE" -e "GITHUB_ACTION" -e "GITHUB_EVENT_PATH" -e "GITHUB_ACTION_REPOSITORY" -e "GITHUB_ACTION_REF" -e "GITHUB_PATH" -e "GITHUB_ENV" -e "GITHUB_STEP_SUMMARY" -e "GITHUB_STATE" -e "GITHUB_OUTPUT" -e "RUNNER_OS" -e "RUNNER_ARCH" -e "RUNNER_NAME" -e "RUNNER_ENVIRONMENT" -e "RUNNER_TOOL_CACHE" -e "RUNNER_TEMP" -e "RUNNER_WORKSPACE" -e "ACTIONS_RUNTIME_URL" -e "ACTIONS_RUNTIME_TOKEN" -e "ACTIONS_CACHE_URL" -e GITHUB_ACTIONS=true -e CI=true -v "/var/run/docker.sock":"/var/run/docker.sock" -v "/home/runner/work/_temp/_github_home":"/github/home" -v "/home/runner/work/_temp/_github_workflow":"/github/workflow" -v "/home/runner/work/_temp/_runner_file_commands":"/github/file_commands" -v "/home/runner/work/repo_name/repo_name":"/github/workspace" *****
Notice: Starting action
Notice: Generating comment for PR
Notice: HTTP Request: GET https://api.github.com/repos/user_name/repo_name/contents/data.json?ref=python-coverage-comment-action-data "HTTP/1.1 404 Not Found"
Notice: HTTP Request: GET https://api.github.com/user "HTTP/1.1 403 Forbidden"
Notice: HTTP Request: GET https://api.github.com/repos/user_name/repo_name/issues/68/comments "HTTP/1.1 200 OK"
Notice: Adding new comment
Notice: HTTP Request: POST https://api.github.com/repos/user_name/repo_name/issues/68/comments "HTTP/1.1 201 Created"
Notice: Ending action

My workflow:
      - name: Coverage comment
        id: coverage_comment
        uses: py-cov-action/python-coverage-comment-action@v3
        with:
          GITHUB_TOKEN: ${{ github.token }}

      - name: Store Pull Request comment to be posted
        uses: actions/upload-artifact@v3
        if: steps.coverage_comment.outputs.COMMENT_FILE_WRITTEN == 'true'
        with:
          # If you use a different name, update COMMENT_ARTIFACT_NAME accordingly
          name: python-coverage-comment-action
          # If you use a different name, update COMMENT_FILENAME accordingly
          path: python-coverage-comment-action.txt

.coveragerc:
[run]
relative_files = True

The action does successfully make a comment, but seems to fail in uploading an artifact to be used later. The "Store Pull Request comment to be posted" step does not seem to get executed.

This is actually intended (in case it is not an external PR). The problem is that for a PR that is external and could therefore contain untrusted code, you don't want to combine a checkout step and the permissions needed to post a comment, for example. Therefore, it is recommended to split these two things into two workflows. But the second one is only executed when it is needed.
If someone opens a PR who has enough permissions on the repo, the comment is posted directly in the first step.
So if the action does everything it is supposed to (post comment, save coverage data, ...), then there is no problem with the workflow being skipped.

Maybe we should be clearer about that in the docs...

Thanks for the info! The other problem I had was that I was working it into an existing workflow which only ran on pull_request and not on pushes to the main branch, so there was never anything to configure. It's sorted now.


adds saga pattern, custom retry policies, defining custom errors

First draft.

In Exercise 1, I notice you have a working credit card number in the solution directory, so that technically, the end goal from Part C doesn't quite match the solution. I wound up having to do something similar in the failure converter exercise of the codecs course and wasn't happy with the way that came out, so I worked around that in this exercise by having the credit card number be a runtime argument (so that you can provide a good or a bad one without having to change the solution code). Technically I think this is OK since the failure converter exercise in the Python course is the same way, but I think if it comes up again it's worth trying to address.

You use two different credit card validation mechanisms in practice and solution for Exercise 1; one is const isValid = creditCardNumber.length == 16; and the other is a regex. Could be misleading.

Also, node_modules seems to be committed for the Exercise 1 solution, but not for the others -- it probably shouldn't be in there.

// TODO Part F: Import your compensatsefunction anderrorMessage function in rollback-with-saga/practice/src

Error messages at the end of workflows.ts in the Saga Exercise are also quite a bit different between practice and solution:
log.error('Error occurred in pizza workflow', { error: err });

vs
log.error(`Unable to bill customer: ${err}`);

Everything else looks good and is working in my testing :)


Missing signature for verification of root filesystem

Hi,
We're working on establishing trust for Docker containers, and for that to work, there needs to be a signature on the rootfs.tar.xz file.
Is it possible to add a (detached) signature in the relevant commits?

Unfortunately, these rootfs tarballs aren't (and can't currently reasonably be) built on the machine where I keep my GPG key, but I am interested in changing that somehow to make the provenance even more clear here, so I'm going to leave this open as an official "request for enhancement". :+1:

Thank you, I understand the concerns, but want to (re)state our concern here in that it's difficult to track the origins, something that's even worse by Debians design decision to not have a signed package manifest, but to only sign the apt lists.
We aren't trying to rebuild the Docker infrastructure here, but we're trying to take a known container and verify it's origin binaries, something that's turned out to be far harder than anticipated.

I came to this thread also trying to stablish up to which point the official debian docker image can be trusted.
It is certainly impossible to stablish some kind of trust right now. Even considering that the image is being managed by members of the Debian dev team.
This also brings some questions regarding what docker means by "official".
Alpine linux is now distributing a GPG signed minimal rootfs to be used for containers, just like any other flavor of distribution.
I think debian should do the same. The Dockerfile here could download the rootfs from Debian and verify the GPG signature.
I also wonder weather it is feasible to generate the rootfs from the netinstall.iso, which is signed, in the Dockerfile.

This repository is now deprecated in favor of https://github.com/debuerreotype/docker-debian-artifacts, which builds reproducible Debian rootfs tarballs using https://github.com/debuerreotype/debuerreotype. :+1:
To verify the new tarballs, I'd recommend grabbing debuerreotype and regenerating them externally.  For all but wheezy, the results should be bit-for-bit identical to what I've generated.
For wheezy, using diffoscope on what I've published and the newly generated bits should show a single benign change, which is documented in debuerreotype's README file.

That's pretty awesome. Thank you!
Ok to close this issue then.
On Wed, 7 Jun 2017, 22:52 Tianon Gravi<EMAIL_ADDRESS>wrote:

This repository is now deprecated in favor of
https://github.com/debuerreotype/docker-debian-artifacts, which builds
reproducible Debian rootfs tarballs using
https://github.com/debuerreotype/debuerreotype. 👍
To verify the new tarballs, I'd recommend grabbing debuerreotype and
regenerating them externally. For all but wheezy, the results should be
bit-for-bit identical to what I've generated.
For wheezy, using diffoscope on what I've published and the newly
generated bits should show a single benign change, which is documented in
debuerreotype's README file.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/tianon/docker-brew-debian/issues/46#issuecomment-306921283,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABmI5s0NW5Fk7CRmRuleyk9YzwtgNZZ8ks5sBw2fgaJpZM4IwsAC
.


Added negative parameter validation to Core/Recurrent/Convolutional Keras layers.

This PR adds validation and custom errors for negative inputs in various Keras layers throughout the core, convolutional, and recurrent modules.

Ok, I've made the changes as have been requested. Should I add tests for these different cases?


nixos/pcscd: allow use without polkit

Description of changes
The polkit support in pcsclite is entirely optional but package enables
it unconditionally and this breaks connecting to the pcscd daemon on
systems without polkit.
The fix is making this configurable and automatically disabling
polkitSupport when the polkit service is disabled.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] Tested programs can connect to the daemon (with and without polkitSupport)
[ ] Tested compilation of all packages that depend on this change
[x] Tested basic functionality of all binary files
[x] 22.11 Release Notes - shouldn't be necessary
[x] Fits CONTRIBUTING.md.

@GrahamcOfBorg build pcsclite

@ofborg eval


Every update triggers a full update / 2023 datastream not loading

Dependency Check v7.4.3 CLI (also v7.4.1).
When the database realises it needs to update (after 4 hours since the previous update) it re-downloads and re-processes all data files from nvdcve-1.1-2002.json.gz onwards. Previously,  only nvdcve-1.1-modified.json.gz would be downloaded and processed.
Also, nvdcve-1.1-2023.json.gz is not downloaded, just nvdcve-1.1-2023.meta.
This behaviour seems to have started since the turn of the year (unsure if this is significant).
edit: Add log
nvdache directory
Update output.txt
dc.log

This is also happening on 7.3.0.

This behaviour seems to have started since the turn of the year (unsure if this is significant).

It is... and will auto-resolve when the first succesful import of a 2023 datastream is done.
There is a provision to not break due to absence of a datastream early in the year, but regardless of that it will do a full update of everything as long as no data has been loaded for the new year, since before checking the availability of the datastream a flag is already set that a full update is required because at least one year (the year just started) has never been loaded into the database.
We should definitely fix this, but once 7.4.4 is out (fixing the current issue in loading NVD data) the issue will be invisible for almost a year as by now the datastream of 2023 is present, so after the next successful update it will be seen by DependencyCheck that data for 2023 has been loaded and data-age is checked to see if full- or modified-only update is required.

Hmmm..scratch the 'will be resolved after 7.4.4 can successfully load' I spotted some more bugs in the logic - should be fine again (until next year.... but before that I expect to develop a fix) after January 10.
As 7.4.4 should go out ASAP (issue 5220) and a fix of the download logic would need a bit better testing to ensure that this time it will really 'do the right thing early in the new year' I'm not going to rush the patch to try-and-squeeze it in for 7.4.4.

On second thought.... fixing it is unnecessary as by the next turn-of-year there will be no more NVD datafeeds to import as the NIST is phasing them out this year

Keeping the ticket open until 10 January has passed

Any update on issue as still getting error finding CVE 2023 as below.
`> Task :dependencyCheckUpdate
Error downloading NVD CVE - 2023 Reason: Requested resource does not exists - received a 404

Task :dependencyCheckUpdate
The execution of the download was interrupted
org.owasp.dependencycheck.data.update.exception.UpdateException: The execution of the download was interrupted
at org.owasp.dependencycheck.data.update.NvdCveUpdater.performUpdate(NvdCveUpdater.java:289)
at org.owasp.dependencycheck.data.update.NvdCveUpdater.update(NvdCveUpdater.java:136)`

Any update on issue as still getting error finding CVE 2023 as below.
`> Task :dependencyCheckUpdate
Error downloading NVD CVE - 2023 Reason: Requested resource does not exists - received a 404

Task :dependencyCheckUpdate
The execution of the download was interrupted
org.owasp.dependencycheck.data.update.exception.UpdateException: The execution of the download was interrupted
at org.owasp.dependencycheck.data.update.NvdCveUpdater.performUpdate(NvdCveUpdater.java:289)
at org.owasp.dependencycheck.data.update.NvdCveUpdater.update(NvdCveUpdater.java:136)`

Also experiencing the same issue as this currently, it affects all our builds, any solution to this one? or we can only wait for them to have the NVD CVE 2023?
Thanks.

@stevenpila  Sounds like you connect to a mirror that somehow doesn't have the 2023 datasterams. They've been available from NIST NVD for several days. My mirror had it's last update with lastmodifieddate:2023-01-09T03:00:00-05:00

I can confirm my original problem(s) no longer occur, although others seem to still be having issues.

@stevenpila Sounds like you connect to a mirror that somehow doesn't have the 2023 datasterams. They've been available from NIST NVD for several days. My mirror had it's last update with lastmodifieddate:2023-01-09T03:00:00-05:00

Hi, it's already working for us now and you're right, it was previously connected to a different mirror link (not the default) that still doesn't have the 2023 data streams. Thank you. :)


v1.1.1 breaks routing with encoded newlines in query strings

The v1.1.1 release introduced URI decoding of path and query params, meaning encoded newlines in query strings (?param=foo%0Abar) prevent matching against ANY route since the regular expression dot (.*) doesn't match newlines. This broke things pretty badly for us, which is frustrating for a point-release.
Not sure what the best fix is, but I'm thinking Router#_routeToRegExp should probably be updated to match against newlines as well. That or there should at least be documentation explaining that query params cannot contain encoded newline characters. Thoughts? I'd be happy to attach a PR to this if there's consensus on how this should be resolved.

I think I encountered something related to this in IE 11. Workaround:
    // Not sure why, but IE is unable to match routes with `\n` characters in them?
    // Re-encoding the characters fixes it.
    Backbone.History.prototype.decodeFragment = _.wrap(Backbone.History.prototype.decodeFragment, function (decodeFragment, fragment) {
        var decoded = decodeFragment.call(this, fragment);
        return decoded.replace(/\n/g, '%0A');
    });

Thought I'd share in case anyone else has this issue. I assume it's just an edge-case that will hopefully get fixed in later releases on IE (maybe Edge?).


[WIP] Docs/events

This PR introduces Events to the UOR Framework.

@d10n @jpower432 can you please let me know which parts of this doc need clarification?


Avoid compiling and running the tests of tools

The tools directory of the project contains the source of some tools that have been copied from the openshift/release project, as decribed here. A side effect of that is that when running make check the build scripts try to compile also the tests of those tools, in particular the tests of the junitreport tool. That fails because of missing dependencies:
tools/junitreport/pkg/builder/flat/test_suites_builder.go:4:2: cannot find package "github.com/openshift/origin/tools/junitreport/pkg/api" in any of:
	/files/projects/openshift/autoheal/_output/local/go/src/github.com/openshift/autoheal/vendor/github.com/openshift/origin/tools/junitreport/pkg/api (vendor tree)
	/usr/lib/golang/src/github.com/openshift/origin/tools/junitreport/pkg/api (from $GOROOT)
	/files/projects/openshift/autoheal/_output/local/go/src/github.com/openshift/origin/tools/junitreport/pkg/api (from $GOPATH)

Currently we solved this removing those tests files from the repository, but that isn't a good long term solution, as the tests may be accidentally re-added when the tools directory is updated in the future.
A possible solution suggested by @ironcladlou in #6 is to tell dep to ignore that directory, adding the following to the Gopkg.toml file:
ignored = ["github.com/openshift/autoheal/tools*"]

That seems like a more correct solution, but in our initial tests it didn't solve the problem. In addition, even if it solves the problem, then the tests of the junitreport  tool would be executed in addition to the tests of the project itself, thus polluting the output:
ok  	github.com/openshift/autoheal/cmd/autoheal	1.452s	coverage: 11.8% of statements
ok  	github.com/openshift/autoheal/tools/junitreport/pkg/builder/flat	1.009s	coverage: 100.0% of statements
ok  	github.com/openshift/autoheal/tools/junitreport/pkg/builder/nested	1.008s	coverage: 98.5% of statements
ok  	github.com/openshift/autoheal/tools/junitreport/pkg/parser/oscmd	1.103s	coverage: 100.0% of statements
ok  	github.com/openshift/autoheal/tools/junitreport/pkg/parser/stack	1.009s	coverage: 17.2% of statements

The optimal solution would preserve the test files, wouldn't add the junitreport project or its dependencies to the vendor directory and wouldn't run the junitreport tests together with the project tests. We should try to find that solution.

The first attempt to address this issue is #16.

The way I see it, the "tools" code is actually a completely self contained Go project with its own dependency tree. Here are two ways I can think of that this could work less invasively:

If tools doesn't actually need to compile any tools stuff at runtime (and this would include runtime compilation indirectly via go run), then the installation procedure for tools could use a compilation process to ensure everything in the project tools directory has no external dependencies
If tools absolutely must compile stuff at runtime, the tools directory should be a self-contained GOPATH, and all tools dependencies should be vendored with in it.

Other ideas?

Whoops, I meant to put that comment an in issue against the release tools themselves. I think first I'd like to actually come up with a repeatable "example" project to help frame the discussion and test solutions.


Add JMeter plan for Find

Context
Following the structure of the Apply and Manage plans, add a plan which
exercises common paths in Find.

Changes proposed in this pull request

Navigate through the three options for searching for a course,
clicking on a course page each time.
Add configurable wait factor and thread count.

Guidance to review

Diff should be adequate to get an overview of what paths are being hit
Can be run locally without any additional dependencies (doesn't need any extra files or scripts like the Apply plan).

Link to Trello card
https://trello.com/c/sj551ab3

Things to check

[ ] This code does not rely on migrations in the same Pull Request
[ ] If this code includes a migration adding or changing columns, it also backfills existing records for consistency
[ ] API release notes have been updated if necessary
[ ] Required environment variables have been updated added to the Azure KeyVault

It's def worth @mnacos having a look as i'm not super familiar with Jmeter, but it looks good to me Malcolm


Help with configuration

⚠ Please verify that this question has NOT been raised before.

[X] I checked and didn't find similar issue

🛡 Security Policy

[X] I agree to have read this project Security Policy

📝 Describe your problem
I need some help to configure a monitor.
I have to call a URL that return a JSON and then check a value in the JSON.
curl https://pool.braiins.com/accounts/profile/json/btc/ -H "SlushPool-Auth-Token: xxxxxxxxxxxxxxx"
that return
{   "username": "vellanix",   "btc": {     "low_workers": 0,     "off_workers": 0,     "ok_workers": 4,     "dis_workers": 0,   } }
and I want to check that the value of "ok_workers" is 4.
My monitoring setup is:

but unfortunately doesnt work, and in the LOG file I see:
2024-09-05T11:46:21+02:00 [MONITOR] WARN: Monitor #8 'Workers': **Failing: Cannot read properties of undefined (reading 'toString')** | Interval: 60 seconds | Type: json-query | Down Count: 0 | Resend Interval: 0
What's wrong?
Thank you
📝 Error Message(s) or Log
2024-09-05T11:46:21+02:00 [MONITOR] WARN: Monitor #8 'Workers': Failing: Cannot read properties of undefined (reading 'toString') | Interval: 60 seconds | Type: json-query | Down Count: 0 | Resend Interval: 0
🐻 Uptime-Kuma Version
1.23.13
💻 Operating System and Arch
docker
🌐 Browser
chrome
🖥 Deployment Environment

Runtime:
Database:
Filesystem used to store the database on:
number of monitors:

Sorry for the late reply
First of all, are you sure that the above is returned from the API? The reason I am asking is that that is not valid JSON (see the last ,).
Could you try $.btc.ok_workers?
We have improved the provided docs for this, but this is waiting for #4500
If this does not work, I am asssuming this is because the invalid JSON issue noted above :eyes:


ARROW-5336: [C++] Implement arrow::Concatenate for dictionary-encoded arrays with unequal dictionaries

The dictionaries still need to have the same index & value types.  It is possible that concatenating two dictionaries still fails because the resulting dictionary has more values than its index type can represent.
The unification will still fail if nulls are present in either dictionary.  The canonical approach seems to be representing nulls in the indices array with a validity bitmap.  The existing unifier had this constraint in place.  My guess is that this was to avoid making the memo table null-aware.  It could be handled without modification to the memo table by using a -1 index and so I could easily add this if desired.  I wasn't sure if support for this non-typical case justified the complexity.

Thanks for the insight @pitrou .  Your guess was right, there was a bug with multi-byte index types.  I believe I have addressed your concerns.

Thanks for the insight @pitrou .  Your guess was right, there was a bug with multi-byte index types.  I believe I have addressed your concerns.

A bit late that I think of it, but the arrow->pandas code already has some dictionary concatenation code (https://github.com/apache/arrow/blob/97f8160e56036909cdf554860baa341c46d3caf3/cpp/src/arrow/python/arrow_to_pandas.cc#L1641-L1676). I am not that familiar with the code, but there might be room for simplification there with the functionality added in this PR.

A bit late that I think of it, but the arrow->pandas code already has some dictionary concatenation code (https://github.com/apache/arrow/blob/97f8160e56036909cdf554860baa341c46d3caf3/cpp/src/arrow/python/arrow_to_pandas.cc#L1641-L1676). I am not that familiar with the code, but there might be room for simplification there with the functionality added in this PR.

@jorisvandenbossche It's pretty close but there are a few differences.

The pandas code allows the index type to expand (e.g. from uint8_t to uint16_t).  In fact, it looks like it always sets it to int32_t.  Also, arrow doesn't allow dictionary indices to be negative.
The pandas code puts -1 in the map for a null value.  Arrow uses null in the validity bitmap for the indices array and/or null as an item in the dictionary itself with a valid index (both approaches are legal)

I'll defer to @pitrou if we want to combine them but it seems simpler to just leave them separate for now.

@jorisvandenbossche It's pretty close but there are a few differences.

The pandas code allows the index type to expand (e.g. from uint8_t to uint16_t).  In fact, it looks like it always sets it to int32_t.  Also, arrow doesn't allow dictionary indices to be negative.
The pandas code puts -1 in the map for a null value.  Arrow uses null in the validity bitmap for the indices array and/or null as an item in the dictionary itself with a valid index (both approaches are legal)

I'll defer to @pitrou if we want to combine them but it seems simpler to just leave them separate for now.

Ah, yes, I forgot about the null handling needed for pandas. That's certainly something that shouldn't be added to the general arrow functionality, but can be left as specific handling the arrow_to_pandas code.

Ah, yes, I forgot about the null handling needed for pandas. That's certainly something that shouldn't be added to the general arrow functionality, but can be left as specific handling the arrow_to_pandas code.

The differences look a bit annoying to reconcile (especially the different null representation). Not sure it's worth doing anything.

The differences look a bit annoying to reconcile (especially the different null representation). Not sure it's worth doing anything.