ADD: objects can override is_dict_like()

By setting obj._xarray_dict_like_, any object obj can now tell xarray to treat it like it is (or is not) a dict. Note: objects without the _xarray_dict_like_ attribute will be unaffected; this change is fully backwards-compatible.
There are no relevant issue reports, tests added, user visible changes, or new functions / methods.
This is my first contribution to xarray, I tried my best to follow the contribution guidelines; please let me know if I am missing anything essential!
Motivation
I have been using xarray in my personal project pretty successfully (xarray is a great package, and I am very grateful for it)! However, I sometimes use dict-like objects as coordinates. xarray seems to be okay with this most of the time, but fails when it comes to things like the DataArray.sel method. I would really like to be able to use sel, since my dict-like objects are only dict-like for reasons completely unrelated to xarray.
For example, I built a PlasmaFluid class which stores information about different fluids. And, I use instances of that class as coordinates for my DataArray. E.g.:
import xarray as xr
import mypackage
f0 = mypackage.PlasmaFluid(0, 'e-', q=-1, density=1e10)     # fluid composed of electrons
f1 = mypackage.PlasmaFluid(1, 'H neutral', q=0, density=1e14)     # fluid composed of neutral hydrogen
f2 = mypackage.PlasmaFluid(2, 'p', q=1, density=1e10)     # fluid composed of protons
# fluids can have many parameters, including charge, mass, density, and more.
#   so, each PlasmaFluid object has a .keys() method which tells the parameters,
#   and a __getitem__ method to get the values. E.g.:
f0['q']     # -1
f0['density']     # 1e10
# xarray seems happy enough to allow PlasmaFluid objects to be used as coordinates, e.g.:
u_x = xr.DataArray([2, 7, 3], coords=dict(fluid=[f0, f1, f2]))
density = xr.DataArray([f0['density'], f1['density'], f2['density']], coords=dict(fluid=[f0, f1, f2]))
momentum_density_x = density * u_x   # == xr.DataArray([2e10, 7e14, 3e10], coords=dict(fluid=[f0, f1, f2]))

This code works just fine, and produces a nicely-labeled DataArray, where the fluid dimension contains the actual PlasmaFluid objects, e.g. u_x.isel(fluid=0) is f0.
However, it fails when I try to use the sel method, e.g.:
u_x.sel(fluid=f1)
# --> ValueError: cannot use a dict-like object for selection on a dimension that does not have a MultiIndex

After implementing the change in this PR, I am able to avoid this issue, and can use the sel method by updating the class I wrote to include PlasmaFluid._xarray_dict_like_ = False.

Thanks for the PR.
I don't have a strong view but one quick question — could you instead implement the methods that get checked on the custom object?

Thanks for the PR.
I don't have a strong view but one quick question — could you instead implement the methods that get checked on the custom object?

Thanks for your response. I had considered that, but unfortunately the is_dict_like function before my changes only checks for the existence of attributes. The code previously looked like:
def is_dict_like(value: Any) -> TypeGuard[Mapping]:
    return hasattr(value, "keys") and hasattr(value, "__getitem__")

Ideally I would like a solution that allows me to keep the keys and __getitem__ method in my PlasmaFluid class (and other similar classes I've written), since those classes store a bunch of different parameters' values, and IMO the most natural way to do that is with a dictionary-like object.

Ah I see, thanks.

I wonder if we could alternatively check that doesn't have Hashable implemented. So if you implemented Hashable, then xarray would not see it as dict-like.
The downside is that something like https://pypi.org/project/frozendict/ — which is Hashable — won't work to lookup on MultiIndexes.

Ideally I think we should avoid these sorts of custom attributes — they make xarray's implementation more complicated, increase the cardinality of its interface. And often this sort of issue is emblematic of a deeper issue — should we be doing something quite different depending on the type of the argument / is there a more lower-level API even if .sel tries to be helpful by guessing?
On the lower-level API point — does the equivalent of da.loc[dict(space='IA')] work?

FYI @Sevans711 one thing that would be useful here is a reproducible example, with a minimal class that has those methods.

I don't see a reason why we could not simply remove this check (I didn't look at the code, possibly requires some refactoring).
This would solve the issue at hand and for other use cases raise a more low level error (I assume).
Just a note: @Sevans711 are you sure you want to build your code like this? You are giving away lots of the power of xarray by using this approach. It would be much more intuitive (and faster!) if you would use the Plasma fluid properties directly as coordinates.

another option would be to wrap the value you're looking for in a 0D array with object dtype (so instead of u_x.sel(fluid=f1) try u_x.sel(fluid=np.array(f1, dtype=object)).
In general I agree, though, this is a pretty un-idiomatic use of xarray.

Thank you all for your comments. Replying to the various points you made:
@max-sixty

I wouldn't want to affect frozendict's interaction with xarray, that seems not ideal, mostly because I don't understand exactly how MultiIndexes are used here and whether frozendict should work with them or not. If the is_dict_like check added any check other than hasattr for a few attrs, I would be happy; it definitely doesn't need to be the check I proposed with this PR. I am mostly looking for some way to tell xarray it's okay to use PlasmaFluid (and similar classes) in sel (and similar methods).
I agree maybe my solution is not the best one, I appreciate your suggestions and would be happy for a different solution to be implemented. Maybe a bigger change is a good idea, but I didn't want to poke around too much without understanding what it might break. Regarding da.loc, it produces the same error message for me; e.g. arr.loc(dict(fluid=f2)) crashes just like arr.sel(dict(fluid=f2)).
edited the original message to include a reproducible example, thank you for this recommendation!

@headtr1ck

I also don't understand why we need the check, though I did get the impression it is there to help prevent mistakes for people who are intending to use MultiIndexes, but input them incorrectly. I wouldn't want to make changes which lead to a hard-to-understand error or unexpected behavior, for those people.
I appreciate your concern for the way I built the code, but I am pretty sure it is how I want it to be. There have been numerous benefits, including some unexpected benefits, which signals "good object oriented programming" to me. I don't want to discuss it too much here but some examples include:

My code accepts multiple different kinds of data input, where each kind has its own quirks. E.g., PlasmaFluidKind1 only knows about charge and mass, while PlasmaFluidKind2 knows about charge, mass, and 12+ other parameters. By using the PlasmaFluid objects as coordinates, my arrays look the same regardless of the kind of input.
fluid is not the only array dimension; there are other important coordinates too, and for better readability I would prefer the arrays to not be flooded with lots of fluid-related coordinates.
I implemented PlasmaFluid.__str__, so the coordinates appear as easy-to-read strings such as ('e-', 'H', 'p'). xarray includes the array type (object) to help hint that they aren't actually strings.
When I expand the coordinates via the clickable stack-thing in Jupyter, I see the __repr__ showing PlasmaFluidKind1(...) (or PlasmaFluidKind2), so I can easily tell what kind of data this array came from.

I didn't realize it would be faster to use fluid properties directly as coordinates. I suspect it isn't important in my use-case (my arrays usually have a few fluids but >500x500 points along x&y coordinates which are floats), but I could check by profiling the code. Would you be willing to explain when / why it would be faster to avoid object coordinates?

@keewis

Thank you for letting me know this trick. Indeed, wrapping the value in a numpy array does work, and numpy is even smart enough to figure out it should use dtype=object without me explicitly specifying it. E.g., u_x.sel(fluid=np.array(f1)) works too! This is a good workaround in the meantime, while this PR is still being discussed.

Just to throw out some ideas, the data you're describing seems like a particularly well fit for awkward, a library for ragged arrays (basically, "arrays of structs") which was built with high-energy physics in mind. Over the past month, @jpivarski, one of the maintainers of awkward, has also been working on ragged, a library that describes the subset of awkward that xarray can wrap (see #7988).

Just to throw out some ideas, the data you're describing seems like a particularly well fit for awkward, a library for ragged arrays (basically, "arrays of structs") which was built with high-energy physics in mind. Over the past month, @jpivarski, one of the maintainers of awkward, has also been working on ragged, a library that describes the subset of awkward that xarray can wrap (see #7988).

Thanks for pointing this out, I didn't know about this! I will continue to consider it, though I don't know if it is the best fit for me. To clarify my use-case: all my data is homogeneous, of the same type and with no holes or variable-length lists. I believe the only thing I'm doing that doesn't quite follow the usual patterns is using objects for coordinates, instead of a simple type like int/float/str. There's no reason my data couldn't work with numpy, but I'm using xarray to make it easier to track all the coordinates and dimensions :)

If all of the objects are fixed-size data structures (i.e. all instances in the array have the same set of named fields), then Awkward Array would be overkill. Looking at PlasmaFluid with parameters q and m (assuming that they're always q and m, for a given array), then what you really have is a two-tier structure to your coordinate names, right?
Such a thing could be implemented as records within records, but it could also be represented as nested columns, like using Pandas's MultiIndex on column names, like
>>> pd.DataFrame(
...     data=[[1, 1.1, "one"], [2, 2.2, "two"], [3, 3.3, "three"]],
...     columns=pd.MultiIndex.from_tuples([("a1", "x"), ("a1", "y"), ("a2", "z")])
... )
  a1          a2
   x    y      z
0  1  1.1    one
1  2  2.2    two
2  3  3.3  three

In xarray, would xarray-datatree work?
On the other hand, maybe I've misunderstood and only the i field of PlasmaFluid is relevant for indexing. In that case, maybe just make the class interpretable as an integer index?
class PlasmaFluid:
    ...
    def __index__(self):    # or maybe __int__
        return self.i

On the other hand, maybe I've misunderstood and only the i field of PlasmaFluid is relevant for indexing. In that case, maybe just make the class interpretable as an integer index?

This is correct, only the i field is relevant for indexing. I see why it was confusing, it is due to somewhat poorly-chosen examples on my part. In general, I can have lots of other fluids too with the same mass and/or charge (e.g. PlasmaFluid(3, 'He+', q=1), PlasmaFluid(4, 'C+', q=1)). But, every fluid should be assigned a unique integer, so I can unambiguously refer to it.
It is a good idea to implement __int__ or __index__, and in fact I have already done that (in the same way you suggested), and some parts of my code utilize that to convert PlasmaFluid objects to integers. However, even when using either method (__index__ or __int__), I get the same error when I try to use sel.
What are your thoughts on having the is_dict_like() check return False for objects with an __index__ method? This is similar to @max-sixty's idea, but maybe less likely to cause conflicts. I am guessing that __index__-able dict-like objects are far less common than Hashable dict-like objects. I would also think that anyone using a dict-like object with __index__ shouldn't complain if that object is not treated like a dictionary when it comes to DataArray.sel, which relates to indexing.

I want to briefly mention another benefit of including the PlasmaFluid objects as coordinates, maybe it will be more convincing than my other examples:

Consider a function plot_with_fluid_info(array) which will make one plot per fluid in the array, and in each plot add a textbox containing PlasmaFluid.get_plot_info(). PlasmaFluid subclasses can control what goes onto plots, by overriding this method. In this way, my plotting code can be exactly the same for each kind of input, but the plots can contain relevant info specific to the kind of input I'm plotting.
Consider any number of other analysis routines which also take one array as input, yet want access to the corresponding PlasmaFluid objects and methods therein. By using PlasmaFluid as coordinates, I don't need to pass more info into these functions; they can read the info directly from the array.
This behavior would be difficult to replicate if I insist on using the properties of PlasmaFluids as coordinates instead of the PlasmaFluids themselves.

Seems like the general request is to allow indexing of object-type arrays with objects.
Can we just skip the check if the dimension being indexed is backed by an object dtype array?

Can we just skip the check if the dimension being indexed is backed by an object dtype array?

This seems worth trying. I'm not sure exactly how multiindexes will work, but if tests pass it's probably fine...

I'm not exactly sure, but I believe @benbovy has been working on making MultiIndexes less of a special case, and by doing so I believe we'd be removing the special casing for dict objects as well. Can you confirm that, @benbovy?

Yes I think we can safely remove this special case now.
Selection on both single and multi-indexes used to be handled internally through the same function that was supporting only dimension coordinate indexers. This is not the case anymore.

Awesome!
If this will be getting fixed imminently and sometime in the not-too-distant future (maybe within a few months?) I am happy to wait. I suspect it would be much less work for someone who is more familiar with the codebase than me. However if you need me to attempt to remove this special case please let me know, and I'll see what I can do.


Programming exercises: Build Plan API

Checklist
General

[ ] I tested all changes and their related features with all corresponding user types on a test server.
[ ] This is a small issue that I tested locally and was confirmed by another developer on a test server.
[x] Language: I followed the guidelines for inclusive, diversity-sensitive, and appreciative language.
[x] I chose a title conforming to the naming conventions for pull requests.

Server

[x] I followed the coding and design guidelines.
[x] I added multiple integration tests (Spring) related to the features (with a high test coverage).
[x] I added @PreAuthorize and checked the course groups for all new REST Calls (security).
[x] I implemented the changes with a good performance and prevented too many database calls.
[ ] I documented the Java code using JavaDoc style.

Changes affecting Programming Exercises

[ ] I tested all changes and their related features with all corresponding user types on Test Server 1 (Atlassian Suite).
[ ] I tested all changes and their related features with all corresponding user types on Test Server 2 (Jenkins and Gitlab).

Motivation and Context
In GitLab CI the build configuration can be an external URL (https://docs.gitlab.com/ee/ci/pipelines/settings.html#specify-a-custom-cicd-configuration-file). This PR adds the corresponding API endpoint to access the build plan for a programming exercise.
Description

Database change according to #5259
On creation of a programming exercise the corresponding template build plan is added to the exercise. In GitLab CI the URL to the new API endpoint is stored. For each execution of the CI the build plan is fetched from the API.

Steps for Testing
! Please test this PR locally !
Prerequisites:

Local GitLab instance with a Runner (See #4881 for setup)
MySQL database

Generate a personal access token with all scopes under http://localhost/-/profile/personal_access_tokens
Create application-local.yml and adapt the password and the access token

artemis:
    course-archives-path: ./exports/courses
    repo-clone-path: ./repos
    repo-download-clone-path: ./repos-download
    encryption-password: artemis_admin           # LEGACY: arbitrary password for encrypting database values
    bcrypt-salt-rounds: 11  # The number of salt rounds for the bcrypt password hashing. Lower numbers make it faster but more unsecure and vice versa.
    # Please use the bcrypt benchmark tool to determine the best number of rounds for your system. https://github.com/ls1intum/bcrypt-Benchmark
    user-management:
        use-external: false
        internal-admin:
            username: artemis_admin
            password: artemis_admin
        accept-terms: false
        login:
            account-name: TUM
    version-control:
        url: http://<IP_ADDRESS>:80
        user: root
        password: artemis_admin # Change here!
        token: artemis-gitlab-token # Change here!
    git:
        name: Artemis
        email<EMAIL_ADDRESS>server:
    port: 8080
    url: http://<IP_ADDRESS>:8080 # `http://host.docker.internal:8080` for Windows

Start Artemis with the gitlabci profile. Use Artemis (Server, GitLabCI & Gitlab) in IntelliJ.
Open Artemis in your browser and create a new course.
Generate a new programming exercise (with default configuration).
Open the template, solution and test repository. In the template and solution repository CI should be enabled and configured. Go to Settings > CI/CD > General Pipelines and open the URL from CI/CD configuration file. This should be one of the template build configurations (Java, Empty)
Create another exercise with the same programming language. Check in the database, that the build plan is stored only once and referenced by both exercises (SELECT p.id, p.build_plan_id FROM programming_exercise_details p; and SELECT * FROM build_plan;).
Push a change to the template or solution repository. Make sure GitLab CI successfully fetched the build plan from the API.

Review Progress

Code Review

[ ] Review 1
[ ] Review 2

Manual Tests

[ ] Test 1
[ ] Test 2

Test Coverage

Class/File
Branch
Line

@jpbernius @Mtze The PR is now ready for review.


[Proposal] Snabbdom V2

Snabbdom V2
This issue is a placeholder for some discussions about snabbdom v2.
Goals

20% perf improvement on the most common cases.
30% size reduction of the core library.
Provide extension point for custom comparison of vnodes.
Provide a way to normalize children collection in modules.
Clear separation between helpers and core lib.
Formalize hooks and modules workflow for the different type of vnodes.
Preserve module's API for backward compatibility.
Make shadowDOM and Fragments first class citizens to support web components.
Eliminate the ambiguious double exports.

Other changes

No more dist/ folder, users of this low-level library, users of it can bundle it at their will.
Perf infrastructure to measure incremental changes.
Improve test infrastructure.
Improve the overall contributing experience.

Details
1. Perf Improvements

Reduce string manipulation and string comparison during the critical path.
Reduce the amount of branches during the critical path.
Off-load part of the heavy lifting (vnode normalization) to the vnode creation.
Reduce type cohertion.

2. Size Reduction

Core lib does not need to know about the DOM or Elements at all.
Patch API reduced to only deal with normalized vnodes.
Eliminate unnecessary abstractions.

3. Custom Comparison
Using key and sel as a way to determine whether or not two vnodes are alike can still cover a lot of ground, but in some cases, users might want to apply a more restrictive mechanism to avoid recycling old vnodes. We should provide a way to define such comparison as an extension point.
4. Children collection could be normalized by modules
As today, the children reference is stored before invoking update or create hook, this makes it difficult for modules to do any kind of slotting or normalization of children without mutating the original children array, which is not ideal and goes against the principle of snabbdom of never mutating objects that it doesn't own.
A possible solution is to only extract the children value of the vnode after all modules are done with the update or create process.
5. Core vs Helpers vs Modules
This project contains the "core lib" whos job is to diff and patch, it also contains a default set of modules that covers most common cases for a DOM Element patching, and a set of helpers to pave the way for users to adopt snabbdom for the Web. This separation is not clear today, and should be very explicit in the next version. The proposed separation is:

Helpers: attachto, h, thunk, tovnode
Modules: same as today
Core: snabbdom plus the types defined in hooks and vnode

Additionally, I believe htmldomapi should be a helper too, and should be a required argument of the init method to keep the separation clear, while snabbdom can focused on the critical path only.
6. Formalizing workflow
As today, there are some arbitrary conditions to call certain hooks for certain types of vnodes, or certain type of data, these conditions seems arbitrary to the best of my knowledge, and I will like to formalize them. E.g.: vnodes with only a text will never go thru the create/destroy hooks. In some other cases, vnodes without data are not good for create/update.

I suggest introduce similar DOM APIs for modules too. For example, attributesapi for attributes module, styleapi for style module and so on.

@katyo , good day. I've thought the same and even liked this with :+1: .
But I have a new thought now: all Snabbdom is strongly DOM-oriented and DOM-specific. See: whole attributes module should be "interfaced" in this case. Even xlinkNS value. Or here.
Now I have a new thought: even remove htmldomapi! :)


Add command for importing address data.

What's this PR do?
This pull request adds a simple command to import the (already processed) address information from Mobile Commons from a script created by Sohaib. Since Blink has been having some trouble, we'll update these records directly on Customer.io.
References #152249269.
How should this be reviewed?
🚧
Checklist

[ ] Documentation added for changed endpoints.
[ ] Tests added for new features/bug fixes.
[ ] Post a message in #api if this includes something that causes a rebuild!

This should be safe to run on production once we've finished with #662. I'll triple check tomorrow, but the CSV provided by Sohaib should have exact addr_* values we want for each ID (based on the logic described in the Pivotal ticket), and we'll be providing that separately to the Customer.io folks so we don't need to make any API requests here.
One change I did have to make – I renamed addr_country to country in the CSV so it would match the Northstar field name. We should make this change in the original CSV we're handing off as well.


Add error handling for connection and login issues

thanks, I added proper error handling for most cases slighty different
let me know if you have any issues with it!


Multiple windows -> notifications are shown only in one

When multiple safari windows are open I only get notifications in one of them.

Fixed in 1.1.0. You might need to manually update (reinstall) it.


data_sources doesn not exist

Package Name:
Package Version:
Operating system:
[x] nodejs

version: v18.18.0

[ ] browser

name/version:

[x] typescript

version:

Is the bug related to documentation in

[x] README.md
[x] source code documentation
[x] SDK API docs on https://learn.microsoft.com

Describe the bug
When I try to following the example on https://www.npmjs.com/package/@azure/openai, to use my data on azure openai API
I got a error msg with my compiler
>npm list @azure/openai
<EMAIL_ADDRESS>/Users/billyli/github/rockychat
└──<EMAIL_ADDRESS>>npm list openai
<EMAIL_ADDRESS>/Users/billyli/github/rockychat
└──<EMAIL_ADDRESS>
'data_source' does not exist in type 'ChatCompletionCreateParamsNonStreaming'.
To Reproduce
Steps to reproduce the behavior:
1.
TSError: ⨯ Unable to compile TypeScript:
2024-08-20 15:11:41 src/commands/CommandHandler.ts(186,5): error TS2769: No overload matches this call.
2024-08-20 15:11:41   Overload 1 of 3, '(body: ChatCompletionCreateParamsNonStreaming, options?: RequestOptions<unknown> | undefined): APIPromise<ChatCompletion>', gave the following error.
2024-08-20 15:11:41     Object literal may only specify known properties, and 'data_source' does not exist in type 'ChatCompletionCreateParamsNonStreaming'.
2024-08-20 15:11:41   Overload 2 of 3, '(body: ChatCompletionCreateParamsStreaming, options?: RequestOptions<unknown> | undefined): APIPromise<Stream<ChatCompletionChunk>>', gave the following error.
2024-08-20 15:11:41     Object literal may only specify known properties, and 'data_source' does not exist in type 'ChatCompletionCreateParamsStreaming'.
2024-08-20 15:11:41   Overload 3 of 3, '(body: ChatCompletionCreateParamsBase, options?: RequestOptions<unknown> | undefined): APIPromise<ChatCompletion | Stream<...>>', gave the following error.
2024-08-20 15:11:41     Object literal may only specify known properties, and 'data_source' does not exist in type 'ChatCompletionCreateParamsBase'.

Expected behavior
A clear and concise description of what you expected to happen.
I can successfully use my data for Azure openai API endpoint
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.

Hi @w8896699 Thanks for reaching out! It should be data_sources, notice it is plural. Please let us know if you have any other questions!

data_sources

Hi @deyaaeldeen , thanks for your reply. Even I changed to data_sources, I am still getting the same error:
   Overload 1 of 3, '(body: ChatCompletionCreateParamsNonStreaming, options?: RequestOptions<unknown> | undefined): APIPromise<ChatCompletion>', gave the following error.
2024-08-21 09:12:49     Object literal may only specify known properties, and 'data_sources' does not exist in type 'ChatCompletionCreateParamsNonStreaming'.

@deyaaeldeen the issue still exist, could you please reopen the ticket?

Hi @w8896699 The object you have in the screenshot doesn't match the type and that is why you're getting a type error. You need to replace the key property with an authentication property defined as follows:
{
  type: 'api_key',
  key: 'searchKey'
}

Hi @deyaaeldeen, Thanks for your reply, I have tried your suggestion and still getting:
 Overload 1 of 3, '(body: ChatCompletionCreateParamsNonStreaming, options?: RequestOptions<unknown> | undefined): APIPromise<ChatCompletion>', gave the following error.
2024-08-21 11:23:41     Object literal may only specify known properties, and 'data_sources' does not exist in type 'ChatCompletionCreateParamsNonStreaming'.

I am using import { AzureOpenAI } from "openai";
and<EMAIL_ADDRESS>/Users/billyli/github/rockychat
└──<EMAIL_ADDRESS>

Could you share your code? Also, could you make sure you're importing @azure/openai similar to https://github.com/Azure/azure-sdk-for-js/blob/3caf49a8517b3a5cb73999556b13cb1eee554425/sdk/openai/openai/samples/v2-beta/typescript/src/onYourData.ts#L12?

I am not importing from @azure/openai, but from openai directly.
I am following this doc: https://www.npmjs.com/package/@azure/openai
Here's my code: https://github.com/bcgov/rockychat/pull/18/files#diff-b25dfa5bf9c6f67269056c57a97b937b23f02cdb784c3d21ba939b0e656e56ac.
You can find it under handleOpenAiCommand
If I use import { OpenAIClient, AzureKeyCredential } from "@azure/openai";.
I got error saying:
Module '"@azure/openai"' has no exported member 'OpenAIClient'.

npm list @azure/openai
<EMAIL_ADDRESS>/Users/billyli/github/rockychat
└──<EMAIL_ADDRESS>

You need to have  import "@azure/openai/types"; instead of import { OpenAIClient, AzureKeyCredential } from "@azure/openai";

can you give me docs or sample code snippets

Please checkout the complete sample in https://github.com/Azure/azure-sdk-for-js/blob/main/sdk/openai/openai/samples/v2-beta/typescript/src/onYourData.ts. If you were already using v1 before and in the process of migrating to v2, please checkout the migration guide.

I am trying to follow the sample there:
  const azureADTokenProvider = getBearerTokenProvider(new DefaultAzureCredential(), scope);
  const deployment = "gpt-4";
  const apiVersion = "2024-07-01-preview";
   const client = new AzureOpenAI({ azureADTokenProvider, deployment, apiVersion });
  const searchEndpoint = 'https://rockytest.search.windows.net'

  const result = await client.chat.completions.create({
    stream: true,
    messages: [
      {
        role: "user",
        content: query,
      },
    ],
    max_tokens: 128,
    model: "",
    data_sources: [
      {
        type: "azure_search",
        parameters: {
          endpoint: searchEndpoint,
          index_name: 'rockytest',
          authentication: {
            type: "system_assigned_managed_identity",
          },
        },
      },
    ],
  });

But still same error:
src/commands/CommandHandler.ts(49,48): error TS2769: No overload matches this call.
2024-08-21 15:57:10   Overload 1 of 3, '(body: ChatCompletionCreateParamsNonStreaming, options?: RequestOptions<unknown> | undefined): APIPromise<ChatCompletion>', gave the following error.
2024-08-21 15:57:10     Type 'true' is not assignable to type 'false'.
2024-08-21 15:57:10   Overload 2 of 3, '(body: ChatCompletionCreateParamsStreaming, options?: RequestOptions<unknown> | undefined): APIPromise<Stream<ChatCompletionChunk>>', gave the following error.
2024-08-21 15:57:10     Object literal may only specify known properties, and 'data_sources' does not exist in type 'ChatCompletionCreateParamsStreaming'.
2024-08-21 15:57:10   Overload 3 of 3, '(body: ChatCompletionCreateParamsBase, options?: RequestOptions<unknown> | undefined): APIPromise<ChatCompletion | Stream<...>>', gave the following error.
2024-08-21 15:57:10     Object literal may only specify known properties, and 'data_sources' does not exist in type 'ChatCompletionCreateParamsBase'.

I still believe its a SDK issue. I am not migrating from v1 to v2. this is a new project

@deyaaeldeen do you have any other suggestions what I should try?

@w8896699 did you make sure to include the `import "@azure/openai/types" at the top of this code module?

Yes, you can check my code here https://github.com/bcgov/rockychat/pull/18/files#diff-b25dfa5bf9c6f67269056c57a97b937b23f02cdb784c3d21ba939b0e656e56ac

@w8896699 tsconfig.json's module property is set to "commonjs", and @azure/openai is not compatible with it. You need to use a modern option such as "node16".

It works, Thanks

@deyaaeldeen do you know where to find docs to add those configuration into the data_source?

@w8896699 checkout the docs.


Split Binding class

Get the Binding class ready for the bidi protocol

Binding doesn't have a base class


Separate UI Kit Classes from chat project

Create chat_ui project
Move io.skygear.plugins.chat.ui classes into chat_ui project
Add bintray script
Update script/deploy.sh
Add :chat_ui:build into .travis.yml

Connects #81

@carmenlau  I sent a message to request bintray to include the package in jcenter, will update the PR after it is approved.

skygear-chat-android-uikit is now at jcenter. https://bintray.com/bintray/jcenter?filterByPkgName=skygear-chat-android

@carmenlau  please check and merge the PR, thx.

Thanks @howawong Can you also help updating the guides? Just similar to the ios version is fine.
https://docs.skygear.io/guides/chat/quick-start/android/
And how can I import the uikit from github? I imported it the chat sdk this way
compile 'com.github.skygeario:chat-sdk-android:master-SNAPSHOT'

thank you~!

compile 'io.skygear.plugins:chat_ui:1.1.3'
or
compile 'io.skygear.plugins:chat_ui:+'

I think jitpack remains unchanged. because in settings.gradle chat and chat_ui are included.

@howawong I tried using your commit in the demo app. Got dependeny error as follow, do i miss something?
Error:Conflict with dependency 'com.google.code.findbugs:jsr305' in project ':app'. Resolved versions for app (3.0.2) and test app (2.0.1) differ. See http://g.co/androidstudio/app-test-app-conflict for details.
Error:Module 'com.github.howawong-oursky:chat-sdk-android:4e2cef4' depends on one or more Android Libraries but is a jar

I changed the app chat dependencies like this
compile 'com.github.howawong-oursky:chat-sdk-android:4e2cef4'

I downgraded the minSDKVersion from 19 to 16 in chat_ui. Can you try again with 576754e ?

Just tried and still got the error :(
Error:Module 'com.github.howawong-oursky:chat-sdk-android:576754e' depends on one or more Android Libraries but is a jar

I think it is mixed with jcenter repo, can you try
compile 'com.github.howawong-oursky:chat-sdk-android: 576754e@aar'

Seems jitpack doesn't support @arr >"<
Error:Could not find chat-sdk-android.aar (com.github.howawong-oursky:chat-sdk-android:576754e).
Searched in the following locations:
    https://jitpack.io/com/github/howawong-oursky/chat-sdk-android/576754e/chat-sdk-android-576754e.aar

I just checked out a clean copy and with the following diff, and then I can build the demo. What version of gradle plugin and Android studio are you using?
diff --git a/app/build.gradle b/app/build.gradle
index b575e0f..dc446ce 100644
--- a/app/build.gradle
+++ b/app/build.gradle
@@ -25,7 +25,7 @@ dependencies {
         exclude group: 'com.android.support', module: 'support-annotations'
     })
     compile 'io.skygear:skygear:+'
-    compile 'io.skygear.plugins:chat:1.1.3'
+    compile 'com.github.howawong-oursky:chat-sdk-android:576754e'
     compile 'com.android.support:appcompat-v7:26.+'
     compile 'com.android.support.constraint:constraint-layout:1.0.2'
     compile 'com.android.support:design:26.+'
diff --git a/build.gradle b/build.gradle
index feae75e..7408a21 100644
--- a/build.gradle
+++ b/build.gradle
@@ -5,7 +5,7 @@ buildscript {
         jcenter()
     }
     dependencies {
-        classpath 'com.android.tools.build:gradle:2.3.3'
+        classpath 'com.android.tools.build:gradle:3.0.1'

         // NOTE: Do not place your application dependencies here; they belong
         // in the individual module build.gradle files
diff --git a/gradle/wrapper/gradle-wrapper.properties b/gradle/wrapper/gradle-wrapper.properties
index ef42fc6..9c36894 100644
--- a/gradle/wrapper/gradle-wrapper.properties
+++ b/gradle/wrapper/gradle-wrapper.properties
@@ -1,6 +1,6 @@
-#Mon Oct 16 15:21:30 HKT 2017
+#Fri Dec 15 17:31:26 HKT 2017
 distributionBase=GRADLE_USER_HOME
 distributionPath=wrapper/dists
 zipStoreBase=GRADLE_USER_HOME
 zipStorePath=wrapper/dists
-distributionUrl=https\://services.gradle.org/distributions/gradle-3.3-all.zip
+distributionUrl=https\://services.gradle.org/distributions/gradle-4.1-all.zip

My android studio is 3.0.1 and this is my project setting

Maybe let me also try check a clean copy

Mine is different from yours...

@howawong
I tired in gradle3.3, master branch ok, but seperate uikit branch has error
In gradle 4.4, both branches work great. After more check, it looks like jitpack problem to me that the aar link is not valid. As long as it works on jcenter i think it is ok. Do jcenter has alpha channel or support snapshot? So we can test

@carmenlau jcenter does not have any specific feature like this but I think uploading a binary naming it as 1.x.x-alpha is fine.

@howawong If we upload 1.x.x-alpha to jcenter, when user use compile 'io.skygear.plugins:chat:+' They will only get the stable release but not the alpha one? If so, maybe we could try submit alpha and do the test. :)

Continue at #123


chore: Publish v1.3.93 with swc_core v0.85.7

It looks like this version didn't include releasing<EMAIL_ADDRESS>is that on purpose and I'm misunderstanding the setup, or was there an error here?
I think this might be causing some errors with trying to use<EMAIL_ADDRESS>in StackBlitz.
https://github.com/swc-project/swc/actions/runs/6503658050/job/17664453856

@kdy1 Sorry for pinging you directly, but this seems to be a pressing issue, since stackblitz reproductions doesn't work anymore for Storybook, see e.g. https://github.com/storybookjs/storybook/issues/24567


Set a background color behind a video element.

Hello,
I would like to set a background color to a video tag element like this :
<video name="md_video">
         <pos>0.308 0.369</pos>
         <maxSize>0.2005 0.2680</maxSize>
         <delay>1.0</delay>
         <zIndex>44</zIndex>
         <color>000000</color>
</video>

But it seems the <color> feature isn't available for this element. So I think its an improvment, not a bug.
Why I'm looking for this feature ? On some vertical arcade games the video screen resolution doesn't overide properly the screenshot area of a mixed picture with screenshot+boxart+cartridge+marquee.
I did a video here to illustrate : https://www.youtube.com/watch?v=hh8kmRI7akk
You can see on the CRT screen, the screenshot picture overflows behind the video preview. And it's not really pretty.
I know the <showSnapshotNoVideo> tag to automatically swith between picture and video. But we can't recreate a full mixed picture with separated elements like using the <image name="md_marquee">. Because, it requires new media supports like : md_boxard, md_screenshot.
Kind regards.

In the video element, you can use  combined to  ( image, thumbnail, marquee -> image in you case ), it will solve your problem. You can also disable the bump effect using  set to "none".
You can also crop video using minSize instead of maxSize to "fill" the "TV"

Hello Fabrice,
Thank you so much for your reply.
I used this code to display my boxart picture.
<image name="md_thumbnail">
         <pos>0.1 0.1</pos>
         <maxSize>1 1</maxSize>
         <zIndex>42</zIndex>
</image>

Unfortunatly it shows me the "mix" picture. And I already use "md_image" image to display the "mix" picture.
I use ARRM to scrape media from ScreenScraper. It's the most powerfull and accurate tool I can found for now.
Here is the gamelist.xml format for games :
<game>
    <path>./1942.zip</path>
    <name>1942 (Revision B)</name>
    <desc>"1942" est le premier jeu d'une longue lignée d'avions américains bouffant du japonais, même si par la suite, les zéro devinrent des alliés dans les jeux suivant, combattant des ennemis non identifiés.
Assez difficile, je ne suis jamais allé très loin. J'ai tenté ma chance sur commodore 64, ce qui économisait quelques balles que je pus renvoyer à l'ennemi (hihihouhihouha le jeu de mots hé). bref, il est aujourd'hui assez vieillot. Je vous conseille donc de le télécharger pour l'histoire et de vous plonger plutôt sur "strikers 1945" qui bénéficie d'une dizaine d'années de savoir faire dans le domaine du shoot them up, largement tributaire de 1942.

</desc>
    <rating>4</rating>
    <releasedate>19840101T000000</releasedate>
    <developer>Capcom</developer>
    <publisher>Capcom</publisher>
    <genre>Shoot'em up / Vertical, Shoot'em Up</genre>
    <players>1-2</players>
    <image>./#snaps/1942_screenscraper_mix_arrm.png</image>
    <boxart>./#snaps/1942_screenscraper_boxart_arrm.png</boxart>
    <screenshot>./#snaps/1942_screenscraper_screenshot_arrm.png</screenshot>
    <marquee>./#snaps/1942_screenscraper_wheel_arrm.png</marquee>
    <video>./#records/1942_screenscraper_video_arrm.mp4</video>
    <mix>./#snaps/1942_screenscraper_mix_arrm.png</mix>
    <playcount>0</playcount>
    <lastplayed />
    <md5 />
    <region>wor</region>
  </game>

My current Batocera version is 5.24.
Do I need to upgrade softwares to link the "md_thumnnail" argument with the xml  tag as you explain ?
Is there an online doc about all new available options in EmulationStation's themes ? The most accurate ressource I was able to find is : https://github.com/RetroPie/EmulationStation/blob/master/THEMES.md


[Divider] Fix the build

[x] PR has tests / docs demo, and is linted.
[x] Commit and PR titles begin with [ComponentName], and are in imperative form: "[Component] Fix leaky abstraction".
[x] Description explains the issue / use-case resolved, and auto-closes the related issue(s) (http://tr.im/vFqem).

Finished 55 tests in 29027ms.
55 passes.
0 failures.


Deprecation warning in init.py

... pandas/pandas/init.py:12: DeprecationWarning: BaseException.message has been deprecated as
of Python 2.6
Shows up when I edit the code base with omnicompletion in vim.

Fixed in latest commit


Reconsider how to expose collections/connections

Per https://github.com/hapijs/discuss/issues/182#issuecomment-150984055

I'm torn!  Because DBs by definition contribute to application state, part of me would like to put the collections on server.app.collections and request.app.collections.  On the other hand, it's nice for plugins to not pollute the app namespace when they have their own namespace (as alluded to on https://github.com/hapijs/discuss/issues/182#issuecomment-155541308).  Anyone have thoughts?

Keeping it in the plugin namespace.


OBI with workshop-revised COB demo

This PR is a version of the OBI-COB transition that uses the revised version of COB that implements the decisions made during the workshop (OBOFoundry/COB#288). It is very similar to the previous OBI-COB demo PRs I've created, with a handful of cosmetic differences (e.g., COB:'molecular entity' is now COB:'molecule', so CHEBI:'molecular entity' was obsoleted and replaced with COB:'molecule'), plus a couple non-trivial differences/issues that will require some further decision-making.
Namely, some BFO terms that were previously in COB were not discussed/decided upon during the workshop, including BFO:0000016 "disposition", BFO:0000029 "site", and BFO:0000034 "function". These classes are not in the revised version of COB at present, so for the time being, these are all dangling classes in this PR. I haven't touched any of their uses. To restore some core functionality, we'll need to either (1) redirect all uses of these terms away from them, as we've done for other BFO terms that we knew weren't going in COB, or (2) place these three BFO classes in COB.

I think the dangling classes are fine for now, and that we should address
them as part of further COB work - we knew that we were skipping some
parts, and not having something in COB doesn't (yet) mean that it won't be.
On Fri, Nov 1, 2024 at 2:31 PM Sebastian Duesing @.***>
wrote:

This PR is a version of the OBI-COB transition that uses the revised
version of COB that implements the decisions made during the workshop (
OBOFoundry/COB#288 https://github.com/OBOFoundry/COB/pull/288). It is
very similar to the previous OBI-COB demo PRs I've created, with a handful
of cosmetic differences (e.g., COB:'molecular entity' is now
COB:'molecule', so CHEBI:'molecular entity' was obsoleted and replaced with
COB:'molecule'), plus a couple non-trivial differences/issues that will
require some further decision-making.
Namely, some BFO terms that were previously in COB were not
discussed/decided upon during the workshop, including BFO:0000016
"disposition", BFO:0000029 "site", and BFO:0000034 "function". These
classes are not in the revised version of COB at present, so for the time
being, these are all dangling classes in this PR. I haven't touched any of
their uses. To restore some core functionality, we'll need to either (1)
redirect all uses of these terms away from them, as we've done for other
BFO terms that we knew weren't going in COB, or (2) place these three BFO
classes in COB.
You can view, comment on, or merge this pull request online at:
https://github.com/obi-ontology/obi/pull/1834
Commit Summary

9c7986c
https://github.com/obi-ontology/obi/pull/1834/commits/9c7986ca48404068d3a0948136f2a99792e4142d
Replace OMO import with versioned OMO import
ced9b9a
https://github.com/obi-ontology/obi/pull/1834/commits/ced9b9a937501722fcd8c8345fcdee1aea61f7b2
Add OntoFox RO import and drop external-byhand
04389c2
https://github.com/obi-ontology/obi/pull/1834/commits/04389c235ae72c8ba1c3e56188a9ce7638b6b3d1
Prepare IAO import file
07bf569
https://github.com/obi-ontology/obi/pull/1834/commits/07bf5696fb51019507e039429fefc01a90f55964
Remove BFO import
972064d
https://github.com/obi-ontology/obi/pull/1834/commits/972064d4fab30d8eb569c70a2373572e53be86bc
Add import of revised COB
5245b12
https://github.com/obi-ontology/obi/pull/1834/commits/5245b129f75db9e0f9409d6cbf5f7930f51cfdaf
Relabel alternative term to alternative label in all templates
eb9e87f
https://github.com/obi-ontology/obi/pull/1834/commits/eb9e87f34b43a64c7cdc6d16b9fea0b6a5223317
Replace inheres in and bearer of with characteristic of and has
characteristic
5d7da15
https://github.com/obi-ontology/obi/pull/1834/commits/5d7da15c0a1455475f88be0e0531675c5f7ed7e9
Redirect CHEBI:atom references to COB:atom
b03f544
https://github.com/obi-ontology/obi/pull/1834/commits/b03f544d94f383b47ab00f94075ed326973d45e8
Redirect CHEBI:molecular entity references to COB:molecule
b79d55c
https://github.com/obi-ontology/obi/pull/1834/commits/b79d55ced54e51288a23ce51d84ecddd5f4283c4
Obsolete OBI:device and redirect to COB:device
97f0623
https://github.com/obi-ontology/obi/pull/1834/commits/97f0623a072dd05c6a4a08b1e3ee4f802fc2b399
Obsolete OBI:organism and redirect to COB:organism
13238a7
https://github.com/obi-ontology/obi/pull/1834/commits/13238a7a3d16b8be0b9f654ae00c2ecfb724513e
Obsolete OBI:planned process and redirect to COB:CEPP
e83988f
https://github.com/obi-ontology/obi/pull/1834/commits/e83988f9c74c051d6de3746ca76e547b6343f37c
Obsolete OBI:material processing and redirect to COB:material processing
30c60b3
https://github.com/obi-ontology/obi/pull/1834/commits/30c60b35ab9641a666c331d5ca123b9a333bc91e
Line order update to obi-edit by Protege
a850a9a
https://github.com/obi-ontology/obi/pull/1834/commits/a850a9ae1b549c4efea8e361807b872a9cdad91f
Remove BFO:0000001
fb3c0f0
https://github.com/obi-ontology/obi/pull/1834/commits/fb3c0f041bbe2555713468eb61ba4b2d8928cfe9
Remove BFO:0000002
0bae0fd
https://github.com/obi-ontology/obi/pull/1834/commits/0bae0fd683a2535d31f265c70f8093052490de23
Remove BFO:0000003
082607d
https://github.com/obi-ontology/obi/pull/1834/commits/082607df435b5f6af1ad810b9e7072a4dc640380
Remove BFO:0000004
4f065ec
https://github.com/obi-ontology/obi/pull/1834/commits/4f065ec557ce28c7ea0639bcbd14b9258dd46a03
Remove BFO:0000019
40478c2
https://github.com/obi-ontology/obi/pull/1834/commits/40478c2281ff47eecbc380aa07c50a02b346c99e
Remove BFO:0000020
ad9bb8a
https://github.com/obi-ontology/obi/pull/1834/commits/ad9bb8aec72c9a271a6109a27b5e32003575c981
Remove BFO:0000028
72981f0
https://github.com/obi-ontology/obi/pull/1834/commits/72981f0706f485eb9cb482e034f4c5e2a8d19c7e
Remove one usage of BFO:0000031
2850a17
https://github.com/obi-ontology/obi/pull/1834/commits/2850a1727cd3e384cb0d233b1d882bb883c6d4a4
Line order update by Protege
738995c
https://github.com/obi-ontology/obi/pull/1834/commits/738995c2dfcaa22ac8a4bd3aae8f232aac5578f6
Remove BFO:0000035
e840aac
https://github.com/obi-ontology/obi/pull/1834/commits/e840aac47ae939cdaad01924565fa0cd13893449
Fix duplicate labels
c9c6973
https://github.com/obi-ontology/obi/pull/1834/commits/c9c697386933c42275d81e8f13b7b68fdbeac4cd
Obsolete OBI:processed material and redirect to COB:processed material
entity

File Changes
(45 files https://github.com/obi-ontology/obi/pull/1834/files)

M src/ontology/OntoFox_inputs/ChEBI_input.txt
https://github.com/obi-ontology/obi/pull/1834/files#diff-0154000ac20ed7f828016761158e7f3637204396e3488f80e4f4c673b675e8e4
(190)
M src/ontology/OntoFox_inputs/IAO_input.txt
https://github.com/obi-ontology/obi/pull/1834/files#diff-7a8ce1d9e5e1f49a8236c13f5da5ca9d0d900ca32a1ea36da252f358f290c92a
(7)
M src/ontology/OntoFox_inputs/NCBITaxon_input.txt
https://github.com/obi-ontology/obi/pull/1834/files#diff-1ece8661815d51cff1b83b0c89ea6d60671b0dfb3ffe519b564a0d29217df91c
(8)
M src/ontology/OntoFox_inputs/OBA_input.txt
https://github.com/obi-ontology/obi/pull/1834/files#diff-e7da8571605b5765c6a7bea5bf41a35a56c1337c772c599cfcc5de86b12896b2
(2)
M src/ontology/OntoFox_inputs/OGMS_input.txt
https://github.com/obi-ontology/obi/pull/1834/files#diff-ca825d8a83116e01a838cce36bded1a5b3ec3eb64eb9c45c1b28942c8cc53090
(2)
M src/ontology/OntoFox_inputs/OPL_input.txt
https://github.com/obi-ontology/obi/pull/1834/files#diff-14f1014ed832d33041bf1f8c4f0fecd6626113a9a1bf4628f00f690453d272f7
(4)
M src/ontology/OntoFox_inputs/PATO_input.txt
https://github.com/obi-ontology/obi/pull/1834/files#diff-c212ed3cd4f9aad82fb7a3929d2802bb4ee449538e6a01ef00a51fd1b0b09db5
(4)
A src/ontology/OntoFox_inputs/RO_input.txt
https://github.com/obi-ontology/obi/pull/1834/files#diff-20dcf05945feca99be2eed04e7ecb63ead3c71a1e5507220a448188fe2e3c61e
(43)
M src/ontology/OntoFox_inputs/SO_input.txt
https://github.com/obi-ontology/obi/pull/1834/files#diff-ba2e1c017213bdb793b2034616835bb3255cffabeb85df7885450b9a853074ef
(4)
M src/ontology/OntoFox_outputs/ChEBI_imports.owl
https://github.com/obi-ontology/obi/pull/1834/files#diff-8d8f7ca40708034ae6e08942cd1aaf2a8ec132d5bfa1bbc5ca064663d7f677ca
(230)
M src/ontology/OntoFox_outputs/IAO_imports.owl
https://github.com/obi-ontology/obi/pull/1834/files#diff-13692bb1af789cc8f73065650d4300eca12deaf379491feab2df2c3da1ccb0a2
(134)
M src/ontology/OntoFox_outputs/NCBITaxon_imports.owl
https://github.com/obi-ontology/obi/pull/1834/files#diff-ae1f5c0d7cf0b339e908e810761e5f3dfc1d8cf3a2f0c0e472cab40d63b09cf6
(20)
M src/ontology/OntoFox_outputs/OBA_imports.owl
https://github.com/obi-ontology/obi/pull/1834/files#diff-de51944392023c40808896c6da2c81555ee5042212e6db6ec63ff9a631ccf4da
(6)
M src/ontology/OntoFox_outputs/OGMS_imports.owl
https://github.com/obi-ontology/obi/pull/1834/files#diff-10625d02790ffa2ccee9070660055e3c4ddcdd99298ee07e6238840e9023a13a
(6)
M src/ontology/OntoFox_outputs/OPL_imports.owl
https://github.com/obi-ontology/obi/pull/1834/files#diff-a59fdf1bd3ca8af4be7b8cb0fad4dbcfd6862ed3f7888561b852faa5bcc21502
(10)
M src/ontology/OntoFox_outputs/PATO_imports.owl
https://github.com/obi-ontology/obi/pull/1834/files#diff-5eeee5db972c4214d9c4ec184df8227519c65ba46b1b3dc79c1189fcf232119b
(56)
A src/ontology/OntoFox_outputs/RO_imports.owl
https://github.com/obi-ontology/obi/pull/1834/files#diff-193fd8d470583590766c6ed791a7670373209238ed69e291300b414d505d9025
(295)
M src/ontology/OntoFox_outputs/SO_imports.owl
https://github.com/obi-ontology/obi/pull/1834/files#diff-ca1d68aeee8c7bc4bfb07d8fdb1639723dc14f3c02f5227b5f682bb7bf047dba
(6)
M src/ontology/catalog-v001.xml
https://github.com/obi-ontology/obi/pull/1834/files#diff-1767a95a5492cdd15ad99a4e14e9b8e9bf531f8758dba8cadb180951ccfe9e7e
(3)
M src/ontology/modules/assays.owl
https://github.com/obi-ontology/obi/pull/1834/files#diff-bb6a53ab9e90aca175e4dab30aec980fe4474713113c6f2d7deae81666332250
(88)
M src/ontology/modules/biopsy.owl
https://github.com/obi-ontology/obi/pull/1834/files#diff-a350b2fbb74648a24f831c666669d6547bc9bf2ad7f99afcbda26f1c26ecc6e6
(14)
M src/ontology/modules/data-sets.owl
https://github.com/obi-ontology/obi/pull/1834/files#diff-6d54ede405fe64473cd599ce27c55493dbc6441e24437bbf5c51f9bc5dca245c
(12)
M src/ontology/modules/devices.owl
https://github.com/obi-ontology/obi/pull/1834/files#diff-5d0788088b3b5220b2a881058ceafbcfae367a279757cf3db66dfc493c55fbc8
(382)
M src/ontology/modules/medical-history.owl
https://github.com/obi-ontology/obi/pull/1834/files#diff-ca989233953962ebd4173ec65bd3decae3a3c2597ee483c43815efa990b4ee5c
(14)
M src/ontology/modules/obsolete.owl
https://github.com/obi-ontology/obi/pull/1834/files#diff-99c14e62824f6850a3ef317149442f0f0572e2866c5974f6557bfad2cff319e9
(106)
M src/ontology/modules/study-designs.owl
https://github.com/obi-ontology/obi/pull/1834/files#diff-96a9ec428e511d94ebc21f152e7944ad8199cd6d37a6f1bfd847cf8365cb28b7
(30)
M src/ontology/obi-edit.owl
https://github.com/obi-ontology/obi/pull/1834/files#diff-3cafd7b54e04455cb327c1bee8733e37b1576feae65583ec8d842cce80826290
(682)
M src/ontology/templates/administration.tsv
https://github.com/obi-ontology/obi/pull/1834/files#diff-82439b910f3c4aa5705913c1800e6192e30113cd86406fffdab16cd44ee2f7a7
(14)
M src/ontology/templates/antibody-purification.tsv
https://github.com/obi-ontology/obi/pull/1834/files#diff-c86905f31c96d647a0554da06211adfa716f4a30d1c333d232aa4dd4e58684fd
(4)
M src/ontology/templates/assays.tsv
https://github.com/obi-ontology/obi/pull/1834/files#diff-612c15e9bcc0806a3d9dcea267b312f154260649ecfaafd41e21a57b3cd5a7ef
(68)
M src/ontology/templates/biobank-specimens.tsv
https://github.com/obi-ontology/obi/pull/1834/files#diff-638cf84b419f647e79d766702cbd300f9841535a476b754d01a3de0d3f3781ab
(4)
M src/ontology/templates/biopsy.tsv
https://github.com/obi-ontology/obi/pull/1834/files#diff-3511488a5803e17d4f13d0e08c452ea5b89295ce22f1dff48942366ceafecb5d
(4)
M src/ontology/templates/data-sets.tsv
https://github.com/obi-ontology/obi/pull/1834/files#diff-aaa464b9b455dca7e2d11666937c8495d780dd2ff513988f8df0068278519002
(6)
M src/ontology/templates/data-transformations.tsv
https://github.com/obi-ontology/obi/pull/1834/files#diff-467375ca4d19275f1a08d634a0484e603b82218007c5f7a80db8b32956d87842
(4)
M src/ontology/templates/devices.tsv
https://github.com/obi-ontology/obi/pull/1834/files#diff-1a0501dfe6ebf75ea4aa7c8d271bcae929d5ef3a4f9529d98df6174349762187
(8)
M src/ontology/templates/epitope-assays.tsv
https://github.com/obi-ontology/obi/pull/1834/files#diff-70225811edb80013e824b20e3bf9f895be89d832d383f635d2eaa4308ce99f81
(4)
M src/ontology/templates/medical-history.tsv
https://github.com/obi-ontology/obi/pull/1834/files#diff-07c559b20a5b89a9c90531219f9406597fec6998e3844db00115835a48de7dd9
(4)
M src/ontology/templates/obsolete.tsv
https://github.com/obi-ontology/obi/pull/1834/files#diff-b3f756d8bb199b3d66bef22175d49a6e422d2585f286cbc627dbcfbb55cefdce
(9)
M src/ontology/templates/organizations.tsv
https://github.com/obi-ontology/obi/pull/1834/files#diff-59011e9d41eec75d7a1fcd92581079eb5c98171ded89ed93744e5fabddc7975e
(4)
M src/ontology/templates/physical-examination.tsv
https://github.com/obi-ontology/obi/pull/1834/files#diff-2f77f3eb6493df953b485f6041361e458977087bbce86eaaea7300db051671f2
(4)
M src/ontology/templates/sample-collection.tsv
https://github.com/obi-ontology/obi/pull/1834/files#diff-dab7148048073836c885d01d60c55bd5f4851bac59ebffc62c7ba354693f24fb
(4)
M src/ontology/templates/sequence-analysis.tsv
https://github.com/obi-ontology/obi/pull/1834/files#diff-7086a2dbade9f3d8aab2211267bc4f0164de2ed0cf77f96a2e6155dcfea4ede5
(4)
M src/ontology/templates/specimen-assay-data.tsv
https://github.com/obi-ontology/obi/pull/1834/files#diff-ff9500722f56c9a492063d7ab7d0e9c7f6343064cdeafed3f87286930e75023b
(4)
M src/ontology/templates/study-designs.tsv
https://github.com/obi-ontology/obi/pull/1834/files#diff-c620eca8f03a1a1cec10a37064ab87fd4a957fd7b8dfa62181214a9ea6937f06
(4)
M src/ontology/templates/value-specifications.tsv
https://github.com/obi-ontology/obi/pull/1834/files#diff-55549adbc838f5666e5b80c27b95ffc991620bee82088262f236d116756a1570
(4)

Patch Links:

https://github.com/obi-ontology/obi/pull/1834.patch
https://github.com/obi-ontology/obi/pull/1834.diff

—
Reply to this email directly, view it on GitHub
https://github.com/obi-ontology/obi/pull/1834, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADJX2IVXVMPVTQLZOSLTCOTZ6PXLPAVCNFSM6AAAAABRA77ZOGVHI2DSMVQWIX3LMV43ASLTON2WKOZSGYZDSOJQGQ2TSMI
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

--
Bjoern Peters
Professor
La Jolla Institute for Immunology
9420 Athena Circle
La Jolla, CA 92037, USA
Tel: 858/752-6914
Fax: 858/752-6987
http://www.liai.org/pages/faculty-peters

Discussed on OBI dev call 2024-11-04: James will be updating the revised COB test PR to include "disposition", "site", and "function", plus some object properties and data properties, so that others can test a revised version of COB with those included. That will resolve these three dangling BFO classes in this demo.
Jie proposed discussing the creation of a new OMO release in the next OBO call; a new OMO release would resolve the one remaining dangling BFO class, GDC.


Add "planning on" to English phrase match list

Good addition. :+1:

Was @hallomatt's suggestion!


Remove the needs review check

This fails every time I create a PR, can we just remove it?  I am getting lots of emails because of this failing check.
PRs will be checked before they're merged.

Instead of removing completely, can we try using GITHUB_TOKEN
The job's are failing whenever an issue or pr is created because the token PROJECT_BOARD_AUTOMATION_TOKEN  might not be setup in this repository secrets, which is used in both the below files
https://github.com/unitycatalog/unitycatalog/blob/6e07f9e4e55ba9f8e9c50b2b10c980756fe80026/.github/workflows/project-board-automation-for-issues.yml#L18
https://github.com/unitycatalog/unitycatalog/blob/6e07f9e4e55ba9f8e9c50b2b10c980756fe80026/.github/workflows/project-board-automation-for-prs.yml#L22
Instead of PROJECT_BOARD_AUTOMATION_TOKEN , GITHUB_TOKEN might work!


Changes for SWIFT 2.0 and Xcode 7

Hi, made the necessary changes to get your source compiled with XCode 7 and Swift 2.0

Hi @Jeannot-Muller ,
PR merged. Thanks

you’re welcome!
Thanks for the merge

On 19 Oct 2015, at 13:57, Ahmed Ali<EMAIL_ADDRESS>wrote:
Hi @Jeannot-Muller https://github.com/Jeannot-Muller ,
PR merged. Thanks
—
Reply to this email directly or view it on GitHub https://github.com/Ahmed-Ali/RealmObjectEditor/pull/8#issuecomment-149194238.

--
ramgad.com http://ramgad.com/
Dr. Jeannot Muller Consulting & Publishing
Lebzelterstr. 15 C
81827 Munich
Germany
USt-IdNr.: DE298983498
+49 89 451 452 70
+49 171 9 37 17 67


skeleton

@h1alexbel the puzzle #23 is still not solved.

@h1alexbel the only puzzle #23 is solved here.


Overflow issue fix plus couple of improvment

fixed overflow when using more the 7 pages - upgraded flutter_svg - added support for custom skip and done button color/textStyle/shape
#16 #15

@medyas thanks for opening a pull request, I'll soon review and merge it 👍

@xsahil03x thanks, and can you inform when its published to pub.dev because i am using the repo branch in my app.

Thank you @medyas for the PR. Cheers :+1:


After selecting image when i again run didSelectAssets function . it Show previous selected photos . How to refresh that?

You can try this:
pickerController.defaultSelectedAssets = nil

Wow!! Thats easy Fix.. thanks a lot
Well, i just wanna pick only photo .. i m using .SmartAlbumScreenshots Group type. I want to pick all photo. Which group type is that ??

Wow!! Thats easy Fix.. thanks a lot
Well, i just wanna pick only photo .. i m using .SmartAlbumScreenshots Group type. I want to pick all photo. Which group type is that ??

Just use pickerController.assetType = .AllPhotos

Thanks Again ... :)

Let me know if you have any questions :)


Unbox Rekordbox in export mode?

Hi,
Is it possible to run unbox with Rekordbox in export mode?
Then I'm open the software, I don't get any information from my Rekordbox, I use only PC with Windows.

Not yet, but there is an update coming very soon that will allow you to use export mode on rb6 if you're on Windows 64 bit, are you running rb6 on Windows 64?

I'm ussing Rekordbox 5 and Windows 10, 64 bit

Yep that will work when this goes live, should be out sometime this week. I'll post here when it's live.

@Sigvaladson the latest version should now work with export mode


Open in Runme

This patch adds a uri handler that would allow us to have a link like vscode://stateful.runme?command=setup&repository=git@github.com:webdriverio/webdriverio.git anywhere to have users check out a project locally with Runme. An initial POC looks like this:

If users don't have Runme installed the following message will be displayed and allows users to immediately get started:

Btw, I fixed the URI in the description, it's vscode://stateful.runme?command=setup&repository=git@github.com:webdriverio/webdriverio.git versus<EMAIL_ADDRESS>

unless I'm doing something wrong?

The current implementation only accepts git urls of the format git@provider.com:org/project.git as a start. This can be extended arbitrarily. The getSuggestedProjectName is responsible for parsing this information.

In my mind the .runme file semantics are something to mull over and address.

Sure. This can be changed later on without having to worry about UX regressions given that the file is temporary and will not be part of the project. I currently don't have enough information about future use cases that I can make any better guesses about this.

The current implementation only accepts git urls of the format git@provider.com:org/project.git as a start. This can be extended arbitrarily. The getSuggestedProjectName is responsible for parsing this information.

OK. Let's support it before merging please.

Sure. This can be changed later on without having to worry about UX regressions given that the file is temporary and will not be part of the project. I currently don't have enough information about future use cases that I can make any better guesses about this.

Makes sense. What I'm saying is that .runme it ever exists at the root of a repo should be a directory not a file. Not asking for guessing, just to not use it as a file please.

if it ever exists at the root of a repo should be a directory not a file.

Can you help me understand the reasoning? For me it didn't matter much and I decided for the simplest solution which is a basic file. Using a directory would imply we use it for other types of files too which we currently don't, also the file contains the information about which file of the project runme should open. It also didn't really matter that much because the file is removed once VS Code opened.
Anyway, thinking about this a bit more made me realise that this information can be stored in the extension directory which would allow to not create it in the first place, so I will go with that.

Can you help me understand the reasoning? For me it didn't matter much and I decided for the simplest solution which is a basic file. Using a directory would imply we use it for other types of files too which we currently don't, also the file contains the information about which file of the project runme should open. It also didn't really matter that much because the file is removed once VS Code opened.
Anyway, thinking about this a bit more made me realise that this information can be stored in the extension directory which would allow to not create it in the first place, so I will go with that.

I'm ok with .runme_bootstrap or .runme/bootstrap. not really opinionated on bootstrap. it's more about being specific and consistency to have all .runme info in a common dir and being straightforward how that will work.

@sourishkrout @mxsdev can I have another round of feedback?

LGTM 👍 .


fix(Vertex): Compile error when MTOON_OUTLINE_WIDTH_SCREEN

ERROR: 0:1077: 'normalize' : no matching overloaded function found
ERROR: 0:1077: '-' : wrong operand types - no operation '-' exists that takes a left-hand operand of type 'const int' and a right operand of type 'const mediump float' (or there is no acceptable conversion)
ERROR: 0:1077: 'clamp' : no matching overloaded function found

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

GitHub release
npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:


[Bug] Site Crashes for Events with no Location Data

Description
I am trying to generate some data but it's crashing. The event object has no location data and it results in a crash. I have tested for live and also attaching a screenshot with error message in the console.
Screenshots

Additional information
No response

Hello! Can you please provide the steps to recreate? I am not seeing this but am doing some testing to try.

From what I can tell you have not been added to the API to be able to work on the map so this may be why you are seeing some issues.  Please refer to the readme and make sure all steps have been completed to be able to generate data.
If you are still seeing issues after this, provide all the steps to recreate so we can identify the problem.

I am added to the API. Here's the screenshot of the issue I created for it.

To create data I am editing a comment of an issue and it results in a crash.

To create data I am editing a comment of an issue and it results in a crash.

Ah okay, perfect. I couldn't find you before.  I see what you mean now.  Would you like to take on this bug to add a check for no location data?
The end result should still add an event card, but no point to the map and of course, not crash.

Yes, I'll add checks for it.


Missing Guidance On Hybrid Connection 'Key' 'Value' Properties

What is the configuration for 'User specified metadata stored within the resource.' section of the Hybrid Connection?  What are the values we need to insert for 'Key' and 'Value' fields of the create Hybrid Connection?  Do we insert any random 'key' 'value' strings here?  What's the deal?

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

ID: 6e0efd5e-72d6-5124-f225-dd6426c9e004
Version Independent ID: 8ca96d3d-d9bc-fcd4-fe19-f10cd6fa3370
Content: Azure Relay Hybrid Connections protocol guide
Content Source: articles/service-bus-relay/relay-hybrid-connections-protocol.md
Service: service-bus-relay
GitHub Login: @clemensv
Microsoft Alias: clemensv

@d-h-morrison Thanks for the comment! We will investigate on this issue and get back to you soon.

@d-h-morrison Can you please confirm if your question is related to the referenced document? if not please provide a link to the correct document.
In Hybrid Connection, the usermetadata is a placeholder to store user-defined string data for the hybrid connection endpoint. For example, it can be used to store descriptive data, such as a list of teams and their contact information. Also, user-defined configuration settings can be stored.
userMetadata": "[{\"key\":\"test\",\"value\":\"test\"}]"
See the Rest API reference for the details.

@d-h-morrison Checking in to see if the above post helped answering your question.

@d-h-morrison Since we have not heard back from you we will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.

Hi,
Thanks for the all the help.  I've been out of pocket; apologies that it took me some time to get back.  The info you supplied is helpful and did the trick.  Nice work.
David

From: KetanChawda-MSFT<EMAIL_ADDRESS>Sent: Thursday, May 23, 2019 3:21 AM
To: MicrosoftDocs/azure-docs
Cc: Dave-O; Mention
Subject: Re: [MicrosoftDocs/azure-docs] Missing Guidance On Hybrid Connection 'Key' 'Value' Properties (#31528)
Closed #31528https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fissues%2F31528&data=02|01||f6979c71e3c440a6931e08d6df2db5b6|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636941784739303093&sdata=19hI706Jp0hv%2BH0TqJ9yGaSl59e9%2B%2F9QBpVXkFnJqvk%3D&reserved=0.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fissues%2F31528%3Femail_source%3Dnotifications%26email_token%3DADBAIXY7FXTYDAURX34KJXTPWYESRA5CNFSM4HNZN54KYY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGORS6DULA%23event-2361145900&data=02|01||f6979c71e3c440a6931e08d6df2db5b6|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636941784739313098&sdata=9MX%2BTwKFN66C0XpHUxsA4qZfp6rRRuaVg5zZnqVIC2o%3D&reserved=0, or mute the threadhttps://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FADBAIX76OYWJFBKR62OJMX3PWYESRANCNFSM4HNZN54A&data=02|01||f6979c71e3c440a6931e08d6df2db5b6|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636941784739323109&sdata=UecidIuGtCbtGGl8yxHLmuU2VGvUQLChPPXVKJR89Ig%3D&reserved=0.

Hi @KetanChawda-MSFT,
I tried as you mentioned, but it's not working for me, could you please help me?
...
"properties": {
"requiresClientAuthorization": true,
"userMetaData": ["{"key":"endpoint","value":"test"}"]
}
}
...
"error": {
00:54:57 -     "message": "Unexpected character encountered while parsing value: [. Path 'properties.userMetaData', line 1,
00:54:57 - position 98. CorrelationId: 36e7509b-7204-4e62-aa05-ab1aa1022255",
00:54:57 -     "code": "BadRequest"
00:54:57 -   }
00:54:57 - }'
Thanks,
Aravindh

Hi @KetanChawda-MSFT ,
I managed to resolve the issue, by using variables.
"hybridMetaData": "[concat('[{"key":"endpoint","value":"', parameters('hybridEndpoint'), '"}]')]"
Thanks


added zoom via mouse wheel

Closes #1.
Unfortunately it doesn't work properly yet when you open the faction table and scroll down a bit.

Scrolling is reserved for panning the map currently. You can double click to zoom into any area and double click to zoom back out


fixed go to top button position

I have changed the position of go to top button, as go to top button is on top which is not good for user experience and also it look good at bottom

I have changed the position of go to top button, as go to top button is on top which is not good for user experience and also it look good at bottom

Please start the repo and share on social media


Implement ETCD auto-compaction

With etcd 3.x there is an automatic-compaction feature available hence the cronjob for the compaction would not be needed anymore.
With etcd 3.3 there is a new feature as well to specify the revision number to be kept in the DB which could help with the size of ETCD DB.
Reference: https://etcd.io/docs/v3.5/op-guide/maintenance/#auto-compaction

Auto-compaction has to be enabled in the ETCD. It is advised to run also defragmentation after each compaction. We have to be careful here as the defragmentation is blocking read/writes hence the 'downtime' on etcd service.
We have to check the needed frequency for compaction/defragmentation as well as the number of revisions on the ETCD.
Next steps is to check the data for heaviest cluster (deu01)

Internal steps: https://github.com/giantswarm/giantswarm/issues/26218

With AWS release v18.3.0, we do now integrate etcd compaction and allow quota backend adjustment by default, https://github.com/giantswarm/k8scloudconfig/pull/1116.
Closing this issue for now.


Github CI to check java code format.

To make sure pushed changes are conform with the style guides, each commit and PR should be style checked.

Nice


SyntaxError: Cannot use import statement outside a module

I am using Typescript 4.9.4 and get the below error immediately when I run the vite build.
My package.json has:
type: "module"

My tsconfig.json has:
"allowSyntheticDefaultImports": true,
"esModuleInterop": true,

Error:
failed to load config from
/my/frontend/repo/vite.config.js
error when starting dev server:
/my/frontend/repo/node_modules/vite-plugin-rollbar/esm/index.js:1
import FormData from 'form-data';
^^^^^^

SyntaxError: Cannot use import statement outside a module
    at internalCompileFunction (node:internal/vm:73:18)
    at wrapSafe (node:internal/modules/cjs/loader:1176:20)
    at Module._compile (node:internal/modules/cjs/loader:1218:27)
    at Module._extensions..js (node:internal/modules/cjs/loader:1308:10)
    at Module.load (node:internal/modules/cjs/loader:1117:32)
    at Module._load (node:internal/modules/cjs/loader:958:12)
    at ModuleWrap.<anonymous>
(node:internal/modules/esm/translators:169:29)
    at ModuleJob.run (node:internal/modules/esm/module_job:194:25)

Can you try adding "module": "es2020" inside your tsconfig.json file?

I've stepped away from this tool for now, but if I end up trying it out again I'll come back and report. Feel free to close if you want.

I also ran into this problem. Looks like a change to package.json fixes it. I've PR'd that change: #5

+1, I added type:module to packpage.json & module:es2020 to tsconfig but still not be able to sync the source map
err: FormData is not defined.
detail:

+1, I added type:module to packpage.json & module:es2020 to tsconfig but still not be able to sync the source map err: FormData is not defined. detail:

@mrth2 are you running node v18+?

@rang-ali  nope, it's node v16.14.2


[Tooltip] Tooltip stays on when scrolling in a DataGrid

Steps to reproduce
Steps:

Open this link to live example
Hover over one of the tooltips in the Last Name column
Scroll on the datagrid
You'll notice the tool tip stays open

Current behavior
The tool tip stays open on scroll inside a Datagrid.
Expected behavior
The tool tip should close when scrolled away from.
Context
We are using a tooltip inside of a data grid. When a user hovers the tooltip, we have an api call that happens to populate the it's contents. This call takes milliseconds to complete. When a user hovers the tooltip, and scrolls in the Datagrid, the tool tip stays open even though the user's cursor is no longer hovering the tooltip.

  Output from `npx @mui/envinfo` goes here.

Search keywords: Tooltip, stays open, tooltip hover

I'm able to reproduce the behavior you describe. Not sure if it can be considered a bug or not.
React Aria and Radix close the tooltip as soon as the cursor leaves the trigger, no matter if a scroll event or the user moving te cursor caused it. Ariakit has the same behavior as the one in Material UI: the tooltip is not closed when the cursor leaves the trigger because of the user scrolling; it's only closed after the user moves the cursor.

@aarongarciah - Thanks for the quick reply.
I've updated the stackblitz code to have a timeout to simulate an api call to set the text and opening the tool tip (This is what we're doing in our application).  If you hover over one, and quickly move to a different one or scroll, you'll be able to tell when you even move the mouse, that the tooltip stays open.

Closing when the cursor leaves the trigger no matter the reason (scroll, actual cursor move) feels more correct to me. It would also be closer to how the behavior is described in:
The ARIA pattern (though a WIP):

(the tooltip) remains open as long as the cursor is over the trigger or the tooltip.

Material Design 2:

Tooltip disappears when cursor moves out of the touch target

@BTish I agree with @mj12albert. What you're trying to achieve is outside of a tooltip pattern.
Maybe a Popover is better suited for your use case. We had a recent issue where this was discussed, see https://github.com/mui/material-ui/issues/44554#issuecomment-2501565829. Tooltips are meant to display secondary info (e.g. provide more context on a button that performs an action) while popovers are meant to display primary info and the sole purpose of the popover trigger is to open the trigger. Let me know if this helps.
In a future major version, once we adopt Base UI in Material UI's Popover, we'll have first-class support to open Popovers via hover.

What you're trying to achieve is outside of a tooltip pattern.

Wait, regardless of the use-case, we are all agreeing with OP's reported current and expected behavior right? (the Datagrid part isn't relevant)

Current behavior
The tool tip stays open on scroll ~inside a Datagrid.~
Expected behavior
The tool tip should close when scrolled away from.

I think this could be considered a bug 🤔

@mj12albert I mixes a couple of issues in my previous response, sorry about that. I redacted my comment. I agree, closing the Tooltip when scrolling away seems a better default. Do you know how this will be handled in the Base UI rewrite? AFAIK the tooltip is closed when scrolling away but only after the user has stopped scrolling.
@BTish if the content you're displaying in the Tooltip is something that's vital for the UX and not something secondary, maybe Popover is better fir your use case,

@BTish if the content you're displaying in the Tooltip is something that's vital for the UX and not something secondary, maybe Popover is a better fit for your use case.

Sounds great. Thanks @aarongarciah. I've talked with our UI/UX and we're going to go with the Popover route.

Nice @BTish. I'll keep this issue open so we tackle this in the future although this issue will probably be solved once we adopt Base UI.


[Bug] Navigation Bar image rendering in dark mode (closes #89)

This pull request fixes issue #89.

Added a second vector file to the asset collection 'navi_bar_icon' containing the same logo/image, but with white text color to adapt to dark mode.
Fixed the metadata for the mentioned asset collection. (I also added the static propertie  "properties" : {   "template-rendering-intent" : "original" } so the propertie tag in the source code for rendering the image as 'orginal' can be removed.
I moved the initial creation of the 'navigationItem.leftBarButtonItem' to the super method 'viewDidLayoutSubviews()' so it gets properly redrawn when the appearance of the UI changes (from light to dark or vice versa).

Hi @tens0rfl0w ,
Please resolve the conflict.

Hi @tens0rfl0w ,
Please resolve the conflict.
@haosap
Fixed!


Additional Fragments: Circle, Nut Profile, and Locking Nut Profile

"{circle} {nut_profile} {locknut_profile} {locknut_profile}\nTest" gives

The circle is something I wanted for magnets.
The nut and locking nut profiles seemed nicer than the (standard) box, and would allow me to tell the two types of nuts apart. I would like it for the width parameter on these last two to be optional, but I didn't figure out how to do that (yet?). I've set the nut (base) to be the same width as the screw heads; this seems like a better option.
Mention of these have been added to the Readme.

Thank you! I especially like the nut profile!


a bar with run button is disappeared

Issue Type: Bug
a bar with run button is disapeared on my Azure Data Studio window. Pls help.
I cannot run any query now.
Azure Data Studio version: azuredatastudio 1.31.1 (65fb22cc7c36db9c53af1ed2fdbdf48f66c682be, 2021-07-28T21:13:05.032Z)
OS version: Darwin x64 20.6.0

System Info

Item
Value

CPUs
Apple M1 (8 x 24)

GPU Status
2d_canvas: enabledgpu_compositing: enabledmetal: disabled_offmultiple_raster_threads: enabled_onoop_rasterization: enabledopengl: enabled_onrasterization: enabledskia_renderer: disabled_off_okvideo_decode: enabledwebgl: enabledwebgl2: enabled

Load (avg)
2, 2, 2

Memory (System)
8.00GB (0.02GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions (3)

Extension
Author (truncated)
Version

datavirtualization
Mic
1.12.0

import
Mic
1.3.1

query-history
Mic
0.1.0

Could you please attach a screenshot of the issue?
If this is for a new query window (or opening an existing .sql file) does the issue still occur if you open a new query window/file?

@Charles-Gagnon
Thank you.
For your question:
It's ok with new query window

But It occurs when I save a new file or open an existing .sql file.

@emmaziinggg looks like you are not using the latest ADS, please upgrade to 1.32 and see whether this still repro.

@emmaziinggg If you're still seeing this issue after updating please follow these steps so we can get some additional logs :

Download a private build of ADS with some extra logging I added : https://sqltools.blob.core.windows.net/public/azuredatastudio-win32-x64.zip
Unzip it
Close all other instances of ADS
In the unzipped folder run azuredatastudio-insiders.exe
Open up an editor in a way that causes it to not display the toolbar
Run the Developer: Open Logs Folder command
Zip up the entire contents of that folder and then either attach them to this issue or e-mail them to me at<EMAIL_ADDRESS>

Closing based on previous suggestions.  Please updated to latest ADS version and let us know if the issue reproduces.  If so, please provide additional log data as requested above.  Thanks!


Winetrick failed to run winetricks -q msls31

Related to:

https://github.com/Winetricks/winetricks/issues/1807

Link to:

https://github.com/huan/docker-wechat/issues/131

Fixed by https://github.com/Winetricks/winetricks/pull/1814


refactor(waku): prettify cli using commander.js

now the CLI has growing complex, I think we need a standard library to handle the thing

now the CLI has growing complex, I think we need a standard library to handle the thing

Yeah, I was thinking about it too. But, I have a few concerns:

The diff doesn't seem to improve so much. Maybe it's too early at this point.
I used commander.js before, and found it somewhat traditional. Is it still widely used?
It must be an optional peer dependency and it requires to add a dependency in the templates. That's a huge motivation to avoid using libraries unless it's very helpful.

now the CLI has growing complex, I think we need a standard library to handle the thing

Yeah, I was thinking about it too. But, I have a few concerns:

The diff doesn't seem to improve so much. Maybe it's too early at this point.
I used commander.js before, and found it somewhat traditional. Is it still widely used?
It must be an optional peer dependency and it requires to add a dependency in the templates. That's a huge motivation to avoid using libraries unless it's very helpful.

There are some options:
arg: https://github.com/huozhi/bunchee/blob/main/src/bin/index.ts
commander.js: https://github.com/vercel/next.js/blob/canary/packages/create-next-app/index.ts
clipanion: https://github.com/napi-rs/napi-rs/blob/main/cli/src/cli.ts

https://www.npmjs.com/package/meow

Thanks.
I would like to hold this for the moment, and revisit it in the future. There might be more hidden requirements in cli.ts and we can't decide it now.

It must be an optional peer dependency and it requires to add a dependency in the templates. That's a huge motivation to avoid using libraries unless it's very helpful.

This limitation is gone with #355.

I'm still interested in using commander.js or some alternatives (maybe commander.js is fine.)
Maybe some time later, maybe before v1-alpha. Let's start over anyway.


embassy time missing from Cargo.toml

https://github.com/esp-rs/esp-hal/blob/main/examples/src/bin/embassy_hello_world_systimer.rs#L16 relies on embassy-time, but it's not present in https://github.com/esp-rs/esp-hal/blob/main/esp-hal/Cargo.toml

It's an example, so it can be found in the examples Cargo.toml: https://github.com/esp-rs/esp-hal/blob/da3375bbe47dcb659353b909fbc556a74bb64cda/examples/Cargo.toml#L16

I think I read the wrong Cargo.toml then, that's my fault.


Call GuzzleHttp\Client::get() to retrieve resource

Should allow timeouts to be set for #157

Nope, this won't then allow the request that was sent to be returned in ResourceRetriever


Feature: disable built in basic auth

When Venus-influx-loader is deployed behind reverse proxy handling auth, there is no need to handle basic auth ourselves. Add option to disable basic auth via command line and config file

Possible via: https://github.com/victronenergy/venus-influx-loader/commit/aa8adf4f09353cd253b2e7323f6af991fcff0a81
I'd like to also hide the side bar Security pane when auth is disabled to avoid confusion, leaving open for now.

Completed via https://github.com/victronenergy/venus-influx-loader/commit/a75990cedfe008bd70c1a0892573f16e3ec17c0f which brings ability to hide panes in Settings UI depending on the deployment needs.


[VS Code] Joining collaboration session: Could not join the collaboration session as it has already reached the maximum of 5 participants.

Error:
Joining collaboration session: Could not join the collaboration session as it has already reached the maximum of 5 participants.
Steps to Reproduce:

Version Data

extensionName
VSLS

extensionVersion
1.0.125

protocolVersion
2.2

applicationName
VSCode

applicationVersion
1.33.1

platformName
MacOS

platformVersion
18.5.0

Hey! You can increase the maximum number of collaborators to 30 by changing the following setting:
"liveshare.increasedGuestLimit": true
Please re-open the issue if this does not fix your problem. Thanks!

Thank you very much!
On Tue, May 7, 2019 at 12:35 PM Daniel Lebu<EMAIL_ADDRESS>wrote:

Closed #2062 https://github.com/MicrosoftDocs/live-share/issues/2062.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/live-share/issues/2062#event-2324959353,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHXL2AGKDQL4PFVGAMDMRKDPUG4VVANCNFSM4HLCURFQ
.


When I open the library with files to set properties, it will flash back

Description
When I open the library with files to set properties, it will flash back。
Steps To Reproduce
1.Open files, select the library and right-click properties

2.click [customization]

3.it will flash back

Expected behavior
I hope I can adjust the properties correctly and change the folder with a new icon
Files Version
<IP_ADDRESS>
Windows Version
Windows11 21H2  10.0.22000.318
Relevant Assets
[debug.log](https://github.com/files-community/Files/files/7551682/debug.log
debug_fulltrust.log
)

Same as #6909


It doesn't run on VSCODIUM

Hi, please i can't install on my EXCELENT VSCODIUM (because your only dispath vscode).
Please fix that editor.
Thanks you.

I haven't looked at the platform's repo. But based on the fact that when you log in via OAuth to any service (GitHub, Google, etc.) on VS Codium you get redirected to VS Code, I'm guessing the solution is making the platform pass a parameter to modify the URI that will open either VS Code or VS Codium

Looks like we need to use vscodium:// as the scheme instead of vscode:// or vscode-insiders://. We'll need to change the Sourcegraph frontend to allow redirects to this scheme, or use http:// like JetBrains.


Entity delete

It is possible to delete “entity” even if:
it is owned by another entity
it owns other entities,

This is the expected behaviour, it has been developed in this way. Do you need to change the current development?
The only restriction is that there are no risk session for this entity.
This is an existing issue (#159), please joint to the discussion adding your rationale to change the behaviour


[WIP][SPARK-29750][BUILD] Avoid dependency from joda-time

What changes were proposed in this pull request?
Removed direct dependency from joda-time.
Why are the changes needed?
To reduce number of direct Spark dependencies.
Does this PR introduce any user-facing change?
No, only if users depend on joda-time transitively.
How was this patch tested?
By building Spark via ./build/sbt -Phive -Phive-thriftserver package

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-K8s/18153/
Test PASSed.

Test build #113242 has started for PR 26392 at commit cb8c387.

Test build #113242 has finished for PR 26392 at commit cb8c387.

This patch fails build dependency tests.
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/113242/
Test FAILed.

Test build #113243 has started for PR 26392 at commit 02e9bee.

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-K8s/18154/
Test PASSed.

Sorry, but I'm -1 to downgrade like this.

@dongjoon-hyun You are so quick.

arrow vector requires joda time in 12.x:
[info] joda-time:joda-time:2.9.9
[info]   +-org.apache.arrow:arrow-vector:0.12.0

https://github.com/apache/arrow/blob/apache-arrow-0.12.0/java/vector/pom.xml#L34-L38
but arrow 0.15.1 does not require it anymore: https://github.com/apache/arrow/blob/apache-arrow-0.15.1/java/vector/pom.xml

Is that the last one? Or, just one dependency instance?

Is that the last one? Or, just one dependency instance?

I bumped arrow version to 0.15.1 locally, so, there is no dependency from joda-time anymore. Not sure that is is safe to migrate to arrow vector 0.15.1

I pinged you the on-going Arrow upgrade PR. Let's resume this PR after that PR.

There is a transitive dependency from joda-time via hive-common for hadoop-3.2:
[info] joda-time:joda-time:2.8.1
[info]   +-org.apache.hive:hive-common:2.3.6
[info]     +-org.apache.spark:spark-hive_2.12:3.0.0-SNAPSHOT [S]

which still exists in hive's master: https://github.com/apache/hive/blob/master/common/pom.xml#L101-L105

Test build #113243 has finished for PR 26392 at commit 02e9bee.

This patch fails due to an unknown error code, -9.
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/113243/
Test FAILed.

I am closing this because there is no chance of hive-common avoids dependency from joda-time any time soon.