Possible bug in SimConcretizationStrategySingle

The _concretize function in concretization_strategies/single.py checks for exactly 0 solutions instead of exactly 1 solution:
Original:
    def _concretize(self, memory, addr):
        addrs = self._eval(memory, addr, 2)
        if len(addrs) == 0:
            return addrs

Probably intended:
    def _concretize(self, memory, addr):
        addrs = self._eval(memory, addr, 2)
        if len(addrs) == 1:
            return addrs

lol. You are right. This will be fixed in angr's wip/the_end_times branch.


[wip] Adding redirects to /developer-plus/signup.

Fixes #659

Creates a 301 (permanent) redirect from /devtrial to /developer-plus/signup.
Creates a 302 (temporary) redirect from /signup to /developer-plus/signup (since /signup is pretty broad in scope and we might decide to do something else with it in the future).

How are you feeling about this PR now? Would you want to bring this in still?

Please don't commit this change - /signup is our active page. Thanks!

Okee doke, should we close this then?


Backup fails to delete previous backup file

Simple Backup: 1.1.0
OS: Windows 11 Pro
Joplin: 2.9.1 (prod, win32)
Issue
Consistently, when I open Joplin, I get a message that a previous backup file doesn't exist when it does.

More Information
This started happening a few weeks ago, prior to updating to Simple Backup 1.1.0, so I don't think it's a Simple Backup version issue.
I've tried the following:

Set the entire Joplin Backup folder to allow offline access
Restart Joplin and manually ran backup

I may have had a false negative with number 2. I assumed that, when running a manual backup, older backups would be deleted. But I can't confirm if that's the expected behavior. The reason I wanted to run that test is in case Joplin is starting before Google Drive and is capturing file system information early. In short, maybe Joplin doesn't believe the G drive exists. Or, maybe SB doesn't.

Hm I'm not sure if this has todo with the G drive and how it handles the files in the file system.
The G Drive is accessible, because a new backup is created and the old backup set would be deleted after the creation.
The Files reald offline accessible, because the other files have a cloud symbol.

I just did a bunch more thorough testing. Conclusions and tests below. What
other troubleshooting do you suggest? Is there debug logging I can enable?
Conclusions

Joplin or SB incorrectly stores the backup path when entered directly
into the text control. (Works correctly using the Browse button.
Joplin or SB incorrectly displays the backup path when it contains
spaces.
Deleting old backup sets isn't working regardless of path. (Google
Drive is not the problem, nor is spaces in the path.)

SB Config
[image: image.png]
Backup Info:
[{"name":"20220713-1041.7z","date":1657730443323},{"name":"20220717-1812.7z","date":1658103122905},{"name":"20220718-0930.7z","date":1658158191828},{"name":"20220719-1020.7z","date":1658247590005},{"name":"20220720-1024.7z","date":1658334229471},{"name":"20220721-1024.7z","date":1658420663602},{"name":"20220721-1043.7z","date":1658421806451},{"name":"20220721-1416.7z","date":1658434564894},{"name":"20220722-0708.7z","date":1658495298124},{"name":"20220723-1525.7z","date":1658611519524},{"name":"20220724-0635.7z","date":1658666067405},{"name":"20220726-1000.7z","date":1658851196577},{"name":"20220726-1045.7z","date":1658852847081},{"name":"20220726-1103.7z","date":1658854914269},{"name":"20220726-1223.7z","date":1658859757871},{"name":"20220726-1226.7z","date":1658859945446}]
Tests

A simple Joplin quit/restart today, got the same backup error message.
Quit > set all files to offline access > restart. Same error.

I was going to try changing the backup path, and when I checked Backup
settings I saw this:
[image: image.png]
However, the SQLite settings table does have the correct value:
[image: image.png]
So, test steps.

Copy all backups to  C:\Users\charl\Downloads\Joplin Backup

In Joplin, change backup path using copy/paste
to C:\Users\charl\Downloads\Joplin Backup

Quit and restart

Check how path is displayed. OK.
[image: image.png]

Wait for on-startup backup. Get bizarre error message. What's with
that path?
[image: image.png]

What's in the database?
[image: image.png]

On a whim, tried browsing to the backup folder and selecting it. This
resulted, again, in the truncated path displayed. Database value is correct.
[image: image.png]

Renamed the backup folder, removing spaces. Pasted in the new path.
The path displays correctly, but is stored wrong.
[image: image.png]
[image: image.png]

Use the Browse button to select the path. This time all is correct.
[image: image.png]

Quit/restart. Same error!
[image: image.png]

--
Charles L Flatt
"If my life wasn't funny it would just be true, and that is unacceptable."
--Carrie Fisher
On Tue, Jul 26, 2022 at 12:02 PM JackGruber @.***>
wrote:

Hm I'm not sure if this has todo with the G drive and how it handles the
files in the file system.
The G Drive is accessible, because a new backup is created and the old
backup set would be deleted after the creation.
The Files reald offline accessible, because the other files have a cloud
symbol.
—
Reply to this email directly, view it on GitHub
https://github.com/JackGruber/joplin-plugin-backup/issues/45#issuecomment-1195808528,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAWE24YCXRNNG7XKEMXFGBTVWAR2RANCNFSM54WQX22A
.
You are receiving this because you authored the thread.Message ID:
@.***>

(Repost to include the images directly. Email replied don't support Markdown.)
I just did a bunch more thorough testing. Conclusions and tests below. What
other troubleshooting do you suggest? Is there debug logging I can enable?
(Updated to include images.)
Conclusions

Joplin or SB incorrectly stores the backup path when entered directly
into the text control. (Works correctly using the Browse button.
Joplin or SB incorrectly displays the backup path when it contains
spaces.
Deleting old backup sets isn't working regardless of path. (Google
Drive is not the problem, nor is spaces in the path.)

SB Config

Backup Info:
[{"name":"20220713-1041.7z","date":1657730443323},{"name":"20220717-1812.7z","date":1658103122905},{"name":"20220718-0930.7z","date":1658158191828},{"name":"20220719-1020.7z","date":1658247590005},{"name":"20220720-1024.7z","date":1658334229471},{"name":"20220721-1024.7z","date":1658420663602},{"name":"20220721-1043.7z","date":1658421806451},{"name":"20220721-1416.7z","date":1658434564894},{"name":"20220722-0708.7z","date":1658495298124},{"name":"20220723-1525.7z","date":1658611519524},{"name":"20220724-0635.7z","date":1658666067405},{"name":"20220726-1000.7z","date":1658851196577},{"name":"20220726-1045.7z","date":1658852847081},{"name":"20220726-1103.7z","date":1658854914269},{"name":"20220726-1223.7z","date":1658859757871},{"name":"20220726-1226.7z","date":1658859945446}]

Tests

A simple Joplin quit/restart today, got the same backup error message.
Quit > set all files to offline access > restart. Same error.

I was going to try changing the backup path, and when I checked Backup
settings I saw this:

However, the SQLite settings table does have the correct value:

So, test steps.

Copy all backups to  C:\Users\charl\Downloads\Joplin Backup
In Joplin, change backup path using copy/paste to C:\Users\charl\Downloads\Joplin Backup
Quit and restart
Check how path is displayed. OK.

Wait for on-startup backup. Get bizarre error message. What's with that path?

What's in the database?

On a whim, tried browsing to the backup folder and selecting it. This resulted, again, in the truncated path displayed. Database value is correct.

Renamed the backup folder, removing spaces. Pasted in the new path. The path displays correctly, but is stored wrong.

Use the Browse button to select the path. This time all is correct.

Quit/restart. Same error!

I think there a different bugs with the Folder selector. The first Bug I have logged.
https://github.com/laurent22/joplin/issues/6692

I see the problem. SB is trying to delete a directory, but should be deleting a file. In the screenshot the command is
rmdir
Should be
del or some other delete command.

And a second issue with manual enterd path
https://github.com/laurent22/joplin/issues/6693

OK, the error for deleting the ZIP files is fixed, but for the problems with the manual enterd path oder path with space we need  a fix on the Joplin side.

Oh, good news! I'll be looking for the plugin update to appear in Joplin and will apply and confirm back to you.

Thanks, Jack! I installed the plugin manually. Seems to be working as expected, now.


Sales Professional License Limitation to Create Orders from Quotes

Hi Team
Can we please clearly mention here that "If you're using a sales professional license, you are not allowed to create orders from quote and that's why the 'create order' button is missing. You can convert a quote to invoice but not orders. If you need to create orders for your sales process, upgrade to Sales Enterprise Licensing."

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

ID: 83bf84d6-3a96-1cf5-ee4b-b070fe9fe18b
Version Independent ID: 4a5b7baa-b501-4711-eb9e-f225e7a205ca
Content: Create and manage invoices in Dynamics 365 Sales Professional
Content Source: ce/sales-professional/create-invoices.md
Service: dynamics-365-sales
GitHub Login: @shubhadaj
Microsoft Alias: shujoshi

@Closing this bug because I've responded to #1469 around the same issue.


Dopameme (Meme/Art Generator Platform Bounty)

Name : Swayam Sharma, Shreyash Singh, Vivek Shah,
Email and contact details:
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Project details:
Dopameme is an advanced meme-making platform designed to simplify and elevate the creative process using AI technology. It offers a variety of innovative tools, enabling users to effortlessly generate, customize, and share memes. Dopameme transforms the traditionally time-consuming task of meme creation into an engaging, automated experience, making it accessible to everyone.
Demo video: https://www.youtube.com/watch?v=ruex9eExt4s ,
Demo link:  https://web.telegram.org/k/#@dopameme_fun_bot ,
GitHub repository details: https://github.com/vivekratr/Dopameme-Miniapp-v2 ,
Tech stack used:
Spheron SDK, Telegram SDK, Reactjs, Python, Tailwind CSS, Rainbow Kit, Dynamic Wallet, Ethers JS, Arbitrium Sepolia, Gemini, Computer Vision.

Please add a good readme into your repo showcasing it's installation & running process.
Also, Include deployment steps on Spheron with the YAML. Since it's an open source contribution you have to add MIT or Apache license into your repo as well.
Going forward, I would recommend removing your phone numbers from here for privacy reasons.

Also, can you properly describe how you use Spheron in your project and what OSS AI models you use in your project?

Also, can you properly describe how you use Spheron in your project and what OSS AI models you use in your project?

The open-source models have been used as API inference in our Flask application, which integrates all models and has been deployed on Spheron.

Also, can you properly describe how you use Spheron in your project and what OSS AI models you use in your project?

The open-source models have been used as API inference in our Flask application, which integrates all models and has been deployed on Spheron.

But I don't see that code anywhere in the repo you have shared in the submission. If there are any other repositories for the Flask backend, then please share them here in the submission description. Also, share the spheron ICL (yaml) configuration so that we can test it out.

Please add a good readme into your repo showcasing it's installation & running process.
Also, Include deployment steps on Spheron with the YAML. Since it's an open source contribution you have to add MIT or Apache license into your repo as well.
Going forward, I would recommend removing your phone numbers from here for privacy reasons.

All the changes mentioned is done

I don't think it's done, as far as i can see the YAML you have provided is not the real one with your docker containers. You need to setup a deployment YAML of your container on Spheron & not just with the random example.

Please add a good readme into your repo showcasing it's installation & running process.
Also, Include deployment steps on Spheron with the YAML. Since it's an open source contribution you have to add MIT or Apache license into your repo as well.
Going forward, I would recommend removing your phone numbers from here for privacy reasons.

All the changes mentioned is done

I don't think it's done, as far as i can see the YAML you have provided is not the real one with your docker containers. You need to setup a deployment YAML of your container on Spheron & not just with the random example.

We've now updated the YAML with the real Docker image and provided a video link demonstrating the deployment process on Spheron, completed by our team. Please check it out and let us know if you need anything else.
Watch the video.

Hey @vivekratr took a look into it.
Here are the comments & questions:

Readme is still not updated on the main repo Readme.md
You have added the Spheron folder for deployment but can't find any GPU usage into it
Which models are you using for this & where these models are deployed.
If models are deployed else where then we don't accept this submissions. Models must be deployed on the Spheron GPU & tutorial must showcase the process of deployment on Spheron.

Please take your time to updated everything properly. If we will see the same issue again & again we will disqualify your submissions. Ensure you follow everything stated for the submission guidelines with outmost quality.

Also, can you properly describe how you use Spheron in your project and what OSS AI models you use in your project?

We are deploying our Flask backend using Spheron. The open-source model we are utilizing is Artples/LAI-ImageGeneration-vSDXL-2.

Also, can you properly describe how you use Spheron in your project and what OSS AI models you use in your project?

The open-source models have been used as API inference in our Flask application, which integrates all models and has been deployed on Spheron.

But I don't see that code anywhere in the repo you have shared in the submission. If there are any other repositories for the Flask backend, then please share them here in the submission description. Also, share the spheron ICL (yaml) configuration so that we can test it out.

The information you mentioned has been updated and is now available for review. Additionally, we have provided the YAML configuration for your reference. Please feel free to test it out.

Hey @vivekratr took a look into it.
Here are the comments & questions:

Readme is still not updated on the main repo Readme.md
You have added the Spheron folder for deployment but can't find any GPU usage into it
Which models are you using for this & where these models are deployed.
If models are deployed else where then we don't accept this submissions. Models must be deployed on the Spheron GPU & tutorial must showcase the process of deployment on Spheron.

Please take your time to updated everything properly. If we will see the same issue again & again we will disqualify your submissions. Ensure you follow everything stated for the submission guidelines with outmost quality.

-> The README has been updated to include detailed deployment steps for both the front-end and back-end components of the application on Spheron. Additionally, the product features have been outlined and included in the README.
-> With regard to the GPU, our Flask backend has been successfully deployed to the Spheron folder. You can view the GPU usage in the source code pipeline (src/pipeline) folder.
-> Our overall AI system, responsible for the generation component, has been deployed on the Spheron network. You can review it.

We can still see that your GitHub is closed source. We would love to see the dopameme deployed on decentralized infra

Closing this submission as there is been a long time of inactivity


Trigger leader mode map in emacs-state

Hi All,
I'm looking for a way to set a binding that would trigger the leader mode-map in buffers without evil, or in evil's emacs-state, like dired, comin, man page, and other modes. Basically where I'd normally type "SPC o n" in these buffers I'd instead type "M-m o n" or similar like in spacemacs. I'm sure there's an easy way to do this, I just need it pointed out.
Thanks in advance for the help :smile:

You can change doom-leader-key (SPC) and doom-localleader-key (SPC m). e.g.
(setq doom-leader-key "M-m"
      doom-localleader-key "M-S-m")

I suggest putting this in one of your init.el files. For example: ~/.emacs.d/init.el or ~/.doom.d/init.el.
Hope that helps!

Hmm, that's not quite it. I'd still like to be able to use the normal leader key "SPC", just have an additional leader key to use in non evil buffers

Ah, I see what you mean. An alias for the leader key. Unfortunately, there's no simple way to do this.
I plan to redesign the keybind system after 2.1 goes up (to use general.el behind the scenes). I suspect this change will make your request possible, but it may be a while until I get there (until May, I think).

Thanks for the answer! In the interim, I'm gonna see if i can play around with the map! macro and convince it to make two bindings for every binding it declares, one beginning with leader and one with "M-m". Will update this ticket if I get it working!

Now that general is in Doom, we've got four variables for controlling leader/localleader keys in evil and non-evil sessions and states:
These are used in evil normal, visual and motion states:

doom-leader-key (default: "SPC")
doom-localleader-key ("SPC m")

And these are used in insert and emacs states, as well as non-evil sessions:

doom-leader-alt-key ("M-SPC")
doom-localleader-alt-key ("M-SPC m")

Change them as early as possible (in ~/.doom.d/init.el) for the new keys to take effect.
With that I'll consider this issue resolved. Let me know if there's anything else you need help with.


fix(_handlers.ts): typo

Description
Fix a small typo: occured -> occurred
Motivation and Context

How has this been tested?

Types of changes

[x] 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)

Checklist:

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.

Could you also fix the  failing unit tests in test/unit/handlers.spec.ts?

Fixed

Coverage remained the same at 98.86% when pulling 7d726d54cea2762cb69c0165cd627b63cd13621e on maple3142:patch-1 into aca648f65d14fd764d20fa35163885d4913b5b59 on chimurai:master.

Thanks!


Add virtual

Codecov Report

Merging #31 (71bbf34) into main (8532623) will increase coverage by 2.93%.
The diff coverage is 78.49%.

@@            Coverage Diff             @@
##             main      #31      +/-   ##
==========================================
+ Coverage   54.39%   57.32%   +2.93%
==========================================
  Files           5        7       +2
  Lines         671      764      +93
  Branches      343      359      +16
==========================================
+ Hits          365      438      +73
- Misses         25       33       +8
- Partials      281      293      +12

Impacted Files
Coverage Δ

src/vm.cpp
75.40% <75.40%> (ø)

include/lisp/vm.h
84.37% <84.37%> (ø)

Continue to review full report at Codecov.

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


Add examples folder for alerts & dashboards, and observability stack

Part of #448
There are separate issues to update these dashboards, add new ones and add example alerts, all tracked in https://github.com/Kuadrant/kuadrant-operator/issues/439
There's a separate PR for how these dashboards will be included as part of the release process.
https://github.com/Kuadrant/architecture/pull/85
To verify this PR, the single cluster getting started guide can be followed https://docs.kuadrant.io/getting-started-single-cluster/
Then run the commands from the observability README in the PR to deploy the stack and access grafana or prometheus.
You can also import the example dashboards json into grafana.
For data to show up on the dashboards, you can follow the guide at https://docs.kuadrant.io/kuadrant-operator/doc/user-guides/secure-protect-connect/ to create various gateway api and kuadrant resources.

👀

Feedback on Dashboards:
app-developer:
The table should use center it looks cleaner and fit screens better
platform:

Im thinking the single stat values could be a little bit bigger i don't see the table needing as much space as it has

Gateway table is all squshed into the corner would be better to have even spaced and in the center

Space out table columns evenly and center them

Center the apis table columns

Feedback on Dashboards

Thanks for the feedback on the dashboards.
While this PR is moreso getting the examples in place and a process for developing dashboards, those notes should be helpful for the follow up issues #434 and #435 (the former which has a PR already #494).
I'll leave any modifications to the dashboards out of this PR so that it can land earlier and we'll have the process in place for updating as needed then.

ah ok deadly if its just to get things up and running it does what it says on the tin

@R-Lawton I've pushed up the recommended changes.
The link to the examples folder works locally in vscode, but not in the preview. I think it should work when back on main rather than viewing it in the PR rich diff view.


Online limb-darkening tool has some missing JWST bandpasses

Hi folks,
As pointed out in today's ExoCTK team meeting by @JeffValenti, NIRSpec, NIRISS orders 2/3 and different NIRCam combinations are missing from the possible bandpasses in the online tool. We think this is OK for now, but this will be critical for JWST data analysis.
I'm assigning this to @hover2pi as he might have some quick ideas on how to solve this. I believe the easiest thing would be to ask the user to upload a bandpass in a specified format --- but the optimal would be to retrieve bandpasses periodically from some central source (e.g., is there any CRDS file that stores this info for JWST bandpasses?).
I'm setting this for v1.2 (i.e., our next-next release), as this is low priority for now.
N.

Yeah, this has been a problem because there is no central repository for the bandpasses of each instrument. I have had to just get some from JDOX and contact the instrument teams directly. I would strongly advocate for these files to be quality controlled and centrally located.

Possible solution from Klaus Pontoppidan:
def get_pce(instrument,mode,config):
   obsmode = {
              ‘instrument’: instrument,
              ‘mode’: mode,
              ‘filter’: config[‘filter’],
              ‘aperture’: config[‘aperture’],
              ‘disperser’: config[‘disperser’]
              }
   conf = {‘instrument’: obsmode}
   i = InstrumentFactory(config=conf)
   wr = i.get_wave_range()
   wave = np.linspace(wr[‘wmin’], wr[‘wmax’], num=500)
   pce = i.get_total_eff(wave)
   return wave,pce

I ended up just writing a function in the helpers.py module to grab the FITS files in the pandeia_refdata directory and save them locally as text files so svo_filters can read them. It didn't work.
So I released svo_filters v0.3.0 which fixes a few small bugs in the load_txt method and updated the relevant code in limb_darkening_fit.py (as well as the env dependency) which DID work, but it has exposed something curious.
The NIRISS dispersers all seem to be problematic. The GR700XD has strange linearly interpolated values in their throughput curves and the GR150C/R grisms are just constant values. Is this correct? I checked the headers and there are no instructions for some special conversion or manipulating. The NRM filter is all ones but that is intentional since the ETC separately takes it into account.
The NIRCam and NIRSpec dispersers all look reasonable so it appears to only be the files delivered by NIRISS to the ETC.
Any ideas?

Ok, I confirmed that with pandeia_data v1.5.3 the NIRISS GR700XD is still messed up as shown above. I'm going to check with the pandeia folks to see if they know about it and why it looks the way it does.

Looks like you are plotting the dispersion (dl/ds) micron per pixel, not the throughput.

This is resolved in #458


Consider upgrading to sbt 1.x

@SethTisue got the upgrade partially working in https://github.com/scalameta/scalameta/pull/1720. Let's discuss whether/when/how this should be done.

I think it's good to look into this once Scalameta v4.0 and sbt v1.2 are out. sbt v1.2 adds nice improvements to cross-building which could avoid a lot of boilerplate in build.sbt

Using sbt 1.3.8 now - can be closed?

Yes. This issue is now fixed


Task – Offline edited task name changed with delay in DM chat LHN

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: v1.4.62-0
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/4486193
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause Internal Team
Slack conversation:
Action Performed:

Go to https://staging.new.expensify.com/
Log in.
Go to any chat
Create a task with assignee
Go Offline and edit task name
Go back Online and observe task name in a DM chat in LHN (not task details)

Expected Result:
Offline edited task name changed without delay in DM chat LHN
Actual Result:
Offline edited task name changed with delay in DM chat LHN when go Online. Task name in LHN must be changed when Offline
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
https://github.com/Expensify/App/assets/38435837/f4eeab0d-a315-4154-b3db-41367119a06a
Bug6445047_1712787643540!Log.txt.txt
Add any screenshot/video evidence

View all open jobs on GitHub

@sakluger FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors.

Proposal
Please re-state the problem that we are trying to solve in this issue.
When we update the task title, the LHN of the chat report doesn't update with the new title.
What is the root cause of that problem?
The task title in the LHN last message takes the title from getTaskTitle.
https://github.com/Expensify/App/blob/bbc676100f7309a4495307885d0c6823b2825d47/src/libs/TaskUtils.ts#L40-L52
getTaskTitle will first get the title from the task report reportName and fallback to the task action childReportName. When we edit the task, we already optimistically update the task report reportName.
https://github.com/Expensify/App/blob/bbc676100f7309a4495307885d0c6823b2825d47/src/libs/actions/Task.ts#L447-L450
However, getTaskTitle never use reportName. That is because the task report here is always an empty object because we access it incorrectly
https://github.com/Expensify/App/blob/bbc676100f7309a4495307885d0c6823b2825d47/src/libs/TaskUtils.ts#L40-L41
allReports contains the collection of the report which is keyed by report_{id} but we try to access it with {id}. This started to happen after https://github.com/Expensify/App/pull/38464. Previously, allReports is keyed by {id}.

What changes do you think we should make in order to solve the problem?

Access the task report by report_{id}.
const taskReport = allReports?.[`${ONYXKEYS.COLLECTION.REPORT}${taskReportID}`] ?? {};

What alternative solutions did you explore? (Optional)
Use the old approach by keyed it with {id} and remove waitForCollectionCallback.
https://github.com/Expensify/App/blob/bbc676100f7309a4495307885d0c6823b2825d47/src/libs/TaskUtils.ts#L10-L17

@bernhardoj's proposal LGTM.

PR is ready
cc: @getusha

I paid @bernhardoj's contract. @bernhardoj could you please complete the BZ checklist?

@sakluger I think @getusha should be the one that complete the checklist

@bernhardoj you're right, my bad! @getusha please complete the checklist when you have a moment.

BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

[x] [@getusha] The PR that introduced the bug has been identified. Link to the PR: https://github.com/Expensify/App/pull/38464
[x] [@getusha] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment: https://github.com/Expensify/App/pull/38464/files#r1596233138
[x] [@getusha] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion: N/a
[x] [@getusha] Determine if we should create a regression test for this bug. No, it looks like a minor bug
[x] [@getusha] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again. N/a

Thanks! All paid out.


AWS Lambda error timeout after 30s /  "cannot execute binary file"

Hi,
just did a fresh install of Chromeless with the remote option. The lambda function is being triggered when I run the example script, but it times out after 30 secs. I followed the instructions exactly and the deployment seemed to have gone perfectly. I can see that Chrome is simply not starting, probably caused by the fact the the "headless_shell" binary cannot be run.
This is 100% reproducable, I could give your my api key to try it out.
Data:
chromeless 1.3.0
aws region: eu-central-1
Cloudwatch output:
TART RequestId: 29c90ac5-8e3d-11e7-944e-07f9e1b67b80 Version: $LATEST
2017-08-31T11:11:43.192Z	29c90ac5-8e3d-11e7-944e-07f9e1b67b80	@serverless-chrome/lambda Spawning headless shell
2017-08-31T11:11:43.198Z	29c90ac5-8e3d-11e7-944e-07f9e1b67b80	@serverless-chrome/lambda ChromeLauncher No debugging port found on port 9222, launching a new Chrome.
2017-08-31T11:11:43.206Z	29c90ac5-8e3d-11e7-944e-07f9e1b67b80	@serverless-chrome/lambda Launcher Chrome running with pid 13 on port 9222.
2017-08-31T11:11:43.207Z	29c90ac5-8e3d-11e7-944e-07f9e1b67b80	@serverless-chrome/lambda Waiting for Chrome 0
2017-08-31T11:11:43.711Z	29c90ac5-8e3d-11e7-944e-07f9e1b67b80	@serverless-chrome/lambda Waiting for Chrome 1
2017-08-31T11:11:44.211Z	29c90ac5-8e3d-11e7-944e-07f9e1b67b80	@serverless-chrome/lambda Waiting for Chrome 2
2017-08-31T11:11:44.712Z	29c90ac5-8e3d-11e7-944e-07f9e1b67b80	@serverless-chrome/lambda Waiting for Chrome 3
2017-08-31T11:11:45.213Z	29c90ac5-8e3d-11e7-944e-07f9e1b67b80	@serverless-chrome/lambda Waiting for Chrome 4
2017-08-31T11:11:45.714Z	29c90ac5-8e3d-11e7-944e-07f9e1b67b80	@serverless-chrome/lambda Waiting for Chrome 5
2017-08-31T11:11:46.216Z	29c90ac5-8e3d-11e7-944e-07f9e1b67b80	@serverless-chrome/lambda Waiting for Chrome 6
2017-08-31T11:11:46.717Z	29c90ac5-8e3d-11e7-944e-07f9e1b67b80	@serverless-chrome/lambda Waiting for Chrome 7
2017-08-31T11:11:47.218Z	29c90ac5-8e3d-11e7-944e-07f9e1b67b80	@serverless-chrome/lambda Waiting for Chrome 8
2017-08-31T11:11:47.719Z	29c90ac5-8e3d-11e7-944e-07f9e1b67b80	@serverless-chrome/lambda Waiting for Chrome 9
2017-08-31T11:11:48.220Z	29c90ac5-8e3d-11e7-944e-07f9e1b67b80	@serverless-chrome/lambda Waiting for Chrome 10
2017-08-31T11:11:48.230Z	29c90ac5-8e3d-11e7-944e-07f9e1b67b80	@serverless-chrome/lambda Error trying to spawn chrome: { Error: connect ECONNREFUSED <IP_ADDRESS>:9222
at Object.exports._errnoException (util.js:1018:11)
at exports._exceptionWithHostPort (util.js:1041:20)
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1086:14)
code: 'ECONNREFUSED',
errno: 'ECONNREFUSED',
syscall: 'connect',
address: '<IP_ADDRESS>',
port: 9222 }
2017-08-31T11:11:48.236Z	29c90ac5-8e3d-11e7-944e-07f9e1b67b80	@serverless-chrome/lambda stdout log:
2017-08-31T11:11:48.236Z	29c90ac5-8e3d-11e7-944e-07f9e1b67b80	@serverless-chrome/lambda stderr log: /var/task/node_modules/@serverless-chrome/lambda/dist/headless_shell: /var/task/node_modules/@serverless-chrome/lambda/dist/headless_shell: cannot execute binary file

2017-08-31T11:11:48.236Z	29c90ac5-8e3d-11e7-944e-07f9e1b67b80	Error occured in serverless-plugin-chrome wrapper when trying to ensure Chrome for default() handler.
{}
Error: Unable to start Chrome. If you have the DEBUG env variable set,there will be more in the logs.
at /var/task/node_modules/@serverless-chrome/lambda/dist/bundle.cjs.js:304:13
at throw (native)
at step (/var/task/node_modules/@serverless-chrome/lambda/dist/bundle.cjs.js:257:191)
at /var/task/node_modules/@serverless-chrome/lambda/dist/bundle.cjs.js:257:402
at process._tickDomainCallback (internal/process/next_tick.js:135:7)
END RequestId: 29c90ac5-8e3d-11e7-944e-07f9e1b67b80
REPORT RequestId: 29c90ac5-8e3d-11e7-944e-07f9e1b67b80	Duration: 5048.54 ms	Billed Duration: 5100 ms Memory Size: 1536 MB	Max Memory Used: 38 MB

@tnolet Are you deploying from Windows? Deploying the Proxy from Windows currently won't work because of a known issue: https://github.com/graphcool/chromeless/issues/70#issuecomment-318634457, https://github.com/adieuadieu/serverless-chrome/issues/21, https://github.com/serverless/serverless/issues/3557

@adieuadieu No, I'm deploying from MacOS. I am however running Node 6.11.2. Is it possible that the installation scripts need Node 8? I'm aware the Chromeless syntax uses Node 8 features, and that is fine.

@tnolet @adieuadieu I have the same error:  Timed out after 30sec. Connection couldn't be established. (MacOS, Node: 8.4.0, chromeless 1.3.0, eu-central-1)

@kamilregulski can you maybe check your Cloudwatch logs and see if it has the same cannot execute binary file error?

@tnolet Yes, the same:
2017-09-01T22:50:20.373Z	eb74e766-8f67-11e7-93ce-531cc778d996	@serverless-chrome/lambda stderr log: /var/task/node_modules/@serverless-chrome/lambda/dist/headless_shell: /var/task/node_modules/@serverless-chrome/lambda/dist/headless_shell: cannot execute binary file

Have the exact same issue.

Maybe something changed in the AWS lambda container, making the binary incompatibe?

What steps could we follow to debug this?
Should we rebuild the binary?

After thinking about it for a while, I think I found the root of the issue. The AMI for the Lambdas was updated to the 2017.03 version.
I ran a simple lambda doing cat /etc/system-release and this was the output:
"Amazon Linux AMI release 2017.03\n"

Tomorrow I will try to recompile Chrome 61 with the Lambda patch using the "Amazon Linux AMI release 2017.03" image.

I found a workaround, though it is a bit annoying. https://github.com/adieuadieu/serverless-chrome/issues/65

There was a bug in Serverless CLI 1.21.0... https://github.com/serverless/serverless/pull/4189
We can close this ticket.
Solution
Update Serverless to 1.21.1.
npm install -g<EMAIL_ADDRESS>

@carlosbaraza fantastic! Thanks for the hard work!

Just want to add that if you are getting this error then please make sure your AWS_IOT region is same as the region specified in serverless.yml (it defaults to ireland i think). I was getting this timeout error because of this and now it's fixed.
P.S. Also since it's my first comment here, a huge thanks to everyone involved in this project for their hardwork. This is just awesome!

hmm..none of the mentioned solutions are working in my case.
configuration:
serverless: 1.21.1
chromeless: 1.3.0
operating system: Mac
node: 8.2.1
in my serverless.yml
awsIotHost: ${env:XXXXXXXXXXX.iot.eu-central-1.amazonaws.com}
runtime: nodejs6.10
region: eu-central-1

any ideas?


feat: add globalStylesEnabled option

Description
This PR add the globalStylesEnabled.
Additional context
The globalStylesEnabled option allows to disable the automatic fetching of the openbim-components styles.
This useful if you want to provide the styles by your own and modify/revert scrollbar styling.

What is the purpose of this pull request?

[ ] Bug fix
[x] New Feature
[ ] Documentation update
[ ] Other

Before submitting the PR, please make sure you do the following:

[x] Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
[x] Follow the Conventional Commits v1.0.0 standard for PR naming (e.g. feat(examples): add hello-world example).
[x] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
[x] Ideally, include relevant tests that fail without this PR but pass with it.

Hi @myasteiner, thanks for your PR!
We're currently working on UIComponents 2.0, and some things about this matter are being changed. However, I think is a good proposal from your side. Could you please add globalStylesEnabled in the UIManager itself and not in the components instance? In fact, uiEnabled should be the same thing, but that's from our side. If you do it, I will merge your PR right away.
Thanks a lot!

Init is only called when you write components.init. So, if you write the following:
const components = OBC.Components()
components.ui.globalStyles = false
//other things here
components.init()

Everything should be fine.
Now, in any case, you can always download the styles.css, put them in your HTML file, and then modify only the things you want to override. If you want, that approach can also work and I will take care of this PR.
Let me know!

My suggestion to you is to monkey patch the init method to use a custom UIManager. I know it is no clean solution but for now it works.
const bimComponents = new OBC.Components();
// monky patch to use our own UI manager
bimComponents.init = async function () {
    this.enabled = true;
    this._clock.start();
    if (this.uiEnabled) {
        this._ui = new CustomUIManager(this);
        await this.ui.init();
    }
    await this.update();
    await this.onInitialized.trigger(this);
};

Hey guys!
We are working on UIComponents 2.0. It's going to be a completely new library separated from openbim-components. The thing is, everything regarding how the UI works today is going to be replaced by new stuff, hopefully will be more polished and less problematic.
If you haven't seen some of the videos we have published about it, you can see them in our LinkedIn account.
You can also see the roadmap in order to de when to expect this.
Closing this PR.


Add Vale for prose linting

What/Why/How?
To ensure good quality documentation, add Vale to check for common mistakes in written English.
This enables a few rules to get us started, fixes the existing docs to comply with those rules, adds instructions to CONTRIBUTING and sets up a GitHub action to run on all pull requests.
Reference
https://vale.sh/
Testing
Make a spelling mistake in a pull request based off this branch - or by running the tool locally.
Screenshots (optional)
Check yourself

[ ] Code is linted
[ ] Tested with redoc/reference-docs/workflows
[ ] All new/updated code is covered with tests

Security

[ ] Security impact of change has been considered
[ ] Code follows company security practices and guidelines

@HCloward I had to make a bunch of grammatical changes for this "future tense" check to pass. Could you double check it all seems right to you please? (sorry, it's quite a lot of changes!)
Everyone else is welcome to review as well, particularly the tool implementation.


RangeError: Invalid string length

I'm getting this error while running this query:
{
  "size": 1000,
  "query": {
    "filtered": {
      "filter": {
        "bool": {
          "must": [
            {
              "range": {
                "records_len": {
                  "gte": 130
                }
              }
            }
          ]
        }
      }
    }
  }
}

also, there is no indication of the error in the screen, only in the browser console.
This is the full backtrace:
lib.js:119 RangeError: Invalid string length
at Array.join (native)
at h (http://localhost:9000/js/lib.js:395:743)
at f (http://localhost:9000/js/lib.js:395:490)
at m (http://localhost:9000/js/lib.js:395:1083)
at http://localhost:9000/js/lib.js:395:578
at Array.map (native)
at g (http://localhost:9000/js/lib.js:395:555)
at f (http://localhost:9000/js/lib.js:395:499)
at m (http://localhost:9000/js/lib.js:395:1083)
at http://localhost:9000/js/lib.js:395:578

hum, this is very odd. which browser are you using?

I used chrome & firefox.
If I understand correctly this happened when the return value from the server was a very long string (the documents are pretty big).

@arossert yep, i looked around and it seems you are right. and unfortunately also not much I can do about it(perhaps I could catch the error and warn about it, but I doubt this adds much value). sorry :)


Add dialog callback fallback

Currently the app will hang if a dialog API is called with a null or undefined callback parameter since the callback added by the rpc-server.js for asynchronous APIs will then be at the 4th argument position and parseArgs in dialog.js will be looking for it at the third position.
This pull request adds a fallback that uses the last argument as the callback so that the rpc-server callback wrapper argument will always be used when specified.
Closes #4936

👍


Modified join and leave channels page with mobile content

Summary

Modifies the Join and leave channels end user documentation page to include content that covers the user's mobile experience, helping to publish webapp/desktop app and mobile app end user step details to all end users.
Ticket Link

Fixes #5924

Hello @michizhou,
Thanks for your pull request! A Core Committer will review your pull request soon. For code contributions, you can learn more about the review process here.


tests: drivers: Extend coverage for NRF GRTC timer

Add more test cases for nRF GRTC timer

Please review

CC @adamkondraciuk


field checks done too early causing error

Attrs does some checks on fields like no defaulted fields coming before non-defaulted fields before running custom field transformers. This is a problem when a field transformer intends to modify the fields but gets an error before being able to apply their modification.
For example, this field transformer reorders fields so that in fact the defaulted field x comes after the non-defaulted field y. But attrs errors before the transformer is ever called.
def order_by_metadata(cls, fields):
    fields.sort(key=lambda x: x.metadata["field_order"])
    return fields

@define(field_transformer=order_by_metadata)
class A:
    x: int = field(metadata={"field_order": 1}, default=0)
    y: int = field(metadata={"field_order": 0})

Traceback (most recent call last):
  File "...", line 426, in <module>
    class A:
  File ".../attr/_next_gen.py", line 146, in wrap
    return do_it(cls, True)
  File ".../attr/_next_gen.py", line 90, in do_it
    return attrs(
  File ".../attr/_make.py", line 1603, in attrs
    return wrap(maybe_cls)
  File ".../attr/_make.py", line 1499, in wrap
    builder = _ClassBuilder(
  File ".../attr/_make.py", line 657, in __init__
    attrs, base_attrs, base_map = _transform_attrs(
  File ".../attr/_make.py", line 566, in _transform_attrs
    raise ValueError(
ValueError: No mandatory attributes allowed after an attribute with a default value or factory.  Attribute in question: Attribute(name='y', default=NOTHING, validator=None, repr=True, eq=True, eq_key=None, order=True, order_key=None, hash=None, init=True, metadata=mappingproxy({'field_order': 0}), type='int', converter=None, kw_only=False, inherited=False, on_setattr=None, alias=None)

I think these checks should be done after custom field transformers.

See also https://github.com/python-attrs/attrs/issues/1169#issuecomment-2240403489

@sscherfke transformers are your labor of love – is this realistic without adding a whole abstraction layer over this?

is this realistic without adding a whole abstraction layer over this?

Not sure what you mean -- why isn't it sufficient to just move the order check after the field transformer has been applied?
IIUC, field transformers can already do arbitrary rearranging, as long as the initial field order is valid.
But as that's not the final order, it should not matter, right? Conversely, a field transformer that results in an invalid order would currently slip past the check.
That said, why do we need the manual check in the first place? Python already gives us a pretty good exception when attempting to evaluate the incorrect code. Picking up the above example:
def order_by_metadata(cls, fields):
    fields.sort(key=lambda x: x.metadata["field_order"])
    return fields

@define(field_transformer=order_by_metadata)
class A:
    x: int = field(metadata={"field_order": 1})
    y: int = field(metadata={"field_order": 0}, default=0)

This yields the following error:
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/me/.local/lib/python3.11/site-packages/attr/_next_gen.py", line 144, in wrap
    return do_it(cls, True)
           ^^^^^^^^^^^^^^^^
  File "/home/me/.local/lib/python3.11/site-packages/attr/_next_gen.py", line 90, in do_it
    return attrs(
           ^^^^^^
  File "/home/me/.local/lib/python3.11/site-packages/attr/_make.py", line 1715, in attrs
    return wrap(maybe_cls)
           ^^^^^^^^^^^^^^^
  File "/home/me/.local/lib/python3.11/site-packages/attr/_make.py", line 1694, in wrap
    builder.add_init()
  File "/home/me/.local/lib/python3.11/site-packages/attr/_make.py", line 1090, in add_init
    _make_init(
  File "/home/me/.local/lib/python3.11/site-packages/attr/_make.py", line 2181, in _make_init
    init = _make_method(
           ^^^^^^^^^^^^^
  File "/home/me/.local/lib/python3.11/site-packages/attr/_make.py", line 345, in _make_method
    _compile_and_eval(script, globs, locs, filename)
  File "/home/me/.local/lib/python3.11/site-packages/attr/_make.py", line 317, in _compile_and_eval
    bytecode = compile(script, filename, "exec")
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "<attrs generated init __main__.A>", line 1
    def __init__(self, y=attr_dict['y'].default, x):
                                                 ^
SyntaxError: non-default argument follows default argument


graviton-ready-java: NoClassDefFoundError in JarNativeInfo misses potential native methods

Describe the bug
When you ask tool to verify N jars, that are dependent on each other, like:

jar1 -> Class1
jar2 -> Class2
jar3 -> Class3

And Class2 has a dependency on Class1 and also contains native methods,  JarNativeInfo would try to load Class2, but fail will NoClassDefFound error, that would be ignored: https://github.com/aws/porting-advisor-for-graviton/blob/main/src/advisor/tools/graviton-ready-java/src/main/java/com/amazonaws/labs/GravitonReadyAssessor/JarNativeInfo.java#L185
This just results in skipping some native methods and marking libraries as "good" without them actually being "good".
Proposed fix
It would be better to not try to load class into JVM, but rather parse the bytecode using javassist. That way class could be analyzed for presence of native methods without loading all dependent classes.

Thank you for your reaching out @aidar-stripe. Our team will take a look at this and get back to you with any comments.


Formatting

Remove useless scripts
Flake8
Remove hard-coded paths

Thank you @johncoltrane1.
I have rebased, squashed, streamlined... and finally pushed your changes :wink:


elf_helper: skip SYS_INIT() "devices"

SYS_INIT instantiates a device struct, but this is really
just used to run some functions at boot, it does not correspond
to a device driver belonging to a subsystem. Don't put them in
the kernel object table.
These are easy to filter since they are all named with the
_SYS_NAME macro.
Signed-off-by: Andrew Boie<EMAIL_ADDRESS>

What is the meaning of this change? Is it to reduce the amount of kernel objects?

@ioannisg yes, it reduces the number of objects that get put in the gperf table.
Things declared with SYS_INIT() are never going to be drivers that belong to a subsystem, even though they internally instantiate a struct device.

Right

Codecov Report

Merging #11821 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master   #11821   +/-   ##
=======================================
  Coverage   48.29%   48.29%
=======================================
  Files         280      280
  Lines       43333    43333
  Branches    10375    10375
=======================================
  Hits        20929    20929
  Misses      18252    18252
  Partials     4152     4152

Continue to review full report at Codecov.

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


Loading members

Reworked loadMemberData and loadMemberContext to a list of loaded members (static methods involved), a loader and an object for each member.
I'm quite confident something is broken.
While at it I also created a featureEnabled function to replace all the in_array used to check if a "core feature" is enabled or not. I think it is more readable that way and the check is centralized, so easier to maintain (actually, I did it only because the array was in $context and loaded only way too later in the loading of the theme lol ).

That should do! :D


golang 1.17.5

To address this issue - https://github.ibm.com/IBMPrivateCloud/roadmap/issues/51513

/cherry-pick release-eus


[Backend] Introduce getExecutableExt method to executor

This commit introduces getExecutableExt method which returns executable
extension list to Executor class.
ONE-vscode-DCO-1.0-Signed-off-by: yunjay-hong<EMAIL_ADDRESS>
draft: #522

/cc @Samsung/one-vscode_committers


feat: tree component API for virtual tree

Description
Extending the Tree component with a new virtualTreeConnector props make it possible
to use accessible navigation with virtualized trees.
Links
https://jira-eng-gpk2.cisco.com/jira/browse/SPARK-552764

There is a known issue, when the user using Voice Over and scroll away from the focused node, VO announce one more time the focused node. Probably because we clone it and programatically focus it.
I could not find a way to prevent this extra announcement, but I think it is acceptable trade off.


Uncaught AssertionError: html-pdf: Failed to load PhantomJS module. You have to set the path to t...

[Enter steps to reproduce below:]

...
...

Atom Version: 1.0.19
System: Microsoft Windows 7 Enterprise
Thrown From: markdown-themeable-pdf package, v0.10.1
Stack Trace
Uncaught AssertionError: html-pdf: Failed to load PhantomJS module. You have to set the path to the PhantomJS binary using 'options.phantomPath'
At assert.js:89

AssertionError: html-pdf: Failed to load PhantomJS module. You have to set the path to the PhantomJS binary using 'options.phantomPath'
  at new PDF (C:\Users\bdevries\.atom\packages\markdown-themeable-pdf\node_modules\html-pdf\lib\pdf.js:41:7)
  at Object.exports.create (C:\Users\bdevries\.atom\packages\markdown-themeable-pdf\node_modules\html-pdf\lib\index.js:13:14)
  at C:\Users\bdevries\.atom\packages\markdown-themeable-pdf\lib\markdown-themeable-pdf.js:447:27
  at FSReqWrap.readFileAfterClose [as oncomplete] (fs.js:380:3)

Commands
  2x -8:26.7.0 core:move-left (atom-text-editor.editor.is-focused)
  5x -8:22.1.0 core:backspace (atom-text-editor.editor.is-focused)
  3x -7:24.4.0 core:move-down (atom-text-editor.editor.is-focused)
 11x -7:09.9.0 core:backspace (atom-text-editor.editor.is-focused)
  2x -6:51.3.0 core:move-down (atom-text-editor.editor.is-focused)
  9x -6:43.8.0 core:backspace (atom-text-editor.editor.is-focused)
  5x -6:01.5.0 core:move-up (atom-text-editor.editor.is-focused)
  2x -6:00.5.0 core:move-down (atom-text-editor.editor.is-focused)
     -5:59.7.0 core:move-right (atom-text-editor.editor.is-focused)
     -5:59.1.0 core:move-up (atom-text-editor.editor.is-focused)
 21x -5:58.8.0 core:move-right (atom-text-editor.editor.is-focused)
     -5:53.4.0 core:backspace (atom-text-editor.editor.is-focused)
  9x -5:52.9.0 core:move-left (atom-text-editor.editor.is-focused)
     -5:50.7.0 core:backspace (atom-text-editor.editor.is-focused)
     -4:32.8.0 settings-view:install-packages-and-themes (atom-text-editor.editor.is-focused)
     -4:20.2.0 core:confirm (atom-text-editor.editor.mini.is-focused)

Config
{
  "core": {
    "themes": [
      "spacegray-mocha-ui",
      "atom-light-syntax"
    ],
    "disabledPackages": [
      "language-gfm"
    ]
  }
}

Installed Packages
# User
language-ipynb, v1.3.0
markdown-themeable-pdf, v0.10.1
spacegray-mocha-ui, v0.2.0

# Dev
No dev packages

Please try to reinstall markdown-themeable-pdf and check your firewall settings.

If the error is still up to date, write in this Ticket

I have the same issue using Atom 1.0.11 in Linux/Fedora 23. I tried to reinstall after disabled firewall, no success.

Strange, I have Fedora 23, too.

I also meet the same error, which tells me You have to set the path to the PhantomJS binary using 'options.phantomPath'. I fix this error by using npm install html-pdf in command prompt. Hope it works for you.

I'm using openSUSE Tumbleweed, after a long wait to install this package, and also have this problem. Re-installation doesn't do any help.

Sorry, but I can not do more than writing the package compliant :/ Unfortunately, the problems must be on your OS, Node, or atom installation

I am having the same problem on Windows10 64, could anybody give some hint to fix it?

@yonglei I had the same problem just now on my Windows 10 64-bit machine. I managed to fix it following the instructions given by @Myasuka:

Make sure you have npm installed on your machine. If you don't have it you can download it from here (Node.js comes packaged with npm and I read that it was the easiest way to get npm.
Open your command prompt and run the command npm install html-pdf
One of the lines from the log should tell you where the PhantomJS binary is located:

Done. Phantomjs binary available at C:\Users\jonathan\node_modules\html-pdf\node_modules\phantomjs-prebuilt\lib\phantom\bin\phantomjs.exe

Add the binary to your path.
Restart Atom

This worked for me. I hope it works for you too.

@Myasuka @JonnyCBB I got the location of PhantomJS binary. May you please tell me how to 'Add the binary to your path'? Thank you so much.

Hey @bowang14, sorry for late reply. Assuming you're on a Windows machine here's how to add a binary to your path:

Right click the Windows icon in the bottom right corner of your screen
Select "Control Panel"
You'll get a screen with lots of options. Select "System"
On the new screen select "Advanced system settings"
In the new window that pops up, select "Environment Variables..."
Then you'll get another new window with two boxes: one for "User variables" and one for "System variables". If you're using a personal machine where you're the only user then there's practically no difference using either. Scroll down the list in the "System variable" box until you see "Path" in the "Variable" column. Click on "Path" and then click "Edit..." below.
If you're using Windows 10 then you'll have a nice interface to modifying your path. You can click "New" and then enter the path to the Phantom JS binary that you were given when prompted. Otherwise if you're using like Windows 7 or earlier (I can't remember what Windows 8 was like) then you'll have a nasty long string of paths separated by semicolons. You'll have to scroll to the end, add a semicolon and then add the path.
8, Click "Ok" to everything and then you should be good to go.

I hope this works for you :)

@JonnyCBB Thank you for your reply and I have to say sorry that I forgot to tell you I use a Mac. Thank you so much for your help all the same.
I found a way via Google and had already add it to my path. However, it doesn't work still.
[bogon:~ wangbo$ echo $PATH
/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:**/Users/wangbo/node_modules/html-pdf/node_modules/phantomjs-prebuilt/lib/phantom/bin/phantomjs**:/Library/TeX/texbin
Is there any mistake I made?
Again thank you so much.

I have to admit that I know least about Macs.
What error message do you get? Is it the same as before?

Yes, exactly the same one.

@bowang14 I've been trying to reproduce the error but unfortunately I can't so I'm not quite sure what the problem is. Sorry :(

@JonnyCBB Thank you so so so much for your help all the same.

I made it by........just re-installing Atom. sigh

I'm glad that you got it working.

@JonnyCBB @bowang14 It works for me well and I maybe understand more about environment variables. Thank you.

我也遇到同样问题，根据以上评论，记录一下解决过程。
atom markdown转换PDF 解决AssertionError: html-pdf: Failed to load PhantomJS module
http://blog.csdn.net/dream_an/article/details/51800523

I tried adding the PhantomJS binary to my environment path, but it doesn't work.
However, I fixed it by directly copy the html-pdf folder created by npm install html-pdf to ~/.atom/packages/markdown-themeable-pdf/node-modules and overwrite the previous html-pdf folder.

Well,I have the same problem and try to set the path manually.
Firstly,download the phantomjs:
npm install phantomjs
or
cnpm install phantomjs
and you will see
Done. Phantomjs binary available at C:\Users\Kael\AppData\Roaming\npm\node_modules\.phantomjs_npminstall\phantomjs\2.1.7\phantomjs\lib\phantom\bin\phantomjs.exe
copy the path and find this js file:
C:\Users\Kael\.atom\packages\markdown-pdf\node_modules\html-pdf\lib\PDF.js
paste the path and write:
this.options.phantomPath = "C:\\Users\\Kael\AppData\\Roaming\\npm\\node_modules\\.phantomjs_npminstall\\phantomjs\\2.1.7\\phantomjs\\lib\\phantom\\bin";
done.

ubuntu 16.04  Atom 1.9.2

Make sure you have installed nodejs,
Run  sudo npm install -g phantomjs-prebuilt
Reinstall markdown-themeable-pdf,
Restart Atom
Enjoy it!

Same problem here on ubuntu 16.04 Atom 1.12.05
At last, add a recommended procedure to install PhantomJs on the Readme file ?
Because it's seems like to be a prerequisite for this package.

I don't use ubuntu so I can't say for certain that the procedure worked for me but I guess you submit this to the package author as a pull request.

It was really easy to fix on Linux:

in Atom uninstall the markdown-themeable-pdf package and close Atom.
open a terminal and change to super-user su
install npm (use your OS installer, whichever that may be, pacman, zypper, yum, apt, etc)
now just: npm install -g html-pdf  (this will make sure PhantomJS is correctly installed)
open Atom and install the markdown-themeable-pdf package

This worked for me without any issues, thanks for this amazing package @cakebake

On my macOS:

npm install -g phantomjs
reinstall markdown-themeable-pdf
restart Atom

@CharlSteynberg

Hello,I follow your steps,I dont get any errors messages when I ```uninstall markdown-themeable-pdf``` and ```npm install -g html-pdf```.But there havent the button of Markdown to PDF at the packages of my Atom editor.
So,have you any other suggestion for me solve this question?Thank U!

@CharlSteynberg

I forgot to say that my OS is Ubuntu16.04LTS and Atom 1.15.0-X64 :)

@CharlSteynberg

hahahaha,I reinstall markdown-pdf and then is ok.Have the button and get PDF correctly ↖(▔▽▔)↗

@explosic4 原来是因为缺少包啊

我也遇到了这个问题，卸载后重启atom，然后重新安装，然后重启atom就可以用了

npm install -g html-pdf
npm install -g phantomjs

I dont know why, but using yarn instead of npm seems to solve my problem


python310Packages.pydeconz: 106 -> 107

Diff: https://github.com/Kane610/deconz/compare/refs/tags/v106...v107
Description of changes

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 216834 run on x86_64-linux 1

4 packages built:

home-assistant-component-tests.deconz
home-assistant-component-tests.zha
python310Packages.pydeconz
python311Packages.pydeconz


Add breakpad_symbol SymbolFile fuzzer

Going to leave this running overnight. Could find something else, because it was previously exiting early because of the (now fixed in #419) overflow.
I looked in the rest of this crate, and couldn't really see anything doing much complex work.

420, fuzz it. :sunglasses:

:sunglasses:
time to write that stack walk fuzzer you warned me about

rad!

time to write that stack walk fuzzer you warned me about

:sweat_smile: If you want to chat about potential approaches to this feel free to join us in Sentry's discord, the #native-crashes channel, or via Twitter DM. I will say that while it's an interesting idea, in terms of bang-for-the-buck you've already covered the most useful fuzz targets at this point.


service/pypi, test: add support for withdrawn vulnerabilities

This will have no effect until pypi/warehouse#12443 is merged.
See #388.
Signed-off-by: William Woodruff<EMAIL_ADDRESS>

Whoops, forgot to do a changelog entry for this one. I'll do a followup in a moment.


Enable JSON viewer for .pipeline files

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Currently .pipeline files can only be opened in the VPE or the plain text editor from the File Browser context menu:

Describe the solution you'd like
Enable the JSON viewer (like it is for Jupyter notebooks) to make it easier to browse the file:

@ajbozarth - thoughts?

As I mentioned in the dev meeting I took a swing at addressing this sometime last year and actually spent some time on it.
The options that are show in the context menu are determined by the widget factories. When a widget factory is created it lists the file types that it supports, which would then list that widget as an option in the context menu for that file type. In this case the JSON extension in core creates the factory and sets the file types (json and notebook). File types are separately defined in the doc registry. In pipeline-editor-extension we add the pipeline file type for .pipeline files and the PipelineEditorFactory is created with the pipeline file type listed.
To add pipeline files to the JSON factory we would need to add it in core JL. If .pipeline was a standard format we might be able to do that (geojson file type is also supported), but it is not a standard format so I would expect such a PR would be rejected.
Another option would be to "override" the JSON factory by removing it and then adding an extension that "extends" it ourselves with the pipeline file type support, but the JSON editor does not seem easily extendable to do so.
As my extensive work on this is well over a year old things might have changed on the JL core side that would more easily allow this feature add though if someone else wants to take the time to look into it again.

Leaving a note here, it seems the Doc Registry can now be extended, so we "may" be able to implement the "override" idea at the docRegistry level instead. Not sure if it would be useful but I'll make note of this here https://github.com/jupyterlab/jupyterlab/pull/10256

IIUC https://github.com/jupyterlab/jupyterlab/pull/11540 has added support for this. Once that is released we'll be able to add this support. As such moving this to the 4.0 sprint (with the assumption that it will be release in lab 4)

Once https://github.com/elyra-ai/elyra/pull/2495 is merged this should be pretty trial for me to fix


Cannot target DOTNET 5.0 for upgrade

There appears to be no way to tell the Upgrade Assistant to target DOTNET 5.0 instead of 6.0.  Nor do there seem to be any DOTNET-Target-Specific releases of Upgrade Assistant to roll back to.

This worked me in command line before running tool
set DefaultTargetFrameworks__LTS=net5.0
then using running with this option
--target-tfm-support LTS

Thank you for that suggestion - I will try it and see if it works for me as well.  How on earth did you discover that, though?

Open source is the best :)
https://github.com/dotnet/upgrade-assistant/blob/main/src/cli/Microsoft.DotNet.UpgradeAssistant.Cli/appsettings.json

Hmm.  Didn't work for me - at least, not as expected.  I used the command as shown above, and tested it on one csproj file (comparing it to a csproj from a newer application that has been built against DOTNET 5.0).
The upgrade assistant created a csproj with: <TargetFramework>netstandard2.0</TargetFramework> rather than the expected <TargetFramework>net5.0</TargetFramework>?

I think there is logic in the tool that will target netstandard2.0 if it can if it is a library project.
source

Yes, that is correct there is no straight-forward way to upgrade to .NET 5.0 using upgrade-assistant since we switched LTS, Current and Preview to be .NET 6.0. Also, .NET 5.0 is EOL in a few months, so its probably a good idea to move to .NET 6.0 which is a LTS release meaning its going to be around for 3 years. Closing this issue as there is nothing actionable UA team can do here, feel free to continue discussions if need be.


How does the code combine 9 images in different brightness into 1 image before fitting in the model?

In  visualize.py line 68, I save data['img'] before it fit to the model.
and find out the origin image was not only processed with Normalization and Resize,
but also done some brightness adjust and put 9 of them in 3 by 3 grid together.
However I can not figure out how and where does it be done.
I need to know how to do it cause I want to implement a real time webcam prediction demo.
Also, does it mean during the training the model is actually watching only one third resolution even after resized?
Thanks for the answer.

I found out that this operation is done by collater(data) in dataloader.py


Contact Dan Buscombe

to discuss lighting options for camera and how to format spreadsheet for SediNet

LED rings as far back as possible. very diffused light. as uniform as possible
avoid specular reflections with light too close to the lens, and internal reflections.

the P is Pixel, D is grain size...  so D50 is grain size in mm P50 is grain size in pixels... to convert just do mm/pixels..

So how would I convert our sieved samples to grain size in pixels? I am a little confused now

The idea is that each of these images from sedinet is from a sieve analysis, grains that make it through the upper sieve, but not the lower sieve. Each sample has a range of grain sizes. D5, D10, D50, etc.
Images of these samples are taken, and the pixel dimension are determined.. so X mm/ pixel.. Then all teh grain size metrics are converted to Pixel Size metrics (P5, P10, P50, etc.)...  by dividing grain size metric (mm) by known pixel size (mm/pixel).
that is what is expressed in these CSVs... does that make sense? so the steps for us would be:

determine grain size metrics for a given sand sample
take a picture of the sample
compute pixel size of image
convert the grain sizes metrics for the sample in 'P' metrics by dividing by the  pixel size.

Okay, I think I might of sent Dan an email before I saw you posted this but it clears everything up. So after I have done all of the pictures, computed pixel size and converted metrics to pixel size, I should be able to run it through the SediNet


ApplyButter method is not reflected in images.

The method void ApplyButter(Toast toast) is mentioned in the code but is not reflected in images. The three images in this document only reflect the method void ApplyJam(Toast toast) but not void ApplyButter(Toast toast).

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

ID: 17d27a0d-c072-8c9f-7e31-3de60bee9ae8
Version Independent ID: e0c09794-e712-19ff-cb9f-12648d60d4f6
Content: Asynchronous programming in C#
Content Source: docs/csharp/programming-guide/concepts/async/index.md
Product: dotnet-csharp
Technology: csharp-async
GitHub Login: @BillWagner
Microsoft Alias: wiwagn

Closing without action. There haven't been any other notes to this effect.
The image blocks get larger and more cumbersome by adding additional detail. As they exist now, they do show the flow well.


Fix/add regex sqlite

Closes #564
The changes in the order of the imports were done by isort, if you want I can restore the order

Coverage increased (+0.001%) to 98.314% when pulling a5931d73702cb9bd1910a384f7a76e749ac3f8e2 on lyz-code:fix/add-regex-sqlite into 7d0bc587014b0180dfa826f477a06592d8484d01 on kayak:master.


ngClick ?

What about add ng-click to the sidemenu-button ?
I needed to add locally in the sources by myself but this change will be override when i update future versions.

@keplerk Did you implement that?

Yes but it was long time ago, i dont use sidemenu anymore.

@keplerk you need to execute another function on ng-click?


Fix managed channel is not closed

channelFactory is not closed after tisession being closed.
This fixes https://github.com/pingcap/tispark/issues/621

/run-all-tests

Codecov Report

:exclamation: No coverage uploaded for pull request base (batch_write@6ddef21). Click here to learn what that means.
The diff coverage is 85.71%.

@@              Coverage Diff               @@
##             batch_write     #622   +/-   ##
==============================================
  Coverage               ?   51.22%
  Complexity             ?      994
==============================================
  Files                  ?      146
  Lines                  ?     6823
  Branches               ?      795
==============================================
  Hits                   ?     3495
  Misses                 ?     2996
  Partials               ?      332

Impacted Files
Coverage Δ
Complexity Δ

...ient/src/main/java/com/pingcap/tikv/TiSession.java
75.34% <100%> (ø)
15 <0> (?)

...ain/java/com/pingcap/tikv/util/ChannelFactory.java
86.36% <83.33%> (ø)
5 <2> (?)

Continue to review full report at Codecov.

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


const http -> var http

Seems to be causing an issue on Ubuntu 14: https://github.com/ShenNoether/MiniNodo/issues/3

The problem is not Ubuntu but older versions of Node.js that do not support basic use of the ES6 const syntax in strict mode. See here: http://node.green/#bindings
Anyway, I merged since it doesn't make much difference in this case to use const or var. They might still have an issue with let...


Release new version 0.0.3

@JuliaRegistrator register()

Error while trying to register: "Tag with name v0.0.2 already exists and points to a different commit"

Project.toml has indeed wrong version.

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/83980
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.0.3 -m "<description of version>" 1d7253fd8b56c5d6c27bee4b22b937b93142cf5b
git push origin v0.0.3


Version on nuget does not serialize DateTime properly

The version on nuget serializes DateTime's like so: 02/01/2016 15:40:19 -06:00
The latest from master serializes DateTime's properly: 2016-02-01T15:40:19.26112-06:00

This was fixed with 2acbc724b73a43a8dbafe6ecace8a29b849cd37d which is not in version 4.0.0 of the NuGetPackage, but in will be in the next one.

Release new NuGet package


PowerGrid the ag-Grid-AutoColumn how can I set properties?

Hi,
using the Power Grid and if for example 1 column is grouping and the 'ag-Grid-AutoColumn' appear.
I move the width of this group column.
I store the state of the grid and to apply this state later.
If I come back to this grid and restored the column state the width does not keep the with I gave it before.
There is any trick to solve this situation?
Or doing that by process maybe can I put the  'ag-Grid-AutoColumn'  pinned left?
Un Saludo
Juan Ramírez

Hi Juan,
columns will auto resize by default to fit the grid width.
If you don't want a column to be auto resized you can set the column property autoResize=false.
Regards,
Paolo

Hi Juan,
columns will auto resize by default to fit the grid width.
If you don't want a column to be auto resized you can set the column property autoResize=false.
Regards,
Paolo

Hi Paolo,
yes I know that property but my question is haw can I control the grouping column (it call 'ag-Grid-AutoColumn').
In my case I try to show some statistics and when I refresh the information the first column become small.

I have a process to change the size and the pinned I works but not the  autoResize=false.
function onColumnStateChanged(columnState) { 	var  _state,/** @type {Object<*>} */ _jsonState,_restore=false; 	_state= _super.onColumnStateChanged(columnState); 	if (_state){ 		_jsonState = JSON.parse(_state); 		 if (!_jsonState || !_jsonState.columnState || !_jsonState.columnState.length) return _state;  		 for (var i = 0; i < _jsonState.columnState.length; i++) { 			 if ( _jsonState.columnState[i].colId=='ag-Grid-AutoColumn'&& !_jsonState.columnState[i].pinned){ 				 _jsonState.columnState[i].pinned='left'; 				 _jsonState.columnState[i].width=200; 				 _jsonState.columnState[i].autoResize=false; 				 _restore=true; 				 break; 			 } 		 } 	} 	if (_jsonState && _restore){ 		_state = JSON.stringify(_jsonState); 		elements.rejilla.restoreColumnState(_state); 	} 	return _state; }
Un Saludo
Juan

Hi Paolo,
yes I know that property but my question is haw can I control the grouping column (it call 'ag-Grid-AutoColumn').
In my case I try to show some statistics and when I refresh the information the first column become small.

I have a process to change the size and the pinned I works but not the  autoResize=false.
function onColumnStateChanged(columnState) { 	var  _state,/** @type {Object<*>} */ _jsonState,_restore=false; 	_state= _super.onColumnStateChanged(columnState); 	if (_state){ 		_jsonState = JSON.parse(_state); 		 if (!_jsonState || !_jsonState.columnState || !_jsonState.columnState.length) return _state;  		 for (var i = 0; i < _jsonState.columnState.length; i++) { 			 if ( _jsonState.columnState[i].colId=='ag-Grid-AutoColumn'&& !_jsonState.columnState[i].pinned){ 				 _jsonState.columnState[i].pinned='left'; 				 _jsonState.columnState[i].width=200; 				 _jsonState.columnState[i].autoResize=false; 				 _restore=true; 				 break; 			 } 		 } 	} 	if (_jsonState && _restore){ 		_state = JSON.stringify(_jsonState); 		elements.rejilla.restoreColumnState(_state); 	} 	return _state; }
Un Saludo
Juan

Hi Juan,
you mean to use the entire row for the grouped row ?
There is a property for that. You can add it in the gridOptions as groupUseEntireRow:true.
Let me know if that is what you are looking for

Hi Juan,
you mean to use the entire row for the grouped row ?
There is a property for that. You can add it in the gridOptions as groupUseEntireRow:true.
Let me know if that is what you are looking for

Hi Paolo,
no this is not what I am looking for.
Sorry is difficult to explain it.
I have in a form a powerGrid, I feed that powerGrid with a function and I launch that process with a button.
This function depends on some variables.
With the svyProperties module I store the columnState.
Some columns are pinned to the left and sometimes you want to group some of that columns.
When you have the powerGrid with a column grouped, you have a new column,
this column if you check it inside, it have the id = 'ag-Grid-AutoColumn'. But I cannot put properties to this column. And I cannot store the properties, so I do a process to change that properties.
The problem is that when I launch the procees to feed the powerGrid again the width of this column became to small.
All the columns have the property  autoResize=false.

Un saludo
Juan ramírez

Hi Paolo,
no this is not what I am looking for.
Sorry is difficult to explain it.
I have in a form a powerGrid, I feed that powerGrid with a function and I launch that process with a button.
This function depends on some variables.
With the svyProperties module I store the columnState.
Some columns are pinned to the left and sometimes you want to group some of that columns.
When you have the powerGrid with a column grouped, you have a new column,
this column if you check it inside, it have the id = 'ag-Grid-AutoColumn'. But I cannot put properties to this column. And I cannot store the properties, so I do a process to change that properties.
The problem is that when I launch the procees to feed the powerGrid again the width of this column became to small.
All the columns have the property  autoResize=false.

Un saludo
Juan ramírez

Hi Juan,
i understand your problem now.
AutoGroup column are defined in the gridOptions property, using the autoGroupColumnDef property.
You can possibly override the column def using the ngService:
	plugins.ngPowerGrid.gridOptions = {
        autoGroupColumnDef : {
        	headerName: "Group Title",
			minWidth: 200,
			suppressSizeToFit: true
		}
	}

However be aware by doing so you will override the built in implementation of autoGroupColumnDef  for the power grid.
Specifically you won't be able to use the groupStyleClass property and the groupRowRendererFunc property.
Regards,
Paolo

Hi Juan,
i understand your problem now.
AutoGroup column are defined in the gridOptions property, using the autoGroupColumnDef property.
You can possibly override the column def using the ngService:
	plugins.ngPowerGrid.gridOptions = {
        autoGroupColumnDef : {
        	headerName: "Group Title",
			minWidth: 200,
			suppressSizeToFit: true
		}
	}

However be aware by doing so you will override the built in implementation of autoGroupColumnDef  for the power grid.
Specifically you won't be able to use the groupStyleClass property and the groupRowRendererFunc property.
Regards,
Paolo

Thanks that's is what I want.
Sorry my bad explanation.
Un Saludo
Juan Ramírez

Thanks that's is what I want.
Sorry my bad explanation.
Un Saludo
Juan Ramírez


Ignoring auth requests by clicking X prevents further auth requests

SAFE Browser Version: head of peruse branch

That's interesting - are you sure that's SAFE Browser and not Peruse? I think this happened to me with the WebID test build of Peruse this week, but using an earlier official build of SAFE Browser this did not happen.

@theWebalyst I should have specified peruse branch.

Addressed by PR https://github.com/maidsafe/safe_browser/pull/280


[Feat]: move to oras 0.16.x for bats tests

Is your feature request related to a problem? Please describe.
oras 0.16.0 now supports OCI artifacts and references.
https://github.com/oras-project/oras/releases
Start the test with this:
https://oras.land/cli/6_reference_types/
But switch over to:
11/24/2022 10:56 AM •
$ ./oras version
Version:        0.16.0
Go version:     go1.19.2
Git commit:     d606fed4be252fd6162f63548e024451c31f3864
Git tree state: clean

$ ./oras attach localhost:8080/alpine:edge     --artifact-type 'signature/example'      ./signature.json:application/json

Uploading b5334d78ecfc signature.json
Uploaded  b5334d78ecfc signature.json
Attached to localhost:8080/alpine@sha256:77ee9d7d39229024fd77373e079e03f3a6d384044391a0f9ae1d1f115aa38e8e
Digest: sha256:f9c6125ff6a19fa838ca7d09ddb60c490e159b06be8a18b7ce4a7c18743f79d1

$ ./oras discover localhost:8080/alpine:edge -o tree

localhost:8080/alpine:edge
└── signature/example
    └── sha256:f9c6125ff6a19fa838ca7d09ddb60c490e159b06be8a18b7ce4a7c18743f79d1

Describe the solution you'd like
No response
Describe alternatives you've considered
No response
Additional context
No response

https://github.com/oras-project/oras/releases
Start the test with this:
https://oras.land/cli/6_reference_types/
But switch over to:
11/24/2022 10:56 AM •
$ ./oras version
Version:        0.16.0
Go version:     go1.19.2
Git commit:     d606fed4be252fd6162f63548e024451c31f3864
Git tree state: clean

$ ./oras attach localhost:8080/alpine:edge     --artifact-type 'signature/example'      ./signature.json:application/json

Uploading b5334d78ecfc signature.json
Uploaded  b5334d78ecfc signature.json
Attached to localhost:8080/alpine@sha256:77ee9d7d39229024fd77373e079e03f3a6d384044391a0f9ae1d1f115aa38e8e
Digest: sha256:f9c6125ff6a19fa838ca7d09ddb60c490e159b06be8a18b7ce4a7c18743f79d1

$ ./oras discover localhost:8080/alpine:edge -o tree

localhost:8080/alpine:edge
└── signature/example
    └── sha256:f9c6125ff6a19fa838ca7d09ddb60c490e159b06be8a18b7ce4a7c18743f79d1


[BUG] API not present in configuration file is still being deployed

Release version
v6.0.11
Describe the bug
As per documentation and #435, I was told that I should be able to prevent the deployment of an API by omitting the API from the configuration file.
However, this does not appear to work as I have an API currently commented in configuration code:
[...]
apis:
[...]
  # - name: api2
  #   properties:
  #     serviceUrl: ""
  # there is no dev env

but the API is being deployed whether I make a publish all artifacts or edit the specs and publish last commit...
I always deploy with configuration file as I have multiple environment, I am using different configuration files for each environment
Expected behavior
Only API defined explicitly in the configuration files are published. API that are commented should not be published.
Actual behavior
All API are deployed, all the time.
Reproduction Steps
configuration file configuration.d1.yaml:
---
apimServiceName: apimdev01
apis:
#APIs Begin
  - name: api1
    properties:
      serviceUrl: "https://api1.example.net"
  # - name: api2
  #   properties:
  #     serviceUrl: ""
  # there is no dev env

folder structure:

apis

api1

apiInformation.json
specification.json

api2

apiInformation.json
specification.json

Based on what I can see when I debug the publisher ("Launch Publisher" in VS code), it seems that there is a part of the code that look at files on the disk and will always push config that is stored locally, regardless if there is an entry in the configuration file.

@fabienmazieres - are you passing the full path of configurationd1.yaml to the publisher? You can see how it's defined in our starter ADO and GitHub pipelines.

@guythetechie ,
I am following the GitHub pipeline example:
          CONFIGURATION_YAML_PATH: ${{ GITHUB.WORKSPACE }}/${{ inputs.CONFIGURATION_YAML_PATH }}

I have changes a few things from the template to adapt to our authentication and self-hosted runners but this part of run-publisher-with-env.yaml was left as per the original file, I did copy/paste code from your repo when working on upgrade to 6.0

@fabienmazieres - after rereading your issue, I think there's a misunderstanding of how the extractor and publisher work with configuration.

The extractor configuration file specifies which resources should be extracted. If resourceType: [resource1, resource2, ...] is specified, when the extractor extracts resources of resourceType, only resource1 and resource2 will be extracted. If nothing is specified, all resources will be extracted.
The publisher configuration file allows you to override the properties of resources that are published. It does not influence which resources get published. The publisher chooses resources to publish like this:

If a commit ID is passed in configuration, only resources changed in that commit will be published.
If no commit ID is passed in configuration, all artifacts will be published.

There is no built-in functionality to only publish (or exclude from publishing) a specific resource. You can only control what gets extracted. Once something lands in your artifacts source control, it's eligible for publishing.

@fabienmazieres - I don't think so. It's not a simple task, and it goes against our philosophy of Git being the source of truth.
If different teams are responsible for different components of the same APIM instance, they can work with different repositories. Team A can work in repository A where only artifacts related to API A are extracted. They have their own extractor/publisher pipeline. Similarly, team B can work in repository B with their separate artifacts and extractor/publisher pipelines. Both teams can target the same APIM instance, and only their relevant resources will be published.


errors loading Power BI

🐛 Problem
When configuring the Power BI Cost Summary report we receive as many rows loaded as well as errors.
👣 Repro steps

Open Power BI
Create a configuration to the hub
Refresh data.

🤔 Expected
All rows loaded without errors.
📷 Screenshots

ℹ Additional context
This was a completely new setup without any customization.
🙋♀ Ask for the community

Please vote this issue up (👍) to prioritize it.
Leave comments to help us solidify the vision.

@maikvandergaag, just to confirm, are you using FinOps hubs or the Cost Management connector here? Did you happen to click "View errors" to see what the issue was?
If you're using hubs, we have a big update coming in 0.2 that simplifies a lot of the code and will likely resolve this but it would be helpful to see what the error is.

@allcontributors please add @maikvandergaag for bug

We are using the FinOps Hub.
Any idea when the 0.2 version is coming?

@maikvandergaag 0.2 is available now @ https://aka.ms/ftk/latest 🙂
Note that 0.2 uses FOCUS exports, so you'll need to recreate exports. You can use PowerShell to create them or a special preview link in the docs: https://aka.ms/exportsv2.
I'll keep this open and move it to 0.3 for a couple weeks to give you a chance to confirm this works for you.

Thanks, is there any migration path described for moving from 0.1 to 0.2 for the hub and powerbi?

Deploy the template (see below)
Delete old exports
Create new FOCUS exports
Backfill data by running exports for previous months

NOTE: There's an Export selected dates command in the new export experience that allows picking specific dates without creating separate one-time exports.

Download and setup the new Power BI reports
Optional: After all is done, if you want to reduce storage costs, delete the old data

FYI - Here's a release candidate that fixes 2 known bugs in 0.2: https://gist.github.com/flanakin/419b5ed778d12a109b297d0dd406c10f
I did a quick pass to make sure the files land in ingestion. Will confirm the rest later.

hey Michael,
We just used the deployment you have in the previous post, we are getting this error when we try to connect to the data source (storage account with parquet files). we are testing trying to ingest to the laste costSummary.pbix and also costSummary.pbit, both with the same error.
screenshot below

@olp0678 There was a path issue in the previous version. I updated that. Please try the latest:
@maikvandergaag, can you also verify this release candidate? We will publish this in the next release soon.
https://finops/hubs/rc

thanks @flanakin , I believe link you have there its not working and you meant this one https://gist.github.com/flanakin/419b5ed778d12a109b297d0dd406c10f , I will deploy and see how it goes.

Doh! I left out the "aka.ms" part. Kinda critical 😅 Fixed the link above.

@maikvandergaag / @olp0678, can y'all confirm whether you're still running into issues? I want to confirm all is good and close this issue.


Update PPP

Codecov Report

Merging #345 (b831c73) into master (15cf79b) will increase coverage by 0.62%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master     #345      +/-   ##
============================================
+ Coverage     63.85%   64.47%   +0.62%
- Complexity      475      479       +4
============================================
  Files            90       90
  Lines          1779     1782       +3
  Branches        189      189
============================================
+ Hits           1136     1149      +13
+ Misses          592      578      -14
- Partials         51       55       +4

Impacted Files
Coverage Δ

...in/java/seedu/unify/model/util/SampleDataUtil.java
16.66% <0.00%> (-3.34%)
:arrow_down:

...in/java/seedu/unify/logic/commands/TagCommand.java
88.63% <0.00%> (+2.27%)
:arrow_up:

...va/seedu/unify/model/task/TaskIsDonePredicate.java
100.00% <0.00%> (+50.00%)
:arrow_up:

...ava/seedu/unify/logic/parser/TagCommandParser.java
61.11% <0.00%> (+61.11%)
:arrow_up:

Continue to review full report at Codecov.

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


[DATA CONTRIBUTION] Caravan extension Iceland

Basin prefix
lamahice
Zenodo DOI
https://www.hydroshare.org/resource/86117a5f36cc4b7c90a5d54e18161c91/
Number of catchments
88
Location of catchments
Iceland
For which periods are streamflow records available in your dataset?
Meteorological time series are available from 1950-01-01 to 2021-09-23. The streamflow records are of variable length. The earliest start date is 1950-01-01, with the most common end date being 2021-09-29.
Please list any sources of the data you contributed.
The streamflow records were obtained from the Icelandic Meteorological Office and the National Power Company of Iceland.
License
The Creative Commons Attribution NonCommercial 4.0 International License CC-BY-NC-4.0 applies to the streamflow measurements. The Creative Commons Attribution 4.0 International License CC-BY-4.0 applies to all other data (meteorological timeseries from ERA5-Land, shapefiles and attribute values).
Additional context
This data was originally published as the LamaH-Ice dataset by Helgason and Nijssen (2023). Compared to the original LamaH-Ice, the Caravan extension does not include basins with a strong anthropogenic or natural influence on streamflow (20 basins). The LamaH-Ice data description paper (in review as of October 9 2023) is available at https://essd.copernicus.org/preprints/essd-2023-349/
Checklist

[X] I have uploaded my dataset on Zenodo, where it is accessible under the DOI provided above.
[X] I used a basin prefix that is not yet used by any other Caravan sub-dataset (you can check this via the Data Contributions discussion thread, where all accepted Caravan contributions are listed).
[X] Permissive License: My data is available under a license that is compatible with the Caravan CC-BY-4.0 license (the easiest way to be sure about this is if your data uses CC-BY-4.0, too).

Hi Hordur,
thanks for contributing your data also to Caravan. I had a quick look and here are a few issues I found. All of them should be easy to fix and it would be great if you can update the caravan-extension archive in your repository.

attributes_caravan index column not named "gauge_id"
attributes_hydroatlas index column not named "gauge_id"
attributes_other index column not named "gauge_id"
gauge_id in shapefile is missing extension prefix (currently only the numbers)
shapefile contains more than 88 polygons (it contains 111)
license file is not in a subdirectory. Should be licenses/lamahice/license_lamahice.md

Perfect, yes, I checked it again and looks all good. So I will close this issue and link all the relevant info in #10 Thanks again for providing the data to Caravan.


Scope for next release?

What do we want done for the 6.12 release in January? And when should it be finished by relative to the January release schedule? I'd like to make a GitHub milestone for that work and decide what can realistically be done in a polished state by then.

I think @stamourv needs to answer this one.

Well, I'm not 100% clear in what this can do at the moment, so here's an attempt at an answer.
IIUC, it seems like this docker setup can run all the automated tests that are on the release checklist. If that's the case, then it sounds like a good goal would be to get to a point where all those items on the checklist can be replaced by one person (presumably me) running the docker image instead.
There will already be structural changes to the checklist and the process around it for the next release, so it seems like a good time to make that change too.
Now, I would imagine that the above would require making it is the relevant test suites have no expected failures. Is that something that you think would be reasonable within that time frame?

I think #1 has some of the status there for the automatable tests.

Ah, I see. Do you think there's a chance the checklist could be complete in time for the next release?

More likely if you help. ;)
More seriously,  the issues with the racket tests might be fixed by the IPv6 fix @mflatt made for Travis. The DrRacket issue is less clear.
The other ones should be relatively easy to fix -- unclarity in the checklist instructions, or expected failures, or tests that I've never succeeded in running outside of Docker either, and thus need some instruction.

Okay, I think a good scope to target is:

Don't bother with more docker improvements like package / installer caching, Windows containers, images for more kinds of installations, speeding up builds and test runs, or deflaking the Travis CI setup
Run as many automated non-flaky non-failing release tests (both GUI and non-GUI) as feasible on all currently dockerized installers (in-place installs on linux 32 bit, 64 bit, and 64 bit with bundled OS packages)
Write down issues for what needs to be done to deflake currently unreliable tests, automate currently manual tests, and fix currently failing tests (good place to start: breaking #1 down into issues for individual tests)

The existing docker compose interface seems good enough, so I'm not sure we need to work on any more docker-related issues for now. @samth, do you think testing unix-style installations and build-from-installer-source installations is too much work before the next release?

To complete the automatable items on the checklist, we want to at least build from source, build with the couple build options mentioned in the checklist (-funsigned-char and -DTEST_ALTERNATE_TARGET_REGISTER=1), and test the unix-style installs. I don't think those should be hard, I made them work in my initial Dockerfile in this repo.

Okay, that seems reasonable. I also think the extflonum test fixes (racket/typed-racket#652) should be included.