libvterm failed to compile on Windows in CI

This PR should fix a build error on Windows CI (AppVeyor).
While looking at this, I also noticed that struct VTermLineInfo in vterm.h uses bitfields, so I assume saving memory there matters there:
typedef struct {
  unsigned int    doublewidth:1;     /* DECDWL or DECDHL line */
  unsigned int    doubleheight:2;    /* DECDHL line (1=top 2=bottom) */
  unsigned int    continuation:1;    /* Line is a flow continuation of the previous */
} VTermLineInfo;

Yet sizeof(VTermLineInfo) is 4 and could potentially be 1. if we did:
typedef struct {
  unsigned char    doublewidth:1;     /* DECDWL or DECDHL line */
  unsigned char    doubleheight:2;    /* DECDHL line (1=top 2=bottom) */
  unsigned char    continuation:1;    /* Line is a flow continuation of the previous */
} VTermLineInfo;

That builds with gcc or clang, but I think that to be pedantic, I recall reading that bitfields should use int or unsigned int so it's maybe not portable (not sure).

Dominique wrote:

This PR should fix a build error on Windows CI (AppVeyor).
While looking at this, I also noticed that struct VTermLineInfo in vterm.h uses bitfields, so I assume saving memory there matters there:
typedef struct {
  unsigned int    doublewidth:1;     /* DECDWL or DECDHL line */
  unsigned int    doubleheight:2;    /* DECDHL line (1=top 2=bottom) */
  unsigned int    continuation:1;    /* Line is a flow continuation of the previous */
} VTermLineInfo;

Yet sizeof(VTermLineInfo) is 4 and could potentially be 1. if we did:
typedef struct {
  unsigned char    doublewidth:1;     /* DECDWL or DECDHL line */
  unsigned char    doubleheight:2;    /* DECDHL line (1=top 2=bottom) */
  unsigned char    continuation:1;    /* Line is a flow continuation of the previous */
} VTermLineInfo;

That builds with gcc or clang, but I think that to be pedantic, I recall reading that bitfields should use int or unsigned int so it's maybe not portable (not sure).

Thanks for the fix.
Please chat with Paul Evans about the bitfields. I'm trying to stay
close to the upstream version to make merging patches easier.  I still
run into a lot of conflicts, because of these C99 constructs that not
all compilers can handle.  I haven't been able to convince Paul to use
C90 syntax.  C99 might be a bit nicer, but it blocks using libvterm with
older compiilers.
--
Never eat yellow snow.
/// Bram Moolenaar --<EMAIL_ADDRESS>-- http://www.Moolenaar.net   \
///        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \
\\  an exciting new programming language -- http://www.Zimbu.org        ///
\\            help me help AIDS victims -- http://ICCF-Holland.org    ///

Should we drop support for older MSVC (2010, 2012 and 2013)?
MSVC 2015 and later have better support for C99, and we already use MSVC 2015 in vim-win32-installer.

Ken Takata wrote:

Should we drop support for older MSVC (2010, 2012 and 2013)?  MSVC
2015 and later have better support for C99, and we already use MSVC
2015 in vim-win32-installer.

I do usually build with MSVC 2015.  Still, I like to get these errors,
because there are several other systems with a compiler that can't
handle these constructs.  And we don't have those in CI, depends on
individuals reporting problems.
I'm not sure when dropping C90 would be possible.  Switching to C99
brings in a few minor nice things, but nothing drastic.
--
Although the scythe isn't pre-eminent among the weapons of war, anyone who
has been on the wrong end of, say, a peasants' revolt will know that in
skilled hands it is fearsome.
-- (Terry Pratchett, Mort)
/// Bram Moolenaar --<EMAIL_ADDRESS>-- http://www.Moolenaar.net   \
///        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \
\\  an exciting new programming language -- http://www.Zimbu.org        ///
\\            help me help AIDS victims -- http://ICCF-Holland.org    ///


Change update checker version source

https://github.com/godotengine/godot/pull/75916#discussion_r1566912471
Don't merge until the page is actually up :D

The page https://godotengine.org/versions.yml should serve the file needed. @KoBeWi please test it out to see if there is anything wrong/missing.

It's a bit more work on the website side, but shouldn't we expose the data as an easier-to-parse JSON so we can simplify the logic (and third-party project managers / hubs could also use it via our JSON parser, instead of manually implementing a YAML one)?

I'm fine with either, I think json is more web-friendly, so we should probably use that. Happy to make the adjustments needed, but would like to get at least specifications to generate the file with all the information required.

The file loads fine.
We could replace it with JSON, but technically parsing the file line-by-line is more efficient (with JSON you need to parse the whole file and then search for data). JSON would make the code simpler, but since it's already written, it's fine either way.
As for the specs, it would be best if it was an array of dictionaries, sorted from newest to oldest. Each dictionary needs a version number and flavor/name. The download archive link can be generated from version and release notes are unused, so they don't need to be included.

The download archive link can be generated from version and release notes are unused, so they don't need to be included.

I think the release notes could be used in the future, or by other users of this file, to link directly to release notes. So I'd suggest including them.
As for the download, I'd suggest including it too, in case we ever change the URLs for it.
Currently it's constructed as "https://godotengine.org/download/archive/" + found_version, but if we change this in the future, having it in the JSON means we can just update the JSON and all past Godot versions will still have working links instead of 404s.
Alternatively, we could include just the download archive URL "https://godotengine.org/download/archive/" as a field in the JSON, that can be read by any user and used to compose the full URL for each version, provided we're committed to always have such URLs like "URL_BASE/4.3-dev5".

I would muse, for further Future Proofing, it would be nice if the actual URL checked is an editor setting, kinda like how you can determine where to download the export templates in that URL?

I made the simplest conversion and the file is now a json file: https://godotengine.org/versions.json
If any other field should be included it can be added to the regular _data/versions.yml.
Let me know if further changes are needed!

I made the simplest conversion and the file is now a json file: https://godotengine.org/versions.json If any other field should be included it can be added to the regular _data/versions.yml.
Let me know if further changes are needed!

Looks good! For ease of use, should we add the https://godotengine.org prefix to the release notes fields?

They all include the full path in the json file now 👍

For some reason Godot loads only half of that file 🤔I printed the received string and it cuts abruptly.

Updated to use the new JSON.

Thanks!


Compare two files that git doesn't recognize as a rename

Description
The particular use-case I'm encountering is migrating a JavaScript codebase to TypeScript and when there have been too many changes in a file git will no longer treat it like a rename but as a delete and add. We try to limit the amount of changes in a file to avoid this but sometimes, especially if the file is smaller, it's unavoidable without having multiple PRs which adds a bunch of administrative overhead to getting the work done.
I would like to see an option to select two files or even using some simple heuristics like seeing a delete and add with the file path being the same except the extension and then a way to compare them (perhaps by linking to an external tool).
Screenshot

Example URL
https://github.com/refined-github/refined-github/pull/5562/files

Unfortunately there's no way to ask GitHub to compare two unrelated files nor it's possible for us to reimplement the whole diff view. This would have to load its own diffing tool and thus be its own extension.


Cannot reproduce the pretrained model accuracy for NTU120 无法复现提供的pretrained模型的accuracy

Hi,
Thanks for the great work. I follow the given config files to run both the joint and the bone streams for the NTU120 dataset. However, I could not obtain the accuracy as high as the provided pretrained models.
非常感谢您的好工作. 我用您给的config文件来跑joint和bone stream的NTU120数据集. 但是, 我跑不到像pretrained model那么高的结果.
For XSub Joint, I got top-1 82.19 and top-5 95.77. However, the results for the pretrained model are: top-1 83.32 and top-5 96.06.
For XSub Bone, I got top-1 84.69 and top-5 96.76. However, the results for the pretrained model are: top-1 85.88 and top-5 97.04.
For XSet Joint, I got top-1 84.05 and top-5 95.97. However, the results for the pretrained model are: top-1 84.44 and top-5 95.89.
For XSet Bone, I got top-1 86.47 and top-5 96.89. However, the results for the pretrained model are: top-1 87.39 and top-5 97.36.
I received consistent worse performance. Can you please enlighten me on how to get the accuracy that is the same as the provided pretrained models? Thank you very much!

Hi Zhenyue,
Thanks for your interest.

I would suggest trying the joint-bone ensemble results first, and see if they deviate a lot from those produced by the pre-trained models, as the single-stream performance does have more fluctuations than I expect.  Note also that worse single-stream models sometimes actually give better ensemble results.
Do pay attention to sensitive hyperparams like LR, full/forward batch sizes, and the number of devices. Have you changed any of these? e.g. a smaller forward_batch_size will harm batch norm.
Without further context, I can't really help debugging the performance, and it'd be helpful if you could share the config for those runs (by default they are at the top of log.txt; an example here).
Note also that the pretrained models are the best models during training rather than the last saved models (at the end of training).
The pretrained models are trained using the procedure in README, and, if I remember correctly, mostly with full batch size 32, 1/2 1080ti/2080ti GPUs, and --amp-opt-level 1. (There really aren't any training tricks just in case you are wondering.)

I would also suggest checking the previous related issues:

https://github.com/kenziyuliu/MS-G3D/issues/12
https://github.com/kenziyuliu/MS-G3D/issues/14  (also has my config log for NTU120 XSub joint)

Hope this helps. Please feel free to comment below for further questions.


Stackage LTS-9

Any plan to push the package to stackage in a near future ?
https://github.com/begriffs/postgrest/issues/944
Cheers,

Alright, I guess it won't happen unless critbit is on stackage ;-)

I wouldn't be opposed to it,  but this package is still in a pretty rough state.   I'm aware of some API bugs that I need to fix for 0.1 for example.

If you'd like to take responsibility for configurator-ng on stackage,  you have my blessing.  There are several other packages of mine on stackage, but I'm not responsible for any of them.

#9 would put the package closer to a state to be included with stackage.


⚠ Bofrost.de has degraded performance

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

HTTP code: 200
Response time: 1176 ms

Resolved: Bofrost.de performance has improved in 6117337 after 7 minutes.


Differentiate between Twitter Blue and Twitter Blue accounts paid for by Musk

Since it was revealed that Elon paid for a handful of celebrities Twitter Blue accounts, is there a way to differentiate or hide the badge for them?
So far it's Lebron James, Stephen King, and William Shatner.
See: https://www.theverge.com/2023/4/20/23691831/twitter-blue-verified-celebrity-lebron-james-stephen-king

Elon is saying those are the only three.

It doesn't seem possible to differentiate them via the API response, would have to be hardcoded, not sure if that's worth doing.

There are now a whole bunch of these as of tonight:

https://twitter.com/sanjanacurtis/status/1649906198076968960
https://twitter.com/nberlat/status/1649911374506590216
https://twitter.com/ddale8/status/1649902084488142850
https://twitter.com/MattBinder/status/1649884329240141828
https://twitter.com/OwenJones84/status/1649899605289566222
https://twitter.com/McJesse/status/1649909816209580033
https://twitter.com/hasanthehun/status/1649897908056227840
https://twitter.com/pattonoswalt/status/1649913791445106688

I'm stopping there for now, but I'm sure there'll be more if I keep scrolling

Not sure how different this would be to an API but you could just get them from:
https://gist.github.com/travisbrown/b50d6745298cccd6b1f4697e4ec22103

There is already a project that brings back the legacy verification and also differentiates it from those who have paid for Twitter blue. It is now available on Firefox, and for Chrome, it is still under review
https://github.com/luiserdef/twitter-real-verified

Is this not fixed? I see that LinusTechTips, who Musk gave a Paid checkmark to, now says Verified instead, like it should.

This may help: https://twitter.com/titterdaily/status/1662753923478765571

There is already a project that brings back the legacy verification and also differentiates it from those who have paid for Twitter blue. It is now available on Firefox, and for Chrome, it is still under review
luiserdef/twitter-real-verified

Thanks, I switched to using this instead, and it's been working pretty well for me.


Added force back to travis.yml file

This fixes a CI failure that travis was having.

@miq-bot housekeeping
@miq-bot euwe/no

@miq-bot add_label housekeeping
@miq-bot add_label euwe/no


Support for Date Time API types in SQL module

I created JSR 310 (Date Time API) support in sql module. Still the problem is in sql module build.
[INFO] --- animal-sniffer-maven-plugin:1.13:check (ensure-java-1.6-class-library) @ querydsl-sql ---

All new api classes will not be seen so I'm unable to build module on JDK 8.
Please continue from here or let me know what to fix.

@timowest there are actually two solutions to this.

move this out, so we can make only that build on jdk8
add a JSR310-compatible library to the classpath, so the packages are known and we can compile against that.

@arturchyzy thanks at least for the effort, I will fix the animal sniffer 'problem'.

I'd maybe at first try the compatibility library approach, because there are only a few classes involved.

You think more of a separate library or new module ?

I meant that the JSR 310 types would be included in querydsl-sql and the dependencies for the JDK 7 build would be provided by a compatibility library.

ThreeTen is however published under a different package name, so unfortunately it doesn't work that well..

What we could do, is via a maven profile:
with jdk8, we have another plugin that applies a patch to the imports of these classes.
The source references the backport's package structure, and for compatibility's sake we use that as reference what (if running jdk8) is available at runtime.
This would mean an additional querydsl-sql artifact with jdk8 classifier, so I don't know how you feel about this?

I'd feel uncomfortable if we touch the sources. If we don't have a proper compatibility layer we probably need to have a separate module for the JSR 310 types. querydsl-sql-jsr310?

Indeed.
I found one last thing, but it is rather.. weird.
Apparently, someone took ThreeTen-bp and forked it, to publish it under the java.time package.
This is not really a solution, since we can't conditionally check if the java.time.* classes come from the standard API or from that artifact.
In essence, I can't find a viable alternative, so a seperate module would be best.

I pushed some fixes and modification of data conversion (with set tests for added types). Please carefully take a look at them as I see those conversion are little bit tricky. I hope I did it well. Hope this issue will be resolved soon.

Alternatively we can make JDK 1.8 a build requirement for Querydsl. Excluding querydsl-sql-jsr310 via a profile trick might be a bit messy.

Yes, that is actually fine by me.
Since we strive and check for runtime compatibility, we shouldn't run into problems.

I am reviewing this currently, and want to apply some fixes, is that okay?
For example this method will never work.

Just wanted to let you know that your changes has been merged. What's left to merge it to master ?

We still need to update our build matrix.
If we were to merge it to master, none of our CI builds would compile, since it requires JDK8.
So @timowest shall we update travis.yml in this PR or a separate one?

@Shredder121 It can be updated in this PR.

I will do so shortly.

I think it is a good idea to add a working test case, to test whether or not my DateTimeFormatter fix is any good.

@timowest @arturchyzy I have added a few tests, and will push them.
There is however one problem with the JSR310ZonedDateTimeType.
There is no way to know what time zone was originally used, we can by default set it to UTC, but that is about it, and it is feels counterintuitive to the syntax.
ZonedDateTime zonedDT = ...;
ZonedDateTime result = query().singleResult(Expressions.constant(zonedDT));
assertEquals(zonedDT, result);//<- fails, since TimeZone information could not be reconstructed.

Furthermore, it feels as if they made some mistake, Instants feel practically useless.
I get it that they can't really be queried (day of week, etc), but all code relies on the querying model.
If you were to create a LocalDateTime out of it, the LocalDate part cannot be queried.
Instant instant = ...;
LocalDateTime test = LocalDateTime.from(instant);// <- fails

After all of this I can say it is tricky to get working.

@Shredder121 If you want to save timezone I think you should use Types.TIMESTAMP_WIITH_TIMEZIME (available from Java 8) instead of Types.TIMESTAMP. But I feel it's not a common case to use it with timezone or limit use of ZoneDateTime to specific database usage. Joda-Time's DateTime also contains timezone and conversion was made to UTC so solution is compatible with Joda solution.
About Instant - that's true. Instant is not a format to convert from, it's more like one to convert to. There are also  .of* methods which seems more like one which should be use when creating new instances.
Please let me know if you need anything about this issue (writing tests, checking). Do you plan to push it to main repo ? Do you also plan to merge this request or work on your personal branch ? Anyway please let me know when I should close it.

I (only) just pushed a few new commits, I think that writing tests would be very good indeed.
Also, I need people from different timezones, so it would be helpful to have a few people.
And I am not quite sure with what you meant with TIMESTAMP_WITH_TIMEZONE.
I think we can open up a pull request on our end? We can take the conversation there, this makes it a little easier to fix up some commits, and make the PR merge-able.
@timowest what is your opinion? do you agree?

@Shredder121 I am fine with that.

@Shredder121 Check TIMESTAMP_WITH_TIMEZONE - introduced with java 8, previous versions of java had only TIMESTAMP. Please be aware that there is also TIME_WITH_TIMEZONE starting from Java 8

I indeed found that already, but I meant that I don't quite see the relation between that type code and getting the timezone information from the resultset.
I think we'll have to make a test case with a column with timezone information and work from that.

Closing in favor of https://github.com/querydsl/querydsl/issues/1399


AVRO-3240: fix deserializer schema backward compatibility

When providing your own schema to from_avro_datum,
the deserialization is not backward compatible with messages
containing a previous schema even if the schemas are created
to be backward compatible.
This is due to the decode_variable function in utils returning
Error::ReadVariableIntegerBytes when the reader object is
smaller than expected and thus cannot fill the read_exact buffer.
Reading a message generated with an older schema version than the
one we are statically using, the payload buffer is by essence
smaller than the expected payload from a message serialized with
a newer schema (backward compatible schemas are basically append
only).
The proposed fix takes that into account and just returns empty
Ok() which will be interpreted as null. This is in line with the
fact that a backward compatible schema has to allow for null
values to the newly added fields.
Make sure you have checked all steps below.
Jira

[x] AVRO-3240

Tests

[x] I have implemented a test to demonstrate the problem

Sorry for the late reply @martin-g I took some time off, now back to business!
I pushed the corrections you asked for.

I've checked out you PR locally but I am not able to push to your branch.
I am not sure whether it is just because I don't do something right or it is ASF policy...
Anyway, I've fixed the formatting and now I will have to squash all commits for this PR into one and then push it to master.
The problem is that this way you won't appear in the commit log. All your work will be credited to me... :-/
Any concerns ?

Actually, I could merge the PR and then fix the formatting in a follow up commit!

Done!
Thank you for the contribution, @ultrabug !

Thank you @martin-g :) with #1368 after this one I'll be close to being able to switch to mainstream Rust avro :+1:

Done!

I don't understand why this is required: according to the spec, the exact writer schema should be made available at deserialization, while this feature seems to be about deserializing while specifying a different "writer schema" than the data was actually written with.

@Ten0 different writer schema is actually called a reader schema. This is used for schema evolution.

Yes and when using that we normally still need to specify the actual writer schema, and reader schema is provided as a separate argument.
But this feature seems to be about deserializing using a different schema than the writer schema as writer_schema, cf test.
I can't find mention of schema evolution that is supposed to work this way in the spec.


Simulator refactorings

Refactor of main test code

Some helper structs added to track state
Add new trailer checking routine
Add extra test for upgrade+revert with failure
Misc improvements

@d3zd3z I still want to apply some changes to the no revert test but might as well open a smaller PR over this one.

Overall it looks good. I think it might make sense to make a bunch of these functions methods on the Image struct, but that's an easy change to make later.

I'm not sure I like that it now doesn't print anything, even with logging on. It'd be nice to at least have an indication that some tests have run.


TypeError when using the exporting.spring_project function

I've been trying to export my data to SPRING using the external export feature. I do all my processing in Seurat and then export a loom file to be read in scanpy and export to SPRING. I've been however getting the below error.
The notebook with the code and the loom file can be found here: https://github.com/tejas-j/seurat2spring
Is there a better way to achieve what I'm trying to do (data -> Seurat -> scanpy -> SPRING)
---------------------------------------------------------------------------
TypeError                                 Traceback (most recent call last)
<ipython-input-13-3b0044b18ade> in <module>
      1 import time
      2 t0 = time.time()
----> 3 sce.exporting.spring_project(data, './pbmc3k', 'draw_graph', subplot_name='force1', overwrite=True)
      4 print(time.time() - t0)

~/miniconda2/envs/py36/lib/python3.6/site-packages/scanpy/_exporting.py in spring_project(adata, project_dir, embedding_method, subplot_name, cell_groupings, custom_color_tracks, total_counts_key, overwrite)
    157     # Write continuous colors
    158     continuous_extras['Uniform'] = np.zeros(E.shape[0])
--> 159     write_color_tracks(continuous_extras, subplot_dir / 'color_data_gene_sets.csv')
    160
    161     # Create and write a dictionary of color profiles to be used by the visualizer

~/miniconda2/envs/py36/lib/python3.6/site-packages/scanpy/_exporting.py in write_color_tracks(ctracks, fname)
    301     out = []
    302     for name,score in ctracks.items():
--> 303         line = name + ',' + ','.join(['%.3f' %x for x in score])
    304         out += [line]
    305     out = sorted(out,key=lambda x: x.split(',')[0])

~/miniconda2/envs/py36/lib/python3.6/site-packages/scanpy/_exporting.py in <listcomp>(.0)
    301     out = []
    302     for name,score in ctracks.items():
--> 303         line = name + ',' + ','.join(['%.3f' %x for x in score])
    304         out += [line]
    305     out = sorted(out,key=lambda x: x.split(',')[0])

TypeError: must be real number, not numpy.str_

Hi @swolock, any ideas?

@calebweinreb any ideas on how to fix this issue?

I think the spring export function currently fails because it only checks whether each column in adata.obs is a pandas categorical variable (not is_categorical(adata.obs[obs_name])) and, if not, assumes it's a continuous variable and then tries to join a str with an integer.
If you look at your file data.obs contains a number of categorical variables that are currently numpy objects
data.obs.dtypes
ClusterID             int32
ClusterName          object
RNA_snn_res_0_5      object
nCount_RNA          float32
nFeature_RNA          int32
orig_ident           object
percent_mt          float32
seurat_clusters      object
louvain            category
dtype: object

As a quick fix, I think you can do something like this:
adata = data.copy()
obj_cols = adata.obs.columns[adata.obs.dtypes == np.object]
adata.obs[obj_cols] = adata.obs[obj_cols].astype('category')
sce.exporting.spring_project(adata, './pbmc3k', 'draw_graph', subplot_name='force1', overwrite=True)

Not sure what's the best way to fix it for the future: check for other dtypes or uses f-strings to avoid the str concatenation errors?

doesn't sanitize_anndata() do exactly that @flying-sheep? Could just add a call to that before exporting to SPRING?


Schema#toString() causes NPE

Using Flyway 6.3.0 community edition against postgres:9.6-alpine Docker image, the following snippet:
Flyway
        .configure()
        .locations("classpath:/flyway")
        .dataSource(dataSource)
        .baselineOnMigrate(true)
        .baselineVersion("000")
        .schemas("foo")
        .load()
        .migrate();

causes this NPE:
Caused by: java.lang.NullPointerException
	at org.flywaydb.core.internal.util.StringUtils.replaceAll(StringUtils.java:154)
	at org.flywaydb.core.internal.database.postgresql.PostgreSQLDatabase.pgQuote(PostgreSQLDatabase.java:131)
	at org.flywaydb.core.internal.database.postgresql.PostgreSQLDatabase.doQuote(PostgreSQLDatabase.java:127)
	at org.flywaydb.core.internal.database.base.Database.quote(Database.java:280)
	at org.flywaydb.core.internal.database.base.Schema.toString(Schema.java:267)
	at java.lang.String.valueOf(String.java:2994)
	at java.lang.StringBuilder.append(StringBuilder.java:131)
	at org.flywaydb.core.internal.command.DbSchemas$1.call(DbSchemas.java:85)
	at org.flywaydb.core.internal.command.DbSchemas$1.call(DbSchemas.java:79)
	at org.flywaydb.core.internal.jdbc.TransactionalExecutionTemplate.execute(TransactionalExecutionTemplate.java:66)
	at org.flywaydb.core.internal.command.DbSchemas.create(DbSchemas.java:79)
	at org.flywaydb.core.Flyway$1.execute(Flyway.java:187)
	at org.flywaydb.core.Flyway$1.execute(Flyway.java:153)
	at org.flywaydb.core.Flyway.execute(Flyway.java:523)
	at org.flywaydb.core.Flyway.migrate(Flyway.java:153)

The host is a Xubuntu 18.04.4 LTS box running AdoptOpenJDK (build 1.8.0_242-b08).

I'm not able to reproduce this. Do you have a logging framework (eg. logback, log4j) available to do a full debug-level log which might throw more light on it?

Thanks for taking time to check the issue @juliahayward. Due to Corona, I can barely spare some extra computer time next to my day job halved by babysitting sessions. Hence, I could not bisect in the code base to spot the state yielding the error. Though what I can comment on is, an Object#toString() method should not throw an NPE anyway. As far as I can trace back from the stacktrace, Schema#toString() reaches out to a set of methods where the passed parameter (in this case schema, I guess) is null. What about making StringUtils.replaceAll null-proof?

As far as I can determine, the only way that Schema.toString() can NPE is if the schema name is null, and that should be impossible (as you've set the schema name in ... .schemas("foo"). If Flyway has managed to get into an invalid state then failing as soon as that comes to light has the fewest bad side effects - there's no sensible response Schema.toString() could give other than an exception of some sort.


profile dropdownBUG:

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
Profile dropdown needs to update @arghadipmanna101 assign this issue to me , I will fix it . Thankyou
Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

just created PR #614 for this issue . Thankyou

since the pr #614 is merged hence closing this issue


WebSites ResourceHealthMetadata APIs and Tests

Adding the Microsoft.Web ResourceHealthMetadata APIs as well as new test cases for these APIs

Description
Adding Microsoft.Web ResourceHealthMetadata APIs and test cases for these APIs. Used generate.cmd to generate everything except the test cases and the Microsoft.Azure.Management.Websites.csproj edit. Here is the azure-rest-api-specs pull request - https://github.com/Azure/azure-rest-api-specs/pull/2588

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] Please add REST spec PR link to the SDK PR
[ ] I have read the contribution guidelines.
[ ] The pull request does not introduce breaking changes.

General Guidelines

[ ] Title of the pull request is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

SDK Generation Guidelines

[ ] If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
[ ] The generate.cmd file for the SDK has been updated with the version of AutoRest, as well as the commitid of your swagger spec or link to the swagger spec, used to generate the code.
[ ] The *.csproj and AssemblyInfo.cs files have been updated with the new version of the SDK.

@pavelzel please create a generate.ps1 file and re-generate the code using it


KAFKA-3175 (Rebased) : topic not accessible after deletion even when delete.topic.enable is disabled

Rebased the patch with current trunk.

It seems the original PR  #846 hasn't been merged? Is this one created accidentally?

closing this. will rebase with the original PR : https://github.com/apache/kafka/pull/846


Some questions about the .pth file in project_feature.py

Thank you very much for your work! I encountered some issues while generating pseudo masks:

Could you please let me know how to obtain the .pth file in project_feature.py? (lines 157-160). It seems the output of data_prepare_ScanNet.py are files end with .ply.
https://github.com/SooLab/Part2Object/blob/65d728edecdb461bf6fd88c173996874ae862c45/pseudo_mask_gen/project_feature.py#L156C1-L160C92
Does this work use the complete version of ScanNet v2(1.5T) or the scannet_frames_25k(≈6G) version?

Thanks again for your hard work and support!

Meanwhile, these .pth files also seem to be applied in the downstream files get_dis_matrix.py , scene_frame_ncut.py etc.
Also, in get_dis_matrix.py, it requires the input of init_segments, is it the output of initial superpoints produced by initialSP_prepare_ScanNet.py? However, it seems to come with the postfix _superpoint.npy instead of .pth.
https://github.com/SooLab/Part2Object/blob/65d728edecdb461bf6fd88c173996874ae862c45/pseudo_mask_gen/get_dis_matrix.py#L31-L39
Please correct me if I am wrong; thank you for your reply.

Thank you for your timely reply! It indeed helps to produce the .pth file under train/val folder. However, I still have the problem about getting the .pth file under the init_segments folder just as described previously:

Also, in get_dis_matrix.py, it requires the input of init_segments, is it the output of initial superpoints produced by initialSP_prepare_ScanNet.py? However, it seems to come with the postfix _superpoint.npy instead of .pth. https://github.com/SooLab/Part2Object/blob/65d728edecdb461bf6fd88c173996874ae862c45/pseudo_mask_gen/get_dis_matrix.py#L31-L39

These files are used in get_dis_matrix.py:
https://github.com/SooLab/Part2Object/blob/65d728edecdb461bf6fd88c173996874ae862c45/pseudo_mask_gen/get_dis_matrix.py#L38-L39
Thank again for your timely reply! Also, it will be of great help if you can take a look at #7 , I still face the problem of the dimension of the dino output tensor to run project_features.py.

I also find out that the scene_frame_ncut.py and scene_frame_merge.py requires the variables png and mask_path under the outputs folder, is it also generated by SAM3D? How can I get them, thank you!
https://github.com/SooLab/Part2Object/blob/65d728edecdb461bf6fd88c173996874ae862c45/pseudo_mask_gen/get bbox prior/scene_frame_ncut.py#L138
https://github.com/SooLab/Part2Object/blob/65d728edecdb461bf6fd88c173996874ae862c45/pseudo_mask_gen/get bbox prior/scene_frame_ncut.py#L145-L149

In the data preprocessing part, we follow SAM3D and Mask3D to convert the point cloud data (.ply) into a tensor form (.pth /.npy) for ease of use. You can follow SAM3D to get the data in the form of.pth

For faster reading and less storage, we changed .pth to .npy format. Sorry that we did not synchronize the modification in the subsequent files due to our negligence. You only need to modify .pth into _superpoint.npy format.

Thank you for your timely reply! It indeed helps to produce the .pth file under train/val folder. However, I still have the problem about getting the .pth file under the init_segments folder just as described previously:

Also, in get_dis_matrix.py, it requires the input of init_segments, is it the output of initial superpoints produced by initialSP_prepare_ScanNet.py? However, it seems to come with the postfix _superpoint.npy instead of .pth. https://github.com/SooLab/Part2Object/blob/65d728edecdb461bf6fd88c173996874ae862c45/pseudo_mask_gen/get_dis_matrix.py#L31-L39

These files are used in get_dis_matrix.py:
https://github.com/SooLab/Part2Object/blob/65d728edecdb461bf6fd88c173996874ae862c45/pseudo_mask_gen/get_dis_matrix.py#L38-L39
Thank again for your timely reply! Also, it will be of great help if you can take a look at #7 , I still face the problem of the dimension of the dino output tensor to run project_features.py.

For faster reading and less storage, we changed .pth to .npy format. Sorry that we did not synchronize the modification in the subsequent files due to our negligence. You only need to modify .pth into _superpoint.npy format.

I also find out that the scene_frame_ncut.py and scene_frame_merge.py requires the variables png and mask_path under the outputs folder, is it also generated by SAM3D? How can I get them, thank you!
https://github.com/SooLab/Part2Object/blob/65d728edecdb461bf6fd88c173996874ae862c45/pseudo_mask_gen/get bbox prior/scene_frame_ncut.py#L138
https://github.com/SooLab/Part2Object/blob/65d728edecdb461bf6fd88c173996874ae862c45/pseudo_mask_gen/get bbox prior/scene_frame_ncut.py#L145-L149

For 2D mask acquisition, referring to our paper, the use of SAM is not allowed in the unsupervised setting. We follow cutler, it is an unsupervised image segmentation algorithm.

I also find out that the scene_frame_ncut.py and scene_frame_merge.py requires the variables png and mask_path under the outputs folder, is it also generated by SAM3D? How can I get them, thank you!
https://github.com/SooLab/Part2Object/blob/65d728edecdb461bf6fd88c173996874ae862c45/pseudo_mask_gen/get bbox prior/scene_frame_ncut.py#L138
https://github.com/SooLab/Part2Object/blob/65d728edecdb461bf6fd88c173996874ae862c45/pseudo_mask_gen/get bbox prior/scene_frame_ncut.py#L145-L149

For 2D mask acquisition, referring to our paper, the use of SAM is not allowed in the unsupervised setting. We follow cutler, it is an unsupervised image segmentation algorithm.

Thank you for your reply! I will try this.


meaningful messages on files not existing

Summary:
Provide meaningful messages on exit when files are missing.
Description:
When files are missing, produce reasonable messages. The current behavior is to allow the var_context dump reader to fail.
The behavior should be fixed for the data and init files.
This should be fixed in the validation of the arguments. This needs to wait for stan-dev/math#1751.
We should also add a test for this.
Current Output:
> ./examples/bernoulli/bernoulli sample data file=foo.data.R

Exception: variable does not exist; processing stage=data initialization; variable name=N; base type=int
Diagnostic information:
Dynamic exception type: std::runtime_error
std::exception::what: variable does not exist; processing stage=data initialization; variable name=N; base type=int

Expected Output:
>  ./examples/bernoulli/bernoulli sample data file=foo.data.R

Can't open specified data file, "foo.data.R"

Current Version:
v2.12.0

This has been fixed sometime in between. Cmdstan outputs Can't open specified file, "foo.data.R"


Support diagnostics for integrations and devices

Diagnostics for integrations and devices is a new HA feature from HA 2022.2.

https://github.com/toreamun/amshan-homeassistant/releases/tag/2022.2.5-beta


Ruby 3.1.4 and bundle update

We can't switch to Ruby 3.2 while we're on Rails 6, but it seems like a good idea to keep it updated.

coverage: 94.312%. remained the same when pulling 35f0230c1e898a7348d22de73e046a64bbd7c2fe on nimmo-ruby-3-1-4 into 3e7c8404aca30200f7fb5beed91b63cf3d87be1f on main.

Ugh.  Trying to upgrade to 3.1.4 broke my world.. Can't even get things to work going back to 3.1.2.  I'll need to poke at it in the morning after I sleep.

Was thinking about this. I wonder if what you need to do is bundle update on your machine.
I noticed that our gemfile.lock has hardware-platform-specific versions of a few gems, and if they were missing…?
Sorry, the whole update was super smooth for me. I just changed ruby-version and bundle-update and it worked.

On Oct 3, 2023, at 6:40 PM, Nathan Wilson @.***> wrote:
Ugh. Trying to upgrade to 3.1.4 broke my world.. Can't even get things to work going back to 3.1.2. I'll need to poke at it in the morning after I sleep.
—
Reply to this email directly, view it on GitHub https://github.com/MushroomObserver/mushroom-observer/pull/1655#issuecomment-1745996606, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAO3TP7LEOTD67IXSEPHMR3X5S5ANAVCNFSM6AAAAAA5ORTDQOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONBVHE4TMNRQGY.
You are receiving this because you modified the open/close state.

I think I got it sorted and I'm not on MacOS Ventura and fully brewed up.  All the tests are passing both on main and on my branch.  I had to wrestle a bit with the mysql2 gem, but I think I finally won.  There's a minor tweak that needs to go in the Gemfile.lock at some point, but I have it on my branch so I think I'll just wait for that to merge.

This PR did not get pushed to production so I was surprised when I found that 3.1.4 wasn't installed there.  For the moment I update the .ruby-version on production to stick at 3.1.2.

Doing the bundle install for 3.1.4....

Ok, 3.1.4 is installed on production and production is flipped over to it.

Thanks Nathan. On Oct 5, 2023, at 4:38 PM, Nathan Wilson @.***> wrote:
Ok, 3.1.4 is installed on production and production is flipped over to it.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you modified the open/close state.Message ID: @.***>


Feature request: Provide alternative authorization strategies

I was considering authorization issues raised on #746 and after a I think that handling authorization based on o entities instead of endpoints can be an inconvenient issue, specially when dealing with plugins.
POC scenario
I set up the getting started app with movies table and seeded it.
After that the authorization was configured with the following input:
"authorization": {
    "adminSecret": "easy",
    "rules": [
      { "role": "platformatic-admin",
        "find": false,
        "save": true,
        "delete": true,
        "entity": "movie"
      }
    ]
  }

When a GET request was sent to /movies the app replied with unauthorized, as expected.
But when a request was sent to be handled by a plugin that had app.platformatic.entities.movies.find  it responded with the movies array (which I found quite odd considering this part of the docs).
Thinking about the alternatives I came up with the idea of providing another way of authorizing a request, that regards not the entity, but the endpoint used. Something like this:
{
 "rules": [{
    "endpoint": "/plugin",
    "role": "customRole",
    "find": true,
    "save": true,
    "delete": true
 }]
}

But when a request was sent to be handled by a plugin that had app.platformatic.entities.movies.find it responded with the movies array (which I found quite odd considering this part of the docs).

Could you include a reproduction script for this?

What you need for custom plugins is https://github.com/platformatic/platformatic/issues/668. It's on our radar.

But when a request was sent to be handled by a plugin that had app.platformatic.entities.movies.find it responded with the movies array (which I found quite odd considering this part of the docs).

Could you include a reproduction script for this?

Sure! Here's the repo: https://github.com/luizgribeiro/platformatic-auth-plugin
These were the requests made:
This one fails as expected (request directly made to movies entity)
curl -X 'GET' \
  'http://localhost:3042/movies/?totalCount=false&fields=title' \
  -H 'accept: application/json' \
-H 'X-PLATFORMATIC-ADMIN-SECRET: easy'

This one works, but it also deals with the the movies entity
curl -X 'GET' \
  'http://localhost:3042/' \
  -H 'accept: application/json' \
-H 'X-PLATFORMATIC-ADMIN-SECRET: easy' | jq

Regarding the authorization configs, I think I didn't give enough details on the hole idea behind it, but I can work on something to express how it would/should work.
I've been working on a suite of authorization mechanisms for my employer that are both role based and, if more granular permission is needed, we use attribute based alternatives.
In terms of DX it would be possible to:

Keep it backwards compatible with the current strategy
Provide fine grained access control out of the box
Use a single "source of truth" (on platformatic.de.json) for authorization

Here's an idea of how the authorization structure would look like:
{
"rules": [
    { //entity maps to all endpoints auto generated by platformatic
       entity: "movies",
      "role": "customRole",
      "find": true,
      "save": true,
      "delete": true
   },
  { //endpoint based, using roles
       endpoint: "/customEndpoint1",
      "role": "customRole",
      "find": true,
      "save": true,
      "delete": true
  },

  { //endpoint based, using scopes and custom authorizer (it gets metadata from the auth rule and checks user infos in order to allow or deny)
       endpoint: "/customEndpoint1",
      "scopes": ["movies.title", "actors.name"],
      "authorizerPath": "./jwtScopesAuthorizer",
      "find": true,
      "save": true,
      "delete": true
    }
  ]
}

Sure! Here's the repo: https://github.com/luizgribeiro/platformatic-auth-plugin

You are not passing in the request context ctx to the mapper function. Therefore it cannot know about the current request user.
You can get it via const ctx = req.platformaticContext.
This was implemented in https://github.com/platformatic/platformatic/pull/697 and likely should have been documented within authorization ad well.
Would you like to send a PR to improve the docs?

Would you like to send a PR to improve the docs?

Here it is

I think I might be a bit annoying at this point (if so, let me know please).
But the point of checking at entity level for permission seems a bit odd to me.
Have o look at this exemple of a plugin:
app.post('/custom', async (req, reply) => {
  const ctx = req.createPlatformaticCtx()

  await app.platformatic.entities.movies.save({/*payload*/},
    ctx
  });

  await app.platformatic.entities.actors.save({/*payload*/},
    ctx
  });
})

If a role has permission to save a movie but doesn't  have to save an actor an exception would be thrown and half of the changes that the handler should do will be commit (possibly living the application in an undesirable state).
Does it make sense?
If this permission check was made at endpoint level this would not be possible

I think I might be a bit annoying at this point (if so, let me know please).

You are actually helping us refine this. Thank you!

If a role has permission to save a movie but doesn't have to save an actor an exception would be thrown and half of the changes that the handler should do will be commit (possibly living the application in an undesirable state).
Does it make sense?

Yes! We support transactions for this cases: https://oss.platformatic.dev/docs/reference/sql-mapper/entities/transactions. Having route level permission would not (unfortunately) solve this problem because anything could cause the second query to fail.

Ultimately I think providing route level permissions would be amazing.
The first step is #697.
If you'd like to work on this and add this feature it would be amazing.

Having route level permission would not (unfortunately) solve this problem because anything could cause the second query to fail.

Yeah, distribute systems are ~a pain~ good fun! But it would make it harder to make this kind of stuff happen (I can see myself and some friends forgetting to wrap things around transactions and providing ctx to the queries).

If you'd like to work on this and add this feature it would be amazing.

Sure! I'll have a look on this PR. I'll probably need some help to understand a few things. Should I use Discord to ask those questions?
It would be great to have something about structure and behavior of this feature. Do you have something in mind?
I think I can come up with something using the current approach as base if needed

This could be a starting point: https://github.com/platformatic/platformatic/compare/main...db-authorize

I would add my two cents. When I, as a user, have a custom route, I usually have other handler logic than db queries: API calls, logging, etc. What I want is to be sure that this logic would not be executed if a caller doesn't have enough permissions. Example:
{
  handler: async () => {
    const ctx = req.createPlatformaticCtx()

    const userName = await getUserName()
    const userApiKey = await generateApiKey()

    await app.platformatic.entities.save(
      input: { name: userName, apiKey: userApiKey },
      ctx
    )
  }
}

I don't want getUserName and generateApiKey to be executed if I know that a caller doesn't have permission to save a user entity.


[BUG] esp32 pid controller + psram issue

Description / Steps to reproduce the issue
see the following test code:
#include <nuttx/sched.h>

void print_stackinfo(const char *label, const struct stackinfo_s *p) {
  printf("%s: %p: %zu %p %p\n", label, p, p->adj_stack_size, p->stack_alloc_ptr,
         p->stack_base_ptr);
}

void test(void) {
  int i;

  struct stackinfo_s s;
  nxsched_get_stackinfo(0, &s);
  for (i = 0; i < 4; i++) {
    print_stackinfo("iram", &s);
  }

  struct stackinfo_s *psram = (void *)SOC_EXTRAM_DATA_LOW;
  nxsched_get_stackinfo(0, psram);
  for (i = 0;; i++) {
    print_stackinfo("psram", psram);
    if (psram->stack_alloc_ptr == s.stack_alloc_ptr) {
      break;
    }
  }
}

run it with a configuration where:

esp32 protected mode
userland pid is 5 (ie. CONFIG_ESP32_USER_DATA_EXTMEM is not set)
psram is initialized but not registered to any nuttx system heaps. (so that user apps can use them directly)

for some reasons, it prints garbage-looking values on the first run as the following.
nsh> esp32_pid
print_stackinfo(iram): 0x3ffca290: 2000 0x3ffc9b40 0x3ffc9b70
print_stackinfo(iram): 0x3ffca290: 2000 0x3ffc9b40 0x3ffc9b70
print_stackinfo(iram): 0x3ffca290: 2000 0x3ffc9b40 0x3ffc9b70
print_stackinfo(iram): 0x3ffca290: 2000 0x3ffc9b40 0x3ffc9b70
print_stackinfo(psram): 0x3f800000:<PHONE_NUMBER> 0x5d755d51 0x3ffd9b54
print_stackinfo(psram): 0x3f800000:<PHONE_NUMBER> 0x5d755d51 0x3ffd9b54
print_stackinfo(psram): 0x3f800000:<PHONE_NUMBER> 0x5d755d51 0x3ffd9b54
print_stackinfo(psram): 0x3f800000:<PHONE_NUMBER> 0x5d755d51 0x3ffd9b54
nsh> esp32_pid
print_stackinfo(iram): 0x3ffca290: 2000 0x3ffc9b40 0x3ffc9b70
print_stackinfo(iram): 0x3ffca290: 2000 0x3ffc9b40 0x3ffc9b70
print_stackinfo(iram): 0x3ffca290: 2000 0x3ffc9b40 0x3ffc9b70
print_stackinfo(iram): 0x3ffca290: 2000 0x3ffc9b40 0x3ffc9b70
print_stackinfo(psram): 0x3f800000: 2000 0x3ffc9b40 0x3ffc9b70
nsh> esp32_pid
print_stackinfo(iram): 0x3ffca290: 2000 0x3ffc9b40 0x3ffc9b70
print_stackinfo(iram): 0x3ffca290: 2000 0x3ffc9b40 0x3ffc9b70
print_stackinfo(iram): 0x3ffca290: 2000 0x3ffc9b40 0x3ffc9b70
print_stackinfo(iram): 0x3ffca290: 2000 0x3ffc9b40 0x3ffc9b70
print_stackinfo(psram): 0x3f800000: 2000 0x3ffc9b40 0x3ffc9b70
nsh>

my understanding is that

nxsched_get_stackinfo system call (the kernel, which runs with pid 0) wrote the values to the buffer (psram)
the thread returned to the userspace. (thus switch its pid back to 5)
the userspace read the buffer immediately and got the wrong values for some reasons
for some reasons, after a while (5th iteration of the loop in the following example), it started reading the correct values.

maybe pid controller takes longer to get ready than usual?
i suspect this can explain the problem which forced us to use pid 1 for CONFIG_ESP32_USER_DATA_EXTMEM in the first place.
i wonder if there is a reasonable way to wait for the pid controller (or maybe mmu/cache? i dunno) ready after a pid switch.
On which OS does this issue occur?
[OS: Mac]
What is the version of your OS?
macos
NuttX Version
modified master
Issue Architecture
[Arch: xtensa]
Issue Area
[Area: Specific Peripheral]
Verification

[X] I have verified before submitting the report.

i wonder if there is a reasonable way to wait for the pid controller (or maybe mmu/cache? i dunno) ready after a pid switch.

@gustavonihei
@tmedicci
do you have any idea?

ESP32 PID Controller is (or should be) experimental and must not be used for production.
You can only use PID1 and 0 only. They have the same privilege, so ESP32 doesn't actually provide any protection and it is just for 'testing' the approach of protected mode.
If you actually need this, you should use ESP32-S2 or, better, ESP32-S3.

Further insights:

To be more specific, there are 8 PIDs: Privileged (0-1) and Unprivileged (2-7).
On the same CPU, you can't switch between these 2 groups.
PROCPU always starts with PID0, so it ends being forced to never run unprivileged PIDs.
To use PIDs2-7, you will have to make sure APP CPU is ALWAYS running PIDs 2-7.

IMO, I would test this as it is (experimental, PID0-1) and if necessary to use on a product, move to ESP32S3.

ESP32 PID Controller is (or should be) experimental and must not be used for production.

why?
is there a known hardware bug or something?
do you have a reference?

You can only use PID1 and 0 only. They have the same privilege, so ESP32 doesn't actually provide any protection and it is just for 'testing' the approach of protected mode.
If you actually need this, you should use ESP32-S2 or, better, ESP32-S3.
Further insights:
* To be more specific, there are 8 PIDs: Privileged (0-1) and Unprivileged (2-7).

* On the same CPU, you can't switch between these 2 groups.

why not?

* PROCPU always starts with PID0, so it ends being forced to never run unprivileged PIDs.

* To use PIDs2-7, you will have to make sure APP CPU is ALWAYS running PIDs 2-7.

IMO, I would test this as it is (experimental, PID0-1) and if necessary to use on a product, move to ESP32S3.

why?
First answer is that it is not implemented. Second is that we won't work on it past experimental. You'll be on your own if you really need it on ESP32. It is not a bug, it was not implemented.

is there a known hardware bug or something?
Not a bug, but its implementations is more suitable for AMP scenarios and/or a bare metal hypervisor approach. For regular, single kernel on multicore approach, it becomes quite hard to use it.

do you have a reference?
Datasheet. My opinion also comes from evaluating it as a Project: too big, little to gain, something only valid for ESP32 as others are different.

why not?
Ok, I oversimplified. The point is you can't simply switch PIDs. You must follow the steps on how to make it work (on datasheet). It is currently not implemented and there are some caveats on how NuttX is and what would need change to make that work. It get more complex when you throw multicore SMP in the game. Cherry on top is the IRQ control and all the changes it will require.

why?

First answer is that it is not implemented. Second is that we won't work on it past experimental. You'll be on your own if you really need it on ESP32. It is not a bug, it was not implemented.

do you mean not implemented in nuttx?
i'm interested in implementing it.
i'm not asking you to implement it. :-)

is there a known hardware bug or something?

Not a bug, but its implementations is more suitable for AMP scenarios and/or a bare metal hypervisor approach. For regular, single kernel on multicore approach, it becomes quite hard to use it.

i wanted to use it for something specific to my applications.
it can be different from generic nuttx protected model semantics.

do you have a reference?

Datasheet. My opinion also comes from evaluating it as a Project: too big, little to gain, something only valid for ESP32 as others are different.

do you mean the TRM? otherwise, can you give me an URL?

why not?

Ok, I oversimplified. The point is you can't simply switch PIDs. You must follow the steps on how to make it work (on datasheet). It is currently not implemented and there are some caveats on how NuttX is and what would need change to make that work. It get more complex when you throw multicore SMP in the game. Cherry on top is the IRQ control and all the changes it will require.

i wanted to know the steps to follow.
however, i couldn't find it in the TRM.
that's why i asked it here and there.

ESP32 TRM v5.2 chap 28.3.3

ESP32 TRM v5.2 chap 28.3.3

thank you.
isn't it basically what's already implemented in get_prev_pid/set_next_pid and exception_entry_hook/exception_exit_hook?

thank you. isn't it basically what's already implemented in get_prev_pid/set_next_pid and exception_entry_hook/exception_exit_hook?

Clearly something is missing, as it is not working outside the scope I mentioned. You should check chapter 27, as PID controller also affects memory.
Unfortunatelly, I can't be of more help than this and sorry for not pointing you to a better solution. But if I can offer one last advice is to evaluate the implications of chapter 28. By doing it we concluded the effort was too big. Good luck!


setup.py include some thing unnecessary

it's common acknowledge that package SHOULD NOT include dir like tests, examples etc.
You supposed to exclude this packages in setup.py.
like
# setup.py
from setuptools import setup, find_packages

about = {}
with open('flask_state/__about__.py') as f:
    exec(f.read(), about)
# Metadata goes in setup.cfg. These are here for GitHub's dependency graph.
setup(
    name=about['__title__'],
    version=about['__version__'],
    # Here
    packages=find_packages(exclude=("tests", "examples")),
    install_requires=[
        "Werkzeug>=0.15",
        "Jinja2>=2.10.1",
        "itsdangerous>=0.24",
        "click>=5.1",
        "Flask>=1.0",
        "SQLAlchemy>=1.2",
        "Flask-SQLAlchemy>=1.0"
    ]
)

Copy that


Set Timer w/ Microseconds?

Considering the Teensy's clock has sub-microsecond length periods, it'd be nice if the timer could be set for shorter than a millisecond. Is there any simple work-around for this?

It depends on what sleep mode you are using, 'DeepSleep' and 'Hibernate' would need an external pin trigger but 'Sleep' could use the Teenyduino's 'Interval Timer' which is not implemented through Snooze.

Okay, I'll look into using the interval timer. Any idea how snoozing
affects writes to an SD card over SPI? I saw some comments regardings
problems with Serial.println(). Any fixes you're aware of for that (aside
from waiting)?
Best,
ploderup
On Tue, Feb 20, 2018 at 5:06 PM, duff2013<EMAIL_ADDRESS>wrote:

It depends on what sleep mode you are using, 'DeepSleep' and 'Hibernate'
would need an external pin trigger but 'Sleep' could use the Teenyduino's
'Interval Timer' which is not implemented through Snooze.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/duff2013/Snooze/issues/46#issuecomment-367165922, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AWVrkb_RU2xUqKwn_GQie84eLxcjxy4Eks5tW14EgaJpZM4SM0cH
.

SD should work much quicker to work after waking from sleep mode than Serial. Nothing special should have to be done to make it work.

Is there a way to sleep at full clock speed? If not, I might just see if I
can't drop power consumption by dropping the clock frequency a little.
On Feb 21, 2018 17:26, "duff2013"<EMAIL_ADDRESS>wrote:

Actually Interval Timer won't work now that I think about it because
during 'Sleep' the bus clock is at 2MHz so the Interval Timers won't fire
at the time you set. I would look into getting external timer that has a
pin toggle you can connect to a Teensy pin.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/duff2013/Snooze/issues/46#issuecomment-367525215, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AWVrkdiY85gQY3Zfz2si3kA8YPiNyWi8ks5tXLQ1gaJpZM4SM0cH
.

There is a function in Snooze Called 'Idle' that puts the cpu into wait mode until any interrupt happens which is usually would be systick interrupt every millisecond . You can use it for spin loops where you are waiting for something. It will lower the Teensy power usage and not side effect because the cpu and bus are not reduced.


Consider exposing value_t as function rather than macro

Rust Version
rustc 1.17.0-nightly (6eb9960d3 2017-03-19)
Affected Version of clap
2.21.2
Expected Behavior Summary
Be able to get a typed value for an argument using standard functions (and thus also through local type inference).
Actual Behavior Summary
A macro must be used, which also requires explicitly stating the desired type.
Sample Implementation
pub trait TypedGet {
    fn parse<S: AsRef<str>, T: FromStr>(&self, name: S) -> Result<T, String>
        where T::Err: fmt::Display;
}

impl<'a> TypedGet for ArgMatches<'a> {
    fn parse<S: AsRef<str>, T: FromStr>(&self, name: S) -> Result<T, String>
        where T::Err: fmt::Display
    {
        let raw = self.value_of(name).ok_or("parameter not found".to_string())?;
        T::from_str(raw).map_err(|e| e.to_string())
    }
}

In this case, I used parse for its alignment with the function exposed on strings.

Interesting. I like this idea! I'll need some time to play with this idea and see if it leads to any strange edge cases or breakage, but looks pretty straight forward!

Three quick thoughts:

I'd probably make  the trait TypedValue to go along with the value_of methods
There should also be an OsStr equivilant, or we'll need to decide how this'll work with the value_of_os and value_of_lossy methods.
We'd need to also figure out multiple values (values_of and their _os and _lossy counterparts).

I've forked the repro to start looking at adding this. The macro doesn't currently support OsStr, so I'm not planning on doing that in method form. I am looking at values_of, since there is a values_t! macro today.
I have some questions about the desired return type.
Error Type
There are 3 options for the error type:

clap::Error - this is consistent with the current values_t! macro, but completely suppresses the error returned by the invoked FromStr impl. That seems suboptimal.
T::Err - this would expose the error returned by the parser, but doesn't account for the possibility of failures in clap's conversion from OsStr to &str.
String - this can pipe either kind of error back through, but is impossible to match on or otherwise handle, and it requires that T::Err: std::fmt::Display, which may not always be true.

I don't have a good answer here, especially since clap::ErrorKind doesn't have a __Hidden__ variant and therefore extending it could break existing users who depend on an exhaustive match.
Return Structure (Fail-fast)

Result<Vec<T>, __> - the method would abort on first error.
Vec<Result<T, _>> - the method would process all arguments and return the collection of successes and failures.

For the return structure, I'm leaning towards option 1: The caller can invoke values_of and map those through FromStr::from_str if they want to provide more detailed errors to the caller.

@TedDriggs thanks for taking a swing at this! Apologies for the late reply, I was travelling the past week. As for your questions, here's my thoughts:

Error Type

I would lean option 1 because we could also add an impl to resolve the error as we do with errors arising from std::fmt.

I don't have a good answer here, especially since clap::ErrorKind doesn't have a Hidden variant and therefore extending it could break existing users who depend on an exhaustive match.

There's two options.

Re-use the ErrorKind::ValueValidation or perhaps more appropriately ErrorKind::InvalidValue which is correct-ish provided the docs are updated as well.
We add the variant, being that I would unbelievably surprised if someone was actually relying on exhaustive matching here being that it would mean they're handling each of clap's error types manually. I believe this is the type of breaking change that is also in line with Rust precedents of allowing a minor breaking change that no code in the wild is using or likely to use.

In fact, doing a quick ripgrep through all the crates on crates.io and looking through Github yields none. I know this doesn't represent 100% coverage especially considering clap is made for binaries and not libs, and not all projects use Github but I still think it's telling.
Having said this, I also don't want to go this route unless all other options have worse downsides.
Technically there's a third option of waiting until 3x (which I'm actively working on as we speak, but don't have a good idea for release candidates yet. I'm planning on within the next 2 months, but life can always throw curveballs....in fact I'm typing this at about 1/8th normal speed due to a cast on my hand).

Return Structure (Fail-fast)

For the return structure, I'm leaning towards option 1: The caller can invoke values_of and map those through FromStr::from_str if they want to provide more detailed errors to the caller.

I 100% agree. 👍

Closing this in favor of the Custom Derive structopt style use which will be primary in v3


Fix test command path in nx-pulumi init template

The generated pulumi project is added to apps/ path. The test command for the generated project should also use the same path.
Reproducing

Generate new project with the nx generate @wanews/nx-pulumi:init
Run the tests => test fails (due to current working directory is invalid)

Thanks for the fix @eemelipa


visual question answering

can i use this object detection to find a solution for visual question answering, if yes, could you please explain how

With ImageAI, you can retrieve recognition data on 1000 different objects (from ImageNet1000) and detection data on 80 most common daily objects (from COCO Dataset). With this data, you can build a system that can process text/sound commands to show visual answers.


chore: Add script for copying build output to package dist directories

This will be useful for publishing via Changesets. We can remove this once we've reconfigured Rollup accordingly.

@mcansh Any clue why we'd suddenly be running out of memory in CI? I don't feel like anything has substantially changed about the build other than including the Rollup TS plugin, and I have no such issues w/ Node's default memory limit running locally.

nothing's jumping out at me, but i can take a look

@brophdawg11 Successfully tested with npx<EMAIL_ADDRESS>If you want to spin it up you'll need to force install to deal w/ peer deps (need to fix that in the version script), but should be good to go.


distances in export are written in exponential notation instead of regular notation

Hi,
When creating an export of shapes there is an optional field called shape_dist_traveled, this field does not allow exponential notation, however by default this library does use exponential notation when the value is rather small (default behaviour of .Net)
Can this be changed so that it does never use exponentation notation?
Hint : the location where this occurs is in GTFSWriter.cs in method Write(IGTFSTargetFile file, IEnumerable entities) on the following line :
data[4] = this.WriteFieldDouble("shapes", "shape_dist_traveled", entity.DistanceTravelled);
hereunder is the warning stated that you will get when exporting data with this library and validating it with the feed validator from google :
Invalid numeric value 9.49307305463114E-05. Please ensure that the number includes an explicit whole number portion (ie. use 0.5 instead of .5), that you do not use the exponential notation (ie. use 0.001 instead of 1E-3), and that it is a properly formated decimal value.
in line 7 of shapes.txt

Thanks for checking and reporting :-1:  will have a look first thing next time I work on this. Should not take too long to fix.

great!
By the way I expect that the same issue occurs with any other value that can be a double ( latitude, longitude, distance, .... )

Ah, ok, thanks... will check the spec again first before fixing.

I have a fix ready. See my fork.
I took precision 1E-9. Tune it as you see fit.


Replace Grunt with Webpack

I think that it would be nice to replace Grunt with Webpack + move project to CommonJS syntax. This should allow to:

lower down technical debt
coding will be much fun
support for Node.js 12 (developing - https://github.com/gionkunz/chartist-js/issues/1233)
What do you think?

This project is in maintenance mode and version 1 is already based on a more modern stack. Although development is also paused there until I can dedicate more time again. https://github.com/chartist-js/chartist

I think I will start all over again with version 1 and switch from jspm to webpack. I ported the whole code to ES2015 and now I'm even playing with the thought of moving it to TypeScript.

Ok, so:

In my opinion, this repo (gionkunz/chartist-js) should be archived, and big information should be visible that new official repo is chartist-js/chartist. So other guys will know to develop that 2nd repo :)
Great to hear about ES2015 etc! To be honest meanwhile I was waiting for your answer, I have started to move the current code (gionkunz/chartist) to ES2015 hehe :D If you need help, then I can try. I don't have a huge experience in TypeScript, but I think that it's a pretty cool idea. Good thing that if you would switch to Webpack, then you can do switch from ES6 to TS in parts. As Webpack loaders will take care of it.

P.S. We can move this conversation to the new repo if you want.

@marverix Yeah, the new chartist 1.0 repo is still under development and not yet ready to release. So it's still inofficial. However, we should only fix critical bugs in 0.9.x and focus on getting the new version ready. However, there's still a lot to do there. You can checkout the new repo. It's already ported to ES2015 and also some of the underlying core architecture changes are also worked on there.
Yeah, the good thing about TypeScript is that it's 100% ES2015 forward compatible or in other words, you can just run ES2015 code, without type annotations, and it works just nicely. So there's no need to a separate loader in Webpack. The TypeScript loader will be just fine.

Yeah, let's close this issue and continue there!


Adding a custom component isn't working with schema

Nuxt 3
@formkit/nuxt1.0.0-beta.11

I'm having such a headache lol I've been trying to add a multiselect since 3 days and I tried literally everything from the docs. Nothing seems to work.
What I want

adding the @vueform/multiselect component to the schema, or even better: creating a component FormkitMultiselect which has @vueform/multiselect as a child component
adding a label to this component in the same style like all other inputs (native formkit text inputs etc.)
correct value handling

What already works

having the VueMultiselect rendered with my provided options

Problems

how to add a label when using a custom component?
how to handle the data? (v-model) for some reason all values are selected (see screenshot)

I tried everything from the docs... createInput etc., but nothing worked for me.
My Code
@vueform/multiselect is provided globally via Nuxt plugin
import VueMultiselect from '@vueform/multiselect'

export default defineNuxtPlugin((nuxtApp) => {
    nuxtApp.vueApp.component("VueMultiselect", VueMultiselect)
})

const schema = ref<FormKitSchemaCondition | FormKitSchemaNode[]>([
    {
        $formkit: 'text',
        name: 'title',
        label: 'Recipe Title',
        validation: 'required',
        value: ''
    },
    {
        $cmp: 'VueMultiselect',
        props: {
            options: useRecipeBadges()
        }
    },
])

Passing schema to a wrapper component

<FormBuilder
    :schema="schema"
/>

wrapper passes it to FormKit
<FormKit type="form" @submit="handleSubmit" :submit-label="submitLabel">
    <FormKitSchema
        :schema="schema"
    />
</FormKit>

All values selected

@justin-schroeder Hey, thanks for your time. I already tried that. Unfortunately the docs don't show how to use a custom input with schema. And with that attempt I have other problems...
What's working now

label is being rendered
component is being rendered

Problems:

(select) options aren't showing (I pass them as a prop)
Typescript error
not sure how to handle data yet, but maybe I can figure this out by myself after I see the options etc...

Form.vue
const FormkitMultiselectWrapper = resolveComponent('FormkitMultiselectWrapper')
const multiselect = createInput(FormkitMultiselectWrapper)

... schema
{
        $formkit: multiselect,
        name: 'badges',
        label: 'Badges',
        value: 'spicy',
        props: {
                options: useRecipeBadges(),

        }
    },

Typescript Error
No overload matches this call.   Overload 2 of 3, '(value: FormKitSchemaCondition | FormKitSchemaNode[]): Ref<{ if: string; then: string | ... | { $el: string; attrs?: { [index: string]: FormKitAttributeValue; } | { ...; }; ... 5 more ...; meta?: FormKitSchemaMeta; } | { ...; } | { ...; } | (string | ... 3 more ... | { ...; })[]; else?: string | ... 4 more ... | (string | ... 3 more ... | { ...; })[]; } | (string | ... 3 more ... | { ...; })[]>', gave the following error.   Overload 2 of 3, '(value: FormKitSchemaCondition | FormKitSchemaNode[]): Ref<{ if: string; then: string | ... | { $el: string; attrs?: { [index: string]: FormKitAttributeValue; } | { ...; }; ... 5 more ...; meta?: FormKitSchemaMeta; } | { ...; } | { ...; } | (string | ... 3 more ... | { ...; })[]; else?: string | ... 4 more ... | (string | ... 3 more ... | { ...; })[]; } | (string | ... 3 more ... | { ...; })[]>', gave the following error.ts(2769) index.d.ts(986, 5): '$formkit' is declared here.
Can you see what I'm doing wrong? If you need more information please let me know!

How about you provide a minimal reproduction of in a repository or stackblitz and we can take a look from there.

How about you provide a minimal reproduction of in a repository or stackblitz and we can take a look from there.

I added a reproduction here
This is my first reproduction, so let me know if this helps :)
Unfortunately, the Typescript isn't showing in stackblitz. I'm not sure if I need to configure something in stackblitz or if my editor (VSCode) is showing me the Typescript error by mistake.

Thank you for the reproduction. I saw a number of issues that needed resolving, but rather than list them all out, here’s your reproduction working: https://stackblitz.com/edit/vueform-multiselect-formkit
Best of luck 👍 And if you enjoy FormKit, consider using our Pro inputs next time to help support the project 🙂

@justin-schroeder thanks for your time!


Markdown table headers unreadable when saved to HTML from markdown preview.

Markdown table headers unreadable when saved to HTML from markdown preview.
Reproduction Steps:

Create/save a markdown file containing a table e.g.

My
Table

some
value

Bring up "markdown preview" using [ctrl]+[m]
Right-click in the markdown preview pane and select "save markdown as HTML"

Expected behaviour
UI theme shouldn't affect Markdown Preview's [save as HTML]
Observed behaviour
Open the HTML file in a browser and observe the background color of the header text is dark and so is the text, making it unreadable.  Switch UI Theme away from Atom Material & repeat = problem goes away (but can't use the theme).

Atom version: 1.14.3
OS and version: Win7
Installed packages:
Markdown Packages in use
In case there are interactions with other packages:

https://atom.io/packages/markdown-preview
https://atom.io/packages/markdown-preview-plus
https://atom.io/packages/markdown-writer
https://atom.io/packages/markdown-scroll-sync

Themes in Use

UI: Atom Material
Syntax: One Dark

This is fixed in 2.0 which is available for Atom 1.17-beta users.


Assign all unassigned issues

We have a bunch of old issues that aren't assigned, We should assign them and then change the inbox tracking URL to be simply this: https://github.com/Microsoft/vscode/issues?q=is%3Aopen+is%3Aissue+no%3Aassignee
Context in https://github.com/Microsoft/vscode/issues/8753

We're not going this direction after discussions within the team.


Release 1.0.0

Time to release Kaku 1.0.0 before 19th, July :) Needs to prepare for different builds for each platform.

:+1:

:+1:

Let's go :)


CMP-5906 Add option to enable Class data sharing (CDS)

CMP-5906 Add option to enable Class data sharing (CDS)
Alternatively this could be enabled by default, what do you think?
This PR adds an option for CDS, not for AppCDS.
AppCDS is probably not worth it. Generating it at first startup slows down the startup. So it should probably be generated at install time somehow (not sure if even possible, and would take too much time). Generating it at build time in this gradle plugin would be another option (which I think is best), but that would increase app size. AppCDS would require more investigation before adding it. I think what would be ideal, is that the gradle plugin would launch the app in the background when building, and maybe run some sort of compose test to warm up code. Then exit and include the generated file in the archive. Does this make sense?

It will be great to have this feature.
@AlexeyTsvetkov, could you look at the PR?

AppCDS makes starting up Compose Desktop applications muuuuuch faster.
I tried to fiddle around to enable this without a patch but could not figure out a way.
Could this be considered again? Pretty please :)

For readers who want to enable CDS Today, here's a dirty workaround:
afterEvaluate {
    tasks.named<AbstractJLinkTask>("createRuntimeImage") {
        freeArgs.addAll("--generate-cds-archive")
        @Suppress("UNCHECKED_CAST")
        val stripNativeCommands = this::class.java.methods
            .single { it.name.startsWith("getStripNativeCommands") }
            .invoke(this) as Property<Boolean>
        stripNativeCommands.set(false)
        doLast {
            destinationDir.get().dir("bin").asFile.deleteRecursively()
        }
    }
}

Nice, I am curious what AppCDS could do for a compose app in addition to CDS.

I got AppCDS working on top of CDS. I did not measure precisely but it feels snappier.
compose.desktop {
  application {
    nativeDistributions {
      jvmArgs += "-Xlog:cds=error" // change to 'debug' to get more info
      jvmArgs += "-Xshare:auto"
      jvmArgs += "-XX:+AutoCreateSharedArchive"
      jvmArgs += "-XX:SharedArchiveFile=path/to/app-cds.jsa"
    }
  }
}

One painful thing is that you need to provide a path relative the the JVM working directory for the jsa file.

I got AppCDS working on top of CDS.

I just gave it a try, and it seems to generate the app-cds.jsa as expected. However, the first startup now takes about 30 seconds, so that is pretty bad. I guess it would be better to somehow generate this file in the gradle plugin automatically and include it at build time.

Hi @igordmn, could you please review this or assign it to the correct person?


Redirecting to authentication page

Hello,
I'm getting the Navigation problem in my internal project, when I click into a button then page is navigated to another page which require the authentication info.
Is there any way to pass the authentication info when user interacts with elements?

@ducthanh you can pass the username & password as part of the URL if you are doing a visit(Page) call. This works great in all modern browsers.
<EMAIL_ADDRESS>I would advise that you pass any special characters in HTML code form

as part of the navigation process you can, have function on the page that does authenticate, if you need to populate username password ....

I'm going to close this. It's a unique situation and it's been several years. If you do still need this, we can re-open and investigate options.


Add link to contract addresses

Updating README to link to the contract addresses

Coverage remained the same at 91.913% when pulling 5542416ee339cfb97fa24bdb6a8bbd3677518406 on jrhea-patch-1 into a6cb960896301b7562ced70a8b221f3cc964ea0a on main.


There is no possibility to change item`s spacing

There is no possibility to change item`s spacing. You should make this editable.

You mean this: https://github.com/leocavalcante/page_view_indicator#changing-the-space-bettwen-the-indicators ?


Idea: "safe mode" tab

Ability to open a "safe-mode" tab with more restricted security policies, eg no javascript, or no third-party domain requests.
Use-case: diagnostically exploring a site that you don't trust. It might be good for "safe browsing" too, and could have similar effects to ad-blockers.
Additional idea: Maybe when you open the safe-mode tab, the tab goes to a start page where you configure how restrictive the policies will be.

Maybe for the slider, it can have the same levels as Tor has: https://en.wikipedia.org/wiki/Tor_(anonymity_network)#Levels_of_security


fix for coverage reports w/ absolute file path

fix coverage report if clover uses absolute path
fix compatibility issue with pylint 1.8.0 (released 12.15.2017) as it writes a specific message to stderr (there's no command line switch to turn it off)
ref: https://github.com/PyCQA/pylint/pull/1522

Coverage increased (+0.0007%) to 99.095% when pulling d2930c6329ca7e4c7ed13307ebc82d9b2819e9e2 on peterg79:master into eee923940bb537f8940aea9815fb69e634e75a1d on Bachmann1234:master.

Kk. I'll.merge this now and get a release asap. Maybe tonight or tomorrow.

I could not figure out a way to run pylint in quiet mode; it seems like this option is not exposed.

Released! https://pypi.python.org/pypi/diff_cover/1.0.2


Style edit. Fix formatting, typos, usage.

Codecov Report

Merging #190 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #190   +/-   ##
=======================================
  Coverage   50.36%   50.36%
=======================================
  Files          93       93
  Lines        4684     4684
=======================================
  Hits         2359     2359
  Misses       2325     2325

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 da77647...8d3570f. Read the comment docs.

LGTM


Commandline argument split-pane subcommand sometimes doesn't work when preceded by a focus-tab subcommand

Environment
Windows build number: Version 10.0.18362.752
Windows Terminal version (if applicable): 0.10.781.0

Steps to reproduce
Create a shortcut with this target: %LOCALAPPDATA%\Microsoft\WindowsApps\wt.exe ; new-tab ; focus-tab -t 0 ; split-pane. Repeatedly open and close the terminal using this shortcut.
Expected behavior
The terminal should open with two tabs, the first tab should be focused and split in two.
Actual behavior
The split-pane often doesn't do anything. The terminal just opens with two tabs and the first tab focused, but no split pane visible. This doesn't always happen. If it happens I can close the terminal and open the shortcut again and it will eventually work.

This sounds like a /dupe of #4430, which is fixed for 0.11


Expose set_uid()

Exposes set_uid() method. Given the exposed methods in ResourceUID singleton, exposing this method too is only logical and has some valid use-cases (like https://github.com/godotengine/godot/pull/87706#issuecomment-1915441490).

See also https://github.com/godotengine/godot/pull/88111


Correct windows build flags for clang-cl/msvc-cl under opt/fastbuild/dbg

Commit Message:  Clean up build flags for clang + msvc opt/fastbuild/dbg
Additional Description:

Move what were '--config=msvc-cl' settings out of .bazelrc into the
default cflags for Windows compilation. This enables bazel build ...
and bazel test ... to simply work out of the box.

Cleans up .bazelrc lists of windows vs. clang-cl settings, dividing
the list into desired toggles vs. bazel or envoy bug workarounds

Fix errors in curl library creation in fastbuild on Windows

Introduce toggles and defaults for alwayslink argument to library objects.
Defaults remain the same for now.

Introduce, but do not toggle clang-cl flags (this will arrive in a
later PR when we resolve the opt build errors missing intrinsic base
class destructors in the mock classes)

Risk Level: low
Testing: local, msvc and clang-cl on windows
Docs Changes: n/a
Release Notes: n/a

@envoyproxy/windows-dev note the resolution to Nick and Randy's observations about omitting -config msvc-cl, this should now work.

/retest

/retest

@envoyproxy/windows-dev for your inspection, this looks ready to run better msvc-cl and new clang-cl pipelines, and defaults should not be sensible.

@htuch Just FYI that this has progressed r.e. https://github.com/envoyproxy/envoy/issues/11974
It may be unwise to simply drop msvc-cl from the matrix, because that compiler is giving us additional insight into mistaken assumptions about C++ inherited from gcc/clang, but we'll zero in on one-or-the-other as "official binaries" coming from the project.

@wrowe great, I think this will pay off with our Chromium interop and other OSS libs, thanks, seems awesome progress.

This patch has been greatly simplified, it adds the minimal support for introducing some new features in future patches (such as exposing linkalways flags for potential overrides) and relocates a number of flags without changing the behaviors significantly.
It should continue to permit building fastbuild out-of-the-box by default without invoking ci/windows_build_steps.sh, but it will no longer introduce release 'opt' build debug .pdb's on Windows due to the memory constraints of the GCP RBE environment. We'll address that in a later patch in sync with changes to the GCP worker pool, and wait to introduce clang-cl build pipeline until those opt build bugs are sorted out.

Note, this PR is a https://github.com/envoyproxy/envoy/milestone/16 dependency

@lizan could you give this a final pass so we can move on to the clang-cl pipeline PR which depends on these updates?


Investigate potential bug in rmw API

rmw_shutdown() is invoked by rcl before rmw_destroy_node(). See https://github.com/ros2/rmw_zenoh/blob/85698981dafe966f18b83a525875436c8443476a/rmw_zenoh_cpp/src/rmw_init.cpp#L372-L375

This is by design; see #92.  Closing this one out.


[feature] [question] disable internal state updates

I would like to use the onEnd event to manage my own state, and then pass the new children back into the sortable object.  I was just wondering if there is a way to prevent onEnd to change anything with the children.  I would like to manually manage that, however it seems like my management and the sortable are both trying to update the children at the same time.  I am trying to use this to create my own react component because the react-sortablejs has some issues that I am trying to work around.

This library is designed extremely close to the DOM (closer than I'd like it to).
The way you want to do it isn't possible from what I know.
We'll probably try this in version 2 of Sortable, if that day ever comes.


QtRVSim: 0.9.3 -> 0.9.4

Description of changes
Bump to a new release.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)
[x] Fits CONTRIBUTING.md.

nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD"
1 package built:
qtrvsim

@ofborg build qtrvsim


Adding unit tests for tanh activation

Awesome package Brad! Please consider these basic unit tests for the tanh activation.

Thanks @jsupanova ! @Chronocook will ultimately review.
Can you do me a favor? Since we don't have a package set up yet, can you create a directory called tests/ and put this in there? Also can you comment on this PR what command we should run to execute the tests?


updates to fix deploy-manual action

Description of the change:
Motivation for the change:
Checklist
If the pull request includes user-facing changes, extra documentation is required:

[ ] Add a new changelog fragment in changelog/fragments (see changelog/fragments/00-template.yaml)
[ ] Add or update relevant sections of the docs website in website/content/en/docs

/lgtm


Parse date to remove the year

To keep dates valid, the format which is used is YYYY-MM-DD. A function should be written to return the date as a local date string without the year.
Function to use: Date.prototype.toLocaleDateString().

An other way would be returning an object such as the argument in this example:
console.log(zodiac.getSignByDate({ day: 22, month: 6 }));

UPDATING THIS WILL BREAK ACTUAL CODE.


Request for macOS Compatibility and Optional Dependency: Remove Conda Package nnops

I wonder if it is possible to create a version of the "endstate correction" repository that does not depend on the conda package nnops. Currently, nnops only offers a Linux CUDA distribution and lacks support for macOS distribution.
Our use case involves integrating the "endstate correction" repository into our software stack. Many users intend to utilize our tool on their macOS laptops for post-simulation analysis and simple system setup. However, if we integrate "endstate correction" and its dependency nnops into our software stack, it will render our tool unusable on macOS.
Ideally, the implementation in "endstate correction" could dynamically switch between using nnops (if available) and falling back to a CPU implementation when nnops is absent. Notably, it appears that other components such as openmm-torch, torchani, and openmm-ml already support the macOS platform.
Adopting a version of "endstate correction" without nnops would greatly simplify testing on Continuous Integration (CI) systems. The absence of nnops would eliminate the need for artificial CUDA setups in the CI environment.
Desired Outcome:

Create a version of "endstate correction" that is compatible with macOS by removing the nnops dependency.
Implement dynamic switching between nnops and CPU implementation within the "endstate correction" codebase.
Ensure compatibility with existing macOS-supported components such as openmm-torch, torchani, and openmm-ml.
Enhance CI testing by providing a version without nnops, eliminating the need for simulated CUDA setups.

Additional Context:
Our goal is to seamlessly integrate "endstate correction" into our software stack while ensuring broad compatibility for macOS users. This adjustment would significantly enhance user experience and simplify development and testing processes.

Pin @wiederm here as well for visibility.


Use package in manifest and shorten import

We can use package to rename bitcoin_hashes to hashes and bitcoin_internals to internals. This makes imports more terse with no loss of meaning.

Fixed schemars test by not changing the bitcoin_hashes import.

@Kixunil and @sanket1729 you guys have ack'd but not approved, could you hit that button please.


[release-v3.28] Auto pick #9053: Update win FV test results semaphore path

Cherry pick of #9053 on release-v3.28.
#9053: Update win FV test results semaphore path
Original PR Body below
Description

Related issues/PRs

Todos

[ ] Tests
[ ] Documentation
[ ] Release note

Release Note

TBD

Reminder for the reviewer
Make sure that this PR has the correct labels and milestone set.
Every PR needs one docs-* label.

docs-pr-required: This change requires a change to the documentation that has not been completed yet.
docs-completed: This change has all necessary documentation completed.
docs-not-required: This change has no user-facing impact and requires no docs.

Every PR needs one release-note-* label.

release-note-required: This PR has user-facing changes. Most PRs should have this label.
release-note-not-required: This PR has no user-facing changes.

Other optional labels:

cherry-pick-candidate: This PR should be cherry-picked to an earlier release. For bug fixes only.
needs-operator-pr: This PR is related to install and requires a corresponding change to the operator.

Instead of changing the path we should call popd like the AWS code path does (addressed in https://github.com/projectcalico/calico/pull/9065)


Cleanse tests

Pull Request Test Coverage Report for Build 90

4 of 28 (14.29%)  changed or added relevant lines in 4 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.06%) to 14.618%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

tests/test_covariance.py
0
1
0.0%

tests/test_bo.py
0
4
0.0%

tests/test_gp.py
1
20
5.0%

Files with Coverage Reduction
New Missed Lines
%

bayeso/bo.py
1
23.75%

Totals

Change from base Build 87:
-0.06%

Covered Lines:
176

Relevant Lines:
1204

💛  - Coveralls

Pull Request Test Coverage Report for Build 90

4 of 28 (14.29%)  changed or added relevant lines in 4 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.06%) to 14.618%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

tests/test_covariance.py
0
1
0.0%

tests/test_bo.py
0
4
0.0%

tests/test_gp.py
1
20
5.0%

Files with Coverage Reduction
New Missed Lines
%

bayeso/bo.py
1
23.75%

Totals

Change from base Build 87:
-0.06%

Covered Lines:
176

Relevant Lines:
1204

💛  - Coveralls


Implement merge sort algorithm in Java

I will do this.

@tushar-nitave 👍

i'm already working on this. please assign me

i think the Merge Sort program is already present in Sorting/java?

@tushar-nitave @Mah1ndra The algorithms have been added but readme is missing. You can document that or feel free to create an issue to add a missing algo/pattern.

readme for merge sort?

@tushar-nitave yes

Ok. Working.


feat(i18n): Czech language support

Hello, I'd like to contribute a Czech language support. This PR is a complete translation and setup needed to make current main of ZITADEL work with Czech as another supported language.
Please let me know if there are any specifics as to contributing translations or anything I could do to the format/extent of this PR for a possible inclusion.
Thank you!

Hey @petrmifek
Thanks for your contribution, we really appreciate it.
We thank our contributors with a little gift, if you are interested, please reach out to<EMAIL_ADDRESS>we will then send you a form where you can fill your address, etc.


nigelb

Hi,
Can anyone tell me if the iopay wallet has a glitch at the moment?  When I open and unlock the wallet, the right side, where any balance would show is greyed out and I get the message "Unlock your wallet to see details".  Not too helpful!
I know I'm in the right place because it lets me see my private key, but not my balance.  Any ideas???  Advice would be appreciated!
Thanks...

Hi all,
Further to this, looks like the Cloudflare network may be to blame?


Set default assertion mode at class level

Feature request: It'd be handy to be able to put an annotation on a test class that would change the default assertion mode for any @ExpectedDatabase annotations on methods. We usually use NON_STRICT_UNORDERED mode and it's a little ugly-looking to have to specify that explicitly on every test method.
To be more concrete, I'm asking for something along the lines of,
@DbUnitConfiguration(defaultAssertionMode = DatabaseAssertionMode.NON_STRICT_UNORDERED)
public class MyDbUnitTest {
    @Test
    @ExpectedDatabase("MyDataSet.xml")
    public void testSomeDbStuff() { ... }
}

which would be equivalent to what we do today,
public class MyDbUnitTest {
    @Test
    @ExpectedDatabase(value = "MyDataSet.xml", assertionMode = DatabaseAssertionMode.NON_STRICT_UNORDERED)
    public void testSomeDbStuff() { ... }
}

It's a nice idea but I can't see an easy way to implement it without breaking back compatibility. If you come up with any ideas feel free to submit a pull-request.


CPP/taskcpp/Binary_to_decimal.cpp

Convert a Binary number to a decimal
NOTE:- Screenshot of the code and output is required

Hello assign this to me

Please assign this Issue!

Hey I have done pull request #195 !


[FLINK-2844][jobmanager] remove old web interface

The new web interface supports all features of the old web interface once #1164 and #1233 have been merged. It's time to remove the old one.

The WebFrontendITCase still needs to be adapted.

This should also remove all Jetty dependencies (runtime pom and root pom)

YarnSessionFIFOITCase checks the old job manager web interface. We should change that too.

An update from my side. I have

adapted the WebFrontendITCase
adapted the YarnSessionFIFOITCase
removed the Jetty dependencies

Based on  #1222 I changed the serving of the static files to work with the fat jar and a temporary directory. This is the default way now and ensures that everything works standalone and on YARN.

I suspect we can close https://github.com/apache/flink/pull/1222 then?

Yes, #1222 is obsolete now.

Build passes (ScalaShellLocalStartupITCase has some hickups).

Nice, will merge this...


SLIM-612 introduce result status to operations to make errors clear

Adds NOT OK result to ActionResponseDtos created when an exception has occurred.
Adds Result to the response for a non bundled specific configuration object (no longer returning an exception message as ConfigurationData without further indication of error).

All is well.


[New Theme Request] SelfhostedPro / Yacht

Yacht is an in-dev alternative to Portainer for managing your Docker environment.
https://github.com/SelfhostedPro/Yacht
Having theme.park available for Yacht would be fantastic.
Demo from their repository:

Loving theme.park and thank you for all the effort you're putting into it. It's made Portainer and Grafana much more enjoyable for me.

This is still under heavy development, so I'm gonna hold off on this for a while.


Fix typo in api helpers

expet => expect

It gets ignored unfortunately, which is surprising as I thought expect was a method call . . .