[NetAppFiles ]Anf 18545 rotterdam phase2 2021 12 01 preview

The changes in this PR where reviewed on the private repo and synced with latest main here.  This adds a new preview api version.
https://github.com/Azure/azure-rest-api-specs-pr/pull/5709
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Changelog
Add a changelog entry for this PR by answering the following questions:

What's the purpose of the update?

[ ] new service onboarding
[x] new API version
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month.
When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.
If updating an existing version, please select the specific language SDKs and CLIs that must be refreshed after the swagger is published.

[ ] SDK of .NET (need service team to ensure code readiness)
[ ] SDK of Python
[ ] SDK of Java
[ ] SDK of Js
[ ] SDK of Go
[ ] PowerShell
[ ] CLI
[ ] Terraform
[ ] No refresh required for updates in this PR

Contribution checklist:

[x] I commit to follow the Breaking Change Policy of "no breaking changes"
[x] I have reviewed the documentation for the workflow.
[x] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

Applicability: :warning:
If your changes encompass only the following scenarios, you should SKIP this section, as these scenarios do not require ARM review.

Change to data plane APIs
Adding new properties
All removals

Otherwise your PR may be subject to ARM review requirements. Complete the following:

[ ] Check this box if any of the following apply to the PR so that label "WaitForARMFeedback" will be added automatically to begin ARM API Review. Failure to comply may result in delays to the manifest.

Adding a new service
Adding new API(s)
Adding a new API version
-[ ] To review changes efficiently, ensure you are using OpenAPIHub to initialize the PR for adding a new version. More details, refer to the wiki.

[ ] Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If any of the following scenarios apply to the PR, request approval from the Breaking Change Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in a stable version
[ ] Removing properties in a stable version
[ ] Removing API version(s) in a stable version
[ ] Updating API in a stable or public preview version with Breaking Change Validation errors
[ ] Updating API(s) in public preview over 1 year (refer to Retirement of Previews)

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.

/azp run

/azp run

/azp run

@raych1 can we get this PR moving the changes here are in a preview api version and where reviewed in the private repo.  https://github.com/Azure/azure-rest-api-specs-pr/pull/5709

.

ping

@audunn , next time please use the publish PR link to publish the PR reviewed in private repo so that the review here can be fast.
I saw this PR has 6 more file changes than the PR in private repo. What's that change?
Please also resolve the conflicts.

@raych1 did not know of this button thank you will use next time should make thinks simpler. Thank you.

"/subscriptions/{subscriptionId}/providers/Microsoft.NetApp/locations/{location}/regionInfo": {

This URI format specifies a collection of instances of the type regionInfo, so the response should be an array. If regionInfo doesn't actually behave like a resource type, you should consider using POST instead. If it does behave like a resource type, it should be modeled as named instances of the regionInfo resource type with the full complement of CRUD operations (GET/PUT/collection GET/DELETE/PATCH).

Refers to: specification/netapp/resource-manager/Microsoft.NetApp/preview/2021-12-01-preview/netapp.json:295 in 9be46d5. [](commit_id = 9be46d54bcb7f1ab5da845e5e34c9891d8984262, deletion_comment = False)

"/subscriptions/{subscriptionId}/providers/Microsoft.NetApp/locations/{location}/queryNetworkSiblingSet": {

From looking at the definitions for these payloads, it seems like sibling set does behave more like an ARM resource type (has a name/id, has query and update operations). Did you consider modeling as a resource type with standard ARM CRUD operations?

Refers to: specification/netapp/resource-manager/Microsoft.NetApp/preview/2021-12-01-preview/netapp.json:332 in 9be46d5. [](commit_id = 9be46d54bcb7f1ab5da845e5e34c9891d8984262, deletion_comment = False)

@audunn - Looks like this PR got into my queue before WaitForARMReview was removed. I left some comments related to ARM review before noticing the label was gone. Please consider those comments in any subsequent PRs or updates.

@audunn , can you resolve conflicts and resolve the CI check errors(lintDiff)?
In addition, can you get breaking change review approval for the change of changing default value? see cross version breaking change errors.


Add support for Python 3.13

See https://github.com/GoogleCloudPlatform/cloud-sql-python-connector/pull/1177 for reference.

Also https://www.python.org/downloads/release/python-3130/

Also, we should match Cloud SQL and drop Python 3.8. See https://github.com/GoogleCloudPlatform/cloud-sql-python-connector/pull/1176.

Python 3.13 was added in asyncpg 0.30.0 so once #375 is merged this should be good to go

After #375 is merged, do we need to modify setup.py so that its asyncpg version is >= 0.30.0?: https://github.com/GoogleCloudPlatform/alloydb-python-connector/blob/main/setup.py#L80

After #375 is merged, do we need to modify setup.py so that its asyncpg version is >= 0.30.0?: https://github.com/GoogleCloudPlatform/alloydb-python-connector/blob/main/setup.py#L80

That is a good question and one that I have been thinking about. Since we don't pin to a specific version, if the asyncpg package is not already installed in the environment pip will download the latest version by default, so fresh Python 3.13 installs would get 0.30.0 automatically with our current setup.
However since we are planning to document native asyncpg pool support with the Connector #382 which was also added in v0.30.0 then I think between the two of these it is worth pinning to >=0.30.0 in setup.py.
For Cloud SQL I am going to pin to v0.30.0 as part of adding native connection pool examples.

I agree with you. I'll also pin to v0.30.0 as part of adding native connection pool examples in #382

Looks like this was linked to the dropping of Python 3.8 PR by accident


Patchwork fix for Windows dev. environment.

 No idea why it works on Mac the way it is, though.
More info:
http://stackoverflow.com/questions/33307399/unity3d-project-crashes-vscode
https://code.visualstudio.com/issues/detail/20069

This fixes problems with crashing. Thanks @Taugeshtu

@reapazor any comments?


Python3 support

Fixed HMAC initialization for using in Python3.
Fix tests.

Thanks! I'll take a look and get hopefully merge this week

Thanks a lot!

What do you think about it?

yup, I am actually re-factoring my build environment, so I'll update PyPi in the new year.

Thanks a lot!


[FLINK-14553][runtime] Respect non-blocking output in StreamTask#processInput

What is the purpose of the change
The non-blocking output was introduced in FLINK-14396 and FLINK-14498 to solve the problem of handling the checkpoint barrier in the case of backpressure.
In order to make the whole process through, StreamInputProcessor should be allowed to process input elements if the output is also available.
The default core size of LocalBufferPool for ResultPartition should also be increased by 1 for two considerations:

StreamTask can only process input if there is at-least one available buffer on output side, so it might cause stuck problem if the minimum pool size is exactly equal to the number of subpartitions, because every subpartition might maintain a partial unfilled buffer.

Increases one more buffer for every output LocalBufferPool to void performance regression if processing input is based on at-least one buffer available on output side.

Brief change log

Rename AvailabilityProvider#isAvailable as AvailabilityProvider#getAvailableFuture
Refactor ResultPartitionWriter interface to abstract class
Refactor AvailabilityProvider to provide default #isAvailable and #isVolatileAvailable methods
*Adjust StreamTask stack to consider output status while processInput
Increase one more minimum size for output LocalBufferPool

Verifying this change
Some new unit tests would be added later after confirming the core process make sense.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (yes / no)
The serializers: (yes / no / don't know)
The runtime per-record code paths (performance sensitive): (yes / no / don't know)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (yes / no / don't know)
The S3 file system connector: (yes / no / don't know)

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

Note: I would add some new tests for covering the changes later after confirming the core process make sense to do so.

Thanks for the review and good suggestions @pnowojski !
Concerning of refactor of getAvailableFuture() and isAvailable(), I explained my thought in inline comments.
I remembered there were some discussions for this issue before. But now I find it is not very convenient to judge the available state via checking whether the future is completed or not in some cases. Because the returned CompleteFuture is mainly used for callback action, but if we only want to know the current state and do not need the requirement of monitoring the state for callback in some cases, then the previous way is heave-weight to some extent.
I agree it would bring some overheads for outside implementations like SourceReader. But if we can explain the semantics of two methods clearly, then they can be orthogonal.

I think this PR can not be merged until we fix/migrate the back-pressure monitor to use the availability future?

Exactly, it seems not much conflicts to prelaunch this PR, so I focus on it firstly and the back-pressure monitor would be done by yingjie.

I updated the codes for addressing previous comments.
I would also supplement a itcase for verifying the non-blocking effect for small records scenario later, and I also try to add new tests to verify the method of RecordWriterDelegate#close if possible.

Thanks for the further review @AHeise !
I appended a fixup commit for addressing some comments.


ENHANCEMENT NEEDED IN "TESTIMONIALS" SECTION #1823

Fixes:  #1823
Description
so basically i just MANIPULATE the "TESTIMONIALS" SECTION   IN HOME PAGE which gives the interactive interface for going  smoothly. This page deals with to collecting reviews from users regarding your website.  Transitions ,keyframes are used in these making it more interactive and the the things are unable to show in one picture just go and check  out  the transitions for hovering effects if you like the designing then  please rate it as "level3" or "level 2" label 👍 .
AS I ADDED:-

redesign the  cards
provide eye catching colors on hovering
interactive hovering
change the  approach of designing
ADD HOVER EFFECTS
ADD TRANSITIONS
BUILD A interactive user interface
and many more you need to check it out

ENHANCEMENT NEEDED IN "TESTIMONIALS" SECTION #1823

[ ] Bug fix
[x] Feature enhancement
[ ] Documentation update
[ ] Other (specify): _______________

Screenshots / videos (if applicable)
--BEFORE:-

--AFTER:-

Checklist:

[x] I have made this change from my own.
[x] My code follows the style guidelines of this project.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generate no new warnings.
[x] I have tested the changes thoroughly before submitting this pull request.
[x] I have provided relevant issue numbers and screenshots after making the changes.

@PriyaGhosal KINDLY MERGE MY PR AND LET ME KNOW IF THERE IS ANY ISSUE

@PriyaGhosal KINDLY MERGE MY PR AND LET ME KNOW IF THERE IS ANY ISSUE


Disable search for redirect (quickfix for discord redirect)

Changes

...

Checklist

[x] Read the contribution guide and accept the code of conduct
[ ] Readme (updated or not needed)
[ ] Tests (added, updated or not needed)

📝Changed routes:

/discord

(view full size)

Commit 3f4900f7a214a71be3229d7c8477b0b6b0681e9c (https://website-jsf4ixmx1.vercel.app).


Epic | Dark/light theme

Based on theme control styling should be changed.

[x] Initial setup of dark and light theme
[x] POC for applying styles.
[ ] Apply the styling for all controls.
[x] Check the possibility for custom theme

Added the initial setup files for light and dark themes to support both modes.
Custom theme also supports.
Applied theme setup for button control.


BUG: Pages are not properly linked.

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
The pages such as PrivacyPolicy, Licensing and TermsandConditions are not properly linked. On clicking, the NotFound page gets loaded instead. Kindly assign me this issue.
https://github.com/VanshKing30/FoodiesWeb/assets/154075283/cc383d57-ae8b-414e-89ad-5ac10b171c4e
Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

ok start working on this


After actions like open the door, remove guard the map stops saving data

Affected Scenario(s): [e.g. testet with 1,2]
Describe the bug
After actions (which required additional menu selection) like opening the door, remove guard the map stops saving data. It means that if I refresh the board all changes move to the position before making this menu action.
Same with people observing it in a pro version from another device. (before buying pro was the same problem)
but in Android this totally blocks us from moving but may be the same root cause
Tested on Mac/Win/Android
Browsers: Chrome, Safari
To Reproduce
Steps to reproduce the behavior:

Open 1 scenario, for example: https://vgb.purplekingdomgames.com/?lockRoomCode=1&lockScenario=1&scenario=1&seed=76531240
2.1 if you move character and refresh the browser all data is saved correctly
2.2. BUT if you click on door and select Open (or click on guard and select Remove)
After refresh it is not saved

Hmmmm... this seems to be exclusively a Chrome bug 🙁 We're actually in the middle of a complete upgrade to the VGB so I'm fairly certain this will go away when that's released. I'll keep this issue open, but will reference it in #99 so that we remember to check it before that goes live.
Worth mentioning I think (as this leads to some confusion) that we are completely separate to the Gloomhaven Storyboard App and only really provide integration to it, so your tier of plan there won't affect any of the features of the VGB (which is free)

Hi @kbubnovich , I've just had a thought actually... do you have any characters selected at all (menu, then 'Change Players)?
I've been playing around with this and I can replicate it in Firefox and Chrome if I have no players selected at all, but I can't replicate it in other circumstances. Let me know, and hopefully it'll be an easy fix 🤞

Hi, thanks for the quick reply, just checked in Firefox and it is not reproduceble there so finally we will be able to play :) so with this workaround i'm already happy)
and yes 2 players selected and in chrome on android/mac/windows there are still problems.


Issues with Pixel Segment Code

Variables are not directly copied to the correct location. They are first allocated with temporary device variables, and then manually copied in the kernel (addPixelSegmentToMemory device function).
https://github.com/SegmentLinking/TrackLooper/blob/cff3eda1228855233f5be55620aee06c0d3464b5/SDL/Event.cu#L830-L846

SegmentsInGPU is allocated with a large constant amount of space, instead of using the correct "size" variable.
https://github.com/SegmentLinking/TrackLooper/blob/cff3eda1228855233f5be55620aee06c0d3464b5/SDL/Event.cu#L765-L768

createMDArrayRanges and createSegmentArrayRanges both make the mistake of pulling variables from the GPU, computing some quantities on the CPU, and then pushing the results back to the GPU instead of just calculating everything directly on the GPU.
https://github.com/SegmentLinking/TrackLooper/blob/4015cfcb67b215aee3eaf990e4ab4d3135392c1f/SDL/Segment.cu#L32-L103

Issue 3 is now fixed by #272, thank you @tresreid!

...And I believe that issue 2 is a necessary evil, as showcased in PR #342. Should we close this? @GNiendorf


Alert display fixed

lgtm

Generating Alerts

@pilhuhn @garg-anuj Please review these major changes.

@pg301 sorry for delay :wink:


fix(validate): get non-namespace scoped resources

Description
Updates some of the logic to identify which resources are cluster-scoped, and allow those that are to be reduced by name.
Related Issue
Fixes #409
Type of change

[X] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Other (security config, docs update, etc)

Checklist before merging

[X] Test, docs, adr added or updated as needed
[ ] Schema Updates applied
[ ] Contributor Guide Steps followed

I am appreciative of the thoroughness for checking if the resource is namespaced.
While I am likely not considering some edge cases you have ran into - I want to play devils advocate for a second. a non-namespaced resource must have a unique name for all same resources. Given a resource name being defined in the kubernetes domain resource item - this is a non-problem (to my understanding) - as we can assume a non-namespaced & named resource would be unique.
but the problem here lies in namespaced items not being unique across the cluster - could we instead change reduceByName to collect all instances and error when > 1? preventing additional network activity for ever single resource I believe?

could we instead change reduceByName to collect all instances and error when > 1?

I think yeah, this would work. I think perhaps this change in logic would just result in less error fidelity - for instance:
If a user requests a named pod and no-namespace specified - In one case if there is only one pod matching the name in the cluster, they will get a result. If for some reason the cluster changes and now there's two pods, same name, different namespaces, then the same request will result in an error. If we had know that "pod" should require a namespace the first time around, then that resource-rule would have been blocked properly.
I don't love the request to the server to to find if something is namespace scoped, so I think it's probably just a tradeoff that could go either way.
The only other things I could think of to solve this would be breaking, but some other options could be:

request cluster-scoped tag (probably default to false so most validations wouldn't need to add it)
return the full list of all matching named things, regardless of namespace - also breaking since we currently only assume one item is returned

I think actually the third alternative here is to just use the Get method on the dynamic client instead of list, as that seems to handle all of this natively... will explore and update the PR

Agreed on the tradeoffs discussion - worth framing through the lens of "which would we want to support in production?"
Which behaviors are going to require the least amount of adaptation in the event of failure. A validation requiring update could be annoying yet would provide a more stable validation over time.

return the full list of all matching named things, regardless of namespace - also breaking since we currently only assume one item is returned

Another flavor of this I am still noodling on for implications would be the idea of returning a list if many or a single if one (given the generic interface).

Ok I updated as follows

Removed the reduceByName and isClusterScoped functions in favor of dynamic's Get - as mentioned this seems like the more native solution
Updated the test cases, both adding ones that should fail and one for a cluster-scoped resource request
Updated the schema - I removed the rule that namespaces should be specified if name is for resource-rule - if a namespaced resource is requested without a namespace, the Get will fail anyway, so not sure this needs to be in the schema since for cluster-scoped ones it's an invalid assumption. I also had to make the type one of "array" or "null" to handle where namespaces is just not set at all. I think that was a gap before because it always failed when it wasn't defined, regardless of if it was actually needed. I don't believe this breaks anything but could be missing something.

Quick augmentation of the tests for the added failure validations would be nice to check the observations for specific errors versus simply not-satisfied findings.

What are you thinking for this one? My initial thought is that you're wanting me to validate all the remarks are equal to some string for each of the failure cases? If thats the case this may require more than a little rework, just checking before I go forth

Quick augmentation of the tests for the added failure validations would be nice to check the observations for specific errors versus simply not-satisfied findings.

What are you thinking for this one? My initial thought is that you're wanting me to validate all the remarks are equal to some string for each of the failure cases? If thats the case this may require more than a little rework, just checking before I go forth

That was my thought but open to that being a separate issue if necessary. I see a variety of different scenarios in the failure cases (which is good) that have resulted in findings being listed as not-satisfied but the observations range from errors at various different points and some Validations being evaluated and others not-evaluated.
It would be nice to trace a known error handling scenario is actually hitting the intended handling target.

It would be nice to trace a known error handling scenario is actually hitting the intended handling target.

Yeah I agree, I don't love that they're all not satisfied without knowing the reason... I also feel like checking the remarks text is also potentially a little too blunt an instrument. I think maybe having like an error code returned and checking that might be better? But yeah I would probably say that should be a separate issue and would require a little bit of time to architect properly


I want to verify my contract, but the terminal prompts me that I have two suitable contracts, what should I do

I want to verify my contract, but the terminal prompts me that I have two suitable contracts, what should I do

Can you:

Make this a discusson on the full repo? https://github.com/smartcontractkit/full-blockchain-solidity-course-js/
Follow this section for formatting questions? https://www.youtube.com/watch?t=19846&v=gyMwXuJrbJQ&feature=youtu.be


add Series.duration/3

Closes #568
Closes #581
Hi, so I've taken a stab at #568, but I think I need some feedback. Here are a couple of things I'd like to confirm or unsure of:

If we had gone for diff(s1, s2) it suggests that s1 > s2, but for duration(s1, s2) it would be sensible to have it s1 < s2 right? As in it is 'the duration from and to'.
At the moment it's one function to do :datetime, :date and :time, and we can do cross-dtype comparison. The default for :date is 00:00 time and for :time it is 1970/01/01. I don't know if we want to enforce a same-dtype constraint.
System.time_unit()only defines ns, us, ms and s. This is what I've gone for too, but I thought it would be convenient to have minute, hour, day and week. What do you think?

Awesome work @anthony-khong!
What is the dtype of a duration? The duration can be stored in different time units, so that plays a role. Perhaps this is a good opportunity to introduce parameterized dtypes, such as {:duration, :nanosecond}, and eventually we would do the same for datetime. We need to make sure that Series.dtype, Series.from_list and all conversion functions, such as Series.to_binary, can handle durations as well.

This is a good question and I could not find prior art, which may mean we don't want to add a duration function and instead add a diff-like function? Remember we will also need operations to add a duration to an date/time/datetime, so maybe we should consider the naming of both functions. We could also always overload add/subtract but it won't feel very Elixir-like.

I would keep Elixir semantics here: we can cast date to datetime and we can cast time to datetime, but nothing more.

I see no issue with providing all of those. In fact, I would even say we don't force any interval in particular, going with the highest possible for a given different is likely the best approach

Given this will likely turn out to be bigger task and there is more work to be done as it adds a new dtype, I am wondering if we should break this in parts:

Change :datetime dtype to be {:datetime, time_unit} (as listed here). Change all conversion functions to handle datetimes with different time units. This can then be used as template for...

Introduce a new :duration dtype with encoding/decoding but without necessarily adding new functions.

Add operations that can receive/return durations

WDYT?

Hi José, thanks for the feedback!

Given this will likely turn out to be bigger task and there is more work to be done as it adds a new dtype, I am wondering if we should break this in parts:

I think having a duration dtype is better than what we have here, as it would be more obvious. The task breakdown also makes sense, but I may not currently have the time to work on it in the coming weeks. Let me close this PR for now, just because it's not going in the same direction, and link the original issue back to your comment. I'll pick it back up when I have the time if it's not already done!
Thanks again José!


Can't receive event in global child component which event is emit in router beforeEach method.

Vue.js version
2.0.2
Steps to reproduce
router.beforeEach((to, from, next) => {
	bus.$emit('test');
        .......
});

What is Expected?
receive event in child component。
What is actually happening?
received nothing,because the event is not sticky.when it is emit,the child component may not be created.

This is expected behavior, you actually explained it yourself.

any plan to support sticky event in Vue2.0 eventbus?


Implement Noise Handshake (BOLT8)

This implements the Noise handshake protocol as per BOLT8 as per Issue134. This PR mostly uses the BOLT8 handshake structures implemented here, which is refactored to suit our needs.
Following are brief descriptions of modules in src/lnp/session/noise/ directory
act: This describes the handshake action structures as defined in BOLT8.
chacha: Encryption and Decryption functions for ChaCha20Poly1305 AEAD encryption.
hkdf: Key derivation functions as defined in BOLT8
conduit: Connection conduit that has read buffer and implements automatic key rotation as per BOLT8. This structure is also implemented with Transcode and Bipolar to make the API compatible with other parts of the library.
handshake: The Handshake states and their transition logic as per BOLT8.
This is more or less self contained at this moment. The Noise module is private and none of the functionalities are used elsewhere.
A previous noise.rs file which had basic AEAD examples has been removed.
Test cases are included to indicate the proper functioning of the module.
Open to suggestion on how to properly credit the above PR author in rust-lightning.

Just would like to know to thank @julianknutsen and let him know that we used the code he wrote for rust-lightning (but was never accepted) in our rust Lighting Network Protocol implementation (which is otherwise independent from the rust-lightning).
This implementation is used in lightning node https://github.com/LNP-BP/lnp-node by LNP/BP Standards association, designed specially for supporting such projects as RGB, DLCs and future LN extensions (eltoo, PTLCs etc).
CC @Tibo-lg

I appreciate the call out and good luck with the project. I'm glad the code found a good use case here and that it was able to help the larger LDK community.


[BUG] Chibisafe throws Server Error

I used your Dockerfile to build a local docker image. I dont need the nginx part because i use the linuserver/swag nginx for my setup. So i build the image and got some Warnings. The Image seems to start and chibisafe should running.
if i try to open it on my subdomain, i got the following error
Server error
An error occurred in the application and your page could not be served. If you are the application owner, check your logs for details.

Docker Logs says:
Backend ready and listening on port 5000

Error occurred when calling nuxtServerInit:  Request failed with status code 403

 ERROR  Request failed with status code 403

  at createError (node_modules/axios/lib/core/createError.js:16:15)

  at settle (node_modules/axios/lib/core/settle.js:17:12)

  at Unzip.handleStreamEnd (node_modules/axios/lib/adapters/http.js:260:11)

  at Unzip.emit (events.js:400:28)

  at Unzip.emit (domain.js:475:12)

  at endReadableNT (internal/streams/readable.js:1334:12)

  at processTicksAndRejections (internal/process/task_queues.js:82:21)

The nginx config looks like this:
server {
    listen 443 ssl;
    listen [::]:443 ssl;

    server_name safe.xxxxx.net;

    include /config/nginx/ssl.conf;

    client_max_body_size 0;

    # enable for ldap auth, fill in ldap details in ldap.conf
    #include /config/nginx/ldap.conf;

    # enable for Authelia
    #include /config/nginx/authelia-server.conf;

    location / {
        # enable the next two lines for http auth
        #auth_basic "Restricted";
        #auth_basic_user_file /config/nginx/.htpasswd;

        # enable the next two lines for ldap auth
        #auth_request /auth;
        #error_page 401 =200 /ldaplogin;

        # enable for Authelia
        #include /config/nginx/authelia-location.conf;

        include /config/nginx/proxy.conf;
        include /config/nginx/resolver.conf;
        set $upstream_app <IP_ADDRESS>;
        set $upstream_port 5000;
        set $upstream_proto http;
        proxy_pass $upstream_proto://$upstream_app:$upstream_port;

    }
}

And my Env's looks like this:
OVERWRITE_SETTINGS=false
CHUNK_SIZE=90
ROUTE_PREFIX=/api
RATE_LIMIT_WINDOW=2
RATE_LIMIT_MAX=5
BLOCKED_EXTENSIONS=.jar,.exe,.msi,.com,.bat,.cmd,.scr,.ps1,.sh
SECRET=*****************************************
MAX_LINKS_PER_ALBUM=5
META_THEME_COLOR=#20222b
META_DESCRIPTION=XxXxXxX - Blazing fast file bunker! 🚀
META_KEYWORDS=XxXxXxX
SERVER_PORT=5000
DOMAIN=http://safe.xxxxxxxxx.net
SERVICE_NAME=XxXxXxX
MAX_SIZE=5000
GENERATE_THUMBNAILS=true
GENERATE_ZIPS=true
STRIP_EXIF=true
SERVE_WITH_NODE=true
GENERATED_FILENAME_LENGTH=6
GENERATED_ALBUM_LENGTH=4
PUBLIC_MODE=false
USER_ACCOUNTS=true
ADMIN_ACCOUNT=SomeUserName
ADMIN_PASSWORD=**************************
DB_CLIENT=sqlite3
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
NODE_VERSION=14.19.0
YARN_VERSION=1.22.17

I dont know much about node so i need some help and adjustments to get it running.
<3 Thank you ;)
FULL LOG:
><EMAIL_ADDRESS>migrate /usr/chibisafe

> knex migrate:latest

Already up to date

><EMAIL_ADDRESS>seed /usr/chibisafe

> knex seed:run

=========================================================

==       admin account already exists, skipping.       ==

=========================================================

==    Run `pm2 start pm2.json` to start the service    ==

=========================================================

Ran 1 seed files

><EMAIL_ADDRESS>start /usr/chibisafe

> npm run migrate && nuxt build && cross-env NODE_ENV=production node src/api/structures/Server

><EMAIL_ADDRESS>migrate /usr/chibisafe

> knex migrate:latest

Already up to date

ℹ Production build

ℹ Bundling for server and client side

ℹ Target: server

✔ Builder initialized

✔ Nuxt files generated

 WARN  Browserslist: caniuse-lite is outdated. Please run:

npx browserslist@latest --update-db

Why you should do it regularly:

https://github.com/browserslist/browserslist#browsers-data-updating

ℹ Compiling Client

DEPRECATION WARNING: Using / for division outside of calc() is deprecated and will be removed in Dart Sass 2.0.0.

Recommendation: math.div($value, 255) or calc($value / 255)

More info and automated migrator: https://sass-lang.com/d/slash-div

   ╷

70 │     $value: $value / 255

   │             ^^^^^^^^^^^^

   ╵

    node_modules/bulma/sass/utilities/functions.sass 70:13   colorLuminance()

    node_modules/bulma/sass/utilities/functions.sass 80:8    findColorInvert()

    src/site/assets/styles/_bulma_colors_extender.scss 7:20  @import

    src/site/assets/styles/style.scss 2:9                    @import

    src/site/layouts/default.vue 64:9                        root stylesheet

DEPRECATION WARNING: Using / for division outside of calc() is deprecated and will be removed in Dart Sass 2.0.0.

Recommendation: math.div($value + 0.055, 1.055) or calc(($value + 0.055) / 1.055)

More info and automated migrator: https://sass-lang.com/d/slash-div

   ╷

74 │       $value: ($value + .055) / 1.055

   │               ^^^^^^^^^^^^^^^^^^^^^^^

   ╵

    node_modules/bulma/sass/utilities/functions.sass 74:15   colorLuminance()

    node_modules/bulma/sass/utilities/functions.sass 80:8    findColorInvert()

    src/site/assets/styles/_bulma_colors_extender.scss 7:20  @import

    src/site/assets/styles/style.scss 2:9                    @import

    src/site/layouts/default.vue 64:9                        root stylesheet

DEPRECATION WARNING: Using / for division outside of calc() is deprecated and will be removed in Dart Sass 2.0.0.

Recommendation: math.div($value, 12.92) or calc($value / 12.92)

More info and automated migrator: https://sass-lang.com/d/slash-div

   ╷

72 │       $value: $value / 12.92

   │               ^^^^^^^^^^^^^^

   ╵

    node_modules/bulma/sass/utilities/functions.sass 72:15          colorLuminance()

    node_modules/bulma/sass/utilities/functions.sass 80:8           findColorInvert()

    node_modules/bulma/sass/utilities/derived-variables.sass 16:20  @import

    node_modules/bulma/sass/utilities/_all.sass 6:9                 @import

    src/site/assets/styles/style.scss 6:9                           @import

    src/site/layouts/default.vue 64:9                               root stylesheet

DEPRECATION WARNING: Using / for division outside of calc() is deprecated and will be removed in Dart Sass 2.0.0.

Recommendation: math.div(-1, 2) or calc(-1 / 2)

More info and automated migrator: https://sass-lang.com/d/slash-div

   ╷

76 │       +ltr-property("margin", calc(#{-1 / 2 * $button-padding-horizontal} - #{$button-border-width}), false)

   │                                      ^^^^^^

   ╵

    node_modules/bulma/sass/elements/button.sass 76:38  @import

    node_modules/bulma/sass/elements/_all.sass 5:9      @import

    node_modules/bulma/bulma.sass 5:9                   @import

    src/site/assets/styles/style.scss 16:9              @import

    src/site/layouts/default.vue 64:9                   root stylesheet

DEPRECATION WARNING: Using / for division outside of calc() is deprecated and will be removed in Dart Sass 2.0.0.

Recommendation: math.div($button-padding-horizontal, 4) or calc($button-padding-horizontal / 4)

More info and automated migrator: https://sass-lang.com/d/slash-div

   ╷

77 │       +ltr-property("margin", $button-padding-horizontal / 4)

   │                               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

   ╵

    node_modules/bulma/sass/elements/button.sass 77:31  @import

    node_modules/bulma/sass/elements/_all.sass 5:9      @import

    node_modules/bulma/bulma.sass 5:9                   @import

    src/site/assets/styles/style.scss 16:9              @import

    src/site/layouts/default.vue 64:9                   root stylesheet

WARNING: 37 repetitive deprecation warnings omitted.

✔ Client: Compiled successfully in 25.79s

ℹ Compiling Server

DEPRECATION WARNING: Using / for division outside of calc() is deprecated and will be removed in Dart Sass 2.0.0.

Recommendation: math.div($value, 255) or calc($value / 255)

More info and automated migrator: https://sass-lang.com/d/slash-div

   ╷

70 │     $value: $value / 255

   │             ^^^^^^^^^^^^

   ╵

    node_modules/bulma/sass/utilities/functions.sass 70:13   colorLuminance()

    node_modules/bulma/sass/utilities/functions.sass 80:8    findColorInvert()

    src/site/assets/styles/_bulma_colors_extender.scss 7:20  @import

    src/site/assets/styles/style.scss 2:9                    @import

    src/site/layouts/default.vue 64:9                        root stylesheet

DEPRECATION WARNING: Using / for division outside of calc() is deprecated and will be removed in Dart Sass 2.0.0.

Recommendation: math.div($value + 0.055, 1.055) or calc(($value + 0.055) / 1.055)

More info and automated migrator: https://sass-lang.com/d/slash-div

   ╷

74 │       $value: ($value + .055) / 1.055

   │               ^^^^^^^^^^^^^^^^^^^^^^^

   ╵

    node_modules/bulma/sass/utilities/functions.sass 74:15   colorLuminance()

    node_modules/bulma/sass/utilities/functions.sass 80:8    findColorInvert()

    src/site/assets/styles/_bulma_colors_extender.scss 7:20  @import

    src/site/assets/styles/style.scss 2:9                    @import

    src/site/layouts/default.vue 64:9                        root stylesheet

DEPRECATION WARNING: Using / for division outside of calc() is deprecated and will be removed in Dart Sass 2.0.0.

Recommendation: math.div($value, 12.92) or calc($value / 12.92)

More info and automated migrator: https://sass-lang.com/d/slash-div

   ╷

72 │       $value: $value / 12.92

   │               ^^^^^^^^^^^^^^

   ╵

    node_modules/bulma/sass/utilities/functions.sass 72:15          colorLuminance()

    node_modules/bulma/sass/utilities/functions.sass 80:8           findColorInvert()

    node_modules/bulma/sass/utilities/derived-variables.sass 16:20  @import

    node_modules/bulma/sass/utilities/_all.sass 6:9                 @import

    src/site/assets/styles/style.scss 6:9                           @import

    src/site/layouts/default.vue 64:9                               root stylesheet

DEPRECATION WARNING: Using / for division outside of calc() is deprecated and will be removed in Dart Sass 2.0.0.

Recommendation: math.div(-1, 2) or calc(-1 / 2)

More info and automated migrator: https://sass-lang.com/d/slash-div

   ╷

76 │       +ltr-property("margin", calc(#{-1 / 2 * $button-padding-horizontal} - #{$button-border-width}), false)

   │                                      ^^^^^^

   ╵

    node_modules/bulma/sass/elements/button.sass 76:38  @import

    node_modules/bulma/sass/elements/_all.sass 5:9      @import

    node_modules/bulma/bulma.sass 5:9                   @import

    src/site/assets/styles/style.scss 16:9              @import

    src/site/layouts/default.vue 64:9                   root stylesheet

DEPRECATION WARNING: Using / for division outside of calc() is deprecated and will be removed in Dart Sass 2.0.0.

Recommendation: math.div($button-padding-horizontal, 4) or calc($button-padding-horizontal / 4)

More info and automated migrator: https://sass-lang.com/d/slash-div

   ╷

77 │       +ltr-property("margin", $button-padding-horizontal / 4)

   │                               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

   ╵

    node_modules/bulma/sass/elements/button.sass 77:31  @import

    node_modules/bulma/sass/elements/_all.sass 5:9      @import

    node_modules/bulma/bulma.sass 5:9                   @import

    src/site/assets/styles/style.scss 16:9              @import

    src/site/layouts/default.vue 64:9                   root stylesheet

WARNING: 37 repetitive deprecation warnings omitted.

✔ Server: Compiled successfully in 8.83s

Hash: fa84012f50ef16b233c3

Version: webpack 4.46.0

Time: 25789ms

Built at: 02/02/2022 6:07:17 PM

                                                                                Asset       Size  Chunks                                Chunk Names

                                                                                ../server/client.manifest.json   33.9 KiB          [emitted]

                                                                                0155224.js   50.2 KiB      23  [emitted] [immutable]         vendors/pages/index

                                                                                048e880.js   6.42 KiB       5  [emitted] [immutable]         pages/a/_identifier

                                                                                0c9d795.js   5.83 KiB       7  [emitted] [immutable]         pages/dashboard/admin/file/_id

                                                                                269a95c.js   3.01 KiB      18  [emitted] [immutable]         pages/login

                                                                                2e30f75.js   20.8 KiB       0  [emitted] [immutable]         pages/a/_identifier/pages/dashboard/admin/user/_id/pages/dashboard/albums/_id/pages/dashboard/index

                                                                                30883af.js   4.07 KiB      14  [emitted] [immutable]         pages/dashboard/index

                                                                                3c5c78e.js   11.3 KiB       8  [emitted] [immutable]         pages/dashboard/admin/settings

                                                                                3f414f5.js   27.8 KiB       1  [emitted] [immutable]         vendors/pages/a/_identifier/pages/dashboard/admin/user/_id/pages/dashboard/albums/_id/pages/dashboard/index

                                                                                3f4bdba.js   9.07 KiB       9  [emitted] [immutable]         pages/dashboard/admin/statistics

                                                                                48523dd.js   2.89 KiB      16  [emitted] [immutable]         pages/faq

                                                                                665ea05.js   5.62 KiB      21  [emitted] [immutable]         runtime

                                                                                79ce550.js   18.5 KiB       2  [emitted] [immutable]         pages/dashboard/albums/_id/pages/dashboard/index

                                                                                7cd02b1.js   6.16 KiB      10  [emitted] [immutable]         pages/dashboard/admin/user/_id

                                                                                7ef9f8b.js   87.8 KiB       3  [emitted] [immutable]         app

                                                                                80cc466.js   6.99 KiB       6  [emitted] [immutable]         pages/dashboard/account

                                                                                92c8422.js  519 bytes      19  [emitted] [immutable]         pages/logout

                                                                                946061b.js   8.14 KiB      11  [emitted] [immutable]         pages/dashboard/admin/users

                                                                                LICENSES   1.07 KiB          [emitted]

                                                                                app.b00a7a7.css    624 KiB       3  [emitted] [immutable]  [big]  app

                                                                                beec9c8.js   2.96 KiB      20  [emitted] [immutable]         pages/register

                                                                                c42f890.js    191 KiB       4  [emitted] [immutable]         commons/app

                                                                                c4e04c7.js   10.7 KiB      17  [emitted] [immutable]         pages/index

                                                                                dbee12e.js   18.7 KiB      13  [emitted] [immutable]         pages/dashboard/albums/index

                                                                                f15883c.js    307 KiB      22  [emitted] [immutable]  [big]  vendors/app

                                                                                f253a87.js   4.09 KiB      12  [emitted] [immutable]         pages/dashboard/albums/_id

                                                                                f964b62.js   6.58 KiB      15  [emitted] [immutable]         pages/dashboard/tags/index

                                                                  fonts/materialdesignicons-webfont.3d1f8fa.eot    982 KiB          [emitted]              [big]

                                                                  fonts/materialdesignicons-webfont.3e722fd.ttf    981 KiB          [emitted]              [big]

                                                                fonts/materialdesignicons-webfont.4187121.woff2    312 KiB          [emitted]              [big]

                                                                 fonts/materialdesignicons-webfont.fec1b66.woff    446 KiB          [emitted]              [big]

                                                                                img/background.4a227cd.jpg   73.7 KiB          [emitted]

                                                                                img/blank.daa9806.png   1.44 KiB          [emitted]

                                                                                img/logo.a61651d.png     11 KiB          [emitted]

                                                                                pages/a/_identifier.c6aaeb9.css  548 bytes       5  [emitted] [immutable]         pages/a/_identifier

pages/a/_identifier/pages/dashboard/admin/user/_id/pages/dashboard/albums/_id/pages/dashboard/index.8a817a7.css   3.09 KiB       0  [emitted] [immutable]         pages/a/_identifier/pages/dashboard/admin/user/_id/pages/dashboard/albums/_id/pages/dashboard/index

                                                                            pages/dashboard/account.53158bf.css  257 bytes       6  [emitted] [immutable]         pages/dashboard/account

                                                                     pages/dashboard/admin/file/_id.c3991d3.css  311 bytes       7  [emitted] [immutable]         pages/dashboard/admin/file/_id

                                                                     pages/dashboard/admin/settings.a0fa9f4.css  814 bytes       8  [emitted] [immutable]         pages/dashboard/admin/settings

                                                                   pages/dashboard/admin/statistics.40b9093.css  571 bytes       9  [emitted] [immutable]         pages/dashboard/admin/statistics

                                                                     pages/dashboard/admin/user/_id.aee17cc.css  311 bytes      10  [emitted] [immutable]         pages/dashboard/admin/user/_id

                                                                        pages/dashboard/admin/users.60e0839.css    2.3 KiB      11  [emitted] [immutable]         pages/dashboard/admin/users

                                                                         pages/dashboard/albums/_id.2bd807b.css  295 bytes      12  [emitted] [immutable]         pages/dashboard/albums/_id

                                                   pages/dashboard/albums/_id/pages/dashboard/index.5b39451.css  325 bytes       2  [emitted] [immutable]         pages/dashboard/albums/_id/pages/dashboard/index

                                                                       pages/dashboard/albums/index.cb9f048.css   2.74 KiB      13  [emitted] [immutable]         pages/dashboard/albums/index

                                                                              pages/dashboard/index.93736b0.css  189 bytes      14  [emitted] [immutable]         pages/dashboard/index

                                                                         pages/dashboard/tags/index.3cfa1dd.css    2.2 KiB      15  [emitted] [immutable]         pages/dashboard/tags/index

                                                                                pages/faq.e32dd9b.css   55 bytes      16  [emitted] [immutable]         pages/faq

                                                                                pages/index.f426ced.css   12.1 KiB      17  [emitted] [immutable]         pages/index

 + 2 hidden assets

Entrypoint app [big] = 665ea05.js c42f890.js f15883c.js app.b00a7a7.css 7ef9f8b.js

WARNING in asset size limit: The following asset(s) exceed the recommended size limit (244 KiB).

This can impact web performance.

Assets:

  fonts/materialdesignicons-webfont.4187121.woff2 (312 KiB)

  fonts/materialdesignicons-webfont.fec1b66.woff (446 KiB)

  fonts/materialdesignicons-webfont.3d1f8fa.eot (982 KiB)

  fonts/materialdesignicons-webfont.3e722fd.ttf (981 KiB)

  app.b00a7a7.css (624 KiB)

  f15883c.js (307 KiB)

WARNING in entrypoint size limit: The following entrypoint(s) combined asset size exceeds the recommended limit (1000 KiB). This can impact web performance.

Entrypoints:

  app (1.19 MiB)

      665ea05.js

      c42f890.js

      f15883c.js

      app.b00a7a7.css

      7ef9f8b.js

Hash: 12b4cd985cf59265d8e3

Version: webpack 4.46.0

Time: 8829ms

Built at: 02/02/2022 6:07:26 PM

                              Asset      Size  Chunks             Chunk Names

             pages/a/_identifier.js  52.9 KiB       1  [emitted]  pages/a/_identifier

         pages/dashboard/account.js  12.6 KiB       2  [emitted]  pages/dashboard/account

  pages/dashboard/admin/file/_id.js  15.1 KiB       3  [emitted]  pages/dashboard/admin/file/_id

  pages/dashboard/admin/settings.js  21.7 KiB       4  [emitted]  pages/dashboard/admin/settings

pages/dashboard/admin/statistics.js  26.7 KiB       5  [emitted]  pages/dashboard/admin/statistics

  pages/dashboard/admin/user/_id.js  54.1 KiB       6  [emitted]  pages/dashboard/admin/user/_id

     pages/dashboard/admin/users.js    17 KiB       7  [emitted]  pages/dashboard/admin/users

      pages/dashboard/albums/_id.js  99.9 KiB       8  [emitted]  pages/dashboard/albums/_id

    pages/dashboard/albums/index.js  35.2 KiB       9  [emitted]  pages/dashboard/albums/index

           pages/dashboard/index.js  97.1 KiB      10  [emitted]  pages/dashboard/index

      pages/dashboard/tags/index.js  16.7 KiB      11  [emitted]  pages/dashboard/tags/index

                       pages/faq.js  6.73 KiB      12  [emitted]  pages/faq

                     pages/index.js  28.3 KiB      13  [emitted]  pages/index

                     pages/login.js  5.36 KiB      14  [emitted]  pages/login

                    pages/logout.js  1.27 KiB      15  [emitted]  pages/logout

                  pages/register.js  4.74 KiB      16  [emitted]  pages/register

                          server.js   138 KiB       0  [emitted]  app

               server.manifest.json  2.11 KiB          [emitted]

 + 17 hidden assets

Entrypoint app = server.js server.js.map

ℹ Ready to run nuxt start

   ╭──────────────────────────────────────────────────────────────────────────────────────╮

   │                                                                                │

   │   ⚠ Nuxt Warning                                                                     │

   │                                                                                │

   │   The command 'nuxt build' finished but did not exit after 5s                        │

   │   This is most likely not caused by a bug in Nuxt                                    │

   │   Make sure to cleanup all timers and listeners you or your plugins/modules start.   │

   │   Nuxt will now force exit                                                           │

   │                                                                                │

   │   DeprecationWarning: Starting with Nuxt version 3 this will be a fatal error        │

   │                                                                                │

   ╰──────────────────────────────────────────────────────────────────────────────────────╯

Found route POST /api/admin/ban/ip

Found route GET /api/admin/file/:id

Found route POST /api/admin/unban/ip

Found route POST /api/admin/users/demote

Found route POST /api/admin/users/disable

Found route POST /api/admin/users/enable

Found route GET /api/admin/users/:id

Found route POST /api/admin/users/promote

Found route POST /api/admin/users/purge

Found route GET /api/admin/users

Found route DELETE /api/album/:id

Found route POST /api/album/edit

Found route GET /api/album/:id/full

Found route GET /api/album/:identifier

Found route POST /api/album/new

Found route DELETE /api/album/:id/purge

Found route GET /api/album/:identifier/zip

Found route GET /api/albums/mini

Found route GET /api/albums/dropdown

Found route DELETE /api/album/link/delete/:identifier

Found route POST /api/album/link/edit

Found route POST /api/album/link/new

Found route GET /api/album/:id/links

Found route POST /api/auth/login

Found route POST /api/auth/register

Found route POST /api/file/album/add

Found route POST /api/file/album/del

Found route DELETE /api/file/:id

Found route GET /api/file/:id

Found route GET /api/file/:id/albums

Found route GET /api/files

Found route POST /api/file/tag/addBatch

Found route POST /api/file/tag/add

Found route POST /api/file/tag/del

Found route GET /api/search/

Found route GET /api/service/config/all

Found route GET /api/service/config

Found route POST /api/service/config

Found route GET /api/service/config/schema

Found route POST /api/service/restart

Found route GET /api/service/statistics/:category?

Found route GET /api/version

Found route DELETE /api/tag/:id/:purge?

Found route POST /api/tag/new

Found route GET /api/tags

Found route POST /api/upload

Found route POST /api/user/apikey/change

Found route POST /api/user/password/change

Found route GET /api/users/me

Found route GET /api/verify

Backend ready and listening on port 5000

Error occurred when calling nuxtServerInit:  Request failed with status code 403

 ERROR  Request failed with status code 403

  at createError (node_modules/axios/lib/core/createError.js:16:15)

  at settle (node_modules/axios/lib/core/settle.js:17:12)

  at Unzip.handleStreamEnd (node_modules/axios/lib/adapters/http.js:260:11)

  at Unzip.emit (events.js:400:28)

  at Unzip.emit (domain.js:475:12)

  at endReadableNT (internal/streams/readable.js:1334:12)

  at processTicksAndRejections (internal/process/task_queues.js:82:21)

Dart Sass deprecation warnings shouldn't result in Nuxt's "Service Error" page.

Error occurred when calling nuxtServerInit:  Request failed with status code 403

I see only one nuxtServerInit in store, and it does 2 requests:

GET /service/config
GET /auth/verify

The 2nd call is wrapped in try...catch so shouldn't throw
The 1st one shouldn't return 403 according to { bypassAuth: true } and Route implementation
No part of the related code have been modified in at least 5 months, it is strange no one reported the issue before. Are there any major changes in your custom config compared to the default one?

sorry for the late response, i dont change anything on the config or dockerfile. i only use the ENV's

I had the same problem today. I hope it will be fixed soon. But I have the problem outside of docker.

This is happening to me as well. I don't use docker and get this error.

I'm closing this since the new version was just pushed to master.


Any chance of releasing the new Beta anytime soon?

Hi Marcel,
The new XCode is available so I was wondering if you will be releasing the new beta anytime soon.
I really miss setting the default values in the current beta.
Thanks in advance.
Robert

Done. v1.2.2beta2 :grin:
Sometimes life takes precedence and I can't release new versions. But the difficult times are hopefully over and I'm back in action. Expect the final release of 1.2.2 soon!

Thanks!


Searching in a PR finds results in deleted files

Open https://github.dev/roblourens/testrepo/pull/3
Search "hello"
I get results in readme.md, which is deleted in that PR

Tested with https://github.dev/JacksonKearl/RollDice-Discord/pull/15, can no longer reproduce.


Basic unit test structure for SimplePolicyPlugin (2)

Guys, I did some progress in creating basic unit testing for SimplePolicyPlugin. Using this, we will be able to easily test if transaction policies are being respected, even on compile time.
I created a simple configuration example with maximum 10 transactions and 3 free.

Waiting for #10


Doesn't work in Bootstrap 4.0.0

For modal, the ui bootstrap doesn't work for the Bootstrap V4.0.0.
V3.3.7
.fade {...} .fade.in{}
V4.0.0
.fade{} .fade.show{}, Don't use the class 'in'
Could you please fix it, thanks very much!

This project is finished.

Closing this as this project is no longer being maintained, per the README and the ISSUE_TEMPLATE.


GML encoding of code lists

In the meeting on 21 October 2021 we discussed the GML encoding of code lists.

The code lists should be kept simple, i.e. they should only contain codes with associated code descriptions.

In addition, metadata information should be added to the code lists, in particular metadata attributes for the language of the code list, the CityGML data type to which the code list refers and the CityGML version.
-> This information is enough to allow for providing code lists for the same data type in different languages. These language specific code lists contain the same codes, but the descriptions are provided in different languages.
-> In this way, by means of the metadata information also the code lists in other languages can be identified, even if the CityGML file refers to a code list in a specific language only.

The code lists are to be represented using GML 3.2.1 dictionaries.
-> Metadata information can be added to the dictionaries by means of a <gml:metaDataProperty> element.
-> The <gml:identifier> element can be used for the code.
-> the <gml:name> element can be used for the description, also in different languages as the element has multiplicity "unbounded".

We also discussed about providing a CSV encoding in addition.
The CSV files should contain three columns.
The first column indicates whether the row contains a code or metadata.
The second column contains the code or name of the metadata attribute.
The third column contains the code description or the metadata value.
-> When a code value in a CityGML instance links to an external code list, the encoding of the external code list can be determined based on the suffix .gml or .csv.
-> The code lists could then simply be managed using Excel.

Homework tasks:

Claus will check whether CityGML 2 code lists will validate against GML 3.2.1
Thomas and Tatjana will provide an example for a code list encoded as csv file

The NGA maintains a registry of codelists designed for run-time access from GML documents.  It is located at https://nsgreg.nga.mil/voc/registers.jsp?register=CDV. The intent of this register is to remove the codelist values from the data model, managing them as a separate resource. Codelist values are identified in a GML document through a URI. That URI consists of the URI for the register, followed by the codelist name, followed by the codelist value. An advantage of this approach is that the codelist value is resolvable to a definition of that value.

The European Commission's INSPIRE Code Lists are managed at https://inspire.ec.europa.eu/codelist towards a similar (the same?) result.
The preferred approach from the GML documents is an encoding like this:

Where the URI goes "straight to" the required code list value; the xlink:title provides a utility value for those parsers who do not want to dereference the URI. (Some schemas allow the element to also have text content carrying a national translation of the code list value). The definition can be retrieved in various formats by dereferencing the URI.

@PeterParslow The registers are comparable.  The difference is how the code list values are encoded. While INSPIRE uses xlinks, NGA uses gco:CodeListValue_Type. Here is an example (from gmd:CI_ResponsibleParty in ISO 19115):
gmd:role
<gmd:CI_RoleCode codeList="http://api.nsgreg.nga.mil/codelist/RoleCode" codeListValue="originator"/>
</gmd:role>
Both approaches work. It would be best to pick one and use it consistently. Do the ISO schemas we use push us toward one over the other?

@cmheazel : I have to ask "which ISO schemas?"

Sorry for dropping the ball on codelists. Even though I was tied up in another SWG at the time, I did do some prototyping for the 21 October meeting. My suggestion was for

an implementation-independent logical model

a "neutral" archive format editable with basic tools e.g. a Json text file

a web service that
a. validates and loads an archive for a specified domain e.g. CityGML 3.0
b. serves individual codelists in whatever (multiple) encodings we choose

a static file store in an OGC domain with materialized versions of all registered codelists in all supported encodings

a utility to periodically refresh the static file store

All code list values are encoded using gml:CodeType. Thus, we can use XLinks to reference a codelist just like in INSPIRE and in previous versions of CityGML. We do not mandate how the codelist values shall be stored and managed. So, using a registry like NGA does and referencing this registry via an URI would be perfectly fine. If there is no (local, regional, nation-wide, global, what-so-ever) registry, then codelists can also be stored as files and these files can be referenced via URIs. For this case, we want to define two encodings: a GML encoding and a CSV encoding. So, for instance, if users want to provide their codelists as GML files, they shall use the specified GML encoding (which is just the default GML 3.2.1 encoding for dictionaries). If they want to share them as Excel files, they need to make sure that consumers can read and understand them.
I think this approach is very lightweight as we can neither manage nor define a global registry for all CityGML users and use cases. And, it is very in line with how CityGML 2.0 and 1.0 work.

I have made some progress in prototyping this, using some 2.0 codelists as a starting point.
CityGML_3.0_CodelistDomainJson.txt
AuxiliaryTrafficAreaFunctionValueXML.txt
AuxiliaryTrafficAreaFunctionValueJSON.txt

I am also happy with Claus' comment. See you soon.

Thanks for your thoughts, @3DXScape. I would welcome having a third predefined JSON encoding.

In our web meeting on 18 November 2021 we discussed that each code list should have the following metadata information

the data type to which the code list refers
XML namespace of the corresponding CityGML module in which the code list is defined. The CityGML 3 conceptual model currently does not define code lists with duplicate names in different modules. But this information will be helpful for ADEs that will be defined in the future and that might have duplicate names.
the language in which the descriptions of the code values are provided
the authority/issuer of the code list
the version of the code list, this could be a date or version number

GML does not provide a content model for the metadata. We need to define our own UML class with the required metadata attributes and encode it in XML to be able to add the metadata to the GML code lists.
-> Tatjana will check how to do this with ShapeChange.
Furthermore, we discussed that we do not intend to specify the encoding of code lists in a normative way.
As in the CityGML 2.0 specification, we will rather include a chapter on the encoding of code lists that provides users and developers with examples on how code lists can be encoded in the formats GML, CSV, and JSON. These code lists can serve as templates for users who want to define their own code lists.
We will try to provide non-empty code lists for all code lists defined in the conceptual model. These code lists will only serve as examples, they will not provide exhaustive lists of possible code list values. These code lists may be used by others, but everybody is still free to create their own code lists.
Setting up a registry for the code lists and defining a REST API to access the code list values are tasks that our group cannot deal with as part of the GML encoding specification.

The results from the web meeting on 15 December 2021.
Metadata for code lists
We discussed the following slides on the encoding of the metadata information that is to be provided with each code list: https://github.com/opengeospatial/CityGML-3.0Encodings/blob/master/CityGML/Encoding Rules/Metadata for code lists.pdf
We agreed on making use of option 2, i.e. providing our own container element for the metadata information.
The XML schema for the metadata is available here:
https://github.com/opengeospatial/CityGML-3.0Encodings/blob/master/CityGML/Schema/codeListMetaData.xsd
Code list structure
We agreed on the following CityGML 3.0 codelist structure:
<gml:Dictionary gml:id="roofTypes">
    <gml:metaDataProperty>
        <cmd:CodeListMetaData>
            <cmd:dataType>RoofTypeValue</cmd:dataType>
            <cmd:namespace>http://www.opengis.net/citygml/building/3.0</cmd:namespace>
            <cmd:language>en</cmd:language>
            <cmd:authority>xyz</cmd:authority>
            <cmd:version>1.0</cmd:version>
        <cmd:CodeListMetaData>
    </gml:metaDataProperty>
    <gml:description>Roof type values</gml:description>
    <gml:identifier codeSpace="https://ogc.org/citygml/3.0/codelists/gml/rooftypes">RoofTypeValue</gml:identifier>
    <gml:dictionaryEntry>
        <gml:Definition gml:id="id1">
            <gml:description>roof primarily a single plane, not necessarily level</gml:description>
            <gml:identifier codeSpace="https://ogc.org/citygml/3.0/codelists/gml/rooftypes">1000</gml:identifier>
            <gml:name>flat roof</gml:name>
        </gml:Definition>
    </gml:dictionaryEntry>
    <gml:dictionaryEntry>
        <gml:Definition gml:id="id2">
            <gml:description>a roof that has a ridge and two gables</gml:description>
            <gml:identifier codeSpace="https://ogc.org/citygml/3.0/codelists/gml/rooftypes">3100</gml:identifier>
            <gml:name>saddle roof</gml:name>
        </gml:Definition>
    </gml:dictionaryEntry>
</gml:Dictionary>

For the individual code list entries we defined the following:

gml:description: can be used to provide a textual description of the code, is optional
gml:identifier: contains the code, the code is unique within the code list, the code can be a number or a string
gml:name: provides a human-readable representation of the code, is optional and should be provided when the code is given as a number

@3DXScape I had a look at the chapter on ADEs and have some comments and questions.

What is the purpose of providing an XML schema for the code lists? As far as I understood from our discussions, we intend to use GML Dictionaries for representing code lists. And for GML Dictionaries an XML schema already exists. It's not mentioned in the chapter that we use the predefined GML Dictionaries.
Is the intention of the XML schema that users can validate their code lists instances against the schema?
Why a new element <Codelist> as root element and not the existing GML element <gml:Dictionary>?
The elements <gml:identifier> and <gml:name> for the individual code list entries are currently defined as mandatory in the XML schema. We once discussed that only <gml:identifier> should be mandatory and <gml:name> optional. <gml:identifier> does not necessarily need to contain a code value, but can instead also contain a text value and in that case it is not required to provide the text value in the <name> element as well. The same for the <gml:description> element, this should also be optional. See also my comment above from December.
Also, we have created an XML schema for the metadata. This schema is not mentioned in the chapter. The metadata elements have now become part of the new XML schema for code lists. And a new <Metadata> element is introduced that will contain the metadata information. Does that mean that we do not make use of the <gml:metaDataProperty> element any more in the code list GML instances? The instance provided in the chapter, however, still uses the <gml:metaDataProperty> element.

Regarding the metadata elements:

Should the metadata elements be shortly explained? I think it would make sense.
The metadata element <version> was defined as xs:string in the metadata XML schema, because we said that the value could be a date or version number. Now it's defined as xs:decimal.
The metadata element <namespace> was defined as xs:anyURI in the metadata XML schema, now it's defined as xs:string.

I noted down several things from the meeting where we discussed code lists. Would it make sense to provide these things as recommencations?

The dictionary must always have a gml:id
The <gml:identifier> element contains the code and is mandatory, the <gml:name> element contains a human-readable representation of the code. But the gml:name element is only required, when the code is a numeric code.
The gml:description element can be used for additional descriptions of the code, but is optional.
Always the same code space should be used for the whole dictionary and the individual entries.
Code lists can be extended by referencing external code lists.
In the GML instance document, the codespace links to a code list file or API.

The CSV example is completely different from what @thomashkolbe and I suggested some time ago.
We have sent this by e-mail some time ago. It's this file:
Codelist_BuildingClassValue_en.csv
We probably should discuss this further.

I will realign the chapter as you describe. We should review the results at the next meeting.

What is the purpose of providing an XML schema for the code lists? As far as I understood from our discussions, we intend to use GML Dictionaries for representing code lists. And for GML Dictionaries an XML schema already exists. It's not mentioned in the chapter that we use the predefined GML Dictionaries.

Good point. I ignored the details of the discussion. I originally wanted an XML encoding not tied to external schemas. I will use the GML Dictionary as it is in 3.2.1.

Is the intention of the XML schema that users can validate their code lists instances against the schema?

No. It was intended to be informative for consumers of our example codelists. Most real world codelists defined by government agencies or other communities will not follow our choice.

Why a new element  as root element and not the existing GML element gml:Dictionary?

See above for the reason. I am happy to explicitly use the gml:Dictionary structure.

The elements gml:identifier and gml:name for the individual code list entries are currently defined as mandatory in the XML schema. We once discussed that only gml:identifier should be mandatory and gml:name optional. gml:identifier does not necessarily need to contain a code value, but can instead also contain a text value and in that case it is not required to provide the text value in the  element as well. The same for the gml:description element, this should also be optional. See also my comment above from December.

I do not see a difference between a "code" value and a "text" value. Again, I have no problem using the name field and the description field for essentially the same purpose if it aligns better.

Also, we have created an XML schema for the metadata. This schema is not mentioned in the chapter. The metadata elements have now become part of the new XML schema for code lists. And a new  element is introduced that will contain the metadata information. Does that mean that we do not make use of the gml:metaDataProperty element any more in the code list GML instances? The instance provided in the chapter, however, still uses the gml:metaDataProperty element.

Will change.

Regarding the metadata elements:
Should the metadata elements be shortly explained? I think it would make sense..The metadata element  was defined as xs:string in the metadata XML schema, because we said that the value could be a date or version number. Now it's defined as xs:decimal.

Yes.

The metadata element  was defined as xs:anyURI in the metadata XML schema, now it's defined as xs:string.
I noted down several things from the meeting where we discussed code lists. Would it make sense to provide these things as recommencations?

Yes.

The dictionary must always have a gml:id
The gml:identifier element contains the code and is mandatory, the gml:name element contains a human-readable representation of the code. But the gml:name element is only required, when the code is a numeric code.

I think it makes sense to just make the name element optional. An identifier can be opaque even it is not a number.
I think the discussion was that a name is only helpful if the identifier is some opaque value, such as a number. My opinion is that the description is the best place to explain opaque codes. I will agree with having an optional name, since we have legacy codelist entries with both codes and names.

The gml:description element can be used for additional descriptions of the code, but is optional.
Always the same code space should be used for the whole dictionary and the individual entries.
Code lists can be extended by referencing external code lists.
In the GML instance document, the codespace links to a code list file or API.

OK.

Good point. I see that most (all?) of the examples in the repo and in the document do not have a codeSpace attribute. The attribute seems logically necessary in order to interpret or validate the code value. One way to solve the GML issues is to change the mapping of CodeList stereotyped types from GML:CodeType. to the Core type "Code", which is in the CM and seems to be a clone of CodeType but not in the GML namespace. (Maybe I am missing something in the history of Code??)
Optionality would still be still an issue. We add a requirement that restricts the allowed multiplicity to 1 or to 1..* That would support testing whether a codelist value was indeed valid in the specified codelist. It might also give access to other information specific to an external codelist that might enhance the user experience, e.g. plaintext alias or description for the code values- all outside the scope of our standard.
The downside of removing optionality would be breaking of backwards compatibility.

The downside of making the XML attribute codeSpace mandatory is that you always have to have a codelist. Remember that the CM does not define codelists. And then please check how many thematic attributes in the CM are of type gml:CodeType. You will not be able to use one of those attributes without defining a codelist beforehand.
A (possibly undocumented?) idea of CityGML 2.0 is that you can simply store a clear-text string as value of a gml:CodeType attribute without the need for referencing a codelist via codeSpace. For example, you could simply store the value "hospital" as bldg:function of a bldg:Building element. I think this should still be possible in CityGML 3.0.

I agree with Claus' comment.

That is two votes for leaving the codeSpace attribute optional. If we do that, then we should give some more definition to the use of the attribute when it is present. Here's my suggestion:
A gml:CodeValue datatype may have an optional codeSpace attribute. The purpose of the codeSpace attribute is to identify the codelist from which the value is taken. An authority sponsoring the identified codelist may have rules governing the use and meaning of the codelist's values and metadata. The authority may also have rules defining such things as the use and interpretation of values that do not appear in the codelist, the duplication of values, or any other characteristics of a codelist. All such properties and uses of a codelist or codelist value are outside the scope of this CityGML 3.0 Encoding Specification. This does not in any way restrict the ability of an authority sponsoring a codelist, as denoted by the use of a codeSpace attribute, to have application-specific codelist values, rules, interpretations, and uses specified in an independent specification.

This suggestion looks good to me!

I think it would be helpful to include something in the note about the benefit to users of having the codeSpace attribute populated, such as:
"Providing the codeSpace, especially when you use a dereferenceable identifier, should allows the user easy access to further information about the value such as more detail about what it means."

Incorporating that suggestion and tidying up the language a bit:
A gml:CodeValue datatype may have an optional codeSpace attribute. The purpose of the codeSpace attribute is to identify the codelist from which the value has been taken. Providing the codeSpace, especially with a dereferenceable identifier,  allows easy access to further information detailing rules governing the use and meaning of the codelist's values and metadata. There may also be rules defining such things as the use and interpretation of values that do not appear in the codelist, the duplication of values, or any other characteristics of a codelist. All such properties and uses of a codelist or codelist value are outside the scope of this CityGML 3.0 Encoding Specification. This does not in any way restrict the ability of an authority sponsoring a codelist, as denoted by the use of a codeSpace attribute, to have application-specific codelist values, rules, interpretations, and uses in an independent specification.

The language of my previous text, that is!

I like the text.

Also looks good to me. Thanks, @3DXScape and @PeterParslow

A question about Claus' comment April 9: since the gml:CodeType codeSpace attribute is optional can we have the requirements:

if the codeSpace attribute is present and resolves to a valid remote resource, then the content of the gml:CodeType element shall match the gml:identifier property of some entry in a codelist encoded as a gml:Dictionary or it SHALL match some codelist value in a codelist if the encoding is not gml:Dictionary, and
if the codeSpace attribute is absent or does not resolve to a valid remote resource, then the gmlcCodeType element SHALL be a non-empty string.

This seems necessary to me since an gml:CodeType value that does not occur in a codelist referenced via a codeSpace attribute seems pointless.


ADS

Hey, I have a question.
Can the bot see the ads when they pop on the stream?
If not, would it be possible to make that? Thanks.

Hello, maybe yes, maybe not because it's just a request sent on the streams. If they show the ads, they only show them for 1 second. I'm not going to implement this feature because it's illegal. Sorry.


The password is not displayed the first time a deployed virtual machine is started

Steps to reproduce

Create VM (with a password but do not start it)
Start created VM

Actual result

Create VM with a password which not started during deployment. Deployment window will show that there is no information about the password but Save password button work. When you start this VM for the first time there is no information about password provided, but this data exists in response from a server.
Expected result

If there is no information about a password in deployment window when deployed VM does not start, Password information not shown. After the first start of the deployed VM modal window with password appears, for example as when resetting the password.
Environment

Browser:
- [ ] Chrome version XX
- [ ] Firefox version XX
- [ ] Safari version XX
- [ ] Opera version XX
- [ ] IE version XX
- [ ] Edge version XX

Others:

Connected feature ID

vm_deploy
vm_start
Screenshots

New dialog view added see PR #1199
Regression:
vm_deploy
vm_start
vm_password_reset

Tested on 1199


TypeError: Cannot use 'in' operator to search for 'moduleId' in 100-continue

I'm submitting a bug report

Library Version:
1.7.1

Please tell us about your environment:

Operating System:
Affects Linux and Windows (probably all environments)

Node Version:
v16.16.0, also affects v14.x

NPM Version:
8.11.0

JSPM OR Webpack AND Version
Webpack 5.46.0

Browser:
Chrome, Chrome headless, Aurelia SSR

Language:
All

Current behavior:
When navigating to the following route:
/?__proto__.expect=100-continue&constructor.prototype.expect=100-continue&id.__proto__.expect=100-continue&id.constructor.prototype.expect=100-continue&id%5B__proto__%5D%5Bexpect%5D=100-continue
The application crashes with the following error:
INFO [aurelia] Aurelia Started
ERROR [app-router] TypeError: Cannot use 'in' operator to search for 'moduleId' in 100-continue
ERROR [app-router] TypeError: Cannot use 'in' operator to search for 'moduleId' in 100-continue
ERROR [app-router] TypeError: Cannot use 'in' operator to search for 'moduleId' in 100-continue
ERROR [app-router] TypeError: Cannot use 'in' operator to search for 'moduleId' in 100-continue
ERROR [app-router] TypeError: Cannot use 'in' operator to search for 'moduleId' in 100-continue
ERROR [app-router] TypeError: Cannot use 'in' operator to search for 'moduleId' in 100-continue
ERROR [app-router] TypeError: Cannot use 'in' operator to search for 'moduleId' in 100-continue
ERROR [app-router] TypeError: Cannot use 'in' operator to search for 'moduleId' in 100-continue
ERROR [app-router] TypeError: Cannot use 'in' operator to search for 'moduleId' in 100-continue
ERROR [app-router] 10 navigation instructions have been attempted without success. Restoring last known good location.
ERROR [app-router] TypeError: Cannot use 'in' operator to search for 'moduleId' in 100-continue
ERROR [undefined] Router Error TypeError: Cannot use 'in' operator to search for 'moduleId' in 100-continue
    at eval (webpack://frontend/./node_modules/aurelia-templating-router/dist/native-modules/aurelia-templating-router.js?:302:28)
    at new Promise (<anonymous>)
    at TemplatingRouteLoader.resolveViewModel (webpack://frontend/./node_modules/aurelia-templating-router/dist/native-modules/aurelia-templating-router.js?:300:16)
    at TemplatingRouteLoader.loadRoute (webpack://frontend/./node_modules/aurelia-templating-router/dist/native-modules/aurelia-templating-router.js?:346:14)
    at eval (webpack://frontend/./node_modules/aurelia-router/dist/native-modules/aurelia-router.js?:1534:48)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async Promise.all (index 1)
ERROR [event-aggregator] TypeError: Cannot destructure property 'config' of 'router.currentInstruction' as it is null.
    at eval (webpack://frontend/./src/providers/server-platform-provider.ts?:36:21)
    at invokeCallback (webpack://frontend/./node_modules/aurelia-event-aggregator/dist/native-modules/aurelia-event-aggregator.js?:33:5)
    at EventAggregator.publish (webpack://frontend/./node_modules/aurelia-event-aggregator/dist/native-modules/aurelia-event-aggregator.js?:70:11)
    at resolveInstruction (webpack://frontend/./node_modules/aurelia-router/dist/native-modules/aurelia-router.js?:2271:25)
    at eval (webpack://frontend/./node_modules/aurelia-router/dist/native-modules/aurelia-router.js?:2199:50)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
Error in Koa Error: read ECONNRESET
    at TCP.onStreamRead (node:internal/stream_base_commons:217:20) {
  errno: -4077,
  code: 'ECONNRESET',
  syscall: 'read',
  headerSent: true
}

Expected/desired behavior:
It should not crash. It should parse properly and take you to the page that is set to handle "/".

It seems the issue is reproducible with navigating to the following URL as well:
/?something[__proto__][else]=oops
I believe there's some magic going on with trying to set nested properties on proto, then trying to look for that property on something using the in keyword, which won't exist as it was set on the proto. I have a strong feeling that it's an issue with the aurelia-route-recognizer, but we have a suitable workaround for now.


Autorest Regen Preview to 3.0.0-alpha.20240222.1 by Michael Nash from refs/pull/4259/head

Triggered from https://github.com/Azure/autorest.csharp/pull/4259

API change check
API changes are not detected in this pull request.


configure R to use with IntelliJ

Team,
I cannot get R to compile in IntelliJ on MacOS.   The following screenshots show what my settings are:

my code will compile if I use the R console on the right, but will not function if I code in IntelliJ

R is a scripting language, there is no compilation (unless your doing package development).
All the plugin is doing is to build an index from your installed packages and to provide an embedded terminal to run code selections.

Thanks for the reply.    I am preparing for my upcoming class that uses R.  How do I see the output from my script in IntelliJ?  Or do I need to just use R studio for that?

Yes, you could use the integrated console, which will show your results.


Transfer google drive document file ownership for newly created file

I successfully create file.
 string[] scopes = new string[] { DriveService.Scope.Drive };
    GoogleCredential credential;
    using (var stream = new FileStream(Directory.GetCurrentDirectory() + "/Resources/GoogleCredentials.json", FileMode.Open, FileAccess.Read))
    {
        credential = GoogleCredential.FromStream(stream).CreateScoped(scopes);
    }
    DriveService drive = new DriveService(new BaseClientService.Initializer()
    {
        HttpClientInitializer = credential,
    });
    var f = drive.Files;
    var request = f.Create(new Google.Apis.Drive.v3.Data.File()
    {
        Name = "Test from ASP.NET Core",
        AppProperties = prop,
        MimeType = "application/vnd.google-apps.document"
    });
    var file = await request.ExecuteAsync();

but I can not transfer ownership:
Permission permission = new Permission()
 {
     EmailAddress =<EMAIL_ADDRESS>     Type = "user",
     Domain = "example.com",
     Role = "owner"
 };
 var requestpermission = drive.Permissions.Create(permission, file.Id);
 requestpermission.TransferOwnership = true;
 var perm = await requestpermission.ExecuteAsync();

I get error:

The specified domain is invalid or not applicable for the given permission type.

Can someone explain to me, what am I doing wrong?

I suggest you post this question on StackOverflow.Com tag it Google-api-dotnet-client and Google-drive-sdk
I will have a look in the morning.
This is an issue with the Google Drive api and not the client library itself so stackoverflow.com is the best place to get help.

Think this is their question:
Google Drive API (.NET) - Transfer ownership from Service Account to Domain user

This has been answer on stackoverflow


the mismatch between result_.sentence and result_.word_pieces when using TLG decoding？

Hello,
when I use TLG decode ,I find the result_[0].sentence and result_[0].word_pieces are difference, the result_[0].sentence is generated by searcher_->Outputs()（the TLG outputs_[0]）,and  the result_[0].word_pieces are based on searcher_->Inputs()（the  TLG  alignment）. There is a difference between the two results especially when the recognition result contains repeated words.This also causes the results of the timestamp to be inconsistent with the final recognition result.
Is there any way to keep them consistent?
Thank you very much.

Yes, for TLG(with LM) decoding, result[0].sentence is gererated by searcher->Outputs() since it is the output unit of TLG. However, timestamp is generated by our modeling units(searcher->Inputs()), which is designed in the way on purpose since we can get more accurate timestamp with smaller units.

Thanks for pointing it out, this is a normal behaviour as explaned by robin1001.
I will hold this PR for anyone else who has encountered and interested in the same question.


Support fro vertical blinds

Would it be possible to support vertical blinds like the one below,  it is possible to control it but the graphic is  up to down and not left to right
https://www.home-assistant.io/integrations/hunterdouglas_powerview/

I'm looking for that as well, any updates ?


Internationalization of mCalendarView

Two main adjustments :

Auto Translation of the day (mon, tue, etc ...)
Handling of the first day of the week
And a quick fix for a crash that happen very rarely

(third time i try to push that one and each time i was finding another bug, this time every case is tested, sorry for the inconveniance)

Thanks for your contribution!
Sorry for the late reply. Currently I'm busy with company projects so don't have much time for GitHub Projects.
Thanks again!

Hi,
No problem ! It's my pleasure :)
Have a nice day !


Update RxJS dependency to 5.0.x

The new angular-cli and angular 2.3.x requires rxjs 5.0.1
angular-jwt still requires rxjs beta-12

Sounds like this is for angular2-jwt :)
There's actually a PR in flight there right now: https://github.com/auth0/angular2-jwt/pull/253

Sorry.. you're right.. forgot the 2 in the url.. :-S


style: fix typos

Found via codespell -S ./langcodes/data,./langcodes/data_dicts.py -L statics,vai and typos --hidden --format brief

@kianmeng Thank you for the contribution! :rocket: This looks good to me. I am going to merge it and it will be part of the next release
A possible next step might be to enforce this using Github Actions. But this can be done in a later step.

:partying_face: :partying_face: :partying_face: :partying_face: :partying_face:


The Birt reports do not work with https access

[Version] OSCM 17.5.0 2017/10/30
Docker image with TomEE
[How to reproduce]

Login to administration portal and to the marketplace
Go to Account -> Create report (portal) and to Account -> Reports (marketplace)
Click on any report (portal); choose any report from the list (mktpl)

[Expected result]
The report is shown
[Observed result]
Nothing happens, the report is not shown

Do you mean HTTPS not HTTP? Not that only HTTPS is going to be supported for any kind of OSCM access from external host. We have successfully tested the reports recently. If reports are not executable for your tests please check following.
Questions

Can you create BIRT sample reports from the browser?
Are report configuration settings correct
In BIRT application within the container, locate the file viewer.properties and check the value Base URL. This has to match with the HTTPS Base URL in the OSCM portal.

Hi @GoebelL

I can create report from the browser with http and https

I think my configuration is correct:
1.REPORT_ENGINEURL: http://<IP_ADDRESS>:8680/birt/frameset?__report=${reportname}.rptdesign&SessionId=${sessionid}&__locale=${locale}&WSDLURL=${wsdlurl}&SOAPEndPoint=${soapendpoint}&wsname=Report&wsport=ReportPort
2.REPORT_SOAP_ENDPOINT: http://oscm-core:8080/oscm-reporting/ReportingServiceBean
3.REPORT_WSDLURL: http://oscm-core:8080/oscm-reporting/ReportingServiceBean?wsdl

In fact, I have different values in those two places.
1.configsetting BASE_URL_HTTPS: https://<IP_ADDRESS>:8081/oscm-portal/
2.viewer.properties base_url=https://estessbesci8.intern.est.fujitsu.com:8681

So my question is:
Adress for which container should be in the file viewer.properties, for oscm-core or for oscm-birt?

@kwodzynski Are you actually accessing the portal and report engine with the host name or with the IP address? I see that in viewer.properties the host name is set. If you access the reporting engine with the IP address this may cause issues.
Can you please try the following:

If you do not have DNS, please try to create an entry in your system's hosts file so you can use the host name to access portal and report engine.
Change the BASE_URL_HTTPS and REPORT_ENGINEURL config settings to also use the host name
Does it work then?

Hi @shimizuf
I added dns to my host file, but our polish proxy cannot resolve that.
Should I change base_url in viewer.properties to IP ?

It's worth trying, yes. But it's possible that the configuration change requires a restart of Tomcat which will end your running container.
I think this might be easier:
Stop the running containers manually on the Docker system. Then edit the var.env file to have the HOST_FQDN variable contain the IP address instead of the host name. Then use Docker Compose to start the containers again. The viewer.properties should then contain the IP address in the base_url.

@shimizuf I followed your instruction and now I have base_url set to IP address. But I still can't generate the Birt reports in https. I think I may be caused by number of port (base_url=https://<IP_ADDRESS>:8681)
Shouldn't be there port to oscm-core container?

In the case of the reporting engine the port is correct. Here, base_url must be set to the base URL of the reporting engine.
Now that you have set the base_url to the IP address, can you please try to access the report engine's example report?
https://<IP_ADDRESS>:8681/birt/frameset?__report=test.rptdesign&sample=my+parameter

Ok, since I have changed REPORT_ENGINEURL to https, I can generate reports. Thanks for your help. Closing

Tested on 17.5 2017/12/06. The Birt reports work good.


[Core] Docs Changes Needed from dbt-core Issue #9907

At a minimum, update body to include a link to the page on docs.getdbt.com requiring updates and what part(s) of the page you would like to see updated.

PR #9907

PR: #10137

@nataliefiann : this may not need a docs update. please double-check with emmyoop before closing. tysm!

Hiya @emmyoop
Happy Monday - I hope you're well.
I just wanted to ask if this still needs a docs update?
Kind Regards
Natalie

@mirnawong1 was correct.  This does not need a docs update.  It only affected our internal testing.  I'll close it.


Debugger: Failed to attach to proccess:Unknown Error:0x80131c08

Environment data
dotnet --info output:
OS: ubuntu14.04
VS Code version: 1.9.1
C# Extension version: 1.8.0-beta1
dotnet cli: 1.0.0-preview2-1-003177
Steps to reproduce

Open attached folder with VSCode.
hwapp.zip

Select '.NET Core Attach'.

Open one terminal, and 'dotnet run' the project.

F5 to start debugging and select the running process to attach to.

Stop debugging after the process run correctly.

Continue to do the step #4 above.

Expected  behavior
The process can work correctly.
Actual behavior
Pop up a following error message:

Investigation

After the #6, maybe need to wait about 15 seconds or more.
This issue often occur second 'Attach' operation.

I'm unable to reproduce.. lets keep the issue open for now.

cc @gregg-miskelly
This appears to be yet another issue with testing with tight loops. After attaching to this process that is running a tight, infinite loop, we are unable to disconnect cleanly from the debuggee. This leaves us in a state where vsdbg-ui is just killed out from underneath us and the debuggee process is left in a bad state. Attaching to it again is then completely broken. Adding a Thread.Sleep(100); to the loop appears to fix all issues.
@ClaireKang Can you please try this tests again after adding Thread.Sleep(100); to your loop?

This issue didn't reproduce after adding Thread.Sleep(100).

Thanks! In that case this is more or less the same issue as dotnet/coreclr#4623. Please avoid super tight loop in test debuggees until that is resolved (which is likely to be a long time).


Python bindings reference count fixes

This merge request fixes several reference count issues in the python bindings.

Hi, thank you, but old libkeybinder (not 3) is effectively discontinued, unless someone wants to maintain it.


Poc settings menu

POC for navbar popout settings menu:

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


Rename nrf52-hal to nrf52832-hal

nrf52-hal is actually specific to nRF52832, so the current name is highly misleading in this context.

Yeah, I'd like to see this happen.  Probably easiest to get this done once both of the outstanding pull requests are merged

Still to do: review crates.io and rename/archive/publish as appropriate

Renamed by #32


change default signature algorithm to "default_md = md5"

Hi,
i must change the default signature algorithm from sha256 to md5. my client yealink phone only sipports this signature algorithm. what is the best way to make this setting?
best regards
Thomas

It's kind of painful and not recommended.  I'd try to fix your client.  Using md5 is strongly frowned upon.