[VS Code] Service not available: DebuggerHostService

Error:
Service not available: DebuggerHostService
Steps to Reproduce:

Version Data

extensionName
VSLS

extensionVersion
0.3.395

protocolVersion
2.2

applicationName
VSCode

applicationVersion
1.25.0

platformName
Linux

platformVersion
4.15.0-23-generic

@ogeday26 Thanks for reporting this issue, we are aware of it and working on a fix. Closing as a duplicate of #696.


Fix Memoryleak

https://github.com/cefsharp/Puppeteer/discussions/30
Please check if freeing _httpRequestsMap has any impact on the whole API

Did you run the unit tests?
You've reformatted the whole class so it's impossible to review, revert the formatting changes.

https://github.com/cefsharp/Puppeteer/blob/main/CONTRIBUTING.md#code-style

I actually only added one line. No idea why GitHub makes everything green. Look at line 24 in the green field. That has been added. Unfortunately, the unit test failed for me. Something caused problems. :(
Line +24: _httpRequestsMap.TryRemove(requestId, out _);

You've changed the formatting of the whole file. Most likely you've converted the tabs to spaces or vice versa.
Run the unit tests without your change for comparison. Make sure you generated the certificate as per the contributing guide.

I passed the test successfully. I have no idea why that happened. I made the pull request through GitHub (website) not through Visual Studio. Via the edit pen at this link. I just added the line there. (https://github.com/cefsharp/Puppeteer/blob/main/lib/PuppeteerSharp/NetworkEventManager.cs)

Just look at line 24 in the green and check your source code. You should know best if that could cause any problems or why things are stored there at all. The familiarization with your source code to fix the memory leak also cost me 4 hours. It shouldn't be a problem to check yours now.

Puppeteer currently manages to eat up to 1GB of RAM within a loop that runs for around 1 - 2 hours. Puppeteer is currently unusable. :(
The more I read from the website, the more it becomes around 0.5MB - 1MB per read.


New match brand logic.

Вітаю!
Problem:
After adding new brand which intersects with existed brand prefix but with more accurate prefix, detector still return old brand value.
Example:
We have brand maestro with prefix 505. We add new brand kortimilli with more accurate prefix 505827028.
CreditCardValidations::Detector.add_brand(:kortimilli, length: 15, prefixes: '505827028')
But detector still return maestro instead kortimilli
CreditCardValidations::Detector.new('505827028341713').brand # => :maestro
Solution:
Instead of returning first matched by prefix brand, we get all matched and return one with more accurate prefix length.

@Fivell, could you review please?

@pavelgyravel  thanks will do soon

@pavelgyravel  what do you think about different approach, just an idea, currently when we are adding branch rules in the beginning of the brands hash
https://github.com/didww/credit_card_validations/blob/v6.0.0/lib/credit_card_validations/detector.rb#L87
detecting mechanism find first key value pair and return brand
def valid_number?(*keys)
      selected_brands = keys.blank? ? self.brands : resolve_keys(*keys)
      if selected_brands.any?
        selected_brands.each do |key, brand|
          return key if matches_brand?(brand)
        end
      end
      nil
    end

    ```

    what if we will try to insert new branch in the beginning so manually added rules will have better priority

    something like this

   instead of

brands[key] = {rules: [], options: options || {}}

we can try something

brand_config  = {key:  {rules: [], options: options || {}} } #define new hash for brand
brands = brand_config.merge(brands) #after this key : kortimilli will be in the beginning of the hash and

after it brands keys will have koritmilli on the first place

tested with ruby2.7

{code}
2.7.3 :001 > brands = {maestro: 'something', visa: 'something'}
=> {:maestro=>"something", :visa=>"something"}
2.7.3 :002 > new_brand = {kortimilli: 'something' }
=> {:kortimilli=>"something"}
2.7.3 :003 > brands = new_brand.merge(brands)
=> {:kortimilli=>"something", :maestro=>"something", :visa=>"something"}
2.7.3 :004 > brands.keys
=> [:kortimilli, :maestro, :visa]
{code}

@pavelgyravel what do you think about different approach, just an idea, currently when we are adding branch rules in the beginning of the brands hash
https://github.com/didww/credit_card_validations/blob/v6.0.0/lib/credit_card_validations/detector.rb#L87
detecting mechanism find first key value pair and return brand
def valid_number?(*keys)
      selected_brands = keys.blank? ? self.brands : resolve_keys(*keys)
      if selected_brands.any?
        selected_brands.each do |key, brand|
          return key if matches_brand?(brand)
        end
      end
      nil
    end

what if we will try to insert new branch in the beginning so manually added rules will have better priority something like this
instead of
   brands[key] = {rules: [], options: options || {}}

we can try something
  brand_config  = {key:  {rules: [], options: options || {}} } #define new hash for brand
  brands = brand_config.merge(brands) #after this key : kortimilli will be in the beginning of the hash and

after it brands keys will have koritmilli on the first place
tested with ruby2.7
 2.7.3 :001 > brands = {maestro: 'something', visa: 'something'}
 => {:maestro=>"something", :visa=>"something"}
2.7.3 :002 > new_brand = {kortimilli: 'something' }
 => {:kortimilli=>"something"}
2.7.3 :003 > brands = new_brand.merge(brands)
 => {:kortimilli=>"something", :maestro=>"something", :visa=>"something"}
2.7.3 :004 > brands.keys
 => [:kortimilli, :maestro, :visa]

@Fivell, thank you for your time!
Your proposal  should work in my case. But in general, i think, algorithm I purposed, is more accurate. Frequently local brands has same prefix, but wider as brands like maestro, but thay are not kobrands or part of that brand. So I think that brand recognition wil better work when its based on more accurate intersection of prefix
For example:
505 -> maestro
505827001 -> kortimilli
5058270017 -> could be some other local brand
and in this case brand should be recognized propertly with no depending of order of adding to Detector.brands.

@pavelgyravel , ok i've got your point , lets try it !

@pavelgyravel  https://rubygems.org/gems/credit_card_validations/versions/6.2.0


Errors during install

With installing the webpack I receive the following error:
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/webpack/node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
If I however try to install swip I got :
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed.
npm WARN<EMAIL_ADDRESS>requires a peer of webpack@1 || 2 || ^2.1.0-beta || ^2.2.0-rc but none was installed.
I Am trying to install on centos 6.7 (Final)
How to proceed ?

I solved it by installing the right socket.io version manual. Very nice I can see lots of fun applications with this.


Added Chetan-07 to CoP

Added Chetan-07 to CoP to resolve #539

@pabrahamsson updated to lowercase


[WIP] Extend Vesting Lockup periods

Closes: #XXX
Description

For contributor use:

[ ] Targeted PR against correct branch (see CONTRIBUTING.md)
[ ] Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
[ ] Code follows the module structure standards.
[ ] Wrote unit and integration tests
[ ] Updated relevant documentation (docs/) or specification (x/<module>/spec/)
[ ] Added  relevant godoc comments.
[ ] Added a relevant changelog entry to the Unreleased section in CHANGELOG.md
[ ] Re-reviewed Files changed in the Github PR explorer

For admin use:

[ ] Added appropriate labels to PR (ex. WIP, R4R, docs, etc)
[ ] Reviewers assigned
[ ] Squashed all commits, uses message "Merge pull request #XYZ: [title]" (coding standards)

Codecov Report
Attention: Patch coverage is 60.95618% with 98 lines in your changes are missing coverage. Please review.

Files
Patch %
Lines

x/liquidvesting/types/genesis.go
0.00%
43 Missing :warning:

x/liquidvesting/keeper/denom.go
0.00%
23 Missing :warning:

app/upgrades/v1.7.4/upgrades.go
5.88%
15 Missing and 1 partial :warning:

app/app.go
85.71%
6 Missing :warning:

x/liquidvesting/types/schedule.go
14.28%
6 Missing :warning:

x/liquidvesting/types/denom.go
0.00%
4 Missing :warning:

:loudspeaker: Thoughts on this report? Let us know!


1.3.0 reports incorrect version

Hey, not a big deal but binaries downloaded from tag v1.3.0 report they are 1.2.0  with --version:
$ tar xf plow_1.3.0_darwin_amd64.tar.gz
$ ./plow --version
1.2.0

This might confuse some Ansible playbooks which use the stdout version to determine if a new binary needs to be downloaded.

Thanks for your feedback, this is a known issue and has been fixed in the latest v1.3.1 .

Nice.  Do you think we could add it to the tag notes for v1.3.0 please?


Angular2 Firebase installation Error

This error is come when i m getting install the ( npm install angularfire2 --save ), Any One  have solution?

You have to update your @angular/cli version.

@saimzishan the errors you are getting are peer dependency errors. This means that some of the packages you are using expect certain other packages (and versions).
In this case, you are using<EMAIL_ADDRESS>and you are getting a few warnings about how it requires other package/version combos (like @angular/common@^4.0.0).
Just go through all of those and install them (npm install<EMAIL_ADDRESS>--save and so forth).
Installing some new peer dependencies may show more peer dependency warnings because the new package can have it's own requirements as well. As you go through all of them they'll start to go away.

@filipesilva thanks for comment, i have solve this problem my own, my npm is in old version, i replace with a new one version, and error is gone.
Thanks


Strange early-time evolution in metric perturbations

In trying to match the CLASS perturbations in #44, we saw before that there was a several percent disagreement pretty much all the time (i.e. even on superhorizon scales / early times). I have looked at this more carefully, and \Phi is clearly doing something strange at very early times (plot attached for k=0.03 h/Mpc) that we were not looking at in that draft PR thread.
The orange dashed line is Bolt and shows that at early times \Phi is evolving in the first 100 steps or so before leveling off until horizon entry. This definitely should not be happening - \Phi (and \Psi) should be constant (and \Phi' negligible) until horizon entry (e.g. MB Fig.2).

You can actually see that initially (very first step) we are in agreement with the initial \Phi value of CLASS, but after this evolution, our \Phi is too high and this affects subsequent evolution, resulting in the percent level differences we see (I am surprised it is not worse, to be honest).
I tried setting Neff to some very small value (1e-4) and this seems to make the problem go away (though late-time evolution won't match CLASS because Neff is wrong):

This is also true if I take out both massive neutrinos and massless neutrinos (by commenting out the lines in the background and einstein equations). The issue is not related to the massive neutrinos, as it persists when only massless neutrinos are included.
I likely made some mistake in the past when setting up the massless neutrinos. I will dig into this in the first few steps to see what about massless neutrinos is making \Phi' non-negligible. I have checked that we get the correct \Psi in the initial conditions, so I guess it is somehow an error in the 00 Einstein eqn (or something less obvious with the neutrinos).

After too many hours, I found that this was due to a problem in the initial conditions. The ICs as they stand are I believe(?) copied out of Callin06, and even though he includes the massless neutrino hierarchy, the ICs do not consistently account for massless neutrinos.
The reason for this is that when neutrinos are present it is not correct to use both \Theta_{0} = \scrN_{0} = \Phi/2 and \Phi=1 in the initial conditions (as the code was doing). If \Phi=1, this fixes \Psi through \Phi = -\Psi(1+2/5 f_{\nu}). But the initial value of the photon density perturbation and all the other (adiabatic) perturbations are determined through \Psi, not \Phi.
Ignoring this fact is fine when massless neutrinos are not included, and then the only relativistic species is photons. Since photons have negligible quadrupole at early times, turning Neff down appears to fix the problem by sending \Psi to 1 (= \Phi).
It looks like this mistake may have been made in Callin because the discussion around this in Dodelson (the reference he cites for ICs) is not very careful with respect to the neutrinos. The statement that \Theta_{0} = \scrN_{0} = \Phi/2 is implicitly assuming \Phi=\Psi - i.e. it assumes the non-existence of neutrinos.
If I instead use the MB ICs (eqn 98), which use \Psi to set the density ICs, as expected from the above discussion, we resolve this issue (no more evolution and \Phi' \approx 0):

I will add something describing this in the notes.

Also you can see that at late times \Phi is still not perfect, but this is almost certainly due to the RSA issues mentioned in #48. So since the large-scale issue is resolved I will close this.

Addressed in 38405c65eb70571392466c2d1df6068748375acf

FWIW I was wrong here - the late-time discrepancy is too early to be due to RSA - the switch for which happens around x~-3.5. The issue turned out to be a small discrepancy in the kvalue I used in my script to generate the plot - Phi looks like this (<0.4% diff from class) if you don't mess up the k mode values =]


Update the faker seeding script

This PR updates the faker seeding script for the test data, since the faker package is deprecating the function we are using (faker.name.findName()). I updated the script a bit so that we will get fake first names for the firstName field, and fake last name for the lastName field.
Fixes #621

On a side note, I noticed that the avatar image does not correspond to the handle. I realized that this is an expected behavior given that the seeding script is generating avatar independent of the handle:
avatar: `https://eu.ui-avatars.com/api/?rounded=true&background=574cfa&color=ffffff&name=${faker.internet.userName()}`,

Note that it may make sense to test this after we add the seeding script for Heroku (After #724)

Now that #724 is merged, I'm marking this ready for review ✌

Natuurlijk! 👍


Implement the name_tag method.

It's a really rough patch, because I'm just hacking something together, but this implements the name_tag method for Mixpanel.

Hey... thanks for this.  Before I merge it in... can you give me a quick explanation of what the name_tag MixPanel method does?
If it's truly a unique-to-MixPanel method, then this is exactly right.  But I want to double-check that it's not related to the track() or identify() method instead, because whenever possible the goal is to keep the APIs unified across the different analytics providers.
Thanks!

It sets the name attached to a user in their UI. Thinking about it passing a
:name option to identify would probably make more sense, but it would still
need to call name_tag in their JavaScript API.
On Oct 17, 2011 7:31 PM, "Joshua Krall" <
<EMAIL_ADDRESS>wrote:

Hey... thanks for this.  Before I merge it in... can you give me a quick
explanation of what the name_tag MixPanel method does?
If it's truly a unique-to-MixPanel method, then this is exactly right.  But
I want to double-check that it's not related to the track() or identify()
method instead, because whenever possible the goal is to keep the APIs
unified across the different analytics providers.
Thanks!
--
Reply to this email directly or view it on GitHub:
https://github.com/jkrall/analytical/pull/27#issuecomment-2432786

Ah yeah, that makes sense.
My gut says: have #identify accept an optional :name=>'name' attribute,
and then append the call to MixPanel's name_tag function after the
existing #identify functionality... does that make sense?
Maybe we should keep this additional #name_tag method but also add the
functionality to #identify so that users who don't want to add
MixPanel-specific stuff into their analytical calls still get the benefit of
name_tag?
If this makes sense... and you have time... go ahead and add this
functionality to this commit, and I'll gladly merge this in.
Thanks!
On Mon, Oct 17, 2011 at 1:34 PM, Jon Wood <
<EMAIL_ADDRESS>
It sets the name attached to a user in their UI. Thinking about it passing
a
:name option to identify would probably make more sense, but it would still
need to call name_tag in their JavaScript API.
On Oct 17, 2011 7:31 PM, "Joshua Krall" <
<EMAIL_ADDRESS>wrote:

Hey... thanks for this.  Before I merge it in... can you give me a quick
explanation of what the name_tag MixPanel method does?
If it's truly a unique-to-MixPanel method, then this is exactly right.
But
I want to double-check that it's not related to the track() or identify()
method instead, because whenever possible the goal is to keep the APIs
unified across the different analytics providers.
Thanks!
--
Reply to this email directly or view it on GitHub:
https://github.com/jkrall/analytical/pull/27#issuecomment-2432786

--
Reply to this email directly or view it on GitHub:
https://github.com/jkrall/analytical/pull/27#issuecomment-2432830

Closing this one, because it was handled here:  https://github.com/jkrall/analytical/pull/31


[Snyk] Security upgrade electron from 25.4.0 to 25.8.0

Details

Changes to the following files to upgrade the vulnerable dependencies to a fixed version:

package.json
package-lock.json

Vulnerabilities that will be fixed
With an upgrade:

Severity
Priority Score (*)
Issue
Breaking Change
Exploit Maturity

716/1000  Why? Recently disclosed, Has a fix available, CVSS 8.6
Out-of-Bounds SNYK-JS-ELECTRON-5880432
No
No Known Exploit

(*) Note that the real score may have changed since the PR was raised.
Check the changes in this PR to ensure they won't cause issues with your project.

Fixed Issues

$
PROPOSAL:
Tests

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

Offline tests

QA Steps

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

PR Author Checklist

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

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

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

[x] Android / native
[x] Android / Chrome
[x] iOS / native
[x] iOS / 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 a new component is created I verified that:

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

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

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

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

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(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.
[x] I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

Screenshots/Videos

Web

Mobile Web - Chrome

Mobile Web - Safari

Desktop

iOS

Android

Linked issue: #27097
C+: Please follow these steps to test the linked PR before running through the reviewer checklist:

[x] The first step is to understand the PR: what dependency is it upgrading, for which vulnerability, how it impacts our product & end users.
[x] If the issue is not worth fixing, please add your reasoning in the issue and have the internal engineer review it.
[x] Check the change log (which should be included in the PR description) to see all changes. We want to identify any breaking changes. If it is a minor version bump, it's unlikely that there are any breaking changes.
[x] Test our feature(s) that make use of this package. If it does not work, we should understand what broke it. It is also a good idea to check our main flows to make sure they are not broken that you can add in the checklist screenshots/videos.

Changelog (25.4.0 -> 25.8.0)

No breaking changes

Reviewer Checklist

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

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

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

[x] Android / native
[x] Android / Chrome
[x] iOS / native
[x] iOS / Safari
[x] MacOS / Chrome / Safari
[x] MacOS / Desktop

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

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is 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 verified that this PR follows the guidelines as stated in the Review Guidelines
[x] I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] If a new component is created I verified that:

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

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

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

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

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(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.
[x] I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Web

Mobile Web - Chrome

Mobile Web - Safari

Desktop
Desktop app works fine as normal
https://github.com/Expensify/App/assets/108292595/f622e108-49aa-4b7f-925f-c11155d61960

iOS

Android

@youssef-lr conflict came from https://github.com/Expensify/App/pull/26967. We can just ignore those changes and force replace with our PR. Can you please fix conflict? (I don't have push access to this branch)

: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/youssef-lr in version: 1.3.68-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/Julesssss in version: 1.3.68-17 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
failure ❌

🕸 web 🕸
success ✅


Bjorncs/tito tag format

It would be nice to avoid having the .tito folder checked into the repository, but this should work.

@aressem PTAL

Looks better now. I will merge this.


fix(debug): fix detection of JS tags in debug template

:tada: This PR is included in version 2.2.2 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Clarify responses to event publishers

The spec includes an event response message, but we need to clarify the use of this. We need to be clear on what is returned in the response to the synchronous call into the EMS to post and event (OperationOutcome) vs what responses an event subscriber might expect to produce (errors, etc) to send back to us if they can't process the event.

See comment added to Issue 1

@ahatherly I have updated the spec to make it clear for a POST to the publish API an OperationOutcome will be returned containing one of the error codes from the Spine standard error codes (You can see the changes on the netlify published version of the develop branch https://ems-develop.netlify.com/publication_publish.html#response). Do we want to try and call out the most likely causes of error responses to publishers or leave it high level as publishers should not send us invalid events.
For the subscribers recieving events I have updated the specification Event Receiver Requirements Overview page to make the existing requirements more clear that "There are currently no requirements defined for the Events Management Service to receive or act upon failures in consuming systems" (You can see the changes on the netlify published version of the develop branch, https://ems-develop.netlify.com/receiver_requirements.html#itk3-acknowledgements-and-errors). We have added a requirement that they still develope against the ITK3 Message Distribution specification just incase we want to ask for a response in the future. Do you think we should pull out some more of the key aspects of this spec and put them in the EMS spec as well as linking to the ITK3 spec.

Test

I am closing this for now as there is more information in the spec around error responses. If we think any more detail is required in the future we can raise more specific issues when we identify useful guidance or gaps in guidance/requirements.


Make view snapshot_summary

To help us with https://github.com/bcgov/range-web/issues/683 and at the very least testing/troubleshooting https://github.com/bcgov/range-web/issues/700 .  See https://github.com/bcgov/range-web/issues/700#issuecomment-611208676

Resizing to reflect reality.  This is a database view and is what now powers the version endpoint.  Until the web side of it is done its hard to test but i can do a query in the database to show what versions and their legal status is for a given plan in test.


Functional-oriented argparse groups

The idea is to have functional-oriented argparse groups.
How would this feature be useful?
It will increase the readability of the help message.
Describe the solution you'd like
Instead of having primary/additinal argparse groups we can split the arguments into more functional-oriented groups e.g.:

general: --help, --version, --verbose, --noxfile, posargs
reporting: --nocolor, --forcecolor, --report
collection: --list, --session, --keywords
environment: --envdir, --reuse-existing-virtualenvs, etc.
execution: --stop-on-first-error, --install-only, --non-interactive, etc.

I based above on pytest --help

I'm all for this and it would be a good first issue for someone to tackle

Hello, I'd like to work on this issue if it's OK. Thx.


The function "loadGenerator" you want to update is not yet deployed

I tried following the quick start instructions by doing the following:
npm i -g serverless serverless-artillery
slsart deploy

The error I get back is:
	Deploying Lambda to AWS...

{ ServerlessError: The function "loadGenerator" you want to update is not yet deployed. Please run "serverless deploy" to deploy your service. After that you can redeploy your services functions with the "serverless deploy function" command.
    at provider.request.then.catch (/usr/local/lib/node_modules/serverless/lib/plugins/aws/deployFunction/index.js:65:13)
    at tryCatcher (/usr/local/lib/node_modules/serverless/node_modules/bluebird/js/release/util.js:16:23)
    at Promise._settlePromiseFromHandler (/usr/local/lib/node_modules/serverless/node_modules/bluebird/js/release/promise.js:512:31)
    at Promise._settlePromise (/usr/local/lib/node_modules/serverless/node_modules/bluebird/js/release/promise.js:569:18)
    at Promise._settlePromise0 (/usr/local/lib/node_modules/serverless/node_modules/bluebird/js/release/promise.js:614:10)
    at Promise._settlePromises (/usr/local/lib/node_modules/serverless/node_modules/bluebird/js/release/promise.js:689:18)
    at Async._drainQueue (/usr/local/lib/node_modules/serverless/node_modules/bluebird/js/release/async.js:133:16)
    at Async._drainQueues (/usr/local/lib/node_modules/serverless/node_modules/bluebird/js/release/async.js:143:10)
    at Immediate.Async.drainQueues (/usr/local/lib/node_modules/serverless/node_modules/bluebird/js/release/async.js:17:14)
    at runCallback (timers.js:637:20)
    at tryOnImmediate (timers.js:610:5)
    at processImmediate [as _immediateCallback] (timers.js:582:5) name: 'ServerlessError', statusCode: undefined }

	Deploy complete.

I can't find any other config I'm supposed to be doing in the documentation.

This is unexpected, thank you for reporting it.  Perhaps downgrading Serverless would help but we will investigate.

You can downgrade Serverless in the local directory rather than globally if you like.

Hi @countergram.  Thank you very much for reporting this!  Busy week last week.  We have been able to reproduce this locally and will be resolving the matter as quickly as we are able.

Unfortunately, @countergram, this appears to have been introduced in 1.21.1 (via https://github.com/serverless/serverless/pull/4192).  Very sorry you were impacted!
If you downgrade to npm i -g<EMAIL_ADDRESS>I have validated that you will be able to use the serverless-artillery tool successfully.  I am tracking this issue down in https://github.com/serverless/serverless/issues/4246 and will report back here once we have a resolution.

The root cause of this is that we added a previously ignored flag here:
https://github.com/Nordstrom/serverless-artillery/commit/83c7d1c5f1151fba3f28c8be460224896effa9be#diff-cd8767be2a8141c69090791119dc9c6bL32
...but Serverless has released a convenience feature to upgrade an sls deploy -f <name> to a sls deploy function -f <name> which has a different meaning.
The resolution is to stop adding the previously ignored flag in our invocation of serverless.  We will open a PR to fix this shortly.
Thanks again for your report and apologies for the negative experience.

@countergram Version 0.2.2 has been published to NPM. This should contain the fix you need. Please give this a try and let us know if it doesn't address the problem.
Thanks again for bringing this bug to our attention!

Looks good. I'll give it another try from work tomorrow. Thanks for the quick response.

Thanks @countergram!  Please let us know if you run into any other issues or if there are any features the tool is missing.  On that note, acceptance mode should be dropping soon.


readme(dm): update dm test readme

What problem does this PR solve?
Suggest IT use MySQL 8.0.21.
What is changed and how it works?
Check List
Tests

No code

Release note
`None`.

Codecov Report

Merging #3933 (69bd8ce) into master (eed6f9b) will decrease coverage by 0.4885%.
The diff coverage is 58.2125%.

Flag
Coverage Δ

cdc
57.8139% <72.0095%> (-0.6233%)
:arrow_down:

dm
56.0088% <44.1463%> (-0.3664%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.
 Higher MySQL support FLUSH_TABLE privilege to flush table with read lock. So SOME test will failed! e.g. full_mode - -

/merge

/run-leak-test


Farmerbot v020 issue with Json, nodes not powering on

A Farmer on Telegram reported that the new release doesn't power on nodes.
I also experience the same problem. For testing, I did restart the farmerbot with the previous release, and it does work.
Here is one of the log file section:
2023-07-11 02:45:09 [INFO ] [POWERMANAGER] Executing job: POWERON 880
2023-07-11 02:45:09 [DEBUG] Received error response for job with guid 9ec5dc64-1c8e-4612-9f41-1454c55d000c
2023-07-11 02:45:09 [DEBUG] Returned job 9ec5dc64-1c8e-4612-9f41-1454c55d000c
2023-07-11 02:45:09 [ERROR] [POWERMANAGER] Job to power on node 880 failed: Error while calling set_node_power: Cannot read properties of undefined (reading 'toJSON')
2023-07-11 02:45:09 [INFO ] [POWERMANAGER] Periodic wakeup for node 879
2023-07-11 02:45:09 [DEBUG] Received job with guid f7109df0-97e2-4da6-910f-3e2d80137c92
2023-07-11 02:45:09 [DEBUG] Assigned job f7109df0-97e2-4da6-910f-3e2d80137c92 to jobs.actors.farmerbot.powermanager:
2023-07-11 02:45:09 [DEBUG] jobs.ActionJob{
    guid: 'f7109df0-97e2-4da6-910f-3e2d80137c92'
    twinid: 0
    action: 'farmerbot.powermanager.poweron'
    args: params.Params{
        params: [params.Param{
            key: 'nodeid'
            value: '879'
        }]
        args: []
    }
    result: params.Params{
        params: []
        args: []
    }
    state: tostart
    start: 2023-07-11 02:45:09
    end: 1970-01-01 00:00:00
    grace_period: 0
    error: ''
    timeout: 0
    src_twinid: 0
    src_action: ''
    dependencies: []
}

Two things stand out:

end: 1970-01-01 00:00:00
twinid: 0

@brandonpille
Might be just about changing line 28 here to this:

image: ghcr.io/threefoldtech/grid_http_server:2.1.0-rc2

(rc2 instead of rc1).
I'll make a PR on this.

That is probably where the issue comes from. Let's see the result.


Back button on android does not close

If i press the back button on Android (instead the cancel button), it does not close the screen. Instead, it goes back to the previous page, and the cancel button won't work either (and the screen will be freezed on the current screen).
I have been trying to fix this using the ionicPlatform functions (onHardwareBackButton, offHardwareBackButton, registerBackButtonAction), but i cannot achieve a function that is only valid when the modal is opened and destroyed when is closed.
Any idea?

this line of code does not work for you? https://github.com/israelidanny/ion-google-place/blob/master/ion-google-place.js#L114


jdk-11.0.4+11.4 installled, but build 11.0.4+11 reported? [mac installer]

Steps to reproduce:

install jdk-11.0.4+11.4 for Mac
check version, the build date is supposed to be 24 August 2019

~$ java -version
openjdk version "11.0.4" 2019-07-16
OpenJDK Runtime Environment AdoptOpenJDK (build 11.0.4+11)
OpenJDK 64-Bit Server VM AdoptOpenJDK (build 11.0.4+11, mixed mode)

@uqix we've tried that before but unfortunately it's not supported upstream. Closing as this wouldn't be possible without a considerable amount of work upstream


Fatal error :(

latest.log

Could not find required mod: gunpowder-signshop requires {gunpowder-currency @ [*]}

install Gunpowder Currency


[NG] Enable tab content to scale to tabs container (#3279)

The introduction of block-level section element had introduced the
need to explicitly manage the container height. Reverting it to
inline will allow direct visibility between the tab content and tabs
parent container.
Signed-off-by: Ivan Donchev<EMAIL_ADDRESS>

Hi Ivan, as the tabs component is a layout component, shouldn't we rather have block, flex, grid as a display property instead of inline? Secondly, it seems like our tabs component works just fine if user sets the height on the tab content.

Hi @Shijir,
1.0.x is fine, the problem is with 1.1.x - https://stackblitz.com/edit/clarity-tabs-with-heigth-1-1-x?file=package.json
About if it would be better to have the tabs as block level - it probably would, but it will be a breaking change, as it will require users to update their current code. This specific change is more aimed at restoring the previous way this component worked.
If you need more information I can point you to the slack discussion we had on this topic, where both these options were compared and discussed.

As per our discussion, I've given it :shipit: . Please make sure it works across different browsers. Thank you :)


Database migrations?

A very general question - does cubdb offer any support for performing data migrations?
If not, can you give any advice on how to implement data migrations?
Thanks

You can create a custom Migrator module to handle any migrations you need. Start a transaction, fetch the data to be updated, and perform the updates.
Alternatively, you can adopt a lazy migration approach, updating data only when it is accessed.
Lastly, consider storing the schema version as a field and processing the data based on its specific schema.


Added new version of Korean translations for document, and some Miscellaneous changes!

New Korean translation is now here!
I’ve translated tweepy’s documents to Korean, to more people can use tweepy easily.
Previous translation was outdated, but I can’t modify or update it because I had to serve in the military in Korea(not North, but near(DMZ/GOP)). But now I’m discharged due to expiration of mandatory service period, so I’ve made new Korean translation document for tweepy.
1. Commit summary
A. Added: new version of Korean translation for reference document.
B. Added: krHTML_autoBuild.bat for debugging .po files at local devices (QoL).
C. Removed: unused document .po files and TRANSLATORS_ko_KR.txt.
2. What’s changed
A. Added new version of Korean translation
Translated next documents:

api.po, asyncstream.po, auth_tutorial.po, authentication.po, changelog.po, client.po, development.po, examples.po, exceptions.po, extended_tweets.po, faq.po, getting_started.po, index.po, install.po, models.po, pagination.po, parameters.po, stream.po, streaming.po

Much of the translation has been modified to suit with the latest version. The terms and explanations used in documents were also unified as much as possible. There might be an loose translation for convinence at understanding, but It doesn’t interfere the original sentence’s intend.
B. Added krHTML_autoBuild.bat for debugging .po files at local devices (QoL).
Previously, we need to build Korean version of HTML with 2 commands to debug documents, but It’s kind a tiresome work. So I’ve added .bat file. This will be changed to improved batch files at future.
C. Removed unused document .po files and TRANSLATORS_ko_KR.txt.
I’ve removed unused document files (ex. streaming_how_to.po), and TRANSLATORS_ko_KR.txt(This file is also outdated, and overlaps with tweepy/tweepy → Insights → Contributors).
3. Known Issue
A. Completed translation of examples.po, but it doesn't appear at final results.
Because it's not an important part (it's the title of the tab), this part will be revised later.
B.  Some Duplicate label errors. Error logs below.
C:\Users\pinkr\GitHub Repository\tweepy\docs\..\tweepy\asynchronous\streaming.py:docstring of tweepy.asynchronous.streaming.AsyncStream.filter:: WARNING: more than one target found for cross-reference 'List': tweepy.models.List, tweepy.List
C:\Users\pinkr\GitHub Repository\tweepy\docs\..\tweepy\asynchronous\streaming.py:docstring of tweepy.asynchronous.streaming.AsyncStream.filter:: WARNING: more than one target found for cross-reference 'List': tweepy.models.List, tweepy.List
C:\Users\pinkr\GitHub Repository\tweepy\docs\..\tweepy\asynchronous\streaming.py:docstring of tweepy.asynchronous.streaming.AsyncStream.filter:: WARNING: more than one target found for cross-reference 'List': tweepy.models.List, tweepy.List
C:\Users\pinkr\GitHub Repository\tweepy\docs\..\tweepy\asynchronous\streaming.py:docstring of tweepy.asynchronous.streaming.AsyncStream.filter:: WARNING: more than one target found for cross-reference 'List': tweepy.models.List, tweepy.List
C:\Users\pinkr\GitHub Repository\tweepy\docs\..\tweepy\asynchronous\streaming.py:docstring of tweepy.asynchronous.streaming.AsyncStream.sample:: WARNING: more than one target found for cross-reference 'List': tweepy.models.List, tweepy.List
C:\Users\pinkr\GitHub Repository\tweepy\docs\..\tweepy\errors.py:docstring of tweepy.errors.HTTPException:15: WARNING: more than one target found for cross-reference 'List': tweepy.models.List, tweepy.List
C:\Users\pinkr\GitHub Repository\tweepy\docs\..\tweepy\errors.py:docstring of tweepy.errors.HTTPException:21: WARNING: more than one target found for cross-reference 'List': tweepy.models.List, tweepy.List
C:\Users\pinkr\GitHub Repository\tweepy\docs\..\tweepy\errors.py:docstring of tweepy.errors.HTTPException:27: WARNING: more than one target found for cross-reference 'List': tweepy.models.List, tweepy.List

4. Miscellaneous
A. Recommended label: ‘Documentation’
B. Translated by

악동분홍토끼(@pinkrabbit412)
https://github.com/pinkrabbit412

Thanks for PR reviewing!
I've made some changes, so I re-requesting PR review.
Additional changes

Removed unnecessary batch file (krHTML_autoBuild.bat)
1st and 4th line of .po files modified appropriately
Reverted Polish translation file to previous version


[WIP][BEAM-9228] Support further partition for FnApi ListBuffer

Please add a meaningful description for your change here

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
Post-Commit Tests Status (on master branch)

Lang
SDK
Apex
Dataflow
Flink
Gearpump
Samza
Spark

Go

---
---

---
---

Java

Python

---

---
---

XLang
---
---
---

---
---
---

Pre-Commit Tests Status (on master branch)

---
Java
Python
Go
Website

Non-portable

Portable
---

---
---

See .test-infra/jenkins/README for trigger phrase, status and link of all Jenkins jobs.

retest this please

retest this please

R: @robertwb
Current PR passes all tests, except SDF ones. Can you please take a look to see I am on the correct track before I spend more time on investigation? Thank you.

errors: https://builds.apache.org/job/beam_PreCommit_Python_Commit/11130/testReport/

retest it please

@robertwb, please take a look.

kindly ping. @robertwb


PyPI

This tool doesnt appear to be on PyPI yet.

No, it's not. Development has stopped right now, so this is not on my agenda at the moment.


http-options doens't work

I'm trying to set a authorization property to my request header but nothing works... I've tried:
    <vuetable ref="vuetable"
              :api-url="apiEndPoint('form-template')"
              :http-options="$http.defaults.headers"
              :fields="fields"
    >

    <vuetable ref="vuetable"
              :api-url="apiEndPoint('form-template')"
              :http-options="$http.defaults.headers.common"
              :fields="fields"
    >

    <vuetable ref="vuetable"
              :api-url="apiEndPoint('form-template')"
              :http-options="{ get: $http.defaults.headers.common }"
              :fields="fields"
    >

Any clue why?

try doing :http-options="{ header: <header-options (JSON)> }
vuetables is using axios. the http-options is passes as the config to the request, so the object for http-options should follow the axios config.
https://github.com/mzabriskie/axios
note that the params overwritten before the request is made, so dont include parameters in the httpOptions propery, instead, put parameters in the :appendParams property

@lgullestrup Can you help share your opinion on this comment?

This worked like a charm! Thank you @lgullestrup!

How can i achieve this ?

@onlineexamsystem Shouldn't you have a : in front of http-options?


Can vunit overcome the problems that surround treating a page segment as a viewport?

There is an issue that I have been trying to overcome which is that VW/VH units become completely useless as soon as you are working with any kind of split screen/pane. I've been looking for a solution where one segment of this split can be treated as it's own viewport, but the only real solution is using iframes. See a question about this on Stack Overflow.
jsFiddle use the iFrames approach, which is how they able to have their screen area split 4 ways, but still be able to correctly display elements sized with vw and vh in the bottom right hand preview window see here.
Although the jsFiddle approach is precisely the behavior I want, splitting my application up into separate pages, so that they can be windowed separately within iFrames, just so I can use viewport measurements in each, seems rather extreme.. and so my question is...
Does vunit offer the flexibility to calculate it's units from a specific DIV container, or does it only calculate from the entire viewport?
Thanks

No, the vUnit does not offer that feature, unfortunately. It's quite out of the scope of the lib.
But it looks like something you'd be able to achieve with a combination of percentages, calc and position absolute.
On a side note, this could be also useful for you: http://kumailht.com/responsive-elements/
Good luck!

Hi @joaocunha, Thanks for your quick response.
With a little play around in jsfiddle, I have successful managed to tweak the behaviour of your library so that it does exactly what I need (I might folk this because, with the additional functionality, it is incredibly powerful).
All I have changed is your calculateViewportSize function, so it gets the height and width from my DIV instead of the window.
And now all of your great resizing functionality works, but relative to the specified DIV.
Please check out my crude, but affective, jsfiddle.
At first glance, if you resize the preview window, you'll get the exact same functionality as your library would give alone, but now, for test purposes, I have added jQuery Resizeable to the main DIV. So, grab the bottom right corner of the DIV and resize it.
This is exactly the functionality I need. The means to size elements in a VW / VH type of way, even when working within DIVs/windows, within the main viewport!
Many thanks to you!

I quite like that approach. I'd be willing to take a PR if we can make it simple to define on the options.

Hi @joaocunha, I've updated my fiddle. Check it out and you'll see that I've modified your libraries code to achieve the following edition functionality.

Pass in containerID in the options.
New condition added in viewportHasChanged function to determine if a container ID has been passed in and is an existing HTML element.
If container has been passed in and it is a valid HTML element, use new function called calculateContainerSize.
Otherwise, fallback to using calculateViewportSize.

For my current usage, this is now in a useable state. I have the choice between selecting one specific container, or letting it run as vunit currently does by simply omitting a containerID.
However, in the future, it could be taken to the next logical step of allowing to except multiple IDs like..
containerIDs: ['main',sidebar]
..but then we would need to do something like scope the generated CSS. Something like..
#main.vw_width1{width:6px} #main.vw_width2{width:12px} #main.vw_width3{width:18px} #main.vw_width4{width:24px} #main.vw_width5{width:30px}
and
#sidebar.vw_width1{width:6px} #sidebar.vw_width2{width:12px} #sidebar.vw_width3{width:18px} #sidebar.vw_width4{width:24px} #sidebar.vw_width5{width:30px}
..but it would then mean you could use it independently in as mean DIVs as you like.

Right. I'll digest it for a while to see if it's a fit.
Thanks for that!

I tested the solution from johnsq to size an iFrame and it worked great for me, IE11 Windows 10.


Search bar for events

to create a search bar for searching different events

Please assign this issue to me and add gssoc'21 label to it. i would love to work on this @javedhamdan107

an unwanetd feature. But still thanks for your contributions. Please look into other active issues:)


ldap: Fix error while updating an user registered in multiple realms.

Fixes: #11520.

Closing as the original issue was fixed in https://github.com/zulip/zulip/commit/67b6179df28522274ebdc66e6820a6e7e41511fa.


Remove RES from departments.json

What are the relevant tickets?
Part of https://github.com/mitodl/hq/issues/4855
Description (What does it do?)
This PR removes RES from departments.json
How can this be tested?

Additional Context

This PR will be on hold until data migration is done for existing courses to remove RES department first.

This PR is still on hold until the relevant changes are made in open and the courses are updated there after the changes.


Update navbar styles

Problem
Our current navbar doesn't match the one Tabler's provide:

Solution
Mockups: Figma
Let's update our navbar styles to match the one in Tabler:

Desktop:

[x] Keep 24px side paddings (to match paddings in page layout)
[x] Keep our 1.5 line-height for text
[ ] Change badge placement according to the mockup (centered, 4px spacing between text and badge)
[ ] Search input: add search icon (1.25 stroke-width); add "S" <kbd> text at the end; change placeholder text to "Search..."
[ ] Set spacing between search input and avatar to 16px

Mobile:

[x] Keep 24px side paddings (to match paddings in page layout)
[ ] Set 16px spacing between elements
[ ] Search input: add search icon (1.25 stroke-width); change placeholder text to "Search..."
[ ] When opened: highlight currently opened page with --tblr-primary color (#066FD1)
[ ] Do not trigger sub-menu when avatar is clicked, instead display "Settings" and "Sign out" options in main menu below separator line

seems "Keep 24px side paddings" already was fixed

@amgalanbadmaev "Change badge placement" means badge for tasks tab?

do we want to fix this jumping?
https://github.com/user-attachments/assets/3bcc24c2-438f-4bae-96df-92daaa039f91

we did not highlight opened nav in desktop
our

mockup

do we want to fix this in this issue?
"Settings" and "Sign out" looks strange

"Keep 24px side paddings" already fixed
" Keep our 1.5 line-height for text" already fixed

this was added since Tabler's navbar have different paddings and line-height set

@amgalanbadmaev "Change badge placement" means badge for tasks nav?

yes, should be as on mockup

before adapt the search field we have to do this issue because rn chevron down displays for all select fields

Should we close this issue and create separate to set styles for Navbar after the mentioned issue for select @delavaler ?

do we want to fix this in this issue? "Settings" and "Sign out" looks strange

Yes, please fix. Note that currently opened page should also be highlighted via tblr-primary color for nav-link text on Mobile.

Also separator line on mobile navbar menu currently is not visible due to white color. Should be changed to #DCE1E7 (or the one tabler uses in their own).

Yes, please fix. Note that currently opened page should also be highlighted via tblr-primary color for nav-link text on Mobile.

should we colorize "Settings" on desktop?
do not look at ugly dropdown, will fix it

No, only on mobile please

before adapt the search field we have to do this issue because rn chevron down displays for all select fields

Should we close this issue once all other things are done and create separate to set styles for Navbar after the mentioned issue for select @delavaler ?

sounds reasonable

not quite understand, close the whole issue or just part with the search field. I almost made other fixes.

is this behaviour ok for us? (doubled options when open 2 dropdowns)
https://github.com/user-attachments/assets/f9d66244-81cf-4d17-bee3-7cbde2ce1d87

not quite understand, close the whole issue or just part with the search field. I almost made other fixes.

ignore Search input (icon and kbd text) points in issue, will be moved to separate one

is this behaviour ok for us? (doubled options when open 2 dropdowns)
simplescreenrecorder-2024-11-08_09.27.59.mp4

can we make so that on mobile Avatar doesn't open dropdown menu at all?

but i think we should make nav after clicking on avatar on mobile
"Do not trigger sub-menu when avatar is clicked, instead display "Settings" and "Sign out" options in main menu below separator line" - please clarify what do we need here

But keep in mind that on Desktop it should open (since we don't display these links in navbar)

On 320px viewport avatar wraps to the 2nd row, Tabler's navbar doesn't have this issue:

i think tabler has the same problem too

seems in our case the select field wants more space, we may try to fix this

Let's do it


Persist login status on refresh

Love this module, so easy to integrate and work with, just wondering one thing:
From what I can tell this should persist the user being logged in between refreshes or am I being slow? It's logging out user between refreshes, localStorage values still present...

same here :)

Seems like something isn't working on the auth0 side, the module returns an error. Need to do some more investigation

Seems like we're not the only ones dealing with this issue:

On community chat here - a huge thread about persisting login
On a walkthrough here, if you search the page for Keeping Users Signed In after a Refresh it'll take you to the bottom of the page you find a section detailing having to register the app with whichever provider (in the example and my case, google) you're using.

Going to try this out and will report back

Tadaaaa it works 💃
Will open a PR to update README to give some brief details around the steps required!

Thanks so much for your help and research @omonk


Error: Format of generated html files

Acknowledge the following

[x] I carefully read and followed the Getting Started guide.
[x] I read through FAQ and searched through the past issues, none of which addressed my issue.
[x] The issue I am raising is a potential bug in al-folio and not just a usage question.  [For usage questions, please post in the Discussions instead of raising an issue.]

Describe the bug
I tried to upgrade my homepage to the latest commit of al-folio. Everything worked fine. However, I realized that all generated HTML files were in the wrong format. The content of these files is in-line and cannot be read without re-format.

The source:
https://github.com/DoHaiSon/dohaison.github.io/tree/source
The output HTML misformatted:
https://github.com/DoHaiSon/dohaison.github.io/blob/gh-pages/index.html

System (please complete the following information):

OS: Ubuntu 20.04 WSL2

What you mean by cannot be read without re-format? By a human?
If so, this is not a problem, since this html file is supposed to be served on gh-pages (as can be seen in the misformatted url). The main focus of this html is NOT to be human readable. Even so, a file with less spaces and line breaks have less characters, and consequently less file size. It might not be too much of a difference here, but that is the whole point of existing minified versions of commonly used libraries.

Oh, I see. So, if you confirm that this format is what we did on purpose, I agree with you.
I'm sorry, I missed this update changelog of al-folio.

I can't assure you that this change in spacing is made on purpose, either by our side (if it is, idk where) or by the jekyll build process (I looked for it, but couldn't find anything). I just said that it doesn't matter, since this html is not supposed to be read by humans.


Can't read from stdin in debug console

Environment data
dotnet --info output:
.NET Command Line Tools (1.0.1)
Product Information:
Version:            1.0.1
Commit SHA-1 hash:  005db40cd1
Runtime Environment:
OS Name:     ubuntu
OS Version:  16.04
OS Platform: Linux
RID:         ubuntu.16.04-x64
VS Code version: 1.10.2
C# Extension version: 1.8.0
Steps to reproduce
Read from stdin (Console.ReadLine()) in DEBUG CONSOLE.
Expected  behavior
Program reads from debug console input and pauses on breakpoints.
Actual behavior
I cant do interactive debugging in this console. Input doesn't cause any effect. When program reaches point with reading from stdin, it just waits. Maybe, I didn't configured VS Code in a proper way?

@mitutee the debug console is not intended to be used with applications that need to read from stdin. For such programs, set console to be `integratedTerminal' or 'externalTerminal'. GitHub's printing of markdown seems to not be working at the second, but for full documentation see https://github.com/OmniSharp/omnisharp-vscode/blob/release/debugger.md.


purge old external cirrus.lib package

With the archival of cirrus-lib it seems reasonable time for the external cirrus-lib package to go now, agreed?

@jkeifer -- I don't know if this change is too soon or not, but after bonking the "re-run jobs" button twice (only one job seems to be able to upload coverage at a time), the tests passed w/ the change in coverage likely due to winning at code-golf.

@jkeifer thoughts about merging this?

I'm good with this, the only thing I'd call out is adding a clear "Breaking Changes" section to the CHANGELOG.md (as has been done in the past for breaking changes) with the instruction that any users relying on the automatic packaging of cirrus.lib into lambdas will need to explicitly add cirrus.lib to those function requirements (and that cirrus.lib is no longer maintained and that we recommend migrating to stac-task).

I'm good with this, the only thing I'd call out is adding a clear "Breaking Changes" section to the CHANGELOG.md (as has been done in the past for breaking changes) with the instruction that any users relying on the automatic packaging of cirrus.lib into lambdas will need to explicitly add cirrus.lib to those function requirements (and that cirrus.lib is no longer maintained and that we recommend migrating to stac-task).

I'll make that change


Make Ollama serve requests in parallel

It seems that requests are served sequentially. It would help if they can be served in parallel.

streaming support.

Closing as a dupe of #358


Can't run a local repo with "helm serve"

Output of helm version:
Client: &version.Version{SemVer:"v2.8.2", GitCommit:"a80231648a1473929271764b920a8e346f6de844", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.8.1", GitCommit:"6af75a8fd72e2aa18a2b278cfe5c7a1c5feca7f2", GitTreeState:"clean"}

Output of kubectl version:
Client Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.3", GitCommit:"2bba0127d85d5a46ab4b778548be28623b32d0b0", GitTreeState:"clean", BuildDate:"2018-05-21T09:17:39Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.0", GitCommit:"fc32d2f3698e36b93322a3465f63a14e9f0eaead", GitTreeState:"clean", BuildDate:"2018-03-26T16:44:10Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}

Cloud Provider/Platform (AKS, GKE, Minikube etc.):
none
I run the following from one Ubuntu Linux shell:
helm repo index ./local-charts
helm --debug serve --repo-path ./local-charts

Note the local-charts folder has this:
index.html
my-chart-0.1.0.tgz

I run this from another shell (same machine):
helm search local/my-chart
No results found

What am I doing wrong?

did you run helm repo update? Without running helm repo update, the local indices in ~/.helm have not been updated which is what helm search requires to search.

Don't you need to add the repo?
$ helm repo add test http://<IP_ADDRESS>:8879/
"test" has been added to your repositories
$ helm search meraki-helm
NAME                    CHART VERSION   APP VERSION     DESCRIPTION
test/meraki-helm        0.1.4           1.0             A Helm chart for Meraki App

local is added by default on helm init, so there's no need to add an extra.
><> helm repo list
NAME            URL
stable          https://kubernetes-charts.storage.googleapis.com
local           http://<IP_ADDRESS>:8879/charts

I think the OP might be refering to local/chart in a broader sense, meaning from his local repo (not the local cache). If that's what he mean, then I think he needs to add it and give it a name.

Repo update always prints out that it skips the local one =:|
I looked into Christian's idea of defining a repo pointing to <IP_ADDRESS>...
Although this seems to work, there is still something fishy going on
because if I do "helm repo list", I can see a "local" one which points
to <IP_ADDRESS>, but there doesnt seem to be a way of accessing it via serve
except by manually defining a repo pointing to same address. Talk about
confusing!
Also seems that "helm search local/chart" behaves differently from "helm
search local-folder/chart" and that you can change behavior by having a
called local. This makes interpretation of the piece ahead of "/"
rule-dependant, the rules being hidden inside the software. There should be
a way of telling helm whether the prefix is a served repo or a local folder
acting as a repo.
On Tue, Jun 19, 2018, 14:14 Matthew Fisher<EMAIL_ADDRESS>wrote:

did you run helm repo update? Without running helm repo update, the local
indices in ~/.helm have not been updated which is what helm search
requires to search.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes/helm/issues/4242#issuecomment-398494802,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACenmKAFKkVrI7KcqQRIIEZft84tVYjaks5t-T-TgaJpZM4Ut8y_
.

--
Oliver Schoenborn
|| Cloud Application Engineer, Owner || Sentian Software Engineering ||
Ottawa, ON, Canada
|| +1-613-552-4466 (mobile) || @schollii2 (Twitter) || schoenborno (Skype)
|| LinkedIn https://linkedin.com/in/oliver-schoenborn || StackOverFlow
https://stackoverflow.com/users/869951/oliver || CodeProject
https://www.codeproject.com/Articles/schollii#Tip || GitHub
https://github.com/schollii

Facing the same issue, but adding the repo made it work. Seems a little surprising.

helm serve has been removed in Helm 3. Closing as inactive/fixed through removal.


get err next time when interval across month

func main() {

	c := cron.New()
	c.AddFunc("0 54 10 21/30 3 ?", func() {
		fmt.Println("function exec")
	})
	c.Start()

	for ; ; {
		time.Sleep(time.Second * 1)
		for _, v := range c.Entries() {
			fmt.Println(v.Next.Local().Format("2006-01-02 15:04"))
		}
	}
}

Run time is 2019-03-21 10:53, this is result:
2019-03-21 10:54
2019-03-21 10:54
function exec
2020-03-21 10:54
2020-03-21 10:54
2020-03-21 10:54

That result looks like it's working as intended. Perhaps you meant "21,30" instead of "21/30" if you expected "2019-03-30" instead?


consider peer reputation score when deciding to disconnect

Noticed in peering logs we are disconnecting quite useful peers with timeouts and "useless responses". This exacerbates peering issues because we are quite early to disconnect, whereas if we just wait a bit longer the peer can still be useful. More of an issue in low peer count networks.

consider peer reputation score when deciding whether to disconnect peer for repeated timeouts/useless responses
increase threshold for timeout counts
decrease score points deducted for timeout/useless response

➜  besu grep  "Disconnect - Outbound" besu03.log
2023-11-17 17:47:27.730+10:00 | nioEventLoopGroup-3-5 | DEBUG | EthProtocolManager | Disconnect - Outbound - 0x0b TIMEOUT - 0x45d5... - 5 peers left
2023-11-17 17:49:10.232+10:00 | nioEventLoopGroup-3-1 | DEBUG | EthProtocolManager | Disconnect - Outbound - 0x0b TIMEOUT - 0xcbba... - 4 peers left
2023-11-17 18:02:33.476+10:00 | nioEventLoopGroup-3-8 | DEBUG | EthProtocolManager | Disconnect - Outbound - 0x03 USELESS_PEER - 0x6a7... - 3 peers left

It think that PR should go along with these two PR that switch peer on retry, otherwise it is possible that we get stuck with a useless peer
https://github.com/hyperledger/besu/pull/5508 https://github.com/hyperledger/besu/pull/5509


Replace 'request.json' by 'request.get_json' if flask is greater than…

… 0.12.2.
Request.json is deprecated since Flask 0.12.2. This commit fix
the handling of this field avoiding a warning. The warning only happens
over Python 3.
Tested with python 3.5.3

The warning is only triggered with python3. Here is how to test it:
https://gist.github.com/dhilst/6e4e76824467d21f12b74f1bd53dbf35

I need an opinion.  The
second do more conservative changes. What you guy prefer?
The third commit fixes the tests.

Here is an example of the warning.

We are seeing these same warnings at our company as well (JW Player), looking forward to the cleanup!

@dhilst this isn't a case anymore. With Flask 1.0. flask .json isn't deprecated anymore.

@galuszkak No problem! :-)

I guess the issue solved itself! Thank you for the PR though :)


Make these errors optional

[x] I've verified and I assure that I'm running youtube-dl 2016.04.19
[x] At least skimmed through README and most notably FAQ and BUGS sections
[x] Searched the bugtracker for similar issues including closed ones

What is the purpose of your issue?

[ ] Bug report (encountered problems with youtube-dl)
[ ] Site support request (request for adding support for a new site)
[x] Feature request (request for a new functionality)
[x] Question
[ ] Other

The following sections concretize particular purposed issues, you can erase any section (the contents between triple ---) not applicable to your issue

Description of your issue, suggested solution and other information
"ERROR: YouTube said: This video is available in Andorra, United Arab Emirates, A
fghanistan, Antigua and Barbuda, Anguilla, Albania, Armenia, Angola, Antarctica,
Argentina, American Samoa, Austria, Australia, Aruba, Åland Islands, Azerbaijan
, Bosnia and Herzegovina, Barbados, Bangladesh, Belgium, Burkina Faso, Bulgaria,
Bahrain, Burundi, Benin, Saint Barthélemy, Bermuda, Brunei Darussalam, Bolivia,
Plurinational State of, Bonaire, Sint Eustatius and Saba, Brazil, Bahamas, Bhut
an, Bouvet Island, Botswana, Belarus, Belize, Cocos (Keeling) Islands, Congo, th
e Democratic Republic of the, Central African Republic, Congo, Switzerland, Côte
d'Ivoire, Cook Islands, Chile, Cameroon, China, Colombia, Costa Rica, Cuba, Cap
e Verde, Curaçao, Christmas Island, Cyprus, Czech Republic, Djibouti, Denmark, D
ominica, Dominican Republic, Algeria, Ecuador, Estonia, Egypt, Western Sahara, E
ritrea, Spain, Ethiopia, Finland, Fiji, Falkland Islands (Malvinas), Micronesia,
Federated States of, Faroe Islands, France, Gabon, United Kingdom, Grenada, Geo
rgia, French Guiana, Guernsey, Ghana, Gibraltar, Greenland, Gambia, Guinea, Guad
eloupe, Equatorial Guinea, Greece, South Georgia and the South Sandwich Islands,
Guatemala, Guam, Guinea-Bissau, Guyana, Hong Kong, Heard Island and McDonald Is
lands, Honduras, Croatia, Haiti, Hungary, Indonesia, Ireland, Israel, Isle of Ma
n, India, British Indian Ocean Territory, Iraq, Iran, Islamic Republic of, Icela
nd, Italy, Jersey, Jamaica, Jordan, Japan, Kenya, Kyrgyzstan, Cambodia, Kiribati
, Comoros, Saint Kitts and Nevis, Korea, Democratic People's Republic of, Korea,
Republic of, Kuwait, Cayman Islands, Kazakhstan, Lao People's Democratic Republ
ic, Lebanon, Saint Lucia, Liechtenstein, Sri Lanka, Liberia, Lesotho, Lithuania,
Luxembourg, Latvia, Libya, Morocco, Monaco, Moldova, Republic of, Montenegro, S
aint Martin (French part), Madagascar, Marshall Islands, Macedonia, the Former Y
ugoslav Republic of, Mali, Myanmar, Mongolia, Macao, Northern Mariana Islands, M
artinique, Mauritania, Montserrat, Malta, Mauritius, Maldives, Malawi, Mexico, M
alaysia, Mozambique, Namibia, New Caledonia, Niger, Norfolk Island, Nigeria, Nic
aragua, Netherlands, Norway, Nepal, Nauru, Niue, New Zealand, Oman, Panama, Peru
, French Polynesia, Papua New Guinea, Philippines, Pakistan, Poland, Saint Pierr
e and Miquelon, Pitcairn, Palestine, State of, Portugal, Palau, Paraguay, Qatar,
Réunion, Romania, Serbia, Russian Federation, Rwanda, Saudi Arabia, Solomon Isl
ands, Seychelles, Sudan, Sweden, Singapore, Saint Helena, Ascension and Tristan
da Cunha, Slovenia, Svalbard and Jan Mayen, Slovakia, Sierra Leone, San Marino,
Senegal, Somalia, Suriname, South Sudan, Sao Tome and Principe, El Salvador, Sin
t Maarten (Dutch part), Syrian Arab Republic, Swaziland, Turks and Caicos Island
s, Chad, French Southern Territories, Togo, Thailand, Tajikistan, Tokelau, Timor
-Leste, Turkmenistan, Tunisia, Tonga, Turkey, Trinidad and Tobago, Tuvalu, Taiwa
n, Province of China, Tanzania, United Republic of, Ukraine, Uganda, United Stat
es Minor Outlying Islands, Uruguay, Uzbekistan, Holy See (Vatican City State), S
aint Vincent and the Grenadines, Venezuela, Bolivarian Republic of, Virgin Islan
ds, British, Virgin Islands, U.S., Viet Nam, Vanuatu, Wallis and Futuna, Samoa,
Yemen, Mayotte, South Africa, Zambia, Zimbabwe only"
This is printed when some videos cant be accessed and youtube supplies a message I want a option to turn that printing of that message off as my dict currently does not work even if I have quiet set to True.
my dict is this.
ytdlo = {'quiet': True, 'no_warnings': True, 'ignoreerrors': True}

Just catch ExtractorError and do whatever you want.

Logger can be used to intercept errors though it will hook all the errors.


Autofocus even when autofocus is set to false

When creating a dropdown with the below code:
VirtualSelect.init({ ele: this, search: true, zIndex: 1000, maxWidth: maxWidth, autofocus: false });
The page autofocuses to the dropdown element.
This issue appears to only happen in 1.0.45
I have tested versions going back to 1.0.40, and prior versions seems to be ok.
My guess is it has to do with this line: https://github.com/sa-si-dev/virtual-select/pull/350/files#diff-7075f90f187d4b281f22b3136982040883bc7595e92f73267c6e47868729dd64R2359
commenting it out on version 1.0.45 seems to solve the issue, however I'm not proficient in JS enough to dig deeper than that.

@slinkymanbyday I was also able to reproduce a similar issue but only when the dropdown has initial values.
Could you share a sample in codepen or similar with your particular use case?

it happens when I'm setting initial values, I just noticed the silentInitialValueSet param. I'll try that and see if it helps

Can confirm that silentInitialValueSet has worked for me. still kinda strange that focus happens when this value is true, but since it's working happy for this issue to be closed.


BUILD FAILED .. SwiftEmitModule normal arm64 Emitting module for react_native_llm_mediapipe

I managed with some effort, to spin up the project from example app,
but after I install llm-mediapipe using npm on freshly generated project, I get an error after running the project
 nvm use --lts
 # also tried with nvm use 18
 # also tried latest RN
npx @react-native-community/cli@latest init LlmMediapipeExample --version 0.73.7
cd LlmMediapipeExample
npm install react-native-llm-mediapipe

# in xcode copy gemma-2b-it-cpu-int4.bin to the root of the project

 cd ios && pod install && cd ..
 npx react-native run-ios

Output:
...
Lots of errors
...
/Users/user/Library/Developer/Xcode/DerivedData/LlmProject-afbekltqetkvwhabyqjxrvrkpevz/Build/Intermediates.noindex/Pods.build/Debug-iphonesimulator/react-native-llm-mediapipe.build/Objects-normal/arm64/react_native_llm_mediapipe.abi.json
/Users/user/Data_local/projects/mntl/llm_research/makingitwork/LlmProject/node_modules/react-native-llm-mediapipe/ios/LlmInferenceModel.swift:32:16: error: value of type 'LlmInference.Options' has no member 'topk'
llmOptions.topk = self.topK
....
warning: Run script build phase 'Bundle React Native code and images' will be run during every build because it does not specify any outputs. To address this issue, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'LlmProject' from project 'LlmProject')
--- xcodebuild: WARNING: Using the first of multiple matching destinations:
{ platform:iOS Simulator, id:A0DDE1B1-E28F-45E5-964F-3D8FEA09663D, OS:18.0, name:iPhone SE (3rd generation) }
{ platform:iOS Simulator, id:A0DDE1B1-E28F-45E5-964F-3D8FEA09663D, OS:18.0, name:iPhone SE (3rd generation) }
** BUILD FAILED **
The following build commands failed:
SwiftEmitModule normal arm64 Emitting\ module\ for\ react_native_llm_mediapipe (in target 'react-native-llm-mediapipe' from project 'Pods')
EmitSwiftModule normal arm64 (in target 'react-native-llm-mediapipe' from project 'Pods')
Building workspace LlmProject with scheme LlmProject and configuration Debug
(3 failures)

UPD.
I commented these lines
in node_modules/react-native-llm-mediapipe/ios/LlmInferenceModel.swift
and it's running now, although i'm not sure yet, if it runs as intended, it responds something on the first prompt, and stops responding for the second prompt.
final class LlmInferenceModel {

  weak var delegate: LlmInferenceModelDelegate?

  private lazy var inference: LlmInference! = {
    let llmOptions = LlmInference.Options(modelPath: self.modelPath)
    llmOptions.maxTokens = self.maxTokens
    //llmOptions.topK = self.topK
    //llmOptions.temperature = self.temperature
    //llmOptions.randomSeed = self.randomSeed
    return try? LlmInference(options: llmOptions)
  }()


Fix retry-subscriber version

According to the entire readme, it's based on Guzzle ~5.0, but in the installing section, the subscriber points to version ~1.0 which require guzzle ~4.0

is there anybody out there?

:+1: :ship:


Docker image very big containing a lot of unnecessary stuff

What happened:

The image<PHONE_NUMBER>52.dkr.ecr.eu-central-1.amazonaws.com/amazon/aws-network-policy-agent:v1.0.8-eksbuild.1  is very big and takes more than 20 seconds to download.
Looking into the image it contains things like old kernel sources:
bash-4.2# ls -la /usr/src/kernels/
total 4
drwxr-xr-x.  1 root root   44 Feb  5 20:48 .
drwxr-xr-x.  1 root root   21 Jan 23 17:37 ..
drwxr-xr-x. 23 root root 4096 Feb  5 20:48 4.14.336-255.557.amzn2.aarch64

Furthermore it contains a lot of other stuff
bash-4.2# cd /
bash-4.2# du -s -h .
du: cannot access './proc/78/task/78/fd/4': No such file or directory
du: cannot access './proc/78/task/78/fdinfo/4': No such file or directory
du: cannot access './proc/78/fd/3': No such file or directory
du: cannot access './proc/78/fdinfo/3': No such file or directory
975M	.
bash-4.2# du --max-depth=1 -h .
0	./boot
0	./dev
2.1M	./etc
0	./home
0	./local
0	./media
0	./mnt
0	./opt
du: cannot access './proc/79/task/79/fd/4': No such file or directory
du: cannot access './proc/79/task/79/fdinfo/4': No such file or directory
du: cannot access './proc/79/fd/3': No such file or directory
du: cannot access './proc/79/fdinfo/3': No such file or directory
0	./proc
4.0K	./root
20K	./run
0	./srv
0	./sys
0	./tmp
764M	./usr
19M	./var
104M	./host
975M	.
bash-4.2# du --max-depth=1 -h /usr/
74M	/usr/bin
0	/usr/etc
0	/usr/games
20M	/usr/include
44M	/usr/lib
351M	/usr/lib64
56M	/usr/libexec
4.0K	/usr/local
5.7M	/usr/sbin
123M	/usr/share
92M	/usr/src
764M	/usr/
bash-4.2# du --max-depth=1 -h /usr/share/
0	/usr/share/X11
8.0K	/usr/share/aclocal
32K	/usr/share/applications
0	/usr/share/augeas
84K	/usr/share/awk
0	/usr/share/backgrounds
72K	/usr/share/bash-completion
0	/usr/share/desktop-directories
0	/usr/share/dict
19M	/usr/share/doc
0	/usr/share/empty
0	/usr/share/file
0	/usr/share/games
216K	/usr/share/gcc-7
8.0K	/usr/share/gdb
0	/usr/share/ghostscript
0	/usr/share/glib-2.0
0	/usr/share/gnome
312K	/usr/share/gnupg
0	/usr/share/i18n
0	/usr/share/icons
0	/usr/share/idl
4.4M	/usr/share/info
1.1M	/usr/share/licenses
54M	/usr/share/locale
0	/usr/share/lua
8.1M	/usr/share/man
5.4M	/usr/share/mime
0	/usr/share/mime-info
2.8M	/usr/share/misc
0	/usr/share/omf
4.0K	/usr/share/p11-kit
0	/usr/share/pixmaps
4.0K	/usr/share/pkgconfig
1.1M	/usr/share/pki
0	/usr/share/sounds
4.0K	/usr/share/systemtap
16K	/usr/share/tabset
476K	/usr/share/terminfo
0	/usr/share/themes
12K	/usr/share/vim
0	/usr/share/xsessions
908K	/usr/share/yum-cli
0	/usr/share/yum-plugins
4.5M	/usr/share/zoneinfo
16K	/usr/share/zsh
1.9M	/usr/share/groff
48K	/usr/share/opt-viewer
20M	/usr/share/perl5
123M	/usr/share/

Attach logs

Successfully pulled image "602401143452.dkr.ecr.eu-central-1.amazonaws.com/amazon/aws-network-policy-agent:v1.0.8-eksbuild.1" in 20.619s (20.619s including waiting)

What you expected to happen:
I would like to see a minimal image without any unnecessary stuff.
How to reproduce it (as minimally and precisely as possible):
Install latest aws cni.
Anything else we need to know?:
Especially security related stuff like this agent should be using a very thin auditable image.
Environment:

Kubernetes version (use kubectl version): 1.29.x
CNI Version: v1.16.3-eksbuild.2
Network Policy Agent Version:  v1.0.8-eksbuild.1
OS (e.g: cat /etc/os-release): na
Kernel (e.g. uname -a): na

Possibly related to
https://github.com/aws/aws-network-policy-agent/pull/212
This change should be out soon

New version v1.1.0 is out which uses the minimal build. It reduces the image size to ~40 MB.

addressed via the new node agent release.


add wire/edge methods position_at, tangent_at, location_at to class Curve

Currently the operators @, %, ^ for position_at, tangent_at, location_at are bound to class Curve but the actual methods position_at, tangent_at, location_at are not present

Please hold off on this.  As part of the refactoring of topology.py (Issue #788) Curve is changing. Still needs some verification but a Curve that can be a Wire is converted to one during the + operation so all the normal Mixin1D methods work for them.  If the Curve consists of disconnected Edges then it will be a Compound and these operations don't apply.

Makes sense, and sounds good -- I started working on it briefly and then realized I was creating more entanglements so I stopped.


Null pointer exception: Ticking entity 1.14

I've been having issues in my modpack for quite a while now with null pointer crashes on ticking entities. We've looked into it and we believe it's your mod that is causing the issue. If i'm wrong I apologize.
Here's a couple example crash logs:
https://pastebin.com/ipuxM5nf
https://paste.ee/p/rlYdy
Here's the modpack for reference:
https://www.curseforge.com/minecraft/modpacks/valuepack-2/files

Not sure why you think apoth has anything to do with that, damage indicatiors is the only mod in the call stack, which means its on them


Which Ctrl?

Currently, both Ctrl could be used to switch to the next desktop, how can I limit it to only work for right or left ctrl? Thanks.

This is a DLL, it does not bind keyboard shortcuts. You bind shortcuts with own AutoHotkey script.
I'm closing this issue, but feel free to ask more questions, maybe your issue is with autohotkey script of yours.


release: [v3.6.1] (June 30 2023)

Feat:

Enable channel creation when no user present to select
Mobile: Keep keyboard open after sending the message

Fixes:

Update @sendbird/uikit-tools to 0.0.1-alpha.39
alpha.39 has CJS support, otherwise, UIKit wont work
on next-js page router

Chore:

Update all examples to V4 + StackBlitz

Update all sample code to V4
Convert CodeSandbox to StackBlitz
Render all examples with Vite
Thanks @tylerhammer

/bot create ticket

[Creating Ticket] 🔖 Done https://sendbird.atlassian.net/browse/SDKRLSD-891

https://www.youtube.com/watch?v=KSQ-xv8ZLQg


Update docs, tutorial

The tutorial now includes the step for adding SwiftGodotMacros to Package.swift.
The README now also demonstrates the initSwiftExtension macro.

Thank you for the update!


Add Install button for Insiders on Marketplace

As I see it could be done by simply adding a button with slightly changed href
- <a href="vscode:extension
+ <a href="vscode-insiders:extension

@joaomoreno This has to be supported by market place right?

cc @viradhamMS @pkuma-msft
We already brought this up, especially during the design phase of the install button. Is this in the Marketplace's backlog yet?

@joaomoreno Yes this is in our backlog

@usernamehw We care. But we also care about other stuff. 👍

From the message it seems like there's a separate issue tracker where this issue already exists...

Has anyone created a userscript for this?

I mean ... it's just feels useless keeping it open.
For button design you can try something like split dropdown:

The main button would install in Stable, while dropdown would contain (Insiders & Exploration) entries.
https://getbootstrap.com/docs/4.0/components/dropdowns/#split-button-dropdowns


Glaze Theme

After i started my Spotify today it was buggy. I completely uninstalled spotify and spicetify and reinstalled it. The Bar with the volume, current song etc is slipped very far up. I have the newest spotify and spicetify version.

@v6r Fixed in my most PR


fix: 避免锁超时

这个 PR 实现什么功能/修复什么问题:
避免锁超时
是否需要 backport 到之前的 release 分支:

release/2.13

/area region
/cc @wanyaoqi

Codecov Report

Merging #6686 into master will increase coverage by 0.01%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master    #6686      +/-   ##
==========================================
+ Coverage    7.14%    7.16%   +0.01%
==========================================
  Files         647      647
  Lines      109345   109346       +1
==========================================
+ Hits         7818     7831      +13
+ Misses     100929   100917      -12
  Partials      598      598

Flag
Coverage Δ

#aFlag
7.16% <0.00%> (+0.01%)
:arrow_up:

Impacted Files
Coverage Δ

pkg/compute/models/secgroups.go
1.88% <0.00%> (-0.01%)
:arrow_down:

pkg/cloudcommon/validators/validators_cert.go
39.77% <0.00%> (ø)

pkg/cloudcommon/cronman/cronman.go
53.95% <0.00%> (+5.11%)
:arrow_up:

pkg/cloudcommon/db/lockman/fifo.go
90.00% <0.00%> (+10.00%)
:arrow_up:

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 9307660...a519a66. Read the comment docs.

/lgtm

/lgtm

/lgtm

/approve


suprpress broken links

What type of PR is this?
/kind cleanup
What this PR does / why we need it:
This PR ensures we never ship any broken link by throwing an error.
https://docusaurus.io/docs/api/docusaurus-config#onBrokenLinks
https://docusaurus.io/docs/api/docusaurus-config#onBrokenMarkdownLinks
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:

https://app.netlify.com/sites/karmada/deploys/6308433328f4a100095e8410
11:53:30 AM: [success] [webpackbar] Client: Compiled with some errors in 28.36s
11:53:30 AM: Error: Docs markdown link couldn't be resolved: (../clustermanager/working-with-anp.md) in "/opt/build/repo/docs/userguide/globalview/proxy-global-resource.md" for version current


Add Releases for SVD files ?

Could we add resulting SVD as release files ? In this way we could download them from any scripting, IDE, command line tool that wants to work with them.
Also enabling mirrors in Espressif DL servers.

One place where they are stored is here: https://github.com/posborne/cmsis-svd/tree/master/data/Espressif
Probably out of date, but it might be useful.

Not against doing this but I'm not really sure how to go about accomplishing it. SVDs are updated irregularly (they do not get updated all at once) and the version numbers are not in sync.

How about making an automated release whenever something gets updated, using the current YYYYMMDD date as the release tag? Not ideal, but at least it's going to be pretty easy to set up and won't require changes to the project workflow.

We could also maintain the "latest" release using https://github.com/eine/tip.


Bar chart mouse over the bar is black

I have an issue with the bar color when the mouse is over a bar. This is the example and how the bars are displaying at the beginning.

When the mouse goes over a bar, the bar becomes black first

and then, after few seconds, the bar has the expected colour.

How can I fix it?
Thank you,
Henry

Fixed it


[Feature] Add "Cancel" button in Edit Profile

Hi,
In the "Edit Profile" page:

Can we add a "Cancel" button here (next to "Submit") that redirects to the homepage? Thank you

I think Cancel button is not needed because it is not a modal dialog but a full page. Normally people add cancel to dialogs/modals when they appear on top of the page hiding the content behind.


Cover tmt.libraries with pyright checks

Pull Request Checklist

[x] implement the feature

/packit test --identifier full


WIP: ENH: Use input and target in hedging loss (#568)

Codecov Report

Merging #569 (27b116a) into main (b45416a) will increase coverage by 0.58%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #569      +/-   ##
==========================================
+ Coverage   96.56%   97.15%   +0.58%
==========================================
  Files          56       56
  Lines        2303     2318      +15
==========================================
+ Hits         2224     2252      +28
+ Misses         79       66      -13

Impacted Files
Coverage Δ

pfhedge/nn/functional.py
91.56% <ø> (+5.33%)
:arrow_up:

pfhedge/nn/modules/hedger.py
100.00% <100.00%> (ø)

pfhedge/nn/modules/loss.py
100.00% <100.00%> (ø)

pfhedge/autogreek.py
100.00% <0.00%> (ø)

pfhedge/instruments/derivative/base.py
93.02% <0.00%> (ø)

pfhedge/nn/modules/bs/european_binary.py
100.00% <0.00%> (ø)

Continue to review full report at Codecov.

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


version upgrade 3.0.0-beta to 3.0.0-rc

Hi, i try to version upgrade  beta to rc, cropper is not stretch the parent. This only happens on android device.Width and height seem to be calculating incorrectly.
Version 3.0.0-beta

Version 3.0.0-rc

Just set the width of your image and image container to 100%:
.img-container {
  width: 100%;
}

.img-container > img {
  width: 100%;
}

Nope, i already have this. it is the same, only android browser have this problem.

html

javascript
$image.attr('src', selectedImage);
 setTimeout(function(){
     $image.cropper({
                            rotatable: false,
                            cropBoxResizable: false,
                            aspectRatio: 16 / 9,
                            dragMode: "move",
                            viewMode: 2,
                            autoCropArea: 1,
                            minCropBoxWidth:"2000",
                            minCropBoxHeight:"2000",
                        });
 $(window).trigger('resize');

}, 500);

v3.0.0-rc.3 has the same problem. You closed the issue but problem problem still persistç

I have not idea on this, you might have to check your code carefully for the problem by yourself.