Tutorial: dynamic page quiz answer incorrect on FF

Describe the bug
the quiz asks for the url when clicking on the link. when selecting the option seen in firefox, it's marked as incorrect (it is correct on chrome).
To Reproduce

follow tutorial steps normally
answer quiz on https://nextjs.org/learn/basics/create-dynamic-pages/adding-a-list-of-posts
get wrong answer when using what's seen on firefox

Expected behavior
i'm not sure... i think both are valid (/post?title=Hello%20Next.js and /post?title=Hello Next.js). i understand that the end result is the same, but it might be confusing for beginners when running through the tutorial.
Screenshots

System information

OS: macOS
Browser: firefox dev edition, 61.0b4
Version of Next.js: 6.0.2

Just faced the same issue

Please file under github.com/zeit/next-site. Thanks 🙏

Done #35


Problem on running "production"

Hi, thanks for this project and your effort.
Using it on the boilerplate Cedra I could manage to integrate dramatiq into a Cement app.
But running built project "in production" does not seem to work.
When I setup the project after checkout by:
python setup.py install

The lazy-loader doesn't seems to do it's job.
Running the same by using
python setup.py develop

all ist working fine.
You can test it with the above project, after checkout (inside project folder):
rm -rf .venv ; make virtualenv ; source .venv/bin/activate ; python setup.py install ; cedra --help

does not work
but instead
rm -rf .venv ; make virtualenv ; source .venv/bin/activate ; python setup.py develop ; cedra --help

does work.

Any suggestions?
Cheers
Tom

Hi @TomFreudenberg, we'd need a bit more information to debug here. What do you mean by "does not work"?
Note that setup.py develop is nowadays spelled pip install --no-build-isolation -e ., and python setup.py install becomes pip install ..

Closing due to lack of information.


updated to python3

using 2to3 tool

Just seeing this now - I believe these changes are integrated into #12, closing. Please re-open if there is an issue.


Safe method for creating UninitSlice

When implementing BufMut the BufMut::chunk_mut method requires you to return an UninitSlice instance.
As UninitSlice only has the unsafe from_raw_parts() constructor, this means that even if your slice is definitely already initiated you still need to write unsafe code to return this slice.
This isn't great, and it would be nice to have a way to safely create a UninitSlice from a slice of already initiated data.

Adding this seems fine to me.


fix: [Dupe detection] Tax field does not show the "Default" label on the confirmation page

Explanation of Change

When selecting a transaction in review duplicate page, the default label was not shown in the tax field.
This PR stores the comment object (contains necessary details like customUnit, wypoints) of the selected transaction and merges it when creating the new comment object with the selected description (comment.comment) when building a new transaction on review duplicate confirmation page.

// buildNewTransactionAfterReviewingDuplicates util function
comment: {...reviewDuplicateTransaction?.comment, comment: reviewDuplicateTransaction?.description},

Fixed Issues
$ https://github.com/Expensify/App/issues/47975
PROPOSAL: https://github.com/Expensify/App/issues/47975#issuecomment-2308874978
Tests
Precondition:

Track tax is enabled in Workspace settings > Distance rates > Settings.
Distance rate has Tax rate and Tax reclaimable fields populated.

Go to workspace chat.
Submit two same distance expenses with the same distance rate that has tax rate and tax reclaimable on.
Go to transaction thread of any submitted expense.
Note that Tax field has the "Default" label.
Click Review duplicates.
Click Keep this on (any).
Proceed to confirmation page.
Verify Tax field shows the "Default" label .

[x] Verify that no errors appear in the JS console

Offline tests

Dupe detect does not work in offline mode but the PR changes can be tested if the Review duplicates is already showing for the same distance expenses

QA Steps
Precondition:

Track tax is enabled in Workspace settings > Distance rates > Settings.
Distance rate has Tax rate and Tax reclaimable fields populated.

Go to workspace chat.
Submit two same distance expenses with the same distance rate that has tax rate and tax reclaimable on.
Go to transaction thread of any submitted expense.
Note that Tax field has the "Default" label.
Click Review duplicates.
Click Keep this on (any).
Proceed to confirmation page.
Verify Tax field shows the "Default" label .

// TODO: These must be filled out, or the issue title must include "[No QA]."

[x] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native
https://github.com/user-attachments/assets/875cf769-2583-4998-908c-a0b664f83b4f

Android: mWeb Chrome
https://github.com/user-attachments/assets/d8f31f5f-1725-481e-9a28-45d865e299b4

iOS: Native
https://github.com/user-attachments/assets/38a35d66-bd0d-4150-9572-46cc1df2eaad

iOS: mWeb Safari
https://github.com/user-attachments/assets/dd9e092f-70ef-4ba5-a0d6-e0fbd391e615

MacOS: Chrome / Safari
https://github.com/user-attachments/assets/06e704fa-c9ef-424c-90ca-609d60c9d901

MacOS: Desktop
https://github.com/user-attachments/assets/38af2dc5-9d12-4846-bd51-ee8624f62a14

@alitoshmatov I think it's waiting for you!

Reviewer Checklist

[x] I have verified the author checklist is complete (all boxes are checked off).
[x] I verified the correct issue is linked in the ### Fixed Issues section above
[x] I verified testing steps are clear and they cover the changes made in this PR

[x] I verified the steps for local testing are in the Tests section
[x] I verified the steps for Staging and/or Production testing are in the QA steps section
[x] I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)

[x] I checked that screenshots or videos are included for tests on all platforms
[x] I included screenshots or videos for tests on all platforms
[x] I verified tests pass on all platforms & I tested again on:

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

[x] If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
[x] I verified proper code patterns were followed (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I verified that this PR follows the guidelines as stated in the Review Guidelines
[x] I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] If a new component is created I verified that:

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[x] I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: Native
https://github.com/user-attachments/assets/16449e7a-ce0d-42e3-9df1-352fd3986269

Android: mWeb Chrome

https://github.com/user-attachments/assets/6b850b0e-6fee-46bf-b897-25081becea85

iOS: Native

https://github.com/user-attachments/assets/6fc66677-1828-4a04-8422-7d73b2e288c8

iOS: mWeb Safari

https://github.com/user-attachments/assets/f47f9622-f668-45db-a928-174af0c0578f

MacOS: Chrome / Safari

https://github.com/user-attachments/assets/8581c849-1424-4117-818a-71ca21b407f9

MacOS: Desktop

https://github.com/user-attachments/assets/e43f3bb5-88f2-4fc1-a521-7ebe44bc6450

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

Failing in mweb with original bug id https://github.com/Expensify/App/issues/47975
https://platform.applause.com/services/links/v1/external/beb749795044548a2ab078d54c143bc49bbd113f43a076972943b10ef80ba1f1


chore: replace serum -> openbook in code

replace references to serum with references to openbook

Hi thank you for helping with the rename, unfortunately this change would cause a lot of unnecessary breaking changes across the ecosystem. Openbook v1 was developed under a 99% backwards compatibility mandate. Openbook v2 development (which has already started and should be open sourced today or early next week) will allow for this kind of change.

I see, sir


Redesigned request queues

#6 - redesigned request queues

Codecov Report

Merging #7 into master will decrease coverage by 2.37%.
The diff coverage is 77.33%.

@@             Coverage Diff              @@
##             master       #7      +/-   ##
============================================
- Coverage     74.72%   72.34%   -2.38%
- Complexity       45       58      +13
============================================
  Files            13       14       +1
  Lines           269      311      +42
  Branches         13       25      +12
============================================
+ Hits            201      225      +24
- Misses           61       74      +13
- Partials          7       12       +5

Impacted Files
Coverage Δ
Complexity Δ

.../main/java/wtf/g4s8/rio/file/CloseChanOnError.java
43.75% <33.33%> (ø)
2.00 <1.00> (?)

src/main/java/wtf/g4s8/rio/file/WriteGreed.java
70.58% <50.00%> (-16.92%)
1.00 <0.00> (ø)

...rc/main/java/wtf/g4s8/rio/file/WriteTaskQueue.java
66.66% <69.23%> (ø)
8.00 <4.00> (?)

.../main/java/wtf/g4s8/rio/file/ErrorOnException.java
77.77% <77.77%> (ø)
2.00 <2.00> (?)

src/main/java/wtf/g4s8/rio/file/ReadTaskQueue.java
82.85% <82.60%> (ø)
12.00 <5.00> (?)

src/main/java/wtf/g4s8/rio/file/ReadFlow.java
94.44% <100.00%> (+4.78%)
3.00 <0.00> (ø)

.../main/java/wtf/g4s8/rio/file/ReadSubscription.java
100.00% <100.00%> (ø)
5.00 <1.00> (ø)

src/main/java/wtf/g4s8/rio/file/WriteRequest.java
63.41% <100.00%> (+2.88%)
1.00 <0.00> (ø)

...c/main/java/wtf/g4s8/rio/file/WriteSubscriber.java
90.00% <100.00%> (+3.63%)
6.00 <3.00> (ø)

... and 2 more

Continue to review full report at Codecov.

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


AttributeError: 'bool' object has no attribute 'cursor'

delete issue - false alarm

thanks for reporting that


The ablation experiment of the size of memory bank

Hi! In your code the size of the memory bank of each class is set as 10000 and the background class's is set as 30000. Have you conducted the ablation study on the size of memobank and seen what the influence is exactly? Thanks!

Since the class background usually contains more pixels than other categories, we set a larger queue. We did not ablate the exact size of each categories.

Thanks!


ST3 Build 3103

Edited (October 7, 2018): I just pushed up some changes, please see https://github.com/jonschlinkert/sublime-monokai-extended/pull/88. Let me know if this works for you, I would appreciate any feedback.

If you update to ST Build 3013, you might notice that your colors are different. This is due to changes in ST, nothing was changed in this theme.
I personally find the colors way too busy now, so I'll be making some improvements. In the meantime, if you have any feedback or preferences, please comment here. Thanks!

You may mean 3103 build. And yes, i noticed the changes earlier today, firstly not like them, but now i find logic in them. It's cool to color every method name when params given to it, and not color method name and color parenthesis when no params to it.

But yea, I dont like that object properties are same color as strings.
And now, currently I dont use your theme, but the things are same everywhere :)
Btw, hot discussion was opened https://github.com/sublimehq/Packages/issues/141
Cheers,
Charlike.

I was able to easily fix most of the color changes. Also, since it's super easy to create new themes, and to toggle to different themes, I might just add a few different choices so that uses can have what they want.

@orbitbot it's because the new engine of sublime and won't be changed as i remember (but Jon can provide way to configure it?). see more https://github.com/sublimehq/Packages/issues/141
Actually, initially, i also don't like it, but now it seems better and okey to me.

I have fixes for a lot of these issues. I'll try to push up today

+1, subscribing here to see when #69 gets fixed.

Please see https://github.com/jonschlinkert/sublime-monokai-extended/pull/88.


monitor multiple elements

Hi there.
Could you help me?
How can i watch multiple elements? Thanks.
example: http://jsbin.com/qicizodeke
(function () {
    var projectCounter, options = {
        useEasing: true,
        useGrouping: true,
        separator: ',',
        decimal: '.',
        prefix: '',
        suffix: ''
    };

    var elem = $('.list__counter'),
        elemId = '',
        countNumber = elem.data('count');

    elem.each(function (index) {
        VisSense($(this)[0]).monitor({
            visible: function (monitor) {
                projectCounter = new CountUp(elem.attr('id'), 0, +countNumber, 0, 1, options);
                projectCounter.start();

                monitor.stop();
            }
        }).start();
    });
})();

@codev0 You are providing the same element to your "CountUp" instance.
Replace elem.attr('id') with $(elem[index]).attr('id') and it should work as expected.
Please report back if that solved your issue.

@theborakompanioni My bad. Thanks.

@codev0 No problem. Feel free to ask any question regarding this library! Have a nice day.


version 3.0.0 compatibility 2.9.2

i have custom spring starter with version 2.9.2. This starter create bean
@Configuration
PriestControllerConfiguration{
 @Bean
    fun priest(): Docket {
        return Docket(DocumentationType.SWAGGER_2)
            .groupName("priest")
            .select()
            .apis(RequestHandlerSelectors.basePackage(
                PriestController::class.java.getPackage().name
            ))
            .build()
            .apiInfo(apiInfo())
            .useDefaultResponseMessages(false)
    }
    }

all my consumer project(around 100 microservice) stay at version swagger 2.9.2. But now, some developers want up swagger to 3.0.0 and reporting that my starter failed.

APPLICATION FAILED TO START

Description:

An attempt was made to call a method that does not exist. The attempt was made from the following location:

    ru.tinkoff.bpm.priestspring.configuration.production.PriestControllerConfiguration.priest(PriestControllerConfiguration.kt:29)

The following method did not exist:

    'com.google.common.base.Predicate springfox.documentation.builders.RequestHandlerSelectors.basePackage(java.lang.String)'

The method's class, springfox.documentation.builders.RequestHandlerSelectors, is available from the following locations:

    jar:file:/C:/Users/mar15/.gradle/caches/modules-2/files-2.1/io.springfox/springfox-core/3.0.0/7c3367ce577c8acd9bf64c74488c9269253516c9/springfox-core-3.0.0.jar!/springfox/documentation/builders/RequestHandlerSelectors.class

The class hierarchy was loaded from the following locations:

    springfox.documentation.builders.RequestHandlerSelectors: file:/C:/Users/mar15/.gradle/caches/modules-2/files-2.1/io.springfox/springfox-core/3.0.0/7c3367ce577c8acd9bf64c74488c9269253516c9/springfox-core-3.0.0.jar

Action:

Correct the classpath of your application so that it contains a single, compatible version of springfox.documentation.builders.RequestHandlerSelectors

Process finished with exit code 1

I try up version swagger in my starter to 3.0.0
But now projects that remained on version 2.9.2 failed !!!
how i can configure my starter for migration time, when i must support 2.9.2 and 3.0.0 at the same time?

swagger versions you mention don't exist; you are using springfox which is a different project, please raise your issue there.

swagger versions you mention don't exist; you are using springfox which is a different project, please raise your issue there.


dependencies list should return consistent content for same API token and Gemfile.lock

We have a job that polls gemnasium using the CLI to get dependencies list every hour.
Sometimes, the response has the full list of our gems with their color coded statuses, but other times, we just get:
+--------------+--------------+--------+--------+------------+ | DEPENDENCIES | REQUIREMENTS | LOCKED | STATUS | ADVISORIES | +--------------+--------------+--------+--------+------------+ +--------------+--------------+--------+--------+------------+

The API documentation states that there's no rate limiting. If there's another issue, the CLI should return an appropriate error.

Hi Utako,
Thanks for reporting this. Could you maybe send more information to support.gemnasium.com (like the email used on gemnasium, and the id of the project)?
I'd like to investigate that.
Thanks,
Philippe

Sure thing.
Thanks,
Utako


Compiling Typescript project with graphql-hive/client fails due to missing graphql-yoda

Project with these files:
// package.json
{
  "name": "graphql-demo",
  "version": "1.0.0",
  "description": "demo",
  "main": "index.js",
  "scripts": {
    "compile": "tsc --build",
    "test": "echo \"Error: no test specified\" && exit 1"
  },
  "keywords": [],
  "author": "",
  "license": "ISC",
  "dependencies": {
    "@graphql-hive/client": "^0.32.0"
  },
  "devDependencis": {
    "typescript": "^5.2.2"
  }
}

// tsconfig.json
{
  "compilerOptions": {
  "outDir": "dist",
  "strict": true,
  "moduleResolution": "node",
  "esModuleInterop": true,
  "module": "commonjs",
  "target": "es2020"
  },
  "include": [
    "src/**/*",
  ],
  "exclude": [
    "node_modules"
  ]
}

// src/index.ts
import { hiveApollo } from '@graphql-hive/client'

console.log('hello');

fails when tsc --build is run with this error message:
12:08:25 ❯ npm run compile

><EMAIL_ADDRESS>compile
> tsc --build

node_modules/@graphql-hive/client/typings/yoga.d.ts:1:29 - error TS2307: Cannot find module 'graphql-yoga' or its corresponding type declarations.

1 import type { Plugin } from 'graphql-yoga';

This can be fixed with this line added to tsconfig.json, this is not optimal solution though:
"skipLibCheck": true

but it says @graphql-hive/client?

can you provide some kind of reproduction?

but it says @graphql-hive/client?

Sorry, got confused because I installed the CLI and I thought that was the issue. Updated the issue title.

can you provide some kind of reproduction?

I updated the issue with minimal reproduction (package.json, tsconfig.json and src/index.ts)

https://github.com/kamilkisiela/graphql-hive/issues/4571
we will ship a fix soon

https://the-guild.dev/graphql/hive/product-updates/2024-04-23-graphql-server-integrations-workers-support


Mangasco source link update

Source information
MangaSco 1.4.38
Source language
English
Source new URL
Mgsco.org
Other details
Just found it since it redirects me

Acknowledgements

[X] I have updated all installed extensions.
[x] I have opened WebView and checked that the source URL has not changed yet.
[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] I will fill out all of the requested information in this form.

When will it get fixed??


When creating different views, it would be nice to copy colors and filters from other views within the same project

What would you like to be added?
Right now, I've populated my Table view with many color rules and filter options.  When I create a Board or Calendar view, I have to recreate all those color and filter rules. I would like to have the option to use shared color rulesets (and filter rulesets) across all views within the project
Why is this needed?
Saved rulesets are the backbone of data visualization. Having to recreate them each time is painful and time consuming.

Prefer issue #779 and close this as duplicate.


Language compatibility issue: special characters

In the protocol you can specify reminder text of notifications (for example see https://github.com/JeroenDMW/RADAR-aRMT-protocols/blob/master/DynaMORE/protocol.json). I noticed that this is not yet compatible with special characters (e.g. special characters in polish / Hebrew alphabet).
Is this something that can be fixed without requiring an app update?
@mpgxvii

EDIT: Added screenshot for reference

@mpgxvii I assuming these lines here https://github.com/JeroenDMW/RADAR-aRMT-protocols/blob/0a115bba82f8f5318e94310108c1fe19d24f9dab/DynaMORE/protocol.json#L132-L137

@mpgxvii I assuming these lines here https://github.com/JeroenDMW/RADAR-aRMT-protocols/blob/0a115bba82f8f5318e94310108c1fe19d24f9dab/DynaMORE/protocol.json#L132-L137

That's correct :)

Moved issue to https://github.com/RADAR-base/RADAR-Questionnaire/issues/1305.


discussion: let Table can be clone

In risingwave sink, the sink own the table. We create writer or coordinator using table in sink. We need commit in writer or coordinator which means that we also need own table in writer and coordinator.

cc @liurenjie1024 @Xuanwo

Perhaps the sink could store all configuration needed to create a new table, instead of relying on the current state of the Table.


Docker migrations don't seem to run anymore.

It's really weird because last night docker ran perfectly for me on both pg and mysql. For some reason now the migrations don't get run. Not sure what could have changed between now and then. Perhaps something with the docker image?
I went through and cleaned up the docker file and added options to that sqlite works. Went to test that all 3 still worked in docker and it was broken. I've spend 3 hours trying to get to the bottom of it but all I can figure out is that migrate isn't happening although it still works fine with kgen m up if I run it locally. Ran a shell inside the docker image and kgen m up exited without any messages.

Seems to just be an issue with table already existing in volume.

@elorest how did you resolve this?  I'm having the same issue.

also, do you mind if I change the db flag to -d instead of --db?
I added support for ecr templates and want to use -t
https://github.com/TechMagister/kemalyst-generator/pull/34

Yeah -d sounds great. I also add a flag called --deps while I was making sqlite work.
I spent 4 hours from midnight til 4AM trying to make docker work again. I'm super confused on that. It actually started working for me like 10 times in a row so I closed the ticket and it immediately came back. Like some sort of ghost in the machine. :(. It seems to be some sort of issue with loading precedence or something. Sometimes the migrate container exits before the database has even started. Not sure if there's something wrong with the depends_on syntax or what. I have a lot of other projects to work on today and I've spent way to many hours working on crystal this week.
If I can solve docker soon I'm just going to send a pull request for my sqlite fix which also works in docker, and let someone who understands docker-compose a bit better try to fix this. I'm hoping that's you.

Sounds good. The depends_on option doesn't wait for the port to open. I will look at adding a check to wait for the port to open before migrating.
Looking forward to the SQLite support.
Sent from my iPhone

On Apr 16, 2017, at 12:09 PM, Isaac Sloan<EMAIL_ADDRESS>wrote:
Yeah -d sounds great. I also add a flag called --deps while I was making sqlite work.
I spent 4 hours from midnight til 4AM trying to make docker work again. I'm super confused on that. It actually started working for me like 10 times in a row so I closed the ticket and it immediately came back. Like some sort of ghost in the machine. :(. It seems to be some sort of issue with loading precedence or something. Sometimes the migrate container exits before the database has even started. Not sure if there's something wrong with the depends_on syntax or what. I have a lot of other projects to work on today and I've spent way to many hours working on crystal this week.
If I can solve docker soon I'm just going to send a pull request for my sqlite fix which also works in docker, and let someone who understands docker-compose a bit better try to fix this. I'm hoping that's you.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or mute the thread.

I reverted back to the postgres only version of the docker-compose and it
still doesn't work. Then I tried it on my other computer and it worked 3
times and then stopped. I wonder if it has to do with how we're storing the
volume locally or something... I'm going to commit my
docker-compose.yml.ecr that should work with everything as
docker-compose.yml.wip.ecr in the sqlite PR.
Isaac Sloan - isaacsloan.com
Artisan Rails Architect
1391 S Slate Canyon Dr.
Provo, Ut 84606
Cell:<PHONE_NUMBER>
On Sun, Apr 16, 2017 at 2:02 PM, Dru Jensen<EMAIL_ADDRESS>wrote:

Sounds good. The depends_on option doesn't wait for the port to open. I
will look at adding a check to wait for the port to open before migrating.
Looking forward to the SQLite support.
Sent from my iPhone

On Apr 16, 2017, at 12:09 PM, Isaac Sloan<EMAIL_ADDRESS>wrote:
Yeah -d sounds great. I also add a flag called --deps while I was making
sqlite work.
I spent 4 hours from midnight til 4AM trying to make docker work again.
I'm super confused on that. It actually started working for me like 10
times in a row so I closed the ticket and it immediately came back. Like
some sort of ghost in the machine. :(. It seems to be some sort of issue
with loading precedence or something. Sometimes the migrate container exits
before the database has even started. Not sure if there's something wrong
with the depends_on syntax or what. I have a lot of other projects to work
on today and I've spent way to many hours working on crystal this week.
If I can solve docker soon I'm just going to send a pull request for my
sqlite fix which also works in docker, and let someone who understands
docker-compose a bit better try to fix this. I'm hoping that's you.
—
You are receiving this because you modified the open/close state.

Reply to this email directly, view it on GitHub, or mute the thread.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/TechMagister/kemalyst-generator/issues/35#issuecomment-294371120,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAHmpMyRcJ--m-qD6yRccYakwZcGdINkks5rwnPOgaJpZM4M-kna
.

Perhaps something like this could be useful.

@elorest this should now be fixed.  let me know if you still run into any issues.

darn, worked locally but now having issues.

minor fix.  should be good now.

LOL. Yeah I had nightmares about that bug last night. So frustrating when
it would start working randomly and then stop.
Isaac Sloan - isaacsloan.com
Artisan Rails Architect
1391 S Slate Canyon Dr.
Provo, Ut 84606
Cell:<PHONE_NUMBER>
On Sun, Apr 16, 2017 at 10:15 PM, Dru Jensen<EMAIL_ADDRESS>wrote:

Closed #35 https://github.com/TechMagister/kemalyst-generator/issues/35.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/TechMagister/kemalyst-generator/issues/35#event-1044598605,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAHmpGw2eN2TEzwvf8Ns74wDeEKNi1UEks5rwudSgaJpZM4M-kna
.


Optimize vmdkops_admin.get_metadata() function

The command "vmdkops_admin volume ls" took around 28 seconds against a 500 volume setup. One of the major bottlenecks is the function vmdkops_admin.get_metadata(), which took about 6 seconds to complete. We need to optimize this function to get rid of the bottleneck.
Please refer to #1083 for detailed performance analysis.

Performance enhancement should be a mustfix


Next release

This issue should have been a discussion but since discussions aren't open I guess it's fine if we discuss it here.
Is there a goal or roadmap for a next release, something planned?

Apologies for the delay.
Firstly, good point about discussions - I'll try getting that set up now.
Right now there's no clear roadmap for a new release, because although the supabase python libraries are community libraries it's mainly the 4 of us maintainers who're working on them, and this repo has been sort of on the backburner while we worked on the other libraries (postgrest-py, storage-py, gotrue-py etc). We'd be happy to review and merge contributions here too though!
A sort of rough roadmap I've had for some time:

Remove the synchronous interfaces this library provides
Try and complete these three issues:
[ ] supabase-community/supabase-py#73
[ ] supabase-community/supabase-py#89
[ ] supabase-community/supabase-py#107

I'm happy to hear more suggestions!

Thanks for the response, I'll check for the issues and will try to contribute to a solution for them.
I was asking because our team needs to use a higher version of websockets with was merge but isn't on the package for pypi yet.

Sorry for late response, I'm sick.
Currently realtime is using websockets 10.3 but the released version is using 9.2 I think.


[LOW] Coaches upload video introducing themselves (marketing and online platform)

What problem does this solve?

Video hosting is very very expensive, I would rather have the coaches upload a youtube video and we embed that into the site.

Yeah this is great.


update doc comment for new_archetype in query-state

Objective
I was reading through the bevy_ecs code, trying to understand how everything works.
I was getting a bit confused when reading the doc comment for the new_archetype function; it looks like it doesn't create a new archetype but instead updates some internal state in the SystemParam to facility QueryIteration.
(I still couldn't find where a new archetype was actually created)
Solution

Adding a doc comment with a more correct explanation.

If it's deemed correct, I can also update the doc-comment for the other new_archetype calls

If it's deemed correct, I can also update the doc-comment for the other new_archetype calls

Let's do this in the same PR.

Updated the docs for all other new_archetype calls. Maybe the function itself should be renamed

bors r+


Proper way to import Materialize in requirejs module

Description
I want to import Materialize in a requirejs module.
Materialize is passed through define(), but then a Materialize.toast() function is not recognised.
If not using requirejs, but loading from

@gg4u You have to require the specific library from materialize you want to use. Try the following config file for requirejs:
paths: {
     // I'm assuming you have a JS folder, this sets the root to the JS folder. So you do not have to
     // keep writing: 'materialize/js/{js_file}.js' everytime.
     materialize': 'libs/materialize/js'
},
shim: {
     'materialize/velocity.min': {
            deps: ['jquery']
     },
     // Some of these were needed in order to force a loading order.
      'materialize/global': ['jquery', 'materialize/velocity.min'],
        'materialize/jquery.easing.1.3': ['jquery'],
        'materialize/jquery.hammer': {
            deps: ['jquery', 'hammerjs'],
            exports: '$.hammer'
        },
        'materialize/tabs': ['jquery', 'materialize/global'],
        'materialize/buttons': ['jquery', 'materialize/global'],
        'materialize/dropdown': ['jquery', 'materialize/global', 'materialize/jquery.easing.1.3'],
        'materialize/sideNav': ['jquery', 'materialize/jquery.hammer'],
}

@gg4u Did you solve the problem?
Thanks
Closed due inactivity, feel free to reopen it if it is still necessary.

Duplicate of https://github.com/Dogfalo/materialize/issues/1422


Have description in stream popover

Fixes: #6032

This PR is for the issue 6032
Discussions:
https://chat.zulip.org/#narrow/stream/6-frontend/topic/stuck.20PR
https://chat.zulip.org/#narrow/stream/design/topic/stream.20description.20in.20the.20pop-up.20nav.20box
GIFs or Screenshots:
Before:

After:

@timabbott @rishig please review :smile:

Tested locally. Here are the results on Firefox 59:

I would recommend using ellipsis in case the description is larger than the width of the component. I believe there is a CSS property for that.

@aero31aero can you check again for ellipsis because css property is defined for it and it is showing ellipsis for me in firefox.If it is still same for you then let me know.I'll fix the alignment issue for firefox.

@aero31aero @showell please review. The max width and ellpisis issue has now been resolved.

The code LGTM.
@rishig Can you give this a quick style review?  I'm a little concerned that the description will look funny if it's not below the name of the stream.  It might be worth thinking about putting the name of the stream above the description, and then remove the stream name from lots of the individual items, where it looks cluttered to me.

yeah, that's a great idea (stream name on top, remove it from the individual items).
Could you give a screenshot of what it currently looks like?

@rishig
currently the popover looks like this

On doing the required changes it will look like this.

Great! Mostly just minor comments:

Pin stream to top -> Pin to top; Compose a .. -> New topic; Mark all .. -> Mark all messages as read; Mute .. -> Mute
Maybe a hr, like

between the description and the "Stream settings"
Could you show an example with the text being too long?

(As unrelated follow-up, we should replace all the icons with fixed-width versions of the icons. I'm also not sure why "Narrow to stream" has the icon it does.)

@rishig sorry for the typos earlier. Here are the screenshots.
Introduced horizontal ruler

A stream with big description

I feel like this design, which only really works with 1-line descriptions, is going to be problematic.  We should at least have a way to see the full description that's nicer than a mouse-over (maybe an "expand") button?  I'm imagining use cases like having a link where the HTML title sort of thing really won't work.
For layout, I would be interested in a screenshot for the two-column idea.  The other idea I'd try is decreasing the font size for the "description" thing; I suspect that will lead to a better outcome than just making it really wide.

Can it be a javascript-controlled popover instead? Expand also seems good, though in that case possibly we should limit the description to N characters (possibly we should limit it anyway).


Inverted zoom

I've inverted zoom as it should be.

I am not sure if this is the the way it should be I think it depends on implementation in any project. If you point me to some document where this is described, I would consider these change. Otherwise we can just add settings for zoom inversing.

Well, browsers use it and on the phone it is the same thing too. Now even the finger gestures are reversed.

I've tried finger gestures and you are right. Merging this. Thank you!


How to get the distance of the vehicle from the center of the lane and the angle between the vehicle orientation and the road tangent

Hi, I am using CARLA 0.9.13 in Ubuntu20.04. This answer said that we could use the waypoint to calculate the distance and the relative angle. I tried to do so, but the problem is that the yaw of the waypoint would suddenly change 360 degree even when the vehicle is still on the same lane.
code to compute the distance and relative angle
#orientation of vehicle: vehicle.get_transform().rotation.yaw
      veh_trans = vehicle.get_transform()
      veh_loc = veh_trans.location
      veh_rot = veh_trans.rotation

      wpt = world.get_map().get_waypoint(vehicle.get_location(), project_to_road=True)
      #wpt = world.get_map().get_waypoint(carla.Location(), project_to_road=True)
      wpt_loc = wpt.transform.location
      wpt_rot = wpt.transform.rotation

      print("veh loc: ", veh_loc)
      print("wpt loc: ", wpt_loc)
      print("veh rot: ", veh_rot)
      print("wpt rot: ", wpt_rot)
      print("road id: %d lane id: %d section id:%d "%(wpt.road_id, wpt.lane_id, wpt.section_id))
      print("x dist: ", veh_loc.x - wpt_loc.x, "y dist: ", veh_loc.y - wpt_loc.y)
      print("x-y dist: ", np.linalg.norm(np.array([veh_loc.x - wpt_loc.x, veh_loc.y - wpt_loc.y])))
      print("rel ang: ", veh_rot.yaw - wpt_rot.yaw)

output of two consecutive frames (i.e. world.tick())
veh loc:  Location(x=384.683350, y=326.657074, z=0.001258)
wpt loc:  Location(x=384.807983, y=326.609802, z=0.000000)
veh rot:  Rotation(pitch=0.017772, yaw=172.483643, roll=-0.245605)
wpt rot:  Rotation(pitch=0.000000, yaw=179.578339, roll=0.000000)
road id: 14 lane id: -1 section id:0
x dist:  -0.1246337890625 y dist:  0.047271728515625
x-y dist:  0.13329740317399547
rel ang:  -7.094696044921875

veh loc:  Location(x=384.281006, y=326.685822, z=0.001440)
wpt loc:  Location(x=384.281006, y=326.609985, z=0.000000)
veh rot:  Rotation(pitch=0.009050, yaw=174.069626, roll=-0.216553)
wpt rot:  Rotation(pitch=0.000000, yaw=-180.000000, roll=0.000000)
road id: 14 lane id: -1 section id:0
x dist:  0.0 y dist:  0.075836181640625
x-y dist:  0.075836181640625
rel ang:<PHONE_NUMBER>544922

Is the calculation method wrong? Or do I misunderstand anything about the waypoint? Thanks in advance.

I'm facing a similar problem. I uses LocalPlanner.get_plan to retrieve a planned route for a vehicle. While checking whether the vehicle has reached its destination, I want to make sure both the distance and orientation is within a pre-defined threshold.
When calculating the orientation difference, I used:
np.radians(np.abs(dest_waypoint.transform.rotation.yaw - hero_actor.get_transform().rotation.yaw))

But the returned value could be very large even if I manually controlled the vehicle to stop at the destination. I've checked these two transforms, and I got:

Apparently, these two "yaw" are all around 0, but their value varies about 360 degrees. How to fix that?


Unable to sign XCM Transactions

We are unable to sign XCM Transactions. Any other transactions (SWAP for eg.) work fine.
We have tried to use PolkadotJS wallet and Talisman, and both output the same.
Mangata X app works fine with XCM, any hint as to where the error might be?
Many thanks.

Hey @dudo50 ! Im Gonzalo QA lead at mangata.
Can you please help us by providing the following info?

How to reproduce
Hash of the transaction you are aiming to sign.
Browser & extension, and account ( just the address :P )
Thanks!

hey @dudo50 ,
I can see in the source code that you are creating the API promise from the web socket. We have some types / rpcs that may impact the correct signing behavior.
Have you considered using our awesome SDK? It will import all the types and the API together!  There are plenty of eamples and how to use it. You can even have a look at our tests in mangata-e2e repo. They may also help :)
SDK:
https://github.com/mangata-finance/mangata-sdk
Feel free to ping @devdanco  for any related Sdk technicality!

@goncer,
we managed to fix it by using the mentioned sdk. Many thanks for your assistance!


Rationalize fieldSpec part for the functions

type FieldSpec struct {
	resid.Gvk          `json:",inline,omitempty" yaml:",inline,omitempty"`
	Path               string `json:"path,omitempty" yaml:"path,omitempty"`
	CreateIfNotPresent bool   `json:"create,omitempty" yaml:"create,omitempty"`
}

fieldSpec is used in kustomize to filter/select resources that will be processed by transformers. We need to have a pipeline level filter/selector to do this for all functions in pipeline.
Each function needs to have the functionality to process the fields in CRDs. For example, metadata.labels for a CRD.

cc @droot @frankfarzan @mengqiy

cc @droot @frankfarzan @mengqiy


feat: automatically progress trades when approvals are executed externally

Description

Pull Request Type

[ ] :bug: Bug fix (Non-breaking Change: Fixes an issue)
[ ] :hammer_and_wrench: Chore (Non-breaking Change: Doc updates, pkg upgrades, typos, etc..)
[ ] :nail_care: New Feature (Breaking/Non-breaking Change)

Issue (if applicable)

closes #
Risk

Testing

Engineering

Operations

Screenshots (if applicable)

Current dependencies on/for this PR:

develop

PR #5825   👈

This stack of pull requests is managed by Graphite.


⚠ Thumbnails API Endpoint has degraded performance

In 0e50463, Thumbnails API Endpoint (https://thumbnails.roblox.com/v1/assets?assetIds=82738847&format=Png&isCircular=false&size=30x30) experienced degraded performance:

HTTP code: 200
Response time: 1174 ms

Resolved: Thumbnails API Endpoint performance has improved in 40cfbc1.


Code cleanup

More time bored in WebEx meetings .... is this really more fun to do? Right now it sure is.

Hi @calebnelton, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by .NET Foundation and real humans are currently evaluating your PR.
TTYL, DNFBOT;

@calebnelton thanks for the PR. Can you squash everything into one commit?
I should note that we generally prefer avoiding such changes because they don't offer a significant improvement of the code, and it takes a fair bit of time from many people to work on reviewing, merging, and verifying the PR. Feel free to discuss with us through issues any additional changes you might have in mind.

@Eilon commits squashed
The next time I commit changes of this nature i'll make sure I combine them with other issues that will provide better improvements to the codebase.

@calebnelton thanks!

These changes have been merged. Thanks @calebnelton for your contribution!


Commit 4b03944 switched psm1 file to binary

With commit 4b03944e3716d057475a4209474da3e54d956ae2, git now thinks z.psm1 and z.psd1 are binary files.  The commands run are through tortoisegit in windows.

Looks like github thinks it is a binary file as well now.


LDAP git login does not work with 2FA pwd on LDAP, it does however work on web UI

I'm using FreeIPA as a central user management system.
We provide users with 2FA tokens activated in FreeIPA, so users have dynamic passwords (the 2FA token is appended to the static user password)
i can successfully log in on web UI using an LDAP account with 2FA enabled in FreeIPA
however, that same account fails to authenicate when accessing via git (clone, push). git pull however appears to successfully authenticate.
no issues arise when accessing via git with accounts that are not enabled for 2FA using static passwords.
Error in debug log when accessing using git with an account that has 2FA enabled:
2022/04/06 10:05:15 ...dules/git/command.go:143:RunWithContext() [D] /home/gitea/repos/sipcall/bfl.git: /usr/bin/git -c credential.helper= -c protocol.version=2 -c uploadpack.allowfilter=true -c filter.lfs.required= -c filter.lfs.smudge= -c filter.lfs.clean= upload-pack --stateless-rpc --advertise-refs .
2022/04/06 10:05:15 ...dap/source_search.go:141:bindUser() [D] LDAP auth. failed for uid=******,dc=admin, reason: LDAP Result Code 49 "Invalid Credentials":

Git should use SSH key or generated token. Git doesn't use the password.

Git doesn't use the password.

Appears to use password for non 2FA users. No one uses token currently. However only 2FA LDAP users appear affected.

Hmm, then let's keep the issue open to see if there are other opinions about the git + ldap system. The auth system is pretty complex at the moment.

I've spend some time testing since it was quiet at work. Enabled 2FA on my FreeIPA account in our test environment and tried to clone, push and pull over https.

git pull however appears to successfully authenticate.

I'm not sure how you came to this conclusion. It is indeed the case that, when there are no changes while doing a git pull, git successfully returns Already up to date.. However when there are new commits to pull down, I get the same error as when trying a git clone or git push with 2FA enabled:
Username for 'https://xxx.yyy.zzz': ********
Password for<EMAIL_ADDRESS>
error: RPC failed; HTTP 401 curl 22 The requested URL returned error: 401
fatal: the remote end hung up unexpectedly

However there's nothing in the Gitea log for me, perhaps I need to increase the log level for this?
Far be it from me to tell you how to do things, but I do agree with @wxiaoguang that you should probably switch to tokens or ssh keys for git authentication. Github.com does not even allow you to use account passwords anymore when authenticating git operations and I'm sure others will follow. If you were using 2FA on Github, you were already required to use tokens. Using tokens or ssh keys has several security advantages.
You can easily use ssh keys throughout your environment by having users generate the key pair, then add the public part to their account in FreeIPA or have them do that themselves. Then in Gitea, in the FreeIPA authentication source configuration, set ipaSshPubKey as the value for Public SSH Key Attribute and sync all users so Gitea pulls in all the public keys. You'll have to change the remote URL for all your repositories to ssh:// or git@gitea style URLs, but you should be able to copy the correct URL from the repository page in Gitea.

Related to https://github.com/go-gitea/gitea/issues/17350  (or I'd like to say they are the same problem)


Install dependencies with yarn

We are installing our dependencies with npm, not yarn.  We want to switch over to installing with yarn and create a yarn.lock file.
https://github.com/cerner/generator-terra-module/blob/master/generators/app/index.js#L252-L256
Here is documentation on how we can use yarn instead of npm.
http://yeoman.io/authoring/dependencies.html
In order to install with yarn, we also need to upgrade our version of yeoman-generator to ^1.0.0. Installing with yarn is not supported by our current version of yeoman-generator.
https://github.com/yeoman/generator/commit/4eccb2a81b4fdb652ebf618a3dd7be7aa7950a96

Lerna is not compatible with yarn. Closing issue.


Allow int and bool types in most YAML types

Since #86 promotes any integers encoded as strings to integers, this change allows integers and bools to convert back to strings in YAML.
This change also prevents panics as in #108. Fixes #113.
Signed-off-by: Lachlan Donald<EMAIL_ADDRESS>

We can't convert bools to strings because yaml converts many different values (y, yes, True, true, etc) to a single value of true. In almost all cases, this is not what you want, and can break things. A raw bool should be an error , and needs to be quoted.
Integers are ok though, because they don't change form (as far we've seen).

Closing in favour of #115.


Deadlock on lifecycleMonitor

Back port of issue https://github.com/spring-projects/spring-kafka/pull/2629

Fixed via https://github.com/spring-projects/spring-kafka/commit/ea8744099f6d8c3c7c93d68eaf72cb4bb39e97e8


Support default values

Currently, when using FluentMethod with default values, the FluentApi does not keep the default values in the generated builder, such that the value always has to be provided. It would be nice if the generator was able to carry them over. See also ParameterInfo.DefaultValue. It would be interesting if the FluentMethod also allowed different signatures for the same method name at the same step, although I can imagine that overloads are supported already (I didn't verify that).

Thank you, good catch! Yes, overloads are already working.


[10.x] Fix date validation issues

Fixes #49955
Fixes #49988
This is an alternative to #49956
In Laravel v10.42.0, we can validate that a date is after or before another one, adding/subtracting a given amount of minutes, hours, seconds:
$data = [
    'dt1' => '2020-01-01',
    'dt2' => '2024-01-01',
];

Validator::make($data, [
    'dt1' => 'required|date',
    'dt2' => 'required|date|after:dt1 +1 day', //dt +1day also works
]);

PR #49871 broke this behavior and the nested after date validation.
I tried to fix both issues without reverting the original PR. Also added tests to make sure after and before are working as expected now.

Reverted original PR. Will release that before trying again.

@taylorotwell should I send this again once you release the new version?


added a comma for testing

I can revert this comma change after capturing the pull request step.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.


failed to run bootc install

fresh install today
restarted my machine to be rootful
installed via brew
podman-bootc run quay.io/fedora/fedora-bootc:41
Copying config sha256:3f8962e7d7f711840e16cd50d88d8c7ebe991f2a5df3814c98d434060e9c2e6d
Writing manifest to image destination
Creating bootc disk image...
Installing image: docker://quay.io/fedora/fedora-bootc:41
Digest: sha256:c7d8354b1271c490d57cf70ec6758284e1ff3f8d16c56fd55ba0bcab0411d36a
ERROR Installing to disk: Creating rootfs: No root filesystem specified
Error: unable to install bootc image: failed to create disk image: failed to run bootc install```

See the tag "Important" under
https://docs.fedoraproject.org/en-US/bootc/podman-bootc-cli/

There is no default root filesystem type configured for the Fedora base images; you can select one in this way:

It's kind of intentionally painful actually because the current vision of the base image is to be generic and encourage derived images which can include their own default filesystem types and other tweaks.
Maybe we could tweak podman-bootc to detect this case better but for now I think the docs are hopefully enough?

Boooo
example commands should "just work"
Error: unknown flag: --filesystem

Maybe we could tweak podman-bootc to detect this case better but for now I think the docs are hopefully enough?
I don't think docs are enough for someone who is taking this out for a spin. or error messages should tell me where to look.

I checked for closed issues, but beyond issues, why would I go to fedora to figure out why the tool isn't working?

and now with reading #70 I'm all caught up


Made a REST API using FastAPI and connected it to the AWS RDS PostgreSQL

Made a REST API using the FastAPI as the web framework. Also, established a connection to the AWS RDS PostgreSQL database. Made the list of the tables as discussed in the database schema.

Looks good!


Format duration using prime characters

Durations in minutes and seconds are sometimes denoted using the prime and double-prime characters, e.g. 4′33″.
Would it make sense to add a "prime" style to allow formatting a duration in this manner?

This is a question for CLDR. If CLDR adds this data, we could expose it with another style option in DurationFormat. I was looking and I think this is the closest ticket:
https://unicode-org.atlassian.net/browse/CLDR-14208

Closing this issue since it's beyond the scope of this proposal.


fails to connect to emulator started through gcloud sdk docker image

Is this a client library issue or a product issue?

I'm not entirely sure but couldn't find a better place to file the issue.

Did someone already solve this?
after a couple days of searching, I was unable to find an existing bug or solutoin in https://github.com/googleapis/nodejs-firestore/issues,  https://github.com/googleapis/google-cloud-node or http://stackoverflow.com/questions/tagged/google-cloud-platform+node.js but considering the sheer volume of these sources I may have missed it. If so I apologize in advance

Environment details

OS: Ubuntu 20.04.1 LTS
Node.js version: v12.18.3
npm version: 6.14.6
@google-cloud/firestore version: 4.2.0

Steps to reproduce

clone https://github.com/jeantil/diggin-firebase-admin
run npm install
start gcloud sdk emulator through docker image:  docker run --rm -p 8080:8080  google/cloud-sdk gcloud beta emulators firestore start --host-port=<IP_ADDRESS>:8080
run the test case : DEBUG="digin:*" node_modules/.bin/babel-node firestore.js

When the test case works, it will display
  digin:firebase:admin start +0ms
  digin:firebase:admin trying to connect to firebase on localhost:8080 +2ms
Entered new data into the document
Updated an existing document
Read the document
Deleted the document

if it fails, it will display
  digin:firebase:admin start +0ms
  digin:firebase:admin trying to connect to firebase on localhost:8080 +1ms
watchdog timed out!

I am unsure what is failing exactly but I had an older docker image (custom made based on firebase-tools) which contains the cloud-firestore-emulator-v1.9.0.jar and running this version of the emulator works consistently and running agains an image which contains cloud-firestore-emulator-v1.11.7.jar fails.
I was unable to find a repository/issue tracker for cloud-firestore-emulator and this repository seemed to be the next best thing. If this is not the place, i'll be happy to take a pointer !

@schmidt-sebastian can you include emulator folks? it seems a recent release may be interfering with the client?

@yuchenshi Does this ring a bell?

We haven't really changed the listener logic recently and I'm curious what is going on here. I know it's hard to debug connectivity issues, but could you please try these things:

Use curl to check if you can connect to the emulator inside AND outside Docker. (e.g. docker exec may help for "running in the docker". Try also netstat -l and compare the output.
Try changing --host-port=<IP_ADDRESS>:8080 to --host-port=<IP_ADDRESS>:8080 and repeat 1.

That should get us started on this.

@yuchenshi thanks for the pointers, here are the results I observe for the various commands requested
using --host-port=<IP_ADDRESS>:8080
> docker run --rm -p 8080:8080 google/cloud-sdk gcloud beta emulators firestore start --host-port=<IP_ADDRESS>:8080
Executing: /usr/lib/google-cloud-sdk/platform/cloud-firestore-emulator/cloud_firestore_emulator start --host=<IP_ADDRESS> --port=8080
[firestore] API endpoint: http://<IP_ADDRESS>:8080
[firestore] If you are using a library that supports the FIRESTORE_EMULATOR_HOST environment variable, run:
[firestore]
[firestore]    export FIRESTORE_EMULATOR_HOST=<IP_ADDRESS>:8080
[firestore]
[firestore] Dev App Server is now running.
[firestore]
^Y[firestore] Sep 23, 2020 7:53:25 PM io.gapi.emulators.netty.HttpVersionRoutingHandler channelRead
[firestore] INFO: Detected non-HTTP/2 connection.

from host
> docker ps
CONTAINER ID        IMAGE                              COMMAND                  CREATED              STATUS              PORTS                     NAMES
ea68b3d3cfbf        google/cloud-sdk                   "gcloud beta emulato…"   About a minute ago   Up About a minute   <IP_ADDRESS>:8080->8080/tcp    blissful_dewdney

curl

> curl http://<IP_ADDRESS>:8080
curl: (56) Recv failure: Connection reset by peer

netstat (which has been replaced by the ss command)

> sudo ss -ltpn | grep 8080
LISTEN   0        4096                        *:8080                   *:*       users:(("docker-proxy",pid=426827,fd=4))

provided sample

DEBUG="digin:*" node_modules/.bin/babel-node firestore.js
  digin:firebase:admin trying to connect to firebase on localhost:8080 +0ms
watchdog timed out!

from container
 docker exec -it blissful_dewdney /bin/bash

curl

root@ea68b3d3cfbf:/# curl http://<IP_ADDRESS>:8080
Ok

netstat (which has been replaced by the ss command)

root@ea68b3d3cfbf:/# ss -ltpn
State                    Recv-Q                   Send-Q                                       Local Address:Port                                        Peer Address:Port
LISTEN                   0                        4096                                             <IP_ADDRESS>:32955                                            <IP_ADDRESS>:*                       users:(("java",pid=40,fd=96))
LISTEN                   0                        50                                               <IP_ADDRESS>:37861                                            <IP_ADDRESS>:*                       users:(("java",pid=40,fd=44))
LISTEN                   0                        4096                                             <IP_ADDRESS>:8080                                             <IP_ADDRESS>:*                       users:(("java",pid=40,fd=97))

using --host-port=<IP_ADDRESS>:8080
> docker run --rm -p 8080:8080 google/cloud-sdk gcloud beta emulators firestore start --host-port=<IP_ADDRESS>:8080
Executing: /usr/lib/google-cloud-sdk/platform/cloud-firestore-emulator/cloud_firestore_emulator start --host=<IP_ADDRESS> --port=8080
[firestore] API endpoint: http://<IP_ADDRESS>:8080
[firestore] If you are using a library that supports the FIRESTORE_EMULATOR_HOST environment variable, run:
[firestore]
[firestore]    export FIRESTORE_EMULATOR_HOST=<IP_ADDRESS>:8080
[firestore]
[firestore] Dev App Server is now running.
[firestore]

from host
docker ps
CONTAINER ID        IMAGE                              COMMAND                  CREATED             STATUS              PORTS                     NAMES
e4172f6a312d        google/cloud-sdk                   "gcloud beta emulato…"   56 seconds ago      Up 54 seconds       <IP_ADDRESS>:8080->8080/tcp    reverent_ishizaka

curl

curl http://<IP_ADDRESS>:8080
Ok

netstat (aka ss)

sudo ss -ltpn | grep 8080
LISTEN   0        4096                        *:8080                   *:*       users:(("docker-proxy",pid=428377,fd=4))

provided sample
tried with both localhost:8080 and <IP_ADDRESS>:8080 for process.env.FIRESTORE_EMULATOR_HOST same failure

DEBUG="digin:*" node_modules/.bin/babel-node firestore.js
  digin:firebase:admin trying to connect to firebase on <IP_ADDRESS>:8080 +0ms
watchdog timed out!

from container
 docker exec -it reverent_ishizaka /bin/bash

curl

root@e4172f6a312d:/# curl http://<IP_ADDRESS>:8080
Ok

netstat (which has been replaced by the ss command)

root@e4172f6a312d:/# ss -lntp
State                    Recv-Q                   Send-Q                                       Local Address:Port                                        Peer Address:Port
LISTEN                   0                        4096                                               <IP_ADDRESS>:8080                                             <IP_ADDRESS>:*                       users:(("java",pid=40,fd=97))
LISTEN                   0                        4096                                               <IP_ADDRESS>:40849                                            <IP_ADDRESS>:*                       users:(("java",pid=40,fd=96))
LISTEN                   0                        50                                                 <IP_ADDRESS>:43897                                            <IP_ADDRESS>:*                       users:(("java",pid=40,fd=44))

Misc
Using the second setup --host=<IP_ADDRESS>:8080 the admin.js test case actually works whereas the firestore.js sample doesn't work, this points to a possible issue with the firestore sample, since it is really very simple and mostly lifted from examples in the documentation it could be that  "@google-cloud/firestore" doesn't pick up the FIRESTORE_EMULATOR_HOST env variable by itself.

Alternatively you can try using host networking when you launch the docker containers so that you aren't having to traverse a network interface.
The command would change to be
docker run -it --net=host google/cloud-sdk gcloud beta emulators firestore start --host-port=<IP_ADDRESS>:8080

Then the emulator would bind to the same localhost as your host system.

@BenWhitehead using --net=host results in a successful curl command when using --host-port=<IP_ADDRESS>:8080 admin.js  sample does work, firestore.js still fails :(

firestore.js is a slightly improved version of the example in the README (I switched from console to debug and added  a timeout to have faster feedback)

@jeantil Just to make sure, does export FIRESTORE_EMULATOR_HOST=<IP_ADDRESS>:8080 work when you actually set it to listen to <IP_ADDRESS>? The SDKs may not like <IP_ADDRESS> as the destination host since that would be unrouteable. If that's the case, we can fix the message printed by the Firestore emulator on output.

Closing this due to lack of update. @jeantil feel free to ping us and we can re-open.


Ability to customize env for requests

User should be able to set env variables per request with do_request method call.

Do you mean customize the rack env hash? If so I'm not a fan. RAD is an integration level tool, so playing around with the env isn't something I want add.

@oestrich how would one set HTTP_AUTHORIZATION env if i wanted to test routes that require basic auth?  Here's an example of what i'm trying to do:
resource 'Users' do
  #header 'HTTP_AUTHORIZATION'<EMAIL_ADDRESS>"password")

  before do
    @user = FactoryGirl.create :user, email<EMAIL_ADDRESS>password: 'password'
    request.env['HTTP_AUTHORIZATION'] =<EMAIL_ADDRESS>"password")
  end

  get "/admin/api/v1/users" do
    example "listing users" do
      do_request
      status.should == 200
      response_body.should == {users: [{users: @user}]}.to_json
    end
  end
end

This returns a 401. However, using the standard Rspec DSL, the tests actually pass.

@kareemshahin we have done this in the past, I think you'll want to customize your client via config.client_method

You want to use the header DSL.
header "Authorization", :basic_auth

let(:basic_auth) do
  ActionController::HttpAuthentication::Basic.encode_credentials(user.email, "password")
end

thank you @oestrich, silly mistake on my behalf. i was using the wrong header


Better error when tibble is grouped in gt and fx table

If table is provided groupped throw warning and ungroup


DateAndList datatype doesn't support datetimestamp without milisec with zoneID(2015-02-07T13:28:17+00:00)

Sending 2015-02-07T13:28:17+00:00(when not including milisec) for the last_updated parameter in our questionnaire API (using hapi library DateAndList type) might cause hapi to return an error. It seems DateAndList might not expect time zones without milisecond.
{
"resourceType": "OperationOutcome",
"issue": [
{
"severity": "error",
"code": "processing",
"diagnostics": "HAPI-1883: Invalid date/time format: "2015-02-07T13:28:17 00:00": Expected character '.' at index 19 but found "
}
]
}
Expected behavior
it should accept the zone offset without milisecond precision as well.
Screenshots

Environment (please complete the following information):

20.0.0
OS: mac
Browser : postman

As per HL7 FHIR specification given in to below URL "dateTime" data type should support Format : YYYY-MM-DDThh:mm:ss+zz:zz  . We had seen current HAPI FHIR implementation is always expecting millsec if we pass +zz:zz ( timezone) component as a input.
https://www.hl7.org/fhir/R4/datatypes.html#dateTime

@jamesagnew any more update on this issue?

You need to properly escape the + character, it's being correctly treated as a space by the server. I'm surprised that whatever testing UI you're using in that screenshot (postman presumably?) isn't doing that for you automatically but it clearly isn't since the error shows a space character where the + was.
Replace the + with %2B and I'd assume it should work.


Bug Report: astream_events fails when tool returns a dictionary

Checked other resources

[X] I added a very descriptive title to this issue.
[X] I searched the LangChain documentation with the integrated search.
[X] I used the GitHub search to find a similar question and didn't find it.
[X] I am sure that this is a bug in LangChain rather than my code.
[X] The bug is not resolved by updating to the latest stable version of LangChain (or the specific integration package).

Description
When using astream_events with an agent that has multiple tools, if one of the tools returns a dictionary containing an answer and source documents, the streaming process fails. However, the same setup works correctly in non-streaming mode.
Steps to Reproduce

Set up an agent with multiple tools, including one that returns a dictionary.
Use astream_events to stream the agent's output.
Observe the error when the tool returning a dictionary is called.

Code to Reproduce
import asyncio
import json
import os
import random
import warnings
from typing import Type, Dict, Any

import boto3
from dotenv import find_dotenv, load_dotenv
from langchain.agents import create_react_agent, AgentExecutor
from langchain.prompts import PromptTemplate
from langchain.tools import BaseTool
from langchain_aws import ChatBedrock
from langsmith import Client
from pydantic import BaseModel, Field

# Suppress warnings
warnings.filterwarnings("ignore")

load_dotenv(find_dotenv())

reproduce_problem = True

boto3_session = boto3.Session(
    aws_access_key_id=os.environ["BEDROCK_AWS_ACCESS_KEY"],
    aws_secret_access_key=os.environ["BEDROCK_AWS_ACCESS_SECRET"],
    region_name=os.environ["BEDROCK_AWS_REGION"],
)
model = ChatBedrock(
    model_id="anthropic.claude-3-5-sonnet-20240620-v1:0",
    client=boto3_session.client("bedrock-runtime"),
    streaming=True,
    model_kwargs={
        "temperature": 0,
    },
    tags=["agent"],
    metadata={"streaming": True},
    callbacks=None,
)

class CatHidingInput(BaseModel):
    query: str = Field(default="", description="Query about where the cat is hiding")

class CatHidingTool(BaseTool):
    name = "where_cat_is_hiding"
    description = "Use this tool to find out where the cat is hiding right now."
    args_schema: Type[BaseModel] = CatHidingInput

    async def _arun(self, query: str) -> str:
        return random.choice(["under the bed", "on the shelf"])

    def _run(self, query: str) -> str:
        return random.choice(["under the bed", "on the shelf"])

class GetItemsInput(BaseModel):
    place: str = Field(..., description="The place to look for items")

class GetItemsTool(BaseTool):
    name = "get_items"
    description = "Use this tool to look up which items are in the given place."
    args_schema: Type[BaseModel] = GetItemsInput

    async def _arun(self, place: str) -> Dict[str, Any]:
        return self._get_items(place)

    def _run(self, place: str) -> Dict[str, Any]:
        return self._get_items(place)

    def _get_items(self, place: str):
        items = ""
        if "bed" in place:
            items = "socks, shoes and dust bunnies"
        elif "shelf" in place:
            items = "books, pencils and pictures"
        else:
            items = "cat snacks"
        answer = f"The items in the {place} are: {items}"
        source_documents = [
            {
                "page_content": f"Items found in {place}: {items}",
                "metadata": {"source": "GetItemsTool", "place": place},
            }
        ]
        # xxxx: this is the issue
        # it doesn't work in streaming if i return a dictionary which works in non-streaming mode in my application
        if reproduce_problem:
            return {"answer": answer, "source_documents": source_documents}
        else:
            # it works if i return one string
            return json.dumps({"answer": answer, "source_documents": source_documents})

client = Client()

REACT_PROMPT = PromptTemplate.from_template(
    """You are an AI assistant helping to find a cat and items in its location.
Human: {input}
AI: To solve this task, I have access to the following tools:

{tools}

The available tool names are: {tool_names}

Let's approach this step-by-step:

Always use the following format:

Thought: Consider what to do next
Action: the action to take, should be one of [{tool_names}]
Action Input: the input to the action
Observation: the result of the action
... (this Thought/Action/Action Input/Observation can repeat N times)
Thought: I now know the final answer
Final Answer: the final answer to the original input question

{agent_scratchpad}"""
)

async def run_agent_streaming():
    tools = [GetItemsTool(), CatHidingTool()]
    agent = create_react_agent(model, tools, REACT_PROMPT)
    agent_executor = AgentExecutor(
        agent=agent,
        tools=tools,
        return_intermediate_steps=True,
        return_source_documents=True,
        handle_parsing_errors=True,
    ).with_config({"run_name": "Agent"})
    async for event in agent_executor.astream_events(
        {"input": "where is the cat hiding? what items are in that location?"},
        version="v2",
    ):
        kind = event["event"]
        if kind == "on_chain_start":
            if event["name"] == "Agent":
                print(
                    f"Starting agent: {event['name']} with input: {event['data'].get('input')}"
                )
        elif kind == "on_chain_end":
            if event["name"] == "Agent":
                print()
                print("--")
                print(
                    f"Done agent: {event['name']} with output: {event['data'].get('output')['output']}"
                )
        elif kind == "on_chat_model_stream":
            content = event["data"]["chunk"].content
            if content:
                print(content, end="|")
        elif kind == "on_tool_start":
            print("--")
            print(
                f"Starting tool: {event['name']} with inputs: {event['data'].get('input')}"
            )
        elif kind == "on_tool_end":
            print(f"Done tool: {event['name']}")
            print(f"Tool output was: {event['data'].get('output')}")
            print("--")

async def run_agent_non_streaming():
    tools = [GetItemsTool(), CatHidingTool()]
    agent = create_react_agent(model, tools, REACT_PROMPT)
    agent_executor = AgentExecutor(
        agent=agent,
        tools=tools,
        return_intermediate_steps=True,
        return_source_documents=True,
        handle_parsing_errors=True,
    ).with_config({"run_name": "Agent"})
    result = await agent_executor.ainvoke(
        {"input": "where is the cat hiding? what items are in that location?"}
    )
    print(f"Agent output: {result['output']}")
    print("Intermediate steps:")
    for step in result.get("intermediate_steps", []):
        print(f"- Action: {step[0].tool}")
        print(f"  Input: {step[0].tool_input}")
        print(f"  Output: {step[1]}")

if __name__ == "__main__":
    print("Running streaming version:")
    asyncio.run(run_agent_streaming())
    print("\nRunning non-streaming version:")
    asyncio.run(run_agent_non_streaming())

Error Message
pydantic.v1.error_wrappers.ValidationError: 2 validation errors for HumanMessage
content
  str type expected (type=type_error.str)
content
  value is not a valid list (type=type_error.list)

Expected Behavior
The astream_events method should handle tool outputs that return dictionaries, just as it does in non-streaming mode.
Actual Behavior
The streaming process fails with a ValidationError when a tool returns a dictionary.
Workaround
Returning a JSON string instead of a dictionary from the tool allows the streaming to work:
return json.dumps({"answer": answer, "source_documents": source_documents})

Environment

LangChain version: 0.3.0
LangChain Core version: 0.3.2
Python version: 3.11
Pydantic version: 2.9.2
Pydantic Core version: 2.23.4
langchain-aws: (please specify version)
boto3: (please specify version)

Model:

AWS Bedrock
Model ID: anthropic.claude-3-5-sonnet-20240620-v1:0

Operating System: (Please specify your OS)
Additional Context
This issue only occurs in streaming mode when using astream_events. The same code works correctly in non-streaming mode. It appears that the astream_events method is not properly handling dictionary outputs from tools, possibly due to an issue in the event conversion process.
The problem is reproducible with AWS Bedrock using the Claude 3 Sonnet model, but it may also affect other LLM providers and models.

i added reproducible code in this gist
https://gist.github.com/sharrajesh/da783f07cbb9daa5373f9a47b649a514

I found a workaround. Please feel free to close.
On Tue, Dec 24, 2024, 11:04 AM dosubot[bot] @.***>
wrote:

Hi, @sharrajesh https://github.com/sharrajesh. I'm Dosu
https://dosu.dev, and I'm helping the LangChain team manage their
backlog. I'm marking this issue as stale.
Issue Summary:

The issue involves a bug in the astream_events function when used
with an agent with multiple tools.
The streaming process fails if a tool returns a dictionary with an
answer and source documents.
This issue does not occur in non-streaming mode and persists even
after updating to the latest version.
You provided additional context with gists demonstrating the
problem, specifically with create_react_agent.

Next Steps:

Could you please confirm if this issue is still relevant to the
latest version of the LangChain repository? If so, feel free to keep the
discussion open by commenting here.
Otherwise, this issue will be automatically closed in 7 days.

Thank you for your understanding and contribution!
—
Reply to this email directly, view it on GitHub
https://github.com/langchain-ai/langchain/issues/26763#issuecomment-2561258214,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACHN2P66JWVZUPO6UMTSSD2HGAZRAVCNFSM6AAAAABOVK2436VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNRRGI2TQMRRGQ
.
You are receiving this because you were mentioned.Message ID:
@.***>


DCOS-12063: Changing the labels for healthchecks DSL filter

⚠  Depends on #1564

This PR renames health: health-check attribute to:

health:healthy -> is:healthy
health:unhealthy -> is:unhealthy
health:na -> no:healthchecks
health:idle -> Removed

retest this please

you failed, retest this please again

✨ Awesome


fix:typo in startup edmonton card

Fixed typo in startup edmonton card
This pr fixes #247

@all-contributors add @PrathameshSonje for code


SomePythonThings.ZipManager version 4.2.0

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?

[x] Does your manifest conform to the 1.0 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

@ItzLevvie  I just removed the .0 from the 4.2.0 as you suggested, and now Azure pipelines don't accepyh the manifest as a valid manifest


How can I use the Containers test with a Swarm cluster?

Good evening everyone,
Today I have a Swarm Hybrid cluster with Linux and Windows, my Jenkins pipelines are configured to run on Windows, but I would like to use SQL Server with Linux container on my linux nodes, is there any way to use Stack Deploy together with the testContainer to ensure that the tests are performed on the correct nodes?

Hey @viniciusxyz,
as of now, Testcontainers doesn't support Docker-Swarm. We might add it in the future (maybe as part of the Docker-Compose support or something distinct altogether), but we don't have any concrete plans for this.

thanks for the quick response and great work on the project!


Android - Small White Icon Issue

What I'm trying to do is format the notification icons for React Native Android and is running into an issue where a small white square will appear on the notification banner (screenshot).

This is what I'm sending remotely
data: {
        key: 'major',
        another_one: 'another value',
        custom_notification: {
            title: 'Title of your push notification',
            body: 'Body of your push notification',
            icon: 'icon_small',
            large_icon: 'ic_launcher',
            show_in_foreground: true
        },
    }

It's strange because on top bar the icon will show correctly, however, when you roll down the notifications and look at the banner there is a white square instead. I've tried changing the icon to different sizes and no luck. When I change the icon value being sent to ic_launcher, it will show up with no color. Is there something I missed? Anyone else running into this issue?
When icon is set to ic_launcher:

What verion of RN and react-native-fcm are you running?
RN: 0.40.0
react-native-fcm: 4.0.0
What device are you using? (e.g iOS9 emulator, Android 6 device)?
Android - Galaxy S5
Is your app running in foreground, background or not running?
Issue shows up on each of these states.

perhaps that icon has to be white with transparent background? just like the icon limitation after lolipop

@jnrepo any updates?

close due to inactivity


How do i do?

Hello, i found this on github today, and i'm a RF online player.
How do i do, to use this program? i never use .ahk

oh man... my bad, too busy irl , i did not even noticed. Anyway, just in case your still checking this out, i'll try my best to recall, these macros/clickers were (badly) written specifically for an old server we used to play with. Probably the easiest to explain are the RFO_AFK_Tools.ahk which allow you to spam "x" for looting and allows an accretian striker to launch its 2 skills (doom blast? chain rocket? can't remember) if their set in "F1" and "F2" while afk and the Mysterious_Box_Clicker.ahk that just spams "F10" we used this to open leon boxes or any stackable items that need to be right clicked.
While the iggy_Xchanger.ahk and upgrader_Clicker.ahk are macros that deals with item combination on Hero (Lotan? Lotar?)  that allows Hero combination of iggy and favor talics in exchange for weapon/armor upgrader, so I think this is server specific and also drag the Hero Combination hud to the top left corner in order for this clicker to work properly.
I think you need to install autohotkey in order to lauch ahk files or convert them to exe to distribute elsewhere.
Anyway, this is a long shot and I hope it helps.

awfully explained, still explained.


Could you supporting OS ventura? plz...

Hi, Mr.slashlos !!

After the update, the temperature is irregular when use He3 in my macbook.
And layout gets tangled when use "stage maneger"
sometimes, my mouse pointer disappears.

thank you so much.
if you can,,,
could you supporting OS ventura? plz...

Yes it's on the radar; you mean after you upgraded the OS I presume; will do same with the current build to see what happens...

I hope everything goes well  :D
p.s  Occasionally, the issue of increasing temperature has also been identified.

I'be been running a few week now fine.  I am not familiar with Stage Manager but Helium as a floating browser might be incompatible by its nature. I do not see otherwise performance (heat) impact on a M1pro.  I just installed, bo changes made so perhaps there's something I need to do...

p.s., development is moving to Sonoma 14.2.1 (23C71).


Long function definitions should be displayed using shortened version (unless --verbose option is given)

For example: l() { if [[ -n "$1" ]]; then ...; }   (7 more lines).

Depends: #49

This is not a priority. Closing.


Support relationships via links to content items in Rich text elements

Motivation
We already support most kinds of relationships among GraphQL nodes. One of the two remaining kinds is relationships based on links to content items in Rich text elements.
Proposed solution
Implement the relationships similarly to the decorateItemNodeWithLinkedItemsLinks method.

Implemented in v3 and described in Readme