globalcatalogv1.PricingGet: API is not returning the price of the plan

Describe the bug
The Price field of the Price structure is not being unmarshalled because there's a case mismatch between the annotation in the go code and the value returned in the json payload.  Looks like it's this code that's the problem, but since it's generated I'm assuming there's something else similar to the other PricingGet issue I opened last week.  Likely some entries here : https://github.ibm.com/cloud-api-docs/resource-catalog/blob/production/global-catalog.json#L397
The struct definition here is wrong ( compared with the plain REST payloads ) : https://github.com/IBM/platform-services-go-sdk/blob/main/globalcatalogv1/global_catalog_v1.go#L3685
// Price : Pricing-related information.
type Price struct {
	// Pricing tier.
	QuantityTier *int64 `json:"quantity_tier,omitempty"`

	// Price in the selected currency.
	Price *float64 `json:"Price,omitempty"` <<<<<<<<<<<<<< The json annotation is the wrong case
}

To Reproduce
You can use the application that I posted as part of https://github.com/IBM/platform-services-go-sdk/issues/247 to reproduce the problem.  What you will see is that when the price information is dumped there's no Price value ( ie. the dollar cost ) - only the quantity tier is reported.
For example, a partial output of one of the Kubernetes plans reports :
{
    "deployment_id": "public.containers.kubernetes.b1c.32x128:ca-tor28613",
    "deployment_location": "ca-tor",
    "type": "Paid",
    "origin": "pricing_catalog",
    "starting_price": {},
    "metrics": [
        {
            "part_ref": "",
            "metric_id": "D1SL6LL",
            "tier_model": "Step Tier",
            "charge_unit": "Instance-Hours",
            "charge_unit_name": "instance_hours",
            "charge_unit_quantity": 1,
            "resource_display_name": "",
            "charge_unit_display_name": "",
            "usage_cap_qty": 0,
            "display_cap": 0,
            "effective_from": "2023-04-01T00:00:00.000Z",
            "effective_until": "2023-04-30T23:59:59.999Z",
            "amounts": [
                {
                    "country": "USA",
                    "currency": "USD",
                    "prices": [
                        {
                            "quantity_tier": 150                 <<<<<<<<<<<<<< price is missing here
                        },
                        {
                            "quantity_tier": 290
                        },
                        {
                            "quantity_tier": 540
                        },
                        {
                            "quantity_tier": 999999999
                        }
                    ]
                },

but in the similar REST payload, the content looks like :
{
  "deployment_id": "public.containers.kubernetes.b1c.32x128:ca-tor28613",
  "deployment_location": "ca-tor",
  "deployment_region": "DEFAULT",
  "origin": "pricing_catalog",
  "type": "Paid",
  "i18n": {},
  "starting_price": {},
  "effective_from": "2023-04-01T00:00:00Z",
  "effective_until": "2023-04-30T23:59:59.999Z",
  "metrics": [
    {
      "part_ref": "",
      "metric_id": "D1SL6LL",
      "tier_model": "Step Tier",
      "resource_display_name": "",
      "charge_unit_display_name": "",
      "charge_unit_name": "instance_hours",
      "charge_unit": "Instance-Hours",
      "charge_unit_quantity": 1,
      "amounts": [
        {
          "country": "USA",
          "currency": "USD",
          "prices": [
            {
              "quantity_tier": 150,
              "price": 1.87  <<<<<<< expecting to get the price like this in the above output
            },
            {
              "quantity_tier": 290,
              "price": 1.78
            },

Must gather (please complete the following information):
SDK Version : 0.37.1
Go Version : go1.19.8
Name of service that you're trying to use : globalcatalogv1
Name of operation that you're trying to invoke :PricingGet

@dubee - here's another issue with the Pricing API - can you please have a look ?

@dubee I checked the global-catalog API definition and the "price" property is defined as "Price".  The name used in the API definition should match the field name that will appear in the JSON response returned by the server.
So, to fix this, we'd need to fix the API definition and then re-gen the SDK code.
Do we have an integration test for the affected operation(s) where we can test that this is working correctly once fixed?


Set rights for  maintenance dir

Resolves issue #220

Thanks for your pull request!
I'm closing this one as @TimGroenenberg already fixed the issue.


Missing /lib/index.js file on instalation

I was installing iv-analysis on a project and there's no lib folder with js files, is this intentional?

Please don't assign me to issues. I use assignment to know what I am working on.

Sorry, didn't know

Tentative fix: https://github.com/cheminfo/analysis/pull/11

Fixed in v0.1.1<EMAIL_ADDRESS>


Unsupport discord.py v1.7.x

Discord api removed v7, so discord.py v1.7.x can’t use.

There's not really any immediate reason to do this since the environments this would affect are broken regardless of whether jishaku claims it's compatible or not. A bump should probably be done at the same time as the shims being removed, and that would involve also reconsidering whether fork support is still worth it or not amongst other things. I have ideas for PaginatorInterface that might warrant the cleanup anyway, but I'm not particularly going to prioritize bumping the requirements until I hit something that justifies it, and at that point it would probably just be a straight bump to 2.1/2.2, whatever the latest is at the time.

But discord.ui.Modal is can use only discord.py v2, so i think you must stop support fork library.


Provide helper function ShouldStreamItem to encapsulate context cancellation check and limit check

duplicate of https://github.com/turbot/steampipe-plugin-sdk/issues/177


filer service exception is raised by using port 7333 download big file . The file in the filer service cannot be accessed

weed filer  -master=<IP_ADDRESS>:9333 -port=8888  -port.readonly=7333
8888 filer service exception is raised by using port 7333 download big file . The file in the filer service cannot be accessed.
weed version
version 30GB 3.05 acc318e12bdeca0dcf0f4fc601cc659f7831fa92 linux amd64

need a way to reproduce.

It is easy to reproduce. If you use the filer readonly port to download a 2G file, it will reproduce. There is no exception in the background log


Fix: User can now only delete/edit another user with same or lower role

To be fixed in https://github.com/nodes-vapor/admin-panel-provider/pull/64


Wanna transfer this to the SublimeLinter group?

We'd like to improve the compatibility of this plugin and usually it's easier if members of the SL group can just go and make a fix rather than having to go through a pull request.
So @roadhump, if you want to transfer this to me (@braver) I'll put it in the group and make sure you still have access.

@braver Thank you, it would be a pleasure for me, I did not use ST now.

@braver Also, will it be possible for you to take https://github.com/roadhump/SublimeLinter-contrib-eslint_d to SL group as well?


RELEASE: Remove requeue of dependent modules

This is a hot fix to avoid infinite queuing of modules for analysis.

OK, this will undo some of the GotoDef/FindReferences stuff in https://github.com/Microsoft/python-language-server/pull/110, but we'll try and find another approach later.


Adding md documentation (for static doc generation) to repo

@heathermiller Just curious, should we be trying to revive this?

Is this a website for scala/pickling? It would be really cool to have this available as the official docs. Otherwise we could use li haoyi's template!


Reduce duplication in UI components

There is a large amount or reused/duplicated DOM within RetroQuest's UI components. Examples include, but are not limited to:

RetroQuest logo and header
Page structure
(add more examples as they are discovered)

Refactoring duplicated content here will make the code more maintainable.

Since the front end was refactored to react, this is no longer an issue.


Help report Insta account: @thrift.save.rave

Hi please pleaseee help report this account, they scammed me of my money and has blocked me everywhere now, I'll really appreciate it thanks a lott!

This is not an issue

:)))

what happened?
On Mon, 22 Nov, 2021, 7:37 am ikamyx, @.***> wrote:

:)))
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/Khanejo/Instagram-mass-reporter/issues/26#issuecomment-975005938,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AVYWNOQQ5737UUKMLDR6H33UNGQX7ANCNFSM5GY2GYKQ
.


What kind of accuracy logic is used in this Reference Kit?

This Reference Kit does the following import..
from neural_compressor.experimental import Benchmark
then it runs the following code...
evaluator = Benchmark(config_path)
evaluator.model = int8_model
# create benchmark dataloader like examples/tensorflow/qat/benchmark.py
evaluator.b_dataloader = test_loader
evaluator('accuracy')

print("*"*50)
print("Evaluating the FP32 Model")
print("*"*50)
evaluator = Benchmark(config_path)
evaluator.model = model
# create benchmark dataloader like examples/tensorflow/qat/benchmark.py
evaluator.b_dataloader = test_loader
evaluator('accuracy')

What kind of accuracy logic is being run behind the scenes?

The accuracy metric is defined in yaml file: https://github.com/oneapi-src/visual-quality-inspection/blob/main/src/intel_neural_compressor/conf.yaml#L8

Sorry, but i still don't know the answer.
That line says it is optional but required if the user doesn't provide eval_func in neural_compressor.Quantization.
I didn't change anything in the code. What is the accuracy metric used by default in this reference kit?

https://github.com/oneapi-src/visual-quality-inspection/blob/main/src/intel_neural_compressor/conf.yaml#L10
accuracy:
metric:
topk: 1
Is this the answer that you need?


chore(master): release 1.2.0

:robot: I have created a release beep boop
1.2.0 (2023-02-27)
Features

broadcast live data to clients #48 (bd532a3)
Merge pull request #55 from NeilHanlon/work-screen_buttons (764c714)
show live temperature + electricals (5533ec0)
Work screen improvements and functionality implmementation (7291869)

Bug Fixes

screen disappears if no device found (88cf666)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/builder555/PineSAM/releases/tag/v1.2.0 :sunflower:


Add Artifact Repository #2

This PR picks up from the work that work that @ttrently started in PR #1453.
Requirements
This implementation requires some additional packages that have not been included in rez.vendor.

awscli
pymongo==4.6.2

These can be installed via python -m pip install PKG --target path\to\rez\Lib\site-packages.
Setup
For testing I setup Mongo and Mongo Express docker containers locally by running the following commands:

docker run --detach --name mongo_rez --network rez -p 27017:27017 mongo:7.0.5
docker run --detach --name mongo_rez_express --network rez -e ME_CONFIG_MONGODB_SERVER=mongo_rez -p 8081:8081 mongo-express:1.0.2-20

I ran the Mongo Express container so I could easily see the contents of the DB in the browser.
How To Use
In order to use you will need an existing S3 bucket and a MongoDB instance with a named database and a collection called "packages".
In your rezconfig.py you will need to set the following:
packages_path = [
    "mongodb@localhost:27017/db_name",
]

artifacts_path = [
    "s3@s3://bucket-1/packages",
]

default_cachable = True
package_cache_same_device = True
package_cache_async  = False

Please note that the above Mongo URI will not directly be usable by PyMongo in a Python Console.
Steps

Run rez build --install -p mongo@localhost:27017/db_name  --clean to build a package and put its definition in the MongoDB. TODO: Running this seems to upload to DB now but install_variant doesn't fully work yet.

Changes

Made package caching optionally asynchronous. TODO: Not sure why this choice was made yet.

FUTURE
The following changes are not handled by this PR, but should be kept in mind for the future.

Introduce new terminology for variants:

Download: Pull a variant payload from the Artifact Repository to disk somehow? TODO: Clarify this.
Install: Unpacks the payload if necessary (if it's an archive file format), and caches it using payload caching? TODO: Investigate this.

For rez-release do we need to make release_packages_path a list so we can deploy to potentially multiple package repositories at once?

TODO:

No Credential Provider class as described in https://gist.github.com/JeanChristopheMorinPerso/9a0705d1498378178b53061d90f3b2d4
need some help with modern practices for credentials management and what our workflow should be here.
Check if this packs the payload before uploading to the Artifact Repository (convert to .zip)?
Figure out how to handle the two new PyPi package requirements:

awscli
pymongo

Hopefully we don't have to add these to the rez/vendor folder, but maybe that's a good first thing to do?
Define rez release behavior. Does this push to both to package repository and artifact repository? What does this do if there are multiple of either of those?
Need to clarify where exactly ArtifactRepositories belong in the architecture of Rez. Do we need a ArtifactRepository for packages on a shared filesystem or do we only use ArtifactRepositories when they are off premise?
Add new tests.

Thought for potential backlog item: Can we use a different data validation library or perhaps updated our vendored schema package? The output you get out of it currently is borderline unreadable to a human. For example here's a snippet of a traceback I got while working on this PR:
  File "D:\Code\rez\venv\lib\site-packages\rez\vendor\schema\schema.py", line 235, in validate
    raise SchemaError([None] + x.autos, [e] + x.errors)
rez.vendor.schema.schema.SchemaError: Or(<class 'rez.utils.sourcecode.SourceCode'>, Schema({Optional(<class 'str'>): Or(Or(<class 'str'>, [<class 'str'>]), {Optional(<class 'str'>): <class 'object'>, 'command': Or(<class 'str'>, [<class 'str'>]), Optional('requires'): [Or(<class 'str'>, And(<class 'rez.util
s.formatting.PackageRequest'>, Use(<class 'str'>)))], Optional('run_on'): Or(<class 'str'>, [<class 'str'>]), Optional('on_variants'): Or(<class 'bool'>, {'type': 'requires', 'value': [Or(<class 'str'>, And(<class 'rez.utils.formatting.PackageRequest'>, Use(<class 'str'>)))]})})})) did not validate 'None'
'None' should be instance of {Optional(<class 'str'>): Or(Or(<class 'str'>, [<class 'str'>]), {Optional(<class 'str'>): <class 'object'>, 'command': Or(<class 'str'>, [<class 'str'>]), Optional('requires'): [Or(<class 'str'>, And(<class 'rez.utils.formatting.PackageRequest'>, Use(<class 'str'>)))], Optional
('run_on'): Or(<class 'str'>, [<class 'str'>]), Optional('on_variants'): Or(<class 'bool'>, {'type': 'requires', 'value': [Or(<class 'str'>, And(<class 'rez.utils.formatting.PackageRequest'>, Use(<class 'str'>)))]})})}

@BryceGattis I agree the errors are awful. I have started to look at replacing our schema stuff with something more modern. But it's a difficult task because the schemas leak into our public API is in some places, the rez internals (the core ones) are all very tightly coupled to schemas and it is also very performance sensitive. It is probably positive do swap our wcha library with something else without introducing breaking changes, but I'll be a tough task.


Ident renaming

#78 tracks one kind of schema alteration: altering attributes.
This issue is for the other part: renaming idents.

An ident rename is as simple as:
{:db/id oldid
  :db/ident :some/newident}

We need to watch for these during transactions, updating our in-memory mappings (e.g., schema names) accordingly. Note that one can rename an ident then install a new attribute with the new name — developer beware!


Not a valid SSR component

this is the error I'm getting:
Error: <LottiePlayer> is not a valid SSR component. You may need to review your build config to ensure that dependencies are compiled, rather than imported as pre-compiled module

Figured it out, lottie needed to go into devDependencies. That fixed it.


The service is started and registered successfully, but the etcd warn information is always reported

log info：
{"level":"warn","ts":"2022-03-24T14:22:02.645+0800","logger":"etcd-client","caller":"v3@v3.5.2/retry_interceptor.go:62","msg":"retrying of unary invoker failed","target":"etcd-endpoints://0xc00050a540/<IP_ADDRESS>:12379","attempt": 0,"error":"rpc error: code = DeadlineExceeded desc = latest balancer error: last connection error: connection error: desc = "transport: Error while dialing dial tcp: lookup etcd1: no such host""}
docker-compose.yaml：
etcd1:
image: quay.io/coreos/etcd
container_name: etcd1
command: etcd -name etcd1 -advertise-client-urls http://etcd1:2379 -listen-client-urls http://<IP_ADDRESS>:2379 -listen-peer-urls http://<IP_ADDRESS>:2380 -initial-cluster-token etcd-cluster -initial-cluster "etcd1=http://etcd1:2380,etcd2=http://etcd2:2380,etcd3=http://etcd3:2380" -initial-cluster-state new
ports:
- "12379:2379"
- "12380:2380"
expose:
- 12379
networks:
- backend
etcd2:
image: quay.io/coreos/etcd
container_name: etcd2
command: etcd -name etcd2 -advertise-client-urls http://etcd2:2379 -listen-client-urls http://<IP_ADDRESS>:2379 -listen-peer-urls http://<IP_ADDRESS>:2380 -initial-cluster-token etcd-cluster -initial-cluster "etcd1=http://etcd1:2380,etcd2=http://etcd2:2380,etcd3=http://etcd3:2380" -initial-cluster-state new
ports:
- "22379:2379"
- "22380:2380"
networks:
- backend
etcd3:
image: quay.io/coreos/etcd
container_name: etcd3
command: etcd -name etcd3 -advertise-client-urls http://etcd3:2379 -listen-client-urls http://<IP_ADDRESS>:2379 -listen-peer-urls http://<IP_ADDRESS>:2380 -initial-cluster-token etcd-cluster -initial-cluster "etcd1=http://etcd1:2380,etcd2=http://etcd2:2380,etcd3=http://etcd3:2380" -initial-cluster-state new
ports:
- "32379:2379"
- "32380:2380"
networks:
- backend

format your docker-compose.yml for readability pls

how you run your rpc service, is it on your local laptop? Are etcd1, etcd2, etcd3 reachable? Can you ping them? and also please unset http_proxy or HTTP_PROXY environment variables

fyi: https://etcd.io/docs/v3.5/faq/#what-is-the-difference-between-listen-clientpeer-urls-advertise-client-urls-or-initial-advertise-peer-urls


Introduce createFormatter Static Method for Formatter Logic

Introduce a new static method, createFormatter, which encapsulates the existing logic for creating a formatter based on locale, type, and pattern.
It helps adhere to the DRY principle.
Also add two missing @thows lines in PHPDoc comments.

@bizley Done

Thanks.


🐛 [firebase_messaging] failed-service-worker-registration, The script has an unsupported MIME type

I've deployed a new version of a flutter 3.3.2 web application.
Like the web application was started with a lower Flutter version and index.html and FlutterFire plugins registration has changed, I've created a new sample web flutter application, and have copied the new index.html:
index.html.txt
and have done all the steps related on https://firebase.google.com/docs/flutter/setup?platform=web.
All works well, but there is one customer than can't load the application. Appears this error:
[firebase_messaging/failed-service-worker-registration] Messaging: We are unable to register the default service worker. Failed to register a ServiceWorker for scope ('https://host/firebase-cloud-messaging-push-scope') with script ('https://host/firebase-messaging-sw.js'): The script has an unsupported MIME type ('text/html'). ., )
On the message error above, I've changed the real host name with the word host.
Nothing works, he already have pressed the refresh button, F5 and Ctrl+F5. Even I've included a page error with a button:
 IconButton(                              onPressed: () => window.location.reload(),                                 icon: const Icon(Icons.refresh))                           ],
He is using Chrome 105.0.5195.127

@dumabg
As the error says The script has an unsupported MIME type ('text/html'), indicating wrong MIME type of file in your server.  You may want to check the format / config of the said file on your local dev server and on release build if that helps ?

On previous FlutterFire versions, I need to create this file for configuring messaging, but now doesn't exist. I suppose that the browser is caching the file and the old index.html. I don't know.
The new build hasn't this file.
It seems a cache problem, but it isn't resolved deploying a new version nor Ctrl+F5. It seems that the browser doesn't invalidated the cache. But only in this customer, in others works well.

I am not sure if there's anything can be done from client (Flutterfire) side on it. I suggest you to reach out to firebase support for further resolution since this looks to be setup / config issue and that too happening in one customer's end.

I had a component that was using messaging 12. On my project, all other Firebase component are using the last version (core 1.23). I have changed that component and now messaging is in the last version (13.0.3).
After upgrade, I have another errors, only on Firefox and only if are new browsers (not acceded previously). If use incognito, also appears. Appears one of these errors:

[firebase_messaging/failed-service-worker-registration] Messaging: We are unable to register the default service worker. The operation is insecure. ., ).
In some the phrase "The operation is insecure" appears and in others no.
FirebaseError: Messaging: This browser doesn't support the API's required to use the Firebase SDK. (messaging/unsupported-browser).

The Firefox version is 105.0
On Chromium, continues with the MIME type error.

Reading again the documentation on https://firebase.google.com/docs/cloud-messaging/flutter/receive,
I created again firebase-messaging-sw.js, but where put navigator.serviceWorker.register('/firebase-messaging-sw.js');?
Now index.html is completely different.
I put in all these places:
 window.addEventListener('load', function(ev) {
      navigator.serviceWorker.register('/firebase-messaging-sw.js');   // HERE
      // Download main.dart.js
      _flutter.loader.loadEntrypoint({
      ...

 window.addEventListener('load', function(ev) {
      // Download main.dart.js
      _flutter.loader.loadEntrypoint({
        serviceWorker: {
          serviceWorkerVersion: serviceWorkerVersion,
        }
      }).then(function(engineInitializer) {
        navigator.serviceWorker.register('/firebase-messaging-sw.js');      // HERE
        return engineInitializer.initializeEngine();
      }).then(function(appRunner) {
        return appRunner.runApp();
      });
    });

 window.addEventListener('load', function(ev) {
      // Download main.dart.js
      _flutter.loader.loadEntrypoint({
        serviceWorker: {
          serviceWorkerVersion: serviceWorkerVersion,
        }
      }).then(function(engineInitializer) {
        return engineInitializer.initializeEngine();
      }).then(function(appRunner) {
        navigator.serviceWorker.register('/firebase-messaging-sw.js');   // HERE
        return appRunner.runApp();
      });
    });

But always apperas this error: navigator.serviceWorker is undefined

Check this similar issue and underlying comments and see if it helps.

I have restored the index.html that was created in Flutter 2. After that, all works again. The new index.html seems to have some problems.


Implement New UI Design

This branch is contain of new implement design.
Overall all page was available.
For checking, you should login first and then open page /realtime-logs-dummy.

The old page before still available in code, I just added new files.

@rohmad-st when can you continue working on this?


Switch Ubuntu instructions to just use the Debian instructions

The problem I'm trying to solve:
Since the snap is no longer recommended, it might make sense to simply combine the Debian and Ubuntu instructions, since Ubuntu is a Debian derivative anyway, it's already available in the repositories, and the instructions work predictably.
If I ever find a tool without a specific Ubuntu package, I just use the Debian ones.
How I imagine hub could expose this functionality:
ant@veil:~/Projects$ sudo apt install hub
[sudo] password for ant:
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
  xsel
The following NEW packages will be installed
  hub xsel

This would just be a readme update. Happy to open a PR if people think this is a good idea.

In trying to install this on Ubuntu 18.04.5 LTS the apt package was not found
sudo apt-get install hub
Reading package lists... Done
Building dependency tree
Reading state information... Done

No apt package "hub", but there is a snap with that name.
Try "snap install hub"

E: Unable to locate package hub

In trying to install this on Ubuntu 18.04.5 LTS the apt package was not found
sudo apt-get install hub
Reading package lists... Done
Building dependency tree
Reading state information... Done

No apt package "hub", but there is a snap with that name.
Try "snap install hub"

E: Unable to locate package hub

Yeah I wouldn't expect anyone to build packages for a two+ year old
unsupported distribution. I've tried it on the latest and I would expect it
to install on a more recent LTS.
I'll try on 20.04 LTS to verify when I get a chance.
On Fri, 15 Jan 2021 at 22:33, Joseph Swantek<EMAIL_ADDRESS>wrote:

In trying to install this on Ubuntu 18.04.5 LTS the apt package was not
found
sudo apt-get install hub
Reading package lists... Done
Building dependency tree
Reading state information... Done
No apt package "hub", but there is a snap with that name.
Try "snap install hub"
E: Unable to locate package hub
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/github/hub/issues/2695#issuecomment-761232524, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AABVORO6W2EO7U4SKFMNZC3S2C7FJANCNFSM4WCFJSQQ
.

--

ꜽ . antony jones . http://www.enzy.org

Yeah I wouldn't expect anyone to build packages for a two+ year old
unsupported distribution. I've tried it on the latest and I would expect it
to install on a more recent LTS.
I'll try on 20.04 LTS to verify when I get a chance.
On Fri, 15 Jan 2021 at 22:33, Joseph Swantek<EMAIL_ADDRESS>wrote:

In trying to install this on Ubuntu 18.04.5 LTS the apt package was not
found
sudo apt-get install hub
Reading package lists... Done
Building dependency tree
Reading state information... Done
No apt package "hub", but there is a snap with that name.
Try "snap install hub"
E: Unable to locate package hub
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/github/hub/issues/2695#issuecomment-761232524, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AABVORO6W2EO7U4SKFMNZC3S2C7FJANCNFSM4WCFJSQQ
.

--

ꜽ . antony jones . http://www.enzy.org

Since the snap is no longer recommended, it might make sense to simply combine the Debian and Ubuntu instructions, since Ubuntu is a Debian derivative anyway, it's already available in the repositories, and the instructions work predictably.

Sure! I'll accept whatever improvement to our installation instructions leads to a better/stabler experience for users.

Since the snap is no longer recommended, it might make sense to simply combine the Debian and Ubuntu instructions, since Ubuntu is a Debian derivative anyway, it's already available in the repositories, and the instructions work predictably.

Sure! I'll accept whatever improvement to our installation instructions leads to a better/stabler experience for users.

Opened a PR https://github.com/github/hub/pull/2697
I've retained the note about snap as a footnote to aid returning users, existing users, and pre-empt the "why not snap" question. Happy to remove it preferred.

Opened a PR https://github.com/github/hub/pull/2697
I've retained the note about snap as a footnote to aid returning users, existing users, and pre-empt the "why not snap" question. Happy to remove it preferred.


picard-tools: 2.23.4 -> 2.23.8

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/picard-tools/versions.
meta.description for picard-tools is: "Tools for high-throughput sequencing (HTS) data and formats such as SAM/BAM/CRAM and VCF"
meta.homepage for picard-tools is: "https://broadinstitute.github.io/picard/"
meta.changelog for picard-tools is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 2.23.8 with grep in /nix/store/lzq0k4hxcb35n9siqnlk68glfb56bxlk-picard-tools-2.23.8

directory tree listing: https://gist.github.com/a0a137810ceaf6016155fccf6fcfdb82

du listing: https://gist.github.com/fb52600eecc2b6dbc98b38ff93b2ec70

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
1 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
picard-tools

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/lzq0k4hxcb35n9siqnlk68glfb56bxlk-picard-tools-2.23.8 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A picard-tools https://github.com/r-ryantm/nixpkgs/archive/6391d3c1b501e063d2102b2a65cf12557d5e3251.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/lzq0k4hxcb35n9siqnlk68glfb56bxlk-picard-tools-2.23.8
ls -la /nix/store/lzq0k4hxcb35n9siqnlk68glfb56bxlk-picard-tools-2.23.8/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review 1

1 package built:

picard-tools

Maintainer pings
cc @jbedo for testing.

LGTM.

Result of nixpkgs-review pr 102707 run on x86_64-darwin 1

1 package built:

picard-tools


Update index.html

Angepasste Texte (Anwendungsfälle)
Checklist

[ ] Resolves #id
[ ] The code of conduct is respected
[ ] Added project
[ ] Added label "Review needed"
[ ] Assigned a reviewer

Reviewer

[ ] I've checked out the code and tested it myself.

Changes

List your changes here.

I have fixed minor text issues and the paragraphs. Also removed the flexbox styling of the solutions as the texts were getting too big for a column layout


[1.7.2rc2] ln_default_sync_initial_done not applicable to CL

this blocks the ssh terminal entering the menu so will remove the check for CL for now
did not try without any LN implementation set yet

might be related to: #2902


segmentation fault（core dumped）

when I run “”bin/rnn2fst -rnnlm examples/rnn2wfst.model -fst examples/rnn2wfst.k1+8.p1e-3.fst -discretize examples/rnn2wfst.1+8.kmeans -hcluster -prune 1e-3 -backoff 2”，it will show “segmentation fault（core dumped）“.
and in build_cluster_hierarchy.pl，function compute_word_probs("$f.membership",$WRD_TRACE, %w_probs); as $WRD_TRACE has no definition and the function did not compute normally,
anybody know how to use this tool?

when I run “”bin/rnn2fst -rnnlm examples/rnn2wfst.model -fst examples/rnn2wfst.k1+8.p1e-3.fst -discretize examples/rnn2wfst.1+8.kmeans -hcluster -prune 1e-3 -backoff 2”，
it will show “new cluster in 0th level
0th level : 1 clusters
new cluster in 1th level
new cluster in 1th level
1th level : 2 clusters
MIN BACKOFF -1 | ∅
H=0.42687 / N proc'd=0 / N added=0 (-nan %) / N bo=0 (-nan %) / 0/0 Nodes (-nan %)run_rnnlm2fst.sh: line 32: 29908 Segmentation fault      (core dumped) bin/rnn2fst -rnnlm ${model_checkpoint} -fst ${model_fst} -discretize ${model_kmeans} -hcluster -prune 1e-3 -backoff -1“
anybody know how to use this tool?
Thanks


fix: upload loading sign shows when creating new folder

I'm not sure we need to introduce another piece of state here. isCreating represents the open state of the input although we should rename it to be something more specific.

We are using the same query to upload both files & folders. We need 2 states, 1 to differentiate folder from file & the other to hold the state of input state, else the loading sign will be shown at 2 places when we upload a file.

I'll take a look at this, whenever there's a lot of useState it's usually a sign of something wrong


Bug: CSS initial not supported on IE11

According to https://developer.mozilla.org/en-US/docs/Web/CSS/initial, initial is not supported at all on IE
We have the issue on IE that the pagination text are always hidden and never shown because initial is not recognized.
https://github.com/carbon-design-system/carbon-components/blob/master/src/components/pagination/_pagination.scss
.bx--pagination__text {
    @include font-size('12');
    color: $text-02;
    display: none;

    @include breakpoint('530px') {
      display: initial;
    }
  }

Looks like it was "By design" for IE 11 to not support initial 😕
https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/9528179/#comment-0


feat(PageContent): set unique ids on nested headers

See https://github.com/BookStackApp/BookStack/issues/3058 for informations

Thank you for this @Julesdevops, and thank you very much for supplying a test with the PR!
All looked and seems to work great. Have merged to be part of the next patch release.

@ssddanbrown You're welcome. Thank you for your work on this great projet


refactor(esl-event-listener): change API of extended EventTargets

BREAKING CHANGE: beta ESLEventUtils.resize replaced with ESLResizeObserverTarget.for
BREAKING CHANGE: beta ESLEventUtils.decorate replaced with ESLDecoratedEventTarget.for

:tada: This PR is included in version 4.4.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Fix-Extra grey space in published mode Table Widget when columns are hidden

Description
Fixed extra grey space in published mode Table Widget when columns are hidden
Fixes #4832
Type of change

Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

Added cypress test to validate column titles are occupying full table space

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes

Test coverage results :test_tube:
:white_circle: Total coverage has not changed
// Code coverage diff between base branch:release and head branch: fix/table-hidden-column-empty-space

Status
File
% Stmts
% Branch
% Funcs
% Lines

:green_circle:
app/client/src/widgets/TableWidget/index.tsx
9.33 (0.02)
0 (0)
10.64 (0)
10 (0.03)

/ok-to-test sha=6f346b0

Verified working as expected

Rerunning flaky test fail


Performance issue after latest update

For some reason plot commands became really slow in IJulia after I updated Python and Julia. Any idea on what is causing the issue?
>>> import sys
>>> sys.version
'3.4.3 (default, Mar 25 2015, 17:13:50) \n[GCC 4.9.2 20150304 (prerelease)]'

julia> versioninfo()
Julia Version 0.4.0-dev+4059
Commit e0d95e9* (2015-03-29 15:28 UTC)
Platform Info:
  System: Linux (x86_64-unknown-linux-gnu)
  CPU: Intel(R) Core(TM) i7-3632QM CPU @ 2.20GHz
  WORD_SIZE: 64
  BLAS: libopenblas (USE64BITINT DYNAMIC_ARCH NO_AFFINITY Sandybridge)
  LAPACK: libopenblas
  LIBM: libopenlibm
  LLVM: libLLVM-3.3

julia> Pkg.status("PyPlot")
 - PyPlot                        1.5.1+             master

julia> Pkg.status("IJulia")
 - IJulia                        0.2.1+             master

I tried @time imshow(randn(400,400)) and it takes 0.06 seconds which is ok. The image however takes a while to show up in the notebook. The kernel is busy.

Can you try doing a Pkg.update()?  I had accidentally broken the numpy wrappers in PyCall, so it was making a very inefficient copy of the array as nested Python lists rather than using NumPy.

Hi Steven,
I did the update, but the problem persists.

@stevengj this is probably an issue of IJulia instead of PyCall/PyPlot, no?

@juliohm, that's true, but only if you didn't update PyCall/PyPlot when you updated IJulia.  Are you sure that isn't the case?

Hi Steven,
I only updated IJulia after noticing the issue with imshow().
Do you want me to try with specific versions?

@juliohm, you said that you had also updated Python?  What IPython version are you using?

IPython 3.0.0 (Jupyter)
This is the root of the issue?

Can you try it with IPython 2.x (but everything else the same) to see if the performance issue goes away?

I cannot guarantee I'll have time to downgrade, but will try.
Thanks.

Hi Steven, you don't have easy access to Jupyter?
-Júlio

The issue is gone.

Great!

Hi Steven, I am getting this issue again. In short, plots show swiftly when I work from terminal, in IJulia, for complicated plots the slowdown is such that it is practically unusable. I work in this environment:
  | | |_| | | | (_| |  |  Version 0.4.1 (2015-11-08 10:33 UTC)
 _/ |\__'_|_|_|\__'_|  |
|__/                   |  x86_64-apple-darwin15.0.0

julia> Pkg.status("IJulia")
 - IJulia                        1.1.8

julia> Pkg.status("PyPlot")
 - PyPlot                        2.1.1

julia> Pkg.status("PyCall")
 - PyCall                        1.2.0

You are using Jupyter notebook.

The version of the notebook server is 4.0.6-e7cffd3 and is running on:
Python 2.7.10 (default, Jul 13 2015, 12:05:58)
[GCC 4.2.1 Compatible Apple LLVM 6.1.0 (clang-602.0.53)]

Tried to change to python 3.5, did not help.
I would be glad for any help on this.

You haven't set PyPlot.svg(true), have you?

No, I haven't. Is there any way how to debug? I have today a bit of time so might try to do that.

You could try to figure out if the backend is different in the terminal vs. IJulia.   Or try the Agg backend in the terminal and check that writing to a .png file is fast.  (IJulia uses the Agg backend for inline plots, and sends them as PNG.)

Alright, it was probably my mistake. Because I don't know much matplotlib I was copypasting stuff and trying to get a decent image and I also copypasted
fig[:canvas][:draw]()

that causes the whole issue. Any reason why this exact line is causing so much trouble? Thanks anyway and sorry for bothering.

No idea why that would be a problem, other than potentially causing things to be rendered twice.


KAFKA-15031: Add plugin.discovery to Connect worker configuration (KIP-898)

This is the primary feature for KIP-898, which allows users to reconfigure the Connect worker among the different scanning modes. The different modes and their functionality and intended use are as described in https://cwiki.apache.org/confluence/display/KAFKA/KIP-898%3A+Modernize+Connect+plugin+discovery
In addition to the configuration defaulting to HYBRID_WARN for production use-cases, the default for the EmbeddedConnectCluster is set to HYBRID_FAIL. This has necessitated that all of the connect:runtime:main and connect:runtime:test plugins get valid manifest files so that they can be loaded. This includes the Mock, Schema, and Verifiable connectors that are being relocated in #13302, so these PRs will conflict.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

Here's an example error log output when in HYBRID_FAIL mode (I shortened the listing for brevity; the actual prints include every non-migrated plugin)
Plugins are missing ServiceLoader manifests, these plugins will not be visible with plugin.discovery=SERVICE_LOAD: [
classpath	org.apache.kafka.connect.converters.ByteArrayConverter	undefined
classpath	org.apache.kafka.connect.converters.DoubleConverter	undefined
classpath	org.apache.kafka.connect.converters.FloatConverter	undefined
classpath	org.apache.kafka.connect.converters.IntegerConverter	undefined
classpath	org.apache.kafka.connect.converters.LongConverter	undefined
classpath	org.apache.kafka.connect.converters.ShortConverter	undefined
classpath	org.apache.kafka.connect.integration.BlockingConnectorTest$BlockingConnector	0.0.0
classpath	org.apache.kafka.connect.integration.BlockingConnectorTest$BlockingSinkConnector	0.0.0
...
classpath	org.apache.kafka.connect.transforms.predicates.TopicNameMatches	undefined
]
	at app//org.apache.kafka.connect.runtime.isolation.Plugins.maybeReportHybridDiscoveryIssue(Plugins.java:131)
	at app//org.apache.kafka.connect.runtime.isolation.Plugins.initLoaders(Plugins.java:92)
	at app//org.apache.kafka.connect.runtime.isolation.Plugins.<init>(Plugins.java:74)
	at app//org.apache.kafka.connect.runtime.isolation.Plugins.<init>(Plugins.java:64)
	at app//org.apache.kafka.connect.cli.AbstractConnectCli.startConnect(AbstractConnectCli.java:121)
	at app//org.apache.kafka.connect.util.clusters.WorkerHandle.start(WorkerHandle.java:50)
	at app//org.apache.kafka.connect.util.clusters.EmbeddedConnectCluster.addWorker(EmbeddedConnectCluster.java:187)
	at app//org.apache.kafka.connect.util.clusters.EmbeddedConnectCluster.startConnect(EmbeddedConnectCluster.java:283)
	at app//org.apache.kafka.connect.util.clusters.EmbeddedConnectCluster.start(EmbeddedConnectCluster.java:148)
	...
	(test suite)

This is what appears if the manifests included in this PR are not present.
The same, but with HYBRID_WARN:
[2023-07-19 17:03:44,143] WARN Plugins are missing ServiceLoader manifests, these plugins will not be visible with plugin.discovery=SERVICE_LOAD: [
classpath	org.apache.kafka.connect.converters.ByteArrayConverter	undefined
...
classpath	org.apache.kafka.connect.transforms.predicates.TopicNameMatches	undefined
] (org.apache.kafka.connect.runtime.isolation.Plugins:128)

I did notice that if logging is OFF or ERROR for the runtime (such as in the mirror tests) then the warning doesn't print if the caller overrides the configuration. The failure does propagate, so they will certainly see that in HYBRID_FAIL.
I'm going to push the required manifests, so just delete/revert them if you'd like to see these errors on the classpath.

The question of plugins that are installed directly onto the classpath might be a bit tricky... let me know if I've missed something. My current understanding is that these plugins will continue to be available on the worker regardless of which discovery mode is used (with the possible exception of HYBRID_FAIL, if they prevent workers from starting up), but that they may not be visible in portions of the REST API (I'm thinking GET /connector-plugins, though there may be others).

This is incorrect, and I think i've contributed to the confusion, sorry. To be very explicit:

The plugin.discovery configuration treats classpath and plugin.path the same. If a non-migrated plugin is on the classpath, then it will appear in HYBRID_WARN warnings, HYBRID_FAIL exceptions, and won't be usable with SERVICE_LOAD. It will not appear in GET /connector-plugins and attempting to use it will cause ClassNotFound or similar exceptions to be thrown.
The connect-plugin-path script will only migrate plugins included in it's arguments, leaving classpath completely unchanged. The list command will not show classpath plugins. This means someone may have HYBRID_FAIL enabled, and the connect-plugin-path script will not solve it, such as in unit tests, when everything is on the classpath.
If someone adds non-migrated plugins to the classpath (such as in a production deployment), they will need to pay additional attention to those plugins. They can either move them to plugin.path, upgrade them, or use --plugin-location to specify each one manually.

The question of plugins that are installed directly onto the classpath might be a bit tricky... let me know if I've missed something. My current understanding is that these plugins will continue to be available on the worker regardless of which discovery mode is used (with the possible exception of HYBRID_FAIL, if they prevent workers from starting up), but that they may not be visible in portions of the REST API (I'm thinking GET /connector-plugins, though there may be others).

This is incorrect, and I think i've contributed to the confusion, sorry.

I apologize, you are correct, and I was the one who was confused. Because someone can still specify the classname directly, and that classname is loadable in the AppClassLoader, then the plugin will still be "usable", but aliases will be missing and it will be hidden from the REST API.
I don't think it's possible to make the classpath and plugins behave the consistently in this case. If SERVICE_LOAD doesn't discover the plugin, then it's indistinguishable from a non-plugin in the DelegatingClassLoader#loadClass. And we have to allow non-plugins to delegate upwards, because that's how every other class is loaded. We would make a situation where the runtime can't load a classpath plugin but the plugins can, which is a bit silly. Do you think this behavior is worth changing?
I've updated the documentation string (and site docs) to be intentionally vague and say "may not be usable" to cover both cases, let me know if you'd like to adjust that.
Also just small style choice: Do you think we should use all-caps or lowercase values for this configuration in docs?

LGTM assuming the two small remaining comments (tweaking language in Plugins::maybeReportHybridDiscoveryIssue and using lowercase values in docs for plugin.discovery.mode property) are addressed. Thanks Greg!

These have been addressed.

Ah, spoke too soon--it looks like the SynchronizationTest::testSimultaneousUpwardAndDownwardDelegating test case is consistently failing now. Can we look into that before merging?

The test was failing because the ServiceLoaderScanner called PluginClassLoader#loadClass on the JsonConverter during the Plugins initialization. This caused the PluginClassLoader to cache the class, preventing the test from causing an upward-delegation. I've swapped out the JsonConverter for an arbitrary non-plugin class that isn't loaded during initialization.

Flaky test failures appear unrelated, and the tests pass locally.


BUG: Unable to delete row from lil matrix after scalar multiplication.

BUG: Unable to delete row from lil matrix after scalar multiplication (closes #1427).

Looks good, +1.


Support Python 3

What does this PR do?
Adds support for Python3 for twemproxy
Motivation
Support Py3 for more things.
Review checklist

[ ] PR has a meaningful title or PR has the no-changelog label attached
[ ] Feature or bugfix has tests
[ ] Git history is clean
[ ] If PR impacts documentation, docs team has been notified or an issue has been opened on the documentation repo
[ ] If PR adds a configuration option, it has been added to the configuration file.

Additional Notes
Will refactor tests and add E2E in another PR.

Codecov Report

Merging #2817 into master will decrease coverage by 4.06%.
The diff coverage is 71.42%.

@@            Coverage Diff             @@
##           master    #2817      +/-   ##
==========================================
- Coverage   84.71%   80.64%   -4.07%
==========================================
  Files         662        4     -658
  Lines       37609      155   -37454
  Branches     4507       21    -4486
==========================================
- Hits        31860      125   -31735
+ Misses       4432       20    -4412
+ Partials     1317       10    -1307


Update Duo Web SDK JS code to version 2.6

Hey all!
We've updated our Web SDK JS code. We've also actually started tracking this code on Github as well: https://github.com/duosecurity/duo_web_sdk
The changes are backwards compatible too, so no worries about breaking changes. If there's further testing you'd like me to provide let me know!

Hello!
Thank you for the PR. You should however post the same PR to this project instead:
https://github.com/apereo/cas
cas-mfa here is no longer maintained...and I believe CAS (the repo above) already contains the change. Please verify.

Ahh, thanks for the heads up! We'll make PRs against https://github.com/apereo/cas in the future.


use seek_to='earliest' with external stream will core dump.

-- redpanda
rpk topic create test

-- proton
drop stream if exists test_external1;
create external stream if not exists test_external1(id int, value string) settings type = 'kafka', brokers = 'redpanda-1:9092', topic = 'test', data_format='JSONEachRow';

-- redpanda
rpk topic produce test
{"id":1,"value":"sometext"}
Produced to partition 0 at offset 2 with timestamp<PHONE_NUMBER>153.
{"id":2,"value":"aaaaa"}
Produced to partition 0 at offset 3 with timestamp<PHONE_NUMBER>203.
{"id":3,"value":"bbbbb"}
Produced to partition 0 at offset 4 with timestamp<PHONE_NUMBER>238.
{"id":4,"value":"ccccc"}
Produced to partition 0 at offset 5 with timestamp<PHONE_NUMBER>389.

-- proton
select * from test_external1 settings seek_to='earliest';
-- no results and Core Dump

2023.11.16 13:19:20.279404 [ 304985 ] {3feeacc9-6851-493d-bdba-4efae38d3895} <Fatal> : Logical error: 'Bad cast from type DB::ColumnVector<int> to DB::ColumnString'.
2023.11.16 13:19:20.280532 [ 305421 ] {} <Fatal> BaseDaemon: ########################################
2023.11.16 13:19:20.280962 [ 305421 ] {} <Fatal> BaseDaemon: (version 1.3.22, build id: 5613AA59E0EF211617341403B5ED5344D382662E) (from thread 304985) (query_id: 3feeacc9-6851-493d-bdba-4efae38d3895) (query: select * from test_external1 settings seek_to='earliest';) Received signal Aborted (6)
2023.11.16 13:19:20.281244 [ 305421 ] {} <Fatal> BaseDaemon:
2023.11.16 13:19:20.281797 [ 305421 ] {} <Fatal> BaseDaemon: Stack trace: 0x7f7ff838300b 0x7f7ff8362859 0x34153d9b 0x34153f1d 0x34154153 0x1e8e2e2c 0x489adb2a 0x595471da 0x59546b02 0x59546aad 0x596615b6 0x59551c8d 0x595460b1 0x4a81bfe9 0x4a81b4f3 0x4a925b37 0x4a9255cf 0x4a8ae5a3 0x4a8af046 0x4a8b4f7f 0x4a8b4e15 0x4a8b4df9 0x4a8b4d3d 0x4a8b4ad4 0x4a8b4775 0x4a8b4755 0x4a8b4735 0x4a8b4703 0x34213343 0x34208ab5 0x34424115 0x34436225 0x344360d5 0x34435f9d 0x34435656 0x7f7ff854a609 0x7f7ff845f133
2023.11.16 13:19:20.282169 [ 305421 ] {} <Fatal> BaseDaemon: 4. raise @ 0x7f7ff838300b in ?
2023.11.16 13:19:20.282451 [ 305421 ] {} <Fatal> BaseDaemon: 5. abort @ 0x7f7ff8362859 in ?
2023.11.16 13:19:20.386376 [ 305421 ] {} <Fatal> BaseDaemon: 6. /home/timeplus/lijianan/ssd/gitdownload/proton_/src/Common/Exception.cpp:0: DB::abortOnFailedAssertion(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char>> const&) @ 0x34153d9b in /home/timeplus/lijianan/ssd/gitdownload/proton_/build/programs/proton
2023.11.16 13:19:20.454533 [ 305421 ] {} <Fatal> BaseDaemon: 7. /home/timeplus/lijianan/ssd/gitdownload/proton_/src/Common/Exception.cpp:63: DB::handle_error_code(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char>> const&, int, bool, std::__1::vector<void*, std::__1::allocator<void*>> const&) @ 0x34153f1d in /home/timeplus/lijianan/ssd/gitdownload/proton_/build/programs/proton
2023.11.16 13:19:20.521590 [ 305421 ] {} <Fatal> BaseDaemon: 8. /home/timeplus/lijianan/ssd/gitdownload/proton_/src/Common/Exception.cpp:70: DB::Exception::Exception(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char>> const&, int, bool) @ 0x34154153 in /home/timeplus/lijianan/ssd/gitdownload/proton_/build/programs/proton
2023.11.16 13:19:21.000602 [ 304943 ] {} <Information> AsynchronousMetrics: MemoryTracking: was 1.84 GiB, peak 1.84 GiB, free memory in arenas 0.00 B, will set to 1.90 GiB (RSS), difference: 65.02 MiB
2023.11.16 13:19:21.170451 [ 305421 ] {} <Fatal> BaseDaemon: 9. /home/timeplus/lijianan/ssd/gitdownload/proton_/src/Common/assert_cast.h:47: DB::ColumnString const& assert_cast<DB::ColumnString const&, DB::IColumn const&>(DB::IColumn const&) @ 0x1e8e2e2c in /home/timeplus/lijianan/ssd/gitdownload/proton_/build/programs/proton
2023.11.16 13:19:21.266746 [ 305421 ] {} <Fatal> BaseDaemon: 10. /home/timeplus/lijianan/ssd/gitdownload/proton_/src/Columns/ColumnString.cpp:118: DB::ColumnString::insertRangeFrom(DB::IColumn const&, unsigned long, unsigned long) @ 0x489adb2a in /home/timeplus/lijianan/ssd/gitdownload/proton_/build/programs/proton
2023.11.16 13:19:21.452815 [ 305421 ] {} <Fatal> BaseDaemon: 11. /home/timeplus/lijianan/ssd/gitdownload/proton_/src/Storages/ExternalStream/Kafka/KafkaSource.cpp:194: DB::KafkaSource::parseFormat(rd_kafka_message_s const*) @ 0x595471da in /home/timeplus/lijianan/ssd/gitdownload/proton_/build/programs/proton
2023.11.16 13:19:21.606242 [ 305421 ] {} <Fatal> BaseDaemon: 12. /home/timeplus/lijianan/ssd/gitdownload/proton_/src/Storages/ExternalStream/Kafka/KafkaSource.cpp:125: DB::KafkaSource::doParseMessage(rd_kafka_message_s const*, unsigned long) @ 0x59546b02 in /home/timeplus/lijianan/ssd/gitdownload/proton_/build/programs/proton
2023.11.16 13:19:21.760038 [ 305421 ] {} <Fatal> BaseDaemon: 13. /home/timeplus/lijianan/ssd/gitdownload/proton_/src/Storages/ExternalStream/Kafka/KafkaSource.cpp:120: DB::KafkaSource::parseMessage(void*, unsigned long, void*) @ 0x59546aad in /home/timeplus/lijianan/ssd/gitdownload/proton_/build/programs/proton
2023.11.16 13:19:21.883039 [ 305421 ] {} <Fatal> BaseDaemon: 14. /home/timeplus/lijianan/ssd/gitdownload/proton_/src/KafkaLog/KafkaWALSimpleConsumer.cpp:450: klog::KafkaWALSimpleConsumer::consume(void (*)(void*, unsigned long, void*), void*, unsigned int, int, klog::KafkaWALContext const&) const @ 0x596615b6 in /home/timeplus/lijianan/ssd/gitdownload/proton_/build/programs/proton
2023.11.16 13:19:22.000479 [ 304943 ] {} <Information> AsynchronousMetrics: MemoryTracking: was 1.90 GiB, peak 1.90 GiB, free memory in arenas 0.00 B, will set to 2.04 GiB (RSS), difference: 144.41 MiB
2023.11.16 13:19:22.000738 [ 304943 ] {} <Debug> MemoryTracker: Current memory usage (total): 2.04 GiB.
2023.11.16 13:19:22.021055 [ 305421 ] {} <Fatal> BaseDaemon: 15. /home/timeplus/lijianan/ssd/gitdownload/proton_/src/Storages/ExternalStream/Kafka/KafkaSource.cpp:103: DB::KafkaSource::readAndProcess() @ 0x59551c8d in /home/timeplus/lijianan/ssd/gitdownload/proton_/build/programs/proton
2023.11.16 13:19:22.162947 [ 305421 ] {} <Fatal> BaseDaemon: 16. /home/timeplus/lijianan/ssd/gitdownload/proton_/src/Storages/ExternalStream/Kafka/KafkaSource.cpp:81: DB::KafkaSource::generate() @ 0x595460b1 in /home/timeplus/lijianan/ssd/gitdownload/proton_/build/programs/proton
2023.11.16 13:19:22.243379 [ 305421 ] {} <Fatal> BaseDaemon: 17. /home/timeplus/lijianan/ssd/gitdownload/proton_/src/Processors/ISource.cpp:138: DB::ISource::tryGenerate() @ 0x4a81bfe9 in /home/timeplus/lijianan/ssd/gitdownload/proton_/build/programs/proton
2023.11.16 13:19:22.326628 [ 305421 ] {} <Fatal> BaseDaemon: 18. /home/timeplus/lijianan/ssd/gitdownload/proton_/src/Processors/ISource.cpp:103: DB::ISource::work() @ 0x4a81b4f3 in /home/timeplus/lijianan/ssd/gitdownload/proton_/build/programs/proton
2023.11.16 13:19:22.391552 [ 305421 ] {} <Fatal> BaseDaemon: 19. /home/timeplus/lijianan/ssd/gitdownload/proton_/src/Processors/Executors/ExecutionThreadContext.cpp:46: DB::executeJob(DB::ExecutingGraph::Node*, DB::ReadProgressCallback*) @ 0x4a925b37 in /home/timeplus/lijianan/ssd/gitdownload/proton_/build/programs/proton
2023.11.16 13:19:22.458116 [ 305421 ] {} <Fatal> BaseDaemon: 20. /home/timeplus/lijianan/ssd/gitdownload/proton_/src/Processors/Executors/ExecutionThreadContext.cpp:84: DB::ExecutionThreadContext::executeTask() @ 0x4a9255cf in /home/timeplus/lijianan/ssd/gitdownload/proton_/build/programs/proton
2023.11.16 13:19:22.560971 [ 305421 ] {} <Fatal> BaseDaemon: 21. /home/timeplus/lijianan/ssd/gitdownload/proton_/src/Processors/Executors/PipelineExecutor.cpp:271: DB::PipelineExecutor::executeStepImpl(unsigned long, std::__1::atomic<bool>*) @ 0x4a8ae5a3 in /home/timeplus/lijianan/ssd/gitdownload/proton_/build/programs/proton
2023.11.16 13:19:22.660475 [ 305421 ] {} <Fatal> BaseDaemon: 22. /home/timeplus/lijianan/ssd/gitdownload/proton_/src/Processors/Executors/PipelineExecutor.cpp:236: DB::PipelineExecutor::executeSingleThread(unsigned long) @ 0x4a8af046 in /home/timeplus/lijianan/ssd/gitdownload/proton_/build/programs/proton
2023.11.16 13:19:22.761690 [ 305421 ] {} <Fatal> BaseDaemon: 23. /home/timeplus/lijianan/ssd/gitdownload/proton_/src/Processors/Executors/PipelineExecutor.cpp:373: DB::PipelineExecutor::executeImpl(unsigned long, DB::ExecuteMode)::$_0::operator()() const @ 0x4a8b4f7f in /home/timeplus/lijianan/ssd/gitdownload/proton_/build/programs/proton
2023.11.16 13:19:22.866410 [ 305421 ] {} <Fatal> BaseDaemon: 24. /home/timeplus/lijianan/ssd/gitdownload/proton_/contrib/llvm-project/libcxx/include/__functional/invoke.h:394: decltype(std::declval<DB::PipelineExecutor::executeImpl(unsigned long, DB::ExecuteMode)::$_0&>()()) std::__1::__invoke[abi:v15000]<DB::PipelineExecutor::executeImpl(unsigned long, DB::ExecuteMode)::$_0&>(DB::PipelineExecutor::executeImpl(unsigned long, DB::ExecuteMode)::$_0&) @ 0x4a8b4e15 in /home/timeplus/lijianan/ssd/gitdownload/proton_/build/programs/proton
2023.11.16 13:19:22.976268 [ 305421 ] {} <Fatal> BaseDaemon: 25. /home/timeplus/lijianan/ssd/gitdownload/proton_/contrib/llvm-project/libcxx/include/tuple:1789: decltype(auto) std::__1::__apply_tuple_impl[abi:v15000]<DB::PipelineExecutor::executeImpl(unsigned long, DB::ExecuteMode)::$_0&, std::__1::tuple<>&>(DB::PipelineExecutor::executeImpl(unsigned long, DB::ExecuteMode)::$_0&, std::__1::tuple<>&, std::__1::__tuple_indices<>) @ 0x4a8b4df9 in /home/timeplus/lijianan/ssd/gitdownload/proton_/build/programs/proton
2023.11.16 13:19:23.078951 [ 305421 ] {} <Fatal> BaseDaemon: 26. /home/timeplus/lijianan/ssd/gitdownload/proton_/contrib/llvm-project/libcxx/include/tuple:1798: decltype(auto) std::__1::apply[abi:v15000]<DB::PipelineExecutor::executeImpl(unsigned long, DB::ExecuteMode)::$_0&, std::__1::tuple<>&>(DB::PipelineExecutor::executeImpl(unsigned long, DB::ExecuteMode)::$_0&, std::__1::tuple<>&) @ 0x4a8b4d3d in /home/timeplus/lijianan/ssd/gitdownload/proton_/build/programs/proton
2023.11.16 13:19:23.176044 [ 305421 ] {} <Fatal> BaseDaemon: 27. /home/timeplus/lijianan/ssd/gitdownload/proton_/src/Common/ThreadPool.h:202: ThreadFromGlobalPool::ThreadFromGlobalPool<DB::PipelineExecutor::executeImpl(unsigned long, DB::ExecuteMode)::$_0>(DB::PipelineExecutor::executeImpl(unsigned long, DB::ExecuteMode)::$_0&&)::'lambda'()::operator()() @ 0x4a8b4ad4 in /home/timeplus/lijianan/ssd/gitdownload/proton_/build/programs/proton
2023.11.16 13:19:23.278742 [ 305421 ] {} <Fatal> BaseDaemon: 28. /home/timeplus/lijianan/ssd/gitdownload/proton_/contrib/llvm-project/libcxx/include/__functional/invoke.h:394: decltype(std::declval<DB::PipelineExecutor::executeImpl(unsigned long, DB::ExecuteMode)::$_0>()()) std::__1::__invoke[abi:v15000]<ThreadFromGlobalPool::ThreadFromGlobalPool<DB::PipelineExecutor::executeImpl(unsigned long, DB::ExecuteMode)::$_0>(DB::PipelineExecutor::executeImpl(unsigned long, DB::ExecuteMode)::$_0&&)::'lambda'()&>(DB::PipelineExecutor::executeImpl(unsigned long, DB::ExecuteMode)::$_0&&) @ 0x4a8b4775 in /home/timeplus/lijianan/ssd/gitdownload/proton_/build/programs/proton
2023.11.16 13:19:23.381950 [ 305421 ] {} <Fatal> BaseDaemon: 29. /home/timeplus/lijianan/ssd/gitdownload/proton_/contrib/llvm-project/libcxx/include/__functional/invoke.h:480: void std::__1::__invoke_void_return_wrapper<void, true>::__call<ThreadFromGlobalPool::ThreadFromGlobalPool<DB::PipelineExecutor::executeImpl(unsigned long, DB::ExecuteMode)::$_0>(DB::PipelineExecutor::executeImpl(unsigned long, DB::ExecuteMode)::$_0&&)::'lambda'()&>(ThreadFromGlobalPool::ThreadFromGlobalPool<DB::PipelineExecutor::executeImpl(unsigned long, DB::ExecuteMode)::$_0>(DB::PipelineExecutor::executeImpl(unsigned long, DB::ExecuteMode)::$_0&&)::'lambda'()&) @ 0x4a8b4755 in /home/timeplus/lijianan/ssd/gitdownload/proton_/build/programs/proton
2023.11.16 13:19:23.452575 [ 304754 ] {} <Debug> DNSResolver: Updating DNS cache
2023.11.16 13:19:23.452707 [ 304754 ] {} <Debug> DNSResolver: Updated DNS cache
2023.11.16 13:19:23.484039 [ 305421 ] {} <Fatal> BaseDaemon: 30. /home/timeplus/lijianan/ssd/gitdownload/proton_/contrib/llvm-project/libcxx/include/__functional/function.h:235: std::__1::__function::__default_alloc_func<ThreadFromGlobalPool::ThreadFromGlobalPool<DB::PipelineExecutor::executeImpl(unsigned long, DB::ExecuteMode)::$_0>(DB::PipelineExecutor::executeImpl(unsigned long, DB::ExecuteMode)::$_0&&)::'lambda'(), void ()>::operator()[abi:v15000]() @ 0x4a8b4735 in /home/timeplus/lijianan/ssd/gitdownload/proton_/build/programs/proton
2023.11.16 13:19:23.588186 [ 305421 ] {} <Fatal> BaseDaemon: 31. /home/timeplus/lijianan/ssd/gitdownload/proton_/contrib/llvm-project/libcxx/include/__functional/function.h:717: void std::__1::__function::__policy_invoker<void ()>::__call_impl<std::__1::__function::__default_alloc_func<ThreadFromGlobalPool::ThreadFromGlobalPool<DB::PipelineExecutor::executeImpl(unsigned long, DB::ExecuteMode)::$_0>(DB::PipelineExecutor::executeImpl(unsigned long, DB::ExecuteMode)::$_0&&)::'lambda'(), void ()>>(std::__1::__function::__policy_storage const*) @ 0x4a8b4703 in /home/timeplus/lijianan/ssd/gitdownload/proton_/build/programs/proton
2023.11.16 13:19:23.631865 [ 305421 ] {} <Fatal> BaseDaemon: 32. /home/timeplus/lijianan/ssd/gitdownload/proton_/contrib/llvm-project/libcxx/include/__functional/function.h:848: std::__1::__function::__policy_func<void ()>::operator()[abi:v15000]() const @ 0x34213343 in /home/timeplus/lijianan/ssd/gitdownload/proton_/build/programs/proton
2023.11.16 13:19:23.677863 [ 305421 ] {} <Fatal> BaseDaemon: 33. /home/timeplus/lijianan/ssd/gitdownload/proton_/contrib/llvm-project/libcxx/include/__functional/function.h:1187: std::__1::function<void ()>::operator()() const @ 0x34208ab5 in /home/timeplus/lijianan/ssd/gitdownload/proton_/build/programs/proton
2023.11.16 13:19:23.727970 [ 305421 ] {} <Fatal> BaseDaemon: 34. /home/timeplus/lijianan/ssd/gitdownload/proton_/src/Common/ThreadPool.cpp:295: ThreadPoolImpl<std::__1::thread>::worker(std::__1::__list_iterator<std::__1::thread, void*>) @ 0x34424115 in /home/timeplus/lijianan/ssd/gitdownload/proton_/build/programs/proton
2023.11.16 13:19:23.781663 [ 305421 ] {} <Fatal> BaseDaemon: 35. /home/timeplus/lijianan/ssd/gitdownload/proton_/src/Common/ThreadPool.cpp:140: void ThreadPoolImpl<std::__1::thread>::scheduleImpl<void>(std::__1::function<void ()>, long, std::__1::optional<unsigned long>, bool)::'lambda0'()::operator()() const @ 0x34436225 in /home/timeplus/lijianan/ssd/gitdownload/proton_/build/programs/proton
2023.11.16 13:19:23.839696 [ 305421 ] {} <Fatal> BaseDaemon: 36. /home/timeplus/lijianan/ssd/gitdownload/proton_/contrib/llvm-project/libcxx/include/__functional/invoke.h:394: decltype(std::declval<void>()()) std::__1::__invoke[abi:v15000]<void ThreadPoolImpl<std::__1::thread>::scheduleImpl<void>(std::__1::function<void ()>, long, std::__1::optional<unsigned long>, bool)::'lambda0'()>(void&&) @ 0x344360d5 in /home/timeplus/lijianan/ssd/gitdownload/proton_/build/programs/proton
2023.11.16 13:19:23.900407 [ 305421 ] {} <Fatal> BaseDaemon: 37. /home/timeplus/lijianan/ssd/gitdownload/proton_/contrib/llvm-project/libcxx/include/thread:285: void std::__1::__thread_execute[abi:v15000]<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct>>, void ThreadPoolImpl<std::__1::thread>::scheduleImpl<void>(std::__1::function<void ()>, long, std::__1::optional<unsigned long>, bool)::'lambda0'()>(std::__1::tuple<void, void ThreadPoolImpl<std::__1::thread>::scheduleImpl<void>(std::__1::function<void ()>, long, std::__1::optional<unsigned long>, bool)::'lambda0'()>&, std::__1::__tuple_indices<>) @ 0x34435f9d in /home/timeplus/lijianan/ssd/gitdownload/proton_/build/programs/proton
2023.11.16 13:19:23.954731 [ 305421 ] {} <Fatal> BaseDaemon: 38. /home/timeplus/lijianan/ssd/gitdownload/proton_/contrib/llvm-project/libcxx/include/thread:295: void* std::__1::__thread_proxy[abi:v15000]<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct>>, void ThreadPoolImpl<std::__1::thread>::scheduleImpl<void>(std::__1::function<void ()>, long, std::__1::optional<unsigned long>, bool)::'lambda0'()>>(void*) @ 0x34435656 in /home/timeplus/lijianan/ssd/gitdownload/proton_/build/programs/proton
2023.11.16 13:19:23.954906 [ 305421 ] {} <Fatal> BaseDaemon: 39. ? @ 0x7f7ff854a609 in ?
2023.11.16 13:19:23.954971 [ 305421 ] {} <Fatal> BaseDaemon: 40. clone @ 0x7f7ff845f133 in ?
2023.11.16 13:19:23.955027 [ 305421 ] {} <Fatal> BaseDaemon: Integrity check of the executable skipped because the reference checksum could not be read.
2023.11.16 13:19:27.000342 [ 304943 ] {} <Information> AsynchronousMetrics: MemoryTracking: was 2.14 GiB, peak 2.14 GiB, free memory in arenas 0.00 B, will set to 2.06 GiB (RSS), difference: -80.25 MiB

It's an issue with JSONEachRow (maybe with other formats too). Using the raw format seek_to works fine.


library is using a deprecated batch endpoint

The libary currently has www.googleapis.com/batch hardcoded as the endpoint for batch API requests unless caller manually sets batch_uri. See:
https://github.com/google/google-api-python-client/blob/master/googleapiclient/http.py#L1089
per Google Developers blog post this universal endpoint is being turned down in favor of per-API endpoints.
library needs to:

ensure all members of the batch are homogenous (same API) and throw an error if they're not.
utilize the batchPath from the individual API rather than the generic one, this would be something like:

service._rootDesc['rootUrl'] + service._rootDesc['batchPath']

Turns out this library is doing the right thing, but only if you construct the BatchHTTPRequest using service.new_batch_http_request. This method is documented in the docs here.
I've sent a PR to add a helpful warning if you construct BatchHTTPRequest manually and specify the legacy URI. This is the best compromise I can see that doesn't break the library's interface.

The docs also need updating, they're still importing the old camel case call:
https://developers.google.com/api-client-library/python/guide/batch

Yeah but it's not using it. Easy to fix.


Console command via web interface

I want to use console command via web interface because i dont have acces to cli using my android tablet & other mobile device, there are exists PHP for Android ( http://php-for-android.googlecode.com ) however seems no longer maintained.
Since many important action can only be performed using cli such as migration, i want yii to add this feature, maybe in we can add the feature to the Gii interface.

I plan creating an extension providing it in a browser.
Will be here: https://github.com/samdark/yii2-webshell

also related #6904


[backport] Fix missing module declaration

Backport of #6662

[automatic post] Jenkins, test this please.

Jenkins CI test (for commit 11948d5ab48183000412765c9ac5a4c382f116a6, target branch v5) succeeded!

LGTM!


Dotnet471

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

@sugol - Thanks for the submission.  How is this different than #28 which was merged yesterday?


Fix assetUrl and json files with webpack 4

Webpack 4 started handling parsing of JSON files automatically and abstracted away the "type" of file. We can restore the webpack 3 behavior by including some loader config to just set the type of json files, which will allow json files to work inside of assetUrl again.
More context: https://github.com/webpack/webpack/issues/6586#issuecomment-368677035

!merge


Adding auth-file: "/var/lib/ntfy/user.db" auth-default-access: "read-write" in docker instance problems.

Hi,
On a docker instance If we add
auth-file: "/var/lib/ntfy/user.db"
auth-default-access: "read-write"
to the server.yml file  The docker instance fails to restart. and when these files are removed it works perfectly fine.

The problem seems to be the
auth-file: "/var/lib/ntfy/user.db"
If I leave the second one the docker container starts. But can't get the auth part to work ^^

It might be easier to solve this on Discord. But it seems like you're not correctly mounting the /var/lib/ntfy directory inside the Docker container. Or you might be mounting it but the user that is running the container may not have access to that directory. I'd need to know more about your setup

Its a simple docker instance spinned up via docker-compose as fund here https://docs.ntfy.sh/install/#docker

As suggested by @wunter8 on discord.
When using Docker,  it's easier to use environment variables to configure everything instead of server.yml. Here's an example docker-compose.yml file with some good default settings.
Working docker-compose config.
version: '3'
services:
  ntfy:
    image: binwiederhier/ntfy
    restart: unless-stopped
    environment:
      NTFY_BASE_URL: <base_url>
      NTFY_AUTH_FILE: /etc/ntfy/auth.db
      NTFY_AUTH_DEFAULT_ACCESS: read-write
      NTFY_BEHIND_PROXY: true
      NTFY_ATTACHMENT_CACHE_DIR: /etc/ntfy/attachments
      NTFY_UPSTREAM_BASE_URL: https://ntfy.sh
      NTFY_ENABLE_LOGIN: true
      NTFY_WEB_PUSH_PUBLIC_KEY: <public_key>
      NTFY_WEB_PUSH_PRIVATE_KEY: <private_key>
      NTFY_WEB_PUSH_FILE: /etc/ntfy/webpush.db
      NTFY_WEB_PUSH_EMAIL_ADDRESS: <email>
    volumes:
      - ./:/etc/ntfy
    ports:
      - 8093:80
    command: serve

All credits to @wunter8 for this solution.


Added libs to classpaths

I added the libraries to the classpath to enable codacy

Minor issue as reported by codacy: a repeated semicolon on an import. Could you fix that for the next commit?


Make envoy.now.sh/std pattern deno.land/std compatible

<EMAIL_ADDRESS>works but
<EMAIL_ADDRESS>does not.
So this import map will work:
{
  "imports": {
    "https://deno.land/": "https://envoy.now.sh/"
  }
}

/x/std works but  it's not a good idea

I really don't see why it would be a bad idea. every registry has it's own route.
Also this project is not supposed to be a actual registry to use in production. I made this as an POC and to experiment with serverless caching proxies before we add this feature to nest.land, I was just pushing the boundary and seeing how many type of registries and what sizes it can handle (yes, importing large file fails).
sorry but I'd discourage the use this as a mirror for std (it's not. It's just a caching proxy). if you want an actual mirror for std you can take a look at nest.land/std


Only matched is fired, why?

Not sure i am doing this right.
enquire.register("screen and (max-width: 767px)", {
    match : function() {
        var feed = new Instafeed({
            clientId: '237094fcb1b84784b49e93a52f30dc6d',
            accessToken: '3230782367.1677ed0.eb1d8459f00840beb6db38b73eb4b25e',
            get: 'user',
            userId:<PHONE_NUMBER>,
            resolution: 'standard_resolution',
            limit: '6'
        });
        feed.run();
    },
    unmatch : function() {
        var feed = new Instafeed({
            clientId: '237094fcb1b84784b49e93a52f30dc6d',
            accessToken: '3230782367.1677ed0.eb1d8459f00840beb6db38b73eb4b25e',
            get: 'user',
            userId:<PHONE_NUMBER>,
            resolution: 'standard_resolution',
            limit: '8'
        });
        feed.run();
    }
});`

This only gives me the matched version ie, the mobile one, my page is blank on desktop until it hits 767px width.

Yes, that's the intended behaviour. The library is meant for progressive enhancement - unmatch only fires, if the query has been previously matched (it's meant for undoing anything you did in match, not to be the else case).
If you want to run code when it doesn't match, you can register a new handler and either:

negate your media query with the not keyword
write a mutually exclusive media query like screen and (min-width: 767px) (though i can't remember if min-width is inclusive, please adjust accordingly)


How to run this project

First of all thanks for this cool project i was trying to run this but was unable to, not from a java background would be a great help if you can provide a code sample. I tried to run the example.java file as basic javac command but it threw some errors

Thank you for using my project!
To run Example.java file, please open project with an IDE (like Intellij) with java 1.8 or higher and uncomment one of these line.

line 102: it will generate 100 lessons of puzzle 16x16 and save to file at path ./example-result/sudoku16x16/Gen.txt
line 103: it will generate 7x7 puzzle and print the puzzle and solved puzzle to the terminal.
line 104: it will solve the input puzzle 7x7 and print the result to the terminal.

To use code in your project, please copy folder vn/com/dangnguyendota to your project src folder and import following the tutorial in the Readme file.


Fix json comparison using Irmin.Type.equal

Fixes #587

I am not sure why the windows CI is unhappy (it seems to be stuck while synchronising pinned packages?), so merging.


Address front end vulnerabilities

Address node.js vulnerabilities in the latest Twistlock scan.

Closed in #105


the bridge cannot confirm the receival of the sent DFI

Dear Dr. Cagara, I came across the same issue today on 8th, Sep. 2022 like others that the UI of the bridge cannot confirm the receival of my sent 1284 DFI. The following is my TxID. Please help solving the problem, it is a little bit terrifying. The most important thing is how to get my DFI back into my Metamask wallet. Thank you so much in advance:
https://defiscan.live/transactions/9044b34f65e9d743d3e1079f8234eef5b71816deeddffee8904b05476abad9b1
PS: I have used this wonderful bridge not a few times, but it is the first time today I am stuck in this issue.

I tried to recover the transaction, but failed too

I am looking into it now, but can you please adding your metamask address into the second field in the recovery?
Sent from my iPhone
On 8 Sep 2022, at 1:08 pm, js-1105 @.***> wrote:

I tried to recover the transaction, but failed too
[截圖 2022-09-08 上午11 05 55]https://user-images.githubusercontent.com/101442789/189025157-e3e15245-02e0-4f9c-9340-2e442ad6aae3.png
—
Reply to this email directly, view it on GitHubhttps://github.com/muirglacier/bridge-ui/issues/36#issuecomment-1240162348, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AQVPOW7I3QEOBZ56QQWACLTV5FKBFANCNFSM6AAAAAAQHHUIPQ.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

How much I thank you for your email. I didn’t add my metamask address because there is no mention of this in the explanation.
Now the issue is solved. Your message is very much appreciated!
One suggestion: Maybe the explanation shall be more clear, and for the second row ,the entering of your address' shall be revised to that of the receiving address, i.e. the metamask or BSC address.  The present one with ERC20 could be misleading.
Thanks again!
Best wishes,
Johannes
PS. How shall I close the case in Github?
muirglacier<EMAIL_ADDRESS>於 2022年9月8日 上午11:35 寫道：
I am looking into it now, but can you please adding your metamask address into the second field in the recovery?
Sent from my iPhone
On 8 Sep 2022, at 1:08 pm, js-1105 @.***> wrote:

I tried to recover the transaction, but failed too
[截圖 2022-09-08 上午11 05 55]https://user-images.githubusercontent.com/101442789/189025157-e3e15245-02e0-4f9c-9340-2e442ad6aae3.png
—
Reply to this email directly, view it on GitHubhttps://github.com/muirglacier/bridge-ui/issues/36#issuecomment-1240162348, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AQVPOW7I3QEOBZ56QQWACLTV5FKBFANCNFSM6AAAAAAQHHUIPQ.
You are receiving this because you are subscribed to this thread.Message ID: @.***>
—
Reply to this email directly, view it on GitHubhttps://github.com/muirglacier/bridge-ui/issues/36#issuecomment-1240176277, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AYF6JZJ5BT7263VYJXW7FPTV5FNHLANCNFSM6AAAAAAQHHUIPQ.
You are receiving this because you authored the thread.Message ID: @.***>

Hey Johannes,
Thanks for the feedback, I didn’t see how confusing the text was! I will change it today! Thank you so much for the hint
Sent from my iPhone
On 9 Sep 2022, at 1:25 pm, js-1105 @.***> wrote:

Closed #36https://github.com/muirglacier/bridge-ui/issues/36 as completed.
—
Reply to this email directly, view it on GitHubhttps://github.com/muirglacier/bridge-ui/issues/36#event-7352938920, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AQVPOW2P53227URA4O3LZL3V5KU3BANCNFSM6AAAAAAQHHUIPQ.
 You guys are an excellent team, bringing so much conveniences and new use cases for the community


with the current cluster-template only master shows up

when #96 #98 will get merged you will notice that only the k8s master gets created, the workers do not for some reason.
we use DeploymentMachine for that, and I remember it worked a week ago, so probably something got lost along the way

I see it too. #98 is merged in, and #96, I just cheated by setting the PACKET_API_KEY to base64 encoded, so it all worked.
The master Machine came up, but nothing for the workers based on MachineDeployment.
Nothing in the packet manager logs either, which means it is not even calling them.

I think maybe I found your problem. PR coming soon

No, no PR needed. The default for WORKER_MACHINE_COUNT is 0. If you set it to something else, then it works. You can do it as an env var or as --worker-machine-count when calling clusterctl.
I will update the docs.


Readme content of Azure Core Http is unclear

1
Section Link

Suggestion: Remove "," after "e.g"
2
Section Link

Comment: Correct it as "impersonation"

For contributing section, we should re-direct to the the guide in the root like we do in the other Track 2 packages

Fixed. The comments in node-sample.ts was updated earlier and doesn't have the typo.


Is it possible to add an attribute to the root element?

I want to generate following xml:
<?xml version="1.0" encoding="UTF-8" ?>
<paymentService version="1">
  <body merchantId="1000011011">
    <transaction refno="941521">
      <request>
        <amount>100</amount>
        <currency>CHF</currency>
        <uppTransactionId>800247117123456789</uppTransactionId>
      </request>
    </transaction>
  </body>
</paymentService>

Source: https://www.datatrans.ch/showcase/settlement/xml-settlement-request
How can I add the version attribute to the root element "paymentService"?
I use this php code to generate the xml:
$xmlService = new XmlService();

return $xmlService->write(
            'paymentService',
            [
                'name' => 'body',
                'attributes' => [
                    'merchantId' => '123',
                ],
                'value' => [
                    'name' => 'transaction',
                    'attributes' => [
                        'refno' => '123',
                    ],
                    'value' => ['request' => [
                        'amount' => '132',
                        'currency' => 'CHF',
                    ]],
                ],
            ]
        );

I would guess
$xmlService = new XmlService();

return $xmlService->write([
            'name' => 'paymentService',
            'attributes' => [
                'version' => '123',
            ],
            'value' => [
                'name' => 'body',
                'attributes' => [
                    'merchantId' => '123',
                ],
                'value' => [
                    'name' => 'transaction',
                    'attributes' => [
                        'refno' => '123',
                    ],
                    'value' => ['request' => [
                        'amount' => '132',
                        'currency' => 'CHF',
                    ]],
                ],
            ]
        ]);

IMO, the scalar typehint is wrong in the write method.
opened a PR to fix that: https://github.com/fruux/sabre-xml/pull/118

I agree that adding attributes to the root element is a bit awkward, but I don't think the typehint should be changed to support this syntax. I wanted to have a nice symmetry between reading and writing, and this resulted in that syntax.
If you want to add an attribute to the root element, you have a few options. The obvious one is to not use the write() method but just call getWriter() and do what you need there. If you look at the implementation of the write() method, it also just calls getWriter().
Here's another way around that. Again not super intuitive but it works just fine:
$xmlService = new Service();
echo $xmlService->write(
  'root',
  function($writer) {
    $writer->writeAttribute('foo','bar');
    $writer->write('Your element array goes here');
  }
);


[docs][joy] Provide better documentation on overwriting substyles

Duplicates

[X] I have searched the existing issues

Related page
n/a
Kind of issue
Missing information
Issue description
The theme providers a variable ownerState to change the styling of a component based on its current state. As such, when a list item button was selected, I expected this to work:
JoyListItemButton: {
  styleOverrides: {
    root: ({ ownerState }: { ownerState: ListItemButtonOwnerState }) => ({
      borderRadius: 8,
      gap: 12,
      '--ListItemDecorator-size': '1rem',
      ...(ownerState.selected && {
        '--Icon-color': 'var(--joy-palette-primary-main)',
        backgroundColor: 'rgba(var(--joy-palette-primary-mainChannel) / .15)',
        fontWeight: 400
      }),
    })
  }
},

But it doesn't. The background color and font weight only gets applies when !important is added behind it (which isn't ideal anyways) because these styles are directly applied to .MuiListItemButton-root instead of .MuiListItemButton-root.Mui-selected and changing the --Icon-color for the selected state is completely impossible this way.
Instead, these customization have to be applied as follows for them to properly work:
JoyListItemButton: {
  styleOverrides: {
    root: {
      borderRadius: 8,
      gap: 12,
      '--ListItemDecorator-size': '1rem',
      '&.Mui-selected': {
        backgroundColor: 'rgba(var(--joy-palette-primary-mainChannel) / .15)',
        fontWeight: 400,
        '& .MuiListItemDecorator-root': {
          // As far as I can tell, even setting --Icon-color here has not the desired effect
          color: 'var(--joy-palette-primary-plainColor)',
        }
      }
    }
  }
},

If there is a better way for this, I'd love to hear it.
Regardless, my primary concern is that this entire thing isn't documented anywhere. As far as I can tell,  the docs only ever mention ownerState to say "hey, this exists" and never actually talk about what it is. I learned this was a thing only from a random example on the docs that used it and I still don't really know what is all included in there, nor how it exactly behaves (because from the example, I'd assumed that overwriting .Mui-selected was a thing, but it clearly isn't that simple).
It feels like extendTheme() is severly under-documented. Like the ´ownerStateAPI within it, as far as I can tellextendTheme` and its functionalities are nowhere properly documented for developers.
Context 🔦
Other examples of this are the various hooks in MUI, like useColorScheme.
Why is useMediaQuery the only hook that has an actual proper documentation page including a description of its API?

Thanks for opening this issue up! I agree with the sentiment ⎯ there is "assumed" knowledge in all product docs that we don't entirely introduce to readers upfront as well and clearly as we should, and then we end up using them in demo examples and it just ends up looking like extra stuff that I'm not sure why it's there, scaring those who don't have prior context/experience. Talking from a development sort of beginner mindset, I have felt the same with literally the ownerState thing and what it meant/does while trying to make sense of the source file for a Joy UI component.
cc @samuelsycamore big opportunity here. 😬
cc @zanivan to keep you in the loop.


Jkralik/add ping propagation

@jeffwelder-ellenbytech I have updated the code as we wanted to merge it. Additionally, I will add some tests there.

Codecov Report
Attention: 53 lines in your changes are missing coverage. Please review.

 Consider uploading reports for the commit e3ad79e to get more accurate results

Files
Patch %
Lines

options/commonOptions.go
0.00%
26 Missing :warning:

udp/client/conn.go
63.33%
9 Missing and 2 partials :warning:

tcp/client/conn.go
70.83%
6 Missing and 1 partial :warning:

tcp/client/session.go
14.28%
4 Missing and 2 partials :warning:

udp/client.go
57.14%
2 Missing and 1 partial :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #511      +/-   ##
==========================================
- Coverage   73.60%   73.32%   -0.29%
==========================================
  Files          71       71
  Lines        5729     5836     +107
==========================================
+ Hits         4217     4279      +62
- Misses       1122     1162      +40
- Partials      390      395       +5

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

@jkralik Great, I pulled the latest commit into my project to test, and it works as expected. :)


0.6 Mac OS X. debug_path in Render Viewport node should be system agnostic

Not sure if it is used other than for debugging, but it contained a Windows path so it produced error on Mac (and probably Linux).
main_window.gd
func render_shader_to_viewport(shader, textures, render_size, method, args):
	if debug_path != null and debug_path != "":
		var f = File.new()
		f.open(debug_path+str(debug_file_index)+".shader", File.WRITE)
		f.store_string(shader)
		f.close()
		debug_file_index += 1

Yes this is a debug feature. I will replace it with a debug node (that shows the generated shader for its input).


Production install of Conda on Cheyenne

@kmpaul, @davidedelvento, I managed to get a Conda module installation (using HPCinstall) working on Cheyenne. I am using Miniconda instead of the full-fledged Anaconda due to this hashing issue https://github.com/NCAR/HPCinstall/issues/90.
Anyways, I did sanity testing. Everything seems to be working properly.
Is this something that the Pangeo project users could be benefit from in a long term (having a system wide module instead of each user having to install Conda themselves)?

This is great!  What we need to try is this:
Have a non-admin user try something as simple as “conda install ...”
without activating any environment. (In other words, just the default conda
environment.) They should get a permission error (or errors).
Then, have that same non-admin user create an environment and try
installing new packages in their environment.
Then, another user should try “conda env list”. They should not see the
other user’s environments.
If that works, then we have a working / safe system conda install.
Anderson, if you don’t have time to do this, let me know how to load your
new module and I’ll try testing.
Kevin
On Wed, Dec 6, 2017 at 1:52 PM Anderson Banihirwe<EMAIL_ADDRESS>wrote:

@kmpaul https://github.com/kmpaul, @davidedelvento
https://github.com/davidedelvento, I managed to get a Conda module
installation (using HPCinstall) working on Cheyenne. I am using Miniconda
instead of the full-fledged Anaconda due to this hashing issue
NCAR/HPCinstall#90 https://github.com/NCAR/HPCinstall/issues/90.
Anyways, I did sanity testing. Everything seems to be working properly.
Is this something that the Pangeo project users could be benefit from in a
long term (having a system wide module instead of each user installing
Conda themselves)?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/andersy005/conda-deploy-cheyenne/issues/1, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AK4fg7lxkFujLmzJsTTsFBAhS6B8rS2bks5s9v6IgaJpZM4Q4kFk
.

--
Kevin Paul, PhD
Project Scientist, Head of I/O & Workflow Applications (IOWA)
The National Center for Atmospheric Research
Computational and Information Systems Laboratory
1850 Table Mesa Dr
Boulder, CO 80305
Phone:<PHONE_NUMBER>
Office:  ML460B

@kmpaul,
To load this module:
$ ml use /glade/scratch/abanihi/ch/test_installs/modulefiles/idep/
$ ml conda

I have addressed the first issue of changing conda's root environment  permission to read only by chmod'ing /glade/scratch/abanihi/ch/test_installs/conda/4.3.30/miniconda/conda-meta/histroy to 444

abanihi@cheyenne5: ~ $ conda info
Current conda install:

               platform : linux-64
          conda version : 4.3.30
       conda is private : False
      conda-env version : 4.3.30
    conda-build version : not installed
         python version : 3.6.3.final.0
       requests version : 2.18.4
       root environment : /glade/scratch/abanihi/ch/test_installs/conda/4.3.30/miniconda  (read only)
    default environment : /glade/scratch/abanihi/ch/test_installs/conda/4.3.30/miniconda
       envs directories : /glade/u/home/abanihi/.conda/envs
                          /glade/scratch/abanihi/ch/test_installs/conda/4.3.30/miniconda/envs
          package cache : /glade/scratch/abanihi/ch/test_installs/conda/4.3.30/miniconda/pkgs
                          /glade/u/home/abanihi/.conda/pkgs
           channel URLs : https://conda.anaconda.org/ioam/linux-64
                          https://conda.anaconda.org/ioam/noarch
                          https://conda.anaconda.org/bokeh/linux-64
                          https://conda.anaconda.org/bokeh/noarch
                          https://conda.anaconda.org/conda-forge/linux-64
                          https://conda.anaconda.org/conda-forge/noarch
                          https://repo.continuum.io/pkgs/main/linux-64
                          https://repo.continuum.io/pkgs/main/noarch
                          https://repo.continuum.io/pkgs/free/linux-64
                          https://repo.continuum.io/pkgs/free/noarch
                          https://repo.continuum.io/pkgs/r/linux-64
                          https://repo.continuum.io/pkgs/r/noarch
                          https://repo.continuum.io/pkgs/pro/linux-64
                          https://repo.continuum.io/pkgs/pro/noarch
            config file : /glade/u/home/abanihi/.condarc
             netrc file : None
           offline mode : False
             user-agent : conda/4.3.30 requests/2.18.4 CPython/3.6.3 Linux/3.12.62-60.64.8-default SUSE Linux Enterprise Server /12 glibc/2.19
                UID:GID : 29557:1000

When I try installing some package in the root environment, I get:
abanihi@cheyenne5: ~ $ conda install numpy
Fetching package metadata .................
Solving package specifications: .

Package plan for installation in environment /glade/scratch/abanihi/ch/test_installs/conda/4.3.30/miniconda:

The following NEW packages will be INSTALLED:

    blas:        1.1-openblas                  conda-forge
    libgfortran: 3.0.0-1
    numpy:       1.13.3-py36_blas_openblas_201 conda-forge [blas_openblas]
    openblas:    0.2.20-6                      conda-forge

The following packages will be SUPERSEDED by a higher-priority channel:

    conda:       4.3.30-py36h5d9f9f4_0                     --> 4.3.29-py36_0 conda-forge
    conda-env:   2.6.0-h36134e3_1                          --> 2.6.0-0       conda-forge

Proceed ([y]/n)? y

CondaIOError: Missing write permissions in: /glade/scratch/abanihi/ch/test_installs/conda/4.3.30/miniconda
#
# You don't appear to have the necessary permissions to install packages
# into the install area '/glade/scratch/abanihi/ch/test_installs/conda/4.3.30/miniconda'.
# However you can clone this environment into your home directory and
# then make changes to it.
# This may be done using the command:
#
# $ conda create -n my_root --clone="/glade/scratch/abanihi/ch/test_installs/conda/4.3.30/miniconda"

For the second issue where another user should try “conda env list” and not see the other user’s environments, I don't have a solution yet. Let me know if you know/find any.

Please do some test for the first issue and let me know if it works as expected.

@kmpaul, for the second issue: I think that conda is actually taking care of that under the hood.  Conda, by default, creates its environments under $HOME/.conda/envs. Because $HOME is unique for every user, we might have a solution to that issue as well. This is just my speculation, and it happens to be easily testable.
I have some test environments under my home directory:
abanihi@cheyenne5: ~ $ conda env list
# conda environments:
#
my_root               *  /glade/u/home/abanihi/.conda/envs/my_root
tensorflow-gpu           /glade/u/home/abanihi/.conda/envs/tensorflow-gpu
root                     /glade/scratch/abanihi/ch/test_installs/conda/4.3.30/miniconda

Let me know what you get when you try conda env list on your side.

Anderson!  You're not supposed to be this productive!  :-)
Well, this is fantastic!  I'm going to try to check it out myself.

@kmpaul, have you had any chance to check it out? Does it work as expected?

I haven't, yet.  I will try it tomorrow, though.  I've been pretty busy
with other things.
On Mon, Dec 18, 2017 at 4:07 PM, Anderson Banihirwe <
<EMAIL_ADDRESS>wrote:

@kmpaul https://github.com/kmpaul, have you had any chance to check it
out? Does it work as expected?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/andersy005/conda-deploy-cheyenne/issues/1#issuecomment-352586846,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AK4fg7C1QmVM_t0oy3NEeheBK1IsUeqLks5tBvA4gaJpZM4Q4kFk
.

--
Kevin Paul, PhD
Project Scientist, Head of I/O & Workflow Applications (IOWA)
The National Center for Atmospheric Research
Computational and Information Systems Laboratory
1850 Table Mesa Dr
Boulder, CO 80305
Phone:<PHONE_NUMBER>
Office:  ML460B

I understand. Let me know how it goes when you get a chance to check it out.

I just tried this out.  It appears to work very well.  Thanks for doing this!

Anytime, @kmpaul. I am glad that I can contribute.


A lot of links are really slow.

Hey there,
I've got a site with a lot of alternate links (5 languages in 31 countries). But Helmet is at that point extremely slow. I've wrote now the hacky way and render the meta data for this site only on server but I hope you've got a better solution.

Do you have a sample project that we can investigate?


Move null-check out of Validator constructor

add getOrDefault method

I gave #370 a shot.  I even added the getOrDefault method I envisioned before.

Is this getOrDefault necessary when you already added the overload? I think the way you did it before actually makes more sense, you don't want a default value in case validation fails?

It will only use the default value if all validation checks pass and it is still null.  The reason I like this is because it is type safe.  Instead of giving a String version of the value you want, you give it the actual type of the param.   But yeah its not super necessary, Its just how I figured it would work before so decided to add it.  I can remove it

Thanks @SmithKevin, looks good. Will mere once Travis is done.

This has been released as part of 2.3.0 now: https://javalin.io/news/2018/10/06/javalin-2.3.0-released.html