issues Lizard functions

I discovered some issues while testing the new Lizard functions:

GroundwaterObs_from_lizard.meta only returns start_hand, start_diver, timeseries_types as metadata

When a monitoring wells has a tube nr 11 and 1 GroundwaterObs_from_lizard returns tube_nr 11 also when tube_nr 1 is defined.
Example: monitoring well EEWP004

Type_timeseries = ‘combine’  returns KeyError: 'name'

When using multiple codes in a list, the tube numbers are overwritten. Therefore, only the last tube number will be used from the second tube
Example ['39F-0736', '39F-0737']

When using an extent with multiple pages, only the data of the last page is defined with the function _prepare_API_input

BUWP014 raises a ValueError: invalid literal for int() with base 10: '4-2', because the last three characters are not only numbers

Thanks Anouk, I will have a look so we can discuss them on Friday

I created a Pull Request to fix these issues.

GroundwaterObs_from_lizard.meta only returns start_hand, start_diver, timeseries_types as metadata
The other metadata is saved as attributes in the GroundwaterObs. For 'x' you can use GroundwaterObs.x

When a monitoring wells has a tube nr 11 and 1 GroundwaterObs_from_lizard returns tube_nr 11 also when tube_nr 1 is defined.
Example: monitoring well EEWP004
fixed

Type_timeseries = ‘combine’ returns KeyError: 'name'
fixed

When using multiple codes in a list, the tube numbers are overwritten. Therefore, only the last tube number will be used from the second tube
Example ['39F-0736', '39F-0737']
fixed

When using an extent with multiple pages, only the data of the last page is defined with the function _prepare_API_input
fixed

BUWP014 raises a ValueError: invalid literal for int() with base 10: '4-2', because the last three characters are not only numbers
This one was kind of a headache. The code 'BUWP014' has 12 tubes but the metadata list contains 19 instances because some tube numbers have 2 or 3 duplicates. This is probably due to replaced tubes or some other administrative issue. In Hydropandas it is rather annoying to have duplicate tubes, therefore I added some code to combine the data from the different tubes. I give a warning if the metadata of tubes with the same tube number differs.

Also added some logging.

fixed in dev branch


refactor eval framework library code to reduce duplicate code

In code/taxcompare/eval_framework.py, there are two places where @gregcaporaso left comments about refactoring. This refactoring would help reduce some duplication of code.

refactored beyond recognition


Make ErrorDetails dumpable, print errors array when failing.

The error message The request contains bad syntax or cannot be filled due to a fault from the client sending the request. is not very descriptive when a ClientError occurs. Also, trying to print the errors array results in:
<uber_rides.errors.ErrorDetails object at 0x10e630690>

This pull request adds a string representation for ErrorDetails so it is easily dumped. This pull request also prints out the errors array in fail_print() in the example app to give the user more details. For example:
The request contains bad syntax or cannot be filled due to a fault from the client sending the request.
[ErrorDetails: 401 unauthorized Missing scope: request]

Thanks for the PR. Please sign our CLA and we'll merge your requests.
https://docs.google.com/forms/d/1pAwS_-dA1KhPlfxzYLBqK6rsSWwRwH95OCCZrcsY5rk/viewform
On Tue, May 24, 2016, 8:05 AM David Ng<EMAIL_ADDRESS>wrote:

The error message The request contains bad syntax or cannot be filled due
to a fault from the client sending the request. is not very descriptive
when a ClientError occurs. Also, trying to print the errors array results
in:
<uber_rides.errors.ErrorDetails object at 0x10e630690>
This pull request adds a string representation for ErrorDetails so it is
easily dumped. This pull request also prints out the errors array in
fail_print() to give the user more details. For example:
The request contains bad syntax or cannot be filled due to a fault from the client sending the request.
[ErrorDetails: 401 unauthorized Missing scope: request]

You can view, comment on, or merge this pull request online at:
https://github.com/uber/rides-python-sdk/pull/13
Commit Summary

Make ErrorDetails dumpable, print errors structure when failing.

File Changes

M example/utils.py
https://github.com/uber/rides-python-sdk/pull/13/files#diff-0 (5)
M uber_rides/errors.py
https://github.com/uber/rides-python-sdk/pull/13/files#diff-1 (2)

Patch Links:

https://github.com/uber/rides-python-sdk/pull/13.patch
https://github.com/uber/rides-python-sdk/pull/13.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/uber/rides-python-sdk/pull/13

Merged these changes into the internal repo which will be reflected in the public repo soon. Closing this out.


How to modify contents of section Y?

Hello,
I've been using vim-airline for a long time and really enjoy it.  Thank you!  Recently I've begun trying to customize vim-airline's statusbar sections, and I've been unable to modify section Y to have a BOM (byte-order mark) indicator display, in addition to the file encoding and line ending indicators already displayed there.
A few days ago when I wanted to update section Z to display byte offset, all I had to do was add this line to my .vimrc file:
let g:airline_section_z = '%3p%% %{g:airline_symbols.linenr} %#__accent_bold#%3l%#__restore__#:%3v 𝐁 %5o'

Great!  This worked perfectly.
No such luck with section Y.  I've tried placing the following lines in my .vimrc file, but no matter what I do, the default value of g:airline_section_y is always returned whenever I run echo g:airline_section_y (output: %{airline#util#wrap(airline#parts#ffenc(),0)}), and the [bom] string doesn't appear when a file with a BOM is open.
Attempt 1:
" override g:airline_section_y
" see https://github.com/bling/vim-airline/issues/136#issuecomment-22958373
let g:airline_section_y = "%{&fenc}%{&bomb ? '[bom]' : ''}%{strlen(&ff) > 0 ? '['.&ff.']' : ''}"

Attempt 2:
" override the function referenced in g:airline_section_y
function! airline#parts#ffenc()
  return printf('%s%s%s', &fenc, &bomb ? '[bom]' : '', strlen(&ff) > 0 ? '['.&ff.']' : '')
endfunction

Next I came across the airline-parts help section, and maybe I need to do something with the airline#parts#define_function function?  I'm not sure what to do with this function however, or if it's even where I should be looking.
Any help you can offer would be greatly appreciated.  Thank you for taking the time to read this.  :)

Nevermind, I figured out how to do it after reading through the documentation more closely.
if has('autocmd')
  augroup airline_init
    autocmd!
    autocmd User AirlineAfterInit
      \ call s:airline_init()
  augroup END
endif

call airline#parts#define_function(
  \ 'fencbomffmt',
  \ 'Airline_file_encoding_bom_file_format'
\)

function! s:airline_init()
  let l:spc = g:airline_symbols.space
  let g:airline_section_y = airline#section#create_right([
    \ 'fencbomffmt'
  \])
  let g:airline_section_z = airline#section#create([
    \ 'windowswap',
    \ '%3p%%'.l:spc,
    \ 'linenr',
    \ ':%3v'.l:spc,
    \ '𝐁'.l:spc,
    \ '%5o'
  \])
endfunction

function! Airline_file_encoding_bom_file_format()
  return printf(
    \ '%s%s%s',
    \ &fenc,
    \ &bomb ? '[bom]' : '',
    \ strlen(&ff) > 0 ? '['.&ff.']' : ''
  \)
endfunction


test: more mods for osx permission issues

We may run into a situation where the sudo conda install still creates a file in /pkgs which is owned by root and that we can't access, so if that happens, then the solution is probably to either do the chmod at the end, or just delete the contents of pkgs which might not be a bad move anyway.


SALMON_TXIMPORT process produces two tsv files that are not marked for export

Description of the bug
The -profile test of nf-core/rnaseq runs the SALMON_TXIMPORT which produces six tsv files which marked for output:

salmon.merged.gene_counts.tsv
salmon.merged.gene_counts_length_scaled.tsv
salmon.merged.gene_counts_scaled.tsv
salmon.merged.gene_tpm.tsv
salmon.merged.transcript_counts.tsv
salmon.merged.transcript_tpm.tsv

... and two tsv files which are not marked for output:

salmon.merged.gene_tpm_length_scaled.tsv
salmon.merged.gene_tpm_scaled.tsv

I think that these files include valuable data and should be published alongside the others in the outdir.
Command used and terminal output
$ nextflow run -profile test,docker --outdir results

Relevant files
No response
System information
No response

Another file which would be helpful in the output (STAR-Salmon) would be the *gene_lengths.tsv: effective gene lengths. It is not included in output and would be good base information to have.

@dross101 the effective lengths have been output since 3.12.2

Modules has recently moved to nf-core/modules, so addressing this there, will then bump module etc here.

Solved in https://github.com/nf-core/rnaseq/pull/1302


update device model list. New devices: Pixel 2, Nexus 7 16_9 aspect ratio (beta)

could you please include a screenshot of the table from the WF editor?

Hi @trapacska !
Here is the screenshot:


Regression Bug: What happened to the UsersWhoHODLYou array?

Hi,
The latest commit https://github.com/bitclout/frontend/pull/132 seems to have broken the GetStatelessUser response. It no longer contains the UsersWhoHODLYou array, only the count.
I tried explicitly adding SkipForLeaderboard: false but that did not work.
This broke a feature in my app. Can we get this back, please?

NVM.. closing this out.
I ended up switching to the api/v0/get-hodlers-for-public-key route. That seems more appropriate anyway. Thanks!

I'm actually reopening this because api/v0/get-hodlers-for-public-key actually returns creators I hold. So, the original issue still exists.

Haha... closing again. Sorry.


simply-reactive is missing

Seems like the package "simply-reactive" is deleted from npmjs.com, but svelte-carousel depends on it. At first running npm install gave me errors telling that there is no such package as simply-reactive on github. But now I think someone figured it out that it was a problem and npm install no longer throws an error. But I'm curious what will happen next? I feel like some day we'll have problems with it again

Are there gonna be any fixes to the problem?

Fixed in<EMAIL_ADDRESS>


Log Exception in Micro-services

When exception raise in micro-service then no logs are created in respective micro-service

fixed


PDF generation not working on example page

I'm interested in using this lib, but the examples on the linked website open a new tab with nothing happening or downloading.
(using mac os catalina and latest chrome stable)

Also, it seems that the examples don't parse markdown links in the description.

we try to cover most of the markdown syntax, but there are still gaps, like images are not supported.
Can you point me to the place where you see that markdowns are not supported ?


WIP: 4-ci-srv-06: [no-test] Check for NPM dependency updates

Check for any outstanding update of point version of any outstanding NPM package dependency

[ ] npm-update

npm-update in progress on 4-ci-srv-06.
Log: https://logs.cockpit-project.org/logs/npm-update-1046-20200718-100707/


fix: notification time darkmode

Why
Notification create date was invisible in dark mode.

How
Added text-white for dark mode.

Test Plan

Superseded by #1860


Make tags available in GitHub project

This module has releases available in Puppet Forge, but there are no corresponding tags here. This is an issue for those who deploy modules from Git. When using r10k for environment management, deploying from Git is mandatory.
Pls replicate the tags from Forge in GitHub.

I agree. Big problem for me!

@maxchk Would you mind check this?


Correct recommendations template-faq.md

Added your information in a PR I was working on. Thanks for the update!
https://experienceleague.adobe.com/docs/target/using/recommendations/recommendations-design/template-faq.html?lang=en#section_6BD55203984A4D80A0C6F241AD7806DF
Can I use a profile script in a Recommendations design?
Yes. To use a profile script in a Recommendations design, wrap the name in ${...}. For example, if your profile script is named user.basket, refer it as ${user.basket} in the design. Note that the backslash implies that the profile script is not rendered by Velocity. Therefore, you cannot perform any operations on the profile script in a Velocity template. The value will be directly printed on the page.


Low voter turn out

Low MNO participation (~1000 from ~4600 in average excluding exchanges ~3800) in voting is hurting the proposal system:

MNOs who vote would be more likely to start engaging in discussions and maybe projects.
More voters participation reduces the influence of few loud (negative) voices.

In this thread several ideas were discussed including their pros/cons:

Conditioning MNOs rewards (partially) on voting.
Facilitating voting for example by enabling voting from the mobile wallet.

Here is a relevant proposal: Set Your Price Proposals


[20.09]  zoom-us: 5.6.13632.0328 -> 5.6.16775.0418

(cherry picked from commit 50a7cb2cfbcce473bdda321c0c4fbc6cef0a4946)
backport of https://github.com/NixOS/nixpkgs/pull/120032#event-4623564449

Motivation for this change
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 120038 at d6c2346b run on x86_64-linux 1

1 package failed to build:

zoom-us

Note that build failures may predate this PR, and could be nondeterministic or hardware dependent.
Please exercise your independent judgement.

It's broken. Why did this get merged?!
$ nix-build channel:nixos-20.09 -A zoom-us
these derivations will be built:
  /nix/store/3ryxkdkw12nsdh5wlph9lzqfmj2xyny2-zoom-5.6.16775.0418.drv
building '/nix/store/3ryxkdkw12nsdh5wlph9lzqfmj2xyny2-zoom-5.6.16775.0418.drv'...
unpacking sources
variable $src or $srcs should point to the source
builder for '/nix/store/3ryxkdkw12nsdh5wlph9lzqfmj2xyny2-zoom-5.6.16775.0418.drv' failed with exit code 1

The failure in 20.09 is not related to this backport. It's due to other changes made in the expression which weren't backported. With https://github.com/NixOS/nixpkgs/pull/120242 it should be fixed.


added new headers for group type. fix segue bug,

 populating all groups, create 3 headers for groups. fix segue.


Ensure wait_iter handles StopAsyncIteration properly

What was wrong?
Currently, when we run trinity and then stop it using CTRL+C we'll see three of these errors.
   ERROR  02-27 17:01:55               asyncio  Task exception was never retrieved
future: <Task finished coro=<async_generator_asend()> exception=StopAsyncIteration()>
StopAsyncIteration
    INFO  02-27 17:01:55            FullServer  Closing server...
 WARNING  02-27 17:01:55  ETHHeaderChainSyncer  Tried to cancel <trinity.protocol.eth.sync.ETHHeaderChainSyncer object at 0x7f8155e07358>, but it was already cancelled
    INFO  02-27 17:01:55         PluginManager  Shutting down PluginManager with scope <class 'trinity.extensibility.plugin_manager.SharedProcessScope'>
    INFO  02-27 17:01:55         PluginManager  Stopping plugin: Syncer Plugin
    INFO  02-27 17:01:55         PluginManager  Successfully stopped plugin: Syncer Plugin
   ERROR  02-27 17:01:55               asyncio  Task exception was never retrieved
future: <Task finished coro=<async_generator_asend()> exception=StopAsyncIteration()>
StopAsyncIteration
   ERROR  02-27 17:01:55               asyncio  Task exception was never retrieved
future: <Task finished coro=<async_generator_asend()> exception=StopAsyncIteration()>
StopAsyncIteration

These errors appeared first when we started to use wait_iter to consume the event_bus.stream(...) API. The wait_iter is needed to ensure we stop streaming when a cancel token is triggered. However, it appears there's a problem where we don't handle the StopAsyncIteration exception properly.
We can get a bit more info if we run PYTHONASYNCIODEBUG=1 trinity which will then expand the error message (of a single error of these) into this.
   ERROR  02-27 17:06:29               asyncio  Task exception was never retrieved
future: <Task finished coro=<async_generator_asend()> exception=StopAsyncIteration() created at /home/cburgdorf/Documents/hacking/ef/trinity/venv/lib/python3.6/site-packages/cancel_token/token.py:126>
source_traceback: Object created at (most recent call last):
  File "<string>", line 1, in <module>
  File "/usr/lib/python3.6/multiprocessing/spawn.py", line 105, in spawn_main
    exitcode = _main(fd)
  File "/usr/lib/python3.6/multiprocessing/spawn.py", line 118, in _main
    return self._bootstrap()
  File "/usr/lib/python3.6/multiprocessing/process.py", line 258, in _bootstrap
    self.run()
  File "/usr/lib/python3.6/multiprocessing/process.py", line 93, in run
    self._target(*self._args, **self._kwargs)
  File "/home/cburgdorf/Documents/hacking/ef/trinity/trinity/_utils/profiling.py", line 31, in inner
    return fn(*args, **kwargs)
  File "/home/cburgdorf/Documents/hacking/ef/trinity/trinity/_utils/logging.py", line 161, in inner
    return fn(*args, **inner_kwargs)
  File "/home/cburgdorf/Documents/hacking/ef/trinity/trinity/main.py", line 195, in launch_node
    loop.run_forever()
  File "/usr/lib/python3.6/asyncio/coroutines.py", line 126, in send
    return self.gen.send(value)
  File "/home/cburgdorf/Documents/hacking/ef/trinity/p2p/service.py", line 139, in _run_task_wrapper
    await awaitable
  File "/usr/lib/python3.6/asyncio/coroutines.py", line 110, in __next__
    return self.gen.send(None)
  File "/home/cburgdorf/Documents/hacking/ef/trinity/p2p/service.py", line 158, in _run_daemon_task_wrapper
    await awaitable
  File "/usr/lib/python3.6/asyncio/coroutines.py", line 110, in __next__
    return self.gen.send(None)
  File "/home/cburgdorf/Documents/hacking/ef/trinity/trinity/nodes/base.py", line 61, in handle_network_id_requests
    async for req in self.wait_iter(self.event_bus.stream(NetworkIdRequest)):
  File "/home/cburgdorf/Documents/hacking/ef/trinity/p2p/cancellable.py", line 66, in wait_iter
    timeout=timeout,
  File "/usr/lib/python3.6/asyncio/coroutines.py", line 110, in __next__
    return self.gen.send(None)
  File "/home/cburgdorf/Documents/hacking/ef/trinity/p2p/cancellable.py", line 20, in wait
    return await self.wait_first(awaitable, token=token, timeout=timeout)
  File "/usr/lib/python3.6/asyncio/coroutines.py", line 110, in __next__
    return self.gen.send(None)
  File "/home/cburgdorf/Documents/hacking/ef/trinity/p2p/cancellable.py", line 42, in wait_first
    return await token_chain.cancellable_wait(*awaitables, timeout=timeout)
  File "/usr/lib/python3.6/asyncio/coroutines.py", line 110, in __next__
    return self.gen.send(None)
  File "/home/cburgdorf/Documents/hacking/ef/trinity/venv/lib/python3.6/site-packages/cancel_token/token.py", line 126, in cancellable_wait
    futures = [asyncio.ensure_future(a, loop=self.loop) for a in awaitables + (self.wait(),)]
  File "/home/cburgdorf/Documents/hacking/ef/trinity/venv/lib/python3.6/site-packages/cancel_token/token.py", line 126, in <listcomp>
    futures = [asyncio.ensure_future(a, loop=self.loop) for a in awaitables + (self.wait(),)]
StopAsyncIteration

How was it fixed?
Let's first make it clear that I believe the following is a hack and that my main motivation to open up this PR as is, is to fire up imagination so that some :unicorn: can show me how to do it properly :sweat_smile:

Previously in wait_iter we did this:

        while True:
            try:
                yield await self.wait(
                    aiter.__anext__(),
                    token=token,
                    timeout=timeout,
                )
            except StopAsyncIteration:
                break

However, it appears that we never catch the StopAsyncIteration this way.

This change moves the __anext()__ into a helper function where we then catch the exception and trigger a special CancelToken .

The special token is then used in the while loop to decide whether it should move on or not

Cute Animal Picture

@carver I pinged you for a review here because you've written the wait_iter function. I know you are busy debugging #308 so don't feel pushed to review this any time soon. After all, it only fixes issues with unwinding Trinity which is a lower priority. Also, I'm almost certain there's a better approach how to solve it so take your time with this ;)

I expect wait_iter() to follow the same semantics as wait(), which is that it raises OperationCancelled so that nothing else in the method runs. I'm not certain that we've really nailed down the problem, either, because this test works before the PR:
@pytest.mark.asyncio
async def test_wait_iter():
    service = WaitService()
    asyncio.ensure_future(service.run())

    async def generator():
        yield 1
        yield 2
        yield 3

    try:
        async for val in service.wait_iter(generator()):
            assert val == 1
            await service.cancel()
    except OperationCancelled:
        pass
    else:
        assert False, "Service must be cancelled during iteration"

    service = WaitService()
    asyncio.ensure_future(service.run())

    vals = [val async for val in service.wait_iter(generator())]
    assert vals == [1, 2, 3]
    await service.cancel()
    assert False, "check out logs"

(I added a failure at the end, so that pytest doesn't swallow the logs, and I could look for any warnings. None show up on master).

So that covers both simple cases: service cancelled mid-iteration, and normal iteration completion. Which other case are we missing? When the token is cancelled and the exception is raised, although that also seems to be handled here:
https://github.com/ethereum/asyncio-cancel-token/blob/135395a1a396c50731c03cf570e267c47c612694/cancel_token/token.py#L145-L149
^ tangent: why isn't this doing the cool inlining code thing?

I notice that if we're not cancelled yet, and get two results, then we're not cleaning out the exceptions the way we do when we are cancelled:
https://github.com/ethereum/asyncio-cancel-token/blob/135395a1a396c50731c03cf570e267c47c612694/cancel_token/token.py#L153
We're just ignoring the other items in done. Seems like we should probably iterate those other ones and access exception(). But I'd love to see the test case that reproduces the issue on master, first. Then we can fiddle around with trying to fix it.

But I'd love to see the test case that reproduces the issue on master, first. Then we can fiddle around with trying to fix it.

Yes, I agree. It's a bit of a mystery to me why I can't come up with a test that nails it down. We clearly seem to never catch StopAsyncIteration with the current wait_iter implementation which causes all these nasty errors when Trinity shuts down but I haven't been able yet to isolate that in a clear test case.

Kept futzing around with it. I couldn't get a reproducible (isolated) test case yet and have to move on to other things. The two possibilities that come to mind are:

the service is not cancelled, and there might be two done futures, despite it being a WAIT_FIRST (recap of earlier theory
A CancelledError is raised, but somehow some of the futures got run first, and an AsyncStopIteration is in one of those futures.

Here's a test-case which reliably reproduces it:
@pytest.mark.asyncio
async def test_wait_iter():
    service = WaitService()
    fut = asyncio.ensure_future(service.run())

    await asyncio.sleep(0)  # give the service a chance to start

    # a badly-behaved async generator
    async def error_on_cancel():
        try:
            await asyncio.sleep(10)
            for i in itertools.count:
                yield i
        except asyncio.CancelledError:
            pass

    async def wait_on_iter():
        async for i in service.wait_iter(error_on_cancel()):
            print(i)

    fut = asyncio.ensure_future(wait_on_iter())
    await asyncio.sleep(0)  # give the generator a chance to start
    fut.cancel()  # raise a cancellation

    await service.cancel()
    assert False

I've used a generator here but I believe the same problem would occur for any [coroutine which raised an exception after it had been cancelled] that was passed into CancelToken.cancellable_wait.
The unclean shutdown problem was caused by a method (Endpoint.stream) in lahja which did this. I've opened a PR which gets rid of almost all the messy lines during trinity's shutdown! https://github.com/ethereum/lahja/pull/156

That's awesome! Maybe contribute that test case to the PR that eventually upgrades to a fixed lahja version. Or, alternatively, maybe a similar test case could be added to the lahja PR that fixes the issue so that it gets caught early in the lahja library.

I thought about this for a while but I couldn't think of a good thing to test for. I can certainly add a test that Endpoint.stream() doesn't throw an exception when cancelled, but it seems unlikely that problem'll be introduced again.
To make this problem easier to catch in the future:

Maybe CancelToken.cancellable_wait could do something (I'm not sure what) to notice that cancelled coros are misbehaving, and print an additional warning which makes debugging this problem easier if it happens again in the future.

We could add a lint rule. I think it's almost always wrong to catch CancelledError and not re-raise it, maybe we could add a check to our repos that required adding an # ignore: swallows-cancellation to the times where swallowing cancellation is really the behavior we want.

Yeah, I see what you mean. I like both suggestion. I'm not sure how hard it would be to write a flake8 extension that does this but I think it would be very useful :+1:

Closing this. The exceptions that this PR fixed have been long fixed meanwhile.


Docs - OutRank as a Python library

No reason not to use the library as just another ML framework within e.g., Notebooks. Required todos here:

Add documentation related to this aspect
Add a few notebooks with walk-through(s)
Additional tests that cover this functionality

Hi @SkBlaz,
I am genuinely excited about testing this out! Could you please let me know when I can have a look?
Thank you!
Marek

@mglowacki100 I appear to have missed this notification :facepalm: , example lib use was added, it's first docs page btw.


Test and validate cluster performance

TODO:

Conduct tests to ensure the new cluster and its node pools are configured correctly.
Run AI-based computational tasks to validate the performance enhancements achieved with the new setup.

Done using this example from https://learn.microsoft.com/en-us/azure/aks/gpu-cluster?tabs=add-ubuntu-gpu-node-pool#run-a-gpu-enabled-workload
apiVersion: batch/v1
kind: Job
metadata:
  labels:
    app: samples-tf-mnist-demo
  name: samples-tf-mnist-demo
spec:
  template:
    metadata:
      labels:
        app: samples-tf-mnist-demo
    spec:
      containers:
      - name: samples-tf-mnist-demo
        image: mcr.microsoft.com/azuredocs/samples-tf-mnist-demo:gpu
        args: ["--max_steps", "500"]
        imagePullPolicy: IfNotPresent
        resources:
          limits:
           nvidia.com/gpu: 1
      restartPolicy: OnFailure
      tolerations:
      - key: "sku"
        operator: "Equal"
        value: "gpu"
        effect: "NoSchedule"


Implement formatter for axaml files

There is no formatter available for axaml files at the moment

duplicate of #44


Update firefox's version from 2.1.1 to latest in addon store.

Last version is 3 years old and some engines are broken, like google's.
Also need to update to get the gold smiley working.

Submitted 2.1.4 to see if the process still works. Once we got the other bugfixes/features in will submit another version.

2.1.4 has just been approved. That was a sweet fast process :)

Updated to 2.2.0. closing


[BUG] TP worker's scheduler may block python thread

TP worker's scheduler is blocking for broadcast.
Make it async.

Also solved in #13


Foggy Island

An island located somewhere far out in the deep ocean. The location isn't mapped, as everyone who has set out to do so never returned.
Introducing Foggy Island (name TBD); an endgame location with some of the more difficult content in the mod. The Foggy Island is not visible until you enter, and escaping is difficult: thick fog clouds your vision, and you're seemingly drawn in closer and closer despite your attempts to turn back...

You hear the sound of crumbling paper and start to smell the sea.
    It's been a while since you started traveling in your boat. A strange light caught your eye off the coast, and you couldn't help but investigate. Despite the fact that the bay itself was fairly small, it had been a good 30 minutes since you had left-- much longer than it should take on a normal day.
    The fog was getting mysteriously thick.  While you had a feeling continuing onwards would be dangerous, you still sought out that pail light, which would occasionally spark in the distant fog, guiding your path.

Thump.
    A rock? Something hard brushed up against the boat, and the rain seemed to have stopped momentarily... almost as if something large was looming ahead...
        like a large, pillaring rock. Despite your almost non-existant sight, you could barely make out a large spike protruding from the crashing surface of the water. Next to it sat several other spikes of similar spikes, all reaching for the skies.
    Your thoughts of climbing up the towers, despite the rain, were cut short as a screech emanated from the sky. Through the fog, which had started to lessen up at this point, flew several large shadows. Discovering the source of the shadows was not on your to-do list, and would most likely stay off it for quite a long time.
Tsshh...
    The light, which had been dashing between the pillar's gaps for quite some time now, suddenly came to a rest in your vision, just as it had started. It took you a second to notice, but the churning of the boat in the waves suddenly stopped: as a matter of fact, the boat was stopped. Moving your hands to the side of the boat, you feel around for anything of interest. A brittle, soft texture responds back... grainy to the touch, yet packed together. Sand?
    You had hit land. You step out of the boat and rub your eyes to push the water aside; your vision gradually returns and you take a look at what you had stumbled upon.
    To say it was the king of the previous pillars was an understatement. If the stone spikes reached for the skies, this skewer reached for the stars. It wouldn't be a bad estimate to say the fog in the sky reached around 1/3 way up the peak, but you couldn't confirm without getting closer.
    An opportunity to go closer appears just as you wish for it-- the light, which had been stationary till this point, started to slowly ascend up the wall of stone. In the wake of the luminance, you can make out a small, steep path circling up the mountain.
Will you follow it?
In every slate of darkness...
       is a small pillar of light.

Meta details on entering:
    When you enter the fog of the Foggy Island Zone, you're inside a custom biome with thick fog. If you choose to continue to travel in (which ends up being around 100 blocks), your screen will start to turn gray from the fog, until you can only see a solid gray. At this point, your dimension is swapped, but the dimension changing screen is replaced with pure gray as well-- in other words, an attempt at seamless dimension transportation. This mechanic exists to allow more space in the fog; the zone in the spooky dimension is only around 200x200 big, but the zone itself is in the upper zones of 750x750. Turning backward while in the dimension results in heading back to the spooky dimension with the same mechanic. The player is lead by a glowing light in the fog, which leads to the island.
Non-narrative description:
  The Foggy Island consists of 4 parts: inner island, outer island, outer spikes, and foggy surface. You'll first enter the foggy surface, which is an area with almost no visibility and nothing but water. Sea beasts lurk in the depth: some are waiting for you to take a dip, while others are more than happy to rock your boat. Pirate ships are a great way to travel through!
Once you're close enough in, you'll start to see spikes jutting out of the water. Large shadows lurk at the base of the spikes (they are hungry), and soaring ghosts will take you out of the air if you attempt to climb up a spike to see further out.
If you make it past the spikes, you'll hit a length of open space, and then hit the beach of the island. The fog at this point is less severe than earlier, but it still prevents visibility far up and limits you to around 50 blocks of view horizontally.
To make it up the mountain, you can take one of the several paths provided up the side. Pillaring is prohibited, and flying gets you struck down by lightning. Both have warning messages associated with the action: "You start to regret pillaring up...", and "The smell of electricity fills the air... it may be best to land."
I don't have any concrete ideas as to what is at the top (or what the light is) just yet. I just want a cool area with fog and fun, seamless, instanced dimensional teleportation! Maybe the light could be the old ruler of the spooky world (flashback time ???) and the boss could be a giant stone-spike golem who climbs around the main mountain... :)

I reckon foggy island could be done via having a rare deep ocean variant of the sea biome group, which has an edge layer that replaces surrounding biome groups with the sea biome group, making it surrounded much by sea. This would only generate 6 or more large-biome-fractal-tiles out (manhattan distance)

On around Thursday I’ll start working on that if no one else has already

Foggy Island will be it’s own dimension, as mentioned in the original issue.

Yes, the actual island would be a separate dimension. What we do need is a way to calculate how far from the center the player is to scale fog amount (center = max fog); in other words, it should basically be a circle biome with no different characteristics from the biomes around it (ignoring fog).


QUnit is not changing the 'config.current' to the next test

Ok, sorry for creating a new issue, looks like I cant reopen the last one.
The 2nd to last test is not running the following code around line 200
queue: function() {
    var test = this;
    synchronize(function() {
        test.init();
    });
    function run() {
        // each of these can by async
        synchronize(function() {
            test.setup();
        });
        synchronize(function() {
            test.run();
        });
        synchronize(function() {
            test.teardown();
        });
        synchronize(function() {
            test.finish();
        });
    }

test.setup() is called, followed by test.finish().  test.run() is not called.
Then on the following test, it is called twice.
It seems as if some of the synchronization has got mixed up and looks like this
Queue test 1
Queue test 2
Queue test 3
... start testing
test1.setup
test1.run
test1.finish
test2.setup
test2.finish
test3.setup
test2.run
test3.run
test3.finish
But because test 2 is finished before it runs, no results are displayed.

Fixed by #148


Don't like the extensions category to be displayed if there are no extension methods

It's adding visual clutter - first on the list and an eye-catching color - when I have a class that I don't need or want to expect every to use extension methods.  I have some classes that have no instance methods and yet there is a category.

My preference is to leave extensions in regardless if there are extensions. Pharo adds and removes computed categories as you suggest but I find them confusing. I think the heart of my preference is that I want to always know exactly where to look to find the first actual category in my class. If the first category is bouncing around, I find it distracting.

Well, my feeling is that if the extensions category is empty the only way I'll know it is empty  is if I click on it, so my pref would be to not have it present if there are no extensions ... it hasn't bothered me up til now, because I "know it is always empty" ... although I don't think I've tested that theory :)

Showing the extensions category is providing incorrect information to the user.
I get that it may make a developer's work a little more onerous to understand how pharo is constructing categories on the fly... but product features should prioritize users rather than developers...

It's a valid complaint that showing a computed 'extensions' category when no extensions are in the class is misleading. My complaint is that the first true category shifts positions if you don't display the computed category all the time.  This makes it more difficult to find the category you want.
To show what I mean, I attached some pictures of what Pharo does. Pharo uses many computed categories and they only show a computed category if there are methods (as you recommend). But, notice how the first true category (accessing) goes from 6th to 5th to 2nd in the category list? Looking for a category alphabetically becomes more difficult. Opening a Pharo browser and selecting different classes may be the best way to get a feel for my argument.
What if I put the computed category (and any future computed categories) at the bottom of the category list?

Bottom of the list works for me.  extension methods are sort of bonus.

This looks good.


input[autocomplete] (values besides on/off)

autocomplete attribute (values besides on/off)
http://www.whatwg.org/specs/web-apps/current-work/multipage/association-of-controls-and-forms.html#autofilling-form-controls:-the-autocomplete-attribute

This issue was imported from Google Moderator
Moderator votes: +6
Issue added by thermistor on 2012-08-28

Duplicate of #976 so moving half the votes there.

Removing duplicate label on this and re-purposing it for the non on/off values of autocomplete

+1

+1 cc-name, cc-number, for example

+1

+1

+1

+1
also see

https://html.spec.whatwg.org/multipage/forms.html#enabling-client-side-automatic-filling-of-form-controls
http://blog.cloudfour.com/autofill-what-web-devs-should-know-but-dont/

+1

+1

+1

+1

+1

This should perhaps be renamed to include the term autofill, e.g. “autofill field names”, see HTML. I think the shipping/billing distinction should be covered separately.
These are currently covered: one-time-code #4914, webauthn, new-password.
Also, more general: global attribute, form.


use ffmpeg for detect-crop instead of mplayer

mplayer is quite a big dependency. If it's used only for crop detection, would it be possible to replace it by ffmpeg?
https://stackoverflow.com/questions/17265381/ffmpeg-get-value-from-cropdetect

@legrostdg I have recently considered using ffmpeg for crop detection. And my experiments show it would, with a little effort, actually do the job. But...
How do you then preview the crop? I'm afraid you're stuck with mplayer for that.
Now, you might suggest ffplayfor previewing. But most distributions of ffmpeg no longer include that tool. And, truth be told, it doesn't work well anyway.
A better idea might be using mpv for preview and, possibly, detection too since it includes the "libav" routines required for that. But that would mean complicated scripts written in Lua that don't exactly fit on the command line.
So, I'm afraid we're stuck with mplayer. :(
I'm closing this now but feel free to continue commenting. Especially if you figure out a way to solve these problems. Heck, I'll re-open the issue and get to coding it.

@legrostdg Seriously, I'm really worried about depending on mplayer for the long term since it appears the whole project might be moribund.
If you have experience with Lua and can figure out how to leverage mpv for this then I would love to collaborate on the effort.

https://github.com/mpv-player/mpv/wiki/User-Scripts mentions https://github.com/mpv-player/mpv/blob/master/TOOLS/lua/autocrop.lua.
Can't you just get the dimensions with ffmpeg and use mpv with these dimensions? Why would you need to have one command calculating the crop and playing a preview?

mpv --vf=crop[=w:h:x:y]

@legrostdg Yes, I've perused that Lua script many times in the last few weeks. :)
You're correct that the same tool isn't required to detect the crop. But using two different tools would mean that crop-detectitself  would have yet another dependency.
You're also correct that using --vf=crop with mpv would display the cropped video. But how do you show the bordered version? There's no equivalent --vf=rectangle filter. And I don't want to lose that feature since I use it all the time.

I'm sure you can draw a rectangle with ffmpeg, and then play with whatever you want.
https://ffmpeg.org/ffmpeg-filters.html#drawbox

@legrostdg How could I draw a rectangle with ffmpeg when it's not the player? I would have to transcode the whole video for that.
The problem here is that mpv doesn't have the equivalent filter. At least, none that I can find so far.

@legrostdg OK, I did some more digging. It seems that mpv allows access to the drawbox  filter through its -vf lavfi option. I'm playing with it now.
So, I'll re-open this for consideration.

@legrostdg Here are preview commands for a typical video using mplayer :
mplayer -really-quiet -nosound -vf rectangle=1920:800:0:140 Movie.mkv
mplayer -really-quiet -nosound -vf crop=1920:800:0:140 Movie.mkv

...and the same video using mpv:
mpv --no-audio --vf lavfi=[drawbox=0:140:1920:800:invert:1] Movie.mkv
mpv --no-audio --vf crop=1920:800:0:140  Movie.mkv

As you can see, the drawbox coordinates are flipped for mpv. But everything works the same.

@legrostdg I'm playing with ffmpeg now to remind myself of how it works with the cropdetect filter. It's very similar to mplayer, which is not surprising since they use essentially the same code. :)
So, I can switch over from using mplayer for crop detection to using ffmpeg as you suggest. The hard part will be 1) parsing the different output, 2) testing it to make sure nothing breaks and 3) making sure it doesn't return radically different results.
But before I do any of that I want to write a proposal detailing all the changes required and ask for feedback. Because this means an added, possibly optional, dependency on mpv for previewing the crop results. And people may not actually want that if the system they have already works.
Plus, I need @samhutchins and @JMoVS to weigh in for what this means for the Windows platform since they're the experts there.
I'll probably open a new issue to cover all theses changes and reference your issue here, leaving it open as well.
 And let me know what you think.

@legrostdg BTW, I could probably figure out a way to use mpv now for crop detection but it appears to be much easier to implement with ffmpeg, as you suspected. :)

@legrostdg Uh oh. Houston, we have a problem. :(
It appears that ffmpeg may not work after all. That's because it won't actually seek to a specific offset in the input file using its -ss option without scanning through the whole file up until that point. Since my crop detection algorithm for mplayer skips through the file to sample it, much like HandBrake does itself, this would be performance disaster to implement.

Maybe using ffplay is not so bad after all? On debian, it is installed with ffmpeg.

or you can use ffmpeg -t

@donmelton Easy enough to install on Windows, same as MPlayer really: download a nightly build and drop it in a folder in $PATH. Like all these projects they link out to 3rd party builders for Windows versions.
Doubt I'll have time to try the Linux Subsystem thing until next week, but maybe @JMoVS will be able to try sooner.
It's possible that mpv will be less finicky than MPlayer on Windows, if you recall I has some issues with MPlayer that I couldn't nail down the source of. The UI for mpv is much nicer too

@legrostdg Unfortunately ffplay isn't included with the Homebrew-based installation, which is what the majority of folks use.
And, the -t option only sets the duration, not the offset within the input file. So that won't work either. :(

@samhutchins Cool. Well, since I've hit a snag with using ffmpeg to do the crop detection part, this is going to take awhile anyway.

Sure, -t sets the duration, but you can combine it with -ss to get a offset. -t 5 -ss 10 to get a 5s extract starting at 10s. If that's what you were asking for...
Can't ffplay be added to the homebrew formula of ffmpeg?

@legrostdg Yes, but the problem is -ss itself. It has to very slowly scan through the whole file to get to the offset. That just won't ever be performant.
Yes, I believe ffplay can be added to the Homebrew install of ffmpeg. But it's non-trivial for most users. And it's slow to add it because it requires a complete re-compile of ffmpeg. And that last time I required that users hated it.
But there's another reason to avoid ffplay. It's not included by default because it's almost as moribund of a project as mplayer itself.

OK, I did not get the -ss problem. Is that what -noaccurate_seek is for?
 :) I was stupidly placing the -ss option after the -i option. It has to come before the input file to work correctly. I forgot that ffmpeg is mind-numbingly anal-retentive about the order of options and input files.
So, we're back on! I can make this work. I think. :)

The -noaccurate_seek option is actually the default behavior so, unfortunately, that doesn't speed anything up.

On debian at least the default is -accurate_seek (according to the manpage):
   -ss position (input/output)
       When used as an input option (before "-i"), seeks in this input file to position. Note that in most formats it is
       not possible to seek exactly, so ffmpeg will seek to the closest seek point before position.  When transcoding
       and -accurate_seek is enabled (the default), this extra segment between the seek point and position will be
       decoded and discarded. When doing stream copy or when -noaccurate_seek is used, it will be preserved.

@legrostdg I was going by the built-in help which seems to imply the opposite. But it doesn't matter since I don't need to use it now.

@legrostdg OK, I've got a version of detect-crop using ffmpeg instead of mplayer now. In fact, the code worked correctly the first time I tried it. :)
The good news is that ffmpeg appears to be faster than mplayer even without using the -noaccurate_seek option.
The bad news is that's getting slightly different results in some cases.
This will take much more testing but I think I'm on the right track.

@legrostdg Believe it or not using the -noaccurate_seek option with ffmpeg gets results much closer to those from mplayer and it's even faster. :)

@legrostdg It seems that for some media files, ffmpeg is actually slower than mplayer for crop detection. It's rare but it happens. And I have no idea why. Yet.

In the end, what command do you use? If mplayer only use ffmpeg, another solution would be to look directly into mplayer's code to find out what options are used.

@legrostdg I'm using the same parameters for both. I suspect it's just the difference in the version of the underlying libraries. Which also explains the few times when the actual crop detection results have been different. And, so far, those few differences may be a good thing because they seem to be more accurate now with ffmpeg.

@legrostdg Thanks again for filing this! The change is in. Just gem update video_transcoding to get version 0.17.0.


Allow free-form queries within FastAPI

First check

[x] I added a very descriptive title to this issue.
[x] I used the GitHub search to find a similar issue and didn't find it.
[x] I searched the FastAPI documentation, with the integrated search.
[x] I already searched in Google "How to X in FastAPI" and didn't find any information.
[x] I already read and followed all the tutorial in the docs and didn't find an answer.
[x] I already checked if it is not related to FastAPI but to Pydantic.
[x] I already checked if it is not related to FastAPI but to Swagger UI.
[x] I already checked if it is not related to FastAPI but to ReDoc.
[x] After submitting this, I commit to:

Read open issues with questions until I find 2 issues where I can help someone and add a comment to help there.
Or, I already hit the "watch" button in this repository to receive notifications and I commit to help at least 2 people that ask questions in the future.
Implement a Pull Request for a confirmed bug.

Description
There is a notion of "free-form query parameters" that allows a user to accept multiple non-predefined query params:

This is in fact can be described by Open-API 3.0:
https://stackoverflow.com/questions/49582559/how-to-document-dynamic-query-parameter-names-in-openapi-swagger
Unfortunately, as of now you cannot define "free-form query parameters" within FastAPI.
Example
This is how it would look like:
from fastapi import FastAPI

app = FastAPI()

@app.get("/")
def read_root(arguments: Dict[str, str] = Query({})):
    ...

But unfortunately, this raises an exception:
AssertionError: Param: arguments can only be a request body, using Body(...)

While at it, I hacked FastAPI a bit, and managed to make it render docs page with the valid entries:

By modifying: sequence_shapes set:
from fastapi.dependencies.utils import sequence_shapes
from pydantic.fields import SHAPE_MAPPING

sequence_shapes.add(SHAPE_MAPPING)

I understand that it is not how it should be done, I just wanted to verify that it would generate a valid openapi.json.
Also not surprisingly, arguments var would evaluate to an empty dict {}.
Describe alternatives you've considered
Currently, I am using the following workaround:
from pydantic.types import Json
from fastapi import FastAPI

app = FastAPI()

@app.get("/")
def read_root(arguments: Json = Query({})):
    ...

That allows me to pass multiple query parameters that are only assigned to arguments Json|Dict object. However, all params needs to be encoded inside ?arguments=<params> which is undesirable.
Environment

OS: macOS:Darwin Kernel Version 19.5.0

FastAPI Version: 0.55.1

Python version: 3.7.7

Additional context
I am willing to prepare a PR if provided with some pointers :)

@chrisngyn and @YKo20010 will be working on this!

Awesome! I can contribute too, if you need any help :)

@yeralin
Hey Daniyar, @chrisngyn and I are wrapping up some of our other open issues before our fellowship ends, so feel free to take this one on if you'd like!
This is the contributions page to help you get started: https://fastapi.tiangolo.com/contributing/
And here's what our maintainer @tiangolo had in mind, so it may take a bit of experimenting:

Created a PR with an initial idea on how this feature would look like:
https://github.com/tiangolo/fastapi/pull/1885
@YKo20010 @chrisngyn @tiangolo


Readme contains links to non-existing pages

When clicking in the mainpage in the README.md links to the HelloWorld(s)  example configurations, you get a page not found error.

fixed in readme.md and pulled :+1:


Enable title in original language (alongside EN)

Currently, the title of the resource needs to be in English. However, we feel that it should be possible to also add original name as dictionaries are often known by the name in the original language.
E.g. to the title 'Karelian Dictionary', 'Karjalan lielen sanakirja' would be added.

The complexity of that depends on what exactly you need to achieve... In theory the metadata registry has a field dc.title.alternative with the following semantics

Varying (or substitute) form of title proper appearing in item, e.g. abbreviation or translation

Which kind of sounds like something you could use*. Though, I guess, the "title proper" is the non English string and 'Karelian Dictionary' is actually the translation.
*You can add it now via edit item (or via other processes); that would probably affect search results (ie. there'd be hits for 'Karjalan lielen sanakirja') but it wouldn't be displayed anywhere. One of the places were it'd make sense is probably the landing page of an item, that can be changed by modifying the item-view.xsl.
Several other things would need changing if you also want to export the alternative in all oai-pmh formats.
If you are exposing the submission workflow to users; the extra field can be added there as well; you just need to take care describing what the title proper is and what the alternative is.
In edit item you can also specify a language of metadata value, so it might actually be possible to add both into dc.title (and specify different languages). But there might be expectations there's only one title for an item, so I'd be really careful with trying that...


Update net-standard-table.md add missing dot

Add missing dot for 4.61
Title
On the title describe
what you've fixed (or created) with this Pull Request (PR).
Summary
Insert a short (one or two sentence) summary here.
Fixes #Issue_Number

Note: The "Fixes #nnn" syntax in the PR description causes
GitHub to automatically close the issue when this PR is merged.
Remove that line if you don't have issues associated with this
PR. Click on the Guidelines for Contributing link above for details.

Details
Explain your changes, and why you made them. If that
information is already available in the issue referenced
above, just referencing the issue is preferred to copying
the text.
This may not be necessary depending on the scope of the PR
changes. For example, "fix typo in introduction.md" is
sufficient to describe that PR.
Suggested Reviewers
If you know who should review this, use '@' to request a review.

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. We will now review your pull request.
Thanks,
.NET Foundation Pull Request Bot

@LRPalacios Thanks for doing that and thanks for putting the fix in. We'll get it merged as soon as the build completes.

LGTM


Multiple popups open when browser icon clicked multiple times very quickly.

uProxy assumes no popup is open if popupWindowId is not set. However, if the user clicks the browser icon very quickly, they can launch multiple popups in the short time between when the first popup launches and when its popup ID is saved to popupWindowId.
Reasonable fix seems to limit the browser icon onclick function to running at most once a second.

I expect we can come up with a more deterministic solution if we put our
minds to it.
On Thu, Feb 12, 2015 at 5:01 PM, lucyhe<EMAIL_ADDRESS>wrote:

uProxy assumes no popup is open if popupWindowId is not set. However, if
the user clicks the browser icon very quickly, they can launch multiple
popups in the short time between when the first popup launches and when its
popup ID is saved to popupWindowId.
Reasonable fix seems to limit the browser icon onclick function to running
at most once a second.
[image: screen shot 2015-02-12 at 3 38 02 pm]
https://cloud.githubusercontent.com/assets/8723127/6177909/4da163be-b2d8-11e4-945e-7a0e578539b4.png
—
Reply to this email directly or view it on GitHub
https://github.com/uProxy/uproxy/issues/907.

Fixed in #915


ShaderValidation: may has incorrect check for read only buffers

Hi,
we are getting this error:

Error: (objectType=0, object=0x0, location=0, errorCode=15) Validation: Object: VK_NULL_HANDLE (Type = 0) | Shader requires VkPhysicalDeviceFeatures::vertexPipelineStoresAndAtomics but is not enabled on the device

Our baseline is DX11 HLSL 5 - it has only support for UAV resources in pixel and compute shaders. We translate the HLSL into GLSL and let glslang do the transformation to Spir-V. We validated the GLSL and it only correctly emits storage objects as readonly for vertex shaders.
So we where surprised to see this error.
Here is an example:
spir-v dissaembly
source glsl
The resource binding slots/sets are different as they are rearranged in the glslang ioremap phase to compact the descriptor sets.

Closing as duplicate of #2526.

@mark-lunarg I've got a plan for fixing this now, but have my hands full with another project. How urgent is fixing this?


feat: add setup script

Add an interactive setup bash script that will:

clone the repo
do some initial configuration related to sparse checkout (including defining a git alias to reuse the --filter=blob:none
Unfortunately, from what I've read, even if sparse-checkout can avoid tracking files in the working dir, it won't prevent fetching everything remotely when one use git fetch or git pull (which defeats what we wanted: avoid downloading too much stuff)
ask what to add/remove from sparse checkout

Later the same script can be run again (I wrapped it in an npm script for convenience) to skip the initial cloning and just ask to add or remove packages from sparse checkout.
Closes #21
Test plan:

in an already cloned repo:

checkout this branch
npm setup: should ask to add or remove package
press a or r
next you are asked to choose a package
press e, p or s
verify that the package was checked out or removed in your working dir

test the initial cloning and setup:

Delete your existing repo

bash <(curl https://raw.githubusercontent.com/privacy-scaling-explorations/snark-artifacts/setup/scripts/bin/setup) fetch setup

Follow the prompts. Check that what you wanted was checked out.

Comments
This became a bit complicated.
Was a fun exercise to learn a lot about git and bash. sparse-checkout is still a bit of an obscure option.
Not a perfect script. But I think we should not spend too much further time on this...Not sure the dx benefits are worth it.

@cedoor I pushed a fix
Can you try to test again?
https://github.com/privacy-scaling-explorations/snark-artifacts/pull/22/commits/53a30cc6d795c6683ec75bf7c70735357f7a7762


Add files via upload

I HAD UPLOADAED SOURCE FILE AND ANGULAR  CLI VERSION 17.3.4 AND NODE: 20.12.2

NO COMMENT


More helpful message on missing field.

Closes #588.
Honestly, I am unfamiliar with internal of circe and how to use cats.
The changes are mix of suggested changes in https://github.com/circe/circe/issues/588#issue-214064936 and https://github.com/circe/circe/issues/588#issuecomment-286423496.
I believe addressing the long-unadressed issue improves developer experience of circe, so opened up this PR.
I am happy to update PRs based on feedbacks and guidance.

Codecov Report

Merging #1081 into master will decrease coverage by 0.14%.
The diff coverage is 90.9%.

@@            Coverage Diff             @@
##           master    #1081      +/-   ##
==========================================
- Coverage   84.22%   84.08%   -0.15%
==========================================
  Files          76       76
  Lines        2435     2444       +9
  Branches      184      182       -2
==========================================
+ Hits         2051     2055       +4
- Misses        384      389       +5

Impacted Files
Coverage Δ

...es/core/shared/src/main/scala/io/circe/Error.scala
62.5% <ø> (ø)
:arrow_up:

.../core/shared/src/main/scala/io/circe/Decoder.scala
90.48% <90.9%> (-0.05%)
:arrow_down:

...e/generic/extras/decoding/EnumerationDecoder.scala
88.88% <0%> (-11.12%)
:arrow_down:

...re/shared/src/main/scala/io/circe/JsonNumber.scala
91.25% <0%> (-1.25%)
:arrow_down:

...rc/main/scala/io/circe/numbers/BiggerDecimal.scala
88.55% <0%> (-1.21%)
:arrow_down:

Continue to review full report at Codecov.

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

@exoego based on this code, I think you would benefit from show on errors:
@ import cats.implicits._
@ import io.circe.parser._
@ import io.circe.generic.auto._

@ case class A(x: Int, y: String)

@ case class B(a: A, z: Int)

@ decode[A]("""{"x":1}""").left.get.show
res10: String = "DecodingFailure at .y: Attempt to decode value on failed cursor"

@ decode[B]("""{ "z" : 1 }""").left.get.show
res15: String = "DecodingFailure at .a: Attempt to decode value on failed cursor"

@ decode[B]("""{ "z" : 1, "a": { "x": 1 } }""").left.get.show
res16: String = "DecodingFailure at .a.y: Attempt to decode value on failed cursor"

@tkroman
Let me confirm your intent.
Do you mean: this PR should modify show instead of tryDecode ?

I rather meant that this functionality is already covered by Show instances on errors, so maybe you just want to use that.

this functionality is already covered by Show instances on errors

We could argue that is is covered.
But the point of  the issue #588 is improving error message.
Current error message DecodingFailure at .x: Attempt to decode value on failed cursor tell that just something went wrong.
It is better to decipher such message into more user-friendly message like Field x is missing.

Could I get review on this?

Closing this since no interests in this PR.

Reopened since #588 is still open for 2 months.

Sorry for the extremely long delay on review here. I don't think this will make it into 0.12.0, but I'm going to have more time for circe maintenance over the next few weeks, and this will be the basis of a reworking of errors for 0.13.0.

@exoego thanks the PR. There's this other one https://github.com/circe/circe/pull/1617 which introduce typed errors (including missing field). If you can take a quick look and see if that addresses everything you need then that'll be good :)

Closing in favor of #1613


Getter will not execute when the schema defined ref option

For example: (without ref)
  UserSchema = new mongoose.Schema({
    name: {
      type: String,
      get: function(val) {
        console.log('execute getter');
        return val;
      }
    }
  });
  UserModel = mongoose.model("User", UserSchema);
  user = new UserModel;
  user.name;  // dump "execute getter"

And (without ref):
  UserSchema = new mongoose.Schema({
    name: {
      type: String,
      ref: "Someone",   // add ref
      get: function(val) {
        console.log('execute getter');
        return val;
      }
    }
  });
  UserModel = mongoose.model("User", UserSchema);
  user = new UserModel;
  user.name;  // dump nothing

mongoose version: 3.8.x (3.8.21)

This is some old code that's been around since 2011 (see #568) that no longer seems to be necessary. Just in case, I'm gonna put this into 4.0 - as far as I can tell this shouldn't be backwards breaking, but somebody might be depending on this behavior.


Bring in rotatable crosshairs.

RE: #2098
Bring in recent crosshair updates from react-vtkjs-viewport.

Hi, amazing feature !
I wonder if the orientation isn't inverted in the preview,
see the screen capture, in the axial view I got the costal axis witch is oriented foward and down.
But the red line that should symbolize by axial view in the saggital view is oriented foward and up

Ahh, good catch, I think you are right.

I've moved the react-vtkjs-viewport to a brainscan which makes this much more obvious.
The issue was actually just a trivial error due to SVG and the webgl coordinates being inverted with respect to each other, I've fixed it locally, I'll ping you when its up if you want to have another look @salimkanoun  :)

thx @JamesAPetts , I will give a look, that's a very important feature as the MPR wasn't really usable without these crosshairs (you get often lost without crosshairs)

Should be up now after netlify rebuilds (or you can pull locally and check).

Great ! Much better.
One question, the cross hair seems to be relative to the image, when you zoom In / Out you have the interaction dot moving out the field of view, and possible land on the center of the screen (which is disturbing).
Did you considered fixing the interation dot at a fix % of the viewport axis (ex 25 % - 75%) this way the dots will stay accessible no matter of the applied zoom and will never cover the center of the image ?

Good points, for now we need to merge this, but feel free to make a follow up issue with feedback.


Corrupt Mac JDK Mission Control?

Browser: Google Chrome is up to date
Version 78.0.3904.70 (Official Build) (64-bit)

I have the latest MacOS (macOS Catalina Version 10.15).
I downloaded JDK Mission Control (org.openjdk.jmc-macosx.cocoa.x86_64.tar.gz) from your download page (https://adoptopenjdk.net/jmc.html).
After expanding the gz (through double click in Finder), I attempt to launch the app (JDK Mission Control.app) and I get the following popup message:
"JDK Mission Control.app" is damaged and can't be opened. You should move it to the Trash.
The only options given are cancel and "Move to Trash". I even tried right clicking and selecting "Open" while holding Alt key in case this was actually a security block imposed by Catalina but I got the same message.
Thanks for any help on this.
Carlos

Hm. It works when running JDK\ Mission\ Control.app/Contents/MacOS/jmc

Starting a locally built JMC app I just compiled by double clicking the app does work.

Sorry @thegreystone , this is probably a dumb question, but can I assume you were able to confirm/replicate my issue (when using the downloaded gz of the app) and are now trying investigate/correct it?

Yes, I can confirm that I can reproduce the issue.
It is not related to Catalina - I can reproduce this trying to open an Adopt OpenJDK built JMC on Mojave.
I can not reproduce this on a locally built JMC. For me, building and running on my machine by simply clicking the built app works.
Funnily enough, the Adopt OpenJDK built JMC seems to work when launched from the command line, as I described above. I.e. running JDK\ Mission\ Control.app/Contents/MacOS/jmc from the command line.

Good to hear It’s not just me. ...
Actually as I was writing this I found the issue. The problem seems to be with .gz (or .tar.gz) files and the mac built in unarchive utility that expands the file on double click. It apparently changes/corrupts the files in some way.
When I expand the file on the command line with:
gunzip -c org.openjdk.jmc-macosx.cocoa.x86_64.tar.gz |  tar xopf -
The app runs fine. I can't recall ever seeing a .gz file to deliver apps and I wondered about that. I mostly see .zip and especially .dmg.
Definitely this is Apple causing the issue so I'm not blaming you guys.
Anyway here is more evidence of this problem (see the comments at the very end of page):
https://bugs.eclipse.org/bugs/show_bug.cgi?id=398450

https://bugs.openjdk.java.net/browse/JMC-6131

gunzip -c org.openjdk.jmc-macosx.cocoa.x86_64.tar.gz | tar xopf -

I can confirm this works!

Funnily, it doesn't seem to be a problem for Zulu Mission Control for some reason. Liberica Mission Control deliver a zip for Mac OS X, so I am thinking perhaps they have the same problem, and simply do the gunzip dance, and then re-zip the contents. Perhaps we should do the same.

@reinhapa what do you think? Do the gunzip thing and re-zip?

The problem is caused by the Mac's quarantine attribute set to unsigned artifacts as the following command executed within a extracted JDK Mission Control.app folder reveals:
ls -l@  ~/Downloads/org.openjdk.jmc-macosx.cocoa.x86_64.tar.gz
-rw-r--r--@ 1 pr  staff  66955612  5 Nov 15:35 /Users/pr/Downloads/org.openjdk.jmc-macosx.cocoa.x86_64.tar.gz
	com.apple.lastuseddate#PS	      16
	com.apple.metadata:kMDItemDownloadedDate	      53
	com.apple.metadata:kMDItemWhereFroms	     186
	com.apple.quarantine	      57

And therefore after untar:
~/Downloads/JDK Mission Control.app  ls -l@ .                                                                                 ✓  10210  16:49:41
total 0
drwxr-xr-x@ 6 pr  staff  192  4 Nov 14:21 Contents
	com.apple.quarantine	 21

This flag can be removed by issuing the following command within the base directory of the extracted application:
sudo xattr -r -d com.apple.quarantine JDK\ Mission\ Control.app

Excellent findings! So, the options then seem to be for Adopt to either sign the builds, or to do the gunzip dance, and instead zip the thing and release the zips.

A more simper "dance" is to isolate those special attributes from the tar process ty unpacking like so:
cat org.openjdk.jmc-macosx.cocoa.x86_64.tar.gz |tar xv -

This has the same effect, as by this method tar is receiving a byte stream, that has no notion of special file attributes.
You could also install it using curllike so:
curl https://ci.adoptopenjdk.net/view/JMC/job/jmc-latest/lastSuccessfulBuild/artifact/target/products/org.openjdk.jmc-linux.gtk.x86_64.tar.gz | tar xf -

It would be great if it just worked for the end user when double-clicking on the compressed archive though.

On has to sign and notarize every executable, otherwise there are going to be errors and silent failures galore on Catalina.

Ah. Signing would be preferred then.

IIRC @klaraward was involved in much of the work to sign the Oracle JMC builds. Of course, every signing service is different, and I am not sure how Adopt does this. That said, I believe we signed a few different things:

The executable
The individual eclipse/p2 bundles
The archives

Klara, can you confirm?

As much as i understood so far this notarize step we need to create a .pkg for that and the notarization only works with Xcode using a Mac environment...

I'll update the website as a stop gap measure, by adding special mac unpacking instructions as proposed by @reinhapa:
cat org.openjdk.jmc-macosx.cocoa.x86_64.tar.gz |tar xv -

Judging from what it looks like for JMC 6.0.0 on Mac (and what seems to match my memory), I believe we signed:

The features and plugins jar for the update sites, verified with jarsigner
The executable, verified withspctl
The Mac app, verified with codesign

We did not sign the jars in the RCP app, and not the updatesite archives themselves.


bore over https

How can I run bore to support https request?
It seems to work only over http.

See #66


Disk panel form consistency

Begins to address issue defined in #806, by starting with the DiskPanel form
Form elements were added where missing to get appropriate submit behavior for both buttons and inputs.
Regarding addition of button types, see implicit-submission notes here: https://html.spec.whatwg.org/multipage/forms.html#implicit-submission

+1 to the standardized form and submit/cancel buttons

Coverage increased (+1.2%) to 85.005% when pulling bb0c8aa035caaed4ddb640fcfba0f1c699c7b06c on mparke:disk-panel-form-consistency into b5e6548330f84470a71ff50d1c294745333a6aa2 on linode:master.

I like the button components but I don't really see what the Form component is getting us because there is basically nothing unique to us in there. I also don't think there particularly will be.

Re: the form component:

for starters we're missing form elements where they should exist, where adding them makes it semantically correct
for enter-to-submit inputs, this is gained as a default behavior when inputs are inside a form element
creating a component makes it so we can handle the default submit behavior ( preventing page submit since this is single page ) without having to redefine it


⚠ API - Lens has degraded performance

In 7908d82, API - Lens ($LENS_API_URL) experienced degraded performance:

HTTP code: 503
Response time: 337 ms

Resolved: API - Lens performance has improved in 5031505 after 6 minutes.


[Task ISSUE-7] Upgrade GivWenZen to support latest versions of Fitnesse

This commit features an upgrade to GivWenZen that
enables it to work with the latest versions of Fitnesse.

Version bumped to 2.0.0
PropertyEditorParser class is updated with appropriate implementation
All dependencies were updated to their latest versions (where possible)
Added Fitnesse tests for Hash Table parameter support

Fixes #7 .

Github's "File Filter" could help to filter out the FitNesseRoot changes.

Any chance for this to get reviewed?

Yes, apologies, this is crunch time where I work at the moment, preparing
for holiday shopping. I'll get this done in the next few days.
On Tue, Nov 12, 2019, 12:30 AM Veselin Stoyanov<EMAIL_ADDRESS>wrote:

Any chance for this to get reviewed?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/weswilliams/GivWenZen/pull/8?email_source=notifications&email_token=AABVJ7K5W2ZKM7QMTHT4CYDQTJSRXA5CNFSM4HWJPDP2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEDZOA4I#issuecomment-552788081,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABVJ7LPSD76FZZAMKAVMY3QTJSRXANCNFSM4HWJPDPQ
.


Change connectionconfig's children could be in random order

Change connectionconfig's children could be in random order.

LGTM, thanks for updating the Changelog!


[vault-secrets-webhook] Provide the vault-tls-secret certificate as an env variable

Is your feature request related to a problem? Please describe.
I occasionally forget to copy the internal CA certificate used by the Vault cluster to the target namespace. Consequently, when I deploy a Pod in that namespace, during mutation the vault-secrets-webhook attempts to connect to the Vault cluster, but fails to perform TLS verification due to the missing/unknown certificate.
Describe the solution you'd like
Ideally, the Pod mutated by vault-secrets-webhook should look for the vault.security.banzaicloud.io/vault-tls-secret Secret in the namespace where the webhook is deployed (not in the target namespace of the Pod that gets mutated). Due to the way how it is designed, this is impossible.
The cleanest way would probably be to have an option to provide the CA certificate as an env variable. During Pod mutation the CA certificate would be inserted as an env variable in the target Pod. Afterwards the injected initContainer that makes everything work, could also copy the contents of this env variable into a file and pass it to the vault-env container.
(Or, vault-env and vault-agent could support reading the certificates from env variables directly.)

This is also a problem whenever the operator refresh the CA certificate, which seems to happen once a year.


Bind Loader ?

Hello,
Very good project. Thank you :)
Is it possible to generate a Bind Powershell Loader (One-liner) with Empire? (and not a Reverse Loader)
In some case, a firewall can be between the target and the auditor with connection initializations from the target to the auditor's machine blocked.
I have not found this Bind feature in your project.
Thank you in advance,

Based on the async http[s] get/post methods that Empire uses, there's no way to build bind type communications into the architecture at this point. Even if we built a bind loader for the initial agent, communications could be over http[s] methods similar to the staging component.


[9.x] Adds Route::environment 🐝

This pull request is a work in progress, and it proposes the addition of a minimal environment method to the route definition that allows the creation routes for certain environments only. In other words, sometimes, we may have those "test" routes that we want to use locally — or in staging — but not in production:
Route::get('/playground', function () {
    // My test code...
})->environment('local');

Route::get('/playground', function () {
    // My test code...
})->environment(['local', 'staging']);

Of course, when trying to visit these routes from production the response back will be an 404.

Wouldn't it be better to not register those routes on unwanted environments in the first place, instead of always registering them but filtering them out later on?

I have been able to do such a feature and the team did not accept its integration. I don't know why, but it is very important in the coming period for developers so that they do not create links to the experience and forget it. #42723

I'm wondering if the feature could be...
Route::environmentGroup('local', function () {
    //
});

which would just be a shortcut for...
if ($this->container->environment($environments)) {
    return Route::group($closure);
}

return new Fluent; // nop

Then we just don't execute the closure and there isn't a performance penalty for de-serializing etc.
A single route would still be easily registered...
Route::environmentGroup('local', fn () => Route::get('playground', function () {
    // ..
});

I am up to it. Nice addition. 😀

What would artisan route:cache do with regard to this PR, when executed in a local environment ?
APP_NAME="Laravel Project"
APP_DEBUG=true
APP_ENV=local
APP_URL=http://localhost:6001

I build the route cache on my own development machine (with local environment). And then deploy the bootstrap/cache/routes-v7.php to production. Because I have no ssh access to the production site, which is on shared hosting.

What about a local.php routes file instead?

Wouldn't it be better to not register those routes on unwanted environments in the first place, instead of always registering them but filtering them out later on?

With you on this. is better IMO to just register a separate routes file in local if you only need it for local

I think filtering out routes by using the middleware is fine during local development. But I think the route:cache command should be updated, too, so it doesn't include any routes that were registered for a different environment. Maybe we could add some kind of --environment option to route:cache command so the user doesn't have to muck around with their environment variables.

I think filtering out routes by using the middleware is fine during local development. But I think the route:cache command should be updated, too, so it doesn't include any routes that were registered for a different environment. Maybe we could add some kind of --environment option to route:cache command so the user doesn't have to muck around with their environment variables.

I think when you issue a route:cache command you are always preparing for production.

So the default should be --environment=production.
If some truely wants to cache routes on the local development machine --environment=local can be used. I normally use route:clear on my local development machine.
--environment=staging is a bit odd. Because if you forget to change the routes to production and go into production it won't work. And as a sidenote, changing the routes to production should undertake another test and staging run.

This is getting very confusing!
I think environment is not a good property to test. What you possible may want is APP_DEBUG routes, independend of the environment. But enabling APP_DEBUG on a production system is not really recommended.

@nunomaduro it's amazing faeature


18kami

Source information
18kami 1.4.2
Source language
English
Source new URL
https://18comic.vip/albums/meiman
Other details
The webpage looks different from what i remember, and the title is 18comic now. So the source doesn't load in app, but webview opens.
Acknowledgements

[X] I have updated all installed extensions.
[X] I have opened WebView and checked that the source URL has not changed yet.
[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] I will fill out all of the requested information in this form.

I'm not sure they are related. Also I'm not able to find the one mentioned as duplicate. I checked open and closed ones and no ones posted this. Unless I'm looking in the wrong area. Sorry if I'm wrong.


[docs] Fix that value in onChange can be null in Rating Docs

[o] I have followed (at least) the PR section of the contributing guide.

Converted the value type in onChange in Rating Docs for all languages from
value: number
to
value: number | null
Related #26497

Thanks for the work.
Did you see the directions I gave in https://github.com/mui-org/material-ui/issues/26497#issuecomment-851427712? The files you changed are generate and shouldn't be edited manually.

@eps1lon I read your comments.  I don't completely understand the comments.  Still working on the fix.  Please hold on.   Going to give an update again in 24 hours.

The PR somehow got closed immediately after I reverted my previous change. Please look at this PR instead.
https://github.com/mui-org/material-ui/pull/26542


Is it possible to specify IoT Edge Version?

Would be great to be able to specify a specific IoT Edge version to deploy. or is it possible now?

thanks for your feedback @sihbher . Currently IoTEdgeConfig installs Edge Runtime 1.2. It would help us to understand better your use case - which version of Edge Runtime is needed and why is 1.2 not suitable?

Hi, in my role sometimes have to try to reproduce errors/bugs/strange behaviour in customer/partner environments and they sometimes don't have the latest version, and propose only to update to latest version needs to be supported with facts because it could imply to do changes in a production environments.

@sihbher thank you for sharing your use case. At this time I am closing this issue as we don't have immediate plans for offering earlier versions support.


[Question] Is QIconPicker ready for production?

I have some places in my project admin panel to use it.
And interesting is it ready for production?
I can test on my project.

Well, there is a few more things I would like to do with it. But, those things should not break current functionality.
And, the more people that use it the more tested it will be. Go ahaead and test with it and give some suggestions if you like.


Loading in inference checkpoints

Hi,
I saw this pull request in the DeepSpeed library but I couldn't see any documentation on this: https://github.com/microsoft/DeepSpeed/pull/4664
How can I save and load in inference checkpoints on my own model with DeepSpeed-fastergen?

Hi, you can refer these docs and code examples:

https://github.com/microsoft/DeepSpeed/tree/master/blogs/deepspeed-fastgen
https://github.com/microsoft/DeepSpeed-MII
https://github.com/microsoft/DeepSpeedExamples/tree/master/inference/mii

for adding new unsupported models:

https://github.com/microsoft/DeepSpeed/blob/master/deepspeed/inference/v2/model_implementations/AddingAModel.md


Add spicy stews to item stats plugin

Would be nice if it would show the possible boosts you could get from eating a spicy stew, based on how many spices you put in it. Mechanics are on the wiki, http://oldschoolrunescape.wikia.com/wiki/Spicy_stew

You can't know from the item how many spice has been put in it though, you'd have to track the user's actions and then based on those display the possible boosts. Seems kind of unnecessary work for an item that's not used as much.

Yeah if there's no way to tell what spices have been used without manually tracking it, might not be worth the effort.

If nobody else takes this on, I might use it as an excuse to make some progress in Recipe For Disaster. I haven't looked into the items API but I'm convinced that there'd be some metadata which can assist with this. We'll see if I'm wrong.

@SomeoneWithAnInternetConnection and I figured this one out, no tracking required ;) Shouldn't take long to add a tooltip listing the affected skills.

This is resolved by #1088 now. 🍵


Implementation of GenerateRawCBinding option

This implements GenerateRawCBinding option, which is designed for C libraries, as described here in https://github.com/mono/CppSharp/issues/989.
This option remove the high level classes, and generates only the "internal" classes as structs, with raw pointers.
if enabled with C++ libraries, the behavior undefined and will probably not work.

@ddobrev here is a gist of the generated code for the Nuklear library: https://gist.github.com/raizam/edba07fb4c019b86ca235690a917ce76

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


Error while trying to query how much usdt is in a wallet

Hi,
Im getting a hex error while trying to query how much usdt is in wallet here is my code
from tronpy import Tron, keys
from tronpy.providers import HTTPProvider

def get_usdt_balance(tron, usdt_contract_address, tron_address):
    try:
        # Convert TRON address to hex format
        address = keys.to_hex_address(tron_address)
        print(address)

        result = tron.trigger_constant_contract(
            contract_address=usdt_contract_address,
            owner_address="TGQVLckg1gDZS5wUwPTrPgRG4U8MKC4jcP",
            function_selector="balanceOf(address)",
            parameter=[{"type": "address", "value": address}],
        )

        # Extract the balance from the result
        balance = int(result["constant_result"][0], 16)

        return balance

    except Exception as e:
        print(f"Error checking balance: {e}")
        return None

def main():
    tron = Tron(
        HTTPProvider(api_key="xxxxx"), network="nile"
    )

    # USDT contract address on the TRON network (replace with the actual USDT contract address)
    usdt_contract_address = "TXLAQ63Xg1NAzckPwKHvzw7CSEmLMEqcdj"

    tron_address = "4153213d0cd0058dc92642bd286e4e1a104a87fcdc"

    # Get and print the USDT balance
    usdt_balance = get_usdt_balance(tron, usdt_contract_address, tron_address)
    if usdt_balance is not None:
        print(f"USDT Balance for {tron_address}: {usdt_balance}")

if __name__ == "__main__":
    main()

And this is the error I keep encountering: Error checking balance: ('class org.bouncycastle.util.encoders.DecoderException : exception decoding Hex string: invalid characters encountered in Hex string', 'OTHER_ERROR')
Any help on where im going wrong or if this is a bug how to work around it would be appriciated.

I found the issue and now have this working


[Release] sdk/resourcemanager/costmanagement/armcostmanagement/2.0.0

https://github.com/Azure/sdk-release-request/issues/4087

The breaking changes are introduced and approved in this PR.

@JeffreyRichter , please approve this major version release by adding label of Approved Major Version, thanks.


Cannot set speech rate from within emacs.

This used to work in 1.0. When I use the emacspeak command to set the speech rate, C E D R, speech gets cut off. It doesn't matter what value I set it to, either.

I am having trouble reproducing, works for me fine.  Can you give some specific values you are inputing.  Also, what does "cut off" mean, per word or per block?

So, I was using values between 100 and 500, the problem was resolved after I used values between 0.0 and 1.0. Still, the predefined rates, using C E D number, can’t be used, even tho they work for other servers like espeak.
Diego Vicioso.

On Aug 11, 2024, at 5:46 PM, Robert Melton @.***> wrote:
I am having trouble reproducing, works for me fine. Can you give some specific values you are inputing. Also, what does "cut off" mean, per word or per block?
—
Reply to this email directly, view it on GitHub https://github.com/robertmeta/swiftmac/issues/44#issuecomment-2282899649, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALITD5BQB5ZRGRJDOWGM3QTZQ7LSXAVCNFSM6AAAAABMJYJESWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOBSHA4TSNRUHE.
You are receiving this because you authored the thread.


Add apiErrorMiddleware to auth router

Can you add a test that shows the error comes through? Like duplicate user or something?

Nice, thank you!


class Decompressor can use socket.recv()

Thank you for the suggestion. I think it might be better to instead have the compressor accept a method as as a 2nd optional argument, e.g. Compressor(fp=None, read_func=None) and then it's possible to directly specify a method instead of passing "anything" and having to check.
But ... since the Compressor class is only 65 lines in total I think there's nothing wrong with having a separate SocketCompressor (or whatever sounds right) class to handle sockets and their specific error cases separately instead. Such a class would not be part of this module as it is quite specific.
I'm happy to consider a pull request which allows specifying a 2nd argument as the read-like function, but please against the dev-contrib branch, as detailed here. If you don't have much time I'll consider adding the change (and crediting you for suggesting it) when I get around to another release (e.g. updated lz4 C library).

Instead of creating separate classes SocketCompressor, I personally would have broken backward compatibility and completely abandoned the fd for direct function.
Compressor(write_func)
Decompressor(read_func)
eg.:
Compressor(fd.write) or Compressor(socket.sendall)
Decompressor(fd.read) or Decompressor(socket.recv)

It seems to me a much more flexible and generic solution.

That is a good argument @nri-pl,  although backwards compatibility has to be considered a little bit and also read/recv do not behave the same way and have different exceptions to handle. You can also achieve the same desired functionality with a small wrapper class, e.g. (Python 3):
from collections import namedtuple
from lz4framed import compress, Decompressor

# Present any function as a class with a read function
ReadWrapper = namedtuple('nt_ReadWrapper', 'read')

# Then can e.g. do:
for chunk in Decompressor(ReadWrapper(socket.recv)):
    print(repr(chunk))

# or you could even subclass the Decompressor class, e.g.:
class SocketDecompressor(Decompressor):

    def __init__(self, socket):
        super().__init__(ReadWrapper(socket.recv))


Searchbox on clients tab

Add a global searchbox on clients tab. Each item on the results list will have a badge representing the list where it is.

Added on v1.1.0


Change image for sleep containers away from Alpine

Alpine uses a sleep that cannot be interrupted by SIGTERM, which causes a lot of tests to have to wait for 'podman rm -fa' to time out when removing containers.

LGTM

Nevermind, this seems to be caused by sleep itself, closing


Carthage Static Dependencies Support

Hi @yonaskolb
Quick question about Carthage's new static framework support. To my understanding, Carthage will create a separate directory under build/{Platform} called Static. Do we need to do anything extra to get support for this in Xcodegen.
From the top of my mind, the dependency resolver and framework search paths probably need to be updated?
Thanks.

Hi @peymankh
From looking at Carthage's documentation it seems what we need to do is to add a static property to Dependency for carthage dependencies that would control:

which directory we look for the framework in. Static would look in Carthage/Build/$(PLATFORM_NAME)/Static
whether to add the framework to the Carthage copy-frameworks input and output files

@yonaskolb That property (or something similar) would be useful for the other forms of Dependency as well. Only mentioning it so we name it properly from the start (I’m hoping to tackle the non-Carthage versions of it soon).
Sent with GitHawk

@brentleyjones yep, my thinking too 👍

@yonaskolb Think I can take a stab at this first? I want to make sure it fits the grander static library/framework vision I'm trying to roll out. If not, that's cool, but one change I was thinking was instead of static we call the property preferredLinkage (similar to the buck property) and it defaults to dynamic and can be also be set to static or none. I plan on using the same property and values for other dependency types as well as for framework targets.

Sounds good. Go for it 👍

@yonaskolb @brentleyjones
Hey guys,
Thanks for giving this a head start. Just a few notes on adding a new attribute to dependency. To my understanding, we are currently separating out dependencies via their type already i.e. target and carthage. in regards to other types of dependencies, that probably needs to be defined there not as a new attribute of dependency itself. As for Static carthage dependencies, I'm still not totally convinced, whether a new attribute is necessary. Although I haven't looked at the implementation, would it be possible to pick the framework internally and not mark it explicitly as static or dynamic? So basically if dynamic is available we choose that, if not, we'll try to choose from the Static directory and internally mark it as static to avoid embedding that in the copy frameworks phase. As a result we won't need to add a new attribute to dependency. Optionally we can provide preferredLinkage to make this explicit.
On a separate note, have you guys thought about setting FRAMEWORK_SEARCH_PATHS to include static frameworks? One thing we can do is to use the current one to search recursively ${CARTHAGE_BUILD_PATH}/${PLATFORM}/** or add ${CARTHAGE_BUILD_PATH}/Static if there are any static dependencies available?
What do you think?

I'll need to see how it's been implemented. Before this change you could still do static frameworks if they were distributed as binaries. We couldn't tell if they were static or not, so preferredLinkage would be required. If Carthage handles it correctly for every case then it won't be needed. Like I mentioned above, you might list a framework dependency which is just a path, and we won't know if it's static or dynamic their either, so preferredLinkage will be needed for that case as well. A new attribute won't be an issue for Carthage since if we can determine if it's static we would default preferredLinkage to the correct thing.

@brentleyjones
Fair enough. This is how I'm currently using it, which is not the prettiest.
- carthage: Static/Alamofire
  embed: false

Same. And that currently breaks transitive linking support.

@brentleyjones Definitely, anything I can help to move this forward faster?

I'm planning on a release tomorrow. If one of you wants to get this in before then, be my guest!

I've started work on this, but it won't make this release.
@peymankh Thanks for the offer. I was just bogged down with other stuff. This is my priority (outside of work) now.

No. I made good progress and it’s nearly done, but I’ve gotten side tracked a while ago and I currently don’t have the time to finish it.
I do recommend that we do a simple solution though that simply includes the additional path in the search path. We don’t properly support static frameworks right now (instead doing the “embed: false” hack) and I think the first and easy step would be the continue the status quo here (also require “embed: false” on these).
Sent with GitHawk

@brentleyjones would you like to commit what you have to a PR and we can finish it

@yonaskolb Not really, sorry. It's a large overhaul of how dependencies are picked up and how static frameworks are seen. It was also before the migration to xcproj 6.


Add a proper Duktape fatal error handler

This happens at the time of creating the duktape context, should provide some kind of top level error handler like the one you see in React Native which just pops up a big red error screen with the error message and stack trace.

Adding a little more information here; see the fatal error handling docs for duktape: https://wiki.duktape.org/howtofatalerrors
I think a nice way to do this would be to install a fatal error callback that when hit:

ReactApplicationRoot removes any child components it has
ReactApplicationRoot paints itself red and paints the error msg and stack trace (like React Native)
Raise a cpp exception to halt the program

Perhaps this will be implemented some time after #9 in which case the fatal error handling would be inside the DuktapeEngine class; maybe we add a method there to install a callback when the fatal error handler is hit

Note to self: refactoring the js engine is nearly complete, and is definitely the place for the fatal error handling. After spending some time with Duktape's error handling facilities, I think it makes the most sense to use protected calls everywhere inside the js engine, and when we catch an error at that level, call some user-given callback with the msg and stack trace. For all other errors, such as duktape's out of memory errors, we'll enable DUK_USE_CPP_EXCEPTIONS to bubble them up as runtime exceptions

Addressed in 4c82eecd60d3dbba247b80da946569bd9e6e155b and the previous two commits.


Download multiple courses

Looking good, will review today 👍

Overall, it's looking good.
Thank you for your work and patience.
Merged.


Gcc6 fixes

With these fixes, it's possible to build (and boot!) a full op-build master-next build with GCC6.
None of these changes should be controversial, and GCC6 did pick up actual problems such as:

not specifying what C++ version to build (and there are changes that matter)
returning something from a void method
invalid __sync ops (can't use a bool)
relying on the address of a passed-by-reference object able to be NULL (which is not at all what anyone would expect, and it appears the compiler may have been okay to assume it could never be null)

This change is

Nice work!

I'll get this pulled into our internal repo for review and testing.

Note, for gnu++03, there's one extra build error that needs fixing: .//mvpd_accessors/getMBvpdAttr.C:395:36: error: in C++98 ‘l_vmVersionBuf’ must be initialized by constructor, not by ‘{...}’
New patch series fixes that issue too. Seems to boot on firestone!

Any news?

ping?

Rebased and also addreses https://github.com/open-power/hostboot/issues/69

We have to detect the ability of the host g++ to accept the -std=gnu++03 as RHEL6.4 contains some kind of stone age GCC.

Note that without this patch I cannot build hostboot on my laptop (Fedora 24)

Is this PR still relevant?  I see a fork used it but I don't know what fspbld is.

Is this PR still relevant? I see a fork used it but I don't know what fspbld is.

No longer relevant, we have these bits upstream (somehow, I forget how), and there's now the GCC8 patches


[tinygltf] update to v.2.8.4

Fixes https://github.com/microsoft/vcpkg/issues/30213

[x] Changes comply with the maintainer guide
[x] SHA512s are updated for each updated download
[ ] The "supports" clause reflects platforms that may be fixed by this new version
[ ] Any fixed CI baseline entries are removed from that file.
[ ] Any patches that are no longer applied are deleted from the port's directory.
[x] The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
[x] Only one version is added to each modified port's versions file.

/azp run


[MSINTEROP-824] Add database schema documentation

relies on #59 (only because there are slight modifications to the database in that PR)

/verified

/verified

@myakove had to rebase, can you review again