ScssLint not using config file

I have a .scss-lint.yml file that is being ignored by my PreCommit hook.
.scss-lint.yml:
scss_files: 'app/assets/stylesheets/**/*.scss'
.overcommit.yml:
PreCommit:
  RuboCop:
    enabled: true
    on_warn: fail # Treat all warnings as failures
  Reek:
    enabled: true
  ScssLint:
    enabled: true
PrePush:
  RSpec:
    enabled: true

And the output has a ton of errors from files such as:
/Users/eric/Development/proj/web/vendor/assets/stylesheets/bourbon/_bourbon.scss:72 StringQuotes: Prefer single quoted strings

One more thing - when I run scss-lint from the command line in the root of the project, it does work properly (ignoring all those issues in the vendor directory).

Is the .scss-lint.yml file tracked by git? I seem to remember a similar issue where a file was ignored because it wasn't in the git index.

I can confirm that .scss-lint.yml is committed to the repo and is not in .gitignore, with the contents:
scss_files: 'app/assets/stylesheets/**/*.scss'
I confirmed this by checking the proper branch on github.

overcommit 0.32.0
I have been running overcommit --run but if we think that might be related, I could just do a git commit.

It does seem to work properly when run via a git commit but not when run via overcommit --run.

What happens if you run with bundle exec overcommit --run?

Here you go:
Erics-MacBook-Pro:web eric$ bundle exec overcommit --run
Running pre-commit hooks
Analyze with scss-lint.....................................[ScssLint] FAILED
Unable to parse JSON returned by SCSS-Lint: A JSON text must at least contain two octets!
STDOUT:
STDERR: Bundler is using a binstub that was created for a different gem.
This is deprecated, in future versions you may need to `bundle binstub scss_lint` to work around a system/bundle conflict.
/Users/eric/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/scss-lint-0.30.0/bin/scss-lint:7:in `block in <top (required)>': undefined method `parse_arguments' for #<SCSSLint::CLI:0x007f9bd99c46f0> (NoMethodError)
	from /Users/eric/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/scss-lint-0.30.0/bin/scss-lint:6:in `tap'
	from /Users/eric/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/scss-lint-0.30.0/bin/scss-lint:6:in `<top (required)>'
	from /Users/eric/.rbenv/versions/2.3.0/bin/scss-lint:23:in `load'
	from /Users/eric/.rbenv/versions/2.3.0/bin/scss-lint:23:in `<main>'

Analyze with RuboCop........................................[RuboCop] OK
Analyze with Reek..............................................[Reek] OK

✗ One or more pre-commit hooks failed

Erics-MacBook-Pro:web eric$

Also, I am trying to do a git commit now and I am getting this:
Erics-MacBook-Pro:web eric$ git commit -m '[#114570237] Improve survey styling'
Running pre-commit hooks
Analyze with scss-lint.....................................[ScssLint] FAILED
Warnings on lines you didn't modify:
/Users/eric/Development/proj/web/vendor/assets/stylesheets/bourbon/addons/_buttons.scss:1 StringQuotes: Prefer single quoted strings

Analyze with Reek..............................................[Reek] OK
Analyze with RuboCop........................................[RuboCop] OK

✗ One or more pre-commit hooks failed

even though that file should be ignored based on my .scss-lint.yml file - so I guess it's not really working in the git commit case either.

Notice from the stack trace that scss-lint-0.30.0 is the version being run. It should be scss_lint (with an underscore) and a much newer version. Please upgrade to the latest version.

Closing. Feel free to reopen if upgrading doesn't fix the issue, but I'm pretty sure that's the issue here.

Good catch @vill, would you be willing to submit a PR for that?

@trotzig, please check #457

i still have this error after all updates

please help me to  resolve it

overcommit 0.38.0

@miukki, I have such versions all works fine:
# Gemfile
gem 'scss_lint', '~> 0.52.0', require: false
gem 'overcommit', '~> 0.38.0', require: false

What is the output of this commands gem list scss-lint and which scss-lint?

Maybe this:

@trotzig commented on Mar 1, 2016
Is the .scss-lint.yml file tracked by git? I seem to remember a similar issue where a file was ignored because it wasn't in the git index.


Log is expanding rapidly

Docker Outline container log file is expanding rapidly.
Within a week it grew to 6GB on two different servers.
No clients! I don't have a single client!
Do I need to set a cron task to delete the log every day?
How to turn off the log?

Hi @webair-studio , do you mean Outline Server logs? If so, could you please create an issue in https://github.com/Jigsaw-Code/outline-server/issues? Thanks.


Add requests package to setup.py

Issue overview
The requests package is not imported by another dependency when pip installing buildstock-query. Unclear poe
Current Behavior
The library does not work after installing via setup.py because of missing requests dependency
Expected Behavior
The library works after installing via setup.py

@asparke2 Can you add a minimal reproducible example?
I created a new python environment, installed requests library and then installed buildstock-query
conda create -n test_env python=3.10
conda activate test_env
pip install requests
pip install git+https://github.com/NREL/buildstock-query

I was then able to import both buildstock_query and requests.
from buildstock_query import BuildStockQuery
import requests  # no error

@rajeee remove the pip install requests from your minimal example and run from buildstock_query import BuildStockQuery and you get:
>>> from buildstock_query import BuildStockQuery
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "C:\Users\aparker\Anaconda3\envs\test_env\lib\site-packages\buildstock_query\__init__.py", line 63, in <module>
    from buildstock_query.main import BuildStockQuery
  File "C:\Users\aparker\Anaconda3\envs\test_env\lib\site-packages\buildstock_query\main.py", line 7, in <module>
    from buildstock_query.tools import UpgradesAnalyzer
  File "C:\Users\aparker\Anaconda3\envs\test_env\lib\site-packages\buildstock_query\tools\__init__.py", line 1, in <module>
    from .upgrades_analyzer import UpgradesAnalyzer
  File "C:\Users\aparker\Anaconda3\envs\test_env\lib\site-packages\buildstock_query\tools\upgrades_analyzer.py", line 13, in <module>
    from buildstock_query.tools.logic_parser import LogicParser
  File "C:\Users\aparker\Anaconda3\envs\test_env\lib\site-packages\buildstock_query\tools\logic_parser.py", line 7, in <module>
    from buildstock_query.file_getter import OpenOrDownload
  File "C:\Users\aparker\Anaconda3\envs\test_env\lib\site-packages\buildstock_query\file_getter.py", line 1, in <module>
    import requests
ModuleNotFoundError: No module named 'requests'

Basically what I'm saying is that requests needs to be added to setup.py since it's a runtime dependency of buildstock-query. A user shouldn't have to manually pip install it separately.

Oh duh! Your Issue title was clear enough. Got confused by the description!


feat(ffe-tables): modifier to preserve whitespace

Added a --preserve-white-space modifier to the table cell
class ffe-table__cell. Using this will add white-space: pre
to the cell it's used on.

It doesn't seem like the less-modules are documentet any more so I couldn't figure out a good place to add documentation for this modifier. Normally the React component would have it but

Nothing is currently documentet in the styleguide because there are no inline comments for anything in the propTypes and it looks like a giant scope-creep to have to document the entire component just to add a modifier in the less-package.

I don't see how the current API of Table would let me selectively add a modifier to a table cell in any kind of useful way so I can't really make a corresponding change in the component that can act as documentation

If nothing else, it's going to be listed in the changelog so that's something I guess.

Coverage remained the same at 77.992% when pulling 46dc09b18b5abf1accad647b67dc368c4b13070b on ivarni:add-preserve-whitespace-modifier into cfc949e954dc37e1746422135e32138a7b7c4272 on SpareBank1:master.

Is this a common case? If not, could this be achieved by nesting <pre> tags or with app-specific css classes?

I dunno 🤷♂
It's a case for me right now at least. <pre> changes the font-family and I thought we were trying to avoid app-specific changes to the FFE css but it's actually less work for me to do that so if you prefer a local solution, sure.

Nothing is currently documentet in the styleguide because there are no inline comments for anything in the propTypes

Wrong prop types
As you point out, though, they aren't showing up in the style guide. That's a bug - I've created an issue for it.
As for the modifiers, it can be added to each column - wouldn't that be good enough? Like the alignRight modifier found here.

Uh.. it's already implemented like that but just not documented?

If you refer to the documentation, then yes. Looks like there was some kind of bug in the source code parser that Styleguidist uses that didn't recognize this component as a component. That's fixed now in this pull request. If you refer to something else, I don't think I quite understand what 😄
The columns array is our API to add behavior and looks to each column. Examples are whether or not they are sortable, or if you should align the text a certain way. All the data is passed through the data prop.
All of that aside, I think I agree with @kwltrs here - a local solution might be the most appropriate here (at least until we see there's a lot of preformatted text in our consumer code bases.

Can we close this PR?

That's up to you.
I'd like to see it merged (or I wouldn't have created the PR), but it's ultimately not my decision what happens with it.


The “Swift Language Version” (SWIFT_VERSION) build setting must be set to a supported value for targets which use Swift. This setting can be set in the build settings editor.

🐛 Bug Report

google_api_availability does not specify a Swift version and none of the targets (Runner) integrating it have the SWIFT_VERSION attribute set. Please contact the author or set the SWIFT_VERSION attribute in at least one of the targets that integrate this pod.
Expected behavior
Reproduction steps
Configuration
Version: 3
Platform:

[x] :iphone: iOS
[x] :robot: Android

Duplicate of #219


⚠ Bofrost.lu has degraded performance

In 38b5ca8, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1000 ms

Resolved: Bofrost.lu performance has improved in edbf373 after 6 minutes.


Does stream-sql supports FOR JSON clause?

SQL Server 2016 and Azure SQL Database provide new FOR JSON clause that formats results of SQL query as JSON text. However it does not returns one single JSON text - it splits output JSON into 2KB chunks and each chunk is returned as a separate row see https://msdn.microsoft.com/en-us/library/dn921882.aspx#Anchor_3
This looks like a perfects fit for your library, so I wander have you tried it? If this is supported we could execute SQL query with FOR JSON clause and simply pipe results into some output stream (maybe even a Http response of express REST service).
This might be nice use case for some example in Readme.md file.

I have tried to stream results of FOR JSON to express response and it failed. Code:
router.get('/', function (req, res) {
    sql.execute("select * from todo for json path").pipe(res);
});

It failed with the following error:
 _http_outgoing.js:430
      throw new TypeError('first argument must be a string or Buffer');

I see in index.js that it has received expected JSON as object instead of text, but I'm not sure is this a bug or not supported feature.

I have fixed this problem and sent pull request https://github.com/randolpho/stream-sql/pull/3 . Following function is updated:
   function TdsRow(columns) {
      var rowObj = {};
      if (columns.length == 1 &&
              (columns[0].metadata.colName == "JSON_F52E2B61-18A1-11d1-B105-00805F49916B"
              || columns[0].metadata.colName == "XML_F52E2B61-18A1-11d1-B105-00805F49916B")) {
          rowObj = columns[0].value;
      } else {
          columns.forEach(function (column) {
              rowObj[column.metadata.colName] = column.value;
          });
      }
      responseStream.push(rowObj);
  }


Add missing copy=False updates

Addressing #20170
@rgommers @matthewfeickert Here's a fix for "Unable to avoid copy" errors pointed out in #20170.
I missed those due to the fact that np.array(..., copy=copy) were placed in subclasses.

I'm working on a few more shims locally (I needed way more changes for full suite to pass)

I'm working on a few more shims locally (I needed way more changes for full suite to pass)

@mtsokol @tylerjereddy In that case, do you want me to go for https://github.com/scipy/scipy/issues/20170#issuecomment-1973884589?

continued in gh-20172


Update the integration parameter delta time

This is expected to be accurate by a good bit of users of the library, including rapier's KCC impl here. So we should probably keep it updated/accurate with what the simulation is actually stepping by.
Some thoughts: We might want to do this in a separate function from step_simulation, in something like PreUpdate or First, because a lot of users are likely to have their systems ordered before PhysicsSet::StepSimulation. This means there would be a 1 frame lag here, so we'd be reading the previous frame time rather than next.

Thanks!


[eas-cli] Split republish command from update command

Checklist

[ ] I've added an entry to CHANGELOG.md if necessary. You can comment this pull request with /changelog-entry [breaking-change|new-feature|bug-fix|chore] [message] and CHANGELOG.md will be updated automatically.

Why
Part of ENG-5926
It also fixes or improves a couple of things:

Do not create a new git hash for the republished update
Reuse old code signing from the original update (instead of calculating again)
Explicitly block republishing to a different branch, with helpful next-step commands

TODO

Drop the republish logic from eas update and refer to eas update:republish when using eas update --republish or eas update --group -> Will be a new PR stacked on this one.

How
Copied existing republish code from eas update, and moved it to a new command. This command now has basic tests to validate exit cases and a successful publish (with mocks).
As for fix #1 - We actually ask the VSC client for a new hash when republishing with eas update, which is incorrect. It should use the existing git reference from the original update.
As for improvement #2 - @wschurman, I believe this is the correct behavior (specifically for republishing).
As for fix #3 - When using environment variables to load the branch name within the app, this will be incorrect when reusing the exact same bundle to publish on another branch. Because of that, I added this block with commands to still achieve what the user might want to do.
Test Plan
Instead of:
$ eas update --republish --branch <name> --group <id>

You can now use any of:
# Assumes the branch from existing group
$ eas update:republish --group <id>

# Asks users to pick an update from the branch
$ eas update:republish --branch <name>

# Edit: As per https://github.com/expo/eas-cli/pull/1533#discussion_r1029882169
# Defining both `--branch` and `--group` is now invalid.

# Both are also possible, but branch is validated to be the same (see #3)
# $ eas update:republish --branch <name> --group <id>

Looks good as far as the feature goes, just a few comments. Nice test!

Drop the republish logic from eas update and refer to eas update:republish when using eas update --republish or eas update --group -> Will be a new PR stacked on this one.

yep, let's just make use of the flag throw and inform the user that the command has changed (breaking change).

Done in #1535 :)

/changelog-entry breaking-change Move update republish to separate command

/changelog-entry breaking-change Move update republish to separate command


Example not working when I publish

Hi everyone,
I can't make it run the basic sample at index script on a lambda function, here's what I did:
Clone this repo and then run npm install... test locally and works.
Then I run serverless deploy, everything get published, but when I run I always have this issue:
"errorMessage": "No node found for selector: #lst-ib", (to test, I simply go to the lambda function, and run a test)
Actually, I can't inspect any element, If I use waitForSelector I have a timeout, so I assume that page never get loaded.
Here's part of log:

START RequestId: 031bea5a-d60d-11e8-94d7-015d775a53cf Version: $LATEST
2018-10-22T15:13:22.647Z	031bea5a-d60d-11e8-94d7-015d775a53cf	setup local chrome
2018-10-22T15:13:24.574Z	031bea5a-d60d-11e8-94d7-015d775a53cf	setup done
2018-10-22T15:13:25.359Z	031bea5a-d60d-11e8-94d7-015d775a53cf	launch done: HeadlessChrome/67.0.3361.0

Is there an issue with this build or I'm missing something?
Thanks in advance.

Your browser is starting properly, but must likely puppeteer isn't working.
The problem here is that only certain versions of puppeteer will work with this compiled binary included in the package.
At the moment, in package.json you have puppeteer dependency declared with version "^1.0.3" which means, when you run npm install it will fetch the latest available package. Anything up till 1.10 works, but if you install 1.11 or 1.12 - it will fail.
Just use the 1.0.3 puppeteer with the 67 binary and you'll be good to go. Also, change the package.json

@vbrundic
I deployed the package.zip with chrome

without modifying package.json
changing puppeteer version to ~1.3.0 in package.json and re-packaging

Both resulted in the same error. Please help
START RequestId: c6f56420-aca0-46ee-b8e8-26f9780d85ca Version: $LATEST
END RequestId: c6f56420-aca0-46ee-b8e8-26f9780d85ca
REPORT RequestId: c6f56420-aca0-46ee-b8e8-26f9780d85ca	Duration: 3003.29 ms	Billed Duration: 3000 ms 	Memory Size: 128 MB	Max Memory Used: 87 MB
2019-02-06T05:46:54.232Z c6f56420-aca0-46ee-b8e8-26f9780d85ca Task timed out after 3.00 seconds```

I was running into this same issue and it was due to a newer version of puppeteer being installed. I deleted my node_modules folder then pinned the version of puppteer in my package.json to "puppeteer": "1.10" and ran npm install. I re packaged and deployed and the sample script is working for me I see the source logged but also the element just has a bad selector (I think). So it's working if you see the html in cloudwatch logs.

It would be nice if anyone states explicitly the versions which are compatible with this lib :)
Took me so much time to realize that I was using the wrong version of puppeteer too. It only works for versions till ˆ1.1.0 by the time I'm writing this comment.
Thanks in any case for the great job 👍

I had "puppeteer": "1.1.1" and it was silently failing, without any exceptions.
1.1.0 version works!

With this version I can't find a puppeteer version that works, not even 1.1.0 :( It gets stuck in this line

@feliun I am using the other file headless_shell.tar.gz.
And I'm using puppeteer 1.1.1
I didn't try with the other one. It's working fine for me

I just downloaded the exact example from the repo, deployed the lambda and didn't work out of the box with 1.1.1. Some people stated the puppeteer version should be downgraded but not even like that. If it's not the code, could it be something different on my lambdas @jprivillaso ?

Bloody hell! Yeah I was using the caret coming from the repo. When I changed my package.json to "puppeteer": "~1.1.0", it did work!

I can share later the codebase that I am using if you want

I had the same problem. I've submitted two PRs to update this starter kit:
First pins puppeteer to v1.3.0, which is the latest which puppeteer itself bundled with chrome v67: https://github.com/sambaiz/puppeteer-lambda-starter-kit/pull/45
Second PR updates to nodejs 8.10 syntax and fixes the google query element selector: https://github.com/sambaiz/puppeteer-lambda-starter-kit/pull/46
Hopefully these PRs will be integrated soon. Otherwise, you can find them already integrated on my fork: https://github.com/mglasgow/puppeteer-lambda-starter-kit


Add Logo instead of Text

Here i want to add a logo so it looks good for user so it can navigate easily rather than the text looks as usual . i want to add logo, please assign this issue to me under SWOC (Social Winter of Code)

@saismrutiranjan18 create all your issues in one pr

@saismrutiranjan18 create all your issues in one pr

If you don't mind I'll contribute after 1st Jan because it'll count from 1st January

@saismrutiranjan18 create all your issues in one pr

If you don't mind I'll contribute after 1st Jan because it'll count from 1st January

ok fine

@saismrutiranjan18 create all your issues in one pr

If you don't mind I'll contribute after 1st Jan because it'll count from 1st January

ok fine

which issue I raise should I have to done in one PR or for another? And what about points is it for one or for separate?

#5 in separate pr remain u can do in one pr

#3 and #5  in separate pr remain u can do in one pr

Ok Thank you very much


Matrix conversion

This PR is for #195. Updates to file conversion and functional tests for new implementation

Hm why didn't codecov run?

Just a thought, do we want to separate the results S3 bucket into one for Redshift query results and one for expression matrices? We probably want to clean up the former with an expiration policy and not the latter

I have no idea why neither Travis nor Codecov ran 🤔

https://github.com/HumanCellAtlas/matrix-service/issues/236 created


Add node 0.10 to TravisCI and fix test

Something change in how sort compares objects (?).
Removed the sort which is also better since then the correct order is also tested,

@johnjbarton TBR


Future Works < - > Nice to Haves

@lwhiteley feature that you think we be useful and that we should add to the logger.

app.config(['logExProvider', function(logExProvider) {
    // this will extend the default configurations configure global templating
    logExProvider.disallow("^s.+e$"); // ignores messages starting with an 's' and ending with a 'e'
}]);

$log.log('something confidential, ignore please');

// >> Dec-08-2013-1:00:47PM >>  ['filtered']

we can build an ajax hook, that will allow persons to persist data on their back-end
app.config(['logExProvider', function(logExProvider) {
    // ignores messages starting with an 's' and ending with a 'e'
    logExProvider.persist({
        "batchSize": 3,
         executor : function (logs) {...}
     });
}]);


Fix camera names

unify camera names
better loading and searching for known cameras (in case no simtel file is open)

so far camera names look like this:

see also issue #255

Do you plan to change "GATE" to "CHEC" now? I noticed you reverted "GCT" back to "GATE".

this fixes #404

Do you plan to change "GATE" to "CHEC" now? I noticed you reverted "GCT" back to "GATE".

I think GATE is gone now (at least it should be - do you see somewhere where it was missed?), it's only CHEC.  Note that GCT is the name of the telescope, but GATE is the name of the camera (this is the camera_id), so I think that makes the most sense.  Imagine for example putting a "GATE" camera on an Astri telescope, for example, and then it wouldn't make sense to call it GCT.  When I finish implementing the TelescopeOptics classes (which are like CameraGeometry but for the telescope), those will be associated with a telescope name and version (so 'GCT' would make sense there).

Never mind, I see in the figure above that there is still a GATE! I'll track down where it's coming from... Perhaps some place I forgot to fix a name.

I seem to be just crazy and accidently forgot which one was the camera name :) I'll fix it in the master.

@watson is it correct that the camera is called CHEC? or has it be renamed GCTCam or something?

Yes the camera is called CHEC :)


use pytest for integration tests

Per https://github.com/DavidBuchanan314/millipds/issues/16 TODO use testing framework (pytest)

Thank you for the contribution, this is looking really clean!


[fix][connector-v2][connector-assert] Optimize Assert Sink verification method

Purpose of this pull request
When there are multiple AssertSinkWriters, some Sinks will run to completion first and enter the close method. You need to let it wait for other Sinks to complete, otherwise it will make wrong judgments.
Does this PR introduce any user-facing change?

How was this patch tested?

Check list

[ ] If any new Jar binary package adding in your PR, please add License Notice according
New License Guide
[ ] If necessary, please update the documentation to describe the new feature. https://github.com/apache/seatunnel/tree/dev/docs
[ ] If you are contributing the connector code, please check that the following files are updated:

Update plugin-mapping.properties and add new connector information in it
Update the pom file of seatunnel-dist
Add ci label in label-scope-conf
Add e2e testcase in seatunnel-e2e
Update connector plugin_config

[ ] Update the release-note.

@Hisoka-X  PTAL.


Layout?

Going through examples, it is not quite clear how to handle layout. I want something like hbox and vbox. Should this be implemented using css?? Or is there some kind of tag in material-ui, that I can use for my purpose?
Regards.

I'm having the same issue as well. Not able to use CSS either because a lot of the components here have unnamed divs making it very difficult to style and position.

@nripendra You should be able to use any css grid framework with this library. Please see #190 for some suggestions.

I suggest providing two or three example layouts maybe even using different grid frameworks (to clarify that there is no one single recommended grid framework). These examples would probably help material-ui newbies like myself to get started quickly.


Add gpg to required apt packages

I think gpg is one of the packages "needed to use the Kubernetes apt repository".

@vladislav-sharapov Thanks you for your contribution.
Could you please sign the CLA before the PR can be reviewed.
You can follow the steps documented here: CLA Steps

@dipesh-rawat
Sorry, I didn't know that I have to provide my mailing address and city.


Add alt-hack glyphs directory download archive as Github release

Not necessary, the entire repository can be downloaded with https://github.com/source-foundry/alt-hack/archive/master.zip and includes minimal documentation + license beyond the glyphs directory itself.  Closing


Jaeger ui suggestion

I have used jaeger-ui for a while, and then I found some details that can be improved during use.
1.search ui's find trace button can add a dark color so that you can see it at a glance

It is best to add a search function to the "dependenices" page.

The service name in the "dependenices" page is best not to be placed outside the circle, it is best to put it inside the circle.

The number of self-calls in the "dependenices" page I think can be displayed without

I want to work on the first issue.

@wuyupengwoaini UI suggestion might better go to https://github.com/jaegertracing/jaeger-ui/issues.

@guanw  ok,I'll close this issue,and open in jaeger-ui


npm start support all locale

Have you read the Contributing Guidelines on issues?

[X] I have read the Contributing Guidelines on issues.

Description
When working at a multilingual docusaurus project, I always switch between npm start and npm start --locale zh-cn.
Could the user just run npm start and let localeDropdown works normally?
Has this been requested on Canny?
No
Motivation
Currently,  npm start doesn't work for multi language site. npm run is not a full-version preview.
Could the user just run npm start and let localeDropdown works normally?
API design
No response
Have you tried building it?
No response
Self-service

[ ] I'd be willing to contribute this feature to Docusaurus myself.

This is a technical limitation. We use Webpack dev server, which only supports one Webpack process per port. I don't have a decisive answer about whether it's possible or not, but I can't think of a possible way to do this.

In order to support this, we need to support:

Simultaneously running two SPAs on one port
Namespacing the generated files by locale (currently only one set of generated files are output, which is why the build cannot run in parallel either)
Possibly other infra changes around paralleling build processes?

I highly doubt its feasibility and ROI.

Closing because of lack of response and no defense against my challenges

Did I get right, that it is not possible to localize page in different languages and turn between them while working? If so, how does https://docusaurus.io/ work?

@VitaliiKuzennyi Each locale is an individual SPA, so in development, you can only start one SPA. During production, we will build all locales one-by-one, and essentially deploy N SPAs where N is the number of locales. When you use the locale dropdown, you are switching between those SPAs, each of them being pretty much ignorant about the state of the other.

If it's important for you to preview both locales at the same time, I suggest you use yarn start for your primary locale, and yarn start --port 3001 --locale zh-Hans for your second locale. You won't get to use the locale dropdown, but at least you can compare them side-by-side.

@Josh-Cena Thanks for your answer. It`s clear.

If it's important for you to preview both locales at the same time, I suggest you use yarn start for your primary locale, and yarn start --port 3001 --locale zh-Hans for your second locale. You won't get to use the locale dropdown, but at least you can compare them side-by-side.
Update: both locales will try to write generated files to the same directory, so if you are starting two locales in parallel, you have to change the generated directory of one locale, for example: cross-env DOCUSAURUS_GENERATED_FILES_DIR_NAME=.docusaurus/zh-Hans yarn start --locale zh-Hans --port 3001
Hi, @Josh-Cena
Regarding to your update. Is there some documentation about using cross-env. Did I get it right, this can resolve problem of starting project with two localisations available?

cross-env is an npm package. In practice, if you are using Unix, you may not install it. I'm only adding this because setting environment variables on Windows is tricky. The main idea is you need to set the DOCUSAURUS_GENERATED_FILES_DIR environment variable.


[INTEL MKL] In BUILD file fixed missing copts

The -DINTEL_MKL compiler option was not getting passed to mkl related eager files
removed in a prior commit.
Added tf_copts to the build, tf_copts includes -DINTEL_MKL.

Bazel is deprecating "nocopts" this was removed by bazel team because of that.
So adding it back wont help, and will break with bazel 1.0

Hi @gunan @penpornk  This is duplicate of the PR https://github.com/tensorflow/tensorflow/pull/32317  submitted from Intel.  This one is not from us. Please close this one.


feat: working gestures

This add most touch gestures for canvas.
touch:pinch is now emitting wheel event as it seems to be happening in browser on mobile devices
In a sense it is a work in progress there might still be some corner cases, but for the most part it seems to be working.
One thing is not "figured out" yet. @nativescript-community/gesturehander requires an install method to be called for gestures to work correctly. Maybe we could do that in the require('@nativescript/canvas-polyfill'); ?
It needs to be done before the page is created.

Thanks I implemented it here


Make use of global variables

The parts that populate Attributes and Entity Categories are called when every SP is loading.
Instead of loading those values from disc, make use of global variables.
That will make the Tolkit faster and more reliable.

Fixed with Pull Request #75


Support patch directives in pod/container overrides

What does this PR do?
Adds support for Kubernetes strategic merge patch directives. This allows deleting/overwriting fields that are not settable otherwise.
For example, if the default pod securityContext is configured to be
config:
  workspace:
    podSecurityContext:
      fsGroup: 2000
      runAsGroup: 3000
      runAsUser: 1000

setting the pod-overrides attribute to be
      pod-overrides:
        spec:
          securityContext:
            runAsUser: 1001

will result in the pod using the securityContext
securityContext:
    fsGroup: 2000
    runAsGroup: 3000
    runAsUser: 1001

whereas setting it to be
      pod-overrides:
        spec:
          securityContext:
            runAsUser: 1001
            $patch: replace

will result in the securityContext
securityContext:
    runAsUser: 1001

To do this, we have to apply the raw yaml specified in the overrides field as the patch rather than deserializing it, since Go will drop unrecognized fields in the struct when deserializing.
What issues does this PR fix or reference?
Closes https://github.com/devfile/devworkspace-operator/issues/966
Is it tested? How?
Test by using directives in pod/container overrides.
PR Checklist

[ ] E2E tests pass (when PR is ready, comment /test v8-devworkspace-operator-e2e, v8-che-happy-path to trigger)

[ ] v8-devworkspace-operator-e2e: DevWorkspace e2e test
[ ] v8-che-happy-path: Happy path for verification integration with Che

I still need to do some manual testing, but the code changes look good to me.
It might be worth linking https://github.com/kubernetes/community/blob/master/contributors/devel/sig-api-machinery/strategic-merge-patch.md?rgh-link-date=2022-11-03T17%3A21%3A38Z#basic-patch-format in the additional documentation for pod/container overrides.
Maybe something as simple as:

...The value of the attribute is applied via Kubernetes strategic merge to patch the default configuration according to predefined merge rules.


feat: build manifests; CI check

this adds a subcommand to generate the CRD manifests:
$ cargo run -- --help
    Finished dev [unoptimized + debuginfo] target(s) in 0.06s
     Running `target/debug/sinker --help`
Command-line arguments used to configure an admin server

Usage: sinker [OPTIONS] <COMMAND>

Commands:
  manifests  Generates k8s manifests
  help       Print this message or the help of the given subcommand(s)

Options:
      --log-level <LOG_LEVEL>         The tracing filter used for logs [env: SINKER_LOG=] [default: sinker=info,warn]
      --log-format <LOG_FORMAT>       The logging format [default: plain]
      --cluster <CLUSTER>             The name of the kubeconfig cluster to use
      --context <CONTEXT>             The name of the kubeconfig context to use
      --user <USER>                   The name of the kubeconfig user to use
      --kubeconfig <KUBECONFIG>       The path to the kubeconfig file to use
      --as <IMPERSONATE_USER>         Username to impersonate for Kubernetes operations
      --as-group <IMPERSONATE_GROUP>  Group to impersonate for Kubernetes operations
      --admin-addr <ADMIN_ADDR>       The admin server's address [default: <IP_ADDRESS>:8080]
  -h, --help                          Print help
  -V, --version                       Print version

When run it will write the manifest to manifests/crd.yml.
I also checked in the current one and added a job to the github actions workflow to verify that no changes to the CRD were introduced in a PR without committing them. I wasn't able to test this.

please rebase

merging; I'll fix the CI


Route specific scroll configuration

Hi,
Because the history prop is passed to the React Router and not to a Route, I'm assuming this is not possible to have this route use simpleScroll (ex: shop listing view) and that route use scrollToTop (ex: product detail view).
Would you have any recommendations to accomplish that?
Thanks.

Right now? No - that possibility is precluded by the current API.
That doesn't mean we won't support it - it just means we have to change the API.

Okay wanted to make sure.
Well I will be very interested if it ends up in a future release : ).
Closing this issue.

Let's leave this open for now - there are broader issues related to the current API, and this issue is as good as any.

Hi, is there a workaround to get this working for now?

Not really. The current implementation doesn't know about routes at all. Maybe it'd have to be some event-emitter-y thing but you'd have to write a fair bit of code.

Correct me @taion if I'm wrong.
You can register event listeners on your own app's history object. This is what this repo actually does, each scroll rule in the readme has a different listen handler. You can still do the same yourself and add specific patches depending on your needs while there's no better solution.
Here's a snippet:
const history = createBrowserHistory();

history.listenBefore(function() {
  // Here you have the window.location before the route changes. You can save it into a global var, the scroll position shouldn't be changed at that point (assumption). It's called before history.listen.
});

// Nothing fancy here, it's what useSimpleScroll does.
history.listen(function(newLocation) {
  // Don't scroll if it's a pop event (ex: browser back button)
  if (newLocation.action === 'POP') {
    return;
  }

  // Otherwise, scroll to the top after a few milliseconds.
  setTimeout(() => { window.scrollTo(0, 0); });
});

You can also save the scroll position in your application before you change routes, put it into a store (flux store, session storage, ...) and restore it when you come back to the same route. Still not the best or cleanest solution but that can work.

I was thinking of emitting an event from the scroll behavior and letting subscribers call preventDefault or something on it.

Thanks @florrain, very helpful!

For now, use shouldUpdateScroll to customize scroll behavior.


Set server location

I put the wrong address for my server location in the client and it had to go through 10 attempts before resetting to the default settings. It would be great if there was a button next to 'Close Application' that would reset to the default settings straight away.

Recommended Solution: duplicate the button at the bottom in index.html, change the text to "Use Default Values", and trigger the same code as what happens when reloadProfile's loadProfileCount is over 10.


Swift 4.x (x < 2) names are obsoleted in 4.2, not 5.

Pulls in changes from #16468 into swift-4.2-branch-04-30-2018.

@swift-ci test

@swift-ci Please test

Build failed
Swift Test Linux Platform
Git Sha - e8de4ca55d53f2db3bdd577f6a0aff246960318f


Update dd-trace-api, dd-trace-ot to 1.10.1

About this PR
📦 Updates

com.datadoghq:dd-trace-api
com.datadoghq:dd-trace-ot

from 1.7.0 to 1.10.1
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.datadoghq" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "com.datadoghq" }
}]

labels: library-update, early-semver-minor, semver-spec-minor, commit-count:1

Superseded by #756.


Misc lemming fixes

new operator version
expose more services by default
test coverage

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

27 of 27 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.9%) to 63.097%

Totals

Change from base Build<PHONE_NUMBER>:
0.9%

Covered Lines:
2893

Relevant Lines:
4585

💛  - Coveralls

This will fail the presubmit because it will pull version 1 instead of 2 of the operator, this is known issue with the presubmit so I will ignore it. Did you test this locally to confirm?

yup, it's working for me and in our presubmit


Linux documentation

I have just done this for a Linux VM, and the only change I noticed was passing -Linux to Set-AzureRmVMOSDisk instead of -Windows.  Would be nice to update the documentation to reflect this.

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

ID: 7eed234f-9a8d-4c1b-2368-fe4c8fbe8299
Version Independent ID: 876980d5-e42c-b070-c0a6-73ed3f2c91d1
Content: Change a VMs availability set
Content Source: articles/virtual-machines/windows/change-availability-set.md
Service: virtual-machines-windows
GitHub Login: @zr-msft
Microsoft Alias: zarhoads

Thanks for the feedback! We are currently investigating and will update you shortly.

@zr-msft Can you please update the doc as needed with the information on changing the availability sets for Linux VMs. Thanks :)

cc @cynthn

So we discovered only later that this scripts leaves a few things out which are quite important:

Tags are lost
Extensions are lost
Auto-shutdown settings are lost
Most importantly, the license type is lost.  This can be a costly oversight, as our machines were using bring-your-own licensing, and with this script, switched back to included license.  I believe it would be an easty change to include at least this setting in the script.

@MicahMcKittrick-MSFT or @Karishma-Tiwari-MSFT can you reassign this to me? I have a backlog work item to create a Linux version of this topic, I just haven't had time to create it yet. Thanks!

#please-close @lonevvolf Thank you for the feedback! I'm going to close this issue for now. I have a work item to create Linux specific docs in this space. Thanks again!

MARKETPLACE ERROR - I am trying to move a Marketplace created VM, but getting the below error. What is the script missing?
PS /home/jonathan>     New-AzVM `

-ResourceGroupName $resourceGroup    -Location $originalVM.Location
-VM $newVM `
-DisableBginfoExtension
WARNING: Since the VM is created using premium storage or managed disk, existing standard storage account, hubwenetstoragesa, is used for boot diagnostics.
New-AzVM: Long running operation failed with status 'Failed'. Additional Info:'Creating a virtual machine from Marketplace image requires Plan information in the request. VM: '/subscriptions/5f9f4b8d-78ca-4eb7-9f37-f5fc59d026aa/resourceGroups/HALIT-VDC-HUB-NET-WE/providers/Microsoft.Compute/virtualMachines/azuhalitvdchubfw2we'.'
ErrorCode: VMMarketplaceInvalidInput
ErrorMessage: Creating a virtual machine from Marketplace image requires Plan information in the request. VM: '/subscriptions/5f9f4b8d-78ca-4eb7-9f37-f5fc59d026aa/resourceGroups/HALIT-VDC-HUB-NET-WE/providers/Microsoft.Compute/virtualMachines/azuhalitvdchubfw2we'.
ErrorTarget:
StartTime: 3/19/2020 11:24:22 AM
EndTime: 3/19/2020 11:24:24 AM
OperationID: bd9d154c-a23c-4af2-98ce-2d6d639edd67
Status: Failed


[FEATURE] Add watcher for variable changes

Description of the requested feature
I want to be able to watch a variable for a deflisten and be able to update another variable. The example I'm thinking is when playerctl catches a track change, I want to do an
eww update revealSpotify=${revealSpotify ? false : true}
I think this has the potential to be useful in other use cases
Proposed configuration syntax
I'm thinking something along the lines of
# capture the changes of tracks
(deflisten music :initial "" "playerctl --follow metadata --format '{{ artist }} - {{ title }}' || true")

# monitor the listen to perform the command on state change
(defwatcher name :watch music  :initial "false" "eww update reveal=${reveal ? false : true}")

Additional context
I'm using this to learn a bit of Rust and I'm happy to contribute - however, if you don't think its useful or have something in the pipeline that is going to fulfil this then I should probably look at something else.

I'm wondering if I've over-thought this - maybe the answer here is much simpler and add an onChange to defListen
(deflisten music
  :initial ""
  :onChange "eww update revealSpotify=true && sleep 5 && eww update revealSpotify=false"
"playerctl --follow metadata --format '{{ artist }} - {{ title }}' || true")

Withdrawing as per contents of #356


Added new Color CLEAR_WHITE

When you are tinting a texture, you may want to lerp from white to completely transparent. Unfortunately, if you use Color.CLEAR, it will also darken the image as it turns transparent. That's because Color.CLEAR is defined as (0, 0, 0, 0). That has its uses, but in this case Color.CLEAR_WHITE is a better option. It's defined as (1, 1, 1, 0). The texture will not be darkened if users implement this new Color. This change will not impact any existing code.

That's a good catch and I think it should be added to reset() for consistency. Thank you so much!

I'll make a mental note to make a wiki article on colors. That would make for a good subject. Muchas gracias.


Update the max_slice setting name to max_slice_count

Description
Changing the name of the setting to add _count suffix
Related Issues
Follow-Up of https://github.com/opensearch-project/OpenSearch/pull/9107
Check List

[ ] New functionality includes testing.

[ ] All tests pass

[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[X] Commits are signed per the DCO using --signoff
[] Commit changes are listed out in CHANGELOG.md file (See: Changelog)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@andrross This is the follow-up PR to change the setting name.


Backend search: Use DBAL-Query Builder instead of raw queries + add events

1. Why is this change necessary?
Backend search right now is quite hit or miss and by its design can't be used to filter by custom fields (without hooking the controller itself), like the customer number that is used in your ERP and synced between shopware and your external system. By adding events to both the fields that are used to filter each article/customer/order this is now possible.
The other commit of this PR is prerequisite to those events as orders and customers use raw queries and are therefore not accessible in a structured, OOP way required for using those events efficiently.
2. What does this change do, exactly?

commit: use dbal query instead of raw queries
commit: add event for searchterm manipulation and to modify the whole query builder object just before it will be executed

3. Describe each step to reproduce the issue or behaviour.
4. Please link to the relevant issues (if any).
5. Which documentation changes (if any) need to be made because of this PR?
Using shopware.model.search_builder introduces weights to each parameter and therefore might change the order of the results. This should improve the search results as more relevant fields get preferred, but using events it is easily tweakable to your own needs if not sufficient.
6. Checklist

[ ] I have written tests and verified that they fail without my change
[x] I have squashed any insignificant commits
[ ] This change has comments for package types, values, functions, and non-obvious lines of code
[x] I have read the contribution requirements and fulfil them.

Hey @pascalheidman-bedarf,
unfortunately your PR is changing code, that is not used in Shopware 5.5 anymore.
We will add a deprecation message and those methods will be removed in one of the next minor releases.
Instead you should have a look at our GlobalSearch service ("shopware.backend.global_search").


Build with webpack

Hello,
Has anyone succeeded building NSFW.js with Webpack, that would be able to provide me with a working config?
Unfortunately, when building I get some warnings, which I'm not sure whether I can fix or not  (no errors I get), but then, when I run "node index.min.js", I get a huge output which is a partial minified JS, and then the following error:

*/var n=Object.getOwnPropertySymbols,i=Object.prototype.hasOwnProperty,o=Object.prototype.propertyIsEnumerable;function a(e){if(null==e)throw new TypeError("Object.assign cannot be called with null or undefined");return Object(e)}e.exports=function(){try{if(!Object.assign)return!1;var e=new String("abc");if(e[5]="de","5"===Object.getOwnPropertyNames(e)[0])return!1;for(var t={},r=0;r<10;r++)t["_"+String.fromCharCode(r)]=r;if("0123456789"!==Object.getOwnPropertyNames(t)
(there's a lot more code, but I truncated it for this issue)
Error: package.json does not exist at F:\package.json
at Object.t.find (F:\path\to\proj\build\index.min.js:169:11682)
at Object. (F:\path\to\proj\build\index.min.js:472:426)
at Object. (F:\path\to\proj\build\index.min.js:472:916)
at r (F:\path\to\proj\build\index.min.js:1:110)
at Object. (F:\path\to\proj\build\index.min.js:289:44677)
at r (F:\path\to\proj\build\index.min.js:1:110)
at F:\path\to\proj\build\index.min.js:1:902
at Object. (F:\path\to\proj\build\index.min.js:1:913)
at Module._compile (internal/modules/cjs/loader.js:1151:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1171:10)

I can't understand why a production build is looking for "package.json" in the root of the F:\ drive.
My webpack config:
module.exports = [
	{
		name: 'server',
		context: __dirname,
		entry: './index.js',
		target: 'node',
		mode: 'production',
		output: {
			path: path.resolve(__dirname, 'build'),
			filename: 'index.min.js',
		},
		module: {
			rules : [
			{
				test: /\.js$/,
				exclude: /node_modules/,
				use: ['babel-loader'],
			},
			]
		},
		resolve: {
			modules: [
				path.join(__dirname, "node_modules"),
			]
		},
		node: {
			fs: 'empty', // Module not found: Error: Can't resolve 'fs'
			child_process: 'empty', // Module not found: Error: Can't resolve 'child_process'
		},
		plugins: [],
	}
];

helpful/not helpful
NSFWJS.com is webpack under the create react app config.
I know that's like throwing a phone book at someone, but it proves it is possible.

@ghnp5 let us know if you're still having this problem, in the mean time we're closing this issue. Thanks!


Naming Conflict -- DatabaseSeeder

Can you rename your DatabaseSeeder class? It has no namespace defined and by default, the app/database/seeds/DatabaseSeeder class also has no namespace which causes conflict.

+1!

Fixed in b572ab6b4f952f0a963c4ce086540d98e04cdefe.


Where to place Message-config file for all applications in advanced template?

Trying to insert translations from all applications (console, frontend, backend) into database
currently my config look like this and located in one of applications
https://gist.github.com/anonymous/872c18a83f86b2bce5bd
Where to place message-config file if I want to insert messages into database for all applications in advanced template?

The location of the config does not matter. What matters is sourcePath. If you'll specify it as root of your project, message command will check all apps.

Ok let's say I place message-config in root directory, first problem - it will include vendor directory also to scanning process. Second, where will it get the $db configuration if the file will be in the root directory?

Add vendor to except section. It will always get config from console since it's run from console.

Thank you very much!


⚠ Spryr has degraded performance

In c52d837, Spryr (https://spryr.com) experienced degraded performance:

HTTP code: 200
Response time: 7923 ms

Resolved: Spryr performance has improved in da10f70 after 34 minutes.


Virtual Machines

Thanks for a great resources. Please Check Virtual Machines section there is Deploy used 2 times.

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

ID: 510808e8-db5d-6b07-9a04-6edb743a2dfc
Version Independent ID: 20d098aa-ef31-cb26-d677-765cfc9a7164
Content: Choosing an Azure compute service - Azure Architecture Center
Content Source: docs/guide/technology-choices/compute-decision-tree.md
Service: architecture-center
Sub-service: reference-architecture
GitHub Login: @MikeWasson
Microsoft Alias: pnp

Thanks for reporting - this issue is under review.  This is a Microsoft Internal DevOps Bug ID AB#

@Jurisnakib PR has been created for this which will address this. Thanks so much for providing the feedback that help us in improving the documentation. For now I will proceed with closure of this and If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


[KOGITO-4833] Make REST generation optional

https://issues.redhat.com/browse/KOGITO-4833
Details:

Introduced RestAnnotator and moved there REST specific codegen methods extracted from DependencyInjectionAnnotator
Updated all REST generation to use REST_TYPE
Introduced kogito.generate.rest and kogito.generate.di to disable REST/DI generation
Updated IncrementalRuleCodegenTest, ApplicationGeneratorTest and PredictionCodegenTest to use ParameterizedTest and test all the context (Quarkus, Spring and Java)
Removed Springboot disabled codegen tests (KOGITO-4000)
Migrated codegen integration tests that required REST dependencies to compile: they were just compiling and then using reflection to make some assertions, now they are inside process codegen module with the same assertions but directly on generated source code
Removed REST/Spring dependencies from codegen integration tests: now it generates and compiles only no DI classes
Removed Spring dependencies from kogito-build-parent
Created spring and quarkus -norest integration test to make sure this new scenario is properly covered

PR list:

https://github.com/kiegroup/kogito-runtimes/pull/1185
https://github.com/kiegroup/kogito-apps/pull/735

Jenkins run native

The Native check has failed. Please check the logs.

The Linux check has failed. Please check the logs.

Jenkins run native

The Linux check has failed. Please check the logs.

jenkins retest this please

The Linux check has failed. Please check the logs.

The Native check has failed. Please check the logs.

jenkins retest this please

The Linux check is successful.

The Linux check is successful.

The Linux check is successful.


How do you write to the default stream in the EU region?

I'm trying to write to the _default stream (from Cloud Functions), as mentioned in various source files.
But it's not working. I keep getting the error that the table does not exist, while it does. Also tried generating the table in the US region, but that results in the same error. But I need it for the EU region.
Simple proto file (simple_table_record.proto)
// The BigQuery Storage API expects protocol buffer data to be encoded in the
// proto2 wire format. This allows it to disambiguate missing optional fields
// from default values without the need for wrapper types.
syntax = "proto2";

// Define a message type representing the rows in your table. The message
// cannot contain fields which are not present in the table.
message SimpleTableRecord {
  required string name = 1;
}

I've generated the associated js file using grpc_tools_node_protoc --js_out=import_style=commonjs,binary:. simple_table_record.proto.
The test script (typescript)
import { BigQueryWriteClient, protos } from '@google-cloud/bigquery-storage'
import { getProjectId } from '../../utils'
import { logger } from 'firebase-functions/v1'
import { v4 } from 'uuid'
import * as rec from './proto/simple_table_record_pb'

import FieldDescriptorProto = protos.google.protobuf.FieldDescriptorProto
import Storage = protos.google.cloud.bigquery.storage.v1

export async function writeDefaultStreamTest(
  projectId = getProjectId(),
  datasetId = 'firebase_export',
  tableId = 'simple_table',
) {
  return new Promise(async (resolve, reject) => {
    try {
      const writeClient = new BigQueryWriteClient()

      const parent = `projects/${projectId}/datasets/${datasetId}/tables/${tableId}/streams/_default`
      const [writeStream] = await writeClient.createWriteStream({
        parent,
        writeStream: { type: Storage.WriteStream.Type.COMMITTED },
      })

      logger.log(`Stream created: ${writeStream.name}`)

      const stream = writeClient.appendRows({
        otherArgs: {
          headers: {
            'x-goog-request-params': `write_stream=${writeStream.name}&parent=${parent}`,
          }
        }
      })

      const serializedRows: any[] = []
      const row = new (rec as any).SimpleTableRecord()
      row.row_num = 1
      row.setName(v4())
      serializedRows.push(row.serializeBinary())

      stream.on('data', response => logger.log(response))
      stream.on('error', err => {
        logger.error(err)
        reject(err)
      })
      stream.on('end', () => {
        logger.log('!!!END!!!')
        resolve(null)
      })

      stream.write({
        writeStream: writeStream.name,
        protoRows: {
          writerSchema: {
            protoDescriptor: {
              name: 'SimpleTableRecord',
              field: [{
                name: 'name',
                number: 1,
                type: FieldDescriptorProto.Type.TYPE_STRING,
              }]
            }
          },
          rows: { serializedRows },
        },
      }, undefined, (err) => {
        logger.error(err)
        reject(err)
      })
    } catch (err) {
      logger.error(err)
      reject(err)
    }
  })
}

When run, it throws the following error:
Error: 3 INVALID_ARGUMENT: Invalid table name. Entity: projects/<project-name>/datasets/firebase_export/tables/simple_table/streams/_default
    at Object.callErrorFromStatus (/workspace/node_modules/@grpc/grpc-js/src/call.ts:81:24)
    at Object.onReceiveStatus (/workspace/node_modules/@grpc/grpc-js/src/client.ts:343:36)
    at Object.onReceiveStatus (/workspace/node_modules/@grpc/grpc-js/src/client-interceptors.ts:462:34)
    at Object.onReceiveStatus (/workspace/node_modules/@grpc/grpc-js/src/client-interceptors.ts:424:48)
    at /workspace/node_modules/@grpc/grpc-js/src/call-stream.ts:330:24
    at processTicksAndRejections (internal/process/task_queues.js:77:11) {
  code: 3,
  details: 'Invalid table name. Entity: projects/<project-name>/datasets/firebase_export/tables/simple_table/streams/_default',
  metadata: Metadata { internalRepr: Map(0) {}, options: {} },
  note: 'Exception occurred in retry method that was not classified as transient'
}

The BigQuery table schema:
{
  name: string (nullable)
}

So I got it working by not calling "createWriteStream", and making the following changes:
const parent = `projects/${projectId}/datasets/${datasetId}/tables/${tableId}`
const writeStreamName = `projects/${projectId}/datasets/${datasetId}/tables/${tableId}/streams/_default`
// const [writeStream] = await writeClient.createWriteStream({
//   parent,
//   writeStream: { type: Storage.WriteStream.Type.COMMITTED },
// })

const stream = writeClient.appendRows({
    otherArgs: {
        headers: {
        'x-goog-request-params': `write_stream=${writeStreamName}&parent=${parent}`,
        }
    }
})

You can turn this issue into a feature request for better docs. They are incomplete and pretty vague.

@larssn This is demonstrated in the code samples:

https://github.com/googleapis/nodejs-bigquery-storage/blob/fb8acf1f4eab7823132159bcf5927c9eda6374e2/samples/append_rows_pending.js#L84
https://github.com/googleapis/nodejs-bigquery-storage/blob/fb8acf1f4eab7823132159bcf5927c9eda6374e2/samples/append_rows_proto2.js#L147

Is there another location in the docs you were referencing where this is not present?

@steffnay Thanks for stopping by!
But writing to the default stream is never demonstrated, and the existing samples seems to have come from the python samples, which is better than nothing. I just wish there were some dedicated samples; more explanatory, maybe in typescript, to get the point across. 🙂
Another thing I've run into that I haven't been able to solve yet, is writing a protoDescriptor for nested fields (record/struct).
Here's what I go so far, but it's not accepted by grcp:
   stream.write({
      writeStream: writeStreamPath,
      protoRows: {
        writerSchema: {
          protoDescriptor: {
            name: 'SimpleTableRecord',
            field: [
              {
                name: 'record',
                number: 1,
                label: FieldDescriptorProto.Label.LABEL_OPTIONAL,
                type: FieldDescriptorProto.Type.TYPE_MESSAGE,
                type_name: 'SimpleTableRecord.SampleStruct', // Also tried just 'SampleStruct'.
                field: [
                  {
                    number: 1,
                    name: 'name',
                    label: FieldDescriptorProto.Label.LABEL_OPTIONAL,
                    type: FieldDescriptorProto.Type.TYPE_STRING,
                  },
                  {
                    number: 2,
                    name: 'value',
                    label: FieldDescriptorProto.Label.LABEL_OPTIONAL,
                    type: FieldDescriptorProto.Type.TYPE_STRING,
                  }
                ],
              },
            ]
          }
        },
        rows: { serializedRows },
      },
    })

With this being the proto file:
message SimpleTableRecord {
  message SampleStruct {
    optional string name = 1;
    optional string value = 2;
  }

  optional SampleStruct record = 1;
}

Thanks for reading

@larssn Hello, have you solved the issue about nested message type  in .proto file and the way of declaring proto descriptors ?

@ben790924 Sadly no. I've looked all over for where protoDescriptor is parsed, without any luck.
Let me know if you find it

Thanks for your information。
BTW, I found this project written in Go. What's the difference is it declares message outside of main message in a .proto file. So you can jsut declare descriptor as JS objects does。(I have not tested it in JS yet, but hope this helps)
Go Proto Example


🐛 Bug Report: GitHub Actions Plugin status field does not sort for completed items

📜 Description
When sorting the plugin by status, the sub statuses that roll up to completed are not actually sorted.  Pressing the sort button leaves them in the same order.
👍 Expected behavior
Items within the completed status should be sorted alphabetically based on the conclusion (e.g. Aborted, Timed Out, Error, etc)
👎 Actual Behavior with Screenshots
Pressing the Status header keeps the items in the same order even when sorting ascending or descending.

👟 Reproduction steps

Load Backstage
Click the Catalog
Click a component that has workflow runs on GitHub Actions
Click the CI/CD plugin
Click the STATUS header to sort
Click the STATUS header to sort again

📃 Provide the context for the Bug.
Users are unable to sort similar items together for review.  The status column is also not included in the filter meaning the only way to find them is to page through the results.
🖥 Your Environment
Latest version of Chrome with Backstage 1.16.x
👀 Have you spent some time to check if this bug has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Are you willing to submit PR?
None

Just wanted to note you can reproduce this here: https://demo.backstage.io/catalog/default/component/backstage-demo/ci-cd
Also, my experience when using a render like this is that you need to provide your own sort logic:
https://github.com/backstage/backstage/blob/419e4ffaafa9db58f6b66308a5e156dbaed0c04c/plugins/github-actions/src/components/WorkflowRunsTable/WorkflowRunsTable.tsx#L88C5-L92C7


add get_feature_names_out to MinHashEncoder

We generate feature names as feature_name_1_0, ... feature_name_1_n_components etc. If feature names are missing, we use x_0, x_1 etc
(+ a test to check that the MinHashEncoder is deterministic)

Thanks for the comments @Vincent-Maladiere !


Long response time when exception is thrown

There are 3 layers in the application.

Api
Application
Infrastructure

Test 1
An application level exception is thrown.
here are the codes
Api
 public async Task<IActionResult> Get()
 {
     await _app.Handler();
 }

Application
 public async Task Handler()
 {
     throw new NotFoundException();
 }

 public class NotFoundException : Exception
 {
     public NotFoundException()
         : base($"Product not found.")
     {
     }
 }

Infrastructure
 public async Task Service()
 {
     return null;
 }

Here is the result
Exception thrown: 'Application.Exceptions.NotFoundException' in Application.dll
Exception thrown: 'Application.Exceptions.NotFoundException' in System.Private.CoreLib.dll
Response Time 400ms between 500ms
Test 2
An infrastructure level exception is thrown.
here are the codes
Api
public async Task<IActionResult> Get()
{
    await _app.Handler();
}

Application
public async Task Handler()
{
    return null;
}

Infrastructure
public async Task Service()
{
    throw new NotFoundException();
}

public class NotFoundException : Exception
{
    public NotFoundException()
        : base($"Product not found.")
    {
    }
}

Here is the result
Exception thrown: 'Application.Exceptions.NotFoundException' in Application.dll
Exception thrown: 'Application.Exceptions.NotFoundException' in System.Private.CoreLib.dll
Exception thrown: 'Application.Exceptions.NotFoundException' in System.Private.CoreLib.dll
Response Time 800ms between 900ms
Question
why response time increases?
is this a usual thing?

There's too little information here to know why the response time has increased. Please share your full infra.


Bugfix: v8.2.3019 End Position Support

Do not add endline if the search result is one-line.
It had got result-line and item-key-name mismatch.
For example, for the line
autoload/qfedit.vim|36 col 15-26| let items[qfedit#line(item)] = item,
it tries to find list key
autoload/qfedit.vim|36-36 col 15-26| let items[qfedit#line(item)] = item,
with end line.
It results to find the entry and clear all the vimgrep result.

Thank you.

Perhaps isn't it dangerous to remove mismatch lines?
Quickfix result is unexpectedly cleaned up wrongly, saying nothing.
If it is easy to do,
it would be more kind to leave unfound lines (only adding error mark, for example),
rather than removing silently.


Update tests for final 13.02.00 release

Need to update a few tests based on final 13.02.00 release.

Tests were updated.  Close the issue.


Variants for forename and surname

Might be better to have name variants selectable for both first and last name.

Presume this refers to option to select first/last names on soundex.

For example, name variants on Find my Past:


Sphinx extension doesn't work when run outside the project root

Michele Mattioni reported (see https://groups.google.com/forum/#!topic/sumatra-users/UFdbK5gDsJs):
"I store the image in an ad hoc file per run, however the Datastore path is store as relative, and when ran with sphinx the images and plot are not find.
The problem is that this line:
https://bitbucket.org/apdavison/sumatra/src/658cec5709a0/src/publishing/utils.py?at=default#cl-86
calls this line
https://bitbucket.org/apdavison/sumatra/src/658cec5709a0/src/datastore/filesystem.py?at=default#cl-119
which instantiate a new DataFile
(https://bitbucket.org/apdavison/sumatra/src/658cec5709a0/src/datastore/filesystem.py?at=default#cl-16)
The full path is determined combining the datastore with the path of the image.
The problem I have is that, when I ran sphinx, the image is not found because is one directory too deep.
Let me give you an example. My current structure is
project_dir
    .smt
    doc
    Results
        20130325-133206
        20130325-133234
        20130325-135536
   src

The output are stored in the Results directory, more accurately in the
subdirectories created from the timestamp. When I ran the make build
from the doc directory, the datastore has as root
"Results/20130325-133206" for example, e.g.
    print (record.datastore)
    Results/20130325-133206

and the fullpath of the DataFile is than
    self.full_path = os.path.join(store.root, path)
#Results/20130325-133206, name_of_the_plot.png

the problem is, sphinx is ran from the doc directory, therefore the
real directory of the record_store is one level up, like
../Results/20130325-133206
I'm not sure how to fix this. TBH right now I have a terrible hack in
place and this is like my get_image (in sumatra/publishing/utils)
looks like
    def get_image(record, image_path, sumatra_options, err=Exception):

        if image_path is None:
            image_key = record.output_data[0]
        else:
            image_key = None
            for key in record.output_data:
                if key.path == image_path:
                    image_key = key
                    break
            if image_key is None:
                raise ValueError("Record %s has no output data file
with path %s. Valid paths are: %s" % (
                        record.label, image_path, ", ".join(key.path
for key in record.output_data)))
        assert isinstance(image_key, DataKey)
        # check expected digest, if supplied, against key.digest
        if ('digest' in sumatra_options
            and sumatra_options['digest'] != image_key.digest):
            raise err('Digests do not match')
        record.datastore.root = os.path.join("../",
record.datastore.root) #TERRIBLE HACK!! # We need a better way
        return record.datastore.get_data_item(image_key)  # checks
key.digest against file contents

basically I overwrite the root of the datastore on the fly. But this
works only if you have a project with my same structure.
I'm not sure what is the best way to attack this."
Imported from Bitbucket issue 182,  created by apdavison on 05-30-2013 at 11:42, last modified: 04-16-2014 at 11:28

It does seem as though we need to store the absolute path for the datastore root, if we want to be able to work in subdirectories of the project root, or if we want to use the provenance data on a different machine to where it was captured. However, when accessing data stores in multiple ways (e.g. through symbolic links, NFS) it is very helpful to have the relative path (see ticket:2).
This suggests we need:

a tool to re-map the roots for (some of?) the datastores in a separate copy of a given record store ("smt migrate"?)
a tool to dynamically remap roots when accessing the same datastore through a symbolic link, NFS

Trac comment by apdavison on 05-30-2013 at 21:31


Optimizing code and adding from http to https

Can one of the admins verify this patch?

Thanks! Changes are done as per your suggestion. Can we go ahead :)

Jenkins, test this please.


Avoid running xcode-locator which can be super slow (and can fail) if the machine has many Xcode versions

This fixes the flaky CI.

@thii thanks for the PR - this seems good for now!
We have a fix for this upstream as well:   bazelbuild/bazel#14328

I should have time at best early next week to fix this upstream in Bazel ( the timeout )


gitolite.conf file being written when configuration file set to another .conf

I changed :gitolite_config_file (Gitolite configuration file) in setting.yml from gitolite.conf to redmine.conf, while I added a include "redmine.conf" directive in the former. Problem is that redmine_git_hosting will update gitolite.conf file, removing my include directive, adding some repo @all thing, thus losing track of its true conf file, everytime I change something related to repositories, be it add or remove user keys or create/delete repos.
While it does edit gitolite.conf, it also edits redmine.conf correctly, placing repos directives and its accesses.

I tried poking more with this problem I am having, and I discovered it happens even when I RAILS_ENV=production rake redmine_git_hosting:update_repositories. What this rake is actually doing is mindlessly restoring gitolite.conf to its former configuration, as it were at the moment I setup redmine_git_hosting.

Ok, I kinda fixed my problem, though the bug maybe is still there. What I did was to manually edit gitolite.conf at $REDMINE_USER/redmine/tmp/redmine_git_hosting/gitolite3/ and commit and push to origin from there, with my redmine user.


Dummy PR to test Jenkins

This is dummy PR to test of Jenkins job will be triggered

Can one of the admins verify this patch?


RHOAI 2.11 update

Updating manifests for #61. Specifically, updating workbench and pipeline runtime images as well as adding pvc for model training pipeline.

Merged into dev-rhoai-211 for integration tests.


Spectacles / Glasses

Is your feature request about our website? Please describe.
Is your feature request about the Usage? Please describe.
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.

https://remixicon.com/icon/glasses-line
https://remixicon.com/icon/glasses-2-line
https://remixicon.com/icon/goggles-line


Fix selection while text is being generated on UE4.27 & UE5.0

All text is replaced when updated and the text block is losing the selected reference causing a strange behavior on selection.

Will return with this issue in the future.


Cosmos ChangeFeedProcessor fixes

Fix to terminate the current processing threads when the lease renewal worker thread has failed.
Fix for out of bounds exception when the leases load balancer thread is trying to acquire a lease.

/azp run java - cosmos - tests


Update typing for font_sizes in image captcha

previous typing
-> tuple of one int value
now
-> tuple of int values

Welcome to Codecov :tada:
Once merged to your default branch, Codecov will compare your coverage reports and display the results in this comment.
Thanks for integrating Codecov - We've got you covered :open_umbrella:


3090 out of memory with tile_size 512

python -u inference.py --version v2 --task fr_bg --upscale 2 --cfg_scale 4.0 --input inputs/demo/bfr/whole_img --output results/demo_bfr_unaligned --device cuda --tiled --tile_size 512 --tile_stride 256
use sdp attention as default
keep default attention mode
using device cuda
[3, 3, 64, 23, 32, 4]
Setting up SDPCrossAttention (sdp). Query dim is 320, context_dim is None and using 5 heads.
Setting up SDPCrossAttention (sdp). Query dim is 320, context_dim is 1024 and using 5 heads.
Setting up SDPCrossAttention (sdp). Query dim is 320, context_dim is None and using 5 heads.
Setting up SDPCrossAttention (sdp). Query dim is 320, context_dim is 1024 and using 5 heads.
Setting up SDPCrossAttention (sdp). Query dim is 640, context_dim is None and using 10 heads.
Setting up SDPCrossAttention (sdp). Query dim is 640, context_dim is 1024 and using 10 heads.
Setting up SDPCrossAttention (sdp). Query dim is 640, context_dim is None and using 10 heads.
Setting up SDPCrossAttention (sdp). Query dim is 640, context_dim is 1024 and using 10 heads.
Setting up SDPCrossAttention (sdp). Query dim is 1280, context_dim is None and using 20 heads.
Setting up SDPCrossAttention (sdp). Query dim is 1280, context_dim is 1024 and using 20 heads.
Setting up SDPCrossAttention (sdp). Query dim is 1280, context_dim is None and using 20 heads.
Setting up SDPCrossAttention (sdp). Query dim is 1280, context_dim is 1024 and using 20 heads.
Setting up SDPCrossAttention (sdp). Query dim is 1280, context_dim is None and using 20 heads.
Setting up SDPCrossAttention (sdp). Query dim is 1280, context_dim is 1024 and using 20 heads.
Setting up SDPCrossAttention (sdp). Query dim is 1280, context_dim is None and using 20 heads.
Setting up SDPCrossAttention (sdp). Query dim is 1280, context_dim is 1024 and using 20 heads.
Setting up SDPCrossAttention (sdp). Query dim is 1280, context_dim is None and using 20 heads.
Setting up SDPCrossAttention (sdp). Query dim is 1280, context_dim is 1024 and using 20 heads.
Setting up SDPCrossAttention (sdp). Query dim is 1280, context_dim is None and using 20 heads.
Setting up SDPCrossAttention (sdp). Query dim is 1280, context_dim is 1024 and using 20 heads.
Setting up SDPCrossAttention (sdp). Query dim is 640, context_dim is None and using 10 heads.
Setting up SDPCrossAttention (sdp). Query dim is 640, context_dim is 1024 and using 10 heads.
Setting up SDPCrossAttention (sdp). Query dim is 640, context_dim is None and using 10 heads.
Setting up SDPCrossAttention (sdp). Query dim is 640, context_dim is 1024 and using 10 heads.
Setting up SDPCrossAttention (sdp). Query dim is 640, context_dim is None and using 10 heads.
Setting up SDPCrossAttention (sdp). Query dim is 640, context_dim is 1024 and using 10 heads.
Setting up SDPCrossAttention (sdp). Query dim is 320, context_dim is None and using 5 heads.
Setting up SDPCrossAttention (sdp). Query dim is 320, context_dim is 1024 and using 5 heads.
Setting up SDPCrossAttention (sdp). Query dim is 320, context_dim is None and using 5 heads.
Setting up SDPCrossAttention (sdp). Query dim is 320, context_dim is 1024 and using 5 heads.
Setting up SDPCrossAttention (sdp). Query dim is 320, context_dim is None and using 5 heads.
Setting up SDPCrossAttention (sdp). Query dim is 320, context_dim is 1024 and using 5 heads.
building SDPAttnBlock (sdp) with 512 in_channels
building SDPAttnBlock (sdp) with 512 in_channels
Setting up SDPCrossAttention (sdp). Query dim is 320, context_dim is None and using 5 heads.
Setting up SDPCrossAttention (sdp). Query dim is 320, context_dim is 1024 and using 5 heads.
Setting up SDPCrossAttention (sdp). Query dim is 320, context_dim is None and using 5 heads.
Setting up SDPCrossAttention (sdp). Query dim is 320, context_dim is 1024 and using 5 heads.
Setting up SDPCrossAttention (sdp). Query dim is 640, context_dim is None and using 10 heads.
Setting up SDPCrossAttention (sdp). Query dim is 640, context_dim is 1024 and using 10 heads.
Setting up SDPCrossAttention (sdp). Query dim is 640, context_dim is None and using 10 heads.
Setting up SDPCrossAttention (sdp). Query dim is 640, context_dim is 1024 and using 10 heads.
Setting up SDPCrossAttention (sdp). Query dim is 1280, context_dim is None and using 20 heads.
Setting up SDPCrossAttention (sdp). Query dim is 1280, context_dim is 1024 and using 20 heads.
Setting up SDPCrossAttention (sdp). Query dim is 1280, context_dim is None and using 20 heads.
Setting up SDPCrossAttention (sdp). Query dim is 1280, context_dim is 1024 and using 20 heads.
Setting up SDPCrossAttention (sdp). Query dim is 1280, context_dim is None and using 20 heads.
Setting up SDPCrossAttention (sdp). Query dim is 1280, context_dim is 1024 and using 20 heads.
strictly load pretrained sd_v2.1, unused weights: {'posterior_variance', 'log_one_minus_alphas_cumprod', 'sqrt_one_minus_alphas_cumprod', 'sqrt_recipm1_alphas_cumprod', 'model_ema.decay', 'posterior_log_variance_clipped', 'posterior_mean_coef2', 'alphas_cumprod_prev', 'alphas_cumprod', 'model_ema.num_updates', 'sqrt_alphas_cumprod', 'sqrt_recip_alphas_cumprod', 'betas', 'posterior_mean_coef1'}
strictly load controlnet weight
/usr/local/lib/python3.10/dist-packages/torchvision/models/_utils.py:208: UserWarning: The parameter 'pretrained' is deprecated since 0.13 and may be removed in the future, please use 'weights' instead.
warnings.warn(
/usr/local/lib/python3.10/dist-packages/torchvision/models/_utils.py:223: UserWarning: Arguments other than a weight enum or None for 'weights' are deprecated since 0.13 and may be removed in the future. The current behavior is equivalent to passing weights=None.
warnings.warn(msg)
load lq: inputs/demo/bfr/whole_img/00794.png
detect 1 faces
Spaced Sampler: 100%|███████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████| 50/50 [00:12<00:00,  4.05it/s]
Traceback (most recent call last):
File "/workspace/DiffBIR/inference.py", line 86, in
main()
File "/workspace/DiffBIR/inference.py", line 81, in main
supported_tasksargs.task.run()
File "/usr/local/lib/python3.10/dist-packages/torch/utils/_contextlib.py", line 115, in decorate_context
return func(*args, **kwargs)
File "/workspace/DiffBIR/utils/inference.py", line 147, in run
sample = self.pipeline.run(
File "/usr/local/lib/python3.10/dist-packages/torch/utils/_contextlib.py", line 115, in decorate_context
return func(*args, **kwargs)
File "/workspace/DiffBIR/utils/helpers.py", line 147, in run
clean = self.run_stage1(lq)
File "/workspace/DiffBIR/utils/helpers.py", line 176, in run_stage1
clean = self.stage1_model(lq)
File "/usr/local/lib/python3.10/dist-packages/torch/nn/modules/module.py", line 1511, in _wrapped_call_impl
return self._call_impl(*args, **kwargs)
File "/usr/local/lib/python3.10/dist-packages/torch/nn/modules/module.py", line 1520, in _call_impl
return forward_call(*args, **kwargs)
File "/workspace/DiffBIR/model/bsrnet.py", line 101, in forward
fea = self.lrelu(self.upconv2(F.interpolate(fea, scale_factor=2, mode='nearest')))
File "/usr/local/lib/python3.10/dist-packages/torch/nn/modules/module.py", line 1511, in _wrapped_call_impl
return self._call_impl(*args, **kwargs)
File "/usr/local/lib/python3.10/dist-packages/torch/nn/modules/module.py", line 1520, in _call_impl
return forward_call(*args, **kwargs)
File "/usr/local/lib/python3.10/dist-packages/torch/nn/modules/conv.py", line 460, in forward
return self._conv_forward(input, self.weight, self.bias)
File "/usr/local/lib/python3.10/dist-packages/torch/nn/modules/conv.py", line 456, in _conv_forward
return F.conv2d(input, weight, bias, self.stride,
torch.cuda.OutOfMemoryError: CUDA out of memory. Tried to allocate 7.91 GiB. GPU 0 has a total capacity of 23.68 GiB of which 6.25 GiB is free. Process 1475434 has 17.43 GiB memory in use. Of the allocated memory 16.99 GiB is allocated by PyTorch, and 131.54 MiB is reserved by PyTorch but unallocated. If reserved but unallocated memory is large try setting PYTORCH_CUDA_ALLOC_CONF=expandable_segments:True to avoid fragmentation.  See documentation for Memory Management  (https://pytorch.org/docs/stable/notes/cuda.html#environment-variables)

Sorry for replying so late. DiffBIR v2 did not perform tiling on the first stage model, which resulted in a OOM error. We have now fixed this problem in DiffBIR v2.1.


Query CAR database according to epoch

Issue summary
There are two kinds of data stores in Forest: Read-only CAR files and writeable ParityDB databases. Since all values are uniquely determined by their key, it does not matter for correctness which data store we query first. It does matter for performance, though, and we want to query as few data stores as possible.
We first query the CAR data stores in the order they were added. If a key isn't present in the CAR data stores, we then query the ParityDB database. However, in regular operation, we're significantly more likely to query new data than old data. As such, querying the data stores with the latest data first is a better option. The ParityDB database contains current data and is, therefore, the newest and should be queried first. The CAR data stores should be sorted from highest to lowest by epoch.

[x] Query ParityDB first.
[x] Sort CAR data stores by the epoch of the heaviest tipset.
[ ] (Optional) Trim unusable CAR data stores if we know we'll never access their data. This happens if we're evaluating tipset 1000, and we have CAR stores for epochs 0-1500 and 1500-3000. The second CAR store will not be used for evaluating this tipset and can be removed from the list.

Other information and links

Calling .iter() on a BinaryHeap traverses the items in arbitrary order. We want to traverse the CAR files from the highest epoch to the lowest epoch.
https://github.com/ChainSafe/forest/blob/606751433dbda1cf78fca5bf1444e22c96080490/src/db/car/many.rs#L159-L163


Remove unused member variable from test code

My mistake, apparently I needed coffee before opening this PR.


Reward Ad S2S Callback event token is incorrect

MAX Plugin Version
applovin_max: ^2.5.0
Flutter Version
Flutter 3.7.12
Device/Platform Info
Android, IOS
Current Behavior
The Applovin server sends a request with the {EVENT_TOKEN} macro is incorrect with what the document described.
The callback url of the Rewarded Ad unit in MAX:
https://myserver.com/verifyreward?event={EVENT_ID}&token={EVENT_TOKEN}&amount={AMOUNT}&user_id={USER_ID}&data={CUSTOM_DATA}
My debug log the request query parameters:
event=a46bd0fe2b866b797f7cea5babb16e2b4be968e6&token=8f0fcabd9e6e5af0b19896e367da7026198ae6bd&amount=3000.000000&user_id=yDvGtR6HXWaPMa7n0DBxSVefTpC3&data=mycustomdata
As the doc on how the callback works (https://support.applovin.com/hc/en-us/articles/4403788356749-How-Server-to-Server-Callback-Works), I calculate the sha1 hash using node as below:
const eventId = req.query.event;
const eventToken = req.query.token;

const shasum = crypto.createHash("sha1");
const eventKey = <get key from environment var>;
// I can confirm the log event key is correct match with what show in the MAX reward ad unit

const message = eventId + eventKey; // eventId get from the query parameter
shasum.update(message);
const resultToken = shasum.digest("hex");

The resultToken log is 8d36cba210a030e43e3ffa0573055aa08328999b and not match with the eventToken in the query parametter.
I have double checked my code with the result built with sha1(eventId + eventKey) on http://www.sha1-online.com/ and they generate same sha1 hash result.
I don't know what sha1 function the Applovin using to calculate the hash that cause the different or my sha1 function missing some thing.
Expected Behavior
eventToken in the query parameter match with my sha1 calculation.
How to Reproduce

Enable S2S callback, and ask support to generate event key for the account
Setup server code like above
Test with real reward ad

Additional Info
No response

@andj207 - Since we'll need your account info to debug, could you send this inquiry to https://applovin.zendesk.com/hc/en-us/requests/new?

Thank you, @thomasmso ! I have sent the inquiry as advised.

The supporter told me to use the event key under Dashboard --> Account --> Keys instead of the one under the rewarded ad unit (the two are different). It is working perfectly now.