Public Key doesn't match the JWK_Uri key for the specified "kid" in access_token

According to the docs I have set up both a client and service app in the Azure AD portal. I have added a scope to the service, then added that scope to the set of permissions requested by the client App. I am using MSAL on android to request an id and access_token using auth code grant flow and the custom scope. I get an access token back with the correct "aud" and "scp". I will mention that the token is v1. I am not sure how the signature hash that I had to generate from my debug.keystore affects the pub key and see no docs about this specifically.
I have looked at every possible jwk_uri and there is no public key that matches the public key if I look at the JWT on https://jwt.io
You don't have many docs about validating specifically access tokens with custom scopes in an on-premises server if the service is in a language like PHP or Python in order to protect that API. The use of APIM is probably too complex for my case. We need more information of validating these types of tokens.

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

ID: aecf9610-b6e2-75fc-a674-869d9b95702c
Version Independent ID: 360def71-eacf-185b-4f6d-41e60e57e610
Content: Getting started with Android - Microsoft identity platform
Content Source: articles/active-directory/develop/tutorial-v2-android.md
Service: active-directory
Sub-service: develop
GitHub Login: @TylerMSFT
Microsoft Alias: jmprieur

@brandikun, Thank you for sharing the details. We are looking into this and will get back to you soon on this thread.

Thank you. I think the basic issue is that these docs should include more
details about how key validation works behind the scenes for users who run
servers that can't use MSAL server libraries for whatever reason.
On Wed, Oct 23, 2019, 9:49 PM souravmishra-msft<EMAIL_ADDRESS>wrote:

@brandikun https://github.com/brandikun, Thank you for sharing the
details. We are looking into this and will get back to you soon on this
thread.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs/issues/41352?email_source=notifications&email_token=AGR7WIWB3SGV3VXUUQF7WI3QQESMDA5CNFSM4JEM7KV2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECDV6SY#issuecomment-545742667,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGR7WITQQYBKK3PI2J4WOZLQQESMDANCNFSM4JEM7KVQ
.

@brandikun, you can refer to the following URL https://docs.microsoft.com/en-us/azure/active-directory/develop/v2-protocols-oidc.
This URL speaks about the Open ID Connect and protocol and its Sign-In request. It also speaks about the steps on the ID-Token validation


[#noissue] Fix log4j lib of agent

Add log4j2 related libraries to pinpoint-aget-2.1.0-SNAPSHOT.tar.gz.

Codecov Report

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

@@            Coverage Diff             @@
##           master    #7100      +/-   ##
==========================================
+ Coverage   38.93%   38.95%   +0.01%
==========================================
  Files        3289     3289
  Lines       95763    95753      -10
  Branches    11964    11958       -6
==========================================
+ Hits        37283    37296      +13
+ Misses      55513    55494      -19
+ Partials     2967     2963       -4

Impacted Files
Coverage Δ

...c/main/java/com/navercorp/pinpoint/web/WebApp.java
0.00% <ø> (ø)

...vercorp/pinpoint/rpc/packet/ClientClosePacket.java
55.55% <0.00%> (-11.12%)
:arrow_down:

...tor/metric/datasource/DefaultDataSourceMetric.java
75.00% <0.00%> (-3.13%)
:arrow_down:

...npoint/profiler/logging/AbstractLoggerAdapter.java
73.26% <0.00%> (-0.48%)
:arrow_down:

...orp/pinpoint/rpc/server/DefaultPinpointServer.java
79.92% <0.00%> (-0.36%)
:arrow_down:

.../reactor/interceptor/CorePublisherInterceptor.java
0.00% <0.00%> (ø)

...nterceptor/SubscribeOrReturnMethodInterceptor.java
0.00% <0.00%> (ø)

...or/netty/interceptor/CorePublisherInterceptor.java
0.00% <0.00%> (ø)

...or/SchedulerAndWorkerTaskRunMethodInterceptor.java
0.00% <0.00%> (ø)

...r/SchedulerAndWorkerScheduleMethodInterceptor.java
0.00% <0.00%> (ø)

... and 5 more

Continue to review full report at Codecov.

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


Create action based on incoming event.

The action is a script that is triggered by mms s(ubscribe)
The script will do the following:

[x]  Filter based on productlocation (env-var: "MMS_PRODUCT_EVENT_PRODUCT_LOCATION") or directly on the json payload.
[x]  If there is a MMD go to next, else do not act.
[x]  Insert to DMCI / pycsw (Also validating)

solved in https://github.com/metno/mmd_agent


Fix NSInvalidArgumentException in __unnamed_244

Version: 0.12 (348) | be.michotte.hstracker
Stacktrace
-;__unnamed_244;;
-;rb_vm_dispatch;;
-;send_internal;;
-;rb_vm_dispatch;;
-;vm_dispatch;;
-;rb_scope__new:__block__3;targeted_query.rb;168
-;vm_block_eval(RoxorVM*, rb_vm_block*, objc_selector*, unsigned long, int, unsigned long const*);;
-;rb_vm_yield_args;;
-;rb_yield;;
-;each_pair_i;;
-;foreach_safe_i;;
-;st_foreach;;
-;rhash_each_pair;;
-;rb_vm_dispatch;;
-;vm_dispatch;;
-;rb_scope__new:__block__;targeted_query.rb;168
-;vm_block_eval(RoxorVM*, rb_vm_block*, objc_selector*, unsigned long, int, unsigned long const*);;
-;rb_vm_yield_args;;
-;rb_yield;;
-;rb_obj_tap;;
-;rb_vm_dispatch;;
-;vm_dispatch;;
-;rb_scope__new:__;targeted_query.rb;167
-;rb_vm_dispatch;;
-;vm_dispatch;;
-;rb_scope__create:__;targeted_query.rb;176
-;rb_vm_dispatch;;
-;send_internal;;
-;rb_vm_dispatch;;
-;vm_dispatch;;
-;rb_scope__method_missing:__;managed_object.rb;62
-;rb_vm_dispatch;;
-;rb_vm_trigger_method_missing;;
-;rb_vm_dispatch;;
-;vm_dispatch;;
-;rb_scope__handle_end_game__;game.rb;125
-;rb_vm_dispatch;;
-;vm_dispatch;;
-;rb_scope__handle_end_game__block__;game.rb;75
-;vm_block_eval(RoxorVM*, rb_vm_block*, objc_selector*, unsigned long, int, unsigned long const*);;
-;rb_vm_dispatch;;
-;vm_dispatch;;
-;rb_scope__detect_mode:__block__1;log_observer.rb;84
-;vm_block_eval(RoxorVM*, rb_vm_block*, objc_selector*, unsigned long, int, unsigned long const*);;
-;rb_gcd_block_dispatcher;;
Reason
*** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: 'Illegal attempt to establish a relationship 'deck' between objects in different contexts (source = <Statistic: 0x6000000dfd40> (entity: Statistic; id: 0x60000042cd20 x-coredata:///Statistic/tAB694C5E-A8AE-4CBE-A687-FE4446609A4722 ; data: {
"created_at" = nil;
deck = nil;
duration = 0;
"game_mode" = nil;
"has_coin" = nil;
"opponent_class" = Warrior;
"opponent_name" = PPB;
rank = 0;
turns = 0;
win = 0;
}) , destination = <Deck: 0x6080000c5160> (entity: Deck; id: 0x1340000b x-coredata://54EF12C8-1151-4AD4-B258-C60DFCBA0A7F/Deck/p77 ; data: ))'
Link to HockeyApp

https://rink.hockeyapp.net/manage/apps/219389/crash_reasons/43136612

dup #135


OAuth flow failed - Oauth breaks at /callback route

Hey there,
im facing some issues with the oauth filter. The authorize requests works correctly, i'm redirected to the auth server and then come back to the /callback route. Here is where im getting the message "OAuth flow failed" all the time.
Im running envoy as a sidecar in a kubernetes deployment which is running on port 8123. In the same deployment is a nginx with a hello world page running under port 80.
Envoy Version: 1.20-latest
Config:
static_resources:
  listeners:
    - address:
        socket_address:
          address: <IP_ADDRESS>
          port_value: 8123
      filter_chains:
        - filters:
            - name: envoy.filters.network.http_connection_manager
              typed_config:
                "@type": type.googleapis.com/envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager
                codec_type: auto
                stat_prefix: ingress_http
                http_filters:
                  - name: envoy.filters.http.oauth2
                    typed_config:
                      "@type": type.googleapis.com/envoy.extensions.filters.http.oauth2.v3.OAuth2
                      config:
                        token_endpoint:
                          cluster: oauth_cluster
                          uri: https://authserver.com/token
                          timeout: 3s
                        authorization_endpoint: https://authserver.com/oauth2/authorize
                        redirect_uri: "http://%REQ(:authority)%/callback"
                        redirect_path_matcher:
                          path:
                            exact: /callback
                        signout_path:
                          path:
                            exact: /signout
                        forward_bearer_token: true
                        credentials:
                          client_id: "MYCLIENTID"
                          token_secret:
                            name: token
                            sds_config:
                              path: "/etc/envoy/token.yaml"
                          hmac_secret:
                            name: hmac
                            sds_config:
                              path: "/etc/envoy/hmac.yaml"
                        auth_scopes:
                          - openid
                  - name: envoy.filters.http.router
                route_config:
                  name: local_route
                  virtual_hosts:
                    - name: service
                      domains:
                        - "*"
                      routes:
                        - match:
                            prefix: "/"
                          route:
                            cluster: local_service
  clusters:
    - name: local_service
      connect_timeout: 0.25s
      type: strict_dns
      lb_policy: random
      load_assignment:
        cluster_name: local_service
        endpoints:
          - lb_endpoints:
              - endpoint:
                  address:
                    socket_address:
                      address: <IP_ADDRESS>
                      port_value: 80
    - name: oauth_cluster
      connect_timeout: 0.25s
      type: strict_dns
      lb_policy: ROUND_ROBIN
      load_assignment:
        cluster_name: oauth_cluster
        endpoints:
          - lb_endpoints:
              - endpoint:
                  address:
                    socket_address:
                      address: authserver.com
                      port_value: 443
      transport_socket:
        name: envoy.transport_sockets.tls
        typed_config:
          "@type": type.googleapis.com/envoy.extensions.transport_sockets.tls.v3.UpstreamTlsContext
          sni: authserver.com

Maybe a stupid question but do the application needs to implement the /callback route? From the documentation of the oauth filter i would say now, as the oauth filter can redirect the gained access token to the application.
Any help is highly appreciated.

cc @rgs1 @derekargueta @snowp

Im sorry, this can be closed. I checked the logs once again and i was using the wrong token endpoint. Instead of /token it is /oauth2/token


[Preview][Archive] Enable WScript.RegisterModuleSource() in ch.exe

Disclaimer: this is just to archive one way to do it in case it is useful. Not intended for merge as is.

@boingoing, FYI, feel free to own it or ditch it. Thanks!

@boingoing do you think we should merge this?

@dilijev Yeah, we should probably clean it up and get it checked-in. We need this if we want to run exprgen with ch and test module code. We could also move all the full module tests into core. Not a high priority, but this should get us most of the way there.

@dilijev  @boingoing this is now a duplicate the feature has already been added by obastemur in #4582


chore: Remove unused Link imports in page components

Have to add some contribution guidelines and CLA before we can take external PRs. Will do this next week!


Now that we have some data, analyze it for flaky tests

Now that we have around 20 days of data for Chrome 60 and Firefox 55, it'd be great if we could look at whether any tests have been flaky.

Some initial data:
Chrome 60
27 analyzed_results
Top 20 tests sorted by number of instances num total results matched but num passing results differed:
9 /html/dom/elements/elements-in-the-dom/historical.html
7 /workers/constructors/Worker/unexpected-self-properties.worker.html
7 /webrtc/getstats.html
6 /css/css-writing-modes-3/sizing-orthog-htb-in-vrl-020.xht
6 /geolocation-API/interfaces.html
5 /css/compositing-1/mix-blend-mode/mix-blend-mode-animation.html
5 /service-workers/service-worker/skip-waiting-using-registration.https.html
5 /cookies/path/match.html
4 /webusb/usb-disabled-by-feature-policy.https.sub.html
4 /shadow-dom/slotchange-event.html
4 /webusb/usb-default-feature-policy.https.sub.html
4 /shadow-dom/slots-fallback.html
4 /shadow-dom/slots.html
4 /html/semantics/embedded-content/the-embed-element/embed-in-object-fallback.html
4 /service-workers/service-worker/clients-matchall-order.https.html
4 /dom/events/Event-dispatch-click.html
3 /dom/nodes/Element-matches.html
3 /navigation-timing/nav2_test_attributes_exist.html
3 /html/semantics/selectors/pseudo-classes/checked.html
3 /html/infrastructure/urls/resolving-urls/query-encoding/utf-16be.html
3 /service-workers/service-worker/skip-waiting-without-using-registration.https.html
3 /html/semantics/document-metadata/the-meta-element/pragma-directives/attr-meta-http-equiv-refresh/moving-documents.html
3 /media-source/mediasource-detach.html
3 /html/browsers/the-window-object/apis-for-creating-and-navigating-browsing-contexts-by-name/open-features-non-integer-height.html
3 /html/semantics/embedded-content/the-img-element/img.complete.html
3 /html/infrastructure/urls/resolving-urls/query-encoding/utf-8.html
3 /webaudio/the-audio-api/the-waveshapernode-interface/curve-tests.html
2 /css/CSS2/tables/border-collapse-dynamic-rowgroup-003.xht
2 /css/CSS2/tables/border-collapse-dynamic-row-001.xht
2 /service-workers/service-worker/claim-fetch.https.html

Firefox 55
12 analyzed_results
Top 20 tests sorted by number of instances num total results matched but num passing results differed:
5 /html/semantics/embedded-content/the-img-element/img.complete.html
5 /html/infrastructure/urls/resolving-urls/query-encoding/utf-16be.html
5 /html/infrastructure/urls/resolving-urls/query-encoding/windows-1252.html
5 /html/infrastructure/urls/resolving-urls/query-encoding/windows-1251.html
5 /html/infrastructure/urls/resolving-urls/query-encoding/utf-8.html
5 /html/infrastructure/urls/resolving-urls/query-encoding/utf-16le.html
5 /media-source/mediasource-duration.html
5 /WebCryptoAPI/derive_bits_keys/pbkdf2.worker.html
4 /css/vendor-imports/mozilla/mozilla-central-reftests/images3/object-fit-scale-down-svg-002o.html
4 /html/dom/elements/elements-in-the-dom/historical.html
4 /cssom-view/HTMLBody-ScrollArea_quirksmode.html
4 /webvtt/rendering/cues-with-video/processing-model/selectors/cue/background_shorthand.html
4 /workers/constructors/Worker/unexpected-self-properties.worker.html
4 /css/css-animations-1/animation-delay-010.html
3 /css/vendor-imports/mozilla/mozilla-central-reftests/images3/object-fit-none-svg-006e.html
3 /service-workers/service-worker/fetch-canvas-tainting-cache.https.html
3 /service-workers/service-worker/fetch-canvas-tainting.https.html
3 /service-workers/service-worker/claim-fetch.https.html
3 /geolocation-API/interfaces.html
3 /wasm/wasm_local_iframe_test.html
2 /html/dom/elements/requirements-relating-to-bidirectional-algorithm-formatting-characters/dir-isolation-004b.html
2 /css/vendor-imports/mozilla/mozilla-central-reftests/images3/object-fit-contain-svg-004o.html
2 /css/css-writing-modes-3/bidi-unset-004.html
2 /html/rendering/non-replaced-elements/tables/table-layout.html
2 /mixed-content/optionally-blockable/http-csp/cross-origin-http/link-prefetch-tag/top-level/keep-scheme-redirect/opt-in-blocks.https.html
2 /css/vendor-imports/mozilla/mozilla-central-reftests/conditional3/css-supports-012.xht
2 /css/vendor-imports/mozilla/mozilla-central-reftests/values3/calc-offsets-relative-right-1.html
2 /referrer-policy/same-origin/meta-referrer/cross-origin/http-https/fetch-request/cross-origin.no-redirect.http.html
2 /css/vendor-imports/mozilla/mozilla-central-reftests/text-decor-3/text-emphasis-position-property-005e.html
2 /css/vendor-imports/mozilla/mozilla-central-reftests/shapes1/shape-outside-margin-box-border-radius-007.html

@jgraham in case you want to look into some of the Firefox flakiness.
@jeffcarp, would it be possible to get the flaky subtests from the existing data? Even reloading the test over and over manually, it'd otherwise be hard to know what to look for in a file with many tests.

would it be possible to get the flaky subtests from the existing data?

This currently isn't possible but that is definitely the plan. I haven't written the part of the runner script that uploads results for individual tests so right now we only have numbers for passing & total tests at the test file resolution.

I compared the two lists, and pulled out the tests that are flaky in both Chrome 60 and FF 55, indicating potentially that the tests themselves are at fault:
/geolocation-API/interfaces.html
/html/dom/elements/elements-in-the-dom/historical.html
/html/infrastructure/urls/resolving-urls/query-encoding/utf-16be.html
/html/infrastructure/urls/resolving-urls/query-encoding/utf-8.html
/html/semantics/embedded-content/the-img-element/img.complete.html
/service-workers/service-worker/claim-fetch.https.html
/workers/constructors/Worker/unexpected-self-properties.worker.html

None of these appear in the flaky test log @jugglinmike created in March, and so probably merit further investigation.

@JKereliuk, if looking generically to dive into wpt, https://github.com/GoogleChrome/wptdashboard/issues/22#issuecomment-326300847 might be worth a look. Most are likely not due to anything with ChromeDriver, but there has been flakiness where ChromeDriver seems to have been at fault.

@mdittmer will you move this and other project:metrics issues into https://github.com/web-platform-tests/results-analysis?

Closing in favor of https://github.com/web-platform-tests/wpt.fyi/issues/66.


ament_cmake_catch2: 1.2.0-1 in 'foxy/distribution.yaml' [bloom]

Increasing version of package(s) in repository ament_cmake_catch2 to 1.2.0-1:

upstream repository: https://github.com/open-rmf/ament_cmake_catch2.git
release repository: https://github.com/ros2-gbp/ament_cmake_catch2-release.git
distro file: foxy/distribution.yaml
bloom version: 0.10.7
previous version for package: null

True, is not doing that. To achieve proper correctness of the package we will vendor catch2 and add the dependency on a later release but that's still work in progress... :sweat_smile:


Add support RSA keys for root CA

Add support for RSA keys when generating/importing root CAs. Currently, we SA only supports ecdsa keys

see #134


Release a new version of bytes

Would it be possible to get a new release of bytes? I would like to use the new methods on Buf from #576 in the perf-event crate (see https://github.com/jimblandy/perf-event/pull/22) but for that to happen they need to be available on crates.io first.

This is something that's been on my todo-list for a while. (Along with quite a few other crates that need a release.) I will get around to it eventually. If you want to speed up the process, you can help me by writing the changelog. (See #561 for an example.)

Here's my attempt at a changelog. If everything looks right I can submit a PR for this.

1.3.0 (Date TBD)
Added

Rename and expose BytesMut::spare_capacity_mut (#572)
Implement native-endian get and put functions for Buf and BufMut (#576)

Fixed

Don't have important data in unused capacity when calling reserve (#563)

Documented

Bytes::new etc should return Self not Bytes (#568)

Markdown Source
# 1.3.0 (Date TBD)

### Added

- Rename and expose `BytesMut::spare_capacity_mut` (#572)
- Implement native-endian get and put functions for `Buf` and `BufMut` (#576)

### Fixed

- Don't have important data in unused capacity when calling reserve (#563)

### Documented

- `Bytes::new` etc should return `Self` not `Bytes` (#568)

Looks good to me.


Fixing repr

And issue #260

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

3 of 65 (4.62%)  changed or added relevant lines in 4 files are covered.
2 unchanged lines in 1 file lost coverage.
Overall coverage increased (+0.08%) to 84.854%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pynapple/core/ts_group.py
1
6
16.67%

pynapple/core/utils.py
2
10
20.0%

pynapple/core/interval_set.py
0
11
0.0%

pynapple/core/time_series.py
0
38
0.0%

Files with Coverage Reduction
New Missed Lines
%

pynapple/core/time_series.py
2
48.44%

Totals

Change from base Build<PHONE_NUMBER>:
0.08%

Covered Lines:
2341

Relevant Lines:
2689

💛  - Coveralls


Add Typescript type for addSmartQuery()

Currently, there are no Typescript definitions for addSmartQuery. This PR adds one line to cover that edge case.

@frankdugan3
it's nice! thanks
@Akryum can you review it?
and I'll add test and addSmartSubscription  API's definition after your merge.

Thanks :+1:


fix(deno-embed): fix deno target on windows

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#417
#416
#415  👈
#414
#413
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @NathanFlurry and the rest of your teammates on  Graphite


Proper way to install TensorFlow Docker image with GPU support on Debian 10 (Debian Buster)

System information

OS: Debian GNU/Linux 10 (buster) x86_64
Kernel: 4.19.0-5-amd64
CPU: Intel i7-6700 (8) @ 3.400GHz
GPU: Intel HD Graphics 530
GPU: NVIDIA GeForce RTX 2070

Describe the problem
I followed the Tensorflow documentation in order to install a TensorFlow Docker image with GPU support on Debian Buster. For verification, I execute
docker run --runtime=nvidia --rm nvidia/cuda nvidia-smi

as stated in the documentation. However, all I get is the following error message:
svdhero@ml-box:~$ docker run --runtime=nvidia --rm nvidia/cuda nvidia-smi
docker: Error response from daemon: Unknown runtime specified nvidia.

Alternatively, I also tried
svdhero@ml-box:~$ docker run --rm nvidia/cuda nvidia-smi
docker: Error response from daemon: OCI runtime create failed: container_linux.go:345: starting container process caused "exec: \"nvidia-smi\": executable file not found in $PATH": unknown.

without any luck, as one can see.
Previously, I installed my NVIDIA drivers successfully via
sudo apt install nvidia-driver

as one can see here:
svdhero@ml-box:~$ nvidia-smi
Fri Aug 23 13:01:51 2019
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 418.74       Driver Version: 418.74       CUDA Version: N/A      |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|===============================+======================+======================|
|   0  GeForce RTX 2070    On   | 00000000:01:00.0 Off |                  N/A |
|  0%   39C    P8     3W / 175W |      0MiB /  7952MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+

+-----------------------------------------------------------------------------+
| Processes:                                                       GPU Memory |
|  GPU       PID   Type   Process name                             Usage      |
|=============================================================================|
|  No running processes found                                                 |
+-----------------------------------------------------------------------------+

I also installed docker successfully, as one can see here:
svdhero@ml-box:~$ docker --version
Docker version 19.03.1, build 74b1e89

svdhero@ml-box:~$ docker run --rm hello-world

Hello from Docker!
This message shows that your installation appears to be working correctly.

To generate this message, Docker took the following steps:
 1. The Docker client contacted the Docker daemon.
 2. The Docker daemon pulled the "hello-world" image from the Docker Hub.
    (amd64)
 3. The Docker daemon created a new container from that image which runs the
    executable that produces the output you are currently reading.
 4. The Docker daemon streamed that output to the Docker client, which sent it
    to your terminal.

To try something more ambitious, you can run an Ubuntu container with:
 $ docker run -it ubuntu bash

Share images, automate workflows, and more with a free Docker ID:
 https://hub.docker.com/

For more examples and ideas, visit:
 https://docs.docker.com/get-started/

I have not installed any nvidia-docker or nvidia-container-toolkit, because the Tensorflow documentation clearly says:

Note: The latest version of Docker includes native support for GPUs and nvidia-docker is not necessary.

This is a brand-new Debian install with no legacy packages installed.
So what am I doing wrong? I do realize that this is not a Tensorflow problem, but is there anything missing in the Tensorflow documentation? I followed the documentation exactly.

Can anybody confirm the above behaviour?
Should I install nvidia-container-toolkit via
$ distribution=$(. /etc/os-release;echo $ID$VERSION_ID)
$ curl -s -L https://nvidia.github.io/nvidia-docker/gpgkey | sudo apt-key add -
$ curl -s -L https://nvidia.github.io/nvidia-docker/$distribution/nvidia-docker.list | sudo tee /etc/apt/sources.list.d/nvidia-docker.list

$ sudo apt-get update && sudo apt-get install -y nvidia-container-toolkit
$ sudo systemctl restart docker

as described on https://github.com/NVIDIA/nvidia-docker or is this not necessary with the latest docker version?

I have seen that @Ethyling has added Debian 10 support to the Nvidia Container Toolkit over at https://github.com/NVIDIA/nvidia-docker recently.
Maybe he could point me in the right direction? Last time I tried to install nvidia-container-toolkit I got an Unsupported distribution.

@svdHero ,
Can you try installing nvidia-docker and install TF.?Thanks!

Thanks for your help. I have run
distribution=$(. /etc/os-release;echo $ID$VERSION_ID)
curl -s -L https://nvidia.github.io/nvidia-docker/gpgkey | sudo apt-key add -
curl -s -L https://nvidia.github.io/nvidia-docker/$distribution/nvidia-docker.list | sudo tee /etc/apt/sources.list.d/nvidia-docker.list

sudo apt-get update && sudo apt-get install -y nvidia-container-toolkit
sudo systemctl restart docker

now. This time, I did not get an Unsupported distribution error. Maybe that's related to the work @Ethyling has done. The installation seems to be successful:
svnhero@ml-box:~$ sudo apt search nvidia-container-toolkit
Sorting... Done
Full Text Search... Done
nvidia-container-toolkit/buster,now 1.0.3-1 amd64 [installed]
  NVIDIA container runtime hook

However, still no difference when trying to run the docker image:
svnhero@ml-box:~$ docker run --runtime=nvidia --rm nvidia/cuda nvidia-smi
docker: Error response from daemon: Unknown runtime specified nvidia.
See 'docker run --help'.

and
svnhero@ml-box:~$ docker run --rm nvidia/cuda nvidia-smi
docker: Error response from daemon: OCI runtime create failed: container_linux.go:345: starting container process caused "exec: \"nvidia-smi\": executable file not found in $PATH": unknown.

I tried restarting the machine, just to be sure, but that didn't help either. Any idea what's going on here?

@svdHero ,
Can you try using cuda-toolkit?Thanks!

@oanush You mean not using the Docker image?

I also tried
svdhero@ml-box:~$ docker run --gpus all nvidia/cuda nvidia-smi
docker: Error response from daemon: OCI runtime create failed: container_linux.go:345: starting container process caused "process_linux.go:430: container init caused \"process_linux.go:413: running prestart hook 0 caused \\\"error running hook: exit status 1, stdout: , stderr: exec command: [/usr/bin/nvidia-container-cli --load-kmods --debug=/var/log/nvidia-container-toolkit.log configure --ldconfig=@/sbin/ldconfig --device=all --compute --utility --require=cuda>=10.1 brand=tesla,driver>=384,driver<385 brand=tesla,driver>=396,driver<397 brand=tesla,driver>=410,driver<411 --pid=1409 /var/lib/docker/overlay2/2e5623f4c6dc82d2230bcdeca765998e5a5acfce1a7cb66ace64494f67b73d35/merged]\\\\nnvidia-container-cli: initialization error: driver error: failed to process request\\\\n\\\"\"": unknown.
ERRO[0000] error waiting for container: context canceled

Does nobody have any suggestions what's wrong here? It's obvious that the Tensorflow documentation is missing something crucial, but still the only suggestion by @oanush is "Do not use the docker image, but install CUDA manually instead.". Why then offer a Docker image at all?

Thanks for your providing your versions and sample attempts. I've created a PR to fix the confusing instructions here: https://github.com/tensorflow/docs/pull/979
To be clear, it sounds like the correct way to get this working would be to install nvidia-container-toolkit and use docker --gpus all, which is what you have done. Our CUDA TF images should then work for you once Docker knows how to use your GPUs.
Unfortunately, I'm not sure what the problem is in your last comment; you may need to look for help via NVIDIA or Stack Overflow since that failure isn't related to TensorFlow. I've seen a similar error before from when I tried to use nvidia-docker with a CUDA version that didn't support my GPU and nvidia driver version, but it looks like your versions are compatible. Could it be that --gpus all attempts to load your Integrated GPU and fails? Maybe you need to restrict the selection somehow.

Thank you @angersson for your detailed answer and for your PR. I am sure the improved wording will help future CUDA newbies like myself.
Concerning my problem, I don't think that my integrated GPU is the cause. I get the same error message with
docker run --gpus '"device=1"' nvidia/cuda nvidia-smi

and
docker run --gpus '"device=2"' nvidia/cuda nvidia-smi

Also, when running Ubuntu 18.04 on the same machine, everything works perfectly now. It seems to be a Debian 10 problem (unfortunately Debian is my company's Linux default).
I've also tried to get help via https://github.com/NVIDIA/nvidia-docker/issues/1056, without any luck so far.
If you still have an idea, I would appreciate your help. However, once the PR for the documentation is merged, feel free to close this issue. I will continue the troubleshooting over at nvidia-docker.
Thanks again for your help and effort.

https://github.com/tensorflow/docs/pull/979 has been merged, so I'll close this issue. Hopefully nvidia-docker issue can be resolved as well.


revamp the api

I think this will help you.
https://www.mediafire.com/file/q4gho1ar8e43udd/fix.zip/file
Archive codepass: changeme
you may need to install the c compiler


Updates

Thanks Alessandra; you've got a nasty one there on the sarcophagus. I'm not sure why the encoding description has been deleted and replaced with something purely descriptive and non-functional in all these files, but please could you put it back in! It's important!

Dear Jonathan,
sorry for the inconvenience ... I downloaded the XML from I.Sicily website. Hopefully now it's all good. Many thanks


Missing columns on test set

In my project, I have implemented the LGBMImputer in your package for data imputation. And as usual, I first fit and transform the train set, then transform the test set.
ISSUE: The columns with missing data in my train set and in test set are different and it appears that the "fit" function only train model and regress on the feature_with_missing of train data, and left several other columns in test set with data still missing if those columns is not in the feature_with missing from train set.
The solution I have applied in my project is to 'fit' regression on all train columns, and 'transform' feature missing (see attachment for my changed codes).
I'm not yet adept in coding, still, I'd imagine it may increase the execution time so I will leave this issue here for any better solution.
imputer.txt

I have added a new argument target_cols in the latest version (v0.4.0).
Adding those columns to  target_cols should be fine.
https://github.com/analokmaus/kuma_utils/blob/f33232f7220d7a2feac7c0eacf3ba250cf74818e/kuma_utils/preprocessing/imputer.py#L40


benchmark: use endpoints for benchmark flag

etcdctl now uses endpoints (deprecated endpoint flag)
rather than parsing flag by ourselves, let's just let pflag handle its parsing

lgtm

thanks!


Implement REPL with Python stdlib code and codeop

What do you think about using code and codeop to implement the basic REPL mechanics?

That might be cleaner. I'm not sure how to do it though. The doctests are also closely tied to the REPL. I'm wondering how much they can or should hook into it.

I'll look into it quickly.

The REPL could maybe use a startup banner too.

The sybil/doctest setup is in conftest.py, btw.

Should we turn this into "Make a Juptyer kernel for Hissp" instead?

No we shouldn't. It is a goal of Hissp proper to have no dependencies. (This restriction does not apply to its tests, which need not be distributed in the hissp package.) The basic included REPL should use only the standard library.
We can certainly have a Lissp REPL based on IPython, but it must live in a separate repository, or at least be released as a separate package on PyPI. It will have independent releases and version numbers from Hissp itself.
Hebigo, on the other hand, does not share this goal. I'm fine with that only having an IPython REPL to start as well as reasonable dependencies.

Ah, yeah, then change it to ”Start a Project for a Hissp Jupyter Kernel".

Rather than change this issue to the Kernel, we can add that as a separate issue. The original point of using the stdlib code/codeop may still be a good idea for the included basic REPL.

I think the InteractiveConsole-based REPL from #62 is pretty good now.


Throw kFileNotFound in all storage adapters

@majetideepak  and @mbasmanova , could you please help to review this PR? This PR is the follow up of https://github.com/facebookincubator/velox/pull/8615 to make sure all remote storage adapters have same error interface for file not found error.
Thanks.

Got a linter warning:

CC: @majetideepak


Unnecessary big dependency

I see that the library requires @nguniversal/express-engine, which is a pretty big dependency. Wouldn't it be easier for AoT apps to just be not dependent on it? I created the services on my app and removed the dependency, and they work fine because they can get the user agent from the current browser window. Apparently the express-engine is only for apps that run on servers and it's not useful for an app that is statically-served.
Thoughts?

Currently express-engine (5.0.0-beta.6) increases the bundle size by about ~600kb. Fix for this - https://github.com/angular/universal/pull/930 (available in beta.7, also fix in device-detector.service.ts required). Agree that express-engine is not useful for statically served apps and better not to use express-engine dependency in order not to increase bundle size.

@AhsanAyaz can you please take a look? Thanks!

@Mc128k , @safatseyeva
The support for @nguniversal/express-engine has been removed temporarily.
I will be looking into handling this once and for all in April because of lack of time. Feel free to play around and create a PR if someone can.
We could also split the packages into two. One for browsers and one for SSR. Not sure that's a good idea though.


Support mixed route paths

points of interest are:

SwapRouter.ts, especially lines 192-292 (https://github.com/Uniswap/router-sdk/pull/26/files#diff-d6c50d2e115ee74f2bd01e291289d53d8d555af6622dbc13ad117bd108177792R192-R292)
Since you last reviewed, I mostly added mixedRoute tests to src/entities/trade.ts

Changes look good to go! Feel free to merge @zhongeric


Add DOI to website

We should add the DOI to the website somewhere. Options include the top left so that it is carried to every page (which currently lists the version number), or we could just have it on one of the data pages.
The DOI is doi:10.13026/C2XW26.

Added to acknowledgements with https://github.com/MIT-LCP/mimic-website/commit/18a954e28210781fe17c7cbda28a06bc7c40d67e


Milestone: add devise

Blog app: add devise
In this project, I added the devise gem to the app and use it for the registration and login of users.
Summary:

Remove current_user method in ApplicationController✅
Install and setup devise✅
Can register a new user. ✅
User logs in with a combination of email and password.✅
Hashed password should be stored in the database.✅
Ask for confirmation of email.✅
Can reset password.✅

Screenshots 📷

🟢  Changes Applied
Summary

Add confirmation email request
change styles

Screenshots

New login window

New sign up window

Create new user

Confirmation link

Confirmation mail

Confirmation window

Signed in succesfully


Different autocomplete search results than on Mapzen website

The search on the Mapzen website displays results that include matches with special characters. I don't get the same results when using the API (using autocomplete and defaults similar to the ones on the website).

Hi @ungemachc, thanks for filing an issue. Could you please add an example query and results you're seeing? Would help us to debug this better. Thanks!


win: simplify mkdtemp

Use our builtin getrandom helper instead of the more verbose CryptoAPI
functions, which also happen to be deprecated.
CI: https://ci.nodejs.org/view/libuv/job/libuv-test-commit/1585/

@libuv/windows can I have one extra review please?

Landed in 9b2c9b6c, thanks for the reviews!


replace NODE_ENV with mode

Towards closing #40.
The breaking change is that I'm defaulting to production when an environment is not specified. Since webpack >= 4 does the same when mode is omitted, I believe we can do the same thing.
I don't think there is any webpack <= 3 code left to change. README will need to be updated - I think a separate PR will be needed since there'll be other changes to be added in the README once #40 is done.

Codecov Report

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

@@           Coverage Diff           @@
##           master      #49   +/-   ##
=======================================
  Coverage   98.78%   98.78%
=======================================
  Files           2        2
  Lines          82       82
=======================================
  Hits           81       81
  Misses          1        1

Impacted Files
Coverage Δ

src/index.js
98.73% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

Updated the README and move the mapping logic to a function.

I believe we are good to go! :D


malformed derive attribute input deletes derive arguments

Describe the bug
Adding a generic type to a derive macro deletes all derives

To Reproduce
cat <<EOF | rustfmt
#[derive(Debug, Foo<T>)]
enum Bar{}
EOF

This produces the following output, removing all derive attributes:
#[derive()]
enum Bar {}

Expected behavior
Something less nefarious, like rustc's
error: malformed `derive` attribute input

Meta

rustfmt version: rustrustfmt 1.4.24-stable (eb894d5 2020-11-05)
From where did you install rustfmt?: rustup
How do you run rustfmt: In an editor with undo hopefully :smiling_imp:

Just noticed this as well:
#[derive(Debug, , Default)]
struct Struct(i32);

turns into this:
#[derive()]
struct Struct(i32);

which is bizarre when you're deleting one of the derives and you save partway through!

This has been fixed in source but not backported to a released version. Will try to do so for the upcoming 1.4.28 release

Closing as a duplicate of #3898, fix has been backported and will be in the next release


Change for overriding OUTPUT_DIR for reference implementation

This change allows results to be output to a custom folder while using the reference implementation.

Outdated


panic on missing input variable

It would be great to detect the mistake during initial parse than at run time.
type Mutation {
  updateHuman(ClientMutationId: String!, input: UpdateHumanInput!): updateHumanPayload
}

mutation M($in: UpdateHumanInput!) {
  updateHuman(clientMutationId: "1",input: $in ) {
    ...
  }
}

above gives the panic, as clientMutationId should be ClientMutationId
below works
mutation M($in: UpdateHumanInput!) {
  updateHuman(ClientMutationId: "1",input: $in ) {
    ...
  }
}

stack
2016/11/18 18:04:46 graphql: graphql: panic occured: runtime error: invalid memory address or nil pointer dereference
goroutine 36 [running]:
github.com/neelance/graphql-go/internal/exec.(*request).handlePanic(0xc4201a18c0)
	/Users/bsr/.../external/src/github.com/neelance/graphql-go/internal/exec/exec.go:392 +0x123
panic(0x5b1760, 0xc420012060)
	/usr/local/go/src/runtime/panic.go:458 +0x243
github.com/neelance/graphql-go/internal/exec.(*fieldExec).execField2(0xc4204513b0, 0x934400, 0xc4201c5ad0, 0xc4201a18c0, 0xc4201a17c0, 0x5c0960, 0x984ae8, 0x16, 0x937a20, 0xc420472c80, ...)
	/Users/bsr/.../external/src/github.com/neelance/graphql-go/internal/exec/exec.go:664 +0x1f9
github.com/neelance/graphql-go/internal/exec.(*fieldExec).execField(0xc4204513b0, 0x934400, 0xc4201c59b0, 0xc4201a18c0, 0xc4201a17c0, 0x5c0960, 0x984ae8, 0x16, 0xc4201872c0)
	/Users/bsr/.../external/src/github.com/neelance/graphql-go/internal/exec/exec.go:640 +0x3b2
github.com/neelance/graphql-go/internal/exec.(*objectExec).execSelectionSet.func2()
	/Users/bsr/.../external/src/github.com/neelance/graphql-go/internal/exec/exec.go:573 +0x3f4
github.com/neelance/graphql-go/internal/exec.(*objectExec).execSelectionSet.func1(0xc42019d540)
	/Users/bsr/.../external/src/github.com/neelance/graphql-go/internal/exec/exec.go:524 +0xc0
INFO     2016-11-18 23:04:46,763 module.py:788] default: "POST /graphql HTTP/1.1" 200 125
github.com/neelance/graphql-go/internal/exec.(*objectExec).execSelectionSet(0xc4204568a0, 0x934400, 0xc4201c59b0, 0xc4201a18c0, 0xc420187260, 0x5c0960, 0x984ae8, 0x16, 0xc4201872c0, 0x54701)

This is probably related to #5. You want an error on parse time of the query, correct?

yes. not too critical but nice to have. thanks.

thanks.. it doesn't happen anymore.


[gym][wrappers] StackObservation is not preserving the order for OrderedDict observation spaces.

observation_stack.StackObservation changes the key order of an OrderedDict observation_space while preserving the correct key order of observation. If it is used in conjunction with FlattenObservation, we find ourselves with env.observation and env.observation_spaces arrays with indices that doesn't correspond to each other. A side effect is then that the obs (after step) becomes different from env.observation because it is then clipped wrongly by a faulty env.observation_space.
Reproduction script:
from gym_jiminy.common.wrappers import FlattenObservation, StackObservation
from gym_jiminy.envs.atlas import AtlasPDControlJiminyEnv

env = StackObservation(AtlasPDControlJiminyEnv(),skip_frames_ratio=-1,
            num_stack=2,
            nested_filter_keys=[["t"]],
        )
_, _ = env.reset(seed = 0)

print("======= env.observation keys() ==========")
for key in env.observation:
    print(key)
print("======= env.observation_space keys() ==========")
for key in env.observation_space:
    print(key)

env = FlattenObservation(StackObservation(AtlasPDControlJiminyEnv(),skip_frames_ratio=-1,
            num_stack=2,
            nested_filter_keys=[["t"]],
        ))
_, _ = env.reset(seed = 0)

N = 100
for _ in range(N):
    env.step(env.action_space.sample())
obs, _, _, _, _ = env.step(env.action_space.sample())

print("=========== Bounds of unflatten (stacked) env.env.observation space of 't' ========" )
print(env.env.observation_space["t"].low)
print(env.env.observation_space["t"].high)

print("=========== Bounds of flatten env.observation_space first 2 elements ========" )
print(env.observation_space.low[:2])
print(env.observation_space.high[:2])

print("=========== env.observation's first 2 elements ========" )
print(env.observation[:2])
print("=========== obs' 2 first elements ========" )
print(obs[:2])
print("======= The above two lines should be equals ! ===========")

Here is a fix if you think this solution works for you:
def _unflatten_as(data: StructNested[Any],
                  data_leaf_it: Iterator) -> StructNested[Any]:
    """Internal method un-flattening a sequence into a nested data structure by
    calling itself recursively on each top-level nodes that are not leaves and
    fetching the next leaf value otherwise.
    """
    data_type = type(data)
    if issubclass_mapping(data_type):  # type: ignore[arg-type]
        return data_type(OrderedDict({  # type: ignore[call-arg]
            key: _unflatten_as(value, data_leaf_it)
            for key, value in data.items()  # type: ignore[union-attr]
        }))
    if issubclass_sequence(data_type):  # type: ignore[arg-type]
        return data_type(tuple(  # type: ignore[call-arg]
            _unflatten_as(value, data_leaf_it) for value in data
        ))
    return next(data_leaf_it)

The solution just wrapped the created dict by the OrderedDict class.

Ok the chain of consequences is quite complex and unfortunate x) I will add a unit test for this.
for the record, it should be slightly faster to flatten before anything else, including normalization for instance. Post-processing is bound to be slower, even when using pre-compiled methods, when the memory layout is fragmented.


Markdown round-tripping and recorded edit history

Currently if you edit metadata and set the description to:
# Hi there

When you later go to edit it the editable text will have been converted to:

hi

It would be nice if round-trip editing worked here.

Three options:

Use an HTML-to-markdown conversion routine (complex, risky)
Store the original Markdown in an additional table, so it can be presented to edit again later
A weird hack where the original Markdown is stashed in an HTML  comment in the stored description

I'm torn between option 2 and option 3.

Option 2 could be compatible with a feature that records the full history of changes that were made, which is a nice-to-have already.

I'm going to do the history thing. Need to design the schema for that - I could do individual columns or I could cheat and use blobs of JSON.

Considered a migration to take existing table and migrate content to the new history table (in addition to using it to populate the core tables), but two problems with that:

No author or timestamp information - would have to default to null author and current time
That table stores HTML, not Markdown - but the new edit table will be storing Markdown

For the schema, I'm going to go with a single table that stores the data they entered in the form as JSON, but has nullable columns to indicate WHAT they edited. Something like this:

database_name
resource_name
column_name
actor_id
updated_at
fields_json

null
null
null
1
2024-08-05T14:30:00Z
{"license": "Apache", "license_url": "https://www.apache.org/licenses/LICENSE-2.0"}

content
null
null
1
2024-08-06T09:15:30Z
{"description": "This is a description"}

content
news
null
3
2024-08-06T11:45:22Z
{"license": "Apache", "license_url": "https://www.apache.org/licenses/LICENSE-2.0"}

Manual testing of the code to record edits seems to work:

Needs tests, also the code that recovers the latest markdown version from the edit logs to populate the form.
There's a potential conflict here: what happens if some other plugin has called datasette.set_instance_metadata() to set description_html to something else since it was edited with this plugin? Since we don't know WHEN that happened we might prefill the form field with the saved markdown from our last edit even though the actual description in the core metadata tables has been modified since then.

I'm going to change the form field name to description_markdown to make it more obvious what is going on here.

Next steps: comprehensive tests and a mechanism to display the history.

I started on the tests using the new gemini-1.5-pro-exp-0801 via https://aistudio.google.com/app/prompts/new_chat and got a pretty good result - files-to-prompt . --ignore LICENSE | pbcopy and then pasted that in and added:

Provide me with additional unit tests that exercise the new feature where edits are recorded and their markdown is then used to prefill the HTML form when the user later edits the same thing

It gave me this.
I had to make a few tweaks to get the tests to work but still pretty useful.


Feats are incomplete.

Grappler is the only feat that is in the data.

Hi JoshPoole09
Unfortunately this is the only feat that is listed inside the DnD 5e SRD, you can reference it here on page 75. I also thought I was missing data as well when I first looked into this project.
https://www.dndbeyond.com/resources/1781-systems-reference-document-srd?srsltid=AfmBOooblayh4mfxjJBalcVzi4bsvOgfRVk6Cl1WtZRTCSYp_HIkdpu_


Document special behaviour of "Softroot" item

The Softroot Item (first entry of the navigation which is set as "Home") has special attributes and behaviours.
For example when setting off "in Menu" to the softroot, all sub children still will be shown within render_menu. All other menu entries would hide those elements.
There might be other oddities which I'm not aware off and might be documented. This can cause some question marks.

closed and collected in #4597


Bug 2282841: UI change for creation of pvc label selector for managed applications

BZ: https://bugzilla.redhat.com/show_bug.cgi?id=2282841
Design change: https://www.figma.com/design/74GFRiBTJR1RR3CTG7fEBs/Create-custom-PVC-label-selector?node-id=0-459&t=zG8QX6mH6ea2fJOY-0

/retitle Bug 2282841: UI change for creation of pvc label selector for managed applications

/retitle UI change for creation of pvc label selector for managed applications

LGTM
@bipuladh can u plz tag the PR if it looks okay ?

/cherry-pick release-4.17

/cherry-pick release-4.17

/cherry-pick release-4.17-compatibility


openapi2jsonschema.py fails for AlertmanagerConfig

I tried to integrate kubeconform into the CI workflow of an internal project. On the intial run
helm template . | kubeconform
it had trouble finding the schemas for

ExternalSecret
AlertmanagerConfig
PrometheusRule
ServiceMonitors

I followed the advice in https://github.com/yannh/kubeconform/issues/51#issuecomment-880223640 to generate a schema using openapi2jsonschema.py from the OpenAPI-Specs provided for AlertmanagerConfig, PrometheusRule and ServiceMonitors.
It worked for ServiceMonitors and PrometheusRule but failed for AlertmanagerConfig with the following error:
convert-crd_1  | Traceback (most recent call last):
convert-crd_1  |   File "/apps/convert/openapi2jsonschema.py", line 123, in <module>
convert-crd_1  |     for y in yaml.load_all(f, Loader=yaml.SafeLoader):
convert-crd_1  |   File "/usr/local/lib/python3.8/site-packages/yaml/__init__.py", line 93, in load_all
convert-crd_1  |     yield loader.get_data()
convert-crd_1  |   File "/usr/local/lib/python3.8/site-packages/yaml/constructor.py", line 45, in get_data
convert-crd_1  |     return self.construct_document(self.get_node())
convert-crd_1  |   File "/usr/local/lib/python3.8/site-packages/yaml/constructor.py", line 60, in construct_document
convert-crd_1  |     for dummy in generator:
convert-crd_1  |   File "/usr/local/lib/python3.8/site-packages/yaml/constructor.py", line 408, in construct_yaml_seq
convert-crd_1  |     data.extend(self.construct_sequence(node))
convert-crd_1  |   File "/usr/local/lib/python3.8/site-packages/yaml/constructor.py", line 129, in construct_sequence
convert-crd_1  |     return [self.construct_object(child, deep=deep)
convert-crd_1  |   File "/usr/local/lib/python3.8/site-packages/yaml/constructor.py", line 129, in <listcomp>
convert-crd_1  |     return [self.construct_object(child, deep=deep)
convert-crd_1  |   File "/usr/local/lib/python3.8/site-packages/yaml/constructor.py", line 100, in construct_object
convert-crd_1  |     data = constructor(self, node)
convert-crd_1  |   File "/usr/local/lib/python3.8/site-packages/yaml/constructor.py", line 427, in construct_undefined
convert-crd_1  |     raise ConstructorError(None, None,
convert-crd_1  | yaml.constructor.ConstructorError: could not determine a constructor for the tag 'tag:yaml.org,2002:value'
convert-crd_1  |   in "<file>", line 3916, column 29

https://raw.githubusercontent.com/prometheus-operator/prometheus-operator/main/example/prometheus-operator-crd/monitoring.coreos.com_alertmanagerconfigs.yaml
https://raw.githubusercontent.com/prometheus-operator/prometheus-operator/main/example/prometheus-operator-crd/monitoring.coreos.com_prometheusrules.yaml
https://raw.githubusercontent.com/prometheus-operator/prometheus-operator/main/example/prometheus-operator-crd/monitoring.coreos.com_servicemonitors.yaml

I submitted a PR to fix that.
In the meanwhile, you can this version of JSON Schema that I have created from your YAML:
https://gist.github.com/eyarz/c2c5665a877491f7fc0e84176fff8011


readme: add support server

since the widget is disabled I've chosen a custom badge, does it look good or should we use the "x online" one

since the widget is disabled

I have just enabled it.

I'd say this looks better, using Discord's official embedded images:

<div align="center">

![Sapphire Logo](https://cdn.skyra.pw/gh-assets/sapphire.png)

# Sapphire

**A pleasant Discord Bot framework**

[![GitHub](https://img.shields.io/github/license/sapphire-project/framework)](https://github.com/sapphire-project/framework/blob/main/LICENSE.md)
[![Total alerts](https://img.shields.io/lgtm/alerts/g/sapphire-project/framework.svg?logo=lgtm&logoWidth=18)](https://lgtm.com/projects/g/sapphire-project/framework/alerts/)
[![Language grade: JavaScript](https://img.shields.io/lgtm/grade/javascript/g/sapphire-project/framework.svg?logo=lgtm&logoWidth=18)](https://lgtm.com/projects/g/sapphire-project/framework/context:javascript)
[![Coverage Status](https://coveralls.io/repos/github/sapphire-project/framework/badge.svg?branch=main)](https://coveralls.io/github/sapphire-project/framework?branch=main)
[![npm](https://img.shields.io/npm/v/@sapphire/framework?color=crimson&label=TypeScript%20version&logo=npm&style=flat-square)](https://www.npmjs.com/package/@sapphire/framework)
[![Depfu](https://badges.depfu.com/badges/e367f2c68b857253ca23e1e8d73d1e14/count.svg)](https://depfu.com/github/sapphire-project/framework?project_id=14147)

[![Support Server](https://discord.com/api/guilds/737141877803057244/embed.png?style=banner2)](https://join.skyra.pw/sapphire)

</div>

I love it

The npm link will work once @kyranet publishes 😇

/approve (I'm in Zoom rn can't open GitHub)


resources/app folder has broken permissions

The /resources/app folder can't be deleted because its permissions are somehow broken. I get this error either by trying to package as an asar or when trying to overwrite a previous build when using the Programmatic API with electron-packager installed locally in the folder.
{ Error: EPERM: operation not permitted, rmdir 'D:\user\appNameFolder\appName-win32-x64\resources\app'
  at Error (native)
  errno: -4048,
  code: 'EPERM',
  syscall: 'rmdir',
  path: 'D:\\user\\appNameFolder\\appName-win32-x64\\resources\\app' }

When I use command line using the global package.
EPERM: operation not permitted, rmdir 'C:\Users\User\AppData\Local\Temp\electron-packager\win32-x64\appName-win32-x64\resources\app'

After this error occurs, I can delete the app folder myself but I can't using the rmdir Windows command and it returns "Access is Denied". If I check the permissions through the properties window it has the same settings as any other folder. I'm not sure what's causing this error and I've tried investigating but haven't gotten anywhere so far.
I figured it might be problem with npm but I've tried reinstalling npm and nodejs multiple times to no avail.
After the error occurs once with the command line, using it a second time will cause no console output. This can be fixed by deleting the AppData/Local/Temp/electron-packager folder. It gets stuck here because it doesn't have permission to delete the app folder from the previous build.

Which version of electron-packager are you using?

7.0.4

What CLI arguments are you passing? Alternatively, if you are using the API, what parameters are
you passing to the packager() function?

for the packager() function
const options = {
    platform: 'win32',
    arch: 'x64',
    dir: '.',
    version: '1.2.3',
    tmpdir: false,
    asar: true,
    overwrite: true
};

for the command line
electron-packager . --platform=win32 --arch=x64 --version=1.2.3

Although I have tried many other options with no success.

What version of Electron are you building with?

Tried 1.2.1 and 1.2.3

What is the host platform are you running electron-packager on?

Windows 10 x64

What target platform(s)/architecture(s) are you building for?
win32 x64
Please provide either a failing testcase or detailed steps to reproduce your problem.
Installing it both globally

I wonder if this is related to #375, despite not being on OSX?
CC: @jprichardson

It might be related but there are few differences. It still doesn't work using tmpdir=false. Also, I can delete it as a user but not through command line which is the opposite to that issue.
It's been working fine up until recently but I'm not exactly sure what triggered this.

Try an earlier version of electron-packager?

Yeah, I don't think this one is related to #375. Windows has some funky delete issues at times - I'm not saying that's what's going on here, but I've ran into similar strange issues in the past related to these sorts of things.
Possibly related: https://github.com/isaacs/rimraf/issues/105. Also, not the same error, but discusses more Windows related delete issues: https://github.com/isaacs/rimraf/issues/72.

Possible workaround: use asar: true.
Possible, because electron-packager still doesn't create asar directly from app, but copies and only then creates asar archive.

Thank you everyone for the help, I finally solved the issue even although I think it wasn't directly related to electron-packager.
I'm not sure how but the folder had been set to read-only. It took a while to realize this because I've never dealt with Windows permission issues before. Everything inside the folder was writable and setting it through the properties window had no effect.
I only found out that it was read-only by using ls in powershell and saw there was an r mode where there shouldn't be. I fixed the issue using the command  attrib -R appNameFolder.

I'm not sure how but the folder had been set to read-only.

Yep, so it was the pesky https://github.com/isaacs/rimraf/issues/105 then.

Yeah looks like it was something to do with that.

After getting this error, trying to repackage doesn't work (or do anything), even using --overwrite. Removing the read-only permission from the app folder as described above and deleting the %localappdata%/Temp/electron-packager/  folder then allowed it to work next time

@binaryfunt Are you using SVN for your project? I ran into this issues while using TortoiseSVN for the project.
Recently I tried moving the .svn folder out of my project, then runing attrib -r /d /s on the project root. After that I was able to build repeatedly. (Before that, I had to run the attrib every time, as you stated.)
If I then move the .svn folder back in, it still works. The only explanation I can think of is that TortoiseSVN doesn't like the .svn folder not being readonly, but it applies it in a way that affects the project folder. I'm really grasping at straws here, though.
At this point I am able to rebuild repeatedly without issue. Though if it is SVN, a project update may cause a regression. At the very least, I assume this would have to be done by anyone who checks out the project.


How to remove duplicates from UNWIND query result ?

OrientDB Version: 3.0.17
OS: Mac OS X 10.14.2
Expected behavior
I have a case when UNWIND is used in query, it sometimes returns the same items more times. This behavior is totally correct but, how do I eliminate duplicates in it, please?
Thanks.

Hi @petervavro
Which is the exact query? Typically a SELECT DISTINCT is enough to solve the problem
Thanks
Luigi

@luigidellaquila Thank you for answer, is this documented somewhere please?


EnsembleDriftAuditor

One possible auditor is based on the deviation of trajectories generated by multiple ensemble members at a time

This could be useful in proxima too, as a replacement for our strategy of randomly inserting audits. We could instead audit after the drift gets too big


Google plus button breaks all buttons

Hi,
I have encountered a problem with Google plus button - I want to use Facebook, Twitter and Google Plus buttons. When I try this setting on localhost everything works just fine. But when I move it to my hosting nothing happens after I click on any button. But when I disable the Google Plus button everything else is back to normal, working just fine.
I thought that the problem might be the sharrre.php - I made sure permissions allow execution, I tried to put it to root, I tried to put it to that page's directory - http://www.simplyeasy.cz/war-on-procrastination/ - when I navigate to sharrre.php it returns {"url":null,"count":0}
Curl is enabled... I don't know what else could that be. No error message, no clue. I am afraid I will have to use Sharre without Google Plus.
I probably made some stupid mistake - If you have any idea what might be the problem I would really appreciate it.

Hi honzzz,
When I test your URL I have this error:
Warning:  curl_setopt_array() [function.curl-setopt-array]: CURLOPT_FOLLOWLOCATION cannot be activated when safe_mode is enabled or an open_basedir is set in /home/simplyea/domains/simplyeasy.cz/public_html/war-on-procrastination/sharrre.php on line 56

Hi Julienh,
thank you very much. It seems like something related to my hosting company's setting and I guess there is not much I can do about it. Is there any workaround?
BTW, could you please tell me... how can I reproduce that warning? I don't see any warnings when I run sharrre.php.

You can see that warning here:
http://www.simplyeasy.cz/war-on-procrastination/sharrre.php?url=http%3A%2F%2Fwww.simplyeasy.cz%2Fwar-on-procrastination%2F&type=googlePlus
Try to disable safe_mode

Thanks again Julienh - safe_mode is disabled, it seems that open_basedir is the problem and I cannot do anything about it - I am on shared hosting and they would not let me change this for security reasons.

When Google will add API to get share number, the PHP script won't be necessary.


chore(main): release 0.2.2

:robot: I have created a release beep boop
0.2.2 (2023-07-03)
Bug Fixes

remove unused protein_info_table (be4cb0d)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/socialgene/sgnf/releases/tag/v0.2.2 :sunflower:


Change destination address to be signingAddress

Fixes #2128.
This makes it so that Web3Torrent provides the signingAddress of its peer and wallet as the destination when creating a channel. Similarly, the wallet uses the signing address in the ApproveBudgetAndFund call which then sets up the ledger channel as appropriate. This small changes allows the user of Web3Torrent to use the app, close tabs and switch accounts, and return to the app and use it again.
When withdrawing, the selected address is actually used, so withdrawing works as expected. This change only really becomes slightly confusing if you challenge a channel, but even then it is not that confusing.
It's worth considering whether or not it makes sense for the app to even be providing a destination value to the wallet.

Unless I have misunderstood, this would mean that when you withdraw from the ledger channel, the funds get paid out to an account that is not known to metamask, and getting control of those funds requires digging into IndexedDB for a private key?

When withdrawing, the selected address is actually used, so withdrawing works as expected. This change only really becomes slightly confusing if you challenge a channel, but even then it is not that confusing.

Do you mean that we can basically overwrite the outcome with the one that we really want, as long as we are all collaborating?
I'm not sure that it's worth doing this just to support the use switching accounts in metamask. Won't #2140 mostly fix that problem, anyway?

Unless I have misunderstood, this would mean that when you withdraw from the ledger channel, the funds get paid out to an account that is not known to metamask, and getting control of those funds requires digging into IndexedDB for a private key?

Actually I take back what I said earlier. I thought what was already implemented correctly was that, regardless of ledger channel outcomes, when you call CloseAndWithdraw the account selected in MetaMask would be the recipient of the funds. It looks like it should be implemented that way based on this code:
https://github.com/statechannels/monorepo/blob/49b9585cd7b981e9c21fd36994e862539a0fdfa2/packages/xstate-wallet/src/messaging.ts#L252-L262

Do you mean that we can basically overwrite the outcome with the one that we really want, as long as we are all collaborating?

This is how I thought it worked (see above)

I'm not sure that it's worth doing this just to support the use switching accounts in metamask. Won't #2140 mostly fix that problem, anyway?

#2140 does not fix the problem of switching accounts outside of the tab and then returning AFAICT because your ledger channel's destination address is of the previous session.
There is a check in the wallet which ensures equality of the target channel destination (provided by the app) and the ledger channel destination:
https://github.com/statechannels/monorepo/blob/49b9585cd7b981e9c21fd36994e862539a0fdfa2/packages/xstate-wallet/src/utils/outcome.ts#L71-L72

Also the fact that the tests passed gave me the impression that the currently selected MetaMask address would be getting the funds. However maybe instead it's just an indication that this is not tested. I haven't checked just yet.

Yeah I think you have touched on some stuff that we should fix around concluding and withdrawing:

We should get the necessary data to conclude the ledger channel from the latest state we have for that channel (not window.ethereum.selectedAddress, not even store.chain.selectedAddress)
We should test that funds are returned to whichever account was selected in metamask at the point when ApproveBudgetAndFund was called.

(In a previous iteration of the contracts, IIRC you could specify a new address when withdrawing. That is not currently supported, though).

We discussed this on standup and the plan is to:

Rename selectedAddress to idealOutcomeAddress or something like that which conveys that this is not a selected address but rather an address that, if ETH were sent there, would be easily accessible by the user. It will be set as the selected address in MetaMask the first time any app ever calls EnableEthereum.

Store idealOutcomeAddress in IndexedDB and re-use that as the destination address for all channels in the future instead of checking ethereum.selectedAddress each time.

Remove destination from being a property that can be provided by the application in the call to CreateChannel

Suggestion: rename selectedAddress to destinationAddress?


Message 0x022b - during App connect

Value goes from 0 to 1 during app connect
Unprocessed message SparkIO 22B length 7:0
Message: 22B
undefined LIVE connection messages
Unprocessed message SparkIO 22B length 7:1
Message: 22B
undefined LIVE connection messages

This is a request for the LIVE preset checksums - the byte is 0 for Input 1 and 1 for Input 2

Sorted


Rename instructlab.config to instructlab.configuration

This changed in the instructlab repo, so match it.
Signed-off-by: Russell Bryant<EMAIL_ADDRESS>

do we want to backport this :thinking:

do we want to backport this 🤔

no - this is the sdg repo, it's fine

some more context -- the fact that this library is still importing stuff from instructlab is a bug tracked at #6
We're just still in transition here so it's a bit messy ...

oops, I need more coffee. I thought we were in a different repo :sweat_smile:


Fix issue 5007: heap buffer overflow with C locale

This PR issue #5007. Invalid memory access was reproducible with:
$ valgrind ./vim --clean -c 'set enc=latin1' -c 'x`=' 2> vg.log
$ cat vg.log
==23162== Memcheck, a memory error detector
==23162== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==23162== Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright info
==23162== Command: ./vim --clean -c set\ enc=latin1 -c x`=
==23162==
==23162== Invalid read of size 1
==23162==    at 0x1A3357: separate_nextcmd (ex_docmd.c:4302)
==23162==    by 0x1A85A2: do_one_cmd (ex_docmd.c:2142)
==23162==    by 0x1A85A2: do_cmdline (ex_docmd.c:966)
==23162==    by 0x3320FF: exe_commands (main.c:3133)
==23162==    by 0x3320FF: vim_main2 (main.c:795)
==23162==    by 0x13A584: main (main.c:444)
==23162==  Address 0xb32bf84 is 0 bytes after a block of size 4 alloc'd
==23162==    at 0x4C2FB0F: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==23162==    by 0x2084F0: lalloc (misc2.c:924)
==23162==    by 0x208F4E: alloc (misc2.c:827)
==23162==    by 0x208F4E: vim_strsave (misc2.c:1276)
==23162==    by 0x1A72CF: do_cmdline (ex_docmd.c:896)
==23162==    by 0x3320FF: exe_commands (main.c:3133)
==23162==    by 0x3320FF: vim_main2 (main.c:795)
==23162==    by 0x13A584: main (main.c:444)

The change to macros MB_PTR2LEN, MB_PTR_ADV
and MB_CPPTR_ADV seems risky as it can affect many
pieces of code, but all tests pass at least.

Codecov Report

Merging #5021 into master will decrease coverage by 0.43%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #5021      +/-   ##
==========================================
- Coverage   81.96%   81.53%   -0.44%
==========================================
  Files         133      133
  Lines      146563   146563
==========================================
- Hits       120135   119500     -635
- Misses      26428    27063     +635

Impacted Files
Coverage Δ

src/gui_gtk_x11.c
49.21% <0%> (-8.9%)
:arrow_down:

src/gui.c
58.41% <0%> (-5.29%)
:arrow_down:

src/gui_gtk.c
28.57% <0%> (-2.89%)
:arrow_down:

src/os_unix.c
60.91% <0%> (-2.55%)
:arrow_down:

src/buffer.c
82.35% <0%> (-2.38%)
:arrow_down:

src/highlight.c
78.22% <0%> (-2.34%)
:arrow_down:

src/if_xcmdsrv.c
84.2% <0%> (-1.98%)
:arrow_down:

src/misc2.c
85.88% <0%> (-1.22%)
:arrow_down:

src/testing.c
88.81% <0%> (-1.17%)
:arrow_down:

src/ui.c
67.98% <0%> (-1.08%)
:arrow_down:

... and 29 more

Continue to review full report at Codecov.

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

Dominique wrote:

dpelle commented on this pull request.

@@ -230,11 +230,11 @@

PTR2CHAR(): get character from pointer.
/
/ Get the length of the character p points to, including composing chars */
-#define MB_PTR2LEN(p)	    (has_mbyte ? (*mb_ptr2len)(p) : 1)
+#define MB_PTR2LEN(p)	    (has_mbyte ? (*mb_ptr2len)(p) : (*p == NUL ? 0 : 1))

Hmm, now I think it should simply be:
#define MB_PTR2LEN(p) *mb_ptr2len(p)

... but then I don't really see the need for a macro anymore.
Same remark for other macros.

Yes, mb_ptr2len() should work for any encoding.
The macro was for when there was still FEAT_MBYTE.
--
The Law of VIM:
For each member b of the possible behaviour space B of program P, there exists
a finite time t before which at least one user u in the total user space U of
program P will request b becomes a member of the allowed behaviour space B'
(B' <= B).
In other words: Sooner or later everyone wants everything as an option.
-- Vince Negri
/// Bram Moolenaar --<EMAIL_ADDRESS>-- http://www.Moolenaar.net   \
///        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \
\\  an exciting new programming language -- http://www.Zimbu.org        ///
\\            help me help AIDS victims -- http://ICCF-Holland.org    ///


remove the duplicate files

In GitLab by @tmon546596046 on Apr 23, 2018, 15:42
there are some deplicate files in make/dev and make/release directories. please review the directory struct and remove the dups.

In GitLab by @yhua123 on Nov 8, 2019, 07:49
These duplicate files are meant to make the Makefile easier to write. The problem is the synchronization of file changes. How to balance is a problem that requires careful consideration and design. Who have better suggestion?

In GitLab by @sokril on Nov 8, 2019, 08:21
assigned to @wknet123

In GitLab by @sokril on Dec 26, 2019, 03:21
changed the description

In GitLab by @luotian-github on Mar 25, 2020, 01:50
Need a united makefile to handle both dev and release


feat: add push based subscription for new topics

Description
Adds a specific topic to which all consumer services subscribe. Messages in this topic contain the names of any new topics created by publishers, and consumers will automatically add the new topics to their subscription list.
In this way we can reduce the time needed to add a new topic to a couple of seconds, instead of relying on the metadata.max.age.ms parameter (#1223)
Fixes #1253
Type of change

[x] New feature (non-breaking change which adds functionality)

How Has This Been Tested?
Full deployment of the stack on my local minikube cluster

[x] Create new topics with MQTTExplorer. The new topics are received by kafka-to-postgresql in the matter of seconds
[ ] Injecting new topics via NodeRed does not work, but that is probably NodeRed's problem. In a production environment all the new topics will eventually pass through MQTT.

Checklist:

[ ] I have made corresponding changes to the documentation
[x] I have made corresponding changes to the changelog (if needed).
[ ] I have made corresponding notices to the upgrade instructions (if needed)

Changelog changes
Added push-based detection of new topics
Upgrade instructions
not needed

Codecov Report

Merging #1257 (792f4d5) into main (ba3ab6e) will decrease coverage by 0.09%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main    #1257      +/-   ##
==========================================
- Coverage   12.44%   12.34%   -0.10%
==========================================
  Files          29       29
  Lines        8302     8368      +66
==========================================
  Hits         1033     1033
- Misses       7197     7263      +66
  Partials       72       72

Impacted Files
Coverage Δ

golang/internal/kafka.go
0.00% <0.00%> (ø)

golang/internal/kafkaMessageProcessing.go
0.00% <0.00%> (ø)

golang/internal/kafkaSharedTypes.go
0.00% <0.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Issue with k8s.io/docs/tasks/run-application/run-replicated-stateful-application/

NAME          READY   STATUS       RESTARTS   AGE     IP                   NOMINATED NODE   READINESS GATES
pod/mysql-0   2/2     Running      0          7m53s   <IP_ADDRESS>
pod/mysql-1   2/2     Running      0          6m46s   <IP_ADDRESS>
pod/mysql-2   0/2     Init:Error   4          2m25s   <IP_ADDRESS>
NAME                 TYPE        CLUSTER-IP     EXTERNAL-IP   PORT(S)    AGE   SELECTOR
service/mysql        ClusterIP   None                   3306/TCP   97m   app=mysql
service/mysql-read   ClusterIP   <IP_ADDRESS>           3306/TCP   97m   app=mysql
NAME                     READY   AGE     CONTAINERS         IMAGES
statefulset.apps/mysql   2/3     7m53s   mysql,xtrabackup   mysql:5.7,gcr.io/google-samples/xtrabackup:1.0
Failed container logs
[root@worker-2 ~]# docker logs ef1

[[ -d /var/lib/mysql/mysql ]]
++ hostname
[[ mysql-2 =~ -([0-9]+)$ ]]
ordinal=2
[[ 2 -eq 0 ]]
ncat --recv-only mysql-1.mysql 3307
xbstream -x -C /var/lib/mysql
Ncat: Could not resolve hostname "mysql-1.mysql": Name or service not known. QUITTING.
xtrabackup --prepare --target-dir=/var/lib/mysql
xtrabackup version 2.4.4 based on MySQL server 5.7.13 Linux (x86_64) (revision id: df58cf2)
xtrabackup: cd to /var/lib/mysql
xtrabackup: Error: cannot open ./xtrabackup_checkpoints
xtrabackup: error: xtrabackup_read_metadata()
xtrabackup: This target seems not to have correct metadata...
InnoDB: Number of pools: 1
InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
xtrabackup: Warning: cannot open ./xtrabackup_logfile. will try to find.
InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
xtrabackup: Fatal error: cannot find ./xtrabackup_logfile.
xtrabackup: Error: xtrabackup_init_temp_log() failed.

Hi @Syed-Saifulla
I can see that you have provided some diagnostics. I'm guessing that you want to report a bug, get help, or possibly ask for an improvement to the site. Can you explain more about what's on your mind?
/triage needs-information


Basic Login via js api not working

I don't thing it's me?
`var fs = require('fs'),
https = require('https');
var ssl = {
key: fs.readFileSync('./', 'utf8'),
cert: fs.readFileSync('./', 'utf8'),
ca: [fs.readFileSync('./', 'utf8'),
fs.readFileSync('./', 'utf8')]
};
var express = require('express');
var ParseServer = require('parse-server').ParseServer;
var databaseUri = ' ';
var port = process.env.PORT || 4337;
//var port = 443;
var api = new ParseServer({
databaseURI: databaseUri,
cloud: __dirname + '/cloud/main.js',
serverURL: 'aa',
appId: 'aa,
'javascriptKey':'aa',
restAPIKey: 'a',
clientKey:'a',
facebookAppIds :['a'],
masterKey: 'a'
});
var app = express();
// Serve the Parse API on the /parse URL prefix
var mountPath = '/a';
app.use(mountPath, api);
app.use(express.static('public'));
// Parse Server plays nicely with the rest of your web routes
app.get('/', function(req, res) {
res.status(200).send('I dream of being a web site.');
});
app.listen(4338,function () { console.log('Server on port 4338'); });
https.createServer(ssl, app)
.listen(port, function() {
console.log('Server running on port ' + port + '.');
});`
Response is {"error":"unauthorized"}
My appid is correct.

Cross issue: https://github.com/ParsePlatform/parse-server/issues/1615

bump

We have lots of passing test cases that cover these features. Can you post some code that reliably reproduces your issue? Ideally as a test case we can add to our test suite.

I'm literally using the out of box example on a server that already works with IOS. I can pm you the site if you want to have a gander.

I've tried multiple things even using the master key.  Downloaded yesterday.

The SDK won't encounter cross-domain issues, since it uses special POST requests with embedded methods.
Can you provide the code you're running with the Parse SDK (not Parse Server) that produces the {"error": "unauthorized"} you mention?

`
var user = new Parse.User();
user.set("username", "my name");
user.set("password", "my pass");
user.set("email", "email@example.com");
// other fields can be set just like with Parse.Object
user.set("phone", "415-392-0202");
user.signUp(null, {
success: function(user) {
console.log(user);
},
error: function(user, error) {
// Show the error message somewhere and let the user try again.
console.log(error);
}
});
`

Are you pointing your Parse SDK at your Parse Server location?
Parse.initialize("YOUR_APP_ID");
Parse.serverURL = 'http://your.server.url:port/path'

absolutely.

I've even tried it with master key, js key, etc. ...

So, the response you're receiving
{"error":"unauthorized"}

results when you send the wrong keys to the server. I'd double-check that
a) you're actually communicating with your server, and not parse.com
b) you're using the right keys
If our out-of-the box experience were broken, we would have tests that caught that. The error is somewhere in your configuration. Sorry.

I can see my server in the chrome net console. It's correct.

What it's pointing to is the latest version of parse-server is broken. I have an older different version running on a separate machine with the same exact config that doesn't have these errors.

Your iOS app points at the new server and works, right?

My ios points at a clone of the same server with the same config. The difference is I ran parse update on this new box.

Unfortunately, unless you can provide a more specific reproducible case, there's nothing I can do to help.
This does not sound like a bug within the JS SDK (you say yourself that changing the parse-server breaks things, not the SDK), so I am closing this issue.

Hi, I know this is an old bug, but I'm experiencing the same problem. The point is everything works well if my parse-server is version 2.2.23 or below. But if I upgrade my server to version 2.2.24 my JS client gets this response: {"error": "unauthorized"}
My iOS client works fine both in version 2.2.23 and 2.2.24. I've tested with parse-server versions 2.2.24 and 2.3.1.
I had to rollback my parse-server version to 2.2.23 to keep working.

BTW, I'm using JS npm version 1.9.2

I open a new issue (https://github.com/ParsePlatform/Parse-SDK-JS/issues/396)


Tweaks needed for AWS usage

@tiny-dancer I'm finally getting my hands dirty with runiac, sorry it took me so long. Picked this up to build a POC today and noticed that out of the box, the environment variables you allow passing to the run container don't include known AWS environment variables supported by the AWS CLI and SDKs.
Obviously in most companies, making use of AWS IAM users for operations isn't a best practice and the preference falls to IAM roles, which is what I am trying to make use of.  Would you accept a PR for passing along these env vars and maybe some other AWS tweaks as I come upon them?

Hello hello! Glad to have you onboard, absolutely please do.
Current AWS usage (that I know of) leverages a third party secrets manager to set environment variables in entrypoint.sh, happy to review any enhancements you see in the native runiac set up.


fetch ParseInternalError from tresParse if possible

Looks good! Disabling error logging for union fields might hide error logging further down the line for the correct union but I guess that can be dealt with when it arises :)

The disabling of logging for union fields will hide downstream errors, but we cannot possibly guess which union field is the one we want. So the best bet is to just inform the user that the parsing of the union didn't match any of the fields that were provided


migrating an existent Moodle to this docker container

Hi, thank you for sharing your work.
I've seen this is a container that installs moodle at startup.
I have an existing moodle installation (apache-PHP-MariaDB) and want to migrate to docker.
I want to use your Nginx-PHP image with a MariaDB database. I can add a service in docker-compose.yml  for MariaDB that uses my migrated DB and mount var/lib/mysql as a volume, but I don't know how to run my actual 4.1 installation in your image.
sorry for borrowing, I'm a docker rookie. May you help me, please?
Thanks
Carlo

IMHO, migrating direct /var/lib/mysql files can be a little bit messy. Seems easier if you dump your current database and import in the new Dockerized one, or best if you export your moodle courses directly. Let me know which option do you prefer, and I will try to help you.

Hi @ccomincini,
Just wanted to let you know that I'm closing the GitHub issue we've been discussing, since we haven't received any additional data to move forward with a solution. If you have any updates or information to share in the future, feel free to reopen the issue.
Best regards


[BFCL] The handling of prompt formatting in GLM is incorrect.

Describe the issue
Hi, thanks for your excellent work.
I think there is a bug in the formatted prompt handling of GLM.
ID datapoint
https://github.com/zhangch-ss/gorilla/blob/main/berkeley-function-call-leaderboard/bfcl/model_handler/oss_model/glm.py
apply_chat_template
What is the issue
This is the result of apply_chat_template, and it seems that the tool descriptions are missing. Additionally, it appears that support for multiple roles is not yet implemented.
"[gMASK]<sop><|user|>\nI'm playing a dice game and want to calculate my chances. I roll the die 20 times, and I'm trying to figure out the probability of landing on a 6 exactly five times, considering each roll has a one in six chance of being a 6. Could you help me with that?<|assistant|>"
Proposed Changes
It seems that the apply_chat_template function needs to be modified to support the mentioned features. If possible, I would be happy to submit a PR to fix it.

Hi @zhangch-ss,
Thanks for the issue. We also noticed the abnormal behaviour of the GLM model, thus we haven't report its score on the leaderboard. (We can tell it's abnormal because it scores 0 on all the non-live categories (the same as BFCL V1) and it used to score quite a lot on those categories before the release of the live dataset). If you raise the PR, we are happy to review it.

Thanks for your reply, this issue may be the cause of the abnormal behavior of glm,
This is the evaluation result of non-live categories after fixed.
It looks normal, but GLM seems to be incapable of parallel function calling

I have submitted a PR.


Domain activation is Failed - [BRIEF DESCRIPTION]

App Id: d2qwqmz5kprk4w
Region: us-east-1
Step: Domain activation
Status: Failed

Note: Do not include information that is sensitive in nature such as your domain name, company etc.

Issue/question
I am trying to deploy my Angular frontend to a Route53 domain. In the past, i have used amplify app to do this but looks like i could not see the old amplify app, so had to create a new one. However, while deploying to custom domain - it is failed with an error message.
Error message: One or more of the CNAMEs you provided are already associated with a different resource.
How should i retrieve the old amplify app and disassociate it from this domain or allow my new amplify app to my domain -
https://codebysandeep.io
Error message
Error message: One or more of the CNAMEs you provided are already associated with a different resource.
Additional information
Please add any other relevant information. Please feel free to include screenshots.

Refer to our documentation to troubleshoot domain setup.
https://docs.aws.amazon.com/amplify/latest/userguide/custom-domain-troubleshoot-guide.html
https://docs.aws.amazon.com/amplify/latest/userguide/custom-domain-troubleshoot-guide.html#i-get-a-cnamealreadyexistsexception-error
Let us know if you're still facing issues.

Refer to our documentation to troubleshoot domain setup.
https://docs.aws.amazon.com/amplify/latest/userguide/custom-domain-troubleshoot-guide.html
https://docs.aws.amazon.com/amplify/latest/userguide/custom-domain-troubleshoot-guide.html#i-get-a-cnamealreadyexistsexception-error
Let us know if you're still facing issues.

@brnmye I did go through the documentation. However, it does not mention anything about lets say a past amplify app was using the same domain. However, it is deleted now so i am not able to disassociate this domain from old app.
Please suggest next steps

@brnmye I did go through the documentation. However, it does not mention anything about lets say a past amplify app was using the same domain. However, it is deleted now so i am not able to disassociate this domain from old app.
Please suggest next steps


Zigbee2MQTT Devices do not appear when shared with remote domoticz

Issue description
Im trying to share the devices between my domoticz instances (using Domoticz - Remote Server)
I have tested the sharing by using a dummy device, and that seems to work.
I don't know if sharing devices in this way is actualy suported, but i could not find it being described in the documentation, or an issue with this question.
Additional information
Zigbee2MQTT version: 1.7.1
Python version:  3.7.3
Domoticz version: 4.10717
Plugin version: 0.0.19

Try to ask this question on Domoticz forum, because there is nothing could be done from plugin side, it just integrates into existed Domoticz instance.

Thanks for the quick responce,
I have created a post on the Domoticz forum https://www.domoticz.com/forum/viewtopic.php?f=68&t=30301
I will close the issue.


Updating a DID fails when the anchor origin is down

Steps to reproduce:

Domain1, Domain2 and Domain3 are all following and witnessing each other
Create a DID on Domain3 (Domain1 and Domain2 witness the anchor)
Shut down Domain3
Update the created DID on Domain1

Results in the following error:
orb.domain1.com              |  [sidetree-core-writer] 2022/02/18 20:54:55 UTC - batch.(*Writer).cutAndProcess -> ERROR [did:orb] Error processing 17 batch operations: failed to create witness list: resolve witness: failed to resolve witness: failed to get key[https://orb.domain3.com] from host metadata cache: failed to get host-meta document via HTTP/HTTPS: failed to get a response from the host-meta endpoint: Get "https://orb.domain3.com/.well-known/host-meta.json": dial tcp: lookup orb.domain5.com on <IP_ADDRESS>:53: no such host
And the batch is never anchored.
The expectation is that, since Domain2 is still up then Domain2 can witness the update and the batch should be anchored.

VDR change to use different domain when anchor origin is down

https://github.com/hyperledger/aries-framework-go-ext/pull/280


feat(plugin-chart-echarts): subject add sort by metric for Pie Chart

After
https://user-images.githubusercontent.com/8277264/107389461-75c54780-6aff-11eb-8ca3-4fdd03837b37.mp4

@villebro @ktmud @rusackas

Since the default row limit is very large, I doubt this will change the accuracy of the final rendered pie chart for most users.


support the cortex-m7f

:pushpin: Commit b0d634c has been approved by japaric

@homunkulus r+

:hourglass: Testing commit b0d634c with merge b0d634c...

:broken_heart: Test failed - travis

@homunkulus r+

:pushpin: Commit bb31d8b has been approved by japaric

:hourglass: Testing commit bb31d8b with merge bb31d8b...

:sunny: Test successful - travis


fix: allow DefinePlugin shorthand property

closes #16764

Summary

🤖 Generated by Copilot at af7126c
The pull request enhances the DefinePlugin to support a new syntax for defining object properties. It also adds a test case to ensure the functionality works as expected.
Details

🤖 Generated by Copilot at af7126c

Allow DefinePlugin to handle shorthand property syntax by prepending the property name to the code string (link, link, link, link) in lib/DefinePlugin.js
Add a test case in test/configCases/plugins/define-plugin/index.js to verify the correct behavior of DefinePlugin with shorthand property syntax (link)

Thank you

Congrats @shamoilarsi on your first PR to webpack! 🎉 🚀

@TheLarkInn Thanks a lot 😄 looking forward to fixing others 🚀


[Feature Request] Variables for more redstone properties

A variable for redstone power was added in the v4.0.0 betas. I think it's a great addition and I would like to see more variables like this, such as a facing variable that is specific to redstone components, if a hopper is enabled or not, if a dropper/dispenser is triggered or not, etc. I saw that there was a target_block_props variable in the v4.0.0 betas, but it didn't do what I was looking for.

Found a solution to this. If anyone's looking for the same thing, you can use target_block_property:<property>:<method>, where <property> would be the desired property and <method> would be the type of return value.
For example,
{target_block_property:power:value} would display a value like the one shown in the F3 menu
{target_block_property:power:name} would display power
{target_block_property:power:type} would display Number


Make header component containers' styles configurable

In beta 6, header components' styles are absolute positioned and I hate the fact that title component has left/right offset so I make the style configurable to override the default style
Since we now have a way to set component styles, I also deprecated the titleStyle
Demo:
const MyHomeScreen = ({ navigation }) => (
  <MyNavScreen
    banner="Home Screen"
    navigation={navigation}
  />
);
MyHomeScreen.navigationOptions = {
  title: 'Welcome',
  header: () => ({
    componentStyle: {
      title: {
        backgroundColor: 'red',
        left: 0,
        right: 0,
      },
    },
  }),
};

const MyProfileScreen = ({ navigation }) => (
  <MyNavScreen
    banner={
      `${navigation.state.params.mode === 'edit' ? 'Now Editing ' : ''
      }${navigation.state.params.name}'s Profile`
    }
    navigation={navigation}
  />
);
MyProfileScreen.navigationOptions = {
  header: ({ state, setParams }) => ({
    title: `${state.params.name}'s Profile!`,
    // Render a button on the right side of the header.
    // When pressed switches the screen to edit mode.
    right: (
      <Button
        title={state.params.mode === 'edit' ? 'Done' : 'Edit'}
        onPress={() => setParams({ mode: state.params.mode === 'edit' ? '' : 'edit' })}
      />
    ),
    componentStyle: {
      title: {
        backgroundColor: 'red',
        left: 0,
        right: 0,
      },
      left: {
        backgroundColor: 'blue',
      },
      right: {
        backgroundColor: 'yellow',
      },
    },
  }),
};

const MyProfileScreen = ({ navigation }) => (
  <MyNavScreen
    banner={
      `${navigation.state.params.mode === 'edit' ? 'Now Editing ' : ''
      }${navigation.state.params.name}'s Profile`
    }
    navigation={navigation}
  />
);
MyProfileScreen.navigationOptions = {
  header: ({ state, setParams }) => ({
    title: `${state.params.name}'s Profile!`,
    // Render a button on the right side of the header.
    // When pressed switches the screen to edit mode.
    right: (
      <Button
        title={state.params.mode === 'edit' ? 'Done' : 'Edit'}
        onPress={() => setParams({ mode: state.params.mode === 'edit' ? '' : 'edit' })}
      />
    ),
    componentStyle: {
      title: {
        backgroundColor: 'red',
        left: 0,
        right: 0,
      },
      right: {
        backgroundColor: 'yellow',
      },
    },
  }),
};

What's the motivation? What kind of UI do you want to achieve? Setting background color for left and right components seem very specific.
There's titleStyle for customising the title's style.

@satya164
Actually, I have to remove the title component's, which is a custom view,  left and right offset in my current project and titleStyle is only applied when we set title in navigationOptions but not title in header

titleStyle is only applied when we set title in navigationOptions but not title in header

That looks like a bug.

That looks like a bug.

Oh I see. Anyway, I think it is more flexible if developers can set the components' styles.

I think it is more flexible if developers can set the components' styles.

You can set back buttons color with tintColor. I don't think people rarely need to set the background color. You can replace whole back button with your implementation if you want heavy customization.
Regarding right component, it's always provided by the user, so there's no need for having a config option for that.

I see your point. Will close PR and submit a new one for fixing the titleStyle not applying to custom title view.


Question: Derivative with respect to real space coordinate

Hi! I used the QDHT to calculate the convolution of two radially symmetric functions via multiplication in Fourier space and then transforming back. What I am now interested in is the derivative of the convolution result with respect to the radial variable. Math-wise it should be something like this I think:
$$ \frac{d}{dr}f(r) = \frac{d}{dr}H_0^{-1}(F(k)) = \frac{d}{dr} \int_0^\infty F(k) J_0(kr)k\ dk = - \int_0^\infty F(k) J_1(kr)k^2\ dk = -H_1^{-1}(kF(k))$$
Question: Is there a nice way to obtain the result using QDHT? So far I think no, as $H_0$ and $H_1$ use different discretizations of the real and reciproke space, but I'd be happy if there's a workaround.

Question: Is there a nice way to obtain the result using QDHT?

I can't think of a way to get this result from QDHT. My best idea would be to fit some interpolation like a spline to the values of f returned from the inverse transform and then use the derivative of that function. @chrisbrahms can you think of a better way?

Off the top of my head, I also don't think this works directly. Maybe you can get somewhere by expanding in Fourier-Bessel series and using the Hankel transform to turn it into a matrix or vector multiplication, similar to what you can for integrals (see the derivation in the docs). But that's just speculation, I haven't tried.

My best idea would be to fit some interpolation like a spline to the values of f returned from the inverse transform and then use the derivative of that function.

That's exactly what I ended up with and it should suffice for now. Thanks for your help!