actions/search.go:84:16: undefined: buffalo.EvtAppStart

My system
Ubuntu 18.04
go version go1.11 linux/amd64
buffalo 0.12.6
node 8.10.0
npm 3.5.2
yarn 1.9.3
What I did:
I followed the instructions here to get the solution working in dev mode.
What I expected
I expected to be able to access http://<IP_ADDRESS>:3000 after running the three setup commands
What happened
jason@freeland:~/coding/go/src/github.com/gobuffalo/gobuffalo$ buffalo dev
buffalo: 2018/09/25 08:10:51 === Rebuild on: :start: ===
buffalo: 2018/09/25 08:10:51 === Running: go build -v -i -tags development -o /tmp/gobuffalo-build  (PID: 20377) ===
github.com/gobuffalo/gobuffalo/actions
# github.com/gobuffalo/gobuffalo/actions
actions/search.go:84:16: undefined: buffalo.EvtAppStart
buffalo: 2018/09/25 08:10:52 === Error! ===
buffalo: 2018/09/25 08:10:52 === exit status 2
github.com/gobuffalo/gobuffalo/actions
# github.com/gobuffalo/gobuffalo/actions
actions/search.go:84:16: undefined: buffalo.EvtAppStart
 ===

Webpack is watching the files…

Live Reload listening on port 35729

Hash: a1a374e3044d6321aca2
Version: webpack 4.5.0
Time: 8606ms
Built at: 9/25/2018 8:11:01 AM
                                Asset       Size         Chunks             Chunk Names
      images/landing_icons/models.svg   6.97 KiB                 [emitted]
 674f50d287a8c48dc19ba404d20fe713.eot    162 KiB                 [emitted]
  application.a1a374e3044d6321aca2.js    960 KiB    application  [emitted]  application
clipboard.min.a1a374e3044d6321aca2.js   17.1 KiB  clipboard.min  [emitted]  clipboard.min
        home.37ef2a29baca4b00337d.css   8.39 KiB           home  [emitted]  home
         home.a1a374e3044d6321aca2.js   3.77 KiB           home  [emitted]  home
        theme.a1a374e3044d6321aca2.js    613 KiB          theme  [emitted]  theme
               images/404_example.png    117 KiB                 [emitted]
  images/apple-touch-icon-114x114.png   20.4 KiB                 [emitted]
  images/apple-touch-icon-120x120.png   21.6 KiB                 [emitted]
  images/apple-touch-icon-144x144.png   29.4 KiB                 [emitted]
    images/apple-touch-icon-57x57.png   6.56 KiB                 [emitted]
               images/500_example.png    626 KiB                 [emitted]
  images/apple-touch-icon-152x152.png   32.5 KiB                 [emitted]
    images/apple-touch-icon-72x72.png   9.37 KiB                 [emitted]
             images/favicon-16x16.png  928 bytes                 [emitted]
                   images/buffalo.svg   55.4 KiB                 [emitted]
             images/favicon-32x32.png   2.62 KiB                 [emitted]
                   images/buffalo.png   8.72 KiB                 [emitted]
                   images/favicon.ico    5.3 KiB                 [emitted]
      images/landing_icons/cactus.svg   5.06 KiB                 [emitted]
 application.a615e838e118100f0357.css    1.2 MiB    application  [emitted]  application
 images/landing_icons/play_button.svg   1.46 KiB                 [emitted]
        images/landing_icons/plus.svg   1.73 KiB                 [emitted]
    images/landing_icons/frontend.svg   6.46 KiB                 [emitted]
        images/landing_icons/Mask.png   20.1 KiB                 [emitted]
        images/landing_icons/task.svg   11.1 KiB                 [emitted]
     images/landing_icons/routing.svg   10.7 KiB                 [emitted]
  images/landing_icons/templating.svg   3.87 KiB                 [emitted]
     images/landing_icons/testing.svg   7.26 KiB                 [emitted]
                        images/bg.png   2.66 MiB                 [emitted]
     images/landing_icons/toolbox.svg    5.5 KiB                 [emitted]
  images/landing_icons/tumbleweed.svg   23.6 KiB                 [emitted]
                      images/logo.svg   64.4 KiB                 [emitted]
                  images/logo_top.png   3.58 KiB                 [emitted]
                  images/logo_med.png    153 KiB                 [emitted]
             images/logos/missing.png   2.27 KiB                 [emitted]
            images/logos/wawandco.png   8.16 KiB                 [emitted]
           images/logos/papercall.png   85.5 KiB                 [emitted]
        images/logos/gopherguides.png    504 KiB                 [emitted]
                  images/new-coke.png   33.9 KiB                 [emitted]
                        manifest.json   2.53 KiB                 [emitted]
Entrypoint application = application.a615e838e118100f0357.css application.a1a374e3044d6321aca2.js
Entrypoint home = home.37ef2a29baca4b00337d.css home.a1a374e3044d6321aca2.js
Entrypoint clipboard.min = clipboard.min.a1a374e3044d6321aca2.js
Entrypoint theme = theme.a1a374e3044d6321aca2.js
[./assets/css/application.scss] 39 bytes {application} [built]
[./assets/css/home.scss] 39 bytes {home} [built]
[./assets/js/application.js] 2.79 KiB {application} [built]
[./assets/js/clipboard.min.js] 13.1 KiB {clipboard.min} {application} [built]
[./assets/js/theme.js] 295 KiB {theme} {application} [built]
[./node_modules/expose-loader/index.js?Clipboard!./assets/js/clipboard.min.js-exposed] ./node_modules/expose-loader?Clipboard!./assets/js/clipboard.min.js-exposed 167 bytes {app
lication} [built]
[./node_modules/webpack/buildin/amd-options.js] (webpack)/buildin/amd-options.js 82 bytes {theme} {application} [built]
[./node_modules/webpack/buildin/global.js] (webpack)/buildin/global.js 509 bytes {theme} {application} [built]
   [0] multi ./node_modules/jquery-ujs/src/rails.js ./assets/css/application.scss ./assets/js/application.js 52 bytes {application} [built]
   [4] multi ./assets/css/home.scss 28 bytes {home} [built]
   [6] multi ./assets/js/clipboard.min.js 28 bytes {clipboard.min} [built]
   [7] multi ./assets/js/theme.js 28 bytes {theme} [built]
    + 12 hidden modules
Child mini-css-extract-plugin node_modules/css-loader/index.js??ref--4-1!node_modules/sass-loader/lib/loader.js??ref--4-2!assets/css/application.scss:
                                   Asset     Size  Chunks             Chunk Names
    674f50d287a8c48dc19ba404d20fe713.eot  162 KiB          [emitted]
    Entrypoint mini-css-extract-plugin = *
    [./node_modules/css-loader/index.js??ref--4-1!./node_modules/sass-loader/lib/loader.js??ref--4-2!./assets/css/application.scss] ./node_modules/css-loader??ref--4-1!./node_mo
dules/sass-loader/lib/loader.js??ref--4-2!./assets/css/application.scss 520 KiB {mini-css-extract-plugin} [built]
        + 10 hidden modules
Child mini-css-extract-plugin node_modules/css-loader/index.js??ref--4-1!node_modules/sass-loader/lib/loader.js??ref--4-2!assets/css/home.scss:
    Entrypoint mini-css-extract-plugin = *
    [./node_modules/css-loader/index.js??ref--4-1!./node_modules/sass-loader/lib/loader.js??ref--4-2!./assets/css/home.scss] ./node_modules/css-loader??ref--4-1!./node_modules/s
ass-loader/lib/loader.js??ref--4-2!./assets/css/home.scss 23.3 KiB {mini-css-extract-plugin} [built]
        + 1 hidden module

This is not a blocker to the Spanish translation work I'm doing but I'd still like to get a working version on local.
Thanks in advance for your help!

I deleted the directory and tried to pull again:
$ go get github.com/gobuffalo/gobuffalo
# github.com/gobuffalo/gobuffalo/actions
coding/go/src/github.com/gobuffalo/gobuffalo/actions/search.go:84:16: undefined: buffalo.EvtAppStart

Resolved after installing dep package.

I'm still having the same issue here using go 1.10.4.
% /usr/local/bin/buffalo version
INFO[0000] Buffalo version is: v0.12.6

% go get github.com/gobuffalo/gobuffalo
# github.com/gobuffalo/gobuffalo/actions
gobuffalo/actions/search.go:84:16: undefined: buffalo.EvtAppStart

% buffalo dev
buffalo: 2018/10/02 08:37:35 === Rebuild on: :start: ===
buffalo: 2018/10/02 08:37:35 === Running: go build -v -i -tags development -o /tmp/gobuffalo-build  (PID: 34674) ===
github.com/gobuffalo/gobuffalo/actions
# github.com/gobuffalo/gobuffalo/actions
actions/search.go:84:16: undefined: buffalo.EvtAppStart
buffalo: 2018/10/02 08:37:36 === Error! ===
buffalo: 2018/10/02 08:37:36 === exit status 2
github.com/gobuffalo/gobuffalo/actions
# github.com/gobuffalo/gobuffalo/actions
actions/search.go:84:16: undefined: buffalo.EvtAppStart
 ===

@duffn You need to use dep. The project uses the development branch of buffalo.

Okay, so
% dep ensure
% buffalo dev

then gives me a bunch of missing asset errors and the pages are served without styling.
ERRO[2018-10-02T08:57:47-06:00] could not find assets/application.css
ERRO[2018-10-02T08:57:47-06:00] could not find assets/images/logo_med.png
ERRO[2018-10-02T08:57:47-06:00] could not find assets/images/logo_top.png
ERRO[2018-10-02T08:57:47-06:00] could not find assets/home.css
ERRO[2018-10-02T08:57:48-06:00] could not find assets/application.js
ERRO[2018-10-02T08:57:48-06:00] could not find assets/images/landing_icons/play_button.svg
ERRO[2018-10-02T08:57:48-06:00] could not find assets/images/landing_icons/routing.svg
ERRO[2018-10-02T08:57:48-06:00] could not find assets/images/landing_icons/templating.svg
ERRO[2018-10-02T08:57:48-06:00] could not find assets/images/landing_icons/toolbox.svg
ERRO[2018-10-02T08:57:48-06:00] could not find assets/images/landing_icons/testing.svg
ERRO[2018-10-02T08:57:48-06:00] could not find assets/images/landing_icons/frontend.svg
ERRO[2018-10-02T08:57:48-06:00] could not find assets/images/landing_icons/models.svg
ERRO[2018-10-02T08:57:48-06:00] could not find assets/images/landing_icons/task.svg
ERRO[2018-10-02T08:57:48-06:00] could not find assets/images/landing_icons/cactus.svg
ERRO[2018-10-02T08:57:48-06:00] could not find assets/images/logos/gopherguides.png
ERRO[2018-10-02T08:57:48-06:00] could not find assets/images/logos/papercall.png
ERRO[2018-10-02T08:57:48-06:00] could not find assets/images/logos/wawandco.png
ERRO[2018-10-02T08:57:48-06:00] could not find assets/images/landing_icons/tumbleweed.svg
ERRO[2018-10-02T08:57:48-06:00] could not find assets/images/landing_icons/plus.svg

Can you try buffalo setup?

That did it, thank you.


Add RichTextBox

In this topic we collect all issues related to RichEdit functionality.

@generalloki, thanks for all new "functions" available for TextBox and Sample added into Text Input

May be we need to create a separate control like RichTextBox (and just set IsRichEdit = true in the constructor)?

This is good idea. But first we need to study difference between
wxRichTextCtrl (https://docs.wxwidgets.org/3.2/classwx_rich_text_ctrl.html)
and wxTextCtrl in rich edit mode. Also we need to study whether wxRichTextCtrl/wxTextCtrl
has file save/open feature in rich text format.

sounds good, wxRichTextCtrl may provide extra features, need to be investigated.

I am closing this issue for now as fully featured RichTextBox is implemented


added volos and acl config and pipette starting capability

I'm happy to merge this once the tests pass, since it doesn't impact any existing code.


update ci to use non-deprecated release action

apparently i got inspiration from a project using a deprecated action and now i cant customize it...
we are using create-release in our release action, but should be using softprops/actions-gh-release (as we are in kube-rs main repo).
...then we can make the change i wanted to make:

generate_release_notes -> true (so we auto-generate before the release email has been sent)

started doing this now and made the 0.7.0 release. hopefully the release asset stuff just work otherwise will fix later.

that worked well:

https://github.com/kube-rs/kopium/releases/tag/v0.7.0
https://github.com/kube-rs/kopium/actions/runs/1867855285


build: bump ops to latest possible version

Part of canonical/bundle-kubeflow#868

I see that the CI fails due to https://github.com/canonical/bundle-kubeflow/issues/921. Should we block on this?

I see that the CI fails due to canonical/bundle-kubeflow#921. Should we block on this?

I think it is not worth for now to update this as this component will fall out of maintenance soon.
Closing this PR for now.


NSFS | NC | fix list-objecs-versions issues

Explain the changes

change _get_object_list to return version id in suspended mode, causing list-object-versions to return version-id in suspended mode as well
set isLatest flags for objects in the main bucket folder and not in .version
add special case to check if delete marker is the latest version by checking if its the most recent entry of the key

Issues: Fixed #xxx / Gap #xxx

https://github.com/noobaa/noobaa-core/issues/7372

Testing Instructions:

sudo NC_CORETEST=true node ./node_modules/mocha/bin/mocha src/test/unit_tests/test_bucketspace.js

[ ] Doc added/updated
[x] Tests added

is this backported to 4.17 , in noobaa d/s 0904, this one is still a problem ""IsLatest": true"

@rkomandu it was backported on 0904, so no, it's not there...


When use method rollTo reset roulette

Hello, I am using this package and I notice that when using the "rollTo" method the spinner resets and spins instead of continuing where it was going.
Any idea how to make the roulette continue where it was and not see that reset screenshot?
I think that the problem maybe is in _controller.forward(from: 0) instead of current index.
Future<void> rollTo(     int targetIndex, {     Duration duration = defaultDuration,     int minRotateCircles = defaultMinRotateCircles,     bool clockwise = true,     Curve? curve = Curves.fastOutSlowIn,     double offset = 0,   }) async {     final targetRotate = calculateEndRotate(       group,       targetIndex,       clockwise,       minRotateCircles,       offset: offset,     );     _controller.duration = duration;     _animation = makeAnimation(_controller, targetRotate, curve);     notifyListeners();     **await _controller.forward(from: 0);**  }``
Thank very much

That’s because I’m too lazy to do that =). Thanks for pointing this out.
I try to implement that on the branch “dev/feature/continuous-rollTo”.
(Hash tag is 3047ee0272c54a2e6e524f24f9270007e73fc537).
You could try import that version using git reference in pubspec.yaml.
If you find that's useful, please let me know and I would consider to release it on main branch.
发件人: @.>
发送时间: 2022年10月15日 19:11
收件人: @.>
抄送: @.***>
主题: [do9core/roulette] When use method rollTo reset roulette (Issue #14)
Hello, I am using this package and I notice that when using the "rollTo" method the spinner resets and spins instead of continuing where it was going.
Any idea how to make the roulette continue where it was and not see that reset screenshot?
Thank very much
―
Reply to this email directly, view it on GitHubhttps://github.com/do9core/roulette/issues/14, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AE2RK3EG2BQ7MBKM6VK7JULWDKGM3ANCNFSM6AAAAAARF3XG6U.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

Now it's perfect!!!!
Thank you very much
So it looks more natural and better :)

I'v published the version 0.1.3 to fix this.
You can upgrade to that version now and, I'm closing this issue.
If you have any other questions about this issue, please re-open, thanks :)


Action based on a trendline touched trigger?

Is it possible to make an automatic order or other action based on a trendline touched trigger ?

This is a rendering-only lib, but the answer: yes, in your app.

I see.  When I draw a trendline how can i get value of each trendline points (coordinates)  for every Timeframe unit ?  because i suppose in the app i need to compare the coordinates of the trendline point and the value of the candle chart to see if  the trendline i draw is touching the candle chart on a  specific timeframe (for example minute in my case)

The line points are in the overlay's settings object (see LineTool.vue). All you need is to apply a simple math.

Ok Thanks


Move to graphp organization

Now that all components have been split off into separate packages under the graphp organization, we should eventually also move this repository.
Things to consider:

Does this involve any BC breaks? What about consumers of this package?
Should we rename this package to the "graphp" vendor?
If so, what package name should we assign?

I'd like to migrate previous issues, PR, among with all watchers and stargazers, so forking does not seem to be an option.
Any input would be much appreciated!

I recently moved a repo then cloned it back on the old location then removed all files except for the README.md to tell about the move.
Old consumers will still find the releases on the old location.
Do not forget to tell https://packagist.org

Thanks for the feedback!
Moving this repository to the graphp organization should actually be a no-brainer, given that GitHub automatically sets up redirects and Composer does a reasonable good job at following redirects.
I'm voting for moving this repository instead of setting up a clone (in either direction) because this will set up a working redirect for all existing links (including issues/PRs etc.)
The future home will likely be graphp/graph, though I'm not entirely sure I like the name (could be confusing?). Perhaps an additional redirect from graphp/graphp to graphp/graph (notice the subtle trailing p) could help? Also keep in mind the name is not set in stone…
Any input is welcome!
FWIW, renaming the package will be the next step that will probably be postponed for a few weeks (just in case).

Ping @all:
What do you think about the name "graphp/graph"?
Any better suggestions?

Ping @all:
What do you think about the name "graphp/graph"?

:shipit: ?

I like the organization name. And hopefully it would be a good starting point finding sponsors.

For the reference, this ticket is only about moving this repo to the graphp organization, without affecting the composer package name. As such, this should not have a huge impact on our existing user base.
Updating the package name will be postponed to #134, as this will break compatibility with all existing users.

I like the organization name.

So do I :-) However, I'm not sure about the project name within this organization:
graphp/graph ?
graphp/graphp ?
This also affects the PHP namespace and class names:
Graphp\Graph\Graph ?
Graphp\Graph\Vertex

And hopefully it would be a good starting point finding sponsors.

Not sure I follow… what do you have in mind? :-)

Ic � what about graphp/core ?

I like your suggestion, but then again, what is a "core"? :-)
https://en.wikipedia.org/wiki/Core_(graph_theory)

core is core of graphp/* � guess kernel / base as similar disputable :p

Does this involve any BC breaks? What about consumers of this package?

To prevent any BC, I would move everything from PSR-4 to PSR-0 (e.g. src/Exception.php to src/Fhaculty/Graph/Exception.php), move old sources under the new namespace, make them extend the old classes (empty classes used temporary only to maintain the original type) and use a deprecations system to allow users to adapt their sources.
Example:
// src/Fhaculty/Graph/Graph.php

/**
 * @deprecated Deprecated since version 0.9, to be removed in 1.0. Use Graphp\Graph\Graph instead.
 */
class Graph
{
}

// src/Graphp/Graph/Graph.php

class Graph extends \Fhaculty\Graph\Graph
{
  // ...
}

Of course this change should be done in composer.json too, but that's considered an internal change, no APIs are involved.
The code shouldn't stay dirty for a long time considering that this library is at v0.9.

Should we rename this package to the "graphp" vendor?
If so, what package name should we assign?

Yes, I'm +1 for graphp/graph
Also the repository redirect is no more a pain.
If you need a help I'm available, https://github.com/graphp seems a really nice project. :)

Does this involve any BC breaks? What about consumers of this package?

Thanks for your valuable input @EmanueleMinotto, but I believe most of this actually belongs to #134 :+1:
This ticket here is only concerned with moving the repository to the https://github.com/graphp GitHub organization. As far as I can tell, this does not involve any BC breaks whatsoever, now that GitHub will setup redirects for HTTP and git links and composer seems to be able to cope with this just as well.

Should we rename this package to the "graphp" vendor?
Yes, I'm +1 for graphp/graph

Thanks! I think we agree here, so let's move forward on this one :+1:

I found https://github.com/graphp/graph which confuses me. It is a clone of this repo https://github.com/clue/graph which contradicts https://github.com/clue/graph/issues/130#issuecomment-116861859

Moving this repository to the graphp organization should actually be a no-brainer, given that GitHub automatically sets up redirects and Composer does a reasonable good job at following redirects.

See also https://github.com/graphp/graph/network. I'm confused.
Regarding the name I'm still fine with graphp/graph :)


UNFCCC 'Tools' as a new concept in Guardian

Problem description
Currently Guardian has a number of methods to help users to build policies more efficiently and re-use the code:

modules
linked policies
copy-paste and parent/child actions on blocks and sets of blocks

However these tools are too low level for subject matter (non-technical) experts - environmental specialists, which think in higher-order concepts. The best example of such concepts and the most relevant 'standard' modules are Tools as developed by the UN FCCC project. These currently can not be directly implemented in Guardian policy as concepts and thus mapping UNFCCC tools which are numbered to policy elements is not straightforward.
Requirements
Introduce 'Tools' concept as a 'first-class' citizen of Guardian policies such that policy authors can 'just' re-use Tools (without any modification), linking them together and mixing with custom policy blocks etc in a policy to deliver a seamless onboarding experience for environment projects managed by non-technical individuals.
'Tools' should have the following properties:

contain schemas for VCs, logic (including especially calculation block and if-then-else capability) and be able to 'consume' and 'produce' multiple VC documents
be shareable  and re-useable across instances and within an instace
be signed and immutable in the sense that they don't requite any modification to be included/used in a policy
should be able to 'include' other Tools, i.e. Tools can be nested into other tools to reflect e.g. the relationship between Tool 14 (a container) and Tool 3 (embedded in T14)

Definition of done

Guardian capabilities enable the creation of the UNFCCC tool library mapping one-to-one, including the embedded relationships between Tools.
A few example Tools are created matching does found in the UNFCCC website
Documentation is created

Acceptance criteria

It is possible the implement library of UNFCCC Tools in Guardian Tools
Users can see one-to-one mapping between Tool numbers in UNFCCC and Guardian Tool library

Design notes:

Functionally 'Tools' are the same as Policies. Policies can 'employ' (or reference) Tools, Tools can 'employ' other Tools.
When a Tool is published the system create a zip similar to the one for policy, the only difference is that there is a manifest with signatures which can attest to its correctness
This zip file is saved in a BD and IPFS
When a Policy is created which 'employs' a Tool the latter is added to the Policy as a link
4.5 Tools are read-only
When a Policy is exported the exported bundle contains a folder 'Tools' which contains the zip fils of all the Tools it 'employs'.
Correspondingly, when a Policy 'with Tools' is imported the Policy itself is imported as before, the Tools are imported into the Tools table if the instance does not have those already.
When the Policy is run
7.1 The system searches for Tools in the block tree
7.2 Zip files of the found Tools are retrieved from the DB/IPFS and unarchived, signatures validated
7.3  Schemas (and other artifacts like tokens) are added to the list of Policy files
7.4  The tree of blocks from the Tool is inserted into the Policy tree of blocks exactly where the link to the Tool is in the original Policy document
7.5  The Policy run-time object (now with the blocks from the Tools) is run as if all these blocks where directly in the Policy natively


Added post-artifact hooks

This would help me to respond to successful artifact uploads, particularly with deployment.

Looks great! I'll push this out in the next stable release of the agent! Thanks! :+1:

@joelmoss pushed out a new stable with your new hooks! Thanks again!

Cheers!
--
Joel Moss
Sent with Airmail
On 29 July 2015 at 17:00:42, Keith Pitt<EMAIL_ADDRESS>wrote:
@joelmoss pushed out a new stable with your new hooks! Thanks again!
—
Reply to this email directly or view it on GitHub.


transaction implemented?

I'm trying to update a post object in Firebase using a transaction, but i'm getting an error that transaction is not defined.
I looked in:
\react-native-firestack\lib\modules\database.js
but do not see any references to transactions, is this implemented?
Example code:
function toggleStar(postRef, uid) {   postRef.transaction(function(post) {     if (post) {       if (post.stars && post.stars[uid]) {         post.starCount--;         post.stars[uid] = null;       } else {         post.starCount++;         if (!post.stars) {           post.stars = {};         }         post.stars[uid] = true;       }     }     return post;   }); }

Good catch. We do not yet have transactions implemented.
Wanna make a PR? I can walk you through how to do it, if so. Otherwise, I'll see if I have time this weekend.

I took a look but I think this is a bit over my head, I'm not much of a java programmer.  I definitely appreciate your help.

Also looking for this feature :)

Alright. I'll prioritize this. Shouldn't be too difficult to implement, I don't think.

Also looking for this feature. Any update on this?

Also looking for this feature, fix yet?


sourcemap didn't effective

I successfully uploaded the sourcemap and I can see the sourcemap list showed on the grafana front-end, but the error detail didn't convert stack traces from JavaScript browser errors back into their original representation after I upload the sourcemap
the error show below, it turns out whether I upload the sourcemap or not, it shows the same error detail, how does the sourcemap associate with our js file? is there any possible problem about the usage or do I missing anything?
Error: test sourcemap
at onClick (http://<IP_ADDRESS>:8080/xxx.js:537:2618)
at Object.lj (https://cdn.jsdelivr.net/npm/react-dom@18.2.0/umd/react-dom.production.min.js:223:217)
at  (:0:0)
at  (:0:0)
at  (:0:0)
at  (:0:0)
at  (:0:0)
at  (:0:0)
at  (:0:0)
at  (:0:0)
the integration works that I do:
//add in webpack
new FaroSourceMapUploaderPlugin({
appName: 'Welcome',
endpoint: 'xxx',
appId: 'xxx',
stackId: 'xxx',
apiKey: webpackConfigEnv.FaroSourceMapKey,
gzipContents: true
})
]
look forward to your response!!

hi @ambershi1 sorry for the delay
are you still experiencing this issue? if so, please provide me with some more details so I can better identify what the problem is.
can you share:

your configuration of the Faro web SDK? specifically the initializeFaro portion
the rest of the configuration of your webpack configuration
the output of your bundler when you run it

let me know - thank you

I'm afraid I just can provide the below info, and also I pick one sourcemapId:<PHONE_NUMBER>3471066c174d4 which was shown in Source Map List, does that useful?
plugins: [
  // other plugins...
  new FaroSourceMapUploaderPlugin({
    appName: 'Harness',
    endpoint: 'https://faro-api-prod-us-central-0.grafana.net/faro/api/v1',
    appId: '1117',
    stackId: '399567',
    apiKey: 'api-key',
    gzipContents: true,
  }),
],

@eskirk

@ambershi1 in order to be able diagnose this issue I will need to know how you initialize the Faro web SDK.


[Plugins] add a test_plugin.html which would allow testing the plugins API

these files should not be packaged (when deploying to remix.ethereum.org)
<!DOCTYPE html>

<html>
	<head>
		<meta charset="utf-8">
		<!--
		The MIT License (MIT)

		Copyright (c) 2014, 2015, the individual contributors

		Permission is hereby granted, free of charge, to any person obtaining a copy
		of this software and associated documentation files (the "Software"), to deal
		in the Software without restriction, including without limitation the rights
		to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
		copies of the Software, and to permit persons to whom the Software is
		furnished to do so, subject to the following conditions:

		The above copyright notice and this permission notice shall be included in
		all copies or substantial portions of the Software.

		 IN NO EVENT SHALL THE
		AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
		LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
		OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
		THE SOFTWARE.
		-->
		<meta http-equiv="X-UA-Compatible" content="chrome=1">
		<title></title>
		<link rel="stylesheet" href="assets/css/pygment_trac.css">
		<link rel="stylesheet" href="assets/css/font-awesome.min.css">
		<script type="text/javascript" src="remix_plugin.js"></script>
		<meta name="viewport" content="width=device-width, initial-scale=1, user-scalable=no">
	</head>
	<body>
	</body>
</html>

and for remix_plugin.js
function receiveMessage(event) {
console.log('receiveMessage', event.data, event.source, event.origin)
}
window.addEventListener("message", receiveMessage, false)

I'm not completely sure I follow how this is supposed to work.
So wouldn't I need to load an iframe with a certain "remix plugin" (e.g. solium) and then add the receiveMessage event listener to that iframe to see if it is emitting the correct messages?

This page would be a fake plugin that we could use for testing.
We don't want to test particular plugin here, just the API

ah ok. I understand :-)
Ok this makes more sense, even though it would not ever reply anything to the remix-ide, right?

if we want to test plugin=>remix-ide communication , it will


Update latest release to v1.3.5

Also update the wget command to use the correct filename format
generated by the new GitHub Actions release step.
Signed-off-by: Phil Estes<EMAIL_ADDRESS>

You can verify that the release download page in the preview uses the artifact URLs directly from GitHub, so even with our change to 1.4.0 and above and 1.3.5 and above on the filename, the download links work properly across this transition. The canned "wget" command on the page is updated to the new format, as it will never show a command for the older releases now that our "latest" is past the changeover point.


Introduce spawnWithRetriesAndLogs and use in ADB

Description

This pull request addresses the issue described here: https://github.com/wix-private/mobile-guild/issues/192

In this pull request, I have introduced a new child-process spawning (not exec) function that interactively logs the child-process' outputs (stdout and stderr), which also supports retries.
In the process, I've refactored exec.js, which has become bloated, onto exec and spawn under a new subdirectory - childProcess/.
TODO:

[ ] Unit testing over spawn
[ ] Fix unit tests over ADB.
[ ] Unit test that verifies that tracking ID is coherent among usage of exec and spawn.
[ ] Inline todo's

For features/enhancements:

[ ] I have added/updated the relevant references in the documentation files.

For API changes:

[ ] I have made the necessary changes in the types index file.

@noomorph would love to get your early-bird insights on this.

Overall, looks OK, although the code cries for more refactoring. 😭 🙂

I was originally aiming for a single function that unifies the various spawn()'s and exec()'s, but merging both in amounted into a level of complexity I didn't think was actually worth it.
What did you have in mind?


Update builder.toml

This moves the Node.js buildpack to the last position in order.toml, which will prevent it from being used on apps that have a package.json but don't want to run the node buildpack (a very common case).

@jkutner I'm going to close this given that we removed the nodejs buildpack https://github.com/buildpack/samples/pull/24


Error installing package

When importing a package with github, I get two errors

I import the package through the package manager as it usually does, then I get two errors:

1. Library\PackageCache\dev.yarnspinner.unity@720b6c94da\Runtime\LineProviders\UnityLocalisedLineProvider.cs(330,105): error CS0117: 'UnityLocalisedLineProvider' does not contain a definition for 'stringsTable'
2. Library\PackageCache\dev.yarnspinner.unity@720b6c94da\Runtime\LineProviders\UnityLocalisedLineProvider.cs(331,103): error CS0117: 'UnityLocalisedLineProvider' does not contain a definition for 'assetTable'

Please tell us about your environment:

Yarn Spinner Version: latest
Unity Version: 2022.2.12f1, 2022.1.13f1, 2021.3.22f1

This was fixed with the 2.3.1 release. I am closing this issue for now but if the error reappears please open another.


When querying from a azure function using input binding, a query plan request is made that is not mapped

When creating a function app and a function with cosmosdb input binding and a sqlquery,
two post requests are made to "/dbs/:dbId/colls/:collId/docs", one of which has the "x-ms-cosmos-is-query-plan-request: True" header.
The Azure function expects a specific response from this request, after which the actual query request will be made.
The expected resposne looks like this:
{
    "partitionedQueryExecutionInfoVersion": "2",
    "queryInfo": {
        "distinctType": "None",
        "top": null,
        "offset": null,
        "limit": null,
        "orderBy": [],
        "orderByExpressions": [],
        "groupByExpressions": [],
        "groupByAliases": [],
        "aggregates": [],
        "groupByAliasToAggregateType": {},
        "rewrittenQuery": "",
        "hasSelectValue": false,
        "dCountInfo": null
    },
    "queryRanges": [
        {
            "min": "05C1A3C5D33F20083200",
            "max": "05C1A3C5D33F20083200",
            "isMinInclusive": true,
            "isMaxInclusive": true
        }
    ]
}

with attribute values depending on the specific query, for instance if "order by" is added, the attributes
orderBy and orderByExpressions will contain "Ascending/Descending" and the column names respectively

bump


Refactoring and Code improvements

…upgrading libraries
Purpose

Externalized the authentication configuration out from the authConfig.ts to config.json with an example config.example.json for reference.
Moved all *.jsx to *.tsx.
Added types to the *.tsx where applicable.
Upgraded libraries in the package.json
Updated the README.md to reflect the new changes.

Does this introduce a breaking change?
[ ] Yes
[ x] No

Pull Request Type
What kind of change does this Pull Request introduce?
[ ] Bugfix
[ ] Feature
[x] Code style update (formatting, local variables)
[x] Refactoring (no functional changes, no api changes)
[x] Documentation content changes
[ ] Other... Please describe:

How to Test

Get the code

git clone [repo-address]
cd [repo-name]
git checkout [branch-name]
npm install

Test the code

Follow instructions in the README.md for creating a src/config.json and updating it accordingly.
npm run start
Sign in and fetch the profile information.

What to Check
Verify that the following are valid

The functionality before and after this PR should be identical, no functional changes were introduced.

Other Information
The biggest change, beyond refactoring to tsx is externalizing the authentication config into a config.json

Hi @engineersamuel, thanks for taking time to improve our samples! Unfortunately this repo is used as a template by the Azure portal quickstart (and ms docs) so we refrain from making any changes to it if not absolutely needed as that requires some coordination. For anyone that needs an example in TypeScript, please see.


Wrong path in Makefile.windows.mk

Make for  Windows in Linux environment end with error, that it can not find the ZynAddSubFX.dll. The problem is there:
cp $(ZYNADDSUBFX_BUILD_DIR)/src/Plugin/ZynAddSubFX/ZynAddSubFX.dll $(ZYN_FUSION_OUT)/
Right path should be look like it:
cp $(ZYNADDSUBFX_BUILD_DIR)/src/Plugin/ZynAddSubFX/vst/ZynAddSubFX.dll $(ZYN_FUSION_OUT)/
Then a make finished successfully.

Likely a consequence of https://github.com/zynaddsubfx/zynaddsubfx/pull/151 . As you've mentioned it's a 4 character fix, so feel free to add a PR if you want to have the fix recorded in git history or I'll fix it in one of the periodic git issues sweeps and credit you for the find :)


[Gateway] : Dark and Light theme should be consistence across all the pages.

Issue Type

[x] bug report
[ ] feature request

Current Behavior

Dark Light them is not consistent across all page.
Expected Behavior

Dark and Light theme should be consistence across all the pages.
Steps to Reproduce

Suggested Fix

https://github.com/bobanetwork/boba/issues/377
duplicated


Play button for currently loaded project

Add a play button to the top to run the projects main.py file.
depends on #15

Dedicated start entries are placed in the title menu. Once there are more things for a toolbar to actually add one, this should be added there as well.


Temperature in integer

Hello, i would do that :
binary_sensor:
  - platform: template
    sensors:
      temp_zone_vie:
            unique_id: 4cbf0f03-2f7e-4697-ad20-098a1288f4c9
            friendly_name: "Zone Vie"
            device_class: temperature
            value_template:  "{{state_attr('climate.domicile_zone_vie', 'current_temperature')}}"

It work, but binary_sensor.temp_zone_vie make me a state with "." and no ",".
So i think, some trouble bring me bug.
Look history :

isn't a graph like this:

And, i can't try to use the stat in node red or other..
I think it's because the value uploaded by airzone need a new format !?

I'm not sure that is a bug... but you could try to apply
{{ states('binary_sensor. temp_zone_vie').replace(',','\.') }}

I try but it's break the entity:

You talk about what settings ? Aircloud or Home assistant ? Because Home assistant look like be good..

    temp_zone_vie:
      unique_id: 4cbf0f03-2f7e-4697-ad20-098a1288f4c9
      friendly_name: "Zone Vie"
      device_class: temperature
      value_template:  "{{state_attr('climate.domicile_zone_vie', 'current_temperature').replace(',','.')}}"

i think that replace doesn't works on state_attr, you need to creata another binary_sensor (ie: temp_zone_vie_wit_point)
something like
temp_zone_vie_wit_point:
      unique_id: 4cbf0f03-2f7e-4697-ad20-098a12s88f4c9
      device_class: temperature
      value_template:  "{{ states('binary_sensor.temp_zone_vie_wit_point').replace(',','\.') }}"

Hello,
Can you retry with the new version (v1.1.1) ?


Installation of macOS 13 Beta guest fails on macOS 12.4 host

The error is "Internal Virtualization Error. Installation Failed."
When attempting to create the VM, I chose "Virtualize", then "macOS 12+". I imported the IPSW file "UniversalMac_13.0_22A5266r_Restore.ipsw", which I'd downloaded from https://developer.apple.com. I left all the other settings at their defaults. The failure happened at the beginning of the installation -- while the meter still read "Installation: 0%". I did this on UTM 3.2.4, downloaded from https://mac.getutm.app/.
The same procedure works fine on a host running macOS 13.0 Beta build 22A5266r, also using UTM 3.2.4.
I assume this is Apple's fault. But I wanted to report it for the record.

Oops. This seems to be a dup of https://github.com/utmapp/UTM/issues/4099.


[Bug]: CRASH strange

All of the following criteria must be met

[X] All Requirements must be installed.
[ ] Full Latest.log file included. If no file exists then leave this unchecked and state so.

All of the following are optional to answer

[X] Tried reinstalling the Game.
[X] Tried reinstalling MelonLoader.
[ ] Tried restarting PC.
[X] Was able to see the Start Screen.

Describe the issue.

MelonLoader_23-01-07_20-22-51.449.log
Did you attach your log file?

[X] Yes, I attached my log file to the text box above.
[ ] No, I could not find a log file at {Game_Directory}\MelonLoader\Latest.log

the game crash after this line

Fixed in 0.6.0 alpha. Enable alpha in the installer settings.


Add clang support

Add support for clang and provide wrappers + to use it as a "drop-in" replacement for gcc.
The clang-class could be used to set CC and CXX to the clang wrappers so that the remaining recipe could stay untouched.
By adding clang to cpackage it becomes the default compiler, but since there are many autotools-based packages not compiling with clang I disabled clang within the autotools class. So only cmake and meson packages are using clang.
I haven't compiled all packages with clang so this might break some packages. But at least for the packages we're using it works this way. As an alternative it would be also possible to selectively enable clang for packages where it has been tested. :shrug:
:warning: devel::clang compile time is ~1h on my core ultra 5 using 10 cores...
There is one known issue I couldn't solve - it doesn't compile outside the sandbox:
[186/204] Linking CXX executable bin/llvm-min-tblgen
FAILED: bin/llvm-min-tblgen
[...]
x86_64-bob_compat-linux-gnu/bin/ld: /usr/lib/libzstd.so: unknown type [0x13] section `.relr.dyn'

I guess this is because the host-compat-gcc is too old to work on my (arch-based) system...

Depends on https://github.com/BobBuildTool/basement/pull/232 ...

Thanks a lot! :tada:  I'll have a look in the next days.

There is one known issue I couldn't solve - it doesn't compile outside the sandbox:
[186/204] Linking CXX executable bin/llvm-min-tblgen
FAILED: bin/llvm-min-tblgen
[...]
x86_64-bob_compat-linux-gnu/bin/ld: /usr/lib/libzstd.so: unknown type [0x13] section `.relr.dyn'

Looks like it is using the wrong library. The compat-toolchain is a cross-compiling toolchain! That should never use libraries from the host.
(BTW, the CI build failed because Bob was not updated on ci.bobbuildtool.dev. I've fixed that.)

I added a small patch to work around the issue with the zstd lib. Looks like the cmake parameter is not passed to the native configuration when cross compiling and a shared zstd is the default...

I'm still rebasing our ~4 years old basement to the upstream basement / basement-gnu-linux. Turns out building the latest mesa3d  for intel requires llvm-libs + (ocaml) bindings as well. I'm in progress of reworking this...

Thanks. That is very much appreciated!
I'm still pondering about how we should exactly integrate clang support. I think there are two use cases:

The user might want to compile selected packages with clang for whatever reason. This might be its own software packages that need clang or because certain clang features are needed. In the end, clang is just a replacement for gcc and the recipes should better not need to care.
A package actually requires clang for compilation. Not sure if such packages exist.

I would consider the need for LLVM to be somewhat independent of this. Clang is really the C/C++ compiler frontend for LLVM and serves as a drop-in replacement for gcc. Packages that need LLVM can still be compiled with gcc, they just need the tooling and/or the library. AFAICT rust bindgen is such an example too.
Then there is also lld as a replacement of the GNU linker. Not sure if there is a use case for this but given the speed advantage, some people might want to give it a try.
But because there certainly are packages that cannot be compiled with clang, I would not make this a global decision. Instead, a project may enable clang for parts of the dependency tree. How to enable clang without modifying existing recipes is still something where I have no good idea to be honest.
BTW, there seems to be Yocto layer and there they seem to have a rather large blacklist of incompatible packages. Additionally, the layer seems to modify many other recipes.

ATM we only have use-case 1, but with some additional requirements. We're compiling our packages with both, gcc and clang to get different warnings or errors. We're also using different version to check if it breaks with an older version and so on. Obviously we don't want to edit the recipe to switch between clang and gcc. This is done in the clang-class either setting CC and CXX to clang or gcc.
We're not using lld or the libcxx and I'd leave this open for now. The mesa stuff seams to require llvm-libs, llvm-libclc,  llvm-ocaml-bindings and all the dependencies. Unfortunately I don't have access to my changes before 2nd week of January due to some technical issues.
For me it would be also fine to upstream only the llvm-recipe (I think it should go to libs/llvm.yaml(?), and maybe also to basement-gnu-linux (??)) and a clang-support class. This way we would simply add clang to the packages we want to build with clang and no other upstream recipe would be touched.

Having support for clang in basement totally makes sense. It's just a question how it is done exactly.
The BASEMENT_HAS_CLANG variable does not look right, though. It will cause all packages to be rebuilt even if USE_CLANG is not set. Intuitively, I thought something CPACKAGE_USE_CLANG could be used instead. If set, the clang tool is added to buildTools and the package is built with clang. But this still feels like it does not give enough control because it will apply for a whole dependency tree. Right now I don't have a better solution, though.
The recipe itself could be named recipes/devel/llvm.yaml. Clang would be something like devel::llvm-clang and libclc devel::llvm-libclc. I know the naming is suboptimal for packages that provide tools and libraries from the same source package so there is no good rule how to name such packages.


Linking User Accounts

Hey,
is it possible with dex to link user accounts from different connectors ?
e.g. user logs in with GitHub or LinkedIn and results as the same User Account in the Web-App.
Auth0 does this and I think its pretty neat: https://auth0.com/docs/link-accounts

This requires more state and user management facilities then we're likely to add at this time. If you would like to do this consider doing the linking in whatever app is using dex to authenticate users.


Add option to include the syntax source in the SVG metadata

Using the xml source as a feature in the SVG format can be very useful to include metadata in the generated file.
One awesome thing js-sequence-diagrams does, is including a <source> tag with a CDATA value when you download the SVG file and make it possible/easier for future editions in the generated diagram by someone else besides the author.

Thanks!
A good idea!

Given how long ago this issue's activity died out, I'm closing it.
This allows us to maintain a fresh list of issues the community is interested in.


ctrl+` has to be pressed twice when terminal is not in foucs

VSCode Version: 1.35.0-insider
OS Version: Windows 10

Steps to Reproduce:

Open file
Open terminal using ctrl+`
Click on the file
Attempt to close terminal using ctrl+`. It will not close.

If the terminal is in focus, pressing ctrl+` works fine to show/hide the terminal. If the terminal is not in focus, you have to hit ctrl+` twice and then it will hide (showing still only requires a single press).
The action should be consistent regardless of whether or not the terminal is in focus, especially since it is not easy to see if the terminal is in focus or not, so you don't know how many times you will need to hit ctrl+`.

Try this keybinding
{ "key": "ctrl+`",           "command": "workbench.action.terminal.focus", "when": "!terminalFocus" },


@sha256@sha256 strikes again! (on <IP_ADDRESS>)

[//]: # kind bug
And in case Prow notices:
/kind bug
Description
As seen back in #877, but now on <IP_ADDRESS>.
Steps to reproduce the issue:
I haven't worked out a minimal reproducer yet, but we've had a number of folks using this script (openshift/installer#933) see:
$ sudo podman inspect quay.io/openshift-release-dev/ocp-release:4.0.0-8 -f '{{ index .RepoDigests 0 }}'
quay.io/openshift-release-dev/ocp-release@sha256@sha256:2390e665f4b3a2a12c2e676e7a75af6ff74f66e57242ab2f2e58b9d8e6837777

Describe the results you expected:
I expected the RepoDigests entry to only contain a single @sha256.
Additional information you deem important (e.g. issue happens only occasionally):
Some OpenShift Installer runs do not see this problem, but some (using the same podman and update payload image) do.  Runs that see it once can reproduce it reliably.  So there's some way to stumble into the broken state, and once you do you stay there.  But there's also a way to avoid the broken state.
Output of podman version:
@robszumski was kind enough to work through all of this, and he had:
$ podman version
Version:       <IP_ADDRESS>
Go Version:    go1.10.2
OS/Arch:       linux/amd64
$ podman info
host:
  BuildahVersion: 1.5-dev
  Conmon:
    package: podman-<IP_ADDRESS>-3.git594495d.el7.x86_64
    path: /usr/libexec/podman/conmon
    version: 'conmon version 1.12.0-dev, commit: ce5c8112ef76bda67e00829952505aa447b343c1-dirty'
  Distribution:
    distribution: '"rhcos"'
    version: "4.0"
  MemFree:<PHONE_NUMBER>
  MemTotal:<PHONE_NUMBER>
  OCIRuntime:
    package: runc-1.0.0-57.dev.git2abd837.el7.x86_64
    path: /usr/bin/runc
    version: 'runc version spec: 1.0.0'
  SwapFree: 0
  SwapTotal: 0
  arch: amd64
  cpus: 2
  hostname: ip-10-0-6-138
  kernel: 3.10.0-957.1.3.el7.x86_64
  os: linux
  rootless: false
  uptime: 2h 8m 39.48s (Approximately 0.08 days)
insecure registries:
  registries: []
registries:
  registries:
  - registry.access.redhat.com
  - docker.io
  - registry.fedoraproject.org
  - quay.io
  - registry.centos.org
store:
  ContainerStore:
    number: 5
  GraphDriverName: overlay
  GraphOptions:
  - overlay.override_kernel_check=true
  GraphRoot: /var/lib/containers/storage
  GraphStatus:
    Backing Filesystem: xfs
    Native Overlay Diff: "true"
    Supports d_type: "true"
  ImageStore:
    number: 14
  RunRoot: /var/run/containers/storage

Additional environment details (AWS, VirtualBox, physical, etc.):
AWS.  Using:
$ cat /etc/os-release
NAME="Red Hat CoreOS"
VERSION="4.0"
ID="rhcos"
ID_LIKE="rhel fedora"
VERSION_ID="4.0"
PRETTY_NAME="Red Hat CoreOS 4.0"
ANSI_COLOR="0;31"
HOME_URL="https://www.redhat.com/"
BUG_REPORT_URL="https://bugzilla.redhat.com/"
REDHAT_BUGZILLA_PRODUCT="Red Hat 7"
REDHAT_BUGZILLA_PRODUCT_VERSION="4.0"
REDHAT_SUPPORT_PRODUCT="Red Hat"
REDHAT_SUPPORT_PRODUCT_VERSION="4.0"
OSTREE_VERSION=47.235

as installed by the v0.8.0 installer.  From the broken state:
$ sudo podman inspect quay.io/openshift-release-dev/ocp-release:4.0.0-8
[
   {
       "Id": "e3cd6917002af26debf8052e7f1d95ef7ed912111593248cff8de9ca076569e8",
       "Digest": "sha256:2390e665f4b3a2a12c2e676e7a75af6ff74f66e57242ab2f2e58b9d8e6837777",
       "RepoTags": [
           "quay.io/openshift-release-dev/ocp-release@sha256:2390e665f4b3a2a12c2e676e7a75af6ff74f66e57242ab2f2e58b9d8e6837777",
           "quay.io/openshift-release-dev/ocp-release:4.0.0-8"
       ],
       "RepoDigests": [
           "quay.io/openshift-release-dev/ocp-release@sha256@sha256:2390e665f4b3a2a12c2e676e7a75af6ff74f66e57242ab2f2e58b9d8e6837777",
           "quay.io/openshift-release-dev/ocp-release@sha256:2390e665f4b3a2a12c2e676e7a75af6ff74f66e57242ab2f2e58b9d8e6837777"
       ],
       "Parent": "",
       "Comment": "Release image for OpenShift",
       "Created": "2018-12-22T22:18:35.744591Z",
       "ContainerConfig": {
           "Env": [
               "OPENSHIFT_BUILD_NAME=cluster-version-operator",
               "OPENSHIFT_BUILD_NAMESPACE=ci-op-zlhfgrm2",
               "PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"
           ],
           "Entrypoint": [
               "/usr/bin/cluster-version-operator"
           ],
           "Labels": {
               "io.openshift.release": "4.0.0-8",
               "io.openshift.release.base-image-digest": "sha256:57ea7826cf3c73d2dd29dfff375f5c09da087cb0e6a72b998bb74a9d18adeaa7"
           }
       },
       "Version": "1.13.1",
       "Author": "",
       "Architecture": "amd64",
       "Os": "linux",
       "Size": 291664680,
       "VirtualSize": 291664680,
       "GraphDriver": {
           "Name": "overlay",
           "Data": {
               "LowerDir": "/var/lib/containers/storage/overlay/57266b1eabbfe64e1c3330b16f0534b77c76af1ba2e28d69ecbc59779785dd1d/diff:/var/lib/containers/storage/overlay/ccbac139cf89893ed2760507dc7f3e19210593e72a9a2d8f05c486e0bb77e7a6/diff:/var/lib/containers/storage/overlay/071d8bd765171080d01682844524be57ac9883e53079b6ac66707e192ea25956/diff",
               "MergedDir": "/var/lib/containers/storage/overlay/5c857d77af584de126b963367139d6546cbfe34208c92cbeee967e2ceaaaee10/merged",
               "UpperDir": "/var/lib/containers/storage/overlay/5c857d77af584de126b963367139d6546cbfe34208c92cbeee967e2ceaaaee10/diff",
               "WorkDir": "/var/lib/containers/storage/overlay/5c857d77af584de126b963367139d6546cbfe34208c92cbeee967e2ceaaaee10/work"
           }
       },
       "RootFS": {
           "Type": "layers",
           "Layers": [
               "",
               "",
               "",
               ""
           ]
       },
       "Labels": {
           "io.openshift.release": "4.0.0-8",
           "io.openshift.release.base-image-digest": "sha256:57ea7826cf3c73d2dd29dfff375f5c09da087cb0e6a72b998bb74a9d18adeaa7"
       },
       "Annotations": {},
       "ManifestType": "application/vnd.docker.distribution.manifest.v1+prettyjws",
       "User": ""
   }
]

Comparing that with a local:
$ podman pull quay.io/openshift-release-dev/ocp-release:4.0.0-8
$ podman inspect quay.io/openshift-release-dev/ocp-release:4.0.0-8

yielded:
--- good
+++ broken
@@ -3,9 +3,11 @@
        "Id": "e3cd6917002af26debf8052e7f1d95ef7ed912111593248cff8de9ca076569e8",
        "Digest": "sha256:2390e665f4b3a2a12c2e676e7a75af6ff74f66e57242ab2f2e58b9d8e6837777",
        "RepoTags": [
+            "quay.io/openshift-release-dev/ocp-release@sha256:2390e665f4b3a2a12c2e676e7a75af6ff74f66e57242ab2f2e58b9d8e6837777",
            "quay.io/openshift-release-dev/ocp-release:4.0.0-8"
        ],
        "RepoDigests": [
+            "quay.io/openshift-release-dev/ocp-release@sha256@sha256:2390e665f4b3a2a12c2e676e7a75af6ff74f66e57242ab2f2e58b9d8e6837777",
            "quay.io/openshift-release-dev/ocp-release@sha256:2390e665f4b3a2a12c2e676e7a75af6ff74f66e57242ab2f2e58b9d8e6837777"
        ],
        "Parent": "",

With the same podman, pulling a fresh, similar image (-7) avoided the broken state:
$ podman pull quay.io/openshift-release-dev/ocp-release:4.0.0-7
$ podman inspect quay.io/openshift-release-dev/ocp-release:4.0.0-7
[
    {
        "Id": "72d96fea0c4fbcc527f509963c11b7c9c9b0bf9ba5641cd18968eb9150f54464",
        "Digest": "sha256:3e70b2d2004c9335dabc24d6259c5b03739fd86eae435c191ee2b8592e86efec",
        "RepoTags": [
            "quay.io/openshift-release-dev/ocp-release:4.0.0-7"
        ],
        "RepoDigests": [
            "quay.io/openshift-release-dev/ocp-release@sha256:3e70b2d2004c9335dabc24d6259c5b03739fd86eae435c191ee2b8592e86efec"
        ],
        "Parent": "",
        "Comment": "Release image for OpenShift",
        "Created": "2018-12-15T06:41:33.392131088Z",
        "ContainerConfig": {
            "Env": [
                "OPENSHIFT_BUILD_NAME=cluster-version-operator",
                "OPENSHIFT_BUILD_NAMESPACE=ci-op-40fz390h",
                "PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"
            ],
            "Entrypoint": [
                "/usr/bin/cluster-version-operator"
            ],
            "Labels": {
                "io.openshift.release": "4.0.0-7",
                "io.openshift.release.base-image-digest": "sha256:f9585cce1889d934b6f9c8361bb1fcc532235ddc4b88ab8614be40545e6bf5d8"
            }
        },
        "Version": "1.13.1",
        "Author": "",
        "Architecture": "amd64",
        "Os": "linux",
        "Size": 292396852,
        "VirtualSize": 292396852,
        "GraphDriver": {
            "Name": "overlay",
            "Data": {
                "LowerDir": "/var/lib/containers/storage/overlay/639b39d8f4d99083f7276b1915cc51b4c24db7e7e5cb9a0817e8b414843b105a/diff:/var/lib/containers/storage/overlay/eb0c639d1332b895a66623afad255f15d2ac507a51f4d54a8604d292660a7d45/diff:/var/lib/containers/storage/overlay/071d8bd765171080d01682844524be57ac9883e53079b6ac66707e192ea25956/diff",
                "MergedDir": "/var/lib/containers/storage/overlay/7ce4431b6f986e887ce043bab47c2e36838e460a3fa2ea7353ad5a30f85fe7c7/merged",
                "UpperDir": "/var/lib/containers/storage/overlay/7ce4431b6f986e887ce043bab47c2e36838e460a3fa2ea7353ad5a30f85fe7c7/diff",
                "WorkDir": "/var/lib/containers/storage/overlay/7ce4431b6f986e887ce043bab47c2e36838e460a3fa2ea7353ad5a30f85fe7c7/work"
            }
        },
        "RootFS": {
            "Type": "layers",
            "Layers": [
                "",
                "",
                "",
                ""
            ]
        },
        "Labels": {
            "io.openshift.release": "4.0.0-7",
            "io.openshift.release.base-image-digest": "sha256:f9585cce1889d934b6f9c8361bb1fcc532235ddc4b88ab8614be40545e6bf5d8"
        },
        "Annotations": {},
        "ManifestType": "application/vnd.docker.distribution.manifest.v1+prettyjws",
        "User": ""
    }
]

Also in this space is #1139, but I don't understand RepoDigests generation well enough to know if this is a dup of that issue or not.

The SHA256s seem to match here, where they did not in #877 - which seems to indicate we're pulling the right image, which is good.
This could just be a display issue (or we could be setting a nonsensical name when we save the image)


Markdown Preview Inconsistent Colors for C# Code Block

Issue Type: Bug
Steps:

Open new document, set language to Markdown, open preview
Type a C# code block containing a mix of types, fields, and reserved words

Example code block:
class MyClass
{
    int MyInt;
    MyOtherClass MyProperty;
}

Actual results:
The reserved words class and int are rendered in different colors, blue and green, respectively. Types are rendered in white, which is also used for members.
Expected results:
Reserved words should be rendered in a consistent color. Ideally types should be rendered in a different color than members, especially since the syntax coloration in the markdown file itself does, though I suppose it's at least not inconsistent to use white for both.
 Extensions can provide alternative highlighting, such as https://marketplace.visualstudio.com/items?itemName=bierner.markdown-shiki


Send attachments

Hi,
Is there any way to send an attachment to a channel/DM ?
That should be a great thing to send some media content.

@Huljo there absolutely is a way to do that.  just add an attachment object on the message object.
So something like
msg.attachments = [
    {
      title: "text",
      title_link: "https://link",
      text: "Rocket.Chat, the best open source chat",
      image_url: "https://rocket.chat/images/mockup.png",
      color: "#764FA5"
    }
];

Other properties available like:

title_link_download: true
image_url
image_type
image_size
image_dimensions
audio_url
audio_type
audio_size
video_url
video_type
video_size

Thank you @geekgonecrazy, I'll have a try.

@geekgonecrazy hello, could you please explain where I should add message object

for future googlers, here is an example:
`module.exports = function(robot) {
var msg = {};
msg.attachments = [
	{
		title: "text",
		title_link: "https://link",
		text: "Rocket.Chat, the best open source chat",
		image_url: "https://rocket.chat/images/mockup.png",
		color: "#764FA5"
	}
];

robot.messageRoom("general", msg);

};`

@fedevegili do you have a script example (js or coffescript)? I try to integrate with my examples but the hubot container return error and not stop it.
Thank you!

Can we open these links in the hubot like webview rather than opening in next tab or browser?


[Unexpected Behavior] "Double" default style when 2 people are present

What you're using
Default theme for SM5.3. Started game with 2 players.
"Double" is the default selected option, despite it being a 1-player option.
Expected behavior
"Versus" should be the default selected option, because it is the first 2-player option.

This issue is a duplicate of #47 .


Use Pytest for all tests

We would like to have all our tests use pytest, rather than some using unittest.
Context
Most other repos use pytest, so would nice to be consistent.
Possible Implementation
Replace the unittest framework in the tests with pytest

@jacobbieker, Can I be assign to this issue?

Yes!

can i get your insights what is done and what is needed to be done? @norbline

@vikasgrewal16 I think @norbline has it going so far, if you want to take #231 that would be great!

Thanks @jacobbieker I have been working on #231 and will get to you as soon as possible


Make python version metadata a comma separated list

In #480 we introduced the plugin metadata links to the plugin page and also updated the Python versions metadata to show all supported Python versions. Since this list will get long with later versions of Python, we should eventually make this into a comma separate listed like the file extensions metadata.

This is a good point, although we might also be able to simplify this if the napari project explicitly deprecates older versions of Python, as numpy does (and recommends that the broader scientific Python community does as well).

For example, the latest version of napari is only tested against 3.8, 3.9, and 3.10: https://github.com/napari/napari/blob/main/.github/workflows/test_pull_requests.yml#L54

And support for 3.7 was explicitly dropped in the last release: https://github.com/napari/napari/releases/tag/v0.4.15


Roll engine e3e4b26fce0d..f336286cde9c (3 commits)

https://github.com/flutter/engine/compare/e3e4b26fce0d...f336286cde9c
git log e3e4b26fce0de9d4aa870835ffad24e6817a08ce..f336286cde9c17d4aa36e3217f91cc0b239a3391 --no-merges --oneline
f336286cd Roll src/third_party/skia 947efe28de74..08ba11370342 (9 commits) (flutter/engine#9865)
dcac8a9c9 Fixed error in generated xml Info.plist. (flutter/engine#9867)
b7e5940e3  Started adding the engine hash to frameworks' Info.plist. (flutter/engine#9847)
The AutoRoll server is located here: https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md
If the roll is causing failures, please contact the current sheriff (aaclarke@google.com), and stop
the roller if necessary.

Auto-roller completed checks. About to merge.


🐛: When a simulation is running on run.biosimulations.org the web site claims constant failures

Contact Details
No response
Location
BioSimulations
What happened?
Reported by @luciansmith
While a simulation is running (see https://run.biosimulations.org/runs/66f1aa621f1841b171a08d2d below), we get constant windows popping up every five seconds that say "Something went wrong! We're sorry! Please try again later. If this error persists, please submit an issue or contact us at<EMAIL_ADDRESS>This happens regardless of whether something went wrong or not.
(Something did indeed go wrong with that particular run; it seems to be stuck at the 'Created' phase. But that just makes it a nice URL to use as an example; running anything will show the problem.)
What made it happen?
submit a simulation and monitor status
Version
Production (Deployed on a .org domain)
What browsers are you seeing the problem on?
No response
Relevant log output
"Something went wrong!"

We're sorry! Please try again later.  If theis error persists, please submit an issue or contact us...

"Something went wrong!"

We're sorry! Please try again later.  If theis error persists, please submit an issue or contact us...

Code of Conduct

[X] I agree to follow this project's Code of Conduct

@luciansmith I moved your issue from biosimulators/biosimulators repo, see https://github.com/biosimulators/Biosimulators/issues/697


add clarity in man/docker-build

add clarity/fix typos man/docker-build
add needed clarity for

using STDIN to pass build context
--cpu-shares flag use

also a few typos, final arguments needed in examples '.'
Again, thanks Robert P.J.Day for finding these.
Signed-off-by: Sally O'Malley<EMAIL_ADDRESS>

Thanks @sallyom, looking good, but found two issues

Thanks @sallyom, much appreciated again!
LGTM

ping @fredlf @jamtur01 @moxiegirl @SvenDowideit

Minor comment otherwise LGTM

@thaJeztah , it's np, I seriously love my job...

LGTM \o/


e.g. barcode.default_writer_options['quiet_zone'] = 10 isn´t working properly

Hello,
I´m trying to set the quiet_zone very low. e.g. 0.6.
I fixed the order in the base.py render function:
Line 105 and 106:
Removed this:
options = Barcode.default_writer_options.copy()
options.update(writer_options or {})
Instead I added this:
writer_options.update(Barcode.default_writer_options)
options = writer_options.copy()
Now its working.  I´m new to github. Dont know how to make a pull request

hi, which area is the quiet_zone


Allow paths as suffixes for broker request URLs

Goal
We have several scenarios where brokers need to be exposed from endpoints that are not just a base hostname/port pair, but also contain path elements. We would like to be able to expose the broker API endpoints as path suffixes on an existing base path, and include the path as part of the broker URL when registering it with the platform.
Current model
Currently brokers must be registered as root hosts, e.g.,
Broker: http://mybroker.mycompany.com:8080
Username: me
Password: supersecret

Calls must always be made to broker spec paths as the root path, e.g., http://mybroker.mycompany.com:8080/v2/catalog. This is because they are specified in the spec as HTTP calls like GET /v2/catalog.
Proposed change
We would like to be able to register brokers including a base path, such as
Broker: http://mybroker.mycompany.com:8080/some/base/path
Username: me
Password: supersecret

Broker spec paths are then appended to whatever broker URI has been registered, e.g., http://mybroker.mycompany.com:8080/some/base/path/v2/catalog.

Worth noting that I believe this is already achievable in Kubernetes service-catalog because you submit a base URL for each broker, which may include a path.

Yes you are correct, each broker path is a format string prefixed by the provided broker URL.

Agreed

This is also possible today in Cloud Foundry. Like Kubernetes service-catalog, you can just submit a base URL for each broker which may include a path.
Is there somewhere in the spec that needs updating to make this clear?

The spec is defined as raw HTTP calls for each method, e.g.,
GET /v2/catalog
PUT /v2/service_instances/:instance_id

However! I just happened upon this section from the spec, and perhaps is sufficient for my request.

A platform marketplace may expose services from one or many service brokers, and an individual service broker may support one or many platform marketplaces using different URL prefixes and credentials.

So the main question is: is the intention to allow prefix URLs as part of the spec? And is the section I quoted intended to convey that?

I am actually going to reopen this. It would be good to have this be more explicit in the spec to specify that path prefixing is required by the platform.
I am happy to draft this change.

@bmelville yes, I think it is worth clarifying that API paths can be prefixed. Can you explain the problem that having a base path solves for you?
I think the design problem of supporting multiple platforms from multiple vendors is one we could provide guidance/patterns for.

A concrete use-case is a broker which exposes a different catalog of managed services based on the path. For example, broker.foo.com/catalog1/v2/catalog and broker.foo.com/catalog2/v2/catalog expose different catalogs of services, and are thus managed as logically separate brokers.
This is slightly different from a single broker supporting multiple platforms, and I might call it more of a "multi-tenant" broker platform.

@bmelville I agree that it would be better to have this more explicitly stated in the spec. Do you want to have a go at drafting the change?

Yes I plan to give it some thought and hopefully have a PR for review this week!

I believe this is resolved by this line in the spec:
A Platform MAY expose services from one or many Service Brokers, and an individual Service Broker MAY support one or many Platforms using different URL prefixes and credentials.

Closing!


Replace heavy mathjs dependency with a lighter one

Removed MathJS to make the package lighter

I completely understand the need  for a smaller math parser - it is large.
However I'm also not overly keen on moving to something with a different syntax - With expr-eval it seems that you have to create a Parser object for each use, then evaluate it separaretly.
That's not to say I'm completely averse to it.
I'm wondering if it may be better to use the reduced version of MathJS (https://github.com/josdejong/mathjs-expression-parser), which would keep the syntax the same and only mean a change in the NPM include.
Also, looking at the package sizes, it looks like reduced MathJS (41kb) is smaller that expr-eval (68kb).

Does expr-eval provide any benefits over the reduced MathJS package?

I don't think so, I just wanted something similar to eval to remplace MathJS so the package is lighter. Though I think it's a good idea to add a reduced version of MathJS to make it lighter.

I've created another pull request (#87) which uses the reduced version of MathJS, to keep the syntax consistent.
Although it wasn't used, thank you for your contribution. It's really appreciated.

Just to let you know, I've released a patch version that uses the reduced size version of MathJS, which halves the package size<EMAIL_ADDRESS>There's still some bundle size changes I want to make, but it's difficult at the moment when I'm having to bundle UMD files for nodeJS. Once NodeJS fully supports ES imports then I can scrap those, which will reduce the filesize even more.


Separate Accounts guidance

This guidance all the sudden is only talking about on-premises AD DS. We also need separate accounts (cloud-only dedicated accounts) for cloud admin roles.

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

ID: 16b5dc24-f7bb-2112-6195-10715ef4f179
Version Independent ID: 0530498b-874c-377a-f268-903b46d55216
Content: Security rapid modernization plan
Content Source: articles/active-directory/fundamentals/security/security-rapid-modernization-plan.md
Service: active-directory
Sub-service: ****
GitHub Login: @MicrosoftGuyJFlo
Microsoft Alias: joflore

@sailando
Thanks for your feedback! We will investigate and update as appropriate.


Add clone_cube

Suggestion from @claxn:

Moreover, a function clone_raster_cube (i.e. copying all properties from a raster cube and creating an empty one) could be helpful in case a user only has to change one property instead of specifying all spatial attributes.

Does that sound helpful to everybody? I assume the values would all be set to no data (null)?
Could be someting like:
clone_cube(raster_cube cube, ?boolean clone_values = false) : raster_cube
clone values = false => Set all values to null (no data)
clone values = true => Copy also the pixel values

Sounds good! I am not sure what a user could do with an empty, cloned data cube except requesting its properties or using it in other functions such as warp. Are there any restrictions that a data cube has to be depictable (one can visualise it on a map)? If yes, then the above notation suits well. If no, we could save some time and only copy its properties. Nevertheless, I would prefer your definition and the output, since the data cube then preserves the bands and the temporal dimension and will be easier to handle.

Yes, we agreed here after some discussion that we would need to define additional processes that allow changing the data cube, e.g. properties, dimension values etc. But currently we don't have such processes and so we had no ideas for use cases we could need this for. There are probably some use cases, so I'd leave this issue open to be solved later once we also define the mentioned processes that work on properties, dimension values etc.

Currently what one would need to do is call a resample_xxx with a source datacube and target cube parameters, rather than a parameterized target cube (which we can't construct freely).

Telco: We don't have a use case for it at the moment.


Fix issue 179

https://github.com/voxpupuli/puppet-iis/issues/179
Fixes issue 179 where a system assembly was not loaded for 4 different actions within manage_app_pool.
Testing was done on Windows Server 2012R2 and Powershell 5.0

Thanks for the PR @dzeleski!

No problem! @bastelfreak


Default Config file for packaged install incorrect

The docs say that the default config directory is:
/usr/local/etc/arangodb/arangod.conf

However, having installed from the downloadable .rpm from the downloads page (for RHEL 6), the directory does not exist.
Actually, none of the stated default install directories exist.

Yes, you are right. This directory is valid for MacOSX, but not valid. Need to update the documentation.

Thanks Frank! I think I've found that it's /etc/arangodb.  Quick Question, what's the difference between arangob.conf and arangod.conf?
If I start with /etc/init.d/arangodb start, will it use any configs specified in /etc/arangob.conf, and the other conf is for when arango is run as a daemon?

The config files correspond to the executables:

arangod: the database server
arangob: a benchmark tool
arangosh: the shell
...

/etc/init.d/arangodb will start the server arangod, therefore it will only use arangod.conf. Independent of the daemon mode: arangod will always use arangod.conf.

gotcha. Thanks!

I want to move arangodb databases (system & userdbs) from default location to another drive/folder. Tried moving database folders and changing 2 pointers in arangod.conf.  Appears to work for system database but can no longer see user databases.  Am I missing something?


Blocks

We are excited in introducing a powerful feature in spurtcms admin the concept of blocks. These are modular units which allow flexibility in website creation blocks can be arranged and positioned within different regions of page layout. This allows flexibility and dynamic customization of pages.

Where should I create blocks in the SpurtCMS admin panel to make use of the new feature effectively?

Please follow the below steps to start with block create
Steps:-
step 1 : login into admin spurt_cms
step 2 :Go to Blocks tab
step 3 : Now Explore your blocks feature

The blocks feature in Spurt CMS is quite impressive. It works seamlessly and provides a dynamic way to manage and customize content. The interface is user-friendly, making it easy to explore and utilize the blocks effectively. Overall, it's a great feature that enhances content management with efficiency and flexibility.


set up javascript animation

This solves #229 by setting up jshtml for the animation output, which will not require ffmpeg to run nor Pillow as an example dependency.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 75.78%. Comparing base (32132b1) to head (f7d217f).
Report is 284 commits behind head on development.

:exclamation:  There is a different number of reports uploaded between BASE (32132b1) and HEAD (f7d217f). Click for more details.
HEAD has 8 uploads less than BASE

Flag
BASE (32132b1)
HEAD (f7d217f)

9
1

Additional details and impacted files
@@               Coverage Diff                @@
##           development     #230       +/-   ##
================================================
- Coverage        97.30%   75.78%   -21.52%
================================================
  Files               18       24        +6
  Lines             1669     2358      +689
================================================
+ Hits              1624     1787      +163
- Misses              45      571      +526

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

ERROR   -  Here is a summary of the problems encountered when running the examples

           Unexpected failing examples:
           /mnt/home/svenditto/GitHub/nemos/docs/tutorials/plot_02_head_direction.py failed leaving traceback:
           Traceback (most recent call last):
             File "/mnt/home/svenditto/GitHub/nemos/docs/tutorials/plot_02_head_direction.py", line 185, in <module>
               doc_plots.run_animation(neuron_count, epoch_one_spk.start[0])
             File "/mnt/home/svenditto/GitHub/nemos/src/nemos/_documentation_utils/plotting.py", line 506, in run_animation
               return HTML(anim.to_html5_video())
             File "/mnt/home/svenditto/python_venvs/nemos/lib/python3.10/site-packages/matplotlib/animation.py", line 1265, in to_html5_video
               Writer = writers[mpl.rcParams['animation.writer']]
             File "/mnt/home/svenditto/python_venvs/nemos/lib/python3.10/site-packages/matplotlib/animation.py", line 128, in __getitem__
               raise RuntimeError(f"Requested MovieWriter ({name}) not available")
           RuntimeError: Requested MovieWriter (ffmpeg) not available

Still requiring ffmpeg on a fresh build

Oh I think this may be fault (since I think I wrote the animation code in _documentation_utils/plotting.py. Hold up, let me see if I can fix it.

@sjvenditto try it now

This works now!


onSelectionChange on <Tab> component is triggered by nested tabs

Provide a general summary of the issue here
When there is a nested <Tab> component inside another <Tab> component, the selection change event is triggered by any of the nested tabs. This can cause an infinite render loop when the tab is controlled and the nested tab is the default one that is selected because onSelectionChange is triggered alternatively by the parent and the child <Tab> component (see logs in Sandbox below)
🤔 Expected Behavior?
In my opinion, the event onSelectionChange on the parent should be triggered only if the selection of a parent tab changes
😯 Current Behavior
The event onSelectionChange on the parent is triggered also by the nested tabs components
💁 Possible Solution
No response
🔦 Context
No response
🖥 Steps to Reproduce
https://stackblitz.com/edit/stackblitz-starters-pu2gbh?devToolsHeight=33&file=src%2FApp.tsx
Version
react-aria-components 1.0.0-rc.0
What browsers are you seeing the problem on?
Chrome
If other, please specify.
No response
What operating system are you using?
Linux
🧢 Your Company/Team
No response
🕷 Tracking Issue
No response

Thanks for the issue!
I think our Collection implementation is rendering a little too far. We should probably make use of useShallowRender or something along those lines for the TabPanel so that the nested collection isn't rendered as part of the initial one.
https://github.com/search?q=repo%3Aadobe%2Freact-spectrum useShallowRender&type=code
I tried this out, and unfortunately it caused an issue with the order of react hooks being called, so it may require a bit more work.

+1 , started migrating to react aria at work & hit the first roadblock

Thanks @shivamtracxn for sharing a workaround. I found another one which is to ignore keys corresponding to nested tabs in onSelectionChange event. In pseudo code, it would be something like this:
if(key is from parentTab){
    doSomething()
} else {
    // ignore
}

@adauleuklaxoon Nice, For me there could be same keys in the nested tabs so couldn't use this
There is another sol. that i wont use but it is to set just the onSelectionChange as undefined in the Tabs slot, so it is not passed down

I found that the className is also shared between the parent and nested <Tabs /> components.
v1.0.0

This appears to be fixed in the latest release. https://stackblitz.com/edit/stackblitz-starters-7wjeh5?devToolsHeight=33&file=package.json,src%2FApp.tsx


Printers are already in sync; there are 0

I've read the entry in https://github.com/google/cloud-print-connector/wiki/Common-problems about the "Printers are already in sync; there are 0" message which I indeed see on my Raspberry PI (Linux pi1 4.9.35-v7+ #1014 SMP Fri Jun 30 14:47:43 BST 2017 armv7l GNU/Linux) every minute from my /tmp/cloud-print-connector log:
I [12/Feb/2018:04:44:37 +0000] Synchronizing printers, stand by
I [12/Feb/2018:04:44:37 +0000] Printers are already in sync; there are 0
I [12/Feb/2018:04:45:37 +0000] Synchronizing printers, stand by
I [12/Feb/2018:04:45:38 +0000] Printers are already in sync; there are 0
I [12/Feb/2018:04:46:38 +0000] Synchronizing printers, stand by
I [12/Feb/2018:04:46:38 +0000] Printers are already in sync; there are 0
I [12/Feb/2018:04:47:38 +0000] Synchronizing printers, stand by
I [12/Feb/2018:04:47:38 +0000] Printers are already in sync; there are 0

The associated entries in /var/log/cups/error_log have:
D [12/Feb/2018:04:47:38 +0000] [Client 19] Accepted from localhost (Domain)
D [12/Feb/2018:04:47:38 +0000] [Client 19] Waiting for request.

D [12/Feb/2018:04:47:38 +0000] [Client 19] OPTIONS * HTTP/1.1
D [12/Feb/2018:04:47:38 +0000] cupsdSetBusyState: newbusy="Active clients", busy="Not busy"
D [12/Feb/2018:04:47:38 +0000] [Client 19] No authentication data provided.
D [12/Feb/2018:04:47:38 +0000] [Client 19] Encrypting connection.
D [12/Feb/2018:04:47:38 +0000] Connection from localhost now encrypted.
D [12/Feb/2018:04:47:38 +0000] cupsdSetBusyState: newbusy="Not busy", busy="Active clients"
D [12/Feb/2018:04:47:38 +0000] cupsd is not idle any more, canceling shutdown.
D [12/Feb/2018:04:47:38 +0000] [Client 19] POST / HTTP/1.1
D [12/Feb/2018:04:47:38 +0000] cupsdSetBusyState: newbusy="Active clients", busy="Not busy"
D [12/Feb/2018:04:47:38 +0000] [Client 19] No authentication data provided.
D [12/Feb/2018:04:47:38 +0000] [Client 19] 2.0 CUPS-Get-Printers 17
D [12/Feb/2018:04:47:38 +0000] CUPS-Get-Printers
D [12/Feb/2018:04:47:38 +0000] [Client 19] Returning IPP successful-ok for CUPS-Get-Printers (no URI) from localhost
D [12/Feb/2018:04:47:38 +0000] [Client 19] Content-Length: 1767
D [12/Feb/2018:04:47:38 +0000] cupsd is not idle any more, canceling shutdown.
D [12/Feb/2018:04:47:38 +0000] [Client 19] cupsdWriteClient error=0, used=0, state=HTTP_STATE_POST_SEND, data_encoding=HTTP_ENCODING_LENGTH, data_remaining=1767, response=0x551b8710(IPP_IDLE), pipe_pid=0, file=-1
D [12/Feb/2018:04:47:38 +0000] [Client 19] Writing IPP response, ipp_state=DATA, old wused=0, new wused=0
D [12/Feb/2018:04:47:38 +0000] [Client 19] bytes=0, http_state=0, data_remaining=0
D [12/Feb/2018:04:47:38 +0000] [Client 19] Waiting for request.
D [12/Feb/2018:04:47:38 +0000] cupsdSetBusyState: newbusy="Not busy", busy="Active clients"
D [12/Feb/2018:04:47:38 +0000] cupsd is not idle any more, canceling shutdown.
D [12/Feb/2018:04:47:39 +0000] cupsd is not idle any more, canceling shutdown.
D [12/Feb/2018:04:47:39 +0000] [Client 19] HTTP_STATE_WAITING Closing on EOF
D [12/Feb/2018:04:47:39 +0000] [Client 19] Closing connection.
D [12/Feb/2018:04:47:39 +0000] SSL shutdown successful!
D [12/Feb/2018:04:47:39 +0000] cupsdSetBusyState: newbusy="Not busy", busy="Not busy"
D [12/Feb/2018:04:47:39 +0000] [Client 19] Waiting for socket close.
D [12/Feb/2018:04:47:39 +0000] cupsd is not idle any more, canceling shutdown.
D [12/Feb/2018:04:47:39 +0000] [Client 19] HTTP_STATE_WAITING Closing on EOF
D [12/Feb/2018:04:47:39 +0000] [Client 19] Closing connection.
D [12/Feb/2018:04:47:39 +0000] cupsdSetBusyState: newbusy="Not busy", busy="Not busy"
D [12/Feb/2018:04:47:39 +0000] cupsd is not idle any more, canceling shutdown.
D [12/Feb/2018:04:47:40 +0000] cupsd is not idle any more, canceling shutdown.

I do have my printer shared:
Brother_MFC-7340 (Idle, Accepting Jobs, Shared, Server Default)
And I have sharing enabled on my CUPS server too.  Both "Share printers connected to this system" and "Allow printing from the Internet" are enabled.
Any ideas?

By complete chance on the mailing list today this same issue was mentioned: https://groups.google.com/forum/#!topic/cloud-print-connector/5uRd_SoDxz0.
I discovered there is an option cups_ignore_raw_printers which by default is set to true and indeed I have a raw printer.  I have set this to "false" and now I get:
[19/Feb/2018:03:34:27 +0000] [Printer Brother_MFC-7340] Failed to call cupsGetPPD3(): 1030 Not Found
I don't believe the drivers are supported out of the box for the PI which is why I had this set to RAW (which works fine for normal printing).
Is there a way around this?

supply a PPD file to CUPS? (as I mentioned in the other thread, failing to do that was the blunder that I had made)

I tried that, but I got this:
Idle - "File "/usr/lib/cups/filter/brlpdwrapperMFC7340" not available: No
such file or directory"
Basically it is because there is no printer driver available out of the box
for the MFC-7340 for the PI.  So I had to use the RAW printer driver which
works fine locally.
It is just the cloud print connector doesn't seem to support it.
On Tue, Feb 20, 2018 at 12:16 PM, kanreki<EMAIL_ADDRESS>wrote:

supply a PPD file to CUPS? (as I mentioned in the other thread, failing to
do that was the blunder that I had made)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/google/cloud-print-connector/issues/399#issuecomment-366840175,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEXRAan9BBRi163mofkhJugzRymj-21oks5tWhzhgaJpZM4SBsZQ
.


PS4 wireless controller Support?

Is PS4/PS4 Wireless Controller support possible?

Yeah, what about adding PS Move controllers support? Would be cool, i think
Thanks in advance :)

Is there support for reading Euler angles from generic controllers(Like Arduino, etc.,) that can stream data via BLE?


MacOS: Using the OS's mechanism for opening a file

I'm trying to set Oni2 as my main editor for other programs to launch as well based on extension. For example, opening a file from Alfred using Onivim2. Onivim2 will open, but without the file.
On the command line, it would be the same as open -a /Applications/Onivim2.app ~/.zshrc. The OS opens the program and tells it to open the file. But, Onivim2 is ignoring the request for opening the file. This is particular to macOS.
I can create Alfred actions to do it properly on the command line for me, but in the long run Onivim2 should work with the OS and it's methods of launching the file as well.

I attempted this today, and used --args to do so. The behavior varied:

With a file:

open -a /Applications/Onivim2.app --args /Users/lbot/.bash_profile
it renders the file but no sidebar:

If I pass in a folder, it renders the full app (ignore the messed up onilogo, was testing the logos on my branch:

Try to use "Open with..." from Finder (or most other Finder type programs).
It doesn't open the file, just launches Oni2. Also, set Oni2 as your
default editor for a file extension and try to open that file by double
click. Again, it just opens the program. Oni2 should support these methods
of opening a file if it is to be a main stream editor.
On Mon, Feb 24, 2020 at 7:08 AM Lee Matos<EMAIL_ADDRESS>wrote:

I attempted this today, and used --args to do so. The behavior varied:

With a file:

open -a /Applications/Onivim2.app --args /Users/lbot/.bash_profile
it renders the file but no sidebar:
[image: image]
https://user-images.githubusercontent.com/359140/75122804-730fdf00-566f-11ea-8956-358d799f9721.png
If I pass in a folder, it renders the full app (ignore the messed up
onilogo, was testing the logos on my branch:
[image: image]
https://user-images.githubusercontent.com/359140/75122823-963a8e80-566f-11ea-91f0-0280ff644a5f.png
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/onivim/oni2/issues/1085?email_source=notifications&email_token=AAS7JRYSC66OHBZYVIZ3LFLREMFWNA5CNFSM4J5B4O6KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMWLQLA#issuecomment-590133292,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAS7JR3DGPTC5IBJUNIHNQLREMFWNANCNFSM4J5B4O6A
.

Just a note of thanks. It is working great for me now. Thank you so much.


Fix broken robot localization

It no longer exists in this repo, so it is fixed.
QED
We are migrating to a fork of the robot_localization repository instead, so that is why it has been removed from here.

Added a few more changes to make sure things launch smoothly, but will go ahead and merge now


Coordinate Conversion input format doesn't ignore case in hemisphere designator (ArcGIS Pro)

According to the following help topic, ArcGIS Pro ignores the case for hemisphere designators (N,S,E,W, n,s,e,w), however, the Coordinate Convert addin is case sensitive.
http://pro.arcgis.com/en/pro-app/tool-reference/data-management/supported-notation-formats.htm
I tested the ArcGIS Pro addin built on 1.2 SDK in ArcGIS Pro 1.2.

[x] The addin must ignore case for hemisphere designators, when the designators are suffixes for DD:
45.00n 70.00w

[x] The addin must ignore case for hemisphere designators, when the designators are prefixes for DD:
n45.00 w70.00

[x] The addin must ignore case for hemisphere designators, when the designators are suffixes for DDM:
45 00.00n 70 00.00w

[x] The addin must ignore case for hemisphere designators, when the designators are prefixes for DDM:
n45 00.00 w70 00.00

[x] The addin must ignore case for hemisphere designators, when the designators are suffixes for DMS:
45 00 00.00n 70 00 00.00w

[x] The addin must ignore case for hemisphere designators, when the designators are prefixes for DMS:
n45 00 00.00 w70 00 00.00

NOTE: the addin should also support this when entering in Longitude Latitude order.

@jmhauck Installed Pro addin dated 05 Jan 2017 09:08 and tested on Pro build 1.4.7197 and case is being ignored. Closing issue.


Fix error logging in libp2p

Explain your changes:

Replace %w with %s for errors logged in Libp2p helper (%w was the wrong descriptor in the first place)
Add trace-level logging for every outgoing IPC message on Daemon

Explain how you tested your changes:

Tested on cluster, helped in tracing an issue

Checklist:

[x] Dependency versions are unchanged

Notify Velocity team if dependencies must change in CI

[ ] Modified the current draft of release notes with details on what is completed or incomplete within this project
[x] Document code purpose, how to use it

Mention expected invariants, implicit constraints

[x] Tests were added for the new behavior

Document test purpose, significance of failures
Test names should reflect their purpose

[x] All tests pass (CI will check this if you didn't)
[x] Serialized types are in stable-versioned modules
[ ] Does this close issues? None

!ci-build-me

!ci-build-me

!approved-for-mainnet


DSD-824: HelperErrorText styling/implementation refactor

Fixes JIRA ticket DSD-824
This PR does the following:

Updates the styling for the HelperErrorText component, mostly by removing individual DS component's own use of marginTop for its placement.
Updates the theme object key name of helper to helperErrorText where appropriate.
Removes the Box wrapper around the HelperErrorText component in Checkbox, CheckboxGroup, ComponentWrapper, DatePicker, Fieldset, Label, Radio, RadioGroup, Select, Slider, TextInput, and Toggle.

@bigfishdesign13 The marginTop for the HelperErrorText is set to "xxs" for all components, but the CheckboxGroup and RadioGroup components both have their marginTop set to "s". I didn't change this because I wanted to run this by you but should it be set to "xxs" as well?
How has this been tested?
Storybook. Just visually checking that the UI is the same even though the DOM has changed (the wrapper div around the HelperErrorText component has been removed).
Accessibility concerns or updates

N/A

Checklist:

[ ] I have updated the Storybook documentation accordingly.
[ ] I have added relevant accessibility documentation for this pull request.
[ ] All new and existing tests passed.

Front End Review:

[ ] View the example in Storybook

Tugboat has finished building the preview for this pull request!
Link:

https://pr925-ul0rf2b71hm8pfwiugd9frjflbafznos.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/62446b339413e8006b35fbf3

Tugboat has finished building the preview for this pull request!
Link:

https://pr925-ul0rf2b71hm8pfwiugd9frjflbafznos.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/62446b339413e8006b35fbf3

@EdwinGuzman,
@bigfishdesign13 The marginTop for the HelperErrorText is set to "xxs" for all components, but the CheckboxGroup and RadioGroup components both have their marginTop set to "s". I didn't change this because I wanted to run this by you but should it be set to "xxs" as well?

I debated this initially and chose to leave it at the “s” value, but looking at it now, I think we can cut it back.  However, let’s use “xs” for the group components.

Updated.

Tugboat has finished building the preview for this pull request!
Link:

https://pr925-ul0rf2b71hm8pfwiugd9frjflbafznos.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/62446b339413e8006b35fbf3

Updated.

Tugboat has finished building the preview for this pull request!
Link:

https://pr925-ul0rf2b71hm8pfwiugd9frjflbafznos.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/62446b339413e8006b35fbf3

Tugboat has finished building the preview for this pull request!
Link:

https://pr925-ul0rf2b71hm8pfwiugd9frjflbafznos.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/62446b339413e8006b35fbf3

Tugboat has finished building the preview for this pull request!
Link:

https://pr925-ul0rf2b71hm8pfwiugd9frjflbafznos.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/62446b339413e8006b35fbf3


Animation error with Android

Hi there.
I created some animations for a app and when the developer test on android, the animation had a fill error that didn't have in IOS version. The problem is that there is not any fill where the error occour.
I attached the ae files and the images with the error
I'm a beginner in bodymovin, so I do not know if the way to export to Android is different from the one for IOS
After Effects Version: CC 2015
report_error.zip

I'm a beginner on bodymovin, so I don't know if I exported the files of right way to android

Hi, if you're using Lottie, I'd suggest that you post the issue directly on their github page.
https://github.com/airbnb/lottie-android

Ok! Thanks!


fix: update llama-index

Description

Testing

Additional context

Codecov Report

Merging #52 (adef10c) into main (e750415) will decrease coverage by 1.78%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main      #52      +/-   ##
==========================================
- Coverage   88.16%   86.39%   -1.78%
==========================================
  Files          11       11
  Lines         338      338
  Branches       47       47
==========================================
- Hits          298      292       -6
- Misses         25       32       +7
+ Partials       15       14       -1

Flag
Coverage Δ

integration
?

unittests
86.39% <ø> (ø)

unittests-3.10
86.39% <ø> (ø)

unittests-3.11
86.39% <ø> (ø)

unittests-3.8
86.39% <ø> (ø)

unittests-3.9
86.39% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
see 2 files with indirect coverage changes


Cannot read property 'element' of null when using vue component

The same error occured within Vue.Draggabel for vue 2 as you can see in this issue:
https://github.com/SortableJS/Vue.Draggable/issues/647
It was fixed in Version 2.22.0 but seem to appear in version 4.1 for vue3.
When using a Vue component inside the template tag, an error occurs when dragging the elements which says
Cannot read property 'element' of null
This won't work:
   <draggable
        class="draggable"
        :list="components"
        item-key="uuid"
        group="shared"
        animation="300"
        :key="components.length"
    >
      <template #item="{element}">
        <ZrmRow :isActive="chosenElement && chosenElement.uuid === element.uuid" :zrmComponent="element"/>
      </template>

But wrapped with a single div this does work:
 <draggable
       class="draggable"
       :list="components"
       item-key="uuid"
       group="shared"
       animation="300"
       :key="components.length"
   >
     <template #item="{element}">
       <div>
       <ZrmRow :isActive="chosenElement && chosenElement.uuid === element.uuid" :zrmComponent="element"/>
       </div>
     </template>

The error occurs in vuedraggable.js:
this.context seems to be null
 onDragStart(evt) {
      this.context = this.getUnderlyingVm(evt.item);
      evt.item._underlying_vm_ = this.clone(this.context.element);
      draggingElement = evt.item;
    },

System info
macOS 12.3.1
Node v18.1.0
npm 8.8.0
Packages
vue 3.2.37
vuedraggable 4.1.0
Builder
vite 2.9.12
@vitejs/plugin-vue 2.3.3
typescript 4.7.4
vue-tsc 0.38.3
Browser
Chrome 106.0.5249.103

This is relevant https://github.com/SortableJS/vue.draggable.next/pull/46

This is still happening and I can't have an extra div because it is a table and everything is packed into one element. @lu-roth Have you found another solution?

Any solution ?

I manage to resolve the issue by making sure the child component is imported. It was previously imported as a global component via defineAsyncComponent, which meant it wasn't being loaded in time.