ExecutionDAO: new method for counting all tasks

Hello,
I'd like to add (i.e. provide a PR) the following method in ExecutionDAO:
long getTotalNumberOfTaskExecution(final String taskDefName);
Its purpose is to have a way to know the number of task executed/in execution for a given taskDef.
This information might be useful to provide some paging information in the services for example.
What do you think?

Agreed, i could be really useful, not only for the TaskExecution but for all the objects.

This API getInProgressTaskCount(String taskDefName already exists to provide information about the number of tasks currently being executed for a given taskDef.
To get a count of all the task executions for a given taskDef the search API from the indexDAO can be used which would be more generic for searching across tasks.

Closing this issue, since the search API in indexDAO on tasks meets the need for a exhaustive view across all task executions and the existing API in executionDAO provides the count for current executions.
Please reopen if you still feel there is a need for a new API.

Hello @apanicker-nflx,
I would like about this subject, which could be the best approach to have a count for WorkflowDef. May be better to add them to the IndexDAO or perhaps to have a new method in the MetadataDAO. What do you suggest?
Thanks


Add query archive function tests to ledger tests

The ledger example is missing tests for querying the archives. It has a query blocks test but not a query archives test. The complicated part is getting the archives to be created in a local environment, I'm just not sure how to do it or how long/how many resources it would take.

Consider waiting for full ICRC support on the ledger, as querying blocks I believe is coming to ICRC.


Update index diff when staging hunks in diff mode

While staging changes in diffsplit using <leader>gs for stage_hunk the index file doesn't update automatically, requiring an update of the index buffer, say with the e command to see what the new state of the index is.
This is true in fugitive's Gdiffsplit and Gitsigns diffthis.
Though, the buffer IS updated in "fugitive diff" if you use diffput command.

@daephx can you try #502 ?

@lewis6991 Quick response, thanks for addressing this! Yup, that appears to work in diffthis.
Any chance it can also work with fugitive diff? I tend to rely on fugitive more often since it allows me to modify the index directly for really granular staging. I only just recently learned about diffthis and from what I can tell, it appears a lot more like vscode where the index is read-only?

I can have a look, It will just be a case of telling fugitive to update the whole thing.
Note that Gitsigns supports visual selection staging of partial hunks. This will also provide very granular staging.

I only just recently learned about diffthis and from what I can tell, it appears a lot more like vscode where the index is read-only?

Yeah, pretty much. I haven't considered making it modifiable or what the semantics of that would be. I guess every buffer change of the index would require a stage.

Hopefully it proves simple enough!

I guess every buffer change of the index would require a stage
If I understand correctly I'm pretty sure fugitive waits until buffer write before the stage is noticeable in a separate terminal.

Note that Gitsigns supports visual selection staging of partial hunks. This will also provide very granular staging.
That much I'm aware of from use outside the diff mode. I use it very often indeed.
I was more alluding to the hyper-granularity (for lack of a better term) achievable by directly editing diff lines in the index.

If I understand correctly I'm pretty sure fugitive waits until buffer write before the stage is noticeable in a separate terminal.

This makes sense and wouldn't be too hard to implement.

I've updated #502 to update fugitive buffers too. Not sure how robust it is, but seems to work.
Note, if you have unwritten changes in the fugitive buffer then they are wiped away.

Cool, It is updating the fugitive buffer now on my end.

if you have unwritten changes in the fugitive buffer then they are wiped away

Wiping the changes doesn't sound great but is understandable, can those changes be retrieved with an  undo command within the index in the case they have been wiped?
I attempted to force this to check for myself, instead of wiping I get this error.
E5108: Error executing lua ...ite/pack/packer/opt/gitsigns.nvim/lua/gitsigns/async.lua:68: The coroutine failed with this message: vim/shared.lua:0: attempt to index a nil value
stack traceback:
        vim/shared.lua: in function 'list_slice'
        ...e/pack/packer/opt/gitsigns.nvim/lua/gitsigns/actions.lua:151: in function <...e/pack/packer/opt/gitsigns.nvim/lua/gitsigns/actions.lua:131>
stack traceback:
        [C]: in function 'error'
        ...ite/pack/packer/opt/gitsigns.nvim/lua/gitsigns/async.lua:68: in function 'step'
        ...ite/pack/packer/opt/gitsigns.nvim/lua/gitsigns/async.lua:84: in function 'execute'
        ...ite/pack/packer/opt/gitsigns.nvim/lua/gitsigns/async.lua:115: in function 'fn'
        ...te/pack/packer/opt/gitsigns.nvim/lua/gitsigns/repeat.lua:15: in function 'repeat_fn'
        ...te/pack/packer/opt/gitsigns.nvim/lua/gitsigns/repeat.lua:22: in function 'stage_hunk'
        [string ":lua"]:1: in main chunk

A negitive side effect I noticed is that if you have another buffer open when in diff mode, when you stage a hunk it will bug out.
The bottom drawer is a terminal buffer using toggleterm.

@daephx give the latest update a go. I've made it so the index buffers are editable too.

Wow, that's working great, Good job!
I'll definitely keep working with it and see if anything crops up.
As a next set, do you have an idea if it's possible with how gitsigns currently handles hunks to prevent the buffer wiping unstaged changes? It appears fugitive diffput is capable of doing just that, so to me that's a decent sign it's possible.

Ok if fugitive can do it then I'll look into it.

The difference is that gitsigns stage_hunk() actually writes to the index, which causes the buffer to become out-of-date and need a reload, which then wipes the unsaved changes. diffput just applies the changes to the other buffer. As far as I can tell diffput with both fugitive and gitsigns works as it should.

Oh ok I see, so fugitive handles it within vim?
What on your thoughts on the safety of the current implementation? Keeping it "as-is", with the overwrites and let the user handle any issues? A simple undo can get the most basic things back in a pinch anyway. Or perhaps stage_hunk could providing a warning in the echo area and/or preventing further stages if there are unwritten changes to the index buffer?

@daephx I've worked on #502 a bit more. It no longer wipes unsaved changes and brings up a warning prompt instead. Can you give it a look?

@lewis6991 Thanks for the heads up! It's a good compromise given the limitation.
I just tested it; given the options [O]k and [L]oad, is it intended for [O] to do nothing? Just serve as a confirmation, much like saying No or Yes respectively? Other then that slight confusion it appears to work as expected. 👍


Add Extraction Support for SPTimerJobState

As listed in the Parity with SharePointDSC page, we need to add support in ReverseDSC to be able to extract values out of the SPTimerJobState Resource.

Added in <IP_ADDRESS> + New SkipTimerJobState switch


Subclass of ErrorHandlingDeserializer not detected (inconsostent behaviour)

Hi all,
I am not sure if this is a bug or the expected behaviour but it might be a bug in my eyes. We want to use the ErrorHandlingDeserializer to catch DeserialzationExceptions. But as we are using the same setup in many applications I wrote a CustomDeserialzer which has the ErrorHandlingDeseralzer as Super-Class and just adds some config options.
public class CustomDeserialzer<T> extends ErrorHandlingDeserializer<T> {

	@Override
	public void configure(Map<String, ? extends Object> configs, boolean isKey) {
		Map<String, Object> tmp = new HashMap<>(configs);

		tmp.put(ErrorHandlingDeserializer.KEY_DESERIALIZER_CLASS, String.class.getName());
		tmp.put(ErrorHandlingDeserializer.VALUE_DESERIALIZER_CLASS, JsonDeserializer.class.getName());
		tmp.put(JsonDeserializer.VALUE_DEFAULT_TYPE, Name.class.getName());

		super.configure(tmp, isKey);
	}

}

I set the CustomDeserialzer as value.deserializer in the following application.yaml.
spring.cloud:
  stream:
    function.definition: process
    bindings:
      process-in-0:
        destination: topic1
        group: group1
        consumer:
          useNativeDecoding: true
    kafka:
      binder:
        autoCreateTopics: true
      bindings:
        process-in-0:
          consumer:
            autoCommitOnError: true
            enableDlq: true
            dlqName: dead-out
            configuration:
              value.deserializer: com.example.demo.serde.CustomDeserialzer

The KafkaMessageListenerContainer uses the method checkDeserializer (see referenced Code below) to check if the Deserialzer is Type of ErrorHandlingDeserializer. Only in case of true, the KafkaMessageListenerContainer checks for an Deserialzation-Exception in the Header. But this is not happening in our case.
https://github.com/spring-projects/spring-kafka/blob/9776c42b40fa4fbeae6309336f82a1a5e722a914/spring-kafka/src/main/java/org/springframework/kafka/listener/KafkaMessageListenerContainer.java#L918-L922
If the deser parameter is instanceof Class, the check ErrorHandlingDeserializer.class.isAssignableFrom((Class<?>) deser) will returne true, if the deser object is a Sub-Class of the ErrorHandlingDeserialzer.
But the value.deserializer: com.example.demo.serde.CustomDeserialzer is not passed as Class but as String. But the check deser.equals(ErrorHandlingDeserializer.class.getName()) will NOT return true, in case of a Deserialzer which uses the ErrorHandlingDeserializer as Super-Class.
It looks like the method is inconsostent because handing parameter "com.example.demo.serde.CustomDeserialzer" as String the return value will be false and handing the CustomDeserialzer as Class<?> the return value is true.
A possible solution would be to get a Class-Object with Class.forName(deser) and also check with ErrorHandlingDeserializer.class.isAssignableFrom on that object like below
private boolean checkDeserializer(Object deser) {
			return deser instanceof Class
					? ErrorHandlingDeserializer.class.isAssignableFrom((Class<?>) deser)
					: deser instanceof String && ErrorHandlingDeserializer.class.isAssignableFrom(Class.forName(deser));
		}

Best regards
Philipp

As a work-around (if the value deserializer is used by all bindings), use
spring.kafka.consumer.value-deserializer=...

(notice -) instead of setting it at the binding level, then Spring Boot will convert your class name to a class.


fixed proxy config path

Fixed serve proxy.conf.json path. The documentation wants us to create the config file next to the package.json (project root), not the src subdirectory. So, the proxyConfig needs that path.

Can you please rebase and fix your commit message? It should be something along
docs: fix proxy config paths

Superseded  by
https://github.com/angular/angular-cli/pull/12071


spring-5-reactive-security: fixing EmployeeControllerIntegrationTest

Hi,
it seems that com.baeldung.reactive.webflux.EmployeeControllerIntegrationTest in the project spring-5-reactive-security is red at the moment:
cd spring-5-reactive-security
mvn test -Dtest=EmployeeControllerIntegrationTest -Dgib.enabled=false

=>
[ERROR] Failures:
[ERROR]   EmployeeControllerIntegrationTest.givenEmployeeId_whenGetEmployeeById_thenCorrectEmployee:46 Status expected:<200> but was:<404>
...
[ERROR]   EmployeeControllerIntegrationTest.whenGetAllEmployees_thenCorrectEmployees:71 Status expected:<200> but was:<404>

Changing the classes property of the @SpringBootTest should fix it:
=>
[INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 28.8 s - in com.baeldung.reactive.webflux.EmployeeControllerIntegrationTest

@cror  Thanks, merged.


Works on 4.2.x but no other operating system

Hi,
So I've gotten this snippet to work on an android phone (Galaxy S3 running 4.1.2):
    nfc.addNdefListener (
        function (nfcEvent) {
            var text = document.querySelector('.writeEncoded'));
            var link = ndef.textRecord(text);
            nfc.write([link], function(){
                    alert('Success!');
                },
                function(){
                    alert('I\'m sorry, something went wrong, please try again');
                }
            );
        },
        function () {
            alert("Waiting for NDEF tag");
        },
        function (error) {
            alert("Error adding NDEF listener " + JSON.stringify(error));
        }
    );

For some reason it doesn't work on a Samsung Galaxy Tab 4 running 5.0.2, it also doesn't work on a Nexus 7 running either 4.4.4 or 5.1.
Other information: the alert for successfully adding the listener is called, but when I touch my nfc tags (mifare classic and mifare ultralight) to the reader it only gives me a response on the phone.  I've tested the readers and tags on the tablets, other apps can interact with the same tags.
Any direction would be much appreciated. Thank you

it does work on a Nexus 7 running 4.2.

Mifare Classic tags don't work as NDEF tags on devices with Broadcom NFC chips. The original Nexus 7 was OK, I'm not sure about the Nexus 7 2013. Some of the Galaxy devices might be a problem too.
You could try adding nfc.addTagDiscoveredListener to see if you can read the tag id on devices that won't read the tag.
https://github.com/don/phonegap-nfc-issue-247/blob/master/www/js/index.js#L68-L81
If a tag is not formatted as NDEF, you'll need nfc.addNdefFormatableListener to read the tag and write data to it.
https://github.com/don/phonegap-nfc-issue-247/blob/master/www/js/index.js#L83-L105
It's fine to have multiple listeners, Android will call the most specific one for the tag that's scanned.
Other things to try are

Run adb logcat and look for error when you scan the tag
Open chrome://inspect on your computer and look for JavaScript errors on the device

I've done a few things now, (I'm guessing the important one is 5)

I downloaded an nfc reader app, all my devices can read and write to both mifare classic and mifare ultralight

I've added nfc.showSettings, nfc is definitely accessible on my device

I've added tagDiscovered, ndef formatable, and nfc.enabled to my program and tested on devices running 4.4.4, 5.0.2, and 4.2.2.  nfc.enabled returns true, all listener's success functions are returned, but the only device that does anything when a tag is brought is the one running 4.2.2

I removed Ndef listener, for good measure, and tested the same 3 operating systems.  Both discovered and formatable listeners were added, but when a tag was brought, only 4.2.2 was able to find the tag at all.

using chrome://inspect the log says NFCPlugin initialized, then returned 2 errors on nfcEvent
Refused to evaluate a string as JavaScript because 'unsafe-eval' is not an allowed source of script in the following Content Security Policy directive: "default-src * 'unsafe-inline'". Note that 'script-src' was not explicitly set, so 'default-src' is used as a fallback.
and
Uncaught EvalError: Refused to evaluate a string as JavaScript because 'unsafe-eval' is not an allowed source of script in the following Content Security Policy directive: "default-src * 'unsafe-inline'".

when using chrome://inspect on the 4.2.2 device I'm not even shown the app running on my device

Here is the logcat result from the tablet running 4.4.4
D/NfcDispatcher(  757): dispatch tag: TAG: Tech [android.nfc.tech.MifareUltralight, android.nfc.tech.NfcA, android.nfc.tech.Ndef] message: NdefMessage [NdefRecord tnf=1 type=54 payload=02656E32763570636E686D]
D/NfcPlugin( 5406): onPause Intent {  }
D/NfcPlugin( 5406): stopNfc
D/NfcDispatcher(  757): Set Foreground Dispatch
I/ActivityManager(  494): START u0 {act=android.nfc.action.TECH_DISCOVERED flg=0x24000000 cmp=org.ali75.form/.NFC_Form (has extras)} from pid -1
W/ActivityManager(  494): startActivity called from non-Activity context; forcing Intent.FLAG_ACTIVITY_NEW_TASK for: Intent { act=android.nfc.action.TECH_DISCOVERED flg=0x24000000 cmp=org.ali75.form/.NFC_Form (has extras) }
D/NfcPlugin( 5406): onNewIntent Intent { act=android.nfc.action.TECH_DISCOVERED flg=0x24000000 cmp=org.ali75.form/.NFC_Form (has extras) }
I/NfcDispatcher(  757): matched TECH override
D/NfcPlugin( 5406): onResume Intent { act=android.nfc.action.TECH_DISCOVERED flg=0x24000000 cmp=org.ali75.form/.NFC_Form (has extras) }
D/NfcDispatcher(  757): Set Foreground Dispatch
D/NfcPlugin( 5406): parseMessage Intent { act=android.nfc.action.TECH_DISCOVERED flg=0x24000000 cmp=org.ali75.form/.NFC_Form (has extras) }
D/NfcPlugin( 5406): action android.nfc.action.TECH_DISCOVERED
D/NfcPlugin( 5406): android.nfc.tech.MifareUltralight
D/NfcPlugin( 5406): android.nfc.tech.NfcA
D/NfcPlugin( 5406): android.nfc.tech.Ndef
V/NfcPlugin( 5406): var e = document.createEvent('Events');
V/NfcPlugin( 5406): e.initEvent('ndef');
V/NfcPlugin( 5406): e.tag = {"isWritable":true,"id":[4,33,-51,-126,116,64,-127],"techTypes":["android.nfc.tech.MifareUltralight","android.nfc.tech.NfcA","android.nfc.tech.Ndef"],"type":"NFC Forum Type 2","canMakeReadOnly":true,"maxSize":137,"ndefMessage":[{"id":[],"type":[84],"payload":[2,101,110,50,118,53,112,99,110,104,109],"tnf":1}]};
V/NfcPlugin( 5406): document.dispatchEvent(e);
I/chromium( 5406): [INFO:CONSOLE(0)] "Refused to evaluate a string as JavaScript because 'unsafe-eval' is not an allowed source of script in the following Content Security Policy directive: "default-src * 'unsafe-inline'". Note that 'script-src' was not explicitly set, so 'default-src' is used as a fallback.
I/chromium( 5406): ", source:  (0)
I/chromium( 5406): [INFO:CONSOLE(1070)] "Uncaught EvalError: Refused to evaluate a string as JavaScript because 'unsafe-eval' is not an allowed source of script in the following Content Security Policy directive: "default-src * 'unsafe-inline'".
I/chromium( 5406): ", source: file:///android_asset/www/cordova.js (1070)
D/NativeNfcTag(  757): Tag lost, restarting polling loop

and the logcat from 4.2.2
D/NfcDispatcher(  754): dispatch tag: TAG: Tech [android.nfc.tech.MifareUltralight, android.nfc.tech.NfcA, android.nfc.tech.Ndef] message: NdefMessage [NdefRecord tnf=1 type=54 payload=02656E32763570636E686D]
I/ActivityManager(  477): START u0 {act=android.nfc.action.TECH_DISCOVERED flg=0x24000000 cmp=org.ali75.form/.NFC_Form (has extras)} from pid -1
D/NfcPlugin( 5500): onPause Intent {  }
D/NfcPlugin( 5500): stopNfc
D/NfcDispatcher(  754): Set Foreground Dispatch
D/NfcPlugin( 5500): onNewIntent Intent { act=android.nfc.action.TECH_DISCOVERED flg=0x24000000 cmp=org.ali75.form/.NFC_Form (has extras) }
W/ActivityManager(  477): startActivity called from non-Activity context; forcing Intent.FLAG_ACTIVITY_NEW_TASK for: Intent { act=android.nfc.action.TECH_DISCOVERED flg=0x24000000 cmp=org.ali75.form/.NFC_Form (has extras) }
D/NfcPlugin( 5500): onResume Intent { act=android.nfc.action.TECH_DISCOVERED flg=0x24000000 cmp=org.ali75.form/.NFC_Form (has extras) }
D/NfcPlugin( 5500): parseMessage Intent { act=android.nfc.action.TECH_DISCOVERED flg=0x24000000 cmp=org.ali75.form/.NFC_Form (has extras) }
D/NfcPlugin( 5500): action android.nfc.action.TECH_DISCOVERED
D/NfcPlugin( 5500): android.nfc.tech.MifareUltralight
D/NfcPlugin( 5500): android.nfc.tech.NfcA
D/NfcPlugin( 5500): android.nfc.tech.Ndef
V/NfcPlugin( 5500): var e = document.createEvent('Events');
V/NfcPlugin( 5500): e.initEvent('ndef');
V/NfcPlugin( 5500): e.tag = {"isWritable":true,"id":[4,33,-51,-126,116,64,-127],"techTypes":["android.nfc.tech.MifareUltralight","android.nfc.tech.NfcA","android.nfc.tech.Ndef"],"type":"NFC Forum Type 2","canMakeReadOnly":true,"maxSize":137,"ndefMessage":[{"id":[],"type":[84],"payload":[2,101,110,50,118,53,112,99,110,104,109],"tnf":1}]};
V/NfcPlugin( 5500): document.dispatchEvent(e);
D/NfcDispatcher(  754): Set Foreground Dispatch
I/NfcDispatcher(  754): matched TECH override
D/dalvikvm( 5500): GC_CONCURRENT freed 2214K, 23% free 8153K/10512K, paused 4ms+3ms, total 33ms
D/NativeNfcTag(  754): Tag lost, restarting polling loop

Any updates on this?

It looks like the Content Security Policy (CSP) for you app is causing the plugin to fail.
[INFO:CONSOLE(0)] "Refused to evaluate a string as JavaScript because 'unsafe-eval' is not an allowed source of script in the following Content Security Policy directive: "default-src * 'unsafe-inline'". Note that 'script-src' was not explicitly set, so 'default-src' is used as a fallback.

I just followed these instructions and my Nexus 5X running Android 7.0 can scan tags with NDEF messages. https://github.com/chariotsolutions/phonegap-nfc/blob/master/doc/GettingStartedCLI.md
The CSP from the default generated app is very permissive
        <meta http-equiv="Content-Security-Policy" content="default-src 'self' data: gap: https://ssl.gstatic.com 'unsafe-eval'; style-src 'self' 'unsafe-inline'; media-src *; img-src 'self' data: content:;">

See the Cordova docs for more info on how to customize the CSP for your app https://github.com/apache/cordova-plugin-whitelist/blob/master/README.md#content-security-policy

Also see https://github.com/chariotsolutions/phonegap-nfc/issues/249#issuecomment-236559032 for more CSP info


Investigate/remedy suspect code in EntryVersionHelper

Describe the bug
The code near this line in EntryVersionHelper looks odd:
https://github.com/dockstore/dockstore/blob/c59924138e1490a71afc0a889fc00777580650fe/dockstore-webservice/src/main/java/io/dockstore/webservice/helpers/EntryVersionHelper.java#L285
The adjacent code appears to be intended to compute a path, preferring the workflow version path and using the workflow path as a backup, but instead, both the workflowPath and workflowVersionPath variables are assigned the same value (workflowVersion.getWorkflowPath()).  As a result, some of the following code has no functional effect.
Investigate and fix if necessary.
Expected behavior
Whatever we determine is correct.
┆Issue is synchronized with this Jira Story
┆fixVersions: Dockstore 1.13
┆friendlyId: DOCK-2071
┆sprint: 93- Ursula
┆taskType: Story

Looked at the code again; looks good. Difficult to do end-user testing for this.


Backport 2.1: Use "#!/usr/bin/env perl" as shebang line.

Backport of #1533 for 2.1 branch.

retest

I've tested the majority of the scripts, and am labelling this as 'ready for merge'.


new to Git hub

im new to Github,i want to use this MaterialView pager material design into my project i tryd to import it into android studio,but it shows some error

Please provide more info about your problem. How are you importing the library? What is the error? etc.
No body will be able to help you without any information.
:+1:

I'm using android studio
I imported the MaterialViewPager-master by
file->new->import project
and the error shown is
Gradle DSL method not found:'android()'
possible causes:
Error:(39, 0) Gradle DSL method not found: 'android()'
Possible causes:The project 'MaterialViewPager-master' may be using
a version of Gradle that does not contain the method.
The build file may be missing a Gradle plugin.
On Tue, Aug 11, 2015 at 4:48 PM, Devesh Khandelwal<EMAIL_ADDRESS>
wrote:

Please provide more info about your problem. How are you importing the
library? What is the error? etc.
No body will be able to help you without any information.
[image: :+1:]
—
Reply to this email directly or view it on GitHub
https://github.com/florent37/MaterialViewPager/issues/135#issuecomment-129841678
.

There is no need to do that. Just add the following to your build.gradle(:app) file:
compile ('com.github.florent37:materialviewpager:1.1.0@aar'){
    transitive = true
}

And then perform a Gradle sync. The library should be automatically added to your project.
You can now use the import statements. :smiley:

1)i downloaded MaterialViewPager-master.
2)file->new->import project //i have a doubt weather should import as module or project
3)in the MaterialViewPager-master there was build.gradle i pasted
compile ('com.github.florent37:materialviewpager:1.1.0@aar'){
transitive = true
}
4)i performed a Gradle sync
5)i get an error Error:(3, 0) Cannot invoke method compile() on null object

I think you are not getting my point. You do not need to import the project. Just add what I told you above in the gradle build file of your app, NOT MaterialViewPager, and you'll be good to go.

Thank you again sir,but here comes an another error,plz give me step by step process so it will be usefull

You are going in the right direction. Tell me the error, the error is not visible in the snapshot. :+1:

Thank you again sir,but here comes an another error,plz give me step by step process so it will be usefull
1)i created anew project
2)i imported d module
3)in bulid i inserted
compile ('com.github.florent37:materialviewpager:1.1.0@aar'){
transitive = true
}

Thank you again sir,but here comes an another error,plz give me step by step process so it will be usefull
1)i created anew project
2)i imported d module
3)in bulid i inserted
compile ('com.github.florent37:materialviewpager:1.1.0@aar'){
transitive = true
}

Well, it should work as now you've done the right steps. Can you please, put up your project on a repo, so I can compile myself?

actually sir im new to git hub i have created a repo but how to add my project,https://github.com/Rahulkishanm/celebrationsapp buti doono how to insert my project into it

https://gist.github.com/Rahulkishanm/3f2c929b8c904a5a60f9

I can't run your app like this, you have to push your app into a repository, not a gist.
I have seen that you have created a repo in your account, now you just need to push your app's code into that repository.

I don't know how to ad my project into my repo..
I know to store it in drive and share my link
On Thu, Aug 13, 2015 at 2:44 PM, Devesh Khandelwal<EMAIL_ADDRESS>
wrote:

I can't run your app like this, you have to push your app into a
repository, not a gist.
I have seen that you have created a repo in your account, now you just
need to push your app's code into that repository.
—
Reply to this email directly or view it on GitHub
https://github.com/florent37/MaterialViewPager/issues/135#issuecomment-130587469
.

https://drive.google.com/folderview?id=0B1WFXRJ-fFkcfmNFOW5TZzhOQUlGd2RUd082LXpzRUk5WTczT2FyUmJkc1N5QkRjck5pbTA&usp=sharing
this is my project....imm new to git hub so I don't know how to add into
repo...plz share me some knowledge
On Thu, Aug 13, 2015 at 3:13 PM, Rahul kishan<EMAIL_ADDRESS>
wrote:

I don't know how to ad my project into my repo..
I know to store it in drive and share my link
On Thu, Aug 13, 2015 at 2:44 PM, Devesh Khandelwal <
<EMAIL_ADDRESS>wrote:

I can't run your app like this, you have to push your app into a
repository, not a gist.
I have seen that you have created a repo in your account, now you just
need to push your app's code into that repository.
—
Reply to this email directly or view it on GitHub
https://github.com/florent37/MaterialViewPager/issues/135#issuecomment-130587469
.

Found the error, there is comma [,], in your project's build.gradle, right after classpath statements. Remove the comma and it should sync properly.

@Rahulkishanm If your issue is resolved, then please close this issue.
Thank You.

sir it dint wrk...plz provide me step by step process sir
On Fri, Aug 14, 2015 at 2:25 PM, Devesh Khandelwal<EMAIL_ADDRESS>
wrote:

@Rahulkishanm https://github.com/Rahulkishanm If your issue is
resolved, then please close this issue.
Thank You.
—
Reply to this email directly or view it on GitHub
https://github.com/florent37/MaterialViewPager/issues/135#issuecomment-131030621
.

Did you try removing that comma [ , ] I mentioned about in your Celebrations project?

Error:(3, 0) Cannot invoke method compile() on null object

Long discussions are not good for here. Can you please join Gitter, so that I can help you in detail?


Added some documentation on coroutines

I was trying to understand the coroutine code in order to make some additions to it, and in the process had added some of my own documentation. I think it's all correct, but it's my own guesswork.

@jameysharp you're welcome. What you've told me should help me fix things up a bit further. The commit message is indeed a mess - I rebased over a large range of commits, so I'll try to clean that up.
I'm a little new to GitHub pull request workflow - should I squash again and do a force push?

A pull request is pretty unusual as git workflows go. It's the only case I can think of where a force push is a good idea. So yes, you can either squash again or git commit --amend, then force push. Thanks!

Okay, I think I've integrated in everything that you noted (I'm checking your notes again now), and hopefully understood the details properly this time.


[BDG-FORMATS-20] Add readme

Fixes #20

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/bdg-formats-prb/114/
Test PASSed.

Wonderful! Merged. Thanks @heuermh.


[backport 2.7] Fix possible close_notify/ClientHello confusion

This is the 2.7 backport of #3050

@gilles-peskine-arm Thanks for catching the unintended and inconsistent change. I now aligned the timeout with the 2.16 branch for that entire series of tests, in a separate commit for clarity. Please review again.


Draw the loss curve

@xuhongzuo . I want to use pd.DataFrame to save loss, loss_oc and val_loss in each epoch, and save it as a csv file. Could you add the code for this function?

I printed these loss values after each training epoch.
You could do this personalized requirement by yourself.
issue closed.


Web RTC issue

By implementation WebRtc we have found that the following socket event doesn’t work -->
1)socket.on('appointment:status')
2)socket.on('appointment:messages')
We suppose that the issue is in this part of code on the server in file socket.js -->
1)http://prntscr.com/ibg9dx
2)http://prntscr.com/ibg9j9
3)http://prntscr.com/ibg9os
As the socket event emits doesn’t work, we suppose that the root of issue is in the file db.js, where there is a selection from Database. Could you please check it from your side as it is very important for our work on WEBRTC module.
Here in socket.emit('appointment:messages') --> http://prntscr.com/ibgbcp --> we give the following data for listening on the server, is our structure right?
Currently, these issues block our further work with WebRTC. This is urgent.
Related issue: https://github.com/PulseTile/PulseTile-React/issues/115

thanks @anna-otrokhova
See this related update here
https://github.com/PulseTile/PulseTile-React/issues/115#issuecomment-365002711
= TURN server needs reinstalling

Update from Alexey re
stun:<IP_ADDRESS>:3478
username: idcr
password: E3rtvo6fkghFrt6
when I run apt-get install coturn it asked me what to do with existing config
I kept it and then just check turnserver.conf and turnserverdb.conf
then check turn to connect

@tony-shannon
Excuse me, Tony. Could you please specify if you finished configuration of WEBRTC module on backend side (TURN server installation)?
And could you please clarify what changes we should do in videochat.js ?
Thank you in advance

Please revisit the related issue you raise on the PulseTIle React repo
THanks
Tony
On 21 February 2018 at 11:03, Anna Otrokhova<EMAIL_ADDRESS>wrote:

@tony-shannon https://github.com/tony-shannon
Excuse me, Tony. Could you please specify if you finished configuration of
WEBRTC module on backend side (TURN server installation)?
And could you please clarify what changes we should do in videochat.js ?
Thank you in advance
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/RippleOSI/Ripple-Qewd/issues/80#issuecomment-367291365,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA5X3BDGz825QP_M6REPoW0Az8-oa1sgks5tW_f2gaJpZM4R8-w0
.

@tony-shannon Thank you


Input buffer has corrupt header: pngload_buffer: invalid eXIf chunk

Possible bug
Is this a possible bug in a feature of sharp, unrelated to installation?

[x] Running npm install sharp completes without error.
[x] Running node -e "require('sharp')" completes without error.

I'm reading a PNG file but getting the following error:
Error: Input buffer has corrupt header: pngload_buffer: too many text chunks

The code I'm running:
const sharp = require('sharp');
const imagePath = 'D://apple.png';
const metaData= await sharp(imagePath).metadata();

I'm using the version of sharp : 0.28.3.  the image is exported by blender, you can download here apple.zip

I'm using the version of sharp : 0.28.3

Please see https://github.com/lovell/sharp/issues/2917 and upgrade to the latest version.


updated link to well known capabilities test

Pull requests into Inferno require the following items to be completed. Submitter and reviewer
should check the relevant check boxes when the associated item is done. For items that are not
applicable, note it's not applicable ("N/A") and check the box. For example, external Pull
Requests do not require ticket links.
Submitter:

[ ] This pull request describes why these changes were made
[ ] Internal ticket for this PR:
[ ] Internal ticket links to this PR
[ ] Internal ticket is properly labeled (Community/Program)
[ ] Internal ticket has a justification for its Community/Program label
[ ] Code diff has been reviewed for extraneous/missing code
[ ] Tests are included and test edge cases
[ ] Tests/code quality metrics have been run locally and pass

Reviewer 1:
Name:

[ ] Code is maintainable and reusable, reuses existing code and infrastructure
where appropriate, and accomplishes the task's purpose
[ ] The tests appropriately test the new code, including edge cases
[ ] You have tried to break the code

Reviewer 2:
Name:

[ ] Code is maintainable and reusable, reuses existing code and infrastructure
where appropriate, and accomplishes the task's purpose
[ ] The tests appropriately test the new code, including edge cases
[ ] You have tried to break the code

Pull request to update link to test ONCSD-06 "Well-known configuration declares support for required capabilities" so it points to the correct documentation

I'm not sure I agree with this...
The original link was where the actual requirement is:
capabilities: REQUIRED, array of strings representing SMART capabilities (e.g., single-sign-on or launch-standalone) that the server supports.
If anything I would update the link to http://hl7.org/fhir/smart-app-launch/conformance/index.html#metadatawhich points to section 4.2.1 directly.
The other section is useful, but I don't think it represents the requirement of the test.


Duplicate instances of self._setup_complex_phase() in relative_setup.py

I noticed that self._setup_complex_phase() is called twice.

first time: https://github.com/choderalab/perses/blob/main/perses/app/relative_setup.py#L333 -- as noted in the comments, this call needs to happen before the system generator is created because for host guest systems, the host molecule needs to be supplied to when creating the system generator
second time: https://github.com/choderalab/perses/blob/main/perses/app/relative_setup.py#L409 -- not sure if this is necessary, try removing it and seeing what happens?

Iván notes that this is not super high priority since we are in the midst of overhauling the API anyway

Yes,the comment on https://github.com/choderalab/perses/blob/ae5580173e321cc85014a2a780080b9b546f18bf/perses/app/relative_setup.py#L329 explains why we needed that at that instance but, as discussed, we can quickly investigate what happens if we remove the second call, since that seems redundant and it shouldn't be doing anything new.
As a reference, when I worked in the refactor for the NEQ cycling protocol, the RelativeFEPSetup.__init__ method of is more organized and it's only setting up the phases at the end of it, as per https://github.com/choderalab/perses/blob/faac03085376d8aace61d41e8b53d1e8e6e2f035/perses/app/relative_setup.py#L349 (just to keep in mind).


Add blurb about extensions

https://github.com/fabric8-launcher/launcher-quarkus/issues/2#issuecomment-507568201

@emmanuelbernard @jasonbrock

After discussion it with Jason, we thought that adding a click was a bad idea.
So we thought we could split the content of this message, the first part would be as a closable info block in the Extensions section:

Think of Quarkus extensions as your project dependencies. Extensions configure, boot and integrate a framework or technology into your Quarkus application.
They also do all of the heavy lifting of providing the right information to GraalVM for your application to compile natively.

And the second part would be in the "What's next" modal (after generation):

It could even be contextual to what type of project as been selected (maven or gradle)

Jason is preparing a design for the info box..

This one would be a likely blocker but to ahve some text, better design can wait

I agree with you that we don't need the quarkus:list-extensions etc on this page. Or less proheminent, that can wait for sure

+1 to get a foldable blurb approach

Here is a proposal for a new blurb
This page will help you bootstrap your Quarkus application and discover its extensions ecosystem.

Think of Quarkus extensions as your project dependencies. Extensions configure, boot and integrate a framework or technology into your Quarkus application. They also do all of the heavy lifting of providing the right information to GraalVM for your application to compile natively.

Explore the wide breath of technologies Quarkus applications and generate your project!

The middle paragraph could be the foldable part.
Also on the page after the generation, I'd change the text to
Your new Quarkus app has been generated

Your download should start shortly. If it doesn't, please use the direct link.
What's next!

Unzip the project and start playing with Quarkus by running `./mvnw compile quarkus:dev`.
Follow the guides for your next steps!

to learn more and build a great Quarkus app!

@emmanuelbernard ok thanks, I think this one is really important too: https://github.com/fabric8-launcher/launcher-quarkus/issues/15


Update transform-api.md

add space

@dlepow : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@dlepow : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@dlepow : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@ktoliver - Sorry, my mistake, this PR is intended for the azure-docs-pr repo. I'm closing and will follow up there.


Anet Feature issue

Your work is very good, I want to know more about it, but your paper doesn’t seem to show how Anet’s CLIP text feature is obtained, and Anet’s visual feature is: sub_activitynet_v1-3.c3d.hdf5?

Can you reproduce the results for anet and Charades?

Can you reproduce the results for anet and Charades? @Lonicer

He did not give the anet data reading file. I only conducted experiments on the Charades data set, and it felt much lower, as follows:
{
"brief": {
<EMAIL_ADDRESS>49.87,
<EMAIL_ADDRESS>26.83,
<EMAIL_ADDRESS>65.46,
<EMAIL_ADDRESS>34.35,
"MR-full-mAP": 28.54,
<EMAIL_ADDRESS>57.39,
<EMAIL_ADDRESS>24.63,
"MR-middle-mAP": 31.58,
"MR-short-mAP": 27.73
},

Can you also share the opt.json file for that result?
Here are my reproduced results for ANet.
<EMAIL_ADDRESS>39.28,
<EMAIL_ADDRESS>22.05,
<EMAIL_ADDRESS>66.19,
<EMAIL_ADDRESS>40.32,
"MR-full-mAP": 27.64,
<EMAIL_ADDRESS>50.95,
<EMAIL_ADDRESS>24.84,
"MR-middle-mAP": 24.05,
"MR-short-mAP": 15.1
opt.zip

Are you using start_end_dataset.py provided by EaTR for data reading operations? Can hdf5 data be read? My Charades-STA options file is as follows.
opt.zip

Yes right, but since self.feat_anet is not defined in the implementation, I defined with hd5 file by myself.

Sorry for the late reply and confusion on the code. The data uploading code for the Charades-STA and ANet Caption datasets is the old version. I will update clear version of the code and config file soon as possible.

Are you using start_end_dataset.py provided by EaTR for data reading operations? Can hdf5 data be read? My Charades-STA options file is as follows. opt.zip

Hello! Did you successfully run the code on the charades dataset? Could you tell me your wechat or email address? I want to ask you something about the code running!

Sorry for bothering, I wonder why the ActivityNet Caption Link can not be donwloaded and where are the txt_feature?

Sorry for the late reply and confusion on the code. The data uploading code for the Charades-STA and ANet Caption datasets is the old version. I will update clear version of the code and config file as soon as possible.

Sorry for bothering, I wonder if you could give the config file of charades-STA?


Use ahooks

Feature Request
Is your feature request related to a problem? Please describe:
ahooks is an upgrade for Umi hook
Describe the feature you'd like:
Use ahooks: https://ahooks.js.org/docs/umi-hooks-to-ahooks
Describe alternatives you've considered:

Teachability, Documentation, Adoption, Migration Strategy:

Leave it to UCP.


added descriptions of current_execution_status values

@sivey42 : Thanks for your contribution! The author(s) have been notified to review your proposed change.


fix: no more ansi colored logs

Problem
Allure does not support ansi colored logs, yet compute_ctl has them.
Summary of changes
Upgrade criterion to get rid of atty dependency, disable ansi colors, remove atty dependency and disable ansi feature of tracing-subscriber.
This is a heavy-handed approach. I am not aware of a workflow where you'd want to connect a terminal directly to for example compute_ctl, usually you find the logs in a file. If someone had been using colors, they will now need to:

turn the tracing-subscriber.default-features to true
edit their wanted project to have colors

I decided to explicitly disable ansi colors in case we would have in future a dependency accidentally enabling the feature on tracing-subscriber, which would be quite surprising but not unimagineable.
By getting rid of atty from dependencies we get rid of https://github.com/advisories/GHSA-g98v-hv3f-hcfr.
Checklist before requesting a review

[ ] I have performed a self-review of my code.
[ ] If it is a core feature, I have added thorough tests.
[ ] Do we need to implement analytics? if so did you add the relevant metrics to the dashboard?
[ ] If this PR requires public announcement, mark it with /release-notes label and add several sentences in this section.

Checklist before merging

[ ] Do not forget to reformat commit message to not include the above checklist

Here's an example of a compute.log, looks much more clean now, thanks @koivunej 👍
I wonder if we can unify the log format between C and Rust parts:
2023-07-03T11:19:01.168515Z  INFO configurator_main_loop: woken up for compute status: Running, sleeping
2023-07-03T11:19:01.222254Z  INFO http request{otel.name=/status http.method=GET}: serving /status GET request
2023-07-03 11:19:01.232 GMT [85050] LOG:  [NEON_SMGR] libpagestore: connected to 'postgresql://no_user@localhost:25020'
2023-07-03 11:19:01.247 GMT [85062] LOG:  [NEON_SMGR] libpagestore: connected to 'postgresql://no_user@localhost:25020'

Implementation wise this looks good, although I am missing context on whether color support was wanted in the first place or if auto-detection is desired.

There has been a bit of head scratching as to why some logs have ansi colors, and most don't. With some browsers it's possible to copy paste ansi escaped sequences from our log search to slack for example, which is highly unpleasant to read. With allure reports (our "regress" or integration test reporting) as linked by @bayandin in https://github.com/neondatabase/neon/pull/4613#issuecomment-1618026137 there is no ansi => html conversion.
So at least with compute_ctl, it was never explicitly enabled it was just true because of default-features = true. For other binaries... I don't understand in which case you'd run them directly but maybe there's a workflow I don't know. Usually binaries are ran through cargo neon or cargo run -bin neon_local (control_plane/src/bin/neon_local.rs).

I wonder if we can unify the log format between C and Rust parts (not required for this PR):

We don't define postgres log_line_prefix in this repo, maybe it comes from control plane database directly? Though, couldn't find it right away. Could be it is currently the default %m [%p]  which is timestamp + process id which our logs seem to have as well, though would not have suspected timezone to be there by default.

The colors do not seem to be a popular topic anyone else would care deeply for. I'll just merge it to have people come complaining. The PR removes duplicate dependencies so at least our build will be faster.


delete troublesome prismic cookie

deletes the preview cookie before setting another.
Seems to help, I'd like to understand more why, but that can wait.
Also accounts for the cookie being the last cookie and thus not having the ;.

Going to merge this to test with Kirsten


Solarium 5 support?

It would be nice to support Solarium 5.
As far as I can see the only issue should be the change for the default path?
https://github.com/nelmio/NelmioSolariumBundle/compare/master...dmaicher:solarium_5_compat?expand=1
I tried this on my project and it works without any other adjustments with solarium 5.0.3.
But that's because I don't set the path option on my project, so it uses the new default then.
So here my question: Should we support both Solarium < 5 and 5? If so maybe we can adjust the default config option (or maybe add a normalizer that strips out any /solr prefix) based on the used Solarium version? Not sure if there is a reliable way of detecting which Solarium version is used?
Or can we release a new major (4.0.0) that will only support Solarium 5?
I'm willing to contribute if we agree on an approach :blush:

@Seldaek @thePanz any feedback on this? :blush:

@dmaicher I like your proposal of having a new major version (4.0.0), only supporting Solarium 5 :+1:
Feel free to create a PR for that :)


change the value $ShellId to powershell

change the value $ShellId to powershell rather than Microsoft.PowerShell
PS C:\> $PSVersionTable

Name                           Value
----                           -----
PSVersion                      7.0.0-rc.1
PSEdition                      Core
GitCommitId                    7.0.0-rc.1
OS                             Microsoft Windows 6.3.9600
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

PS C:\> $ShellId
Microsoft.PowerShell
PS C:\>

This would be breaking change, from what I can tell, because $ShellID is used in to derive configuration paths / settings from, notably the (current-host) $PROFILE path(s). (The distinction between the editions is in the parent directory name).
Also, PS Core is still Microsoft PowerShell, just not Windows PowerShell anymore.
To distinguish between the editions you have $PSVersionTable.Edition and $IsCoreCLR.


Add paired end barcoding feature

Need to modify amplicon identification functions to read double-barcoded amplicons.

For double barcoded SiMSenSeq
For Duplex Sequencing?

Unresolved. Closing issues unrelated to debarcer 2


Fix #13274 - make Brackets margin/padding remoteHighlight work like Chrome one

Added support for transform-origin and fixed the way of showing border in highlight div.
This contains a little bit more of changes than the previous one and probably will need a bit of refactor, but it should work. Please mention me if it isn't working for some sets of properties and provide the piece of code that does not look correct.
I've tested/developed it on OSX Sierra 10.12.4, Chrome 57.0.2987.133 (64-bit)

The issue which I mentioned in the last PR is resolved now.

@swmitra what do you think?

It seems to be working fine 👍
Let me have a look at the change set ...

Good work worie 👍
Merging the PR, this will give us more time to identify issues (if any) well before 1.10 release.

@worie I am working on the same set of files for some other feature. I will refactor it in my PR 😄

Awesome! I'm glad it turned out ok, feel free to ping me if necessary :)


[question] possible incorrect setup steps?

So I tried following your directions on this plugin.  I'm on a centos 7.4 system
sriov failed to start
passthrough started but did not appear to  work.
ideas?

Hi @choman,
Can you please post the logs that you see in plugin console for sriov failure case and passthrough mode?
for sriov, it may be possible that SRIOV capability is not enabled in the NIC that you are using.
Which NIC are you using? Can you please post the output of lspci -vvv for the device on which you are trying to use.


Add community messages feed

I think we can reuse this feed for the community messages, see https://github.com/encointer/encointer-wallet-flutter/issues/707.
I would propose to add the community messages like: community_messages/lang_code/cm.json
{
    "some-uuid": {
	   "title": "Test Community Nachricht Titel",
	   "content": "Hello, dies ist eine Test Community Nachricht",
	   "show-at": "2022-08-25T12:30:00.00+00:00"
	}
}

Where show at, defines the scheduling of the notification. It will be the App's responsibility to keep track of the notifications that were already shown.
This scheme is currently intended for messages across all communities.
Later, I could imagine adding feeds per community here: cid/lang_code/messages.json. So community leaders would only need to supply a PR here, in order to have their message shown.

@brenzi feedback?


Provide at least once delivery guarantees in Kafka Channel

Problem
Given the eventing contrib  KafkaChannel, with no subscriber based offset, it is impossible to provide at least once delivery guarantees. Retries and dead letter queue are the user's best options.

@devguyio what do you mean "with no subscriber based offset"? Each subscriber gets its own consumer group. Isn't this enough?

I talked to @devguyio and it seems we are in agreement that for now the only thing we need is making retries the default to at least support broker upgrades. Later on we'll provide way to customize the behavior.

sounds good to me on the retires!

I also want to retire :-)


libui-ng related methods: how to use it?

Hey there kojix2,
I saw the changelog - for instance in ffi.rb:
try_extern 'void uiComboboxClear(uiCombobox *c)'

So I was thinking I could use .clear() on a combobox. But when I tested in irb,
the method name was not showing up (or perhaps I made a mistake).
IF it is possible to clear a combo box, could a simple example be added that
shows how this could be done? Or perhaps what the name of the method
may be.
I tried via irb but I could only see these methods:
LibUI.combobox_append
LibUI.combobox_on_selected
LibUI.combobox_selected
LibUI.combobox_set_selected

Does one have to do something special to tap into that ffi.rb related functionality?

I have not yet prepared an easy way to use libui-ng with Ruby's LibUI.
Still, it is great that you want to try libui-ng.
I just tried to see if I could reproduce the problem, but I could not. ( ui_combobox_clear showed up in irb )
Perhaps you are using the latest RubyGem? Or are you using andlabs branch?
If that is the case, the libui-ng methods will not show up. You need to use the main branch on Github.
I wrote previously that I wanted to use libui-ng in 0.0.15, but it did not happen and 0.0.15 simply supports M1 Mac. Sorry if this caused any confusion.
As you may already know, here is the link again on how to specify libui.so using the LIBUIDIR environment variable. if you use libui-ng, you must specify the location of libui.so yourself. (Alternatively, you can copy it into the vendor directory.)
https://github.com/kojix2/LibUI/issues/46


Avoid Flooding followers with X posts at once

First of all it's really great news that v2 is out, I have moved all my bots to the latest release and I'm experimenting with the new avoid duplicate feature, thanks for all this amazing work !
Now that Queueing is out I was wondering if we could revisit the idea of spacing out posts in the queue when there is more than 2 posts in the queue, simply set a timer to space each posts of X minutes that could be configurable via the config.json
In previous exchanges about this I had concern about :
use cases of news bots that have high volume of posts :

what if there is a queue of 10 posts, spaced out by 5 minutes between each posts and while this first queue is still flushing out, 5 or 10 new posts comes in the queue, how could we solve not accumulating perpetually the queue by either dropping posts in the queue or accelerating the rate to make sure to flush the queue completely at least every 30 minutes.

I know this may be very edgy use case, but I'm worried about queue filling up and flushing out too slowly creating a whole new set of issues but perhaps the only fix for this is to lower the overall volume of post of the bot at the source (rss feed)
Let me know what you think, perhaps you'll have a better idea, maybe @garaytc can chime in if he has some time :)

I'll look into adding this. I see your point, but I won't prioritize this feature at the moment. When I get some spare time, I'll slowly work on this, but for now, since there isn't much interest from others, I won't prioritize it. I'd recommend forking this and adding it yourself if you need it urgently.

OK, I'll try to come up with a PR because this is something that is bothering the users of my bots since the start, hopefully they have the ability to add the bot into a feed and then consume the news updates without following it but it's acting like a deterrent for users to follow it, so i'm going to have a shot at it :)


Fix/mint and deploy dune

Also fixes infinite pagination bug and incorrect variable name on cursor which affected complex wallets.


feat: replace addresses for v2 jobs

feat: replace addresses for v2 jobs

fix: documentation

fix: deprecate workForTokens

fix: tend address in readme

Description
Updates addresses to new jobs

RTM :+1:

@poolpitako plz merge! 🚀
package should be release automatically


bring up profile card when clicking on a users who have been mentioned.

Instead of taking the user to their profile right away, it should offer the same profile card that pops up when clicking on the username on the front page.

I'm going to have to rework how that works a bit to implement this, but I assume you want the same thing done for hashtags too? @bluabaleno


[internal] Shutdown R after tests

extendr-engine never enacts the end_r function. This means that we never see the consequences of the finalizers for ExternalPtr, or for ALTREP.
Also, if our tests make temporary directories/files through R those are never cleaned properly.
The only lean way to do this I found is with ctor, a crate that provides a way to add "init function" for a library; In this case, we use the "shutdown" for a library, i.e. dtor.
This is a draft for now, as it may uncover unforseen bugs.

While test is a draft, it does show various errors that happens, simply because we are cleaning up after tests.
If anyone wants to dig deeper to these issues, they are more than welcome. Tagging expert bug chasers: @yutannihilation @Ilia-Kosenkov

No idea. Again, this is one of the reasons why I think extendr should give up its embedded usages. While you think it's a shortcut to write tests without a real R session, on the other hand, it consumes your time for investigating such errors like this.

You're absolutely right. But the extendr-developer is blind to what happens when R shutsdown,
whilst containing extendr-things.
We tracked a bug down yesterday, in which R would segfaults, on exit. Turns out it was an R --save exit.
And then an altrep-string object was being asked for string pointer (by rlang, due to reasons), and then
an erroneous assumption about this pointer was made, and crash.
My attitude towards this is frankly either we improve the testing, or as you say, we take it out.
But then the extendr-developer experience is indeed strange.
jlrs the Julia/Rust wrapper project started out being a "run julia in R" first, and was that for atleast a year,
before providing bindings for Rust things in Julia. So there is that perspective as well...

@yutannihilation wonderful! Your latest find made this PR pass tests! Thank you so much.

Ah, was that the cause? Glad to know it helps here.


App Update at App Startup

What feature or improvement do you think would benefit Files?
It is not a convenient idea to have the app check for updates at each startup. It impacts negatively on productivity. It is better for updates to be checked in the background and also include an option in the settings for users to check for updates.
Requirements
.
Files Version
<IP_ADDRESS>
Windows Version
10.0.22631.3155
Comments
No response

Files already checks for app updates in the background and only displays a notification in the toolbar if an update is available. Can you elaborate on the issue?

Files already checks for app updates in the background and only displays a notification in the toolbar if an update is available. Can you elaborate on the issue?

For me it isn't — I see this "update check" on every Files app startup, even when it's minimized to the system tray:

Probably OP experiences the same problem.

Are you on <IP_ADDRESS>?

What feature or improvement do you think would benefit Files?
It is not a convenient idea to have the app check for updates at each startup. It impacts negatively on productivity. It is better for updates to be checked in the background and also include an option in the settings for users to check for updates.
Requirements
.
Files Version
<IP_ADDRESS>
Windows Version
10.0.22631.3155
Comments
No response

I do not know if it is due to installing the Files App using your classic installer as I had issues using my credit card on Microsoft store but anytime I click a folder to open from any location on my PC or launch the app freshly, what comes up first is an update check small window by the left which also attempts to load some other information. I may not be able to describe the accurate information it displayed as I already have it uninstalled, in as much as I find the app beautiful, but this behaviour is unproductive. I expect that the Files App will launch directly on each attempt and also that opening a folder from any location opens in the existing instance of the Files App but that's not the case as observed.

Files already checks for app updates in the background and only displays a notification in the toolbar if an update is available. Can you elaborate on the issue?

I do not know if it is due to installing the Files App using your classic installer as I had issues using my credit card on Microsoft store but anytime I click a folder to open from any location on my PC or launch the app freshly, what comes up first is an update check small window by the left which also attempts to load some other information. I may not be able to describe the accurate information it displayed as I already have it uninstalled, in as much as I find the app beautiful, but this behaviour is unproductive. I expect that the Files App will launch directly on each attempt and also that opening a folder from any location opens in the existing instance of the Files App but that's not the case as observed.

Are you on <IP_ADDRESS>?

Yes

@emvaized that prompt isn't from Files, it's from the App Installer component that's bundled with Windows. From what other users have reported, updating App Installer to the latest version fixes this issue. You can update it from the Microsoft Store app on your device, or by downloading and running the installer.

@yaira2
Hm, I just tried running the installer, and it seems I'm already running the latest version of this component. It doesn't give me option to update, only to fully reinstall:

It seems the installer is out of date because the newest version of App Installer is 1.23.532.0.
You can find the installer on the WinGet repo https://github.com/microsoft/winget-cli/releases/tag/v1.8.532-preview (it's the one labeled as Microsoft.DesktopAppInstaller_8wekyb3d8bbwe.msixbundle.

That prompt isn't from Files, it's from the App Installer component that's bundled with Windows. From what other users have reported, updating App Installer to the latest version fixes this issue. You can update the component from the Microsoft Store app on your device, or by downloading and running the installer.

Ok. I tried this link but it points to the official release of AppInstaller which is up to date on my system, (Version: 1.22.10582.0). But the second link you shared points to the experimental version (Version: 1.23.532.0). I have now installed Version: 1.23.532.0 but the problem persists. I set the FilesApp to be the default File Explorer.

You likely need to reinstall Files as well (uninstall first and then run the Files installer again).

It seems the installer is out of date because the newest version of App Installer is 1.23.532.0.
You can find the installer on the WinGet repo https://github.com/microsoft/winget-cli/releases/tag/v1.8.532-preview (it's the one labeled as Microsoft.DesktopAppInstaller_8wekyb3d8bbwe.msixbundle.

Ok. I tried this link but it points to the official release of AppInstaller which is up to date on my system, (Version: 1.22.10582.0). But the second link you shared points to the experimental version (Version: 1.23.532.0). I have now installed Version: 1.23.532.0 but the problem persists. I set the FilesApp to be the default File Explorer.
If an instance of FilesApp is open and I tried launching another instance, the same box appears. If I attempt to open a folder from my desktop, the folder does not open, except that it attempts to open that same box but nothing gets shown afterwards. So, apparently, folders does not open if I attempt to launch from outside the FilesApp. Folders open only within the FilesApp and the update box keeps coming up.

You likely need to reinstall Files as well (uninstall first and then run the Files installer again).

Still the same after upgrading the installer and uninstalling and re-installing the Files App.

The other option is to:

Use the Store version, this doesn't use App Installer so it won't have this issue.
Try installing the msixbundle but it's possible that it'll still have this problem https://cdn.files.community/files/stable/Files.Package_<IP_ADDRESS>_Stable_Test/Files.Package_<IP_ADDRESS>_x64_ARM64_Stable.msixbundle

@yaira2
I just tried installing the package you shared, and it didn't have the loading popup on launch. Does it mean this version won't receive automatic updates in the future?

It should still update as before, the only reason the other prompt is displayed is because of AppInstaller (it's not supposed to, but it seems to happen on some devices).
Why do we use AppInstaller? The msixbundle will only install if the other dependencies are installed first, the AppInstaller file takes care of this for users.

The other option is to:

Use the Store version, this doesn't use App Installer so it won't have this issue.
Try installing the msixbundle but it's possible that it'll still have this problem https://cdn.files.community/files/stable/Files.Package_<IP_ADDRESS>_Stable_Test/Files.Package_<IP_ADDRESS>_x64_ARM64_Stable.msixbundle

Hurray!. I installed the msixbundle through the powershell route. The update prompt no longer comes up. I have another observation though, but will open another thread for it. Thanks for the effort put in the making of the app. Will consider making some donation later on when I fix my credit card issue.

Thanks for the update! We're glad it worked 👍
A third option I forgot to mention is the Chocolatey method, it's not officially supported but it's another way to work around this issue.

@yaira2
Thanks for explanation! It clears it out.
Is there any permanent link where most recent version could be downloaded as msixbundle? The "classic installer" option on the website only allows to download the regular AppInstaller version

Just replace the version number in to match the latest release https://cdn.files.community/files/stable/Files.Package_<IP_ADDRESS>_Stable_Test/Files.Package_<IP_ADDRESS>_x64_ARM64_Stable.msixbundle

Just replace the version number in the link to match the latest release https://cdn.files.community/files/stable/Files.Package_<IP_ADDRESS>_Stable_Test/Files.Package_<IP_ADDRESS>_x64_ARM64_Stable.msixbundle

I tried to replace the number in link, and it doesn't work for recent version <IP_ADDRESS>:
https://cdn.files.community/files/stable/Files.Package_<IP_ADDRESS>_Stable_Test/Files.Package_<IP_ADDRESS>_x64_ARM64_Stable.msixbundle
Result:
The specified blob does not exist

The link works on my end so it might be a caching issue in Cloudflare. I cleared the cache so you can try again and see if it works.

The link works on my end so it might be a caching issue in Cloudflare. I cleared the cache so you can try again and see if it works.

It still doesn't work for me. Maybe something wrong in the link I shared above?

It's the correct link but arm64 is no longer capitalized https://cdn.files.community/files/stable/Files.Package_<IP_ADDRESS>_Stable_Test/Files.Package_<IP_ADDRESS>_x64_arm64_Stable.msixbundle

This one works. Thanks!

It's the correct link but arm64 is no longer capitalized https://cdn.files.community/files/stable/Files.Package_<IP_ADDRESS>_Stable_Test/Files.Package_<IP_ADDRESS>_x64_arm64_Stable.msixbundle

This one works. Thanks!

Is there a download link for the preview version?
Thanks!

@hthr24nzkyuc https://files.community/download

@yaira2 I meant the preview msixbundle file, thanks a lot!

https://cdn.files.community/files/preview/Files.Package_<IP_ADDRESS>_Preview_Test/Files.Package_<IP_ADDRESS>_x64_arm64_Preview.msixbundle


Naive addition of Level node

I made an implementation of the level node (#84) analogous to Basin/LevelControl. I have not yet added this new node to a test model.

Looks like a good start! We still need to fix #126 to document this process.
The main things I can think of now that are still missing:

formulate! function for the Level node, and calling that in water_balance!
create a new module python/ribasim/ribasim/level.py
add new Level class in qgis/nodes.py

@gijsber is correct that we'd like to support dynamic levels as well. Though there are a few other node types that still need this as well, so we can also do that together with Pump etc. in a separate PR.


Export/model inference cleanup (for release)

Change log

Autosave contexts now respect the default batching strategy and can be configured to use content size-based batching
All SDK methods now use autosave=True or its equivalent rather than calling sample.save() in a loop
Renames export_media parameter to write_clips in video sample parsers, for clarity
Centralizes the application of select_fields() in compute_embeddings() and compute_patch_embeddings(), for consistency with how this is handled in the apply_model() utility.
Adds support for sample collections to fou.iter_slices()
Adds a SampleCollection._resolve_media_field() utility
Adds a fos.read_files() method to efficiently read from multiple files in a threadpool
Adds a warning when uploading large amounts of data to CVAT
Removes unneeded pylint: disable=no-member

closing in favor of https://github.com/voxel51/fiftyone/pull/4244


Cannot parse from Zlib::GzipReader

I'm trying to optimize the parsing and processing of large CSV files (500+ MB). Since the source is already gzip, I tried to use Zlib::GzipReader.open which did not work:
Rcsv.parse(Zlib::GzipReader.open("test.gz")) do |row|
  # …
end

results in
NoMethodError: undefined method `pos=' for #<Zlib::GzipReader:0x0000011f275b58>
	from /Users/basti/.rvm/gems/ruby-2.2.3/gems/rcsv-0.3.1/lib/rcsv.rb:136:in `parse'
	…

I was wondering, if this is a general problem or something that can be made work.

This is a general issue in that rcsv assumes that IO objects are from plain files (the only type of IO that normally allows random seek), not e.g. pipes, sockets, et c. A quick read indicates that the reason for this seems to be that it wants to "peek" the header.


Added note at the bottom to point to missing RBAC. Linting

If you look at the numbers in the browser you see markdown automatically adds them up.
Feature is there so you don't have to change the numbers if you decide to reorder the list :)


lock: -m alias for --machine-type

Just like suite.py.
Signed-off-by: Sage Weil<EMAIL_ADDRESS>

please test this

test this please


Inline local var refactoring

@devoncarew

hook up inline local var refactoring
extract refactorings into submenu

Can you add a screenshot of what the new context menu looks like?
lgtm

(also, we should update the changelog to include info about the new refactoring)

Good idea. Here's the submenu screenshot and I'll update the change log once your PR lands

Looks nice :)


DBZ-1419 Document adaptive/connect mode for SQL Server

https://github.com/debezium/debezium/pull/999

LGTM; thanks!

I have opened a PR against the main repository for this change.  @jpechane can you double check that I did make a mistake and if it looks good, feel free to merge it prior to the next release?

@Naros, I've merged https://github.com/debezium/debezium/pull/1011 into master, as I had changed the Antora config to publish from upstream/development_docs instead of master. This will allow us to do any doc changes as part of the actual code PR going forward. I've also updated the contribution guide accordingly. Thanks!


flow_control: Refactor setWatermark

Context
In flow control part 3 PR where downstream push back sidestream, sidestream needs to subscribe to downstream watermark events (via addDownstreamWatermarkCallbacks), so that back pressure can be invoked when when the downstream buffers are overrun
Problem Statement
The subscription（i.e.，addDownstreamWatermarkCallbacks)happens on pool ready  which is initiated by client (e.g., ext_proc)'s startStream. However, the setWatermark happens after it (one line below). This leads to problem that addDownstreamWatermarkCallbacks in sidestream failed because watermark is not set
Tracing example of the repro :

Solution
Move setWatermark earlier right after stream has been initiated/started successfully . The watermark callbacks are passed by streamOptions
Risk Level: LOW? runtime gard.
Testing: ext_proc + gRPC integration test
Docs Changes: N/A
Release Notes: N/A
Platform Specific Features: N/A

/retest

/assign @alyssawilk @yanavlasov


Still no FL2000 support in Linux

Hi, just wanted to ask whether you guys are aware of https://github.com/fresco-fl2000/fl2000? Idk about this stuff but it looks like it might help you to actually get that driver written? Also, there's someone at https://unix.stackexchange.com/questions/309913/usb-hdmi-adapter-detected-only-as-audio-adapter/378729 and someone at<EMAIL_ADDRESS>who are both looking to get a driver for this little bugger.

Someone pointed me to that recent release by FL, it looks great and will be extremely useful in developing a more complete driver.  I seem to always be busy with various other projects, but I do intend to get some work done this within the next month.  It's nice to know someone is interested!

I'm sure the whole (linux) world will be interested, as these devices are so affordable, there is hardly any alternative, and it is nice of FL to try to help!

Hello!!
They send an email, abou HDMI suport you can see it in here ;) i hope this can help https://github.com/fresco-fl2000/fl2000/issues/4

https://support.frescologic.com/portal/helpcenter/articles/operating-systems-supported

Hello guys,
FWIW:
How is the HDMI support with this device under Windows ??
I can do this test on my systems because lack of this OS.

@ulli-kroll  HDMI support for this chip is close to perfect on Windows actually

@C-Bouthoorn
thanks
please read
https://github.com/ulli-kroll/FL2000/blob/master/TODO.md


Video Resolution is not saved

Video Resolution is reset to 100% when starting ALVR. It was already an issue, but it was fixed back  then.

nice. I can confirm that its working now. thanks!

yes.


[refactor-prompt] Add missing tests for wallet create, verbose and create_addr

What current issue(s) does this address, or what feature is it adding?
Add missing tests after PR #720 (also see https://github.com/CityOfZion/neo-python/pull/726#issuecomment-442285227)
The tests are for the following commands wallet create, wallet verbose, wallet create_addr.
How did you solve this problem?
Added some tests.
How did you make sure your solution works?
Run make test.
Are there any special changes in the code that we should be aware of?
No.
Please check the following, if applicable:

[x] Did you add any tests?
[x] Did you run make lint?
[x] Did you run make test?
[x] Are you making a PR to a feature branch or development rather than master?
[ ] Did you add an entry to CHANGELOG.rst? (if not, please do)

Note:

I couldn't find any other test related to wallet migration so I was unable to test the command wallet migrate.

Coverage increased (+0.2%) to 83.79% when pulling ae18011037be193b4b0655d1607a1c2149d6fecb on LysanderGG:add_command_wallet_tests into d21222f1ead1e2e42b56febb1b6b3fdf051818b1 on CityOfZion:refactor-prompt.

This looks good. Could you also add a test for wallet?

Also, it would be nice to see a test for an invalid wallet command

And, I was looking here: https://coveralls.io/builds/20405190/source?filename=neo/Prompt/Commands/Wallet.py#L109
Is the logic here wrong? It seems like we have nothing actually triggering start_wallet_loop

@ixje @jseagrave21 Thank you for the first review!

test for wallet (coverage)
-> Done, but there's not much to test.
Shall I test what is printed to std::out?

test invalid wallet (coverage)
-> Done, but there's not much to test.

ensure wallet loop is actually started when creating a new wallet (functionality)
The bug had been introduced with #726.
I fixed it.

Please review a second time when you have time.

I couldn't find any other test related to wallet migration so I was unable to test the command wallet migrate

Skip it. I'm going to remove all migrate code. It's old an no longer used.

@LysanderGG I prefer integrated tests which simulate user input as much as possible. When I implemented the testing method here https://github.com/CityOfZion/neo-python/pull/726#issuecomment-441996896 I wasn't sure how to test directly from prompt.py. But if that is possible, I would prefer that.

Back here https://github.com/CityOfZion/neo-python/pull/726#discussion_r236785324 I kind of reasoned that testing "GroupCommand" vs "SubCommand" doesn't really matter, although "GroupCommand" makes it more obvious what scenario we're working on and will need testing anyway. Which would be in line with @jseagrave21 's last comment.
After your discussion above I kind of realise that people might start calling commands directly when they're extending neo-python. e.g. when they implement a web interface, REST API, new RPC commands or want to control neo-python programmatically. They should not have to re-create the logic for let's say sending assets when there's a CommandSend already doing this. Now being aware of this I don't think we can avoid some code duplication between the "Group Command"  and "SubCommand" so to say. For the extensibility reasons mentioned before, I would now lean towards testing commands directly while not excluding testing group commands. (let me know if that last line doesn't make sense and I'll try to rephrase)

I think that the best to do is keep the functionnalities not related to the command line outside of Commands so that these functions can be used elsewhere.

I actually had that in mind (separate presentation from functionality) before writing my previous comment, but thought it might lead to more confusion at this point.

I'm a bit lost with this big discussion; can you
No worries, same here. This is a good showcase why we should keep PR's small, because discussions can still get big :)

I think for this one let's get it in and we'll think about moving out the body of execute() functions before we do the big merge. That way we can have it in a clean PR which is easier to discuss. @jseagrave21 any objections at this point or things that need solving before merging?
PS: I added the last paragraph as a TODO item to the original "CLI refactoring post"


Missing data in incremental models by time range

Hi! I'm getting less rows than expected when doing incremental models in BigQuery. Here is a reproducible example:

Take the dataset thelook_eccommerce and make a copy of events table to a dataset called ecommerce_demo.

Initialize a new SQLMesh project with the following config.yaml:
gateways:
  local:
    connection:
      type: duckdb
      database: local.db

  bigquery:
    state_connection:
      type: duckdb
      database: state.db
    connection:
      type: bigquery
      project: your_gcloud_project
      location: europe-west1

default_gateway: bigquery

model_defaults:
  dialect: bigquery
  start: 2024-11-01

Create the following model:
MODEL (
    name ecommerce_demo_silver.events_test,
    kind INCREMENTAL_BY_TIME_RANGE (
      time_column (created_at, '%Y-%m-%d %H:%i:%s %Z'),
    ),
    cron '@daily',
    grain (event_id),
    partitioned_by TIMESTAMP_TRUNC(created_at, DAY),
);

SELECT *
FROM ecommerce_demo.events
WHERE created_at BETWEEN @start_ds and @end_ds

Check that it fails to bring the same number of rows:
with counts_web_events as (
  select
  count(distinct id) as n_web_events
from ecommerce_demo_silver.events_test
)
, counts_events as (
  select
  count(distinct id) as n_events
from ecommerce_demo.events
where date(created_at) >= '2024-11-01'
)
select *
from counts_web_events, counts_events
where n_web_events <> n_events
-- 117477, 124223

Thanks!

By default, SQLMesh only process complete intervals. In this case your model is daily, which means that it will only process complete day-long intervals..
You should either put an upper date bound on your second query like:
where date(created_at) >= '2024-11-01' and date(created_at) <= '<the end date backfilled by sqlmesh>'

Or if you want SQLMesh to backfill partial intervals set the allow_partials attribute to TRUE in the model definition.
Please feel free to re-open the issue with additional info.


fix cross-cluster gRPC in security tests

https://github.com/istio/istio/blob/a26f344ec07efc4a435ca086347acf68b4d1eb23/tests/integration/security/util/connection/checker.go#L48-L49

@stevenctl can you please provide some more detail on what this is needed for? Thanks

Added slightly more detail – but it's hard to tell if this is a known limitation, a bug or something else. There are a lot of skips in our test that aren't linked back to an issue to investigate/unskip.


Add Formatter option to disable colors

Currently colors can apparently only be disabled via a build-time feature flag. There are however many scenarios where you might want to be able to do both color and no-color without having to rebuild the binary, e.g. providing a --no-color option, disabling colors when the stdout is not a TTY but e.g. piped or redirected, or doing UI tests without wanting to deal with ANSI escape codes in the test files.

Good idea, I'll add that.


Some cleanup for AnnotationController

Moved xref endpoint to a separate controller
Removed all endpoints except annotation from the swagger documentation
Some of the removed endpoints are still available. Keeping those hidden endpoints for now to avoid breaking our internal pipelines.

Codecov Report

Merging #68 into master will decrease coverage by 0.23%.
The diff coverage is 0%.

@@             Coverage Diff              @@
##             master      #68      +/-   ##
============================================
- Coverage     21.89%   21.65%   -0.24%
  Complexity       73       73
============================================
  Files            30       31       +1
  Lines           813      822       +9
  Branches         77       78       +1
============================================
  Hits            178      178
- Misses          622      631       +9
  Partials         13       13

Impacted Files
Coverage Δ
Complexity Δ

...ome_nexus/annotation/web/AnnotationController.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

...nexus/annotation/web/CrossReferenceController.java
0% <0%> (ø)
0 <0> (?)

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 64bf9c0...003a88f. Read the comment docs.

@onursumer what do you think about using groups instead, similar to how cBioPortal API works. (We could make a similar group=internal): http://www.cbioportal.org/api/swagger-ui.html. Didn't think of this before, perhaps better if we want to continue to use the docs ourselves to explore the currently existing APIs.

@inodb sounds good to me. I can update the PR, so that we can add a controller for the internal API

the (now hidden) hgvs endpoint still provides backwards compatibility, returning a list of objects as before. Merging this PR now, as it is been put into production.
Additional improvements can follow in future PRs


Swift client: [Errno 111] Connection refused, HTTPConnectionPool(host='controller', port=8080): Max retries exceeded

On either controller or swiftproxy nodes :
. admin-openrc.sh

Please enter your OpenStack Password:

swift list

HTTPConnectionPool(host='controller', port=8080): Max retries exceeded with url: /v1/AUTH_cdbcbc3eeb8a472c8abb2b67e749774c?format=json (Caused by <class 'socket.error'>: [Errno 111] Connection refused)

On swift proxy node:
root@swiftProxy:/# tail /var/log/syslog

Oct 19 00:48:48 swiftProxy proxy-server: Using /tmp/keystone-signing-EiU8XG as cache directory for signing certificate
Oct 19 00:48:48 swiftProxy proxy-server: Started child 2688
Oct 19 00:48:48 swiftProxy proxy-server: Adding required filter dlo to pipeline at position 0
Oct 19 00:48:48 swiftProxy proxy-server: Adding required filter gatekeeper to pipeline at position 0
Oct 19 00:48:48 swiftProxy proxy-server: Adding required filter catch_errors to pipeline at position 0
Oct 19 00:48:48 swiftProxy proxy-server: Pipeline was modified. New pipeline is "catch_errors gatekeeper dlo healthcheck memcache keystoneclient.middleware.auth_token:filter_factory keystoneauth proxy".
Oct 19 00:48:48 swiftProxy proxy-server: Starting keystone auth_token middleware
Oct 19 00:48:48 swiftProxy proxy-server: Configuring auth_uri to point to the public identity endpoint is required; clients may not be able to authenticate against an admin endpoint
Oct 19 00:48:48 swiftProxy proxy-server: Using /tmp/keystone-signing-y6DDNe as cache directory for signing certificate
Oct 19 01:17:01 swiftProxy CRON[2734]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)

Following the previously mentioned logs:

Oct 19 00:48:48 swiftProxy proxy-server: Configuring auth_uri to point to the public identity endpoint is required; clients may not be able to authenticate against an admin endpoint

I added auth_uri = http://controller:5000 in /etc/swift/proxy-server.conf

# references to keystone server
auth_protocol = http
auth_uri = http://controller:5000
auth_host = controller
auth_port = 35357

the log note disappeared but Still doesn't solve the issue

with a separate deployment of swift proxy node, I should have configured swift endpoint url with swift proxy node NOT controller.
So I removed swift service and its endpoints and re-created new service and endpoints with as swiftproxy url
root@controller:/home/ajn# keystone service-create --name swift --type object-store --description "OpenStack Object Storage"

+-------------+----------------------------------+
|   Property  |              Value               |
+-------------+----------------------------------+
| description |     OpenStack Object Storage     |
|   enabled   |               True               |
|      id     | 7a0d02c3900142678905d6fb3913f294 |
|     name    |              swift               |
|     type    |           object-store           |
+-------------+----------------------------------+

root@controller:/home/ajn#
keystone endpoint-create \
> --service-id=$(keystone service-list | awk '/ object-store / {print $2}') \
> --publicurl="http://swiftProxy:8080/v1/AUTH_%(tenant_id)s" \
> --internalurl="http://swiftProxy:8080/v1/AUTH_%(tenant_id)s" \
> --adminurl="http://swiftProxy:8080" \
> --region regionOne

+-------------+----------------------------------------------+
|   Property  |                    Value                     |
+-------------+----------------------------------------------+
|   adminurl  |            http://swiftProxy:8080            |
|      id     |       da9f5931bb1249108503ba85d56333f1       |
| internalurl | http://swiftProxy:8080/v1/AUTH_%(tenant_id)s |
|  publicurl  | http://swiftProxy:8080/v1/AUTH_%(tenant_id)s |
|    region   |                  regionOne                   |
|  service_id |       7a0d02c3900142678905d6fb3913f294       |
+-------------+----------------------------------------------+

Now it works fine:
# swift stat

   Account: AUTH_cdbcbc3eeb8a472c8abb2b67e749774c
Containers: 1
   Objects: 2
     Bytes: 0

Accept-Ranges: bytes
X-Timestamp:<PHONE_NUMBER>.69520
X-Trans-Id: tx2194837e13ae4e8e96291-0058077146
Content-Type: text/plain; charset=utf-8

# touch test1.txt
# swift upload container-test1 test1.txt

test1.txt

# rm test1.txt

# ls *.txt
# swift download container-test1

test1.txt [auth 0.201s, headers 0.241s, total 0.241s, 0.000 MB/s]

# ls

test1.txt


cp -u not working on MacOS

Cross platform-support is a real joy. On MacOS I now get this error:
cp: illegal option -- u

See #201

Fixed with PR #201


[3.8.x] Backports

Just curious. Is there any fix with quarkus-qpid-jms:2.6.0 which we need in 3.8.x?

Not really in this instance. But we should stay aligned with whatever version is used in the platform 3.8.x branch (and elsewhere).

OK, that remind me that it also need to upgrade quarkus-pooled-jms to 2.3.1 and quarkus-mybatis to .2.2.2


[WIP] Move to Confluent.Kafka 1.0-experimental

@Aaronontheweb I guess we can close this, because we have #30 merged.


Feature: Add whatlang language identifier.

I have been having some fun with polars plugins and written (with tests) integration with the what-lang crate.
The scope is three functions:

what_lang - can identify a string's language to either: English name for the language, language name, or language code.
what_lang_confidence -floating point confidence score for identification.
what_lang_reliable - boolean for reliable/not. (I haven't looked into great detail for the relationship between this and what_lang_confidence. Both methods are straight out of the crate).

I know this is a little different from the more standard format string processing you have so far. Would you be open to a PR?
I am keen to learn more and better rust, so would be more than happy to respond to any changes you request to the contribution.

Imo this is probably better done outside a dataframe. The user can turn a string column into a list of strings and pass to a Python Wrapper of what lang.
Someone needs to develop a Python wrapper for that though.
@ctdunc ideas?

I think this makes sense as a Polars plugin. Taking e.g. chat data and grouping by user > language is a pretty reasonable use case that can't easily be done by passing to a python list.
This would also make a good standalone package.
I think it is probably beyond the scope of "identifier strings/standardized formats" but would be happy to help stand this up as its own plugin, or expand the scope of polars_istr. @abstractqqq
Neat idea! I wonder what language would be guessed for US037833100

Thanks for your thoughts both! :)
I am now thinking of extending this to a few other crates: lingua-rs, rust-cld2, and whichlang.
So, I think it will make sense as a stand-alone library.


Positron > Positron Pro

Due to licensing, we had to change Positron to Positron Pro when discussing Positron Sessions in Workbench (very similar to RStudio vs. RStudio Pro).
I just wanted to flag it here in case there is any cross-over.

Double checked and all mentions of Positron are about the IDE and are not referencing sessions in Workbench.
Thanks for flagging it here so we could take a look. Closing. 👍


Refactor Gulp or move away from Gulp

Gulp is currently not "compiling" correctly the project, sometimes  documents are left and you have to run gulp again. Also gulp watch is broken as well. This needs to be revisited soon

I propose using npm scripts directly.

@AsLogd is refactoring to NPM scripts

PRed in #78

Done in #78


inconsistency in notification of Topic "ready" status and still generating

I received an email that my topic was "ready," however, I went to the topic and it said "still generating"

now the Topic summary screen shows. Not sure if it is a page caching issue or what...

this is a known bug.  we send the email out when the snapshotting process
is done, but at that point there may still be stories in the solr import
queue.  the snapshot.is_searchable field is not set until there are no more
stories for the given snapshot in the solr import queue.  for small topics,
this usually happens within a few minutes.  for big topics, it can take
several hours.
this is a backend issue.
-hal
On Mon, May 4, 2020 at 11:22 AM cindyb<EMAIL_ADDRESS>wrote:

now the Topic summary screen shows. Not sure if it is a page caching issue
or what...
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_mitmedialab_MediaCloud-2DWeb-2DTools_issues_1816-23issuecomment-2D623563891&d=DwMCaQ&c=WO-RGvefibhHBZq3fL85hQ&r=0c5FW2CrwCh84ocLICzUHjcwKK-QMUDy4RRw_n18mMo&m=2DB7-ro9sU18sie24OENsTxmivuSAB0jCbgA7zw64P4&s=hhi4obav0hyQnSIa0VV2FdTmuJ76etaZMgHt-pc_2EY&e=,
or unsubscribe
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AAN66T6WYWEUQMQ6BDB3SC3RP3TTBANCNFSM4MY4RVQQ&d=DwMCaQ&c=WO-RGvefibhHBZq3fL85hQ&r=0c5FW2CrwCh84ocLICzUHjcwKK-QMUDy4RRw_n18mMo&m=2DB7-ro9sU18sie24OENsTxmivuSAB0jCbgA7zw64P4&s=ZCNQPCevDgl9zdvCqItag924s3p5YksnESrrHgAeFWI&e=
.

Addressed on the backend


Snippet spacing and indentation touch-ups

The csharp snippets need a smidgen of work with stray line spaces and broken indentation. This will be broken down into two PR's. One will mostly address language-reference, while the other will mostly address the programming-guide.
@tompratt-AQ Will this conflict with anything you've been doing?

Glad you are tackling this Luke! I've seen some of the issues that you mention here during my recent work with the snippets, and I fixed a few of them where I could - but I'm sure there will be plenty left over. That said, I don't think we will directly conflict. Especially, after my PRs 2128, 2131, and 2138 are merged. All 3 of these PRs are about addressing the correct snippets from the topics, so I only touched  snippet files to fix snippet tags when they were mismatched or otherwise broken.

Ok, cool. I didn't want to dup any work you were doing or land us into a patch of PR conflicts. What I did didn't take long; so if we need to close this and address later, we certainly can do that.

is this still blocked @GuardRex?

@mairaw I held off on further work ... see https://github.com/dotnet/docs/pull/2153#issuecomment-301626945

@mairaw This one pertaining to indentation in snippets won't make the cut for 7/31. Do u want to re-assign?


Memory keeps rising when decoding rtsp stream

System info

Ubuntu 22.04
GeForce RTX 3060
Driver Version: 535.183.01   CUDA Version: 11.8

To Reproduce
def update(source, gpuid, stream_index):
    try:
        # 尝试创建 PyFFmpegDemuxer 对象，处理视频流
        # , 'timeout': "10000000"
        pyDec = nvc.PyDecoder(source, {'timeout': "10000000", 'rtsp_transport': 'tcp'}, 0)
    except RuntimeError as e:
        logger.error(f"无法打开视频源 {source}: {e}")  # 记录错误日志
        return

    # 创建颜色空间转换器对象，将显存中的图像转换为BGR格式到内存中
    pyCvt = nvc.PySurfaceConverter(
        pyDec.Format(),
        nvc.PixelFormat.RGB,
        gpu_id=0)

    pyCvt2 = nvc.PySurfaceConverter(
        nvc.PixelFormat.RGB,
        nvc.PixelFormat.BGR,
        gpu_id=0)

    pyCvt3 = nvc.PySurfaceConverter(
        pyDec.Format(),
        nvc.PixelFormat.BGR,
        gpu_id=0
    )

    # 创建表面下载器对象，从GPU下载图像数据到内存
    pyDwn = nvc.PySurfaceDownloader(
        gpuid  # GPU编号
    )

    # 初始化变量
    rawFrame = np.ndarray((pyDec.Height(), pyDec.Width(), 3), dtype=np.uint8)  # 存储解码后的视频帧数据的数组
    # Raw decoded Surface
    surf_src = nvc.Surface.Make(
        format=pyDec.Format(),
        width=pyDec.Width(),
        height=pyDec.Height(),
        gpu_id=0)

    # Raw Surface, converted to RGB
    surf_dst = nvc.Surface.Make(
        format=nvc.PixelFormat.RGB,
        width=pyDec.Width(),
        height=pyDec.Height(),
        gpu_id=0)

    surf_dst2 = nvc.Surface.Make(
        format=nvc.PixelFormat.BGR,
        width=pyDec.Width(),
        height=pyDec.Height(),
        gpu_id=0)
    # Packet data
    pkt_data = nvc.PacketData()

    # 确定颜色空间转换参数
    cspace, crange = pyDec.ColorSpace(), pyDec.ColorRange()
    if nvc.ColorSpace.UNSPEC == cspace:
        cspace = nvc.ColorSpace.BT_709
    if nvc.ColorRange.UDEF == crange:
        crange = nvc.ColorRange.MPEG
    cc_ctx = nvc.ColorspaceConversionContext(cspace, crange)  # 创建颜色空间转换上下文对象

    # 获取视频帧率
    frame_rate = pyDec.AvgFramerate() if pyDec.AvgFramerate() is not None else 20

    while True:  # 循环处理视频流中的帧
        try:
            success, details = pyDec.DecodeSingleSurface(surf_src)
        except Exception as e:
            logger.error(f"处理视频帧时出现异常: {e}，{source}")  # 记录异常日志
            continue  # 继续下一次循环

update("rtsp://admin:13572468$@<IP_ADDRESS>:554/cam/realmonitor?channel=1&subtype=0", 0, 0)

success, details = pyDec.DecodeSingleSurface(surf_src)
This code will cause RES to keep rising

My current VALI version is 3.2.10. I used PyFFmpegDemuxer 3.1.1 before, and RES will be fixed in a range.

Hi @leyankon

This code will cause RES to keep rising

What does that mean ?
From your code example I see that you decode video from RTSP source using tcp protocol and 10s timeout.
There are also multiple converters and downloader, none of them are used.
What's the exact problem ? vRAM consumption goes up over time ?

@RomanArzumanyan
success, details = pyDec.DecodeSingleSurface(surf_src)

When this line of code exists, enter htop in the terminal, and you can see that the RES of the process continues to rise.
I'm wondering if this is normal?

Ok, so the actual question is "Non-swapped physical memory consumption goes up during RTSP stream decode".
That's very interesting and indeed important question which I have not investigated yet.
Why ? Because it's quite generic.
E. g. I can track memory allocations within VALI itself (Surfaces and Buffers and things of that kind) but I can't so easily do that for 3rd party libraries.
If you're willing to investigate on this possible issue that would be very helpful. Can you track memory consumption on some local video file ? If this behavior reproduces with one of the testing videos - that would be even better (easier to repro on my side).

@RomanArzumanyan

I tested mp4 and had the same problem. I selected a one-hour video. From the beginning to the end, the RES increased by 1000M.
This should be a common situation.
Both video and rtsp will increase RES over time.

@leyankon
Thanks for the update.
I'll repro on my side and will come back to you as I find somethig.

@leyankon
It looks like I've found the memory leak reason: av_packet_unref call was missing within decoding loop.
Please check out latest main branch which has the patch and LMK if the issue persists.
Otherwise if it's solved I'll draft a release.
P. S.
That's how I've checked memory consumption.
import PyNvCodec as nvc

def getCurrentMemoryUsage():
    ''' Memory usage in kB '''

    with open('/proc/self/status') as f:
        memusage = f.read().split('VmRSS:')[1].split('\n')[0][:-3]

    return int(memusage.strip())

url = "tests/data/my/video.mp4"

pyDec = nvc.PyDecoder(url, {}, gpu_id=0)

surf_src = nvc.Surface.Make(
    format=pyDec.Format(),
    width=pyDec.Width(),
    height=pyDec.Height(),
    gpu_id=0)

while True:
    success, details = pyDec.DecodeSingleSurface(surf_src)
    if not success:
        print(details)
        break

    info = getCurrentMemoryUsage()
    print(info, flush=True)

It outputs stable memory consumption through decoding loop:
321668
321668
321668
321668
...
321668
321668
321668
321668
...
321668
321668
321668
321668
TaskExecInfo.END_OF_STREAM

@RomanArzumanyan
Sorry for not getting back to you in time. I've tested it and now it's no problem. Thanks for the quick fix.


developer.paypal.com - Express Checkout / Customize Checkout Flow

Both examples where payment function in paypal.Button.render's configuration object is used is invalid by the provided argument(s):
payment: function(data, actions) {
            return actions.payment.create({
                transactions: [
                    {
                        amount: { total: '1.00', currency: 'USD' }
                    }
                ]
   ...

it should be:
payment: function(actions) {
            return actions.payment.create({
                transactions: [
                    {
                        amount: { total: '1.00', currency: 'USD' }
                    }
                ]
  ...

This is now fixed.


Chrome port

todo

The stuff I could get done mostly automatically with the polyfill is done.

Looking like this isn't going to be possible in this plugin, a different approach will need to be taken with Chrome, one which will probably require working with an upstream project to implement part of the functionality. Brave seems likely.
Closing in 7 days unless something presents itself.

There's no non-awful way of doing this in the new version of the plugin. Firefox-only it is.


Update azure-dns.md

fixed the broken link

@kongou-ae : Thanks for your contribution! The author, @RicksterCDN, has been notified to review your proposed change.

#sign-off @kongou-ae thank you for the feedback!
@PRmerger I will send a request for an exception to get this merged.

@cynthn: I'm sorry - only the author of this article, @RicksterCDN, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.