Is the project abandoned?

I was just looking at the release frequency, current issues, pending pull request, and overall activity as of late; and considering that I myself am experiencing some of the issues already reported, it is hard to not think the case. So, is the project abandoned?

Can you give some insights to this @jxnblk ?

In the case that it has been abandoned, do people just fork the repo and try to add their own changes?

I've been using https://github.com/system-ui/theme-ui as a straight-up replacement for this and it seems (mostly) compatible.

Maybe https://xstyled.dev is an alternative. It is inspired by styled-system but maintained but somebody else

I have migrated from Styled System to Theme UI. Which after some research seem's to be created by some of the same maintainers as Styled System and is also described as "The next evolution of Styled System".
As far as a migration between tools like these goes, Theme UI is fairly easy and quick to migrate to.
The structure is pretty much the same, but there are some bigger differences when it comes to the principles and approaches. All in all, with theme UI you will lose some flexibility to do stuff like custom props, but you'll gain in ease of use and features (color modes, color scheme media query, variants, ...).

I'm still wondering why there is no mention of Theme UI being the "official" new version of Styled System. Especially since both tools seem to be made by the same people and that Styled System looks pretty much abandoned.

Feel free to switch to Theme UI, as to me, this is the only sensible option at this point 🚀

See https://jxnblk.com/blog/two-steps-forward/ where author suggest people to give Theme UI a try (great read to understand history of CSS-in-JS as well)

I'm confused, according to Github insights, https://github.com/system-ui/theme-ui has also been started by (and primary maintainer) @jxnblk This may indeed be the "Two steps forward". However, considering this unannounced but implicitly deducted faith of Styled Systems, I'm now questioning the future prospects of Theme UI even though there is at least one other maintainer there.
https://xstyled.dev looks promising but does not seem to support react-native yet.

https://xstyled.dev looks promising but does not seem to support react-native yet.

I have not tried, but I think ‘@xstyled/system‘ can support react-native and ‘@xstyled/styled-components‘ will support it soon.

I just find it bit odd that there is nothing in the README or announcement about the current status of the project. It would be nice to know if this project is done and what people should move on to.
Is there a fork that is being maintained?

I just find it bit odd that there is nothing in the README or announcement about the current status of the project. It would be nice to know if this project is done and what people should move on to.
Is there a fork that is being maintained?

Hi all, I'm maintaining a fork that also adds a handful of frequently requested features from the issues here. The libraries aren't entirely identical (doesn't have all of the different styled-system packages) but the foundation is there.
https://github.com/system-props/system-props
Here's a shortlist of what's been added:

Rewritten in TypeScript, including types for props
Support for configurable pseudo props, similar to Chakra-UI's PsuedoBox
Support for theme values in shorthand properties (e.g., margin, padding, border, box-shadow, etc)
Designate theme values with a $ prefix

This is not the first project by @jxnblk that was abandoned abruptly.
I'm now maintaining a project that's based on https://github.com/jxnblk/system-components/ and not even sure what to migrate to.
I'm also worrying about the future direction here.

Hey @dmt0
I was in the same situation and made the switch to Theme UI, It's very similar to Styled System and the migration is pretty easy. There are some functionalities that aren't there, but others that make it worthwhile.
A lot of works have been done recently, and the project is pretty active.
I'd suggest you try it out!

I'm closing this issue. It's been 7 months now and I think my original question has been answered, albeit  implicitly. There are already some great alternatives listed here which we can all pick from. Happy coding!

Hey @dmt0
I was in the same situation and made the switch to Theme UI, It's very similar to Styled System and the migration is pretty easy. There are some functionalities that aren't there, but others that make it worthwhile.
A lot of works have been done recently, and the project is pretty active.
I'd suggest you try it out!

Isn't Theme-ui Emotion under the hood? That wasn't a hard transition?

I'd stay away from projects done by these guys altogether. It's all fun and games if you're using it for a toy project, but if you need to maintain something long term, it's a no-go. There are 3 abandoned projects now:

https://github.com/jxnblk/system-components/
https://github.com/rebassjs/components
this one
System UI - will it reach 1.0 and be abandoned right after in pursuit of a new "philosophy" or before 1.0?

No communication in the repos. No clear migration paths. Nothing.
Ripping out frameworks from production projects is not fun. I'd rather use something stable and focus on functionality.
</rant>
Credit where credit is due - all of those projects are actually really nice to use. But without long-term support all of this is for nothing.

@httpete
The migration between Styled Components to Emotion was very simple. The syntax is 99% the same.
The only difference being how global styles are handled, and the class composition. But overall not much at all.
As for staying off these projects, I do get the point, it is a very valid one. And I'm using Theme UI in production, so I'd like to believe it's gonna stay active for a while. But I haven't seen any activity from @jxnblk ever on that project. It's the community that keeps it going.
So far they're doing an incredible job.

I also made a fork of styled-system and added some improvements and fixes to it (plus wrote it in Typescript).
Even though the types aren't 100% there, the library functions mostly the same as this one (and the exceptions are noted in the readme) and I intend to support it going forward as I made a design system a top it and use that in some medium to large client projects.

I like https://github.com/ppiyush13/react-styled-flex simple approach

Maybe https://xstyled.dev is an alternative. It is inspired by styled-system but maintained by someone else.

There's any support to variants?

xstyled.dev is a great alternative!

I

xstyled.dev is a great alternative! It is a near drop-in replacement for styled-system

If it wasnt because it replaces styled-components entirely

https://github.com/The-Code-Monkey/styled-system/ continuation of the project here for anyone who wants it


Cypress Peer Dependency

will the Cypress Peer Dependency get update? i see its still on 4.5.0 which is very old.

We get:
▶ npm audit fix
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/cypress
npm ERR!   dev<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/cypress-plugin-snapshots
npm ERR!   dev<EMAIL_ADDRESS>from the root project

Although the plugin clearly works with<EMAIL_ADDRESS>I would submit a PR to change the peer dependency to change the peer dependency to:
  "peerDependencies": {
    "cypress": ">=4.5.0"
  },

But I don't know if this plugin works with cypress versions higher than 5.2

i am on "cypress": "^7.1.0" and it works fine locally on my machine.

@meinaart when can we expect this to be merged and published ?

has this fix been released?

Any news on this? I just got the error with Cypress 9.5.1

@ozkoidi were you ever able to resolve that issue from your screenshot?

Looks like a reasonable fork has happened => https://www.npmjs.com/package/@mosofsky/cypress-plugin-snapshots
(Make sure to review the commits since this repo yourself!)


Worker cleanup

We have several workers that haven't been up for some time, and every time the master restarts a message is sent to the status mailing list announcing that the worker is down.  If these workers have been abandoned I would like to remove them from the master, or figure out if there's something we can do differently from the master side to improve things.
Here are the currently-troublesome workers:

~@embray~

~bray-win10-cygwin-amd64~

~No data on last build~
Retired in #356 per https://github.com/python/buildmaster-config/issues/349#issuecomment-1331203465

@jkloth

kloth-win64
kloth-win11

@jkloth, I know you announced a move and extended downtime some months ago; do you have a timeline for the return of these workers?

@kulikjak

kulikjak-solaris-sparcv9

Last builds were a month ago after a 2 month disappearance, and those builds did not finish
Hoped to return around first week of December 2022 according to https://github.com/python/buildmaster-config/issues/349#issuecomment-1326745033

~@nsait-linaro~

~linaro2-win-arm64~

~Last build was 3 months ago.  I seem to have a vague memory of this being a transitional worker anyway?  Am I making that up? :)~
Removed in #355 per https://github.com/python/buildmaster-config/issues/349#issuecomment-1321913148

@orsenthil

skumaran-ubuntu-x86_64

Last build was 2 months ago.
To be fixed according to https://github.com/python/buildmaster-config/issues/349#issuecomment-1323226391

Honorable mentions:

@koobs

koobs-freebsd-564d
Last build was only 6 days ago, but this one still seems like a frequent entry in the list of workers that don't reconnect after a master restart.  Are such restarts actually causing a problem for this worker?  Do we need to figure out a different strategy for restarting?
To be fixed Soon™ according to https://github.com/python/buildmaster-config/issues/349#issuecomment-1324142009

To anyone @-mentioned above, please comment here with the status of your worker(s).  I'll give at least a couple of weeks for responses here before I do anything with these (and may forget about it for longer than that :)), I'm not trying to rush anyone out here.
Thank you all for running your workers, whether they're still active or not.  They have all served the CPython project well!

@nsait-linaro https://github.com/nsait-linaro

linaro2-win-arm64

Last build was 3 months ago. I seem to have a vague memory of this
being a transitional worker anyway? Am I making that up? :)

Yes, you are right. Will open a PR to remove the worker.
On Fri, 18 Nov 2022 at 16:29, Zachary Ware @.***> wrote:

We have several workers that haven't been up for some time, and every time
the master restarts a message is sent to the status mailing list announcing
that the worker is down. If these workers have been abandoned I would like
to remove them from the master, or figure out if there's something we can
do differently from the master side to improve things.
Here are the currently-troublesome workers:

@embray https://github.com/embray

bray-win10-cygwin-amd64

No data on last build

@jkloth https://github.com/jkloth
kloth-win64
kloth-win11

@jkloth https://github.com/jkloth, I know you announced a
move and extended downtime some months ago; do you have a timeline for the
return of these workers?

@kulikjak https://github.com/kulikjak
kulikjak-solaris-sparcv9

Last builds were a month ago after a 2 month disappearance,
and those builds did not finish

@nsait-linaro https://github.com/nsait-linaro
linaro2-win-arm64

Last build was 3 months ago. I seem to have a vague memory of
this being a transitional worker anyway? Am I making that up? :)

@orsenthil https://github.com/orsenthil
skumaran-ubuntu-x86_64

Last build was 2 months ago.

Honorable mentions:

@koobs https://github.com/koobs

koobs-freebsd-564d
Last build was only 6 days ago, but this one still seems like a
frequent entry in the list of workers that don't reconnect after a master
restart. Are such restarts actually causing a problem for this worker? Do
we need to figure out a different strategy for restarting?

To anyone @-mentioned above, please comment here with the status of your
worker(s). I'll give at least a couple of weeks for responses here before I
do anything with these (and may forget about it for longer than that :)),
I'm not trying to rush anyone out here.
Thank you all for running your workers, whether they're still active or
not. They have all served the CPython project well!
—
Reply to this email directly, view it on GitHub
https://github.com/python/buildmaster-config/issues/349, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AU3CND5ZZ5XJZMJT2CWEBN3WI6VG3ANCNFSM6AAAAAASEVGFVM
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Niyas Sait
Linaro Limited

@kulikjak

kulikjak-solaris-sparcv9

Last builds were a month ago after a 2 month disappearance, and those builds did not finish

Sorry about this one. The machine broke some time ago and because of several reasons we were not able to fix everything yet. However, we still intend to bring a Solaris SPARC machine and its worker up again and hopefully make Solaris green once that is done.

However, we still intend to bring a Solaris SPARC machine and its worker up again and hopefully make Solaris green once that is done.

Thanks for the update!  Do you have a rough timeline on when it might be back?

@nsait-linaro https://github.com/nsait-linaro - linaro2-win-arm64 - Last build was 3 months ago. I seem to have a vague memory of this being a transitional worker anyway? Am I making that up? :)
Yes, you are right. Will open a PR to remove the worker.

Just sent PR for this one https://github.com/python/buildmaster-config/pull/355

I will fix mine. Didn't realize it was down or had issues.
On Fri, Nov 18, 2022, 8:29 AM Zachary Ware @.***> wrote:

We have several workers that haven't been up for some time, and every time
the master restarts a message is sent to the status mailing list announcing
that the worker is down. If these workers have been abandoned I would like
to remove them from the master, or figure out if there's something we can
do differently from the master side to improve things.
Here are the currently-troublesome workers:

@embray https://github.com/embray

bray-win10-cygwin-amd64

No data on last build

@jkloth https://github.com/jkloth
kloth-win64
kloth-win11

@jkloth https://github.com/jkloth, I know you announced a
move and extended downtime some months ago; do you have a timeline for the
return of these workers?

@kulikjak https://github.com/kulikjak
kulikjak-solaris-sparcv9

Last builds were a month ago after a 2 month disappearance,
and those builds did not finish

@nsait-linaro https://github.com/nsait-linaro
linaro2-win-arm64

Last build was 3 months ago. I seem to have a vague memory of
this being a transitional worker anyway? Am I making that up? :)

@orsenthil https://github.com/orsenthil
skumaran-ubuntu-x86_64

Last build was 2 months ago.

Honorable mentions:

@koobs https://github.com/koobs

koobs-freebsd-564d
Last build was only 6 days ago, but this one still seems like a
frequent entry in the list of workers that don't reconnect after a master
restart. Are such restarts actually causing a problem for this worker? Do
we need to figure out a different strategy for restarting?

To anyone @-mentioned above, please comment here with the status of your
worker(s). I'll give at least a couple of weeks for responses here before I
do anything with these (and may forget about it for longer than that :)),
I'm not trying to rush anyone out here.
Thank you all for running your workers, whether they're still active or
not. They have all served the CPython project well!
—
Reply to this email directly, view it on GitHub
https://github.com/python/buildmaster-config/issues/349, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACREKWJGHESWDNVW7HQSULWI6VGZANCNFSM6AAAAAASEVGFVM
.
You are receiving this because you were mentioned.Message ID:
@.***>

@zware storage failure last week on freebsd-564d, working on recovering it.
Can we temporarily disable, or is config ok to sit there for now?
I'll either fix it or stand up a new instance, and reach out to brainstorm potential restart behaviour improvements. I'm not sure what's up with that and would need to investigate.

Can we temporarily disable, or is config ok to sit there for now?

It's ok to stay for now, especially if you have a rough timeline on when it may be back :)

It's ok to stay for now, especially if you have a rough timeline on when it may be back :)

Rough timeline is asap-life-permitting, thanks mate 👍

Thanks for the update! Do you have a rough timeline on when it might be back?

We talked about it today, and I hope that we will be able to bring it up again sometime next week. Also, I will newly be the direct maintainer of this machine (it was slightly more complicated before), so I will hopefully be able to solve potential future problems much faster.

For bray-win10-cygwin-amd64, I am no longer at the job that afforded me time to work on Python for cygwin.  I really wish I could do more but I don't see it getting back up again any time soon, much less reliably :(

@embray Thanks for the update!  I'll go ahead and remove the configuration for now, but if circumstances change again it can always be added back in the future :)

Hi, I am very sorry, but the lab where our current machine is will be closed in just a few days, which means that we need to find a different machine/place for it. We are working on that, but at this point, I don't really know how long that will take...

Hi. Sorry it took so long, but the Solaris machine is up again and should stay running for many months to come.

Finally back to look at this again.
One of the biggest issues I'm currently seeing is frequent detach/reattach cycles from skumaran-ubuntu-x86_64 (@orsenthil), linaro-win-arm64 (@pbo-linaro), kulikjak-solaris-sparcv9, (@kulikjak), and angelico-debian-amd64 (@Rosuav).
Can each of you check your buildbot.tac and confirm that you have buildmaster_host = 'buildbot-api.python.org' (not buildbot.python.org)?  You may also want to check your keepalive setting; 60 is working well for two of my workers.

Ah, mine had a probably-old address buildbot.python.org and a keepalive of 600 - that might have been the problem. Thanks for pinging.
I've made the change and fully rebooted the VM (just in case there were other, unrelated issues), so let's see if that improves stability.

Looks like that resolved what I was seeing from yours; thanks!

Solaris buildbot was also configured to connect to buildbot.python.org; I switched it to the correct one yesterday so hopefully connection issues should be gone.

I updated buildmaster_host and keep_alive settings for linaro-win-arm64.

Both look healthy now, thank you!

What's the status of this issue @zware? Can it be closed?


Create lute.txt

Lviv University of Trade and Economics

@thedeathlessend Pull request merged. Thank you!


Installation instructions for MAC OSX

First , you should talk about Xcode or CommandLineTools; otherwise, vim won't compile because there may be neither make, clang, nor other command line utilities to build and install vim successfully (even that git!)   by default on some versions of Mac OS X.
Next, you should mention various options of configure; in particular, --disable-darwin and --with-mac-arch, which are most relevant to that particular OS.
To check the resulting executable, consider making use of make test.
Last but not least.  It could be OK to replace /usr/bin/vim of your system with a newly compiled vim at your own risk.  But, generally speaking, I do think such recommendation is wrong.
It's far better to use the PATH environment variable than overwriting or aliasing vim, and that's a widely accepted way for years.

Thanks for the response, I'll make those changes.

How about suggesting
sudo make install

instead of overwriting system Vim or messing with aliases or PATH?

I realize this is late but there is a patch sent to the mailing list: https://gist.github.com/sukima/4d649a5dfeb38a05a344 I don't remember the outcome of that.

There's nothing special to OS X to build and install Vim.  It's as easy as that for other UNIX variants.
First, make sure you've installed Xcode or CommandLineToots.  If not, open a terminal and do
$ make --version

Then, a window pops up instructing you to install the developer tools.
Next, unarchive the tarball or clone the git repository, and, just like other UNIX variants,
$ cd vim/src
$ make
$ make test
$ sudo make install

or
$ cd vim
$ ./configure
$ make
$ make test
$ sudo make install

Either of them will install the executables into /usr/local/bin with  the runtime into /usr/local/share/vim/vim74.
If you find the default configuration is not enough for your needs, read src/INSTALL for general information about build and installation, e.g., how to pass variables to make and options to configure, and read src/INSTALLmac.txt for the information specific to OS X.
Reading src/Makefile and src/configure.in is often useful and helpful to figure out how to set up the build and installation system to meet your demands.


Fix travis build so it only publishes master

The branches: master config is apparently not working - my last PR got published to gh-pages automatically, but should not have done so until merge to master.

I fixed this by simply turning on PR builds on Travis. If we end up with any code that requires quality checks to run, we can use some of the solutions discussed on these pages:
http://docs.travis-ci.com/user/pull-requests/
http://stackoverflow.com/questions/21076678/disable-travis-ci-for-pull-requests
The issue wasn't that branches:master doesn't work - travis was not incorrectly building branches. The issue is that PRs are a merge-master locally on travis, which means the branches:master config doesn't apply.

Hey man. Sadly, you should probably drop my account front the GitHub repos.

On Sep 18, 2015, at 7:35 PM, Nathan Evans<EMAIL_ADDRESS>wrote:
Closed #20.
—
Reply to this email directly or view it on GitHub.


[spmd] self-attention module's proj.bias isn't properly updated on all ranks but rank 0

What the problem is:

Sharded TensorParallelMultiheadAttention(#477) module fails to update proj.bias parameter though the back-propagated gradient is correct.
Also, this error doesn't occur on rank 0.

How to reproduce:
I created a branch ad-hoc-self-attn-exp which based on origin/main with a bunch of print statements added to help reproduce the problem.
git checkout origin/ad-hoc-self-attn-exp
pytest test/spmd/tensor/parallel/test_tp_examples.py -s -k test_self_attn_megatron_e2e

Observation:

Other parameters (qkv.weight, qkv.bias, proj.weight) don't have this issue.
Model on Rank 0 perform the same parameter update with the single-node model.
Both proj.bias and its grad has replicate placement on mesh while qkv.bias is sharded on mesh.

This is kind of OK because we have a trick for this so that we only use bias from rank0 (local rank)


DatabaseOrder not respected when used in conjunction with DatabasesInParallel

When using @DatabasesInParallel = 'Y', databases to be processed are stored in the QueueDatabase table, along with the database order. If there are multiple jobs configured to use different orders, the database order for all queues, including active queues, will be updated to whichever queue was updated last. In my case, the frequent log backup order (random), is overriding the order of longer duration jobs: full/diff backup (size desc), and integrity (date asc).
This issue is present in stored procs: DatabaseBackup, DatabaseIntegrityCheck, and IndexOptimize. I believe the query responsible for this is the following:
UPDATE QueueDatabase
SET DatabaseOrder = tmpDatabases.[Order]
FROM dbo.QueueDatabase QueueDatabase
INNER JOIN @tmpDatabases tmpDatabases ON QueueDatabase.DatabaseName = tmpDatabases.DatabaseName

This lacks a predicate to limit the queues that are updated, resulting in all queues being updated with the same database ordering.

This issue has been fixed.
https://ola.hallengren.com/versions.html
Thank you for reporting it.


fix: Update core-metadata.yaml for missing tabs and description'

close #4611
ref: https://github.com/edgexfoundry/go-mod-core-contracts/pull/783/files

If your build fails  due to your commit message not passing the build checks, please review the guidelines here: https://github.com/edgexfoundry/edgex-go/blob/main/.github/Contributing.md
PR Checklist
Please check if your PR fulfills the following requirements:

[x] I am not introducing a breaking change (if you are, flag in conventional commit message with BREAKING CHANGE: describing the break)
[x] I am not introducing a new dependency (add notes below if you are)
[ ] I have added unit tests for the new feature or bug fix (if not, why?)
[ ] I have fully tested (add details below) this the new feature or bug fix (if not, why?)
[x] I have opened a PR for the related docs change (if not, why?)

Testing Instructions

New Dependency Instructions (If applicable)

Codecov Report

Merging #4612 (0622ab8) into main (e66fa62) will not change coverage.
The diff coverage is n/a.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@           Coverage Diff           @@
##             main    #4612   +/-   ##
=======================================
  Coverage   41.49%   41.49%
=======================================
  Files         105      105
  Lines        9719     9719
=======================================
  Hits         4033     4033
  Misses       5343     5343
  Partials      343      343


SCI-952 confirm_human middleware

SCI-952
Story
Decisions for some (most?) experiments are best done in Python code, before template rendering starts. For this to work with existing mechanism that filters out bots, we need to call the relevant function early enough. Best place do to that is a middleware class.
Overview
This PR adds a new middleware class that calls confirm_human method. It was not added in the existing middleware because the two are both optional.
Also fixed failing tests in Python 2 due to changes in iterators

Sorry, wrong repo :D


[BEAM-1260] Revert "Captures assertion site and message in PAssert"

This reverts commit c62611c73ab0f9a5769f3ee9b28b11e917628f78.
It breaks post-commit Dataflow and Flink runners, e.g. https://builds.apache.org/job/beam_PostCommit_Java_RunnableOnService_Dataflow/2010/org.apache.beam$beam-runners-google-cloud-dataflow-java/consoleFull
R: @kennknowles

LGTM, merging.

Every tweak to how we wrap (or don't wrap) exception seems to bite us. It is a very brittle area of the code. From what I could tell on the Dataflow postcommit, the new sites were missing, right? It was only the new tests failing.


Add function to unescape string

For the Token::Attribute variant and similar, the StrSpan returned can get the original string value, but this library doesn't seem to have a function to unescape xml-encoded strings, so I've had to hand-roll my own version of this. It would be great if this crate had something like:
#[cfg(feature = "alloc")]
pub fn unescape(&str) -> Result<alloc::borrow::Cow<str>, UnescapeError>;

You cannot properly unescape XML strings without parsing DTD. This is what roxmltree does for you.
Not to mention that text node strings, attribute strings and CDATA strings all have to be handled differently. XML is a mess.
I don't see a way it can be implemented on the xmlparser side. Too much complexity and context required.

I will think about it. As I mentioned above, it's not that simple, since text node text and attribute value text have to be escaped differently. So the API would be a bit convoluted.

Short of reading a spec manual, I haven't been able to find anything saying the (builtin) escape sequences are different for text nodes and attribute values. I've seen cases where, e.g., > doesn't have to be escaped in attr text specifically (and similar), like v="a>b" or v="a>b". But as far as I can tell they both get parsed as v="a>b", so the same unescape logic is used as text nodes. CDATA has different semantics, but that would just be the user's responsibility to know not to unescape the content.

The unescape should unescape new lines as well. And they have to be handled differently.
If you want to escape just > and friends - you can easily do it on your side.

The unescape function should unescape new lines as well. And they have to be handled differently.

While text nodes can contain literal new line characters, as far as I can tell they still unambiguously unescape CR and LF (
 and
) if present regardless, so it seems like the same unescape function as attr text would be fine, wouldn't it?

If you want to escape just > and friends - you can easily do it on your side.

I mean it's also the &#[0-9]+; and &#x[0-9a-fA-F]+; numeric forms. That's kind of non-trivial and literally every user that needs unescaping would have to hand-roll their own version like I did. I mean it's not crazy hard, but very annoying. The only way I'd say that's "easy" for users is .replace(...).replace(...).replace(...)... for all the standard escape sequences, which is wildly inefficient and doesn't work for the numeric encoded escapes. And if there was a single impl in this crate, we could add more efficient options like zero-copy (when possible).

The current text unescape code in roxmltree is nearly 400 LOC. It's far from trivial and I'm not sure it would be easy to port to xmlparser. Maybe one day. For now - use your own implementation.

I mean it's also the &#[0-9]+; and &#x[0-9a-fA-F]+; numeric forms

This is already available via Stream::try_consume_reference. See example here.

The current text unescape code in roxmltree is nearly 400 LOC. It's far from trivial and I'm not sure it would be easy to port to xmlparser. Maybe one day. For now - use your own implementation.

Well they also do context-based entity resolving, which I was suggesting we not handle - just basic escape codes. But even better:

This is already available via Stream::try_consume_reference. See example here.

If that exists, why not just provide a function like unescape_with from quick-xml:
pub fn unescape_with<'a, F: Fn(&str) -> &str>(content: &'a str, entity_resolver: F) -> Cow<&'a str>;

That could use the existing stream features this crate already has, consumes characters that are encoundered (including numeric escape sequences which are already supported), and any entity references are just handed off to the passed-in entity resolver.
Then it really would be easy for users to hand roll their own since we added the generic form for any resolver:
fn my_unescape(s: &str) -> Cow<&str> {
    xmlparser::unescape_with(s, |x| match x {
        "name" => "marco polo",
        "age" => "185",
        "gt" => ">",
        ....
    })
}

If that exists, why not just provide a function like unescape_with from quick-xml:

Because it's not XML complaint! You want a function that is good enough for you. I want a function that is correct. Period.
There is no "just", "basic" or "simple" in XML. XML is hated for a reason.
As I said before, there are no plans to implement such functionality. You have to write you own.

The point is it would be up to the user to have XML-compliant entity resolving if they want that, cause we'd only handle numeric escape codes, which should always be unescaped in every context. I fail to see how that's such an unacceptable compromise - there would be no non-compliant logic in this crate. I just want something that's most convenient for users. But since you're so adamantly against it, I'll just make my own util crate.

Ok, well that's a valid reason. God, XML is a mess...


Update the Golang bindings

This PR brings in changes from Docker for Mac and Windows to the Golang Datakit bindings.
This is necessary for us to switch to using the bindings upstream instead of our internal package

This also explains why the bridge fails to handle PRs being deleted (the Go hooks try to delete the wrong directory). Though I'm not sure why we don't see a Failed to Remove message in the logs when that happens.


Development of VesselWithHeaveAndRotation dynamic systems

New system is to implement is module offshore.py. It should be inherited from similar class being implemented within scope of the module if possible.

The system works properly, when called using DynSysOverviewReport it returns all the necessary information.


Remove names argument from configuration factory function

Remove names argument from readConfig function because it doesn't do anything due to the removal of that argument in Configuration class constructor.
const readConfig = (dirPath, options, names) =>
  new Config(dirPath, options, names);

class Config {
  constructor(dirPath, options = {}) {
    ...
  }
}

[x] tests and linter show no problems (npm t)
[x] code is properly formatted (npm run fmt)

Landed in https://github.com/metarhia/config/commit/87874f579e51833e2fddfcf9953fda3a8f6f163a


Beamng enters VR but headset shows black screen

Using a Samsung Odyssey plus on win11 with a gtx1070 and 32gb ram.
Here's the log for troubleshooting.
XR_APILAYER_MBUCCHIA_vulkan_d3d12_interop.log
Thank you for your awesome support to VR.

It's working fine here. Try disabling OpenXR Toolkit and XRNeckSafer.

Can you also check you're running the latest Nvidia driver? I hope your driver isn't as old as your GPU ^^ :)

it was xr neck safer, I disabled it and it worked. Thank you!

Thanks for letting me know. This is super strange... I'm not even sure how that one could interfere!


Moving persistence logic into BulkMutation.

The BulkMutation processing was duplicated, yet was inconsistent, in BatchExecutor and BigtableBufferedMutator.  Encapsulating all of the persistence logic into BulkMutation for better reuse.

All comments were addressed.  PTAL.

LGTM


Bump version to 0.1.1

I have to bump the version to reupload to pypi

@isamaru feel free to delete the merged branches (to keep the repo clean).


Restructured Compiler to contain Transforms. Added an InlineInstance pass.

New structure:

A Compiler contains a sequence of Transforms.
Each Transform consumes a Circuit and a list of CircuitAnnotations.
Each Transform returns a Circuit, an optional CircuitAnnotation, and an optional  RenameMap.
After executing each transform, the compiler updates the list of CircuitAnnotations with the RenameMap.

An example Transform, InlineInstances,  uses this system.

Ah, good stuff.

On the whole this looks great!
If you agree @azidar, I'm going to look in to tweaking the InlineInstances pass to use Uniquify's stuff to help deal with name collisions. @davidbiancolin and I have a transformation that I'll try out with this branch just to make sure I understand what all is going on and how to use it. Good work!


fix: code generated from proto breaks compilation

Fixes #291
Changes:

Re-generated protobuf with make -C pkg/connectors build
Actions in M4DModule are now SupportedActions instead of EnforcementActions  (m4dmodule_types.go); in the spirit of https://github.com/IBM/the-mesh-for-data/issues/65.
Using RawExtension instead of proto generated structures in CRDs:

Added pkg/serde with RawExtension (de)serialization
Transformations passed to module arguments are now RawExtensions (blueprint_types.go)
Connection in app.DataStore is now RawExtension (datacatalog_types.go)
Extracting from catalog connector only required fields (data_catalog_interface.go)

Can you explain why the move to raw extensions?

Can you explain why the move to raw extensions?

Can you explain why the move to raw extensions?

It is described in the issue. Newer versions of protoc-gen-go generate code that can't be used inside CRDs (the structures are not allowed to be copied). We had this issue for a while now and from time to time someone accidently bumped the version and caused our code to break. We recently updated protoc-gen-go because we had to (dependency issues) and this issue came back.
The use of RawExtension is a way to include arbitrary objects in CRDs. See the issue for a link to its use in opa.

Can you explain why the move to raw extensions?

It is described in the issue. Newer versions of protoc-gen-go generate code that can't be used inside CRDs (the structures are not allowed to be copied). We had this issue for a while now and from time to time someone accidently bumped the version and caused our code to break. We recently updated protoc-gen-go because we had to (dependency issues) and this issue came back.
The use of RawExtension is a way to include arbitrary objects in CRDs. See the issue for a link to its use in opa.


I'm trying to run the application on the Android emulator, but it gives an ndkVersion error

Is there an existing issue for this?

[X] I have searched the existing issues

The question

I recently had an ndkVersion error.
I was able to fix the problem when I found the following block was missing from the main android\build.gradle file
rootProject.buildDir = '../build'
subprojects {
project.buildDir = "${rootProject.buildDir}/${project.name}"
}
No idea why it was missing or why it cured the problem! I assume it was a path problem.

I managed to solve the problem, it was a problem related to settings due to the application's superclipboard. I configured the file android/app/build.gradle and android/app/src/main/AndroidManifest.xml


[HW]

Name: Samreen Reyaz A.
Email<EMAIL_ADDRESS>Linkedin Profile: https://www.linkedin.com/in/samreen-reyaz/
Attach the homework step I screenshots below:

Attach the homework step II screenshots below:

Looks like you were successful in deploying the app, thanks Samreen!

Here's your badge. Thank you again for joining us. https://api.badgr.io/public/assertions/vgIKi_XHT-inHelrZ2cHQA?identity__email=samreenreyaz%40outlook.com

Thank you for the amazing session!
--
Thanks and regards,
Samreen Reyaz
Phone: +91-99200-12297
LinkedIn: linkedin.com/in/samreen-reyaz/http://linkedin.com/in/samreen-reyaz/

From: RyanWelford @.>
Sent: 27 May 2021 20:12
To: datastaxdevs/workshop-astra-tik-tok @.>
Cc: SamDaQueen @.>; Author @.>
Subject: Re: [datastaxdevs/workshop-astra-tik-tok] [HW]  (#22)
Looks like you were successful in deploying the app, thanks Samreen!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/datastaxdevs/workshop-astra-tik-tok/issues/22#issuecomment-849693595, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AI3VNNJLIZNXJMXFAYIL23TTPZK6BANCNFSM45TXR5DA.


feature support push down no group agg to olap scan

Proposed changes
Issue Number: close #14464
legacy planner #12881
use zonemap to do aggregate without group by exprs.
valid aggregate function:

count
min
max

Problem summary
Describe your changes.
Checklist(Required)

Does it affect the original behavior:

[ ] Yes
[ ] No
[ ] I don't know

Has unit tests been added:

[ ] Yes
[ ] No
[ ] No Need

Has document been added or modified:

[ ] Yes
[ ] No
[ ] No Need

Does it need to update dependencies:

[ ] Yes
[ ] No

Are there any changes that cannot be rolled back:

[ ] Yes (If Yes, please explain WHY)
[ ] No

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 35.44 seconds
load time: 430 seconds
storage size:<PHONE_NUMBER>7 Bytes
https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20221129211336_clickbench_pr_55152.html


Animate the flowers

Scope
We need to animate all the flowers in the unity scenes Forest and Town. The goal is to make animations for the flowers as if the wind were hitting them.
How flowers are currently implemented?
We have two types of flowers with different colors, we need to animate both types:

All flowers is located inside the "Flowers" object inside the "Grid" object for each scene.
Each flower inside the map is an object called "FlowerType1" or "FlowerType2".
In the inspector panel you can see the characteristics and components of each flower.
Don't touch the order and sorting layers.
Don't remove or change the asset of any flower, just make them animated.

How to apply?

Please follow the contribution guidelines in the readme file

hello @jimenezz22  i'm an experienced frontend developer and a blockchain developer i would love to work on this issue
Pleasee kindly assign :)

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
I am an advanced computer science student with experience in Java, JavaScript, and Unity. I am currently part of SunsetLabs, where I am responsible for the frontend development of the game Citizen of Arcanis, which we are working on in Unity 3D. This role has provided me with practical experience in asset management, animations, and UI systems in Unity. Given my experience in Unity 3D, I am confident in my ability to tackle issues in Unity 2D and implement solutions efficiently, such as character animations and UI enhancements.
How I plan on tackling this issue
Hello,
I am interested in animating the flowers in the Forest and Town scenes to simulate the effect of wind. I propose the following:
Animator: I will set up an Animator for each type of flower, using different animation cycles that simulate the smooth and natural movement of the flowers in the wind. This will include animations that reflect the tilting and swaying of the flowers in various directions.
Effect Adjustments: I will adjust the speed and frequency parameters of the animations to ensure they are consistent with the environment, making sure the movement feels realistic and not forced.
Scene Testing: I will conduct tests in both scenes to ensure the animations integrate well and display correctly within the game's context.
I am ready to start and contribute to the project. Thank you for considering my proposal.

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
I have development experience in Unity, where I have worked on various tasks such as setting up character animations, configuring camera systems and implementing interactive elements in scenes. My previous experience with similar tasks on the Sunset Labs project has prepared me well to address this issue effectively and deliver high quality results.
How I plan on tackling this issue
I would like to contribute to this issue. I am currently working on the Sunset Labs project with Unity and have already completed several tasks, such as setting up animations and the character camera. I have some experience with the tool, and I’m ready to take on the challenge of animating the chimneys. I plan to implement a particle system to simulate smoke coming out of the chimneys, with appropriate settings to ensure the effect integrates seamlessly with the environment.

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
Hello @jimenezz22
I'm a software engineer from Costa Rica and a proud member of Dojo Coding. I've contributed to projects like Go Stark Me, Coffiblocks, and DipDup, and I have experience with technologies such as C#, Cairo. I've created some basic animations using Unity so I think that can do this.
How I plan on tackling this issue
For this issue I will:
1. Understand the Flowers object: I will analyze the Flowers object to get more context about them
2. Animating: I will animate the object using the flower spritesheets in the direction of the wind.
3. Test: I will make sure that all the flowers are animated in the direction of the wind.
4. Documentation: I will prepare any necessary documentation to support the implementation.
Looking forward to your feedback!
Best regards,
Diego Duarte Fernández.

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
i have experience in game dev previously as personal projects and hoping to make use of them here
How I plan on tackling this issue
I'll apply sine wave modulation on this visual "ripple" effect of flower patches with a harmonized flower animation system. Flowers would behave in response to a virtual wind vector changing direction at a slow pace. There should be a small difference in the frequency response between FlowerType1 and FlowerType2 so there is even more natural variety. Each flower will use custom lightweight scripts sampling its position for the phase offset; that creates meadow-like wave patterns, preserving existing sorting layers and hierarchies.

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
I am a Full Stack Developer specializing in Next.js, TypeScript, Node.js, Cairo and Rust . With over 31 contributions across projects in the OnlyDust ecosystem, I’ve developed strong proficiency in delivering high-quality solutions and resolving complex issues within tight deadlines. My experience spans frontend, backend, smart contracts, and the optimization and maintenance of scalable codebases.
How I plan on tackling this issue
To animate the flowers in the Unity scenes (Forest and Town), I aim to create wind-like movements for two types of flowers without altering their existing structure or assets.
The implementation will begin by analyzing the current organization of the flowers, which are grouped under the “Flowers” object within the “Grid.” I will develop a wind animation script targeting each flower type, specifically focusing on the movement of their petals and stems.
Using Unity’s animation tools, I’ll create effects that simulate gentle swaying in response to wind, incorporating variations to enhance realism. I will ensure that the existing order and sorting layers remain unchanged and that no assets are modified.
Throughout the process, thorough testing will be conducted to guarantee seamless integration with the scenes, and I will document our methods for future reference.

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
I'm from dojo coding
All flowers are located inside the "Flowers" object within the "Grid" object of each scene. This means I'll access and manipulate the flowers under these objects, without changing their hierarchy, sorting layers, or assets.
How I plan on tackling this issue
I'll create a simple swaying effect to simulate wind hitting the flowers. This can be done by rotating or scaling the flower models back and forth to create the illusion of them bending under the force of the wind.I'm proficient in C# scripting, which will allow me to customize the animations programmatically if needed for better performance or control.

gm @CristopherAguilar10 assigned to you, feel free to research an implement the solution

gm @CristopherAguilar10 assigned to you, feel free to research an implement the solution

gm @jimenezz22, thank you very much for the opportunity


Release Storage Track 2 Library Preview 4 for Python

*=Work owned by xstore team
Features

[x] * Batch #6436

[x] Azure.Core support for content type multi-part/mixed #6995

[x] * Echo client request ID #6437
[x] * DownloadSparsePageBlob #7295

Breaking Changes

[x] Consistency in offset and length #7509
[x] Permission models #7508  #7510
[x] from_blob_url method #7511
[x] max_connections #7512
[x] Modify **kwargs #7503

Fit and finish

[x] Other API review changes #7507
[x] Tests #7263
[x] Use swagger generated version as constant API version #6193
[x] Regenerate Swagger #7264
[x] Unicode chars #6685
[x] userDelegationToken bug #6977
[x] Urllib3 Bug #7407
[x] * download blob with offset bug #7061

Moved to Preview 5 / At risk

[ ] CI improvements #6167
[ ] Storage Stream Downloader #7504
[ ] Retriable data streamer #5121
[ ] response hook param #7067
[ ] Docs  #6165
[ ] Tests #6225, #5120

Preview 4 has shipped.  All remaining, open issues moved to preview 5.


Supporting BCP14 (RFC 2119) keywords

Some keywords are special in Internet Drafts / RFCs: "MUST", "MUST NOT", "SHOULD", etc.
These words are BCP14 keywords and must always be represented as uppercase "MUST". Our gem should detect these and ensure they are properly encoded in the XML within bcp14 tags.

There is provision to mark these up in the Asciidoc for v3: [bcp14]#MUST NOT# will produce <bcp14>MUST NOT</bcp14>. I would be very wary of going further, and marking up automatically any instance of uppercase "MUST NOT" etc in the source. BCP14 is not supported in v2.
I do not believe anything further needs to be done with these.

... Could I confirm that's ok, @ronaldtse? Or do you want me to at least issue warnings if it finds either a BCP14 not in capitals, or a capital MUST not marked up as BCP14?

Syntactically [bcp14]#MUST NOT# is fine but as you can see in every Internet-Draft or RFC, there are A LOT of them in every document. In MMark the star-star (sorry on mobile) syntax is used which is OK. It would be great if there is some shortcut syntax for BCP14 elements.
On the rfc-openpgp-oscca draft, remove the star-star from a keyword, compile it and run the idnits tool on the txt, you will see the various warnings including the "bcp14 keyword not marked" one.

In v2 I believe bcp14 keywords must be capitalized too.

Merge this issue into #43


[Python] Expose FileReader::ReadRowGroups() to Python

Expose ReadRowGroups to Python to allow efficient filtered reading implementations as suggested @xhochy in https://github.com/apache/arrow/issues/2491#issuecomment-416958663_
Without this PR users would have to re-implement threaded reads in python.

As it stands, this PR replicates the C++ interface of parquet in python. Namely it introduces the method read_row_groups(row_groups, ...) in addition to the existing read_row_group(i, ...) in ParquetReader and ParquetFile.
It might be worth considering whether maintainers would prefer avoiding the almost-duplication in the API and would prefer to extend the functionality of the existing read_row_group() to accept a list-like object in addition to the currently accepted integer.

@ARF1 Thank you for the PR.  Could you open a JIRA and prefix the PR title with: ARROW-{JIRA #}:
https://github.com/apache/arrow/blob/master/.github/CONTRIBUTING.md has more thorough documentation on the process.

It also looks like there are flake8 violations:
+python3 -m flake8 --count /home/travis/build/apache/arrow/python
/home/travis/build/apache/arrow/python/pyarrow/parquet.py:193:24: E128 continuation line under-indented for visual indent
/home/travis/build/apache/arrow/python/pyarrow/parquet.py:218:80: E501 line too long (85 > 79 characters)

@ARF1 Thank you for the PR. Could you open a JIRA and prefix the PR title with: ARROW-{JIRA #}:
https://github.com/apache/arrow/blob/master/.github/CONTRIBUTING.md has more thorough documentation on the process.

@emkornfield Done. Thanks for the guidance. The flake8 violations should now also be fixed. The checks are still running...

Codecov Report

Merging #5241 into master will decrease coverage by 22.54%.
The diff coverage is 100%.

@@             Coverage Diff             @@
##           master    #5241       +/-   ##
===========================================
- Coverage   87.64%   65.09%   -22.55%
===========================================
  Files        1033      500      -533
  Lines      148463    67929    -80534
  Branches     1437        0     -1437
===========================================
- Hits       130118    44219    -85899
- Misses      17983    23710     +5727
+ Partials      362        0      -362

Impacted Files
Coverage Δ

python/pyarrow/parquet.py
92.34% <100%> (+0.04%)
:arrow_up:

python/pyarrow/_parquet.pyx
91.33% <100%> (+0.04%)
:arrow_up:

python/pyarrow/tests/test_parquet.py
96.61% <100%> (+0.1%)
:arrow_up:

cpp/src/arrow/util/memory.h
0% <0%> (-100%)
:arrow_down:

cpp/src/gandiva/date_utils.h
0% <0%> (-100%)
:arrow_down:

cpp/src/arrow/util/memory.cc
0% <0%> (-100%)
:arrow_down:

cpp/src/gandiva/decimal_type_util.h
0% <0%> (-100%)
:arrow_down:

cpp/src/arrow/filesystem/util_internal.cc
0% <0%> (-100%)
:arrow_down:

cpp/src/arrow/compute/logical_type.h
0% <0%> (-100%)
:arrow_down:

cpp/src/parquet/hasher.h
0% <0%> (-100%)
:arrow_down:

... and 791 more

Continue to review full report at Codecov.

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


[W5][T12-1]Zhang Chenxi

I think you should add some tests!

Really nice enhancement! We can maybe use this enhancement for group related activities that we have in our mind for the final project.


Why were the {M, Un}arshalJSON Methods for Enums Removed in Proto3

Is appears like like the MarshalJSON and UnmarshalJSON methods for enums were removed in proto3 as evidence by this code.
What is the workaround for proto3? Currently I have to manually implement these methods.

The code you're referencing is on the gogo/protobuf repo.  Please file an issue there instead.

my apologies

@cybrcodr It appears like the same code exists in this project:
https://github.com/golang/protobuf/blob/master/protoc-gen-go/generator/generator.go#L1422-L1432
Do you know why these were removed? The blame says this was done for proto3 but I fail to see what is proto2 specific about it.

Perhaps this is why:
Examine this function:
https://github.com/golang/protobuf/blob/8d0c54c1246661d9a51ca0ba455d22116d485eaa/proto/lib.go#L473-L498
A comment says that the old style is that enums are ints and the new style is enums are strings. Maybe at one time, it was in the proposal to have enums as string for proto3. However, in proto3, enums are still ints.

Sorry, I'm not familiar with the history of these changes.
The jsonpb package in this repo provides the functionality for JSON marshaling and unmarshaling proto messages.

You're right that jsonpb only supports marshaling of proto.Message.  I believe that is intended and consistent with binary marshaling.
I'm not very familiar with the database driver interfaces, but seems like one will still need to write wrapper implementations for the Scanner and Valuer interfaces for proto enums.
Btw, the Go type for proto enum has been int32.  The jsonpb.Marshaler with default options will try to marshal an enum using its corresponding enum name but will marshal out an integer value if the value is unknown.


Problems with solutions and comments

Hey there!, Thanks for submitting a PR to this repo :smiley:
Please complete the following checklist for your PR to be approved. Mark the items by adding an x.
Example:  - [ ] Mark me as completed
To mark: - [x] Mark me as completed

[x] My Pull Request adheres to the Contribution guidelines.
[x] I have added problem.md and solution files in the appropriate folder
[x] In problem.md I have provided a correct link to the problem.
(In case you are not adding a problem, you can freely mark this as complete)
[x] My solution passes all the testcases within the given constraints.
[x] I have properly indented and documented my solution using comments.

If any of the above is unmarked, please make the necessary changes and then mark them so that you're PR can be approved and merged.
(Only completed checklist PRs will be reviewed)

@ArjunBhandari-666  Could you please rename the folder to just Math and Strings Problems

Duplicate of #359 . Closing this


Failed to run models with libtensorflow_jni and tensorflow text together

Please make sure that this is a build/installation issue. As per our GitHub Policy, we only address code/doc bugs, performance issues, feature requests and build/installation issues on GitHub. tag:build_template
System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04): CentOS7
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device: n/a
TensorFlow installed from (source or binary): source
TensorFlow version: 2.3.1
Python version:  n/a
Installed using virtualenv? pip? conda?: n/a
Bazel version (if compiling from source): 3.1.0
GCC/Compiler version (if compiling from source): gcc7
CUDA/cuDNN version: n/a
GPU model and memory: n/a

Describe the problem
Provide the exact sequence of commands / steps that you executed before running into the problem
When using libtensorflow_jni.so with tensorflow text, it crashes.
Same issue: https://github.com/tensorflow/java/issues/82
Any other info / logs
2021-02-17 19:20:45.283001: W tensorflow/core/framework/op_kernel.cc:1767] OP_REQUIRES failed at wordpiece_kernel.cc:204 : Invalid argument: Trying to access resource using the wrong type. Expected N10tensorflow6lookup15LookupInterfaceE got N10tensorflow6lookup15LookupInterfaceE

@liyinhgqw,
In order to expedite the trouble-shooting process, could you please provide the complete code to reproduce the issue reported here.
Also, please update TensorFlow to the latest stable version v2.4.1 and check if you are facing the same error. Thanks!


Incorrect database_path()

Larastan Version: latest
--level used: 1

Description
When analyzing a superior webshop https://github.com/thepinecode/bazar which is a Composer package, not an application database_path() returns vendor/orchestra/testbench-core/laravel/database/migrations thus no migration analysis takes place.
Laravel code where the issue was found
// in Larastan
ModelPropertyExtension::initializeTables()

Please advise.

After hard-wiring the path it works 🎉

This is maybe related to #507
Also if you are using the testbench package, maybe you can copy the migrations into the app testbench creates in the setUp method. Like we do here.

Thank you.


Audio logs for Android

Cross-requested with https://github.com/dimagi/opendatakit.collect/pull/55

@ctsims Changed seconds to ms. null vs -1 I think is a "six vs half-dozen" issue, so I left that alone.


Please include type_traits for std::is_trivial for older gcc

I met a compilation error on gcc 5:
include/ringbuffer.hpp:350:17: error: "is_trivial™ is not a member of "std™
   static_assert(std::is_trivial<T>::value, "non trivial objects will currently break");
                 ^
include/ringbuffer.hpp:350:34: error: expected primary-expression before ">™ token
   static_assert(std::is_trivial<T>::value, "non trivial objects will currently break");
                                  ^
include/ringbuffer.hpp:350:35: error: "::value" has not been declared
   static_assert(std::is_trivial<T>::value, "non trivial objects will currently break");
                                   ^

It is caused by lack of include <type_traits>.
This PR is to solve it.
PS: I know it is very trivial patch. So you can miss this PR and fix it on HEAD.

@jnk0le
Thanks a lot for your quick response!

That should not work even on a newer compilers, though i have missed it somehow.


Rename provide.system to provide.service in data_uses

Is your feature request related to a specific problem?
This is a simple one, but I’ve found that every time we explain the provide data use, we invariably want to say something like “…the provide use is the most common reason to collect user data, and it’s because you need their data to provide your product or service.” On top of these, we use the noun system in many places in fideslang (including as a top-level category in data_category) where it has a different meaning, so I feel it'd be more intuitive to not use the "system" terminology in the data_use taxonomy at all.
Describe the solution you'd like
Now, we have data uses like:

provide.system
provide.system.operations.support

After, we’d just rename these:

provide.service
provide.service.operations.support

Describe alternatives you've considered, if any
A description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

Combined with #58


 in blade

Hi, thanks for the package. I don't know if it's just me but when I use style in blade, the closing tag always adds one blank line before it.
Template
<style>
.some-background {
  background-color: red;
}
</style>

After formatting, it looks like this:
<style>
.some-background {
  background-color: red;
}

</style>

Context (Environment)
Version: 1.65.2
Plugin: 0.13.11
Laravel: 8.x
PHP: 8.x

@pkboom
I think this is because js-beautify, which is used internally, inserts whitespace in the style tag as well when the end-with-newline option is enabled.
I think this is an unexpected behavior so I'll look into it. Thanks.

Fixed at https://github.com/shufo/vscode-blade-formatter/releases/tag/v0.14.6


Added Home Security Cost Calculator

Fixes Issue🛠

Closes #981
Description👨💻

This project is inspired by the need for a simple tool to estimate home security system costs. No external dependencies are required for this project.
Type of change📄

[x] New feature (non-breaking change which adds functionality)

How this has been tested✅

This project has been tested on the following web browsers:

Google Chrome
Microsoft Edge

Checklist✅

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have added demonstration in the form of GIF/video file
[x] I am an Open Source Contributor

Screenshots/GIF📷

Pls rename your folder to Home-Security-Cost-Calculator and make the necessary changes in this same PR by making the commits.
Also, style and enhance the UI @Nikitakandwal

I have added the changes!

Merged 🎉 @Nikitakandwal


.hpp header not get std option from .mm source.

My .hpp header does not get std option from my .mm source.
For below case, it is -std=gnu++2a. So constructs in new standard do not work.
Logs
I[17:15:10.084] ASTWorker building file /Users/crupest/codes/cru/src/osx/gui/Window.mm version 1 with command
[/Users/crupest/codes/cru/build]
/usr/bin/clang++ --driver-mode=g++ -DCRU_DEBUG -DCRU_PLATFORM_OSX -Dcru_osx_gui_EXPORTS -I/Users/crupest/codes/cru/include -isystem /Users/crupest/codes/cru/build/vcpkg_installed/x64-osx/include -g -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX12.1.sdk -fPIC -std=gnu++2a -o src/osx/gui/CMakeFiles/cru_osx_gui.dir/Window.mm.o -c -resource-dir=/usr/local/Cellar/llvm/13.0.1/lib/clang/13.0.1 -- /Users/crupest/codes/cru/src/osx/gui/Window.mm

I[17:15:35.056] ASTWorker building file /Users/crupest/codes/cru/include/cru/osx/gui/Window.hpp version 1 with command inferred from /Users/crupest/codes/cru/src/osx/gui/Window.mm
[/Users/crupest/codes/cru/build]
/usr/bin/clang++ --driver-mode=g++ -DCRU_DEBUG -DCRU_PLATFORM_OSX -Dcru_osx_gui_EXPORTS -I/Users/crupest/codes/cru/include -isystem /Users/crupest/codes/cru/build/vcpkg_installed/x64-osx/include -g -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX12.1.sdk -fPIC -c -resource-dir=/usr/local/Cellar/llvm/13.0.1/lib/clang/13.0.1 /Users/crupest/codes/cru/include/cru/osx/gui/Window.hpp

System information
Output of clangd --version:
Homebrew clangd version 13.0.1
Features: mac+xpc
Platform: x86_64-apple-darwin21.3.0

Editor/LSP plugin: VS Code
Operating system: macOS 12.2

I suspect this is related to the inferred language being different.
Is it correct that your header file is plain C++, and your implementation is Objective-C++?
AFAIK, *.hpp is not an extension used for Obj-C, see e.g. GCC docs, clang tables

Thank you for quick response.
I use a mixed C++ and Obj-C++ code. The .hpp header is included both in C++ (.cpp) and Obj-C++(.mm). When its compile options get inferred from C++, it works fine. However when it is inferred from Obj-C++, the std option is get rid of.
Thank you for pointing out .hpp is not used for Obj-C++. So there might be some problems for my file naming. I wonder whether you guys consider this a bug or not.
And here is logs with --log=verbose. Hope you can find more useful info.
I[17:42:06.741] <-- textDocument/codeAction(9)
V[17:42:06.741] <<< {"id":10,"jsonrpc":"2.0","method":"textDocument/documentLink","params":{"textDocument":{"uri":"file:///Users/crupest/codes/cru/include/cru/osx/gui/Window.hpp"}}}

I[17:42:06.741] <-- textDocument/documentLink(10)
V[17:42:06.741] <<< {"id":11,"jsonrpc":"2.0","method":"textDocument/documentSymbol","params":{"textDocument":{"uri":"file:///Users/crupest/codes/cru/include/cru/osx/gui/Window.hpp"}}}

I[17:42:06.741] <-- textDocument/documentSymbol(11)
V[17:42:06.742] ASTWorker running EnumerateTweaks on version 1 of /Users/crupest/codes/cru/include/cru/osx/gui/Window.hpp
I[17:42:06.742] --> reply:textDocument/codeAction(9) 0 ms
V[17:42:06.742] >>> {"id":9,"jsonrpc":"2.0","result":[]}

V[17:42:06.742] ASTWorker running DocumentLinks on version 1 of /Users/crupest/codes/cru/include/cru/osx/gui/Window.hpp
I[17:42:06.742] --> reply:textDocument/documentLink(10) 0 ms
V[17:42:06.742] >>> {"id":10,"jsonrpc":"2.0","result":[{"range":{"end":{"character":23,"line":1},"start":{"character":9,"line":1}},"target":"file:///Users/crupest/codes/cru/include/cru/osx/gui/Resource.hpp"},{"range":{"end":{"character":36,"line":2},"start":{"character":9,"line":2}},"target":"file:///Users/crupest/codes/cru/include/cru/platform/gui/Base.hpp"},{"range":{"end":{"character":43,"line":3},"start":{"character":9,"line":3}},"target":"file:///Users/crupest/codes/cru/include/cru/platform/gui/InputMethod.hpp"},{"range":{"end":{"character":38,"line":4},"start":{"character":9,"line":4}},"target":"file:///Users/crupest/codes/cru/include/cru/platform/gui/Window.hpp"},{"range":{"end":{"character":17,"line":6},"start":{"character":9,"line":6}},"target":"file:///Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/c%2B%2B/v1/memory"}]}

V[17:42:06.742] ASTWorker running DocumentSymbols on version 1 of /Users/crupest/codes/cru/include/cru/osx/gui/Window.hpp
I[17:42:06.743] --> reply:textDocument/documentSymbol(11) 2 ms
V[17:42:06.748] >>> {"id":11,"jsonrpc":"2.0","result":[{"children":[{"children":[{"children":[{"children":[{"children":[{"detail":"class","kind":5,"name":"OsxWindowPrivate","range":{"end":{"character":22,"line":10},"start":{"character":0,"line":10}},"selectionRange":{"end":{"character":22,"line":10},"start":{"character":6,"line":10}}},{"detail":"class","kind":5,"name":"OsxInputMethodContextPrivate","range":{"end":{"character":34,"line":11},"start":{"character":0,"line":11}},"selectionRange":{"end":{"character":34,"line":11},"start":{"character":6,"line":11}}}],"kind":3,"name":"details","range":{"end":{"character":1,"line":12},"start":{"character":0,"line":9}},"selectionRange":{"end":{"character":17,"line":9},"start":{"character":10,"line":9}}},{"detail":"class","kind":5,"name":"OsxUiApplication","range":{"end":{"character":22,"line":14},"start":{"character":0,"line":14}},"selectionRange":{"end":{"character":22,"line":14},"start":{"character":6,"line":14}}},{"detail":"class","kind":5,"name":"OsxInputMethodContext","range":{"end":{"character":27,"line":15},"start":{"character":0,"line":15}},"selectionRange":{"end":{"character":27,"line":15},"start":{"character":6,"line":15}}},{"children":[{"detail":"(OsxUiApplication *)","kind":9,"name":"OsxWindow","range":{"end":{"character":45,"line":22},"start":{"character":2,"line":22}},"selectionRange":{"end":{"character":11,"line":22},"start":{"character":2,"line":22}}},{"children":[{"detail":"(const OsxWindow &)","kind":9,"name":"OsxWindow","range":{"end":{"character":27,"line":24},"start":{"character":2,"line":24}},"selectionRange":{"end":{"character":27,"line":24},"start":{"character":18,"line":24}}},{"detail":"OsxWindow &(const OsxWindow &)","kind":6,"name":"operator=","range":{"end":{"character":27,"line":24},"start":{"character":2,"line":24}},"selectionRange":{"end":{"character":17,"line":24},"start":{"character":2,"line":24}}}],"detail":"(OsxWindow)","kind":21,"name":"CRU_DELETE_COPY","range":{"end":{"character":28,"line":24},"start":{"character":2,"line":24}},"selectionRange":{"end":{"character":17,"line":24},"start":{"character":2,"line":24}}},{"children":[{"detail":"(OsxWindow &&)","kind":9,"name":"OsxWindow","range":{"end":{"character":27,"line":25},"start":{"character":2,"line":25}},"selectionRange":{"end":{"character":27,"line":25},"start":{"character":18,"line":25}}},{"detail":"OsxWindow &(OsxWindow &&)","kind":6,"name":"operator=","range":{"end":{"character":27,"line":25},"start":{"character":2,"line":25}},"selectionRange":{"end":{"character":17,"line":25},"start":{"character":2,"line":25}}}],"detail":"(OsxWindow)","kind":21,"name":"CRU_DELETE_MOVE","range":{"end":{"character":28,"line":25},"start":{"character":2,"line":25}},"selectionRange":{"end":{"character":17,"line":25},"start":{"character":2,"line":25}}},{"kind":9,"name":"~OsxWindow","range":{"end":{"character":23,"line":27},"start":{"character":2,"line":27}},"selectionRange":{"end":{"character":3,"line":27},"start":{"character":2,"line":27}}},{"detail":"void ()","kind":6,"name":"Close","range":{"end":{"character":23,"line":30},"start":{"character":2,"line":30}},"selectionRange":{"end":{"character":12,"line":30},"start":{"character":7,"line":30}}},{"detail":"INativeWindow *()","kind":6,"name":"GetParent","range":{"end":{"character":37,"line":32},"start":{"character":2,"line":32}},"selectionRange":{"end":{"character":26,"line":32},"start":{"character":17,"line":32}}},{"detail":"void (INativeWindow *)","kind":6,"name":"SetParent","range":{"end":{"character":48,"line":33},"start":{"character":2,"line":33}},"selectionRange":{"end":{"character":16,"line":33},"start":{"character":7,"line":33}}},{"detail":"WindowStyleFlag ()","kind":6,"name":"GetStyleFlag","range":{"end":{"character":41,"line":35},"start":{"character":2,"line":35}},"selectionRange":{"end":{"character":30,"line":35},"start":{"character":18,"line":35}}},{"detail":"void (WindowStyleFlag)","kind":6,"name":"SetStyleFlag","range":{"end":{"character":50,"line":36},"start":{"character":2,"line":36}},"selectionRange":{"end":{"character":19,"line":36},"start":{"character":7,"line":36}}},{"detail":"String ()","kind":6,"name":"GetTitle","range":{"end":{"character":28,"line":38},"start":{"character":2,"line":38}},"selectionRange":{"end":{"character":17,"line":38},"start":{"character":9,"line":38}}},{"detail":"void (String)","kind":6,"name":"SetTitle","range":{"end":{"character":38,"line":39},"start":{"character":2,"line":39}},"selectionRange":{"end":{"character":15,"line":39},"start":{"character":7,"line":39}}},{"detail":"WindowVisibilityType ()","kind":6,"name":"GetVisibility","range":{"end":{"character":47,"line":41},"start":{"character":2,"line":41}},"selectionRange":{"end":{"character":36,"line":41},"start":{"character":23,"line":41}}},{"detail":"void (WindowVisibilityType)","kind":6,"name":"SetVisibility","range":{"end":{"character":62,"line":42},"start":{"character":2,"line":42}},"selectionRange":{"end":{"character":20,"line":42},"start":{"character":7,"line":42}}},{"detail":"Size ()","kind":6,"name":"GetClientSize","range":{"end":{"character":31,"line":44},"start":{"character":2,"line":44}},"selectionRange":{"end":{"character":20,"line":44},"start":{"character":7,"line":44}}},{"detail":"void (const Size &)","kind":6,"name":"SetClientSize","range":{"end":{"character":47,"line":45},"start":{"character":2,"line":45}},"selectionRange":{"end":{"character":20,"line":45},"start":{"character":7,"line":45}}},{"detail":"Rect ()","kind":6,"name":"GetClientRect","range":{"end":{"character":31,"line":47},"start":{"character":2,"line":47}},"selectionRange":{"end":{"character":20,"line":47},"start":{"character":7,"line":47}}},{"detail":"void (const Rect &)","kind":6,"name":"SetClientRect","range":{"end":{"character":47,"line":48},"start":{"character":2,"line":48}},"selectionRange":{"end":{"character":20,"line":48},"start":{"character":7,"line":48}}},{"detail":"Rect ()","kind":6,"name":"GetWindowRect","range":{"end":{"character":31,"line":50},"start":{"character":2,"line":50}},"selectionRange":{"end":{"character":20,"line":50},"start":{"character":7,"line":50}}},{"detail":"void (const Rect &)","kind":6,"name":"SetWindowRect","range":{"end":{"character":47,"line":51},"start":{"character":2,"line":51}},"selectionRange":{"end":{"character":20,"line":51},"start":{"character":7,"line":51}}},{"detail":"bool ()","kind":6,"name":"RequestFocus","range":{"end":{"character":30,"line":53},"start":{"character":2,"line":53}},"selectionRange":{"end":{"character":19,"line":53},"start":{"character":7,"line":53}}},{"detail":"Point ()","kind":6,"name":"GetMousePosition","range":{"end":{"character":35,"line":55},"start":{"character":2,"line":55}},"selectionRange":{"end":{"character":24,"line":55},"start":{"character":8,"line":55}}},{"detail":"bool ()","kind":6,"name":"CaptureMouse","range":{"end":{"character":30,"line":57},"start":{"character":2,"line":57}},"selectionRange":{"end":{"character":19,"line":57},"start":{"character":7,"line":57}}},{"detail":"bool ()","kind":6,"name":"ReleaseMouse","range":{"end":{"character":30,"line":58},"start":{"character":2,"line":58}},"selectionRange":{"end":{"character":19,"line":58},"start":{"character":7,"line":58}}},{"detail":"void (std::shared_ptr<ICursor>)","kind":6,"name":"SetCursor","range":{"end":{"character":58,"line":60},"start":{"character":2,"line":60}},"selectionRange":{"end":{"character":16,"line":60},"start":{"character":7,"line":60}}},{"detail":"void ()","kind":6,"name":"SetToForeground","range":{"end":{"character":33,"line":62},"start":{"character":2,"line":62}},"selectionRange":{"end":{"character":22,"line":62},"start":{"character":7,"line":62}}},{"detail":"void ()","kind":6,"name":"RequestRepaint","range":{"end":{"character":32,"line":64},"start":{"character":2,"line":64}},"selectionRange":{"end":{"character":21,"line":64},"start":{"character":7,"line":64}}},{"detail":"std::unique_ptr<graphics::IPainter> ()","kind":6,"name":"BeginPaint","range":{"end":{"character":59,"line":66},"start":{"character":2,"line":66}},"selectionRange":{"end":{"character":48,"line":66},"start":{"character":38,"line":66}}},{"detail":"IEvent<std::nullptr_t> *()","kind":6,"name":"CreateEvent","range":{"end":{"character":48,"line":68},"start":{"character":2,"line":68}},"selectionRange":{"end":{"character":37,"line":68},"start":{"character":26,"line":68}}},{"detail":"IEvent<std::nullptr_t> *()","kind":6,"name":"DestroyEvent","range":{"end":{"character":49,"line":69},"start":{"character":2,"line":69}},"selectionRange":{"end":{"character":38,"line":69},"start":{"character":26,"line":69}}},{"detail":"IEvent<std::nullptr_t> *()","kind":6,"name":"PaintEvent","range":{"end":{"character":47,"line":70},"start":{"character":2,"line":70}},"selectionRange":{"end":{"character":36,"line":70},"start":{"character":26,"line":70}}},{"detail":"IEvent<WindowVisibilityType> *()","kind":6,"name":"VisibilityChangeEvent","range":{"end":{"character":64,"line":72},"start":{"character":2,"line":72}},"selectionRange":{"end":{"character":53,"line":72},"start":{"character":32,"line":72}}},{"detail":"IEvent<Size> *()","kind":6,"name":"ResizeEvent","range":{"end":{"character":38,"line":73},"start":{"character":2,"line":73}},"selectionRange":{"end":{"character":27,"line":73},"start":{"character":16,"line":73}}},{"detail":"IEvent<FocusChangeType> *()","kind":6,"name":"FocusEvent","range":{"end":{"character":48,"line":74},"start":{"character":2,"line":74}},"selectionRange":{"end":{"character":37,"line":74},"start":{"character":27,"line":74}}},{"detail":"IEvent<MouseEnterLeaveType> *()","kind":6,"name":"MouseEnterLeaveEvent","range":{"end":{"character":62,"line":76},"start":{"character":2,"line":76}},"selectionRange":{"end":{"character":51,"line":76},"start":{"character":31,"line":76}}},{"detail":"IEvent<Point> *()","kind":6,"name":"MouseMoveEvent","range":{"end":{"character":42,"line":77},"start":{"character":2,"line":77}},"selectionRange":{"end":{"character":31,"line":77},"start":{"character":17,"line":77}}},{"detail":"IEvent<NativeMouseButtonEventArgs> *()","kind":6,"name":"MouseDownEvent","range":{"end":{"character":63,"line":78},"start":{"character":2,"line":78}},"selectionRange":{"end":{"character":52,"line":78},"start":{"character":38,"line":78}}},{"detail":"IEvent<NativeMouseButtonEventArgs> *()","kind":6,"name":"MouseUpEvent","range":{"end":{"character":61,"line":79},"start":{"character":2,"line":79}},"selectionRange":{"end":{"character":50,"line":79},"start":{"character":38,"line":79}}},{"detail":"IEvent<NativeMouseWheelEventArgs> *()","kind":6,"name":"MouseWheelEvent","range":{"end":{"character":63,"line":80},"start":{"character":2,"line":80}},"selectionRange":{"end":{"character":52,"line":80},"start":{"character":37,"line":80}}},{"detail":"IEvent<NativeKeyEventArgs> *()","kind":6,"name":"KeyDownEvent","range":{"end":{"character":53,"line":81},"start":{"character":2,"line":81}},"selectionRange":{"end":{"character":42,"line":81},"start":{"character":30,"line":81}}},{"detail":"IEvent<NativeKeyEventArgs> *()","kind":6,"name":"KeyUpEvent","range":{"end":{"character":51,"line":82},"start":{"character":2,"line":82}},"selectionRange":{"end":{"character":40,"line":82},"start":{"character":30,"line":82}}},{"detail":"IInputMethodContext *()","kind":6,"name":"GetInputMethodContext","range":{"end":{"character":55,"line":84},"start":{"character":2,"line":84}},"selectionRange":{"end":{"character":44,"line":84},"start":{"character":23,"line":84}}},{"detail":"std::unique_ptr<details::OsxWindowPrivate>","kind":8,"name":"p_","range":{"end":{"character":47,"line":87},"start":{"character":2,"line":87}},"selectionRange":{"end":{"character":47,"line":87},"start":{"character":45,"line":87}}}],"detail":"class","kind":5,"name":"OsxWindow","range":{"end":{"character":1,"line":88},"start":{"character":0,"line":17}},"selectionRange":{"end":{"character":15,"line":17},"start":{"character":6,"line":17}}}],"kind":3,"name":"osx","range":{"end":{"character":1,"line":89},"start":{"character":28,"line":8}},"selectionRange":{"end":{"character":33,"line":8},"start":{"character":30,"line":8}}}],"kind":3,"name":"gui","range":{"end":{"character":1,"line":89},"start":{"character":23,"line":8}},"selectionRange":{"end":{"character":28,"line":8},"start":{"character":25,"line":8}}}],"kind":3,"name":"platform","range":{"end":{"character":1,"line":89},"start":{"character":13,"line":8}},"selectionRange":{"end":{"character":23,"line":8},"start":{"character":15,"line":8}}}],"kind":3,"name":"cru","range":{"end":{"character":1,"line":89},"start":{"character":0,"line":8}},"selectionRange":{"end":{"character":13,"line":8},"start":{"character":10,"line":8}}}]}

I[17:42:06.750] --> textDocument/clangd.fileStatus
V[17:42:06.750] >>> {"jsonrpc":"2.0","method":"textDocument/clangd.fileStatus","params":{"state":"idle","uri":"file:///Users/crupest/codes/cru/include/cru/osx/gui/Window.hpp"}}

V[17:42:06.920] <<< {"id":12,"jsonrpc":"2.0","method":"textDocument/codeAction","params":{"context":{"diagnostics":[]},"range":{"end":{"character":17,"line":6},"start":{"character":17,"line":6}},"textDocument":{"uri":"file:///Users/crupest/codes/cru/include/cru/osx/gui/Window.hpp"}}}

I[17:42:06.920] <-- textDocument/codeAction(12)
V[17:42:06.920] ASTWorker running EnumerateTweaks on version 1 of /Users/crupest/codes/cru/include/cru/osx/gui/Window.hpp
I[17:42:06.920] --> reply:textDocument/codeAction(12) 0 ms
V[17:42:06.920] >>> {"id":12,"jsonrpc":"2.0","result":[]}

I[17:42:06.920] --> textDocument/clangd.fileStatus
V[17:42:06.920] >>> {"jsonrpc":"2.0","method":"textDocument/clangd.fileStatus","params":{"state":"idle","uri":"file:///Users/crupest/codes/cru/include/cru/osx/gui/Window.hpp"}}

I think this is a bug, including a C++ header from ObjC++ is perfectly valid so we should try to produce a sensible set of flags.
The compile-command-transfer logic is treating the -std option as language-specific, which makes sense for C vs C++ but not for ObjC[++] vs C[++].


Background Animation

background animation, with cascading lines, adds a sleek, modern look to BitBox. It creates a dynamic backdrop that enhances the overall user experience without distracting from the content.

Can you give me sample @sv410?

Can you give star to the repo?


Error in AppVeyor CI because NUPKG is not produced

An error is occurring at the end of the AppVeyor CI build process. It appears that the build is not producing the Nuget package:

Took a few minutes to poke at this.
When I run this on my local machine I can't actually reproduce it.  If you look at the image you can see all of the produced files are appended with <IP_ADDRESS>.

However the nupkg file does not have the final .0 - why is beyond me. I set $env:AppVeyor_Build_Version on my local machine to match it produces the file correctly.

The way I see it we have to quick/dirty ways to fix.

Modify this line to not include the build number. I have no idea what that breaks but doesn't seem great to me.
Modify the next line to not specify the exact file name but filter on all nukpg files. ie:

    Get-ChildItem -Path "$env:APPVEYOR_BUILD_FOLDER" -Filter '*.nupkg' | ForEach-Object -Process {
        Push-AppveyorArtifact $_.FullName -FileName $_.Name
    }

Downside with this one is we now upload all nupkg files which means if we generate more then the one we might end up with more then we intend. Not sure really.

@tysonjhayes - I think I've found the problem:

Nuget.exe v<IP_ADDRESS>8: This is the version downloaded by AppVeyor by this line. It produces a NUPKG with the trailing 0 stripped off.

Nuget.exe v<IP_ADDRESS>8: This is the version I have on my machine - came with VS2015. It produces a NUPKG with the trailing 0 retained.

So it looks like this is a behaviour that is implemented in Nuget 3.5 - although I haven't been able to find any specific mention of it.
I did a quick test and downloaded the 3.4.4 Nuget.exe from https://dist.nuget.org/win-x86-commandline/v3.4.4/NuGet.exe and gave that a try. It retains the trailing 0.
So I think the solution might be to specify the 3.4.4 version of Nuget.exe in the AppVeyor.yml:
 - appveyor DownloadFile https://dist.nuget.org/win-x86-commandline/v3.4.4/NuGet.exe

Whatcha reckon?

I got the same error over at xSQLServer. So I wait to see what your solution is a do the same :)
In the appveyor.yml in xSQLServer it is specified a minimum version, so I could also change that to a specific version.
@PlagueHO great work finding that!

Hmm.. in xSQLServer its using Install-PackageProvider so I guess I have to change the entire row to solve this one.
But strangely this started happen on the December 31, on December 28 the build was passing, but from December 31 that the error appears. And the same version of package provider is being used. I guess some internals was changed.
I will try @PlagueHO solution this evening.

I have tested a bit...
When using "my own" AppVeyor connected to my fork of xSQLServer it fails when I push to my fork. In these two tests I printed out the version of the Nuget.exe. In the last I also printed the nuspec to see if it contained the right version. It did.
Failed with Nuget v<IP_ADDRESS>1:
https://ci.appveyor.com/project/johlju/xsqlserver/build/4.0.315.0#L4551
Failed with Nuget v<IP_ADDRESS>5
https://ci.appveyor.com/project/johlju/xsqlserver/build/4.0.316.0#L4015
But if I actually send in a PR to xSQLServer then it is working without any change to the .yml. Becuse it does not do the build step I guess:
https://ci.appveyor.com/project/PowerShell/xsqlserver/build/4.0.734.0#L3631
But when I merge code into 'dev' it is failing again (without any change to the .yml)
https://ci.appveyor.com/project/PowerShell/xsqlserver/build/4.0.730.0
I would liek to see this working on my fork before merging any changes into dev. I can't get the 3.4.x version to work either.
So only way I see now is actually removing the last '.0', or filter on "$($env:APPVEYOR_PROJECT_NAME)*.nupkg" as @tysonjhayes suggest.
One thought though. Is there a nuget.exe somewhere in the build worker that is used, and not the one downloaded to the project folder 🤔

@johlju - that is very odd! I'm looking into this further. Great investigation!
FYI: I think the last two links are transposed (the last one shows a successful run because the build is skipped, but the second to last is failing because of the missing .0).

If I change the .yml to the following it works; https://ci.appveyor.com/project/johlju/xsqlserver/build/4.0.318.0#L4046
      $nuGetPackageName = "$($env:APPVEYOR_PROJECT_NAME)*.nupkg"
      $nuGetPackagePath = (Get-ChildItem $nuGetPackageName).FullName

But then I tried to force it to use the nuget.exe in the project folder. And it WORKED!
https://ci.appveyor.com/project/johlju/xsqlserver/build/4.0.319.0#L4003
& "$($env:APPVEYOR_BUILD_FOLDER)\nuget" pack ".\$($env:APPVEYOR_PROJECT_NAME).nuspec" -outputdirectory .

@PlagueHO @tysonjhayes Can you see if this works for you as well? If so then there is a nuget.exe in the build worker that messes things up... maybe?
Do I get a local nuget.exe from Install-PackageProvider? 🤔 I will try to revert the code and see.

I notice SharePointDsc uses the "latest" URL for Nuget.exe as well. But it doesn't look like it has been changed/rebuilt since mid Dec last year. @BrianFarnhill - have you by any chance run across this issue (Nuget stripping off .0 from end of the version number in the NUPKG filename).

@johlju - good detective work! There is a Nuget.exe installed by default in the AppVeyor build worker. I'm not sure which version though.
However, in xNetworking (and SharePointDsc) one of the first steps we perform is to download a the latest copy of Nuget.exe from Nuget.org into the build folder. However, we use this code to perform the Nuget Pack. So I'm not certain which copy is being used here - I'd actually like to refine this code so we are enforcing the copy being used.
You are right: It does sound like this is just a situation where multiple copies of Nuget.exe end up being available and more care and control needs to be put in to ensure the correct (3.4.4) version is being used.

Yes, I need to change so that nuget.exe is download like you do, and using the correct version. Using the current Install-PackageProvider install the package in other folders.
I did see that you are using Install-PackageProvider too here.
I tested with the latest nuget.exe and using the code that "force" using the one downloaded. It did not work (as you said it wouldn't).
So changing back to 3.4.4 now and using the same way of starting nuget.exe as you (Start-Process). But I do it from the .yml file still.
I feel comfortable that this is the solution. But I will monitor here if you find a better solution. 😄

I think the Install-PackageProvider cmdlet only downloads and installs the Nuget Provider assemblies to C:\Program Files\PackageManagement\ProviderAssemblies\nuget - not Nuget.exe itself - but I could be wrong here.
Good to hear it is working! I'm going to submit a PR through here but perform the entire change within the AppVeyor.psm1 file because I think having it out in the AppVeyor.yml leaves it open to problems. Also, as the AppVeyor.psm1 file is also being moved over to DSCResource.Tests (and generalized) to be used by all DSC Resources it makes sense to ensure the dependencies are correctly downloaded.

Yes, I agree. I do it in .yml because I'm not there yet with AppVeyor.psm1. :) I think I wait and see what you guys put together first in DSCResources.Tests.
Side note: I did some work during the holidays to implement AppVeyor.psm1 (based on @tysonjhayes work here), but at the end I did not send in the PR to xSQLServer, still have it though. But I did take some bits an pieces which ended up in a common test here; https://github.com/PowerShell/xSQLServer/blob/dev/Tests/xSQLServerCommon.Tests.ps1.
It has helped tremendously to find bugs!

@PlagueHO I haven't noticed it, but I did just have 4 weeks of leave after a fairly hectic run up to Christmas so I haven't been paying as much attention as I should be, so I'll get back in and have a look when I get a minute.

@BrianFarnhill - thank pal!
@tysonjhayes, @johlju - I'm going to fix this issue when I implement support for https://github.com/PowerShell/DscResources/issues/205 in this resource module. I've added code in DSCResource.Tests to ensure a known Nuget.exe is downloaded and used in every case (rather than whatever is found in the build worker).

@PlagueHO Sounds great!

@johlju - I've just finished the changes to DSCResource.Tests and have so far tested it with xNetworking, xDFS and I'm in process of testing it with SharePointDsc and xSQLServer.
Forcing the use of a specific Nuget.exe (which the new AppVeyor.psm1 downloads the $ENV:Temp) resolves the version number NUPKG issue.
Once I've completed the tests on xSQLServer and SharePointDsc with this new AppVeyor.yml I'll submit the PR to DSCResource.Tests. Once that is through I can submit the PR's to each repo (xNetworking, xSQLServer, SharePointDsc and xDFS) to bring them over to using the AppVeyor.psm1.
The changes are pretty minimal (you can see the xDFS ones here: https://github.com/PlagueHO/xDFS/blob/Use-AppVeyor-Module/appveyor.yml). It is cloning DSCResource.Tests from my repo at the moment (so I can test).

@PlagueHO Awesome work! 👍  Looking forward getting this to xSQLServer as well, so your PR a welcomed! 😄

@tysonjhayes - I've fixed this issue in the PR to move AppVeyor.psm1 over to DSCResource.Tests. Once that is through we can update xNetworking to use it (I've got the PR ready to go). This will fix the Nuget.exe problem.

@kwirkykat - xNetworking is scheduled for release next week, but this issue is currently blocking release. The fix is contained in the PR I submitted to DSCResource.Tests (https://github.com/PowerShell/DscResource.Tests/pull/84). Let me know if you think the change to DSCResource.Tests won't be merged in time and I'll see about cross-porting the fix for this - although I'd rather avoid it if possible.
Once the PR for DSCResource.Tests has gone through, there will still need to be a PR merged into this repo as well. So the timing might be tight.

@PlagueHO I can release xNetworking whenever it's ready in-between main DSC Resource Kit releases if this doesn't get done by Wednesday.
But also, we don't actually release the package that AppVeyor creates right now. We probably should (so it's really good this is getting fixed 👍 ), but right now we don't. We clone the repo locally and then just call Publish-Module on the cloned module's path. So I could still release it on Wednesday even with this bug if you'd like.

If this isn't blocking release then ship it! Well get it patched up but no sense in blocking release.

@tysonjhayes - doh! I though I responded to this last night (must have not clicked comment). But yep I reckon we can definitely release this.


feat(proxy): support environment http_proxy and https_proxy

I have signed the CLA.

Thank you. Could you give some background on why this should be added to karma directly?

@dignifiedquire
I was trying to proxy a remote URL from Karma, but it was unable to resolve the remote hostname because it was not reading my system's proxy settings correctly.  This fixes that issue.
I'm not sure that it would be possible to add it externally as the proxy object is not exposed or exported by the API.  Also, reading it from the environment is preferable because it's not a part of the test configuration - I would want to use the upstream proxy settings of wherever I am running my tests.  (E.g., running Karma from my office requires different proxy settings than running it from my home, and those settings are specific to where the tests are being run, not what is being tested.)

I called it a feature because it's doing something new that it wasn't doing it before, and a new flag was added to opt-out.
From another perspective, though, it is a bug fix.  It fixes the issue that Karma does not honor the system proxy of the environment it is running it.

@errorx666 sounds good, left one comment other than that looks good

As this is more than two years old, please try a new PR against current master.


Bug fix: remote mode errors out with bad backend type

Due to code reorg, the config must now be parsed via
subnet.ParseConfig in remote client.

LGTM


Make default values things that are available in maven central

👍

@zzl0 fyi, I haven't updated master with this patch yet because 0.9.1-SNAPSHOT isn't in maven central anyways.


Test cross-compilation with stable gnullvm targets

Continuation of https://github.com/microsoft/windows-rs/pull/3007 but this time with a stable toolchain.

It looks like a preinstalled stable toolchain was not yet updated to the latest version.

When do you expect that to be updated?

Judging by the history of https://github.com/actions/runner-images/blob/main/images/ubuntu/Ubuntu2204-Readme.md, I'd expect it to happen today, but I don't have the details on how GitHub updates their images.

Rather than wait for GitHub, which might be busy/frozen due to events this week, can we just update the tools at start of the workflow (like we already do)?

If this fails again, I'll look into incorporating changes from other workflows to make sure Rust is up to date.

I don't know if this is related but GNU builds have started failing:
https://github.com/microsoft/windows-rs/actions/runs/9567088234/job/26373942886

It looks like a Windows Server 2022 update is currently in progress so it shouldn't be too long now.

Even though GHA docs were updated yesterday so the compiler should be up-to-date now I added the step to update the toolchain like in the other jobs.

It looks like a Windows Server 2022 update is currently in progress so it shouldn't be too long now.

That's good, I guess?
Don't know how it's related, though.

I don't know if this is related but GNU builds have started failing:
microsoft/windows-rs/actions/runs/9567088234/job/26373942886

It uses GHA image 20240610.1.0 so it's unlikely to be related. Probably something in nightly or rustup. Maybe it's related to https://github.com/rust-lang/rust/issues/125809?

Ah, forgot about Mac.
Added if: startsWith(matrix.image, 'ubuntu-') && contains(matrix.target, 'gnullvm') || endsWith(matrix.target, 'gnu') to Test step so the tests for gnullvm won't run there, but it's still not ideal since there are 3 macos gnullvm jobs that basically do checkout exit with success.
Still, it's an improvement compared to the master branch, so good to go?

Hmm, just noticed those unused mac tests. We can clean those up separately.


[Suggestion] New App Icon

Hi! I find this app really useful so I decided to contribute. As you may have noticed, simple and minimalist icons are trending right now. Thus, here are my suggestions for the  app icon in order to give it a modern look and a brand identity. These icons combine symbol for "notification" (bell) and " human e-voice" which well-represent what this app is capable of.  What do you think? I'll be happy to make adjustments.

Glad you like it.  Will it be okay to send the vectors and files via pull request? If you have further suggestions, please let me know.

Glad you like it. I made some blue/cyan variations as you mentioned. Which one do you prefer? I will upload the vectors and png files of your final pick.

Great! I  uploaded the vectors and exports in a google drive which you can access here with included license. Thank you for the opportunity to contribute to this project.
This work is licensed under a Creative Commons Attribution 4.0 International License.

The third blue is best for me. But I love also your old.


How to account for singular/plural formatting?

Let's say I have the following:
moment.duration(121, "minutes").format("h [hrs], m [min]");
which outputs: 2 hrs, 1 min
but If I have
moment.duration(90, "minutes").format("h [hrs], m [min]");
then I get: 1 hrs, 30 min
Ideally, I'd get: 1 hr, 30 mins instead of 1 hrs, 30 min
How can I account for singular/plural forms of "hr/hrs" and "min/mins"?
Is there a way to regex or otherwise format to accomplish this?

This was my workaround, but I would have expected there to be a way to do this without having to do the formatting logic myself:
`convertMinutes(mins) {
let hours = Math.floor(mins / 60);
let minutes = mins % 60;
    if (hours < 1) {
        hours = "";
    } else if (hours == 1) {
        hours = hours + " hr, ";
    } else {
        hours = hours + " hrs, ";
    }

    if (minutes < 1) {
        minutes = "";
    } else if (minutes == 1) {
        minutes = minutes + " min";
    } else {
        minutes = minutes + " mins";
    }

    let time = hours + minutes;

    return time;
}`

Looks like #38 will handle this.

Can you close this, so everybody can focus on #38?

I've pushed a new version of the plugin to the master branch. It's labeled as version 2.0.0b1 in the js file.
This version implements largest as well as trim: "both" (which can be used in conjunction with largest).
This version also extends the moment en locale so that duration unit strings will be auto-singularized. e.g. instead of outputting 1 minutes or 1 mins, the plugin will now automatically output 1 minute or 1 min.
Basic documentation for the new options can be found in the js file in the default options section. I'll add documentation to the readme in the next few days.
Once I've done that, added a few more tests, and reviewed the other open issues, I'll publish version 2.0.0.
Closing this as suggested.

Fixed in 6d2ff9e7779a62da620649810a24f11770fd07ff.


sync with zenodo

https://coderefinery.github.io/github-without-command-line/doi/#step-2-activate-the-repository-on-zenodo-sandbox

done


Dereferencing an exported (0 :: Int) fails

Int prim type is represented as JavaScript integer, so this check in h$derefExport wrongfully fails:
if (!e.root) return null;

Same problem with anything that is represented in JavaScript as a falsy value (false, undefined, empty string).

good point. keep in mind that you can only export lifted values though, these are always either a number, a boolean or a heap object. but this is indeed wrong, and a bit tricky to reproduce even.

I didn't have any trouble reproduce it ;)
main = withExport (0 :: Int) $ \r -> do
        v <- derefExport r
        print (v :: Maybe Int)

prints "Nothing".

It's easy to export the unevaluated version instead, and if GHC floats it to the top level it also becomes boxed again, and therefore truthy.
I've fixed it now and added it to the test case.