No way to tell from CSV export if coordinates are obscured

Several project curators have been asking for tools to to see which observations in their project they have access to the private coordinates of. I've been advocating that they look in the CSV export. But I just realized that the CSV export doesn't give any indication if the values in latitude/longitude are accurate or not. For example, this is an obs of a threatened species so the lat/lon are not accurate, but I have no way of knowing that from the export:

id
observed_on_string
observed_on
time_observed_at
time_zone
out_of_range
user_id
user_login
created_at
updated_at
quality_grade
license   url
image_url
tag_list
description
id_please
num_identification_agreements
num_identification_disagreements
captive_cultivated
oauth_application_id
place_guess
latitude
longitude
positional_accuracy
geoprivacy
positioning_method
positioning_device
species_guess
scientific_name
common_name
iconic_taxon_name
taxon_id

5914
3/7/2010 12:05:00
3/7/2010
2010-03-07 20:05:00 UTC
Pacific Time (US & Canada)
FALSE
1
kueda
2010-03-09 08:27:48 UTC
2014-10-20 03:12:27 UTC
research
CC-BY
http://www.inaturalist.org/observations/5914
http://farm5.staticflickr.com/4063/4419561806_28f457cdb5.jpg
Didn't smell too fragrant to me, but boy, what a looker.
FALSE
1
0
FALSE

Edgewood County Park, San Mateo County, CA, USA
37.44495777
-122.2749524

fragrant fritillary
Fritillaria liliacea
fragrant fritillary
Plantae
53054

The geoprivacy column currently stores 'obscured' or 'private' if the obs owner chose to add geoprivacy - perhaps adding an additional value like 'threatened' if the obs is obscured automatically? If not, maybe another column that says whether the lat/lon represent precise or obscured values?

It would be easy enough to add coordinates_obscured to Observation::GEO_COLUMNS and have it appear in the export field list. Would that be enough? It would take a little more processing in the export to also add what the taxon's exact establishment_means is for all observations

You could also add private_latitude and private_longitude to the export, and make sure the viewer only sees private coordinates they have access to.

I see private_latitude and private_longitude are now part of the export, but that still assumes the user knows which species are having their coordinates automatically obscured. For example, take this record:

id
species_guess
scientific_name
common_name
iconic_taxon_name
taxon_id
latitude
longitude
positional_accuracy
private_latitude
private_longitude
private_positional_accuracy
geoprivacy
positioning_method
positioning_device
curator_coordinate_access

1485885
Three-toed Box Turtle
Terrapene carolina triunguis
Three-toed Box Turtle
Reptilia
39818
30.09172708
-95.73833618
6109

FALSE

private_latitude and private_longitude are blank and curator_coordinate_access is FALSE. But the user would have to know a priori that Three-toed Box Turtle is automatically obscured to know that latitude and longitude do not hold the precise values.
Would an alternative solution of modifying the geoprivacy column to say 'obscured by owner' or 'obscured by taxon' to encompass all obscured observations while still distinguishing between these flavors?

I'd preferred @pleary's coordinates_obscured suggestion. That way there's just one column that tells you whether the coordinates were obscured, regardless of cause.

fine with me

ok I'll add that and take a look at #713

Thought about this a bit more. I think we should include coordinates_obscured, but there's still the problem of not knowing what the true coordinate uncertainty is, which varies by positional_accuracy and by latitude. We could address this by including public_positional_accuracy, which is MAX(uncertainty_cell_diagonal_meters, positional_accuracy), and which we use to determine what place names to use when describing coordinates (i.e. don't be too precise if the coordinates aren't precise), but that's not really the same thing as coordinate uncertainty, b/c if the positional_accuracy is blank, we don't actually know what the coordinate uncertainty is, we just know how much we obscured the coordinates. If the true uncertainty is the size of California for an observation of a CA Condor but the positional_accuracy is blank, public_positional_accuracy will be incorrectly low, i.e. the size of the uncertainty cell, which is much smaller than the true uncertainty.
Proposal:

[ ] include coordinates_obscured in obs CSV exports
[ ] rename public_positonal_accuracy to display_coordinate_uncertainty and continue using it as we have been
[ ] add public_coordinate_uncertainty and set it to positional_accuracy ? MAX(positional_accuracy, uncertainty_cell_diagonal_meters) : null
[ ] set public_coordinate_uncertainty for all past observations
[ ] include public_coordinate_uncertainty in obs CSV exports
[ ] use public_coordinate_uncertainty for coordinateUncertaintyInMeters in DwC-A exports

do we have public_positonal_accuracy now? I thought we only had positonal_accuracy? What is  public_positonal_accuracy currently storing?

To quote myself from above, public_positional_accuracy

is MAX(uncertainty_cell_diagonal_meters, positional_accuracy), and which we use to determine what place names to use when describing coordinates (i.e. don't be too precise if the coordinates aren't precise)

I thought 'rename public_positonal_accuracy to display_coordinate_uncertainty and continue using it as we have been' implied that this field currently exists. 'add public_coordinate_uncertainty and set it to positional_accuracy ? MAX(positional_accuracy, uncertainty_cell_diagonal_meters) : null' implies it doesn't

public_positional_accuracy exists and its value is MAX(uncertainty_cell_diagonal_meters, positional_accuracy)
I am proposing renaming that field so its name better describes what we use it for, and adding a new field called public_coordinate_uncertainty whose value would be positional_accuracy ? MAX(positional_accuracy, uncertainty_cell_diagonal_meters) : null

thats what I was after - thanks

proposal seems fine to me

Can we revisit this? I haven't found anything in the private_positional_accuracy field yet even though it exists. If I understand the above conversation correctly, I'd like to add the following proposal to this:

[ ] copy positional_accuracy to private_positional_accuracy

I believe with the changes above, if a location is not obscured, positional_accuracy renamed as public_coordinate_uncertainty will remain the same as private_positional_accuracy, but if it is obscured, then public_coordinate_uncertainty will be different than private_positional_accuracy.
Do we know how this should work for private observations that are not mappable at all? Seems we should just have the private_positional_accuracy with no value for public_coordinate_uncertainty.

I don't think private_positional_accuracy actually does anything or is ever used, so I propose we remove it.

positional_accuracy renamed as public_coordinate_uncertainty will remain the same as private_positional_accuracy

I don't think anyone is proposing that we rename positional_accuracy so I'm not sure what this means.
For private coordinates, coordinated_obscured will be true, latitude and longitude will be blank, and private_latitude and private_longitude will be set if you have access to them.

To date, I think private_positional_accuracy has been unused, but I think we should use it, rather than delete it.
Re-reading above, I see that positional_accuracy will remain. I tried and failed to make a table in here, so hand drew a table that hopefully better explains my ideas about how the fields will work under different geoprivacy conditions.

Just reread all this and Ken-ichi's proposal makes sense to me and still seems like a good option to fix the remaining issue that an obs with positional_accuracy = nil should also have a nil public_coordinate_uncertainty.
Carrie - do you have any specific issues with this approach and if so can you help explain what they are and how what you describe above resolves them?

I agree with everything Ken-ichi proposed, with the exception of removing private_positional_accuracy.
I propose that private_positional_accuracy contain a value derived from the positional_accuracy field when exporting private coordinates.

@carrieseltzer, just a reminder, this is sitting in a branch. I can get it on staging or something if/when you're ready to test.

Pretty sure this was dealt with in #2891. Going to close and remove the branch.


Replay speed modification

Modified the _load function so the next frame to show is either hold up for longer if the video speed is slowed down, or skipped if the video speed is accelerated.
Tested in sample_player2.py

Hey thanks for creating the pull-request, I am a bit busy right now, and it might take a couple of months for me to be free again to continue reviewing the pull requests in this repo.
I'll let you know once the review is complete. Thanks again for your time


Multiple vue versions imported

Hi, i'm trying to use this plugin for a vue 2 app via vite, but it appears to be pulling in two versions of vue:

it also throws the following errors in the console when the input is updated, which i assume is related

This issue can be reproduced in this example by running yarn dev
https://github.com/samturrell/vite-issue
Hopefully somebody can help? I'm at a bit of a loss here.
I'm having to pull in import Vue from 'vue/dist/vue.js'; rather than just vue otherwise it errors with
vue.runtime.esm.js:4568 [Vue warn]: You are using the runtime-only build of Vue where the template compiler is not available. Either pre-compile the templates into render functions, or use the compiler-included build.

I feel like this might also be related, but i'm not sure what else i need to do.

I just started the project and find the error.
If you want to change the default import-source of vue, use resolve.alias instead.
export default defineConfig({
  plugins: [
    vue(),
  ],
  resolve: {
    alias: {
      vue: 'vue/dist/vue.js'
    }
  }
})

Directly import from vue/dist/vue.js will split the relations among the dependencies, which result in multi instance exception.


Re-enable merge ds internal sorting

+1 once you've considered my final (minor) comments and made sure that the test failure isn't related.

Fixed size_t -> uint64_t
Fixed timing issue with the test


Fix CI build tests

This fixes errors that occurred due to a missing newline at EOF in a newly added .puml file.

Codecov Report

Merging #93 (d40ff18) into master (7036934) will increase coverage by 0.06%.
The diff coverage is 0.00%.

:exclamation: Current head d40ff18 differs from pull request most recent head 4bf2d43. Consider uploading reports for the commit 4bf2d43 to get more accurate results

@@             Coverage Diff              @@
##             master      #93      +/-   ##
============================================
+ Coverage     58.75%   58.81%   +0.06%
  Complexity      547      547
============================================
  Files            93       93
  Lines          1954     1952       -2
  Branches        230      230
============================================
  Hits           1148     1148
+ Misses          736      734       -2
  Partials         70       70

Impacted Files
Coverage Δ

.../seedu/address/logic/parser/EditCommandParser.java
66.00% <0.00%> (+2.53%)
:arrow_up:

Continue to review full report at Codecov.

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


Add FIPS indicator for TEST-RAND RNG

This RNG is not and never will be approved and is guarded by a fips="no" property but it still should have an indicator saying not FIPS.

[ ] documentation is added or updated
[x] tests are added or updated

Needs update to EVP_RAND-TEST_RAND.pod
This should also trigger the callback somewhere so you may want to add a call also call ossl_FIPS_IND_callback inside a #ifdef FIPS_MODULE

This should also trigger the callback somewhere so you may want to add a call to ossl_FIPS_IND_callback inside a #ifdef FIPS_MODULE

Why?  This is never FIPS approved and doesn't fail if it is used.  I don't see a need for the callback.

Ping @openssl/committers for review.

@t8m can you reconfirm?

looks like there is a doc-nits issue

reconfirmed after trivial cvhange

Merged, thanks for the input.


I am confused about the dataset

In the cora.content file, I don't know what is the features mean.

The .content file is the features of every node(paper). The first column is paper_id, and the last column means its ground-truth label.
The columns in the middle represent the feature of this paper.  Every dim of the feature here is 0 or 1. Maybe, dim1 means 'containing the word: neural network', dim2 means ..., dim3 means..

Maybe you can refer to the paper which proposed dataset 'cora', for more details.


JSDoc: function with param or null

Example:
/**
 * @param {?((n: number) => void)} add - shows [ add: (n: number) => void ]
 * @param {?(() => void)} delete - shows [ delete: (() => void) | null) ]
 */
function example(add, delete) {
    add && add(1)
    delete && delete()
}

The first line should be add: ((n: number) => void) | null

VS Code's JS intellisense is powered by the TypeScript project. Please file a feature request upstream for recognizing JSDoc's nullable types.
You can use TS Types instead:
 * @param {null | ((n: number) => void)} add - shows [ add: (n: number) => void ]


Memory Summary is not printed on OOM

It would appear that the memory summary isn't printed on OoM.  I notice the exit 137 which is the container killing the current process.  It's only a second after the OoM so I don't think it's a timing issue.  I wonder if jvmkill is actually busting the container memory limit when it reaches out for MBeans.
Because all of this happens so close to the end of the JVM, I think we should probably ensure flushes of the std* streams before the jvmkill takes down the process for sure.  Once we've got that, it'd be good to see if we can diagnose whether making those calls is occupying enough memory that we provoke the container.  If that's the case, maybe we update the memory calculator to leave 1% (or 0.5%, etc) for jvmkill to do its thing.

Another example shows the following logs produced by jvmkill:
2017-03-20T09:10:32.91+0000 [APP/PROC/WEB/0]OUT | 300            | 7200        | Ljava/util/concurrent/CopyOnWriteArrayList;                                                                      |
2017-03-20T09:10:32.99+0000 [APP/PROC/WEB/0]ERR Killing current process
2017-03-20T09:10:33.03+0000 [APP/PROC/WEB/0]OUT | 22Exit status 137

"Killing current process" is logged to standard error by jvmkill just before killing the JVM with SIGKILL (9). This is consistent with the process exiting with status code 137 (=128+9). So the OOM killer is not necessarily involved here.

It turned out that the memory summary was not being flushed properly. Adding flushing and some sleeps to avoid over-exerting loggregator produced the correct output.


FNET DNS doesn't resolve for certain urls

Since there seems actually no activity on the reository of butok to solve this issue, I post this issue here as well.
see:
https://github.com/butok/FNET/issues/7

Hi @vjmuzik,
perhaps you are interested to join the discussion on butok/FNET
https://github.com/butok/FNET/issues/7

#6


Updated File Progress Receiver Tests

Updated the BlobAPITest and EncryptedBlockBlobAPITest Download file progress receiver tests to handle the case when there are empty buffers in the reactive stream after the full download size has reached completion. The test now validates that there is at least one report with the expected file size and there are zero reports which are greater than the expected size.

/azp run java - storage - tests

/azp run java - storage - tests

/azp run java - storage - tests

/azp run java - storage - tests


New package: GDIP v0.1.0

Registering package: GDIP
Repository: https://github.com/comrob/GDIP.jl
Created by: @petvana
Version: v0.1.0
Commit: a3127aa6f99652ec030a7b1872586ece22f271e6
Git reference: HEAD

Renamed to GeneralizedDubinsIntervalProblem (#44904). This PR can be closed.


R_p(h) in the paper might be inconsistent with the implementation in the code

@wl-zhao In the paper, Theorem 3.1 shows ${R_p}{\left( h \right)_{p,p}} = {\left( {{r_p}h} \right)^{p - 1}}$. But
https://github.com/wl-zhao/UniPC/blob/a54e61e6a5b860c62678f45a8d1d9af0ea0eef69/example/stable-diffusion/ldm/models/diffusion/uni_pc/uni_pc.py#L626
shows ${R_p}{\left( h \right)_{p,p}} = {\left( {{r_p}} \right)^{p - 1}}$.

Hi, thanks for your interest in our work!
Actually, the two versions are equivalent. The definition in the paper makes it easier to give the condition in Equation (5) (and make the theoretical proof clearer), while the implementation in the code is more efficient.
Feel free to ask if you still have any questions.
Best,
Wenliang

Hi, thanks for your interest in our work!
Actually, the two versions are equivalent. The definition in the paper makes it easier to give the condition in Equation (5) (and make the theoretical proof clearer), while the implementation in the code is more efficient.
Feel free to ask if you still have any questions.
Best, Wenliang

Thank you for your quick reply.
Changing
R.append(torch.pow(rks, i - 1))

to
R.append(torch.pow(rks*h, i-1))

will not significantly increase the computational cost.
Therefore, Is ${R_p}{\left( h \right)_{p,p}} = {\left( {{r_p}} \right)^{p - 1}}$ considered for numerical stability?

Sorry for the confusion. It's not about the computational cost. Actually, our algorithm is initially designed as implemented in the code. We just use an equivalent form in the paper for the sake of a clearer presentation. We didn't test the numerical stability of the two methods. But I think using $R_{p, p}=r_p^{p-1}$ is indeed more stable, especially when there are more timesteps such that $h$ is too small.

Sorry for the confusion. It's not about the computational cost. Actually, our algorithm is initially designed as implemented in the code. We just use an equivalent form in the paper for the sake of a clearer presentation. We didn't test the numerical stability of the two methods. But I think using Rp,p=rpp−1 is indeed more stable, especially when there are more timesteps such that h is too small.

Thank you very much for your answer！


[BUG] 一键部署报错

Run API or Web? [api/web/all/quit] all
Do you want to start the app and api service when system boot? [y/n] y
Created symlink from /etc/systemd/system/multi-user.target.wants/web_app.service to /etc/systemd/system/web_app.service.
Created symlink from /etc/systemd/system/multi-user.target.wants/web_api.service to /etc/systemd/system/web_api.service.
Starting WEB and API Services...
Failed to start web_app.service: Unit is not loaded properly: Invalid argument.
See system logs and 'systemctl status web_app.service' for details.
Failed to start web_api.service: Unit is not loaded properly: Invalid argument.
See system logs and 'systemctl status web_api.service' for details.
API and APP service are running!
You can stop the api service by running following command:
systemctl stop (web_app.service||web_api.service)
[root@glory ~]# systemctl status web_api.service
● web_api.service - www/wwwroot/Douyin_TikTok_Download_API/web_api.py deamon
Loaded: error (Reason: Invalid argument)
Active: inactive (dead)
Aug 11 09:32:44 glory systemd[1]: [/etc/systemd/system/web_api.service:10] Executable path is not absolute, ignoring: python3 web_api.py
Aug 11 09:32:44 glory systemd[1]: web_api.service lacks both ExecStart= and ExecStop= setting. Refusing.
Aug 11 09:32:44 glory systemd[1]: [/etc/systemd/system/web_api.service:10] Executable path is not absolute, ignoring: python3 web_api.py
Aug 11 09:32:44 glory systemd[1]: web_api.service lacks both ExecStart= and ExecStop= setting. Refusing.

请使用Ubuntu进行部署。


Added check for explicit_application_access_allowed in async base paig authorizer

Change Description
Following are the changes present in the PR:

For GenAI Applications, the user and groups level access controls are enforced
Set the paig policy id if the access was granted by the application (or application config).
Add reason for debugging purpose for both check_explicit_application_access and explicit_application_access_allowed (internal)
Removed if condition from the printing the debug logs for debugging

Issue reference
This PR fixes issue #108
Checklist

[x] I have reviewed the contribution guidelines
[x] My code includes unit tests
[x] All unit tests and lint checks pass locally
[x] My PR contains documentation updates / additions if required

@sushilsani1 We have to do same changes in base_paig_authorizer.py as well and write the test cases as well. The changes you did was for the user who are using async mechanism to call authorizer, we have to do same changes for the synchronous one too.

@sushilsani1 We have to do same changes in base_paig_authorizer.py as well and write the test cases as well. The changes you did was for the user who are using async mechanism to call authorizer, we have to do same changes for the synchronous one too.

@akshayr-privacera-github review comment addressed please check the latest changes


Exception System.IndexOutOfRangeException

Type: System.IndexOutOfRangeException
Message: Index was outside the bounds of the array.
Source: ScintillaNET
Stack:    at ScintillaNET.GapBuffer`1.get_Item(Int32 index)
at ScintillaNET.LineCollection.CharLineLength(Int32 index)
at ScintillaNET.LineCollection.DeletePerLine(Int32 index)
at ScintillaNET.LineCollection.TrackDeleteText(SCNotification scn)
at ScintillaNET.LineCollection.scintilla_SCNotification(Object sender, SCNotificationEventArgs e)
at ScintillaNET.Scintilla.WmReflectNotify(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
Is there anyway we can handle this exception?

You shouldn't be receiving this exception. It is likely you are doing something with Scintilla outside the standard API. Maybe you can explain more what is causing it.


Is it possible to use movable-only state machine with SML?

Hi!
Consider the following example:
#include <boost/sml.hpp>

#include <cassert>
#include <iostream>
#include <variant>
#include <mutex>

namespace sml = boost::sml;

namespace {
struct connect {};
struct disconnect {};

class data {
    struct Disconnected {};
    struct Connected {
        int id{};
    };

public:
    explicit data(const std::string& address) : address{address} {}

    inline auto operator()() {
        using namespace boost::sml;
        return make_transition_table(
                * state<Disconnected> + event<connect> / [this] {
                    data_ = Connected{42};
                } = state<Connected>
                , state<Connected> + event<disconnect> / [this] {
                    std::cout << std::get<Connected>(data_).id << std::endl;
                } = X
        );
    }

private:
    std::mutex mutex;
    std::string address{};
    std::variant<Disconnected, Connected> data_{};
};
}  // namespace

int main() {
    sml::sm<data> sm{data{"<IP_ADDRESS>"}};
    sm.process_event(connect{});
    sm.process_event(disconnect{});
    assert(sm.is(sml::X));
}

If you try to compile: you will get something like this: https://pastebin.com/rYbdrbL8
I cannot be compiled since std::mutex is movable only type.
My question is: is it possible avoid such limitation with SML library? If yes, how can I do it?

std::mutex is neither copyable not movable.

Sorry, my bad. Of course you are right.
What about the following sample?
#include <boost/sml.hpp>

#include <cassert>
#include <iostream>
#include <variant>
#include <mutex>

namespace sml = boost::sml;

namespace {
struct connect {};
struct disconnect {};

struct type
{
    type() = default;
    type(const type&) = delete;
    type(type&&) = default;

    int a;
};

class data {
    struct Disconnected {};
    struct Connected {
        int id{};
    };

public:
    explicit data(const std::string& address) : address{address} {}

    inline auto operator()() {
        using namespace boost::sml;
        return make_transition_table(
                * state<Disconnected> + event<connect> / [this] {
                    data_ = Connected{42};
                } = state<Connected>
                , state<Connected> + event<disconnect> / [this] {
                    std::cout << std::get<Connected>(data_).id << std::endl;
                } = X
        );
    }

private:
    type t;
    std::string address{};
    std::variant<Disconnected, Connected> data_{};
};
}  // namespace

int main() {
    sml::sm<data> sm{data{"<IP_ADDRESS>"}};
    sm.process_event(connect{});
    sm.process_event(disconnect{});
    assert(sm.is(sml::X));
}

Should probably work fine with perfect forwarding used in aux::pool and aux::pool_type, but I'm not familiar enough with SML guts to be 100% sure. You may try to add it here:
explicit pool_type(T object) : value{object} {}

And here:
explicit pool(Ts... ts) : pool_type<Ts>(ts)... {}

Maybe it would also require making aux::pool movable itself.


CON-4868 Fixed setConnectMappedCategory during import

Coverage increased (+0.006%) to 35.147% when pulling 37be9e25cbf18f4f65829197ebab2da8c75db0a8 on CON-4868 into 23faee24f443affff4e3f6cfd578d0d522965d50 on master.

Coverage increased (+0.01%) to 35.943% when pulling 8a7e7965e97911125210c6394b020f6ef9c43a84 on CON-4868 into 7c3972acf69a76ccdd5c4b304a84e01215b2822b on master.


Providing an improperly formatted dotenv file silently passes

Describe the bug
If using the --dotenv option from the command-line or dotenv: in a Config File and providing a file that is not a dotenv file doesn't cause an error. It would be better to let the user know that they provided an improperly formatted instead of continuing with executing commands and potentially failing later.
To Reproduce
Steps to reproduce the behavior:

Run build-magic --dotenv [some file] echo hello where [some file] is any file that isn't a dotenv file.

Expected behavior
An improperly formatted dotenv file should raise an error and communicate the impropriety to the user.
Additional context
The dotenv file is read and parsed in cli/parse_dotenv_file()  and the logic simply continues to the next line if it doesn't contain an "=":
envs = {}
    for line in dotenv.readlines():
        if line.startswith('#'):
            continue
        if '=' not in line:
            continue
        env, val = line.split('=', maxsplit=1)
        envs.update({env.strip(): val.strip()})

The checks inside this loop should be replaced with a single step that validates the dotenv file.

Can i try these.

Feel free to submit a pull request. I've assigned the issue to you and sent you an invitation to the project.

Feel free to submit a pull request. I've assigned the issue to you and sent you an invitation to the proS
So by "improperly formatted dotenv file" you are talking about the contents of the .env file right?

Feel free to submit a pull request. I've assigned the issue to you and sent you an invitation to the proS
So by "improperly formatted dotenv file" you are talking about the contents of the .env file right?

Correct, the content of the dotenv file does not contain equal sign separated key value pairs on each line. You can test against a plane text file or binary file like a jpg.

Correct, the content of the dotenv file does not contain equal sign separated key value pairs on each line. You can test against a plane text file or binary file like a jpg.


RKObjectLoader, RKRequest, RKResponse aren't released

Looks like neither RKRequest or RKResponse are getting deallocated and there appears to be a retain/release cycle happening if you forcibly release it.   RKResponse retains RKRequest and RKRequest retains RKResponse.
RKResponse init retains request:  _request = [request retain]; dealloc has [_request release] which can never happen because of the
cross reference. That reference to _request is only needed until all of the delegate calls are finished.
I patched it with this and all is well again:
- (void)dealloc {
//  [_request release]; <-- it has already been released
  _request = nil;
  [_httpURLResponse release];
}

- (void)connectionDidFinishLoading:(NSURLConnection *)connection {
  RKLogTrace(@"Read response body: %@", [self bodyAsString]);
  [_request didFinishLoad:self];
  [_request release]; // <-- moved it here
}

- (void)connection:(NSURLConnection *)connection didFailWithError: (NSError *)error {
  _failureError = [error retain];
  [_request didFailLoadWithError:_failureError];
  [_request release]; // <-- moved it here
}

Fixed this by reverting the change that introduced it.


Cli

Working front end.
Scheduler sends the location of the final result to the front end, which the front end then runs an independent scan to display it.

Codecov Report
Attention: Patch coverage is 9.48617% with 229 lines in your changes are missing coverage. Please review.

Project coverage is 56.54%. Comparing base (4cae38a) to head (206ca95).
Report is 1 commits behind head on main.

Files
Patch %
Lines

scheduler/src/cli.rs
0.00%
127 Missing :warning:

scheduler/src/proto_server.rs
0.00%
55 Missing :warning:

scheduler/src/executor.rs
0.00%
34 Missing :warning:

scheduler/src/scheduler.rs
0.00%
11 Missing :warning:

scheduler/src/integration.rs
77.77%
1 Missing and 1 partial :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #18      +/-   ##
==========================================
- Coverage   62.23%   56.54%   -5.70%
==========================================
  Files           7        8       +1
  Lines        1851     2048     +197
  Branches     1851     2048     +197
==========================================
+ Hits         1152     1158       +6
- Misses        592      781     +189
- Partials      107      109       +2

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


Creator Kit - DetailsList BUG: sort is no longer working

in the latest release (1.1.34) we can no longer sort items in the DetailsList
To Reproduce
Steps to reproduce the behavior:

Install the latest release of the PowerCat Code Components (May 24)
Open the Creator Kit Reference App (Canvas)
Play the app in Power Apps Studio
Navigate to DetailsList and try to sort
Sort does not work

After re-publishing the app and refreshing the browser cache sort is also no longer working in the published version of the app
Expected behavior
By following the documentation for manual sorting, the DetailsList should support sorting on any sort-enabled column.
Screenshots
Sorting has no effect:

Additional context
I did already verify the collection used in the DetailsList items. It is sorted correctly and differently to what is displayed.
Workaround needed
I have already tried to revert back to a previous version without success. Kit is installed from AppSource. How can I remove it and use a previous version?
I am happy to try any workarounds until this is fixed in a later release. What options do I have to make this work now?
AB#3905

Hi, we are aware of this issue impacting the sorting order of datasets in controls such as the Details List and are working to deploy a fix soon. In the meantime, please revert back to Canvas studio version v3.24072 (by appending "&studio-version=v3.24072.6.302069373" to the studio URL) to fix this issue.
You can refer to this known issue for live updates as the fix deploys. https://admin.powerplatform.microsoft.com/knownissues/4238060

The fix has been deployed, please verify and close the bug when you can.

This was all working for me but now I'm seeing it's broken again. I published an app yesterday and the details list no longer sorts. This is on version 3.24081.10. Switching back to 3.24075.18 fixes it for me.

I'm seeing similar behavior but on the Navigation Breadcrumbs component.  The ItemKey is no longer sorting the items in the navigation using Studio version 3.24081.10.  Reverting to <IP_ADDRESS> appears to properly sort the items.

I am also seeing sort issues with the details list as of today. It will only sort by the first column in the collection used for its items. I am on the same Studio version as above: 3.24081.10

I'm still seeing sorting issues also on version 3.24081.10.

I just had a user report this to me too, hadnt noticed it broke.
3.24081.10 is the current suggested version but if I bump to 3.24083.10 it works again.

I can confirm that the Sorting issue (as well as the Adding of new Fields issue) is fixed in PowerApps Studio version 3.24083.14.
I'll let you know if it creeps back into future builds -
(I'm hoping this Creator Kit Team have better links to the Studio Dev Team if reporting these bugs - poor little Devs like myself only have the Power Platform Support Ticket mechanism to use, which is pretty much useless in these genuine BUG scenarios)


About prometheus deploy large-scale deployment problems

I can not understand prometheus pull this way, I have nearly 2,000 servers, some single server running the application 2-3, if I use open source prometheus CLIENT EXPORTERS need to start 2-3 on a single server a client exportes. There is no other way? What if I also need to monitor CPU memory disk on the server, and also requires DJANGO on the Monitoring Server and MYSQL I'll need to download the client exports three applications, so deploying it is not too much trouble?

A single beefy Prometheus server can likely handle that load though splitting into several Prometheus servers would be better (presuming that's 2k servers in one datacenter). Seehttp://www.robustperception.io/scaling-and-federating-prometheus/  Assuming you have good infrastructure, none of this should present a major challenge.

@brian-brazil Thank you, I mean, the server needs to be monitored simultaneously monitor mysql redis and also need to monitor CPU, memory, disk, if I use an existing (https://prometheus.io/docs/instrumenting/exporters/) EXPORTERS means I need to start being a lot of listening ports on this server, unless I have to write an integrated mysql and redis, disk, cpu, memory exportes. But if one day my server is monitored deleted MYSQL, do I also need to edit your client exportes code? Is there a better way? please help me

This is what service discovery is for (https://prometheus.io/blog/2015/06/01/advanced-service-discovery/), when a given host no longer has a given service then Prometheus would no longer monitor it. Your configuration management can add/remove exporters as part of adding/removing the associated service.

@brian-brazil Thank you very much, there is a problem, why prometheus the alert rule are not stored inside the DB, similar ZABBIX can set the alarm go rules WEB UI. What put this document is designed to do?

Our paradigm is that all configuration is provided via files. If there was some form of WebUI we'd need to be able to sync with replicas, integrate with configuration management, offer an API etc. - not trivial problems. Instead we leave it up to the user how they manage the configuration.

@brian-brazil  thank you! Problems Close


cluster shutdown w/ ES 2.x doesn't work anymore

With Elasticsearch 2.x release they don't provide a _shutdown endpoint anymore, but force users to kill the Elasticsearch cluster using SIGTERM. See https://www.elastic.co/guide/en/elasticsearch/reference/current/cluster-nodes-shutdown.html for details.
I started working on a fix (writing a .pid file on start and using it to issue a kill in the stop action), but didn't manage to kill the process yet.

ok, proof of concept is available at https://github.com/gesellix/bilberry/tree/process-mgmt-elasticsearch2
I'll clean up the code a bit and then create a PR


support v1beta2 API for mco

ref: https://github.com/open-cluster-management/backlog/issues/10749
based on https://github.com/open-cluster-management/multicluster-observability-operator/pull/404

/hold

closing this in favor of https://github.com/open-cluster-management/multicluster-observability-operator/pull/416


Link to here from BananaBread?

Really awesome stuff here!
What do you think about linking to here from the BananaBread repo? Now and then people ask there about whether there is any news in this space.

Sure! I will clean up the README for this repo and then make a pull request in BananaBread when I get the chance. My plan is to attempt to update the engine to the latest Sauerbraten revision, which may make this a bit more appealing :tada:

Sounds great!


Export all types/interfaces

Is your feature request related to a problem? Please describe.
Hello! This package has been a massive time saver!
However, I've had a lot of use cases where I need to use the types inside the package. (Ex.: Creating wrapper functions, allowing for arbitrary parameters to be passed)
I believe that if the package doesn't export it's types/interfaces, developers are going to find themselves re-creating a lot of the same types, probably incorrectly.
Describe the solution you'd like
All types/interfaces to be exported thorough the package and accessible in projects.
Example of some interfaces that are not exported: UseQuerySingleReturn, UseQueryMaybeSingleReturn, UseQueryReturn, UseQueryAnyReturn, UseSubscriptionQueryOpts, UseSubscriptionOpts.
Describe alternatives you've considered
Coping the type code inside the project, re-creating only parts of the types.

thanks for opening the issue @heloineto! sure, that would make sense. are you willing to create the pr yourself?

No problem, I'll create a PR asap


OFP TCP TIME_WAIT buffer count increment

Hi Team,
In OFP timewait.c file,  below function is used to set number of TIME_WAIT buffers:
---------------------------------  code  --------------------------------------------
static int
tcptw_auto_size(void)
{
#ifdef OFP_TCP_MAX_CONNECTION_RATE
return global_param->pcb_tcp_max;
#else
int halfrange;
/*
 * Max out at half the ephemeral port range so that TIME_WAIT
 * sockets don't tie up too many ephemeral ports.
 */
if (V_ipport_lastauto > V_ipport_firstauto)
	halfrange = (V_ipport_lastauto - V_ipport_firstauto) / 2;
else
	halfrange = (V_ipport_firstauto - V_ipport_lastauto) / 2;
/* Protect against goofy port ranges smaller than 32. */
return (imin(imax(halfrange, 32), global_param->pcb_tcp_max / 5));

#endif /* OFP_TCP_MAX_CONNECTION_RATE*/
}
In the above code we are assigning 20% of TCP max buffers for TIME_WAIT using formula as below
global_param->pcb_tcp_max / 5
Queries :

As we can see above TIME_WAIT buffers are dependent on TCP max buffers (global_param->pcb_tcp_max). Can we increase TIME_WAIT buffer alone using /4 (divide by 4), /3 (divide by 3) OR TCP max buffers need to be increase in order to increase TIME_WAIT buffers?

If  we increase TCP TIME_WAIT buffers using /4(divide by 4) or /3(divide by 3) then is there any impact of this?

Hi @manishmatey,
The value for 'pcb_tcp_max' can be configured through OFP configuration file (See OFP_CONF_FILE_ENV).
I see no reason not to propose a similar method for tcptw.. e.g:  to permit configuration of tcptw size as value or percentage of global_param->pcb_tcp_max.
You can propose a change (pull request) with this... it will take (near) forever to be reviewed but you may have it.
At least a memory impact is expected as the computed value is used on allocation of V_tcptw_zone (that is an ODP pool).
If memory is not an issue for your setup, you can enable (define) OFP_TCP_MAX_CONNECTION_RATE in ofp_config.h for the default configuration (tcptw size = pcb_tcp_max)

@bogdanPricope Thanks for the reply. I will increase TIME_WAIT buffer and proceed.

@manishmatey You may also check the NFP repo: https://github.com/NetInoSoftware/nfp
NFP is a commercial version of OFP with the 'nfp' repo as 'public'/'demo' part.
API is similar and has a lot of cool features (e.g DHCP IPv4 client).


Adapter fails almost every day.

Host: NUC i3 running HA with Z2M/Z2MA and Node-red add-ons via VMware.
Coordinator: CC26X2R1_20200805
Routers: CC2530_CC2591_router_2019_02 x 2
Devices: All Xiaomi and Aqara devices, including covers, wall switches, power switches, motion sensors, door & window sensors, and water leak sensors. Around 100 devices in one Zigbee network.
It works well the first several hours after being configured.
However, some of those devices become unresponsive randomly after that.
Almost every day, when I get up in the morning, the network is dead and all devices are unresponsive.
This is what I do to fix this temporarily.

Unplug the coordinator from NUC.
Re-plug it
Restart the Z2M add-on in HA
Most of the devices will back alive one by one in about half an hour.
For the rest devices, I need to permit join in Z2MA, and then re-pair them by pressing and holding the pairing keys.

I have also tried those solutions mentioned on the Z2M website, forum, and issues on Github, none of them works.
A. I do press the reset key next to the USB port after plugging the coordinator to NUC, it doesn't change anything.
B. I erased the coordinator board and flash it with the latest master and develop firmware, none of them works, the develop version is more unstable.
C. I have removed those IKEA devices from the network ( they used to be part of it ), with only Xiaomi and Aqara devices left there, no progress.
D. I tried to remove those routers from the network and re-add them in, it doesn't help.
Here is the log after the coordinator is dead:
2020-08-09T13:54:30: PM2 log: App [npm:0] exited with code [1] via signal [SIGINT]
2020-08-09T13:54:30: PM2 log: App [npm:0] starting in -fork mode-
2020-08-09T13:54:30: PM2 log: App [npm:0] online

<EMAIL_ADDRESS>start /zigbee2mqtt-1.14.2
node index.js
zigbee2mqtt:info  2020-08-09 13:54:30: Logging to console and directory: '/share/zigbee2mqtt/log/2020-08-09.13-54-30' filename: log.txt
zigbee2mqtt:info  2020-08-09 13:54:31: Starting zigbee2mqtt version 1.14.2 (commit #unknown)
zigbee2mqtt:info  2020-08-09 13:54:31: Starting zigbee-herdsman...
zigbee2mqtt:error 2020-08-09 13:54:50: Error while starting zigbee-herdsman
zigbee2mqtt:error 2020-08-09 13:54:50: Failed to start zigbee
zigbee2mqtt:error 2020-08-09 13:54:50: Exiting...
zigbee2mqtt:error 2020-08-09 13:54:50: Error: Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)
at ZStackAdapter. (/zigbee2mqtt-1.14.2/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/zStackAdapter.js:87:31)
at Generator.throw ()
at rejected (/zigbee2mqtt-1.14.2/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/zStackAdapter.js:25:65)
npm
ERR! code ELIFECYCLE
npm ERR! errno
1
npm ERR<EMAIL_ADDRESS>start: node index.js
npm ERR!
Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>start script.
npm
ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2020-08-09T05_54_50_708Z-debug.log

Do you have a log at the moment it crashes?

I just checked the log folder, it looks like this:
info  2020-08-09 17:41:05: Logging to console and directory: '/share/zigbee2mqtt/log/2020-08-09.17-41-05' filename: log.txt
info  2020-08-09 17:41:06: Starting zigbee2mqtt version 1.14.2 (commit #unknown)
info  2020-08-09 17:41:06: Starting zigbee-herdsman...
error 2020-08-09 17:41:25: Error while starting zigbee-herdsman
I have set the log level to warning and above, I will upload a copy next time it crashes.

It fails again last night.
However, there are 10 folders in the log folder, all of them only have the same record like I posted above.
Is there any way to remove the quantity limit of the log records?

Changing in the systemctl config (https://www.zigbee2mqtt.io/getting_started/running_zigbee2mqtt.html#5-optional-running-as-a-daemon-with-systemctl) Restart=always to Restart=no should prevent the restarts (and you will only end up with 1 log dir)

Changing in the systemctl config (https://www.zigbee2mqtt.io/getting_started/running_zigbee2mqtt.html#5-optional-running-as-a-daemon-with-systemctl) Restart=always to Restart=no should prevent the restarts (and you will only end up with 1 log dir)

Thanks.
It fails again today and I got these:

Before the adapter was down, all devices were unresponsive. The log shows something like this:
info  2020-08-14 05:36:00: MQTT publish: topic 'zigbee2mqtt/bridge/config/devices', payload '[{"ieeeAddr":"0x00124b001caa6ab0","type":"Coordinator","networkAddress":0,"friendly_name":"Coordinator","softwareBuildID":"zStack3x0","dateCode":"20200805","lastSeen":1597354560090},{"ieeeAddr":"0x00158d00047b9965","type":"EndDevice","networkAddress":61171,"model":"RTCGQ11LM","vendor":"Xiaomi","description":"Aqara human body movement and illuminance sensor","friendly_name":"MS_DIN_R","manufacturerID":4151,"manufacturerName":"LUMI","powerSource":"Battery","modelID":"lumi.sensor_motion.aq2","hardwareVersion":1,"softwareBuildID":"3000-0001","dateCode":"20170627","lastSeen":1597346207897},{"ieeeAddr":"0x00124b001f320e8e","type":"Router","networkAddress":9873,"model":"CC2530.ROUTER","vendor":"Custom devices (DiY)","description":"[CC2530 router](http://ptvo.info/cc2530-based-zigbee-coordinator-and-router-112/)","friendly_name":"RT_DR","manufacturerID":4447,"manufacturerName":"LUMI","powerSource":"Mains (single phase)","modelID":"lumi.router","hardwareVersion":1,"dateCode":"2018-09-26","lastSeen":1597347234491},{"ieeeAddr":"0x00158d000363e359","type":"EndDevice","networkAddress":2564,"model":"QBKG04LM","vendor":"Xiaomi","description":"Aqara single key wired wall switch without neutral wire. Doesn't work as a router and doesn't support power meter","friendly_name":"LS_GR","manufacturerID":4151,"manufacturerName":"LUMI","powerSource":"DC Source","modelID":"lumi.ctrl_neutral1","hardwareVersion":38,"dateCode":"04-25-2018","lastSeen":1597347260047},{"ieeeAddr":"0x00158d00044c3b2e","type":"EndDevice","networkAddress":22696,"model":"WXKG12LM","vendor":"Xiaomi","description":"Aqara wireless switch (with gyroscope)","friendly_name":"WBTN_GR","manufacturerID":4151,"manufacturerName":"LUMI","powerSource":"Battery","modelID":"lumi.sensor_switch.aq3","hardwareVersion":1,"softwareBuildID":"3000-0001","dateCode":"20180629","lastSeen":1597345329976},{"ieeeAddr":"0x00158d0003f3a1a8","type":"EndDevice","networkAddress":65354,"model":"RTCGQ11LM","vendor":"Xiaomi","description":"Aqara human body movement and illuminance sensor","friendly_name":"MS_GR","manufacturerID":4151,"manufacturerName":"LUMI","powerSource":"Battery","modelID":"lumi.sensor_motion.aq2","hardwareVersion":1,"softwareBuildID":"3000-0001","dateCode":"20170627","lastSeen":1597342493521},{"ieeeAddr":"0x00158d0003fb5c34","type":"Router","networkAddress":33196,"model":"ZNCLDJ11LM","vendor":"Xiaomi","description":"Aqara curtain motor","friendly_name":"CT_GR","manufacturerID":4447,"manufacturerName":"LUMI","powerSource":"Mains (single phase)","modelID":"lumi.curtain","hardwareVersion":17,"dateCode":"08-13-2018","lastSeen":1597347015832},{"ieeeAddr":"0x00158d0003599d0f","type":"EndDevice","networkAddress":1723,"model":"QBKG04LM","vendor":"Xiaomi","description":"Aqara single key wired wall switch without neutral wire. Doesn't work as a router and doesn't support power meter","friendly_name":"LS_ER","manufacturerID":4151,"manufacturerName":"LUMI","powerSource":"DC Source","modelID":"lumi.ctrl_neutral1","hardwareVersion":38,"dateCode":"04-25-2018","lastSeen":1597347248620},
It looks like the coordinator was trying to get all the devices back but none of them responsed.

After a period of time, the adapter itself was dead:
error 2020-08-14 09:01:49: Adapter disconnected, stopping

I noticed that the board was very hot when I tried to unplug and re-plug it.

After re-plug, it gradually got all those devices back.

Can you provide the complete debug logging of this?

It looks like the coordinator was trying to get all the devices back but none of them responsed.

Based on what do you conclude this?

log.txt
The attachment is one of the log file

Can you provide the complete debug logging of this?

It looks like the coordinator was trying to get all the devices back but none of them responsed.

Based on what do you conclude this?

The attachment is one of the log files
log.txt

This is your problem:
Routers: CC2530_CC2591_router_2019_02 x 2

I have bad experience with all other router except cc2652/1352 with latest sdk(3.4 or later).
My network:
1, Xiaomi sensors, only end device, not router like curtain.
2, Router: CC2652
3, ZC: cc1352p

cc2652/1352

Thanks.
It will be appreciated if you could help me with another two questions:

Is it okay to use CC26X2R1 as the coordinator and use CC2652/1352 as routers?
Where could I find the router firmware for  CC2652/1352?

cc2652/1352

Thanks.
It will be appreciated if you could help me with another two questions:
1. Is it okay to use CC26X2R1 as the coordinator and use CC2652/1352 as routers?

2. Where could I find the router firmware for  CC2652/1352?

What channel are you running?

I just update router firmware for CC2652R1 dev board, you can download it here: https://github.com/dzungpv/Z-Stack-firmware/tree/master/router/CC2652R1

I just update router firmware for CC2652R1 dev board, you can download it here: https://github.com/dzungpv/Z-Stack-firmware/tree/master/router/CC2652R1

Thanks!
Just got time to work on it.
The channel is 11.
So I just need to purchase another LAUNCHXL-CC26X2R1 board, flash the router firmware and use it to replace those 2 CC2530 routers, right?
Any other recommendations? The LAUNCHXL-CC26X2R1 board is too big to be used as a router anyway...
I also talked with Sascha, the creator of the slaesh’s CC2652RB stick, it is much more compact.
However, he doesn't have a firm schedule for a router firmware.
Thanks again for your help.
Best regards,
Mandarin Duck

I just update router firmware for CC2652R1 dev board, you can download it here: https://github.com/dzungpv/Z-Stack-firmware/tree/master/router/CC2652R1

Thanks!
Just got time to work on it.
The channel is 11.
So I just need to purchase another LAUNCHXL-CC26X2R1 board, flash the router firmware and use it to replace those 2 CC2530 routers, right?
Any other recommendations? The LAUNCHXL-CC26X2R1 board is too big to be used as a router anyway...
I also talked with Sascha, the creator of the slaesh’s CC2652RB stick, it is much more compact.
However, he doesn't have a firm schedule for a router firmware.
Thanks again for your help.
Best regards,
Mandarin Duck

Use channel 26 and plan your wifi channel with lowest interference. For the CC2652RB, i can build it in free time, but in order to flash it, you must have a programmer, TI kit include programmer so it not the problem.

If you need a cheap router, I'm really happy with this kind of devices:
https://fr.aliexpress.com/item/32966584298.html
I got actually 30 end devices connected with it and I found it even more reliable than HUE bulbs.

If you need a cheap router, I'm really happy with this kind of devices:
https://fr.aliexpress.com/item/32966584298.html
I got actually 30 end devices connected with it and I found it even more reliable than HUE bulbs.

Any of those devices are xiaomi/aqara devices ? They seem to be picky about connecting to routers...

Any of those devices are xiaomi/aqara devices ? They seem to be picky about connecting to routers...
It's mainly xiaomi/aqara devices ! That's why I advice it. The only thing that I don't know if it's a router that support zigbee 3.x.

I just update router firmware for CC2652R1 dev board, you can download it here: https://github.com/dzungpv/Z-Stack-firmware/tree/master/router/CC2652R1

Thanks!
Just got time to work on it.
The channel is 11.
So I just need to purchase another LAUNCHXL-CC26X2R1 board, flash the router firmware and use it to replace those 2 CC2530 routers, right?
Any other recommendations? The LAUNCHXL-CC26X2R1 board is too big to be used as a router anyway...
I also talked with Sascha, the creator of the slaesh’s CC2652RB stick, it is much more compact.
However, he doesn't have a firm schedule for a router firmware.
Thanks again for your help.
Best regards,
Mandarin Duck

Use channel 26 and plan your wifi channel with lowest interference. For the CC2652RB, i can build it in free time, but in order to flash it, you must have a programmer, TI kit include programmer so it not the problem.

Thanks! Just got time to make progress on my HA setup.
I have ordered several slaesh’s CC2652RB sticks, it will spend another 20 days or even more on the way so I guess I should just wait.
I will also try the cheap router recommended by zen2 as well.

Any of those devices are xiaomi/aqara devices ? They seem to be picky about connecting to routers...

It's mainly xiaomi/aqara devices ! That's why I advice it. The only thing that I don't know if it's a router that support zigbee 3.x.

Thanks!
I will get some from our local market.
My coordinator is working under Zigbee 3.X.
I will post here if the router works well with it.


UI design

Few UI design considerations:

Mention what fields are required?
If it is restricted to US, have states a list item.
Geocode the address
Volunteers required is a enterable field. Limit if it can't go over certain limit of characters.
Date started for 1/1/0001. Start from today's date.

for issue 5 see already logged issue #1312
for issue 1 see related issue #1300 .


Updated to include TEMPLATE requirement for Django 1.9+

In Django 1.9+ if you do not add: 'builtins': ['overextends.templatetags.overextends_tags'], to your TEMPLATES section you will receive a TemplateSyntaxError when the overextends template files are rendered: "Invalid block tag on line".  Including 'builtins': ['overextends.templatetags.overextends_tags'], per the overextends docs (and experience) resolves this error.
https://github.com/stephenmcd/django-overextends

Looks good to me! Thanks for fixing

Squashed and merged in 8ac23d0554acaa44776561ce1c9b1cebff5afe46 thanks!


Daisyui incompatible with tailwind >=3.2.2?

Hi,
I'm running into a strange error when bumping a working project with tailwind 3.2.1 to tailwind 3.2.2, with DaisyUI included at any version it fails the build.
When removing DaisyUI from tailwind config, the build succeeds.
I did the whole wipe-cache/node_modules/... reset dance multiple times, tested different DaisyUI versions, changed order of the plugins. It seems to come down to daisyUI meets tailwind 3.2.2 or I'm doing something wrong.
rm -rf .parcel-cache && parcel build --log-level verbose --no-optimize --no-cache | cat
🚨 Build failed.

@parcel/transformer-css: Invalid empty selector

  ./src/main.css:2309:3
    2308 |   border-top-left-radius: 0.5rem;
  > 2309 | } {
  >      |   ^
    2310 |   border-top-left-radius: 0.5rem !important;
    2311 | }:where(.table *:first-child) :where(*:first-child) :where(th, td):last-child {

tailwind.config.js
/** @type {import('tailwindcss').Config} */
module.exports = {
  content: ["./src/**/*.{html,js,jsx,ts,tsx}"],
  plugins: [
    // require('@tailwindcss/typography'),
    // require("tailwindcss-animate"),
    require("daisyui"),
  ],
}

When injecting some console logging into @parcel/transformer-css I find this generated css and indeed, it is missing selectors:
}.\!table :where(thead, tfoot) :where(th, td) {
  --tw-bg-opacity: 1 !important;
  background-color: hsl(var(--b2, var(--b1)) / var(--tw-bg-opacity)) !important;
  font-size: 0.75rem !important;
  line-height: 1rem !important;
  font-weight: 700 !important;
  text-transform: uppercase !important;
}.table :where(tbody th, tbody td) {
  --tw-bg-opacity: 1;
  background-color: hsl(var(--b1) / var(--tw-bg-opacity));
}.\!table :where(tbody th, tbody td) {
  --tw-bg-opacity: 1 !important;
  background-color: hsl(var(--b1) / var(--tw-bg-opacity)) !important;
}:where(.table *:first-child) :where(*:first-child) :where(th, td):first-child {
  border-top-left-radius: 0.5rem;
} {
  border-top-left-radius: 0.5rem !important;
}:where(.table *:first-child) :where(*:first-child) :where(th, td):last-child {
  border-top-right-radius: 0.5rem;
} {
  border-top-right-radius: 0.5rem !important;
}:where(.table *:last-child) :where(*:last-child) :where(th, td):first-child {
  border-bottom-left-radius: 0.5rem;
} {
  border-bottom-left-radius: 0.5rem !important;
}:where(.table *:last-child) :where(*:last-child) :where(th, td):last-child {
  border-bottom-right-radius: 0.5rem;
} {
  border-bottom-right-radius: 0.5rem !important;
}.textarea-bordered {

Any ideas?

Can you please update every dependency (Parcel, daisyUI, Tailwind CSS, PostCSS) to the latest version and try again?
I could not reproduce the issue with tailwindcss 3.2.2 (or even latest version) and parcel 2.8.1
Here's an example repo: https://github.com/saadeghi/daisyui-parcel-table-issue

The issue remains with the latest versions.
I've also tried removing all extra packages used by parcel (except tsx) from parcel/babel/..., but no luck.
I've also tried porting all the project config (package.json, .parcelrc, .babelrc and tsx transform) to your example repo, but it doesn't reproduce there.
It seems something other than the table might be setting off the problem.
.babelrc
{
  "plugins": [
    ["@babel/plugin-transform-react-jsx", {
      "runtime": "automatic",
      "importSource": "shared/src"
    }]
  ],
  "comments": false
}

{
  "extends": ["@parcel/config-default"],
  "reporters":  ["...", "parcel-reporter-static-files-copy"]
}

.postcssrc
{
  "plugins": {
    "tailwindcss": {}
  }
}

package.json example repo everything added
{
  "scripts": {
    "dev": "parcel src/index.html --open",
    "build": "parcel build src/index.html"
  },
  "devDependencies": {
    "daisyui": "^2.43.0",
    "parcel": "^2.8.1",
    "postcss": "^8.4.20",
    "tailwindcss": "^3.2.2"
  },
  "dependencies": {
    "@babel/plugin-transform-react-jsx": "^7.19.0",
    "@parcel/transformer-inline-string": "^2.8.1",
    "autoprefixer": "^10.4.13",
    "parcel-reporter-static-files-copy": "^1.4.0",
    "typescript": "^4.9.4"
  },
  "browserslist": "> 0.5%, last 2 versions, not dead"
}

I have attempted to reproduce the issue, but have been unable to do so in a fresh repository. The repo where the error happens is still private and quite large. I have also tried removing all tables from the project, as it seems this may be what is causing the code to trigger the error, but this did not resolve the issue. Additionally, I have attempted to use cssnano and different build configurations, but the error persists. It appears to occur during the build step, not during CSS optimization. So far, I have not been able to find a solution.
It appears that there may be an incompatibility between parcel2, tailwind, and daisyui. Not sure. Due to the error blocking latest tailwind, I've started the process of removing daisyui from the project step by step, and will also try upgrading to tailwindcss 3.2.2 during the refactoring process. If the problem gets resolved when doing so, it may provide a clue as to where the issue is originating.

I'm sure with default config, Parcel, Tailwind and DaisyUI work together without issue. However, I think your build process is making some modifications to the CSS. For example, there are no !important rules in daisyUI or Tailwind by default but for some reason the code you mentioned is like this:
  ./src/main.css:2309:3
    2308 |   border-top-left-radius: 0.5rem;
  > 2309 | } {
  >      |   ^
    2310 |   border-top-left-radius: 0.5rem !important;

It is repeating the same line of CSS rule, once without !important and the second time with !important
That's weird.
I would like to help fixing this but I'm pretty sure the issue is not from daisyUI so I have to close this issue.
Feel free to continue the conversation. Or if you could provide a example reproduction repo, that would be helpful for finding the issue.

A clue might be found in the 2.26.0 version: I've done the reverse search, check with what daisyui version the build starts showing problems.

With daisyui 2.25.0 and tailwind 3.2.4 it works.
With daisyUI 2.26.0 and tailwind 3.2.4 it fails.
No other changes.
The issue lies somewhere in these changes: https://github.com/saadeghi/daisyui/compare/v2.25.0...v2.26.0

@saadeghi I've discovered the culprit.
There is an empty tbody tag in the project (which gets dynamically filled) and this causes the css builder to remove some parts which apply to  tags I think. And removing these parts creates broken css.
Once I add a stub

 into the tbody, the build error is gone.
Maybe we can do something like "if table used: include the whole css for tables".
I'm going to check if I can somehow make the default build stop doing this behavior and include a full build.
Build error:

          User

No build error anymore:

          User

I removed my previous comment. The root cause is not yet found. The issue remains.

I think the problem is from that part of your build process (I don't know what package or config is doing it) that is adding an !important rule.
Here:

Yes, thanks for joining in the search, it's an annoying problem.
I've checked for that, the problem is that I cannot find anything that sets it off. I've disabled and remove anything so that it becomes a vanilla setup with pure tailwind, daisyUI, JSX transformer and utility classes and components used. And the JSX transformer is not adding new classes.
And Parcel build is quite a mess to debug.
While it is a big project (that used almost all daisyUI components), it is not a complex project.
In the codebase there are no css overrides active, no plugins anymore and !utility classes are never used.
Let's close this and stop the search, while not my preferred choice, I've started removing Daisy from the project to be able to move on.
I'll keep on trying to bump the version and see if it compiles at some point.

I'm running into this exact issue on a repo created yesterday
Default tailwindcss and parcel installation, only with this configuration:
# .parcelrc
 {
"extends": ["@parcel/config-webextension"],
}

I can try getting a reproducible repo tomorrow

I take this back. went to sleep, woke up, cloned the repo to a second computer, and it now compiles correctly
not even sure if it's something wrong with my laptop setup, or if it was just a random heisenbug

@naps62 I'm glad the issue is gone. I still have no idea about the cause of issue but i'm sure it's not from daisyUI. daisyUI and Tailwind CSS do not apply !imporant rules by default and CSS build tools should not do that automatically either.
It's dangerous to use !important in CSS generally because it's the highest CSS specificity and it prevents style overriding.

@saadeghi I have encountered similar issues that the generated CSS have wierd !important rules. And finally I found it's from Tailwind CSS Important modifier.
The problem is, I did not intend to use this feature. But when my code has a same variable name with daisyUI's class name, for example:
const collapse = false
if (!collapse) {
  console.log('not collapse')
}

When building, Tailwind CSS will detect !collapse pattern and apply !important modifier. The generated CSS will be:
.\!collapse {
  display: grid !important;
  overflow: hidden !important;
  position: relative !important
}
.\!collapse>input[type=checkbox],
.collapse-content,
.collapse-title {
  grid-column-start: 1 !important;
  grid-row-start: 1 !important
}
.\!collapse>input[type=checkbox] {
  -webkit-appearance: none !important;
  -moz-appearance: none !important;
  appearance: none !important;
  opacity: 0 !important
}
.\!collapse:focus:not(.collapse-close) .collapse-content,
.\!collapse:not(.collapse-close) input[type=checkbox]:checked~.collapse-content,
.collapse-open .collapse-content {
  max-height: 9000px !important
}
.\!collapse:focus-visible {
  outline: 2px solid hsl(var(--nf)) !important;
  outline-offset: 2px !important
}
.\!collapse:not(.collapse-open):not(.collapse-close) .collapse-title,
.\!collapse:not(.collapse-open):not(.collapse-close) input[type=checkbox] {
  cursor: pointer !important
}
.\!collapse:focus:not(.collapse-open):not(.collapse-close) .collapse-title {
  cursor: unset !important
}
:where(.\!collapse>input[type=checkbox]) {
  z-index: 1 !important
}
.collapse-title,
:where(.\!collapse>input[type=checkbox]) {
  min-height: 3.75rem !important;
  padding: 1rem 3rem 1rem 1rem !important;
  transition: background-color .2s ease-in-out !important;
  width: 100% !important
}
.\!collapse:focus:not(.collapse-close) :where(.collapse-content),
.\!collapse:not(.collapse-close) :where(input[type=checkbox]:checked~.collapse-content),
.collapse-open :where(.collapse-content) {
  padding-bottom: 1rem !important;
  transition: padding .2s ease-in-out, background-color .2s ease-in-out !important
}

I'm not sure whether it's the same problem with this issue. In my case it didn't break the build, most times it influences nothing(except increase the bundle size). But when I apply additional styles to daisyUI's collapse component, it will break the styles.
And I cannot find a configuration in Tailwind's document to disable the Important modifier feature. Finally I renamed these variables to avoid this case.

When building, Tailwind CSS will detect !collapse pattern and apply !important modifier.

@maliut Good catch! This is the reason.
This happens when we use !anything string in our markup and there is style for that using CSS :where() Tailwind generates invalid CSS for it:
https://play.tailwindcss.com/Oy7NHRkftL?file=config (look at Generated CSS)

I created an issue on Tailwind CSS repo: https://github.com/tailwindlabs/tailwindcss/issues/10582

This is fixed in Tailwind CSS 3.2.7

I encountered this exact very frustrating problem too.
I think this behavior is worth to be mentioned in common issues in discussion.

@arily it shouldn't be an issue. It must be fixed if it still exists. Which style is broken for you exactly? Which variable name is causing the issue?

@arily it shouldn't be an issue. It must be fixed if it still exists. Which style is broken for you exactly? Which variable name is causing the issue?

names causing issues:active and disabled, affecting all .active and .disabled classes. For me it was nav and menu.
:active got "!important'd" by :hover, so anything with :active class will lose their visual cues.

I was adding daisyUI to already existing svelte app (an old svelte app made with rollup, though we can't migrate it to vite at the moment due to some reasons)
module.exports = {
  content: ["./src/**/*.{html,js,svelte,ts}"],
  theme: {
    extend: {},
  },
  plugins: [require("daisyui")],
};

if I remove require("daisyui") the build fails.
I used postcss to add tailwind which works fine,
now as soon as I add daisy to the tailwind config it gives the below error.
[!] (plugin svelte) ValidationError: :global(...) must contain a single selector
src/App.svelte
1966:   border-radius: var(--rounded-btn, 0.5rem);
1967: }
1968:   :global(.table) :global(:where(th), :global(td)) {
                        ^
1969:   padding-left: 1rem;
1970:   padding-right: 1rem;
ValidationError: :global(...) must contain a single selector
    at error (/Users/yashash/Documents/GitHub/svelte-report-creator-v1/client/node_modules/.pnpm/svelte@3.46.4/node_modules/svelte/src/compiler/utils/error.ts:25:16)
    at Component.error (/Users/yashash/Documents/GitHub/svelte-report-creator-v1/client/node_modules/.pnpm/svelte@3.46.4/node_modules/svelte/src/compiler/compile/Component.ts:467:4)
    at Selector$1.validate_global_with_multiple_selectors (/Users/yashash/Documents/GitHub/svelte-report-creator-v1/client/node_modules/.pnpm/svelte@3.46.4/node_modules/svelte/src/compiler/compile/css/Selector.ts:159:17)
    at Selector$1.validate (/Users/yashash/Documents/GitHub/svelte-report-creator-v1/client/node_modules/.pnpm/svelte@3.46.4/node_modules/svelte/src/compiler/compile/css/Selector.ts:146:8)
    at /Users/yashash/Documents/GitHub/svelte-report-creator-v1/client/node_modules/.pnpm/svelte@3.46.4/node_modules/svelte/src/compiler/compile/css/Stylesheet.ts:104:13
    at Array.forEach (<anonymous>)
    at Rule$1.validate (/Users/yashash/Documents/GitHub/svelte-report-creator-v1/client/node_modules/.pnpm/svelte@3.46.4/node_modules/svelte/src/compiler/compile/css/Stylesheet.ts:103:18)
    at /Users/yashash/Documents/GitHub/svelte-report-creator-v1/client/node_modules/.pnpm/svelte@3.46.4/node_modules/svelte/src/compiler/compile/css/Stylesheet.ts:447:10
    at Array.forEach (<anonymous>)
    at Stylesheet.validate (/Users/yashash/Documents/GitHub/svelte-report-creator-v1/client/node_modules/.pnpm/svelte@3.46.4/node_modules/svelte/src/compiler/compile/css/Stylesheet.ts:446:17)
    ```


-y should execute silently

A common usage for dpx is to leverage it within github actions to prevent the manual dart pub global activate... step
In this case we always pass -y since it is known that the executable doesn't actually exist, and we want to force install it
When doing this though, the output for installing the package is still emitted:
Need to install the following packages:
Git repository<EMAIL_ADDRESS>
the major downside of this is if we pipe the output of a command this verbose header is included:
$ dpx -y my_command > out.json
$ cat out.json
Need to install the following packages:
Git repository<EMAIL_ADDRESS>{
 "command_json": "here"
}

Thoughts on silencing all command installation output when -y is provided?

How about updating dpx to write those preamble logs to stderr instead of stdout so that stdout can be redirected independently and won't include any of the noise from dpx itself?

Unfortunately for my use case, the output I'm trying to capture is actually from stderr (nuance of the current implementation in semver-audit-dart)
Arguably, this is incorrect, and should actually be stdout, but I'm unsure of the downstream changes that adjusting that would be
More generally though, is using stderr for something like that misuse of what stderr is designed to be used for? It is my impression that some executions rely on the output of stederr to determine failure cases

I think it varies largely because there are only two options to write to, but from what I've seen on the topic, the expected output of a command should go to stdout and everything else (not just errors) should go to stderr. Additionally, I think the exit code should be the primary indicator of whether it failed (and what type of failure it was), not the presence of content on stderr.
The expected output of a command is important here, since it could mean that the same type of content (e.g. help or usage text) goes to a different place based on the command being run. If the user runs dpx --help, they're expecting to receive help output, so it should go to stdout (which would let them pipe it to less, for example). Alternatively, if the user runs dpx --wrong-flag, we might still want to print that same help output, but it should go to stderr because it's no longer intended output of the command, it's an error.
Similarly for the use case in this issue, I'd view dpx -y my_command as a command intended to eventually run my_command. If it isn't already installed, we would install it and (at least as currently implemented) produce some output about that install, but that output isn't a part of the ultimate goal of that command, so it should be on stderr.

For the suggestion in the original issue description of having -y execute silently, I think I'd rather see us implement some level of logging verbosity control. That way it would still at least be possible to have dpx -y my_command print out information about the install process (could be useful for debugging).

Huh, seems more murky than I was expecting
I do like this though, seems like a good principal behind the concept

"Well, it's an explicit request for help so it should go to output."

By that logic, I could get behind the installation output sending to stderr


i want to user &::after{} and @keyframes progress{} css property in css inlineStyle

i Have used like below:
const style = {
position: 'relative',
overflow: 'hidden',
width: '50%',
height: '40px',
background: '#f3f3f3',
'&::after':{
content: '',
position: 'absolute',
top: '0',
left: '0',
width: '100%',
height: '100%',
background: 'linear-gradient(90deg,#f3f3f3,#fbfbfb,#f3f3f3)',
animation: 'progress 1s ease-in-out infinite',
},
'@keyframes progress':{
'0%': {
transform: 'translate3d(-100%, 0, 0)',
},
'100%': {
transform: 'translate3d(100%, 0, 0)'
}
}
}

This is an issue tracker for React docs. Please ask your question on a relevant support forum. Thanks!

This is also issue. You can check. It is not working
On Thu 22 Mar, 2018, 9:19 PM Dan Abramov<EMAIL_ADDRESS>wrote:

This is an issue tracker for React docs. Please ask your question on a
relevant support forum. Thanks!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/reactjs/reactjs.org/issues/699#issuecomment-375355861,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ATNRaMOJoduh_oEwv5IWV2f7JF1Z5sUnks5tg8gQgaJpZM4S2ufx
.


Css fixes

Things Modified:
Changes in CSS of all HTML pages, Improvements in HTML and CSS, Color improvements, Margin, Padding
Issue No. #56
Changes Introduced

GitHub page link please @skpandey885

@2024-SANDHYA  https://skpandey885.github.io/Blood-Buddy/

The fonts you've used make the appearance look less formal and poor. The registration button is poorly designed. Not gonna work, doesn't look good. Don't work on this.


New approach for localizing Apple and Android voice names

As initially mentioned in #38 and #29, documenting all possible combinations for localized voices on Apple and Android devices feels like a dead-end.
The more voices that I add to this repo, the longer it takes and JSON files keep on getting larger and larger.
To work around this issue, I'm opening a draft PR while I revisit all languages one by one to:

identify voices that are localized
and document localized strings for each language

This will be a massive effort, but feels like the best option to continue extending the scope of this project with more and more languages.
I won't merge this PR until we can offer an open-source JS/TS library to work with these localized strings and offer the feature set initially proposed in #9.

I'm moving this one to "Ready for review" and the review itself will be the code implementation.

Now that I've worked on how a code based approach could work, I'm tempted to drop languages/regions localization entirely and just focus on how the different voice quality presets are localized on Apple devices.
With such a minimal take on localization, it would make more sense to keep a single localization file that contains all languages.
We would no longer be able to match Android voices though, but since these are not truly voices anyway, I'm not sure we'd really lose anything.

I only care about Microsoft voices, azure cloud voices are great.
Not sure how they get exposed to the user via Edge Android, Edge iOS and Edge MacOS.
So, no complaint about unable to match google voices. As long as it is easy to get a list of voices if no matches are found.

Not sure how they get exposed to the user via Edge Android, Edge iOS and Edge MacOS.

Edge voices are not affected by localization issues at all, so this doesn't make any difference.

Spending time with @panaC yesterday was very helpful to identify various issues with this PR. Hopefully things are in a better state now.
We've also discovered Intl.DisplayNames which makes my previous effort of documenting languages/regions even more redundant. I'm keeping these extended locales in the PR for now but will open an issue to drop them once we've fully evaluated to which extend we can rely on Intl.DisplayNames.


Support MQTT-5 will message with message expiry interval and delay interval

Master Issue: #369
Motivation
Support MQTT-5 will message with message expiry interval and delay interval.
Documentation

[x] no-need-doc

Codecov Report

Merging #670 (b27dc21) into master (0d0af93) will increase coverage by 0.33%.
The diff coverage is 74.39%.

@@             Coverage Diff              @@
##             master     #670      +/-   ##
============================================
+ Coverage     77.97%   78.31%   +0.33%
- Complexity      910      952      +42
============================================
  Files           108      108
  Lines          3923     4058     +135
  Branches        276      307      +31
============================================
+ Hits           3059     3178     +119
- Misses          702      711       +9
- Partials        162      169       +7

Impacted Files
Coverage Δ

...streamnative/pulsar/handlers/mqtt/MQTTService.java
82.60% <0.00%> (-1.84%)
:arrow_down:

...s/mqtt/proxy/MQTTProxyProtocolMethodProcessor.java
77.89% <0.00%> (-0.86%)
:arrow_down:

...lsar/handlers/mqtt/support/Qos1PublishHandler.java
64.81% <0.00%> (ø)

...qtt/support/MQTTBrokerProtocolMethodProcessor.java
78.84% <41.17%> (-0.99%)
:arrow_down:

...lsar/handlers/mqtt/support/WillMessageHandler.java
78.04% <71.42%> (-1.37%)
:arrow_down:

...handlers/mqtt/restrictions/ClientRestrictions.java
66.66% <80.00%> (ø)

...ar/handlers/mqtt/utils/PulsarMessageConverter.java
89.16% <92.30%> (+3.45%)
:arrow_up:

...lsar/handlers/mqtt/messages/MqttPropertyUtils.java
89.47% <100.00%> (-0.78%)
:arrow_down:

.../pulsar/handlers/mqtt/messages/ack/MqttPubAck.java
87.80% <100.00%> (+0.30%)
:arrow_up:

...ive/pulsar/handlers/mqtt/support/MQTTConsumer.java
97.61% <100.00%> (+0.32%)
:arrow_up:

... and 2 more

Continue to review full report at Codecov.

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


Unable to use output of one subworkflow as the input of another subworkflow

Describe the bug
Initially in attempting to use the list of outputs from a foreach subworkflow, the workflow fails with a validation error because the output object of the subworkflow is assigned a random ID that does not match the ID of the input schema of the second subworkflow.
2024-01-29T18:14:14+01:00	error	source=main	Invalid workflow (input validation failed for workflow step 'cpu_index_loop' stage 'execute' (Validation failed: error while validating sub-type of property Items with type *schema.ListSchema (Validation failed: validation failed for object schema ID IndexObject. ID qb5jeq63hl52vihbj04tnbwq0mem4ybj does not match.)))

I was advised to define an outputSchema for the first subworkflow in order to define its ID explicitly so that it matches the input of the second workflow. After adding this to the first subworkflow:
...
outputSchema:
  success:
    schema:
      root: IndexObject
      objects:
        IndexObject:
          id: IndexObject
          properties:
            pcp:
              type:
                type_id: list
                items:
                  type_id: any

outputs:
  success:
    pcp: !expr $.steps.pcp.outputs.success.pcp_output

After doing this, the workflow produced a new error, which may be a bug in the go SDK:
2024-01-29T18:16:15+01:00	error	source=main	Invalid workflow (invalid workflow (failed to load schema for step sysbench_cpu_loop (invalid workflow (Validation failed for 'outputSchema': Field cannot be set (reflect.Value.Convert: value of type map[string]*schema.StepOutputSchema cannot be converted to type map[string]interface {})))))

To reproduce
The WIP workflow that has this configuration is here: https://gitlab.com/redhat/edge/tests/perfscale/arcaflow-workflow-sysbench/-/tree/new-opensearch-plugin?ref_type=heads

Possible bug location is within this function: https://github.com/arcalot/arcaflow-plugin-sdk-go/blob/f5ab86d119d6746c43d6c589e38ab91cec5730e9/schema/object.go#L99

This issue must be resolved within the arcaflow engine project. A new issue has been created.


Fix Azure-related data races

azure/api/mock: Add (*API).updateInstancesLocked helper
azure/api/mock: Make copy of instance map to avoid data races
azure: Set interface ID upfront in a dedicated method

Fixes: https://github.com/cilium/cilium/issues/13619

ci-aks

ci-aks

ci-aks


Unable to load workflows

Is this a BUG REPORT or FEATURE REQUEST?:
BUG
What happened:
Installed using, https://github.com/argoproj/argo/blob/master/manifests/namespace-install.yaml
Argo UI errors: Unable to show data Internal server error

What you expected to happen:
UI shows the workflows with no issues.
How to reproduce it (as minimally and precisely as possible):
Just install namespace-install.yml above
Anything else we need to know?:
Environment:

Argo version:2.2.1

$ argo version

Kubernetes version :1.9

$ kubectl version -o yaml

Other debugging information (if applicable):

argo-ui logs error:

error: workflows.argoproj.io is forbidden: User "system:serviceaccount:argo:argo-ui" cannot list workflows.argoproj.io at the cluster scope {"code":403,"timestamp":"2018-12-06T00:08:45.055Z"}

Update,
Argo version:2.2.0

Issue fixed in master but still exists in v2.2.1. UI tries to load workflows from all namespaces and fails if argo-ui account does not have permissions.  Only workaround for now is to use pre-release image argoproj/argoui:v2.2.1-37808b1 and manually add FORCE_NAMESPACE_ISOLATION env variable in argo-ui deployment:
   spec:
      containers:
      - env:
        - name: FORCE_NAMESPACE_ISOLATION
          value: "true"
        - name: ARGO_NAMESPACE
          valueFrom:
            fieldRef:
              apiVersion: v1
              fieldPath: metadata.namespace
        - name: IN_CLUSTER
          value: "true"
        - name: ENABLE_WEB_CONSOLE
          value: "false"
        - name: BASE_HREF
          value: /
        image: argoproj/argoui:v2.2.1-37808b1

That works, thanks!

Is it possible to install `argo-events namespace scoped?


ECS Label keys for domain.main and domain.sans contain invalid characters

Do you want to request a feature or report a bug?

Bug

What did you do?
I've been attempting to stand up Traefik in Amazon ECS, handling SSL termination and proxying the requests back to an nginx container running php-fpm.
The nginx container receives all traffic that hits the NLB in front of Traefik, via a rule:
Method(`GET`,`POST`,`HEAD`,`PUT`,`PATCH`,`DELETE`)

This is because it may receive traffic for whitelabels that can point their domains to the service.
The stack is still in dev and I'm trying to get LE to provide a certificate for a domain in the .dev TLD (mandatory HSTS). So I set a few labels as advised.
traefik.http.routers.php-fpm.tls.domains[0].main=example1.dev
traefik.http.routers.php-fpm.tls.domains[0].sans=www.example1.dev
traefik.http.routers.php-fpm.tls.domains[1].main=example2.dev
traefik.http.routers.php-fpm.tls.domains[1].sans=www.example2.dev

AWS is rejecting this configuration with this message:
Docker label key traefik.http.routers.php-fpm.tls.domains[1].sans contains invalid characters, does not match pattern ^[_\-a-zA-Z0-9./]+$

Per Docker's guidelines on label metadata, AWS is in fact right to enforce this.
Thus, it may be wise to modify these labels to be within spec, perhaps by omitting the square brackets and simply having an integer to iterate over.

What did you expect to see?
A running config with multiple names and SANs to pull certificates for.
What did you see instead?
The configuration is rejected by ECS as invalid.
Output of traefik version: (What version of Traefik are you using?)

N/A as ECS rejects the configuration instead of Traefik, but per the docs this is the current advised behavior.
What is your environment & configuration (arguments, toml, provider, platform, ...)?
AWS ECS, EC2 task definitions.

If applicable, please paste the log output in DEBUG level (--log.level=DEBUG switch)
N/A

Hello @pxdnbluesoul,
You need to enclose the whole label in double quotes:
 - "traefik.http.routers.router1.tls.domains[0].main=foobar"

as per the docs that you referenced.
Please let us know if this works for you.

The ECS console does not allow creating labels in this way, only as key-value pairs in separate fields.

having the same issue, any workaround?

having the same issue, any workaround?

I ended up using the route53 provider and Host() rules. Not ideal for us but doing the job for the time being. Fixing this approach using the domains object would be a huge boon.

I ended up using the route53 provider and Host() rules. Not ideal for us but doing the job for the time being. Fixing this approach using the domains object would be a huge boon.

Thanks, route53 suits me as this is what I'm already using, and it seems to work indeed. But I think this is getting a certificate for each domain name in the rule, right?
I was hoping to be able to add something like this as labels so I can use wildcard domains, but yeah, anyway, it will do for now
"traefik.http.routers.sam-api.tls.domains[0]main": "${hostname}",
"traefik.http.routers.sam-api.tls.domains[0]sans": "*.${hostname}"

maybe this could be solved like these did
https://github.com/gliderlabs/connectable/pull/31
using an alternative notation like traefik.http.routers.sam-api.tls.domains.0.main": "${hostname}"

Thanks, route53 suits me as this is what I'm already using, and it seems to work indeed. But I think this is getting a certificate for each domain name in the rule, right?
I was hoping to be able to add something like this as labels so I can use wildcard domains, but yeah, anyway, it will do for now
"traefik.http.routers.sam-api.tls.domains[0]main": "${hostname}",
"traefik.http.routers.sam-api.tls.domains[0]sans": "*.${hostname}"

maybe this could be solved like these did
https://github.com/gliderlabs/connectable/pull/31
using an alternative notation like traefik.http.routers.sam-api.tls.domains.0.main": "${hostname}"

I just ran into an issue where I have a lot of subdomains and I hit the lets encrypt rate limit. It would be good if this is fixed.

Have almost the exact same use case as @tiberiu89 where we're trying to use a wildcard domain name for containers in ECS, using route53 as our provider. Currently we're using the Host() rule, but this is acquiring a new certificate for every sub-domain, and we're starting to run quite a few of them which will eventually bump up against LetsEncrypts limits at some point.
Has anyone found any work-arounds for this issue?

... same issue... wildcard domains for TLS.

Same issue.  wildcard domains for TLS prevent me deploying to AWS.

Still no fix?

Facing the same. Still no fix due to documentation.
The only found workaround is to use HostRegexp() and generate default certificate


[BUG]: Sketch axes visible after using Exit Sketch keyboard shortcut

Describe the bug
This may or may be intended behaviour but it is certainly inconsistent with the 'Exit Sketch' button in the toolbar.  I was able to get the sketch axes to persist in the 3D mode using the 'Exit Sketch' keyboard shortcut and wasn't able to do the same with the button in the toolbar.
Steps to Reproduce

Open app.zoo.dev.
If there is any code, clear it and refresh the page.
Enter sketch mode (any plane) with the 'Enter Sketch' tool.
Exit sketch mode with the 'Exit Sketch' keyboard shortcut, which is ESC for me.
Note the axes continue to be rendered in 3D mode, even when panning the camera.

Expected Behavior
The behaviour of the 'Exit Sketch' keyboard shortcut would match the dedicated button, i.e., the camera would return to 3D mode without the sketch axes being drawn.
Screenshots and Recordings
Screencast from 2024-06-05 16-43-07.webm
Desktop OS
Ubuntu 23.10
Browser
Firefox 124.0.2
Version
v22.0.0
Additional Context
No response

I was able to recreate these issues.

State
No Code
Colored Planes Visible
Visible Axis Helpers
Grid (if settings are on)

Page Load / Idle
✅
✅
❌
✅

On ESC exit
❌
✅
✅
✅

On Button Click Exit
✅
✅
✅
✅

idle -> Sketch Mode -> ESC actually throws an error and I need to hit ESC twice.
The ideal state is the Page Load / Idle. So we need to have the other workflows match this.
Here are the workflows
Page Load / Idle -> Start Sketch -> Exit Sketch
Page Load / Idle -> Press S ->  Press ESC


Db-icon and Db-Button not working

https://db-ui.github.io/elements/version/v0.16.1/?path=/docs/db-icon--live-demo
on the playground is also seen that db-icon is not working at all and this effects db-button as well using with db-icon together.
Workaround for db-button setting    data-icon=editattribute

@EmilAlipiev thanks a lot for your feedback.
This is most likely related to that DB UI Core stylesheets aren't correctly rendering the icons declarations for the regular / non-enterprise styling, that we're using within our DB UI Elements examples.
As this is a known bug, we're even already working on releasing the solution.


the "onSlideChangeEnd" event does'nt trigger when I try to slide fast.

just as the title desc.

Duplicate of #1216


Is it possible to set a column to its default value during update?

I don't feel like this is the best place for these sorts of questions, but I'm not sure what the right place is, so feel free to redirect me.
I have a table with a column with a default value. I know on insert, I can just leave that column out of my insertable type, and it will take the default value. Is there a way to "reset" it to the default value via update?

A good place to ask questions is in gitter. There's a link in the README. There's not a way to set a column to its default right now, but it's something we're exploring.


docs: update and fix BulkWriter docs

Hide _sendBatch() from docs
Add detailed callback documentation for success/error listeners.

@thebrianchen I'm not sure if this is the best place to ask this, but I'll give it a shot. I'm trying to use the BulkWriter to backfill a new field onto approximately six million documents in a Firestore collection. I've been running the script below on small test batches, around 20,000 - 50,000 docs, and I'm encountering RATE_LIMIT_EXCEEDED errors. Is there something I'm doing incorrectly here, or perhaps there's something I'm missing?
Any help would be appreciated!
const { Firestore } = require('@google-cloud/firestore');
const fs = require('fs');
const { differenceInSeconds } = require('date-fns');

const folder = 'input';
const fileName = 'bq-results-20210422';

const collectionName = 'orders';
const flushValue = 500;
let totalCounter = 0;
let operationCounter = 0;

async function bulkWriter() {
    try {
        const sDate = new Date();
        console.log(`Start time: ${sDate}`);

        const docData = await fs.readFileSync(`./${folder}/${fileName}.json`, 'utf-8').split('\n');

        const firestore = new Firestore();
        let bulkWriter = firestore.bulkWriter();

        docData.forEach(async data => {
            const { fsDocId } = JSON.parse(data);
            const documentRef = firestore.doc(`${collectionName}/${fsDocId}`);

            bulkWriter.update(documentRef, { isFraud: false })
                .then(result => fs.appendFileSync(`./output/writeSuccess.json`, `${result}\n`))
                .catch(error => fs.appendFileSync(`./output/writeFailures.json`, `${error}\n`))

            totalCounter++;
            operationCounter++;
            if (operationCounter === flushValue) {
                operationCounter = 0;
                await bulkWriter.flush().then(() => {
                    console.log(`Flush complete`);
                });
            };
        });

        await bulkWriter.close().then(() => {
          console.log('Executed all writes');
        });
        console.log(`Total: ${totalCounter}`);

        const eDate = new Date();
        console.log(`End time: ${eDate}`);
        console.log(`Running time (in seconds): ${differenceInSeconds(eDate, sDate)}`);
    } catch(error) {
        console.error(error);
    };
};

bulkWriter();


Compatibility with lossless scaling

Lossless Scaling frame generation works well to smooth out the low framerate of BG2, making it far easier on the eyes. But when lossless scaling is enabled the Radar Overlay doesn't stay on top. Lossless scaling keeps the window in windowed mode, but on top of Rader Overlay. This happens with both normal and alternate renderer in BG2 options. And with any Lossless Scaling settings.
It is possible to get Rader Overlay above BG2+Lossless Scaling with Autohotkey, using: F12::WinSetAlwaysOnTop -1, "BG Overlay"
That doesn't work full since newly created windows aren't affected, but it proves it's possible at least.

Hii!
I wanted to try lossless scaling too but the author made it unavailable for my country.
There is not much i can do


Add functional tests

Use a separate folder for functional tests like this article does for integration tests. Refer another article as well

Still need to add tests for starlark templates to both API and plugin. Also need to add tests for error scenarios for the API


[C++][Parquet] Support writing (and test reading) boolean values with RLE encoding

This is supported by the Parquet specification, we should ensure that we are able to read such data
Reporter: Wes McKinney / @wesm
Assignee: Xuwei Fu](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=mwish) / @mapleFU
Note: This issue was originally created as PARQUET-1199. Please see the migration documentation for further details.

Jim Pivarski / @jpivarski:
I happen to have appropriate test files. The following is correct output.
https://github.com/diana-hep/oamap/blob/master/tests/samples/record-primitives.parquet
https://github.com/diana-hep/oamap/blob/master/tests/samples/nullable-record-primitives.parquet

The following is correct output from pyarrow 0.8.0.
>>> import pyarrow.parquet
>>> f1 = pyarrow.parquet.read_table("record-primitives.parquet", columns=["u1", "u4"])
>>> f2 = pyarrow.parquet.read_table("nullable-record-primitives.parquet", columns=["u1", "u4"])
>>> f1[0]
<pyarrow.lib.Column object at 0x7ec13d01ea50>
chunk 0: <pyarrow.lib.BooleanArray object at 0x7ec13d09a3c0>
[
 False,
 True,
 True,
 False,
 False
]
>>> f1[1]
<pyarrow.lib.Column object at 0x7ec1508546c0>
chunk 0: <pyarrow.lib.Int32Array object at 0x7ec13d09a0a8>
[
 1,
 2,
 3,
 4,
 5
]
>>> f2[0]
<pyarrow.lib.Column object at 0x7ec13d01e960>
chunk 0: <pyarrow.lib.BooleanArray object at 0x7ec13d09a3c0>
[
 NA,
 True,
 NA,
 False,
 NA
]
>>> f2[1]
<pyarrow.lib.Column object at 0x7ec1508546c0>
chunk 0: <pyarrow.lib.Int32Array object at 0x7ec13d09a0a8>
[
 1,
 NA,
 NA,
 NA,
 5
]

Wes McKinney / @wesm:
We'll have to do some work in parquet-cpp to add this as an option

Jim Pivarski / @jpivarski:
SORRY--- I misread the issue. This is plain encoding (encoding == 0, PLAIN). I don't know how to force it to generate RLE encoding (3).

Gang Wu / @wgtmac:
This is resolved in [GH-15107: [C++][Parquet] Parquet Encoder: Support RLE for Boolean by mapleFU · Pull Request #34526 · apache/arrow (github.com)|https://github.com/apache/arrow/pull/34526]


accordion - Learn about Motions to Modify formatting bullet points are off

Your children's schedule changes - bullet off
Check the whole step

Done


Check Yamamura at normal incidence

Check the following implementation of Yamamura's sputtering yields at normal incidence against published values.

The following slides include verification of sputtering yield for normal incidence.
sputtering_yield_for_normal_incidence.pdf

Excellent


Google maps doesn't show HTML objects on ios

Bug Report
Plugin(s)
@Capacitor/googlemaps
Capacitor Version

  @capacitor/cli: 4.6.1
  @capacitor/android: 4.6.1
  @capacitor/core: 4.6.1
  @capacitor/ios: 4.6.1

Platform(s)
IOS
Problem
I recently upgraded to capacitor 4 & used @Capacitor/googlemaps instead of capacitor-community/google-maps
It works fine on android devices but i got an issue running it on IOS devices
it takes all the screen and hide all HTML elements on the page seems like its come over the webview itself.
as shown on the image:

as you can see both header & footer are gone away i searched a lot about that issue but i didn't get any workaround or solution.
also if it will help i got on xcode debug that error direct after map creation :
2022-12-08 23:36:03.319063+0300 App[3647:1011396] [core] "Error returned from daemon: Error Domain=com.apple.accounts Code=7 "(null)""

If you can help with that thank you.

You are most likely using @capacitor/google-maps. You are now in the @capacitor-community/google-maps repository.


increase consensus reactor queue capacities

This PR expands a few of the reactor queue capacities, not unlike those found in the only p2p stack. This has been tested on roughly 10 nodes for about 2 weeks on mamaki, and has effectively fixed the downtime many validators have been experiencing.
The capacities picked were rather arbitrary. The legacy p2p stack had infinite queue capacities, so increasing these to arbitrarily large numbers is as safe as that.

Since we've been testing this for a few weeks, I think this is safe enough to include in an official release as an intermediate step to increase network stability until we can downgrade.