Windows exrm release bat does not work in directories with spaces

running bin/bgfx.bat console
The system cannot find the file specified.
Error occurred while processing: C:\Users\My.
The system cannot find the path specified.
"Using C:\Users\My Name\Downloads\ex_bgfx\releases\\bgfx.bat"
'"C:\Users\My Name\Downloads\ex_bgfx\releases\\bgfx.bat"' is not recognized as an internal or external command, operable program or batch file.

Expected that the bat will work in directories with spaces.

@fire Work is ongoing to bring the batch file up to par, including a fix for this specific issue. I'll keep this open until it's merged into master.

Status check?

It does not work in the latest release. The problem is that "bin/[APP].bat" and "release/[VERSION]/[APP].bat" sometimes use quotes around the paths, sometimes forgets the quotes and some paths gets double quoted.
I had to do the following to get the console command to work.
In "bin/[APP].bat":
line 19, @for /f "delims=" %%i in ('type "%start_erl%"') do @(
Add quotes around %start_erl%.
in "release/[VERSION]/[APP].bat":
line 29, @for /f "delims=" %%i in ('type "%start_erl%"') do @(
Add quotes around %start_erl%.
line 130, @set conform_schema=%rel_dir%\%rel_name%.schema.exs
Remove the quotes around %rel_dir%\%rel_name%.schema.exs. The script correctly puts quotes around conform_schema on line 143 and 144 which means you end up with if ""[path]"" (.
line 203, @start "%rel_name% console" "%werl%" -config "%sys_config%" ^
Add quotes around %werl%.
I can submit a pull request with the rest of the fixes sometimes next week if you want.

That would be great, and I can play with it.

@Gyllsdorff If you can submit a PR that would be greatly appreciated!
@fire There are a few people working on various Windows-related PRs right now, so things are improving, but still not ready for prime-time sadly. I plan to announce when Windows support is legit, so that people are aware, in the meantime though, I throw the windows label on anything related to it in the issue tracker


Feature: Updated layout icons in the toolbar

Resolved / Related Issues

[x] Were these changes approved in an issue or discussion with the project maintainers? In order to prevent extra work, feature requests and changes to the codebase must be approved before the pull request will be reviewed. This prevents extra work for the contributors and maintainers.
For #10492

Validation
How did you test these changes?

[x] Did you build the app and test your changes?
[ ] Did you check for accessibility? You can use Accessibility Insights for this.
[ ] Did you remove any strings from the en-us resource file?

[ ] Did you search the solution to see if the string is still being used?

[ ] Did you implement any design changes to an existing feature?

[ ] Was this change approved?

[x] Are there any other steps that were used to validate these changes?

Confirm the toolbar icon displays for each layout

Screenshots (optional)
Add screenshots here.

If I were you, I'd rename them like ColorIconLayoutSizesExtraLarge28x28 Using dot is not recommended in the MSDN.

I'll put the size last, but using dot is a pattern that works well and makes it easier to select the correct option from auto complete.


Add 'select all' for major  and 'minor' lists, not just initial package lists

When selecting pacakge for major and minor bumps from list, also display all changed and all unchanged, in similar way to initial package select, to make mass releases easier.
@mitchellhamilton if you don't have any args against, I'll mark this is a good first issue and send it.

Assuming you mean a section thing like the changed and unchanged packages thing then I’m good with it.

Yeah, that.

I've already started this.


Feature Request (txt file as argument)

Add the option to pass a txt file with multiple URLs as an argument.

Try it out and let me know how you think. I made it to where you can use an input file and links on the command line together. They will all be combined and downloaded together.

Just tested it.
It works well.
Thanks.


Master

要解决的问题 Describe the problem to be solved

要解决的Issue编号（可多个） Associated issue number (multiple)

???


-Ctarget-feature=+crt-static on musl builds

from https://github.com/axodotdev/cargo-dist/pull/483#issuecomment-1766970460 via @bjorn3

Could you explicitly enable -Ctarget-feature=+crt-static? The intent is to switch the musl target to default to dynamic linking in the future. Having everyone who depends on musl statically linking explicitly specify this will make it easier to flip the switch in the future.

@bjorn3 happy to flip crt-static (we do it for windows already) -- is there any movement towards a naming scheme to quickly distinguish "dynamic musl" from "static musl" in target triples? Vaguely mulling over cargo-dist referring to it as unknown-linux-musl-static or unknown-linux-musl+static to be clear about it.

@bjorn3 reading https://github.com/rust-lang/compiler-team/issues/422#issuecomment-812135847 - it looks like we may need more than the suggested flag to maintain compatibility with the current behavior- is that true? also, thanks again for commenting with the heads up, it's very appreciated

@bjorn3 reading https://github.com/rust-lang/compiler-team/issues/422#issuecomment-812135847 - it looks like we may need more than the suggested flag to maintain compatibility with the current behavior- is that true?

Good point. Using -Clink-self-contained=yes may also be necessary in the future if we decide to change the default for that to false too. Or alternatively you could install musl libc before compiling. Debian derived distros allow installing it next to glibc.

is there any movement towards a naming scheme to quickly distinguish "dynamic musl" from "static musl" in target triples?

Not that I am aware of.


Tooltip for the selected sorting option doesn't appear properly in Manage Streams UI

The tooltip for the selected sorting option seems to be hidden behind other elements while it works fine for the 2 un-selected options.
Currently if a user has to see what the selected option does, they'd first have to select another sort option, and then hover over the previous one.

Fixed in #21330.


Summary to file

Is there a way to get the summary as string, similar to:
chip.run()
summary = chip.get_summary()

So it could be saved in a file.

I don't believe we have a quick and easy way to do this yet. One option as a workaround could to copy-paste the summary implementation from core.py into your own code, and replace the print() calls at the end with a single return df.to_string(). Then you could call this directly from your code.
This is a good idea though, and we can take it under consideration as a feature request!

Depends on what you want to do with the summary? All the data is in the .json file, which is dumped with the write_manifest() method. The summary function is just looping through the metrics dictionary to print put the values to screen. The same thing could be done eaily in Javascript or any other language that can parse json.

Got it! I didn't know the write_manifest() function. It works for me. Thanks both!

Fantastic!


Fix error message for missing migration files

This was caused by this change 1.0

Changed Migrator to return list of migrations as objects consistently.

I'm not sure how / if I should add tests for this. Let me know if you'd like them :)
This fixes the following error:
$ (createdb luma-test &> /dev/null || true) && knex migrate:latest --env test && node -r esbuild-register ./node_modules/knex/bin/cli.js seed:run --env test --specific=seed_db.ts && NODE_ENV=test jest --runInBand
Using environment: test
The migration directory is corrupt, the following files are missing: [object Object]
Error: The migration directory is corrupt, the following files are missing: [object Object]
    at validateMigrationList (/Users/victor/Code/luma/node_modules/.pnpm/knex@1.0.1_pg@8.7.1/node_modules/knex/lib/migrations/migrate/Migrator.js:566:11)
    at Migrator.latest (/Users/victor/Code/luma/node_modules/.pnpm/knex@1.0.1_pg@8.7.1/node_modules/knex/lib/migrations/migrate/Migrator.js:69:7)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async Command.<anonymous> (/Users/victor/Code/luma/node_modules/.pnpm/knex@1.0.1_pg@8.7.1/node_modules/knex/bin/cli.js:232:32)

Thank you!

Released in 1.0.2


Implement the ability to persist values in the minder CLI config file

Details:
At the moment a user can leverage config files to create different contexts for the minder CLI works on. For example, one can set a project ID that would be used across all calls (unless it's set explicitly via an env var or a flag, then viper uses them instead of what's in the config).
This should allow the user to persist values in the config file through the minder CLI and not have to edit the config file manually.
Proposal:
For example, have something like - minder config set --project <project> which persist the <project> value on the current config file.

If the config file is also specified, use it, otherwise use the default one.
We should first try to look if there's such a config file and edit it accordingly, and if it's missing then create a blank one with the new value stored.
In any case we don't want to overwrite or lose any other existing content unintentionally.

References:

https://github.com/stacklok/minder/issues/1750
https://github.com/spf13/viper?tab=readme-ov-file#writing-config-files

We have environment variables like MINDER_PROJECT that can do some of this.  I'm not sure we want to build something like kubectl context ....

Closing this for now, you can use MINDER_CONFIG to switch between different config files, and the other environment variables for more detailed tweaks.


[docs] update UUID datatype description

https://ydb.tech/docs/en/yql/reference/types/primitive#string

You can create columns with uuid
They can't be in primary key
Limitations and implementation notes for uuid

please don't forget to merge to 24-1 branch for docs

Actually UUID can be used as PK, but this feature is disabled by default for compatibility reason. To use UUID as PK in 24.1  the feature flag EnableUuidAsPrimaryKey must be switched on.

Actually UUID can be used as PK, but this feature is disabled by default for compatibility reason. To use UUID as PK in 24.1 the feature flag EnableUuidAsPrimaryKey must be switched on.

Thanks for details
Since we can use versioned docs it would be wonderful to write about feature flag in 24-1 and info about UUID as OK for main


Casting of TarfinLabs\LaravelSpatial\Types\Point to string (for upsert())

We use static method upsert() for inserting or updating several rows in one query (https://laravel.com/docs/10.x/eloquent#upserts).
Unfortunately, Laravel in this place does not support casting out of a box. So trying to run:
Property::upsert(
    [
        ['external_id' => 5, 'location' => new Point(50, 20, 4326)],
        ['external_id' => 7, 'location' => new Point(60, 30, 4326)],
    ],
    ['external_id'],
    ['location'],
);

gives an error Object of class TarfinLabs\LaravelSpatial\Types\Point could not be converted to string. So maybe the solution to this could be quite easy? I mean supplying the method __toString for converting object to string.
For now, I'm using this workaround solution:
Property::upsert(
    [
        ['external_id' => 5, 'location' => DB::raw("ST_GeomFromText('POINT(50 20)', 4326, 'axis-order=long-lat')")],
        ['external_id' => 7, 'location' => DB::raw("ST_GeomFromText('POINT(60 30)', 4326, 'axis-order=long-lat')")],
    ],
    ['external_id'],
    ['location'],
);

Hi @boryn,
Thank you for bringing this issue to our attention. We're glad to inform you that we have addressed the issue and released a new version that includes the fix.
We appreciate your patience and understanding while we worked on this issue. Please let us know if you have any further questions or concerns.
Best regards,
@tkaratug


DDPB-4191: Prefer acsauk/clamav-rest-1 to lokori/clamav-rest

Purpose
Adding a temporary fix for a maintained version of our scanner rest API while we look at longer-term solutions.
Fixes DDPB-4191.

You'll need to add it in /environment/scan.tf#L75 as well.

Ah of course, thanks @mattmachell


non-admin clarification

For Objects category it is mentioned "A non-admin user can create no more than 250 objects." can we clarify what type of admin can do this thinking about the minimum requirements to create more than 250 objects?

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

ID: 42a0b4cb-1981-1cbc-ce2c-dbfd8af1527c
Version Independent ID: d49c873c-9843-8428-a6d1-a1995067d13b
Content: Azure Active Directory service limits and restrictions
Content Source: articles/active-directory/users-groups-roles/directory-service-limits-restrictions.md
Service: active-directory
GitHub Login: @curtand
Microsoft Alias: curtand

@gonzalre
Thanks for your feedback! We will investigate and update as appropriate.

Hi @gonzalre
I'll dig into this and find out if there are admin roles that can do more. Thanks for your contribution!

+1 on this issue.  Would like a way to authorize higher limits for AD App Principals to create more than 250 objects in particular.  Applications which automate things like AD App creation will run into this limit pretty quickly.

Hi @gonzalre , @pgazmuri
There isn’t a good way today. It’s definitely we'll be addressing in the future. The admin roles that can create more than 250 objects are all pretty highly privileged. I may have missed one.
 I think a solution will come sooner rather than later.
@MarileeTurscak-MSFT
#please-close

@curtand , that certainly IS NOT a good practice.  In fact, I am astonished Microsoft would even consider recommending this "workaround" - it is a highly insecure and extremely hack job of attempting to circumvent the object quota restrictions.
In my opinion, you should either create a specific role, which includes NO OTHER PERMISSIONS, that permits users with said role to create more than 250 objects ... or simply raise the limit and have it the same for everyone.  Of course, I would favor the former, as it would provide more fine-grained control over resources and minimize abuse of the privilege.  However, to recommend that any user needing to create more than the limit be granted an administrative role blows my mind and makes me think twice about the real security of Azure AD as it currently exists.  (e.g. If such recommendations are made publicly, what types of hacks are going on internally which may adversly affect our organizations?)
Please push this to the higher ups for a quick resolution with minimal or zero security impact.  There is no reason I can think of that a new role wouldn't be able to be created to do one thing - permit bypassing this restriction.
Thanks.


Lower leader election lease durations.

We currently alert if hive is down for 5 minutes, however our leader
election timeouts can easily blow past this if a pod loses
leader status without a clean exit.
These limits were originally from CCO and requests to avoid the default
writes to etcd every 2s.
Cut the limits in half such that we're writing to etcd every 30s, and we
timeout after 2 minutes, which should work well with our 5 min alert.

/assign @abutcher
/cc @suhanime

/lgtm


Added CUDA 10.1 compatibility

Due to compilation option, install wasn't available from package.

Thank you for the PR! Could you please comment a bit on what wasn't working?

Which OS did you try to compile on?
Does it fail with -O, but work with -O3?
Is there any nvcc version that would not support -O3, or can we just omit the version check?
Thank you!

Hello @f0k
Sorry for the delay,
Let me find a GPU VM and I'll say you.

@f0k I checked the documentation and for older versions default value is 3 for optimization anyway:
https://docs.nvidia.com/cuda/archive/9.2/cuda-compiler-driver-nvcc/index.html#ptxas-options
So technically there is no need for version check but I didnt try to compile with every version

@ynsgnr Thanks for the pointer! I checked with an old CUDA version (4.0), it doesn't do -O3 by default, but according to the documentation, it also expects the level to be given. So nvcc -O (without a level) should never have worked. I had taken it from the original cudamat Makefile.
So the correct solution would be to unconditionally pass -O3 instead of -O. @ZuluPro, can you amend your commit (i.e., change your code, do git commit -a --amend, then git push --force)? If it's too much of a hassle, I can do it myself. Cheers!

Merged manually since I couldn't push the requested change to your fork.


More interned string

This is a series of attempts to remove temporary strings. There is no evidence that this will help with anything, but it just seems cleaner.
Probably easier to read one commit at a time.

r? @alexcrichton
(rust_highfive has picked a reviewer for you, use r? to override)

Ah... like if the name has a " in it. I will put the cows back in the
morning and see if I can add a test to keep this supported.
On Fri, Jul 6, 2018, 8:38 PM Alex Crichton<EMAIL_ADDRESS>wrote:

@alexcrichton commented on this pull request.
In src/cargo/sources/registry/mod.rs
https://github.com/rust-lang/cargo/pull/5694#discussion_r200796893:

@@ -235,14 +234,14 @@ enum Field {

#[derive(Deserialize)]
struct RegistryDependency<'a> {

name: Cow<'a, str>,

I think for these the Cow was due to the derive above to handle escapes
in names if they ever creep in
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/rust-lang/cargo/pull/5694#pullrequestreview-135187297,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADiaQKyD8i8rCuFujgjJP-jrdUZrTjKCks5uEAMCgaJpZM4VGFF4
.

Cows are back, and test is added.

:sunny: Test successful - status-appveyor, status-travis
Approved by: alexcrichton
Pushing b02cd42d5bab187f0d2366f6a17f64ff2001c622 to master...

I was just looking at some profiles from >servo cargo generate-lockfile -Z no-index-update and RegistryPackage::Deserialize is ~3% So this clean up may have included some important parts of the code!
~90% was checking if files exist, reading files, or asking git to do the same.

Nice! How long does that take locally for you as well? 90% checking for files and such is pretty extreme, and it may be the next scaling bottleneck for Cargo...

I think it is not so long for evry cargo command. I don't wait that long for other projects. I think it is just that servo has a lot of git dependencies specified. Eche one needs to be checked out and parsed and checked for being a workspace, each time it is updated. So I don't think that a build command would have to do as much work, not that I tested it yet.  I am sure, if everything was that slow we would hear it from the servo team. :-)
servo>cargo +nightly generate-lockfile -Z no-index-update
    Updating git repository `https://github.com/servo/osmesa-src`
    Updating git repository `https://github.com/servo/webrender`
    Updating git repository `https://github.com/servo/gaol`
    Updating git repository `https://github.com/servo/devices`
    Updating git repository `https://github.com/energymon/energymon-rust.git`
    Updating git repository `https://github.com/pcwalton/signpost.git`
    Updating git repository `https://github.com/servo/rust-azure`
    Updating git repository `https://github.com/servo/fontsan`
    Updating git repository `https://github.com/energymon/energymon-sys.git`

Ah ok that makes more sense!


Allow for more frontend settings to be overridden

govuk-frontend allows a number of values in its SCSS styles to be modified but currently we only allow $govuk-brand-colour and $govuk-font-family to be modified.
This PR adds support for many more, but not all. I’ve excluded those that will be deprecated in v5.0, as well as those relating to form controls as this plugin is not designed to be used on sites that include forms.
Given the number of options, wondering if they should be moved under a top-level option name; perhaps settings? We can still keep brandColour and fontFamily, but deprecate them in favour of settings.brandColour and settings.fontFamily.
This change was done primarily for my own interests, but worth pointing out that without these changes, it is not currently possible to create a site that uses the same link colours as the MOD.UK Design System or page background colours as used by the Home Office Design System; this change would make that possible.
(See also this upstream fix to govuk-frontend: https://github.com/alphagov/govuk-frontend/pull/4268)
To do

[ ] Move options under a parent option value?
[ ] Add documentation

Also need to add:

$govuk-inverse-button-background-colour
$govuk-inverse-button-text-colour

Replaced by #216.


[🐛] Video quality is too low.

Description
launchCamera({
        mediaType: 'video',
        videoQuality: 'high',
        ...option,
})

The video qulity is too low even though videoQuality: 'high' passed
Solution
videoQuality seems not work at all.
Additional Information

Image Picker version: 5.3.1
React Native version: 0.71.7
Platform: ios
Development Operating System: Macos
Dev tools: xcode

Same from my side

This bug still exists on iOS 18


Microsoft Teams Update Process

This page does not cover at all how features are released.   We have a single tenant...all MS Teams clients running the exact same version and yet individuals within our tenant have different features exposed at the same time.   Some have the popout window feature, some do not.  Some have custom backgrounds, some do not.  Some have the raise hand feature, some do not.
We have no means as an organization to properly support our user community as we have no idea who will have what feature.  We want to announce new features and make sure users are aware of them, however, we cannot as it just leads to a bevy of phone calls about how they don't have the feature we announced (although some do).
It seems we have no means to control whatsoever when these features appear or do not appear for individuals within our organization.   It is very strange that an entire tenant does not get the same updates at the same time.  At the very least, however, this should be documented.
[Enter feedback here]

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

ID: f6da28da-eb7b-d3ae-4c2f-8f87803b1830
Version Independent ID: 8c42d7a2-80c6-86dd-347a-ed6d8d909c41
Content: Teams updates - Microsoft Teams
Content Source: Teams/teams-client-update.md
Service: msteams
GitHub Login: @LolaJacobsen
Microsoft Alias: lolaj

@joeljanke  Thank you for submitting feedback and contributing to the docs. We are currently investigating this

@joeljanke Thank you for reaching out to improve MS Docs. Please let me know this link helps - https://docs.microsoft.com/microsoftteams/troubleshoot-installation

@joeljanke We appreciate any feedback that improves the content in the Microsoft docs but we haven't had any response from you so we are going to close this issue.
Please feel free to re-open this issue if there is a specific area of the docs that we can improve or make better. Thank you.

Curious how "Can admins deploy updates instead of Teams auto-updating?
Teams does not give admins the ability to deploy updates through any delivery mechanism." is acceptable to the product group? This currently has my customer highly upset that there is no way for them to control the version of Teams on their network. Because of this they just found out that they have 17 versions of the Teams client installed. Curious how the product group thinks that is acceptable from a company like Microsoft?


[Model] New Annotation-only Azure Architecture model

          @SAHU-01 we're ready to incorporate this model as one of the out-of-the-box models in Meshery releases. Can you take next steps here?

Originally posted by @leecalcote in https://github.com/meshery/meshery.io/issues/1918#issuecomment-2419608329

@SAHU-01, @TraXIcoN is there any hope that we might actually complete this item?


FYI: Breaking change?

Hi,
I noticed you're registering 0.1.3, but while I didn't look carefully, it seems you're deleting a lot of stuff, and then if this is a breaking change the version number should be 0.2.0. Even with 0.x semver holds for Julia packages, then breaking changes up the 0.x.0, for 1.x.y and higher, breaking changes up the first number.

The deletions were some bad commits made from my machine where src/models/* was accidentally committed to src/* -- whoops.
Syntactically, there aren't many changes. The biggest changes are as follows:
Stats now works off of distribution objects, and you can test by providing distributions and data as a parameter. Right now I haven't diven into the cummulative distribution functions, but you can still get your stat and lookup on a table to get a proper P value.
Furthermore, documentation for most of stats, all of preprocess, and the new models is now over-hauled with markdown.
Additionally, there is the addition of  the RandomForestClassifier and DecisionTreeClassifier.
Lastly, consistency for pipelining is now universal. The objects for preprocess that use distributions now call on lstats distribution objects.
Todo on these updates:
Cdf (obviously)
More pdfs (thinking F, binomial revision, bernealli)
The nueral implementation needs modular layers, also am working on some time series lstm stuff in terms of that.
Improved documentation on functions that are unrevised.
Also -
Julia won't let you skip a version -- even so each version has a respective branch add Lathe#0.1.x


Non breaking spaces being stripped

Version
4.0.5
Environment info
no command :/ couldn't find anything about what vue info does so ¯\_(ツ)_/¯

Steps to reproduce
Add non breaking space characters. eg, in a component:
{{ text }}< template v-if="something">& nbsp ;< specialComponent />< /template>
they are stripped out by default and replaced with an ordinary space. (ignore the weird spaces. i needed some way to make those things appear in the form preview)
if i'm adding a non breaking space then there's a high chance i need it.
you can't even add a non breaking space with & nbsp ; but instead need to use {{ '\xa0' }}
What is expected?
non breaking spaces are preserved
What is actually happening?
non breaking spaces are removed and replaced with one ordinary space
non breaking spaces can only be added with what's pretty much an ugly hack

If you are looking for a configuration option then here it is: https://github.com/vuejs/vue/tree/dev/packages/vue-template-compiler#options (whitespace or preserveWhitespace)
If not, please report to https://github.com/vuejs/vue with the required minimal reproduction link.

This is a bug. whitespace: condense should not remove  , they are not whitespaces but non breaking whitespaces and there is a difference, if it is being added with an html entity vue should definitely not remove it or change it to something else


Refactoring augmenters

Codecov Report

Merging #79 into master will decrease coverage by 2.56%.
The diff coverage is 94.36%.

@@             Coverage Diff              @@
##             master      #79      +/-   ##
============================================
- Coverage     85.32%   82.75%   -2.57%
+ Complexity      142      128      -14
============================================
  Files            40       39       -1
  Lines           327      319       -8
  Branches         27       19       -8
============================================
- Hits            279      264      -15
- Misses           38       46       +8
+ Partials         10        9       -1

Impacted Files
Coverage Δ
Complexity Δ

.../algo3/engine/score/augmenters/ScoreAugmenter.java
100.00% <ø> (ø)
1.00 <0.00> (ø)

src/main/java/edu/fiuba/algo3/model/Question.java
83.33% <ø> (ø)
6.00 <0.00> (ø)

...algo3/engine/score/augmenters/ThreeMultiplier.java
80.00% <66.66%> (-20.00%)
3.00 <2.00> (ø)

...a/algo3/engine/score/augmenters/TwoMultiplier.java
80.00% <66.66%> (-20.00%)
3.00 <2.00> (ø)

...ba/algo3/engine/score/augmenters/NoMultiplier.java
75.00% <75.00%> (-25.00%)
3.00 <3.00> (ø)

...engine/score/augmenters/ExclusivityMultiplier.java
90.00% <87.50%> (-10.00%)
5.00 <4.00> (ø)

.../java/edu/fiuba/algo3/constants/AugmenterType.java
87.50% <100.00%> (-1.39%)
4.00 <1.00> (-2.00)

.../java/edu/fiuba/algo3/constants/AugmenterUses.java
100.00% <100.00%> (ø)
1.00 <1.00> (ø)

.../edu/fiuba/algo3/engine/score/ScoreCalculator.java
100.00% <100.00%> (ø)
6.00 <6.00> (+1.00)

src/main/java/edu/fiuba/algo3/model/Game.java
83.33% <100.00%> (ø)
14.00 <4.00> (ø)

... and 11 more

Continue to review full report at Codecov.

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


[Snyk] Security upgrade next from 12.2.4 to 13.5.0

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to fix one or more vulnerable packages in the `npm` dependencies of this project.
Changes included in this PR

Changes to the following files to upgrade the vulnerable dependencies to a fixed version:

package.json
package-lock.json

Vulnerabilities that will be fixed
With an upgrade:

Severity
Priority Score (*)
Issue
Breaking Change
Exploit Maturity

658/1000  Why? Proof of Concept exploit, Recently disclosed, Has a fix available, CVSS 5.3
Resource Exhaustion SNYK-JS-NEXT-6032387
Yes
Proof of Concept

(*) Note that the real score may have changed since the PR was raised.

Commit messages

Package name: next
    The new version differs by 250 commits.

ffafad2 v13.5.0
4a589ed v13.4.20-canary.41
deb81cf fix styled-jsx alias (#55581)
1a9b0f6 improve internal error logging (#55582)
0631549 Fix react packages are not bundled for metadata routes (#55579)
bad5365 Update supported config options for Turbopack (#55556)
8881c41 Fix useState function initialiser case for `optimize_server_react` transform (#55551)
1025011 Add react-icons to optimizePackageImports (#55572)
d5c35a1 chore: replace issue triaing actions with `nissuer` (#55525)
33c561b Consolidate experimental React opt-in & add `ppr` flag (#55560)
f630cb8 Add `mui-core` to the default `optimizePackageImports` list (#55554)
caa9083 chore: Fix heading hierarchy in revalidateTag documentation (#55470)
d01ab61 v13.4.20-canary.40
6123a97 Fix missing trace file and unhandledRejection in ensurePage (#55553)
b5beb3a Correct spelling in playwright docs (#55557)
4c6d4b3 Type Error on Event Type payment_intent webhook (#55493)
41c89f0 v13.4.20-canary.39
7fe01bb Disable client-only for middleware and pages api layer (#55541)
e4439b1 chore(third-parties): replace rimraf with rm.mjs (#55547)
1b8ce8f Add route groups example to revalidatePath doc (#55543)
9697bcd Fix notFound status code with ISR in app (#55542)
0338dcd fix next.js own build on windows (#55544)
4f98dc6 v13.4.20-canary.38
0ddb15b fix: run turbopack in forked process (#55545)

See the full diff

Check the changes in this PR to ensure they won't cause issues with your project.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
🛠 Adjust project settings
📚 Read more about Snyk's upgrade and patch logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Resource Exhaustion

👷 Deploy Preview for master0101 processing.

Name
Link

🔨 Latest commit
62be1f134aba6f8f91309e746fa75f99736bf48b

🔍 Latest deploy log
https://app.netlify.com/sites/master0101/deploys/65394ff1106d520009e9fd5d


python3Packages.torchWithRocm: 2.0.0 unnecessarily requires unfree dependencies

Issue description
Once we update python3Packages.torch to 2.X.X, its torchWithRocm variation will depend on cudaPacakges.cuda_nvcc (through python3Packages.openai-triton), which is unfree. This means hydra won't be building and caching torchWithRocm.
Upstream enforces that there be a copy of bin/ptxas (from cuda_nvcc):

https://github.com/pytorch/pytorch/blob/558e5a240e0c2a5e9a0d5350fe6c25b029efca6a/setup.py#L931
https://github.com/openai/triton/blob/01a93185a1105cf4b3ab504ec385ff3585160932/python/setup.py#L211

However, they do not actually use it except for cuda support (obviosuly).
We should patch around this to re-enable caching, and we should work with upstream to make the dependency optional in the first place
CC @NixOS/rocm-maintainers

Sadly, with the new ROCm updates, I've only made it worse.
We can't seem to reasonably patch hsa-amd-aqlprofile out of rocprofiler anymore.

This was fixed in 6f3f5b64f2cb52294097f9b2b74762cb7776c95e and #263048.


Resolve framework versions correctly in error page footer

Followup to https://github.com/aspnet/Hosting/pull/726.
Currently we generate footers like

which uses assembly version as the .NET Framework version. This is not very useful and the version should look like 4.5.1, 4.6, ...
cc @DamianEdwards

We can do this now in 3.0.0 with https://github.com/dotnet/core-setup/issues/4453.
AppDomain.CurrentDomain.GetData("FX_PRODUCT_VERSION") should return the version.


Plaza and Pedestrian Zones have broke Realistic Parking Feature

Describe the problem
Steps to reproduce

Create Ped Zone
Zone Ped Zone
Let Game run a bit before a car becomes utterly confused and breaks itself blocking up traffic for miles

Screenshots?
https://gyazo.com/1139ef27e2209102f1ab6eb7d975f513
Notes or questions?

Cars get confused because you've placed parking spots near pedestrian streets that cars are not allowed to use.
Parking AI works like this:

citizen is forced to park his car
TMPE is searching for parking spot (either building parking or parking lane)
TMPE is trying to find path between current car position and parking spot (here everything fails).
DLC didn't break Parking AI. The feature has never handled correctly a scenario where access to parking spot is restricted

Cars get confused because you've placed parking spots near pedestrian streets that cars are not allowed to use. Parking AI works like this:

citizen is forced to park his car
TMPE is searching for parking spot (either building parking or parking lane)
TMPE is trying to find path between current car position and parking spot (here everything fails).
DLC didn't break Parking AI. The feature has never handled correctly a scenario where access to parking spot is restricted

Nope, Ill attach save file
https://gyazo.com/b939809a92c94f73339fe422da1ab038

Yeah, savegame would be useful, either file or share via Steam (guide in the wiki)

Yeah, savegame would be useful, either file or share via Steam (guide in the wiki)

https://gyazo.com/b939809a92c94f73339fe422da1ab038

Yeah, savegame would be useful, either file or share via Steam (guide in the wiki)

Here ya go https://steamcommunity.com/sharedfiles/filedetails/?id=2867763274

They stuck because of your road settings.
Vehicle is waiting on green segment at the bottom. Wants to park at red segment but on the road side that goes downwards.
It's impossible (most likely path is too long since it forces car to go to the main city far on the right to do a U-turn somewhere).

Notice lane connections (cars cannot ignore those). U-turn is not allowed, segment on the right allows only for incoming flow of vehicles so vehicles which exit from the main road are trapped inside.

Reverse direction of the highway road on the right or remove lane connections and allow U-turn and vehicles will immediately unstuck.
Here another potential problem. Depends on where is the vehicle it may also stuck because of no path (cannot use pedestrian street to access parking)

Alright well that explains that but what about in the main City at the T intersection, why are vehicles getting stuck there?

Also, why don't they just reroute to a different spot instead of getting stuck?

They stuck because of your road settings. Vehicle is waiting on green segment at the bottom. Wants to park at red segment but on the road side that goes downwards. It's impossible (most likely path is too long since it forces car to go to the main city far on the right to do a U-turn somewhere).

Notice lane connections (cars cannot ignore those). U-turn is not allowed, segment on the right allows only for incoming flow of vehicles so vehicles which exit from the main road are trapped inside.
Reverse direction of the highway road on the right or remove lane connections and allow U-turn and vehicles will immediately unstuck.
Here another potential problem. Depends on where is the vehicle it may also stuck because of no path (cannot use pedestrian street to access parking)

Alright I went ahead and did a quick test and allowed U-turns at that intersection but cars still got stuck at those intersection, but if you look at the buildings they are trying to go to they are all in the pedestrian ahead hence my belief its to do with the Ped Areas, also PS I did try removing ALL parking lots just as a quick bug test but that didn't fix the issue

I found some weird issues in the pathfinding. The reason why vehicles can stuck is pathfinding returns path that contains incorrect lanes (non-vehicle), but only if Parking AI is enabled. I'm working on fix.

. I'm working on fix.

BTW: I noticed this issue here, too, but even for cars that want to go to a destination that is nowhere near the pedestrian road.
I started my pedestrian road by changing the last 2 segments of a cul-de-sac to be pedestrian roads. Now cars get stuck when driving by the junction that goes into that road, even when they want to go to a target that is 5 blocks away. They seems to always be on the turn lane that leads in the opposite direction of the pedestrian zone, even though they'd need to go straight to get to their destination.
I just watched the Traffic Routes overlay for a couple of minutes and I noticed several cars driving weird routes. One drove past the left turn into its destination, followed the road for 8 blocks, turned around in a side street, passed by its destination, did a u-turn and then turned left into into its home street. This may be the reason why cars that only need to pass by near the pedestrian street segment get suck?
Which reminds me that I spent most of the evening yesterday nailing down lane permissions to make it impossible for my busses to randomly turn left or right instead of following their route. Interestingly this only happend on the street that passes by the cul-de-sac which ends in pedestrian road segments.
TL;DR: This also affects vehicles that have no reason to go into/through a pedestrian road by just being near it.


A package for inspecting the build-time environment

Summary

A new package that deals with build-time configuration. See additional comment on PR for some open questions I'd like feedback on.
I'm not married to any naming choices I've made. Bikeshed away. I have a preference for something self-explanatory in light of recent conversations about how to make buildpack-building libraries more accessible to newbies and those who don't have English as their first language.
I will add GoDoc if/when this PR is closer to merging 🙂
Use Cases

Buildpacks frequently read from the build environment to make decisions about their behaviour.  There are examples across essentially every language family. Currently, unit tests for these buildpacks are run sequentially to avoid test pollution caused by modifying os.Env(), which is global state.
In addition, there are a few common patterns that arise across buildpacks (with some selected examples):

reading values from environment variables but falling back to defaults if unset:

BP_DOTNET_PROJECT_PATH
BP_NODE_PROJECT_PATH

reading  environment variable values as shell words

BP_GO_BUILD_FLAGS in go-build
BP_DOTNET_RESTORE_FLAGS and BP_DOTNET_PUBLISH_FLAGS per .NET Buildpack RFC 0003

reading environment variables as booleans to enable/disable certain features

BP_LIVE_RELOAD_ENABLED per RFC0032, which will be implemented in all Paketo buildpacks

Checklist

[ ] I have viewed, signed, and submitted the Contributor License Agreement.
[ ] I have linked issue(s) that this PR should close using keywords or the Github UI (See docs)
[ ] I have added an integration test, if necessary.
[ ] I have reviewed the styleguide for guidance on my code quality.
[ ] I'm happy with the commit history on this PR (I have rebased/squashed as needed).

@fg-j I'm good with this! @ForestEckhardt @ryanmoran y'all have opinions here?

I think the implementation here looks technically sound. I just have questions about the utility, and that's likely a bit subjective. I just can't imagine using this package. Maybe that just means I don't have the problems its trying to solve?

Thanks for bringing that up @ryanmoran. My impetus for writing this was the proliferation of some repeated env var checking code that has come up as we implement support for hot reloading. We do basically the same thing in:

python start
go build
dotnet execute
node start
yarn start and npm start will soon do the same, too

All that repetition made my refactor senses tingle. The only preexisting shared library that all of the above buildpacks pull from is packit, so I tried pushing the functionality here.


Generate rubocop_todo.yml

This PR adds a rubocop_todo.yml file to root. This file was generated using the --auto-gen-config flag. This file can be leveraged to understand areas for "improvement" in the application code, and provide an easier path towards resolving offenses.
No worries if this is not something the rspec-core team wants to include. I noticed you recently upgraded to the most recent version of RuboCop.
If this is accepted, there are a few steps I'd recommend come next.

Add the cop Departments into rubocop_rspec_base.yml file. So instead of just MethodLength, this would be Metrics/MethodLength.
Alphabetize both rubocop config files to make it more user friendly when looking up your linting conventions. This also makes it easier to cross reference.
Revisit the mass disabling of rules during upgrade. These decisions can definitely be put off. But removing the falses and then regenerating this todo file presents a clear view of the current state of the project (in the view of rubocop, of course). I've found it had to make decisions about these all at once because there are 300+ cops with granular configurations. Often there is a setting for a cop that is preferable to disabling it. Not always though :).
Start addressing desired refactorings/fixes one group of related rules at a time, utilizing --auto-correct when possible.

Happy to do any of these things in follow up PRs. Also happy if you decide this doesn't sound like a good direction for the repo and this PR is closed :) .

Let me know if you'd like me to reopen, or do any rubocop logistics once the repos have been combined :).


Fails to compile a valid build

I'm not really sure this is actually a Mill issue, but rather due to the recent changes in coursier.  In my github-dependency-graph Mill plugin I came across a bug in coursier in the past about reconciled versions containing ranges. I added some hacks to work around it but recently with the pr to support the 0.12 series here I noticed that the behavior for this specific case changes a bit now and won't even compile when I believe it should. Given a minimal build like this:
import mill._, scalalib._

object minimalDep extends ScalaModule {
  def scalaVersion = "2.13.15"

  def ivyDeps = Agg(
    ivy"com.fasterxml.jackson.core:jackson-core:2.13.3"
  )
}

object minimal extends ScalaModule {
  def moduleDeps = Seq(minimalDep)

  def scalaVersion = "2.13.8"

  def ivyDeps = Agg(
    ivy"org.jongo:jongo:1.5.0"
  )
}

In earlier versions of Mill this would compile just fine. The reason I had this test is the jongo here wants a range of jackson data-bind [2.7.0,2.12.3] where jackson-core specifically wants 2.13.3. These should be compatible and 2.13.3 should be resolved and all should work fine. However, with 0.12.4 this no longer compiles:
[84/84] ============================== __.compile ============================== 3s
1 tasks failed
minimal.resolvedIvyDeps coursier.error.ResolutionError$ConflictingDependencies: Conflicting dependencies:
com.fasterxml.jackson.core:jackson-core:2.12.3 or [2.7.0,2.12.3] wanted by

  com.fasterxml.jackson.core:jackson-databind:2.12.3 wants 2.12.3
  └─ org.jongo:jongo:1.5.0 wants com.fasterxml.jackson.core:jackson-databind:[2.7.0,2.12.3]

  org.jongo:jongo:1.5.0 wants [2.7.0,2.12.3]

    mill.util.CoursierSupport.resolveDependenciesMetadataSafe(CoursierSupport.scala:312)
    mill.util.CoursierSupport.resolveDependenciesMetadataSafe$(CoursierSupport.scala:249)
    mill.util.Jvm$.resolveDependenciesMetadataSafe(Jvm.scala:15)
    mill.util.CoursierSupport.resolveDependenciesMetadataSafe(CoursierSupport.scala:339)
    mill.util.CoursierSupport.resolveDependenciesMetadataSafe$(CoursierSupport.scala:320)
    mill.util.Jvm$.resolveDependenciesMetadataSafe(Jvm.scala:15)
    mill.util.CoursierSupport.resolveDependencies(CoursierSupport.scala:80)
    mill.util.CoursierSupport.resolveDependencies$(CoursierSupport.scala:56)
    mill.util.Jvm$.resolveDependencies(Jvm.scala:15)
    mill.scalalib.Lib$.resolveDependencies(Lib.scala:158)
    mill.scalalib.CoursierModule$Resolver.resolveDeps(CoursierModule.scala:216)
    mill.scalalib.JavaModule.$anonfun$resolvedIvyDeps$3(JavaModule.scala:779)
coursier.error.ResolutionError$ConflictingDependencies: Conflicting dependencies:
com.fasterxml.jackson.core:jackson-core:2.12.3 or [2.7.0,2.12.3] wanted by

  com.fasterxml.jackson.core:jackson-databind:2.12.3 wants 2.12.3
  └─ org.jongo:jongo:1.5.0 wants com.fasterxml.jackson.core:jackson-databind:[2.7.0,2.12.3]

  org.jongo:jongo:1.5.0 wants [2.7.0,2.12.3]

Shouldn't these be compatible, 2.12.3 be resolved, and all compile fine?

I think this should resolve properly. Is this with Mill 0.12.4? Could you please verify, if this works with Mill 0.12.3? It is likely related to https://github.com/com-lihaoyi/mill/pull/3924. @alexarchambault Do you have an idea?

I think this should resolve properly. Is this with Mill 0.12.4? Could you please verify, if this works with Mill 0.12.3? It is likely related to #3924. @alexarchambault Do you have an idea?

So it looks like this broke in general with the 0.12.x series. I confirmed that it works with 0.11.13, but not with 0.12.0 and onwards.

I think we're seeing two things here:

since 0.12 and https://github.com/com-lihaoyi/mill/pull/3513, we report such conflicts (the coursier 2.x API handles that for us). Mill <= 0.11 used to trap those conflicts
[2.7.0,2.12.3] and 2.12.3 ought to be compatible, indeed. That looks like a bug in coursier.

@ckipp01 In the build example above, you're using 2.13.3 as a version for jackson-core? That's a typo, right? You meant 0.12.3? I can't reproduce the conflict with 0.12.3 on the command-line

I would say the bug is in the conflict message of coursier, not in the resolver itself:
$ cs resolve com.fasterxml.jackson.core:jackson-core:2.12.3 org.jongo:jongo:1.5.0
com.fasterxml.jackson.core:jackson-annotations:2.12.3:default
com.fasterxml.jackson.core:jackson-core:2.12.3:default
com.fasterxml.jackson.core:jackson-databind:2.12.3:default
de.undercouch:bson4jackson:2.12.0:default
org.jongo:jongo:1.5.0:default

$ cs resolve com.fasterxml.jackson.core:jackson-core:2.13.3 org.jongo:jongo:1.5.0
Resolution error: Conflicting dependencies:
com.fasterxml.jackson.core:jackson-core:2.12.3 or [2.7.0,2.12.3] wanted by

  com.fasterxml.jackson.core:jackson-databind:2.12.3 wants 2.12.3
  └─ org.jongo:jongo:1.5.0 wants com.fasterxml.jackson.core:jackson-databind:[2.7.0,2.12.3]

  org.jongo:jongo:1.5.0 wants [2.7.0,2.12.3]

(it should have printed com.fasterxml.jackson.core:jackson-core:2.13.3 rather than com.fasterxml.jackson.core:jackson-core:2.12.3 in the second run)

@ckipp01 In the build example above, you're using 2.13.3 as a version for jackson-core. That's a typo, right? You meant 2.12.3? I can't reproduce the conflict with 2.12.3 on the command-line (I can't reproduce there the bug you seem to be running into)

ahhhh actually I did have 2.13.3 correctly, but was confused by the error message. The range is actually incompatible with 2.13.3, but I was focused on the error message which makes it seem like 2.12.3. So I guess this isn't an error here with Mill, or really an error at all in logic, just a confusing error message.


Added Padang State Polytechnic domain JetBrain whitelist

add Padang State Polytechnic as a domain
you can check the official information here regarding Information Technology https://ti.pnp.ac.id
one of the largest Information Technology academies in West Sumatera Indonesia

@wandriputra First stage of verification passed, official domain is pnp.ac.id as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

@wandriputra I have to close this request without merging, because you requested to add a non-existent domain to this repository: ;; connection timed out; no servers could be reached Please ensure that you are familiar with this repository rules located at the bottom of this page and submit a new request with the correct information. Thank you for your understanding!


[tutorial] Add checklist to sidebar

Removes "Before you go"
Adds Checklist to sidebar

LOVE THIS, @Jutanium! I popped in and fixed 1.1, but the rest all look good.


Fixes #204 Search Minimum BIN

Clear transfer cache before querying market.
Use new DTO.

LGTM, thanks!

@furkick @Mardaneus86  Thanks A lot...
How can I clear transfer market cache?


Upsert Function shouldn't lose data that the caller wasn't aware of

Currently when saving a doc, the save is absolute:
            var updates = ordered.Where(x => x.Column != "id" && x.Column.IsNotEmpty())
                .Select(x => $"\"{x.Column}\" = {x.Arg}").Concat(systemUpdates).Join(", ");

Which generates:
data = $1

More or less.
This means if the existing doc is:
{
   "Id": 1,
   "FullName": "Phillip Haydon"
}

And you have 2 applications running against this document and you reploy a new version of 1 of those apps which:

You decide to replace Full Name with First / Last name.
Patch any existing documents.

If you save from the new deployment the save doc would look like:
{
    "Id": 1,
    "FirstName": "Phillip",
    "LastName": "Haydon"
}

The upsert function would delete the FullName property from the doc, breaking the existing app.
We should change this to apply the new doc to he existing doc.
data = data || $1

This would result in only new properties and changes in the new doc to be applied to the old doc:
The above scenario would result in:
{
    "Id": 1,
    "FullName": "Phillip Haydon,
    "FirstName": "Phillip",
    "LastName": "Haydon"
}

This allows patching to be applied without the risk of document data being lost.

I've tested this and see 0 change in the update perf on a large document, but I can't figure out a way to save LOTS of things to see if there is any real performance loss.
However I believe any perf loss is outweighted by the benefits of not losing document data.

So this only works for top level properties and breaks in nested properties.

It's by design because jsonb_concat is a "shallow concatenation" [1].
Here is a related thread in hackers [2]. "Deep concatenation" functionality
is still to be implemented, but you can use jsonb_deep_extend from this extension [3].

[1] https://wiki.postgresql.org/wiki/What's_new_in_PostgreSQL_9.5#jsonb_.7C.7C_jsonb_.28concatenate_.2F_overwrite.29
[2]<EMAIL_ADDRESS>[3]<EMAIL_ADDRESS>
We can have a flag to turn this on in future versions of PostgreSQL when it becomes avaliable, but for not I'm closing this as it's not possible. :(


added recently-played endpoint

not sure if the test on after vs before is correct (if one is set, the other must not be specified)

This mostly looks good, thanks for the PR!
A test is needed, though. If you need some inspiration, testGetFeaturedPlaylists is a good one. Let me know if you need any help!

Thanks for the comments, will apply the changes and provide a test.
Just need to know how to make changes/edits to the PR. It says that I need "push access" to the patch-1 branch... (first time I do that on github :) )
Also, about the test I am not sure if I get what they are and how to...test them, but I should also do a PR for it, right ?

It looks like you deleted your fork of this repository. I'm not sure if it's possible to continue working in this PR. Perhaps if you fork this repository again and create a branch named patch-1 again. But clone the fork to your computer so you don't have to work in the GitHub UI :)
If it's impossible to continue working on this PR, just submit a new one with the changes and a test in the same one :)

forked it again, added the changes in patch-1 and patch-1-1 for the test. let me know

It looks like you need to open a new PR, so I'm gonna close this one.
But merge those two branches first so we get the test and the new method at the same time.
Thanks!

I opened a new PR (finally kinda understood how that works :)) #68


Nothing

UHH there's nothing there

Sorry, but we are working on that.
LOCKED AND LOADED

BUT, there is still nothing there.

FOR THE LAST TIME, we are working on it!!!


.Net 7 throw 'System.TypeInitializationException' in FastReport.dll

A piece of very simple code,  Report invoiceReport = new Report();
then application throw an exception.
It looks like causing by using GDI+  in MacOS,  the error log mentioned 'libgdiplus'.
Any idea about that?
Thanks
Expected behavior
Report invoiceReport = new Report();
// throw the exception once I new a instance.
Stacktrace
Exception thrown: 'System.TypeInitializationException' in FastReport.dll
[08:51:40 ERR] ---------- RemoteServiceErrorInfo ----------
{
"code": null,
"message": "An internal error occurred during your request!",
"details": null,
"data": {},
"validationErrors": null
}
[08:51:40 ERR] The type initializer for 'FastReport.Report' threw an exception.
System.TypeInitializationException: The type initializer for 'FastReport.Report' threw an exception.
---> System.TypeInitializationException: The type initializer for 'FastReport.Utils.Config' threw an exception.
---> System.TypeInitializationException: The type initializer for 'FastReport.TypeConverters.FontConverter' threw an exception.
---> System.TypeInitializationException: The type initializer for 'Gdip' threw an exception.
---> System.DllNotFoundException: Unable to load shared library 'libgdiplus' or one of its dependencies. In order to help diagnose loading problems, consider setting the DYLD_PRINT_LIBRARIES environment variable:
Screenshots
If applicable, add screenshots to help explain your problem.
Device (please complete the following information):

OS: MacOS 13.4.1

Additional context
Add any other context about the problem here.

Try to install  libgdiplus
brew install mono-libgdiplus

Try to install libgdiplus brew install mono-libgdiplus

It does no work. I tried it before.

You need to use FastReport Core Skia. You can read more in this article
https://www.fast-report.com/en/blog/show/fastreport-core-skia/


feat: Greyish palettes and swatches

Closes #16

@rultor merge

@rultor merge

@rafamizes OK, I'll try to merge now. You can check the progress of the merge here

@rultor merge

@rafamizes Done! FYI, the full log is here (took me 2min)

Merged by Rultor.


Col order not working in React 16.2.0

The order classes were not showing up for my Col elements so I assumed something was wrong with my syntax.
So I copied the entire Layout example from here to test and but had the same issue.
Other properties like size and offset work fine but order does not show up at all as a class.

This should work now, order is supported with the latest release.


WATCH OUT! use ajp read_file, the target is down!!!

I use is only one time, the target host is down and can't do anything
socket.error: [Errno 10054]
the host rerjects my connection?
what code triggers it

Hi,
I don't understand your issue. Can you please provide more details such as:

Is the target up?
Is the AJP port exposed and reachable?
Which options are you using?
What is the Tomcat version?

Without further details, I cannot help you.

my issue is about read_file 'Exploit CVE-2020-1938'
the target is up.
ajp port 8009 is open.
here I tried another script on github, it works, but the return has Chinese characters and unreadable, then I found your script, I use yours, it works but still can't read the Chinese characters, then I changed decode 'gbk' in line 387, then I tried again, the result is:
socket.error: [Errno 10054]
and can't connect it again

I'm sorry but I did not test against instances with Chinese characters and I cannot work on this at the moment.
Feel free to make a pull request if you manage to fix this issue, it would be awesome :)


[TOPI] LRN & L2norm Operator

LRN operator for caffe alexnet model to use with onnx frontend

@sxjscience can you help review this?

I'll check the formula next week... This week I decide to focus on the MT demo.

Looks that the functionality can be implemented by stacking multiple reduce/broadcast ops in TOPI.

@sxjscience
For better readability I have split the implementation as per the LRN equation. This way is also correct right?

@sxjscience Using broadcast/reduce I feel it will be difficult since we need to compute for a selected area based on the "local size" parameter, thats why i used reduce_axis to do the sum operation.

Yes, you are correct. Stacking multiple reduce/bcast seems to be infeasible. I’ll check the implementation in detail this week. Currently too busy with other works...
Get Outlook for iOShttps://aka.ms/o0ukef

From: Pariksheet Pinjari<EMAIL_ADDRESS>Sent: Sunday, March 18, 2018 11:32:47 PM
To: dmlc/tvm
Cc: Xingjian SHI; Mention
Subject: Re: [dmlc/tvm] [TOPI] LRN Operator (#1000)
@sxjsciencehttps://github.com/sxjscience Using broadcast/reduce I feel it will be difficult since we need to compute for a selected area based on the "local size" parameter, thats why i used reduce_axis to do the sum operation.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/dmlc/tvm/pull/1000#issuecomment-374113938, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AE8D7nEnQ6OrqVZcDjMgF707rdSGCTXCks5tf1EPgaJpZM4SpTLK.

I will upload L2norm operator implementation also along with this pull request, please help to review together.

ping @sxjscience can you take another look

Review comments are updated in https://github.com/dmlc/tvm/pull/1051


ci: continue when Ana06/get-changed-files step fails

Turns out this action in this step can not real with scheduled runs:
Run<EMAIL_ADDRESS>  with:
    format: json
    token: ***
    filter: *
  env:
    HAS_BUILDPULSE_SECRETS: true
    PRISMA_TELEMETRY_INFORMATION: prisma test.yml
    PRISMA_HIDE_UPDATE_MESSAGE: true
Error: This action only supports pull requests and pushes, schedule events are not supported. Please submit an issue on this action's GitHub repo if you believe this in correct.
Base commit: undefined
Head commit: undefined
Error: The base and head commits are missing from the payload for this schedule event. Please submit an issue on this action's GitHub repo.
Error: Not Found

via https://github.com/prisma/prisma/actions/runs/4029879690/jobs/6928157785
This change should make the next step to run anyway, which would then decide to run all the tests, as intended.
Docs on used property: https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepscontinue-on-error

Alternative solution from Pierre: https://github.com/prisma/prisma/pull/17598

This didn't work because we didn't test it 😄
I did a commit to fix in https://github.com/prisma/prisma/commit/3fde8fb4aaf2f6b011d5db17e3ed0c7a1f1546d5

@Jolg42 That's the problem of individual actions - hard to test :/

Note: this should work now https://github.com/prisma/prisma/commit/3e695e75aa27059dd957383526b590466f24bad3


$zk_session_timeout

Hi there,
Greetings,
May I know what is the best practice here to add an --zk_session_timeout option when starting the Mesos master?
Kind regards,
Tamama

Typically via options:
class{'mesos::master':
  options => {
    zk_session_timeout => 20
  }
}

or via hiera config:
mesos::master::options:
    zk_session_timeout: 20

Though I figured that out sometime ago from your source code, I thank you for confirming the answer. :)


Decide on semantics for workspace environment syncing (with --package, --extra, and --dev)

We had an extensive discussion about this in Discord. I'll try to summarize some of it here, but we still need to make some important decisions about how virtualenv syncing should behave for workspaces. Most of these changes aren't hard to implement, but they do have a lot of follow-on impact.
Today, we use a single virtualenv at the workspace root. When you do uv run -p package, we bring the environment in-sync with the necessary dependencies for package. That is, we don't install the entire workspace -- only the dependencies that are required for package. This has the benefit that you can't accidentally import some other dependency from the workspace within the package code (it enforces some amount of isolation).
However, this syncing is purely additive. So if you run uv run -p foo then uv run -p bar, we'll install any packages necessary for bar, but we won't uninstall the packages that we needed for foo (but not bar).
Extras behave similarly.
This strategy has some desirable properties (we enforce isolation on initial uv run -p, we only sync the necessary packages rather than building the entire workspace) but it's sort of a compromise (we don't enforce strict isolation on subsequent uv run -p).
One alternative we discussed was: creating a virtualenv per package in the workspace, on-demand. So if you did uv run -p package, we'd create a virtualenv in package with that package's dependencies. We'd also have a virtualenv in the workspace root.
This gives us the same properties that we have today, with the added benefit that it does enforce strict isolation. But there are two downsides: (1) you now have multiple virtualenvs in your project, which could confuse editors (I think this is totally fine); (2) you don't have a single virtualenv with the entire workspace installed, which means your editor could lack completions and Go-To definition for packages in the workspace (this problem also exists today); and (3) it doesn't solve the extras problem.
(3) seems to be the critical one. Extras are kind of the same problem (stateful environments) as -p, but don't have a natural analog to "store the virtualenv in the package". In short, we leave extras enabled after a uv run, and this could be problematic for some packages.
One solution to the "extras" problem would be to do a strict sync on every uv run. So if you did uv run -p foo --extra bar and then uv run -p foo, we'd remove the bar extra on that second invocation. The main downside here seems to be that you uv sync -p foo --extra bar and then uv run -p foo would remove the bar extra, which some have argued is unintuitive. (N.B. uv sync -p foo does not exist today.)

One proposal:

uv run --package creates a venv in --package
uv run operates with pip install semantics (doesn't remove extraneous packages)
uv sync operates with pip install semantics
uv sync --locked operates with pip sync semantics
uv run --locked operates with pip sync semantics

Another proposal from @konstin:

Alright here's the pitch:

uv sync installs everything in .venv. That gives your IDE (and type checkers) all packages for analysis. uv sync retains --package and --extra, but they are when you need that level of control, most users should use uv run. If you use uv sync with parameters, you effectively opt in to managing venv state yourself.
uv run runs in a separate environment by default. We place that venv under .uv/venvs, so you can clean it up with rm -rf .uv and inspect it if needs be. This means there are only two folder in your project with uv state (.venv and .uv; that's one too many for me already, but we don't get out of .venv)
If you need a per-project env, you can cd packages/bert && uv venv && uv sync -p bert. It's a regular venv still so IDEs will run regularly just on this package.
When you do uv run -p bert --extra torch, we create something like .uv/venvs/bert-torch with exactly that set of dependencies. This means that you get both a strict invocation and a cached environment on the next run. (ofc if your lockfile changed, we update the env)

In a way this gives us three levels in the uv CLI:

The pip mode, everything is manual, there are the known quirks. Interesting for users coming from pip and pip-tools
Managing your venv manually with uv sync --package ... --extra .... Similar to poetry or pdm, that's probably what i'd use a lot cause that's where my level of expertise is
The managed uv run mode. You shouldn't know about venvs at all beyond "my IDE see .venv" to use this. This is the easiest, most user friendly way, but also the one with the least control when you're used to pip installing to your hand-curated venvs.

The huge drawback here: Modulo default-{packages,extras,command}, you have to specify all arguments in every uv run every time.

I want to add another perspective to this: It says the problem we're looking at is venv state. There are several things that influence the state of the venv:

Additional packages, both workspace packages (-p) and extras (--extra). To me, a workspace is one big virtual package where the members are optional dependencies like extras, so i've put them here with the extras.
Removing packages, such as --no-dev
Changing the python version. Changing the python version has the effect that we have to change many packages and that the meaning of extras can change (through markers with both python version and extra condition).

Different use cases want different venvs:

IDEs, type checker and other linters want to have a .venv with all dependencies installed (for slightly different definitions of all) so they can inspect your dependencies.
When running pytest on a specific of package on a specific python version with specific extras i'd like to test only that configuration. In this case, i'm ready to specify what exactly i need and generally accept that the venv is temporary,
When i run e.g. the backend entrypoint, it would be nice if only the backend dependencies were available to check they are correct (nice to have).
When deploying (mainly docker containers), i want to sync only a specific set of packages, extras and no dev deps.

Contrary to the pitch in the comment above, i've realized that for my use cases, isolation generally isn't that important, i'm fine with a single "everything venv", as long as i can run with isolation when i need it. Caching isolated temporary venvs created e.g. running pytest with isolation (ideally in a single gitignored folder in the project root where i can clear them) would be nice.

I'd agree with @konstin - and that's something that might be useful for Airflow.
For development, even for regular running of the tests, having single .venv where you can install all packages is ideal, while you have a way to run tests or scripts in separate, isolated venvs. You should be able to choose whether you want to install all packages or just one or few packages there.
There are cases where you have "main" package and "extra" packages and some of the extra packages have (sometimes optional) dependencies on each other - and in this case isolated environments will not work - because even for tests you need the "other" packages as well - at least for some of the tests.
So natural behaviour would be:
a) run your development, autocomplete, tests in your "all-combined" environment.
b) cd to your package and run your tests (or subset of those that do not require other packages) there in an "isolated environment).
c) (optional) allow those "isolated" environments to install other packages if you really want (to be able to test those cross-package tests)
I think choosing which packages to install and syncing the "main" or "isolated" (if c) is supported) venvs should be purely additive - UNLESS you deliberately choose to cleanup the venv before. That should simplify all the "remove package from spec" cases - you allow the venv to have more things than needed, and if. you really want a clean version, run the installation with --clean switch.

Relatedly: we need to consider how this will interact with the red-knot work...

A few competing concerns:

We want the user to have a great editor experience -- one that "just works". This likely requires (1) a fully-populated virtualenv, with all packages and extras that (2) exists at the repo root, rather than being hidden away in some cache directory.

We'd like to avoid syncing any more packages than are necessary when the user runs a command. For example, uv run -p foo shouldn't need to install and build bar in the workspace, if it's not in the foo dependency tree.

We'd like to avoid allowing users to import packages that aren't declared as dependencies for a given workspace member (i.e., enforce some isolation). The same applies to extras: we'd like to avoid allowing users to import an extra dependency that hasn't been requested.

Here's my latest proposal:

We keep our current behavior for now. This includes: a single virtualenv at the root that's updated additively (i.e., with pip install semantics). So running uv run -p foo from an empty state would add foo and its dependencies. Running uv run would then add any missing dependencies for the root, and so on.

We repurpose --isolated (or introduce a new flag) to mean "don't use the project .venv, run the command in an isolated environment". So you can run commands in ephemeral environments per above.

Given the criteria above, this proposal is weak on the following points:

We don't enforce import or extra boundaries for packages, unless the user runs with --isolated.
There isn't really a way to sync the extra workspace to the root .venv. uv sync --all-extras is close, but if there are packages in the workspace that aren't depended on by the root package, those won't be included.

Other than that, though, I think it does a good job on the three points above. It's also easy to implement (it's close to what we do today) and IMO easy to change and extend in the future.
One additional behavior that I'd be open to:

uv run -p foo creates a new virtualenv in .venv, and we run in there.

This would at least enforce import boundaries for packages (but not extras).

uv run -p foo creates a new virtualenv in .venv, and we run in there.

I would avoid specifying the location, i.e., I think we'd just cache it as normal (like we do for tools) — we can determine if it should be user-facing separately. The important bit here is whether or not uv run -p foo is isolated by default or with opt in, right?
We probably need a separate flag from --isolated. Frankly I think --isolated makes the most sense when applied to environments, not settings but this is a tough spot since Ruff uses --isolated for config discovery. Riffing on some other options: --no-workspace, --no-project, --strict. I find it nice to focus on the idea that we're excluding various other dependencies rather than something like --fresh-venv which emphasizes how we go about excluding the other dependencies.
I'm feeling something like:

uv sync is required to create the user-facing persistent environment (.venv) for an editor experience or manual modifications of the environment. By default, this environment should contain most of the workspace (and their extras?).
uv run always uses a layered non-persistent environment (it can be cached). It could be empty if the persistent environment meets the requirements but prevents something like uv run -- pip install anyio having inconsistent behavior i.e. sometimes mutating the persistent environment.
An --isolated (or similar) flag is available to avoid layering on top of the persistent environment, enforce that manually managed packages aren't used, and that a package's dependencies are correctly declared.

Regarding:

If there are packages in the workspace that aren't depended on by the root package, those won't be included.

I think this is reasonable default behavior, though I'm not sure how we solve for it in the editor. We should have a flag, e.g., --all-workspace-members, to install everything regardless of the dependencies of the root package? but I imagine if a workspace member is intentionally excluded from the tree then it is intended to be incompatible or used separately? Do we allow package version incompatibilities in this case?

By default, this environment should contain most of the workspace (and their extras?).

I think we should leave this as-is today, honestly. The rest seems fine to me for now.

As of this proposal, we'd be using --isolated for ~three things:

Ignore any discovered settings.
Avoid operating in the context of a project for uv run.
Avoid using the persistent environment for uv run (this is in conflict with (2)).

For (2), we also have the no-managed = true flag in the TOML which achieves the same effect, I think.
I think it's probably right for --isolated to do the first two things, because it's meant to mean "ignore any files on-disk". It would be strange for it to do just the first but not the second, because then we'd use the dependencies for the discovered project but not the settings, that live in the same file? Though we could say that's fine and make them separate...
What are the ideal names here? Something like...

--no-config?
--no-project?
--isolated?

Candidly, I think the easiest thing for now (which also leaves the door open for future improvements) is just to keep what we have now, but add an --isolated or --standalone flag to run in an ephemeral environment, without the base environment.
Everything else can kind of be layered on later if we want (e.g., always running in a (maybe empty) ephemeral environment --that seems purely additive).
I personally don't want uv sync to be required, because it makes the environments feel too "hidden" for my liking.

Arguably we have further things to discuss here, maybe we should just drop it from the project? Or just remember to revisit later?

Yeah that's reasonable.

(Removed from the project.)


⚠ Bofrost.es has degraded performance

In ffa4cd5, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1617 ms

Resolved: Bofrost.es performance has improved in 8037b8b after 19 minutes.


Recipe for Doc-String in python

Is your feature request related to a problem? Please describe.
I'm always confused what doc-string style I should use and why.
Describe the solution you'd like
List up options for doc-string style with pros and cons.
Describe alternatives you've considered
Just pick the best one we think we should recommend.

@magencio,  @akirakakar - is this issue still relevant, and active or ok to close?

Sorry, we missed this issue. As it wasn't assigned to the Engineering Playbook Backlog project it didn't show up in our backlog. So, I'm not sure if this is still relevant. @akirakakar, may you confirm? Thank you and sorry for that.

Our general guidelines for code style for python is to use Pep8 and this is already documented in the playbook.


Duplicate message processing with SetPartitionsAssignedHandler()

Description
We are storing offsets in our DB to ensure exactly-once processing of data.
Storage of offsets and data from messages are in same transaction.
SetPartitionsAssignedHandler is used to retrieve the stored offsets from DB.
However the latest message is always duplicated when service is restarted.
Question
Should handler provided to SetPartitionsAssignedHandler return latest committed offset or offset of the first next message we want to receive?

you should specify the next message you want to receive (== committed offset if you were using kafka to track offsets)

"next message you want to receive" means offset of last received message + 1, right?

yes. the offset you return from the partitions assigned handler is expected to follow the same convention as what would be committed to kafka. see: https://github.com/confluentinc/confluent-kafka-dotnet/blob/master/src/Confluent.Kafka/IConsumer.cs#L357

Thanks for explanation. Works as expected :)


[Feature] Allow looping

Probably will have to restrict usage a little by forcing looping of entire bars.


The .labels in a Table View are no more a link to their lens

(more background/context and test files is available at https://github.com/simile-widgets/exhibit/issues/158)
Symptoms ;-)
In a Table View, you show a list of items. One column is the .label:

When displayed, the items with .label column (i.e. Rooms here) are no more links but static text.
Pre-diagnostic:
A quick test shows that using the API:
src="http://api.simile-widgets.org/exhibit/STABLE/exhibit-api.js", the link works as expected
src="http://api.simile-widgets.org/exhibit/HEAD/exhibit-api.js", there is no link but static text :-(.
Thanks for your help.

see also:
https://github.com/simile-widgets/exhibit/issues/158

This is resolved by explicitly defining the type as item in source files (json).
In Exhivit V2 this was implicit while in Exhibit V3 it is explicitely required of will be shown as text content.
So I am closing this issue.
Thanks All.


performance issue

Hello,
I have a big performance issue like https://github.com/SpriteLink/NIPAP/issues/1077
Tried to up the RAM, postgres buffers,  couldn't find anything working.
This performance problem happens when, as it is in our network:
split a xx.0.0.0/8 in 2000 /24 subnets
When i then "open" the scope in the webinterface, it is a unusable waittime.
this is the faulty query :
nipap=> SELECT pid, age(clock_timestamp(), query_start), usename, query
FROM pg_stat_activity
WHERE query != '' AND query NOT ILIKE '%pg_stat_activity%'
ORDER BY query_start desc;
pid  |       age       | usename  |                               query
-------+-----------------+----------+--------------------------------------------------------------------
21579 |                 |          |
21581 |                 | postgres |
21577 |                 |          |
21576 |                 |          |
21578 |                 |          |
21583 | 00:00:01.958938 | nipap    |                                                                   +
|                 |          |     SELECT                                                        +
|                 |          |         id,                                                       +
|                 |          |         vrf_id,                                                   +
|                 |          |         vrf_rt,                                                   +
|                 |          |         vrf_name,                                                 +
|                 |          |         family,                                                   +
|                 |          |         display,                                                  +
|                 |          |         match,                                                    +
|                 |          |         prefix,                                                   +
|                 |          |         prefix_length,                                            +
|                 |          |         display_prefix::text AS display_prefix,                   +
|                 |          |         description,                                              +
|                 |          |         comment,                                                  +
|                 |          |         inherited_tags,                                           +
|                 |          |         tags,                                                     +
|                 |          |         node,                                                     +
|                 |          |         pool_id,                                                  +
|                 |          |         pool_name,                                                +
|                 |          |         type,                                                     +
|                 |          |         status,                                                   +
|                 |          |         indent,                                                   +
|                 |          |         country,                                                  +
|                 |          |         order_id,                                                 +
|                 |          |         customer_id,                                              +
|                 |          |         external_key,                                             +
|                 |          |         authoritative_source,                                     +
|                 |          |         alarm_priority,                                           +
|                 |          |         monitor,                                                  +
|                 |          |         vlan,                                                     +
|                 |          |         added,                                                    +
|                 |          |         last_modified,                                            +
|                 |          |         children,                                                 +
|                 |          |         total_addresses,                                          +
|                 |          |         used_addresses,                                           +
|                 |          |         free_addresses,                                           +
|                 |          |         avps,                                                     +
|                 |          |         expires                                                   +
|                 |          |     FROM (                                                        +
|                 |          |         SELECT DISTINCT ON(vrf_rt_order(vrf.rt), p1.prefix) p1.id,+
|                 |          |             p1.prefix,                                            +
|                 |          |             p1.display_prefix,                                    +
|                 |          |             p1.description,                                       +
|                 |          |             p1.comment,                                           +
|                 |          |             COALESCE(p1.inherited_tags, '{}') AS inherited_tags,  +
|                 |          |             COALESCE(p1.tags, '{}') AS tags,                      +
|                 |          |             p1.node,                                              +
|                 |          |
(6 rows)
nipap=>
What should i do?

so let me resume: the already mentionned 1077
https://github.com/SpriteLink/NIPAP/issues/1095
https://github.com/SpriteLink/NIPAP/issues/1169
are all the same problem:
when there are too many subnets (or hosts) in a subnet, the query will take too much time.
This issue is already several years old.
As sexy as NIPAP is, it doesn't look to be scalable.


Creating Payload

[] Creating Payload using Pyinstaller...
[] Error In Creating Payload... Exiting..
2928 INFO: PyInstaller: 3.3.dev0
2928 INFO: Python: 2.7.12
2930 INFO: Platform: Windows-7-6.1.7601-SP1
2970 ERROR: We need PyCrypto >= 2.4 to use byte-code obufscation but we could not
2970 ERROR: find it. You can install it with pip by running:
2970 ERROR:   pip install PyCrypto
[*] Cleaning Up
I did a   pip install PyCrypto  no use

Hi,
What OS/distribution are you using?
Thanks

Im using Kali linux 64bit 2017.1

Okay,
Could you try the following please.
wine /root/.wine/drive_c/Python27/Scripts/pip.exe install pycrypto
Thanks

That fix the issue but I get this know
Traceback (most recent call last):
File "./WinPayloads.py", line 5, in
from lib.menu import *
File "/root/Winpayloads/lib/menu.py", line 4, in
from generatepayload import *
File "/root/Winpayloads/lib/generatepayload.py", line 3, in
from psexecspray import *
ImportError: No module named psexecspray
pip intall  psexecspray   Could not find a version that satisfies the requirement psexecspray (from versions: )
No matching distribution found for psexecspray

Hi,
Can you rerun the setup.sh with the -r flag
Thanks

Traceback (most recent call last):
File "./WinPayloads.py", line 42, in
getAndRunMainMenu()
File "/root/Winpayloads/lib/menu.py", line 61, in getAndRunMainMenu
mainMenu.runmenu()
File "/root/Winpayloads/lib/menu.py", line 115, in runmenu
result = extrawork(payloadchoice,payload)
File "/root/Winpayloads/lib/preparepayload.py", line 90, in httpsPayloadGeneration
GeneratePayload(ez2read_shellcode,payloadname,shellcode)
File "/root/Winpayloads/lib/generatepayload.py", line 60, in GeneratePayload
Filesave.write(do_Encryption(SHELLCODE.injectwindows % (ez2read_shellcode)))
File "/root/Winpayloads/lib/encrypt.py", line 24, in do_Encryption
encrypto = AES.new(key, AES.MODE_CTR, counter=lambda: counter)
File "/usr/local/lib/python2.7/dist-packages/Crypto/Cipher/AES.py", line 264, in new
return _create_cipher(sys.modules[name], key, mode, *args, **kwargs)
File "/usr/local/lib/python2.7/dist-packages/Crypto/Cipher/init.py", line 130, in _create_cipher
return modes[mode](factory, **kwargs)
File "/usr/local/lib/python2.7/dist-packages/Crypto/Cipher/_mode_ctr.py", line 319, in _create_ctr_cipher
_counter = dict(counter)
TypeError: 'function' object is not iterable

Hi,
Can you give me the output of ./setup.sh -r please
Thanks

[] Installing Dependencies
Hit:3 http://deb.bitmask.net/debian testing InRelease
Hit:1 http://archive-7.kali.org/kali kali-rolling InRelease
Hit:2 http://archive-7.kali.org/kali kali-bleeding-edge InRelease
Reading package lists... Done
Reading package lists... Done
Building dependency tree
Reading state information... Done
git is already the newest version (1:2.11.0-3).
python is already the newest version (2.7.13-2).
python-crypto is already the newest version (2.6.1-7).
python-pefile is already the newest version (2016.3.28-4).
python-pip is already the newest version (9.0.1-2).
python2.7 is already the newest version (2.7.13-2).
unzip is already the newest version (6.0-21).
wget is already the newest version (1.18-5).
winbind is already the newest version (2:4.5.8+dfsg-2).
0 upgraded, 0 newly installed, 0 to remove and 17 not upgraded.
[] Installing Wine
Reading package lists... Done
Building dependency tree
Reading state information... Done
wine32:i386 is already the newest version (1.8.7-2).
0 upgraded, 0 newly installed, 0 to remove and 17 not upgraded.
Reading package lists... Done
Building dependency tree
Reading state information... Done
wine is already the newest version (1.8.7-2).
0 upgraded, 0 newly installed, 0 to remove and 17 not upgraded.
[] Installing Python Requirements
Requirement already satisfied: blessings in /usr/local/lib/python3.5/dist-packages
Requirement already satisfied: pyasn1 in /usr/local/lib/python3.5/dist-packages
[] Installing Pyinstaller
[] Installed Already, Skipping!
[] Downloading Python27, Pywin32 and Pycrypto For Wine
[] Installed Already, Skipping!
[] Installing impacket from Git
[] Installed Already, Skipping!
[] Grabbing Wine Modules
Requirement already satisfied (use --upgrade to upgrade): pefile in c:\python27\lib\site-packages
Requirement already satisfied (use --upgrade to upgrade): future in c:\python27\lib\site-packages (from pefile)
You are using pip version 8.1.1, however version 9.0.1 is available.
You should consider upgrading via the 'python -m pip install --upgrade pip' command.
[] Done
[] Grabbing Modules
% Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
Dload  Upload   Total   Spent    Left  Speed
100  4698  100  4698    0     0  10828      0 --:--:-- --:--:-- --:--:-- 10849
[] Done
[] Grabbing Certs
Generating RSA private key, 2048 bit long modulus
.....+++
..+++
e is 65537 (0x010001)
writing RSA key
Signature ok
subject=C = US, ST = Denial, L = Springfield, O = Dis, CN = www.example.com
Getting Private key
[] Done
[] Cleaning Up
[*] Done

Hi,
It looks like you didn't run the setup with the -r flag.
Could you try
Thanks

root@vultr:~/Winpayloads# ./WinPayloads.py
Traceback (most recent call last):
File "./WinPayloads.py", line 2, in
from lib.main import *
File "/root/Winpayloads/lib/main.py", line 8, in
import blessed
ImportError: No module named blessed
root@vultr:~/Winpayloads#

./WinPayloads.py
Traceback (most recent call last):
File "./WinPayloads.py", line 2, in
from lib.main import *
File "/root/Winpayloads/lib/main.py", line 8, in
import blessed
ImportError: No module named blessed

Did you run the setup?
Try pip install blessed


url encode hub url (#5099)

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


feat: configuration for traces

Component
Forge, Cast
Describe the feature you would like
forge test, forge script, and cast run all produce traces. Depending on your use case, there are various display modes that may be the most helpful:

Hiding addresses if you have a label vs. showing label + addr vs. always showing addr (ref https://github.com/foundry-rs/foundry/issues/3381)
Truncated address like 0x123...def vs full addresses (this has come up in an issue before, can't find it now though)
Overall tx state diffs vs. no state diffs (ref https://github.com/foundry-rs/foundry/issues/2846)
Call-level state diffs within the trace (arguably would get cluttered, but still is useful)
Showing only logs instead of a full trace
Showing vs. hiding function parameter names
Showing vs. hiding decoded SSTOREs and SLOADs in a call, similar to https://tx.eth.samczsun.com/#txhash=0x3443cd8f0c722fa9d83e12033f29eb590b177804ae625f2072625dfb79b329c2
Hide/modify certain calls in the traces, for example file/json reading/writing large files can quickly clutter logs. Perhaps a flag that takes an array of VM function names/signatures and replaces them with some other value

I think we should support these various options in two ways:

A new [trace] section in the config file (more useful for forge)
CLI flags (more useful for cast)

Additional context
No response

Linking also this as relevant: https://github.com/foundry-rs/foundry/issues/3599
I will probably PR a quick fix for #3599, as it's really painful.  But, generally, really like this "proper" solution to this family of use cases.


Unable to pull docker image

When I run docker pull ghcr.io/els-rd/transformer-deploy:0.5.0, the result is:
Error response from daemon: manifest unknown.
If I change the 0.5.0 to 0.4.0 it works. Does the 0.5.0 exist?

Hi, not yet. We are finishing the implementation of T5 in convert tool. You can build it yourself however through the Makefile.


VS Code 1.60.0 via Submodule

While #4010 resolves some incompatibilities with 1.60.0, it's still in review and needs additional testing. This PR updates lib/vscode to use a submodule pointing to our VS Code fork. Once this is merged, any remaining fork clean up branches will be ported over to the submodule.
Fixes #3917
Notable changes from upstream

The log service now defers initialization.
Several terminal channels were added.
Serval type definitions were adjusted.

How to review this PR
This is a somewhat unusual PR since we don’t yet have a diff to start with, however, I’ve made a branch on our fork with the previous changes form lib/vscode. This allows you compare all the changes from upstream, as well as the adjustments to our code to fix them in 1.60.0
https://github.com/cdr/vscode/compare/1.57.1-initial...cdr:1.60.0-code-server-patch

https://github.com/cdr/code-server/pull/4122/checks?check_run_id=3550356321#step:6:2125

It looks like the postinstall script is failing? Is that because it runs yarn inside lib/vscode but now that that's a submodule, we need to modify it? just a guess

I'm looking at the list of commits and there are 3,600 😮 I'm thinking the only reasonable way to review this is to check it out locally, run it and make sure everything works

@jsjoeio,

I'm looking at the list of commits and there are 3,600 😮 I'm thinking the only reasonable way to review this is to check it out locally, run it and make sure everything works

This is unfortunately the case until our own tests can run along side upstream’s to ensure we didn’t cause a regression in their code.

It looks like the postinstall script is failing? Is that because it runs yarn inside lib/vscode but now that that's a submodule, we need to modify it? just a guess

Bingo 😃

Dang it! It failed again.


Bug with MD052 and Hugo Shortcodes

Hi Peoples
I think I've found a bug in the way rule MD052 is processed. In my markdown files I have the following snippet:
Security issues found, if any, will be triaged following [the standard process][4].

With the references at the end of the markdown being:
[1]: https://docs.google.com/document/d/15eNKGA3zyZazsJMldqTBFbYMnVUSQSpU14lo22JMZQY/edit
[2]: https://gitlab.com/gitlab-com/gl-security/appsec/appsec-reviews/issues
[3]: {{< ref "./_index.md#stable-counterparts" >}}
[4]: {{< ref "/handbook/security#issue-triage" >}}

Items 4 and 3 are Hugo shortcodes which produce valid URLs but I think because of the way markdownlint processes this section it throws an MD052 error. My exact error is:
application-security/appsec-reviews.md:29:58 MD052/reference-links-images Reference links and images should use a label that is defined [Missing link or image reference definition: "4"] [Context: "[the standard process][4]"]

Would it be possible to confirm the bug and advise if you might fix it so I can advise my handbook community and make a decision on if I should disable the rule in my project (not something I want to do).

Cool... Thank you for taking a look.  I'd throw out a feature request to add shortcode support in the future.
I'll disable the rule in our config as I think this going to come up a lot for our Handbook.  I'll close the issue.


I wish I could send the email directly

I wish I could send the email directly

https://www.cnblogs.com/smartloli/p/12110570.html


food

This ticket was created automatically by our robot from our contribution page.

Seems to be an error: a description is missing.


add ssl support for send email

Some mail service providers use ssl connection to send/receive emails.
Had test with tencent's enterprise mail success: smtp.exmail.qq.com:465

@xionglun What error does this PR try to fix?

@reasonerjt

Currently, code didn't support SSL connection!
Mail providers such as QQ Exmail don't support non-ssl smtp email send.
This PR try to add SSL support for emails.

https://golang.org/src/net/smtp/smtp.go#L300
godoc says smtp pkg supports TLS by default, we'll do more testing before make decision on this PR.
Could you let us know what error did you see and you have to make the change to fix it?

Golang's implementation  does not use TLS by default, it will upgrade an existing insecure connection to a secure connection if server support.
And you can read SendMail's comment

// SendMail connects to the server at addr, switches to TLS if
// possible, authenticates with the optional mechanism a if possible,
// and then sends an email from address from, to addresses to, with
// message msg.

I think the problem is that:
Some mail providers don't support insecure connection at all.
So you can't start off as plaintext, then upgrade the connection to an SSL/TLS encrypted one.
Additional Doc:
SSL vs TLS vs STARTTLS

@xionglun Thanks I see your point.  Seems smtp package should provide more api...
But as long as this fixes your problem, could you please update the default value of email_ssl to false and add more explanation of this attribute in the .md file?

@reasonerjt  I have squashed my commit, and set email_ssl to false by default.


Made the website HTTPS-compatible

Updated .gitignore to include "bower_components";
Made the website HTTPS-compatible by using HTTPS URLs for resources and links.

Looks good :sparkles:


Add email verification on sign up

User Story: As a user I want get a confirmation email when I register with papercups on the signup page.

With respect to this would we want the email to contain a kind of password or just a link which directly gets us into the page.

@sladyn98 would your team be able to help contribute to this one?

@cheeseblubber Yeah sure

Verification email would clean up our email database so we don't have a bunch of fake emails

Since we use pow this will be relatively easy task, I can take on

@flmel feel free to use whatever message you want for now :) it should be pretty easy to change it later if we want to
to start off, something like this should be fine:
Subject:

Please verify your email to complete your setup with Papercups

Message:

Please click the link below to verify your email:
[link with email verification token here]
Thank you!
Papercups Team

Is this still open?
Was poking around at this and saw a place where it could be done at.
When a user registers the "enqueue_welcome_email" function is called in the "create" function on the "registration_controller" to use the "SendWelcomeEmail" worker.
Could the process be done in that so when a welcome email is sent it also asks for email verification?

@LeviLong01 Thanks for your interest, I guess @cheeseblubber would be able to help you here

@LeviLong01 I would keep it separate right now. I m not sure if that function is active at the moment but you can follow a similar pattern to the welcome email


support for foot terminal (https://codeberg.org/dnkl/foot)

Hi,
I've just added support for the foot terminal (https://codeberg.org/dnkl/foot). Would be great if this could be merged.
Thanks!
pfuender

Great Thank you!!!
I have to update the README with the terminals on which Gogh works, I never thought that this code would work on so many terminals, and I still need to take advantage of the JSON :smile: , thank you