The status message should let teams know what is pending

Story
As a user, I would like to know what is pending in the Web UI.
Description
Right now the Web UI just says "pending" when an edit request is in-flight. We would like to to say "Update Pending"
Done When
The user sees "Update Pending" in the web UI.

**Bugfix updated on the platform-registry-prod silver cluster: Jan 12, 2021

**Bugfix updated on the platform-registry-prod silver cluster: Jan 12, 2021


Mobile version support

I'd like to use it on mobile version too , but it looks like this;

I can barely click them and can't see texts.
Can you improve it for mobile version? I'm using Kiwi Browser, (Violentmonkey ext.)

Oh I didn't expect people can use a userscript on their phone. 😄
Sure, let me see how to improve the behavior here.

This is what it will look like in the next version.
But I couldn't test this on an actual phone. 🙏

Please note that mobile devices who are not supporting :has() selector will not being able to use this feature.


Fixed issue where vite couldnt find browserified http/https packages on windows systems.

As the title says.
Had to do this to get yarn start to work on windows.

in master from another branch


Run make presubmit and fix the errors

Codecov Report

Merging #681 into master will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##           master     #681   +/-   ##
=======================================
  Coverage   57.38%   57.38%
=======================================
  Files          35       35
  Lines        2485     2485
=======================================
  Hits         1426     1426
  Misses        770      770
  Partials      289      289

Impacted Files
Coverage Δ

core/mutator/entry/entry.go
78.94% <ø> (ø)
:arrow_up:

core/mapserver/mapserver.go
47.82% <ø> (ø)
:arrow_up:

core/crypto/vrf/p256/p256.go
82.25% <100%> (ø)
: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 32c9b57...85cf6f7. Read the comment docs.


Enable typescript validation with eslint and update CI build/test scripts

Changes are similar to https://github.com/RedHatInsights/hac-core-frontend/pull/13

Removed unused babel dependencies
Replaced .eslintrc.yml with .eslintrc.js from hac-core
Fix eslint issues
Updated build.sh and test.sh to run npm run build and npm run verify on CI

Appears to be an issue with your lint setup. I see the same thing locally.
FWIW, I setup our hac-core-frontend like:

.eslintrc.js
npm run script for lint

/cc @rohitkrai03

Happy coding HAC-Dev folks 😄
Let me know if there are any other issues with the CI. I posted in your slack channel as well.

/lgtm cancel

laaaaaaaaame... meant to wait for Rohit

Too late. Damn... Who can expect such a quick CI... :smirk:


Java Guide- Added Examples to Built in functions

Added examples of Java.IO package and Java.lang packages

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Thank you @bomerzz for your contribution.


Alias ID and Alias ZID for Users

Issue #2505
Users may be copied from a custom identity zone to the default identity zone (or vice versa) to enable customers to do user management in own identity zones.
Prerequisites:

#2637
#2850
#2769

@adrianhoelzl-sap Will you be updating this so it is able to be merged?

@adrianhoelzl-sap Will you be updating this so it is able to be merged?

I resolved the merge conflicts earlier today, does it still show conflicts for you?


fix: inline config if entry parse.

1. Does this PR affect any open issues?(Y/N) and add issue references (e.g. "fix #123", "re #123".):

[x] N
[ ] Y

fix: inline config if entry parse.

2. What is the scope of this PR (e.g. component or file name):

3. Provide a description of the PR(e.g. more details, effects, motivations or doc link):

[ ] Affects user behaviors
[ ] Contains syntax changes
[ ] Contains variable changes
[ ] Contains experimental features
[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[x] Other

4. Are there any breaking changes?(Y/N) and describe the breaking changes(e.g. more details, motivations or doc link):

[x] N
[ ] Y

5. Are there test cases for these changes?(Y/N) select and add more details, references or doc links:

[x] Unit test
[x] Integration test
[ ] Benchmark (add benchmark stats below)
[ ] Manual test (add detailed scripts or steps below)
[ ] Other

kclvm/parser/src/parser/tests.rs
kclvm/parser/src/tests/snapshots/**
test/grammar/datatype/dict/if_item_10/main.k
test/grammar/datatype/dict/if_item_11/main.k

6. Release note

Please refer to Release Notes Language Style Guide to write a quality release note.
None

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 87.988%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
2300

Relevant Lines:
2614

💛  - Coveralls


test(@kampus-apps/gql): Vitest added

Description
Vitest has been added to "gql" platform. Tests were added for following:

Mock Prisma
Sozluk Loaders
User Loaders
Loader Types (yes type tests 🤣)
Loader Key
Term query

Checklist

[x] discord username: ketcapwastaken
[x] Closes #445
[x] PR must be created for an issue from issues under "In progress" column from our project board.
[x] A descriptive and understandable title: The PR title should clearly describe the nature and purpose of the changes. The PR title should be the first thing displayed when the PR is opened. And it should follow the semantic commit rules, and should include the app/package/service name in the title. For example, a title like "docs(@kampus-apps/pano): Add README.md" can be used.
[x] Related file selection: Only relevant files should be touched and no other files should be affected.
[x] I ran npx turbo run at the root of the repository, and build was successful.
[x] I installed the npm packages using npm install --save-exact <package> so my package is pinned to a specific npm version. Leave empty if no package was installed. Leave empty if no package was installed with this PR.

How were these changes tested?
Use npm run test -w @kampus-apps/gql to see all tests are passing.


Activate HRQ E2E test

HRQ E2E test is pending now.
By adding HRQ to v1.1 as a new feature, should we activate it?
https://github.com/kubernetes-sigs/hierarchical-namespaces/blob/168dd7ebae3a6fd47bdbb649b44d5f96aa1a05c5/test/e2e/hrq_test.go#L31-L33

@adrianludwin
Is it related?

I'm going to have to enable HRQ by default before these tests will pass though so I'll work on that next.

https://github.com/kubernetes-sigs/hierarchical-namespaces/pull/289#issuecomment-1579690774

I've changed my mind, I think HRQ should be opt-in for v1.1, then on by default in v1.2. So we can activate the e2e tests on master.

/assign
These are all working except one test, I think because the number of default secrets in the namespace has changed. I'll update the test to be robust to this.

@adrianludwin
Thanks for your answer and I see.

/remove-lifecycle stale


DigitalGamepad with extra buttons

How do I configure extra buttons for Type=DigitalGamepad ?
This cfg doesn't work:
[Mapper]
Type = DigitalGamepad

; These changes are applied on top of the template.
ButtonA             = Button(4)
ButtonB             = Button(3)
ButtonX             = Button(2)
ButtonY             = Button(1)

it fails saying ButtonA etc. are unknown. My goal is to force my Hori Fighting Stick MINI arcade stick (DPAD for directions + 8 buttons) as LS controller with at least 4 buttons.
With Type = DigitalGamepad it works fine, but the emulator then detects just 1 fire button.

You need to put your customizations into a custom mapper. Try this instead:
[Mapper]
Type = Custom

[CustomMapper]
Template = DigitalGamepad

; These changes are applied on top of the template.
ButtonA             = Button(4)
ButtonB             = Button(3)
ButtonX             = Button(2)
ButtonY             = Button(1)

Doesn't seem to be working: Log
Always shows 1 button only...

You might need to change the mapping scheme then.
Does the application actually support multiple gamepad buttons, and if so does it work with another controller with or without Xidi?
You can try mapping to a keyboard button. For example:
; Maps the A button on the controller to the X key on the keyboard
ButtonA = Keyboard(X)

Thanks...
Yes "forcing" ButtonB = Keyboard(z)... does work as expected and the buttons get mapped to the corresponding key in the emu now. The strange thing is that it always sees one single button joystick only:

Of course if I use the XBox One BT controller it shows correctly all the buttons. Same if I use XInputPlus wrapper with the Hori Fighting Stick Mini: the emulator gives me all the expected buttons to be remapped internally...

Digging in a little bit more, it looks like there are some bugs that affect how the game enumerates objects (more specifically, buttons).
One of them is an API issue that can be fixed pretty easily, and the other of which might need a workaround.

This is partially addressed by 9efe81ad4f7b51e80dfa07556d712c023908b085.

The emulator is doing something strange in terms of how it figures out the return value from a call to EnumObjects, which is used to enumerate virtual controller objects like axes, buttons, and so on. For axes it seems fine, but for buttons it seems to be reading memory it shouldn't be reading.
For the system's DirectInput implementation and XInput Plus it seems to get back a non-zero value, which is interpreted as "give me more buttons." But with Xidi it is somehow computing zero, which means "stop giving me buttons." This is why it is only seeing one button with Xidi.
I added a workaround that ignores the return code from the application and enumerates all objects regardless of what the application says. It appears to fix this issue.
Please give this development build a try, along with the supplied configuration.
Xidi-v4.1.1-dev.6.0+a8e64f50.zip
Xidi.ini:
[Mapper]
Type = DigitalGamepad

[Workarounds]
IgnoreEnumObjectsCallbackReturnCode = yes

Works fine as expected now! All buttons are available and remappable from within the emulator.

Great, glad to hear that this fixes the problem.


Hi

I am making now a mpg , and i having a little bit of trouble i am beginer at programing .
When i start the controller the keyboard is 5x4 , but last colon is cloned on first one begining from 2 row i mean
1 2 3 4
4 5 6 7
7 8 9 0
0 a b c
c d e f
i looked in code ,ad i tryed to modify the bitwise function , and it changed a little , but then all goes chaotic .
static uint8_t kbd_read( uint8_t *c1, uint8_t *c2 )
{
uint8_t col, row;
if( c1 == 0 )
  return 0;
*c1 = 0;
if( c2 )
  *c2 = 0;

row = 4;
while( row-- )
{
  reset_row( row );
  col=32;
  while( --col ) __asm("nop");
  col = 5;
  while( col-- )
  {
    uint8_t key;
    if( read_col( col ) )
      continue;
    key = kbd_key_codes[(row<<2)+col];
    if( 0 == *c1 )
    {
      *c1 = key;
    }
    else if( c2 )
    {
      *c2 = key;
      /* dirtyyyy */
      set_row( row );
      return 2;
    }
    else
    {
      set_row( row );
      return 1;
    }
  }
  set_row( row );
}
if( *c1 )
  return 1;
return 0;

}
Thanks .

Hi,
Please provide me information about your wirings, i need to know how you connect your keyboard to board.

So i have a board that i  made by miself and look like this .
The keyboard is made by me , and i don't have any short in there , i measure with multimeter  , and the row and colons are connecting to right pin .

And the problem i have looks like this .

On the rest of keys i have the commands in order , but it duplicate the last row .

Very strange behavior... matrix keyboard code is very simple and i never heard about such problem.
All COLs ( PB5-PB9 ) is pull-up input ( you can check it by default it use internal pull-up to VDD ( 3.3V in our case ) ). So scan looks like this:
PB15 - set to Zero ( than PB14, PB13, PB12 )
then cycle on all COLs to get which one sets to zero and after that calculate keycode ( row_index*4+col_index ).
Looks like something wrong in your real keyboard ( or wiring ), your schematics is fine... but need to check in real. You can do it with multimeter just connect one wire to ROW and check connection between two point ROW + COL i think it will help to find problem.

Thanks for ur help .
I will check the wirings with a osciloscpe , and a multimeter , to see if all works ok , and i will let u know .
I have another question about a think that bothers me .
If i select on rotative button a selection like x , or y or z or anyone , if i move the hand wheel pulse generator , it moves the axis , but if in time the axis moves , i change the rotative comutator , it never stops , and continues to moves until i change position of rotative connector back to selection where i changed earlier .
Ex: i set rotative comutator on x and rotate encoder , the axis start to move , when this happens , i change the rotative comutator to z , and the axis don't stop anymore form it movment , only if i rotate back to x position axis stop after few moments .
I use uccnc as a controller and is set in mpg cont. mode .
I was thinking if i insert a condion on rotative function it will help  to check if the rotative comutator is not moving at all .
Thanks , for this , i want to understand more how this is working .

I have tried now with another stm32 blue pill , and same the last colum gets cloned on first , and i try without a keyboard , just connecting the wires directly from blue pill .

I have checked ur code , and found this :
key = kbd_key_codes[(row<<2)+col]
if
row=3
col=1
result is 13
but if
row=2
col=5
result is still 13
if row=3
col=5 result is 17
if row =4
col=1 result is still 17

Hm... nice tip i just forget about it, my original matrix keyboard was 4x4 and this problem does not apear to me. About axis selection and movement i will check it too. I think i can found time to fix it all. Thanx for this
p.s. workaround it is use 4x4 keyboard.( just not use col5 wire ).

Hi i just resolved this , just change this and will work all ok , its tested.
key = kbd_key_codes[(row*5)+col]

Wondering if u have any info on few sketches to make a wifi conn between pendant adnc pc .
I was  thinking to implement on a bluetoth hc-05 device , but i realy don't know where to start.

Hi i just resolved this , just change this and will work all ok , its tested.
key = kbd_key_codes[(row*5)+col]

yep it will works too thanx.

Wondering if u have any info on few sketches to make a wifi conn between pendant adnc pc .
I was thinking to implement on a bluetoth hc-05 device , but i realy don't know where to start.

Much easy to use something like NRF24L01 as wireless bridge, very easy to program... you can leave USB part as USB-RF dongle and add another one with just RF MPG and keys. My CNC hobby was ended about 6 years ago like that project, so i have no plans for new wireless version.


[8.1.x] ISPN-6192 Memory leak caused by RPCs that complete prior to their timeout

https://issues.jboss.org/browse/ISPN-6192
Re-instrument singleton pattern using enum.

Pulling..

Integrated into 8.1.x, thanks @pferraro !


'NoSuchMethodError' occurs when clipboardData is null

A NoSuchMethodError exception occurs when trying to access the text property of clipboardData when it's null. The relevant code is:
https://github.com/Tkko/Flutter_PinPut/blob/5fb62e572bc356e8fcd35236617acffa9dc61316/lib/pin_put/pin_put_bloc.dart#L51-L56

https://github.com/Tkko/Flutter_PinPut/pull/10

Merged your request, thanks.


Smite support?

Any chance there can be smite support? I see there will be a focus on LoL support, any chance for smite though?

I may consider it, thanks for the suggestion.

Thank you for taking it for consideration!

We will track this in #208


Infinite loop of logs if database no longer exists

Describe the bug
We noticed that if the database inside a clichouse instance is renamed or deleted the Clichouse driver starts logging about 5 million lines every 5 minutes (which has saturated our Datadog quota). Here is the repeating log line:
at com.mchange.v2.resourcepool.BasicResourcePool.checkoutResource(BasicResourcePool.java:594)
Steps to reproduce

Rename or a database in clichouse

Expected behaviour
Few logs not millions !
Error log
at com.mchange.v2.resourcepool.BasicResourcePool.checkoutResource(BasicResourcePool.java:594)
Configuration
Environment

metabase-clickhouse-driver version:  1.50.1
metabase-clickhouse-driver configuration:
Metabase version: v0.50.6

Can you please provide the entire log entry? I will check if it's coming from Metabase itself or the driver.

Hi,
here is a rough extract of logs:
"2024-07-11T09:15:59.978Z",,"""metabase""","at com.mchange.v2.resourcepool.BasicResourcePool.checkoutResource(BasicResourcePool.java:594)" "2024-07-11T09:15:59.978Z",,"""metabase""","at com.mchange.v2.resourcepool.BasicResourcePool.checkoutResource(BasicResourcePool.java:594)" "2024-07-11T09:15:59.978Z",,"""metabase""","at com.mchange.v2.resourcepool.BasicResourcePool.checkoutResource(BasicResourcePool.java:594)" "2024-07-11T09:15:59.978Z",,"""metabase""","at com.mchange.v2.resourcepool.BasicResourcePool.checkoutResource(BasicResourcePool.java:594)" "2024-07-11T09:15:59.978Z",,"""metabase""","at com.mchange.v2.resourcepool.BasicResourcePool.checkoutResource(BasicResourcePool.java:594)" "2024-07-11T09:15:59.978Z",,"""metabase""","at com.mchange.v2.resourcepool.BasicResourcePool.checkoutResource(BasicResourcePool.java:594)" "2024-07-11T09:15:59.978Z",,"""metabase""","at com.mchange.v2.resourcepool.BasicResourcePool.checkoutResource(BasicResourcePool.java:594)" "2024-07-11T09:15:59.978Z",,"""metabase""","at com.mchange.v2.resourcepool.BasicResourcePool.checkoutResource(BasicResourcePool.java:594)" "2024-07-11T09:15:59.978Z",,"""metabase""","at com.mchange.v2.resourcepool.BasicResourcePool.checkoutResource(BasicResourcePool.java:594)" "2024-07-11T09:15:59.978Z",,"""metabase""","at com.mchange.v2.resourcepool.BasicResourcePool.checkoutResource(BasicResourcePool.java:594)" "2024-07-11T09:15:59.978Z",,"""metabase""","at com.mchange.v2.resourcepool.BasicResourcePool.checkoutResource(BasicResourcePool.java:594)" "2024-07-11T09:15:59.978Z",,"""metabase""","at com.mchange.v2.resourcepool.BasicResourcePool.checkoutResource(BasicResourcePool.java:594)" "2024-07-11T09:15:59.978Z",,"""metabase""","at com.mchange.v2.resourcepool.BasicResourcePool.checkoutResource(BasicResourcePool.java:594)" "2024-07-11T09:15:59.978Z",,"""metabase""","at com.mchange.v2.resourcepool.BasicResourcePool.checkoutResource(BasicResourcePool.java:558)" "2024-07-11T09:15:59.978Z",,"""metabase""","at com.mchange.v2.resourcepool.BasicResourcePool.attemptRefurbishResourceOnCheckout(BasicResourcePool.java:1771)" "2024-07-11T09:15:59.978Z",,"""metabase""","at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1PooledConnectionResourcePoolManager.refurbishResourceOnCheckout(C3P0PooledConnectionPool.java:339)" "2024-07-11T09:15:59.978Z",,"""metabase""","at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1PooledConnectionResourcePoolManager.testPooledConnection(C3P0PooledConnectionPool.java:464)" "2024-07-11T09:15:59.978Z",,"""metabase""","at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1PooledConnectionResourcePoolManager.testPooledConnection(C3P0PooledConnectionPool.java:504)" "2024-07-11T09:15:59.978Z",,"""metabase""","at com.mchange.v2.c3p0.AbstractConnectionTester.activeCheckConnection(AbstractConnectionTester.java:79)" "2024-07-11T09:15:59.978Z",,"""metabase""","at com.mchange.v2.c3p0.impl.DefaultConnectionTester.activeCheckConnection(DefaultConnectionTester.java:275)" "2024-07-11T09:15:59.978Z",,"""metabase""","at com.mchange.v2.c3p0.impl.DefaultConnectionTester$3.activeCheckConnectionNoQuery(DefaultConnectionTester.java:180)" "2024-07-11T09:15:59.978Z",,"""metabase""","at com.mchange.v2.c3p0.impl.DefaultConnectionTester$2.activeCheckConnectionNoQuery(DefaultConnectionTester.java:136)" "2024-07-11T09:15:59.978Z",,"""metabase""","at com.clickhouse.jdbc.internal.ClickHouseConnectionImpl.isValid(ClickHouseConnectionImpl.java:911)" "2024-07-11T09:15:59.978Z",,"""metabase""","at com.clickhouse.client.ClickHouseClientBuilder$Agent.ping(ClickHouseClientBuilder.java:317)" "2024-07-11T09:15:59.978Z",,"""metabase""","at com.clickhouse.client.AbstractClient.ping(AbstractClient.java:338)" "2024-07-11T09:15:59.978Z",,"""metabase""","at com.clickhouse.client.ClickHouseClient.ping(ClickHouseClient.java:959)" "2024-07-11T09:15:59.978Z",,"""metabase""","at java.base/java.util.concurrent.CompletableFuture.get(Unknown Source)" "2024-07-11T09:15:59.978Z",,"""metabase""","at java.base/java.util.concurrent.CompletableFuture.reportGet(Unknown Source)" "2024-07-11T09:15:59.978Z",,"""metabase""","java.util.concurrent.ExecutionException: com.clickhouse.client.ClickHouseException: Code: 81. DB::Exception: Database staging does not exist.  DB::Exception: Database staging does not exist. (UNKNOWN_DATABASE) (version <IP_ADDRESS>70 (official build))" "2024-07-11T09:15:59.977Z",,"""metabase""","... 1006 more" "2024-07-11T09:15:59.977Z",,"""metabase""","at com.mchange.v2.resourcepool.BasicResourcePool.checkoutResource(BasicResourcePool.java:558)" "2024-07-11T09:15:59.977Z",,"""metabase""","at com.mchange.v2.resourcepool.BasicResourcePool.attemptRefurbishResourceOnCheckout(BasicResourcePool.java:1771)" "2024-07-11T09:15:59.977Z",,"""metabase""","at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1PooledConnectionResourcePoolManager.refurbishResourceOnCheckout(C3P0PooledConnectionPool.java:339)" "2024-07-11T09:15:59.977Z",,"""metabase""","at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1PooledConnectionResourcePoolManager.testPooledConnection(C3P0PooledConnectionPool.java:464)" "2024-07-11T09:15:59.977Z",,"""metabase""","at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1PooledConnectionResourcePoolManager.testPooledConnection(C3P0PooledConnectionPool.java:504)" "2024-07-11T09:15:59.977Z",,"""metabase""","at com.mchange.v2.c3p0.AbstractConnectionTester.activeCheckConnection(AbstractConnectionTester.java:79)" "2024-07-11T09:15:59.977Z",,"""metabase""","at com.mchange.v2.c3p0.impl.DefaultConnectionTester.activeCheckConnection(DefaultConnectionTester.java:275)" "2024-07-11T09:15:59.977Z",,"""metabase""","at com.mchange.v2.c3p0.impl.DefaultConnectionTester$3.activeCheckConnectionNoQuery(DefaultConnectionTester.java:180)" "2024-07-11T09:15:59.977Z",,"""metabase""","at com.mchange.v2.c3p0.impl.DefaultConnectionTester$2.activeCheckConnectionNoQuery(DefaultConnectionTester.java:136)" "2024-07-11T09:15:59.977Z",,"""metabase""","at com.clickhouse.jdbc.internal.ClickHouseConnectionImpl.isValid(ClickHouseConnectionImpl.java:911)" "2024-07-11T09:15:59.977Z",,"""metabase""","at com.clickhouse.client.ClickHouseClientBuilder$Agent.ping(ClickHouseClientBuilder.java:317)" "2024-07-11T09:15:59.977Z",,"""metabase""","at com.clickhouse.client.AbstractClient.ping(AbstractClient.java:338)" "2024-07-11T09:15:59.977Z",,"""metabase""","at com.clickhouse.client.ClickHouseClient.ping(ClickHouseClient.java:958)" "2024-07-11T09:15:59.977Z",,"""metabase""","at com.clickhouse.client.ClickHouseRequest.execute(ClickHouseRequest.java:2144)" "2024-07-11T09:15:59.977Z",,"""metabase""","at com.clickhouse.client.AbstractClient.execute(AbstractClient.java:280)" "2024-07-11T09:15:59.977Z",,"""metabase""","at com.clickhouse.client.http.ClickHouseHttpClient.send(ClickHouseHttpClient.java:200)" "2024-07-11T09:15:59.977Z",,"""metabase""","at com.clickhouse.client.http.HttpUrlConnectionImpl.post(HttpUrlConnectionImpl.java:246)" "2024-07-11T09:15:59.977Z",,"""metabase""","at com.clickhouse.client.http.HttpUrlConnectionImpl.checkResponse(HttpUrlConnectionImpl.java:203)" "2024-07-11T09:15:59.977Z",,"""metabase""","Caused by: java.io.IOException: Code: 81. DB::Exception: Database staging does not exist. (UNKNOWN_DATABASE) (version <IP_ADDRESS>70 (official build))" "2024-07-11T09:15:59.977Z",,"""metabase""","... 1008 more" "2024-07-11T09:15:59.977Z",,"""metabase""","at com.mchange.v2.resourcepool.BasicResourcePool.checkoutResource(BasicResourcePool.java:558)" "2024-07-11T09:15:59.977Z",,"""metabase""","at com.mchange.v2.resourcepool.BasicResourcePool.attemptRefurbishResourceOnCheckout(BasicResourcePool.java:1771)" "2024-07-11T09:15:59.977Z",,"""metabase""","at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1PooledConnectionResourcePoolManager.refurbishResourceOnCheckout(C3P0PooledConnectionPool.java:339)" "2024-07-11T09:15:59.977Z",,"""metabase""","at com.mchange.v2.resourcepool.BasicResourcePool.checkoutResource(BasicResourcePool.java:558)" "2024-07-11T09:15:59.977Z",,"""metabase""","at com.mchange.v2.resourcepool.BasicResourcePool.attemptRefurbishResourceOnCheckout(BasicResourcePool.java:1771)" "2024-07-11T09:15:59.977Z",,"""metabase""","at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1PooledConnectionResourcePoolManager.refurbishResourceOnCheckout(C3P0PooledConnectionPool.java:339)" "2024-07-11T09:15:59.977Z",,"""metabase""","at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1PooledConnectionResourcePoolManager.testPooledConnection(C3P0PooledConnectionPool.java:464)" "2024-07-11T09:15:59.977Z",,"""metabase""","at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1PooledConnectionResourcePoolManager.testPooledConnection(C3P0PooledConnectionPool.java:504)" "2024-07-11T09:15:59.977Z",,"""metabase""","at com.mchange.v2.c3p0.AbstractConnectionTester.activeCheckConnection(AbstractConnectionTester.java:79)" "2024-07-11T09:15:59.977Z",,"""metabase""","at com.mchange.v2.c3p0.impl.DefaultConnectionTester.activeCheckConnection(DefaultConnectionTester.java:275)" "2024-07-11T09:15:59.977Z",,"""metabase""","at com.mchange.v2.c3p0.impl.DefaultConnectionTester$3.activeCheckConnectionNoQuery(DefaultConnectionTester.java:180)" "2024-07-11T09:15:59.977Z",,"""metabase""","at com.mchange.v2.c3p0.impl.DefaultConnectionTester$2.activeCheckConnectionNoQuery(DefaultConnectionTester.java:136)" "2024-07-11T09:15:59.977Z",,"""metabase""","at com.clickhouse.jdbc.internal.ClickHouseConnectionImpl.isValid(ClickHouseConnectionImpl.java:911)" "2024-07-11T09:15:59.977Z",,"""metabase""","at com.clickhouse.client.ClickHouseClientBuilder$Agent.ping(ClickHouseClientBuilder.java:317)" "2024-07-11T09:15:59.977Z",,"""metabase""","at com.clickhouse.client.AbstractClient.ping(AbstractClient.java:338)" "2024-07-11T09:15:59.977Z",,"""metabase""","at com.clickhouse.client.ClickHouseClient.ping(ClickHouseClient.java:958)" "2024-07-11T09:15:59.977Z",,"""metabase""","at com.clickhouse.client.ClickHouseRequest.execute(ClickHouseRequest.java:2144)" "2024-07-11T09:15:59.977Z",,"""metabase""","at com.clickhouse.client.AbstractClient.execute(AbstractClient.java:280)" "2024-07-11T09:15:59.977Z",,"""metabase""","at com.clickhouse.client.http.ClickHouseHttpClient.send(ClickHouseHttpClient.java:200)" "2024-07-11T09:15:59.977Z",,"""metabase""","at com.clickhouse.client.http.HttpUrlConnectionImpl.post(HttpUrlConnectionImpl.java:246)" "2024-07-11T09:15:59.977Z",,"""metabase""","at com.clickhouse.client.http.HttpUrlConnectionImpl.checkResponse(HttpUrlConnectionImpl.java:203)" "2024-07-11T09:15:59.977Z",,"""metabase""","Caused by: java.io.IOException: Code: 81. DB::Exception: Database staging does not exist. (UNKNOWN_DATABASE) (version <IP_ADDRESS>70 (official build))" "2024-07-11T09:15:59.977Z",,"""metabase""","... 1008 more" "2024-07-11T09:15:59.977Z",,"""metabase""","at com.mchange.v2.resourcepool.BasicResourcePool.checkoutResource(BasicResourcePool.java:558)" "2024-07-11T09:15:59.977Z",,"""metabase""","at com.mchange.v2.resourcepool.BasicResourcePool.attemptRefurbishResourceOnCheckout(BasicResourcePool.java:1771)" "2024-07-11T09:15:59.977Z",,"""metabase""","at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1PooledConnectionResourcePoolManager.refurbishResourceOnCheckout(C3P0PooledConnectionPool.java:339)" "2024-07-11T09:15:59.977Z",,"""metabase""","at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1PooledConnectionResourcePoolManager.testPooledConnection(C3P0PooledConnectionPool.java:464)" "2024-07-11T09:15:59.977Z",,"""metabase""","at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1PooledConnectionResourcePoolManager.testPooledConnection(C3P0PooledConnectionPool.java:504)" "2024-07-11T09:15:59.977Z",,"""metabase""","at com.mchange.v2.c3p0.AbstractConnectionTester.activeCheckConnection(AbstractConnectionTester.java:79)" "2024-07-11T09:15:59.977Z",,"""metabase""","at com.mchange.v2.c3p0.impl.DefaultConnectionTester.activeCheckConnection(DefaultConnectionTester.java:275)" "2024-07-11T09:15:59.977Z",,"""metabase""","at com.mchange.v2.c3p0.impl.DefaultConnectionTester$3.activeCheckConnectionNoQuery(DefaultConnectionTester.java:180)" "2024-07-11T09:15:59.976Z",,"""metabase""","at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1PooledConnectionResourcePoolManager.testPooledConnection(C3P0PooledConnectionPool.java:464)" "2024-07-11T09:15:59.976Z",,"""metabase""","at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1PooledConnectionResourcePoolManager.testPooledConnection(C3P0PooledConnectionPool.java:504)" "2024-07-11T09:15:59.976Z",,"""metabase""","at com.mchange.v2.c3p0.AbstractConnectionTester.activeCheckConnection(AbstractConnectionTester.java:79)" "2024-07-11T09:15:59.976Z",,"""metabase""","at com.mchange.v2.c3p0.impl.DefaultConnectionTester.activeCheckConnection(DefaultConnectionTester.java:275)" "2024-07-11T09:15:59.976Z",,"""metabase""","at com.mchange.v2.c3p0.impl.DefaultConnectionTester$3.activeCheckConnectionNoQuery(DefaultConnectionTester.java:180)" "2024-07-11T09:15:59.976Z",,"""metabase""","at com.mchange.v2.c3p0.impl.DefaultConnectionTester$2.activeCheckConnectionNoQuery(DefaultConnectionTester.java:136)" "2024-07-11T09:15:59.976Z",,"""metabase""","at com.clickhouse.jdbc.internal.ClickHouseConnectionImpl.isValid(ClickHouseConnectionImpl.java:911)" "2024-07-11T09:15:59.976Z",,"""metabase""","at com.clickhouse.client.ClickHouseClientBuilder$Agent.ping(ClickHouseClientBuilder.java:317)" "2024-07-11T09:15:59.976Z",,"""metabase""","at com.clickhouse.client.AbstractClient.ping(AbstractClient.java:338)" "2024-07-11T09:15:59.976Z",,"""metabase""","at com.clickhouse.client.ClickHouseClient.ping(ClickHouseClient.java:958)" "2024-07-11T09:15:59.976Z",,"""metabase""","at com.clickhouse.client.ClickHouseRequest.execute(ClickHouseRequest.java:2144)" "2024-07-11T09:15:59.976Z",,"""metabase""","at com.clickhouse.client.AbstractClient.execute(AbstractClient.java:282)" "2024-07-11T09:15:59.976Z",,"""metabase""","at com.clickhouse.client.ClickHouseException.of(ClickHouseException.java:151)" "2024-07-11T09:15:59.976Z",,"""metabase""","Caused by: com.clickhouse.client.ClickHouseException: Code: 81. DB::Exception: Database staging does not exist. (UNKNOWN_DATABASE) (version <IP_ADDRESS>70 (official build))" "2024-07-11T09:15:59.976Z",,"""metabase""","at com.mchange.v2.resourcepool.BasicResourcePool.checkoutResource(BasicResourcePool.java:594)" "2024-07-11T09:15:59.976Z",,"""metabase""","at com.mchange.v2.resourcepool.BasicResourcePool.checkoutResource(BasicResourcePool.java:594)" "2024-07-11T09:15:59.976Z",,"""metabase""","at com.mchange.v2.resourcepool.BasicResourcePool.checkoutResource(BasicResourcePool.java:594)" "2024-07-11T09:15:59.976Z",,"""metabase""","at com.mchange.v2.resourcepool.BasicResourcePool.checkoutResource(BasicResourcePool.java:594)" "2024-07-11T09:15:59.976Z",,"""metabase""","at com.mchange.v2.resourcepool.BasicResourcePool.checkoutResource(BasicResourcePool.java:594)" "2024-07-11T09:15:59.976Z",,"""metabase""","at com.mchange.v2.resourcepool.BasicResourcePool.checkoutResource(BasicResourcePool.java:594)" "2024-07-11T09:15:59.976Z",,"""metabase""","at com.mchange.v2.resourcepool.BasicResourcePool.checkoutResource(BasicResourcePool.java:594)" "2024-07-11T09:15:59.976Z",,"""metabase""","at com.mchange.v2.resourcepool.BasicResourcePool.checkoutResource(BasicResourcePool.java:594)"

Thanks, I repro'd on 0.50.6 and 0.50.8. Steps:

Set up a database in ClickHouse. e.g.

clickhouse-client -q "CREATE DATABASE IF NOT EXISTS db;"
clickhouse-client -q "CREATE TABLE db.table_1 (c_1 Int32) ENGINE = MergeTree() ORDER BY c_1;"

Add the database in Metabase Admin Settings.
Rename the database in ClickHouse. e.g.

clickhouse-client -q "RENAME DATABASE db TO newdb;"

Query from the table created in step 1. Go to Home > Databases > the clickhouse DB > the table.


flutter web support?

Does anyone have any suggestions for web support?

I'll look into it.

I'm so glad to hear that, I hope you get it sorted soon.

I'll look into it.

For the web support you might be able to use jsPDF. Though it would render html into an embedded image.
It needs these two dependencies:
<script src="jspdf.umd.js"></script>
<script src="html2canvas.js"></script>

then the following js code produces PDF document:
window.jsPDF = window.jspdf.jsPDF;
var doc = new jsPDF();
doc.html(document.body, {
   callback: function (doc) {
     doc.save();
   },
   width: 135,
   windowWidth: 600
});

I'll look into it.

For the web support you might be able to use jsPDF. Though it would render html into an embedded image.
It needs these two dependencies:
<script src="jspdf.umd.js"></script>
<script src="html2canvas.js"></script>

then the following js code produces PDF document:
window.jsPDF = window.jspdf.jsPDF;
var doc = new jsPDF();
doc.html(document.body, {
   callback: function (doc) {
     doc.save();
   },
   width: 135,
   windowWidth: 600
});

can u show me full example project?


Remove check that Java version output must start with "java version"

This PR removes the check for Java version output from JavaVersion.java class from STF.

Background: We do not need to check for java version output's validity in STF, since we have functional tests to check for it and also perform additional tests for it on TKG. Besides, this check over here causes exceptions every time we want to test a new SDK (e.g.  https://github.com/eclipse-openj9/openj9/issues/13154).

Note : This PR is part of a larger task of re-implementing how STF figures out Java version - which requires that we first investigate how Java version is used in various STF based tests. We will cover that in a separate PR.

Signed-off-by: Mesbah-Alam<EMAIL_ADDRESS>

Test : Grinder/16865/

lgtm


High CPU load on copying big amount of files

Lastly, I discovered on using the tool with SD cards containing thousands of files, the CPU load quickly up and reach pretty amazing loads for just copying files (https://twitter.com/Themimitoof/status/1344369659781513218?s=20)
I don't know if write cache synchronization can be the cause but I need to troubleshoot that and also check for implementing multithreading (#3) and see if it can solve or reduce the pressure on the system.

The problem only happen on my work laptop and my broken XFS partition.


[FEATURE] NATS Object store implementation for wasi:blobstore

Affected project(s)

[ ] documentation
[ ] examples
[ ] wasmCloud host
[ ] wasmCloud CLI (wash)
[ ] wasmCloud dashboard UI (washboard)
[X] capability providers
[ ] provider bindgen
[ ] control interface client
[ ] other / not sure

Is your feature request related to a problem? Please describe.
No response
Describe the solution you'd like
I would love to see an implementation of wasi:blobstore (via wrpc:blobstore) for NATS object store.
Describe alternatives you've considered
No response
Additional context
No response

@ossfellow

Please assign to me; I'll add the issue description later.

@brooksmtownsend, I'm separating the provider, and the example, as I anticipate that the latter will require its own scrutiny. I have create issue https://github.com/wasmCloud/wasmCloud/issues/3737 for the example, which should be assigned to me.
Thank you.


Data export: include trips (start and end time/odometer)

Extend export to include trips as well as charging sessions so can see if needed to charge during peak because of an upcoming trip.

Lower priority on this one.


Autoscale from 0 CPUs in a Ray cluster

Describe the bug
Daft may not be handling the case where a Ray cluster is started with 0 workers correctly.

Duplicate of #1823


🔨 ThreadBot Middlware hook addition

📖 Improve original readme using npx readme-md-generator
:gear: Improve settings improvement suggestions for consistent formatting from vscode + recommended extension
🎉 Threadbot.channel included
🎉 Template for readme to allow more consistent documentation from contributions

Awesome. Thanks!


[Bug]: Queries do not fetch any data when datasources are configured while importing an app

Is there an existing issue for this?

[X] I have searched the existing issues

Description
When we configure DSs while importing an app, the queries of the respective DSs do not fetch any data.
Note: This is not reproducible on prod.
App used:
OldApp_DSTesting1.9.24_Latest.json
Steps To Reproduce

Import app using a JSON.
Authorise datasources and then go to the application.
Run the queries of the said datasources.

Expected: The queries should fetch relevant data.
Actual: No data is retrieved on running the queries & we see errors.
Public Sample App
No response
Environment
Release
Severity
High (Blocker to building or releasing)
Issue video log
https://jam.dev/c/ee7b7fed-c2fa-4846-8e77-4a9fb83b6d93
Version
Cloud

Verified on release.
https://jam.dev/c/382b1bde-464b-4bd4-8601-5bff31d95cd0


rancher up hangs while upgrading if the container health check fails

Rancher versions:
rancher/server: 1.6.0
rancher/agent: v1.2.2
Infrastructure Stack versions:
healthcheck: v0.3.0
ipsec: 0.1.0
network-services: v0.2.0
scheduler: v0.5.1
kubernetes (if applicable):
Docker version: (docker version,docker info preferred)
17.03
Operating system and kernel: (cat /etc/os-release, uname -r preferred)
4.11.0-1.el7.elrepo.x86_64
/etc/os-release
NAME="CentOS Linux"
VERSION="7 (Core)"
ID="centos"
ID_LIKE="rhel fedora"
VERSION_ID="7"
PRETTY_NAME="CentOS Linux 7 (Core)"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:centos:centos:7"
HOME_URL="https://www.centos.org/"
BUG_REPORT_URL="https://bugs.centos.org/"
CENTOS_MANTISBT_PROJECT="CentOS-7"
CENTOS_MANTISBT_PROJECT_VERSION="7"
REDHAT_SUPPORT_PRODUCT="centos"
REDHAT_SUPPORT_PRODUCT_VERSION="7"
Type/provider of hosts: (VirtualBox/Bare-metal/AWS/GCE/DO)
AWS
Setup details: (single node rancher vs. HA rancher, internal DB vs. external DB)
HA Rancher
Environment Template: (Cattle/Kubernetes/Swarm/Mesos)
Cattle
We're currently making use of above rancher v1.6.0 which has cattle v0.179.7 installed. We have also configured the healthcheck of the container and mentioned the values of both initializing_timeout and reinitializing_timeout of around 80 seconds.
Now, while doing rancher upgrade via rancher up -s <stack-name> --force-recreate --pull --batch-size 1 -d
the health check of the container fails, but the rancher up command simply hangs up and doesn't fails, in the jenkins job.
What we want to have finally
We are actually looking for the rancher up command to fail automatically if the application deployment inside the container fails and print the container logs on the jenkins console itself.
Really need help on this. @deniseschannon @ibuildthecloud

What's the full configuration of your healthcheck? Could you post the docker-compose.yml and rancher-compose.yml files (with any sensitive parts sanitized)?

@cjellick
Please see the modified (with sensitive parts sanitized) docker-compose.yml and rancher-compose.yml file.
docker-compose.yml
version: '2' services:   nginx-test:     mem_limit: 150000000     image: modified-nginx     hostname: nqa-docker-nginx-test     environment:       ENV: nqa     command:     - /usr/bin/supervisord     labels:       io.rancher.container.pull_image: always
So, in the modified-nginx image, we have installed supervisord and configured supervisord to execute the start.sh script present in /mnt1.
now, in /mnt1/start.sh script, I have
#!/bin/bash sleep 60 exit 1
rancher-compose.yml
version: '2' services:   nginx-test:     scale: 2     start_on_create: true     health_check:       healthy_threshold: 2       response_timeout: 5000       port: 80       unhealthy_threshold: 2       initializing_timeout: 80000       interval: 10000       strategy: recreate       reinitializing_timeout: 80000
the healthcheck is configured as mentioned above in rancher-compose.yml file.
now while running this, rancher up command or rancher-compose up command with the below options --force-recreate --pull --batch-size 1
keeps on spawning containers again and again in the jenkins job. Via the jenkins job itself, we're not able to identify whether the deployment inside the container is failing or not or whether container is healthy or not.
let me know, if you need any other info.

Thanks for your report!
With the release of Rancher 2.0, development on v1.6 is only limited to critical bug fixes and security patches.
If you think we should keep this issue open, please let me know.


Fix minor doc bugs in README.md

Not having that meta tag can lead to a really fun error message.

LGTM. I'll merge since I have the power.


dbeaver hangs while trying to open previous tab with .erd that is deleted

System information:

Operating system (distribution) and version - Windows 10 Enterprise
DBeaver version - 7.0 Enterprise
Additional extensions
None

Connection specification:

Database name and version
Driver name
Do you use tunnels or proxies (SSH, SOCKS, etc)?

Describe the problem you're observing:
Dbeaver hangs on startup and never recovers...
Steps to reproduce, if exist:
Create a new ERD diagram and save the file.
Left the tab with .erd file open and closed the dbeaver application
Delete the .erd file
Open dbeaver, notice you will see the erd tab and blocked UI.
Include any warning/errors/backtraces from the logs

Hi @AMassani ,
unfortunately cannot reproduce it. Could you try if it reproducible for you against 7.1?

there is not any update on issue for a long time. Ticket is closed.
If issue is still actual for you - feel free to reopen the issue with additional info

For what its worth, this exact same thing just happened to me in 7.1.0. I had to go delete the workbench.xmi file to be able to get back into DBeaver. I had an ERD I created in DBeaver and had subsequently deleted. Got hung trying to open that tab.

For what its worth, this exact same thing just happened to me in 7.1.0. I had to go delete the workbench.xmi file to be able to get back into DBeaver. I had an ERD I created in DBeaver and had subsequently deleted. Got hung trying to open that tab.


Parser Error - AFNetworking

Hi, I am experiencing a problem somehow similar to this https://github.com/felixge/node-formidable/issues/71.
In my building a multipart request with the help of AFNetworking this way
NSMutableURLRequest * request = [manager multipartFormRequestWithObject:nil method:RKRequestMethodPOST path:path parameters:nil constructingBodyWithBlock:
^(id<AFMultipartFormData> formData) {
        NSData * data = [NSData dataWithContentsOfURL:path];
        [formData appendPartWithFileData:data name:@"data[file]" <EMAIL_ADDRESS>mimeType:@"video/quicktime"];
    }];

The request has been tested against the express body parser which does not cause any problem.
Formidable is unable to parse the request. It fails raising this exception [Error: parser error, 1623 of 1627 bytes parsed].
I think that the issue can be related to the multipart boundary used in AFNetworking:
static NSString * const kAFMultipartFormBoundary = @"Boundary+0xAbCdEfGbOuNdArY";

closing, open again if you can reproduce


Move timezone offset calculation to client side

I think we can do the timezone offset in the client instead on server side when we change to reactjs:
Serve $event_timestamp + $server_time. Get offset using $server_time - $browser_time and render the correct timestamp in the browser.
The $server_time can retrieved once one socket connect or an similar event

This is done in "batcode", where the backend store RFC 3339 which is sent directly to the frontend and rendered using local timezone.


Can't build on macOS Sierra

Hey,
Just tried to build omnisharp on macOS Sierra 10.12 and run into multiple errors. I saw similar issue on other projects and if I understand the problem correctly, this must be fixed on project level.
Problem
$ git rev-parse HEAD
3d943b4f5b21ce97667a0be06b8110e63c6456ec

$ ./build.sh
Feeds used:
  /Users/d12frosted/.local/share/NuGet/Cache
  /Users/d12frosted/.nuget/packages/
  https://dotnet.myget.org/F/dotnet-buildtools/api/v3/index.json
  https://api.nuget.org/v3/index.json

All packages listed in /Users/d12frosted/Developer/Other/omnisharp-roslyn/scripts/packages.config are already installed.
Analyzing build script...
Processing build script...
Installing addins...
Compiling build script...

========================================
Cleanup
========================================
Executing task: Cleanup
Finished executing task: Cleanup

========================================
BuildEnvironment
========================================
Executing task: BuildEnvironment
dotnet-install: .NET SDK version 1.0.0-preview2-003121 is already installed.
dotnet-install: Adding to current process PATH: /Users/d12frosted/Developer/Other/omnisharp-roslyn/.dotnet. Note: This change will be visible only when sourcing script.
dotnet-install: Installation finished successfully.
.NET Command Line Tools (1.0.0-preview2-003121)

Product Information:
 Version:            1.0.0-preview2-003121
 Commit SHA-1 hash:  1e9d529bc5

Runtime Environment:
 OS Name:     Mac OS X
 OS Version:  10.12
 OS Platform: Darwin
 RID:         osx.10.12-x64
Feeds used:
  https://dotnet.myget.org/F/dotnet-buildtools/api/v3/index.json
  https://api.nuget.org/v3/index.json

Package "xunit.runner.console.2.2.0-beta2-build3300" is already installed.
Finished executing task: BuildEnvironment

========================================
PopulateRuntimes
========================================
Executing task: PopulateRuntimes
Finished executing task: PopulateRuntimes

========================================
Setup
========================================
Executing task: Setup
Finished executing task: Setup

========================================
Restore
========================================
Executing task: Restore
Restoring packages....
Package restore successful!
Restoring packages....
log  : Restoring packages for /Users/d12frosted/Developer/Other/omnisharp-roslyn/tests/TestSamples/ProjectSearchSample06/src/Project2/project.json...
log  : Restoring packages for /Users/d12frosted/Developer/Other/omnisharp-roslyn/tests/TestSamples/ProjectSearchSample06/tests/Test1/project.json...
log  : Restoring packages for /Users/d12frosted/Developer/Other/omnisharp-roslyn/tests/TestUtility/project.json...
log  : Restoring packages for /Users/d12frosted/Developer/Other/omnisharp-roslyn/tests/TestSamples/ProjectSearchSample07/tests/Test1/project.json...
log  : Restoring packages for /Users/d12frosted/Developer/Other/omnisharp-roslyn/tests/TestSamples/ProjectSearchSample07/src/Project1/project.json...
log  : Restoring packages for /Users/d12frosted/Developer/Other/omnisharp-roslyn/tests/TestSamples/ProjectSearchSample07/src/Project2/project.json...
log  : Restoring packages for /Users/d12frosted/Developer/Other/omnisharp-roslyn/tests/TestSamples/ProjectSearchSample07/src/Project2/Embed/project.json...
log  : Restoring packages for /Users/d12frosted/Developer/Other/omnisharp-roslyn/tests/TestSamples/ProjectSearchSample06/src/Project2/Embed/project.json...
error: System.Diagnostics.Process 4.1.0 provides a compile-time reference assembly for System.Diagnostics.Process on .NETCoreApp,Version=v1.0, but there is no run-time assembly compatible with osx.10.12-x64.

...

Full log can be found here.
Oh, and just to make this report more interesting, here is screenshot that made my day. I wasn't ready for this 💃 😸

P. S. Sorry if it's actually not related to Omnisharp.

You'll probably need to change this line to osx.10.12-x64.

@willl
Thanks for suggestion. But still doesn't work. I also tried to build on clean repository (so it downloaded some required tools / libs) with that change in project.json file. Here is new output (52.3 Mb and buffer has 202401 lines, 8321969 words, and 54891506 characters 😸).

@d12frosted, @wjk: Could you try PR #642? Does that address the problem. I'm a bit nervous about updating to Sierra myself to see if it fixes it.

Ah -- I see why it's failing. We didn't specify a RID in build.cake on OSX: https://github.com/OmniSharp/omnisharp-roslyn/blob/dev/build.cake#L118

I think I've got a fix for this here: https://github.com/OmniSharp/omnisharp-roslyn/pull/644. It'd be great if somebody could pull that change and try it out.

It looks like we also do a "dotnet restore --infer-runtimes" for tests in https://github.com/OmniSharp/omnisharp-roslyn/blob/dev/build.cake#L172-L183, which will certainly break on macSierra.

@DustinCampbell Replacing dotnet restore --infer-runtimes with just plain dotnet restore causes the restore to succeed, but then the BuildTest target fails with the following message:
Can not find runtime target for framework '.NETCoreApp,Version=v1.0' compatible with one of the target runtimes: 'osx.10.12-x64'. Possible causes:
1. The project has not been restored or restore failed - run `dotnet restore`
2. The project does not list one of 'osx.10.12-x64' in the 'runtimes' section.
3. You may be trying to publish a library, which is not supported. Use `dotnet pack` to distribute libraries.

Yeah, "default" keeps getting threaded through various steps in the build process. I've updated to macSierra and am working through the issues.

OK. #644 should fix this now.

@DustinCampbell thank you for suggestions. I will try those PRs today in the evening. And I'll let you know about results.

I'm a bit nervous about updating to Sierra myself to see if it fixes it.

Now I am a bit nervous about doing update as well 😸 💃

@d12frosted: No worries. #644 does fix the build.

@DustinCampbell indeed. Thanks for a quick solution! 💃 ❤


Instability problems: Nuxt.js server responds very slowly on local / dev environments

Version
v2.8.1
Reproduction link
http://jsfiddle.net
Steps to reproduce
Just run npm update, then load any pages on the site (on dev / localhost), and notice: many pages either dont load, or reload. The console is also flooded with messages. I've included the diff'd package-lock.json.
What is expected ?
Should not be seeing any slowness.
What is actually happening?
After an npm update, this issue came back: https://github.com/nuxt/nuxt.js/issues/3566
Nuxt.js server responds very slowly, even on local / dev environments. The console is flooded with workbox messages, and a lot of pages on my site don't load, or reload.
Something broke because of the updated package-lock.json below.
Using CacheFirst to respond to '/_nuxt/icons/icon_64.9mld2VBMsQ$.png'  Router is responding to: /__webpack_hmr/client

diff --git a/package-lock.json b/package-lock.json
index 1ea16ec..5d84ccd 100644
--- a/package-lock.json
+++ b/package-lock.json
@@ -5914,9 +5914,9 @@
       }
     },
     "jpeg-js": {
-      "version": "0.3.5",
-      "resolved": "https://registry.npmjs.org/jpeg-js/-/jpeg-js-0.3.5.tgz",
-      "integrity": "sha512-hvaExqwmQDS8O9qnZAVDXGWU43Tbu1V0wMZmjROjT11jloSgGICZpscG+P6Nyi1BVAvyu2ARRx8qmEW30sxgdQ=="
+      "version": "0.3.6",
+      "resolved": "https://registry.npmjs.org/jpeg-js/-/jpeg-js-0.3.6.tgz",
+      "integrity": "sha512-MUj2XlMB8kpe+8DJUGH/3UJm4XpI8XEgZQ+CiHDeyrGoKPdW/8FJv6ku+3UiYm5Fz3CWaL+iXmD8Q4Ap6aC1Jw=="
     },
     "js-base64": {
       "version": "2.5.1",
@@ -9334,6 +9334,16 @@
         "strip-indent": "^1.0.1"
       }
     },
+    "reduce-css-calc": {
+      "version": "2.1.6",
+      "resolved": "https://registry.npmjs.org/reduce-css-calc/-/reduce-css-calc-2.1.6.tgz",
+      "integrity": "sha512-+l5/qlQmdsbM9h6JerJ/y5vR5Ci0k93aszLNpCmbadC3nBcbRGmIBm0s9Nj59i22LvCjTGftWzdQRwdknayxhw==",
+      "dev": true,
+      "requires": {
+        "css-unit-converter": "^1.1.1",
+        "postcss-value-parser": "^3.3.0"
+      }
+    },
     "regenerate": {
       "version": "1.4.0",
       "resolved": "https://registry.npmjs.org/regenerate/-/regenerate-1.4.0.tgz",
@@ -10343,13 +10353,13 @@
       }
     },
     "string.prototype.trim": {
-      "version": "1.1.2",
-      "resolved": "https://registry.npmjs.org/string.prototype.trim/-/string.prototype.trim-1.1.2.tgz",
-      "integrity": "sha1-0E3iyJ4Tf019IG8Ia17S+ua+jOo=",
+      "version": "1.2.0",
+      "resolved": "https://registry.npmjs.org/string.prototype.trim/-/string.prototype.trim-1.2.0.tgz",
+      "integrity": "sha512-9EIjYD/WdlvLpn987+ctkLf0FfvBefOCuiEr2henD8X+7jfwPnyvTdmW8OJhj5p+M0/96mBdynLWkxUr+rHlpg==",
       "requires": {
-        "define-properties": "^1.1.2",
-        "es-abstract": "^1.5.0",
-        "function-bind": "^1.0.2"
+        "define-properties": "^1.1.3",
+        "es-abstract": "^1.13.0",
+        "function-bind": "^1.1.1"
       }
     },
     "string_decoder": {
@@ -10484,9 +10494,9 @@
       }
     },
     "tailwindcss": {
-      "version": "1.0.6",
-      "resolved": "https://registry.npmjs.org/tailwindcss/-/tailwindcss-1.0.6.tgz",
-      "integrity": "sha512-hhdvXpnlYNnxfZCpldMypSWRzgmoQbKBy3namGlsP0Gs+qM8EwF3DBVUPoq8wJYbBFjzrgatE4czWJ6f12Y9+Q==",
+      "version": "1.1.0",
+      "resolved": "https://registry.npmjs.org/tailwindcss/-/tailwindcss-1.1.0.tgz",
+      "integrity": "sha512-hcxY5MUrY/LcdsX4Xr2aOF24eF4HaxDbHCbDu3W2+bCJRsXRhJmZfAgjipjsyhZult0YAa9HFp14xRXMqwUYTw==",
       "dev": true,
       "requires": {
         "autoprefixer": "^9.4.5",
@@ -10501,7 +10511,8 @@
         "postcss-js": "^2.0.0",
         "postcss-nested": "^4.1.1",
         "postcss-selector-parser": "^6.0.0",
-        "pretty-hrtime": "^1.0.3"
+        "pretty-hrtime": "^1.0.3",
+        "reduce-css-calc": "^2.1.6"
       },

This bug report is available on Nuxt community (#c9617)

Update: things seem to be working fine if you run "npm run build && npm run start", though the logs still show lots of messages from workbox.
On running npm run dev, however, none of the pages are loading.

In the console logs:
vendors.app.js:12916 warn [HMR] Update check failed: Error: Manifest request to /_nuxt/e12a06ad6b43baad4b84.hot-update.json timed out.
    at XMLHttpRequest.request.onreadystatechange (http://localhost:3000/_nuxt/runtime.js:92:16)
value @ vendors.app.js:12916
value @ vendors.app.js:12916
value @ vendors.app.js:12916
(anonymous) @ vendors.app.js:12916
handleError @ vendors.app.js:15731
cb @ vendors.app.js:15641
Promise.catch (async)
check @ vendors.app.js:15677
push../node_modules/webpack-hot-middleware/process-update.js.module.exports @ vendors.app.js:15636
processMessage @ vendors.app.js:15513
handleMessage @ vendors.app.js:15373
handleMessage @ vendors.app.js:15336
runtime.js:92 Uncaught (in promise) Error: Manifest request to /_nuxt/e12a06ad6b43baad4b84.hot-update.json timed out.
    at XMLHttpRequest.request.onreadystatechange (runtime.js:92)

Please add a repository or CodeSandbox that clearly shows the problem.

@manniL the issue went away when I cleared all cookies, local storage and other "stuff" in chrome dev tools. So, I cant reproduce this anymore...but I know this problem was there and it happened on doing a "npm update". I defer to you on what you want to do next.

The problem happes when you run your production version on localhost:300 with pwa/workbox enabled and then run dev on same port without unregister service worker.
This is a long known issue which happens for webpack HMR already registered workbox.

Interesting @pi0 thanks for the extra color here.
So is the lesson that we should NOT run a production version (do a npm run build && npm run start) on localhost:3000 with pwa enabled?
Still seems like an issue in Nuxt, correct? Worth keeping the issue open or is it a duplicate?
As an aside, I'm seeing another intermittent issue on running "npm run dev' where the pages dont load. In that case I have to stop the terminal and run "npm run dev" again. That usually fixes it, but it's a minor annoyance.

This issue is directly related to HMR and Workbox. However, there was an open issue in pwa repository. I think for waiting for a workaround we may open an issue there or mention this as a known issue in the docs. Not really related to nuxt core.

As an aside, I'm seeing another intermittent issue on running "npm run dev' where the pages don't load.

Is this happening even without workbox being registered? A reproduction would be awesome. The #6186 should also potentially fix it for 2.9. you can early test it using nuxt-edge.

@pi0 sounds good and makes sense to keep the PWA one open.
This 2nd issue:
 intermittent issue on running "npm run dev' where the pages don't load.
has been happening since as far as I can remember, I can't think of the patterns when it triggers but I'll keep an eye out for it. I had never heard of workbox until this issue was reported yesterday...so no changes there from the basic nuxt installation.
Is it recommended we use Nuxt-edge or is there a way to try out 3.0 beta? Don't see a tag here for it.

@connecteev there is no nuxt 3 beta out yet. nuxt-edge is recommended for personal or projects with a small team working on. All nighly releases are fully automated tested but there might not be a proper changelog and integration tets.

@pi0 cool. Will nuxt-edge become the nuxt-3 beta and eventually nuxt 3?
I did a npm install nuxt-edge
Does one need both of these in package.json for nuxt-edge?
     "nuxt": "^2.0.0",
    "nuxt-edge": "^2.9.0-26089340.de7ed24b",

or only the latter is enough and can I remove the first line? Btw, I couldn't find any good, official information on nuxt-edge from googling around. Is there a guide / more information on nuxt-edge and what is included. Thanks.

Will nuxt-edge become the nuxt-3 beta and eventually nuxt 3?

Not exactly. It is a preview of all next release. Currently 2.9. And only nuxt-edge should be listed.

@pi0 got it. I just tried a nuxt-edge installation and it keeps squawking about one error after another...not sure what I am missing or whether this just isnt ready for prime time yet.

> nuxt --port 3000

   ╭─────────────────────────────────────────────╮
   │                                             │
   │   Nuxt.js v2.9.0-26089340.de7ed24b          │
   │   Running in development mode (universal)   │
   │                                             │
   │   Listening on: http://localhost:3000/      │
   │                                             │
   ╰─────────────────────────────────────────────╯

 ERROR  Cannot import module '@nuxt/webpack-edge'                                                                                12:09:57

  at _import (node_modules/nuxt-edge/node_modules/@nuxt/cli-edge/dist/cli-command.js:75:17)
  at process._tickCallback (internal/process/next_tick.js:68:7)

$ npm install @nuxt/webpack-edge
npm WARN deprecated<EMAIL_ADDRESS>I wrote this module a very long time ago; you should use something else.
npm WARN<EMAIL_ADDRESS>requires a peer of eslint@>= 5.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.

+<EMAIL_ADDRESS>added 9 packages from 40 contributors, removed 21 packages, updated 14 packages, moved 44 packages and audited 22823 packages in 29.953s
found 0 vulnerabilities

OneStepAtATime:kb_frontend_nuxt kunalpunjabi$ npm run dev

> nuxt --port 3000

   ╭─────────────────────────────────────────────╮
   │                                             │
   │   Nuxt.js v2.9.0-26089340.de7ed24b          │
   │   Running in development mode (universal)   │
   │                                             │
   │   Listening on: http://localhost:3000/      │
   │                                             │
   ╰─────────────────────────────────────────────╯

ℹ Preparing project for development                                                                                12:11:01
ℹ Initial build may take a while                                                                                12:11:01

 FATAL  Cannot find module 'vue-meta/package.json'                                                                                12:11:01

  at Function.Module._resolveFilename (internal/modules/cjs/loader.js:636:15)
  at Function.Module._load (internal/modules/cjs/loader.js:562:25)
  at Module.require (internal/modules/cjs/loader.js:690:17)
  at require (internal/modules/cjs/helpers.js:25:18)
  at Resolver.requireModule (node_modules/@nuxt/core-edge/dist/core.js:629:26)
  at Builder.validateTemplate (node_modules/@nuxt/builder-edge/dist/builder.js:5630:38)
  at Builder.build (node_modules/@nuxt/builder-edge/dist/builder.js:5564:12)

   ╭───────────────────────────────────────────────────────╮
   │                                                       │
   │   ✖ Nuxt Fatal Error                                  │
   │                                                       │
   │   Error: Cannot find module 'vue-meta/package.json'   │
   │                                                       │
   ╰───────────────────────────────────────────────────────╯

There might be something wrong with npm/yarn. Try cleaning node_modules and lock file.

@pi0 Great thanks...that worked. Glad that my site still works with the latest and greatest version of nuxt.
While there are some glitches we encountered in this ticket, I have no issues right now. I'll come back to update this issue if I see anything is odd.

This is not an issue anymore

Faced the same issue today. Issue seems to do with websockets and their availability. After restarting the system, it worked fine.

Same problem again today !

今天又遇到同样的问题！

Same problem here too.
Been having a lot of problem with nuxt in the past but not being able to hot-reload is a pretty big buzzkill.

我后面发现出现热跟新失败的原因
我猜测是因为和电脑cpu只有两个内核, 当我开第三个网页的时候就会出现热更新失败的现象
这只是我的猜测

The problem happes when you run your production version on localhost:300 with pwa/workbox enabled and then run dev on same port without unregister service worker.
This is a long known issue which happens for webpack HMR already registered workbox.

Thank you very much for the answer. Quoting your reply because it hasn't got enough attention.

The problem happes when you run your production version on localhost:300 with pwa/workbox enabled and then run dev on same port without unregister service worker.

Thank you. changed the port number. now it's working without any issue

Stopping the service worker via devtools fixes it for me, but it still locks up periodically. Stopping the SW seems to unlock it again.

我后面发现出现热跟新失败的原因
我猜测是因为和电脑cpu只有两个内核, 当我开第三个网页的时候就会出现热更新失败的现象, 一直保持两个页面就不会出现这种现象
这只是我的猜测

确实是这个问题。。。但是我电脑是8核的。。。也是开三个就热更卡死

我 后面 发现 出现 热 跟 新 失败 的 原因
P 猜测 是 因为 和 电脑 电脑 内核 内核 内核 内核 当 当 当 当 的 的 的 的 的 的 的 的 直 直 直 直 直 直 直 直 直
直 我

确实 是 这个 问题 ... 但是 我 电脑 是 8 核 的 ... 也是 开 三个 就 热 更 卡 死

Спасибо

Deleting and Unregistering the service worker did the fix for me. Please see the photo below

Hopefully these workarounds are temporary and the nuxt team looks into the stability issues....not good if this happens to production users.

Hopefully these workarounds are temporary and the nuxt team looks into the stability issues....not good if this happens to production users.

This issue has never happened in prod so far. The reason, as well as a workaround, is also known. There is nothing to worry about in production environments!

The problem happes when you run your production version on localhost:300 with pwa/workbox enabled and then run dev on same port without unregister service worker.
This is a long known issue which happens for webpack HMR already registered workbox.

Hopefully these workarounds are temporary and the nuxt team looks into the stability issues....not good if this happens to production users.

I agree with @manniL. This will only happen in local as well. You need to have both dev and prod environment with the same URL and port for this to happen.

warn [HMR] Update check failed: Error: Manifest request to/_nuxt/e12a06ad6b43baad4b84.hot-update.json timed out

i have the same problem when i run dev with NODE_ENV=production, delete Cache Storage in browser an then run dev width NODE_ENV=development

I'm changing port in package.json and  .env file
ex: http://localhost:3000/ to http://localhost:3001/
It's works

。您需要拥有具有相同 URL 和端口的 dev 和

I don't quite understand. Would you please tell me in detail

Hello,
I've change the port http://localhost:3000 to http://localhost:8000.
It was working for a few seconds and now it not working again.

I noticed that for me, only on chrome, but localhost will have those nuxt timeout issue with "Manifest request to /_nuxt/5d8bf94471479c1c5ddc.hot-update.json timed out." but it goes away if I replace localhost with <IP_ADDRESS>, I don't know much about those loopback interface not sure why this is the case only for chrome.

I have the same error by replacing localhost with <IP_ADDRESS>, or not. For now it's work (with <IP_ADDRESS>) but given that I still have the error, I think that it's going to start again. I have not the error on Chrome (just on Safari) but on Chrome sometimes it's was not working.

That's it, it starts again...

nuxt2，只打开了一个页面，然后刷新一下就一直显示在加载中了。也一直都加载不出来，请问怎么处理啊？这个问题

I have a similar problem, my Nuxt v2.17.1 project, when I open it from Chrome it stays loading (load spinner appears), and it takes 3-15 seconds to fully load the app. I have SSR disabled. In incognito and guest mode this does not happen or in other browsers. It is worth mentioning that I have no extensions installed. I tried over and over again clearing cache and all browser data but the same thing keeps happening.
My version of Node.js v16.16.0
In fact, I create a whole new project from scratch and the same thing happens: I get the Loading spinner.
I have uninstalled and reinstalled Chrome several times from scratch (even older versions), I have even removed the keys that the browser generates in regedit but the problem persists.
In my nuxt.config.js I set the load value to 'false' and it still shows up.
I tried on another computer and the load is immediate, the spinner is not shown. So this "error" is kind of weird.
I tried changing the localhost port and nothing.
I tried with Postman and the response is immediate, the only drawback is with Chrome.


feat(l10n): add zh-HANS

Thanks for this - you got in just in time, as I'm about to open up proper localization in CrowdIn.
I'll merge this in in a little bit and then upload it to the CrowdIn project for future updates (and there are some more strings coming shortly).


Fix typo

Target Live Date: 2019-03-11

[x] This has been reviewed and approved by (@samthor )
[x] I have run npm test locally and all tests pass.
[x] I have added the appropriate type-something label.
[x] I've staged the site and manually verified that my content displays correctly.

CC: @petele

Whoops!
There were 11 warnings that will prevent this PR from being merged. Please take a look, and either fix, or provide a justification for why they can't be fixed.
WARNINGS
src/content/en/updates/2019/03/kv-storage.md#L173 - '


Node.js  Loaders Team Meeting 2022-05-24

Time
UTC Tue 24-May-2022 18:00 (06:00 PM):

Timezone
Date/Time

US / Pacific
Tue 24-May-2022 11:00 (11:00 AM)

US / Mountain
Tue 24-May-2022 12:00 (12:00 PM)

US / Central
Tue 24-May-2022 13:00 (01:00 PM)

US / Eastern
Tue 24-May-2022 14:00 (02:00 PM)

EU / Western
Tue 24-May-2022 19:00 (07:00 PM)

EU / Central
Tue 24-May-2022 20:00 (08:00 PM)

EU / Eastern
Tue 24-May-2022 21:00 (09:00 PM)

Moscow
Tue 24-May-2022 21:00 (09:00 PM)

Chennai
Tue 24-May-2022 23:30 (11:30 PM)

Hangzhou
Wed 25-May-2022 02:00 (02:00 AM)

Tokyo
Wed 25-May-2022 03:00 (03:00 AM)

Sydney
Wed 25-May-2022 04:00 (04:00 AM)

Or in your local time:

https://www.timeanddate.com/worldclock/fixedtime.html?msg=Node.js+Foundation+Loaders Team+Meeting+2022-05-24&iso=20220524T1800
or https://www.wolframalpha.com/input/?i=06PM+UTC%2C+May+24%2C+2022+in+local+time

Links

Minutes Google Doc: https://docs.google.com/document/d/1roPk2QBwplO3_QpPE7xJ4FhIZAe5mVsmtPxzBjz8lfE/edit

Agenda
Extracted from loaders-agenda labelled issues and pull requests from the nodejs org prior to the meeting.
Invited

Loaders team: @nodejs/loaders

Observers/Guests
Notes
The agenda comes from issues labelled with loaders-agenda across all of the repositories in the nodejs org. Please label any additional issues that should be on the agenda before the meeting starts.
Joining the meeting

link for participants: https://zoom.us/j/97506450082

For those who just want to watch: https://www.youtube.com/c/nodejs+foundation/live

No agenda and it looks like @JakobJingleheimer can’t attend, so I think I’ll cancel this one unless anyone objects. There’s progress being made in open PRs.


Revert "fixes #52 - update user permissions on artifacts in production docker…"

Reverts networknt/light-oauth2#67

Both changes are cherry-picked into master and develop. Thanks.


An error when run 4dface app

I did the steps as you say in readme.md , and my system is ubuntu 14.04 , but when I run the 4dface app ,it occurs ## "terminate called after throwing an instance of 'std::runtime_error' what():  Error opening given file: ../share/sfm_shape_3448.bin
已放弃 (核心已转储)"
How can I solve the problem ?

The error says that the file ../share/sfm_shape_3448.bin couldn't be found. I think you most likely didn't run the install target. It copies the model files to the install directory, so they will be automatically found by the executable. Either run the install target, or just specify the model file with -m path-to-model - you probably also need to specify all the other files needed, so running the install target would be easier since it copies everything to the correct place.

I'll close this, since it was simply a matter of not passing the correct path to the model file on the command-line.


Add class for centering justified text

I have come across use cases where you might want to center justified texts for improved design. I would like to propose a new class, .text-justify-center, which centers the last line of justified text. Most browsers support this feature except for Safari. If the browser does not support it, this class simply makes the text justified as .text-justify does. Below is the implementation:
.text-justify-center {
  text-align: justify !important;
  text-align-last: center !important;
}

I would like to start contributing to bootstrap. I would like to start with this issue. Do I need to assign this issue to myself?

It's not possible to set users not in the Collaborators group as assignees on GitHub unfortunately. But feel free to make a pull request for this regardless. Although I'm not sure what @mdo's opinion is on this feature, so don't feel bad if the PR gets declined. Or you may wish to choose a different issue.

Thanks, but we'll pass on this utility for now.


add variational dropout to gluon ptb example

changes:

remove the download shell script
add cell api usage to the model
add variational dropout when using cell (requires #7067)

@yzhang87 yes, reset is indeed called automatically. Removed. Thanks!

The word language model is intended to be a simple example, not a SOTA solution. I'm not sure we should keep adding more stuff to it.

This is intended also as an example for using cell API, which we currently lack.

I think its better to use another example to introduce the cell API.
For example we can add an attention example

OK


Improved ExecuteRule output

An information messagebox isn't good enough
YARA output on a successful rule detection is like this:
${Rulename} ${Target filename}

Gonna put a hold on this. When I merge windows -> master I'm gonna strip out the ExecuteRule stuff and focus on releasing the compilation stuff

This function was removed from the script. Closing


[Bug]: BRPT3SHBM:The unit muzzle does not rotate with the turret of the upper body

What happened?
There seems to be a problem with one unit model in TOTALMAYHEM. The unit's muzzle position does not move as the turret rotates, causing the laser to shoot from the wrong position when the turret rotates

Steps to reproduce
Have this unit fire to the left, right, and right, and you'll see problems with the laser beam and the muzzle.
Expected behavior
I have fixed this problem by editing the scm file. But I don't know how to operate PR on github. That's why I sent the file I fixed here. If there is no p
BRPT3SHBM_lod0.zip
roblem after anyone checks, he can directly adopt.

fixed in https://github.com/FAForever/fa-total-mayhem/pull/27


Update Readme.md to add fullgroup explanation

This is a follow-up to #219 to add a short description on how to use the fullgroup variable.

:heavy_check_mark: :bow:


irmin-unix: Update Irmin_unix.Resolver.Store.create to use hash argument

Fixes #1636

Thanks! Can you rebase over upstream/main? The CI wants a recent fix to deps.


Fix SPI mode and bit order settings

#12
The logical not in this line makes the mask 0 and wipes out the earlier settings. This should be a bitwise not, but even so the 0xFF would also mask off the SSLA bits b6-b4 and half of the SPB bits b9-b8. Changing 0xFF to 3 will clear just the BRDV bits b3-b2.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

I verified the fix using an ADXL345, and it works!
Thanks.

Thank you so much for the fix!


Upgrade to Java 20

Generate Docker images that run on a Java 20 JVM to take advantage of recent
performance improvements and bugfixes.
Currently, the Kotlin compiler only supports generating classfiles for JVM
versions up to 19, so configure the target classfile version separately from the
version of the JVM itself.
To make it easier to switch versions in the future, start using Gradle's Java
toolchain support to automatically install an appropriate JVM version.
A couple of Java standard library functions have been deprecated in recent
releases; update our uses of them to use the non-deprecated alternatives.

Current dependencies on/for this PR:

main

PR #1086

PR #1087

PR #1092   👈

This comment was auto-generated by Graphite.

Not sure what's going on with the failures on this one. I'm not able to reproduce any of these errors in my dev environment.


Question: It is possible to continue with a lane if something in it fails?

Is it possible to configure a lane as such that some action are anticipated to fail sometimes, and if they fail to still continue?
For example, if a lane requires a network connection, but somehow the network is out. If that part fails, still continue with all the other things the lane does.
lane :create_test_release do
  download_new_strings_files_and_replace_old_ones # <-- might fail, but isn't critical
  gym
  hockeyapp
end

You could perhaps implement something in before_all and then use that to do your online abilities, then put your offline ones in a different lane. Do you have en example of the actions you're triggering?
before_all do
    update_fastlane
end

The fictitious example pretty much sums it up. The plugin in question is poeditor_export.
The person in charge of building didn't like it for the automated builds, because it relies on a network connection that might fail due to no fault of our own. So, being able to fail gracefully would help put this into the automated builds as well.
Putting the online things in before_all wouldn't work, since if it fails there, the lane still stops completely.
Only thing I can come up with is adding a MIGHT_FAIL environment variable in each lane that uses actions that are expected to fail sometimes. Then you can check for that environment variable in error. But that kills using error for actual cleanup. Also, if you can call lanes from there, you shouldn't really.

I'd say your build status should be somewhat disconnected from any network-based activity shouldn't it?
Run a :test lane to do your acceptance testing, and another lane to handle any CI deployment? Run it as two tasks in your build system. If :test fails, then don't try and deploy the build. If it passes, try and deploy it? Or is your setup more complex?

Yeah, you can use Ruby for that
lane :yolo do
  cocoapods
  begin
     something_that_might_fail
   rescue => ex
     UI.error("Something went wrong: #{ex}")
   end
   deliver
end


rework transcode plugin

The transcode plugin has certain limitations at the moment:

Some player controls like play/pause/seek don't work while transcoding
There is no playlist support

Improvements that could be made:

Instead of transcoding on the fly and piping the output directly as HTTP response to the user the output should be piped into an temp file which acts as some sort of buffer. While the transcoding is in progress the temp file can be piped to the user as HTTP response. This way play/pause/seek should work again.
The temp files could be deleted on process.end().
Don't know if this is too much magic: Instead of the --tomp4 option files could get transcoded based on the file extensions. For example .avi and .mkv would be transcoded but not .mp4 or .mp3. This way we should also be able to create playlists with files which need transcoding.
Users should get an error message displayed if they try to transcode a file but don't have ffmpeg installed.

Related discussions
https://github.com/xat/castnow/issues/58

OK, there are a simple bin of ffmpeg (avconv) that can give all information about a media file: ffprobe (or avprobe, at the newest versions). There are node.js modules to parse the ffprobe information in a json file, but get that informations is a quite simples task even without this modules.
About how videostrem does what it does, i suspect they use some type of FIFO (first in first out file, or named pipe on unix SOs) to handle wiht play/pause situations, becouse sekking IMO is a simple question of restart the trasnconding process at the new point of video file (maybe with -ss on ffmprg).

@kriptolix:

About how videostrem does what it does, i suspect they use some type of FIFO (first in first out file, or named pipe on unix SOs) to handle wiht play/pause situations, becouse sekking IMO is a simple question of restart the trasnconding process at the new point of video file (maybe with -ss on ffmprg) explaining why.

I don't expect seeking to work like that with the -ss option. See my comment here and also another comment here.

"Using the -ss option doesn't output byte range of the original file, it creates a new file with a different byte stream entirely"
Yes @parshap, it's right, but I believe that is exactly what happen with videostream, a new request of a the new transcoding output ("new file") using the current session, only the transition is too fast and smooth to be noted. Play/Pause with this logic also is possible, just saving the current point of video file e restarting the transcode by this.
ps: I am novice in the trasconding chromecast world, so excuse if my theory not make sense, I could not try this yet.


ImportError: No module named api

I've installed it using pip python-amazon-simple-product-api

I have the same issue. Did you solve the problem?

Same issue here, any luck?


destroy

Ran Plan for dir: . workspace: default
Plan Error
Show Output
running "/home/codespace/.asdf/shims/terraform plan -input=false -refresh -out \"/home/codespace/.atlantis/repos/samgabrail/env0-atlantis-gcp/16/default/default.tfplan\"" in "/home/codespace/.atlantis/repos/samgabrail/env0-atlantis-gcp/16/default": exit status 1
╷
│ Error: Reference to undeclared resource
│
│   on outputs.tf line 2, in output "instance_id":
│    2:   value = google_compute_instance.default.instance_id
│
│ A managed resource "google_compute_instance" "default" has not been
│ declared in the root module.
╵
╷
│ Error: Reference to undeclared resource
│
│   on outputs.tf line 6, in output "public_ip":
│    6:   value = google_compute_instance.default.network_interface[0].access_config[0].nat_ip
│
│ A managed resource "google_compute_instance" "default" has not been
│ declared in the root module.
╵

Ran Plan for dir: . workspace: default
Show Output
google_compute_instance.default: Refreshing state... [id=projects/terraformprojects-365816/zones/us-central1-a/instances/atlantis-vm-dev]

Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
- destroy

Terraform will perform the following actions:

  # google_compute_instance.default will be destroyed
  # (because google_compute_instance.default is not in configuration)
- resource "google_compute_instance" "default" {
      - can_ip_forward       = false -> null
      - cpu_platform         = "Intel Broadwell" -> null
      - current_status       = "RUNNING" -> null
      - deletion_protection  = false -> null
      - enable_display       = false -> null
      - guest_accelerator    = [] -> null
      - id                   = "projects/terraformprojects-365816/zones/us-central1-a/instances/atlantis-vm-dev" -> null
      - instance_id          = "2979553188716095310" -> null
      - label_fingerprint    = "42WmSpB8rSM=" -> null
      - labels               = {} -> null
      - machine_type         = "e2-micro" -> null
      - metadata             = {} -> null
      - metadata_fingerprint = "OunhsVn_J1I=" -> null
      - name                 = "atlantis-vm-dev" -> null
      - project              = "terraformprojects-365816" -> null
      - resource_policies    = [] -> null
      - self_link            = "https://www.googleapis.com/compute/v1/projects/terraformprojects-365816/zones/us-central1-a/instances/atlantis-vm-dev" -> null
      - tags                 = [
          - "dev",
          - "engineering",
        ] -> null
      - tags_fingerprint     = "x7YZUfmdF48=" -> null
      - zone                 = "us-central1-a" -> null

      - boot_disk {
          - auto_delete = true -> null
          - device_name = "persistent-disk-0" -> null
          - mode        = "READ_WRITE" -> null
          - source      = "https://www.googleapis.com/compute/v1/projects/terraformprojects-365816/zones/us-central1-a/disks/atlantis-vm-dev" -> null

          - initialize_params {
              - image  = "https://www.googleapis.com/compute/v1/projects/ubuntu-os-cloud/global/images/ubuntu-2204-jammy-v20221014" -> null
              - labels = {
                  - "env" = "dev"
                } -> null
              - size   = 10 -> null
              - type   = "pd-standard" -> null
            }
        }

      - network_interface {
          - name               = "nic0" -> null
          - network            = "https://www.googleapis.com/compute/v1/projects/terraformprojects-365816/global/networks/default" -> null
          - network_ip         = "<IP_ADDRESS>" -> null
          - queue_count        = 0 -> null
          - stack_type         = "IPV4_ONLY" -> null
          - subnetwork         = "https://www.googleapis.com/compute/v1/projects/terraformprojects-365816/regions/us-central1/subnetworks/default" -> null
          - subnetwork_project = "terraformprojects-365816" -> null

          - access_config {
              - nat_ip       = "<IP_ADDRESS>" -> null
              - network_tier = "PREMIUM" -> null
            }
        }

      - scheduling {
          - automatic_restart   = true -> null
          - min_node_cpus       = 0 -> null
          - on_host_maintenance = "MIGRATE" -> null
          - preemptible         = false -> null
          - provisioning_model  = "STANDARD" -> null
        }

      - shielded_instance_config {
          - enable_integrity_monitoring = true -> null
          - enable_secure_boot          = false -> null
          - enable_vtpm                 = true -> null
        }
    }

Plan: 0 to add, 0 to change, 1 to destroy.

Changes to Outputs:
- instance_id = "2979553188716095310" -> null
- public_ip   = "<IP_ADDRESS>" -> null

:arrow_forward: To apply this plan, comment:

atlantis apply -d .

:put_litter_in_its_place: To delete this plan click here
:repeat: To plan this project again, comment:

atlantis plan -d .

Plan: 0 to add, 0 to change, 1 to destroy.

:fast_forward: To apply all unapplied plans from this pull request, comment:

atlantis apply

:put_litter_in_its_place: To delete all plans and locks for the PR, comment:

atlantis unlock

Error: Running atlantis apply is disabled.

Ran Apply for dir: . workspace: default
google_compute_instance.default: Destroying... [id=projects/terraformprojects-365816/zones/us-central1-a/instances/atlantis-vm-dev]
google_compute_instance.default: Still destroying... [id=projects/terraformprojects-365816/zones/us-central1-a/instances/atlantis-vm-dev, 10s elapsed]
google_compute_instance.default: Still destroying... [id=projects/terraformprojects-365816/zones/us-central1-a/instances/atlantis-vm-dev, 20s elapsed]
google_compute_instance.default: Still destroying... [id=projects/terraformprojects-365816/zones/us-central1-a/instances/atlantis-vm-dev, 30s elapsed]
google_compute_instance.default: Still destroying... [id=projects/terraformprojects-365816/zones/us-central1-a/instances/atlantis-vm-dev, 40s elapsed]
google_compute_instance.default: Still destroying... [id=projects/terraformprojects-365816/zones/us-central1-a/instances/atlantis-vm-dev, 50s elapsed]
google_compute_instance.default: Destruction complete after 51s

Apply complete! Resources: 0 added, 0 changed, 1 destroyed.

Locks and plans deleted for the projects and workspaces modified in this pull request:

dir: . workspace: default


Cannot connect to host eu-api.coolkit.cc:8080

2021-12-13 20:01:44 WARNING (MainThread) [homeassistant.setup] Setup of sonoff is taking over 10 seconds.
2021-12-13 20:02:07 ERROR (MainThread) [custom_components.sonoff.sonoff_cloud] Coolkit API error: Cannot connect to host eu-api.coolkit.cc:8080 ssl:default [Connect call failed ('<IP_ADDRESS>', 8080)]
Traceback (most recent call last):
File "/usr/local/lib/python3.9/site-packages/aiohttp/connector.py", line 969, in _wrap_create_connection
return await self._loop.create_connection(*args, **kwargs) # type: ignore # noqa
File "/usr/local/lib/python3.9/asyncio/base_events.py", line 1056, in create_connection
raise exceptions[0]
File "/usr/local/lib/python3.9/asyncio/base_events.py", line 1041, in create_connection
sock = await self._connect_sock(
File "/usr/local/lib/python3.9/asyncio/base_events.py", line 955, in _connect_sock
await self.sock_connect(sock, address)
File "/usr/local/lib/python3.9/asyncio/selector_events.py", line 502, in sock_connect
return await fut
File "/usr/local/lib/python3.9/asyncio/selector_events.py", line 537, in _sock_connect_cb
raise OSError(err, f'Connect call failed {address}')
TimeoutError: [Errno 110] Connect call failed ('<IP_ADDRESS>', 8080)
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/config/custom_components/sonoff/sonoff_cloud.py", line 148, in _api
r = await coro
File "/usr/local/lib/python3.9/site-packages/aiohttp/client.py", line 520, in _request
conn = await self._connector.connect(
File "/usr/local/lib/python3.9/site-packages/aiohttp/connector.py", line 535, in connect
proto = await self._create_connection(req, traces, timeout)
File "/usr/local/lib/python3.9/site-packages/aiohttp/connector.py", line 892, in _create_connection
_, proto = await self._create_direct_connection(req, traces, timeout)
File "/usr/local/lib/python3.9/site-packages/aiohttp/connector.py", line 1051, in _create_direct_connection
raise last_exc
File "/usr/local/lib/python3.9/site-packages/aiohttp/connector.py", line 1020, in _create_direct_connection
transp, proto = await self._wrap_create_connection(
File "/usr/local/lib/python3.9/site-packages/aiohttp/connector.py", line 975, in _wrap_create_connection
raise client_error(req.connection_key, exc) from exc
aiohttp.client_exceptions.ClientConnectorError: Cannot connect to host eu-api.coolkit.cc:8080 ssl:default [Connect call failed ('<IP_ADDRESS>', 8080)]
2021-12-13 20:02:07 ERROR (MainThread) [custom_components.sonoff.sonoff_cloud] Login error: None
2021-12-13 20:02:07 WARNING (MainThread) [custom_components.sonoff] Can't connect to eWeLink Cloud

I have the same issue. I can't ping eu-api.coolkit.cc. I can ping cn-api.coolkit.cc. How do you set your region? I tried api_region

@DJ-L1GhTeR if you change line 104 in custom_components/sonoff/sonoff_cloud.py from  _baseurl = 'https://eu-api.coolkit.cc:8080/ to  _baseurl = 'https://us-api.coolkit.cc:8080/ it connects.

Check new beta-version:
https://github.com/AlexxIT/SonoffLAN/releases
It using new ewelink cloud API

Having the same issue. Not working on v.3.3.1 and against master (as of 09/11/2022).

@sm0ke21 you have not same issue. You already using new API.


KAFKA-4564: Add system test for pre-0.10 brokers

https://jenkins.confluent.io/job/system-test-kafka-branch-builder-2/255/

Call for review @enothereska @dguy

LGTM

Updated this.

Call for final review and merging @guozhangwang

retest this please


org-journal TODOs in org-agenda-list for today

I've started using org-journal and find it very useful. I keep a running bunch of TODOs in it that carry over from day to day. They also show up in org-todo-list thanks to the tips in the README. But I would also like them to show up in the org-agenda-list for the current day. Any tips on that?

I don't use org-agenda-list, sorry.

@bon The task need a timestamp (scheduled, deadline or active timestamp) to show up in org-agenda-list. Also check if you really have set org-journal-enable-agenda-integration to t.


operationId not correct case

I specified @operationId("WorkloadNetworks_GetVMGroup"), but it is showing up as WorkloadNetworks_GetVmGroup in OpenAPI output. This is from https://github.com/Azure/azure-rest-api-specs-pr/pull/15631 .

The routes.tsp contains:
@armResourceOperations
interface WorkloadNetworkVmGroups {
  #suppress "@azure-tools/typespec-azure-core/no-operation-id" "Can not change existing operationId."
  @operationId("WorkloadNetworks_ListVMGroups")
  list is ArmResourceListByParent<WorkloadNetworkVMGroup>;

  #suppress "@azure-tools/typespec-azure-core/no-operation-id" "Can not change existing operationId."
  @operationId("WorkloadNetworks_GetVMGroup")
  get is ArmResourceRead<WorkloadNetworkVMGroup>;

  #suppress "@azure-tools/typespec-azure-core/no-operation-id" "Can not change existing operationId."
  @operationId("WorkloadNetworks_CreateVMGroup")
  create is ArmResourceCreateOrUpdateAsync<WorkloadNetworkVMGroup>;

  #suppress "@azure-tools/typespec-azure-core/no-operation-id" "Can not change existing operationId."
  @operationId("WorkloadNetworks_UpdateVMGroup")
  update is ArmResourcePatchAsync<
    WorkloadNetworkVMGroup,
    WorkloadNetworkVMGroupProperties
  >;

  #suppress "@azure-tools/typespec-azure-core/no-operation-id" "Can not change existing operationId."
  @operationId("WorkloadNetworks_DeleteVMGroup")
  delete is ArmResourceDeleteAsync<WorkloadNetworkVMGroup>;
}

Are those issues for the autorest emitter or openapi3?

Using the autorest emitter. https://github.com/Azure/azure-rest-api-specs-pr/pull/15631/files#r1376530388

Just for later reference, the autorest emitter is in our azure repository https://github.com/Azure/typespec-azure, GitHub unfortunately doesn't let us move issues across orgs.

Moved to https://github.com/Azure/typespec-azure/issues/3794.


Bump curl from 7.48 to 7.59 in dcos 1.9

High-level description
This PR bumps curl from 17.48 to 7.59.0 in 1.9
Corresponding DC/OS tickets (obligatory)
These DC/OS JIRA ticket(s) must be updated (ideally closed) in the moment this PR lands:
https://jira.mesosphere.com/browse/DCOS-21557
Checklist for all PRs

[x] Read the DC/OS contributing guidelines
[x] Followed relevant code rules Rules for Packages and Systemd

@mesosphere-mergebot label Ready For Review

@mesosphere-mergebot bump-ee

@mesosphere-mergebot bump-ee

@mesosphere-mergebot label Work In Progress

@mesosphere-mergebot bump-ee

@mesosphere-mergebot bump-ee

Closing this PR in favour of https://github.com/dcos/dcos/pull/2757


proposal benjamin 12-10-2022

Hey Benjamin, thanks for the proposal. The work you’ve done in JBM is greatly appreciated!
However, I am going to have to vote against this proposal at this time. I don’t think that 5-6 hours is enough of a time commitment to continually generate meaningful commits to the JBM application.
I feel that in order to provide the ability for this to be meaningful, we would need a collectively bigger attempt at detailing bug and small feature fixes to allow a strong async relationship with someone on a small hourly window, which I am unsure can be provided at this time.
With that said, I could definitely support a commitment of around 25-30 hours. I think what Peel really needs from a supporting part time role at the moment is someone to own the communications from the Juicebox #bugs channel in Discord.


Bug when exiting audio player when audio is playing

I know the audio player is experimental atm, I just thought I should mention this bug just to be safe. When using the audio player, if you return to the editor without stopping the music, then go back to the music player, you are unable to stop the music that is currently playing, and can have multiple songs playing at the same time.

Fixed in ce00a98 by having the music stop when leaving the Audio page. Thanks!


configuring blogkit-[source]

#27
suggest changing Request to (...config: any[]) => Request or another best practice in BlogkitConfig.request

duplicate #28
close


MergeStrategy does not work for duplicate META-INF/io.netty.versions.properties

no merge strategy works to eliminate this issue:
io.netty/netty-codec-http/jars/netty-codec-http-4.1.17.Final.jar:META-INF/io.netty.versions.properties
io.netty/netty-codec/jars/netty-codec-4.1.17.Final.jar:META-INF/io.netty.versions.properties
io.netty/netty-transport/jars/netty-transport-4.1.17.Final.jar:META-INF/io.netty.versions.properties
io.netty/netty-buffer/jars/netty-buffer-4.1.17.Final.jar:META-INF/io.netty.versions.properties
io.netty/netty-common/jars/netty-common-4.1.17.Final.jar:META-INF/io.netty.versions.properties
io.netty/netty-resolver/jars/netty-resolver-4.1.17.Final.jar:META-INF/io.netty.versions.properties
io.netty/netty-handler/jars/netty-handler-4.1.17.Final.jar:META-INF/io.netty.versions.properties

assemblyMergeStrategy in assembly := {
 case PathList("META-INF", "MANIFEST.MF") => MergeStrategy.discard
 case "META-INF/io.netty.versions.properties" => MergeStrategy.first
 case x => MergeStrategy.first
}

Was this resolved?

@nextdtinc what was the solution to this?

use:
case "META-INF/io.netty.versions.properties" => MergeStrategy.first
in sbt shell:
clean
reload

I have run into the same issue on windows but unluckily found this issue has been closed.
After spending some time on this, I think the correct solution is to replace the line
case "META-INF/io.netty.versions.properties" => MergeStrategy.first

with:
case PathList("META-INF", "io.netty.versions.properties") => MergeStrategy.first

Putting it together, it will be:
assemblyMergeStrategy in assembly := {
 case PathList("META-INF", "MANIFEST.MF") => MergeStrategy.discard
 case PathList("META-INF", "io.netty.versions.properties") => MergeStrategy.first
 case x => MergeStrategy.first
}

Does anyone know why this workaround is needed?

As a note for future seekers, the following is equivalent to the suggestion above, and worked to resolve the issue for me:
assemblyMergeStrategy in assembly := {
 case PathList("META-INF", "MANIFEST.MF") => MergeStrategy.discard
 case x => MergeStrategy.first
}


⚠ PrivateHD has degraded performance

In 5cf6e5f, PrivateHD ($PHD) experienced degraded performance:

HTTP code: 200
Response time: 1990 ms

Resolved: PrivateHD performance has improved in ab48f0d.


Add golang and psutil to all containers

Supporting BoringSSL build & new parallel testing

[x] ubuntu
[x] alpine
[x] debian
[x] centos7
[x] centos8

Golang postponed. Otherwise closed by #42


[#489] Update JS libraries to the latest

Addresses # 489
Description
This PR updates bots' dependency libraries to newer versions and remove the unnecessary ones, updates the yarn.lock file and excludes it from the Deploy pipeline.
Detailed Changes

Updated nodemon version to 2.0.15 for SimpleHostBot, WaterfallHostBot, EchoSkillBot and WaterfallSkillBot.
Updated yarn.lock file to represent these latest changes and prevent outdated versions.
Updated the Deploy pipeline for JavaScript bots to remove yarn.lock to prevent being misinterpreted with outdated dependencies' versions, since this pipeline can be tested against multiple BotBuilder versions.
Removed EchoSkillBot-v3 unnecessary dependencies.

Testing
The following image shows the Deploy pipeline continues working.

Promoted to https://github.com/microsoft/BotFramework-FunctionalTests/pull/491


feat: add new javascript quiz

Checklist:

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)

Closes #XXXXX

Congrats on another contribution to our repository. 🎉
We look forward to future contributions. 👍

Thanks a lot, @jdwilkin4


BodySite is subset of a transversal list.

This list should be completed in a new version of the document.

Hans De Keersmaecker suggests we should use the text field of the CodeableConcept.

WG: we will receive the list today.

updated in #205

documents by Geert Vandenhole:
NL_430000 - bericht - stv - v01r07.pdf
I-2022-27-soins de plaie(s) message 430000-FR.pdf

WG: Ask @PBACIN what will be the link between the new valueset for the Mycarenet Service.


Update create-synonym-transact-sql.md

Deleted "object_name" on line 45. The original syntax says that if you specify "server_name", you need to specify "object_name" twice.
Original syntax expanded to several rows:
[
server_name.[ database_name ] . [ schema_name_2 ]. object_name
|
database_name . [ schema_name_2 ].
|
schema_name_2.
] object_name

@JediSQL : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#label:"aq-pr-triaged"

Nice catch @JediSQL, this does indeed appear to be an issue in the syntax.  After the updated article is published, GitHub will list you as an article contributor.
Thanks again for this feedback, your suggestions help improve our documentation.