Loading Unconditional Model Failure!!!

Version: 1.1.3
Type: BUG
When I use unconditional to interrupt training, loading the model again will cause the following error.
Traceback (most recent call last):   File "D:\Integrated-Design-Diffusion-Model\tools\train.py", line 408, in <module>     main(args)   File "D:\Integrated-Design-Diffusion-Model\tools\train.py", line 293, in main     train(args=args)   File "D:\Integrated-Design-Diffusion-Model\tools\train.py", line 156, in train     load_ckpt(ckpt_path=pretrain_path, model=model, device=device, is_pretrain=pretrain,     load_model_ckpt(model=model, model_ckpt=ckpt_model, is_train=is_train, is_pretrain=is_pretrain,   File "D:\Integrated-Design-Diffusion-Model\utils\checkpoint.py", line 115, in load_model_ckpt     model_weights_dict = {k: v for k, v in model_weights_dict.items() if np.shape(model_dict[k]) == np.shape(v)}   File "D:\Integrated-Design-Diffusion-Model\utils\checkpoint.py", line 115, in <dictcomp>     model_weights_dict = {k: v for k, v in model_weights_dict.items() if np.shape(model_dict[k]) == np.shape(v)} KeyError: 'label_emb.weight'
The model incorrectly loaded the weights in the conditional mode. I think there is an error here. Should we add conditional parameter to the load_model_ckpt() method in checkpoint.py?

Hi, @bestl1fe
Thanks for reporting this bug in this issue. 👍👍👍
I also found this bug in the recent test, and I have submitted the latest patch tonight, for details : #57. Please pull the latest code in this repository.


Dynamically generate controllers based on contents of assets

/retest

/retest

/retest

/retest

Review comments will be in future PR.
/lgtm


InstantApp: package not for download 26.0.0-rc2

You'll have to get the build tools from the canary channel.
From the CLI run sdkmanager "build-tools;26.0.0-rc2" --channel=3.

you need to use 3.0 canary for this one I guess.

thanks, @darkpiv  @keyboardsurfer it's working on android studio 3.0.


styled-components broken by #41841

Found by overnight DT run for #41841
Here's a standalone repro; it's not minimal but it doesn't depend on anything else.
interface FunctionComponent<P = {}> {
    defaultProps?: Partial<P>;
}
type ComponentType<P = {}> = FunctionComponent<P>;
export type KProps<C extends string | ComponentType<any>> =
    object extends object ? Omit<C, any> & Partial<C> : never;
export interface StyledK<C extends string | ComponentType<any>> {
    (props: KProps<C>): never
}
type Constraint<T extends ComponentType> = T ;
export type StyledComponentInnerComponent<C> = C extends StyledK<infer I> ? I : C;
export type SProblem<C extends ComponentType<any>> = C extends StyledK<any> ? Constraint<StyledComponentInnerComponent<C>> : number;

Expected behavior:
No error, as in 4.1.
Actual behavior:
Error in SProblem on Constraint<StyledComponentInnerComponent<C>>:
error TS2344: Type 'StyledComponentInnerComponent<C>' does not satisfy the constraint 'ComponentType<{}>'.
  Type 'string | ComponentType<any> | C' is not assignable to type 'FunctionComponent<{}>'.
    Type 'string' has no properties in common with type 'FunctionComponent<{}>'.
      Type 'string | ComponentType<any>' is not assignable to type 'FunctionComponent<{}>'.
        Type 'string' has no properties in common with type 'FunctionComponent<{}>'.

Here's a smaller repo. I think it better illustrates the problem:
interface StyledK<C extends string> {
    (props: {}): never
}
type Constraint<T extends { p }> = T ;
type Inner<C> = C extends StyledK<infer I> ? I : C;
export type SProblem<C extends { p }> = C extends StyledK<any> ? Constraint<Inner<C>> : number;

I guess before the string constraint on C from the outer C extends StyledK<any> ? ... got dropped? It kind of looks like this new error is correct.

I guess before the string constraint on C from the outer C extends StyledK ? ... got dropped? It kind of looks like this new error is correct.

Yes, that was the problem with not preserving substitution types in conditional types--constraints implied by outer conditional types were dropped. They're now preserved, which in this case reveals an error. If C is a StyledK<any> then Inner<C> is constrained to string | C, and string is not assignable to { p: any }.
BTW, I have no earthly idea what these types are supposed to be doing!

Presumably they made sense in situ. The standalone repro chops them up pretty badly. I'll go back to the original and try to figure out a workaround.
(There are nearby comments in the original along the lines of "I'm quitting now before my head starts hurting again." So.)

Later: It seems like the string constraint was a low-fi keyof JSX.IntrinsicElements substitute, because switching to that now compiles successfully. I'm afraid that it's going to be a lot slower though.
https://github.com/DefinitelyTyped/DefinitelyTyped/pull/50046


Update node packages

Fixes #2398
Updated node packages by simply check with node outdated.

Codecov Report

Merging #2451 (bf8adaa) into main (5d414d4) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #2451   +/-   ##
=======================================
  Coverage   81.83%   81.83%
=======================================
  Files         623      623
  Lines       22427    22427
=======================================
  Hits        18354    18354
  Misses       4073     4073

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 5d414d4...bf8adaa. Read the comment docs.


Add note about System.NET.Http breaking change

Summary
See this customer comment here:
https://developercommunity.visualstudio.com/t/https:learnmicrosoftcomen-usdotnet/10787012
https://learn.microsoft.com/en-us/dotnet/core/compatibility/sdk/8.0/implicit-global-using-netfx
I'm not sure how important it is to include the breaking change in the primary documentation so I'll defer to the doc folks but putting this PR out as a proposal.

Internal previews

📄 File
🔗 Preview link

docs/core/project-sdk/overview.md
docs/core/project-sdk/overview

Since .NET 6/7 are no longer supported, it might just be better to remove System.Net.Http from line 132 and 136.

@gewarren the nuance here is that in the .NET 8 SDK, System.Net.Http was removed from .NET Framework targeting (eg. net472 targeting). It's still included if you target net8.0 or net9.0. I wasn't sure the best way to include that distinction in the documentation.


jqlite returns incorrect value for boolean attributes in some cases

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

What is the current behavior?
jqlite.attr(attrName) returns the lowercase version of attrName if the element has attrName set as a property. See the discussion in https://github.com/angular/angular.js/issues/14115

What is the expected behavior?
jqlite should always return the actual attribute value like jquery does.

What is the motivation / use case for changing the behavior?
mainly consistency with jquery, because this behavior doesn't seem to cause issues outside of tests.

Which version of Angular, and which browser and OS does this issue affect? Did this work in previous
versions of Angular? Please also test with the latest stable and snapshot versions.
all versions up to 1.5.0

I'll do it as part of the other jQuery changes for 1.6.0.


update login.js

Title of the Pull Request

[ ] Have you renamed the PR Title in a meaningful way?

Related Issue

Closes: #
Description

How Has This Been Tested? ⚙

Screenshots 📷

Type of change
What sort of changes have you made:

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Code style update (formatting, local variables)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Checklist

[ ] My code follows the code style of this project.
[ ] I have followed the contribution guidelines
[ ] I have performed a self-review of my own code.
[ ] I have ensured my changes don't generate any new warnings or errors.
[ ] I have updated the documentation (if necessary).
[ ] I have resolved all merge conflicts.

This solves which issue ??


Fuzzy matching

There should be a way to check output in a more flexible manner, such as by using a regex, or an array of possible values.
A couple possible implementations off the top of my head could be:
/// Match against any in a vec
assert_cli!("shuf", &["-i", "1-2", "-n", "1"] => Success, &["1", "2"]);

/// Match with regex
assert_cli!("shuf", &["-i", "1-99", "-n", "1"] => Success, r"[0-9]+");

I agree, this is a feature that would come in really handy. Like I mention
in the other issue, I'd like to have it behind a cargo feature though (to
not force the regex dependency on everyone).
I'm not sure how you'd differentiate between normal and fuzzy matching.
Prefixing a string literal with an r means it should be treated as a raw
literal (no escape sequences), so I don't think we can use that. Maybe use
~> instead of =>?
Linden Krouse<EMAIL_ADDRESS>schrieb am So. 10. Juli 2016 um
17:23:

There should be a way to check output in a more flexible manner, such as
by using a regex, or an array of possible values.
A couple possible implementations off the top of my head could be:
/// Match against any in a vec
assert_cli!("shuf", &["-i", "1-2", "-n", "1"] => Success, &["1", "2"]);
/// Match with regex
assert_cli!("shuf", &["-i", "1-99", "-n", "1"] => Success, r"[0-9]+");
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/killercup/assert_cli/issues/8, or mute the thread
https://github.com/notifications/unsubscribe/AABOX-Jx3CMrV35xYL3RmlJ0Vtwy-Kkmks5qUQ6JgaJpZM4JI2vu
.

Of course.
I agree that prefixing it with r is not a great idea, I just wanted to make the issue so it wasn't forgotten. ~> sounds like a good idea, although it might be a little difficult to pick out since it isn't part of the output-to-match argument, but I like the flavor of it. Prefixing with regex might be too verbose, what about prefixing the output string with ~?
/// Match with regex
assert_cli!("shuf", &["-i", "1-99", "-n", "1"] => Success, ~"[0-9]+");


Fix information leak in rsa padding check

The memory blocks contain secret data and must be
cleared before returning to the system heap.
This PR is for the 1.0.2 branch

Merged to 1.0.2 branch as 57ad215.
Thanks!


Rake aborted! SystemStackError:stack level too deep

While migrating database an error occurred, i already tried
bundle exec rake db:migrate

You won't believe I have spent around 22hrs on installing FuzzAPI and fixing errors from the beginning . And this the final one i guess!
Installed Components:
Ruby 2.4.0p0 (2016-12-24 revision 57164) [x86_64-linux]
Rails 3.0.11
Bundler version 1.17.3

Same error +1

same here


Strip leading zeros

Hi — thanks for writing this lovely tool.
While using it I found an interesting bug while comparing different versions of Docker:
→ ./semver2.sh 18.09.1 18.04.1 debug
./semver2.sh: line 83: 04 - 09: value too great for base (error token is "09")
DEBUG: Detected: 18 09 1 identifiers:
DEBUG: Detected: 18 04 1 identifiers:
DEBUG: MAJOR are equal
DEBUG: MINOR is different

Essentially the error occurs because the shell interprets numbers with a leading zero as (poorly formed) octals — example using bash 3 in posix mode:
$ echo $BASH_VERSION
3.2.57(1)-release

$ echo $((04 - 09))
sh: 04 - 09: value too great for base (error token is "09")

$ echo $((0x4 - 0x9))
-5

I'd like to suggest a fix — after a little bit of poking on SO I think the simplest solution to stripping the leading zeroes might be to just pipe to bc

Shoot, thought bc was standard library but apparently isn't available oob on Ubuntu
$ semver2 18.04 18.09
/usr/local/bin/semver2: 143: /usr/local/bin/semver2: bc: not found

hey @mfdj thanks for commenting and attempting to fix.
Unfortunately this is not a problem of this library, it is a problem with docker it self. Docker versioning does not meet SEMVERSION 2.0 schema.
Please check the rules: https://semver.org/#spec-item-2
A normal version number MUST take the form X.Y.Z where X, Y, and Z are non-negative integers, and MUST NOT contain leading zeroes.
But maybe i could think to create a special version to handle Docker versioning 👍  i will think about that once having time at weekend.

@Ariel-Rodriguez aha — thanks for the through explanation! I didn't realize leading zeroes weren't allowed (makes perfect sense though)
Thanks again for this great library!


how to get cell value by index number of w2ui selected row.

grid.records[index] - will return you entire record. Cell value is part of it. Please submit only bugs here in the future


Docs Update Required - When setting up a contract

We need to add a reminder in the main guide to let the developer know that they need to unlock their wallet after restarting their eosd node.

Public wiki to be updated this week and will include a note on this in the CLI Wallets section.  Note that this is an issue related to restarting your wallet manager, which could be either nodeos or keosd.

great, thanks for the update @rbw3821


Fix column range filter

This fixes issue #1001.
I added defensive null checks, unit tests and integration tests.

LGTM! Glad to see the thorough new tests.


No command to clear keybindings search history

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

VS Code Version: 1.67.2
OS Version: Windows 11

Steps to Reproduce:

Open the Keyboard Shortcuts editor (e.g., by using the Ctrl+K Ctrl+S keyboard shortcut).
Enter something into the search bar in the Keyboard Shortcuts editor.
Clear the search field (e.g., by pressing escape).
Press the up arrow key. The previously entered search term repopulates the search field.

Expected Result:
There should be a way (ideally through a command in the command palette) for users to clear the keybindings search history. This would provide a consistent experience with clearing search history for the find in files (Ctrl+Shift+F) view (where it is also possible to use the up/down arrow keys to cycle through search history), through the Search: Clear Search History command.
Actual Result:
Currently, the only way to clear the keybindings search history would be to open the global state database (located at %APPDATA%\Code\User\globalStorage\state.vscdb), locating the momento/workbench.editor.keybindings key in the ItemTable table, and clearing the "searchHistory" array (see screenshot below).

Hey, I want to start with contributing to opensource projects. Is it okey if I look into this pr?

Sure. That would be great.

Microsoft Open Source Code of Conduct
This project has adopted the Microsoft Open Source Code of Conduct.
Resources:

Microsoft Open Source Code of Conduct
Microsoft Code of Conduct FAQ
Contact<EMAIL_ADDRESS>with questions or concerns


[DPE-2944] kibanaserver user

IGNORE failing lint tests, as they will get green as Temporary Solution is resolved
Issues
kibanaserver user doesn't exist
Opensearch Charm has a particularly strict user management.
At start ALL users are deleted.
Then, one-by-one they are "re-added" back (such as admin) -- or brand-new ones may be created (such as COS monitor user).
We are planning to use the system kibanaserver user for Dashboard access, as it seems the most stable and resilient solution.
kibanaserver user with password should be available to Dashboard
On a particular, specific relation request (from the Dashboard Charm), the Opensearch Charm should provide the kibanaserver
user credentials (via Juju Secrets).
Solution

We "re-add" the freshly deleted kibanaserver user.
NOTE: unlike the original, the new one will have reserved: false set, in order to allow for password changes.

We alter the charm's current OpensearchProvider interface, so that it recognizes the kibana_server request as an extra_user_role. When this role is requrested, instead of creating a new relation user, the Opensearch Charm returns the kibanaserver user's credentials.

NOTE: This PR is also providing a fix for https://github.com/canonical/opensearch-operator/issues/246
Temporary solution
NOTE: Currently the PR is copying over the correct version of the opensearch-dashboard-operator charm to use it in the pipelines. THIS IS TO BE REMOVED BEFORE MERGE, being blocked on https://github.com/canonical/opensearch-dashboards-operator/pull/1 to be merged first.
NOTE: The lint tests will go green at this point

I think we can keep treat the kibanaserver user at the same level of admin and not delete it but rather change its password / hash and store it in internalusers.yml - we can also keep it as reserved: true and we'll still be able to rotate the password later on with the REST Api

To my understanding admin IS deleted.

Ah! And admin isn't reserved...

No we can't: As you find in my PR they appear with different parameters in internal_users.yaml, they are quite different.
I don't like the current solution, but it's no worse than hanving a
def create_internal_user():
    if username == 'kibanaserver':
        <do this>
    if username == 'admin':
        <do totally different>

So far the current approach (that I'm far from happy with) was the most elegant way to unite common code, and distinguish where needed.

Also note that we treat secrets different for admin as for others (as we're also saving the password hash, which we don't need for others)

@Mehdi-Bendriss FYI I also added a solution for https://github.com/canonical/opensearch-operator/issues/246 in this PR at the end.
This was the most convenient way, due to how secrets interactions are designed.
Turns out if we don't fetch a charm internal secret, we're not gonna get secret-changed events about it. (See https://matrix.to/#/!wJiiHsLipVywuWOyNi:ubuntu.com/$y-BhyxlsJvxTjYp68JgdAbL6DSN8W8nhug6ICSgyi7w?via=ubuntu.com&via=matrix.org&via=beeper.com)
The most convenient way to "initial fetch" secrets in question was to fix the issue. As we initialize internal_users.yml correctly, we fetch and use the <user>-password-hash secrets for the first time on all units. Thus when rotating these credentials all units will get notified of the secret change, and be able to correctly maintain their internal list of users.


Per-key actor epochs for vnode vclock entries

See basho/riak_kv#679 and the associated platform_task RFC and summary.
This PR addresses the "doomstone", backup-restore, and some byzantine flavours of the kv679 bug.
The RFC explains the mechanism in detail but briefly:
add a persisted to disk vnode counter (persisted with leases, aysnc)
when ever a key is written to for the "first time" by a vnode, create an epoch actor for the key by concatenating vnodeid+counter (and increment the counter)
This ensures that a first time write for a key gets a new actor, this is the epoch for the key. It means we don't mix up deleted+re-created keys {a,1} event with the original {a, 1} event for some key, by ensuring an actor per epoch, without causing a keyspace wide actor explosion.
There are riak_tests at https://github.com/basho/riak_test/tree/rdb/gh-kv679

This has been long running work, there is a PR here basho/riak_kv#1040 and here basho/riak_kv/pull/1053 that are closed in favour of this.

[ ] review
[ ] benchmarking
[ ] riak_test review
[ ] add Kelly's EQC test

I have set to 20seconds, you think more?

If there's a buffer flush storm, or if the disk hardware is stuttering, then 20 seconds might or might not be enough.  Other reviewers, do you have opinions?

I've looked through the other diffs, +1 from me.

I'm seeing the following failure when running make test for riak_kv on this branch.
Failures:

  1) riak_kv_schema_tests:commit_hooks_test/0
     Failure/Error: ?assertEqual({error,apply_translations,{error,[{error,[84,114,97,110,115,108,97,116,105,111,110,32,102,111,114,32,39,114,105,97,107,95,99,111,114,101,46,100,101,102,97,117,108,116,95,98,117,99,107,101,116,95,112,114,111,112,115,46,112,111,115,116,99,111,109,109,105,116,39,32,102,111,117,110,100,32,105,110,118,97,108,105,100,32,99,111,110,102,105,103,117,114,97,116,105,111,110,58,32,105,110,99,111,114,114,101,99,116,32,104,111,111,107,32,102,111,114,109,97,116,32,39,106,115,76,79,76,39]},{error,[84,114,97,110,115,108,97,116,105,111,110,32,102,111,114,32,39,114,105,97,107,95,99,111,114,101,46,100,101,102,97,117,108,116,95,98,117,99,107,101,116,95,112,114,111,112,115,46,112,114,101,99,111,109,109,105,116,39,32,102,111,117,110,100,32,105,110,118,97,108,105,100,32,99,111,110,102,105,103,117,114,97,116,105,111,110,58,32,105,110,99,111,114,114,101,99,116,32,104,111,111,107,32,102,111,114,109,97,116,32,39,98,97,100,58,109,111,100,58,102,117,110,39]}]}}, Config)
       expected: {error,apply_translations,
                     {error,
                         [{error,
                              "Translation for 'riak_core.default_bucket_props.postcommit' found invalid configuration: incorrect hook format 'jsLOL'"},
                          {error,
                              "Translation for 'riak_core.default_bucket_props.precommit' found invalid configuration: incorrect hook format 'bad:mod:fun'"}]}}
            got: {error,apply_translations,
                     {errorlist,
                         [{error,
                              {translation_invalid_configuration,
                                  {"riak_core.default_bucket_props.postcommit",
                                   "incorrect hook format 'jsLOL'"}}},
                          {error,
                              {translation_invalid_configuration,
                                  {"riak_core.default_bucket_props.precommit",
                                   "incorrect hook format 'bad:mod:fun'"}}}]}}
     %% test/riak_kv_schema_tests.erl:278:in `riak_kv_schema_tests:-commit_hooks_test/0-fun-0-/2`

  2) riak_kv_schema_tests:correct_error_handling_by_multibackend_test/0
     Failure/Error: ?assertMatch({ error , apply_translations , { error , _ } }, Config)
       expected: = { error , apply_translations , { error , _ } }
            got: {error,apply_translations,
                     {errorlist,
                         [{error,
                              {translation_invalid_configuration,
                                  {"riak_kv.multi_backend",
                                   "Error processing multi_backend configuration for backend default"}}}]}}
     %% test/riak_kv_schema_tests.erl:305:in `riak_kv_schema_tests:correct_error_handling_by_multibackend_test/0`

@andrewjstone Those are fixed by #1071.

Thanks @seancribbs
On Thu, Jan 8, 2015 at 6:34 PM, Sean Cribbs<EMAIL_ADDRESS>wrote:

@andrewjstone https://github.com/andrewjstone Those are fixed by #1071
https://github.com/basho/riak_kv/pull/1071.
—
Reply to this email directly or view it on GitHub
https://github.com/basho/riak_kv/pull/1070#issuecomment-69270074.

@russelldb This PR looks very good. I've gone over all the code and ran the eqc test a few times. Tomorrow I will go over the corresponding riak_test PR and run that against this code.

Arrggh. I messed up. Need to re-do that change, hold off re-review for now

Urgh, I went and rebased again. And I don't know how to "unrebase" and I don't want to force push. Give me a bit of time to wrestle with the tools here.

there we go

:+1:  d77f65f
riak_tests specific to this pass. So do dt tests and sibling explosion tests. Code looks good as well.

I was checking this over to see if you had already inserted a metric for when the epoch increments (or leases granted, etc), and found you have a stray file in the PR, test/vnode_driver.erl~. I'll make a separate task for the metrics but removing that stray file would be good, then we can re-approve and merge.


Miss-formatting LESS file

Hi, the plugin so far works great. Today I found an issue that took me a lot of effort to understand.
#main > header.big-menu nav ul.level-3 > li > ul li div a:hover {
    &:extend(#main > header.big-menu nav ul li > a: hover);
}

Beautify added a random space in that piece of code, within a LESS file of over 1000 lines, making it impossible for me to compile it and even harder for me to understand what was wrong.
For some reason, Beautify added a space in "a:hover", making it be "a: hover", therefore rendering it invalid.
Please check that error, because probably I'm not the only one who had a hard time with it.
Thanks!

You are not the only one.
I think this is a duplicate of #618.

@edoher  I believe this is fixed in 1.6.4.  Please reopen if it is still present.


Bootstrap border colours

Description
In this issue i will be describing all the border colours that bootstrap provides.
Domain
Frontend Dev HTML/CSS/JS
Type of Contribution
Documentation
Code of Conduct

[X] I follow Contributing Guidelines & Code of conduct of this project.

/assign


#33 Feature: CRUD operations for bus

What does this PR do?

CRUD operations for bus
Dashboard Layout

Description of Task to be completed?
As an operator, I want to create, update, and delete buses so that they can be put or removed to/from use.

The operator should be able to create, update, and delete a bus.
The operator should be able to view a paginated list of buses in the system.
Users should be able to view the bus's details.
Skeleton UIs/screen are/is shown when the page loads/is loading.
The page is responsive.
Appropriate error messages are displayed on unsuccessful attempts

How should this be manually tested?

Clone the repo

checkout to branch ft-crud-operations-for-buses-33

pull the changes by git pull

install all packages by running npm install

start app by running npm run start

Any background context you want to provide?
N/A
What are the relevant pivotal tracker stories?
Trello Board
Screenshots (if appropriate)

Questions:
N/A

@PrinceNiyonshuti, Try to solve that conflict

Thanks @tysepa , the conflicts have been solved


How to influence the json encoding/decoding? JsonViews possible?

Hi, i guess the wamp client use Jackson 2 to encode/decode the parameters to and from json? Is it possible to make use of JsonViews? I dont know where i could pass which view to use for each call. The documentation says 'for more complex data structures you might need to use annotations to instruct the serializer.' Does anyone have some examples for that or a helpful link?

You can pass a custom ObjectMapper to the WampClientBuilder in order to influence de/encoding. I don't know what JsonViews are, so I can't help you there. Regarding Jackson version: Best thing is to look it up in the dependencies of the library - don't know it out of my head :)


Datasync improvements #2526

Some enhancements to DataSync code:
Added task metadata
Added update_task mock
Also changed Travis.yml so that lint checks are done before the build.
This (should) speed up CI/CD by failing the Travis build if linting is not correct

I still need to test if the change to .travis.yml has the intended effect. Will intentionally introduce a linting issue to confirm

Coverage decreased (-0.004%) to 93.666% when pulling 6fa691af01996f6f5ae684ad4f6d9876b3129daf on baolsen:datasync-improvements into b19abbc63ec2dbaa7802c783942e5925f84aa3b2 on spulec:master.

Coverage decreased (-0.004%) to 93.666% when pulling 6fa691af01996f6f5ae684ad4f6d9876b3129daf on baolsen:datasync-improvements into b19abbc63ec2dbaa7802c783942e5925f84aa3b2 on spulec:master.

Comparing these build attempts:
Before: https://travis-ci.org/spulec/moto/builds/607196025?utm_medium=notification&utm_source=github_status
After: https://travis-ci.org/spulec/moto/builds/607637939?utm_medium=notification&utm_source=github_status
The travis.yml change works well, reducing build time (for incorrectly linted builds):
2min20 vs 9m30
3min26 vs 15min55
Time saved: ~20min
Might be worth adding 'make lint' for the other Python versions, to provide similar improvements.

Added delete_task and delete_location functionality to DataSync as well

Ready to merge


Reference

Ivan,
Could you please point me to your paper where you use the BRITS?
Thanks,
Haochen

https://www.sciencedirect.com/science/article/pii/S016816992100394X

https://www.sciencedirect.com/science/article/pii/S016816992100394X

and this too:
https://www.sciencedirect.com/science/article/pii/S0167739X21003794

https://www.sciencedirect.com/science/article/pii/S016816992100394X

and this too:
https://www.sciencedirect.com/science/article/pii/S0167739X21003794

Thank you. I will cite them


how to pipenv install/upgrade devlop (--dev) packages WITHOUT touching default (app) packages?

Hi all,
Based on https://pipenv.readthedocs.io/en/latest/cli/#pipenv, I am struggling to understand how one is supposed to run python tests (and other fun CI stuff), without also upgrading the base default packages.
So consider:

we have a Docker image with snapped pipenv to the right base packages via Pipfile.lock
developers and pipelines need to run "pipenv install --dev" in order to get pytest/etc.

Our Requirements:

we want default (app) packages in Pipfile and Pipfile.lock
we want develop (--dev) packages in Pipfile but NOT Pipfile.lock
when the app runs, it should ONLY have the app/default packages
when dev/ci runs, it should have the LATEST version of packages available in [develop] from Pipfile

The problem:

"pipenv install --dev" ALSO upgrades the default packages :( -- we DO NOT want to change the base application (default) packages, and ONLY install/upgrade the latest develop packages as needed / on demand;

-d, --dev     Install both develop and default packages.

The other options I have considered:
These two are contradictory ...

--skip-lock is good for the "--dev" packages (it is faster, and we don't want to lock dev packages), however then this ALSO upgrades app default packages :(
--ignore-pipfile is good for the default packages (it forces pipenv to use the Pipfile.lock), BUT, we don't want to lock the dev packages!

I see:

--selective-upgrade, and do it ONLY for the dev packages ... but that feels annoying and counter-productive to --dev's purpose!
--keep-outdated not entirely sure if this helps, but I don't think so

Advise? Am I missing it?
Hoping there is some clean command/workflow here to achieve our goals.  I imagine that this is a common set of requirements for projects.

pipenv --support

$ pipenv --support
Pipenv version: '2018.11.26'
Pipenv location: '/usr/local/lib/python3.7/site-packages/pipenv'
Python location: '/usr/local/bin/python'
Python installations found:

3.7.3: /usr/local/bin/python
3.7.3: /usr/local/bin/python3.7m
3.5.3: /usr/bin/python3.5m
3.5.3: /usr/bin/python3

PEP 508 Information:
{'implementation_name': 'cpython',
 'implementation_version': '3.7.3',
 'os_name': 'posix',
 'platform_machine': 'x86_64',
 'platform_python_implementation': 'CPython',
 'platform_release': '4.15.0-64-generic',
 'platform_system': 'Linux',
 'platform_version': '#73-Ubuntu SMP Thu Sep 12 13:16:13 UTC 2019',
 'python_full_version': '3.7.3',
 'python_version': '3.7',
 'sys_platform': 'linux'}

System environment variables:

HOSTNAME
PYTHON_PIP_VERSION
HOME
GPG_KEY
TERM
PATH
LANG
PYTHON_VERSION
PWD
PYTHONPATH
PIP_DISABLE_PIP_VERSION_CHECK
PYTHONDONTWRITEBYTECODE
PIP_SHIMS_BASE_MODULE
PIP_PYTHON_PATH
PYTHONFINDER_IGNORE_UNSUPPORTED

Pipenv–specific environment variables:
Debug–specific environment variables:

PATH: /usr/local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
LANG: C.UTF-8
PWD: /app

Contents of Pipfile ('/app/Pipfile'):
[[source]]
url = "https://pypi.org/simple"
verify_ssl = true
name = "pypi"

[packages]
"boto3" = "*"
(SNIP)
mysql-connector-python = "*"
pyodbc = "*"
requests = "*"
xlrd = "*"

[dev-packages]
freezegun = "*"
metrics = "*"
moto = "*"
pyfakefs = "*"
pylint = "*"
pytest = "*"
pytest-cov = "*"
pytest-mock = "*"
pytest-sugar = "*"
pytz = "*"
sqlparse = "*"

[requires]
python_version = "3.7"

(SNIP) (lock file N/A for now - it depends/varies when the user runs lock ;o)

In case others reach this report (and for the report itself), our workaround is as follows:

/usr/local/bin/pipenv install --dev --skip-lock
/usr/local/bin/pipenv sync

This achieves the goal, albeit a bit inefficiently as we have to install and upgrade ALL packages, then revert the APP/DEFAULT packages down to Pipfile.lock.

I believe this will not be supported, because default group is used as constraints for the other groups.  Right now there is the develop group, but soon we will support arbitrary groups, and it is constrained by the default which requires relocking the default which was work done prior this summer by @dqkqd.   I am also working on supporting more named categories or package groups, but they too are constrained by the default group:   https://github.com/pypa/pipenv/issues/4745


[FEATURE] Create a About Us page

🎇 Description
About us - A page where people would be able to know know what is the project about and features of project
🖼 Screenshots
No response

Hi, @KiranAminPanjwani Kindly assign this issue to me i would like on this

Sure, go ahead.✨

pls assign it to me

@Kriagr23 any progress?

@Kriagr23 any progress?

yes its done

Is there improvement to be done on About us page? If yes, assign it to me.


New release of sncosmo Please

Kyle, can you please make a new release of sncosmo, so that the ZTF filter transmissions can be made available standard?
Thanks,
Danny

v2.1.0 has been released.


Create Torrent: make trackers editable again

Fixes #768

Nice!

Released in WebTorrent Desktop v0.11!


feat: [CDS-59301]: support for infrastructure tags

Harness Developer Pull Request
Thanks for helping us make the Developer Hub better. The PR will be looked at
by the maintainers.
What Type of PR is This?

[ ] Issue
[X] Feature
[ ] Maintenance/Chore

If tied to an Issue, list the Issue(s) here:

Issue(s)

House Keeping
Some items to keep track of. Screen shots of changes are optional but would help the maintainers review quicker.

[ ] Tested Locally
[X] Optional Screen Shot.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app


ios can not get the event

AudioPlayer _audioPlayer = AudioPlayer();
_audioPlayer.onAudioPositionChanged.listen((Duration p) async {
print(p)
});
_audioPlayer.play(path, isLocal: true);
ios 10.0, flutter version 1.20.3

Please follow the issue template carefully, otherwise I will just close the issue.

Closing due inactivity, if there is more info that you can add to the issue, comment here and we can re open the issue.


Postgres driver doesn't get installed automatically

Issue Summary
ghost-5 doesn't automatically install the pg dependency.
Additionally, the it's trying to install pg with npm but the distribution contains yarn.lock file. It should install it with yarn instead.
Steps to Reproduce
  ghost:
       image: ghost:5-alpine
      restart: always
      networks:
        - postgres
      ports:
        - 8080:2368
      environment:
        # see https://ghost.org/docs/config/#configuration-options
        database__client: postgres
        database__connection__host: postgres
        database__connection__user: postgres
        database__connection__password: some easy password
        database__connection__database: site_blog
        # this url value is just an example, and is likely wrong for your environment!
        VIRTUAL_HOST: https://example.com
        # contrary to the default mentioned in the linked documentation, this image defaults to NODE_ENV=production (so development mode needs to be explicitly specified if desired)
        NODE_ENV: development

Ghost Version
ghost:5-alpine
Node.js Version
from docker
How did you install Ghost?
docker
Database type
Other
Browser & OS version
No response
Relevant log / error output
[2023-03-21 07:24:59] INFO Ctrl+C to shut down
[2023-03-21 07:24:59] INFO Ghost server started in 0.328s
Knex: run
$ npm install pg --save
Cannot find module 'pg'
Require stack:
- /var/lib/ghost/versions/5.39.0/node_modules/knex-migrator/node_modules/knex/lib/dialects/postgres/index.js
- /var/lib/ghost/versions/5.39.0/node_modules/knex-migrator/node_modules/knex/lib/dialects/index.js
- /var/lib/ghost/versions/5.39.0/node_modules/knex-migrator/node_modules/knex/lib/knex-builder/internal/config-resolver.js
- /var/lib/ghost/versions/5.39.0/node_modules/knex-migrator/node_modules/knex/lib/knex-builder/Knex.js
- /var/lib/ghost/versions/5.39.0/node_modules/knex-migrator/node_modules/knex/lib/index.js
- /var/lib/ghost/versions/5.39.0/node_modules/knex-migrator/node_modules/knex/knex.js
- /var/lib/ghost/versions/5.39.0/node_modules/knex-migrator/lib/database.js
- /var/lib/ghost/versions/5.39.0/node_modules/knex-migrator/lib/index.js
- /var/lib/ghost/versions/5.39.0/core/server/data/db/state-manager.js
- /var/lib/ghost/versions/5.39.0/core/boot.js
- /var/lib/ghost/versions/5.39.0/ghost.js
- /var/lib/ghost/versions/5.39.0/index.js
Error: Cannot find module 'pg'

Code of Conduct

[X] I agree to be friendly and polite to people in this repository

I managed to install the driver manually. But the migration is not compatible with PostgreSQL
[2023-03-21 08:38:32] INFO Ghost is running in development...
[2023-03-21 08:38:32] INFO Listening on: :::2368
[2023-03-21 08:38:32] INFO Url configured as: https://example.com/
[2023-03-21 08:38:32] INFO Ctrl+C to shut down
[2023-03-21 08:38:32] INFO Ghost server started in 0.303s
[2023-03-21 08:38:33] ERROR alter table "migrations_lock" add constraint "migrations_lock_pkey" primary key ("lock_key") - multiple primary keys for table "migrations_lock" are not allowed

alter table "migrations_lock" add constraint "migrations_lock_pkey" primary key ("lock_key") - multiple primary keys for table "migrations_lock" are not allowed

Error ID:
    c377c570-c7c3-11ed-ac17-5f1013cae863

Error Code:
    42P16

----------------------------------------

error: alter table "migrations_lock" add constraint "migrations_lock_pkey" primary key ("lock_key") - multiple primary keys for table "migrations_lock" are not allowed
    at DatabaseStateManager.getState (/var/lib/ghost/versions/5.39.0/core/server/data/db/state-manager.js:64:32)
    at Parser.parseErrorMessage (/var/lib/ghost/versions/5.39.0/node_modules/pg-protocol/dist/parser.js:287:98)
    at Parser.handlePacket (/var/lib/ghost/versions/5.39.0/node_modules/pg-protocol/dist/parser.js:126:29)
    at Parser.parse (/var/lib/ghost/versions/5.39.0/node_modules/pg-protocol/dist/parser.js:39:38)
    at Socket.<anonymous> (/var/lib/ghost/versions/5.39.0/node_modules/pg-protocol/dist/index.js:11:42)
    at Socket.emit (node:events:513:28)
    at addChunk (node:internal/streams/readable:315:12)
    at readableAddChunk (node:internal/streams/readable:289:9)
    at Socket.Readable.push (node:internal/streams/readable:228:10)
    at TCP.onStreamRead (node:internal/stream_base_commons:190:23)

[2023-03-21 08:38:33] WARN Ghost is shutting down
[2023-03-21 08:38:33] WARN Ghost has shut down
[2023-03-21 08:38:33] WARN Ghost was running for a few seconds

Hi @mesudip - Postgres is not a supported database in Ghost v5 🙂 https://ghost.org/docs/faq/supported-databases/


Display bug with [@page-reference ]

I keep seeing these. The markdown looks OK so inclined to think it is rendering funky for some reason.

Source URL: https://blockstack-docs-git-mainnet-docs.blockstack.vercel.app/start-mining/mainnet
BrowserChrome 87.0.4280.88Screen Size2560 x 1440OSOS X 10.15.7Viewport Size2007 x 1226Zoom Level100%Pixel Ratio@1x

fixed in master
https://docs.blockstack.org/start-mining/mainnet
commit here: https://github.com/blockstack/docs/commit/529df3502f11d6f882d976d982215276ccd5062c#diff-5da5b88049a8268a82ad826128717667c81ac6e4c8fcee5218a17d559dfc1099R23
closing :)

fixed in master
https://docs.blockstack.org/start-mining/mainnet
commit here: https://github.com/blockstack/docs/commit/529df3502f11d6f882d976d982215276ccd5062c#diff-5da5b88049a8268a82ad826128717667c81ac6e4c8fcee5218a17d559dfc1099R23
closing :)

Such fast service here.

Such fast service here.


Feature: Add an event stream

The whole purpose of the event stream is to broadcast system events.
#125

implementation is done


Profile build of hello world does not launch with --sound-null-safety

command:
flutter run  --sound-null-safety --enable-experiment=non-nullable --profile

Result:
E/flutter (18201): [ERROR:flutter/runtime/dart_isolate.cc(228)] CreateDartIsolateGroup failed: Snapshot not compatible with the current VM configuration: the snapshot requires 'release no-dwarf_stack_traces_mode no-causal_async_stacks lazy_async_stacks no-lazy_dispatchers use_bare_instructions no-dedup_instructions no-"asserts" no-code-comments arm64-sysv null-safety' but the VM has 'release no-dwarf_stack_traces_mode no-causal_async_stacks lazy_async_stacks no-lazy_dispatchers use_bare_instructions no-dedup_instructions no-"asserts" no-code-comments arm64-sysv no-null-safety'

release and debug works fine.

@a-siva: "snapshot requires ... null-safety ... but the VM has ... no-null-safety." indicates that the snapshot is incorrectly built right? But, I am not sure how this can happen because the isolate can be launched in either mode depending on the isolate flags we set (by introspecting the snapshot itself).
I'll try to debug this as I am not able to reproduce this in profile runtime mode in the engine native test harness.

It appears that the snapshot was built with the --null-safety string but the isolate is starting in no-null-safety mode, this isolate could be the service isolate, we should check how the service isolate is started.

The engine doesn't initiate the launch of the service isolate. Instead, the VM gives the engine a callback in response to the launch of the root isolate. In the callback, the isolate flags of the parent are passed in which are used (unmodified) to create the new isolate.

@jonahwilliams: Are the outstanding changes on ToT? I am unable to run the Hello World application with the command you used because the default of complaints that packages don't fully support null-safety.
dart pub outdated --mode=null-safety result.
In the meantime, I'm debugging this in the engine test harness to dump service isolate launch flags.

@chinmaygarde Try changing the hello_world package SDK constraint (https://github.com/flutter/flutter/blob/master/examples/hello_world/pubspec.yaml#L5) to:
sdk: ">=2.11.0-213.0.dev <2.12.0"

So, the isolate flags don't seem to be inherited. But then, I am not sure how this works in debug mode since the procedure is the same. Also, since the flags are not inherited, I can't stash the original flags anywhere. Will chat with @a-siva about how this is meant to work.


width of container

width of container in 1200px was increased from 1140px to 1200px

We don't modify the dist files, and there won't be any changes to the container sizes at this time.


How to properly close and deallocate a cursor?

While the docs for TSQL cursors explain how to they can be closed and deallocated, there is no coherent example where a cursor is declared, opened, used, and then closed and deallocated. This is especially difficult in the case of properly closing a cursor.
For example, in the remarks section of the DEALLOCATE docs, it says "A cursor variable does not have to be explicitly deallocated. The variable is implicitly deallocated when it goes out of scope". However, in the CLOSE docs, nothing is mentioned that the cursor is closed when a cursor variable goes out of scope.
I think this leads to confusion, e.g. this StackOverflow answer says that you can simply declare a cursor variable and let it go out of scope to close and deallocate the cursor (personally, I'm not so sure if this is actually working).
Specifically, I have the following questions:

How do you properly close a cursor? Do you have to call CLOSE and then DEALLOCATE? Is there an automatic mechanism that does this?
Can CLOSE and DEALLOCATE throw exceptions? Should these statements be put in a separate try-catch block?
Can you provide a comprehensive example where a cursor is declared, opened, used, and then closed and deallocated? Including the usual stuff that one needs in Stored Procedures like a transaction and try-catch blocks?
Can you provide information what DEALLOCATE actually does internally? Is it a reference counting mechanism? The documentation of CLOSE already describes that it frees the cursor result set and cursor locks.

Please notice: this issue is based on my StackOverflow question: https://stackoverflow.com/questions/57952068/close-and-deallocate-cursor-and-try-catch-in-tsql

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

ID: 78d01993-979b-91ee-862c-55dbb00dd1dd
Version Independent ID: b4e53b79-3356-7bd8-bcde-112e208aad9a
Content: Cursors (Transact-SQL) - SQL Server
Content Source: docs/t-sql/language-elements/cursors-transact-sql.md
Product: sql
Technology: t-sql
GitHub Login: @rothja
Microsoft Alias: jroth

I've just read "Error and Transaction Handling in SQL Server" by Erland Sommarskog (Part 1, Part 2, and Part 3). In Part 2 Chapter 5, he talks about different behavior when a transaction is involved as well as when SET XACT_ABORT is set to ON or OFF. I don't know if this has any consequences for closing a cursor? If it has, it might be worth mentioning them in the docs, too.

@feO2x Thank you for these questions. I will try to find someone internally who can answer some of these questions. We might not be able to address everything here in the git issue, as this question is more in line with a forum question (which I see you've already posted on Stack Overflow, thanks!). However, from a documentation perspective, I can see how you are pointing to holes in how we document cursors, especially for CLOSE and DEALLOCATE. Please let me look into this a bit more and get back to you. Thanks, again, for the feedback!

@rothja Thanks for the info. @srutzky answered the StackOverflow question and pointed out that DEALLOCATE implicitly calls CLOSE when the the cursor is not used by any other piece of code. I think this should be part of the DEALLOCATE docs.

@feO2x and @rothja : I don't think I said anything about "when the cursor is not used by any other piece of code". If anything, I was saying that no other code is truly connected to a cursor, so there shouldn't be any reason that could cause a CLOSE or DEALLOCATE to error. The docs do mention something about using a cursor variable and "if there are no other references, then DEALLOCATE will de-list the cursor entirely." I could not exactly reproduce that scenario. The closest I was able to get was creating a named cursor and a separate cursor variable, and then setting that variable to the named cursor's name. In that one scenario, calling DEALLOCATE on the cursor variable merely un-set the variable from referencing that cursor and left the variable without any reference at all (kinda like going from a value to being NULL). It's possible that the DEALLOCATE doc is wrong in its description of the behavior. I will need to do a little more testing at some point to know for certain. I have several test scripts showing a variety of scenarios for scope, locking, closing & deallocating,  checking for cursor existence and status, etc that will be the basis of a detailed post on the various aspects of cursors. No ETA when I will actually get time to complete it, but I at least have a good start to it 😃 . For now, a good portion of most of my notes are encapsulated in my answer to feO2x's StackOverflow question.
Take care,
Solomon...
https://SqlQuantumLeap.com/

@srutzky Thanks for the detailed reply and thanks to you both for pointing me to the discussion in StackOverflow. At this point, it sounds like there is not enough conclusive evidence on exactly how the docs should be changed until we get more data. I will also try to reach out internally to see if I can find someone that knows this area well and would be able to explain how we can improve the docs.

Apologies for the delay, but per my previous comment, I'm not sure exactly how to proceed. For that reason, I'll close this git issue, but feel free to provide more comments on any specific change you recommend based on this discussion. I believe that @srutzky has made direct edits to the content with the edit button on the articles, so that is another route for suggestions/fixes. Thank you!


entity does not accept name as parameter

Describe the bug （描述一下问题）
When configuring the entity you cannot give a name to it. It is very difficult to identify the entity if you don't give a name.
Screenshots / Logs / Pcap File（屏幕截图/日志/抓包文件）
when configuring yaml in this way:
climate:     - platform: midea_ac       name: "Condizionatore Wifi"       host: <IP_ADDRESS>       id:<PHONE_NUMBER>09138       token: E2D12F391041ABEFF9BFD5FAEC443C4E3DC208C60C4DE3586CB85AA76CD4E922A9686C5C8CCF61D2653CBFCF7FC4E0F0B343       k1: 9b1234280b3e4699afea202b4dfe48eb60f5dad085704564bae61e42188d5814
I get:
Invalid config for [climate.midea_ac]: [name] is an invalid option for [climate.midea_ac]. Check: climate.midea_ac->name. (See ?, line ?).
Versions (版本信息)

Home Assistant version: 2022.10.5 ( docker )
Midea msmart version:  0.2.3

A possible solution for you. Install the latest commit (or even better my future branch instead). It supports configuration via the GUI and registers a device which can be renamed.


Count Tokens example in the documentation no longer works

Describe the bug
This page in the docs https://docs.griptape.ai/examples/count-tokens/ demonstrates how users can use the TokenCounter utility for keeping track of how many tokens have been used.
To Reproduce
Steps to reproduce the behavior:

Copy the code in the above page into a new file
run the code
see that total tokens: 0
set a breakpoint at line 11 in token_counter.py
run the code again in debug mode
see that the breakpoint is never hit

Expected behavior
The expected behavior is that this function should be called and the total tokens  should be non zero.
Desktop (please complete the following information):

OS: windows 10
Version: 19045
Griptape Version: 0.15.3
Python Version: 3.11.4

Additional context
Discord Thread

Also tested this on Ubuntu 22.04.2 LTS and  python 3.10.6 and can still reproduce the bug.

Hey @mgcollie! This was resolved in 149; we should have a release that contains this fix out soon.

Thanks @collindutter !

@mgcollie this has been fixed in v0.16.0 release. Thanks for the report 🙂


Lint undefined functions?

Hello!
I just started using stylelint so I probably haven't looked at all the docs. However, I was hoping it could lint my most common problem: lint undefined functions (due to missing @imported file)
Does anyone mind pointing me in the right direction? I've gotten the impression it might have to do with some post-CSS shenanigans but I'm not sure where to start :(

Sounds like this should be an issue made directly to https://github.com/stylelint/stylelint or looked around on S/O - without more context or an example I can't help you much further. Good luck!


Ubuntu derivative support

Is it possible to add *buntu support, such as xbuntu, or primarily lubuntu as I personally would use

http://www.ubuntu.com/about/about-ubuntu/flavours
http://lubuntu.net

Have you tried doing a regular install and then choosing that package set for the derivative you want?

My apologies, I was sure they hosted their own mini.iso, I was misinformed, the ubuntu installation works perfectly

Cool, sounds good, thanks!


Getting error despite null check in module scoped functions

I could not reproduce this on the live console because document is not accessible there. Here is a sample code anyway.
// @flow

// returned type is HTMLElement | null
const element = document.getElementById('my-element');

function getRect() {
  // Error Cannot call element.getBoundingClientRect because property getBoundingClientRect is missing in null
  return element.getBoundingClientRect();
}

export default function main() {
  if (!element) return; // Checking element is defined
  console.log(getRect()); // calling getRect
}

I'm in an ES6 module so getRect can not be called from outside and the only code that's calling it is my main function which performs a null check before. Still, I'm getting a error about element being potentially null. Is this normal behavior ?
Using flow 0.70.0
Thanks in advance

Refinement doesn't propagate across function calls by design


Fix URL of Windows artifacts

They end in .exe.
Also my integration tests were failing because buckle was failing due to a corrupted cache, but I couldn't see that because stderr wasn't being reported in the error message. I added stderr to the command assertions.

This is also probably fixed by #8


Cannot run default flutter app

Hi I have recently update my Android Studio and have created a new Flutter Application. Without editing, i run it to see if it is working.
The following error code below arises.
I have tried running my previous Flutter Projects and it works. Anyone out, please advise. Thank you.
* Error running Gradle:
ProcessException: Process "/Users/glenn/Desktop/2Training/flutter_app/android/gradlew" exited abnormally:
Starting a Gradle Daemon (subsequent builds will be faster)

> Configure project :app
NDK is missing a "platforms" directory.
If you are using NDK, verify the ndk.dir is set to a valid NDK directory.  It is currently set to /Users/glenn/Library/Android/sdk/ndk-bundle.
If you are not using NDK, unset the NDK variable from ANDROID_NDK_HOME or local.properties to remove this warning.

Checking the license for package Android SDK Build-Tools 28.0.3 in /Users/glenn/Library/Android/sdk/licenses
Warning: License for package Android SDK Build-Tools 28.0.3 not accepted.

FAILURE: Build failed with an exception.

* Where:
Build file '/Users/glenn/Desktop/2Training/flutter_app/android/build.gradle' line: 24

* What went wrong:
A problem occurred evaluating root project 'android'.
> A problem occurred configuring project ':app'.
   > Failed to install the following Android SDK packages as some licences have not been accepted.
        build-tools;28.0.3 Android SDK Build-Tools 28.0.3
     To build this project, accept the SDK license agreements and install the missing components using the Android Studio SDK Manager.
     Alternatively, to transfer the license agreements from one workstation to another, see http://d.android.com/r/studio-ui/export-licenses.html

     Using Android SDK: /Users/glenn/Library/Android/sdk

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 22s
  Command: /Users/glenn/Desktop/2Training/flutter_app/android/gradlew app:properties

Finished with error: Please review your Gradle project setup in the android/ folder.

Can you attach the output of running flutter doctor -v?


[bug] Export to image cut long name

steps

Open the editor with Google Chrome
Set "Aéroport Charles-de-Gaulle 2 TGV" as a stop name
Export the project as an picture
Open PNG picture (with Aperçu app, on M1)

Screenshoots: Line 19 having a long name
title with an icon

title without an icon

Duplicate of #13


Add cipher interface to key wrapping modes

We provide the NIST key wrapping modes (KW, KWP) through a custom interface (mbedtls_nist_kw_xxx). A key wrapping mode is an AEAD mode, functionally speaking, so it would make sense to provide an interface to these modes through the generic AEAD functions in the cipher module.
The key wrapping modes would only be supported by the one-shot functions (mbedtls_cipher_auth_encrypt, mbedtls_cipher_auth_decrypt), not by the multipart functions, because they process the full input at once. This is already the case for CCM (which processes the data in a streaming fashion but can't start encrypting until it knows the length of the plaintext) so we wouldn't be changing the philosophy of that API.
Requested by @jethrogb in https://github.com/ARMmbed/mbedtls/pull/1658#issuecomment-417461217

We have started working on this.


OpenWRT support

Please describe your issue:
OpenWRT is a Linux distribution focused for routers. While the nature of the project is such, they provide x86 and x86_64 images, and tarballs for the rootfs. Recommend we support OpenWRT as well since its a very minimal and small Linux distribution

The network configuration in a crouton chroot is controlled by Chrome OS so I believe this would have to be implemented in Chrome OS and not in the chroot.
Hope this helps,
-DennisLfromGA


[Bug] Authentication Proxy does not work with Skaffold (blocks on rollout status)

What kind of request is this (question/bug/enhancement/feature request):
Bug related to https://github.com/GoogleContainerTools/skaffold/issues/5810
Steps to reproduce (least amount of steps as possible):
Manage a cluster via rancher
Get the kubeconfig for the cluster and make sure your context is set to accessing the cluster via the rancher url (proxy mode) and not via the Authenticated Cluster Endpoint
Try using skaffold with the kubectl deployer and a deployment manifest (can be any simple deployment):
skaffold.yaml
apiVersion: skaffold/v2beta13
kind: Config
metadata:
  name: minimal-example
deploy:
  kubectl:
    manifests:
    - deployment.yaml

deployment.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: minimal
spec:
  replicas: 3
  selector:
    matchLabels:
      app: minimal
  template:
    metadata:
      labels:
        app: minimal
    spec:
      containers:
      - name: minimal
        image: busybox
        command:
          - sleep
        args:
          - "10000"

Result:
Skaffold gets stuck at waiting for deployments to stabilize https://github.com/GoogleContainerTools/skaffold/issues/5810 and only converges after approximately 7 minutes
Other details that may be helpful:
Directly accessing the cluster via the api server authorized endpoint instead of the endpoint proxied by the rancher server works fine. So it appears that there is either missing functionality or some sort of weird caching behavior in play.
Happens for all kinds of downstream clusters such as k3s or rke spawned by rancher.
Environment information

Rancher version 2.5.8
Installation option (single install/HA): HA

Moving this back to test, as I can no longer reproduce in 2.6-head. Both contexts complete in around 7 seconds, whereas in v2.6.2, the proxy completes in about 30 seconds.

@Blackclaws , wondering if you can validate if this is working as expected on v2.6-head image? (https://hub.docker.com/r/rancher/rancher/tags).

I can try validating it on a standalone installation or I can wait until 2.6.3 is released to validate it on our production system.

@Blackclaws , thank you for getting back to me. It would be great if you could validate it on a standalone installation prior in the next week or so - so we're sure it's actually fixed. Is this something you can do?

I've tried it on our production system by upgrading a copy of that to head. Issue persists. I'll try it on a standalone system as well.

A compounding issue is that as of rancher 2.6 the authorized endpoint is also broken for Keycloak backed users:
https://github.com/rancher/rancher/issues/35187

@Blackclaws still working on this, but still having some issues reproducing. Would you mind sharing some of the following information regarding your setup?

What kind of clusters are these (AKS, imported etc.)?
What kubernetes version is being used?
What version of skaffold is being used?

Also any information regarding either skaffold or the command kubectl -v 10 --context test-cluster rollout status deployment minimal --namespace default --watch=false  blocking would be appreciated, as I haven't been able to reproduce comparable results with either.

Sure I'll help you as much as I can to reproduce this, I'll try to get a minimal example working as well if possible

RKE rancher launched clusters.
1.21.5 in production 1.22.4 in the test I did
Skaffold version 1.23.0

However skaffold version is not relevant as the blocking kubectl command itself shows the issue without even using skaffold.

It indeed seems fixed for new rancher setups. The existing production setup still has this issue. Setting up a new rancher starting at least from 2.5.10 doesn't show this issue, for whatever reason that may be.
Since I can't reproduce this on a new install it seems this issue has something to do with something that happened in the past with our system. I think closing this issue is probably the best right now. I'll just setup the production system again over the holidays. If the issue does crop back up I'll reopen a new issue, or you can keep this issue open for a while, your choice.

following the comment instructions here, I was also unable to reproduce this issue using rancher v2.6.4-rc3.


IVector page contains merge conflict markup

This page appears to contain markup from a merge conflict; i.e.
<<<<<<< HEAD IVector inherits ...
...
>>>>>>> cd84458f70e29e2fa6b720ec78056581fa3bce0b

(The last part renders as a sequence of nested blockquotes.)
Side note: The "Content Source" link below doesn't render correctly (here on GitHub) due to the backtick in the interface name.

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

ID: 1897ffed-ceed-72d1-9fba-82541ac877af
Version Independent ID: 247436b5-6c34-da61-fd01-87597be694e7
Content: IVector<T> Interface (Windows.Foundation.Collections) - Windows UWP applications
Content Source: [winrt-api-build/xml/Windows.Foundation.Collections/IVector1.xml](https://github.com/MicrosoftDocs/winrt-api/blob/docs/winrt-api-build/xml/Windows.Foundation.Collections/IVector1.xml)
Product: uwp
Technology: winrt-reference
GitHub Login: @hickeys
Microsoft Alias: hickeys

It looks like somebody else has resolved this problem without closing the issue. This feels resolved, so I'm going to close this issue.
Though the Issue will be marked as Closed, we will monitor any replies that come afterwards so treat this like an open Issue. Many thanks!


[BUG]

Describe the bug
The server doesnt even start
To Reproduce
try to to start the server on a fresh project
Expected behavior
the server wont crash
Screenshots
If applicable, add screenshots to help explain your problem.

what are your errors? cant help at all if you dont provide more info

you need to update your dependencies, then bind the ws server to a specific port like 8080.
i've managed to modify and run my own version but it's not very beginner friendly, but the work done here is impressive

ah actually the websocket server is running at [your_ip]:3000/moomoo
it's the url you should use to connect


Reorganise view folders

Now that we're prototyping more services we should reorganise the view folders so we can clearly distinguish between services and prototype versions.

👍  LGTM


Ridables Permissions

Spark link
https://spark.lucko.me/0EICMITmYT
Expected behavior
When a player with the allow.ride.Animalnamehere permission tries to ride the mob it lets them on and they can ride despite if they have been opped or not
Observed/Actual behavior
i cant seem to get the ridables permissions working, i can only ride mobs if im Opped
it was working before 1.19.3
i checked the config and riding is set to on for everything but ill use the bee as the example, i also set my donors to have the rank "quantum" and under the quantum rank in luckperms i set allow.ride.bee to true
but they still cant ride the bee
Steps/models to reproduce
using luckperms give default group access to allow.ride.(animalnamehere)
try to ride the animal while deopped, be denied the ability to ride unless opped
Purpur version
[12:56:28 INFO]: Current: git-Purpur-1862 (MC: 1.19.3)*
Previous: git-Purpur-1861 (MC: 1.19.3)

You are running the latest version

Agreements

[X] I am running the latest version of Purpur available from https://purpurmc.org/downloads.
[X] I have searched for and ensured there isn't already an open issue regarding this.
[X] My version of Minecraft is supported by Purpur.

Other
this was discussed and i think acknowledged in the discord under help-and-support already and Eclipse | Rhythmic posted a video of the issue I just thought i should perhaps make an official bug report too

I see the problem. The internal ID that I am using seems to be set to custom by Paper. I'll have to find another way to get the entity id for the permission check.

I'll have this fixed shortly.


Fix incorrect urlBase when the load address is the resource root.

Addresses #32. If the SystemJS baseURL is to the root and the SystemJS import is not in a folder eg.
System.config({
 baseURL: '/'
});

...

System.import('sample.scss!')

Then the urlBase should set to /. However, currently a trailing slash is always added to the urlBase, which breaks the importer when the urlBase is already /. To see the effects of this, modify the new test added to set urlBase to //. The test will fail.
I've gone back and updated #32 to reflect the conclusion I've come to regarding the problem.

What about sass-builder.js#L73? The issue only affects sass-inject.js and not sass-builder.js?

In both sass-builder and sass-inject the objective is to get the path of the absolute address where the entry file is loaded from. sass-builder is working straight from the file system, so, as I understand it, the issue would surface there if a file was loaded from the root of the filesystem (e.g. file:/// would become file:////). For my use case, I had no problems using sass-builder by replacing my System.import('main.scss!') with import './main.scss!. The styles were all resolved as I expected.


organicmaps: 2024.07.29-2 -> 2024.07.27-8

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for organicmaps is: Detailed Offline Maps for Travellers, Tourists, Hikers and Cyclists
meta.homepage for organicmaps is: https://organicmaps.app/
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2024.07.27-8 in filename of file in /nix/store/v2xj8v8qj4bkzl29kcs79amcmgq03sab-organicmaps-2024.07.27-8

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

organicmaps

Instructions to test this update (click to expand)

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

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

Or:
nix build github:r-ryantm/nixpkgs/c2a89e6fd3b6cd087b598972ffa6587980098e31#organicmaps

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/v2xj8v8qj4bkzl29kcs79amcmgq03sab-organicmaps-2024.07.27-8
ls -la /nix/store/v2xj8v8qj4bkzl29kcs79amcmgq03sab-organicmaps-2024.07.27-8/bin

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

1 package built:

organicmaps

Maintainer pings
cc @fgaz for testing.

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

@ryantm This is a downgrade!

I think it's because the latest tag does not have a corresponding "github release". I'm surprised the bot doesn't check for this kind of situation

I've seen another downgrade just yesterday: https://github.com/NixOS/nixpkgs/pull/334238

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for organicmaps is: Detailed Offline Maps for Travellers, Tourists, Hikers and Cyclists
meta.homepage for organicmaps is: https://organicmaps.app/
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2024.08.16-5 in filename of file in /nix/store/s4wjz5khq08ad6jr7a5fp6hl6mld01yb-organicmaps-2024.08.16-5

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

organicmaps

Instructions to test this update (click to expand)

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

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

Or:
nix build github:r-ryantm/nixpkgs/91d9eee346be90077a5931f58e46d9a2ca2b8a1b#organicmaps

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/s4wjz5khq08ad6jr7a5fp6hl6mld01yb-organicmaps-2024.08.16-5
ls -la /nix/store/s4wjz5khq08ad6jr7a5fp6hl6mld01yb-organicmaps-2024.08.16-5/bin

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

1 package built:

organicmaps

Maintainer pings
cc @fgaz for testing.

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

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