Auto-branch when you don't have commit permissions on current branch

I saw some issues talking about auto-forking when you can't push a branch, but this is about not being able to commit to the current branch.

I'd like to work on main.  If I try to commit, it would be nice for it to detect that I cannot push this due to permissions and provide a way to quickly branch, commit, PR.

We were talking about this exact concept at lunch and I came here to file this issue. The flow I want:

Have main checked out
Type code
Open scm view, write a commit message
Click button that is like "commit to PR"
A branch is created, the commit is written to it, and a PR is created with the commit message as title

We have also been talking about this. The flow I heard was:

Setting is set in folder that indicates that the main branch shouldn't be committed to.
Have main checked out
Type code
Open scm view, write a commit message
Scm input box shows a warning since we can do that now.
Click button that is like "commit to new branch"
A branch is created, the commit is written to it
One more step, you must still manually click the "create pr" button. Discussion was that maybe just creating the PR was too magic.

Usure yet if this should live in the built-in git extension or in GHPRI though.
@lszomoru do you have any strong opinions here?

Thank you all for the feedback. @alexr00, let's get together and discuss the best way to move this forward.

One more step, you must still manually click the "create pr" button. Discussion was that maybe just creating the PR was too magic.

I'd love a setting for this. Maybe not publishing the PR but opening the Create PR view. Some cool smartness would be opening the PR view when my commit message includes "Fixes #xyz" but not otherwise

https://github.com/microsoft/vscode/issues/151589 tracks the integration with the built-in git extension that will cover this.


[Lua 5.1] Added old version of lua

Describe the pull request
So I don't really know if this is the correct way of adding a older version of a already newer library. But i thought i will give it a try.

What does your PR fix? Fixes #7713

Which triplets are supported/not supported? Have you updated the CI baseline? yes

Does your PR follow the maintainer guide?yes

pinging @vadi2 as he requested this and might have time to test this as soon as it is ready to use.

waiting for the ci run and then pushing the commits to go back to version 5.4.3

Nice, how would I try this in the project?

Nice, how would I try this in the project?

currently you could clone the https://github.com/mathisloge/vcpkg with the branch lua 5.1.
But after i push the commits to go back to 5.4.3 you need to follow https://github.com/microsoft/vcpkg/blob/master/docs/users/versioning.md to freeze the version to 5.1

Per policy we don't allow downgrading of libraries. The correct way to accomplish this would be to create your own custom Git registry and push the needed versions to that registry.
You can read our registries blog post that includes an in-depth tutorial. If you need more help setting this up for your project/team please feel free to open a new discussion or contact us by email or Slack/Discord.

So I thought if I'm pushing it back to 5.4.3 the version feature should allow projects to consume the 5.1 version. But since lua started (in vcpkg) with version 5.4.3 only version beginning with this version are supported in the future?
All older versions have to live in a slcu) custom registry?
Thanks for clarifying.

@mathisloge
That's correct. Our current stance is to have missing versions be provided by custom registries; we hope that a federated environment of high-quality custom registries is born at some point in time that can address the shortcomings of the main registry. We also may change our stance on this in the future.

@vadi2 Have created a custom registry as @vicroms said with lua versions 5.1, 5.2 and 5.3 since 5.4 and onward will be supported from vcpkg main repo
https://github.com/mathisloge/vcpkg-registry

@vicroms  should maybe also close #7713


optimize/functions: fix ExtendedRosenbrock for BFGS test

Please take a look.
Updates #1218.

From what I can see, the higher precision allows results that are calculated in the gradient to not underflow to zero. This means that when the step is taken, because the gradients are so small, the step does actually underflow, thus leaving a non-zero gradient and a zero progression. This is one of the manifestations, there are others that I'm not entirely clear on; I added print statements into the tail of the function being changed here and at places in LinesearchMethod.Iterate and compared the amd64 and arm64 runs side by side. There are catastrophic deviations that happen when either the gradients are very small (<1e-30) or when elements of the gradient are significantly different in magnitude (>1e16).
My intention is to leave #1218 open and only check off the fixes that we're happy with (this is why I'm tagging them with commits, so we can easily go back to the fixes to see if we are). When we're happy with all of them, we can close it.

Yes, BrownBadlyScaled function is indeed badly scaled and is difficult to optimize it with a method that doesn't take it into account. So basically even with this "fix" it works by chance and I doubt the utility of the test case. It doesn't verify that the implementation is neither correct nor numerically robust.
Interestingly, if I comment out the check that causes the failure (in LinesearchMethod.initNextLinesearch and relax the gradient tolerance to 1e-9, the test passes. This happens because even if the method does not advance from the current location, the history of the method is updated by incorporating the current gradient. At every retry the generated direction points more in the direction of the gradient so eventually the current location may change and move towards a local minimum. I commented on this already in the past but I'm still unsure if we should do anything about it. Not all methods have this "autocorrecting" ability, gradient descent does not, for example. We could have a retry mechanism and give up only after a certain number of retries but that increases complexity slightly and adds another magic parameter (number of retries). In this particular case one retry is enough to move the location. The current way is simple but we sometimes fail to find the minimum. Seeing that the alternative is to semi-randomly prevent fused multiply-add operations, I wouldn't be opposed to the retry mechanism.

Yes, BrownBadlyScaled function is indeed badly scaled ...
Oh, wrong function but ExtendedRosenbrock is not pretty either.

I tried to implement the retries but the logic is not so simple there and it would be an ugly hack too.
LGTM


MountTmpfsAtTemp: Option to mount tmp on ephemeral mount

Is your feature request related to a problem? Please describe.
We have some jobs which use a lot of tmp -- too much for tmpfs in memory.  So, we have set MountTmpfsAtTemp=false.    This uses keeps /tmp on the root device (EBS).
But, we are also using instance types with ephemeral NVMe disks (EnableInstanceStorage=true).
Describe the solution you'd like
If EnableInstanceStorage=true and MountTmpfsAtTemp=false, it would be great to mount tmp on the /mnt/ephemeral mount.  Or another configuration option to opt specifically into this behavior.
Additional context
It looks like most of this functionality is in https://github.com/buildkite/elastic-ci-stack-for-aws/blob/main/packer/linux/conf/bin/bk-mount-instance-storage.sh#L27-L42 -- might need somre re-ordering with the script, but should be pretty feasible?

Hey @pquerna! Thanks for raising this – we can see the value in what you're suggesting. Would you be up for submitting a PR to make this change?
One option that could be explored is symlinking /tmp to /mnt/ephemeral/tmp or similar. It'll need to be behind a parameter as well – no good names come to mind, so feel free to suggest one!


Question: OpenAPI tools

Is there a list of tools that support OpenAPI/Swagger?
I saw this page to be very appealing: http://raml.org/projects/projects
Can we build a website like this?

Ok, I've found this: http://swagger.io/tools/
But would swagger.io be renamed to OpenAPI.io?

The official tooling list is now available at https://tools.openapis.org


Objects of type LogTargetDensity are not callable

Hi, I’m trying to execute the following example for AdvancedHMC:
using AdvancedHMC, ForwardDiff
using LogDensityProblems
using LinearAlgebra

# Define the target distribution using the `LogDensityProblem` interface
struct LogTargetDensity
    dim::Int
end
LogDensityProblems.logdensity(p::LogTargetDensity, θ) = -sum(abs2, θ) / 2  # standard multivariate normal
LogDensityProblems.dimension(p::LogTargetDensity) = p.dim
LogDensityProblems.capabilities(::Type{LogTargetDensity}) = LogDensityProblems.LogDensityOrder{0}()

# Choose parameter dimensionality and initial parameter value
D = 10; initial_θ = rand(D)
ℓπ = LogTargetDensity(D)

# Set the number of samples to draw and warmup iterations
n_samples, n_adapts = 2_000, 1_000

# Define a Hamiltonian system
metric = DiagEuclideanMetric(D)
hamiltonian = Hamiltonian(metric, ℓπ, ForwardDiff)

# Define a leapfrog solver, with initial step size chosen heuristically
initial_ϵ = find_good_stepsize(hamiltonian, initial_θ)
integrator = Leapfrog(initial_ϵ)

# Define an HMC sampler, with the following components
#   - multinomial sampling scheme,
#   - generalised No-U-Turn criteria, and
#   - windowed adaption for step-size and diagonal mass matrix
proposal = NUTS{MultinomialTS, GeneralisedNoUTurn}(integrator)
adaptor = StanHMCAdaptor(MassMatrixAdaptor(metric), StepSizeAdaptor(0.8, integrator))

# Run the sampler to draw samples from the specified Gaussian, where
#   - `samples` will store the samples
#   - `stats` will store diagnostic statistics for each sample
samples, stats = sample(hamiltonian, proposal, initial_θ, n_samples, adaptor, n_adapts; progress=true)

However, ForwardDiff does not seem equipped to handle the LogTargetDensity type.  Thanks.

What version are you using @arnold-pdev ?


ME documentation update

Awesome!

Where do you think discussion of the I/O CCE and UCE should live? Probably in the microarchitecture guide, with a reference to them here?

Yes, sounds good.
On Fri, Jun 26, 2020, 6:10 PM Dan Petrisko<EMAIL_ADDRESS>wrote:

Where do you think discussion of the I/O CCE and UCE should live? Probably
in the microarchitecture guide, with a reference to them here?
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/black-parrot/black-parrot/pull/552#issuecomment-650467866,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABHX6DXXGVKYTLVTHBHKDATRYVBJRANCNFSM4OJVUB3Q
.


NNBD introduced breaking change to Isolate.spawn functions

Projects that executed fine have been broken with the introduction of NNBD without any changes.  This appears to happen because Isolate.spawnUri doesn't inherit the settings from the calling context so a non-NNBD context spawning an isolate will attempt to make a NNBD isolate unless the called code has a language version annotation.
Examples:

https://github.com/flutter/flutter/issues/70355 (this issue could be addressed by just adding a language annotation to the executing code)
https://cirrus-ci.com/task/5943556349100032 (this one had to be fixed by upgrading the test package)

Expected result:
I expect Isolate.spawn functions to default the spawned isolate to the same settings as the spawning isolate unless otherwise specified.
Dart version:
2.12.0 (build 2.12.0-31.0.dev)

Related: https://github.com/dart-lang/sdk/issues/40632, https://github.com/dart-lang/sdk/issues/41207.
@jakemac53 @natebosch @leafpetersen @lrhn

If I read this correctly, it's Isolate.spawnUri which opts its spawned isolate into sound null safety based on the entry-point library.
This is dangerous if the library may depend on non-null-safe libraries, and there is no way to override the behavior.
(Or rather, one will have to create a non-null-safe entry point which forwards to the real entry-point library, and use that until all dependencies have been migrated).
It's only a problem for out-of-order migration.

It's only a problem for out-of-order migration.

The problem we are hitting is that it's a problem for users who upgrade their SDK but don't care about null safety yet.
The reasoning to default to opt-in if the VM doesn't know the language version is the same as the reasoning to default the overall VM to opt-in if you run a script that isn't in a package - we want the default to be null safety because it's the best default in the long term. In the short term during the SDK switch it does cause some pain.

If I read this correctly, it's Isolate.spawnUri which opts its spawned isolate into sound null safety based on the entry-point library.

With the Pigeon issue mentioned in the description, the spawning context was non-NNBD but it was attempting to create a NNBD isolate.  The code worked fine until there was an upgrade of Dart and it stopped working.  I had to fix it by adding a language annotation to the spawned code.
Something like this this could would be broken with a Dart upgrade (see pigeon for a real example):
void main() {
  final String code = """
void main(List<String> args, SendPort sendPort) async {
  print('hello');
}
""";

  String path = tempFilePath();
  File(path).writeAsString(code);
  Isolate.spawnUri(Uri.file(path), null, null);
}

Yes this is a breaking change but it is exactly the same breaking change that is being made for all dart code.
If you have some code which is not a part of a package (including raw code in a string), it will be opted in to null safety. That is the default language version.
It is imo correct for both Isolate.spawnUri(<uri>) and dart <uri> to have the same behavior, and they do today, which is what you are seeing.
We should likely call this out explicitly in the breaking change announcements for NNBD though, if it isn't already.

We should likely call this out explicitly in the breaking change announcements for NNBD though, if it isn't already.

@leafpetersen have we actually sent a general breaking change notification for null safety overall? With it going to beta, and dart <file name> getting null safety by-default, that might be a good idea.

@leafpetersen have we actually sent a general breaking change notification for null safety overall?

No.  I can do so.

When you first announced null safety, you made a big point of saying "Null safety is backwards compatible". This is a clear backwards incompatibility, and one that's already affecting real users—Dart Sass's CI has been broken for six days because of it, and we have no recourse but to wait for an upstream fix. And that's not counting the numerous changes we've had to make to a number of other packages we use to work around the underlying VM-default issue.
I understand the desire to move everyone onto null safety, and to have the VM default to the language version that's ultimately going to be universal in the future. But you can't just go about making breaking changes left and right, especially when you've publicly promised not to do so. Just because the new behavior is better doesn't negate the pain, frustration, and lost productivity that those breakages cause.
In Sass, when we need to make a breaking change, we follow a process for doing so that's designed to minimize user pain. First, we mark the old behavior as deprecated, and produce some kind of message or warning when it happens. (This is also how, for example, what Node.js did when they transitioned unhandled promises from being silently ignored to crashing the program.) We allow that deprecation to exist in the ecosystem for a substantial length of time—usually a year or more, but sometimes less if the breaking change is urgently necessary to support a CSS feature—and only once we're confident everyone has had a chance to migrate away from the old behavior do we add the new behavior.
I would suggest a similar pattern here. In Dart 2.12, continue to treat unmarked scripts as being the lowest possible language version, but if they have null-unsafe dependencies produce a warning message that indicates that their version should be explicitly marked. Then in Dart 2.15 or whatever, once null safety is more or less universal, switch the default with way lower risk of breakage.

@nex3 I agree Dart should have avoided this breaking change.  Seems like they have enough contextual information to move people to NNBD and not break people in this case, but in the meantime I was able to work around the issues by:

Adding language specifications to the top of my scripts
Upgrading the test package

Hopefully you can do that, too, to unblock your CI.

@leafpetersen I'm assigning this to you, please assign a priority, Thx!

Any updates on this? Since 2.12 was released to stable, this is now a breaking change. Dart Sass's CI is still broken, which is forcing us to pin to 2.11.

Could we change Isolate.spawnUri to always make the new isolate non-sound when the spawning isolate is non-sound?
That would mean that you cannot spawn a sound isolate ever, if your starting isolate is unsound, but when your entire program is sound, you will get sound isolates too.

Could we change Isolate.spawnUri to always make the new isolate non-sound when the spawning isolate is non-sound?
That would mean that you cannot spawn a sound isolate ever, if your starting isolate is unsound, but when your entire program is sound, you will get sound isolates too.

This would mean you couldn't run sound tests at all until the test runner is migrated, etc. At this point it is nearly released as a sound mode app but flutter users won't get that until the next flutter release due to package pinning, so no flutter tests would be able to run in sound mode.
It would also introduce a weird divergence in behavior between isolates and normal apps which I don't think is justified, and isn't the desired behavior either.

This isn't the first time we've run into the broad category of issues where "sometimes you want an isolate to inherit X from its parent and sometimes you want to control X explicitly". Maybe there's a need for an opaque Map<Symbol, Object> flags parameter that can be used to trigger migration-compatibility behavior in a way that won't introduce API bloat once a migration is completed? For example, Isolate.spawnUri() could default to the same soundness as its parent, but test could pass in flags: {#forceSoundNullSafety: true} when it wants to ensure tests run in null-safe mode. Then when null safety is no longer optional, dart:isolate could just ignore #forceSoundNullSafety going forward (or similar for any future migration).


Initial commit to test pull requests

Just added a comment to pet_proc_bids.sh to test the pull request cycle.

Thanks, Gaylord! Approving your test request.


Add X-Remote-Extra- headers prefix configuration

Fixes https://github.com/kcp-dev/helm-charts/issues/103.
kcp-front-proxy sets the X-Remote- headers after validating a ServiceAccount token, but the kcp server wasn't accepting that header. This fixes that oversight, so now all extra auth information parsed by the front-proxy should be accepted by the kcp server.
Some of the information lost in the process was the clusterName that the ServiceAccount is coming from, which resulted in having to explicitly grant them access via RBAC if the ServiceAccount token was used against the front-proxy (but not against the server directly).

/approve


Question: How does the lazy start work?

The API docs claim that " ParallelFuture starts lazily". However, the implementation of par just seems to call async_std::task::spawn:
https://github.com/yoshuawuyts/parallel-future/blob/fe65333ff4910d84b1e85c9a5e6b5180013c6a1f/src/lib.rs#L126
This task::spawn function doesn't seem to be lazy (or at least it doesn't mention it in its docs).
So I'm a bit confused, how does this work?

Oh hey! Yeah good catch; I messed that up when I rewrote the API surface two days ago.
It's no excuse, but I'm currently traveling and definitely didn't pay enough attention. With some luck I'll have a few spare mins later today to fix it. Ty for catching this!

Thanks! There's no hurry, I was just curious how you implemented this after reading your latest blog post.


Fix 11619 alan

Just a logic update (3rd commit) based on Valentin's PR (1st and 2nd commits): https://github.com/dmwm/WMCore/pull/11884
In short, for each active workflow with pileup, perform the following:

Find all pileupconf.json files inside the workflow sandbox (not the tarball)
For each pileup JSON found:
2.a. load its content
2.b. figure out the dataset name
2.c. iterate over the pileup documents from MSPileup and find the correct pileup document
2.d. compare the block and their location between the JSON and MSPileup. If there are no changes, jump to step 2.
2.e. if there are changes, update the json content with addition/removal of blocks and update of their locations
2.f. finally, update the tarball with that content against that specific pileupconf.json file (writePileupJson() method)
2.g. go back to step 2

The only difference between this and what we previously discussed is that here I start iterating over the pileupconf.json first, to avoid multiple load/dump from the filesystem.
NOTE though that the performance is very sub-optimal, as we might be untarring + tarring the same spec N times, where N is the number of pileupconf.json files in the tarball (which can either belong to the same dataset or to different ones).

@vkuznet Valentin, I guess this is no longer needed. However, please let me know if we need to reopen this for any reason. Closing this out.


fix typo in README.md

Coverage remained the same at 91.785% when pulling 446d4cae959ac1f96b4cc6f545e5500fd64cee19 on svsool:fix-typo into 021d57af3b8d44b757f7a940fcb14f3055c4b63e on sokil:master.

Coverage remained the same at 91.785% when pulling 446d4cae959ac1f96b4cc6f545e5500fd64cee19 on svsool:fix-typo into 021d57af3b8d44b757f7a940fcb14f3055c4b63e on sokil:master.


Change version suffix separator from '-' to '~'.

Changing the suffix separator from '-' to '~' you will obtain a correct versions comparison.
Currently '2.0.0-dev' > '2.0.0'.
With the '~' suffix separator you obtains '2.0.0~dev' < '2.0.0'.
Tested on debian, ubuntu and freebsd.

Is it me or it looks like a hack ? I guess applications that need it can parse a version number, can't they ?

@hardening ~ seems to be the common way to add a suffix to a version and have the suffixed version less then the not-suffixed. If I'm packaging your packaging (like it is) and you are releasing a not-suffixed version and I packaged it my system will not update it.

@hardening I confirm the same behavior on FreeBSD and Fedora, and moving to ~ it won't change your life I think ;-) , on the contrary in the packaging world the - as suffix is a disaster, except if you really mean that 2.0.0-dev is less updated than 2.0.0
2.0.0-dev < 2.0.0 < 2.0.0~dev

My 2¢

2.0.0-dev < 2.0.0 < 2.0.0~dev

well... the other way around, sorry
2.0.0-dev > 2.0.0 > 2.0.0~dev

Ok, sorry I read too fast the first statement. That's just a matter of packaging names, so I guess that if @bmiklautz is ok we (he) should merge that.

BTW @freerdp-bot  can you test that too ?

freerdp-bot is lazy ...

Hi all, RedHat/Fedora people told me that '~' in the release name is a problem, I retire the PR, sorry for the waste of time.

@nastasi the -dev doesn't have anything todo with the packaging itself. It is rather a "hint" for users and developers. When packaging you can set the package name/version to whatever you want.


Why / Balance
Admins are discussing to add a new rule to prevent head revs being held on to by other crew that prolong rounds and stall them out by the head revs not being executed.
This would mechanically prevent those issues and prevent another rule from being added.
Technical details
On mind shielding for a head rev, the entity takes 300 genetic damage and looses all their blood out to the floor in a simulated hemorrhage.
Media
https://github.com/space-wizards/space-station-14/assets/47093363/3c64e8a2-8410-43f8-afdf-ccd28e2b1ba7

[X] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Breaking changes
None
Changelog
:cl: Repo

tweak: Head revs now die on mind shielding.

my main concern is that this is an incredibly quick way to kill someone that is not communicated very well to the player. Instantly killing the player after a 3(?) second doafter is really extreme, especially for an antag. I could very much see these being used as a way to try and quick-kill revs. Stunning someone with a baton and quickly injecting while they're down could be seriously overpowered if it just straight up kills headrevs.

my main concern is that this is an incredibly quick way to kill someone that is not communicated very well to the player. Instantly killing the player after a 3(?) second doafter is really extreme, especially for an antag. I could very much see these being used as a way to try and quick-kill revs. Stunning someone with a baton and quickly injecting while they're down could be seriously overpowered if it just straight up kills headrevs.

Agreed, straight up round ending headrevs after a 5  second do-after is absurd. The only way you could realistically round end someone that fast normally is with a christmas gib stick and eating the brain right after :skull:

my main concern is that this is an incredibly quick way to kill someone that is not communicated very well to the player. Instantly killing the player after a 3(?) second doafter is really extreme, especially for an antag.

This was just my first thought to have a mechanical implementation to what most commonly happens during normal gameplay on rev rounds. So that additional rules are not required.
I'm keen for any other way this might solve the underlying problem, that being round stalling due to headrev protesting or sec RP'ing them as a prisoner to the determent of the rest of the players or a rule that just adds admin overhead to the prior.
Currently 1 of 2 things happen when a head rev is mindshielded,

Most commonly, the mind shield breaks, everyone sees and then whatever nearby player is around, all go to town and gib the head rev, If it is the last rev the round continues on to the end condition and shuttle is called.
The Head rev is taken away by sec/captor, or the head rev demands a trial etc, essentially stalling and extending the round at a stage where a large portion of the players are ghosts already. Generally resulting in admin intervention to prevent stalling.

This would essentially do what happens already but prevent the stalling aspects of once a head rev is mindshielded.

I could very much see these being used as a way to try and quick-kill revs. Stunning someone with a baton and quickly injecting while they're down could be seriously overpowered if it just straight up kills headrevs.

With regards to the power gaming example, people can do this already to make a determination of the head rev, they would just do the killing gibing in a subsequent action after seeing the mindshield broken text. If people were just randomly mindshielding it sounds more like a powergaming issue if people are running around beating random crew and doing a test mindshield.

@EmoGarbage404 Thank you for the review, I appreciate it. I've made all the requested changes, although it seems like the vibe is not to go forward with this?

my main concern is that this is an incredibly quick way to kill someone that is not communicated very well to the player.

Just touching on this one too, the alternative feels much worse, there is not clear in game que that the head rev should be killed and then you have to go consult the wiki/rules/space law then go and find in some huge table for a particular action/problem that references another rule that says you should kill them without trial.
https://wiki.spacestation14.io/wiki/Space_Law#Refusal_of_Mental_Shielding
Which feels like its even less communicated in game and a larger headache.

This also just promotes NRP and doesn't even allow for you to roleplay out execution/permaing of rev heads

This also just promotes NRP and doesn't even allow for you to roleplay out execution/permaing of rev heads

This is true a little, but at the benefit of the game being more self sufficient not requiring admin intervention, yet another rule added/managed, or the game mode breaking down because someone wants to make half the server of ghosts wait for a trial.
The situation you speak of is exactly what I'm trying to prevent as when you get to late game revs it is inevitable you have at least several ghost and the round mode objective is that the revs or the heads die, not put them in jail or give them their day in court.
The space law/rule has already been updated to this for higher RP environments so the intent from the rules and game mode is that you should kill them without any long winded RP anyway. This just mechanically enforces this so some admin doesn't get saying this round is stalled because Urist mchands is stalling the round by putting the rev in perma instead of killing them and not following the execution rule/law.
This follows similar mechanical solutions in team antags, Nukies essentially have the same thing with the acidifier and the shuttle auto call on all dead for their mode and zombies have stall prevention too with over X% zombie pop shuttle is called.

The concensus was that instant round removal of head revs isn't a good way of solving these sort of problems


LSA signature not found

Describe the bug
LSA signature not found. Use volatility3-pypykatz plugin for volatility, but as i see error from pypykatz code. The same error if use pypykatz against exctracted lsass.dmp. Dump is correct, at least i can get hashdump and process handles from dump, using another volatility plugins
Volatility Version:  develop, today (10.05.2024)
Operating System:  Kali Linux
Python Version:  3.11.7
Suspected Operating System:  dump from Windows Server 2016 (10.0.17763) (Domain Controller and CA)
UPD: It is Windows Server 2019
Command:  python3 vol.py -f ~/testy-tms/silver.raw -l t1  windows.volu_pypykatz.pypykatz
Steps to reproduce the behavior:

Use command 'python3 vol.py -f ~/testy-tms/silver.raw -l t1  windows.volu_pypykatz.pypykatz'
See error
Traceback (most recent call last):
File "/home/andy/2/volatility3/vol.py", line 7, in
import volatility3.cli
File "/home/andy/2/volatility3/volatility3/cli/init.py", line 29, in
from volatility3.cli import text_renderer, volargparse
File "/home/andy/2/volatility3/volatility3/cli/text_renderer.py", line 22, in
import capstone
File "/home/andy/.local/lib/python3.11/site-packages/capstone/init.py", line 380, in
import pkg_resources
File "/home/andy/.local/lib/python3.11/site-packages/pkg_resources/init.py", line 3324, in
@_call_aside
^^^^^^^^^^^
File "/home/andy/.local/lib/python3.11/site-packages/pkg_resources/init.py", line 3299, in _call_aside
f(*args, **kwargs)
File "/home/andy/.local/lib/python3.11/site-packages/pkg_resources/init.py", line 3337, in _initialize_master_working_set
working_set = WorkingSet._build_master()
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/andy/.local/lib/python3.11/site-packages/pkg_resources/init.py", line 622, in _build_master
ws = cls()
^^^^^
File "/home/andy/.local/lib/python3.11/site-packages/pkg_resources/init.py", line 615, in init
self.add_entry(entry)
File "/home/andy/.local/lib/python3.11/site-packages/pkg_resources/init.py", line 671, in add_entry
for dist in find_distributions(entry, True):
File "/home/andy/.local/lib/python3.11/site-packages/pkg_resources/init.py", line 2133, in find_on_path
yield from factory(fullpath)
File "/home/andy/.local/lib/python3.11/site-packages/pkg_resources/init.py", line 2190, in distributions_from_metadata
if len(os.listdir(path)) == 0:
^^^^^^^^^^^^^^^^
KeyboardInterrupt

The RAM dump was made by "Magnet RAM Forensics", lsass.dmp was extracted from RAM dump by MemProcFS, minidump module for extracted lsass.dmp doesnt show errors
minidump_output.txt

same issue for me as well, here are the error details:
INFO:pypykatz:pypyKatz version: 0.6.8
INFO:pypykatz:CPU arch: X64
INFO:pypykatz:OS: Windows 10
INFO:pypykatz:BuildNumber: 19041
INFO:pypykatz:MajorVersion: 6
INFO:pypykatz:MSV timestamp: 46191720

Dear all,
The problem with parsing lsass which is extracted by memory capture tools is referred to as memory smearing which is a known behavior of all forensics tools. There are no plans to add more heuristics to pypykatz to battle this issue, as this problem is not something worth addressing on a global level.
I can tell you how I solve this problem:

take memory snapshot multiple times, there is a good chance you'll get at least one dump which is parsable.
modify pypykatz code to suite your needs. by manually identifying key locations, you can edit the code to either look for the smeared values, or add a static offset where you expect the structures to be present.

The RAM dump was made by "Magnet RAM Forensics", lsass.dmp was extracted from RAM dump by MemProcFS, minidump module for extracted lsass.dmp doesnt show errors minidump_output.txt

The problem is that "show no errors" doesn't mean that the actual data in the regions were captured correctly, it merely tell you that all regions were accounted for and the minidump file could be reconstructed. Sometimes even that is not correct, especially with "Magnet dump" which is the usual suspect of causing some issues.

Thank you for the info Skelsec! The memory dump I've collected has been created using Dumpit. Funny enough it works really well with some Windows builds but fails with others.  I will try to play with the structures and see if I can identify something. On the specific machine that it failed creating multiple dumps did not help (so far) unfortunately, so I will try to work with pypykatz and try to modify it a bit.
Thank you for your amazing work with pypykatz!


New version: OpenMedia.4KVideoDownloaderPlus version <IP_ADDRESS>7

Pull request has been created with komac v2.7.0 :rocket:
Microsoft Reviewers: Open in CodeFlow

Automatic Validation ended with:

No errors to post.

(Automated response - build 899.)

@wingetbot run

@wingetbot run


show correct answers

the show correct answers doesn't work. i inserted script into console and it said : Cannot read properties of undefined (reading answers)

Misguided issue. Read server announcements.


Counties don't appear at zoom < ~6

For painting by county, the county boundaries do not appear at a zoom level below ~6 (more zoomed out). There may be cases when users want a bit more zoomed out county painting.

Note: This is probably at tile generation problem


Simplify time format

Storing time without date should be sufficient as the date in encoded by the file location.
Also, it might be worth considering to get rid of the time zone.

Fixed in #52


Change ../ to the previous folder name

Sometimes i forget where i am, emacs already do something like that.
Example:

with this, i always know where i am

Is prompt_path what you are looking for? Try setting it to true in extension's settings table.

Perfect, thats it, THANKS!


Error RIP

Game name: (please, specify the game name)
Engine version: (specify engine version, if known)
Platform: (specify platform, if known)
Error message: Some data left
Stack trace:    at uTinyRipper.Lz4.Lz4DecodeStream.ReadBuffer(Stream stream, Int64 count)
at uTinyRipper.BundleFileScheme.ReadFileStreamMetadata(Stream stream, Int64 basePosition)
at uTinyRipper.BundleFileScheme.ReadScheme(Stream stream)
at uTinyRipper.GameCollection.ReadScheme(SmartStream stream, String filePath, String fileName)
at uTinyRipper.GameCollection.LoadScheme(String filePath, String fileName)
at uTinyRipper.GameStructure.ProcessPlatformStructure(GameStructureProcessor processor, PlatformGameStructure structure)
at uTinyRipper.GameStructure.Load(List1 pathes, LayoutInfo layinfo)    at uTinyRipper.GameStructure.Load(IEnumerable1 pathes, LayoutInfo layinfo)
at uTinyRipperGUI.MainWindow.LoadFiles(Object data)
idk why i think cause cant rip unity 2019?

No promises, but you can try my AssetRipper fork.

i do,
but some like material and texture no Sync

Try again. This was a known bug that I just fixed.


Mark ImageSurface and PDFSurface as Send

While following this guide, I found that Surface wasn't Send. I assume that if it is possible to share it between threads in C, it should also be possible in Rust.

Question: shouldn't cairo-sys-rs be part of gtk-rs/sys? gtk-rs/sys/gdk-sys and gtk-rs/sys/gtk-sys, depend on it. So when I modified cairo, I had to modify gtk-rs/sys to use my repository and ended up editing dependencies in: gio, glib, gtk, gdk, gdk-pixbuf, pango (and gstreamer and gstreamer-sys since my project also depends on gstreamer).

Question: shouldn't cairo-sys-rs be part of gtk-rs/sys?

No, it doesn't have a gir file so it's on its own.

All right! What about a separate crate then? ;) IMHO, it feels strange to modify glib and all the crates that depend on it for a simple modification in cairo-rs.
Anyway, that was just a mere comment. What do you think about the PR?

@GuillaumeGomez what do you think about this PR?

For me it seems fine but I'd prefer to have the confirmation from @EPashkin and @sdroege. :)

I don't think this is safe, and the Cairo documentation there is at least misleading and outdated. See also https://developer.gnome.org/gdk3/stable/gdk3-Threads.html#gdk-threads-enter , those functions are deprecated since years.
While it is safe to send Cairo surfaces backed by a threadsafe underlying surface to another thread, this is not generally the case. With X11 you can in theory make it work (but it's not supported by GDK/GTK anymore, see above). The image surface is also always fine, being backed by just some memory. With Windows you can completely forget it and can't make it work (and the code on the Cairo website never worked on Windows).

tl;dr: This PR is wrong, but you can do something like this for image surfaces. And don't use GTK/GDK from multiple threads, ever :)

I don't use the deprecated functions you mentioned, the guide was just a source of inspiration. I'm implementing a double buffer mechanism, which by design must be multithreaded. Everything GTK related is done in the GTK thread. The double buffer mechanism is shared between threads, one doing the rendering using Cairo, the other being the GTK thread which handles drawing to a drawing area.
If this PR is wrong, how am I supposed to send my Cairo surface between the 2 threads?

Or are you saying that I should find a different design to work this around because this modification could be unsafe in an uncontrolled environment?

What kind of surface are you using for your double buffering implementation?

I'm using cairo::ImageSurface. I think I finally got your first comment. Can I safely set the Send trait on cairo::ImageSurface instead of the general cairo::Surface?

Yes, also the PNG, PDF, SVG surfaces should be safe to mark Send (but not Sync).

Ok! Thanks

Update since last commit:

Send removed from Surface
Send added to ImageSurface and PDFSurface

PNGSurface isn't a dedicated type, there is a convenience function PNGSurface::create_from_png that builds an ImageSurface using cairo_image_surface_create_from_png_stream.
SVGSurface is not available in gtk-rs/cairo yet.

👍 for this now.

@sdroege: Good for you as well?

Sure, that's exactly what I wrote before :)

Then let's merge. Thanks!


Is there any plan to upgrade shipwright and tekton version?

Thank you very much for providing the helm charts installation method of shipwright and Tekton! Now the latest version of shipwright is 0.11, shipwright version 0.11 needs Tekton version 0.41+, I don't know if you have a plan to upgrade the version?

It depends on the minimum kubernetes version they need.

It depends on the minimum kubernetes version they need.

I got it, thanks.


Setup Golint GH Action for this repository

Setup Golint GH Action for this repository

This feature is already implemented -> closing this one.


PR for issue 11

now you can send name of input from material-iput tag defination..
P.S
NPM upgrade and push needed
thanks :)

wait i guess this'll need more modifications than needed

than done*

please reject this PR...
as the rest of the code would need change as well

hey so now the PR is for riot style event listeners for material-input and material-tabs
P.S
NPM upgrade and push needed
thanks :)

@prateekbh Thank you. Code was merged and npm package was updated.


[HOLD for payment 2022-05-23] [$250] Validate password complexity in the front end

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Sign in with a password that is too short

Expected Result:

Error message is shown and we do not call Authenticate command

Actual Result:

Authenticate command is called and error message is shown

Workaround:
Yes
Platform:

Where is this issue occurring?

Web
iOS
Android
Desktop App
Mobile Web

Version Number:
Reproducible in staging?: Yes
Reproducible in production?: Yes
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
Expensify/Expensify Issue URL:
Issue reported by:
Slack conversation:
Job Post https://www.upwork.com/jobs/~01b4cd92ce29d9f69c
View all open jobs on GitHub
IMPORTANT
Our password complexity check is in use here we're just not using it for sign in
https://github.com/Expensify/App/blob/84d058f5ade145a8bc89e00c36b340ba9078a8b0/src/CONST.js#L376-L377

@thesahindia Care to put a quick proposal together for this?

@thesahindia Care to put a quick proposal together for this?

Yeah sure.
Proposal
We have a function for this already -
https://github.com/Expensify/App/blob/bd548576e288229e516223d2ac40929a7825b6a0/src/libs/ValidationUtils.js#L276-L277
We can just use it inside validateAndSubmitForm
https://github.com/Expensify/App/blob/bd548576e288229e516223d2ac40929a7825b6a0/src/pages/signin/PasswordForm.js#L93-L100
        if (!ValidationUtils.isValidPassword(this.state.password)) {
            this.setState({formError: 'passwordForm.error.incorrectLoginOrPassword'});
            return;
        }

Just a quick question, we wanna show the same error message right?

Looks good to me! @kevinksullivan Can you spin up something in Upwork for this and hire @thesahindia?

Just a quick question, we wanna show the same error message right?

Yeah, I think passwordForm.error.incorrectLoginOrPassword is fine to use for now.

hm sorry about that @mananjadhav , I added you back in case we need a C+ for review.
@thesahindia I sent an offer for the job in Upwork, please accept when you get a chance.

Accepted the offer, will raise the PR today.

Waiting on deploy.

Hired ya @mananjadhav , let us know when you accept
Paid @thesahindia $250 for the fix,

Accepted @mallenexpensify

Paid @mananjadhav $250 for C+
Thanks for the help y'all


feat: support MATCH_RECOGNIZE

The code in this PR is me thinking out loud about modelling MATCH_RECOGNIZE in Substrait.
It builds off of the work in https://github.com/substrait-io/substrait/pull/636.
This should not be considered final. The primary reason I've wired this into substrait-java is to be able to produce example plans quickly.

Halting this work for now due to changes in priorities.


Linux repositories and appimages

It'd be great to have app repositories for different Linux distributions. Some of the (free) options you have are,

Bintray by JFrog  ( https://bintray.com )
Gemfury ( https://gemfury.com )
Packagecloud ( https://packagecloud.io )

And for the other distributions, there should be appimages ( http://appimage.org )

I'm not very familiar with the Linux world. What are app repositories? How would it benefit users of this app?
I plan on switching to electron-builder very soon, which will enable me to easily produce both RPM and DEB packages.
AppImage looks like a great idea. Can you open an issue on electron-builder about supporting it?

Great. You can upload the debs and rpms to the one of those repositories.

Can you open an issue on electron-builder about supporting it?

https://github.com/electron-userland/electron-builder/issues/504

@sindresorhus with your comment

Can you open an issue on electron-builder about supporting it?

you got the ball rolling - with the latest electron-builder AppImage is not only supported but is actually now the default format for Linux, https://github.com/electron-userland/electron-builder/issues/504#issuecomment-242812961
Thanks for having started to get the ball rolling!

@probonopd That's awesome! I'll have some time next week to finish up the electron-builder migration and get out an AppImage version of Anatine.


Debug Index.js

How can I debug the server files? e.g. /srv/index.js

Hi. Sorry sir the time of answers, I didn't see this issue.
What do you mean by debuging the server? You can add your console.log as normally, and use the node debugger with your ide as standard.

Ok will try that. Thanks


Support "not in" as well as operator.contains()

Also support "in" on homogenous tuples.
Based on PR #1733.

@pitrou in general can non-homogenous data structures be supported performantly and eventually by "generating explicit branches at compile time rather than relying on runtime dispatch.", as is proposed for Julia?

Can you point to me what Julia's proposal is?
Numba already supports non-homogenous tuples, as well as Numpy structured arrays.

Github is still showing the diff with the types_refactor changes.  Can you try merging master to see if that cleans up the diff?

Yes, done.


Redirecting to Home Page using logo and logo text

Related Issue
[Cite any related issue(s) this pull request addresses. If none, simply state “None”]
Fixes:  #1453
Description
The feature involves enabling proper navigation through clickable elements like the logo or a “Buddytrail” text. When users click on these elements, they should be not-redirected to home when on Team, Blogs, About, FAQ, or Contact—depending on the pages.

#1453

[X] Bug fix
[X] Feature enhancement
[ ] Documentation update
[ ] Other (specify): _______________
Before

https://github.com/user-attachments/assets/e09cbf0b-63ad-4931-bbc4-e53fd8deb262
After
https://github.com/user-attachments/assets/70e8c95f-52c8-4838-9b34-48c73d544102
Checklist:

[X] I have made this change from my own.
[ ] I have taken help from some online resources.
[X] My code follows the style guidelines of this project.
[X] I have performed a self-review of my own code.
[X] I have commented my code, particularly in hard-to-understand areas.
[X] I have made corresponding changes to the documentation.
[X] My changes generate no new warnings.
[X] I have tested the changes thoroughly before submitting this pull request.
[X] I have provided relevant issue numbers and screenshots after making the changes.

kindly review my code
Requesting to add a Level 2 label to my PR focused improves navigation by allowing the logo click to redirect to the Home page.
@PriyaGhosal

@govindbairi Please see the conflicts .


In iOS video feed of friend(or remote) is not visible if app is opening from not running application state

platform: iOS
OS: 15.2
application state: not running
Application is in the not-running state, when the call is answered local video feed is visible but the friend's(or remote) video feed is not visible, only a white screen. In the other application states foreground and background, I can see both local and remote video feeds.
VOIP push is used to trigger the call.
The agora integration is done by following the documentation.
Please help !!
Thank you!
Issue Screenshot:

I am facing the same issue any update?

is it working while application is in the running state?


Unauthorised when trying to get guild roles

I'm trying to get the guild roles using DiscordOAuth2Session.request, and I'm getting an unauthorised error. I'm guessing this is because my application itself doesn't have authorisation to view the roles, how could I get the roles of a guild in this situation?

The guild roles is not provided as Discord OAuth2. It requires your bot application token to acess such resources rather than authorization token obtained from OAuth2.
Work is in progress to included bot resources which are outside of OAuth resources. I think I will update soon with acess to such models. You can track the progress in dev branch.

The guild roles is not provided as Discord OAuth2. It requires your bot application token to acess such resources rather than authorization token obtained from OAuth2.
Work is in progress to included bot resources which are outside of OAuth resources. I think I will update soon with acess to such models. You can track the progress in dev branch.

Is there any way (in dev or release branch) I can do this? (With my bot token ofc)

Give me a bit and I will push the working roles model to dev. Then you can follow same pattern if you want other models.
Anyways if you want you can use this internal method present in dev branch https://github.com/thec0sm0s/Flask-Discord/blob/3ea0fcc44e0f11afbc6f5d3bad5a6a4db9457113/flask_discord/_http.py#L156
Something like:
my_flask_app.config["DISCORD_BOT_TOKEN"] = ""

roles_payload = discord.bot_request("/guilds/{guild.id}/roles")

...

Thank you! Time to swap to dev branch then aha. Any extra requirements I need to know before swapping?

Don't think so. There's no breaking change there.

Seems to have worked! Thank you.

Sorry to re-open this, but I thought this would be a suitable place. How could we use post requests with bot_request?

https://github.com/thec0sm0s/Flask-Discord/blob/3ea0fcc44e0f11afbc6f5d3bad5a6a4db9457113/flask_discord/_http.py#L156
It accepts a method kwarg which defaults to GET. To make post requests, just pass method="POST". It fundamentaly uses the requests.request(...) method and all of the other **kwargs of .bot_request get passed to requests.request. Meaning if you want to pass custom Json payload, you can simply do something like, .bot.request("/route/", method="POST", json=dict()).

Thank you! I don't think I can close this again on mobile.


Fix for external DNS resolution

Certain setups seem to have trouble with the default ndots:5 dns config. Setting this value to 1 should resolve this.
For an example, this breaks DNS resolution of the identity.bitwarden.com domain, because it appends the Kubernetes search domain to it.

I put it in its own configuration section now for if someone needs to configure anything else with the DNS for whatever reason.


update package.json

seems that you've introduced a module called history, which is not listed in your package.json.
pls update your package.json, Thx.
sorry for missing some info, it occurs on version 1.0.1

history is included with react-router


Our agent couldn't find any inactive projects.

i'm frequently getting the message 'Our agent couldn't find any inactive projects.' on a folder containing many node projects and node_modules directories.
I'm not sure whats causing the error, however if i drill down into a specific folder containing a node_modules folder within my code directory it will find it. If I look at a folder that may contain for instance a node project folder as well as a wordpress folder and other it might come up with the above message.
I understand if the project isn't active right now, but perhaps someone has the same issue and can suggest a solution

Hi @amcc, so no node_modules are getting removed?
Could you try running wipe-modules with the --dry flag to see what it finds?
wipe-modules ~/code 20 --dry

just ran this on a folder that contained 2 subfolders, one had a node module folder within it. The other had 2 more subfolders, one with 2 more folders each with a node modules folder, the other itself contained a node-modules folder.
So thats 4 node-modules folders total.
this is the output of the command:
 Our agent is examining your files... Hold on a sec.

 The node_modules in the following directories can be wiped out:

 twitter

 1 node_modules were found!

Oh yeah, right now, the agent only looks and can remove node_modules at one-level depth, so the modules inside react-twitter-apps/funador and react-twitter-apps/react-twitter won't be detected, only the twitter one.
At the moment, wipe-modules isn't very active in terms of development but I'm seriously planning to make a v2 of this with lots of features in mind, one of those features is to support nested projects as well as monorepos, among other cool stuff (rewritten in typescript or python).
What do you think?

As soon as I posted that I figured out that it was a depth thing. That list painted a picture I couldn't figure out originally!
Mining down into folders would be so handy. I put projects into folders to tidy things up.
That single feature would do it for me. It's a fantastic thing other than that. A big issue for me is time machine and Google drive (also Dropbox etc) hating those folders


SA. Too large Heat-Seeking Crosshair, Radar Lines too thick and SunSizeHack = 0 turning off the map fog.

currently using the 2024 Update Hotfix 1 (Builds 9.1/11.1/33.1/6) version.

Check the changelog, those are fixes, not bugs:

Heat-seeking missile crosshair and the weapon crosshair shown while aiming with a gamepad now properly scale to resolution.

The boundaries of the cursor on the Map screen, and the cursor itself now scale to resolution correctly

As for SunSizeHack, I will check, but with that option disabled stock PC draw distance parameters are used for the sun size. I would be surprised if it affected anything else.

can you make it optional? to change in the .ini file.

No. They were not scaling to resolution, so without any doubt it was a bug.


fix(date)!: Restore 'format', 'precison', and usage of moment for the date validator

Resolves https://github.com/adopted-ember-addons/ember-cp-validations/issues/723 .
Changes proposed:

reimplements the date validator that was removed in https://github.com/rwwagner90/ember-validators/pull/100/

I still think it would be better to support a consumer-defined "use luxon" or "use moment" or "use ___", or perhaps to propose an interface in which the consuming app can massage their preferred date library to support determining the before / onOrBefore / after / onOrAfter relationship states.

restores the test suite semantics from before https://github.com/adopted-ember-addons/ember-cp-validations/pull/715 (git diff d6c95d741fa8388ae2c764037bddcd6c91691f09 tests/unit/validators/date-test.js), while adding some additional tests / ensuring the test assertion messages help convey the test intent.

Tasks:

[x] Added test case(s)
[x] Updated documentation

cc: @fsmanuel for visibility

It's worth noting that this is a breaking change to only those on 4.0.0-beta.13 or v4 that modified their usage of the date validator to be compatible with the version provided in ember-cp-validations.
Anyone who is still on 4.0.0-beta.12 or lower would probably consider this to remove a breaking change that is currently in v4.

I still think it would be better to support a consumer-defined "use luxon" or "use moment"

@tehhowch I very much agree with this.
We are currently running the https://github.com/qonto/ember-cp-validations/commit/3767e4114e0c327138287486094e228bd71a45ec in production (as we made efforts to upgrade to ember 4 prior to this addon being adopted).
We have also recently replaced momentjs with dayjs (saving ~25kB's of payload size).
Therefore this PR would be a step backwards for us getting back onto the official repo, as we wouldn't want the extra kB's being reintroduced.
I also completely understand that this PR would undo some unexpected breaking changes for consuming apps that rely on now / precision etc, which I'm all for - this was more a "I agree with your suggestion to let the consumer decide"

@tehhowch I'm on holiday and will have a look after I'm back. I'm still undecided how to move forward with the date validator. I think the addon should not diverge/reimplement too much from ember-validators. Maybe we can provide the old implementation (from this PR) in the docs/readme/migration guide. That way people can use it if they want.
I also agree that a more agnostic solution would be great. Next to moment and dayjs there is also date-fns


chore: bump gh-problem-matcher github action, to silence confusing messages

Resolving a confusion reported on zulip, and recently patched in the Github action. https://github.com/liskin/gh-problem-matcher-wrap/pull/16

I was wrong to be so pessimistic about this being resolved upstream so quickly, nice!

I'm not sure this PR is actually needed though. Following the apparent GH actions conventions the v2 tag for problem matcher looks to be already tracking the minor version number also (i.e. v2 now points at v2.02 already) so explicitly pinning this minor version just means we won't automatically receive future improvements.

I just checked some recent logs and indeed I can't see the remove matcher line so indeed this seems like it just pins us to an old version (which doesn't seem helpful to me)

Thanks for catching that, @alexjbest, I hadn't known.


Simple sort horizontally

I have a simple list similar to this
http://react-dnd.github.io/react-dnd/examples-sortable-simple.html
The only change I have made is added a 'float: left' so instead of a vertical list I now have a horizontal list. The sorting still "works" but not nearly as well as the vertical list. It often doesn't sort at all, any ideas on how to do this?

Sorry found this https://github.com/OliverJAsh/react-dnd-sortable-simple/commit/9ebcabe0f8ade4fd97bf30bf95f011d611072464


make tlc-install is now idempotent

Issues:
Fixes #378
Problem: This command only ran once, then errored on rerun.
For development convenience I tweaked it a bit so it always
just runs.
Analysis:  If the start point is sufficient, then the end point
is the same whether or not make tlc-install has been run
before.

@pjbreaux waddya' think?

OK @pjbreaux "All checks have passed"

@zancas did you actually test that this works?

@swormke is writing a page on confluence with instructions on how to replicate a buildbot worker on your laptop to execute these scripts.  This code is for production regression testing.  Making changes for your personal development environment MUST be isolated in some other container or wrapper script.


Typo

Hi,
Under the external users section: "That contact can share with others users in the external organization"
other*
Thanks,
John

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

ID: 06201faf-0037-3647-4e91-bb0af80d4812
Version Independent ID: 1b397d76-ecfe-046e-a4c4-0fe5293bceb3
Content: What is Azure AD entitlement management? (Preview) - Azure Active Directory
Content Source: articles/active-directory/governance/entitlement-management-overview.md
Service: active-directory
Sub-service: compliance
GitHub Login: @rolyon
Microsoft Alias: rolyon

@frobnitzz Thanks a lot for reporting this. I have updated the doc and it will be published shortly.
Thanks again.


Update all dependencies to latest versions.

LGTM, please squash your commits. Thank you @odd

Thanks @odd. Please squash your commits for merging to master.


crates.io and test resources

Due to the test HDT file tests/resources/swdf.hdt (5.9 MB uncompressed), the hdt package uses 2.42 MB on crates.io, which is much more than other crates typically use.
While this is not much, the eternal nature of crates.io motivates saving space.
Thus, the filesize of the package should be significantly reduced before publishing a new version.
Options

keep it like it is now
use a smaller HDT test file
download the test file when required so that users who don't need the tests don't download it
automatically generate the test file

https://crates.io/crates/brotli-decompressor/2.3.2 also has large amounts of test data


Rename variable names

https://github.com/arillso/ansible.system/blob/723cdc7adadb9a661816f8ff5df6798521de036b/roles/iptables/vars/Debian.yml#L8C47-L8C47
Should the variables not be named?

iptables_configuration_ipv4
iptables_configuration_ipv6

As they are used here: https://github.com/arillso/ansible.system/blob/723cdc7adadb9a661816f8ff5df6798521de036b/roles/iptables/tasks/main.yml#L84

Hello @kpestalozzi,
The issue has been resolved in version 0.0.27. The problem arose due to incorrect adaptation of the variables in /vars to the new Ansible conventions for variable naming.


Wrong default route of onboarded BIG-IP VE

BIG-IP VE can not connect to DNS server due to wrong default route.
[root@host-10-250-15-193:ModuleNotLicensed::Active:Standalone] config # netstat -r
Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
default         <IP_ADDRESS>     <IP_ADDRESS>         UG        0 0          0 vlan-external2
default         <IP_ADDRESS>     <IP_ADDRESS>         UG        0 0          0 mgmt
<IP_ADDRESS>     *               <IP_ADDRESS>   U         0 0          0 mgmt
<IP_ADDRESS>     *               <IP_ADDRESS>   U         0 0          0 vlan-external2
<IP_ADDRESS>     *               <IP_ADDRESS>   U         0 0          0 vlan-internal1
<IP_ADDRESS>     *               <IP_ADDRESS>   U         0 0          0 vlan-failover1
<IP_ADDRESS>       *               <IP_ADDRESS>   U         0 0          0 tmm
<IP_ADDRESS>       tmm-shared      <IP_ADDRESS>     UG        0 0          0 tmm
<IP_ADDRESS>      *               <IP_ADDRESS>     U         0 0          0 tmm_bp

Close this issue, since BIG-IP can work with two default route. We just need to ensure the external network default route can work.


test: Add test to demonstrate PartialEq

Adds a test to demonstrate PartialEq when comparing two parsed
JsonApiDocument objects. Useful to demonstrate that ordering of
attributes / keys within the JSON:API document are irrelevant when
comparing two similar documents.
Adds additional docs to various functions for better understanding of
this crate's implementation

The test changes here are pretty benign, this was mostly motivated by my desire to better understand Rust's PartialEq and how that was implemented on the JsonApiDocument. The documentation here was really spurred from my investigation into the issue in #37. I thought this might help others better understand how all the pieces fit together.


Colors do not show

Hi,
I've installed your package which seems really cool on a Windows machine running Atom 1.0.19 yet colors do not show in the tabs.
I have a the seti icons package installed which alters the tabs yet I disabled it and reloaded Atom and still no color.
I it helps I'm rocking the Atom Matrial UI with Seti Syntax which may also alter the tabs.
Thank you.

Having the same issue as above. Using Atom Material UI and One Dark syntax running on Mac OSX 10.10.
I've also tried switching themes and syntaxes, to no avail.

Definitely a bug, sorry about that, just released this last night but I'll have a fix up soon.

It doesn't work

Okay, I did not see that the rainbow-extensions:toggle command had to be ran. With this things are working for me on OSX (I'll report for Windows in the morning).

I have updated the plugin to automatically activate on atom loading. Sorry for the confusion.


production names are saved to .glyphs file even if same as default

Take e.g. https://gitlab.gnome.org/GNOME/cantarell-fonts, roundtrip to UFO and back.
I suppose there is a case for storing production names in the UFO, but storing them in the glyphs file again if they are the same as the default?

If the production name is always written to the .ufo, the there could be another key like com.schriftgestaltung.storeProduction. That way one can see if it was manually set in Glyphs.

When the production name is always written to .ufo, there could be a key like com.schriftgestaltung.storeProductionName, if it was set manually in Glyphs.

I think we can omit them if they are the same as the default. The default isn’t going to change (I hope), so it should be safe.

@schriftgestalt the key would contain a list of glyphs with manually set production names? What's your stance on changing glyph names in the official GlyphData files? All previous renamings are reflected in altNames, right?

The storeProduction is a bool. It says that the production name in the ufo should be read into the .glyphs file.

It just occurred to me that if I only write a production name to a glyph when it doesn't match the default, I might rely on my _construct_production_name() function to give me "the default" -- it can deviate from what Glyphs.app thinks though 🤔 maybe the dissonance is small enough though...

@schriftgestalt So to match Glyphs, we only set a GSGlyph's production name from a UFO if that glyph has e.g. a com.schriftgestaltung.storeProduction == True lib key?

So what Glyphs seems to be doing is, you set GSGlpyh::storeProductionNames to True and can then change GSGlpyh::productionNames, which is saved to the file. On reading the .glyphs file, GSGlpyh::storeProductionNames is implicitly set to True when a production name is found in it and False otherwise.


Remove unused import package error

Closing this PR as we are completely changing the way we handle errors and warnings


Spurious Build Warnings in Xcode 12.5

Goals
Using Realm in Xcode 12.5 results in several build warnings, as shown in this screenshot:

Expected Results
These warnings should not appear.
The build runs correctly, but the extra 6 warnings pollute the project and make it harder to see when ACTUAL issues are happening.
Actual Results
These warnings appear in Xcode 12.5 but NOT in Xcode 12.4.
Steps for others to Reproduce

Install Realm via Swift Package Manager
Import Realm and RealmSwift into a file and build the project.

Attempted Fixes
I have tried clearing the Package cache and re-installing the packages. No difference.
As far as I can see, there's no way for me to configure them in a way that would remove these warnings?
Version of Realm and Tooling
Realm framework version: 10.7.7
Xcode version: 12.5 Beta 1
iOS/OSX version: macOS 11.4
Dependency manager + version: Swift Package Manager

Newer versions of SPM have the wonderful behavior where it warns if there's any files not explicitly excluded and also warns if there's any excluded files which don't exist, which AFAICT make it impossible to always build without warnings if there's files which conditionally exist. I guess we should probably prioritize building without warnings when the package is being installed over having no warnings when we're developing it.

I guess we should probably prioritize building without warnings when the package is being installed over having no warnings when we're developing it.

That seems right. It doesn't look good to have the "caution sign" icon next to Realm and RealmDatabase in Xcode's sidebar, leading you to believe there's something wrong with the packages.
I looked for a flag to disable that specific warning, but was not able to find one.

Using Xcode13 beta1 and I am having the same problem.
My project is quite big and Realm is the one that shows a warning. I don't know if a warning in one package could be affecting others (Xcode bug?) but so far all others SPM packages I have do not work at all. Maybe this is helpful to Realm team to prioritize on this.


Add maps feature

Pull Request Test Coverage Report for Build 373

13 of 65 (20.0%) changed or added relevant lines in 7 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-1.4%) to 83.64%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/main/java/seedu/address/logic/parser/AddressBookParser.java
0
1
0.0%

src/main/java/seedu/address/model/building/Building.java
1
5
20.0%

src/main/java/seedu/address/ui/GoogleMapsDisplay.java
11
17
64.71%

src/main/java/seedu/address/logic/parser/MapCommandParser.java
0
6
0.0%

src/main/java/seedu/address/commons/events/ui/GoogleMapsEvent.java
0
7
0.0%

src/main/java/seedu/address/ui/InfoPanel.java
1
11
9.09%

src/main/java/seedu/address/logic/commands/MapCommand.java
0
18
0.0%

Totals

Change from base Build 370:
-1.4%

Covered Lines:
2546

Relevant Lines:
3044

💛  - Coveralls


Set up Auth System

Need to incorporate google oauth or something similar so that we can have members login via their WATonomous emails. Must be able to see their groups in order to see what type of permissions they have.

Completed by #25
Continued in #23


Modernize

Python 3 migration: runnable on python 3.6+
Replaced the source of SimpleWebSocketServer from git submodule to pip
Updated Docker base image to python:alpine (latest alpine; previously stuck in both python 2 and older alpine version)
Some indentation inconsistencies has been resolved

Using this for a server to relay from a raspberry pi to reduce home network load, works great, thanks.


wayland: temporary horrible fix for damage

This is NOT a permanent fix to #9.
Fixing #9 will require some additional api changes.
At the moment we do not damage the surface on wayland. This means calling set_buffer will do nothing on some compositors (KDE in my case).
Damage is also broken with window scaling, the API will need to be adjusted to add damage.

Thanks for the PR! Sorry for the delay. I had some employment contract issues with FOSS contributions, and they are now resolved.


Can't lint and format

I use svlangserver by coc.nvim and config like below.
Verilator and verible-verilog-format can run in terminal.
{
    "languageserver": {
        "svlangserver": {
            "command": "svlangserver",
            "filetypes": ["systemverilog"],
            "settings": {
                "systemverilog.includeIndexing": ["**/*.{sv,svh}"],
                "systemverilog.excludeIndexing": ["test/**/*.sv*"],
                "systemverilog.defines" : [],
                "systemverilog.launchConfiguration": "verilator -sv -Wall --lint-only",
                "systemverilog.formatCommand": "verible-verilog-format"
            }
        }
    }
}

What do the logs report? You should be able to get those using the command CocCommand workspace.showOutput and then selecting svlangserver

INFO: INFO: settings[systemverilog.includeIndexing] = **/*.{v,sv,svh}
INFO: INFO: settings[systemverilog.mustIncludeIndexing] =
INFO: INFO: settings[systemverilog.libraryIndexing] =
INFO: INFO: settings[systemverilog.excludeIndexing] = test/**/*.sv*
INFO: INFO: settings[systemverilog.linter] = verilator
INFO: INFO: settings[systemverilog.launchConfiguration] = verilator -sv -Wall --lint-only
INFO: INFO: settings[systemverilog.defines] =
INFO: INFO: settings[systemverilog.lintOnUnsaved] = true
INFO: INFO: settings[systemverilog.linterWhitelist] = /Unsupported: Interfaced port on top level module/i,/Parent instance's interface is not found/i
INFO: INFO: settings[systemverilog.formatCommand] = verible-verilog-format
INFO: INFO: settings[systemverilog.disableCompletionProvider] = false
INFO: INFO: settings[systemverilog.disableHoverProvider] = false
INFO: INFO: settings[systemverilog.disableSignatureHelpProvider] = false
INFO: INFO: settings[systemverilog.disableLinting] = false
INFO: INFO: settings[systemverilog.includeIndexing] = **/*.{v,sv,svh}
INFO: INFO: settings[systemverilog.mustIncludeIndexing] =
INFO: INFO: settings[systemverilog.libraryIndexing] =
INFO: INFO: settings[systemverilog.excludeIndexing] = test/**/*.sv*
INFO: INFO: settings[systemverilog.linter] = verilator
INFO: INFO: settings[systemverilog.launchConfiguration] = verilator -sv -Wall --lint-only
INFO: INFO: settings[systemverilog.defines] =
INFO: INFO: settings[systemverilog.lintOnUnsaved] = true
INFO: INFO: settings[systemverilog.linterWhitelist] = /Unsupported: Interfaced port on top level module/i,/Parent instance's interface is not found/i
INFO: INFO: settings[systemverilog.formatCommand] = verible-verilog-format
INFO: INFO: settings[systemverilog.disableCompletionProvider] = false
INFO: INFO: settings[systemverilog.disableHoverProvider] = false
INFO: INFO: settings[systemverilog.disableSignatureHelpProvider] = false
INFO: INFO: settings[systemverilog.disableLinting] = false
[Error - 22:46:44.440] ERROR: TypeError: Cannot read properties of undefined (reading 'symbolsInfo')
[Error - 22:46:47.440] ERROR: TypeError: Cannot read properties of undefined (reading 'symbolsInfo')
[Error - 22:47:28.662] ERROR: TypeError: Cannot read properties of undefined (reading 'symbolsInfo')
[Error - 22:47:42.096] ERROR: Timeout trying to index document file:///home/wj/tmp/verilog/abc.v
[Error - 22:47:44.475] ERROR: Timeout trying to index document file:///home/wj/tmp/verilog/abc.v
[Error - 22:47:47.477] ERROR: Timeout trying to index document file:///home/wj/tmp/verilog/abc.v

Do you have a .svlangserver folder in your workspace? Does it have a file index.json?
Is the excludeIndexing pattern correct? If it doesn't match any files, then you should empty it out.
Does abc.v have any verification constructs? The language server doesn't understand verification constructs yet.

I don't have a .svlangserver folder in your workspace. I can't see any document about this.
wj@wj:~/tmp/verilog$ ls -al
drwxrwxr-x   - wj 11 Feb 22:44 .git
.rw-rw-r-- 199 wj 14 Feb 22:34 abc.v

// abc.v
`timescale  1 ns/1 ps

module abc
(
    input                       clk,
    inpu                       rst,
);

reg abc = 0;
    always @ (posedge clk)
    begi
        abc <= 1;
    end

endmodule

    command! SvBuildIndex call CocRequest("svlangserver", 'workspace/executeCommand', {'command': 'systemverilog.build_index'})

I must run this command


quick supression of oplocks flag

the parent key isn't there anymore in 2016.  this can easily be improved by os filtering the processing of each element.  I'd have done that but am unsure if this setting exists in 2012r2.  I'd swear it does... dont have a machine on hand... anyhoo...

@vchepkov this should be pulled in from where this comes from, or simply update refs in our puppetfile to track the upstream module.  fixes opslocks missing registry key

Not a big fan of commented sections of the code
better make it a conditional block and a parameter to the class


Zoom by sliding up or down

In future versions could this be integrated.

Yes definitely. I will look into this for the next release
Andrew

Is there any milestone for this and #7? I can help out.

@marcosgriselli zoom by sliding will be implemented on the next release. #7 will be fairly complicated, and I do not believe I will be able to tackle it as I lack the knowledge of AVAssetReader/AVAssetWriter. I would love assistance!

This feature has been added to Version 2.3.0


Standalone: commands run-command and copy-file randomly raise ImportError

Flintrock version: 0.7
OS: OSX Sierra (10.12.1) and Debian Jessie

Using the standalone package, commands run-command and copy-file sometimes raise ImportError: cannot import name 'backend'. I haven't been able to reproduce this error consistently.

Failed to execute script standalone
Traceback (most recent call last):
  File "standalone.py", line 11, in <module>
  File "flintrock/flintrock.py", line 1104, in main
  File "click/core.py", line 716, in __call__
  File "click/core.py", line 696, in main
  File "click/core.py", line 1060, in invoke
  File "click/core.py", line 889, in invoke
  File "click/core.py", line 534, in invoke
  File "click/decorators.py", line 17, in new_func
  File "flintrock/flintrock.py", line 845, in run_command
  File "flintrock/ec2.py", line 49, in wrapper
  File "flintrock/ec2.py", line 384, in run_command
  File "flintrock/core.py", line 384, in run_command
  File "flintrock/core.py", line 484, in _run_asynchronously
  File "asyncio/base_events.py", line 337, in run_until_complete
  File "asyncio/futures.py", line 274, in result
  File "concurrent/futures/thread.py", line 55, in run
  File "flintrock/core.py", line 818, in run_command_node
  File "flintrock/ssh.py", line 57, in get_ssh_client
  File "paramiko/client.py", line 101, in load_system_host_keys
  File "paramiko/hostkeys.py", line 101, in load
  File "paramiko/hostkeys.py", line 335, in from_line
  File "paramiko/ecdsakey.py", line 138, in __init__
  File "cryptography/hazmat/backends/__init__.py", line 71, in default_backend
  File "cryptography/hazmat/backends/__init__.py", line 33, in _available_backends
  File "cryptography/hazmat/backends/__init__.py", line 50, in _backend_import_fallback
ImportError: cannot import name 'backend'

And a stacktrace for copy-file:
Copying file to cluster...
[<IP_ADDRESS>] Copying file...
[<IP_ADDRESS>] Copying file...
[<IP_ADDRESS>] Copying file...
[<IP_ADDRESS>] Copying file...
[<IP_ADDRESS>] Copying file...
[<IP_ADDRESS>] Copying file...
[<IP_ADDRESS>] Copying file...
[<IP_ADDRESS>] Copying file...
[<IP_ADDRESS>] Copying file...
[<IP_ADDRESS>] Copying file...
[<IP_ADDRESS>] Copying file...
[<IP_ADDRESS>] Copy complete.
[<IP_ADDRESS>] Copy complete.
[<IP_ADDRESS>] Copy complete.
[<IP_ADDRESS>] Copy complete.
[<IP_ADDRESS>] Copy complete.
[<IP_ADDRESS>] Copy complete.
[<IP_ADDRESS>] Copy complete.
[<IP_ADDRESS>] Copy complete.
[<IP_ADDRESS>] Copy complete.
[<IP_ADDRESS>] Copy complete.
[<IP_ADDRESS>] Copy complete.
Failed to execute script standalone
Traceback (most recent call last):
  File "standalone.py", line 11, in <module>
  File "flintrock/flintrock.py", line 1104, in main
  File "click/core.py", line 716, in __call__
  File "click/core.py", line 696, in main
  File "click/core.py", line 1060, in invoke
  File "click/core.py", line 889, in invoke
  File "click/core.py", line 534, in invoke
  File "click/decorators.py", line 17, in new_func
  File "flintrock/flintrock.py", line 950, in copy_file
  File "flintrock/ec2.py", line 49, in wrapper
  File "flintrock/ec2.py", line 400, in copy_file
  File "flintrock/core.py", line 422, in copy_file
  File "flintrock/core.py", line 484, in _run_asynchronously
  File "asyncio/base_events.py", line 337, in run_until_complete
  File "asyncio/futures.py", line 274, in result
  File "concurrent/futures/thread.py", line 55, in run
  File "flintrock/core.py", line 848, in copy_file_node
  File "flintrock/ssh.py", line 57, in get_ssh_client
  File "paramiko/client.py", line 101, in load_system_host_keys
  File "paramiko/hostkeys.py", line 101, in load
  File "paramiko/hostkeys.py", line 335, in from_line
  File "paramiko/ecdsakey.py", line 138, in __init__
  File "cryptography/hazmat/backends/__init__.py", line 71, in default_backend
  File "cryptography/hazmat/backends/__init__.py", line 33, in _available_backends
  File "cryptography/hazmat/backends/__init__.py", line 50, in _backend_import_fallback
ImportError: cannot import name 'backend'

This was done with a cluster of 34 slaves, we can see that both commands are partially executed.
This error may be due to https://github.com/nchammas/flintrock/pull/161, which migrates paramiko from version 1.15.4 (which use pycryto) to version 2.0.2 (which uses cryptography).
cryptography supports pyInstaller since version 1.6, according to https://github.com/pyca/cryptography/issues/2039. However, paramiko 2.0.2+ uses cryptography>=1.1

Thanks for the detailed report with references to possible causes. This will make it much easier to investigate! I presume you don't see this with the pip-installed version of Flintrock, correct? (It's OK if you haven't tried that setup.)
I will look at pinning Cryptography to a newer version and send you a test build to try out.
(Note to self, #158 is also related to our PyInstaller packaging.)

@dm-tran - If you dig in to the Flintrock standalone package can you tell exactly what version of Cryptography is in there? It would be good to know if the version is < 1.6 or not. I can check on this later as well.

@nchammas Thanks for your reactivity.
I haven't tried with the pip-installed version. Actually, I'm using a fork of Flintrock that is compatible with my company's VPC.
I'm not familiar with pyinstaller. Where can I see the version of cryptography in the standalone package ?

Hmm, I'm not sure. Don't worry about it if you can't see where. (Part of the issue is that the Linux standalone package for Flintrock is built on Travis CI, so the version of Cryptography selected there may technically be different from the one on my Mac workstation since I haven't pinned it in setup.py.)

@dm-tran - I created a standalone Flintrock package on Ubuntu with Cryptography 1.7.1.
Flintrock-0.8.0.dev0-standalone-Linux-x86_64.zip
Can you test it out and let me know if it resolves the issue you were seeing? I know you said you couldn't reproduce it consistently, but I'm assuming with enough tries you'll know if the issue has been addressed or not.

@nchammas: sorry for the late answer, I was on holidays. I will try this standalone package and will let you know if I can reproduce the issue.
FYI, I have tried downgrading paramiko from version 2.0.2 to version 1.15.4: I haven't run into the "ImportError" since this downgrade.

How did you downgrade if you were using the standalone package?

I reverted commit 65160b4b8d1a603d7e9f7a9ca150be82f09fd792 and used a docker container based on image "python:3.5.2": docker run -t -i -v /absolutePath/to/flintrockRepository:/flintrock python:3.5.2 /bin/bash
I ran pip3 install -r requirements/maintainer.pip and python generate-standalone-package.py to generate a standalone package.

I have tested your stand alone package that was built with Cryptography 1.7.1, and I haven't reproduced the issue.
Here is how I tested it, from my Mac workstation :

create a container from image "Debian Jessie": docker run -t -i -v /absolutePathTo/Flintrock-0.8.0.dev0-standalone-Linux-x86_64:/flintrock debian:jessie /bin/bash
within the container, run the following script:

#!/bin/bash
for i in {1..200}
do
  echo "Iteration $i"
  /flintrock/flintrock --config myConfig.yaml run-command my-cluster 'touch /tmp/test'
  sleep 1
done

@nchammas Today I had the exact same error : ImportError: cannot import name 'backend'. What I found is that when I build using python generate-standalone-package.py and PyInstaller==3.2, I get missing module named cryptography.hazmat.backends.openssl.backend.backend - imported by cryptography.hazmat.backends.openssl.backend, cryptography.hazmat.primitives.ciphers.aead, cryptography.hazmat.primitives.asymmetric.x25519, cryptography.hazmat.backends.openssl, cryptography.hazmat.backends in dist/build/flintrock/warnflintrock.txt (I debugged thanks to this). I do not get this warning with PyInstaller==3.3.
Our fork has been branched from your v0.9.0 tag where PyInstaller == 3.2, do you have the same problem when building that standalone version ? Or maybe I am doing something wrong during the build, maybe the python version ? I am building inside a docker container with Python 3.5.2.
Thank you in advance !

Before generating a standalone package, you should install our maintainer requirements. We require PyInstaller 3.3.

@nchammas There is no error while building, it is just a warning in dist/build/flintrock/warnflintrock.txt, but it explains the error at runtime. Here is my pip freeze for the build:
asn1crypto==0.24.0
attrs==17.4.0
boto3==1.4.4
botocore==1.5.10
certifi==2018.4.16
cffi==1.11.5
chardet==3.0.4
click==6.7
coverage==4.5.1
cryptography==2.2.2
docutils==0.14
flake8==3.3.0
-e git+git@github.com:adotmob/flintrock.git@59e84b60a636e03532103be67549ae38c0dd9df6#egg=Flintrock
idna==2.6
jmespath==0.9.3
mccabe==0.6.1
more-itertools==4.1.0
paramiko==2.1.1
pkginfo==1.4.2
pluggy==0.6.0
py==1.5.3
pyasn1==0.4.2
pycodestyle==2.3.1
pycparser==2.18
pyflakes==1.5.0
PyInstaller==3.2
pypandoc==1.4
pytest==3.5.1
pytest-cov==2.5.1
python-dateutil==2.7.2
PyYAML==3.12
requests==2.18.4
requests-toolbelt==0.8.0
s3transfer==0.1.13
six==1.11.0
tqdm==4.23.2
twine==1.11.0
urllib3==1.22

How do you usually build the standalone package ? I do pip install -r requirements/maintainer.pip and then python generate-standalone-package.py, on a Python 3.5.2 clean Docker container.
I found the line that fixes this in PyInstaller 3.3: https://github.com/pyinstaller/pyinstaller/blob/v3.3/PyInstaller/hooks/hook-cryptography.py#L26
Which is not there for PyInstaller 3.2:
https://github.com/pyinstaller/pyinstaller/blob/v3.2/PyInstaller/hooks/hook-cryptography.py
If the official release for Flintrock v0.9.0 has been built using PyInstaller 3.2, then it might contain the bug. What do you think?

Try building again with cryptography at the minimum version allowed in setup.py.

@nchammas Thank you for your quick response! I still get some warnings with cryptography==1.7.2, but not the one that was causing the error at runtime. I guess the best way to go is to update PyInstaller to 3.3. But in any case, I am curious to know how you build the official releases, what is the workflow to avoid this kind of nasty bugs? Any plans on using pipenv and its awesome Pipfile.lock, to produce deterministic builds?

Yes, pinned versions would be better for the standalone version build because the executable is isolated from any other installed python package.
I am sure there is no problem with the official release, otherwise somebody else would have already raised the issue.
Here is how I fixed my problem (this is definitely not permanent, I just needed to make it work): https://github.com/adotmob/flintrock/commit/416b19003104b07252ca1790fae2e807d6ff6211
Yes, we do regularly create our own Flintrock packages. Basically, every time we want to upgrade Flintrock, we rebase on your master branch and build internally. I think it is mainly because we use Flintrock from a scheduler, which runs on Python 2, so pip install flintrock is not an option. And also, we use private VPCs. You can check the commits we add to make it possible here: https://github.com/adotmob/flintrock/commits/adotmob-version-0.9

Thanks for sharing that background. I'm sorry I've been difficult about getting support for private VPCs in. 😅 The contributions I've gotten in this regard have been good, but always tended to miss something important that would keep me from merging them in.
Would you like to file a separate issue about moving to more deterministic builds, whether it's by fleshing out setup.py some more, or by using a tool like Pipenv or poetry?

Done: https://github.com/nchammas/flintrock/issues/248


Pull support for latest Bazel version

This makes the 2.0 branch match the current maximum Bazel version settings on master. It should help resolve https://github.com/tensorflow/tensorflow/issues/26553, where the latest devel images don't support r2.0.
I'm not sure what the minimum version really is, though.

@goldiegadde is it okay for us to merge PR on 2.0 branch?

@goldiegadde is it okay for us to merge PR on 2.0 branch?

Hi Yifei, yes I think it is okay to merge.

Thanks @goldiegadde!


[backport] Fix split and array_split with unordered indices supplied

Backport of #2815

[automatic post] Jenkins, test this please.

Jenkins CI test (for commit 21a6df6f5de10eb8f34a13e702fa143989e30993, target branch v6) succeeded!

LGTM!


italicize scientific names

@rdmpage
Scientific names should be italicized. Because it is correct.

@MortenHofft It's a small thing but it will have an impact on how experts will view the site. Put another way, it shows that GBIF cares about representing the subject matter correctly.

The GBFI API allows you to request a ParsedName object that has the individual name parts needed to render it nicely for any name usage like this:
http://api.gbif.org/v1/species/118637812/name

For first milestone, we need this for titles of pages at the very least.

this has been implemented for species pages, featured search results and occurrences pages. For lists of occurrences it isn't as we would need to look up each name. we could consider this, but it seems less important in those cases (say occurrence search table where you have the full taxonomic breakdown). Now that we have a way to do so, we can expand the usage of it as needed.
I will close and we can reopen if we overlook important places or someone disagree the decision to not show it in e.g. tables.


KeyError: returns

Expected Behavior
Not crashing
Actual Behavior
Crashing
Steps to Reproduce
Just run the bot
Other Information
OS: Ubuntu 16
From git log:
ec2b7add95da6bc580035d8d4c472c1d41e439a6
Traceback (most recent call last):
File "pokecli.py", line 220, in
main()
File "pokecli.py", line 206, in main
bot.start()
File "/home/jacqueline/Documents/Projects/PokemonGo-Bot/pokemongo_bot/init.py", line 31, in start
self._setup_api()
File "/home/jacqueline/Documents/Projects/PokemonGo-Bot/pokemongo_bot/init.py", line 186, in _setup_api
self.update_inventory()
File "/home/jacqueline/Documents/Projects/PokemonGo-Bot/pokemongo_bot/init.py", line 208, in update_inventory
response = self.api.call()
File "/home/jacqueline/Documents/Projects/PokemonGo-Bot/src/pgoapi/pgoapi/pgoapi.py", line 80, in call
response = request.request(api_endpoint, self._req_method_list, player_position)
File "/home/jacqueline/Documents/Projects/PokemonGo-Bot/src/pgoapi/pgoapi/rpc_api.py", line 93, in request
response_dict = self._parse_main_response(response, subrequests)
File "/home/jacqueline/Documents/Projects/PokemonGo-Bot/src/pgoapi/pgoapi/rpc_api.py", line 201, in _parse_main_response
response_proto_dict = self._parse_sub_responses(response_proto, subrequests, response_proto_dict)
File "/home/jacqueline/Documents/Projects/PokemonGo-Bot/src/pgoapi/pgoapi/rpc_api.py", line 208, in _parse_sub_responses
del response_proto_dict['returns']
KeyError: 'returns'
Saw another person with the same issue that seemed to be solved by getting the latest commit and reinstall requirement, already done that but still doesn't work

#1491

Run git log -n 1 --pretty=format:"%H"' and send the output, you didn't specify it in the post.

Updated

Most likely a problem with Pokemon GO servers being down, it's happening to multiple people. Assuming your output is a little bit different than #1491 because of you being on dev branch.

I'm getting this same error.  I updated the requirements and still nothing.

I switched to Dev branch and update requirement and get the new config and it work

Same problem

Please close this issue then.
To fix:
Switch to dev branch.
(git clone -b dev https://github.com/PokemonGoF/PokemonGo-Bot)
cd PokemonGo-Bot
pip install -r requirements.txt
Edit your config(s) and try running.

Well okay, it mean it is only fixed on the dev branch though, master is still messed up.
But if you want me to to close it I will.


AwsSession copies endpoint_url if region is the same

Description of changes:
If the region in aws_session.copy_session(region) is the same as the one of aws_session, the endpoint url is also copied.
Example:
import boto3
from braket.devices import Devices
from braket.aws import AwsSession, AwsDevice

region_name = "us-west-2"
endpoint_url = "some-endpoint"
braket_client = boto3.client("braket", region_name=region_name, endpoint_url=endpoint_url)
aws_session = AwsSession(braket_client=braket_client)

device = AwsDevice(Devices.Amazon.SV1, aws_session=aws_session)
task_batch = device.run_batch([Circuit().x(0)]*2, shots=100)

is expected to create tasks in some-endpoint. But currently it would create tasks in the default endpoint of users' region. This PR fix this issue and creates task in some-endpoint.
Testing done:
tox
Merge Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your pull request.
General

[x] I have read the CONTRIBUTING doc
[x] I used the commit message format described in CONTRIBUTING
[x] I have updated any necessary documentation, including READMEs and API docs (if appropriate)

Tests

[x] I have added tests that prove my fix is effective or that my feature works (if appropriate)
[x] I have checked that my tests are not configured for a specific region or account (if appropriate)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Would you be able to update the PR description with an example of the user problem that this fix solves?

@yitchen-tim Would you be able to update the PR description with an example of the user problem that this fix solves?

yes, I added an generic example to the description. A more specific example is in an internal tracking board.

Can we solve this by using environment variables?
import os
from braket.devices import Devices
from braket.aws import AwsSession, AwsDevice

os.environ["AWS_REGION"] = "us-west-2"
os.environ["BRAKET_ENDPOINT"] = "some-endpoint"

device = AwsDevice(Devices.Amazon.SV1)
task_batch = device.run_batch([Circuit().x(0)]*2, shots=100)

I believe should work without any code changes

thank you, this os.environ works well for me


Will not open Chrome When i run in Live Server

Issue Type: Bug
Will not open Chrome When i run in Live Server,
It started when I tryed to run debug NodeJs
VS Code version: Code 1.37.1 (f06011ac164ae4dc8e753a3fe7f9549844d15e35, 2019-08-15T16:17:55.855Z)
OS version: Windows_NT x64 10.0.17763

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-8265U CPU @ 1.60GHz (8 x 1800)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwareoop_rasterization: disabled_offprotected_video_decode: enabledrasterization: enabledskia_deferred_display_list: disabled_offskia_renderer: disabled_offsurface_synchronization: enabled_onvideo_decode: enabledviz_display_compositor: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
7.85GB (4.05GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions (6)

Extension
Author (truncated)
Version

vscode-devtools-for-chrome
cod
0.0.5

vscode-eslint
dba
1.9.1

beautify
Hoo
1.5.0

open-html-in-browser
pea
1.3.0

LiveServer
rit
5.6.1

open-in-browser
tec
2.0.0

can you attach debug configuration?

I cant find a "debug configuration" in the list to add in launch.json. It looks like this ...
{
// Use IntelliSense to learn about possible attributes.
// Hover to view descriptions of existing attributes.
// For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
"version": "0.2.0",
"configurations": [
    {
        "type": "chrome",
        "request": "attach",
        "name": "Attach to Chrome",
        "port": 9222,
        "webRoot": "${workspaceFolder}"
    },

    {
        "type": "chrome",
        "request": "launch",
        "name": "Launch Chrome against localhost",
        "url": "http://localhost:5500",
        "webRoot": "${workspaceFolder}"
    }
]

}

Get this error when I run debug - Attach to Chrome

	{
		"name": "(Electron) Attach Renderer",
		"type": "chrome",
		"request": "attach",
		"port": 9223,
		"timeout": 30000
	},
	{
		"type": "chrome",
		"request": "launch",
		"name": "(React) Launch",
		"runtimeExecutable": "F:/Program Files/Google/Chrome/Application/chrome.exe",
		"url": "http://localhost:3000",
		"timeout": 60000,
		"userDataDir": "C:/samples/electron-app/.chrome",
		"runtimeArgs": [
			"--disable-session-crashed-bubble",
			"--disable-infobars"
		]
	}

as an example

Please give more details about exactly what you are doing. Are you saying that you expect Live Server to launch Chrome? Or if you want the launch config to launch Chrome, you will have to run the "launch" type config.

I actively use VS code and have a live server running whilst doing game development course work.
If VS code has been open for some time, the extension for live server seems to become unresponsive.
In order to work around this, VS code needs to be closed and opened again.
As I was writing this; the live server had opened but only after like 10-20 minutes after I clicked "Run Live Server".
I have only experienced this issue recently. I cannot pin point the exact version it started on since VS code has had a few updates recently but I would say the time frame is accurate with the start of this bug report.

Please let me know if you need additional information to help resolve this issue.

@LukeWolfGames check for some process using lots of CPU and slowing down your machine. Possibly file an issue on Live Server. I am closing this, no response from OP.


Symbol '+' in route+tag.min.js and HTTP/2 protocol

Hello my friends.
Im enable HTTP/2.0 protocol in my project and loading route+tag.min.js says:
Status Code:404
If remove symbol ‘+’ in route+tag.min.js => route.tag.min.js result:
 Status Code:200
Symbol ‘+’ not valid on names in h2 protocol?
Yes all files are present in the directory 8-)

use route%2Btag.min.js instead


metadata polishing

-- checking of "-bin" key suffix, automatic downcasing of metadata keys, making instances of Metadata.Entry immutable.
-- added tests for metadata entry.
-- a bit of style fixing

LGTM, once tests pass.


Various UI improvements

regarding text inputs can I see screenshots before merging?

Sure, it was not easy to see the input line so I made it much darker. The text itself is slightly darker.

Do you like how it looks now?  I'm not sure...

Yeah, it looks strange in this screen because the input line and dropdown box touch and have different colors. But I find that a visible input line greatly improves usability in other screens. An option would be to make the dropdown box the same color. I'll play around.

Ok, what about this: default input line color is lighter but still visible. On contract screens, input fields and boxes have a small space in between.

Looks good!


pretty-ms-cli

It may seem strange, but a lot of the dependencies (9 / 14) are used for cli.
Сan you split the package?

More thanks!


Nightly lints

Fix warnings generated by nightly clippy.

Codecov Report
Patch coverage: 100.00% and no project coverage change.

Comparison is base (722606b) 93.38% compared to head (744ab68) 93.38%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #341   +/-   ##
=======================================
  Coverage   93.38%   93.38%
=======================================
  Files         119      119
  Lines       18976    18979    +3
=======================================
+ Hits        17721    17724    +3
  Misses       1255     1255

Impacted Files
Coverage Δ

argmin/src/solver/quasinewton/lbfgs.rs
96.19% <ø> (ø)

argmin/src/core/macros.rs
94.54% <100.00%> (ø)

... and 3 files with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.