mystmd: 1.1.55 -> 1.2.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for mystmd is: Command line tools for working with MyST Markdown
meta.homepage for mystmd is: https://github.com/executablebooks/mystmd
meta.changelog for mystmd is<EMAIL_ADDRESS>Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.1.56 with grep in /nix/store/62wcpd73pnwi4j0qfnm8xz10kqkv1jmx-mystmd-1.1.56
found 1.1.56 in filename of file in /nix/store/62wcpd73pnwi4j0qfnm8xz10kqkv1jmx-mystmd-1.1.56

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

mystmd

Instructions to test this update (click to expand)

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

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

Or:
nix build github:r-ryantm/nixpkgs/f7d4e13006ac3e026a2362b976cda68d006a7db9#mystmd

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/62wcpd73pnwi4j0qfnm8xz10kqkv1jmx-mystmd-1.1.56
ls -la /nix/store/62wcpd73pnwi4j0qfnm8xz10kqkv1jmx-mystmd-1.1.56/bin

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

1 package built:

mystmd

Maintainer pings

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for mystmd is: Command line tools for working with MyST Markdown
meta.homepage for mystmd is: https://github.com/executablebooks/mystmd
meta.changelog for mystmd is<EMAIL_ADDRESS>Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.2.0 with grep in /nix/store/9fayalnasi25073c1j6kaq2znk2qy06l-mystmd-1.2.0
found 1.2.0 in filename of file in /nix/store/9fayalnasi25073c1j6kaq2znk2qy06l-mystmd-1.2.0

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

mystmd

Instructions to test this update (click to expand)

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

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

Or:
nix build github:r-ryantm/nixpkgs/11eec875cbb821f0ce3901c9ed429b1db0092f4c#mystmd

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/9fayalnasi25073c1j6kaq2znk2qy06l-mystmd-1.2.0
ls -la /nix/store/9fayalnasi25073c1j6kaq2znk2qy06l-mystmd-1.2.0/bin

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

1 package built:

mystmd

Maintainer pings


Creating a custom render class still requires Cairo

I'm trying to use pcb-tools to create an importer for Blender. The approach I'm thinking of is to create a custom renderer that actually generates Blender geometry. However, when importing gerber.render it fails because that module tries to import .cairo_backend.
By automatically importing that module, Cairo is always a requirement, even when it's not used at all.
To reproduce this issue, just run import gerber.render.render in a Cairo-less environment.

Yeah cairo has been the de-facto renderer for a while, extensibility needs a bit of love and documentation. Check with 5245fb9 and see if that works for you


Azure Database for PostgreSQL  in Gov

Azure Database for PostgreSQL - Flexible Server states that it is available in Gov, however, products by region says that this is unavailable in Gov. Which is correct?
https://azure.microsoft.com/en-us/explore/global-infrastructure/products-by-region/?products=postgresql

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

ID: 789139e9-15bb-58a9-7dc3-bd85c0bcfee5
Version Independent ID: cda59fed-f3ff-aa09-a13c-027a54e4141a
Content: Azure Database for PostgreSQL - Flexible Server
Content Source: articles/postgresql/flexible-server/overview.md
Service: postgresql
Sub-service: flexible-server
GitHub Login: @sunilagarwal
Microsoft Alias: sunila

Hi @sunilagarwal,
Could you please look into the correctness of the document and get this updated in official page as applicable. Thanks

It is available in government.

#please-close


Unable to run salt modules/functions from rundeck using salt step

Hi
I am able to run only cmd.run_all module/function salt commands from rundeck using salt step plugin.
I am aware that the cmd.run_all function is present in:
/build/resources/main/defaultReturners.yaml:
handlerMappings:
cmd.run_all: *defaultCommandParser
state.highstate: *alwaysSuccessful
file.touch: *alwaysSuccessful
file.append: *alwaysSuccessful
file.remove: *alwaysSuccessful
Could anyone please tell me how can i run all the salt commands like for example : "test.ping" or "pkg.install"
I am not able to find any documentation about salt-step plugin usage with salt-api and salt.

Found the fix myself.
The problem with salt modules and functions like test.ping return a boolean value like TRUE or FALSE.
org.rundeck.plugin.salt.output.SaltReturnResponse expects the return value to be a json response from salt api.
To add the boolean value, one needs to modify the code located at /src/main/java/org/rundeck/plugin/salt/output/SaltJsonReturnHandler.java
/**

Copyright (c) 2013, salesforce.com, inc.
All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided
that the following conditions are met:

Redistributions of source code must retain the above copyright notice, this list of conditions and the
following disclaimer.

Redistributions in binary form must reproduce the above copyright notice, this list of conditions and
the following disclaimer in the documentation and/or other materials provided with the distribution.

Neither the name of salesforce.com, inc. nor the names of its contributors may be used to endorse or
promote products derived from this software without specific prior written permission.

 IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR
ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED
TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.
*/

package org.rundeck.plugin.salt.output;
import java.lang.reflect.Type;
import java.util.Map;
import com.google.gson.Gson;
import com.google.gson.JsonSyntaxException;
import com.google.gson.reflect.TypeToken;
/**

Handler for generating {@link SaltReturnResponse} from minion json responses.
*/
public class SaltJsonReturnHandler implements SaltReturnHandler {
protected static final Type RETURN_RESPONSE_TYPE = new TypeToken<Map<String, String>>() {}.getType();
protected String exitCodeKey;
protected String standardOutputKey;
protected String standardErrorKey;
public void setExitCodeKey(String exitCodeKey) {
this.exitCodeKey = exitCodeKey;
}
public void setStandardOutputKey(String standardOutputKey) {
this.standardOutputKey = standardOutputKey;
}
public void setStandardErrorKey(String standardErrorKey) {
this.standardErrorKey = standardErrorKey;
}
@Override
public String toString() {
return "SaltJsonReturnHandler [exitCodeKey=" + exitCodeKey + ", standardOutputKey=" + standardOutputKey
+ ", standardErrorKey=" + standardErrorKey + "]";
}
/**

Deserializes a {@link SaltReturnResponse} from a salt minion json response using
the specified exit code, standard output, and standard error keys.

@param rawResponse

       a minion's json response.

@throws SaltReturnResponseParseException

        if there was an error interpreting the response

*/
@Override
public SaltReturnResponse extractResponse(String rawResponse) throws SaltReturnResponseParseException {
try {
Gson gson = new Gson();
Map<String, String> result = gson.fromJson(rawResponse, RETURN_RESPONSE_TYPE);
SaltReturnResponse response = new SaltReturnResponse();
     if (exitCodeKey != null) {
         String exitCodeStringValue = extractOrDie(exitCodeKey, result);
         Integer exitCode = Double.valueOf(exitCodeStringValue).intValue();
         response.setExitCode(exitCode);
     }

     if (standardOutputKey != null) {
         String output = extractOrDie(standardOutputKey, result);
         response.addOutput(output);
     }

     if (standardErrorKey != null) {
         String error = extractOrDie(standardErrorKey, result);
         response.addError(error);
     }

     return response;
 } catch (JsonSyntaxException e) {
     throw new SaltReturnResponseParseException(e);
 }

}
protected String extractOrDie(String key, Map<String, String> data) throws SaltReturnResponseParseException {
if (!data.containsKey(key)) {
throw new SaltReturnResponseParseException(String.format("Expected key %s in %s, found none.", key, data));
} else {
return data.get(key);
}
}
}

In the above code, Gson object should be able to evaluate RETURN_RESPONSE_TYPE as boolean as shown below:
Map<String, String> result = gson.fromJson(rawResponse, RETURN_RESPONSE_TYPE);
I have decided to write my custom module and function in salt so that it returns the json response to rundeck salt step plugin instead of modifying the Gson code because i need to differentiate between command executed from rundeck is either a cmd.run_all or a salt module Example : test.ping
Thanks to all who had a look at this issue and walked over it :+1:


Correct solution

removed solution by mod

@Viniciogj
Please do not post your solution on here. You could help people at FreeCodeCamp Chat Room or Forum. GitHub Issues are for reporting bugs on the website only.
Happy Coding!


Can't get loading spinner to show up

First of all, thanks for your great work on this component.
We're having a bit of trouble getting any sort of activity indicator to show in our app while it fetches locations from Google's API using version 1.2.12 of react-native-google-places-autocomplete. Here's the code we're using to include it:
<GooglePlacesAutocomplete
  placeholder={this.props.placeholder || 'Enter Location'}
  minLength={2}
  autoFocus
  listViewDisplayed='auto'
  fetchDetails
  enablePoweredByContainer={false}
  renderDescription={(row) => row.description}
  textInputProps={{
    autoCorrect: false
  }}
  onPress={(data, details = {}) => this._setDetails(details)}
  query={{
    key: googleMapsKey,
    language: 'en'
  }}
  styles={placesStyles}
  nearbyPlacesAPI='GooglePlacesSearch'
/>

const placesStyles = {
  textInputContainer: {
    height: 40
  },
  textInput: {
    borderRadius: 0,
    marginLeft: 0,
    marginRight: 0,
    marginTop: 0,
    height: 40,
    borderWidth: 1,
    borderColor: colors.grey,
    fontFamily
  },
  description: {
    fontFamily
  }
}

Looking at the source code for the component, it looks like you're doing a if (rowData.isLoading === true) { check within the _renderLoader function. When I insert a console.log here, this is always undefined for me. However, if I change the equality check to if (true) { I still never see an ActivityIndicator rendered, even if simulate a really slow connection.
Aside from this, everything seems to work as we'd expect, we can get results back just fine as you can see from the screenshot below:

Any help anyone could offer would be very much appreciated. This is causing a poor user experience in our app at the moment for users with slow connections.

Hi, are you able to workaround to show loader when it's searching?

The spinner is related to the onPress event of an item. But it's good to have this kind of feeding.
I think the loading it's not added because it's hard to find a good ux for it since the load it's supposed to appear in the onChange event, which might clean all the places you already have.
Maybe the usage of the NetworkActivityIndicatorVisible (here - iOS only) might be a good thing to add.
Otherwise, can you give me some ideas about a good place to put the loading indicator?

Hi guys, I am also stuck on this issue.Anyone found a solution?

I would say if you can make a progress bar under the textinput container or something custom so that whosoever wants to add a loader can add as per their own accordance.


Behaviour of range methods when start > end

List.range(100,1) returns an empty List. It would be better if we either

Throw an exception (or)
Return a list in reverse order.

Thank you for your suggestion. We align to Scala's Range, which works as follows:
scala> 0 until 10 // same as Range(0, 10)
res0: scala.collection.immutable.Range = Range(0, 1, 2, 3, 4, 5, 6, 7, 8, 9)

scala> 10 until 0 // same as Range(10, 0)
res1: scala.collection.immutable.Range = Range()

scala> 10 until 0 by -1 // same as Range(10, 0, -1)
res2: scala.collection.immutable.Range = Range(10, 9, 8, 7, 6, 5, 4, 3, 2, 1)

In Javaslang it looks like this:
// = List(0, 1, 2, 3, 4, 5, 6, 7, 8, 9)
List.range(0, 10);

// = List()
List.range(10, 0);

// = List(10, 9, 8, 7, 6, 5, 4, 3, 2, 1)
List.rangeBy(10, 0, -1);

Changing the current range implementation would break semantics of existing source code. Also it would confuse developers (including me) to have different semantics than in other programming languages. So let's keep the currenty behavior and please use rangeBy. I will close this ticket.
Note: Throwing exceptions is (in general) no viable solution for Javaslang. Exceptions are concidered evil. Try to work with defined values whenever possible.


[#2] Fix warnings during gem building process

This is fix for issue #2.
Here are changes:

Update gemspec file to fix warnings
Update gem version

thanks & pushed to rubygems


[KEv2] EKS v2 clusters need to have network role tags

To support service type LoadBalancer and ALB ingress controller on EKS the subnets need to be tagged. The scope of this is only for subnets that we provide for the user. If the user is bringing their own subnets and VPCs then it is the responsibility of the user to tag appropriately.
All subnets should have:

Key
Value

kubernetes.io/cluster/
shared

public subnet:

Key
Value

kubernetes.io/role/elb
1

Private Subnet:

Key
Value

kubernetes.io/role/internal-elb
1

see:
https://docs.aws.amazon.com/eks/latest/userguide/load-balancing.html
https://docs.aws.amazon.com/eks/latest/userguide/alb-ingress.html

On master-head - commit id: c428bc9fe

Deploy a hosted EKS cluster, do not specify VPC/subnet (Public access)
Subnets for Instances created for the cluster have the below tags:


when called from hypridle after suspend , key press behaves like 3 keys pressed

When triggering it from elsewhere is fine. But when coming back from suspend with the current configuration, it just displays the lockscreen correctly, but when pressing one key like 'p', you see on the input '***' for every key press.
Im using the following in hypridle and hyprlock
general {
    lock_cmd = dunstify "lock\!" -t 1200                                 # dbus/sysd lock command (loginctl lock-session)
    unlock_cmd = #notify-send "unlock!"                                   # same as above, but unlock
    # comented out to avoid hard logout via tty
    before_sleep_cmd = #grim /tmp/lockscreen.png; hyprlock                       # command ran before sleep
    after_sleep_cmd = #notify-send "Welcome Back form hypridle " -t 1000  # command ran after sleep
    ignore_dbus_inhibit = false                                 # whether to ignore dbus-sent idle-inhibit requests (used by e.g. firefox or steam)
}

listener {
    timeout = 500                                                       # in seconds
    on-timeout = notify-send "You are idle!"                            # command to run when timeout has passed
    on-resume = notify-send "Welcome back!" -t 1000                     # command to run when activity is detected after timeout has fired.
}

background {
    monitor =
    # only png supported for now
    path = /tmp/lockscreen.png
    color = rgba(255, 255, 255, 1.0)
    blur_passes = 2 # 0 disables blurring
    blur_size = 4
    noise = 0.0117
    contrast = 0.8916
    brightness = 1.00
    vibrancy = 0.8696
    vibrancy_darkness = 0.0
}

input-field {
    monitor =
    size = 200, 50
    outline_thickness = 3
    dots_size = 0.33 # Scale of input-field height, 0.2 - 0.8
    dots_spacing = 0.15 # Scale of dots' absolute size, 0.0 - 1.0
    dots_center = false
    outer_color = rgb(151515)
    inner_color = rgb(200, 200, 200)
    font_color = rgb(10, 10, 10)
    fade_on_empty = true
    placeholder_text = <i>Input Password...</i> # Text rendered in the input box when it's empty.
    hide_input = false

    position = 0, -20
    halign = center
    valign = center
}

Linux arch 6.7.6-arch1-1
hyprland 0.35.0-2

updated to latest, got rid of the grim unnecesary step and it works

how did you get rid of the grim unnecessary steps?

I had this
before_sleep_cmd = #grim /tmp/lockscreen.png; hyprlock

But is wrong and unnecessary, since hyprlock is already making a screenshot with the option screenshot in path


Hides Contact button for uninquireable works and removes Specialist button entirely

This is currently an illustrative PR - it shouldn't be merged yet.
Fixes #1385

1 Warning

:warning:
Found unstubbbed networking requests

ARFairFavoritesNetworkModelSpec in test_ignores_artworks_without_a_partner
ARFairFavoritesNetworkModelSpec in test_ignores_artworks_without_a_partner
ARFairFavoritesNetworkModelSpec in test_ignores_artworks_without_a_partner

  Generated by :no_entry_sign: danger

Since the google doc is no longer maintained, I removed the link to it and added what I hope are helpful documentation comments.

removes Specialist button entirely

Can you elaborate a bit on how you arrived at this needing to be removed completely?

@katarinabatina said we should mimic what web does, and @broskoski said they've removed this from both force and martsy.

@sarahscott yes we should have removed ask a specialist a while ago, we should go ahead and do now

@sarahscott Can you add a CHANGELOG?

:+1:

Nice work on the comments :+1:


compared with other RPC, performance needs to be improved

v2 version, compared with Go RPC, performance is not as good

V2 is unsupported. V3 is non-commercial. Performance is not my concern at this time.


Facebook: Return delivery error metadata

Is your feature request related to a problem? Please describe.
In case delivery for a Facebook message fails, I want the reason of failure to be returned async via metadata webhook/websocket.
Describe the solution you'd like
When sending a message to Facebook using /messages.send fails I want to receive the error in the metadata.

@chrismatix: can we make the implementation of this generic for all sources?
The same problem exists for all conversational sources.

@steffh The mechanism to send metadata back already exists, but actually doing so is, unfortunately, source-specific. But we can expand the ticket to add this to all sources.
The only way to make this source agnostic is by using the source api.

okay i see, thanks @chrismatix. if it's not too much effort implementing it in all sources + source api in the same way, that would make things easier for the clients not to differentiate between sources.

@steffh It's implemented for all current sources now (the source API already had this). Here are the new docs https://deploy-preview-2657--docs-airy.netlify.app/api/endpoints/messages#error-handling

@chrismatix thank you! perfect!


cant start localstack

Hi, Im sorry but it seems I cant start localstart running:
docker run --rm -it -p 4566:4566 -p 4510-4559:4510-4559 localstack/localstack:1.2.0

Can you help me?

Looks like Docker is not running on your machine.
Sorry for the late reply! I will close this.


[feature] One-version for core dependencies.

Is your feature request related to a problem? Please describe.
I want to standardize the dependency version for a huge mount of packages for my monorepy. I.e. one typescript, one react, one react-dom, one jest etc. Previously I've done this by having a root project (with npm workspaces) and other packages inherit from it.
I can't figure out how to get that root package to be installed using moon.
I can't figure out how to prohibit other packages from overriding the package version (don't want to write another sync script).
I can't figure out how to ensure that all packages share the same version of core dependencies.
I.e. if package/demo1/pakcage.json specifies<EMAIL_ADDRESS>and package/demo2/package.json specifies<EMAIL_ADDRESS>I'd like those to be reconciled to one version or display an error to the user.
Describe the solution you'd like
From the documentation where it says Can sync cross-project dependencies to package.json I thought this was already implemented. But I don't see it working. In fact the root package.json is ignored, and conflicting versions in sibling packages aren't touched by moon tooling.
Describe alternatives you've considered
A. I can write a unit test scanning package.json files manually and error out if incompatible versions are found. I'd also need to write a tool that would remove those deps if they're specified in the root folder.
B. I think I'd also need to move my root package.json outside of the typescript folder (undesired) for moon to see it. Or I have to list it as a sibling project (even though it's a root).
Additional context

I found some settings to help define the root project:
toolchain.yml
typescript:
  rootConfigFileName: "typescript/tsconfig.json"
  rootOptionsConfigFileName: "typescript/tsconfig.options.json"

workspace.yml
projects:
  root: "typescript"

But I still see conflicting versions in each package.

I can't figure out how to get that root package to be installed using moon.

The root package.json that has workspaces (for monorepo setup) can define dependencies.  Are you saying these deps don't get installed?

I can't figure out how to prohibit other packages from overriding the package version (don't want to write another sync script).

This isn't something that moon prevents. You would need your own custom scripts to check this.

I can't figure out how to ensure that all packages share the same version of core dependencies.

Same as the previous answer. You'll need something custom here.

From the documentation where it says Can sync cross-project dependencies to package.json I thought this was already implemented. But I don't see it working. In fact the root package.json is ignored, and conflicting versions in sibling packages aren't touched by moon tooling.

This isn't npm dependencies, this is local packages required for monorepo setups. The workspace:* kind of stuff.
With all that being said, this is known as the "single version policy" or "one version policy" and is something that I want to build into moon directly, but it currently does not exist. It assumes your using workspaces for monorepos.

Added a setting to support the one version policy pattern. https://moonrepo.dev/blog/moon-v1.17#supporting-the-single-version-policy-pattern


Correct the systemctl command in README.md

systemd is not a command
enable is not a flag in systemctl, it's a subcommand

Nice catch, thank you.


v0.11.0 is not published to npm

Describe the bug
As title
Reproduction
<EMAIL_ADDRESS>System Info
N/A

Used Package Manager
n/a
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guide.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
[X] The provided reproduction is a minimal reproducible of the bug.

Published. Thanks


Adding migration generator

No options currently used
Simple generator: bundle exec lotus generate migration create_user

Coverage decreased (-0.36%) when pulling f4a713c9aa16814ff36fa5cf7f1322c636e58d7a on thecatwasnot:migration_generator into cb0eea01d23032ee15d2860d7fedae18ec489886 on lotus:master.

Coverage decreased (-0.3%) when pulling c172ca010bbd507fdf0d3cf11461531281b7a20e on thecatwasnot:migration_generator into cb0eea01d23032ee15d2860d7fedae18ec489886 on lotus:master.

:+1: perfect for me except above comments

except above comments and failed build, this is :+1:
Pending discussion: In order to generate migration for lib/chirp and apps/web, we need a reliable way to detect the app name. Suggested solution is having app name defined in .lotusrc file. I am not really a fan of this approach, I prefer an alternative and implicit way.
Here is my proposal:

Enforce naming convention for lib/chirp, that is renaming lib/chirp.rb to lib/application.rb
Introduce options to set migration path for Lotus::Model and Lotus::Application

@jodosha thoughts?

Coverage decreased (-0.3%) when pulling cc692d1e917c4a5f5d9164e9b326cf9309dd0d8a on thecatwasnot:migration_generator into cb0eea01d23032ee15d2860d7fedae18ec489886 on lotus:master.

Coverage increased (+1.27%) when pulling 942fbd9d2602c1913b0971bb2040aa3b32d8c0df on thecatwasnot:migration_generator into cb0eea01d23032ee15d2860d7fedae18ec489886 on lotus:master.

My current feeling is that the application db migratioins should live in db/migrate and slice specific migrations should live in apps/web/db/migrate
IMHO that would be the least surprising option.
I can add the slice migration generator with bundle exec lotus generate migration web migration_name

@thecatwasnot db/migrate seems to be poor choice of naming, as suggested, I want to rename it to db/migrations, can you do some magic and make it happen? TIA

I think we should cover the 2 scenarios:
bundle exec lotus generate migration migration_name and bundle exec lotus generate migration slice_name migration_name

this is in progress guys, should be done tonight
On Mon, Jan 19, 2015 at 8:03 AM, AlfonsoUceda<EMAIL_ADDRESS>wrote:

I think we should cover the 2 scenarios:
bundle exec lotus generate migration migration_name and bundle exec lotus
generate migration slice_name migration_name
—
Reply to this email directly or view it on GitHub
https://github.com/lotus/lotus/pull/139#issuecomment-70496079.

Coverage increased (+1.49%) when pulling 2d91fc963ccb531cd509c1b20d9182d05b672903 on thecatwasnot:migration_generator into cb0eea01d23032ee15d2860d7fedae18ec489886 on lotus:master.

#256 has more features & is up to date


Update the ASA Wikipedia page with information on the new release

Describe the solution you'd like
The public Wikipedia page should be updated to include information on the new version, but leaving some information on the original version, too.

Updated to clarify project is current at a Preview-release stage and updated existing text identifying classic 1.0 version of tool for clarity -see Why Attack Surface Analyzer section.


Suggestion: add possibility to process the texts directly

I would like to see a flag that makes it possible to process the texts directly, without going through the menu. I think this would be quite useful to use the tool e.g. in scripts.

Closing this issue, as this is merged and ready to go for the v0.2 release.


Rewrite CIF saving logic.

I put this on hold until confirmed we want to use CIF, see #52
Description

minimize logic, delete unused fields
enforce all tensors are on CPU
delete PdbAtom
fix Het flag for ligans
rename ligand atoms during creation, remove renaming step
fix logic if plddts are not provided
delete PdbExporting

Test plan
Logic was confirmed by diffing before/after CIF outputs on default test example

this PR is stall, closing in favor of #233


Epic: Firefox 68 release

This Epic collects together all of the documentation work that relates to features landing in the Firefox 68 release, which is happening on July 9th.
Acceptance criteria

See the below tasks for their individual acceptance criteria.

This epic can be closed.


Adding passenv for tox -e docs.

Without it, the master docs just show the last version rather than the last commit.
See #880 for context.

@tseaver PTAL

LGTM


Use built-in functions in a custom Engine, without instantiating RecalcEngine

We want to create our own custom Engine instead of using RecalcEngine, but we'd still like to use some of the built-in functions provided in the internal library:
https://github.com/microsoft/Power-Fx/blob/2a82bc542d94d9ffd9e5bc81ce46c30dca53e8dd/src/libraries/Microsoft.PowerFx.Interpreter/RecalcEngine.cs#L51
Can we provide something like ReadOnlySymbolTable.NewDefault() to allow us to obtain the functions without creating RecalcEngine as a throwaway, intermediate resource?
Or even better, perhaps something like SymbolTable.NewDefault(), so we can modify the set without having to call GetMutableCopyOfFunctions first to selectively remove the ones we don't want.
If there's a problem with it because SymbolTable is in Core and the library is in Interpreter... then maybe a CreateNewDefaultSymbolTable() in PowerFxConfigExtensions.cs
Thanks :)

Currently, you need to do something like this:
var mylist = new RecalcEngine().SupportedFunctions.GetMutableCopy();
One challenge is that TexlFunction is still internal, so even if NewDefault was public, what would you pass to it?

Yeah I understand we can just do var mylist = new RecalcEngine().SupportedFunctions.GetMutableCopy();. It just seems unnecessary to create an Engine just to get functions from it.
The method I'm proposing doesn't take in paramaters. The name "default" should imply that it loads the default set of built-in functions. Something like this:

public SymbolTable CreateNewDefaultSymbolTable() {
        var coreFunctions = Library.FunctionList;
        var s = new SymbolTable
        {
            EnumStoreBuilder = new EnumStoreBuilder(),
            DebugName = $"BuiltinFunctions ({coreFunctions.Count()})"
        };

        foreach (var func in coreFunctions)
        {
            s.AddFunction(func);
        }

        return s;
}

Or even...
public static void AddBuiltInSimpleFunctions(this SymbolTable symbolTable) {
        var coreFunctions = Library.SimpleFunctionList; // Get from SimpleFunctionImplementations
        foreach (var func in coreFunctions)
        {
            symbolTable.AddFunction(func);
        }
}

It'll be nice for us because we don't want tabular overloads, at least not yet.
And then if we decide to enable overloads for tables, we can do this
        public static void AddSimpleFunctionTabularOverloadFunctions(this SymbolTable symbolTable)
        {
             var coreFunctions = Library.SimpleFunctionabularOverloadList; // Get from SimpleFunctionTabularOverloadImplementations
             foreach (var func in coreFunctions)
             {
                // maybe some sanity check here to skip adding the overload if the simpleFunction peer doesn't exist in here.
                symbolTable.AddFunction(func);
             }
        }


feat: add option for overwriting indexes

also refactored add method to avoid code duplication
The idea is to be able to set a bookmark for a given keybind, so that i.e:
I use alt+q to go to index 1
I use alt+w to go to index 2
When I want to pin a pane/session to alt+q, I can press prefix+alt+q to store that pane on index 1, which alt+q is bound to.
This avoids manually maintaining the index list when all you want is to put a bookmark for a given index

@Chaitanyabsprip I liked all your suggestions. Also noticed that I hadn't updated the help command.
I made an assumption based on my reply to one of your comments, if that's not what you meant then I'll change it up.

Sorry for the mistakes, I had originally made my changes and tested them, and accidentally restored my changes in git. Then after recreating my changes I thought I had tested them again, but I think I might have forgotten to refresh my tmux config or something.
I pushed new updates now according to your comments @Chaitanyabsprip

Thanks for your contribution and prompt replies and changes. I really appreciate it, hope this tool caters to you better with these changes.


Improve fill_struct_fields assist

The Intellij plugin generates literals for some types when filling struct fields.
If I remember correctly, this is String::new() for strings,  Vec::new() for vectors, 0 / 0.0 for numbers, false for bools.
I like this behaviour since it let's me know the type, and provides a valid initialization.
I checked the code and I'm happy to implement this, but I wanted to discuss  desired semantics first.
Eg, strings could also be implemented as "".to_string() instead of String::new(). Similarly, Vec could be vec![]. This would make it easier to provide your own values.
For other types, we could check if the type implements Default, and use T::default().

See, I have a weird feeling about this, as that would rarely be what you wanted. Assigning unit for each field ensures that you'll get an error, instead of leaving a field be some random default value. But that's just my take on it.

as that would rarely be what you wanted

I also had this concern, theoretically. But I found that (at least for me) it's not an issue.
The big benefit is that you immediately know the required type for many fields. Otherwise, you have to jump back to the field name and trigger the hover to find the type, which costs a lot of time if you don't know the struct.

Guess we just work differently and that's fair :) For cases where I don't already know what types go where, I especially love it filling with unit, as it forces me to go look at the type, and preferably the documentation, so I can actually know what goes in the fields, and not just the types.
In any case, it should probably be behind a configuration flag no matter what, as I could easily see lots of people preferring either way.

The Intellij plugin style of filling works great when writing unit tests where some parts of the fields are irrelevant, so I just want a quick fill

Here's another idea that I think could be useful.  Imagine this code:
struct Person {
    name: String,
    age: u8,
    employed: bool,
}

let name: String = "Alice".to_string();
let age: u8 = 45;

let person = Person {
// <|> run "Fill struct fields" here
};

Today if you use the "Fill struct fields" assist, you'll get this:
let person = Person {
  name: (),
  age: (),
  employed: (),
}

But it would be neat if RA could recognize that there are two field names that have matching local variables of the same type, and auto-fill in the struct like this:
let person = Person {
  name,
  age,
  employed: (),
}


Need to make a Linux installation walkthrough

There's a Mac walkthrough up on the wiki, but my only Linux install is on Heroku, which is not at all like a standard Linux install.
Ideally, somebody who knows what a Linux install should look like would take this, not someone (like me) who'd stumble through and eventually say, "Okay it works now."

I think @cohoe's changes have dealt with this issue. If there's more to do let's open new issues for the leftover bits.


Cannot convert caffe model with "Reshape" layer

When the deploy.prototxt file contains layer of type "Reshape", convertToIR script crashes with error:
Traceback (most recent call last):
  File "/usr/lib/python2.7/runpy.py", line 174, in _run_module_as_main
    "__main__", fname, loader, pkg_name)
  File "/usr/lib/python2.7/runpy.py", line 72, in _run_code
    exec code in run_globals
  File "/usr/local/lib/python2.7/dist-packages/mmdnn/conversion/_script/convertToIR.py", line 159, in <module>
    _main()
  File "/usr/local/lib/python2.7/dist-packages/mmdnn/conversion/_script/convertToIR.py", line 154, in _main
    ret = _convert(args)
  File "/usr/local/lib/python2.7/dist-packages/mmdnn/conversion/_script/convertToIR.py", line 9, in _convert
    transformer = CaffeTransformer(args.network, args.weights, "tensorflow", args.inputShape, phase = args.caffePhase)
  File "/usr/local/lib/python2.7/dist-packages/mmdnn/conversion/caffe/transformer.py", line 308, in __init__
    graph = GraphBuilder(def_path, self.input_shape, self.is_train_proto, phase).build()
  File "/usr/local/lib/python2.7/dist-packages/mmdnn/conversion/caffe/graph.py", line 444, in build
    graph.compute_output_shapes(self.model)
  File "/usr/local/lib/python2.7/dist-packages/mmdnn/conversion/caffe/graph.py", line 265, in compute_output_shapes
    node.output_shape = TensorShape(*NodeKind.compute_output_shape(node))
  File "/usr/local/lib/python2.7/dist-packages/mmdnn/conversion/caffe/graph.py", line 125, in compute_output_shape
    return LAYER_DESCRIPTORS[node.kind](node)
KeyError: None

@kitstar - can we expect these patches in the near feature?

Hi @andrusza2, you have modify some axes in your case manually and it should work.

Hi @andrusza2 . Implemented. Please try the newest code.
Note: when you try to convert IR->DST, please modify the axis parameter of Concat layer for 3 to 1.
For example, in tensorflow model code
I just want to know I should modify which file ?

what does  axis parameter mean?

modify
shallow_q       = tf.concat([pool1_q2_flat, pool1_q3_flat], 3, name = 'shallow_q')
q_concat        = tf.concat([shallow_q_norm, fc8_q_norm], 3, name = 'q_concat')

to
shallow_q       = tf.concat([pool1_q2_flat, pool1_q3_flat], 1, name = 'shallow_q')
q_concat        = tf.concat([shallow_q_norm, fc8_q_norm], 1, name = 'q_concat')

@kitstar @andrusza2
Hi, I think this issue is still there.
Here is the prototext file I am trying to convert.

https://github.com/hszhao/PSPNet/blob/master/evaluation/prototxt/pspnet101_cityscapes_713.prototxt

Here is the command I used to convert Caffemodel to IR

mmtoir -f caffe -n path-to-prototxt -w path-to-caffemodel -o caffe_resnet_IR

Here is my stack trace.

Traceback (most recent call last):
File "/data/bdhanani/Experiments_04/Notebooks/cf_to_tf/mmdnn/bin/mmconvert", line 11, in
sys.exit(_main())
File "/data/bdhanani/Experiments_04/Notebooks/cf_to_tf/mmdnn/lib/python2.7/site-packages/mmdnn/conversion/_script/convert.py", line 95, in _main
ret = convertToIR._convert(ir_args)
File "/data/bdhanani/Experiments_04/Notebooks/cf_to_tf/mmdnn/lib/python2.7/site-packages/mmdnn/conversion/_script/convertToIR.py", line 9, in _convert
transformer = CaffeTransformer(args.network, args.weights, "tensorflow", args.inputShape, phase = args.caffePhase)
File "/data/bdhanani/Experiments_04/Notebooks/cf_to_tf/mmdnn/lib/python2.7/site-packages/mmdnn/conversion/caffe/transformer.py", line 318, in init
graph = GraphBuilder(def_path, self.input_shape, self.is_train_proto, phase).build()
File "/data/bdhanani/Experiments_04/Notebooks/cf_to_tf/mmdnn/lib/python2.7/site-packages/mmdnn/conversion/caffe/graph.py", line 450, in build
graph.compute_output_shapes(self.model)
File "/data/bdhanani/Experiments_04/Notebooks/cf_to_tf/mmdnn/lib/python2.7/site-packages/mmdnn/conversion/caffe/graph.py", line 269, in compute_output_shapes
node.output_shape = TensorShape(*NodeKind.compute_output_shape(node))
File "/data/bdhanani/Experiments_04/Notebooks/cf_to_tf/mmdnn/lib/python2.7/site-packages/mmdnn/conversion/caffe/graph.py", line 129, in compute_output_shape
return LAYER_DESCRIPTORSnode.kind
KeyError: None

Regarding the error, my guess is on these two things

The prototxt file has a layer name called "BN" which is nothing but a "BatchNorm" layer. If I parse the file with the layer name "BatchNorm", I get this error:

check failed: param_size <= num_param_blobs (4 vs. 3) Too many params specified for layer conv1_1_3x3_s2/bn

To tackle this error, I changed the layer definition and reduced batch norm parameter from 4 to 3 which afterwards lead me to this error:

Check failed: target_blobs.size() == source_layer.blobs_size() (3 vs. 4) Incompatible number of blobs for layer conv1_1_3x3_s2/bn

Which makes sense, since my weights has 4 blobs for the batch norm layer: scale, offset, mean and variance.

The prototxt file has a layer name called "Interp" which is custom layer implemented in the Caffe.

I am not sure which of these things from above causing this issue.
I have a small suggestions.

Can the error be more informative than just "Keyerror":None ? Like, which layer is problematic or the root cause of the error.

Please let me know if anyone had the same issue or my approach is wrong.
Thanks,
Bee


🐞Fix the error if the device in masks_to_boxes is not both CPU and CUDA

📝 Description

Addresses https://github.com/openvinotoolkit/anomalib/issues/1830

✨ Changes
Select what type of change your PR is:

[x] 🐞 Bug fix (non-breaking change which fixes an issue)
[ ] 🔨 Refactor (non-breaking change which refactors the code base)
[ ] 🚀 New feature (non-breaking change which adds functionality)
[ ] 💥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] 📚 Documentation update
[ ] 🔒 Security update

✅ Checklist
Before you submit your pull request, please make sure you have completed the following steps:

[x] 📋 I have summarized my changes in the CHANGELOG and followed the guidelines for my type of change (skip for minor changes, documentation updates, and test enhancements).
[x] 📚 I have made the necessary updates to the documentation (if applicable).
[x] 🧪 I have written tests that support my changes and prove that my fix is effective or my feature works (if applicable).

For more information about code review checklists, see the Code Review Checklist.

@samet-akcay, @ashwinvaidya17, @djdameln, PR is ready for a code review. Please take a look 🙂

For some reason the tests are skipped in the CI. I ran it locally


[magisk]magisk hide broken

Latest YAKT make magisk (kitsuen mask or official magisk 27.0) magisk hide broken.Apps added to magisk hide cannot be opened and are stuck in the startup screen or FC (eg. momo or some bank app).
By editing the code I found out  that it is the following code causing the problem, and is able to recover it by deleting the code.
Tweak scheduler to have less Latency
Credits to RedHat & tytydraco & KTweak
log-yakt "Tweaking scheduler to reduce latency"
write "$KL/sched_migration_cost_ns" 5000000
write "$KL/sched_min_granularity_ns" 10000000
write "$KL/sched_wakeup_granularity_ns" 12000000
write "$KL/sched_nr_migrate" 8
log-yakt "Done."
log-yakt ""

Hey @WhiCCX0 ,
Sorry for late reply, that's weird about magisk hide being broken but thanks for the info and i will see what i can do about to fix it,
Thank you!

If you can, use Alpha instead, its author is very skilled, Kistsuen doesn't have much time and skill, and LSPosed and Shamiko don't provide support for Kitsuen


feat(change links): add interested party number change link

:tada: This PR is included in version 2.7.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 2.6.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


run ginkgo test error

Hi guys, I try to run the ginkgo tests, but just failed, and the error log is:
Running Suite: Gqt Suite
========================
Random Seed:<PHONE_NUMBER>
Will run 1 of 1 specs

[d][guardian] spawned /tmp/gexec_artifacts826867777/g190076076/guardian (pid: 25141)
[o][guardian] {"timestamp":"1445845659.613978386","source":"guardian","message":"guardian.runner.command.starting","log_level":0,"data":{"argv":["mountpoint","-q","/tmp/cgroups-1"],"session":"2.1"}}
[o][guardian] {"timestamp":"1445845659.615394592","source":"guardian","message":"guardian.runner.command.failed","log_level":2,"data":{"argv":["mountpoint","-q","/tmp/cgroups-1"],"error":"exit status 1","exit-status":1,"session":"2.1","stderr":"","stdout":"","took":"1.406194ms"}}
[o][guardian] {"timestamp":"1445845659.615459681","source":"guardian","message":"guardian.runner.command.starting","log_level":0,"data":{"argv":["mount","-t","tmpfs","-o","uid=0,gid=0,mode=0755","cgroup","/tmp/cgroups-1"],"session":"2.2"}}
[o][guardian] {"timestamp":"1445845659.621389866","source":"guardian","message":"guardian.runner.command.succeeded","log_level":0,"data":{"argv":["mount","-t","tmpfs","-o","uid=0,gid=0,mode=0755","cgroup","/tmp/cgroups-1"],"exit-status":0,"session":"2.2","took":"5.922984ms"}}
[o][guardian] {"timestamp":"1445845659.621483088","source":"guardian","message":"guardian.setup-cgroup.started","log_level":1,"data":{"path":"/tmp/cgroups-1/cpu","session":"7","type":"cpu"}}
[o][guardian] {"timestamp":"1445845659.621526241","source":"guardian","message":"guardian.runner.command.starting","log_level":0,"data":{"argv":["mountpoint","-q","/tmp/cgroups-1/cpu"],"session":"2.3"}}
[o][guardian] {"timestamp":"1445845659.623045683","source":"guardian","message":"guardian.runner.command.failed","log_level":2,"data":{"argv":["mountpoint","-q","/tmp/cgroups-1/cpu"],"error":"exit status 1","exit-status":1,"session":"2.3","stderr":"","stdout":"","took":"1.508992ms"}}
[o][guardian] {"timestamp":"1445845659.623255491","source":"guardian","message":"guardian.runner.command.starting","log_level":0,"data":{"argv":["mount","-n","-t","cgroup","-o","cpu","cgroup","/tmp/cgroups-1/cpu"],"session":"2.4"}}
[o][guardian] {"timestamp":"1445845659.624535322","source":"guardian","message":"guardian.setup-cgroup.mount-cgroup-cmd.received-data","log_level":1,"data":{"data":"mount: cgroup is already mounted or /tmp/cgroups-1/cpu busy\n","path":"/tmp/cgroups-1/cpu","session":"7.1","type":"cpu"}}
[o][guardian] {"timestamp":"1445845659.624782324","source":"guardian","message":"guardian.setup-cgroup.mount-cgroup-cmd.received-data","log_level":1,"data":{"data":"       cgroup is already mounted on /sys/fs/cgroup/systemd\n       cgroup is already mounted on /sys/fs/cgroup/cpuset\n","path":"/tmp/cgroups-1/cpu","session":"7.1","type":"cpu"}}
[o][guardian] {"timestamp":"1445845659.624815464","source":"guardian","message":"guardian.setup-cgroup.mount-cgroup-cmd.received-data","log_level":1,"data":{"data":"       cgroup is already mounted on /sys/fs/cgroup/cpu,cpuacct\n       cgroup is already mounted on /sys/fs/cgroup/memory\n       cgroup is already mounted on /sys/fs/cgroup/devices\n       cgroup is already mounted on /sys/fs/cgroup/freezer\n       cgroup is already mounted on /sys/fs/cgroup/net_cls\n       cgroup is already mounted on /sys/fs/cgroup/blkio\n       cgroup is already mounted on /sys/fs/cgroup/perf_event\n       cgroup is already mounted on /sys/fs/cgroup/hugetlb\n       cgroup is already mounted on /tmp/cgroups-1\n","path":"/tmp/cgroups-1/cpu","session":"7.1","type":"cpu"}}
[o][guardian] {"timestamp":"1445845659.624980450","source":"guardian","message":"guardian.runner.command.failed","log_level":2,"data":{"argv":["mount","-n","-t","cgroup","-o","cpu","cgroup","/tmp/cgroups-1/cpu"],"error":"exit status 32","exit-status":32,"session":"2.4","stderr":"mount: cgroup is already mounted or /tmp/cgroups-1/cpu busy\n       cgroup is already mounted on /sys/fs/cgroup/systemd\n       cgroup is already mounted on /sys/fs/cgroup/cpuset\n       cgroup is already mounted on /sys/fs/cgroup/cpu,cpuacct\n       cgroup is already mounted on /sys/fs/cgroup/memory\n       cgroup is already mounted on /sys/fs/cgroup/devices\n       cgroup is already mounted on /sys/fs/cgroup/freezer\n       cgroup is already mounted on /sys/fs/cgroup/net_cls\n       cgroup is already mounted on /sys/fs/cgroup/blkio\n       cgroup is already mounted on /sys/fs/cgroup/perf_event\n       cgroup is already mounted on /sys/fs/cgroup/hugetlb\n       cgroup is already mounted on /tmp/cgroups-1\n","stdout":"","took":"1.713413ms"}}
[o][guardian] {"timestamp":"1445845659.625034809","source":"guardian","message":"guardian.setup-cgroup.mount-cgroup-failed","log_level":2,"data":{"error":"exit status 32","path":"/tmp/cgroups-1/cpu","session":"7","type":"cpu"}}
[o][guardian] {"timestamp":"1445845659.625054836","source":"guardian","message":"guardian.setup-cgroup.finished","log_level":1,"data":{"path":"/tmp/cgroups-1/cpu","session":"7","type":"cpu"}}
[o][guardian] {"timestamp":"1445845659.625111818","source":"guardian","message":"guardian.failed-to-start-server","log_level":3,"data":{"error":"exit status 32","trace":"goroutine 1 [running]:\ngithub.com/pivotal-golang/lager.(*logger).Fatal(0xc8200f60c0, 0x940ef0, 0x16, 0x7f716ab35f08, 0xc8200fc3e0, 0x0, 0x0, 0x0)\n\t/home/tony/Documents/go/src/github.com/pivotal-golang/lager/logger.go:131 +0xc5\nmain.main()\n\t/home/tony/Documents/go/src/github.com/cloudfoundry-incubator/guardian/cmd/guardian/main.go:228 +0x8c2\n"}}
[e][guardian] panic: exit status 32
[e][guardian]
[e][guardian] goroutine 1 [running]:
[e][guardian] github.com/pivotal-golang/lager.(*logger).Fatal(0xc8200f60c0, 0x940ef0, 0x16, 0x7f716ab35f08, 0xc8200fc3e0, 0x0, 0x0, 0x0)
[e][guardian] 	/home/tony/Documents/go/src/github.com/pivotal-golang/lager/logger.go:152 +0x698
[e][guardian] main.main()
[e][guardian] 	/home/tony/Documents/go/src/github.com/cloudfoundry-incubator/guardian/cmd/guardian/main.go:228 +0x8c2
[e][guardian]
[e][guardian] goroutine 17 [syscall, locked to thread]:
[e][guardian] runtime.goexit()
[e][guardian] 	/usr/local/go/src/runtime/asm_amd64.s:1696 +0x1
[e][guardian]
[e][guardian] goroutine 5 [syscall]:
[e][guardian] os/signal.loop()
[e][guardian] 	/usr/local/go/src/os/signal/signal_unix.go:22 +0x18
[e][guardian] created by os/signal.init.1
[e][guardian] 	/usr/local/go/src/os/signal/signal_unix.go:28 +0x37
• Failure in Spec Setup (BeforeEach) [3.639 seconds]
Net
/home/tony/Documents/go/src/github.com/cloudfoundry-incubator/guardian/gqt/net_test.go:120
  should have a (dynamically assigned) IP address [BeforeEach]
  /home/tony/Documents/go/src/github.com/cloudfoundry-incubator/guardian/gqt/net_test.go:63

  Expected error:
      <*url.Error | 0xc820212b10>: {
          Op: "Post",
          URL: "http://api/containers",
          Err: {
              Op: "dial",
              Net: "unix",
              Source: nil,
              Addr: {
                  Name: "/tmp/garden_1.sock",
                  Net: "unix",
              },
              Err: {Syscall: "connect", Err: 0x2},
          },
      }
      Post http://api/containers: dial unix /tmp/garden_1.sock: connect: no such file or directory
  not to have occurred

  /home/tony/Documents/go/src/github.com/cloudfoundry-incubator/guardian/gqt/net_test.go:29
------------------------------

Summarizing 1 Failure:

[Fail] Net [BeforeEach] should have a (dynamically assigned) IP address
/home/tony/Documents/go/src/github.com/cloudfoundry-incubator/guardian/gqt/net_test.go:29

Ran 1 of 1 Specs in 3.639 seconds
FAIL! -- 0 Passed | 1 Failed | 0 Pending | 0 Skipped --- FAIL: TestGqt (3.64s)
FAIL

Ginkgo ran 1 suite in 5.036839752s
Test Suite Failed

even though I run these test from scratch, I get this error, I don't know why cgroup is already mounter.
If i run this command: cat /proc/mounts | grep cgroup, I will get such output:
tmpfs /sys/fs/cgroup tmpfs rw,seclabel,nosuid,nodev,noexec,mode=755 0 0
cgroup /sys/fs/cgroup/systemd cgroup rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/usr/lib/systemd/systemd-cgroups-agent,name=systemd 0 0
cgroup /sys/fs/cgroup/cpuset cgroup rw,nosuid,nodev,noexec,relatime,cpuset 0 0
cgroup /sys/fs/cgroup/cpu,cpuacct cgroup rw,nosuid,nodev,noexec,relatime,cpuacct,cpu 0 0
cgroup /sys/fs/cgroup/memory cgroup rw,nosuid,nodev,noexec,relatime,memory 0 0
cgroup /sys/fs/cgroup/devices cgroup rw,nosuid,nodev,noexec,relatime,devices 0 0
cgroup /sys/fs/cgroup/freezer cgroup rw,nosuid,nodev,noexec,relatime,freezer 0 0
cgroup /sys/fs/cgroup/net_cls cgroup rw,nosuid,nodev,noexec,relatime,net_cls 0 0
cgroup /sys/fs/cgroup/blkio cgroup rw,nosuid,nodev,noexec,relatime,blkio 0 0
cgroup /sys/fs/cgroup/perf_event cgroup rw,nosuid,nodev,noexec,relatime,perf_event 0 0
cgroup /sys/fs/cgroup/hugetlb cgroup rw,nosuid,nodev,noexec,relatime,hugetlb 0 0
cgroup /tmp/cgroups-1 tmpfs rw,seclabel,relatime,mode=755 0 0

I did try to run this command: umount /tmp/cgroup-1, but useless. I am wondering how can I run this test case correctly.

I think I see what's happening. We all develop on mac, so we only really run these linux-only tests inside concourse builds. Concourse runs builds inside garden-linux containers, and these containers don't automatically mount any cgroups, but I think you're running the tests on a real linux host which already has cgroups mounted (probably because it's a modern linux with systemd enabled?).
The workaround is to run these tests using concourse like we do (follow the instructions on the concourse repo to set up a local concourse/lite environment and then you can use ./script/test inside guardian-release to do this). The real solution, of course, is we should make sure these tests cope with running inside an environment that already has cgroups mounted. I created a story here to do this.
Thanks again!

@julz Thanks very much. I will try that on my MBP.

Hi there!
We use Pivotal Tracker to provide visibility into what our team is working on. A story for this issue has been automatically created.
The current status is as follows:

[ ] #106740184 GQT tests should work when run on 'real' linux (not a container)

This comment, as well as the labels on the issue, will be automatically updated as the status in Tracker changes.

@AdoHe We fixed the tests. You should install aufs in order to run the tests as well. I updated the README to illustrate exact steps.


Remove version: BellSoft.LibericaJDK.16 version <IP_ADDRESS>

[Automated] It returns code over 400 in all urls
Microsoft Reviewers: Open in CodeFlow

Close with reason: Package still available.;


Make the code in chapter 06 compile

I did this manually, which is error prone. I don't know if adding skeptic to the mix makes any sense.  At first glance, it appears skeptic might be able to prevent bugs from creeping in, but I've never used it before and haven't allocated the time to look into it further.

Thanks for these fixes.
Just for your (and any future readers) information:

I've actually installed mdbook-keeper which is effectively a fork of Skeptic that I wrote, but specifically integrates into mdbook. This means that where examples can be tested, they hopefully are being tested.
This example unfortunately can't be tested right now, because the point of the example is: "hey, you can't just write an impl without the <'a> or <'_> being there". This example would give a compilation error, and should do so. I guess we could build a mechanism for saying "there should only be these error codes", but that'd require some development of mdbook-keeper which I don't have time for right now. Perhaps a good project though...

There might be a better way of achieving the educational goal without so much untested code, would be keen to hear your perspective. I'll leave this un-merged until you have a chance to think over it, in case there is a better approach (and just in case I'm missing something obvious).

Going to merge this now so I can do formatting. Please do let me know if you have further thoughts though :)


How to train the model with the image2image mode

Thank for your code.
I want to train this model with my dataset, and could i use this model for my image, I have a dataset with pairs of original image and noisy image, noisy images have some kind of noises like motion blur, salt and pepper noise and exposure noise for example.

Hi,
In this repo, only gaussian noise is added progressively. It seems that based on your requirement, this paper, might be exactly what you are looking for.  They have an implementation online - https://github.com/arpitbansal297/Cold-Diffusion-Models , so the deblurring diffusion(with some modifications) should fit your use case.

oh thank you, i will try it


Gamee question

Hi, is it possible to make log in to Gamee by using Open App button that is located on the left from message field?
For me this is essential because, for whatever reason, bot communicates with me in different languages and doesn't use English.
I've tried to change telegram language and os language and region, but it still doesn't use English. There is also no language setting in the bot, so I guess it's impossible to change communication language

Hi Gamee, is currently not working anyway after they blocked access via Telegram web. If we are able to restore it, we'll look at the login button.
Thanks


specialize arithmetic operators for native float types

Write specialized versions of arithmetic operators for native float type e.g. operator+(cpp_quad_float<double>, double)
Question: Should we also specialize arithmetic operators for cpp_double_float inside cpp_quad_float (e.g. operator+(cpp_quad_float, cpp_double_float)?

specialize arithmetic operators for ...

I think the best thing to do is to specialize eval_add(), eval_sub(), eval_mul(), eval_div(). If memory serves, there exists the possibility within the backend boilerplate code to find specializations of these eval_- functions for various built-in types. A classic is multiplication with integral value.
In this case (of double float and quad float), add/sub/mul/div could all benefit from specializations with built-in floating-point types, as long as the built in type is less than or as wide as the constituent parts of the double-float or quad-float compound type.
Cc: @sinandredemption


Op3dTensorGeneric kernel improvements

Simplified and significantly improved speed (up to 250+ times on gfx9xx and 100+ times on gfx10xx) of Op3dTensorGeneric kernel. There are few cases where it can be up to 20% slower than initial kernel, but most of them are small tensors - less than 8K elements in total.

perf.xlsx
Perf measurements

@JehandadKhan @junliume is "no new opencl kernels" is a strict rule or we could proceed with this PR and transfer to HIP in a separate PR? Work on this one began before the announcement.

@CAHEK7 please provide more detailed descriptions in the top comment regarding verification and performance changes if PR could possibly affect one or another. Few examples #1927, #1747. Tables shown by @shurale-nkn  in this comment  are also a good example of what would be nice to see in original description.

@Kirpich30000, thanks for the examples, I will update this pull request once we decide to proceed with opencl.
As about the limitations - for MI210 the case with full B tensor (case x x x) is always faster for packed version (+15% is the worst case) and at least has the same performance for incredible strided access (4KB strides for dimensions of 2-3 elements). Why would we ignore such kind of performance gain?  The same for squashed B tensor (case 1 1 1) - at least it has the same performance except a few cases with 3-5% perf drop and one of the cases is outside of 8k boundary.
As I mentioned before - most of the small tensors performance drops can be mitigated by increasing number of active groups and decreasing number of threads per group. Since I utilize all the threads from the group, small tensors may use just a few wraps of one group and may underutilize GPU - previous version of the kernel used just one thread of the group and much more groups instead and small tensors were distributed by larger number of wraps\CUs. So we can mimic the same behavior, replace old kernel completely significantly simplify the host code and minimize number of kernels to support (for example to rewrite kernels to HIP).

A few words about any "average" metrics from this PR - currently they all are highly biased to lower-sized tensors since tensor sizes grow in some kind of log2 scale. If I choose different datasets, for example evenly distributed tensors sizes, I will get completely different picture in terms of "average", "median" and all the percentages from this comment and from my initial description.


regex issue

In MacVim, the regex  "[^"]{-}" seems to ignore the "minimal" aspect of the match, and instead matches maximally, while in plain vim this is not the case.  So e.g.
"hi" something "there"
will match the entire string in MacVim, but in standard vim only "hi" and "there" are matched.  This is most noticeable when "hls" is on.

Please report in https://github.com/vim/vim/issues for Vim issues.

@ronaaron said that plain Vim does not exhibit the incorrect behavior, while MacVim does.  That means the place to report it is right here.

body p { margin-bottom: 0cm; margin-top: 0pt; }

Yes, it happens on MacVim but not on standard vim.

On 09/02/2016 00:57, chdiza wrote:

  @ronaaron said that plain Vim does
    not exhibit the incorrect behavior, while MacVim does. That
    means the place to report it is right here.
  —
    Reply to this email directly or view
      it on GitHub.

--

      Ron Aaron, CTO
      Aaron High-Tech, Ltd.
      +1<PHONE_NUMBER>
      +972 52.652.5543
      GPG Key: 91F92EB8

@ronaaron Do you actually check https://github.com/vim/vim ? What is the version of "standard vim"?

Yes.
I use vim (the most recent version built from the vim repo) every day.
I also use MacVim (also the most recent version) every day.  So I can
categorically state that the behavior is different.
On 09/02/2016 06:47, Kazuki Sakamoto wrote:

@ronaaron https://github.com/ronaaron Do you actually check
https://github.com/vim/vim ? What is the version of "standard vim"?
—
Reply to this email directly or view it on GitHub
https://github.com/macvim-dev/macvim/issues/239#issuecomment-181709591.

@ronaaron What is the version of vim?

7.4.1290, same as the MacVim I'm running right now.  Just like I said
before.
On 09/02/2016 06:58, Kazuki Sakamoto wrote:

@ronaaron https://github.com/ronaaron What is the version of vim?
—
Reply to this email directly or view it on GitHub
https://github.com/macvim-dev/macvim/issues/239#issuecomment-181711031.

@ronaaron Can you create a vim script for reproducing the issue?

No.  The "matchstr()" function works correctly, but doing the same from
normal mode "/" does not
Here's what I tried w/ a script:
let m1 = matchstr('"one" "two"', '"[^"]{-}"')
if (m1 == '"one"')
echo "OK"
else
echo "BAD: " . m1
endif
On 02/09/2016 07:33, Kazuki Sakamoto wrote:

@ronaaron https://github.com/ronaaron Can you create a vim script
for reproducing the issue?
—
Reply to this email directly or view it on GitHub
https://github.com/macvim-dev/macvim/issues/239#issuecomment-181716687.

@ronaaron I can't repro the issue.
https://github.com/macvim-dev/macvim/wiki/Troubleshooting
$ killall MacVim
$ killall Vim
$ defaults delete org.vim.MacVim
$ /Applications/MacVim.app/Contents/MacOS/Vim -g -u NONE -U NONE
Can you explain the exact detail how to reproduce the issue from here.

OK.  It seems that the actual problem was "cpoptions=Bes" on my MacVim
setup.
Omitting the 'c' from there caused the problem.
On 02/09/2016 08:11, Kazuki Sakamoto wrote:

@ronaaron https://github.com/ronaaron I can't repro the issue.
https://github.com/macvim-dev/macvim/wiki/Troubleshooting
$ killall MacVim
$ killall Vim
$ defaults delete org.vim.MacVim
$ /Applications/MacVim.app/Contents/MacOS/Vim -g -u NONE -U NONE
Can you explain the exact detail how to reproduce the issue from here.
—
Reply to this email directly or view it on GitHub
https://github.com/macvim-dev/macvim/issues/239#issuecomment-181726011.


Bypassing max jobs by cycling protection request

It currently is technically possible to join the max jobs, but to quit and quickly join another, then go back ~ we noticed a slight increase in this, sometimes even with mods that auto switch as they switch their tool or block breaking. Something we wish to discourage. And yes, there's a "loss" you can configure if you switch jobs.
But, would it be possible (i couldn't find it) to have a cooldown or timeout setting in generalConfig.yml that would inform the player: Sorry, you can only leave and rejoin a job once per day (or whatever is technically logical to do to achieve this)
max jobs: 1
Player> join miner

joined miner

Player> leave miner

left miner

Player> join builder

joined builder

Player> leave builder

left builder

Player> join miner

sorry, you left miner earlier today, you can switch jobs once per day

Player> join builder

sorry, you left miner earlier today, you can switch jobs once per day

Player> join fisherman

join fisherman

  # Defines how often in seconds player can rejoin this job. Can be bypassed with jobs.rejoinbypass
  rejoinCooldown: 10

This can be found in _EXAMPLE.yml file and allows to set timer on rejoining jobs top prevent this job jumping. And for good practice i would recommend to keep exp loss when leaving job to atleast like 10% to discourage such actions but still keep it for those who wants to do it at some point.


minimal support for protected / member only content

We're close to rolling out member only content, which will be tagged with c:members-only tag on the claim. We should filter this in all categories outside of following/wild west as part of "not tags".  It should be shown on following/channel pages.
For claims with c:members-only, refer users to odysee.com to sign up for memberships to view content. If we want, we can check if they are authorized to view, and then we can use the existing get call to play it back via URL signed domains.
To check if they have access to something, use this call: https://api.odysee.com/membership_perk/check
Pass: auth_token
claim_id
type: "Exclusive content" for static, or "Exclusive livestreams" for lives

Few questions:

Are there member only livestreams?
Member only content should be filtered from search, right?
What's URL signed domains?
Should there be some indication that it's member only before going to the file view page?


[SPARK-10807][SPARKR] Added as.data.frame as a synonym for collect

Created method as.data.frame as a synonym for collect().

Can one of the admins verify this patch?

Jenkins, ok to test

Merged build triggered.

Merged build started.

Test build #42981 has started for   PR 8908 at commit e9e34b5.

Test build #42981 has finished for   PR 8908 at commit e9e34b5.

This patch fails R style tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42981/
Test FAILed.

How can I check the style in my local environment? I ran the unit tests but got no issues. Tried the link below, but it's only for Python and Scala: https://cwiki.apache.org/confluence/display/SPARK/Spark+Code+Style+Guide,

You can run dev/lint-r in your tree and it should do the style checks. Also the jenkins log has the error at the end
R/DataFrame.R:1867:69: style: Trailing whitespace is superfluous.
setMethod(f = "as.data.frame", signature = "DataFrame", definition =

Yeah, I saw that one. Thank you so much! I have fixed it, and ran dev/lint-r on my local. It should be good now :)

Merged build triggered.

Merged build started.

Test build #42989 has started for   PR 8908 at commit cee871c.

Test build #42989 has finished for   PR 8908 at commit cee871c.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42989/
Test PASSed.

Thanks @olarayej -- I just had a couple of minor style comments
One more thing is that it will be good to add a unit test for this. You could just add a test case to some of the existing tests at https://github.com/apache/spark/blob/922338812c03eba43f2f1a6c414d1b6b049811cf/R/pkg/inst/tests/test_sparkSQL.R#L215

Also could you change the PR title to [SPARK-10807][SPARKR] ? This matches the format we use for all PRs -- https://cwiki.apache.org/confluence/display/SPARK/Contributing+to+Spark#ContributingtoSpark-PullRequest has more information

@olarayej Sorry I wasn't clear the last time around but the title should be [SPARK-10807][SPARKR] Added as.data.frame as a synonym for collect

Merged build triggered.

Merged build started.

@shivaram Thanks a lot for your comments! I have addressed them.
-Oscar

Test build #43069 has started for   PR 8908 at commit de6d164.

Merged build triggered.

Merged build started.

Test build #43072 has started for   PR 8908 at commit a346cc6.

Test build #43072 has finished for   PR 8908 at commit a346cc6.

This patch fails MiMa tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43072/
Test FAILed.

Jenkins, retest this please

Merged build triggered.

Merged build started.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43075/
Test FAILed.

Test build #43069 has finished for   PR 8908 at commit de6d164.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43069/
Test FAILed.

Jenkins, retest this please

Merged build triggered.

Merged build started.

Test build #43086 has started for   PR 8908 at commit a346cc6.

Test build #43086 has finished for   PR 8908 at commit a346cc6.

This patch fails MiMa tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43086/
Test FAILed.

Jenkins, retest this please

Merged build triggered.

Merged build started.

Test build #43097 has started for   PR 8908 at commit a346cc6.

Test build #43097 has finished for   PR 8908 at commit a346cc6.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43097/
Test FAILed.

Merged build finished. Test FAILed.

@shaneknapp The log has a strange error I haven't seen so far
/home/jenkins/workspace/SparkPullRequestBuilder/build/sbt -Pyarn -Phadoop-2.3 -Dhadoop.version=2.3.0 -Phive -Pkinesis-asl -Phive-thriftserver test ; received return code 143

Any ideas if this is related to the recent Jenkins issues ?

huh, i haven't seen that error message either.  when i run that command locally (same box, same working dir, jenkins user), it works.  i'll try and keep an eye out for failures like this, but please let me know if you see something like this again.

@shivaram @shaneknapp: any suggestions? I did double check the unit tests work fine on my environment. Thanks!

Jenkins, retest this please

Merged build triggered.

Merged build started.

Test build #43106 has started for   PR 8908 at commit a346cc6.

Test build #43106 has finished for   PR 8908 at commit a346cc6.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43106/
Test FAILed.

@shaneknapp Looks like the same error again.
@olarayej Could you remove the change to .gitignore in this PR ? Because of the way our tests are setup only changes in R/ will only run SparkR unit tests which should pass without a problem I think

i'll take a closer look tomorrow, @shivaram.
On Tue, Sep 29, 2015 at 8:41 PM, Shivaram Venkataraman <
<EMAIL_ADDRESS>wrote:

@shaneknapp https://github.com/shaneknapp Looks like the same error
again.
@olarayej https://github.com/olarayej Could you remove the change to
.gitignore in this PR ? Because of the way our tests are setup only
changes in R/ will only run SparkR unit tests which should pass without a
problem I think
—
Reply to this email directly or view it on GitHub
https://github.com/apache/spark/pull/8908#issuecomment-144273647.

@shivaram I have removed the changes to .gitignore. My apologies, I didn't intentionally change this file. Thanks!

Merged build triggered.

Merged build started.

Test build #43136 has started for   PR 8908 at commit 6c4dcbc.

Test build #43136 has finished for   PR 8908 at commit 6c4dcbc.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43136/
Test PASSed.

Awesome! :-)

Thanks @olarayej LGTM. Merging this


Build broken by recent commit updating llvm-raw

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

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

Describe the problem
Build errors out with
INFO: Repository 'llvm-raw' used the following cache hits instead of downloading the corresponding file.

Hash 'd68b5fa9b851cc0b8a5f84f7659404380f477efc859f21951bc3554476047245' for https://storage.googleapis.com/mirror.tensorflow.org/github.com/llvm/llvm-project/archive/ec0e4545caa18e0b55e4f25db913a10a4782fdc3.tar.gz
If the definition of 'llvm-raw' was updated, verify that the hashes were also updated.
ERROR: An error occurred during the fetch of repository 'llvm-raw':
Traceback (most recent call last):
File "/home/andrew/src/tensorflow/third_party/repo.bzl", line 75, column 30, in _tf_http_archive_impl
ctx.patch(patch_file, strip = 1)
Error in patch: Error applying patch /home/andrew/src/tensorflow/third_party/llvm/Bazel-update-build-files-for.patch: Incorrect Chunk: the chunk content doesn't match the target
Original Position: 840

Original Content:
copts = llvm_copts,
deps = [
":Core",
":Support",
":config",
],
Revised Content:
copts = llvm_copts,
deps = [
":Core",
":DebugInfoDWARF",
":Support",
":config",
],
ERROR: no such package '@llvm-raw//utils/bazel': Error applying patch /home/andrew/src/tensorflow/third_party/llvm/Bazel-update-build-files-for.patch: Incorrect Chunk: the chunk content doesn't match the target
Original Position: 840
Original Content:
copts = llvm_copts,
deps = [
":Core",
":Support",
":config",
],
Revised Content:
copts = llvm_copts,
deps = [
":Core",
":DebugInfoDWARF",
":Support",
":config",
],
INFO: Elapsed time: 64.208s
INFO: 0 processes.
FAILED: Build did NOT complete successfully (0 packages loaded)
FAILED: Build did NOT complete successfully (0 packages loaded)
Provide the exact sequence of commands / steps that you executed before running into the problem
bazel test --test_timeout=300,500,-1,-1 --flaky_test_attempts=3 --test_output=all --cache_test_results=no --remote_http_cache=""  --remote_cache_proxy="" --noremote_accept_cached --config=nonccl --build_tag_filters=-no_oss,-oss_serial,-gpu,-tpu,-benchmark-test,-v1only --test_tag_filters=-no_oss,-oss_serial,-gpu,-tpu,-benchmark-test,-v1only --copt=-ffp-contract=off --verbose_failures -- //tensorflow/core/ir/...
Any other info / logs
Include any logs or source code that would be helpful to diagnose the problem. If including tracebacks, please include the full traceback. Large logs and files should be attached.
This commit seems to be implicated
https://github.com/tensorflow/tensorflow/commit/403b4b19f9d143b4868d8a822c325acb6fdd8704

@cfRod @nSircombe

Build gets past the failure point at the commit just prior to the one mentioned above.
git checkout 8ae9fff651a617ed102fe51fbea2cdb81e51e1bd

I dont understand ？fixed？


[Feature] Add more metadata fields

Here are some more fields that would be great to add support for:
tag.trackArtist, -- added via https://github.com/erikas-taroza/audiotags/pull/10
tag.albumArtist -- added via https://github.com/erikas-taroza/audiotags/pull/10
tag.producer,
tag.originalReleaseDate,
tag.recordingDate,
tag.trackNumber -- already supported
tag.trackTotal -- already supported
tag.discNumber
tag.discTotal
tag.language
tag.lyrics

All of these fields are available in lofty.
I know you already have the tag.artist field, but having both track artist and album artist fields would be great. I believe you recently added tag.trackNumber, from my previous feature request, so feel free to ignore that.
Thanks again Erikas!
PS: I've been working on setting up my dev environment, so I may chip in to adding support for some of these fields, as it would be a good first assignment in familiarizing myself with your codebase.
Cheers :)

PS: I've been working on setting up my dev environment, so I may chip in to adding support for some of these fields, as it would be a good first assignment in familiarizing myself with your codebase.

These changes are pretty simple to feel free to PR. For recordingDate and originalReleaseDate, you will have to use chrono to handle dates in Rust.

First PR ready for review (implements two of my requested fields) https://github.com/erikas-taroza/audiotags/pull/10


The documentation could make it clear why Substring is preferred over String

The earlier videos make this quite clear but for those who haven't seen those they might not understand why the [...] is used and why sometimes the argument to parse is inout and sometimes not, and why the compiler will present errors for some parsers if you try to pass them a String (they only have Substring and utf8 implementations).
This lack of understanding will increase frustration for new users of this package and reduce adoption as a result.
#111 is a specific instance of an actual typo on this topic.

@haikusw We've been revamping our docs and now have a dedicated article about string abstractions here: https://pointfreeco.github.io/swift-parsing/main/documentation/parsing/stringabstractions
Does this address your concerns enough to close this issue out?

Sounds promising!  I'll take a look soon and update this as appropriate.

@haikusw Thanks!

Looks great.  I made a PR with a couple of very minor changes.


Type parameter inference not working with union types

TypeScript Version:  2.7.0-dev.20171031
Code
// generic interface for a visitor, all visitor methods return the same type
interface IVisitor<T> {
    visitThing(thing: Thing): T;
    visitOtherThing(other: OtherThing): T;
}

// "visitee" classes
class Thing {
    other: OtherThing;

    visit<T>(visitor: IVisitor<T>) {
        return visitor.visitThing(this);
    }
}

class OtherThing {
    visit<T>(visitor: IVisitor<T>) {
        return visitor.visitOtherThing(this);
    }
}

// an implementation of the above interface
// visitor methods can return void or number
class SomeVisitor implements IVisitor<number | void> {
    visitThing(thing: Thing) {
        // type parameter of 'thing.other.visit' resolves to 'void', not 'number | void'
        // cast to 'number' fails
        const result = thing.other.visit(this) as number;
    }

    visitOtherThing(other: OtherThing) {
        return 4;
    }
}

Expected behavior:
I have a simple setup for the visitor pattern, but with a generic interface so that I can create visitors that return different types. This works perfectly if I implement the interface with a single type.
However, I have a situation where I have two types of "visitee" classes for a particular visitor. One type will return a number, and the other will return void. So I decided I would specify number | void as the return type of the visitor. I am fine with having to do a cast when calling a number visitee from a void visitee, as I do above.
I would expect that when I call thing.other.visit(this), the type parameter for visit<T>() would use the type of SomeVisitor, which is IVisitor<number | void>, and T would infer to number | void.
Actual behavior:
However, for some reason, the type for T is inferred to be void, which leads me to believe that some other mechanism is being used to determine the type parameter. Since number is not assignable to void, the cast to number fails.
I can work around this by specifying the type parameter explicitly:
const result = thing.other.visit<number | void>(this) as number;

or casting this to the expected visitor type:
const result = thing.other.visit(this as IVisitor<number | void>) as number;

but I believe that TypeScript should be able to correctly infer the type given the information that it has.

This is one of the pitfalls of a structural type system -- the implements clause doesn't determine the type, the actual method types do. So you can fix your error by declaring explicit return types on visitThing and visitOtherThing to return number | void.

Oh yea, sure enough. If I put an explicit return type of number | void on at least one method in SomeVisitor, then it infers correctly.
Still seems weird though...

Basically, the implements clause asserts type compatibility but doesn't actually affect the type of the class. Related: #10077

duplicate of https://github.com/Microsoft/TypeScript/issues/1373


Use a template file for the static html code

Currently the whole html code is inside the python script. This is very unwieldy and ugly.
We should place the whole html code inside a template.html file and add some placeholders which will be filled by the python script.
e.g.:
https://stackoverflow.com/questions/11646948/simple-html-template-in-python
I think in the first place a simple template string replacement should be enough.

All the static html code is now inside template/main.html
This makes the Python code much clearer and you can easily redesign the html file without having to understand python code.


OoTR Compliance Update: Water Temple

This updates Water Temple's logic, though it required some significant creativity. I honestly cannot 100% promise this is an exact match for OoTR, but I am reasonably sure it is logically sound. The key point is that water level changing and whether you can guarantee access to any given water level is just a bit picky, and some of the logic requirements (especially for water level high) are kinda weird and don't have the most obvious tie-in to how you would physically navigate the dungeon. I also fixed some issues like accounting for Dragon Spiral access via the river and fixing the requirements in the Boss Key loop in general.

👍


BUG: More robust FASTQ validation

Fixes #148
Pair-programmed with @ebolyen

merge conflicts 😿

Thanks @jairideout! I have addressed your recommendations in a squash commit 🎃. I also fixed the merge conflict.


Add basic public API benchmarks on *.mt source files.

These are some basic benchmarks for normalize, typeOf and the Eq instance, so only the API that Core.hs exports.
The benchmarks are done by parsing recursive.mt found in the tutorial and factorial.mt.
If it's all ok and before moving forward with adding new benchmarks I'd like it if we can discuss more about:

Moving Morte.Core into something like Morte.Internal.Core where everything is exported so that we cand benchmark and test every component,
and make Morte.Core just reexport what should pe public API. Or anything that allows us to do this.
Writing an benchmarking on *.mt is not really feasible for all kinds of benchmarks. We should be able to generate expressions in a deterministic manner and what
I'm interested in this case is at what level of control do you think we should do it ? Should we be able to control all of depth, free variables, number of Pi terms, Lambda terms, applications      parameters ? I'm wondering if you think this would be overkill and time better spent on something else.

I would be fine with just exporting the remaining functions.  There's no real reason that they need to be hidden and they could be useful for downstream libraries.
I think you already covered the most important cases to optimize.  If we get those two programs efficient then pretty much everything else will be efficient as well.
We probably should have a way to generate Arbitrary closed expressions that are well-typed, but mainly for testing purposes to assert properties like:
normalize . normalize = normalize

typeOf . normalize = typeOf

Also, there you can more reliably embed the test Morte files in the benchmarks by using Cabal's "Data-files" features, which lets you embed the Morte code in the cabal package.  This will ensure that people can benchmark the code using cabal directly and without having to check out the repository.
The way you do this is you add a Data-files clause to the .cabal file, like this:
Data-Dir: benchmark/src
Data-Files:
    recursive.mt,
    factorial.mt

... and then when you need the file path in the benchmark code you would write:
import Paths_morte (getDataFileName)

... and then you can use getDataFileName to locate where cabal installed the files, like this:
-- getDataFileName :: String -> IO String

readMtFile filename = do
    path <- getDataFileName filename
    mtFile <- readFile path
    return (filename, mtFile)

The path that getDataFileName will give me is relative to the install location and does no seem to work when doing just cabal-bench, I will look into it some more.

Made the changes.
In order to have the sources in the appropriate directory you have to now run cabal install before cabal bench.

Thank you!  I appreciate the help


kubeletConfigurations endpoint returns error if the --config kubelet parameter is not used

I'm running Kubescape with --enable-host-scan against the Azure AKS cluster default node image and getting error:
{"level":"error","ts":"2022-06-30T13:10:37.3024482Z","msg":"Request failed","method":"GET","requestURI":"/kubeletConfigurations","remoteAddr":"<IP_ADDRESS>:33890","requestStartTime":"2022-06-30T13:10:37.046321419Z","Request body":"","HTTP status":500,"Response size":104,"Response body":"failed to sense kubelet conf: in SenseKubeletConfigurations failed to find kubelet config File location\n"}
[negroni] 2022-06-30T13:10:37Z | 500 |   256.705187ms | ...westeurope.azmk8s.io:443 | GET /kubeletConfigurations

I understand that this is because the --config parameter was not used when running the kubelet process. But as this parameter is optional and all the other parameters can override configuration from this file, other parameters should be also considered in this endpoint and merged with the configuration file (if present).

Hi @psivak , thanks for pointing this out.
You are totally right.
This is why we are taking the entire kubelet command line, as you can see here: sense kubelet cmd.
In addition, many (135) of the kubelete command line arguments are deprecated.
Please let us know if you have any other issue or something you think we should improve.


cleaned up tests

fixed codestyle
avoid manual setup/tearDown calls
no longer initializing classes and calling the static methods as if they're normal methods
calling BitcoinLib::setMagicBytes in every setup so that it's always what we expect it to bit
fixed ElectrumTest
using BITCOINLIB_EXTENSIVE_TESTING on more places to make the tests during development as fast as possible, while travis still does the heavy lifting
added BITCOINLIB_RPC_* ENV vars to configure running against RPC
removed autoload.php from the test files, using phpunit bootstrap file option

I tried adding code coverage checking, but it requires xdebug, which makes the tests take 11 minutes instead of 1 minute so not doing that for now since @afk11 is playing around with Scrutinizer so I'll wait till the dust settles on that.

I think I just copied Bitpays :) phing parses it locally to do phpunit/phpcs. Though looks like there is no phpmd.xml, which is why it's not running..

also no phpmd require-dev


Add webdriver to build gn file for flutter driver

Description
Fixes flutter/fuchsia roll. is there a way to verify this is sufficient?

@jonahwilliams unfortunately there is no easy way to verify this, go/flutter-cq-post-submits has a plan for verifying this post commit, but in the short term the easiest way would be to wait for the roller to try again.
LGTM

I needed to add package:matcher in google3, do you think that would be needed as well in gn?

Might as well be safe...

Hold this PR, revert of web driver is coming: https://github.com/flutter/flutter/pull/47389


Replace back link placeholder URLs with javascript

In most cases, the back button should simply go back to the referring page, so we can use window.history.
Closes #494
There is a small potential issue when hovering on the link, as browsers will display the href property in the status bar, which in this case is just some javascript (as shown in the image below).

I'm not sure how much of an issue this is for prototyping.

Not 100% sure, but you could argue this is a 'new feature' rather than a fix and therefore needs a more extended changelog entry to explain the change to users

I've added a feature CHANGELOG entry.

After a chat with @EoinShaughnessy, we've decided it'll be easier for the 2i reviewer if all changelog/release note changes are in one PR. So we're going to merge this as-is and incorporate the suggested release note changes into a separate PR with the other changelog changes.


[POSTGRES] GENERATED ALWAYS AS IDENTITY doesn't get @PrimaryGeneratedColumn decorator

Hiya - fantastic tool! Amazed at how much it seems to have extracted from my database... but...
I might be confused, but I generated this table in postgres:
CREATE TABLE "address" (   "addressId" INT GENERATED ALWAYS AS IDENTITY PRIMARY KEY);
When running typeorm-model-generator with defaults, the resultant model had addressId like so:
@Column("integer", { primary: true, name: "addressId" })   addressId: number;
As a beginner with type-orm, I was expecting
@PrimaryGeneratedColumn({ name: "addressId" })   addressId: number;
I hope I've given enough detail to be clear / allow for reproduction but apologies if not, I can supply them naturally. Thanks in advance!

Implemented in<EMAIL_ADDRESS>


[Proposal] Add scrollableTabAlignment to TabBarTheme

Is there an existing issue for this?

[X] I have searched the existing issues
[X] I have read the guide to filing a bug

Use case
The implementation of TabBarTheme.tabAlignment is, in my opinion, flawed. When setting a global tabAlignment, if not all of your TabBar's isScrollable property are uniform, you'll get an error at runtime, and have to change the tabAlignment property on the TabBar level. There is no current way to add a global default for scrollable and non-scrollable TabBar's at the same time.
Proposal
My proposal is to add a scrollableTabAlignment to TabBarTheme. The TabBar widget would pull either the tabAlignment or the scrollableTabAlignment depending on isScrollable's value.

I need this feature too


Add additional tests for 'formatoptions'

Codecov Report

Merging #6031 into master will decrease coverage by 0.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #6031      +/-   ##
==========================================
- Coverage   87.02%   87.01%   -0.02%
==========================================
  Files         142      142
  Lines      156393   156393
==========================================
- Hits       136108   136088      -20
- Misses      20285    20305      +20

Impacted Files
Coverage Δ

src/gui.c
63.30% <0.00%> (-0.76%)
:arrow_down:

src/gui_gtk_x11.c
57.69% <0.00%> (-0.39%)
:arrow_down:

src/netbeans.c
74.66% <0.00%> (-0.23%)
:arrow_down:

src/sign.c
94.77% <0.00%> (-0.18%)
:arrow_down:

src/mbyte.c
65.95% <0.00%> (-0.13%)
:arrow_down:

src/clipboard.c
83.07% <0.00%> (-0.11%)
:arrow_down:

src/term.c
81.68% <0.00%> (-0.06%)
:arrow_down:

src/message.c
88.59% <0.00%> (-0.05%)
:arrow_down:

src/window.c
89.30% <0.00%> (+0.03%)
:arrow_up:

src/drawscreen.c
83.40% <0.00%> (+0.07%)
:arrow_up:

... and 3 more

Continue to review full report at Codecov.

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


Bar: add 'middle' option for borderSkipped

Resolves: #9288
This could be considered a breaking change on custom usage of the bar element, because it no longed parses the borderSkipped from its options, but excepts the controller to do that.

I think this is fine to change since it's an internal implementation detail


Ability to choose seed value

Is your feature request related to a problem? Please describe.
In order to make it perfectly customizable, the seed has to be editable by users.
Describe the solution you'd like
A text area at the top of options settings on the UI.
Additional context
Had an issue while trying to take off the earring with micah style, so changing the seed might help.

[X] Tested locally
[X] Tested on streamlit

Notes
Updates were not rolled out on streamlit.io directly.
Only after a reboot, the changes were present.
Ref: #22


Error boundary still showing in production

Is this a bug report?
Maybe

Did you try recovering your dependencies?

1.16.0
Which terms did you search for in User Guide?

deoloy production create react app heroku
error boundary overlay production
error boundar showing on creater react app production
Environment

Environment Info:
System:
OS: macOS 10.14.5
CPU: (4) x64 Intel(R) Core(TM) i5-6360U CPU @ 2.00GHz
Binaries:
Node: 8.16.0 - /usr/local/opt/node@8/bin/node
Yarn: 1.16.0 - /usr/local/bin/yarn
npm: 6.4.1 - /usr/local/opt/node@8/bin/npm
Browsers:
Chrome: 74.0.3729.169
Firefox: Not Found
Safari: 12.1.1
npmPackages:
react: ^16.8.6 => 16.8.6
react-dom: ^16.8.6 => 16.8.6
react-scripts: 3.0.1 => 3.0.1
npmGlobalPackages:
create-react-app: Not Found
Steps to Reproduce

(Write your steps here:)

Set up an error boundary around the app
Deploy the production and staging app to heroku
When the error it triggered, an overlay should not show up.  This is not the case for both staging an production.

Expected Behavior

The error overlay should not show.
Actual Behavior

The error boundary shows in front of the fallback page.
Reproducible Demo

(Paste the link to an example project and exact instructions to reproduce the issue.)

Is the app correctly builded with NODE_ENV set to production ?

Please show a screenshot .And how you built the app

Please show a screenshot .And how you built the app

I run yarn build but I notice that the build folder in the create react app is in the gitignore file.  Do I need to commit my build folder?

import React, { Component, Fragment } from 'react';
import type { Node } from 'react';
import RollbarLog from '../../helpers/rollbar';
import SomethingWentWrongPage from './SomethingWentWrongPage';

type ErrorBoundaryProps = {
  children: Node,
  history: Object,
};

type ErrorBoundaryState = {
  hasError: boolean,
};

export default class ErrorBoundary extends Component<ErrorBoundaryProps, ErrorBoundaryState> {
  state = {
    hasError: false,
  };

  componentDidCatch(error: Object, info: Object) {
    this.setState({ hasError: true });
    RollbarLog.warning(error, info);
  }

  render() {
    const { hasError } = this.state;
    const { children, history } = this.props;
    if (hasError) {
      return <SomethingWentWrongPage history={history} />;
    }
    return <Fragment>{children}</Fragment>;
  }
}

The app still managed to be build in development mode somehow.
What are the exact steps that you're following ?

The app still managed to be built in development mode somehow.
What are the exact steps that you've followed ?

I'm hosting on heroku.  I run a yarn build locally and then commit, and push to heroku with git push production master all my NODE_ENV vars on heroku are set to 'production'.  But my question was, do I need to remove my bundle file from the .gitignore?  Create-react-app has it ignored by default.  Maybe that's my problem.

You'll need to use the create-react-app buildpack on heroku: https://github.com/mars/create-react-app-buildpack

You'll need to use the create-react-app buildpack on heroku: https://github.com/mars/create-react-app-buildpack

Thank you!!!