Problems with rendering reports in Webclient / missing fonts

When i want to preview a report in webclient, the report just uses a Standard font because the Fonts in the container are missing.
Please provide the Windows Standardfonts in the Image.
Best Regards
Patrick

In NavContainerHelper there is a function called Add-FontsToNavContainer - which will copy fonts from the host, please use that, I cannot add the fonts up front.


Thanks for sharing

Thanks for sharing your collection of tools for InfoWater models!
My background is mostly with InfoWorks WS Pro which has a full set of APIs to let you code directly within the application and I've only recently started using InfoWater. I've been wanting to do some coding in InfoWater but I wasn't sure where to even start so this repo was a massive help.
One quick question, from what I've seen you're limited to working with the output files and the geographic layers within ArcGIS and don't have any way to directly interface with InfoWater, correct?
Keep up the good work, I'm hoping to share some tools for InfoWater as well to go with my InfoWorks WS Pro open source tools.

Happy to share!
Infowater unfortunately does not have an API to work with/manipulate models. It would be my number 1 feature for Innovyze add one to infowater pro.
Consequently, this means all processing needs to be done on outputs such as the report files or data exported from the EXT_APP_FILTER option.
There isn't many tools I've seen for infowater so I'm always interested to see what others are working on.

I'm not sure if you're familiar with InfoWorks WS Pro but if you wanted to see examples of the API Innovyze set up I've got a repo here:
https://github.com/modelcreate/infoworks-ruby-scripts/
The other alternative I thought to using the EXT_APP_FILTER option would be to reading the HYDQUA.OUT binary file. I'm assuming its a modification of the EPANET structure so a little reverse engineering and you could access all the time series data.
I saw you're based out of Kitchener, I work for C3 Water in Breslau, maybe we will cross paths in the future. If you're ever interested in learning more about any of my open source work feel free to shot me an email<EMAIL_ADDRESS>or<EMAIL_ADDRESS>It's a rare combination to be both a modeller and a programmer!


Wait until page is fully loaded?

I would like to wait for the graphs on my webpage to fully load before making a PDF, and "await Page.loadEventFired();" doesn't seem suitable for the job.
Is there any API available for determining when a page is fully loaded, or do I need to wait for a specific element to appear in the DOM?

Whether a page is fully loaded (besides Page.loadEventFired) is not  something that can be understood by Chrome. You'll need to implement your own check, e.g., an HTML element appears, a JavaScript object has a certain property, etc.
In any case everything boils down to start and await a promise in Runtime.evaluate which gets fulfilled when your custom event triggers.
await Runtime.evaluate({
    expression: `new Promise((fulfill, reject) => {
        /*...*/
    })`,
    awaitPromise: true
});

See this wiki recipe.

Thank you

@cyrus-and Do you know if there is a way to listen for alerts rather than modify an element/object?

Using Page.handleJavaScriptDialog, see this comment, in this case you don't need to inject JavaScript code with Runtime.evaluate.


Can't instantiate Metaphor

Unable to instantiate Metaphor
This expression is not constructable.
 Type 'typeof import("node_modules/metaphor-node/dist/index")' has no construct signatures.ts(2351)

How I'm importing and instantiating:
import Metaphor from "metaphor-node";

const metaphor = new Metaphor(process.env.METAPHOR_API_KEY);

Node v18.16.0
Package.json:
{
  "name": "synthmedia-worker",
  "version": "1.0.0",
  "main": "index.js",
  "type": "module",
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1",
    "start": "node -r dotenv/config dist/index.js"
  },
  "keywords": [],
  "author": "",
  "license": "ISC",
  "devDependencies": {
    "@types/node": "^20.4.2",
    "@types/node-cron": "^3.0.8",
    "@types/react": "^18.2.25",
    "prisma": "^5.0.0",
    "ts-node": "^10.9.1",
    "typescript": "^5.1.6"
  },
  "dependencies": {
    "@clerk/clerk-sdk-node": "^4.12.1",
    "@prisma/client": "^5.0.0",
    "@react-email/components": "^0.0.7",
    "@react-email/render": "^0.0.7",
    "@sendgrid/mail": "^7.7.0",
    "axios": "^1.5.1",
    "bullmq": "^4.6.0",
    "dayjs": "^1.11.9",
    "dotenv": "^16.3.1",
    "langchain": "^0.0.118",
    "metaphor-node": "^1.0.22",
    "node-cron": "^3.0.2",
    "puppeteer": "^19.11.1"
  },
  "description": ""
}

tsconfig:
{
	"compilerOptions": {
		"jsx": "react",
		"target": "ESNext",
		"module": "ESNext",
		"moduleResolution": "NodeNext",
		"esModuleInterop": true,
		"allowSyntheticDefaultImports": true,
		"forceConsistentCasingInFileNames": true,
		"strict": true,
		"skipLibCheck": true,
		"outDir": "./dist"
	}
}

Hi @Potrock! Thanks for raising the issue. Are you able to modify your tsconfig to use moduleResolution: 'commonjs'. I'll continue investigating how we can make metaphor-node compatible with nodenext, but for now, please let me know if this fixes your issue.

Hi @Potrock! Thanks for raising the issue. Are you able to modify your tsconfig to use moduleResolution: 'commonjs'. I'll continue investigating how we can make metaphor-node compatible with nodenext, but for now, please let me know if this fixes your issue.

This works. Thanks @jiito .


In the home page, the photos in the headphone, tshirt and mobile section is disoriented

Currently in the home page, the photos go out of the container in which they are kept, that is for all the sections as you can see

I would like to make this right and fix it

I would like to fix this and work on it @JigarJoshi04 @codervivek5
Please assign this


Docs: remove conflicting desc. of default freezing behavior

Hi Immer maintainers,
Just a small drive-by docs fix! This PR clarifies the default freezing behavior by removing one of the conflicting descriptions.
Thanks,
xkxx

Nice!

:tada: This PR is included in version 4.0.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Syntax errors for duplicate object properties

Fixes for syntax errors which should have been triggered outside strict mode too.
See discussion on http://code.google.com/p/esprima/issues/detail?id=166

Merged. Thanks!


[Question] How to remove cookies?

I am having some problem figuring out how to remove cookies.
Cause you need to have the cookie in order to remove it, which to me is weird as i would expect to remove it by it's name.
But if you get the cookie beforehand you can't use that cookie to remove it cause of lifetime issues.
Are you supposed to just create a dummy cookie like in the Counter example?
    async fn handler(Extension(cookies): Extension<Cookies>) {
        let key = KEY.get().unwrap();
        let private_cookies = cookies.signed(key);
        cookies.remove(Cookie::new(COOKIE_NAME, ""));
    }

Hey :)
Yep, a dummy cookie is ok. I see your point, but tower-cookies is just a tokio middleware around cookie crate, I guess they have their reasons for this kind of api. Here's the description of its remove method. Maybe make_removal is what you're looking for.

Hey :)
Thanks for the quick response.
It indeed looks like make_removal is what i am looking for.
Is it possible to expose it from tower-cookies?
same goes for SameSite, cause then one wouldn't need to have the cookie crate in parallel.

But then i still use the cookie i grabbed which doesn't work cause of the lifetime right?

Right. I don't see an obvious way to fix this. And also I don't remember ever needing make_removal, it feels always easier to just "remove" potentially non-existing cookie (it won't even create unnecessary header if the cookie doesn't exist as there won't be any "delta").
As for removing cookies by name, it certainly feels more intuitive, thank you for the suggestion. Could you review the changes before I merge it: https://github.com/imbolc/tower-cookies/commit/56a1fc359e5005ee6c1e83c11833086bf29bf36a

Hmm... I don't think it's a correct approach though as cookie::CookieJar::remove says:

To properly generate the removal cookie, cookie must contain the same path and domain as the cookie that was initially set.

So I guess we should first check if the cookie is there and use its path and domain while removing it just by name.

I think it's done: https://github.com/imbolc/tower-cookies/pull/15
@davidpdrsn @programatik29 would one of you guys have a few minutes to review it? It makes it possible to remove cookies by name, thakns :pray:

Oh you work quick.
Good catch with the Path part, otherwise it would be quite prone to "error".
Also, i remove some cookies in my error handler, but i don't know how to use the tower-cookies there as you just get access to the error and make a response.
Is there something i am might be missing you think, or might this just be a special case where i gotta use headers directly?
Thanks:)

Also, i remove some cookies in my error handler, but i don't know how to use the tower-cookies there as you just get access to the error and make a response.

What specifically do you mean by "error handler"? Do you mean using HandleErrorLayer, because that also supports running extractors. async fn handle_error(cookies: tower_cookies::Cookies, err: axum::BoxError) should work.

Or in case of a middleware, where you have only a request you can use Cookies::from_request: https://github.com/imbolc/tower-cookies/blob/353003051701d3e0d728301614bde80201e2a875/examples/counter-extractor.rs#L22

It's a impl IntoResponse for MyError
Perhaps no the correct way to do it?

Jar is kept in request extensions, so no access to request - no cookies :)

make sense:)
So can i "solve" this by using a middleware or?
The purpose of the error handling is to be able to use Result.
But yeah this is clearly off topic so feel bad taking up even more of your time, so no need to really answer this.

If you have request where you raise the error, you can process cookies there:
enum Error {
    LogOut
}

impl Error {
    log_out(req: RequestParts) -> Self {
        let cookies = Cookies::from_request(req).await?;
        ...
        Self::LogOut
    }
}

If you don't have the request, you can put something into the response extensions. And then in a middleware you can check the extensions and change cookies. Maybe there's a simpler way of doing this, you can ask in the axum discord: https://discord.com/channels/500028886025895936/870760546109116496

So I guess we stick with the current behavior :)


Add HOTH workshops to Archive

I realize that we didn't add HOTH workshops to https://hack.uclaacm.com/archive. This issue tracks doing so.

Fixed by #169.


[systemd integration] Need to ensure that systemd timer is automatically enabled

After installing the latest packages after adding the systemd service and timer, and rebooting, I don't see the timer service being enabled:
sudo systemctl status scc-hypervisor-collector.{timer,service}
\u25cf scc-hypervisor-collector.timer - update SCC daily with collecter hypervisor details
     Loaded: loaded (/usr/lib/systemd/system/scc-hypervisor-collector.timer; static)
     Active: inactive (dead)
    Trigger: n/a
   Triggers: \u25cf scc-hypervisor-collector.service
       Docs: man:scc-hypervisor-collector(1)
             man:scc-hypervisor-collector.service(8)

\u25cf scc-hypervisor-collector.service - run scc-hypervisor-collector if valid config defined
     Loaded: loaded (/usr/lib/systemd/system/scc-hypervisor-collector.service; static)
     Active: inactive (dead)
       Docs: man:scc-hypervisor-collector(1)
             man:scc-hypervisor-collector.service(8)

This needs investigation & fixing.

The systemd .timer script is missing an [Install] section WantedBy= setting.

This was fixed by #39


Update auxtools

make sure to edit Cargo.toml and to point to your own auxcallback and then cargo update -p auxcallback before merging

I'm just pushing all my fixes into this PR


Dashboard

Dashboard with a bit of styling.

added dashboard(Nav) with bootstrap
changed css to scss file
installed loaders needed for sass file

Look great. Thanks Elie.


docker-compose up failing, Dockerfile out of date

Expected Behavior

Upon cloning boozallen/projectjellyfish, you should be able to run docker-compose up from a Docker terminal to create and start both a web and db container.
Current Behavior

Running docker-compose up will create db container, and attempt to create web container. Web container will fail on NPM install (Step 17).
Possible Solution

As per #1147 the build process has changed to no longer use npm and gulp, in favor of bundle and rake tasks. The Dockerfile/docker-compse.yml should be updated to reflect this change.
Steps to Reproduce (for bugs)

Clone boozallen/projectjellyfish
Open a docker terminal and navigate to repository
From the newly cloned repository, run docker-compose up

Context

With your release of v4.0.0, you are currently unable to run Project Jellyfish as a Docker container.
Your Environment

Version used: v4.0.0 (#1159)
Browser Name and version: N/A
Operating System and version (desktop or mobile): Mac OSX (Desktop)

Looking into this.

Looks like the builds were failing.  should be working now.


chore: support light mode, dark mode logo

Minor fix for dark and light mode in readme
It looks like there is no proper method to fix this with RST
Added css to svg to support the mode

I see there is issue with Safari and prefers-color-scheme for SVG files.
One option is to use the normal text for Datachain but it will be on new line below logo. Let me know if it's okay.

One option is to use the normal text for Datachain but it will be on new line below logo. Let me know if it's okay.

@yathomasi, this might be a better solution. https://github.blog/changelog/2021-11-24-specify-theme-context-for-images-in-markdown/

There is also support for showing images based on theme (see https://github.blog/changelog/2022-05-19-specify-theme-context-for-images-in-markdown-beta/), but for that we'll have to change README to markdown from rst.

Thanks @djsauble @skshetry for your inputs.
I am sorry to mention that I had already went through all of those before suggesting the solution. Let's go with the suggestion mentioned if we want to support Safari.

Thanks @djsauble. That's great. Merged your change.


bug: M3-2102 Notification flags missing in Linodes landing.

Original PR: https://github.com/linode/manager/pull/4292
Description
Notifications were not matched up with Linodes resulting in the notification flag not appears on the Landing items (rows/cards).
Type of Change

bug

Note to Reviewers
Either have a Linode with a pending/scheduled migration and view the Linodes landing page. A flag should appear in the Card or Row for the specific Linode. On hover the notification message should be displayed.

Extracted styles for card and row view.
Created HOCs for;

withRecentEvent
withDisplayType
hasMutationAvailable

Combined LinodeRow and LinodeRowWithState.
All three are used on both row and card views.

Coverage increased (+0.04%) to 33.016% when pulling 3613220b62166c29ffb42096bd019ea3857c13fb on rjstires:M3-2102 into 7f6d210d9865208e22f8c50c04126a0be5716002 on linode:develop.


Update Capabilities.java to use fhir-cache

Capabilities.java currently uses a ConcurrentMap to manage a tenant-specific cache for the capabilities statement. This could be updated to use a fhir-cache managed cache with a time-based eviction policy.

After setting the fhirServer/core/capabilityStatementCacheTimeout property to 1 (minute), I ran the following two tests.

GET [base]/metadata

get it again right away and confirm that its cached (by noting response time and CapabilityStatement.date)

wait a minute, then try again.

GET [base]/metadata?mode=terminology

get it again right away and confirm that its cached (by noting response time and TerminologyCapabilities.date)

wait a minute, then try again

In each case, the resource was server cached in step 2 and served fresh on step 3.


[Merged by Bors] - chore(Geometry,GroupTheory): use since syntax for all deprecation dates

Thanks for the reviews!


Clarify meaning of "Node allocation time"

I'm using low-priority nodes and try to understand what "node allocation time" means. This is what it shows in the Azure Portal:

My confusion here is with preemption of nodes. If a node gets preempted such that a new node has to join the pool, would that mean that the allocation time is reset? Or does it stay at the initial value and the logical "node" does not in fact leave/join the pool but is just receiving a VM under the covers?
What confuses me in the screenshot above is that the last boot time seems to be way after allocation, so maybe when the node got preempted? It's quite hard to really understand what's happening without a more detailed historic log.

We can definitely improve the documentation here.
To answer your specific question though, allocation time is indeed the time that node logical node is allocated for the first time. This is unaffected by preemption (as the logical node hasn't changed, it has the same name, etc).
Last boot time is the last time the Batch agent running on the node booted. That means it will get updated when any of the following happen:

The node boots for the first time
The node reboots (due to user request or due to an underlying Azure infrastructure issue)
The node is reimaged
The node is preempted and then is recovered by batch

@alfpark you can probably assign this to me and I can improve the documentation on these properties for our next API version.

I've made some improvements to the docs which should be making their way public in the next week or so. @alfpark I believe we can close this

@matthchr Can you link to the commit(s) that changed it?

It's not actually merged yet, it's included in this PR


Issue with watchdog

Fix inc .44 released

Now its working.
@dtandersen i think 0.16.44 is missing if you want them add it manualy


ignore option seemingly having no effect

I have some styles that are only active after user interaction, and have added that class to the ignore parameter - but any selectors starting with .offCanvas are missing after unCSS has run.
I've tried different ways of defining the classes to ignore, but there's no change.
Am I doing something wrong? (This is using Gulp)
.pipe(uncss({   html: [index.html],   ignore: [    '.offCanvas *'             ]  }))
Thanks,
John

Regexs have saved the day - thanks to @ben_eb for the answer:
 '/\.offCanvas/' did it


Update for History Plugin, ESRPSigning_core.json

Summary of the Pull Request
Update for History Plugin.

PR Checklist

[ ] Closes: #xxx
[ ] Communication: I've discussed this with core contributors already. If work hasn't been agreed, this work might be rejected
[ ] Tests: Added/updated and all pass
[ ] Localization: All end user facing strings can be localized
[ ] Dev docs: Added/updated
[ ] New binaries: Added on the required places

[ ] JSON for signing for new binaries
[ ] WXS for installer for new binaries and localization folder
[ ] YML for CI pipeline for new test projects
[ ] YML for signed pipeline

[ ] Documentation updated: If checked, please file a pull request on our docs repo and link it here: #xxx

Detailed Description of the Pull Request / Additional comments
For https://github.com/microsoft/PowerToys/pull/19569

Validation Steps Performed

Why do we need extra prs here. Splitting things up bri gs complexity for reviewers. Can we do these things in the plugin pr please.

Why do we need extra prs here. Splitting things up bri gs complexity for reviewers. Can we do these things in the plugin pr please.

Agree. To small change for separate PR :)

Why do we need extra prs here. Splitting things up bri gs complexity for reviewers. Can we do these things in the plugin pr please.

Agree. To small change for separate PR :)

I agree also and I am the one that did this!
It's my fault, I am new to this project and there are a number things across multiple VS projects, and even things to do in external docs repos when adding a new plugin. @htcfreek did a fantastic job of holding my hand here, but I think I needed a bit more, sorry.
Also, @htcfreek I was confused by you saying "All these thing can be done in different PRs." here (https://github.com/microsoft/PowerToys/pull/19569#issuecomment-1214447567).
@stefansjfw, @htcfreek:
I see now that I DO need a separate PR for MicrosoftDocs" only, because this is in a separate repo. I think that one is fine and is here, https://github.com/MicrosoftDocs/windows-uwp/pull/3998.
With regard to the extra/separate PRs here, which are:

doc/devdocs/modules/launcher/plugins/history.md

.pipelines/ESRPSigning_core.json
 (this one...)

Should we proceed and (I) promise to not do this again? Or should close these two PRs and just add the code to the current/main PR here, https://github.com/microsoft/PowerToys/pull/19569.
Either is fine with me.

The reason for having it in a single PR is if we need to revert it for some reason (and I don't say it will happen :P) we can just revert a single merge commit. This way we'll need to do it for every PR

No need to explain, I get it. But you didn't actually answer the question.
Should we proceed OR should I close https://github.com/microsoft/PowerToys/pull/19917 and https://github.com/microsoft/PowerToys/pull/19919 add the changes from those PRs into https://github.com/microsoft/PowerToys/pull/19569.
@stefansjfw say the word. I'm happy to do the work to make this less complicated for us all now and in the future.

No need to explain, I get it. But you didn't actually answer the question.
Should we proceed OR should I close #19917 and #19919 add the changes from those PRs into #19569.
@stefansjfw say the word. I'm happy to do the work to make this less complicated for us all now and in the future.

Right, sorry. Please merge to a single PR. BTW, I'm looking into the main PR now. Thanks

Merged with #19569, closing this. Dead.


README

@Zapadlo Updated the README with the end points. Can you give feedback please. Thank you.
The following are the three endpoints I have currently defined:
/hosts - For the tiles on the dashboards (should this be named something else? )
/widgets - For widgets in dashing
/dashboard - For dashboards

How about calling tiles - "tiles"? :)
At least our tiles represent clusters, others might be different.

Tiles!
Thank you George :)


Set MacOS Runner to 11 and Fix Unknown Method Error

Did a fork and build to get reacclimatized to the code base.  A few observations.  One, the build contained an unknown method error.  Two, the test matrix was pulling macos-latest, which used OpenSSL3 and broke the tests.  Three, the CI pipeline isn't running the full set of tests.  This PR addresses the first two issues.  I'm not sure what the rationale was for running only a small subset of tests in GitHub actions, but we may want to consider running them all, at least in some of the matrix builds.

Including the console output for the unit tests.
test_output.txt

Codecov Report

Merging #242 (f700eed) into master (26b8ffb) will decrease coverage by 0.39%.
Report is 11 commits behind head on master.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##             master     #242      +/-   ##
============================================
- Coverage     75.04%   74.65%   -0.39%
+ Complexity      448      445       -3
============================================
  Files            38       38
  Lines          1823     1823
  Branches        181      181
============================================
- Hits           1368     1361       -7
- Misses          341      348       +7
  Partials        114      114

Files Changed
Coverage Δ

...g/apache/commons/crypto/utils/ReflectionUtils.java
91.66% <100.00%> (ø)

... and 3 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Inconsistent Focus Behavior with Lists

Provide a general summary of the issue here
The issue can be demonstrated in the Storybook - ListView - default.

Click into "focus before" and tab into the ListView. The first item is focused. Now tab into "focus after" and shift-tab back. Again, the first item is focused.
Now make sure the last active item ("Adobe Illustrator") is focused in the List, and do the above steps again. When you shift-tab back, the checkbox is focused, not the item.

🤔 Expected Behavior?
The item should be focused in the second scenario, not the checkbox.
😯 Current Behavior
Storybook link
💁 Possible Solution
No response
🔦 Context
No response
🖥 Steps to Reproduce
See summary. Also happens in the docs
Version
main branch
What browsers are you seeing the problem on?
Firefox, Chrome, Microsoft Edge
If other, please specify.
No response
What operating system are you using?
windows
🧢 Your Company/Team
No response
🕷 Tracking Issue
No response

After looking into the code: shift-tab moves focus to the last item's button, and useSelectableCollection kicks in. The onFocus handler deals with most cases, except for one: The browser moves focus to the last button and the last item is focusedKey. Because of the test
if (!element.contains(document.activeElement))

the focus remains on the button.
One possible solution is to change the above test to:
if (!element.contains(document.activeElement) || !e.relatedTarget || (ref.current && !ref.current.contains(e.relatedTarget)))

I have tested this and found no issues, but this is located deeply enough to require more consideration.

Thanks for the issue. We'll most likely be revisiting this as a part of a push to support edit mode/interactive elements within grids, will update this when we settle on desired behavior


ci: setup PyPi releases

[x] Set up test PyPi trusted publisher
[x] Set up PyPi trusted publisher
[x] Merge #14

We currently have a blocker: caikit-nlkp is not currently released on pypi because it depends on the git version of peft. Until https://github.com/caikit/caikit-nlp/pull/265 is merged and released, we can only publish on pypi if we delete/comment out the caikit-nlp test dependency (which I guess is not a blocker)

Set up a trusted publisher on pypi:


Hide a node based on a condition

Hello Author,
Thanks you for your wonderful work & thanks very much for providing a solution for my previous request.
Is there a way to conditionally hide/show a node?
I'm working on a feature where expanding a particular node reveals multiple children with the same attributes. I'd like to show just one child node and display the number of similar nodes (essentially hiding the duplicates).
I also want this functionality to work when expanding all
Thanks in advance

Hi, why not precomputing that data before passing it to the org chart and then just showing up that number inside nodes?
I don't see why that logic has to be inside org chart

Yes, I did that. I removed duplicate nodes from data then rendered the chart, but it’s not possible to see all the children if I want to since I removed from data
Was just looking for any functionality in the chart itself 😊
I can keep original data and load the chart with modified data. And when I want to see all the children while expanding then I’ll have render chart with original data

I was wondering if there could be any easy way to implement this 😊

@ganeshpaharan  can you add some kind of rough sketches of what you want, I might not be understanding it fully

Sure
Below is the example I’m trying to achieve

@ganeshpaharan  can you also link an online sample where you tried my suggestion  and faced the problem which you mentioned?
You can extend this sample - https://stackblitz.com/edit/js-mfzkbs?file=index.html


[release-1.13] remote.Image respect fetchOpts

Manual cherrypick required.
#37318 failed to apply on top of branch "release-1.13":
Applying: `remote.Image` respect `fetchOpts`
Using index info to reconstruct a base tree...
M	pkg/wasm/imagefetcher.go
Falling back to patching base and 3-way merge...
Auto-merging pkg/wasm/imagefetcher.go
CONFLICT (content): Merge conflict in pkg/wasm/imagefetcher.go
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 `remote.Image` respect `fetchOpts`
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

wait for https://github.com/istio/istio/pull/37532

new PR: https://github.com/istio/istio/pull/37554

/close


[BUG] Missing line at Bhagavad Gita Shloka 1.20

🙁 Actual behavior
In this issue, it seems that the third line is missing in the Sanskrit version of the shloka. But it is completed in Romanized text.
Missing line

Complete shloka from holy-bhagavad-gita.org

🙂 Expected behavior
It should include the third line in the Sanskrit version of Shloka.
🔢 Steps to Reproduce the Problem

Go https://bhagavadgita.io/
Navigate to chapter 1 verse 20.
You can see the third line is missing in the Sanskrit version of the Verse.

If this issue is still open can i try working on this ?


⚠ ClamAV has degraded performance

In c951652, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 201 ms

Resolved: ClamAV performance has improved in af6fe59.


ParquetCachedBatchSerializer (PCBS) shouldn't write int96

I made a mistake writing int96 to cache
Signed-off-by: Raza Jafri<EMAIL_ADDRESS>

build


Add prodigal module (already tested)

PR checklist

[ ] I added prodigal module and insert it inside metatdenovo.nf script.

I added the If statement and the params.orf_caller. I checked it and it works.
Also, I added a new line for samplesheets.csv

Didn't you update the schema with the new parameters (both orf_caller and the one you used for training data)?

I didn't, how should I do?

Didn't you update the schema with the new parameters (both orf_caller and the one you used for training data)?

I didn't, how should I do?

There's a tool in nf-core that helps you: nf-core schema build (remember to change into the correct branch).
More documentation here: https://nf-co.re/developers/adding_pipelines#nf-core-pipeline-structure. (One is not advised to update it with a text editor, but if you're working in sequoia, it will be difficult with the web interface. Either do it with a text editor, copying a relevant example param, or push the branch and pull to your local computer and do the update there.)


Some words can not be encoded (upper case and lower case)

Hi, @vaibhavad
I met the same problem as @Yan2266336 raised. For example, when trying to encode the word 'alleged', it returns the following error:
RuntimeError: The expanded size of the tensor (2) must match the existing size (3) at non-singleton dimension 0.  Target sizes: [2].  Tensor sizes: [3].
I am using llm2vec==0.1.8 plus mntp-supervised and could you please check the problem? Thanks!

Hi, @vaibhavad I met the same problem as @Yan2266336 raised. For example, when trying to encode the word 'alleged', it returns the following error: RuntimeError: The expanded size of the tensor (2) must match the existing size (3) at non-singleton dimension 0. Target sizes: [2]. Tensor sizes: [3]. I am using llm2vec==0.1.8 plus mntp-supervised and could you please check the problem? Thanks!

Meanwhile, I found that even if the encoding vector of 'Alleged' and 'ALLEGED' is the same, the encoding vector of the following two sentences are different: 'Alleged is related to crime' and 'ALLEGED is related to crime'. Can you explain it?

Hi @wyhwhy,
Thank you for your interest in our work. Can you provide a code sample to reproduce the issue?

Hi @wyhwhy,
Thank you for your interest in our work. Can you provide a code sample to reproduce the issue?
You can also see my response on #80 to see if it is the same underlying problem.

Hi, since this is not the same problem as issue #80, the code sample is as follows:
import torch
from llm2vec import LLM2Vec
l2v = LLM2Vec.from_pretrained(
"llama3-8B",
peft_model_name_or_path="/McGill-NLP/LLM2Vec-Meta-Llama-3-8B-Instruct-mntp-supervised",
device_map="cuda" if torch.cuda.is_available() else "cpu",
torch_dtype=torch.bfloat16,
)
documents = ['alleged','Alleged','ALLEGED']
d_reps = l2v.encode([documents[0]]) #error happens here
d_reps = l2v.encode([documents[1]]) #no error
d_reps = l2v.encode([documents[2]]) #no error
We have found that this bug comes from Line 160 in llm2vec.py, in which the revised code should be: 't = text.split(" !@#$%^&*()")', .i.e., a space in front of '!'. Thanks.

Thanks for finding this bug and fixing it!


caoyue.WindowResizer version 1.0.1

Checklist for Pull Requests

[x] Have you signed the Contributor License Agreement?
[ ] Is there a linked Issue?

Manifests

[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[x] Have you validated your manifest locally with winget validate --manifest <path>?

[x] Does your manifest conform to the 1.6 schema?

Note: <path> is the directory's name containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

Manual Validation ended with:

Application: WindowResizer.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.IO.FileNotFoundException    at WindowResizer.TrayContext+d__5.MoveNext()    at System.Runtime.CompilerServices.AsyncTaskMethodBuilder.Start[[WindowResizer.TrayContext+d__5, WindowResizer, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null]](d__5 ByRef)    at WindowResizer.TrayContext.Update()    at WindowResizer.Program.Main()
Faulting application name: WindowResizer.exe, version: <IP_ADDRESS>, time stamp: 0x61cd5930
Faulting module name: KERNELBASE.dll, version: 10.0.19041.1202, time stamp: 0xc9db1934 Exception code: 0xe0434352 Fault offset: 0x0000000000034f99
Faulting process id: 0x2fc
Faulting application start time: 0x01dafe25c4de83d4
Faulting application path: C:\Users\User\AppData\Local\WindowResizer\app-1.0.1\WindowResizer.exe
Faulting module path: C:\Windows\System32\KERNELBASE.dll Report Id: f76b1af5-e4e0-40f4-a9e3-dbadeee814ed
Faulting package full name:
Faulting package-relative application ID:

(Automated response - build 894.)

Clicking "Open Setup Log" just closes the window.

This was a known bug in Squirrel Installer, but they didn't fix that yet.
Usually the setup log located at %localappdata%\SquirrelTemp, could you please check the setup log located in that directory?

@wingetbot run

The window is not resizable, and there seems to be some text peeking up from the lower left.


Decimal Places

Throughout the software, we're using 4 places after the decimal. We should use appropriate levels of rounding for the different results. It does not make sense to report 1/1000 of a dollar.

Probability should have 4 decimal places, everything else should have 2 decimal places.

the string constants class defines to defaults:

N2 is two decimal places and N4 is 4 decimal places.
This is an example of how it gets used by the UI

I am going to go top to bottom through the tree and document the fields that have decimals:
Unsteady HDF:

Steady HDF:

Gridded:

Frequencies needs some work.
Original:

I am updating the table with plot to use the default instead of the detailed format. This is global. As the comment indicates we should probably come up with a way to pass what format we want per column.

This is the new table:

Scenario results:
These look good:

Alternative Results:

Alternative comparison report results:

How to update the table with plot to format columns differently?
I am sure there is a more elegant solution, but it is very easy to do it based on the column header name.

I think another tactic would be to have the decimal places as an attribute similar to how we do the headers, but that doesn't solve the issue if we want "x value" to sometimes be 2 and sometimes be 4 decimal places. But here is how you would do that.
1.) add another attribute for precision

2.) Then i think it would show up in this column attribute object and you could check the desired precision and set the column to have that precision.


sample_glue_loader returns 'Something went wrong...' on the front-end

Expected Behavior
Glue tables metadata is displayed on the front-end
Current Behavior
On the front-end, I see 'Something went wrong...'
Possible Solution

Steps to Reproduce
I am running Amundsen on my local machine:

followed the installation guide at https://github.com/amundsen-io/amundsen/blob/master/docs/installation.md, including the required python libraries.
modified sample_glue_loader and added aws session token.
when I opened the front-end, the tables from Glue were listed but when I click any, the error displayed 'Something went wrong...' . The example of the URL of one of the tables (iriscsv) located in in the iris database is:
http://localhost:5000/table_detail/AWSSessionToken="/glue/iris/iriscsv.

Screenshots (if appropriate)
Context
I am doing a POC.
Your Environment

do you verify the table is ingested into neo4j correctly with neo4j UI?

do you verify the table is ingested into neo4j correctly with neo4j UI?

I can see the tables on neo4j, when I switch to the table view, I see the similar content for all tables retrieved:
{
"name": "test_table1",
"publisher_last_updated_epoch_ms":<PHONE_NUMBER>471,
"published_tag": "unique_tag",
"key": "hive://gold.test_schema/test_table1",
"is_view": false
}

I can see the tables on neo4j, when I switch to the table view, I see the similar content for all tables retrieved:
{
"name": "test_table1",
"publisher_last_updated_epoch_ms":<PHONE_NUMBER>471,
"published_tag": "unique_tag",
"key": "hive://gold.test_schema/test_table1",
"is_view": false
}

I'm experiencing the same thing as well. Any help here

I'm experiencing the same thing as well. Any help here

OElesin, check the Athena one if you need to get crawl the s3 data. If you use Python, not Airflow, I slightly modified the original code at https://github.com/eponkratova/articles/blob/master/data_discovery/code/athena_data_loader.py

OElesin, check the Athena one if you need to get crawl the s3 data. If you use Python, not Airflow, I slightly modified the original code at https://github.com/eponkratova/articles/blob/master/data_discovery/code/athena_data_loader.py

@eponkratova, I tried this and got the same error. This is quite surprising

@eponkratova, I tried this and got the same error. This is quite surprising

From the error logs
self.client = get_proxy_client()
--
File "/usr/local/lib/python3.7/site-packages/amundsen_metadata-3.0.1-py3.7.egg/metadata_service/proxy/__init__.py", line 47, in get_proxy_client
client_kwargs=client_kwargs)
TypeError: __init__() got an unexpected keyword argument 'client_kwargs'

From the error logs
self.client = get_proxy_client()
--
File "/usr/local/lib/python3.7/site-packages/amundsen_metadata-3.0.1-py3.7.egg/metadata_service/proxy/__init__.py", line 47, in get_proxy_client
client_kwargs=client_kwargs)
TypeError: __init__() got an unexpected keyword argument 'client_kwargs'

@feng-tao and @eponkratova, the issue is likely due to recent changes in the metadata library. I reverted the image being used to amundsen-metadata:3.0.0 and everything seems to be fixed.
Looks like this is from: https://github.com/amundsen-io/amundsenmetadatalibrary/blob/master/metadata_service/proxy/init.py#L47

@feng-tao and @eponkratova, the issue is likely due to recent changes in the metadata library. I reverted the image being used to amundsen-metadata:3.0.0 and everything seems to be fixed.
Looks like this is from: https://github.com/amundsen-io/amundsenmetadatalibrary/blob/master/metadata_service/proxy/init.py#L47

@OElesin , so, did you make the Glue connector working as well?

@eponkratova, both are working.

Aha, thank you, @OElesin

cc @mgorsk1

I have installed new code and I am also facing the same issue and it complains about
TypeError: __init__() got an unexpected keyword argument 'client_kwargs'

@mgorsk1 could you take a look?

sure, looking into it

apologies, that's my blunder. I've submitted fix https://github.com/amundsen-io/amundsenmetadatalibrary/pull/258 any chance you can verify if that helped @OElesin @eponkratova

no worry, @mgorsk1 's change (https://github.com/amundsen-io/amundsenmetadatalibrary/pull/258) is just merged. @NiravLangaliya could you pull from master and see if the issue is gone?

Feel free to reopen if the issue persists after pulling from master.

@feng-tao - I'm getting the same issue now with loading Glue data. I'm on the latest branch from master, my data is in neo4j. When I click on a table in the WebUI I get 404 not found. Any guidance would be appreciated!


Dedicated mailer support for Mailables

With this change we will be able to use dedicated mailer that was set in Mailable, instead of overriding it.
Solves this issue: https://github.com/laravel/framework/issues/32979 and doesnt break anything.

https://laravel.com/docs/8.x/mail#sending-mail-via-a-specific-mailer
You can wrap this logic behind your own method that receives a mailable, etc.


Bugs..

After last update:
1- The amount of bots that is spawning is always showing 0 even though some of the bots are working.
2- This error is showing: Cannot read property 'name' of undefined
@pulviscriptor Hope you help me. Thank you.
Also anyway that knows how to fix them, please comment down below how. Thanks :)

these are agar-feeder-bot related issues, please close this and open it at davidmann's repo.

But they only happened since pulviscriptor updated his repo ... and David didn't touch his. Plus david isn't replying lately so pulviscriptor might help me ._. Anyway I got this new error also.. I don't know what's happening.

@ElieeCh thats called a packet error, some say it is caused from bad proxies.

Does it matter if the proxies are transparent or anonymous or elite ?
Also most of mine are pretty fast.. I've already checked them with 3 different programs...

Okay, so I was using a modified version ogar-feeder-bot made by david, now that I've tried using his version the only error left is this one

Edit: It looks like the error that I see (from unexpected server response <400>) is caused by my proxies because I'm using HTTP ones also I don't know why they're causing this error even though most of them are working fine.


Update offering-ISO-27001.md

Changed intune to Microsoft Endpoint Manager

Issue#https://github.com/MicrosoftDocs/microsoft-365-docs/issues/2027

@JohanFreelancer9 - kindly do the copy editor review for this PR. Thanks.

Closing this as not merged - Endpoint Manager includes the Intune service (among others) and is not a 1:1 rebranding for Intune in all cases. I will confirm the broader strategy for including Endpoint Manager in the compliance offering topics.


updated splash screen background color

XCODE IS FUN

Before (taken from alpha branch):

After (taken from splash-background-color branch):


Create hello.c

Initial commit - ANSI C version of "hello.bas"

I made the input processing case-sensitive by default, but strings_match() could easily use strncasecmp() instead.


"Owner not found in a voice channel, could not autosummon"

Can someone help me fix this issue? I am connected to the voice channel.

Do you see the bot listed as a user in the server?

yes

In the the options.ini file, do you have your user ID listed as the bot owner?

Thank you so much! I got it working! :)


Broker URL does not support context paths

Given a base URL of HOST/path, when the broker client navigates the HAL paths it joins the given Base URL with the path defined in the HAL response. This results in duplicate context paths in subsequent requests:
See the following slightly modified log (for readability):
Verifier Output
---------------

Failures:

1) Failed to load pact - Could not load pacts from the pact broker 'https://notarealhost/pactbroker/'

There were 1 pact failures

Verifier Logs
-------------
2022-09-22T08:41:28.393792Z TRACE ThreadId(01) pactffi_verifier_execute{handle=0x19ff671b120}: pact_verifier: fetch_pacts(source=PactBrokerWithDynamicConfiguration(https://notarealhost/pactbroker/, provider_name='MerchantsCore', enable_ending=false, include_wip_since=None, provider_tags=[], provider_branch=None, consumer_version_selectors='[ConsumerVersionSelector { consumer: None, tag: None, fallback_tag: None, latest: Some(true), deployed_or_released: None, deployed: None, released: None, environment: None, main_branch: None, branch: None, matching_branch: None }], auth=None'), consumers=[])
2022-09-22T08:41:28.393858Z TRACE ThreadId(01) pactffi_verifier_execute{handle=0x19ff671b120}: pact_verifier: fetch_pact(source=PactBrokerWithDynamicConfiguration(https://notarealhost/pactbroker/, provider_name='MerchantsCore', enable_ending=false, include_wip_since=None, provider_tags=[], provider_branch=None, consumer_version_selectors='[ConsumerVersionSelector { consumer: None, tag: None, fallback_tag: None, latest: Some(true), deployed_or_released: None, deployed: None, released: None, environment: None, main_branch: None, branch: None, matching_branch: None }], auth=None'))
2022-09-22T08:41:28.393934Z TRACE ThreadId(01) pactffi_verifier_execute{handle=0x19ff671b120}: pact_verifier::pact_broker: fetch_pacts_dynamically_from_broker(broker_url='https://notarealhost/pactbroker/', provider_name='MerchantsCore', pending=false, include_wip_pacts_since=None, provider_tags: [], consumer_version_selectors: [ConsumerVersionSelector { consumer: None, tag: None, fallback_tag: None, latest: Some(true), deployed_or_released: None, deployed: None, released: None, environment: None, main_branch: None, branch: None, matching_branch: None }], auth=User(none, [no password]))
2022-09-22T08:41:28.407707Z TRACE ThreadId(01) pactffi_verifier_execute{handle=0x19ff671b120}: pact_verifier::pact_broker: navigate(link='pb:provider-pacts-for-verification', template_values={"provider": "MerchantsCore"})
2022-09-22T08:41:28.407743Z  INFO ThreadId(01) pactffi_verifier_execute{handle=0x19ff671b120}: pact_verifier::pact_broker: Fetching path '/' from pact broker
2022-09-22T08:41:28.408178Z TRACE ThreadId(01) pactffi_verifier_execute{handle=0x19ff671b120}: hyper::client::pool: checkout waiting for idle connection: ("https", notarealhost)
2022-09-22T08:41:28.408310Z DEBUG ThreadId(01) pactffi_verifier_execute{handle=0x19ff671b120}: reqwest::connect: starting new connection: https://notarealhost/
2022-09-22T08:41:28.408415Z TRACE ThreadId(01) pactffi_verifier_execute{handle=0x19ff671b120}: hyper::client::connect::http: Http::connect; scheme=Some("https"), host=Some("notarealhost"), port=None
2022-09-22T08:41:28.427866Z DEBUG ThreadId(01) pactffi_verifier_execute{handle=0x19ff671b120}: hyper::client::connect::http: connecting to <IP_ADDRESS>:443
2022-09-22T08:41:28.428570Z TRACE ThreadId(01) pactffi_verifier_execute{handle=0x19ff671b120}: mio::poll: registering event source with poller: token=Token(0), interests=READABLE | WRITABLE
2022-09-22T08:41:28.475216Z DEBUG ThreadId(01) pactffi_verifier_execute{handle=0x19ff671b120}: hyper::client::connect::http: connected to <IP_ADDRESS>:443
2022-09-22T08:41:28.475331Z DEBUG ThreadId(01) pactffi_verifier_execute{handle=0x19ff671b120}: rustls::client::hs: No cached session for DnsName(DnsName(DnsName("notarealhost")))
2022-09-22T08:41:28.475585Z DEBUG ThreadId(01) pactffi_verifier_execute{handle=0x19ff671b120}: rustls::client::hs: Not resuming any session
2022-09-22T08:41:28.475913Z TRACE ThreadId(01) pactffi_verifier_execute{handle=0x19ff671b120}: rustls::client::hs: Sending ...
2022-09-22T08:41:28.610819Z DEBUG ThreadId(01) pactffi_verifier_execute{handle=0x19ff671b120}: rustls::client::hs: ALPN protocol is None
2022-09-22T08:41:28.610835Z DEBUG ThreadId(01) pactffi_verifier_execute{handle=0x19ff671b120}: rustls::client::hs: Using ciphersuite TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
2022-09-22T08:41:28.610890Z DEBUG ThreadId(01) pactffi_verifier_execute{handle=0x19ff671b120}: rustls::client::tls12::server_hello: Server supports tickets
2022-09-22T08:41:28.653907Z DEBUG ThreadId(01) pactffi_verifier_execute{handle=0x19ff671b120}: rustls::client::tls12: ECDHE curve is ECParameters { curve_type: NamedCurve, named_group: secp256r1 }
2022-09-22T08:41:28.654245Z DEBUG ThreadId(01) pactffi_verifier_execute{handle=0x19ff671b120}: rustls::client::tls12: Server DNS name is DnsName(DnsName(DnsName("notarealhost")))
2022-09-22T08:41:28.740611Z DEBUG ThreadId(01) pactffi_verifier_execute{handle=0x19ff671b120}: rustls::client::tls12: Session saved
2022-09-22T08:41:28.845266Z DEBUG ThreadId(01) pactffi_verifier_execute{handle=0x19ff671b120}: hyper::client::pool: pooling idle connection for ("https", notarealhost)
2022-09-22T08:41:28.845302Z DEBUG ThreadId(01) pactffi_verifier_execute{handle=0x19ff671b120}: reqwest::async_impl::client: response '200 OK' for https://notarealhost/pactbroker
2022-09-22T08:41:28.845403Z TRACE ThreadId(01) pactffi_verifier_execute{handle=0x19ff671b120}: pact_verifier::utils: with_retries: attempt 2/3 is Ok(Response { url: Url { scheme: "https", cannot_be_a_base: false, username: "", password: None, host: Some(Domain("notarealhost")), port: None, path: "/pactbroker", query: None, fragment: None }, status: 200, headers: {"server": "nginx", "date": "Thu, 22 Sep 2022 08:41:29 GMT", "content-type": "application/hal+json;charset=utf-8", "content-length": "5028", "status": "200 OK", "vary": "Accept", "x-content-type-options": "nosniff", "x-pact-broker-version": "2.102.2", "x-powered-by": "Phusion Passenger 5.3.7", "x-kong-upstream-latency": "8", "x-kong-proxy-latency": "1", "via": "kong/2.8.1"} })
2022-09-22T08:41:28.846124Z TRACE ThreadId(01) pactffi_verifier_execute{handle=0x19ff671b120}: pact_verifier::pact_broker: fetch_link(link='pb:provider-pacts-for-verification', template_values={"provider": "MerchantsCore"})
2022-09-22T08:41:28.846177Z TRACE ThreadId(01) pactffi_verifier_execute{handle=0x19ff671b120}: pact_verifier::pact_broker: fetch_url(link=Link { name: "pb:provider-pacts-for-verification", href: Some("https://notarealhost/pactbroker/pacts/provider/{provider}/for-verification"), templated: true, title: Some("Pact versions to be verified for the specified provider") }, template_values={"provider": "MerchantsCore"})
2022-09-22T08:41:28.846184Z DEBUG ThreadId(01) pactffi_verifier_execute{handle=0x19ff671b120}: pact_verifier::pact_broker: Link URL is templated
2022-09-22T08:41:28.846213Z DEBUG ThreadId(01) pactffi_verifier_execute{handle=0x19ff671b120}: pact_verifier::pact_broker: templated URL = https://notarealhost/pactbroker/pacts/provider/{provider}/for-verification
2022-09-22T08:41:28.847602Z TRACE ThreadId(01) pactffi_verifier_execute{handle=0x19ff671b120}: pact_verifier::pact_broker: Looking up value for key 'provider'
2022-09-22T08:41:28.847614Z DEBUG ThreadId(01) pactffi_verifier_execute{handle=0x19ff671b120}: pact_verifier::pact_broker: final URL = https://notarealhost/pactbroker/pacts/provider/MerchantsCore/for-verification
2022-09-22T08:41:28.847681Z  INFO ThreadId(01) pactffi_verifier_execute{handle=0x19ff671b120}: pact_verifier::pact_broker: Fetching path '/pactbroker/pacts/provider/MerchantsCore/for-verification' from pact broker
2022-09-22T08:41:28.847716Z TRACE ThreadId(01) pactffi_verifier_execute{handle=0x19ff671b120}: hyper::client::pool: take? ("https", notarealhost): expiration = Some(90s)
2022-09-22T08:41:28.847758Z DEBUG ThreadId(01) pactffi_verifier_execute{handle=0x19ff671b120}: hyper::client::pool: reuse idle connection for ("https", notarealhost)
2022-09-22T08:41:28.940398Z TRACE ThreadId(01) pactffi_verifier_execute{handle=0x19ff671b120}: hyper::client::pool: put; add idle connection for ("https", notarealhost)
2022-09-22T08:41:28.940414Z DEBUG ThreadId(01) pactffi_verifier_execute{handle=0x19ff671b120}: hyper::client::pool: pooling idle connection for ("https", notarealhost)
2022-09-22T08:41:28.940422Z DEBUG ThreadId(01) pactffi_verifier_execute{handle=0x19ff671b120}: reqwest::async_impl::client: response '404 Not Found' for https://notarealhost/pactbroker/pactbroker/pacts/provider/MerchantsCore/for-verification
2022-09-22T08:41:28.940435Z TRACE ThreadId(01) pactffi_verifier_execute{handle=0x19ff671b120}: pact_verifier::utils: with_retries: attempt 2/3 is Ok(Response { url: Url { scheme: "https", cannot_be_a_base: false, username: "", password: None, host: Some(Domain("notarealhost")), port: None, path: "/pactbroker/pactbroker/pacts/provider/MerchantsCore/for-verification", query: None, fragment: None }, status: 404, headers: {"server": "nginx", "date": "Thu, 22 Sep 2022 08:41:29 GMT", "content-type": "application/hal+json;charset=utf-8", "content-length": "0", "status": "404 Not Found", "vary": "Accept", "x-content-type-options": "nosniff", "x-pact-broker-version": "2.102.2", "x-powered-by": "Phusion Passenger 5.3.7", "x-kong-upstream-latency": "2", "x-kong-proxy-latency": "0", "via": "kong/2.8.1"} })
2022-09-22T08:41:28.940827Z ERROR ThreadId(01) pactffi_verifier_execute{handle=0x19ff671b120}: pact_verifier: Failed to load pact - \x1b[31mCould not load pacts from the pact broker 'https://notarealhost/pactbroker/'\x1b[0m
2022-09-22T08:41:28.940881Z  WARN ThreadId(01) pactffi_verifier_execute{handle=0x19ff671b120}: pact_matching::metrics:

In this case, the URL given is https://notarealhost/pactbroker/, the HAL link is https://notarealhost/pactbroker/pacts/provider/{provider}/for-verification and the constructed URL is https://notarealhost/pactbroker/pactbroker/pacts/provider/MerchantsCore/for-verification (note the duplicate path).
I believe rather than joining the user defined BaseURL and extracting paths from the HAL resources, we should just follow the fully qualified HAL resources. Is there a reason (e.g. security) that we're not doing this?

Not for security, it makes testing easier.

Thanks!


Problem composing per_samplify with functools.partial

model = TestModel() # From tests.scenarios
params = dict(model.named_parameters())
batch_inputs = torch.randn(3, 10)
batch_labels = torch.randint(2, (3,)).unsqueeze(-1)
batch_spec = {"inputs": batch_inputs, "labels": batch_labels}

def log_likelihood(params, batch):
    output = torch.func.functional_call(model, params, batch["inputs"])
    return -torch.nn.BCEWithLogitsLoss()(output, batch["labels"].float())

log_likelihood_per_sample = per_samplify(log_likelihood)

Works fine:
log_likelihood_per_sample(params, batch_spec)

Throws ValueError:
partial(log_likelihood_per_sample, batch= batch_spec)(params)
# ValueError: vmap(f_per_sample, in_dims=(None, 0), ...)(<inputs>): in_dims is not compatible with the structure of `inputs`. in_dims has structure TreeSpec(tuple, None, [*,
#  *]) but inputs has structure TreeSpec(tuple, None, [TreeSpec(dict, ['linear.weight', 'linear.bias'], [*,
#    *])]).

Fixed in #79


Fix pom

Fixed an error I was getting during the Maven build regarding annotations. Also changed the web.xml for the client to point to the correct welcome page.

Looks good ! Thanks Fernando.


No documentation yet.

No or nearly no documentation yet:

Add an installation section for macOS.
Add an installation section for macOS.
Add more information about this script.

I have add information in my main README.md and now I am creating README for each directory.


Ensure azure storage accounts are deleted only if empty

What this PR does / why we need it
Towards https://github.com/giantswarm/giantswarm/issues/31006
This PR ensures the storage containers are empty before we can delete them
Checklist

[x] Update changelog in CHANGELOG.md.

Closing, @marieroque is working on another fix


Guard undefs and use an object that implements :=~ in all Ruby versions for specs

Starting in Ruby 3.2 arrays no longer implement =~. So add a respond_to? in the proxy definition for hygiene and use a different object (a string) that does implement that method.

Thank you!


[RabbitMQ] Adds RabbitMQ

There's a pretty major issue with this, in order to do the admin of the rabbit server, I have to dl a python script. I cannot run it in the container, as the container doesn't have python in it (I was amazed, too). I think dling the python script, executing it, and then deleting it after the test run is the best way to do this, but if anyone has a better idea I'd be happy to hear it.

Awesome! thanks @gmmeyer


make the auth emails pretty

Right now the emails that are sent out at auth are very plain with just text and a link. It would be great to add some color and styling and make them look like they're part of Level 10.
It could be great to try out an email framework. MJML seems to be very popular, but Maizzle could be even better since it uses TailwindCSS just like Level 10 does.

Inspiration here: https://reallygoodemails.com/categories/welcome

Inspiration here: https://reallygoodemails.com/categories/welcome


feat: publish JS dependencies to appserver/package/static/js/dependencies.txt

More info: https://github.com/splunk/addonfactory-ucc-generator/issues/422

:tada: This PR is included in version 1.10.0 :tada:
The release is available on:

v1.10.0
GitHub release

Your semantic-release bot :package::rocket:


Set specific cell to have Focus in Worksheet

Can you set the cell that has focus or the selected cell in a sheet?
By default it will be A1 when opened
if you save an excel file - the last cell selected/focus is remembered when you reopen it so excel supports it

$worksheet.Select("B5")
This will only work on the first open though, the last selected cell overrides it afterwards. If you wanted it to work each time you'd probably have to make a macro.

Thanks


scrollableParent prop type problem

When I set scrollableParent to a DOM element, waypoint writes a warning Warning: Failed propType: Invalid prop scrollableParent supplied to Waypoint, expected a ReactNode. to the browser console.
Although README says that scrollableParent: PropTypes.any, in fact it's PropTypes.node (https://github.com/brigade/react-waypoint/blob/master/src/waypoint.jsx#L17) which causes a warning.
Can you please fix it?
In spite of warning, scrollableParent works as expected. Thanks for introducing it.

That sounds like a bug. Any chance you could file a PR to update the code? I'll assist you if you need help!

Here is a PR - https://github.com/brigade/react-waypoint/pull/59


Adds ProcessTask, with local and ssh linux backends

Codecov Report
Base: 79.72% // Head: 80.84% // Increases project coverage by +1.11% :tada:

Coverage data is based on head (26691b9) compared to base (62f88eb).
Patch coverage: 83.28% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##             main       #1      +/-   ##
==========================================
+ Coverage   79.72%   80.84%   +1.11%
==========================================
  Files           7        9       +2
  Lines        1406     1723     +317
==========================================
+ Hits         1121     1393     +272
- Misses        285      330      +45

Flag
Coverage Δ

unittests
80.84% <83.28%> (+1.11%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

pydatatask/repository.py
92.05% <58.33%> (-0.69%)
:arrow_down:

pydatatask/task.py
81.42% <80.29%> (+1.63%)
:arrow_up:

pydatatask/linux_manager.py
82.67% <82.67%> (ø)

pydatatask/resource_manager.py
96.49% <96.49%> (ø)

pydatatask/__init__.py
100.00% <100.00%> (ø)

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

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


Static typing

Resolves #54.

Hi tedmiston,
Can you pls help me I wanna use your spelling bee answer tool for the school website but I don't know anything about coding so can you pls tell me how can I use your code to run in my school website. Like some of these sbsolver.com/answers
sbhinter.com/spelling-bee-answer ?


A high MP sample image needed, using this lib❓

Question
Hello,
Searched on web but could not find anything useful, other than some factory samples
Can someone share a link of camera image, taken by this library, "without" pixel binning? I am particularly looking for Xiaomi 10-13 range outputs, but others also work well. I am looking to evaluate detail loss. Therefore, any image format with minimal loss is good for me.
-I am specifically looking for high MegaPixel camera outputs,
-40MP or higher. The higher the better.
-Jpeg or HEIF (or any other that preserves details well, as far as I understand, there is no RAW suppport yet)
Thanks for any help !
What I tried
n/a
VisionCamera Version
n/a
Additional information

[ ] I am using Expo
[X] I have read the Troubleshooting Guide
[X] I agree to follow this project's Code of Conduct
[X] I searched for similar questions in the issues page as well as in the discussions page and found none.

Closing as this is a stale issue - this might have been fixed with the full rewrite in VisionCamera V3 (🥳) - if not, please create a new issue.
If your issue has been fixed, consider sponsoring me on GitHub to say thanks 💖


Add LICENSE file

This project is licensed under the MIT license, but there's no LICENSE file in the repository 🤔
To close this issue:

Fork this repository
Add a new file called LICENSE and add the license text which you can find here, and commit
Make a Pull Request for this repository
Celebrate! 🎉  (And accept feedback on the PR!)

If you have any questions, comment below! ✌

Closed by #17


Update ParentNode interface

Fixes Microsoft/TypeScript#14246

closing for now. please reopen with updated files.


Add mailhog to SOE images

For catching mail:
https://github.com/mailhog/MailHog

Fixed in c0664f6307b5891359312a712a72115bc31c2a3f


Event name character limit too big and copying leads to Internal Server Error.

Describe the Bug
Definitely a bit of an edge case :)
After you have copied an event that has the reached the character limit, its possible to give the copy of the event an even longer name as the character limit has changed.
If you then change the event name to its 'new' character limit and copy it again you get an Internal Server Error ( see #3145 )
Steps to Reproduce
Event A = Original Event
Event B = Copy of Original

Create a new event (Event A) with the event name set to the character limit
Copy Event A
See that (copy) was added behind the name of Event B and no Internal Server Error
Edit Event B and set the length of the name to its character limit
See that the character limit has increased
Save Event B
Copy Event B
See an Internal Server Error

Expected Behavior
No Internal Server Error. The 'new' character limit should be less.
Actual Behavior
The character limit of the copy has increased by a lot. If that name is too long and then the event is copied it results in an Internal Server Error.
Additional Information
Version history of example in cms-test: https://cms-test.integreat-app.de/testumgebung/events/de/6917/versions/

Traceback

Tested successfully!


use debugpy directly for debugging python code

Any chance to use debugpy to debug directly instead of relying on nodejs?

It looks like its packaged in vscode-python but still in the experimental phase.
If you want to try it out I think you can update the command arguments in https://github.com/daveleroy/sublime_debugger/blob/master/modules/debugger/adapters/python.py
To something like
command = [
	'python3',
	f'{install_path}/extension/pythonFiles/lib/python/debugpy/wheels/debugpy/adapter',
]

It would be nice to stop using the node adapter since it is not compatible with the latest versions of node

Thanks, I confirm that it is working. Though it seems that debugOptions is now a list, so I have to do
		"debug.configurations":
		[
			{
				"name": "Python Debug",
				"type": "python",
				"request": "launch",
				"program": "${project_path}/main.py",
				"debugOptions" : []
			},
		]

This can now be enabled with the setting python.experimental_debugpy_adapter. debugpy is started with python3 which I don't think will work on Windows and it should be customizable.

debugpy is now the only supported python adapter since vscode-python has removed ptvsd


Investigate use of Mustache

In particular feasibility of using it with Graal native. Seems that it has very little dependencies but we need to make sure it compiles.

Experiment is here:
https://github.com/spericas/helidon-build-tools/tree/mustache
No problems compiling CLI using Mustache. There is some config required for reflection and resources (the templates themselves) but nothing too difficult. See,
https://github.com/spericas/helidon-build-tools/tree/mustache/helidon-cli/impl/src/main/resources/META-INF/native-image
The experiment modifies the init command to run a Mustache template borrowed from its repo. Totally unrelated to the task at hand, but simply to verify that it can be compiled and executed under Graal native.


Wait for CEC and CCEC resources before restoring endpoints.

Just like we are currently waiting for policy CRDs before generating endpoints for the first time after restoring them during an agent restart, it is also beneficial to wait for CEC and CCEC resources as well. This is mainly due to possible policy redirections to CEC/CCEC listeners, but also for the possibility of L7 LB service annotations, as well as east/west Ingress and Gateway API, which are implemented via CEC/CCEC resources.
In order to achieve this we first break up potentially blocking parts of daemon lifecycle start hook to run in a goroutine, so that the hive may run concurrently with the daemon bootstrap. This is necessary as start hooks are executed in the order in which they are appended to the hive lifecycle, and the next start hook can only run when the previous one has returned.
startDeamon() blocks waiting for a subset of k8s resources to have been synchronized, and as we add CEC and CCEC resources to that subset, we want to be able to use the hive lifecycle to start running the resource watchers for these resources. This becomes possible by making sure daemon start hooks do not block for this purpose. Similarly, any start hook that needs to await for the daemon promise needs to perform that Await call in a goroutine. This allows the hive to run all the needed start hooks while startDaemon() is waiting for the resources to have been synchronized.
This change also allows reverting the change in k8s policy watchers introduced in https://github.com/cilium/cilium/pull/32028, as now the hive is not stalled by the daemon waiting for the k8s resources to synchronize.
During testing there were spurious error and warning logs from the vendored k8s code when Cilium resources were requested before the corresponding CRDs had been registered. This is resolved by providing a new CRDSync promise to the hive, and then awaiting for that promise before requesting any Cilium resources. This eliminates the error and warning logs seen for CiliumNode, CiliumEnvoyConfig, and CIliumClusterwideEnvoyConfig resources. The CRDSync promise is optional so that it can be ignored for other than the agent hive.

Added missing sign-off to the revert commit.

/test

Changed to not use context from lifecycle OnStart hook in deamon promise await, as it will be canceled as soon as all the start hooks have executed, which may be before daemon promise becomes resolved.

/test

/test

I still feel a bit uneasy about the fact that go startDaemon() might cause lifecycle start hooks earlier than before.

That is kind of the whole point of this PR... and we already had the daemon promise for this purpose. Also I moved config related code up (including the code writing the config to a file), so that we can safely resolve the config promise while still working on startDaemon. Also, while the control of the daemon initialization changes from one goroutine to another, at all times there is only one goroutine doing it, until the daemon promise is resolved.

@gandro Moved resolving the PolicyManager promise to newDaemonPromise(), between newDaemon() and startDaemon(). It was previously directly injected from newDaemon(), now it is resolved a bit later, but still before startDaemon() blocks for k8s.CacheSynced.
Also added a new 1st commit to log an Error if BlockWaitGroupToSyncResources() is called too late.

/test

/test

What I dislike about this change is that it moves lots of initialization code to earlier than before, thus making it easier to accidentally accessing partially initialized state. There is for example absolutely no protection against code accidentally modifying DaemonConfig while the Daemon is still starting, except a source code comment saying "don't do it".

Added a controller to watch for option.Config changes and provide the diff in the error if there has been any changes.

/test

/test

fixed go lint

/test

Fixed comments, flipped the cmp.Diff arguments to get meaningful -/+ semantics.

/test

Rebased to address conflict with main and addressed comments by @dylandreimerink, thanks for the review!

/test

Noticed that option.Config.Opts pointer is not safe for changes, now taking a shallow copy for summing purposes instead. Opts pointer in the copy is safe to nil and does not need to be restored.
Issued #33164 for hardening option.Config.Opts use.

Fixed conflicts with main.

/test

Added use of the new CRD sync promise to clustermesh-apiserver on the first commit to avoid CI erroring on the new error log from the 3rd commit for clustermesh-apiserver.

/test

/test

/test

/test

Had to move k8s: Move CastInformerEvent to informer commit up front to resolve a circular dependency. Now CRDSync type can be in pkg/k8s/synced where it logically belongs, and it can be used from pkg/k8s as pkg/k8s/synced no longer imports pkg/k8s.

rebased for ci-e2e fix

/test

Thanks for the updates, taking the hash at this point in the codepath I think is crucial https://github.com/cilium/cilium/pull/32981/files#diff-8a383aefc352ba8854dbab293a563fecf7f8916983d013ab36f677293996ca3cR4012


Enable original package patching using swift package mirroring

As we discussed in swift-syntax, a top-level package dependency graph can be patched with:
swift package config set-mirror --original https://github.com/swiftlang/swift-syntax --mirror https://github.com/johnno1962/InstantSyntax

This can potentially ease swift-syntax replacement with its respective binary version.
The only caveat is that the repository of the mirrored package should contain all tags from the original repository for the SPM to resolve the overridden package.
Since then, the request from the Swift community for InstantSyntax has been to maintain all tags from the source package repository.
Thank you in advance.

"Just" maintaining tags for all those in the source repo isn't the only issue this repo faces. Versioning is a complex problem which Apple is much better situated to resolve give they have control of the related tooling. I'm afraid I won't be looking at this.

I don't know if all tags are necessary to recreate. Maybe major + or minor?
I’ve tried to replace the original swift-syntax with my fork of InstantSyntax using the package mirroring in the project that depends on The Composable Architecture and it seems that a wide range of versions is available to choose from.
Nonetheless, the compilation failed on switch covers known cases, but 'AccessorBlockSyntax.Accessors' may have additional unknown values.

I guess that the problem is caused by commenting out unsafe flags for weak frameworks to link.
let staticLink = ["\(clone)\(tag)/libSwiftSyntax.a"] +
    modules.map { $0.name }.flatMap({ module in
    ["-weak_framework", module] + platforms.flatMap({
        ["-F", "\(clone)\(tag)/\(module).xcframework/\($0)"] })
    })

(...)

    .target(
      name: "InstantSyntax"
//      linkerSettings: [.unsafeFlags(staticLink)]
    ),

I've did it get rid of package resolution error:
the target 'InstantSyntax' in product 'SwiftSyntaxMacros' contains unsafe build flags

which is (in my opinion) due to an overly restrictive SPM policy towards passing custom compilation flags.
@johnno1962 Have you been troubled with passing unsafe flags during InstantSyntax development?

@lyzkov were you able to resolve the unsafe build flag issue? It seems like the manual copying is meant to override this policy https://github.com/johnno1962/InstantSyntax/issues/3#issuecomment-1950221184 but it doesn't work for me.

@benedelstein Nope. Manual copying has nothing to do with this issue because third-party packages that depend on the InstantSyntax package are meant by SPM to restrict all unsafe flags.
If I remember correctly, only top-level 1st party packages can have unsafe flags specified. You would have to fork all dependencies to overwrite all unsafe flags, which is an unacceptable workaround with terrible maintenance tradeoffs.
I'd suggest waiting until the SPM guys resolve the swift-syntax prebuilt package distribution. Anyway, I hope they are not about to hack SPM's preexisting limitations through compiler flags.

I've updated he README to say this package no longer works. I've not seen it work with Xcode 16. I may archive the repo.

Seems Apple is working on a solution https://forums.swift.org/t/compilation-extremely-slow-since-macros-adoption/67921/124

@johnno1962 @lyzkov we have a solution at @PreternaturalAI. See swift-precompiled/swift-syntax.


Pass context to event publishing.

To allow tracing propagation via events, we need to pass the context
to the Publish function of reva events. This adds the context
everywhere where events are published. If there was no context to pass,
we started a new one with context.Background().

nothing seems to brake ... but I also cannot get a trace that shows eg that search has been triggered by an upload. But I assume that is caused by it not picking up the trace from the event, yet.

Exactly, this just adds the context, it doesn't do anything with it yet, as I was asked to keep the PR small. I want to start processing after the merge.


Update Readme Badges

@jsvigneshkanna
task: done 👍
star the repo: done 👍
Kindly if all is good if you can give me hacktoberfest-accepted label

noted 👍
Could you add the hacktoberfest-accepted label in the PR so it can count towards my contribution please

Apologies, missed the label


Move AncestryDNA uploads to oauth2 project

[x] Started repo at OpenHumans/oh-ancestrydna-source
[x] Export data validation/conversion logic into stand-alone oauth2 project
[x] Finalize integration to delete unprocessed file, etc.
[ ] Write copy for the project (is ftdna-specific right now)
[ ] Deploy external project
[x] Wrote management task in oh-23andme-source repo to import users from old legacy activity
[ ] shutdown legacy integration
[ ] Generate oauth2 tokens for existing legacy members
[ ] Alter foreign-keys of existing data files to stand-alone project and create the additional direct/private/whatever sharing objects in the main site backend
[ ] Import newly created tokens into stand-alone project
[ ] Activate new project on main site

This PR will do the data validation/conversion for AncestryDNA. I adapted all tests to the different file format and all tests pass the same way they do for 23andMe. The only thing missing at this point is integrating the Ancestry Logo along with the copy writing that needs to be adapted for Ancestry.

Both are now merged, I deployed the app at https://ohancestrydnasource.herokuapp.com/.
IMPORTANT NOTE: If you're an existing 23andMe integration user you don't have to upload your data again, we will merge this into a single application in the next steps!

And that migration is done too! 🎉


As a websocket consumer I need to set InitialSubscriptionPosition to earliest

Search before asking

[X] I searched in the issues and found nothing similar.

Motivation
As a websocket client, I need to subscribe to a persistent topic that has existing messages.
I need to consume all messages, starting from the first (earliest) one, and keep consuming messages as they become available.
Persistent subscription cursor is needed, hence the use of consumer api.
There is no parameter available for this setting shown in the documentation, or in the code that creates the subscription.
There is a similar setting messageId for the Reader endpoint.
But not for the Consumer endpoint.
Solution
Receive a new url parameter "initialSubscriptionPosition", and add the value to the consumer builder using the corresponding java api method.
Alternatives
Use the Reader endpoint: I would really prefer Pulsar to handle the cursor, instead of having to manage that state.
Anything else?
I would be open to implement this myself, if needed.
Thank you very much for your contributions!
Are you willing to submit a PR?

[X] I'm willing to submit a PR!

Makes sense to add support for initialSubscriptionPosition


report errors?

I love seeing things get deployed, etc. on the slack channel. Would be great if I could get error messages from the flux logs as well, to know when I've committed something wrong.

fluxcloud should be reporting any errors that flux reports to it. It’s not going to pick up everything from the flux log, but it will pick up manifest errors. If you’re not getting those are you on the latest version?

Yeah I do see manifest errors coming through. I don't remember the specific error for this, I had just assumed no errors were coming through at all.


Fix PascalVOC 2012 md5 sum (#2588)

Fixes issue #2588
EDIT: Fixes #2588

Seems like VOCdevkit/VOC2012/JPEGImages/2008_005714.jpg has changed between old archive and the new one. Rather strange...

Yup I'm not sure what happened, seemed like the change was made sometime this morning.


fix(engineimage): new status incompatible.

Modified the test case test_engine_image_incompatible by new introduced status field incompatible.
Ref: longhorn/longhorn#7683, longhorn/longhorn#7539

@mergify backport v1.6.x


Add message context to Committers

Before it was not possible to add custom committers or custom committer configuration to the consumer, so here is a proposal to add support.
Creating the committers in the consume method instead of injecting via the constructor of Consumer makes sense because in some cases you want the RdKafka\KafkaConsumer object in the committer. Like the KafkaCommitter that was present already, and the SeekToCurrentErrorCommitter also needs it.
Hence the extraction of a CommitterFactory interface and renaming the CommitterFactory class to DefaultCommitterFactory.
I've also added the SeekToCurrentErrorCommitter, for which I started these changes in the first place. You can use this committer when you need to do in-order processing of messages while blocking the entire stream consumption when one of the messages cannot be processed.
The unsubscribe/subscribe implementation is somewhat hacky. But safe, even with multiple clients in the same consumer group, and across partitions, but probably not very efficient in a setup with multiple clients as this will yield a rebalancing.
I intended all changes in this PR to be fully backwards compatible. Lucky the committers were implicitly private to this library before, because there was no way to set the on the Consumer.

Thank you @rtuin!


Error: dns service error: name conflict

Hm whats wrong with the avahi-deamon or the node-red-contrib-homekit node?
Is it a node-red bug or a homekit error im not sure where is the problem.
Can anyone help me? Reinstall/reboot did not help.
On Deploy with node-red-contrib-homekit nodes in the flow  gives me this error:
6 Oct 14:53:51 - Error: dns service error: name conflict
    at Error (native)
    at new Advertisement (/root/node-red/node_modules/mdns/lib/advertisement.js:56:10)
    at Object.create [as createAdvertisement] (/root/node-red/node_modules/mdns/lib/advertisement.js:64:10)
    at Advertiser.startAdvertising (/root/node-red/node_modules/hap-nodejs/lib/Advertiser.js:43:30)
    at Accessory._onListening (/root/node-red/node_modules/hap-nodejs/lib/Accessory.js:611:20)
    at emitOne (events.js:96:13)
    at HAPServer.emit (events.js:188:7)
    at HAPServer._onListening (/root/node-red/node_modules/hap-nodejs/lib/HAPServer.js:190:8)
    at emitOne (events.js:96:13)
    at EventedHTTPServer.emit (events.js:188:7)

Hi,
thanks for raising an issue.
This is not an issue with the core of node-red, so this issue tracker isn't the best place to seek help.
If you check out our contribution guidelines you'll see we prefer to handle this sort of thing on the mailing list, slack team or you could ask a question on Stack Overflow and tag it node-red. That way the whole Node-RED user community can help, rather than rely on the core development team.
As the error appears related to the node-red-contrib-homekit node, you could also direct your question to its maintainers - https://github.com/mschm/node-red-contrib-homekit
Thanks!

Oh okay sorry!

Closing as not a core issue


Getting LIFECYCLE error when running tests with coverage

Not sure if this is a bug yet, so forgoing bug template till I get some feedback.
I am getting random LIFECYCLE errors when running tests via react-scripts in coverage mode
Here is the error:
/node_modules/react-scripts/scripts/test.js:22
  throw err;
  ^
[object Object]
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>test:coverage: `react-scripts test --env=jsdom --coverage`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>test:coverage script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR!      /Users/adamduro/.npm/_logs/2017-08-06T05_24_47_697Z-debug.log

It fails on a random test (not the same one each time).
I rebooted my machine, got one clean test run in, and then subsequent runs of this command begin failing everytime (just on different tests each time).
I do not have jest installed globally.
I am on react-scripts v1.0.10
I am using node v8.2.1 (npm v5.3.0)
The only additional info is that I upgraded eslint to v4.3.0 outside of react-scripts, which does throw some peer-deps warnings, but so far has been working without any error.
If it's helpful, here is my complete package.json
{
  "name": "portal2",
  "version": "0.1.0",
  "private": true,
  "dependencies": {
    "debug": "^2.6.8",
    "es6-promise": "^4.1.1",
    "http-status-codes": "^1.2.0",
    "immutable": "^3.8.1",
    "isomorphic-fetch": "^2.2.1",
    "lodash": "^4.17.4",
    "prop-types": "^15.5.10",
    "react": "^15.6.1",
    "react-dom": "^15.6.1",
    "react-redux": "^5.0.5",
    "react-router-dom": "^4.1.2",
    "react-scripts": "1.0.10",
    "redux": "^3.7.2",
    "redux-form": "^7.0.3",
    "redux-logger": "^3.0.6",
    "redux-pack": "^0.1.5",
    "styled-components": "^2.1.1"
  },
  "scripts": {
    "precommit": "lint-staged",
    "start": "react-scripts start",
    "build": "react-scripts build",
    "test": "react-scripts test --env=jsdom",
    "test:coverage": "react-scripts test --env=jsdom --coverage",
    "eject": "react-scripts eject",
    "storybook": "start-storybook -p 6006",
    "build-storybook": "build-storybook",
    "generate:generator": "yo ./generator/generator",
    "generate:component": "yo ./generator/component",
    "generate:view": "yo ./generator/view",
    "generate:duck": "yo ./generator/duck"
  },
  "devDependencies": {
    "@storybook/cli": "^3.2.3",
    "@storybook/react": "^3.2.3",
    "babel-eslint": "^7.2.3",
    "ejs-lint": "^0.3.0",
    "enzyme": "^2.9.1",
    "eslint": "^4.3.0",
    "eslint-config-prettier": "^2.3.0",
    "eslint-config-walmart": "git+https://github.com/walmartlabs/eslint-config-walmart.git",
    "eslint-plugin-filenames": "^1.2.0",
    "husky": "^0.14.3",
    "lint-staged": "^4.0.2",
    "nock": "^9.0.14",
    "prettier": "^1.5.3",
    "prettier-eslint-cli": "^4.1.1",
    "react-test-renderer": "^15.6.1",
    "yeoman-generator": "^1.1.1",
    "yo": "^2.0.0"
  },
  "lint-staged": {
    "src/**/*.js": [
      "prettier-eslint --write \"src/**/*.js\" \"stories/**/*.js\" \".storybook/**/*.js\"",
      "git add"
    ]
  },
  "jest": {
    "collectCoverageFrom": [
      "src/**/*.{js,jsx}",
      "!<rootDir>/node_modules/",
      "!src/index.js",
      "!src/registerServiceWorker.js",
      "!src/**/story.js"
    ]
  }
}

I'm pretty sure this is my issue. I've isolated it to running tests on a certain part of my app. Seems I have some kind of unhandled exception.


Allow Transport Layer Security to be configured in the UI definition

This PR allows for Transport Layer Security to be configured for Elasticsearch and Kibana through the Azure Markerplace UI definition. All inputs are optional.
Elasticsearch
HTTP layer
A user can choose between supplying a PKCS#12 archive

containing the certificates and private key with which to secure all nodes within the cluster
This would be the typical option where a CNAME is configured for the Elasticsearch external load balancer IP/FDQN, and the certificate supplied corresponds to the CNAME.

or

containing a Certificate Authority (CA) certificate and private key with which to generate a certificate for each node within the cluster for the HTTP layer

Transport layer
A user can supply a PKCS#12 archive containing a Certificate Authority (CA) certificate and private key with which to generate a certificate for each node within the cluster for the Transport layer.
Kibana
A user can supply a PEM certificate and private key with which to secure communication between the browser and Kibana.

should be merged after #281 is merged.
npm run links -- --branch 7.1

should also be run before merging


New resharing concept breaks testsuite

Describe the bug
With the new reshare concept some tests are failing. We need to discuss how we can adjust them (or if the reshare concept is faulty)
See https://github.com/cs3org/reva/pull/2877
Steps to reproduce
With reva from https://github.com/cs3org/reva/pull/2877 and master ocis run test mentioned in list
Expected behavior
The test should pass
Actual behavior
The tests fail
List
Additional context
Add any other context about the problem here.

@phil-davis @individual-it we need to work together on this. The main problem is that the bitmask for the permissions has 31 as a representation for all permissions which is not true anymore.

@phil-davis @micbar @individual-it sorry this ticket is not ready yet. I'm still trying to figure out which tests need to be fixed. So nothing to do atm. Sorry for confusion

Update: reva seems fine with the changes, we have just some spaces ocis test failing. They are explicitly testing that resharing does not work. So these need to be changed. See list of failing tests in ocis PR:
https://github.com/owncloud/ocis/pull/3804/files#diff-733a682a252e8a35d985692d58d7b793107aa0abe81eac800edd774e3415fc07R26-R34

@kobergj thanks!
I am fine with adding these tests to the expected failures now.
@ScharfViktor Can then evaulate changes to the gherkin steps later.

Yes, sure. I'll do it

Just small info: Web is already working on sending roles instead of int permissions. @fschade is that already merged?

@individual-it @phil-davis
We found an issue with the reva test suite. You can see it in apiShareReshareToShares3/reShareUpdate.feature:153 for example.
We think the problematic test line is:
And user "Alice" has updated the last share of "Alice" with
The last share will send a request for the wrong share (here 4 instead of the correct 3)
It is probably related to int ids of reva, as the test works correct against ocis (which is using uuids)
For now this not blocking us, as tests get green anyways, but I have no clue how many other tests are affected.
cc @fschade @micbar

Note: I am working on issue https://github.com/owncloud/core/issues/40093 in PR https://github.com/owncloud/core/pull/40095 - that aims to make all those "somebody does something related to the last share" steps work regardless of the format of share-ids. The test code will remember more of the shares that it created in a scenario, and will avoid ever having to do a "general API query" to discover the shares that exist - no more making a "partly-educated guess" about what "the last share" refers to.

core PR https://github.com/owncloud/core/pull/40114 is in review. Hopefully it all passes and can be merged overnight. Then I will bump the core-commit-id in reva and oCIS. That should help with test steps about "the last share"

Done


Clear viztmp file even if there's something wrong with trace report saving

Currently viztmp file is not guaranteed to be cleared if something goes wrong during report saving. We should make sure the cleanup executes even with some exceptions.

Closed by #403


Change github url to use http

When cloning the repo I got this error:
$ git clone git@github.com:hoodiehq/hoodie-app-something-tracker.git
Klone nach 'hoodie-app-something-tracker' ...
Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

Changing the github url to https://github.com/hoodiehq/hoodie-app-something-tracker.git fixed this.

can you clone other repos from github? Can you try this?
$ git clone git@github.com:github/hub.git

I think your github ssh key might be borked?

Thanks, you were right.

GitHub removed my SSH keys I were using, I've readded them and now it works with the SSH url.


python312Packages.pdm-backend: 2.3.3 -> 2.4.2

Resolves #350523

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] 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/)
24.11 Release Notes (or backporting 23.11 and 24.05 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.

Add a :+1: reaction to pull requests you find important.

2.4.1 on staging-next. And there won't be another python-updates cycle before branch-off.


add to declaration/id response

Add field to get declaration by id in Cabinet, according to Design
https://api.dev.asclepius.com.ua/api/cabinet/declarations/{id}

data.person.gender

my next task
add

data.person.birth_country


Can't Subscribe to a Private Channel on Web, Cookie Mismatch

Hello,
I'm trying to get this to work with a Laravel backend (Flutter Web) on a private channel which is uses a cookie in the backend to maintain authentication. When I just tried to point authEndpoint to the correct URL to validate that the user has access to a given channel my backend returns a 401 because the cookie being provided doesn't match the correct cookie. This leads me to the conclusion that Pusher is using some sort of separate HTTP client under the hood that is maintaining its own session state.
I have tried everything I can think of to override the HTTP request here, so I can inject my own request to make sure the cookie values are properly managed and I can't do it.
Is there any way to override the default behavior for the client when requesting authorization?

To add to this..
Trying to get past this bug I decided it made sense anyway for me to provide a way to authenticate API requests (and thus private channels) using a simple Authorization header. I've implemented that solution and I attempted to get it working with this code base with no success:
        await client.init(
            apiKey: _apiKey,
            cluster: _apiCluster,
            onConnectionStateChange: _onConnectionStateChange,
            onError: _onError,
            logToConsole: logToConsole,
            onSubscriptionSucceeded: _onSubscriptionSucceeded,
            onEvent: _onEvent,
            onSubscriptionError: _onSubscriptionError,
            onDecryptionFailure: _onDecryptionFailure,
            onMemberAdded: _onMemberAdded,
            onMemberRemoved: _onMemberRemoved,
            authEndpoint: authEndpoint,
            authParams: {
                'params' : {},
                'headers': {
                    'Authorization' : 'Bearer ' + _currentUser.api_token
                }
            },
            onSubscriptionCount: _onSubscriptionCount,
        );

When this code is executed I get an exception:
Error: PlatformException(error, Expected a value of type 'AuthOptions', but got one of type
'LinkedMap<Object?, Object?>', null, null)
dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/errors.dart 294:49  throw_
packages/flutter/src/services/message_codecs.dart 652:7                       decodeEnvelope
packages/flutter/src/services/platform_channel.dart 310:18                    _invokeMethod
dart-sdk/lib/_internal/js_dev_runtime/patch/async_patch.dart 45:50            <fn>
dart-sdk/lib/async/zone.dart 1661:54                                          runUnary
dart-sdk/lib/async/future_impl.dart 156:18                                    handleValue
dart-sdk/lib/async/future_impl.dart 840:44                                    handleValueCallback
dart-sdk/lib/async/future_impl.dart 869:13                                    _propagateToListeners
dart-sdk/lib/async/future_impl.dart 641:5                                     [_completeWithValue]
dart-sdk/lib/async/future_impl.dart 715:7                                     callback
dart-sdk/lib/async/schedule_microtask.dart 40:11                              _microtaskLoop
dart-sdk/lib/async/schedule_microtask.dart 49:5                               _startMicrotaskLoop
dart-sdk/lib/_internal/js_dev_runtime/patch/async_patch.dart 181:15           <fn>

Further, I have also attempted to use onAuthorizer (both with and without authEndpoint) to build my own authorization request and provide the response. As far as I can tell, I have seen no evidence this method is called under any circumstances.
Unless I am missing something really obvious, it seems that this package is broken entirely for private channels. Please help!

I'm not entirely certain why you are encountering the Expected a value of type 'AuthOptions error, but to achieve what you are looking for you need to use onAuthorizer (without the authEndpoint param defined) so I think it makes sense to troubleshoot this setup.
Can you share the implementation of this approach?

Closing as we haven't had a response here.
If you need more support please get in touch at https://messagebird.com/support-center/Pusher-request-new

Closing as we haven't had a response here.
If you need more support please get in touch at https://messagebird.com/support-center/Pusher-request-new


[NET_BUFFER] A lot of members do not have details

The members of struct NET_BUFFER such as Next, CurrentMdl, etc., lack explanations.

文档详细信息
⚠ 请勿编辑此部分。 docs.microsoft.com ➟ GitHub 问题链接必须具有此部分。

ID: c4439666-d0cb-01e2-985b-e994b2b2d16c
Version Independent ID: dd99a34b-1156-605c-1bff-5f265a0217d3
Content: _NET_BUFFER (ndis.h) - Windows drivers
Content Source: wdk-ddi-src/content/ndis/ns-ndis-_net_buffer.md
Product: windows-hardware
Technology: windows-devices
GitHub Login: @duncanmacmichael
Microsoft Alias: dumacmic

Hi @xiaoyinl, thanks for finding this. It looks like the NET_BUFFER structure got updated in a recent release to include the members of the NET_BUFFER_DATA structure in the NET_BUFFER itself, but those changes slipped by us. I've updated the member descriptions and have published the changes for the English version of the page; they should also be live for the Chinese version as soon as our localization team does another sweep over the content soon.
Thanks!


How to extend map using another point cloud rosbag?

Hi, just wonder how to extend my map if I have already generated a map and I want extend it?

Hi @jinfagang ,
This package itself does not provide a capability to extend an existing map. I think you need to merge maps generated separately using, for instance, ICP matching.


Fix dbmirror2 replication init, function search_path  (fixes #6)

add dbmirror2 schema
init replication
explicitly set search_path on function creation

These changes seem to have fixed the problem for me.

Are there any updates on getting this PR merged? Would love to see syncing functionality functional.