API changes for statements and final comments

Describe your changes

chore(packages/appeals): split FINAL_COMMENT type into 2 subtypes
There will be LPA final comments and appellant final comments.
feat(api): split final comments code into the 2 subtypes
chore(api): change FINAL_COMMENT type to correct subtype in seed script
feat(packages/appeals): add INCOMPLETE representation type
feat(api): only allow LPA statements to be set to the incomplete status

Issue ticket number and link
A2-1772
Type of change 🧩

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation update
[ ] Other (please explain in the description section above)

Checklist before requesting a review

[x] I have performed a self-review of my own code
[x] I have double checked this work does not include any hardcoded secrets or passwords
[ ] I have made corresponding changes to the documentation
[ ] I have provided details on how I have tested my code
[x] I have referenced the ticket number above
[x] I have provided a description of the ticket
[ ] I have included unit tests to cover any testable code changes

It's a bit of rework I know but how would you feel about having one get endpoint for all reps that optionally takes a query param for type? It already accepts pagination vars and status so it's not that big of a step and would increase code reuse

I was initially thinking the same, but I noticed that for this endpoint the behaviour and response is quite different. I'm just a bit concerned that these new endpoints will also end up sufficiently different from each other that a single endpoint would end up overloaded with parameters, and/or we'd end up splitting it back out into multiple endpoints.
What do you think?

Nice! I should have said I did a lil PR for this yesterday in case we did want to pivot to one endpoint but you've done more clean up so let's goo with this PR. Only thing I'd ask for is I'd set up the repository to accept multiple types, could we get that behaviour in here? Hopefully you can pilfer it https://github.com/Planning-Inspectorate/appeals-back-office/pull/722/files.
Also I wasn't sure what the behaviour should be if no type was given. I went with giving all reps but maybe it should be none?

https://github.com/Planning-Inspectorate/appeals-back-office/pull/722/files

👍 That's set up now.
I think returning all types if no types are specified is the best approach. So the query string allows you to query an otherwise unfiltered set of results.


Issue2681: Multiple imports of same module

Module declarations never instantiate when multiple imports point to the same module. Root cause is that the counter for uninitialized child modules is incremented even if the child module has been parsed, in which case the counter can never go back to zero, therefore never triggers instantiation. Fix by checking if a child module has been parse(vs. instantiated).

Addresses https://github.com/Microsoft/ChakraCore/issues/2702

@boingoing @akroshg @Yongqu @Microsoft/chakra-es review pls?

Is this the case where a child module has been parsed already because it was already included as a child of a previous root module? Or because the same module record can be returned from the host via different module specifiers?

There was only one root module, but import clauses in different source files share the same specifier. Take the updated unit test:
moduletest1.js > passmodule.js > exportmodule.js > passmodule.js (2nd encounter, resolved, parsed but not instantiated)
The counter for exportmodule is incremented to 1 for passmodule but will never go to 0.

In reply to: 287507214 [](ancestors = 287507214)

Sounds reasonable. This can only happen in the cyclical case, then?

@suwc what about the cases where another module throws error? do we still parse rest of the imports?

No, this happens in non-cyclic cases too, e.g. in the github issue we are trying to address:
script.js > mod0 > mod1b
> mod1a > mod1b (2nd encounter)

In reply to: 287508635 [](ancestors = 287508635)

In this case module resolution happens before byteCodeGen, therefore only early error will be seen.

In reply to: 287509096 [](ancestors = 287509096)

@boingoing @akroshg @Yongqu could you take a look at the new iteration please?

@dotnet-bot
test Ubuntu static_ubuntu_linux_test


Keyboard navigation is out-of-sync from viewstate

Describe the bug
A clear and concise description of what the bug is.
when opening a folder in the tree using the right-arrow, and then move down, the focus is on the item after the tree item, IF the 'items' of the tree are the same. when the items change as well (for instance items keeping track of expand state as well) then it works fine.
To Reproduce
Steps to reproduce the behavior:

visit: https://rct.lukasbach.com/docs/guides/controlled-environment/#managing-the-view-state-of-the-tree
Click 'Desserts' (it should expand immediately)
Press arrow down (focus becomes "Drinks")

Expected behavior
A clear and concise description of what you expected to happen.

visit: https://rct.lukasbach.com/docs/guides/controlled-environment/#managing-the-view-state-of-the-tree
Click 'Desserts' (it should expand immediately)
Press arrow down (focus should become "Cookies")

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

OS: MacOS
Browser: Chrome
Version: 102

Additional context
Add any other context about the problem here.
I could fix this behaviour in my own application by updating the object reference of items whenever the expanded view state changed. I suspect there the keyboard navigation is somehow using an out of date 'linear list' because it only updates when the 'items' change, and not when the 'expandedItems' state changes.

Hmm that Particular issue is fixed, but now a new issue has risen. when I click in the tree and start keyboard navigation I get index errors.
1.1.6

with 1.1.7

Hm, that is odd, I'm not getting that in any of the storybook instances. Do you have your project deployed anywhere where it would be possible to reproduce this issue?

Go to https://geppetto.js.org/app/
Check if version commit is 5a005c.
Press 'Load Demo File'
On the top, Press "Composition"
In the tree to the left, press "Saturation (2)"
Try keyboard navigation

Thanks, that really was helpful in debugging, I believe I found the issue now. Please try again with RCT version 1.1.8, I hope this time there are no other problems 😅 Let me know if you have any other issues, and btw your project looks awesome! :)

It works perfectly now! Thank you! (will update the online build later)


valid_email2 is not validating the emails correctly

I tried to validate emails using valid_email2 gem (without ActiveModel) but i noticed there is something that needs to improve.
Look at following examples (Especially email address)
1-
 > email
   =><EMAIL_ADDRESS> > ValidEmail2::Address.new(email).valid?
   => true

Why?

2-
 > email
   => "jacoblarsonband@yahoo.comfargoasfsn123!"
 > ValidEmail2::Address.new(email).valid?
   => true

Why it's saying valid email?

and also for email =<EMAIL_ADDRESS>any suggestion will be appreciated. Thanks

I've release v2.1.0 to rubygems with the fix. Thanks!


ABORT_INVALIDARGNOTATOM for seeing/1

Following code will cause ABORT_INVALIDARGNOTATOM error:
:- initialization(main).

main :- seeing(S), write(S), nl, halt.

GProlog, SWI and Yap will write user to output.

Fix confirmed, thanks.


OpenRPC: tRPC, ts-rest, zodios alternative now support vue query

Seem this dead, so I think good if give dev more choices
https://github.com/unnoq/orpc

Hi @unnoq ... I'm not sure it is up to you to decide if something is dead or not, but this is incredibly disrespectful to do this to promote your own library/libraries.
Whilst I don't doubt your library is good, or perhaps better, please do not do this in future to mine, or others, libraries.
Perhaps, instead offer support for maintenance, or offer feature suggestions or improvements.
Thank you.

@unnoq No worries at all, apology accepted. And thank you for closing. My advise in future: reach out to me in person. I am human.
I will follow your library as it looks very interesting.


fix(client): LanguageList export

Checklist:

[x] I have read and followed the contribution guidelines.
[x] I have read and followed the how to open a pull request guide.
[x] My pull request targets the main branch of freeCodeCamp.
[x] I have tested these changes either locally on my machine, or GitPod.

Closes #50266

Thank you 💚

lgtm


Creating the viewer requires the DOM element to already exist in the page.

Hi.
I'm taking the Single Resolution Cube demo as a starting point.
And I noticed something.
Creating a DOM element on the fly and appending it to the Document works just fine.
// Create element
var element = $('
')[0];

// Append element to document
document.body.appendChild(element);

// Single Resolution Cube Demo Code
var viewer = new Marzipano.Viewer(element);
var source = Marzipano.ImageUrlSource.fromString("http://www.marzipano.net/media/cubemap/{f}.jpg");
...

But if I try to do the same into a fragment nothing happens, not even an error.
// Create element
var element = $('
')[0];

// Single Resolution Cube Demo Code
var viewer = new Marzipano.Viewer(element);
var source = Marzipano.ImageUrlSource.fromString("http://www.marzipano.net/media/cubemap/{f}.jpg");
var geometry = new Marzipano.CubeGeometry([{ tileSize: 1024, size: 1024 }]);
var limiter = Marzipano.RectilinearView.limit.traditional(4096, 100*Math.PI/180);
var view = new Marzipano.RectilinearView(null, limiter);

viewer.createScene({ source: source, geometry: geometry, view: view, pinFirstLevel: true }).switchTo();

// Append element to document
document.body.appendChild(element);

Is there a way to "render" to a fragment first and later append to the document?

The "issue" is here:
https://github.com/google/marzipano/blob/master/src/stages/Stage.js#L159
Stage.prototype.updateSize = function() {
  this._width = this._domElement.parentElement.clientWidth;
  this._height = this._domElement.parentElement.clientHeight;

  this._updateSize(); // defined by subclasses

  this.emit('resize');
  this.emitRenderInvalid();
};

clientWidth and clientHeight always return 0 until they are part of a document.
I wonder if there's any way to circumvent this.

Unfortunately, there's no API to set the stage size. I believe this is an oversight; it would be nice to support the off-page rendering case.
I think Stage#updateSize should take an explicit width and height as arguments, and Stage#updateSize should be the one reading the size from the DOM and passing it along. This way, regular clients wouldn't be forced to set the size explicitly, but your use case would be possible by instantiating the stage directly.
Pull request #36 gives the general idea. It's not ready to be merged yet - I need to fix some of the demos and test it more thoroughly.

Thank you very much,
Came up with a similar solution, but I prefer yours and I'll incorporate it until Pull request #36 is ready.
Thanks for the help :)


No Courses Found

whenever i search for any course, it shows no courses found. Help needed!

Are you enrolled in any courses?
The logged in user must be enrolled in a Udemy course!

Are you enrolled in any courses?
The logged in user must be enrolled in a Udemy course!

Yes i did. Still not working at All.

You searched for python, the title of this course does not contain that word


Improve heuristic for --openssl-legacy-provider (#2155)

Improve the heuristic for detecting whether we need --openssl-legacy-provider added in #2116 by also checking whether the Node.js was actually built against OpenSSL 3 and has that option available.
Fixes #2155.

This is a very nice solution! I'm afk at the moment, but can I trust that you've tested this for versions that require and don't require the flag? Happy to merge if so.

Yup, tested with the repo in linked issue on both native Node (built with 1.1.1m) and Node as installed by fnm (built with OpenSSL 3.0.1+quic).

Thanks again for this PR! We'll do a release soon.


Testing Redux-form

React Boilerplate
Before opening a new issue, please take a moment to review our community guidelines to make the contribution process easy and effective for everyone involved.
Please direct redux-saga related questions to stack overflow:
http://stackoverflow.com/questions/tagged/redux-saga
For questions related to the boilerplate itself, you can also find answers on our gitter chat:
https://gitter.im/mxstbr/react-boilerplate
Before opening a new issue, you may find an answer in already closed issues:
https://github.com/react-boilerplate/react-boilerplate/issues?q=is%3Aissue+is%3Aclosed
Issue Type

[ ] Bug (https://github.com/react-boilerplate/react-boilerplate/blob/master/.github/CONTRIBUTING.md#bug-reports)
[ ] Feature (https://github.com/react-boilerplate/react-boilerplate/blob/master/.github/CONTRIBUTING.md#feature-requests)

Description
(Add images if possible)
Redux-form Test fails with error message :
nvariant Violation: Could not find "store" in either the context or props of "Connect(Form(WizardFormPage))"
shallowWrapper::dive() can not be called on DOM componentshallowWrapper::dive() can not be called on DOM components
Steps to reproduce
//index.tst.js
import { shallow, mount } from 'enzyme';
import React from 'react';
import {store} from '../../../containers/app'
// import { IntlProvider } from 'react-intl';
import data from '../../../containers/App/data.json';
import WizardFormPage from '../WizardFormPage';
import WizardForm from '../index';
describe('', () => {
it('should render WizardFormPage firstpage', () => {
let subject = null
let submitting, touched, error, reset, onSave, onSaveResponse, handleSubmit
beforeEach(() => {
submitting = false
touched = false
error = null
reset = sinon.spy()
onSaveResponse = Promise.resolve()
handleSubmit = fn => fn
})
const props = {
onSave,
submitting: submitting,
// The real redux form has many properties for each field,
// including onChange and onBlur handlers. We only need to provide
// the ones that will change the rendered output.
fields: {
A01: {
value: '',
touched: touched,
error: error
}
},
handleSubmit,
reset
}
// const firstQuestion = {
//   id: 'A01',
//   next: 'A02',
//   reply: '',
//   text: 'What happened to your product?',
//   type: 'string',
// }
const html =
<ReduxForm page="0" question={{"id": "A01", "next": "A02", "reply": "", "text": "What happened to your product?", "type": "string"}} />

const text = "What happened to your product?"
const nextPage = () => {}
// const renderedComponent = shallow(
//
// ).dive();
const renderedComponent2 = shallow(
<WizardFormPage {...props} store={store} page="0" onSubmit={jest.fn()} nextPage={jest.fn()} question={data.questions[0]} />
).dive();
expect(renderedComponent2.html()).toEqual(html);
// expect(renderedComponent.contains(
//
// )).toEqual(true);
});
// it('should render an error if loading failed', () => {
//   const renderedComponent = mount(
//
//       <WizardForm
//         loading={false}
//         error={{ message: 'Loading failed!' }}
//       />
//
//   );
//   expect(renderedComponent.text()).toMatch(/Something went wrong/);
// });
// it('should render the repositories if loading was successful', () => {
//   const repos = [{
//     owner: {
//       login: 'mxstbr',
//     },
//     html_url: 'https://github.com/react-boilerplate/react-boilerplate',
//     name: 'react-boilerplate',
//     open_issues_count: 20,
//     full_name: 'react-boilerplate/react-boilerplate',
//   }];
//   const renderedComponent = shallow(
//     <WizardForm
//       repos={repos}
//       error={false}
//     />
//   );
//
//   expect(renderedComponent.contains()).toEqual(true);
// });
it('should not render anything if nothing is provided', () => {
const renderedComponent = shallow(

);
expect(renderedComponent.html()).toEqual("

");

});
});
Help appreciated!
(Add link to a demo on https://jsfiddle.net or similar if possible)
Versions

React-Boilerplate (see package.json):
Node/NPM:
Browser:

Sorry mate but this isn't a support forum. Only issues directly related to react-boilerplate are allowed here. Check out Stack Overflow or other sites for your need.

PS: Also, make sure you place your code in triple backticks and indent next time. It's unreadable as is.


What is the status of this project and other forks?

If I understand correctly, Pystache started with https://github.com/defunkt/pystache. This repo claims to be the fork of it, but so does https://github.com/PennyDreadfulMTG/pystache. At the same time, the PyPI version release date doesn't match either your or @PennyDreadfulMTG's release dates on GitHub.
As such, I have the following questions:

Is the source of the PyPI this repository? If yes, why don't you tell others to download pystache from PyPI, but rather from GitHub's releases page?
Who controls pystache on PyPI? If it's you, why isn't the PyPI package linked here?
If you don't control the pystache package, could you reupload it to PyPI under a different name? Alternatively, could you ask @defunkt (or I guess it's @bakert) for the rights to continue publishing improvements under the old name?

@bakert @defunkt if you don't maintain your versions of pystache any more, could you please specify the current maintainer in the README and archive the repos?

The PyPi version is now https://github.com/PennyDreadfulMTG/pystache
All of @sarnold's improvements have been incorporated there.

The PyPi version is now https://github.com/PennyDreadfulMTG/pystache

But it doesn't get published to PyPI, does it? The latest version on PyPI is 0.6.0. The latest GitHub release is 0.6.1. The latest Change log entry is 0.6.2.
I can see that publish step is disabled:
https://github.com/PennyDreadfulMTG/pystache/blob/748b359a147111febbe188020dabab63862099d5/.github/workflows/release.yml#L107
Is there a reason for that?
The thing is, one can't depend on a non-PyPI package if one wants to get their package published to PyPI. That means, that any improvements you make to the parser are unavailable to those who use it as a dependency.

@kytta Thanks for your feedback. Although I'm 7 months late I've fixed this and now the repo, github releases and pypi all agree that 0.6.4 is our latest release.

@kytta Thanks for your feedback. Although I'm 7 months late I've fixed this and now the repo, github releases and pypi all agree that 0.6.4 is our latest release.

It's never too late :) Thanks a lot!


Upgrade to argonaut codecs 7

Hi, I saw that there will be a version upgrade soon in argonaut codecs.
This is a WIP PR. Just putting it here for initial opinions. :) I am not sure if it is "safe" to merge since v7 is not yet in the official package-sets

@seanyu4296 thanks for fixing this

Is this good to merge @BebeSparkelSparkel or do you have any comments?

@seanyu4296 Looks exactly like what I did, so I think it is good to go.

v7 is in the package sets now.

I've been away from PureScript world for a while - can you confirm what you need me to do here? Bump the version and publish to bower?

@seanyu4296 do you think this is a major version bump? Kind of hard to tell.

Yeah I'm not sure myself too based from the libraries that were updated https://github.com/purescript/package-sets/pull/651 some did a major version bump, but some did a patch version bump.
@BebeSparkelSparkel

hmmm i'm not sure if one can still push updates to bower i haven't tried, but i think the community is leaning now to this approach https://github.com/purescript/package-sets/blob/master/CONTRIBUTING.md using spago @jmackie

or listed in the new-packages in the registry repo. https://github.com/purescript/registry/blob/master/new-packages.json

I just created a PR to convert to foreign-generic without seeing this PR, are people still using argonaut, I thought foreign-generic was "the standard" in purescript these days?


When a job with retry set to 0 gets dequeued, it should be removed.

We are sure the job will never be requeued again, since it is against the retry parameter set to 0, meaning the user requested the at most once semantics. Waiting for an ACK for this job is probably silly, we should just remove the job as soon as we transmit it to the client.

By removing the job after it's been transmitted, we lose access to the job's metadata from SHOW <job-id>. For example, GETJOB does not return ctime which is needed to determine the age of a job.

@justincase yep that's true... we miss the ability to inspect the job in the Disque side, but then if it's a fire and forget job... do we really want to retain this information? Or fire and forget jobs will likely have a short TTL so this is acceptable? Or maybe we should retain those jobs, but evict them in freeMemoryIfNeeded() like ACKs when we are short on memory? The last one sounds sensible, so if there is free memory, we use it to retain more state.
About GETJOB not returning those info, there is the idea to augment GETJOB with more options so that you can get a number of information about a job, including ctime, the count of retries and NACKs (when available), and so forth. So this is going to be solved in a direct way... :-)

I like the idea of GETJOB optionally returning the job's metadata. That way the job itself can be discarded right away without the need to retain anything.

Quick update on the issue. So currently best solution apparently is:

If memory warning is > 0 (75% of more used), discard at-most-once delivery jobs ASAP when they are returned by GETJOB.
Once there is to evict data in freeMemoryIfNeed() we discard those jobs to reclaim memory.
However I would also add an option to discard at-moce-once jobs ASAP in all the cases for people that don't care much about observability of that jobs and want a more vanilla memory behavior. This would go in the advanced section of disque.conf anyway.

In the above discussion there is an important missing part, which is, if we discard the job having retry set to 0, and the client acknowledges it anyway, currently what happens is that the node receiving the ACKJOB of a job it does not know, will create a dummy ack. It cannot know the ack is about a job with retry set to 0. This will trigger a cluster-wide GC attempt.
So there are a few solutions:

Retain the jobs and only evict them on critical memory issues in freeMemoryIfNeeded().
Put in some way the retry policy inside the job ID, so that receiving nodes know about the fact there is no need to create a dummy ack.
It's a bit of a shame that retry 0 jobs must be ACKnowledged explicitly at all, so we may also return the retry count alongside with the job in GETJOB. This way if a job as retry set to 0, the client should not ACK it. However this makes the API more complex, and fire and forget workload may be less important then expected with Disque.

Ok my latest take on this, until implementation or next change of idea:

Retain jobs, so that the workflow is identical whatever the job kind is, from the POV of clients.
Evict those jobs when we are short on memory, since they are irrelevant if lost, and there is not the problem of leaking them otherwise.

However in addition to that, it would be kinda nice to also have a one bit flag in the node ID signaling this job is a fire-and-forget one. This way we could avoid the creation of a dummy ack. Not sure where to put this currently.

Finally fixed the first issue ever opened :-)


Added legacy article

Docs Build status updates of commit 9b693c9:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error-PullRequestMergeConflict] Cannot sync git repo to specified state. Please make sure the pull request is mergeable.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 9b693c9:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error-PullRequestMergeConflict] Cannot sync git repo to specified state. Please make sure the pull request is mergeable.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit cd45e5c:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error-PullRequestMergeConflict] Cannot sync git repo to specified state. Please make sure the pull request is mergeable.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 606f7dd:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error-PullRequestMergeConflict] Cannot sync git repo to specified state. Please make sure the pull request is mergeable.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit c6422cb:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.publish.config.json
:white_check_mark:Succeeded

.openpublishing.redirection.json
:white_check_mark:Succeeded

developer/docfx.json
:white_check_mark:Succeeded

developer/toc.yml
:white_check_mark:Succeeded
View

legacy/breadcrumb/toc.yml
:white_check_mark:Succeeded

legacy/docfx.json
:white_check_mark:Succeeded

legacy/index.yml
:white_check_mark:Succeeded
View

legacy/toc.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 22951c6:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

developer/toc.yml
:x:Error

Details

developer/toc.yml

Line 4, Column 3: [Error-yaml-syntax-error] While parsing a block mapping, did not find expected key.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 0f8e90a:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.publish.config.json
:white_check_mark:Succeeded

.openpublishing.redirection.json
:white_check_mark:Succeeded

developer/docfx.json
:white_check_mark:Succeeded

developer/toc.yml
:white_check_mark:Succeeded
View

legacy/breadcrumb/toc.yml
:white_check_mark:Succeeded

legacy/docfx.json
:white_check_mark:Succeeded

legacy/index.yml
:white_check_mark:Succeeded
View

legacy/toc.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit f0b6019:
:warning: Validation status: warnings

File
Status
Preview URL
Details

legacy/toc.yml
:warning:Warning
View
Details

.openpublishing.publish.config.json
:white_check_mark:Succeeded

.openpublishing.redirection.json
:white_check_mark:Succeeded

developer/docfx.json
:white_check_mark:Succeeded

developer/toc.yml
:white_check_mark:Succeeded
View

legacy/breadcrumb/toc.yml
:white_check_mark:Succeeded

legacy/docfx.json
:white_check_mark:Succeeded

legacy/index.yml
:white_check_mark:Succeeded
View

legacy/toc.yml

Line 2, Column 9: [Warning-file-not-found] Invalid file link: 'index'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 7c94849:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.publish.config.json
:white_check_mark:Succeeded

.openpublishing.redirection.json
:white_check_mark:Succeeded

developer/docfx.json
:white_check_mark:Succeeded

developer/toc.yml
:white_check_mark:Succeeded
View

legacy/breadcrumb/toc.yml
:white_check_mark:Succeeded

legacy/docfx.json
:white_check_mark:Succeeded

legacy/index.yml
:white_check_mark:Succeeded
View

legacy/toc.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 278e27b:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.publish.config.json
:white_check_mark:Succeeded

.openpublishing.redirection.json
:white_check_mark:Succeeded

developer/docfx.json
:white_check_mark:Succeeded

developer/toc.yml
:white_check_mark:Succeeded
View

legacy/breadcrumb/toc.yml
:white_check_mark:Succeeded

legacy/docfx.json
:white_check_mark:Succeeded

legacy/index.yml
:white_check_mark:Succeeded
View

legacy/toc.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit db036b0:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.publish.config.json
:white_check_mark:Succeeded

.openpublishing.redirection.json
:white_check_mark:Succeeded

developer/docfx.json
:white_check_mark:Succeeded

developer/toc.yml
:white_check_mark:Succeeded
View

legacy/breadcrumb/toc.yml
:white_check_mark:Succeeded

legacy/docfx.json
:white_check_mark:Succeeded

legacy/index.yml
:white_check_mark:Succeeded
View

legacy/toc.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit db036b0:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.publish.config.json
:white_check_mark:Succeeded

.openpublishing.redirection.json
:white_check_mark:Succeeded

developer/docfx.json
:white_check_mark:Succeeded

developer/toc.yml
:white_check_mark:Succeeded
View

legacy/breadcrumb/toc.yml
:white_check_mark:Succeeded

legacy/docfx.json
:white_check_mark:Succeeded

legacy/index.yml
:white_check_mark:Succeeded
View

legacy/toc.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Rock RMS

https://github.com/SparkDevNetwork/Rock/issues/5068
Need to validate this project has "reasonable following, popularity or visibility" before adding.

Similarweb global rank of https://rockrms.com is 945,092.

Added in ee6709444dd08e7922ec0bb126ef441a3ed9d6e1.
@elliotwutingfeng Thanks, hard to put a global site rank into relative terms to be honest.
I did see they have over 80 reviews on Capterra so look fairly well established.


Added getData() method to Basho\Riak\Search\Doc

See Basho\Riak\Search\Doc does not allow to fetch all values returned by Solr #117 (CLIENTS-683) (CLIENTS-754)
Note that getData() returns an array (see issue comment). I also added tests and inline documentation.

Looks good. Thanks @lastzero .


Emacs freezes after calling 'doom/window-enlargen'

What did you expect to happen?
Calling doom/window-enlargen will enlarge my current window
What actually happened?
Emacs freezes.
Steps to reproduce:
I'm still not completely sure of this issue's reproducibility, but this is the simplest form I could distill it to.

Open a new Emacs session
Download this org file: https://raw.githubusercontent.com/archiif/random/master/test.org and open it in Emacs
Scroll all the way down, until the pointer can no longer move
Split the window vertically and select the right window
Switch to the aforementioned org buffer in that new window
M-x doom/window-enlargen

System information:

emacs   version    27.1
        features   XPM JPEG TIFF GIF PNG RSVG CAIRO SOUND GPM DBUS GSETTINGS GLIB
                   NOTIFY INOTIFY ACL LIBSELINUX GNUTLS LIBXML2 FREETYPE HARFBUZZ M17N_FLT
                   LIBOTF ZLIB TOOLKIT_SCROLL_BARS GTK3 X11 XDBE XIM MODULES THREADS
                   LIBSYSTEMD JSON PDUMPER LCMS2 GMP
        build      Aug 13, 2020
        buildopts  (--with-cairo --with-mailutils)
        windowsys  x
        daemonp    server-running
doom    version    2.0.9
        build      HEAD -> develop a2da5d7a6 2020-08-17 21:25:34 -0400
        dir        ~/.doom.d/
system  type       gnu/linux
        config     x86_64-pc-linux-gnu
        shell      /bin/bash
        uname      Linux 4.4.0-18362-Microsoft #836-Microsoft Mon May 05 16:04:00 PST 2020 x86_64
        path       ;; truncated, way too long and a bit TMI
config  envfile    envvar-file
        elc-files  0
        modules    (:input japanese :completion company helm ivy :ui doom
               doom-dashboard doom-quit hl-todo modeline ophints (popup +defaults) tabs
               treemacs unicode vc-gutter vi-tilde-fringe workspaces :editor (evil
               +everywhere) file-templates fold (format +onsave) snippets word-wrap
               :emacs dired electric undo vc :term vterm :checkers syntax :tools (eval
               +overlay) lookup magit pdf rgb :lang common-lisp emacs-lisp markdown org
               python sh yaml :email (mu4e +gmail) :app irc :config (default +bindings
               +smartparens))
        packages   ((org-download :recipe (:host github :repo
                abo-abo/org-download)) (helm-org-rifle) (ahk-mode) (scrollkeeper)
                (vterm-extra :recipe (:host github :repo Sbozzolo/vterm-extra))
                (org-ql))
        unpin      (n/a)
        elpa       (n/a)

Hi! Is this still an issue after 8999719? I haven't been able to reproduce this, but I suspect disabling window-resize-pixelwise may have helped. Please let me know.

I have still seen the freeze since.

Yep, it still freezes for me. The above reproduction steps still applies.


Update to the latest choco-theme

Description Of Changes
This updates to the latest choco-theme. No significant changes have been made that would affect the functionality of this website.
Motivation and Context
Choco-theme is outdated and it would be good to have it the same as the other websites so it doesn't get too far behind.
Testing

[x] I have previewed these changes using the Docker Container or another method before submitting this pull request.

Change Types Made

[ ] Minor documentation fix (typos etc.).
[ ] Major documentation change (refactoring, reformatting or adding documentation to existing page).
[ ] New documentation page added.
[ ] The change I have made should have a video added, and I have raised an issue for this.

Change Checklist

[ ] Requires a change to menu structure (top or left hand side)/
[ ] Menu structure has been updated

Related Issue
n/a

Thanks for getting this updated @st3phhays


Fix eslint typeof warning

Notes for Reviewers
This PR fixes #7687
Signed commits

[x] Yes, I signed my commits.

Eslint is fixed on master now.


Discoverability of .Flatten() and .WithFixedPageSize() methods

The IPagedEnumerable<...> (and IPagedAsyncEnumerable<...>) .Flatten() and WithFixedPageSize() extension methods are in namespace Google.Api.Gax, possibly making them less discoverable than we might like.
Should we add these methods to the interfaces, given that we don't expect anyone else to implement these interfaces?

Yes, I think that would be a good idea. Having used this a couple of times now, the discoverability could certainly be better.

Assigning myself as I can do this in a PR before taking off for vacation...


Add ParserUtils.getPersonFromIndex

Additional changes:

Now person can be fetched from within the parser instead of during the execution of addTxn command

close #211

Fixed a cyclic dependency issue. Refer to https://github.com/AY2425S1-CS2103-F13-1/tp/pull/245#discussion_r1827606083 to see fix


[Feature Request] Converst JS to JSON during Beautify

Overview

Insomnia Version:  5.7.4 (<IP_ADDRESS>3)

If I write a js object,  I want to format to a json (like jsoneditoronline), or when send it transform to json;

This is a fairly difficult problem to solve. Do you know of any existing libraries for converting JS syntax to JSON?

That seems rather unsafe ☠

JSON.stringify().

@LouisRitchie it would need to be a JS object to do that. Hence the unsafe eval suggestion above to turn it from a string to a JS object.

Hmm, found a few suggestions here. https://stackoverflow.com/questions/9637517/parsing-relaxed-json-without-eval

Would JSON5 be acceptable? The project has been around for quite awhile and is based of Crockford's original implementation.

I think JSON5 could possibly work.

Do you think it would work better as it's own body type (ie. JSON & JSON5) or do we just patch JSON to try and parse and if it fails fallback to JSON5?
I have not looked at the nunjucks templating code yet, but do you forsee any issues integrating with that?

Ya, I'm not quite sure about that yet. Currently, Insomnia uses a custom parser to prettify JSON in order to modify it as little as possible. It might actually be possible to modify it to do things like add quotes and ignore comments. It already does this with Nunjucks tokens.

Comments are actually  pretty tricky though since you want to keep them in but you don't want to send them with the request. In that case, a new body type may be desirable.

Actually, this issue wasn't really about comments so maybe that doesn't matter.
There is actually already a way to do comments and that's using Nunjucks sytax {# a comment #}

Sure, thanks for the info! I think I will have some time this weekend to start hacking on this.

Awesome! What's your rough plan? Just want to make sure we're on the same page since a lot has been discussed here.
Also, let me know if there's anything I can help with. 😀

Hmm. I think the main scope of this and what I personally would like as well is just unquoted keys and single-quoted strings (trailing commas would be nice too).
Plan would be to see if we can just hack those into the existing parser and call it a win? As I said, have not looked at the code very closely at all (except to see that it is nicely organized 😄 ), so I think I will need to dig in a bit before I know more.

That sounds perfect. We were on the exact same page.


add ability to add a field prefix for join_as

Codecov Report
Attention: 3 lines in your changes are missing coverage. Please review.

Comparison is base (c9eb851) 81.40% compared to head (e7d6568) 81.49%.

Files
Patch %
Lines

metrics_layer/core/model/field.py
70.00%
2 Missing and 1 partial :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##           master     #152      +/-   ##
==========================================
+ Coverage   81.40%   81.49%   +0.08%
==========================================
  Files          46       46
  Lines        5540     5549       +9
  Branches     1374     1377       +3
==========================================
+ Hits         4510     4522      +12
+ Misses        787      784       -3
  Partials      243      243

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


PasswordTextbox hint not appearing on iOS

Describe the bug
The Hint property for the PasswordTextbox does not appear in the companion app.
Affects

[ ] Designer
[ ] Blocks editor
[ ] Projects Explorer
[x] Companion (iOS)
[ ] Compiled apps
[ ] Buildserver
[ ] Debugging
[ ] Other... (please describe)

Expected behavior
Creating a PasswordTextbox and setting its Hint property should show a hint. However, that does not appear to be the case. This was discovered in a worshop.
Steps to reproduce
See above.

Actually, upon reviewing this the hint does have a color, but it is such a light gray that it is almost indistinguishable from the white of the textbox's background color.

This should be fixed as of iOS companion 2.64.4 (13).


Exception: Xcodeproj is not installed  even when XcodeProj is installed

I tried to update a flavor today and got the error that Xcodeproj is not installed. This worked fine a few weeks ago.
So I do the command gem install xcodeproj, It says its already installed. I also removed both versions I had and ran the command again but still, the same issue persists where Flavorizr is saying that I don't have it installed.
I get the following error in the console:
Executing task ios:xcconfig
Running XcodeprojProcessor: Checking if xcodeproj is installed
Unhandled exception:
Exception: Xcodeproj is not installed. Please install it by running gem install xcodeproj
#0      XcodeprojProcessor.execute (package:flutter_flavorizr/src/processors/darwin/xcodeproj_processor.dart:20:7)
#1      QueueProcessor.execute (package:flutter_flavorizr/src/processors/commons/queue_processor.dart:44:17)
#2      Processor.execute (package:flutter_flavorizr/src/processors/processor.dart:140:24)

Any idea what could be happening? I also updated Ruby Gems and xcodeproj to the latest version but no change.

Same error here. Error when running even though xcodeproj is installed.

Can you please provide the output of:
gem list -i ^xcodeproj$
and
gem list xcodeproj

The output for first command is true
And for second command: xcodeproj (1.24.0)

Everything is installed as you can see, still throwing error

same problem

Hi,
You must add a .cmd extension for gem in xcodeproj_processor.dart.
you can find it in Pub\Cache\hosted\pub.dev\flutter_flavorizr-[VERSION]\lib\src\processors\darwin\xcodeproj_processor.dart

Hi, for temp solution:
You must add a .cmd extension for gem in xcodeproj_processor.dart. you can find it in Pub\Cache\hosted\pub.dev\flutter_flavorizr-[VERSION]\lib\src\processors\darwin\xcodeproj_processor.dart

cc: @AngeloAvv

This still seems to be the only thing that works

Hi, for temp solution:
You must add a .cmd extension for gem in xcodeproj_processor.dart. you can find it in Pub\Cache\hosted\pub.dev\flutter_flavorizr-[VERSION]\lib\src\processors\darwin\xcodeproj_processor.dart

cc: @AngeloAvv

This still seems to be the only thing that works

It doesn't work for me, it says command not found: gem.cmd, so it's not a good solution that would work for everyone

Hi, for temp solution:
You must add a .cmd extension for gem in xcodeproj_processor.dart. you can find it in Pub\Cache\hosted\pub.dev\flutter_flavorizr-[VERSION]\lib\src\processors\darwin\xcodeproj_processor.dart

cc: @AngeloAvv

This still seems to be the only thing that works

It doesn't work for me, it says command not found: gem.cmd, so it's not a good solution that would work for everyone
Question: .cmd files are used on Windows, are you running flutter_flavorizr on Windows? If you have iOS/macOS flavors, you must run flutter_flavorizr on macOS. There's no way you could use xcodeproj gem on other operating systems

I am indeed running on windows, and its actually always worked perfectly on windows, no need to be on macOS to create flavors, which is also the thing i love so much about this package. This issue that i needs to be set to .cmd has only happened the last 6 months or so before that i never had an issue

Ok, now I see the bigger picture caused by the introduction of more restricted checks on xcodeproj.
A lot of people do not read the README and forget about installing the gem, therefore they keep opening the same issue repeatedly, that's why I introduced this kind of check.
I honestly never ran flutter_flavorizr on other OSes than macOS when I needed to flavorize iOS/macOS apps, that's why I'm saying it will never work (I mean, it could, but I never tested it)
At this point, at least I know how to reproduce this issue. Let me think about it and I will come back with a solution

No worries, very understandable! But great that where the issue lies is now clear, if you need any additional info from me let me know!

Same issue am also facing

need help

@Mr-yuwei @suhailthajudeen see the fix/workaround above


Prevent from css broken

@Teranode , please check when you have time.
Issue:

when we're using styles as object

  pluginOptions: {
    autoImports: true, // default
    styles: { configFile: 'assets/sass/settings.scss' },
  },

We will got css broken, since it doesn't included the vuetify/styles with.

@Teranode can you release it?


[AutoDiff] Fix semantic member accessor pullbacks ownership errors.

Fix ownership errors in semantic member accessor pullbacks:

Getter pullbacks: emit copy value operation before storing value.
Setter pullbacks: track loaded value as a temporary, to be destroyed.

Add tests covering trivial, non-trivial, and address-only properties.
Resolves SR-12778 and SR-12779.

@swift-ci Please test


Not clear that too many boxes are checked

When more than two location boxes are checked, a small text is given to you after you try to calculate the travel time. There should be a better way.  There are a few ways to improve this, none necessarily wrong:

Not allow more than one destination to be selected and give instant, clear feedback that selecting another is not allowed
Allow them to select a third box, but show them that one of the other boxes must be deselcted before calculating the time

F17 OK (150 pts)

This one looks good.

F17 CLOSED


Integrate LW++ into the next stage of SpaceWarps

Goal
We plan to embed the LW++ into SpaceWarps so that citizen scientists can not only help us to identify lenses, but also model lenses trivially.
Tasks

Initialize LW++ according to the click position from users at Space Warps.

[ ] Cut out the lensed images.
[ ] Initialize the Einstein Radius, the Ellipticity, and the orientation of the lens.
[ ] Initialize the position of the source.
[ ] Build an "initializing button" to implement the task above together.

Model the lens by clicking the "Sample" button. This task is described in #7 .

Phil's Suggestions
To get started, though, we could also make an "initialize" button that sets up a lens and source model just based on the data image properties. x_lens and y_lens can come from the R channel, x_img and y_img can come from the (B - alpha*R) image, where alpha is a scalar chosen to minimise the difference between the B and R images (as in Tom's BlueRings project here: https://github.com/DES-SL/BlueRings/blob/master/StandAloneRingFinder.py#L66)  The lens Einstein radius could just be set to the 3/4 of the arc radius or something.

:-) @linan7788626 Can you please edit your message above so it says "one day hope to" rather than "plan to", there are many steps along the path to productive Space Warps integration!
For example, the first step is to get the Space Warps PIs plus Rafi Kueng and Prasenjit Saha over here, to help guide the project. Rafi is doing a PhD on collaborative online lens modeling, and knows best what his team of citizens needs.
Then, Aprajita Verma and Anupreeta More are working on the Space Warps site itself: they will be able to give good advice on what to focus on so that the LW++ app is useful for all citizens and not just Rafi's modeling team.
I'll email all these people and invite them over!
Then, I think you should postpone the idea of using the SW click positions to initialize the model, and instead focus on the lens light subtraction initialization. Can you edit your first message to reflect this as well please? Thanks!
In short, a standalone app that a user can initialize from scratch (by some combination of subtracting the red from the blue channels and then manipulating the model by hand) is the best thing to focus on at first.  "MCMC Sample" and "Optimize" buttons would be fantastic though - everyone will want them! :-)

PS. This issue's title should probably also be changed, to something like "Initialize model and data by subtracting and measuring channel images"

Agreed, the title seems to be overkilled, and we should focus on a standalone APP. I just changed the title and updated the list of tasks. Please let me know if you have any other suggestions. Thanks

I think Task 1 should read:
Initialize Button, when pressed:

[ ] Finds the peak of the red image and assume that this is the center of the lens galaxy, and that that pixel has the color of the lens galaxy
[ ] Separates the red ("lens") light from the blue ("source") light to make 2 separate PNGs
[ ] initializes a lens mass model based on the "lens" light
[ ] Initializes a source model based on the "source" light
[ ] Displays only the lens light PNG in the "Mass Model" panel, and the source light PNG in the "Image Plane" panel

This would be a pretty good automatic, one-click initilization routine.
If we already had a mass and source model, however, we could use them to do a better initialization! The mass model could be used to define the position of the lens light (and its color), and the chosen lensed image position could be used to define the position of the lensed source light (as discussed in #4) and its color. I recommend we implement the one-click option anyway, though, because the "initialize" button should always work. BTW do you think it should be labelled "initialize" or better "Separate Foreground/Background" or "Subtract" or something?

PS. We should replace "LW++" with "Hoopla" in the first comment, as well! :-)

Just did it, thanks for your reminding.

I think Task 1 should read:
Initialize Button, when pressed:

[ ]  Finds the peak of the red image and assume that this is the center of the lens galaxy, and that that pixel has the color of the lens galaxy

[ ] Separates the red ("lens") light from the blue ("source") light to make 2 separate PNGs
[ ] initializes a lens mass model based on the "lens" light
[ ] Initializes a source model based on the "source" light
[ ] Displays only the lens light PNG in the "Mass Model" panel, and the source light PNG in the   "Image Plane" panel

This would be a pretty good automatic, one-click initialization routine.

Sounds great, these bullets make the issue more clear, I will update this issue asap. Thank you.

If we already had a mass and source model, however, we could use them to do a better initialization! The mass model could be used to define the position of the lens light (and its color), and the chosen lensed image position could be used to define the position of the lensed source light (as discussed in #4) and its color. I recommend we implement the one-click option anyway, though, because the "initialize" button should always work. BTW do you think it should be labelled "initialize" or better "Separate Foreground/Background" or "Subtract" or something?

Agreed, let us make the simplest way happens first. In term of the label, I would like to use "initialize" because the tasks list covers more than "Separate" and "subtract" . We can create more issues for the sub-projects (for example, "Separate" and "Subtract") in this issue. I will think about this and implement it later.

Good plan!
On Thu, Sep 15, 2016 at 12:07 PM, Nan Li<EMAIL_ADDRESS>wrote:

I think Task 1 should read:
Initialize Button, when pressed:

Finds the peak of the red image and assume that this is the center
of the lens galaxy, and that that pixel has the color of the lens galaxy

Separates the red ("lens") light from the blue ("source") light
to make 2 separate PNGs
initializes a lens mass model based on the "lens" light
Initializes a source model based on the "source" light
Displays only the lens light PNG in the "Mass Model" panel, and
the source light PNG in the "Image Plane" panel This would be a pretty good
automatic, one-click initialization routine.

Sounds great, these bullets make the issue more clear, I will update this
issue asap. Thank you.
If we already had a mass and source model, however, we could use them to
do a better initialization! The mass model could be used to define the
position of the lens light (and its color), and the chosen lensed image
position could be used to define the position of the lensed source light
(as discussed in #4 https://github.com/linan7788626/Hoopla/issues/4)
and its color. I recommend we implement the one-click option anyway,
though, because the "initialize" button should always work. BTW do you
think it should be labelled "initialize" or better "Separate
Foreground/Background" or "Subtract" or something?
Agreed, let us make the simplest way happens first. In term of the label,
I would like to use "initialize" because the tasks list covers more than
"Separate" and "subtract" . We can create more issues for the sub-projects
(for example, "Separate" and "Subtract") in this issue. I will think about
this and implement it later.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/linan7788626/Hoopla/issues/8#issuecomment-247422078,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AArY9yC_O_qzsuTCkuLmtk67F2BxTZ1wks5qqZdigaJpZM4J7zyx
.


New/link css

with the next version of the site, i'm going to see if i can both separate content + site, maybe set the repository as a template so people don't have to fork it, etc. etc.
but uhhh... whoops lol (^^;)


style(Combobox): Add transparent background to wrapper

Resolves #1630
We might not need to use the Box component here, but this PR only changes the css to be transparent

Doh! 🙈
Maybe we add a different background color to Storybook for better testing.

We do have the testing page, but since we did not add a label it was not spotted :P


Show a warning message on suspected usages of parameter GPU migration

Function.to_gpu and FunctionSet.to_gpu involves array copying, while an Optimizer object does not know this event. Consequently, user must migrate parameters onto devices BEFORE passing them to the optimizer. Violating this rule does not emit any messages currently, which ends up to making the training code meaningless.
So how about show a warning message if FunctionSet.collect_parameters is called after FunctionSet.to_gpu?

I think it's enough.

It is important what Chainer shows as a warning message. I think we should add not only the measures we should take when users are confronted with the warning but also the reason (that beam2d mentions in this issue) why they must take the measures. One of the solution would be to refer to this issue in the warning message.

@delta2323 That's a good idea! Let's include into the message a reason why we show it (maybe with a pointer to this issue).

Close since this issue is obsolete.


remove docs on the PersistentVolumeLabler controller

This is a follow-up to https://github.com/kubernetes/website/pull/12375, forgot to clean up docs on this topic in the cloud-controller page.
/assign @dims

/approve
/lgtm

xref: https://github.com/kubernetes/kubernetes/pull/72972
This should go to dev-1.14 branch not master.

/hold

/hold cancel

/lgtm
/approve
Master is 1.14 now.


Issue with Loading Models from Huggingface Repo

Hi,
Thank you for your fantastic project.
I've encountered a problem when trying to evaluate the model downloaded from the Huggingface repo given in your project.  I'm facing an issue with both the small and tiny vim models. When I loaded the models, I receive the following error message:
"size mismatch for pos_embed: copying a param with shape torch.Size([1, 730, 384]) from checkpoint, the shape in the current model is torch.Size([1, 197, 384])."
Could you please offer some guidance on how to address this problem? Your assistance would be greatly appreciated.
Thank you so much for this matter!

metoo ,what is file

yes i got

yes i got

Did you make it work with any of the models? I tried both the Tiny and Small versions but none of them works for me..

me too, anyone solved this issue?

me too, anyone solved this issue?

@jiabingxiing Hi, I encountered same problem and have fixed it. Use models whose name contains 'stride8' in vim\models_mamba.py (such as vim_tiny_patch16_stride8_224_bimambav2_final_pool_mean_abs_pos_embed_with_midclstok_div2), which is compatible with the pth on huggingface

@jiabingxiing @cskyl try stride8 version,
import torch

from models_mamba import (
    vim_small_patch16_224_bimambav2_final_pool_mean_abs_pos_embed_with_midclstok_div2,
    vim_small_patch16_stride8_224_bimambav2_final_pool_mean_abs_pos_embed_with_midclstok_div2,
    vim_tiny_patch16_224_bimambav2_final_pool_mean_abs_pos_embed_with_midclstok_div2,
    vim_tiny_patch16_stride8_224_bimambav2_final_pool_mean_abs_pos_embed_with_midclstok_div2)

def main():
    model = vim_small_patch16_stride8_224_bimambav2_final_pool_mean_abs_pos_embed_with_midclstok_div2()
    sd = torch.load("checkpoints/vim_s_midclstok_ft_81p6acc.pth")
    model.load_state_dict(sd["model"])

    model = model.to("cuda:0")
    model(torch.rand(4, 3, 224, 224, device="cuda:0"))

    model = vim_tiny_patch16_stride8_224_bimambav2_final_pool_mean_abs_pos_embed_with_midclstok_div2()
    sd = torch.load("checkpoints/vim_t_midclstok_ft_78p3acc.pth")
    model.load_state_dict(sd["model"])

    model = model.to("cuda:0")
    model(torch.rand(4, 3, 224, 224, device="cuda:0"))

if __name__ == "__main__":
    main()

Thank you!

@cskyl @lyhyl have it worked for you? I am facing the same error as you posted. and if I try the stride8 version then I got "model.load_state_dict(sd["model"])
error: couldn't allocate input reg for constraint 'l'"


Fix pprint for Product2

This fixes https://github.com/lihaoyi/PPrint/issues/28
We had a similar problem while pprinting akka.kafka.ConsumerMessage.CommittableMessage. I found that the problem is reproduced when Product2 is used.
Walker.scala:90 calls Util.isOperator(x.productPrefix), but Product defines it as an empty string :
def productPrefix = ""

So ident(0) in Util.scala:50 fails with java.lang.StringIndexOutOfBoundsException
I've added a unit test and my proposition of a fix.

Hello, any chance of accepting this PR?


TypeError: Cannot read properties of undefined (reading 'code_snippet')

Please include some context and the contents of the console in your browser's developer tools.
TypeError: Cannot read properties of undefined (reading 'code_snippet')
    at XE (http://localhost:8001/:72:249981)
    at mi (http://localhost:8001/:72:70706)
    at Ql (http://localhost:8001/:72:122308)
    at xc (http://localhost:8001/:72:109797)
    at _c (http://localhost:8001/:72:109725)
    at Cc (http://localhost:8001/:72:109588)
    at Nc (http://localhost:8001/:72:106582)
    at hc (http://localhost:8001/:72:103958)
    at nu (http://localhost:8001/:72:119816)
    at http://localhost:8001/:72:121187

User Agent
Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/100.0.4896.60 Safari/537.36

Thanks! This seems to be a duplicate of #109. I'll close this issue for now and we'll continue this discussion there.


Tabe with header on each page

I am trying to render a table in pdf which spawns across multiple pages. I want the header to appear on every page.
I tied multiple things including having a thead, tbody etc but nothing worked.
When viewed in html and printed to pdf from the browser, the page renders correctly with table headers on each page. Please help.

https://github.com/marcbachmann/node-html-pdf/issues/46


certificates expired for datanode after long downtime

Hi,
I have a docket-setup of Graylog in my home lab.  Before I restarted it the next time the selfmade certificates of the datanode expired. Now Graylog does not come up again.
Here an quote from the log:

INFO  [OpensearchProcessImpl] [2024-03-09T13:14:24,051][WARN ][o.o.h.AbstractHttpServerTransport] [opensearch] caught exception while handling client http traffic, closing connection Netty4HttpChannel{localAddress=/<IP_ADDRESS>:9200, remoteAddress=/<IP_ADDRESS>:47170}
datanode_1  | 2024-03-09T13:14:24.053Z INFO  [OpensearchProcessImpl] io.netty.handler.codec.DecoderException: javax.net.ssl.SSLHandshakeException: Received fatal alert: certificate_unknown

I think the mechanism to rotate the certs on it's own does only work when Graylog is up and running - but is it not starting here. It's a bit sad not to consider this case.
My suggested fix would be to check the certs during startup and rotate if necessary during startup.
cheers,
Snab

I have the same problem due to the short certificate times, my mongo db died, and when I came to fix it, I think the process that automaticly renews it then didn't happen, and now I can't get the stack back up.
I can't find any documentation that tells you how to manually renew the certificate when using a built in CA. Just how to do the initial setup.

Happened to me twice that I had to ditch the DB and start fresh (after a few days trying...). Recovery from problems isn't easy.
So I made a mongodump to save inputs, searches and dashboards. Then restored them after a full reset. I recently found out you can also export those into a "content pack" (System -> Content Pack).
The logs are lost, but it's OK if that only happens from time to time.

I finally managed to fix it. Well a workaround.
I connected to the datanode https API instance on port 9200, to check when the certificate expired. Stopped the containers. I then disabled NTP on the host and then set the time on the server to one day before the expiry. Started all the containers, 3-4 minutes later, I went to 9200 again and could see the certificate had renewed. Luckily I didn't need to repeat this process again with an interim date, as the new certs date range included todays date, as it only expired 20 days ago. I then stopped the containers, renabled ntp again, which brought the date back to current. Started containers and then it all worked again.
Hopefully you get this problem again or someone else does, they can try the above workaround. A proper fix would indeed be better though, like a force renew command or something to temporary disable the cert check, so it can get in and renew it via the APIs, it doesn't trust due to the date being wrong.

Hi everyone, I just wanted to let you know that I am working on a better way of certificate renewal with your problems in my mind. Thanks for your feedback and reports!
Best regards,
Tomas


Sync RabbitMQ changes from the rabbitmq sensu plugin repo

Avoid incredibly small egress numbers breaking graphite output
Allow monitoring all queues except those you exclude in the consumer count check
Allow specifying per queue message count thresholds vs. system level message count thresholds

@tas50 Can you rekick this.  Travis is puking again

Should be fixed now.  That same fix is in the rmq repo now as well.


Meaning of Sum

I got your training script to run, but I was wondering what the meaning of "sum" is.
I.e. "2018-08-18 09:23:40 steps >>> epoch 1 batch 12 sum:       10.1"
Is that the sum of the losses in the given batch or how can I interpret it?
I looked into the code and couldn't find the information. I'm assuming it's part of the steppy toolkit?

Hi @sushimon . yeah steppy has an option to pass a list of losses with weights and then it is loss sum. Here we actually have one loss but it is still called a sum.
Anyhow it is just the epoch training loss.


Merging documentation and naming refactors in diffuse_raw

No pasa, arregla estas 3 cosas please
src/diffupy/diffuse_raw.py:28:1: D205 1 blank line required between summary line and description
src/diffupy/diffuse_raw.py:28:1: D400 First line should end with a period
src/diffupy/diffuse_raw.py:28:1: D401 First line should be in imperative mood; try rephrasing


reduced_genome.sh error - grep: memory exhausted

Hi,
I get an error running the reduce_genome.sh script on the full hg19 genome (seems to have issues with the line which selects unique fasta sequences). Increasing the session memory doesn't seem to help (as much as 96g); it might be a built in limitation in grep?
Ended up replacing:
grep -v '^>' ${genome}_${enzyme}flanking_sequences${fl}unique_2.fa | sort | uniq -i -u | grep -xF -f hg19_dpnii_flanking_sequences_100_unique_2.fa.temp -B 1 ${genome}${enzyme}flanking_sequences${fl}unique_2.fa | grep -v '^--' > ${genome}${enzyme}flanking_sequences${fl}_unique.fa
with an awk liner:
awk '$1~/^>/{seq=$1; next};{$1=toupper($1)};a[$1]>0{a[$1]-=1;next};{a[$1]=seq};END{for(x in a){if(a[x]>0){print a[x];print x}}}' hg19_dpnii_flanking_sequences_100_unique_2.fa > hg19_dpnii_flanking_sequences_100_unique.fa
which seems to fix things...

Hi thanks a lot for re-writing this to be less memory intensive. I have never had problems running this script but I know other people have. Would you be ok with me giving this line to people if they are having the same problems?

Certainly!
I made a mistake copying the code over:
The proper liner is:
awk '$1~/^>/{seq=$1; next};{$1=toupper($1)};a[$1]>0{a[$1]-=1;next};{a[$1]=seq};END{for(x in a){if(a[x]>0){print a[x];print x}}}' hg19_dpnii_flanking_sequences_100_unique_2.fa > hg19_dpnii_flanking_sequences_100_unique.fa

Certainly!
I made a mistake earlier copying the liner. It's now fixed in the above comment

Thanks! :)

For me, that awk one-liner doesn't give the same results as the original command. Full test with example data below, and an alternative approach that avoids grep and does match results from the original comand.
39MB example data here: https://helix.nih.gov/~dalerr/dm6_DpnII_25mer_flanking.fa
Setup
wget https://helix.nih.gov/~dalerr/dm6_DpnII_25mer_flanking.fa
INPUT=dm6_DpnII_25mer_flanking.fa
OUTPUT=dm6_DpnII_25mer_flanking_unique.fa

Option 1
As used in reduce_genome.sh;  ~12 seconds
grep -v '^>' $INPUT \
  | sort \
  | uniq -i -u \
  | grep -xF -f - -B 1 $INPUT \
  | grep -v '^--' > ${OUTPUT}.1

Option 2
From @mimi31k in above post; ~4 seconds
awk \
'$1~/^>/{seq=$1; next};\
{$1=toupper($1)};\
a[$1]>0{a[$1]-=1;next};\
{a[$1]=seq};\
END\
{for(x in a){if(a[x]>0){print a[x];print x}}}' \
$INPUT > ${OUTPUT}.2

Option 3
My alternative attempt. Uses 2 arrays; a to keep track of the sequence count and b to keep track of the header for the last-seen sequence. Since we only care about cases where there's only one sequence, it's OK that the b array entries get overwritten for subsequent sequence occurrences. Plus it also keeps memory usage low. ~3 seconds
paste - - < $INPUT | awk \
  '{a[toupper($2)]++; b[$2]=$1}; END \
  {for(n in a) if (a[n] == 1) print b[n]"\n"n}' \
  > ${OUTPUT}.3

Comparisons
Since the awk methods do not retain the sorting of the original, first I'm sorting the files just for comparison purposes:
sort ${OUTPUT}.1 > out1.sorted
sort ${OUTPUT}.2 > out2.sorted
sort ${OUTPUT}.3 > out3.sorted

Then compare them. Option 2 is reporting about 1% extra sites compared to option 1, but option 1 and option 3 output match.
diff out1.sorted out3.sorted | wc -l  # 0

# Compare option 1 and option 2
# in both:
comm out1.sorted out2.sorted -1 -2 | wc -l  # 1324242

# only in option 2
comm out1.sorted out2.sorted -1 -3 | wc -l  # 15638

# only in option 1
comm out1.sorted out2.sorted -2 -3 | wc -l  # 0

So I think option 3 would be a better approach, as long as it's OK that the de-duped sequences have a different order from the original.

Update to get sorted output. This runs slower than the original, at ~20s.
paste - - < $INPUT | awk \
  '{a[toupper($2)]++; b[$2]=$1}; END \
  {for(n in a) if (a[n] == 1) print b[n]"\n"n}' \
  | sort -k1,1 -k2,2n -k3,3n \
  | awk '{print $1":"$2"-"$3"\n"$4}' \
  > ${OUTPUT}.3

I had some issues with the script above so I re-wrote this:
awk '{if(NR%2){printf("%s\t",$1)}else{print}}' ${genome}_${enzyme}flanking_sequences${fl}unique_2.fa | sort -k2,2| awk -v IGNORECASE=1 '{if($2==SEQ){gsub(">","",$1);ID=ID"|"$1;counter++} else{if(SEQ!="" && counter == 1){printf("%s\n%s\n", ID,SEQ)}SEQ=$2;ID=$1;counter = 1} }END{printf("%s\n%s\n", ID,SEQ)}' > ${genome}${enzyme}flanking_sequences${fl}_unique.fa


Documentation fix: grammar issue

What changes were proposed in this pull request?

Why are the changes needed?

Does this PR introduce any user-facing change?

How was this patch tested?

Can one of the admins verify this patch?

Can one of the admins verify this patch?


CHQ-66 Updated TOC on README.md and added core devs and envs

Story
https://maddonkeysoftware.myjetbrains.com/youtrack/issue/CHQ-66
Summary

Updated TOC on README.md and added core devs and environments table

Testing

N/A - Documentation change

Merging since this has sat for too long without review.


Fixing Broken Link

https://github.com/MicrosoftDocs/OfficeDocs-SkypeForBusiness/issues/2447

@nenonix @JohanFreelancer9 Copy editing is needed for this PR. Thanks.

@jambirk - please review


broker restart fails

The /var/log/kafka/kafka_init_stdout.log file showed:
No kafka server to stop

for this chef-client failure:
  * service[kafka] action stop

    ================================================================================
    Error executing action `stop` on resource 'service[kafka]'
    ================================================================================

    Mixlib::ShellOut::ShellCommandFailed
    ------------------------------------
    Expected process to exit with [0], but received '1'
    ---- Begin output of /sbin/service kafka stop ----
    STDOUT: Attempting to shutdown Kafka...
    Attempting to shutdown Kafka...
    Error stopping Kafka
    STDERR:
    ---- End output of /sbin/service kafka stop ----
    Ran /sbin/service kafka stop returned 1

    Resource Declaration:
    ---------------------
    # In /var/chef/cache/cookbooks/cerner_kafka/recipes/default.rb

    207: service "kafka" do
    208:   action [:enable, :start]
    209:   supports :status => true, :restart => true
    210: end
    211:

    Compiled Resource:
    ------------------
    # Declared in /var/chef/cache/cookbooks/cerner_kafka/recipes/default.rb:207:in `from_file'

    service("kafka") do
      action [:enable, :start]
      supports {:status=>true, :restart=>true}
      retries 0
      retry_delay 2
      default_guard_interpreter :default
      service_name "kafka"
      enabled nil
      running nil
      masked nil
      pattern "kafka"
      declared_type :service
      cookbook_name "cerner_kafka"
      recipe_name "default"
    end

when attempting to update from 2.2.0 to 2.2.1
I don't know what exactly changed to cause this to start happening, but the cookbook should be more robust and not fail out if it can't stop a broker because it was not detected as running.

I think this might just be a timing issue where the init.d script's sleep time roughly matches the time it takes for the broker process to shutdown.


Fix some warnings on nightly Rust

Cargo is warning about the usage of workspace dependencies where the workspace declaration does not mention default-features but the dependency mentions default-features, so this explicitly turns off default features for cranelift-codegen at the workspace level and removes the explicit default-features = false at the manifest levels.

Looks like cranelift-codegen does not build without the std and unwind features enabled at this time, which are in the default set. Instead of trying to get the "off by default" aspect of this PR I've instead just by-default enabled the default feature for all crates in this workspace. I'll leave it to a future PR to clean this up further if necessary.


Basic UI change

Change color scheme and basic UI of current website. It can be similar to this.

tracked as subtask of #1


support for npm@3 flattened modules

npm introduced flattened modules on 3.x.x versions, since then, grunt-jsdoc needs to be adapted to handle this or it breaks.
Running "jsdoc:src" (jsdoc) task
>> FATAL: Unable to load template: Cannot find module 'node_modules/grunt-jsdoc/node_modules/ink-docstrap/template/publish'
Warning: jsdoc terminated with a non-zero exit code Use --force to continue.

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/27064680-support-for-npm-3-flattened-modules?utm_campaign=plugin&utm_content=tracker%2F294645&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F294645&utm_medium=issues&utm_source=github).

maybe it's my bad.
On my task options I was setting template: 'node_modules/grunt-jsdoc/node_modules/ink-docstrap/template',
This still requires an update on the readme file.

Good point. I though npm 3 was still in beta and had some time left, but it seems it's time to support it.

npm i -g npm already brings it.


Use the system allocator for codspeed benchmarks

Summary
Our benchmarks have been very flaky recently. The one thing that I noticed is that it is mainly due to changes where jemalloc performs reallocations (or moves entire arenas). This randomness is intentional by jemalloc but is kind of hurtful in "reliable" benchmarks.
I haven't found a way to disable the randomness. This PR suggests disabling jemalloc for benchmarks running in codspeed. This has the downside that the codspeed benchmarks are further away from what we run in production. I do think that this is the less worse outcome than us loosing trust in our benchmarks (I'm currently ignoring them because they're just noise).
Codspeed support thread
Test plan
We'll have to test on main to see if the benchmark results are more stable.

I'm going to merge this. We can still revert if it doesn't help to make the benchmarks more stable.


add JSDoc to Vitest code

Clear and concise description of the problem
Vitest functions have little or no documentation in the code, making them difficult to use and adopt.
This is what the editor shows me:

and this is what I hope to see:

Suggested solution
add JSDoc to Vitest code
Alternative
I have to go to the documentation every time I'm not sure how to use a function :/
Additional context
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

hey folks, I'd like to take a look on it to get familiarized with the project. would you guys have any clue?

You can add jsdoc to the type definition here
https://github.com/vitest-dev/vitest/blob/f969fb0f9f0247a7daa2afee8f70de25ea5e123f/packages/expect/src/types.ts#L116-L164
For example,
  /**
   * write something...
   * @example
   *   expect("xxx").toEqual("xxx") // OK
   */
  toEqual: <E>(expected: E) => void

Thanks a lot man!


'Oauth 2.0 Finish page' window not closed...

After auth.  'Oauth 2.0 Finish page' window stays unclosed.
console log : Scripts may close only the windows that were opened by it.
How can I remove this created chrome tab ?

facing same issue.
Page is not closing after sign in with google


Add Support for RPI PICO SDK locking in multithread

Implemented locking for rpi pico sdk per our discussion here:
https://github.com/micro-ROS/micro_ros_raspberrypi_pico_sdk/issues/795

Build status:

Linux
Windows


Tools 181 move uns code to separate module

Moving colors_check, check_not_empty, copy_over_uns to it's own module within uns_functions.
Adding new comment format to these functions.

Thank you! I have yet to go through the code, but I was looking at Brian's and the validator code, it's nice that they have parameters and return value in the comment for each function. Did you want to add that to uns_function.py?  Sorry to have only thought of this just now!

I am getting:

% python flattener.py -m demo LATDF190KNY
Traceback (most recent call last):
File "/Users/jychien/Lattice-Data/lattice-tools/scripts/flattener.py", line 21, in
import flattener_mods as fm
File "/Users/jychien/Lattice-Data/lattice-tools/scripts/flattener_mods/init.py", line 1, in
from flattener_mods.uns_functions import colors_check, report_dataset, check_not_empty, copy_over_uns
ImportError: cannot import name 'report_dataset' from 'flattener_mods.uns_functions' (/Users/jychien/Lattice-Data/lattice-tools/scripts/flattener_mods/uns_functions.py)

I think going forward, might be more straight forward to work on 1 ticket at a time and then merge to main before starting on another ticket. That way, if changes in one ticket affect another, then it would not be as complicated.


Expand docs around the deprecation of former secret syntax

I've been following along the discussion about the deprecation of the secrets syntax with the planned removal for 3.x. I thought it would help to make people feel better informed/have an idea of what to do if the documentation is expanded a bit on that section.
This is my attempt at this, but please feel free to expand/edit etc as needed!

Thanks for the feedback, hopefully it resolved all the outstanding issues!

Will do, just one question: why would the deprecation warning not go into the current docs? as far as I can tell it’s already been deprecated (but not removed) in the current 2.8 version? 🤔

current docs = 3.0 (for now).
There is no secrets there.


Can't get state with react-router. (maybe not working connect())

const mapStateToProps = (state)=>{
    return {
        userData: state.userData
    }
}

export default connect(mapStateToProps, null)(Init);

connected component like this.
btw when I read this.props, it doesn't have userData.
this.props is like below
http://prntscr.com/iypnvj

This is a bug tracker, not a support system. For usage questions, please use Stack Overflow or Reactiflux where there are a lot more people ready to help you out. Thanks!


Missing Email Address

Hi, I tried to setup an alert on a list but it is complaining that
You do not have an e-mail address.
How do we sync the email address from Azure AD?
Is it through Step 4 by adding a $map4 to the powershell?
Please advise.
Thanks,
Alain

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

ID: f079fa08-284c-3f14-be4a-1f32d5b0e7b9
Version Independent ID: 707cbeee-d311-d430-6119-e9ae8b8aeae5
Content: Using Azure AD for SharePoint Server Authentication
Content Source: Enterprise/using-azure-ad-for-sharepoint-server-authentication.md
Service: o365-solutions
GitHub Login: @MSFTTracyP
Microsoft Alias: tracyp

Apologies, I do not have a tenant with O365 to test with emails. However, the default behavior for the AAD application is to include the email claim as http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress.

Using this, you should be able to add another claim type mapping.
$map = New-SPClaimTypeMapping -IncomingClaimType "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name" -IncomingClaimTypeDisplayName "name" -LocalClaimType "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/upn" $map2 = New-SPClaimTypeMapping -IncomingClaimType "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/givenname" -IncomingClaimTypeDisplayName "GivenName" -SameAsIncoming $map3 = New-SPClaimTypeMapping -IncomingClaimType "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/surname" -IncomingClaimTypeDisplayName "SurName" -SameAsIncoming $map4 = New-SPClaimTypeMapping -IncomingClaimType "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress" -IncomingClaimTypeDisplayName "Email" -SameAsIncoming
Please try it out and let us know if this works.

Thanks I was able to include the email using $map4.
However in user profile of a user
The only information that have been mapped are
Account name<EMAIL_ADDRESS>Name<EMAIL_ADDRESS>I was expecting in User profile that First name should have been mapped to "GivenName" ClaimType, Last name: to "SurName" ClaimType and Work Email to "Email" ClaimType. But those fields are blank.

If I manually enter the email address in a user profile, a 2013 workflow email to the creator, and I assume also an alert, will work.
Has anyone set up some sort of user profile sync to sync values such as email, manager, department with Azure AD?

@sngoz There is no built-in capability for SharePoint to sync user profiles with Azure AD. As you pointed out, it works if you add those attributes to the user profile. You will need to build this capability yourself. The two components you need are something to read user profiles from the Graph and to programatically store them into the user profile system in the section "What if My User Doesn’t Come From Active Directory?" (see the end of the article).


Cannot write on port

I can get the ports, connect to them and read data. but I cannot write
writeBytesFromString  and  writeBytesFromUint8List always returns false

.

Actually, write successed. It's due to overlapped mode. Write Operation will return 0 and GetLastErrir will retrun 997.
I wii fix it.

Well Done.
Thank you so much👍


adding ApplicationBeanConfig not using reflections

This implementation only uses Application class to find endpoints. Avoid the need of reflections (and transitively javassist). Also makes it faster since it doesnt needs to scan (again if in a container) and more reliable in OSGi)

Wasn't the goal here to remove the reflections dependency? I'd expect it to be removed from the pom as well.

Can be excluded from users pom bjt BeanConfig still relies on it.

Why was it closed? e.g. with CDI you also don't need reflections.
The performance would be better and the WAR file smaller in many cases!


Achieving good quality conversion to other formats

With what tool did you achieve conversions from resource folder (raviewer) ? a single .jpg converted to all of those color formats. Regular libraries seems ineffective with that tasks

@tgorochowik

Please take a look at imagemagick
https://imagemagick.org/script/convert.php


ZeebeSourceTaskFetcher changes requestTimeout for Zeebe based on its internal backoff algorithm

The setting zeebe.client.requestTimeout must be used as a constant for ActivateJobs requests, but it internally changed by ZeebeSourceTaskFetcher based on backoff algorithm.
This causes many unprocessable requests to Zeebe with very small timeouts such as -1 ms, 100 ms, 200 ms, etc.
Log:
[2024-06-17 06:15:29,637] TRACE Sending activate jobs command for maximal 20 jobs of type sendZeebeMessage with request timeout PT-0.001S (io.zeebe.kafka.connect.source.ZeebeSourceTaskFetcher)

@berndruecker please take a look at fix #224
could you please merge it and build a new image of kafka-connect-zeebe?


More human relative time for seconds.

I noticed while doing sampling the library that seconds strings for relative time weren't really that "good" especially in the french translation so I kind of fixed it for both english and french, if some more experimented people could fix those in the other language files it would also be cool.

This sounds fine to me, but it's going to break the unit tests. Could you update the following files, rebuild, test, and submit another pull request?
./test/lang/en.js
./test/lang/fr.js
./test/lang.js // this will be built by the build script

To test in the browser, fire up ./test/index.html. Don't worry about testing in node.
Thanks!

I made the changes but I still get errors. The first one is concerning the timezone format you assume that it's going to be "PST PST" but due to my location (Paris, France) I get "CET CET", I think this is minor and it all depends on where you test from if you're in a browser or how your time is configured on your server if you test with node. The second one is coming from the "from" test on the "25 days" test in your test you expect to get "25 days" but I get "a month" when running the tests so I don't know wether I should fix that or not.
By the way, just 'til you know I get the same errors on the tests when using the hosted version.

Don't worry about those two. The timezone does assume PST, so i'm not worried about that one failing (Actually, it's good that it fails in a different time zone)
I remember hearing about the other one failing, but I couldn't reproduce. Maybe also a time zone thing, I'm not sure. I'll look into it though. Could you post which number test is failing?

Okay I just pushed two updates, the first one fixes the tests for the new second formatting in french (I also translated the french prefix for future times) and the second one fixes the "25 days" / "a month" ambiguity (I basically changed the "less than" to "less than or equal to" in "relativeTime()"). So, to sum up I only now have 4 errors referring to the timezone issue, here are the guilty ones:

19
26
33
40

Hope this helps!

Awesome, thanks for contributing!
I'll bump up the version number and release on npm soon.
As far as the timezone errors go, I don't think there is an easy way to build that into the unit tests without replicating the code that it's supposed to be testing. I think I'll leave the unit tests broken in all time zones but PST for now, unless a better solution comes to me.


Updated to .NET Framework 4.8 and Akka 1.14.38

No longer needed, as we're running on .NET Standard 2.0 and .NET 6 now


Made a Fully Working Ping Pong game

In this, I have made some complex logic so that the ball moves with different angles on hitting the bars on different angles.
Also it is keeping the records of high scores using local storage

@CoderChirag Take this points :

You are supposed to create a new branch and add your project there , not in master (main) branch.
The folder you made on your fork is inaccesible on github due to errors in git workflow. In case you don't know how it will be fixed refer this https://stackoverflow.com/questions/62056294/github-folders-have-a-white-arrow-on-them
As mentioned, We can't see your files So, your code review will be done after clearing above changes.


JS: More improvements to access paths

Commit-by-commit review encouraged.
Improvements to access paths:

Rely on data flow nodes instead of expressions
Handle destructuring assignments, that is, for let { y } = x, let y be an alias for x.y instead of being the root of its own access path.
Handle local aliasing in some cases, that is, for let y = x.y, let y be an alias for x.y.

Also adds SsaExplicitDefinition.getRhsNode() which is something I've often been missing even if not all definitions have a RHS node. In the future, we could possibly add more cases here, such as for postfix update expressions.
Evaluation is uneventful but as usual this is a stepping stone towards making access paths usable for call graph construction.

The test failures revealed some problems with how I tried to handle local aliasing, so I've rolled back the last commit for now. Hopefully we can land the preceding commits and I'll retry the aliasing and destructuring in a separate PR.

LGTM, but needs conflict resolution.

Removing the last commit fixed the tests but broke the evaluation. I'll tinker with it a bit more.


Limit workflows runs based on file changes

Description
Recently I found myself repeteadly annoyed at how much time it takes to wait for tiny changes on docs to be approved by CI. So I looked up the github actions docs and found that you can indeed limit which workflows are run based on what parts of the code are run.
This PR just tells CI to skip running tests on the code if the only thing that changed is the docs. It might be broken due to workflow dependencies, and there might be a lot more restrictions we could add (i.e: only test examples if the only code that was changed was example code, etc). This is mainly to bring the option up and see if it's suitable :)
cc @Carreau, since I know you've been fighting down CI times lately.

Type of change

[ ] Bug-fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

References

How has this been tested?

[ ] example: the test suite for my feature covers cases x, y, and z
[ ] example: all tests pass with my change

Final checklist:

[ ] My PR is the minimum possible work for the desired functionality
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] If I included new strings, I have used trans. to make them localizable.
For more information see our translations guide.

+1, I think we can do that on bundles as well.