"ERROR: Sign in to confirm your age" on YouTube

Checklist

[x] I'm reporting a broken site support
[x] I've verified that I'm running youtube-dl version 2021.06.06
[x] I've checked that all provided URLs are alive and playable in a browser
[x] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[x] I've searched the bugtracker for similar issues including closed ones

Verbose log

$ youtube-dl -v 'https://www.youtube.com/watch?v=zgqz8Je7P0s'
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['-v', 'https://www.youtube.com/watch?v=zgqz8Je7P0s']
[debug] Encodings: locale UTF-8, fs utf-8, out utf-8, pref UTF-8
[debug] youtube-dl version 2021.06.06
[debug] Python version 3.9.5 (CPython) - Linux-5.12.11-300.fc34.x86_64-x86_64-with-glibc2.33
[debug] exe versions: ffmpeg 4.4, ffprobe 4.4
[debug] Proxy map: {}
[youtube] zgqz8Je7P0s: Downloading webpage
[youtube] zgqz8Je7P0s: Refetching age-gated info webpage
WARNING: unable to download video info webpage: HTTP Error 404: Not Found
ERROR: Sign in to confirm your age
This video may be inappropriate for some users.
Traceback (most recent call last):
  File "/home/rg3/.local/lib/python3.9/site-packages/youtube_dl/YoutubeDL.py", line 815, in wrapper
    return func(self, *args, **kwargs)
  File "/home/rg3/.local/lib/python3.9/site-packages/youtube_dl/YoutubeDL.py", line 836, in __extract_info
    ie_result = ie.extract(url)
  File "/home/rg3/.local/lib/python3.9/site-packages/youtube_dl/extractor/common.py", line 534, in extract
    ie_result = self._real_extract(url)
  File "/home/rg3/.local/lib/python3.9/site-packages/youtube_dl/extractor/youtube.py", line 1713, in _real_extract
    raise ExtractorError(reason, expected=True)
youtube_dl.utils.ExtractorError: Sign in to confirm your age
This video may be inappropriate for some users.

Description

It seems like the "ERROR: Sign in to confirm your age" problem is unfortunately happening again with the latest version. However, using tools like NSFW YouTube in the browser the video is playable without signing in. Thanks in advance.

Fixed in master branch, but a new release was not made yet.

Fixed in master branch, but a new release was not made yet.

Ah, sorry. I should have tried that first. Just checked and it works, indeed. Thanks a lot for the tip.

Did it just break again? I installed the current master, a8035827177d6b59aca03bd717acb6a9bdd75ada, and I'm getting the same error.

Even am using VPN and able to see video (without filling forms) ,
Youtube-Dl can't download it (no matter i use in addition --geo-bypass)
D:\ffmpeg>youtube-dl https://www.youtube.com/watch?v=mFZc3GE830w
[youtube] mFZc3GE830w: Downloading webpage
[youtube] mFZc3GE830w: Refetching age-gated info webpage
WARNING: unable to download video info webpage: HTTP Error 404: Not Found
ERROR: Sign in to confirm your age
This video may be inappropriate for some users.

When can a new release (that fixes this) be expected? Last one was a month ago.

v2021.06.06
youtube-dl.exe -F QvvE0fvned0 [youtube] QvvE0fvned0: Downloading webpage [youtube] QvvE0fvned0: Refetching age-gated info webpage WARNING: unable to download video info webpage: HTTP Error 404: Not Found Traceback (most recent call last):   File "__main__.py", line 19, in <module>   File "youtube_dl\__init__.pyo", line 475, in main   File "youtube_dl\__init__.pyo", line 465, in _real_main   File "youtube_dl\YoutubeDL.pyo", line 2070, in download   File "youtube_dl\YoutubeDL.pyo", line 809, in extract_info   File "youtube_dl\YoutubeDL.pyo", line 816, in wrapper   File "youtube_dl\YoutubeDL.pyo", line 837, in __extract_info   File "youtube_dl\extractor\common.pyo", line 534, in extract   File "youtube_dl\extractor\youtube.pyo", line 1503, in _real_extract   File "youtube_dl\compat.pyo", line 2644, in compat_parse_qs   File "youtube_dl\compat.pyo", line 2614, in _parse_qsl AttributeError: 'bool' object has no attribute 'split'
2020.11.17
ydl.exe -F QvvE0fvned0 [youtube] QvvE0fvned0: Downloading webpage [youtube] QvvE0fvned0: Downloading embed webpage [youtube] QvvE0fvned0: Refetching age-gated info webpage [ERROR] ERROR: Sign in to confirm your age ERROR: Sign in to confirm your age

just got that error

I'd recommend switching to yt-dlp, which seems to generally be in better shape.

I'd recommend switching to yt-dlp, which seems to generally be in better shape.

Thanks ... I didn't knew about the fork ... it works perfectly at first try and it's way much faster !!!


Backward compat functional test

Based off #392.
This introduces a backward-compatibility functional test. For now it really is targeted at testing the DB migration from 0.3 to the upcoming 0.4, but the concept is also useful more generally to automatically test backward compatibility between our releases.

self-ACK 6cc4efd


Filter using regex is not returning any values

I am running a policy against EC2 resources with a filter to do a partial match on the Security Groups configured of the instances, to ensure a specific SG is configured for the instances:
policies:
  - name: ec2-sgs
    resource: ec2
    filters:
      - type: value
        key: "SecurityGroups[].GroupName"
        op: regex
        value: \S*NexposeScanTargetsSG\S*

I have four instances which should match on a groupname of Rapid7ScanEngineEC2Instance-NexposeScanTargetsSG-xxxxxxxxxxxxx.
Two with a single SG of that name and two where this SG is the second value in the key.
If use SecurityGroups[].GroupName or SecurityGroups[*].GroupName then there is no match but if use SecurityGroups[0].GroupName or SecurityGroups[1].GroupName then the two that match this item in the array are returned.
Is this right?
If I test using the following filter specifying the full SG value and 'contains' then returns all 4 instances
    filters:
      - type: value
        key: "SecurityGroups[].GroupName"
        op: contains
        value: "Rapid7ScanEngineEC2Instance-NexposeScanTargetsSG-xxxxxxxxxxxxx"

For info - I made this work by using the following filter
    filters:
        - type: security-group
          key: GroupName
          op: regex
          value: \S*NexposeScanTargetsSG\S*


Add OutputType to Get-Error cmdlet

PR Summary
Cmdlet was missing declaring OutputType which is ErrorRecord and Exception.  Added OutputType attribute.
PR Checklist

[x] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[x] Summarized changes
[x] Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
[x] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.

Breaking changes

[x] None
OR
[ ] Experimental feature(s) needed

[ ] Experimental feature name(s):

User-facing changes

[x] Not Applicable
OR
[ ] Documentation needed

[ ] Issue filed:

Testing - New and feature

[x] N/A or can only be tested interactively
OR
[ ] Make sure you've added a new test if existing tests do not effectively test the code changed

Tooling

[x] I have considered the user experience from a tooling perspective and don't believe tooling will be impacted.
OR
[ ] I have considered the user experience from a tooling perspective and enumerated concerns in the summary. This may include:

Impact on PowerShell Editor Services which is used in the PowerShell extension for VSCode (which runs in a different PS Host).
Impact on Completions (both in the console and in editors) - one of PowerShell's most powerful features.
Impact on PSScriptAnalyzer (which provides linting & formatting in the editor extensions).
Impact on EditorSyntax (which provides syntax highlighting with in VSCode, GitHub, and many other editors).

@PoshChan please retry windows

@SteveL-MSFT, successfully started retry of PowerShell-CI-Windows

@PoshChan please retry static

@SteveL-MSFT, successfully started retry of PowerShell-CI-static-analysis

@JamesWTruher can you point out where exactly is the typo you are referring to?

@JamesWTruher can you point out where exactly is the typo you are referring to?

@SteveL-MSFT Do you want to get approve from anybody?

@JamesWTruher can you review?

Up.


Incorrect agent result

Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; Clarsentia)
We have a site with several sub-sites.  This bot clicked on every ad on each sub-site (ignoring rel=nofollow).  It did not fetch robots.txt either.

Good catch. Fancy submitting a PR?

Fixed in #213


[REQ] Support specifying font-size for placeholder_text/fail_text

Currently, it seems that there's no way to set the font-size of placeholder_text / fail_text in input-field. Instead, it seems to just be based off of the height of the input-field specified in size.
This might be a good choice for people who don't use hide_input, however most people who have hide_input = false will likely want to use a pretty big height in the size. That then leads to the text being really big, which doesn't look good.
It'd be nice to have a way to override this behavior and manually specify a font-size for this text, leaving the height-based calculation only as a default fallback.

https://docs.gtk.org/Pango/pango_markup.html#the-span-attributes

Fair, but why do labels have a font_size attribute then? I suppose it's just for convenience, perhaps the same convenience would be nice to have here too?

no, pango markup


provide popover frame through props

@roubkar Hey, thanks for the contribution. But I'm a little lost about exactly what you're trying to do. Can you clarify? Thanks!

@jasonkuhrt Hey, sorry for the mess, Firstly I added ability to pass a reference for element which should be popover-s parent frame, last two commits are for React 16 compatibility, but I removed the parent frame logic during last commits. Sorry for taking your time.


chore: improve commitlint experience when not using commitizen

PR Type

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no API changes)
[ ] Build-related changes
[X] CI-related changes
[ ] Documentation content changes
[ ] Application / infrastructure changes
[x] Other: Commit Linter
What Is the Current Behavior?

It allows committing back changes without type.
❯ echo "bar" | ./node_modules/.bin/commitlint

Issue Number: N/A
What Is the New Behavior?
It forces the user to specify the "type" of the commit message.
It will fail if not present or not according to commitizen config.
❯ echo "bar" | ./node_modules/.bin/commitlint
⧗   input: bar
✖   subject may not be empty [subject-empty]
✖   type may not be empty [type-empty]

✖   found 2 problems, 0 warnings
ⓘ   Get help: https://github.com/conventional-changelog/commitlint/#what-is-commitlint

❯ echo "foo: bar" | ./node_modules/.bin/commitlint
⧗   input: foo: bar
✖   type must be one of [build, chore, ci, docs, feat, fix, perf, refactor, revert, style, test] [type-enum]

✖   found 1 problems, 0 warnings
ⓘ   Get help: https://github.com/conventional-changelog/commitlint/#what-is-commitlint

Does this PR Introduce a Breaking Change?

[ ] Yes
[x] No
Other Information
Useful when using commitlint in CI.

@jometzner @dhhyi unf I was forced to duplicate the PR, same changes as in https://github.com/intershop/intershop-pwa/pull/1301

Deactivating the commit lint script can be done by using variable HUSKY=0 I trust?  I'd find it a bit intrusive to tell them for that case they must use conventional commits when they just want to "save" their current work.

@jometzner AFAIK you can always use --no-verify flag when using git commit / git cz

@kepek Thank you for your fix. I used the opportunity to clean up a bit more of the Commitizen/Commitlint integration of the project.


discusion: accept :shipit: as LGTM

Seems like it's an old custom, but I think it's cute.

H/T @bnb

I'm -1 on this
People should have to be explicit on this. We don't consider shipit an official LGTM for core commits afaik

It is cute indeed, but I'm -1 too.
The only other case I'd accept with LGTM is "SGTM", because it's explicit. But I don't think we should extend too much on the accepted cases.

@Tiriel I wouldn't accept SGTM either because that implies the person has not actually reviewed i.e LOOKed into the code, therefore they don't count as reviewers.

Also in my understanding, reviewers should be able to backport or fix regressions when the original author is not available. SGTM or shipit do not really imply that either..

This makes me think of an actual but tangential idea. Report analytics on the versions parameter (such as how many people still LGTM in comments).
If you don't mind I'll pivot this issue and self assign.
New subject: analytics


Provide support for cloning existing health check rules

@abozaralizadeh  yep, I will get to work on this feature

Dear @mdesalvo your request is implemented and is now available at https://github.com/abozaralizadeh/ApiWatchTower/commit/0f5d5eb68c72b7f8030e967717a4d48a04763178
Try it by selecting rules and click on Duplicate, the new rule will be created with the prefix "Copy of xxx":


Support syntax-quoted symbol literals

We could extend literal notation to treat syntax-quoted symbol literals as constant patterns. e.g.  `baba/banana could map to (!constant `baba/banana).
This came out of a conversation with @darkleaf on this issue thread https://github.com/missingfaktor/akar/issues/20.

Fixed.


Default tests don't pass

When running code from the freshly cloned repo (master branch), 2 es$core tests fail.
I get the following output:
duckling.core=> (load!)
Loading module :fr$core
Loading module :en$core
Loading module :es$core
Loading module :it$core
Loading module :cn$core
"not found" "viernes a las doce"
"not found" "viernes a las 12:00 horas"
nil

duckling.core=> (run)
:cn$core: 327 examples, 0 failed.
:it$core: 137 examples, 0 failed.
0 FAIL "viernes a las doce"
    Expected {:start #<DateTime 2013-02-15T12:00:00.000-02:00>, :grain :hour}
    Got      12
    Got      12
    Got      12
    Got      12
    Got      {:start #<DateTime 2013-02-15T00:00:00.000-02:00>, :grain :hour}
1 FAIL "viernes a las 12:00 horas"
    Expected {:start #<DateTime 2013-02-15T12:00:00.000-02:00>, :grain :minute}
    Got      12
    Got      0
    Got      {:hour 0}
    Got      12
    Got      0
    Got      12
    Got      0
    Got      12
    Got      0
    Got      {:start #<DateTime 2013-02-15T00:00:00.000-02:00>, :grain :minute}
:es$core: 294 examples, 2 failed.
:en$core: 408 examples, 0 failed.
:fr$core: 330 examples, 0 failed.
#'duckling.core/c

Thanks for reporting. I just commented the 2 ES datetime examples that were failing and committed. These are edge cases and can be managed later.


Update sha256 sum for pepper-flash

==> Downloading https://admdownload.adobe.com/bin/live/AdobeFlashPlayer_20ppau_a_install.dmg
######################################################################## 100.0%
==> Verifying checksum for Cask pepper-flash
==> Note: running "brew update" may fix sha256 checksum errors
Error: sha256 mismatch
Expected: c94600c9b85f5e96f21580ac8aaa4be2aa8511c18379d1cb488a3d813bcbcce1
Actual: c8eb2fde34a1b886de9fe68b299ec85b0acf83012fce5d3cef0e5e6e351fcddd
File: /Library/Caches/Homebrew/pepper-flash-<IP_ADDRESS>.dmg
To retry an incomplete download, remove the file above.

Seems the shasum of this cask is wrong.

Thank you for the contribution. It was merged directly as cd4891ffaece2b7b79f659bf3ffd8b9173b6d39b to keep commit history cleaner. Your contribution is still credited to you.


Find out what atom-eval is

Right now it's listed as "Super secret stuff".

It isn't necessary for Juno, so I've removed it from the docs. IIUC it does for Atom (or coffeescript) what Juno does for Julia.

Yup. The main reason it's not documented is that it has a lot more trip-ups than Julia eval. But it's pretty sweet if you know what you're doing, and I'm happy to help anyone interested get set up.


Get OCaml compiler version from base image

This simplifies the compiler search for duniverse builds, and is useful for the solver branch too.

Looks good to me, but how does it affect duniverse builds?

Scratch that last comment. I just noticed the top of the diff which simplifies the matching of compilers.

It's actually not quite right at the moment because duniverse wants e.g. 4.10, not 4.10.0.

That's something we need to refine the meaning of. I think that if a package requests "4.10", that should translate to "the latest patch version".
Otoh, some packages might specifically ask for "4.10.1" since they need a specific version. This is rarer, but can happen sometimes.


Forms Failling on save/update

Environment information
System:
  OS: macOS 14.5
  CPU: (10) arm64 Apple M1 Max
  Memory: 156.11 MB / 32.00 GB
  Shell: /bin/zsh
Binaries:
  Node: 20.12.2 - ~/.asdf/installs/nodejs/20.12.2/bin/node
  Yarn: undefined - undefined
  npm: 10.8.1 - ~/.asdf/plugins/nodejs/shims/npm
  pnpm: undefined - undefined
NPM Packages:
  @aws-amplify/backend: 1.0.3
  @aws-amplify/backend-cli: 1.0.4
  aws-amplify: 6.3.7
  aws-cdk: 2.146.0
  aws-cdk-lib: 2.146.0
  typescript: 5.4.5
AWS environment variables:

Data packages
<EMAIL_ADDRESS>/Users/jgamboa/fleet/emprendimiento/multiapi
├─┬<EMAIL_ADDRESS>│ └─┬<EMAIL_ADDRESS>│   └──<EMAIL_ADDRESS>└─┬<EMAIL_ADDRESS>  └─┬<EMAIL_ADDRESS>    └──<EMAIL_ADDRESS>
Description
After the latest upgrade of npm packages of amplify my application broke.
We have this model

We are using only the forms generated by amplify with generate forms. After the update, when regenerating forms , mutations etc with the command we started getting problems on update and create like this

Basically we have the billing information that is abelogns to customer and a has one from customer, but it can be set later, now if we try to update or create customer with the amplify form we get that errors.
I know this is a security improvement but i think there is a lot of dev and companies having this problem and rolling back the cli is not an option at the moment (Security concerns) Is it possible to add a flag on the command so we can choose how the forms are generated?
This is the way how amplify is creating the graphql client

Maybe we can choose to genereate that from default, or a flag to choose to use the client schema query, because if. you use the schema query client you dont have any problem, but everytime we regenerate the forms everythings goes back to the mutation
this is the mutation created by the new cli
export const createCustomer = /* GraphQL */   mutation CreateCustomer(     $condition: ModelCustomerConditionInput     $input: CreateCustomerInput!   ) {     createCustomer(condition: $condition, input: $input) {       billingInformation {         address         city         companyName         createdAt         customerId         id         identityCard         municipality         owner         updatedAt         __typename       }       createdAt       email       fullName       id       owner       phone       updatedAt       __typename     }   };
this is the one created by the old one
export const createCustomer = /* GraphQL */   mutation CreateCustomer(     $condition: ModelCustomerConditionInput     $input: CreateCustomerInput!   ) {     createCustomer(condition: $condition, input: $input) {       createdAt       email       fullName       id       owner       phone       updatedAt       __typename     }   };
and pretty sure thats is what generating all this problems

Hi @JGamboa, Thanks for raising this. This issue is related to #2636. Please subscribe to #2636 for future updates.

Hi @JGamboa
The error seems to be complaining about implicit fields that are automatically added by the graphql transformer. They are being marked as required on the schema.
In the meantime, can you try generating your graphql statements using this command instead?
npx ampx generate graphql-client-code --statement-max-depth=1 --out=ui-components/graphql

I was able to reproduce the errors related to the relational fields and mitigated it with the command above, allowing me to create records without errors.
before

after

Hi @JGamboa
The error seems to be complaining about implicit fields that are automatically added by the graphql transformer. They are being marked as required on the schema.
In the meantime, can you try generating your graphql statements using this command instead?
npx ampx generate graphql-client-code --statement-max-depth=1 --out=ui-components/graphql

sorry just getting back home thats why didnt answer earlier. Ill try, but either way, i already create almost all the app again using queries =/ will have in mind for new formularies :D

Hey @JGamboa, Could you please provide the library versions you were using when the mutation code looked like this?
this is the one created by the old one

export const createCustomer = /* GraphQL */ mutation CreateCustomer( $condition: ModelCustomerConditionInput $input: CreateCustomerInput! ) { createCustomer(condition: $condition, input: $input) { createdAt email fullName id owner phone updatedAt __typename } };

@AnilMaktala sorry i cant, after this "upgrade" amplify team make, i lost 80% of functionalities, so i made the rework, i dont have any chance to know what version i was using.  But i can say it was the previous version, im very sorry. :(

Hey @JGamboa, no worries, Thanks for the quick response.


Add a nullptr check

Objective-C binary sizes
*****************STATIC******************
  New size                      Old size
 1,952,730      Total (=)      1,952,730

 No significant differences in binary sizes

***************FRAMEWORKS****************
  New size                      Old size
10,663,755      Total (<)     10,663,757

 No significant differences in binary sizes

****************************************************************

libgrpc.so

     VM SIZE        FILE SIZE
 ++++++++++++++  ++++++++++++++

  [ = ]       0        0  [ = ]

****************************************************************

libgrpc++.so

     VM SIZE              FILE SIZE
 ++++++++++++++ GROWIN ++++++++++++++

 -------------- SHRINK --------------
  [ = ]       0 [None]    -160  -0.0%

  [ = ]       0 TOTAL     -160  -0.0%

[trickle] No significant performance differences

Objective-C binary sizes
*****************STATIC******************
  New size                      Old size
 1,952,730      Total (=)      1,952,730

 No significant differences in binary sizes

***************FRAMEWORKS****************
  New size                      Old size
10,663,742      Total (<)     10,663,752

 No significant differences in binary sizes

[microbenchmarks] No significant performance differences

Known issues : #16123


Trusted workspace paths have no validation

Testing #122233

Open an workspace with workspace trust enabled
Add a completely bogus path full of illegal characters to the list of trusted folders
🐛 It doesn't complain at all

I understand this isn't a huge issue since we will stay in the untrusted state, but I would've liked a warning message or something.
Side feature request: The file picker showing up for me to pick a folder would be cool too since it wasn't clear at first (since I'm in the mindset of this workspace) that these were absolute paths and it kept adding the / in front.

see https://github.com/microsoft/vscode/issues/121090 for second request

Also from https://github.com/microsoft/vscode/issues/122530:
If you clear the input box and press Enter, the folder gets removed 🐛

@joaomoreno I would argue that's not a bug. We do the same in the settings editor for lists. This is not an explorer where you are renaming a folder, so you aren't accidentally deleting a file or something. It's an intuitive way to delete an item.

I would argue that it is. An empty folder name should be a validation error and pressing Enter on that situation should be a no-op. Why on earth would you consider causing this pain to a user?

Shouldn't accept folders only?
I mean, I can type a single file or a .code-workspace file and it accepts.

I did some tweaking on this again today. With the new validation, only folders can be selected due to limitations on windows and linux in electrons open dialogs.  However, this limitation seems acceptable in the current UX because you don't gain any more from being able to add a single workspace file than you would trusting that entry directly.


Are the Utils PowerShell Core Depends on in Linux managed and published?

The Get-Help on Linux Depends on "less" command - this is an Amazon Linux 2 container (which - as provided by AWS - has a completely minimalized package footprint) and I get this error:

This raises the questions:

is there a managed list of what PowerShell core assumes is on the system?
shouldn't the packages for PowerShell Core check for and resolve these dependencies if system commands depend on them?
or should it just not depend on any OS packages?

Apologies if this is covered somewhere - if so, please drop a link in this issue :)

I have raised a concern related specifically to the availability of less here before:
https://github.com/PowerShell/PowerShell/issues/7851
FWIW it's not Get-Help that has this dependency; it's the help function, which is actually a function and not a true alias. Get-Help on its own normally does not provide paging.


TabMon sample workbook for v.10 cannot be opened

Hello!
I tried several times to download sample workbook for version 10 and open it in Tableau desktop on different projects, version 10.0 and 10.2, but not successfull.
Latest error message was on 10.2 version, following:

Can you, please, help, what I'm doing wrongly or how can I fix it?
Thanks ;)

Hello,
The sample workbook should be included with TabMon install, try using these. In order to find the workbooks please log on to the TabMon computer then navigate to a directory like this:
\TabMon\Resources\Sample Workbooks
This directory will have all of the updated workbooks.
Please let me know if there are any issues with this.
Thanks,
-Dan

Hi!
Thank you very much for your answer! It was my fault when downloading
sample workbook wrongly.
Now I'm able to republish TabMon workbook without any issue.
Have a nice day!
J+
On Fri, Jun 9, 2017 at 10:30 PM, Dan Rahm<EMAIL_ADDRESS>wrote:

Hello,
The sample workbook should be included with TabMon install, try using
these. In order to find the workbooks please log on to the TabMon computer
then navigate to a directory like this:
\TabMon\Resources\Sample Workbooks
This directory will have all of the updated workbooks.
Please let me know if there are any issues with this.
Thanks,
-Dan
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/tableau/TabMon/issues/122#issuecomment-307492071, or mute
the thread
https://github.com/notifications/unsubscribe-auth/Ab8qyctZqmmbk5blB1Jk2ervGTQuy-DXks5sCatMgaJpZM4N1S6v
.

I'm glad everything worked out! I'll close this issue now!


[FAB-17831] Use generic constant/var names for ledger data format

Signed-off-by: Wenjian Qiao<EMAIL_ADDRESS>Type of change

Improvement (improvement to code, performance, etc)

Description
Currently Version1x and Version20 are defined in common/ledger/dataformat.go.
They should be renamed to more generic names such as PreviousVersion and CurrentVersion.
Related issues
https://jira.hyperledger.org/browse/FAB-17831

@wenjianqiao Can you give a bit more context here? When we move to version 3, will we change the current version to 3.0 and previous version to 2.x?

@wenjianqiao Can you give a bit more context here? When we move to version 3, will we change the current version to 3.0 and previous version to 2.x?

@cendhu - yes, that was the intent

Hit a CI flake.
FAIL: TestWithStaticDeliverClientLeader (46.00s)
gossip_service_test.go:626: Failed to establish full channel membership. Only 0 out of 2 peers have full membership

/ci-run

/azp run

/azp run


C++

Type: Bug
C# won't let me compile when I execute a code I get an error
VS Code version: Code 1.75.0 (e2816fe719a4026ffa1ee0189dc89bdfdbafb164, 2023-02-01T15:23:45.584Z)
OS version: Windows_NT x64 10.0.19045
Modes: Unsupported
Sandboxed: No

System Info

Item
Value

CPUs
AMD Ryzen 5 3500 6-Core Processor               (6 x 3950)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: disabled_off

Load (avg)
undefined

Memory (System)
31.89GB (19.97GB free)

Process Argv
--crash-reporter-id b868f5d6-9c72-48cf-8be6-cc2ffd63e184

Screen Reader
no

VM
0%

Extensions (37)

Extension
Author (truncated)
Version

include-autocomplete
ajs
0.0.4

blackbox
Bla
0.10.29

c-cpp-compile-run
dan
1.0.29

dscodegpt
Dan
1.0.15

vscode-html-css
ecm
1.13.1

code-runner
for
0.12.0

c-cpp-runner
fra
5.0.0

vscode-chatgpt
gen
3.5.9

vscode-language-pack-es
MS-
1.75.2023020809

csharp
ms-
1.25.4

vscode-edge-devtools
ms-
2.1.1

isort
ms-
2022.8.0

python
ms-
2023.2.0

vscode-pylance
ms-
2023.2.10

jupyter
ms-
2023.1.2010391206

jupyter-keymap
ms-
1.0.0

jupyter-renderers
ms-
1.0.14

vscode-jupyter-cell-tags
ms-
0.1.6

vscode-jupyter-slideshow
ms-
0.1.5

cmake-tools
ms-
1.13.45

cpptools
ms-
1.13.9

cpptools-extension-pack
ms-
1.3.0

material-icon-theme
PKi
4.23.1

java
red
1.14.0

background
sha
1.2.8

html5-boilerplate
sid
1.1.1

cmake
twx
0.0.17

vscode-lldb
vad
1.8.1

intellicode-api-usage-examples
Vis
0.2.7

vscodeintellicode
Vis
1.2.30

vscode-java-debug
vsc
0.48.0

vscode-java-dependency
vsc
0.21.1

vscode-java-pack
vsc
0.25.7

vscode-java-test
vsc
0.37.1

vscode-maven
vsc
0.40.4

JavaScriptSnippets
xab
1.8.0

cpp-quick-start-snippet-for-beginners
yyx
1.0.1

(5 theme extensions excluded)

A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vstes627:30244334
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242:30382549
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscorecescf:30445987
pythondataviewer:30285071
vscod805cf:30301675
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593:30376534
pythonvs932:30410667
cppdebug:30492333
vsclangdf:30486550
c4g48928:30535728
dsvsc012:30540252
azure-dev_surveyone:30548225
pyindex848cf:30577861
nodejswelcome1cf:30587006
3biah626:30602489
pyind779cf:30657577
89544117:30613380
pythonsymbol12cf:30657549
2i9eh265:30646982

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.76.2. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

/gifPlease

Thanks for reporting this issue! Unfortunately, it's hard for us to understand what issue you're seeing. Please help us out by providing a screen recording showing exactly what isn't working as expected. While we can work with most standard formats, .gif files are preferred as they are displayed inline on GitHub. You may find https://gifcap.dev helpful as a browser-based gif recording tool.
If the issue depends on keyboard input, you can help us by enabling screencast mode for the recording (Developer: Toggle Screencast Mode in the command palette). Lastly, please attach this file via the GitHub web interface as emailed responses will strip files out from the issue.
Happy coding!

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


Add access control config to worker nodes

Add access control config files to worker to enable graceful shutdown,
Fixes:  https://github.com/trinodb/trino/issues/22589

👋 @nineinchnick PTAL

Maybe @losipiuk

Superseded by #226


Please add valid tags for versioning

See:
https://developer.apple.com/documentation/xcode/publishing-a-swift-package-with-xcode#Tag-your-latest-commit

Thank you Christian, gonna work on that!

Hi Christian, I think that valid tags for versioning should now work. Let me know! If everything works, I'll close the issue.


It's impossible to animate the 'offset' object property

    let obj = { offset : 0 };

    anime({
            targets: obj,
            offset: 200,
            update: () => {
                console.log(obj)
            }
    });

Yeah that one is tricky since offset is part of the API.
That's the biggest downside of having a unified / flat parameter object.
The only solution is to separate the global parameters from the animation properties, but I prefer keeping the unified syntax.


Pagination

Hii @lhandel ,
Is there any way I can handle pagination? when reaching some at point I need to add more data in array of card stack.
Or is there any way I can handle it with load more data in stack without refreshing whole content?

@mitjnextt ,
Hey mit's, I am also facing this issue.
need Help..

Did not get any success, Had to implement some custom logic

Did not get any success, Had to implement some custom logic

ohh nice, can you please share?

Yes actually what I did was...
I rendered 5 items in Array at first, and then whenever users swipes Left or Right, using onSwipedLeft & onSwipedRight I pushed new card at the end of the array!


Added some changes that reset the score every time a player restarts the game.

The score wasn't resetting when the player wanted to play again after winning or losing. The previous score was instead kept and new scores were added to it. For example, if the user had a score 5 in the previous game, the user's score kept increasing from 5 when playing a new game instead of increasing from 0.

I fixed merge conflicts with master


Enhancement: Improve Volume handling

Disclaimer:
Please go through existing feature requests to avoid creating duplicates. If you found a similar issue please post a comment there. If you are certain your issue is not related to others then create the issue. Obvious ignorance of this rule might get you blocked from posting new issues. Please tick the box below to show that you have followed the guideline.

[x] I have checked for a similar issue and sure it hasn't been reported before.

Description:
Users are experiencing volume behaviour inconsistency as mentioned in #111 and #246
Need to stay as close to native volume behaviour of macOS

Just wanted to open the issue on the same topic. This is worth fixing

This issue should be resolved in v0.3.1.
Please update the app and let me know if this issue is still relevant. Thank you

Sorry to say, there are some problems. I updated, it worked ok but than I tried to switch the device (not sure which name there was) and the program halted. Sound became completely off. I started again, it said you need to reinstall the driver. It failed. Than I tried to go to sound settings (as no sound devices show up in menu at all) and Settings app crashed. It does it every time I go to sound settings.
No I'm without speakers at all 🙄


API token exposed in Strapi settings page

Great plugin, however the API token appears to be exposed in the Strapi settings page for the plugin.
It might also be useful to lock down the deployment page to specific users/roles as well.

The token is exposed on purpose. The settings page is meant to check which configurations you are using.
I'm sorry, but I never used Strapi in a team with more than one person. Which is the best approach, in your opinion?

No worries @gianlucaparadise . The problem is the token provides full access to your teams Vercel platform API. There may be circumstances where and not all Strapi Super Admins should have full access to your team's Vercel platform.
This is an unfortunate gap on how these tokens are controlled. Hopefully in the future Vercel adds additional granular control similar to Github personal access tokens.
Unless I'm completely wrong and there is granular access somewhere 😆
I think a good first step would be to not display the the full API key. If it's useful to verify the correct key is used, you could display just the first or last 4 characters. I think the only place it should be fully determined is the .env file.
Unsure how to help or suggest with implementing the roles suggestion for the Deploy page. You would be the expert there 😄  But basically you would want the plugin to be configurable within the Roles page in Strapi settings (/admin/settings/roles/1)
Hopefully that helps

I released v1.3.0. In the new version of the plugin:

The API token will not be displayed entirely
You can decide which roles can deploy

Unfortunately the Strapi documentation doesn't explain how to hide the menu link depending on the roles. If the user doesn't have any of the specified roles, he/she can't see the list of the deployments, can't deploy and can't see the configurations. I'll try to improve the plugin and hide the menu link somehow.
Thank you for the suggestions!


Filter endpoint requires updated node-jira lib

Latest node-jira library does not support the /filter API endpoint. Will have to submit a patch for it.

https://github.com/jira-node/node-jira-client/issues/297

Pull request was accepted and merged... closing this issue


Removed react and react-native as devdependencies

If we're thinking about using flow, then they actually need to be installed in node_modules to be considered in the static type checking.
Sorry for being so back and forth, but it is good to get viewpoints from different people.


Adding Parallel Evaluation mode and MERT embeddings

Adding additional MERT backbone for music evaluation tasks.
Adding a multi-GPU evaluation mode, realized by PyTorch DDP.

A caveat: since the VGGish implemented called in this repo would only accept a numpy.ndarray waveform sample in, the frechet audio distance would be calculated on the first available GPU only.

The added changes have been tested through the test samples generate by this repo. Note that the results are extremely close, but not exactly the same.
PANN backbone:

Metric
Single GPU
Multiple GPUs

Fréchet Distance
76.5592910152047
76.55929104668417

Fréchet Audio Distance
25.13933342756768
25.13933342756768

KL Divergence (Sigmoid)
4.942387580871582
4.942387580871582

KL Divergence (Softmax)
5.392766952514648
5.392767429351807

Inception Score (Mean)
1.4111682664276006
1.3807413446235108

Inception Score (Std)
0.2100466806269512
0.16963117700578514

MERT backbone:

Metric
Single GPU
Multiple GPUs

Fréchet Distance
35.53496529798653
35.534967212472644

Fréchet Audio Distance
25.13933342756768
25.13933342756768

KL Divergence (Sigmoid)
2.0398805141448975
2.0328383445739746

KL Divergence (Softmax)
0.021201787516474724
0.025442462414503098

Inception Score (Mean)
1.017859189575241
1.0178318327079956

Inception Score (Std)
0.0009513526838024663
0.0011269906062056378

This may be due to NCCL communications' non-deterministic nature, see https://github.com/NVIDIA/nccl/issues/157. As the difference is quite small, the users can choose for themselves in if they want to use the parallel calculation, which may save time if the evaluation set is large.

Thanks for your contribution! That for sure will make the evaluation much faster on across multiple GPUs. Great work.
Looks good to me. Merging.


Output Parameter Order

It looks like when specifying the output parameters, you actually have to put the gcs output path second, and the local file first. Is this correct? The example in the README has it going the opposite way, but it doesn't seem to work that way.

Yes, you are right... that portion of the README was incorrect.  I've just updated it.


[Compute] az sig image-definition create: Fix bug about default value of Security Type

Related command

Description

Testing Guide

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change
[Component Name 2] az command b: Add some customer-facing feature

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

[ ] I adhere to the Error Handling Guidelines.

Compute


Stackage LTS: Relaxing bounds on cryptonite

Hi @zohl, I am currently trying to build an LTS on Stackage and running into a strict upper bound issue with servant-auth-cookie. Would you be able to relax the upper bound of cryptonite to <=0.21?
I'm currently seeing:
stackage-curator: cryptonite-0.21 (Vincent Hanquez @vincenthz) is out of bounds for:
- [ ] servant-auth-cookie-0.3.2 (>=0.14 && <=0.20). Al Zohali<EMAIL_ADDRESS>@zohl. @zohl. Used by: library, executable, test-suite, benchmark

Hello,
Sure, I've uploaded version with relaxed upper bound. [1]
Stackage LTS should pick it up during a week. If you don't want to wait, you can try to use servant-auth-cookie-0.4.2: there haven't been made many changes yet and they are not that radical to expect everything to break ;)
[1] https://hackage.haskell.org/package/servant-auth-cookie-0.3.3

Thanks @zohl! We tried with 0.4.2 but it was bringing too many new constraints. Great that you made the release, I'll fire up a new build then :+1:


EQUATION_EXPLORER: Allow the entire implication graph to be downloaded as a CSV

This would be a 4694 x 4694 table.  Perhaps with a numerical code such as
+4: explicitly proved
+3: implicitly proved
+2: explicitly conjectured
+1: implicitly conjectured
0: no conjecture
-1: implicitly conjectured false
-2: explicitly conjectured false
-3: implicitly disproved
-4: explicitly disproved
Some legend may need to be attached to the CSV file somehow to explain the code.

claim

propose PR: https://github.com/teorth/equational_theories/pull/628

I'd suggest perhaps instead of making this part of the equation explorer, that maybe it makes sense to just generate data like this in the blueprint github action workflow and include links from the dashboard? A number of people seemed to be happy to use data I generated just using different modes of lake exe extract_implications, perhaps we can just export some JSONs, make a CSV, and link this from the dashboard? Since they can be individually large files, perhaps we zip them individually as well.

Perhaps we can do both?  Certainly I think we can add a bit more functionality to the dashboard than we have currently.  It did seem to me though that the Equation Explorer was already a sort of interactive spreadsheet to begin with, so exporting to spreadsheet formats within that tool seemed to make sense to me as well.


Camera not found on Android 11

Hello,
I have the following issue only on some Android 11 phones.
D/CameraValidator( 2192): Verifying camera lens facing on A13, lensFacingInteger: null
E/CameraValidator( 2192): Camera LensFacing verification failed, existing cameras: [Camera@131caf1[id=0], Camera@8201aae[id=1], Camera@9f231c8[id=3], Camera@cf433e3[id=4]]
W/CameraX ( 2192): Retry init. Start time<PHONE_NUMBER> current time<PHONE_NUMBER>
W/CameraX ( 2192): androidx.camera.core.impl.CameraValidator$CameraIdListIncorrectException: Expected camera missing from device.
W/CameraX ( 2192): 	at androidx.camera.core.impl.CameraValidator.validateCameras(CameraValidator.java:97)
W/CameraX ( 2192): 	at androidx.camera.core.CameraX.lambda$initAndRetryRecursively$2$androidx-camera-core-CameraX(CameraX.java:334)
W/CameraX ( 2192): 	at androidx.camera.core.CameraX$$ExternalSyntheticLambda3.run(Unknown Source:10)
W/CameraX ( 2192): 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
W/CameraX ( 2192): 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
W/CameraX ( 2192): 	at java.lang.Thread.run(Thread.java:923)
W/CameraX ( 2192): Caused by: java.lang.IllegalArgumentException: The given lens facing integer: 255 can not be recognized.
W/CameraX ( 2192): 	at androidx.camera.camera2.internal.LensFacingUtil.getCameraSelectorLensFacing(LensFacingUtil.java:56)
W/CameraX ( 2192): 	at androidx.camera.camera2.internal.Camera2CameraInfoImpl.getLensFacing(Camera2CameraInfoImpl.java:198)
W/CameraX ( 2192): 	at androidx.camera.core.impl.LensFacingCameraFilter.filter(LensFacingCameraFilter.java:48)
W/CameraX ( 2192): 	at androidx.camera.core.CameraSelector.filter(CameraSelector.java:128)
W/CameraX ( 2192): 	at androidx.camera.core.CameraSelector.filter(CameraSelector.java:153)
W/CameraX ( 2192): 	at androidx.camera.core.CameraSelector.select(CameraSelector.java:90)
W/CameraX ( 2192): 	at androidx.camera.core.impl.CameraValidator.validateCameras(CameraValidator.java:83)
W/CameraX ( 2192): 	... 5 more
D/CameraRepository( 2192): Added camera: 0
I/Camera2CameraInfo( 2192): Device Level: INFO_SUPPORTED_HARDWARE_LEVEL_LIMITED
D/CameraRepository( 2192): Added camera: 1
I/Camera2CameraInfo( 2192): Device Level: INFO_SUPPORTED_HARDWARE_LEVEL_LIMITED
D/CameraRepository( 2192): Added camera: 3
I/Camera2CameraInfo( 2192): Device Level: INFO_SUPPORTED_HARDWARE_LEVEL_LIMITED
D/CameraRepository( 2192): Added camera: 4
I/Camera2CameraInfo( 2192): Device Level: INFO_SUPPORTED_HARDWARE_LEVEL_LIMITED

This doesn't permit to scan any code.
Is there any solution to this?

What type of camera is camera id 2 ? Because that one seems to be missing?
Is this a USB camera?

Nope, is an integrated camera in a phone (Umidigi phone).
There's 2 cameras in the back of the phone and one in front of it.
We have 5 of them and all have the same issue.
I had a similar issue on an old ZTE phone but I didn't have the possibility to debug it.


Classes that override +resolveClassMethod: can't be mocked

If you have a class that overrides +resolveClassMethod: and attempt to mock it, you will crash due to recursion.

Merged corresponding PR.


Renders the content twice while liquid-fire transition is in progress

I noticed that the wormhole content is rendered twice into the target during liquid fire transitions using liquid-outlet.
I think for transitioning from route1 to route2 liquid-fire has both pages prepared. That results in rendering the wormhole content of both pages into my header buttons area.

Issue is due to when using liquid-fire both routes (transition to and transition from) are displayed on the screen while doing transform animations. Consquently the wormhole will display the new content and the old content at the same time until the transition is complete and the from route is destroyed.

Has anyone came up with a workaround for this? I am experiencing the same issue.

I did animations with css. I‘ve created a wrapper component that can delay its destruction for the animation duration. Everything else was just a matter of switching css classes.
I should have done this from start because it was so much more productive. As you go from transition definition by custom js api to well-known standard css


Solve travis

Codecov Report

Merging #4 into master will increase coverage by 9.85%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master       #4      +/-   ##
==========================================
+ Coverage   82.98%   92.84%   +9.85%
==========================================
  Files           5        5
  Lines         629      629
==========================================
+ Hits          522      584      +62
+ Misses        107       45      -62

Impacted Files
Coverage Δ

ssdedupe/mssql/cli.py
93.92% <0%> (+2.83%)
:arrow_up:

ssdedupe/mssql/exact_matches.py
82.08% <0%> (+82.08%)
: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 2b83a72...e5d3944. Read the comment docs.


Release alluxio-enterprise 2.4.2-2.1.2-1.0 (automated commit)

Description:
Alluxio Enterprise Edition
Source URL: https://alluxio-dcos-dev.s3.amazonaws.com/autodelete7d/alluxio-enterprise/20200204-130546-KygnoR78HauvYfjY/stub-universe-alluxio-enterprise.json
Changes between revisions 300 => 400:
0 files added: []
0 files removed: []
3 files changed:
--- 300/marathon.json.mustache
+++ 400/marathon.json.mustache
@@ -21,10 +21,10 @@
   },
   {{/service.service-account-secret}}
   "env": {
-    "PACKAGE_BUILD_TIME_EPOCH_MS": "1576876153455",
-    "PACKAGE_BUILD_TIME_STR": "Fri Dec 20 2019 21:09:13 +0000",
+    "PACKAGE_BUILD_TIME_EPOCH_MS": "1580850348714",
+    "PACKAGE_BUILD_TIME_STR": "Tue Feb 04 2020 21:05:48 +0000",
     "PACKAGE_NAME": "alluxio-enterprise",
-    "PACKAGE_VERSION": "2.4.1-2.1.1-1.0",
+    "PACKAGE_VERSION": "2.4.2-2.1.2-1.0",

     "BOOTSTRAP_URI": "{{resource.assets.uris.bootstrap-zip}}",
     "EXECUTOR_URI": "{{resource.assets.uris.executor-zip}}",
@@ -48,7 +48,7 @@
     "SERVICE_USER": "{{service.user}}",
     "TASKCFG_ALL_ALLUXIO_DISTRIBUTION": "{{service.alluxio-distribution}}",
     "TASKCFG_ALL_ALLUXIO_LICENSE": "{{service.license}}",
-    "TASKCFG_ALL_ALLUXIO_VERSION": "2.1.1-1.0",
+    "TASKCFG_ALL_ALLUXIO_VERSION": "2.1.2-1.0",
     "TASKCFG_ALL_LOG_LEVEL": "{{service.log-level}}",
     "TASKCFG_ALL_SERVICE_NAME": "{{service.name}}",

--- 300/package.json
+++ 400/package.json
@@ -3,7 +3,7 @@
   "upgradesFrom": [],
   "downgradesTo": [],
   "name": "alluxio-enterprise",
-  "version": "2.4.1-2.1.1-1.0",
+  "version": "2.4.2-2.1.2-1.0",
   "maintainer"<EMAIL_ADDRESS>   "description": "Alluxio, formerly Tachyon, is the world's first system that unifies disparate storage systems at memory speed. With Alluxio, enterprises can manage data efficiently, accelerate business analytics, and ease the adoption of hybrid cloud. \n\n Alluxio Enterprise Edition delivers operational benefits of a stable, high performance system with enterprise features and support for critical deployments. Please refer to https://alluxio.com/docs/enterprise/1.7/en/Alluxio-on-DCOS.html for a detailed operation guide. \n\n Release Notes: \n - Upgrade to version 2.1.0 of Alluxio",
   "selected": false,
--- 300/resource.json
+++ 400/resource.json
@@ -5,12 +5,12 @@
       "alluxio-agent-darwin_amd64": "https://alluxio-dcos-release.s3.amazonaws.com/agent/v1.5.0/darwin_amd64/alluxio-dcos",
       "alluxio-agent-linux_386": "https://alluxio-dcos-release.s3.amazonaws.com/agent/v1.5.0/linux_386/alluxio-dcos",
       "alluxio-agent-linux_amd64": "https://alluxio-dcos-release.s3.amazonaws.com/agent/v1.5.0/linux_amd64/alluxio-dcos",
-      "bootstrap-zip": "https://alluxio-dcos-release.s3.amazonaws.com/artifacts/2.4.1-2.1.1-1.0/bootstrap.zip",
-      "executor-zip": "https://alluxio-dcos-release.s3.amazonaws.com/artifacts/2.4.1-2.1.1-1.0/executor.zip",
+      "bootstrap-zip": "https://alluxio-dcos-release.s3.amazonaws.com/artifacts/2.4.2-2.1.2-1.0/bootstrap.zip",
+      "executor-zip": "https://alluxio-dcos-release.s3.amazonaws.com/artifacts/2.4.2-2.1.2-1.0/executor.zip",
       "java-tar-gz": "https://alluxio-dcos-release.s3.amazonaws.com/jdk/jdk1.8.0_144_jce_policy.tar.gz",
       "jre-tar-gz": "https://downloads.mesosphere.com/java/server-jre-8u162-linux-x64.tar.gz",
       "libmesos-bundle-tar-gz": "https://downloads.mesosphere.com/libmesos-bundle/libmesos-bundle-master-28f8827.tar.gz",
-      "scheduler-zip": "https://alluxio-dcos-release.s3.amazonaws.com/artifacts/2.4.1-2.1.1-1.0/alluxio-enterprise-scheduler.zip"
+      "scheduler-zip": "https://alluxio-dcos-release.s3.amazonaws.com/artifacts/2.4.2-2.1.2-1.0/alluxio-enterprise-scheduler.zip"
     }
   },
   "images": {
@@ -29,7 +29,7 @@
             }
           ],
           "kind": "executable",
-          "url": "https://alluxio-dcos-release.s3.amazonaws.com/artifacts/2.4.1-2.1.1-1.0/dcos-service-cli-darwin"
+          "url": "https://alluxio-dcos-release.s3.amazonaws.com/artifacts/2.4.2-2.1.2-1.0/dcos-service-cli-darwin"
         }
       },
       "linux": {
@@ -41,7 +41,7 @@
             }
           ],
           "kind": "executable",
-          "url": "https://alluxio-dcos-release.s3.amazonaws.com/artifacts/2.4.1-2.1.1-1.0/dcos-service-cli-linux"
+          "url": "https://alluxio-dcos-release.s3.amazonaws.com/artifacts/2.4.2-2.1.2-1.0/dcos-service-cli-linux"
         }
       },
       "windows": {
@@ -53,7 +53,7 @@
             }
           ],
           "kind": "executable",
-          "url": "https://alluxio-dcos-release.s3.amazonaws.com/artifacts/2.4.1-2.1.1-1.0/dcos-service-cli.exe"
+          "url": "https://alluxio-dcos-release.s3.amazonaws.com/artifacts/2.4.2-2.1.2-1.0/dcos-service-cli.exe"
         }
       }
     }

@ryadav88 Please take a look.

Closing in favor of an updated PR #2502.


Re-work docs site, possibly add support for versioned documentation

Versioned docs (with version switcher - could use Mike for Mkdocs)

@afolson @aaronsteers what are some paths forward on this? This would be a big benefit both for the community and for our general release process as it would avoid situations where docs are updated prior to features being released and vice versa?
Is this something we could do in July or August?

@tayloramurphy This can be done in Jekyll with some work or we could move this to another tool like Sphinx. The latter might be better long term but is a larger undertaking and I'm not sure it's worth it just for this at the moment.

@afolson will you update this issue with your current status with Docasaurus? I'm realizing we've stated a lot of requirements for the new docs site but haven't written them down on the primary issue?
Big things I believe we've aligned on are:

versioned documentation
3 panel view (side bar, content, ToC)
Easy search
Good design and ease of maintenance

cc @DouweM @sbalnojan

Deployed: https://afolson-docs.netlify.app/concepts/
Ignore the weird side bar and default home page.

Other docs frameworks considered:

Mkdocs
Sphinx
Staying with Jekyll
Readme.io

All were ruled out due to the significant time it would take to re-theme them, time to create plugins to get functionality we wanted (specifically around docs versioning or OpenAPI/swagger tools), or lack of flexibility with diataxis framework.

@sbalnojan Yeah all of that will be added back. I haven't added any of the custom scripts/theme stuff yet.

@afolson What are the steps yet to be done before we can replace the current docs site with this? I don't think it needs to better yet, just have feature parity, and then we can continuously improve it from there.

Steps to get this to feature parity/launch:

Improved search experience
Home page

Ideally the theme would match the brand guidelines.

Given our limited bandwidth, I'm starting to feel like it makes sense to just make the current site work better for us. As nice as it would be to get versioned docs and prettier highlighting/TOC/etc out of the box, it's going to end up being a larger time investment than it's probably worth at this point in time.
@sbalnojan @tayloramurphy Would love to get your thoughts on this. Completely open to ideas. We can do versioning with Jekyll it's just not as pretty and may be a more manual process.

@afolson true we have limited bandwidth, but this is a high value improvement that is worth doing prior to GA. The docs are an extension of our product as as we move into Cloud GA we need to elevate the experience around the docs.
What are the current blockers from your perspective? We'll have some frontend capacity with Wil. Is it mainly getting some engineering help on getting this deployed and replacing Jekyll?
cc @DouweM

@tayloramurphy It sounds like most of Wil's time will be taken up with Cloud, Hub, and maybe some new website stuff as part of that launch. My worry is that it pushes this stuff out several more weeks. The new site needs a home page and some template tweaks to make it on par with what we currently have.

@afolson I'll sync up with @aaronsteers and @seth-meltano next week and see if we can get an estimate on scope given everything. Cloud is pending a few decisions on scope, Hub is awaiting the desigers for the bigger redesign.
Do you have an open PR where the current status is?

@afolson - can you provide the repo and a list of known remaining todo items for scoping?

@tayloramurphy @aaronsteers The site is here and deploys from this repo. I can make a PR for it if that's easier but initially didn't because it would have been a messier merge conflict later.
The homepage is the main thing to do to get it launched. I'm meeting with Wil tomorrow to discuss a wireframe that I made and will make specific issues with action items out of that.

@afolson would you mind inviting me to that call?

Docusaurus PR and action items here: https://github.com/meltano/meltano/pull/7208
Preview: https://deploy-preview-7208--meltano.netlify.app/

Not a priority for now.

Closing as we're moving to docusaurus.


treesitter error when I open doc throught telescope

When I hit <leader>sh which is mapped to telescope help_tags function, this error comes up:

Error executing vim.schedule lua callback: /usr/local/share/nvim/runtime/lua/vim/treesitter/query.lua:219: query: invalid node type at position 14 for language help
stack traceback:
        [C]: in function '_ts_parse_query'
        /usr/local/share/nvim/runtime/lua/vim/treesitter/query.lua:219: in function 'get_query'
        ...l/share/nvim/runtime/lua/vim/treesitter/languagetree.lua:52: in function 'new'
        /usr/local/share/nvim/runtime/lua/vim/treesitter.lua:45: in function '_create_parser'
        /usr/local/share/nvim/runtime/lua/vim/treesitter.lua:96: in function 'get_parser'
        .../start/telescope.nvim/lua/telescope/previewers/utils.lua:129: in function 'ts_highlighter'
        .../start/telescope.nvim/lua/telescope/previewers/utils.lua:106: in function 'highlighter'
        ...scope.nvim/lua/telescope/previewers/buffer_previewer.lua:242: in function ''
        vim/_editor.lua: in function <vim/_editor.lua:0>
Press ENTER or type command to continue

I have no idea how to deal with this and maybe I should open this issue on telescope?

make sure that you have most up-to-date neovim and associated plugins (either 0.8.1 stable release or nightly).

yes, I've checked it (PackerUpdate and I built neovim using nigthly tag)

I've done it again just to be sure (sudo cmake --build build/ --target uninstall
and sudo make install of 0.8.1 and rm -rf ~/.local/share/nvim) , same error when I press <leader>sh.
Also, if no preview, no errors (it seems something related with nvim doc).
I've executed :checkhealth and here's the treesitter section in case it helps:
## The following errors have been detected:
  - ERROR: help(highlights): /usr/local/share/nvim/runtime/lua/vim/treesitter/query.lua:219: query: invalid node type at position 424 for language help
    help(highlights) is concatenated from the following files:
    | [ERROR]:"/home/mgreco/.local/share/nvim/site/pack/packer/start/nvim-treesitter/queries/help/highlights.scm", failed to load: /usr/local/share/nvim/runtime/lua/vim/treesitter/query.lua:219: query: invalid node type at position 424 for language help
  - ERROR: help(injections): /usr/local/share/nvim/runtime/lua/vim/treesitter/query.lua:219: query: invalid node type at position 14 for language help
    help(injections) is concatenated from the following files:
    | [ERROR]:"/home/mgreco/.local/share/nvim/site/pack/packer/start/nvim-treesitter/queries/help/injections.scm", failed to load: /usr/local/share/nvim/runtime/lua/vim/treesitter/query.lua:219: query: invalid node type at position 14 for language help

full output :checkhealth

gitsigns: require("gitsigns.health").check()
========================================================================
  - OK: git version 2.34.1

man: require("man.health").check()
========================================================================
  - OK: plugin/man.vim not in $VIMRUNTIME
  - OK: autoload/man.vim not in $VIMRUNTIME

mason: require("mason.health").check()
========================================================================
## mason.nvim report
  - OK: neovim version >= 0.7.0
  - OK: **Go**: `go version go1.18.1 linux/amd64`
  - OK: **cargo**: `cargo 1.65.0 (4bc8f24d3 2022-10-20)`
  - WARNING: **luarocks**: not available
  - OK: **Ruby**: `ruby 3.0.2p107 (2021-07-07 revision 0db68f0233) [x86_64-linux-gnu]`
  - OK: **RubyGem**: `3.3.5`
  - WARNING: **Composer**: not available
  - WARNING: **PHP**: not available
  - OK: **npm**: `8.19.2`
  - OK: **node**: `v18.12.1`
  - OK: **python3**: `Python 3.10.6`
  - OK: **pip3**: `pip 22.0.2 from /usr/lib/python3/dist-packages/pip (python 3.10)`
  - WARNING: **javac**: not available
  - WARNING: **java**: not available
  - WARNING: **julia**: not available
  - OK: **wget**: `GNU Wget 1.21.2 built on linux-gnu.`
  - OK: **curl**: `curl 7.81.0 (x86_64-pc-linux-gnu) libcurl/7.81.0 OpenSSL/3.0.2 zlib/1.2.11 brotli/1.0.9 zstd/1.4.8 libidn2/2.3.2 libpsl/0.21.0 (+libidn2/2.3.2) libssh/0.9.6/openssl/zlib nghttp2/1.43.0 librtmp/2.3 OpenLDAP/2.5.13`
  - OK: **gzip**: `gzip 1.10`
  - OK: **tar**: `tar (GNU tar) 1.34`
  - WARNING: **pwsh**: not available
  - OK: **bash**: `GNU bash, version 5.1.16(1)-release (x86_64-pc-linux-gnu)`
  - OK: **sh**: `Ok`
  - OK: GitHub API rate limit. Used: 0. Remaining: 60. Limit: 60. Reset: Fri 02 Dec 2022 15:16:02 CET.

nvim: health#nvim#check
========================================================================
## Configuration
  - WARNING: Missing user config file: /home/mgreco/.config/nvim/init.vim
    - ADVICE:
      - :help |init.vim|

## Performance
  - OK: Build type: Release

## Remote Plugins
  - OK: Up to date

## terminal
  - INFO: key_backspace (kbs) terminfo entry: key_backspace=\177
  - INFO: key_dc (kdch1) terminfo entry: key_dc=\E[3~
  - INFO: $TERM_PROGRAM='tmux'
  - INFO: $COLORTERM='truecolor'

## tmux
  - OK: escape-time: 10
  - INFO: Checking stuff
  - WARNING: `focus-events` is not enabled. |'autoread'| may not work.
    - ADVICE:
      - (tmux 1.9+ only) Set `focus-events` in ~/.tmux.conf:
          set-option -g focus-events on
  - INFO: $TERM: tmux-256color

nvim-treesitter: require("nvim-treesitter.health").check()
========================================================================
## Installation
  - WARNING: `tree-sitter` executable not found (parser generator, only needed for :TSInstallFromGrammar, not required for :TSInstall)
  - OK: `node` found v18.12.1 (only needed for :TSInstallFromGrammar)
  - OK: `git` executable found.
  - OK: `cc` executable found. Selected from { vim.NIL, "cc", "gcc", "clang", "cl", "zig" }
    Version: cc (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0
  - OK: Neovim was compiled with tree-sitter runtime ABI version 14 (required >=13). Parsers must be compatible with runtime ABI.

## OS Info:
{
  machine = "x86_64",
  release = "5.17.15-76051715-generic",
  sysname = "Linux",
  version = "#202206141358~1655919116~22.04~1db9e34 SMP PREEMPT Wed Jun 22 19"
}

## Parser/Features H L F I J
  - go             ✓ ✓ ✓ ✓ ✓
  - help           x . . . x
  - cpp            ✓ ✓ ✓ ✓ ✓
  - python         ✓ ✓ ✓ ✓ ✓
  - rust           ✓ ✓ ✓ ✓ ✓
  - typescript     ✓ ✓ ✓ ✓ ✓
  - lua            ✓ ✓ ✓ ✓ ✓
  - c              ✓ ✓ ✓ ✓ ✓
  - vim            ✓ ✓ ✓ . ✓

  Legend: H[ighlight], L[ocals], F[olds], I[ndents], In[j]ections
         +) multiple parsers found, only one will be used
         x) errors found in the query, try to run :TSUpdate {lang}

## The following errors have been detected:
  - ERROR: help(highlights): /usr/local/share/nvim/runtime/lua/vim/treesitter/query.lua:219: query: invalid node type at position 424 for language help
    help(highlights) is concatenated from the following files:
    | [ERROR]:"/home/mgreco/.local/share/nvim/site/pack/packer/start/nvim-treesitter/queries/help/highlights.scm", failed to load: /usr/local/share/nvim/runtime/lua/vim/treesitter/query.lua:219: query: invalid node type at position 424 for language help
  - ERROR: help(injections): /usr/local/share/nvim/runtime/lua/vim/treesitter/query.lua:219: query: invalid node type at position 14 for language help
    help(injections) is concatenated from the following files:
    | [ERROR]:"/home/mgreco/.local/share/nvim/site/pack/packer/start/nvim-treesitter/queries/help/injections.scm", failed to load: /usr/local/share/nvim/runtime/lua/vim/treesitter/query.lua:219: query: invalid node type at position 14 for language help

provider: health#provider#check
========================================================================
## Clipboard (optional)
  - OK: Clipboard tool found: xclip

## Python 3 provider (optional)
  - WARNING: No Python executable found that can `import neovim`. Using the first available executable for diagnostics.
  - WARNING: Could not load Python 3:
    /usr/bin/python3 does not have the "neovim" module.
    /usr/bin/python3.10 does not have the "neovim" module.
    /usr/bin/python3.9 does not have the "neovim" module.
    python3.8 not found in search path or not executable.
    python3.7 not found in search path or not executable.
    python not found in search path or not executable.
    - ADVICE:
      - See :help |provider-python| for more information.
      - You may disable this provider (and warning) by adding `let g:loaded_python3_provider = 0` to your init.vim
  - INFO: Executable: Not found

## Python virtualenv
  - OK: no $VIRTUAL_ENV

## Ruby provider (optional)
  - INFO: Ruby: ruby 3.0.2p107 (2021-07-07 revision 0db68f0233) [x86_64-linux-gnu]
  - WARNING: `neovim-ruby-host` not found.
    - ADVICE:
      - Run `gem install neovim` to ensure the neovim RubyGem is installed.
      - Run `gem environment` to ensure the gem bin directory is in $PATH.
      - If you are using rvm/rbenv/chruby, try "rehashing".
      - See :help |g:ruby_host_prog| for non-standard gem installations.
      - You may disable this provider (and warning) by adding `let g:loaded_ruby_provider = 0` to your init.vim

## Node.js provider (optional)
  - INFO: Node.js: v18.12.1
  - WARNING: Missing "neovim" npm (or yarn, pnpm) package.
    - ADVICE:
      - Run in shell: npm install -g neovim
      - Run in shell (if you use yarn): yarn global add neovim
      - Run in shell (if you use pnpm): pnpm install -g neovim
      - You may disable this provider (and warning) by adding `let g:loaded_node_provider = 0` to your init.vim

## Perl provider (optional)
  - WARNING: "Neovim::Ext" cpan module is not installed
    - ADVICE:
      - See :help |provider-perl| for more information.
      - You may disable this provider (and warning) by adding `let g:loaded_perl_provider = 0` to your init.vim

telescope: require("telescope.health").check()
========================================================================
## Checking for required plugins
  - OK: plenary installed.
  - OK: nvim-treesitter installed.

## Checking external dependencies
  - OK: rg: found ripgrep 13.0.0
  - OK: fd: found fd 8.3.1

## ===== Installed extensions =====

vim.lsp: require("vim.lsp.health").check()
========================================================================
  - INFO: LSP log level : WARN
  - INFO: Log path: /home/mgreco/.local/state/nvim/lsp.log
  - INFO: Log size: 2 KB

vim.treesitter: require("vim.treesitter.health").check()
========================================================================
  - INFO: Runtime ABI version : 14
  - OK: Loaded parser for c: ABI version 13
  - OK: Loaded parser for cpp: ABI version 14
  - OK: Loaded parser for go: ABI version 14
  - OK: Loaded parser for lua: ABI version 13
  - OK: Loaded parser for python: ABI version 14
  - OK: Loaded parser for rust: ABI version 14
  - OK: Loaded parser for typescript: ABI version 14
  - OK: Loaded parser for vim: ABI version 14
  - OK: Loaded parser for c: ABI version 13
  - OK: Loaded parser for help: ABI version 14
  - OK: Loaded parser for lua: ABI version 13
  - OK: Loaded parser for vim: ABI version 14

Thanks for the repro steps -- I will check soon (hopefully today or  this weekend) and let you know what I find.

One thought I had is to put this:  ensure_installed = { 'c', 'cpp', 'go', 'help', 'lua', 'python', 'rust', 'typescript' }, in for the ensure_installed (i.e. add "help" to the list) and then make sure all the tree sitters are up-to-date as well.

yes!! adding 'help' into the list fixed the issue magically! ;-)


CMS API should supply images for omnisearch

The search API for CMS content does not provide images.  It should.

Implemented as https://github.com/gbif/gbif-drupal/commit/53f36c655b9c286816509941a0f0db93343518b7. Specification of images can be adjusted.


Add asset-manager

What
Add asset manager to test cluster
Reference
https://trello.com/c/pRBFWfGx/688-asset-manager-replatforming

OK, I'll update the yaml


How I use these gauges in my project? Can anyone give me some template.?

You could either take a look at the medusademo project or check the Demo.java file which is part of the Medusa library.

Answered


Errors registering Gauge with JMX

This issue is caused by using MXBeans instead of MBeans. Reverting 90396fc resolves this issue.
javax.management.NotCompliantMBeanException: com.yammer.metrics.reporting.JmxReporter$GaugeMXBean: Method com.yammer.metrics.reporting.JmxReporter$GaugeMXBean.getValue has parameter or return type that cannot be translated into an open type
Caused by: java.lang.IllegalArgumentException: Method com.yammer.metrics.reporting.JmxReporter$GaugeMXBean.getValue has parameter or return type that cannot be translated into an open type
	at com.sun.jmx.mbeanserver.ConvertingMethod.from(ConvertingMethod.java:32)
...
Caused by: javax.management.openmbean.OpenDataException: Cannot convert type: class java.lang.Object
	at com.sun.jmx.mbeanserver.OpenConverter.openDataException(OpenConverter.java:1411)
...
Caused by: javax.management.openmbean.OpenDataException: Can't map java.lang.Object to an open data type
	at com.sun.jmx.mbeanserver.OpenConverter.makeCompositeConverter(OpenConverter.java:454)

Dupe of #175.

Sorry about that, didn't see that issue!


Allow using ApiOperation on fields in addition to methods

Hi guys,
Could you please allow using ApiOperation on fields in addition to methods ?
The thing is that in Spray Framework (which now became Akka-Http) it's common to define routing table via defining nested constructions (e.g. http://spray.io/documentation/1.2.2/spray-routing/#longer-example).
It would be nice if I could put ApiOperation on val-s.
Currently I have to create bunch of dummy classes in separate package just to annotate them,

Do you use spray-swagger?

Yes. I'll fork and modify spray-swagger most likely to search for annotations on Scala val-s (currently it checks only top-level methods), but for that I'd need ApiOperation to have additional target.

Actually, you don't.
You can create your own annotation, and annotate with with @ApiOperation, and that should work for introspection.
I don't think it's a right step for us to add a target on fields as well. It doesn't make sense to any of the frameworks Swagger-Core supports, nor any other Java frameworks. My concern is that it'll end up confusing the users.

This won't work with the jaxrs implementation.  for other uses, it is very reasonable to annotate members.


Update reference versions

@pranavkm

Hi @BrennanConroy, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by .NET Foundation and real humans are currently evaluating your PR.
TTYL, DNFBOT;


FMWK-570 Add backup state/continuation for backup/restore operation

wip on state support

Codecov Report
Attention: Patch coverage is 63.82979% with 17 lines in your changes missing coverage. Please review.

Project coverage is 80.03%. Comparing base (8ce777b) to head (adf5d05).

Files with missing lines
Patch %
Lines

state.go
63.82%
10 Missing and 7 partials :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #158      +/-   ##
==========================================
- Coverage   80.18%   80.03%   -0.15%
==========================================
  Files          93       94       +1
  Lines        5172     5219      +47
==========================================
+ Hits         4147     4177      +30
- Misses        720      730      +10
- Partials      305      312       +7

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


kube version has a plus in the minor version string

The response from kubeVersion.Minor here will be e.g 16+ rather than 16. This means that strconv.ParseFloat fails, as 1.16+ cannot be properly parsed.
I'm creating an issue because I'm not certain of the best way to tackle this – do we just want to drop the +? Should we rely on GitVersion instead?
The advantage of GitVersion would be that we can do a proper semver compare, as versions like v1.16.6-beta.0 or v1.16.8-gke.15 are both valid SemVer versions, and can be properly compared against e.g "1.9". This would also make the Map.yaml a bit more readable as we could do "1.9" rather than "1.09" which looks a bit weird (after all, it is version 1.9).
Happy to PR this once there's some decision on how we want to do the version comparison :)

@phroggyy Thanks for raising this.
I didn't see the + in kubeVersion.Minor while adding the feature. I was however unhappy having to set "1.09" alright and was hoping to return to it when I got a chance. I wanted to deliver the feature first as it would be helpful to users.
I would be delighted if you want to push a PR for this. I am interested how you can compare with SemVer versions which would also hopefully remove need for conversations. Assigning it to you.

Sure, I'll have a look at this. From a quick glance it seems GitVersion should be reliable for a SemVer tag https://github.com/kubernetes/kubernetes/blob/master/hack/lib/version.sh#L70-L72 so I'll work off that.

I don't want to step on your toes @phroggyy, but I have a fix using GitVersion that compares the versions using the semver package and checks the version string's validity.

@flowjo-shaunr no toe stepping at all! That was exactly what I was going to do, beyond happy that someone else has already done the work 😄

Looking forward to whoever pushes the PR! 😄  Great stuff @phroggyy @flowjo-shaunr 👍

i've just came across this bug and tested the pr from @flowjo-shaunr
looks good so far.
but it still looks like some errors are just ignored like here (current master)
	kubeVersion, err := strconv.ParseFloat(kubeVersionStr, 32)
	if err != nil {
		errors.Wrap(err, "Failed to get Kubernetes server version")
	}

errors.Wrap returns an error which is ignored.. AFAIK this will not logged or fail the process

@eloo I reviewed the PR #28 and added comments there. Probably best add them in there, instead of the issue.

Thanks @flowjo-shaunr for pushing a PR for this. The addition of semver checking improves robustness and usability to the plugin. 👏


Just in sequence part 1.0.0

Description
Just-in-sequence (JiS) parts are parts that are made to order and delivered to a customer in a specific sequence to be built into the customer's product in the delivered sequence. Highly individualized parts like car seats or wiring harnesses are typically JiS-Parts. Some of them can't be identified by a serial number or a batch ID. But they can be identified by using a combination of their parent parts, the call-off numbers, and the call-off date used to order such a part.
Thus in order to improve the traceability of such parts, a combination of these keys is needed.
At the same time, some supply chain participants do not have a part ID (on part type level) for the individual variants of such parts, which is mandatory for serial parts. Because of this and also semantic considerations you can't reuse existing as-built models even if adapting them.
Closes #104

MS2 Criteria
(to be filled out by PR reviewer)

[ ] the model validates with the BAMM SDS SDK in the version specified in the Readme.md of this repository by the time of the MS2 check  (e.g., 'java -jar bamm-cli.jar -i <path-to-aspect-model> -v ). The  BAMM CLI is available here and in GitHub
[ ] use Camel-Case (e.g., "MyModelElement" or "TimeDifferenceGmtId", when in doubt follow https://google.github.io/styleguide/javaguide.html#s5.3-camel-case)
[ ] the identifiers for all model elements start with a capital letter except for properties
[ ] the identifier for properties starts with a small letter
[ ] all model elements at least contain the fields "name" and "description" in English language.
[ ] no duplicate names or preferredNames within an Aspect (e.g. a Property and the referenced Characteristic should not have the same name)
[ ] the versioning in the URN follows semantic versioning, where minor version bumps are backwards compatible and major version bumps are not backwards compatible.
[ ] use abbreviations only when necessary and if these are sufficiently common
[ ] avoid redundant prefixes in property names (consider adding properties to an enclosing Entity or even adapt the namespace of the model elements, e.g., instead of having two properties DismantlerId and DismantlerName use an Entity Dismantler with the properties name and id or use a URN like io.catenax.dismantler:0.0.1)
[ ] fields preferredName and description are not the same
[ ] preferredName should be human readable and follow normal orthography (e.g., no camel case but normal word separation)
[ ] name of aspect is singular except if it only has one property which is a Collection, List or Set. In theses cases, the aspect name is plural.
[ ] units are referenced from the BAMM unit catalog whenever possible
[ ] use constraints to make known constraints from the use case explicit in the aspect model
[ ] when relying on external standards, they are referenced through a "see" element
[ ] all properties with an simple type have an example value
[ ] metadata.json exists with status "release"
[ ] file RELEASE_NOTES.md exists and contains entries for proposed model changes

MS3 Criteria
(to be filled out by semantic modeling team before merge to main-branch)

[ ] All required reviewers have approved this PR (see reviewers section)
[ ] The new aspect (version) will be implemented by at least one data provider
[ ] The new aspect (version) will be consumed by at least one data consumer
[ ] There exists valid test data
[ ] In case of a new (incompatible) major version to an existing version, a migration strategy has been developed
[ ] The model has at least version '1.0.0'

modeling_team

camel case and pascal case is ok
names ok
description ok
metadata.json and release notes ok
not all property have examples

all good

[x] All required reviewers have approved this PR (see reviewers section)
[x] The new aspect (version) will be implemented by at least one data provider
[x] The new aspect (version) will be consumed by at least one data consumer
[x] There exists valid test data
[x] In case of a new (incompatible) major version to an existing version, a migration strategy has been developed
[x] The model has at least version '1.0.0'
@jacewski-bosch update copyright
other than that
MS3 approved please merge when copyright is updated @bs-jokri

@bs-jokri ready to merge (or rather fork and merge)

Superseded by #124


Revert "vendor: bump github.com/operator-framework/operator-sdk"

This reverts commit be81d55dd3c1a18308d27cb261263d0fa7256644.
This is done since bundle_builds are failing.
Signed-off-by: Rakshith R<EMAIL_ADDRESS>Refer: https://github.com/csi-addons/kubernetes-csi-addons/runs/5991350174?check_suite_focus=true#step:4:16
go build -o /home/runner/work/kubernetes-csi-addons/kubernetes-csi-addons/bin/operator-sdk ./vendor/github.com/operator-framework/operator-sdk/cmd/operator-sdk
# github.com/deislabs/oras/pkg/oras
Error: vendor/github.com/deislabs/oras/pkg/oras/push.go:52:31: not enough arguments in call to remotes.PushContent
	have (context.Context, remotes.Pusher, v1.Descriptor, "github.com/containerd/containerd/content".Store, nil, func(images.Handler) images.Handler)
	want (context.Context, remotes.Pusher, v1.Descriptor, "github.com/containerd/containerd/content".Store, *semaphore.Weighted, platforms.MatchComparer, func(images.Handler) images.Handler)
make: *** [Makefile:203: operator-sdk] Error 2

https://github.com/csi-addons/kubernetes-csi-addons/pull/144 is not sufficient
it still hits https://github.com/operator-framework/operator-sdk/issues/5574.
PTAL @csi-addons/kubernetes-csi-addons-contributors


Great Idea, but can't get it to work on the Mac.

This is such a great idea but I have no idea how to configure this on the Mac.
Outlook: Version 16.60 Mac
OS: Monterey Version 12.2.1
Model Name:	MacBook Pro
Model Identifier:	MacBookPro16,1
Processor Name:	8-Core Intel Core i9
Processor Speed:	2.3 GHz

It's not functioning right now, so it makes sense that it doesn't work. I've been too busy with thesis and personal life to work on this, sorry!

Good luck with your Thesis. I don't have the Node skills to help on this, unfortunately.  👍🏻


'overlay2' is not supported over overlayfs" storage-driver=overlay2 while using containerd ctr to run dind

Description

This is the error output of terminal

This is the cmd:
ctr --debug run --no-pivot --privileged --rm --net-host docker.io/library/docker:dind xxx
There is always one error "'overlay2' is not supported over overlayfs" storage-driver=overlay2 ". But I can run dind using docker normally. I changed containerd.service and snapshots/overlay.go but it doesn't work.

make sure you use a mount for /var/lib/docker for your container (not sure if containerd attaches one automatically)

make sure you use a mount for /var/lib/docker for your container (not sure if containerd attaches one automatically)

I am sorry but I am new to containerd. I find one directory "containerd" under /var/lib/docker. In this directory I found some containerd runtime file. But they should be produced last time I run dind using docker.  It seems not related.

What do you mean use a mount for this? Could you please tell me more specifically? Does dind must run on docker daemon even thou I am using containerd to start it?
Thank you very much!

oh, sorry, missed your last comment, but I see you got a reply here; https://github.com/containerd/containerd/issues/3158#issuecomment-479020472

oh, sorry, missed your last comment, but I see you got a reply here; #3158 (comment)

Yes,you answer also helps me a lot.


Generate configuration-metadata

Use @ConfigurationProperties so that metadata for the configuration options is
available and boots relaxed bindings can be used
This commit changes the semantics of batch.config.path-xml slightly as now the
full resource pattern, including 'classpath:' and '*.xml' has to be specified.
This commit renames some of the properties:
batch.config.path.xml --> batch.config.path-xml
batch.config.package.javaconfig --> batch.config.package-javaconfig
batch.defaultprotocol.enabled --> batch.default-protocol.enabled
batch.logfileseparation.enabled --> batch.logfile-separation.enabled
batch.core.pool.size --> batch.task-executor.core-pool-size
batch.max.pool.size --> batch.task-executor.max-pool-size
batch.queue.capacity --> batch.task-executor.queue-capacity
batch.repository.isolationlevelforcreate --> batch.repository.isolation-level-for-create
batch.repository.tableprefix --> batch.repository.table-prefix
Also Add the spring-boot-configuration-processor as optional dependency so that the
configuration-metadata will be generated.

Hm, changing property names and semantics is breaking backward compatibility. We should only do that on major releases.

@tobiasflohre Couldn't you publish a 1.4 when switching to boot 1.3?
If not, would it be ok to use the old property-names as aliases?

Included in 2.0.1.RELEASE


Some more inconsistency between can_cast_types  and cast_with_options

Describe the bug

There are more inconsistency between can_cast_types and cast_with_options that is cast_with_options can cast but can_cast_types reports false.
For example,

Casting from Dictionary of Integer to DecimalArray

thread 'test_can_cast_types' panicked at 'Was able to cast array DictionaryArray {keys: PrimitiveArray<Int8>
[
  0,
  1,
] values: PrimitiveArray<Int32>
[
  1,
  2,
]}
 from Dictionary(Int8, Int32) to Decimal128(38, 0) but can_cast_types reported false', arrow/tests/array_cast.rs:83:21

Casting from List of some type (e.g., Integer) to Dictionary of Utf8

thread 'test_can_cast_types' panicked at 'Was not able to cast array ListArray
[
  PrimitiveArray<Int32>
[
  0,
  1,
  2,
],
  PrimitiveArray<Int32>
[
  3,
  4,
  5,
],
  PrimitiveArray<Int32>
[
  6,
  7,
],
] from List(Field { name: "item", data_type: Int32, nullable: true, dict_id: 0, dict_is_ordered: false, metadata: {} }) to Dictionary(Int16, Utf8) but can_cast_types reported true. Error was CastError("Cannot cast list to non-list data types")', arrow/tests/array_cast.rs:87:21

To Reproduce

Expected behavior

Additional context

label_issue.py automatically added labels {'arrow'} from #3238


Remove the playground Lambda

Remove the playground lambda and the routing to it. We are no longer supporting playground. A request to javabuilder with playground as the mini app type will now return a 400.
Next Steps

Remove playground logic from code-dot-org
Remove playground logic from the build and run Lambda

LGTM! To confirm, what's the user experience on playground levels now? Will they just see the standard "We had an error connecting to our server" message?

@sanchitmalhotra126 yep they get the generic server error message. Since the course is deprecated now the only place they should be able to even run playground is the allthethings level (which we will remove soon).


Gnocchi Cleanup solves part of #25

Of the goals in #25, this PR covers the following (only in the code for the non-incremental methods and classes):

[x] Strip functionality that will not be in 0.1.0
[x] Fix tests to generate only temp files
[x] Clean out unnecessary comments, printlns, etc.
[x] Get rid of repeat code and refactor as necessary
[ ] Add documentation
[x] Correct license declarations at the top of each file
[x] Add readme

Can one of the admins verify this patch?

Closing in favor of #38.


CkoPhoneNumber coding key query

Hi.
Just wanted to query something I've noticed in the API contracts for registering a card in the payment flows (POST https://api.checkout.com/tokens).
The CkoAddress type (and other associated types, like CkoCardTokenRequest) is encoded using snake case keys (https://github.com/checkout/frames-ios/blob/master/Source/CkoAddress.swift), as can be seen in the Encodable implementation. addressLine1 becomes address_line1 for example.
However CkoPhoneNumber is not encoded with any custom CodingKeys (https://github.com/checkout/frames-ios/blob/master/Source/CkoPhoneNumber.swift) and will therefore take the standard swift case convention e.g. countryCode remains as countryCode.
Is this a known quirk on the API? Or maybe a bug in this SDK?

@adamwaite Thanks for raising this with us. We are aware of this now and we will plan to make a fix in the SDK with our next release. Thanks

Hey CkoAddress still implements CodingKeys, is that an edge case?

Also CkoCardTokenRequest

Hey @adamwaite, the update was a quick fix that just addressed the Codable objects that were causing errors. We'll work on improving the whole decoding/encoding logic for a future update. 🙂


Configure jenkins.fornever.me to build LogList and deploy on CTOR

Is depended on by #113

$ sbt clean compile dist

http://jenkins.fornever.me/job/loglist/

Oh my gosh!!  Thank you, uncle Never!!!


Add final_snapshot_identifier to rds

This allows rds resources to be destroyed. Currently, destroys fail with an error because we haven't specificed a name for the final snapshot.
rds-cluster has this already.

@tejasmanohar You'll also want to pull this in to your rds_replica branch because it's breaking the warehouse terracode builds.

What's the potential impact for existing RDS? Is it possible someone has set an existing final_snapshot_id already? I guess not since this module doesnt allow for it?

I will rebase my branch against master when this is merged

@tejasmanohar I'll go ahead and handle the merge in to your branch.

This is merged. Unfortunately any already-created rds modules will still need to be manually destroyed, but this will fix destroys for all new rds modules in the future.


Update README.md

Point to newer .Net version w/ reference in the Readme

AppVeyor build and test fail.

I have updated the readme with https://github.com/docusign/docusign-csharp-client/pull/243.
Closing this as redundant.


Error: Image not found: images/...

Source ticket: https://github.com/metanorma/metanorma-iso/issues/796
I'm trying to generate presentation XML for the document https://github.com/metanorma/iso-19135
bundle exec metanorma -t iso -x presentation document.adoc ended with created document.xml.abort and error:
(XML Line 004956): Image not found: images/D:/Work/Metanorma/repositories/iso-19135/sources/iso-19135-2021/images/lutaml/lutaml20220913-7144-s5djb6.png

	<name>Elements of the Register model</name>
	<image src="images/D:/Work/Metanorma/repositories/iso-19135/sources/iso-19135-2021/images/lutaml/lutaml20220913-7144-s5djb6.png" id="_54ab6cec-6beb-a71b-7050-6567f8f26a9d" mimetype="image/png" height="auto" width="auto"/>

(XML Line 005271): Image not found: images/D:/Work/Metanorma/repositories/iso-19135/sources/iso-19135-2021/images/lutaml/lutaml20220913-7144-9w030j.png

	<name>Identifiers in the Register</name>
	<image src="images/D:/Work/Metanorma/repositories/iso-19135/sources/iso-19135-2021/images/lutaml/lutaml20220913-7144-9w030j.png" id="_99edfe0f-11da-d423-9c2c-50d01a8850e3" mimetype="image/png" height="auto" width="auto"/>

(XML Line 005392): Image not found: images/D:/Work/Metanorma/repositories/iso-19135/sources/iso-19135-2021/images/lutaml/lutaml20220913-7144-48e0d4.png

	<name>Register item statuses and relationships</name>
	<image src="images/D:/Work/Metanorma/repositories/iso-19135/sources/iso-19135-2021/images/lutaml/lutaml20220913-7144-48e0d4.png" id="_6a528a0e-8487-7109-c1b7-cfe0074c8310" mimetype="image/png" height="auto" width="auto"/>

(XML Line 005570): Image not found: images/D:/Work/Metanorma/repositories/iso-19135/sources/iso-19135-2021/images/lutaml/lutaml20220913-7144-cd4c0k.png

	<name>Proposal and Appeal</name>
	<image src="images/D:/Work/Metanorma/repositories/iso-19135/sources/iso-19135-2021/images/lutaml/lutaml20220913-7144-cd4c0k.png" id="_19688494-dc26-50b0-4100-ff3e066c5143" mimetype="image/png" height="auto" width="auto"/>

The file D:/Work/Metanorma/repositories/iso-19135/sources/iso-19135-2021/images/lutaml/lutaml20220913-7144-9w030j.png physically is present on the disk, but there is a strange prefix images/ before D:/Work.
It seems this issue occurs on Win platform only: https://github.com/metanorma/iso-19135/actions/runs/3040514350/jobs/4896647319

I think this may be an image processing problem after the incorporation of pngcheck. Ping @opoudjis .

Some investigation - see https://github.com/metanorma/metanorma-iso/issues/796#issuecomment-1245306704.

The paths in the src should be relative, not absolute.
(https://github.com/metanorma/metanorma-cli/issues/255)
For instance, in the presentation XML generated on Ubuntu (found in /home/testuser/iso-19135/sources/iso-19135-2021/), instead of
<image src="/home/testuser/iso-19135/sources/iso-19135-2021/images/lutaml/lutaml20220913-4327-zyjutc.png"

expected:
<image src="./images/lutaml/lutaml20220913-4327-zyjutc.png"

I think I know what happened with images prefix: D:/ not being recognised as an absolute path in metanorma-utils.

What changed is @ronaldtse taking it upon himself to refactor metanorma-utils in https://github.com/metanorma/metanorma-utils/commit/aee97aca2b89e749d5dcc48c421fdb79be7b70ed , and introducing several bugs in the process, including this.
@ronaldtse I have enough to do already without you destroying functioning code. You also committed that code without giving me the opportunity to review it. This is not acceptable, and I will revert any future commits you make to Metanorma code if you have not first discussed them with me. Only PRs are acceptable.

@opoudjis with latest metanorma-utils commit '3803557a36d3...' I get the error:
Fatal Error: undefined local variable or method `uri' for Metanorma::Utils:Module

          warn "Image specified at `#{uri}` does not exist."
                                       ^^^

Did you mean?  URI
C:/tools/ruby31/lib/ruby/gems/3.1.0/bundler/gems/metanorma-utils-3803557a36d3/lib/utils/image.rb:140:in `datauri1': undefined local variable or method `uri' for Metanorma::Utils:Module (NameError)

          warn "Image specified at `#{uri}` does not exist."\r

Did you mean?  URI

        from C:/tools/ruby31/lib/ruby/gems/3.1.0/bundler/gems/metanorma-utils-3803557a36d3/lib/utils/image.rb:135:in `datauri'
        from C:/tools/ruby31/lib/ruby/gems/3.1.0/bundler/gems/metanorma-standoc-35e26a016582/lib/metanorma/standoc/cleanup_image.rb:67:in `block in img_cleanup'

The problem with the latest crash is @opoudjis artificially split a method that is not supposed to be split:
https://github.com/metanorma/metanorma-utils/commit/7f20637a2be8853e449aa3703646285584f6b2a5#diff-365195b15b8cb4ad83fe5e25c64e72b0206de119661460ea4a5ad8752e345a5aR138-R142
That these "method splits" should not happen and is representative of poor practice.

That these "method splits" should not happen and is representative of poor practice.

I'm not the one who decided 10 lines per method is good practice.

Hotfix metanorma-utils released, @Intelligent2013

@opoudjis the current behavior you committed does not generate datauri for an absolute file path. See the correct fix at https://github.com/metanorma/metanorma-utils/pull/24 with specs.


Forbid unsafe code

png does not seem to use unsafe code, which is very good :)
And is great for an image library!
To prevent this from ever happening, add following line to the top:
#![forbid(unsafe_code)]

of https://github.com/image-rs/image-png/blob/master/src/lib.rs
Other workspace like https://github.com/image-rs/image-png/blob/master/png-afl/src/main.rs could also use this if you want to (and if possible).
This will make the package green in
https://github.com/anderejd/cargo-geiger

I'm in favor of this. Want to create a pull request?

Okay, I'll create a pull request.


[Question]: flink 1.14 能用吗？

If the question is concise and probably has a short answer, asking it in community Slack
Question
Environment

OS Version and CPU Arch(uname -a):

Component Version:

目前应该是不行的，在九月正式release前会验证一下，以最终的readme描述为准吧。


Doesn't work probably the URL incorrect

Extension accesses: https://console.aws.amazon.com/*
My logs are at: https://eu-west-2.console.aws.amazon.com/*
So this may be why it doesn't work. Nice idea though.

Good catch!
The version 1.3 should fix the issue, let me know if it does not.


publish error: etcdserver: request timed out when receiving big snapshot message

2015-10-28 22:46:14.604404 I | raft: raft.node: 87db82abb8b7e0d5 elected leader c93f463cb660f225 at term 8
2015-10-28 22:46:21.593053 E | etcdserver: publish error: etcdserver: request timed out, possibly due to previous leader failure
2015-10-28 22:46:28.593314 E | etcdserver: publish error: etcdserver: request timed out
2015-10-28 22:46:35.593572 E | etcdserver: publish error: etcdserver: request timed out
2015-10-28 22:46:42.593792 E | etcdserver: publish error: etcdserver: request timed out
2015-10-28 22:46:49.594016 E | etcdserver: publish error: etcdserver: request timed out

It should print better log messages.
follow #2370

I think this is fine since it only prints out every 5 seconds. Also we can tell from the log that it was receiving a snapshot, which might cause a commit delay on the server.
A solution I can think of is to disable timeout warning when receiving snapshot. But I think it is overkill.


部署qwen-vl的自定义模型时，哪怕选择了qwen-vl-chat，页面风格还是大语言模型的风格，而不是多模态有图片上传的

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
To help us to reproduce this bug, please provide information below:

Your Python version.
The version of xinference you use.
Versions of crucial packages.
Full stack of the error.
Minimized code to reproduce the error.

Expected behavior
A clear and concise description of what you expected to happen.
Additional context
Add any other context about the problem here.

自定义还没支持选择 vl 的功能，近期会开发支持

Actually, I tried downloading the qwen-vl-chat model, and upon the initial launch, the displayed interface was llama-2-7b-chat. However, when I reran xinference-local, the interface appeared normal.
And I noticed that when downloading the qwen-vl-chat model, the llama-2 model was also downloaded simultaneously.
The running model interface of the qwen-vl model is normal.

This should not be a problem for the latest version, close it first, feel free to reopen if you have any issue.


Please only keep your main project in the root folder

Currently you have a few different folders for different versions. GIT Version control was made for this.

Since this is a school project, I need to show my progression to the teacher during my assessment. If I put the different versions in branches, I'm not able to show them via GitHub Pages.