Model paths not found in ElasticBeanstalk

📝 Describe error
When deploying the transpiled code from ts to js and deploy it to AWS Elastic Beanstalk. It will show at the logs that the modules for the models are not found.
To Reproduce
Steps to reproduce the behavior:

Build you app.
Deploy it to your provider whether DigitalOcean or AWS.
See error

⛔ Error Message

This happens because of the file directory is "/var/app/current/". In controller decorator it only split the directory by "\" because on local machine the directory are using "\" not "/". Maybe a good fix is to check what is the format of the directory then split it by either "\" or "/".


Add "and applications for memoization" to cabal file synopsis

I search libraries by going to http://hackage.haskell.org/packages and grepping for keywords, and including "memoiz" would have helped me find this lib

Thanks!


If you have two copies of Chrome installed, and uproxy is incomplete in one, it will attempt to complete in the other

I have Chrome Canary, with an incomplete copy of uProxy (both parts are installed, but only part 2 is enabled).  If I click on uProxy in chrome://apps, it shows a "next" button to acquire part 1, which opens https://beta-dot-uproxysite.appspot.com/chrome-install.html in the default browser ... which is a different browser (Chrome stable).
On some machines, the default browser might not even be Chrome...

Any idea for a fix for this? (de-assigning @lucyhe - using assignments for when people are actively working on the issue)

Chrome added an app API to v42 that I think will solve this: https://developer.chrome.com/apps/browser haven't yet figured out how to hook everything up


Filesystem support (with flysystem)

Coverage increased (+1.8%) to 29.649% when pulling d8a682861253109634a85092fd73e96552fe5f44 on mducharme-flysystem into 6e9336ca0b347d68a3fbcf35f36bddd8fc5a2a68 on master.

Coverage increased (+1.8%) to 29.649% when pulling d8a682861253109634a85092fd73e96552fe5f44 on mducharme-flysystem into 6e9336ca0b347d68a3fbcf35f36bddd8fc5a2a68 on master.

Coverage increased (+1.8%) to 29.649% when pulling d8a682861253109634a85092fd73e96552fe5f44 on mducharme-flysystem into 6e9336ca0b347d68a3fbcf35f36bddd8fc5a2a68 on master.

Coverage increased (+1.8%) to 29.678% when pulling 063985e8912303cd1acb867b628748fb9f23fb04 on mducharme-flysystem into 6e9336ca0b347d68a3fbcf35f36bddd8fc5a2a68 on master.

Coverage increased (+1.8%) to 29.678% when pulling 063985e8912303cd1acb867b628748fb9f23fb04 on mducharme-flysystem into 6e9336ca0b347d68a3fbcf35f36bddd8fc5a2a68 on master.


Add @storybook/* to the ESM modules

This way we can modernize all storybook packages
Alternatively, optimize everything and allow users to specify include/exclude as optimizations

[ ] how big is the performance hit?

Would be nice with an option to include extra modules names for transpilation. Something like:
{
  name: '@storybook/addon-ie11',
  options: {
    includeModules: ['react-hook-form']
  },
}

As per @caspardue 's suggestion, I've given this a try, as I've been struggling with this last week.
Open for feedback on the PR:
https://github.com/storybookjs/addon-ie11/pull/10

@samwalshnz @shilman Hi! Is there any update on this issue? I have faced a similar problem in my project. Modifying the nodeModulesThatNeedToBeParsedBecauseTheyExposeES6 seems to solve it.
It would be nice if there was a possilbilty to expand this array without the need to modify the source in node_modules

I also had to add a few packages to nodeModulesThatNeedToBeParsedBecauseTheyExposeES6 in order to get IE 11 to behave in my environment: deep-object-diff, markdown-to-jsx, and react-router. It would be great if there was a way to pass additional package names into the addon options. I am running Storybook version 6.4.19.


Sorry, there was an error while fetching repositories

I recently (over a week ago) published a new bower package oxygen-language. The package is published, and it can be installed:
bower install --save oxygen-language

Before publishing I checked whether the name was available and there were other packages that were returned with the oxygen prefix. After publishing my package, when attempting to search for oxygen on the Bower website it returns:
Sorry, there was an error while fetching repositories
I think something about the package I published is breaking the search functionality.

Thanks for the issue. I'm also seeing this.. however the request is returning valid JSON (see below). Maybe something with rendering the data onto the page. This also happens for queries like "xyz"
or just "ox"...
[
   {
      "name":"oxygen-googlefont",
      "platform":"Bower",
      "description":null,
      "homepage":null,
      "repository_url":"https://github.com/google-fonts-bower/oxygen-bower",
      "normalized_licenses":[

      ],
      "rank":0,
      "latest_release_published_at":"2016-04-17T08:52:14.983Z",
      "latest_release_number":null,
      "language":"HTML",
      "status":null,
      "package_manager_url":null,
      "stars":0,
      "forks":0,
      "keywords":[

      ],
      "versions":[

      ]
   },
   {
      "name":"oxygenmono-googlefont",
      "platform":"Bower",
      "description":null,
      "homepage":null,
      "repository_url":"https://github.com/google-fonts-bower/oxygenmono-bower",
      "normalized_licenses":[

      ],
      "rank":0,
      "latest_release_published_at":"2016-04-17T08:52:15.036Z",
      "latest_release_number":null,
      "language":"HTML",
      "status":null,
      "package_manager_url":null,
      "stars":0,
      "forks":0,
      "keywords":[

      ],
      "versions":[

      ]
   },
   {
      "name":"oxygen-language",
      "platform":"Bower",
      "description":null,
      "homepage":null,
      "repository_url":null,
      "normalized_licenses":[

      ],
      "rank":0,
      "latest_release_published_at":"2016-08-29T06:03:23.526Z",
      "latest_release_number":null,
      "language":null,
      "status":null,
      "package_manager_url":null,
      "stars":0,
      "forks":0,
      "keywords":[

      ],
      "versions":[

      ]
   }
]

Why is the repository for oxygen-language set to null? Isn't the repository_url required? This might explain why the error is related to "fetching repositories"?

Yeah that seems wrong indeed. Didn't have the time to take a closer look earlier and I'm at work now, however I'll dig deeper as soon as I have some time.
cc: @andrew : Just mentioning you cause the returned null might also come from the query/db, I guess?

Thanks for the ping @BenMann, I didn't notice that Bower now allows non-github repositories, have fixed the null repository_url on ~300 bower projects including oxygen-language and handle it better for any new ones in future too.

@andrew Thanks for the awesomely quick fix ❤
Issue solved :-)

Thank you - great job :)


[Bug]: Partial export and import not working as expected.

Is there an existing issue for this?

[X] I have searched the existing issues

Description
In edit mode, after performing an import operation on an undeployed app, the widgets are not visible on the canvas, even though the entities are successfully exported and visible in the explorer.
Steps To Reproduce

In edit mode, without deploying the app:

Added a table widget and bound it with a user query to fetch user records (sample database users) on page 1.
Added a JS object to return a table selectedRow name for page 1.
Bound the JS object function with a text widget to display the name for page 1.
Added a new page, page 2.

Select page 1 and click the three dots to show the action menu, then click export. A JSON file is generated.

Selected page 2.

Click import and select the file generated in step 2.

Observed Result

The export happens successfully, and all entities are visible in the explorer on page 2.
However, the widgets are not visible on the canvas of page 2.

Expected Result

After importing the entities on page 2, the widgets should be visible on the canvas, matching the structure and configuration of the exported entities.

Note

When the app is deployed, the import works as expected, and the widgets are visible on the canvas.

Untitled application 1-before-deployment.json
Untitled application 1-post-deployment.json
Public Sample App
No response
Environment
Release
Issue video log
No response
Version
Release

@rahulbarwal This looks like a FE issue. Can you check this?

@jnikhila Can you please provide a video how of this?

When I follow the steps in description, i.e. export everything(without deployment) on page1 and import it in page 2.
I can see widgets on canvas.

@jnikhila Can you please check this again? we were unable to reproduce this.


Error: The extension is not allowed to be used at this point

The validation errors indicate that the given extensions can only be a part of Claim.Item or ClaimResponse directly, but the same implementation guide also lists them as part of ClaimResponse.item and ClaimResponse.item.extension in the resource profiles.

Below is our sample ClaimResponse.item extension:
ClaimResponse.item[0].extension:
[
   {
         "url": "http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension-administrationReferenceNumber",
         "valueString": "EXAMPLE_NUMBER"
    },
    {
        "url": "http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension-epsdtIndicator",
        "valueBoolean": false
    },
    {
        "url": "http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension-nursingHomeLevelOfCare",
        "valueCodeableConcept": {
             "coding": [
                 {
                     "code": "EXAMPLE_CODE",
                     "system": "https://codesystem.x12.org/005010/1337"
                 }
              ]
         }
     }
]

Below are the structure definitions showing them as part of ClaimResponse.item.extension:
http://hl7.org/fhir/us/davinci-pas/STU2/StructureDefinition-profile-claimresponse-base-definitions.html#diff_ClaimResponse.item.extension:administrationReferenceNumber
http://hl7.org/fhir/us/davinci-pas/STU2/StructureDefinition-profile-claim-definitions.html#diff_Claim.item.extension:epsdtIndicator
http://hl7.org/fhir/us/davinci-pas/STU2/StructureDefinition-profile-claim-definitions.html#diff_Claim.item.extension:nursingHomeLevelOfCare
I am wondering if you know this is a PAS Test Suite issue or IG issue, thank you!

I think this is an IG issue:

The PAS Claim Response Base profile indicates that the administrationReferenceNumber extension appears under item
The AdministrationReferenceNumber extension indicates that it appears at the ClaimResponse level (Element ID ClaimResponse)

Compare this to the Claim resource where

The PAS Claim Base profile indicates that the administrationReferenceNumber extension appears under item
The AdministrationReferenceNumber extension also indicates that it appears under item within Claim instances (Element ID Claim.item)

I think that each of the extensions you reference should look more like the RequestedService extension which indicates usage in context Element ID ClaimResponse.item.
It looks like the current build version is the same, so it doesn't appear to have been addressed yet. If you raise it with the PAS IG authors and get confirmation that these are spurious errors, we may be able to filter them out of the Inferno output even before the new version is published.

Hi Karl, thank you for taking a look! Your theory makes sense to me. I posted in the Zulips FHIR PAS group, and I will update here once I hear back from the IG authors.

Hi Karl, I heard back from Jean Duteau that anywhere the extensions are used will be the proper context. Based on the ClaimReponse spec, the extensions appear to be under ClaimResponse.item. Some of the extensions have incorrect contexts and will be updated in the next STU update.
Link to PAS Zulips post: https://chat.fhir.org/#narrow/stream/208874-Da-Vinci-PAS/topic/Extension.20under.20ClaimResponse.20or.20ClaimResponse.2Eitem

Karl, this plan sounds good to me! Thank you.


Design system documentation on system status indicators (i.e. pilot, alpha, beta)

Now that we have designs for pilot services, we should write documentation to add to the design system relating to these designs.

Duplicate issue.


rich glob pattern (e.g. support of !, (), etc)

Which project is this feature idea for?
Turborepo
Describe the feature you'd like to request
It seems it does not support widely-used styles of glob pattern, like ! and (), which can be used like the below snippet just for example.
{
  "inputs": ["(src,test)/**/*.(js,jsx,ts,tsx)", "!test/foo.js"]
}

Is there a special reason?
Thanks.
Describe the solution you'd like
Add support would be great.
Describe alternatives you've considered
None.

! should work already, are you having trouble with it? We have a passing test for it as well: https://github.com/vercel/turbo/blob/main/turborepo-tests/integration/tests/excluded_inputs.t

According to what we've specified in the documentation, this is supported today: https://turbo.build/repo/docs/reference/configuration#glob-specification-for-paths
If you have any troubles with it, please do open a bug report.


Android - Background State - Mic is not accessible

[x] I have read the Getting Started and Getting Started(with call invitation)
[x] I have already searched for the same problem

Environment

Technology
Version

Flutter version
3.22.2

Plugin version
^4.12.1

Android version
14

iOS version
17.4

macOS version

Xcode version
15.4

Google Chrome version
125.0.6422.142

Device information: Realme 11 Pro Plus - Android 14 (and other Android devices also)
Description
Expected behavior:
A normal voice calls with all modes - foreground, background, and kill mode.
Current behavior:
During voice calls, if the user (callee or caller) closes the app or locks the phone. The app is not able to access the microphone and the audio gets muted. As a result, there is no audio from one side.
Steps to reproduce
Install with UI kit with basic flutter and check with the Android device (app in the background or locked status).
Additional efforts
After reading multiple articles, we tried to use foreground services for Android. We used one package (https://pub.dev/packages/flutter_foreground_task) to keep the call mic status active. But all was in vain.
We are looking for help with the above package or any alternative way to enable the mic during the background/kill state.  What will be the service/function/method to be used with the above package to keep the mic accessible?

Please use foreground keep-alive.
it cannot be embedded in UIKit, so you need to embed it yourself in your app.

@yoer Thanks. Which service or method of zegocloud?

i mean, you can refer to plugins like flutter_background or flutter_foreground_task.

I have tried these plugins. These plugins require a specific task to run in the foreground. I am not sure, what will be the task or task to keep alive during background or kill state. Will we have to keep alive any specific zegocloud function?

@yoer
We are using only API for calling (https://www.zegocloud.com/docs/uikit/callkit-flutter/invitation-config/api-for-call-invitation). We have limited access to the calling screen with UI Kit.
Using the above plugins - We can put a specific code/action in the foreground mode. Here, I do not have any action or widget to put in the foreground.  Please suggest more about this.
It's a major bug for the voice call feature.

@yoer please give your suggestion on this in detail so we can implemented this

You need to implement app keeping alive by yourself, we do not provide a keeping alive solution

this example should be keep alive during background, You can refer to it

@yoer Using this, we are getting another issue with the Android devices. The app keeps active with the locked screen and not getting any calls.

do you mean, the app is now kept alive in the background.
but when the screen is locked, the call cannot be received?

Yes, I am aware of offline calls with background and killed state.
Issue
The user locks the phone during the app in the foreground stage. The app keeps opening and not able to receive notifications or calls. It may be due to the wake lock, etc.

Can you give me a log and the specific time of occurrence (call time)?
Regarding how to get the logs, you can refer to the How to get android device logs chapter of this document

@yoer Please share your email address. I will share zip files.

<EMAIL_ADDRESS>

@yoer We have tried with the updated document. It's crashing with Android 14.


Remove a few more implicit std::string <-> Filepath conversions

Part of https://github.com/newsboat/newsboat/issues/2326
Continuation of https://github.com/newsboat/newsboat/pull/2795

coverage: 61.023%. remained the same
when pulling 1b86c72a00c14e78194ded25c45bdbb0ef14bfe3 on dennisschagt:incremental-feature/2326-filepath
into 33c23569cdb987c2c6b20943855c47f905634710 on newsboat:feature/2326-filepath.

While reviewing it occurred to me that we should have a separate method on ConfigContainer that returns a Filepath. I added this to the top post of https://github.com/newsboat/newsboat/issues/2326.

While reviewing it occurred to me that we should have a separate method on ConfigContainer that returns a Filepath. I added this to the top post of https://github.com/newsboat/newsboat/issues/2326.

Good idea, however, I'm not getting to that for a while so I will deliver this as-is and update whenever I have time to apply the suggestion throughout the whole codebase.


add msgspec signature model

PR Checklist

[ ] Have you followed the guidelines in CONTRIBUTING.rst?
[ ] Have you got 100% test coverage on new code?
[ ] Have you updated the prose documentation?
[ ] Have you updated the reference documentation?

This PR is blocked - and will probably have to be closed due to lingering issues on the msgspec side that make it unsuitable for integration at this stage.


[TagInput] onInputValueChange invoked on onValueChange

🐛 Bug report
Need a way to invoke the onInputValueChange tagsInput hook not be invoked when the the onValueChange tagsInput hook is invoked
Ie. When we submit a tag by input keyboard enter instead of clicking the dropdown, both of the callbacks get called and we cannot handle the dropdown filter logic properly. onInputValueChange I just want to filter based of the input text so far and onValueChange I want to filter based of off what options there are left
Even the paid example has this bug with the filtering not working properly. If you select a number of options, then delete them all, and select another option again, all of the deleted options show up along with the new selected option
  const tagInput = useTagsInput({
    onInputValueChange: handleInputChange,
    onValueChange: handleValueChange,
    validate: (details) => initialItems.includes(details.inputValue)
    && !details.value.includes(details.inputValue),
  })

https://www.loom.com/share/f33c9412b21f43cbbefb0ab951ac8b21
💥 Steps to reproduce

Go to '...'
Click on '....'
Scroll down to '....'
See error

💻 Link to reproduction

CodeSandbox reproduction: https://your-codesandbox-link-goes-here.io
🧐 Expected behavior

I expect to be able to properly filter the dropdown items upon select as well as input type
🧭 Possible Solution

🌍 System information

Software
Version(s)

Zag Version
0.74.2 (Ark 4.1.2)

Browser
Chrome Version 129.0.6668.101 (Official Build) (arm64)

Operating System
MacOS Sonoma 14.6.1

📝 Additional information

I'd recommend moving the onInputValueChange  logic to the TagsInput.Input directly  as onChange
In the future, we'll consider exposing some actionMeta information to all events.

We'll update Ark Plus shortly


Fail to build for android NDK r16b

I use android NDK r16b to cross-compile in linux,follow the NOTES.ANDROID to build and got errors below when make:
/usr/local/andk/toolchains/arm-linux-androideabi-4.9/prebuilt/linux-x86_64/bin/../lib/gcc/arm-linux-androideabi/4.9.x/../../../../arm-linux-androideabi/bin/ld: error: cannot find -ldl
apps/ca.o:ca.c:function ca_main: error: undefined reference to 'stdin'
apps/ca.o:ca.c:function do_body.isra.3: error: undefined reference to 'stdin'
apps/dgst.o:dgst.c:function dgst_main: error: undefined reference to 'stdin'
apps/engine.o:engine.c:function engine_main: error: undefined reference to 'stdout'
apps/openssl.o:openssl.c:function main: error: undefined reference to 'stdin'
apps/openssl.o:openssl.c:function main: error: undefined reference to 'stdout'
apps/req.o:req.c:function req_main: error: undefined reference to 'stdout'
apps/s_time.o:s_time.c:function s_time_main: error: undefined reference to 'stdout'
./libcrypto.a(c_zlib.o):c_zlib.c:function zlib_stateful_expand_block: error: undefined reference to 'inflate'
./libcrypto.a(c_zlib.o):c_zlib.c:function zlib_stateful_compress_block: error: undefined reference to 'deflate'
./libcrypto.a(c_zlib.o):c_zlib.c:function zlib_stateful_finish: error: undefined reference to 'inflateEnd'
./libcrypto.a(c_zlib.o):c_zlib.c:function zlib_stateful_finish: error: undefined reference to 'deflateEnd'
./libcrypto.a(c_zlib.o):c_zlib.c:function zlib_stateful_init: error: undefined reference to 'inflateInit_'
./libcrypto.a(c_zlib.o):c_zlib.c:function zlib_stateful_init: error: undefined reference to 'deflateInit_'
./libcrypto.a(c_zlib.o):c_zlib.c:function bio_zlib_free: error: undefined reference to 'inflateEnd'
./libcrypto.a(c_zlib.o):c_zlib.c:function bio_zlib_free: error: undefined reference to 'deflateEnd'
./libcrypto.a(c_zlib.o):c_zlib.c:function bio_zlib_ctrl: error: undefined reference to 'deflate'
./libcrypto.a(c_zlib.o):c_zlib.c:function bio_zlib_ctrl: error: undefined reference to 'zError'
./libcrypto.a(c_zlib.o):c_zlib.c:function bio_zlib_write: error: undefined reference to 'deflate'
./libcrypto.a(c_zlib.o):c_zlib.c:function bio_zlib_write: error: undefined reference to 'zError'
./libcrypto.a(c_zlib.o):c_zlib.c:function bio_zlib_write: error: undefined reference to 'deflateInit_'
./libcrypto.a(c_zlib.o):c_zlib.c:function bio_zlib_read: error: undefined reference to 'inflate'
./libcrypto.a(c_zlib.o):c_zlib.c:function bio_zlib_read: error: undefined reference to 'zError'
./libcrypto.a(c_zlib.o):c_zlib.c:function bio_zlib_read: error: undefined reference to 'inflateInit_'
collect2: error: ld returned 1 exit status
make[1]: *** [apps/openssl] Error 1
make[1]: Leaving directory `/usr/local/anative/src/openssl-1.1.1'

One can find impossible flag combination for any given platform. And when one does, it doesn't actually mean that it's OpenSSL problem. Especially when one starts passing contradicting options. I mean what's up for example with -fPIC no-shared? Well, it's not actually so that they are problem here, -static is. And it is mentioned in NOTES.ANDROID. That one needs to modify Makefile, and that it takes an API version that is known to come with usable static libraries. In the essence it means that no guarantee can be left that -static actually works. In fact it applies to -static in general, it's viewed as debugging non-production option. To summarize, don't use -static. As for other options, give closer consideration...


#16 Feature: Possibility to pass many rst files at once

Added possibility to pass one or many rst files to 'rst-lint' command.
Moved tests out of the restructuredtext_lint (reduced build package size).

While it's great that you want to relocate the tests and reduce the build size, I prefer to bundle my tests into the repo to allow for testing packages upon download. Could we please move them back to their original positions?

Okay... a lot of feedback on this PR. There were a lot of undiscussed changes and inconsitencies with the repo. I am fine with discussing these changes but throwing them on a PR without talking to the maintainer is frustrating for both of us.

Removed all changes considered unrelated to the problem being fixed.

Thanks for the quick reply, fixes, and respecting my opinion =)
It looks like my comments regarding the test changes (not the renaming but the contents of the file) were lost though. I am going to re-post them =/

Just an observation:
There's a lot of conventions that are hard to notice since they aren't written down and tests/lints don't cover them. It would be extremely helpful if I started coding with the list of your required conventions.

Yea, sorry about that. Once this PR is landed, I will add in some linting/enforcement.

Regarding JSON being inefficient memory wise, I totally agree and we should consider moving to a streaming JSON output in the future.

Regarding JSON being inefficient memory wise, I totally agree and we should consider moving to a streaming JSON output in the future.

I couldn't find any library that would do it. Python json.JSONEncoder actually can output chunks of JSON but still it requires a dumped object to be in memory.
I find that the only possibility is to write JSON chunks on our own: '[', '{"level": 4, "source": "invalid_line_mismatch.rst", "full_message": "Title overline & underline mismatch.\n\n=====\nb\n====", "line": 1, "type": "SEVERE", "message": "Title overline & underline mismatch."}', ..., ']'

Regarding JSON being inefficient memory wise, I totally agree and we should consider moving to a streaming JSON output in the future.

I couldn't find any library that would do it. Python json.JSONEncoder actually can output chunks of JSON but still it requires a dumped object to be in memory.
I find that the only possibility is to write JSON chunks on our own: '[', '{"level": 4, "source": "invalid_line_mismatch.rst", "full_message": "Title overline & underline mismatch.\n\n=====\nb\n====", "line": 1, "type": "SEVERE", "message": "Title overline & underline mismatch."}', ..., ']'

JSONStreamWriter seems to fit our use case. However, we should not worry about that in this PR:
https://github.com/lysdexia/python-json-stream-writer

Everything looks good. Landing this PR shortly. Thanks for all your work and quick responses =)

There was some noise in the test runner due to not capturing stderr from check_output. I am patching this before landing.
$ nosetests --nocapture $*
.......usage: cli.py [-h] [--format FORMAT] [--encoding ENCODING]
              filepath [filepath ...]
cli.py: error: too few arguments
.
----------------------------------------------------------------------
Ran 8 tests in 0.136s

OK

This has been merged/released in 0.12.0. Thanks again for all your work =)

:+1:


the lack of expression After the word ","

when i run psrecon.ps1, it doesn`t work. it remind me that line 1010 of psrecon.ps1  lack of expression after word " , " charactor :35  why?

I believe this has been resolved in the latest push. Thanks for the heads-up!


urdf_parser_py: 1.2.1-1 in 'humble/distribution.yaml' [bloom]

Increasing version of package(s) in repository urdf_parser_py to 1.2.1-1:

upstream repository: https://github.com/ros/urdf_parser_py.git
release repository: https://github.com/ros2-gbp/urdfdom_py-release.git
distro file: humble/distribution.yaml
bloom version: 0.11.2
previous version for package: 1.2.0-2

urdfdom_py
* Switch to unittest.mock (#78 <https://github.com/ros/urdf_parser_py/issues/78>)
* Add BSD LICENSE file (#77 <https://github.com/ros/urdf_parser_py/issues/77>)
* Update Maintainers (#76 <https://github.com/ros/urdf_parser_py/issues/76>)
* Contributors: Audrow Nash, Scott K Logan, Silvio Traversaro

Holding for a Humble sync


Can't properly change 'primary' color in app.config.ts

Environment

Node version: 18.20.2
Yarn version: 1.22.22
OS: Windows 10

Version
^2.16.0
Reproduction
app.config.ts:
export default defineAppConfig({
  ui: {
    primary: 'primary', // I'm pushed to use copy named 'main' instead of my 'primary' color
    gray: 'cool',
  },
})

tailwind.config.ts
module.exports = {
   mode: 'jit',
...
    theme: {
      colors: {
        transparent: 'transparent',
        primary: {
          900: '#242B3D',
          800: '#2D3B57',
          700: '#334464',
          600: '#3B4E6F',
          DEFAULT: '#425577',
          500: '#425577',
          400: '#5D6D88',
          300: '#79879C',
          200: '#9DA8B9',
          100: '#C3CAD5',
          50: '#E7EAED',
        },
        main: {
          900: '#242B3D',
          800: '#2D3B57',
          700: '#334464',
          600: '#3B4E6F',
          DEFAULT: '#425577',
          500: '#425577',
          400: '#5D6D88',
          300: '#79879C',
          200: '#9DA8B9',
          100: '#C3CAD5',
          50: '#E7EAED',
        }
    }
...
}

Description
I needed to set my 'primary' color from Tailwind as Primary for nuxt/ui components.
The string must be exactly 'primary', because I am getting it from the backend as props for buttons, etc.
Additional context
No response
Logs
No response

Nuxt UI already creates a primary color with CSS variables so you can change it at runtime with your app.config.ts, this means you can't name your color primary in your tailwind.config.ts. You need to rename it to whatever you want, like mycolor and then use this color as:
export default defineAppConfig({
  ui: {
    primary: 'mycolor',
    gray: 'cool',
  },
})

You can read more about this here: https://ui.nuxt.com/getting-started/theming#colors


程序运行出错，无法调用GPU

2020-11-13 02:23:11.384991: I tensorflow/core/platform/profile_utils/cpu_utils.cc:94] CPU Frequency:<PHONE_NUMBER> Hz
2020-11-13 02:23:11.385217: I tensorflow/compiler/xla/service/service.cc:168] XLA service 0x30c3100 initialized for platform Host (this does not guarantee that XLA will be used). Devices:
2020-11-13 02:23:11.385248: I tensorflow/compiler/xla/service/service.cc:176]   StreamExecutor device (0): Host, Default Version
2020-11-13 02:23:11.387063: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcuda.so.1
2020-11-13 02:23:11.481223: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:983] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2020-11-13 02:23:11.481876: I tensorflow/compiler/xla/service/service.cc:168] XLA service 0x30c32c0 initialized for platform CUDA (this does not guarantee that XLA will be used). Devices:
2020-11-13 02:23:11.481917: I tensorflow/compiler/xla/service/service.cc:176]   StreamExecutor device (0): Tesla T4, Compute Capability 7.5
2020-11-13 02:23:11.482084: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:983] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2020-11-13 02:23:11.482636: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1639] Found device 0 with properties:
name: Tesla T4 major: 7 minor: 5 memoryClockRate(GHz): 1.59
pciBusID: 0000:00:04.0
2020-11-13 02:23:11.482720: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcudart.so.10.1
2020-11-13 02:23:11.484130: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcublas.so.10
2020-11-13 02:23:11.485643: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcufft.so.10
2020-11-13 02:23:11.485956: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcurand.so.10
2020-11-13 02:23:11.487339: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcusolver.so.10
2020-11-13 02:23:11.488005: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcusparse.so.10
2020-11-13 02:23:11.490719: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcudnn.so.7
2020-11-13 02:23:11.490831: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:983] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2020-11-13 02:23:11.491423: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:983] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2020-11-13 02:23:11.491921: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1767] Adding visible gpu devices: 0
2020-11-13 02:23:11.491982: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcudart.so.10.1
2020-11-13 02:23:11.494064: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1180] Device interconnect StreamExecutor with strength 1 edge matrix:
2020-11-13 02:23:11.494092: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1186]      0
2020-11-13 02:23:11.494103: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1199] 0:   N
2020-11-13 02:23:11.494232: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:983] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2020-11-13 02:23:11.494778: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:983] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2020-11-13 02:23:11.495338: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1325] Created TensorFlow device (/job:localhost/replica:0/task:0/device:GPU:0 with 14121 MB memory) -> physical GPU (device: 0, name: Tesla T4, pci bus id: 0000:00:04.0, compute capability: 7.5)
2020-11-13 02:23:11.802288: W tensorflow/core/common_runtime/colocation_graph.cc:983] Failed to place the graph without changing the devices of some resources. Some of the operations (that had to be colocated with resource generating operations) are not supported on the resources' devices. Current candidate devices are [
/job:localhost/replica:0/task:0/device:CPU:0].
See below for details of this colocation group:
Colocation Debug Info:
Colocation group had the following types and supported devices:
Root Member(assigned_device_name_index_=-1 requested_device_name_='/device:GPU:0' assigned_device_name_='' resource_device_name_='/device:GPU:0' supported_device_types_=[CPU] possible_devices_=[]
Identity: GPU CPU XLA_CPU XLA_GPU
VariableV2: CPU
Assign: CPU
Colocation members, user-requested devices, and framework assigned devices, if any:
get_batch/matching_filenames (VariableV2) /device:GPU:0
get_batch/matching_filenames/Assign (Assign) /device:GPU:0
get_batch/matching_filenames/read (Identity) /device:GPU:0
2020-11-13 02:23:11.802745: W tensorflow/core/common_runtime/colocation_graph.cc:983] Failed to place the graph without changing the devices of some resources. Some of the operations (that had to be colocated with resource generating operations) are not supported on the resources' devices. Current candidate devices are [
/job:localhost/replica:0/task:0/device:CPU:0].
See below for details of this colocation group:
Colocation Debug Info:
Colocation group had the following types and supported devices:
Root Member(assigned_device_name_index_=-1 requested_device_name_='/device:GPU:0' assigned_device_name_='' resource_device_name_='/device:GPU:0' supported_device_types_=[CPU] possible_devices_=[]
ReaderReadV2: CPU
TFRecordReaderV2: CPU
QueueSizeV2: GPU CPU XLA_CPU XLA_GPU
QueueCloseV2: GPU CPU XLA_CPU XLA_GPU
FIFOQueueV2: CPU XLA_CPU XLA_GPU
QueueEnqueueManyV2: CPU
Colocation members, user-requested devices, and framework assigned devices, if any:
get_batch/input_producer (FIFOQueueV2) /device:GPU:0
get_batch/input_producer/input_producer_EnqueueMany (QueueEnqueueManyV2) /device:GPU:0
get_batch/input_producer/input_producer_Close (QueueCloseV2) /device:GPU:0
get_batch/input_producer/input_producer_Close_1 (QueueCloseV2) /device:GPU:0
get_batch/input_producer/input_producer_Size (QueueSizeV2) /device:GPU:0
get_batch/TFRecordReaderV2 (TFRecordReaderV2) /device:GPU:0
get_batch/ReaderReadV2 (ReaderReadV2) /device:GPU:0
2020-11-13 02:23:11.803188: W tensorflow/core/common_runtime/colocation_graph.cc:983] Failed to place the graph without changing the devices of some resources. Some of the operations (that had to be colocated with resource generating operations) are not supported on the resources' devices. Current candidate devices are [
/job:localhost/replica:0/task:0/device:CPU:0].
See below for details of this colocation group:
Colocation Debug Info:
Colocation group had the following types and supported devices:
Root Member(assigned_device_name_index_=-1 requested_device_name_='/device:GPU:0' assigned_device_name_='' resource_device_name_='/device:GPU:0' supported_device_types_=[CPU] possible_devices_=[]
QueueDequeueManyV2: CPU
QueueCloseV2: GPU CPU XLA_CPU XLA_GPU
PaddingFIFOQueueV2: CPU
QueueSizeV2: GPU CPU XLA_CPU XLA_GPU
QueueEnqueueV2: GPU CPU XLA_CPU XLA_GPU
Colocation members, user-requested devices, and framework assigned devices, if any:
get_batch/batch/padding_fifo_queue (PaddingFIFOQueueV2) /device:GPU:0
get_batch/batch/padding_fifo_queue_enqueue (QueueEnqueueV2) /device:GPU:0
get_batch/batch/padding_fifo_queue_Close (QueueCloseV2) /device:GPU:0
get_batch/batch/padding_fifo_queue_Close_1 (QueueCloseV2) /device:GPU:0
get_batch/batch/padding_fifo_queue_Size (QueueSizeV2) /device:GPU:0
get_batch/batch (QueueDequeueManyV2) /device:GPU:0
WARNING:tensorflow:From multi_gpu_train_r3det.py:319: start_queue_runners (from tensorflow.python.training.queue_runner_impl) is deprecated and will be removed in a future version.
Instructions for updating:
To construct input pipelines, use the tf.data module.
WARNING:tensorflow:From multi_gpu_train_r3det.py:323: The name tf.summary.FileWriter is deprecated. Please use tf.compat.v1.summary.FileWriter instead.
restore model
2020-11-13 02:23:25.462669: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcudnn.so.7
2020-11-13 02:23:27.224448: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcublas.so.10

2020-11-13 02:24:39: global_step:19  current_step:20
per_cost_time:12.169s
cls_loss:0.127
reg_loss:0.000
refine_cls_loss:0.006
refine_reg_loss:0.000
refine_cls_loss_stage3:0.000
refine_reg_loss_stage3:0.000
total_losses:0.133

2020-11-13 02:25:21: global_step:39  current_step:40
per_cost_time:1.232s
cls_loss:0.163
reg_loss:0.000
refine_cls_loss:0.008
refine_reg_loss:0.000
refine_cls_loss_stage3:0.000
refine_reg_loss_stage3:0.000
total_losses:0.171

2020-11-13 02:25:50: global_step:59  current_step:60
per_cost_time:1.187s
cls_loss:0.148
reg_loss:0.000
refine_cls_loss:0.007
refine_reg_loss:0.000
refine_cls_loss_stage3:0.000
refine_reg_loss_stage3:0.000
total_losses:0.155

安装tensorflow-gpu

安装tensorflow-gpu

这样是有结果的：
import tensorflow as tf
with tf.device('/gpu:0'):
v1 = tf.constant([1.0, 2.0, 3.0], shape=[3], name='v1')
v2 = tf.constant([1.0, 2.0, 3.0], shape=[3], name='v2')
sumV12 = v1 + v2
with tf.Session(config=tf.ConfigProto(log_device_placement=True)) as sess:
    print(sess.run(sumV12))

[2. 4. 6.]

有结果不代表你调用了gpu，你得用nvidia-smi来观察。你就确认一下安装的是不是tensorflow-gpu


Add support of Text Mention notification event in @liveblocks/emails

Add a set of functions and utilities to help developers build email templates for the Text Mention notification event 👇🏻

Exposes prepareTextMentionNotificationEmailAsReact from @liveblocks/emails: it takes a webhook TextMentionNotificationEvent and prepare data to be used in an email and converts extracted document content fragment surrounding a mention as React.
Exposes prepareTextMentionNotificationEmailAsHtml from @liveblocks/emails: it takes a webhook TextMentionNotificationEvent and prepare data to be used in an email and converts extracted document content fragment surrounding a mention as html.

ℹ Naming is not set in stone, if you have better understandable suggestions I'd love to have your feedback and insights 🙏🏻
Two examples have added for now:

examples/nextjs-lexical-emails-resend → DX example when using prepareTextMentionNotificationEmailAsReact with Resend for Lexical text editor
examples/nextjs-tiptap-emails-resend → DX example when using prepareTextMentionNotificationEmailAsReact with Resend for Tiptap text editor

Checklist

[x] Add unit tests
[x] Add documentation
[x] Add guide
[x] Remove link example

Important informations
This branch has been created from email-templates-functions-and-utilities before it was merged into main. So the list of commit is quit very long. However the files changed are correct and show only the files changed corresponding to add the support of TextMentionNotificationEvent.
Thanks 🙏🏻

✅


ADO 14178377 - HIS: Update GitHub author in /db2oledbv and /esso folders

https://msazure.visualstudio.com/Intune/_workitems/edit/14178377

Docs Build status updates of commit 7011b97:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

his/db2oledbv/data-consumer-issues.md
:bulb:Suggestion
View
Details

his/db2oledbv/accessibility.md
:white_check_mark:Succeeded
View

his/db2oledbv/architecture.md
:white_check_mark:Succeeded
View

his/db2oledbv/code-page-conversions.md
:white_check_mark:Succeeded
View

his/db2oledbv/data-access-tool1.md
:white_check_mark:Succeeded
View

his/db2oledbv/data-link-tool.md
:white_check_mark:Succeeded
View

his/db2oledbv/data-provider-error-codes.md
:white_check_mark:Succeeded
View

his/db2oledbv/data-source-wizard.md
:white_check_mark:Succeeded
View

his/db2oledbv/data-type-mapping1.md
:white_check_mark:Succeeded
View

his/db2oledbv/deployment3.md
:white_check_mark:Succeeded
View

his/db2oledbv/getting-started.md
:white_check_mark:Succeeded
View

his/db2oledbv/installing-data-provider-version-6-0.md
:white_check_mark:Succeeded
View

his/db2oledbv/microsoft-ole-db-provider-for-db2.md
:white_check_mark:Succeeded
View

his/db2oledbv/operations2.md
:white_check_mark:Succeeded
View

his/db2oledbv/overview-of-data-provider.md
:white_check_mark:Succeeded
View

his/db2oledbv/performance1.md
:white_check_mark:Succeeded
View

his/db2oledbv/planning-and-architecture2.md
:white_check_mark:Succeeded
View

his/db2oledbv/planning.md
:white_check_mark:Succeeded
View

his/db2oledbv/protection1.md
:white_check_mark:Succeeded
View

his/db2oledbv/security-and-protection2.md
:white_check_mark:Succeeded
View

his/db2oledbv/security2.md
:white_check_mark:Succeeded
View

his/db2oledbv/tracing.md
:white_check_mark:Succeeded
View

his/db2oledbv/troubleshooting2.md
:white_check_mark:Succeeded
View

his/db2oledbv/what-s-new-in-version-6-0.md
:white_check_mark:Succeeded
View

his/esso/adapter-groups-and-group-adapters.md
:white_check_mark:Succeeded
View

his/esso/adapter-programming-administration.md
:white_check_mark:Succeeded
View

his/esso/adapter-programming-configuration.md
:white_check_mark:Succeeded
View

his/esso/administering-password-synchronization.md
:white_check_mark:Succeeded
View

his/esso/back-up-the-existing-security-data.md
:white_check_mark:Succeeded
View

his/esso/com-mapper-programmer-s-reference.md
:white_check_mark:Succeeded
View

his/esso/configuration-requirements-for-host-initiated-sso.md
:white_check_mark:Succeeded
View

his/esso/configuring-enterprise-single-sign-on1.md
:white_check_mark:Succeeded
View

his/esso/configuring-password-synchronization.md
:white_check_mark:Succeeded
View

his/esso/copy-the-migration-utility-to-the-master-secret-server.md
:white_check_mark:Succeeded
View

his/esso/creating-a-single-sign-on-application.md
:white_check_mark:Succeeded
View

his/esso/creating-affiliate-applications-for-host-initiated-sso.md
:white_check_mark:Succeeded
View

his/esso/deployment-overview1.md
:white_check_mark:Succeeded
View

his/esso/deployment-process.md
:white_check_mark:Succeeded
View

his/esso/enabling-and-disabling-host-initiated-sso.md
:white_check_mark:Succeeded
View

his/esso/enterprise-single-sign-on-basics.md
:white_check_mark:Succeeded
View

his/esso/enterprise-single-sign-on-flags.md
:white_check_mark:Succeeded
View

his/esso/enterprise-single-sign-on-programmer-s-reference.md
:white_check_mark:Succeeded
View

his/esso/enterprise-single-sign-on-tasks.md
:white_check_mark:Succeeded
View

his/esso/enterprise-single-sign-on-user-groups.md
:white_check_mark:Succeeded
View

his/esso/enterprise-single-sign-on1.md
:white_check_mark:Succeeded
View

his/esso/export-the-encryption-key.md
:white_check_mark:Succeeded
View

his/esso/high-availability-installation-options.md
:white_check_mark:Succeeded
View

his/esso/host-initiated-single-sign-on.md
:white_check_mark:Succeeded
View

his/esso/how-to-assign-an-application-to-an-adapter.md
:white_check_mark:Succeeded
View

his/esso/how-to-audit-enterprise-single-sign-on.md
:white_check_mark:Succeeded
View

This comment lists only the first 50 files in the pull request.

his/db2oledbv/data-consumer-issues.md

Line 297, Column 125: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/host-integration-server/core/data-links-db2-2' will be broken in isolated environments. Replace with a relative link.
Line 301, Column 28: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? If so, add &preserve-view=true to the URL: /sql/relational-databases/system-stored-procedures/sp-addarticle-transact-sql?view=sql-server-2017
Line 301, Column 183: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/sql/relational-databases/system-stored-procedures/sp-addarticle-transact-sql?view=sql-server-2017' will be broken in isolated environments. Replace with a relative link.
Line 301, Column 183: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? If so, add &preserve-view=true to the URL: https://docs.microsoft.com/sql/relational-databases/system-stored-procedures/sp-addarticle-transact-sql?view=sql-server-2017

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 832117d:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

his/db2oledbv/accessibility.md
:white_check_mark:Succeeded
View

his/db2oledbv/architecture.md
:white_check_mark:Succeeded
View

his/db2oledbv/code-page-conversions.md
:white_check_mark:Succeeded
View

his/db2oledbv/data-access-tool1.md
:white_check_mark:Succeeded
View

his/db2oledbv/data-consumer-issues.md
:white_check_mark:Succeeded
View

his/db2oledbv/data-link-tool.md
:white_check_mark:Succeeded
View

his/db2oledbv/data-provider-error-codes.md
:white_check_mark:Succeeded
View

his/db2oledbv/data-source-wizard.md
:white_check_mark:Succeeded
View

his/db2oledbv/data-type-mapping1.md
:white_check_mark:Succeeded
View

his/db2oledbv/deployment3.md
:white_check_mark:Succeeded
View

his/db2oledbv/getting-started.md
:white_check_mark:Succeeded
View

his/db2oledbv/installing-data-provider-version-6-0.md
:white_check_mark:Succeeded
View

his/db2oledbv/microsoft-ole-db-provider-for-db2.md
:white_check_mark:Succeeded
View

his/db2oledbv/operations2.md
:white_check_mark:Succeeded
View

his/db2oledbv/overview-of-data-provider.md
:white_check_mark:Succeeded
View

his/db2oledbv/performance1.md
:white_check_mark:Succeeded
View

his/db2oledbv/planning-and-architecture2.md
:white_check_mark:Succeeded
View

his/db2oledbv/planning.md
:white_check_mark:Succeeded
View

his/db2oledbv/protection1.md
:white_check_mark:Succeeded
View

his/db2oledbv/security-and-protection2.md
:white_check_mark:Succeeded
View

his/db2oledbv/security2.md
:white_check_mark:Succeeded
View

his/db2oledbv/tracing.md
:white_check_mark:Succeeded
View

his/db2oledbv/troubleshooting2.md
:white_check_mark:Succeeded
View

his/db2oledbv/what-s-new-in-version-6-0.md
:white_check_mark:Succeeded
View

his/esso/adapter-groups-and-group-adapters.md
:white_check_mark:Succeeded
View

his/esso/adapter-programming-administration.md
:white_check_mark:Succeeded
View

his/esso/adapter-programming-configuration.md
:white_check_mark:Succeeded
View

his/esso/administering-password-synchronization.md
:white_check_mark:Succeeded
View

his/esso/back-up-the-existing-security-data.md
:white_check_mark:Succeeded
View

his/esso/com-mapper-programmer-s-reference.md
:white_check_mark:Succeeded
View

his/esso/configuration-requirements-for-host-initiated-sso.md
:white_check_mark:Succeeded
View

his/esso/configuring-enterprise-single-sign-on1.md
:white_check_mark:Succeeded
View

his/esso/configuring-password-synchronization.md
:white_check_mark:Succeeded
View

his/esso/copy-the-migration-utility-to-the-master-secret-server.md
:white_check_mark:Succeeded
View

his/esso/creating-a-single-sign-on-application.md
:white_check_mark:Succeeded
View

his/esso/creating-affiliate-applications-for-host-initiated-sso.md
:white_check_mark:Succeeded
View

his/esso/deployment-overview1.md
:white_check_mark:Succeeded
View

his/esso/deployment-process.md
:white_check_mark:Succeeded
View

his/esso/enabling-and-disabling-host-initiated-sso.md
:white_check_mark:Succeeded
View

his/esso/enterprise-single-sign-on-basics.md
:white_check_mark:Succeeded
View

his/esso/enterprise-single-sign-on-flags.md
:white_check_mark:Succeeded
View

his/esso/enterprise-single-sign-on-programmer-s-reference.md
:white_check_mark:Succeeded
View

his/esso/enterprise-single-sign-on-tasks.md
:white_check_mark:Succeeded
View

his/esso/enterprise-single-sign-on-user-groups.md
:white_check_mark:Succeeded
View

his/esso/enterprise-single-sign-on1.md
:white_check_mark:Succeeded
View

his/esso/export-the-encryption-key.md
:white_check_mark:Succeeded
View

his/esso/high-availability-installation-options.md
:white_check_mark:Succeeded
View

his/esso/host-initiated-single-sign-on.md
:white_check_mark:Succeeded
View

his/esso/how-to-assign-an-application-to-an-adapter.md
:white_check_mark:Succeeded
View

his/esso/how-to-audit-enterprise-single-sign-on.md
:white_check_mark:Succeeded
View

This comment lists only the first 50 files in the pull request.
For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


feature: Support mirror "alias" in addition to name

Currently, the name you give a mirror in the Mirrorbits CLI is the name shown to users on the mirrorlist and mirrorstats pages.
This, however, might not be very user-friendly.
For instance, for ease of management with scripts, I name our mirrors with short "infrastructure" like names such as tor1 and sfo1. But then when a user views the mirrorlist for a given file, this is all they see under the "Mirror Name" field, i.e.

I'd like there to be a way to set an "Alias" or "Nice Name" (or something of that description) for each mirror, which would be what is shown to end-users on that page. This would allow us to preserve the simplicity of management (e.g. for mirror in tor1 sfo1 ...-type stuff) while providing nice names to end users (e.g. "Toronto, Canada", "San Francisco, USA East", etc.).

And I should have looked at the code first - it seems this is exactly what "Sponsor Name" does. Let this serve as a bit of documentation for what that does :D


Notifier: Discord

We should support webhooks to various services whenever a backup completes.
For our purposes, the most obvious webhook is to Discord. When the entire backup process completes, we want to send a webhook with a status report for the whole job.
For example, a report might look like this:
Postgres: [ok]
Redis: [ok]
Mongo: [failed]

Solved!

Solved!


[libgourou] Add new port and its dep

Describe the pull request
New port

What does your PR fix?

N/A

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

Linux, macOS

Does your PR follow the maintainer guide?

Yes
If you are still working on the PR, open it as a Draft: https://github.blog/2019-02-14-introducing-draft-pull-requests/

Please use vcpkg_install_copyright instead of file(INSTALL ...) for copyright file.
Other cl failures can be found in the log here: https://dev.azure.com/vcpkg/public/_build/results?buildId=81584&view=artifacts&pathAsName=false&type=publishedArtifacts

@Cheney-W That should do the trick.

I tried to test the usage on Linux machine with following CMakelist.txt:
cmake_minimum_required(VERSION 3.10)
project(test-project)
add_executable(main main.cpp)
find_package(libgourou CONFIG REQUIRED)
target_link_libraries(main PRIVATE gourou gourou_utils gourou_include gourou_compiler_flags)

and I got below errors:
CMake Error at offscale/scripts/buildsystems/vcpkg.cmake:582 (_add_executable):
  Target "main" links to target "pugixml::static" but the target was not
  found.  Perhaps a find_package() call is missing for an IMPORTED target, or
  an ALIAS target is missing?
Call Stack (most recent call first):
  CMakeLists.txt:3 (add_executable)

CMake Error at offscale/scripts/buildsystems/vcpkg.cmake:582 (_add_executable):
  Target "main" links to target "pugixml::pugixml" but the target was not
  found.  Perhaps a find_package() call is missing for an IMPORTED target, or
  an ALIAS target is missing?
Call Stack (most recent call first):
  CMakeLists.txt:3 (add_executable)

CMake Error at offscale/scripts/buildsystems/vcpkg.cmake:582 (_add_executable):
  Target "main" links to target "libzip::zip" but the target was not found.
  Perhaps a find_package() call is missing for an IMPORTED target, or an
  ALIAS target is missing?
Call Stack (most recent call first):
  CMakeLists.txt:3 (add_executable)

CMake Error at offscale/scripts/buildsystems/vcpkg.cmake:582 (_add_executable):
  Target "main" links to target "OpenSSL::SSL" but the target was not found.
  Perhaps a find_package() call is missing for an IMPORTED target, or an
  ALIAS target is missing?
Call Stack (most recent call first):
  CMakeLists.txt:3 (add_executable)

CMake Error at offscale/scripts/buildsystems/vcpkg.cmake:582 (_add_executable):
  Target "main" links to target "CURL::libcurl" but the target was not found.
  Perhaps a find_package() call is missing for an IMPORTED target, or an
  ALIAS target is missing?
Call Stack (most recent call first):
  CMakeLists.txt:3 (add_executable)

For fixing above errors, I think you should add below contents into the https://github.com/SamuelMarks/libgourou/blob/cmake/cmake/Config.cmake.in file:
include(CMakeFindDependencyMacro)

find_dependency(CURL)
find_dependency(libzip)
find_dependency(OpenSSL)
find_dependency(pugixml)

@Cheney-W Darn, it's been open for 2 years and no activity for 3 months (whence someone had built solution on their fork): https://gitlab.kitware.com/cmake/cmake/-/issues/20511
I'll make the changes you suggested & thanks

@Cheney-W I thought I did a week ago? - Or did I miss something?

I added some comments in vcpkg.json file before, about the "version" and "supports", could you please take a look?

@SamuelMarks Are you still working on this PR?

https://github.com/microsoft/vcpkg/pull/28037/files#r1034336129
https://github.com/microsoft/vcpkg/pull/28037/files#r1034336172
https://github.com/microsoft/vcpkg/pull/28037/files#r1034349135
https://github.com/microsoft/vcpkg/pull/28037/files#r1034336205
https://github.com/microsoft/vcpkg/pull/28037/files#r1034336223
https://github.com/microsoft/vcpkg/pull/28037/files#r1034349662
Could you please apply above suggestions? Thank you!

@SamuelMarks Are you still working on this PR?

OK, please apply my suggestions by the way when you add new changes.

Otherwise it's basically ready at is

Oops, sorry this slipped through review cracks for so long; I'm guessing because it is still marked as 'draft'. Can you confirm that you still want this change as is by marking 'ready for review'?
Thanks!


add date format hint text

a single date field text box confuses users unless they are told the required date format

:+1:


Bundled binaries in repository

Currently the repository bundles (at least) two binaries for the compiled eBPF code: ./support/ebpf/tracer.ebpf.amd64 and ./support/ebpf/tracer.ebpf.arm64
This makes it a bit easier to reuse the profiler as a library (since the client application doesn't need to rebuild the eBPF binaries itself), but it makes it much harder to change the unwinder code: we have to change the code, then remember to build on two different machines (for each architecture) and commit. It also isn't reproducible: who knows what flags compiler version, etc. the blobs in the repo were built with?
I'm opening this issue to discuss whether this design should be changed.

Related: https://github.com/open-telemetry/opentelemetry-ebpf-profiler/issues/44

It also isn't reproducible: who knows what flags compiler version, etc. the blobs in the repo were built with?

The ones specified in the Makefile. We have validated that the build is reproducible as long as the same version of clang is being used, including when cross compiling.

then remember to build on two different machines (for each architecture)

You can cross-compile it:
cd support/ebpf
make TARGET_ARCH=amd64
make TARGET_ARCH=arm64

That's what we do. But yeah, we'll at the very least have to set up a builder image soon to ensure that everyone ends up with the same binaries + we can verify it in CI.

We have validated that the build is reproducible as long as the same version of clang is being used, including when cross compiling.

Right, but nobody knows if what exists in the repo was actually built using that version of clang and those flags (or even what code it is built with).
Unless there is a step in CI that checks that the code in the repo compiles to something bit-for-bit identical to the checked-in version. If there is not already, I'd suggest adding this.
OK, I think this issue can be considered a duplicate of #44, so I'll close it.


Does support static next.js apps?

Hi!
Does this package support static Next.js Apps(Static HTML Export)?

Hello, this protection needs to use code runned in /api to verify password on serverside. So, no.


Could you provide the grid search result?

I wanna reproduce your experiment results. Could you provide the parameter searching space and the best combination?
I mean:
learning rate searching space: [0.010, 0.003, 0.01 ......]
dropout searching space: [0.1, 0.2, 0.3 ......]
Thanks!

Typical spaces can be used. Not so sensitive, though.
e.g.
"learning_rate": [1e-3, 1e-4],
"unit": [256, 512],
"dropout": [0.1, 0.5].


Convert directory command doesn't work, throws no errors.

I tried running this against a directory containing MV2 source files:
python3 emc.py dir/path/
Nothing in the directory changes. Here's the extension I'm trying to convert:
https://github.com/GoogleChrome/chrome-extensions-samples/tree/main/_archive/mv2/howto/sandbox

I just ran it successfully using the steps that you provided. The new extension is converted and resides in sandbox_delete. What's different about your setup?
% python3 emc.py /tmp/chrome-extensions-samples/_archive/mv2/howto/sandbox
/tmp/chrome-extensions-samples/_archive/mv2/howto/sandbox
Changing manifest_version to 3
Changed to chrome.action in manifest.json
Changed to chrome.action in .js files
Updating web_accessible_resources
Converted extension into: /tmp/chrome-extensions-samples/_archive/mv2/howto/sandbox_delete

I wasn't looking for it in sandbox/_delete and failed to notice that it told me to look there. Sorry about that.


bug: Types not working with typescript 4.8

Is there an existing issue for this?

[X] I have searched the existing issues

Description of the bug
With the new changes to the {} type, sapphire is throwing errors when compiling.
Steps To Reproduce

Update to typescript 4.8
Run tsc

Expected behavior
Not throwing an error.
Screenshots

Additional context
No response

The SchemaOf issue is easily fixable by adding extends NonNullable in SchemaOf but I tried to fix other type issues related to {} and I wasn't able to do it. The issue is coming from https://github.com/sapphiredev/shapeshift/blob/main/src/lib/util-types.ts#L10
before 4.8, it was {} & object but after 4.8, it's now object. The only solution which worked for me was by removing extends NonNullableObject from https://github.com/sapphiredev/shapeshift/blob/main/src/validators/ObjectValidator.ts#L15 but that's not a solution as it'll now accept any values

The SchemaOf issue is easily fixable by adding extends NonNullable in SchemaOf but I tried to fix other type issues related to {} and I wasn't able to do it. The issue is coming from https://github.com/sapphiredev/shapeshift/blob/main/src/lib/util-types.ts#L10 before 4.8, it was {} & object but after 4.8, it's now object. The only solution that worked for me was removing extends NonNullableObject from https://github.com/sapphiredev/shapeshift/blob/main/src/validators/ObjectValidator.ts#L15 but that's not a solution as it'll now accept any values.
For now you can add skipLibCheck in your tsconfig or use typescript < 4.8

I have been using skipLibCheck because of this, but its not the best thing to do.
About object, maybe a solution to this would be using Record<PropertyKey, unknown> which can be used to represent any object but might need some changes in other parts of the code.


Timecourse data structure

Hi,
I'm not sure how to save my .tif files given that I have multiple channels, positions, and a timecourse (all in single-channel individual .tiffiles). Even when I only work with the files from a single position, the 'Create data structure from microscopy files' does not allow for a timecourse. It either tries to force multiple sites or gives an error when I set up number of timepoints correctly. Can the ADCC work correctly with a timecourse in multiple channels?

Hi @ewabb, I'm happy to hear you want to try out Cell-ACDC!
You can definitely work with timecourse data with multiple channels, this is how I use Cell-ACDC on a daily basis.
However, it needs to be structured in a specific way. Essentially you need to have one .tif file per position per channel. So let's suppose you have three channels, 10 positions and 150 frames per channel. In this example, you are going to need 30 .tif files, 3 channels per position. The single .tif file will be a single-channel multi-page .tif file with 150 frames, so essentially a series of 150 2D  images (or 3D if you have z-stacks). Each file should have the same basename (typically the name of the microscopy file) plus a text that allows you to identify which file is which channel.
Achieving this manually is tedious, which is why we have the Create data structure from microscopy files module.
If I understood correctly you have multiple .tif files where a single file contains a single-channel time course data, right? Do you have one such file for each position or does the file also contain the positions? Because if you already have one .tif file per position per channel it sounds like you already have the correct structure and you "only" need to put it into Position folders. I can write a small utility for that.
However, the fastest way would be that I test with your data, if possible. You can share it with me on Google Drive to my email<EMAIL_ADDRESS>or you can use any other cloud service you want.
Let me know what you prefer, thanks!
Cheers,
Francesco

Hi, @ewabb I received your data and I will test it soon! I will keep you updated!
PS: Sorry for the late replies but you seem to be in a different time zone (I'm in Germany).
Cheers,
Francesco

Hi @ewabb, so I looked at your data and I have a couple of questions:

Are these the files produced by the microscope or are the files you processed with MATLAB?
If I understood correctly the file 3_4_2_Hoechst_1.tif is the first time point of a specific position of the Hoechst channel (do the numbers 3_4_2 have a meaning? I guess they identify a position?), while the file 3_4_2_reporter_1.tif is the first time point of the same position but different channel? So then,  3_8_1_Hoechst_1.tif is the first time point of the channel  Hoechst but different position?

Because I could easily make a utility to correctly structure the data given what you sent me, but I would prefer to start from the raw microscopy files, if possible. How big are they?
One of the advantages of using the raw microscopy files directly as input for the Create data structure from microscopy files module is that this module can also read the metadata of the image, like the pixel size, the number of frames, the frame interval etc. (if they are available in the microscopy file of course).
So far, we never had to work with microscopy files separated by time-point, so we definitely need to implement something for your data, but I can do it pretty easily.
Please, let me know what you think, and if you can share a sample of microscopy files. Have a good weekend!
Cheers,
Francesco

Hi Francesco,
sorry for not replying here earlier. Thank you so much for your prompt reply and willingness to help!
Yes, you are correct, I have multiple .tif files, separated by position and channel. In your example, that is 10 positions x 150 frames x 3 channels = 4500 images. The microscope produces images separated in different folders by the time point, then I rename and reorganize them using a custom script in MATLAB (so I can change the naming if that is the issue). I am sharing sample files from 3 sites (the first three numbers are row, column and site on the plate), 2 channels (Hoechst/reporter), 5 time points (last number). Your understanding of the naming is correct.
I'm going to share 3 time point folders produced by the microscope with you now for comparison. Either way works with me.
Best,
Ewa

Also, in some experiments the run will be paused and restarted, which results in multiple folders, each with its Timepoint folders that need to be stitched together

Hi Ewa, perfect I got it. I will add this type of data structure to the Cell-ACDC data structure module. I will keep you updated!
Cheers,
Francesco

Hi Ewa,
In the end, I decided to go for the structure of the files you created with MATLAB because I think it is a good pattern that can be useful also to other users dealing with files separated by time-point.
I released v1.2.4rc48 with the new feature. To use it, run the module 0. Create data structure from microscopy/image file(s)... and then, instead of Bio-Formats, choose "Re-structure". From there follow the instructions in the pop-up windows, I hope they are clear enough.
To install the latest version, please, activate the acdc environment and then install with the command pip install --upgrade cellacdc.
Let me know if it works! Thanks.
Cheers,
Francesco

Thanks Francesco, I'll let you know how it went!

It works, thanks! If I may have a request for further update, would it be possible to add additional channels to a time course that only have one time point? If you have an additional channel that has a stable expression and only want to measure it once or do a staining at the end of the experiment and correlate the data with live traces in the same cells, that would be very powerful. Thanks!

Ok great! I will close this issue then and open a new one with the new request ok? It's easier for me to keep track of things this way. I created the new issue #182, see you there!
Cheers,
Francesco


init() got an unexpected keyword argument 'cert_file'

Using python 2.7, crate==0.16.2, and urllib3==1.16, I get an error when trying to retrieve a blob.
The table was created using:
create blob table testblobs clustered into 2 shards with (number_of_replicas=1)

The file was successfully added using:
from crate import client
ctx = client.connect(['box1.local:4200', 'box1.local:4200', 'box3.local:4200'])
blobs = ctx.get_blob_container('testblobs')

with open('/path/sample.tif') as f:
    blobs.put(f, digest='<sha1hash>')

When trying to retrieve:
from crate import client
ctx = client.connect(['box1.local:4200', 'box1.local:4200', 'box3.local:4200'])
blobs = ctx.get_blob_container('testblobs')

res = blobs.get('<sha1hash>')

  (...)
  File "/root/test/lib/python2.7/site-packages/crate/client/blob.py", line 80, in get
    return self.conn.client.blob_get(self.container_name, digest)
  File "/root/test/lib/python2.7/site-packages/crate/client/http.py", line 347, in blob_get
    response = self._request('GET', _blob_path(table, digest), stream=True)
  File "/root/test/lib/python2.7/site-packages/crate/client/http.py", line 406, in _request
    raise ProgrammingError(_ex_to_message(e))
crate.client.exceptions.ProgrammingError: __init__() got an unexpected keyword argument 'cert_file'

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/36819687-__init__-got-an-unexpected-keyword-argument-cert_file?utm_campaign=plugin&utm_content=tracker%2F505660&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F505660&utm_medium=issues&utm_source=github).

duplicate of #179


Update the README.md to demo browser-like experience setup.

For example:

option shift t to restore the last closed buffer.
option w to close the current buffer and move to "the next"(you can customize this, see the API in README.md) buffer.

Buffer restoring has been removed.


ND4j empty arrays in transforms

ND4J at this moment doesn't check legacy transform ops arguments for being empty. Affected op groups: all transforms, scalars, pairwise, broadcasts. In case of empty operands these ops become no-op effectively,

Implemented


Update quickstart-chatbot.mdx

just fix a typo which i found during learning about use of copilot

Thanks!


:context=>:foo does not set specified context in nested controller?

I'm trying to override context in a nested controller
I have similar controllers nested under different namespaces but want to manage only one kind of permission for all.
I have a roles with permissions like this.
has_permission_on :foo, :to=>:manage
And a controller that might look like this:
class Bars::FooController
#this does not work,  it denies permissions for context => :bars_foo
filter_access_to :new, :create, :require =>:manage, :context=>:foo
#but this DOES work!?
filter_access_to :index, :require =>:read, :context=>:foo
#Explicitly overriding decl_auth_context works however...
class << self
def decl_auth_context
:foo
end
end
[...]
end
Something strange is going on. It works for :read, but not for :new (falling back to default). I can't see the logic behind it...

This sounds strange, indeed.  There shouldn't be any difference between the new/create and the index case.  Are you sure that there isn't something else wrong?  Are those controllers inheriting filter_access_to statements already, for example?


Update doc API

API (PUT - is it a good choice?) for updating a doc.
Not tested. Please either test or explain me which part of the UI to use for testing.

Fixes #8.

API (PUT - is it a good choice?) for updating a doc.
Not tested. Please either test or explain me which part of the UI to use for testing.

Yes. PUT is fine
you can just use the Postman or curl to test it.
PUT http://localhost:8880/api/v1/docs/{pk}
If you don't want to bother with the token, just comment out the current_user: User = Depends(get_current_user) or take the token from the browser(console)

you can just use the Postman or curl to test it.

I am not sure how to test embeddings: Should I write a specialized testing code that check embeddings to be created/deleted as needed? Or is there an easier variant?

you can just use the Postman or curl to test it.

I am not sure how to test embeddings: Should I write a specialized testing code that check embeddings to be created/deleted as needed? Or is there an easier variant?

@vporton do you need to test embedding? You just need to be able to search for the new content through the /docs/search endpoint. That is the real test

I fixed some, but not all, bugs.
Please help:
The browser outputs
GET http://<IP_ADDRESS>:8880/api/v1/admin/user/docs
405 Method Not Allowed

I don't understand how this can happen: The string user/docs appears in the sources only twice, the first time is handling a POST request, and the second time is:
	{
		"item_id": 48123,
		"title": "Add doc",
		"article_type": "api",
		"application": "chat",
		"text": "To add a new documentation a given application you can use the following request. \n Params: - title \n - text \n- app_key \n Example: `curl -L  -X POST  -H \"Accept: application/json\"  -H \"Authorization: Bearer <YOUR-TOKEN>\"  http://localhost:8880/api/v1/admin/user/docs  -d '{\"title\":\"my doc title\", \"text\":\"my doc text\", \"app_key\":\"application key\"}'` \n\n Request render: ` request_render:{'text':{'field_type': 'textarea'}}` \n\n #action"
	},

It is a post request.
From where can a GET request appear? Please help me to understand which piece of the source produces this GET.

@apssouza22 Note that this query is triggered by the prompt:

Search app docs for the word "text"

@apssouza22 Note that this query is triggered by the prompt:

Search app docs for the word "text"

We don't have a doc for the doc search. Probably the engine is guessing that search docs uses get. So the get could be generated by the chatGPT.
It would be easier just use Postman.
Another option  is just prompt in the UI "your new text" and then look at the network tab of the browser. The first request is to retrieve the doc based on the input. Just check if it is finding your edited doc

There is basic issues.
File "/Users/alexsandro.souza/projects/my/chatflow/server/src/api/docs.py", line 65, in update_doc
    return await update_app_doc(request, pk=request.pk)
AttributeError: 'AddDocRequest' object has no attribute 'pk'

To test. call http://<IP_ADDRESS>:8880/api/v1/admin/applications/chat/docs  get the PK for the doc you want to edit
calll http://<IP_ADDRESS>:8880/api/v1/docs/{pk} with the following body
{
    "text": "test delete this content",
    "app_key": "chat",
    "title": "test- delete me"
}

Then call http://localhost:8880/api/v1/docs/search to search for the new text
{
    "text": "delete this content",
    "app_key":"chat"
}

Find attached the postman collection to all the endpoints
Chat-commander.postman_collection.json

@apssouza22 My advice to you:
Add the following collection-level pre-request script in Postman:
pm.sendRequest({
    url: "http://localhost:8880/api/v1/admin/user/login",
    method: 'POST',
    header: {
        'content-type': 'application/json'
    },
    body: {
        mode: 'raw',
        raw: JSON.stringify({email<EMAIL_ADDRESS>password: "123"})
    }
}, (err, res) => pm.collectionVariables.set("token", res.json().access_token));

Currently the output of /api/v1/admin/applications/chat/docs looks like this:
{
    "total": 11,
    "data": [
        {
            "pk": "01HCQMGBSGA8SE52EWNTNTDB5S",
            "item_id": 30039,
            "item_metadata": {
                "pk": "01HCQMGBSG41NATRTPZ2TPRAV2",

Note that item and its item_metadata have two different pk values. It is probably my error.
Before fixing it, I want to make sure that @apssouza22 agrees with me which of the two pks to leave intact and which to delete. I'd vote for the outer key to be left intact and the inner one to be deleted. @apssouza22 ?

@vporton I agree that the item_metadata pk can be deleted

@vporton I agree that the item_metadata pk can be deleted

This double pk seems to be a feature of redis-om-python, that possibly cannot be turned off.

calll http://<IP_ADDRESS>:8880/api/v1/docs/{pk} with the following body

There is no /docs/{pk} POST/PUT endpoint.

@vporton I agree that the item_metadata pk can be deleted

This double pk seems to be a feature of redis-om-python, that possibly cannot be turned off.

I meant that u can delete the whole object and create it again

calll http://<IP_ADDRESS>:8880/api/v1/docs/{pk} with the following body

There is no /docs/{pk} POST/PUT endpoint.

That's your new endpoint, right?

That's your new endpoint, right?

Oh, sorry, right. Apparently I was on a wrong Git branch :-(

After every query to /docs/{pk}, the number of results returned by /admin/applications/chat/docs decreases by one. Items are deleted instead of updated :-~
Do you @apssouza22 have any idea why this may happen?

After every query to /docs/{pk}, the number of results returned by /admin/applications/chat/docs decreases by one. Items are deleted instead of updated :-~
Do you @apssouza22 have any idea why this may happen?

@vporton I have simplified the doc structure. Please refer to the latest version. It should be much simpler to edit the docs now

Please refer to the latest version.

git pull downloads no updates.

Please refer to the latest version.

git pull downloads no updates.

Make sure u are getting from the right repository. You are probably pulling from your own repo.
You need to add a new repository. Run the following
git remote add apssouza myrepo
Then git pull apssouza

@vporton I have simplified the doc structure. Please refer to the latest version. It should be much simpler to edit the docs now

It still (I don't understand why) deletes a doc instead of updating it on the PUT request.

Sorry, I screwed up the update-doc branch, trying to resolve the conflicts.

Sorry, I screwed up the update-doc branch, trying to resolve the conflicts.

 How come that you deleted ItemMetadata which is used in _save_app_doc, etc.?
We need to communicate in words before further trying to edit it together.

I think, we should revert to my commit ed44edebef9d94300d1b2edace440cc33871a568 and start merging anew.
I apologize for my mistakes, I don't have much experience in merging teamwork.

@apssouza22 I can't work on this until coordinating with you: revert to my commit ed44edebef9d94300d1b2edace440cc33871a568? or if not, then what will we do instead?

Just delete and create another one as part of update. It should be very easy since we have those operations already

delete and create another one

Delete and create another what? (branch?)
Maybe, better to use git revert?

Docs update. The thing u were trying to do here
On Mon 16 Oct 2023, 19:13 mathematician, @.***> wrote:

delete and create another one
Delete and create another what? (branch?)
Maybe, better to use git revert?
—
Reply to this email directly, view it on GitHub
https://github.com/apssouza22/chatflow/pull/48#issuecomment-1765037596,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAC3RWO73Y5T5PFAVQUVWWTX7V2NJAVCNFSM6AAAAAA52UT4AKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONRVGAZTONJZGY
.
You are receiving this because you were mentioned.Message ID:
@.***>

Docs update. The thing u were trying to do here

Sorry, I am sometimes a little dislexic. I don't understand what you refer to by "docs update" and "the thing".
Is it OK for you if I do git revert?

 Before we merge it.
It lives in your repository
I am talking about the functionality you were trying to implement - Update
docs
On Mon 16 Oct 2023, 19:25 mathematician, @.***> wrote:

Docs update. The thing u were trying to do here
Sorry, I am sometimes a little dislexic. I don't understand what you refer
to by "docs update" and "the thing".
Is it OK for you if I do git revert?
—
Reply to this email directly, view it on GitHub
https://github.com/apssouza22/chatflow/pull/48#issuecomment-1765053900,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAC3RWJ3KGEQI5TCCXZWW4DX7V3X5AVCNFSM6AAAAAA52UT4AKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONRVGA2TGOJQGA
.
You are receiving this because you were mentioned.Message ID:
@.***>

OK, it seems I now understand what happened: I did some changes and after this you applied a patch (3fe1b6a4a83b46cd504970ce0d0d4f95832aede9.) that did not took into account my changes. The result was screwed up code that confused me, and I even more incorrectly did merging after this.
So, to put this in order, I did on my copy of repository git reset --hard to remove main branch changes and reverted the above mentioned patch.
After this I removed @r.post("/docs/metadata" and @app.on_event("startup"), because, it is apparently a right intention to removed them.
Now I am starting testing anew. Please, don't screw it again like that patch.

That is real life flow. We changed the same files and it will cause conflict. U need to pull the latest version, fix the conflicts and push your version. There was no patch. There were new commits to the repo, as it has to be.
If u are not able to fix the conflicts, I suggest starting with a new Branch

Oh, I did something wrong and my git reset --hard deleted all my changes :-( I should run reset --hard as a last resort. git merge in some reason not worked, so I did it.
Not that bad, I will re-create the branch from main and write @put code again.

@vporton I will test this and if it works fine I will merge it


Added page-item and page-link classes for Bootstrap 4.

Bootstrap 4 uses different classes to build the pagination, see http://v4-alpha.getbootstrap.com/components/pagination/#default-pagination
PS: your editor should be configured to remove trailing white space

I'm in research about support for Bootstrap 4.


Should Openshift Sandbox be the default tab instead of ROKS?

Most definitely, just added it to #52 👍


Log level in test with @DynamicPropertySource

When you try to set up property of logging.level.org.zalando.logbook in tests trough @DynamicPropertySource logbook will not work. Only manual setting in application.yaml is handling logbook properly.
@DynamicPropertySource
static void props(DynamicPropertyRegistry reg) {
reg.add("logging.level.org.zalando.logbook", ()-> "TRACE");
}

The logging.level.* property doesn't belong to logbook but Spring directly.
If you want to change log levels at runtime, they offer eg a management bean/endpoint, iirc.


Gatsby standard codacy test

This PR has some code lint problems. It was created to test Codacy.

Apparently it still doesn't work. Closing now and I will leave testing to another repo.


Config should be passed as an argument as opposed to a global variable

At the moment the config is a global variable WebVRConfig. It would be nicer if you could just pass it in as an argument to the manager. I think this also applies to webvr-polyfill.
var manager = new WebVRManager(renderer, effect, options);

The reason we currently use WebVRConfig is that the polyfill is completely
invisible to the developer.
All of the WebVRConfig options pertaining to the boilerplate could be
converted to an options array, but then there would be two different ways
of configuring.
On Wed, Jan 6, 2016 at 3:15 AM Ehsan Ziya<EMAIL_ADDRESS>wrote:

At the moment the config is a global variable WebVRConfig. It would be
nicer if you could just pass it in as an argument to the manager. I think
this also applies to webvr-polyfill.
var manager = new WebVRManager(renderer, effect, options);
—
Reply to this email directly or view it on GitHub
https://github.com/borismus/webvr-boilerplate/issues/100.

The polyfill is invisible to the developer and so the developer manages the visible and unusual step of defining a global configuration.


Create a Modal component

Description
A Modal component would help us tackle special scenarios and prompt the user for input in a very convenient fashion.
Motivation
In the userpass workflow, we could use the Modal component to show the different accounts the user might have for a given identity.

Closing this as #54 is merged.


Updated cryptocurrency mining paragraph.

The cryptocurrency mining description was lacking. I corrected the description and included a short sentence mentioning the possibility of alternatives to the proof-of-work consensus algorithm.

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

@dillon, everything LGTM! Thank you for helping us improve this section of the guide. Hope you don't mind, but I made a slight change to your final sentence. Looking forward to your next contribution! :+1: :+1:


Margin at TopAppBar it does not fit correctly

What RMWC Version are you using [major.minor.patch]:
6.014
Name your build system [Webpack, Rollup...]:
webpack
Describe the bug with as much detail as possible:
there is a margin when using top-app-bar
What happened, and what was supposed to happen:

the top app bar should fit at the top of the browser without a margin, you can see on the following sandbox:
https://codesandbox.io/s/rmwc-sandbox-9ctfw?file=/index.js

The styles come directly from google, so this would be an upstream issue.
But the actual issue is that every browser has a default margin / padding on the body. Either use a reset or just apply margin and padding of 0 to the body and HTML element.

Hello James,
Ok, I will review that, also I notice that the font does not adapt to different screen sizes, the ones that are featured like headline1 headline 3, etc.
do you have an example on how to manage this from rmwc?, thanks


ROX-20788: add wif enabled field for google image integrations

Description
Prefactor for adding WIF support to google image integrations.
Checklist

[x] Investigated and inspected CI test results
[ ] Unit test and regression tests added
[ ] Evaluated and added CHANGELOG entry if required
[ ] Determined and documented upgrade steps
[ ] Documented user facing changes (create PR based on openshift/openshift-docs and merge into rhacs-docs)

If any of these don't apply, please comment below.
Testing Performed
Here I tell how I validated my change
CI
Reminder for reviewers
In addition to reviewing code here, reviewers must also review testing and request further testing in case the
performed one does not seem sufficient. As a reviewer, you must not approve the change until you understand the
performed testing and you are satisfied with it.

/retest


flutter run should auto-create missing platform directories

We need a way to be able to just have a pubspec.yaml, a lib/main.dart, and perhaps a .metadata file, and be able to flutter run a project from only that. One way to do that would be to have flutter run auto-create the missing platform directory for the platform that the user is attempting to run on, either right in the project directory, or (probably better) in a temp area, perhaps inside the build dir.
The use case is that I'd like to be able to have "bare" projects that don't have any platform directories in them by default, so they can be checked in that way without all the boilerplate, and whenever they are run, they get the latest platform code for the version of Flutter running them.
This won't work for any app that needs customization, of course, but I do think there are a lot of "examples" and simple apps that could benefit from this kind of setup. One place where this would help is to eliminate the stale boilerplate code in the Flutter repo itself, including a bunch of legacy icon binaries that we'd rather not have in the repo in the first place.
Also, if this was the default mode of flutter create, when someone first encounters of a Flutter project, their first impression would be that of something pretty clean and simple, instead of a lot of arcane boilerplate that they probably don't understand or understand the need for (yet).
Some challenges to this proposal would be:

It would mean adding a way to write the platform boilerplate in a permanent location so it could be modified.
We'd need to make sure that changing the flutter create default behavior doesn't mess up the IDE integrations.
Projects that don't support a particular platform will no longer be able to indicate that just by not creating a platform directory for it: Flutter would just attempt to run there and fail.
The method of converting from temporary to "permanent" platform directories needs to be discoverable, and we'd need to educate users as to when that is necessary.

I know we used to have something similar, with the .ios and .android ephemeral directories, and we removed them. I can't remember exactly why, but perhaps we can avoid the pitfalls of that?
cc @Hixie @jonahwilliams

The big question in my mind is how does this interact with device auto selection? Maybe it doesn't ...

(we do still have .ios/.android but I don't think we talk about it at all)

Projects that don't support a particular platform will no longer be able to indicate that just by not creating a platform directory for it: Flutter would just attempt to run there and fail.

I think this would be incredibly annoying for open-source projects (maintainers and explorers alike); people would end up filing a lot of useless bugs about build failures on platforms the author has no intention of supporting.
It could be avoided by making it opt-in per platform. E.g., having a platform directory that's empty except for one magic file.

We do something similar with plugins IIRC, with the pubpec.yaml saying which platforms are supported, etc.
That said, if we move to pluggable platforms it would be unfortunate to have to run some incantation before being able to run an app on a new platform so I'd prefer if the opt-in defaulted to "all allowed" and just allowed apps to opt-in to being limited to specific platforms if desired.

if we move to pluggable platforms it would be unfortunate to have to run some incantation before being able to run an app on a new platform

Would it though? The more niche the embedding, the less likely an arbitrary application is to work due to plugin ecosystem coverage differences.


FMI integration force HA to refresh forecast many times a second

I noticed that on the latest HA the FMI integration refreshes the forecast many times a second.
I think this is caused by 'async_request_refresh' called from update methods.
This call also produces a lot of warnings about coroutine not been awaited.
I'll try my fix and create a PR when it is ready.

There is a proposed fix: https://github.com/anand-p-r/fmi-hass-custom/pull/40
It also contains a few other improvements. Let me know if you want me to separate them.


Add pinentry margin

@keybase/react-hackers
super small, adds margin bottom to pinentry popups.
Adds overflow auto to dropdown for users (if you have a lot of users you aren't able to pick them all or click someone else)

:+1:

:mag_right: The commits 5832a68ae3d5...985d4161d108 introduced some visual changes on win32:

Changed: unlock_folders-Normal (before) (after)

Changed: Pinentry-Passphrase_With_Error (before) (after)

Changed: Pinentry-Passphrase_Save_in_keychain (before) (after)

Changed: Pinentry-Passphrase_Normal (before) (after)

:mag_right: The commits 5832a68ae3d5...985d4161d108 introduced some visual changes on linux:

Changed: Pinentry-Passphrase_With_Error (before) (after)

Changed: Pinentry-Passphrase_Save_in_keychain (before) (after)

Changed: Pinentry-Passphrase_Normal (before) (after)


python3Packages.slicedimage: add tifffile dependency

Motivation for this change
noticed it was broken reviewing another package
Things done

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

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

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

Notify maintainers
cc @
[0 built (1 failed), 2 copied (9.4 MiB), 0.9 MiB DL]
error: build of '/nix/store/i3il08ishm9y5fdx5icy527s8cv1anzm-env.drv' failed
https://github.com/NixOS/nixpkgs/pull/74434
1 package failed to build:
python37Packages.starfish

1 package were built:
python37Packages.slicedimage

@GrahamcOfBorg build python37Packages.slicedimage

starfish is broken on master, not a regression


In Reviews Section - Grammatical Mistake Found.

Issue Description
The statement mentioned in the Reviews section is having a Grammatical Mistake. Please correct the statement.
Bagisto Version - Master
Steps To Reproduce
1. Reviews Section in Profile -> There we can see that.
Actual Result
Please check the screenshot

Expected Result
Correct Statement - You have not reviewed any products yet.

@jitendra-webkul
Now, this issue. is fixed. so I am closing this issue.
And I have attached a screenshot Here, for future reference.


Brew error when running cdev configure

  The command "brew services list | grep php@" failed.

  Exit Code: 1(General error)

  Working directory: /Users/benleonard/Development/northern ballet/northernballet.com

  Output:
  ================

  Error Output:
  ================
  Cloning into '/usr/local/Homebrew/Library/Taps/homebrew/homebrew-services'...
  Warning: No services available to control with `brew services`

$ brew --version
Homebrew 2.1.2
Homebrew/homebrew-core (git revision 3a1a; last commit 2019-05-15)

This was because php was not installed through brew. The solution was to install a version of php through brew.
The apache httpd.conf should reference this version of php (to handle php files) as described in the following article https://app.tettra.co/teams/creodechat/pages/cdev-local-php below "Apache PHP Setup - Part 1".