Unable to export GPG key

Behaviour
Steps to reproduce this issue

Set your GitHub secrets:

${{ secrets.GPG_PRIVATE_KEY }}
${{ secrets.GPG_PASSPHRASE }}
${{ secrets.GPG_KEY_ID }}

Configure a GitHub action like so

      - name: Import GPG key
        uses: crazy-max/ghaction-import-gpg@v5
        with:
          gpg_private_key: ${{ secrets.GPG_PRIVATE_KEY }}
          passphrase: ${{ secrets.GPG_PASSPHRASE }}
          fingerprint: ${{ secrets.GPG_KEY_ID }}

      - name: Export GPG key to legacy format
        run: gpg --export-secret-keys > ~/.gnupg/pubring.gpg

Run the action

Expected behaviour
GPG should export the specified GPG key into ~/.gnupg/pubring.gpg
Actual behaviour
The import step completes successfully, but exporting the key does not.  Below is what is shown:
  Run gpg --export-secret-keys > ~/.gnupg/pubring.gpg
  gpg --export-secret-keys > ~/.gnupg/pubring.gpg
  shell: /usr/bin/bash -e {0}
gpg: key 3542E92F08CF2673973F54E25347ACDAC05744B8: error receiving key from agent: Inappropriate ioctl for device - skipped
gpg: 672E6CBF977A40F508F88F4CBBE8211E927B068C: error receiving key from agent: Inappropriate ioctl for device - skipped
gpg: WARNING: nothing exported
Error: Process completed with exit code 2.

Note: I know it shows I used crazy-max/ghaction-import-gpg@v5, but before that version, I tried the latest v5.2.0.

Haha, I guess it didn't make a difference to block out that information. 😛
Configuration

Repository URL (if public): https://github.com/jdstone/helm-charts
Build URL (if public): https://github.com/jdstone/helm-charts/actions/runs/4522300214/jobs/7964665430

name: Release Charts

on:
  push:
    branches:
      - main

jobs:
  release:
    runs-on: ubuntu-latest

    permissions:
      contents: write

    steps:
      - name: Checkout
        uses: actions/checkout@v3
        with:
          fetch-depth: 0

      - name: Configure Git
        run: |
          git config user.name "$GITHUB_ACTOR"
          git config user.email<EMAIL_ADDRESS>
      - name: Install Helm
        uses: azure/setup-helm@v3
        with:
          version: v3.8.1

      - name: Import GPG key
        uses: crazy-max/ghaction-import-gpg@v5
        with:
          gpg_private_key: ${{ secrets.GPG_PRIVATE_KEY }}
          passphrase: ${{ secrets.GPG_PASSPHRASE }}
          fingerprint: ${{ secrets.GPG_KEY_ID }}

      - name: Export GPG key to legacy format
        run: gpg --export-secret-keys > ~/.gnupg/pubring.gpg

      - name: Add dependency chart repos
        run: |
          helm repo add jdstone https://charts.jdstone.dev

      - name: Run chart-releaser
        uses<EMAIL_ADDRESS>        with:
          charts_dir: charts
          config: cr.yaml
        env:
          CR_TOKEN: "${{ secrets.GITHUB_TOKEN }}"

Logs
logs_47.zip

I'm having this exact issue with v5 and latest ubuntu (which I believe is 20.04) on github action runners. What was the workaround?
@crazy-max I've seen numerous comments from you around this exact error and I've regenerated the keys twice but the issue still persists.

Alright, turned out to be a simple case of the name of the secret being a typo, so passphrase was coming up as empty and gpg was prompting for it.


Reader monad

A reader monad with some simple test cases

I believe the test cases in the Writer Spec should port over with very little resistance.

It's missing the global functions ask and asks.

@CodaFi Any thoughts about the ask/asks api? I tried to match as closely as I could to Haskell mtl in Swift.

@CodaFi Latest commit with update based on your comments.

:+1: Give it the old rebase and we're good to go

Rebased from master now. After tests pass should be all ready to go. :)

:fire:
:boat:


Setup project and wireframe design

Created a branch feature.
Set up the project with webpack bundler.
Design the project with wireframe guide.
Check linter errors.

Hi @BranBayou,
While you made a great effort in this project, unfortunately, I cannot proceed to review your code.
Invalid Code Review Request
You have submitted a project, that is invalid because the branch name is not descriptive, we can rename our PR branch to for example, leaderbpard_setup, etc
Your Code Review Request will be marked as invalid in your Dashboard, so please submit a new one once you are ready 🙏
Cheers and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, remember to tag me in your question so I can receive the notification.
Please, do not open a new Pull Request for re-reviews. You should use the same Pull Request submitted for the first review, either valid or invalid unless it is requested otherwise.

Invalid Code Review Request does not count into the code reviews limit.


Initial draft of testing documentation

For https://github.com/tempestphp/tempest-app/pull/8 I wanted to add documentation about testing. This is ofcourse far from complete, but I hope this is a good start. I think next up could be the following subjects:

Console commands
Mocking objects
Interacting with the container
Database migrations
Using the clock to change time

Yes, very good start!


My business requires batch processing of messages. Currently, the Consumer can only provide one callback at a time. Can I open up chan (msgs)? I want to handle message callbacks myself

just return rabbitmq.Manual like this:
func handler(d rabbitmq.Delivery) rabbitmq.Action {
  	// record message
	push(d)

	return rabbitmq.Manual
}

and use d.Ack(true) by yourself.


The 'Build your IoT Edge solution' section is missing a step

The tutorial instructs the user to change the name of the module from SampleModule to CSharpModule. The user must also then change the names in the Edge Hub routes. That is the missing step. Without this step, the routes will be incorrectly setup and the messages will not be routed correctly.
The user needs to change SampleModule to CSharpModule in the following lines in deployment.template.json.
"sensorToSampleModule": "FROM /messages/modules/tempSensor/outputs/temperatureOutput INTO BrokeredEndpoint("/modules/SampleModule/inputs/input1")",
"SampleModuleToIoTHub": "FROM /messages/modules/SampleModule/outputs/output1 INTO $upstream"

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

ID: 181d5562-f8d7-9c59-85ea-09efbe397f3e
Version Independent ID: dbedd952-a050-286e-c951-4529ec8e87b8
Content: Azure IoT Edge C# tutorial
Content Source: articles/iot-edge/tutorial-csharp-module.md
Service: iot-edge
GitHub Login: @kgremban
Microsoft Alias: kgremban

Hi @dsajanice - Thank you for your feedback! We have assigned this issue to the author to investigate further and take the right course of action.

@dsajanice I can't reproduce this experience. When I create a new IoT Edge solution, and replace the default SampleModule with CSharpModule, the deployment.template.json is built with my module name. Are you changing the module name after the new IoT Edge solution is created?

@kgremban I see. I think you're right. I must have changed the name after I created the solution. Sorry about the mistake. Closing this..


Integrate draw.io

should be a plugin that enhances the editor similar to the existing math-plugin.

can be done with shortcode plugin


Fix unit tests for normal precision decay methods

What does this PR implement/fix?
Previously around when v0.4.14 was released, normal precision decay() and cumulative_decays() unit tests started failing on GitHub Actions and conda-forge feedstock CI. I couldn't reproduce these failures locally (tried Windows, MacOS, Ubuntu and using the CI Docker images locally), but the cause is clearly floating point error build up. The modifications for release 0.4.14 were independent of the failures, so I guess the origin is changes in NumPy/SciPy, their underlying libraries or with the CI settings somewhere.
This commit introduces a new dict_assert_almost_equal() function within the tests, which uses math.isclose() to check if two floats are almost equal. Found rel_tol=1e-13, abs_tol=1e-30 were reasonably tight tolerance settings for the allowed float difference.
Fixes Issue
N/A
Other comments?
One for the future: dict_assert_almost_equal() could do with showing a better traceback if an assertion fails, i.e. it should show the two floats and the nuclide key that caused the failure.

Codecov Report

Merging #84 (14608e5) into main (31d3fd0) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #84   +/-   ##
=======================================
  Coverage   99.76%   99.76%
=======================================
  Files           7        7
  Lines         854      854
=======================================
  Hits          852      852
  Misses          2        2

Flag
Coverage Δ

unittests
99.76% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out 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 31d3fd0...14608e5. Read the comment docs.


Potential usage with wasm?

Hi, I'm currently trying to evaluate if I could port an application of mine to wasm. One of the requirements is being able to read a lot of files from a folder. So I'm wondering if dropping an archive in the web app could do it.
I'm not familiar with tar-rs, mostly exploring options so sorry if the question doesn't fit the scope of the lib. Basically, do you think tar-rs could be used with wasm-bindgen (web_sys in particular which has a notion of File, Blob, etc.)?

It sort of depends on what you want to do, but it is in theory compatible. You won't be able to use functions like unpack and such, but iteration, creation, and reading archives all works with arbitrary Read/Write types which can be implemented for wasm for types like Blob and such.

In my current "normal" program, I have a folder with the following structure:
folder/
  - list-imgs.txt  (each line contains something like: `0 img/0.png`)
  - img/
    - 0.png
    - ...

Basically my program takes the file list-imgs.txt as an argument and then process all the images listed in it, starting by loading them with the image crate.
From what I understand, the first step would be to try to load them from the archive directly. I might have to copy the archive entries into a map of bytes. Then I have to verify that I can use the image crate to read from bytes instead of from a file. Checking wasm compatibility will only happen after all this is sorted out.
Thanks for the answer! I'll try it out when I find some time, and I'll let you know if I eventually manage to have a minimalist wasm example usage.


swcli dataset copy hungup when the dataset is big

Describe the bug

It doesn't raise any error or finish with a success tip for tens of miniutes
To Reproduce
grailqa dataset
Expected behavior
show some tips or make it faster
Environment

it makes the loading slow because of the type inference of huge data
https://github.com/star-whale/starwhale/blob/8aeaf0e3384a56c5f82ebced371a1c3eef0b8c9b/client/starwhale/api/_impl/data_store.py#L599-L605


Update references

Old references such as TD-Tutorial should not be used anymore. Make a reference to the current practise document.

I think the following link to should stay in..

the bindings specs for the WoT IG plugfest

Agree removing TD-Tutorial link


Cannot copy image from chat to other places (Request)

When trying to drag and drop image to site or copy image to other place than "Teams" - it does not work.
Workaround - download image, open it and then use it with drag and drop or copy.

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

ID: 41ddf8ce-fda9-ee9d-d96a-801f9a2f66b7
Version Independent ID: 9aa5a49f-c440-95a8-83a1-9d38bdaeda39
Content: Known issues for Microsoft Teams
Content Source: Teams/Known-issues.md
Service: msteams
GitHub Login: @LolaJacobsen
Microsoft Alias: lolaj

Hi @Kosmosas , thank you for your feedback.
Are you talking about copy or drag and drop from Teams outside Teams, right?

@Kosmosas  Thank you for submitting this feedback.
From our understanding the issue has been resolved. If you feel it hasn't been resolved please re-open this issue.

@officedocsbot close


feat(multi-module): splitted to modules

ref: #13
ref: #26
@h1alexbel take a look, please

PR-Codex overview
The focus of this PR is to refactor the cli and server codebases to separate concerns and improve maintainability.
Detailed summary

Moved server-related logic to server crate
Created a Server struct to handle server setup and start
Updated main.rs in cli to use the Server struct
Added a test for creating the server in server

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

@h1alexbel does it make any sense to have fakehub- prefix inside of fakehub workspace? Don't get it, can you explain?

@l3r8yJ let's drop the prefix then

@h1alexbel take a look, please

@l3r8yJ let's stay with default clippy configuration for now

@h1alexbel in general PR is ready and you can review it, but I have small problem with build. While i'm trying to find WA, i've posted a question on SA, hope someone will answer sooner than I'll fix it by myself

@h1alexbel take a look, please


Dynamic bottomOffset not respected when switching between inputs

Describe the bug
When I switch focus from one input to another and change the bottom offset used for my <KeyboardAwareScrollView> it doesn't seem to actually use the new offset. You can see in the code snippet below how I change the offset when I focus the second input. If I focus the second input directly everything works. But if I first focus the top input, and then go directly to focus the second one the offset seems to stay at 30
Code snippet
This is obviously just parts of the code. See the linked repo for the full implementation
export default function AwareScrollView() {
  const [bottomOffset, setBottomOffset] = useState(30);

  return (
    <KeyboardAwareScrollView
      bottomOffset={bottomOffset}
      contentContainerStyle={styles.content}
    >
        <TextInput /* ... */ />

        <TextInput
          // ...
          onBlur={(e) => {
            setBottomOffset(30);
          }}
          onFocus={(e) => {
            setBottomOffset(90);
          }}
        />
    </KeyboardAwareScrollView>
  );
}

Repo for reproducing
https://github.com/Tobbe/rnkc-bottom-offset
To Reproduce
Steps to reproduce the behavior:

Run the app in the repo above
Press the password input field. Notice how the full button is visible above the keyboard
Press the lorem ipsum text to dismiss the keyboard
Press the email input field
Press the password input filed.
Notice how the full button is not visible

Expected behavior
I expect the full button to always be visible after switching focus to the password input field
Screenshots
Here's a video of the behavior I'm seeing
https://github.com/user-attachments/assets/a6cec0a0-aa9b-4208-9a00-319f1f6b9f94
Smartphone (please complete the following information):

Desktop OS: Latest MacOS
Device: Android Emulator
OS: Android 15
RN version: 0.76.5
RN architecture: old
JS engine: Hermes
Library version: 1.15.1

Additional context
In this particular example I can just keep the offset to always be 90. But with more input fields, or just more text above the first one, always doing 90 (or more) feels like too much
Another workaround that kind of works is to also change the bottom offset when the text changes. So as soon as the user starts typing in the password input field the log in button scrolls into view.
onChangeText={(text) => {
  setBottomOffset(90);
  setPassword(text);
}}

for example if you have validation errors that shift layout down

This is a good point! I haven't thought much about that yet. Let me play around a bit with error and how I display them in my app and see what I come up with

Do you think this could be caused by maybeScroll not being passed as a hook dependency? I'm facing kind of the same issue now, where bottomOffset is changing dynamically.
From what I see, this hook picks up the maybeScroll function only at the very first renderer, and although subsequent changes to values recreate the function, it is not (passed to / updated in) this hook.
src/components/KeyboardAwareScrollView/index.tsx
    useAnimatedReaction(
      () => input.value,
      (current, previous) => {
        if (
          current?.target === previous?.target &&
          current?.layout.height !== previous?.layout.height
        ) {
          const prevLayout = layout.value;

          layout.value = input.value;
          scrollPosition.value += maybeScroll(keyboardHeight.value, true);
          layout.value = prevLayout;
        }
      },
      [],
    );

useAnimatedReaction(
      () => input.value,
      (current, previous) => {
        if (
          current?.target === previous?.target &&
          current?.layout.height !== previous?.layout.height
        ) {
          const prevLayout = layout.value;

          layout.value = input.value;
          scrollPosition.value += maybeScroll(keyboardHeight.value, true);
          layout.value = prevLayout;
        }
      },
      [],
    );

I think this code should detect only "input grow" event (at least it was originally designed to do that) 🤔
Input switching gets handled in useSmoothKeyboardHandler. And if you change bottomOffset, then maybeScroll gets called first (when input was changed via worklet) with not yet updated bottomOffset value. I think it's what causing the bug 👀


Test Explorer not showing all tests when sharding tests

Describe the Bug
I just installed karma-parallel in my project to launch tests in parallel. When I launch more than one executor the tests are split in several browsers, but in the test explorer I can only see the tests that are launched in one of the browsers. In the output I can see that there are tests with id=specN where N is a number from 0 to N for each of the browsers that have been skipped.
Steps to Reproduce the Behavior

Have an Angular project with tests that works properly
Install karma-parallel
Execute the tests in more than one executor.
Se how the test explorer does not show all the tests.

Describe the Expected Behavior
The test explorer should show all tests even if they are in different browsers, as it does if you run the tests with "ng test".
Provide Debug Logs
***Karma Test Explorer:
[2023-01-30 12:15:35.694] [INFO] [MainFactory]: Using test framework: jasmine (auto-detected)
[2023-01-30 12:15:35.890] [INFO] [DefaultTestManager]: Using requested --> available karma port: 9976 --> 9976
[2023-01-30 12:15:35.892] [INFO] [DefaultTestManager]: Using requested --> available karma listener socket port: 9999 --> 9999
[2023-01-30 12:15:35.900] [INFO] [KarmaTestServer]: Starting karma server
[2023-01-30 12:15:35.958] [INFO] [KarmaTestListener]: Waiting for Karma to connect on port 9999
[2023-01-30 12:16:03.714] [INFO] [KarmaTestListener]: Established new connection with Karma on port 9999
[2023-01-30 12:16:07.005] [INFO] [DefaultTestManager]: Discovering tests
[2023-01-30 12:16:11.137] [WARN] [KarmaTestEventProcessor]: Ignoring duplicate result for already processed test result. Processed test: id='spec0', status='Skipped'. Duplicate test: id='spec0', status='Skipped'
[2023-01-30 12:16:11.251] [WARN] [KarmaTestEventProcessor]: Ignoring duplicate result for already processed test result. Processed test: id='spec1', status='Skipped'. Duplicate test: id='spec1', status='Skipped'
[2023-01-30 12:16:11.252] [WARN] [KarmaTestEventProcessor]: Ignoring duplicate result for already processed test result. Processed test: id='spec0', status='Skipped'. Duplicate test: id='spec0', status='Skipped'
[2023-01-30 12:16:11.278] [WARN] [KarmaTestEventProcessor]: Ignoring duplicate result for already processed test result. Processed test: id='spec2', status='Skipped'. Duplicate test: id='spec2', status='Skipped'
[2023-01-30 12:16:11.341] [WARN] [KarmaTestEventProcessor]: Ignoring duplicate result for already processed test result. Processed test: id='spec3', status='Skipped'. Duplicate test: id='spec3', status='Skipped'
[2023-01-30 12:16:11.344] [WARN] [KarmaTestEventProcessor]: Ignoring duplicate result for already processed test result. Processed test: id='spec2', status='Skipped'. Duplicate test: id='spec2', status='Skipped'
[2023-01-30 12:16:11.350] [WARN] [KarmaTestEventProcessor]: Ignoring duplicate result for already processed test result. Processed test: id='spec1', status='Skipped'. Duplicate test: id='spec1', status='Skipped'
[2023-01-30 12:16:11.373] [WARN] [KarmaTestEventProcessor]: Ignoring duplicate result for already processed test result. Processed test: id='spec0', status='Skipped'. Duplicate test: id='spec0', status='Skipped'
[2023-01-30 12:16:11.407] [INFO] [KarmaTestExplorer]: Finished loading tests in 35.70 secs (13 tests loaded)

***Karma Server:
------------------------------------
Karma Test Explorer: Launching Karma
------------------------------------

30 01 2023 13:15:43.432:INFO [framework:karma-parallel]: sharding specs across 4 browsers

30 01 2023 13:16:04.094:INFO [launcher]: Launching browsers rchrome, rchrome, rchrome, rchrome with concurrency unlimited

30 01 2023 13:16:04.102:INFO [launcher]: Starting browser chrome via Remote WebDriver

30 01 2023 13:16:04.123:INFO [launcher]: Starting browser chrome via Remote WebDriver

30 01 2023 13:16:04.126:INFO [launcher]: Starting browser chrome via Remote WebDriver

30 01 2023 13:16:04.146:INFO [launcher]: Starting browser chrome via Remote WebDriver

30 01 2023 13:16:06.934:INFO [Chrome 94.0.4606.61 (Linux x86_64)]: Connected on socket Q78ziEoXVTmDZ8tyAAAH with id 73218511

30 01 2023 13:16:06.986:INFO [Chrome 94.0.4606.61 (Linux x86_64)]: Connected on socket BoLVoYtRbh6arPSZAAAE with id 53204062

30 01 2023 13:16:06.995:INFO [Chrome 94.0.4606.61 (Linux x86_64)]: Connected on socket dzS-f9rdgE_i9wgfAAAF with id 82118754

30 01 2023 13:16:06.998:INFO [Chrome 94.0.4606.61 (Linux x86_64)]: Connected on socket o1PkuJQ89L4nIy2wAAAG with id 22447646

TOTAL: 0 SUCCESS

Please Provide the Following Information

OS: Ubuntu 22.04
Node Version: v16.18.1
VS Code Version: 1.74.3
Karma Version: 6.3.20
Frameworks: Angular

@sbachiller this is very similar to the limitation in #32. See my comment there on adding multi-browser support.

Please reopen if you would like to contribute this feature.


What are the features of Apache AGE Viewer?

Really wondering the featuers

very excited for apache viewer project

Bitnine used Apache AGE Viewer to implement its graph database as a service.
https://bitnine.net/ag-cloud/

Excited to paticipate! Is there any guidance to start?

Fast analysis and real-time data processing.
Can be provided as an extension to PostgreSQL.

Interested in getting started

Look forward to getting started

Ready to get started !

Feeling great to be a part of this.

Ready to get started!

I am ready to get started.

i'm very excited for apache viewer project

Ready to get started.

Hey, I'm interested in contributing.

Hi, I'm interested.

Hello everyone, I'm gonna share some useful information regarding the features of AGE Viewer.
The fundamentals of AGE Viewer can be seen on AG Cloud Express available at agcloud.bitnine.net
AG Cloud Express is a cloud-based graph visualization software that introduces graph analytical experience for graph beginners. Within the software includes AG Viewer, the core tech AGE Viewer will take root from and evolve.
The features inside the AG Cloud Express includes:

Built in datasets (Projects) like Movies data and Fraud Detection
Understanding graph db and cypher
advanced cypher tutorial

The link below tells you how to login, add a new project (sample datasets), where to type in cypher queries, and other features available at the AG Viewer.
https://bitnine.net/blog-useful-information/tutorial-ag-cloud-express-movies/
If you need a video tutorial for better understanding, refer to the video below.
https://bitnine.net/blog-useful-information/tutorial-ag-cloud-express-movies/
Last but not least, you may find the projects in AG Cloud Express a bit lacking. If you would like to import your csv files and play around with nodes and edges for a bit, try looking at the csv tutorial guides below. There are certain requirements to making a CSV file compatible for AG Cloud Express, so be sure to refer to the guides below.
https://bitnine.net/blog-useful-information/how-to-import-csv-in-ag-cloud-express/
bitnine.net/blog-useful-information/import-data-ag-cloud-express/

Actually when I am trying to open links above gave me 403 forbidden error!
Thanks

It's working fine for me, but if the current links above don't work, try copy-pasting the links below.
AG Cloud Express
https://agcloud.bitnine.net/
AG Viewer Tutorial Blog
https://bitnine.net/blog-useful-information/tutorial-ag-cloud-express-movies/
AGCE Video Tutorial
https://bitnine.net/blog-useful-information/tutorial-analyzing-movie-data-with-ag-cloud-express-opencypher/
How to import csv in ag cloud express
https://www.youtube.com/watch?v=8S1IJswl7Lg
Import Data ag cloud express
https://bitnine.net/blog-useful-information/import-data-ag-cloud-express/

Please assign this to me as well.

Hello everyone, I'd like to share how to run pgAdmin using docker for those who might have difficulty in connecting database.
First, you need to install docker. Here's a link for downloading docker: https://www.docker.com/. You can simply click the download button on the home page.
After downloading it, in order to make sure the download was successful, you can run the following command in your terminal: docker version
Now run the following command in your terminal to create a docker container with apache image:
docker run -d --name AGEDB -e POSTGRES_USER=age  -e POSTGRES_PASSWORD=age  -p 5432:5432 apache/age:latest
After creating a new container, now we need to access the pgAdmin4 to set up the postgreSQL connection and use if for the pgAdmin Docker setup.  Select Servers -> Register -> Server
The Name under the General tap is not essential which name you enter in the filed name as this is only for the organization within the tool. Click on the "Connection" tab, and in the field "username", "password", you will use the username and password that you specified in your docker compose.
Here's how I did
Name -> AGEDB
Host name/address -> localhost
Port -> 5432
Maintenance database -> age
username -> age
password -> age
Now the connection to the database has been established, We can now run AGE Viewer program using "npm run start" command and enter host, username, password that we specified in connection.
This link might be helpful and give you more idea how to set up the connection using Docker: https://towardsdatascience.com/how-to-run-postgresql-and-pgadmin-using-docker-3a6a8ae918b5

Excited to be part of this project.

To be assigned

Hello everyone, I'd like to share how to run pgAdmin using docker for those who might have difficulty in connecting database.
First, you need to install docker. Here's a link for downloading docker: https://www.docker.com/. You can simply click the download button on the home page.
After downloading it, in order to make sure the download was successful, you can run the following command in your terminal: docker version
Now run the following command in your terminal to create a docker container with apache image: docker run -d --name AGEDB -e POSTGRES_USER=age -e POSTGRES_PASSWORD=age -p 5432:5432 apache/age:latest
After creating a new container, now we need to access the pgAdmin4 to set up the postgreSQL connection and use if for the pgAdmin Docker setup. Select Servers -> Register -> Server
The Name under the General tap is not essential which name you enter in the filed name as this is only for the organization within the tool. Click on the "Connection" tab, and in the field "username", "password", you will use the username and password that you specified in your docker compose.
Here's how I did
Name -> AGEDB Host name/address -> localhost Port -> 5432 Maintenance database -> age username -> age password -> age
Now the connection to the database has been established, We can now run AGE Viewer program using "npm run start" command and enter host, username, password that we specified in connection.
This link might be helpful and give you more idea how to set up the connection using Docker: https://towardsdatascience.com/how-to-run-postgresql-and-pgadmin-using-docker-3a6a8ae918b5

Just a quick question, what is the graph path in AGViewer?

Hello everyone, I'd like to share how to run pgAdmin using docker for those who might have difficulty in connecting database.
First, you need to install docker. Here's a link for downloading docker: https://www.docker.com/. You can simply click the download button on the home page.
After downloading it, in order to make sure the download was successful, you can run the following command in your terminal: docker version
Now run the following command in your terminal to create a docker container with apache image: docker run -d --name AGEDB -e POSTGRES_USER=age -e POSTGRES_PASSWORD=age -p 5432:5432 apache/age:latest
After creating a new container, now we need to access the pgAdmin4 to set up the postgreSQL connection and use if for the pgAdmin Docker setup. Select Servers -> Register -> Server
The Name under the General tap is not essential which name you enter in the filed name as this is only for the organization within the tool. Click on the "Connection" tab, and in the field "username", "password", you will use the username and password that you specified in your docker compose.
Here's how I did
Name -> AGEDB Host name/address -> localhost Port -> 5432 Maintenance database -> age username -> age password -> age
Now the connection to the database has been established, We can now run AGE Viewer program using "npm run start" command and enter host, username, password that we specified in connection.
This link might be helpful and give you more idea how to set up the connection using Docker: https://towardsdatascience.com/how-to-run-postgresql-and-pgadmin-using-docker-3a6a8ae918b5

Just a quick question, what is the graph path in AGViewer?

After accessing db using Pgadmin, etc., run the query below to create a graph path
SELECT * FROM ag_catalog.create_graph('graph_name');

I believe the graph path is just the path name of graph, so it can be the name of any graph. After connecting to the database, the connection status will be displayed.
Here's my connection status:
You are connected as user age
to localhost:5432/age
Graph path has been set to Jin
(In this case, I specified Jin for graph path and it still worked)

Hello everyone, I'd like to share how to run pgAdmin using docker for those who might have difficulty in connecting database.
First, you need to install docker. Here's a link for downloading docker: https://www.docker.com/. You can simply click the download button on the home page.
After downloading it, in order to make sure the download was successful, you can run the following command in your terminal: docker version
Now run the following command in your terminal to create a docker container with apache image: docker run -d --name AGEDB -e POSTGRES_USER=age -e POSTGRES_PASSWORD=age -p 5432:5432 apache/age:latest
After creating a new container, now we need to access the pgAdmin4 to set up the postgreSQL connection and use if for the pgAdmin Docker setup. Select Servers -> Register -> Server
The Name under the General tap is not essential which name you enter in the filed name as this is only for the organization within the tool. Click on the "Connection" tab, and in the field "username", "password", you will use the username and password that you specified in your docker compose.
Here's how I did
Name -> AGEDB Host name/address -> localhost Port -> 5432 Maintenance database -> age username -> age password -> age
Now the connection to the database has been established, We can now run AGE Viewer program using "npm run start" command and enter host, username, password that we specified in connection.
This link might be helpful and give you more idea how to set up the connection using Docker: https://towardsdatascience.com/how-to-run-postgresql-and-pgadmin-using-docker-3a6a8ae918b5

Just a quick question, what is the graph path in AGViewer?

After accessing db using Pgadmin, etc., run the query below to create a graph path SELECT * FROM ag_catalog.create_graph('graph_name');
Please refer to the document for more information https://age.apache.org/age-manual/master/intro/graphs.html#create-a-graph

awesome!

I believe the graph path is just the path name of graph, so it can be the name of any graph. After connecting to the database, the connection status will be displayed.
Here's my connection status:
You are connected as user age to localhost:5432/age Graph path has been set to Jin
(In this case, I specified Jin for graph path and it still worked)

Got it, then next step is to run backend? As localhost:5432 is not available. Also I had trouble with running backend due to the additional logging output, and when I update it, there is the same issue for running frontend as well.

Hello! I have ran into another problem. When I shut down my laptop last night and started it today, even though I made connections on both docker and pgadmin, how come the connection failed after entering the connection informations we've made previously? Thank you in advance!

Looking forward to working with everyone!

Excited to be part of this project.

after following @MJinH instructions I was able to connect to the database and run the age-viewer application

This is the issue I've indicated above

This is the issue I've indicated above

Hi Henry,
Were your docker and database server running when you tried to connect? Please make sure the servers are running you are attempting.

This is the issue I've indicated above

Hi Henry,
Were your docker and database server running when you tried to connect? Please make sure the servers are running you are attempting.

Yes they're running, but how come it's not connected?

This is the issue I've indicated above

Hi Henry,
Were your docker and database server running when you tried to connect? Please make sure the servers are running you are attempting.

Yes they're running, but how come it's not connected?

Hello! I have ran into another problem. When I shut down my laptop last night and started it today, even though I made connections on both docker and pgadmin, how come the connection failed after entering the connection informations we've made previously? Thanks in advance!

I'd just like to make sure. were you able to connect to database server and run the application successfully before shutting down your laptop? and after turning on your laptop the next day, you're no longer able to connect to database server. am I assuming correct?

This is the issue I've indicated above

Hi Henry,
Were your docker and database server running when you tried to connect? Please make sure the servers are running you are attempting.

Yes they're running, but how come it's not connected?

Hello! I have ran into another problem. When I shut down my laptop last night and started it today, even though I made connections on both docker and pgadmin, how come the connection failed after entering the connection informations we've made previously? Thanks in advance!

I'd just like to make sure. were you able to connect to database server and run the application successfully before shutting down your laptop? and after turning on your laptop the next day, you're no longer able to connect to database server. am I assuming correct?

Yes, that's the issue

i think discussions would be much more better on the "age-viewer" discord channel.

Hello everyone,
Sorry for the sudden change, but would you be able to join our discord server? After some discussion, we determined that a GitHub issue wasn't the best place for discussions, and we needed a place for the team to hold conversations.
https://discord.gg/EvXYuAr9

@Henry417E1610 I had kinda same issue where everything was configured correct but host address.
I was using localhost as the host, changing to <IP_ADDRESS> worked for me.

Hello, I am delighted to be part of this project.


Allow passing of analysis store through external compile interfaces

Zinc bypasses the IC API and uses AggressiveCompile.compile1 directly so that it can pass in an AnalysisStore. This is needed for complete control of a static cache for analysis stores.

We're already doing this with MixedAnalyzingCompiler.staticCache. This can be closed.


Fixing issue with steamids being changed due to float conversion.

Addresses https://github.com/pnxenopoulos/awpy/issues/213.
I also added a test for exactly this and cleaned up the _parse_kills... functions.

The test failures are from changes to imageio and already addressed in https://github.com/pnxenopoulos/awpy/pull/228.
Specifically in https://github.com/pnxenopoulos/awpy/pull/228/commits/fb587e339b8b3bf94d4c5480bd73f7a6ac4b946f and https://github.com/pnxenopoulos/awpy/pull/228/commits/2250a5407d583e7c7c1cb3ff87e2ff075c51ec6d


Make subscription iterable

Motivation
The most common pattern for working with subscriptions is to:

allocate the subscription by evaluating an on operation.
loop infinitely and evaluate subscription.next()

This introduces a lot of noise to get at the meat of the operation which is to just do something for every event that gets received on a particular target. We encountered this recently when fixing a bug in the bigtest proxy server where we had to re-write a server event loop to something like:
yield spawn(function*(): Operation<void> {
  let subscription = yield on(server, 'request');

  while (true) {
    let [req, res]: [http.IncomingMessage, http.ServerResponse] = yield subscription.next();
    yield spawn(function*() {
      try {
        proxyServer.web(req, res)
        yield once(res, 'close');
      } finally {
        req.destroy();
      }
    });
  }
});

Approach
We can remove a lot of the noise of the subscription mechanics by making the subscription object itself iterable as a stream of operations that yield the next item. That way, we can re-write this as:
yield spawn(function*(): Operation<void> {
  for (let next of yield on(server, 'request')) {
    let [req, res]: [http.IncomingMessage, http.ServerResponse] = yield next;
    yield spawn(function*() {
      try {
        proxyServer.web(req, res)
        yield once(res, 'close');
      } finally {
        req.destroy();
      }
    });
  }
})

This is very similar to the async iterator syntax, and it might even be worth exploring later on if we can use the async generator syntax to be able to iterate over a subscription implicitly in parallel since any operation can be trivially converted into a promise by calling spawn on it.
yield spawn(async function*() {
  for await (let [req,res] of yield on(server, 'request')) {
    try {
      proxyServer.web(req, res)
      yield once(res, 'close');
    } finally {
      req.destroy();
    }
  }
})

The idea that each body of a for loop would be executed in parallel is kinda crazy to wrap your head around, but is pretty straightforward to implement, and would be absurdly powerful. For example, it would make implementing a race operation nearly trivial.
All food for thought. The scope of this PR is simple iterable subscriptions.

I think probably that for-await will be challenging, since we'll be unable to cancel the next operation. Maybe we can tie its lifetime to the subscription? So cancelling a subscription would automatically cancel all async iterations off of this?
I am also interested in working this out, due to working on subscriptions at the moment, where the API is an async iterator, and it's somewhat challenging to work out how this fits into the effection ecosystem.

This is superceded by #128, #129


Fixed ShapeDtypeStruct((), None) giving float64 under 32-bit mode

As title!

I wonder if dtype=None should raise an error here instead? It seems like an unintended use to me.

FWIW I figured this was intended. I think it's convenient to be able to specify "please use the default precision", without having to manually check jax.config.jax_enable_x64 manually oneself.
(E.g. we use it in Diffrax here, although if you wanted we could easily change that.)

Raising an error seems safer to me.

If we were to allow it, would it always be a float (of the default precision), and not an integer type?

Numpy chooses float:
>>> np.dtype(None)
dtype('float64')

but I still think for a lower-level API, requiring an explicit non-None dtype is better than assuming user intent.

How would we recommend one succinctly write what @patrick-kidger is looking for, namely "give me a dtype of the default precision"?

We don't have a well-defined API for that. As currently implemented, jnp.result_type(float) will return the default floating-point type though (i.e. respecting the values of the JAX_DEFAULT_DTYPE_BITS and JAX_ENABLE_X64 flags)

Would it make more sense for jnp.dtype to include canonicalization, rather than just being an alias for np.dtype?

Wondering the same, but not sure. Maybe a new function, with a new and descriptive name, would be clearer and avoid surprises. I could imagine a case for having it live in the top-level jax module—something like jax.canonical_dtype—so that it can also resolve (trivially) any opaque dtypes (not in numpy).
cc @mattjj, at least for the opaque dtypes bit

Closing due to lack of interest.

How would we recommend one succinctly write what @patrick-kidger is looking for, namely "give me a dtype of the default precision"?

I realized we do have a decent answer for this:
import jax
from jax import dtypes

with jax.experimental.enable_x64():
  print(dtypes.result_type(None))
  print(dtypes.result_type(float))
  print(dtypes.result_type(int))

float64
float64
int64

with jax.experimental.disable_x64():
  print(dtypes.result_type(None))
  print(dtypes.result_type(float))
  print(dtypes.result_type(int))

float32
float32
int32

I still think that for ShapeDtypeStruct, it should probably raise an error for dtype = None. I'm going to give that a try and see if it breaks anyone.


Check for CONTAINER_MODE environmental variable for rotation

Desired Outcome
If using environmental variables to configure secrets provider and you add secrets rotation,
you should be able to set the container mode with environmental variable.
Implemented Changes
Add a check for the CONTAINER_MODE environmental variable.
In main.go just added a check to read the environmental variable to keep the changes
to a minimum as these changes will be removed when we depreciate env variables.
Connected Issue/Story
Resolves #N/A
Definition of Done
At least 1 todo must be completed in the sections below for the PR to be
merged.
Changelog

[ ] The CHANGELOG has been updated, or
[x] This PR does not include user-facing changes and doesn't require a
CHANGELOG update

Test coverage

[ ] This PR includes new unit and integration tests to go with the code
changes, or
[x] The changes in this PR do not require tests

Documentation

[ ] Docs (e.g. READMEs) were updated in this PR
[ ] A follow-up issue to update official docs has been filed here: insert issue ID
[x] This PR does not require updating any documentation

Behavior

[ ] This PR changes product behavior and has been reviewed by a PO, or
[ ] These changes are part of a larger initiative that will be reviewed later, or
[x] No behavior was changed with this PR

Security

[ ] Security architect has reviewed the changes in this PR,
[ ] These changes are part of a larger initiative with a separate security review, or
[x] There are no security aspects to these changes

I'm not quite as familiar with Go testing, but is there an easy way to slip in a test for this change? Seems like a good candidate for a bug the automated tests could have caught.


Adding String Anagram Checker

Project title
String Anagram Checker
Project Description
A program to check if two strings are anagrams or not.
Stack:

[x] Html
[x] CSS
[x] JavaScript

/assign


Specify a query timeout for the client

Problem
When running in a serverless environment, any queries executed by the prisma client should take less time than the timeout imposed by the external environment, so that there can be proper error management instead of the serverless function just timing out.
Suggested solution
Allow specifying a general request timeout on prisma client.
Alternatives
Allow specifying a timeout per request.
Additional context

Note that PostgreSQL for example has statement_timeout: https://www.postgresql.org/docs/current/runtime-config-client.html#:~:text=statement_timeout (integer) This could be set on connection creation to configure each connection to have a set timeout.

This could perhaps be experimented on with a simple client extension.

This would really help me as I have some situations where I want to wait in perpetuity for findMany calls but timeout for count calls.

Hello, let me +1 this and explain another use case.
Recently our database server (PostgreSQL) suddenly stopped responding to any query.
This resulted in existing Prisma connections being hung up indefinitely and subsequent connection pool timeout errors.
Fortunately some of our application code used the $transaction API that had default timeout settings. Such code was able to timeout and create a new, working connections.
Global query timeout settings would be beneficial for quicker recovery from this kind of incident. In this case database-level setting like statement_timeout is not helpful since DB is in an abnormal state.

The same thing mentioned by uhyo happened in production for me. Some of the hung queries were around for  over 6 hours. Had to kill the queries manually when the Prisma client could not create new connections.
Am surprised that this is not a quick setting to apply.

We are seeing similar issues where queries get stuck long after the request that caused the query has timed out

I had an issue with query on postgres which was sometimes long to run, and I wanted just to abort after 10 seconds.
I achieved it this way:
 const result = await prisma.$transaction(async (tx) => {
      await tx.$executeRawUnsafe('set statement_timeout to 10000;');
      return await tx.$queryRawUnsafe(
        query,
      );
 });


Update tls-termination.md, added a small note to help other people setting up tls with multiple ambassador instances running in one cluster.

This should be documented somewhere, not sure if this is the right place, but a least this would have helped me.
Description
A few sentences describing the overall goals of the pull request's commits.
Related Issues
List related issues.
Testing
A few sentences describing what testing you've done, e.g., manual tests, automated tests, deployed in production, etc.
Tasks That Must Be Done

[ ] Did you update CHANGELOG.md?
[ ] Did you add or update tests?
[ ] Did you update documentation?
[ ] Were there any special dev tricks you had to use to work on this code efficiently?

[ ] Did you add them to DEVELOPING.md?

[ ] Is this a build change?

[ ] If so, did you test on both Mac and Linux?

Other

If this is a documentation change for a particular release, please open the pull request against the release branch.

I don't really care if you guys accept this pull request, but someone should add some documentation on this somewhere.

Thank you! Do you think https://www.getambassador.io/docs/latest/topics/running/running/#ambassador_id would make more sense?

Hey Richard, that probably makes more sense. Thank you :)

(Since this PR was into master, this won't appear in the live docs until later this week.)


Sync With Wiki bookmarklet not working

As of 5/12/2024, it seems that the Sync With Wiki function isn't working as it should. It's not opening the Infinite Craft Wiki page, just reads 'Syncing with Wiki' at top.

Thanks for the feedback! I'll take a look

It should be updated now, please refresh and update the bookmarklet (delete the bookmarklet, and drag to your bookmarklet bar again)


Add Linked List

And a whole suite of helper functions that modify the list.

Thank you for your contribution!  It's a good way to contribute to Hacktoberfest 😎


Allow adding custom classes on modal-dialog

This would allow custom styling and positioning of modals.
The custom classes could be enabled through the ModalConfig with classes: string property and by adding [ngClass]="dialogInstance.config.classes || ''" to the BootstrapModalContainer template.
This would make modal alignment as mentioned in #29 easy to do with a little css.

How do I set a custom class on the modal-dialog element?

It should look like this
modal.alert()
    .headerClass('modal-header')
    .title('Hello World')
    .body('A Customized Modal')
    .bodyClass('modal-body')
    .footerClass('modal-footer')
    .okBtnClass('btn')
    .open();

Play with the generator to see other options... http://shlomiassaf.github.io/angular2-modal#/customizeModals

Basically there is a 1 custom modal that I'v implemented that replace the old ones (okOnly, yesNo)
I've built the alert,prompt and confirm presets around it which provides a lot of flexibility.
If a more advanced scenario is needed a custom modal is needed...

I'm aware of the headerClass, bodyClass and footerClass, but that will not allow you to do any positioning. That why I wanted to see a way to add a class to the modal-dialog. It could be an optional `.modalClass('my-custom-modal')´ in the fluent api

The problem with modal-dialog is that it hold the "size" css class.
So, What would you think is the best approach here?
Template:
    `

`

So having a custom css class should override the size, which then creates a weird behaviour...

Doing something like this will not override the size class

Yep I agrre but that doesn't solve my issue.
config.size has a default value, usually "lg".
So a user will have to do
modal.alert()
    .size('')
    .modalDialogClass('something')
    .open()

To get the class to be what he wanted...
Maybe setting modalDialogClass will also override size?

You know what, overriding make's sense, if someone wants to be explicit then by all means, all the way.

There should be room for both - I my current setup I use both lg and custom class

If u'r setting a custom modal-dialog class you will need to set "modal-lg" as a custom class.
e.g: modal.alert().dialogClass('my-cutom modal-lg')
I think it looks better then modal.alert().dialogClass('my-cutom').size('')

Btw. don't know if modalDialogClass would be the best fit for a name. What about modalClass to keep it aligned with the headerClass

The naming convention is xClass where x is the original class name without the modal (modal-x).
e.g: modal-header -> headerClass
So it will be dialogClass

Makes sense

BTW, you know that all xClass methods override the class, so setting dialogClass will remove the original class (modal-dialog), if it's addition you're after you will have to do modal-dialog my-css
There's no other option...

I'm not seeing that behaviour using beta12.
When I'm using [ngClass]="dialogInstance.config.modalDialogClass || ''" I get the value from the config added to the class list. My modal-dialog ends of with the following class list: modal-dialog lg custom

I talked about general behaviour of xClass in the preset's.
As for the expression dialogInstance.config.modalDialogClass it invalid because dialogInstance.config is not the preset API, it's an instance of ModalConfig which is build from the preset, but it's not the preset so dialogInstance.config.modalDialogClass will always be null.
The actual preset is injected into the Modal component itself.
The preset is wrapper that combine's the two, but when doing a manual implementation they are separate.

Okay, I misunderstood. Btw. the dialogInstance.config.modalDialogClass is just something I have in a local fork - switching to your new fluent api version when the dialogClass is implemented.

Cool :+1:
It will probably end up (dialogClass) on the config object since it's a level above the modal component...

See latest commits, modal-dialog is enabled via dialogClass
You can verify it in the code generator.
If size is set it will not remove it, I left it as you requested originally
npm version 0.1.1


INT B-21376 I-13558

Downstream of https://github.com/transcom/mymove/pull/14253 - don't merge until that is merged into INT
Agility ticket
Issue ticket
Summary
They wanted to see the UB allowance up top where the weight allowance is shown, so Imma show it.
How to test

Set up your env so you can create UB shipments
After adding your orders information, go back to your home page and check out your headers
Should see a UB allowance up there lookin' all pretty

Screenshots

Recommend marking #14253 as an upstream, this PR doesn't work for civilians
Screen.Recording.2024-11-22.at.9.33.19.AM.mov

Updated description of PR - I'll hold off on merging until that's in.

Just merged in the upstream

@traskowskycaci could you push the merge? Will retest it

@danieljordan-caci Will retest once resynced

Well.. it works for civilian now, but fails for

Aviation Cadet
Service Academy Cadet
Midshipman

What are we thinking for how to proceed?
Screen.Recording.2024-11-22.at.10.07.40.AM.mov

Well... The only reason why it'd be failing would be the payload is not sending the ub_allowance

Well.. it works for civilian now, but fails for

Aviation Cadet
Service Academy Cadet
Midshipman

What are we thinking for how to proceed?
Screen.Recording.2024-11-22.at.10.07.40.AM.mov

Not a fail - just 0 for the UB allowance for those grades which is expected - https://ustcdp3.slack.com/archives/C06D8HB31HP/p1730480371710309

Well.. it works for civilian now, but fails for

Aviation Cadet
Service Academy Cadet
Midshipman

What are we thinking for how to proceed?
Screen.Recording.2024-11-22.at.10.07.40.AM.mov

Not a fail - just 0 for the UB allowance for those grades which is expected - https://ustcdp3.slack.com/archives/C06D8HB31HP/p1730480371710309

Sorry wrong link - read the comments here
https://ustcdp3.slack.com/archives/C06D8HB31HP/p1730754253194339


setState() or markNeedsBuild() called during build - Not clear how to resolve issue

I think this problem likely resides behind the keyboard as I am new to Flutter.
That said, I am trying to use a ternary statement in within a StreamBuilder, builder function to redirect based upon some Bloc stream data.
Here is the Widget in question:
import 'package:flutter/material.dart';
import '../blocs/auth_bloc.dart';

class LoginPage extends StatelessWidget {
  final authBloc = AuthBloc();
  final Map<String, bool> initialData = {'loginSuccess': false, 'isLoading': false};

  @override
  Widget build(BuildContext context) {
    return StreamBuilder(
        stream: authBloc.redirect,
        initialData: initialData,
        builder: (context, snapshot) {
          return Scaffold(body: _render(context, snapshot));
        });
  }

  _render(BuildContext context, AsyncSnapshot snapshot) {
    return !snapshot.data['loginSuccess'] && snapshot.data['isLoading']
        ? _circularSpinner()
        : snapshot.data['loginSuccess'] && !snapshot.data['isLoading']
            ? _redirect(context)
            : _buildPage();
  }

  _redirect(BuildContext context) {
    return Navigator.of(context).pushReplacementNamed('/dashboard');
  }

  Widget _buildPage() {
    return Container(
      margin: EdgeInsets.all(20.0),
      child: Center(
        child: SingleChildScrollView(
          child: Column(
            children: <Widget>[
              _emailField(authBloc),
              _padding(),
              _passwordField(authBloc),
              _padding(),
              _submitButton(authBloc)
            ],
          ),
        ),
      ),
    );
  }

  Widget _circularSpinner() {
    return Center(
      child: CircularProgressIndicator(),
    );
  }

  Widget _emailField(AuthBloc authBloc) {
    return StreamBuilder(
      stream: authBloc.email,
      builder: (BuildContext context, snapshot) {
        return TextField(
          onChanged: authBloc.emailChanged,
          keyboardType: TextInputType.emailAddress,
          decoration: InputDecoration(
            hintText<EMAIL_ADDRESS>            labelText: 'Email Address',
            errorText: snapshot.error,
            border: OutlineInputBorder(),
          ),
        );
      },
    );
  }

  Widget _passwordField(AuthBloc authBloc) {
    return StreamBuilder(
      stream: authBloc.password,
      builder: (BuildContext context, snapshot) {
        return TextField(
          onChanged: authBloc.passwordChanged,
          obscureText: true,
          keyboardType: TextInputType.emailAddress,
          decoration: InputDecoration(
            hintText: '8 characters or more with at least 1 number',
            labelText: 'Password',
            errorText: snapshot.error,
            border: OutlineInputBorder(),
          ),
        );
      },
    );
  }

  Widget _padding() {
    return Padding(
      padding: EdgeInsets.only(top: 20.0),
    );
  }

  Widget _submitButton(AuthBloc authBloc) {
    return StreamBuilder(
        stream: authBloc.submitValid,
        builder: (context, snapshot) {
          return RaisedButton(
            child: Text('Login'),
            color: Colors.blue,
            onPressed: snapshot.hasError ? null : authBloc.submitForm,
          );
        });
  }
}

This results in the following log:
I/flutter ( 4657): ══╡ EXCEPTION CAUGHT BY WIDGETS LIBRARY ╞═══════════════════════════════════════════════════════════
I/flutter ( 4657): The following assertion was thrown building StreamBuilder<Map<dynamic, dynamic>>(dirty, state:
I/flutter ( 4657): _StreamBuilderBaseState<Map<dynamic, dynamic>, AsyncSnapshot<Map<dynamic, dynamic>>>#a5165):
I/flutter ( 4657): setState() or markNeedsBuild() called during build.
I/flutter ( 4657): This Overlay widget cannot be marked as needing to build because the framework is already in the
I/flutter ( 4657): process of building widgets. A widget can be marked as needing to be built during the build phase
I/flutter ( 4657): only if one of its ancestors is currently building. This exception is allowed because the framework

It is not clear from the log what I need to do to resolve. Or can we not use ternary statements to redirect in this context?

I seem to have resolved my issue here.
It seems that you just can't Navigator away within a StreamBuilder.
Here is the changed code:
 @override
  Widget build(BuildContext context) {
    // Manually listening for redirect conidtions here
    // once a response is received from the server
    authBloc.loginSuccess.listen((data) {
      if (data) {
        Navigator.pushReplacementNamed(context, '/dashboard');
      }
    });

    return StreamBuilder(
        stream: authBloc.isLoading,
        initialData: false,
        builder: (context, snapshot) {
          print(snapshot.data);
          return Scaffold(
            body: snapshot.data ? _circularSpinner() : _buildPage(),
          );
        });
  }

I will let someone else decide whether to close or not. The log wasn't overly helpful in resolving the issue. That said I am only just picking up flutter and used to the react way of thinking and logging.

I faced this issue once, it's probably related to the onPressed: snapshot.hasError ? null : authBloc.submitForm, line, try using onPressed: () => snapshot.hasError ? null : authBloc.submitForm,

I faced this issue once, it's probably related to the onPressed: snapshot.hasError ? null : authBloc.submitForm, line.
Try using onPressed: () => snapshot.hasError ? null : authBloc.submitForm, instead.

Thanks. I will have a look at that later and let you know if it worked. I am unsure as there are no errors present.

I encounter the same problem. I agree with @jhc1982. It seems that we can't use navigation when the widget is building. I try showDialogue, I can use it neither.

We use the stream builder. Thus we can't use the didUpdateWidget to judget whether we need navigation.

I think the addPostFrameCallback is what you are looking for. Please refer to this article on how to use the postFrameCallback for displaying dialog boxes and navigating to screens during or before widget build.

I think it's safe to close the issue as it got resolved. If you disagree, please comment, I will re-open it right away.

Eu esta com o mesmo problema.
The following assertion was thrown building FutureBuilder<List<dynamic>>(dirty, state: _FutureBuilderState<List<dynamic>>#1f278): setState() or markNeedsBuild() called during build.
Para resolver o problema (removi) o final das variáveis.

Exemplo:
Antes:
class ListLivroScreen extends StatefulWidget {
String tipo;
List livros;
Depois:
class ListLivroScreen extends StatefulWidget {
final String tipo;
final List livros;

I sovle the problem by add async and await when use  Navigator.pushNamed on tap or press
onPressed:()=>navToAttachList(context)

  navToAttachList(context) async{
    await Navigator.pushNamed(
      context,
      AttachListWidget.routeName,
      arguments: {
        'id':this.id
      }
    );
  }

I sovle the problem by add async and await when use  Navigator.pushNamed on tap or press
onPressed:()=>navToAttachList(context)

  navToAttachList(context) async{
    await Navigator.pushNamed(
      context,
      AttachListWidget.routeName,
      arguments: {
        'id':this.id
      }
    );
  }

thank you work for me


need help

I am having an issue with rest-assured output. i am able to get result with Postman, also with java 11 http API i am getting a full response but not with RestAssured.
attaching screenshots

so? why no answer?

We're all volunteers here and no one gets paid to work on REST Assured so
there's no guarantee that you'll get an answer. I hope you understand.
I'm not even sure I understand your question, what is it that you're asking?
If I try to interpret your images, one thing you could try to do is to
escape "$" char in the queryParam and see that works. For example
"queryParam("$filter",
...)". If this works for you please let me know, since if so rest assured
should probably do the escaping for you.
On Wed, Oct 2, 2019 at 8:17 PM Mr Y<EMAIL_ADDRESS>wrote:

so? why no answer?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/rest-assured/rest-assured/issues/1217?email_source=notifications&email_token=AABNVFJLLEBG7CPQ2CU7NATQMTQVBA5CNFSM4I2TSAR2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAFWF7Q#issuecomment-537617150,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABNVFITOPKQILOJJCSVJADQMTQVBANCNFSM4I2TSARQ
.

@johanhaleby
Thank you for your time and help,
nope it didn't work for me. i got Bad Request 400


Some methods added

Added Method for: GET /1/organizations/[idOrg or name]/members and GET /1/lists/[idList]/cards
Created type PluginData

oops, this was automatically closed when I deleted old "dev" branch.

I looked at the changes - there are many changed lines, in particular in Trello interface, which seem to be from re-formatted code. this makes review unnecessarily complex.
let's minimize changes to what is needed to add a feature,
and apply formatting changes in separate commits.


fix typo

What this PR does / why we need it:
docs: fix typo
The wrong video device number can be confusing.
Special notes for your reviewer:
If applicable:

[ ] this PR contains documentation
[ ] this PR contains unit tests
[ ] added code adheres to standard Rust formatting (cargo fmt)
[ ] code builds properly (cargo build)
[ ] code is free of common mistakes (cargo clippy)
[ ] all Akri tests succeed (cargo test)
[ ] inline documentation builds (cargo doc)
[ ] version has been updated appropriately (./version.sh)

Thank you for catching this and making a fix!

No worries, my pleasure.


Cereal serialization - Any

SGVector.h is not updated
load and save methods in SGVector class will confuse examples in examples/undocumented because they're taking similar params as old save-load methods in SGVector class. Most examples will fail with current methods naming. BUT so far I have found that the inheritance serialization only works with the exact "load-save" pairs so I'd keep it like this for now.
This PR can only be merged once #3226 is finished.

Fine to merge from my side modulo cosmetic comments

Seems like this wasnt touched in 5 days ....

Merged via #3375


Make use of code-run-websites

For many languages websites exist, where people can run code snippets.
We currently don't really do that in the AAA, but I think it's a cool thing to add for languages supporting it.
People wouldn't have to download and install everything needed just to run some code and people could also run code on mobile.
This topic came to my attention again, because of this https://github.com/algorithm-archivists/algorithm-archive/pull/164 which included a convenient way to run the code.
So I open this issue for discussion about this topic. What do you guys think?

I can see two different methods of doing this. Either include just a link to the website or have it somehow integrate in the AAA.
I think the first one will be fine for now, while the second one is something to consider for the future, because I imagine to to be far more complex.
@jiegillet I would say just creating it manually and checking if the output is right is enough. We need to pay attention to this then in future PRs of course, but I think this will be fine. I don't know what you mean by tools... A GitBook plugin doing that would be neat (and cover the second method I named), but I highly doubt it exists.

Yeah I was thinking GitBook plugin... We have all the informations, where the file is, what the language is. Some online interpreters can handle hundreds of languages. But yes, chances are low it exists.

I must say I'm not a fan of integrating these tools. I'd support the decision to have an introduction chapter with a bunch of links to such online interpreters/compilers, but in the end, we're writing a book. I don't think it needs live code execution.
Secondly, I don't like the idea of creating a bunch of dependencies on third-party services. They can go down, change their APIs and it will be work to maintain working connections to them.

@Gustorn recently brought up that we could do something like this: https://doc.rust-lang.org/book/second-edition/ch01-02-hello-world.html, where each codeblock can be run in the background. I don't know how well this will play with the include-codeblocks and theme-api plugins.
@julianschacher mentioned we could use this too: https://docs.microsoft.com/en-us/dotnet/csharp/quick-starts/hello-world?tutorial-step=2, which brings up a separate editor so people can play with the code.
I also don't know what languages are supported for a similar feature. Like @Butt4cak3 I don't know if these services will be stable for a long time or not... But I am not sure how long our current tools will be stable for anyway.

Cannot we just test in local what the results are, and cheat a little bit : when the user will press on buttons like 'play' or something like that, the results are stored somewhere and are just display!
It's not the best solution, but It will do the job!

@xam4lor The cool thing with those code running websites is, that people can modify the code and see what happens. With our cheat this wouldn't be possible. We also decided not to provide output files (and maybe use random input) for our implementations, right here: https://github.com/algorithm-archivists/algorithm-archive/pull/55 (scroll down a bit)


  This is the expected behavior of the build system.

OPS Build status updates of commit c9b0cc7:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

xml/FrameworksIndex/azure-dotnet.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Auth/BatchCredentials.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Auth/BatchSharedKeyCredentials.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Auth/BatchTokenCredentials.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/AccessScope.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/AddTaskStatus.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/AllocationState.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/AutoUserScope.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/BatchErrorCodeStrings.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/BatchException.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/CachingType.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/CertStoreLocation.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/CertificateFormat.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/CertificateState.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/CertificateVisibility.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/ComputeNodeDeallocationOption.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/ComputeNodeFillType.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/ComputeNodeRebootOption.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/ComputeNodeReimageOption.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/ComputeNodeState.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/DependencyAction.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/DisableComputeNodeSchedulingOption.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/DisableJobOption.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/DynamicVNetAssignmentScope.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/ElevationLevel.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/ErrorCategory.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/ExponentialRetry.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/IRetryPolicy.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/InboundEndpointProtocol.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/JobAction.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/JobPreparationTaskState.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/JobReleaseTaskState.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/JobScheduleState.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/JobSchedulingErrorCodes.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/JobState.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/LinearRetry.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/LoginMode.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/NetworkSecurityGroupRuleAccess.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/NoRetry.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/OSType.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/OnAllTasksComplete.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/OnTaskFailure.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/OperationContext.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/OutputFileUploadCondition.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/PoolLifetimeOption.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/PoolResizeErrorCodes.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/PoolState.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/RequestInformation.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/RequestResult.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/RetryDecision.xml
:white_check_mark:Succeeded

This comment lists only the first 50 files in the pull request.
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

  This is the expected behavior of the build system.

OPS Build status updates of commit 3c3d274:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

xml/FrameworksIndex/azure-dotnet.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Auth/BatchCredentials.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Auth/BatchSharedKeyCredentials.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Auth/BatchTokenCredentials.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/AccessScope.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/AddTaskStatus.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/AllocationState.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/AutoUserScope.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/BatchErrorCodeStrings.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/BatchException.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/CachingType.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/CertStoreLocation.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/CertificateFormat.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/CertificateState.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/CertificateVisibility.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/ComputeNodeDeallocationOption.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/ComputeNodeFillType.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/ComputeNodeRebootOption.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/ComputeNodeReimageOption.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/ComputeNodeState.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/DependencyAction.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/DisableComputeNodeSchedulingOption.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/DisableJobOption.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/DynamicVNetAssignmentScope.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/ElevationLevel.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/ErrorCategory.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/ExponentialRetry.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/IRetryPolicy.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/InboundEndpointProtocol.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/JobAction.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/JobPreparationTaskState.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/JobReleaseTaskState.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/JobScheduleState.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/JobSchedulingErrorCodes.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/JobState.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/LinearRetry.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/LoginMode.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/NetworkSecurityGroupRuleAccess.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/NoRetry.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/OSType.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/OnAllTasksComplete.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/OnTaskFailure.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/OperationContext.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/OutputFileUploadCondition.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/PoolLifetimeOption.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/PoolResizeErrorCodes.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/PoolState.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/RequestInformation.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/RequestResult.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/RetryDecision.xml
:white_check_mark:Succeeded

This comment lists only the first 50 files in the pull request.
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

  This is the expected behavior of the build system.

  This is the expected behavior of the build system.

OPS Build status updates of commit f3e5a04:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

api/overview/azure/iot.md
:white_check_mark:Succeeded
View

xml/FrameworksIndex/azure-dotnet.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Auth/BatchCredentials.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Auth/BatchSharedKeyCredentials.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Auth/BatchTokenCredentials.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/AccessScope.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/AddTaskStatus.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/AllocationState.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/AutoUserScope.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/BatchErrorCodeStrings.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/BatchException.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/CachingType.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/CertStoreLocation.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/CertificateFormat.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/CertificateState.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/CertificateVisibility.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/ComputeNodeDeallocationOption.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/ComputeNodeFillType.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/ComputeNodeRebootOption.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/ComputeNodeReimageOption.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/ComputeNodeState.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/DependencyAction.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/DisableComputeNodeSchedulingOption.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/DisableJobOption.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/DynamicVNetAssignmentScope.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/ElevationLevel.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/ErrorCategory.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/ExponentialRetry.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/IRetryPolicy.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/InboundEndpointProtocol.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/JobAction.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/JobPreparationTaskState.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/JobReleaseTaskState.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/JobScheduleState.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/JobSchedulingErrorCodes.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/JobState.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/LinearRetry.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/LoginMode.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/NetworkSecurityGroupRuleAccess.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/NoRetry.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/OSType.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/OnAllTasksComplete.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/OnTaskFailure.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/OperationContext.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/OutputFileUploadCondition.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/PoolLifetimeOption.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/PoolResizeErrorCodes.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/PoolState.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/RequestInformation.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/RequestResult.xml
:white_check_mark:Succeeded

This comment lists only the first 50 files in the pull request.
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

  This is the expected behavior of the build system.

OPS Build status updates of commit 0a40d3a:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

api/overview/azure/iot.md
:white_check_mark:Succeeded
View

docfx.json
:white_check_mark:Succeeded

xml/FrameworksIndex/azure-dotnet.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Auth/BatchCredentials.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Auth/BatchSharedKeyCredentials.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Auth/BatchTokenCredentials.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/AccessScope.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/AddTaskStatus.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/AllocationState.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/AutoUserScope.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/BatchErrorCodeStrings.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/BatchException.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/CachingType.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/CertStoreLocation.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/CertificateFormat.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/CertificateState.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/CertificateVisibility.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/ComputeNodeDeallocationOption.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/ComputeNodeFillType.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/ComputeNodeRebootOption.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/ComputeNodeReimageOption.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/ComputeNodeState.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/DependencyAction.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/DisableComputeNodeSchedulingOption.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/DisableJobOption.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/DynamicVNetAssignmentScope.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/ElevationLevel.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/ErrorCategory.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/ExponentialRetry.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/IRetryPolicy.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/InboundEndpointProtocol.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/JobAction.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/JobPreparationTaskState.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/JobReleaseTaskState.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/JobScheduleState.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/JobSchedulingErrorCodes.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/JobState.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/LinearRetry.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/LoginMode.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/NetworkSecurityGroupRuleAccess.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/NoRetry.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/OSType.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/OnAllTasksComplete.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/OnTaskFailure.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/OperationContext.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/OutputFileUploadCondition.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/PoolLifetimeOption.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/PoolResizeErrorCodes.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/PoolState.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Batch.Common/RequestInformation.xml
:white_check_mark:Succeeded

This comment lists only the first 50 files in the pull request.
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Fix description of enableLanguageServer option

Hi, I am finding this extension to be a great help. Thank you for your work!
I found a mistake in the README. Based on the implementation, it seems that the default value for the phpstan.enableLanguageServer option is false.

https://github.com/SanderRonde/phpstan-vscode/blob/v3.1.14/package.json#L127-L131
https://github.com/SanderRonde/phpstan-vscode/blob/v3.1.14/shared/commands/defs.ts#L166-L173

If there are no problems, please consider merging this change.

Ah oops, missed this one. Thanks!


Fetch line numbers for Python frames lazily

Up until now we've been greedily capturing the line number of each
Python frame as we first encounter it, but this is unnecessarily
inefficient. Since we've already been assuming that it's safe to call
PyFrame_GetLineNumber without the GIL held (and we'd already need to
change this code should that assumption become false in a future CPython
version), we can delay calculating the Python line number until we're
about to emit the frame. Since many frames are entered without ever
being emitted (because no allocation is performed under them), this
drastically reduces the number of calls to PyFrame_GetLineNumber,
which is a deceptively slow function.

Flipping this to Draft - this is subtly broken in a way that our test suite doesn't catch. I'll need to circle back to this - and add a new test...

OK, I think this is now actually correct... And the new test case covers the problem that the original version of this had, so that we know we won't regress on it.

Experiments executed for python -m memray run  -o /dev/null -m test test_list test_list test_list test_list test_list test_list test_list test_list test_list test_list for a total duration of 1.2595737380001992 seconds in baseline.
With this PR
      Calls to PyFrame_GetLineNumber: 25550
     0.03%     0.03%  python  python3.10  [.] PyFrame_GetLineNumber                                                                                ▒

Baseline
      Calls to PyFrame_GetLineNumber: 270090
     0.39%     0.39%  python  python3.10                               [.] PyFrame_GetLineNumber                                                   ◆

This means that in general the most we can save (that we are indeed saving it) is 0.39% of the total runtime (this is assuming no PYTHONMALLOC=malloc where most savings will be there since calls to PyFrame_GetLineNumber in pushPythonFrame are a bigger percentage of the runtime because our hooks are called less).
For the case where PYTHONMALLOC=malloc for a total duration of 3.0231499819997225 seconds in baseline:
      Calls to PyFrame_GetLineNumber: 21057170
+    5.26%     5.26%  python  python3.10                               [.] PyFrame_GetLineNumber

Baseline
      Calls to PyFrame_GetLineNumber: 21125440
+    7.23%     7.23%  python  python3.10                               [.] PyFrame_GetLineNumber

This means that in the latter we are saving ~2% maximum. This is consistent with the timing results of 2.8712007330000233 (PR) against 2.935535135000009 (baseline).
PR
  Test duration: 2.8712007330000233
  Time (mean ± σ):      3.058 s ±  0.051 s    [User: 3.008 s, System: 0.056 s]
  Range (min … max):    2.983 s …  3.167 s    10 runs

Baseline
    Test duration: 2.935535135000009
  Time (mean ± σ):      3.120 s ±  0.046 s    [User: 3.070 s, System: 0.056 s]
  Range (min … max):    3.064 s …  3.210 s    10 runs

That is around 3.5% of the difference.


DATABASE_URL env variable as source of database connection info

Is your feature request related to a problem? Please describe.
The DATABASE_URL environment variable is standard in many environments for specifying how to connect to the database. It would be nice if sqls could use, reducing the need for manual configuration.
Describe the solution you'd like
Check for the environment variable, if it's there use it to connect to the database.
Describe alternatives you've considered
Manual configuration.
Additional context
I don't know how standardized the format is. Possibly you'd need to do more work to support multiple variations.

How would you setup multiple connection through environment vars?

How would you setup multiple connection through environment vars?

direnv: https://direnv.net/

I guess cizordj is talking about how to specify multiple connection string in one environment variable.

I guess cizordj is talking about how to specify multiple connection string in one environment variable.

This


Use plotly in the backend to generate plots for the frontend

Quite a large PR sorry for that.
We create plots in the backend and then we forward them to the frontend which only have to render them. I think prettier wasn't run on a previous commit.
@nitish1295 We can configure the zoom controls here and the background color here

LGTM.
I will try to look more into this later but when we set a refresh interval, at each data/graph refresh the page is pulled back to the the initial graph. This might be distracting in a situation when a user might be looking at a different part of the page and then suddenly the page focuses on the first graph.


[tensorflow/compiler/mlir/python/mlir.cc] Use correct size type for node_names.size() iterator

https://github.com/tensorflow/tensorflow/pull/51739#issuecomment-940389562 told me to split the larger PR into one PR per file; thus this (thanks bash, git and gh!)

@SamuelMarks Any update on this PR? Please. Thanks!

@gbaned I have made the size types the same as the size type returned by the .size() function. If @joker-eph wants a different return type, then he should create a new vector type that has its size type as what he wants it to be. Otherwise type inconsistencies occur, which is the whole problem this PR purports to solve.

Please reopen if you'd like to address comments, otherwise I don't think there is any point in keeping this open.


Is there a way to avoid boxing while using custom serializer?

I'm using a collection of messages which are all unmanaged structs. I was wondering if I could use a custom serializer which in part just use some method like MemoryMarshal.Write() to directly translate a struct into Span of bytes.
The problem is that ISerializer interface produces and consumes constructs as objects which introduces boxing and therefore unnecessary performance hit. I'm aware that there are also ISerializer<T> and IDeserializer<T>  interfaces, but I could not get my head around how to wire those inside a custom serializer given that none of the current exposed API does not seem to accept any materialized generic interfaces.
Any suggestion on how to avoid boxing, and better yet, avoid interface devirtualization, is appreciated.

Thanks!
I though of the solution you put forward. However, since all the API within middleware to pass on the marshaled values to the handlers also use object, e.g.
 await next(context.SetMessage(context.Message.Key, messageValue)).ConfigureAwait(false);

I ended up with forsaking all middlewares and changing my handlers to typed handlers of byte[] and deserializing messages there.


url path changes

Here i have simply changes url paths and also this is for our test pull request.

Seems you are not using cargo fmt yet.

Also you have forked the repo. We prefer you work with this repo only.
Problem with fork is I can not update this PR, I will have to ask you to do updates. If you checkout this repo and do pushes here, then anyone in FifthTry can update your PR.
Sometimes comments make sense, and sometimes its faster to just do the change, so we prefer to avoid forks.

Ok will do it
On Fri, Oct 28, 2022, 2:55 PM Amit Upadhyay @.***>
wrote:

Also you have forked the repo. We prefer you work with this repo only.
Problem with fork is I can not update this PR, I will have to ask you to
do updates. If you checkout this repo and do pushes here, then anyone in
FifthTry can update your PR.
Sometimes comments make sense, and sometimes its faster to just do the
change, so we prefer to avoid forks.
—
Reply to this email directly, view it on GitHub
https://github.com/ftd-lang/fpm-auth/pull/2#issuecomment-1294791021, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AC4S2RCVSBFKNBPESLY7HJ3WFOPI3ANCNFSM6AAAAAARQZ4Y3Y
.
You are receiving this because you authored the thread.Message ID:
@.***>

I will now use fpm for further work
On Fri, Oct 28, 2022, 3:57 PM Wasif Shah @.***> wrote:

Ok will do it
On Fri, Oct 28, 2022, 2:55 PM Amit Upadhyay @.***>
wrote:

Also you have forked the repo. We prefer you work with this repo only.
Problem with fork is I can not update this PR, I will have to ask you to
do updates. If you checkout this repo and do pushes here, then anyone in
FifthTry can update your PR.
Sometimes comments make sense, and sometimes its faster to just do the
change, so we prefer to avoid forks.
—
Reply to this email directly, view it on GitHub
https://github.com/ftd-lang/fpm-auth/pull/2#issuecomment-1294791021,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AC4S2RCVSBFKNBPESLY7HJ3WFOPI3ANCNFSM6AAAAAARQZ4Y3Y
.
You are receiving this because you authored the thread.Message ID:
@.***>

yes not yet.
On Fri, Oct 28, 2022 at 2:51 PM Amit Upadhyay @.***>
wrote:

Seems you are not using cargo fmt yet.
—
Reply to this email directly, view it on GitHub
https://github.com/ftd-lang/fpm-auth/pull/2#issuecomment-1294785913, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AC4S2RGECKNOCCXYJCO5XB3WFOOY7ANCNFSM6AAAAAARQZ4Y3Y
.
You are receiving this because you authored the thread.Message ID:
@.***>


App crashes when viewing organization's calendar that has repeating events

Situation:
Basically when you add a google calendar that had repeating events
add yourself to the club
look at the events tab
app turns all white and becomes non-responsive

To reproduce:
add webdev club as one of your clubs and
look at the events tab


Does this project have Pytorch version

this evopose model is very useful~!thanks

It does not, sorry!


Update readme.md

Dead Link
By submitting this pull request, I promise I have read the contribution guidelines twice and ensured my submission follows it. I realize not doing so wastes the maintainers' time that they could have spent making the world better. 🖖
⬆⬆⬆⬆⬆⬆⬆⬆⬆⬆

Please use a descriptive pull request title.


LFS-734: Add time question support for minute and second format

Reuses dateFormat question parameter
If mm:ss is specified, use a regexp backed text field rather than a time input

Testing: Create a question of type time with a dateFormat of either hh:mm or mm:ss. If hours and minutes, then the browsers date picker should be used. If minutes and seconds, a text field should be created which limits input to the format ##:##, where both numbers are in the range 00 to 59. Both formats should support minimum and maximum values, specified in the format ##:##

fields are marked as INVALID/INCOMPLETE

By the way, having two components can easily be done by making the condition in registerAnswerComponent more complex:
AnswerComponentManager.registerAnswerComponent((questionDefinition) => {
  if (questionDefinition.dataType === "time" && questionDefinition.dateFormat === 'mm:ss') {
    return [StyledTimeQuestion, 60];
  }
});


adding ability to ignore ssl validation

Thank you for contributing to the go-pivnet API library!

Have you made this pull request to the develop branch? yes
Have you run the tests locally? yes

@calebwashburn Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.

@calebwashburn Thank you for signing the Contributor License Agreement!

@caleb Washburn thanks for this. I'm happy to merge it in. Just out of curiosity what custom endpoint are you targeting that doesn't have valid SSL configured?

This is due to using pivnet behind corporate proxy server that is injecting a "decrypt" cert.  also testing with the pivnet councourse resource as well.

Cool thanks, I figured it was something like that.