Does this multiselect contain these features?

Hey, this is not an issue, but becasue the documentation is not the most descriptive of its parameters, I would like to know if this support several things:

ng-change - on change, can I trigger a function? (example: ng-change="myFunction()"
paramter-key - If my array is of objects, can I deside what parameter of the object is the key? (example parameter-key="custon_id")
parameter-value - format the shown value (example: parameter-value="name - key: id". When the object is {name: "example", key: "ex", id: 1} will show "example - ex: 1")
button-title - custom button title for the button to show more than 1 word. (example: button-title="Countries")

Besides these, I realy like the design, and options for the directive, and looking forward using it if above things exist (I realy dont need everything, most I can simulate on my own, but I want to know if some exist for I not to write jumbled code inside your neat directive)
Thanks

Hi there,
Apologies if these answers are not super-clear, but I haven't worked on
this project (and angularJS in general) for quite a while.

ng-change: Unless it is supported out of the box by ngmodelcontroller,
this is not supported. Should be easy to implement though!
parameter key: you can use the "id-prop" attribute for that, which is
described in the documentation (
http://bentorfs.github.io/angular-bootstrap-multiselect/) in section
(objects as model).
Parameter value: you can use "display-prop" attribute for that
(described in the same place in the docs). You can not use a combination of
values though.
Button title: you can use "default-text" attribute for this. It's not
documented though. It was added by someone else in a merge request I
approved.

Thanks for your kind words. If you add any features, please make a merge
request for it, so that others can benefit! Also, if the documentation is
lacking for you, I'll approve merge requests. I'm not very actively
maintaining this project :)
On Mon, Mar 28, 2016 at 8:07 PM Amit Moryossef<EMAIL_ADDRESS>wrote:

Hey, this is not an issue, but becasue the documentation is not the most
descriptive of its parameters, I would like to know if this support several
things:

ng-change - on change, can I trigger a function? (example:
ng-change="myFunction()"
paramter-key - If my array is of objects, can I deside what
parameter of the object is the key? (example parameter-key="custon_id")
parameter-value - format the shown value (example:
parameter-value="name - key: id". When the object is {name: "example", key:
"ex", id: 1} will show "example - ex: 1")
button-title - custom button title for the button to show more than
1 word. (example: button-title="Countries")

Besides these, I realy like the design, and options for the directive, and
looking forward using it if above things exist (I realy dont need
everything, most I can simulate on my own, but I want to know if some exist
for I not to write jumbled code inside your neat directive)
Thanks
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/bentorfs/angular-bootstrap-multiselect/issues/12

Thanks.
I created what I wanted except for the full on editable display prop, this might happen later. (At the moment I want to use this directive, but am not sure if will)
This is the first time I "contribute" to a project, and I am not sure if I am doing something wrong.
I commited the changes, and created a markdown file specifieng what I change and why.
I also created the pull request, hope that was not wrong as well.
Thanks again for this project, you have a really compact and nice code to work with!

How to use the library without bower ?


HMR forces page reload loops since update to nuxt 3.9.0

Environment

Operating System: Darwin
Node Version:     v21.6.0
Nuxt Version:     3.9.3
CLI Version:      3.10.0
Nitro Version:    2.8.1
Package Manager<EMAIL_ADDRESS>Builder:          -
User Config:      devtools, runtimeConfig, colorMode, extends, modules, supabase, pinia, vite
Runtime Modules<EMAIL_ADDRESS><EMAIL_ADDRESS>Build Modules:    -

Reproduction
Cannot provide at this time.
Describe the bug
Since the update, Vite is randomly forcing a hard refresh of the server and I get an infinite loop of folder creations in the terminal.

Additional context
No response
Logs
✔ Vite server hmr 14 files in 621.583ms
ℹ Directory components/ created                                    8:25:51 am
ℹ Directory components/ created                                    8:25:51 am
ℹ Directory components/ created                                    8:25:51 am
ℹ Directory components/ created                                    8:25:51 am
ℹ Directory components/ created                                    8:25:51 am
ℹ Restarting nuxt...                                               8:25:51 am
ℹ Restarting nuxt...                                               8:25:51 am
ℹ Using default Tailwind CSS file                 nuxt:tailwindcss 8:25:52 am
[nuxt:tailwindcss 8:25:52 am] ℹ Tailwind Viewer: http://<IP_ADDRESS>:3000/_tailwind/
ℹ Directory components/ created (repeated 16 times)                8:25:51 am
ℹ Vite server warmed up in 2848ms                                  8:25:55 am
✔ Nitro built in 1646 ms                                     nitro 8:25:55 am
[8:25:55 am] ℹ ✨ new dependencies optimized: @vee-validate/zod, vee-validate, zod
ℹ ✨ optimized dependencies changed. reloading                     8:25:55 am
ℹ Vite client warmed up in 3210ms                                  8:25:55 am
(node:18443) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
[8:28:17 am] ℹ hmr update /components/viewer/page.vue, /node_modules/tailwindcss/tailwind.css, /node_modules/tailwindcss/tailwind.css?direct
[8:28:23 am] ℹ hmr update /components/viewer/page.vue, /node_modules/tailwindcss/tailwind.css, /node_modules/tailwindcss/tailwind.css?direct (x2)
✔ Vite server hmr 14 files in 676.802ms
ℹ Directory components/ created                                    8:28:38 am
ℹ Directory components/ created                                    8:28:38 am
ℹ Directory components/ created                                    8:28:38 am
ℹ Directory components/ created                                    8:28:38 am
ℹ Directory components/ created                                    8:28:38 am
ℹ Directory components/ created                                    8:28:38 am
ℹ Restarting nuxt...                                               8:28:38 am
ℹ Using default Tailwind CSS file                 nuxt:tailwindcss 8:28:38 am
ℹ Directory components/ created (repeated 16 times)                8:28:38 am
ℹ Using default Tailwind CSS file                 nuxt:tailwindcss 8:28:38 am
ℹ Vite client warmed up in 3015ms                                  8:28:42 am
ℹ Vite server warmed up in 2819ms                                  8:28:42 am
✔ Nitro built in 1634 ms                                     nitro 8:28:42 am
(node:18443) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
✔ Vite server hmr 8 files in 786.374ms
ℹ Directory components/ created                                    8:28:57 am
ℹ Directory components/ created                                    8:28:57 am
ℹ Directory components/ created                                    8:28:57 am
ℹ Directory components/ created                                    8:28:57 am
ℹ Directory components/ created                                    8:28:57 am
ℹ Directory components/ created                                    8:28:57 am
ℹ Restarting nuxt...                                               8:28:57 am
ℹ Using default Tailwind CSS file                 nuxt:tailwindcss 8:28:57 am

I was using vite build target es2022 to enable top level await usage in the project to support a dependancy. I added the tsconfigRaw vite options as depicted in the screenshot and the forced reload reload loops have stopped. Appears related too: https://github.com/vitejs/vite/issues/15201


Shape Keys Not Appearing In Mapping

Confirmation

[X] I have followed the troubleshooting guide.

Summary
Installed the Rhubarb add-on. It doesn't appear in my Object Properties at all. Even when I have the object with shape keys selected. It does show on my Tools bar. I can import an audio.wav file. I can Capture the (sounds). But I can't map my keyframes. Why is this? I even cycled through all the filters. Renamed all of my shape keys to match the required naming conventions. Still, no such luck. Please help.
Rhubarb Lipsync NG addon version
1.5.2
Blender Version
4.1
Operating System
Windows

Hi @jLion23 ,
Note you also need to create shapekey-Actions. It is similar like normal Actions but they work with shape-keys. More details are here: https://www.youtube.com/watch?v=USCpOJGp_Zo&t=469s

Hi @jLion23 , Note you also need to create shapekey-Actions. It is similar like normal Actions but they work with shape-keys. More details are here: https://www.youtube.com/watch?v=USCpOJGp_Zo&t=469s

thanks alot. tha thelp out tremedously!!!!

Thanks alot. Problem solved :)


Deployment Pane: bicep file - .bicepparam is not available from file picker

In the Deployment Pane, Parameters section, the Pick JSON Parameters File picker can only select .json file not the recommended .bicepparam file

Thanks for raising this. For a workaround, you can open the deploy pane for an active .bicepparam file: https://github.com/Azure/bicep/blob/main/docs/experimental/deploy-ui.md#using

@anthony-c-martin  opening the deploy pane on a .bicepparam file doesnt offer you the 'Edit Parameters' option,  like is offered when you pick a json params file  from within the bicep template deploy pane view, so whilst opening it on a .bicepparam directly is a good workaround for deployments, its not for editing in the pane. The workaround for that would be to right click on a .bicepparam file and chose 'build parameters file' to create the .json version, then use that to get full functionality

@philricelf - correct, that was an intentional decision I made at the time. I imagined it would be simpler to have the .bicepparam and pane open side-by-side. If you need to edit a parameter value, then you can just edit it directly in the file.
If we were to show a form, what behavior would you expect if you overrode a particular value? Would the change be reflected in the .bicepparam file, or would the values only be used for the deployment/validation?

@anthony-c-martin  - it isnt something I personally find to be an issue , but mentioning just because it seems like a difference in behaviour. I.e  if you load a json parameters file in when using the deployment pane view opened from a .bicep file, that will allow you to edit, whilst when you open it directly on a .bicepparam it does not as mentioned - so it will entirely depend on the individuals use case as to if this is effects usability for them or not I guess.
Personally, I was exploring the potential for  using it as a tool for allowing engineers (that are less IaC savvy or early in the journey)  to perform deployments from a user friendly interface , so in that context I think having BOTH the ability to update parameters and deploy (with saving) and also the ability to update and save (or save as to create a new copy) might be nice.


Documentation.  Code cleanup.  Reenable archaius-legacy.

archaius-pull-requests #199 SUCCESS
This pull request looks good

NetflixOSS » archaius » archaius-pull-requests #30 SUCCESS
This pull request looks good


File validation for all monosi setup files

Description
There should be validation for all monosi related files (collections, monosi_project, monitors). Currently, we do not validate any of the files related to the monosi project. We need to check each related file to ensure that they are defined correctly. If there's an issue in the format or syntax, throw an error.
Other notes
This should be done in the validate function. This should probably use some form of schema validation (maybe https://python-jsonschema.readthedocs.io/en/stable/)

No longer necessary


Add win condition for light receivers

Light receiver objects have a charge attribute that increments as the light rays are on them. A win condition (a charge value) must be set to then trigger a win state.

Win condition set and takes user to win screen once met. Win screen has multiple options: continue or return to menu. Right now, only return to menu has functionality since there is only one level.


Optionally start nodes sequentially

Provide a flag that starts nodes sequentially so that node IDs match
hostnames.
Fix #47.

This change is

 that was easy.

Review status: 0 of 2 files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


FEATURE: Admin Dashboard

I have tried Stein using Google OAuth.
First we still need to login using email & password then login by google.
Can we just login by using Google OAuth if it's enabled?
Second, if we keep this flow as login is there any possibilities we will seeing Admin Dashboard that lists all of storage and users. Maybe not UAC Feature, just Storage Feature.
Or is it already fixed?

The current login flow allows multiple Google accounts to be connected, so we're going to stick to that.
Apart from that, we can look into creating a page that displays the connected Google accounts and storages. At the moment you can access the mongo console, switch to stein database, and list the storages (db.storages.find()) and the users.
If you'd want to work on creating that page, let me know 🙂


Unable to run test after changes to resize cat image

Challenge Size your Images has an issue.
User Agent is: Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/47.0.2526.111 Safari/537.36.
Please describe how to reproduce this issue, and include links to screenshots if possible.
I attempt to press the "Run Test" button or the CTRL+ENTER keys to run the test and move to the next, but I am unable to.  What did I do wrong?

I even cookies and pasted the next challenge's code back onto this issue and it still didn't work.
I'll email you again when and if I get it to work.
Maybe we should do it on Firefox?
Sent from my iPhone

On Jan 16, 2016, at 4:09 PM, Cathy<EMAIL_ADDRESS>wrote:
I am stuck at the same spot :(
—
Reply to this email directly or view it on GitHub.

Hey!
I appreciate you reaching out to me. I opened it up in Internet explorer (
not by choice ha) and my code worked perfectly.
Maybe chrome won't be the best for this site.
Again, thanks for following back up! 😊
Cathy
On Saturday, January 16, 2016, Cheryl U<EMAIL_ADDRESS>wrote:

I moved onto the next challenge.
I even cookies and pasted the next challenge's code back onto this issue
and it still didn't work.
I'll email you again when and if I get it to work.
Maybe we should do it on Firefox?
Sent from my iPhone

On Jan 16, 2016, at 4:09 PM, Cathy<EMAIL_ADDRESS><javascript:_e(%7B%7D,'cvml','notifications@github.com');>> wrote:
I am stuck at the same spot :(
—
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHub
https://github.com/FreeCodeCamp/FreeCodeCamp/issues/6225#issuecomment-172286434
.

--
Cathy Cortell
IT Recruiter at Accentuate staffing
(919)961-1284 Cell
(919)844-2900 Work
<EMAIL_ADDRESS>

I'm not able to repro this unfortunately, so I can't do any investigation into the cause.

I too, amhaving the same problem here.

Try running it in Internet Explorer or Firefox.
Sent from my iPhone

On Jan 17, 2016, at 4:00 PM, SpaulQ<EMAIL_ADDRESS>wrote:
I too, amhaving the same problem here.
—
Reply to this email directly or view it on GitHub.

Thanks, i have been using firefox.

It worked in firefox while doing this.

For some reason, it didn't work on Chrome.  It worked on Firefox and on I.E.
Sent from my iPhone

On Jan 17, 2016, at 8:46 PM, SpaulQ<EMAIL_ADDRESS>wrote:
It worked in firefox while doing this.
—
Reply to this email directly or view it on GitHub.

Not reproduceable on Google Chrome 46.0.2490.80 or Mozilla Firefox 41.0.2

Same problem in Chrome

Try it on Firefox or I.E.  It'll work.

On Jan 31, 2016, at 5:09 PM, Crystal C. Joseph<EMAIL_ADDRESS>wrote:
Same problem in Chrome
—
Reply to this email directly or view it on GitHub.

I tried Firefox and that wouldn't work either. LOL I just went on to the next challenge - had the code correct at least - but I'll try I.E. when I get home. Thanks!
Sincerely,
Crystal Joseph
about.me/crystal.joseph

On Jan 31, 2016, at 7:16 PM, Cheryl U<EMAIL_ADDRESS>wrote:
Try it on Firefox or I.E. It'll work.

On Jan 31, 2016, at 5:09 PM, Crystal C. Joseph<EMAIL_ADDRESS>wrote:
Same problem in Chrome
—
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHub.

@CrystalCJoseph @CherylU Can you guys try Reset + Hard Refresh?
First copy your code, some where.
Next click reset button on the challenge page.
Finally do a hard refresh (Ctrl + F5).
Then paste your code back and try running the tests.

😁 Tried that too, the button still will not work.
Sincerely,
Crystal Joseph
about.me/crystal.joseph

On Feb 1, 2016, at 11:07 AM, Mrugesh Mohapatra<EMAIL_ADDRESS>wrote:
@CrystalCJoseph @CherylU Can you guys try Reset + Hard Refresh?
First copy your code, some where.
Next click reset button on the challenge page.
Finally do a hard refresh (Ctrl + F5).
Then paste your code back and try running the tests.
—
Reply to this email directly or view it on GitHub.

Thanks @CrystalCJoseph Can you post a screenshot of browser console?
Press F12 to open the developer tools, and take a screenshot of the console and network tabs like below:

Okay, attached you will find both Firefox and Chrome screenshots :)
On Thu, Feb 4, 2016 at 12:10 PM, Mrugesh Mohapatra<EMAIL_ADDRESS>
wrote:

Thanks @CrystalCJoseph https://github.com/CrystalCJoseph Can you post a
screenshot of browser console?
Press F12 to open the developer tools, and take a screenshot of the
console and network tabs like below:
[image: 1]
https://cloud.githubusercontent.com/assets/1884376/12824679/646f901e-cb98-11e5-9642-0d38f64606e5.PNG
[image: 2]
https://cloud.githubusercontent.com/assets/1884376/12824678/646ec418-cb98-11e5-8f82-f4009f52625d.PNG
—
Reply to this email directly or view it on GitHub
https://github.com/FreeCodeCamp/FreeCodeCamp/issues/6225#issuecomment-179973344
.

--
Sincerely,
Crystal Claire Joseph

@CrystalCJoseph
Umm, Github doesn't let you attach images via email! You have to visit this issue page here.
And drag and drop those screenshots in to the comment box.
Thanks again for helping us out!

Oh I had replied via email and attached them that way, not realizing where you were actually viewing this. Sorry lol  When I'm at my computer I'll drop the pics in

Chrome - Console

Chrome - Network

Firefox- Console

Firefox- Network

Sorry @raisedadead I was just replying to the email on my phone, so I didn't realize the photos wouldn't go into the comment. But, there they are in my last comment so I hope it helps

@CrystalCJoseph Thanks for the screenshots.
From your Chrome Console log is appears that your facing a CSP issue, many campers faced recently (read more).
Since you are blocked by issue on both Chrome and Firefox, I recommend you go through the wiki link below, and try browsec. It may resolve your case at least.
https://github.com/FreeCodeCamp/FreeCodeCamp/wiki/Using-browsec-for-securing-your-connection-to-fcc
Let me know, how it goes.

Hey @Raisedadead I Installed Browsec on Chrome but I am still experiencing the same problem with the button. Though Browsec is cool so thanks for the tip on that extension!

Ug.
I'm glad I got it right. I'm sad that I got so very frutrated for DAYS before coming here to find that... I'm not the only one and my code on this was correct.
Now I'm going to sift through this thread to find an answer. I hope.

oh wow. I figured it out. I was wrong. carry on.

Closing as we have moved to site wide SSL. All/Most URLs are now migrated to use https.
Please open fresh issue if this persists.
Thanks and Happy Coding!


Cannot pass the unittest (pytest)

The Issue with pytest 8.2.0 and tornado async tests was found.
The workaround:

Downgrade the pytest to 8.1.2

pip install 'pytest<8.2.0'

Upgrade the tornado to at least 6.4.1

pip install 'tornado>=6.4.1'

Current test output:
========== short test summary info ==========
ERROR tests/test_app.py::AsyncHTTPTestCase - AttributeError: 'AsyncHTTPTestCase' object has no attribute 'runTest'. Did you mean: 'subTest'?
ERROR tests/test_app.py::TestAppBase - AttributeError: 'TestAppBase' object has no attribute 'runTest'. Did you mean: 'subTest'?
ERROR tests/test_app.py::TestAppBasic - AttributeError: 'TestAppBasic' object has no attribute 'runTest'. Did you mean: 'subTest'?
ERROR tests/test_app.py::OtherTestBase - AttributeError: 'OtherTestBase' object has no attribute 'runTest'. Did you mean: 'subTest'?
ERROR tests/test_app.py::TestAppInDebugMode - AttributeError: 'TestAppInDebugMode' object has no attribute 'runTest'. Did you mean: 'subTest'?
ERROR tests/test_app.py::TestAppWithLargeBuffer - AttributeError: 'TestAppWithLargeBuffer' object has no attribute 'runTest'. Did you mean: 'subTest'?
ERROR tests/test_app.py::TestAppWithRejectPolicy - AttributeError: 'TestAppWithRejectPolicy' object has no attribute 'runTest'. Did you mean: 'subTest'?
ERROR tests/test_app.py::TestAppWithBadHostKey - AttributeError: 'TestAppWithBadHostKey' object has no attribute 'runTest'. Did you mean: 'subTest'?
ERROR tests/test_app.py::TestAppWithTrustedStream - AttributeError: 'TestAppWithTrustedStream' object has no attribute 'runTest'. Did you mean: 'subTest'?
ERROR tests/test_app.py::TestAppNotFoundHandler - AttributeError: 'TestAppNotFoundHandler' object has no attribute 'runTest'. Did you mean: 'subTest'?
ERROR tests/test_app.py::TestAppWithHeadRequest - AttributeError: 'TestAppWithHeadRequest' object has no attribute 'runTest'. Did you mean: 'subTest'?
ERROR tests/test_app.py::TestAppWithPutRequest - AttributeError: 'TestAppWithPutRequest' object has no attribute 'runTest'. Did you mean: 'subTest'?
ERROR tests/test_app.py::TestAppWithTooManyConnections - AttributeError: 'TestAppWithTooManyConnections' object has no attribute 'runTest'. Did you mean: 'subTest'?
ERROR tests/test_app.py::TestAppWithCrossOriginOperation - AttributeError: 'TestAppWithCrossOriginOperation' object has no attribute 'runTest'. Did you mean: 'subTest'?
ERROR tests/test_app.py::TestAppWithBadEncoding - AttributeError: 'TestAppWithBadEncoding' object has no attribute 'runTest'. Did you mean: 'subTest'?
ERROR tests/test_app.py::TestAppWithUnknownEncoding - AttributeError: 'TestAppWithUnknownEncoding' object has no attribute 'runTest'. Did you mean: 'subTest'?
ERROR tests/test_profiles.py::AsyncTestCase - AttributeError: 'AsyncTestCase' object has no attribute 'runTest'. Did you mean: 'subTest'?
ERROR tests/test_profiles.py::AsyncHTTPTestCase - AttributeError: 'AsyncHTTPTestCase' object has no attribute 'runTest'. Did you mean: 'subTest'?
ERROR tests/test_profiles.py::TestWebGUIWithProfiles - AttributeError: 'TestWebGUIWithProfiles' object has no attribute 'runTest'. Did you mean: 'subTest'?
ERROR tests/test_profiles.py::TestWebGUIWithoutProfiles - AttributeError: 'TestWebGUIWithoutProfiles' object has no attribute 'runTest'. Did you mean: 'subTest'?
!!!!!!!!!! Interrupted: 20 errors during collection !!!!!!!!!!
========== 20 errors in 0.52s ==========

issue-385-fixing.patch
Attached the patch for upgrading the tornado to 6.4.1


Special case array length reporting

@ofrobots PTAL.

As discussed; this looks reasonable, but perhaps a more generic approach that catches all/more built-in object properties would be preferable.

After discussing this with the V8 team, it seems a more complete solution does not currently exist. We can continue pursuing that approach but I think this patch will address the immediate problem and we are not currently aware of other members in this class of safe to evaluate, native properties (String.length does also fall here but we report strings as literals and do not list their properties so this is not an issue for us).

It is also worth noting that array length does not show up on the object mirror in Node.js v0.12. This change only prevents the error we were previously reporting in v1+.

LGTM w/ nits.


add option to attach event id from sentry to error as per #99

@ryankauk hey there, sorry for getting back this late, I completely missed your PR! Just for my understanding, you're trying to attach the event id created by Sentry to the error object?
From what I see the implementation is rather minimal, which is great. The only thing I'd double-check is if TypeScript complains when you're for example passing in an ApolloError, so an error that is based on the default Error, but adds own types to it, maybe this causes some conflict but I'm not entirely sure 🤔

@BrunoScheufler sure sounds good, I'll check it out and verify


t-display-s3-full.stp corrupt file

Hello. I had some corrupt file issues with this file
t-display-s3-full.stp

Downloading the file as RAW worked in fusion 360


Add FOV and resolution options, update for Hero9, and mention AUR package

Thanks for your contribution @NewoIsTaken

Thank you for starting this project @jschmid1! Also, I believe there is another pull request that aims to do the same thing. I don't that one will be needed anymore.

I don't that one will be needed anymore.

Yes. I was about to close it


Rewrite JS module to an ESModule

Move js file over to a module, to lower the risk of future namespace clashes.

Fixed quite some time ago


html option not handled as expected

when html option is on,  it does not render markdown contents inside
when html option is off, it does render markdown contents inside, but keep the html tags visible.
this kind of behavior invalidates one big advantage of of using embedding html into markdown

Can someone please answer this!! I also have the same issue!


define default srcDir and outputDir

define default srcDir and outputDir.
Having a default outputDir is a must, as stampo will wipe the output dir on build.

done.
https://github.com/digitalfondue/stampo-maven-plugin/commit/f96f5d2ccc39986c74c5d13fb854b11381c1e24b


[Bug]: "Load error: Resource recorder error" when waking from idle

What happened?
The deployment command works well, but when it waked from idle, it always crashed because of "Resource recorder error". Sometimes "could not verify project ownership" and sometimes ""This resource endpoint is discontinued. Please restart your project."
Version
v0.39.0
Which operating system(s) are you seeing the problem on?
In deployment
Which CPU architectures are you seeing the problem on?
In deployment
Relevant log output
2024-02-24T07:42:19.471932Z [Deployer]  INFO start_deployment
2024-02-24T07:42:19.472074Z [Deployer]  INFO Entering Built state
2024-02-24T07:42:19.472076Z [Deployer]  INFO Starting deployment
2024-02-24T07:42:19.472219Z [Deployer]  INFO Entering Loading state
2024-02-24T07:42:19.472222Z [Deployer]  INFO Loading resources
2024-02-24T07:42:19.472288Z [Deployer]  INFO shuttle_service::runner: {args="/opt/shuttle/shuttle-builds/remove-box-rs/.shuttle-executables/28ac3c9e-cde5-413e-862c-2ac127b1edbb --port 20004 --provisioner-address http://provisioner:8000/ --env production --auth-uri http://auth:8000/"} Spawning runtime process
2024-02-24T07:42:19.472498Z [Deployer]  INFO shuttle_proto::runtime: connecting runtime client
2024-02-24T07:42:19.478487Z [Runtime] shuttle-runtime executable started (version 0.39.0)
2024-02-24T07:42:19.478489Z [Runtime] ===============================================================
2024-02-24T07:42:19.478489Z [Runtime] Shuttle's default tracing subscriber is initialized!
2024-02-24T07:42:19.478490Z [Runtime] To disable the subscriber and use your own,
2024-02-24T07:42:19.478491Z [Runtime] turn off the default features for shuttle-runtime:
2024-02-24T07:42:19.478491Z [Runtime]
2024-02-24T07:42:19.478492Z [Runtime] shuttle-runtime = { version = "...", default-features = false }
2024-02-24T07:42:19.478492Z [Runtime] ===============================================================
2024-02-24T07:42:19.478633Z [Deployer]  INFO shuttle_deployer::deployment::run: Loading resources
2024-02-24T07:42:19.478670Z [Deployer]  INFO shuttle_deployer::persistence: {__self.project_id="01HQ7W881Z44R49MFJVDYBKK73"} Getting resources from resource-recorder
2024-02-24T07:42:19.480267Z [Deployer]  INFO Entering Crashed state
2024-02-24T07:42:19.480269Z [Deployer]  INFO Cleaning up startup crashed deployment
2024-02-24T07:42:19.480295Z [Deployer] ERROR shuttle_deployer::deployment::run: {error="Load error: Resource recorder error: status: Internal, message: \"could not verify project ownership\", details: [], metadata: MetadataMap { headers: {\"content-type\": \"application/grpc\", \"date\": \"Sat, 24 Feb 2024 07:42:19 GMT\", \"content-length\": \"0\"} }"} Service startup encountered an error

2024-02-24T07:42:19.471932Z [Deployer]  INFO start_deployment
2024-02-24T07:42:19.472074Z [Deployer]  INFO Entering Built state
2024-02-24T07:42:19.472076Z [Deployer]  INFO Starting deployment
2024-02-24T07:42:19.472219Z [Deployer]  INFO Entering Loading state
2024-02-24T07:42:19.472222Z [Deployer]  INFO Loading resources
2024-02-24T07:42:19.472288Z [Deployer]  INFO shuttle_service::runner: {args="/opt/shuttle/shuttle-builds/remove-box-rs/.shuttle-executables/28ac3c9e-cde5-413e-862c-2ac127b1edbb --port 20004 --provisioner-address http://provisioner:8000/ --env production --auth-uri http://auth:8000/"} Spawning runtime process
2024-02-24T07:42:19.472498Z [Deployer]  INFO shuttle_proto::runtime: connecting runtime client
2024-02-24T07:42:19.478487Z [Runtime] shuttle-runtime executable started (version 0.39.0)
2024-02-24T07:42:19.478489Z [Runtime] ===============================================================
2024-02-24T07:42:19.478489Z [Runtime] Shuttle's default tracing subscriber is initialized!
2024-02-24T07:42:19.478490Z [Runtime] To disable the subscriber and use your own,
2024-02-24T07:42:19.478491Z [Runtime] turn off the default features for shuttle-runtime:
2024-02-24T07:42:19.478491Z [Runtime]
2024-02-24T07:42:19.478492Z [Runtime] shuttle-runtime = { version = "...", default-features = false }
2024-02-24T07:42:19.478492Z [Runtime] ===============================================================
2024-02-24T07:42:19.478633Z [Deployer]  INFO shuttle_deployer::deployment::run: Loading resources
2024-02-24T07:42:19.478670Z [Deployer]  INFO shuttle_deployer::persistence: {__self.project_id="01HQ7W881Z44R49MFJVDYBKK73"} Getting resources from resource-recorder
2024-02-24T07:42:19.480267Z [Deployer]  INFO Entering Crashed state
2024-02-24T07:42:19.480269Z [Deployer]  INFO Cleaning up startup crashed deployment
2024-02-24T07:42:19.480295Z [Deployer] ERROR shuttle_deployer::deployment::run: {error="Load error: Resource recorder error: status: Internal, message: \"could not verify project ownership\", details: [], metadata: MetadataMap { headers: {\"content-type\": \"application/grpc\", \"date\": \"Sat, 24 Feb 2024 07:42:19 GMT\", \"content-length\": \"0\"} }"} Service startup encountered an error

Duplicate declaration

[X] I have searched the issues and there are none like this.

This is due to a security patch we released yesterday. The solution is to restart the project: cargo shuttle project restart

Confirmed, also seeing
2024-02-25T23:05:09.251176Z [Deployer] ERROR shuttle_deployer::deployment::run: {error="Load error: Resource recorder error: status: Internal, message: \"could not verify project ownership\", details: [], metadata: MetadataMap { headers: {\"content-type\": \"application/grpc\", \"date\": \"Sun, 25 Feb 2024 23:05:09 GMT\", \"content-length\": \"0\"} }"} Service startup encountered an error

Going to try @s-lambert fix setting idle minutes to 0

@s-lambert @djmango Earlier today, we fixed a follow-up issue from the patch release that fixes crashes when waking up from idle.

Our patch yesterday should have fixed this error. Feel free to re-open the issue if it did not :smile:


Workflow Management CLI

This PR adds a command-line interface for workflow management. There are five new commands:

npx dbos workflow list: List workflows run by your application. Takes in parameters to filter on time, status, user, etc.
npx dbos workflow get <uuid>: Retrieve the status of a workflow.
npx dbos workflow cancel <uuid>: Cancel a workflow so it is no longer automatically retried or restarted . Active executions are not halted and the workflow can still be manually retried or restarted.
npx dbos workflow retry<uuid>: Retry a workflow from the last step it executed, keeping its UUID.
npx dbos workflow restart<uuid>: Resubmit a workflow, restarting it from the beginning with the same arguments but a new UUID.

npx dbos workflow retry<uuid>: Retry a workflow from the last step it executed, keeping its UUID.
npx dbos workflow restart<uuid>: Resubmit a workflow, restarting it from the beginning with the same arguments but a new UUID.

Retry and restart are confusing  to me. Maybe consider resume vs restart? resume naturally means it starts from where it left off, and restart naturally means it starts from the beginning.


chore: Update documentation

:tada: This PR is included in version 6.0.0-beta.15 :tada:
The release is available on:

v6.0.0-beta.15
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 6.0.0-rc.1 :tada:
The release is available on:

v6.0.0-rc.1
GitHub release

Your semantic-release bot :package::rocket:


Use haproxy official downloads over https instead of an arbitrary s3 bucket

This reverts https://github.com/Yelp/synapse-tools/pull/87 and switches to https protocol, which I've confirmed works locally. Will see if the github actions tests work 🤞

The test failure doesn't look related to my changes :(
Successfully built 58b55712c1b4
Successfully tagged bionic_bionic:latest
compose.cli.verbose_proxy.proxy_callable: docker close <- ()
compose.cli.verbose_proxy.proxy_callable: docker close -> None
package_bionic runtests: commands[1] | docker-compose run bionic
Creating network "bionic_default" with the default driver
GLOB sdist-make: /work/src/setup.py
bionic create: /work/src/.tox/bionic
bionic installdeps: -r/work/src/requirements.txt, flake8, pytest, mock==2.0.0
Traceback (most recent call last):
  File "/usr/bin/tox", line 11, in <module>
    load_entry_point('tox==2.5.0', 'console_scripts', 'tox')()
  File "/usr/lib/python3/dist-packages/tox/session.py", line 39, in main
    retcode = Session(config).runcommand()
  File "/usr/lib/python3/dist-packages/tox/session.py", line 390, in runcommand
    return self.subcommand_test()
  File "/usr/lib/python3/dist-packages/tox/session.py", line 541, in subcommand_test
    if self.setupenv(venv):
  File "/usr/lib/python3/dist-packages/tox/session.py", line 449, in setupenv
    status = venv.update(action=action)
  File "/usr/lib/python3/dist-packages/tox/venv.py", line 168, in update
    self.hook.tox_testenv_install_deps(action=action, venv=self)
  File "/usr/lib/python3/dist-packages/pluggy/__init__.py", line 617, in __call__
    return self._hookexec(self, self._nonwrappers + self._wrappers, kwargs)
  File "/usr/lib/python3/dist-packages/pluggy/__init__.py", line 222, in _hookexec
    return self._inner_hookexec(hook, methods, kwargs)
  File "/usr/lib/python3/dist-packages/pluggy/__init__.py", line 216, in <lambda>
    firstresult=hook.spec_opts.get('firstresult'),
  File "/usr/lib/python3/dist-packages/pluggy/callers.py", line 201, in _multicall
    return outcome.get_result()
  File "/usr/lib/python3/dist-packages/pluggy/callers.py", line 76, in get_result
    raise ex[1].with_traceback(ex[2])
  File "/usr/lib/python3/dist-packages/pluggy/callers.py", line 180, in _multicall
    res = hook_impl.function(*args)
  File "/usr/lib/python3/dist-packages/tox/venv.py", line 423, in tox_testenv_install_deps
    venv._install(deps, action=action)
  File "/usr/lib/python3/dist-packages/tox/venv.py", line 305, in _install
    action=action)
  File "/usr/lib/python3/dist-packages/tox/venv.py", line 278, in run_install_command
    redirect=self.session.report.verbosity < 2)
  File "/usr/lib/python3/dist-packages/tox/venv.py", line 384, in _pcall
    redirect=redirect, ignore_ret=ignore_ret)
  File "/usr/lib/python3/dist-packages/tox/session.py", line 201, in popen
    out = outpath.read()
  File "/usr/lib/python3/dist-packages/py/_path/common.py", line 171, in read
    return f.read()
  File "/usr/lib/python3.6/encodings/ascii.py", line 26, in decode
    return codecs.ascii_decode(input, self.errors)[0]
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 627: ordinal not in range(128)
ERROR: InvocationError for command '/home/runner/work/synapse-tools/synapse-tools/.tox/package_bionic/bin/docker-compose run bionic' (exited with code 1)


Fix missing closing bracket on handle_message

This fix solves issue #12.
A missing bracket was resulting in a critical block of the handle_message
switch never being reached. Before this fix, the vehicle would loop forever
waiting for those unhandled messages.
Signed-off-by: Guilherme Campos Camargo<EMAIL_ADDRESS>

Ship it

@rchiossi, can you please test this patch in your set-up as well before merging?

I'm on  the airport now, will try to test it ASAP, but if waiting for me would delay your work, merge it and we send a new patch later if the problem  persists

Managed to test it. Works for me.

@rchiossi, thanks! Merging...


Created function unauthorized to get from GraphQL API.

Describe the bug
Created function unauthorized to get from GraphQL API.
{
  errors: [
    {
      errorType: 'UnauthorizedException',
      message: 'Permission denied'
    }
  ]
}

Amplify CLI Version
4.18.1
To Reproduce

Initialize amplify project
Setup API with default Cognito auth, additonal iam auth
Add function, when asked for access, select API and choose read access.
Add a type (with @model) to the schema with auth iam read

type User @model @auth(rules: [{ allow: private, provider: iam, operations: [read] }]) {
  id: ID!
  tenantAdmin: Boolean!
  role: Role @connection(name: "UserRole")
  tenant: Tenant @connection(name: "UserTenant")
}

Go to the AWS console, go to lambda, open the created function. Do a (signed) HTTP call to the API.

  query GetUser($id: ID!) {
    getUser(id: $id) {
      id
      tenantAdmin
    }
  }

Create lambda test, and run it.

Expected behavior
Authorized to get the user.

Solved by https://github.com/aws-amplify/amplify-cli/issues/2890


Swipe left/right for next hotspot card

When trying to view all my hotspot details, I find it slightly painful to have to swipe a hotspot card down, hit Back, then choose another hotspot to get to the next hotspot details. Would be easier if I could swipe left/right to go from one hotspot card to the next.

let's do arrow left and right on the hotspot details page, and move the hamburger out into a share button elsewhere (kebab next to hotspot name?)

I had been working on something but it turned into a larger revision. The goal was to provide better navigation closer to the base of the app.


Screenshot

(3rd time's the charm!)
Rebase of: https://github.com/openfl/openfl/pull/925
I'm sure a better API can be designed, but this works and can be easily rearranged

(Travis will fail on this build until this is merged: https://github.com/openfl/lime/pull/666)


Re-write guide scraper

Re-write guide scraper with application wrapper, logging, parameterization, etc.

Will also try writing this in Go, mostly as a Go learning exercise. Will look into multi-threading to cut down on run time. Could increase frequency. Need to verify there are not rate limits on API service.
Also need to write a better README with instructions on creating an account to use with the API.


Add classloader protection

Currently, if you create a classloader from a container group, it will use the current stste of that container group to work. If you then modify anything in the container group, it will discard the classloader entirely and create a new one next time it is used.
This might be considered potentially confusing behaviour in some cases like the following pseudocode:
classLoader1 := compiler.classOutput.classLoader
fooClass1 := classLoader1.loadClass("org.example.Foo")

compiler.classOutput.add(newPath)

classLoader2 := compiler.classOutput.classLoader
fooClass2 := classLoader2.loadClass("org.example.Foo")

foo1 := fooClass1.newInstance()
foo2 := fooClass2.newInstance()

assert foo1.class.equals(foo2.class)  // bang!

To prevent this, we could consider adding protection code around container groups so that once a classloader is requested, the container group is considered effectively frozen and will refuse any operation for further modification. Instead, it could raise an informative exception instead.

Closing this for now as the implementation complexity of this outweighs the small number of edge cases where this can occur. Documentation is pretty decent for this at the moment I think, but if this is raised as a source of confusion in the future then I will reconsider looking into this.


Feature: Allow turning off the fade-in animation with transparent windows

When you show a transparent window on windows, it fades in. I would prefer it came in immediately.
It would be good if there was a setting for this, if it is possible.

The transparent window doesn't fade in, it is probably just showing too slow on your machine.


Refactor C++ Test Drivers

The C++ test drivers consist of a lot of copy pasta, which violates the DRY principle. These should be cleaned up and have common functionality factored out to improve future maintainability and extensibility.

These are unused and have been so for a while. Perhaps they should be deleted?

perhaps ping  #788 ?
I'd love to have ./lib as a self-contained and installable library, as we're using it as such. Obviously sans the semver promises that apply to the python api. Removing crud would help :)

I was actually pondering a C++ test suite the other day -- a lot of my multithreading stuff is low level, and very difficult to test from Python without writing more CPython objects, which kind of defeats the purpose of simple tests by adding tons of extra glue code just to run them in the first place. Unfortunately, I have zero knowledge or experience with C++ testing libs. Thoughts @ctb, @mr-c @luizirber ?

On Thu, Mar 19, 2015 at 08:56:38AM -0700, Camille Scott wrote:

I was actually pondering a C++ test suite the other day -- a lot of my multithreading stuff is low level, and very difficult to test from Python without writing more CPython objects, which kind of defeats the purpose of simple tests by adding tons of extra glue code just to run them in the first place. Unfortunately, I have zero knowledge or experience with C++ testing libs. Thoughts @ctb, @mr-c @luizirber ?

I hear Boost has a testing lib.

:{

This looks pretty cool:
https://github.com/philsquared/Catch
Header only, boost licensed.


grandpa: always try to import available block justifcation

Currently GrandpaBlockImport only tries to import justifications for blocks that it needs to (i.e. authority set change blocks), even if a justification is available it is discarded.
This means that during sync, on a network with no authority set changes there are long periods of unfinalized blocks, since we are discarding any available justification. On a PoS network this should not be an issue as there regular authority set changes.
 Unfortunately, for most of the initial chain there doesn't seem to be many available justifications in the network (although there are some and my node imported them). I think this is mostly because validators who had observed finality live (and stored a justification), may have resynced their nodes (with archive pruning), and hence dropping the existing justifications. On Kusama the nodes should be storing justifications every 512 blocks.


a few edits

:tada: This PR is included in version 8.6.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Update README.md

Added a PR for an update to the UmbracoDocs repo for an update to a Umbraco Forms page

Thanks @AndyBoot - the docs repo already counts for hacktoberfest, so no need to submit here.
However... this awesome package you should definitely add to the list! https://twitter.com/i/web/status/1584135281548361728 👍

Ah just saw you already did that, thanks! 🎉 https://github.com/umbraco/HacktoberfestActivityLog/pull/22


S3 project simplification

:loudspeaker: Type of change

[ ] Bugfix
[ ] New feature
[ ] Enhancement
[x] Refactoring

:scroll: Description
An optional refactoring which i didn't want to include in https://github.com/awspring/spring-cloud-aws/pull/453.
This change makes it no longer necessary to commit the AbstractCrossRegionS3Client.
If this change is desirable, i will rebase this PR on main after https://github.com/awspring/spring-cloud-aws/pull/453 is merged.
:bulb: Motivation and Context
Since a lot of this code is generated anyway, there is no need to have it in source control, and we can simplify the project structure a bit.
:green_heart: How did you test it?
CI
:pencil: Checklist

[x] I reviewed submitted code
[ ] I added tests to verify changes
[ ] I updated reference documentation to reflect the change
[x] All tests passing
[x] No breaking changes

:crystal_ball: Next steps

@fjmacagno apologies for late reply - I was on holidays. The problem with not having generated client in source control is that it gets difficult to see if/what has changed - where change can happen when AWS SDK changes.
This means that we can accidentally introduce breaking change - which I would like to avoid.

No worries, i was also on vacation. That makes sense, my gut tells me there is a way to solve all the issues but i cant think of it.


Title label truncation before the icon

The label should now truncate before the icon.

@aleffert please review.

:+1:


[Backport] 2.4: V1 Logging on recently upgraded/created AKS clusters fails with "Connection reset by peer"

Original Issue:
https://github.com/rancher/rancher/issues/30425

Rancher version v2.4.13-rc1 (01/12/2020)
rancher-logging v1 chart version: 0.2.4
Azure AKS: v1.18.10
Docker: 19.3.12
I left logging collecting the cluster container logs for 3 hours I didn't see the exception thrown on any of the fluentd containers.
Logs where flowing properly during this time window.
Logging provider: Elasticsearch 7.8.0
Repro details: https://github.com/rancher/rancher/issues/30425#issuecomment-749581725

Rancher version v2.4.13-rc1 (01/12/2020)
rancher-logging v1 chart version: 0.2.4
Azure AKS: v1.18.10
Docker: 19.3.12
I left logging collecting the cluster container logs for 3 hours I didn't see the exception thrown on any of the fluentd containers.
Logs where flowing properly during this time window.
Logging provider: Elasticsearch 7.8.0
Repro details: https://github.com/rancher/rancher/issues/30425#issuecomment-749581725


Rewrite admin using Angular2

[ ] Configure compilation of TypeScript into JS
[ ] Make BlueberryPy serve initial template and Angular's static
[ ] Implement and decompose app into

[ ] Router
[ ] Components
[ ] API resources
[ ] Auth service
[ ] convert template syntax

[ ] ... etc

UPD: rewrite admin using Angular 4


Snake phase names

Default name of phases where based on a lower cased version of their classnames.
That was bad. eg FFILanguageAssignationPhase -> ffilanguageassignation
So this PR snakecase them instead.
But the spec of to_snake_case was awful: f_f_i_language_assignation
So also fix the spec of this method and get something nice ffi_language_assignation.

:shipit:

reroll: annnnn uppercase

+1


Generated prjoect has a git repo added which doesn't let it add as a submodule to another project

Version
3.0.0-beta.6
Reproduction link
https://github.com/abondar24/SocialTournamentService
Steps to reproduce
Clone and create a new vue app via vue create
What is expected?
App is not added to a bigger project before it's done by git add .
What is actually happening?
.git dir is created  and the app is created as a submodule which is tough to maintain.

Either turn off creating a local git repo or add an option while creating. Via the link to my repo you will find the app added as a I wanted. For this I had to ignore registring a VCS root in IntelliJ Idea. Then removed .git dir.

I just run into this as well. I don't expect a cli to init a git, I might not even use git or set the project in a monorepo, etc. I would expect this kind of actions to be optional.

Same here -- in my case, I'm rewriting my app in vue, so I did git checkout --orphan v2 to create a fresh orphan branch. I didn't realise I could use vue create . so I did it in a subdirectory and moved the files up, but noticed that .git directory in there and was surprised.
While it is convenient for a new project, in my opinion, I don't think anyone would expect a git commit to be made from vue-cli. Of course, I've thought about this all of 30 seconds, and I'm sure whoever authored it thought about it plenty more. Just wanted to share my bit of feedback. Thanks for your work on this project -- the cli 3.0 is really handy!

I definitely think the CLI needs an option to either opt into or out of initializing a git repo on project creation.  Would be helpful especially for those that do not use git.

How about checking if already in a git repo, instead of initializing a submodule (since the user seems to have the repo in control)? e.g. via git rev-parse --is-inside-work-tree.
Would be really nice if it didn't create a repo; my current workflow with the cli is:
vue create xyz
cd xyz
rm -rf .git
npm run dev

Please get rid of the generated .git folder, its the last thing I want to be installed, can I just delete it?)

How about checking if already in a git repo, instead of initializing a submodule

This is a good idea.

Please get rid of the generated .git folder, its the last thing I want to be installed, can I just delete it?

You can delete it, but you will lose change detection after invoking a plugin that modifies your files.

I don't really get the point of the .git folder, Ember cli and create react app, manages pretty good without a .git folder
Having the previous .git folder messes up my git log and I've spent most of today trying to fix it
13:02	Checked out ae73e9ccc6f59c17d346a33ec4f1b2fb21e62a2f (show balloon)
13:02	Couldn't checkout 064071910d689420fdb5f45847069755b7a757c3: Updating the following directories would lose untracked files in it:

I don't really get the point of the .git folder, Ember cli and create react app, manages pretty good without a .git folder

vue-cli plugins are meant to modify your file. Without a .git folder, vue-cli couldn't let you know precisely which file was modified and how, and you couldn't see the changes by yourself and eventually revert some of them thant doesn't suit you.

Thanks for the clarification. What I will do is just create a new project and upload this direct to the remote.


chore(Data): use newly introduced finset notation

For s : Finset α, replace s.card with #s, s.filter p with {x ∈ s | p x}, ∑ x ∈ s.filter p, f x with ∑ x ∈ s with p x, f x. Rewrap lines around and open the Finset locale where necessary.

Thanks!
bors r+


Two Dimensional Histograms

When I open a 2D histogram in uproot and convert the data to a numpy array, the output only contains bin edges for one axis and under/overflow bins are included in the content, e.g.,:
# h2 is the 2d histogram from a root file with 4 x-bins and 2 y-bins
>>> h2.numpy
(array([0.  , 0.  , 0.  , 0.  , 0.  , 0.  , 0.08, 0.06, 0.03, 0.02, 0.  ,
       0.  , 0.01, 0.04, 0.07, 0.1 , 0.  , 0.  , 0.  , 0.  , 0.  , 0.  ]), array([0., 1., 2., 3., 4.]))

The bins with 0 are somewhat consistent with the under/overflow bins (in ROOT the 'real' bins start at bin numbers 7-10; 13-16).  However, from the information returned by the numpy method, it isn't clear (without already knowing) where the 'real' bins begin and end.
Could the TH1Methods class be extended to support 2D histograms such that the above output would instead be something like:
>>> h2.numpy
(
array( [0.08, 0.06, 0.03, 0.02],    # first y-bin
       [0.01, 0.04, 0.07, 0.1] ] ), # second y-bin
array( [ [0., 1., 2., 3., 4.], [0., 1., 2.] ]) . # (x-bins, y-bins)
)

NB: I believe I can recreate what I want using the allvalues, fXaxis, fYaxis, f*axis.fXmin, f*axis.fXmax, and f*axis.fNbins methods. If the bins have variable widths, it appears the f*axis.fXbins method will contain the proper bin edges.

This sounds good. As you can see, I haven't explicitly thought about methods for 2d histograms. If you have in mind what kinds of methods you'd like to see, I've created a stub for TH2Methods.
If you check out (or fork) the issue-92 branch, you can add whatever you want in this class. Any methods or properties that depend only on the f* variables can be added to 2D histograms.
Here's a demo. The tests/samples/hepdata-example.root file contains a 2D histogram named "hpxpy" and a 1D histogram named "hpx":
>>> import uproot      # local branch
>>> f = uproot.open("tests/samples/hepdata-example.root")
>>> f["hpxpy"].hello()
'world'
>>> f["hpx"].hello()
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
AttributeError: 'TH1F' object has no attribute 'hello'

You can probably get the non-underflow/non-overflow bins with a .reshape (to make it 2-d) followed by a slice.

I merged your implementation into scikit-hep/uproot/issue-92 and made my own clean-ups and fixes. There's a pull request to add it to master with a new version number (2.8.33 → 2.9.0 because it's a new feature). I've given you commit access so that you can make changes directly on the pull request to put in any last-minute additions. For example, I had to add a hist2d function so that TH2Methods.__add__ would be able to make new histograms, but I only put in enough functionality for __add__ to work. You might want to make hist2d as fully functional as hist.
When you're satisfied, give me the go-ahead and I'll merge to master and post uproot 2.9.0 on PyPI. Thanks!

Pull request #94, that is.

Closed by #94

Version 2.9.0 is on PyPI. Cheers!


RCA skill

Describe the contribution to the taxonomy
This skill provides the ability to summarize an RCA into when it happened, what was the impact, what was the root cause and what are the corrective actions.
Input given at the prompt

   ...

Response that was received

  ...

Response that is now received instead

  ...

Contribution checklist

[ ] Contribution was tested with lab generate
[ ] No errors or warnings were produced by lab generate
[ ] All commits are signed off (DCO)
[ ] The qna.yaml file was linted and prettified (yaml-validator can do both)

Thank you for your contribution to InstructLab! Unfortunately, once a Github repo is made public, all open PRs are automatically closed since they link against a private repo. We have detected that your PR might have been one of the ones affected by this change. If you are still interested in contributing your improvement, please fill out the following short form by no later than May 3rd, and we will get back to you with the additional steps necessary once we have had time to assess the PRs of those still interested:
https://forms.gle/V7SrPPMZDo6iGDYu8


fix: dont show generate button if create permission for action and pages is absent

Description

Removed the display of generate button on google sheet datasource page for schema preview if the user lacks the permissions for creating actions or pages. Added checks for create:pageActions and create:pages permission to show generate page button.
Disabled the generate new page on datasource cards on active datasources page

PR fixes following issue(s)
Fixes #26181

if no issue exists, please create an issue and ask the maintainers about this first

Media

A video or a GIF is preferred. when using Loom, don’t embed because it looks like it’s a GIF. instead, just link to the video

Type of change

Please delete options that are not relevant.

Bug fix (non-breaking change which fixes an issue)
New feature (non-breaking change which adds functionality)
Breaking change (fix or feature that would cause existing functionality to not work as expected)
Chore (housekeeping or task changes that don't impact user perception)
This change requires a documentation update

Testing

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Also list any relevant details for your test configuration.
Delete anything that is not relevant

[ ] Manual
[ ] Jest
[ ] Cypress

Test Plan

Add Testsmith test cases links that relate to this PR

Issues raised during DP testing

Link issues raised during DP testing for better visiblity and tracking (copy link from comments dropped on this PR)

Checklist:
Dev activity

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] PR is being merged under a feature flag

QA activity:

[ ] Speedbreak features have been covered
[ ] Test plan covers all impacted features and areas of interest
[ ] Test plan has been peer reviewed by project stakeholders and other QA members
[ ] Manually tested functionality on DP
[ ] We had an implementation alignment call with stakeholders post QA Round 2
[ ] Cypress test cases have been added and approved by SDET/manual QA
[ ] Added Test Plan Approved label after Cypress tests were reviewed
[ ] Added Test Plan Approved label after JUnit tests were reviewed

/ok-to-test

/ok-to-test

/ok-to-test


Should we handle apps not on the root level of the dmg/zip?

If the app we want to use as the basis for recipe-building isn't on the root level of the dmg or zip, do we want to dig much farther, or should we error-out?
Two easy examples, both of which require the user to drag a folder to their /Applications folder, rather than an app:

Thinking about this might be out of scope for Recipe Robot, but just wanted to put it out there.

This is does bring up an interesting dilemma. Especially since even if you went one level down looking for an .app bundle, who's to say the destination folder is always"Applications". RR at best would have to assume that's the intended destination (insert danger alert here!).

Well, personally I think these kinds of apps are both annoying and dated. But they are annoyingly still present. We have several at DA which I can come up with right off the top of my head.
Including one called Casper Suite that you might be familiar with...
In almost all of these cases, though, isn't their an alias to the Applications folder that the user is supposed to use to drag their folder into when the disk image mounts?
So would it be possible, as part of scanning the disk image, to os.walk and see if there's an Applications item that is_dir and is_link?

I guess the major deviation from /Applications that I forgot to mention is /Library/Internet Plug-Ins.
That being said, how many internet plugins are there that don't already have recipes for them?

Another exception is prefPanes. I can think of MenuMeters off the top of my head. Should be pretty easy to check for the presence of a bundle ending with .prefPane or .plugin.
I like that idea: Check to see whether there are two items in the disk image, and one of them is an alias to /Applications. If so, we know what to do.

Audacity is another. The Autdacity folder contains both the app as well as some supporting files (help documents etc).

The stated goal of Recipe Robot is "to create new AutoPkg recipes for simple Mac apps." The more examples of the above I see, the more I think that Mac apps that are delivered with nested subfolders do not meet at least one definition of "simple." I'm going to close this one.


ClientModel: Investigate paging pattern for unbranded clients

This is needed for the preview release currently stated for 5/20

Consider the OpenAI paging pattern and other popular paging patterns
Investigate whether a given pattern is generic and popular enough to include in System.ClientModel
For each paging pattern that is adopted by Client Model, create an issue to track the work for implementation/testing.

Why is this p2? Pagination is needed for OpenAI scenarios like Files, Images etc. We currently do not have GA timelines but this is something we will have to think about. For instance, why is this lower priority than Variant type?

Rescoping this to "investigate" because we need to make a decision whether or not there's a paging pattern popular enough that we feel it should be included in Client Model. If the OpenAI implementation is specific to OpenAI, then it should be local to that library.

Related to https://github.com/Azure/azure-sdk-for-net/issues/42487

Addressed by https://github.com/Azure/azure-sdk-for-net/pull/44026


Issue39 generic facts

Coverage decreased (-2.0%) to 94.324% when pulling 234860c6f928e93372849e6dc131f3378868d6c4 on Issue39_GenericFacts into a572c9bb7b70d7c52bec26ca95d0616417f014bb on develop.


Internally manage dependencies and modules

Code
In main.rs
use timers::Config;
fn main() {
    timers::run(config);
}

In lib.rs
pub fn run(config: Config) {}

Issue
graphviz shows = main -> ...main.rs.timers::run but should be ...lib.rs.run
Explanation
Imports are not explicitly clear from rust AST. We have to track import statements and internally manage dependencies and modules.

use timers::Config;
fn main() {
timers::run(config);}
pub fn run(config: Config) {}


Download Mananger

TODO
Still playing around with it and I've only just started.


Highlight Elixir string markdown header correctly

Elixir allows markdown inside its triple-quote heredoc syntax. However,
the "#" used in markdown headers is currently misinterpreted as a
comment. So, if you write this:
@doc """
Get the first name of a user.

## Parameters

- `user` - A User struct.

## Examples

    user = %User{name: "Alice Winston"}
    User.first_name(user)
    "Alice"

"""

Prism interprets the markdown headers as comments, not as part of the
string, and this messes up the coloring.

It's easy to fix, just put the string regular expressions before the
comment regular expression in the elixir component.

Unfortunately, this will lead to other issues (e.g. strings will be highlighted inside comments (breaking them))...
Comments might be used to comment code, and that's why we usually handle it first.
Would it be ok to only change the negative look-ahead in the comment pattern, so that we ignore comments starting with more than one hash?  /#(?![{#]).*/

I'll give it a try and let you know.

Changing the negative lookahead wasn't enough. If it was given this:
@doc """
## Header
"""

It would match on # Header. Since Javascript doesn't support negative lookbehinds, I added a negated capture group to assert that the # is not preceded by any other #s. What do you think of this solution?

 Please use the lookbehind feature provided by Prism, though, so that the char before the hash is not consumed:
'comment': {
	pattern: /([^#])#(?![{#]).*/,
	lookbehind: true
}

Can you also fix the indentation before the comments you added?
I can merge this once it's done ;)

Done! I amended the commit.

Thanks!

Oh, I have to add an alternative to handle the empty comment # and pass the tests.
The final pattern is: /(^|[^#])#(?![{#]).*/m

How do you run the tests?

By running npm test

I'm fixing this now.

It's fixed already! See ccb6566ccb14f365ab221525f09247d775a9bd06

:+1:


Don't use invalid Root in bad version test

The httpBatchStore test TestVersionMismatch() expects a panic,
but the test was actually potentially causing MULTIPLE panics.
One due to the version mismatch, and another due to using an
invalid root.

PTAL


Incorporate mldatafind

Incorporates mldatafind library into timeslide, train and background projects.
Some comments:

Omicron runs over training and testing datasets are now split into separate directories to reduce any confusion

mldatafind authenticate function is now called at the beginning of the background project

channels and state_flags are now passed as a list, one for each ifo. This will allow us to include Virgo and other detectors in the future as channel names ( and state_flags) differ from the LIGO detectors.

We don't fully take advantage of the find_data generator in the timeslide project. This would require a bit of refactoring that I didn't want to attack in this PR

Bit off more than I can chew here so refactoring into smaller PR's


FileNotFoundError: [Errno 2] No such file or directory: './logs/tanks_and_temple_unbounded'

Hi, nice work.
When I run:
python run_FourierGrid.py --program train --config FourierGrid/configs/tankstemple_unbounded/playground_single.py --num_per_block -1 --render_train --render_test --render_video --exp_id 57
I get this error:
FileNotFoundError: [Errno 2] No such file or directory: './logs/tanks_and_temple_unbounded'
What am I missing?
Thx

mkdir logs
This command is in the installation guide.

Thx, but I don't find the command in the installation guide. I created a directory "logs" in the FourierGrid folder because in the root there is one folder called logs (attach an image), and nothing happens, and I get the same error. Can you help me?

Logs is just an empty folder to store all training logs and ckpts and rendering results.

Yes, but in which location must be this ./logs/tanks_and_temple_unbounded folder?
Thx

Quick fix: Just create it at where it goes wrong.

I checked the doc, this instruction is already in the commit list but not in the remote repo now.

I changed the "logs" symlink to "logs_0" and created the logs/tanks_and_temple_unbounded directory, and now it's training. I hope this change doesn't hurt regular training.
Thx


Accessibility for components

Would a PR be accepted that added accessible outlines, tab navigation and screen readability to these components?

Sure. I may not be able to pull it in quite yet though. Planning some major code chaange to make it work with react. Also planning to create a mono repo for ease : https://github.com/wiredjs/wired-elements/issues/11
I think it would be much easier to accept PRs after that is done.

Related: https://github.com/wiredjs/wired-toggle/issues/4

All the components are in a monorepo now! I may not have time to work on these in the near future, so any help with accessibility is welcome.

Button accessibility added by https://github.com/wiredjs/wired-elements/pull/28
Slider accessibility added by https://github.com/wiredjs/wired-elements/pull/35

With https://github.com/wiredjs/wired-elements/pull/41 all components are now accessible.


Work navigation

Navigation from the header to the work section was missing because the code was accessing a wrong place. The work title is defined in data/work.toml.

Thanks for providing this fix :+1:  - it seems I've missed this spot while refactoring the theme.


can we only evaluate  the mmlu_dataset  when sh   sh scripts/finetune_guanaco_7b.sh?

Hi, have you figured out this issue?


Workmanager

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.08%) to 61.287%

Totals

Change from base Build<PHONE_NUMBER>:
0.08%

Covered Lines:
4393

Relevant Lines:
6651

💛  - Coveralls


Is t265 supported in unreal?

I have not managed to compile the unreal wraper yet but I thought I would ask first. Is there any support for Pose from T265 in Unreal. I cant seem to find any examples or mention of it in the https://github.com/IntelRealSense/librealsense/tree/development/wrappers/unrealengine4

I think it's going to be a couple of months before wrappers are supported for T265

Indeed it can take some time until dedicated tracking examples make it into all the wrappers, however, I believe most if not all wrappers have access to pose stream type and frames.


Queue published blocks from future slots

PR Description
With the validator moving to use an independent timer instead of responding to slot events from the beacon chain, it's possible that it will create a block at the start of a slot slightly before the beacon chain has actually reached that slot. Previously, the block would be rejected and dropped - now it is added to the future blocks queue like gossiped blocks are and processed once the slot is reached.
Fixed Issue(s)
#1918
Documentation

[x] I thought about documentation and added the documentation label to this PR if updates are required.

Logged https://github.com/PegaSysEng/teku/issues/2912 to do further tidy up of BlockManager which is in a bit of a weird position now.


FIX fix array_map function with array index function without checkout arg…

Proposed changes
fix array index function without checkout argument type
which would make a core

Issue Number: close #xxx

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

run p0


Special underlining logic no longer necessary?

Chrome (and other browsers I think) now underline more intelligently, so the special-casing of underlining is not just unnecessary, depending on your point of view it's actually intrusive. Perhaps the time has come or will soon come to get rid of it. Meanwhile, I have found that this works:
a:link { all: unset; }

And then putting back underlines yourself with text-decoration if you want.

Chrome (and other browsers I think) now underline more intelligently,

Is there a chart of browser support for underlining that clears descenders? I can't find one on a quick search, and last I heard support was on its way but not arrived. (The quality of that support would also have to compare favorably to our current approach.)
Tufte CSS is happy with the current approach until the feature is supported widely across browsers. Just Chrome support is unsatisfactory for our purposes.

I'm adding to this thread only to caution against confusing "support for underlining that clear descenders" with support for text-decoration-skip-ink. I believe Safari desktop and mobile do not yet support this, yet their default behavior elegantly renders without clashing with descenders.

Is there a chart of browser support for underlining that clears descenders?

https://caniuse.com/#feat=text-decoration — note footnotes 3, 4, and 5

Thanks for the link, Joel. Closing this for now. The time is soon but not now. Let's all keep an eye on browser support for descender-clearing both by default and through text-decoration-skip-ink, and either comment here or open a new issue or PR when such a solution is available.

For reference, the browser support information for text-decoration-skip-ink can be checked directly at caniuse: https://caniuse.com/#feat=mdn-css_properties_text-decoration-skip-ink (although the data comes from MDN).


Xlint:path error with JUNG, Gradle and Error Prone

Hi Error Prone team.
This is an issue which I posted already on https://github.com/jrtom/jung/issues/66. @jrtom seems to be at a loss as to what's causing it, so I wonder if someone on the Error Prone team can help me.
I've pasted the original issue text below so that people don't have to follow the link to read it.

When I try to run gradle run with the following build.gradle
plugins {
  id 'application'
  id 'java'
  id 'net.ltgt.errorprone' version '0.0.8'
}

group 'org.jbduncan'
version '1.0-SNAPSHOT'

sourceCompatibility = 1.8

mainClassName = 'org.jbduncan.helloworld.HelloWorld'

repositories {
  jcenter()
}

dependencies {
  compile 'net.sf.jung:jung-graph-impl:2.1.1'
  errorprone 'com.google.errorprone:error_prone_core:2.0.11'
}

tasks.withType(JavaCompile) {
  options.encoding = 'UTF-8'
  options.compilerArgs = [
    '-Xlint:all',
    '-Werror'
  ]
}

and this class
package org.jbduncan.helloworld;

public final class HelloWorld {
  public static void main(String[] args) {
    System.out.println("Hello, world!");
  }
}

it emits the following message.
:compileJava
warning: [path] bad path element "C:\Users\Jonathan\.gradle\caches\modules-2\files-2.1\net.sf.jung\jung-graph-impl\2.1.1\8293acb2ab4c00a3939cb99a8751e5d38a4299dc\jung-api-2.1.1.jar": no such file or directory
warning: [path] bad path element "C:\Users\Jonathan\.gradle\caches\modules-2\files-2.1\net.sf.jung\jung-graph-impl\2.1.1\8293acb2ab4c00a3939cb99a8751e5d38a4299dc\guava-19.0.jar": no such file or directory
warning: [path] bad path element "C:\Users\Jonathan\.gradle\caches\modules-2\files-2.1\net.sf.jung\jung-api\2.1.1\e47ee4efdfacce12f0af620747d9d0e44bf2eaa4\guava-19.0.jar": no such file or directory
error: warnings found and -Werror specified
1 error
3 warnings
:compileJava FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':compileJava'.
> Compilation failed with exit code 1; see the compiler error output for details.

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

BUILD FAILED

Total time: 5.488 secs

When I investigate the contents of my Gradle cache, I can see that, indeed, the jar files mentioned above simply don't exist.
When I look into C:\Users\Jonathan\.gradle\caches\modules-2\files-2.1\net.sf.jung\jung-graph-impl\2.1.1\8293acb2ab4c00a3939cb99a8751e5d38a4299dc\jung-graph-impl-2.1.1.jar, the META-INF/MANIFEST.MF contains this text.
Manifest-Version: 1.0
Archiver-Version: Plexus Archiver
Created-By: Apache Maven 3.0.5
Built-By: jrtom
Build-Jdk: 1.8.0-google-v7
Class-Path: jung-api-2.1.1.jar guava-19.0.jar

I get the same problem with JUNG versions 2.1 and 2.0, and no other library with dependencies I've tried seems to have this problem.
However the problem goes away when I exclude from build.gradle the lines id 'net.ltgt.errorprone' version '0.0.8' and errorprone 'com.google.errorprone:error_prone_core:2.0.11', so it's not clear to me if this is a problem with JUNG or if it's gradle-errorprone-plugin or Error Prone related.

(Since writing the original issue, I upgraded from Error Prone 2.0.11 to 2.0.13, but that didn't seem to solve my problem.)

Apparently, it's the expected behavior of JavaC; see: http://bugs.java.com/bugdatabase/view_bug.do?bug_id=6485027 (and related, specifically http://bugs.java.com/bugdatabase/view_bug.do?bug_id=4212732), along with https://github.com/google/error-prone-javac/blob/90149b22e202e7b24bfafc80df7509c8fb490ee7/src/jdk.compiler/share/classes/com/sun/tools/javac/file/Locations.java#L317-L329 (which is the post-8 pre-9 version of JavaC used by ErrorProne), https://github.com/google/error-prone-javac/blob/90149b22e202e7b24bfafc80df7509c8fb490ee7/test/tools/javac/Paths/Class-Path.sh, and https://github.com/google/error-prone-javac/blob/90149b22e202e7b24bfafc80df7509c8fb490ee7/test/tools/javac/Paths/TestCompileJARInClassPath.java (among others).
So the question actually is: why isn't the error happening without ErrorProne?

So the question actually is: why isn't the error happening without ErrorProne?

Error Prone invokes javac using internal APIs, and gradle uses JSR 199 which doesn't handle -Xlint:path correctly: http://mail.openjdk.java.net/pipermail/compiler-dev/2016-October/010455.html

FWIW, running Gradle with --debug, I extracted the arguments it passes to JavaC:
17:33:04.984 [DEBUG] [org.gradle.api.internal.tasks.compile.NormalizingJavaCompiler] Compiler arguments: -source 1.8 -target 1.8 -d /…/build/classes/main -g -encoding UTF-8 -sourcepath /…/build/tmp/compileJava/emptySourcePathRef -Xlint:all -Werror -classpath /…/.gradle/caches/modules-2/files-2.1/net.sf.jung/jung-graph-impl/2.1.1/8293acb2ab4c00a3939cb99a8751e5d38a4299dc/jung-graph-impl-2.1.1.jar:/…/.gradle/caches/modules-2/files-2.1/net.sf.jung/jung-api/2.1.1/e47ee4efdfacce12f0af620747d9d0e44bf2eaa4/jung-api-2.1.1.jar:/…/.gradle/caches/modules-2/files-2.1/com.google.guava/guava/19.0/6ce200f6b23222af3d8abb6b6459e6c44f4bb0e9/guava-19.0.jar /…/src/main/java/org/jbduncan/helloworld/HelloWorld.java -XDuseUnsharedTable=true

Now running JavaC with those same arguments gives the same error as with ErrorProne:
$ javac -source 1.8 -target 1.8 -d /…/build/classes/main -g -encoding UTF-8 -sourcepath /…/build/tmp/compileJava/emptySourcePathRef -Xlint:all -Werror -classpath /…/.gradle/caches/modules-2/files-2.1/net.sf.jung/jung-graph-impl/2.1.1/8293acb2ab4c00a3939cb99a8751e5d38a4299dc/jung-graph-impl-2.1.1.jar:/…/.gradle/caches/modules-2/files-2.1/net.sf.jung/jung-api/2.1.1/e47ee4efdfacce12f0af620747d9d0e44bf2eaa4/jung-api-2.1.1.jar:/…/.gradle/caches/modules-2/files-2.1/com.google.guava/guava/19.0/6ce200f6b23222af3d8abb6b6459e6c44f4bb0e9/guava-19.0.jar /…/src/main/java/org/jbduncan/helloworld/HelloWorld.java -XDuseUnsharedTable=true
warning: [path] bad path element "/…/.gradle/caches/modules-2/files-2.1/net.sf.jung/jung-graph-impl/2.1.1/8293acb2ab4c00a3939cb99a8751e5d38a4299dc/jung-api-2.1.1.jar": no such file or directory
warning: [path] bad path element "/…/.gradle/caches/modules-2/files-2.1/net.sf.jung/jung-graph-impl/2.1.1/8293acb2ab4c00a3939cb99a8751e5d38a4299dc/guava-19.0.jar": no such file or directory
warning: [path] bad path element "/…/.gradle/caches/modules-2/files-2.1/net.sf.jung/jung-api/2.1.1/e47ee4efdfacce12f0af620747d9d0e44bf2eaa4/guava-19.0.jar": no such file or directory
error: warnings found and -Werror specified
1 error
3 warnings

Note that the arguments passed by Gradle are the same whether you use the gradle-errorprone-plugin or not.
So, from my point of view, it's a bug in Gradle (and other build tools; I could similarly reproduce this with Maven: build succeeds, running with -X to get the arguments and then running JavaC on the command-line with the same arguments fails, with the same output, modulo JAR paths; Ant correctly fails the compilation though), and it's a bug in JUNG for deploying such JARs to a Maven repository.
It's arguable too that Gradle and Maven explicitly ignore such errors by default because there are people deploying such JARs, and I could then have a look at doing the same in the gradle-errorprone-plugin. It's interesting to note that Maven has the same behavior though: compiles without complaining with standard maven-compiler-plugin, fails the build when using ErrorProne.
Also, unsurprisingly, compilation works with Bazel, as it extracts an ijar and does not directly pass the JARs to JavaC/ErrorProne.
For the record, here's the Maven POM I used to replicate the issue with Maven:
<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">

  <!-- POM file generated with GWT webAppCreator -->
  <modelVersion>4.0.0</modelVersion>
  <groupId>test</groupId>
  <artifactId>Test</artifactId>
  <version>1.0-SNAPSHOT</version>
  <name>test.Test</name>

  <properties>
    <maven.compiler.source>1.8</maven.compiler.source>
    <maven.compiler.target>1.8</maven.compiler.target>
    <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
    <project.reporting.outputEncoding>UTF-8</project.reporting.outputEncoding>
  </properties>

<dependencies>
<dependency>
<groupId>net.sf.jung</groupId>
<artifactId>jung-graph-impl</artifactId>
<version>2.1.1</version>
</dependency>
</dependencies>

  <build>
    <plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<version>3.5.1</version>
<configuration>
  <compilerArgs>
    <arg>-Xlint:all</arg>
    <arg>-Werror</arg>
  </compilerArgs>
  <showWarnings>true</showWarnings>
  <showDeprecations>true</showDeprecations>
<compilerId>javac-with-errorprone</compilerId>
        <forceJavacCompilerUse>true</forceJavacCompilerUse>
</configuration>
      <dependencies>
        <dependency>
          <groupId>org.codehaus.plexus</groupId>
          <artifactId>plexus-compiler-javac-errorprone</artifactId>
          <version>2.5</version>
        </dependency>
        <!-- override plexus-compiler-javac-errorprone's dependency on
             Error Prone with the latest version -->
        <dependency>
          <groupId>com.google.errorprone</groupId>
          <artifactId>error_prone_core</artifactId>
          <version>2.0.13</version>
        </dependency>
      </dependencies>
</plugin>
    </plugins>
  </build>
</project>

and the Ant build.xml (using the JARs downloaded by Maven):
<project basedir=".">
  <target name="javac">
    <javac srcdir="src/main/java" destdir="target/classes" source="1.8" target="1.8" encoding="UTF-8" includeantruntime="false">
      <compilerarg value="-Xlint:all"/>
      <compilerarg value="-Werror"/>
      <classpath>
        <pathelement location="/…/.m2/repository/net/sf/jung/jung-graph-impl/2.1.1/jung-graph-impl-2.1.1.jar" />
        <pathelement location="/…/.m2/repository/net/sf/jung/jung-api/2.1.1/jung-api-2.1.1.jar" />
        <pathelement location="/…/.m2/repository/com/google/guava/guava/19.0/guava-19.0.jar"/>
      </classpath>
    </javac>
  </target>
</project>

and finally the Bazel WORKSPACE:
maven_jar(
	name = "net_sf_jung_jung_graph_impl",
	artifact = "net.sf.jung:jung-graph-impl:2.1.1",
)
maven_jar(
	name = "net_sf_jung_jung_api",
	artifact = "net.sf.jung:jung-api:2.1.1",
)
maven_jar(
	name = "com_google_guava_guava",
	artifact = "com.google.guava:guava:19.0",
)

and BUILD
java_binary(
	name = 'helloworld',
	srcs = glob(['src/main/java/**/*.java']),
	deps = [
		'@net_sf_jung_jung_graph_impl//jar',
		'@net_sf_jung_jung_api//jar',
		'@com_google_guava_guava//jar',
	],
	main_class = 'org.jbduncan.helloworld.HelloWorld',
	javacopts = ['-Xlint:all', '-Werror'],
)

FWIW, using <forceJavacCompilerUse>true</forceJavacCompilerUse> without ErrorProne will break a Maven build (respects -Xlint:path, from the -Xlint:all).
And similarly for Gradle when using options.fork = true and options.forkOptions.executbale = 'javac'.

The fork/forceJavacCompilerUse options cause the javac CLI to be used instead of JSR 199, right? That would get the same non-buggy option handling Error Prone calls into.

Also, unsurprisingly, compilation works with Bazel, as it extracts an ijar and does not directly pass the JARs to JavaC/ErrorProne.

ijar deletes MANIFESTs from the jars it processes, which I consider to be a feature.

Hmm, sounds to me like this is half a bug in JUNG and half a bug in JSR 199. Is my understanding correct?
What I've not yet understood is, if it's indeed half a bug in JUNG, how could I or @jrtom fix it on the JUNG side?
I see that @cushon has just raised the JSR 199 side of it with the OpenJDK devs at http://mail.openjdk.java.net/pipermail/compiler-dev/2016-October/010455.html. Does this mean we now wait until it's fixed on their end?
I also see that @tbroyer seems to think it's a bug with Gradle. Has this been raised on the Gradle forums yet? If not, I'd be happy to link this issue in the topic I raised.

I don't think there's a gradle bug here beyond the underlying JSR 199 bug.
I suggest having JUNG not set Class-Path in the jar's manifest.  Removing <addClasspath> from the pom should do it: https://github.com/jrtom/jung/blob/6c0a8e568a2215c15a8195f3ec75321f6241ce48/pom.xml#L152
Setting Class-Path makes assumptions about the filesystem layout of build tools that will be using the jars, and interacts badly with other dependency resolution mechanisms.

@cushon forceJavacCompilerUse forces the use of the com.sun.….Main class, and fork in Gradle will fork a cli javac process. So yes, they force not using jsr199, so bypass the bug.

ijar deletes MANIFESTs from the jars it processes, which I consider to be a feature.

👍
@jbduncan Both Maven and Gradle use jsr199 by default, so indeed they're not direct at fault. FWIW, I believe old versions of Gradle allowed using JavaC Main the same way forceJavacCompilerUse does in Maven, this is no longer an option.

Thank you everyone, @cushon and @tbroyer included. It seems it was a bug in how the JUNG jar was being built, which I've submitted a fix for, so I'm closing this issue for now.
@cushon, on a related note, have you received any news regarding the bug in JSR 199 which you queried about at http://mail.openjdk.java.net/pipermail/compiler-dev/2016-October/010455.html?


Reformat shifting bytes

Fixes #123

would it make more sense to call it something like shiftLeftAsUInt or something?


Add cylc 6.4.1 and rose 2015.04.1

resolution_fixed   |    by<EMAIL_ADDRESS>
Install latest versions of rose and cylc.
Investigate setting defaults to these versions.

Issue migrated from trac:190 at 2024-01-31 18:13:01 +1100

<EMAIL_ADDRESS>commented

When communicating status back to accessdev, cylc 6.3.0 effectively does
ssh accessdev /usr/local/cylc/bin/cylc started

This gets handled by the remote-job-submission command.
However cylc 6.4.1 adds an environment variable before the command, effectively
ssh accessdev CYLC_VERSION=6.4.1 /usr/local/cylc/bin/cylc started

This fails before even getting as far as the remote-job-submission command.
Temporarily working around this by removing line
command += ["CYLC_VERSION=%s" % CYLC_VERSION]

from remote.py

<EMAIL_ADDRESS>changed owner from `` to mrd599

<EMAIL_ADDRESS>changed status from new to assigned

<EMAIL_ADDRESS>edited the issue description

<EMAIL_ADDRESS>commented

Also need to add a link to the new default cylc version in /opt/remote-job-submission/rbin.d
Presently hardwired in modules/accessdevnode/manifests/init.pp: but ideally it should pick up the cylc default_version set in project.yaml.

<EMAIL_ADDRESS>changed _comment0 which not transferred by tractive

<EMAIL_ADDRESS>commented

If the cylc status commands on raijin can't include CYLC_VERSION in the command line then they'll always communicate with the default version on accessdev. In turn this creates a message that gets sent to the controlling cylc process on accessdev via pyro.
cylc-5.4.14 created messages like
model.2001010100 started at 2015-05-23T04:10:49

but cylc-6 includes a timezone, e.g.
model.2001010100 started at 2015-05-23T04:10:49Z

cylc uses a regexp to strip off the time part and get the status (e.g. started). The regexp used by cylc5 doesn't handle the timezone and so the messages aren't interpreted properly and the suite hangs. Using the cylc6 regexp works ok.

<EMAIL_ADDRESS>commented

raijin:~access/bin/cylc changed to do
if [[ $CYLC_VERSION = 6.4.1 ]]; then
    module load rose/2015.04.1
elif [[ $CYLC_VERSION = 6* ]]; then
    module load rose/2015.02.0
else
    module load rose/2014-04
fi

We need something cleverer than this in the longer term.
After updating default version of cylc on accessdev-test to 6.4.1, cylc started failed
raijin% ssh accessdev-test /usr/local/cylc/6.4.1/bin/cylc started
Failed to get version number!

Cylc gets the version number by calling git describe. On accessdev
/opt/remote-job-submission/bin/git has
parent="$(/bin/ps -o command= -p $PPID)"
#echo "$parent" 1>&2

if [ "$parent" = "/bin/bash /usr/local/cylc/admin/get-repo-version" ]; then
        exec /usr/bin/git "$@"
fi

and otherwise fails. In this case the parent is the default version cylc/cylc-6.4.1 rather than cylc. This has been broken since we installed cylc-6.3.0 but not causing a problem because cylc 5.4.14 returned an empty version number rather than a fatal error.
Matching on a regular expression like
cylc_regexp="/bin/bash /usr/local/cylc/cylc-[.0-9]*/admin/get-repo-version"
if [[ $parent =~  $cylc_regexp ]]; then

would work.

<EMAIL_ADDRESS>changed _comment0 which not transferred by tractive

<EMAIL_ADDRESS>commented

Tested updating accessdev-test. Simple cylc5 suite kept running through the entire process without a problem.
rose bush now shows job.out and job.err from cylc6 suites properly.
rosie go shows the MOSRS repository properly. Just need $HOME/.metomi/rose.conf with
[rosie-id]
prefix-username.u = name

<EMAIL_ADDRESS>changed _comment0 which not transferred by tractive

<EMAIL_ADDRESS>commented

Cylc6 jobs now work properly. However a cylc 5 suite will communicate back with a command like
ssh accessdev /usr/local/cylc/bin/cylc started

The lack of a version number means it will get the default version of cylc and the timezone issue above recurs.
Possibilities are

Modify cylc-5.4.14 on raijin to include the version number when communicating
Patch cylc on accessdev to use a new regexp
Modify the cylc wrapper on accessdev to default to the older versions for commands like started but the normal default otherwise

The first seems the simplest and least likely to cause problems with later updates of accessdev.
Created ~access/apps/cylc-5.4.14.sendversion with a change to remote.py to add the version number. Checked that this worked properly with existing setup on accessdev and new setup on accessdev-test and then modified ~access/app/cylc/5.4.14 to point to this version.

<EMAIL_ADDRESS>commented

Chris Allen has patched the remote-job-submission script so that the environment variable is passed properly. This makes previous comment irrelevant. Also patched the remote-job-submission git script to use the regexp.

<EMAIL_ADDRESS>changed status from assigned to closed

<EMAIL_ADDRESS>changed status from closed to reopened

<EMAIL_ADDRESS>changed resolution from `` to fixed

<EMAIL_ADDRESS>changed resolution from fixed to ``

<EMAIL_ADDRESS>commented

rose-bush on accessdev isn't showing the job list of a suite or job output files, though it does on accessdev-test.
Compare
https://accessdev.nci.org.au/rose-bush/jobs/mrd599/simple_cycle6
and
https://accessdev-test.nci.org.au/rose-bush/jobs/mrd599/simple_cycle6
Both are running 2014.05.1
accessdev is showing a job list for a cylc5 suite so somewhere it's still using the old directory structure. Some default not updated somewhere?

<EMAIL_ADDRESS>changed _comment0 which not transferred by tractive

<EMAIL_ADDRESS>changed status from reopened to closed

<EMAIL_ADDRESS>changed resolution from `` to fixed

<EMAIL_ADDRESS>commented

Error messages suggested it was using the new version of rose bush but still using an old version of some other rose code, presumably cached somewhere. Probably didn't happen on accessdev-test because old version of rose-bush wasn't used before the update.
Fixed by restarting apache on accessdev.


[draft] Replace use_auth_token arg by token everywhere

Fix https://github.com/huggingface/huggingface_hub/issues/1094.
This is a very first draft (and broken).

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


support pyarrow recordbatch as a valid data source for writing Iceberg table

Feature Request / Improvement
currently using this in a an environment with limited RAM
  df=final.arrow()
  catalog , table_location = connect_catalog(storage)
  catalog.create_table_if_not_exists(db+".scada",schema=df.schema,location= table_location+f'/{db}/scada' )
  catalog.load_table(db+".scada").append(df)

I get sometimes  out of memory because arrow table needs to be fully materialized in memory,  I can generate recordbatch from my source system which will use less memory,

@djouallah Thanks for raising this. To clarify, does the final.arrow() cause an OOM, or the .append operation?

Append operation cause OOM


Interface support added

Addresses #29 and #14. This PR adds interface support on the merger:

Added tests for checking the correct merging of interfaces.
Added tests for checking the correct merging of methods defined on interfaces.
Added tests for checking the correct merging of properties defined on interfaces.
Added tests for checking the correct merging of index signatures defined on interfaces.

Also added:

The possibility to merge comments that are in class and interface declarations.
extends and implements now get merged.


Graph shall deliver historical balances

User Story
As user I want to see the current and historical token balances of a DAO treasury so I can get insights about their wealth development. In order to enable Frontend to build it we need a Graph update.
Acceptance Criteria

History: Graph should be queryable for: blocknumber[], wallet address, currencyID & balance
Latest: Graph should be queryable for: wallet address, currencyID & balance

Additional Information

is blocking frontend ticket https://github.com/gamedaoco/gamedao-haiku/issues/310

How to test

open graph and find balance queries and submit: blocknumber or range of blocknumber for a given wallet address and currencyID to retrieve balances
check current balance with subscribing to the current balance

We've already discussed a number of different approaches in the scope of this task, but the final one is next:

iterate over blocks
read Balances and Token related events from every block
get balance data directly from the chain's storage for each account mentioned in the block's events

I think the best would be to utilize Subsquid and not implement a new service (reuse ORML, DB, blocks processing logic).
With the old Subsquid's processor implementation, I'm struggling of finding a way to iterate over blocks. With the newest Subsquid it's possible.
Since the migration to Firesquid was still one of our high-priority tasks, my suggestion would be to do #160 first and then switch to this task.
@2075 does it make sense to you?
cc: @5-mark @vayesy

@vovacha ACK. ETA?

#160 - the main complexity there - is a new batch processor implementation. It looks more like 3 SP, but there is some uncertainty (1-3 days).
#202 (current) - 3 SP (1-2 days).
Ok, I'm switching immediately to the #160 then.

@vovacha what is the status here?

Done. Test env: https://test.graph.dev.sub.zero.io/


TAP: "# tests N" non-standard?

I can't find anything in the TAP spec that suggests/implies that printing out a "# tests N" summary is within specification. Should it be removed it from TAP output?

I believe @vdemedes modeled our output after node-tap (which I believe uses the draft v14 spec)

Yeah, I think I used tap or tape when building TAP support into AVA.

Oh, so why does it print "TAP version 13"? ;)

I believe v14 is backward compatible in most ways. Any additions were done as comment directives. node-tap still prints v13 because v14 isn't officially recognized yet. But tap-mocha-reporters recognize many v14 directives.
As I recall the v14 draft was born from the extensions node-tap added to the spec.

I couldn't find anything about v14, can you post a link?

https://github.com/TestAnything/testanything.github.io/pull/36

@isaacs Seems your PR https://github.com/TestAnything/testanything.github.io/pull/36 has been open for a while. What would it take to get it merged? Anything we can help with?

Thanks for the link

I think we should also take into consideration that if we're going to use a draft specification, the TAP output that AVA produces will likely break most reporters in some way. I would be more comfortable with sticking to v13, personally, because I want to use tools that are available today and not have to wait for things to get updated to v14 (which as @sindresorhus points out has been sitting in discussion for several months).

the TAP output that AVA produces will likely break most reporters in some way

Not really. We are following the output of the two most popular tap producing libraries on Node (node-tap and tape). From the first line of that PR:

[v14] seeks to ratify existing behavior of TAP harnesses and producers

In other words - codify the existing reality.

it stands to reason that v14 will be backwards compatible to v13, but not the other way around

Not really. v14 output should be interpreted just fine by v13 consumers (though perhaps not as pretty as it could).

Well, I said that based on the fact that other reporters like faucet seem to get confused in certain situations (maybe it's just an opportunity to get faucet up to v14 spec, then, and any others that can't parse the newer spec output can probably be considered edge cases). I'm fine with whatever the consensus is, just wanted to open the discussion. Thanks for the input. :grinning:

maybe it's just an opportunity to get faucet up to v14 spec

It's been 2 years since a faucet release. That it works at all is a testament to good backward compatible design built in to the TAP protocol.
That said - if the problem is just the # tests N line, that could be removed. (Though I think that's actually something we emulated from tape instead of the spec - so it is a bit weird it doesn't work with faucet as it's from the same author).

That in particular "works" (in the sense that it just ignores it and doesn't suppress the line).

We (and by that I mean, mostly I) need to get back to pushing TAP 14 over the finish line.  There were some good bits of feedback from the last round of comment on the PR, and I just haven't gotten around to incorporating them yet.  I should probably spend more time on the spec, and a little bit less on node-tap, I suppose, but when I'm not doing my "real" job, I try to just let the spirit guide me :)
At the current state of things, the latest and greatest versions of node-tap, prove, and Test::More are pretty much in alignment.
The reason why node-tap's output says "TAP version 13" is because the TAP 13 spec requires it!  However, TAP is a very "anything goes" protocol, so the other stuff like nested tests and such is pretty ambiguous.  Anything that is prefixed by whitespace that isn't yaml should be ignored by a consumer, so that's why child tests work.  If you're not down with them, you just get the roll-up, and it's less informative, but not incorrect.  (Even the idea of whether # 4 tests, 2 pass is a "comment" or a "directive" is very unclear, but it is clear that consumers should do nothing with it.)
I'd recommend, especially in the JavaScript world, to follow the not-yet-fully-birthed TAP14 specification.  What you actually print on the version line is mostly irrelevant.

Thanks @isaacs