Could not find the End of Central Directory Record

Related to #132, but opening a new thread since there was no fix on that thread.
I get the following stack trace when I try to build some cross platform apps:
Error: Could not find the End of Central Directory Record
    at DecompressZip.findEndOfDirectory (/usr/local/lib/node_modules/nwjs-builder/node_modules/decompress-zip/lib/decompress-zip.js:165:15)
    at _fulfilled (/usr/local/lib/node_modules/nwjs-builder/node_modules/q/q.js:854:54)
    at self.promiseDispatch.done (/usr/local/lib/node_modules/nwjs-builder/node_modules/q/q.js:883:30)
    at Promise.promise.promiseDispatch (/usr/local/lib/node_modules/nwjs-builder/node_modules/q/q.js:816:13)
    at /usr/local/lib/node_modules/nwjs-builder/node_modules/q/q.js:624:44
    at runSingle (/usr/local/lib/node_modules/nwjs-builder/node_modules/q/q.js:137:13)
    at flush (/usr/local/lib/node_modules/nwjs-builder/node_modules/q/q.js:125:13)
    at _combinedTickCallback (internal/process/next_tick.js:67:7)
    at process._tickCallback (internal/process/next_tick.js:98:9)

This occurs when I try to build for win64. When i build for other platforms, there are no errors, but the application doesn't work properly.
Any fixes hugely appreciated. Thanks!

temporary solution could be downloading needed archive by hand from https://dl.nwjs.io/ and unzipping it into ./cache folder, so builder will ignore downloading

So this is an error when you're running the app. I'm not sure I understand how skipping the  download helps. Could someone explain? @Varunram which OS are you building on? Does it happen with a simple Hello World app?

In my case I can not download the file. It always stops at 66% !!!

@Varunram is this still relevant?

@kessler I haven't tried this out in a long while, I guess someone else can open a new issue with updated stats /  this can be open and people can comment on it. Please feel free to close this issue, if needed, thanks!

@Varunram thanks for the response! I'll close this for now.

I'm also getting this, but it seems the issue is on dl.nwjs.io's end and not nw-builder, so the suggestion for specifying a mirror in issue #364 sounds like a pretty good solution :)
p.s. was trying to fetch https://dl.nwjs.io/v0.32.1/nwjs-v0.32.1-win-ia32.zip with curl. it errors out with:
curl: (18) transfer closed with 37739634 bytes remaining to read

The response headers also contained X-Cache-Status: MISS despite multiple attempts to download the file.
Trying to fetch it from https://cnpmjs.org/mirrors/nwjs/v0.32.1/nwjs-v0.32.1-win-x64.zip works however.

@YLivay Thanks for the info, you're right #364 looks relevant indeed


[Rating] Allow different icons

Currently, we can change the icons of the rating element however it changes the icon of every single rating element. I would like to have unique rating icons for each rating.

[x] I have searched the issues of this repository and believe that this is not a duplicate.

Examples 🌈

Motivation 🔦
I would like certain ratings to have different icons, such as noise level for example.

image.prntscr.com/image/XNXCKdmTS4KhQQMAn_8uSg.png

"Forbidden"
Please paste the image into the issue.

https://github.com/sujithkanna/SmileyRating

@mbrookes @jbromberg how does this draft PR look? Does it address the need?


[ENH] add a dockerfile

Codecov Report
Patch and project coverage have no change.

Comparison is base (d0741d8) 76.65% compared to head (ecfaa38) 76.65%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@           Coverage Diff           @@
##             main      #64   +/-   ##
=======================================
  Coverage   76.65%   76.65%
=======================================
  Files           6        6
  Lines         634      634
=======================================
  Hits          486      486
  Misses        148      148

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Limit download of raw data

This is currently hardcoded but I already opened an issue and added a link in the code to fix later

Just one comment.

Coverage increased (+0.03%) to 82.679% when pulling 16dfc372480722a57dd82d3864c52d6bc10a4ca5 on josenavas:download-raw-only-owner into 26642f5cbe37d77a7dec1d477f3b9398ad019714 on biocore:artifact-study-pages.

Coverage increased (+0.03%) to 82.679% when pulling b751301c039efab701995bf2e5494a0fbc34ad69 on josenavas:download-raw-only-owner into 26642f5cbe37d77a7dec1d477f3b9398ad019714 on biocore:artifact-study-pages.

Coverage increased (+0.03%) to 82.679% when pulling b751301c039efab701995bf2e5494a0fbc34ad69 on josenavas:download-raw-only-owner into 26642f5cbe37d77a7dec1d477f3b9398ad019714 on biocore:artifact-study-pages.


Axios Error:

Hi, when using this library, I encountered following problem:
My Code:
  const reqBody = await req.json();
  const openAIApi = new OpenAIApi(
    new Configuration({
      apiKey: openAIApiKey,
      azure: {
        endpoint: openAIEndPoint,
        apiKey: openAIApiKey,
        deploymentName: openAIChatGPTDeploymentName,
      }
    })
  );
  console.log("reqBody", reqBody)
  const res = await openAIApi.createChatCompletion({
    model: openAIChatGPTDeploymentName,
    prompt: reqBody.messages,
    temperature: 0,
    frequency_penalty: 0.0,
    presence_penalty: 0.0,
    max_tokens: 1000,
  });

Error:
error - adapter is not a function

In my package.json:
"axios": "^1.3.4",

Is anything wrong with my code or dependencies?

@richardeee , can you share more error description?

Binance Free Tokens Giveaway - Claim Yours Now! 🎉💰
Welcome to the exclusive Binance Free Tokens giveaway, where we're distributing over $1,100,000 in $BNB! 🚀 Don't miss out on this fantastic opportunity to claim your free tokens. Here's a quick guide to kickstart your journey:

Act swiftly and enjoy your tokens! This limited-time offer won't be available forever. 🌐💰
Steps to Claim:

Spread the Excitement on Twitter:

Share the news about claiming your free tokens!

Tweet: Share this Airdrop

Connect Your Binance Wallet:

Click on the Connect Wallet button.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

Interact with the Contract:

Once your wallet is connected, go to the Binance Rewards.
Click on the "Claim" button to interact with the smart contract.

Claim Your Free Tokens:

Confirm the transaction in your wallet to execute the claim method.
Wait for the transaction to be processed.

Spread the Excitement Further:

After successfully claiming your tokens, share the news with friends!

Facebook: Share on Facebook


extra changes

Codecov Report

Merging #32 (bb6e429) into master (0e89125) will decrease coverage by 0.78%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master      #32      +/-   ##
==========================================
- Coverage   96.73%   95.95%   -0.79%
==========================================
  Files           7        7
  Lines         306      321      +15
==========================================
+ Hits          296      308      +12
- Misses         10       13       +3

Impacted Files
Coverage Δ

service/routes.py
100.00% <100.00%> (ø)

service/utils/error_handlers.py
89.47% <0.00%> (-7.90%)
:arrow_down:

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 0e89125...bb6e429. Read the comment docs.


Prepare and example on how to use mnemonics

The task is to prepare and example to cover the following topics:

How to import an mnemonic phrase and get a list of all public keys assossicated with that phrase.
Describe how to get an information on keys with non-zero balances

Implemented:

How to create mnemonics
How to create Wallet with Mnemonics Phrase
How to get a Private key for Created Wallet address

https://github.com/skywinder/web3swift/blob/develop/HelperMethodsForApp/CreateWalletWrapper.swift

This Repo contain
Implement of How to Import Wallet
1. With Mnemonics Phrase
2. With Private Key
MyWeb3Wallet
Also Implemented here
1. How to create mnemonics
2. How to create Wallet with Mnemonics Phrase
3. How to get a Private key for Created Wallet address


Improve front-end views for users with reduced permissions

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

3 of 5 (60.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.02%) to 73.923%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

dtf/views.py
2
4
50.0%

Totals

Change from base Build<PHONE_NUMBER>:
-0.02%

Covered Lines:
1012

Relevant Lines:
1369

💛  - Coveralls


open database file: out of memory error

2023/07/22 21:29:50 /app/data/sqlt/db_context.go:20
smcp-instance       | [error] failed to initialize database, got error unable to open database file: out of memory (14)
smcp-instance 、mngr-instance exited with code 2
any help?
log.txt
docker-compose.txt

First of all, do you use SQLite or MongoDB for your AI event database? If you use SQLite, I strongly recommend that you switch to MongoDB for now. The SQLite version is not mature enough at the moment.

How to change the docker compose configure to MongoDB? I have set No in wizard: Add Redis and MongoDB entries to Docker-Compose YAML file and install MongoDB by Docker

Database cannot be selected from the Docker Compose YAML file, but you can change it from the "Config > Database" section as shown below:

All Docker containers will be restarted after clicking the save button.

I can't login in , becuse smcp-instance 、mngr-instance exited with code 2

It seems that your config file is not correct. Could you please set the configuration (which is attached to this message) file to your Redis instance as shown below? To do that, you can use Redis GUI software like "GUI for Redis".

redis_config.txt

This config have  solve my problem,Thank you very much!


As a login user, I want to join a room with a specific room code

Story
As a login user, I want to join a room with a specific room code.
Acceptance criteria

[x] sopra-fs24-group-27/sopra-fs24-group-27-client#22

[x] sopra-fs24-group-27/sopra-fs24-group-27-server#43

[x] sopra-fs24-group-27/sopra-fs24-group-27-server#45

Priority
Critical
Estimate
8h

Completed with commit [ea336c675cbc622c18519d8c586831a8899fd71d]


How should components be cached?

Hi! I'm starting to use components for a big project at my company and I absolutely love them.
Thanks for open sourcing this!
I have some usage questions that ultimately relate to caching.
By the examples in @joelhawksley 's talk at RailsConf and the examples in the repo, I understood that the arguments you pass to your component should be as lean as possible. I infer it wouldn't be a good practice to pass entire objects (please correct me if I'm getting it wrong).
For example, if I have a message class:
Class Message < ApplicationRecord
  # body
  # status
  ...
end

To render it, I created the following component
Class MessageComponent < ApplicationComponent
  def initialize(body: , status: )
    @body = body
    @status = status
  end

  private

  attr_reader :body, :status

end

... and the following template
.message
  .message__body = body
  .messate__status = status

In this scenario, how should caching be handled?
I see the following options:

Add a caching option to the render method

render MessageComponent(body: body, status: status), cached: true

Cache directly in the template

- @messages.each do |message|
  - cache message
    = render MessageComponent(body: body, status: status)

If I'm getting the arguments part wrong (see beginning of post) and it is OK to pass an object as an argument, then the component's template could handle caching with something like

- cache message
  .message
    .message__body = body
    .messate__status = status

This would also relate to the question on rendering collections #21
= render MessageComponent, collection: products, cached: true

Thanks in advance!

@pinzonjulian it's exciting to hear that components are working well for you on your project!

By the examples in @joelhawksley 's talk at RailsConf and the examples in the repo, I understood that the arguments you pass to your component should be as lean as possible. I infer it wouldn't be a good practice to pass entire objects (please correct me if I'm getting it wrong).

Honestly, I'm becoming less sure about this as time goes on. I think that it's good to keep interfaces as lean as possible in general, but I don't think it's necessarily a bad thing to pass in an entire object. I don't think view components are any different in regards to this than any other Ruby object.
Said another way: If you have a partial you're replacing with a view component, and that partial relied heavily on being passed an object, I would probably stick to passing in an object if you think it's necessary!

In this scenario, how should caching be handled?

Honestly, I think all three of these proposals have merit, but I'm not sure if any of them would work at the moment. #1 probably wouldn't, but #2/#3 might.
As the design philosophy for this project states, we're trying to make ActionView::Component behave in a manner that is as predictable and consistent with Rails as possible.
That being said, we should probably support all of these interfaces. If you're up for it, I'd welcome a PR 😍

We've been using components for a while in our applications. Thanks to all contributors, ActionView::Component is really great !
We've been thinking a lot about caching a lot because we use extensively Russian doll caching, and collection caching with Rails' syntax where you pass a Proc as the cache key.
I think we should be able to use components exactly like we use (and cache) partials.
This syntax for caching a collection based on each record would be great :
= render ProductCardComponent, collection: products, cached: true

But if we have a component that uses several named arguments, I don't see how it would work (a collection passed a single record).
We probably should also be able to let the parent template cache collections like we are used to :
- cache products do
  = render ProductCardComponent, collection: products

Same problem here with passing named arguments to the component.
Finally there is the possibility of having a Proc for the cache key like we can today, and another for passing arguments to the component. But that seems not elegant at all.
I don't know if it is feasible but this pseudo code "ok" to me :
- cache_each products  do |product|
  = render ProductCardComponent, product: product

And you could pass a proc for the custom cache key like so :
- cache_each products, key: -> { |e| [:special_cache_key, e] }  do |product|
  = render ProductCardComponent, product: product

Or like this, more like we have in Rails :
- cache_each products do |product|
  = render ProductCardComponent, product: product, cached: -> { |e| [:special_cache_key, e] }

Last idea : implementing the cache key inside the component's class so we don't have to specify anything where we call the component. By default, component's class name + arguments.
Sorry if the ideas are a bit blurry :)


ERROR  The "name" argument must be specified

Environment

Operating System: Darwin
Node Version:     v19.7.0
Nuxt Version:     3.2.3
Nitro Version:    2.2.3
Package Manager<EMAIL_ADDRESS>Builder:          vite
User Config:      css, build, vite, modules, googleSignIn, app, i18n
Runtime Modules<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Build Modules:    -

Reproduction
add '@nuxtjs/i18n', to modules in nuxt.config.ts and then run yarn install
Describe the bug
Nuxi 3.2.3                                                                                22:40:13
ERROR  The "name" argument must be specified                                                                                22:40:14
at new NodeError (node:internal/errors:399:5)
at Performance.mark (node:internal/perf/performance:125:13)
at normalizedModule (node_modules/@nuxtjs/i18n/node_modules/@nuxt/kit/dist/index.mjs:168:30)
at async installModule (node_modules/@nuxt/kit/dist/index.mjs:435:15)
at async initNuxt (node_modules/nuxt/dist/index.mjs:2256:7)
at async loadNuxt (node_modules/nuxt/dist/index.mjs:2289:5)
at async loadNuxt (node_modules/@nuxt/kit/dist/index.mjs:522:19)
at async Object.invoke (node_modules/nuxi/dist/chunks/prepare.mjs:30:18)
at async _main (node_modules/nuxi/dist/cli.mjs:50:20)
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/add for documentation about this command.
Additional context
No response
Logs
No response

Hi, please check https://github.com/nuxt/nuxt/issues/19682 and see if that helps!


Fix: emoji suggestion does't reopen on revisit

Details

Fixed Issues

$ https://github.com/Expensify/App/issues/30188
PROPOSAL: https://github.com/Expensify/App/issues/30188#issuecomment-1775578732
Tests

Go to a chat and add :jo in the composer
Verify that the emoji suggestion shows up
Change to another tab or screen and go back to App again
Verify that the emoji suggestion shows up when the App page is focused again

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

Offline tests

Same as tests
QA Steps

Same as tests

[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 approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[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(themeColors.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 a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

https://github.com/Expensify/App/assets/117511920/7ca610b6-a473-4335-8978-0ea0844046b4

Android: mWeb Chrome

https://github.com/Expensify/App/assets/117511920/7dac807f-ff22-4f2e-94dd-9107546a4825

iOS: Native

https://github.com/Expensify/App/assets/117511920/b08e2617-31e5-4ef6-a651-64a9cebfa361

iOS: mWeb Safari

https://github.com/Expensify/App/assets/117511920/913a7a12-fca3-4e95-b0af-2dcd6355cfae

MacOS: Chrome / Safari

https://github.com/Expensify/App/assets/117511920/1faec1b8-1462-4435-a8a2-e49e52861739

MacOS: Desktop

https://github.com/Expensify/App/assets/117511920/8f2dfc98-8766-4f02-a25e-efe5b8b1fd64

@cristipaval Friendly bump :)

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

🚀 Deployed to staging by https://github.com/cristipaval in version: 1.4.3-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
cancelled 🔪

🕸 web 🕸
success ✅

🚀 Deployed to staging by https://github.com/cristipaval in version: 1.4.3-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/AndrewGable in version: 1.4.3-11 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


[BugFix] Fix display auto partition statement incorrect

What type of PR is this：

[x] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Which issues of this PR fixes ：

Fixes #19511
Problem Summary(Required) ：

Checklist:

[x] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[x] I have checked the version labels which the pr will be auto backported to target branch

[x] 3.0
[ ] 2.5
[ ] 2.4
[ ] 2.3

[FE PR Coverage Check]
:disappointed: fail : 1 / 2 (50.00%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/server/GlobalStateMgr.java
0
1
00.00%
[2635]

:large_blue_circle:
com/starrocks/catalog/ExpressionRangePartitionInfo.java
1
1
100.00%
[]

run starrocks_admit_test


[Package Issue]: Docker.DockerDesktop ha the wrong installer link

Please confirm these before moving forward

[X] I have searched for my issue and not found a work-in-progress/duplicate/resolved issue.
[X] I have not been informed if the issue is resolved in a preview version of the winget client.

Category of the issue
Installation issue.
Brief description of your issue
The installer link for Docker.DockerDesktop v4.21.1 is pointing to latest and leading to hash mismatch. Correct link is: https://desktop.docker.com/win/main/amd64/114176/Docker Desktop Installer.exe
Steps to reproduce
winger --id docker.dockerdesktop
Actual behavior
installer hash does not match
Expected behavior
docker desktop installed
Environment
--

Screenshots and Logs
No response

The issue is back with 4.26.0


RunOnFxThread annotation and Interceptor

@RunOnFxThread annotation and interceptor to run methods on JavaFx's UI thread  JavaFX Application Thread inspired by Gluon Ignite

Example usage

VBox vBox = new VBox();

public void start(@Observes @PrimaryStage final Stage stage) {
    Scene scene = new Scene(vBox);
    stage.setScene(scene);
    stage.show();

    try (ExecutorService executorService = Executors.newVirtualThreadPerTaskExecutor()) {
        for (int i = 0; i < 10; i++) {
            executorService.submit(() -> showNode(createExpensiveNode()));
        }
    }
}

Node createExpensiveNode() {
    try {
        TimeUnit.SECONDS.sleep(3);
    } catch (Exception e) {
        e.printStackTrace();
    }
    return new Label(LocalTime.now().toString());
}

@RunOnFxThread
void showNode(Node node) {
    vBox.getChildren().add(node);
}

Also, bonus :

update the documentation
provide a test case

Anyway, this can be done later (and I can help !)

@CodeSimcoe  Thanks for the quick review
Planning to update docs and try to write a test as part of this PR, just need some more time.

I have a concern about testing a graphic application.
We'll need the build process to have a working graphic environment.

I added basic docs page and a test case inspired from #6, have not tested on any CI environment

@all-contributors add @ghazyami for code


Descriptions of children of a schema do not get reproduced in the opened note

Is it a bug? Or a non-yet implemented feature?
From what  I could understand, the description of a schema is passed on to the resulting note obeying to that schema. However, if said schema has children, and children do also have descriptions, children's descriptions are not passed on to their resulting notes.
How to to Reproduce

Open new note based on schema with children which, in turn, have descriptions.
On the resulting note, the description field is empty.

Expected behavior
The expectation is that the children's description gets passed on to the new note based on said schema.

Could you paste a sample schema just to help me understand and reproduce?

@HeuFui - I think we need an example to understand this better, I don't think this is actionable at this time.


Include Build Tag Limitations

Hit an issue today when attempting to use the AddBuildTag command with : within it's name. The build failed reporting an error of ##[error]A potentially dangerous Request.Path value was detected from the client (:). A google search directed me to microsoft/azure-pipelines-agent#2877 which led me to realize the issue was :.
I would like the documentation around Logging Commands updated to include an area to describe restricted characters.

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

ID: 16bf0bbb-8b63-6384-aa33-b5b1e2b8cfe3
Version Independent ID: f4da8dbd-a02f-bbdf-2cf2-60e081339237
Content: Logging commands - Azure Pipelines
Content Source: docs/pipelines/scripts/logging-commands.md
Product: devops
Technology: devops-cicd-scripts
GitHub Login: @juliakm
Microsoft Alias: jukullam

Got the same error trying to add a url as tag.

I have the same problem as @svengrav . Has anyone found a solution?

Hello, all.
I've just tripped over the same issue when trying to set a build tag in a pipeline using an inline bash task, where the tag contains a semi-colon.
My command is:
last_scanned="last_scanned:$(date --utc --iso-8601=seconds)"
echo "##vso[build.addbuildtag]$last_scanned"

The error is:
Async Command Start: Add Build Tag
Async Command End: Add Build Tag
##[error]A potentially dangerous Request.Path value was detected from the client (:).

Does anyone have an example of this working in a pipeline? I'd happily take examples of either Bash or PowerShell.
I'm currently running agent version 2.210.1 on a runner image using ubuntu-20.04.

@lukemaslany-next, @giorgiococci, @svengrav I just posted a workaround for this on a related GH issue: https://github.com/microsoft/azure-pipelines-agent/issues/2877#issuecomment-1292393121

I'll update the article now to include the colon limitation. Please note that there's an active issue for this in the Developer Community. There does not appear to be a way to easily escape the colon.


mod_auth_mellon: 0.12.0 -> 0.13.1

Motivation for this change
latest upstream version
Things done

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

[x] NixOS
[ ] macOS
[ ] Linux

[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

ping @womfoo


Softdeluxe.FreeDownloadManager version <IP_ADDRESS>73

[ ] Have you signed the Contributor License Agreement?
[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.0 schema?

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

Microsoft Reviewers: Open in CodeFlow

i dont think this software is safe, my dns resolver blocks the website from being accessed anyone at microsoft like @KaranKad confirm this?

anyone at microsoft like @KaranKad confirm this?

I don't work at Microsoft actually, and about this software, I think its just ok software I haven't really used it but virustotal scan returns nothing.


Tag only with ST4 on Package Control

Hi!
It would be nice if our page at https://packagecontrol.io/packages/ElixirSyntax only displayed support for ST4. :+1:
PS.: After a little hiatus I'm about to complete a new release. Do you have some time to check it? Two major things: 1. Proper highlighting of argument clauses in a for statement. 2. Commands for running mix test in various ways.

Do we no longer support previous versions?

Not really. The st3 branch still exists but we're not really keeping an eye on it. Is it even installable from ST3? Regardless, it's too much effort to support it as well I think.

Right

I'll do the update after the transfer is done.


[DOC] Add example Jupyter notebooks with new features (stain normalization, batch-load API)

Report needed documentation
Report needed documentation
It would be nice to add Jupyter notebooks that show how to use newly added features.
E.g.,

stain normalization (#273)
batch loading API (related issue: #303)

I recently made a notebook for stain normalization and can make a PR for it soon.


RtcRemoteView.SurfaceView() not working in example project (Flutter Web)

Describe the bug
In dev/flutter2 branch, while running the example project, everything is working fine except for RtcRemoteView.SurfaceView().
To Reproduce
Steps to reproduce the behavior:

Run the example project in dev/flutter2
Go to JoinChannelVideo menu
Join Channel with atleast one remote user.

Expected behavior
Only local video loads, remote videos do not load.
Screenshots
Please see this screen recording where left side are my remote users and right is the local: https://streamable.com/u7aw0p
Desktop (please complete the following information):

OS: MacOS
Browser: Chrome
Version: 92

I have had this same issue. Has anyone figured out the fix?

I have had this same issue. Has anyone figured out the fix?

I haven't had any success. Still looking for a fix.

So, I was able to get it working by making some changes in rtc engine callback handlers where I noticed that whenever a new user joins, the video loads if I run remoteUid = remoteUid.of(remoteUid.reversed) in each of the callback setState methods. But it is still not very reliable.

Interesting I am eager to see what one of the developers has to say about this.

because the video track not be subscribed when the userJoined event is received. I have fixed it.


Vulkan: Volumetric fog looks incorrect for SpotLight3D with shadow enabled, depending on the camera angle

Godot version
4.0.alpha (9d1626b4d)
System information
Fedora 34, GeForce GTX 1080 (NVIDIA 495.46)
Issue description
Volumetric fog looks incorrect for SpotLight3D with shadow enabled, depending on the camera angle. This does not affect OmniLight3D, which looks correct after reloading the scene if shadows were enabled for the first time after enabling volumetric fog. (That issue should be reported separately, but I haven't been able to reproduce it consistently yet.)
When reaching a "broken" camera angle, very little fog albedo will be lit (if any). It flickers on and off depending on the camera angle and position.
Left (green): OmniLight3D with shadow enabled, right (red): SpotLight3D with shadow enabled
Shadows disabled

Shadows enabled with working camera angle

Shadows enabled with broken camera angle

See also this video:
https://user-images.githubusercontent.com/180032/152697632-e21359c1-d77a-467b-9b9a-8ec346745f65.mp4
Steps to reproduce

Place some MeshInstances for the light to cast a shadow.
Enable Shadow in the SpotLight3D.
Enable Volumetric Fog in the Environment resource.

Minimal reproduction project
test_volumetric_fog_point_shadows.zip

As a workaround, use a FogVolume with a Cone shape parented to the SpotLight3D node. It won't be able to have shadows though (but the light itself will still be able to cast shadows).

I've noticed that the range of a spotlight also influences interaction with fog volumes as well as viewing angle. For a spotlight which visibly interacts with fog, extending the range reduces the visible effect of this issue, including making the artifacting easier to see at range.

The above pictures show these effects with a spotlight with a range of 2k, from two different viewing angles.
It's worth noting that even with shadows enabled, the projected effect doesn't interact with cast shadows at all.
Below is setup illistrating an omni light top and a spotlight bottom, both with range 30 and shadows enabled.

Hopefully these observations make it easier to locate a root cause.

Yea i can reproduce this issue in beta 14

not sure if this pr fixes it  https://github.com/godotengine/godot/pull/71832 f

not sure if this pr fixes it #71832

Unfortunately #71832 does not fix this issue

Fixed by #73919.


page kivy install 404 Not Found

https://kivy.org/doc/stable/gettingstarted/installation.html

pip install também n funciona

Fixed now. It ran out of space.


Confusing documentation on property value enumeration about XAML

For example:
>The Direction property is of type FlexDirection, an enumeration with four members:
>
>    Column
ColumnReverse (or "column-reverse" in XAML)
Row, the default
RowReverse (or "row-reverse" in XAML)
column-reverse or row-reverse is actually not XAML, it is CSS, like in:
>    .login-container {
background-color: #803A3F44;
width:300;
height:380;
flex-direction: column-reverse;
}

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

ID: b954b795-b38e-61ff-3ba1-26a0623b97e6
Version Independent ID: 65795b50-24d3-1997-038e-ffdb609eb20b
Content: The Xamarin.Forms FlexLayout - Xamarin
Content Source: docs/xamarin-forms/user-interface/layouts/flex-layout.md
Product: xamarin
GitHub Login: @davidbritch
Microsoft Alias: dabritch

Hi @weldryn,
Both you and the doc are correct! "column-reverse" is CSS, but if you look at the paragraph after the bullets it explains that "column-reverse" is CSS, but can also be used in XAML due to the FlexDirectionTypeConverter class. I've tried it myself and can confirm it works.


Revisit WebSafe Base64 in JSON

The conformance test has been updated to now check for this.
Looks like C++ defaults to trying to do WebSafe decode first, and then fall back to "normal" decode.
Looks like C++ also picked up encoding flag to request WebSafe generation (defaults to off).

PR #656 fixes the decode side of this.
I don't have any immediate plans to add support for writing the alternate encoding.

I don't have any immediate plans to add support for writing the alternate encoding.

Yea, I wasn't sure if it made sense, the fact that C++ seems to favor websafe decode was the part I found interesting.

Closing this out, since I don't think we're planning on directly adding support for encoding into websafe until there is a reason.


Add styled button

- Summary

Cherry picks the first commit from this PR: https://github.com/bdougie/open-sauced/pull/27
I add styled components to the project and then recreate the button and hover styling in a styled Button component, then replace it in the project.
- Test plan
I am going to talk to @bdougie about implementing unit tests with this tonight.

The button styling here should be the same, just using styled components instead of a traditional css sheet:

- Description for the changelog

This PR adds the styled components library to the project and replaces the styling for the Buttons with a styled-component of the button element.
- A picture of a cute animal (not mandatory but encouraged)

Deploy preview processing.
Built with commit 2b6734e552dd8e61da90ab93f720cf1c42a29494
https://app.netlify.com/sites/open-sauced/deploys/5932d588a700c474137d001c

https://deploy-preview-28--open-sauced.netlify.com/


Arrows "prev" and "next" inverted when "Yesterday" range selected

Describe the Bug
When I select "Yesterday" in time range, the arrows seems to be inverted.
Clicking in next arrow goes to next day (+1)
Clicking in prev arrow goes to precedent day (-1)

I click in right arrow [ > ] :

I click in right arrow [ > ] :

I click in right arrow [ > ] :

I click in left arrow [ < ] :

All other ranges seems not to have this issue.
Tested in Firefox and Edge, same problem.
Database
Umami Cloud
Relevant log output
No response
Which browser are you using? (if relevant)
Firefox, Edge
How are you deploying your application? (if relevant)
No response

please assign me to this task.

feel free to put in a PR and we will approve. Thanks.

IS this issue still open @franciscao633

Here is the PR : https://github.com/umami-software/umami/pull/2375

Fixed in v2.9.0.


[All Hosts] (setup) rewrite and expand article for environment setup

Fixes 3231

Docs Build status updates of commit 3882bab:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs/overview/set-up-your-dev-environment.md
:warning:Warning
View
Details

docs/overview/set-up-your-dev-environment.md

Line 79, Column 182: [Warning: bookmark-not-found] Cannot find bookmark '#install-nodejs' in 'overview/set-up-your-dev-environment.md'.
Line 79, Column 223: [Warning: bookmark-not-found] Cannot find bookmark '#install-npm' in 'overview/set-up-your-dev-environment.md'.
Line 129, Column 303: [Warning: file-not-found - See documentation] Invalid file link: '../testing/debug-add-ins-overview'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 735b480:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs/overview/set-up-your-dev-environment.md
:warning:Warning
View
Details

docs/overview/set-up-your-dev-environment.md

Line 79, Column 182: [Warning: bookmark-not-found] Cannot find bookmark '#install-node.js-and-npm' in 'overview/set-up-your-dev-environment.md', did you mean '#install-nodejs-and-npm'?
Line 129, Column 303: [Warning: bookmark-not-found] Cannot find bookmark '#server-side-or-client-side.md' in 'testing/debug-add-ins-overview.md', did you mean '#server-side-or-client-side'?

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 29f521d:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/overview/set-up-your-dev-environment.md
:white_check_mark:Succeeded
View

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

Docs Build status updates of commit 4af474e:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/overview/set-up-your-dev-environment.md
:white_check_mark:Succeeded
View

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


fix: missing include and lib search paths

Added some missing search paths. Getting errors to build some software without them.

@f0rmiga Can you provide some more detail? What library/include paths are missing for you?
In official release tarballs, the only c++ directory I can find in include with headers is include/c++; ditto with lib and .a files (just lib and lib/clang/<ver>/lib/...).
Based on:
https://github.com/grailbio/bazel-toolchain/blob/5fe1b6694b544e7cfcf7550f83f2707d25fff053/toolchain/cc_toolchain_config.bzl#L177
it sounds like you're maybe cross-compiling + looking to use libraries on your local system?

The official 14.0.0 release for Linux x86_64:
clang+llvm-14.0.0-x86_64-linux-gnu-ubuntu-18.04 $ find . -type d -name '*c++*'
./include/c++
./include/x86_64-unknown-linux-gnu/c++

clang+llvm-14.0.0-x86_64-linux-gnu-ubuntu-18.04 $ find . -type f -name 'libc++*.a'
./lib/x86_64-unknown-linux-gnu/libc++.a
./lib/x86_64-unknown-linux-gnu/libc++experimental.a
./lib/x86_64-unknown-linux-gnu/libc++abi.a

I wonder how https://github.com/grailbio/bazel-toolchain/blob/32d7596dd99c608015ba9a20c24b4fd5d03fdad2/toolchain/cc_toolchain_config.bzl#L177-L179 would find these libraries without "-L{}lib/{}".format(toolchain_path_prefix, target_system_name).

Looking at some release tarballs, this seems like a change that was made in 14.0.0 but only for some platforms (so far only SLES12 and x86_64 Ubuntu 18.04 seem to have this subdir):
❯ fd 'libc\+\+.a'
clang+llvm-13.0.0-x86_64-linux-gnu-ubuntu-20.04/lib/libc++.a
clang+llvm-14.0.0-amd64-unknown-freebsd13/lib/libc++.a
clang+llvm-14.0.0-armv7a-linux-gnueabihf/lib/libc++.a
clang+llvm-14.0.0-powerpc64le-linux-ubuntu-18.04/lib/libc++.a
clang+llvm-14.0.0-x86_64-apple-darwin/lib/libc++.a
clang+llvm-14.0.0-x86_64-linux-gnu-ubuntu-18.04/lib/x86_64-unknown-linux-gnu/libc++.a
clang+llvm-14.0.0-x86_64-linux-sles12.4/lib/x86_64-unknown-linux-gnu/libc++.a

I can't tell if this was an intentional change or not; I haven't yet looked into how the release tarballs are actually put together.

Regardless, if this is how some of the 14.0.0 tarballs are laid out we should change bazel-toolchain to match.
My concern is that (IIRC) ld warns if library directories it's given don't exist. I think this is worth avoiding (flooding users that aren't on 14.0.0 + particular platforms with warnings seems pretty suboptimal). Ideally we'd gate adding that -L flag on the existence of lib/<target-triple> but (afaik) there's no clean way to do this from within cc_toolchain_config. We'd need to do the check in a repository rule (llvm_config) and thread through the information.
The alternative is to hardcode the list of version+platforms that have a target subdirectory but I think that's a last resort.

I have not given too much thought to this, but one suggestion could be to also allow a {target_system_name} placeholder in the cxx and link flags attributes at:
https://github.com/grailbio/bazel-toolchain/blob/32d7596dd99c608015ba9a20c24b4fd5d03fdad2/toolchain/rules.bzl#L163
This way, any user who finds themselves in this situation will be able to easily customize the link_flags for their use.
As for good defaults that work for all LLVM release distributions, I don't think there is any harm in adding these locations for non-macOS distributions. AFAIK, lld does not complain about non-existent directories by default, but ld64 on macOS does. But I could be wrong. If lld is complaining about this, then maybe just the above solution of having the users set the link_flags themselves, or setting it up ourselves based on the distribution name (and documenting it in the README) could be OK.

For the GCC toolchain I wrote here, I made it a template that I render from the repository rule. This is one way of passing the information we only have access in the repository rule to the config.

We used to do that before, but it led to very expensive repository refetches (mostly extraction of the downloaded and cached archive file) of the toolchain archive when some things changed. So we separated the configuration and the distribution repos.

I encountered this today as well. I made the same fix locally but only to the BUILD.llvm_repo file. For whatever reason I did not have to update the library search paths in cc_toolchain_config.bzl. Was that a necessary update for you @f0rmiga? I'm wondering if LLVM automatically knows to look in these platform specific dirs somehow. I'm only building Rust so I can imagine it's needed for C++ perhaps.
Are there more things that need to be solved before this can be merged?

I encountered this today as well.

@djmarcin are you also using LLVM 14?

I made the same fix locally but only to the BUILD.llvm_repo file. For whatever reason I did not have to update the library search paths in cc_toolchain_config.bzl. Was that a necessary update for you @f0rmiga? I'm wondering if LLVM automatically knows to look in these platform specific dirs somehow. I'm only building Rust so I can imagine it's needed for C++ perhaps.

This is interesting, I'm not really sure what's going on here. Before you added the target specific dirs to the filegroups in BUILD.llvm_repo were you getting linker errors about libc++ being missing?
Just to be sure, are you using builtin-libc++?

Are there more things that need to be solved before this can be merged?

As mentioned here I want to try checking for the existence of the target specific dir in the repository rule; if that proves too tricky we can fall back to the alternatives @siddharthab described.
I'll put something together later today.

Sent 869212179aff3176e48ba6ee891ce58cead100d3 to update the tested version to be 14. We will need to fix the tests in subsequent revisions.

Verified that we don't need the -L flags at all. clang inserts them if the files are present in the sandbox. Same thing for the include dir; if the files are in the sandbox, clang picks up the dir.
Verified using (this PR rebased on current master, and on my Ubuntu 20.04 machine):
cd tests
bazel build -s --copt=-v --linkopt=--verbose --linkopt=-Wl,--verbose //:stdlib

I am going to merge this change and then remove the -L flags and the builtin_include_dirs in a separate commit.

@rrbutani It looks like this is sorted out but just to close the loop on some questions -- yes I am using LLVM14 and I was getting these errors:
  = note: ld.lld: error: unable to find library -l:libc++.a
          ld.lld: error: unable to find library -l:libc++abi.a
          ld.lld: error: unable to find library -l:libunwind.a
          clang: error: linker command failed with exit code 1 (use -v to see invocation)

Closing the loop. All tests have now been fixed to support LLVM 14, except SUSE (see #143).


Feature/seaclouds management policy

This PR is based on #252 and this contains

seaclouds management policy definition
some DamGenerator required refactoring and fixed
API proxy modifications
JS refactoring
Some examples

Please, could you take a look @rosogon @perezp?

I know it is a long commit and it contains some modifications, fixed and patchs, for example DamGenerator requires a big refactoring, as I mentioned on #262 a model object should be defined and used, but I am not responsible of this part.
SeaCloudsManagementPolicy overload the BasicApplication behavior, the policy is able to manage the application deployment, the rules and sla deployment the grafana's dashboard creation.

Current coverage is 38.38%

Merging #269 into master will increase coverage by +1.65% as of 62de0fa

@@            master    #269   diff @@
======================================
  Files          329     332     +3
  Stmts        12064   12527   +463
  Branches      1548    1594    +46
  Methods          0       0
======================================
+ Hit           4432    4809   +377
+ Partial        449     419    -30
- Missed        7183    7299   +116

Review entire Coverage Diff as of 62de0fa

Powered by Codecov. Updated on successful CI builds.

@kiuby88 : the PR is too big, but I don't see any major failures in it. It has tests, and it has been thoroughly tested. Js code will contain bugs, for sure, but we can fix them later. Ok for me. Please, address perepz comments.

@rosogon thank you for checking the PR. @kiuby88 Let's wait also for @MicheleGuerriero opinion because many files regarding the monitor are being removed or some parts deleted...
That's also the part where I found myself unable to check.

@kiuby88 @perezp I had a look at the code. It carries some changes that impact on the monitoring-dam-generator, but I think this policy could be really useful. Overall I don't see any major issue from the monitoring perspective. Of course something need to be changed/removed from the monitoring-dam-generator since part of its work is now done by this policy, but I think it is the right way. I will stay in touch with @kiuby88 to align the monitoring-dam-generator to this PR.


Data log transmit fail on Android app.

Hi,
I have compiled android app by myself. And I connect pebble with my android device.
But there is empty, when I trigger Tricorder on my pebble time watch.
Could you help me?
Thanks!

This has also happened to me in the iOS app. Have you figured it out?


[SCB-29] add README document for config-apollo

Signed-off-by: lijasonvip<EMAIL_ADDRESS>Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Make sure there is a JIRA issue filed for the change (usually before you start working on it).  Trivial changes like typos do not require a JIRA issue.  Your pull request should address just this issue, without pulling in other changes.
[x] Each commit in the pull request should have a meaningful subject line and body.
[x] Format the pull request title like [SCB-XXX] Fixes bug in ApproximateQuantiles, where you replace SCB-XXX with the appropriate JIRA issue.
[x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[x] Run mvn clean install to make sure basic checks pass. A more thorough check will be performed on your pull request automatically.
[x] If this contribution is large, please file an Apache Individual Contributor License Agreement.

Coverage decreased (-0.02%) to 87.166% when pulling 0f0dcb96261b58e93e76df52462ef78e29338145 on lijasonvip:config-doc into e1137b4002659d3a7e482d3ed4b7a6f226054798 on apache:master.

The referenced manual still use io.servicecomb package， please changed it


Feature/fix double reply error

Current coverage is 97.13% (diff: 100%)

Merging #46 into master will not change coverage

@@             master        #46   diff @@
==========================================
  Files            12         12
  Lines           663        663
  Methods         581        583     +2
  Messages          0          0
  Branches         82         80     -2
==========================================
  Hits            644        644
  Misses           19         19
  Partials          0          0

Powered by Codecov. Last update 5e33d76...a6b1259


[pg] Support USING

Query:
SELECT pg_type.oid, typname
FROM pg_catalog.pg_type
LEFT   JOIN (select ns.oid as nspoid, ns.nspname, r.r
  from pg_namespace as ns
join ( select s.r, (current_schemas(false))[s.r] as nspname
 from generate_series(1, array_upper(current_schemas(false), 1)) as s(r) ) as r          using ( nspname )        ) as sp
ON sp.nspoid = typnamespace
WHERE typname = $1  ORDER BY sp.r, pg_type.oid DESC LIMIT 1

Error:
Status: GENERIC_ERROR
Issues:
<main>:1:1: Error: JoinExpr: unsupported using

#2544


HELP

could someone explain to me how FROM LINE 12 TO 16 work ???
i have allready created a script to download youtube video , but i couldent make to download a playlist with multiple video in it .

Hi Ablil98, do you still have a problem understanding the code?
Do you still need help?

ohhh thank u , i have solved the probleme


Wave shuffling with GPU

Added support for wave-shuffling with GPU.
Kernel adjoint now calls md_fmacc2 in a parallel loop.
Minor cosmetic changes.

Please don't commit this just yet. I will be making a few more changes.

Any suggestions on the error? clang doesn't like that I've used openmp.
/home/travis/build/mrirecon/bart/src/wshfl.o: In function `kern_adjoint':
/home/travis/build/mrirecon/bart/src/wshfl.c:(.text+0x3605): undefined reference to `omp_get_max_threads'
/home/travis/build/mrirecon/bart/src/wshfl.c:(.text+0x380e): undefined reference to `omp_get_thread_num'
clang-5.0: error: linker command failed with exit code 1 (use -v to see invocation)
make[1]: *** [wshfl] Error 1
make[1]: Leaving directory `/home/travis/build/mrirecon/bart'
make: *** [test] Error 2

I think the clang test is compiled without openmp. You should use openmp guards for this. See src/num/mem.c for example

Also - you can test this locally by turning off openmp in the Makefile and running make test. Similarly for other Makefile options

Gotcha, thanks! I think I pushed the same fix right around when you commented.


feat: support multiplexing

This PR is for #93

Revised according to the above suggestions

lgtm thanks @woluohenga for this and the refacotry.


Need example to integrate with 3rd party react component such as gridjs

Please give example on adding react component e.g, https://www.npmjs.com/package/gridjs-react
I like to port my streamlit app to fasthtml
Thanks

Just an idea. Since Grid.js works with Vanilla, you can add the JS and CSS to the head of the HTML passing default_hdrs=False and then the appropriate headers like this


Poor consolidation performance with long-terminating nodes

Description
Observed Behavior:
When long-terminating nodes (because of pods with high terminationGracePeriodSeconds  values (hours / tens of hours)) are present in the cluster, one can observe significant consolidation performance degradation resulting in "normal" (as in without long-terminating-pods) underutilized nodes not seeing any consolidation actions for days.
What we've observed in our case - a lot of logs from logAbnormalRuns https://github.com/aws/karpenter-core/blob/edebd24b102814b7c2048b292cc7b0e47d68a822/pkg/controllers/deprovisioning/controller.go#L333-L342 indicating long reconcile loops - tens of minutes.
This is likely because when we delete nodes, we sequentially wait for them (with back-off) up to 10m each:
https://github.com/aws/karpenter-core/blob/edebd24b102814b7c2048b292cc7b0e47d68a822/pkg/controllers/deprovisioning/controller.go#L201C1-L203
https://github.com/aws/karpenter-core/blob/edebd24b102814b7c2048b292cc7b0e47d68a822/pkg/controllers/deprovisioning/controller.go#L67C1-L75
Is there a reason for waiting for the termination sequentially and not in parallel 🤔 ? Also it seems that if we reach a timeout (could it be made configurable ? - it could improve the reconcile loop duration when multiple long-terminating nodes are waited for), any retry errors are actually ignored.
At the same time, because the deprovisioning controller doesn't seem to allow for concurrent reconciles (controller_runtime_max_concurrent_reconciles shows 1), we begin to see consolidations performed very infrequently (and some nodes not getting consolidated for days).
In our case, there seem to be a single workload using a single worker group and provisioner that causes consolidation performance disruption for the entire cluster (it might be ok to see a degraded consolidation performance for nodes provisioned by just this one provisioner but it seems that there is no "isolation"). Moving the worker group to be managed by cluster-autoscaler instead improved the consolidation performance (attaching some graphs showing that both the reconcile frequency and consolidation performance greatly improved afterwards)

Expected Behavior:
The expected behavior would be to:

worst case: see consolidation performance degradation limited to the provisioners that have added the nodes that are long-terminating (maybe have separate reconcile loops for nodes managed by different provisioners)
best case: not see any noticable consolidation performance degradation (parallelization of node termination waits could help, so could possibility of termination timeout configuration)

Reproduction Steps (Please include YAML):
Versions:

Chart Version: v0.27.6
Kubernetes Version: 1.24

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

Linking #542 since this relates to parallelizing the wait so that we don't get stuck waiting for the nodes to fully terminate due to long terminationGracePeriodSeconds.

There's also this mega-issue #370 that's tracking a list of items to improve the speed and efficacy of deprovisioning.

Closing in favor of #370


sync the changed schema to sqlite sql file.

Just noticed the UT will fail if the schema is not synced, closing.


Build fails

I just synced up and tried to clean and rebuild PSharp.sln.  I got the following errors:
Severity	Code	Description	Project	File	Line
Error		Metadata file 'C:\Users\qadeer\Work\PSharp\Binaries\Debug\Microsoft.PSharp.SystematicTesting.dll' could not be found	SystematicTesting.Tests.Unit	C:\Users\qadeer\Work\PSharp\Test\SystematicTesting.Tests.Unit\CSC
Error		Metadata file 'C:\Users\qadeer\Work\PSharp\Binaries\Debug\Microsoft.PSharp.SystematicTesting.dll' could not be found	Tester	C:\Users\qadeer\Work\PSharp\Tools\Tester\CSC

Hi Shaz, can you try build in Release mode? Is this only happening in the Debug build? I cant seem to reproduce this. From the error description it seems the SystematicTesting.dll is not being picked up by these 2 projects.

On 28 Mar 2016, at 10:30, Shaz Qadeer<EMAIL_ADDRESS>wrote:
I just synced up and tried to clean and rebuild PSharp.sln. I got the following errors:
Severity Code Description Project File Line
Error Metadata file 'C:\Users\qadeer\Work\PSharp\Binaries\Debug\Microsoft.PSharp.SystematicTesting.dll' could not be found SystematicTesting.Tests.Unit C:\Users\qadeer\Work\PSharp\Test\SystematicTesting.Tests.Unit\CSC
Error Metadata file 'C:\Users\qadeer\Work\PSharp\Binaries\Debug\Microsoft.PSharp.SystematicTesting.dll' could not be found Tester C:\Users\qadeer\Work\PSharp\Tools\Tester\CSC
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub

I looked more carefully.  A couple  of dependencies on SystematicTesting were missing in PSharp.sln.  I added those and now it works fine for me.  I have checked my changes in.  Please take a look.


Use admin creds if user is in GH groupcluster-admins

NOTE: This is broken as it turned out we don't use the app_metadata anymore so back to square one. CC: @djsd123
What

Users log in using just GitHub
We'll use the admin credentials if user is in cluster-admins (read from user's app_context)
Re-enabled silent SSO

Ticket
https://trello.com/c/rKfx3jDe/699-2-kibana-auth-proxy-to-determine-if-user-is-admin-by-using-gh-groups-and-re-enable-silent-sso

Closing this (at least for now) as it seems like it may be a can of worms and it's strictly not part of sprint (be sure things still work after 1st April deprecation) and more like a nice to have anyway.


Port seaport tests

This is an ongoing PR adressing #6

@tekkac Please have a look I think this should be merged before the beginning of the hack as it introduces a lot of improvements.


Host based route issues with Kong 2.5

Summary
Kong version 2.5
We're having issue with Host based routing since we upgraded to 2.5 from 2.0.
When I define ingresses/KongIngresses for 2 separate hosts:
Ingresses:
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: hosta-portal
namespace: devops
annotations:
konghq.com/override: https-only
konghq.com/plugins: hosta-allowed-ips
kubernetes.io/ingress.class: kong
spec:
tls:

hosts:
hosta.com
secretName: hosta-tls-csi
rules:
host: hosta.com
http:
paths:
path: /
pathType: ImplementationSpecific
backend:
service:
name: hosta-portal
port:
number: 80

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: hostb-portal
namespace: devops
annotations:
konghq.com/override: https-only
kubernetes.io/ingress.class: kong
spec:
tls:

hosts:
hostb.com
secretName: hostb-tls-csi
rules:
host: hostb.com
http:
paths:
path: /
pathType: ImplementationSpecific
backend:
service:
name: hostb-portal
port:
number: 80

Kong Ingresses:
apiVersion: configuration.konghq.com/v1
kind: KongIngress
metadata:
name: hosta-portal
namespace: devops
route:
https_redirect_status_code: 302
path_handling: v0
protocols:

https
strip_path: true

apiVersion: configuration.konghq.com/v1
kind: KongIngress
metadata:
name: hostb-portal
namespace: devops
route:
https_redirect_status_code: 302
path_handling: v0
protocols:

https
strip_path: true

With this definition hosta.com and hostb.com both are performing the allow ip check even though I only have the Plugin reference on hosta and both route to the same backend service.
This worked just fine before we upgraded to 2.5
Has the method of defying host based routing changed since 2.0
@PaulFischer-Kong

Hi, are you able to access Kong's Admin API? If so, please access

/services/hosta-portal/plugins and
/services/hostb-portal/plugins

And check whether the allowed ips plugin appears in both, or only in one.

Actually It appeared on either one. I tried adding the sniper annotation to the ingress this morning and that seems that have cleared up the issue.

closing because it seemed to be an isolated event.  please reopen if the issue persists (or reappears)


Proposal for small improvement

Hello,
Thanks a lot for that VERY nice script.
I would propose to add in uninstall function:
ip link delete dev ${SERVER_WG_NIC}

The interface should already be automatically removed. What OS did you have this issue on?

That's true. Interface is automatically removed.
I had that issue when wg exited on bug
I forgot I opened this issue on github !


Permit middleware process_request to occur after routing

Change middleware behavior so that the presence of a middleware object field would enable process_request to happen after routing has occurred, while also providing access to the resource object.
Issue #400

Closing until I address tests


Add down arrow to the asset dropdowns

As a vortex user, i should be able to select different offramp pairs from the UI
Acceptance criteria

Currently the asset dropdown is unclear if it provides more than one option i.e EUR and ARS
Add a downward arrow to both the assets dropdown [Reference provided]

Reference

Hey team! Please add your planning poker estimate with Zenhub @ebma @gianfra-t @Sharqiewicz @TorstenStueber


Measurment Shortcut Mode

When taking a measurement, if a user switches to "Shortcut Mode", takes a measurement then clicks "Go to Last Spot Created" a new spot is created at your current location instead of going to the last spot created.
One solution might be to just remove shortcut mode. It doesn't seem to be an essential feature and none of the other pages use it.
RPReplay_Final1650990695.mov.zip

Hi @ellennelson10.  The way you are describing the shortcut mode is the correct behavior that @nicolasmroberts wanted.  When the modal is in shortcut mode and a measurement is made then a new spot is created at your current location. All of the shortcut mode buttons create a new spot at your location while doing the assigned task.

@ellennelson10 Can you and @nicolasmroberts talk about whether you want a user to have the ability to go to the Shortcut modal from the Notebook modal and vice versa?  It is easy to take that out.

@NathanNovak We are just going to leave this for the time being.

Ok then closing this issue


Create desktop style for custom 404 page

https://help.github.com/en/github/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site


ServiceBus: exposing AutoRenewTimeout setting to host.json

Addresses #1026
I was able to verify that the default Service Bus AutoRenewTimeout value is 5 minutes, which explains the timing in the filed bug. This allows you to override that.

:ship:


Add @rollup/plugin-replace to vite

https://github.com/rollup/plugins/tree/master/packages/replace

use vite-plugin-replace


slybot jsonschema validation is broken with jsonschema >= 2.0.0

jsonschema >= 2.0.0 changed the way Draft3Validator is created, so this method: https://github.com/scrapinghub/portia/blob/7ab8dd990b946e92a928a6692ecd4706e60b5930/slybot/slybot/validation/schema.py#L21 does nothing.
Tests are failing for slybot:
======================================================================
FAIL: test_invalid_url (test_schema_validation.JsonSchemaTest)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/Users/kmike/svn/slybot/slybot/tests/test_schema_validation.py", line 66, in test_invalid_url
    self.assertRaisesRegexp(ValidationError, "Invalid url:", validator.validate, obj)
  File "/Users/kmike/svn/slybot/slybot/tests/test_schema_validation.py", line 23, in assertRaisesRegexp
    raise AssertionError("%s not raised" % eclass.__name__)
AssertionError: ValidationError not raised

======================================================================
FAIL: test_regex_formatting_wrong (test_schema_validation.JsonSchemaTest)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/Users/kmike/svn/slybot/slybot/tests/test_schema_validation.py", line 35, in test_regex_formatting_wrong
    validator.validate, obj)
  File "/Users/kmike/svn/slybot/slybot/tests/test_schema_validation.py", line 23, in assertRaisesRegexp
    raise AssertionError("%s not raised" % eclass.__name__)
AssertionError: ValidationError not raised

----------------------------------------------------------------------

The tests need to be updated but this issue has been resolved.


Make GitHub reporter sleep when ratelimited

Fixes #699.

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

Project coverage is 94.74%. Comparing base (9155063) to head (d399b51).
Report is 2 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1051   +/-   ##
=======================================
  Coverage   94.74%   94.74%
=======================================
  Files          99       99
  Lines        9932     9941    +9
=======================================
+ Hits         9410     9419    +9
  Misses        366      366
  Partials      156      156

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


Theme color not applied

First thanks for the great theme !
Seems changing the theme_color attribute under config.toml -> [extra] -> theme_color does not change anything.
[extra]
theme_color = "#000"

I am missing something ?

It's a meta tag, and it's just valid for the Chrome  browser on Android devices. See also: “Chrome Mobile color bar theme-color meta tag not working”.

Ah sorry I misunderstood the meaning of the tag. I guess you can close this then.


An example project is needed

Hi, I was looking into trpc and saw that you have a remix-adapter.
The readme minimal setup is very confusing for me.
Would you be able to create an example project?
Thanks in advance

+1 for an example.
I am a huge Remix fan but something I've been interested in is exposing a tRPC endpoint for my react-native mobile app to consume.
Wondering if this is a path I could take towards that?
Ideally - id have a monorepo with remix + RN and a domain/service layer with Prisma that could be shared.
I could see Remix calling the domain layer directly or via tRPC
Lastly, curious about the viability of deploying something like that on vercel serverless.

I am also looking for some better examples of integrating tRPC with Remix. I have a few pages in Remix that have a lot of small mutations (e.g. add, edit, delete, like, etc.) I currently am using individual resource routes for each of these actions. But it feels "strange". I also experimented with having all the mutations post back to the page route and using hidden form values to determine what "action" to carry out. All of these approaches seem off to me.
I love Remix for the simplicity of data loading on the server and posting back to the same route for an action, but when you start to get a lot of interactivity on a single page, then the backend code starts to get a little messy (e.g. separate resource routes or switch statements in a single action handler).
My thought was to reach for tRPC and have a single tRPC api route and then define my procedures accordingly. But, this site is the ONLY place I have seen any kind of thought about using these together. But, the example is not quite clear to me. If anyone has any other resources, I would love to know about them. Thanks!


[FIX] Update control property

After an error from setting a new value of a control property, the value should return back to the initial one.

Nice :+1:


why webpack 4 is solwer than webpack3 both in development

node v8.10.0
npm 5.6.0
os mac
webpack 4.6.0

@jinxin479 Please use issue template, also please provide your configuration and/or minimum reproducible test repo. Thanks!

Could be a duplicate of #6767?


runtime: Stack() calls lock against each other unnecessarily, even when single-goroutine

What version of Go are you using (go version)?

$ go version
1.19.2

Does this issue reproduce with the latest release?
y
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
(encountered on Linux but I assume it shows up everywhere)

What did you do?
I saw a profile that showed 85% of CPU time in calls to runtime.Stack(), and 81% of total CPU time in calls to printlock and printunlock.
What did you expect to see?
I expected calls that were independent of each other, writing into buffers rather than to shared streams, on different CPUs, to proceed without lock contention.
What did you see instead?
Every single write in any part of the traceback process goes through print (and friends) ultimately, which means that it uses printlock and printunlock. This is true even when g.writebuf is non-nil and the different gs will be writing into different buffers. As a result, the stack tracebacks block each other, and since they're both making large numbers of individual calls to print, that results in heavy lock contention. (To complicate things, there's cases where a non-nil g.writebuf still doesn't cause the writes to go into the buffer, as when gp.m is dying.)
This looks like a mess to fix. It's "easy" to fix by changing the code to thread a write target through it, except that you absolutely don't want any of this code dealing with stuff like io.Writer or other higher-level abstractions. I also don't know whether it's actually completely safe to have multiple copies of print running, against different write buffers, on different gs. In the case where you really are writing to a stream, you probably don't want a buffer. You don't want to have two copies of all of this code, identical except for their output. But having two calls to runtime.Stack() generate hundreds of contended locks seems pretty bad too...

cc @golang/runtime

In triage this doesn't seem like high priority to look at. Stack could probably avoid the printlock but that might be tricky today. This might be more doable if we clean up gentraceback in general (CC @aclements).

There was also some discussion in the Gophers Slack about one possible hack fix:
 func printlock() {
-       mp := getg().m
+       gp := getg()
+       if gp.writebuf != nil {
+               return
+       }
+       mp := gp.m

(and the same for printunlock)

That's not the only reason printlock exists.  It also ensures that if two goroutines call print in parallel with multiple arguments then the output will not be interleaved.

Right. But if I read the code correctly (big if), when gp.writebuf is non-nil, we are always non-concurrent.

I am indeed quite aware of that. :)
In those cases, however, gp.writebuf is nil (the output goes straight to stderr). gp.writebuf is only non-nil for runtime.Stack and a runtime tests.

Sure, but my point was that if two different goroutines call print in parallel with multiple arguments, their output will not be interleaved.  And that still seems true to me.  Am I missing something?
(It's true that the output from print can be interleaved with other output that the program might be writing to standard error.  That seems harder to avoid, though as you imply it could be done by setting writebuf.)

Am I missing something?

I hope so? :P
The idea of the patch above was that we effectively disable printlock and printunlock only on the relevant G when its writebuf is non-nil. writebuf is non-nil only when runtime.Stack is actively using its (systemstack's) G to print a stack. All other goroutines that are printing will have nil writebufs, and the locking will proceed as usual.

Argh, sorry, I get it now.  Completely misunderstood.  Apologies.

I did note that runtime.Callers produces part of this data without locking, but there's no way to get the argument info, if you want it, and also there's no easy way to just get the pretty-printed output. So, it solves the performance problem but it loses information; so far as I can tell, there's nothing available to a user that can produce the call stack with args that isn't this.
So far as I can tell, writebuf can only be non-nil during a call to runtime.Stack(), and during one specific test that also assigns to it for some reason. There's no other uses in the code.
So I think in practice the "just dummy out locks when writebuf is non-nil" behavior would be correct, but I'd feel a bit nervous about it being brittle. I'm also not 100% sure I know what it would do in the case where you request tracebacks for all goroutines, but I assume it works. (I also note that if you request tracebacks for all goroutines, the world is stopped, so, good news, no lock contention, bad news, you already took every performance hit.)
That said, I'm certainly not about to volunteer to try to make the traceback stuff work differently, that looks like a really hard problem.


Notifications for calendar events you've favorited

This actually shouldn't be that hard. We could check if you have a favorited calendar event in the next 5 minutes when we check for messages.
(Actually scheduling notifications is a non-starter because on the cruise time zones are a disaster.)

using GET /api/v2/event/mine/:epoch, if we can figure out what :epoch should be...

I can get the epoch from the server by asking out for its time!


Added node selectors for redis and mysql

Added node selectors for redis and mysql in the db template.
The db resources now have another option for node pool allocation.

Thanks can you give me an example of how this would be used?


log ops that take >1 second

KV engine logs slow ops that take > 1 second, which has proven helpful for production issue diagnosis

You may want to consider using Dustin's "yellow" library for this.
https://github.com/dustin/yellow

Looks like it was too simple to need another library.  commit 0d323e07
THere's a new optional cmd-line flag, called "options", which allow for open-ended key=value parameters.  Example usage of the "slowQueryLogTimeout" option...
./cbft ... -options=slowQueryLogTimeout=100ms
./cbft ... -options=slowQueryLogTimeout=5s
./cbft ... -options=slowQueryLogTimeout=10s

When there's a slow query, we'll see output in the log like...
2015/09/22 21:34:47 slow-query: index: bsa, query: {"q":"beer","indexName":"bsa","size":10,"from":0,"explain":true,"highlight":{},"query":{"boost":1,"query":"beer"},"fields":["*"],"ctl":{"consistency":{"level":"","vectors":{}},"timeout":0}}, duration: 86.558171ms, err: <nil>


The Important points to note line about immediately visible to all users should be highlighted near the top of the document

This line, which is the first Important points to note: "Every time you start designing, you're effectively creating a new extension. Your changes are immediately visible to other users" is critically important and could be missed by someone scanning the page. It should be copied up to the top and appear in the colored box with the only available in Sandbox note. I would suggest that you leave it where it currently is, but also show it above as noted.

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

ID: 2e31ad37-068e-3007-2e46-7afc15f6b73b
Version Independent ID: cd16bd61-cd0d-be6b-0af7-c1e9d81c81f5
Content: Using Designer - Business Central
Content Source: dev-itpro/developer/devenv-inclient-designer.md
Service: dynamics365-business-central
GitHub Login: @SusanneWindfeldPedersen
Microsoft Alias: solsen

Thanks for the feedback. Yes, I agree - this note will be moved up for better visibility - available with the next doc refresh. Thanks!


FIX-#3571: fallback to 'sort=True' on categorical keys in groupby

Signed-off-by: Dmitry Chigarev<EMAIL_ADDRESS>
What do these changes do?

[x] commit message follows format outlined here
[x] passes flake8 modin/ asv_bench/benchmarks scripts/doc_checker.py
[x] passes black --check modin/ asv_bench/benchmarks scripts/doc_checker.py
[x] signed commit with git commit -s
[x] Resolves #3571
[x] tests added and passing
[x] module layout described at docs/developer/architecture.rst is up-to-date

Since this PR doesn't fix the actual problem but just hiding it, we should keep the #3571 open after the PR is merged.

@RehanSD do you have any more comments?

Looks good to me!


Cannot send emails on Google Cloud

Tried many email servers and settings, cPanel and Gmail as well. Working fine on VPS but not on Google Cloud Instance.
Logs
[2020-10-08 10:55:55.994][request][INFO] POST /admin/test/smtp/
[2020-10-08 10:56:11.645][error][ERROR] SmtpError.
[CAUSE] Io(
Os {
code: 11,
kind: WouldBlock,
message: "Resource temporarily unavailable",
},
)
[2020-10-08 10:56:11.645][response][INFO] POST /admin/test/smtp (test_smtp) => 400 Bad Request

That log is from BitwardenRS? Are you configuring e-mail through .env before launching docker-compose?

Closing pending further comment


[T4][T01-T3]

@yogamurti @radneran @maltiso @teoshuqi
Some comments added. Please close the PR after reading comments.


Create a contact info block

Add links to social networks (LinkedIn, Facebook, Instagram), phone number, email, Telegram username, etc.

done adding social media links


NotBlankString.get variants

Description
Add the following functions to the NotBlankString type:

getOrNull(index: PositiveInt): Char that should return the character at the specified index, or should return null if the index is out of bounds.
getOrElse(index: PositiveInt, defaultValue: (PositiveInt) -> Char): Char that should return the character at the specified index, or should return the result of calling the defaultValue function if the index is out of bounds.

Checklist

[ ] Implement.
[ ] Test.
[ ] Refactor.
[ ] Update Work in progress section in changelog.

The getOrNull operation is already available for JVM and Native platforms only.


MAINT: backports prior to 1.5.0rc1

Includes:

#12217

PR/cognate issue added to release notes as well

#12227

PR added to release notes, but not the cognate issue, which was reopened

#12236

PR added to release notes; there was no matching issue

32-bit windows Azure CI misbehaving; trying another restart there. ARM64 Travis timeout not related.

Thanks Tyler.

Very exciting to see yet another version thanks to your efforts.


Updated Ruby code block markdown syntax

Submitted per #1446
This pull request updates the feature and Markdown files to have the Ruby code blocks be recognized as such. In the feature files, the code block was indented one too far and so it appears to have been taken as part of quoted text. On the README files, the code blocks weren't delineated at all.
Running rake tests after this change showed no differences in Cucumbers output, but the Middleman display now shows proper code blocks.

Thank you!
As far as I remember, we publish docs for a released version, manually. So once we have a minor version, we’ll publish this.
Similar PRs to other repos are much appreciated.

Similar PRs to other repos are much appreciated.

From my initial look, this repo had the most corrections. I'm poking at the others as well to make sure of that. Thanks!

These have been published, they don't change the output though because our syntax highlighting on features at least don't support the extra information I guess

Actually, it did! I still have a copy of the code from before the changes were pushed and this is what the front page of rspec-expectations 3.12 used to look like:

As of this morning, syntax highlighting works:

Thank you for pushing these changes live! Have a great day,

Looks great with highlighting !
I think Jon meant that feature files don’t get highlighted. But the markdown ones surely are.
I’ve noticed an increased indentation in your screenshot.
Thanks for all the hard work, @threeplanetssoftware . I know, our docs are not easy to improve.


Connection between OpenCR and Intel NUC

Hi,
I'm learning ROS and going to make my own custom robot. It may be OP3-like robot, based on OpenCR & XL-430 (for more economical).  Before I buy these items, I would like to know something.
Q: How OpenCR "physically" connect to Intel NUC on OP3?
The picture on e-manual, there's only one USB port for firmware download (not always connect to NUC), right?

Hi,
We used a U2D2 to connect between NUC and OP3.
[NUC] ---(USB)--- [U2D2] ---(RS485)--- [DXL and OpenCR]
If you make the own firmware for OpenCR, you don't have to connect like this.
you can connect the OpenCR directly (using micro USB port).

Hi Kayman,
Yes. Understand.
I prefer the way of connection in OP3. I think it makes robot look compact and tidy by internal connection. There's no messy external wire.
Thanks again for your support.


🙋 Pick the color of the item icon in timeline

Hi
I was trying to set the background color of my icon in the timeline plugin.
I thought it was through the key attribute, but I didn't manage to do so.
The sample key: pink in the documentation doesn't work :(
Is it possible ? If so, how ?
Thank you for the help :)

Hi @yodamad
I verified the key property works as documented: it applies CSS classes to elements, which enables styling.
Consider this example, to set the background color of icons in a timeline:

adding a key property to specify a CSS class for the HTML elements

::timeline:: class="epic-timeline"
- title: Zeus does something
  content: ...
  icon: ./img/icons/001-zeus.png
  sub_title: Turn 1
  key: zeus
::/timeline::

Then you would include a CSS rule in your custom style sheet for MkDocs to override the background color of dots, for example:
.nt-timeline-dot.zeus.bigger {
  background: gold;
  border-color: gold;
}

Both the .nt-timeline-item and the .nt-timeline-dot elements include the configured class.

👍 Thank you it works
Misread the documentation


Add modules dependencies

Added a vendor directory to keep track of module dependencies
Signed off by: Priyanka Jiandani<EMAIL_ADDRESS>

@priyanka19-98  because the project didn't modify the code of dependncy, so i think there is no need to add vendor. thanks for your suggestion.

@priyanka19-98 because the project didn't modify the code of dependncy, so i think there is no need to add vendor. thanks for your suggestion.

makes sense. Closing the PR.


[vcpkg/scripts/make] determine whether to use automake wrappers

USE_WRAPPERS should not be a option from portfiles. It should only depend on compiler tools.
Using ar-lib to wrap GNU ar will result in error
ar: invalid option -- 'L'

Oh, I'm fighting with this too. I would have changes for the whole file, but there seem to be other PRs pending (targeting Android). The more minimal attempts:
https://github.com/dg0yt/vcpkg/commit/7bd9735b67c59bbd01ce6d4bfac3c7b5594ad673  (used during the last days)
https://github.com/dg0yt/vcpkg/commit/5d7f9ae8e1f1cf6399adf099e7a44f1770c0ea36   (just testing now)

@dg0yt Once the PRs targeting Android get approved and merged, I would try to make CMAKE_HOST_WIN32-only parts to be common for all hosts to enable cross compiling. This PR is also prepared for that.

/azp run

There is only libtasn1 and libidn2 failing now, on x64_osc, in the gtkdocize step while running autoconf. Confirmed to be fixed by brew install autoconf automake gtk-doc.

This is mandatory for mingw on linux. Merge conflict resolution proposed at https://github.com/huangqinjin/vcpkg/pull/1. I hope it gets resolved before new conflicts arrive.

Seems that the issue I am having with Windows support for libtasn1 is related: https://github.com/microsoft/vcpkg/pull/16953#issuecomment-820979602

Seems that the issue I am having with Windows support for libtasn1 is related: #16953 (comment)

I don't think so. Your issue is with windows triplets. This PR is for mingw triplets, and the libtasn1 issues on osx were not related to wrappers.

I don't think so. Your issue is with windows triplets. This PR is for mingw triplets, and the libtasn1 issues on osx were not related to wrappers.

Not sure why you bring up macOS – #16953 is specifically to fix Windows build, and indeed this PR does fix the ar-lib call for me.

This LGTM, thanks for the PR!


Postgres 9.5devel - SKIP LOCKED

I would like to share info at Postgres 9.5devel will support SELECT ... FOR UPDATE SKIP LOCKED. This will be great and we can optimize the code when it is released.

Not everyone has a possibility to upgrade PostgreSQL to desired version :cry: Implement different behavior depending on version? It is also applies to #84 — we cannot rely on jsonb since it's only for >= 9.4

Well... we should add an if statement :).

Hmm... Am I sure that it's useless since Que does job locking using advisory locks, not by SELECT ... FOR UPDATE?
I think, it can be useful for queue_classic but not for Que.

I think the point is that you could avoid the complexity of advisory locks.
Might be worth looking at if it speeds things up.
You'd have to have two versions of the locking code though, until 9.4 and
earlier aren't supported anymore, probably 8 years out.
On Tuesday, February 10, 2015, Vladimir Kochnev<EMAIL_ADDRESS>wrote:

Hmm... Am I sure that it's useless since Que does job locking using
advisory locks, not by SELECT ... FOR UPDATE?
I think, it can be useful for queue_classic
https://github.com/QueueClassic/queue_classic but not for Que.
—
Reply to this email directly or view it on GitHub
https://github.com/chanks/que/issues/87#issuecomment-73710516.

Yeah, I've read about it. One of the advantages of using advisory locks is that they're more robust in terms of failure recovery - if a process goes down, Postgres cleans up the locks for us and they can be picked up immediately by other workers, and you don't have the complexity and uncertainty of locked_at/locked_by columns. So I don't see us giving up advisory locks entirely anytime soon. It'd be very useful for DelayedJob and QueueClassic, though.
It's possible that we might be able to somehow use SKIP LOCKED to speed up the job lock query, though, to handle contention by multiple workers during locking, but I doubt it'd result in nearly the speed boost for Que as it would for DelayedJob or QueueClassic.


Sendrecv not working in Chrome, only in safari

I am using sendrecv and when i open up the index.html, I am able to connect to the local server (signalling). However, when I send an rtsp stream to the index.html using sendrecv/gst/webrtc-sendrecv.py, i only see the video on safari (for a few seconds and freezes) but nothing on chrome, internet explorer, or firefox. What can be causing this issue?

Are you sending H.264?

Currently yes

You need to ensure that you're using the baseline or constrained-baseline profile with H.264. You need to check that the incoming RTSP stream is using that profile. If not, you need to decode and re-encode.

I see. Sorry the given sample sendrecv is not working on chrome. Just the videotestsrc (without using h264) is not showing on chrome. Currently have signaling Python server running locally, index.html opened waiting to receive call, and sendrecv.py running with the id shown on html. The connection is successful but no video shows

I'm having the same problem. I had a working environment about two months ago and now when I returned to the project it doesn't work in Chrome anymore. Then tried the  webrtc_sendrecv.py  and the same. Working in Safari but not Chrome. Checked if related to this issue but the problem remains. Any ideas or other reports about this issue?

Just an update. I have tested the ICE candidates generation with Trickle ICE and the problem with Chrome remains. No ICE candidates are generated in Chrome. What is more odd is that Trickle ICE works fine when I use Chrome in incognito mode.

are you testing on a local network? Perhaps you are running into https://gitlab.freedesktop.org/gstreamer/gst-plugins-bad/issues/1139 ?

These examples have moved to https://gitlab.freedesktop.org/gstreamer/gst-examples/-/tree/master/webrtc and this repository will not be updated further.


chore: refactor base multiplier

Resolves #494

@0xcodercrane can you review this

I will wait for the configuration change PR on production version. @rndquu

https://github.com/ubiquity/ubiquibot-config/pull/4
https://github.com/ubiquibot/ubiquibot-config/pull/3
https://github.com/ubiquity/ubiquibot/pull/559
https://github.com/ubiquity/ubiquity-dollar/pull/741


Question 42: answer differs in node and browser

In Node.js setInterval returns Timeout instance, not unique id.

Thanks for your input! Will rephrase the question 👍