video cache

Does it support the cache?

It is using VideoView for movie display. I am not sure but I believe that is it supporting streaming and buffering. I think cache is in the view but it is destroyed when view is destroyed (in looping view is loaded once, but if you leave an app and open it again then movie will be downloaded again)

thanks a lot


GitHub Workflow yaml is interpreted as Ansible Playbook

Putting valid GH workflow definition under .github/workflows/site.yml renders following error:
Incorrect type. Expected "array". yaml-schema: Ansible Playbook (0) [1, 1]

Renaming the file fixes the issue and applies "GitHub Workflow" as expected.
This happens because of schema definition for Ansible as defined here:
https://github.com/b0o/SchemaStore.nvim/blob/57116dd9fd9ee4d73c1e9a1335d92b4c71851cf7/lua/schemastore/catalog.lua#L1095-L1098
I think that schemas for files that are nested should be prioritized and override more general ones. So in this case "GitHub Workflow" should take a precedence over "Ansible Playbook"  because its file matching are more fine grainer.

There is not much we can do in this plugin, because we are just consuming the catalog from the upstream SchemaStore project and providing it to the LSP. I would recommend opening an issue in the upstream SchemaStore repo or with yaml-language-server.

@b0o https://github.com/SchemaStore/schemastore/pull/3929 should fix the issue.

Nice, it was picked up by our CI already: https://github.com/b0o/SchemaStore.nvim/commit/58a965eedbfe7c358938b0e535ed2d98a4520987
If you update your neovim plugins, you should receive these changes.


Development UI - Make it hybrid search

Describe the bug
The built-in development UI only does keyword search
To Reproduce
n/a
Expected behavior
Allow semantic search
Screenshots
n/a
Meilisearch version:
v1.8
Additional context
Maybe a slider for ratio is required.

Hello @doreilly257
The UI is related to the mini-dashboard repository. We provide a minimal UI and we don't plan to update it for the moment because of our bandwidth. Sorry :(
However, anyone can fork the repo and improve it of course 👍


Update launch.json Attach config to use process picker.

Using the process picker is much better since if you are using VSCode you are likely to have more than one PowerShell process running.  With the picker, just type pow and the process list will filter down to the PowerShell processes.  Just pick the desired process to attach to based on the PID (or command line).

Great!
Is it possible to add a regex filter like "powershell*"?

Unfortunately, I don't believe so.  This is a feature of the C#/.NET Core debugger and if you specify processId, then you are not supposed to specify processName.
Also, eventually you might want to attach to a host named something other than PowerShell.  :-)  Besides, when you press F5 to attach, the process list will appear, type pow and the list will immediately filter down to just the powershell processes.

LGTM.


Added_footer

Fixes #34  by @tinniaru3005
Description
The issue #34 has been resolved by adding a footer to the page. The footer design has been inspired by the original website of Creative Commons to maintain consistency. Additionally, the Twitter icon has been updated to enhance the overall design and functionality.
Screenshots

Checklist

[x] My pull request has a descriptive title (not a vague title like Update index.md).
[x] My pull request targets the default branch of the repository (main or master).
[x] My commit messages follow best practices.
[x] My code follows the established code style of the repository.
[ ] I added or updated tests for the changes I made (if applicable).
[ ] I added or updated documentation (if applicable).
[x] I tried running the project locally and verified that there are no
visible errors.

Developer Certificate of Origin

For the purposes of this DCO, "license" is equivalent to "license or public domain dedication," and "open source license" is equivalent to "open content license or public domain dedication."

Developer Certificate of Origin
Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

@nandu-99 Hi! Thanks for this contribution! ❤
This is not a 1-to-1 implementation of the code in the footer that's currently utilized. It should follow the exact HTML markup and the rendered output should match what is presently visible on CreativeCommons.org. To achieve that there may be a need to use a localized CSS file to correct items local to this repository.
Also, adding the Twitter logo would have to happen here, and this issue is currently status: blocked:

https://github.com/creativecommons/index-prototype/issues/48

@possumbilities Thank you for your feedback! I've implemented the required changes and made sure to closely follow the existing HTML markup to match the rendered output of CreativeCommons.org. Additionally, I've kept the separate CSS file as suggested.
Regarding the logo of Twitter, I've reverted it back to its original state to ensure consistency with the website.
Could you please review the changes and provide any further feedback or suggestions? Your input is highly appreciated!

Hi @nandu-99 that's all much better. I would also recommend the following changes as well to be closer to the implementation of CreativeCommons.org:

include the entire vocabulary directory in a sensible location to import from. You can find it in index-prototype. This will ensure that relevant fonts are present as well, and make it easier to sync updates locally from vocabulary later.
Rather than a <link> in the html, I'd suggest including it the same way its done with an @import and a @layer in a style.css file see vocabulary-theme

I believe #206 resolved this. Closing, thanks for your contribution!

@TimidRobot So will this issue be assigned to me ?


Cleanup M3 token templates for theme lookups

fixes https://github.com/flutter/flutter/issues/117933
Pre-launch Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I signed the CLA.
[x] I listed at least one issue that this PR fixes in the description above.
[ ] I updated/added relevant documentation (doc comments with ///).
[ ] I added new tests to check the change I am making, or this PR is test-exempt.
[x] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

test-exempt: code refactor with no semantic change


[SPARK-47414][SQL] Lowercase collation support for regexp expressions

What changes were proposed in this pull request?
Introduce collation awareness for regexp expressions: like, ilike, like all, not like all, like any, not like any, rlike, split, regexp_replace, regexp_extract, regexp_extract_all, regexp_count, regexp_substr, regexp_instr. Note: collation support is only enabled for binary (UTF8_BINARY, UNICODE) & lowercase (UTF8_BINARY_LCASE) collation.
Why are the changes needed?
Add collation support for built-in regexp functions in Spark.
Does this PR introduce any user-facing change?
Yes, users should now be able to use collated strings within arguments for built-in regexp functions: like, ilike, like all, not like all, like any, not like any, rlike, split, regexp_replace, regexp_extract, regexp_extract_all, regexp_count, regexp_substr, regexp_instr.
How was this patch tested?
Unit regexp expression tests and e2e sql tests.
Was this patch authored or co-authored using generative AI tooling?
No.

thanks, merging to master!


Not working with Nuxt 3

Describe the bug
Not sure if this is  Nuxt or Hyper Fetch related issue.
Importing the Client will results to default is not a constructor in Nuxt.
Any help would be much appreciated. Thank you.
To Reproduce
Steps to reproduce the behavior:

Go to hyperfetch-nuxt-demo
See error on the preview

Expected behavior
No error should happen.
Screenshots
see hyperfetch-nuxt-demo
Desktop (please complete the following information):
N/A
Smartphone (please complete the following information):
N/A
Additional context
N/A

From Nuxt https://github.com/nuxt/nuxt/issues/18532

Still default is not a constructor here https://stackblitz.com/edit/hyperfetch-nuxt-demo?file=pages%2Findex.vue
Updated the hyper-fetch to 3.3.0
Any idea ?

Still default is not a constructor here https://stackblitz.com/edit/hyperfetch-nuxt-demo?file=pages%2Findex.vue
Updated the hyper-fetch to 3.3.0
Any idea ?


It should run only in python3?

If i want to extract browser history using python2 .How should i do that?

Only Python3 and I need to fix an error for safari for macOS.


Non-void functions never tested for missing return value

In stmt.c test_return there is a condition that is never met.
if ( stmt->return_value ) {
   // ...
}
else {
   if ( target->func->return_type ) {
      t_diag( task, DIAG_POS_ERR, &stmt->pos,
         "missing return value in function `%s`", str.value );
      t_bail( task );
   }
}

Since this test occurs only when the parser finds a return statement, a non-void function without a return statement will be overlooked.
In the current state, the code below compiles without errors:
function str test()
{
    // No return
}

I did this on purpose. The reason is that checking every possible path of execution for a return statement is complicated. The goto statement contributes to the complexity of the task. At this time, I haven't developed a good way to solve this.
This behavior is undefined, but the compiler handles it somewhat. At the end of a function, the compiler generates code that returns a zero. So even though a return statement might not be encountered, it will still work, although possibly erroneously.

This is now resolved for the most part. You can still bypass the check by using a goto statement if you want.

@wormt nice to see you're still working on this. I forked it a while ago for a project I was making for Zandronum, but I unfortunately found myself with no spare time to continue.

Hey, @caiosm1005. Nice to see you around.
  One of them is a type system. It supports string concatenation via the + operator. A fixed type is also supported. More information can be found in the Strong Types section of the documentation.


Proposal: Type Builder API

Alongside the relationship API proposed in #9879, it would be very useful to expose an API to programatically build types - this is useful for making comparisons between a build-in type, and a type structure which isn't a part of the original compilation (lint rules, language service extensions, and external tools could find this a very useful API surface, and this is almost a prerequisite for a type provider-like feature). I have a protototype here, and the new API surface (excluding anything covered by #9879) looks like this:
interface TypeChecker {
  getTypeBuilder(): TypeBuilder;
}

interface TypeBuilder {
    startEnumType(): EnumTypeBuilder<Type>;
    startClassType(): ClassTypeBuilder<Type>;
    startInterfaceType(): InterfaceTypeBuilder<Type>;
    startTupleType(): TupleTypeBuilder<Type>;
    startUnionType(): UnionTypeBuilder<Type>;
    startIntersectionType(): IntersectionTypeBuilder<Type>;
    startAnonymousType(): AnonymousTypeBuilder<Type>;
    startNamespace(): NamespaceBuilder<Symbol>;
    startSignature(): SignatureBuilder<Signature>;

    // create an unbound type parameter, optionally with a constraint, for use in generic creation
    createTypeParameter(name: string, constraint?: Lazy<Type>): TypeParameter;
    // Useful for constructing reusable generics in your structures - probably need to make the params/type lazy
    createTypeAlias(name: string, params: TypeParameter[], type: Type): Symbol;
    // This way consumers can fill out generics - probably need to make the type/type arguments lazy
    getTypeReferenceFor(type: GenericType, ...typeArguments: Type[]): TypeReference;
    // Unsure about this one.
}

The goal is to have a fluent API capable of creating an immutable version of any type or structure expressible within the type system. From my prototyping experience, there are only a handful of locations where a link or cache needed to be added to ensure the checker never needs to try to access an AST backing the types - so these "synthetic" or "declarationless" types actually tend to work fairly well within the checker once those are in-place. A few more links or hooks likely need to be added on top of those to ensure that the values are only retrieved lazily (rather than applied eagerly on API type creation). The laziness is actually super important for creating circularly referential types with an immutable API (otherwise a type can't really get a handle to it's finished self before it is done).
Known shortcoming: There's no method (in the type definition I have posted here) for making a member mapped to a well-known symbol, such as Symbol.iterator. I think this would just surface as parameters for object/class/interface members names taking string | WellKnownSymbol and having a method for looking up well-known symbols, though.
cc: @ahejlsberg @mhegazy @DanielRosenwasser @rbuckton
I'd love to hear everyone's thoughts on this - the general fluent creation API I've been working off and on for the last few weeks, and I think it has real promise for letting consumers make valid types safely (and the intellisense support is top notch).

Just curious, could the API also provide a way to 'eval up' a type for simple cases, for brevity sake, e.g.:
const c1 = builder.eval(`class { readonly x: number; readonly y: number; }`);
if (checker.isAssignableTo(c1, someOtherType)) {
  // ...
}

@yortus A eval like API is more approachable for new-comers. But for TypeScript compiler a low-level builder is more desirable. A low-level builder is more powerful for building complex types, e.g. conditional fields where arbitrary logic needs to be executed. And low-level builder does not mix parsing complexity in.
eval like API can be built upon builder API, as a library, like babel-template

That's why I couldn't find ts.createTypeAliasDeclaration then!

Is this proposal dead?
I think I heard that a downside of this kind of approach is that it could be hard for devs consuming the types to debug.

I'm releasing a simple version of this for checking types in runtime in type-plus: https://github.com/unional/type-plus/pull/71


Add integration test

very much still a WIP
This PR introduces an integration test that will test an optimint based network. Instead of building out optimint support for using the KVstore app, I decided to use a default starport app. Not only because starport apps are our initial target and are already working on optimint, but also because it avoids developing the proprietary pieces necessary to get the kvstore tendermint app working with optimint in a similar way.
Using a starport app requires a slight hack if we are to use the local version of optimint in the e2e test. Instead of using our forked version of the sdk, we actually use upstream sdk, but create our own start-optimint (name defo tbd) command and compile the app here. That also means that we will be keeping the e2e test in it's own go module.
still have to:

[ ] add .github workflow
[X] fix dockerfiles
[X] add grpc mock server to network
[ ] write test logic
[ ] swap out my rollup app for something more permanent
[ ] bonus: slim down rollup app

closes #169
should only be merged after: #170

Just to record a decision made earlier this week, we are waiting on the integration test for celestia-app to be fleshed out before finishing this one, as both will be incredibly similar in that they involve a few starport app interacting

Closing, as it's out of date.


No verilog line number or signal name specified with "ERROR: Multiple edge sensitive events found for this signal!"

Makes it really hard to debug what's causing this.

Have a look in the logfile (if you suppress log messages in the console) to learn when the error happened. It should look something like this:
2.2.7. Executing PROC_DFF pass (convert process syncs to FFs).
Creating register for signal `\top.\q' using process `\top.$proc$test.v:2$1'.
ERROR: Multiple edge sensitive events found for this signal!

In this example the module name is top, the signal written to is q, and the location is test.v:2 (file test.v in line number 2), encoded in the process name.


Update http://<IP_ADDRESS>:5000/event/eventsbygames api

get requests do not support sending data in the request body.

check it out!

Working at Postman. But when I run this in the project it doesn't work. This is taken from the axios document. https://github.com/axios/axios. Request methods applicable for only post, delete or put methods only.

Okey converts GET request into POST request. Hope this will resolve the issue. plz check and confirm

working.


Publish artifact on a new tag

Publishing on merge is error prone and with multiple PRs can break proper versioning.

Now when you will create a Github release artifact publishing will start


Complications to install on Windows 10

PHP Version
8.0.26
Shopware Version
6.2
Expected behaviour
The installation is easy to do.
Actual behaviour
First problem is that you need to install with --no-scripts the "composer install" (not indicated in the readme like this), because if you don't then the pre-installation script is run (bin/console ...), which tries to load the autoload.php which obviously does not exist yet.
Then It is not clear at all if you need to run a command for system:setup or system:install or to go to the installation page. You should try stuff, drop part of it, retry etc until you arrive to something.
Then the commands on the composer.json do not work because $PHP_BINARY is nothing, at least in windows.
After doing that, you will find that you just have an error 500, with no logs on apache or php. You need to turn on the debug mode to find out that actually openssl_pkey_new and openssl_pkey_export_to_file return nothing, and add some debug information to understand that you NEED to pass the path of the configuration of openssl (openssl.cnf) for it to work.
Then an error happens regarding the public.pem/private.pem file permissions, which are a pain to change in Windows (ok, that's not really your fault, but why do I need a public.pem/private.pem file of anything, for a basic installation?)
Finally, I figured out that I had to do the compilation of the theme,  with the particular theme:compile, theme: refresh, theme:change commands. It did not work at all, because the import routes are broken on Windows. To fix it I had to go to storefront/Theme/ThemeFileImporter.php and change $file->getFilePath() so that backslashes are now "/".
How to reproduce
Try to install it in a WAMP stack on Windows.

Running shopware under windows is not supported, refer to the official docs.
However you should be able to set shopware up using the Windows Subsystem for Linux (WSL).


WASI: Add stdio and file system support

Hi! I extended the wasi package to support writing and reading from Stdin, Stdout and Stderr. By default the host proccess's Stdin, Stdout and Stderr is used, but custom io.Reader/io.Writers can also be set, which is not possible when using wasmtime-go yet (without creating a temporary file https://github.com/bytecodealliance/wasmtime-go/issues/34).
Also added rudimentary support for preopened directories, so that wasm binaries can open, read and write to files.
The wasi package now supports a few more methods (relates to issue https://github.com/mathetake/gasm/issues/10):

fd_prestat_get
fd_prestat_dir_name
path_open
fd_read
fd_close

I added a wasi.WASI type, which holds preopened directories, custom readers and writers and other options for a particular wasi environment.
Example usage:
vm, err := wasm.NewVM(mod, wasi.New(
	wasi.Stdin(myReader),
	wasi.Stdout(myWriter),
	wasi.Stderr(myErrWriter),
	wasi.Preopen(".", wasi.DirFS(".")),
).Modules())
if err != nil {
	panic(err)
}

if err := vm.ExecExportedFunction("_start"); err != nil {
	panic(err)
}

I couldn't get go code compiled with tinygo to read from Stdin, write to Stderr, or open files. Unless I'm missing something, I think tinygo doesn't support that yet :\ (EDIT: but maybe not for long: https://github.com/tinygo-org/tinygo/pull/1659, https://github.com/tinygo-org/tinygo/issues/1505). But rust does, so I added rust_stdio.rs and rust_file_system.rs to examples/wasm and their respective wasm binaries to test wasi support in gasm (https://github.com/mathetake/gasm/issues/4).
Let me know if you want anything changed, before merging.

@Gaboose Thanks you so much! This is really awesome. Let me review in the next weekend.

@Gaboose sorry for being late, code LGTM thank you so much!
TinyGo's file support has landed the dev branch (https://github.com/tinygo-org/tinygo/pull/1659) so it's available in the tinygo/tinyo-dev:latest image (https://hub.docker.com/r/tinygo/tinygo-dev). Could you try TinyGo, and hopefully remove rust codes? Thanks!

Nice work on the https://github.com/tinygo-org/tinygo/pull/1659! I rebuilt stdio.go and file_system.go examples with the new TinyGo, and the tests now pass, so I removed the rust code and the corresponding wasm modules.
The new TinyGo modules import one more method fd_fdstat_get, which I implemented just enough for the tests to pass.

@Gaboose Thank you so much for your work!


Tab/ F5 not working when input is focused

I think there needs to be a list of key chars that don't trigger the preventDefault function

I'm pretty busy atm, though I think the idea is good. I actually thought about reworking the whole thing at some point cause the current code base is quite messy. In the meantime your are welcome to collab if you need that feature to be in the repo. I can update the npm package if necessary


GPU Version of ESPIRiT Calibration?

Hi, I use bart command line tools in my reconstruction pipeline. I wonder if there is any GPU implementation of ecalib for faster computation? Thanks.

ecalib has an undocumented GPU option (-g) for the second part of the algorithm. You also should look at coil compression, or look at enlive (for calibration). Please ask questions on the mailing list and do not use Github issues next time. This is not an issue.

Thanks for the reply. Will ask the question on the mailing list next time.
On Mon, Dec 7, 2020 at 1:18 AM Martin Uecker<EMAIL_ADDRESS>wrote:

ecalib has an undocumented GPU option (-g) for the second part of the
algorithm. You also should look at coil compression, or look at enlive (for
calibration). Please ask questions on the mailing list and do not use
Github issues next time. This is not an issue.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/mrirecon/bart/issues/241#issuecomment-739694753, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AHVRI27U25QYSDJQS2CGWALSTRXTNANCNFSM4UP2MS2Q
.


added a git course

What does this PR do?
Add resource
For resources
a git and GitHub tutorial
Why is this valuable (or not)?
How do we know it's really free?
it is available on youtube
For book lists, is it a book? For course lists, is it a course? etc.
Checklist:

[x] Read our contributing guidelines
[ ] Search for duplicates.
[x] Include author(s) and platform where appropriate.
[x] Put lists in alphabetical order, correct spacing.
[ ] Add needed indications (PDF, access notes, under construction)

Follow-up

Check the status of GitHub Actions and resolve any reported warnings!

Thanks, and welcome to free-programming-books!


Refs 1920: Did a little more of updates

Summary
Added my intro of myself
Testing steps

@kwarnerredhat check out the contribution guidelines here: https://github.com/content-services/content-sources-backend/blob/main/CONTRIBUTING.md#contributing  for the pr title.  You'll want to adjust it to match which will make the PR Validation check pass

Oh yeah my fault I got you

This still needs to have it's Title changed. Do so by:

clicking the edit button

Then using the guidelines that justin mentioned from above.

⚠ This task currently requires qe-approval, but this PR does not fully resolve the task.  Please contact QE to determine appropriate testing required.

Ack


⚠ Bofrost.de has degraded performance

In aa2e9ea, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1084 ms

Resolved: Bofrost.de performance has improved in 8c581cf after 53 minutes.


TEST: CI: dask test_notebooks fails with RuntimeError: Cluster failed to start: No module named 'bokeh'

example failure: https://github.com/modin-project/modin/actions/runs/3322991945/jobs/5551188570
This workflow run passed before the commit was merged, but failed when I ran it just now. I think bokeh is a dependency of dask.

stack trace
RuntimeError                              Traceback (most recent call last)
Cell In [2], line 13
     10     url_path = "https://modin-test.s3.us-west-1.amazonaws.com/yellow_tripdata_2015-01.csv"
     11     urllib.request.urlretrieve(url_path, "taxi.csv")
---> 13 modin_df = pd.read_csv(s3_path,parse_dates=["tpep_pickup_datetime","tpep_dropoff_datetime"],quoting=3,nrows=1000)

File ~/work/modin/modin/modin/logging/logger_decorator.py:128, in enable_logging.<locals>.decorator.<locals>.run_and_log(*args, **kwargs)
    113 """
    114 Compute function with logging if Modin logging is enabled.
    115
   (...)
    125 Any
    126 """
    127 if LogMode.get() == "disable":
--> 128     return obj(*args,**kwargs)
    130 logger = get_logger()
    131 logger_level = getattr(logger, log_level)

File ~/work/modin/modin/modin/_compat/pandas_api/latest/io.py:156, in read_csv(filepath_or_buffer, sep, delimiter, header, names, index_col, usecols, squeeze, prefix, mangle_dupe_cols, dtype, engine, converters, true_values, false_values, skipinitialspace, skiprows, nrows, na_values, keep_default_na, na_filter, verbose, skip_blank_lines, parse_dates, infer_datetime_format, keep_date_col, date_parser, dayfirst, cache_dates, iterator, chunksize, compression, thousands, decimal, lineterminator, quotechar, quoting, escapechar, comment, encoding, encoding_errors, dialect, error_bad_lines, warn_bad_lines, on_bad_lines, skipfooter, doublequote, delim_whitespace, low_memory, memory_map, float_precision, storage_options)
    154 f_locals.pop("mangle_dupe_cols", None)
    155 kwargs = {k: v for k, v in f_locals.items() if k in _pd_read_csv_signature}
--> 156 return _read(**kwargs)

File ~/work/modin/modin/modin/_compat/pandas_api/common/io.py:35, in _read(**kwargs)
     22 def _read(**kwargs):
     23     """
     24     Read csv file from local disk.
     25
   (...)
     33     modin.pandas.DataFrame
     34     """
---> 35     Engine.subscribe(_update_engine)
     36     from modin.core.execution.dispatching.factories.dispatcher import FactoryDispatcher
     38     squeeze = kwargs.pop("squeeze", False)

File ~/work/modin/modin/modin/config/pubsub.py:217, in Parameter.subscribe(cls, callback)
    208 """
    209 Add `callback` to the `_subs` list and then execute it.
    210
   (...)
    214     Callable to execute.
    215 """
    216 cls._subs.append(callback)
--> 217 callback(cls)

File ~/work/modin/modin/modin/pandas/__init__.py:161, in _update_engine(publisher)
    158     if _is_first_update.get("Dask", True):
    159         from modin.core.execution.dask.common import initialize_dask
--> 161         initialize_dask()
    162 elif publisher.get() == "Cloudray":
    163     from modin.experimental.cloud import get_connection

File ~/work/modin/modin/modin/core/execution/dask/common/utils.py:47, in initialize_dask()
     45     memory_limit = Memory.get()
     46     worker_memory_limit = memory_limit // num_cpus if memory_limit else "auto"
---> 47     client = Client(n_workers=num_cpus,memory_limit=worker_memory_limit)
     49 num_cpus = len(client.ncores())
     50 NPartitions._put(num_cpus)

File /opt/hostedtoolcache/Python/3.8.14/x64/lib/python3.8/site-packages/distributed/client.py:982, in Client.__init__(self, address, loop, timeout, set_as_default, scheduler_file, security, asynchronous, name, heartbeat_interval, serializers, deserializers, extensions, direct_to_workers, connection_limit, **kwargs)
    979 preload_argv = dask.config.get("distributed.client.preload-argv")
    980 self.preloads = preloading.process_preloads(self, preload, preload_argv)
--> 982 self.start(timeout=timeout)
    983 Client._instances.add(self)
    985 from distributed.recreate_tasks import ReplayTaskClient

File /opt/hostedtoolcache/Python/3.8.14/x64/lib/python3.8/site-packages/distributed/client.py:1172, in Client.start(self, **kwargs)
   1170     self._started = asyncio.ensure_future(self._start(**kwargs))
   1171 else:
-> 1172     sync(self.loop,self._start,**kwargs)

File /opt/hostedtoolcache/Python/3.8.14/x64/lib/python3.8/site-packages/distributed/utils.py:406, in sync(loop, func, callback_timeout, *args, **kwargs)
    404 if error:
    405     typ, exc, tb = error
--> 406     raise exc.with_traceback(tb)
    407 else:
    408     return result

File /opt/hostedtoolcache/Python/3.8.14/x64/lib/python3.8/site-packages/distributed/utils.py:379, in sync.<locals>.f()
    377         future = asyncio.wait_for(future, callback_timeout)
    378     future = asyncio.ensure_future(future)
--> 379     result = yield future
    380 except Exception:
    381     error = sys.exc_info()

File /opt/hostedtoolcache/Python/3.8.14/x64/lib/python3.8/site-packages/tornado/gen.py:762, in Runner.run(self)
    759 exc_info = None
    761 try:
--> 762     value = future.result()
    763 except Exception:
    764     exc_info = sys.exc_info()

File /opt/hostedtoolcache/Python/3.8.14/x64/lib/python3.8/site-packages/distributed/client.py:1238, in Client._start(self, timeout, **kwargs)
   1235 elif self._start_arg is None:
   1236     from distributed.deploy import LocalCluster
-> 1238     self.cluster = await LocalCluster(
   1239         loop=self.loop,
   1240         asynchronous=self._asynchronous,
   1241         **self._startup_kwargs,
   1242     )
   1243     address = self.cluster.scheduler_address
   1245 self._gather_semaphore = asyncio.Semaphore(5)

File /opt/hostedtoolcache/Python/3.8.14/x64/lib/python3.8/site-packages/distributed/deploy/spec.py:398, in SpecCluster.__await__.<locals>._()
    396 async def _():
    397     if self.status == Status.created:
--> 398         await self._start()
    399     await self.scheduler
    400     await self._correct_state()

File /opt/hostedtoolcache/Python/3.8.14/x64/lib/python3.8/site-packages/distributed/deploy/spec.py:319, in SpecCluster._start(self)
    317 self.status = Status.failed
    318 await self._close()
--> 319 raise RuntimeError(f"Cluster failed to start: {e}") from e

RuntimeError: Cluster failed to start: No module named 'bokeh'
RuntimeError: Cluster failed to start: No module named 'bokeh'
============================== 4 failed in 58.87s ==============================

I also got this error in pandera CI: https://github.com/unionai-oss/pandera/actions/runs/3348692649/jobs/5549781070

It is only a temporary solution but limiting the dask+distributed versions to be <= 2022.9.2 appears to resolve this error

This has been resolved upstream in Dask.  My apologies for the issue.  The previous release has been yanked from PyPI and a new release has been published.  It is on PyPI now and should be on conda-forge shortly.

@mvashishtha, should we close this issue?

@YarShev yep, nothing left to do here.


Update Status UI Code

Cleanup / Update of the Status UI Code:

Applied code conventions
Moved UI from PlayerController to Character
-> Fixes respawn HP bug

Sweet, thanks for cleaning it up.


Command to go to next diff section in PR

Is there a command which could move focus to the next section of diff in a PR? "workbench.action.compareEditor.nextChange" can do this but it is only for a given file, and cannot move focus to the diff in the next file if it reaches the end of current source file.
Not sure if "pr.goToNextDiffInPr" can do it and haven't tried it successfully.

pr.goToNextDiffInPr is the way to do this. Can you share of gif of this not working for you?

I added below keyboard mapping below which seems does nothing for the shortcut, tried change to to the commented out command which seems working but it does navigation in a single file. Is it used correctly here?
{
"key":      "ctrl+n",
// "command":  "workbench.action.compareEditor.nextChange",
"command": "pr.goToNextDiffInPr",
},

That should work across files until it gets to the last change in the "last" file, at which point it shows a notification. Do you see the nofication?

Thanks for a pointer, does the same config on another device and it worked. Close it for now.


Python functions which accept lists does not do so in Julia

Consider the function cse, which in python accepts lists with expressions. If you send in an array in Julia, you get an error. I worked around it by redefining line 186 in SymPy.jl
from
($meth)(ex::Sym, args...; kwargs...) = sympy_meth(symbol($meth_name), ex, args...; kwargs...)
to
($meth)(ex, args...; kwargs...) = sympy_meth(symbol($meth_name), ex, args...; kwargs...)

Thanks for pointing this out! I see the problem, but this isn't such a good fix, as there can be conflicts with Base functions. (such as collect.) Seems better to add a vectorized from for the method. Rather than your suggestion, try adding this line just after:
 ($meth){T<:SymbolicObject}(ex::Vector{T}, args...; kwargs...) = sympy_meth(symbol($meth_name), map(project,ex), args...; kwargs...)

and let me know if that helps solve this issue. The tests still pass, but I need to add tests for this behavior. If that works, you can put together a PR if you want, or I can push my changes.

I tried your method which works well for julia arrays of dim 1, so for an array of dim 2 (matrx) i had to vectorize the input and then reshape the output, like this
    change,res = cse(AA[:])
    reshape(res,size(AA))

That's not good. We can change Vector{T} to Array{T] in the definition and it should work.

Unfortunately, this method (with Array{T}) produces an error
julia> change,res = cse(AA);
ERROR: PyError (:PyObject_Call) <type 'exceptions.AttributeError'>
AttributeError("'list' object has no attribute 'atoms'",)
  File "/home/fredrikb/.julia/v0.4/Conda/deps/usr/lib/python2.7/site-packages/sympy/simplify/cse_main.py", line 441, in cse
    for expr in reduced_exprs])

 [inlined code] from /home/fredrikb/.julia/v0.4/PyCall/src/exception.jl:81
 in pycall at /home/fredrikb/.julia/v0.4/PyCall/src/PyCall.jl:361
 in fn at /home/fredrikb/.julia/v0.4/PyCall/src/conversions.jl:194
 in call_sympy_fun at /home/fredrikb/.julia/v0.4/SymPy/src/SymPy.jl:263
 in sympy_meth at /home/fredrikb/.julia/v0.4/SymPy/src/SymPy.jl:269
 in cse at /home/fredrikb/.julia/v0.4/SymPy/src/SymPy.jl:188

Can you show me what defines AA? I'd like to think there is a convenient
workaround to this and that will help me debug it. Thanks
On Tue, Jan 26, 2016 at 9:11 AM, baggepinnen<EMAIL_ADDRESS>wrote:

Unfortunately, this method (with Array{T}) produces an error
julia> change,res = cse(AA);
ERROR: PyError (:PyObject_Call) <type 'exceptions.AttributeError'>AttributeError("'list' object has no attribute 'atoms'",)
File "/home/fredrikb/.julia/v0.4/Conda/deps/usr/lib/python2.7/site-packages/sympy/simplify/cse_main.py", line 441, in cse
for expr in reduced_exprs])
[inlined code] from /home/fredrikb/.julia/v0.4/PyCall/src/exception.jl:81
in pycall at /home/fredrikb/.julia/v0.4/PyCall/src/PyCall.jl:361
in fn at /home/fredrikb/.julia/v0.4/PyCall/src/conversions.jl:194
in call_sympy_fun at /home/fredrikb/.julia/v0.4/SymPy/src/SymPy.jl:263
in sympy_meth at /home/fredrikb/.julia/v0.4/SymPy/src/SymPy.jl:269
in cse at /home/fredrikb/.julia/v0.4/SymPy/src/SymPy.jl:188
—
Reply to this email directly or view it on GitHub
https://github.com/jverzani/SymPy.jl/issues/59#issuecomment-175033406.

--
John Verzani
Chair, Department of Mathematics
College of Staten Island, CUNY
<EMAIL_ADDRESS>

The matrix AA is the result of the following code, if it helps I can try to setup a small example which reproduces the error.
AA = zeros(Sym,n_joints, 4n_joints);
    for i = 1:n_joints
        for j = 1:size(AA,2)
            AA[i,j] = coeff(eq[i],w[j]);
        end
        print(i)
    end
julia> typeof(AA)
Array{SymPy.Sym,2}

Thanks, this is an issue with how SymPy.jl uses Julia arrays to store
symbolic objects, rather than SymPy arrays. I have  some other ways of
doing this, but none seem better than manually doing linear indexing and
reshaping:

cse(convert(SymMatrix, AA))

This returns a symbolic matrix object which, if desired, can be converted
to an Array{Sym} object. This step may not be necessary, but is for many
subsequent manipulations.

I could put the linear indexing/reshaping code into the method, but
while that may be the right thing for cse, it may not be for other
functions.

For now, I think your workaround is best. Thoughts?
On Tue, Jan 26, 2016 at 9:16 AM, baggepinnen<EMAIL_ADDRESS>wrote:

The matrix AA is the result of the following code, if it helps I can try
to setup a small example which reproduces the error.
AA = zeros(Sym,n_joints, 4n_joints);
for i = 1:n_joints
for j = 1:size(AA,2)
AA[i,j] = coeff(eq[i],w[j]);
end
print(i)
end
julia> typeof(AA)
Array{SymPy.Sym,2}
—
Reply to this email directly or view it on GitHub
https://github.com/jverzani/SymPy.jl/issues/59#issuecomment-175035346.

--
John Verzani
Chair, Department of Mathematics
College of Staten Island, CUNY
<EMAIL_ADDRESS>

Okay, I decided to special case cse as the more general solution was leaving arrays of type Any. If you find other instances where a list is needed, could you let me know? I'll implement the general pattern in that case. Thanks!

Thanks, your effort is much appreciated! I will let you know, should I find any more cases!


WebGL and rotation when hardware acceleration disabled

We're seeing some visible sheering / distortion when rotating an image with WebGL enabled and the browser's hardware acceleration disabled

Is this expected behavior?

That's funky... certainly not intended, but I'm not sure what I would exactly expect in this case - I've never considered webgl without a graphics card being available. I tried disabling hardware acceleration on my browser (Chrome, MacOS) and the viewer can't even be created. (This revealed a bug I have created a PR for, https://github.com/openseadragon/openseadragon/pull/2557).
What system are you on that lets you use webgl without hardware acceleration? Looks like the canvas drawer is also affected, though not in exactly the same way and less "glitchy" looking.

Yeah that's interesting that a viewer can't even be created on your machine.  I don't think I've seen any issues with a viewer being created like that.
I'm on a 2019 Macbook Pro, OSx 14.4.1, and Chrome 126.0.6478.127
I think the canvas issues are more of an artifact of the screen capture, since I'm not noticing them in the browser.
We had originally run into this in scenarios where a user was in a virtualized environment, but noticed the same behavior happens locally as well when you toggle the functionality off in the browser.

Interesting. I'm on a 2021 Macbook Pro (M1 chip), OSx 13.3 Ventura, Chrome 126.0.6478.127 (Official Build) (arm64).
When I disable graphics acceleration through Chrome, canvasElement.getContext( 'webgl' ) returns null.

I'm on a 2021 Macbook Pro (M1 chip), OSx 13.3 Ventura, Chrome 126.0.6478.127 (Official Build) (arm64).
When I disable graphics acceleration through Chrome, canvasElement.getContext( 'webgl' ) returns null.

Firefox, on the same computer/OS, is able to use the webgl drawer and it has no issues - no glitches like you're seeing. Perhaps there's something specific to Chrome's implementation on CPU on your setup? Does Firefox with hardware acceleration disabled work for you by any chance?

Yeah, Firefox w/o hardware acceleration will both instantiate a viewer and doesn't appear to be showing the render issues.

Yeah, Firefox w/o hardware acceleration will both instantiate a viewer and doesn't appear to be showing the render issues.

Seems to me this is likely to be an issue outside of scope of the WebGLDrawer implementation then... do you agree? Of course, if there's a way to help it work on more platforms we could think about making a change, but I don't even know where to start.

Yeah I agree.  Thank you for talking through it with me!


[Loc] update to arc and azcli xlfs

This PR fixes #

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.008%) to 42.207%

Totals

Change from base Build<PHONE_NUMBER>:
0.008%

Covered Lines:
27757

Relevant Lines:
61529

💛  - Coveralls


x轴文字过长，rotate 会使文字被截断

[ ] I have searched the issues of this repository and believe that this is not a duplicate.

Reproduction link
https://stackblitz.com/edit/react-awjd1d?file=index.js
Steps to reproduce
https://stackblitz.com/edit/react-awjd1d?file=index.js

Environment
Info

f2
4.0.28

System
-

Browser
-

需要手动调整 padding，这边没办法自动调整哈。
<Canvas context={context} pixelRatio={window.devicePixelRatio} theme={{
padding: 20
}}>


sub-generators for creating services and components

@Stefku can be closed. Please add this to the release-notes page in confluence.


log errors when component modules error out

this will log errors when component modules error out (and the error isn't just that the module cannot be found)
this fixes most of the issues we've had with eaten logs
note: this won't log when a component module requires another module that doesn't exist (but it will log if that other module exists but throws a different error)
trello ticket

👍


cmd buffer output not being cleared

When you exec a command, :w for example, you get a message to tell you if its been successful or not, or not recognised.
This message persists even when using the space in the UI, for example performing a search:

I think this can be closed after commit e3f8cb0, yes?

I think this can be closed after commit e3f8cb0, yes?

Yeah.


Possibility to logout if server cannot be reached.

Hi @Teifun2,
First off, thanks for all the work you've done on this project. Fantastic app!
Offline support would be fantastic; however, this is a slightly different request. I noticed when my phone has no internet / data connectivity the app just starts into a perpetual 'loading' screen, with no way to change options or settings it seem without uninstalling and re-installing the app.
This is a bit of a niche use case, but I currently have my app set to a LAN only Nextcloud service, but would like to change it to an internet enabled Nextcloud service -- and potentially even switch back and forth as needed. Aside from my niche use case, I think it would generally be a helpful addition to the app to have multi-account support or at least access a settings menu, even with no offline support yet.
Thanks!

Hello @arsocha
Thanks for your feedback. I have a few questions!

the app just starts into a perpetual 'loading' screen, with no way to change options or settings it seem without uninstalling and re-installing the app.

Does this mean even after you gained internet / data you cannot check your recipes without reinstalling? Or is it more if your nextcloud server is down and you want to switch to another this is not possible due to the perpetual loading screen?

I think it would generally be a helpful addition to the app to have multi-account support or at least access a settings menu, even with no offline support yet.

Multi Account support is definitively something i considered, and want to do at some point. But offline use will be first for sure.
What would you want to have in the settings menu? (Settings menu is already developed but not yet released should come soon with the first settings)

Thanks for the reply @Teifun2!
To try and clarify for your questions:

The second version is the case! When I have internet (+ obviously access to the nextcloud instance) I can check my recipes again. The issue for me was my nextcloud instance was inaccessible (by design, because I was testing it on an instance that was only setup for a local, non-internet nextcloud deployment) but when I wanted to try and switch to another remotely accessible instance I couldn't because of the perpetual loading screen.

Great to hear offline is still in the works, very much looking forward to it. As far as features in a settings menu, really the only major item for me would just be the ability to see / set / re-set the associated nextcloud user credentials (at least prior to loading). I am excited to see what you are working on else wise in a settings menu, but happy to wait and see on that rather than making preemptive comments!

Thanks!

The second version is the case! When I have internet (+ obviously access to the nextcloud instance) I can check my recipes again. The issue for me was my nextcloud instance was inaccessible (by design, because I was testing it on an instance that was only setup for a local, non-internet nextcloud deployment) but when I wanted to try and switch to another remotely accessible instance I couldn't because of the perpetual loading screen.

This is indeed a problem. I will mark this issue as a bug to track this issue.
For part to i will add a Feature Request to track the Multi Account Feature.
Thanks for your involvemement!

Thanks again for reviewing my concern. Appreciate all you are doing on this project.

Delivered with 0.7.5

@Teifun2 thanks for all your work on this!


[docs] Update way of getting driver for testbox

@azhogov I know that it needs more details in this documentation but it needs to start conversation about how we build media-driver and mdf!


Down command

Hello! Is there any ETA for adding the down and stop subcommands? It becomes very tedious to stop the containers manually.

@chrmarti
Hello! Thank you for all your hard work. I believe that the feature I am thinking of would greatly benefit CLI users.
I was wondering if your project is open to pull request submissions? If so, I would love to implement this feature as my contribution to the amazing work you have done. My team and I have greatly benefited from the devcontainer OSS and I would like to reciprocate by contributing to the project.

Hi @yokonao, thanks! Happy to learn the CLI is useful to you. We are indeed open to pull requests. Thank you.

Workaround while we wait for devcontainer down to be released:

https://github.com/devcontainers/ci/issues/207#issuecomment-1672566863

I don't understand why the README in this repo lists the stop & down commands when they don't actually exist yet.

They are not checked in the readme, so I don't think it is misleading.

@IgnisDa ah, I totally didn't even see the checkboxes, might be related to the GitHub dark theme making them harder to see. Still seems like there isn't much value in having it the README. 🤷🏼♂

Here's the checkbox contrast issue mentioned above. I just spent a lot of time thinking that I was on an old version of the CLI because this appeared to show a list that was fully complete (or fully incomplete).

For others looking for this feature, I've actually stopped using this CLI in favor of using the DevPod CLI, which actually has a stop and delete command implemented.
The only catch with using the DevPod CLI/ap is that it implements SSH as the means for getting into the running Dev Container. There is also a desktop UI/app if desired.
I find it way more feature complete and flexible than this CLI. Additionally, the DevPod CLI doesn't require a local NodeJS installed to use.
https://devpod.sh/

Thanks for this recommendation @timnolte! Have you found devpod implements the spec closely enough that users could swap between devpod/vscode/other implementations easily enough?

Thanks all for the discussion! We'd absolutely welcome a PR to contribute these commands. Additionally, our understanding is DevPod leverages our specification (https://containers.dev/supporting#devpod), so if anyone from / working with DevPod would be similarly interested in contributing down and stop here, that'd be fantastic!

Guessing the mechanism for tracking a matching devcontainer exists to some degree given remove-existing-container
https://github.com/devcontainers/cli/blob/9ba1fdaa11dee087b142d33e4ac13c5788392e34/src/spec-node/devContainersSpecCLI.ts#L119
https://github.com/devcontainers/cli/blob/9ba1fdaa11dee087b142d33e4ac13c5788392e34/src/spec-node/singleContainer.ts#L293-L307


feat(worker/mastodon): make mastodon worker revision and add federated api modification

Summary

Added target URLs to post metadata
Fixed missing related URLs and author URLs in activity actions
Added media and type information to comments
Fixed issues with the federated API service (platform/{platform}) by adding federated api functions

Checklist

[ ] The commit message follows Angular Contributing guidelines;
[x] Tests for the changes have been added (for bug fixes / features);

Does this PR introduce a breaking change?

[x] Yes
[ ] No

Other information

API Call:
/federated/tx/{id}
Request:
curl "http://localhost:80/federated/tx/https://mastodon.social/users/jplebreton/statuses/113306326859367213/activity" \
     -H 'Authorization: Bearer test'

Response:
{
  "data": {
    "id": "https://mastodon.social/users/jplebreton/statuses/113306326859367213/activity",
    "owner": "<EMAIL_ADDRESS>    "network": "mastodon",
    "index": 0,
    "from": "<EMAIL_ADDRESS>    "to": "<EMAIL_ADDRESS>    "tag": "social",
    "type": "comment",
    "platform": "Mastodon",
    "total_actions": 1,
    "actions": [
      {
        "tag": "social",
        "type": "comment",
        "platform": "Mastodon",
        "from": "<EMAIL_ADDRESS>        "to": "<EMAIL_ADDRESS>        "metadata": {
          "handle": "<EMAIL_ADDRESS>          "body": "@ dante ( https://masto.posting.haus/@dante ) i did a random wikipedia delve-crawl on the byzantine empire yesterday and i was pretty struck by how artificial it would be to identify with that empire, through its various dissolutions and contractions - it was so many different things over those centuries. the US has been an unbroken (incl one very major civil war obvs) line of power since 1776, but i still feel similarly about it - US patriotism forces people to accept the bad with the good, and so much evil flows from that.",
          "publication_id": "113306326859367213",
          "tags": ["<EMAIL_ADDRESS>          "author_url": "https://mastodon.social/users/jplebreton",
          "timestamp":<PHONE_NUMBER>,
          "target": {
            "handle": "<EMAIL_ADDRESS>            "body": "even in the longest possible understanding, america is young as fuck, and nothing is guaranteed, and maybe it ends tomorrow, and maybe Something Will Happen and things will change dramatically. i can't see the future and neither can you.\n\nthere's a reason why my comfort in troubled times is history, because it puts things in perspective. 600 years into the byzantine empire, things were going Quite Bad. and then they got a bit better! and then they got bad again. all on the scale of lifetimes",
            "publication_id": "113304460895615833",
            "author_url": "https://masto.posting.haus/users/dante",
            "timestamp":<PHONE_NUMBER>
          },
          "target_url": "https://masto.posting.haus/users/dante/statuses/113304460895615833"
        },
        "related_urls": [
          "https://mastodon.social/users/jplebreton/statuses/113306326859367213"
        ]
      }
    ],
    "direction": "in",
    "success": true,
    "timestamp":<PHONE_NUMBER>
  },
  "meta": {
    "totalPages": 1
  }
}

API Call:
/federated/{account}
Request:
curl "http://localhost:80/federated/<EMAIL_ADDRESS>\
     -H 'Authorization: Bearer test'

Response:
{
  "data": [
    {
      "id": "https://mamot.fr/users/matiu_bidule/statuses/113306325867326800/activity",
      "owner": "<EMAIL_ADDRESS>      "network": "mastodon",
      "index": 0,
      "from": "<EMAIL_ADDRESS>      "to": "<EMAIL_ADDRESS>      "tag": "social",
      "type": "comment",
      "platform": "Mastodon",
      "total_actions": 1,
      "actions": [
        {
          "tag": "social",
          "type": "comment",
          "platform": "Mastodon",
          "from": "<EMAIL_ADDRESS>          "to": "<EMAIL_ADDRESS>          "metadata": {
            "handle": "<EMAIL_ADDRESS>            "body": "@ Khrys ( https://mamot.fr/@Khrys )",
            "media": [
              {
                "address": "https://static.mamot.fr/media_attachments/files/113/306/320/849/250/165/original/ea979dc1488abd7a.png",
                "mime_type": "image/png"
              }
            ],
            "publication_id": "113306325867326800",
            "tags": ["@Khrys"],
            "author_url": "https://mamot.fr/users/matiu_bidule",
            "timestamp":<PHONE_NUMBER>,
            "target": {
              "handle": "<EMAIL_ADDRESS>              "publication_id": "113306276701697373",
              "author_url": "https://mamot.fr/users/Khrys"
            },
            "target_url": "https://mamot.fr/users/Khrys/statuses/113306276701697373"
          },
          "related_urls": [
            "https://mamot.fr/users/matiu_bidule/statuses/113306325867326800"
          ]
        }
      ],
      "direction": "out",
      "success": true,
      "timestamp":<PHONE_NUMBER>
    }
  ]
}

API Call:
/federated/platform/{platform}
Request:
curl "http://localhost:80/federated/platform/Mastodon?limit=1" \
     -H 'Authorization: Bearer test'

Response:
{
  "data": [
    {
      "id": "https://mstdn.social/users/TheRaDR/statuses/113306338661194276/activity",
      "owner": "<EMAIL_ADDRESS>      "network": "mastodon",
      "index": 0,
      "from": "<EMAIL_ADDRESS>      "to": "<EMAIL_ADDRESS>      "tag": "social",
      "type": "comment",
      "platform": "Mastodon",
      "total_actions": 1,
      "actions": [
        {
          "tag": "social",
          "type": "comment",
          "platform": "Mastodon",
          "from": "<EMAIL_ADDRESS>          "to": "<EMAIL_ADDRESS>          "metadata": {
            "handle": "<EMAIL_ADDRESS>            "body": "In order to move forward, we must make sense of where we've been. How else can we make sense of whatever will happen next—and our reactions to it? (3/5)",
            "publication_id": "113306338661194276",
            "author_url": "https://mstdn.social/users/TheRaDR",
            "timestamp":<PHONE_NUMBER>,
            "target": {
              "handle": "<EMAIL_ADDRESS>              "publication_id": "113306337622998525",
              "author_url": "https://mstdn.social/users/TheRaDR"
            },
            "target_url": "https://mstdn.social/users/TheRaDR/statuses/113306337622998525"
          },
          "related_urls": [
            "https://mstdn.social/users/TheRaDR/statuses/113306338661194276"
          ]
        }
      ],
      "direction": "self",
      "success": true,
      "timestamp":<PHONE_NUMBER>
    }
  ],
  "meta": {
    "cursor": "https://mstdn.social/users/TheRaDR/statuses/113306338661194276/activity:mastodon"
  }
}

API Call: /federated/network/{network}
Request:
curl "http://localhost:80/federated/network/Mastodon?limit=1" \
     -H 'Authorization: Bearer test'

Response:
{
  "data": [
    {
      "id": "https://mstdn.social/users/TheRaDR/statuses/113306338661194276/activity",
      "owner": "<EMAIL_ADDRESS>      "network": "mastodon",
      "index": 0,
      "from": "<EMAIL_ADDRESS>      "to": "<EMAIL_ADDRESS>      "tag": "social",
      "type": "comment",
      "platform": "Mastodon",
      "total_actions": 1,
      "actions": [
        {
          "tag": "social",
          "type": "comment",
          "platform": "Mastodon",
          "from": "<EMAIL_ADDRESS>          "to": "<EMAIL_ADDRESS>          "metadata": {
            "handle": "<EMAIL_ADDRESS>            "body": "In order to move forward, we must make sense of where we've been. How else can we make sense of whatever will happen next—and our reactions to it? (3/5)",
            "publication_id": "113306338661194276",
            "author_url": "https://mstdn.social/users/TheRaDR",
            "timestamp":<PHONE_NUMBER>,
            "target": {
              "handle": "<EMAIL_ADDRESS>              "publication_id": "113306337622998525",
              "author_url": "https://mstdn.social/users/TheRaDR"
            },
            "target_url": "https://mstdn.social/users/TheRaDR/statuses/113306337622998525"
          },
          "related_urls": [
            "https://mstdn.social/users/TheRaDR/statuses/113306338661194276"
          ]
        }
      ],
      "direction": "self",
      "success": true,
      "timestamp":<PHONE_NUMBER>
    }
  ],
  "meta": {
    "cursor": "https://mstdn.social/users/TheRaDR/statuses/113306338661194276/activity:mastodon"
  }
}

Comment Note Object with media in the action target:
{
          "id": "https://social.timespiral.co.jp/users/find575/statuses/113287741759175713/activity",
          "network": "mastodon",
          "index": 0,
          "from": "<EMAIL_ADDRESS>          "to": "<EMAIL_ADDRESS>          "tag": "social",
          "type": "comment",
          "platform": "Mastodon",
          "total_actions": 1,
          "actions": [
            {
              "tag": "social",
              "type": "comment",
              "platform": "Mastodon",
              "from": "<EMAIL_ADDRESS>              "to": "<EMAIL_ADDRESS>              "metadata": {
                "handle": "<EMAIL_ADDRESS>                "body": "@ cs133 ( https://pawoo.net/@cs133 ) 俳句を発見しました！\n『各駅に エスペラントで 愛称が』",
                "publication_id": "113287741759175713",
                "timestamp":<PHONE_NUMBER>,
                "target": {
                  "handle": "<EMAIL_ADDRESS>                  "body": "Y por si se les pasó, les dejamos también la pieza que nos mandó Lola Matamala contándonos en primera persona el desahucio que sufrió su madre el mes pasado después de llevar setenta años viviendo en la misma calle.\n\nLa empresa Dapamali Works compró el edifio y fue echando uno por uno a todos los vecinos:\n\nhttps:// ctxt.es/es/20241001/Firmas/476 02/lola-matamala-desahucio-Dapamali-Works-primera-persona-aurora-getafe.htm ( https://ctxt.es/es/20241001/Firmas/47602/lola-matamala-desahucio-Dapamali-Works-primera-persona-aurora-getafe.htm )",
                  "media": [
                    {
                      "address": "https://s3.eu-central-2.wasabisys.com/mastodonworld/media_attachments/files/113/287/758/697/714/115/original/2c6c341deae150c0.jpg",
                      "mime_type": "Document"
                    }
                  ],
                  "publication_id": "113287758853959995",
                  "timestamp":<PHONE_NUMBER>
                },
                "target_url": "https://mastodon.world/users/ctxt/statuses/113287758853959995"
              },
              "related_urls": [
                "https://social.timespiral.co.jp/users/find575/statuses/113287741759175713"
              ]
            }
          ],
          "success": true,
          "timestamp":<PHONE_NUMBER>
}


Incorrect Link for Azure Monitor VM's

Under the Sub Heading "Insights" the link attached to the text "Azure Monitor for VMs" is incorrect.
Its pointing to the "https://docs.microsoft.com/en-us/azure/azure-monitor/insights/container-insights-overview" whereas the correct link should be "https://docs.microsoft.com/en-us/azure/azure-monitor/insights/vminsights-overview".
Screenshot showing the same is attached below.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: a592ccdb-4c92-7da9-aeb3-e93cf8cb3512
Version Independent ID: 5ac6b940-88e9-fd5b-98fa-f46eb2cc9758
Content: What is monitored by Azure Monitor - Azure Monitor
Content Source: articles/azure-monitor/monitor-reference.md
Service: azure-monitor
Sub-service: ****
GitHub Login: @bwren
Microsoft Alias: bwren

@binoyjt
Thanks for your feedback! We will investigate and update as appropriate.

@binoyjt thanks! I made a pull request to update this. https://github.com/MicrosoftDocs/azure-docs-pr/pull/117963


Godot loses Input events on Android

Godot version:
3.2.4-beta3
OS/device including version:
Xiaomi - Redmi Note 9
Android 10
Issue description:
Wen pressing a touch button fast, other control nodes loses input. Is expected that the digital analog doesn't loses input.
This bug has been introduced on 3.2.4-beta2, previous versions work OK (beta1 and stable).
In beta-2 happens sometimes (I thought I was doing something wrong), but in beta-3 is really noticeable.
Steps to reproduce:
Export project to Android.
Drag the digital analog on the blue zone and spam fast one of the other buttons, the analog will lose control as if you stooped touching the screen, doesn't matter if you drag the finger across the screen.
Minimal reproduction project:
VirtualAnalog.zip

Related? https://github.com/godotengine/godot/pull/43907

Related? #43907


Better handling of multiple identities and new script for vurderingsportalen

(Sorry about the commit mess, but as you can see from the changed files it's really quite simple.)

Awesome, merged!


Flutter.dev is down

Site can't be reached.

Can't reproduce the error anymore, so I assume this issue can be closed now.

Close this issue as the flutter.dev is working fine now.


fix(ios): multiple onPageSelected calling

Summary
Closes #454
onPageSelected fires for every page in between the range.
Test Plan
https://user-images.githubusercontent.com/12766071/135571785-ab307ee7-18a3-4eda-8d53-9be45c64ffe1.mov

OS
Implemented

iOS
✅

Android
❌

cc: @mikeqcp

https://github.com/callstack/react-native-pager-view/releases/tag/v5.4.6


UTF-8 warning during installation via gem install

When installing tetra via gem I got the following warning:
$ gem install tetra
Fetching tetra-2.0.6.gem
Successfully installed tetra-2.0.6
Parsing documentation for tetra-2.0.6
unable to convert "\xEB" from ASCII-8BIT to UTF-8 for lib/template/bundled/apache-ant-1.9.7/KEYS, skipping
unable to convert "\xAE" from ASCII-8BIT to UTF-8 for lib/template/bundled/apache-ant-1.9.7/LICENSE, skipping
Installing ri documentation for tetra-2.0.6
Done installing documentation for tetra after 0 seconds
1 gem installed

Occurred on openSUSE Tumbleweed with the zsh shell and Ruby version 2.5.9 installed via rvm.

I did some investigation and was not able to find a solution for fixing this, yet.

This comes from the bundlesd Ant version we use. Updating it, did not help. Since this is no real issue, I will close it.


#No issue-Created Cards and Footer With Mock Data- HASEEB_KHALIL

This includes All Mock Data which is being displayed in cards and footer. It should be replaced with real data once database is ready.
Naming Rules
Name your PR like this: ISSUENUMBER-TITLE-YOURNAME
Description
Write a summary of your change. Explain why you have made it.
Just created cards and footer using Mock Data.
Related to
Make sure you include the issue number with a hash sign # so Github can link this PR to the right issue, like this:
Fixes #1
Checklist:

[ * ] My code follows the style guidelines of this project
[ * ] I have carefully reviewed my own code
[ * ] I have commented my code
[ * ] I have updated any documentation

Looking good. You will need to resolve the merge conflict in server/db.js first - https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line


Indexing of duplicated diagrams out of step

This is a severe bug and should be fixed as soon as possible.
Say there are 3 diagrams, ids 0, 1, 2
delete middle diagram to get ids 0, 2
then clicking on right hand diagram does not find id 1, and 'loading ...' indefinitely
duplicate new diagram will result in ids 0, 2, 1
then clicking on middle diagram will edit id 1, not 2

Attached file shows this problem: test-ids.json.zip
Created by adding four diagrams, and then deleting the second one


Cursor return to Barcode field

When barcoding, it's often necessary to switch between different fields in the app. Currently, this requires alternating between using the mouse, the keyboard, and then the mouse again, or pressing the tab key 3 to 8 times to return to the barcode field. I propose that after following actions the cursor should automatically return to the barcode field:

Choosing a MSO/MOS
Entering the species name
Checking off the specimen/label obscured box

This change would not only save time and increase efficiency, but also reduce errors, as we almost always need to return to the barcode field after performing any of the aforementioned actions.

This issue have earlier been reported as a bug in ticket #498

Why was this issue closed on the same day it was opened??

that is a mistake :)

Alright :)
Waiting for feedback from @PipBrewer or @bhsi-snm

It was agreed at the digitiser meeting on 12/11/2024 that this is an issue that all digitisers agree on. In the herbarium, things like obscured labels or MSOs are common and it would be useful that when anything is selected in the app, that the cursor immediately goes to the barcode field afterwards.
It is agreed that this would be annoying at the beginning of a session, but the digitisers said that they think that this would still be worth it.
We have not yet asked collections managers who use the workflow their opinion yet and we need to before we go ahead with this. I have added this to the next herbarium and pinned insect monthly meeting tickets.
In the meantime, @FedorSteeman do you have any idea how this might work? If you click on a radio button, would it ever skip straight to barcode field or would this only work for certain types of fields?

I think we could add a radiobutton for "workflow mode" which has a default position for the current mode and a "fast" position for the fast, skippy mode suggested here. Then at the beginning of your session you can set it to "fast" position if you want to, otherwise the behaviour would be default. We could even make this an app setting that is persisted to the next session.
I'd need to know if this should be a radio button pair, representing the two different modes, or a single one representing "fast" mode. And I'd need to know placement and captions.

@FedorSteeman thank you for this. Question: is this complicated and time consuming to do?

In the meantime, this is a mock up with two radio buttons near the top (on  the left), for discussion. Have posted in Digitiser channel in slack and will add comments here once I have collated them.


added very simple test (with sample PCAP) for CVE-2021-38647

This PR just adds a very simple btest test which will be checked by zkg on installation.

thank you Seth


aligning non-image layers

This PR should address #42
I just changed two lines - converting the input layer types to the more general napari.layers.Layer instead of napari.layers.Image. It seems to have worked.
Image to shape affine transform
https://user-images.githubusercontent.com/54516770/151113341-4f5185e9-ba83-4344-961b-04d29346c14f.mp4
Image to image transform (is preserved)
https://user-images.githubusercontent.com/54516770/151113418-b21b5c1d-27b6-4c74-aea4-c9353140cdd9.mp4
Note that I'm not actually trying to match anything in these examples! So they look weird. But the affine makes the expected distortions to the moving image.

Should I add tests to this? I feel like I must have missed something here...

Thanks @thanushipeiris! I'll merge as soon as tests pass.
Ideally we would update the tests to include testing different layer type combinations, but, given #46 changes the tests and still needs to be merged, I suggest we do that after that gets merged. I'll create a new issue for it.


Thanos cant query from object store

Thanos, Prometheus and Golang version used:
Kubernetes, sidecar in kube prom stack chart
And thanos bitnami chart

Object Storage Provider:
Ceph
What happened:
we are facing an issue with Thanos that it can't query after a certain date even though the side car are pushing metrics until current date but in the Thanos front end I can see the object store has a max time of 2024-02-18
I tried thanos tools bucket verify it didnt show any issue
Logs for sidecar, compactor, storegateway didnt include anything that seems an issue
What you expected to happen:
I cant query up to date
How to reproduce it (as minimally and precisely as possible):
Full logs to relevant components:

Anything else we need to know:

One thing to mention, the bucket size is now 2T
When i do thanos tools bucket inspect i can only see from 2023-09-12 to 2024-02-08

Is your issue cannot query object store or cannot query object store with latest timestamp?

I can see the object store has a max time of 2024-02-18

So your expectation is to see max time of now?
It doesn't sound like an issue of store gateway itself. There is a metric in sidecar for lastest timestamp of uploaded block.

We have similar issue, we can only see metrics that are only 11 days old. And that time is moving every hour. Sidecar is pushing wal files without issues and I can see the oldest wal file is from 03.2024 but when I'm trying to view any metric from grafana or directly from thanos-query I can see the data not older then 11 days. We have exactly the same setup as described above.

@mesiu84 It might be an issue of your compactor retention. Can you share how you configure your compactor retention time?

  enabled: true
  retentionResolutionRaw: 1y
  retentionResolution5m: 1y
  retentionResolution1h: 2y```
this is what we have

I'll just add that when I added --min-time to thanos store command it doesn't fix the issue, that was mentioned somewhere above

We have similar issue, we can only see metrics that are only 11 days old

It would be good to get more details about what you meant of only 11d old metrics. Were queries timing out or queries returned fine but only 11d metrics showed up.
Store Gateway has a built-in UI where it shows loaded blocks of the store gateway. Can you share what it looks like? Is store gateway able to load blocks older than 11 days

Found what was the issue, by mistake Thanos Query was reading data from different S3 bucket then the one used by Sidecar to push the data, after updating the settings all data is visable

@TheCodingSheikh I suspect your problem is more an issue of getting data into your S3, rather than querying your metrics from S3. I will close the issue now. Feel free to reopen if you have any question

One thing to mention, the bucket size is now 2T
When i do thanos tools bucket inspect i can only see from 2023-09-12 to 2024-02-08


Fixing another unstable codepath that can result in a NPE.

Also logging stacktrace for exceptions.
Not sure why https://jenkins.ci.cloudbees.com/job/plugins/job/performance-plugin/212/ had unstable tests, then https://jenkins.ci.cloudbees.com/job/plugins/job/performance-plugin/213/ that ran right after was fine. All tests pass locally.

Thanks for working on this!


Updated descriptions to match the current version syntax requirements

Fix for https://github.com/clastix/cluster-api-control-plane-provider-kamaji/issues/64

Commit lint is complaining, may I ask you to amend the message?
Something as fix(docs): updated description to match the current version syntax requirements


[SPARK-14312] [ML] [SparkR] NaiveBayes model persistence in SparkR

What changes were proposed in this pull request?
SparkR NaiveBayesModel supports save/load by the following API:
df <- createDataFrame(sqlContext, infert)
model <- naiveBayes(education ~ ., df, laplace = 0)
ml.save(model, path)
model2 <- ml.load(path)

How was this patch tested?
Add unit tests.
cc @mengxr

Test build #56528 has started for PR 12573 at commit eb3c9ca.

Test build #56528 has finished for PR 12573 at commit eb3c9ca.

This patch fails to build.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/56528/
Test FAILed.

Test build #56552 has started for PR 12573 at commit c1df7d2.

Test build #56552 has finished for PR 12573 at commit c1df7d2.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/56552/
Test PASSed.

Merged build finished. Test PASSed.

Made one pass and left some minor comments inline.

Test build #56646 has started for PR 12573 at commit 8c7d612.

Test build #56646 has finished for PR 12573 at commit 8c7d612.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/56646/
Test PASSed.

@yanboliang I left two minor comments. I don't know why GitHub folds them by default. Please take a look. LGTM otherwise.

Test build #56845 has started for PR 12573 at commit ac42a0a.

Test build #56845 has finished for PR 12573 at commit ac42a0a.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/56845/
Test PASSed.

Merged into master. Thanks!


Fix keypath test.

The only subscripts we have in this test return A or A?, but this
expression without the subscript would result in a Prop? which I think
was intended here.

@jckarter This looks like a test problem rather than a type checker problem. I took a guess at what you intended here.

@swift-ci Please smoke test

My intent was to include the [sub] subscript with the proper type. Do both variations work? Doesn't hurt to have more tests.

Okay, I'll push a new version with both tests, the test with [sub] resolving to A? instead of Prop?.

@swift-ci Please smoke test and merge

@swift-ci Please smoke test

Thanks!


Reference and Blocks cannot be loaded after staticpkg

Describe the bug
After staticpkg, the Reference and Blocks options under the Help menu in the Editor do not work properly. The "open in new tab" link of each option opens http://host/docs/docs/reference.html and http://host/docs/docs/blocks.html respectively. The "docs" is duplicated.
To Reproduce
Steps to reproduce the behavior:

Run pxt staticpkg in a pxt target
Serve the folder of the packaged files in a webserver and open it in browser using HTTP
Open a project in Makecode
Select Reference or Blocks in the Help menu (the "?")

Expected behavior
The reference or blocks info should be displayed
Screenshots

I am seeing this in the Electron app too, looks like this is a recent regression


Using the MustGet helper, it is not possible to solve dependency injection for a pointer

With the Injector construct, if using the Get operations, this can be achieved.

The MustGet is now properly handling generic types of kind pointer.


SQL Functions created with vsts agent account

We use the 'Run SQL Scripts" deployment task. We have some SQL that drops and creates some functions within the SQL script. The function gets created with vsts agent account.function vs. dbo.function. When the function is referenced later in the SQL script as dbo.funciton, it cannot be located and the SQL deploy fails. Have you seen this in the past? We try executing this SQL inside management studio and it gets created with dbo.function.

Not seen that before. Have you tried watching what is happening with profiler when the build task is running? I would check to see if any SQL exceptions are happening during the deployment.

The account that VSTS is using, how is the security set up in SQL Server?  It should have a default schema and it probably is not set to dbo.
Alternatively, does the object in the Sql Database project have the dbo prefix for the name?  This would force the schema regardless of the users default schema.  I find this to be the better practice.

Is this still an issue?


feat(package): Move nsp check from prepare step to an optional script.

prepare will now output a message telling the user how to run nsp.

fixes #85

Coverage remained the same at 96.667% when pulling c0d6a8e8e84d98047c7179f043a7d726288e5104 on lholmquist:85-nsp-change into 5264b201ca12088f3725f58bdab5ccb485aa90ad on bucharest-gold:master.


[FEATURE] Improving Snowcat error messages

The current error messages by Snowcat refer to the type signatures, which are internal to the mechanics of Snowcat. As correctly pointed out in  #955, these messages are hard to understand.
On one hand, the type checker itself is unaware of the actual TLA+ operators, as it is working over EtcExpr. As a result, the type checker relies on the generic error reporting:
https://github.com/informalsystems/apalache/blob/dec42b8ba2ada9c8c306d320fe731f8a4787dcb9/tla-types/src/main/scala/at/forsyte/apalache/tla/typecheck/etc/EtcTypeChecker.scala#L148-L154
On the other hand, ToEtcExpr is in the best position to explain error messages. We could add an optional callback to EtcExpr that receives the inferred types of the arguments (as in the general callback) and explains the mismatch. Then, the general callback in EtcTypeChecker could call the specialized callback, if it is defined.
I think the best course of action is to evaluate error messages by adding a few specialized callbacks in ToEtcExpr and, if it works well, adding callbacks to all the cases. @gabrielamafra what do you think about this?

I'm not sure I understand your proposal. ToEtcExpr and EtcTypeChecker are two entire different runs that are not connected by callbacks or anything else, I'm struggling to see how we cold connect them with callbacks.
Looking at the implementation, my idea to allow expression information to be used on type error reporting is to keep a map from expression ID to the original expression (similar to sourceStore) to be used by EtcExpr in EtcTypeChecker error callback, but this seems to deviate from your idea. I wonder if I'm missing something from your suggestion.

Source tracking is not an issue. EtcExpr is carrying sourceRef that is pointing to the source id.
What we are lacking is a user-friendly explanation that refers to the semantics of a particular operator. For instance, we have this translation in ToExpr:
https://github.com/informalsystems/apalache/blob/8a0a392f823d50f0d3575d921efb632ae2c412ee/tla-types/src/main/scala/at/forsyte/apalache/tla/typecheck/etc/ToEtcExpr.scala#L209-L213
We could introduce an optional callback in EtcExpr, which EtcTypeChecker would call, e.g., here:
https://github.com/informalsystems/apalache/blob/8a0a392f823d50f0d3575d921efb632ae2c412ee/tla-types/src/main/scala/at/forsyte/apalache/tla/typecheck/etc/EtcTypeChecker.scala#L135-L141
The callback for the equality operator could look like:
def explainArgsMatchError(sig: OperT1, argTypes: Seq[TlaType1]): String = {
  "Equality expected two arguments of equal types, found: " + String.join(" and ", argTypes.map(_.toString))
}

We could attach the callback in ToEtcExpr like this:
mkExRefApp(opsig, args).setOnArgsMatchError(explainArgsMatchError)

This is all very schematic and it probably requires more thinking, but this is basically the idea. Not sure how much drop in the performance it would incur though.

I see. I thought the intention was to have explanations specific to the original TLA expression form, but seems like just using more of the ETC information can be sufficient. I'll try that, thanks!

oh, right. Mentioning the original expression would be perfect but that would require some serious rework of error reporting. It is somehow planned in #943.

@gabrielamafra  has noted that this issue can be refactored into a milestone and smaller issues.

After some exploration, I've break this down into two rather big issues with a more specific description of what to do from what we learned in this initial exploration. They are

https://github.com/informalsystems/apalache/issues/1581
https://github.com/informalsystems/apalache/issues/1582

If it makes sense, the tasks on the second issue can be turned into issues once we are executing them.
I'll close this in favor of the more specific issues just created.


added some concurrent calling we can use

Note: removed previous hello_world examples since they are not needed anymore.
Routers

renamed /docs endpoint to /single_doc so we can use the former for our main endpoint later.
added some error handling

Services
Clients

Moved clients to their own folder.
added some error handling to github_client.py.
added optional API Key use to github_client.py. This is really only necessary if we go past GitHub's API rate limit of 60 requests per hour.

Documentation Service

generate_doc_for_github_file is now async.
new private method _run_concurrently will run a list of async functions concurrently (at the same time, a.k.a. in parallel).

this is how we can generate docs for multiple files at the same time, cutting down on the time it takes to document an entire repo.

Looks great👍
for the naming, I am not sure what we are thinking each of the resources means
so like is it:
/single_doc for single file documentation
/docs for entire repo documentation
?
maybe we could rework to
/file_doc
/repo_docs
or something similar to make it more clear? i dont know the best practice to follow here

Looks great👍
for the naming, I am not sure what we are thinking each of the resources means
so like is it: /single_doc for single file documentation /docs for entire repo documentation ?
maybe we could rework to /file_doc /repo_docs
or something similar to make it more clear? i dont know the best practice to follow here

Completely agree. Will change it to /file-doc for now. Let's meet and map out our resources and their names. Here is some general conventions: https://restfulapi.net/resource-naming/


Add CRUD operations for IVAs (GSI-647)

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

267 of 328 (81.4%)  changed or added relevant lines in 26 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-1.9%) to 91.248%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/auth_service/user_management/user_registry/deps.py
7
8
87.5%

src/auth_service/user_management/user_registry/ports/dao.py
8
9
88.89%

src/auth_service/user_management/user_registry/ports/registry.py
37
46
80.43%

src/auth_service/user_management/user_registry/router.py
41
52
78.85%

src/auth_service/user_management/user_registry/core/registry.py
93
132
70.45%

Files with Coverage Reduction
New Missed Lines
%

src/auth_service/user_management/user_registry/router.py
1
83.81%

Totals

Change from base Build<PHONE_NUMBER>:
-1.9%

Covered Lines:
1616

Relevant Lines:
1771

💛  - Coveralls


RequestTable skip list can be replaced by ArrayRingBuffer (#138)

Please take a look here: I'm not sure if the constrains I'm enforcing here are ok although all tests are passing.
The ring buffer is lazily initialized in order to cover for the reload (on crash) use case (and test): if a ring buffer with head == 1 is used regardless what's the expected index range, committing won't be able to deque from the last added entry and would fail to remove its request.

I get 15 failures when applying this PR: run ant all-tests reports to see them. I'll look into this later, need to understand ArrayRingBuffer first. I'll probably go through ArrayRingBufferTest to see how it works

Another not on ring-buffer: given that it accept gaps (unless the user check that it won't happen), size is not the actual number of non-null elements, but just the number of slots occupied (with elements + gaps).
I can implement it differently to help matching the actual content

I don't think that elements will be appended with gaps, but I think a (more) natural semantics for size() would be the actual non-null elements.

I don't think that elements will be appended with gaps, but I think a (more) natural semantics for size() would be the actual non-null elements.

We can do in 2 different ways:

if the array buffer doesn't allow gaps ever, the size can be as simple as it is now
if the array buffer allow gaps, size/set/add/remove need to be a bit more complicated to count number of gaps added/removed

I think the former is a better option TBH, but I don't know if it matches the other ring buffer usage (LogCache); any idea?

I think a major problem is that RequestTable.isCommitted(idx) (calling ArrayRingBuffer.get(index)) throws an exception when idx > tailSequence. However, my code at [1] probes until it finds an uncommitted entry. So, instead of throwing an exception, isCommitted() should return false when finding an entry that's null. IMO, ArrayRingBuffer.get() should return null if an element is not found (same semantics as the skiplist map used before)...
[1] https://github.com/belaban/jgroups-raft/blob/master/src/org/jgroups/protocols/raft/RAFT.java#L713

IMO, ArrayRingBuffer needs to have the same exact semantics as ConcurrentSkipListMap, so replacement is simple. If you want a get() that throws an exception, I suggest introduce an additional validatingGet(). However, I don't think this is needed

With a (stupid :-)) change such as the one below, all tests PASS:
 public boolean isCommitted(int index) {
        if (requests == null) {
            return false;
        }
        if (index < requests.getHeadSequence()) {
            return true;
        }

        Entry<?> entry = null;

        try {
            entry=requests.get(index);
        }
        catch(Throwable t) {

        }
        return entry != null && entry.committed;
    }

@belaban right now there's a contains that help checking against head/tail boundaries and perform the get: I didn't throw exception so far on get with null element(s) because you won't get any exception by getting a null element from a map (either)

@belaban try checking requests::contains before the get

Hmm... you're changing semantics in a couple of places, e.g.  in RequestTable.notifyAndRemove(), you're expecting the first element to be removed, otherwise you throw an exception.
This is not the semantics I used to have in RequestTable, and I expect this to break code I have in mind when notifying client via stream().parallel()...

OK, so here's what I'll do: I'll change the code regarding RequestTable in this PR, but leave the code in ArrayRingBuffer as is, for future changes. OK?

I changed RequestTable, but also had to add a remove() to ArrayRingBuffer. I'll commit, so we can have the discussion on the latter on a separate (new?) issue. Note that ArrayRingBuffer.size() still needs to be implemented, I'll create a new issue


vid2pose.py: No module named 'src'

Traceback (most recent call last):
File "E:\AI\Moore-AnimateAnyone\tools\vid2pose.py", line 1, in
from src.dwpose import DWposeDetector
ModuleNotFoundError: No module named 'src'

Just run the shell command export PYTHONPATH=$(pwd) under the root directory.

thanks for you help. I have solved it under Win11:

thank you


provide some way (environment?) to determine if inside a stacker

Our make system is aware of stacker, and will do some things (like write a stacker config) before invoking stacker.
The makefile gets invoked both inside and outside of stacker.
I'd like to have some logic that says "if you're already inside stacker, then you don't need to write a stacker config".
Can we provide some way to allow figure out if you're inside a stacker environment or not ?
maybe something like: STACKER_ENVIRONMENT=the_layer_name
I'd get that right now with the following, but i'd like to not have to define my own STACKER_ENVIRONMENT in the build_env.
my_builder:
  from:
    type: docker
    ...
  build_env: {"STACKER_ENVIRONMENT": "my_builder"}
  run: |
    echo hi world. you are in ${STACKER_ENVIRONMENT}
  build_only: true

56eaf93c0b870535373e339679a4356dab373f4c makes it so that STACKER_STACKER_DIR & friends are all exported; is that enough or do you want something more explicit?

hm... I don't think anything there is automatic though, right?  You can reference it in the stacker config but I'd have to explicity do that.
I was hoping that this would "just work":
my_builder:
  from: ...
  run: |
    echo "you are in the stacker environment ${STACKER_ENVIRONMENT}"

What do you mean exactly? It should work just fine,
/tmp/foo sudo stacker build
preparing image my_builder...
loading docker://centos:latest
Getting image source signatures
Copying blob 6910e5a164f7 [--------------------------------------] 0.0b / 0.0b
Copying config 53dc94ba7c done
Writing manifest to image destination
Storing signatures
cache miss because layer definition was changed
+ echo stacker dir /tmp/foo/.stacker
stacker dir /tmp/foo/.stacker
generating layer for my_builder
filesystem my_builder built successfully
/tmp/foo cat stacker.yaml
my_builder:
    from:
        type: docker
        url: docker://centos:latest
    run: |
        echo stacker dir "${{STACKER_STACKER_DIR}}"

So you could do
if [ -z "${{STACKER_STACKER_DIR}}" ]; then
    # write stacker config
fi

right?

oh. i see.
I don't love it.  I'd rather the environment variable just be there rather than requiring replacement of text.


Idea: Add a mode for stages to display as a rotation

In some games, such as Splatoon, the stages (and modes) are set before the match begins

Screenshot from The Squid House Splatoon 2 invitational tournament
As a user, I would like to be able to set up a stage rotation in TSH, alongside a way to annotate the different picks in the rotation (In the example above, this would be used to indicate the game mode) and a way to report which player/team won on which stage

Update: Given that Splatoon 3 now separates game modes in the stage list I don't think annotations for game modes are needed anymore


Create composer.json

Added the composer.json to be able to install the library via the Composer package manager.

Hello, would it be possible to add this file? It would make installations via the PHP Package Manager, "Composer", a lot easier.
See https://getcomposer.org

Short bump to check if this could be added? Thanks a bundle!


Use service-worker to fetch only JSON pages.

We simply don't need to proxy other requests through service workers.
That's might cause some latency issues.

@nkzawa check now.


fix typo: startegy -> strategy

Hej. There is newer version on master. Can you please resolve conflicts and i will merge ))


/bin/sh: pytest: command not found when running evaluations

Describe the bug
Running evaluations on 1 issue of the swe bench lite devset pydicom__pydicom-1256 and looking at the logs this is what I see:
>>>>> Applied Patch (test)
Test Script: . /tmp/sweet/testbed/sweet/pydicom/2.1/tmpydsw8v9j/miniconda3/bin/activate pydicom__pydicom__2.1 && echo 'activate successful' && pytest --no-header -rA --tb=no -p no:cacheprovider pydicom/tests/test_json.py;
[pydicom__pydicom__2.1] [pydicom__pydicom-1256] Command: . /tmp/sweet/testbed/sweet/pydicom/2.1/tmpydsw8v9j/miniconda3/bin/activate pydicom__pydicom__2.1 && echo 'activate successful' && pytest --no-header -rA --tb=no -p no:cacheprovider pydicom/tests/test_json.py
[pydicom__pydicom__2.1] [pydicom__pydicom-1256] Subprocess args: {"check": false, "shell": true, "capture_output": false, "text": true, "env": {"CONDA_PKGS_DIRS": "/tmp/sweet/testbed/sweet/pydicom/2.1/tmpydsw8v9j/miniconda3/cache"}, "stdout": -1, "stderr": -2, "timeout": 900}
[pydicom__pydicom__2.1] [pydicom__pydicom-1256] Std. Output:
activate successful
/bin/sh: pytest: command not found

[pydicom__pydicom__2.1] [pydicom__pydicom-1256] Return Code: 127

>>>>> Some Tests Failed
[pydicom__pydicom__2.1] [pydicom__pydicom-1256] Test script run successful

Shouldn't pytest be present in the repo environment?
 Fresh clone of the repo and fresh conda install.
Expected Results
I would expect pytest to be in the repo venv.
Actual Results

Applied Patch (test)
Test Script: . /tmp/sweet/testbed/sweet/pydicom/2.1/tmpydsw8v9j/miniconda3/bin/activate pydicom__pydicom__2.1 && echo 'activate successful' && pytest --no-header -rA --tb=no -p no:cacheprovider pydicom/tests/test_json.py;
[pydicom__pydicom__2.1] [pydicom__pydicom-1256] Command: . /tmp/sweet/testbed/sweet/pydicom/2.1/tmpydsw8v9j/miniconda3/bin/activate pydicom__pydicom__2.1 && echo 'activate successful' && pytest --no-header -rA --tb=no -p no:cacheprovider pydicom/tests/test_json.py
[pydicom__pydicom__2.1] [pydicom__pydicom-1256] Subprocess args: {"check": false, "shell": true, "capture_output": false, "text": true, "env": {"CONDA_PKGS_DIRS": "/tmp/sweet/testbed/sweet/pydicom/2.1/tmpydsw8v9j/miniconda3/cache"}, "stdout": -1, "stderr": -2, "timeout": 900}
[pydicom__pydicom__2.1] [pydicom__pydicom-1256] Std. Output:
activate successful
/bin/sh: pytest: command not found

[pydicom__pydicom__2.1] [pydicom__pydicom-1256] Return Code: 127

Some Tests Failed
[pydicom__pydicom__2.1] [pydicom__pydicom-1256] Test script run successful

System Information
MacOS ARM
Fresh conda, fresh clone

My dirty workaround to get further has been to edit context_manager.py
self.cmd_activate = (
            f". {os.path.join(self.conda_path, 'bin', 'activate')} "
            + f"{self.venv} && echo 'activate successful' && pip install pytest"
        )

The installation specifications for Pydicom are fully included here.
Based on our validation of the pydicom__pydicom-1256 instance, as shown here, it didn't seem like it was necessary for pytest to be explicitly installed.
The base commit for the instance is here. I believe that the pip install -e . instruction specified here should have taken care of installing pytest automatically, but I will double check this.

Marking this as completed, hope the original comment helped with this!
I checked the pydicom installations, the validation logs are under the validation/ folder in SWE-bench/experiments. I was able to confirm that the explicit pytest installation should not be necessary. With that said, it doesn't hurt to install it again, so I merged #134 which should take care of this.
We are also going to come out with a new SWE-bench evaluation harness within the next 2 weeks, which incorporates Docker containers into the evaluation process. It should resolve a lot of the inconsistencies that are arising from running SWE-bench evaluation on different machines. If you're still interested in working on SWE-bench, definitely look out for the release! 😄


Improved OpenVPN parser

@rohithasrk: check my improvements in 4ebfb69

Coverage remained the same at 100.0% when pulling 4ebfb69cd6af931d78e49d7639804da66bfa858f on openvpn into 90e5eaca5e6df77004a2ee60c352d8fc79ca3707 on master.

thx @rohithasrk, I'll merge now.