Version 2.6 release was not backwards compatible

I'd like us to be more careful when making changes and cutting releases as minor releases. Version 2.6 contained the following change:
https://github.com/uber/jaeger-client-go/pull/129
This change contains a renaming of ClientOptions to Options. I think the renaming was a good step, but when we make changes like this, we should bump the major version.
Can we enforce this in reviews @black-adder and @yurishkuro?

Yes, I thought those types would never actually make it to the client code, but I was wrong, it wasn't worth the hustle.

Unfortunately cutting the release as 2.6 has caused many services to hit failures when upgrading dependencies (I've run into this myself).


relax the malformed CE event to 4XX instead of only 415

Changes

Currently a malformed event is required to be handled as 400 error code. We should relax this to 4XX so that various libraries that may return more specific error codes if necessary. One example is the 415 error code that's returned by cloudevents go-sdk for missing ce-version.
Spec: https://github.com/knative/specs/blob/main/specs/eventing/broker.md

If a Broker receives a produce request and is unable to parse a valid CloudEvent, then it MUST reject the request with HTTP status code 400 Bad Request

/kind

Fixes #

Release Note

Docs

Seems reasonable to me. I'm not sure I see the value in mandating it only be 400 when really all that matters is that it's in the 4xx range. If we had a very specific error condition in mind, then I can see being more picky about the error code to help the possibility of some kind of interop error recovery.

/LGTM

ping @ronavn @bsnchan

/approve


Cross Refences problem

Environment

Binary Ninja Version: DEV <IP_ADDRESS> Personal
OS: Linux
OS Version: Debian 12
CPU Architecture: x64

Bug Description:
Hello,
There is a small synchronization problem between the visualization of code references depending on the different selected languages.
Steps To Reproduce:
Select a variable, display it as a pointer to retrieve the name of the target variable. If you are in Disassembly, you can see its name each time I see this address in the program. In HLIL, I will only see it in the function where you did the renaming.
Tks for the support.

Could you possible share a screenshot or even better a binary?

Sorry, I can only share screenshots...
Code references in while using the HLIL view:

When I change to the Disassembly view:


Enable Github Discussions

Hi @f1stuff - this is a really awesome project!
I've managed to get it up and running on macOS. I can see some historic data already, but am really keen to test the live timing in a little bit for the Miami Quali. Would love to contribute to the development of this project if you have any ideas or need help with anything.
Wanted to also suggest that you set up github discussions for this repo - just to maybe get a conversation going :)
Thanks

Hi, I have a question. I want to do a project like this (a dashboard with real time data and maybe team radio during the race of course) but I don't know where take the API.
So, anyone can tell me where get the API to develop this projects? Thanks

Hi @Felice-Copp56, maybe check out Fast-F1


Option to strip quotes around keys

Would you consider adding an option to strip quotes around keys in the output? Is terraform.FormatValue responsible for the quotes?
re := regexp.MustCompile(`(\s*)"([^"]+)"(\s*)(=.*)`)
hcl = re.ReplaceAllString(hcl, "$1$2$3$4")

just before returning from yamlToHCL seems to work.

Yes the quotes are added by FormatValue – however I had to copy that package over to this codebase anyway, as they made that function private in the core Terraform repository. So we can change it to strip quotes here. I'd rather do that than use a regex to strip them out.

Yes, that would be better. I didn't realise that chaining terraform.FormatValue was an option.

Thanks. Awesome work :100:


Add additional packages/modules/themes at build time by selecting with browser extension.

Is your feature request related to a problem? Please describe
Some issues are related to multiple projects interacting with each other or may have undefined dependencies (those not in composer.json). These additional modules/themes would need to be installed at the same time to fully work on the issue.
Describe the solution you'd like
One option. In the extension, you should allow selecting additional drupal projects/packages to install along with it.
Describe alternatives you've considered
Instruct users to use the terminal to add the additional packages using composer.
Additional context
This may be implemented in a similar way that https://simplytest.me/ allows you to select additional modules/themes.

That is a great idea, thank you!
I'd love making it easier for users to use a UI for choosing multiple projects for 1 workspace.
For now - users could install it manually after the initial process finishes.
The issue of adding such interface, since we're currently using a browser extension, pressing something out of the extension makes the extension disappear :(
I have another issue https://github.com/shaal/DrupalPod/issues/16, it's very possible when that UI is ready - adding this functionality would be a perfect fit.

Not a perfect option, but throwing it out there...
To avoid the complication of an autocomplete (external requests). What about adding a text field that would just accept a list of composer packages. Like drupal/pathauto:^2:0 drupal/token?


Database cache and table cache timeout set to 0 or -1 crashes when creating dataset

Database connection cache and table cache timeout set to 0 or -1 crashes when attempting to create a dataset.
How to reproduce the bug

Create a new Database connection. In my case of type Amazon Redshift.

Go to step 3 and select Performance.

Set Schema cache timeout to 0 seconds.

Set Table cache timeout to 0 seconds.

Save the Database connection.

Go to Datasets in the top menu.

Click + Dataset.

Select the mentioned database.

Select a schema.

This will throw an exception with the following text:

There was an error loading the tables: Unexpected error occurred, please check your logs for details

If I set the cache timeouts to a positive integer, the tables load well.
Unfortunately the Docker Compose logs show nothing relevant.
Expected results
I expect the tables for the schema to load, despite the cache timeout being set to 0.
The larger question: How do you disable the schema and table cache entirely? The UI does not indicate how to do that. Setting the value to 0 or -1 is my best guess.
Actual results
Loading tables will throw an exception with the following text:

There was an error loading the tables: Unexpected error occurred, please check your logs for details

Unfortunately the Docker Compose logs show nothing relevant.
Screenshots

Environment

Chrome. Version 117.0.5938.92 (Official Build) (64-bit).
Superset 3.
Docker Compose latest build, as of Oct 4, 2023.

Additional info
The browser sends an API request:

/api/v1/database/6/tables/?q=(force:!f,schema_name:public)

This fails with status 422 Unprocessable Content.

I don't have a redshift instance to test, but maybe @cbuffevant (from the rolodex, thanks for signing up!) might have some insight here.

I was able to replicate it with a Redshift Serverless cluster, using Superset 3.0.2. I can take a deeper look...

After removing the cache time out values, the error persists...

Oh, interesting. Thanks for validating. I wonder if putting in a reasonable default clears the error? In other words are just 0/-1 problematic, but 60 or 600 are fine? Thanks for looking into this!

Yes, I can confirm that setting timeout value to 1, works fine. The problem seems to be related with values <= 0.

CCing @betodealmeida or @sadpandajoe in case they might be interested in this one.


Hide empty git partial when no repo is found

Fixed on https://github.com/repejota/psh/commit/8a291bc3201d6980c38cf6d36dc6678dab4a4c6f


ReSharper 2018.3 Support?

Is this 2018.3, by chance?  I do not see it at present.

Working on it. Is anyone using Rider now and then?

Currently waiting for approval: https://plugins.jetbrains.com/plugin/11717-testlinker
There is now also a Rider version: https://plugins.jetbrains.com/plugin/12022-testlinker

Great, thank you!  I didn't see the previous question until now unfortunately.  I did try Rider but had problems with its multimon setup.  I should try it again to see if I can get better luck. :)

Quick confirmation here that it works and have it installed.  All is right in the world again. 😁
Thank you for taking the time to make this project and also to jump through the hoops to ensure that it is continuously updated. 👍

@Mike-EEE part of my work basically, but glad you like it :)


TestCafe: ManageAccounts

Please do work for this task in a branch called issue-190.

Page unnecessary/not fully implemented yet?


[Feature]: add LOGO in Footer

🚀 Feature Request
📝 Feature Description
I would like to add logo  to the right side in footer of each page to make it look more appealing.

Please this assign this issue to me under gssoc-ext and hactoberfest

Assign this to me.


Parse Greensboro Message for Initiatives

Here is Greensboro's  City Manager message - https://www.youtube.com/watch?v=u8yQQtatToU
I need to watch this and parse meaning / Greensboro's goals/initiatives into a NC OpenPass Challenge that fits our templates here: https://docs.google.com/document/d/1MhoT2MCrjgWScfgHkdtKlFGpgQEm0iyKU5DhJ-_0Q-E/edit
The idea is to parse out what goals we can and compare them to Wake/Raleigh/Durham/ChapelHill goals that align nicely

I recruited a developer, Randy, who lives in Greensboro.  Recommended that he contact us.

Goal #1: Economic Development. Ensure strong functioning of City services and resources to positively influence and support economic and community development, including making downtown Greensboro a destination location to enhance the economic vitality of the entire city.
Goal #2: Infrastructure. Protect, maintain and enhance the City's public infrastructure to improve the quality of life in Greensboro that is sustainable and cost effective.
Goal #3: Public Safety. Promote public safety and reduce crime by being visible and active in the community and by being responsive to all residents. Continue to work to create a proactive environment that encourages, educates, and develops programs in collaboration with all City departments. GM 911, GBO Fire Department, GBO Police Department
Goal #4: Customer Service. Create a positive customer experience and employee workforce where the customer is respected, appreciated, and valued. Attract, develop, and retain talented leadership throughout the city. Includes Development of enhanced methods of communications and outreach with citizens and businesses. Open Data Portal, City Career Fairs, Quarterly PM Report.
Goal #5. Fiscal Stewardship. Strengthen efficiency and improve effectiveness of City programs to optimize service delivery while promoting transparency and accountability to the public. Budget Development, Effective and efficient use of City resources (Program inventory).
From Jim Westmoreland, Greensboro City Manager.


Mass Blueprint integration

So far pretty much nothing in Mass is exposed to BP except for Mass Agents/actor pooling. It's definitely primarily intended to be used by C++ programmers  but I don't see why it can't be exposed to BP to an extent. Full on BP ticking would kind of defeat the purpose so it would likely be limited to event-ish gameplay code.

[x] Spawning arbitrary entities from Entity Configs
[x] Basic core fragment changes (transform, force etc)

For the future...

[x] BP-able processors (maybe just observers for perf reasons?)

[x] Query config

[ ] Multiple queries

[x] Processor/phase setup
[ ] Deferred actions

[x] Arbitrary fragments get/set

[ ] Shared fragments

[ ] Arbitrary tags get/set

Perhaps some more random extra module-specific functionality if it ever seems useful.

Processor/phase setup already exposed (thankfully)

BP observers and some messy but usable fragment getting is in!

Instanced struct support is in 5.1!!!!!!!!!! Weeeee!!


Bug/#15256

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Update docs

Made some small changes to the qiskit API documentation in line with
https://github.com/CQCL/tket/pull/723.

Use borland pygments
sphinx-copybutton
use grey instead of blue for the API documentation.
Fix outdated docstring for IBMQEmulatorBackend (spotted by Yoshi)

on 4. ...I have updated the docstring but I cannot find the change in the docs if I build locally. Did I forget something?

Should I re-run the failed jobs and merge this if everything passes? I noticed you made a separate PR which is now closed.

I only made the other PR for your question, I think you just need to update this from develop.


GEODE-8877: Configurable UDP membership address

This PR allows to bind membership endpoints to all interfaces via the --bind-address attribute. When a wildcard address is introduced with that parameter, the membership UDP traffic will be bound to localhost due to JGroups does not allow to bind to wildcard addresses.
If a different address for UDP traffic needs to be used, it can be specified with the new parameter called membership-bind-addresss.
I have not squashed the commits of the PR because I think it can be useful for reviewers. The two first commits contains the functionality I mentioned previously, while the three next commits contains some code improvements identified after the review of my first PR for this ticket.

Please see 2 recommended re-writes in the doc file geode-docs/tools_modules/gfsh/command-pages/start.html.md.erb.

Done, thanks Dave!

Thanks @mhansonp & @boglesby , I have added a commit after your comments.

@davebarnes97 Could you check if your "request for changes" can be removed? Thanks

Thanks @mhansonp & @boglesby , I have added a commit after your comments.

I still approve of your changes. Thanks for making the suggested changes as well, they look good.

I've read the ticket and made a first pass over the diffs, but I don't understand why StartLocatorCommandWorkingDirectoryTest and StartServerCommandWorkingDirectoryTest need to be deleted in order to support configurable UDP membership address?

It is not needed. Its a code improvement I identified when implementing the functionality. Notice what I wrote on the PR description:

I have not squashed the commits of the PR because I think it can be useful for reviewers. The two first commits contains the functionality I mentioned previously, while the three next commits contains some code improvements identified after the review of my first PR for this ticket.

Long story: I observed that adding a new parameter in start locator or start server commands had an impact on all tests of StartLocatorCommandWorkingDirectoryTest and StartLocatorCommandWorkingDirectoryTest. Those tests were just testing the working directory resolution, it has no sense they were impacted. So I refactored that code in StartLocatorCommand & StartServerCommand extracting the working directory resolution code to a new method to be able to test it independently. You can review just what I changed for this in this commit:
4cd39cc Refactor StartMemberUtils.resolveWorkingDir

I have added an empty commit to retrigger CI because test were executed again today and one test failed unexpectedly. Last commit was done 21 days ago and tests were ok.

Tests were executed again today and one test failed unexpectedly. Last commit was done 21 days ago

It's always a risk to merge based on tests that passed long time ago (sometimes even short time ago -- a lot can change on develop in a short time).  We recently had a commit merged that immediately broke develop, and found that PR checks had last been run 4 weeks earlier.  To reduce this risk, I will be re-executing tests weekly to improve confidence that PRs have been tested against something more closely resembling the latest develop.

Tests were executed again today and one test failed unexpectedly. Last commit was done 21 days ago

It's always a risk to merge based on tests that passed long time ago (sometimes even short time ago -- a lot can change on develop in a short time). We recently had a commit merged that immediately broke develop, and found that PR checks had last been run 4 weeks earlier. To reduce this risk, I will be re-executing tests weekly to improve confidence that PRs have been tested against something more closely resembling the latest develop.

Agree, but then PRs should be rebased against develop branch, right?
In my case, I have seen there are conflicts I have to solve, so Im going to rebase anyway...

then PRs should be rebased against develop branch, right?

PR checks do automatically rebase against latest develop, so just re-executing them is sufficient.  However when there is a conflict then they will not run at all, so it's a good idea to manually rebase especially if GitHub is also showing conflicts.

I have removed two of the code improvements not related with the feature to separated tickets and PRs. I hope this will make the review of this PR easier.


Improvements to keyboard support

Is your feature request related to a problem? Please describe.
We're very happy that keyboard support has been added to react-easy-crop, as it removed the need for our custom wrapper around it, but we hope we can introduce a couple of tweaks to improve things.
Describe the solution you'd like
Currently (v5.1.0), using the arrow keys while the cropper is focused causes scrolling because preventDefault() isn't being called on the event. It would be better if preventDefault() were called, to prevent scrolling while moving the crop area.
Also, as there is a single fixed step size it can be hard to finely tune the desired area. It seems technically possible to work around this by zooming in further than desired, moving by the fixed step size and then zooming back out and correcting, but this is cumbersome and unintuitive. It would be nice if a modifier key could scale the step size down (say, by a factor of 5) to move the crop area in smaller increments. Our previous wrapper used the shift key for this finer control.
Describe alternatives you've considered
Our previous alternative was to wrap the cropper with our own custom keyboard interaction handing, but as react-easy-crop supports keyboard interaction natively we'd like to avoid the need for that. As of 5.1.0 we still have a slim wrapper just to cancel the scrolling caused by the arrow keys, and have accepted the slight regression in our interface caused by the lack of finer control, but it'd be nice to not need either.
Additional context
We'd be happy to make a pull request for these changes if you're happy with the ideas.

If you have ideas how to implement your new feature, please share!
We could build on JGuardiola95's commit https://github.com/ValentinH/react-easy-crop/pull/570/commits/5f6a353ead6afa3ad04c0782779b64ffc0d1d110 to add preventDefault() in the case  blocks in onKeyDown, and multiply step by 0.2 before the switch if shift is pressed.

I like this idea. You are very welcome to create a PR, I'll be happy to review it 🙂

The improvement was released in https://github.com/ValentinH/react-easy-crop/releases/tag/v5.2.0.


windows-color-fix: Changed foreground and background colors

On windows, the 16 colors visible to the console map out like so:
0 -> backgroundColor
1 -> blue
2 -> green
3 -> cyan
4 -> red
5 -> magenta
6 -> yellow
7 -> lightWhite
8 -> lightBlack
9 -> lightBlue
10 -> lightGreen
11 -> lightCyan
12 -> lightRed
13 -> lightMagenta
14 -> lightYellow
15 -> foregroundColor

As you can see black (which maps to base02 in solarized) and white
(which maps to base2 in solarized) are not visible, meaning these colors
are missing on windows. To remedy this I changed the background colors
to base02 and foreground color to base2 to allow windows to use all 16
colors of solarized.

I am unable to test the effects this has on macOS and Linux machines. So I do not know if this breaks the theme for them.
Obviously this is not the most visually pleasant background and foreground choices, so if there was a way to only have these changed values when running on windows, that would probably be the best. I am not a Node.js programmer, so I don't know if that is possible or how to do it.


Public projects should also have members

Why is the member list and the ability to add members not showing up on a public project? See screenshot.

Member list and "Add User" shows up on public projects if you're admin, but not if you're a random stranger who can view the project only because it's public. I think that's the way it should be, no?

Yeah because the button is not really tied to project visibility but admin access

Yeah. You have to be a project member to do that.
On Thu, Feb 8, 2018 at 12:20 PM, Cyril Ologho<EMAIL_ADDRESS>wrote:

Yeah because the button is not really tied to project visibility but admin
access
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/chanzuckerberg/idseq-web/issues/628#issuecomment-364236214,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABoAQux4VpGIhsqoTF5fJxpkImLwQsyvks5tS1cLgaJpZM4R-wwm
.

ok. That makes sense. I would think you would want to see the total number of members but that doesn't matter. Closing this out! Thanks guys.


[Simplified Collect][CLEAN UP][LOW] Standardize on Workspace wrapper

Details

Fixed Issues

$ https://github.com/Expensify/App/issues/37898
PROPOSAL:
Tests

That's a very broad cleanup, so to verify that nothing is broken would require:
For not found case:

Just use a link with a random name for the proper file route, for example /workspace/dssaddssdaads/categories, this should display and unchanged not found message.

For admin case:

Get the policy id from a proper page, which has a new wrapper with accessVariants including admin
Modify this policy inside of the onyx to have a random role inserted

    Onyx.merge('policy_8F4B1CFAD82C0294', {
        role: 'test',
    });

A proper variant of a not found page should be displayed

For paid case:

Get the policy id from a proper page, which has a new wrapper with accessVariants including admin
Modify this policy inside of the onyx to have a random role inserted

    Onyx.merge('policy_8F4B1CFAD82C0294', {
        role: 'test',
    });

A proper variant of a not found page should be displayed

For feature flag case:

Just hardcode the false feature flag and verify if the proper not found page variant is being displayed

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

Offline tests

QA Steps

[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 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] 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

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

Reviewer Checklist

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

[ ] I verified the steps for local testing are in the Tests section
[ ] I verified the steps for Staging and/or Production testing are in the QA steps section
[ ] 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)
[ ] 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)

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

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

[ ] 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
[ ] I verified proper code patterns were followed (see Reviewing the code)

[ ] 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).
[ ] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[ ] I verified that comments were added to code that is not self explanatory
[ ] 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.
[ ] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
[ ] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[ ] 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)
[ ] 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.
[ ] I verified the JSDocs style guidelines (in STYLE.md) were followed

[ ] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[ ] I verified that this PR follows the guidelines as stated in the Review Guidelines
[ ] 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)
[ ] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[ ] 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
[ ] If a new component is created I verified that:

[ ] A similar component doesn't exist in the codebase
[ ] All props are defined accurately and each prop has a /** comment above it */
[ ] The file is named correctly
[ ] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[ ] The only data being stored in the state is data necessary for rendering and nothing else
[ ] 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)
[ ] 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)
[ ] All JSX used for rendering exists in the render method
[ ] 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

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

[ ] 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

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

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

[ ] 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.
[ ] 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)
[ ] 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.
[ ] 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.
[ ] 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:

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

[ ] 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.
[ ] 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.
[ ] I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

Bug: NoFoundPage appear briefly then loading, then back to appear again when trying to open not found workspace, for example go to  /settings/workspace/fdfdfdfdfdfdfdfdfdfdfdfdf/categories
https://github.com/Expensify/App/assets/41129870/23df7b13-1459-4fa9-9182-904b4ac79317

We need to edit tests steps to be more clear.
For admin case:

Go to Account Settings > Workspaces > create/open any Collect Workspace with admin role.
From LHN click on Categories.
Open your browser console and write this code with replacing YOUR_WORKSPACE_ID with your workspace ID, then press ENTER (you can roll back by merge role: 'admin').

Onyx.merge('policy_YOUR_WORKSPACE_ID', {
    role: 'test',
});

Verify that NoFoundPage is appeared, and you don't access the page.

For paid case:

Go to Account Settings > Workspaces > create/open any Collect Workspace with admin role.
From LHN click on Categories.
Open your browser console and write this code with replacing YOUR_WORKSPACE_ID with your workspace ID, then press ENTER (you can roll back by merge type: 'team').

Onyx.merge('policy_YOUR_WORKSPACE_ID', {
    type: 'free',
});

Verify that NoFoundPage is appeared, and you don't access the page.

For feature flag case:

Go to Account Settings > Workspaces > create/open any Collect Workspace with admin role.
From LHN click on Categories and copy page URL.
From LHN click on More features and disable Categories feature.
Navigate to disabled feature Categories by the URL you copied in step 2.
Verify that NoFoundPage is appeared, and you don't access the page.

also, please add some Screenshots/Videos, and fill Offline tests QA Steps, if it the same as Tests add it `Same as "Tests"`

Bug: NoFoundPage appear briefly then loading, then back to appear again when trying to open not found workspace, for example go to /settings/workspace/fdfdfdfdfdfdfdfdfdfdfdfdf/categories
Screen.Recording.2024-04-23.at.8.59.10.AM.mov

Yeah, it's also present on the main branch

Reviewing now.

Tested well! And record videos for all cases.
@BrtqKr just small updates still here https://github.com/Expensify/App/pull/40598#discussion_r1575330360 https://github.com/Expensify/App/pull/40598#discussion_r1578269403
Thanks!

We have 2 issues from the previous code before this Standardize, we need to open new issues for it.

issue 1
Bug: NoFoundPage appear briefly then loading, then back to appear again when trying to open not found workspace, for example go to  /settings/workspace/fdfdfdfdfdfdfdfdfdfdfdfdf/categories
https://github.com/Expensify/App/assets/41129870/23df7b13-1459-4fa9-9182-904b4ac79317

issue 2
Native - back button overlapping with stausbar when trying to access page without feature enable, and the not found page is displayed.
https://github.com/Expensify/App/assets/41129870/4f0335cf-082f-4562-a6c6-6e9b3673d8f5

@BrtqKr conflicts

@BrtqKr friendly bump to fix conflicts :)

@BrtqKr friendly bump to fix conflicts :)

Done 🙏 , but I had to adjust the wrapper to handle further customization. Let's get this reviewed and merged before we get more conflicts since this PR is modifying many parts of the app

🚀 Cherry-picked to staging by https://github.com/francoisl in version: 1.4.67-7 🚀

platform
result

🤖 android 🤖
failure ❌

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

@Expensify/applauseleads please QA this PR and check it off on the deploy checklist if it passes.

@BrtqKr @ahmedGaber93 @luacmartins Could you help us how to validate in native apps and mweb?

Onyx.merge('policy_YOUR_WORKSPACE_ID', {
role: 'test',
});

🚀 Deployed to staging by https://github.com/luacmartins in version: 1.4.68-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
failure ❌

🕸 web 🕸
success ✅

🚀 Cherry-picked to staging by https://github.com/francoisl in version: 1.4.67-7 🚀

platform
result

🤖 android 🤖
failure ❌

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

@Expensify/applauseleads please QA this PR and check it off on the deploy checklist if it passes.

@kavimuru Sorry for unclear that.
mWeb/Native apps.
We can test is page access or not by links in mWeb and deeplinks in Native apps.
For admin case: try to open admin feature (categories) for any workspace you don't have admin role for it.
Precondition:  user is Admin in workspace A and member in workspace B.

In Your web browser, go to Account Settings > Workspaces > workspace B (member role) and copy your WORKSPACE_ID from browser URL.
In mWeb/Native apps login with same account, try to open /settings/workspaces/WORKSPACE_ID/categories
Verify that NoFoundPage is appeared, and you don't access the page.

For paid case: try to open paid feature (categories) for any free workspace.
Precondition:  user is Admin in paid and free Workspaces.

In Your web browser, go to Account Settings > Workspaces > free workspace, and copy your WORKSPACE_ID from browser URL.
In mWeb/Native apps login with same account, try to open /settings/workspaces/WORKSPACE_ID/categories
Verify that NoFoundPage is appeared, and you don't access the page.

For feature flag case:  disable any feature (categories) in a workspace, try to open this feature by URL.
Precondition:  user is Admin in paid workspace.

In Your web browser, go to Account Settings > Workspaces > paid workspace > Categories and copy page URL.

In mWeb/Native apps login with same account, try to open the URL you copied in step 1.
Verify that NoFoundPage is appeared, and you don't access the page.

@BrtqKr can you link this comment in tests step, or add it manually for mWeb/Native apps.
For more test videos, see here https://github.com/Expensify/App/pull/40598#issuecomment-2070435765

🚀 Deployed to production by https://github.com/francoisl in version: 1.4.68-3 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


train code

Hello, can you provide the code of model training and related configuration, thank you very much

Thank you for your interest.
I'm sorry, but we don't plan to provide a training code.


Faster / parellel i18n AOT builds

Bug Report or Feature Request (mark with an x)
- [ ] bug report -> please search issues before submitting
- [ X ] feature request

Versions.
@angular/cli: 1.1.3
node: 6.10.1
os: darwin x64
@angular/animations: 4.2.4
@angular/common: 4.2.4
@angular/compiler: 4.2.4
@angular/compiler-cli: 4.2.4
@angular/core: 4.2.4
@angular/flex-layout: 2.0.0-beta.8
@angular/forms: 4.2.4
@angular/http: 4.2.4
@angular/material: 2.0.0-beta.7
@angular/platform-browser: 4.2.4
@angular/platform-browser-dynamic: 4.2.4
@angular/platform-server: 4.2.4
@angular/router: 4.2.4
@angular/cli: 1.1.3
Desired functionality.
I'm working on a fairly large app that uses AOT and i18n localization, and we need to translate into 60+ languages. Currently the only option is to run ng build for each language one at a time. For my app this takes 5 hours to complete running them in series. My short-term mitigation is to run ng build in parallel which will helps, but I think we can do better.
My thought is adding something like ng build -prod --i18n-config i18n-config.json
Then, in the config file you could list all the languages you want and the destination directories for each and ng-cli would run them in parallel. Additionally, it feels like it could do the AOT build once and hold the AST in memory then generate each language without having to re-do the entire AOT build for every language. I haven't fully researched this, and I know it'd add a lot of complexity, but for enterprise scale global apps this is absolutely needed to have reasonable build times.

I agree, this will enable the real world use case of having a large team with a large app that has continuous delivery and many languages.

Yeah I can't really argue that 5h is a lot of time to build your app for all languages. I suppose at a low level, the apps array could be leveraged to that effect and used with a ng build --all or something. Wouldn't be much different from just using a shell script like you do currently though.
Saving part of the compilation from before sounds like a better idea, but much more complex. It would also require some explicit support from ngc itself.

We have the same problem at google and it is now reaching the limit of our build systems as well. We are working on improvements for v5, stay tuned!

@ocombe just wanted to checkup on the timeline for the above stuff as v5 landed now :)
I'm guessing this is now a CLI thing since we have AOT watch mode and baking in the languages can be done much quicker?

It will not be parallel builds. We are working on something called "runtime i18n" right now, we'll bundle all translations in the same bundle and apply the translation at runtime (without needing a compiler, so this is still AOT-safe). This means only one build even if you have 100 languages.
It should land in 5.1 or 5.2 (depending if we find any blocker that requires more work).

@ocombe , Anyway we are doing this for all the languages, Why can't we add for all environments.
I mean build only one for all languages and all environments once.
any chance?

@ocombe is there any place we can read about reasons to have all translations in a single bundle? Why not to have a separate trans bundle per language?

we won't force you to have one bundle for all languages, you can build one bundle for each (it's what google will do internally)

we won't force you to have one bundle for all languages, you can build one bundle for each (it's what google will do internally)

Thats sounds promising  @ocombe. Will the i18n bundles then also be feature bundled in order to support lazy load along with the correct application chunk or are we required to load all translations with initial load?

It's undecided yet, as much as we want to support lazy loading it'll probably be too much work for the first iteration of runtime i18n. But that's definitely a feature that we want to add.

@ocombe Sorry for asking here but I cannot find up to date info about the "runtime i18n".. What is the status of the implementation? I have to decide between ngx-translate or angular-i18n (I would prefer the core lib) but we need editable translations. If I want AoT i am forced to use ngx-translate i guess at the moment.

There's no fixed date, we are aiming for v6, but since it's part of the new renderer (ivy) it can be merged at any time (if we miss the v6 deadline, we don't have to wait for v7). It'll be behind a flag, and you'll have to use the new renderer which is not finished yet.
I don't think it's realistic to do a production app using ivy before may or june probably, there will be a lot of bug fixes once the feature parity with the current renderer is achieved

I decided to use ngx-translate in the end because I need dynamic AoT translations since the translation files are hosted and can be changed at any time. If I understood correctly that is not possible with angular-i18n and AoT even after the "runtime i18n" because the translations are bundled, not loaded from the xlf.

no, the translations will not necessarily be bundled, we'll add a way to lazy load them, but there might be some kind of transformation necessary for those files (because we don't want to ship the xliff/xtb compiler, it's like 10kb of code just to transform those xml files into usable js structures)

I'm guessing it will just be a simple JSON file for each language that can be lazy loaded with id -> target mapping. Can't be smaller than that, I think?

yes something like that, the target node might be pre-processed as well to avoid any runtime computation

Any updates on this?  It was discussed coming in versions 5, then 6, then 7.  8 is around the corner.  Our builds take approximately 45 minutes and we have about 20 languages.  We will probably triple the number of languages and are looking at multiple hour builds.  We are also discussing fanning out processing to many docker containers (one language per container) for every build, but wanted to check if there is any change in timeline so we can plan accordingly.  Thanks!

Hi! I am looking as well forward to a solution for this.
Especially as when you are executing the build for multiple locales, you will have a lot of equal files (e.g. runtime.**.js, styles.**.css, polyfill.**.js will stay the same, only the main.**.js file will change according to the locale).
Best,
Sebastian

Is there a safe & tested solution for parallel build or speeding up languages builds now?

my solution for i18n parallel build:
https://stackoverflow.com/a/56463676/2582581

I'm trying to use https://www.npmjs.com/package/npm-run-all this package with --parallel flag. It works on my machine but will rise my CPU usage to 100% and in our CI machine it will throw memory allocation failed exception, but I think that it is only ram issue and we are testing if more RAM will fix it. Some say that you need to run ng command with extra flag with larger project like this: "ng-high-memory": "node --max_old_space_size=8000 ./node_modules/@angular/cli/bin/ng" but yet it didn't fix my problem.

Internationalization in Ivy is a lot smarter about builds so we don't need to do a full rebuild for each language by simply using the --localize parameter. You can specify only specific languages if you want, or build all of them and re-use most of the computation. This should drastically improve build performance.
https://angular.io/guide/i18n#build-from-the-command-line
If you are still having performance/memory problems when using the Ivy process, then please open a new issue where we can look into that specific problem more closely.


Styling a export file

How can i style my exported excel file ?
i need to set header styles and body on csv file

Please refer to the docs for more info about styling.

@bilal001222121 you cannot style a csv file. You can only style xlsx and xls. For those please follow the guide @GlennM has shared


broot: 0.20.0 -> 0.20.3

Motivation for this change
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)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

* [x]  Diff LGTM. Maybe add changelog

* [x]  Commits LGTM

* [x]  Builds via `nix-review`:

https://github.com/NixOS/nixpkgs/pull/96467
1 package built:
broot

Thanks for the review!


Remove integration_tests from app workflow

Description
Despite earlier attempts to address flakey e2e tests, we are still having issues with them. In the short term this is disrupting our dev flow as the build is frequently breaking.
This PR disables running e2e tests in CI. We will need to return to this issue when the time it right.
Verification Steps

[ ] CircleCI file is properly updated.

References

A build that failed this morning
An attempt to address the issue by lengthening the wait time to 10 seconds.

@jim Is there a Tracker task to re-enable this?

@brainsik Good call: https://www.pivotaltracker.com/story/show/155757133


[MDK]: Updated tutorials with latest changes+added some validation Questions

Updated MDK tutorials with latest changes+added some validation Questions

@thecodester This PR contains two new tutorials. Please take over. Thank you.

@MichaelCzcz thanks for your feedback/comments. I have updated and updated the PR.

@jitendrakansal How should we group the 2 new tutorials?

@thecodester I did send you a separate email on this.
Anyway, here are the details:

cp-mobile-dev-kit-i18n-localization should be part of Level up with Mobile Development Kit mission , this tutorial should be added as 2nd last tutorial in the list.

Also  please update mission total time: 3 hr. 20 min
cp-mobile-dev-kit-cert-auth should be part of Brand Your customized App with Mobile Development Kit SDK mission as the last tutorial.
also please update mission total time: 1hr. 55 min


Codecov PR comment shows a code coverage reduction with new Native code

Description:
Codecov PR comment shows a drastic coverage reduction with new Native code.
Check https://github.com/ballerina-platform/module-ballerinax-mysql/pull/104
Steps to reproduce:
Affected Versions:
OS, DB, other environment details and versions:
Related Issues (optional):

Suggested Labels (optional):

Suggested Assignees (optional):

Fixed with https://github.com/ballerina-platform/ballerina-lang/pull/30189

This is the code coverage for the above mentioned PR after applying the fix.
https://codecov.io/github/Dilhasha/module-ballerinax-mysql/commit/c947cef62a5e39723e7031c83874d6f0fae07431

the PR is now having sufficient codecov figures to merge.


Code workflow

 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.:x: singhabhay12 sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.


[WFCORE-5566] Fix FIPS detection so that it also works with Java 17

https://issues.redhat.com/browse/WFCORE-5566

Thanks, @Skyllarr !


Fix Structure level display even without countdown

Current behaviour:
The structure level cannot be selected in a LoS if "Default structure level speaking time in seconds" is bigger than 0
Reproduction:
Preconditions:

at least one structure level
at least two participants need a structure level
reproduction:

in settings -> LoS -> "Default structure level speaking time in seconds" > 0
navigate to a LoS and put the participant with a structure level on it
the structure level is selectable and deselectable
navigate to settings -> LoS
put "Default structure level speaking time in seconds"  to 0
navigate to the old LoS the structure level is not deselectable
put the other participant on the LoS -> the structure level is not selectable

Wanted behaviour:
Even if the structure levels are not connected with the countdowns, they need to displayed in the LoS
If the structure levels are not connected with the countdown then all structure levels should be displayed. They should be separated by a comma)

I don't understand the description of this issue. @Elblinator pls look over it and correct it.


feat(Icon): Teams theme add static outline and filled classes to SVG icons

Closes #716.

[x] Add teamsIconSlotClassNames.outline and filled to all SVG icons in Teams theme which have outline and/or filled paths,
[x] do the same for all ProcessedIcons in Teams theme,
[x] add UT to verify these classes on Teams icons,
[x] Use teamsIconSlotClassNames instead of hardcoded class names in theme styles,
[ ] update CHANGELOG.

Warnings

:warning:
There are no updates provided to CHANGELOG. Ensure there are no publicly visible changes introduced by this PR.

  Generated by :no_entry_sign: dangerJS


Added table for team

Added team info in a table.
SIde-question: do we want to put one of our team pictures up here?
Fixes #4

Pushed a few fixes (nits, markdown).
Did we settle on adding a link for each person?
This is how the page currently looks like

Did we settle on adding a link for each person?

I've added links to Pontoon for at least the PMs.

I'm going to rebase and merge this later, we can iterate next week as needed.


Is rich annoying ?

I find the output maybe nice to read but always full of cruft when there is log messages and tracebacks, that are impossible to copy past. Especially because of the right end side that insist on having the filename where the log happend and insist on reflowing instead of letting the terminal handle new line.
Should we remove rich or make it opt-out for logs ? Or configure it better.

Copy-pastablity is always nice. Also the tracebacks are way too verbose. I guess as the IPython developer you would disagree with this, but I never felt like you need more than one line of context in a traceback.


How to set up the Build Server to run as a service

David is reporting that the build server service (omint) is having the same trouble running as a service that the KB server service did (64-bit Windows platform).  The instructions that you sent using yajsw for the KB server worked perfectly. I’m not finding any instructions for setting up omint as a service.  Can you point me to those instructions, or show us how to use yajsw to set up the build server to run as a service?

Found "Build Server as a Windows Service" instructions here: https://www.openmakesoftware.com/help/#!buildserverasawindowsservice.htm

Yes that is the correct instructions for their install.  Let me know if they run into any issues.


Downloaded TavernAI, it won't Start

I receive two different kinds of errors when I run the Start.bat as either normal and as administrator... I'm very unfamiliar with all of this kind of stuff, so I don't quite understand what the issues are, also I'm running on Windows 10.
Administrator Error:

Non-Administrator Error

PS, thank you for taking the time to read, and if you do reply, please put it in really really basic terms for someone with no computer knowledge to understand so I know what the problem is, and what I'm doing, or what I need to do to fix it.
I've also downloaded and installed Node, there were some Warnings and other things that happened... not sure if that's the root of the problem either.

It is because windows ExecutionPolicy for powershell scripts is in default setting set to Restricted.
Simplest way to get it to work is to run in powershell:
Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser
And say yes when it asks. Just a reminder, it will lower your protection against malicious scripts somewhat (you can read more about it here: https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_execution_policies?view=powershell-7.4#remotesigned). But it is limited to your user account only, so "it is something" :)
Hope it helps.

Actually the fix is simple: open the properties page on the file start.ps1 and unlock it.
I tried writing commands, but it didnt work.


Continuous integration tests failing due to timestamp mismatch

Your CI test script appears to be failing due to a timestamp mismatch, either due to wrong time zone setting for the test instance, or incorrect assumption about AM/PM time, as the timestamps actually differ by exactly 12 hours.

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Thanks a lot for letting me know! I wasn't getting any build failure notifications from Travis CI. It's because I had changed my default git email address, but forgot to verify it in my GitHub account.
I'll get those tests fixed!

Fixed in 210d7124b24935080f210a6ec168c9ed07a81721.
Thanks again, haha I just realized that I haven't been getting Travis CI email notifications for the last 4 years. Nice to have those again


Rewrite RewriteTensorPointer pass to support 2D block store

Prevents StoreOps from being rewritten if it is not suitable for 2D block store.
Addresses Issue: #1143

Note that the forwarding of the data encoding to the StoreOp and the the actual lowering to the 2d block store intrinsic will come in separate PRs.


Bug: Extension does not start up with error "locating users: using /tmp as mount point"

On Windows 11, I am receiving the following error:
Error while locating users: using /tmp as mount point
Feel free to ask if you need more details or are able to provide how to get a more detailed log of the error.

Hi @Cliftonz , thanks for your report.
This is a known issue and we are working to solve it. In the meantime, you should still be able to launch localstack from the extension but unfortunately some features may not be working.

On Windows 11, I am receiving the following error:
Error while locating users: using /tmp as mount point

FYI: On Windows 10, I am receiving the same error.


Implement categorical projection of ontologies

mOWL support different types of models. Select which type fits better for your suggestion.
Ontology graph projection
Publication Link
https://arxiv.org/abs/2305.07163
Reference Implementation
https://github.com/bio-ontology-research-group/catE
Additional Implementations
No response
Additional Information
This graph projection must support some parameters such as: saturation steps, saturation with transitivity, and separation of concept and role categories.

Available in version 0.3.0


Change @Since tags on two operations

Since annotations in ChangeGraphAccess and GetAllGraphInfo reference 1.10.6. They should be updated to 1.11.0 which will is about to be released.

Merged into develop


DATETIME DEFAULT sysdate() works wrong

OrientDB Version: 3.1.0 from develop branch
Java Version: docker openjdk:8-jdk-alpine
OS: docker openjdk:8-jdk-alpine
Expected behavior
timestamp contains 2019-05-20 23:45:34 current timestamp of insertion
Actual behavior
timestamp contains 2019-05-20 23:37:14 timestamp of execution sql ALTER PROPERTY `Table`.`timestamp`...
Steps to reproduce
CREATE CLASS Table
CREATE PROPERTY `Table`.`test` STRING
CREATE PROPERTY `Table`.`timestamp` DATETIME
ALTER PROPERTY `Table`.`timestamp` DEFAULT sysdate("yyyy-MM-dd HH:mm:ss") #2019-05-20 23:37:14
INSERT INTO Table SET test = "1" #2019-05-20 23:45:34

Hi @freeart
Try the following:
ALTER PROPERTY `Table`.`timestamp` DEFAULT 'sysdate("yyyy-MM-dd HH:mm:ss")'

In your case, the sysdate() function is evaluated only once, when you create the schema and the value is assigned as default value.
If you quote it, the funciton is evaluated at each record creation
Thanks
Luigi


wink

Home Assistant release with the issue:

Operating environment (HassOS/Generic):

Supervisor logs:

Description of problem:
Sometime after Hassio v95, my connection to wink failed. Latest version 95.4 on rpi3.  I only have a couple of zigbee ceiling fans on Wink so left it until now. I stopped HA, deleted wink.conf, hard reboot and waited until Hasio found Wink. I entered the client ID and secret and then get a link to authorize. Clicking the link fails as it is using a DuckDNS address which I stopped using when I moved to Nabu Casa. I tried editing the address to authenticate with no success. Any ideas how I can get this complete?

Please close this, after many tries it finally worked.  Issue looks to be at Winks end as their stuff is getting worse and worse.


silver searcher how to unignore files in the .gitignore

I have a folder of aliases. these are bash files.
some are sensitive, so I keep them in a .gitignore
~/.bash_utilities
   bash_a.sh
   bash_b.sh
   .gitignore

.gitignore:
bash_b.sh
the problem is that my silver searcher looks at the .gitignore and skips those files when looking.
how do I tell the silver searcher to ignore the .gitignore and look in all the files in the directory.
my current command is
ag $1 ~/.bash*

nvm mind,
got the answer
-u --unrestricted

Search all files. This ignores .ignore, .gitignore, etc. It searches binary and hidden files as well.

-U --skip-vcs-ignores

Ignore VCS ignore files (.gitignore, .hgignore), but still use .ignore.


Uploading a String[] of Roles

This is linked to https://github.com/stuyspec/stuyspec-api/issues/158. We want to create a way for us to upload a String[] of roles to the database. I would suggest that you replace the current dropdown menu with Chips from RMWC.

Check what I said in stuyspec/stuyspec-api#158.


fix: crash when navigator.userAgentData is undefined

Why
We have gotten several Sentry reports about a crash Cannot read properties of undefined (reading 'brands') from this file. Apparently some browsers does have the field userAgentData defined, but its value is undefined.
What
Adds an extra check that userAgentData is truthy before trying to read it.
Links

Checklist

[ ] Tests added
[ ] Changelog updated
[ ] Documentation updated

 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.You have signed the CLA already but the status is still pending? Let us recheck it.

@Pajn would you do me a favor and add the bug fix to the changelog.

Hey @Pajn we released a patch version including your fix.


When I drag outside of the parent container, and then back it will drag even when my mouse is not on the draggable element

This is a regression and did not act like this v0.8.5. This was introduced in v1.0.0
v0.8.5 and before:

v1.0.0 and up:

This is due to v1 processing deltas only, not relying on the actual absolute position of the element.
A fix would be to look at the mouse position in relation to bounds, and cancel the x or y movement if the mouse is outside of those bounds relative to the element.

I'm not quite following your comment @STRML . Is that something that would have to happen inside the react-draggable source or something we can do as a consumer? I know we can return false from onDrag to stop dragging after they've gone out of bounds, but then they would have to click again to restart dragging

+1 I am having this exact same issue. Users don't expect to have to click again to restart slider dragging if they go out of bounds.


Battery test app

Closes #1292

This change is

PR is added to the queue for testing as 1. task. (d4fcca1)

Test (Success) 89388695 build is completed (d4fcca1)
See https://github.com/ThaliTester/TestResults/tree/89388695d4fcca1_Battery_test_app_andrew-aladev/ for the logs

Test 89388695d4fcca1(d4fcca1) has failed
See https://github.com/ThaliTester/TestResults/tree/89388695d4fcca1_Battery_test_app_andrew-aladev/ for the fail logs

PR is added to the queue for testing as 1. task. (d14a551)

Test (Success) 89388695 build is completed (d14a551)
See https://github.com/ThaliTester/TestResults/tree/89388695d14a551_Battery_test_app_andrew-aladev/ for the logs

Test 89388695d14a551(d14a551) has failed
See https://github.com/ThaliTester/TestResults/tree/89388695d14a551_Battery_test_app_andrew-aladev/ for the fail logs

Reviewed 1 of 2 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

Reviewed 1 of 2 files at r1.
Review status: :shipit: all files reviewed at latest revision, all discussions resolved, all commit checks successful.

Comments from Reviewable

Test (Success) 89388695 build is completed (3df03fb)
See https://github.com/ThaliTester/TestResults/tree/893886953df03fb_Battery_test_app_andrew-aladev/ for the logs

Test 893886953df03fb(3df03fb) has failed
See https://github.com/ThaliTester/TestResults/tree/893886953df03fb_Battery_test_app_andrew-aladev/ for the fail logs


Allow file upload without loading entire file into memory

In other SDKs we use streams or equivalent to only read parts of the file into memory and stream the data to the file upload API.
We support file uploads up to 2.2GB, so we have to be able to upload files without loading the whole file into memory.

@armandobelardo is this resolved now?

The file client has been manually customized and disabled for generation to resolve this.


Unhandled event: ['error', 'Please reload Omegle to continue.']

When starting the script i get this error, never got this error before. always worked today it started this error.
Unhandled event: ['error', 'Please reload Omegle to continue.']
I heard it was due to Omegles update today about clicking the ToS. I am not very good at coding python yet and would like help if possible thanks!

@elias94

Hey @Threadz112 I'm not using the library and there is no active maintainers at the moment.
The code is not difficult, you can give it a try and open a pull request and maybe someone can review your code :)

If it helps, I can basically guarantee it's to do with the new user agreement buttons they added.

Honestly. I might as well maintain this lol. Creating a pull request with the fix.

Edit: Since you aren't planning on maintaining this anymore I'm just going to re-code the lib on my own based off yours so I can have full access. I'll edit the link in for that when it's finished, and be sure to give full credit to you.

https://github.com/isaackogan/OmeglePy

late to the issue but for anyone still having problems with this
use this repo it has it fixed https://github.com/onsagere/pyomegle

thanks hdboye. If you want you can open a PR and I will have a look to merge and update the dependency

late to the issue but for anyone still having problems with this use this repo it has it fixed https://github.com/onsagere/pyomegle

This repo isn't working for me.


Enable circular loop issue #37

You can now do a circular loop for carousel. If at last item, hitting "next" will bring you to the first item, and if at first item, hitting "previous" will bring you to the last item of the carousel.

Hi @ericalas93 thanks for the contribution! We will be including an infinite-looping option for Scooch as part of the v1.0.0 release.
I will close this PR.


Install pytorch to run charm4py CI tests

@matthiasdiener I think this is ready to merge now. Can you take a look


pg_stat_statements.total_time & v13

Version: current master branch
pgcluu_collectd -v gives me this:
psql:<stdin>:54: ERROR:  column "total_time" does not exist
LINE 1: ...[ \n]+', ' ', 'g'), E';', '#SMCLN#', 'g'), calls, total_time...

That seems to be related to pg_stat_statements.
In PG13, total_time was replaced by total_plan_time and total_execution_time.

Hello,
I just pushed a PR to fix this for pg13 and above.
Regards


(BOLT-1057) Standardize BoltSpec::Run helper method signatures

Previously, these methods had confusing and inconsistent signatures
using a mix of optional parameters and keyword arguments. In some cases,
the optional parameters were themselves expects to be hashes, which
conflicted with the keyword arguments. That caused confusing behavior
when invoking the functions with only some arguments, as a hash intended
to be a positional argument could be interpreted as an invalid keyword
arguments hash, or vice versa.
These functions now always require their params (or equivalent)
argument, leading to slightly more verbose but always clear
invocations. The functions which previously expected an options hash in
addition to their keyword arguments now expect the options hash to
be provided as a keyword argument named options.

This will require some corresponding changes to a few modules that use BoltSpec. I know of at least puppetlabs/puppetlabs-package, puppetlabs/puppetlabs-service, puppetlabs/puppetlabs-facts, puppetlabs/puppetlabs-puppet_agent, `puppetlabs/puppetlabs-reboot.

It doesn't look like package or service need changes, because they only use run_task and they always pass the params argument. I've filed corresponding PRs for the three other modules:
https://github.com/puppetlabs/puppetlabs-puppet_agent/pull/389
https://github.com/puppetlabs/puppetlabs-facts/pull/22
https://github.com/puppetlabs/puppetlabs-reboot/pull/201

For the most part, consumers of this code can support both old and new versions of BoltSpec by always passing the params/arguments option.
The only case where there isn't a fully compatible change available is anyone passing options positionally to run_command, since it's now a keyword argument. That's only necessary if you want to use _description or _run_as though, so it's unlikely to be currently used.

CLA signed by all contributors.


fix tests that were not compiling or panicking

Further to the client.StartMonitorEvents prototype change tests where either not compiling or panicking (mock got more arguments than expected).
Signed-off-by: Pierre Wacrenier<EMAIL_ADDRESS>

LGTM


out of stock

All products in catalog mode are out of stock.. How can i fix that ?
Magento version 2.4.4.
[https://estbike.ro/default/motorizate/motociclete.html]
Thank you!

I managed to "fix it" by editing the language file...


Issue15 - Testing mtcpclient part1 (stddev function)

First commit with a minimum contribution to the unit tests:
https://github.com/dachad/tcpgoon/issues/15
Applying TDT for the stddev calculations. Some minor changes/additions introduced in the tested code, but some others expected (see TODO) once we actually increase coverage.
Added the race flag to our scripted go test execution.
As usual, I will squash and merge once approved

@dcaba , do you want to merge this PR as a first step on mtcpconnection testing? or are you expecting to add more commits to it? (just to understand if you are waiting for my approve)

Hi,
I'd merge to keep prs as small as possible, and benefit from them soon ;)
On Dec 11, 2017 08:06, "Christian Adell"<EMAIL_ADDRESS>wrote:

@dcaba https://github.com/dcaba , do you want to merge this PR as a
first step on mtcpconnection testing? or are you expecting to add more
commits to it? (just to understand if you are waiting for my approve)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dachad/tcpgoon/pull/44#issuecomment-350639013, or mute
the thread
https://github.com/notifications/unsubscribe-auth/APKZPqN22FbJv_-hPMRVaEGSIK3pKTZ1ks5s_NR6gaJpZM4Q71Wx
.


Can't see TS typings for this library

It seems the Typescript types are well defined for the fetch-mock library. However, I can't seem to find typings for this wrapper library anywhere. Could you please point me in the right direction?

Also, any comparisons between this library and jest-fetch-mock wuld be much appreciated :)

I've just added the following declarations for now in my project, which seem to work fine though I'm not totally sure if they are correct:
declare module "fetch-mock-jest" {
  import { FetchMockStatic, MockCall, FetchMockSandbox } from "fetch-mock";

  interface FetchMockJestSandbox {
    sandbox(): jest.MockInstance<Response, MockCall> & FetchMockSandbox;
  }

  export type FetchMockJest = jest.MockInstance<Response, MockCall> &
    FetchMockJestSandbox &
    FetchMockStatic;

  const fetchMockJest: FetchMockJest;

  export default fetchMockJest;
}

declare namespace jest {
  import { InspectionFilter, InspectionOptions } from "fetch-mock";

  interface Matchers<R, T> {
    toHaveFetched(filter?: InspectionFilter, options?: InspectionOptions): R;
    toHaveLastFetched(
      filter?: InspectionFilter,
      options?: InspectionOptions
    ): R;
    toHaveNthFetched(
      n: number,
      filter?: InspectionFilter,
      options?: InspectionOptions
    ): R;
    toHaveFetchedTimes(
      times: number,
      filter?: InspectionFilter,
      options?: InspectionOptions
    ): R;
    toBeDone(filter?: InspectionFilter): R;
  }
}

Happy to work on a PR after I've battle tested them a little more.

@mdlawson I don't know typescript very well, but the fetch-mock-jest api isn't very big, so you're probably pretty close. Could do with tslint tests for the PR though. Thanks for starting work on it.
@sadsa By comparisons you mean some sort of feature by feature comparison table?

@wheresrhys - Well, I haven't had enough exposure to the library yet but from a quick visit to the documentation for this project, it's pretty lacking so far. It took me awhile to see that fetch-mock actually has quiet a full set of docs (http://www.wheresrhys.co.uk/fetch-mock/). Either a feature list at the top of the readme or a clear link through to the fetch-mock docs would be nice.

@mdlawson - If you could make a PR for this, that would be awesome

Thanks for the feedback - I'll try to make that clearer

@sadsa Let me know what you think of the readme now

FYI I used the following definitions to get this working on:

"fetch-mock": "^9.2.1"
"fetch-mock-jest": "^1.2.4"
"jest": "^25.1.0"
"ts-jest": "25.2.1"
"typescript": "3.8.3"

<EMAIL_ADDRESS>declare module 'fetch-mock-jest' {
  import { FetchMockStatic, MockCall, FetchMockSandbox } from 'fetch-mock';
  interface FetchMockJestSandbox {
    sandbox(): jest.MockInstance<Response, MockCall> & FetchMockSandbox;
  }

  export type FetchMockJest = jest.MockInstance<Response, MockCall> & FetchMockJestSandbox & FetchMockStatic;

  const fetchMockJest: FetchMockJest;

  export default fetchMockJest;
}

<EMAIL_ADDRESS>import { InspectionFilter, InspectionOptions } from 'fetch-mock';

declare namespace jest {
  interface Matchers<R> {
    toHaveFetched(filter?: InspectionFilter, options?: InspectionOptions): R;
    toHaveLastFetched(filter?: InspectionFilter, options?: InspectionOptions): R;
    toHaveNthFetched(n: number, filter?: InspectionFilter, options?: InspectionOptions): R;
    toHaveFetchedTimes(times: number, filter?: InspectionFilter, options?: InspectionOptions): R;
    toBeDone(filter?: InspectionFilter): R;
  }
}

For reference my type roots are defined in tsconfig.json as:
"typeRoots": ["./src/@types", "node_modules/@types"]

you may need to adjust according to your project layout.
Once I've done some proper testing and if all goes to plan I'll put up a PR.
HTH

@alexb-uk Are you able to share any more information about those errors

@alexb-uk Are you able to share any more information about those errors

Sorry got distracted and forgot to write an update. I fixed the test error  but never managed to get import working. I was hoping the following would work but when you run the test it throws an undefined error:
import fetchMockJest from 'fetch-mock-jest';
const fetchMock = fetchMockJest.sandbox();

// Produces: TypeError: Cannot read property 'sandbox' of undefined

So I've switched back to require. At the very top of the test file before any import statements:
const fetchMock = require('fetch-mock-jest').sandbox();

jest.mock('node-fetch', () => {
  const nodeFetch = jest.requireActual('node-fetch');
  Object.assign(fetchMock.config, {
    fetch: nodeFetch,
  });
  return { ...nodeFetch, default: fetchMock };
});

I have also switched from @types/global.d.ts to @types/jest.d.ts and declare global inside the file:
import { InspectionFilter, InspectionOptions } from 'fetch-mock';

declare global {
  namespace jest {
    interface Matchers<R> {
      toHaveFetched(filter?: InspectionFilter, options?: InspectionOptions): R;
      toHaveLastFetched(filter?: InspectionFilter, options?: InspectionOptions): R;
      toHaveNthFetched(n: number, filter?: InspectionFilter, options?: InspectionOptions): R;
      toHaveFetchedTimes(times: number, filter?: InspectionFilter, options?: InspectionOptions): R;
      toBeDone(filter?: InspectionFilter): R;
    }
  }
}

Give me a shout if I can shed any more light.

Thanks for persevering. I wish I could help, but have next to zero knowledge of typescript
@grug Hello, and welcome to the jest wrapper. Having some trouble with types over here. I wonder if you're able to shed any light?

Any progress on this issue?

@tiljanssen @syffs @essensx I don't write typescript. I would really welcome a pull request to implement the types. If you have the time it'd be a great way to give back to open source

I’ve made a pull request based on the types here and tested it on a few projects: https://github.com/wheresrhys/fetch-mock-jest/pull/23

🙌 @skovhus

@wheresrhys when do you plan to make a new release on npm? I guess this should stay open until it has been released? :)

failing build - will debug now

Released as 1.5.1

It would help if the TypeScript setup was documented now that it's supported. This is what I was able to figure out on my own:
const fetchMock: typeof fetchMockJest = require('isomorphic-fetch')


Test Issue

Issue added from Issues tab.

[x] Test task
6/23/21 - Completed.
[x] test task 2
[ ]  New task

[ ] Task #1
[ ] Task #2

Test note- Hi Rick!

@rhood23699 - did you get a notification?


Run tests from inside the cluster

Codecov Report

Merging #114 (f53aed7) into master (165e024) will decrease coverage by 11.58%.
The diff coverage is n/a.

:exclamation: Current head f53aed7 differs from pull request most recent head 348d93e. Consider uploading reports for the commit 348d93e to get more accurate results

@@             Coverage Diff             @@
##           master     #114       +/-   ##
===========================================
- Coverage   28.95%   17.37%   -11.59%
===========================================
  Files          12       12
  Lines         518      518
===========================================
- Hits          150       90       -60
- Misses        354      424       +70
+ Partials       14        4       -10

Impacted Files
Coverage Δ

pkg/collector/pods_containerlogs_collector.go
25.00% <0.00%> (-52.78%)
:arrow_down:

pkg/collector/helm_collector.go
32.60% <0.00%> (-43.48%)
:arrow_down:

pkg/collector/networkoutbound_collector.go
87.50% <0.00%> (-4.17%)
:arrow_down:

pkg/collector/nodelogs_collector.go
73.33% <0.00%> (ø)

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 165e024...348d93e. Read the comment docs.

💡 Regarding codecov decrease I think we should close this PR and re-open as separate PR:

But Codecov is somehow stuck in random commit:


Types: Pull parameter names from header files

@mrbbot ... please ping me again on this PR once you believe it is ready to land and I'll review it again.

@mrbbot and @penalosa ... I have to revert this in #202. When landing I was optimistically anticipating that there would be a corresponding Workers PR internally that would pull this in quickly but there isn't and it's breaking things. We'll need to revert for now and we'll need y'all to get the corresponding Workers PR open and ready before we can un-revert


Running test for the first time fails on Ubuntu 18.04.5 LTS

I'm starting the test for the first time using:
~/Dokumente/Projects/sapcp/cds-pg$ npm test

But this test fails with the following errors:
><EMAIL_ADDRESS>test /home/gwolf/Dokumente/Projects/sapcp/cds-pg
> run-s test:pg:up jest test:pg:down

><EMAIL_ADDRESS>test:pg:up /home/gwolf/Dokumente/Projects/sapcp/cds-pg
> docker-compose -f __tests__/__assets__/cap-proj/stack.yml up -d

Creating network "capproj_default" with the default driver
Creating capproj_adminer_1 ...
Creating capproj_db_1 ...
Creating capproj_adminer_1
Creating capproj_db_1 ... done

><EMAIL_ADDRESS>jest /home/gwolf/Dokumente/Projects/sapcp/cds-pg
> jest

 PASS  __tests__/cqn2pgsql.js
 FAIL  __tests__/odata.js
  ● Console

    console.error
      [2020-08-18T21:46:55.725Z | ERROR | 1957855]: Connection terminated unexpectedly

      at LoggerFacade.error (node_modules/@sap/odata-server/node_modules/@sap/odata-commons/lib/logging/LoggerFacade.js:109:26)
      at chainEndCallback (node_modules/@sap/odata-server/lib/invocation/CommandExecutor.js:37:34)
      at node_modules/@sap/odata-server/lib/invocation/CommandExecutor.js:84:25

    console.error
      [2020-08-18T21:46:55.727Z | ERROR | 1957855]: Error stacktrace: Error: Connection terminated unexpectedly     at Connection.<anonymous> (/home/gwolf/Dokumente/Projects/sapcp/cds-pg/node_modules/pg/lib/client.js:272:71)     at Object.onceWrapper (events.js:421:28)     at Connection.emit (events.js:315:20)     at Socket.<anonymous> (/home/gwolf/Dokumente/Projects/sapcp/cds-pg/node_modules/pg/lib/connection.js:102:10)     at Socket.emit (events.js:327:22)     at endReadableNT (_stream_readable.js:1220:12)     at processTicksAndRejections (internal/process/task_queues.js:84:21)

      at LoggerFacade.error (node_modules/@sap/odata-server/node_modules/@sap/odata-commons/lib/logging/LoggerFacade.js:109:26)
      at chainEndCallback (node_modules/@sap/odata-server/lib/invocation/CommandExecutor.js:38:34)
      at node_modules/@sap/odata-server/lib/invocation/CommandExecutor.js:84:25

    console.log
      {
        error: { code: '500', message: 'Connection terminated unexpectedly' }
      }

      at Object.<anonymous> (__tests__/odata.js:52:17)

    console.error
      [2020-08-18T21:46:55.748Z | ERROR | 1957855]: read ECONNRESET

      at LoggerFacade.error (node_modules/@sap/odata-server/node_modules/@sap/odata-commons/lib/logging/LoggerFacade.js:109:26)
      at chainEndCallback (node_modules/@sap/odata-server/lib/invocation/CommandExecutor.js:37:34)
      at node_modules/@sap/odata-server/lib/invocation/CommandExecutor.js:84:25

    console.error
      [2020-08-18T21:46:55.748Z | ERROR | 1957855]: Error stacktrace: Error: read ECONNRESET     at TCP.onStreamRead (internal/stream_base_commons.js:205:27)

      at LoggerFacade.error (node_modules/@sap/odata-server/node_modules/@sap/odata-commons/lib/logging/LoggerFacade.js:109:26)
      at chainEndCallback (node_modules/@sap/odata-server/lib/invocation/CommandExecutor.js:38:34)
      at node_modules/@sap/odata-server/lib/invocation/CommandExecutor.js:84:25

  ● OData to Postgres dialect › odata: GET -> sql: SELECT › odata: entityset Beers -> sql: select all beers

    expect(received).toStrictEqual(expected) // deep equality

    Expected: 200
    Received: 500

      52 |         console.log(response.body)
      53 |       }
    > 54 |       expect(response.status).toStrictEqual(200)
         |                               ^
      55 |       // 2 beers in the shop
      56 |       expect(response.body.value.length).toStrictEqual(2)
      57 |       // at least one of them must be the "Lagerbier Hell"

      at Object.<anonymous> (__tests__/odata.js:54:31)

  ● OData to Postgres dialect › odata: GET -> sql: SELECT › odata: entityset Beers -> sql: select all beers

    TypeError: Cannot read property 'release' of undefined

      71 |    */
      72 |   async release() {
    > 73 |     return this.dbc.release(true)
         |                     ^
      74 |   }
      75 | }
      76 |

      at PostgresDatabase.release (index.js:73:21)
      at Object.<anonymous> (__tests__/odata.js:46:20)

  ● OData to Postgres dialect › odata: GET -> sql: SELECT › odata: single entity -> sql: select record

    expect(received).toStrictEqual(expected) // deep equality

    Expected: 200
    Received: 500

      62 |       const response = await request.get('/beershop/Beers(9e1704e3-6fd0-4a5d-bfb1-13ac47f7976b)')
      63 |       // http response code
    > 64 |       expect(response.status).toStrictEqual(200)
         |                               ^
      65 |       // the beer
      66 |       expect(response.body.ID).toStrictEqual('9e1704e3-6fd0-4a5d-bfb1-13ac47f7976b')
      67 |       expect(response.body.name).toStrictEqual('Schönramer Hell')

      at Object.<anonymous> (__tests__/odata.js:64:31)

  ● OData to Postgres dialect › odata: GET -> sql: SELECT › odata: single entity -> sql: select record

    TypeError: Cannot read property 'release' of undefined

      71 |    */
      72 |   async release() {
    > 73 |     return this.dbc.release(true)
         |                     ^
      74 |   }
      75 | }
      76 |

      at PostgresDatabase.release (index.js:73:21)
      at Object.<anonymous> (__tests__/odata.js:46:20)

Test Suites: 1 failed, 1 passed, 2 total
Tests:       2 failed, 3 skipped, 7 todo, 2 passed, 14 total
Snapshots:   0 total
Time:        2.146 s
Ran all test suites.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>jest: `jest`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>jest script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR!  Test failed.  See above for more details.

when I run the test the second time it completes without error.
My node version is 12.18.3, Docker version 19.03.6, build 369ce74a3c, docker-compose version 1.17.1, build unknown

given that github actions also run on ubuntu and don't show this behaviour, it smells like a problem in your local env.
also, the error toward failed socket connections indicate that.
i'm guessing, you're running postgres on ubuntu in a VM. note that npm test boots up its' own docker image with postgres - probably a collision effect btw your postgres in ubuntu and the provided postgres in docker?

I've used the Ubuntu Laptop also for developing on https://github.com/gregorwolf/pg-beershop where I've run postgres also in docker. There is no local postgres installation active as it was on my Mac. The strange thing is that it works with the second attempt (when the docker container is already running) but setting a timeout after the docker start doesn't help either.

can you peak at the pg logs of the docker image on the laptop once it has started (most likely /var/log/postgresql)?
and are there clues in /var/log/syslog pertaining to network messages?

It seems to be an issue with the /docker-entrypoint-initdb.d/ script. It seems that docker-compose returns control already before the script execution completed. The answer to How to block until initdb has finished running in a Docker Postgres container? provides one option.

as this is not mission critical (any more), i'm closing the issue


Release v1.9.39

This is the promotion branch for hotfix release_v1.9.39

/build-deploy-preview env=release

/ok-to-test sha=d06c242

/ok-to-test sha=d06c242


entities[].state it works??

im working in my floorplan and i want to change an image with several conditions of several entities.
i try something like this but i cant be able to make it works
service_data: |
>
if (entity.state === 'on') {
if (entites['input_boolean.test'].state === 'on') {
...

Hi.
Please create question in the Discussion-area.
Also, please help us with helping you:

Add your full YAML for Floorplan
Add any attachments needed, if you have any
Please explain what you would like to do, and what you're expecting to get as the result, too.

Thanks 👍

Hi.
Please create question in the Discussion-area.
Also, please help us with helping you:

Add your full YAML for Floorplan
Add any attachments needed, if you have any
Please explain what you would like to do, and what you're expecting to get as the result, too.

Thanks 👍

Hi @txusebe Below is how you can use JavaScript to generate the service_data.
    - entity: sensor.ring_salon_battery
      state_action:
        - service: floorplan.text_set
          service_data: '${entity.state ? entity.state + "%" : "unknown"}'
        - service: floorplan.style_set
          service_data: |
            >
            var max = [195, 232, 141];
            var min = [240, 113, 120];
            var r = Math.floor(min[0] + ((max[0] - min[0]) * (entity.state / 100)));
            var g = Math.floor(min[1] + ((max[1] - min[1]) * (entity.state / 100)));
            var b = Math.floor(min[2] + ((max[2] - min[2]) * (entity.state / 100)));
            return `fill: rgb(${r}, ${g}, ${b})`;

This is demonstrated in the Ring example.

Hi @txusebe Below is how you can use JavaScript to generate the service_data.
    - entity: sensor.ring_salon_battery
      state_action:
        - service: floorplan.text_set
          service_data: '${entity.state ? entity.state + "%" : "unknown"}'
        - service: floorplan.style_set
          service_data: |
            >
            var max = [195, 232, 141];
            var min = [240, 113, 120];
            var r = Math.floor(min[0] + ((max[0] - min[0]) * (entity.state / 100)));
            var g = Math.floor(min[1] + ((max[1] - min[1]) * (entity.state / 100)));
            var b = Math.floor(min[2] + ((max[2] - min[2]) * (entity.state / 100)));
            return `fill: rgb(${r}, ${g}, ${b})`;

This is demonstrated in the Ring example.


Relative Units for various screens

Hey Guys,
is there a way to define video size in different units or CSS variables?
Always when I write units like WV, or % script fails.
My goal is to set up video width in WV units and video height keep auto, so the video size adapts to a flexible layout.
Thanks for the reply!
Filip

This should work if you correctly target the canvas element that seeThru renders the content in.
You can either target this element using JavaScript when using what is passed to #ready(callback): https://github.com/m90/seeThru#additional-methods or target .seeThru-display elements. Also see the comment on namespaces I left in #57


Arch Linux and Ohter gnu/linux distro

How can I install Manjaro and Arch?
https://wiki.archlinux.org/index.php/creating_packages

This is a Windows app and built on top of Windows UWP stack. It won't work on any linux distro.

FWIW, this might be doable: https://platform.uno/docs/articles/howto-migrate-existing-code.html

FWIW, this might be doable: platform.uno/docs/articles/howto-migrate-existing-code.html

AFAIK, the feature set of UNO is not sufficient at all to match the same feature level as Notepads as it is right now.

Fair enough. Hopefully one day we'll be able to do a community port.
Off the top of your head, what's missing?

The rich edit (text) control UNO implements only has very few APIs to work with. Also, you will not have the Acrylic effect under Linux as well. Basically, everything is missing for a working port of notepads.


Error after install (from comfyui manager)

File "H:\AI\AI_Image_Generation\ComfyUI\ComfyUI_windows_portable\ComfyUI\custom_nodes\ComfyUI-Nexus_init_.py", line 10, in
from .lib.WebSocketManager import WebSocketManager
ModuleNotFoundError: No module named 'ComfyUI-Nexus.lib'

Fixed it !

Please test and tell if its working so i close this ?


Problem on Programatic use Swift3

The delegate method only being called for 2 times, not according to the numberOfPages supplied
but   titleForSectionAt is being called according to the numberOfPages supplied
override func segmentedPager(_ segmentedPager: MXSegmentedPager, viewControllerForPageAt index: Int) -> UIViewController
INfo - This problem is only on programatic use , when i used with the storyboard and segues it is fine, i tried to debug, no luck !

Actually there was some

There was confusion with cache of VC , it only caches 2 VC at a time, i debugged for almost 5 hours and found out this silly conclusion ,
There is no issue with programatic use on Swift 3

How to handle one VC at a time, because 2nd VC will execute based on 1st VC.
Now 2 VC is runs at a time. Any solution please.


android emulator open and close like IOS or browser

When appium is working with Browser or IOS, it will open a browser (simulator) at the start of session and close it at the end.
I am going to make android behave the same way. For example we can read deviceName and platformVersion and create AVD name according to these parameters, launch AVD (it needs these avds to be predefined [or maybe create avd if it did not find it!!]), and close it at the end of session.
this way the behavior will be almost the same as other platforms. What do you think about it? any suggestions?

Appium already does this, if you specify the avd capability.
We don't want this to be the norm, since emulators take so much time to boot.

Avd opens the emulator if it is not already open, but it never close the emulator that it already opened.
As far as I experienced, if the android environment is configured correctly ( HAXM , KVM, ...) it almost starts as fast as IOS, and since for changing locale it does not shut down and start again, it is even a bit faster.
The problem is when you do not close android emulator, it freezes, or just stop respond to appium. The other problem is sometimes, emulator freeze on reload (this weird issue happens on yosemite OS, with android 6! after 2 or 3 restart !).
For not making it a norm, we can have a parameter defined ( like a boolean opts that decide if we should use this or not). also for making that happen, device name should be defined in android tests, which i believe does not do anything right now).

Issue moved to appium/appium #7406 via ZenHub


feat(controller): Deprecate X prefixed headers

X_DEIS_API_VERSION ->  DEIS_API_VERSION
X_DEIS_PLATFORM_VERSION -> DEIS_PLATFORM_VERSION
Since this is a important change I bumped the api version.

Perfectly executed.  Thanks!

@bacongobbler Done!

Code LGTM, my nitpick is optional.

This test failed for a really weird reason. auth:login http://deis.test-06a0bac476.deis.works --username=test1 --password=test1 failed with:
Couldn't connect to the Deis Controller:
('Connection aborted.', BadStatusLine("''",))
Make sure that the Controller URI is correct and the server is running.

However, deis login worked many times before this in the build, causing me to think this is a sporadic error. Could somebody rerun this CI build? Any ideas why this is happening?

Any ideas why this is happening?

Not exactly. We've seen this a few times. I'll try to track it down. It's unrelated to your PR, which passed when I ran it again.
Code LGTM.


InsecureSkipVerify and Debug variables

The current code checks for these variables either present or not. Based on that the action is taken care. However it would be nice, if code checks for boolean value, e.g. Debug=true then set else disable. Similarly for InsecureSkipVerify.
As we want to expose these variables in docker-compose so client can decide.
The default values for both can be false.

@khhipparagi this is correct. I will look into adding proper "boolean" check, where only "true" would accept