Can't complete installation (lamdbaattack-version folder fails)

Hello,
I'm trying to install this, but I keep getting an error when going through the lamdbaattack-version folder.
I installed apache maven successfully, I set up the paths as well, installed the latest version of java, installed MCProtocolLib(Don't know if it was needed but still did just in case, and this one did install without error), I tried everything, I keep rerunning the command but it can never install this folder.
Any help would be appreciated!
Here's the output:

Cmd output
Microsoft Windows [Version 10.0.18362.836]
(c) 2019 Microsoft Corporation. All rights reserved.
C:\Users\Groot>cd C:\Users\Groot\Desktop\LambdaAttack-master
C:\Users\Groot\Desktop\LambdaAttack-master>mvn clean install
[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Build Order:
[INFO]
[INFO] LambdaAttack                                                       [pom]
[INFO] lambdaattack-version                                               [jar]
[INFO] lambdaattack-version-1-11                                          [jar]
[INFO] lambdaattack-version-1-12                                          [jar]
[INFO] lambdaattack-version-1-14                                          [jar]
[INFO] lambdaattack-version-1-15                                          [jar]
[INFO] lambdaattack-core                                                  [jar]
[INFO]
[INFO] ------------------< com.github.games647:lambdaattack >------------------
[INFO] Building LambdaAttack 2.4.0                                        [1/7]
[INFO] --------------------------------[ pom ]---------------------------------
[INFO]
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ lambdaattack ---
[INFO]
[INFO] --- maven-install-plugin:2.4:install (default-install) @ lambdaattack ---
[INFO] Installing C:\Users\Groot\Desktop\LambdaAttack-master\pom.xml to C:\Users\Groot.m2\repository\com\github\games647\lambdaattack\2.4.0\lambdaattack-2.4.0.pom
[INFO]
[INFO] --------------< com.github.games647:lambdaattack-version >--------------
[INFO] Building lambdaattack-version 2.4.0                                [2/7]
[INFO] --------------------------------[ jar ]---------------------------------
[INFO]
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ lambdaattack-version ---
[INFO] Deleting C:\Users\Groot\Desktop\LambdaAttack-master\version\target
[INFO]
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ lambdaattack-version ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory C:\Users\Groot\Desktop\LambdaAttack-master\version\src\main\resources
[INFO]
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ lambdaattack-version ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 2 source files to C:\Users\Groot\Desktop\LambdaAttack-master\version\target\classes
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary for LambdaAttack 2.4.0:
[INFO]
[INFO] LambdaAttack ....................................... SUCCESS [  0.328 s]
[INFO] lambdaattack-version ............................... FAILURE [  0.618 s]
[INFO] lambdaattack-version-1-11 .......................... SKIPPED
[INFO] lambdaattack-version-1-12 .......................... SKIPPED
[INFO] lambdaattack-version-1-14 .......................... SKIPPED
[INFO] lambdaattack-version-1-15 .......................... SKIPPED
[INFO] lambdaattack-core .................................. SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  1.108 s
[INFO] Finished at: 2020-05-19T12:41:03-05:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile) on project lambdaattack-version: Fatal error compiling: invalid target release: 1.9 -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn  -rf :lambdaattack-version
C:\Users\Groot\Desktop\LambdaAttack-master>

Here's the output when doing mvn -e

mvn -e output
C:\Users\Groot\Desktop\LambdaAttack-master>mvn -e
[INFO] Error stacktraces are turned on.
[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Build Order:
[INFO]
[INFO] LambdaAttack                                                       [pom]
[INFO] lambdaattack-version                                               [jar]
[INFO] lambdaattack-version-1-11                                          [jar]
[INFO] lambdaattack-version-1-12                                          [jar]
[INFO] lambdaattack-version-1-14                                          [jar]
[INFO] lambdaattack-version-1-15                                          [jar]
[INFO] lambdaattack-core                                                  [jar]
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary for LambdaAttack 2.4.0:
[INFO]
[INFO] LambdaAttack ....................................... SKIPPED
[INFO] lambdaattack-version ............................... SKIPPED
[INFO] lambdaattack-version-1-11 .......................... SKIPPED
[INFO] lambdaattack-version-1-12 .......................... SKIPPED
[INFO] lambdaattack-version-1-14 .......................... SKIPPED
[INFO] lambdaattack-version-1-15 .......................... SKIPPED
[INFO] lambdaattack-core .................................. SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  0.149 s
[INFO] Finished at: 2020-05-19T12:59:19-05:00
[INFO] ------------------------------------------------------------------------
[ERROR] No goals have been specified for this build. You must specify a valid lifecycle phase or a goal in the format : or :[:]:. Available lifecycle phases are: validate, initialize, generate-sources, process-sources, generate-resources, process-resources, compile, process-classes, generate-test-sources, process-test-sources, generate-test-resources, process-test-resources, test-compile, process-test-classes, test, prepare-package, package, pre-integration-test, integration-test, post-integration-test, verify, install, deploy, pre-clean, clean, post-clean, pre-site, site, post-site, site-deploy. -> [Help 1]
org.apache.maven.lifecycle.NoGoalSpecifiedException: No goals have been specified for this build. You must specify a valid lifecycle phase or a goal in the format : or :[:]:. Available lifecycle phases are: validate, initialize, generate-sources, process-sources, generate-resources, process-resources, compile, process-classes, generate-test-sources, process-test-sources, generate-test-resources, process-test-resources, test-compile, process-test-classes, test, prepare-package, package, pre-integration-test, integration-test, post-integration-test, verify, install, deploy, pre-clean, clean, post-clean, pre-site, site, post-site, site-deploy.
    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:97)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
    at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
    at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957)
    at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289)
    at org.apache.maven.cli.MavenCli.main (MavenCli.java:193)
    at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke (Method.java:498)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225)
    at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406)
    at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347)
[ERROR]
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/NoGoalSpecifiedException

You don't have Java 9 installed.

You don't have Java 9 or higher installed.

Yup, that was it! I forgot to update the path from the old JDK to the new JDK.
Thank you very much!


Update Webpack to v2

This PR updates Webpack to the latest and greatest v2 (as part of #3607) including its babel related dependencies and add-on loaders. Note: npm-shrinkwrap.json was updated with --no-optional

Just rebased this on top of #3636 (and killed the Travis build manually) to see what happens in Linux / a container. All looking good.


terminate called after throwing an instance of 'c10::CUDAError'

🐛 Describe the bug

This error often happens, well, mostly after the training, but not sure whether related to colossalai (maybe not?) I searched this error on google, but other people also do not provide some useful suggestion. I am just wondering does any other user also meet this error when using colossalai?
Thank you!!
Environment
No response

Hi, did you use torchrun to execute this?

Hi, did you use torchrun to execute this?

oh! I did not! Let me try it. Thanks!

In general, this issue is due to improper process termination by the launcher. Don't worry about it if you can get the results you want.


Request: docker driver should config to select a ansible connection

Issue Type

Feature request

Molecule and Ansible details
ansible --version
2.2.1
molecule --version
1.21.1

Molecule installation method: pip
Ansible installation method: OS package

Desired Behaviour
Because some roles are depending on ssh, and docker driver have a better performance for testing, we should have a config key to set ssh connection instead of docker connection. In adittion, each ssh container should have a different ansible_port.
Actual Behaviour (Bug report only)
docker driver seems to always use docker connection in ansible.

Can you provide a sample of a role that depends on the ssh connection driver?

I have some ssh metal machines, so i want some roles to handle basic configurations about ssh, such as
https://github.com/gzm55/ansible-ssh-pubkey-login-role
https://github.com/gzm55/ansible-smart-ssh-pipelining-role
the main logic is for sshd service.

I don't believe I would implement this into Molecule v1.  This could get implemented into v2.  However, it seems like it is unnecessary.
You could simply have molecule spin up two instances with ssh configured as you desire.  You would then write a testinfra test to ssh into the other instance and verify it works as expected.  Simple client/server instances test.  I see no need to change the connection driver.

@retr0h in ansible_playbook.py, the driver specific connection params (including connection=docker) will be put into ansible cli params, then the role is played under docker connection, that is not expected.

@gzm55 ah, yeah I see what you mean.  I'm not entirely sure the best approach to solve your particular issue.  This is somewhat of an edge case, but not entirely.
Would things work to your satisfaction if 'ansible_port' and connection was settable from molecule.yml?

IMHO this is a pretty edgy case.
You could workaround the issue by adding a new host and delegating to it in the playbook:
- name: Add docker host with ssh connection
  add_host:
    name: dockerhost_ssh
    ansible_host: "{{ ansible_default_ipv4.address }}"
    ansible_connection: ssh
- name: Do stuff via ssh
  delegate_to: dockerhost_ssh
  debug: msg="Hello world!"

Would things work to your satisfaction if ansible_port and connection was settable from molecule.yml?

Yes, it could be enough.

You could workaround the issue by adding a new host and delegating to it in the playbook:

This workaround solution may work, but still the developer has to deal with dockerhost_ssh carefully, such as, whether dockerhost_ssh will be in the ansible_play_hosts of the following tasks, what's the behavior of nesting delegate_to (role may contain a delegated task), etc.
I think the way of settable port and connection is more maintainable.

Actually, you don't even need the delegate_to, you can just add a play at the beginning of your playbook that puts all docker containers via add_host in a new group, then run the actual test play against that group.

IMHO this is a pretty edgy case.

Agreed...

@gzm55 @alvaroaleman provided a work-a-round.  However, this request is edgy and prob something we will not address.  Thanks for spending the effort to create an issue.


how to use the action with gradle?

my build file looks like the following, however, I still get the error that > No version of NDK matched the requested version 21.3.6528147. Versions available locally: 22.0.7026061
is there a good way to tell grade that a NDK version has been downloaded? Thanks

      - name: Checkout code
        uses: actions/checkout@v2

      - name: Use Java8
        uses: actions/setup-java@v1
        with:
          java-version: 1.8
      - name: download ndk
        uses: nttld/setup-ndk@v1
        with:
          ndk-version: r21d
      - name: Generate Debug APK
        run: ./gradlew clean assembleDebug

I'm not really familiar with gradle, but this looks like it should do the trick
https://developer.android.com/studio/projects/configure-agp-ndk

I'm not really familiar with gradle, but this looks like it should do the trick
https://developer.android.com/studio/projects/configure-agp-ndk

I'm going to close this issue since it's more of a question about the usage of gradle. This action is mostly meant for fully native worflows, I feel like there are probably better ways to setup the NDK for usage in more "classic" android workflows.

I'm going to close this issue since it's more of a question about the usage of gradle. This action is mostly meant for fully native worflows, I feel like there are probably better ways to setup the NDK for usage in more "classic" android workflows.


Multi-value block returns not implemented?

It seems like multi-value extension is currently only partially implemented, namely multi-value block returns seems to be missing (also confirmed by running the parser on WebAssembly test suite). Are there any plans on implementing full support for the multi-value extension?
I'd be happy to implement this myself if you're open to contributions. I think making BlockType a newtype around Vec<ValueType> (similar to results field of FunctionType) adding another variant to BlockType for the type index for multi-value returning blocks would work. This will be a breaking change so a major version bump will be required.

Sure, go ahead
just make sure that it is behind multi_value feature flag

Any progress on this?


Support for load balancer IPs

Some load balancer services provide an hostname for ingress, some provide an ip. Goal should be to be able to deal with both by simply using whatever is in the load balancer status.


Improve slippage UX for LP users

Problem
User feedback (chompk.eth)

I just talked with Thai community members about providing the liquidity, the got some feedbacks to the current pool status

Most community member are confused on how to get 1:1 nextAsset without slippage from swapping

One of the community member having a hard time trying to provide a nextAsset LP to the pool when they're holding a large amount of money on the destination chain
this guy say that he deposit half nextAsset (from swapping canonical asset to nextAsset) and half canonical asset
he didn't aware of the slippage when depositing, thinking that it should be half-half like x * y = k equation
he said that he's a bit not happy about how he deposit 1000 usd and can't redeem 1000 usd back full (it's 998.4 to be exact) as he doesn't know about the slippage before
he's quite confused if this mechanism will be secure (although it's clearly secure if they understand how mint/lock + AMM works,  we can't expect everyone to understand this as it's quite complex)
The point is that most people still don't understand how this mint/lock + AMM mechanism works. Here's some of the thing i found people misunderstanding:

how stablepools work, most people still have a perception that providing one asset = auto swap 50-50 to the pool like x*y = k
how slippage on stable pools works (they have a thought that for stable asset, providing 100 should get back 100 full)
A lot of people THINKING that nextAsset SHOULD be obtained from swapping canonical asset only (which is false, the best way is to bridge through Connext from mainnet)

Proposed solution

Add 'Pool Balance' field and show the same bar as the Pools Overview page
Show percentages with their respective token assets

Change Price Impact to Slippage when the number is <0
When >=0, change the field title to Bonus

When Slippage <0, then show the warning (same behavior as before).
Change the text to say

Warning

You may have -0.00765% slippage because USDC is currently overweighted in this pool.
If you provide additional nextUSDC instead, you may receive bonus tokens.
use logic for the amount and the asset names

Add a link to our LP guide here
Stuck? Click here for our LP guide ->
Clicking LP Guide links to https://blog.connext.network/providing-liquidity-on-connext-f7aa3f2bc7b8#a940

just made slight update to the wording again

Sort of related to this: make arbitrary amount withdrawals of each pooled token possible

@Tommy-R8 Please track this in the backlog and feel free to comment if you hear more https://github.com/connext/monorepo/issues/3369

https://discord.com/channels/454734546869551114/1053026258021257316/1071084455239888966


$name variable causes script failure cascade if SSID has spaces or quotes in name

See screenshot for example

Thank you for the issue, a few days ago I was improving the code and I noticed that in some parts of it the variables may cause some errors, I try to fix it ASAP. I also will fix the "DISPLAY" erros so in case it fails, it doesn't print any output.


singularity: 3.0.1 -> 3.2.1

Motivation for this change
Version update, build process has changed slightly.
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Assured whether relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

@GrahamcOfBorg build singularity

Should this be back-ported to 19.03, given the fact that the old version seems to have a lot of bugs?

What's the policy on back-porting? While 3.0.1 is buggy it at least isn't insecure (i.e., CVE-2019-11328 doesn't apply) and does have core functionality.

@jbedo If the bugs are severe enough and it does not break anything else or changes behavior a back port could be justified.  I am not a singularity user so I would leave that decision the people actively using it.

OK, I'm not sure the bugs are severe enough to warrant backporting, maybe @bbarker can comment.

I don't have any knowledge of what the specific bugs are, other than the
one I'm experiencing, which may or may not be fixed by upgrading (still
need to test it). As it isn't a showstopper for me currently, I'm happy to
wait for now. What I should do is test the new version in a different
environment to see if that fixes the issue I had.
On Tue, Jun 25, 2019 at 3:13 AM Justin Bedő<EMAIL_ADDRESS>wrote:

OK, I'm not sure the bugs are severe enough to warrant backporting, maybe
@bbarker https://github.com/bbarker can comment.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/NixOS/nixpkgs/pull/63409?email_source=notifications&email_token=AAG7XDVILIHKRZM57BFCSHDP4HASZA5CNFSM4HY35W3KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYPIWMI#issuecomment-505318193,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAG7XDX7F4L4QJQCDMSUH3DP4HASZANCNFSM4HY35W3A
.

--
Brandon Barker
<EMAIL_ADDRESS>


[Feature request] : Add Favourite Restaurant Functionality

Description
I would like to have the ability to add my favourite restaurants to a "Favourites" list for easy access. This feature will enhance the user experience by providing a way to quickly access and view favourite restaurants.
Proposed Solution

Introduce a heart icon (or any suitable icon) on each restaurant card.
When a user clicks on the heart icon, the respective restaurant will be added to their list of favourites.
Implement a "Favourites" page within the app, preferably located below the header and to the right side of the "Filter 4+" button. This page will display the user's favourite restaurants.

Acceptance Criteria

Users can click on the heart icon on a restaurant card to add it to their favourites.

The selected restaurant should appear on the "Favourites" page.

Users can remove a restaurant from their favourites if they wish.

[ ]  I have checked the existing issues

[ ]  I have read the Contributing Guidelines

[ ]  I want to work on this issue

Additional Information
This feature will enhance user engagement and make it easier for users to keep track of their preferred restaurants. It aligns with our goal of creating a user-friendly and enjoyable restaurant exploration experience.
Tasks

[ ] Implement the heart icon on restaurant cards.
[ ] Develop the functionality to add and remove restaurants from the favorites list.
[ ] Create the "Favourites" page and integrate it into the app's layout.
[ ] Test the feature thoroughly to ensure it works seamlessly.
[ ] Update the app's documentation to include information about this new feature.

Contribution Guidelines

Please fork this repository and create a feature branch for this task.
Follow our coding style and conventions (if any) as outlined in our project's guidelines.
Feel free to reach out for any clarifications or assistance during the development process.

Additional details
Please refer to the similar feature screenshot which we are going to implement for a visual representation of this feature.

Let's make our restaurant exploration app even better by adding this exciting feature! Contributors, please indicate your interest in working on this issue. Let's collaborate to make it happen.

Hey Anand, I would like to work on this issue.

@reyrinbafs have you worked on any react project ?

Hi Anand, I would like to work on this issue.

@LynxSumit you can work on it

@LynxSumit done, thanks for the follow up.

Helllo @Anandsg i know i was not assigned this issue but seemed interesting so i have solved it and generated a pull request could you have a look

feature has been deployed hence closing the issue


Create opensuse:leap build

I think the ci/kokoro/install/opensuse-leap build satisfy this requirement.


Support adding more items dynamically

Fixed issue #12
Handle newly added items & allow continuous scrolling.
Adding code to mimic paging.

That's a great pull request, thank you!


Added Allwinner 2013 naming scheme support for A-Series.

Allwinner updated their naming scehme since 2013:
Allwinner_SoC_Family
The new scheme is sunxiwxpx,  the old scheme sunxi is preserved in this PR for compatibility.

Thank you, the build system scripts changes in my local machine i'll fix it.


Issue #165: enhance documentation of *branch properties

Resolves #165 (just documentation)

Travis ok: https://travis-ci.org/github/vackosar/gitflow-incremental-builder/builds/682723746


Grossmann/fpga flow systemverilog test

This adds a highly minimal check to the sv2v front end for the FPGA flow.  Additional work could be done in the future to expand the range of SystemVerilog syntax that we wish to have test coverage for.

Already getting exercised in ASIC flow


Fix hyperlinks to documentation for fud/frontends

Some of the hyperlinks to documentation about fud and the compiler frontends for Calyx were broken - hoping that this fixes most of them.
I'm not sure if there's a template engine for Calyx's documentation that would resolve these issues automatically - if so, feel free to disregard this PR :smile:

Thanks LGTM!


Design a concept for the webshop

Come up with a concept for the webshop to fullfill all the requirements, and display them in a UML Use-Case-Diagramm


[release-0.36] Backport prow release automation changes from 0.40

What this PR does / why we need it:
We had to switch off Travis CI a while back due to leaked credentials, and then we never bothered to update the release automation. This PR backports the release job automation scripts from main to 0.36 branch, so we can do releases without Travis using the postsubmit job working on release tags.
Requires mentioned postsubmit to get adjusted to work for 0.36: https://github.com/kubevirt/project-infra/blob/main/github/ci/prow-deploy/files/jobs/kubevirt/kubevirt/kubevirt-postsubmits.yaml#L42
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
/cc @rmohr
Release note:

Backport prow release automation changes from 0.40 to 0.36

/retest

/lgtm
/approve

/cc @stu-gott

/retest

/retest

/retest

/override pull-kubevirt-e2e-k8s-1.18
Overriding the lane, as according to the PR history each time a different test was failing: https://prow.ci.kubevirt.io/pr-history/?org=kubevirt&repo=kubevirt&pr=6837


Unhandled error Network error: Network request failed Error:

I  got this error in my application ( react-native ) when internet connection is lost.
Version
"apollo-client" "1.0.4",
"react-apollo": "1.1.1",
"react-native": "0.44.0",
Found this error on console
"ExceptionsManager.js:71 Unhandled error Network error: Network request failed Error: Network error: Network request failed at new ApolloError"
How can i fix this issue: Here is my Screen-Shot,

import { AsyncStorage } from 'react-native';
import {SubscriptionClient, addGraphQLSubscriptions} from 'subscriptions-transport-ws';

const wsClient = new SubscriptionClient('wss://<IP_ADDRESS>:5000', {
  reconnect: true,
  connectionParams: {
    accessToken: 'jka sdhkjashd jkashdjk ashdas'
  }
});

const networkInterface = createNetworkInterface({

  uri: 'http://<IP_ADDRESS>:8000/graphql',
  opts: {
    credentials: 'same-origin'
  }
});
const networkInterfaceWithSubscriptions = addGraphQLSubscriptions(
  networkInterface,
  wsClient
);
const client = new ApolloClient({
  dataIdFromObject: o => o.id,
  networkInterface: networkInterfaceWithSubscriptions

});
networkInterface.use([{
  applyMiddleware(req, next) {
    if (!req.options.headers) {
      req.options.headers = {};  // Create the header object if needed.
    }
    // get the authentication token from local storage if it exists
    AsyncStorage.getItem('sessionToken').then((token) => {
      req.options.headers.Authorization = token ? `${token}` : null;
      next();
    }
    );
  }
}]);
export default client;

This issue looks like a question that would be best asked on StackOverflow.
StackOverflow is amazing for Q&A: it has a reputation system, voting, the ability to mark a question as answered. Because of the reputation system it is likely the community will see and answer your question there. This also helps us use the GitHub bug tracker for bugs only.
Will close this as this is really a question that should be asked on StackOverflow.

@haris-ramzan
did you fixed this error at all?


Parallelize multiple crops

Hi,
Atm the student multi-crop wrapper is running different crops sequentially, these could potentially run in parallel in the GPU if they were passed as a single batch to the student network.
Any particular reason why these were kept sequential? I.e., is there any performance requirement on performing two backward propagations (one for each crop/augmentation) ?
Thanks

Hi @4knahs
Thanks for your interest. Crops with the same resolution are batched together so that there is one forward per resolution. We perform forward pass separately on each resolution input. The inputs corresponding to a single resolution are clubbed and single forward is run on the same resolution inputs. Hence we do several forward passes = number of different resolutions used.
We cannot batch crops of different resolution though.
Hope that helps.


Fix issue with focus extension item loss

This PR fixes #88860
I am pretty sure that this is an incorrect solution :)
But I debuged this and the loss of focus occurs here.
Maybe you can help me to find where it is better to fix this behavior

Change will break focusing extension editor.

@sandy081 @Tyriar
I debug list ui component one more time and it seems like unfocus action on double click - is the expected behaviour.

It happens here - https://github.com/microsoft/vscode/blob/0f95917e0f9ccbb32fd6db338afec535a5a15c0a/src/vs/base/browser/ui/list/listWidget.ts#L633
Search lists work exactly the same.

And gray color - is the color of selected item with unfocused list.
So I suppose it’s not a bug? Or maybe I missing something.

This got fixed along with ##91603. Hence closing this.
Thanks.


chore(legendary): add frecency sorting

Frecency sorting was introduce to legendary.nvim few days a ago. I thought it's nice to have it. But if you don't think it's a good idea, fell free to close the PR!

ok sure!  Well do next time!


Update DG

Update Design section to match v1.4
Added section explaining design and implementation of Archive feature
Added most commands to the Manual Testing Appendix section
Added Effort section

Codecov Report

Merging #154 (b95de99) into master (d2d1567) will increase coverage by 6.52%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master     #154      +/-   ##
============================================
+ Coverage     64.16%   70.68%   +6.52%
- Complexity      679      776      +97
============================================
  Files           121      121
  Lines          2601     2610       +9
  Branches        365      371       +6
============================================
+ Hits           1669     1845     +176
+ Misses          773      628     -145
+ Partials        159      137      -22

Impacted Files
Coverage Δ

...ntry/predicate/EventContainsKeywordsPredicate.java
33.33% <0.00%> (ø)

src/main/java/seedu/address/model/entry/Event.java
77.35% <0.00%> (+1.88%)
:arrow_up:

src/main/java/seedu/address/model/AddressBook.java
71.79% <0.00%> (+2.56%)
:arrow_up:

...seedu/address/logic/commands/EditEventCommand.java
97.36% <0.00%> (+2.63%)
:arrow_up:

...in/java/seedu/address/logic/parser/ParserUtil.java
97.10% <0.00%> (+2.89%)
:arrow_up:

...eedu/address/logic/commands/EditPersonCommand.java
97.10% <0.00%> (+2.89%)
:arrow_up:

...rc/main/java/seedu/address/model/ModelManager.java
72.78% <0.00%> (+4.43%)
:arrow_up:

src/main/java/seedu/address/model/entry/Time.java
86.66% <0.00%> (+6.66%)
:arrow_up:

.../main/java/seedu/address/model/entry/Location.java
81.81% <0.00%> (+9.09%)
:arrow_up:

...ava/seedu/address/model/entry/UniqueEntryList.java
85.71% <0.00%> (+9.52%)
:arrow_up:

... and 22 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 d2d1567...b95de99. Read the comment docs.


test(testing): :alembic: Seed phrase and zero balance account

This is an integration test which could be encapsulated into a mbjs method which produced a zero balance (sub account), which when paired with meta transactions in near-api-js upcoming releases could allow users to connect to services without having to purchase any NEAR token.

There isn't much of a need to merge this one really, think we'll rely on wallets to create the accounts for meta transactions

This was only for reference, no need to merge this


Post Curl without waiting for response

I would like to do a post curl request but doesn't want to wait for the external server to response. How do i actually do it with this library?

Hi. If you'd like to make asynchronous requests, you can can use MultiCurl. Here's an example: https://github.com/php-curl-class/php-curl-class/blob/master/examples/multi_curl_post.php
If you'd like to make non-blocking requests, try these:
$ curl --request POST "https://www.example.com/" --data "a=1&b=2&c=3" > /dev/null 2>&1 &

$ php do_post_request.php > /dev/null 2>&1 &

Hey, it works perfectly fine. Thanks for your help!


springcloud-eureka-seata启动报错

2019-07-02 12:09:52.560  WARN 29440 --- [           main] ationConfigEmbeddedWebApplicationContext : Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'org.springframework.boot.autoconfigure.orm.jpa.HibernateJpaAutoConfiguration': Unsatisfied dependency expressed through constructor parameter 0; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'dataSourceProxy' defined in io.seata.sample.AccountApplication: Unsatisfied dependency expressed through method 'dataSourceProxy' parameter 0; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'dataSource' defined in io.seata.sample.AccountApplication: Initialization of bean failed; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'dataSourceInitializer': Invocation of init method failed; nested exception is org.springframework.beans.factory.BeanCurrentlyInCreationException: Error creating bean with name 'dataSourceProxy': Requested bean is currently in creation: Is there an unresolvable circular reference?
2019-07-02 12:09:52.563  INFO 29440 --- [           main] o.apache.catalina.core.StandardService   : Stopping service [Tomcat]
2019-07-02 12:09:52.598  INFO 29440 --- [           main] utoConfigurationReportLoggingInitializer :
Error starting ApplicationContext. To display the auto-configuration report re-run your application with 'debug' enabled.
2019-07-02 12:09:52.605 ERROR 29440 --- [           main] o.s.b.d.LoggingFailureAnalysisReporter   :

APPLICATION FAILED TO START

Description:
The dependencies of some of the beans in the application context form a cycle:
org.springframework.boot.autoconfigure.orm.jpa.HibernateJpaAutoConfiguration
┌─────┐
|  dataSourceProxy defined in io.seata.sample.AccountApplication
↑     ↓
|  dataSource defined in io.seata.sample.AccountApplication
↑     ↓
|  dataSourceInitializer
└─────┘
Process finished with exit code 1

@jorrellz fixed

remove @Primary

解决了吗  我这也产生循环引用了 怎么解决的

@SpringBootApplication(exclude = {DataSourceAutoConfiguration.class})
启动类上注解添加exclude


bug: mouseenter gets emitted with touch data when there is touch movement

Source of the panic:
https://github.com/marc2332/freya/blob/1b1a24a84e2a80bffc3d439ae023cb9a812ec1b1/crates/elements/src/events/mouse.rs#L47

Steps to reproduce:

cargo run --example=switch_theme
Press the switch component with a touch input.
Panic occurs.

https://github.com/marc2332/freya/pull/888 Should fix this


Karate (Thymeleaf -> SAXParser) prints "Fatal Error" when encountering valid HTML5

I am attempting to use Karate to authenticate with our service via an OAuth2 authorization code grant. During the process, my test needs to fetch (and parse, using JSoup in a Java interop) our service's scope approval web page. This page is valid HTML5 (hopefully), containing unclosed <link> and <meta> tags.
As far as I can tell, karate attempts to parse that page through thymeleaf, which, in turn seems to attempt to use a SAXParser to process. That results in an error message "Fatal Error" in the logs (although the test then continues and succeeds).
I am attaching a trivial feature file
html5-fetch.feature.txt
to fetch from a stub from a web site of mine.
Unfortunately, I seem to be unable to produce an English error message; the German equivalent is
[Fatal Error] :7:5: Elementtyp "link" muss mit dem entsprechenden Endtag "</link>" beendet werden.
13:24:03.947 [main] WARN  com.intuit.karate - auto-conversion of response failed: org.xml.sax.SAXParseException; lineNumber: 7; columnNumber: 5; Elementtyp "link" muss mit dem entsprechenden Endtag "</link>" beendet werden.

(seems to translate to org.xml.sax.SAXParseException: Element type "link" must be terminated by a matching end tag "</link>")
I would prefer not having "Fatal Errors" in my test logs, even when they succeed. It does not seem to be a good idea to attempt to parse responses as xml, unless the content type is xml.
I am fine if you regard this topic as a non-issue :)

yes a wontfix this is what I see on my console BTW, and I have no idea how it becomes Thymeleaf for you - but my guess is that the system XML parser has been "hijacked" by JSoup. here is a related issue for anyone who cares to investigate a fix: https://github.com/intuit/karate/issues/1587
18:29:38.757 [main] DEBUG com.intuit.karate - response time in milliseconds: 547
1 < 200
1 < Date: Fri, 16 Jul 2021 12:59:38 GMT
1 < Server: Apache/2.4.43 (Linux/SUSE)
1 < Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
1 < Last-Modified: Fri, 16 Jul 2021 11:12:02 GMT
1 < ETag: "d2-5c73ba833de64"
1 < Accept-Ranges: bytes
1 < Content-Length: 210
1 < Keep-Alive: timeout=15, max=100
1 < Connection: Keep-Alive
1 < Content-Type: text/html
<!DOCTYPE html>

    <meta charset="utf-8">
    <link rel="stylesheet" type="text/css" href="./format.css">
    <title>Stub</title>

Stub

[Fatal Error] :7:5: The element type "link" must be terminated by the matching end-tag "</link>".
18:29:38.770 [main] WARN  com.intuit.karate - auto-conversion of response failed: org.xml.sax.SAXParseException; lineNumber: 7; columnNumber: 5; The element type "link" must be terminated by the matching end-tag "</link>".
---------------------------------------------------------
feature: classpath:com/intuit/karate/junit4/dev/test.feature
scenarios:  1 | passed:  1 | failed:  0 | time: 0.7375
---------------------------------------------------------

you are welcome to improve the error message and submit a PR !
BTW you can also add this line to your test:
* assert responseType == 'string'

and since you seem to trying to scrape things out of HTML see this also: https://stackoverflow.com/a/67331307/143475

actually on second thoughts can @edwardsph comment on this related to https://github.com/intuit/karate/issues/1462
it does make sense that we only convert to XML based on the response content-type. I just worry about existing tests in the wild as always (especially a lot of SOAP users). and if there are more "exotic" content-types that happen to be just XML

I think it should detect that the content-type is neither JSON, XML nor plain text and therefore not attempt to SAX parse it but I will have a closer look next week.

@edwardsph okay I took care of it and the diff is interesting. I think it will be fine, but anyway we will do RC5 to see what the feedback is
@bnutzer you convinced us :) reopening - and do let me know if the fix works !

@ptrthomas Perfect! Works for me, fixes both the sample request as well as my production code.
Thanks for your hint for the karate.extract() function. Probably a valuable solution for lots of cases. However, in my case I need to collect all "name" attributes of all html entities with a certain "class" attribute. That's 3 lines of well readable code using Java, but would be hell of a regex using the "extract" function, I suppose.
The diff looks straight forward and really sensible to me. However, I do understand that this might be breaking for some folks.
Thanks again!

@bnutzer I'll keep this open until the "final" version, that's what we usually do with especially (potentially) breaking issues like this one
P.S. thanks for starring the project - you made it into the screenshot: https://twitter.com/KarateDSL/status/1416013547067248640

1.1.0 released

Please re-open. See PR


Fixes a sample that was causing deadlocks

We should never tell users to use .Result. The correct way to call asynchronous methods is with the await keyword.

Hi @msfcolombo, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

It looks like you're a Microsoft contributor (Fernando Colombo). If you're full-time, we DON'T require a Contribution License Agreement. If you are a vendor, please DO sign the electronic Contribution License Agreement. It will take 2 minutes and there's no faxing! https://cla.microsoft.com.

TTYL, MSBOT;

@msfcolombo : Thanks for your contribution to the Azure documentation! The author, @adhurwit, has been notified to review your proposed change.

#sign-off


Netflix Clone Website #28

Pull Request for WebMasterLog 💡
Issue Title: Netflix Clone Website

Name of the project : Netflix Clone
Category: Front-end projects
Name: Sneha Mishra
GitHub ID: https://github.com/Sneha123-zudo
Idenitfy yourself: JWOC '24 Contributor

Closes: #28

Describe the add-ons or changes you've made 📃
Created a clone of website "Netflix" using HTML  and CSS.
Type of change ☑

What sort of change have you made:

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

How Has This Been Tested? ⚙
I verified my project using live server of vsCode
Checklist: ☑

[x] My code follows the Contributing Guidelines & Code of Conduct of this project.
[x] This PR does not contain plagiarized content.
[x] I have performed a self-review of my own code.
[ ] I have commented my code, particularly wherever it was hard to understand.
[ ] I have made corresponding changes to the documentation.
[x] My changes generate no new warnings.
[x] I have added things that prove my fix is effective or that my feature works.
[ ] Any dependent changes have been merged and published in downstream modules.

Screenshots 📷

Note to reviewers 📄

Please Review my pull request .

@Sneha123-zudo Are you still working on it?

Can i create a new pull request by closing this one and do properly all the things ??

Can i create a new pull request by closing this one and do properly all the things ?? I had made the clone.

If possible to these changes to complete in this pr, it will be better. Otherwise you can create another PR, OK. But Keep the folder structure as mentioned in guidelines carefully.

Ok


fix requre tests again

nice! can you explain what was the problem?

Oh, there were possible several issues, what could caused this strangeness, but I did not have what exactly could cause this.

I've regenerated it locally (but should be same in conainer image) but not sure if all necessary secrets are forwarded to image, not sure if also ssh key or krb keytab should be linked as well, so maybe this could cause issues inside container image regeneration.
I had had version of org, so I've updated the ogr from master (it could be potential issue what caused this if you had some older version of ogr and in zuul there were newer and there were some bigger changes) or you did not removed/updated old container which could contain older version of tools, so that it led to bad generated data
second issue could be, that probably some files from test_data/*/ were not git add ed (probably with your change there were added something new (maybe some tar archives))
third think is that REQURE_MODE=read does not work as I've expected, there is some issue with decorator code invocation, so that this is another issue but it led me to another way of investigation of the issue, thats why it took longer time with debugging.

and it is also  possible that it could be combination of these issue, so that regeneration in container is much cleaner form that perspective.
Maybe we could update doc as well, and add there these possible issues with regeneration.
On the other hand, in case I have clean env, installed all possible deps and do not forget to git add files if there are some new. there were no issue from that point of view :-)

nice! can you explain what was the problem?

Oh, there were possible several issues, what could caused this strangeness, but I did not have what exactly could cause this.

I've regenerated it locally (but should be same in conainer image) but not sure if all necessary secrets are forwarded to image, not sure if also ssh key or krb keytab should be linked as well, so maybe this could cause issues inside container image regeneration.
I had had version of org, so I've updated the ogr from master (it could be potential issue what caused this if you had some older version of ogr and in zuul there were newer and there were some bigger changes) or you did not removed/updated old container which could contain older version of tools, so that it led to bad generated data
second issue could be, that probably some files from test_data/*/ were not git add ed (probably with your change there were added something new (maybe some tar archives))
third think is that REQURE_MODE=read does not work as I've expected, there is some issue with decorator code invocation, so that this is another issue but it led me to another way of investigation of the issue, thats why it took longer time with debugging.

and it is also  possible that it could be combination of these issue, so that regeneration in container is much cleaner form that perspective.
Maybe we could update doc as well, and add there these possible issues with regeneration.
On the other hand, in case I have clean env, installed all possible deps and do not forget to git add files if there are some new. there were no issue from that point of view :-)


No match in graphOutput for targetFilename search causes hang

If the graphOutput doesn't contain the targetFilename then the regex search hangs the script. This can happen if the tests failed before the app even launched (e.g. the app fails to compile), so there's no entry for the app output.
Some investigation suggests that it's down to limitations in python's regex engine that no one's been willing to address due to the effort involved and is likely caused by a bad regex anyway, so possible to solve by the script author (if they're enough of a regex expert).
Example of graphOutput that can cause the hang:
* ActionsInvocationRecord
  - Id: 0~ViderfHG-tjKx31eDlrcCFZ7lPy2wuE4y2vo4xbNPgomTBbBLtWXY_oY9DlOEKXAXAeO_APN3tLJtsZDWABvpA==
  - Size: 129364
  - Refs: 5
    * ActivityLogSection
      - Id: 0~0iVC4vXDH8o3b6GSoiqaSZMTgsP6sg6pTG4gIilVtLqtCVDVk-cBOX_JDOUq2eLiZGPjlvUC8XnhEXBN_orYXg==
      - Size: 11436577
    * CASTree (file or dir)
      - Id: 0~dd8WbHD1pC54m4JODNROAYjzeer5D10hQSwSq6MYiZlYlCEOoAtCxlnDseuq9CfcVS3Y4Lj17r6NJCbJ62Y2Pg==
      - Size: 108
      - Refs: 1
      + UITests-95161872-D4C0-4B1E-8F0D-992DAE6F3366-Configuration-Configuration 1-Iteration-1 (directory)
        * CASTree (file or dir)
          - Id: 0~uvgf1VbnsbNHZK2wbqIVGW6Cue4wKjwl2JC7XiVcHlq9QDYzh778ThaSKkFHJMuxrfPtk0XWFimnCgAl2vYqQQ==
          - Size: 36
          - Refs: 1
          + scheduling.log (plainFile)
            * raw
              - Id: 0~JS3Vdv54JARu0hIXIFMVw0p498mKuRD1kcV29aUwZThJRBn4fK2qome-GEav_4dOf8gqQL_AQk2ogew9GMSv6g==
              - Size: 121
    * ActionsInvocationMetadata
      - Id: 0~eWb2GMD4--4Kr2YVl5KmPZPjfEnO1qJMNRlPLZIRpsKzmAnky8o70g7Q4RWupB4yKODVuXc4_qKisR2HVAJmYw==
      - Size: 475
    * ActivityLogSection
      - Id: 0~wLKGjIRNtB2_yOlkrTvWPI8ekMBwe2tdAL1T5gcTuHmKAL00HGFuylEys6xfgu6LXj6FLU3Py1nn6Q4zIXCspA==
      - Size: 852
    * ActivityLogSection
      - Id: 0~zvTToocgLlp_YbMSA6CoNTeJ4pS80sysrbrAG1nYA4Fbem4MX_4hbQ4JvHG2DqUHe_TWaGnY0MtQ9KJW5BTcdQ==
      - Size: 44943389

Fixed with an early exit: https://github.com/ChrisMash/XCResultExtractor/commit/20fadb0874fcbb402d766138f5f9a76e67e57d14

Fixed with an early exit: https://github.com/ChrisMash/XCResultExtractor/commit/20fadb0874fcbb402d766138f5f9a76e67e57d14


Test modules utils::ranges and utils::perfmeters

see issue title.

completed. Better understanding of correct syntax about ranges usage!


Add tape echo

maybe tape echo is just adding random modulations to the delays?
(also need to add vibrato as i thought, this is just slow pitch oscillation, or for a sample the modulation of the playback rate)
lowpass filter
put a highpass on the delay out (edited)
(how to add noise? https://www.kvraudio.com/forum/viewtopic.php?t=499395
The actual saturation curve depends on the tape material, but usually it's some sort of soft-clip sigmoid or double sigmoid (eg. there might be some cross-over distortion too). Magnetic saturation then usually has some hysteresis (not sure how significant this is for tape) and some stochastic "quantisation" thanks to the finite number of particles in the media, so your tape machine would typically add some high frequency signal (eg. 100kHz or higher) as "bias" to try to negate these effects and the bias signal actually has non-trivial effect on the saturation; it's actually pretty obvious even with a simple wave-shaper.
https://www.kvraudio.com/forum/viewtopic.php?t=499395

ive found what i think is the simplest tape echo for supercollider
it bandpasses the delay line output, applies tanh distortion, and adds a little bit of noise to modulate the delay times

http://sccode.org/1-h/fork


Add AsRef impl to TempDir

It would be nice to be able to just pass the tempdir to a function that takes AsRef<Path> as an argument.

Thanks!


Capitalize scholarship/grant winner text server-side.

Changes

Capitalizes "Grant Winner" or "Scholarship Winner" on the server, rather than relying on CSS property. Fixes #3765.

For review: @DoSomething/front-end @aaronschachter

:+1:

:dancer: :shipit:


WIP: transport efficiency models

Description
Adding new methods for calculating the transport efficiency beyond Bruggeman coefficient. This includes:

log square root
log
linear
half volume fraction
Bruggeman
Tortuosity factor

These were taken from 10.1016/j.ces.2007.03.041 and http://dx.doi.org/10.1016/j.coche.2016.02.006
Fixes #2111

Type of change
Please add a line in the relevant section of CHANGELOG.md to document the change (include PR #) - note reverse order of PR #s. If necessary, also add to the list of breaking changes.

[x] New feature (non-breaking change which adds functionality)
[ ] Optimization (back-end change that speeds up the code)
[ ] Bug fix (non-breaking change which fixes an issue)

Key checklist:

[x] No style issues: $ pre-commit run (see CONTRIBUTING.md for how to set this up to run automatically when committing locally, in just two lines of code)
[x] All tests pass: $ python run-tests.py --all
[x] The documentation builds: $ python run-tests.py --doctest

You can run unit and doctests together at once, using $ python run-tests.py --quick.
Further checks:

[ ] Code is commented, particularly in hard-to-understand areas
[ ] Tests added that prove fix is effective or that feature works

I think we should include references to the papers that propose the relations and maybe rename them to align a bit better with the descriptions given in this table by Shen and Chen. There a few more in the table we could include too.

I also feel like tortuosity itself should be a submodel on its own and transport efficiency should use that. This would allow for uploading experimental data and interpolating against porosity.

Hey @isaacsquires really sorry I haven't responded to this yet properly. Had a short holiday over Easter and then been swamped with other work things. I haven't forgotten about it and hopefully look again tomorrow


crosvm support

crosvm is a qemu alternative with a smaller attack surface, and sometimes better virtio support.
To build it, you need either a full checkout of the chromeos development tree, or a checkout containing at least:

chromium.googlesource.com/chromiumos/platform/crosvm
chromium.googlesource.com/chromiumos/third_party/adhd
android.googlesource.com/platform/external/minijail

It builds as a standard Rust project, with cargo build.
Then you can test it with commands like these:
touch /tmp/disk.img
fallocate -zl1G /tmp/disk.img
RUST_LOG=debug ~/src/chromium.googlesource.com/chromiumos/platform/crosvm/target/debug/crosvm \
  run --disable-sandbox --disk /tmp/disk.img --socket $XDG_RUNTIME_DIR/crosvm.sock \
  ~/src/solo5/tests/test_blk/test_blk.virtio

So the virtio image is multiboot-based (multiboot 1), and crosvm hardcodes some offsets based on x86_64 Linux conventions. So either Solo5's loader should match those conventions or crosvm should be updated to read a multiboot header before setting up registers.

That makes sense to me. I'd try and fix crosvm to support multiboot, otherwise we'd have to maintain some kind of virtio-for-crosvm subtarget inside Solo5 which would be a pain.

crosvm matches the 64-bit BOOT PROTOCOL described in https://www.kernel.org/doc/Documentation/x86/boot.txt.
Solo5's multiboot1 header can't be used because multiboot1 is an x86_32 specification, and crosvm only emulates the CPU in x86_64 mode.
It looks like both ends will need patches for a successful boot.

crosvm matches the 64-bit BOOT PROTOCOL described in [...]

Hmm, okay. I guess that makes sense for them since all the(ir) world is Linux. Though you mentioned that crosvm tries to boot our kernels anyway, is that because the Linux boot protocol has no magic number that lets you detect if the thing you're loading supports it?
Here's a thought. Would it be possible for us to build a virtio binary that supports both protocols in the same file? That would be the way to do it, since it doesn't introduce any kind of "sub-target" or compile-time option/setting.

I'll have to look into it. I think it's possible, since the protocols both use their own offsets (through a symbol in the mutiboot case) and headers.
For now my first idea was to chainload Linux->Solo5/Virtio through kexec.

For now my first idea was to chainload Linux->Solo5/Virtio through kexec.

I think some people tried that ages ago and it didn't work. Our virtio code is minimal so tends to get unhappy if anything in the chain-loading process leaves the virtio "hardware" in a non-default state.

After the elf has been loaded in memory, crosvm will skip past the first 200 bytes which may contain some 32-bit initialization code, the freshly initialized cpu seems to slide past any zero instructions (I had trouble debugging that, but I expect that there's just no logic to handle them yet), then it lands on an entry point that follows Linux's startup_64 convention.
As a consequence, our hybrid elf image should put its multiboot header past the text segment.

Though the multiboot header's physical position within the elf should be quite early (first 8192 bytes), it should either be loaded within the first 200 bytes, loaded past the start of the .text section, or not loaded at all. I'll look at what I can do with linker scripts.

Off the top of my head, you could add a .text.linuxboot or somesuch with the Linux entry point into boot.S, then it should just be a case of something like:
    .text :
    {
        *(.text.linuxboot)
        *(.data.multiboot)
        *(.text)
        *(.text.*)
    }

in the linker script. Assuming .text.linuxboot is not so large as to push .data.multiboot beyond 8k, which it shouldn't be.
WDYT?

Yeah, I did that with a jmp and it worked.

Hi @g2p &@mato , Could you share more info about this issue? Will you try to boot the solo5 kernel from the crosvm?


Independent JAR build config and missing resources fixed

The fat jar that was being generated by running gradle jar was not including certain resources causing the GUI to crash. This has now been fixed. Apologies for not spotting this sooner, would be nice to get some tests running ;)
Also started to build independent jar building for zylib, reli and binnavi.
See commit messages for more detail.

Thanks! I added some comments, please take a look.

OK so all of the above is not an issue and can be resolved fairly quickly. Gradle cannot be downloaded by Maven however the gradlew files are a wrapper that can use gradle without the need of installing it. All the user requires Java on their machine.
If the Gradle route is not something you wish not to use then I will cease development on it. Have a think and if you want to use Gradle I will address the above issues, if not then I can do a PR to delete all the Gradle. Let me know either way :)

I discussed this with @cblichmann and we think you should go ahead with the Gradle integration. Please make sure to address the comments and then we will merge your changes. Thank you for putting so much work into this it is greatly appreciated.

+1
So I suggest the following: Keep Maven while you're working on the Gradle files. We should then switch over to Gradle completely. Is the project structure viable for doing this?

I'm at work at the moment so will not get a chance to look until later
tonight.
I think a full switch is viable, but what I suggest is to:

I'll address the comments.
Merge
Feature branch with a full gradle and maven deleted.
Test test test.
Merge. Welcome to gradle.

That way the project stays running and up to date while we get gradle to a
point we're all happy with. :)
On 2 Sep 2015 8:31 am, "Christian Blichmann"<EMAIL_ADDRESS>wrote:

+1
So I suggest the following: Keep Maven while you're working on the Gradle
files. We should then switch over to Gradle completely. Is the project
structure viable for doing this?
—
Reply to this email directly or view it on GitHub
https://github.com/google/binnavi/pull/20#issuecomment-136961460.

Awesome!

For the record, this is what mostly convinced me.

Yes, read that article some time ago and it really illustrates well the difference in verbosity. However, the comments to the article were mostly not that positive towards Gradle. Anyways, I'm fully in support of trying Gradle out as I accumulated too many scars already from Maven :wink: .
So if I interpret https://github.com/google/binnavi/pull/20#issuecomment-136961460 correctly the plan is to move to Gradle as the standard build system and skip Maven altogether?
Then let' s try out how Eclipse handles Gradle. :smiley:

Sounds like a good plan :)

Ok, played around with the current build.gradle and Eclipse. Here my preliminary and negative experiences. Note however that using Gradle from the command line works fine. This is only about the Eclipse integration.

Using the build description in the README, i.e. letting Gradle generate an Eclipse project file and then import everything as a new project into Eclipse leads to some errors concerning the classpath includes/excludes that need manual fixing as described in the Eclipse build with Ant.
This approach also has the drawback that whenever the build.gradle file is changed one needs to regenerate a project file for Eclipse. Guess no need for a reimport though but have not tried. Still think it is a little bit inflexible.
Adding some of the Eclipse Gradle plugins does not work yet. In theory one should  import a new Gradle project into Eclipse using "Import->Gradle->Gradle Project" and everything ought to work out of the box. This would also mean that any change to the buildfile are immediately updated into your Eclipse project.
However, here Eclipse seems to take the resources.include path in the buildfile over the java.exclude and is then missing the main sources in the project. Removing the resources part fixes this but then we miss the resources. So there seems to be a bug that Eclipse takes the resources as source folders if given in the sourcesSet. Googling around did not find a solution yet. Will wait till @lordqwerty latest changes are pulled in and try again or open a bug for that.

For now back to the Ant project for Eclipse. Ooh the build system woes, they never seem to go away ...
On another note there seems to be two different (or more?) Gradle plugins for Eclipse. I tried both and they both have the bug above and do only seem to differ in the UI they have in Eclipse. Does anyone have a recommendation as to what is the Gradle plugin to use in Eclipse?
Bye
Bogdan

Hm, IntelliJ seems to be the new hotness :P
At least that's what Android Studio is based on (which also uses Gradle).

IntelliJ is much better in my opinion. But I will still fix the above
issues.
Sorry for not sorting this sooner worked late and traveling today. Will
have the PR done by tonight.
On 3 Sep 2015 1:33 pm, "Christian Blichmann"<EMAIL_ADDRESS>wrote:

Hm, IntelliJ seems to be the new hotness :P
At least that's what Android Studio is based on (which also uses Gradle).
—
Reply to this email directly or view it on GitHub
https://github.com/google/binnavi/pull/20#issuecomment-137422173.

We're not in a hurry with this. Take as much time as you need.

Yeah no hurry about Gradle, things should be done well. Take your time.
Regarding IntelliJ, yes I know it is the hotness so I might revisit it after years. But switching IDEs is always slow :). On the other hand Eclipse is really pushing one away as hard as possible by times.

Sorry I am not going to have time to do this.


How to build image only if wasn't created yet?

Would be nice to have ability to build new image only if was never created.
Also to have possibility to be created only if version was changed.

Also how to keep locally only latest build (so if image is building then to delete old builds with old volumes)

the latest version of the plugin already supports cleaning up after itself. if it's not doing that, please let us know.


Doesn't quite function when using Bun as a runtime

I'm not 100% sure if it's necessarily the fault of this lib itself but I haven't been too successful in terms of boiling it down as to what exactly is the problem.
Basically if you use the bun runtime using: https://github.com/gornostay25/svelte-adapter-bun suddenly when submitting any form requests the response is stuck pending endlessly.
To reproduce simply swap out the adapter with the one I listed above and run with:
bun --bun run dev, click on the submit button and watch it load forever.
I used this repo to conduct the test and I was using the latest (0.5.2) adapter for bun.

Somewhere within this function the problems start.
https://github.com/ciscoheat/sveltekit-rate-limiter/blob/0466070755d8458f3defb376df33b01888288df2/src/lib/server/index.ts#L406-L409
I even tried commenting out the 2 funtions that reference the event, no success.
The funny part is, it actually works! As in rate-limiting is being applied if exceeded but the response is somehow lost.

Tested with the latest version of everything (on Windows), and this simple page works fine at least:
import type { PageServerLoad } from './$types';
import { error } from '@sveltejs/kit';
import { RateLimiter } from 'sveltekit-rate-limiter/server';

const limiter = new RateLimiter({
	IP: [3, '10s']
});

export const load = (async (event) => {
	if (await limiter.isLimited(event)) throw error(429);
	return {};
}) satisfies PageServerLoad;

If you have a more advanced case that doesn't work, post a link to its repo and I'll take a look.


When preview a big picture, the pic popup covers all the panel

Before Submitting Your Bug Report

[X] I have verified that there isn't already an issue reporting the same bug to prevent duplication.
[X] I have seen the FAQ.

Maccy Version (see 'About' window)
2.0.1
macOS Version
15.0 (24A335)
Maccy Settings
{
    "KeyboardShortcuts_delete" = "{\\"carbonKeyCode\\":51,\\"carbonModifiers\\":2048}";
    "KeyboardShortcuts_pin" = "{\\"carbonKeyCode\\":35,\\"carbonModifiers\\":2048}";
    "KeyboardShortcuts_popup" = "{\\"carbonModifiers\\":4096,\\"carbonKeyCode\\":9}";
    "LaunchAtLogin__hasMigrated" = 1;
    "NSStatusItem Preferred Position Item-0" = 5506;
    "NSStatusItem Visible Item-1" = 0;
    "NSWindow Frame com.sindresorhus.Settings.FrameAutosaveName" = "608 427 510 473 0 0 1680 1025 ";
    SUAutomaticallyUpdate = 1;
    SUEnableAutomaticChecks = 1;
    SUHasLaunchedBefore = 1;
    SULastCheckTime = "2024-09-22 05:45:54 +0000";
    SUSendProfileInfo = 0;
    SUUpdateGroupIdentifier =<PHONE_NUMBER>;
    avoidTakingFocus = 0;
    enabledPasteboardTypes =     (
        "public.html",
        "public.tiff",
        "public.utf8-plain-text",
        "public.png",
        "public.rtf"
    );
    hideFooter = 1;
    historySize = 50;
    ignoredPasteboardTypes =     (
        "net.antelle.keeweb",
        "com.typeit4me.clipping",
        "Pasteboard generator type",
        "com.agilebits.onepassword",
        "de.petermaurer.TransientPasteboardType"
    );
    imageMaxHeight = 20;
    maxMenuItems = 15;
    menuIcon = clipboard;
    migrations =     {
        "2020-04-25-allow-custom-ignored-types" = 1;
        "2020-06-19-use-keyboardshortcuts" = 1;
        "2020-09-01-ignore-keeweb" = 1;
        "2021-02-20-allow-to-customize-supported-types" = 1;
        "2021-06-28-add-title-to-history-item" = 1;
        "2021-10-16-remove-dynamic-pasteboard-types" = 1;
        "2022-08-01-rename-suppress-clear-alert" = 1;
        "2022-11-14-add-html-rtf-to-supported-types" = 1;
        "2023-01-22-add-regexp-search-mode" = 1;
        "2024-07-01-version-2" = 1;
    };
    pasteByDefault = 1;
    pinTo = bottom;
    popupPosition = cursor;
    previewDelay = 1500;
    removeFormattingByDefault = 0;
    showFooter = 0;
    showInStatusBar = 1;
    showRecentCopyInMenuBar = 0;
    showSearch = 1;
    showTitle = 1;
    windowSize = "[450,800]";
}

Description
When copy a big screen shot, such as a whole screen, when preview the pic in the panel, the preview popup covers the maccy panel, and cannot select other items.
The preview popup should appears on the left or right side of the panel, should not appears in front of the panel.

Steps to Reproduce
No response

The right position:

The wrong position:

@p0deje I've tested 2.1.0 release, this is NOT fixed.

That's the default behavior whenever there is not enough space to the left / right of the window to show the preview.

That's the default behavior whenever there is not enough space to the left / right of the window to show the preview.

Oh, I see. Thanks.
But when there is not enough space to the left / right of the window to show the preview, reduce the preview width to make the preview on the left/right may be better?


codes in the lstlisting disorder when crossing pages

When using lstlisting and codes cross two pages, lots of vertical lines appear in the page. And a word, included in the code, will appear in the right-bottom and top-left corners of the page.
Page 1
left side of page:

right-bottom of the page:

Page 2

won't fix /::| /::D /::<

lstlisting sucks, recommend using minted package, here's my configuration.
\RequirePackage[chapter]{minted}	% listings sucks, use minted
\RequirePackage{mdframed}
\mdfdefinestyle{codebox}{
	leftmargin=3em,
	rightmargin=3em,
	innertopmargin=1em,
	innerbottommargin=1em,
	linewidth=0.6pt
}
\newminted{python}{
	linenos=true,
	breaklines=true,
	breakanywhere=true,
	frame=none,
	python3=true,
	fontsize=\zihao{5},
	numbersep=2em,
	style=default,
	tabsize=2,
	xleftmargin=0.5em,
	xrightmargin=0.5em,
	}
\renewcommand{\theFancyVerbLine}{\rmfamily \textcolor{gray}{\zihao{5} \oldstylenums{\arabic{FancyVerbLine}}}}

modify tongjithesis.cls to replace lstlisting

and remember using these environments in tex
\begin{mdframed}[style=codebox]
\begin{pythoncode}
balabala
\end{pythoncode}
\end{mdframed}

and of course, no more this strange issue.

@Alraemon Many thanks. Would you please send me a pull request?


Hue error with SSM

Hue services fail with SSM enabled:

Either the jars are missing or need to be deployed everywhere (like on Hue hosts too). On EQ Staging Hue hosts are located on different machines than the SSM is deployed on
or
We are missing some Hue specific configuration
or
It's a bug and need a debug & fix

To recreate the problem that the BMW users faced, one must go to Hue Web Interface and choose to browse files (the screenshot provided does not show the error, it’s just for clarification how to recreate the steps that will trigger it when SSM is enabled):
(Attached as a .png the error screenshot)

Solution so far:
           Here is a quick update/fix for HUE issue. Please try it in another cluster (We changes too many configurations in that cluster. Please don’t use it currently).

After changing some configurations with Frank, we found that ‘httpfs’ may not work after deploying SSM. This issue leads to HUE issue (HUE’s file browser cannot list files). Because in that test cluster, ‘httpfs’ is configured as HUE’s ‘HDFS web interface role’. Changing this parameter to ‘Namenode’ will solve HUE issue. (Thanks to Frank) 
We also found that copy smart jars to ‘/opt/cloudera/parcels/CDH/lib/hadoop/lib/’ is enough for HUE and HDFS.
           We are still working on find root cause of ‘httpfs’ problem. We hope that we can solve it ASAP. As a careful reminder, we changed lots of configurations in that cluster (e.g., disable Kerberos, which make lots of services down). Please don’t change any configuration until we found root cause of ‘httpfs’ problem.

Problem solved by changing from httpfs to webhdfs. Issue closed.


Deploying guide for AWS Lambda with serverless framework errors on Windows with Prisma 4.0.0

The serverless configuration provided on this page Deploying to AWS Lambdas does not work with version 4.0.0 of Prisma.

Although this initially looks related to https://github.com/prisma/prisma/issues/5023, it is not: That issue describes a problem when running the deployed app, while this is related to what serverless framework is doing during preparation of deploying the code (via serverless package).


ENH: added exercises directive

Hey @mmcky here is my first pass at making an .. exercise directive.
It seems to work pretty well for me, but isn't a totally clean/optimal implementation.
One place where I really had to do something I'm not proud of is in JupyterTranslator.depart_literal_block
Let me explain what I wanted, then I'll try to defend myself...
I wanted the ability to do something like
.. exercise::
   :class: cfu

   This is a check for understanding exercise

   This is a note that has some *italic* and **bold** embedded

   - list
   - in
   - exercise

   .. code-block:: python

      def foobar(x, y, z):
         print(x, y, z)

   And text after the code block

and have the entire exercise block -- code section and everything -- in a single markdown cell inside a <blockquote> element (html name for >).
The issue is that the literal_block handling caused a cell break to happen on either side of each .. code-block. To get around that I do the following:

if I am in depart_literal_block AND am in an exercise AND the literal_block produced a markdown cell (not a code cell)...
Then (and only then) pop that code filled markdown cell off the output, merge it with the current stack of markdown_lines and proceed onwards.

This will cause the .. code-block to be written out to markdown, but then merged with the cell containing the prose for the .. exercise
I don't love the pop part and it seems like it might be fragile, but in my tests is does what I want 🤷♂

hey @sglyon. Thanks -- this will be a great addition.
I'm not sure I fully follow. If we are in_exercise=True could we not just write code-blocks or more accurately literal_blocks as a syntax highlighted markdown? and skipping the inserted breaks? I will use your test to trace the state and look a bit more closely. Thanks!

Hey @mmcky that's a good point and something I wanted to do.
I found it a bit difficult because the (visit|depart)_literal_block methods are in a different class that don't know anything about the exercise node type, so it was hard to convey that state.
My workaround was to let the other class do its thing and then patch it up in the class that did know about exercises.
One other complication is that sometimes I want to just displayed highlighted code in markdown cells, but other times I actually do want a code cell. Right now I'm differentiating between the two cases by passing different language names for the .. code-block:: (b/c my conf.py has python3 associated with a kernel, that one generates the code cells while python generates markdown highlighted code)

ah -- right. thanks for the update @sglyon. That makes sense - the dual class operations are difficult and probably a poor design in some respects - but was done to reduce duplication.
I have run this branch over the quantecon lectures site and doesn't interact with it in any way so I'm happy to merge this as is and we can improve over time.
thanks!


Issue: Autoplay not working in param

I try to use the autoplay=1 params but it doesn't work appropriately.
<YouTube class=" mx-auto max-w-full" params="autoplay=1 id="https://www.youtube.com/watch?v=abc" />

I think this is expected behaviour. This YouTube component is intentionally designed to avoid loading the YouTube iframe until a user interacts with it. This avoids downloading and running lots of code potentially slowing down a page if a user doesn’t need it.
For autoplaying videos, I’d recommend using the YouTube <iframe> directly.


Document rationale

AFAIK the presentation is the only publicly available documentation for the underlying rationale, so might make sense to link to it.

👍


Integrate GHC's new diagnostic infrastructure

In summary, GHC has changed how diagnostics are emitted that may break then further benefit HLint.
I think this integration is unavoidable in the long run. Maybe we can start from a branch that stages GHC HEAD support into HLint?
@ndmitchell Are you happy with this direction? We can start this work pretty soon.
References:

https://github.com/ghc-proposals/ghc-proposals/pull/306
https://gitlab.haskell.org/ghc/ghc/-/wikis/Errors-as-(structured)-values
https://github.com/haskell/haskell-language-server/issues/2014

I'm not sure how this impacts HLint at all. We don't really look at GHC diagnostics other than to pretty print them for parse errors, but that should be a few lines to pretty print a slightly different type instead, so seems a much smaller deal than the changes required for most GHC upgrades. Are you suggesting HLint should emit errors as structured errors? It doesn't at the moment, and I don't see much benefit to doing so. Curious what changes you think are required?

Sorry if these ideas don't make sense, we're still just learning HLint!
My naive thought was that now the compiler errors/warnings are structured and we don't have to manually parse, can we show more suggestions for them? An example that has no original hints that we may add to:
{-| TcRnDodgyExports is a warning (controlled by -Wdodgy-exports) that occurs when a datatype
    'T' is exported with all constructors, i.e. 'T(..)', but is it just a type synonym or a
    type/data family.

   Example:
     module Foo (
         T(..)  -- Warning: T is a type synonym
       , A(..)  -- Warning: A is a type family
       , C(..)  -- Warning: C is a data family
       ) where

     type T = Int
     type family A :: * -> *
     data family C :: * -> *

   Test cases: warnings/should_compile/DodgyExports01
-}
TcRnDodgyExports :: Name -> TcRnMessage

With Name, here we can hint and refactor T(..) to T?

HLint doesn't parse GHC warnings and doesn't suggest refactoring T(..) or similar. You might be thinking of Haskell Language Server (https://github.com/haskell/haskell-language-server), which does the kinds of things you describe. HLS also integrates HLint for some hints, but not all the suggestions given by HLS are driven by HLint - all those related to warnings are in the HLS repo itself. I suggest raising this issue with HLS.

I actually came here from the original task at HLS. I just happen to know people who don't use HLS in their setup (fewer and fewer nowadays though, and for the better!) so it may be fine to cross on simpler things. Let's keep this open until our team gets more familiar with both and comes up with more concrete ideas then.

I think the thing is HLint has never consumed GHC errors, and is unlikely to start, but happy to leave this ticket open if you want.


Configure / Display OST Pools

Allow for the configuration of OST pools.
Show existing pools.

I can work through the backend portion of this.

One thing to note is that any API layer joining between targets and pools should only use resource URIs and basically mirror the database tables.
This is important so warp-drive can be notified of any LISTEN / NOTIFY updates.

Closing in favor of #1460


feat: expand tilde to home dir

Expand ~/ to current user's home directory on unix

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
Attention: Patch coverage is 86.20690% with 4 lines in your changes missing coverage. Please review.

Project coverage is 51.4%. Comparing base (c3f0fc5) to head (db30b07).
Report is 29 commits behind head on master.

Files with missing lines
Patch %
Lines

crates/mirro-rs/src/config/mod.rs
50.0%
2 Missing :warning:

crates/mirro-rs/src/utils/tilde.rs
92.0%
2 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files

Files with missing lines
Coverage Δ

crates/mirro-rs/src/main.rs
0.0% <ø> (ø)

crates/mirro-rs/src/config/mod.rs
53.4% <50.0%> (+0.5%)
:arrow_up:

crates/mirro-rs/src/utils/tilde.rs
92.0% <92.0%> (ø)

... and 1 file with indirect coverage changes


Added api.stop() to support threadicide

Allow the user to cleanly exit the thread from the current script. This partially solves issue #159
See example usage here https://gist.github.com/djnugent/d65e6adb24344dcdf970

Is there any sort of event triggered when the thread dies on its own?

@mrpollo  Nothing special. After a thread ends/dies/suicides it goes here.
https://github.com/diydrones/dronekit-python/blob/master/droneapi/module/api.py#L336
Just a small clean up for keeping track of threads

@djnugent Did you add any API reference for this?
I think until we've got a way to call this "anywhere" (as per #159) that is probably the extent of what we should do. OK?

DK 2.0 won't need this. Sorry @djnugent!

But it had such a catchy name :( I will endure.

:-)


all_random.sh and replace_blocks.sh: No such file or directory

Hello, I'm reproducing your paper, and I want to look into your test scripts to find arguments of db_bench. However, although run.sh exists, all_random.sh and replace_blocks.sh executed in run.sh are not committed.

@Tom-CaoZH You may take a look

Yes, you are right!


Support for multiple variable type declaration in classes?

Currently this doesn't work in Crystal:
class Point
  @x, @y : Int32
end

This doesn't work for structs either:
struct Point
  x, y : Int32
end

Is this a good idea to support?

It'll be difficult to have getter to support this, as getter x, y : Int32 would be recognized as 2 arguments: x & y : Int32, I don't know how the macro getter could determine that x is of type Int32, and not an instance that don't have type defined here..

I'm not sure this would be benefical. In certain situations it would maybe be a bit better than writing it separately but in general you're probable better off writing each property destinctively.

:-1: to this from me too, it doesn't exactly feel like a common case, and just using multiple lines and a bit of duplication isn't really a massive issue.

@Qwerp-Derp you can use your own macros :smile:
macro int32(*args)
  {% for arg in args %}
    {{arg}} : Int32
  {% end %}
end

class Foo
  int32 @x, @y, @z

  def initialize(@x, @y, @z)
  end
end

foo = Foo.new(1,2,3)
pp foo # => #<Foo:0x... @x=1, @y=2, @z=3>

https://carc.in/#/r/2kkm
I'm also using some personal macros like static:
macro static(m)
  class_{{m}}
end
class MyClass
  static property valor = 0
end

https://github.com/crystal-lang/crystal/issues/4689
I love Crystal macros  :heart_eyes:

Maybe I'm using crystal macros too much :sweat_smile:

So, despite the two downvotes in @faustinoaq, he's right that this could easily be a macro, especially a more generic one:
macro decl(*args)
  {% ty = args[-1] %}
  {% vars = args[0...-1] + [ty.var] %}
  {% for var in vars %}
    {% if ty.value.is_a? Nop %}
      {{ var }} : {{ ty.type }}
    {% else %}
      {{ var }} : {{ ty.type }} = {{ ty.value }}
    {% end %}
  {% end %}
end

class X
  decl @a, @b : Int32 = 1
  decl @c, @d : Int32

  def initialize(@c, @d)
  end
end

https://carc.in/#/r/2kv6/

Oh sure it's possible but I don't think people should be introducing nonstandard macros into their projects when the alternative is so little extra typing.
I don't think people should overdo DRY in general.


table_exists runs a query in the database

I noticed that this implementation: https://github.com/ploomber/jupysql/blob/d721d56d0975d3a6e78dce366a0c5bfa1deeead1/src/sql/util.py#L162
runs a query even when the user passes the with argument. This is inefficient since the with arguments will lead to building a CTE that might take a lot to run. Do we actually need this?
Isn't checking table_name in store enough? We can assume that if a user ran a --save table_name argument, then running --with table_name won't lead to any "table not found error" since the declaration exists (it's not a table but it's a CTE). Am I missing anything?
There is another side effect: if the definition isn't valid SQL.
%%sql --save table_name --no-execute
not valid SQL

If we ran the cell above, table_exists will return false because the query is wrapper in a try, catch statement, which will cause the "table_name does not exist" error to be displayed, which is misleading because the error is that the SQL code isn't valid, not that the table doesn't exist.
I feel like table_name in store should be enough, but perhaps I'm missing something here @yafimvo

Yes, good point. Adding this will make it more efficient and notify the user with a better error message.
I added this logic to this PR.
Since now, if the table exists and the correct --with was provided, we should be able to reproduce the error from this issue. If we remove this line  -- remove top 1% outliers for better visualization we should be able to get the plot, however, it fails with a different error which I'm not sure is related to these changes.
Reproduce
Running these 2 code cells:
%%sql --save many_passengers --no-execute
SELECT *
FROM taxi
WHERE passenger_count > 3
-- remove top 1% outliers for better visualization
AND trip_distance < 18.93

%sqlplot histogram --table many_passengers --column trip_distance --with many_passengers

Should return this TypeError (works OK)
TypeError: %o format: an integer is required, not dict

But running these cells should return a plot without any errors
%%sql --save many_passengers --no-execute
SELECT *
FROM taxi
WHERE passenger_count > 3
AND trip_distance < 18.93

%%sql --save many_passengers --no-execute
SELECT *
FROM taxi
WHERE passenger_count > 3
AND trip_distance < 18.93

But it returns this error:
ProgrammingError: (pymysql.err.ProgrammingError) (1064, 'You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near \'"many_passengers"\' at line 9')
[SQL: WITH `many_passengers` AS (
SELECT *
FROM taxi
WHERE passenger_count > 3
AND trip_distance < 18.93)
SELECT
    MIN("trip_distance"),
    MAX("trip_distance")
FROM "many_passengers"]
(Background on this error at: https://sqlalche.me/e/14/f405)

I think it is something with the query format we try to run:
This was the previous format (working)
%%sql
WITH `many_passengers` AS (
SELECT *
FROM taxi
WHERE passenger_count > 3
AND trip_distance < 18.93)
SELECT
    MIN("trip_distance"),
    MAX("trip_distance")
FROM "many_passengers"

This is the current one (failing)
%%sql
WITH many_passengers AS (
    SELECT *
    FROM taxi
    WHERE passenger_count > 3
    AND trip_distance < 18.93)
SELECT
MIN(`trip_distance`),
MAX(`trip_distance`)
FROM `many_passengers`

@edublancas

I fixed the errors you're encountering in https://github.com/ploomber/jupysql/pull/362,
the issue is that having % o was interpreted as a parameter interpolation in the SQL driver, so passing a .text object to the .execute function tells SQLAlchemy to interpret the query as a literal string, instead of a parameterized one.
The other error you described is because some drivers need backticks, so I changed them to use them depending on the dialect. Looks like it fixed all the problems but I'll merge the PR and try to reproduce your findings to see if we're covered.

fixed in https://github.com/ploomber/jupysql/pull/361


[SCB-1668] Replace sun.misc.BASE64* with java.util.Base64

sun.misc.BASE64Decoder not available on Java 9

Coverage increased (+0.02%) to 80.048% when pulling b57052b69d2842188a0bf207954402135cce0ec7 on coolbeevip:SCB-1668 into 184e9c0bfb2ca73d7acfa15443acba210bb92927 on apache:master.


Creating the POST version of the /edit/<page_name> route

This was challenging because I was unable to get the page to save the changes properly. I ended up realizing that I had the wrong variable names being passed around. I wasn't properly checking for authentication due to a variable name issue. After I fixed that, I found that my code was appearing to work properly when running the debugger, but I was unable to see the changes I made in the file that was supposed to be edited. It turned out that I was writing to the wrong file in the POST route code. I ended up writing it to the root directory for the flask-blog. I ended up fixing this by putting a correct relative path indicating which subdirectory the file should be written to. This worked out to be okay, except that the file that gets written contains an excessive amount of white space.

Excessive amount of whitespace fixed. It ended up being the textarea content having excessive white spaces surrounding the text-to-be-outputted variable as well as the textarea POST value sending additional line-breaks implicitly, which ended up adding a line break between lines automatically upon saving each edit.


Year is maxing out at 2024

Hey this is an awkard one.
I am passing in a date for year 2025 but the date picker is maxing out at 31 Dec 2024.

Version: 2.10.1

Right I see I have to set a max. Any thoughts on making the max default higher then the current year?

No, sorry, think the current default is ok. I don't think it would be worth a breaking change


fix(#1276): Textarea padding

:tada: This PR is included in version 4.12.2 :tada:
The release is available on:

npm package (@BUGFIX dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.12.2 :tada:
The release is available on:

npm package (@BUGFIX dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[WIP] Refactor tests, change mutation API, and rerun query on state change

This PR does a few things (it can be split up if needed).

[x] Queries re run on when the redux state (aside from apollo) change
[ ] mapMutationsToProps rebuild on change
[ ] update Changelog.md
[x] diff queries before rerunning to see if they have changed
[ ] cut release candidate for people to test in examples

cc @stubailo @johnthepink

I think I would prefer { ownProps, state } to be the first argument, not the last, because then it's a lot more consistent to find. I think this might get messy when you start having optional arguments in the mutations.

diff queries before rerunning to see if they have changed

What does this mean?

@jbaxleyiii wait, did we ever decide that rebuilding the mutation functions on each re-render wouldn't work? Is there a downside to that approach, which wouldn't require changing the API to add extra arguments?

@stubailo since we rerun the mapQueriesToProps whenever prop or state changes, I am adding in a check to see if the resulting queries have changed. If not, I don't unsubscribe and rebuild them. So its a performance check to not handle all of the query lifecycle again for no reason.
I can rebuild the mutation functions on each re-render (I have it mostly done). The reason I diverged from that to the { state, ownProps } as arguments was around the use case. Since mutations don't happen on their own (i.e. have to be called within the child component), I thought it would be more efficient to pass the state and props only at execution of the mutation. We can make them first or last for sure. My thought with last was in cases like so:
mapMutationsToProps = () => ({
  action: (my, args) => { // MutationObject }
})

// vs unused `{ ownProps, state }`
mapMutationsToProps = () => ({
  action: ({ ownProps, state }, my, args) => { // MutationObject }
})

Thoughts?

Thx for the update. Any interface that you guys decide is just great, but if I was to do it maybe would be with something like:
const mapMutationsToProps = () => ({ state, ownProps }) => ({
  action: (my, args) => { ... }
});

It is much closer to the original one, it feels more natural...
Also, arguments called in runtime my and args (not sure if this is the case, but it is like raw in the docs right?) should be separate from state and ownProps, and like this seems clearer to me.

Thanks for the feedback! I think that's one of the points behind this change in my mind. my and args are called at runtime, but you also want the current props and state to mutation execution as well.
Keeping it as the current API is possible! I'll do a comparison branch and try to add in a performance test to see if my concerns about rebuilding the mutations each time is valid or not! (We are rebuilding queries each time so it's probably nothing!)

Ehhh, I'll just rewrite to keep the same API. The plumbing is there already and the execution won't be that much, if any perf loss.

Sounds good to me!

@jbaxleyiii looks great to me! :shipit:

I think something broke =[. When I upgrade to 0.3.4 it is taking away too much time to start the app or really do anything at all. The xcode console (I'm using react native) is just spiting this:
equalObjects@http://localhost:8081/index.ios.bundle?platform=ios&dev=true:69878:31
baseIsEqualDeep@http://localhost:8081/index.ios.bundle?platform=ios&dev=true:69668:20
baseIsEqual@http://localhost:8081/index.ios.bundle?platform=ios&dev=true:69610:23
equalObjects@http://localhost:8081/index.ios.bundle?platform=ios&dev=true:69878:31
baseIsEqualDeep@http://localhost:8081/index.ios.bundle?platform=ios&dev=true:69668:20
baseIsEqual@http://localhost:8081/index.ios.bundle?platform=ios&dev=true:69610:23
equalObjects@http://localhost:8081/index.ios.bundle?platform=ios&dev=true:69878:31
baseIsEqualDeep@http://localhost:8081/index.ios.bundle?platform=ios&dev=true:69668:20
baseIsEqual@http://localhost:8081/index.ios.bundle?platform=ios&dev=true:69610:23
isEqual@http://localhost:8081/index.ios.bundle?platform=ios&dev=true:70038:19
http://localhost:8081/index.ios.bundle?platform=ios&dev=true:69118:12
dispatch@http://localhost:8081/index.ios.bundle?platform=ios&dev=true:68541:13
dispatch@http://localhost:8081/index.ios.bundle?platform=ios&dev=true:82792:21
http://localhost:8081/index.ios.bundle?platform=ios&dev=true:71511:21
dispatch@http://localhost:8081/index.ios.bundle?platform=ios&dev=true:68892:17
fetchQuery@http://localhost:8081/index.ios.bundle?platform=ios&dev=true:73879:20
startQuery@http://localhost:8081/index.ios.bundle?platform=ios&dev=true:73933:16
http://localhost:8081/index.ios.bundle?platform=ios&dev=true:73777:29
subscribe@http://localhost:8081/index.ios.bundle?platform=ios&dev=true:78901:58
subscribe@http://localhost:8081/index.ios.bundle?platform=ios&dev=true:73702:39
handleQueryData@http://localhost:8081/index.ios.bundle?platform=ios&dev=true:69220:40
subscribeToAllQueries@http://localhost:8081/index.ios.bundle?platform=ios&dev=true:69163:21
componentWillMount@http://localhost:8081/index.ios.bundle?platform=ios&dev=true:69085:27
mountComponent@http://localhost:8081/index.ios.bundle?platform=ios&dev=true:15996:24

Could this be deep equal failing on a circular reference or something?

@deoqc could you make a reproduction repo I can debug?

It may be a circular reference, or the way I'm rebuilding queries when props / state change is getting stuck in a loop

I found my mistake. Sorry!
But it could have a test and a nice error message for this.
I think will be a common mistake, if it is indeed a mistake - I had this code in 0.3.3 and didn't crash:
const mapMutationsToProps = () => ({
  myBuggyMutation: (myVariable) => ({
    mutation: gql`
      mutation myMutation($myVariable: String!) { # --> same name here
        myMutation (myVariable: $myVariable) # --> and here
      }
    `,
    variables: {
      myVariable,
    },
  }),
});

So I replaced it for:
const mapMutationsToProps = () => ({
  myCorrectMutation: (myVariable) => ({
    mutation: gql`
      mutation onMyMutation($myVariable: String!) { # --> different name here
        myMutation (myVariable: $myVariable) # --> and here
      }
    `,
    variables: {
      myVariable,
    },
  }),
});

Also @deoqc can you post a new issue for this?

@deoqc that's definitely a bug!


Button role-based visibility rules do not work in UI Service

Hi, I would like to report the following bug:
We are running Manage IQ petrosian-1.20230912222549_a07cb46 in a docker container. However, we have experienced this behaviour even before in version Najdorf.
The thing is that when I create a button and set its visibility to one role, it works in classic UI but it is completely ignored in /ui/service
How to reporoduce:

I have created user1 and user2
Created groups user1_group and user2_group
Created user1_role and user2_role and assigned them accordingly to the user and group

I have created a test button and set the visibility to user1_role

Now, user1 should see the button and user2 should not.
In classical UI it works:
user1:

user2:

However in UI Service, the button is shown to both users nevermind the visibility settings.
user1:

user2:

@GilbertCherrie Can you please take a look at this one?

Yeah I can take a look.