pysam installation in python 3.11

(methylbert_311) pip3 install pysam
Collecting pysam
  Using cached pysam-0.22.1.tar.gz (4.6 MB)
  Installing build dependencies ... done
  Getting requirements to build wheel ... error
  error: subprocess-exited-with-error

  × Getting requirements to build wheel did not run successfully.
  │ exit code: 1
  ╰─> [170 lines of output]
      # pysam: cython is available - using cythonize if necessary
      # pysam: htslib mode is shared
      # pysam: HTSLIB_CONFIGURE_OPTIONS=None
      # pysam: (sysconfig) CC=gcc -pthread -B /omics/groups/OE0219/internal/Yunhee/anaconda3/envs/methylbert_311/compiler_compat
      # pysam: (sysconfig) CFLAGS=-DNDEBUG -fwrapv -O2 -Wall   -fPIC   -O2 -isystem /omics/groups/OE0219/internal/Yunhee/anaconda3/envs/methylbert_311/include -fPIC -O2   -isystem /omics/groups/OE0219/internal/Yunhee/anaconda3/envs/methylbert_311/include  -fPIC
      # pysam: (env) LDFLAGS=-Wl,-O2 -Wl,--sort-common -Wl,--as-needed -Wl,-z,relro -Wl,-z,now -Wl,--disable-new-dtags -Wl,--gc-sections -Wl,-rpath,/omics/groups/OE0219/internal/Yunhee/anaconda3/lib -Wl,-rpath-link,/omics/groups/OE0219/internal/Yunhee/anaconda3/lib -L/omics/groups/OE0219/internal/Yunhee/anaconda3/lib
      checking for gcc... gcc -pthread -B /omics/groups/OE0219/internal/Yunhee/anaconda3/envs/methylbert_311/compiler_compat
      checking whether the C compiler works... yes
      checking for C compiler default output file name... a.out
      checking for suffix of executables...
      checking whether we are cross compiling... no
      checking for suffix of object files... o
      checking whether we are using the GNU C compiler... yes
      checking whether gcc -pthread -B /omics/groups/OE0219/internal/Yunhee/anaconda3/envs/methylbert_311/compiler_compat accepts -g... yes
      checking for gcc -pthread -B /omics/groups/OE0219/internal/Yunhee/anaconda3/envs/methylbert_311/compiler_compat option to accept ISO C89... none needed
      checking for ranlib... ranlib
      checking for grep that handles long lines and -e... /usr/bin/grep
      checking for C compiler warning flags... unknown
      checking how to run the C preprocessor... gcc -pthread -B /omics/groups/OE0219/internal/Yunhee/anaconda3/envs/methylbert_311/compiler_compat -E
      checking for egrep... /usr/bin/grep -E
      checking for ANSI C header files... yes
      checking for sys/types.h... yes
      checking for sys/stat.h... yes
      checking for stdlib.h... yes
      checking for string.h... yes
      checking for memory.h... yes
      checking for strings.h... yes
      checking for inttypes.h... yes
      checking for stdint.h... yes
      checking for unistd.h... yes
      checking whether _XOPEN_SOURCE is declared... no
      checking C compiler flags needed for ssse3... -mssse3
      checking C compiler flags needed for popcnt... -mpopcnt
      checking C compiler flags needed for sse4.1... -msse4.1
      checking C compiler flags needed for avx2... -mavx2
      checking C compiler flags needed for avx512f... unsupported
      checking for pkg-config... /usr/bin/pkg-config
      checking pkg-config is at least version 0.9.0... yes
      checking for special C compiler options needed for large files... no
      checking for _FILE_OFFSET_BITS value needed for large files... no
      checking shared library type for unknown-Linux... plain .so
      checking whether the linker supports versioned symbols... no
      checking whether the compiler accepts -fvisibility=hidden... yes
      checking for stdlib.h... (cached) yes
      checking for unistd.h... (cached) yes
      checking for sys/param.h... yes
      checking for getpagesize... yes
      checking for working mmap... yes
      checking for gmtime_r... yes
      checking for fsync... yes
      checking for drand48... yes
      checking for srand48_deterministic... no
      checking whether fdatasync is declared... yes
      checking for fdatasync... yes
      checking for library containing log... -lm
      checking for zlib.h... yes
      checking for inflate in -lz... yes
      checking for library containing recv... none required
      checking for bzlib.h... yes
      checking for BZ2_bzBuffToBuffCompress in -lbz2... yes
      checking for lzma.h... yes
      checking for lzma_easy_buffer_encode in -llzma... no
      configure: error: liblzma development files not found

      The CRAM format may use LZMA2 compression, which is implemented in HTSlib
      by using compression routines from liblzma <http://tukaani.org/xz/>.

      Building HTSlib requires liblzma development files to be installed on the
      build machine; you may need to ensure a package such as liblzma-dev (on Debian
      or Ubuntu Linux), xz-devel (on RPM-based Linux distributions or Cygwin), or
      xz (via Homebrew on macOS) is installed; or build XZ Utils from source.

      Either configure with --disable-lzma (which will make some CRAM files
      produced elsewhere unreadable) or resolve this error to build HTSlib.
      checking for gcc... gcc -pthread -B /omics/groups/OE0219/internal/Yunhee/anaconda3/envs/methylbert_311/compiler_compat
      checking whether the C compiler works... yes
      checking for C compiler default output file name... a.out
      checking for suffix of executables...
      checking whether we are cross compiling... no
      checking for suffix of object files... o
      checking whether we are using the GNU C compiler... yes
      checking whether gcc -pthread -B /omics/groups/OE0219/internal/Yunhee/anaconda3/envs/methylbert_311/compiler_compat accepts -g... yes
      checking for gcc -pthread -B /omics/groups/OE0219/internal/Yunhee/anaconda3/envs/methylbert_311/compiler_compat option to accept ISO C89... none needed
      checking for ranlib... ranlib
      checking for grep that handles long lines and -e... /usr/bin/grep
      checking for C compiler warning flags... unknown
      checking how to run the C preprocessor... gcc -pthread -B /omics/groups/OE0219/internal/Yunhee/anaconda3/envs/methylbert_311/compiler_compat -E
      checking for egrep... /usr/bin/grep -E
      checking for ANSI C header files... yes
      checking for sys/types.h... yes
      checking for sys/stat.h... yes
      checking for stdlib.h... yes
      checking for string.h... yes
      checking for memory.h... yes
      checking for strings.h... yes
      checking for inttypes.h... yes
      checking for stdint.h... yes
      checking for unistd.h... yes
      checking whether _XOPEN_SOURCE is declared... no
      checking C compiler flags needed for ssse3... -mssse3
      checking C compiler flags needed for popcnt... -mpopcnt
      checking C compiler flags needed for sse4.1... -msse4.1
      checking C compiler flags needed for avx2... -mavx2
      checking C compiler flags needed for avx512f... unsupported
      checking for pkg-config... /usr/bin/pkg-config
      checking pkg-config is at least version 0.9.0... yes
      checking for special C compiler options needed for large files... no
      checking for _FILE_OFFSET_BITS value needed for large files... no
      checking shared library type for unknown-Linux... plain .so
      checking whether the linker supports versioned symbols... no
      checking whether the compiler accepts -fvisibility=hidden... yes
      checking for stdlib.h... (cached) yes
      checking for unistd.h... (cached) yes
      checking for sys/param.h... yes
      checking for getpagesize... yes
      checking for working mmap... yes
      checking for gmtime_r... yes
      checking for fsync... yes
      checking for drand48... yes
      checking for srand48_deterministic... no
      checking whether fdatasync is declared... yes
      checking for fdatasync... yes
      checking for library containing log... -lm
      checking for zlib.h... yes
      checking for inflate in -lz... yes
      checking for library containing recv... none required
      checking for bzlib.h... yes
      checking for BZ2_bzBuffToBuffCompress in -lbz2... yes
      checking for lzma.h... yes
      checking for lzma_easy_buffer_encode in -llzma... no
      configure: error: liblzma development files not found

      The CRAM format may use LZMA2 compression, which is implemented in HTSlib
      by using compression routines from liblzma <http://tukaani.org/xz/>.

      Building HTSlib requires liblzma development files to be installed on the
      build machine; you may need to ensure a package such as liblzma-dev (on Debian
      or Ubuntu Linux), xz-devel (on RPM-based Linux distributions or Cygwin), or
      xz (via Homebrew on macOS) is installed; or build XZ Utils from source.

      Either configure with --disable-lzma (which will make some CRAM files
      produced elsewhere unreadable) or resolve this error to build HTSlib.
      config.mk:2: *** Resolve configure error first.  Stop.
      # pysam: htslib configure options: None
      Traceback (most recent call last):
        File "/omics/groups/OE0219/internal/Yunhee/anaconda3/envs/methylbert_311/lib/python3.11/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 353, in <module>
          main()
        File "/omics/groups/OE0219/internal/Yunhee/anaconda3/envs/methylbert_311/lib/python3.11/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 335, in main
          json_out['return_val'] = hook(**hook_input['kwargs'])
                                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
        File "/omics/groups/OE0219/internal/Yunhee/anaconda3/envs/methylbert_311/lib/python3.11/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 118, in get_requires_for_build_wheel
          return hook(config_settings)
                 ^^^^^^^^^^^^^^^^^^^^^
        File "/tmp/pip-build-env-ftjtbw8x/overlay/lib/python3.11/site-packages/setuptools/build_meta.py", line 333, in get_requires_for_build_wheel
          return self._get_build_requires(config_settings, requirements=[])
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
        File "/tmp/pip-build-env-ftjtbw8x/overlay/lib/python3.11/site-packages/setuptools/build_meta.py", line 303, in _get_build_requires
          self.run_setup()
        File "/tmp/pip-build-env-ftjtbw8x/overlay/lib/python3.11/site-packages/setuptools/build_meta.py", line 521, in run_setup
          super().run_setup(setup_script=setup_script)
        File "/tmp/pip-build-env-ftjtbw8x/overlay/lib/python3.11/site-packages/setuptools/build_meta.py", line 319, in run_setup
          exec(code, locals())
        File "<string>", line 437, in <module>
        File "<string>", line 81, in run_make_print_config
        File "/omics/groups/OE0219/internal/Yunhee/anaconda3/envs/methylbert_311/lib/python3.11/subprocess.py", line 466, in check_output
          return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
        File "/omics/groups/OE0219/internal/Yunhee/anaconda3/envs/methylbert_311/lib/python3.11/subprocess.py", line 571, in run
          raise CalledProcessError(retcode, process.args,
      subprocess.CalledProcessError: Command '['make', '-s', 'print-config']' returned non-zero exit status 2.
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
error: subprocess-exited-with-error

× Getting requirements to build wheel did not run successfully.
│ exit code: 1
╰─> See above for output.

note: This error originates from a subprocess, and is likely not a problem with pip.

With the python 3.11 environment, lzma makes a problem while pysam is being installed.

It was the limited conda service term (non-commercial use).
Removed default channels following this:
conda config --show channels
conda config --remove channels defaults
conda config --add channels conda-forge

And then created a new conda environment with python 3.11.


make plugin not dependent on version,

With every new minor version of kibana and dedicated version number of the datasweet plug-in is needed. There are no available version for the latest version of Kibana. Would it be possible to remove the version checking mechanisms?

Hi.
Actually, we only support kibana v5.6.x to v6.4.x.
They are a lot of breaking changes in v6.5.x, and for now, we don't have the time to do the upgrade.

@tcharlot-datasweet is there a timeline of when you guys will have time to upgrade the plugin above 6.4.x?

Hi,
please give it a try to the last release (support for kibana v6.5.x to 6.7.x).
Regards


Add/use OnXYZ event methods instead of raising events directly

Summary of feature
Add protected virtual OnXYZ methods for window events. This way users can override those methods in custom derived window classes and control the event emission by call the base.OnXYZ method or not.
The GlfwWindow implementation will basically call the OnXYZ methods instead of invoking the events directly. The default implementations of the OnXYZ methods will just raise the associated event.
Example of implementation
    // part of GlfwWindow.cs
    ...
    var delta = _renderStopwatch.Elapsed.TotalSeconds;

    OnRender(delta); // changed from Render?.Invoke(delta);

    if (ShouldSwapAutomatically)
    {
        SwapBuffers();
    }
    ...

    // somewhere else in GlfwWindow.cs
    protected virtual void OnRender(double delta)
    {
        Render?.Invoke(delta);
    }

Use case
A custom user window may handle the render logic internally (by overriding the OnRender method) but it may want to prevent populating the Render event to the outside or only do so based on some internal conditions.
This is also handy if it should be ensured that the additional logic is executed before the event is consumed by someone else. The developer of the custom window can call base.OnXYZ after his additional code.
    // part of MyCustomWindowClass
    protected override void OnRender(double delta)
    {
        // do some render related stuff that should be done
        // before anyone is notified about the event ...
        base.OnRender(delta); // raise the event through base method
    }

Implementation
I could implement this very quickly with a PR if you want me to.

In the first ever builds of Silk.NET this is actually how we did things, but we deduced it doesn’t fit well with our dependency injection model. Don’t get me wrong, we could do it, but it’s an unnecessary complication and the events already work fine.
If needed, we can add logic to the existing events so you can cancel further emissions but for virtual methods, we’ve been down this road before and it just doesn’t work well with the API we’ve already forged.

As long as the use cases can be handled in a suitable way I'm ok with different approaches. Conditional event emission and ensurance of custom code execution before event emission are some use cases that may be desirable.
Maybe the time will show if this behavior is a broadly needed feature or not. Until then you may close this issue here. For my current project I get around it with ease.

Yeah, generally we expect the user to wrap the events anyway as there are few cases where a whole engine will need direct access to the window events.


Don't serialize args in account.ts

Looks like there are test failures to look at

Looks like there are test failures to address

looks like these were just lint failures, fixed now


fix imports for M4i driver

As discussed on slack. @WilliamHPNielsen

@WilliamHPNielsen The tests import the driver which triggers importing a library which is not included in the qcodes driver. Can you have a look at this?

Lemme see if I can make any sense of the importing...

@peendebak The docs build needs to import every driver to build the api docs for it. Due to your changes it no longer throws an ImportError when failing to import pyscm but rather a OSError when not finding the shared object. I think all you need to do is catch the OSError along with the import error.
The code in h2py.py is not python 3 compatible I am not sure why we carry this around as it does not seem to be used.

@jenshnielsen I removed the h2py.py. The OSError is now handled similar to the ImportError.


Check logger for DEBUG before calling log_pprint

+1 factory boy logging, mostly in _safe_repr, was taking a significant amount of my test suite - around ~5-10%, though hard to tell as things slow down when running with the profiler.

Had an idea - rather than wrapping with this request, log_pprint could be made to return a lazy object whose str is the result of the formatting with safe_repr. This would require fewer, cleaner changes now, plus would work for future logging statements that get added..

Also, for anyone else that notices this performance penalty, this is how I'm currently obviating it with patchy:
def patch_factory_boy_util_log_pprint():
    """
    This function is used to generate log output for factory boy, unfortunately it takes a lot of CPU time on
    many-factory tests
    """
    from factory.utils import log_pprint
    patchy.patch(log_pprint, """\
        @@ -1,9 +1,2 @@
         def log_pprint(args=(), kwargs=None):
        +    return
        -    kwargs = kwargs or {}
        -    return ', '.join(
        -        [_safe_repr(arg) for arg in args] +
        -        [
        -            '%s=%s' % (key, _safe_repr(value))
        -            for key, value in kwargs.items()
        -        ]
        -    )
        """)

I like the lazy log_pprint idea better indeed :) :+1:

Thanks for the suggestion! I've just implemented the "lazy pprint" approach.

+1 thanks, was just looking at implementing it myself


[WIP] M3-40 Selection Card

Adds "Selection Card" component that supports:

Icons
Images
Font Glyphs
Checked and Unchecked state

@asauber @rjstires ready for review. This has a little more CSS due to the nature of the component and the fact that the default grid item props would break the layout if left as is.
I also changed the markup for each selection card to be a grid item in order to avoid nesting the markup one more level. So obviously the container needs to be a <Grid container
Lastly i need to add a conditional 'selected' className to the root container as it is otherwise unaware of a possible checked child

@asauber good catch, fixed!


Ensure that danger.import_dangerfile evals inside the right context

Fixes - #487
Ensures that external dangerfiles are ran and can use the plugins of the outer Dangerfile.

I agree with @hanneskaeufler that test was not doing anything, happy to merge on 🍏


[Suggestion] Can you please put the compiled idlparser.jar to maven repository? Thanks. [13743]

Thanks for the suggestion, @liberty724048
I am labeling the ticket as an enhancement. I am afraid that, for the moment, IDL Parser is not going to be released into Maven repository. I am moving the ticket to the Ideas discussion forum where enhancements and feature requests are discussed.


Examples for Loading Test From Remote Server

First of all, this a great project!
I just need more examples/guides on how to further develop this project. Especially for loading test cases from a remote server.
Also, as you determined in your roadmap if you can implement more Selenium Webdriver API functionality that will be awesome!
Looking forward to hearing from you!
Thank you!

Hi @omertarik96 !
Unfortunately autotester is frozen(
For me It seems puppeteer API wins over Selenium API as more fresh and intuitive.

Do you know any implementations of puppeteer API for chrome extensions like autotester?

Have a look on remote-browser.


Canceling "unsaved changes" warning closes window anyway

I've encountered a very severe bug (Atom 0.198.0) where if you attempt to close a window with tabs with unsaved changes, and you hit cancel in the warning dialog that appears, it closes the window anyway (presumably without saving).

Thanks for the report! What OS are you running? Can you reproduce this in safe mode (atom --safe)?

This is a duplicate of #4092, please subscribe there for updates (and also comment there with your OS and atom --safe results).


[Question] how to create enum variables and Is it possible to make my own typed event?

I've seen you implemented this. But, I don't know how to create it. There's no enum variable option to create in asset menu.
Also, Is it possible to create my own typed event? Specifically, I want to pass custom class or struct as a parameter but unity event does not support serializing these custom classes.


PS-AWS-Pod-Updates

Changes:

Pod updates

We'll merge this once Ravi is finished with all network tests and regression.


[setup/osflow/boards/index.mk] do not set GHDL_PLUGIN_MODULE unconditionally

Close #148.

:heart:


Remove version: SMPlayer.SMPlayer version 21.8.0

[Automated] It returns code over 400 in all urls
Microsoft Reviewers: Open in CodeFlow

URL: https://sourceforge.net/projects/smplayer/files/SMPlayer/21.8.0/smplayer-21.8.0-x64.exe/download
OK
(Automated message - build 923)

Close with reason: Package still available.;


AA0242: Triggering warning twice for same field throws System.ArgumentException: An item with the same key has already been added

1. Describe the bug
If the AA0242 diagnostic is tripped twice for the same field, it can't handled it and blows up.
2. To Reproduce
pageextension 50100 CustomerListExt extends "Customer List"
{
    trigger OnOpenPage();
    var
        Customer: Record Customer;
        Name: Text;
    begin
        Customer.SetLoadFields("No.");
        Customer.FindFirst();
        Name := Customer.Name;
        Name := Customer.Name;
    end;
}

3. Expected behavior
Two warnings.
4. Actual behavior

Analyzer 'Microsoft.Dynamics.Nav.CodeCop.Design.Rule0242PartialRecordsDetectJitLoads' threw an exception of type 'System.ArgumentException' with message 'System.ArgumentException: An item with the same key has already been added. Key: Name
   at System.Collections.Generic.Dictionary`2.TryInsert(TKey key, TValue value, InsertionBehavior behavior)
   at System.Collections.Generic.Dictionary`2.Add(TKey key, TValue value)
   at Microsoft.Dynamics.Nav.CodeCop.Design.Rule0242PartialRecordsDetectJitLoads.JitLoadDetectionVisitor.VisitFieldAccess(IFieldAccess operation) in D:\a\1\s\source\Prod\Microsoft.Dynamics.Nav.CodeCop\Design\Rule0242PartialRecordsDetectJitLoads.cs:line 201
   at Microsoft.Dynamics.Nav.CodeAnalysis.OperationWalker.Visit(IOperation operation) in D:\a\1\s\source\Prod\Microsoft.Dynamics.Nav.CodeAnalysis\Compilation\OperationWalker.cs:line 36
   at Microsoft.Dynamics.Nav.CodeAnalysis.OperationWalker.Visit(IOperation operation) in D:\a\1\s\source\Prod\Microsoft.Dynamics.Nav.CodeAnalysis\Compilation\OperationWalker.cs:line 36
   at Microsoft.Dynamics.Nav.CodeAnalysis.OperationWalker.VisitAssignmentStatement(IAssignmentStatement operation) in D:\a\1\s\source\Prod\Microsoft.Dynamics.Nav.CodeAnalysis\Compilation\OperationWalker.cs:line 67
   at Microsoft.Dynamics.Nav.CodeAnalysis.BoundAssignmentStatement.Accept(OperationVisitor visitor) in D:\a\1\s\source\Prod\Microsoft.Dynamics.Nav.CodeAnalysis\BoundTree\Statements.cs:line 113
   at Microsoft.Dynamics.Nav.CodeAnalysis.OperationWalker.Visit(IOperation operation) in D:\a\1\s\source\Prod\Microsoft.Dynamics.Nav.CodeAnalysis\Compilation\OperationWalker.cs:line 36
   at Microsoft.Dynamics.Nav.CodeAnalysis.OperationWalker.VisitArray[T](ImmutableArray`1 list) in D:\a\1\s\source\Prod\Microsoft.Dynamics.Nav.CodeAnalysis\Compilation\OperationWalker.cs:line 42
   at Microsoft.Dynamics.Nav.CodeAnalysis.OperationWalker.VisitBlockStatement(IBlockStatement operation) in D:\a\1\s\source\Prod\Microsoft.Dynamics.Nav.CodeAnalysis\Compilation\OperationWalker.cs:line 49
   at Microsoft.Dynamics.Nav.CodeAnalysis.BoundBlock.Accept(OperationVisitor visitor) in D:\a\1\s\source\Prod\Microsoft.Dynamics.Nav.CodeAnalysis\BoundTree\Statements.cs:line 84
   at Microsoft.Dynamics.Nav.CodeAnalysis.OperationWalker.Visit(IOperation operation) in D:\a\1\s\source\Prod\Microsoft.Dynamics.Nav.CodeAnalysis\Compilation\OperationWalker.cs:line 36
   at Microsoft.Dynamics.Nav.CodeCop.Design.Rule0242PartialRecordsDetectJitLoads.AnalyzeMethod(OperationAnalysisContext context) in D:\a\1\s\source\Prod\Microsoft.Dynamics.Nav.CodeCop\Design\Rule0242PartialRecordsDetectJitLoads.cs:line 125
   at Microsoft.Dynamics.Nav.CodeAnalysis.Diagnostics.AnalyzerExecutor.<>c__DisplayClass53_1.<ExecuteOperationAction>b__1() in D:\a\1\s\source\Prod\Microsoft.Dynamics.Nav.CodeAnalysis\DiagnosticAnalyzer\AnalyzerExecutor.cs:line 764
   at Microsoft.Dynamics.Nav.CodeAnalysis.Diagnostics.AnalyzerExecutor.ExecuteAndCatchIfThrows_NoLock(DiagnosticAnalyzer analyzer, Action analyze, Nullable`1 info) in D:\a\1\s\source\Prod\Microsoft.Dynamics.Nav.CodeAnalysis\DiagnosticAnalyzer\AnalyzerExecutor.cs:line 1100'

5. Versions:

AL Language: 7.1.441584
Visual Studio Code: 1.50
Business Central: 17
List of Visual Studio Code extensions that you have installed:

@qutreson please assign to me.

@atoader this has been fixed, we can close this issue.

The fix for this issue has been checked in to the master branch. It will be available in the bcinsider.azurecr.io/bcsandbox-master Docker image starting from platform build number 24292 and VS Code Extension Version 8.0.446271.
If you don’t have access to these images you need to become part of the Ready2Go program: aka.ms/readytogo
For more details on code branches and docker images please read:
https://blogs.msdn.microsoft.com/nav/2018/05/03/al-developer-previews-multiple-releases-and-github/
https://freddysblog.com/2020/06/25/working-with-artifacts/


startAudioRecordingWithConfig throwing a  PlatformException error  "PlatformException(2, invalid argument, null, null)"

Describe the bug
When I tried to use the  startAudioRecordingWithConfig method on android to record the audio, I got a  PlatformException error
" PlatformException(2, invalid argument, null, null) "

So, while trying to figure out what was going on, I found out  that
startAudioRecordingWithConfig and  startAudioRecording  invoked the same channel methods but the arguments are different ;

How do we resolve this.
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

call the engine .startAudioRecordingWithConfig method and pass the config "AudioRecordingConfiguration"

Expected behavior
No error should be thrown.
Additional context
Although the startAudioRecording still works fine, it has the deprecated flag.

Could you pls share your code about calling startAudioRecordingWithConfig?


Element range attribute excludes the Binary type

Currently the range attribute is allowed only for numerical element types,
but Matroska has two Binary elements with a definde range.
https://github.com/ietf-wg-cellar/matroska-specification/issues/730

Indeed, either we don't use the range field or we change the rules here. The text is pretty clear that it's only for "number" values: https://www.rfc-editor.org/rfc/rfc8794.html#expression-of-range
I think the idea of the range field, rather than just being rules written in the text, is that they are machine readable and parseable, to generate code accordingly. It becomes tricky to describe with that field for complex binary blobs, which EBML or Matroska are not supposed to interpret on their own.
So in the spirit of the separation of parsing levels, I would not put binary ranges inside the range field but in the text or in the usage notes.

I would not put binary ranges inside the range field but in the text or in the usage notes.

OK. Sounds logical and I think usage notes could be enough for teh moment.
Would a new range-attribute makes sense, -> range_binary ?


strict-boolean-expressions silently requires strictNullChecks TS option

Bug Report

TSLint version: 4.4.2

Description
Some options (allow-null-union, allow-undefined-union, allow-mix) of strict-boolean-expressions  assume strictNullChecks TypeScript compiler option, but it is not documented.
The related part of code is here . Only string, number, Boolean, and enum are handled as NOT always true or false. For example, object type is treated as always truthy, but it's not true without strictNullChecks . This code path is used even without the mentioned arguments, but somehow the default test passes, too.
The tests specify strictNullChecks option (Ex. https://github.com/palantir/tslint/tree/master/test/rules/strict-boolean-expressions/allow-null-union )
Actual behavior
strictNullChecks  option is assumed for these arguments allow-null-union, allow-undefined-union, allow-mix, but not documented.
Expected behavior
Should be documented. Or, nice if we can lift the assumption.

cc: @andy-hanson

it looks like you can check compiler options in program.getCompilationSettings().strictNullChecks

How should a rule report a configuration error like that?

For the sake of #2200, we need to lift the requirement of strictNullChecks, instead of just throwing error. Please check the discussion in #2200.


sonar suggests upgrading to a new version after installing that version

@alrra Did it still happend when you run it the second time? It always needs the first time to brush up the persisted result. See https://www.npmjs.com/package/update-notifier#how.

Did it still happend when you run it the second time?

No.

Closing, as I didn't see this happening anymore.

I got this again. :(

The data gets updated every hour or so. Will be great to find a way to force it somehow.


Make complex tests’ purposes clearer in compiled SQL and dbt docs

Describe the feature

When a custom schema test fails, the first thing I do is to download the compiled sql and run it myself to see what’s gone wrong.
backsolving from the file’s name and contents of the query is more complex than it needs to be -what exactly does dbt_utils_expression_is_true_paypal__subscribers_is_trial_or_sub_active_is_true__is_trial_expired_is_false_and_is_subscription_expired_is_false mean?
I currently include a comment in the yaml file explaining in English what the test does, but that’s not where I’m looking when a test fails.

        # active accounts can't have expired
        - dbt_utils.expression_is_true:
            expression: 'is_trial_expired is false and is_subscription_expired is false'
            condition: 'is_trial_or_sub_active is true'

        # inactive accounts must have expired
        - dbt_utils.expression_is_true:
            expression: 'is_trial_expired or is_subscription_expired'
            condition: 'is_trial_or_sub_active is false'

        # inactive accounts may only have been a trial or a subscription
        - dbt_utils.expression_is_true:
            expression: 'not (is_trial_expired and is_subscription_expired)'

Instead of it being a yaml comment, I can add a description argument to the test macro and include that as a comment in the compiled SQL

I then got to thinking about how custom tests display in dbt docs, and thought it would be nice to also display that nice comment instead of the stringified kwargs.
Describe alternatives you've considered

stopping at “include the description in the sql query”, which wouldn’t require any changes to dbt itself, but would mean needing to maintain our own fork of the dbt-utils tests
waiting for #1173 which looks like it might be a relative to this, albeit much broader scope

Who will this benefit?

If appropriate, a description property could be exposed to the built-in dbt tests as well as the dbt-utils ones, in which case it would help everyone who wants to debug their failing tests. Admittedly, not_null doesn’t need a lot of explanation, but perhaps it’s useful to say why it shouldn’t be null.
People consuming dbt docs (in fact, this might better live under the dbt-docs repo, but I’m not sure about the interplay before it gets to doc-rendering time - I assume that a description property would need to be explicitly added to the manifest, but not sure if that’s true given that I could already add arbitrary params to this macro...)

Are you interested in contributing this feature?
The docs test suite and I are close personal friends at this point, let’s do it.

@joellabes I 1000% agree with everything you've laid out above. Our current plan is for v0.20.0 to be "the testing release," including a lot of what's covered in #1173 and #2593.
In particular, I really, really want:

a saner unique_id for schema tests, instead of the kwarg portmanteau you pasted above
the ability to configure a description within schema test macros/blocks and data tests, to populate in manifest.json and dbt-docs
the ability to write a human-friendly, plain-language failure message describing what was expected and what's gone wrong, to populate in CLI output and in run_results.json
a much faster time-to-debug, between seeing that a test has failed and finding the failing records, by (optionally) storing those records in the database

All of those are things you touch on above, more or less, and with a cogency that I appreciate. I'm going to leave this issue open and add it to our v0.20.0 milestone. Even if we don't open PRs to address it head-on, it's right in the spirit of where I hope to go.

Awesome, thanks! Looking forward to seeing what comes of it all 👀

@jtcohen6 I missed the stale warning on this one. Here's where I think we stand from your four bullets earlier in the year:
✅  a saner unique_id for schema tests, instead of the kwarg portmanteau you pasted above Completed in https://github.com/dbt-labs/dbt-core/pull/3616
✅  a much faster time-to-debug, between seeing that a test has failed and finding the failing records, by (optionally) storing those records in the database Completed in https://github.com/dbt-labs/dbt-core/pull/3316
⌛ the ability to configure a description within schema test macros/blocks and data tests, to populate in manifest.json and dbt-docs Waiting on https://github.com/dbt-labs/dbt-core/issues/3249
⌛ the ability to write a human-friendly, plain-language failure message describing what was expected and what's gone wrong, to populate in CLI output and in run_results.json Also waiting on https://github.com/dbt-labs/dbt-core/issues/3249
As long as 3249 is going to pick up the torch for these improvements I'm happy for this one to fade into the night - I just want it to stay open somewhere 🥺

👋 I recently had a fever dream 🥵 where dbt tests were failing, but failing in human readable ways ❗ It revived my interest in the idea of making test failures easier to parse/solve, especially at scale.
Then when I was feeling better and back at work, I found on Slack that our new Lead Engineer had run into a test failure while I was away and couldn't quite trace back up the stack and figure out why it was happening. It was a test that affected our model snapshots, so it was effectively blocking one of our snapshot jobs until it could be solved.
I had all the context in my head -- so, if I were around that day, I could have assisted. I wasn't around, and dbt doesn't give us anywhere to stash this context that might be useful for others. For example, tests themselves don't have descriptions, and when tests fail there is (I'm sorry to have to say) nothing inherently very human-friendly about the logging/output of those failures.
This is to say, when something fails, we get the what and the where but much less (I would say) of the why and the how. We get roughly half of the puzzle, but even if the other half of the puzzle is known, we have nowhere to make it available.
I think, returning to Jeremy's comment above, something like this is incredibly important for efficient stack maintenance:
the ability to write a human-friendly, plain-language failure message describing what was expected and what's gone wrong, to populate in CLI output and in run_results.json
When I leave my current employer, that will be everyone who had anything to do with implementing the stack gone, and all that context will therefore be gone forever. There will still be people expected to maintain the stack, but they won't have the context that the stack founders had and they will therefore be dealing with known unknowns rather than known knowns until they get up to speed. But then the cycle will repeat when they leave, and on it could go, ad nauseam.
IMO there should definitely be somewhere (a test config called explanation/context?? 🤔) that I can stash what I have in my brain about why and how tests fail that will ultimately make them easier to resolve. To illustrate the point a little bit:

I can't speak to how easy this would be to implement, but I can speak to how much of a product improvement it would be.


Support all base types for hashListArray

This is continuation to our efforts to Support all base types for repeated fields.

For int64 we use big endian binary encoding to pass to xxhash digest
For float64 we use math.Float64bits to obtain uint64 representation that we get big endian binary encoding to pass to the xxhash digest
For bool we use byte(2) for true and byte(1) for false(This was taken from existing hashBooleanArray function) to pass to xxhash digest

I fixed regression (sort of)
goos: darwin
goarch: amd64
pkg: github.com/polarsignals/frostdb/dynparquet
cpu: Intel(R) Core(TM) i7-7820HQ CPU @ 2.90GHz
                │   old.txt   │              new.txt               │
                │   sec/op    │   sec/op     vs base               │
HashListArray-8   286.6n ± 2%   293.0n ± 0%  +2.27% (p=0.014 n=10)

                │  old.txt   │            new.txt             │
                │    B/op    │    B/op     vs base            │
HashListArray-8   48.00 ± 0%   48.00 ± 0%  ~ (p=1.000 n=10) ¹
¹ all samples are equal

                │  old.txt   │            new.txt             │
                │ allocs/op  │ allocs/op   vs base            │
HashListArray-8   1.000 ± 0%   1.000 ± 0%  ~ (p=1.000 n=10) ¹
¹ all samples are equal

@thorfour any ideas why we see  +2.27% ?. Everything is pretty much identical thats why the other two stats have equal samples.

I fixed regression (sort of)
goos: darwin
goarch: amd64
pkg: github.com/polarsignals/frostdb/dynparquet
cpu: Intel(R) Core(TM) i7-7820HQ CPU @ 2.90GHz
                │   old.txt   │              new.txt               │
                │   sec/op    │   sec/op     vs base               │
HashListArray-8   286.6n ± 2%   293.0n ± 0%  +2.27% (p=0.014 n=10)

                │  old.txt   │            new.txt             │
                │    B/op    │    B/op     vs base            │
HashListArray-8   48.00 ± 0%   48.00 ± 0%  ~ (p=1.000 n=10) ¹
¹ all samples are equal

                │  old.txt   │            new.txt             │
                │ allocs/op  │ allocs/op   vs base            │
HashListArray-8   1.000 ± 0%   1.000 ± 0%  ~ (p=1.000 n=10) ¹
¹ all samples are equal

@thorfour any ideas why we see  +2.27% ?. Everything is pretty much identical thats why the other two stats have equal samples.

I am unsure, but I can take a look this week.

Apologies I ended up getting sick this week and didn't get to it. I'll prioritize next week

Apologies I ended up getting sick this week and didn't get to it. I'll prioritize next week

Sorry to hear that, this is nothing urgent. Get well soon.


Rush's node_modules structure is not resolved in vscode correctly

VSCode Version: 1.28.2 (or insiders)
OS Version: Arch linux

When trying to auto-import node modules within a rush project, intellisense will not locate dependencies. This also results in the editor crashing or re-initializing the TS server somewhat often.
This is likely due to rush's unique node module structure, and it's unclear if this ever worked as I have only adopted rush somewhat recently.
Steps to Reproduce:
You can replicate this issue within the web-build-tools repo itself.

Open https://github.com/Microsoft/web-build-tools/blob/master/libraries/ts-command-line/src/index.ts
type Colors in the top level (from the colors module). You shouldn't be able to resolve the symbol.

eg.
const foo: Colors = {};

export {
  CommandLineAction,
  ICommandLineActionOptions
} from './CommandLineAction';

This also seems to correlate with the editor's TS server crashing intermittently, but its not clear how to reproduce.
Does this issue occur when all extensions are disabled?: Yes
Versions tested:

rush v5.5.2 / v5.3.0
node 6 / node 10
vscode v1.28.2 / insiders
with either of: npm, yarn or pnpm (all latest)
has been tested on multiple linux systems

Workaround
If you execute the below script to replace symlinks with real files:
mv node_modules node_modules_old
rsync node_modules_old/ node_modules/ -a --copy-links -v

Everything should work as expected.
There seems to be an issue with symlinks.
Related: https://github.com/Microsoft/web-build-tools/issues/955

Do I need to do anything special apart from cloning repo, opening file and typing the statement mentioned? I followed those steps (with typescript nightly build) but that seem to work as intended. Do not see any process shutdown or crash. Let me know if I need to do something else. If possible please  share full tsserver log so we can see where things might be going south. Thanks.
You can enable log level verbose in settigns and open and log and share tsserver and ti log or upload them using

With "typescript.tsserver.log": "verbose" enabled
Restart vscode or vscode insiders
Reproduce the problem
Run code --upload-logs on the command line (or code-insiders --upload-logs if using vscode insiders) and follow instructions
Share the log file ID

@sheetalkamat
To replicate, by following those steps you should have not have gotten the auto-import suggestion and no auto-fix bubble. Is this the case for you?
The TS Server crashing is intermittent and harder to replicate.
I'll be sure to use that command when it happens again, as verbose is enabled.

To replicate, by following those steps you should have not have gotten the auto-import suggestion and no auto-fix bubble. Is this the case for you?
Yes that's exactly what I saw. (Used typescript@next)

@sheetalkamat
Uploaded the logs when I noticed that the TS Server was hanging while trying to initialize:
Upload successful! Log file ID: 134282124

@nfour Looking at the log it seems like there are lot of DirectoryWatchers being invoked. Many of them are through failed lookup locations of the sources in project. Is it possible to share the repro project? We can sign nda if needed. (send it to me in email) I would also like to discuss with you about the different directoryWatcher locations that I see and reason about them but I am not sure if your code is private so let me know if we can continue the discussion here on email thread. If email, please contact me at shkamat at microsoft dot com. Thanks.

@sheetalkamat
We're looking into whether we can provide the source code.
As an alternative, do you think the web-build-tools monorepo is capable of reproducing these issues?

@nfour it would be hard to figure out what might be going wrong just from logs. In past we have used source code and figured out if there is something user can do or something we can do to enhance the experience. But that comes from looking at the source code, what kind of things module resolution is looking at etc. So just source structure is not enough (since from the log it seemed module resolution played role in the directory watchers being set). Please let me know once you are ready with the repro code. Thanks.

@sheetalkamat I think we'll be able to get you access to the source, will email!

@sheetalkamat sent you an email requesting info to provide the NDA.

@nfour Thanks for email. I am working on getting you the information.

I want to give an update:

<EMAIL_ADDRESS>no longer spins noticeable CPU cycles with rush 5.5 and pnpm
Auto-import of arbitrary dependencies still does not work - however - those that are rush linked do indeed show up in import suggestions

Assigning this bug till we have concrete repro steps to be able to look into this.

I'm having the same issue, you can check my project and check it out, it's under enjin/src/log.ts the chalk dependency is present and the project works when running but still vscode shows as missing module, it was working fine before converting splitting the project into multiple projects with rush.js

@norman784 The repro you said is your configuration error. With the tsconfig in your project, the module resolution kind is classic and not node (because your target is esnext) Changing the resolution, fixes the errors. You should be able to see details on resolution step with --traceResolution

thanks! feels a bit confusig all the different configurations about how to load modules.

Any update ?

I'm sorry, but we have a concrete repo to replicate the issue with, have we not ?
The issue is reproductible on Microsoft own web tools :
https://github.com/Microsoft/web-build-tools
We are trying to switch to Rush + VsCode (both MS products) and we encountered this issue, which is pretty much a showstopper.
Anyway, here is a really small repo to reproduce the issue : https://github.com/RDeluxe/rush-repro-955
Simply go to libraries/dtos/src/dtos/user.ts
You will have a compiler error. Normally vscode should be able to auto import the missing decorators from class-validator
import { IsEmail, IsString, } from 'class-validator'
Or to autocomplete and autoimport while typing IsE.

Hello, any news ? Could you reproduce on your end ? Thanks !

I'm sorry to bump this again, is there anything I could do ?
I'm not 100% confident jumping in Typescript's codebase, but if somebody could point me in the right direction I may be able to help.

Anyone have any workarounds here? I'm still unable to get autocomplete working with a project using Rush.

Hi @sheetalkamat
Any news about this issue ?
A small repro is here: https://github.com/RDeluxe/rush-repro-955
Any project with rush + ts look like having the issue

The repro provided has nothing to do with rush..
Your tsconfig.json only includes two files and hence there is not auto import suggestion. Duplicate of #28773 where in completion dont have knowledge of symbols that are not part of program
Info 86   [12:31:0.605] Project 'c:/temp/rush-repro-955/libraries/dtos/tsconfig.json' (Configured)
Info 87   [12:31:0.605] 	Files (40)
	c:/Typescript/built/local/lib.es5.d.ts
	c:/Typescript/built/local/lib.es2015.d.ts
	c:/Typescript/built/local/lib.es2016.d.ts
	c:/Typescript/built/local/lib.es2017.d.ts
	c:/Typescript/built/local/lib.es2018.d.ts
	c:/Typescript/built/local/lib.es2019.d.ts
	c:/Typescript/built/local/lib.es2020.d.ts
	c:/Typescript/built/local/lib.esnext.d.ts
	c:/Typescript/built/local/lib.es2015.core.d.ts
	c:/Typescript/built/local/lib.es2015.collection.d.ts
	c:/Typescript/built/local/lib.es2015.generator.d.ts
	c:/Typescript/built/local/lib.es2015.iterable.d.ts
	c:/Typescript/built/local/lib.es2015.promise.d.ts
	c:/Typescript/built/local/lib.es2015.proxy.d.ts
	c:/Typescript/built/local/lib.es2015.reflect.d.ts
	c:/Typescript/built/local/lib.es2015.symbol.d.ts
	c:/Typescript/built/local/lib.es2015.symbol.wellknown.d.ts
	c:/Typescript/built/local/lib.es2016.array.include.d.ts
	c:/Typescript/built/local/lib.es2017.object.d.ts
	c:/Typescript/built/local/lib.es2017.sharedmemory.d.ts
	c:/Typescript/built/local/lib.es2017.string.d.ts
	c:/Typescript/built/local/lib.es2017.intl.d.ts
	c:/Typescript/built/local/lib.es2017.typedarrays.d.ts
	c:/Typescript/built/local/lib.es2018.asyncgenerator.d.ts
	c:/Typescript/built/local/lib.es2018.asynciterable.d.ts
	c:/Typescript/built/local/lib.es2018.intl.d.ts
	c:/Typescript/built/local/lib.es2018.promise.d.ts
	c:/Typescript/built/local/lib.es2018.regexp.d.ts
	c:/Typescript/built/local/lib.es2019.array.d.ts
	c:/Typescript/built/local/lib.es2019.object.d.ts
	c:/Typescript/built/local/lib.es2019.string.d.ts
	c:/Typescript/built/local/lib.es2019.symbol.d.ts
	c:/Typescript/built/local/lib.es2020.bigint.d.ts
	c:/Typescript/built/local/lib.es2020.promise.d.ts
	c:/Typescript/built/local/lib.es2020.string.d.ts
	c:/Typescript/built/local/lib.es2020.symbol.wellknown.d.ts
	c:/Typescript/built/local/lib.esnext.intl.d.ts
	c:/Typescript/built/local/lib.esnext.string.d.ts
	c:/temp/rush-repro-955/libraries/dtos/src/dtos/user.ts
	c:/temp/rush-repro-955/libraries/dtos/src/index.ts

Hey ! sorry for bothering you @sheetalkamat  :(
I made a better repro here: https://github.com/totomakers/rush-example
Maybe i can give you better information for helping you.

sample-app is a NestJS project, fresh install.

Normally, VScode provide me help for finding import, like the decorator @Controller

But with rush nothing happen, i (hope) is because of the node_modules folder is not the same as a classic node install.
Issue was provide in Rush, VSCode and Typescript
Maybe i miss the point :'( sorry and thanks for help

Hello @sheetalkamat ! Thanks for your time.
To be thorough I updated my repo https://github.com/RDeluxe/rush-repro-955
The README should explain everything. There are 3 projects there:

A vanille one (auto imports work)
Rush + yarn (not working)
Rush + pnpm (not working)

@RDeluxe  Thank you for repro. we will investigate this.

Very excited for this to get some attention @sheetalkamat!  This issue has been open for a lonnnng time.

Good news.. i have fix prototype available.. need to polish it and write some tests.. But i will get PR up soon.

still have this problem...

Good news.. i have fix prototype available.. need to polish it and write some tests.. But i will get PR up soon.

For those still searching, make sure that you have vscode installed with the WSL plugin. You must be sure that the WSL backend is used!


for loops not handled correctly

Full_Name: Eric Robert Peskin
Version: cvs tag loopy
OS: RedHat Linux xia.elen.utah.edu 2.2.16-3 #1 Mon Jun 19 18:10:14 EDT 2000 i686 unknown
spec: /home/xia/peskin/atacs/examples/vhd/for.vhd
log: /home/xia/peskin/atacs/examples/vhd/atacs.log
Submission from: xia.elen.utah.edu (<IP_ADDRESS>)
Submitted by: peskin
ATACS parses for loops in VHDL, but does not seem to implement them.
These could be handled by loop unrolling.
For example, I unrolled for.vhd to produce winery6.vhd.
The latter works, but the former does not.
See the sample session below:
497 xia:examples/vhd> atacs -lv patron3.vhd winery6.vhd wine_shop.vhd
wine_example4.vhd wine_shop
ATACS VERSION 4.1
Logging session in:  atacs.log
Compiling patron3.vhd ...
Compiled process patron
Storing module patron3 to patron3.tel
Compiling winery6.vhd ...
Compiled process winery
Storing module winery6 to winery6.tel
Compiling wine_shop.vhd ...
Compiled process shop
Storing module wine_shop to wine_shop.tel
Compiling wine_example4.vhd ...
Storing module wine_shop to wine_shop.tel
Loading timed event/level structure from:  wine_shop.tel
Initializing 3 cycles ... done
Searching for channels ... found channels.
498 xia:examples/vhd> atacs -lv patron3.vhd for.vhd wine_shop.vhd
wine_example4.vhd wine_shop
ATACS VERSION 4.1
Logging session in:  atacs.log
Compiling patron3.vhd ...
Compiled process patron
Storing module patron3 to patron3.tel
Compiling for.vhd ...
Compiled process winery
Storing module for to for.tel
Compiling wine_shop.vhd ...
Compiled process shop
Storing module wine_shop to wine_shop.tel
Compiling wine_example4.vhd ...
Storing module wine_shop to wine_shop.tel
Loading timed event/level structure from:  wine_shop.tel
WARNING:41:  winery_to_shop1! is not a signal!
WARNING:43:  winery_to_shop1! is not a signal!
WARNING:58:  winery_to_shop2! is not a signal!
WARNING:60:  winery_to_shop2! is not a signal!
Initializing 3 cycles ... done
Searching for channels ... found channels.
499 xia:examples/vhd>

ATACS still parses for loops in VHDL, without complaining about the
for loop itself, and then attempts synthesis.  That sort-of
constitutes claiming to support them.  The synthesis fails, because
the for loop is not actually implemented.  So, I'd still call that
Incorrect Behavior (rather than a Feature request.)
If, on the other hand, parsing a for loop issued an error like
for loops are not yet supported
and then stopped processing, in that case I'd call this a Feature
request to add support for for loops.

I would like to leave it as a feature request.  You may add an additional
feature request which is to report when unsupported VHDL syntax appears.
I think this will be very difficult to do though as there is more
unsupported than supported syntax.


commit to branch

Initial code setup for general review

https://github.com/SpikeInterface/spikeextractors/pull/299/files
On Mon, Dec 2, 2019 at 8:35 PM Saksham20<EMAIL_ADDRESS>wrote:

@Saksham20 https://github.com/Saksham20 requested your review on: #1
https://github.com/ben-dichter-consulting/traceextractors/pull/1 commit
to branch.
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/ben-dichter-consulting/traceextractors/pull/1?email_source=notifications&email_token=AAGOEETDOVXUBX7OITCHBKTQWWZXNA5CNFSM4JUQJGQ2YY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGOVHB6VJQ#event-2848189094,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAGOEETDFGWLL75ZEK2LHJDQWWZXNANCNFSM4JUQJGQQ
.

--
Ben Dichter, PhD
Data Science Consultant


Zeus doesn't reload code after change on macOS sierra

Description of Problem
Zeus doesn't reload code after changes on macOS sierra
System details
$ uname -a
Darwin Pavels-MacBook-Pro.local 16.0.0 Darwin Kernel Version 16.0.0: Mon Aug 29 17:56:20 PDT 2016; root:xnu-3789.1.32~3/RELEASE_X86_64 x86_64

$ ruby -v
ruby 2.3.1p112 (2016-04-26 revision 54768) [x86_64-darwin15]

Steps to Reproduce

zeus start in a new rails project
It boots fine, but one error is printed to the stdout:

zeus start
Starting Zeus server v0.15.10
[ready] [crashed] [running] [connecting] [waiting]
boot
└── default_bundle
    ├── development_environment
    │   └── prerake
    └── test_environment
        └── test_helper

Available Commands: [waiting] [crashed] [ready]
zeus rake
zeus runner (alias: r)
zeus console (alias: c)
zeus server (alias: s)
zeus generate (alias: g)
zeus destroy (alias: d)
zeus dbconsole
zeus test (alias: rspec, testrb)
2016-09-09 15:12 zeus-darwin-amd64[61609] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-22)

touch config/application.rb

Observed Behavior
Nothing happens
Expected Behavior
zeus should reload the code

I wonder if something in https://github.com/fsnotify/fsevents/blob/master/fsevents.go needs to be changed to support Sierra? Sadly that project has no tests so it's hard to isolate :-/. Zeus' test should catch this but I'd need a VM running Sierra, I'll see if I can spin one up.

@metcalf, seems so, I've recompiled the gem locally using go1.7.1 darwin/amd64, but the error is still there and the code reloading doesn't work :(

@pavel-d: I got Zeus running inside a Sierra VM and can't reproduce this issue. What version of the Sierra preview are you running? Can you try creating a new, clean project with Zeus in it and see if the same issue occurs?

@pavel-d: I upgraded my VM to the latest GM release of Sierra and still can't reproduce this. It'd be helpful to know if this repros for you on the latest Sierra release and with a new, clean project.

@metcalf, thanks! Sure, I'll dig a bit later this week

Hmm, having the same problem with an existing project in Sierra, will see if I can reproduce it too.

I just uncovered a slew of other bugs and edge cases in Zeus' file monitoring code (e.g. if you replace a watched file by moving another on top of it, it's no longer watched because the underlying inode changed). The work required to handle all these edge cases is great enough that I'm looking into ways to use Facebook's watchman in place of the current file monitoring code. I'm not sure when I'll be able to land that (or if it will work) so it'd still be great to have a repro of the Sierra issues, but if you can't repro than hopefully a solution is in the works!

I'm having the same exact issues as @pavel-d, Sierra 10.12 and zeus 0.15.10. Being stuck on Rails 3 never felt so bad. :(

Is this still open? It seems like it's more of an issue with fsevents

I'm having the same issue too. Sierra 10.12 (16A323), ruby 2.1.6p336, zeus 0.15.10.
After start i see
2016-10-03 19:46 zeus-darwin-amd64[27141] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-22)
and zeus does not reload code

@kyleholzinger Yes it's still open. The "closed" above your comment refers to the PR on the left which mentions this PR.

Right, was just wondering since this seems like an issue with cgo, not zeus @zubin

I've been researching this (since it's a blocker for our upgrade to macOS Sierra), and it seems something changed in Sierra to cause zeus's fsevents program to not work correctly anymore - the advice at https://github.com/facebook/react-native/issues/9309#issuecomment-238966924 says to bump kernel file limits (they were very low in 10.11, and I wonder if they got bumped even lower in 10.12).
The other piece of advice is to upgrade to watchman 4.6 (we don't use watchman in Zeus, but bear with me). It includes a bunch of fsevents-related changes over 4.5, mostly in stream setup, and the handling of the UserDropped attribute. I'm installing a Sierra VM right now, to attempt to repro this too, so maybe I can dig up something more substantial.

@antifuchs it's not zeus' fsevents specifically, it's cgo-- this is the line that it's breaking on, which is an external call

Oh, interesting, I thought zeus still ships its own objc fsevents wrapper! Disregard all I said, then (:

@antifuchs I'm not 100% positive but I think it uses the go one

+1

I was on sierra with 0.15.4 and was not experiencing this
2016-10-11 15:56 zeus-darwin-amd64[86241] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-22)

After upgrading to 0.15.10 the warning comes up.

Interesting, I wonder if they moved from native fsevents/self-packaged to cgo fsevents @pietdaniel

Was anyone able to resolve this? I come from React-native side and following their steps didnt help to resolve it.

I was able to resolve it as follows: https://github.com/facebook/react-native/issues/9309#issuecomment-238966924

Changing max files as suggested does not fix it for me.

@metcalf need a computer running Sierra to test? Wanna swing by one of these days?! I'm also experiencing this error and would be happy to help :-p

@pariser (or anyone else) any chance you have a Go environment set up and can try running make test under Sierra? I'm really hoping we can repro this in tests, add a test to https://github.com/fsnotify/fsevents that also repros the problem and fix it there.

(err, sorry @andrew-stripe == @metcalf, I'm signed in from my work account)

@andrew-stripe running now

@andrew-stripe @metcalf  just got this:
Error: Package "/Users/Kyle/workspace/zeus" not a go package or not in GOPATH

@kyleholzinger: Go likes a very particular directory structure. You need to set a GOPATH environment variable and place Zeus in $GOPATH/src/github.com/burke/zeus.

@andrew-stripe I just had a clean run on eb88f0816fd with go version go1.7.3 darwin/amd64 on 10.12.1.
cd rubygem && bin/rspec
.............................

Finished in 0.02885 seconds (files took 0.09957 seconds to load)
29 examples, 0 failures

That snippet of output only refers to the Ruby tests, I'd have expected to see failures (if any) in the Go tests. Those look like:
ZEUS_TEST_GEMPATH="/Users/andrew/code/go/src/github.com/burke/zeus/rubygem" GO15VENDOREXPERIMENT=1 govendor test +local
?   	github.com/burke/zeus/go/clienthandler	[no test files]
?   	github.com/burke/zeus/go/cmd/zeus	[no test files]
?   	github.com/burke/zeus/go/config	[no test files]
ok  	github.com/burke/zeus/go/filemonitor	1.391s
?   	github.com/burke/zeus/go/messages	[no test files]
?   	github.com/burke/zeus/go/processtree	[no test files]
?   	github.com/burke/zeus/go/shinylog	[no test files]
?   	github.com/burke/zeus/go/statuschart	[no test files]
ok  	github.com/burke/zeus/go/unixsocket	0.008s
?   	github.com/burke/zeus/go/zerror	[no test files]
?   	github.com/burke/zeus/go/zeusclient	[no test files]
ok  	github.com/burke/zeus/go/zeusmaster	1.954s
?   	github.com/burke/zeus/go/zeusversion	[no test files]

Sorry about that, here's the output I have:
ZEUS_TEST_GEMPATH="/Users/mcolyer/gopath/src/github.com/burke/zeus/rubygem" GO15VENDOREXPERIMENT=1 govendor test +local
?       github.com/burke/zeus/go/clienthandler  [no test files]
?       github.com/burke/zeus/go/cmd/zeus       [no test files]
?       github.com/burke/zeus/go/config [no test files]
ok      github.com/burke/zeus/go/filemonitor    1.256s
?       github.com/burke/zeus/go/messages       [no test files]
?       github.com/burke/zeus/go/processtree    [no test files]
?       github.com/burke/zeus/go/shinylog       [no test files]
?       github.com/burke/zeus/go/statuschart    [no test files]
ok      github.com/burke/zeus/go/unixsocket     0.008s
?       github.com/burke/zeus/go/zerror [no test files]
?       github.com/burke/zeus/go/zeusclient     [no test files]
ok      github.com/burke/zeus/go/zeusmaster     1.683s
?       github.com/burke/zeus/go/zeusversion    [no test files]

Hmm, doesn't fail tests, that makes life more difficult. That would be consistent with the explanation that it has to do with max file limits since the tests watch very few files. Recent versions of Watchman encourage you to watch an entire project directory which may help avoid this.
I'm not sure whether errors from the file watching code were surfaced in the same way in 0.15.4. It may have the same issue and is just swallowing the error message. Can anyone confirm whether they observe reloading on file changes on Sierra in 0.15.4 and not 0.15.10 (regardless of any error messages)?

I'm not seeing any reloading behavior in v0.15.4 or v0.15.10. (Nor am I seeing any error messages in v0.15.4).

Sounds like this was always broken and the old file monitor just swallowed the error messages. That's not surprising given how it worked.
My barely-informed guess is that this has to do with Zeus tracking each individual file instead of setting up a watch on the project directory. The test suite doesn't track enough files to hit any kind of limit and raising the maxfiles limit works for some projects. Assuming this is correct, the fix could be local to the filemonitor package but it wouldn't be trivial. It's also possible that something in https://github.com/fsnotify/fsevents/blob/master/fsevents.go is broken for Sierra.
We've decided to move away from Zeus in favor of our own code loader with Watchman for file monitoring. I'm happy to help review changes and answer questions but I don't expect to be investing much more in Zeus.

@andrew-stripe Do you have some examples of replacing zeus with watchman?

Unfortunately nothing off the shelf. We're building internal tooling that's
somewhat specific to our codebase. I'm hoping to open source the work
someday, but given that we're only about to go into internal beta that
could be quite awhile.
On Thu, Nov 10, 2016 at 5:41 AM, Alexey Kuznetsov<EMAIL_ADDRESS>wrote:

@andrew-stripe https://github.com/andrew-stripe Do you have some
examples of replacing zeus with watchman?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/burke/zeus/issues/589#issuecomment-259692295, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AWAzbFsp6MkIAjVlON2K0z-8lGP6KcCYks5q8x7ugaJpZM4J5EKO
.

I've switched to using spring, seems it still works with the latest OSX sierra.

I wonder if a quick fix for that would be to monitor directory instead of files on osx, it seems to work everywhere except osx. I ran into it today as well but only on a larger rails app trying to figure out the limit now.

This seems to be related to the number of monitored files as I have 2 apps 1 causes the issue (the bigger) and a smaller which does not experience it, this is on the same machine with the same version of zeus.
To resolve this the way to go seems to be to monitor the directory instead of the files for changes and then filter in the filemonitor for events we are interested in (based on the file). I took a look at the code in filemonitor_darwin and it seems to be reasonable enough to change it here without the need to touch much else. First step so is to add a test as I wonder what the amount of files needed is. I'm gonna give this a shot when I have a Mac available (aka work).

It would be nice to see that commit by @sideshowcoder merged into master and new gem released. Having to constantly restart zeus is kind of antithetical to its existence.

@siannopollo sadly the commit is not a fix yet, but just a failing test and a description of the fix I'm working towards, any help is greatly appricieated and I'm happy to merge as soon as it is ready 👍

@siannopollo if you fancy testing a local built, #620 now includes a potential fix for the problem, I have to do some more local testing before merging but it seems like it fixes the issue.

Please check version 0.15.13.pre and see if it fixes the problem it seems to work for my setup.

0.15.13.pre fixed the error for me! 👍  Thank you @sideshowcoder !

I'd consider this a fix then, seem to have the same success on other machines as I can see locally here 👍

0.15.13.pre also fixed this issue for me. Thanks @sideshowcoder

I feel like from now on if this fixed anyones issue just respond with a reaction to one of the other messages haha. Plz no more emails ❤

@kyleholzinger Don't you find it ironic that in order to voice that opinion, you had to leave a comment that would send emails to everyone on this thread? I mean, Github provides a Subscribe/Unsubscribe button at the top of each issue if you don't want to be notified any more... ¯_(ツ)_/¯

no, I would like to be notified of legit followups to this if it ever gets opened again

@kyleholzinger But you have no control over the actions of others. So instead of trying to dictate how others should behave to suit your preferences, please just use the tools that Github provides to achieve the experience you desire.

It was a request not a demand, and a very reasonable one, since that is proper GitHub etiquette. I am stopping responding now, as I do not want to bother other people any more with this meaningless babel.

@kyleholzinger Is classifying a seemingly civil discourse as "meaningless babel" also proper GitHub etiquette? Since this has devolved to name-calling, I'll unsubscribe from this thread now.

🎭


Create CLI to perform cookie analysis on sets of URLs (e.g. Sitemap)

Feature Request
Description:
A node based CLI that takes a sitemap as input and produces a JSON file capturing all cookies set by the URLs in the sitemap.
User Story:
As a developer/website owner, I want to be have the capability to run the cookie analysis tool and get report of cookie usage/status for batches of URLs.
Acceptance Criteria:

[ ] Use Puppeteer (https://pptr.dev/)
[ ] A sitemap can be processed and a valid JSON file is returned with the collected cookies and the results from the analysis performed.
[ ] The CLI architecture is designed to make the tool extensible

@gagan0123 @pradeep910 This capability becomes applicable in the context of automated testing for breakage discovery.


How to remove Shadow casted by HDR image.

Current behavior
Currently I am using ModelViewer class to load my gltf Model and IBL for lighting, and for that I am using HDR images. but current IBL images show shadow of the HDR images on my model and that looks little weird. I have attached video below.
https://user-images.githubusercontent.com/86815724/153827864-07792959-5519-472b-85c0-36ddd752e3ee.mp4
Expected behavior
But actually I wants to apply lighting without having shadow on the mode. Similar to below video.
https://user-images.githubusercontent.com/86815724/153828060-31e20666-1d5c-45e8-89d3-ec246c46f71b.mp4
I have tried some HDR images but shadow/reflection is always there. so is there are other way to remove shadow/reflection and apply lighting only ?
Also if you can suggest any HDR image with minimal shadow shadow/reflection, it will be really helpful.
Thanks in Advance.

There are no "shadows", what you are seeing is the result of lighting being applied. If the lighting you are getting is not to your liking, you should use a different IBL. The second video you are showing still shows reflections, it just happens to not have darker areas because the IBL doesn't have them.


chore(main): release 1.5.0

:robot: I have created a release beep boop
1.5.0 (2024-11-16)
Features

add adult parsing (70be90e)

This PR was generated with Release Please. See documentation.

Summary by CodeRabbit

New Features

Introduced adult parsing functionality in version 1.5.0.

Chores

Updated project version from 1.4.1 to 1.5.0.
Updated regex dependency to version ^2023.12.25.

:robot: Created releases:

v1.5.0
:sunflower:


 I can't remember how many colleagues I recommended using it.
There's a problem I've encountered. According to the spec providing JSON params is done via the := operator.  But launching httpie 0.9.9 with these params:
http post localhost/example/ param1="a b c" param2=d jparam:='["test string"]'

Results in a message about invalid JSON. But ["test string"] is valid JSON afaik.
http: error: "jparam:='[test string]'": Expecting value: line 1 column 1 (char 0)

Maybe anyone could shed some line on what seems to be wrong?

Correct me if I'm wrong, but isn't a JSON object usually in the format {"key":"value"}?

@poskadesign the command looks okay and it works for me in Bash. It could be some escaping issue if you use some other shell.
$ http -v httpbin.org/post  param1="a b c" param2=d jparam:='["test string"]'

POST /post HTTP/1.1
Accept: application/json, */*
Accept-Encoding: gzip, deflate
Connection: keep-alive
Content-Length: 61
Content-Type: application/json
Host: httpbin.org
User-Agent: HTTPie/0.9.9

{
    "jparam": [
        "test string"
    ],
    "param1": "a b c",
    "param2": "d"
}

HTTP/1.1 200 OK
Access-Control-Allow-Credentials: true
Access-Control-Allow-Origin: *
Connection: keep-alive
Content-Length: 568
Content-Type: application/json
Date: Sun, 14 May 2017 10:58:53 GMT
Server: meinheld/0.6.1
Via: 1.1 vegur
X-Powered-By: Flask
X-Processed-Time: 0.000903844833374

{
    "args": {},
    "data": "{\"param1\": \"a b c\", \"param2\": \"d\", \"jparam\": [\"test string\"]}",
    "files": {},
    "form": {},
    "headers": {
        "Accept": "application/json, */*",
        "Accept-Encoding": "gzip, deflate",
        "Connection": "close",
        "Content-Length": "61",
        "Content-Type": "application/json",
        "Host": "httpbin.org",
        "User-Agent": "HTTPie/0.9.9"
    },
    "json": {
        "jparam": [
            "test string"
        ],
        "param1": "a b c",
        "param2": "d"
    },
    "origin": "…",
    "url": "http://httpbin.org/post"
}

Hi, I'm a newbie to open source projects. I would like work on this issue. Could you please provide me with more info?

@poskadesign What OS and shell is that? It looks like your shell consumed the double quotes to avoid word-splitting on the space, but then left the single quotes in the argument.

It is something like that.. http POST https://httpbin.org/post wicked=witch casts:='["spells", "curses"]' --json

@sriyanfernando still doesn't work (httpie 0.99, Windows 10x64, Python 3.61, standard Windows Command Prompt):
C:\Users\Me>http post localhost:8000/mail/<EMAIL_ADDRESS>--json
usage: http [--json] [--form] [--pretty {all,colors,format,none}]
            [--style STYLE] [--print WHAT] [--headers] [--body] [--verbose]
            [--all] [--history-print WHAT] [--stream] [--output FILE]
            [--download] [--continue]
            [--session SESSION_NAME_OR_PATH | --session-read-only SESSION_NAME_OR_PATH]
            [--auth USER[:PASS]] [--auth-type {basic,digest}]
            [--proxy PROTOCOL:PROXY_URL] [--follow]
            [--max-redirects MAX_REDIRECTS] [--timeout SECONDS]
            [--check-status] [--verify VERIFY]
            [--ssl {ssl2.3,ssl3,tls1,tls1.1,tls1.2}] [--cert CERT]
            [--cert-key CERT_KEY] [--ignore-stdin] [--help] [--version]
            [--traceback] [--default-scheme DEFAULT_SCHEME] [--debug]
            [METHOD] URL [REQUEST_ITEM [REQUEST_ITEM ...]]
http: error<EMAIL_ADDRESS>Expecting value: line 1 column 1 (char 0)

@poskadesign Try this:
http post localhost/example/ param1="a b c" param2=d jparam:="[\"test string\"]"

I'm not very familiar with Windows command line, but found https://stackoverflow.com/questions/17205292/quotes-around-quotes-in-windows-command-line which is similar.


ViewModels request new data each time view is recreated

If PlantListFragment or GardenPlantingListFragment are recreated, their ViewModels make a new database request instead of returning the last value held by the livedata.
For example:
fun getGardenPlantings() = gardenPlantingRepository.getGardenPlantings()

fun getPlantAndGardenPlantings() = gardenPlantingRepository.getPlantAndGardenPlantings()

The Arch docs say this is a not to do this (link):
    private LiveData<String> getPostalCode(String address) {
       // DON'T DO THIS
       return repository.getPostCode(address);
    }

The UI component then needs to unregister from the previous LiveData object and register to the new instance each time it calls getPostalCode(). In addition, if the UI component is recreated, it triggers another call to the repository.getPostCode() method instead of using the previous call’s result.

The Arch components BasicSample shows a better way to implement this using MediatorLiveData (link)
When I implemented this myself, using the MediatorLiveData also fixed #10
https://github.com/chris-feldman/android-sunflower/blob/master/app/src/main/java/com/google/samples/apps/sunflower/viewmodels/PlantListViewModel.kt

Thanks for the detailed write-up!  Would you be interested in opening a pull request to update the two list ViewModels?

Sure, I'll see if I can get one together today 👍
On Tue, Jun 5, 2018, 11:21 PM Tiem Song<EMAIL_ADDRESS>wrote:

Thanks for the detailed write-up! Would you be interested in opening a
pull request to update the two list ViewModels?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/googlesamples/android-sunflower/issues/24#issuecomment-394927733,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AWQj3YRw8qHSnL3g4uRi4eWNSlj-EeK1ks5t50q4gaJpZM4UbGgs
.

I think better solution is to use new fragment life cycle while observing live data.
Read this
https://medium.com/@BladeCoder/architecture-components-pitfalls-part-1-9300dd969808
check note at end of post
We need to update support lib as new view life cycle is there in 28.0.0

Yeah sorry my bad. Thing is every time you switch fragment from GardenPlantListing to PlantListing and vice versa onCreateView will get call and method in view model also. Which will end up in querying database multiple times. Your PR will fix this issue.
However there is one issue of multiple observation on livedata. So each time you switch fragment new live data observer is being registered. This will lead to multiple callbacks for livedata observer and because of this multiple notifyDataSetChanged() in adapter.
I have figured out this issue. @tiembo Should I create new issue for this ?

Hi @sagar-viradiya - yes, please open a new issue and we can discuss the livedata changes there.

Closing issue; fixed via #33


New favicon and image

Add a new favicon (it's pixel) instead of the original one:

image is 32 * 32 pixels btw


MNT: Consider archiving stale repos in the org

For example: Published papers, past workshops, defunct projects.

We did that, I think.


Time-series charts and card time ranges

Summary

Initial drop of time series cards with carbon charts
Added time range dropdown for cards

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 2.0.0-beta.9 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.67.0 :tada:
The release is available on npm package (@release-1.x dist-tag)
Your semantic-release bot :package::rocket:


fix(xml): fix regression - use parent attibute only for styles

I'm sorry, my previous commit 378c747 introduced a regression. 378c747 added an empty parent attribute to arrays, plurals and attrs. This commit adds a check for type "style" to restore the previous behavior.

@nitram84 thanks :+1:


Reconstruct original message after handling commands

Pull request summary

When reply messages are received, the user is cut off to be able to handle commands. After commands are now the original message is reconstructed, including the username who was replied to.
Checklist

[x] If code changes were made then they have been tested.

[ ] I have updated the documentation to reflect the changes.
[ ] I have updated the changelog with a quick recap of my changes.

[x] This PR fixes an issue.
[ ] This PR adds something new (e.g. new method or parameters).
[ ] This PR is a breaking change (e.g. methods or parameters removed/renamed)
[ ] This PR is not a code change (e.g. documentation, README, ...)

LGTM


Update sources

:robot_face: Updating sources to the latest version.
Commits touching OCaml packages:
Diff URL: https://github.com/NixOS/nixpkgs/compare/79688fd4b2a13bf07b61eb75716c4b0d8146e4f0...af4cf4d6ae4a47fc9a8b58ea6238455a3acf0292

This seems to contain the staging merge which has the stdenv bootstrap refactor.


Move all package and container versions to group_vars/all.yml

It would be nice to be able to see/set versions for the entire platform in one place.  This was implemented for kube_version in #736 and would be nice to see for all packages and containers.

I think most versions / images are configurable.
If some are missing, please list them individually.


k8s overlays are not allowed on BaseComponentSpec

With Istio 1.6.1, k8s overlays are allowed on cluster scoped resources. However, resources such as validatingwebhookconfiguration which are part of BaseComponentSpec are not allowed for overlays.
With this https://github.com/istio/istio/pull/23798, only a subset of cluster scoped resources are allowed for overlays.
https://istio.io/docs/reference/config/istio.operator.v1alpha1/#BaseComponentSpec

Please assign this issue to @ostromart

@morvencao Please add cherrypick label for 1.6 branch. Thanks

@istio-testing Please add cherrypick label for 1.6 branch


Fix panic during tsdb Commit

Fixes the following
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x20 pc=0x19deb45]
goroutine 651118930 [running]:
github.com/prometheus/prometheus/tsdb.(*headAppender).Commit(0xc19100f7c0)
/drone/src/vendor/github.com/prometheus/prometheus/tsdb/head_append.go:855 +0x245
github.com/prometheus/prometheus/tsdb.dbAppender.Commit({{0x35bd6f0?, 0xc19100f7c0?}, 0xc000fa4c00?})
/drone/src/vendor/github.com/prometheus/prometheus/tsdb/db.go:1159 +0x2f
We theorize that the panic happened due the the series referenced by the exemplar being removed between AppendExemplar and Commit due to being idle.

@jesusvazquez @bboreham plz merge if you agree, thx


how to detect my dataset?

i finish LEVIR-CD training and get the new best_ckpt.pt.
So how do i use this new weight(best_ckpt.pt) to predict my picture?
my picture are aerial image (before and after scene, only two images).
before image input A folder
after image input B folder
but i did not label image, so i would not put anything in label folder.
how do i predict my picture?

@stphtan94117 hey,
The label is used to compute the quantitative performance metrics. If you do not have a label available, pls include a dummy label (ie, all zeros) of the same size as input A in the label folder.
Thanks.


Make people able to propose a new badge, through a web form

I mean: for those who have no access to the source code.

Yes :) It's already covered by the current @pierallard PR: #78
Still in WIP, but we will definitely put it in the app!


Failed to mount component: template or render function not defined - BPopover

Hello,
Recently all my click-confirm buttons are now failing after running 'npm run dev' during development of new components. Click-Confirm was working fine for months until a couple days ago. Any ideas on what could be the cause of this issue?
[Vue warn]: Failed to mount component: template or render function not defined.

found in

---> <BPopover>
       <ClickConfirm>

I found a workaround, just remove this line from click-confirm.common.js:
var bPopover = _interopDefault(require('bootstrap-vue'));
and then
components: {
        bPopover: bPopover
}

and import Popover Plugin Globally in your app
import { PopoverPlugin } from 'bootstrap-vue';`
Vue.use(PopoverPlugin);

And it works.

I found a workaround, just remove this line from click-confirm.common.js:
var bPopover = _interopDefault(require('bootstrap-vue'));
and then
components: {
        bPopover: bPopover
}

and import Popover Plugin Globally in your app
import { PopoverPlugin } from 'bootstrap-vue';`
Vue.use(PopoverPlugin);

And it works.


Save Blockrain activity context in Journal

The Blockrain activity don't store its current state and high score in the Journal. So when you close the activity everything is lost.

Blockrain activity source code is here: https://github.com/llaske/sugarizer/tree/dev/activities/Blockrain.activity
Adding datastore handling to an existing activity is explain here: https://github.com/llaske/sugarizer/blob/dev/docs/tutorial_step4.md

Fixed in https://github.com/llaske/sugarizer/commit/8f6a6f7fd28c8e7a2b77f653f48fb1421b5d64d1.


@As annotation command didn't seem to work with SelenideElement

The problem
Taking inspiration from this article, I tried to use @As annotation alias to get meaningful names in the report but that didn't work.
Note: When I use it as $.as() that works.
Example (this works):  private static final SelenideElement USER_NAME_INPUT = $("input[id='edit-name']").as("USER_NAME_INPUT"); it works. So its only the annotation that didnt work.
Details
Below is the report that shows that aliases work when I use the as command with element but not when I use @At annotation.
[INFO]	2022-12-22 17:11:40,723	[SimpleReport]: Report for assertThatUserCanNotAddPatientIfMissingMandatoryFields()
+----------------------------------------------------------------------------------+------------------------------------------------------------------------+------------+------------+
| Element                                                                          | Subject                                                                | Status     | ms.        |
+----------------------------------------------------------------------------------+------------------------------------------------------------------------+------------+------------+
| webdriver                                                                        | create()                                                               | PASS       | 4056       |
| open                                                                             | https://dev8.ebloodbanking.com                                         | PASS       | 7294       |
| USER_NAME_INPUT                                                                  | should be(editable)                                                    | PASS       | 70         |
| USER_NAME_INPUT                                                                  | set value(dummyUserName)                                         | PASS       | 60         |
| input[id='edit-pass']                                                            | should be(editable)                                                    | PASS       | 46         |
| input[id='edit-pass']                                                            | set value(*******)                                                   | PASS       | 51         |
| SUBMIT_BUTTON                                                                    | should be(visible)                                                     | PASS       | 23         |

Tell us about your environment

Selenide Version:   <selenide.version>6.10.1</selenide.version>
Chrome\Firefox\IE Version:  Chrome
Browser Driver Version:  Version 108.0.5359.125 (Official Build) (64-bit)
Selenium Version: default from selenide
OS Version: Windows 10

Running tests with Junit5.
Code To Reproduce Issue [ Good To Have ]
private static final SelenideElement USER_NAME_INPUT = $("input[id='edit-name']").as("USER_NAME_INPUT");

    @As("PASSWORD_INPUT")
    private static final SelenideElement PASSWORD_INPUT = $("input[id='edit-pass']");

@PramodKumarYadav Works as expected.
As mentioned in this article, annotation @As is needed for cases when you have a page object with @FindBy annotations.
In your example, there is no page object, no @FindBy annotations.
In order to make annotations work, you need to initialize page object using method Selenide.page or Selenide.open(url, class).

Thanks for the answer @asolntsev. This explains.
P.S: Out of curiosity, would it be possible to also let the annotations work for Selenide elements? Code would look much more cleaner with those.

Why @As looks more cleaner than .as? I don't see any difference.

would it be possible to also let the annotations work for Selenide elements?
I answer in my previous comment: annotation will work if you initialize page object using method Selenide.page or Selenide.open(url, class).

Why @As looks more cleaner than .as? I don't see any difference.

Cant really defend this since this seems more of a matter of a taste. The only thing I could say is with annotation all names are always aligned on top of elements (as below).
@As("SUBMIT_BUTTON")
private static final SelenideElement SUBMIT_BUTTON = $("button[id='edit-submit']");

@As("SEND_PASSWORD_RESET_INSTRUCTIONS_LINK")
 private static final SelenideElement SEND_PASSWORD_RESET_INSTRUCTIONS_LINK = $("a[class='request-password-link']");

With .as(), depending on how big the selector is the name can get lost towards the right end (as in below example) and would need a bit of scrolling. .
private static final SelenideElement SUBMIT_BUTTON = $("button[id='edit-submit']").as("SUBMIT_BUTTON");

private static final SelenideElement SEND_PASSWORD_RESET_INSTRUCTIONS_LINK = $("a[class='request-password-link']").as("SEND_PASSWORD_RESET_INSTRUCTIONS_LINK");

First of all, thanks for your prompt responses @asolntsev . I appreciate it :).
For below:

I answer in my previous comment: annotation will work if you initialize page object using method Selenide.page or Selenide.open(url, class).

I tried initialing the page using the Selenide.open(url, class) as below, but still in reports, I do not see the alias. Maybe I am doing something wrong that you can see from here?
class LoginPageTest extends TestBase {
    LoginPage loginPage;

    @BeforeEach
    public void setup() {
        loginPage = open(CONFIG.getString("LOGIN_URL"), LoginPage.class);
    }

    @Test
    void assertThatUserCanLoginWithValidUser() {
        loginPage
                .loginWith(CONFIG.getString("USERNAME"), CONFIG.getString("PASSWORD"))
                .shouldRedirectToHomePage();
    }
}

Login page contains these two elements as below.
private static final SelenideElement USER_NAME_INPUT = $("input[id='edit-name']").as("USER_NAME_INPUT");

    @As("PASSWORD_INPUT")
    private static final SelenideElement PASSWORD_INPUT = $("input[id='edit-pass']");

Report only shows the alias for the one that was named using .as() and the one with @As annotation still shows the selector.
[INFO]	2022-12-22 20:17:16,303	[SimpleReport]: Report for [engine:junit-jupiter]/[class:com.jagriti.plasma.tests.LoginPageTest]/[method:assertThatUserCanLoginWithValidUser()]
+-----------------------+------------------------------------------------------------------------+------------+------------+
| Element               | Subject                                                                | Status     | ms.        |
+-----------------------+------------------------------------------------------------------------+------------+------------+
| webdriver             | create()                                                               | PASS       | 4040       |
| open                  | https://dev8.ebloodbanking.com                                         | PASS       | 7232       |
| USER_NAME_INPUT       | should be(editable)                                                    | PASS       | 67         |
| USER_NAME_INPUT       | set value(*****)                                         | PASS       | 56         |
| input[id='edit-pass'] | should be(editable)                                                    | PASS       | 47         |
| input[id='edit-pass'] | set value(*****)                                                   | PASS       | 48         |
| SUBMIT_BUTTON         | should be(visible)                                                     | PASS       | 25         |
| SUBMIT_BUTTON         | click()                                                                | PASS       | 5337       |

@PramodKumarYadav Ah yes, then the field should not be static.
Why you want to create a page object instance, but make its fields static? static is evil.
See https://www.youtube.com/watch?v=dFQSOlOOoXE&list=PLfazdZ9SzB9eDJIugtfH7KeVLLAP1pDLh&ab_channel=DEVCLUB.EE

static is evil

I agree :). It was my bad to keep the field static. Keeping them static for a by locator would still not be an issue (since that would not change per element) but keeping it static for a SelenideElement is indeed bad since an element can have different state/properties depending on the test.

Ah yes, then the field should not be static.
Why you want to create a page object instance, but make its fields static?

I changed the elements to non-static (and also non final) and yet I see the same result .
private SelenideElement USER_NAME_INPUT = $("input[id='edit-name']").as("USER_NAME_INPUT");

@As("PASSWORD_INPUT")
private SelenideElement PASSWORD_INPUT = $("input[id='edit-pass']");

| USER_NAME_INPUT       | should be(editable)                                                    | PASS       | 69         |
| USER_NAME_INPUT       | set value(*******************)                                         | PASS       | 124        |
| input[id='edit-pass'] | should be(editable)                                                    | PASS       | 49         |
| input[id='edit-pass'] | set value(*********)                                                   | PASS       | 121        |

@PramodKumarYadav As I mentioned before, @As annotation was initially intended to work only with fields annotated with @FindBy.
But why not, now I also added PR for using @As annotation with usual $ fields: https://github.com/selenide/selenide/pull/2088

@asolntsev : You rock!  🙌 😊. Thanks for the feature addition!


Support to Laravel ^9.4

I'm using Laravel 9.41.0, when I try to install this plugin:
 composer require --dev psalm/plugin-laravel
Info from https://repo.packagist.org: #StandWithUkraine
Using version ^2.0 for psalm/plugin-laravel
./composer.json has been updated
Running composer update psalm/plugin-laravel
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - orchestra/testbench 6.x-dev requires laravel/framework ^8.83.26 -> found laravel/framework[v8.83.26, 8.x-dev] but it conflicts with your root composer.json require (^9.0).
    - orchestra/testbench[v7.9.0, ..., 7.x-dev] require symfony/yaml ^6.0.9 -> found symfony/yaml[v6.0.10, ..., 6.3.x-dev] but the package is fixed to v5.4.14 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
    - orchestra/testbench v6.22.0 requires laravel/framework ^8.65 -> found laravel/framework[v8.65.0, ..., 8.x-dev] but it conflicts with your root composer.json require (^9.0).
    - orchestra/testbench v6.23.0 requires laravel/framework ^8.67 -> found laravel/framework[v8.67.0, ..., 8.x-dev] but it conflicts with your root composer.json require (^9.0).
    - orchestra/testbench v6.23.1 requires laravel/framework ^8.71 -> found laravel/framework[v8.71.0, ..., 8.x-dev] but it conflicts with your root composer.json require (^9.0).
    - orchestra/testbench[v6.23.2, ..., v6.25.1] require laravel/framework ^8.75 -> found laravel/framework[v8.75.0, ..., 8.x-dev] but it conflicts with your root composer.json require (^9.0).
    - orchestra/testbench[v7.0.0, ..., v7.8.1] require symfony/yaml ^6.0 -> found symfony/yaml[v6.0.0-BETA1, ..., 6.3.x-dev] but the package is fixed to v5.4.14 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
    - psalm/plugin-laravel[v2.0.0, ..., v2.0.1] require orchestra/testbench ^6.22 || ^7.0 -> satisfiable by orchestra/testbench[v6.22.0, ..., 6.x-dev, v7.0.0, ..., 7.x-dev].
    - Root composer.json requires psalm/plugin-laravel ^2.0 -> satisfiable by psalm/plugin-laravel[v2.0.0, v2.0.1].

Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.
You can also try re-running composer require with an explicit version constraint, e.g. "composer require psalm/plugin-laravel:*" to figure out if any version is installable, or "composer require psalm/plugin-laravel:^2.1" if you know which you need.

Installation failed, reverting ./composer.json and ./composer.lock to their original content.

I wonder why we have testbench as a runtime dependency? Shouldn't it be moved to require-dev (if it's used at all).

It is used when booting the application: https://github.com/psalm/psalm-plugin-laravel/blob/39e4241061bc374c3b5dcf2bd5f209e37626636d/src/Providers/ApplicationProvider.php#L60


Ouzel openGL mode can't draw any content until moved/resized on macOS 10.14

Code: master latest, sample project.
Hardware: Macbook pro 15inch 2018
Renderer: Opengl

This is fixed in https://github.com/elnormous/ouzel/commit/eaa566abbee8a2c6e2e07bf4ecfb51960ba5debb

This is fixed in https://github.com/elnormous/ouzel/commit/eaa566abbee8a2c6e2e07bf4ecfb51960ba5debb

I spent some time debugging how NSOpenGLView works and why it has no problems with rendering immediately. I disassembled the NSOpenGLView and found out that it is creating a custom layer (class: _NSOpenGLViewBackingLayer). I tried to create the same layer and it worked. I start to investigate the code of the _NSOpenGLViewBackingLayer and found out that it does some stuff in the display method and it is a subclass of CALayer. I tried to copy the functionality of the _NSOpenGLViewBackingLayer, but with no success. Then I tried to simply create an instance of CALayer and it worked!
PS. One call to [NSOpenGLContext update] must be made (it is done in [NSOpenGLView openGLContext] method.

Ok, my fix broke compatibility with older macOS which does not use layers for rendering. Did some more disassembling and came to a fix, that works both on Mojave and older versions on macOS: https://github.com/elnormous/ouzel/commit/7e708636189d970bad6b013ecd5375cfe693f3f3
Basically calling [NSOpenGLContext update] without a layer attached to the view does nothing and usually, it is not attached to the view on the first frame (that is why you have to do it on the second one). But this risky, because the layer can be attached to the view sometime later. My fix updates the NSOpenGLContext as soon as the layer is being set.


Frontend support

create (optional?) frontend templates and routes

I was wondering if this gem is still maintained?

@Thrasheristico yes, i use it :)


Holding shift to highlight multiple rows

Hi!
Currently the ability to click and drag to copy multiple rows exists. I was wondering if it would be a possibility to add the feature of holding shift to select all rows from the first clicked to the last.
This would also go along with holding ctrl, to select multiple rows not next to each other.
This would make data easier to copy and paste to and from other places.

Hey @sdkrocks ,
It is already possible to SHIFT + Arrow, I think adding SHIFT + CLICK is feasible soon.
But handling multi-selection is too complex and out of the scope of this package.

Hey @sdkrocks ,
It is already possible to SHIFT + Arrow, I think adding SHIFT + CLICK is feasible soon.
But handling multi-selection is too complex and out of the scope of this package.

Understood! Awesome. Thanks for considering it!

Available in V2


For in if syntax doesn't work anymore

{% for i in [1,2,3,4,5] if i == 2 %}
    Hello World!
{% endfor %}

Doesn't output anymore, using master branch.

fixed: 23813770de4

This also fixed a problem with the height not being correctly set in time.html.twig for symfony profiler.

You changed the semantics of for ... if ... though. Now the loop variable is changed on every iteration, even if the condition was not satisfied. Before the condition had to be true before the loop variable was changed.
See:
--TEMPLATE--
{% for i in 1..5 if i is odd -%}
    {{ loop.index }}.{{ i }}
{% endfor %}
--DATA--
return array()
--EXPECT--
1.1
2.3
3.5

This will not work anymore and instead output 1.1 3.3 5.5.

Found that out too! Time too add a regression test for this?

@fabpot Should we open a new ticket for the new bug?

fixed here: 40595b848e


Update 404checker.py

No vulnerabilities were found!

No vulnerabilities were found!

No vulnerabilities were found!

No vulnerabilities were found!


Run logistic regression on the dataset

:clock1: 3h
The lab solution should be copied to our project, the code should be cleaned and commented.

I will commit my code from the lab session

Add to report


Manually add GeoJSON layers to leaflet.draw

Using Leaflet.draw on it's own works very well.
However, I was trying to add some GeoJSON features to the map, which somehow seems to break the editing functionality.
The jsfiddle shows, that the code is working until I add a layer to the editable FeatureGroup.
Is there another way to do that?

can anyone confirm that this works for leaflet 1.0 Beta 2 and Leaflet Draw master-leaflet ?
I'm having trouble getting geoJson layer editable with the latest (beta) builds.

Yeah, it works on Leaflet-1.0.3


small-user-avatars - Support new issue page

part of #7856
Test URLs
https://github.com/nuxt/nuxt/issues?q=sort%3Aupdated-desc+is%3Aissue+is%3Aopen

Please include a screenshot in your PRs so that we can verify how it looks and to keep it for future reference