Rename for the view. Prepare a query for this.

-- Step 1: Retrieve the view definition and store it in a variable
SELECT VIEW_DEFINITION
INTO @view_definition
FROM information_schema.views
WHERE table_schema = 'neup_accounts' AND table_name = 'oldView';
-- Step 2: Construct the CREATE VIEW statement for the new view
SET @newViewSql = CONCAT('CREATE VIEW newView AS ', @view_definition);
-- Step 3: Prepare and execute the CREATE VIEW statement
PREPARE stmt FROM @newViewSql;
EXECUTE @newViewSql;
DEALLOCATE PREPARE stmt;
-- Step 4: Drop the old view
DROP VIEW oldView;
Description
Something like this was to work.
But it seems some error in the code.

Probable solution (generates string)
SELECT VIEW_DEFINITION
FROM information_schema.views
WHERE table_schema = 'databaseName' AND table_name = 'oldView';
Description
This is another probable solution but didn't worked.
This was my approach,
CREATE VIEW newView as
SELECT VIEW_DEFINITION
FROM information_schema.views
WHERE table_schema = 'databaseName' AND table_name = 'oldView';

Delegate for future upon the completion of this project other ways.


clusterctl describe shows stale information

What steps did you take and what happened:
While testing #54, I noticed the status posted by clusterctl describe has stated information even though the tenant cluster was successfully formed:
$ cluster-api/bin/clusterctl --kubeconfig kubeconfig.yaml describe cluster workload-cluster -n test-dda2dda

NAME                                                                 READY  SEVERITY  REASON                       SINCE  MESSAGE
/workload-cluster                                                    True                                          57m
├─ClusterInfrastructure - KubevirtCluster/workload-cluster           True                                          60m
├─ControlPlane - KubeadmControlPlane/workload-cluster-control-plane  True                                          57m
│ └─Machine/workload-cluster-control-plane-9wn55                     True                                          57m
└─Workers
  └─MachineDeployment/workload-cluster-md-0                          False  Warning   WaitingForAvailableMachines  60m    Minimum availability requires 1 replicas, current 0 available
    └─Machine/workload-cluster-md-0-776c5bf974-x2c62                 True                                          56m

What did you expect to happen:
There should be no warning.
Anything else you would like to add:
N/A
Environment:

Cluster-api version: v0.4.5 == 65f95147d52abface1778dd426ad948999cbac7b
Cluster-api-provider-kubevirt version: 353694f61daecb3e4c4ea78d13477a2fc209a4a5
Kubernetes version: (use kubectl version):
Server Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.7", GitCommit:"1dd5338295409edcfff11505e7bb246f0d325d15", GitTreeState:"clean", BuildDate:"2021-01-13T13:15:20Z", GoVersion:"go1.15.5", Compiler:"gc", Platform:"linux/amd64"}
KubeVirt version: v0.38.0
OS (e.g. from /etc/os-release):

NAME="CentOS Linux"
VERSION="7 (Core)"
ID="centos"
ID_LIKE="rhel fedora"
VERSION_ID="7"
PRETTY_NAME="CentOS Linux 7 (Core)"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:centos:centos:7"
HOME_URL="https://www.centos.org/"
BUG_REPORT_URL="https://bugs.centos.org/"

CENTOS_MANTISBT_PROJECT="CentOS-7"
CENTOS_MANTISBT_PROJECT_VERSION="7"
REDHAT_SUPPORT_PRODUCT="centos"
REDHAT_SUPPORT_PRODUCT_VERSION="7"

/kind bug

Umm... One thing can be that you didn't mention replicas, like you need to use minimum 1 replica. Another one can be for the device that you are one, it might not have the capacity for the process. So, you might try using a cloud platform for this. Maybe just a suggestion.


i tried installing ipopt in my mac facing the issue:mumps is trying to use 'depends_on :mpi' but it should be "open-mpi";

Please note we will close your issue without comment if you delete, do not read or do not fill out the issue checklist below and provide ALL the requested information. If you repeatedly fail to use the issue template, we will block you from ever submitting issues to Homebrew again.

[yes ] are reporting a bug others will be able to reproduce and not asking a question. If you're not sure or want to ask a question do so on our Discourse: https://discourse.brew.sh
[ yes] ran a brew command and reproduced the problem with multiple formulae? If it's a problem with a single, official formula (not cask) please file this issue at Homebrew/homebrew-core: https://github.com/Homebrew/homebrew-core/issues/new. If it's a brew cask problem please file this issue at https://github.com/caskroom/homebrew-cask/issues/new. If it's a tap (e.g. Homebrew/homebrew-php) problem please file this issue at the tap.
[ yes] ran brew update and can still reproduce the problem?
[ yes] ran brew doctor, fixed all issues and can still reproduce the problem?
[ yes] ran brew config and brew doctor and included their output with your issue?

To help us debug your issue please explain:

What you were trying to do (and why) : i was trying to install ipopt for my udacity Mpc project.
What happened (include command output): while install mumps is trying to use 'depends_on :mpi' but it should be "open-mpi";
What you expected to happen: download ipopt
Step-by-step reproduction instructions (by running brew commands)
i tried installing brew using :
brew install dpo/openblas/ipopt

Features
Please replace this section with:

a detailed description of your proposed feature
the motivation for the feature
how the feature would be relevant to at least 90% of Homebrew users (if it's not: do not open a feature request)
what alternatives to the feature you have considered

We will close this issue or ask you to create a pull-request if it's something the maintainers are not actively planning to work on.

brew install dpo/openblas/ipopt

Report this there (as the error told you to)


Fix the Readme so that it has valuable information

I want to see a better title, description and maybe a roadmap

I'm working on this issue

Included in the prerelease v0.0.1-alpha


Hide UIToolbar or UIView when scrolling?

I want to add a UIView to the bottom of my UIWebView. How would i hide it (move down) when scrolling?

Hey @londonbridges13
The easier way would be to tap in the delegate methods of the nav controller:
func scrollingNavigationController(_ controller: ScrollingNavigationController, didChangeState state: NavigationBarState) {
    switch state {
    case .collapsed:
        print("navbar collapsed")
    case .expanded:
        print("navbar expanded")
    case .scrolling:
        print("navbar is moving")
    }
}

Thank you


Set up all.r to work with new models

The base will be 55 and the bridge and sensitivity models will be in the same relative order as before

This is done, but note if you merge now, the models 55-70 must be on your machine or the doc will no longer build.

So don't merge with Chris yet!! Unless you know the fancy git commands to revert files.


Service Unavailable when going to /auth/settings

Describe the issue
I get a Service Unavailable message from the auth portal when visiting /auth/settings and logged in via oauth with the authp/admin role
Configuration
Paste full Caddyfile below:
*.secure.domain.com {
			route /auth* {
			authp {
				cookie domain .domain.com
				crypto key sign-verify REDACTED
				backends {

					google_oauth2_backend {
						method oauth2
						realm google
						provider google
						client_id REDACTED
						client_secret REDACTED
						scopes openid email profile

					}
				}

				transform user {
					exact match email<EMAIL_ADDRESS>					action add role authp/admin

				}

			}
		}

		route {
			redir https://{hostport}/auth 302
		}
	}

Version Information
Provide output of caddy list-modules -versions | grep auth below:
http.authentication.hashes.bcrypt v2.4.3
http.authentication.hashes.scrypt v2.4.3
http.authentication.providers.http_basic v2.4.3
http.handlers.authentication v2.4.3
http.authentication.providers.jwt v1.3.13
http.handlers.authp v1.4.17

Expected behavior
Describe expected behavior.
I am wondering if it expected to receive a Service Unavailable from the auth portal when navigating to the /auth/settings endpoint. Is that because I am already using oauth as opposed to the form based auth?
Additional context
I cannot find anything in the logs that say why it is doing this. I have only experienced this after updating to the rewritten plugin. Thank you for your help!

@sandstormkeshav , this is expected behavior, because OAuth2.0 backend does not support settings. The local backend has settings.
Why do you need settings with OAuth2.0?

Hi @greenpau, you are right, I just wanted to make sure I wasn't missing something. Thank you!


mergeTwoArrays.java

*Merging two arrays using the manual method:
-First, we calculate the lengths of both the arrays and add the lengths.
-Then create a new array with the length as the sum of lengths of these two arrays.
-Now we just start adding the elements of each array in the resulting array.
#79

Hi Dear @RakeshKumar13011
Great code
Thanks for your contribution......
Show your support on my youtube channel web Pixar(The institute of coding)
like , share , subscribe
Youtube - https://youtu.be/5qnQjgdpFPg
Telegram-channel - https://t.me/WebPixar
Join our telegram channel for more goodies , swag packs.
You can also join - https://devfolio.co/signup?ref=33d4a02bef
And search for - HackNITR 3.0
There is too  many rewards..


Did it take almost half an hour to load the model inference weights? Is it my problem?

Loaded for me in around 30seconds


Add workflow input with CommandInputEnumSchema

Add workflow input with CommandInputEnumSchema.

Some type checking would be desirable. This is, however, complicated...


Update port_in_use.json

Added instructions for how to see used ports in Linux
Added the specific parameter for the server.properties file

Thanks for the pull request!


AT-2.1: Inventory manager creates an inventory manager account

Test Case ID: AT-2.1
User Story: ALTA-2.1 (#42)
As an inventory manager, I want to be able to create a user account for another inventory manager so that I can provide access to initiate audits.
Acceptance Criteria
Given that the user is logged in as an inventory manager,

The user should be redirected to their affiliated organization's Dashboard page.

The user selects the Employees side menu option and is presented with a table displaying the organization's employee accounts as well as a Create button.

The user selects the Create button to display an empty form for the user to input the new user’s information.

Once the form is complete, the user submits the data by clicking the Save button. The user is then redirected back to the table to validate the creation of the user.

Accepted - but when creating a stock-keeper, disable the option to set a password


No loop rule significantly reduces the application performance on big diagrams

Describe the bug
The diagram from the support ticket makes the application unresponsive, and this is due to the linting (no-loop rule).

Steps to reproduce

Open the diagram from the support ticket
now this happens

Expected behavior
The linting should not slow down the application significantly.
Environment

OS: MacOS
Camunda Modeler Version: 5.23.0, current nightly
Execution Platform: [e.g. Camunda 7, Camunda 8]
Installed plug-ins: [...]

Additional context
SUPPORT-22488

Ideas:

Run linter in a worker (difficult because we need to pass the model)
Limit the number of elements tested for the no-loop rule

The rule is implemented in https://github.com/camunda/bpmnlint-plugin-camunda-compat/blob/main/rules/camunda-cloud/no-loop.js

Let's attempt to solve this in an algorithmic manner first. I suggest anyone picking to check the following (or other) resources:

Solving using depth first search
Solving using topological sorting


overall confusion on requirements and usage

What are the requirements for running the marathon-lb as a docker container via Marathon/Mesos?  Are any special docker permissions required or special paths that need to be mounted from the host? It seems to require access to run iptables. Is this correct?
Is the haproxy web ui exposed?
Thanks

the haproxy stats can be accessed via: :9090/haproxy?stats by default
an minimal example for marathon config can be:
{
    "id": "/marathon-lb",
    "cpus": 1,
    "mem": 128.0,
    "instances": 1,
    "container": {
        "type": "DOCKER",
        "docker": {
            "image": "mesosphere/marathon-lb:v1.0.1",
            "network": "HOST",
            "forcePullImage": false
        }
    }
}

I haven't tried it with Docker 1.10 yet so i cannot tell if you have to apply custom seccomp rules. I'd say you don't have to.

@pgraemer Thanks for the reply.  In my test, I was using bridged networking. I'll give it a try using HOST networking.  I don't think that would allow the container access to IPTables though and I can see it's trying to modify IPTables rules here: https://github.com/mesosphere/marathon-lb/blob/master/service/haproxy/run#L20

looks like i missed some changes in the current master.
have you tried using privileged mode? see README
i updated my last comment.

I read that but completely missed the part about privileged mode with blue/green deployments.  Thanks for pointing it out.

Got things working.  I needed to add privileged mode, use HOST networking, and in my AWS environment, I had to make sure the public IPs of the mesos slaves could all communicate with each other over the public IP.
Thanks again for your help.


OneWayToSource

This document does not mention "OneWayToSource". Has this feature been deprecated or deleted? I use this mode and am having trouble due to the nature of the "ConvertBack" function. I can't figure out how the framework sets the value parameter of this function. From observation, it appears to set this parameter to the default value for the Target type, rather than the actual Target value. This gets converted to the Source type by ConvertBack and ultimately results in ignoring the initial value of both the Source and Target objects. The documentation for ConvertBack, in fact, says: "Modifies the target data before passing it to the source object. This method is called only in TwoWay bindings." I suppose, by extension, based on the elision of OneWayToTheSource from the documentation, that I should expect it to also apply to OneWayToTheSource.
If the gist of my observation is meaningful, might I ask how this is useful? I have no idea how to decide which end of a TwoWay binding should the common (at least, equivalent) value to be shared after the binding operation, but I know that the current situation is dead wrong for the OneWayToSource mode.
Just to set some perspective, I am doing the binding in code, not in XAML.

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

ID: 53f752d7-062a-4935-02c6-48371c208792
Version Independent ID: daa135bb-7f77-3e62-05da-b18a9bfcdf12
Content: Data binding in depth - Windows UWP applications
Content Source: windows-apps-src/data-binding/data-binding-in-depth.md
Product: uwp
GitHub Login: @knicholasa
Microsoft Alias: nichola

Thanks for reaching out with your feedback. Comments left here are meant for documentation feedback, and unfortunately we cannot provide technical support. I will follow up about that topic you mentioned that is missing from the docs, but in the mean time you may have success posting your question in the developer support forums, where other developers and Microsoft engineers can be found. The community there is quite responsive.

After investigating I have a follow up. This article is about UWP data binding, which you’ll find in the Windows.UI.XAML.Data namespace. The UWP BindingMode enum does not have the OneWayToSource value, which is why the article doesn’t talk about it. I'll update the language on the page to make this more clear.


[Carry #818] Trustpinning debug

Carries #818, and I added a follow-up commit with review feedback.
@dnwake thank you for the original contribution! :)
Closes #817

LGTM!  Thanks for following up on this @riyazdf and for your original contribution @dnwake!

LGTM


widgetSizeProvider does not work on deployment

When deployed on the web (gitlab pages), synopsis texts have a size of 100px by 100px, which come from the default of the widgetSizeProvider.
Deployment: https://zivgitlab.uni-muenster.de/SCDH/doering-4esra/esra-demo
Version: 0.5.3
Analysis: The Event handler in the widgetSizeProvider does not catch window initialization event.
Here is a console log, filtering "widget".
adding event listener for widget-size-consumer event index-ff6cf8bd.js:159:2752
initializing widget with  0 index-ff6cf8bd.js:159:761
initializing widget with  0 index-ff6cf8bd.js:159:761
initializing widget with  0 index-ff6cf8bd.js:159:761
initializing widget with  0 index-ff6cf8bd.js:159:761
...

Here is the log for the example synopsis.html, run with npm run dev:
adding event listener for widget-size-consumer event widget-size-provider.ts:90:20
initializing widget with  0 window-mixin.ts:233:9
handling window initialization widget-size-provider.ts:100:10
recalculating dimensions of 1 children widget-size-provider.ts:61:16
initializing widget with  0 window-mixin.ts:233:9
handling window initialization widget-size-provider.ts:100:10
recalculating dimensions of 2 children widget-size-provider.ts:61:16
initializing widget with  0 window-mixin.ts:233:9
handling window initialization widget-size-provider.ts:100:10
recalculating dimensions of 3 children widget-size-provider.ts:61:16
...

mentioned in commit fb3464c6b17f9d222496b19277dc23b181e54bed

Registering the event handler as early as possible, i.e. in the constructor, does the trick.
closed by 6b1c15f9471c2cf05466d456575be838b42bfb40 and 6f0b3d0489f2849d517d9fae07f1bd186d826bcd.

added 45m of time spent

May be related to https://github.com/lit/lit-element/issues/658


Multiple data states to same assignment (seal)

Hi @dr-orlovsky,
I would like to share a strange behavior during my tests with UDC.
In the contract creation step, I am adding two different allocations to the same seal because the UDC allows one or many tokens in the contract.
However, I could not do this because the Builder stores the allocation data in a hashmap, using the seal as the key. That is, the last allocation always overwrites the first.
This is a particular case for UDC because this does not occur in other contracts, as fungibles, because we add a single value.
I considered modifying the Builder to support a set of data states instead of a single data state per seal.
What do you think?

I think we can utilize seal blinding factor to generate distinct seals for the same UTXO

I think we can utilize seal blinding factor to generate distinct seals for the same UTXO

Ok, great!
I will trying implement this ideia in the next week.

I am closing the issues since I believe that the seals must always have a distinct blinding, and thus this is a non-issue and rather an answered question. If there were no way to create seals with different blinding, that would be a bug and you would be welcome to open a new issue for that bug.


[Feature] Remote URL Support

Hi.I didn't find any parameter about remote host file transfer, this requirement is somewhat helpful for my work,  is there any plan for development?

Where is the remote file? If it's on S3 or HDFS, broker Load can be used directly. If it's in another location, you are welcome to contribute to this feature.

Sorry for the ambiguity:Remote Local Files.Another location is optional,OpenDAL may be useful.But I'm not sure if their GO package is available.If I have time, I will do it.


Add on:change event to Input Chip

Describe what feature you'd like. Pseudo-code, mockups, or screenshots of similar solutions are encouraged!
Forward the on:change event up from the hidden Select element within input chip.
What type of pull request would this be?
Enhancement
Any links to similar examples or other references we should review?
Discord discussion:
https://discord.com/channels/1003691521280856084/1072647119581757563/1072647119581757563

The following is my response to the user that originally reported this on Discord: @jpcafe

I was looking to implement the change (above) - however I've ran into an interesting quirk with event forwarded in Svelte. That being, you can't forward events like on:change on elements that don't have user interaction. Given the <select> is hidden within component, users never directly click or touch the element, so the on:change event is not fired.
We can dispatch custom event's when chips are added/removed, but we already have on:add and on:remove. I know you were having issues with this from this thread, but adding a dispatched on:change event would fire at the same time, in the same way as the individual events. This doesn't just make it redundant, but it also means it would be subject to the same issue you reported above.
I'm not really sure how to proceed here. If my other suggestions (to use the event response data in the even handler doesn't work)
Generally speaking, this is a Svelte issue more than a Skeleton issue:

We have a hidden select element within a component to control form state
We provide our own custom UI - the chips UI - which interacts with the select element state
When listening to the update events against this feature, there appears to be a race condition issue where the Select element state is updated slightly behind (both?) the event response data, and the bind value itself.

I'm not sure a fix is possible on our end, but I welcome ideas from others here.


cant load the mnist dataset

i try to load the mnist dataset by writing :
from keras.datasets import mnist
(x_train,y_train),(x_test,y_test)=mnist.load_data()
but i get the following error :
IOError: CRC check failed 0xc187cf56L != 0x14c5212fL
how can i fix this error??

i also tried to mnist.py in my keras datasets directory to download the dataset but i get the following error :
ValueError: Attempted relative import in non-package

rm ~/.keras/datasets/* and retry.

i did that it starts to download the dataset but i get  this error  :
raise IOError(errno.EBADF, "read() on write-only GzipFile object")
IOError: [Errno 9] read() on write-only GzipFile object
thank you for helping

For OSX 10.11.3 using Python3.6, here's what worked for me. To the top of
/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/keras/utils/data_utils.py

just below the import statements, add:
import requests
requests.packages.urllib3.disable_warnings()
import ssl

try:
    _create_unverified_https_context = ssl._create_unverified_context
except AttributeError:
    # Legacy Python that doesn't verify HTTPS certificates by default
    pass
else:
    # Handle target environment that doesn't support HTTPS verification
    ssl._create_default_https_context = _create_unverified_https_context

Restart Python and it will hopefully work

@dderiso 's code change worked for imdb dataset too

@dderiso worked for me.. Thanks

Thank @dderiso it work for me.

nice. I've done it and my VM bricked. hahahahahaha What the hell...
I found the file data_utils.py and copied the code insertion. After reboot the system, it won't boot anymore...


Check write permission for output locations

Annoyingly this relies on having delete permission (to delete the temp file once created) but I couldn't find any other way to achieve this check. Pretty sure there are cases where delete is already needed anyway when we overwrite certain output files.

Why don't we just call it metadata.json, put some metadata about the video in it and then leave it there

@thomshutt could you take another look? thanks


add macOS GUI support, and update README doc

In cleaning up the README, I also noticed that we have a section about a CLA, but no CLA directory. We can probably remove that section? Or at least reword it for contributing without requirement to sign CLA. I can open a separate issue if you like for that.


LVM and LUKS support

RancherOS Version: latest
Where are you running RancherOS? baremetal
Resurrecting https://github.com/rancher/os/pull/1465 but with a focus on only introducing LVM and LUKS support.
The aim would be to enable baremetal and VM based machines to make use of LUKS to prevent data leakage, either through physical access or insecure backup procedures.

All PRs have been merged, you can try master. @bernard-wagner
Also, our QA will help test it out.

Tested with RancherOS version- v1.5.0-rc2
This version supports LVM and LUKS.


What is missing for a new release with the fixes for django 1.10?

currently, I need to use the master branch to use the new style middleware class.
Are there other bugs related to 1.10 that need fixing before we get a new release?

@jsocol issues for a Django 1.10 compatible release are already bundled to milestone 0.12, right?

None of these issues appear to be regressions from 0.11, so even if the current master branch can't claim full support for Django 1.10, it would be great to be able to start using new-style middleware in projects that depend on a released version of django-waffle.

I'm using django-waffle from the master branch in a Django 1.10 project with Python 3 and it works fine (i'm using switches, still not needed flags).
It will be great to have it published in Pypi to don't need to install from git

@saily @do3cc it seems that all issues are merged (#241 is merged, despite the issue is not closed).
I'm using the master branch version for several weeks and it works well.

@jsocol is the only one who can make a release. So we are all stuck with using the master branch until he either makes a new release or distributes the rights to commit and make release to more people.

@jsocol Any update on when a new release could happen?

@jsocol Could you consider to increase the number of people with the rights to do releases?
As you can see, quite a few people are waiting for an update that currently only you can do.

Version 0.12.0 is now available on PyPI.


[Relay] Add more check to type relation.

Thanks for contributing to TVM!   Please refer to guideline https://docs.tvm.ai/contribute/ for useful information and tips. After the pull request is submitted, please request code reviews from Reviewers.

@MarisaKirisame Should we revive this PR? It looks good after rebase.


Allow to use heap buffers when using native transports + better handl…

…e conversation in the nio transport
Motivation:
Sometimes it is preferable to use heap buffers because of memory constrains etc. This was not possible when using the native transports at all as it always used direct buffers. Beside this when we converted from heap to direct buffers we did not take into account of the ByteBufAllocator is pooling direct buffers which could make this conversation quite costly.
Modifications:

In the nio transport only convert from heap to direct buffers if the allocator is pooling direct buffers. If not we will let the JDK handle the conversation internally when a write / read operation is done
In native transports convert from heap to direct buffers once a flush is executed
In native transports either use the allocator to convert from heap to direct buffers (if direct buffers are pooled) or use a ThreadLocal pool of direct ByteBufs to do the convertation.
Deprecate old newDirectByteBuf methods in Channel implementations
Deprecate ByteBufUtil.threadLocalDirectBuffer()

Result:
Be able to use heap buffers with native transports + only use ByteBufAllocator for direct buffer convertion if it provides pooling for direct buffers.

@franz1981 yeah there is some duplicated code (just as before). I wanted to keep the changes to a minimum for now

/cc @tbrooks8

Actually let me just close this for now. I think it is not worth it.


Do a special release with a lower since-build for users of older IDEA to try

See
https://twitter.com/pcreddyn1/status/819199895340978176

We should be careful with that, since we are using API from 2016 SDK version and we might ending up releasing a version which say we support yearly version, but we really don't know
At least we should investigate if JetBrains is backward compatibility

Its a special release for feedback from different users what runs or what does not.
I dont really want to be limited to the latest and greatest version all the time.

In the start I was using 2016.2 version which worked fine at the time.
I wonder if its possible to find older versions to download, it doesnt seem so easy to do

We have a twitter pool
https://twitter.com/davsclaus/status/819881627266465792
At that it seems most users are on 2016 so there is maybe not so many / demand for supporting older releases.

We could add instructions to the readme.md how they can change the plugin version and build for old versions

@fharms wonder if you wanted to add the readme instructions so we can get this ticket resolved

instruction added to readme.md on how to build for a older version of IDEA


Accordion Example: ID and class duplicated in v. 4.1

4.0
https://getbootstrap.com/docs/4.0/components/collapse/#accordion-example

4.1
https://getbootstrap.com/docs/4.1/components/collapse/#accordion-example

why?

a bit weird yes, because we don't have .accordion in our CSS 🤔

https://github.com/twbs/bootstrap/commit/c0246e926f0e9e955f34b34286f97cc201582ba1

I think it would be better:

Closed thanks to @patrickhlauke 👍

yeah the id could be tweaked for clarity

https://github.com/twbs/bootstrap/pull/26391


Issue importing umbral

There is no "umbral" class exported from the package (dist/index.d.ts and dist/service.d.ts)
To reproduce:
npm install umbral
Attempt to include it:
import { umbral } from "umbral";
I noticed there was a "namespace" named CryptoService exported, but no umbral class nor interfaces. To get this to work I am currently cloning this repository to my project to access src/umbral.ts directly.
Thanks & Let me know if you need more info!

I think i previously fixed this but have yet to publish to npm. I'm adding a few other changes today and will update the package afterwards!


Convert LayerID and EpochID to uint32

Motivation
Closes #2082
Changes

Convert LayerID and EpochID to uint32

Test Plan
No new tests required, existing tests should suffice. No functionality was added.
TODO

[x] Do a more thorough grep for uint64

is this something we discussed in research meetings? I remember we decided these will be uint64. if I'm missing something please add some context to this pr.

is this something we discussed in research meetings? I remember we decided these will be uint64. if I'm missing something please add some context to this pr.

Please see https://github.com/spacemeshos/api/issues/88

Confirmed that remaining uint64 references refer to things such as nonce, balance, disk space, tick count, sequence number, etc. and not layer or epoch. Might need to double-check this math:
https://github.com/spacemeshos/go-spacemesh/blob/f3d37caee2b7345ef6c923bbfdc452fef60aea99/miner/blockoracle.go#L205-L211

bors try

bors try

bors try

bors try

bors try

closed due to inactivity and because a lot has changed since probabaly

This is still useful and important, let's keep this open. I will try to refresh it. Pretty sure this is mostly done.

@antonlerner it can be re-assigned to someone else.

Closing this in favor of https://github.com/spacemeshos/go-spacemesh/pull/2489
@lrettig that PR will convert LayerID to uint32. Do you think it's important to also handle EpochID? If you do - let's create a separate issue for it (unless @dshulyak wants to take care of that in the same PR).


Is there a way to search document language other than English?

Please provide us with the following information:

This issue is for a: (mark with an x)
- [ ] bug report -> please search issues before submitting
- [ ] feature request
- [x ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

I have upload some Traditional Chinese document file and follow the steps to use prepdocs to parse the document, but when I asked  related question in Chinese related to the document, it cannot answer any of it.

Any log messages given by the failure

Expected/desired behavior

It can answer questions regardless of the document language.

OS and Version?

Windows 7, 8 or 10. Linux (which distribution). macOS (Yosemite? El Capitan? Sierra?)
Windows 11

Versions

Mention any other details that might be useful
I have tryied to build my own index and run indexer with Chinese Analyzer but it's not working. (Already set the env variable AZURE_SEARCH_INDEX to the new one). The default content analyzer in gptkbindex is English.

Thanks! We'll be in touch soon.

In file ./scripts/prepdocs.py, you should change the function create_search_index() to create an indexer to search in Chinese or other languages. By default, the language is set to English:
SearchableField(name="content", type="Edm.String", analyzer_name="en.microsoft"),

I suggest changing the code and setting analyzer_name="standard.lucene", which seems to work properly for common languages.  For more information on the available languages, refer to the docs: https://learn.microsoft.com/en-us/python/api/azure-search-documents/azure.search.documents.indexes.models.searchfield?view=azure-python
Hope this works for you.

You can try modifying the prompt of app\backend\approvals\chateadretrieveread.py by changing "If the question is not in English, translate the question to English before generating the search query." to "Please search in the language of the original input of the question, never try to translate it into English."

If the question is not in English, translate the question to English before generating the search query.

Would be great if this was not part of the default template. Many customers that struggle with Azure OpenAI on your Data and non English documents will have a look at this accelerator.

Hm, good point. We could alter the prompt based off the query_language parameter? That presumably would reflect the language of the documents in the search index.
I can also flesh out our section about query_language into a whole doc, and suggest tweaking this part of the prompt.


Are you aware of this?

http://php.net/manual/en/class.splenum.php

That's cool but it's not there out of the box: PECL spl_types >= 0.1.0.

also this is more about human-readable functionality for  usage in views and validations.
And some of the enumerations might use functions that are not valid on compilation time such as Yii::t()

:wink: noted, although I'm not sure your implementation is as much enumerations as hash keys then?

I don't understand your question, sorry.


JSDoc Should Override type from d.ts in JavaScript files

From: https://github.com/Microsoft/vscode/issues/21321
TypeScript Version:  2.2.1 / nightly (2.2.0-dev.201xxxxx)
Code
// test-module.d.ts
declare module 'test-module' {
    declare function func<T>(c: T): (y: any) => any;
}

// example.js
import { func } from 'test-module';

/**
 * @function
 * @param {number} c first number
 * @returns {number} result
 */
const thisDoesNot = func(1);

Expected behavior:
The JSDoc specifications give thisDoesNot a type of (c: number) => number
Actual behavior:
The type from the *.d.ts file is preferred instead, giving thisDoesNot a type of (c: any) => any

Also, the param name and param description from the jsdoc should override those from the *.d.ts file

We should actually treat any @param/@return on a variable declaration as a type annotation. If we do that, I don't think that @function needs any special support.
#36633 requests this behaviour.


fix: change default propagator to match spec

Which problem is this PR solving?

Fixes issue #869

Short description of the changes

Change the default propagator in the SDK to match what the spec requires.

Modify unit tests to reflect this change of default propagator.

The lint will be fixed by #1217


sniffglue: 0.16.0 -> 0.16.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/kpcyrd/sniffglue/releases.
meta.description for sniffglue is: Secure multithreaded packet sniffer
meta.homepage for sniffglue is: https://github.com/kpcyrd/sniffglue
Updates performed

Rust version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.16.1 with grep in /nix/store/b3g4qsdg492vfwy5ndbdn4p09sihjknw-sniffglue-0.16.1
found 0.16.1 in filename of file in /nix/store/b3g4qsdg492vfwy5ndbdn4p09sihjknw-sniffglue-0.16.1

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

sniffglue

Instructions to test this update (click to expand)

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

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

Or:
nix build github:r-ryantm/nixpkgs/e8fcc4326645de4dfbefa25bc06f607682a6a6e5#sniffglue

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

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

1 package built:

sniffglue

Maintainer pings
cc @xrelkd for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

Add a :+1: reaction to pull requests you find important.

@NixOS/nixpkgs-merge-bot merge


modify variable name in anonymize_df task in viadot.utils

@trymzet trymzet 3 days ago
Can you rename this to older_than_days pls? I just had too read the code closely to understand what this param actually means because days is so generic it might as well be x, so I found a better name for it.
file to change: src/viadot/utils.py
task :   anonymize_df
action: change var name from days to older_than_days

linked PR - https://github.com/dyvenia/viadot/pull/1040/files

2nd issue:
    elif method == "hash":         df.loc[to_hash, columns] = df.loc[to_hash, columns].apply(             lambda x: x.apply(hash)
@trymzet trymzet last week
Not sure you want to do it this way -- python's built-in hash function does not generate the same output from the same input, so even if your data is the same, the calculated hashes would be different every time you run this function, which could be problematic for some use cases. To produce stable hashes, you need to use hashlib.


Set up config parameter to parameterize production and consumption DC

Two changes:

We require the user to set up config parameters for produce_dc and consume_dc - it's used as a topic prefix.
All event production now go through the production endpoint.

cc @wikimedia/services

Minor comment, otherwise :+1: from me

Coverage decreased (-1.3%) to 93.333% when pulling f1ca66ff0ace1413fff701c1b2960a62c08f90e4 on Pchelolo:dc into b0dd6677b36dbd6b50a59d53a77796e4d7818c85 on wikimedia:master.

@d00rman Updated.

Coverage decreased (-0.4%) to 94.231% when pulling 03480f9ac1e9599716e62399471e0698e7e1cb0c on Pchelolo:dc into b0dd6677b36dbd6b50a59d53a77796e4d7818c85 on wikimedia:master.

Coverage decreased (-0.4%) to 94.175% when pulling 0c84251d28f74861c344ae89ad0d865fd22c8e7e on Pchelolo:dc into b0dd6677b36dbd6b50a59d53a77796e4d7818c85 on wikimedia:master.


Publish a new version on crates.io

#3 and #4 have been merged but aren't available on crates.io

Sorry for the delay. https://crates.io/crates/hound/1.1.0


Missing items: Gem sockets on certain items

Missing Cogwheel sockets for engineering goggles, and missing prismatic sockets for relic slot gear

Also missing cata engineering enchants for gloves, belt


Wrong JSON output escaping

I noticed that fluent-bit's json parser can't parse some of eventrouter's log messages.
Eventrouter config
{
  "sink": "stdout"
}

Eventrouter stdout sample
{"verb":"UPDATED","event":{"metadata":{"name":"fluent-bit-txzvr.1577e0b2a83a3735","namespace":"lunar-system","selfLink":"/api/v1/namespaces/lunar-system/events/fluent-bit-txzvr.1577e0b2a83a3735","uid":"fe6eb861-157c-11e9-a342-5aae0cc8125e","resourceVersion":"23100854","creationTimestamp":"2019-01-11T08:43:40Z"},"involvedObject":{"kind":"Pod","namespace":"lunar-system","name":"fluent-bit-txzvr","uid":"7fc47232-1344-11e9-b82e-663e4d499873","apiVersion":"v1","resourceVersion":"22351098","fieldPath":"spec.containers{fluent-bit}"},"reason":"Pulling","message":"pulling image "fluent/fluent-bit:1.0.1"","source":{"component":"kubelet","host":"aks-nodepool1-30459648-3"},"firstTimestamp":"2019-01-08T12:54:14Z","lastTimestamp":"2019-01-11T08:43:40Z","count":6,"type":"Normal"},"old_event":{"metadata":{"name":"fluent-bit-txzvr.1577e0b2a83a3735","namespace":"lunar-system","selfLink":"/api/v1/namespaces/lunar-system/events/fluent-bit-txzvr.1577e0b2a83a3735","uid":"fe6eb861-157c-11e9-a342-5aae0cc8125e","resourceVersion":"23100854","creationTimestamp":"2019-01-11T08:43:40Z"},"involvedObject":{"kind":"Pod","namespace":"lunar-system","name":"fluent-bit-txzvr","uid":"7fc47232-1344-11e9-b82e-663e4d499873","apiVersion":"v1","resourceVersion":"22351098","fieldPath":"spec.containers{fluent-bit}"},"reason":"Pulling","message":"pulling image "fluent/fluent-bit:1.0.1"","source":{"component":"kubelet","host":"aks-nodepool1-30459648-3"},"firstTimestamp":"2019-01-08T12:54:14Z","lastTimestamp":"2019-01-11T08:43:40Z","count":6,"type":"Normal"}}

If I try to parse it, I got this

glogsink has the same issue.


upgrade from 0.5.0 to 1.0.0 is breaking for Android

I am using M1 machine and iOS build works fine but for Android build it keeps failing.
android/build.gradle
       buildToolsVersion = "30.0.2"
        minSdkVersion = 21
        compileSdkVersion = 30
        targetSdkVersion = 30
        ndkVersion = "21.4.7075529"
        kotlinVersion = '1.6.0'

Error logs
> Task :app:checkDebugAarMetadata FAILED

Deprecated Gradle features were used in this build, making it incompatible with Gradle 7.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See https://docs.gradle.org/6.9/userguide/command_line_interface.html#sec:command_line_warnings
143 actionable tasks: 9 executed, 134 up-to-date

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':app:checkDebugAarMetadata'.
> A failure occurred while executing com.android.build.gradle.internal.tasks.CheckAarMetadataWorkAction
   > The minCompileSdk (31) specified in a
     dependency's AAR metadata (META-INF/com/android/build/gradle/aar-metadata.properties)
     is greater than this module's compileSdkVersion (android-30).
     Dependency: androidx.work:work-runtime-ktx:2.7.1.
     AAR metadata file: /Users/adeem/.gradle/caches/transforms-3/90fad26cc6b303298c4f0660035e44d4/transformed/work-runtime-ktx-2.7.1/META-INF/com/android/build/gradle/aar-metadata.properties.

Hi, Did you try to increase compileSdkVersion to 31? 🤔

Yes we did and it worked. But our developer suggest to keep the compile SDK and Target SDK same level.
Once I move both to 31, I started to get error like below
/Mobile/android/app/src/main/AndroidManifest.xml Error:
        Apps targeting Android 12 and higher are required to specify an explicit value for `android:exported` when the corresponding component has an intent filter defined. See https://developer.android.com/guide/topics/manifest/activity-element#exported for details.
/Mobile/android/app/src/main/AndroidManifest.xml Error:
        Apps targeting Android 12 and higher are required to specify an explicit value for `android:exported` when the corresponding component has an intent filter defined. See https://developer.android.com/guide/topics/manifest/activity-element#exported for details.

To solve above problem, I go into AndroidManifest.xml file and add android:exported="true" to all the activity and it still give above error

When targeting Android 12, this also has to be added to services and broadcast receivers with an intent filter. Here is official Android docu.    Also make sure, that the libraries you are using support Android 12. In case you are not ready yet to update the app for Android 12, you can use the previous version of the SDK.

Not a great solution :( There are many issues you fixed!


Module 2 exercises Judith Nommo Dery]

Exercise 3 Judith.pdf
Exercise 4 Judith.pdf

Please "drag & drop" exercise 1 pdf file below.

Please "drag & drop" exercise 2 pdf file below.

Please "drag & drop" exercise 3 pdf file below.

Please "drag & drop" exercise 4 pdf file below.

Please UPDATE THE TITLE of this "Issue" in the title bar above with your name.

If you haven't done so, please go back to Module 2 and make sure to take
the post-training survey. Participating in surveys is required for receiving
the "GALUP Certificate" by the University of Florida.

Hi Judith, I'm still missing exercises 1 and 2 here.

I sent assignments 1 and 2 a while back and was given feedback on them. I am adding them all here
Galup 1 Judith.pdf
Galup 2 Judith.pdf
Exercise 4 Judith.pdf
Exercise 3 Judith.pdf
though. Thank you.

My mistake! I’ll close out the issue now.

On Jul 5, 2021, at 11:35 AM, Jnommo @.***> wrote:

I sent assignments 1 and 2 a while back and was given feedback on them. I am adding them all here
Galup 1 Judith.pdf
Galup 2 Judith.pdf
Exercise 4 Judith.pdf
Exercise 3 Judith.pdf
though. Thank you.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub, or unsubscribe.


Improve exception logging in rack

> logger = Dry.Logger(:app, formatter: :rack)
# => #<Dry::Logger::Dispatcher:0x00000001077d2aa0

> logger.error(StandardError.new("OH NOEZ").tap { |e| e.set_backtrace(["file-1.rb:321", "file-2:42"]) })
# StandardError: OH NOEZ
# from file-1.rb:321
# from file-2:42

Do we want the "from" prefix in front of every like in the stacktrace? That feels a bit off to me.

@timriley I've no idea why it was there in the first place to be honest. I just carried it over from hanami-utils 🙂

@timriley btw my suggestion would be to replace from:  with a tab. This would give you a nice visual clue about where the stack trace starts and ends when you're looking at the log output.


decide on advice for use of unstable semconv consts: copy or pin dep

[Trent]

I've added that as an option alternative to depending on a pinned version and using the "incubating" entry point. However, do you think we should reverse the suggestion and have the first suggestion be copying the definitions? (This could be done in a separate PR.)

[Jamie]
Thinking through this more... while it may not be a big deal for someone to pin now when only http is stable, it will become a bigger issue when the next wave of stable attributes come through (if there are changes). This would mean folks have the option to either pin and miss out on new stable attributes, or unpin and risk breaking changes. I'm leaning even more heavily now toward copying attributes, but am fine with that as a follow-up.
Originally posted by @JamieDanielson in https://github.com/open-telemetry/opentelemetry-js/issues/5166#issuecomment-2486789075

There is a possibly interesting wrinkle here is the usage of @opentelemetry/semantic-conventions in packages that live in this core repo.
Take this usage, for discussion:
https://github.com/open-telemetry/opentelemetry-js/blob/d8bc6b283ba0522441e4ae6fc5f849ce28041ef1/packages/opentelemetry-resources/src/detectors/platform/node/ProcessDetectorSync.ts#L18-L28
When doing a semconv package release, current practice in this repo is to update the semconv dep in any other core-repo package to the new semconv package version (pinned). E.g. from this release PR:  https://github.com/open-telemetry/opentelemetry-js/pull/5186/files#diff-b12e80a906ecf0de3d9311ef632ab16939846c61c08935857023a117cc3ff910
diff --git a/packages/opentelemetry-resources/package.json b/packages/opentelemetry-resources/package.json
index 6c14650825..79b1796eca 100644
--- a/packages/opentelemetry-resources/package.json
+++ b/packages/opentelemetry-resources/package.json
@@ -92,7 +92,7 @@
   },
   "dependencies": {
     "@opentelemetry/core": "1.28.0",
-    "@opentelemetry/semantic-conventions": "1.27.0"
+    "@opentelemetry/semantic-conventions": "1.28.0"
   },
   "homepage": "https://github.com/open-telemetry/opentelemetry-js/tree/main/packages/opentelemetry-resources",
   "sideEffects": false

Currently there is no problem here. However, soonish we'll want to update the deprecated export name usage, e.g. updating from SEMRESATTRS_PROCESS_COMMAND to ATTR_PROCESS_COMMAND, like this:
https://gist.github.com/trentm/f67edf299645d065f6fe2af4ce9ab894
Note how, on line 28 of that diff, we have changed to use the "incubating" entry-point of the semconv package.
Then, the possible issue is that the newer version of @opentelemetry/semantic-conventions could break unstable semconv exports in a minor release.
Then, the question is:

For core-repo packages that use unstable semconv exports, should we be copying/duplicating the semconv constants and not use the "incubating" entry-point?
Or should we change the semconv package release process to (manually) work through possible breakages in the "incubating" entry-point from the new version of the semconv package?

Then, the question is:

https://github.com/open-telemetry/opentelemetry-js/pull/5187 is a draft PR that shows both options, using the "resources" package as a demo.

When a key is removed it should be moved to the deprecated.yml in semconv. On next release it should still be included in code generation, just with a @deprecated tag. I think there's no reason to pin the dependency. I'd say it even does us a favor by letting linters tell us which packages are out of date in semconv.

I think there's no reason to pin the dependency.

Then why do the semconv incubating packages/entry-points (for JS, Java, etc.) state that the incubating package can have breaking changes in minor versions?
Are you positive that some experimental semconv keys don't just get removed rather than moved to "deprecated.yml"?

Are you positive that some experimental semconv keys don't just get removed rather than moved to "deprecated.yml"?

I briefly tried to find a counter example (i.e. a breaking change going from 1.27.0 to 1.28.0) and could not find one.
Do you happen to know if the JS semconv package is different from the other langs in someway that we don't have breaking changes in "incubating"? Perhaps the other langs don't emit deprecated keys?
So I wonder if it is fine for us to remove the mention here of the incubating entry-point having breaking changes and users needed to beware how they use it.

Perhaps the other langs don't emit deprecated keys?

Some languages do not emit deprecated keys. At least go used to be like that.

A side-effect of pinning in the contrib repo:
https://github.com/open-telemetry/opentelemetry-js-contrib/pull/2473 pinned the semconv dep for instrumentation-pg "as it's using the incubating entrypoint, which may break on minor bumps."
That is currently the only package in the contrib repo that is pinning the semconv dep.
The result of that is that the scripts/update-otel-deps.js script now fails to automatically update @opentelemetry/semantic-conventions from 1.27.0 to 1.28.0.
... as it should fail, because: it fails because the dep is pinned, presumably because incubating is being used, which could have a breaking change. So, in general, it requires a manual look to check for those breaking changes.
We'll need to change the "update otel deps" process somehow to accommodate this. I'll look into it.

Maintainers discussed this earlier today. My notes:

We decided to recommend pinning the semconv dep if using the "incubating" entry-point.

However, a concern (as express in Jamie's comment in this issue description) is that a package using both stable and unstable semconv will need to pin. When that package wants to use newly-stabilized semconv exports the update is slightly harder because they need to watch out for possibly breaking changes in the exports being used from the "incubating" endpoint.
One of the reasons the JS advice (whether to pin the dep or make a copy of any used unstable exports) will differ from Java's (and I assume Python's) is that their import mechanisms do not allow having multiple version of the semantic-conventions package installed. JS's does allow that, so we can use the pinning option.
TODO: update the semconv/README.md usage notes (https://github.com/open-telemetry/opentelemetry-js/blob/main/semantic-conventions/README.md#usage) accordingly

When a user of the JS semconv package is updating, they need advice on how to do so. Ideally we need better changelog/release notes for this package. To a degree the semconv repo changelog can be this changelog, but it might be too obtuse/dense for users of the JS package.

what breaking changes, if any, are in the "incubating" package for this version?
what's new in the stable exports?
what's new in the incubating package?

Some examples of breaking changes in the incubating entry-point we've seen or expect:

In the 1.28.0 release there were some changes in the values of db.cosmosdb.operation.type E.g.:

-export const DB_COSMOSDB_OPERATION_TYPE_VALUE_EXECUTE = "Execute" as const;
+export const DB_COSMOSDB_OPERATION_TYPE_VALUE_EXECUTE = "execute" as const;
-export const DB_COSMOSDB_OPERATION_TYPE_VALUE_EXECUTE_JAVASCRIPT = "ExecuteJavaScript" as const;
+export const DB_COSMOSDB_OPERATION_TYPE_VALUE_EXECUTE_JAVASCRIPT = "execute_javascript" as const;

In the future, there will likely be an exception to the semconv "no change in only underscore or dots" rule to allow changing from export const ATTR_FEATURE_FLAG_PROVIDER_NAME = 'feature_flag.provider_name'; to feature_flag.provider.name.

https://github.com/open-telemetry/opentelemetry-js-contrib/pull/2569 adds a 'npm run lint' step to ensure the semconv dep is pinned if a package is using the incubating entry-point (only usage in "src/**/*.ts" is checked).

One of the reasons the JS advice (whether to pin the dep or make a copy of any used unstable exports) will differ from Java's (and I assume Python's) is that their import mechanisms do not allow having multiple version of the semantic-conventions package installed. JS's does allow that, so we can use the pinning option.

On the other hand, other language's dependency systems don't have the tendency to become the heaviest object in the known universe

Obviously those notes seem very abridged but I'm not sure if the bloat implications of this approach have been sufficiently considered. @opentelemetry/semantic-conventions package is currently at an unpacked size of 6.25MB and every pinning means that it's very likely npm will have to resolve at least one duplicate package (and the amount of duplicates != amount of versions, let's say 30 instrumentation dependencies, 10x use 1.1 + 10x 1.2 + 10x 1.3 means only one of those gets hoisted and you end up with 21 installs.... in an ideal world but who hasn't used npm and ended up with odd resolutions)
In fact, taking an average install of @sentry/node (which is basically the most popular way to end up with an opentelemetry sdk in your node_modules), turns out it already happens before this recommendation became in effect (somehow due to otel itself? again, npm and resolutions)
PS E:\tmp\otel-tree-test> npm init
[...]
PS E:\tmp\otel-tree-test> npm i @sentry/node
[...]
PS E:\tmp\otel-tree-test> npm ls @opentelemetry/semantic-conventions
<EMAIL_ADDRESS>E:\tmp\otel-tree-test
`--<EMAIL_ADDRESS>  +--<EMAIL_ADDRESS>  | `--<EMAIL_ADDRESS>  +--<EMAIL_ADDRESS>  | `--<EMAIL_ADDRESS>deduped
  +--<EMAIL_ADDRESS>  | `--<EMAIL_ADDRESS>deduped
  +--<EMAIL_ADDRESS>  | `--<EMAIL_ADDRESS>deduped
  +--<EMAIL_ADDRESS>  | `--<EMAIL_ADDRESS>deduped
  +--<EMAIL_ADDRESS>  | `--<EMAIL_ADDRESS>deduped
  +--<EMAIL_ADDRESS>  | +--<EMAIL_ADDRESS>  | | `--<EMAIL_ADDRESS>deduped
  | `--<EMAIL_ADDRESS>  +--<EMAIL_ADDRESS>  | `--<EMAIL_ADDRESS>deduped
  +--<EMAIL_ADDRESS>  | `--<EMAIL_ADDRESS>deduped
  +--<EMAIL_ADDRESS>  | `--<EMAIL_ADDRESS>deduped
  +--<EMAIL_ADDRESS>  | `--<EMAIL_ADDRESS>deduped
  +--<EMAIL_ADDRESS>  | `--<EMAIL_ADDRESS>deduped
  +--<EMAIL_ADDRESS>  | `--<EMAIL_ADDRESS>deduped
  +--<EMAIL_ADDRESS>  | `--<EMAIL_ADDRESS>deduped
  +--<EMAIL_ADDRESS>  | `--<EMAIL_ADDRESS>deduped
  +--<EMAIL_ADDRESS>  | `--<EMAIL_ADDRESS>deduped
  +--<EMAIL_ADDRESS>  | `--<EMAIL_ADDRESS>deduped
  +--<EMAIL_ADDRESS>  | `--<EMAIL_ADDRESS>deduped
  +--<EMAIL_ADDRESS>  | `--<EMAIL_ADDRESS>deduped
  +--<EMAIL_ADDRESS>  | `--<EMAIL_ADDRESS>  +--<EMAIL_ADDRESS>  | `--<EMAIL_ADDRESS>  +--<EMAIL_ADDRESS>  `--<EMAIL_ADDRESS>    `--<EMAIL_ADDRESS>deduped

Multiple semantic conventions packages is already half of the disk space after installing a reasonably usable otel setup
In fact I think we can already estimate the effects of pinning by looking at another package that is well known to have issues with how many times it gets installed, @opentelemetry/instrumentation
PS E:\tmp\otel-tree-test> npm ls @opentelemetry/instrumentation
<EMAIL_ADDRESS>E:\tmp\otel-tree-test
`--<EMAIL_ADDRESS>  +--<EMAIL_ADDRESS>  | `--<EMAIL_ADDRESS>deduped
  +--<EMAIL_ADDRESS>  | `--<EMAIL_ADDRESS>deduped
  +--<EMAIL_ADDRESS>  | `--<EMAIL_ADDRESS>  +--<EMAIL_ADDRESS>  | `--<EMAIL_ADDRESS>deduped
  +--<EMAIL_ADDRESS>  | `--<EMAIL_ADDRESS>deduped
  +--<EMAIL_ADDRESS>  | `--<EMAIL_ADDRESS>deduped
  +--<EMAIL_ADDRESS>  | `--<EMAIL_ADDRESS>  +--<EMAIL_ADDRESS>  | `--<EMAIL_ADDRESS>deduped
  +--<EMAIL_ADDRESS>  | `--<EMAIL_ADDRESS>  +--<EMAIL_ADDRESS>  | `--<EMAIL_ADDRESS>  +--<EMAIL_ADDRESS>  | `--<EMAIL_ADDRESS>  +--<EMAIL_ADDRESS>  | `--<EMAIL_ADDRESS>deduped
  +--<EMAIL_ADDRESS>  | `--<EMAIL_ADDRESS>deduped
  +--<EMAIL_ADDRESS>  | `--<EMAIL_ADDRESS>  +--<EMAIL_ADDRESS>  | `--<EMAIL_ADDRESS>  +--<EMAIL_ADDRESS>  | `--<EMAIL_ADDRESS>deduped
  +--<EMAIL_ADDRESS>  | `--<EMAIL_ADDRESS>  +--<EMAIL_ADDRESS>  | `--<EMAIL_ADDRESS>  +--<EMAIL_ADDRESS>  | `--<EMAIL_ADDRESS>  +--<EMAIL_ADDRESS>  | `--<EMAIL_ADDRESS>  +--<EMAIL_ADDRESS>  | `--<EMAIL_ADDRESS>  +--<EMAIL_ADDRESS>  | `--<EMAIL_ADDRESS>  +--<EMAIL_ADDRESS>  | `--<EMAIL_ADDRESS>deduped
  +--<EMAIL_ADDRESS>  | `--<EMAIL_ADDRESS>  +--<EMAIL_ADDRESS>  +--<EMAIL_ADDRESS>  | `--<EMAIL_ADDRESS>  `--<EMAIL_ADDRESS>    `--<EMAIL_ADDRESS>deduped

That is 16 installs of @opentelemetry/instrumentation, if we estimate that each one of those would also end up in a separate semantic convetions package at about 6.2MB each - that's 99.2MB. Now good news is AWS Lambda's maximum deployment package size is around 250MB so you can probably still instrument your application after throwing away a few other dependencies but I don't think anyone wants to use that as their defence
At some point the package size will probably decrease after all the past attempts for export key format can be cleaned up, and while the runtime hit isn't exactly equal to the size on disk, each duplicate still means resolving the package, loading the files, parsing the files, executing them, and then eventually cleaning up extraneous stuff from memory. Not a good look for a performance monitoring library to do it 16 times just because

When a user of the JS semconv package is updating, they need advice on how to do so. Ideally we need better changelog/release notes for this package. To a degree the semconv repo changelog can be this changelog, but it might be too obtuse/dense for users of the JS package.

I don't think you can expect any sort of being up to date from any wider circle than repos under otel. Looking at most users of semantic conventions:

Packages in otel-js: Would be kept up to date on release since they're in same repo and update script
Packages in otel-js-contrib: You'd expect to be kept up to date due to same maintainers but considering the track record so far, I do not have any confidence in immediate updates after a new main repo release
Packages by other vendors: Depends too much on vendor and their release frequency (since usually bigger enterprise -> up to quarterly releases), dependabot exhaustion is a real thing, Best case days, more realistic weeks to months, worst case you end up with aspecto

So I would rather support copying/hard-coding the attributes until they're stable in semantic conventions, otel already has plenty of bloat issues, don't really need more of them

@t2t2 Thanks very much. Maintainers discussed this again. (That was last week. I didn't get back to updating this issue. My bad.)  Concensus was to change to recommending copying used unstable semconv attributes, rather than pinning.
The main argument against pinning was: the disk size taken by a number of installs of @opentelemetry/semantic-conventions for a disk-limited environment (most specifically a Lambda layer zip file, 250MB limit, when not using a bundler/tree-shaker); and the expectation that having a number of installs could be the common case when installing @opentelemetry/auto-instrumentations-node after just a few of those instrumentations pinned.
My plan is to:

Update the advice in https://github.com/open-telemetry/opentelemetry-js/blob/main/semantic-conventions/README.md
Perhaps suggest that users use "src/semconv.ts" as a best-practice file name to store these copies, in the hopes that we might eventually provide some tooling to help create and maintain these copies.
Start making PRs to the opentelemetry-js-contrib.git repo to move to this copying. Currently instrumentation-pg and instrumentation-aws-lambda are using unstable semconv values, but I think there will be more as we (a) move to the newer ATTR_* export names and (b) update instrumentations to more recent semantic conventions.   I don't need to be a blocker on this step.


Refactor to pull out service from UI code

The logic to be pulled out  into services include:

DOI look up
NLMTA look up

Closed by PR #865


Provision for multisite installation

How would vampd provision a multisite installation?

@jordanlgraham What does your multisite installation look like?
There are a couple instances that are present.

Make files to create the multisite install.
1 repo containing all the sites
1 parent repo and then many children that are symlinked into the parent.

I am taking 3 as the more standard approach... This is currently not possible but we are working on a solution that would allow for it. I can push up my branch, there is some trickery that is needing to occur for the drush commands to work properly and the symlinks to take. Essentially, if you have a symlink from sites/my_site/  to assets/my_site/current then all the commands need to run under site/my_site instead of assets/my_site/current.
Hopefully, in the next couple days I can address this, in the mean time though, it would have to be an manual deploy of the sites. You could use vampd to set up the initial instance and then deploy the children.

Our current project has #2 configuration from your note:
/sites
/all
/default
/[second-site.com]
sites.php
...
What I have been doing is provisioning the parent site, manually editing sites/sites.php, running the install script at second-site.com and then dropping, creating and importing the db using mysql commands.


Program Crash

Everytime I  put my ps4 .txt file into the loader it just closes no code nothing just closes

Duplicate of #43 .


Setup access to publish NPM packages

Package org/scope: @aries-bifold
Admin/Owner Access (NPM accounts):

hyperledger-ci
hyperledger-lf
cvarjao

Notes:

What is the process for acquiring an access token for automation? is it from hyperledger-ci account?

@cvarjao NPM_PUBLISH is the name of the secret

Thanks @ryjones !


CCCP 4049 Update MariaDB mirror URL and restore CI file from upstream

The restore of the CI file is because we deleted it before and if we plan to collaborate to upstream we will have to recover it anyway.

The CI checks fail. Should we maybe keep them removed?


Typography

🚀 Feature Proposal
Add Typography components to the library.
Motivation
Typography will allow for consistent text and text styling across the application. This will also allow for differences between contextual meaning and styling. (i.e. the element represents an <h1> tag on the page, but we want to style it like an <h3> tag).
Example
Any page with text.
https://getbootstrap.com/docs/4.0/content/typography/

Good point @jackcmeyer and here I want @StefanoMiC 's point of view.

Can I have this issue?

@gqycloud this has been assigned to you! excited to see what you come up with!

What font will be used in the application?

I’d like to take a crack at this! Do we have styles predefined?


Low contrast between selected and non-selected tabs

Hello, I'v been really enjoying this theme so far.  I love the subtly of the tabs but would it be possible to increase the contrast between the selected tab and the non-selected tabs?  My eyes have difficulty distinguishing which tab is selected and which isn't.  I considered a few ideas either changing the selected tab color or perhaps bolding the selected file name?

I try to stay close to the vscode colors, but I do see your point: the tabs are sometimes a little too low-contrast on some screens. VS Code has the Catppuccin accent under the active tab and Zed does not.
I'll look into what looks good and visible 👍

or perhaps bolding the selected file name

there's currently not a whole lot of customizability for tabs within Zed: themes could only tweak active and inactive color

@tecandrew Thanks so much for making the adjustment and making this awesome Zed theme!

In light mode this new tab colors are semantically counter-intuitive. The lighter tab that is closer to the color of the main background is the inactive tab, while the darker tab is the active one.

There have been many cases where I was confused about which tab I was on!

hmm, idk why I never considered this. it doesn't look a bit better 🤔 I guess I just wanted to stay close to vscode's style.

if you'd like to try this @sipec you can add the following in your settings.json
Latte
"experimental.theme_overrides": {
  "tab.active_background": "#eff1f5",
  "tab.inactive_background": "#dce0e8"
},

Mocha
"experimental.theme_overrides": {
    "tab.inactive_background": "#11111b",
    "tab.active_background": "#1e1e2e"
},


boards: xtensa: nxp_adsp_imx8m: include pinctrl dtsi in overlay

Move the pinctrl dtsi (mimx8ml8dvnlz-pinctrl.dtsi) from board dts to _uart overlay since, now, for nxp_adsp_imx8m, this is used only with uart support for certain samples.
This also fixes a build error on SOF, where we don't take the nxp_hal and the dtsi cannot be found.

I confirm this fixes the SOF build in my workspace,  thank you for the super quick fix!


Release v2.2.7

Merge #328 first

Pull Request Test Coverage Report for Build 760

0 of 0 (NaN%) changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 92.075%

Totals

Change from base Build 755:
0.0%

Covered Lines:
244

Relevant Lines:
265

💛  - Coveralls


ilc.exe from Windows_NT-bin.zip from https://github.com/dotnet/corert/releases gives exception

I've downloaded Windows_NT-bin.zip from https://github.com/dotnet/corert/releases
and when I try to run ilc.exe it gives me an exception:
D:\Windows_NT-bin\bin\Product\Windows_NT.x64.Release>ilc.exe
Wyjątek nieobsłużony: System.IO.FileNotFoundException: Nie można załadować pliku lub zestawu 'System.Console, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' lub jednej z jego zależności. Nie można odnaleźć określonego pliku.
w ILCompiler.Program.Main(String[] args)
(translated to english - it says unhandles exception, cannot load file or assembly System.Console)
why can't it find System.Console assembly ?
I have VS 2015 installed and it is begin run from VS 2015 x64 Native Tools command prompt

The EXE is built for CoreCLR. You'll need to run it through CoreRun - it will not with the desktop CLR (which is what runs if you run the EXE directly on Windows).
The release is also very old - you're better off building ILC from source.
The best way to play with ILC is by following the instructions here: https://github.com/dotnet/corert/blob/master/Documentation/how-to-build-and-run-ilcompiler-in-visual-studio-2015.md or here: https://github.com/dotnet/corert/blob/master/Documentation/how-to-build-and-run-ilcompiler-in-console-shell-prompt.md.

I have deleted the old release to avoid confusion.


Integrated terminal does not open to project root using WLS

VSCode Version: 1.15.1 x64
OS Version: Windows 10, WLS:  Ubuntu 16.04.3 LTS
Terminal Used: zsh/oh-my-zsh
Reproduces without extensions: Yes

Description:
I recently upgraded vscode to the x64 build, and shortly afterward I noticed that the integrated terminal was no longer opening to the project root.
Steps to Reproduce:

Open Folder/Project with or without .vscode workspace settings.
Open Integrated terminal
Terminal opens to '~' instead of project root.

PS:
Not sure if this is relevant or not, but the projects i'm opening are stored on a separate drive from the OS install drive. I mention this because any attempt to use terminal.integrated.cwd to remedy the situation seems to default the the C: drive.

I got terminal.integrated.cwd to work, but its my understanding that without this setting it should still default to the root directory that contains .vscode, which it is not doing.
If my understanding is incorrect, then my apologies and this issue can be closed.

@Zamerick can you elaborate on your settings? I'm switching to the Windows Store version of Ubuntu (the blog states that Bash on Ubuntu on Windows will be deprecated at some point). I figured out that
  "terminal.integrated.shell.windows": "ubuntu.exe",

to get the terminal to launch at all since unlike before, using a path to sysnative (c:\windows\sysnative\bash.exe) never actually launched the terminal.
Also, this #32188 seems related

Been working with Rust on my macOS laptop, and figured I'd continue on my Windows desktop tonight.  So I setup the new WSL (much easier than it used to be) and set my integrated shell to the result of where ubuntu.
It works great, but it opens to home instead of the current workspace root.  And not even my Windows home, it's showing my Ubuntu home instead.
  Powershell's a fine shell, I just prefer the bash ecosystem.

If you are getting an error when launching "bash.exe" but "ubuntu.exe" works, that means your default distro is not configured.
You can solve it by checking which distro's are installed with:
wslconfig.exe /l
and then setting default distro with:
wslconfig.exe /s Ubuntu
Enjoy fixed bash.exe !

Getting this issue as well. Mysteriously I was able to get it work once on another computer.
Invoking Ubuntu does not start in the project folder instead it goes to ~ for the following attempts:

Default terminal is directory to ubuntu.exe
Default terminal is powershell and use that to call ubuntu, wsl, or even bash.

This appears to work now, I testing under 1.19.3/1.21.0-insiders and both launched in the workspace settings. I'm guessing Windows FCU fixed this.

I have the same problem with vscode 1.21.1 and "terminal.integrated.shell.windows": "ubuntu.exe". Opening a new terminal brings me to ~ instead of the cwd.

Can confirm that invoking a specific shell like ubuntu.exe or debian.exe will open the terminal and place you in ~. I tried using the terminal.integrated.cwd to take me to "${workspaceFolder}", but then my terminal would never open.
Changing my terminal.integrated.shell.windows to C:\Windows\sysnative\bash.exe was required for it to open the terminal in my actual workspace folder. Using the comments above to change your default shell to the one you would prefer in VS Code looks like the only workaround.
This seems like a WSL issue, as it used to work as expected when invoking a specific shell.

@bitcrazed any reason why the cwd will only be set correctly when using "bash.exe", not specific distros like "ubuntu.exe"?

@bitcrazed are you meant to use ubuntu.exe run bash to get the cwd to be set correctly when running distros? https://github.com/Microsoft/vscode/issues/50265 Seems messy if so? 😕

@tara-raj

Add this to the catalog of things that appear like they should be simple, but end up being tricky.
When a distro's start-menu tile/pinned shortcut is clicked, the distro's launcher is executed (e.g. ubuntu.exe). To avoid starting the distro at c:\Windows\System32, we force distro launchers to start at home (~/).
When you run <distro>.exe from the command-line, you're launching the distro launcher, which starts session in home (~/).
However, if you execute <distro>[.exe] run, your distro starts-up in the cwd ... or at least it will when the distro vendors update their launcher to the latest code ;) @tara-raj is working with them on this!
Running wsl.exe, on the other hand, is able to start your distro in your cwd.
We are working on something to make this much more consistent - bear with us for now ;)
Also, this may be of interest: https://blogs.msdn.microsoft.com/commandline/2017/11/28/a-guide-to-invoking-wsl/

Could the cwd be used unless it was launched from System32? Alternatively the start menu shortcut could add an arg to start at ~?

Alas, adding tokens to start menu shortcuts isn't supported.
Also, what if the user IS at c:\Windows\System32 and WANTS to open their distro there?
We have a better solution that we're working on … bear with ;)

Thanks for the update, I'll close this off then as there's nothing to action on our side.

This was happening to me because my project folder had spaces in its path


Fix tools not being installed in knative-style

Changes

Always install tools in knative-style so that subsequent steps won't fail

/kind bug
Fixes #158
We don't need to fail fast, we can run all the linters, but since this step was missing the if: always, it would be skipped which means the other steps are definitely going to fail.
I tested this out here: https://github.com/benmoss/eventing-rabbitmq/runs/4562246793?check_suite_focus=true

/lgtm
/approve


[QA-1895] Integration test: speculative fix for navigation timeout error

https://broadworkbench.atlassian.net/browse/QA-1895
Seeing sporadic UI test failures caused by Navigation timeout.
This was recently added
const waitUntilLoadedOrTimeout = timeout => ({ waitUntil: ['load', 'domcontentloaded', 'networkidle0'], timeout })

I think it has to do with waitUntil: load, domcontentloaded options so I'm going to remove these two.

Not necessarily for this PR, but based on the number of page.goto calls that had to be changed here, maybe a goToPage helper function would nice. So that timeout options don't have to be specified every time.

Can you think a better way to hold off checking loading spinner until page is "ready" besides checking for blank page?


fix: commit the ndb in LoadVersionForOverwriting

need to backport to 0.19.x.
It was previously included in https://github.com/cosmos/iavl/pull/636, separate out for easier review.

was this a regression or a new change?

it's a bug fix I believe.

should we backport this to 0.19?

should we backport this to 0.19?

I think so

amazing I will test on a chain before final release

@mergifyio backport release/v0.19.x


Utilize redirect_uri_path from config

Hello!
I noticed that the config schema had the params for redirect_uri_path, but the plugin wasn't passing it through to lua-resty-openidc. This updates it so that it will utilize the config if it is set, and otherwise fallback to the original behavior.
My use case for this is that I am trying to integrate with identityserver.io, which has very strict restrictions on the redirect_uri (for good reasons), and thus it becomes near impossible because all API uris must be registered. This allows for registering just a single endpoint that is used as the callback, which will autoforward to the originally requested uri as done by lua-resty-openidc.

Pull Request Test Coverage Report for Build 58

0 of 0 (NaN%) changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 54.795%

Totals

Change from base Build 52:
0.0%

Covered Lines:
1040

Relevant Lines:
1898

💛  - Coveralls


Data Discrepancy

I am using SPY data, with Resolution.Daily.
Regardless of the DataNormalizationMode in Initialize(), QC says that SPY close price on 2016-06-20 was 207.91, but the actual close price was 207.85. The Open, High, and Low prices for SPY on that date are correct, but for some reason the Close price is not.
See http://www.nasdaq.com/symbol/spy/historical
Am I missing something or is this a bug?

Hi Pi,
Assuming you're referring to the sample data with the LEAN repo -- we use
QuantQuote data and its built from ticks; see this answer here directly
from QuantQuote: https://quantquote.com/support_faq.php
Why is your data different from Yahoo Finance?
"There are several possible reasons for discrepancies. If you are comparing
the close prices, these will often differ slightly because the official
close price listed on NASDAQ or NYSE is not always the last trade that
occurred before 1600, but rather a trade that occurred slightly after
market close. For increased accuracy, our datasets use the last trade
before 1600 which is a more accurate representation of a price one might
get if a position was opened or closed near the end of the trading day.
Within the intraday bars, a source of discrepancies is the fact that
Yahoo's data only comes from one or two exchanges. QuantQuote's data is
aggregated over 12 national exchanges and the FINRA ADF so our prices are
more comprehensive and accurate.
Discrepancies are also possible due to errors in Yahoo Finance. Our data
quality team and customers have discovered errors within Yahoo's daily data
which often stem from incorrect dividend adjustments. However, if you feel
you have discovered a true error in our data, please contact our support
team at<EMAIL_ADDRESS>Our high level of data quality is partially
due to the feedback we have received from customers over the years and we
make every attempt to correct data flaws that are brought to our attention."
Best,
JB
On Mon, Jul 18, 2016 at 12:41 AM, pi-over-two<EMAIL_ADDRESS>wrote:

I am using SPY data, with Resolution.Daily.
Regardless of the DataNormalizationMode in Initialize(), QC says that SPY
close price on 2016-06-20 was 207.91, but the actual close price was
207.85. The Open, High, and Low prices for SPY on that date are correct,
but for some reason the Close price is not.
See http://www.nasdaq.com/symbol/spy/historical
Am I missing something or is this a bug?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/QuantConnect/Lean/issues/490, or mute the thread
https://github.com/notifications/unsubscribe-auth/ACI6mdWmuMW_5XvvjEyhFbonbHIV--veks5qWwP6gaJpZM4JOaJo
.

--
Jared Broad
www.quantconnect.com
Phone-USA: +1<PHONE_NUMBER>
Democratizing Finance, Empowering Individuals
Facebook http://www.facebook.com/QuantConnect | Twitter
https://twitter.com/#!/QuantConnect | LinkedIn
http://www.linkedin.com/company/quantconnect | Skype: jaredbroad

Jared,
Thanks for the prompt response!
I am using the web-based C# editor (hence using the back-end data, right?), does that make a difference?
Your explanation makes sense though; I was looking at the ThinkOrSwim / Google Finance / NASDAQ data, and they all agreed (disagreed with QuantQuote), but the QuantQuote explanation seems to explain the difference.


wiki: OpenSSH

https://nixos.org/wiki/OpenSSH

This page is super useless and can probably just be deleted.

:+1: closing this issues since there is nothing to migrate


Make start/dev Executable Commands Configurable

Is your feature request related to a problem? Please describe.
We now use a bespoke server with Nextjs that is not started via the usual next start/dev commands that RNV assumes
Describe the solution you'd like
It would be good if we can configure this through RNV (we actually invoke node src/next/server/index.js but any child_process compatible format would be doable)

introduction of rnv engines (#511) will bring support for overriding engine specific tasks ie run.
Example config:
{
"engines": {
      "engine-rn-next": {
         "platforms": {
             "web": {
                 "tasks": {
                     "run": {
                         "script": {
                             "node ./src/next/server/index.js"
                         }
                     }
                 }
             }
         }
      }
    },
}

Example usage:
rnv run -p web


Interactive deletion

atuin search --delete -i should work as an interactive deletion.
Right now the --delete argument is ingored.

From my user's point of view: As it was a bit complicated to implement the deletion feature (because atuin can sync the history over systems) it was very important to implement it at all and thus to be able to use it from the command line.
So, I guess that interactive deletion will be implemented finally but it may take some time.


PySpark Dates are automatically converted to local timezone

Describe the bug
When exporting records to Pyspark, time values are being adjusted for the local timezone, but do not contain the timezone information in the object.
To Reproduce
Steps to reproduce the behavior:

Expected behavior
A clear and concise description of what you expected to happen.
In the above query, it is expected that the Year, Month, and Day of Timestamp and Timestamp2 be equal in Python, but, they are not.

By the time the data is loaded into Python, an offset is applied (which seems to be my local timezone vs UTC time, so for me in NYC timezone, all my results are 5 hours to low.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

Windows 11
Python 3.8
Spark 3.2.1
kusto-spark_3.0_2.12:2.9.1
hadoop-azure:3.3.1

Additional context
I was able to replace my kusto query "extend" statement with this command in PySpark. This properly loads the date, which is equal to the orginal.
.withColumn(self.titles.col_date, expr("make_date(year, month, day)"))

My fix was not complete...

Still some weird edge cases to work out...

Is this single mode or distributed mode? You can see it from the loga and
read here how to enforce the mode https://github.com/Azure/azure-kusto-spark/blob/master/docs/KustoSource.md

This was in single mode, but was able to reproduce in disturbed as well on Synapse.

@dciborow
Could not manage to recreate - I tried with the following:
kustoDf  = pyKusto.read. \
            format("com.microsoft.kusto.spark.datasource"). \
            option("kustoCluster", kustoOptions["kustoCluster"]). \
            option("kustoDatabase", kustoOptions["kustoDatabase"]). \
            option("kustoQuery", "datatable(a:string)[\"3\",\"5\"] | extend TS=make_datetime(2021,05,13)"). \
            option("kustoAadAppId", kustoOptions["kustoAadAppId"]). \
            option("kustoAadAppSecret", kustoOptions["kustoAadAppSecret"]). \
            option("kustoAadAuthorityID", kustoOptions["kustoAadAuthorityID"]). \
            load()

display(kustoDf)

And the dates were UTC, regardless of the python setting.
Can you maybe share the full retrieval code?
Also, when running the query directly in kusto, does it give the answer you want?

Closed for no action


Are there any examples of specific applications?

thansk for your greate works, Are there any examples of specific applications?

https://ngc-learn.readthedocs.io/en/latest/walkthroughs/demo1_gen_models.html


other ATmega chip

hey
i want to ask - so its only ATmega32u4 project, so it will not work on arduino nano?

It is, as stated in the readme, for the ATmega32u4 only.

ah, pardon me.


Split API info into another file

It's been reported that for large code bases with thousands of files,
the Analysis object reaches the size of 100MB, mostly from the API info
blob.
This changes SameAPI.apply to use only the API hash, and thereby
removing the necessity to load previous API info during the incremental
compilation.
This also adds APIInfoStore which can be added to an existing
AnalysisStore to read/write full API info to another file. This
allows majority of the users to skip the reading of full API info
during compilation, which should help in both time and space. If needed
we can still call getWithAPI to load the full API info for API
diffing.
/cc @gkossakowski, @romanowski

As far as I understand, this change moves away zinc from operating on api objects. It switches solely to api hashes. It's pretty change big so the commit message should be expanded accordingly. The questions I think commit message should answer are:

what size of the project makes API info file so large that it's a significant performance hit to load it?
what about removed API diffs? API diffs are the key identifying tricky problems in incremental compiler, e.g.: https://github.com/sbt/zinc/issues/88 (and http://www.scala-sbt.org/0.13/docs/Understanding-Recompilation.html#Debugging+an+interface+representation)

@gkossakowski Replaced the commit to based on the review.
The subprojects I'm looking at contains 1000+ source files, which then could further expand via code generation, macro, compiler plugin etc. Also it's not uncommon for Play projects to contain dozens of subprojects, which on their own could expand as teams grow.
I've brought back the API diffing, so all you have to do is enable the flag and load the full API info, which can be done via getWithAPI on AnalysisStore vs plain get.

I did a simple test of compiling an empty class to see how much space we spend on API representation. The number I got is roughly 3.8kb. To get to 100mb of API representation you need around 25k top level classes. The API representation compresses very well using standard zip compression. I get 13.5x contraction in size.
Having said that, splitting API into a separate storage is fine. I think @smarter's latest feedback is spot on and should be addressed.

@gkossakowski @smarter Moved the with or without API info logic into the AnalysisStore.

I agree with @gkossakowski  about simple zip compression - in our we get around 10% of file caches. See my PR: #160
IMO correct way to split APIs to another files is to extract them from AnalyzedClass to separate lazy entry (map) in Analysis itself.

ok. Turned it into lazy instead of optional as per @romanowski's suggestion:
 				{
  					"name": "api",
 -					"type": "Companions"
 +					"type": "lazy Companions"
  				},

This does make the whole thing more "automatic" as read-API-or-not-to-read decision is deferred to the usage point.

@romanowski Thanks for the detailed review. I did adopt most of your suggestions, and pushing the responsibility down to TextAnalysisFormat did make the imple much cleaner. I also made the Companions storage another zip entry.

Except minor comments above LGTM


displaymanager: switch displbe and displaymanager to weston env file

Weston service is using /etc/default/weston file to populate weston
environment to the service. Displaymanager and displ_be should use the
same file because they are dependend from weston.
Signed-off-by: Oleksii Moisieiev<EMAIL_ADDRESS>

`Reviewed-by: Oleksandr Grytsov<EMAIL_ADDRESS>


Weird Viewport at the Top Left of Screen

Godot version
4.1 Stable
System information
Windows 11, RTX 3050 Laptop, 11th Gen i5, Vulkan
Issue description
For whatever reason, I seem to have a white rectangle at the top-right of the screen. I can't do anything or interact with it, and it seems to be connected to one of the viewports that I had in a different scene. I've tried manipulating the viewport's settings, but I couldn't get this resolved, and I can't access any of the project settings/the node panel to navigate through my project anymore.

Steps to reproduce
I honestly don't know what I did that resulted in this. For the MRP, I've linked the changed files since the prior commit of my project (not the actual project itself, and the prior commit worked fine, so the issue must have something to do with the new changes). I'm sorry if it's a mess, but it's better than nothing.
Minimal reproduction project
New_Commit.zip

It's hard to debug without having the full project, but the changes you linked include @tool scripts, and tool scripts run in the editor. It's probably one of those scripts adding something to the editor scene.
Notably in world_view.gd:
func _ready() -> void:
        var vp_tex:           ViewportTexture = get_camera().get_world_texture()
        var chromakey_buffer: ColorRect       = $Camera_FX/FX_VP_Radiance/FX_Buffer_ChromaKey/FX_Radiance_ChromaKey
        chromakey_buffer.material.set_shader_parameter("world_texture", vp_tex)

Ah, I see, so if you have control nodes in a scene that is run by a @tool script, then they'll render on the Editor UI itself? I haven't experienced that before, so that's why I was confused, nor did I know about it. Is there any documentation on this?

Yes, see https://docs.godotengine.org/en/latest/tutorials/plugins/running_code_in_the_editor.html
Notably, the scene tree you have in a @tool script is the editor's scene tree. That's very powerful, but with great power comes great responsibility ;)

Alright, gotcha!
I'll be closing this then.


Terminal reset required after sbt about (or any other command)

(See the guidelines for contributing, linked above)
steps
Using sbt 1.0.1, run sbt about
problem
On macOS, the terminal echo is lost, requiring a reset.
expectation
On any OS, the terminal echo is properly restored, requiring no operation.
notes
sbt version: 1.0.0
This is an adoption blocker.

Duplicate of https://github.com/sbt/sbt/issues/3453.
We'll hopefully issue hotfix release soon.


State an order for multiple alignments for the same read

The script sam_remove_duplicates_inferior_alignments_multimappers.1_5.pl puts in a dictionary/hash  the different alignments for a single read . As these store data unordered the order may change between runs - which makes the test fail when comparing the output to the checksums. So before writing out the remaining alignments for a record, a certain order should be enforced.

Well, that was my assumption. I didn't actually check if that is what's happening. We will see. Probably it's that, or something quite like it.


Fixup cargo unleash

Because the cargo-semver-incompatible release of ed25519-dalek cargo unleash fails if it tries to use the new code on the "old", released rc4. Bumping internal versions to rc5 fixes that.

Please wait until wasmtime update is in?

Will love to have those two PR shipped with rc5
https://github.com/paritytech/substrate/pull/6694
https://github.com/paritytech/substrate/pull/6695

@xlc , @NikVolf fine with delaying it by a day and keeping it as a ci-fix for now. I'll keep an eye out and start prepping rc5 once these are in. mind reviewing and signing off this one?

now that we're at it https://github.com/paritytech/substrate/pull/6693

bot merge


download-tab.js not working

1.5.658.42 linux 64-bit
i enabled download-tab.js but it still uses the sidebar and not vivaldi://downloads
any idea why or what i can try? i tested by going to:
https://www.debian.org/devel/debian-installer/
and then clicking on any of the iso images.
thanks.

vivaldi://settings/downloads/

thanks


Permit adapting plotting configuration to different drive types

SS and HD drives require different plotting parameters for optimal speed. When there is a mixture of drives in a system, there should be a way to tailor the plotting parameters for each drive type, rather than just choose one.
This could be achieved by specifying a plotting configuration for each tmp drive, and then listing multiple plotting configurations, each with a name. Then, when initiating a plot, select the named plotting configuration for the tmp drive.

Agreed this should be done.  No ETA for implementation, but thanks for filing.


chore(salt): update to datio release

This PR bumps OpenSDS-installer/salt versions to the Datio release.
Note: Upstream was updated: https://github.com/saltstack-formulas/opensds-formula/pull/108
Note: Orchestration will be tested and added in a different PR.

Added commit for macos catalina support

Closing to rebase


TaskLocal should propagate when used with Bracket Methods

Related to #806
Making PR as suggested by @oleg-py
The difference between
Task.unit
    .executeAsync
    .guarantee(local.write(10))

and
Task.unit
    .guarantee(local.write(10))

is that the former starts TaskRestartCallback twice (the first one is just after evaluating guarantee body) and the latter just once.
@alexandru If you could provide some explanation of TaskRestartCallback that would help immensely in putting all the pieces together. :) I feel like I'm getting somewhere with my understanding but there are a lot of guesses at this point

I'm merging then so we can move forward, we will revert it if it turns out to be wrong


Azure AD groups not displaying members

Describe the bug
Groups imported from Azure AD don't show it's members + users don't inherit the group roles.
To Reproduce
Steps to reproduce the behavior:

Import Azure groups (+ members)
Go to users and Groups
Select one Group that has members (0+ members - numbers are displayed)
For a split second the members are displayed but then disappear

Expected behavior
Group members should be displayed.
Screenshots
1.

3. inspect

After inserting the groups (and users) from Azure AD we have the following situation:
Good:

Users are imported;
Groups are imported;
User count in groups are shown;
groups of the user are shown.

BAD:

users of each group are not listed/shown;
users don't inherit the privileges of the groups;

Other details:

for a split second the users (members) of the group i'm opening are shown but then are overwritten visually;
when inspecting the page, one graphql lists the group+ users but after it there are multiple search results that apparently overwrite the initial result.

Thank you for reporting this! Taking a look.

I'm assuming you've imported groups using this connector? https://datahubproject.io/docs/metadata-ingestion/source_docs/azure-ad/

Also - which version of client / server are you using?

@jjoyce0510 yes, that is the connector.
DataHub CLI version: <IP_ADDRESS>
Python version: 3.9.1 (default, Jan 15 2022, 19:46:20)
[Clang 13.0.0 (clang-13<IP_ADDRESS>)]

from the deployed helm chart:
`datahub-gms:
enabled: true
image:
repository: linkedin/datahub-gms
tag: "v0.8.23"
datahub-frontend:
enabled: true
image:
repository: linkedin/datahub-frontend-react
tag: "v0.8.23"
Set up ingress to expose react front-end
ingress:
enabled: false`

Even though i've sent you the ingestion recipe i'll also paste it here for reference:
ource:
  type: "azure-ad"
  config:
    client_id: "<client_id>"
    tenant_id: "<tenant_id>"
    client_secret: "<secret>"
    redirect: "https://login.microsoftonline.com/common/oauth2/nativeclient"
    authority: "https://login.microsoftonline.com/<auth>"
    token_url: "https://login.microsoftonline.com/<tenant>/oauth2/token"
    graph_url: "https://graph.microsoft.com/v1.0"
    ingest_users: False
    ingest_groups: True
    ingest_group_membership: True
    ingest_groups_users: True
    azure_ad_response_to_username_attr: "userPrincipalName"
    azure_ad_response_to_username_regex: "(.*)"
    groups_pattern:
      allow:
        - "AMI - VPN - data_and_bi"
    users_pattern:
      allow:
        - ".*"

sink:
  type: "datahub-rest"
  config:
    server: "http://my_server:8080"

Worked with @razvan-am to identify the issue. Working on a fix now. Thanks Razvan!

Hi, thanks @jjoyce0510 . Closing the issue.

Later edit:

if for some reason the users ingestion had any errors (or dhub version bug) the ingestion records were given a "no-run-id-provided" for system metadata. In this cases, the users were not displayed in the group the membership was referring to.

Workaround: Identified the users who had these kind of issues, hard deleted them (through datahub cli) and reran the ingestion for AD group + membership.

Thanks for the update Razvan!


[question] Is there an equivalent of WorkingDirectory?

Hi.
I have a program that must be run from /usr/local. In systemd, there is WorkingDirectory as an option. Does OpenRC have something like this?

Yes, you can use the -d option for start-stop-daemon or supervise-daemon to change directories before starting the process. If you aren't using start-stop-daemon or supervise-daemon, just cd to the directory in the start() function in the script.
Let me know if that answers your question.

Ok, It works.
#!/sbin/openrc-run
pidfile=run/webd.pid
start_pre() {
       checkpath --directory --owner root:www-data --mode 0710 srv
}
start() {
       supervise-daemon --pidfile $pidfile --chdir srv --start /srv/app --group www-data
}

Question aside, is there something like start_stop_daemon_args for supervise-daemon?
supervisor=supervise-daemon
start_stop_daemon_args='--group www-data --chdir /srv'

supervise_daemon_args is the supervise-daemon equivalent of start_stop_daemon_args.
Also, you should remove your start function and use the default, so set command and set supervisor to supervise-daemon.
Take a look at the openrc-run man page and supervise-daemon-guide.md in the distribution for more information.

Sorry for the silence. It works perfectly. Thank you again.

from what i'm reading in the man page, the directory option is supposed to do exactly this (but doesn't)

Over three years have passed, I still had to add the following to my init.d/user-server
directory="${SERVER_PATH}"
start_stop_daemon_args='--group mygroup --chdir $directory'
supervisor=supervise-daemon

Running OpenRC 0.44.5 on Gentoo.

2023 - for me it seems like directory on its own is enough.
running openrc (OpenRC [LXC]) 0.47.1 on alpine 3.18

latest news-solved it with this(maybe not ideal,but works):
#!/sbin/openrc-run

name="zoraxy"
supervisor="supervise-daemon"
#directory="/opt/zoraxy"
command="./zoraxy_linux_amd64"
command_args="-port=:8000"
pidfile="/run/$SVCNAME.pid"

depend() {
        need net
        use dns
}

start_pre()
{
        cd /opt/zoraxy
}