Firebird database views are not visible in version 7.2.5

System information:

Operating system (distribution) and version: Windows 10
DBeaver version: 7.2.5

Database name and version: Firebird
In version 7.2.5 database views could not be found.

Thanks for bug report! fix it soon

Fixed

#10411 created
verified

Fixed

I have tried 7.3.0 from https://dbeaver.io/files/ea/  just now and views in Firebird are still not shown.  I see them as regular tables.

@teklstudio what firebird version do you use?

@teklstudio what firebird version do you use?
@uslss Firebird version 2.5.5

@teklstudio cannot reproduce it

Is there something in the logs?

@uslss where can I send you my database?

@uslss maybe helps, that I have view which consist from union of two selects

@teklstudio you can send the database to<EMAIL_ADDRESS>Thanks in advance

@teklstudio thanks for the help with the investigation of the issue.
The new issue is created #10492
Close this issue as resolved.

@uslss  thank you. it will  be in early access  7.3.2 I expect

@uslss , I have downloaded EA version 7.3.2 and issue is not resolved...

@uslss , I have downloaded EA version 7.3.2 and issue is not resolved...

@uslss , I have downloaded EA version 7.3.2 and issue is not resolved...

@uslss , I have downloaded EA version 7.3.2 and issue is not resolved...


feat(container): default container resource requirements (#1082)

Backport
This will backport the following commits from k8s-24/main to k8s-23/main:

feat(container): default container resource requirements (#1082)

Questions ?
Please refer to the Backport tool documentation

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 1101

Questions ?
Please refer to the Backport tool documentation


Create an API Query Queue

It seems that, depending on how reliable the ADN API is, a browser can get stuck in a loop and hammer an API with multiple calls for the same data. Case in point is a recent observation of the browser requesting the posts/global/stream endpoint 6 times in 10 seconds, and ADN has an average turnaround time of 5.4 seconds for this particular query (for people in Japan).
A query queue would reduce and perhaps prevent this from happening.
Essentially the system would need to fire off a scheduled request as it does now, but the request would be thrown into an array and executed only when there were no preceding items in the queue. Duplicate requests would be ignored completely.

This isn't going to be done as the amount of work necessary to make this happen is just excessive. The time would be better spent on other projects.


Refactor the page of CS1929

This pull request potentially fixes #38646
Although the author does not specify what exactly is incorrect in the page, there are couple of things that are to be corrected and that this PR addresses:

The summary text is incorrect, as the CS1929 error is totally different than Instance argument: cannot convert from 'typeA' to 'typeB'
Two ways of dealing with the error is written in one point, while still making it a one point list.
This was separated into two points.
The original code does not generate CS1928, at least not on my end, perhaps there are some specific compiler flags required to have it? However, I removed mentioning this error, as by default, this code does not result in CS1928.
Indentations were messy
Samples of how to deal with this error were missing - added those for convenience.

Internal previews

📄 File
🔗 Preview link

docs/csharp/misc/cs1929.md
Compiler Error CS1929

@BillWagner Thank you for the review!
I gathered all your suggestions 1:1 locally, as I also wanted to improve the samples a bit.
All improvements and changes are summarized in the latest commit message.


Feature Request: Add support of expires extension like nginx.

Why do we need it?
In real world usage, we want to control resources, like jpg,css,js to have a default expires timeout by using cache-control.
How could it be?
Implement extension that adds some annotations to support cache control with some sub path or path ext name support.
Other related information
Like nginx:
if ($request_uri ~* \.(js|css|gif|jpe?g|png)) {
  expires 30d;
}

expires: http://nginx.org/en/docs/http/ngx_http_headers_module.html#expires

I can have a try

@LeBW  Is there any progress on this?

@LeBW Is there any progress on this?

It's in the development

@LeBW Can you add me as a WeChat friend (my WeChat ID: nomadao), please note your github id to facilitate subsequent communication.


Apply bootstrap EnvoyFilter before proxy reset

Description
Apply EnvoyFilter disabling change in envoy for sidecars and ingress gateway
Related issues

https://github.com/kyma-project/istio/issues/252

/retest

/retest

/retest

/retest

The error logs from pre-main-reconciler-integration-k3d indicate hpainterceptor_test.go failed @triffer , is it something because of your change?
    hpainterceptor_test.go:49:
        	Error Trace:	/home/sa_117798148653314453801/reconciler/pkg/reconciler/service/hpainterceptor_test.go:49
        	Error:      	Received unexpected error:
        	            	no matches for kind "HorizontalPodAutoscaler" in version "autoscaling/v2beta2"
        	Test:       	TestHPAInterceptor
--- FAIL: TestHPAInterceptor (86.23s)

The error logs from pre-main-reconciler-integration-k3d indicate hpainterceptor_test.go failed @triffer , is it something because of your change?
    hpainterceptor_test.go:49:
        	Error Trace:	/home/sa_117798148653314453801/reconciler/pkg/reconciler/service/hpainterceptor_test.go:49
        	Error:      	Received unexpected error:
        	            	no matches for kind "HorizontalPodAutoscaler" in version "autoscaling/v2beta2"
        	Test:       	TestHPAInterceptor
--- FAIL: TestHPAInterceptor (86.23s)

We didn't change anything that could use HPA, to me it looks like a problem with use of deprecated API https://kubernetes.io/docs/reference/using-api/deprecation-guide/#horizontalpodautoscaler-v126

@barchw , can you just change this import from v2beta2 to v2 ? I think then it will fix and make your PR pipeline green.

/retest


Test validation test template

Right now we have a skipped test for the validation template for models with patch clamp data.
This is just a test that we can run the iPython notebook @rgerkin made, so it shouldn't be too hard to get passing again.

@rgerkin Trying to run the ipy notebook and getting an error with neuronunit. Looks like some assertion in this method is failing. I'm assuming this means the observation is not valid? It's not clear why this ran before, but does not currently work.

@travs The data being passed to it used to be a list and is now a tuple.  I was previously only accepting lists and np arrays.  I added tuples so the rgerkin fork should work now but wait until the tests run and I'll give you a pip upgrade path.

Ok awesome! Thanks for checking this out Rick

@travs Try upgrading neuronunit via pip and run the notebook again.

@rgerkin Ok, tl;dr, this is a long comment about my install troubles, since python's packaging/install system is a mess. Does the notebook work for you in the end? If so, could you do a quick pip list and see if I'm missing something locally?
My pip list
begin
When installing from a git+https://package, I could never get the dependencies from dependency_links in package to work automatically. When I install neuronunit like
pip install -e git+https://github.com/rgerkin/neuronunit.git#egg=neuronunit

I have elephant (0.1.0) and neo (0.3.3), for some reason, even though the setup.py in neuronunit specifies other versions.
I tried installing the dependencies manually, like in neuronunit's dependency_links, so I did:
pip install git+http://github.com/neuralensemble/python-neo.git#egg=neo-0.4.0dev
pip install git+http://github.com/neuralensemble/elephant.git#egg=elephant-0.1.1

and I ended up getting this when I ran notebook_test.py
tests/notebook_test.py:11: AssertionError
---------------------------------- Captured stdout call ----------------------------------
Not a valid NeuroML 2 doc: (<type 'exceptions.IOError'>, IOError(u'Error reading file \'../models/Cav1.channel.nml\': failed to load external entity "../models/Cav1.channel.nml"',), <traceback object at 0x1080b13f8>)
---------------------------------- Captured stderr call ----------------------------------
Traceback (most recent call last):
  File "IVCurve_Model.py", line 35, in <module>
    model = ChannelModel(channel_file_path,channel_index=0,name=channel_model_name)
  File "/Users/travis/.virtualenvs/test/src/neuronunit/neuronunit/models/channel.py", line 17, in __init__
    channels = ca.get_channels_from_channel_file(self.nml_file_path)
  File "/Users/travis/.virtualenvs/test/lib/python2.7/site-packages/pyneuroml/analysis/NML2ChannelAnalysis.py", line 246, in get_channels_from_channel_file
    channels = list(doc.ion_channel_hhs.__iter__()) + \
AttributeError: 'NoneType' object has no attribute 'ion_channel_hhs'

Not sure if this is to do with the incorrect version of elephant I apparently have (when I do the install command given above, it still installs 0.1.0) or something internal to the script.

@travs
I think the dependency links are working correctly at least on Travis-CI because it is installing the right versions there, but maybe there is something else going on when you try to install a different way.
But the error you are getting is not elephant or neuronunit related.  It is what you get when the NeuroML doc doesn't load correctly, or when libNeuroML is the wrong version.  Let me reproduce everything on a clean Ubuntu VM and I'll get back to you with the recipe.

@rgerkin Ok, thank you Rick :smile:
The issue with dependency links won't show up directly in Neuronunit, but rather when installing neuronunit via pip install git+https://.... One way around this would be for CW to install neuronunit by cloning the git repo and installing locally with python setup.py install.
I can take care of the installation issues for sure, as long as I can get the notebook running in a local environment.

@travs
I switched my setup.py script from distutils to setuptools recently, precisely so that the dependency links would be honored on setup.py install.  But maybe that keeps them from being honored in pip install?

@rgerkin Ahh, that may be the issue for installation.

OK, I got everything working on a blank Ubuntu VM (the default Ubuntu selection in Amazon EC2).  Here is what was required.
However, none of that really has anything to do with the source of the error.  It was actually several changes in ChannelWorm that were responsible, so I updated IVCurve_model.py in cbbc343 to account for those.
First, the relative path to the NML file wasn't working, so I made the path determination more robust.  See the IOError(u'Error reading file \'../models/Cav1.channel.nml\': failed to load external entity "../models/Cav1.channel.nml"', section in your traceback above, which just says it couldn't find the file.
Second, the Initiator class has a new location, and new method names.
Third, the channel model name, and the path to the experimental data had changed.

Ok, thanks for that Rick. :smile:
We should probably have another discussion about keeping the notebook and script in sync as well, since there are a few steps required right now (make changes in one, replicate in the other).
We discussed something over in #102 as well, but since the current errors involve changing the .py script itself, maybe we don't have to change anything in the notebook.

@travs I think the script should never be edited manually.  It should only be produced via nbconvert from the notebook.  In fact, this will also tell us if the notebook is likely to work from a vanilla installation.

@rgerkin @travs, the parameters used in this script should probably be used for generating the iv curve from the nml file. See also https://github.com/openworm/ChannelWorm/issues/96#issuecomment-134233138


Cluster capacity analysis

Description
Estimation current cluster utilization and express it in a form of "how many pods of given requirements can be still scheduled in a cluster". Operator can then estimation remaining capacity in the following way:

if I can schedule 100 pods of a given shape, capacity is still sufficient
if I can scheduler only 50 pods of a given a shape i am about to run out of resources and need to do something about it.

Progress Tracker

[ ] Alpha

[ ] Write and maintain draft quality doc

[ ] During development keep a doc up-to-date about the desired experience of the feature and how someone can try the feature in its current state. Think of it as the README of your new feature and a skeleton for the docs to be written before the Kubernetes release. Paste link to Google Doc: DOC-LINK

[ ] Design Approval

[ ] Design Proposal.  This goes under docs/proposals.  Doing a proposal as a PR allows line-by-line commenting from community, and creates the basis for later design documentation.  Paste link to merged design proposal here: PROPOSAL-NUMBER
[ ] Decide which repo this feature's code will be checked into. Not everything needs to land in the core kubernetes repo. REPO-NAME
[ ] Initial API review (if API).  Maybe same PR as design doc. PR-NUMBER

Any code that changes an API (/pkg/apis/...)
cc @kubernetes/api

[ ] Identify shepherd (your SIG lead and/or<EMAIL_ADDRESS>will be able to help you). My Shepherd is<EMAIL_ADDRESS>(and/or GH Handle)

A shepherd is an individual who will help acquaint you with the process of getting your feature into the repo, identify reviewers and provide feedback on the feature. They are not (necessarily) the code reviewer of the feature, or tech lead for the area.
The shepherd is not responsible for showing up to Kubernetes-PM meetings and/or communicating if the feature is on-track to make the release goals. That is still your responsibility.

[ ] Identify secondary/backup contact point. My Secondary Contact Point is<EMAIL_ADDRESS>(and/or GH Handle)

[ ] Write (code + tests + docs) then get them merged.  ALL-PR-NUMBERS

[ ] Code needs to be disabled by default.   Verified by code OWNERS
[ ] Minimal testing
[ ] Minimal docs

cc @kubernetes/docs on docs PR
cc @kubernetes/feature-reviewers on this issue to get approval before checking this off
New apis: Glossary Section Item in the docs repo: kubernetes/kubernetes.github.io

[ ] Update release notes

[ ] Beta

[ ] Testing is sufficient for beta
[ ] User docs with tutorials
- Updated walkthrough / tutorial in the docs repo: kubernetes/kubernetes.github.io
- cc @kubernetes/docs on docs PR
- cc @kubernetes/feature-reviewers on this issue to get approval before checking this off
[ ] Thorough API review

cc @kubernetes/api

[ ] Stable

[ ] docs/proposals/foo.md moved to docs/design/foo.md
- cc @kubernetes/feature-reviewers on this issue to get approval before checking this off
[ ] Soak, load testing
[ ] detailed user docs and examples

cc @kubernetes/docs
cc @kubernetes/feature-reviewers on this issue to get approval before checking this off

FEATURE_STATUS is used for feature tracking and to be updated by @kubernetes/feature-reviewers.
FEATURE_STATUS: IN_DEVELOPMENT
More advice:
Design

Once you get LGTM from a @kubernetes/feature-reviewers member, you can check this checkbox, and the reviewer will apply the "design-complete" label.

Coding

Use as many PRs as you need.  Write tests in the same or different PRs, as is convenient for you.
As each PR is merged, add a comment to this issue referencing the PRs.  Code goes in the http://github.com/kubernetes/kubernetes repository,
and sometimes http://github.com/kubernetes/contrib, or other repos.
When you are done with the code, apply the "code-complete" label.
When the feature has user docs, please add a comment mentioning @kubernetes/feature-reviewers and they will
check that the code matches the proposed feature and design, and that everything is done, and that there is adequate
testing.  They won't do detailed code review: that already happened when your PRs were reviewed.
When that is done, you can check this box and the reviewer will apply the "code-complete" label.

Docs

[ ] Write user docs and get them merged in.
User docs go into http://github.com/kubernetes/kubernetes.github.io.
When the feature has user docs, please add a comment mentioning @kubernetes/docs.
When you get LGTM, you can check this checkbox, and the reviewer will apply the "docs-complete" label.

Since I didn't see it mentioned above -- we've been having some discussion of this in kubernetes/kubernetes#32677

@ingvagabund @davidopp which SIG is a sponsor of the feature? SIG-Scheduling, I suppose?

I will get to the description, update it accordingly and carry missing steps. Still cleaning my backlog.

which SIG is a sponsor of the feature? SIG-Scheduling, I suppose?

Yes

Is there actually going to be code for this in 1.5? If not, I think we should remove the 1.5 milestone.

The proof of concept is already implemented [1]. It "just" runs the scheduler as long as it can schedule specified pod. No cluster state re-computation other than adding scheduler pods back to the loop.
[1] https://github.com/ingvagabund/cluster-capacity

@ingvagabund are we expecting to have this feature in 1.5 (at least in Alpha state)?

All PRs needed for the cluster capacity functionality are merged (just need to be picked in 1.5 release). There is one issue that needs to be resolved before the solution can be run in a container for a long time [1]. Otherwise you can already run the analysis over the current master. What is missing is pod specification and a command more user-friendly than curl. Plus some minor issues&nits.
[1] https://github.com/kubernetes/kubernetes/issues/28158

This feature is not in the kubernetes/kubernetes repo, so it is not tied to a release.


Create a repository for curations

Setup a separate repository for PackageCurations.
Consider the use cases:

packaging a set of default curations with ORT
sharing globally valid curations across organizations

Think about different risk profiles of curations:

how correct / risky should the curations be
should the curations for different risk appetites be separated

Best practices / commit guidelines:

It seems important to agree upfront on best practices / commit guidelines, thinking about rules of thumb like prefer excludes over license finding curations, in which case to use package configuration vs. package concluded license and so forth.

File layout:

agree upfront on a file / directory layout

Setup a basic PSV

The repository has been created with an initial set of package curations:
https://github.com/oss-review-toolkit/ort-config
I will close this ticket in favor of creating specific issues in the other repository if required.


Error Keyboard

Hi
I'm having trouble on an ion-input,
I click on it it opens the keyboard, I close the keyboard and try to click again it will not, what can it be?
Sorry, Iam BR
Ionic version:  (check one with "x")
[ ] 2.x
[x] 3.x
[ ] 4.x
I'm submitting a ...  (check one with "x")
[x ] bug report
[ ] feature request

Hello! While we appreciate you opening an issue with us I am going to close this issue and ask that you open a new one that has the issue template filled out, please.
Also, please include a sample application shared via GitHub that demonstrates the issue you are having.
Thanks for using Ionic!


Installer doesn't work

Hello there,
I'm very interested in this application, and I can't find any alternatives. So I would really like to make this work.
When I execute the command listed in the readme.md iit works until it is creating the docker containers. I already have docker installed and I'm running ubuntu on the server. This is the log:
sudo /bin/bash -c "$(curl -fsSL https://get.coollabs.io/coolify/install.sh)"
####################################
If you interested in what this script does, go to https://github.com/coollabsio/get.coollabs.io
####################################

# Executing docker install script, commit: 0e685c6ac0bddd7b2ba7bcaaeb519746ad249a29
Warning: the "docker" command appears to already exist on this system.

If you already have Docker installed, this script can cause trouble, which is
why we're displaying this warning and provide the opportunity to cancel the
installation.

If you installed the current Docker package using this script and are using it
again to update Docker, you can safely ignore this message.

You may press Ctrl+C now to abort this script.
+ sleep 20
+ sh -c 'apt-get update -qq >/dev/null'
+ sh -c 'DEBIAN_FRONTEND=noninteractive apt-get install -y -qq apt-transport-https ca-certificates curl >/dev/null'
+ sh -c 'curl -fsSL "https://download.docker.com/linux/ubuntu/gpg" | gpg --dearmor -o /usr/share/keyrings/docker-archive-keyring.gpg'
File '/usr/share/keyrings/docker-archive-keyring.gpg' exists. Overwrite? (y/N) y
+ sh -c 'echo "deb [arch=amd64 signed-by=/usr/share/keyrings/docker-archive-keyring.gpg] https://download.docker.com/linux/ubuntu groovy stable" > /etc/apt/sources.list.d/docker.list'
+ sh -c 'apt-get update -qq >/dev/null'
+ sh -c 'DEBIAN_FRONTEND=noninteractive apt-get install -y -qq --no-install-recommends  docker-ce-cli docker-scan-plugin docker-ce >/dev/null'
+ version_gte 20.10
+ '[' -z '' ']'
+ return 0
+ sh -c 'DEBIAN_FRONTEND=noninteractive apt-get install -y -qq docker-ce-rootless-extras >/dev/null'
+ sh -c 'docker version'
Client: Docker Engine - Community
 Version:           20.10.8
 API version:       1.41
 Go version:        go1.16.6
 Git commit:        3967b7d
 Built:             Fri Jul 30 19:54:09 2021
 OS/Arch:           linux/amd64
 Context:           default
 Experimental:      true

Server: Docker Engine - Community
 Engine:
  Version:          20.10.8
  API version:      1.41 (minimum version 1.12)
  Go version:       go1.16.6
  Git commit:       75249d8
  Built:            Fri Jul 30 19:52:16 2021
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.4.9
  GitCommit:        e25210fe30a0a703442421b0f60afac609f950a3
 runc:
  Version:          1.0.1
  GitCommit:        v1.0.1-0-g4144b63
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

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

To run Docker as a non-privileged user, consider setting up the
Docker daemon in rootless mode for your user:

    dockerd-rootless-setuptool.sh install

Visit https://docs.docker.com/go/rootless/ to learn about rootless mode.

To run the Docker daemon as a fully privileged service, but granting non-root
users access, refer to https://docs.docker.com/go/daemon-access/

WARNING: Access to the remote API on a privileged Docker daemon is equivalent
         to root access on the host. Refer to the 'Docker daemon attack surface'
         documentation for details: https://docs.docker.com/go/attack-surface/

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

latest: Pulling from coollabsio/coollabs-installer
Digest: sha256:d028d465beddf14e30b96597d1c7ee5421c938f95d16a91e4f89475e6526a7c4
Status: Image is up to date for coollabsio/coollabs-installer:latest
####################################
Installer started on http://<IP>:8080
####################################

[Wed Aug 18 15:56:41 2021] PHP 8.0.7 Development Server (http://<IP_ADDRESS>:8080) started
[Wed Aug 18 15:56:55 2021] <IP_ADDRESS>:37904 Accepted
[Wed Aug 18 15:56:57 2021] PHP Warning:  Undefined array key "QUERY_STRING" in /usr/src/app/coollabs/index.php on line 3
[Wed Aug 18 15:56:57 2021] <IP_ADDRESS>:37904 [200]: GET /
[Wed Aug 18 15:56:57 2021] <IP_ADDRESS>:37904 Closing
[Wed Aug 18 15:57:09 2021] <IP_ADDRESS>:37910 Accepted
nothing found in stack: coollabs-mongodb
Error: No such volume: coollabs-mongodb-data
Nothing found in stack: coollabs-coolify
[Wed Aug 18 15:57:31 2021] <IP_ADDRESS>:37910 [200]: GET /?onlyCoolify&domain=<DOMAIN>&email=<EMAIL>
[Wed Aug 18 15:57:31 2021] <IP_ADDRESS>:37910 Closing

and then it just hangs. No crashes, nothing. Is there maybe another way to install Coolify?

Could you perhaps publish the specifications of the machine, so we can try replicate the problem?

Also, please check if coolify is running by executing the following command: docker service ls

I looked a little futher and found it fails on a missing kernel module named bridge br_netfilter it isn't supported on my server. I guess coolify hasn't anything to do with this so i close this issue for now.


Can Autodock Vina perform Constraint Docking?

I am attempting to use Autodock Vina for molecular docking, and I would like to constrain a core of a small molecule within a binding pocket while allowing the rest of the molecule to undergo conformational search. Does Autodock Vina have a feature or method to achieve this?

Hi @shienliu
According to #280 , #152 and #121 , you can perform Anchored docking with AutoDock-GPU

Thanks, Amy. I will try.


Typescript typings for package

Is your feature request related to a problem? Please describe.
When using this package in a typescript project I receive following error:
/path-to-project/node_modules/awesome-graphql-client/dist/index.modern.mjs' implicitly has an 'any' type.
  There are types at '/path-to-project/node_modules/awesome-graphql-client/dist/index.d.ts', but this result could not be resolved when respecting package.json "exports". The 'awesome-graphql-client' library may need to update its package.json or typings.

NOTE: This problem is produced by vscode.
Describe the solution you'd like
I prefer to have a complete typing when using project or there should be a package like @types/awesome-graphql-client to add necessary typings.

This project is written in Typescript, so we provide all the typings. And for me all the typings work with VSCode. Could you please provide more details?

Closing since no reply

I'm also seeing this, perhaps the bundling isnt quite right @lynxtaa

@onionhammer Could you please provide more details? Maybe small reproduction repository? I've tested it my projects and see no issues

@onionhammer I think it depends on tsconfig.json, please share yours

@lynxtaa stock from npm create vite@latest test-build-project -- --template react-ts provides this:
{
  "compilerOptions": {
    "target": "ES2020",
    "useDefineForClassFields": true,
    "lib": ["ES2020", "DOM", "DOM.Iterable"],
    "module": "ESNext",
    "skipLibCheck": true,

    /* Bundler mode */
    "moduleResolution": "bundler",
    "allowImportingTsExtensions": true,
    "resolveJsonModule": true,
    "isolatedModules": true,
    "noEmit": true,
    "jsx": "react-jsx",

    /* Linting */
    "strict": true,
    "noUnusedLocals": true,
    "noUnusedParameters": true,
    "noFallthroughCasesInSwitch": true
  },
  "include": ["src"],
  "references": [{ "path": "./tsconfig.node.json" }]
}

Thanks! I've found the culprit, will release the fixed version today :)

I've published<EMAIL_ADDRESS>, decided to switch the bundler for tsup. Hope it helps :)

@lynxtaa so far so good, thanks for the quick turnaround; I had no idea what a can of worms file uploading was :S


adding the option "internet_access:fee=customers"

make internet_access:fee to an combo field for adding the option "internet_access:fee=customers", see https://wiki.openstreetmap.org/wiki/Key:internet_access:fee

At the moment, I unluckily do not understand what the "all checks have failed" field wnts to say to me... :/

There is a syntax error in the file that you changed... Also if you click on "Files Changed" the GitHub diff for this Pull Request highlights the error too.

Oh, I see, thanks. I just tried to correct it. I think a { was there which shouldn't have been.

@Lukas458 I incidentally closed this by renaming the default branch. You'll need to open another PR. Apologies!

Oh, I see. Okay, so I will open a new one. Thank you for information.


SGX Module gives incorrect energies for spin-polarized system.

When an open-shell calculation is run with the SGX Module, the results are incorrect unless the debug option is turned on. As an example, see the output of the following script:
from pyscf import gto, dft
from pyscf.sgx.sgx import sgx_fit

mol = gto.M(atom='H 0 0 0; F 0 0 1.1', basis='def2-tzvppd')
mol.build()
ks = dft.RKS(mol)
ks.xc = 'B3LYP'
print('RKS Energy', ks.kernel())
ks = sgx_fit(ks)
print('RKS SGX Energy', ks.kernel())

mol = gto.M(atom='N 0 0 0; O 0 0 1.15', basis='def2-tzvppd', spin=1)
mol.build()
ks = dft.UKS(mol)
ks.xc = 'B3LYP'
print('UKS Energy', ks.kernel())
ks = sgx_fit(ks)
print('UKS SGX Energy', ks.kernel())
ks.with_df.debug = True
print('UKS SGX Debug Energy', ks.kernel())

Output:
converged SCF energy = -100.434912420861
RKS Energy -100.43491242086068
converged SCF energy = -100.434944509951
RKS SGX Energy -100.434944509951
converged SCF energy = -129.891741534874  <S^2> = 0.7534406  2S+1 = 2.0034376
UKS Energy -129.89174153487397
SCF not converged.
SCF energy = -166.417639337615 after 50 cycles  <S^2> = 0.75080318  2S+1 = 2.000803
UKS SGX Energy -166.41763933761473
converged SCF energy = -129.891750579039  <S^2> = 0.75344056  2S+1 = 2.0034376
UKS SGX Debug Energy -129.89175057903878

As shown, the closed-shell molecule is calculated correctly, while the open-shell molecule has far too large an energy and is not converged unless debug=True, in which case the calculation proceeds normally. This issue also occurs for pure Hartree-Fock calculations.
Calculation performed using master branch version at commit 53e2069b4a3a2e0616bdf4d8c2e3f898c10a8330.

Hi, sorry I forgot to close this issue. I have been using the fix and everything is working fine. Thank you so much!


Is there a possibility to use week view not for the week?

Hi! This will be very helpful for me if there is some way to show week view for a full year for example. Because this view is beautiful for gantt diagram, it's simple, it's pretty. But in the scale of the week it will not work for this purpose.

Unfortunately this isn't a common enough use case to add to this module, maybe something like this might be more suited to your needs?

Thank you for quick feedback. Yes, I saw it, but for me your plugin is more pretty and simple.

Maybe fork it for your needs then to add the functionality you need :smile:


Finish implementing the conversion from register class to gcc constraint code

Here, here and here.
The GCC constraints doc will be helpful to do this.

I'll try to tackle this one.
Btw, I think you were right that support for explicit registers like in("r11") will require creating "GCC register variables" which is not yet supported by gccjit yet. I guess that'll be one more libgccjit patch. Anyway, I don't  think this kind of syntax is used often;  syscall is the only example I can come up with.
For now, I'm going to emit an error. The code as it's now is definitely incorrect.

Explicit registers are used by compiler-builtins. Almost every input and output uses an explicit register in https://github.com/rust-lang/compiler-builtins/blob/826d9e9d41dca79c9893118fdbb600fc9a837764/src/mem/x86_64.rs
Tock uses them when switching to userspace: https://github.com/tock/tock/blob/bd4808c787434f6d493f643ea7f9abe8339048e0/arch/cortex-m0/src/lib.rs#L204-L260
The x86_64 crate uses them for ports (https://github.com/rust-osdev/x86_64/blob/a9cbf1471d38b18dcfe22bf399082a445341c3e5/src/instructions/port.rs#L14) and model specific registers (https://github.com/rust-osdev/x86_64/blob/a9cbf1471d38b18dcfe22bf399082a445341c3e5/src/registers/model_specific.rs#L134-L139)

@bjorn3 I agree with all that you said, let me clarify. (I'm using x86-64 as example; everything I say applies to other architectures as well)
Here's the code part I was referring to:
https://github.com/antoyo/rustc_codegen_gcc/blob/6f50986667debbfc67776304a8ee23fe0158613f/src/asm.rs#L235-L250
It translates Rust constraints to GCC constraints, for example in("eax") => a. GCC supports a set of predefined constraints (look for "X86") for specific registers, like a for eax/rax, S for esi/rsi and so on. As you can see from your own examples, these constraints cover 9/10 uses of registers, and this is what I meant when I said that registers like r11 are not used often by programmers.
Unfortunately, when you really do need to use registers like r11, as demonstrated by your Tock example (I think we can add low-level OS/embed code to my list of exceptions), GCC ExtendedAsm does not support them directly. There's a nasty hack widely used and respectable workaround called "register variables", and libgccjit does not support them yet. I do intend to make a patch for it, but I would like to get the base cases working first.
I'd like to stress that current code translating r11 to r11 is plain incorrect and I suspect it will trigger a cryptic "incorrect constraint" error in libgccjit. Oh yes, it does, see for yourself. I think our own error, explaining what's going on and why it's not yet supported will be better.
P.S: This problem does not exist in LLVM because llvm supports "register name in curly braces" syntax for non-covered registers.
P.P.S  Also, while I'm 99% sure that "register variables" is the only proper way to support it - GCC doc explicitly cites it as the way to go, I'll probably ask on GCC mailing list to be sure).

This got me thinking: since it might be a while until I get familiar enough with gccjit codebase (I'm a complete noob to compilers, I build the road as I travel, you've been warned), we could resort to a hack of our own in the meantime. We could get it working by turning these "unknown registers" to the rm constraint and then adjusting the template with code that moves the value from this temporary register/memory to the a desired register.
For example, this Rust code:
let x: u64 = 2;
asm!("add r11, r11", inout("r11") x);

will correspond to this GNU C code:
uint64_t x = 2;
asm("
     mov r11, %0 ; inserted by the backend
     add r11, r11 ; the original template
     mov rax, r11 ; inserted by the backend"

     : "+&rm" (x) // the backend determined rax as a spare register not involved in in/out constraints nor in the clobbers list
     :
     : "r11" // add the original r11 to the clobbers list
);

This code is obviously ineffective, it will clobber more registers than it should, it will diminish some optimizations around this asm block, but this code is both correct and working (in my noob's opinion). And of course this is just a temporary measure until we get libgccjit to support GCC register variables and rewrite it properly.
@antoyo  what do you think?

I can probably quickly make a patch to support register variables.
I'm on vacation, but I'll be back on Monday, so I could start working on it then.
That way, it should be simpler and correct.
In the meantime, you can start working on what does not require them. If at some point you're waiting for me to add the support of register variables, please ping me and I'll see what I can do.

Finished in https://github.com/antoyo/rustc_codegen_gcc/pull/8.


Filter out some tracking

I simply love Umami! It's great, simple design and all.
One thing I've been wondering though, is it possible to filter out all tracking of localhost? It annoys me that it's in my stats :dagger:
Would be a great addition! :100:

I think something like this, if implemented, might be an optional parameter. Could you provide more info on your use case?
In my case, I haven't found it to be much of an issue since the stats can be useful for my local dev installation. For my live sites, I either make sure to only build with the tracking script on production or I can inject the script as a snippet when pushing to my Netlify hosted sites.

Actually, I totally forgot that there's the data-domains property which sets which domains to track. That should be what you're looking for.
https://umami.is/docs/tracker-config

Great, that's exactly what I need! Thanks! :partying_face:

Sadly I've tried using data-domains and still no success?

@Mobilpadde what is not working? The data-domains matches against window.location.hostname. Are those values the same?

I'm matching againt data-domains="hasty.dev,embed.hasty.dev" so two domains in the exact same way as the docs, and what window.location.hostname gives, sadly I'm still getting localhost in my stats :cry:

You can also set umami.disabled to true in local storage when you're using localhost.


WIP: Enum relational serialization

what
Relational approach to serializing enums
why
If we serialize all the enum values as strings, each time an enum data point is ingested, we have an expensive disk operation on our hands. Therefore, this PR explores the idea of storing only the hashcode, rather than the whole string of the enum value.
how
We serialize the hashcode in metrics_preaggregated_full rather than the whole string name. However, we also serialize the hashcode of the value, with the actual value in a separate column_family, as follows:
 key             | column1    | value
-----------------+------------+------------------
 123456.enum1 | -841539219 | anotherenumvalue
 123456.enum1 |  262599952 |        enumvalue

Since the column is the hashcode, while querying we will just get the value stored for the given locator and hashcode.
Todo:
Working on a PoC to make sure that querying the actual string values is feasible

@tilogaat @GeorgeJahad This is a great idea tilo!  Going to look over your code and cassandra schema changes to see how you will implement this and add some comments.

+1


Add filereceiver component with updated functionality

What does this PR do?
This PR is part 2 of https://github.com/f5/otel-arrow-adapter/pull/185
Adds the filereceivercomponent directly rather than using the component currently in opentelemetry-collector-contrib package.
Adding the component directly allows us to use the functionality from this https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/22080 open in the contrib repository. This contrib PR is taking a while to get approved so in the meantime it might be better to add these changes to start using these components to replay data in production.
Example config:
receivers:
  file:
    path: ../../gen/receiver/filereceiver/testdata/metrics.json
    compression: zstd
    format: json

Testing
Ran the cmd/otelarrowcol with the filereceiver component and successfully read from file in the desired format/compression
(cc: @jmacd)

@moh-osman3 there are some conflicts to resolve that prevent to merge this PR.

@lquerel rebased and fixed the conflict. Thank you!

LGTM


Option to have a Tsd as an index

When working with Tsds, I might sometimes write, eg for filtering:
some_tsd = Tsd(...)
some_tsd.d[some_tsd.d > 500] = np.nan

I think it would be nice and not confusing for how the class works atm (very thorough feature equivalence with np.ndarray) having instead:
some_tsd = Tsd(...)
some_tsd[some_tsd > 500] = np.nan

Just by changing the setter and getter for the Tsd.
Would something like this make sense? This is just a draft for Tsd, it could be extended to other classes maybe although I never encountered the need.

I think it's good and I would keep it only for time series.

Everything should have been addressed now, let me know if there's anything else I should fix

That's great. I would still add one test for it.

Excellent point, adding tests I actually realised I did not set the behavior for setitem in TsdFrame.
This should be now be good to go!

It's missing for TsdTensor I think?

Oh sorry maybe I misunderstood one of your early messages - do you thing this should be implemented for Tsdtensors as well?

Or you mean I should exclude tensors?

Yes I would implement it for TsdTensor too

I'll come back to this soon if still unaddressed!
Since I am at it, I'll ask a slightly related but separate question: why is TsIndex not a Ts but a np.array? Is there some actual reason or it is just historical?

Basically TsIndex is like pd.Index in pandas. Ts is the user facing module. TsIndex is the non-user facing module which hold the timestamps and timestamps methods across all modules with time.

This should now good to go!
I did a minor refactoring of test classes for readability, hopefully that's fine. Also, I'd love to do a separate PR for tests cleanup if that is good for you!

Let mw know if anything else is needed here!
(In the test refactoring, move test generated files to temporary folders would be very useful to avoid spurious commits)

Thanks I will look into it as soon as possible.

Ok, done it! I also change a bit the logic to bit more interpretable, and fixed the tests accordingly

Should have fixed stuff and rebased on dev head. Would be great if we can merge so that I won't have to resolve more conflicts in the future!

Looks good thank you Luigi


Clarify the wording here to match what is in the OKTA form.

Why: The wording should reflect the actual field name in OKTA, instead of a description of what the field is.
Closes ISSUE https://github.com/github/docs/issues/22475

What's being changed (if available, include any code snippets, screenshots, or gifs):
Updating the wording here to reflect the actual field name in the OKTA form.

Check off the following:

[x] I have reviewed my changes in staging (look for the "Automatically generated comment" and click the links in the "Preview" column to view your latest changes).
[ ] For content changes, I have completed the self-review checklist.

@stacycarter to review the wording here.

👋 @adamrr724 - Thanks so much for opening a PR! I'll get this triaged for review :zap:

Pls help me


Idiomatic dating

Hi Danny
Added some code to make outputting the date idiomatic. I'm not sure if it's right but I'm sure you'll get the idea. You need to incorporate something for Prid. Kal. (i.e. the last day of the month - annoying to code because of leap years).

Thanks! I'll merge it and then make the changes on the master branch

Made my changes in commit 7b895a6, see what you think!
I'll need to work out some way to automate tests...

Looks good as far as I can tell! There’s only one addition to be worked out. The Roman’s actually said something like “a.d. bis XVI Kal Mar” for the leap year. But I need to figure out exactly what it is they said (what I’ve written here is wrong).
Matthew A Jay
PhD Student in Legal Epidemiology
UCL Legal Epidemiology Grouphttps://www.ucl.ac.uk/child-health/research/population-policy-and-practice/child-health-informatics-group/legal-epidemiology-group
Child Health Informatics Grouphttps://www.ucl.ac.uk/child-health/research/population-policy-and-practice/child-health-informatics-group
Co-ordinator and spoken Latin tutor
UCL Latinitas Societyhttp://www.soclatlon.wordpress.com/
Episode 6 of «Salvi Sitis!» - the Latin language epidemiology podcast – is out now! www.salvisitis.libsyn.comhttp://www.salvisitis.libsyn.com/ / @SalviSitisPodhttp://www.twitter.com/SalviSitisPod
UCL Great Ormond Street Institute of Child Health
30 Guilford Street, London WC1N 1EH
Email: matthew.jay.15<EMAIL_ADDRESS>Twitter: @mattjayresearchhttps://twitter.com/mattjayresearch
Personal URL: https://matthewjayresearch.wordpress.com/
<EMAIL_ADDRESS>From: tech189<EMAIL_ADDRESS>Sent: 27 February 2020 15:08
To: tech189/Ab-Urbe-Condita<EMAIL_ADDRESS>Cc: Jay, Matthew<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [tech189/Ab-Urbe-Condita] Idiomatic dating (#1)
Made my changes in commit 7b895a6https://github.com/tech189/Ab-Urbe-Condita/commit/7b895a6df330c53025648451cd822dbd30bc69d8, see what you think!
I'll need to work out some way to automate tests...
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/tech189/Ab-Urbe-Condita/pull/1?email_source=notifications&email_token=AE2XDIS7K5V32BBWUL627Y3RE7JN7A5CNFSM4KOZZHYKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOENEV5SY#issuecomment-592010955, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AE2XDIVOUXWOXVEL4KN5HSDRE7JN7ANCNFSM4KOZZHYA.

Sorry I realise in my previous comment I posted the wrong commit - my changes are in a719f4e (not 7b895a6) but you've probably seen them in the master branch!
According to this page: http://www.novaroma.org/nr/Roman_dates they used a.d. bis VI Kal. to distinguish between the 24th of February on a leap year and on a normal year. Does that seem right?

Ah yes, that’s it!
Matthew A Jay
PhD Student in Legal Epidemiology
UCL Legal Epidemiology Grouphttps://www.ucl.ac.uk/child-health/research/population-policy-and-practice/child-health-informatics-group/legal-epidemiology-group
Child Health Informatics Grouphttps://www.ucl.ac.uk/child-health/research/population-policy-and-practice/child-health-informatics-group
Co-ordinator and spoken Latin tutor
UCL Latinitas Societyhttp://www.soclatlon.wordpress.com/
Episode 6 of «Salvi Sitis!» - the Latin language epidemiology podcast – is out now! www.salvisitis.libsyn.comhttp://www.salvisitis.libsyn.com/ / @SalviSitisPodhttp://www.twitter.com/SalviSitisPod
UCL Great Ormond Street Institute of Child Health
30 Guilford Street, London WC1N 1EH
Email: matthew.jay.15<EMAIL_ADDRESS>Twitter: @mattjayresearchhttps://twitter.com/mattjayresearch
Personal URL: https://matthewjayresearch.wordpress.com/
<EMAIL_ADDRESS>From: tech189<EMAIL_ADDRESS>Sent: 28 February 2020 10:26
To: tech189/Ab-Urbe-Condita<EMAIL_ADDRESS>Cc: Jay, Matthew<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [tech189/Ab-Urbe-Condita] Idiomatic dating (#1)
Sorry I realise in my previous comment I posted the wrong commit - my changes are in a719f4ehttps://github.com/tech189/Ab-Urbe-Condita/commit/a719f4eab4ce2b9d83600c589a1f2ff692f94e81 (not 7b895a6https://github.com/tech189/Ab-Urbe-Condita/commit/7b895a6df330c53025648451cd822dbd30bc69d8) but you've probably seen them in the master branch!
According to this page: http://www.novaroma.org/nr/Roman_dateshttps://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.novaroma.org%2Fnr%2FRoman_dates&data=02|01||ab394ea0bc6f4b076eaa08d7bc38a547|1faf88fea9984c5b93c9210a11d9a5c2|0|0|637184823784713771&sdata=1D65vDOx9hVPAAML2jRt1lkuvMgAy7k21MXwR81ZNpU%3D&reserved=0 they used a.d. bis VI Kal. to distinguish between the 24th of February on a leap year and on a normal year. Does that seem right?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/tech189/Ab-Urbe-Condita/pull/1?email_source=notifications&email_token=AE2XDIWCXS5NEF45FQCFEPDRFDREPA5CNFSM4KOZZHYKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOENIBFEI#issuecomment-592450193, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AE2XDIRYEPAAGAYKRDKFA6TRFDREPANCNFSM4KOZZHYA.


scope_queryset not working

I have ModelViewSet with permission_class and override method scope_querset inside, but it isn't called  (if not override, parent's method not called too). what could be?

Could you post the relevant parts of your code here?

Method scope_querset is unused and isn't called anywhere. How to use it? Maybe i should in ViewSet to assign queryset value from this method? Or, if possible, advise the correct use

Hi -- sorry about the delay in responding.
Here's an example below. It's a way to virtually segregate the database. For example, in a multi-tenant app, users of one tenant should have no awareness of another tenant's objects/rows. By having the scope_queryset method on the access policy class, the idea is to centralize the access logic.
ViewSet:
@property
    def access_policy(self):
        return self.permission_classes[0]

    def get_queryset(self):
        qs = self.access_policy.scope_queryset(self.request, Task.objects.all())

AccessPolicy:
    @classmethod
    def scope_queryset(cls, request, qs):
        return qs.filter(tenant_id=request.user.tenant_id, soft_delete=False)

ty, i will try. I think this isn't native solution and requires a description of this example in documentation. If possible, i will do it

what is self.request for ViewSets? Do they have such property or it should be defined and assigned?
I get:
File "/home/ahmad/jkar/karmodir/views.py", line 47, in get_queryset
    self.request, self.queryset)
AttributeError: 'MemberViewSet' object has no attribute 'request'


Support int32 in substring dedup

I'm using a tokenizer with > 100k vocab size, so the token id overflow as it is stored in uint16. I'm wondering if we can add support for int32? Is it possible to simply change the type or is there other places that need to be changed?

but why do you need a big tokenizer for dedup?

a large vocab size is better in multilingual setting if we use an unified tokenizer


Handling decimal types explicitly

Related #191
From what I can see, we don't explicitly handle the Python decimal type in our create table statements. Evaluate, then if not, implement this so that users passing explicit decimal types get the proper upload behavior into OmniSci
https://docs.python.org/3.7/library/decimal.html

Update: filed internally as https://jira.omnisci.com/browse/BE-3467 for decimal downcast


Reduce logging level

Why we need this PR

Reduce logging levels
Changes made

Which issue(s) this PR fixes

Test plan

/override "ci/prow/4.12-openshift-e2e"
/override "ci/prow/4.13-openshift-e2e"
/override "ci/prow/4.14-openshift-e2e"
/override "ci/prow/4.15-openshift-e2e"

/override "ci/prow/4.17-openshift-e2e"

/cherry-pick release-0.9


Identity Center Configuration

Describe the bug
When deploying LZA into a brownfield AWS environment (with IDC already in main account) we see a line in the Operations stage that says:

We have not configured IDC in any of the yaml config, so where/how do we change this setting and put IDC in a delegated account that we specify, as the documentation does not give a working example of this
To Reproduce
Run LZA with IDC already configured in main
Expected behavior
LZA should take no action if IDC delegation isn't specified in the yaml configs
Please complete the following information about the solution:

[ 1.3.0] Version: [e.g. v1.1.0]

[ eu-west-1] Region: [e.g. us-east-1]

[No ] Was the solution modified from the version published on this repository?

[ ] If the answer to the previous question was yes, are the changes available on GitHub?

[ ] Have you checked your service quotas for the sevices this solution uses?

[ ] Were there any errors in the CloudWatch Logs?

Screenshots
If applicable, add screenshots to help explain your problem (please DO NOT include sensitive information).
Additional context
Add any other context about the problem here.

@farmerbean Hello, thank you for identifying this bug! This behavior is expected based on the current design in LZA 1.3.0.  Currently, the account set as the delegatedAdminAccount in the security-config.yaml configuration file is used as the delegated administrator for AWS Identity Center.
We've received some similar customer feedback and agree that this behavior is unclear. Additionally, we understand customers may want to use a different account for Identity Center administration. Because of this, we've implemented a separate property in the iam-config.yaml to explicitly set the delegated administrator for AWS Identity Center.
We expect to release this feature in the upcoming v1.3.1 release, I will keep this issue open until that has launched.

Hello! I can confirm that with LZA v1.4.3 this is still happening.
I thought that it was a manual change that we carried out when having enabled IC in our organization, manually, but even if I unset the delegated admin in the IC settings manually in the console, when LZA runs again, it re-sets it, just because we have the delegated admin set in the security-config.yaml.
Please fix this issue, since it only causes confusion and breaks the LZA Deploy stage. I am still struggling with the AWS support to try and fix this :/
Thanks in advance!
Br, Virginia

I can also confirm that this is happening on fresh installation of V1.5.1, in a greenfield AWS landing zone, and would really love some clear guidance here.
For I'm considering forgoing management of Identity Center resources in LZA until this is addressed, but I'd really prefer to be using LZA for as much of this central landing zone management as possible.

Just to add some more weight to this issue - is there any fix for this in v1.6.1 - I see the same behaviour as other commentators here - whereby despite not setting a delegatedAdminAccount in iam-config.yml I'm still seeing Identity Centre deployed in the 'Audit' account as per the config in security-config.yaml


Order tier/amount updates

Adds capability to Order mutations v2 for changing the tier or amount of an order

Generally, if a tier is passed as argument, try to fetch it early from the database and make sure it's existing and valid. That will clarify the code later on.


Broken build: "cannot use c.aws (type *aws.Config) as type client.ConfigProvider"

Hi CoreOS folks,
I'm not 100% sure if the issue is within your packages or the github.com/aws/aws-sdk-go ones..
I ended up down in their code when I tried digging briefly, but didn't see recent commits that changed the broken bits, and I don't have the time to look into this more currently, but thought I'd report the broken build.
See below for output from trying to go get kube-aws (inside the official golang Docker container, so should be reproducible):
$ docker run -t --rm golang go version
go version go1.6 linux/amd64
$ docker run -t --rm golang go get github.com/coreos/coreos-kubernetes/multi-node/aws/cmd/kube-aws
# github.com/coreos/coreos-kubernetes/multi-node/aws/pkg/cluster
src/github.com/coreos/coreos-kubernetes/multi-node/aws/pkg/cluster/cluster.go:232: cannot use c.aws (type *aws.Config) as type client.ConfigProvider in argument to cloudformation.New:
        *aws.Config does not implement client.ConfigProvider (missing ClientConfig method)
src/github.com/coreos/coreos-kubernetes/multi-node/aws/pkg/cluster/cluster.go:236: cannot use c.aws (type *aws.Config) as type client.ConfigProvider in argument to cloudformation.New:
        *aws.Config does not implement client.ConfigProvider (missing ClientConfig method)
src/github.com/coreos/coreos-kubernetes/multi-node/aws/pkg/cluster/cluster.go:241: cannot use c.aws (type *aws.Config) as type client.ConfigProvider in argument to ec2.New:
        *aws.Config does not implement client.ConfigProvider (missing ClientConfig method)
src/github.com/coreos/coreos-kubernetes/multi-node/aws/pkg/cluster/cluster.go:251: cannot use c.aws (type *aws.Config) as type client.ConfigProvider in argument to cloudformation.New:
        *aws.Config does not implement client.ConfigProvider (missing ClientConfig method)

@colhom

@hkjn the way that you're building the kube-aws executable does not use the vendored Godep dependencies. What you're experiencing is the result of aws-sdk-go being a more recent version than it should be.

@colhom Ah, I see what you're saying..
I hadn't noticed the docs under the multi-node/aws/ directory:

https://github.com/coreos/coreos-kubernetes/tree/master/multi-node/aws

I can confirm that using the ./build script under the directory works just fine:
$ docker run --rm -it golang                                                                                [24/24]
root@43e9f080084d:/go# mkdir -p github.com/coreos && cd github.com/coreos/
root@43e9f080084d:/go/src/github.com/coreos# git clone https://github.com/coreos/coreos-kubernetes.git  && cd coreos-kubernetes/multi-node/aws/
Cloning into 'coreos-kubernetes'...
[...]
root@43e9f080084d:/go/src/github.com/coreos/coreos-kubernetes/multi-node/aws# ./build
Building kube-aws<PHONE_NUMBER>7f501943ea984433dc0d8e47ee2a5e...
# github.com/coreos/coreos-kubernetes/multi-node/aws/cmd/kube-aws
link: warning: option -X main.VERSION<PHONE_NUMBER>7f501943ea984433dc0d8e47ee2a5e may not work in future releases; use -X main.VERSION=52609982497f501943ea984433dc0d8e47ee2a5e
done
root@43e9f080084d:/go/src/github.com/coreos/coreos-kubernetes/multi-node/aws# ls /go/bin/
root@43e9f080084d:/go/src/github.com/coreos/coreos-kubernetes/multi-node/aws# ls ./bin/kube-aws
bin/kube-aws
root@43e9f080084d:/go/src/github.com/coreos/coreos-kubernetes/multi-node/aws# ./bin/kube-aws
Manage Kubernetes clusters on AWS

Usage:
  kube-aws [command]
[...]

I'd still suggest updating dependencies (using the vendor/ mechanism now enabled by default in go1.6, if possible) so installation via go get can work, but since there's no build breakage when using the supported process I'm closing the ticket.
Thanks!


Ignore "none" color in item label. Fix missing text on episodes view with Estuary skin.

with default skin Estuary on episodes view we have no text because of color none (our default color for "show name"):

after change:

alternative implementation of https://github.com/elgatito/plugin.video.elementum/pull/1011

but if we also want to make same check for all other colors - then i guess we should came up with some helper function for that.
i am not sure how to make it better.

ok, i converted this to the helper function.
UI looks the same as before:


[WIP] Filename parsing for rasterio

@martindurant @mmccarty @jbednar we have run into the filename parsing situation recently when reading in landsat data. The general issue is that there is information encoded in the filenames that belongs on one of the object's dimensions.
This PR implements the basics of what filename parsing could look like and adds an example that shows the value of this change.

We don't have a convention on this, but do you think it's best to include outputs in the example notebook? It makes for a bigger repo, and less interesting interactive session, but obviously it static-renders much more interesting.

do you think it's best to include outputs in the example notebook?

I think it makes sense to not include the outputs in the examples, and just have them rendered on the website. I only included the outputs in this PR to facilitate discussion.

Thanks!  This situation is an extremely common pattern in fields where data has been collected into flat files for many years; files are generated with a standard naming scheme on an ongoing basis, and everything else just adapts to that.  This particular PR is for intake-xarray, but there are very similar issues with huge banks of .csv files in other fields.
The examples in the notebook are clear, but it would be nice to have one where similar information is encoded in the directory name as well, as it's common to have the date or some other parameter about the data encoded there rather than in the underlying filename.

pinging @scottyhq and @apawloski who are going to be quite interested in this feature.

do you think it's best to include outputs in the example notebook?

I only ever commit the cleared notebook to github, and instead usually post it on my anaconda.org account, both to avoid bloating the repo and make things more diffable, but also because github's notebook viewer doesn't support Bokeh plots anyway.

@jsignell can you clear the notebook output committed to this PR and post it to anaconda.org as @jbednar suggests?  I have a handy script if you need it.  Also, please reference the notebook here.

I cleared the notebook in this PR and put the rendered version here: https://anaconda.org/jsignell/intake_xarray_multifile/notebook

Also, it would be good to get some unit tests for those utilities.

Not sure what the protocol is for this. This PR depends on the latest version of master.

Happy to push a release of Intake to support this. Will that work?

Will that work?

Yep that'll work

@jsignell - passes now. All done here?

@mmccarty @martindurant what do you guys think? I haven't got any tests on this but that would involve adding a few tiffs. There is an example, so potentially if the examples ever get run on CI that would cover this.

We don't run doctests, and I think it would be totally fine to add data files to the repo, so long as they aren't big. You can also generate files, or copy the existing ones to various filenames in a tmpdir.

Ok @martindurant this is ready.

Thank you, that's great.


UserWarning: Applied workaround for CuDNN issue, install nvrtc.so

Dear all,
I have encountered this UserWarning when running model_angelo build_no_seq:

~/anaconda3/envs/model-angelo_local/lib/python3.10/site-packages/torch/nn/modules/conv.py:605: UserWarning: Applied workaround for CuDNN issue, install nvrtc.so (Triggered internally at /opt/conda/conda-bld/pytorch_1711403388920/work/aten/src/ATen/native/cudnn/Conv_v8.cpp:80.)

Following this StackOverflow question I have added a symbolic link at ~/anaconda3/envs/model-angelo_local/lib:
libnvrtc.so -> libnvrtc.so.11.8.89
besides the one that was generated automatically:
libnvrtc.so.11.2 -> libnvrtc.so.11.8.89
By running ln -sfn libnvrtc.so.11.8.89 libnvrtc.so
And now there is no warning.
Hope it helps :)

It helped, thank you!

Thank you @arr0i3 , I am not sure why this error occurs. I will pin your issue.


Move context menu items to submenu

BBT adds 5 items to the Zotero item context menu, several of which I suspect most users never use (e.g., citation links, reporting BBT errors). I imagine that most users only use any of these functions on occasion. It's a bit annoying to me to have so many items that I never use added to the context menu.
Would you be okay with moving the item context menu options to a Better BibTeX sub menu? What about moving the Report BBT Errors option to the Help menu, where Zotero's own error reporting is? If you're okay with that, I can make a PR to do that.

I'm ok with moving them to a submenu, but wrt the error reporting option, that already lives on the help menu but it does something else there. The error report from the help menu only submits the error log, the one from the context menu sends the error report + the selected items. I'd sooner remove the one in the help menu than the one in the context menu. I usually need a copy of the items to do any real debugging, plus it gives me new test cases to prevent regressions.

The file names with colons have been changed on master

Can you also change aux.md to aux-scanner.md (or I can do that).

done (but renaming files of the website needs to be done in tow places to have the navigation work)

Yeah, saw that. Thanks!


Shadow does not appear under triangle of tooltip

The box shadow doesn't appear under the triangle. To solve this, a third triangle needs to be added which emulates the box shadow.

The drop shadow has been added!


Initial CI workflow.

Based on the Routinator CI workflow.

The test failure is fixed in https://github.com/NLnetLabs/routecore/commit/04730b27fc6e8680a5dcf249da712d8317c1675f. As a release of routecore is expected soon this PR can wait to use the new release so that the checks here can all go green before merging.


[HOPSWORKS-3105] Collect user summaries by statement type from sys

@gibchikafa - PR looks ok but it's open on the wrong branch. It should be ndb not master.

I merged this commit in the correct branch we can close this PR.


Separate docker image build step

Not going to work. You cannot split off steps from a job and preserve the existing environment without having a custom runner.


V2 site overwrite magic __call method

Related:

Overwrite __call method
https://github.com/timber/timber/pull/1700

Issue
When calling a site option that does not have it's own method, like site.home. Timber would use the magic __call method from the Core class. This magic method by defaults calls the meta() method. Since the meta() method was deprecated in the site class (https://github.com/timber/timber/pull/1700) the magic __call method throws a deprecation notice.
Solution
Overwrite the __call method in Site.php and call the appropriate option() method instead.
Impact
Less questions on why deprecation notices are thrown.
Usage Changes
None.
Considerations
Sometimes it's hard to wrap your head around what are actual instantiated data in Timber and what is called via these magic methods. I always thought that {{ site.home }} was a valid method, but when digging deeper I found out that you should call {{ site.link }}
I would be in favor of deprecating these magic methods in the future as well so people (including myself) will learn the difference.
Testing
No, should it be tested?

@gchtr , Directly created a PR for this. Should we add this to the 2.0 release?

Sometimes it's hard to wrap your head around what are actual instantiated data in Timber and what is called via these magic methods. [...] I would be in favor of deprecating these magic methods in the future as well so people (including myself) will learn the difference.

I fully support that.

coverage: 88.462% (-0.06%) from 88.522% when pulling 20dd75efd1407aaa15c2c1cdb47aa684ddbef8c6 on v2-site-overwrite-call-method into f56f062cd56a706a24848915bb554615bc215542 on 2.x.

@gchtr , Directly created a PR for this. Should we add this to the 2.0 release?

Thanks for the PR. Yes, because this actually fixes a bug I’d say we should include it in the 2.0 release.

Testing
No, should it be tested?

@Levdbas I think it would be good if we could add a test for this. Do you need help with that?

@gchtr , Directly created a PR for this. Should we add this to the 2.0 release?

Thanks for the PR. Yes, because this actually fixes a bug I’d say we should include it in the 2.0 release.

Testing
No, should it be tested?

@Levdbas I think it would be good if we could add a test for this. Do you need help with that?

Alright I created my first test and used the timber compile_string method for that. removing the __call overwrite in the site class causes the test to fail, so I think we are good here. Any feedback on how to improve this test @gchtr ?


"Panic by the mausoleum in Mortyania" clue pointing to confusing location

For the emote clue scroll "Panic by the mausoleum in Mortyania. Wave before you speak...". The red flashing arrow on the mini-map points at the island you need to get to, but they way it leads you doesn't get you to the island.
You have to go through the experiment cave first, so the arrow should point that way, and then north-west once inside the cave to the ladder that leads you right to where you need to be.

I believe this is just a limitation of the current design. In this case, an emote clue can only have one location associated with it which is where you're supposed to do the emote. In order to guide someone it would need to have several locations and know when to switch them.
Perhaps that can be an enhancement for later?

Looks like this is working as intended


Fix: show manage button when no private vaults, show sync status for websites

Description
Fix 2 bugs:

Show manage / view buttons for managed datasources correctly depending on the feature flags
Show last sync status for website.

Tested locally with: flag on|off X admin|builder|user
Risk
None
Deploy Plan
Deploy front

I don't think we need this ? we're bringing back the system vault and removing management from global vault, see https://github.com/dust-tt/dust/pull/7537


Connecting to remote server api.interfaces.records.teams.microsoft.com failed with the following error message

I am using this command to connect Microsoft Teams through PowerShell 7.1.3 OR PowerShell  5.1.
Step 1
Connect to first domain<EMAIL_ADDRESS>Import-Module MicrosoftTeams
$userCredential = Get-Credential
Connect-MicrosoftTeams -Credential $userCredential

Result: Connected Successfully:

Step 2
Hit the command to get online application instance of the tenant:
Get-CsOnlineApplicationInstance
Result: Retrieved all the app instances successfully
Step 3
Connect to second domain<EMAIL_ADDRESS>in the same PowerShell
Import-Module MicrosoftTeams
$userCredential = Get-Credential
Connect-MicrosoftTeams -Credential $userCredential

Result: Connected successfully
Step 4:
Hit the command to get the application instances again:
Get-CsOnlineApplicationInstance
Error Result: Processing data from remote server api.interfaces.records.teams.microsoft.com failed with the following error message:

Now in the above steps, if I use Disconnect-MicrosoftTeams command after step 2, I get the expected result.
I am doing all this through C# .Net and Asp.Net Core. SDK: Microsoft.PowerShell.SDK
Code Snippet
scriptContents.AppendLine("Set-ExecutionPolicy -ExecutionPolicy Unrestricted -Scope Process");
            scriptContents.AppendLine($"$MicrosoftTeamsConnectorPath = Get-Item -Path {microsoftTeamsModulePath}");
            scriptContents.AppendLine("Import-Module $MicrosoftTeamsConnectorPath -verbose");
            scriptContents.AppendLine("Disconnect-MicrosoftTeams");
            scriptContents.AppendLine("$SecureStringPassword = ConvertTo-SecureString $Password -AsPlainText -Force");
            scriptContents.AppendLine("$Credential = New-Object System.Management.Automation.PSCredential -argumentlist
            $UserName, $SecureStringPassword");
            scriptContents.AppendLine("Connect-MicrosoftTeams -Credential $Credential");

            using (PowerShell ps = PowerShell.Create())
            {
                    ps.AddScript(scriptContents.ToString());
                    ps.AddParameters(scriptParameters);

                    ps.Streams.Error.DataAdded += Error_DataAdded;
                    ps.Streams.Warning.DataAdded += Warning_DataAdded;
                    ps.Streams.Information.DataAdded += Information_DataAdded;

                    var pipelineObjects = await ps.InvokeAsync().ConfigureAwait(false);

                  if (ps.Streams.Error.Count > 0)
                    {

                    }
                   else
                    {
                    }
           }

Main Concern/Question:
When I run the application script locally, Steps 1 to 4 works fine by using Disconnect-MicrosoftTeams but it does not works when I host it on Azure App Service.
Error on Application Insight:

What is the best way to remove the previous MicosoftTeams session (step 1 to 2) so that step 3 to 4 would work?
Is there anything I am missing while deploying it to Azure app service?
Note: I want the PowerShell to work for multiple domains with Microsoft Teams module commands like Get-CsOnlineApllicationInstance when hosted as a .NET core OR .NET framework web API on Azure App Service
Any help would be appreciated?

@yogkumgit Hi Do you have any update on this?

Hi @DEberhardt
I saw that you have similar issue as posted on this issue 7058. You mentioned to cleanly closing existing sessions. And I think the issue I mentioned here is somewhat similar to yours.
Could you please have a look at this issue and let me know what is the way to cleanly close the existing sessions?

I am getting this same error in PowerShell 5.1, using the Get-CSOnlineUser cmdlet from both normal and admin PS shells on Win10.

Hello,
yes, I had the same issue, but that was on v1.1.6 (or v1.1.10-preview) of the Module MicrosoftTeams.
I have no issues on v2.3.1 as the session is created with Connect-MicrosoftTeams.
If you haven't updated to v2.3.1 please do so :)

I opened #7842 as I do have these issues on v2.3.1

@DEberhardt
I am using the latest MS Teams module i.e. 2.3.1
Every things works perfectly when I run the code locally on VS 2019 with Disconnect-MicrososftTeams but it does not work when deployed in Azure App Service.
Seems like previous session of MS Teams is still not closed when sending next request for second tenant. And if I hit the request for first tenant, it works again.
Cross domain is not working when deployed with Disconnect Microsoft Teams.

Interesting.
I have not encountered an issue for this yet on 2.3.1.
Then again, I am using the Windows Terminal and open a new session for each Tenant I need to connect to - keeps it clean and separated as the session can now stay open for longer than an hour (thankfully :D)
I may be able to test this next week somewhen, but the volatility with the session is worrying...

Hello there,
Same issue with Grant-CsTeamsVideoInteropServicePolicy -PolicyName BlueJeansServiceProviderEnabled -Identity $user.UserPrincipalName
I tried with MFA-enabled and non-MFA admin accounts without success.
Get-CsUserPolicyAssignment -Identity $user.UserPrincipalName works though... I don't get it

The issue is around the Session created in the background to the Teams API.
CmdLets using the old SkypeOnline interface will require a PsSession to be created (after using a command you can run Get-PsSession to see it has been created for you).
We seem to be tapping in a bug here with this session. I have written Assert-MicrosoftTeamsConnection to figure out whether the Session was correctly created.
Current Workaround:
Restart PowerShell session and connect from scratch.

Hello @bijaykush how are you? Hope you are doing good.
Here, we are limited to documentation issues, for your inquiry the best would be to open a support ticket directly from your tenant.
Similar issues had already been reported, please see here and here
Hope this information helps you,

The issue is around the Session created in the background to the Teams API.
CmdLets using the old SkypeOnline interface will require a PsSession to be created (after using a command you can run Get-PsSession to see it has been created for you).
We seem to be tapping in a bug here with this session. I have written Assert-MicrosoftTeamsConnection to figure out whether the Session was correctly created.
Current Workaround:
Restart PowerShell session and connect from scratch.

I wish I had known about this module before I wrote my own tooling. Super userful @DEberhardt!

@DEberhardt : Can you please provide some details on how you connect from scratch to PowerShell as you described as Current Workaround?
When I execute Get-PsSession, I get nothing and need to know how to create the session in this case to execute the script that was running before.

from

Thank you @DEberhardt for your suggestion. Does it mean that we need to restart the PowerShell and connect it from scratch programmatically when hosted in Azure App Service?
Because we are facing this issue only when hosted in Azure App service? Locally its working fine i.e. session is being refreshed easily.

The issue is around the Session created in the background to the Teams API.
CmdLets using the old SkypeOnline interface will require a PsSession to be created (after using a command you can run Get-PsSession to see it has been created for you).
We seem to be tapping in a bug here with this session. I have written Assert-MicrosoftTeamsConnection to figure out whether the Session was correctly created.
Current Workaround:
Restart PowerShell session and connect from scratch.

Thank you @DEberhardt for your suggestion. Does it mean that we need to restart the PowerShell and connect it from scratch programmatically when hosted in Azure App Service?
Because we are facing this issue only when hosted in Azure App service? Locally its working fine i.e. session is being refreshed easily.

To elaborate, I am using a PowerShell window, ISE or the new Windows Terminal to create a session (Connect-Me if you fancy using TeamsFunctions :)) - I have to close the window to re-initialize the session when running into this issue.
That said, I have not had it myself since updating to MicrosoftTeams v2.3.1
It may also be influenced by the connection method. I myself always use the -AccountId when connecting.

@get-itips Thank you very much for the contribution and sharing this explanation. @bijaykush Hope this comment is helpful for you. Considering the nature of the issue, as advised, please open a service ticket in your tenant and follow with them for the resolution. We proceed here to close it.
We will be very happy if you can share the outcome or resolution with us if you see documentation update is required. We will certainly update this documentation with that valuable information. Thanks again, for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


Add a license

You guys really need to pick a license if you're going to make something this important (payment processing)

Thanks suggesting this, we have added license to this plugin.


SolanaExtension is not a constructor when using @magic-ext/solana in react-native

✅ Prerequisites

[x] Did you perform a cursory search of open issues? Is this bug already reported elsewhere?
[x] Are you running the latest SDK version?
[x] Are you reporting to the correct repository (magic-sdk)?

🐛 Description
When attempting to use @magic-ext/solana in a build of React Native the build will error out with the following error:
SolanaExtension is not a constructor

🤔 Expected behavior
When using this exact same import scheme in regular web the Magic object is able to be initialized with no errors.
😮 Actual behavior
We see the following warning:

Screenshot of the error:

This is most likely due to some issue with the fact that index.native.js is referencing itself and is not importing correctly. We can see this issue happening in this stack overflow issue
💻 Code Sample
import {Magic} from '@magic-sdk/react-native';
import {SolanaExtension} from '@magic-ext/solana';

  const magic = new Magic('pk_live_xxxxx', {
    extensions: [
      new SolanaExtension({
        rpcUrl: 'https://api.devnet.solana.com',
      }),
    ],
  });

🌎 Environment

Software
Version(s)

@magic-sdk/react-native
7.0.0

@magic-ext/solana
3.1.0

Browser
react native

yarn
1.22.17

Operating System
ios

Note:  Manually changing export * from './index' => export { SolanaExtension } from './index.js'; fixes the issue

:rocket: Issue was released in<EMAIL_ADDRESS><EMAIL_ADDRESS>:rocket:


SD card not found

Hello,
i tried to get the message format of my Nano PK.
But the controller always tells me, that no SD card was found.
Do not all controllers support SD cards?
Any specific size or format to use?
Thank you.

here too, but it still works for me... insert the card, set the date and time to 23:59 and wait around 2 minutes (force the system to write a new dataset)


Fix setting GridContainer content by index

resolves #3657
The problem is that an array does not notify about changing its elements.
This PR adds a GridContainerContent class which wraps a jagged array and provides notifications for its elements changes.

Awesome, but this is a pretty large breaking change. Is it possible to have an implicit operator conversion from Drawable[][] to GridContainerContent?

Is it possible to have an implicit operator conversion from Drawable[][] to GridContainerContent?

AFAIK it is not possible to convert an array to a custom object.  However, I can write an extension method in order to make code a little cleaner.

Vice-versa would also be good to have (GridContainerContent -> Drawable[][], even if it requires allocs).

We can expose the original array via method or property. See https://github.com/UselessToucan/osu-framework/commit/f5b3f9205a8beaa847e392563fc4342703eb2e3d.

AFAIK it is not possible to convert an array to a custom object. However, I can write an extension method in order to make code a little cleaner.

I think the suggestion was to add operators like
public static implicit operator Drawable[][](GridContainerContent content);
public static implicit operator GridContainerContent(Drawable[][] drawables);

and it seems to at least not throw syntax errors and build? This way the changes to Content should no longer be breaking, or am I missing something?

Unfortunately this is still a breaking change, albeit a slightly less breaking one - game-side there's this usage that needs adjusting for.


Refactor Writer.renderTokens() for better readability.

Hi,
PR for #411. It splits the old Writer.renderTokens() into several small functions with a single responsible.
Also removed a lengthy case-switch which quickly gets error prone.
Any thoughts?

Seems the alternative case-switch added a measurable performance hit :( I'll see what I can do with it.

Keep us updated!, and thanks for the work! :)

Any update @phillipj?

Sorry @dasilvacontin, forgot to push some local changes.. By doing a more similar if-else style comparable to the old switch-style, the performance penalty disappeared.
Would you considered it different enough to see any value in this refactoring?

No worries, I was just curious! :) It definitely looks cleaner. I will take a better look tonight!

:+1:

Oups, commits were not squashed.  I have to be extra-careful about that next time.


Write security system, for protecting users from RCE.

We need to fully define the different security levels. Currently the possible run-types are: (in order of safety)

Standard Library
Local Filters
Online Filters

Local is dangerous cause somebody can say "please put this here, and then run X". Its safer than online filters though, because the user at least has to handle the source, and could peek inside.
Online filters could also be compromised, which is why we cache by default, and require a regolith install --force (or another command -syntax isn't 100% decided yet) to flush them + redownload.

We need to make the user agree to some kind of "I understand the risks" clause. Of course, we cannot just store this inside of the regolith.json, because then somebody could simply have it pre-checked (like the MC server EULA).
We should instead look into storing the "regolith safety level" somewhere else.

Closed via #96


"thumbor" storage

Hi, i'm trying create new shrine storage for Thumbor. I try implement basic class as described in documentation (http://shrinerb.com/rdoc/files/doc/creating_storages_md.html).
Thumbor use REST API for posting images and constructed URLs for geting images.
I want send image to thumbor server with RestClient.
I have little success (because my lack of experience with advanced ruby coding). Maybe there is better way?
And one question. Why is storage upload method called twice? First time with io = ActionDispatch::Http::UploadedFile object and second time with io = MyUploaderClass::UploadedFile?
Thanks for advices.
Juraj

I understand now - first time is called upload to cache and second time move to store.
For now i get this code - partialy working - but model.image.url return nil.
require "shrine"
require "down"

class Shrine
  module Storage
    class Thumbor
      def initialize
        @thumbor_base_url = 'https://img.uid.is'
        @thumbor_api      = "#{@thumbor_base_url}/image"
      end

      def upload(io, id, shrine_metadata: {}, **upload_options)
        # uploads `io` to the location `id`, can accept upload options
        slug      = shrine_metadata['filename']
        mime_type = shrine_metadata['mime_type']

        response = RestClient.post(
          @thumbor_api,
          io.read,
          {
            'Content-Type' => mime_type,
            'Slug' => slug
          }
        )

        id.replace(response.headers[:location])
        shrine_metadata.merge!({location: response.headers[:location]})
      end

      def url(id, **options)
        # returns URL to the remote file, accepts options for customizing the URL
        binding.pry
        "#{@thumbor_base_url}#{id}"
      end

      def open(id)
        # returns the remote file as an IO-like object
        Down.open("#{@thumbor_base_url}#{id}")
      end

      def exists?(id)
        # checks if the file exists on the storage
      end

      def delete(id)
        # deletes the file from the storage
      end
    end
  end
end

You definitely got the main points figured out 👍
Could you please repost this code on the Shrine Google group, so that we can talk about it further there, as I prefer to use GitHub issues only for bug reports (I definitely have a few tips to share) 😉


style(front): 置文件下发详情页面中展示详细的输出格式信息 (close #110)

Codecov Report

Merging #119 (bd75cff) into v1.0.9-rc (a6039f8) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           v1.0.9-rc     #119   +/-   ##
==========================================
  Coverage      53.77%   53.77%
==========================================
  Files            180      180
  Lines           8731     8731
==========================================
  Hits            4695     4695
  Misses          4036     4036

Continue to review full report at Codecov.

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


NextJs's Link components do a full refresh

Hi again,
somehow the NextJs Link components do a full refresh, default NextJs applications does not have this behavior.
Not sure if that behavior is due to krabs.
In my case, I have the following setup
const navigation = [
  { name: 'Immobilien', href: '/real-estates', icon: FolderIcon, current: false },
  { name: 'Documents', href: '/documents', icon: InboxIcon, current: false },
  { name: 'Exports', href: '/exports', icon: ChartBarIcon, current: false },
]

    {navigation.map((item) => (
      <Link
        key={item.name}
        href={item.href}
        aria-current={item.current ? 'page' : undefined}
      >
        <a>
          <item.icon
            aria-hidden="true"
          />
          {item.name}
        </a>
      </Link>
    ))}

It's doing a full refresh 'cause you're using getInitialProps in your _app.js file right?

Yes.

App.getInitialProps = async ({ Component, ctx }) => {
  const tenant = ctx?.req?.tenant?.name;
  let pageProps = {};

  if (Component.getInitialProps) {
    pageProps = await Component.getInitialProps(ctx);
  }

  return {
    pageProps: {
      ...pageProps,
      tenant,
    },
  };
};

export default App;

Using getServerSidePropsaswell as getStaticProps has the same effect.
Could you provide an example on how to solve this?

By using getInitialProps in your _app.js file, you require a full SSR for each page in your application. As for now, there's no way to avoid this behavior, but I have a suggestion: use a CDN such as Akamai or Cloudflare for caching your pages after the first render, and use their APIs for invalidating the cache manually or time-based (just like an "enhanced" ISR).
If you feel like wrapping your application behind a CDN is a bit too much, maybe Krabs it's not 100% needed 🙂 it is supposed to work on large-scale projects where a good caching layer is required anyway!
PS. I'm currently running Krabs in production on a two-domain application, and even if I SSR every single page, its performances (cache apart) are outstanding, and that's because Next.js is really well made.


[EventRequest] SalesTaxCalculate.Codeunit.al (codeunit 398 "Sales Tax Calculate")

Hi MS,
Please help us in migrating our verticalized solution by adding below events in SalesTaxCalculate.Codeunit.al codeunit.
Standard Code(Screenshot from DistTaxOverPurchLines function)

Modified Code

Event Signature

Thanks
SUD

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.

Hi There,
In requested event Amount should be passed as parameter as above.
Kindly update!!
Thanks
SUD

Please create a new request.  Don't forget to mention the precise name of the object and the event.
Please always put all details in text instead of screenshots.


WIP: made the name of tap_schema.tables unique by fully qualifying them.

This should be sufficient.
Updating the name at this place will catch the signals when updating metadata and calling rebuild_tap_schema.

It seems that it does the job.
table name in TAP_SCHEMA is fully qualified

On gaia-test-instance:
SELECT table_name FROM gaia_tap_schema.tables WHERE table_name LIKE '*gaia_source'

returns: 'gaiaedr3.gaia_source'

An update of the metadata also properly update the TAP_SCHEMA.

setting a table/schema public/private add/remove the entry from TAP automatically

The TAP service continue working as usual:

all instance-tests pass

[ ] unittests
[ ] instance-tests (dq-dev + test-app)
[x] gaia test (dq-dev + gaia-app)
[ ] rave test

Should work, after CI merge, let's see the tests.


Any tips on responsive layout / adaptive layout

jQuery also has lots of plug-ins for adaptive/responsive layouts. So to resize DOM elements and fonts to fit different screen resolutions.
Maybe you can add tips on how to do a responsive layout / adaptive layout natively, maybe using just CSS? I found this article quite helpful.

Well we can't completely remove media query. But we can minimize media queries. and for responsive flex is best option with VW for font. Because flex give more freedom then using css framework.
Also, VH and VW units can cause issues on iOS devices.


pascal source recognized as json filetype

A pascal source file can be assigned a json type for syntax highlight
if the first line of a pascal source file is a lone { (open comment) then micro
thinks the file is json and not pascal.
circumventing by adding a blank line works, but it's wrong.
demo.txt
Specifications
Commit hash: 225927b9
OS: Windows 11
Terminal: Windows Terminal

It's already fixed with #2819, but the current maintenance is unfortunately slowed down by the lack of free time of the project owner.

Thanks, I tried some searching for issues but didn't find it. No worries on delays from me!

Meant to close.


[SPARK-39997][SQL] Fix ParquetSchemaConverter fails match schema by id

currently, match parquet schema by id fails under certain case
no
new unit test added
What changes were proposed in this pull request?
in this PR, fixed cases where ParquetSchemaConverter fails match schema by id
when converting parquet schema, SparkType is preferred instead of Converted parquet type, chances are SparkType has a name which will then fail the same type validation in later cases when running vectorized nested column read.
Why are the changes needed?
when converting parquet schema, SparkType is preferred instead of Converted parquet type, chances are SparkType has a name which will then fail the same type validation in later cases when running vectorized nested column read.
Does this PR introduce any user-facing change?
no
How was this patch tested?
added new ut

Can one of the admins verify this patch?

cc @sunchao

guess this isn't the fix intended after sunchao commented the spark type is intended for maintaining type precision, but here the spark type is carrying the name c1 which is renamed from c0 so carrying it forward to later phases will cause same type validation errors.


Remove version: igoogolx.lux version 1.3.0

This version is older than what has been set in max-versions-to-keep by the publisher.
Microsoft Reviewers: Open in CodeFlow

URL: https://github.com/igoogolx/lux/releases/download/v1.3.0/lux-1.3.0+1.3.0-windows-setup.exe
OK
(Automated message - build 882)


Log exception and re-throw

Fixing bug #852.
When running under vstest.console.exe, exceptions were swallowed. We should log it out and re-throw.
Repro:
"C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\CommonExtensions\Microsoft\TestWindow\vstest.console.exe" MyProject.njsproj
Expected:
Microsoft (R) Test Execution Command Line Tool Version 14.0.25123.0
Copyright (c) Microsoft Corporation.  All rights reserved.

Starting test execution, please wait...
Error: The imported project "C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v11.0\Node.js Tools\Microsoft.NodejsTools.targets" was not found. Confirm that the path in the <Import> declaration is correct, and that the file exists on disk.  C:\Users\JohnDoe\Source\Repos\MyProject\MyProject.njsproj

Actual:
Microsoft (R) Test Execution Command Line Tool Version 14.0.25123.0
Copyright (c) Microsoft Corporation.  All rights reserved.

Starting test execution, please wait...

Hi @compulim, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. Real humans will now evaluate your PR.

 Fixed and squashed into a single commit.


Fix Cors default_allow_origins() and add allow_credentials

"any" wasnt parsed correctly, the "*" wildcard is recognized by tower

@edg-l looks like this triggered a parsing failure -- it says that it prefers "any" rather than "*", so I've reverted back to "any" in a different PR
could you elaborate on how you arrived at this fix?


Request path contains unescaped characters

I am trying to make a simple GET request to a website : https://www.crunchbase.com/location/belgrade/2a22cd01619e1ff39394303b255670cb?utm_source=crunchbase_tc_river&utm_medium=export&utm_campaign=dataset
I get an error such as this :
throw new TypeError('Request path contains unescaped characters.');
    ^

TypeError: Request path contains unescaped characters.
    at new ClientRequest (_http_client.js:53:11)
    at TunnelingAgent.exports.request (http.js:31:10)
    at TunnelingAgent.createSocket (/usr/lib/nodejs/tunnel-agent/index.js:117:25)
    at TunnelingAgent.createSecureSocket [as createSocket] (/usr/lib/nodejs/tunnel-agent/index.js:184:41)
    at TunnelingAgent.addRequest (/usr/lib/nodejs/tunnel-agent/index.js:80:8)
    at new ClientRequest (_http_client.js:137:16)
    at Object.exports.request (http.js:31:10)
    at Object.exports.request (https.js:181:15)
    at Request.start (/usr/lib/nodejs/request/index.js:607:30)
    at Request.end (/usr/lib/nodejs/request/index.js:1235:28)

Is there any fix to check if the url is compatible to be sent in the request function as a paramater ? I am using<EMAIL_ADDRESS>and node v5.5.0

Works fine when I do it, using same versions as you:

const request = require('request');

request(
	'https://www.crunchbase.com/location/belgrade/2a22cd01619e1ff39394303b255670cb?utm_source=crunchbase_tc_river&utm_medium=export&utm_campaign=dataset',
	(error, response, body) => {
		if (error) {
			return console.error(error);
		}
		return console.log(body.substr(0, 128) + '...');
	}
);

Can you post your code?

I looked into the actual error.
This error can only occur when you snuck a whitespace into the url, I tried to to this but request always seems to escape those correctly.
You'll have to post a snippet, or try a newer version (yours is quite old) and see if the error persists.

I work behind a proxy server. Your code does not seem to work behind a proxy. I am pasting my code below. Could you please tell me whether this is the correct way of sending a request while working behind a proxy server.
`'use strict';
const request = require('request');
var get_config = function(site_url){
var config = {
url : ((site_url)),
proxy : 'http://:'
};
return config;

};
request(
get_config('https://www.crunchbase.com/location/belgrade/2a22cd01619e1ff39394303b255670cb?utm_source=crunchbase_tc_river&utm_medium=export&utm_campaign=dataset'),
(error, response, body) => {
if (error) {
return console.error(error);
}
return console.log(body.substr(0, 128) + '...');
}
);`
Also an interesting observation is that when I am replacing "https" with "http", the request is working properly.

Your proxy doesn't support https then?

From what I can tell, internally there is some redirect happening, but the redirect seems to have a malformed/bad URL that contains whitespaces, that ticks off this error.
If it is a public proxy, could you please post the info?
If not, please add a breakpoint at "/usr/lib/nodejs/request/index.js:607" and inspect the passed url via any debugger.

Hey @dsaumyajit007
This looks fine and works perfectly with google.com, result after your code snippet.
const request = require('request');

var get_config = function(site_url){
    var config = {
        url : ((site_url)),
        proxy : 'http://proxyurl:proxyport'
    };

    return config;
};
request(
    get_config('https://www.crunchbase.com/location/belgrade/2a22cd01619e1ff39394303b255670cb')
    , (function (error, response, body) {
    	console.log(response.statusCode);
    	console.error(error);
        return console.log(body.substr(0, 128) + '...');
    })
);

For google.com
200
null
<!doctype html><html itemscope="" itemtype="http://schema.org/WebPage" lang="en-IN"><head><meta content="text/html; charset=UTF-...

@sudheesh001 Please note that you might be using a different proxy.
Lets wait for him.

I have a very basic doubt : I am running Node js on Ubuntu 14.04 and on running
node --version
I get v5.5.0 . Is this the most stable release because somewhere I saw that the releases are 0.x.x . Am i using the right version of Node?

Yes, the 0.x releases are from before the iojs/nodejs merge.
v5.5.0 is stable.
I still believe it's just your proxy being weird.

Ok. Any reason why the link works on repacing "https" with "http" ? It fixes this issue somehow

https://github.com/request/request/issues/2046#issuecomment-177941023

Ok Its magically working now. :+1:
I just reinstalled nodejs and the request package. Thanks for all the help @sudheesh001 @SimonSchick

I reinstall request module but it fails after few days to this error agian

I had the same problem, wonder if people complaining here have another language activated in their keyboards? I do have arabic/english. this might takes us somewhere while investigating

I am experiencing this issue on windows (ethernet to home network) but not on macOS (wifi to same network). The http trick does not work for me.

axios.get(encodeURI(url)).then( data => { })

在kubernetes环境使用request发送get请求，url中携带中文参数时会发生这个错误，在其他环境则不会


operationsSorter ?

I would like to be able to change sort of actions within action groups. Right now actions are sorted by alpha which results in all verbs get/put/post/delete mixed up. I would like to be able to control that so that maybe gets are first then posts, puts, deletes. Doesn't swagger-ui already support it via operationsSorter? If so how do I get to this setting?

For the next major release of Swashbuckle (6.0.0 targeting AspNet 6), I'm going to remove the C# interface for customizing swagger-ui settings. Instead, the recommended approach for customizing the UI will be to provide your own version of index.html. There, you can customize the UI as described in the swagger-ui documentation - https://github.com/swagger-api/swagger-ui#swaggerui
.
So, with this being the approach going forward, I'm not going to add any additional settings to the current version. To resolve your issue right now, you can inject your own version of index.html as described here - https://github.com/domaindrivendev/Swashbuckle#provide-your-own-index-file.