chore: Set permissions for GitHub actions

Restrict the GitHub token permissions only to the required ones; this way, even if the attackers will succeed in compromising your workflow, they won’t be able to do much.

Included permissions for the action. https://github.com/ossf/scorecard/blob/main/docs/checks.md#token-permissions

https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#permissions
https://docs.github.com/en/actions/using-jobs/assigning-permissions-to-jobs
Keeping your GitHub Actions and workflows secure Part 1: Preventing pwn requests
Signed-off-by: naveen<EMAIL_ADDRESS>

Messages

:book:
:sparkles: Thanks for your contribution to Shields, @naveensrinivasan!

  Generated by :no_entry_sign: dangerJS against 5b03f38ffc61d281a7955b6bde2430e2d4e48a33

Thank you for the PR!
While I'm not explicitly opposed to the proposed changes, they also strike me as purely ceremonial with no value add. Any security mechanisms based on user-modifiable content in the repo are inherently self-defeating. The correct way to manage these settings is via repository settings (something GitHub's docs note in many places) where they can't be modified by anyone other than repository admins.
Additionally, GitHub doesn't propagate any repository secretes, including GITHUB_TOKEN, to runs triggered from a fork. That in turn really only left the supply chain vulnerability potential via Dependabot-style updates that were opened from an in-repo branch. However, GitHub also internally handles that risk already as noted in some of the related posts and documentation to the ones you included in the PR description.
In short, we're familiar with the material you've shared, and it was already reviewed/considered/addressed. I'd personally prefer to primarily rely on repo-setting management instead of establishing a practice of inserting duplicative, easily manipulated, keys into our various yaml files.
Will defer to the other maintainers though as to whether we should move forward with this anyway.

Thank you for the PR!
While I'm not explicitly opposed to the proposed changes, they also strike me as purely ceremonial with no value add. Any security mechanisms based on user-modifiable content in the repo are inherently self-defeating. The correct way to manage these settings is via repository settings (something GitHub's docs note in many places) where they can't be modified by anyone other than repository admins.
Additionally, GitHub doesn't propagate any repository secretes, including GITHUB_TOKEN, to runs triggered from a fork. That in turn really only left the supply chain vulnerability potential via Dependabot-style updates that were opened from an in-repo branch. However, GitHub also internally handles that risk already as noted in some of the related posts and documentation to the ones you included in the PR description.
In short, we're familiar with the material you've shared, and it was already reviewed/considered/addressed. I'd personally prefer to primarily rely on repo-setting management instead of establishing a practice of inserting duplicative, easily manipulated, keys into our various yaml files.
Will defer to the other maintainers though as to whether we should move forward with this anyway.

Ok. I understand. Thanks

I'll try and have a proper look at this next week.
I think one of the things going on here is that GitHub have recently made a change to the default permissions granted to GITHUB_TOKEN but it only applies to mew repos. i.e: if I create a new repo, GITHUB_TOKEN has "Read repository contents permission" out of the gate unless you elevate it, whereas for an older repo like ours we retain the previous default, which is that GITHUB_TOKEN has "Read and write permissions" by default. There may be some mileage in us switching our setting to the new default and elevating where necessary.
@naveensrinivasan is this PR related to that GH policy change, or independent of it?

I'll try and have a proper look at this next week.
I think one of the things going on here is that GitHub have recently made a change to the default permissions granted to GITHUB_TOKEN but it only applies to mew repos. i.e: if I create a new repo, GITHUB_TOKEN has "Read repository contents permission" out of the gate unless you elevate it, whereas for an older repo like ours we retain the previous default, which is that GITHUB_TOKEN has "Read and write permissions" by default. There may be some mileage in us switching our setting to the new default and elevating where necessary.
@naveensrinivasan is this PR related to that GH policy change, or independent of it?

It is independent of it.

merged d6df4fb in preference to this. Thanks :+1:


Provide a general summary of the issue

Prerequisites

[X] I have searched for duplicate or closed issues
[X] I have validated any HTML to avoid common problems
[X] I have read the contributing guidelines

Describe the issue
the dropdown within the navigation bar is not providing the dropdown list option.
copied code from bootstarp:

NAVBAR

Coding with Thinley

Home (current)

Features

Pricing

          Dropdown link

Action
Another action
Something else here

Reduced test cases
CHECKED ON ALL THE MULTIPLE BROWSER NOT WORKING

What operating system(s) are you seeing the problem on?
Windows
What browser(s) are you seeing the problem on?
Chrome, Firefox, Microsoft Edge
What version of Bootstrap are you using?
V4.6

You need to use our JavaScript in order to get our interactive components working. Please read the Getting started page.


Increase validate-pod timeout

I feel a timeout of two minutes is a little short (see below).
https://github.com/apprenda/kismatic/blob/master/ansible/roles/validate-pod/tasks/validate-pod.yaml#L7-L8
I am wondering if we should increase this to no longer than five minutes to allow for network connectivity issues.
@alexbrand thoughts?

Based on your recent installation experiences, I think we should increase it. We'll tackle this soon.


jQuery is required dependency

Please update the readme.
After all, it's a greak work!
Thank you.

Does this require JQuery ?

Doesn't look like it to me.


Update documentation to reference 'config.toml' instead of 'config'.

Describe the problem you are trying to solve
After #7273, we now support loading 'config.toml' and 'credentials.toml' in place of the same files without extension, which used to be the default. Files with extensions are easier for people to edit due to syntax highlighting, etc.
Describe the solution you'd like
We should update all Cargo documentation to mention 'config.toml' and 'credentials.toml' so people use those by default instead of the versions without extension.

Does this mean changing config in text like this
### Hierarchical structure

Cargo allows local configuration for a particular package as well as global
configuration. It looks for configuration files in the current directory and
all parent directories. If, for example, Cargo were invoked in
`/projects/foo/bar/baz`, then the following configuration files would be
probed for and unified in this order:

* `/projects/foo/bar/baz/.cargo/config`
* `/projects/foo/bar/.cargo/config`
* `/projects/foo/.cargo/config`
* `/projects/.cargo/config`
* `/.cargo/config`

into config.toml?
I can help with this.

Indeed yeah that'd be a great start! I suspect there are more mentions of .cargo/config in the documentation, but updating them incrementally is ok too!

@huangjiahua I believed this issue is already fixed?

@pickfire Yeah, I think so.

Oops, thanks for the ping!


Tracking protocol parameters definitions

Following discussions from CIP Editors call # 92, inspired by comments on #847 (here, here, here).
What?

Protocol parameters being to referred to with different names increases the chances of mistaken identity

This is increasingly more important under the age of Voltaire, where DReps, CC and SPOs are expected to evaluate and vote on changes to the protocol parameters.

Historically naming and description has been achieved via CIPs, such as CIP-09 | Protocol Parameters (Shelley Era)

Although continuing to track protocol parameter value settings via CIPs is probably an unnecessary burden post Voltaire

I put in a suggestion in the above referenced discussion to list & define the parameter terms on a GitHub Wiki (which would provide alphabetised [but not groupable] navigation for & sort them, without requiring a quorum of editors to update even "little" changes).
@WhatisRT had offered one of the Ledger repos (one possibly too technical to be much in the public eye) which could house a Wiki but the additional reservation came up with the community (one which I had also felt) that housing this list in a neutral territory not explicitly controlled by any Cardano entity would be considered politically neutral & perhaps better maintainable.
I was very happy to conceive at the meeting we could simply store parameters in a single file or directory starting at the root of the CIPs repository.  The existing maintainers of this parameter list (cc @lehins @Hornan7) can submit an initial PR against the repository to add a file or directory according to file/directory names & organisational principles they think are best.
The initial posting & updates will be approved by CIP editor quorum (@Ryun1 @Crypto2099) after documenting that they are valid changes from a valid source, and we will avoid the bureaucratic fatigue pointed out by @kevinhammond that I also observed: having to classify these changes through one or more CIPs, and providing agreed-upon checkpoints at era boundaries (I believe the GitHub commit history will serve just as well for the latter, when required: an idea expressed for CIPs themselves originally by @KtorZ).
The result would be easily findable and linkable, and make it possible for PR's to be filed against the file(s) by anyone in the Cardano community who thinks they have identified a mistake, as well as Issues and even Discussions if appropriate.  And of course let me reiterate that it won't be practical to store the values of these parameters in the file... being changeable soon by any governance decision... it will just provide a high profile location for unambiguous, official names & definitions.

we could simply store parameters in a single file or directory starting at the root of the CIPs repository.

If we are storing a file in the CIPs repo, it might as well be a CIP 😆
Im happy to take a swing at this, Im thinking a single CIP that is versioned/ updated per era
primarily focussing on explaining purpose of each parameter as well as its nicknames as such

having to classify these changes through one or more CIPs

I think with Conway forward, multiple CIPs is the wrong approach
Past iterations of these CIPs have tried to record the current protocol parameter values, this unnecessarily adds burden, and would be difficult to maintain post post Chang

And of course let me reiterate that it won't be practical to store the values of these parameters in the file...

100% agree

@Ryun1 it sounds like it would work well that way.  The main composers & reviewers in the "old days" of the parameter CIPs (@kevinhammond @KtorZ @JaredCorduan) would recall the irreconcilability that led to abandonment of the process... but the two key differences of a single CIP + no recorded values would avoid the main point of contention as I recall: whether to update prior CIPs with new ledger eras or create new ones.
I also think your approach could be more readable by implementors and governance participants, allowing them to see an evolution over time... not so important that it's in the same document, but rather that they won't have to switch with each ledger era CIP to a differently authored document having different style and organisation.


feat: implement input and output sections in the experimental parser.

This commit implement parsing of input and output sections in the experimental
parser for both tasks and workflows.
Also implemented is the caching of a lexer peek operation which prevents the
lexer from having to tokenize the input again.
The expect* methods of Parser now peek and move next only if the token
matches what's expected; this will prevent consuming recovery tokens in
recovery contexts.
Before submitting this PR, please make sure:

[x] You have added a few sentences describing the PR here.
[x] You have added yourself or the appropriate individual as the assignee.
[x] You have added at least one relevant code reviewer to the PR.
[x] Your code builds clean without any errors or warnings.
[x] You have added tests (when appropriate).
[x] You have updated the README or other documentation to account for these
changes (when appropriate).
[x] You have added an entry to the relevant CHANGELOG.md (see
"keep a changelog" for more information).

[x] Your changes are squashed into a single commit (unless there is a really
good, articulated reason as to why there should be more than one).

This PR needs #43 to merge first, at which point I'll rebase this to simplify the review.


fixed spacing in README.md

Fixed spacing in README.md

Thanks for correcting that 👍

Thanks for correcting that +1

Thank you for making such an amazing library<3


Awfully misleading code folding on if statements.

Environment data
VS Code version: Version: 1.81.1 (user setup)
C# Extension version: v2.0.436
Steps to reproduce

Create a new .cs file with the following code:

long foo = new Random().Next(1,10);
if (foo == 1) {
	Console.WriteLine("Foo is totally one");
} else {
	Console.WriteLine("Foo is absolutely not one").
}

Note: The bracket style is important.

Fold the if statement.

Expected  behavior
Line 3, with the "Foo is totally one" writeline gets folded in and hidden, while preserving the } else { to make it clear when the still visible line 5 is executed.
Actual behavior
The code fold is really misleading if one does not notice that the fold is active:
Before:

After:

Additional context
I know that the bracketing style in this example is not the recommended style. But there is no reason for the folding to behave like this. :)
I also tried the same scenario in JavaScript in VS Code and the misleading fold does not happen there.

@StringEpsilon are you expecting that the folding does not include the else?  e.g.
folded output:
if (foo == 1) {...
} else {
    <>
}


the argument name HP may be wrong?

Should the HP be IV_DEF? If not, then the usage in DpsTable.js is wrong.
https://github.com/WHIZENx/PokeGoBreeze/blob/81b932b84f2a90421110bf1991956bcc55c55e52/src/components/Calculate/Calculate.js#L593

Sorry, I was wrong


Adapting partial code(file name start with S #1) to the sonar cloud rule

Codecov Report

Merging #2264 into dev will decrease coverage by 1.53%.
The diff coverage is 28.49%.

@@             Coverage Diff              @@
##                dev    #2264      +/-   ##
============================================
- Coverage     31.95%   30.42%   -1.54%
- Complexity     1511     1663     +152
============================================
  Files           311      337      +26
  Lines         15402    17827    +2425
  Branches       1864     2238     +374
============================================
+ Hits           4922     5424     +502
- Misses         9968    11846    +1878
- Partials        512      557      +45

Impacted Files
Coverage Δ
Complexity Δ

...heduler/alert/manager/EnterpriseWeChatManager.java
0.00% <0.00%> (ø)
0.00 <0.00> (ø)

...duler/alert/template/impl/DefaultHTMLTemplate.java
77.55% <ø> (ø)
13.00 <0.00> (+1.00)

...inscheduler/alert/utils/EnterpriseWeChatUtils.java
0.00% <0.00%> (ø)
0.00 <0.00> (ø)

...apache/dolphinscheduler/alert/utils/FuncUtils.java
91.66% <ø> (ø)
5.00 <0.00> (ø)

...che/dolphinscheduler/api/ApiApplicationServer.java
33.33% <ø> (ø)
1.00 <0.00> (ø)

...onfiguration/ServiceModelToSwagger2MapperImpl.java
0.81% <0.00%> (ø)
1.00 <0.00> (ø)

...scheduler/api/controller/AlertGroupController.java
3.57% <0.00%> (-0.52%)
2.00 <0.00> (ø)

...heduler/api/controller/DataAnalysisController.java
5.40% <0.00%> (ø)
2.00 <0.00> (ø)

...scheduler/api/controller/DataSourceController.java
2.19% <0.00%> (ø)
2.00 <0.00> (ø)

...inscheduler/api/controller/ExecutorController.java
6.25% <0.00%> (ø)
2.00 <0.00> (ø)

... and 144 more

Continue to review full report at Codecov.

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

please solve Conflicting files locally, thx

meaningless to reslove these conflicts ,close this pr


No detection of cycles in directory structure

(See the guidelines for contributing, linked above)
steps
Create a file structure with cycles (using symbolic links) in the root directory or elsewhere (e.g., in the test resources).
problem
sbt runs forever trying to traverse this structure.
expectation
sbt should check for cycles so it can handle such a structure (like most unix commands do).
notes
In writing a system that does deal with cycles, I need to set up directories with cycles for testing purposes.  I don't know where to put them so it won't confuse sbt.
sbt version: 1.0.1

I am closing this due to inactivity. This might be a legitimate issue but it's unlikely we'd dedicate resource to fix this unless it's found to be a prevalent issue. Contribution to investigate would be welcomed.

I am closing this due to inactivity. This might be a legitimate issue but it's unlikely we'd dedicate resource to fix this unless it's found to be a prevalent issue. Contribution to investigate would be welcomed.

I can't even reproduce the problem right now, so it's definitely nothing crucial. If it happens again, I'll try to investigate.


chore: remove vitest import for the global options

Description
Because the config in vitest.config.e2e.ts of globals is true, so the import synatx was unsless.
Additional context

What is the purpose of this pull request?

[ ] Bug fix
[ ] New Feature
[ ] Documentation update
[x] Other

Before submitting the PR, please make sure you do the following

[ ] Read the Contributing Guidelines.
[ ] Read the Pull Request Guidelines and follow the Commit Convention.
[ ] Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
[ ] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
[ ] Ideally, include relevant tests that fail without this PR but pass with it.

Thanks for the PR @fireairforce!
@antfu would you prefer we keep using globals: true, or are these imports a WIP to remove this flag in the future?

I think globals: true is intended to be removed in future.
https://github.com/vitejs/vite/blob/d35a1e2b828dfe2ef89bd235b3594b797d9ee7a1/playground/test-utils.ts#L4

Thanks for the reference @sapphi-red. @fireairforce closing this PR as the current imports are intended then. If you would like to send PRs to go in the other direction so we are able to remove the globals flag, contribution welcome.

Why remove global api here? it's not recommend ?


chore: track delays when context switching between fibers

This metric should help us measuring responsiveness of fiber switching.

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

Comparison is base (fe7ec28) 77.54% compared to head (0a5d3e5) 77.51%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##           master     #165      +/-   ##
==========================================
- Coverage   77.54%   77.51%   -0.04%
==========================================
  Files          98       98
  Lines        7197     7209      +12
==========================================
+ Hits         5581     5588       +7
- Misses       1616     1621       +5

Files
Coverage Δ

util/fibers/detail/fiber_interface.h
92.59% <ø> (ø)

util/fibers/detail/fiber_interface_impl.h
100.00% <ø> (ø)

util/fibers/detail/scheduler.cc
97.68% <100.00%> (+0.04%)
:arrow_up:

util/fibers/detail/scheduler.h
100.00% <ø> (ø)

util/fibers/epoll_proactor.cc
87.79% <100.00%> (-1.36%)
:arrow_down:

util/fibers/fiber2.h
85.71% <ø> (ø)

util/fibers/uring_proactor.cc
60.90% <100.00%> (+0.09%)
:arrow_up:

util/fibers/detail/fiber_interface.cc
89.57% <86.66%> (-0.63%)
:arrow_down:

... and 2 files with indirect coverage changes

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


Update instruction for notebook: Import Package from Stage

On the "Upload the package using the Package Picker UI" step the instructions are as follow:

Now that the simple.zip package is on the stage, we can specify the path to this package in the Package Picker.
Click on the Packages dropdown
Navigate to Stage Packages tab
Enter the Stage Package Path as: @MY_PACKAGES/simple.zip_
Running cell
import simple
Returns error:
ModuleNotFoundError: Line 1: Module Not Found: simple. To import packages from Anaconda, install them first using the package selector at the top of the page.
In order to fix the issue, the instructions should be updated as per below:
The last step "Enter the Stage Package Path as" should be
Enter the Stage Package Path as (all lowercase): @..my_packages/simple.zip where . is the actual namespace of the stage

Thanks @sashamitrovich! This is fixed now.


Update every icon to Material Design guidelines

The current icons across ODK-X tools are inconsistent. There's a need for each icon to be updated to meet Material Guidelines.
Why this needs to be improved:

The icons used in the apps are not consistent.
Similar icons are used repeatedly for different actions which can confuse users.
Example:

Guidance for this issue:
Update the icons to meet the standards in Material icons

I put all the icons used during the 'Design Custom UI Components' project to meet the standards in Material Icons.
Here's the update on the ODK-X Design Guidelines:
.
Specifications

All icons are 24px in size.
Stroke colours vary depending on the context, but are within the range of colours in this Design Guidelines.

I put all the icons used during the 'Design Custom UI Components' project to meet the standards in Material Icons.
Here's the update on the ODK-X Design Guidelines:

Specifications

All icons are 24px in size.
Stroke colours vary depending on the context, but are within the range of colours in this Design Guidelines.

Hi,
If this is still open I'd like to attempt it


[logger] Adding react-native logger support

Packages impacted by this PR

@azure/logger

Issues associated with this PR

#30065

Describe the problem that is addressed by this PR
Adds logging support through the browser implementation of the logger logic.
What are the possible designs available to address the problem? If there are more than one possible design, why was the one in this PR chosen?
Are there test cases added in this PR? (If not, why?)
Provide a list of related PRs (if any)
Command used to generate this PR:**(Applicable only to SDK release request PRs)
Checklists

[ ] Added impacted package name to the issue description
[ ] Does this PR needs any fixes in the SDK Generator?** (If so, create an Issue in the Autorest/typescript repository and link it here)
[ ] Added a changelog (if necessary)

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

/check-enforcer evaluate


removes planner limitations on order/group/aggregate on INDEX OFF cols

this was an artificial planner limitation: grouping, aggregates and
ordering requires doc_values but no index.

Codecov Report

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

@@             Coverage Diff              @@
##             master    #6594      +/-   ##
============================================
- Coverage     83.08%   83.02%   -0.06%
+ Complexity    13257    13244      -13
============================================
  Files          1520     1520
  Lines         49230    49222       -8
  Branches       5911     5908       -3
============================================
- Hits          40901    40868      -33
- Misses         5548     5565      +17
- Partials       2781     2789       +8

Impacted Files
Coverage Δ
Complexity Δ

...ava/io/crate/planner/node/dql/GroupByConsumer.java
84.37% <ø> (-1.34%)
12 <0> (ø)

...java/io/crate/planner/operators/HashAggregate.java
92.3% <ø> (-0.23%)
14 <0> (ø)

...a/io/crate/analyze/relations/DocTableRelation.java
92.85% <ø> (-0.37%)
22 <0> (ø)

...arch/indices/recovery/BlobStartPrefixResponse.java
66.66% <0%> (-33.34%)
3% <0%> (-2%)

...in/java/io/crate/lucene/match/CrateRegexQuery.java
43.47% <0%> (-30.44%)
4% <0%> (-4%)

...o/crate/analyze/SafeExpressionToStringVisitor.java
83.33% <0%> (-16.67%)
7% <0%> (-1%)

...rc/main/java/io/crate/analyze/UnboundAnalyzer.java
78.94% <0%> (-7.9%)
2% <0%> (ø)

...tor/transport/distributed/ModuloBucketBuilder.java
73.68% <0%> (-5.27%)
10% <0%> (-1%)

...otocols/postgres/RetryOnFailureResultReceiver.java
88.46% <0%> (-3.85%)
10% <0%> (-1%)

...io/crate/planner/operators/GroupHashAggregate.java
90.56% <0%> (-3.78%)
18% <0%> (-1%)

... and 14 more

Continue to review full report at Codecov.

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


Return new Observables instead of using compose with Transformers

Current use of transformers is incorrect, as I'm not actually returning the result of applying a bunch of operators to an upstream Observable. This can result in weird behavior/race conditions if schedulers are used in certain ways (e.g., if the upstream observable emits on a background thread while the outer observable emits on the main thread). Since my current use doesn't fit the compose transformer contract, I probably shouldn't use it.

I'm actually not 100% that this is true.


expand header extra data

change the header store struct

Aim to give extra data for expand

replaced by PR #86


Run make for install/kubernetes/quick-start.yaml

Please ensure your pull request adheres to the following guidelines:

[ ] For first time contributors, read Submitting a pull request
[ ] All code is covered by unit and/or runtime tests where feasible.
[ ] All commits contain a well written commit description including a title,
description and a Fixes: #XXX line if the commit addresses a particular
GitHub issue.
[ ] All commits are signed off. See the section Developer’s Certificate of Origin.
[ ] Provide a title or release-note blurb suitable for the release notes.
[ ] Thanks for contributing!

Running make in install/kubernetes dir produces a different file than the checked in version.

This change is

Coverage decreased (-0.03%) to 45.927% when pulling 541e927aa4977827b3e67ac578dbcfe8fa204b9e on frelon:make-kubernetes-config into 078f19d6b52ebc099edc2ed2a48a25818b6e4a56 on cilium:master.

test-me-please

A CI provisioning failure. Re-running.

test-me-please

The provisioning failed again:
[2019-12-16T12:21:46.042Z]     k8s1-1.11: docker build --build-arg LOCKDEBUG=1 -f cilium-operator.Dockerfile -t "cilium/operator:"latest"" .
[2019-12-16T13:04:24.182Z] Cancelling nested steps due to timeout

test-me-please

CI provisioning issue again. Re-running.

test-me-please


Add some useful information to the README.md

+1 on this. It would be great to simply have the output from 'aws_with --help' here so folks can understand how it works and what it can do before actually installing it.


'CPPFLAGS=-I/absolute/path/to/../Python-3.4.2/FIXLOCALE' not work!!

I followed your step to compile python for android x86, my host is Ubuntu 14.04 x86_64 with ndk_r11
I completed the step of build NDK toolchains and Python-3.4.2 in the README.md;
when I got to the step :
CPPFLAGS=-I/absolute/path/to/../Python-3.4.2/FIXLOCALE ../Python-3.4.2/configure --enable-shared --prefix=/absolute/path/to/install/directory --build=x86_64-linux-gnu --host=i686-linux-android --disable-ipv6 ac_cv_file__dev_ptmx=no ac_cv_file__dev_ptc=no ac_cv_little_endian_double=yes --without-ensurepip
I find the part of log out as followed :
checking wchar.h usability... no
checking wchar.h presence... no
checking for wchar.h... no
checking for UCS-4 tcl... no
and in the file build-for-android/pyconfig.h I found the line #1270~1271 is
/* The size of 'wchar_t', as computed by sizeof. */
/* #undef SIZEOF_WCHAR_T */
then after patch and make, there is compile error happend.
So i guess that the compile config 'CPPFLAGS=-I/absolute/path/to/../Python-3.4.2/FIXLOCALE' does not work, and configure script not find the files 'wchar.h, locale.h, langinfo.h' in the FIXLOCALE.
I have no idea to fix that, please give me some advise.
Thank you! :-)

I have resolve this question. It seems that the file 'FIXLOCAL/wchar.h' have syntax error in the line #64 :
#include <sys/_types.h>
there is no file named _types.h, so you should modify it to :
#include <sys/types.h>
and you have to add your ndk toolchains path of sysroot to you configure by --sysroot


refactor: convert module to use @nuxt/kit

Only notable change is moving async -> sync fs operations due to current unctx approach. (other ideas welcome)

Please don't advocate kit on community repos until we have public documentation.


Limit German CO2 sequestration in each investment year

Extend the functions add_{min/max}_limits in additional_functionality.py to allow stores.
Add limits to DE CO2 sequestration based on feasibility constraints.
E.g. since EU target for 2030 is 50 MtCO2/a sequestration in Net Zero Industry Act, limit DE to 10 MtCO2/a, then relax with subsequent years.
For 365H resolution, this limit reduced sequestration in DE in 2030 from 55 to 10 MtCO2, while increasing system costs by 0.3%. The limit in 2045 reduced sequestration in DE from 97 to 50 MtCO2, while increasing system costs by 2.5%.
Before asking for a review for this PR make sure to complete the following checklist:

[x] Workflow with target rule ariadne_all completes without errors
[x] The logic of export_ariadne_variables has been adapted to the changes
[ ] One or several figures that validate the changes in the PR have been posted as a comment
[ ] A brief description of the changes has been added to Changelog.md
[ ] The latest main has been merged into the PR
[ ] The config has a new prefix of the format YYYYMMDDdescriptive_title

Unfortunately this PR wasn't based on the latest main and diverges quite a bit, because the add_min_limit function has changed in #154 . We should probably redo the code changes and while we are at it unify add_min_limit with add_max_limit

This PR now superceded by https://github.com/PyPSA/pypsa-ariadne/pull/170.


Add HostTable interface to allow wielding of host tables in native code

Depends upon rapidsai/cudf#16784.
Adds a host version of cudf::table_view and cudf::column_view so we can examine and construct tables in host memory, along with APIs to construct a contiguous device table from a host table.  This makes it easier to move some host processing code from Java into native code to avoid excessive object creation for very wide and/or deeply nested table schemas.

build


Does execute_command works for the commands implemented in redis-ml module ?

Hi, I am loading the redis-ml module using execute_command('LOAD MODULE', 'path to the module). After that when I try to use commands in that module I am getting command not found exception. Do I need to modify anything in the client.py ?

Few commands are working if I load the module while creating the cluster. Working commands are ML.MATRIX.SET, ML.MATRIX.GET. But ML.MATRIX.ADD not working and throwing the exception redis.exceptions.ResponseError: WRONGTYPE Operation against a key holding the wrong kind of value. Does any one have any idea regarding this?

@SrujithPoondla Can you list all the internal redis methods that redis-ml wants to use from the normal redis lib? Some commands have changed when working in a redis cluster env.
I see one of 4 scenarios why this happens

redis-ml uses a normal redis command wrongly by sending in a data structure that it do not support
redis-py-cluster have reimplemented a command wrongly
redis-ml is not cluster compatible
You are using redis-ml wrong

It would also help if you can post the entire exception and start to dig around if the problem is in redis-ml or in this lib or down the stack inside reids-py itself. Example code for error reproduction could also help.

Hi @Grokzen  Thanks for the info. Currently, Redis-ML doesn't support cluster. In my case, the error was trying to use ADD command from ml module. But in the cluster scenario, one matrix might be in one node and another in a different node. So it was failing with default ml module. I modified the module to my own use cases with cluster support. It's working now! 👍

@SrujithPoondla You should try to get support for cluster merged into redis-ml if possible.

@Grokzen Sure, I will do that sometime this weekend.


Error "Cannot read properties of undefined (reading 'size')" when Participant leaves

Describe the bug
Error "Cannot read properties of undefined (reading 'size')" when Participant leaves

Reproduction
I encounter this error every time a user leaves the room.
Logs
No response
System Info
Chrome Version 124.0.6367.119 (64-bit)

Severity
serious, but I can work around it
Additional Information
No response

Is this a recent version? The API changed and you have to use room.remoteParticipants now. See migration guide

The error appears in the source code of the package @livekit/egress-sdk. I tried installing this package with the command: 'npm i @livekit/egress-sdk@latest'. In the package.json, it shows version 0.2.0. Is this the latest version?


rust-toolchain files take precedence over input

Thanks for this action!
I just migrated from the actions-rs one and there the input overriden the rust-toolchain file. wondered if we can do the same here?

Prioritizing the rust-toolchain makes more sense to me. After all, you use a toolchain file if you want to control the Rust version of any contributor and consumer of a project. That does include CI. Why do you want to use a different toolchain?

Our use case is that we have a rust toolchain file for pinning the channel (nightly-date) but in the CI we compile against various targets so we'd want to use the action to install specific targets for each build.

If I understand you correctly, you want to pin the tool chain version, but in your CI environment you want to use more/different targets. In that case maybe merging the two sets of target definitions is a better option. Having more targets available should not be downside. Concretely that means first getting rustup to install everything given in the rust-toolchain file. Then callinhg rustup to add all the targets which are given to the action via the input.

I added support for installing additional targets and components via input parameters in #19.

Hi, I have the same problem in avr-hal.  There is a rust-toolchain.toml at the root of the repository which is used for building most things.  However, one component (ravedude) is built with a different toolchain which is specified in a rust-toolchain.toml file in the relevant subdirectory.
In the CI job, however, setup-rust-toolchain always uses the toolchain from the root rust-toolchain.toml and I can't find a way to override it for this one job.

@Rahix Could you please open a separate issue for that? You case is different because you have multiple toolchain files, instead of installing extra targets.


Update to gs 9.54.0

Checklist

[x] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin, please rerender

It looks like there is a bug that prevents building on osx64.

Thanks @FelixMoelder . If the fix for the bug is merged in GhostScript, personally I would be happy to apply it here using a (number of) patch(es) here.

Thanks @FelixMoelder . If the fix for the bug is merged in GhostScript, personally I would be happy to apply it here using a (number of) patch(es) here.

I just tried to apply the referenced changes as a patch but building still keeps failing.
Looking at the release notes states the following:

Mainly due to time constraints, we only support including Tesseract from source included in our release packages, and not linking to Tesseract/Leptonica shared libraries. Whether we add this capability will be largely dependent on community demand for the feature.

I am not that much into C to tell if this might be related to the issue.
Still, one way to get this building on osx is to disable Tesseract by adding --without-tesseract

I am not that much into C to tell if this might be related to the issue.
Still, one way to get this building on osx is to disable Tesseract by adding --without-tesseract

It is a bit surprising / disappointing that the patch did not solve things. BTW, I assume that you tried locally on your mac, because I could not find a trace here.
I'm not sure what would the limitation of --without-tesseract ?

Hi! This is the friendly automated conda-forge-linting service.
I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.
Here's what I've got...
For recipe:

Selectors are suggested to take a <two spaces>#<one space>[<expression>] form. See lines [23]

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

I am not that much into C to tell if this might be related to the issue.
Still, one way to get this building on osx is to disable Tesseract by adding --without-tesseract

It is a bit surprising / disappointing that the patch did not solve things. BTW, I assume that you tried locally on your mac, because I could not find a trace here.
I'm not sure what would the limitation of --without-tesseract ?

You are right, I tried it locally as I did not want to mess around with the PR trying several stuff.
Finally, I got it working by just adding tesseract as dependency for osx.
That's a bit confusing to me as the release note states that tesseract must be part of the gs source-package and shared libraries do not work.

I am not that much into C to tell if this might be related to the issue.
Still, one way to get this building on osx is to disable Tesseract by adding --without-tesseract

It is a bit surprising / disappointing that the patch did not solve things. BTW, I assume that you tried locally on your mac, because I could not find a trace here.
I'm not sure what would the limitation of --without-tesseract ?

You are right, I just tried it locally to keep this PR more or less clean.
Still I could try to apply the patch here as I only have a Apple Silicon device but as the error is identical I don't think the architecture makes a difference.

I am not that much into C to tell if this might be related to the issue.
Still, one way to get this building on osx is to disable Tesseract by adding --without-tesseract

It is a bit surprising / disappointing that the patch did not solve things. BTW, I assume that you tried locally on your mac, because I could not find a trace here.
I'm not sure what would the limitation of --without-tesseract ?

Indeed, I only tested it locally in order to not mess to much with the PR history to get this running.
But I will give it a try here as I only have a osx-arm64 device for testing.
It looks like tesseract is required to enable OCR features in ghostscript.

I am running out of ideas now.
With the latest patch (see commit) I was able to build ghostscript manually (./configure, make clean, make).
When trying to build via conda build locally I receive multiple different errors than initially.
But the CI still keeps failing with the same error...

@FelixMoelder Honestly I'm quite at loss too. Maybe the other maintainers still have ideas @ocefpaf @leouieda ? Otherwise we need to seek wider help:

https://gitter.im/conda-forge/conda-forge.github.io
Registering a bug with ghostscript itself

macOS is always a bit painful and I don't have one to test locally.  Maybe we can try a newer sdk?
https://conda-forge.org/docs/maintainer/knowledge_base.html#requiring-newer-macos-sdks

For reference I also found this : https://stackoverflow.com/questions/10116724/clang-os-x-lion-cannot-find-cstdint . The proposed solution is to compile with -stdlib=libc++. This, however, seems to be done already...

macOS is always a bit painful and I don't have one to test locally. Maybe we can try a newer sdk?
https://conda-forge.org/docs/maintainer/knowledge_base.html#requiring-newer-macos-sdks

I will give it a try.
As conda_build_config.yaml does not already exist I assume that it is fine to add it manually.

@conda-forge-admin, please rerender


fix #078 : remove unused conformanceValue'default' field

fix issue where InteractionClient.d.ts has errors due to typescript build default field. -see #078

Thank you ... I will bring in "set" support soon :-)


C-CANCEL-GET, C-CANCEL-MOVE, C-CANCEL-FIND not available to Association

The DIMSE-C cancel services are not available and need to be implemented.

Added in a848f50aeb957f242a66db000ae314ea6b4c44ec


Fix Styling of Create Button in Navbar. 📌

The create button styling is not proper which is present on the Navbar.

It's little bit large I guess relative to other buttons in navbar. Is that the only problem?
Or will it be fine It gets completely changed?

@scove-viber
Make it look different and highlighted from others
Assigned to you! 🚀

@scove-viber What's the update?

Hey @Spyware007
I would like to work on this. Please assign me this under GSSOC'23.
my proposed change:

@Naina047 Someone has already been assigned to this issue. Kindly look for other ways to contribute.

Didn't he removed his assignment?

check #1594


ReforgingTable only on Server wrong attributes on gear

Hello, i am playing ATM9 and it uses Apotheosis version 7.2.2 and i noticed that when i reforge an item it ends up getting change to something different than what was displayed in the reforging table. i tested it on single player and there it was all fine and as its supposed to be.i hope that github is the correct way to inform about this bug and i hope the images help to show the issue(3pictures always belong toghether[before/changeInto/result]):

See https://github.com/Shadows-of-Fire/Apotheosis/issues/1145

Duplicate of #1145


Create a CAT db based on the Genome Taxonomy Database

Hi @bastiaanvonmeijenfeldt ,
I was thinking it would be nice to have a CAT db based on the Genomes Taxonomy Database ( https://gtdb.ecogenomic.org/ ).
This will lose some of the comprehensiveness of having everything in there, but the presence of a phylogeny might add some value downstream.
This could either mean:

Translate NCBI to GTDB based on the metadata that is provided on their repos and just re-label assignments based on that
Create sequence sets for DIAMOND and all the ncbi-to-gtdb mappings and feed those to CAT prepare.

Option 1 might be tricky since some lineages are reassigned based on phylogeny and there is not always a 1-to-1 relationship with the NCBI TaxID.
E.g. 562 from NCBI (species, E. coli) gets split into different lineages in GTDB
d__Bacteria;p__Proteobacteria;c__Gammaproteobacteria;o__Enterobacterales;f__Enterobacteriaceae;g__Escherichia;s__Escherichia coli
d__Bacteria;p__Proteobacteria;c__Gammaproteobacteria;o__Enterobacterales;f__Enterobacteriaceae;g__Escherichia;s__Escherichia flexneri
d__Bacteria;p__Proteobacteria;c__Gammaproteobacteria;o__Enterobacterales;f__Enterobacteriaceae;g__Escherichia;s__Escherichia dysenteriae
d__Bacteria;p__Proteobacteria;c__Gammaproteobacteria;o__Enterobacterales;f__Enterobacteriaceae;g__Escherichia;s__Escherichia coli_D (<- is that D intended?)

Hi @bastiaanvonmeijenfeldt ,
I made a start here:
https://github.com/MGXlab/gtdb2cat
In principle, most requirements for CAT prepare input are now met. I am probably missing some  taxonomies, because there are no protein files for their respective genomes (yet?) but I still need to get the numbers (which ones, how many etc).
Let me know if you have a look and you see something off.
I am currently finalizing the inputs and I 'll give the database creation a go.
Any ideas on how we should validate/compare/benchmark this to the standard nr?

Hey there, @papanikos :)
Thanks for all your thoughts and work towards this!
I am currently writing up work characterizing metagenomes at the whole-metagenome level and at the MAG-level. And did my contig/gene tax classification with CAT NCBI and my MAG classification with GTDB. Since I am ending up discussing both quite a bit, I am currently facing the decision if i want to just leave things this way (discontinuity in the two taxonomies used) or try to make a CAT db based on gtdb like you've been working on. (I'm sure this is a common situation for many folks)
I was wondering if you've now tried the GTDB CAT db you created and documented on the github you linked? And how it worked out for you?
Thanks!

Hey @AstrobioMike ,
I had to leave things as they were. Which means, I still have to build the index and test it with some data.
I still haven't gotten around to selecting a dataset for a fair comparison. I was thinking of using a couple of the datasets from the CAT paper (CAMI).
If you think you want something more specific for your own data, I can probably just share the index and the taxonomy files with you - once they are ready-  so you can run your own data and have a more "concrete" discussion.

Hey, @papanikos,
I would love if you would share them with me once you create them. I hadn't actually started looking at what it would take to do this yet, and looking through your excellent documentation now is making me realize how much time you've already saved myself and others.

Hi @bastiaanvonmeijenfeldt ,
I 'd like your opinion on the following:
I run into an issue with CAT prepare and my "artificially" created taxonomy files.

The message I was getting, from the log file

[2021-07-28 10:21:46] Done! File ./CAT_database.2021-07-26/2021-07-28.nr.fastaid2LCAtaxid is created. 0 of 789,051,089 headers (0.0%) corrected. 789,051,089 headers (100.0%) do not have a taxid assigned.

All the input sequences were left without a taxid. Initially I just ignored it, as any self-respecting bioinformatician would do, but then CAT was unable to assign anything.
Long story short:
I ended up patching the  tax.find_lineage() function with an extra if block
def find_lineage(taxid, taxid2parent, lineage=None):
    if lineage is None:
        lineage = []

    lineage.append(taxid)

    if taxid2parent[taxid] == taxid: # This is never true in my case
        return lineage

    elif taxid2parent[taxid] == '1' :    # Root is the parent now
        lineage.append('1')    # Root is not in the list yet. Put it in there.
        return lineage    # Just give me what you have

    else:
        return find_lineage(taxid2parent[taxid], taxid2parent, lineage)

Do you see an issue with this? I don't, because now it works, but maybe your experience with dealing with this tells us otherwise.
Do you think it is worth a pull request to be included in the official releases? Would it cause an issue with the official NCBI taxonomy, which was designed for? Maybe also turn it into a proper ERROR when something like this happens?


cant set up environment

mamba env create -f environment.yml
pytorch/linux-64                                            Using cache
pytorch/noarch                                              Using cache
nvidia/linux-64                                             Using cache
nvidia/noarch                                               Using cache
conda-forge/linux-64                                        Using cache
conda-forge/noarch                                          Using cache
pkgs/main/linux-64                                            No change
pkgs/main/noarch                                              No change
pkgs/r/linux-64                                               No change
pkgs/r/noarch                                                 No change
nvidia/label/cuda-11.8.0/linux-64                             No change
https://aws-ml-conda-pre-prod-ec2.s3.us-west-2.a..            No change
nvidia/label/cuda-11.8.0/noarch                               No change
https://aws-ml-conda-pre-prod-ec2.s3.us-west-2.a..            No change
Looking for: ['cudatoolkit=11.6.0', 'cupy=10.4.0', 'faiss-gpu=1.7.2', 'fastparquet=0.5.0', 'nccl=<IP_ADDRESS>', 'pip=22.3.1', 'pyarrow=8.0.0', 'python=3.10.9', 'python-snappy=0.6.1', 'pytorch=1.13.1', 'pytorch-cuda=11.6', 'snappy=1.1.9', 'torchaudio=0.13.1', 'torchvision=0.14.1']
Could not solve for environment specs
Encountered problems while solving:

package nccl-<IP_ADDRESS>-h1a5f58c_0 is excluded by strict repo priority
package fastparquet-0.5.0-py36h92226af_0 requires python_abi 3.6.* *_cp36m, but none of the providers can be installed
package faiss-gpu-1.7.2-py3.6_h98e120b_0_cuda10.2 requires libfaiss 1.7.2 hdbd6f0c_0_cuda10.2, but none of the providers can be installed

The environment can't be solved, aborting the operation

Also having a problem with env setup.  Intially installed on my 22.04 ubuntu desktop and it work without issue. Did a fresh install of 22.04 desktop on a new machine and get the following error:
Could not solve for environment specs                                                                                The following packages are incompatible                                                                                ├─ fastparquet 0.6.3**  is installable with the potential options                                                                                │  ├─ fastparquet 0.6.3 would require                                                                                │  │  ├─ python >=3.6,<3.7.0a0 , which can be installed;                                                                                │  │  └─ python_abi 3.6.* *_cp36m, which can be installed;                                                                                │  ├─ fastparquet 0.6.3 would require                                                                                │  │  ├─ python >=3.7,<3.8.0a0 , which can be installed;                                                                                │  │  └─ python_abi 3.7.* *_cp37m, which can be installed;                                                                                │  ├─ fastparquet 0.6.3 would require                                                                                │  │  ├─ python >=3.8,<3.9.0a0 , which can be installed;                                                                                │  │  └─ python_abi 3.8.* *_cp38, which can be installed;                                                                                │  └─ fastparquet 0.6.3 would require                                                                                │     ├─ python >=3.9,<3.10.0a0 , which can be installed;                                                                                │     └─ python_abi 3.9.* *_cp39, which can be installed;                                                                                └─ python 3.10.9**  is uninstallable because there are no viable options                                                                                ├─ python 3.10.9 conflicts with any installable versions previously reported;                                                                                └─ python 3.10.9 would require                                                                                └─ python_abi 3.10.* *_cp310, which conflicts with any installable versions previously reported.
both desktops have the same version of python installed: 3.10.6.
thanks
Darrin

seemed to have fixed it by install python 3.9, odd i didn't have to do that on the first install.

Didn't really work in the end, seems to be an issue with python3.10.6 and/or Ubuntu 22.04. A fresh server install gives the same above error as a fresh desktop install.

In my environment wsl2 I needed to downgrade to python 3.9 and upgrade to pytorch-cuda=11.7:
$ uname -r
<IP_ADDRESS>-microsoft-standard-WSL2
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 20.04.3 LTS
Release:        20.04
Codename:       focal

conda install pytorch==1.13.1 torchvision==0.14.1 torchaudio==0.13.1 pytorch-cuda=11.7 -c pytorch -c nvidia
Also, I had to pass in memory parameters to run on my RTX 3060 12gb
 python inference/bot.py --model togethercomputer/Pythia-Chat-Base-7B -g 0:11 -r 30
first number is VRAM limit (11gb), second is cpu RAM (30gb)

Thanks, it installed cleanly on Ubuntu 20.04.  I do have it installed on a 22.04 instance but that was a two or three weeks ago, so perhaps something has changed in the meantime.

I have a similar (same?) issue.
this is my output:

~/OpenChatKit$ mamba env create -f environment.yml
nvidia/noarch                                        3.5kB @  35.1kB/s  0.1s
pytorch/noarch                                      10.2kB @  96.5kB/s  0.1s
nvidia/linux-64                                    120.2kB @   1.0MB/s  0.1s
pytorch/linux-64                                   167.3kB @   1.1MB/s  0.2s
pkgs/main/noarch                                   822.9kB @   1.9MB/s  0.4s
pkgs/r/linux-64                                      1.4MB @   2.5MB/s  0.5s
pkgs/r/noarch                                        1.3MB @   2.3MB/s  0.6s
pkgs/main/linux-64                                   5.7MB @   3.5MB/s  1.5s
conda-forge/noarch                                  12.2MB @   4.5MB/s  3.7s
conda-forge/linux-64                                31.4MB @   4.4MB/s 10.6s

Looking for: ['cudatoolkit=11.6.0', 'cupy=10.4.0', 'faiss-gpu=1.7.2', 'fastparquet=0.6.3', 'nccl=<IP_ADDRESS>', 'pip=22.3.1', 'pyarrow=8.0.0', 'python=3.10.9', 'python-snappy=0.6.1', 'pytorch=1.13.1', 'pytorch-cuda=11.6', 'snappy=1.1.9', 'torchaudio=0.13.1', 'torchvision=0.14.1']

Could not solve for environment specs
The following packages are incompatible
├─ fastparquet 0.6.3**  is installable with the potential options
│  ├─ fastparquet 0.6.3 would require
│  │  ├─ python >=3.6,<3.7.0a0 , which can be installed;
│  │  └─ python_abi 3.6.* *_cp36m, which can be installed;
│  ├─ fastparquet 0.6.3 would require
│  │  ├─ python >=3.7,<3.8.0a0 , which can be installed;
│  │  └─ python_abi 3.7.* *_cp37m, which can be installed;
│  ├─ fastparquet 0.6.3 would require
│  │  ├─ python >=3.8,<3.9.0a0 , which can be installed;
│  │  └─ python_abi 3.8.* *_cp38, which can be installed;
│  └─ fastparquet 0.6.3 would require
│     ├─ python >=3.9,<3.10.0a0 , which can be installed;
│     └─ python_abi 3.9.* *_cp39, which can be installed;
└─ python 3.10.9**  is uninstallable because there are no viable options
   ├─ python 3.10.9 conflicts with any installable versions previously reported;
   └─ python 3.10.9 would require
      └─ python_abi 3.10.* *_cp310, which conflicts with any installable versions previously reported.

As suggested by @darrinh, I changed the - python 3.10.9 line to - python 3.9 in the environment.yml file and I did not have the same error anymore
After much tweaking, I feel it might be a conda/mamba issue with more recent versions.
I would love to know your versions. Here are mine:
mamba --version
mamba 1.4.2
conda 23.3.1

The above comment was done in Ubuntu 20 LTS.
But I still cannot make it run on MacOS.
This is my output:
mamba env create -f environment.yml
warning  libmamba Cache file "/Users/mau/miniconda3/pkgs/cache/7fb2ce72.json" was modified by another program
warning  libmamba Cache file "/Users/mau/miniconda3/pkgs/cache/3e39a7aa.json" was modified by another program
warning  libmamba Cache file "/Users/mau/miniconda3/pkgs/cache/dd44a73b.json" was modified by another program
warning  libmamba Cache file "/Users/mau/miniconda3/pkgs/cache/4ea078d6.json" was modified by another program
pytorch/osx-64                                                No change
pytorch/noarch                                                No change
nvidia/osx-64                                                 No change
nvidia/noarch                                                 No change
anaconda/osx-64                                               No change
anaconda/noarch                                               No change
pkgs/main/noarch                                   822.9kB @   1.0MB/s  0.3s
pkgs/r/noarch                                        1.3MB @   1.4MB/s  0.6s
pkgs/r/osx-64                                      820.9kB @ 799.1kB/s  0.2s
pkgs/main/osx-64                                     5.4MB @   3.2MB/s  1.4s
conda-forge/noarch                                  12.2MB @   4.3MB/s  2.7s
conda-forge/osx-64                                  28.3MB @   4.7MB/s  7.1s

Looking for: ['cudatoolkit=11.6.0', 'cupy=10.4.0', 'faiss-gpu=1.7.2', 'fastparquet=0.6.3', 'nccl=<IP_ADDRESS>', 'pip=22.3.1', 'pyarrow=8.0.0', 'python=3.9', 'python-snappy=0.6.1', 'pytorch=1.13.1', 'pytorch-cuda=11.6', 'snappy=1.1.9', 'torchaudio=0.13.1', 'torchvision=0.14.1']

Could not solve for environment specs
The following packages are incompatible
├─ cudatoolkit 11.6.0**  does not exist (perhaps a typo or a missing channel);
├─ cupy 10.4.0**  does not exist (perhaps a typo or a missing channel);
├─ faiss-gpu 1.7.2**  does not exist (perhaps a typo or a missing channel);
├─ nccl <IP_ADDRESS>**  does not exist (perhaps a typo or a missing channel);
└─ pytorch-cuda 11.6**  is uninstallable because it requires
   └─ cuda 11.6.* , which does not exist (perhaps a missing channel).

Mamba and Conda versions are the same as the ubuntu version:
% mamba --version
mamba 1.4.2
conda 23.3.1

Am I supposed to be able to install in MacOS to begin with?

To follow up on @mauhcs comment, this also fixed it for me:

As suggested by @darrinh, I changed the - python 3.10.9 line to - python 3.9 in the environment.yml file and I did not have the same error anymore

I'm seeing pretty much the same thing as @mauhcs on my Mac
The Python version in my base env is 3.10.11
(bold == red/error text)
Could not solve for environment specs
The following packages are incompatible
├─ cudatoolkit 11.6.0  does not exist (perhaps a typo or a missing channel);**
├─ cupy 10.4.0  does not exist (perhaps a typo or a missing channel);**
├─ faiss-gpu 1.7.2  does not exist (perhaps a typo or a missing channel);**
├─ fastparquet 0.6.3**  is installable with the potential options
│  ├─ fastparquet 0.6.3 would require
│  │  ├─ python >=3.6,<3.7.0a0 , which can be installed;
│  │  └─ python_abi 3.6.* _cp36m, which can be installed;
│  ├─ fastparquet 0.6.3 would require
│  │  ├─ python >=3.7,<3.8.0a0 , which can be installed;
│  │  └─ python_abi 3.7. _cp37m, which can be installed;
│  ├─ fastparquet 0.6.3 would require
│  │  ├─ python >=3.8,<3.9.0a0 , which can be installed;
│  │  └─ python_abi 3.8. _cp38, which can be installed;
│  └─ fastparquet 0.6.3 would require
│     ├─ python >=3.9,<3.10.0a0 , which can be installed;
│     └─ python_abi 3.9. _cp39, which can be installed;
├─ nccl <IP_ADDRESS>  does not exist (perhaps a typo or a missing channel);*
├─ python 3.10.9  is uninstallable because there are no viable options**
│  ├─ python 3.10.9 conflicts with any installable versions previously reported;
│  └─ python 3.10.9 would require
│     └─ python_abi 3.10. _cp310, which conflicts with any installable versions previously reported;
└─ pytorch-cuda 11.6  is uninstallable because it requires**
└─ cuda 11.6. , which does not exist (perhaps a missing channel).*

@mauhcs @mgleavitt see this comment to setup the env for Mac


Animated GIF images

I have just tested the package and turns out it doesn't support animated gif images. Why is that? Apparently you're loading the uploaded image into the intervention (GD) and save it like that - and since intervention doesn't support animated images - it's removing the animation.
Mostly likely you could simply call copy on the uploaded image and disable crop/resize functionality to make it work.
Is this known / planned to be fixed?

Thanks for reporting this. This functionality was fixed before and went broken again since recent releases. We will fix this in next release.

@pompex
Great suggestion. Thank you.
Just pushed https://github.com/UniSharp/laravel-filemanager/releases/tag/v<IP_ADDRESS> for this fix.
Filemanager now bypasses GIF and SVG images, treat them as normal files.

BTW, cropping a GIF image will still remove the animation. This is the limitation. :)

@youchenlee Awesome! Thanks for the commit!

@pompex It depends on your settings in composer.json
Or simply run composer require unisharp/laravel-filemanager:~1.8


find with arguments returns empty array.

Is anyone else not getting results when issuing a find command with arguments?  I'm trying to connect to MySql.  The following code returns an empty array:
db.Users.find({id: 1}).execute(function(err, users) {
if(err) {
console.log(err);
//callback({error: err}, null);
}
else {
console.log(users[0].username);
//callback(null, users);
}
});
However the following returns the user:
db.run('SELECT * FROM Users WHERE id = 1',function(err, users) {
if(err) {
console.log(err);
//callback({error: err}, null);
}
else {
console.log(users[0].username);
//callback(null, users);
}
});
Also note the following returns the entire collection of users:
db.Users.find().execute(function(err, users) {
if(err) {
console.log(err);
//callback({error: err}, null);
}
else {
console.log(users[0].username);
//callback(null, users);
}
});
The execute function in mysql.js ....
client.query(sql, params, function(err, results){
The sql variable value =  SELECT * FROM Users WHERE "id" = 1
Notice that field name id is in quotations, I don't think it should.
Is there something I'm doing wrong?  or is it a bug?  I haven't been able to identity the bug yet but I will keep looking.

Shoved MySQL out; no longer supporting in v2. Although I think this problem might come from a local implementation bug or from improper error catching which was fixed in 0.0.4.


Move domain names to one registrar

move sites under one registrar and set-up email for those under new NC Open Pass Labs corporation

May-June

I moved everything to a new account. Except for NCDatapalooza which is still in the 60-day lock down window. I will move that in June


Content type for /v1/promql endpoint is text/plain instead of application/json

When curling the /v1/promql endpoint with a bad query, the error response is formatted as json, but the Content-Type of the header is text/plain; charset=utf-8:
curl -G "http://somesite.com/v1/promql" --data-urlencode 'query=avg_over_time(healthwatch_redis_valueMetricQueue_size{source_id="healthwatch-forwarder"}[5m] + healthwatch_redis_counterEventQueue_size{source_id="healthwatch-forwarder"}[5m])' -H "Authorization: bearer AEDF)" -vvv
*   Trying X.X.X.X...
* TCP_NODELAY set
* Connected to somesite.com (X.X.X.X) port 80 (#0)
> GET /v1/promql?query=avg_over_time%28healthwatch_redis_valueMetricQueue_size%7Bsource_id%3D%22healthwatch-forwarder%22%7D%5B5m%5D%20%2B%20healthwatch_redis_counterEventQueue_size%7Bsource_id%3D%22healthwatch-forwarder%22%7D%5B5m%5D%29 HTTP/1.1
> Host: somesite.com
> User-Agent: curl/7.54.0
> Accept: */*
> Authorization: bearer AEDF
>
< HTTP/1.1 400 Bad Request
< Content-Length: 104
< Content-Type: text/plain; charset=utf-8
< Date: Thu, 28 Jun 2018 20:48:49 GMT
< X-Vcap-Request-Id: f2d0b76f-0519-4371-5401-0f4889787aea
< Via: 1.1 google
<
* Connection #0 to host somesite.com left intact
{"error":"parse error at char 176: binary expression must contain only scalar and instant vector types"}

This causes problems with some deserialization libraries.

This is fixed in master.


Cannot build with vitejs

[x] bug
Swiper Version:  ^6.1.1
Platform/Target and Browser Versions: Linux ubuntu

What you did
Create a fresh vitejs app
$ yarn create vite-app <project-name>
$ cd <project-name>
$ yarn
$ yarn dev

add swiper yarn add swiper
Go to App.vue and simply load and call swiper
import { Swiper } from 'swiper'
console.log(Swiper)

Try to build yarn build
Expected Behavior
Build without error
Actual Behavior
Build throw an error

No problem with yarn dev

It works with webpack and rollup.  I guess issue is on vite side, open issue there


[WIP] add F# WriteCodeFragment

ref https://github.com/dotnet/netcorecli-fsc/issues/93
to generate the assemblyinfo.fs from fsproj properties.
@KevinRansom the plan is to do it like c# does for coreclr (where codedom doesnt exists anyway), like here in src/Tasks/WriteCodeFragment.cs#L294-L313
/cc @rainersigwald

Thanks for opening a PR. Unfortunately we've already closed a similar PR (#2058) after expressing concerns that we would not like to have this logic in MSBuild. If you think this is not correct please open an issue to discuss.

@AndyGerlicher while long term this is not the best place, atm the dotnet/sdk use the WriteCodeFragment in the language agnostic Microsoft.NET.GenerateAssemblyInfo.targets#L93-L96.
So maybe is possibile to make a special case for F# in dotnet/sdk, but msbuild contains both c# and VB atm, so may make sense to leave it there and add F#, to make it work for sdk 2.0?
@AndyGerlicher i need to open an issue to discuss, or can be discussed there? /cc @KevinRansom @cartermp

Adding @dsplaisted @eerhardt for an hint about this, because dotnet/sdk is using the WriteCodeFragment in the language agnostic Microsoft.NET.GenerateAssemblyInfo.targets#L93-L96.
F# now is not supported in WriteCodeFragment, so the file is not generated.
Dunno if there is a better place to discuss, but pratically all the code needed is already there (i just need to add more unit tests, atm is just one), so maybe easier to see on what adding this mean for msbuild  @AndyGerlicher

@enricosada
We can override : tps://github.com/dotnet/sdk/blob/8204b6b1f3ff2f9717c5d66ab903795271de2e9c/src/Tasks/Microsoft.NET.Build.Tasks/build/Microsoft.NET.GenerateAssemblyInfo.targets#L51
in our targets file and sdk apps will work fine.
But we should also send a PR to the dotnet sdk refactoring the current implementation a bit.
@nguerrera said he would welcome a PR that improved this :-)
The bit where the attributes are generated should be moved to a new target:  GetAssemblyAttributes or some such name.
And then : CoreGenerateAssemblyInfo just handles the write.
We can override CoreGenerateAssemblyInfo  to write the attributes with a build task added to the Microsoft.FSharp.Build library ... or something.
Does that make sense?
Enrico,
thanks for pushing on this, it's really great that you take the time to dive into all of the stuff.
Kevin

But we should also send a PR to the dotnet sdk refactoring the current implementation a bit.

There's already https://github.com/dotnet/sdk/pull/1007 which splits the target into _CalculateAssemblyAttributes and CoreGenerateAssemblyInfo but it probably won't land in its current form (see PR discussion. I'll be sending out a PR today for an alternative implementation)

Awesome @dasMulli , can you please add me and @KevinRansom and reference the f# issue  https://github.com/Microsoft/visualfsharp/issues/3113 in that PR, so we'll update.

Thx for review @saul but this is going to Ben replaced with another, without writecodegragment


Clear concurrent promises on cache clear

Found a bug while trying to write some tests for components using SWR. cache.clear() doesn't clear the concurrent promises so further calls get stuck in the suspense fallback (not quite sure why that's the resulting behavior).  Simply iterating through the concurrent promises and deleting entries fixes the problem.
Also had to update react testing library and JSDOM, otherwise the tests pass incorrectly (pretty sure this isn't a bug in either of those libraries). The JSDOM changes the required node version to > 10 to develop the project though

Something to note is that I'm aware of discussion like https://github.com/zeit/swr/pull/326  and dedupingInterval but from my testing that doesn't solve the problem

For reference here is an example test that was failing before this change
import React from 'react';
import { cache } from 'swr';
import { render, waitFor } from '@testing-library/react';
import SomeComponent from './SomeComponent;
import mockedHttpClient from './mockedHttpClient';

describe('container error handling', () => {
  afterEach(() => {
    cache.clear();
  });

  it('should render a homepage at the root url', async () => {
    const { queryByText } = render(<SomeComponent />);
    await waitFor(() => expect(queryByText(/some title/i)).toBeVisible());
  });

  it('should render an error message when srosh is 500ing', async () => {
    mockedHttpClient.onGet('/some_path').replyOnce(500);
    const { queryByText } = render(<SomeComponent />);
    await waitFor(() => expect(queryByText(/error boundary text/i)).toBeVisible());
    expect(queryByText(/title/i)).toBeNull();
  });
});

Thank you for this amazing PR @slightlytyler! I think I'll look deeper into this because from my understanding, the concurrent promises will be removed right after throwing to , if you have dedupingInterval set to 0. So this seems like another bug.

@shuding you're write I think, after looking again I found a bug with how deduping interval was handled https://github.com/zeit/swr/pull/335/files#diff-ab20307c185620c9b54994fa4dcee1b7R270
my change there fixes a part of the failing test I added but it doesn't completely pass yet

Been messing with it for a while and still can't quite narrow the source of the race conditions. Different values in the timeouts produce different failures so pretty sure it's a race condition with concurrent promises beyond the initial one I mentioned

Looking again and seems like the problem is that on initial mount revalidate is called twice. Once as a hard revalidation then again as a soft revalidation. The soft revalidation fails the shouldDeduping check since concurrent promises have already been removed from the deduping timeout. Instead the soft revalidation get's processed as a hard revalidation, and resets concurrent promises
I don't think this produces a bug in the real behavior but it totally messes with tests

Finally got something to  pass  the tests. Basic idea is that  you tracker a counter cache.version, clear increments it, and then in the hook we check for a mismatch in  revalidate and  throw away updates that fail the check. cache.clear also synchronously removes concurrent promises
Not sure if these are the right patterns but I think the test case is valid
Anyways, love SWR, hope I can help you get this solved 👍

My team are also having the same issue. Any progress on this pr @slightlytyler @shuding ?

@alexl0gan not working on a project that uses SWR anymore but I think react-query's ReactQueryCacheProvider is a better way to solve this problem then trying to manipulate the singleton cache synchronously in tests. Closing this as I'm sure it's useless to the project at this point

@slightlytyler I don't think this is useless to the project... I'm still facing the same issue

I've resorted to mocking SWR entirely to resolve this, for anyone else looking


[DO NOT MERGE] test auth diagram

Docs Build status updates of commit 26fffd4:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/authentication/tab_auth_sequence_diagram.png
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

@mobajemu-msft this can be closed now, thanks for your help with it!

@mobajemu-msft let's go ahead and close this stale PR since its no longer needed


DL-16: Add script to merge GitHub PR.

Fetch a list of open Pull Request from GitHub, and merge them into the
repository. If the JIRA credentials are exported, the issues related to
the PR are updated with a comment and closed.
This script is a modified version of the one created for the spark
project.
./dl-merge-pr.py
Which pull request would you like to merge? (e.g. 34): 2
Commit title [DL-4: Add NOTICE file.]:

=== Pull Request #2 ===
PR title	DL-4: Add NOTICE file.
Commit title	DL-4: Add NOTICE file.
Source		franckcuny/fcuny/DL-4
Target		master
URL		https://api.github.com/repos/apache/incubator-distributedlog/pulls/2

Proceed with merging pull request #2? (y/n): y
From https://github.com/apache/incubator-distributedlog
 * [new ref]         refs/pull/2/head -> PR_TOOL_MERGE_PR_2
From git://git.apache.org/incubator-distributedlog
 * [new branch]      master     -> PR_TOOL_MERGE_PR_2_MASTER
Switched to branch 'PR_TOOL_MERGE_PR_2_MASTER'
Do you want to validate unit tests after the merge? (y/n): n
Enter primary author in the format of 'name <email>' [Franck Cuny<EMAIL_ADDRESS>Enter reviewers [Sijie Guo<EMAIL_ADDRESS>
Merge complete (local ref PR_TOOL_MERGE_PR_2_MASTER). Push to apache? (y/n): n
Okay, exiting
Restoring head pointer to fcuny/DL-16
Switched to branch 'fcuny/DL-16'

Creating a JIRA ticket https://issues.apache.org/jira/browse/DL-26 for tracking Travis CI build failure.

LGTM +1. Let's merge this pull request using it :D
Also, I created a wiki page for 'committer workflow' - do you mind filling up the information on how to use this script for committers?
https://cwiki.apache.org/confluence/display/DL/Committer+Workflow

I'll update the wiki.

@franckcuny I merged this pull request. but because the commit message doesn't contain 'close #6' message. so asfgit doesn't close this pull request. Can you manually close this pull request?
The fix for the merge script is on https://github.com/apache/incubator-distributedlog/pull/6. If it is okay to you, can you try to merge that? it would help testing if you have permissions to push the change to apache.

This change has been merged.


how to run multiple run_classifier.py programs at the same time

When I try to run more than one run_classifier.py program, I get error as follows:
E0721 15:11:25.969784<PHONE_NUMBER>45280 error_handling.py:70] Error recorded from training_loop: truncated record at 12582736
[[node IteratorGetNext (defined at run_classifier.py:922) ]]
Original stack trace for 'IteratorGetNext':
File "run_classifier.py", line 1023, in

any news about this?


asciidoctor: add rouge to dependencies

Motivation for this change
Add syntax highlighting support via rouge.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Assured whether relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

I like that README is added (I've had this chicken-and-egg problem with gemset.nix). However I think it is enough to do:
$ nix-shell -p bundix --run 'bundix'

to rebuild gemset.nix.
Also, why should we add rouge?  There already is 'coderay', 'pygments.rb'. Which benefits has rouge compared to those?

I've tried pygments a while back with asciidoctor and it just didn't work.. Found this to be an easy workaround for what I needed instead of debugging pygments (or maybe failure to use it?)
On a more global scale, adding it here costs little and gives users more choice what to use

Regarding bundix, I've added nix-shell to be able to regenerate it without having it installed.. As I stumbled on it a few times - otherwise it fails on missing dependencies

As I stumbled on it a few times - otherwise it fails on missing dependencies.

I've tried rm gemset.nix && nix-shell --pure -p bundix --run 'bundix' and it was enough to regenerate gemset.nix. The rebuild-gemset.nix is redundant here, just mention the command I've proposed in README.adoc.

On a more global scale, adding it here costs little and gives users more choice what to use

Ok. I don't know Ruby packaging details, I'm curious how it behaves when I use asciidoctor and rouge in local Gemfile/gemset.nix. I hope there will be no conflicts.

Thanks, I'll try reproducing the dependencies error when regenerating. Will report back here when done. Will update readme too.

@svalaskevicius have you reproduced the issue?

Sorry didn't have a chance yet. Will try to do it this evening :)

ok, reproduced, (@danbst)
your command works ok only if Gemfile.lock is present, however, it doesn't add new libs to it, only converts the lock file to gemset.nix.
to add rouge to the lock file, one apparently needs to run bundix -m, which runs ruby things.. that fail to install mathematical because there are no binary dependencies installed:
<compiling things and dep errors>
An error occurred while installing mathematical (1.6.12), and Bundler cannot continue.
Make sure that `gem install mathematical -v '1.6.12' --source 'https://rubygems.org/'` succeeds before bundling.

Thus, I still don't see any other alternative rather than in this PR.
I'll update the readme to adoc though :)

done. also when testing now I noticed that rouge and some other dep has upped their version

@svalaskevicius thanks! Makes sense. I found a way to remove duplication. Here's diff:
diff --git a/pkgs/tools/typesetting/asciidoctor/default.nix b/pkgs/tools/typesetting/asciidoctor/default.nix
index 9508f3ff023..e46ebcf18ae 100644
--- a/pkgs/tools/typesetting/asciidoctor/default.nix
+++ b/pkgs/tools/typesetting/asciidoctor/default.nix
@@ -1,10 +1,10 @@
-{ stdenv, lib, bundlerApp, ruby
+{ stdenv, lib, bundlerApp, ruby, bundix, mkShell
   # Dependencies of the 'mathematical' package
 , cmake, bison, flex, glib, pkgconfig, cairo
 , pango, gdk_pixbuf, libxml2, python3, patchelf
 }:

-bundlerApp {
+bundlerApp rec {
   inherit ruby;
   pname = "asciidoctor";
   gemdir = ./.;
@@ -43,6 +43,12 @@ bundlerApp {
     };
   };

+  passthru.updateShell = mkShell {
+    buildInputs = (gemConfig.mathematical {}).buildInputs ++ [
+      bundix
+    ];
+  };
+
   meta = with lib; {
     description = "A faster Asciidoc processor written in Ruby";
     homepage = http://asciidoctor.org/;
diff --git a/pkgs/tools/typesetting/asciidoctor/update.sh b/pkgs/tools/typesetting/asciidoctor/update.sh
new file mode 100755
index<PHONE_NUMBER>0..10a053a847b
--- /dev/null
+++ b/pkgs/tools/typesetting/asciidoctor/update.sh
@@ -0,0 +1,6 @@
+#!/usr/bin/env bash
+rm gemset.nix Gemfile.lock
+nix-shell ../../../.. -A asciidoctor.updateShell --run '
+  bundix -m --bundle-pack-path $TMPDIR/asciidoctor-ruby-bundle
+'
+rm -r .bundle
\ No newline at end of file

That can also remove the need for README, as update.sh is kinda standard way for package update scripts.
If you like it, you may embed it into this PR. Otherwise I can push it separately.

Thanks! I'll test and add it a bit later :)

works well! I've set you as the author in the commit @danbst if it's ok with you :)

@svalaskevicius thanks for doublechecking!


Add support for asp.net mvc web projects

I see we have a CreateNuGetPackagesTask and CreateChocolateyPackagesTask but i'm thinking there should be a "CreateWebPackageTask".
It should

Detect it is a web project
Build the web project
Perform any web.config transforms
Zip up the project and upload to artifacts if applicable.

Is this something the project would be interested in? If so i can draft up a solution. Thanks!

@tjackadams I certainly would have no objections, assuming that it doesn't impact on any of the existing functionality.  To date, the functionality that exists in Cake.Recipe has been directly associated with the types of builds that I use.

Just throwing my thoughts out there:
Considering what would need to be supported to have support for asp.net mvc, this could be something that would be better suited for a separate Recipe.
While it probably would be possible to support MVC projects in Cake.Recipe, it may cause it to be very bloated depending on which features will be added for it (what you listed is just the absolute basic ones).
IMHO, it would be better to have a different addin specifically targeting web projects (not just MVC, but Web Forms, asp.net core, MVC and Web Pages).

@tjackadams Sorry about the delay in replying to this.  I tend to agree with @AdmiringWorm here, and I have done the same thing for when doing VSCode Extension packages.  I would suggest that if this is still something you are interested in, that you look to create a standalone recipe for this.  Some examples can be found here:
https://github.com/cake-contrib/?utf8=✓&q=recipe&type=&language=


De 312 quickbooks tot total transformation

Getting an error running dbt run --target cta --select tag:cta;
Compilation Error in model vendors_MetaData (tot_quickbooks/models/2_partner_matviews/vendors_MetaData.sql)
  Model 'model.default.vendors_MetaData' (tot_quickbooks/models/2_partner_matviews/vendors_MetaData.sql) depends on a source named 'cta.vendors_MetaData_base' which was not found

Changed the sync/folder name. Both cta and partner dbt targets are running successfully.

This is my first phase 2 ticket so please get nit-picky

@royconst oh man, what a heftychomnk of a ticket!! I don't see any flags in the code, but here are a couple more steps you can take to kick the tires on this whole deal:

try running the dbt run --target cta --select tag:cta command locally using the data in prod, to make sure it cooperates with the full data (since it looks like in dev we are only using the CTA test account and syncing a single row)
add the dev_deploy label to both this PR and your PR in airflow-dags to get this running in dev Composer!

@royconst oh man, what a heftychomnk of a ticket!! I don't see any flags in the code, but here are a couple more steps you can take to kick the tires on this whole deal:

try running the dbt run --target cta --select tag:cta command locally using the data in prod, to make sure it cooperates with the full data (since it looks like in dev we are only using the CTA test account and syncing a single row)
add the dev_deploy label to both this PR and your PR in airflow-dags to get this running in dev Composer!

Re: # 1 It did run --target cta and partner successfully on prod. The latter to partner-a and I could see the views.
Re: # 2 Yea, I was wondering if we wanted to keep that dev setup but it would probably be good. I wonder how it will run with no data actually syncing. Hopefully/probably fine. Will test now.

I setup dev. Running it locally and --target cta ran just fine. I can see the new tables. Running --target partner had an issue though. It hung on a materialized view. When cancelling I got The bigquery adapter does not support query cancellation. Some queries may still be running!.  Running the partner views again with --full-refresh and it's progressing.

--target partner ran fine the second time on dev :thumbsup:

@royconst oh wow this connector has a ton of models! The dbt looks good to me, the one comment i would have is that Airbyte default normalization is pretty trash sometimes because it breaks out any nested field into its own table. which doesnt always make sense (like instances where its a single column? what are you doing Airbyte 🤷 ). So sometimes i end up just deleting a lot of those tables created from nested fields and just extract the JSON directly into the main stream table. It definitely helps cut down on a lot of tables that probably wont be used. Probably not something for this connector right now considering just how many models there are but figured id note it! oh and @emily-flambe did start making a version of default dbt normalization that we can use internally! so hopefully we wont even have to worry about it in the near future haha

@emily-flambe totally understand the intent behind using real data but, minor gripe, that would require another live meeting with the partner to get credentials, I've bothered them enough with that lol. Mainly though, it's very sensitive content that I wouldn't feel comfortable putting it in an environment where we do testing. This dev setup really won't tell us a whole lot, but at least it will notify if the api is down, changes in schema, or if we need to test upgrading the connector.

@emily-flambe totally understand the intent behind using real data but, minor gripe, that would require another live meeting with the partner to get credentials, I've bothered them enough with that lol. Mainly though, it's very sensitive content that I wouldn't feel comfortable putting it in an environment where we do testing. This dev setup really won't tell us a whole lot, but at least it will notify if the api is down, changes in schema, or if we need to test upgrading the connector.

Ah!!  I had forgot that the additional connection would require another meeting with the partner. So nuts to that, let's keep running the CTA test connection in dev. Thanks for explaining!!


Is the code for the arduino written using golang and tinygo?

Hey @fiwippi
This looks really accessible for a golang coder like me. and a good way to teach my kid some electronics and coding.
Is some of the golang code running on the arduino UNO ? https://tinygo.org/docs/reference/microcontrollers/arduino/
Just trying to get my head around the topology.

also in the makefile.
i think with gio and windows you dont need to compile the way your doing it.
https://github.com/gioui/gio/tree/main/cmd/gogio does all that and more.
For example:

go install gioui.org/cmd/gogio@latest

gio -o ./bin/binary.exe -target windows .

Hey,

The only code written on the Arduino is written using C with the FastLED library, all the golang code is client side for the GUI and interpreting the computer's audio stream
I'll take a look at it, seems interesting

Further explanation of the go code in the pkg directory:

The audio folder contains all code used to parse audio streams and generate a colour based off of them
The gui folder contains all the gio code for running the gui
The session folder contains the code the computer uses to interface with the arduino over serial bus

If you have any more questions feel free to ask

Thanks


task: storybook build and deploy for appsmith wds

Description
Removed WDS storybook from the client build.sh and added it to a seperate script.

/build-wds-preview

/build-wds-preview


Add a function to re-infer the shapes

Example:
Say we have a network (σ(w2(σ(wx+b)) +b2),  The network is set up for training with a particular shape of x. And if we want to use the same exact network for inference, for which x may have different shapes (smaller batches for example).
The current workarounds are one of these:

Recreate a network, reusing the values of w, b, w2, and b2 in the new network
0-pad the  input x during inference mode.

Neither of these methods are particularly userfriendly. Having done a session with a friend, it occurs to me that we can just write a function like this:
func ReinferShape(g *ExprGraph, newShapes map[*Node]Value) {
    // this check must be true
    for k, v := range newShapes {
        if !k.IsInput(){
            // error
        }
        // further analysis needs to be done on any other shapes dependent upon input
        WithShape(v.Shape().Clone()...)(k) // set shap
    }
    // propagate new shape thru the graph
}

If we trained a model with the following
x = (4, 2),
y = (4, 1)

w = (2, 5)
b = (4, 5)

w2 = (5)
b2 = (4)

And if we infer shape of x to (1, 2) wouldn't (wx + b) be shape mismatch (1, 5) and (4, 5)

Do you know if this ever got fixed? I am struggling to find this function.


1061 refactor core file validators based on aind data schema models expected modalities

This PR takes advantage of the new ExpectedFiles model in aind-data-schema-models to refactor the core metdata validator to check for required/excluded files for all modalities. Currently the validators only check for ecephys/smartspim platform to confirm they have a few required files. The code now checks by modality (not platform) and confirms that all expected/required files are included.
In the event that two modalities are in conflict the code prioritizes REQUIRED > OPTIONAL > EXCLUDED

There's some QC file changes that snuck into this branch... I'll remove those

There's a bug in this PR -- it can't handle modalities with a '-' in the name (need to .replace('-','_'))

There's a bug in this PR -- it can't handle modalities with a '-' in the name (need to .replace('-','_'))

I wonder if it'd be helpful to add the modality folder name explicitly in https://github.com/AllenNeuralDynamics/aind-data-schema-models/blob/main/src/aind_data_schema_models/models/modalities.csv

There's a bug in this PR -- it can't handle modalities with a '-' in the name (need to .replace('-','_'))

~I wonder if it'd be helpful to add the modality folder name explicitly in https://github.com/AllenNeuralDynamics/aind-data-schema-models/blob/main/src/aind_data_schema_models/models/modalities.csv~
I guess I'm just using the abbreviation

Yeah I think we only ever use the abbreviation everywhere


Fixes #3338: Implement "atomic" upgrade/install

What this PR does / why we need it:
Add possibility to put "--safe" argument to install and upgrade command that restores the state of cluster in case of failed install/upgrade attempt.
This resolves the problem of non-atomic upgrade process in helm and removes need to write scripts to handle failed deployments. Also, closes #3338.
Special notes for your reviewer:
This is a proposal for such functionality, so I haven't any documentation and unit tests yet. However I've tested this functionality by hands on living cluster.
Also, I am not a professional Go developer, so if there are ways to improve implementation with fluent Go cunstructions, I would be glad for suggestions.
If applicable:

[x] this PR contains documentation
[x] this PR contains unit tests
[ ] this PR has been tested for backwards compatibility

/cc @nce
@thomastaylor312 @technosophos does this fix https://github.com/helm/helm/issues/1193

@jkroepke I think it helps work around it based on what I am reading, but I don't think it fully solves the issue

/cc @nce
@thomastaylor312 @technosophos One more. Is this a workaround for https://github.com/helm/helm/pull/4871, too? It would be pretty awesome since it breaks the CI, too.

@jkroepke No it does not solve the case, which is described in the PR https://github.com/helm/helm/pull/4871.
4871 is about a bug inside of the install/upgrade operation internals. This operation can break own invariant, which is a bad thing.
This pr 5143 is about automatically running rollback operation (which is the same install/upgrade operation, but reversed), but it does not change the internals of this operation.
Read details and code in the #4871.

After taking a good look at the code, I can see why it doesn't address @distorhead's issues as well: it's not a truly atomic rollback. Resources that are created as part of the failed release are not cleaned up, which #4871 attempts to fix up.
@distorhead if you want to roll your changes into the --atomic flag, that would be a good change to have in this feature. If you don't want to take on that work, I'd be happy to move it forward. Just let me know. :)

After taking a good look at the code, I can see why it doesn't address @distorhead's issues as well: it's not a truly atomic rollback; it just calls helm rollback and hopes for the best. Resources that are created as part of the failed release are not cleaned up, which #4871 attempts to fix up.
@distorhead if you want to roll your changes into the --atomic flag, that would be a good change to have in this feature. If you don't want to take on that work, I'd be happy to move it forward. Just let me know. :)

@bacongobbler Sorry, missed your comment. Created PR https://github.com/helm/helm/pull/5579 to add cleanup-on-fail option support when running rollback operation due to upgrade failure when using atomic.


What's the best way to configure tests involving heroku connect models for tests on CI /CD flows?

The approach in the docs  for testing salesforce models works great for me locally, however the schema / tables for heroku connect models are not being created when circleci runs tests. If this isn't too out of scope, what's the best way to ensure that a test database that isn't local correctly creates heroku connect tables? I know the docs state that The custom database engine will create the Heroku Connect schema for you. The schema is created right via the [pre_migrate](https://docs.djangoproject.com/en/stable/ref/signals/#django.db.models.signals.pre_migrate) signal, only when a test database is created. but this doesn't seem to apply in this case.
Here's my pytest.yml file:
name: Unit Tests
on: [push]
jobs:
  pytest:
    runs-on: ubuntu-latest
    env:
      SECRET_KEY: ${{ secrets.SECRET_KEY }}
    services:
      postgres:
        image: postgres:latest
        env:
          POSTGRES_USER: testuser
          POSTGRES_PASSWORD: testpass
          POSTGRES_DB: gtm_test_db
        ports:
          - 5432:5432
        # needed because the postgres container does not provide a healthcheck
        options: --health-cmd pg_isready --health-interval 10s --health-timeout 5s --health-retries 5
    steps:
      - uses: actions/checkout@v3
      - run: pipx install pipenv
      - uses: actions/setup-python@v2
        with:
          python-version: '3.10'
          cache: 'pipenv'
      - run: pipenv install --dev --deploy
      - name: 'Create env file'
        run: |
          touch .env
          cat .env.example > .env
          cat .env
      - run: pipenv run
      - run: pipenv run pytest --mccabe --cov=gtm -vv server/gtm
      - run: pipenv run coverage report --fail-under=20

pytest.ini
[pytest]
DJANGO_SETTINGS_MODULE = gtm.test_settings
python_files = tests.py test_*.py *_tests.py
addopts = -p no:warnings --strict-markers --no-migrations
mccabe-complexity=10

I've also tried removing the --no-migrations option.
I've tried adding  - run: pipenv run python server/manage.py create_development_schema  as a step before pytest runs to the yml file, but as expected there aren't correct permissions to load a schema that way.

Nevermind, I'm dumb. I had to change the database engine in my test settings to  heroku_connect.db.backends.postgresql 🤦♀


How to deal with virtual fields for Fiori draft v4

Hi Community/CAP team,
It seems, I've found an issue with virtual fields in draft mode. I've reported this in https://answers.sap.com/questions/13019552/how-to-deal-with-virtual-fields-for-fiori-draft-v4.html, but got no response so far.
Maybe someone can have  a  look?
Thanks
Klaus

Closing this because it will be followed up by https://answers.sap.com/questions/13019552/how-to-deal-with-virtual-fields-for-fiori-draft-v4.html

Let's keep it open and link this issue from the SAP Community Q&A.

hi @gregorwolf
i just stumbled across this. should be resolved in cds^4, as virtual elements are filtered on db level.
best,
sebastian

This issue seems to have returned since @sap/cds > 5.4.0. I have tested 5.4.0 and 5.4.3 and both cause a problem when trying to save/activate a draft entity with virtual/readonly fields using SQLite local testing. @sap/cds 5.3.0 is working fine.

With cds^5.4, computed values are preserved during draft activate. See https://cap.cloud.sap/docs/releases/aug21#changes-in-node-js.


Merge Samsung v2.1 submission into submission-v2.1

bring back new keyword settings from master to v2.1 by cherrypicking some patches from the master branch?
@AhmedTElthakeb to change Exynos backend backed to v2.1 submission settings


Can not display local image on iOS

I have the same issue.
When I use the following it works fine:
private win: any = window;
this.win.Ionic.WebView.convertFileSrc();

Does not work from my side with webview v4.1.0...
Still have issue while trying to display a local stored image...
Here is my code
private win: any = window;
this.img = this.win.Ionic.WebView.convertFileSrc(LocalString);

and on my html file
<img [src] = "img" />
Original local url is
file:///var/mobile/Containers/Data/Application/BDC18876-12A6-4DB7-A347-9DEF68C502A2/Library/NoCloud/130/130.jpg
Converted url became
ionic://localhost/_app_file_/var/mobile/Containers/Data/Application/BDC18876-12A6-4DB7-A347-9DEF68C502A2/Library/NoCloud/130/130.jpg
But image is still empty on my device. It does not render...
Anything to see with Content-Security-Policy maybe ?
Mine is
<meta http-equiv="Content-Security-Policy" content="default-src * data: blob:; style-src 'self' 'unsafe-inline'; script-src 'self' 'unsafe-inline' 'unsafe-eval' blob: localhost:*>
Any help ?
Originally posted by @APalau82 in https://github.com/ionic-team/cordova-plugin-ionic-webview/issues/193#issuecomment-505864141

If using angular you have to tell it to trust ionic scheme with dom sanitizer, there is an example in the comments On the other issue you commented

Isn't it possible through base64?

I have same issue , even I used  dom sanitizer,
original file
"file:///var/mobile/Containers/Data/Application/7DAAC398-A7CD-40B6-A5EA-824BBE134D8C/Library/NoCloud/1598542461557_cdv_photo_001.jpg"
Converted url
"ionic://localhost/app_file/var/mobile/Containers/Data/Application/7DAAC398-A7CD-40B6-A5EA-824BBE134D8C/Library/NoCloud/1598542461557_cdv_photo_001.jpg"
Used dom sanitizer
this.sanitizer.bypassSecurityTrustResourceUrl(this.win.Ionic.WebView.convertFileSrc(path));
(https://user-images.githubusercontent.com/69796718/91467222-efe57500-e8ad-11ea-9ac2-300c5e59b3e7.jpeg)


Uploading flipper does not work

RPC-CORE: submitAndWatchExtrinsic(extrinsic: Extrinsic): ExtrinsicStatus:: 1002: Verification Error: Execution: Could not convert parameter `tx` between node and runtime: No such variant in enum MultiSignature: RuntimeApi, Execution: Could not convert parameter `tx` between node and runtime: No such variant in enum MultiSignature

Resolved, it was due to an incompatible version of canvas-node.