"Access is denied." error

When doing the command packwiz init --author Micalobia --fabric-latest --latest --name TestModpack --version 1.0 --modloader fabric, it prints an Access is denied. error for open AppData\Local\ElevatedDiagnostics. When running it with admin privileges, it shows open LogFiles\WMI\RtBackup instead.


docs: add JWT spec

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 82.73%. Comparing base (cf85765) to head (39bf46e).
Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #14   +/-   ##
=======================================
  Coverage   82.73%   82.73%
=======================================
  Files           3        3
  Lines         388      388
  Branches       70       70
=======================================
  Hits          321      321
  Misses         67       67

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


fix link to screenshot

Hi Martin @maweigert ,
with this little PR, the screenshot should become visible on the napari hub page of your plugin after the next release.
Thanks!
Best,
Robert

Awesome! Thanks!


Accessing the DB from outside repl.it

Hey!
I was making an app, and I wanted to use the repl db to save data... The app would be an Android app, and not a repl.it app. Is there a way to access the db from the Android app?
Thanks in Advance!

You can make a repl that proxies requests to the database. This is actually a common usecase so it has been added to the library in the replit.database.server module. You can also roll your own proxy if you want to add some sort of authentication so that random people can't view/change your DB contents.


careers.en: update

@Stanislaw-bnk I would appreciate more descriptive commit messages. I accept this time, but next time, I will ask for changes.


Enhanced and/or Updated Standards and Policies

Have engagement from security branch to review app and data security policy


Localize numbers server-side (maintainers' opinion requested)

This one started when I encountered #12637. I wrote RenderNumber in https://github.com/go-gitea/gitea/commit/b9319f9a46d2b1a6fe549ec12971fa38315bfea6 to format the number of commits, then I thought "Why not format all other numbers in a nice way?". So I did it in https://github.com/go-gitea/gitea/commit/c929ad212f962204fd6ac2b690bae58047a0d5f0.
While running a search for numbers in templates I encountered JsPrettyNumber and CountFmt. JsPrettyNumber seems to localize the numbers client-side (therefore with a "flash of unstyled content") and CountFmt does it server-side disregarding the user's locale. So this PR can go a few ways:

Land RenderNumber + use it in the places of https://github.com/go-gitea/gitea/commit/c929ad212f962204fd6ac2b690bae58047a0d5f0 (current PR state)
Do 1 + refactor the codebase to use only RenderNumber and drop JsPrettyNumber and CountFmt
Drop everything I did and just use JsPrettyNumber for number of commits

What do you prefer?

I don't think we can drop CountFmt as that suffixes with k/ M/ G, and I don't want to have for example 7,654,321B instead of 7,6MB but perfectly localized.
Then, in favor of pure JS side rendering is that it knows best how to format a number for the user.
Against the JS solution speaks especially that it needs JS, and a bit of frontend time, which is especially bad for users with bad hardware or users that disable JS.
Hmm, I don't think that is a strong enough argument not to push the work to the frontend.
So I'm probably in favor of rendering all numbers (where possible) in the frontend.

Thanks @delvh, look like a vote for option 3

The frontend language should not always follow web browser, it's a default option. And users could set their prefer language which maybe different from web browser. And for a more complicated example, users' prefer location and language should become two options, but I think we currently can hold only one.

I think that's a frontend concern and should be in JS code ...

Option 3 decided then, thank you all

Continued in #21786

still thanks :heart:


Add support for setting value of select

Although value is not an attribute of a select element, adding this handling to the value attribute simplifies form building, where all inputs, checkboxes, and radios can easily be set with value.
<select value="{{ <~>gender }}">
  <option value="M">Male</option>
  <option value="F">Female</option>
</select>

Awesome - thanks for adding this! Mind adding a test for this case here? https://github.com/mojo-js/paperclip.js/blob/master/test/old/attributes/value-test.js
Thanks!


target cannot remove keyword completions from newer JS versions in jsconfig.json

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.71.2
OS Version: macOS 11.6.6

Steps to Reproduce:

File > New File save as test.js in a new folder "test"
Open folder "test" in vsCode
Click "Yes, I trust the authors"
run "Javascript: go to project configuration" from command palette
click "Configure jsconfig.json"
replace the default contents with
{
"compilerOptions": {
"lib": ["ES5"]
}
}
save jsconfig.json
type "con" in test.js
Observe that "const" is suggested by intellisense even though const is not supported by ES5:

This continues even after restarting vsCode. In one case jsconfig.json was respected (con didn't cause intellisense to suggest const), but after restarting vsCode jsconfig.json was no longer respected.

For context: This is handled by the TypeScript language service.
"lib" only affects which builtin functions have their type definitions imported into the project.  TypeScript is used to parse both TS and JS and always parses the most modern syntax it supports, regardless of settings.  In a TS codebase the code would be transpiled to the target ES version, so using e.g. const would never be an error.  But builtins aren't polyfilled automatically, so the lib option lets you limit which builtin functions are suggested.
AFAIK there's no way to prevent it from offering const as a completion here.

Thank you for replying so quickly with a detailed answer!
So to get ES5 while having the advantages of intellisense is my only option to work in Typescript and then transpile to ES5? I looked into Babel, but seems that doesn't target a particular standard.
Is there any way to restrict syntax highlighting to ES5 to make sure that coloring is accurate in existing ES5 code? E.g. so that const doesn't get the same color as var?

We can't really rely on the target because it's unclear if a user intends to use a compiler to rewrite the code. They might be using ES5 as a shorthand for "use the ES5 lib".

So to get ES5 while having the advantages of intellisense is my only option

I don't think that the two are at conflict. Auto-suggestion will provide things that it thinks are valid to write, but you ultimately get the say in whether you want to add that code. If you want to restrict what you can write, a linter might be the best option.

I looked into Babel, but seems that doesn't target a particular standard.

Babel's preset-env just downlevels to ES5 when no target is specified, but I'm not an expert at it.

Is there any way to restrict syntax highlighting to ES5 to make sure that coloring is accurate in existing ES5 code? E.g. so that const doesn't get the same color as var?

I believe that if you have semantic highlighting enabled, it will subtly color consts differently than mutable variables. But the keywords themselves are just both keywords or reserved keywords in all modern versions of the language, and there's no way to configure those differently.

Thank you for thinking about this.


doc: Update Japanese Translation

This PR is a modified Japanese translation.

📝 Changed routes:

/docs/with-nextjs.ja
…mples/optimistic-ui.ja

(view full size)
(view full size)

/examples/ssr.ja

(view full size)

Commit 5cb17bc2e0b24e66215a897ba06053e33185955e (https://swr-site-ir12sae2e.vercel.sh).

Thank you!


Wrong instruction on https://www.zotero.org/support/plugins

This isn't a zotero-better-bibtex issue by itself but, if I'm right, there is a wrong instruction on https://www.zotero.org/support/plugins#importexport_of_item_metadata_attachments, "Better Bib(La)TeX" item: for the drag-and-drop citations feature, it is said to select "BibTex cite keys" as the default export format, instead of “LaTeX Citation”.
I could create a account on the Zotero wiki in order to fix this error but all my attempts failed. Moreover, I guess you're much better qualified than me for this (I wouldn't like to give myself a wrong instruction).

Thanks for the heads-up! I've changed the Wiki.


cilium: further improve local address selection

(See commit desc.)

This change is

test-me-please

test-me-please


Small deviations on CRS definition cause VRT errors

Output while building the UTM specific VRTs:
Warning 1: gdalbuildvrt does not support heterogeneous projection: expected NAD83 / UTM zone 18N, got NAD83(2011) / UTM zone 18N. Skipping /path/to/bluetopo_tiles/BlueTopo_VRT/BC26926D/BC26926D_complete.vrt
Building utm16...
Building utm19...
Warning 1: gdalbuildvrt does not support heterogeneous projection: expected NAD83 / UTM zone 19N, got NAD83(2011) / UTM zone 19N. Skipping /path/to/bluetopo_tiles/BlueTopo_VRT/BC26H26C/BC26H26C_complete.vrt
Warning 1: gdalbuildvrt does not support heterogeneous projection: expected NAD83 / UTM zone 19N, got NAD83(2011) / UTM zone 19N. Skipping /path/to/bluetopo_tiles/BlueTopo_VRT/BC26H26D/BC26H26D_complete.vrt
Warning 1: gdalbuildvrt does not support heterogeneous projection: expected NAD83 / UTM zone 19N, got NAD83(2011) / UTM zone 19N. Skipping /path/to/bluetopo_tiles/BlueTopo_VRT/BC26J26D/BC26J26D_complete.vrt
Warning 1: gdalbuildvrt does not support heterogeneous projection: expected NAD83 / UTM zone 19N, got NAD83(2011) / UTM zone 19N. Skipping /path/to/bluetopo_tiles/BlueTopo_VRT/BC26J26C/BC26J26C_complete.vrt

Difference being that the NAD83 has been specified, in files, with a specific, time based realization, rather than using the classic NAD83. gdalinfo output for reference:
COMPOUNDCRS["NAD83(2011) / UTM zone 19N + MSL height",
    PROJCRS["NAD83(2011) / UTM zone 19N",
        BASEGEOGCRS["NAD83(2011)",
            DATUM["NAD83 (National Spatial Reference System 2011)",
                ELLIPSOID["GRS 1980",6378137,298.257222101,
                    LENGTHUNIT["metre",1]]],
            PRIMEM["Greenwich",0,
                ANGLEUNIT["degree",0.0174532925199433]],
            ID["EPSG",6318]],
        CONVERSION["UTM zone 19N",
            METHOD["Transverse Mercator",
                ID["EPSG",9807]],
            PARAMETER["Latitude of natural origin",0,
                ANGLEUNIT["degree",0.0174532925199433],
                ID["EPSG",8801]],
            PARAMETER["Longitude of natural origin",-69,
                ANGLEUNIT["degree",0.0174532925199433],
                ID["EPSG",8802]],
            PARAMETER["Scale factor at natural origin",0.9996,
                SCALEUNIT["unity",1],
                ID["EPSG",8805]],
            PARAMETER["False easting",500000,
                LENGTHUNIT["metre",1],
                ID["EPSG",8806]],
            PARAMETER["False northing",0,
                LENGTHUNIT["metre",1],
                ID["EPSG",8807]]],
        CS[Cartesian,2],
            AXIS["easting",east,
                ORDER[1],
                LENGTHUNIT["metre",1]],
            AXIS["northing",north,
                ORDER[2],
                LENGTHUNIT["metre",1]],
        ID["EPSG",6348]],
    VERTCRS["MSL height",
        VDATUM["Mean Sea Level"],
        CS[vertical,1],
            AXIS["gravity-related height",up,
                LENGTHUNIT["metre",1]],
        ID["EPSG",5714]]]

and this is the CRS of most other VRTs instead:
COMPOUNDCRS["NAD83 / UTM zone 19N + navd88",
    PROJCRS["NAD83 / UTM zone 19N",
        BASEGEOGCRS["NAD83",
            DATUM["North American Datum 1983",
                ELLIPSOID["GRS 1980",6378137,298.257222101,
                    LENGTHUNIT["metre",1]]],
            PRIMEM["Greenwich",0,
                ANGLEUNIT["degree",0.0174532925199433]],
            ID["EPSG",4269]],
        CONVERSION["UTM zone 19N",
            METHOD["Transverse Mercator",
                ID["EPSG",9807]],
            PARAMETER["Latitude of natural origin",0,
                ANGLEUNIT["degree",0.0174532925199433],
                ID["EPSG",8801]],
            PARAMETER["Longitude of natural origin",-69,
                ANGLEUNIT["degree",0.0174532925199433],
                ID["EPSG",8802]],
            PARAMETER["Scale factor at natural origin",0.9996,
                SCALEUNIT["unity",1],
                ID["EPSG",8805]],
            PARAMETER["False easting",500000,
                LENGTHUNIT["metre",1],
                ID["EPSG",8806]],
            PARAMETER["False northing",0,
                LENGTHUNIT["metre",1],
                ID["EPSG",8807]]],
        CS[Cartesian,2],
            AXIS["easting",east,
                ORDER[1],
                LENGTHUNIT["metre",1]],
            AXIS["northing",north,
                ORDER[2],
                LENGTHUNIT["metre",1]],
        ID["EPSG",26919]],
    VERTCRS["navd88",
        VDATUM["unknown"],
        CS[vertical,1],
            AXIS["up",up,
                LENGTHUNIT["metre",1,
                    ID["EPSG",9001]]]]]

Harmless enough to make the change from NAD83(2011) / EPSG 6318 to NAD83 / EPSG 4269 to make this go.  But note that BoundCRS form of this tested ok in [py]proj 2.5D transformations; i.e., MSL(GEOID12B)-specific VERTCRS as SOURCECRS with NAD83(2011) TARGETCRS pivot.  The geometric time-realization information being important for rigorous vertical datum transformations.


The Autocomplete component is not jQuery independient (Cannot set property 'tabIndex' of null)

Expected Behavior

The Autocomplete plugin should be jQuery Independient.

Current Behavior

The Autocomplete plugin depends on jQuery as seen on these lines: (151 and 152)
https://github.com/Dogfalo/materialize/blob/e02575415257beb97ec74f0c06d0dab4c6777ff6/js/autocomplete.js#L151
https://github.com/Dogfalo/materialize/blob/e02575415257beb97ec74f0c06d0dab4c6777ff6/js/autocomplete.js#L152
$(this.container).addClass('autocomplete-content dropdown-content');
      this.$inputField.append(this.container);

The container is not appended to the inputField, since there is no jQuery available,
so, the Dropdown component do not find the container on the document.

Possible Solution

Replace those lines by a non jQuery way.
Steps to Reproduce (for bugs)

Context

Your Environment

Version used:
Browser Name and version:
Operating System and version (desktop or mobile):
Link to your project (if appropriate):

Are you able to actually reproduce an error or anything? We use Cash internally that is a very lightweight library that shares some simple jQuery functionality.

For what it's worth, I was getting this error message until I wrapped the autocomplete with an input-field like this:

  Label
  <input type="text" class="autocomplete" />


Crate dont compile

Just adding amiquip in a new project, I have this error with 'cargo build' :

error: expected =
--> <...>/.cargo/registry/src/github.com-1ecc6299db9ec823/amiquip-0.3.0/src/errors.rs:250:10
|
250 |     #[doc(hidden)]
|          ^^^^^^^^

Hm, that's odd. What version of rust and cargo are you using?

May be it's a change in some dependency ?
cargo 1.36.0 (c4fcfb725 2019-05-15)
rustup 1.18.3 (435397f48 2019-05-22)
rustc 1.36.0 (a53f9df32 2019-07-03)

Can you put a project that has this error somewhere so I can reproduce it?

In fact, I just create a new project.
Add 'amiquip = "0.3.0"' in 'Cargo.toml'
Try to compile ... and it's result with the above error.
(Tryed on a coworker PC ... same result)

Just commented out line /src/errors.rs:250 and all work fine now ...

It was indeed a breaking change in a dependency! Sorry for the long delay on this. I opened an issue there asking about the change, and just published 0.3.1 which removes the #[doc(hidden)] for now as you suggested. I'd like to leave this issue open for now, and plan to publish a 0.3.2 restoring #[doc(hidden)] once I can.

Thanks a lot and sorry for the long delay (holiday).


Better exception handling due to invalid session; add additional properties

When a session is invalidated (perhaps because the user changed their password) and we try to post to a user's feed, we get back an http response object with a 400 error code.  This was causing a general HTTPException to be raised; this should be the more specific SessionInvalidatedDueToPasswordChange exception.
In addition, updated status and photo properties for comments and likes.

This is a huge list of changes. Can you create a pull request with just what is absolutely necessary to fix this issue?

Sure thing; I can split this out into separate PRs.


Fetching list of teams channels within a private chat

Is there a way to get the list of channels the user belongs to when the bot is initially installed in a private chat ?
The scenario is that - the user installs the bot to the private chat and then after performing some steps wants the bot to send a message to one of the teams channels, but there doesn't seem to be a way to fetch the team Id when the bot is in the private chat, maybe I missed something ?

@Manish-Ghumnani You could get the list of teams that a user is part of, using the List Joined Teams graph api. Are you trying to send a proactive message in a channel?

@Gousia-MSFT thanks for your reply, from what I know, the Graph API needs permissions and also an authProvider ? Is there a way to avoid that and get the info through the bot context?

@Manish-Ghumnani Yes, you would need to get an access token with the required permissions to use this Graph API. It is not possible to do this only with the Bot. The Bot can only fetch the details of the conversation where it is part of.

Please re-open if there are any other queries here.


Modifier -> SwiftUI -> Controls and indicators: buttonBorderShape(_:)

Doc: https://developer.apple.com/documentation/swiftui/view/buttonbordershape(_:)

[ ] Swift implementation
[ ] Elixir implementation

duplicates #218


Calico 3.2.2 with K8s 1.11.3: Readiness probe failed

I see calico-node unhealthy, calico-pod READY 1/2, run descibe pod show Warning: Readiness probe failed: calico/node is not ready: felix is not ready: Get http://localhost:9099/readiness: net/http: request canceled while waiting for connection (Client.Timeout exeeced while awaiting headers).
Steps to Reproduce (for bugs)
Installation with latest kubeadm

Run kubeadm init --pod-network-cidr=<IP_ADDRESS>/16.
Setup etcd.yaml, rbac.yaml. For calico.yaml, I tried 2 methods:

The default on calico site.
Update IP_AUTODETECTION_METHOD=interface=ens*.
When join another node, calico-node in the worker works fine with 2/2 READY, but on master node still 1/2 READY with the same warning.

Your Environment

Calico version: 3.2.2
Kubernertes 1.11.3
Ubuntu 16.04

I don't know it comes up with latest version, or with my server environment, because I got server from our sysadmin.

You might be encountering this issue: https://github.com/projectcalico/calico/issues/2146#issuecomment-425030944
Do you see the same behavior if you use Calico v3.1?

Sorry, maybe it causes by system environment. After request another VM, it went out. Still do not know how to inspect this, I also run root in both machine.

Hi, use ifconfig find your network dervice name ,set to calico.yaml  like this :
- name: IP_AUTODETECTION_METHOD
              value: "interface=eth0"


[BugFix] support SqlToScalarOperatorTranslator visit lambda functions more than one times (backport #19843)

What type of PR is this：

[x] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Which issues of this PR fixes ：

Fixes # https://github.com/StarRocks/starrocks/pull/19896/files
Problem Summary(Required) ：

Checklist:

[x] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[x] I have checked the version labels which the pr will be auto backported to target branch

[ ] 3.0
[ ] 2.5
[ ] 2.4
[ ] 2.3

run starrocks_fe_unittest

@mergify rebase

@mergify login

@mergify rebase

@mergify rebase

@mergify rebase


Initial Fire Temple MQ Logic

This was actually a lot easier than I expected.

I think it should say has_goron_tunic_strict


Publishing the slides online to github pages

This pull request is a proposal to publish the actual slides to github pages to make viewing them more comfotable.
To make this work a secret ${{secrets.SECRET_GITHUB_TOKEN}} must be created following this guidline: GitHub Documentation

Pages are now published at https://mvonballmo.github.io/HFU_21H__JAS_20I_doc/. Thanks for the tip!


Add and enforce a @requiredPermissions direction

Related Issue or Background Info

#1074

Changes Proposed

Add a GraphQL instrumentation that rejects queries and mutations whose modeled permission requirements exceed what is assigned to the user

I'm not sure what the right "permission inheritance" story is on GraphQL objects. As is, the @requiredPermissions directive gets attached to arguments and field definitions, which means that a query or mutation that returns an aggregate type can be annotated, e.g.,
type Query {
  patients(
    facilityId: String
    pageNumber: Int
    pageSize: Int
    showDeleted: Boolean
    namePrefixMatch: String
  ): [Patient] @requiredPermissions(anyOf: ["SEARCH_PATIENTS", "READ_PATIENT_LIST"])

Since a user must satisfy all @requiredPermissions leaves on their query tree, this functions as a baseline on the Patient type, since no other query returns patients (though one mutation does).
GraphQL also lets you annotate objects directly, e.g.,
type Patient @requiredPermissions(anyOf: ["SEARCH_PATIENTS", "READ_PATIENT_LIST"]) {
  ...
}

which is harder to enforce but may be closer to the restrictions we're trying to enforce (i.e., "to query any data element on a patient, you must have at a minimum X permissions").

I seem to have sent my comments without a summary, somehow. 😕
In any case, I think this is probably a much better way of doing field-level authorization than the hack I was contemplating, so thanks for that! This seems pretty workable, though I'm sort of curious what the alternative approach was that you overwrote before I got a chance to look at it.
And I don't know how much nip/tuck review you want, so I did a random amount before getting tired. 😁


Query support of structure_features properties

COD will not be able to handle queries for structure_features property, at least not until the release of OPTiMaDe, and even some time afterwards. We do not store the symmetry-reconstructed structures yet, although we plan to do so in future. Would it be possible to reduce the query support requirement level from MUST to RECOMMENDED? If not, the COD will not be fully supporting OPTiMaDe specification for quite some time.

I must be missing something. Why do you need the symmetry-reconstructed structure to fill out structure_features?
All you are supposed to need is:

If there is disorder (i.e., if the cif defines any sites with <1 occupation)
There are any unknown positions among the sites
The structure need assemblies to be represented (i.e., the cif uses the sites grouping feature to indicate anything but completely separate groups)

Right, disorder and assemblies are not that difficult to assume. However, for unknown_positions we would have to parse CIFs and look through the coordinates, because currently we do not store this bit of information in the COD SQL database.
Moreover, I feel the definition of unknown_positions needs additional clarification. I will open a separate issue for that.

So, are you saying that COD is not storing the coordinates even of the representative sites in the database at all? Because then I can see how this is a problem.
Because for someone who stores those coordinates, queries on unknown_positions should be straightforward to translate into queries for nulls in the coordinate table, right? (If my entry in the discussion in #260 makes sense.)
I've always tried to push us in the direction that any reasonable database should be able to implement OPTiMaDe without restructuring their data. Still, I'm very reluctant to the idea of queries on structure_features being optional; because it has a vital role in our handling of data compatibility!
The idea was that carefully constructed end-user queries will almost always include a provision to exclude structures with items in structure_features that are not recognized/cannot be handled. That way it will be easier for implementations to not by mistake, e.g., get a bunch of structures that use assemblies, but the user misinterprets by ignoring the assemblies field.
I'm not sure what I think is the right way to proceed. To me it seems very doable to chew through all COD CIFs once and deduce if they contain "disorder", "unknown_positions", or "assemblies" and add those three boolean columns in a separate table (or even just keep that lookup data in-memory in your API implementation, since it is going to be small...) And this strikes me as information that seems useful also for people who search COD outside of OPTiMaDe. But, to force you to add this to your database does indeed go against the goal of not forcing database changes.

Yes, the COD does not store any sites in any searchable form. Instead, they are kept in CIF files on a disk, therefore, as of now we would need to scan through them for every request. We're planning to store the flag about the unknown positions in our SQL database (just as you have suggested), but this most likely will happen after the release of OPTiMaDe.
The COD already has flags for disorder and assemblies. However, one of the reasons of not having unknown_positions is #260.

However I think about this, to drop the MUST requirement on queries on structure_features would be very unfortunate. It was devised to solve a genuine end-user problem in relation to database-specific extensions and possible future extensions of OPTiMaDe: a client might not have any way of knowing what fields to look at to know for sure it correctly interprets structure data it receives (see discussions in #51 and #93). Allowing users to exclude entries based on unrecognized and unwanted members structure_features is the way we resolved that.
What we could do (but I am not super happy about it), is to divide structure_features into two fields:

structure_features would be restricted to flag precisely ONLY things where there is an additional field somewhere (top level or below, e.g., it can be inside sites) that modifies how the structure should be interpreted so that it is INCORRECT to interpret the structure without that field. This is precisely the situation with assemblies. We would keep structure_features as MUST be queryable.

Something like structure_options or structure_flags or structure_tags can then contain all other flags, e.g., disorder, unknown_positions, and we could re-introduce unperiodic that was dropped from #93. Because all those flags are things a client may want to select or unselect in a query, but if they cannot do that, it will at least surely encounter the data it does not understand in the "normal" structure fields (e.g., nulls among the coordinates.) To support queries on this property can then be dropped to RECOMMENDED. We can even allow implementations to only support queries on some of the flags, and even drop to just RECOMMENDED that the flags are at all present in the response for structures they apply to.

The only other alternative I see is to direct COD (and anyone in the same position) to implement structure_features the slow way. I.e., in a query that contains structure_features, do the query without that limitation and then slowly generate cartesian_site_positions for all of them, check if there are any null elements, and if so filter them out (or in). If a query uses up too much computational resources, there is always the possibility to reject it based on that. (In the long run, of course, it seem to make sense for COD to just dig through all your structures and index if cartesian_site_positions as returned from OPTiMaDe has any null elements, but that is up to you.)

What we could do (but I am not super happy about it), is to divide structure_features into two fields [...]

I am also not very happy about it. But the status quo leaves the COD not conforming to the OPTiMaDe specification for the time being. Maybe we could make it to the publication, but we will have to solve #260 on the way.

While #279 is a great achievement, I fear it did not close this issue. Newly introduced structure feature site_attachments requires slow read-through of all the CIF files in the COD, thus the COD will not be able to support queries on it for some time.
Subscribing @sauliusg to this issue.

While #279 is a great achievement, I fear it did not close this issue. Newly introduced structure feature site_attachments requires slow read-through of all the CIF files in the COD, thus the COD will not be able to support queries on it for some time.
Subscribing @sauliusg to this issue.

If we return cartesian coords, we read the table anyway;

My plans are to have a flag attached_hydrogens in the COD SQL database. This will be easy to do and backwards compatible, and we have several pending changes anyway. Let's discuss this in the COD group.

1. If we return cartesian coords, we read the table anyway;

My main concern is not for generating the values for site_attachments, but for making them queryable. This currently requires reading through all the COD CIFs for even the simplest queries on this feature.

2. My plans are to have a flag `attached_hydrogens` in the COD SQL database. This will be easy to do and backwards compatible, and we have several pending changes anyway. Let's discuss this in the COD group.

This would solve the problem for the COD (unless there could be site attachments other than hydrogen?)

This would indeed solve the problem for the COD (unless there could be site attachments other than hydrogen?)

AFAIK CIF currently only supports hydrogens.

As @sauliusg and I have found a way to fix this on the COD side, I am closing the issue.


Fix masked mypy errors

I'm not sure of the metric in test_comb.py: @Shoeboxam, can you make a suggestion there?
My sense is that context might go away, to be replaced by Polars, so we don't need to invest more time there? Though if it is staying, the test coverage could be improved.

Fix #1264
Unblock #1263

Context stays, but the Query class will get less use in common workloads than before. Test coverage can definitely be improved.


Support Ubuntu 22.04

What type of PR is this?
/kind feature

What this PR does / why we need it:
Support Ubuntu 22.04
Which issue(s) this PR fixes:

Fixes #
Requirements:

[ ] uses conventional commit messages

[ ] includes documentation
[ ] adds unit tests
[ ] tested upgrade from previous version

Special notes for your reviewer:
Release note:
none

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.0%) to 78.134%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
854

Relevant Lines:
1093

💛  - Coveralls


Something is broken with 32-bit Windows on Travis

Originally posted by @giordano in https://github.com/bcbi/GitCommand.jl/pull/13#issuecomment-565836038:

I think there is something broken with 32-bit Windows on Travis, I can't find any working setup.  It used to work.  Alex will probably try to reach out someone in Travis after the holidays.

This script
language: julia
os:
  - linux
  - osx
  - windows
arch:
  - x64
  - x86
matrix:
  exclude:
    - os: osx
      arch: x86
  allow_failures:
    - julia: nightly
julia:
  - 1.0
  - 1.3
  - nightly
notifications:
  email: false

seems to work on travis-ci.org, but not on travis-ci.com :confused:

seems to work on travis-ci.org, but not on travis-ci.com 😕

Hmm. If it works on .org but not on .com, presumably it's a problem on Travis's end?

@giordano @ararslan Did we ever figure this out?

Hmm. If it works on .org but not on .com, presumably it's a problem on Travis's end?

Yeah, as I understand it, deployment to .com and .org happens separately. It's likely that in this case, a change we need was not deployed to .com. I reached out to Travis but haven't yet heard back.

We use GitHub Actions now, so this can be closed.


How to remove components?

Is there any way to remove installed components safely?

What do you mean with components? How did you install it?


add url and timestamp to slack loader documents metadata

Description
Adds url and timestamp to slack loader documents so that you when you return source documents to a user they can get a link to the slack conversation with langchain and others.
Type of Change
Please delete options that are not relevant.

[x] Bug fix / Smaller change

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[x] I stared at the code and made sure it makes sense
[x] Tested locally

Suggested Checklist:

[x] I have performed a self-review of my own code
[x] My changes generate no new warnings
[x] I ran make format; make lint to appease the lint gods

@devinburnette I noticed we can remove url from extra_info if isn't set, can you open another PR with this improvement?

@EmanuelCampos so with the way I currently have it, if workspace_url isn't set, it just defaults to an empty string so URL still becomes /archive/channel/timestamp just without the base url prefixed, which still might be helpful to someone, but yea open to whatever you think is best.

Yea, i think it’s work well, don’t need a new PR, thanks


Cite/ref autocompletions stopped working with LaTeXZeta

After updating LaTeXTools to the latest version, cite/ref dropdown menu stopped appearing. I tried looking into LaTeXTools, but then figured that the issue might be caused by LaTeXZeta. Dropdown menu appears if and only if I remove LaTeXZeta.
I am running LaTeXTools v3.13.3 on ST3.

If you meant the automatic pop up, I would reproduce it. It would because LaTeXZeta provides a version of auto matching of {} which overwrites LaTeXTools defaults.
It will be fixed and meanwhile, you could use the keybind C+l, x to activate the menu.

v0.0.11 should fix it.


Bug in sales return

[x] edit not working
[x] without add items user is able to create sales return
[x] while creating new sales return , return receipt number showing like "NEW"
[x] reason field kept mandatory(but without filling it we can create new sales return)
[x] apply  to invoice not functioning
[x] some sort option is missing in the app(customer name & Balance)
[x] extra fields is available in app(payment terms and Additional charges)
[x] more option in sales return description page not working fine
[x] download option in sales return not working fine
[x] print option not working fine
[x] refund option not functioning
[x] in refund section required field not mentioned
[x] after creating,editing and deleting corresponding response message is not showing
[x] advanced search is not functioning,error messages are displayed and keyboard is not closing after search click
[x] remove normal search from listing page
[x] alignment issue in approve button
[x] REFUND option should be available upon - Draft ,Pending approval ,Approved ,Open

issue closed


Svn Support

Would be nice to be able to export/checkout repositories.

I might be needing export functionality in the future.
@patriksvensson do you prefer an addin using SharpSVN or a Tool in Cake.Common using the svn exe?

@mholo65 An SharpSVN addin would be a excellent place to start.

@mholo65 I was just away to say the same thing as @devlead :smile:

Yep, figured that since Git is available as an Addin, it would be rude to add SVN into Cake.Common :smile:

@mholo65 that is not to say that one, or both of them, won't be pulled into Common at some point in the future.  However, addin's are a good place to incubate extensions of Cake, and allow them to mature.

Addin work started here, can't say when it will be ready.

@mholo65 any news on this? I would like to check that everything is checked into the svn server before doing a produktion release!

@AnderssonPeter sorry, havent touched this in a looong while
Did only need svn export, but currently running it using Process.Start()
I have something done in this branch https://github.com/mholo65/Cake.Svn/tree/wip/export
If you would like to continue on it, I could have @gep13 transfer it to cake-contrib.

@mholo65 @AnderssonPeter if you want, happy to move that repo under the Cake-Contrib organisation, and to get you both added to the team associated with it.

A Cake.Svn addin has now been released.  You can find it here:
https://www.nuget.org/packages/Cake.Svn/


Add schema validation

This PR addresses https://github.com/powersync-ja/powersync-js/issues/431#issuecomment-2522158014.
Added a new Schema test which checks that an error is thrown when a Schema is created incorrectly.

Converting to a draft for now due to validation oversite


Bugfixes and feature updates

This PR contains fixes for two bugs:

When opening files that are already in the "Open Files" list, they would double up
When browsing FTP directories, the current and parent directory would double up

And a few feature upgrades that I felt were necessary:

When the package initialises, the "Open Files" list will get cleared
When browsing a host, the current directory will get saved, returning you to that directory when you browse the host again

I'm not sure if the features I added should be default behaviour, or if they should be added in as a Setting to let the user decide the behaviour.

This looks great! Good work :)
I think it would be beneficial if the two new features were disabled as default and toggleable in settings.
Do you think you could push that as well? That way I can just accept the PR

Updated again, previous features now have Settings that control their behaviour
I have also added a new setting which allows you to filter folders on top when browsing a directory, as well as a path indicator at the top of the modal.
Note: The current path is being placed in the error message div, this may not be ideal
I also removed the current directory entry that would appear, I felt that this is unnecessary since it doesn't really do anything.
Finally, I noticed that the modals that were being created were not being removed from the document after they had been dismissed, so I fixed this by calling destroy() on the panel when it is being destroyed

Great work. Thanks for the contribution :). Will push new version to atom.io shortly.


ec2/load balancer service controller

New ACK Service Controller
We utilize GitOps to deploy all assets by leveraging the aws-controllers-k8s framework. I did not find any controller which creates ALB. The closest match i found is this one which is not maintaned by your team.
a new controller to create AWS Load Balancer or add load balancer features in existing EC2 controller
Support for [service name]
EC2 (ALB and NLB)
List of API resources
List the API resources in order of importance to you:

ALB

kindly suggest any controller exists for creating ALB. if not is it possible to create new or amend existing EC2 controller to add ALB features?

I believe this is a duplicate of https://github.com/aws-controllers-k8s/community/issues/487

Thanks for your reply.
are you going to support creation of load balancers (ALB/NLB) without being tied to k8s ingress? i just want to create ALB directly.

@RedbackThomson Thanks for your reply.
are you going to support creation of load balancers (ALB/NLB) without being tied to k8s ingress? i just want to create ALB directly.

This is unlikely to happen any time soon, unfortunately. Just no resources to work on this :(


Selecting a preset in Assets Container is not stored

If I define a image manipulation preset, and then edit the container to select this preset it is not saved after clicking Save. When clicking Save the browser asks if I want to leave the page, and when it reloads the preset is not selected/saved.
Not 100% sure it is related to Eloquent Driver, but I've not had this problem on other sites.

I am facing the same issue. I see this is been two weeks now. Will it be merged?

This is available now in v2.1.0


[Fix] Hide __p9k_detect_os grep output on Android

This PR fixes #1007

I am not sure if that really makes the desired effect. If I do [[ ${(f)"$(</etc/os-release 2> /dev/null)"} =~ "ID=([A-Za-z]+)" ]] && echo "${match[1]}" || echo "nope", I get:
zsh: no such file or directory: /etc/os-release
nope

Alright. I fixed it by wrapping the redirect in Parentheses.. Thx @onaforeignshore


Mailcatcher just stopped working; Any ideas?

OS X: Yosemite
12:01 $ mailcatcher
Starting MailCatcher
==> smtp://<IP_ADDRESS>:1025
==> http://<IP_ADDRESS>:1080
/Users/orion.delwaterman/.rvm/gems/ruby-2.2.4/gems/eventmachine-<IP_ADDRESS>/lib/eventmachine.rb:1489:in `event_callback': undefined method `close' for 14:Fixnum (NoMethodError)
	from /Users/orion.delwaterman/.rvm/gems/ruby-2.2.4/gems/eventmachine-<IP_ADDRESS>/lib/eventmachine.rb:194:in `run_machine'
	from /Users/orion.delwaterman/.rvm/gems/ruby-2.2.4/gems/eventmachine-<IP_ADDRESS>/lib/eventmachine.rb:194:in `run'
	from /Users/orion.delwaterman/.rvm/gems/ruby-2.2.4/gems/mailcatcher-0.2.4/lib/mail_catcher.rb:21:in `run'
	from /Users/orion.delwaterman/.rvm/gems/ruby-2.2.4/gems/mailcatcher-0.2.4/bin/mailcatcher:44:in `<top (required)>'
	from /Users/orion.delwaterman/.rvm/gems/ruby-2.2.4/bin/mailcatcher:22:in `load'
	from /Users/orion.delwaterman/.rvm/gems/ruby-2.2.4/bin/mailcatcher:22:in `<main>'
	from /Users/orion.delwaterman/.rvm/gems/ruby-2.2.4/bin/ruby_executable_hooks:15:in `eval'
	from /Users/orion.delwaterman/.rvm/gems/ruby-2.2.4/bin/ruby_executable_hooks:15:in `<main>'

That's a very old version of mailcatcher: 0.2.4.
Please try upgrading: gem install mailcatcher

Mailcatcher have some  seriously problems. For example. It can work on cli environment but it is not work on web environment.
So I move to Mailhog. It is perfect fine now. Cheer.

Try this: bundle exec mailcatcher --http-ip <IP_ADDRESS>

According to the Readme: "Please don't put mailcatcher into your Gemfile"


Add news.adobe.com as known federal origin

Description
As part of the news.adobe.com migration, we want to add news.adobe.com as known federal origin as it was set up for federal from an akamai perspective
Resolves: MWPW-151236
Visuals

Test instructions
Milolibs don't work on news.adobe.com as the consumer has not set this up yet. Using local overrides to test this change is the most convenient and quickest method to verify this PR works as intended on the consuming pages.
Test link from @Ruchika4 : https://news.stage.adobe.com/news/news-details/test-redirect
Test URLs:

Before: https://main--milo--adobecom.hlx.live/?martech=off
After: https://mwpw-151236--milo--mokimo.hlx.live/?martech=off

@Ruchika4 is this good to go live/get merged at any point?
If you are on prod with milo/news.adobe.com but don't yet have the akamai prod settings ready, the navigations would 404.
If the akamai prod settings will be applied before you are going live, we can merge the milo PR at any point - would be nice if you can provide the "sign-off"

@Ruchika4 is this good to go live/get merged at any point? If you are on prod with milo/news.adobe.com but don't yet have the akamai prod settings ready, the navigations would 404. If the akamai prod settings will be applied before you are going live, we can merge the milo PR at any point - would be nice if you can provide the "sign-off" that we can merge this without causing any friction.

Hi @mokimo we currently don't have prod site up on akamai prod and akamai settings will be applied before we go live in September. Only stage news.stage.adobe.com has been set up. Current news.adobe.com site is hosted on cloudfare. I believe it should be ok to get this PR merged in main but please let me know if you see any issue.

@Ruchika4 that's perfect context, thanks!


Latest version

Hi,
I'm not not an Git expert...
I tried to get latest version of all modules by doing:
git clone https://github.com/maximkulkin/esp-homekit-demo.git
followed by
git submodule update --init --recursive
But if I look afterwards I see that homekit has not the latest version.
Submodule path 'components/homekit': checked out 'a592dc3587fb3b5b2f27d3ed068186cd6ec8d677'
And in a graphical tool I see:

How do I get the latest version?

Right click on the top line -> Checkout

Hi,
Yes that I know, but that could not be the way to work to get the latest version isn't it? If you follow the readme and execute some terminal commands you think you have the latest versions but that is not the case. What is the reason that the pointer is not pointed to the latest?

If there is no graphical tool, what is the correct command to get the latest version?

 The command for that is:
cd components/common/homekit
git pull origin master


MemoryError workaround

Kindly consider changing the def _expand_paragraphs function in the cdqa_sklearn.py file to accommodate larger datasets. Modifying the dataframe needs a lot of memory for bigger data so it would be better to set it as a list of dict before making it a dataframe.
Below is the modification I did so I would not get a MemoryError:
@staticmethod
def _expand_paragraphs(df):
     data=[]
     for n in range(len(df)):
         stringlist = df.iloc[n][1]
         for m in range(len(stringlist)):
             a=df.iloc[n][0]
             b=stringlist[m]
             data.append({'title' : a, 'content' : b})
     dfx = pd.DataFrame(data)
     return dfx

Very good point. +1 @nortz8
However, your workaround did not work for me. I ended up having the following;
ValueError: empty vocabulary; perhaps the documents only contain stop words
Any idea why  ?


Changed and added (a lot of...) Android functionality

Hi Gonzalo, thanks for the ground work you made.
I was in need of a plugin that uses the new GCM implementation. E.g. subscribing to topics was not possible with the (deprecated) phongegap-push-plugin.
So I found yours and reworked the Android part. It now has much more functionality and mimics the behaviour of phongegap-push-plugin in most of its parts.
Unfortunatly I don't think that the iOS implementation is still working because I changed your callback philosophy to an event based approach.
I hope you will merge this request and adjust the iOS code to my proposals.
Greetings,
André

Gonzalo, why don't you merge this?

Im reviewing this right now and testing, I will keep you posted throughout the day. Thanks @akreienbring for your contribution.

Any update on this @gonzaloaune ? Seems like a lot of good stuff here.

Yes, I'm actually updating the iOS side since this pull request broke that functionality. I expect to have it ready by later today.

Any update regarding this?

@gonzaloaune any update on your review? will be using your plugin if you get this merged :)

I'm also looking forward to this getting merged.

I moved to this plugin...
https://github.com/phonegap/phonegap-plugin-push/pull/282


Invalid access of discarded (invalid, deleted) uWS.HttpResponse/SSLHttpResponse

Here's a demo file for this error. It's just lists the files of a directory
const path = require('path')
const fs = require('fs')
const nanoexpress = require('nanoexpress')
const util = require('util')
const fsReadDir = util.promisify(fs.readdir)

const app = nanoexpress()
const port = 4000

// list the files of `storage/media` directory
app.get('/', async (req, res) => {
  let files = []

  try {
    files = await fsReadDir(path.resolve(__dirname, '../../storage/media'))
    return res.send({error: false, files})
  } catch (err) {
    return res.send({ error: true })
  }
})

// start server
;(async () => {
  try {
    await app.listen(port, '<IP_ADDRESS>')
  } catch (err) {
    console.error(err)
  }
})()

The problem is that every time that i run and the server and send a GET / request, the server throws these warnings
(node:5728) UnhandledPromiseRejectionWarning: Invalid access of discarded (invalid, deleted) uWS.HttpResponse/SSLHttpResponse.
(node:5728) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:5728) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

The problem happens when i call the fsReadDir. If i move the res.send before it, there wont be any warning.

Hi @nikosk93
What result do you get if change some lines?
const path = require('path')
const fs = require('fs')
const nanoexpress = require('nanoexpress')
const util = require('util')
const fsReadDir = util.promisify(fs.readdir)

const app = nanoexpress()
const port = 4000

// list the files of `storage/media` directory
- app.get('/', async (req, res) => {
+ app.get('/', async () => {
   let files = []

  try {
  files = await fsReadDir(path.resolve(__dirname, '../../storage/media'))
-   return res.send({error: false, files})
+   return {error: false, files}
  } catch (err) {
-   return res.send({ error: true })
+   return {error: true}
  }
})

// start server
;(async () => {
  try {
    await app.listen(port, '<IP_ADDRESS>')
  } catch (err) {
    console.error(err)
  }
})()

Also, i am added new example of your case.
For me, these changes fixed issue and works good.
Thanks for reporting.
Waiting feedback from you!
Have a nice day!

It works without throwing any warning 👍
Thanks for your quick response and this great project!

Thank you to reporting.
These issues appears lack of documentation and i will try to fix these issues and documentation when can find time.

@dalisoft I got same issue with following code. I was trying middlewares.
const nanoexpress = require('nanoexpress');

function one(req, res, next) {
  req.one = true;
  next();
}

function two(req, res, next) {
  req.two = true;
  next();
}

nanoexpress()
  .use(one, two)
  .get('/favicon.ico', _ => {})
  .get('/', (req, res) => res.send('Hello'))
  .get('/user/:id', (req, res) => {
    res.end(`User: ${req.params.id}`);
  })
  .listen(3000);

Hi @aprilcoskun and thanks for interesting and using this library.
This may be due of my cache mechanism or maybe issue relates to uWS and I don’t know exactly what happened currently, but i am will try to debug tomorrow, today cannot because of i am out of computer.
I tomorrow test, inspect and if possible i will fix this, if cannot, will add to docs about this bug.
Thanks for reporting, this helps this library improve quality and reduce bugs

@aprilcoskun
You can try now current changes as workaround
const nanoexpress = require('nanoexpress');

function one(req, res, next) {
  req.one = true;
  next();
}

function two(req, res, next) {
  req.two = true;
  next();
}

nanoexpress()
  .use(one, two)
- .get('/favicon.ico', _ => {})
+ .get('/favicon.ico', async () => {})
- .get('/', (req, res) => res.send('Hello'))
+ .get('/', (req, res) => res.end('Hello'))
  .get('/user/:id', (req, res) => {
    res.end(`User: ${req.params.id}`);
  })
  .listen(3000);

There even says error like this
UnhandledPromiseRejectionWarning: Invalid access of discarded (invalid, deleted) uWS.HttpResponse/SSLHttpResponse, response is responding/returning, but error does not disappearing, but i tried and seems cannot fix this issue, but i will add this to documentation as Known Issues

Update docs and i keep this project opened

Related issue here

@dalisoft I realized this caused when I try to reach req.params. Works fine when I don't call request object, It's looks like request object got deleted somewhere.

@aprilcoskun Thanks for info, i will research why it happens and if can, i will fix it

I added res.onAborted before res.send/res.end and the warnings gone
the problem is because the uWebSocket
"Every HttpResponse MUST have an attached abort handler IF you do not respond to it immediately inside of the callback. Returning from an Http request handler without attaching (by calling onAborted) an abort handler is ill-use and will termiante. When this event emits, the response has been aborted and may not be used."
https://unetworking.github.io/uWebSockets.js/generated/interfaces/httpresponse.html#onaborted
the same problem from uWebSockets github https://github.com/uNetworking/uWebSockets.js/issues/123

@Ganuzaz Thanks, it is already here https://github.com/dalisoft/nanoexpress/blob/master/src/handler/http.js#L91

@dalisoft warning still pops out when using sequelize to query.

@Ganuzaz, sorry, I don’t why it is happens, but PR is welcome

This was fixed in PRO version. In Simple/Free version PR is welcome.

@nikosk93 This issue was fixed in v1.1.1 for Simple version.
Sorry for late delay and thanks for your patience!


Homepage Help Component

Add a rich text component on the home page with a link to the OCC Help Desk on Trailblazer. See instructions in post install instructions for 1.2.

Text that Shelly has used:
OCC Community Help Desk
Click this link to join the Trailhead - Ombudsman Cloud Care Community Group to ask questions, connect with others, share success stories, and more.
https://ombudcare.com/OCC-Community-Help-Desk

Also, please add this Google Doc to the Help Component.
https://docs.google.com/forms/d/e/1FAIpQLSc5f8vR_0Z7lGuzD0EyHHW0LbgZTW2kmo7nyQ2y9vFqCE9-ag/viewform?usp=sf_link
It's our Help Ticket form, so OMB have 2 ways to get their questions answered.


feedback for hosted portal dataset page

Saw that feedback is welcome, so here I am:
Referring to: https://hp-antarctic.gbif-uat.org/occurrence/search?view=DATASETS
What I like
I find the organization very neat and it is much more readable than the previous overlay. I very much appreciate this! The different tabs of About, Project, Citations, Download are similar to gbif.org so I find it to be quite intuitive! The little info tag is very thoughtful and it is enough to catch the attention of user.
What can be improved
Better wording in the info tag

I expected to see an explanation on why not all records are in hosted portal when I clicked on it, but it leads me to the dataset on GBIF.org. So perhaps something like view full dataset on GBIF.org will make the intention more explicit, or link it to a page explaining why not all records from the dataset is included in the hosted portal.
Differentiate the occurrence count from hosted portal and from full dataset

I was a little confused by the occurrence count. I think it would be helpful to make it more obvious that the count is from full dataset in the drawer. Or make everything consistent with the occurrence count from the hosted portal and link the occurrences to the scoped version in the hosted portal (e.g. https://hp-antarctic.gbif-uat.org/occurrence/search?datasetKey=7d4ed8b7-f31f-4133-a848-6a315ecfe7cc&view=TABLE)?
awkward bounding box for Geographic scope

The bounding box of this dataset is a little awkward: SCAR Biogeographic Atlas of the Southern Ocean - Porifera - Data
but it looks fine on IPT

Meaning of colours in charts

When looking at this chart, I am not sure if the colours have any meaning? If there is, perhaps some legend will be helpful!
Differentiate DOI to GBIF and preferred DOI

I think it will be helpful to differentiate preferred identifier and the doi to GBIF because that will help the users to decide to go to GBIF for full dataset (since occurrences in hosted portals are scoped) or to see the dataset homepage hosted elsewhere.
Data richness and Issues and flags present related information

I am thinking whether it would be helpful to position these 2 closer to each other because I feel the information presented by both are related? Also I had a question when I saw Identified to species, not sure whether the count is based on interpreted data (based on taxon match to GBIF Backbone Taxonomy) or was it based on provided data (verbatim)? Nonetheless I think the info from both data richness and issues and flags are useful!
I hope this is helpful! Thank you so much for your hard work Morten!!

Thank you @ymgan
info box text
Do you have a suggestion for what the text should be instead?
Differentiate the occurrence count from hosted portal and from full dataset
That is what the info box was intended to do.
The counts on the dataset tab shows a list of datasets that contribute data to a given query. Not how many there is on the hosted portal. Though that is the number if you have no filters added.
e.g. https://hp-antarctic.gbif-uat.org/occurrence/search?taxonKey=1005624&view=DATASETS
When clicking the dataset it will show information about the Dataset,
So Biological observations from the Discovery Investigations 1925-1952 will show a larger number than 11, that is just the number of occurrences for Klugeflustra antarctica (26K is included on the site and the dataset total is 38K)
Then there is the question about wether the dataset show be a subset view of the published dataset that match the scope of the website. I think that is a slippery slope that will never be a good solution. For many reasons:
The geographic scope will show data in areas that might not be included on your site. Similar for the description, taxonomic scope, temporal scope etc. Citations too will be wrong because they will be citations of records in the dataset that isn't part of the hosted portal site. Downloading the archive will include other counts than what the site then states. And lastly I'm not sure the publisher of the dataset will want 50 different representation of their dataset with different data counts etc.
I think the only feasible solution in the long run is to inform the user about what they are looking at. That is the text you are writing :)
awkward bounding box for Geographic scope
Indeed it looks odd. I will replace it with something else at some point. Currently we just use the MapBox static image API, but that has issues as you see. It is just so wonderfully simple to use. A plain html image.
Meaning of colours in charts
You are not the only one to comment on that. I should add tooltips. Or remove it.
I can tell you what it is, and then you can help decide what to do.
This dataset has 38.000 records
The most frequent country has 12.000 records, so roughly 30%. That is the dark hue. Page 2 becomes a very boring chart as Angola: 180 wouldn't even show.
Alternatively I can choose to scale the results on a given page so that the top value is a full bar, and everyone else is relative to that. But then each new page start over with what looks like 100%. That is the light hue. We can now see that Angola is 6 times as frequent as Gambia.
What should the tool tips say? Or should we remove one of the colors?
page 1

page 2

DOI
I'm not sure I understand actually. Could you expand please? Would you like a more prominent link to the GBIF.org website version? If so I tend to agree.
Chart ordering
Why do you feel like these 2 are more related than say data richness and event date?
The reason I added it last is because I wanted it to be easy to find, but not starting out with highlighting issues first. It felt impolite. I want the dataset publisher to be happy with how we present their work.
Identified to species
It is based on interpreted data. I do not believe I ca tell anything from the verbatim scientific name without interpreting it. We can add a tooltip or such? I think it might also have a bug btw: https://github.com/gbif/gbif-web/issues/339

info box text

Do you have a suggestion for what the text should be instead?

What do you think about having a general information part (not customizable) and a custom information part that can be customized by each hosted portal? For example

(start of general part) Not all records from the dataset is included on this site. Visit GBIF.org  for more information on hosted portals. (end of general part) (start of custom markdown) This portal's scope is detailed in the FAQ. (end of custom markdown)

something like that?
Differentiate the occurrence count from hosted portal and from full dataset

I think the only feasible solution in the long run is to inform the user about what they are looking at. That is the text you are writing :)

You are absolutely right about this!
awkward bounding box for Geographic scope

Indeed it looks odd. I will replace it with something else at some point. Currently we just use the MapBox static image API, but that has issues as you see. It is just so wonderfully simple to use. A plain html image.

I totally understand that! Thank you so much for looking into it!
Meaning of colours in charts
Ah, I understand now ... In my humble opinion, the pie chart is more visual for the percentage. I feel it is already hard to point for South Africa which ranked 5th in the dataset, so tooltip will be difficult to use. If it is me, I will prefer to keep only one colour and let pie chart handles the percentage.
DOI

Would you like a more prominent link to the GBIF.org website version? If so I tend to agree.

Yes exactly! Of course you did not understand, because I made a mistake in the previous screenshot 🙈 (sorry about that!) Both DOI of the dataset in the red rectangles point to the dataset home page. It is not obvious to me that the GBIF logo at the bottom means "view dataset on GBIF". So yes please for a more prominent link to the GBIF.org website version!
Chart ordering

Why do you feel like these 2 are more related than say data richness and event date?

I guess I was thinking that if continent and country can be derived from coordinates, it means those records are with coordinates. But I clearly was not thinking straight because datasets with continent and country filled in will not have those flags. So please ignore what I said in the previous comment.

The reason I added it last is because I wanted it to be easy to find, but not starting out with highlighting issues first. It felt impolite. I want the dataset publisher to be happy with how we present their work.

You are absolutely right on this! Thank you for being so considerate, I really appreciate that!
Identified to species

It is based on interpreted data. I do not believe I ca tell anything from the verbatim scientific name without interpreting it. We can add a tooltip or such? I think it might also have a bug btw: https://github.com/gbif/gbif-web/issues/339

Right! Got it! I was thinking differently! I thought it was about the count based on the value of taxonRank == "species" 🙈 Thank you for looking into the possible bug!

Thank you for your detailed comments @ymgan
Issue for charts bars: https://github.com/gbif/gbif-web/issues/345
Info box: I've updated the text and you can overwrite it by adding a custom message in your site config.
I've done so here https://github.com/gbif/hp-antarctic/commit/097e3737a7e0903769ce58b4423c88bfd2d1e2e8
Example: https://hp-antarctic.gbif-staging.org/occurrence/search?datasetKey=96385e98-93b5-4e4a-8081-6e30b738816a&view=DATASETS
Identified to species: you are completely right. That is essentially what it does. It could just as well have been as you say, except I do not have access to the publisher provided info I believe. We can add an explanation, I just need to find a way to do so that doesn't create too much clutter. Having explanations all over the place can be a bit overwhelming, and kind of do the opposite of being helpful.

Feel free to open a new issue if needed. I think I have addressed all of above and deployed it to staging. The geographic scope, is still pending a better solution than mapbox


port rest-json quickstart to camel-quarkus

Fixes #118

@ppalaga fixed (except the legumes thing)

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/camel-quarkus-pr/220/

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/camel-quarkus-pr/221/


cat: /var/vcap/instance/name: No such file or directory

$ bosh ssh --gateway_host <IP_ADDRESS> --gateway_user vcap --gateway_identity_file ~/Projects/bosh_deployments/bosh-lites/sshkeys/bosh-lites.pem
...
cat: /var/vcap/instance/name: No such file or directory
cat: /var/vcap/instance/id: No such file or directory

I've upgraded my bosh-lite to v260.3, I've uploaded the latest warden stemcell, and I'm using the latest bosh v1 cli. What else is required for /var/vcap/instance/name and /var/vcap/instance/id files to be created for the PS1 to be setup correctly? (there is no /var/vcap/instance/ folder created)
Update: I see You are using CLI > 1.2579.0 with a director that doesn't support the new version format you are using. Upgrade your director to match the version of your CLI or downgrade your CLI to 1.2579.0 to avoid versioning mismatch issues. during a deployment. But looking at the parent director which deploys the bosh-lite I see that its the latest v260.3:
| bosh-lite-45              | bosh-warden-cpi/30            | bosh-vsphere-esxi-ubuntu-trusty-go_agent/3262.7  | none         |
|                           | bosh/260.3                    |                                                  |              |
|                           | garden-runc/1.0.0             |                                                  |              |
|                           | port-forwarding/5             |                                                  |              |

@drnic yup. that's the result (cosmetic) of warden stemcells having older agent temporarily. there is a story to address that: https://www.pivotaltracker.com/story/show/134182747.

Ok cool thx
On Mon, Jan 16, 2017 at 3:24 PM -0800, "Dmitriy Kalinin"<EMAIL_ADDRESS>wrote:
@drnic yup. that's the result (cosmetic) of warden stemcells having older agent temporarily. there is a story to address that: https://www.pivotaltracker.com/story/show/134182747.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

I believe this was fixed by https://github.com/cloudfoundry/bosh-linux-stemcell-builder/commit/c7b403b0aced4785cb8261fa2ecf525448bfc689.


MongoFlyway migrations for users with readWrite privileges

We want to run mongoFlyway with a user who has only readWrite privileges.

done.


Copy code block ability

Within the page, it would be useful if there were a button to copy entire code blocks.
E.g.

Already requested in https://github.com/dullage/flatnotes/issues/27. Will close to avoid duplicates.


[Python] Generated namedtuple types have unsat docstrings.

From: https://github.com/googleapis/google-cloud-python/issues/7043
The members of a collections.namedtuple have no semantic information in their docstrings:
>>> import collections
>>> Foo = collections.namedtuple("Foo", ["bar", "baz", "qux"], verbose=True)
class Foo(tuple):
    'Foo(bar, baz, qux)'

    __slots__ = ()

    _fields = ('bar', 'baz', 'qux')

    def __new__(_cls, bar, baz, qux):
        'Create new instance of Foo(bar, baz, qux)'
        return _tuple.__new__(_cls, (bar, baz, qux))

    @classmethod
    def _make(cls, iterable, new=tuple.__new__, len=len):
        'Make a new Foo object from a sequence or iterable'
        result = new(cls, iterable)
        if len(result) != 3:
            raise TypeError('Expected 3 arguments, got %d' % len(result))
        return result

    def __repr__(self):
        'Return a nicely formatted representation string'
        return 'Foo(bar=%r, baz=%r, qux=%r)' % self

    def _asdict(self):
        'Return a new OrderedDict which maps field names to their values'
        return OrderedDict(zip(self._fields, self))

    def _replace(_self, **kwds):
        'Return a new Foo object replacing specified fields with new values'
        result = _self._make(map(kwds.pop, ('bar', 'baz', 'qux'), _self))
        if kwds:
            raise ValueError('Got unexpected field names: %r' % kwds.keys())
        return result

    def __getnewargs__(self):
        'Return self as a plain tuple.  Used by copy and pickle.'
        return tuple(self)

    __dict__ = _property(_asdict)

    def __getstate__(self):
        'Exclude the OrderedDict from pickling'
        pass

    bar = _property(_itemgetter(0), doc='Alias for field number 0')

    baz = _property(_itemgetter(1), doc='Alias for field number 1')

    qux = _property(_itemgetter(2), doc='Alias for field number 2')

@lukesneeringer Assigning to you, but please feel free to reassign. Also, I was unsure whether this would be fixed in gapic-generator, or if the fix will be provided as part of gapic-generator-python.

FWIW, I created a pull request that handles this via the synth file. We might want to close this issue.

@plamut Rather than adding those docstrings in synth.py, it would be preferable to have the generator use whatever comments are in the .proto files for the enums to generate them upstream.

@tseaver After working with synth for a bit, I cannot disagree - I'll be happy to remove that part form it once the generator is updated.


Add setup Travis CI for tracking build docs, and install

I make PR for adding setup Travis CI to track build docs, and install.

You should enable travis run on https://travis-ci.org/

Relate to #429


Refs #33482 -- Fixed QuerySet selecting and filtering againts Exists() with empty queryset.

Thanks Tobias Bengfort for the report.

Seems that Oracle is happy about that 🎉

@charettes Thanks :+1: Looks good :rocket:


Refactor app.tsx into smaller React modules

Refactoring the app.tsx codebase into many different react modules each in charge of their own state and properties (the way we should be using react).
This PR is tied in with another small feature to add a detail view in the home screen for better browsing.
There are also a number of small accessibility fixes around the accessibility menu in the home screen (to show a different one that is representative of the actions a user can take on the home screen).
This PR requires a bunch of updates to our targets. I will prepare a number of target PRs.
I've started optimizing each component to only re-render if a state that it cares about has changed, but there's probably more to be optimized.
Fixes https://github.com/Microsoft/pxt/issues/3271, Fix cookie close icon

Add a warning comment on every state class that implements a custom "shouldUpdate" function that it should also be updated.


fix: problems with account action titles for delete and hide an account

Summary
This PR fixes the bug that causes the app to freeze when the hide action is selected.
Additionally, it centers the title of the deleted wallet action
Changelog
- Added classes attribute to hide wallet title and added necessary tailwind classes
- Centered delete wallet action title

Relevant Issues
Closes #3939
Testing
Platforms

Please select any platforms where your changes have been tested.

Desktop

[ ] MacOS
[ ] Linux
[ ] Windows

Mobile

[x] iOS
[x] Android

Instructions

Please describe the specific instructions, configurations, and/or test cases necessary to test and verify that your changes work as intended.

...
Checklist

Please tick all of the following boxes that are relevant to your changes.

[x] I have followed the contribution guidelines for this project
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have added or modified tests that prove my changes work as intended
[ ] I have verified that new and existing unit tests pass locally with my changes
[ ] I have verified that my latest changes pass CI workflows for testing and linting
[ ] I have made corresponding changes to the documentation

I can't reproduce it 😅 where is the fix for the app crash? I can see only the css center code.

The fix is actually the css center code 😅 The tailwind classes were added to the type attribute not the classes attribute. That causes the crash, when the component has loaded.

I think I discovered another issue here. To match desktop behavior, when we create a new wallet, the other wallet should allow to be hidded and currently it shows the delete option rather than the hide option.

Yeah, I discovered the same while fixing the crash:
https://github.com/iotaledger/firefly/issues/3998

We could have a call to discuss it well tomorrow

Sounds good, just schedule when it fits for you 👍

The fix is actually the css center code sweat_smile The tailwind classes were added to the type attribute not the classes attribute. That causes the crash, when the component has loaded.

Ahh 😄 perfect then I'll test that right now!

I think I discovered another issue here. To match desktop behavior, when we create a new wallet, the other wallet should allow to be hidded and currently it shows the delete option rather than the hide option.

I discovered the same while fixing the crash and was wondering as well:
#3998

Awesome just added it to TODO colomn, so let's merge it asap

We could have a call to discuss it well tomorrow

Sounds good, just schedule when it fits for you +1

maybe we could talk about it tomorrow better, thanks!


Improved design for the initial import process: common entry page (file import, external source, manual entry)

Is your feature request related to a problem? Please describe.
The current workflows for importing publications differ widely in these cases:

import metadata from a file
manually fill the metadata
import metadata from an external source

So it isn't easy for the user to understand the workflow of the different buttons/options at one glance.
Describe the solution you'd like
We would prefer an optional and configurable solution which proceeds via a common entry page containing input components for all three cases, with the entity type and collection selected beforehand (so we can route directly to the entry page for a specific collection). On the common page, the user would immediately see all possible sources/identifier types (see #2136 ) as well as options for uploading a RIS/BibTeX file or manual entry.
If the collection is not determined by the entity type or link, we would continue to offer a selection menu as in the current implementation (but if it is, we can skip the menu)
After completing the submission, we would like the user to be able to return to the common entry page to add additional items or files.
Additional context
Current workflow (starting point):

Proposed workflow for importing items/files:
Step 1: Go to "MyDSpace"
Step 2: Select "New Publication" (this selects the collection and entity type as well)

In our case we have only one collection for this entity type (publication). But if the collection is not determined by the entity type or link, we would continue to offer a selection menu as in the current implementation (but if it is, we can skip the menu).

Step 3: Common entry page with separate options

Manuell eintragen = manual entry; getting into the submission without any prefilled metadata
Suche                       = Search (for this row‘s identifier type in external sources)
Importieren von Metadaten via BibTeX/RIS = Import metadata from BibTeX/RIS file
Step 4: Submission
Further context: https://github.com/DSpace/DSpace/issues/8674

@philipprumpf : It's unclear to me how this ticket and #2136 differ?  Aren't these duplicate tickets now?

@tdonohue : I have closed #2136 because it was meant as a subticket which is not strictly necessary.

Moving this over to "needs discussion" as this redesign would require a larger amount of work (likely starting with prototypes / mock ups of a better workflow).  It's a good idea, but don't have a way to schedule it until a volunteer decides to lead the discussion.


Modify uploaded data

Hi Wei,
When I tried to modify the data I uploaded previously, I got this error (image below)

Would you take a closer look if it is because I have already changed once, or some other issues seem from zenodo
@oeway

Could you please post the error in the browser console (https://balsamiq.com/support/faqs/browserconsole/) when reporting issue? A screenshot is not enough to check the issue.
For this issue, because I made substantial changes to the saving format, I think the best way is you upload a new one. I will remove this existing one from shareloc.

Here is the screenshot and the detailed report
I will upload a new smlm file, in any case, thank you
@oeway

app.0ff1e47f.js?__WB…957957bfebb08080d:1 TypeError: Cannot read property 'samples' of undefined
    at app.0ff1e47f.js?__WB…957957bfebb08080d:1
    at l (chunk-vendors.1b1f56…7cb868b69fb2a795:43)
    at Generator._invoke (chunk-vendors.1b1f56…7cb868b69fb2a795:43)
    at Generator.next (chunk-vendors.1b1f56…7cb868b69fb2a795:43)
    at n (chunk-vendors.1b1f56…07cb868b69fb2a795:1)
    at s (chunk-vendors.1b1f56…07cb868b69fb2a795:1)
| (anonymous) | @ | app.0ff1e47f.js?__WB…957957bfebb08080d:1
-- | -- | -- | --
  | l | @ | chunk-vendors.1b1f56…7cb868b69fb2a795:43
  | (anonymous) | @ | chunk-vendors.1b1f56…7cb868b69fb2a795:43
  | (anonymous) | @ | chunk-vendors.1b1f56…7cb868b69fb2a795:43
  | n | @ | chunk-vendors.1b1f56…07cb868b69fb2a795:1
  | c | @ | chunk-vendors.1b1f56…07cb868b69fb2a795:1
  | Promise.then (async) |   |
  | n | @ | chunk-vendors.1b1f56…07cb868b69fb2a795:1
  | s | @ | chunk-vendors.1b1f56…07cb868b69fb2a795:1
  | Promise.then (async) |   |
  | n | @ | chunk-vendors.1b1f56…07cb868b69fb2a795:1
  | s | @ | chunk-vendors.1b1f56…07cb868b69fb2a795:1
  | (anonymous) | @ | chunk-vendors.1b1f56…07cb868b69fb2a795:1
  | (anonymous) | @ | chunk-vendors.1b1f56…07cb868b69fb2a795:1
  | loadRdfFromURL | @ | app.0ff1e47f.js?__WB…957957bfebb08080d:1
  | (anonymous) | @ | app.0ff1e47f.js?__WB…957957bfebb08080d:1
  | l | @ | chunk-vendors.1b1f56…7cb868b69fb2a795:43
  | (anonymous) | @ | chunk-vendors.1b1f56…7cb868b69fb2a795:43
  | (anonymous) | @ | chunk-vendors.1b1f56…7cb868b69fb2a795:43
  | n | @ | chunk-vendors.1b1f56…07cb868b69fb2a795:1
  | s | @ | chunk-vendors.1b1f56…07cb868b69fb2a795:1
  | (anonymous) | @ | chunk-vendors.1b1f56…07cb868b69fb2a795:1
  | (anonymous) | @ | chunk-vendors.1b1f56…07cb868b69fb2a795:1
  | startFromDepositURL | @ | app.0ff1e47f.js?__WB…957957bfebb08080d:1
  | mounted | @ | app.0ff1e47f.js?__WB…957957bfebb08080d:1
  | it | @ | chunk-vendors.1b1f56…07cb868b69fb2a795:7
  | Fi | @ | chunk-vendors.1b1f56…07cb868b69fb2a795:7
  | insert | @ | chunk-vendors.1b1f56…07cb868b69fb2a795:7
  | N | @ | chunk-vendors.1b1f56…07cb868b69fb2a795:7
  | (anonymous) | @ | chunk-vendors.1b1f56…07cb868b69fb2a795:7
  | (anonymous) | @ | chunk-vendors.1b1f56…07cb868b69fb2a795:7
  | n | @ | chunk-vendors.1b1f56…07cb868b69fb2a795:7
  | (anonymous) | @ | chunk-vendors.1b1f56…07cb868b69fb2a795:7
  | (anonymous) | @ | chunk-vendors.1b1f56…07cb868b69fb2a795:7
  | Ki | @ | chunk-vendors.1b1f56…07cb868b69fb2a795:7
  | (anonymous) | @ | chunk-vendors.1b1f56…07cb868b69fb2a795:7
  | lt | @ | chunk-vendors.1b1f56…07cb868b69fb2a795:7
  | Promise.then (async) |   |
  | rt | @ | chunk-vendors.1b1f56…07cb868b69fb2a795:7
  | mt | @ | chunk-vendors.1b1f56…07cb868b69fb2a795:7
  | Ji | @ | chunk-vendors.1b1f56…07cb868b69fb2a795:7
  | (anonymous) | @ | chunk-vendors.1b1f56…07cb868b69fb2a795:7
  | (anonymous) | @ | chunk-vendors.1b1f56…07cb868b69fb2a795:7
  | set | @ | chunk-vendors.1b1f56…07cb868b69fb2a795:7
  | (anonymous) | @ | chunk-vendors.1b1f56…7cb868b69fb2a795:43
  | (anonymous) | @ | chunk-vendors.1b1f56…7cb868b69fb2a795:43
  | (anonymous) | @ | chunk-vendors.1b1f56…7cb868b69fb2a795:43
  | (anonymous) | @ | chunk-vendors.1b1f56…7cb868b69fb2a795:43
  | (anonymous) | @ | chunk-vendors.1b1f56…7cb868b69fb2a795:43
  | n | @ | chunk-vendors.1b1f56…7cb868b69fb2a795:43
  | n | @ | chunk-vendors.1b1f56…7cb868b69fb2a795:43
  | Fe | @ | chunk-vendors.1b1f56…7cb868b69fb2a795:43
  | (anonymous) | @ | chunk-vendors.1b1f56…7cb868b69fb2a795:43
  | n | @ | chunk-vendors.1b1f56…7cb868b69fb2a795:43
  | (anonymous) | @ | chunk-vendors.1b1f56…7cb868b69fb2a795:43
  | (anonymous) | @ | chunk-vendors.1b1f56…7cb868b69fb2a795:43
  | (anonymous) | @ | chunk-vendors.1b1f56…7cb868b69fb2a795:43
  | m | @ | chunk-vendors.1b1f56…7cb868b69fb2a795:43
  | n | @ | chunk-vendors.1b1f56…7cb868b69fb2a795:43
  | n | @ | chunk-vendors.1b1f56…7cb868b69fb2a795:43
  | n | @ | chunk-vendors.1b1f56…7cb868b69fb2a795:43
  | Fe | @ | chunk-vendors.1b1f56…7cb868b69fb2a795:43
  | (anonymous) | @ | chunk-vendors.1b1f56…7cb868b69fb2a795:43
  | (anonymous) | @ | chunk-vendors.1b1f56…7cb868b69fb2a795:43
  | (anonymous) | @ | chunk-vendors.1b1f56…7cb868b69fb2a795:43
  | (anonymous) | @ | chunk-vendors.1b1f56…7cb868b69fb2a795:43
  | (anonymous) | @ | chunk-vendors.1b1f56…7cb868b69fb2a795:43
  | run | @ | app.0ff1e47f.js?__WB…957957bfebb08080d:1
  | click | @ | app.0ff1e47f.js?__WB…957957bfebb08080d:1
  | it | @ | chunk-vendors.1b1f56…07cb868b69fb2a795:7
  | i | @ | chunk-vendors.1b1f56…07cb868b69fb2a795:7
  | (anonymous) | @ | chunk-vendors.1b1f56…07cb868b69fb2a795:7
failurehttps://shareloc.xyz/js/chunk-vendors.1b1f56da.js.maphttps://shareloc.xyz/js/chunk-vendors.1b1f56da.js?__WB_REVISION__=f8c07cb868b69fb2a795HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILUREfailurehttps://shareloc.xyz/js/app.0ff1e47f.js.maphttps://shareloc.xyz/js/app.0ff1e47f.js?__WB_REVISION__=219957957bfebb08080dHTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILUREsuccesshttps://imjoy-team.github.io/vue-js-modal/index.js.maphttps://imjoy-team.github.io/vue-js-modal/index.js154 814successhttps://cdn.jsdelivr.net/npm/imjoy-core<EMAIL_ADDRESS>167 962successhttps://cdn.jsdelivr.net/npm/imjoy-rpc<EMAIL_ADDRESS>292successhttps://imjoy-team.github.io/jupyter-engine-manager/index.bundle.js.maphttps://imjoy-team.github.io/jupyter-engine-manager/index.bundle.js?version=0.4.133 242 704successhttps://storage.googleapis.com/workbox-cdn/releases/4.3.1/workbox-sw.js.maphttps://storage.googleapis.com/workbox-cdn/releases/4.3.1/workbox-sw.js6 916successhttps://storage.googleapis.com/workbox-cdn/releases/4.3.1/workbox-core.prod.js.maphttps://storage.googleapis.com/workbox-cdn/releases/4.3.1/workbox-core.prod.js50 145successhttps://storage.googleapis.com/workbox-cdn/releases/4.3.1/workbox-precaching.prod.js.maphttps://storage.googleapis.com/workbox-cdn/releases/4.3.1/workbox-precaching.prod.js35 842failurehttps://shareloc.xyz/plugin.webworker.js.mapblob:https://shareloc.xyz/84da1a55-26ae-401d-8c89-dfe4bc817070Fetch through target failed: Target not supported; Fallback: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILUREsuccesshttps://cdnjs.cloudflare.com/ajax/libs/axios/0.19.2/axios.min.maphttps://cdnjs.cloudflare.com/ajax/libs/axios/0.19.2/axios.min.js115 513Fetch through target failed: Target not supported; Fallback:

Hello,
Maybe it's already on the way, just in case: when I try to upload the data, community metadata is not found, could you please tell me when it's ready ? thanks alot
@oeway

Wait, I just removed the community because I need to create a new one with
the new email.
On Thu, 8 Jul 2021 at 11:11, Jiachuan Bai @.***> wrote:

Hello,
Maybe it's already on the way, just in case: when I try to upload the
data, community metadata is not found, could you please tell me when it's
ready ? thanks alot
@oeway https://github.com/oeway
[image: image]
https://user-images.githubusercontent.com/56833522/124895814-2e26e700-dfdd-11eb-987d-56452053189d.png
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/imodpasteur/ShareLoc.XYZ/issues/17#issuecomment-876272231,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AADU3S7POF4WDS4OSIISAG3TWVTUBANCNFSM4745BYJQ
.

@baiddd All the issues have been resolved, please upload a new dataset.

Ok, thank you :) I will close this issue


Specify ONNX model zoo in validated model list

Type of Change
documentation
Description
Specify ONNX model zoo in validated model list
Expected Behavior & Potential Risk
the expected behavior that triggered by this PR
How has this PR been tested?
how to reproduce the test (including hardware information)
Dependency Change?
no

@mengniwang95 These models are missed in validated_model_list.md:


Epic Store: installing Tony Hawk results in Error 500

I am trying to install Tony Hawk's™ Pro Skater™ 1 + 2 from Epic Store. I am using ChimeraOS stable v43.
After clicking the "Install" button I get the following error:

Maybe it is because of the title of the game? If you can point me to the log file I can give you further information.

With stable v44 installing works fine. Therefore I close this issue.


Patch request clarification on change plan for SaaS

https://docs.microsoft.com/en-us/azure/marketplace/partner-center-portal/pc-saas-fulfillment-api-v2#provisioning-for-update-when-its-initiated-from-the-marketplace
Patch request clarification. Should the ISV make both calls for the market place to charge the customer on the changes to a subscritpion. I mean looking at the description in the above link, once a call is sent to subscription patch(change plan) endpoint, ISV waits for the notification  on the webhook and after manually provisioning for the requested change according to the new plan, they will need to call a patch on the same operation received on the webhook to indicate this change of plan is complete. Untill then the customer is not charged for the changed plan? If yes I would like to know if this applies to all changes and states received on the webhook like:
Unsubscribe (when the resource has been deleted)
ChangePlan (when the change plan operation has completed)
ChangeQuantity (when the change quantity operation has completed)
Suspend (when resource has been suspended)
Reinstate (when resource has been reinstated after suspension)

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

ID: fe8750da-cb47-7396-8d1b-0abff019a0be
Version Independent ID: b19143ed-64c0-1554-5ac9-610513382609
Content: SaaS Fulfillment API v2
Content Source: articles/marketplace/partner-center-portal/pc-saas-fulfillment-api-v2.md
Service: marketplace
GitHub Login: @qianw211
Microsoft Alias: evansma

@santhoshbomma9 Thanks for the comment! We will investigate on this issue and get back to you soon.

adding @qianw211 for input.

Any update please?

any update on this please? It has been 3 months

adding @ellacroi for input.

#please-close We're updating the SaaS docs, and this issue will be fixed by then.


Add pictures to Bilbao post

This is quite experimental, since I'm only using the online UI...
But I tested it in my play-repo so it should work actually...^^

I think I did it! ^_^
But I'm not yet confident enough to just merge, so I'll wait for your response anyways, Nick... (Yep, not sending a notification was intended. This is not super urgent, is it..?)

Looks perfect!


global.scss dosen't work

i try to modify the lib/views/global.scss to skinning terriaMap but the build doesn't change, i use yarn gulp dev, i read that the .tjs-xxx styles overload is not compatible with terriajs 8 , how can i modify components style ?

Hi @luca-moscatelli,
Since most components are being migrated from scss to styled-components, it is no longer possible to style them using global.scss. Some of the new theming parameters can be set through the wwwroot/config.json file. Here's an example gist. Let me know if that works for you.


Update inline-css plugin (pull request #16, should solve issue #8)

https://github.com/jonkemp/inline-css/pull/16
https://github.com/jonkemp/inline-css/issues/8

Issues fixed;
@todo bump packages when https://github.com/jonkemp/gulp-inline-css/issues/29 is closed

✅  Merge in all the goodies, including what's gonna come from https://github.com/jonkemp/inline-css/pull/40
✅ Get rid of some redundant inline CSS + comments all over the source code


a is not a function

I'm running wonka within my application, and occasionally this error pops up and crashes my app running locally:
////node_modules/wonka/dist/wonka.js:608
          c.forEach(function (c) {
            ^
TypeError: a is not a function
    at ////node_modules/@urql/core/src/exchanges/fetch.ts:36:17
    at ////node_modules/wonka/dist/wonka.js:167:16
    at ////node_modules/wonka/dist/wonka.js:482:60
    at ////node_modules/wonka/dist/wonka.js:609:13
    at Array.forEach (<anonymous>)
    at b (////node_modules/wonka/dist/wonka.js:608:13)
    at ////node_modules/wonka/dist/wonka.js:1146:42
    at ////node_modules/wonka/dist/wonka.js:630:31
    at ////node_modules/wonka/dist/wonka.js:180:49
    at h (////node_modules/wonka/dist/wonka.js:163:57)

I saw a similar issue here, however I believe we are using suspense
Any help would be greatly appreciated, as it is causing a bad developer experience
Thanks

@kitten any ideas?

Without a reproduction there's not much I can do. Unless you're using Wonka independently though, this is more of a question to post ok the urql repo. On the other hand though, the caveat here is that it must be an issue with the build process or repo itself you may have inadvertently caused here.
However, since the stacktrace here doesn't include call sites, code, and isn't pointing at the correct line even, I can't even guess what's going on 😅

Any luck with this @kitten? We're still facing it a year later and didn't get the answer from the other repo

@shukii Not sure when why this is happening but I'm preparing the repository to move over to TypeScript. urql will move over with the next major bump which will also ditch IE11 support and target ES2015 only.
I've tried this out, and if your environment is set up for it correctly, you should now get full sourcemaps on Wonka. So, potentially, a much easier time debugging.
That said, without a reproduction I can't help you here further myself. This is likely caused by a faulty exchange, faulty usage that shouldn't pass type checks, or an old version/bug that's fixed already 😅


request and response section of network tab inside devtools always shows blank

Steps to Reproduce
#121133 its still happen

Hello @dipakp2726. I am unable to reproduce this issue. Can you reproduce this on the master channel? You can use https://jsonplaceholder.typicode.com/ for your HTTP request

not on master channel but its happening on stable and beta channel.

Then this issue is fixed in master. It will be included as a fix to a future stable version. Since it's fixed, there is nothing to do currently than wait for the fix to be released. Therefore, I am closing this issue

where can we expect this to be released?
can't we cherry-pick this from master

Please see https://github.com/flutter/flutter/wiki/Flutter-build-release-channels for more information


implement found_index (fix #65)

There are a couple other small typos fixes and fix for mouse move before starting all ToolTipsTestCases

Current coverage is 96.52%

Merging #87 into master will increase coverage by +0.02% as of 655e47a

@@            master     #87   diff @@
======================================
  Files           22      22
  Stmts        16324   16330     +6
  Branches         0       0
  Methods          0       0
======================================
+ Hit          15754   15763     +9
  Partial          0       0
+ Missed         570     567     -3

Review entire Coverage Diff as of 655e47a

Powered by Codecov. Updated on successful CI builds.


How do we give priority to an urgent UP that must be deployed fast?

It would be nice to have different priority and different thresholds, but maybe this can be abused by the adversary.

Priority will be given by Delegation. Different thresholds shouldn't be
needed.
On Wed, Mar 13, 2019, 17:24 mciampi<EMAIL_ADDRESS>wrote:

It would be nice to have different priority and different thresholds, but
maybe this can be abused by the adversary.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/input-output-hk/decentralized-software-updates/issues/5#issuecomment-472470141,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAhPPPo7jzpf2aeus5WBVK_bDVQt0nxgks5vWRgegaJpZM4bhiig
.

See update policies on FC20 submitted paper.


Drive dress error

The Google Drive dress is error, I can not open it, would you give me a new dress, ths

Sorry for the mistake! Could you try again? I just updated the link

thx


THRIFT-2975 Graceful handling of server-side errors in Python

Change process_* functions to handle unexpected exceptions from
user-supplied handlers by throwing a TApplicationException(INTERNAL_ERROR)
to the client.

This needs to log the actual exceptions before throwing TApplicationException to the clients and the clients need control of where the exceptions are logged. The current design doesn't cover that. Abandoning this diff to evaluate whether that's possible.


internal/pkg/scorecard/olm_tests.go: improve CRDsHaveResourcesTest

Description of the change:

Adds new valid URI formats in scorecardProxy log parser
Improves suggestion text to include missing resources

Motivation for the change:

Some valid URI formats are not parsed correctly, resulting in tests that erroneously fail
Give users better feedback about why their CRDsHaveResourcesTest failed.

Something that I would like to do (maybe in another PR), is to give the earned point if the CRD simply has an owned resources section and just provide the suggestion of the other resources that were used at the end. According to OLM, operator developers don't need to include all used resources in the CSV, only the ones that a user may need to know about when debugging. Failing an operator for not including a used resource is not a good idea for the scorecard.

@AlexNPavel that seems like a reasonable way to handle it since there doesn't seem to be a place to list every GVK used by the operator.


sequin: 0.2.0 -> 0.3.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/project/sequin/versions.
meta.description for sequin is: Human-readable ANSI sequences
meta.homepage for sequin is: https://github.com/charmbracelet/sequin
meta.changelog for sequin is: https://github.com/charmbracelet/sequin/releases/tag/v0.3.0
Updates performed

Golang update

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.3.0 with grep in /nix/store/6ichdp2k4g68z28c928llbq290m45gq1-sequin-0.3.0
found 0.3.0 in filename of file in /nix/store/6ichdp2k4g68z28c928llbq290m45gq1-sequin-0.3.0

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

sequin

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/6ichdp2k4g68z28c928llbq290m45gq1-sequin-0.3.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A sequin https://github.com/r-ryantm/nixpkgs/archive/ae2e62808944938830e40666c773af8b62d6e796.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/ae2e62808944938830e40666c773af8b62d6e796#sequin

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/6ichdp2k4g68z28c928llbq290m45gq1-sequin-0.3.0
ls -la /nix/store/6ichdp2k4g68z28c928llbq290m45gq1-sequin-0.3.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review

x86_64-linux

:white_check_mark: 1 package built:

sequin

Maintainer pings
cc @caarlos0 for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

Add a :+1: reaction to pull requests you find important.

@NixOS/nixpkgs-merge-bot merge


Machine mac-24 lost external connection from iPhone device.

Machine mac-24 lost external connection from iPhone device.

The external connection has been restored by rebooting mac-24.


Don't generate symbols for pure virtual functions.

Fixes #1197.

 Warning

These commits modify unsafe code. Please review it carefully!

r? @fitzgen or @pepyakin

@bors-servo r+
Looks good!

:pushpin: Commit f4d2d6a has been approved by pepyakin

:hourglass: Testing commit f4d2d6a478413d04930659929c6307af63d32cf0 with merge 04591f01d96a5c05e690dcf49d19d8e003eac7bf...

:sunny: Test successful - status-travis
Approved by: pepyakin
Pushing 04591f01d96a5c05e690dcf49d19d8e003eac7bf to master...


L-585: Add support for Clio regions other than NA

Introducing support for Clio Regions!
Clio API supports four geographic regions:

Region Code
Geographic Area
API

US
United States + Territories
app.clio.com

CA
Canada
ca.app.clio.com

EU
European Union (EMEA)
eu.app.clio.com

AU
Australia
au.app.clio.com

Region support in hyacinth
hyacinth defaults to the US region:
>>> import hyacinth
>>> session = hyacinth.Session(
        token=<token>,
        client_id=<client_id>,
        client_secret=<client_secret>
)
>>> session.make_url("users")
'https://app.clio.com/api/v4/users.json'

To enable region support, supply region parameter, which must be one of ['US', 'CA', 'EU', 'AU'].
>>> ca_session = hyacinth.Session(
        token=<token>,
        client_id=<client_id>,
        client_secret=<client_secret>,
        region="CA"
)
>>> ca_session.make_url("users")
'https://ca.app.clio.com/api/v4/users.json'

Other Notes

I've added a few simple tests for region support as well, I'd love some thoughts on what other ways I can test this!

Thanks for the review my good sir


Add rpc authentication support

The methods from steem.api fail for me with this error: ReferenceError: regeneratorRuntime is not defined. @jnordberg can you reproduce this error running the file /examples/server.js or /examples/index.html?

Bet is the introduction of async functions, @goldibex I'm going to revert to my initial design

@bonustrack try now

Now it's working for me @jnordberg