Server is flaky

When doing long running experiments that use python scripts from a bash loop (i.e. frequently creating/destroying connections), the server stops working after some number of iterations.  Everything goes back to normal if the server is restarted.

I'll take a look on that and try to reproduce the issue. If I understand correctly you are e.g. running the rowhammer.py/hw_rowhammer.py in a loop with different parameters? Have you observed any regularity in that? For example similar loop count? Is it always hanging on the same phase of the *rowhammer.py scripts?

I'll take a look on that and try to reproduce the issue. If I understand correctly you are e.g. running the rowhammer.py/hw_rowhammer.py in a loop with different parameters? Have you observed any regularity in that? For example similar loop count? Is it always hanging on the same phase of the *rowhammer.py scripts?

I did some tests with loops of 50 and 100 runs and could not reproduce the issue. What numbers of tests did you have to run to observe the problem?

I did some tests with loops of 50 and 100 runs and could not reproduce the issue. What numbers of tests did you have to run to observe the problem?

Ok, so I tried a simpler experiment.  I created a patch that loops infinitely on a single command:

def run(self, row_pairs, pattern_generator, read_count, row_progress=16, verify_initial=True):

def __run(self, row_pairs, pattern_generator, read_count, row_progress=16, verify_initial=True):
divisor, mask = 0, 0
if self.data_inversion:
divisor, mask = self.data_inversion
@@ -135,6 +135,13 @@ class HwRowHammer(RowHammer):
self.display_errors(errors)
return

def run(self, row_pairs, pattern_generator, read_count, row_progress=16, verify_initial=True):

   k=0

   while True:

       print('k={}'.format(k))

       self.__run(row_pairs, pattern_generator, read_count, row_progress, verify_initial)

       k+=1

I ran:
python hw_rowhammer.py  --nrows 10 --read_count 475136 --pattern 01_per_row --row-pairs const --const-rows-pair 0 2 --payload-executor  --data-inversion 2 0b10  --no-refresh
And it died at iteration 218:
k=218
Preparing ...
WARNING: only single word patterns supported, using: 0xffffffff
Filling memory with data ...
Progress: [========================================] 16777216 / 16777216
Verifying written memory ...
Progress: [========================================] 16777216 / 16777216 (Errors: 0)
OK
Disabling refresh ...
Running row hammer attacks ...
Generating payload:
tRAS = 5
tRP = 3
tREFI = 977
tRFC = 45
Repeatable unit: 116
Repetitions: 58
Payload size =  1.84KB / 1024.00KB
Payload per-row toggle count = 475.136K  x2 rows
Payload refreshes (if enabled) = 8190
Expected execution time = 7970879 cycles = 63.767 ms
Transferring the payload ...
Executing ...
Time taken: 67.581 ms
Reenabling refresh ...
Verifying attacked memory ...
Traceback (most recent call last):                 ]     3150 / 16777216 (Errors: 203)
File "hw_rowhammer.py", line 148, in
main(row_hammer_cls=HwRowHammer)
File "/home/sqazi/fpga/litex-rowhammer-tester/rowhammer_tester/scripts/rowhammer.py", line 420, in main
row_hammer.run(row_pairs=row_pairs, read_count=args.read_count, pattern_generator=pattern)
File "hw_rowhammer.py", line 142, in run
self.__run(row_pairs, pattern_generator, read_count, row_progress, verify_initial)
File "hw_rowhammer.py", line 130, in __run
errors = self.check_errors(row_pattern)
File "hw_rowhammer.py", line 70, in check_errors
errors = hw_memtest(self.wb, 0x0, self.wb.mems.main_ram.size, [row_pattern])
File "/home/sqazi/fpga/litex-rowhammer-tester/rowhammer_tester/scripts/utils.py", line 402, in hw_memtest
append_errors(wb, errors)
File "/home/sqazi/fpga/litex-rowhammer-tester/rowhammer_tester/scripts/utils.py", line 392, in append_errors
data     = wb.regs.reader_error_data.read(),
File "/home/sqazi/fpga/litex-rowhammer-tester/third_party/litex/litex/tools/remote/csr_builder.py", line 40, in read
datas = self.readfn(self.addr, length=self.length)
File "/home/sqazi/fpga/litex-rowhammer-tester/third_party/litex/litex/tools/litex_client.py", line 60, in read
packet = EtherbonePacket(self.receive_packet(self.socket))
File "/home/sqazi/fpga/litex-rowhammer-tester/third_party/litex/litex/tools/remote/etherbone.py", line 368, in receive_packet
chunk = socket.recv(header_length - len(packet))
socket.timeout: timed out
Server doesn't show a disconnect:
$ make srv
litex_server --udp --udp-ip <IP_ADDRESS> --udp-port 1234
LiteX remote server
[CommUDP] ip: <IP_ADDRESS> / port: 1234 / tcp port: 1234
Connected with <IP_ADDRESS>:40628
Disconnect
Connected with <IP_ADDRESS>:40632
Disconnect
Connected with <IP_ADDRESS>:43306
Disconnect
Connected with <IP_ADDRESS>:43308

Ok, so I tried a simpler experiment.  I created a patch that loops infinitely on a single command:

def run(self, row_pairs, pattern_generator, read_count, row_progress=16, verify_initial=True):

def __run(self, row_pairs, pattern_generator, read_count, row_progress=16, verify_initial=True):
divisor, mask = 0, 0
if self.data_inversion:
divisor, mask = self.data_inversion
@@ -135,6 +135,13 @@ class HwRowHammer(RowHammer):
self.display_errors(errors)
return

def run(self, row_pairs, pattern_generator, read_count, row_progress=16, verify_initial=True):

   k=0

   while True:

       print('k={}'.format(k))

       self.__run(row_pairs, pattern_generator, read_count, row_progress, verify_initial)

       k+=1

I ran:
python hw_rowhammer.py  --nrows 10 --read_count 475136 --pattern 01_per_row --row-pairs const --const-rows-pair 0 2 --payload-executor  --data-inversion 2 0b10  --no-refresh
And it died at iteration 218:
k=218
Preparing ...
WARNING: only single word patterns supported, using: 0xffffffff
Filling memory with data ...
Progress: [========================================] 16777216 / 16777216
Verifying written memory ...
Progress: [========================================] 16777216 / 16777216 (Errors: 0)
OK
Disabling refresh ...
Running row hammer attacks ...
Generating payload:
tRAS = 5
tRP = 3
tREFI = 977
tRFC = 45
Repeatable unit: 116
Repetitions: 58
Payload size =  1.84KB / 1024.00KB
Payload per-row toggle count = 475.136K  x2 rows
Payload refreshes (if enabled) = 8190
Expected execution time = 7970879 cycles = 63.767 ms
Transferring the payload ...
Executing ...
Time taken: 67.581 ms
Reenabling refresh ...
Verifying attacked memory ...
Traceback (most recent call last):                 ]     3150 / 16777216 (Errors: 203)
File "hw_rowhammer.py", line 148, in
main(row_hammer_cls=HwRowHammer)
File "/home/sqazi/fpga/litex-rowhammer-tester/rowhammer_tester/scripts/rowhammer.py", line 420, in main
row_hammer.run(row_pairs=row_pairs, read_count=args.read_count, pattern_generator=pattern)
File "hw_rowhammer.py", line 142, in run
self.__run(row_pairs, pattern_generator, read_count, row_progress, verify_initial)
File "hw_rowhammer.py", line 130, in __run
errors = self.check_errors(row_pattern)
File "hw_rowhammer.py", line 70, in check_errors
errors = hw_memtest(self.wb, 0x0, self.wb.mems.main_ram.size, [row_pattern])
File "/home/sqazi/fpga/litex-rowhammer-tester/rowhammer_tester/scripts/utils.py", line 402, in hw_memtest
append_errors(wb, errors)
File "/home/sqazi/fpga/litex-rowhammer-tester/rowhammer_tester/scripts/utils.py", line 392, in append_errors
data     = wb.regs.reader_error_data.read(),
File "/home/sqazi/fpga/litex-rowhammer-tester/third_party/litex/litex/tools/remote/csr_builder.py", line 40, in read
datas = self.readfn(self.addr, length=self.length)
File "/home/sqazi/fpga/litex-rowhammer-tester/third_party/litex/litex/tools/litex_client.py", line 60, in read
packet = EtherbonePacket(self.receive_packet(self.socket))
File "/home/sqazi/fpga/litex-rowhammer-tester/third_party/litex/litex/tools/remote/etherbone.py", line 368, in receive_packet
chunk = socket.recv(header_length - len(packet))
socket.timeout: timed out
Server doesn't show a disconnect:
$ make srv
litex_server --udp --udp-ip <IP_ADDRESS> --udp-port 1234
LiteX remote server
[CommUDP] ip: <IP_ADDRESS> / port: 1234 / tcp port: 1234
Connected with <IP_ADDRESS>:40628
Disconnect
Connected with <IP_ADDRESS>:40632
Disconnect
Connected with <IP_ADDRESS>:43306
Disconnect
Connected with <IP_ADDRESS>:43308

I've replicated the test you described and it ran for 6385 iterations and it's still running without hanging, so I cannot really reproduce the issue this way. Maybe this is specific to your network configuration? The fact that restarting the litex_server fixes the problem for you means that there is no problem in the ZCU104 firmware nor in the FPGA.
For reference I was using thrid_party/litex at 42d62991 and litex-rowhammer-tester at 3a72ceb, so there should be no changes that could affect this. I built the bistream with python rowhammer_tester/targets/zcu104.py --payload-size 0x100000 --build.

I've replicated the test you described and it ran for 6385 iterations and it's still running without hanging, so I cannot really reproduce the issue this way. Maybe this is specific to your network configuration? The fact that restarting the litex_server fixes the problem for you means that there is no problem in the ZCU104 firmware nor in the FPGA.
For reference I was using thrid_party/litex at 42d62991 and litex-rowhammer-tester at 3a72ceb, so there should be no changes that could affect this. I built the bistream with python rowhammer_tester/targets/zcu104.py --payload-size 0x100000 --build.

You are right.  It was my network setup.  I was using wifi on the host side, which is not such a good idea with UDP.  If I use the wired network, it appears to work fine.

You are right.  It was my network setup.  I was using wifi on the host side, which is not such a good idea with UDP.  If I use the wired network, it appears to work fine.


🐛 Bulid failed: Configure project :react-native-gradle-plugin

What were you trying to do?
Want to scan qr code
Reproduceable Code
No response
What happened instead?
Build fails at about 95% after adding frame processor code and dependencies, and after fallowing the troubleshooting tutorial it doesn't even pass the configuration phase.
Relevant log output
info Running jetifier to migrate libraries to AndroidX. You can disable it using "--no-jetifier" flag.
Jetifier found 1039 file(s) to forward-jetify. Using 4 workers...
info JS server already running.
info Installing the app...

> Configure project :react-native-gradle-plugin
e: /home/o/Documents/clj/repos/react-native/node_modules/react-native-gradle-plugin/build.gradle.kts:9:19: Unresolved reference: configurationcache
e: /home/o/Documents/clj/repos/react-native/node_modules/react-native-gradle-plugin/build.gradle.kts:43:7: Unresolved reference: serviceOf

FAILURE: Build failed with an exception.

* Where:
Build file '/home/o/Documents/clj/repos/react-native/node_modules/react-native-gradle-plugin/build.gradle.kts' line: 9

* What went wrong:
Script compilation errors:

  Line 09: import org.gradle.configurationcache.extensions.serviceOf
                             ^ Unresolved reference: configurationcache

  Line 43:       serviceOf<ModuleRegistry>().getModule("gradle-tooling-api-builders").classpath.asFiles.first()
                 ^ Unresolved reference: serviceOf

2 errors

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 5s

error Failed to install the app. Make sure you have the Android development environment set up: https://reactnative.dev/docs/environment-setup.
Error: Command failed: ./gradlew app:installDebug -PreactNativeDevServerPort=8081
e: /home/o/Documents/clj/repos/react-native/node_modules/react-native-gradle-plugin/build.gradle.kts:9:19: Unresolved reference: configurationcache
e: /home/o/Documents/clj/repos/react-native/node_modules/react-native-gradle-plugin/build.gradle.kts:43:7: Unresolved reference: serviceOf

FAILURE: Build failed with an exception.

* Where:
Build file '/home/o/Documents/clj/repos/react-native/node_modules/react-native-gradle-plugin/build.gradle.kts' line: 9

* What went wrong:
Script compilation errors:

  Line 09: import org.gradle.configurationcache.extensions.serviceOf
                             ^ Unresolved reference: configurationcache

  Line 43:       serviceOf<ModuleRegistry>().getModule("gradle-tooling-api-builders").classpath.asFiles.first()
                 ^ Unresolved reference: serviceOf

2 errors

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 5s

    at makeError (/home/o/Documents/clj/repos/react-native/node_modules/execa/index.js:174:9)
    at /home/o/Documents/clj/repos/react-native/node_modules/execa/index.js:278:16
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async runOnAllDevices (/home/o/Documents/clj/repos/react-native/node_modules/@react-native-community/cli-platform-android/build/commands/runAndroid/runOnAllDevices.js:109:5)
    at async Command.handleAction (/home/o/Documents/clj/repos/react-native/node_modules/@react-native-community/cli/build/index.js:192:9)
info Run CLI with --verbose flag for more details.

Device
genymotion emulator
VisionCamera Version
2.14.1
Additional information

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

i had this problem, anyone find a solution?

Same issue here. Any idea?
Thanks

Hey! I've rewritten the entire Android codebase of VisionCamera from CameraX to Camera2 in the efforts of ✨ VisionCamera V3.
I just now completed the Camera2 rewrite and I believe the core structure is running, but there might be some edge cases to iron out. Can you try and test the PR #1674 for me to see if you can still reproduce this issue here?
Here's an instruction on how you can test that: https://github.com/mrousavy/react-native-vision-camera/pull/1674#issuecomment-1684104217
If the issue cannot be reproduced with that version/PR anymore, then hoorayy, I fixed it! 🎉
Otherwise please let me know and I'll keep this issue open to keep track of it.
Thank you!


English.java:33-35: Implement and unit test Language class R...

The puzzle 174-2ae6a13d in src/main/java/com/amihaiemil/charles/github/English.java (lines 33-35) has to be resolved: Implement and unit test Language class Russian, following the model of this class and its unit tests. The class should use the commands_ru and responses_ru properties files.
The puzzle was created by Mihai Emil Andronache on 19-Jan-17.
Estimate: 30 minutes, role: DEV.
If you have any technical questions, don't ask me, submit new tickets instead. The task will be "done" when the problem is fixed and the text of the puzzle is removed from the source code.

This issue is obsolete now, as we will refactor the brain and it will only speak english, and it won't work with regexes anymore as they are hard to mantain and explain. We'll keep it simple: english and containing words instead or regex...

The puzzle 174-2ae6a13d has disappeared from the source code, that's why I closed this issue.


[Question] - One Drive For Business Delta Token Expiry

Hello there,
I have a question in regards to One Drive For Business delta token expiry duration.
From the documentation, it is stated that it is 7 days for directory & education objects.
https://docs.microsoft.com/en-us/graph/delta-query-overview
However, it's not clear on what's the delta token expiry duration for One drive For Business.
Could you help to advise on the question above?
Thank you,
Baskaran

There is no published expiration for drive items because the delta token does not expire on a set timeframe. Instead, for delta on Drive Items, we recommend that client applications handle the 410/Gone HTTP response code and refresh the token accordingly; further explanation is on this page: https://docs.microsoft.com/en-us/graph/api/driveitem-delta?view=graph-rest-1.0&tabs=http#response-2


Full screen slider (including status bar) on Android 9

Could you elaborate on what you are trying to achieve?

Please, look at the status bar. I'd like to make an intro with full-screen mode (including status bar)

How about using the statusbar-component in renderItem? E.g.
_renderItem = ({ props, dimensions }) => (
    <View
      style={[
        styles.slide,
        ...dimensions,
        backgroundColor: props.backgroundCOlor
      ]}>
          <StatusBar backgroundColor={props.backgroundColor} barStyle="light-content" />
          {props.title}
          {props.text}
    </View>
  );

For future reference this can be achieved by doing:
<View style={{flex: 1}}>
     <StatusBar translucent backgroundColor="transparent" />
     <AppIntroSlider .../>
</View>


[LUCENE-10624] Binary Search for Sparse IndexedDISI advanceWithinBloc…

Description (or a Jira issue link if you have one)
https://issues.apache.org/jira/browse/LUCENE-10624

Thanks @wuwm for opening this PR! The improvement idea makes sense to me. Quick question though, given the similarities of the binary search implementations in the two methods, is it possible to extract them out into a common method?

Thanks @zacharymorn for comments!
There are some implementation diff inside binary search between two methods to handle some edge cases. To make binary search into a single common method, I thought of two ways: A) Add a lambda expression as method parameter to pass in implementation diff part. B) Add if-else to the combined single method. I felt both of them may make readability worse?
Also, I feel, for future changes, since these two methods serve different use cases, future optimization may vary as well (Not an expert in this part, feel free to correct me). Combing into a common method might make future changes complex.

Hmm I see. I'm actually also wondering if it will be possible to have one of them simply delegate to the other one (potentially indirectly via some helper method), and then check the returned value  (e.g. have advanceExactWithinBlock to delegate somehow to advanceWithinBlock and then check if the positioned doc is actually equal to target)?

Can we get this merged?

@yuzhoujianxia There are some discussion on if binary or exponential search can cause performance regression in some use cases. We need to address the concerns before merging. https://issues.apache.org/jira/browse/LUCENE-10624

This sounds like a nice optimization @wuwm!  Is it still relevant?
Lucene's nightly benchmarks include somewhat sparse documents (NYC taxi database) -- maybe this could be used to test the impact of exponential vs full binary search?


Create new C# environment failed

Repro steps:

Action: azureFunctions.createNewProject
Error type: Error
Error Message: Failed to get latest templates: Command "dotnet '/Users/hashibami/.vscode/extensions/ms-azuretools.vscode-azurefunctions-0.19.1/resources/dotnetJsonCli/Microsoft.TemplateEngine.JsonCli.dll' --require '/Users/hashibami/Library/Application Support/Code/User/globalStorage/ms-azuretools.vscode-azurefunctions/dotnetTemplates/itemTemplates-~2.nupkg' --require '/Users/hashibami/Library/Application Support/Code/User/globalStorage/ms-azuretools.vscode-azurefunctions/dotnetTemplates/projectTemplates-~2.nupkg' --operation list" failed with exit code "150":
It was not possible to find any compatible framework version
The specified framework 'Microsoft.NETCore.App', version '2.0.0' was not found.

The following frameworks were found:
3.0.0 at [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]

You can resolve the problem by installing the specified framework and/or SDK.
The .NET Core frameworks can be found at:

https://aka.ms/dotnet-download

Version: 0.19.1
OS: darwin
Product: Visual Studio Code
Product Version: 1.39.2
Language: en

Call Stack
CentralTemplateProvider.<anonymous> extension.bundle.js:164:382699
o extension.bundle.js:164:379638

@hazelnutsgz thanks for filing! We don't support .NET Core 3.0 yet - tracking that work here: https://github.com/microsoft/vscode-azurefunctions/issues/1489
For now you have to have a 2.* version of .NET Core installed


Create function for Affected Eye: ADCM.AFEYE

Create function for Affected Eye: ADCM.AFEYE

Hi @hiren8484, I think this is equivalent to issue #10 which @palmenl is working on?

Thanks @manciniedoardo I realised after assigning it, that Lucy was working on the function that would be applicable across the different ADaMs. Thanks for spotting, will close this off.


dimnames.{list,default} not exported

also see: http://stackoverflow.com/questions/40873221/overwrite-primitives-with-s3-in-r-package

so it looks like dimnames() in base is already a generic and you can define methods for new classes but not overwrite the default classes (answer to the above question hints to that)
best solution: rename the function to e.g. names_along


Optitype "Failed to open file" error

For what i think are 2 "standard" whole exome seq samples, running in paried normal-tumor mode.
I tried both the stable and development releases
Bcbio seems to try to be reading a file which doesn't exist.
Any ideas?
In fact, that whole tmp subdirectory doesn't exist at all:

root@725ec8206460:/data/CNV.valid/P2/work# ls -l /data/CNV.valid/P2/work/align/T2/hla/bcbiotx/
total 0
root@725ec8206460:/data/CNV.valid/P2/work#

This is the error:

[2017-11-03T03:36Z] Timing: hla typing
[2017-11-03T03:36Z] multiprocessing: call_hla
[2017-11-03T03:36Z] HLA typing with OptiType
[2017-11-03T03:37Z] Illegal instruction
[2017-11-03T03:37Z] [E::hts_open_format] Failed to open file /data/CNV.valid/P2/work/align/T2/hla/bcbiotx/tmpkuhkUh/2017_11_03_03_37_03/2017_11_03_03_37_03_1.bam
[2017-11-03T03:37Z] mapping with 16 threads...
[2017-11-03T03:37Z]  0:00:04.05 Mapping OptiType-HLA-A_B_C-input.fq to GEN reference...
[2017-11-03T03:37Z]  0:00:04.70 Generating binary hit matrix.
[2017-11-03T03:37Z] Traceback (most recent call last):
[2017-11-03T03:37Z]   File "/usr/local/bin/OptiTypePipeline.py", line 351, in
[2017-11-03T03:37Z]     pos, read_details = ht.pysam_to_hdf(bam_paths[0])
[2017-11-03T03:37Z]   File "/usr/local/share/bcbio-nextgen/anaconda/share/optitype-1.2.1-0/hlatyper.py", line 186, in pysam_to_hdf
[2017-11-03T03:37Z]     sam = pysam.AlignmentFile(samfile, sam_or_bam)
[2017-11-03T03:37Z]   File "pysam/libcalignmentfile.pyx", line 444, in pysam.libcalignmentfile.AlignmentFile.cinit
[2017-11-03T03:37Z]   File "pysam/libcalignmentfile.pyx", line 621, in pysam.libcalignmentfile.AlignmentFile._open
[2017-11-03T03:37Z] IOError: [Errno 2] could not open alignment file /data/CNV.valid/P2/work/align/T2/hla/bcbiotx/tmpkuhkUh/2017_11_03_03_37_03/2017_11_03_03_37_03_1.bam: No such file or directory
[2017-11-03T03:37Z] Uncaught exception occurred
Traceback (most recent call last):
File "/usr/local/share/bcbio-nextgen/anaconda/lib/python2.7/site-packages/bcbio/provenance/do.py", line 23, in run
_do_run(cmd, checks, log_stdout, env=env)
File "/usr/local/share/bcbio-nextgen/anaconda/lib/python2.7/site-packages/bcbio/provenance/do.py", line 103, in _do_run
raise subprocess.CalledProcessError(exitcode, error_msg)
CalledProcessError: Command 'set -o pipefail; OptiTypePipeline.py -v --dna  -o /data/CNV.valid/P2/work/align/T2/hla/bcbiotx/tmpkuhkUh -i /data/CNV.valid/P2/work/align/T2/hla/OptiType-HLA-A_B_C-input.fq -c /data/CNV.valid/P2/work/align/T2
/hla/bcbiotx/tmpkuhkUh/config.ini
Illegal instruction
[E::hts_open_format] Failed to open file /data/CNV.valid/P2/work/align/T2/hla/bcbiotx/tmpkuhkUh/2017_11_03_03_37_03/2017_11_03_03_37_03_1.bam
mapping with 16 threads...
0:00:04.05 Mapping OptiType-HLA-A_B_C-input.fq to GEN reference...
0:00:04.70 Generating binary hit matrix.
Traceback (most recent call last):
File "/usr/local/bin/OptiTypePipeline.py", line 351, in
pos, read_details = ht.pysam_to_hdf(bam_paths[0])
File "/usr/local/share/bcbio-nextgen/anaconda/share/optitype-1.2.1-0/hlatyper.py", line 186, in pysam_to_hdf
sam = pysam.AlignmentFile(samfile, sam_or_bam)
File "pysam/libcalignmentfile.pyx", line 444, in pysam.libcalignmentfile.AlignmentFile.cinit
File "pysam/libcalignmentfile.pyx", line 621, in pysam.libcalignmentfile.AlignmentFile._open
IOError: [Errno 2] could not open alignment file /data/CNV.valid/P2/work/align/T2/hla/bcbiotx/tmpkuhkUh/2017_11_03_03_37_03/2017_11_03_03_37_03_1.bam: No such file or directory
' returned non-zero exit status 1
Traceback (most recent call last):
File "/usr/local/bin/bcbio_nextgen.py", line 234, in
main(**kwargs)
File "/usr/local/bin/bcbio_nextgen.py", line 43, in main
run_main(**kwargs)
File "/usr/local/share/bcbio-nextgen/anaconda/lib/python2.7/site-packages/bcbio/pipeline/main.py", line 42, in run_main
fc_dir, run_info_yaml)
File "/usr/local/share/bcbio-nextgen/anaconda/lib/python2.7/site-packages/bcbio/pipeline/main.py", line 86, in _run_toplevel
for xs in pipeline(config, run_info_yaml, parallel, dirs, samples):
File "/usr/local/share/bcbio-nextgen/anaconda/lib/python2.7/site-packages/bcbio/pipeline/main.py", line 133, in variant2pipeline
samples = hla.run(samples, run_parallel)
File "/usr/local/share/bcbio-nextgen/anaconda/lib/python2.7/site-packages/bcbio/hla/init.py", line 31, in run
processed = run_parallel("call_hla", ([x] for x in to_process))
File "/usr/local/share/bcbio-nextgen/anaconda/lib/python2.7/site-packages/bcbio/distributed/multi.py", line 28, in run_parallel
return run_multicore(fn, items, config, parallel=parallel)
File "/usr/local/share/bcbio-nextgen/anaconda/lib/python2.7/site-packages/bcbio/distributed/multi.py", line 86, in run_multicore
for data in joblib.Parallel(parallel["num_jobs"], batch_size=1)(joblib.delayed(fn)(x) for x in items):
File "/usr/local/share/bcbio-nextgen/anaconda/lib/python2.7/site-packages/joblib/parallel.py", line 804, in call
while self.dispatch_one_batch(iterator):
File "/usr/local/share/bcbio-nextgen/anaconda/lib/python2.7/site-packages/joblib/parallel.py", line 662, in dispatch_one_batch
self._dispatch(tasks)
File "/usr/local/share/bcbio-nextgen/anaconda/lib/python2.7/site-packages/joblib/parallel.py", line 570, in _dispatch
job = ImmediateComputeBatch(batch)
File "/usr/local/share/bcbio-nextgen/anaconda/lib/python2.7/site-packages/joblib/parallel.py", line 183, in init
self.results = batch()
File "/usr/local/share/bcbio-nextgen/anaconda/lib/python2.7/site-packages/joblib/parallel.py", line 72, in call
return [func(*args, **kwargs) for func, args, kwargs in self.items]
File "/usr/local/share/bcbio-nextgen/anaconda/lib/python2.7/site-packages/bcbio/utils.py", line 50, in wrapper
return apply(f, *args, **kwargs)
File "/usr/local/share/bcbio-nextgen/anaconda/lib/python2.7/site-packages/bcbio/distributed/multitasks.py", line 274, in call_hla
return hla.call_hla(*args)
File "/usr/local/share/bcbio-nextgen/anaconda/lib/python2.7/site-packages/bcbio/hla/init.py", line 15, in call_hla
data = _CALLERShlacaller
File "/usr/local/share/bcbio-nextgen/anaconda/lib/python2.7/site-packages/bcbio/hla/optitype.py", line 39, in run
out_file = _call_hla(hla_fq, out_dir, data)
File "/usr/local/share/bcbio-nextgen/anaconda/lib/python2.7/site-packages/bcbio/hla/optitype.py", line 118, in _call_hla
do.run(cmd.format(**locals()), "HLA typing with OptiType")
File "/usr/local/share/bcbio-nextgen/anaconda/lib/python2.7/site-packages/bcbio/provenance/do.py", line 23, in run
_do_run(cmd, checks, log_stdout, env=env)
File "/usr/local/share/bcbio-nextgen/anaconda/lib/python2.7/site-packages/bcbio/provenance/do.py", line 103, in _do_run
raise subprocess.CalledProcessError(exitcode, error_msg)
subprocess.CalledProcessError: Command 'set -o pipefail; OptiTypePipeline.py -v --dna  -o /data/CNV.valid/P2/work/align/T2/hla/bcbiotx/tmpkuhkUh -i /data/CNV.valid/P2/work/align/T2/hla/OptiType-HLA-A_B_C-input.fq -c /data/CNV.valid/P2/wo
rk/align/T2/hla/bcbiotx/tmpkuhkUh/config.ini
Illegal instruction
[E::hts_open_format] Failed to open file /data/CNV.valid/P2/work/align/T2/hla/bcbiotx/tmpkuhkUh/2017_11_03_03_37_03/2017_11_03_03_37_03_1.bam
mapping with 16 threads...
0:00:04.05 Mapping OptiType-HLA-A_B_C-input.fq to GEN reference...
0:00:04.70 Generating binary hit matrix.
Traceback (most recent call last):
File "/usr/local/bin/OptiTypePipeline.py", line 351, in
pos, read_details = ht.pysam_to_hdf(bam_paths[0])
File "/usr/local/share/bcbio-nextgen/anaconda/share/optitype-1.2.1-0/hlatyper.py", line 186, in pysam_to_hdf
sam = pysam.AlignmentFile(samfile, sam_or_bam)
File "pysam/libcalignmentfile.pyx", line 444, in pysam.libcalignmentfile.AlignmentFile.cinit
File "pysam/libcalignmentfile.pyx", line 621, in pysam.libcalignmentfile.AlignmentFile._open
IOError: [Errno 2] could not open alignment file /data/CNV.valid/P2/work/align/T2/hla/bcbiotx/tmpkuhkUh/2017_11_03_03_37_03/2017_11_03_03_37_03_1.bam: No such file or directory
' returned non-zero exit status 1

Sorry about the issue and thanks for the detailed report. You're getting an error from inside optitype that the alignment file it is meant to generate is missing. The directory it specifies won't be present after the runs fails (it's a transactional directory so gets removed) so having it not present is expected. The best way to debug here is to do two things:

Look at the input file and fastq directory at /data/CNV.valid/P2/work/align/T2/hla/. Do you have HLA reads and reasonable inputs here? The latest development version tries to skip HLA typing if we don't have useful inputs, but may not be detecting this has too few reads or something else that makes OptiType fail.
Run the failing optitype command outside of bcbio writing to a stable directory to see if you can reproduce:

OptiTypePipeline.py -v --dna -o test_outdir -i /data/CNV.valid/P2/work/align/T2/hla/OptiType-HLA-A_B_C-input.fq -c config.ini

where the config.ini file is:
[mapping]
razers3=/usr/local/share/bcbio-nextgen/anaconda/bin/razers3
threads=1
[ilp]
solver=cbc
threads=1
[behavior]
deletebam=true
unpaired_weight=0
use_discordant=false

Then you could look at the outputs and try to figure out why things are not working cleanly.
Hope this helps for debugging.

Thanks for the quick response!
There what appears to be reasonable output to me in the directory:

root@9dc594a1645c:/data/CNV.valid/P2/work/align/T2/hla# ls -l
total 9492
-rw-r--r-- 1 nobody nogroup 3371235 Nov  3 03:36 OptiType-HLA-A_B_C-input.fq
-rw-r--r-- 1 nobody nogroup  991829 Nov  2 16:51 T2-HLA-A.fq
-rw-r--r-- 1 nobody nogroup 1409379 Nov  2 16:51 T2-HLA-B.fq
-rw-r--r-- 1 nobody nogroup  970027 Nov  2 16:51 T2-HLA-C.fq
-rw-r--r-- 1 nobody nogroup  784868 Nov  2 16:51 T2-HLA-DQA1.fq
-rw-r--r-- 1 nobody nogroup  697377 Nov  2 16:51 T2-HLA-DQB1.fq
-rw-r--r-- 1 nobody nogroup 1473768 Nov  2 16:51 T2-HLA-DRB1.fq
drwxr-xr-x 2 nobody nogroup    4096 Nov  3 03:37 bcbiotx
root@9dc594a1645c:/data/CNV.valid/P2/work/align/T2/hla#

and running in a separate directory gives the same error:

mkdir: cannot create directory '/tmp': File exists
root@9dc594a1645c:/data/CNV.valid/P2/work/align/T2/hla# mkdir /tmp/opti
root@9dc594a1645c:/data/CNV.valid/P2/work/align/T2/hla# cd /tmp/opti
root@9dc594a1645c:/tmp/opti# nano config.ini
root@9dc594a1645c:/tmp/opti# OptiTypePipeline.py -v --dna -o test_outdir -i /data/CNV.valid/P2/work/align/T2/hla/OptiType-HLA-A_B_C-input.fq -c config.ini
mapping with 1 threads...
0:00:04.24 Mapping OptiType-HLA-A_B_C-input.fq to GEN reference...
Illegal instruction (core dumped)
0:00:05.61 Generating binary hit matrix.
[E::hts_open_format] Failed to open file test_outdir/2017_11_03_15_29_02/2017_11_03_15_29_02_1.bam
Traceback (most recent call last):
File "/usr/local/bin/OptiTypePipeline.py", line 351, in
pos, read_details = ht.pysam_to_hdf(bam_paths[0])
File "/usr/local/share/bcbio-nextgen/anaconda/share/optitype-1.2.1-0/hlatyper.py", line 186, in pysam_to_hdf
sam = pysam.AlignmentFile(samfile, sam_or_bam)
File "pysam/libcalignmentfile.pyx", line 444, in pysam.libcalignmentfile.AlignmentFile.cinit
File "pysam/libcalignmentfile.pyx", line 621, in pysam.libcalignmentfile.AlignmentFile._open
IOError: [Errno 2] could not open alignment file test_outdir/2017_11_03_15_29_02/2017_11_03_15_29_02_1.bam: No such file or directory
root@9dc594a1645c:/tmp/opti#

there are no files in that directory:

root@9dc594a1645c:/tmp/opti# find .
.
./config.ini
./test_outdir
./test_outdir/2017_11_03_15_29_02
root@9dc594a1645c:/tmp/opti#

Actually, although the error is the same, above it i see a new hint
"Illegal instruction (core dumped)"
which likely explains why that file isn't being generated

In general the command its trying to execute is this:
/usr/local/share/bcbio-nextgen/anaconda/bin/razers3 -i 97 -m 99999 --distance-range 0 -pa -tc %d -o %s %s %s
which when running at the command line on its own, causes the core dump:
root@9dc594a1645c:/tmp/opti# /usr/local/share/bcbio-nextgen/anaconda/bin/razers3
Illegal instruction (core dumped)
Not sure where to go from there? Reinstall razers3?

Thanks for the detailed debugging and drilling in on the problem, this is really helpful. Could you try doing:
bcbio_conda install -c conda-forge -c bioconda razers3=3.5.0

There was a new version of razers3 built on bioconda 5 days ago and I wonder if that's causing issues here. If the 3.5.0 version works cleanly we could pin to that to avoid the problem generally. Thanks again for all the help digging into this.

congratulations, that was it:

root@9dc594a1645c:/tmp/opti# OptiTypePipeline.py -v --dna -o test_outdir -i /data/CNV.valid/P2/work/align/T2/hla/OptiType-HLA-A_B_C-input.fq -c config.ini
mapping with 1 threads...
0:00:00.80 Mapping OptiType-HLA-A_B_C-input.fq to GEN reference...
0:00:44.47 Generating binary hit matrix.
0:00:44.48 Loading test_outdir/2017_11_03_16_02_53/2017_11_03_16_02_53_1.bam started. Number of HLA reads loaded (updated every thousand):
1K...2K...3K...4K...
0:00:53.73 4016 reads loaded. Creating dataframe...

and then runs to completion!

Brilliant -- thanks for confirming and all the help figuring out the issue. I pinned the version in the install so any upgrades should also work going forward. Thanks again for report and help fixing this.

No No, thank you for your hard work.
Such a great tool, I'm glad to help out where i can :)


[FLINK-17724][python] Set working directory before running the Python helper scripts.

What is the purpose of the change
This pull request sets the working directory of the ProcessBuilder before running the Python helper scripts.
Brief change log

Set the working directory of the ProcessBuilder before running the Python helper scripts.

Verifying this change
This change is already covered by existing tests, such as pyflink e2e tests.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
The serializers: (no)
The runtime per-record code paths (performance sensitive): (no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: (no)
The S3 file system connector: (no)

Documentation

Does this pull request introduce a new feature? (no)
If yes, how is the feature documented? (not applicable)

@WeiZhong94 Thanks for the PR. LGTM. Will merge once the tests passed.

@flinkbot run azure

Since this change is basically a fix to the currently broken master, I pushed it to my personal Azure to get a result sooner than Flink's CI: https://dev.azure.com/rmetzger/Flink/_build/results?buildId=8007&view=results

The python e2e test has passed in my Azure though the following test was canceled:
https://dev.azure.com/weizhong0618/Flink/_build/results?buildId=103&view=logs&j=1f3ed471-1849-5d3c-a34c-19792af4ad16&t=2f5b54d0-1d28-5b01-d344-aa50ffe0cdf8
See line 12143. May be this could help..

@rmetzger @WeiZhong94 Thanks a lot. The tests have passed and so merging...


[Issue-101] Distinguish between token mainnet and testnet

Related issue: #101

🚀 Deployed on https://pr-168--papaya-melba-f5c160.netlify.app


Banner and copy update - donation campaign

2) Add a banner (like the one on staging.openapparel.org)
This banner will display persistently (as on OAR staging); it will message a donation campaign that is loosely slated to run from Nov 25 - Dec 31 (specific dates will not be referenced in the copy; but please keep in mind that we will ask that it be turned of in early January)
Copy (with hyperlink): We’re fundraising! Help us maintain OS Hub as a free platform, accessible to all, by donating to our campaign.
Background color: Black
Text color: White
Font and weight: Darker Grotesque font, medium weight

@katieashaw - we created a new ticket per Vanessa's guidance. tagging @hlennett for her feedback.

Updated Copy & styling (with hyperlink): We’re fundraising! Help us maintain OS Hub as a free platform, accessible to all, by donating to our campaign.
Background color: Black
Font: Darker Grotesque font, medium weight
Color: #FCCF3F
Alignment: Centered

@vrwOAR I have just opened pull request #2318 that includes screenshots of the new banner with content and styling matching the commend above (https://github.com/open-apparel-registry/open-apparel-registry/issues/2317#issuecomment-1324079431)

From @vrwOAR

The banner can have an end date of Jan 31, 2023.


aerofc: disable internal compass

It uses a shared I2C bus with MS65611 which causes noise on the baro
reads. This will rely on the external compass instead of the internal
one.

@LorenzMeier @zehortigoza @lfelipe


Update to 2.3.0

[ ] Documentation
[ ] Update showcase apps and tools
[ ] Publish packages
[ ] Docker image
[ ] Release

#121


consider the change in toggle also as filter property modification

Issue:- https://issues.redhat.com/browse/DBZ-3102

I put a comment on the JIRA - I'm thinking maybe just disable the toggle group if there is no value?  wdyt?

@mdrillin I have updated the PR.
Since patternFly does not have a disable option for ToggleGroup i had to disable the ToggleGroupItem individually. Also added this to their issue. https://github.com/patternfly/patternfly-react/issues/5809


🚀 Feature: Use usage attribute instead of anthropic.count_tokens()

Which component is this feature for?
Anthropic Instrumentation
🔖 Feature description
Getting more accurate numbers on token usage, including the token cost of images, by using the usage attribute from the anthropic response.
🎤 Why is this feature needed ?
The description of the function says that the function is only accurate for older models such as Claude 2.1. I think the majority of people use the later 3.X models for which this function gives a very rough estimate. Anthropic say that the usage attribute on the response should be used instead.
def count_tokens(
        self,
        text: str,
    ) -> int:
        """Count the number of tokens in a given string.

        Note that this is only accurate for older models, e.g. `claude-2.1`. For newer
        models this can only be used as a _very_ rough estimate, instead you should rely
        on the `usage` property in the response for exact counts.
        """
        # Note: tokenizer is untyped
        tokenizer = self.get_tokenizer()
        encoded_text = tokenizer.encode(text)  # type: ignore
        return len(encoded_text.ids)  # type: ignore

✌ How do you aim to achieve this?
Update the anthropic instrumentation to use the token count from the usage attribute of the response instead of calling the count_token function.
🔄 Additional Information
No response
👀 Have you spent some time to check if this feature request has been raised before?

[X] I checked and didn't find similar issue

Are you willing to submit PR?
None

Can you please assign this to me @coffecup25 ?

@sahil9001 Doesn't seem like I can do that. You probably have to talk with one of the maintainers of the repo.


Remove duplicates from sorted array

I would like to solve this question in O(N) time and O(1) space complexity.

You can start working on this issue. All the best!


Error while using live LIDAR data from Mid 70 lidar

We are using a Livox Mid 70 lidar and trying to run the livox_detection package.
it works perfectly with the provided ros bag. but when we try to run the same program with the live LIDAR data, we see the follow errors: IndexError: too many indices for array on line 197, in LivoxCallback
[ERROR] [1658247201.950686]: bad callback: <bound method Detector.LivoxCallback of <__main__.Detector object at 0x7f6f3226cf10>>
Traceback (most recent call last):
  File "/opt/ros/noetic/lib/python3/dist-packages/rospy/topics.py", line 750, in _invoke_callback
    cb(msg)
  File "livox_rosdetection.py", line 197, in LivoxCallback
    pointcloud_msg = pcl2.create_cloud_xyz32(header, points_list[:, 0:3])
IndexError: too many indices for array

any help would be appreciated.

The line I have liked below is the problem. We changed the thresholds and we are able to see the points.
https://github.com/Livox-SDK/livox_detection/blob/fe2bd7fed80ec9a1c9f0880936a4c6ca9d508678/livox_rosdetection.py#L190


Allow using screenscraper.fr for scraping media

Hi,
I've been using screenscraper.fr for years through Skraper, it would be nice being able to use it in Daijishou, especially since you can log in and have a dedicated bandwidth. Recently arcade scraping has been disastrous in Daijishou, it would be nice to have an alternative.

https://github.com/TapiocaFox/Daijishou/issues/194#issuecomment-1440150563


Remove patch 10: Clean up and test the UUID code patch

Patch 10 contains a better replacement for replaceAll, but I think adding a method to the utility class and adding unit tests is a little much for removing the word All twice. There's no need to unit test a standard library method, that's Oracle's job. I think a patch to change replaceAll to replace is valid, but the rest is overkill.

Here's an edited patch of it:
From c5c7f68d947f366fef739e0ac3a655baed507bfe Mon Sep 17 00:00:00 2001
From: Jadon Fowler<EMAIL_ADDRESS>Date: Thu, 19 May 2016 18:13:48 -0600
Subject: [PATCH] Optimize conversion to Mojang-style UUIDs by avoiding regex

diff --git a/api/src/main/java/net/md_5/bungee/api/ServerPing.java b/api/src/main/java/net/md_5/bungee/api/ServerPing.java
index 314a1d2..6804ad9 100644
--- a/api/src/main/java/net/md_5/bungee/api/ServerPing.java
+++ b/api/src/main/java/net/md_5/bungee/api/ServerPing.java
@@ -73,7 +73,7 @@ public class ServerPing

         public String getId()
         {
-            return uniqueId.toString().replaceAll( "-", "" );
+            return uniqueId.toString().replace( "-", "" );
         }
     }

diff --git a/proxy/src/main/java/net/md_5/bungee/connection/InitialHandler.java b/proxy/src/main/java/net/md_5/bungee/connection/InitialHandler.java
index dab6ef2..ad19168 100644
--- a/proxy/src/main/java/net/md_5/bungee/connection/InitialHandler.java
+++ b/proxy/src/main/java/net/md_5/bungee/connection/InitialHandler.java
@@ -603,7 +603,7 @@ public class InitialHandler extends PacketHandler implements PendingConnection
     @Override
     public String getUUID()
     {
-        return uniqueId.toString().replaceAll( "-", "" );
+        return uniqueId.toString().replace( "-", "" );
     }

     @Override
--
2.8.3

The methods are overridden in patch 11 already, so I don't see the point here.


Update Kubernetes Client

Currently, Kanali is using v1.5.7 of the k8s.io/kubernetes client. This needs be updated. Since there were some major changes to this client starting with v1.6, this may be involved.

Going to use<EMAIL_ADDRESS>

received an update on a issue linked above:

suggested that this might be fixed with CRDs and that this problem might just be localized to TPRs.

In particular, the serialization of list kinds from the API server using TPRs used a guess at what the valid ListKind may be. CRDs have a field for the user to specify the actual value.

In summary, it appears that moving to CRDs might resolve this issue. Hence, this issue will be solved in conjunction with #3


Duration does not change after -r 2x

Do I understand correctly that after running butterflow -r 2x in.mp4 the output video doubles in duration? If it was 10s it becomes 20s?
I'm running into an issue when the command executes without errors, but I get Drop every: 3 and the video retains the initial duration.

-r sets the playback rate/frame rate. Your command doubled the number of frames in the video and the rate at which it's played back, but it's duration is unchanged - as it should.
You'll need to use -s a=<time>,b=<time>,spd=<speed from 0-1> to alter the duration. Setting spd=0.5 would double the duration, spd=0.25 would 4x the duration, spd=0.15 would 6.67x the duration, and so on. The exact command you're looking for is butterflow -v -s a=0,b=end,spd=0.5 in.mp4.
You saw Drop every: X because BF interpolated too many frames and had to drop them to meet the target number of frames to write. It's not an issue. It's only an issue, a minor one, when BF has to drop original frames when doing slowmo or rate increases. It will warn about that.

Thanks for the detailed explanation. It all makes sense. I checked and the output video's frame rate is doubled as expected.


Configurable download location?

Current workflow:

Go to a page.
Click on the extension.
Click on "download".
Move from your downloads folder to your preferred location (way too many clicks).

Proposed workflow:

Have the configurable download location (example: ~/notes/articles)
Find an article.
Click on the extension.
Click on "download".
The file gets automatically put in the right location.

To be honest I have no idea if it's possible to do this with the add-ons, but it would definitely save seconds each time I want to trigger the add-on.

I've had a bit of a look into this, and I don't think it's possible, unfortunately.
I can specify whether or not to show the Save As dialog, and if I specify not, it will just do whatever the browser does by default - which could be the Save As dialog, or just download to the downloads folder. See this link.
I can specify a path, but it will be relative to the downloads folder, unfortunately. Absolute paths, empty paths, and paths containing back-references (../) will cause an error


Bug: URLs are generated from deprecated username field

I created a scrapbook and saw that my scrapbook username was quite verbose (JessicaCard-U031W2WCX3J).
I believe this is because scrappy might be using the now-deprecated username field from the Slack API, and users added to the Hack Club Slack after the deprecation have their username fields automatically set to their ID's for backwards compatibility.
If this is correct, I think scrappy would want to end up using display_name or display_name_normalized in the user’s profile object.
@MatthewStanciu mentioned, as a potential pitfall:

ALSO I think I know why usernames are generated this way: sometimes two people would have the same or similar names so scrapbook would set their username to undefined and not actually generate a profile for them. This was probably a hacky workaround. Keep that in mind if you edit the username generation thing!

If we wanted to switch away from this we could:

Check if display_name is used by another user
If it isn't set that with snake case or something as the username
Otherwise use id as a fallback

@sampoder nice, I like that and that it would have a fallback. I wonder if there could also be a / command eventually to change your name 🤔

@jessicard /scrappy-setusername does that :D

@exu3 YA'LL ARE GENIUSES omg I can fix my naaame! thank you 🙇

with the set username command I don't even know if it is worth fixing this. maybe just adding a section in https://scrapbook.hackclub.com/about/ for people like me 😆

Added the documentation into /about, closing this since it doesn't need to be fixed!


fix syntax highlighting and missing curly brace

Used code specifiers where appropriate to get syntax highlighting. View the rich diff (button in the top of the diff toolbar) for a better view of the changes.

This is included in #16.


Warning About Multiple CPU Support

Warn that the cpu parsing of the proc file is quite intensive, and may lag the widget for higher end devices with multiple cpus

Fixed via #11 and #12
The code cleanup was awesome as of this commit: 424ad93f9fd7bdcc00cf0070de4a6542564461fb


Fluigi tree not importing

When you upload a JSON file from Fluigi the tree feature doesn't import properly.

This appears to primarily be an incompatibility between how 3DuF and Fluigi define the ends of the trees. Will review with @rkrishnasanka

We have an updated version of TREE that needs to be changed in Fluigi/MINT.  Which works correctly over here.


FreeBSD: A realistic comment about CDE

CDE is certainly more secure than it was in the 1990's. Additionally, calendar and tooltalk database server are not enabled by default, not needed, nor should they be enabled, unless one wants to use the CDE supplied calendar or CDE supplied database. CDE will function without either enabled.

Thanks for the input!


TestContext lack of thread-safety breaks tests classes using fluent API running in parallel

I tried running xUnit tests with BDDfy's fluent API. When I ran each test class on its own everything worked, but when running several test classes in parallel there were non-deterministic errors coming from TestContext class. I examined the code and saw there is a static mutable dictionary inside the class, accessed without locks.
Possible solutions:

Use ConcurrentDictionary, its semantics are exactly what TestContext needs (preferred, but requires .Net 4 and above)
Use locks when accessing the dictionary (.Net 2 and above)

I think ConcurrentDictionary might be a good solution. What do people think of raising BDDfy to .Net 4?

Most things seem to support 4.5 only these days, bumnping to .NET 4 is fine, you might just want to bump major version.

So, BDDfy 5 then?
Do you think we should go to 4.5 then, or stick to 4?
How about Microsoft ending support for .NET Framework 4, 4.5 and 4.5.1? Should we maybe go to 4.5.2?

Hi,
I'm the original issuer, also from Microsoft, and I can tell you that
Microsoft isn't ending support for those frameworks. We in fact still use
.Net 4.5.1 internally. Most moved to .Net 4.5 to enjoy the async/await
goodies.
Thanks for your fast reponse
2016-01-31 16:09 GMT+02:00 Michael Whelan<EMAIL_ADDRESS>
So, BDDfy 5 then?
Do you think we should go to 4.5 then, or stick to 4?
How about Microsoft ending support for .NET Framework 4, 4.5 and 4.5.1?
Should we maybe go to 4.5.2?
—
Reply to this email directly or view it on GitHub
https://github.com/TestStack/TestStack.BDDfy/issues/222#issuecomment-177508364
.

Oh? I was going by this blog post:
http://blogs.msdn.com/b/dotnet/archive/2015/12/09/support-ending-for-the-net-framework-4-4-5-and-4-5-1.aspx

I'm aware of that, and still there are some developers that won't do that
upgrade for coming time, including myself and I'd really like to keep using
BDDfy and receive the fix.
2016-01-31 16:26 GMT+02:00 Michael Whelan<EMAIL_ADDRESS>
Oh? I was going by this blog post:
http://blogs.msdn.com/b/dotnet/archive/2015/12/09/support-ending-for-the-net-framework-4-4-5-and-4-5-1.aspx
—
Reply to this email directly or view it on GitHub
https://github.com/TestStack/TestStack.BDDfy/issues/222#issuecomment-177511961
.

Yes, we want to support as many people as we can so no need to upgrade any higher than the features we need. I'm happy to move to .Net 4 and the ConcurrentDictionary that you suggested.
Is this change to TestContext with ConcurrentDictionary something you might be able to submit a PR for?

I'm waiting for response from Lawyers about contributing to OSS on behalf
of Microsoft, unfortunate legal issues. If they won't response in the next
few days I'll submit a PR myself, though it'll be my first time
contributing to an OSS using Github so it might take a while to get right.
2016-01-31 16:44 GMT+02:00 Michael Whelan<EMAIL_ADDRESS>
Yes, we want to support as many people as we can so no need to upgrade any
higher than the features we need. I'm happy to move to .Net 4 and the
ConcurrentDictionary that you suggested.
Is this change to TestContext with ConcurrentDictionary something you
might be able to submit a PR for?
—
Reply to this email directly or view it on GitHub
https://github.com/TestStack/TestStack.BDDfy/issues/222#issuecomment-177514275
.

Fair enough. Well, I'm keen to try to solve the problem as parallel testing is an important use case.
Could you possibly provide a test case or two that illustrates the non-deterministic errors you were getting from the TestContext class?

I'll do my best to get to it later, meanwhile I'll simply point out that I
attempted to run xUnit tests using ReSharper with default parallelization
settings which means you get each test class running in parallel with other
test classes. All of them used BDDfy's fluent API, and when I ran 8 of them
all at once in a single ReSharper tests session some of them were failing
non-deterministicly due to weird dictionary concurrency issues. Is that
description enough or would you like me to upload fictive test classes to
the issue's discussion? Given the non-deterministic nature of threading
issues I think we should simply acknowledge there's a real problem with
mutable static state being used unprotected. That's also against .Net
standards - static methods must always be thread safe.
2016-01-31 16:57 GMT+02:00 Michael Whelan<EMAIL_ADDRESS>
Fair enough. Well, I'm keen to try to solve the problem as parallel
testing is an important use case.
Could you possibly provide a test case or two that illustrates the
non-deterministic errors you were getting from the TestContext class?
—
Reply to this email directly or view it on GitHub
https://github.com/TestStack/TestStack.BDDfy/issues/222#issuecomment-177516402
.

That is helpful, but fictive test classes would be more concrete to work with! :-)

Hi, thank you very much for fixing this :)
When will a 4.2.1 version be released so this bug fix could reach BDDfy users?

This was released a while back. We just forgot to update this issue and close it off. Thanks for reporting @Eldar1205 and for your patience.


channel not re-selected on edit, related to capitalization

channel won't be reselected if it has capitals in it - somewhere we normalize the channel name.
I created a test with @Test-1 and @test-1, and when editing a claim signed by @Test-1, it selects @test-1.
This channel is @MyLBRYChannel:

Fixed in my branch


{compute} Bump disk 2021-04-01

Description

Testing Guide

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change.
[Component Name 2] az command b: Add some customer-facing feature.

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

[ ] I adhere to the Error Handling Guidelines.

compute


Build Error AVS_SDK

IMPORTANT: Before you create an issue, please take a look at our Issue Reporting Guide.
Briefly summarize your issue:

I am trying to build AVS-SDK in my machine.
What is the expected behavior?

While doing the build, i am getting error. Expected is to get the build successfully.
What behavior are you observing?

Observing error while building.
With the error log:
cmake: /usr/local/lib/libcurl.so.4: no version information available (required by cmake)
Creating the build directory for the AlexaClientSDK with build type: RELEASE
No keyword detector type specified, skipping build of keyword detector.
CMake Warning (dev) at ThirdParty/googletest-release-1.8.0/CMakeLists.txt:3 (project):
Policy CMP0048 is not set: project() command manages VERSION variables.
Run "cmake --help-policy CMP0048" for policy details.  Use the cmake_policy
command to set the policy and suppress this warning.
The following variable(s) would be set to empty:
PROJECT_VERSION
PROJECT_VERSION_MAJOR
PROJECT_VERSION_MINOR
PROJECT_VERSION_PATCH

This warning is for project developers.  Use -Wno-dev to suppress it.
CMake Warning (dev) at ThirdParty/googletest-release-1.8.0/googlemock/CMakeLists.txt:40 (project):
Policy CMP0048 is not set: project() command manages VERSION variables.
Run "cmake --help-policy CMP0048" for policy details.  Use the cmake_policy
command to set the policy and suppress this warning.
The following variable(s) would be set to empty:
PROJECT_VERSION
PROJECT_VERSION_MAJOR
PROJECT_VERSION_MINOR
PROJECT_VERSION_PATCH

This warning is for project developers.  Use -Wno-dev to suppress it.
CMake Warning (dev) at ThirdParty/googletest-release-1.8.0/googletest/CMakeLists.txt:47 (project):
Policy CMP0048 is not set: project() command manages VERSION variables.
Run "cmake --help-policy CMP0048" for policy details.  Use the cmake_policy
command to set the policy and suppress this warning.
The following variable(s) would be set to empty:
PROJECT_VERSION
PROJECT_VERSION_MAJOR
PROJECT_VERSION_MINOR
PROJECT_VERSION_PATCH

This warning is for project developers.  Use -Wno-dev to suppress it.
-- Could NOT find GTest (missing:  GTEST_LIBRARY GTEST_INCLUDE_DIR GTEST_MAIN_LIBRARY)
-- Could NOT find GTest (missing:  GTEST_LIBRARY GTEST_INCLUDE_DIR GTEST_MAIN_LIBRARY)
Creating the build directory for the ACL with build type: RELEASE
No keyword detector type specified, skipping build of keyword detector.
-- Could NOT find GTest (missing:  GTEST_LIBRARY GTEST_INCLUDE_DIR GTEST_MAIN_LIBRARY)
Creating the build directory for the Authorization with build type: RELEASE
No keyword detector type specified, skipping build of keyword detector.
Creating the build directory for the CBLAuthDelegate with build type: RELEASE
No keyword detector type specified, skipping build of keyword detector.
Creating the build directory for the ADSL with build type: RELEASE
No keyword detector type specified, skipping build of keyword detector.
-- Could NOT find GTest (missing:  GTEST_LIBRARY GTEST_INCLUDE_DIR GTEST_MAIN_LIBRARY)
Creating the build directory for the AFML with build type: RELEASE
No keyword detector type specified, skipping build of keyword detector.
-- Could NOT find GTest (missing:  GTEST_LIBRARY GTEST_INCLUDE_DIR GTEST_MAIN_LIBRARY)
Creating the build directory for the CertifiedSender with build type: RELEASE
No keyword detector type specified, skipping build of keyword detector.
-- Could NOT find GTest (missing:  GTEST_LIBRARY GTEST_INCLUDE_DIR GTEST_MAIN_LIBRARY)
Creating the build directory for the ContextManager with build type: RELEASE
No keyword detector type specified, skipping build of keyword detector.
-- Could NOT find GTest (missing:  GTEST_LIBRARY GTEST_INCLUDE_DIR GTEST_MAIN_LIBRARY)
Creating the build directory for the DCFDelegate with build type: RELEASE
No keyword detector type specified, skipping build of keyword detector.
-- Could NOT find GTest (missing:  GTEST_LIBRARY GTEST_INCLUDE_DIR GTEST_MAIN_LIBRARY)
Creating the build directory for the MediaPlayer with build type: RELEASE
No keyword detector type specified, skipping build of keyword detector.
-- Could NOT find GTest (missing:  GTEST_LIBRARY GTEST_INCLUDE_DIR GTEST_MAIN_LIBRARY)
Creating the build directory for the PlaylistParser with build type: RELEASE
No keyword detector type specified, skipping build of keyword detector.
-- Could NOT find GTest (missing:  GTEST_LIBRARY GTEST_INCLUDE_DIR GTEST_MAIN_LIBRARY)
-- Could NOT find GTest (missing:  GTEST_LIBRARY GTEST_INCLUDE_DIR GTEST_MAIN_LIBRARY)
Creating the build directory for the CapabilityAgents with build type: RELEASE
No keyword detector type specified, skipping build of keyword detector.
Creating the build directory for the AIP with build type: RELEASE
No keyword detector type specified, skipping build of keyword detector.
-- Could NOT find GTest (missing:  GTEST_LIBRARY GTEST_INCLUDE_DIR GTEST_MAIN_LIBRARY)
Creating the build directory for the Alerts with build type: RELEASE
No keyword detector type specified, skipping build of keyword detector.
-- Could NOT find GTest (missing:  GTEST_LIBRARY GTEST_INCLUDE_DIR GTEST_MAIN_LIBRARY)
Creating the build directory for the AudioPlayer with build type: RELEASE
No keyword detector type specified, skipping build of keyword detector.
-- Could NOT find GTest (missing:  GTEST_LIBRARY GTEST_INCLUDE_DIR GTEST_MAIN_LIBRARY)
Creating the build directory for the ExternalMediaPlayer with build type: RELEASE
No keyword detector type specified, skipping build of keyword detector.
Creating the build directory for the Notifications with build type: RELEASE
No keyword detector type specified, skipping build of keyword detector.
-- Could NOT find GTest (missing:  GTEST_LIBRARY GTEST_INCLUDE_DIR GTEST_MAIN_LIBRARY)
-- Could NOT find GTest (missing:  GTEST_LIBRARY GTEST_INCLUDE_DIR GTEST_MAIN_LIBRARY)
Creating the build directory for the SpeakerManager with build type: RELEASE
No keyword detector type specified, skipping build of keyword detector.
-- Could NOT find GTest (missing:  GTEST_LIBRARY GTEST_INCLUDE_DIR GTEST_MAIN_LIBRARY)
Creating the build directory for the SpeechSynthesizer with build type: RELEASE
No keyword detector type specified, skipping build of keyword detector.
-- Could NOT find GTest (missing:  GTEST_LIBRARY GTEST_INCLUDE_DIR GTEST_MAIN_LIBRARY)
-- Could NOT find GTest (missing:  GTEST_LIBRARY GTEST_INCLUDE_DIR GTEST_MAIN_LIBRARY)
-- Could NOT find GTest (missing:  GTEST_LIBRARY GTEST_INCLUDE_DIR GTEST_MAIN_LIBRARY)
-- Could NOT find GTest (missing:  GTEST_LIBRARY GTEST_INCLUDE_DIR GTEST_MAIN_LIBRARY)
Creating the build directory for the Integration with build type: RELEASE
No keyword detector type specified, skipping build of keyword detector.
-- Could NOT find GTest (missing:  GTEST_LIBRARY GTEST_INCLUDE_DIR GTEST_MAIN_LIBRARY)
-- Please fill //local/mnt/workspace/avs-sdk/sdk-folder/sdk-build/Integration/AlexaClientSDKConfig.json before you execute integration tests.
Skipping build of NetworkIntegrationTests.cpp.
Creating the build directory for the ApplicationUtilities with build type: RELEASE
No keyword detector type specified, skipping build of keyword detector.
Creating the build directory for the DefaultClient with build type: RELEASE
No keyword detector type specified, skipping build of keyword detector.
Creating the build directory for the ESP with build type: RELEASE
No keyword detector type specified, skipping build of keyword detector.
Creating the build directory for the RegistrationManager with build type: RELEASE
No keyword detector type specified, skipping build of keyword detector.
-- Could NOT find GTest (missing:  GTEST_LIBRARY GTEST_INCLUDE_DIR GTEST_MAIN_LIBRARY)
Creating the build directory for the SampleApp with build type: RELEASE
No keyword detector type specified, skipping build of keyword detector.
Creating the build directory for the Storage with build type: RELEASE
No keyword detector type specified, skipping build of keyword detector.
Creating the build directory for the SQLiteStorage with build type: RELEASE
No keyword detector type specified, skipping build of keyword detector.
-- Could NOT find GTest (missing:  GTEST_LIBRARY GTEST_INCLUDE_DIR GTEST_MAIN_LIBRARY)
-- Configuring done
-- Generating done
-- Build files have been written to: //local/mnt/workspace/avs-sdk/sdk-folder/sdk-build
/usr/bin/cmake: /usr/local/lib/libcurl.so.4: no version information available (required by /usr/bin/cmake)
/usr/bin/cmake: /usr/local/lib/libcurl.so.4: no version information available (required by /usr/bin/cmake)
make[1]: *** No rule to make target '//local/mnt/workspace/avs-sdk/sdk-folder/sdk-build/all'.  Stop.
Makefile:138: recipe for target 'all' failed
make: *** [all] Error 2
Provide the steps to reproduce the issue, if applicable:

followed the link:https://github.com/alexa/avs-device-sdk/wiki/Ubuntu-Linux-Quick-Start-Guide
Tell us about your environment:

What version of the AVS Device SDK are you using?
  <x.y.z>

Enviroment: Ubuntu 16.04.
AVS-Latest
Tell us what hardware you're using:

[x] Desktop / Laptop
[ ] Raspberry Pi
[ ] Other - tell us more:
Desktop

Tell us about your OS (Type & version):

[x] Linux
[ ] MacOS
[ ] Raspbian Stretch
[ ] Raspbian Jessy
[ ] Other - tell us more:
LINUX-16.04

Hi @dipankjain,
Could you show me the exact cmake command you used? Could you also try running cmake and then make as separate commands and posting the output?
Fede

CMAKE COMMAND USED: cmake /$HOME/sdk-folder/sdk-source/avs-device-sdk -DSENSORY_KEY_WORD_DETECTOR=OFF -DGSTREAMER_MEDIA_PLAYER=ON -DPORTAUDIO=ON -DPORTAUDIO_LIB_PATH=/$HOME/sdk-folder/third-party/portaudio/lib/.libs/libportaudio.a -DPORTAUDIO_INCLUDE_DIR=/$HOME/sdk-folder/third-party/portaudio/include && makecmake /$HOME/sdk-folder/sdk-source/avs-device-sdk -DSENSORY_KEY_WORD_DETECTOR=OFF -DGSTREAMER_MEDIA_PLAYER=ON -DPORTAUDIO=ON -DPORTAUDIO_LIB_PATH=/$HOME/sdk-folder/third-party/portaudio/lib/.libs/libportaudio.a
Output:
cmake: /usr/local/lib/libcurl.so.4: no version information available (required by cmake)
Creating the build directory for the AlexaClientSDK with build type: RELEASE
No keyword detector type specified, skipping build of keyword detector.
CMake Warning (dev) at ThirdParty/googletest-release-1.8.0/CMakeLists.txt:3 (project):
Policy CMP0048 is not set: project() command manages VERSION variables.
Run "cmake --help-policy CMP0048" for policy details.  Use the cmake_policy
command to set the policy and suppress this warning.
The following variable(s) would be set to empty:
PROJECT_VERSION
PROJECT_VERSION_MAJOR
PROJECT_VERSION_MINOR
PROJECT_VERSION_PATCH

This warning is for project developers.  Use -Wno-dev to suppress it.
CMake Warning (dev) at ThirdParty/googletest-release-1.8.0/googlemock/CMakeLists.txt:40 (project):
Policy CMP0048 is not set: project() command manages VERSION variables.
Run "cmake --help-policy CMP0048" for policy details.  Use the cmake_policy
command to set the policy and suppress this warning.
The following variable(s) would be set to empty:
PROJECT_VERSION
PROJECT_VERSION_MAJOR
PROJECT_VERSION_MINOR
PROJECT_VERSION_PATCH

This warning is for project developers.  Use -Wno-dev to suppress it.
CMake Warning (dev) at ThirdParty/googletest-release-1.8.0/googletest/CMakeLists.txt:47 (project):
Policy CMP0048 is not set: project() command manages VERSION variables.
Run "cmake --help-policy CMP0048" for policy details.  Use the cmake_policy
command to set the policy and suppress this warning.
The following variable(s) would be set to empty:
PROJECT_VERSION
PROJECT_VERSION_MAJOR
PROJECT_VERSION_MINOR
PROJECT_VERSION_PATCH

This warning is for project developers.  Use -Wno-dev to suppress it.
-- Could NOT find GTest (missing:  GTEST_LIBRARY GTEST_MAIN_LIBRARY)
-- Could NOT find GTest (missing:  GTEST_LIBRARY GTEST_MAIN_LIBRARY)
Creating the build directory for the ACL with build type: RELEASE
No keyword detector type specified, skipping build of keyword detector.
-- Could NOT find GTest (missing:  GTEST_LIBRARY GTEST_MAIN_LIBRARY)
Creating the build directory for the Authorization with build type: RELEASE
No keyword detector type specified, skipping build of keyword detector.
Creating the build directory for the CBLAuthDelegate with build type: RELEASE
No keyword detector type specified, skipping build of keyword detector.
Creating the build directory for the ADSL with build type: RELEASE
No keyword detector type specified, skipping build of keyword detector.
-- Could NOT find GTest (missing:  GTEST_LIBRARY GTEST_MAIN_LIBRARY)
Creating the build directory for the AFML with build type: RELEASE
No keyword detector type specified, skipping build of keyword detector.
-- Could NOT find GTest (missing:  GTEST_LIBRARY GTEST_MAIN_LIBRARY)
Creating the build directory for the CertifiedSender with build type: RELEASE
No keyword detector type specified, skipping build of keyword detector.
-- Could NOT find GTest (missing:  GTEST_LIBRARY GTEST_MAIN_LIBRARY)
Creating the build directory for the ContextManager with build type: RELEASE
No keyword detector type specified, skipping build of keyword detector.
-- Could NOT find GTest (missing:  GTEST_LIBRARY GTEST_MAIN_LIBRARY)
Creating the build directory for the DCFDelegate with build type: RELEASE
No keyword detector type specified, skipping build of keyword detector.
-- Could NOT find GTest (missing:  GTEST_LIBRARY GTEST_MAIN_LIBRARY)
Creating the build directory for the MediaPlayer with build type: RELEASE
No keyword detector type specified, skipping build of keyword detector.
-- Could NOT find GTest (missing:  GTEST_LIBRARY GTEST_MAIN_LIBRARY)
Creating the build directory for the PlaylistParser with build type: RELEASE
No keyword detector type specified, skipping build of keyword detector.
-- Could NOT find GTest (missing:  GTEST_LIBRARY GTEST_MAIN_LIBRARY)
-- Could NOT find GTest (missing:  GTEST_LIBRARY GTEST_MAIN_LIBRARY)
Creating the build directory for the CapabilityAgents with build type: RELEASE
No keyword detector type specified, skipping build of keyword detector.
Creating the build directory for the AIP with build type: RELEASE
No keyword detector type specified, skipping build of keyword detector.
-- Could NOT find GTest (missing:  GTEST_LIBRARY GTEST_MAIN_LIBRARY)
Creating the build directory for the Alerts with build type: RELEASE
No keyword detector type specified, skipping build of keyword detector.
-- Could NOT find GTest (missing:  GTEST_LIBRARY GTEST_MAIN_LIBRARY)
Creating the build directory for the AudioPlayer with build type: RELEASE
No keyword detector type specified, skipping build of keyword detector.
-- Could NOT find GTest (missing:  GTEST_LIBRARY GTEST_MAIN_LIBRARY)
Creating the build directory for the ExternalMediaPlayer with build type: RELEASE
No keyword detector type specified, skipping build of keyword detector.
Creating the build directory for the Notifications with build type: RELEASE
No keyword detector type specified, skipping build of keyword detector.
-- Could NOT find GTest (missing:  GTEST_LIBRARY GTEST_MAIN_LIBRARY)
-- Could NOT find GTest (missing:  GTEST_LIBRARY GTEST_MAIN_LIBRARY)
Creating the build directory for the SpeakerManager with build type: RELEASE
No keyword detector type specified, skipping build of keyword detector.
-- Could NOT find GTest (missing:  GTEST_LIBRARY GTEST_MAIN_LIBRARY)
Creating the build directory for the SpeechSynthesizer with build type: RELEASE
No keyword detector type specified, skipping build of keyword detector.
-- Could NOT find GTest (missing:  GTEST_LIBRARY GTEST_MAIN_LIBRARY)
-- Could NOT find GTest (missing:  GTEST_LIBRARY GTEST_MAIN_LIBRARY)
-- Could NOT find GTest (missing:  GTEST_LIBRARY GTEST_MAIN_LIBRARY)
-- Could NOT find GTest (missing:  GTEST_LIBRARY GTEST_MAIN_LIBRARY)
Creating the build directory for the Integration with build type: RELEASE
No keyword detector type specified, skipping build of keyword detector.
-- Could NOT find GTest (missing:  GTEST_LIBRARY GTEST_MAIN_LIBRARY)
-- Please fill //local/mnt/workspace/avs-sdk/sdk-folder/sdk-build/Integration/AlexaClientSDKConfig.json before you execute integration tests.
Skipping build of NetworkIntegrationTests.cpp.
Creating the build directory for the ApplicationUtilities with build type: RELEASE
No keyword detector type specified, skipping build of keyword detector.
Creating the build directory for the DefaultClient with build type: RELEASE
No keyword detector type specified, skipping build of keyword detector.
Creating the build directory for the ESP with build type: RELEASE
No keyword detector type specified, skipping build of keyword detector.
Creating the build directory for the RegistrationManager with build type: RELEASE
No keyword detector type specified, skipping build of keyword detector.
-- Could NOT find GTest (missing:  GTEST_LIBRARY GTEST_MAIN_LIBRARY)
Creating the build directory for the SampleApp with build type: RELEASE
No keyword detector type specified, skipping build of keyword detector.
Creating the build directory for the Storage with build type: RELEASE
No keyword detector type specified, skipping build of keyword detector.
Creating the build directory for the SQLiteStorage with build type: RELEASE
No keyword detector type specified, skipping build of keyword detector.
-- Could NOT find GTest (missing:  GTEST_LIBRARY GTEST_MAIN_LIBRARY)
-- Configuring done
-- Generating done
-- Build files have been written to: //local/mnt/workspace/avs-sdk/sdk-folder/sdk-build
bash: makecmake: command not found
When Runnig MAKE COMMAND output is :
/usr/bin/cmake: /usr/local/lib/libcurl.so.4: no version information available (required by /usr/bin/cmake)
/usr/bin/cmake: /usr/local/lib/libcurl.so.4: no version information available (required by /usr/bin/cmake)
make[1]: *** No rule to make target '//local/mnt/workspace/avs-sdk/sdk-folder/sdk-build/all'.  Stop.
Makefile:138: recipe for target 'all' failed
make: *** [all] Error 2

gstreamer error has gone post doing:
sudo apt-get install cmake libgtest-dev
cd /usr/src/gtest
sudo cmake CMakeLists.txt
sudo make
copy or symlink libgtest.a and libgtest_main.a to your /usr/lib folder
sudo cp *.a /usr/lib
Command:
cmake /{HOME}/sdk-folder/sdk-source/avs-device-sdk -DSENSORY_KEY_WORD_DETECTOR=OFF -DGSTREAMER_MEDIA_PLAYER=ON -DPORTAUDIO=ON -DPORTAUDIO_LIB_PATH=/{HOME}/sdk-folder/third-party/portaudio/lib/.libs/libportaudio.a -DPORTAUDIO_INCLUDE_DIR=/{HOME}/sdk-folder/third-party/portaudio/include && make
But still getting error:
CMake Error: The source directory "/{HOME}/sdk-folder/sdk-source/avs-device-sdk" does not exist.
Specify --help for usage, or press the help button on the CMake GUI.
dipankj@dipankj-linux://local/mnt/workspace/avs-sdk$ cmake /$HOME/sdk-folder/sdk-source/avs-device-sdk -DSENSORY_KEY_WORD_DETECTOR=OFF -DGSTREAMER_MEDIA_PLAYER=ON -DPORTAUDIO=ON -DPORTAUDIO_LIB_PATH=/$HOME/sdk-folder/third-party/portaudio/lib/.libs/libportaudio.a -DPORTAUDIO_INCLUDE_DIR=/$HOME/sdk-folder/third-party/portaudio/include && make
-- The CXX compiler identification is GNU 5.4.0
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
No build type specified, defaulting to Release.
Creating the build directory for the AlexaClientSDK with build type: RELEASE
No keyword detector type specified, skipping build of keyword detector.
-- Found PkgConfig: /usr/bin/pkg-config (found version "0.29.1")
-- Checking for modules 'gstreamer-1.0>=1.8;gstreamer-app-1.0>=1.8'
--   Found gstreamer-1.0, version 1.12.4
--   Found gstreamer-app-1.0, version 1.12.4
CMake Warning (dev) at ThirdParty/googletest-release-1.8.0/CMakeLists.txt:3 (project):
Policy CMP0048 is not set: project() command manages VERSION variables.
Run "cmake --help-policy CMP0048" for policy details.  Use the cmake_policy
command to set the policy and suppress this warning.
The following variable(s) would be set to empty:
PROJECT_VERSION
PROJECT_VERSION_MAJOR
PROJECT_VERSION_MINOR
PROJECT_VERSION_PATCH

This warning is for project developers.  Use -Wno-dev to suppress it.
-- The C compiler identification is GNU 5.4.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
CMake Warning (dev) at ThirdParty/googletest-release-1.8.0/googlemock/CMakeLists.txt:40 (project):
Policy CMP0048 is not set: project() command manages VERSION variables.
Run "cmake --help-policy CMP0048" for policy details.  Use the cmake_policy
command to set the policy and suppress this warning.
The following variable(s) would be set to empty:
PROJECT_VERSION
PROJECT_VERSION_MAJOR
PROJECT_VERSION_MINOR
PROJECT_VERSION_PATCH

This warning is for project developers.  Use -Wno-dev to suppress it.
CMake Warning (dev) at ThirdParty/googletest-release-1.8.0/googletest/CMakeLists.txt:47 (project):
Policy CMP0048 is not set: project() command manages VERSION variables.
Run "cmake --help-policy CMP0048" for policy details.  Use the cmake_policy
command to set the policy and suppress this warning.
The following variable(s) would be set to empty:
PROJECT_VERSION
PROJECT_VERSION_MAJOR
PROJECT_VERSION_MINOR
PROJECT_VERSION_PATCH

This warning is for project developers.  Use -Wno-dev to suppress it.
-- Found PythonInterp: /usr/bin/python (found version "2.7.12")
-- Looking for pthread.h
-- Looking for pthread.h - found
-- Looking for pthread_create
-- Looking for pthread_create - not found
-- Looking for pthread_create in pthreads
-- Looking for pthread_create in pthreads - not found
-- Looking for pthread_create in pthread
-- Looking for pthread_create in pthread - found
-- Found Threads: TRUE
-- Found CURL: /usr/local/lib/libcurl.so (found suitable version "7.54.0", minimum required is "7.43.0")
-- Found GTest: /usr/lib/libgtest.a
Creating the build directory for the ACL with build type: RELEASE
No keyword detector type specified, skipping build of keyword detector.
Creating the build directory for the Authorization with build type: RELEASE
No keyword detector type specified, skipping build of keyword detector.
Creating the build directory for the CBLAuthDelegate with build type: RELEASE
No keyword detector type specified, skipping build of keyword detector.
Creating the build directory for the ADSL with build type: RELEASE
No keyword detector type specified, skipping build of keyword detector.
Creating the build directory for the AFML with build type: RELEASE
No keyword detector type specified, skipping build of keyword detector.
Creating the build directory for the CertifiedSender with build type: RELEASE
No keyword detector type specified, skipping build of keyword detector.
Creating the build directory for the ContextManager with build type: RELEASE
No keyword detector type specified, skipping build of keyword detector.
Creating the build directory for the DCFDelegate with build type: RELEASE
No keyword detector type specified, skipping build of keyword detector.
Creating the build directory for the MediaPlayer with build type: RELEASE
No keyword detector type specified, skipping build of keyword detector.
Creating the build directory for the PlaylistParser with build type: RELEASE
No keyword detector type specified, skipping build of keyword detector.
Creating the build directory for the CapabilityAgents with build type: RELEASE
No keyword detector type specified, skipping build of keyword detector.
Creating the build directory for the AIP with build type: RELEASE
No keyword detector type specified, skipping build of keyword detector.
Creating the build directory for the Alerts with build type: RELEASE
No keyword detector type specified, skipping build of keyword detector.
Creating the build directory for the AudioPlayer with build type: RELEASE
No keyword detector type specified, skipping build of keyword detector.
Creating the build directory for the ExternalMediaPlayer with build type: RELEASE
No keyword detector type specified, skipping build of keyword detector.
Creating the build directory for the Notifications with build type: RELEASE
No keyword detector type specified, skipping build of keyword detector.
Creating the build directory for the SpeakerManager with build type: RELEASE
No keyword detector type specified, skipping build of keyword detector.
Creating the build directory for the SpeechSynthesizer with build type: RELEASE
No keyword detector type specified, skipping build of keyword detector.
Creating the build directory for the ApplicationUtilities with build type: RELEASE
No keyword detector type specified, skipping build of keyword detector.
Creating the build directory for the DefaultClient with build type: RELEASE
No keyword detector type specified, skipping build of keyword detector.
Creating the build directory for the ESP with build type: RELEASE
No keyword detector type specified, skipping build of keyword detector.
Creating the build directory for the RegistrationManager with build type: RELEASE
No keyword detector type specified, skipping build of keyword detector.
Creating the build directory for the SampleApp with build type: RELEASE
No keyword detector type specified, skipping build of keyword detector.
Creating the build directory for the Storage with build type: RELEASE
No keyword detector type specified, skipping build of keyword detector.
Creating the build directory for the SQLiteStorage with build type: RELEASE
No keyword detector type specified, skipping build of keyword detector.
-- Checking for module 'sqlite3'
--   Found sqlite3, version 3.11.0
-- Found Doxygen: /usr/bin/doxygen (found version "1.8.11")
-- Configuring done
-- Generating done
-- Build files have been written to: //local/mnt/workspace/avs-sdk
make[1]: *** No rule to make target '//local/mnt/workspace/avs-sdk/all'.  Stop.
Makefile:138: recipe for target 'all' failed
make: *** [all] Error 2

With Command
cmake /$HOME/sdk-folder/sdk-source/avs-device-sdk -Wno-dev  -DSENSORY_KEY_WORD_DETECTOR=OFF -DGSTREAMER_MEDIA_PLAYER=ON -DPORTAUDIO=ON -DPORTAUDIO_LIB_PATH=/$HOME/sdk-folder/third-party/portaudio/lib/.libs/libportaudio.a -DPORTAUDIO_INCLUDE_DIR=/$HOME/sdk-folder/third-party/portaudio/include && make
Result
Creating the build directory for the AlexaClientSDK with build type: DEBUG
No keyword detector type specified, skipping build of keyword detector.
Creating the build directory for the ACL with build type: DEBUG
No keyword detector type specified, skipping build of keyword detector.
Creating the build directory for the Authorization with build type: DEBUG
No keyword detector type specified, skipping build of keyword detector.
Creating the build directory for the CBLAuthDelegate with build type: DEBUG
No keyword detector type specified, skipping build of keyword detector.
Creating the build directory for the ADSL with build type: DEBUG
No keyword detector type specified, skipping build of keyword detector.
Creating the build directory for the AFML with build type: DEBUG
No keyword detector type specified, skipping build of keyword detector.
Creating the build directory for the CertifiedSender with build type: DEBUG
No keyword detector type specified, skipping build of keyword detector.
Creating the build directory for the ContextManager with build type: DEBUG
No keyword detector type specified, skipping build of keyword detector.
Creating the build directory for the DCFDelegate with build type: DEBUG
No keyword detector type specified, skipping build of keyword detector.
Creating the build directory for the MediaPlayer with build type: DEBUG
No keyword detector type specified, skipping build of keyword detector.
Creating the build directory for the PlaylistParser with build type: DEBUG
No keyword detector type specified, skipping build of keyword detector.
Creating the build directory for the CapabilityAgents with build type: DEBUG
No keyword detector type specified, skipping build of keyword detector.
Creating the build directory for the AIP with build type: DEBUG
No keyword detector type specified, skipping build of keyword detector.
Creating the build directory for the Alerts with build type: DEBUG
No keyword detector type specified, skipping build of keyword detector.
Creating the build directory for the AudioPlayer with build type: DEBUG
No keyword detector type specified, skipping build of keyword detector.
Creating the build directory for the ExternalMediaPlayer with build type: DEBUG
No keyword detector type specified, skipping build of keyword detector.
Creating the build directory for the Notifications with build type: DEBUG
No keyword detector type specified, skipping build of keyword detector.
Creating the build directory for the SpeakerManager with build type: DEBUG
No keyword detector type specified, skipping build of keyword detector.
Creating the build directory for the SpeechSynthesizer with build type: DEBUG
No keyword detector type specified, skipping build of keyword detector.
Creating the build directory for the ApplicationUtilities with build type: DEBUG
No keyword detector type specified, skipping build of keyword detector.
Creating the build directory for the DefaultClient with build type: DEBUG
No keyword detector type specified, skipping build of keyword detector.
Creating the build directory for the ESP with build type: DEBUG
No keyword detector type specified, skipping build of keyword detector.
Creating the build directory for the RegistrationManager with build type: DEBUG
No keyword detector type specified, skipping build of keyword detector.
Creating the build directory for the SampleApp with build type: DEBUG
No keyword detector type specified, skipping build of keyword detector.
Creating the build directory for the Storage with build type: DEBUG
No keyword detector type specified, skipping build of keyword detector.
Creating the build directory for the SQLiteStorage with build type: DEBUG
No keyword detector type specified, skipping build of keyword detector.
-- Configuring done
-- Generating done
-- Build files have been written to: //local/mnt/workspace/avs-sdk/sdk-folder/sdk-build
make[1]: *** No rule to make target '//local/mnt/workspace/avs-sdk/sdk-folder/sdk-build/all'.  Stop.
Makefile:138: recipe for target 'all' failed
make: *** [all] Error 2

IT statered to build, but got stuck at
ir/SQLiteMessageStorage.cpp.o
[ 58%] Linking CXX shared library libCertifiedSender.so
[ 58%] Built target CertifiedSender
Scanning dependencies of target MessageStorageTest
[ 58%] Building CXX object CertifiedSender/test/CMakeFiles/MessageStorageTe                                                                                st.dir/MessageStorageTest.cpp.o
[ 58%] Linking CXX executable MessageStorageTest
[ 58%] Built target MessageStorageTest
Scanning dependencies of target CertifiedSenderTest
[ 58%] Building CXX object CertifiedSender/test/CMakeFiles/CertifiedSenderT                                                                                est.dir/CertifiedSenderTest.cpp.o
[ 58%] Linking CXX executable CertifiedSenderTest
[ 58%] Built target CertifiedSenderTest
Scanning dependencies of target ContextManager
[ 58%] Building CXX object ContextManager/src/CMakeFiles/ContextManager.dir                                                                                /ContextManager.cpp.o
[ 59%] Linking CXX shared library libContextManager.so
[ 59%] Built target ContextManager
Scanning dependencies of target ContextManagerTest
[ 59%] Building CXX object ContextManager/test/CMakeFiles/ContextManagerTes                                                                                t.dir/ContextManagerTest.cpp.o
[ 59%] Linking CXX executable ContextManagerTest
[ 59%] Built target ContextManagerTest
Scanning dependencies of target DCFDelegate
[ 59%] Building CXX object DCFDelegate/src/CMakeFiles/DCFDelegate.dir/DCFDe                                                                                legate.cpp.o
//local/mnt/workspace/avs-sdk/sdk-folder/sdk-source/avs-device-sdk/DCFDeleg                                                                                ate/src/DCFDelegate.cpp:28:44: fatal error: ACL/Transport/TransportDefines.                                                                                h: No such file or directory
compilation terminated.
DCFDelegate/src/CMakeFiles/DCFDelegate.dir/build.make:62: recipe for target                                                                                'DCFDelegate/src/CMakeFiles/DCFDelegate.dir/DCFDelegate.cpp.o' failed
make[2]: *** [DCFDelegate/src/CMakeFiles/DCFDelegate.dir/DCFDelegate.cpp.o]                                                                                Error 1
CMakeFiles/Makefile2:4204: recipe for target 'DCFDelegate/src/CMakeFiles/DC                                                                                FDelegate.dir/all' failed
make[1]: *** [DCFDelegate/src/CMakeFiles/DCFDelegate.dir/all] Error 2
Makefile:138: recipe for target 'all' failed
make: *** [all] Error 2

@dipankjain
Great!


getCurrentPosition takes too long on 7.6.2

🐛 Bug Report
Hi everyone!
I've been using geolocator for a while and I was about to upgrade the current version ^4.0.3 to ^7.6.2.
Turns out that the method getCurrentPosition takes about 10 seconds to locate the user, while the old version returns almost immediately. I tried to upgrade to ^5.3.1 in the past but got the same behavior.
Does anyone knows a newer version that doesn't takes too long to locate the user?
Expected behavior
Return user location faster. Just as it is in the older version.
Reproduction steps
Call getCurrentPosition to take user location.
Configuration
Version: ^7.6.2
Platform:

[x] :iphone: iOS
[x] :robot: Android

Hi @digocse,
The issue is that we had a bug which resulted in the getCurrentPosition method to return the last known location. The benefit was that it made it return very fast, but of course the disadvantage is that is often returned a wrong location.
We have resolved the issue but unfortunately that means you will have to wait for iOS to make the necessary connections. This can take up to several seconds (especially the first time you call getCurrentPosition). There is unfortunately no way around this.
I'd suggest you first call the getCurrentPosition method and while waiting for the satellite fix call the getLastKnownPosition method to get a fast location update.
More information can also be found in the release notes. I will be closing this issue now as this isn't a bug we can resolve. If you have any follow up questions or feedback feel free to leave a comment.

Hello @SergiDevel,
As mentioned in the previous comment, this is unfortunately how Apple has implemented the solution. It takes up to 10 seconds because Apple's requestLocation method will fetch multiple location updates from the device, compare them to each other and returns the most accurate result (this procedure is very well explained in this article).
If you don't want to wait and don't need a high accuracy result, you could start listening to the getPositionStream, grep the first result and stop listening directly after. You can do this very easily using the .first property:
// Fetch the first result from the position stream and cancel the stream directly after.
final Position position = await Geolocator.getPositionStream().first;

Of course you can do more advanced logic if necessary.

Hello @mvanbeusekom, thanks for the fast answer. I tested the proposed solution requesting the first element but I got a few hundred meters difference for each request.


Check if temporal entity dimension work with dashboard shared filter

Wondering if TemporalEntityDimension wouldn't also work "out of the box", as it looks like it has a timeUnit just like TemporalDimension?

Originally posted by @bprusinowski in https://github.com/visualize-admin/visualization-tool/pull/1545#discussion_r1624444483

@bprusinowski i tried to test on TEST and with the PR links
Time brush for temporal entity dimension based X axis -> works as expected on both the PR and on TEST
Temporal entity dimension in shared dashboard filters

On the PR when I switch to the dashboard layout the shared filter option is not shown:
On TEST i can activate the shared filter, however for the date i am only shown 01.1970, and cannot filter the chart with the time brush

Tested with https://test.visualize.admin.ch/en/v/uVzl9tEGzs_E?dataSource=Int

@sosiology should be fixed on TEST in ~20 mins :) Let me know if it still doesn't work as expected 👍


v1.12.2

v2 Blockchain endpoints

Pull Request Test Coverage Report for Build 687

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 61.485%

Totals

Change from base Build 674:
0.0%

Covered Lines:
1352

Relevant Lines:
2110

💛  - Coveralls

:tada: This PR is included in version 1.0.0 :tada:
Your semantic-release bot :package::rocket:


Added min mass loss, closes #403

This pull request is now managed with CodeReviewHub. Refresh.


[WIP] Support local xgboost regressor

the xgboost library PR #1041  needs to be merged first

@rootfs I updated the xgboost to the main pipeline and upload the trained model on my local repo. Please use it first for testing the WIP code here.
The json of xgboost is in NormalizedNumericalFeature.Weight
You may redefine NormalizedNumericalFeature.Weight to interface{} instead of float and handle it separately for each type.
Not sure but you may need to temporarily save the extracted Weight in json format can read it from the function C.LoadModelFromJSON.
apiVersion: v1
kind: ConfigMap
metadata:
  name: kepler-cfm
  namespace: kepler
data:
  MODEL_CONFIG: |
    NODE_TOTAL_INIT_URL =https://raw.githubusercontent.com/sunya-ch/kepler-model-db/trl-nx12/models/v0.7/nx12/std_v0.7/acpi/AbsPower/BPFOnly/XgboostFitTrainer_1.json
    NODE_COMPONENTS_INIT_URL=https://raw.githubusercontent.com/sunya-ch/kepler-model-db/trl-nx12/models/v0.7/nx12/std_v0.7/rapl/AbsPower/BPFOnly/XgboostFitTrainer_1.json

the git history messed up. Close this PR and reopen in another clean branch

replaced by #1052


Bxmsprod 533

https://issues.redhat.com/browse/BXMSPROD-533

Jenkins retest this please

I have only 1 comment to limiting the running off the master instance, otherwise it looks ok

Thank you for the question! @mareknovotny What do you thing about it?

yes, you could add it to the parent seed job too I think


Create helper script for appending asterisks to students names

Following up on https://github.com/neuropoly/bibeasy/issues/10 we decided that a quick script to add asterisks to students names was a more feasible way to meet an upcoming deadline, and that issue 10 would continue to be worked on over the next while.
@jcohenadad At this point I have what I believe to be a solution to adding asterisks safely, alongside a better understanding of the underlying schema. @SomeoneInParticular and @mguaypaq both assisted in this process and I am very grateful. I'm about to submit a draft PR which will contain:

the script to add asterisks to student names matching bibeasy.formatting.STUDENTS
some additional matches for the STUDENTS list (more names without accented characters)
possibly my de-naming script for testing if I can get it working for CCV

@jcohenadad should I include the updated xml you have provided or leave that out?
I'm currently struggling to test the generated xml, I'm removing as much information as I can from the source XML about who it is from, but the website continues to give me an error related to account mismatches.
Notes:

kousu 's previous observation of unique identifiers for every entry may be what's getting in the way

This might not actually be the problem, as I was previously able to import Nick's xml without regenerating identifiers
Julien's xml is just much larger
I'm currently working to extract only the relevant sections for testing

ccv-cvc.ca doesn't care if the xml is pretty-printed or not
it also doesn't care if \r\n is used, so \n is fine

The latter note is somewhat important for python's xml parser.

@jcohenadad should I include the updated xml you have provided or leave that out?

feel free to add it-- all that info is public anyway

I'm working through some tests today (I know it's a holiday but I really want to get this done). I'm struggling to properly de-identify Julien's CCV, so I'm exporting my own and testing with that.
I've added --append to the script to assist testing. I had previously obtained Nick's testing xml, there was less to remove there and I had gotten that imported a month or so ago.
The script appears to work!!
with python3  student_asterisk_helper.py -i ~/Downloads/CCV-10259659\(3\).xml -o /tmp/ccv-nathan.xml -a 'Cohen-Adad J'
The exported preview CV goes from
CCV-NathanGorvett-2.pdf
To
CCV-NathanGorvett-3.pdf
It appears to be completely valid, the asterisk is kept for Julien (who I've added as an append, to be clear).
Then I ran it over once more without appending Julien and the asterisk was properly removed (as it's not in the list):
python3  student_asterisk_helper.py -i ~/Downloads/CCV-10259659\(3\).xml -o /tmp/ccv-nathan.2.xml
CCV-NathanGorvett-4.pdf

@jcohenadad I merged the changes after adding some help documentation. Please try it out and feel free to re-open the ticket here if there's more I need to do.


App remoting.dll not found when using the XR SDK

When trying to build my UWP app created in Unity via Visual Studio for the HoloLens 2 the following error occurs:  Error MSB3030 Could not copy the file "...\Plugins\ARM64\Microsoft.Holographic.AppRemoting.dll" because it was not found.
In this build I am trying the new XR SDK from Unity. Since I just wanted to try it out, there is only one cube in the scene.
Your setup (please complete the following information)

Unity Version 2019.3.4f1
MRTK Version 2.3

Target platform (please complete the following information)

HoloLens 2

This happens with or without the new XR SDK. The error can be made to go away if you disable WSA Holographic Remoting Supported (assuming you don't need this) in the PLayer XR Settings . Remoting in the editor should still work.

There are no "WSA Holographic Remoting Supported" options enabled.
Settings under Player/XR Settings are depricated disabled and not editable. Also in the XR Plugin Management/ Windows Mixed Reality menu Holographic Remoting ist disabled. So i forgot any Settings?

Ah my bad, I am not currently on the new XR version, that was a wrong assumption on my behalf.

Same issue here:

Unity 2019.3.7f1
MRTK 2.4
Hololens 2

I believe this was fixed in Unity 2019.3.9 and later. Closing as External, but will monitor for follow-up questions.