Fix: Fixes part of text input output component test where component popover elements are block others

Description:
This pull request refactors the selection and interaction of elements in the textInputOutput.spec.ts test file to improve code readability and ensure proper functionality.
Changes:

Consolidated the selection of elements using page.locator for better readability and maintainability.
Elements are now stored in variables (component1, element1, component2, element2) for easier reference.
Ensured that component popups are not blocking the elements by adding component1.blur() and component2.blur() before interactions.
Refactored the drag-and-drop action for better clarity. Used element1.dragTo(element2) to move the first element to the second element's location dynamically.
Left page.mouse.up() to ensure the mouse button is released after the drag-and-drop action.
Removed redundant hover actions and streamlined the interaction process.

hi @596050,
thank you for your cooperation.
LGTM.

hi @596050, thank you for your cooperation.
LGTM.

Hi, sure, we could offset the elements too? Should I create another PR to suggest that or add to this? I'm thinking:
export const offsetElements = async ({
    sourceElement,
    targetElement,
    page,
}) => {

  // Get bounding boxes of the components
  const box1 = await sourceElement.boundingBox();
  const box2 = await targetElement.boundingBox();

  await page.mouse.move((box2?.x  || 0) + 10, (box2?.y || 0))
  await page.mouse.down();

  // Move to the right of the second component
  await page.mouse.move((box2?.x  || 0) + (box2?.width || 0)/2 + (box1?.width || 0), (box2?.y || 0));
  await page.mouse.up();
}

which becomes:
  const component1 = await page.locator(
    '//*[@id="react-flow-id"]/div/div[1]/div/div/div[2]/div[1]',
  );

  const element1 = await page.locator(
    '//*[@id="react-flow-id"]/div/div[1]/div/div/div[2]/div[1]/div/div[2]/div[5]/button/div[1]',
  );

  const component2 = await page.locator(
    '//*[@id="react-flow-id"]/div/div[1]/div/div/div[2]/div[2]',
  );

  const element2 = await page.locator(
    '//*[@id="react-flow-id"]/div/div[1]/div/div/div[2]/div[2]/div/div[2]/div[3]/div/button/div[1]',
  );

  await offsetElements({
    sourceElement: component1,
    targetElement: component2,
    page,
  });

  // ensure elements popups are not blocking
  component1.blur();
  component2.blur();

  // Click and hold on the first element and move to the second element
  await element1?.dragTo(element2);

  // ensure the mouse button is up
  await page.mouse.up();

Which should do something like this:

@596050
this seems an error of replacing .env file on Github.
I'll check and let you

@596050
It seems like the error is due to the OPENAI_API_KEY value not being found in the .env file in the GitHub environment.
I will check this and let you know.

@596050
Due to some GitHub CI issues with the tests, I had to make several refactors. As a result, I need to close this PR. You can continue contributing from this new PR: https://github.com/langflow-ai/langflow/pull/2407.
Thank you very much for your help with this part.
I will close this PR, ok?


GitHub login not working, no auth provider registered

We have 2 auth provider configured Guest and Github.
We are getting the below exception with Github auth provider
{"error":{"name":"NotFoundError","message":"Auth provider registered for 'github' is misconfigured. This could mean the configs under auth.providers.github are missing or the environment variables used are not defined. Check the auth backend plugin logs when the backend starts to see more details.","stack":"NotFoundError: Auth provider registered for 'github' is misconfigured. This could mean the configs under auth.providers.github are missing or the environment variables used are not defined. Check the auth backend plugin logs when the backend starts to see more details.\n    at

Github should open the redirect url for authentication

Updated App-config.yaml file
Section Integration and Auth as below
auth:
providers:
github:
development:
clientId:
$env: AUTH_GITHUB_CLIENT_ID
clientSecret:
$env: AUTH_GITHUB_CLIENT_SECRET
production:
clientId:
$env: AUTH_GITHUB_CLIENT_ID
clientSecret:
$env: AUTH_GITHUB_CLIENT_SECRET
integrations:
github:
- host: github.com
apps:
- $include: github-app-credentials.yaml

Start backstage
Got to login screen, click on Github auth
Exception screen pop up pointing to localhost:7000/api/auth/github URL

Context
We are not able to standup and import custom templates to our environment.
Note the same exception is observed during importing templates.
Your Environment

Browser Information:

Output of yarn backstage-cli info:

C:\Users\amalhotra048\backstage>yarn backstage-cli info
yarn run v1.22.1
$ C:\Users\amalhotra048\backstage\node_modules.bin\backstage-cli info
OS:   Windows_NT 10.0.19042 - win32/x64
node: v16.14.2
yarn: 1.22.1
cli:  0.17.1-next.0 (local)
Dependencies:
@backstage/integration-react     1.0.1
@backstage/integration           1.1.0
@backstage/plugin-catalog-react  1.0.1
@backstage/plugin-home           0.4.20
@backstage/plugin-stack-overflow 0.1.0
Done in 4.75s.

Think this is because now the user is not in the Catalog? Maybe these docs can help you get setup with the users from github into the catalog https://backstage.io/docs/integrations/github/org.

I have the following setup done . Still getting the same User not found exception.
Not sure what is incorrect here.
Members your inputs are appreciated.
Now I am also observing the following
2022-05-02T16:35:31.669Z catalog warn No processor was able to handle reading of github-org:https://github.com/backstage-anks type=plugin entity=location:default/generated-
Task completed as per documentation:
Create an Org "Backstage-anks" and a GitHub App inside "Backstage-ankit-app". It currently have one owner and 1 member.
I added following setting in app-config.yml file
organization:
name: Backstage-anks
integrations:
github:
- host: github.com
token: ${GITHUB_TOKEN}
catalog:
processors:
githubOrg:
providers:
- target: https://github.com
locations:
- type: github-org
target: https://github.com/backstage-anks
rules:
- allow: [User, Group]
auth:
environment: development
providers:
github:
development:
clientId: ${AUTH_GITHUB_CLIENT_ID}
clientSecret: ${AUTH_GITHUB_CLIENT_SECRET}

What does your packages/backend/src/plugins/catalog.ts look like? And have you followed this guide for setting up Github Org data? https://backstage.io/docs/integrations/github/org#docsNav

I'm facing the issue, have you found the way to fix it? Please help me

@HieuMinh67 can you provide more details, and maybe look through the conversation above to see if there's anything else that can help you in here first? What's the error message you're seeing?

@HieuMinh67 can you provide more details, and maybe look through the conversation above to see if there's anything else that can help you in here first? What's the error message you're seeing?

This is the message I got and below is my app info
Dependencies:
@backstage/app-defaults                          1.0.4-next.2
@backstage/backend-common                        0.14.0, 0.14.1-next.2
@backstage/backend-tasks                         0.3.2, 0.3.3-next.2
@backstage/catalog-client                        1.0.3, 1.0.4-next.1
@backstage/catalog-model                         1.0.3, 1.1.0-next.2
@backstage/cli-common                            0.1.9
@backstage/cli                                   0.18.0-next.2
@backstage/config-loader                         1.1.2, 1.1.3-next.0
@backstage/config                                1.0.1
@backstage/core-app-api                          1.0.4-next.0
@backstage/core-components                       0.10.0-next.2
@backstage/core-plugin-api                       1.0.3
@backstage/errors                                1.0.0, 1.1.0-next.0
@backstage/integration-react                     1.1.2-next.2
@backstage/integration                           1.2.1, 1.2.2-next.2
@backstage/plugin-api-docs                       0.8.7-next.2
@backstage/plugin-app-backend                    0.3.34-next.2
@backstage/plugin-auth-backend                   0.15.0-next.2
@backstage/plugin-auth-node                      0.2.2, 0.2.3-next.1
@backstage/plugin-catalog-backend-module-github  0.1.4
@backstage/plugin-catalog-backend                1.2.0, 1.2.1-next.2
@backstage/plugin-catalog-common                 1.0.3, 1.0.4-next.0
@backstage/plugin-catalog-graph                  0.2.19-next.2
@backstage/plugin-catalog-import                 0.8.10-next.2
@backstage/plugin-catalog-react                  1.1.2-next.2
@backstage/plugin-catalog                        1.4.0-next.2
@backstage/plugin-github-actions                 0.5.7-next.2
@backstage/plugin-org                            0.5.7-next.2
@backstage/plugin-permission-common              0.6.2, 0.6.3-next.0
@backstage/plugin-permission-node                0.6.2, 0.6.3-next.1
@backstage/plugin-permission-react               0.4.3-next.0
@backstage/plugin-proxy-backend                  0.2.28-next.0
@backstage/plugin-scaffolder-backend             1.4.0-next.2
@backstage/plugin-scaffolder-common              1.1.1, 1.1.2-next.0
@backstage/plugin-scaffolder                     1.4.0-next.2
@backstage/plugin-search-backend-module-pg       0.3.5-next.2
@backstage/plugin-search-backend-node            0.6.3-next.1
@backstage/plugin-search-backend                 0.5.4-next.1
@backstage/plugin-search-common                  0.3.5, 0.3.6-next.0
@backstage/plugin-search-react                   0.2.2-next.2
@backstage/plugin-search                         0.9.1-next.2
@backstage/plugin-tech-radar                     0.5.14-next.2
@backstage/plugin-techdocs-backend               1.2.0-next.2
@backstage/plugin-techdocs-module-addons-contrib 1.0.2-next.2
@backstage/plugin-techdocs-node                  1.2.0-next.2
@backstage/plugin-techdocs-react                 1.0.2-next.1
@backstage/plugin-techdocs                       1.2.1-next.2
@backstage/plugin-user-settings                  0.4.6-next.2
@backstage/release-manifests                     0.0.4
@backstage/test-utils                            1.1.2-next.1
@backstage/theme                                 0.2.16-next.1
@backstage/types                                 1.0.0
@backstage/version-bridge                        1.0.1

Can you take a look at the previous comment from @Rugvip and answer this?

Do you have AUTH_GITHUB_CLIENT_ID and AUTH_GITHUB_CLIENT_SECRET set in your local environment? Another option is to use your local app-config.local.yaml and put the plaintext configuration there directly?

Can you take a look at the previous comment from @Rugvip and answer this?

Do you have AUTH_GITHUB_CLIENT_ID and AUTH_GITHUB_CLIENT_SECRET set in your local environment? Another option is to use your local app-config.local.yaml and put the plaintext configuration there directly?

Yes, I did put the plaintext configuration directly in app-config.yaml

Ok and is the above file app-config.yaml?
And also what does your packages/backend/src/plugins/auth.ts look like?

Yes, above file app-config.yaml and I didn't change packages/backend/src/plugins/auth.ts

ref https://github.com/backstage/backstage/issues/11119#issuecomment-1180155022
You can provide a auth provider like this
return await createRouter({
    logger: env.logger,
    config: env.config,
    database: env.database,
    discovery: env.discovery,
    tokenManager: env.tokenManager,
    providerFactories: {
      github: providers.github.create({
        signIn: {
          resolver(info, ctx) {
            const { profile } = info;
            const { displayName } = profile;
            const userRef = `user:default/${displayName}`; // Must be a full entity reference

            return ctx.issueToken({
              claims: {
                sub: userRef, // The user's own identity
                ent: [userRef], // A list of identities that the user claims ownership through
              },
            });
          }
        },
      }),
    }
  });

Going to close this then as fixed, please comment to re-open if something changes! :pray:

@HieuMinh67 can you give a more detailed explanation of what worked for you?  What does it mean that you "insert auth inside backend: in app-config.yaml"

Because there are 2 auth so I make a mistake

I have followed this discussion and tried everything... but still getting this error
{"error":{"name":"NotFoundError","message":"No auth provider registered for 'github'","stack":"NotFoundError: No auth provider registered for 'github'\n    at /workspace/backstagePOC/backstage-tutorial/node_modules/@backstage/plugin-auth-backend/dist/index.cjs.js:3541:15\n    at handleReturn (/workspace/backstagePOC/backstage-tutorial/node_modules/express-promise-router/lib/express-promise-router.js:24:23)\n    at /workspace/backstagePOC/backstage-tutorial/node_modules/express-promise-router/lib/express-promise-router.js:64:7\n    at Layer.handle [as handle_request] (/workspace/backstagePOC/backstage-tutorial/node_modules/express/lib/router/layer.js:95:5)\n    at trim_prefix (/workspace/backstagePOC/backstage-tutorial/node_modules/express/lib/router/index.js:328:13)\n    at /workspace/backstagePOC/backstage-tutorial/node_modules/express/lib/router/index.js:286:9\n    at Function.process_params (/workspace/backstagePOC/backstage-tutorial/node_modules/express/lib/router/index.js:346:12)\n    at next (/workspace/backstagePOC/backstage-tutorial/node_modules/express/lib/router/index.js:280:10)\n    at jsonParser (/workspace/backstagePOC/backstage-tutorial/node_modules/body-parser/lib/types/json.js:110:7)\n    at handleReturn (/workspace/backstagePOC/backstage-tutorial/node_modules/express-promise-router/lib/express-promise-router.js:24:23)\n    at jsonParser (/workspace/backstagePOC/backstage-tutorial/node_modules/express-promise-router/lib/express-promise-router.js:64:7)\n    at Layer.handle [as handle_request] (/workspace/backstagePOC/backstage-tutorial/node_modules/express/lib/router/layer.js:95:5)\n    at trim_prefix (/workspace/backstagePOC/backstage-tutorial/node_modules/express/lib/router/index.js:328:13)\n    at /workspace/backstagePOC/backstage-tutorial/node_modules/express/lib/router/index.js:286:9\n    at Function.process_params (/workspace/backstagePOC/backstage-tutorial/node_modules/express/lib/router/index.js:346:12)\n    at next (/workspace/backstagePOC/backstage-tutorial/node_modules/express/lib/router/index.js:280:10)"},"request":{"method":"GET","url":"/api/auth/github/start?scope=read%3Auser%20repo&origin=https%3A%2F%2F3000-rapidxdevel-backstagepo-qgnhs2lefe6.ws-us93.gitpod.io&env=development"},"response":{"statusCode":404}}
Any solution?

@KaranS-hexaware you can just put auth and all values above backend in app-config

I have followed this discussion and tried everything... but still getting this error {"error":{"name":"NotFoundError","message":"No auth provider registered for 'github'","stack":"NotFoundError: No auth provider registered for 'github'\n at /workspace/backstagePOC/backstage-tutorial/node_modules/@backstage/plugin-auth-backend/dist/index.cjs.js:3541:15\n at handleReturn (/workspace/backstagePOC/backstage-tutorial/node_modules/express-promise-router/lib/express-promise-router.js:24:23)\n at /workspace/backstagePOC/backstage-tutorial/node_modules/express-promise-router/lib/express-promise-router.js:64:7\n at Layer.handle [as handle_request] (/workspace/backstagePOC/backstage-tutorial/node_modules/express/lib/router/layer.js:95:5)\n at trim_prefix (/workspace/backstagePOC/backstage-tutorial/node_modules/express/lib/router/index.js:328:13)\n at /workspace/backstagePOC/backstage-tutorial/node_modules/express/lib/router/index.js:286:9\n at Function.process_params (/workspace/backstagePOC/backstage-tutorial/node_modules/express/lib/router/index.js:346:12)\n at next (/workspace/backstagePOC/backstage-tutorial/node_modules/express/lib/router/index.js:280:10)\n at jsonParser (/workspace/backstagePOC/backstage-tutorial/node_modules/body-parser/lib/types/json.js:110:7)\n at handleReturn (/workspace/backstagePOC/backstage-tutorial/node_modules/express-promise-router/lib/express-promise-router.js:24:23)\n at jsonParser (/workspace/backstagePOC/backstage-tutorial/node_modules/express-promise-router/lib/express-promise-router.js:64:7)\n at Layer.handle [as handle_request] (/workspace/backstagePOC/backstage-tutorial/node_modules/express/lib/router/layer.js:95:5)\n at trim_prefix (/workspace/backstagePOC/backstage-tutorial/node_modules/express/lib/router/index.js:328:13)\n at /workspace/backstagePOC/backstage-tutorial/node_modules/express/lib/router/index.js:286:9\n at Function.process_params (/workspace/backstagePOC/backstage-tutorial/node_modules/express/lib/router/index.js:346:12)\n at next (/workspace/backstagePOC/backstage-tutorial/node_modules/express/lib/router/index.js:280:10)"},"request":{"method":"GET","url":"/api/auth/github/start?scope=read%3Auser%20repo&origin=https%3A%2F%2F3000-rapidxdevel-backstagepo-qgnhs2lefe6.ws-us93.gitpod.io&env=development"},"response":{"statusCode":404}} Any solution?

Any updates? I am facing the same issue, tried everything listed here.

 What does it mean that you "insert auth inside backend: in app-config.yaml"

Because there are 2 auth so I make a mistake

Hi @henrypham67  could you help me out , i followed this and addressed the changes but while sign-in i still got error as
Origin 'http://localhost:7007' is not allowed

Hi there, same issue here
{"error":{"name":"NotFoundError","message":"Unknown auth provider 'github'","stack":"NotFoundError: Unknown auth provider 'github'\n    at <anonymous> (/home/fsriachos/backstage/node_modules/@backstage/plugin-auth-backend/src/service/router.ts:161:11)\n    at handleReturn (/home/fsriachos/backstage/node_modules/express-promise-router/lib/express-promise-router.js:24:23)\n    at /home/fsriachos/backstage/node_modules/express-promise-router/lib/express-promise-router.js:64:7\n    at Layer.handle [as handle_request] (/home/fsriachos/backstage/node_modules/express/lib/router/layer.js:95:5)\n    at trim_prefix (/home/fsriachos/backstage/node_modules/express/lib/router/index.js:328:13)\n    at /home/fsriachos/backstage/node_modules/express/lib/router/index.js:286:9\n    at param (/home/fsriachos/backstage/node_modules/express/lib/router/index.js:365:14)\n    at param (/home/fsriachos/backstage/node_modules/express/lib/router/index.js:376:14)\n    at Function.process_params (/home/fsriachos/backstage/node_modules/express/lib/router/index.js:421:3)\n    at next (/home/fsriachos/backstage/node_modules/express/lib/router/index.js:280:10)\n    at /home/fsriachos/backstage/node_modules/express/lib/router/index.js:646:15\n    at next (/home/fsriachos/backstage/node_modules/express/lib/router/index.js:265:14)\n    at Function.handle (/home/fsriachos/backstage/node_modules/express/lib/router/index.js:175:3)\n    at router (/home/fsriachos/backstage/node_modules/express/lib/router/index.js:47:12)\n    at handleReturn (/home/fsriachos/backstage/node_modules/express-promise-router/lib/express-promise-router.js:24:23)\n    at router (/home/fsriachos/backstage/node_modules/express-promise-router/lib/express-promise-router.js:64:7)"},"request":{"method":"GET","url":"/api/auth/github/start?scope=read%3Auser&origin=http%3A%2F%2Flocalhost%3A3000&flow=popup&env=development"},"response":{"statusCode":404}}

Any suggestions?
Thank you

Hi there, same issue here {"error":{"name":"NotFoundError","message":"Unknown auth provider 'github'","stack":"NotFoundError: Unknown auth provider 'github'\n at <anonymous> (/home/fsriachos/backstage/node_modules/@backstage/plugin-auth-backend/src/service/router.ts:161:11)\n at handleReturn (/home/fsriachos/backstage/node_modules/express-promise-router/lib/express-promise-router.js:24:23)\n at /home/fsriachos/backstage/node_modules/express-promise-router/lib/express-promise-router.js:64:7\n at Layer.handle [as handle_request] (/home/fsriachos/backstage/node_modules/express/lib/router/layer.js:95:5)\n at trim_prefix (/home/fsriachos/backstage/node_modules/express/lib/router/index.js:328:13)\n at /home/fsriachos/backstage/node_modules/express/lib/router/index.js:286:9\n at param (/home/fsriachos/backstage/node_modules/express/lib/router/index.js:365:14)\n at param (/home/fsriachos/backstage/node_modules/express/lib/router/index.js:376:14)\n at Function.process_params (/home/fsriachos/backstage/node_modules/express/lib/router/index.js:421:3)\n at next (/home/fsriachos/backstage/node_modules/express/lib/router/index.js:280:10)\n at /home/fsriachos/backstage/node_modules/express/lib/router/index.js:646:15\n at next (/home/fsriachos/backstage/node_modules/express/lib/router/index.js:265:14)\n at Function.handle (/home/fsriachos/backstage/node_modules/express/lib/router/index.js:175:3)\n at router (/home/fsriachos/backstage/node_modules/express/lib/router/index.js:47:12)\n at handleReturn (/home/fsriachos/backstage/node_modules/express-promise-router/lib/express-promise-router.js:24:23)\n at router (/home/fsriachos/backstage/node_modules/express-promise-router/lib/express-promise-router.js:64:7)"},"request":{"method":"GET","url":"/api/auth/github/start?scope=read%3Auser&origin=http%3A%2F%2Flocalhost%3A3000&flow=popup&env=development"},"response":{"statusCode":404}}

Any suggestions?
Thank you

for anyone else having this error when setting up google oauth this is how I resolved it
yarn add @backstage/plugin-auth-backend-module-google-provider in ./packages/backend
and add the following to the backend/src/index.ts
backend.add(import('@backstage/plugin-auth-backend-module-google-provider'));

More information here:
https://backstage.io/docs/auth/identity-resolver#building-custom-resolvers

I am also facing the same issue related to popup for SSO using Github not working

I followed the link from @seslly and added: -
backend.add(import('@backstage/plugin-auth-backend-module-github-provider')); to the backend/src/index.ts file.
Its now working. The guide seems to expect that value to already be there, however, its not in the index.ts file in the boilerplate deployment I used from the Getting Started guide.

I had the "GitHub provider is not configured to support sign-in" issue. I ended up in a different issue thread, and adding the code stated in this answer fixed my issue: https://github.com/backstage/backstage/issues/23748#issuecomment-2089061001


[vim] Correct the scroll position for zt & zb.

zt was placing 40% of the line above the visible area, and zb was placing it too high.

@mightyguava @heppe Want to take a look at this?

Added a couple of tests.

one minor style nit, but other than that, this looks good to merge.

Fixed the whitespace in the tests.

looks good to merge

Thanks! Merged as 237a6b6


Running the example_stft.py and example_melgram.py

Hi Keunwoochoi,
When I run the example_stft.py , I get this error message :
Using TensorFlow backend.
Traceback (most recent call last):
  File "example_stft.py", line 8, in <module>
    specgram = stft.Spectrogram(n_dft=512, input_shape=(len_src, 1), n_hop=256)
  File "/home/claire/Bureau/All/Stage2016/Codes/keras_STFT_layer-master/stft.py", line 220, in Spectrogram
    logamplitude=logamplitude)
  File "/home/claire/Bureau/All/Stage2016/Codes/keras_STFT_layer-master/stft.py", line 176, in get_spectrogram_tensors
    STFT_magnitude = Logam_layer()(STFT_magnitude)
  File "/home/claire/anaconda2/lib/python2.7/site-packages/keras/engine/topology.py", line 514, in __call__
    self.add_inbound_node(inbound_layers, node_indices, tensor_indices)
  File "/home/claire/anaconda2/lib/python2.7/site-packages/keras/engine/topology.py", line 572, in add_inbound_node
    Node.create_node(self, inbound_layers, node_indices, tensor_indices)
  File "/home/claire/anaconda2/lib/python2.7/site-packages/keras/engine/topology.py", line 149, in create_node
    output_tensors = to_list(outbound_layer.call(input_tensors[0], mask=input_masks[0]))
  File "/home/claire/anaconda2/lib/python2.7/site-packages/keras/layers/core.py", line 556, in call
    return self.function(x, **arguments)
  File "/home/claire/Bureau/All/Stage2016/Codes/keras_STFT_layer-master/stft.py", line 89, in <lambda>
    return Lambda(lambda x: logam(x), name=name,
  File "/home/claire/Bureau/All/Stage2016/Codes/keras_STFT_layer-master/stft.py", line 79, in logam
    log_spec = 10*K.log(K.maximum(x, 1e-10))/K.log(10)
  File "/home/claire/anaconda2/lib/python2.7/site-packages/keras/backend/tensorflow_backend.py", line 566, in log
    return tf.log(x)
  File "/home/claire/anaconda2/lib/python2.7/site-packages/tensorflow/python/ops/gen_math_ops.py", line 1094, in log
    result = _op_def_lib.apply_op("Log", x=x, name=name)
  File "/home/claire/anaconda2/lib/python2.7/site-packages/tensorflow/python/ops/op_def_library.py", line 530, in apply_op
    _Attr(op_def, input_arg.type_attr))
  File "/home/claire/anaconda2/lib/python2.7/site-packages/tensorflow/python/ops/op_def_library.py", line 61, in _SatisfiesTypeConstraint
    ", ".join(dtypes.as_dtype(x).name for x in allowed_list)))
TypeError: DataType int32 for attr 'T' not in list of allowed values: float16, float32, float64, complex64, complex128

I'm sorry it's a bit long but I don't understand where it comes from.
And also when I'm running the example_melgram.py, I have this error :
Traceback (most recent call last):
  File "example_melgram.py", line 8, in <module>
    melgram = melgram.Melspectrogram(n_dft=512, n_hop=256, input_shape=(len_src, 1), sr=12000)
TypeError: Melspectrogram() takes at least 3 arguments (4 given)

Could you help me please,
Thank you in advance!

Can you first try it with Theano? Or with dim_ordering()=th?

PS. Formatting with markdown always help!

So I changed to Theano backend in the keras.json file and now I get this error...
Using Theano backend.
output shape of logam: (None, 469, 257)
Traceback (most recent call last):
File "example_stft.py", line 11, in
src, sr = librosa.load('src/bensound-cute.mp3', sr=12000, duration=10.0)  # whole signal
File "/home/claire/anaconda2/lib/python2.7/site-packages/librosa/core/audio.py", line 109, in load
with audioread.audio_open(os.path.realpath(path)) as input_file:
File "/home/claire/anaconda2/lib/python2.7/site-packages/audioread/init.py", line 114, in audio_open
raise NoBackendError()
audioread.NoBackendError
Thanks again
PS. I heard of Markdown recently and begin to use it but what do you mean with it now? Formatting in markdown to post on Git? Sorry that I don't understand.

:) Yep. Now I see audioread.NoBackendError(). It's an error from librosa (which uses audioread to decode audio signals) and nothing about keras or stft layer. It's strange though, those files are standard mp3 format and I assumes it should be able to open it in any OS.

Oh, I didnt make it for Tensorflow. Can you try it with Theano? It's actually not a big problem, I'll try to fix it for TF soon.

On 23 Oct 2016, at 09:57, pianomanu<EMAIL_ADDRESS>wrote:
Hi Keunwoochoi,
When I run the example_stft.py , I get this error message :
Using TensorFlow backend.
Traceback (most recent call last):
File "example_stft.py", line 8, in
specgram = stft.Spectrogram(n_dft=512, input_shape=(len_src, 1), n_hop=256)
File "/home/claire/Bureau/All/Stage2016/Codes/keras_STFT_layer-master/stft.py", line 220, in Spectrogram
logamplitude=logamplitude)
File "/home/claire/Bureau/All/Stage2016/Codes/keras_STFT_layer-master/stft.py", line 176, in get_spectrogram_tensors
STFT_magnitude = Logam_layer()(STFT_magnitude)
File "/home/claire/anaconda2/lib/python2.7/site-packages/keras/engine/topology.py", line 514, in call
self.add_inbound_node(inbound_layers, node_indices, tensor_indices)
File "/home/claire/anaconda2/lib/python2.7/site-packages/keras/engine/topology.py", line 572, in add_inbound_node
Node.create_node(self, inbound_layers, node_indices, tensor_indices)
File "/home/claire/anaconda2/lib/python2.7/site-packages/keras/engine/topology.py", line 149, in create_node
output_tensors = to_list(outbound_layer.call(input_tensors[0], mask=input_masks[0]))
File "/home/claire/anaconda2/lib/python2.7/site-packages/keras/layers/core.py", line 556, in call
return self.function(x, *arguments)
File "/home/claire/Bureau/All/Stage2016/Codes/keras_STFT_layer-master/stft.py", line 89, in
return Lambda(lambda x: logam(x), name=name,
File "/home/claire/Bureau/All/Stage2016/Codes/keras_STFT_layer-master/stft.py", line 79, in logam
log_spec = 10K.log(K.maximum(x, 1e-10))/K.log(10)
File "/home/claire/anaconda2/lib/python2.7/site-packages/keras/backend/tensorflow_backend.py", line 566, in log
return tf.log(x)
File "/home/claire/anaconda2/lib/python2.7/site-packages/tensorflow/python/ops/gen_math_ops.py", line 1094, in log
result = _op_def_lib.apply_op("Log", x=x, name=name)
File "/home/claire/anaconda2/lib/python2.7/site-packages/tensorflow/python/ops/op_def_library.py", line 530, in apply_op
_Attr(op_def, input_arg.type_attr))
File "/home/claire/anaconda2/lib/python2.7/site-packages/tensorflow/python/ops/op_def_library.py", line 61, in _SatisfiesTypeConstraint
", ".join(dtypes.as_dtype(x).name for x in allowed_list)))
TypeError: DataType int32 for attr 'T' not in list of allowed values: float16, float32, float64, complex64, complex128
I'm sorry it's a bit long but I don't understand where it comes from.
And also when I'm running the example_melgram.py, I have this error :
Traceback (most recent call last):
File "example_melgram.py", line 8, in
melgram = melgram.Melspectrogram(n_dft=512, n_hop=256, input_shape=(len_src, 1), sr=12000)
TypeError: Melspectrogram() takes at least 3 arguments (4 given)
Could you help me please,
Thank you in advance!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Thanks again for the answer.
I found a way so that example_stft.py works. I installed ffmpeg with these commands
sudo add-apt-repository ppa:mc3man/trusty-media
sudo apt-get update
sudo apt-get install ffmpeg```

Then example_stft.py works (still not with tensorflow) but example_melgram.py still doesn't work and I have this error message :
```Traceback (most recent call last):
  File "example_melgram.py", line 8, in <module>
    melgram = melgram.Melspectrogram(n_dft=512, n_hop=256, input_shape=(len_src, 1), sr=12000)
TypeError: Melspectrogram() takes at least 3 arguments (4 given)```

I thank you in advance for your help,

Nice, so does it now work with both Theano and Tensorflow?

On 25 Oct 2016, at 15:30, pianomanu<EMAIL_ADDRESS>wrote:
Thanks again for the answer.
I found a way so that example_stft.py works. I installed ffmpeg with these commands
sudo add-apt-repository ppa:mc3man/trusty-media
sudo apt-get update
sudo apt-get install ffmpeg```
Then example_stft.py works (still not with tensorflow) but example_melgram.py still doesn't work and I have this error message :
  File "example_melgram.py", line 8, in <module>
    melgram = melgram.Melspectrogram(n_dft=512, n_hop=256, input_shape=(len_src, 1), sr=12000)
TypeError: Melspectrogram() takes at least 3 arguments (4 given)```

I thank you in advance for your help,
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

No, It doesn't work with Tensorflow.
Also, do you have an idea why I get this error message for example_melgram.py??

Sorry, I missed you already mentioned that. Thanks for reporting!
I just updated example code, please pull the repo, and run the example codes and ipython notebooks.

It works on Theano with both tf and th image ordering.
It doesn't work on Tensorflow now.


simulator: take snapshot count into account

What have you changed? (required)
This PR takes the snapshot count into consideration and ignores ApplyingSnapCount temporarily because applying snapshot can be finished quickly. But there are still many problems to simulate the real behavior of TiKV.
Any suggestions? @disksing @nolouch
What are the type of the changes (required)?

Improvement (non-breaking change which is an improvement to an existing feature)

How has this PR been tested (required)?

Manual tests

Does this PR affect documentation (docs/docs-cn) update? (optional)

Refer to a related PR or issue link (optional)
Benchmark result if necessary (optional)
Add a few positive/negative examples (optional)

Please approve the PR. @nolouch


Fix incompatibility with webpack 2.2.0-rc.0

enhanced-resolve has been bumped to 3.0.

Coverage remained the same at 94.86% when pulling 1bc31c1944a6a0aa0c988e5fd1cd3c6e77d8200e on Kovensky:patch-1 into f3fd43ca9a9b3b5742dd04a28137328d14f902dc on benmosher:master.

Coverage remained the same at 94.86% when pulling 1bc31c1944a6a0aa0c988e5fd1cd3c6e77d8200e on Kovensky:patch-1 into f3fd43ca9a9b3b5742dd04a28137328d14f902dc on benmosher:master.

Coverage remained the same at 94.86% when pulling 1bc31c1944a6a0aa0c988e5fd1cd3c6e77d8200e on Kovensky:patch-1 into f3fd43ca9a9b3b5742dd04a28137328d14f902dc on benmosher:master.

thanks!
were you able to test against a project using Webpack 2.2.0? I don't have one handy.
I'm going to go ahead and merge this though, I figure it can only help


Next prerelease: 3.0.0-rc.0

Preparation for release candidate of next major release.
Not sure, but maybe I will update changelog file with gren after release (it's too much to fill in by hand).

waiting for the new ui-lib rc version

This PR follows the "old" release process but we will try a new process with release-drafter instead gren. I already tested it in a private repo and started to implement it here in this repo #290 and #291. When everything work as expected, we can close this PR without merging!


Misleading error message on privileged ports

If you try to run mailcatcher on an privileged port without root you get the error message
~~> ERROR: Something's using port 25. Are you already running MailCatcher?
even if no other programm uses the port.

Sadly there is no way to know. The underlying error message is:
#<RuntimeError: no acceptor (port is in use or requires root privileges)>

If you can figure it out then patches are welcomed! :-)

you could simpy check if the given port is <=1024


Preparing release 1.10.0

Resolves #1321

There is only one commit https://github.com/jaegertracing/jaeger-ui/commits/master and no new version of UI has been released.

@pavolloffay Per Yuri's request we cut a UI release which has two commits, which are fairly minor bug fixes.
https://github.com/jaegertracing/jaeger-ui/releases/tag/v1.0.1

@tiffon would you like to bump it here?
We could do patch release or wait for the next release #1343. I would like to get out 1.11 in 2 weeks.


Build failed

When following your instructions to install I got this output.
Compiling nalgebra v0.13.1
error: failed to run custom build command for `glfw-sys v3.2.2`
process didn't exit successfully: `/tmp/cargo-install.ij9EEj2EbdnX/release/build/glfw-sys-7281d2a56283e13b/build-script-build` (exit code: 101)
--- stdout
running: "cmake" "/home/aaron/.cargo/registry/src/github.com-1ecc6299db9ec823/glfw-sys-3.2.2/." "-DGLFW_BUILD_EXAMPLES=OFF" "-DGLFW_BUILD_TESTS=OFF" "-DGLFW_BUILD_DOCS=OFF" "-DCMAKE_INSTALL_PREFIX=/tmp/cargo-install.ij9EEj2EbdnX/release/build/glfw-sys-93bf9f8db48e2b8c/out" "-DCMAKE_C_FLAGS= -ffunction-sections -fdata-sections -fPIC -m64" "-DCMAKE_C_COMPILER=/usr/bin/cc" "-DCMAKE_CXX_FLAGS= -ffunction-sections -fdata-sections -fPIC -m64" "-DCMAKE_CXX_COMPILER=/usr/bin/c++" "-DCMAKE_BUILD_TYPE=Release"
-- The C compiler identification is Clang 4.0.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Looking for pthread.h
-- Looking for pthread.h - found
-- Looking for pthread_create
-- Looking for pthread_create - not found
-- Looking for pthread_create in pthreads
-- Looking for pthread_create in pthreads - not found
-- Looking for pthread_create in pthread
-- Looking for pthread_create in pthread - found
-- Found Threads: TRUE
-- Could NOT find Vulkan (missing: VULKAN_LIBRARY VULKAN_INCLUDE_DIR)
-- Using X11 for window creation
-- Looking for XOpenDisplay in /usr/lib/x86_64-linux-gnu/libX11.so;/usr/lib/x86_64-linux-gnu/libXext.so
-- Looking for XOpenDisplay in /usr/lib/x86_64-linux-gnu/libX11.so;/usr/lib/x86_64-linux-gnu/libXext.so - found
-- Looking for gethostbyname
-- Looking for gethostbyname - found
-- Looking for connect
-- Looking for connect - found
-- Looking for remove
-- Looking for remove - found
-- Looking for shmat
-- Looking for shmat - found
-- Looking for IceConnectionNumber in ICE
-- Looking for IceConnectionNumber in ICE - found
-- Found X11: /usr/lib/x86_64-linux-gnu/libX11.so
-- Configuring incomplete, errors occurred!
See also "/tmp/cargo-install.ij9EEj2EbdnX/release/build/glfw-sys-93bf9f8db48e2b8c/out/build/CMakeFiles/CMakeOutput.log".
See also "/tmp/cargo-install.ij9EEj2EbdnX/release/build/glfw-sys-93bf9f8db48e2b8c/out/build/CMakeFiles/CMakeError.log".

--- stderr
CMake Error at CMakeLists.txt:222 (message):
  The RandR library and headers were not found

thread 'main' panicked at '
command did not execute successfully, got: exit code: 1

build script failed, must exit now', /home/aaron/.cargo/registry/src/github.com-1ecc6299db9ec823/cmake-0.1.29/src/lib.rs:632:5
note: Run with `RUST_BACKTRACE=1` for a backtrace.

warning: build failed, waiting for other jobs to finish...
error: failed to compile `urdf-viz v0.9.0`, intermediate artifacts can be found at `/tmp/cargo-install.ij9EEj2EbdnX`

Caused by:
  build failed

this is repeat of readme, but I want to confirm
Really ran below command?
sudo apt-get install cmake xorg-dev libglu1-mesa-dev

and tell me your OS.

I was missing xorg-dev

OK! Good luck!


Convert-BcAppsToRuntimePackages: Allow to skip failing apps, run scriptblock after each processed runtime

Convert-BcAppsToRuntimePackages is an easy to use bulk command without caring about container creation and file exchange.
Most times this is a better choice over Get-BcContainerAppRuntimePackage for simplicity.
However, there could be reasons to allow apps failing without breaking the whole process. And there is an option to handle processing for each created runtime separately.
.Parameter skipFailingApps
If set, a failing app (compiler error or anything else) does not stop the whole process but continues with the next app.
.Parameter afterEachRuntimeCreation
A script block to be executed after an app has been converted to a runtime package.
The parameters are 'appFile', containing the source path and 'runtimeFile' containing the path
to the newly extracted runtime file or $null if the process has failed and skipFailingApps has been set.

Will review this tomorrow, sorry for the delay

Huh? You deleted the target branch?

That was a mistake - will recreate it.

Sorry

If you can recreate the PR?

either on master or dev


tests(api/status): improve test performance of status/ready

Summary
This PR will reduce the waiting time for dp testing.
KAG-1650
Checklist

[ ] The Pull Request has tests
[ ] There's an entry in the CHANGELOG
[ ] There is a user-facing docs PR against https://github.com/Kong/docs.konghq.com - PUT DOCS PR HERE

Full changelog

use nginx_main_worker_processes
start cp before dp

Test comparison:
master:
.......  RUN 102: Hybrid Mode - status ready #postgres dp status ready endpoint for no config should return 200 on data plane after
9366.70   OK 102: Hybrid Mode - status ready #postgres dp status ready endpoint for no config should return 200 on data plane after configuring

PR:
.......  RUN 102: Hybrid Mode - status ready #postgres dp status ready endpoint for no config should return 200 on data plane after
1973.25   OK 102: Hybrid Mode - status ready #postgres dp status ready endpoint for no config should return 200 on data plane after configuring


MLPAB-2117 - Update documentation

Purpose
Provide examples of how to use image and zip artifacts.
Fixes: MLPAB-2117
Approach

fix pre-release mode for releases

Learning
Any tips and tricks, blog posts or tools which helped you. Plus anything notable you've discovered about the Modernising LPA service

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 54.59%. Comparing base (9da6046) to head (1aa8e6c).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #396   +/-   ##
=======================================
  Coverage   54.59%   54.59%
=======================================
  Files           4        4
  Lines         185      185
=======================================
  Hits          101      101
  Misses         72       72
  Partials       12       12

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Unescape pipe escaping for table cells

Fixes #442.
Note that there's no test here. While we have a sample test for something simple, we don't really have test infrastructure for "here's some Markdown, and here's the expected converted Word document". The Word conversion code always creates an actual file, as far as I can see, which also hinders testing.
Some options:

If the Word document is byte-for-byte reproducible, we could have "sample JSON, expected Word document" pairs
We could easily write a unit test for just the code that's changed in this case, but it doesn't help in the longer term, as most changes really need the wider context

I think the first option is the way to go, but it will require a bit of refactoring to allow easy generation of a single-Markdown-file spec (possibly without TOC). I'll try that as a separate commit, still in this PR for now just for simplicity.
(I don't know what we do if the precise content changes each time...)

Second commit contains a rudimentary test framework. While crude, I think it's better than nothing - we can iterate over time.

Over time, I'd like to have our test code be more concise, but I agree that's a task for another day.

My hope is that the new infrastructure means we just need a single line of code and a pair of files for any change that is basically "Markdown x leads to XML y".
I suspect we could get the size of the XML file down if we remove all the bits that are just about the heading (which is required for parsing the Markdown) - I suggest we wait until we've got a few more files so we can see the commonality.


fix: my bug in PR #1

@sgromkov am so sorry.
In PR #1 has bug. I missed it on local tests, appeared in production 😔

❤


Config option to disable the stemmer

From https://github.com/olivernn/lunr.js/issues/38 there are some cases in which you want to turn off lunrjs's stemmer (e.g., with it on "onboard" is the stem and "onboardi" fails to match it, but "onboarding" matches that stem).
It would be nice to be able to have a config option to remove the lunr stemmer the indexer's pipeline.

The given method for removing functions from the pipeline is:
index.pipeline.remove(index.stemmer) or
this.pipeline.remove(lunr.stemmer) if within the shortcut initializer
or to create an empty index and never add the unwanted pipeline functions. A config option would be further redundant.

Unless I'm missing something it seems you have to remove the stemmer from the pipeline before the index is built. Currently the index is built by the jekyll plugin in this file: https://github.com/slashdotdash/jekyll-lunr-js-search/blob/master/lib/jekyll_lunr_js_search/indexer.rb
That means we have no control over removing the stemmer before that point. It seems a config option for configuring the indexer is the only option?


multi-output regression - memory overload

Hi! I was playing around with the recent implementation of multi-output regression. My training dataset has about 2000 observations x 500 observations and the task would be to predict 400 target features. After couple of rounds of training I quickly get memory overload (512 GB RAM). Each round of training would take significantly more RAM than previous.
There is nothing special in the code that I ran:
reg = xgb.XGBRegressor(
    tree_method="hist",
    n_estimators=30,
    n_jobs=1,
    max_depth=8,
    multi_strategy="multi_output_tree",
    subsample=0.3,
)

Was multi-output regression meant to be run on such datasets? Thanks for the help!

We are still working with a small number of targets, otherwise the gradient histogram can eat up all the memory. See https://github.com/dmlc/xgboost/issues/9043 Algorithmic Optimization section for potential options in the future. At the moment, this is a limitation for tree-based multi-target regression.

Closing in favor of https://github.com/dmlc/xgboost/issues/9043 .


Build.SourceBranchName does not include full name, if name includes forward slash

What's not working?
Current result

Build.SourceBranch
Build.SourceBranchName

refs/heads/feature/mynewfeature
mynewfeature

refs/heads/bug/mybug
mybug

Expected result

Build.SourceBranch
Build.SourceBranchName

refs/heads/feature/mynewfeature
feature/mynewfeature

refs/heads/bug/mybug
bug/mybug

The issue is simple. The current value of $(Build.SourceBranch) is actually wrong, leading to non-existent named branches.
Additional info
The same of #838 that has been closed without a real response.
For sure as a community we should contribute by opening a PR and not to pretend, but to ignore issues from the staff is another matter IMHO, so I opened this issue to track it and also be able to know where we can contribute.

In the meantime, if the need of the real name of branch it to do a git checkout, this should solve IMHO, basically by doing a checkout for the reference name with prefixes (e.g.: refs/heads/<branch_name>):
git update-ref $(Build.SourceBranch) $(Build.SourceVersion) # point the named branch reference to the build commit's SHA-1
git symbolic-ref HEAD $(Build.SourceBranch) # point the symbolic reference HEAD to the named branch reference

Changing this behaviour will break our pipelines. We use Build.SourceBranchName for container image tags, which can't contain slashes. Introducing a different variable might make sense though. (See #3076)
(My guess is that the branch name was treated like a file path, where the last part is the name)
There is an easy workaround. (There might be other options as well)
(The current behaviour is not correct, but breaking changes seems like a bad idea)

Hi @maxgio92 this change could break other users - so creating separate variable for this purpose could be the more safe approach here.
Since adding of new variable is related to some changes in Azure DevOps side - could you please create ticket on https://developercommunity.visualstudio.com/search?space=21 to get right eyes on it?

Hi @anatolybolshakov, sure, thank you.

Hi @mohag that workaround isn't correct IMHO as git references strings are not always so simple. Anyway thank you :)

Sorry @anatolybolshakov but I didn't find how can I create a new one discussion/ticket there :( Could you help me?

@maxgio92 sure, you can report about the issue here https://developercommunity.visualstudio.com/report?space=21&entry=problem

Thank you, I just opened a case

@maxgio92 ok thanks! Could you please leave a link to developer community ticket here to track it?
Let me close this one at the moment since there's nothing to on agent side currently. Please feel free to ask any further questions.


Implement TracerClock and abstract away "now"

Motivation:
we do not want to be bound to DispatchWallTime, but we cannot require Clock. We need to introduce a shim type TracerClockProtocol that in the future we'll be able to conform a "good Swift clock" to.
This removes any dependencies on dispatch and makes the Time source swappable. We also implement our own unix timestamp clock.
The core of the change is:

resolves https://github.com/apple/swift-distributed-tracing/issues/71
WIll get to clean this up and make all versions work soon. At least locally confirmed swiftlang-<IP_ADDRESS>.8 worked fine

Just need to get 5.6 done in the overloads maddness and we're done here 🥳

Thanks for the review @FranzBusch I'm going to merge so we can give this a round of testing


Make maximum subscription queue length customizable

I'm opening it as a draft PR because I didn't update the docs yet but feel free to check it out

This PR will help me with https://github.com/api3dao/tasks/issues/626 too because I will run the exhaustive tests with a queue length of 3 (as the logic that works for 3 should also work for 5 or 10)


Rule 200005 missing log action?

Describe the bug
It appears that the rule 200005 is missing the log action, which is present for the other rules of the ModSecurity Recommended Rules.
This applies to the version

v3.0.13: https://github.com/owasp-modsecurity/ModSecurity/blob/v3.0.13/modsecurity.conf-recommended#L158-L159, as well as
v2.9.8: https://github.com/owasp-modsecurity/ModSecurity/blob/v2.9.8/modsecurity.conf-recommended#L111-L112.

The other rules with a deny action all have the log action:
v3.0.13:
$ grep -E ",(log|deny)" modsecurity.conf-recommended
"id:'200007', phase:2,t:none,log,deny,status:400,msg:'Failed to fully parse request body due to large argument count',severity:2"
"id:'200002', phase:2,t:none,log,deny,status:400,msg:'Failed to parse request body.',logdata:'%{reqbody_error_msg}',severity:2"
"id:'200003',phase:2,t:none,log,deny,status:400, \
    "id:'200004',phase:2,t:none,log,deny,msg:'Multipart parser detected a possible unmatched boundary.'"
        "id:'200005',phase:2,t:none,deny,msg:'ModSecurity internal error flagged: %{MATCHED_VAR_NAME}'"

v2.9.8:
$ grep -E ",(log|deny)" modsecurity.conf-recommended
"id:'200002', phase:2,t:none,log,deny,status:400,msg:'Failed to parse request body.',logdata:'%{reqbody_error_msg}',severity:2"
"id:'200003',phase:2,t:none,log,deny,status:400, \
"id:'200004',phase:2,t:none,log,deny,msg:'Multipart parser detected a possible unmatched boundary.'"
        "id:'200005',phase:2,t:none,deny,msg:'ModSecurity internal error flagged: %{MATCHED_VAR_NAME}'"

Logs and dumps
Not applicable.
To Reproduce
Not applicable.
Expected behavior
I would expect the rule 200005 to explicitly use the log action like the other rules.
Server (please complete the following information):

ModSecurity version (and connector): v3.0.13 and v2.9.8
WebServer: Not applicable.
OS (and distro): Not applicable.

Rule Set (please complete the following information):

Running any public or commercial rule set? ModSecurity Recommended Rules
What is the version number? Not applicable.

Additional context
--

Hi @studersi,
thanks for reporting this - yes, you are right, that's the expected form for that rule (in both cases: v2 and v3).
Would you mind to send PR's (for both versions)?

See PR's #3266 and #3267 - those solve this issue in both versions.
Feel free to close this if there is no other question.

See PR's #3266 and #3267 - those solve this issue in both versions.
Feel free to close this if there is no other question.

Perfect, thanks @airween!


Fix for Negative Repeat Count in Scheduler (#101)

Hello Folks,
The line of code s.repeats += -1 in the scheduler function has been commented out. This change is based on the understanding that s.repeats is incorrectly used as a counter for the number of executions of a task, which results in negative values once the task has been executed more times than initially scheduled.
Best Regards
Tobias

Hello,
Sorry I have to write with my mobile phone. So my text will be shorter then my first one.
I pushed another fix, this should now fix the already broken repeats with numbers like -3737
Decreasing Numbers should now only affect numbers higher then 0.

I checked the tests, it seems something is wrong with a multidict. Gcc failed to build.I will look into it.

It seems that gcc is missing to build everything.
error: command 'gcc' failed: No such file or directory
Are you starting the tests from your system or a virtual environment?
Can you check if everything is installed correctly?

I executed the tests with docker-compose like described in your project description.
Everything was running fine:

A few Warnings about deprecated settings, if Django 5 will be used.
I installed the newest Docker Version and started your Test Script within my Virtual Environment.

Thanks for looking into it. The CI error is not due to your PR. It seems unrelated, looks like it has to do with the coveralls library. In any case, this looks good, will merge it.
Thanks!


Kindly ask a question about get_methods()

Hi guys, I am trying to analyze an android app and the code is:
a, d, dx = AnalyzeAPK(path)
for d_one in d:
    for method in d_one.get_methods():
        g = dx.get_method(method)

in the code, the dx.get_method() want to receive an EncodedMethod object as parameter, however, the method is a MethodIdItem object, and the g is None. I think it is a bit weird, could somebody figure out why the class of method is MethodIdItem but not EncodedMethod? Thank you!

Oh, I think I should use get_encoded_methods to get EncodedMethod :)


Standard nnUNet environment variables overwritten

In my setup the (nnUNetv2) paths.py contain the lines:
base = join(os.sep.join(file.split(os.sep)[:-3]), 'data') # or you can set your own path, e.g., base = '/home/user_name/Documents/U-Mamba/data'
nnUNet_raw = join(base, 'nnUNet_raw') # os.environ.get('nnUNet_raw')
nnUNet_preprocessed = join(base, 'nnUNet_preprocessed') # os.environ.get('nnUNet_preprocessed')
nnUNet_results = join(base, 'nnUNet_results') # os.environ.get('nnUNet_results')
where the nnUNet environment variables are ignored and redefined to some subdirectory of the base (code) directory. Took me a while why U-Mamba did not see my data...

Hi,
the paths to directories of datasets and trained model weights in U-Mamba are preset to the codebase's data directory U-Mamba/data to avoid conflicting with the environment variables for preexisting nnUNet instances.
An instruction for configuration datasets is provided in here; links to the raw datasets and the pretrained weights for inference are also included.


Generate the default_preferences.json file from AppOptions

Currently any editing of the preferences require updates in three separate files, which isn't a great developer experience to say the least.
This has annoyed me sufficiently to write this patch, which moves the definition of all preferences into AppOptions and adds a new gulp task to generate the default_preferences.json file for the builds where it's needed.

/botio lint

/botio-linux preview

/botio-linux preview

Nice work! I'm glad that this has become easier to manage now.


Group Types supported for RLS

This page should describe the different types of groups that are or are not supported for RLS.  (There are four different types of groups).
This is surely a common question and yet inexplicably not answered in this documentation.
In the end I found an old answer in the following video (which explains the four different types):
https://www.youtube.com/watch?v=oxYQ2GGefrs
I am not sure if that answer is correct today.
Seems unbelieve that O365 groups are not supported for RLS!
Irrespective of that, this page should make it clear which of the four types of groups are supported and which types aren't supported for RLS.

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

ID: d5505062-94f3-e15d-a52f-ce1ac7f8cb69
Version Independent ID: 34076b73-0ded-2111-ed44-2a31e07deb53
Content: Row-level security (RLS) with Power BI - Power BI
Content Source: powerbi-docs/admin/service-admin-rls.md
Service: powerbi
Sub-service: powerbi-admin
GitHub Login: @paulinbar
Microsoft Alias: painbar

Hi, @cbailiss -- thanks for your suggestion! Passing it along to the author for consideration.

Hi @cbailiss ,
Thank you for your suggestion.  We've made the update and set the article to republish.
All the best,
The DOCS team


Add Hacker Web

https://cheeaun.github.io/hackerweb/

Unfortunately, doesn't look optimized for mobile. Also, doesn't throw install banner on load, though it does have a SW.

cc @cheeaun

@shwetank not sure what you mean by 'doesn't look optimized for mobile' 🤔
As for the install banner, you mean the one done by the browser or some custom banner that I have to code?

@cheeaun On my nexus 6P it looks like this on first load (on both Opera for Android as well as Chrome for Android).

By the install banner - I mean the banner which the browser pops out if it detects that a site is a progressive web app. More details here https://dev.opera.com/blog/web-app-install-banners/
I haven't looked into the code much yet, but it seems you have everything you need in terms of whats required in the manifest file and its served over https too. Requires further investigation why the browser is not displaying the app install banner on this site.

@shwetank omg that screenshot 😱😱😱 okay will fix this!

@shwetank for some reason I couldn't replicate this bug on my Nexus 5X, on both Opera for Android and Chrome. However, this feels surprisingly very similar to this bug ( https://bugs.chromium.org/p/chromium/issues/detail?id=432813 ) so I suspect if it's even a bug on my app at all 🤔

This now lives on https://app.hackerwebapp.com/
I don't get an install banner though.


Transaction replaced by RBF History in Mint，causing sophon to be lost？？

Mint sophon is missing!
Does Mint accept address changes?
original transaction
https://mempool.space/tx/000000ed7c1cfbe1ece18b866242209dd8a9fc9f84ec9a8c6727438c14a0689e
Transactions that were replaced
https://mempool.space/tx/000000424f3a0c53edc1c89f5186859f43fc806e3bf1c1471c8ffa1c18f65b70
causing sophon to be lost
what do I do?

If you can find nonce and time in log when create 000000424f3a0c53edc1c89f5186859f43fc806e3bf1c1471c8ffa1c18f65b70, you can try with https://github.com/atlaslabsapp/atomicals-js/tree/handle_no_reveal, like https://github.com/atomicals/atomicals-js/issues/241#issuecomment-1897873597. It will only take some time to re calculate the reveal bitwork.
If not, It will make a few hours to several days, like https://github.com/atomicals/atomicals-js/issues/244#issuecomment-1900931576.  Since you don't use the latest version, you should enumerate both nonce and time .


Is there any html file?

Hi,
I just wonder that is there any html file which is more vivid I believe.
Thanks.

there would be if #10 gets merged


Changes references to docker/docker to moby/moby

Related issues (optional)
Fixes #2868

@mstanleyjones, this could use another review, I've addressed all your comments.


FileSystemUsage DiskRead and DiskWrite are always 0

I'm trying to get some information about disk usage where my application is storing and reading cache files. I've created simple method that gets FileSystemUsage for cache directory and reads DiskRead, DiskReadBytes, DiskWrite and DiskWriteBytes values at 1 second intervals. At the same time, the other process is creating a large number of memory mapped files. Sigar is always returning 0 for above values. Some other values are read, but I'm also not sure how correct these values are since Files is always the same value.
I've tried this on MacOS and Ubuntu. I couldn't find too much information online about these particular methods so I'm not sure if I missed to do something.

I have the same question in docker.
But it works well in host mode.


[design-system] Extend support of default colors

[x] I have followed (at least) the PR section of the contributing guide.

Coded the change that @oliviertassinari aimed for (24778#issuecomment)

Modified the documentation for Button color from ['inherit', 'primary', 'secondary'] to ['inherit', 'primary', 'secondary', 'default', 'success', 'error', 'info', 'warning']

Related to #24778

@oliviertassinari @siriwatknp could you review the commit?  Today is a weekend, so almost everyone is taking the time off.  Please review when you get time.

We can extend most of the other component to allow all the default colors of the theme

Bootstrap v4/5 supports Light/Dark/Link colors.  Nice if material UI can match as many colors as bootstrap to be feature color complete.  What is your opinion of supporting more colors?
https://getbootstrap.com/docs/4.6/components/buttons/#examples

What is your opinion of supporting more colors?

@sakura90 Off-topic to these changes. Here, I think that we should focus on the support the existing ones of the theme in components 1. , with a possible extension to 2. if it's not too complex/or make 1. easier. But to answer, this is up to @danilo-leal.

This is a step in the direction I think we should go into 👍. However, I think that we could push it much further:

We can extend most of the other component to allow all the default colors of the theme
We can extract the colors from the theme. See #24778 (comment) and this quick test (PaletteColorKeys contains neutral). It > > would simplify this part of the docs: https://next.material-ui.com/customization/palette/#adding-new-colors.

Have some private things to do, so I am going to be unavailable for atleast about a week.   Please feel free to continue the work.  The next change is going to address the above step.  I am going to continue working on the above step when I am back.

I think we should merge this since it is a bug fix for Button (so it does not block beta) and open another PR to work on the color design-system.

since it is a bug fix for Button

@siriwatknp I would personally not frame the current behavior as a bug as we have been pushing until now to restrict the number of colors to make it consistent with the other components and do not have the JSS class name grow significantly.
Happy to move with a smaller step, and merge. We know we want to support all the theme.palette colors in all the components. It will require a lot more effort but it's a step forward.

since it is a bug fix for Button

@siriwatknp I would personally not frame the current behavior as a bug as we have been pushing against it in v4 to restrict the number of colors to make it consistent with the other components and do not have the JSS class name grow significantly.
Happy to move with a smaller step, and merge. We know we want to support all the theme.palette colors in all the components. It will require a lot more effort but it's a step forward.

I consider it as typescript bug because
// @ts-expect-error
<Button color="success" />

but the color is green.
What if we merge this and I will open another PR to list all the components that need to be updated and other people can help?

I consider it as typescript bug because

Interesting, to the limit where we don't document it.

What if we merge this and I will open another PR to list all the components that need to be updated and other people can help?

Is enough #24778 to provide more guidance for the community?

Is #24778 enough to provide more guidance for the community?

Yep, I think it is enough.


BuiltinSound mismatch with 1.11.2

You forgot to add ShulkerBox sound in BuiltinSound, it's create a mismatch on next id because you're registering BuiltinSound with the Enums.ordinal() method.
See : http://pokechu22.github.io/Burger/1.11.html#sounds:block.shulker_box.close
Ps : Great library !

Should be fixed.


wip: update package.json

With the new importMap PR, I think this can be closed.
The user now has control over codegen outdir and the imports.