[8pt] GUID for HydroIDs

The structure of HydroVIS's database calls for this so they don't have to do multi-indexing on branches and HUCs. Please make sure that the GUID is a new column in all hydroTables and the crosswalk_table.csv in the root FIM output folder.

@TylerSchrag-NOAA Please add a comment here if I'm missing any details...

Thank you @CarsonPruitt-NOAA !
Yes, it would be helpful on our side to have a unique ID for feature_id, hydro_id, branch_id, and huc8 combinations. I'm guessing this could essentially be a hash of those combined values.
This would allow us to index the complete set of hydrotables by this new unique id + stage.

I could foresee that including both feature_id and hydro_id in the GUID could be problematic since the feature_id for a particular hydro_id is not necessarily unique and might change with the crosswalking technique being used even though the stream reaches haven't changed. Also, we will still have a crosswalk table that connects a feature_id to each hydro_id.
So I would propose a hash made up of huc8 - branch_id - hydro_id. Thoughts?

I agree, I think the hash of huc8 - branch_id - hydro_id will give us the best chance at exclusivity.

Thanks Matt and Carson.
I think I see what you're saying, and that would still be a big improvement for us.
I may be off on my understanding here, but separate feature_ids assigned to the same hydro_id would still have different hydrotable values, right? I think what I'm getting at is essentially a schema that would enable a primary key to be defined on new_hash_id + stage_ft across the entire cumulative hydrotable, so we'd want the multiple feature_ids to have their own values as well.
But again, what you're proposing would still be a big help on our end, as we could go from 4 joins down to 2. So if that works better on your end, that's OK.

@TylerSchrag-NOAA A hydro_id represents the basic unit, and is associated with exactly one feature_id (there won't be multiple feature_ids assigned to the same hydro_id), but multiple hydro_ids can have the same feature_id -- essentially a many-to-one relationship because the hydro_ids represent reaches that are generally shorter than the NWM streams from where the feature_ids are derived.

Oh right, thanks - I've gotten this backwards before and should have double checked my notes.
Ok, I get you, thanks for the correction!
-Tyler

Hey - This is something I could have / should have thought through communicating earlier... but I've been messing around with this optimization on our end, and for what it's worth, I think we'll convert the unique ID to an integer on our end to speed up the database operations. If that happens to work with your setup, to have the new ID be an integer to begin with, all the better... but we can translate on our side if you'd prefer text.
Thanks.

Hi Tyler. We are rethinking our strategy on this task and our team will talk about it next week.  We are thinking about going back Carson's idea earlier in this email about using a variant of huc8 - branch_id - hydro_id.  Our new idea is to only have just one integer which would be guaranteed to always be unique.  The new pattern we are going to be talking about is 1{huc8}{branch id}{hydroid}.  By adding a "1" in front of it all should help us with a huc starting with a zero. Our team will double check that it can be easily / quickly / reliably on our side.
How does this idea sound conceptionally?
You can use it as a primary key if you want to and setup an index against it. That should speed your system up quite a bit.  Indexes are always, always much faster in databases as integers.

oh.. good point. I wonder if it will matter if they are fully in numerical order. For indexing, it doesn't matter is just the fact that it is indexed in some fashion. Being indexed in a DB makes so the index only has to read a single column. Order doesn't really matter much in indexing.  But ya.. good to think about that one.

Hey Rob and Matt - Yeah, sounds like we came to the same conclusion on using an integer, that would definitely be best.
What I did while prototyping this on our side over the weekend, is just assigned a temporary integer auto-id in our crosswalk table, and then changed the schema throughout [most of] our workflows to ditch the hydro_id, huc8, and branch for that new "hand_id":

It definitely speeds things up a lot on our side to only index on that one column (combined with rc_stage_ft as primary key), and seems to have solved some of the remaining bottleneck issues with my initial extent geometry caching implementation. I'm not sure how much of a performance difference it will be to use a 64 bit integer like  1{huc8}{branch id}{hydroid} instead of the 32 bit integers I'm using now, but can't imagine that will make too much of a difference.
I suppose if it is just a straight forward 1{huc8}{branch id}{hydroid} pattern, we can always just implement this on the viz pipeline side of things, without you needing to change your workflows / schema at all - I probably should have thought that through to begin with, sorry - but I am glad we're having these conversations, as I suspect we're still only at the beginning of appreciating how our two systems can continue to integrate more now that we're both on AWS (for stuff like more iterative / real-time synthetic rating curve updates and whatnot).

Awesome.
It is super easy to add this key to our system. We do need to add a single
digit on the front as HUC8's can start with zero. We can just add the
number 1 in front of it all.
I did think of one new element of the story.  This number schema works for
just one release version (aka.. fim_4_4_5_0 or fim_4_4_9_0, etc).  Do we
need to worry about you loading a table with more than one fim release?  If
so... we need something else to add to the key to distinguish fim versions.
Thoughts?
Rob
On Tue, Jan 16, 2024 at 10:45 AM TylerSchrag-NOAA @.***>
wrote:

Hey Rob and Matt - Yeah, sounds like we came to the same conclusion on
using an integer, that would definitely be best.
What I did while prototyping this on our side over the weekend, is just
assigned a temporary integer auto-id in our crosswalk table, and then
changed the schema throughout [most of] our workflows to ditch the
hydro_id, huc8, and branch for that new "hand_id":
image.png (view on web)
https://github.com/NOAA-OWP/inundation-mapping/assets/97621365/17cc020d-0334-46ea-9d98-d1cf37c4c7a3
It definitely speeds things up a lot on our side to only index on that one
column (combined with rc_stage_ft as primary key), and seems to have solved
some of the remaining bottleneck issues with my initial extent geometry
caching implementation. I'm not sure how much of a performance difference
it will be to use a 64 bit integer like 1{huc8}{branch id}{hydroid} instead
of the 32 bit integers I'm using now, but can't imagine that will make too
much of a difference.
I suppose if it is just a straight forward 1{huc8}{branch id}{hydroid}
pattern, we can always just implement this on the viz pipeline side of
things, without you needing to change your workflows / schema at all - I
probably should have thought that through to begin with, sorry - but I am
glad we're having these conversations, as I suspect we're still only at the
beginning of appreciating how our two systems can continue to integrate
more now that we're both on AWS (for stuff like more iterative / real-time
synthetic rating curve updates and whatnot).
—
Reply to this email directly, view it on GitHub
https://github.com/NOAA-OWP/inundation-mapping/issues/1051#issuecomment-1894218917,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AVVFLIWCHYOHJMR52ZQCYADYO24ENAVCNFSM6AAAAABASCUQXWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOJUGIYTQOJRG4
.
You are receiving this because you commented.Message ID:
@.***>

--
Rob Hanna
@.***
NOAA Affiliate, Lynker

Thanks Rob - We're gonna clear our cache whenever we update to a new FIM
version, so that shouldn't be an issue within our database until the point
of any discussion about more iterative / live updates.
-Tyler
On Tue, Jan 16, 2024 at 10:17 AM Rob Hanna - NOAA @.***>
wrote:

Awesome.
It is super easy to add this key to our system. We do need to add a single
digit on the front as HUC8's can start with zero. We can just add the
number 1 in front of it all.
I did think of one new element of the story. This number schema works for
just one release version (aka.. fim_4_4_5_0 or fim_4_4_9_0, etc). Do we
need to worry about you loading a table with more than one fim release? If
so... we need something else to add to the key to distinguish fim
versions.
Thoughts?
Rob
On Tue, Jan 16, 2024 at 10:45 AM TylerSchrag-NOAA @.***>
wrote:

Hey Rob and Matt - Yeah, sounds like we came to the same conclusion on
using an integer, that would definitely be best.
What I did while prototyping this on our side over the weekend, is just
assigned a temporary integer auto-id in our crosswalk table, and then
changed the schema throughout [most of] our workflows to ditch the
hydro_id, huc8, and branch for that new "hand_id":
image.png (view on web)
<
https://github.com/NOAA-OWP/inundation-mapping/assets/97621365/17cc020d-0334-46ea-9d98-d1cf37c4c7a3>

It definitely speeds things up a lot on our side to only index on that
one
column (combined with rc_stage_ft as primary key), and seems to have
solved
some of the remaining bottleneck issues with my initial extent geometry
caching implementation. I'm not sure how much of a performance
difference
it will be to use a 64 bit integer like 1{huc8}{branch id}{hydroid}
instead
of the 32 bit integers I'm using now, but can't imagine that will make
too
much of a difference.
I suppose if it is just a straight forward 1{huc8}{branch id}{hydroid}
pattern, we can always just implement this on the viz pipeline side of
things, without you needing to change your workflows / schema at all - I
probably should have thought that through to begin with, sorry - but I
am
glad we're having these conversations, as I suspect we're still only at
the
beginning of appreciating how our two systems can continue to integrate
more now that we're both on AWS (for stuff like more iterative /
real-time
synthetic rating curve updates and whatnot).
—
Reply to this email directly, view it on GitHub
<
https://github.com/NOAA-OWP/inundation-mapping/issues/1051#issuecomment-1894218917>,

or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AVVFLIWCHYOHJMR52ZQCYADYO24ENAVCNFSM6AAAAABASCUQXWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOJUGIYTQOJRG4>

.
You are receiving this because you commented.Message ID:
@.***>

--
Rob Hanna
@.***
NOAA Affiliate, Lynker
—
Reply to this email directly, view it on GitHub
https://github.com/NOAA-OWP/inundation-mapping/issues/1051#issuecomment-1894269903,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AXIZK5NJLVVJH6DY5VDXFC3YO273BAVCNFSM6AAAAABASCUQXWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOJUGI3DSOJQGM
.
You are receiving this because you were mentioned.Message ID:
@.***>


bump codespaces-linux to 1.1.3

I added the tag to my fork, but doesn't seem like those get transfererd over? @Chuxel

/cc: @chrmarti  FYI re: bumped version number.
Yes, to do a release the tag has to be done to master.

I merged this into master - so you can do a tag push when you think its ready to go.  CI is doing dev builds now: https://github.com/microsoft/vscode-dev-containers/actions/runs/551828516


android:allowBackup and android:theme override in Manifest.xml

When I add the this library to my project I've got this error:

Attribute application@allowBackup value=(false) from AndroidManifest.xml:4:18-45 is also present at [blahblah] AndroidManifest.xml:12:9-35 value=(true). Suggestion: add 'tools:replace="android:allowBackup"' to element at AndroidManifest.xml:4:5-11:19 to override.

What's the best way to fix this issue?

For people who might have the same issue, Simply add this line to your Manifest.xml :
tools:replace="android:allowBackup,android:theme"


Corrected background of Metrics in Dark Mode

Notes for Reviewers
This PR fixes #7249
https://user-images.githubusercontent.com/103871275/222240649-da39d242-2f21-4042-beb9-0d8f7bff908a.mp4
Signed commits

[ ] Yes, I signed my commits.

Let the tests pass, I'll hit Merge


[BUG] cant send coin

Describe the bug

To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'   wallet take 6 stai send to destination address "Can't send more than<PHONE_NUMBER> in a single transaction"
Scroll down to '....'
See error

Expected behavior
Send wallet works to transfer founds

Screenshots

OS:
OS Version/Flavor:
CPU:

Additional context

This is probably due to how the STAI in your wallet is broken up. There's a limit to how many UTXOs can be spent in Chia forks. Closing due to old age of issue.


executor: detect logical bugs

executor could detect a set of logical bugs in kernel on top of basic safety bugs detected by grepping console output. To the best of my knowledge logical kernel bugs are not detect by any other automated testing systems, so this could give us whole new plast of bugs. Examples of such checks:

process unexpectedly gets uid=0
an unexpected errno value returned from syscalls
unexpected side-effects (e.g. changing/non-changing mm/fs state)
unexpected syscall failure/success
bogus EFAULT result when kernel overreads/writes arguments
detect user-space memory/context corruptions (#2260)

Taking into account complexity of kernel model these checks probably should be very conservative (give up predicting outcome when in doubt). But still it would be interesting to see if we can detect at least some bugs with conservative checks.
Complete model is close to impossible, so we need to aggressively limit scope initially and then incrementally extend it.
This includes:

whitelisting syscalls, e.g. initially we start with just open/read/write/close
aggressively bailing out on anything unexpected, e.g. one syscalls returned ENOSPC, not checking this program
initially no concurrency at all and each syscall is given enough time to finish

Once we get some initial working base, we can start extending it in all directions. Obviously, more syscalls. But also maybe some limited concurrency, e.g. white/black-list of syscalls that can run concurrently (e.g. no close/write). Ultimately, it may be extremely interesting to test that 2 concurrent syscalls are atomic, i.e. result is equal either to one syscall executed first, then another, or vise versa (potential example bugs: 1, 2). This will probably need some blacklist too. But on the other hand, it does not require the second implementation. E.g. concurrent read/write on udp socket should always be atomic.
A related work on checking filesystems against POSIX model:
SibylFS: formal specification and oracle-based testing for POSIX and real-world file systems.
A related idea that may be simpler to implement is to arrange some honeypots for the test process and then checking if the process is caught red-handed at these honeypots. Examples of honeypots:

a file in the working directory that the test process does not have permissions for, then checking if the file data or metadata was altered in any way
a network port that the test process must not be able to reach, then checking if the port has received any packets
a hash stored at known address in kernel memory, then checking if the test process was able to obtain the hash anywhere in the test process memory

Another idea from Kit: Testing OS-level Virtualization for Functional Interference Bugs paper to detect "functional interference bugs in OS-virtualization mechanisms, such as Linux namespaces. The key idea of Kit is to detect inter-container functional interference by comparing the system call traces of a container across two executions, where it runs with and without the preceding execution of another container".

One other idea is testing the behaviour of a new kernel against behaviour of an old kernel.
There would need to be a way to identify or mark behaviour that is expected to change. Alternatively, we could restrict checking behaviour of kernel APIs that are guaranteed to be stable and should not change.
There are still interesting problems related how to minimize non-determinism of the result of a randomly generated test program. Some ideas:

Limit test program generation to those where non-deterministic behaviour is excluded.
Run the test program several times and collect sets of outputs; then, if the set of outputs from the old and new kernel match, it would also be possible to conclude that behaviour matches. There might still be differences if the output depends on hidden system state, such as hardware clocks, or other timing-dependent state that is impossible to control in a normal system; these would need to be avoided.
Run the kernels in a full-system simulator (e.g. Bochs), where the full-system state can be controlled completely.

FWIW Dirty Pipe could have been found by file honeypots.

Inspired by /sys/kernel/notes story:
We could scan all kernel outputs (e.g. what we read from files, receive over sockets, etc) for potential kernel .text/.data addresses. Will likely have false positives and will need some tuning, but may be interesting to do as an experiment just to see if it catches something real.


Feat/add ignore transactions and ignore errors #1391

:scroll: Description
Implemented Issue #1391
:green_heart: How did you test it?
In the Simulator and wrote test cases.
:pencil: Checklist

[ ] I reviewed submitted code
[x] I added tests to verify changes
[x] No new PII added or SDK only sends newly added PII if sendDefaultPii is enabled
[ ] I updated the docs if needed
[ ] All tests passing
[x] No breaking changes

:crystal_ball: Next steps

@martinhaintz there are still tests failing from the change


[CPP-418]  QLDoc enhancements

Type.qll for now.

Which modules still need fixing (and are not being worked on by someone else)?

Now https://github.com/Semmle/ql/pull/2309.


Issues/35

What:

ss

Why:

Fixes: https://github.com/komuw/ong/issues/35

superseded by https://github.com/komuw/ong/pull/115


Undeploy script

This undeploy script (AKA remove.sh) will look for matching <prefix>-chan Channel and <prefix>-sub Subscription resources and remove them in tandem.
Neither a namespace nor a prefix is required--the script will poll the cluster for both if not provided.
If the Subscription has been changed and no longer points to the Channel, the script refuses to delete the resource but gives the user a warning and the commands to do it themselves.

adding @dockerymick to take a look at doc

Is oc a hard requirement for user to run this script? Can we do the same with just kubectl?

Yes, oc is a hard requirement because it allows the script to find and iterate over the available namespaces. I'm not aware of a way to find available namespaces otherwise.
I changed deploy.sh to use oc also, but I can change it back to kubectl if it needs to be more generic. I was thinking the scripts would both be pointing at an Openshift RHACM hub, but maybe that's a poor assumption? If so, I can adjust the script to require a namespace be provided if a user doesn't have clusterwide access.

I think it's not a problem for now. But in the future, after we open source the framework code, it should not require openshift to deploy and test. So it's better to make oc optional.

Ah, okay. Let me make that change now so that we don't have to worry about it later.

@dockerymick I made some additional adjustments to your edits. Most notably, I replaced "View the following example..." with "View the following guidance..." since to me it's not an example. And I also added a note that parameters are optional. What do you think?

@dhaiducek great idea, i agree with your change


Face representations

User story

As an SD
I need to save the faces and their representations
So that I can use them for automatic registration/recognition between sessions

Acceptance criteria

If a new panelist is detected, their face + face representation + age + gender are saved in a separate database (for automatic registration).
If household members also have their face representation(s) saved in their database (currently, they are all saved in a .pkl file).

Definition of done

Project builds with no errors
Feature was demoed and accepted by product owner
Pull request review by other team member
Unit tests written if necessary and all tests are passed
Test coverage is above 40%
Code is understandable and commented

Not necessary. We implemented a different approach for automatic registration.


[docs] Issue with 'Accessibility assesment with aXe'

https://sonarwhal.com/docs/user-guide/rules/axe.html
Documentation on axe reporting levels for .sonarrc:
"rules": {
        "amp-validator": "off",
        "apple-touch-icons": "error",
        "axe": "error",  //what are the available options?

// what are the available options?

@jasonday See:

https://sonarwhal.com/docs/user-guide/#rules
https://sonarwhal.com/docs/user-guide/rules/axe/#cantherulebeconfigured


Fix Issue 23922 - Fix broken links in std.socket

It's in dlang.org: https://github.com/search?q=repo%3Adlang%2Fdlang.org SAMPLESRC&type=code

That's quite unexpected.

Then you may be surprised to learn that LINK2 is defined there as well :)

I assumed that everything is defined in one place, I just used something that I know works. Anyway, better fix link then.


Add newer models + small bugfix

This PR does two things:

Adds the newer model and removes some obsolete experimental ones
Handles the case of messages with just a media file. Currently Gemini errors if there is no text message with it, so this adds a text message with a single space to the media file. Hacky, but works.

@jph00 It does not look like I can request reviewers directly and I cannot find Tommy (or at least GitHub does not want to me to tag him). Notice that a bunch of issues I had found were due to the fact that the PyPi version is not up to date

Thank you for these updates! :D I will release a new version on pypi shortly


The ProcessShortcode module should define the output style

I wonder if it makes more sense to pass an enum with output "styles" instead of a flag - I.e., should the shortcode output Markdown...HTML...something else? If the shortcode can't produce the desired kind of output we could throw an exception. Could even get smart about it - if the shortcode can render HTML, that's okay if you're expecting Markdown (since HTML is valid Markdown) but asking for HTML when the shortcode only outputs Markdown would throw.
new ProcessShortcodes(output: ShortcodeOutput.Markdown)

cc @mholo65

Closed in favor of #62


SA1115 will now allow comments between parameters

Fixes #1921

Current coverage is 79.49%

Merging #1981 into master will increase coverage by +0.06% as of 7d5067a

@@            master   #1981   diff @@
======================================
  Files          559     559
  Stmts        35237   35259    +22
  Branches      9751    9757     +6
  Methods
======================================
+ Hit          27992   28028    +36
- Partial       5694    5695     +1
+ Missed        1551    1536    -15

Review entire Coverage Diff as of 7d5067a

Powered by Codecov. Updated on successful CI builds.

:+1:


[FLINK-24771][jdbc][tests] Bump test dependencies mariadb-java-client to 2.7.4 and mysql-connector-java to 8.0.27

What is the purpose of the change

Update JDBC test dependencies to the latest versions

Brief change log

Bumped org.mariadb.jdbc:mariadb-java-client from 2.5.4 to 2.7.4
Bumped mysql:mysql-connector-java from 8.0.20 to 8.0.27

Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (yes / no)
The serializers: (yes / no / don't know)
The runtime per-record code paths (performance sensitive): (yes / no / don't know)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: (yes / no / don't know)
The S3 file system connector: (yes / no / don't know)

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

@fapaul I didn't update the title of the PR, but I already modified the commit message when I last rebased to Bump test dependencies mariadb-java-client to 2.7.4 and mysql-connector-java to 8.0.27
I'll change the titles now

@fapaul For JDBC, these are currently the available updates:
[INFO]   mysql:mysql-connector-java .......................... 8.0.20 -> 8.0.27
[INFO]   org.apache.derby:derby ........................ <IP_ADDRESS> -> <IP_ADDRESS>
[INFO]   org.mariadb.jdbc:mariadb-java-client ............... 2.5.4 -> 3.0.2-rc
[INFO]   org.mockito:mockito-core ............................. 2.21.0 -> 4.0.0
[INFO]   org.postgresql:postgresql .......................... 42.2.10 -> 42.3.1
[INFO]   org.powermock:powermock-api-mockito2 .................. 2.0.4 -> 2.0.9
[INFO]   org.powermock:powermock-module-junit4 ................. 2.0.4 -> 2.0.9

The MySQL and MariaDB are addressed in this PR.
Both Derby and Postgress caused issues on the build which I need to look more into.
Powermock is addressed in separate PR https://github.com/apache/flink/pull/17727
Mockito has breaking changes that probably deserves its own ticket.

@AHeise Please merge

@fapaul FYI, Derby can't be upgraded yet to 10.15 because that version drops Java 8 support.


When user passes an empty value for --branch, fetch returns the wrong error

When fetch is called with --branch but no value is given for --branch, fetch returns an inaccurate error message:
ERROR: You must specify exactly one of --tag, --commit, or --branch. Run "fetch --help" for full usage info.

Fixed in #55


Move numpy dep from required to extras - AxisArray and test

Closes #160

Moves numpy dep from required to extras - AxisArray and test
Adds helpful error message when user attempts to import from .axisarray and numpy is not installed.

bump


0.10.0

Does this project need an update to support 0.10.0?

Yes. I read through the version changes and there is one breaking change in the syntax:
The _ and * are considered regular text characters when directly surrounded by alphanumeric characters. But with the 0.10 release, the CJK (Chinese - Japanese - Korean) alphanumeric characters won't be part anymore of this exception.
I have to check the Typst implementation to see what exactly is considered "CJK". Anyway. This parsing will have to be done in the C scanner instead of the grammar.js.
Another change to the syntax is the support for other types than strings as dictionary keys. But the grammar already supports any type as dictionary key, so nothing to do for that.

I found it https://github.com/typst/typst/blob/6808e58a3bb2782c49517c02634b65d85fe28664/crates/typst-syntax/src/lexer.rs#L346

I going to make a program that automatically fetches the files from unicode.org and produces C code with functions testing that a character is part of some unicode set.


Something wrong if switching JS editor to Blocks in some Blocks Games

Describe the bug
Something wrong if switching JS editor to Blocks in some Blocks Games
Steps to reproduce the behavior
1.Navigate to https://arcade.makecode.com/beta#editor
2.Block Games---->Jumpy Platformer----->Open Example
Actual behavior
Something wrong if switching JS editor to Blocks in some Blocks Games. But program run normally if switching Python editor to Blocks
Jumpy Platformer:

Hot Air Balloon:

Bunny Hop:

Cat Jumper:

Additional context
1.OS: Windows(rs6)
2.arcade version: 1.3.32
3.Microsoft MakeCode version: 6.8.19

@jwunderl looks like a bad bug. Can you please do the initial investigation?

@jwunderl looks like a bad bug. Can you please do the initial investigation?

this one occurs when switching back to blocks without triggering a decompile (blocks -> js -> blocks with no changes), appears to be same bug as https://github.com/microsoft/pxt-arcade/issues/2905 (repros same way if you go ->assets-> blocks with no changes)

this one occurs when switching back to blocks without triggering a decompile (blocks -> js -> blocks with no changes), appears to be same bug as https://github.com/microsoft/pxt-arcade/issues/2905 (repros same way if you go ->assets-> blocks with no changes)


Seed Words Backup Scheme Health

As a user, I want to see the health of my seed word backup scheme, so that I can take corrective action to improve health when required.
**This is part of MH7, please refer to MH7: https://trello.com/c/hev20wdt
This issue covers changes to the backend and business logic for enabling this functionality.
Most actions and reducers will be added by issue:https://github.com/bithyve/hexa/issues/3083 the scope of this issue is to add the business logic in Sagas and the required changes in Storage, Database, Upgrade Script, and Wallet Image to enable the functionality.
This follows on from and covers:
Health Check for Seed words.
1. There are 3 things user has to keep a check on if they have opted to Seed Words backup: Q&A, Words and Recovery Kit.
2. Q&A check is as usual
3. Recovery kit and Seed words are to be confirmed in 6 months each with Words first being checked after 9 months. (The seed words are not kept in the app so a list of hashes needs to be kept for confirmation or some other ZKP way)
4. The MH screen should show a different view for Seed Words based backup.

This can be closed when seed words backup health functionality is tested


ci: release

Part 2 of the new release process!
When there's a tag matchingwdl-v* pushed to main, this kicks off publishing to crates.io and creating a GitHub release. The GitHub release will have auto-generated release notes based on the merged PRs since the last release. Example here
This also features a change to the previous bump step where CHANGELOGS are now updated as well.

I don't want to use git commits as the CHANGELOG.md or release notes, as I generally agree with the philosophy laid out here.

Changelogs should remain updated in each commit and should be manually added by the software engineer who made the changes. I don't want any automation editing the changelogs.
Release notes can be autogenerated from parsing the CHANGELOG.md(s) upon release if you'd like, but that will require writing parsing code for the way the changelogs are structured.

I think we're in almost total agreement here. I want us to continue manually maintaining the 6 different CHANGELOGs we have, and I am not proposing we automate any of that (other than the insertion of version+date headers which will still have to undergo manual review before making it to main).
I view the release notes we show on GitHub to be a completely separate from the changelogs we maintain.

Release notes can be autogenerated from parsing the CHANGELOG.md(s) upon release if you'd like, but that will require writing parsing code for the way the changelogs are structured (and they need to generate the notes according to the process laid out in RELEASE.md).

I think this is a bad idea. As the "Keep a changelog" document says, changelogs are designed for humans, not machines. The format is very resistant to good automation, and most anything we write to parse them is going to be error-prone.
So I believe we're in agreement about the changelogs and that can be considered settled. But the release notes issue I see as unsolved. Our constraints when filling out release notes are:
a. continue to manually write a bunch of distinct changelogs
b. bc of the format and manual nature of (1), we can't write [good] automation that can parse those changelogs
I see a few potential solutions:

dump git logs using GitHub's automation

(which I'll say I'm surprised by how nice these turn out. I didn't expect much from log dumping, but they did pretty good with cleaning it up)

Leave release notes empty
Populate the release notes with static links to the changelogs

i.e. the release notes will be more or less identical for every release (aside for any changes to which CHANGELOGs we point to)

don't automate the release and write it by hand

I think any of those 4 are reasonable courses of action for this repo, though option (4) is definitely in last place for me personally.

I personally think it's fine for the GitHub release to be auto-generated from the commit history with the individual CHANGELOG.md expected to be maintained with every commit into the repo.


Fixed grammar issue.

@frodopwns thank you!

No problem.  It is nice having an edit link on every doc page!


Vertical Scroll When Horizontal Scroll Bar Is Visible

Description
If horizontal scroll bar is visible you can scroll vertically (using mouse wheel) even if the content does not run off the bottom of the screen. In my case I only have 1 line of text.
Steps to Reproduce

Open new tab
Type really long string that runs off edge of screen causing horizontal scroll bar to be displayed
Use mouse wheel to scroll vertically

Expected behavior: Since there is only 1 line of text there should be no need for vertical scroll
Actual behavior: Vertical scroll happens when not needed
Versions
Atom: 1.8.0
OS: Linux Fedora 23

Can reproduce and ran into this yesterday, here is what I did:

Atom in safe mode.
Ensure Soft Wrap and Scroll Past End is off.
Open a new empty editor and type some text until horizontal scroll bar is shown.
Scroll vertically with the mouse wheel. Atom scrolls one line of text. Expected behavior is to not scroll at all since all content is visible.

Atom 1.9.6 Windows 7.

I can also reproduce this issue in v1.10.2. @lee-dohm can you please change the label.

Confirmed.


feat: port @[elementwise] attribute

This ports the @[elementwise] attribute and the elementwise_of% e term elaborator.
It does not port the elementwise! h tactic, which can instead be handled by replace h := elementwise_of% h for now.

I'm about to push a refactor that removes the code duplication between elementwise and reassoc.

@kmill, if you could have a look at the refactor, and ping me if it's okay, I'm otherwise happy to merge.

@semorrison Looks good to me. Thanks for the refactor.
I'll just mention here again that there's a linting error in test/elementwise.lean where you put the attribute on something that already has simp. Floris knows about it and is planning on fixing it.

bors merge


[ci skip] adding user @traversaro

Hi! This is the friendly automated conda-forge-webservice.
I've added user @traversaro as instructed in #3.
Merge this PR to add the user. Please do not rerender this PR or change it in any way. It has [ci skip] in the commit message to avoid pushing a new build and so the build configuration in the feedstock should not be changed.
Please contact conda-forge/core to have this PR merged, if the maintainer is unresponsive.
Fixes #3

@traversaro can I add you as a maintainer?

@traversaro can I add you as a maintainer?

Ok, I am not familiar with this package, but if it is helpful feel free to add me!

Thanks @traversaro I want to add someone from your team so you can resolve package version issues. It is a relatively bog standard Python library without anything unusual.


pressing 'n' in DMs causes the new post prompt to pop up.

Sorry I missed this, my notifications apparently aren't setup right. I'll take a look and get it fixed.

A quick update. This seems to be the one keyboard shortcut that is implemented by the bluesky-social team. I'll see if there's something I can do to override that, but it isn't immediately clear to me what that is. It may be better solved by a PR on their repo.


chore(deps): op-alloy api changes

Description
Update op-alloy api change.

📚 $\text{Stack Overview}$
Pulls submitted in this stack:

#824 👈
main

This comment was automatically generated by st.


text.repeated implemented

Closes: #154

PR-Codex overview
This PR implements the repeated method in text.eo that returns a string repeated n times.
Detailed summary

Added rec-repeated method that returns a string repeated n times
Added contains method that checks if a string contains a substring
Updated text-tests.eo to test the new methods

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

@rultor merge

@rultor merge

@yegor256 Done! FYI, the full log is here (took me 9min)

@rultor release, tag is 0.4.0

@rultor release, tag is 0.4.0

@yegor256 OK, I will release it now. Please check the progress here


Python auto-complete fail case in for-loop after break

I have part of code like this
for root, suddirs, files in os.walk(indir, True):
    if root != indir:
        break
    for f in files:
        if f.endswith("." + inext):
            regexresult = re.match(r"^[a-zA-Z0-9]+\-[0-9]+", f)
            if regexresult:
                key = regexresult.group(0).lower()
                l = bangodict.get(key, list())
                l.append(f)
                bangodict[key] = l

At line after break, all dot-auto-complete cannot pop up. However, when I am outside this for loop, it works normally again.

Please file this issue on the vscode-python extension's repo: https://github.com/microsoft/vscode-python/issues


support CDK/Angular 14-15

peerDependency is locked to 13.x and prevents a proper install for angular 14/15.

I am working on an upcoming update for angular 15 support

awesome. thanks.
Any chance that you can also setup the Releases within GitHub properly?
Just out of convenience I usually sub to the release notifications.


Hide nightly builds link on macOS

They are unavailable for years
At https://qgis.org/resources/installation-guide/#qgis-nightly-release you are directed to https://download.qgis.org//downloads/macos/qgis-macos-nightly.dmg for master downloads on macOS which is a forbidden URL. And actually no nightly/dev builds have occurred in the parent folder for months and years.
I suggest we hide the mention now and reopen when that macOS issue is solved.

Hi @DelazJ, thank you for this PR.
I think we should update/delete the e2e fixture to match to this change.
https://github.com/qgis/QGIS-Website/blob/bac8ec2d77e10925b634b834c3f858331654df1c/playwright/ci-test/tests/fixtures/installation-guide-page.ts#L94
Please let me know if you need any help.

Hi @Xpirix
Thanks. Sorry for the lack of feedback; I totally forgot this PR.

No problem, you're welcome.


Volunteer Experience

Do you have any plan to add volunteer experience field?

I haven't planned to add it yet. But if you want, you can develop this feature and open a pull request. We'll seen then.

What have you think about it then?

Adding a neat contributing guidelines or roadmap will helpful to understand.


Bad link on uses page

The link for "my post about it" points to /blog/, while the permalink is /notes/.
https://github.com/scottishstoater/chriscollins.me/blob/d950050e678124561dd1bddc2bee8e45d82fe179/src/uses.md#L85
PS. I'll make a PR tomorrow, once Hacktoberfest starts 😉.
PPS. I might run a cypress test to check the site for any more broken links.

@scottishstoater see https://github.com/binyamin/chriscollins.me/tree/cypress, where I set up cypress to test for broken links. So far, there seem to be four broken links. The only thing is, cypress stops checking the page if it finds a broken link. So you would need to keep fixing and testing and fixing, etc.


Update ketcher to 2.11

This requires a recent streamlit as it needs a more recent react.
It solves a lot of issues with aromatic molecules (where the SMILES produced were invalid)

I have the actions running on my side: https://github.com/bjonnh/streamlit-ketcher/actions
So you can check for flakyness across accounts too.

Thank you!


Clicking links in terminal should focus the terminal when it's not focused

https://twitter.com/colshacol/status/918542506870083584

@Tyriar, thanks for making this issue! I was joking on Twitter and planned to come make it myself.
Bug details:
Version: 1.18.0-insider (1.18.0-insider)
Description: When focus is not in the integrated terminal and then a click is made in the integrated terminal and the click lands on a ctrl+clickable link, focus to the integrated terminal is not applied.

@colshacol haha, sarcasm doesn't translate so well to text sometimes 😄

Why is the issue closed?

@colshacol the issue is fixed, it will be in v1.18.0


[MM-38469] - fixed several console errors regarding propTypes

Summary
this PR fixes several console errors that came up due to a false setting of props within the Menu.ItemToggleModalRedux component
Ticket Link
MM-38469
Release Note
NONE

/cherry-pick release-6.0

Cherry pick is scheduled.

Cherry pick is scheduled.

/cherry-pick cloud


Audit QWATCH documentation for consistency

Fixes QWATCH audit and doc update.

Refactor using SET Command docs as reference
Use $ for path demonstration instead of .

@JyotinderSingh went through the review comments. Can you please review and let me know if I still need to update the pull request!

@JyotinderSingh reverted the change to syntax example. Please let me know if further changes are required.


I haven't picked your example apart, but I imagine what you're seeing may have to do with your misuse of dates. Looking at your events, you have both strings and moment objects for start and end, when the documentation specifically states that Big Calendar requires true JS Date objects.

I haven't picked your example apart, but I imagine what you're seeing may have to do with your misuse of dates. Looking at your events, you have both strings and moment objects for start and end, when the documentation specifically states that Big Calendar requires true JS Date objects.
Originally posted by @cutterbl in https://github.com/jquense/react-big-calendar/issues/2166#issuecomment-1092784015

mistake


include post in MockLoggingView

its posted to in the tests
Signed-off-by: Brett Matthews<EMAIL_ADDRESS>

@brett-matthews Thanks for adding this method to the mock class.


Unable to browse, missing images

It seems that something fails to load, both images and menu items.
This is the url when I click on movies and series: http://<IP_ADDRESS>:3000/#
The text works, I can read "Welcome to PiFlix" etc.. I can also see the Torrent and a play symbol.
I would attach a screenshot, but I am quite new to the raspbian, so I don*t know how to..

Since raspbian seems to run x11, you can run scrot <filename> to take a screenshot and save it.

Should be resolved


[WIP] feat: peer country chart

A pie chart showing the top 4 countries peers reside in.

@alanshaw is there anything specific you wanted to add to this PR? I'll adopt it, if you wanna brain dump any todos you had in mind.

I think all that was left here to do here was styling. I believe the design had one segment slightly larger than the rest and tooltips instead of a key.

I'll take a look at the styling then 😄

@olizilla @alanshaw I think we should remove the labels because we can get an enormous list of countries. Otherwise we can keep them at the bottom to match #764

@hacdias we need some kind of label on that graph without having to mouse over, otherwise it's just a mystery pie!

Let's merge this in, and merge it in to the status page PR.


Import framework submodules lazily

Description
Whenever a user calls import transformer_engine, we attempt to import all framework submodules (transformer_engine.pytorch, etc) within try-catch statements. However, this can suppress important errors and make debugging tricky. A more sophisticated approach is to import the submodules lazily, i.e. only import a module the first time it is used. For example, if running with a PyTorch build of TE:
import transformer_engine as te
te.pytorch.__file__  # Imports transformer_engine.pytorch
te.jax.__file__      # Imports transformer_engine.jax, fails, and throws import error

Type of change

[ ] Documentation change (change only to the documentation, either a fix or a new content)
[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Changes
Please list the changes introduced in this PR:

Load framework modules lazily

Checklist:

[x] I have read and followed the contributing guidelines
[x] The functionality is complete
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes

/te-ci

The goal of this PR isn't to fix any existing bugs, just to make debugging easier by not hiding error messages. I don't think we can protect developers from themselves when they write buggy code.

/te-ci

Pylint doesn't seem to understand lazily imported modules and gives a bunch of spurious warnings. I've worked around this by only lazy-loading a module after failing to import it normally. This is uglier, but it still helps give more useful error messages.

I think this PR is causing negative impact on users of TE. Previously, the code read
try:
    from . import jax
except ImportError as e:
    pass

When a pytorch TE user doesn't have jax installed, it's fine. However, we now have
try:
    from . import jax
except ImportError:
    jax = _lazy_import("transformer_engine.jax")

which not only hides the jax import error but also throws that in a much later and hard to understand place with more python lazy import stacks.
Are jax and paddle packages required for pytorch TE users now? If not, we should add try-catch blocks for all those framework imports.
cc @ptrendx  @jjsjann123 @tfogal

Example stacktrace:
E           RuntimeError: Process 0 exited with error code 10 and exception:
E           Traceback (most recent call last):
E             File "/usr/local/lib/python3.10/dist-packages/torch/testing/_internal/common_distributed.py", line 653, in run_test
E               getattr(self, test_name)()
E             File "/usr/local/lib/python3.10/dist-packages/torch/testing/_internal/common_distributed.py", line 539, in wrapper
E               fn()
E             File "/usr/local/lib/python3.10/dist-packages/torch/testing/_internal/common_utils.py", line 2756, in wrapper
E               method(*args, **kwargs)
E             File "/usr/local/lib/python3.10/dist-packages/torch/testing/_internal/common_utils.py", line 443, in instantiated_test
E               test(self, **param_kwargs)
E             File "/opt/pytorch/lightning-thunder/thunder/tests/distributed/test_ddp.py", line 332, in test_all_gather
E               actual = cfoo(a, b, process_group, async_op)
E             File "/opt/pytorch/lightning-thunder/thunder/__init__.py", line 615, in fn_
E               cache_entry, inps, pro_to_epi = get_computation_and_inputs(*args, **kwargs)
E             File "/opt/pytorch/lightning-thunder/thunder/__init__.py", line 202, in cache_info_wrapper
E               res = fn(*args, **kwargs)
E             File "/opt/pytorch/lightning-thunder/thunder/__init__.py", line 473, in get_computation_and_inputs
E               jit_results: TraceResults = interpreter(
E             File "/opt/pytorch/lightning-thunder/thunder/__init__.py", line 190, in _general_frontend
E               return thunder_general_jit(fn, args, kwargs, sharp_edges=sharp_edges, record_history=record_history)
E             File "/opt/pytorch/lightning-thunder/thunder/core/jit_ext.py", line 1524, in thunder_general_jit
E               result = jfn(*args, **kwargs)
E             File "/opt/pytorch/lightning-thunder/thunder/core/interpreter.py", line 6645, in fn_
E               runtimectx: InterpreterRuntimeCtx = InterpreterRuntimeCtx(debug_log=debug_log, record_history=record_history)
E             File "/opt/pytorch/lightning-thunder/thunder/core/interpreter.py", line 531, in __init__
E               self._original_callsite: inspect.FrameInfo = inspect.stack()[2]  # [__init__, fn_, callsite, ...]
E             File "/usr/lib/python3.10/inspect.py", line 1673, in stack
E               return getouterframes(sys._getframe(1), context)
E             File "/usr/lib/python3.10/inspect.py", line 1650, in getouterframes
E               frameinfo = (frame,) + getframeinfo(frame, context)
E             File "/usr/lib/python3.10/inspect.py", line 1624, in getframeinfo
E               lines, lnum = findsource(frame)
E             File "/usr/lib/python3.10/inspect.py", line 952, in findsource
E               module = getmodule(object, file)
E             File "/usr/lib/python3.10/inspect.py", line 869, in getmodule
E               if ismodule(module) and hasattr(module, '__file__'):
E             File "/usr/lib/python3.10/importlib/util.py", line 247, in __getattribute__
E               self.__spec__.loader.exec_module(self)
E             File "<frozen importlib._bootstrap_external>", line 883, in exec_module
E             File "<frozen importlib._bootstrap>", line 241, in _call_with_frames_removed
E             File "/usr/local/lib/python3.10/dist-packages/transformer_engine/jax/__init__.py", line 6, in <module>
E               from . import flax
E             File "/usr/local/lib/python3.10/dist-packages/transformer_engine/jax/flax/__init__.py", line 5, in <module>
E               from .module import DenseGeneral, LayerNorm
E             File "/usr/local/lib/python3.10/dist-packages/transformer_engine/jax/flax/module.py", line 14, in <module>
E               from flax import linen as nn
E           ModuleNotFoundError: No module named 'flax'
E
E           Process 1 exited with error code 10 and exception:
E           Traceback (most recent call last):
E             File "/usr/local/lib/python3.10/dist-packages/torch/testing/_internal/common_distributed.py", line 653, in run_test
E               getattr(self, test_name)()
E             File "/usr/local/lib/python3.10/dist-packages/torch/testing/_internal/common_distributed.py", line 539, in wrapper
E               fn()
E             File "/usr/local/lib/python3.10/dist-packages/torch/testing/_internal/common_utils.py", line 2756, in wrapper
E               method(*args, **kwargs)
E             File "/usr/local/lib/python3.10/dist-packages/torch/testing/_internal/common_utils.py", line 443, in instantiated_test
E               test(self, **param_kwargs)
E             File "/opt/pytorch/lightning-thunder/thunder/tests/distributed/test_ddp.py", line 332, in test_all_gather
E               actual = cfoo(a, b, process_group, async_op)
E             File "/opt/pytorch/lightning-thunder/thunder/__init__.py", line 615, in fn_
E               cache_entry, inps, pro_to_epi = get_computation_and_inputs(*args, **kwargs)
E             File "/opt/pytorch/lightning-thunder/thunder/__init__.py", line 202, in cache_info_wrapper
E               res = fn(*args, **kwargs)
E             File "/opt/pytorch/lightning-thunder/thunder/__init__.py", line 473, in get_computation_and_inputs
E               jit_results: TraceResults = interpreter(
E             File "/opt/pytorch/lightning-thunder/thunder/__init__.py", line 190, in _general_frontend
E               return thunder_general_jit(fn, args, kwargs, sharp_edges=sharp_edges, record_history=record_history)
E             File "/opt/pytorch/lightning-thunder/thunder/core/jit_ext.py", line 1524, in thunder_general_jit
E               result = jfn(*args, **kwargs)
E             File "/opt/pytorch/lightning-thunder/thunder/core/interpreter.py", line 6645, in fn_
E               runtimectx: InterpreterRuntimeCtx = InterpreterRuntimeCtx(debug_log=debug_log, record_history=record_history)
E             File "/opt/pytorch/lightning-thunder/thunder/core/interpreter.py", line 531, in __init__
E               self._original_callsite: inspect.FrameInfo = inspect.stack()[2]  # [__init__, fn_, callsite, ...]
E             File "/usr/lib/python3.10/inspect.py", line 1673, in stack
E               return getouterframes(sys._getframe(1), context)
E             File "/usr/lib/python3.10/inspect.py", line 1650, in getouterframes
E               frameinfo = (frame,) + getframeinfo(frame, context)
E             File "/usr/lib/python3.10/inspect.py", line 1624, in getframeinfo
E               lines, lnum = findsource(frame)
E             File "/usr/lib/python3.10/inspect.py", line 952, in findsource
E               module = getmodule(object, file)
E             File "/usr/lib/python3.10/inspect.py", line 869, in getmodule
E               if ismodule(module) and hasattr(module, '__file__'):
E             File "/usr/lib/python3.10/importlib/util.py", line 247, in __getattribute__
E               self.__spec__.loader.exec_module(self)
E             File "<frozen importlib._bootstrap_external>", line 883, in exec_module
E             File "<frozen importlib._bootstrap>", line 241, in _call_with_frames_removed
E             File "/usr/local/lib/python3.10/dist-packages/transformer_engine/jax/__init__.py", line 6, in <module>
E               from . import flax
E             File "/usr/local/lib/python3.10/dist-packages/transformer_engine/jax/flax/__init__.py", line 5, in <module>
E               from .module import DenseGeneral, LayerNorm
E             File "/usr/local/lib/python3.10/dist-packages/transformer_engine/jax/flax/module.py", line 14, in <module>
E               from flax import linen as nn
E           ModuleNotFoundError: No module named 'flax'

/usr/local/lib/python3.10/dist-packages/torch/testing/_internal/common_distributed.py:805: RuntimeError

Hmm, this seems to be because you are trying to inspect all of the modules, which tries to access their attributes here:
if ismodule(module) and hasattr(module, '__file__'):, which in turns initializes the module.
@DEKHTIARJonathan any suggestions, especially since we want to go with lazy loading as well for the PIP wheel effort? Also @ksivaman for visibility.

This is a messy bug:

The old approach of putting the imports in try-catch statements suppressed useful error messages, especially for developers.
It feels correct to me that import transformer_engine.jax should throw an import error if JAX is not installed.
I don't think we can guarantee that the user has exactly one DL framework installed. I can imagine a user installing TE with PyTorch support, and at some later time installing JAX in the same Conda env.
Thunder's jitter inspects the stack with inspect.stack, which we don't want to modify or reimplement.

I have an initial fix at https://github.com/NVIDIA/TransformerEngine/pull/844, but this can run into the same Thunder bug if the user has multiple DL frameworks installed.

The old approach of putting the imports in try-catch statements suppressed useful error messages, especially for developers.

We can do
try:
    from . import jax
except ImportError as e:
    traceback.print_exc()

@timmoon10 @xwang233 @ptrendx can you try this branch.
Try with

export TE_LAZY_IMPORT_FLAVOR=1
export TE_LAZY_IMPORT_FLAVOR=2
export TE_LAZY_IMPORT_FLAVOR=3

I have 3 tentative implementation, please let me know which one works best


WIP: faster python build experiment

Python builds are taking significantly longer than builds for other wrapped languages.
This PR speeds up python build a lot (at least 2x based on some preliminary results) by providing a parallel_compiler monkeypatch inspired by https://stackoverflow.com/questions/11013851/speeding-up-build-process-with-distutils.

****************************************************************

libgrpc.so

     VM SIZE        FILE SIZE
 ++++++++++++++  ++++++++++++++

  [ = ]       0        0  [ = ]

****************************************************************

libgrpc++.so

     VM SIZE        FILE SIZE
 ++++++++++++++  ++++++++++++++

  [ = ]       0        0  [ = ]

[trickle] No significant performance differences

Corrupt JSON data (indicates timeout or crash):
    bm_call_create.BM_IsolatedFilter_ClientChannelFilter_NoOp_.counters.new: 10
    bm_call_create.BM_IsolatedFilter_ClientChannelFilter_NoOp_.counters.old: 10

[microbenchmarks] No significant performance differences

****************************************************************

libgrpc.so

     VM SIZE        FILE SIZE
 ++++++++++++++  ++++++++++++++

  [ = ]       0        0  [ = ]

****************************************************************

libgrpc++.so

     VM SIZE        FILE SIZE
 ++++++++++++++  ++++++++++++++

  [ = ]       0        0  [ = ]

[trickle] No significant performance differences

****************************************************************

libgrpc.so

     VM SIZE        FILE SIZE
 ++++++++++++++  ++++++++++++++

  [ = ]       0        0  [ = ]

****************************************************************

libgrpc++.so

     VM SIZE        FILE SIZE
 ++++++++++++++  ++++++++++++++

  [ = ]       0        0  [ = ]

[trickle] No significant performance differences

Objective-C binary sizes
*****************STATIC******************
  New size                      Old size
 2,015,649      Total (=)      2,015,649

 No significant differences in binary sizes

***************FRAMEWORKS****************
  New size                      Old size
11,116,195      Total (=)     11,116,195

 No significant differences in binary sizes

Corrupt JSON data (indicates timeout or crash):
    bm_call_create.BM_IsolatedFilter_ClientChannelFilter_NoOp_.counters.new: 10
    bm_call_create.BM_IsolatedFilter_ClientChannelFilter_NoOp_.counters.old: 10

[microbenchmarks] No significant performance differences

Corrupt JSON data (indicates timeout or crash):
    bm_call_create.BM_IsolatedFilter_ClientChannelFilter_NoOp_.counters.new: 10
    bm_call_create.BM_IsolatedFilter_ClientChannelFilter_NoOp_.counters.old: 10

[microbenchmarks] No significant performance differences

****************************************************************

libgrpc.so

     VM SIZE        FILE SIZE
 ++++++++++++++  ++++++++++++++

  [ = ]       0        0  [ = ]

****************************************************************

libgrpc++.so

     VM SIZE        FILE SIZE
 ++++++++++++++  ++++++++++++++

  [ = ]       0        0  [ = ]

Corrupt JSON data (indicates timeout or crash):
    bm_call_create.BM_IsolatedFilter_ClientChannelFilter_NoOp_.counters.new: 10
    bm_call_create.BM_IsolatedFilter_ClientChannelFilter_NoOp_.counters.old: 10

[microbenchmarks] No significant performance differences

****************************************************************

libgrpc.so

     VM SIZE        FILE SIZE
 ++++++++++++++  ++++++++++++++

  [ = ]       0        0  [ = ]

****************************************************************

libgrpc++.so

     VM SIZE        FILE SIZE
 ++++++++++++++  ++++++++++++++

  [ = ]       0        0  [ = ]

[trickle] No significant performance differences

Objective-C binary sizes
*****************STATIC******************
  New size                      Old size
 2,015,649      Total (=)      2,015,649

 No significant differences in binary sizes

***************FRAMEWORKS****************
  New size                      Old size
11,116,198      Total (>)     11,116,196

 No significant differences in binary sizes

Corrupt JSON data (indicates timeout or crash):
    bm_call_create.BM_IsolatedFilter_ClientChannelFilter_NoOp_.counters.new: 10
    bm_call_create.BM_IsolatedFilter_ClientChannelFilter_NoOp_.counters.old: 10

[microbenchmarks] No significant performance differences

Improvements:
Linux before the change:
2018-10-30 12:22:42,818 START: /var/local/git/grpc/tools/run_tests/helper_scripts/build_python.sh
2018-10-30 12:33:47,597 PASSED: /var/local/git/grpc/tools/run_tests/helper_scripts/build_python.sh [time=664.8sec, retries=0:0; cpu_cost=1.0; estimated=1.0]
2018-10-30 12:33:47,598 START: /var/local/git/grpc/tools/run_tests/helper_scripts/build_python.sh
2018-10-30 12:34:58,729 PASSED: /var/local/git/grpc/tools/run_tests/helper_scripts/build_python.sh [time=71.1sec, retries=0:0; cpu_cost=1.0; estimated=1.0]

Linux after the change:
2018-10-31 08:08:04,912 START: /var/local/git/grpc/tools/run_tests/helper_scripts/build_python.sh
2018-10-31 08:12:02,507 PASSED: /var/local/git/grpc/tools/run_tests/helper_scripts/build_python.sh [time=237.6sec, retries=0:0]
2018-10-31 08:12:02,508 START: /var/local/git/grpc/tools/run_tests/helper_scripts/build_python.sh
2018-10-31 08:13:02,714 PASSED: /var/local/git/grpc/tools/run_tests/helper_scripts/build_python.sh [time=60.2sec, retries=0:0]

Mac:
run_tests_python_macos_opt_native  before: ~16min after  ~10.5min
Windows:
run_tests_python_windows_opt_native ~ 10.5min .  -> no improvement
Artifacts:
on linux improved from 9-10mins to  6-9mins (there's multiple artifacts being built, so it adds up)

I understand the change you are marking and it is a brilliant hacking to gain building speed. But as you said I need some history lessons about the building tools, like why there are two setup.py, why are they different, how's their job different from each other...


fix(cli): consistently support URLs as comma-separated values

Motivation
As discussed in https://github.com/ChainSafe/lodestar/pull/4576#discussion_r1232086829 we should support providing URLs as comma-separated values more consistently. This is also the most intuitive pattern to provide multiple values.
Description
We already support this for --beaconNodes
https://github.com/ChainSafe/lodestar/blob/81a6da0a7b93556d6cc62dcc9389625c08d17dcb/packages/cli/src/cmds/validator/options.ts#L165-L172
This PR just applies this pattern to CLI flag that support providing multiple URLs.
Opted to just copy-paste, extracting it into reusable function could make sense but found it to be less intuitive.

:tada: This PR is included in v1.9.0 :tada:


Tensorflow API for Carbon?

@maifeeulasad,
We see that the issue template has not been filled, could you please do so as it helps us analyse the issue. Thank you!

@tilakrayal, I understand it. But I couldn't fit it any of these:

Tensorflow Issue Template
TensorFlow Lite Converter Issue
TensorFlow Lite in Play Services issue
TensorFlow Lite Op Request
Report a security vulnerability

That's why I created an empty issue.

@maifeeulasad,
Could you please try to select Tensorflow Issue Template and provide the required details. So that it will be easy for us to analyse the issue. Thank you!

@tilakrayal Can you suggest to me a template from the list, as I'm not so sure.

@maifeeulasad , Could you please elaborate your requirement to understand the problem better. Thanks!


vim opens multiple files with garbled GETTEXT messages

Steps to reproduce
Install vim from vim-win32-installer, then open MINGW64 zsh in windows terminal or open cmd.exe/powershell; command
vim.exe main.c os_win32.c
杩樻湁 2 杓枃浠 chop 瓑寰呯紪杈

The prompt message is garbled; if chcp 65001 is used before the above command, cmd.exe and mingw64 zsh.exe are normal (the power shell environment is still garbled, and the input/output encoding is set to utf-8 and is normal)
How to set up normal output of messages that does not depend on specific environment
https://github.com/user-attachments/assets/7701a124-b1c1-4fbf-8e15-9c2328716d64
Expected behaviour
A normal message should say that 2 个文件等待编辑
Version of Vim
9.1.X
Environment
OS: Windows 10 x86_64
Shell: zsh 5.9（mingw64) / cmd.exe /power shell
windows terminal
:lang output

Logs and stack traces
No response

Hm, I did not see the error message from your video. Does it happen with vim --clean? Is there a reason, you do not run in UTF-8 codepage by default? I think this is now the default for the new Windows terminal anyhow.

@chrisbra hey，after a week of testing, I found the reason: setlocale setting code page (cp936) is inconsistent with bind_textdomain_codeset (VIMPACKAGE, 'utf-8'). Before terminal output, the utf-8 encoding is recognized as the encoding set by setlocale (p936), so it appears Garbled code, can this be fixed?

is inconsistent with bind_textdomain_codeset (VIMPACKAGE, 'utf-8')

Where do you have set? And isn't your Vim running with utf-8 encoding?

is inconsistent with bind_textdomain_codeset (VIMPACKAGE, 'utf-8')

Where do you have set? And isn't your Vim running with utf-8 encoding?

In mbyte.c,  I set bind_textdomain_codeset (VIMPACKAGE, 'cp936) replacing enc_utf8 ? "utf-8" : (char *)p_enc，then the message normal.

well then try running vim with :set encoding=cp936. Then p_enc should be cp936. But I think you should rather convert to utf-8 instead.

You are right, with setting :set encoding=cp936,  not only the message is garbled,  but also the text file's content. And p_enc is still utf-8 , not cp936.


Added AASA file

To be deployed to QA for deep linking tests

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


FEATURE: possibility to open source file from the tree

This is a GREAT extension! One of the most useful and must have in vs code ecosystem!
I have a little suggestion, which would improve usability: it should be possible to just open a source .md file directly from the items tree in the panel. This allow to quick change/edit source markdown file and let the tree in panel update. Without this, it's sometimes quite unconvenient to locate original source file.

Thanks for the feedback! Any other requests are welcome!
The proposed feature is not that hard to implement, will try to do it, if I have a little spare time.
I think I will add it to the context menu, with the label Open source.

@qyloxe please check the newest update (version 1.2.1), it should work as requested (check the changelog for details)

Works like a charm! Thanks!


[Idea] Add music to some of the emotes

As the title suggests, adding a looping music to the emotes would be a really nice social touch

Technically, I already have the code for this in the mod. It works by checking if there is a boombox nearby, and if the emote you're playing has a song with the same name in one of the asset bundles, it will attempt to play that song, and it seems to work fine.
However, I am a little cautious about adding songs that could flag my mod with anything copyright related, so I currently don't have any songs added into my mod. After I finish some planned updates, maybe I'll get around to compiling an asset bundle of songs that will work for this mod, and provide them as a download from another source instead of including them in my mod, and you would just drag and drop the asset bundle into the mod's asset bundle folder, and ideally, it would just "work" with how my code is set up.
I would say keep your eyes peeled for any information about this on the mod page on the thunderstore in case I do this soon!


Add typed variant of parse, parseAsync, safeParse, and safeParseAsync

Closes #1748. I didn't add any tests since this is build time and not run time, and it's just a wrapper around the existing methods, but if there are some tests you would find useful just let me know and I'll add 'em!

A thought - I know this is closer to what I originally proposed two years ago but what about making parse/safeParse/parseAsync generic, taking an options typearg object, instead? Would avoid expanding the API surface just for the sake of types:
-  parse(data: unknown, params?: Partial<ParseParams>): Output {
+  parse<Options extends {strict: boolean} = {strict: false}>(data: Options['strict'] extends true ? Input : unknown, params?: Partial<ParseParams>): Output {

Usage:
const S = z.string()

S.parse<{strict: true}>('x') // ok
S.parse<{strict: true}>(123) // ts error
S.parse(123) // no ts error
```ts

My preference for this would be a single .assertType(input: Input) method that returns void...basically just there as a utility for type checking. I'm trying to get rid of methods not add more 🙃 Open to suggestions on naming. Something like this will land in Zod 4.


Update tested platforms and use reusable workflow

Description
Update tested platforms and use reusable workflow
Issues Resolved
List any existing issues this PR resolves
Check List

[ ] A summary of changes made is included in the CHANGELOG under ## Unreleased
[ ] New functionality includes testing.
[ ] New functionality has been documented in the README if applicable.

Released as: 8.0.0


create github action for releases

with github actions on release
create an action which creates the .owl file from the .ttl and include it in the release.
If possible, perform a check to see if the version number in the ontology is the same as the release

I am experiment on fork https://github.com/andrecastro0o/aeon/
It will probably need to involve:

https://github.com/ncipollo/release-action

@StroemPhi
The basic functionality of the release action is implemented in release_action.yml

Actions are viewable/triggered in: https://github.com/andrecastro0o/aeon/actions/workflows/release_action.yml
Releases in: https://github.com/andrecastro0o/aeon/releases

A few outstanding issues:

conversions to obo is not possible due to errors (see log at the bottom) - which I think we should also in tests
the action performs a prerelease (can be changed), which means, that:

release can be manually edited and made into a non - prerelease
as long as the the tag does not change, the action  it will continue to "add" to the same pre-release

robot convert --input aeon.ttl --format obo --output aeon.obo
OBO STRUCTURE ERROR Ontology does not conform to OBO structure rules:
multiple comment tags not allowed. in frame:Frame(IAO:0020015 id( IAO:0020015)property_value( IAO:0000117 Mathias Brochhausen xsd:string)def( A personal name is a proper name identifying an individual person.)comment( Personal names "today usually comprises a given name bestowed at birth or at a young age plus a surname. It is nearly universal for a human to have a name; except in rare cases, for example feral children growing up in isolation, or infants orphaned by natural disaster for whom no written record survives.[citation needed] The Convention on the Rights of the Child specifies that a child has the right from birth to a name. Certain isolated tribes, such as the Machiguenga of the Amazon, also lack personal names." (http://en.wikipedia.org/wiki/Personal_name))property_value( IAO:0000119 http://en.wikipedia.org/wiki/Personal_name xsd:string)comment( Sep 29, 2016: The comment that including the wikipedia definition of personal name is not to be interpreted in a way that restricts this class to only contain strings of letters. A numerical or alphanumerical identifier that denotes a human is being is a personal name, too. (MB))property_value( IAO:0000412 http://purl.obolibrary.org/obo/iao/pno/release/2020-04-18/pno.owl xsd:string)name( personal name)is_a( IAO:0020000)intersection_of( IAO:0020000)intersection_of( IAO:0000219 NCBITaxon:9606{{all_only=true} }))
For details see: http://robot.obolibrary.org/errors#obo-structure-error
Use the -vvv option to show the stack trace.
Use the --help option to see usage information.

More possible action-automatic-releases supported-parameters


Revert "[SLM] Allow modules to define pre-processing of weights"

Reverts apache/tvm#16757

@tqchen Can you add a unit test demonstrating the behavior to be retained?  Is it only for the string names of symbolic variables, as mentioned in this comment?

Likely i think it would be primarily two parameters with same vocab_size as the dynamic shape.

Happy to also test followup redos of the PR in case we miss other cases

I replied with a test to the other PR before noticing the on-going thread here. https://github.com/apache/tvm/pull/16757#discussion_r1536887971
@tqchen so could you help pasting it into test_frontend_nn_modules.py? Then we don't need a separate PR for the test.

Merged without the unit test to keep the reversion standalone. Let's add the test case separately. Thank you folks!

I have a parametrized version of the test case, along with testing for cases beyond nn.Linear, that I'll open as a PR.


Add a healthcheck endpoint on the ingesters that distributors can use

This puts a Check endpoint into the ingesters that allows our ingester clients to do a healthcheck loop to make sure their connection is still ok. As part of the maintenance loop to remove stale ingesters, we will now also (in the background) healthcheck each remaining ingester, and if it is not ok delete the entry in distributor.clients. The client will then be remade the next time it is needed by getClientFor.
A couple questions:

As it stands the ingesters need to be upgraded before the ruler/distributors/querier, or else the healtchecks will constantly fail and we will be recreating a lot of grpc clients. Everything will still work, but the logs would be noisy/extra work will be done. Is that a concern for those with CI systems? If so how should it be addressed?
The Check endpoint is based off https://github.com/grpc/grpc/blob/master/doc/health-checking.md. Is that what we want? Or should we make an endpoint that is more ingester specific?

Another solution would be to just periodically close the ingester clients, perhaps put an age field on them and only use them until then.
This PR fixes: https://github.com/weaveworks/cortex/issues/702

This has been running for more than a day in staging, and is now running in our prod cluster.
Started restarting gRPC clients ~17:00 on 3/10

As it stands the ingesters need to be upgraded before the ruler/distributors/querier

General approach to this is to hide the behaviour behind a flag that defaults to off; new code gets rolled out with the behaviour off, then a flag changed can be rolled out to enable it.

From staging, started restarting gRPC clients ~17:00 on 3/10

Oh dear - I'm fine with fixes like this going in work around other issues, but do you have any idea why gRPC is getting so unwell?

Does this help with #157 - use this endpoint as the heartbeat instead of the consul timestamp?

Does this help with #157 - use this endpoint as the heartbeat instead of the consul timestamp?

Not as it stands (ingester clients will be created on demand), but it could be made to do so...

@tomwilkie Thanks for the comments!
I wish I knew why gRPC is getting so unwell, I have been banging my head against a wall for awhile about this. If you or someone else have any ideas I would be happy to test them out.
Also, do you think there is anything we could do in this PR to make it easier to heartbeat with respect to #157? I don't want to do all the work for that here, but would be happy to make it easier in the future.

If you or someone else have any ideas

No ideas, but we had something similar with Bigtable; I just added a timeout and it unstuck it.  Are the ingester timeouts working okay?

is anything we could do in this PR to make it easier to heartbeat with respect to #157?

The two systems are quite decoupled right now; lets get #279 merged and see what shakes out.

Sounds good on waiting for #279. The ingester timeouts seem to be working ok, but every request will start timing out after 2s (push) or 10s (query), and that ingester connection never manages to correct itself.

The ingester timeouts seem to be working ok, but every request will start timing out after 2s (push) or 10s (query), and that ingester connection never manages to correct itself.

Is it worth destroying clients that experience a timeout then?

Yeah, just as a thought...

It would work, and was something I was considering, but liked the healthcheck a bit more. I am happy to rework it based on what everyone thinks though.
Pros:

No extra endpoint
Would find an error on the first time, rather than waiting for up to 15s

Cons:

Any future endpoints on the ingester would need the same handling, this could be abstracted but there would still be some entry function needed.
Putting it in the maintenance loop keeps the maintenance code together
Less straightforward to implement something like "restart if healthchecks fail for x time or y number of requests"
Long queries/pushes could cause a false positive (seems unlikely though)

You had me at "Any future endpoints on the ingester..."

I think its looking much easier to follow wrt locking and concurrency.  A couple of comments, then we should be good to go.
It might also be worth extracting all this to a separate file (and even package), as there is starting to be enough logic to justify it.

Yeah, the more I think about it the more I like the idea of putting it in pkg/ingester/client as a "client cache".

Also, would you mind enabling CircleCI on your fork so we get test runs?  It should be free.

I've done a pull/push to weaveworks/cortex so we get one test run now.

I did the refactor, and definitely think it cleans up distributor quite a bit. I also moved utils/compat to the ingester/client package since otherwise ingester/client could not import utils due to a circular dependency.
Right now the loops for cleaning up stale clients, and health checking each client remain in distributor.go in order to not complicate what should just be a cache. If you want me to move those into the client package I can do that.

Not sure what's wrong with my circle ci yet... hopefully I will get some time to look at it tonight/tomorrow morning.

@bboreham or @tomwilkie Another review would be great when you get a chance!

PR description updated


aq.py ignores system-wide conf file if run from the sources

In 1.12.60, aq.py intentionally ignores  the system-wide conf file if a Makefile file is found in the parent directory of the script (typically means run from the source tree).  Would it be acceptable to have an option on the command line (and possibly in the system-wide conf file) to enable this behaviour rather than having it as the default?

the "typical" deployment is a git clone? really? doesn't aquilon do releases?

@stdweird yes, but releases do not imply packages or anything else other than a defined point in a commit tree

@jrha i meant releases on pypi and such. anyway, is this also an issue with the rpms?

:man_shrugging:

I suspect there are two cases where this could be important:

Running the unit tests.
Running development instances, it is important that the developer does not accidentally run commands against the real production instance.

It may be better to do as @stdweird suggests and ensure the client is run from a properly packaged instance instead of a source tree that may be ahead of the running broker.

I think my point/issue is a little bit distinct from the packaging. Yes it would be great to have a PyPi package for Aquilon but honestly, having doing it as documented with a Git clone, I don't see any major issue and it has also its advantages in this phase where things evolve quicly: easy to test changes, rollback, run PRs not yet committed...
My point is about the default behaviour regarding the config file location. Currently, there is a line that makes the heuristic to decide (silently) the path of the config file completely different whether you run from the source tree or not. And I find this behaviour at least discussable and possibly a source of pain when troubleshooting problems. I understand the intent but I am not convinced that the default behaviour should be for running unit tests as this is a context generally involving a script where it is easy to pass a command line option to say that you are in this context and wants some things to be done differently. As for a development instance, it is something that is normally installed and configured on a more permanent basis and you can ensure that you have the proper config files for it.
That said, I'm attached to backward compatibility and there was a choice made a while ago. I'd like to minimize the changes to this behaviour but still fixing the current behaviour that I find not really appropriate : you can install only from the Git repo but to have the client working as expected (with a system-wide config file outside the source tree), you have to delete the Makefile that is part of the repo, meaning that if you want to take advantage of the fact that you have a Git repo, you have a great chance to make a mistake and commit this removal. Thus the fixed that I proposed in #99 which consists to keep the current behaviour for locating the config file for aqd daemon and everything else except the client (aq.py) as only the client is really impacted by the current behaviour. In case of the client it is still possible to use an explicit broker with the appropriate global option or the env variables and the risk of doing something wrong should be limited by the authorization involved in passing the commands. If it is seen as desirable, it would be easy to add a global option like --development that would implement the current behaviour (ignore system-wide config file).
As explained in #99, the real source of the problem for the client is that the source path is returned unconditionnally if the source tree (the Makefile) is detected, whether it contains an aq (client) config file or not. Another approach (that I'm happy to implement if it is thought better!) is to return the source tree path only if contains a config file (which is not the case by default). As in the current PR, it could be done only for the client (with the use a new argument to lookup_file_path().

Thanks for the detailed reply. I am not opposed to this change in anyway, was just trying to explain why the current behaviour might have seemed desirable (although changing  something "silently" is almost always wrong). I will leave this to the determination of active developers such as @urbonegi who have to be careful to avoid running commands against production!

Thanks! As I said, the PR is the beginning of an attempt to make the life in production easier... I'm really ready to improve it to make easy to ensure that you are not running against the wrong broker because you used the wrong config file, in particular by adding a global option like --ignore-system-config. I'm looking forward @urbonegi feedback.

If we introduce these changes that means that every developer who have their dev environment will have to always export aqhost/aqservice to make sure they hit their dev server not production. It is too bit overhead and will definitely cause us hitting prod endpoints by accident quite often. Having default behavior after git clone to use localhost as dev server is best solution. Please note that MS have shared FS - if we start looking at the conf files elsewhere than source code - we endup with prod endpoint defaults.
The easiest way for you to move forward is just not use same bin/aq.py in the source code directory (use the fact that aq server and client are completely separated). Just have additional - 'prod' deployment with bin/aq which is installed as rpm or some custom Makefile and does not contain Makefile itself :) then if you use bin/aq to call Aquilon server it will not default to source code dir but rather will look for aq.conf in root directories first (/etc/aquilon and /usr/share/aquilon/etc). Moreover, it make sense to use aq.conf which is in code source dir if one runs bin/aq.py from source code dir...

@urbonegi may be my issue description was not clear enough but the problem that I see is that there is no aq.conf in shte source tree by default. So returning the source tree as the location for the config file unconditionally is not completely consistent. You could imaging to create one as part of the Makefile for example. I don't think that it necessarily requires a developper to define env variables. But clearly it will change a little bit the behaviour...
I'll try to update #99 with the other approach I proposed to better illustrate how it could work. Installating Aquilon client with something else than a Git clone would work, just it doesn't exist today! If there is not any change acceptable for you, we can certainly live with a local workaround. Note that the current behaviour is not a problem when the client runs on the same machine as the broker but when you want to install it on another machine (because the default localhost doesn't work).

You have 3 options to fix this:

Have a aq.conf in the source code and just adding a line in .gitignore to ignore it. The aq.conf is internal and custom per organization so it cannot be pushed to github code repo.
'Deploy' the source code to new dir (remove the Makefile), then you can use the aq.conf in /etc/aquilon and not one in source code dir. You can just simply always use that to call any aqd server :) client code changes not so often so you can have it separately sitting somewhere else. You can even create and alias for 'aq' to call the correct path of the client script.
You could just pass the --aqconf _path_to_client_config which fixes your problem :) this seems more appropriate than introducing new option --devmode which creates risk for us :)

Probably options 1 and 2 are acceptable but they are still workarounds (option 1 will be acceptable if we can commit the modified .gitignore). option 3 is not more acceptable than it is for you to add an option everytime you run àq.pyin development mode... I'm still trying to find a solution acceptable for you (I understood that it means a solution changing nothing for you) and fixing the default behaviour for other sites.  Thinking a little bit more about it, that is was may not desesperate :smile: Currently, when noMakefile` is detected, the config file search path is (from https://github.com/quattor/aquilon/blob/c9495232e1460d832b81e71c4bdd92f8b9936599/lib/aquilon/config.py#L61):
/etc/aquilon
/usr/share/etc/aquilon
$SRC_DIR/../../../aqd-vcs/prod/etc
$SRC_DIR/etc

If I understood properly, MS is not using /etc/aquilon and /usr/share/etc/aquilon but rather $SRC_DIR/../../../aqd-vcs/prod/etc that nobody else uses. And that it is this directory that must be ignored for a change not have any impact on you. Is is right? If yes, I'd propose to implement a modified lookup_file_path() where, if the Makefile is detected, the directory $SRC_DIR/../../../aqd-vcs/prod/etc is ignored and $SRC_DIR/etc is inserted first in the list. This way, the change would have no impact on MS and for other sites, if you want to have a specific setting for you development instance you could have an aq.conf in the source tree that would take precedence over the system-wide one.
Would this be acceptable ?!

@jouvin Acceptable to us does not mean "change nothing", it means "fail safe by not talking to production if a developer has checked out the source tree".  That's a good thing for everyone, not just us, and also using the aq client from HEAD is incompatible with talking to an older broker version.
I think deploying code via git clone is actually a pretty good deployment mechanism.  But that's not to say that "git clone" is the only step. @urbonegi's options (1) and (2) are straightforward to implement in quattor. For (1), you are already delivering an aq.conf to /etc/aquilon (I assume via quattor) so this just requires to change the destination to the location of your aq client directory. (I'm not even sure you need a .gitignore file: but if it's necessary then filecopy can add it.)
For (2), @urbonegi tells me you just need two files (aq.py and input.xml) so you filecopy those from your clone to /usr/local/bin (or whatever is convenient for your $PATH). Then your update procedure is something that does:
cd /usr/src/aquilon
git checkout $new-tag
ncm-ncd --configure filecopy

@urbonegi is taking a look at your most recent proposal. We do also use /etc/aquilon in newer environments but she will take a look to see if there a combination that works.

Thanks! I'm waiting for @urbonegi's feedback on my last proposal (not yet implemented!). The client deployment is not difficult, you are right, but it is a little bit more than the files you mentioned. At least lib/aquilon/config.py is missing. At some point it may be good to have the exhaustive list somewhere...

@jouvin  Sorry to take so long to respond - I was occupied by some internal work. So although your solution sounds good @jouvin it will also not work for us, as we use the directories mentioned. We ship /etc/aquilon/aq.conf with a help of quattor templates to aquilon hosts so that they can communicate with the aqd. I think at the end state you can also achieve that as well. Reading what @ned21  and you suggested the best approach is this:

Have your aqconf managed in separate internal project.
As part as aqd deployment do git clone of the main source code and the aq config project (anywhere you like)
Add symlink in your aqd/etc/aq.conf which points to your aq conf project aq.conf file
Submit PR for us to add etc/aq.conf to .gitignore
I think that would be best and require leas changes for everyone habits..
Alternately:
-Use aq.conf what will be deployed in /etc/aquilon/aq.conf - but just delete Makefile so that 'devmode' test will return False. This requires no changes at all :)


how to use onclick methods?

Is there any way to use :click="method" when notification appear?

In case you're still looking for a solution, you can use the .native event modifier:
<notifications @click.native="onClick" />


docs: Fix path to REST endpoints index

The path in the tutorial was incorrect.

Testing Plan:
GIFs or Screenshots:

Merged, thanks @kklin!


Feature request: Tab bar UX improvements

This regards the main element tab bar, but it might also be applicable to element editor (e.g. mapping editor) tab bars.

[x] https://github.com/finos/legend-studio/issues/130
[x] Support translating vertical to horizontal scroll for tab bars: use onWheel event to catch scroll event and then translate that to horizontal scrolling - see vscode for example - solution in https://github.com/finos/legend-studio/pull/1711 is not complete <-- this turns out to be not so trivial, also users can use Shift + scroll to translate vertical to horizontal scrolls
[ ] #1952

Here we should follow the behaviour of Chrome. Let's say if we have the following tabs:
a,b,c,d,e
If we open a new tab from c, we will have:
a,b,c,f,d,e
The order of tabs being opened will also help us find tab to switch to when we close a tab
Also, with this, we can support `go back` feature and support `open last closed tab` feature

[x] Apply changes in https://github.com/finos/legend-studio/pull/1711 to mapping editor

@xannem I think point (2) is very doable, and I know I told you about not doing point (3), but the right way to do it I think is implement a naive address system in Legend Studio where we will just store the history as a stack of addresses, instead of the actual tab state (<- this is dangerous! can cause mem-leak)

Will close this for now as the majority of the work is done by #1711


Format repo

Update eslint and prettier
Format js/ts code

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

Project coverage is 91.75%.  Consider uploading reports for the commit cf2b42c to get more accurate results

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #120      +/-   ##
==========================================
- Coverage   91.78%   91.75%   -0.04%
==========================================
  Files          13       13
  Lines         499      497       -2
  Branches      142      140       -2
==========================================
- Hits          458      456       -2
  Misses         41       41

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


exception 'InvalidArgumentException' with message 'There are no commands defined in the "xxx" namespace.'

I'm getting this error:
[2014-08-24 20:19:02] staging.ERROR: exception 'InvalidArgumentException' with message 'There are no commands defined in the "trusty" namespace.' in /home/trustywebapp/public_html/stagingtrusty/vendor/symfony/console/Symfony/Component/Console/Application.php:516
Stack trace:
#0 /home/trustywebapp/public_html/stagingtrusty/vendor/symfony/console/Symfony/Component/Console/Application.php(550): Symfony\Component\Console\Application->findNamespace('trusty')
#1 /home/trustywebapp/public_html/stagingtrusty/vendor/symfony/console/Symfony/Component/Console/Application.php(190): Symfony\Component\Console\Application->find('trusty:log')
#2 /home/trustywebapp/public_html/stagingtrusty/vendor/symfony/console/Symfony/Component/Console/Application.php(124): Symfony\Component\Console\Application->doRun(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
#3 /home/trustywebapp/public_html/stagingtrusty/artisan(58): Symfony\Component\Console\Application->run()
#4 {main} [] []
This is what I put in the cpanel cron job:
php  /home/trustywebapp/public_html/stagingtrusty/artisan scheduled:run 1>> /dev/null 2>&1
Pls help.

This has been solved?
I'm trying to use Dispacher and I keep getting this error… I've already read all the comments as make all suggestion and still no luck.

@Caneco in my /app/config/packages/indatus/dispatcher/config.php I have
'executable' => '/usr/bin/php-cli'
Does that help?

@sparkeleven that really made the trick! Thank you!

@sparkeleven Thank, it solved!

if you dont find config files in app/config
rung: php artisan config:publish indatus/dispatcher

On the other day this happened to me with this issue…


web out of service

Hello,
I was wondering about the home page - http://imagepy.org but it seems that there is an issue to access this page:
This site can’t be reached imagepy.org’s server IP address could not be found.
Try:
    Checking the connection
    Checking the proxy, firewall, and DNS configuration
ERR_NAME_NOT_RESOLVED

Hi, last week, we translate the newest development document, and wrote a demo plugin repo here.


Add support for tracking

Codecov Report

Merging #64 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff          @@
##           master    #64   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files          30     31    +1
  Lines         243    246    +3
=====================================
+ Hits          243    246    +3

Impacted Files
Coverage Δ

src/letter-spacing.js
100% <100%> (ø)

src/index.js
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


add find bounding box functionality

Hey, I added this pull request but I haven't been doing ruby so long.
I'm happy to adjust if you have comments regarding the code quality.

Coverage increased (+0.1%) to 99.25% when pulling 98c29dc9d310d697afe984652d3c986f82a0be2e on leoroos:master into 5a01e85ad796f511c3f740ab496d192089bd548c on sozialhelden:master.

found, that I left some code that does not belong to the final commit


nvim-cm-php-language-server is using php language server

Is this a vim plugin? If yes, please write "Vim (extension name)"

This is a neovim plugin. Neovim (nvim-cm-php-language-server)


File Upload Error for Files Larger Than 2MB

Package
filament/filament
Package Version
v3.2
Laravel Version
v11.9
Livewire Version
v3.0
PHP Version
PHP 8.3
Problem description
When attempting to upload a file larger than 2MB using the file upload feature in Filament PHP, an error is encountered. This issue has been observed both in personal implementations and on the Filament demo site, specifically in the product create form.
Expected behavior
Files larger than 2MB should upload successfully without any errors.

Steps to reproduce

Go to the product create form on the Filament demo site or a similar form in a personal Filament implementation.
Attempt to upload a file larger than 2MB using the file upload feature.
Observe the error message or failed upload process.

Reproduction repository (issue will be closed if this is not valid)
https://github.com/filamentphp/demo
Relevant log output
No response

Donate 💰 to fund this issue

You can donate funding to this issue. We receive the money once the issue is completed & confirmed by you.
100% of the funding will be distributed between the Filament core team to run all aspects of the project.
Thank you in advance for helping us make maintenance sustainable!

Did you check your php.ini configuration?
Look for
Maximum allowed size for uploaded files.
upload_max_filesize = 60M
#Must be greater than or equal to upload_max_filesize
post_max_size = 60M
Here a tutorial on how to locate your current php ini file
https://codewithsusan.com/notes/php-configs-with-php-ini
After update those values remember restart NGINX or Apache services.


Update debian.md

Changed eol for Debian 11 (Bullseye)
Original release date was 2021-08-14 so security changes on 2024-08-14
(was originally scheduled for 2024-07-31)
Final point release for Bullseye is scheduled for 2024-08-31

updated according to
https://wiki.debian.org/LTS


Need some help with a rocket error

I got this error while opening up my Rocket server:
[Exception] Rocket.Unturned >> Exception in m__1: System.Exception: Failed to deserialize XMLFileAsset: Rocket.Unturned.config.xml ---> System.FormatException: Input string was not in the correct format
I know the error is in the rocket.unturned.config.xml but i dont know what is wrong!
MY Rocket.unturned.config.xml configuration:
log.txt

Your Rocket.Unturned.config.xml is malformed. Delete it or use an xml validator to find the error

It says "No errors were found"(xml validation)


DONOT merge. test-interactive-code

Description

Breaking change?

Example

Checklist

[ ] Unit tested updated code paths
[ ] Tagged 1 of @janniks or @zone117x for review

No longer relevant. Hence closing this.