Fixed Issue in Contact page ! #3254 #3257

Hello PR,
Fixed issue number - #3254 & #3257
When you select Dark mode this "Name", "Email", "Subject" & "Message" text boxes color & text color almost blends with the background color,  but now Issue Fixed -

Fixed text color & text boxes gap issue -

Description
[Text boxes color, text color & text boxes gap ]

Type of PR

[x] Bug fix
[x] Feature enhancement
[x] Documentation update
[ ] Other (specify): _______________

Checklist:

[x] I have made this change from my own.
[x] I have taken help from some online resources.
[x] My code follows the style guidelines of this project.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] I have made corresponding changes to the documentation.
[x] My changes generate no new warnings.
[x] I have tested the changes thoroughly before submitting this pull request.
[x] I have provided relevant issue numbers and screenshots after making the changes.

@sailaja-adapa @avantikasankhe  PA please add the level 2 tag as I have solved these[#3254 & #3257] 2 issue properly.

@sailaja-adapa

yeah done @Subhajit-2023-44

Thank you PA @sailaja-adapa

i'm mentor @Subhajit-2023-44


centos6下执行报错

SMBIOS 2.7.0 - table: address: 0xcf42c000, size: 4858
panic: runtime error: index out of range [36] with length 36

goroutine 1 [running]:
github.com/yumaojun03/dmidecode/parser/processor.ParseProcessor(0xc0002ca980, 0xc0002ca980, 0x2, 0xc00023b8a0)
	/data/apps/gopath/pkg/mod/github.com/yumaojun03/dmidecode@v0.1.3/parser/processor/parse.go:47 +0x8ef
github.com/yumaojun03/dmidecode.(*Decoder).Processor(0xc000222280, 0xc00021d904, 0x4, 0xc00021d904, 0x4, 0x4)
	/data/apps/gopath/pkg/mod/github.com/yumaojun03/dmidecode@v0.1.3/decoder.go:195 +0x115

dmidecode输出信息
 dmidecode  -t memory

# dmidecode 2.12
SMBIOS 2.7 present.


Support camel cased partitionKey and rowKey for output binding

When using a JS function, the JSON ends up having camel cased properties. This was already handled in the T1 extension here - https://github.com/Azure/azure-webjobs-sdk/blob/3f4ec78be9f43bb041937425ced00b341883aa42/src/Microsoft.Azure.WebJobs.Extensions.Storage/Tables/Config/TablesExtensionConfigProvider.cs#L157-L169

API change check for Microsoft.Azure.WebJobs.Extensions.Tables
API changes are not detected in this pull request for Microsoft.Azure.WebJobs.Extensions.Tables


Please add cancel(),isListening(),recognizedOneAsync(timeout:MillSeconds) to SpeechRecognition SDK!

We should have a cancel() function when we don't have to send speech to the server.
We want to be able to check weather the sdk is isListening to Mic input, so i can show it on UI
recognizedOneAsync timeout is 15seconds , I want to change it to 10 seconds or 8 seconds.

Another option would be to allow passing a CancellationToken. Either way, being able to cancel would be nice.

Another option would be to allow passing a CancellationToken. Either way, being able to cancel would be nice.

Thanks for these suggestions!

cancel() is an interesting one, as there may be a way to achieve this with existing functionality. It depends a bit on which kind of "cancel" you'd like to do:

If you'd like to "stop now" (don't send any more audio but wait for the result for whatever was sent so far), you can call StopContinuousRecognitionAsync on the SpeechRecognizer (even if you used RecognizeOnceAsync -- yes, this is odd) and it will quickly finish
If you'd like to "abort" (stop sending audio, don't try to get a result, just stop doing everything!), you can retrieve a connection via Connection::FromRecognizer and then call Close on that connection. This will raise a Canceled event and immediately terminate everything.

isListening() is a great idea for ease of use. As a way to achieve this, you can keep track of SessionStarted and SessionStopped events, as these map to when the SDK is capturing audio: when you get a SessionStarted, audio capture has started; when you get a SessionStopped, audio capture has ended.
Can you share more about what you'd like to see with timeouts? A recognition should end before the 15s if a bit of silence (or near-silence) is detected, or if StopContinuousRecognitionAsync is called per the above. Can you tell us more about what your project is doing and what's not behaving the way you'd like it to?

Thank you!

Thanks for these suggestions!

cancel() is an interesting one, as there may be a way to achieve this with existing functionality. It depends a bit on which kind of "cancel" you'd like to do:

If you'd like to "stop now" (don't send any more audio but wait for the result for whatever was sent so far), you can call StopContinuousRecognitionAsync on the SpeechRecognizer (even if you used RecognizeOnceAsync -- yes, this is odd) and it will quickly finish
If you'd like to "abort" (stop sending audio, don't try to get a result, just stop doing everything!), you can retrieve a connection via Connection::FromRecognizer and then call Close on that connection. This will raise a Canceled event and immediately terminate everything.

isListening() is a great idea for ease of use. As a way to achieve this, you can keep track of SessionStarted and SessionStopped events, as these map to when the SDK is capturing audio: when you get a SessionStarted, audio capture has started; when you get a SessionStopped, audio capture has ended.
Can you share more about what you'd like to see with timeouts? A recognition should end before the 15s if a bit of silence (or near-silence) is detected, or if StopContinuousRecognitionAsync is called per the above. Can you tell us more about what your project is doing and what's not behaving the way you'd like it to?

Thank you!

@trrwilson , this cancel() would be also beneficial for us. We have multiple streams sent to transcription in conversation. So cancel() or returntTranscriptSofar() would help on conversations to separate streams with better accuracy. Do you think this can be implemented? Or your approach would be:

on dominant speaker change for past speaker:
StopContinuosRecognition;
StartContinuosRecognition; // not to loose any bits if he was just interrupted.

What do you think?

@trrwilson , this cancel() would be also beneficial for us. We have multiple streams sent to transcription in conversation. So cancel() or returntTranscriptSofar() would help on conversations to separate streams with better accuracy. Do you think this can be implemented? Or your approach would be:

on dominant speaker change for past speaker:
StopContinuosRecognition;
StartContinuosRecognition; // not to loose any bits if he was just interrupted.

What do you think?

What you outline (Stop immediately followed by Start) will do a pretty good job, but I do see the problem you mention--there will be a (very brief) period of time where audio isn't being listened to between the resolution of the Stop and Start calls. That's almost always OK and even expected (a manual "stop" usually implies a user-involved stop event), but in the case of an arbitrary "stop now" that could be right in the middle of a user speaking, that can be a problem.
There's another issue to consider with a "returnTranscriptSoFar" style of approach, though, and that's that the "recognized" style of final results can be very misleading if they don't have a complete utterance (usually as defined by silence). An example of this would be a user saying (and the system stopping): "I'm going to go pick up the groceries and  two pizzas."
In the above, if we let the system detect silence at the end (or stop it at the natural place by any other means), it'll do a good job of using the rest of the sentence to infer the right recognition--you'll get a single final result out of recognized with something that looks correct. If we force it to return two distinct results, however, it loses all that sentence context and will probably end up with two results that aren't quite right, e.g.:

"I'm going to go pick up the groceries in."
"To pizzas."

Understanding your use case a bit better, I wonder if the "recognizing" events (intermediate results that don't require stopping/starting anything) could serve as the indication you need. These happen quite regularly during an utterance. Have you experimented with those and found a gap in what they do?

What you outline (Stop immediately followed by Start) will do a pretty good job, but I do see the problem you mention--there will be a (very brief) period of time where audio isn't being listened to between the resolution of the Stop and Start calls. That's almost always OK and even expected (a manual "stop" usually implies a user-involved stop event), but in the case of an arbitrary "stop now" that could be right in the middle of a user speaking, that can be a problem.
There's another issue to consider with a "returnTranscriptSoFar" style of approach, though, and that's that the "recognized" style of final results can be very misleading if they don't have a complete utterance (usually as defined by silence). An example of this would be a user saying (and the system stopping): "I'm going to go pick up the groceries and  two pizzas."
In the above, if we let the system detect silence at the end (or stop it at the natural place by any other means), it'll do a good job of using the rest of the sentence to infer the right recognition--you'll get a single final result out of recognized with something that looks correct. If we force it to return two distinct results, however, it loses all that sentence context and will probably end up with two results that aren't quite right, e.g.:

"I'm going to go pick up the groceries in."
"To pizzas."

Understanding your use case a bit better, I wonder if the "recognizing" events (intermediate results that don't require stopping/starting anything) could serve as the indication you need. These happen quite regularly during an utterance. Have you experimented with those and found a gap in what they do?

@trrwilson we understand this. But with our heavy testing we experience real life situations when one person is finished, another person is still speaking and up to 12 second (yes, twelve!) transription is not being returned. How ever if during the same time we make a random noise (f.e. apchi or cough) - transcription appears immediately.
I pinged you on LinkedIn as don't have your email or in chat on Microsoft dedicated channel we are in for partners. I'd love to explain in detail privately. We do have NDAs signed :)

@trrwilson we understand this. But with our heavy testing we experience real life situations when one person is finished, another person is still speaking and up to 12 second (yes, twelve!) transription is not being returned. How ever if during the same time we make a random noise (f.e. apchi or cough) - transcription appears immediately.
I pinged you on LinkedIn as don't have your email or in chat on Microsoft dedicated channel we are in for partners. I'd love to explain in detail privately. We do have NDAs signed :)

To summarize the current discussion, please correct as necessary:

The desired functionality of cancel() and isListening() can be achieved as per comment https://github.com/Azure-Samples/cognitive-services-speech-sdk/issues/920#issuecomment-767768144.

For adjusting RecognizeOnceAsync timeout:

There is InitialSilenceTimeoutMs setting (see https://github.com/Azure-Samples/cognitive-services-speech-sdk/issues/502) which can be used to control how much silence the input audio can have from the beginning before RecognizeOnceAsync returns due to no speech in input.
For other than that, you could use PushAudioInputStream or PullAudioInputStream to feed the audio to the SDK library and thus manage how much audio goes in before closing the stream. I've also added a work item to our backlog to make the max duration of RecognizeOnceAsync configurable (currently the setting is service internal only), for consideration in future Speech SDK releases.

@pankopon , am I missing something or InitialSilenceTimeoutMs  is for Java SDK, but not for Javascript / nodejs?

@Vytenis I don't think we have received reports of that kind at least recently. The initial silence timeout is a parameter that's passed directly to the service backend in the cloud where recognition is done.

Closing this item since instructions have been provided to achieve some of the desired functionality by using existing APIs, and there's a work item for additional enhancements (configurable max duration of RecognizeOnceAsync) which will be considered for future Speech SDK releases. We will provide an update here when implementation is done and the release schedule is known. Please open a new issue if you need support on other specific topics.


copy error

when i use function of get_text()，it makes error:  Err(Unknown { .. } - "Unknown error while interacting with the clipboard: failed to read clipboard string") . this error offen happen.  could you resolve it?
my code:
`
pub fn get_selected_text_by_clipboard() -> Result<String, Box> {
use arboard::Clipboard;
use std::{thread, time::Duration};
let old_clipboard = (Clipboard::new()?.get_text(), Clipboard::new()?.get_image());

let mut write_clipboard = Clipboard::new()?;

let not_selected_placeholder = "";

write_clipboard.set_text(not_selected_placeholder)?;

thread::sleep(Duration::from_millis(50));

copy();

thread::sleep(Duration::from_millis(100));

let new_text = Clipboard::new()?.get_text();

println!("new_text: {:?}", new_text);

match old_clipboard {
    (Ok(old_text), _) => {
        // Old Content is Text
        write_clipboard.set_text(old_text.clone())?;
        if let Ok(new) = new_text {
            if new.trim() == not_selected_placeholder.trim() {
                Ok(String::new())
            } else {
                Ok(new)
            }
        } else {
            Ok(String::new())
        }
    }
    (_, Ok(image)) => {
        // Old Content is Image
        write_clipboard.set_image(image)?;
        if let Ok(new) = new_text {
            if new.trim() == not_selected_placeholder.trim() {
                Ok(String::new())
            } else {
                Ok(new)
            }
        } else {
            Ok(String::new())
        }
    }
    _ => {
        // Old Content is Empty
        write_clipboard.clear()?;
        if let Ok(new) = new_text {
            if new.trim() == not_selected_placeholder.trim() {
                Ok(String::new())
            } else {
                Ok(new)
            }
        } else {
            Ok(String::new())
        }
    }
}

}
`

Hi @letscubo. Can I first ask what version of Windows you are on and if you have any non-default locales/text encoding setup? (this shouldn't be an issue but I'd like to confirm) If this is still failing for you I can open a branch with more debug logging if you'd like to try that, which may show more specific details about the error from the system.
Additionally, do you know which of your get_text calls are failing?


fix: built with commit undefined

fix #9

https://github.com/amondnet/now-deployment/commit/7758a86df87900464d1c9e3851e9bd08b863ed9b#commitcomment-36226183


Odd Win64 LLVM Symbol not found error for recursion test symbols

Error and traceback:
LLVM ERROR: Symbol not found: .numba.unresolved$_ZN5numba5tests18recursion_usecases12make_mutual212_3clocals_3e3fooB4v217B38c8tJTIcFKzyF2ILShI4CrgQElQb6HczSBAA_3dEx

Current thread 0x00001ac4 (most recent call first):
  File "C:\Miniconda\envs\testenv\Lib\site-packages\llvmlite\binding\ffi.py", line 152 in __call__
  File "C:\Miniconda\envs\testenv\Lib\site-packages\llvmlite\binding\executionengine.py", line 92 in finalize_object
  ...
  File "D:\a\1\s\numba\tests\test_sort.py", line 860 in check_sort_copy
  File "D:\a\1\s\numba\tests\test_sort.py", line 897 in test_np_sort_int
  ...

See details in AzureCI log
Oddities:

LLVM complains about a unresolved symbol for https://github.com/numba/numba/blob/30df74943112acc2706a98630bba6ca1f310e0c8/numba/tests/recursion_usecases.py#L80-L85. However, the traceback seems to point to an unrelated test at: https://github.com/numba/numba/blob/96989df52cadc9b0e2cf15d08788907de141f36a/numba/tests/test_sort.py#L892-L897.
Failed attempt uses llvmlite with GOT patch (https://github.com/numba/llvmlite/pull/926). Second attempt without the GOT patch passed. However, the problem haven't been successfully replicated manually.

In numba/llvmlite#926, @apmasell mentioned that that was down to mis-tagged packages in conda - do we think the same is the case here?

I don't think it can be down to tags:

It failed with a llvmlite package built against LLVM 14 with the GOT patch, these llvmlite packages were then moved to a different label so that AzureCI wouldn't pick them up.
The same job(s) were rerun and a llvmlite built against LLVM 14 without the GOT patch was in use instead and these jobs passed.


Prevent re-rendering tabs

Why does it need to rerender tabs? I've use Nativebase and it doesnt re-render the tabs once you open it and then decided go back again. How to fix it

@ashrithks any fix to this please?

@ashrithks  yo~ please any update?

Hello,
Native base has introduced this feature,
https://codeburst.io/react-native-parallax-scroll-with-tabs-721feec463c5
<EMAIL_ADDRESS>

Fixed, Update to latest, 0.1.6
check , https://github.com/ashrithks/rn-collapsing-tab-bar/blob/master/Example/CollapseExample.js
for example


Change max_wal_size to only be 60% of WAL disk

To err on the side of caution, we reduce the max_wal_size to be
60% of the WAL disk size. 80% was a bit high and probably where
one would set alerts, so we want to be a bit below that range.

Codecov Report

Merging #63 into master will not change coverage by %.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #63   +/-   ##
=======================================
  Coverage   91.88%   91.88%
=======================================
  Files          17       17
  Lines         912      912
=======================================
  Hits          838      838
  Misses         63       63
  Partials       11       11

Continue to review full report at Codecov.

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


Uncomment all robot tests

Signed-off-by: Vratko Polak<EMAIL_ADDRESS>

Coverage decreased (-0.05%) to 59.193% when pulling 907a863d9c99bca89346587f8348fd28c045eea5 on vrpolakatcisco:uncomment_tests into 340c1c549d8c2b7235a3bc5033da5f0228a3fde7 on contiv:master.


[$500] Dev: Web - Trailing Newlines are not trimmed on the  My Note page.

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

Action Performed:

Open the App and Create a workspace. If not created
Go to #admins
Click on header > Private notes > My note
Press on Notes
Add 3-4 newlines before the actual message; Press Save

Expected Result:
Trailing Newlines should be trimmed on the My Note page.
Actual Result:
Trailing Newlines are not trimmed on the My Note page, and it shows the empty lines on it.
Workaround:
Unknown
Platforms:

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

[ ] Android / native
[ ] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[x] MacOS / Chrome / Safari
[ ] MacOS / Desktop

Version Number: Dev <IP_ADDRESS>
Reproducible in staging?: n
Reproducible in production?: n
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://github.com/Expensify/App/assets/93399543/f0d9be97-4d65-4837-88a3-5e2b5f77a91f
Expensify/Expensify Issue URL:
Issue reported by: @jayeshmangwani
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1694787278356809
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01a1c9388800197ffc
Upwork Job ID:<PHONE_NUMBER>888500736
Last Price Increase: 2023-09-16
Automatic offers:

jayeshmangwani | Contributor | 26743629
jayeshmangwani | Reporter | 26743630

Proposal
Please re-state the problem that we are trying to solve in this issue.
Dev - Trailing Newlines are not trimmed on the  My Note page.
What is the root cause of that problem?
we trim the privateNote only on amount in useState defaul value
https://github.com/Expensify/App/blob/76c1559fb3fbee1d07c8f210b522b63edd03920e/src/pages/PrivateNotes/PrivateNotesEditPage.js#L63
and not trim it when save
https://github.com/Expensify/App/blob/76c1559fb3fbee1d07c8f210b522b63edd03920e/src/pages/PrivateNotes/PrivateNotesEditPage.js#L69-L76
What changes do you think we should make in order to solve the problem?
we need to trim the privateNote before saving
const editedNote = parser.replace(privateNote.trim());

https://github.com/Expensify/App/blob/76c1559fb3fbee1d07c8f210b522b63edd03920e/src/pages/PrivateNotes/PrivateNotesEditPage.js#L69-L76
What alternative solutions did you explore? (Optional)
N/A

Proposal by: @jayeshmangwani
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1694787278356809
Proposal
Please re-state the problem that we are trying to solve in this issue.
Trailing Newlines are not trimmed on the  My Note page.
What is the root cause of that problem?
We are not trimming Private Note Value on Private Notes page, before passing the privateNote value to the API
What changes do you think we should make in order to solve the problem?
We should trim the privateNote Value here before passing to the API
https://github.com/Expensify/App/blob/76c1559fb3fbee1d07c8f210b522b63edd03920e/src/pages/PrivateNotes/PrivateNotesEditPage.js#L69-L70
    const editedNote = parser.replace(privateNote.trim());

What alternative solutions did you explore? (Optional)
none

Proposal
Please re-state the problem that we are trying to solve in this issue.
Trailing Newlines are not trimmed on the  My Note page.
What is the root cause of that problem?
We are not trimming Private Note Value on Private Notes page, before passing the privateNote value to the API
What changes do you think we should make in order to solve the problem?
We should trim the privateNote Value here before passing to the API
https://github.com/Expensify/App/blob/76c1559fb3fbee1d07c8f210b522b63edd03920e/src/pages/PrivateNotes/PrivateNotesEditPage.js#L69-L70
const editedNote = parser.replace(privateNote.trim());

Note This was my proposal that I had added on Slack, so I am commenting on GH, too.
What alternative solutions did you explore? (Optional)
none

I've just reviewed all the proposals - they are all the same (and correct), but in fact the one from @jayeshmangwani was the first (he posted in the slack thread first, then @kbecciv posted it for him here, and then he posted it here himself), so we should proceed with it.
🎀 👀 🎀 C+ reviewed

PR is ready for review
cc: @burczu

@burczu friendly bump for review

@burczu friendly bump for review

@garrettmknight today payment will released so I want to ask if the urgency bonus be considered ?, though PR merged on 4th day but PR was raised after few hours I've assigned but C+ reviewed on 4th day,  TIA
Assigned 6:44 AM

PR raised 11:32 AM , Same day

@jayeshmangwani the urgency bonus is based on the PR getting merged so this one didn't make it.
Summary of payments:

urgency bonus? no
Reporter: @jayeshmangwani $50 paid via Upwork
Contributor: @jayeshmangwani $500 paid via Upwork
Contributor+: N/A

Upwork job: https://www.upwork.com/jobs/~01a1c9388800197ffc

Issue is reproducible on build <IP_ADDRESS>
https://github.com/Expensify/App/assets/93399543/8051633f-d8f1-4769-be95-00471a1d51b8

@kbecciv Video you have attached is an expected behavior; we do not trim new lines between the notes. We trim if the note message has new lines at the start or end of the message

@namhihi237  is right here; this is another issue caused by another PR. It used to work during existng issue's PR merge, but resurfaced after this PR. It looks like this is a regression from this issue.
cc: @burczu @MariaHCD

Okay, I don't have the most context on if that other issue caused this issue so I've asked here: https://github.com/Expensify/App/issues/28599#issuecomment-1775041682

Looks like it is indeed a regression from the other issue: https://github.com/Expensify/App/issues/28599#issuecomment-1775865180
I think we can close this one out.


[MM-15506] Draft of user detail page, routing, and basic actions

Summary
This is a draft of the user info page with basic routing and actions (Reset password, Activate/Deactivate). Code is not final, the intent is to have a working prototype with basic wiring in place for PMs/UX to review.
Ticket Link
https://mattermost.atlassian.net/browse/MM-15506
https://mattermost.atlassian.net/browse/MM-15548
https://mattermost.atlassian.net/browse/MM-15742

Setup Test Server label detected. Spinmint test server created if build succeeds (checks pass and no conflicts with base branch).

Spinmint test server created at: https://i-047105bd888ac8598.test.spinmint.com
Test Admin Account: Username: sysadmin | Password: sysadmin
Test User Account: Username: user-1 | Password: user-1
Internal IP: <IP_ADDRESS>
Instance ID: i-047105bd888ac8598

Spinmint test server destroyed


For DockerToolbox installations, use port forwarding

Porting forwarding port 8888 will enable access on Windows from http://localhost:8888 instead of having to use http://<IP_ADDRESS>:8888

Fixed by PR #64


Verify CAPI v1.5.6 & v1.6.2 support

With Cluster API v1.5.6 and v1.6.2 released, check to make sure we support it.

CAPI 1.6.2 is working for deployments here.


Retrieve description of remote work items in HTML

[Opening the issue for discussion]
ALM Core should be able to return work item descriptions in HTML rather than in their input format (markdown, asciidoc, etc.). This has already been discussed in #98.
For remote work items, the description is currently retrieved in its 'raw' form (ie, Markdown for GitHub and WikitText for JIRA), but with some slight changes in the way the requests are emitted, we could retrieve the description as an HTML fragment, instead.
GitHub
If we use the Accept:application/vnd.github.html header in the requests to get GitHub issues, the response offers a body_html element instead of body and as it names implies, body_html contains the body rendered in HTML rather than how it was input (in Markdown).
Eg:

curl -H "Accept:application/vnd.github.html+json" https://api.github.com/repos/almighty/almighty-core/issues/477

JIRA
For JIRA, we need to append ?expand=renderedFields to the query, and the description field is retrieved in HTML rather than WikiText.
Eg:

curl https://jira.atlassian.com/rest/api/latest/issue/JRA-63602?expand=renderedFields

Would it be interesting to retrieve the rendered, HTML portion of the body, so that we don't have to care about the rendering (and mark the remote work item descriptions as read-only, as mentioned for other fields in #558) ?
Or should we keep the raw descriptions, which makes sense if we need to edit the description of remote items ?

Retrieving HTML and rendering it as such is going to be secure?

@baijum, could you explain in more details which security concerns you have, please ?

@xcoulon Let's say there is a malicious JS embedded in the HTML and it is executed in the context of ALM client side. Well, I am not really a security guy, just a thought.

I understand your concern, but if the source of HTML is GitHub or JIRA
themselves, can't we trust them ? Also, I'm confident it would be possible
to convert the markdown flavor used on GitHub, but I have no idea if JIRA
WikiText/HTML converter is open source or not.
On Fri, Dec 23, 2016 at 2:37 PM, Baiju Muthukadan<EMAIL_ADDRESS>wrote:

@xcoulon https://github.com/xcoulon Let's say there is a malicious JS
embedded in the HTML and it is executed in the context of ALM client side.
Well, I am not really a security guy, just a thought.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/almighty/almighty-core/issues/618#issuecomment-268990737,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAK5RtbOLlkFqyf0r02EwvmiFkvAntjCks5rK86dgaJpZM4LT126
.

--
Best regards,
/Xavier

@xcoulon Maybe Mylyn Confluence Wiki support would work for Jira? https://blog.oio.de/2012/03/21/mylyn-wikitext-an-open-source-library-for-handling-wiki-markup/

@aslakknutsen actually, JIRA can export the issue description in HTML, as I explained in the issue description, so I'm not sure how Mylyn Confluence Wiki would be more relevant. Unless we need to keep the description's raw input, but I'm not sure why we would want to do that.

the go-github library does not support custom media-types to retrieve the HTML rendered body of the issues. An RFE has been opened for that: https://github.com/google/go-github/issues/545


Buttons should be updated

Questions
Answers

Description?
Modules - Buttons should be updated

Type?
improvement

BC breaks?
no

Deprecations?
no

Fixed ticket?
Fixes https://github.com/PrestaShop/PrestaShop/issues/21361

How to test?
please follow https://github.com/PrestaShop/PrestaShop/issues/21361

TEST OK

Thanks @khouloudbelguith & @ngodefroy


Using a formatter

Context: https://github.com/gristlabs/grist-core/pull/594#discussion_r1274875933
Using a formatter tool like prettier would reduce the remarks regarding the code style.
Also husky is a convenient npm package to add git hooks, which would allow us to add a pre-commit one to format the code.

I don't remember why I have closed this issue. I reopen it, I still would like to have such a tool.

As an alternative to prettier (and eslint as well, all-in-one), there exist Biome:
https://github.com/biomejs/biome/


Fixed bug rendering gif using mpl

Fixes an annoying bug that's been causing tests to fail about 80% of the time recently. Not sure why or how it worked sometimes but the previous approach was definitely wrong.

Looking at it, I am surprised it ever worked!

It seems to still sporadically fail but seemingly less often (granted that's based on 3 observations).

Best way to find out how often it is failing now is to merge. So I'll go ahead...


module: add options for configs in HOME, XDG_CONFIG_HOME, XDG_DATA_HOME

Certain applications, such as konsole, store some configuration in XDG_DATA_HOME (~/.local/share/konsole).
Currently, plasma-manger can only define config files in XDG_CONFIG_HOME.
This PR adds 2 new options for defining configurations

plasma.dataFile for configuration files residing in XDG_DATA_HOME.
plasma.file for any configuration files relative to HOME, to handle edge cases where applications put their data somewhere not covered by the other options.

I renamed the original plasma.files option to plasma.configFile (using mkRenamedOptionModule) to be more consistent with the new options and with the home-manager equivalent (xdg.configFile), but I can revert that if you do not want the option name to change.
I couldn't get the check script to run even before my changes, but some manual testing suggests that  the changes are working correctly.

@MatthewCash Thank you for this.
I'm hoping that in the next week I'll get some time to review this.

Since it has been a little while, I just want to check to see if you have any updates. No worries either way :)

@MatthewCash Sorry about the delay (and thanks for the reminder).
I tested this out and everything works as expected.  I think this is a great change.  Thank you so much for the help!


tests, move Get-DbaSuspectPage to 2008R2

as requested in https://github.com/sqlcollaborative/dbatools/pull/2392

very much appreciated! And now I know i gotta modify pester.groups.ps1! 🎉


fix(version): update fabric8-stack-analysis-ui to 0.1.16

There were the following issues with your Pull Request

Commit: 3a73fd5a78158e307217807f379d7d05e1bf2e1b
Your subject line is longer than 50 characters

Guidelines are available at https://github.com/fabric8io/fabric8-ui

This message was auto-generated by https://gitcop.com


Gotta solve for using files in the personas ( for specifying large returns for example in the params )

currently I have it implemented with passing in the resource to the definition
body : (data, params) => return = taxReturnLookUpMap[params.return]

I think that's more of an implementation problem to solve from whatever is consuming saloon. Our examples use static JSON files. There's nothing to say that you couldn't use dynamic JS modules that return objects.

It would be nice to have it baked in to the tool so that the consumer does not have to solve for it.


nerdctl system prune should prune build caches too

Hi! I want to take it a try! Could you assign this issue to me? :heart:

I believe that we should do the same thing for nat on windows


deny unkown fields in txs of sn client

This change is

Previously, yair-starkware (Yair) wrote…
Doesn't this break backward compatibility?

I mean, forward compatibility


Deleted

Description
When using Clickhouse driver in combination with a constraint that all queries have a time-based filter, DBeaver generates an error in the General/Connections/Database hierarchical navigation.  Queries from the navigation panel can safely ignore the need for time-based filters.
DBeaver Version
Community Edition 23.0.3
Operating System
macOS Ventura 13
Database and driver
Hydrolix v3.36
Clickhouse ClickHouse client version <IP_ADDRESS>.
Steps to reproduce
No response
Additional context
No response

Hello @danhydrolix
Could you please provide the log files? You can find instructions here: https://dbeaver.com/docs/wiki/Log-files/. Thank you.

Also, clear steps for reproducing your issue will be helpful.

It's been a while since no update here. If the issue is still actual, please let me know and provide additional information.


stress: flaky test

Discovered in CI for #10089.
--- FAIL: Test_typeArrBadTypes (0.00s)
	stress_test.go:110: Expected line protocol float64 got 0
FAIL	github.com/influxdata/influxdb/stress	2.124s

Addressed in #10173


params should only be converted once

For example
param :foo, type: Todo
the incoming value should only be converted once, not everytime the param is read.
This is a regression from pre 0.7

This issue was moved to reactrb/reactrb#124


Fix k8s api connection leak

Please answer these questions before submitting pull request

Why submit this pull request?
[x] Bug fix
[ ] New feature provided
[ ] Improve performance

Coverage increased (+0.1%) to 12.299% when pulling c89f6b1e82ba4fdc69d6948a380736ff58aca802 on fix/k8s into f2828e771e76e6c426f39b13f81ffa3133a1cb2a on master.


Update the README to follow the new format

See https://github.com/GoogleCloudPlatform/gcloud-meta/issues/3 for what we're hoping to be the shared (mostly) format.

[x] builds/pypi/coveralls
[x] services supported
[x] quickstart
[x] example applications
[x] authorization
[ ] example of bigquery (longer)
[ ] example of datastore (longer)
[ ] example of storage (longer)
[ ] example of pub/sub (longer)
[x] contributing
[x] license

I've added a checkbox list based on the meta-link. Authorization could use some code snippets but how much longer do the examples need to be and what would we like to specifically show off that we aren't currently showing off?

Added authorization clarifications to README. I'd say we are done with this as our examples seem sufficient. @stephenplusplus thoughts?

I'd agree that it all looks good to me. I think the only thing that could be useful is showing dataset.save, as that seems to be the one "big" use missing.

I think we are good here. Feel free to re-open if you have more ideas for how we can improve the README.


Add option to clear single item from recent items list

Sometimes I want to remove one item from the recent item list, right now the only solution is to clear the full list.
The ideal solution would be to add an option to the right click context menu that allows you to remove one item without clearing the full list.
Another idea would be to have a small 'x' all the way at the right of ever item that lets you remove them from the list, this may confuse users though and make them worry they are deleting the file.

Hi,
I've got a PR ready if I can be added as a contributor to make a new branch.
Cheers,
Rob.

@RobbyRobbyRobby the best way to do it would be to fork the repository and open a PR from there.

@RobbyRobbyRobby Just click the fork button. You can clone the copy of the repository from your git account, make changes, and open a pull request across the forks


Refactor code for 0.3.0

The code base has got rather gnarly over the year or so it's been worked on and while the linter has stopped this to a certain extent, there are several areas I'd like to improve to make it easier to work on.
Here are some goals I have in mind for 0.3.0, please comment if you think I've missed anything or these are bad ideas:

[ ] Use 4 spaces for indent, rather than the horrible mix we have.
[ ] Trim down bot.ts to 400 lines, move code to handler classes.
[ ] Decide and explicitly state a convention for function names such as handler/public/private.
[ ] Improve test coverage so that we can stomp out more bugs

see #270 for part of it

@Half-Shot what's left?

Honestly, I'd be happy to close this. We managed to lint all the things.


not working workspaceFolderBasename

not working workspaceFolderBasename
https://code.visualstudio.com/docs/editor/variables-reference
my setting
"local-history.path": "${workspaceFolder}/../historyCode/${workspaceFolderBasename}/",

This is a VSCode variable and it's not supported by this extension.
Use only what is explained for local-history.path in documentation

I want the parameter to be available.
you can do it

Sorry, not for now.
With variable inside folders, and more complex settings like your example, it will break the current logique, so not easy to implement.
(e. g. restore mechanisme...)


Remove obsolete cookie options API

Follow up to https://github.com/aspnet/Security/pull/1285
Remove these obsoleted API in the next major release
CookieAuthenticationOptions
  .CookieName
  .CookieDomain
  .CookiePath
  .CookieHttpOnly
  .CookieSecure
  .ExpireTimeSpan

Not ExpireTimeSpan: https://github.com/aspnet/Security/issues/1293

@HaoK forgot to close this one? :)


make hinoki figure out lifetimes automatically by looking at the dependencies

currently the user has to manually divide/organize factories by their lifetime (the folders application, request, middleware in the case of fragments) and move factories manually between lifetimes/files if their lifetime changes.
it would be really nice if hinoki would figure this out for us !
that is possible:
if a fragment directly or indirectly depends on params or next it is in the middleware lifetime.
if a fragment directly or indirectly depends on req or res it is in the request lifetime.
otherwise it is in the application lifetime.
is this a good idea overall ?
are there any disadvantages/showstoppers when compared to the manual solution ?
does this break other usage patterns of hinoki than our own ?
how to implement this ?
how to transition to this ?
needs a lot more thought !
possible implementation
factories/sources are currently complected with state/values in containers.
decomplect: have hinoki consume an array of sources (which are either "objects containing factories" or "factory factories") as well as an array of lifetimes.
lifetimes will be what lifetime.values currently is.
lifetimes are simply objects of values.
lifetimes manage state.
a value will then be cached in the last lifetime that contains values it directly or indirectly depends on. et voila !
hinoki(sourceS, lifetimeS, nameS);

notes
care has to be taken with fragments that should only exist during a specific lifetime but don't depend on values in that lifetime.
k in fragments is an example.
a solution is to use params or next as an unused "marker-dependency" to force it into the middleware lifetime.
need a solution for promisesAwaitingResolution.
previously in lifetimes. where now ?
as __promises in new lifetimes ?
we could also detect lifetimes ahead of time by looking at the dependencies
and then either add them as metadata to the factories $lifetime or filter factories into the specific lifetimes and use the old lifetime system.
lifetimes only control/influence where and how long the value will be cached.

:+1:

care has to be taken with fragments that should only exist during a specific lifetime but don't depend on values in that lifetime.
k in fragments is an example.
a solution is to use params or next as an unused "marker-dependency" to force it into the middleware lifetime.

fix via metadata e.g. module.exports.someFoo.$lifetime = "middleware" / module.exports.someFoo.$lifetimeIsMiddleware = true

:+1:

this is now present in master and released > 1.0.0-rc.1


Removes Prometheus and adds OTEL for metrics/logs/traces

This PR removes prometheus and adds OTEL for trace/logs/metrics collection.
Type:  Feature
What is the current behavior?
Metrics:

Prometheus is used as a metrics collector.
Prometheus registry is passed to appropriate services and used.
Data is collected and sent to Prometheus backend which connects to dashboards (Grafana) for visualisation.

Logs:

utils/setup_logger is used to format the logs.
uses log::info/trace/debug/warn/error to show logs on CLI.

Traces:

currently not supported

Resolves: #NA
What is the new behavior?

Implemented Analytics that initiates OTEL metrics/logs/traces providers and sets them globally for use.

Analytics is initiated at the top of main function of  madara node.

Each service implements it's own metric services that uses global provider set above.

These services then creates appropriate meter and instruments and register data.

Data is batched and channeled to otel-collector service running externally.

Moreover, otel-collector can be configured to export data to numerous backend and dashboards.

A dashboard created on Signoz is also attached.

NOTE:

Analytics doesn't implement Service like any other client, because :

It's setup is a sync function.
It needs to be started before anything, adding it to current service setup  fails to promise that.

Any logs that were defined like logs::info are changed to use tracing lib like : tracing::info
Appropriate functions are instrumented for traces using #[tracing::instrument()] feature of tracing.
Prometheus Gauge/Counter instruments are replaced with their Otel correspondent.
Addition of #[tracing::instrument()] is incremental, as we use the services more, we'll add more tracing.

Does this introduce a breaking change?
No, but the analytics services currently setup with prometheus will stop working.
Other information
Example of tracing :

Example of new format for logs :

Very cool, I've wanted to move to tracing entirely for some time
I have one small thing to note: i want the logs to be kept as clean as possible if you start madara without just to test it or develop with it, which is why i've done all this https://github.com/madara-alliance/madara/blob/main/crates/node/src/util.rs#L40 which is a bit cursed (for example, I check the log target to show "HTTP" in purple instead of the blue "INFO", I hide the target in some cases (rpc internal server error), add emojis to the warn/errors
and also the HTTP logs show the time elapsed in color etc etc. All of this is very terminal-specific and isn't made to work in production with OTEL stack - it's really for development and devnet uses.
I'd like to keep that behavior by doing a custom tracing terminal format, which would be disabled / hooked up differently for production where the full OTEL stack makes more sense, wdyt @heemankv

Although all the logs are being converted to tracing, if the scope of the PR also includes adding detailed tracing, we might have to add more logs.

As mentioned in the PR description :

Addition of #[tracing::instrument()] is incremental, as we use the services more, we'll add more tracing.

Let's keep adding more logs and tracing incremental, and mark this PR as a start for that effort,
we can do more rounds of PRs to add tracing and logs, after which any new PR needs to handle that by itself.

Although all the logs are being converted to tracing, if the scope of the PR also includes adding detailed tracing, we might have to add more logs.

As mentioned in the PR description :

Addition of #[tracing::instrument()] is incremental, as we use the services more, we'll add more tracing.

Let's keep adding more logs and tracing incremental, and mark this PR as a start for that effort, we can do more rounds of PRs to add tracing and logs, after which any new PR needs to handle that by itself.
WDYT @Mohiiit

cool, my bad

Good changes, looking forwards to being able to use tracing in the codebase :)
Some things still need to be updated. I was being a bit picky with the function instrumentation and the way certain key arguments are skip, but then I saw how many they were and didn't have time to check them all 💀. Imo it might still be better to update these over time but still, maybe un-skip certain arguments.
Some metrics are being cast to more imprecise types, is there a really good reason for this? To me it seems like more of an artefact of the previous metrics. We really want to avoid a scenario were we get some very creative imaginary bugs because of integer overflows in the metrics -yikes!
Also, you should probably update the parsing logic for the log level and collection endpoints.

Thanks for the detailed review @Trantorian1, I have replied to majorly all of your comments, we can start a re-review.

Valid, instrumentation can be made better, this PR focuses on introducing OTEL instrumentation to the code base, we can have multiple (module based maybe) PRs to properly add instrumentation and accordingly we can re-review skip.
Yes the metrics are indeed an artefact of the pre-existing Prometheus metrics, keeping your concerns of overflow in mind, I have implemented all the suggestions provided.
Yes the parsing logic is now much simplified, thanks to your reviews.

Very cool, I've wanted to move to tracing entirely for some time I have one small thing to note: i want the logs to be kept as clean as possible if you start madara without just to test it or develop with it, which is why i've done all this https://github.com/madara-alliance/madara/blob/main/crates/node/src/util.rs#L40 which is a bit cursed (for example, I check the log target to show "HTTP" in purple instead of the blue "INFO", I hide the target in some cases (rpc internal server error), add emojis to the warn/errors and also the HTTP logs show the time elapsed in color etc etc. All of this is very terminal-specific and isn't made to work in production with OTEL stack - it's really for development and devnet uses.
I'd like to keep that behavior by doing a custom tracing terminal format, which would be disabled / hooked up differently for production where the full OTEL stack makes more sense, wdyt @heemankv

Interesting,
The codebase currently checks if the otel_endpoint is available or not,
If it is available then it initialises OTEL, else it just initialises the tracing_subscriber.
We can tweak this logic to initialise our custom format if the OTEL is not being initialised.
I currently use fmt().format to configure and format the logs to the new version this PR introduces. I believe we can try format_event to format the logs as per our custom logic.
Is this close to what you are trying to solve for ?
WDYT @cchudant

@heemankv yes, as long as the devnet / development experience stays nice and clean it's okay

@heemankv yes, as long as the devnet / development experience stays nice and clean it's okay

@cchudant I reworked the tracing logger to work similar to the logging code already written, I hope this satisfies all the requirements.


Update reference.md and README.md to flex 2.1, add gtfs/gtfs-flex 2.1 diagram comparison

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

The only tiny tiny comment I would make is that MobilityData standardized the naming of GTFS extensions, and that therefore we slightly tend to advocate to write "GTFS-Flex" instead of "GTFS-flex".
But this is tiny tiny, and thanks for putting together the proposal and assembling it. Great job!
I've shared a few thoughts in the email I sent you just a bit earlier @thomastrillium, but overall LGTM

Much appreciated and I have actually been thinking about this recently
whenever I type GTFS-flex and GTFS-Fares next to one another :)
Weston could you make this update?
On Fri, Oct 30, 2020 at 12:37 PM Leo Frachet<EMAIL_ADDRESS>wrote:

The only tiny tiny comment I would make is that MobilityData standardized
the naming of GTFS extensions, and that therefore we slightly tend to
advocate to write "GTFS-Flex" instead of "GTFS-flex".
But this is tiny tiny, and thanks for putting together the proposal and
assembling it. Great job!
I've shared a few thoughts in the email I sent you just a bit earlier
@thomastrillium https://github.com/thomastrillium, but overall LGTM
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MobilityData/gtfs-flex/pull/42#issuecomment-719756769,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABZ6ZNHOIBBH3ZURW43YPULSNMIW7ANCNFSM4S2OHVTQ
.

@thomastrillium Capitalization change made to README.md.

@scmcca I don't think I have the creds to merge this PR. Is that something you could go ahead and do?


Fix the SYS_SEMCTL value issue for NetBSD

This hopefully fixes the issue.

Before sending a pull request, please review Contribution Guidelines:
https://github.com/google/syzkaller/blob/master/docs/contributing.md

On Oct 29,  3:38pm<EMAIL_ADDRESS>(Utkarsh Anand) wrote:
-- Subject: Re: [google/syzkaller] Fix the SYS_SEMCTL value issue for NetBSD
| utkarsh009 commented on this pull request.
|
|
|
| >  	mode	int16
| -	nlink	int16
| -	rdev	int16
| +	nlink	int32
| +	rdev	int64
|  	size	int32
|
| @zoulasc I couldn't find the type of off_t and mode_t, so I left them as they are. Thanks for pointing out.
|
This needs to be done exactly right. If it is not things are not going
to work; guessing does not help.
fgrep -r mode_t /usr/src/sys/sys | grep typedef
so mode_t is int32
off_t is int64
etc.
christos

@zoulasc I was supposed to follow along the lines of FreeBSD, and with so much content, there were a few things that I had skipped. This work is not meant to be done by a single person and verification of each and every statement requires a lot of time. There are only a few things that I missed. Kindly cooperate by pointing out the mistakes rather than accusing me of guessing.

I am not accusing you of guessing; I am showing you how to do it.
If I point out all the mistakes, this means that I went through
each of the fields and checked them. At which point I can issue
the pullup myself directly. If you just keep fixing things haphazardly
you are not doing anyone a favor. Someone will eventually have to
verify this for real. Actually fixing partially the struct fields
does more harm than good, because future bugs are less obvious.
The path to success involves patience and careful work...

you are not doing anyone a favor.

 I take orders only when I get paid, sufficiently.

On Oct 29,  4:22pm<EMAIL_ADDRESS>(Utkarsh Anand) wrote:
-- Subject: Re: [google/syzkaller] Fix the SYS_SEMCTL value issue for NetBSD
| > you are not doing anyone a favor.
|
| Of course I'm not doing anyone a favour and I'm not getting paid
| either so there's no point complaining about it. I take orders only
| when I get paid, sufficiently.
You are learning how to do things patiently and correctly by people
who are willing to spend time teaching you. Nobody is being paid,
gives, or takes orders.
christos


JWKS artifact is not published in maven central

While trying to use jwt-jwks-kt I realized that, unlike the ecdsa artifact, it is not published.
Has it only been forgotten, or is there a reason it is not included?
While I can work with a local artifact, it is not ideal when building something in a CI pipeline.
Publishing the current version would be very much appreciated.

JWKS is not yet supported, because it is not yet supported in cryptography-kotlin for all platforms. See discussion here: https://github.com/whyoleg/cryptography-kotlin/issues/16
So if I would publish it now, it would just throw not-yet-implemented exceptions on most platforms.

Thanks for the clarification. I was just getting started and expected the module to be present as well. But it's fine for me to stick with pem keys for the time being.


Question about consolidation behavior

I have moved from CrossRef API consolidation to biblio-glutton with CrossRef database loaded as described in its documentation few weeks ago and met a difference in its behavior.
Earlier with CrossRef API for consolidation, I have received the bibtex data for the translated version of an article using its transliterated original, which is desired. I suppose that the consolidation was based on the author string and year.
@article{15,
  author = {Bersenev, I S and Bragin, V V and Evstyugin, S N and Petryshev, A Yu and Pigarev, S P and Pokolenko, A Yu},
  title = {Evolution of structure and metallurgical properties of iron ore pellets when fluxing with dolomite, JSC Mikhailovsky GOK named after A.V. Varichev},
  journal = {Steel in Translation},
  publisher = {Allerton Press},
  date = {2020-11},
  year = {2020},
  month = {11},
  pages = {788-794},
  volume = {50},
  number = {11},
  doi = {10.3103/s0967091220110054},
  raw = {16. I.S. Bersenev, V.V. Bragin, S.N. Evstyugin i dr. Evolyutsiya struktury i metallurgicheskikh svoistv zhelezorudnykh okatyshei AO «MGOK im. A.V. Varicheva» pri oflyusovanii dolomitom // Stal'. 2020. № 11. S. 11 – 17.}
}

Unfortunately, biblio-glutton now yields a different result:
@article{0,
  author = {Bersenev, I S and Bragin, V V and Evstyugin I Dr, S N},
  title = {Evolyutsiya struktury i metallurgicheskikh svoistv zhelezorudnykh okatyshei AO},
  journal = {MGOK im. A.V. Varicheva» pri oflyusovanii dolomitom // Stal},
  date = {2020},
  year = {2020},
  pages = {11--17},
  volume = {11},
  raw = {I.S. Bersenev, V.V. Bragin, S.N. Evstyugin i dr. Evolyutsiya struktury i metallurgicheskikh svoistv zhelezorudnykh okatyshei AO «MGOK im. A.V. Varicheva» pri oflyusovanii dolomitom // Stal'. 2020. № 11. S. 11 – 17}
}

How can I adjust the consolidation behavior of the biblio-glutton method?
If needed, my OS is Ubuntu 20.04.6 LTS (GNU/Linux 5.4.0-105-generic x86_64) and my java version is 17.0.6.
The consolidation with biblio-glutton is still possible with the data of the translated version:
@article{0,
  author = {Bersenev, I S and Bragin, V V and Evstyugin, S N and Petryshev, A Yu.  and Pigarev, S P and Pokolenko, A Yu. },
  title = {Evolution of Structure and Metallurgical Properties of Iron Ore Pellets When Fluxing with Dolomite, JSC Mikhailovsky GOK Named after A.V. Varichev},
  journal = {Steel in Translation},
  publisher = {Allerton Press},
  date = {2020-11},
  year = {2020},
  month = {11},
  pages = {788-794},
  volume = {50},
  number = {11},
  doi = {10.3103/s0967091220110054},
  raw = {Bersenev, I.S., Bragin, V.V., Evstyugin, S.N., Petryshev, A.Yu., Pigarev, S.P., and Pokolenko, A.Yu., Evolution of structure and metallurgical properties of iron ore pellets when fluxing with dolomite, JSC Mikhailovsky GOK named after A.V. Varichev, Steel in Translation, 2020, vol. 50, no. 11, pp. 788-794.}
}

Hi @oborin1, I have a few questions.
Did you obtain the original version when you process the file through grobid? Or you call directly biblio-glutton?
If in the case of Grobid, could you provide the logs?
I just tested via firstAuthor + title and biblio glutton yield the correct result so we should understand which query was sent to biblio-glutton.
Here my example (just a reference on the query, as the server might be down, as it's a on-demand GC service)
http://<IP_ADDRESS>/glutton/service/lookup?firstAuthor=Bersenev&atitle=Evolution of structure and metallurgical properties of iron ore pellets when fluxing with dolomite%2C JSC Mikhailovsky GOK named after A.V. Varichev
{"URL":"http://dx.doi.org/10.3103/s0967091220110054","resource":{"primary":{"URL":"http://link.springer.com/10.3103/S0967091220110054"}},"member":"1627","score":0.0,"created":{"date-parts":[[2021,3,11]],"date-time":"2021-03-11T15:05:38Z","timestamp":1615475138000},"update-policy":"http://dx.doi.org/10.1007/springer_crossmark_policy","license":[{"start":{"date-parts":[[2020,11,1]],"date-time":"2020-11-01T00:00:00Z","timestamp":1604188800000},"content-version":"tdm","delay-in-days":0,"URL":"http://www.springer.com/tdm"},{"start":{"date-parts":[[2020,11,1]],"date-time":"2020-11-01T00:00:00Z","timestamp":1604188800000},"content-version":"vor","delay-in-days":0,"URL":"http://www.springer.com/tdm"}],"ISSN":["0967-0912","1935-0988"],"container-title":["Steel in Translation"],"issued":{"date-parts":[[2020,11]]},"issue":"11","prefix":"10.3103","reference-count":16,"author":[{"given":"I. S.","family":"Bersenev","sequence":"first","affiliation":[]},{"given":"V. V.","family":"Bragin","sequence":"additional","affiliation":[]},{"given":"S. N.","family":"Evstyugin","sequence":"additional","affiliation":[]},{"given":"A. Yu.","family":"Petryshev","sequence":"additional","affiliation":[]},{"given":"S. P.","family":"Pigarev","sequence":"additional","affiliation":[]},{"given":"A. Yu.","family":"Pokolenko","sequence":"additional","affiliation":[]}],"DOI":"10.3103/s0967091220110054","is-referenced-by-count":8,"published":{"date-parts":[[2020,11]]},"published-print":{"date-parts":[[2020,11]]},"alternative-id":["1284"],"published-online":{"date-parts":[[2021,3,11]]},"content-domain":{"domain":["link.springer.com"],"crossmark-restriction":false},"title":["Evolution of Structure and Metallurgical Properties of Iron Ore Pellets When Fluxing with Dolomite, JSC Mikhailovsky GOK Named after A.V. Varichev"],"link":[{"URL":"http://link.springer.com/content/pdf/10.3103/S0967091220110054.pdf","content-type":"application/pdf","content-version":"vor","intended-application":"text-mining"},{"URL":"http://link.springer.com/article/10.3103/S0967091220110054/fulltext.html","content-type":"text/html","content-version":"vor","intended-application":"text-mining"},{"URL":"http://link.springer.com/content/pdf/10.3103/S0967091220110054.pdf","content-type":"application/pdf","content-version":"vor","intended-application":"similarity-checking"}],"source":"Crossref","type":"journal-article","publisher":"Allerton Press","journal-issue":{"issue":"11","published-print":{"date-parts":[[2020,11]]}},"volume":"50","references-count":16,"issn-type":[{"value":"0967-0912","type":"print"},{"value":"1935-0988","type":"electronic"}],"assertion":[{"value":"12 October 2020","order":1,"name":"received","label":"Received","group":{"name":"ArticleHistory","label":"Article History"}},{"value":"11 March 2021","order":2,"name":"first_online","label":"First Online","group":{"name":"ArticleHistory","label":"Article History"}}],"deposited":{"date-parts":[[2021,3,11]],"date-time":"2021-03-11T15:22:43Z","timestamp":1615476163000},"language":"en","page":"788-794","short-container-title":["Steel Transl."]}

Hi @lfoppiano,
thank you for your reply!
In all cases I started GROBID servers and called the Python client to process the references with the corresponding changes in the server's configuration. (Having tried to get logs within my running GROBID container, I found out that logging is different in grobid.yaml and grobid-full.yaml by default; is it intended?) The grobid logs attached just say that a particular consolidation wasn't successful.
grobid-service.log
If I directly call biblio-glutton with the curl request
curl "http://localhost:8080/service/lookup?biblio=I.S.+Bersenev,+V.V.+Bragin,+S.N.+Evstyugin+i+dr.+Evolyutsiya+struktury+i+metallurgicheskikh+svoistv+zhelezorudnykh+okatyshei+AO+«MGOK+im.+A.V.+Varicheva»+pri+oflyusovanii+dolomitom+//+Stal'.+2020.+№+11.+S.+11+–+17"
it returns
{"message":"Best bibliographical record did not passed the post-validation"}
In cases with the raw string of the translated version (available in CrossRef database), it yields the correct result.
Maybe, the post-validation is the key to the solution I seek?

Ok maybe now I understand better.
Are you processing a PDF document with the original bibliographic data?
Then I think crossref returns the translated version, and with biblio-glutton you don't get any condolidation because of the post-validation. The post-validation is a mechanism to avoid false positive, when results from biblio-glutton and the input are too different, therefore biblio-glutton prefer to abort the consolidation than to return wrong results.

@lfoppiano,
thank you for your answers.
Is LookupEngine.java the place to dig further?
I am processing text files with reference strings, rather than PDFs. (My intention is to process reference lists for publication, so any mistakes introduced by PDFs are annoying.)
Have I understood it correctly that GROBID has no post-validation mechanism when it receives the results from the CrossRef API?

Is LookupEngine.java the place to dig further?

I think so, definitely you can track it down starting from the contoller. Feel free to open a specific issue on the biblio-glutton repo.

I am processing text files with reference strings, rather than PDFs. (My intention is to process reference lists for publication, so any mistakes introduced by PDFs are annoying.)

OK so do you call directly biblio-glutton, without grobid?

Have I understood it correctly that GROBID has no post-validation mechanism when it receives the results from the CrossRef API?

Actually is the other way around, grobid is not responsible on the quality of the retrieval, so it does assume that everything that is returned is the best possible matching. When we wrote biblio-glutton we decided to do not answer, rather than answer something completely wrong. So, I would say it's a feature in biblio-glutton that I'm not sure crossref has 😉


Migrate server from express-graphql to Apollo 2.0

Completes #83, rewrites server.ts and changes parts of both index.ts and server.test.ts for compatibility. Uses the standalone implementation of Apollo and now instead of GraphiQL localhost runs Playground (which is built on top of GraphiQL and adds some useful features).
As far as additional functionality, the query times were very similar to the express server, if tending towards a bit quicker. Using Apollo will allow us to get useful performance tracing right from the Apollo Engine.
The middleware section of server.ts was removed as I figured we could run the server successfully without it, but am open to suggestions.
Love to hear what you think, had good fun with this spike! 😃

Made a few changes:

Enclosed the EthQL server into a class EthqlServer – which in the future can be abstract with multiple concrete implementations if we want to support other HTTP servers going forward.
Removed package-lock.json as we use Yarn.
Added an example query to Playground.

oh man, I'm working on migrating a server from express-graphql to apollo, and this was crazy helpful. thanks!


stop generating button

hi please add a button to stop generating text.

Added.
There is now a "Cancel" button next to the message input when a response is being generated.


Break on error

Why gulp-install do not break on error, when bower/npm fails - https://github.com/slushjs/gulp-install/blob/master/index.js#L46 ?
If dependencies are not installed, what is the point to continue build?

Fixed by #13


Type of substraction result of datetime and timedelta is not timedelta

@Kitsunetic commented on Thu Aug 22 2019
Intellisence recognize the type of (datetime - timedelta) is timedelta
Type of both sum and subtraction operation about datetime and timedelta is datetime
It seems works well if it's add operation but not subtraction operation.
from datetime import datetime, timedelta

now = datetime.utcnow()
time_add = now + timedelta(1) # intellisence thinks it's `datetime`
time_sub = now - timedelta(1) # intellisence thinks it's `timedelta`, but it's `datetime`

Environment data

VS Code version: 1.37.1
Extension version (available under the Extensions sidebar): 2019.8.30787
OS and version: Windows 10 Pro
Python version (& distribution if applicable, e.g. Anaconda): 3.5.4

@karrtikr commented on Mon Aug 26 2019
Please inform if you're using Language Server or Jedi, i.e check the value of python.jediEnabled in settings.json.

I see a related bug in the vscode type inference - with Jedi enabled.
Reproducer:
from datetime import datetime, timedelta
now = datetime.utcnow()
future = datetime(2020, 6, 1)
delta = future - now

VSCode thinks delta is datetime.datetime, but it's a datetime.timedelta object.

Related:

https://github.com/microsoft/python-language-server/issues/860
https://twitter.com/ChristophDeil/status/1257730178517733378

@luabud - could you please x-link the issue or PR with the upstream fix in
https://github.com/microsoft/vscode-python/issues/4983 ?
By upstream do you mean Jedi there or Python language server?

hey @cdeil!
I updated the comment in microsoft/vscode-python#4983 to the PR that fixed it in the Python Language Server.
As for the issue with Jedi, I think it should be addressed upstream as well, so I created an issue in the Jedi repo: https://github.com/davidhalter/jedi/issues/1577.

This was fixed in Jedi.
@karrtikr I might be out of the loop, but why did you move the Jedi issue here? Is this language server now also responsible for Jedi related issues? (Because AFAIK this language server is not about Jedi at all).

The original issue was microsoft/vscode-python#7085; this was a bit ago and the original reporter never responded so I think it may have been transferred to us to look into (the assumption being that it was something in this repo). I do not believe this is an issue here either.

Works here:

So I'll close this issue too.

@davidhalter At the time I could reproduce the issue with Language server, which is why I transferred it here. Seems it was fixed with https://github.com/microsoft/python-language-server/pull/1011


Using openbmctool in automation bucket for collecting FFDC, Checking events, Sensors,

Objective of this epic is to use openbmc-tool in openbmc-test-automation.

[ ] FFDC Collection

[ ] Checking Events

[ ] Sensors (OCC ..)

[ ] Netboot HOST (cool)

[ ] Host reboot

This is done mostly by Steven Sombar. So closing it.


KuzuDB support

Kuzudb is a highly scalable, extremely fast, easy-to-use embeddable graph database and a good replacement of Neo4j. Please consider adding support for Kuzudb https://kuzudb.com/

While we want to add support for additional graph databases in the future, those are not currently on our roadmap.


KAFKA-6647 KafkaStreams.cleanUp creates .lock file in directory it tries to clean

Specify StandardOpenOption#DELETE_ON_CLOSE when creating the FileChannel.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

Whilst this may be a nice to have I remain unconvinced that this will fix the issue.
Looking at clean() in the StateDirectory, it catches any IOExceptions thrown from Utils.delete(). Utils.delete  in postVisitDirectory will throw java.nio.file.DirectoryNotEmptyException so a new StreamsException(e) will be thrown
public synchronized void clean() {
        try {
            cleanRemovedTasks(0, true);
        } catch (final Exception e) {
            // this is already logged within cleanRemovedTasks
            throw new StreamsException(e);
        }
        try {
            Utils.delete(globalStateDir().getAbsoluteFile());
        } catch (final IOException e) {
            log.error("{} Failed to delete global state directory due to an unexpected exception", logPrefix(), e);
            throw new StreamsException(e);
        }
    }

\cc @bbejeck @vvcephei

Left one minor comment.  Plus do we need to add a new test?

This seems related:
https://stackoverflow.com/questions/2479222/problem-with-java-file-locking-mechanism-filelock-etc

Guozhang has different opinion on the approach.
Waiting for discussion to conclude before taking further action.

Any update on this issue?

@gartho We are still pondering what is the best fix for this issue across different file systems. What's your use case and is this a blocker issue for your app?

I’m coming across this issue during integration level testing. I’ve decided to resolve it for now by clearing out the state store folder before I run my tests so it’s not blocking me at present.

Any updates so far?

Any updates?

@gartho  @philippkamps  Sorry for being late on this PR. @tedyu I'd suggest follow the option 2) I've proposed in the JIRA ticket, i.e.
Just another note, for locking purposes, when the apps shutdown cleanly, it is OK to have the lock file left in the state directory since threads are excluding each other not via the ownership of the file but via locking the file handle. So for your case, if you indeed want to clean up the whole directory upon shutting down, then I think there is still a valid point to close all the file channels upon shutting down. For which we can consider:

1) either use StandardOpenOption.DELETE_ON_CLOSE as you did in the PR.
2) or add a new function in the state directory class that closes all the managed file channels upon KafkaStreams.close(); which may be safer than 1) since StandardOpenOption.DELETE_ON_CLOSE is best-effort.

WDYT?

+1

@tedyu What is the status of this PR?

From @guozhangwang 's comment on the JIRA, I thought he acknowledged that lifting the lock up one dir would solve the problem for Windows environment.

Can we discuss how to achieve compatibility with existing locking structure first ?
Thanks

Sure. However, I am not exactly sure what you mean? Can you elaborate?

I meant that, after the move of the lock file, is there any compatibility issue we need to consider.

I didn't find the local repo for the original PR.
Need to open a new one if the approach in current PR is confirmed.

@tedyu Sorry for late reply.

I meant that, after the move of the lock file, is there any compatibility issue we need to consider.

I don't think so. If an app is shut down, it should free all locks. On startup, it can just use the new locking strategy. Or do I miss anything? It would only be an issue, if multiple thread (or different versions) would operate in parallel -- but this case should be be possible on a single machine and thus we should be fine?

bq. but this case should be be possible on a single machine
I guess you meant 'should not be'

Created #5650

@tedyu @mjsax My concern about compatibility is that if we have multiple instances of Streams running on the same machine, say A and B, where A shuts down and upgrades to a new version, it will then try to create the lock file in a different directory (one layer up) while B is still holding locks on the old directory, is it possible that both instances think they now own the task's directory and move on to modify the state (e.g. one still owning the task while the other moves in and "cleanup" the state)?

If you run two KafkaStreams instanced on one machine, you need to configure it with two different state.dir -- thus, both should be isolated and the case you describe cannot happen. Or am I wrong with the assumption about different state.dirs ?

I just started up a small example app that merely created the state.dir.  I ran two instances of the application.
In one case I used the same app-id, and both instances started up fine.  It makes sense as the different instances will end up writing to different task-id directories.
In the other case, I changed the app-id of the second instance and a new directory state.dir/app-id/<task-directories>.
So I think we need more testing to cover the scenario @guozhangwang outlined above.  But it wouldn't hurt to follow @mjsax suggestion to configure with different state.dir entries, but it would be easy to forget to do so.

Today we do not actually enforce different state.dir configs for different instances: imagine if Streams is specified via K8s, where the config values are wired in and are the same. K8s may allocate containers on the same machine.
Thoughts @vvcephei @bbejeck @tedyu @dguy ?

I think for K8s deployment, the state directory should be customized for each streaming app.

@tedyu What is the status of this PR?

See the above comment from Guozhang.
It seems we should consider the case where state.dir is shared between streaming apps

Can we move the discussion to the new PR? Thanks.


Mdata pr

Please provide Issues links to:

Provide test code:

	// get current Window Active , return CMData
	cmdata := robotgo.GetActiveCMData()

	// set Window Active by CMData
	robotgo.SetActiveByCMData(cmdata)

Description
In macos, I cannot get the pid of the wechat child window, so I can only use GetActive and SetActive to operate. However, since there is no secondary definition of the C.MData type, it is difficult to do the intermediate comparison operation, so I submitted This PR hopes to add CMData type return, and also add GetActiveCMData and SetActiveByCMData to facilitate operation.
By the way, since I am using it under macos15, I have to make adjustments based on the branch of https://github.com/go-vgo/robotgo/pull/682

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.0 out of 2 committers have signed the CLA.:x: vcaesar:x: vstvst seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

Closed because of code breaking and conflicts, I think there's must have clearer API and default promise call return value, see the #685.


Overlay service

[x] Portals and PortalHosts
[x] DomPortalHost
[x] Skeleton Overlay service
[ ] Overlay sizing
[x] Overlay global positioning
[ ] Overlay relative positioning
[ ] Overlay scrolling
[ ] Overlay animation

How can we help to close this issue and start interesting components

would it be possible to return the component from the promise after its attached:
line 14 from https://github.com/angular/material2/blob/master/src/core/overlay/overlay-ref.ts
  attach(portal: Portal<any>): Promise<any> {
    return this._portalHost.attach(portal).then(() => {
      this._updatePosition();
    });
  }

would there be any objection to making it:
  attach(portal: Portal<any>): Promise<any> {
    return this._portalHost.attach(portal).then((_comp) => {
      this._updatePosition();
      return _comp;
    });
  }

my current use case is for a right click context menu that I need to bind to after its attached.

@ratscrew I might be possible to play with the generics a bit to cut out some of the any; it's definitely something I want to explore before I consider the portal / overlay stuff to be mature enough to release on its own.

+1 for @ratscrew's issue.. I was also just tearing my hair out trying to figure out how to access the component ref of the resulting portal component when I used the ComponentPortal.
I'm re-writing a set of components that use the dynamicComponentLoader and pass values from a directive to the resulting popup but I can't seem to access the ComponentRef any other way. For the time being I'm using the modded version..

Closing this issue for now, going to track remaining issues in smaller issues.


"CRITICAL:root:twint.feed:Follow:IndexError" when trying to get a user's followers (but I can still get tweets)

Initial Check

[x] Python version is 3.6;
[x] Updated Twint with pip3 install --user --upgrade -e git+https://github.com/twintproject/twint.git@origin/master#egg=twint;
[x] I have searched the issues and there are no duplicates of this issue/question/request.

Command Ran
twint -u jack works. twint -u jack --followers does not.
Description of Issue
I can retrieve a given user's tweets on the command line using twint -u jack, and it works as expected. However, when I try to get the user's followers then Twint fails with the following error:
root@935e3dcb5ef7:~# twint -u jack --followers
CRITICAL:root:twint.feed:Follow:IndexError
root@935e3dcb5ef7:~#

Environment Details
I'm using the provided Dockerfile.

Hi @JesseTG , I happen to run into the same kind of problem. How did you solve this problem?

Hi @JesseTG , I happen to run into the same kind of problem. How did you solve this problem?

I didn't; I used something else.

Hi @JesseTG , I happen to run into the same kind of problem. How did you solve this problem?

I didn't; I used something else.

What's your new method for getting followers or followings? Excepting the API provided by twitter.

Hi @JesseTG , I happen to run into the same kind of problem. How did you solve this problem?

I didn't; I used something else.

Hi, What's your new method for getting followers or followings? Excepting the API provided by twitter.

I used the API provided by Twitter. Takes a lot longer, but it's reliable.

Hi @JesseTG, did you face "RatelimitsError" and how to solve it?

same issue, cant get followers and following
For both get error CRITICAL:root:twint.feed:Follow:IndexError

Same here