Support linking to compound foreign keys

Reported as a bug in #1098 because they caused 500 errors - but it would be even better if Datasette could hyperlink to related rows via compound foreign keys.

My fix in deb0be4ae56f191f121239b29e83dd53b62d6305 for #1098 was to have Datasette deliberately pretend that compound foreign keys don't exist: https://github.com/simonw/datasette/blob/deb0be4ae56f191f121239b29e83dd53b62d6305/datasette/utils/init.py#L470-L495
This workaround will need to be rethought to implement real support for them.

https://latest.datasette.io/_internal/foreign_keys (use https://latest.datasette.io/login-as-root first) is now a compound foreign key table:
CREATE TABLE foreign_keys (
        "database_name" TEXT,
        "table_name" TEXT,
        "id" INTEGER,
        "seq" INTEGER,
        "table" TEXT,
        "from" TEXT,
        "to" TEXT,
        "on_update" TEXT,
        "on_delete" TEXT,
        "match" TEXT,
        PRIMARY KEY (database_name, table_name, id, seq),
        FOREIGN KEY (database_name) REFERENCES databases(database_name),
        FOREIGN KEY (database_name, table_name) REFERENCES tables(database_name, table_name)
    );

Currently the database_name column becomes a link (because it's a single foreign key) but the table_name one remains a non-link:

My original idea for compound foreign keys was to turn both of those columns into links, but that doesn't fit here because database_name is already part of a different foreign key.

Also need to solve displaying these links in the opposite direction:
https://latest.datasette.io/_internal/tables/fixtures,facet_cities

That page should link to lists of records in columns, foreign_keys and indexes.

I went ahead and spiked something together, in #2003

My original idea for compound foreign keys was to turn both of those columns into links, but that doesn't fit here because database_name is already part of a different foreign key.

it's pretty hard to know what the right thing to do is if a field is part of multiple foreign keys.
but, if that's not the case, what about making each of the columns a link. seems like an improvement over the status quo.


Textual definition update: trehalose BP terms

Trehalose is important in insect metabolism, but the related BP defs suggest it's only relevant to 'lichens and fungi'.
I suggest the "a disaccharide isomeric with sucrose and obtained from certain lichens and fungi." bit is replaced with "a disaccharide consisting of two molecules of glucose and that is isomeric with sucrose." in each case.
id: GO:0005991
name: trehalose metabolic process
namespace: biological_process
def: "The chemical reactions and pathways involving trehalose, a disaccharide isomeric with sucrose and obtained from certain lichens and fungi." [GOC:jl, ISBN:0028623819]
id: GO:0005992
name: trehalose biosynthetic process
namespace: biological_process
def: "The chemical reactions and pathways resulting in the formation of trehalose, a disaccharide isomeric with sucrose and obtained from certain lichens and fungi." [GOC:jl, ISBN:0028623819]
id: GO:0005993
name: trehalose catabolic process
namespace: biological_process
def: "The chemical reactions and pathways resulting in the breakdown of trehalose, a disaccharide isomeric with sucrose and obtained from certain lichens and fungi." [GOC:jl, ISBN:0028623819]
id: GO:0015771
name: trehalose transport
namespace: biological_process
def: "The directed movement of trehalose into, out of or within a cell, or between cells, by means of some agent such as a transporter or pore. Trehalose is a disaccharide isomeric with sucrose and obtained from certain lichens and fungi." [GOC:ai, PMID:17606922, PMID:20035867]
id: GO:0090062
name: regulation of trehalose metabolic process
def: "Any process that modulates the frequency, rate or extent of trehalose metabolism, the chemical reactions and pathways involving trehalose, a disaccharide isomeric with sucrose and obtained from certain lichens and fungi." [GOC:dph, GOC:tb]

Yeah it's always the risk of giving additional information; do you want to update the defs, or remove mention of the organisms?
Thanks,
Pascale

I was proposing to update the defs by removing the organisms! (As well as providing the other bit of useful info that trehalose is a disaccharide of 2x glucose.)
If OK with you, I'll go ahead with those updates.

Yes OK - perfect!!


Basic comparison for List

Which issue does this PR close?

Part of #5407
TODO in follow on PR:

Distinct / Not Distinct
Test for Nested
Struct

Rationale for this change

What changes are included in this PR?

Are there any user-facing changes?

If I'm not mistaken this changes the null behaviour from what is documented for these kernels. I'm not sure we want to support nested types in these kernels for this reason


[RAINCATCH-1182] Fix loglevel compile issue

Motivation
Fix compilation issues from hybrid hoisting and non-hoisting bootstrapping via using the core and angularjs repos together.
Description
Use the loglevel library untyped, copy over relevant enum.
This should fix the compilation issues without changing the logger's public library.

To verify:

Run lerna bootstrap from core/ linked inside the angularjs repo
Run lerna bootstrap from the angularjs repo above in the filesystem structure
Run lerna run build from the angularjs repo, it should also compile the logger module correctly

Changes Unknown when pulling c06efe7c40726c9bf30f0d70e23816fc71f7dfaa on RAINCATCH-1182 into ** on master**.

Verified


As an admin I want to be able select locations that i want to delete or update

we can't delete it for now (per osm)


(SUP-4990) S0039 Accommodate parsing of unicode dates in September

Add string substitution to S0039 to accommodate unicode CLDR change from Sep to Sept for %b in September
Please check off the steps below as you complete each step

[x] Put the Jira ticket or Github issue number in parentheses in the Title e.g. (SUP-XXXX) Add Super Duper State Check
[ ] Update the Jira ticket status to Ready for Review if there is one
[x] Review any CI failures and fix issues

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

@EdwardBenton update the branch and I'll get that approved, so far it looks good to me.


how to dynamically increases output ?

My scenerio is that i have a  one node in editor when i click on that node one popup is opened. in that pop up we are given number like 2 or 3. if i am added 3 then.it will be immediately add 3 output on that node. how we can do like this.
Thank you in advance.

Please read documentation in readme: (Opened 9 issues.)
https://github.com/jerosoler/Drawflow#methods
Method - addNodeOutput - To increase outputs.

Can't I dynamically generate output?

Example:
editor.addNodeOutput(5);

Before asking please try searching the issues.

https://github.com/jerosoler/Drawflow/issues/35

i used this method.but after that we need to initialize editor again or directly it added 5 outputs.
editor.addNodeOutput(5);
i am used this but it does not worked for me.

Number 5 it's id of node to add ouput.

can you provide one sample example ?


Respawn problem

After using the bed on the airship, can't respawn properly if player die after player destroy all the blocks that make up the airship.

Old issue, closed. I'll be deleting the custom respawn code soon.


Contrived example used

A contrived example is used at developers/fundamentals/avm-concepts/initializable-fields/
I recommend that all examples be functional and informative. Contrived examples give the appearance that the documenter does not fully understand the value of the thing being demonstrated.
If you cannot find a real example to demonstrate the documented feature then REMOVE THE FEATURE!
Be creative! When I was writing the NatSpec documentation for Solidity, this was an excuse to go learn a little bit about botany. Software documentation exists to help our dear customers go build things that matter to them, not demonstrate our mastery of computer science concepts :-p

This issue has been added into the current sprint and will be address in the next two weeks.

A change has been submitted to address this issue: 97f53fda9ebcf3912f14a579bb9a6d0323ea8000

The example was updated to show somebody passing an API key through a web service.
🙅♂
Here is a specimen of a well-documented example code:
https://solidity.readthedocs.io/en/v0.5.11/natspec-format.html?highlight=Natspec

Looks like we don't quite understand your issue then. Please suggest an example, or even make a PR if you have the time.


Hotfix/private and export native module

Owner

[x] Nickname(Tuya):
[x] Intra-group review（组内审阅人员）：田坤(萧瑟)

Description
del session disconnect status
Package
Please select the relevant package.

[ ] tuya-panel-animation-sdk
[ ] tuya-panel-api
[ ] tuya-panel-electrician-sdk
[x] tuya-panel-ipc-sdk
[ ] tuya-panel-lamp-sdk
[ ] tuya-panel-lock-sdk
[ ] tuya-panel-robot-sdk
[ ] tuya-panel-outdoor-sdk

Type of change
Please select the relevant option.

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Self CheckList
Please check all options.

[x] Intra-group review
[x] ESLint lint
[x] Example Run
[x] Jest Run
[x] No Grammer Error
[x] No Spell Error
[x] No Merge Conflict

LGTM

Codecov Report

Merging #142 (34d0939) into main (6b638a6) will decrease coverage by 1.13%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #142      +/-   ##
==========================================
- Coverage   64.69%   63.56%   -1.14%
==========================================
  Files         248      261      +13
  Lines        9367     9883     +516
  Branches     2156     2251      +95
==========================================
+ Hits         6060     6282     +222
- Misses       3295     3589     +294
  Partials       12       12

Impacted Files
Coverage Δ

...nel-outdoor-sdk/src/components/swipe-pop/swipe.tsx
2.85% <0.00%> (ø)

...mp-sdk/src/components/music/music-drawer/index.tsx
64.00% <0.00%> (ø)

...dk/src/components/preview/color-rect/ColorRect.tsx
92.59% <0.00%> (ø)

...panel-lamp-sdk/src/formatter/rhythmMode/default.ts
100.00% <0.00%> (ø)

...nel-outdoor-sdk/src/components/swipe-pop/arrow.tsx
19.35% <0.00%> (ø)

...a-panel-lamp-sdk/src/formatter/colourData/index.ts
94.44% <0.00%> (ø)

...omponents/list/color-selector-animation/Circle.tsx
85.71% <0.00%> (ø)

...a-panel-lamp-sdk/src/formatter/rhythmMode/index.ts
97.87% <0.00%> (ø)

...-panel-lamp-sdk/src/formatter/controlData/index.ts
95.00% <0.00%> (ø)

...nel-outdoor-sdk/src/components/swipe-pop/index.tsx
83.33% <0.00%> (ø)

... and 4 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 6b638a6...34d0939. Read the comment docs.


es6/7 import syntax stacks the imports

When using es6/7 imports, the objects to import are reformatted to something along the lines of json/js syntax.
Example:
import { foo } from 'foo-framework';

Becomes:
import {
    foo
} from 'foo-framework';

Is there a way to keep the imports either unmodified or keep them on a single line?

Duplicate of #9 , thanks for the report :)


fix(sdf): Graph cycles aren't a 500 when editing attribute bindings

We can hold off on merging this until the other intrinsics work ships
via GIPHY

Cherry-picked into #4636. Needed to fix the lint error too, but it's good to go in that PR.

Closing as Nick pulled this into his PR!


podvm-mkosi: use toolchain from nixpkgs

If we want to have reproducible OS image build, we need to use the toolchain from nixpkgs. The mkosi version in nixpkgs uses a patched version of systemd (with commits that are upstream, but will only be part of the next release). We also fixed many of the tools mkosi uses to get things reproducible.
I maintain the mkosi package in nixpkgs with a colleague. We have nightly tests running on nixpkgs master + mkosi main to ensure things stay reproducible and working.
The use of Nix in general is discussed in #1516. Nevertheless, as I already have this ready, I wanted to open this at least as a draft. I don't think using Nix must be an all-or-nothing decision. I don't think there is currently a way to get around using it for what it is used in this PR if we want reproducible images.

I tried the gh workflow using nektos/act  and it failed during the build image step.
Binaries got built successfully.
warning: Git tree '/home/ubuntu/cloud-api-adaptor' is dirty
error: getting status of '/nix/store/7pqci4rwn43ng88610r6a79xxx1j2irm-source/flake.nix': No such file or directory
[Create a Pod VM image with mkosi/Build image   ]   ❌  Failure - Main Build nix shell to cache dependencies
[Create a Pod VM image with mkosi/Build image   ] exitcode '1': failure
[Create a Pod VM image with mkosi/Build image   ] ⭐ Run Post Install Nix
[Create a Pod VM image with mkosi/Build image   ]   🐳  docker cp src=/home/ubuntu/.cache/act/cachix-install-nix-action@v22/ dst=/var/run/act/actions/cachix-install-nix-action@v22/
[Create a Pod VM image with mkosi/Build image   ]   ✅  Success - Post Install Nix
[Create a Pod VM image with mkosi/Build image   ] 🏁  Job failed
Error: Job 'Build image' failed

Another question on the gh-action, is it possible to reuse a pre-built binaries for the podvm "build image" job ? In my local env, re-running the "build image" job results in rebuilding the binaries. And it took roughly 30 min to build the binaries on a VM with 2vcpus and 16GB mem.

I tried the gh workflow using nektos/act and it failed during the build image step. Binaries got built successfully.

I haven't tried this with act, not sure what caused the error you observed. If you want to test this workflow, you can just trigger it on your fork. Container images are automatically pushed to the registry of the repo the workflow is executed. Here is a successful run on my fork: https://github.com/katexochen/cloud-api-adaptor/actions/runs/6928972339

Another question on the gh-action, is it possible to reuse a pre-built binaries for the podvm "build image" job ? In my local env, re-running the "build image" job results in rebuilding the binaries. And it took roughly 30 min to build the binaries on a VM with 2vcpus and 16GB mem.

Yes, this definitely can be optimized. Should we just add a input for the image name? Then we can skip the first job if the image is passed as input.
As we've already discussed a few times, we should get rid of the binaries container image build step, build binaries in separate and cache them in the mid-term.

Another question on the gh-action, is it possible to reuse a pre-built binaries for the podvm "build image" job ? In my local env, re-running the "build image" job results in rebuilding the binaries. And it took roughly 30 min to build the binaries on a VM with 2vcpus and 16GB mem.

Yes, this definitely can be optimized. Should we just add a input for the image name? Then we can skip the first job if the image is passed as input.

Yeah, this might be helpful.

As we've already discussed a few times, we should get rid of the binaries container image build step, build binaries in separate and cache them in the mid-term.

Would it make sense to split the workflow into two - one for building the binaries and another for the podvm image ?

Would it make sense to split the workflow into two - one for building the binaries and another for the podvm image ?

Not sure about this, that would place the burden on managing cache invalidation on the developer - which hasn't been working out well with the old image pipeline, where we would only update these images once or twice a release cycle.

Would it make sense to split the workflow into two - one for building the binaries and another for the podvm image ?

Not sure about this, that would place the burden on managing cache invalidation on the developer - which hasn't been working out well with the old image pipeline, where we would only update these images once or twice a release cycle.

I see..


Author by letter

Rewrite of page using Vue.js components.
author name opens new tab to show
sources for each author are listable, showable from each list element
author names and sources are pinnable, deletable.  sources addable/removable from this project.

Coverage increased (+0.004%) to 72.359% when pulling 0e2e680070f0d174f9c0fc438ab18740b7135882 on author_by_letter into 26128386abbcfb7e612c0a3912198bca90d57e38 on development.

Use relative paths to import generic components, for example:
import RadialAnnotator from '../../../../components/annotator/annotator'
For:
import RadialAnnotator from 'components/annotator/annotator'

Merged development into this branch, ready to merge back.


6.3.2 breaks BullMQ-Pro lib

Hi, we use bullmq pro for the group features, and your dashboard has been wonderful to use. But it seems 6.3.2 broke the ability to attach to bullmq-pro queues here: d0e42c7
setup a new QueuePro:
const queue = new QueuePro(queuename, queueoptions);
reference that queue when setting up a new bull-board:
queues: _.map(queues,(q) => new BullMQAdapter(q))
and it throws "You've used the BullMQ adapter with a non-BullMQ queue"
Assuming this is because of the type is QueuePro, would there be a different check that could be used?
instead of if (!(queue instanceof BullQueue)) could use "libName" from the queue object? in pro it's just "bullmq-pro"? or anything similar?

Hi, I can check alternative ways, it is a breaking change, since we don't support bullmq-pro officially.

thanks, I know you don't want to support pro features, but it would be great if it still worked for the regular stuff.
if you need anything from my side about what is in the QueuePro object, let me know. Appreciate it!

Yeah, can you share how can i distinguish a ProQueue?

the only thing i can think of right now is !(queue instanceof bullmq_1.Queue || queue.libName === "bullmq-pro") it seems bullmq-pro is shipped with it's own bullmq, which is different than that of the bullmq included by your package.json, so direct compares with instanceof fails.
I don't "love it" but it would work?

I've checked that libName field, the problem is that it protected, which means TS won't allow to access it (it may change since it is not public)

Can u test v6.4.1?

working well, thank you!

For the record, the version field appeared last month in bullmq 5.20, previous versions (still 5.x) will experience this Cannot read properties of undefined (reading 'startsWith').

For the record, the version field appeared last month in bullmq 5.20, previous versions (still 5.x) will experience this Cannot read properties of undefined (reading 'startsWith').

Thank for the notice... I'll add an additional check


Windows can't find ebook-convert

I'm on Win10. I have Calibre installed. I can run ebook-convert via command line and get the man page, but running ruby oathbringer.rb with an output of :mobi will always result in:
[html] Generated HTML file
[error] Can't generate MOBI without ebook-convert
[error] Please check README for PDF dependencies
I have all other dependencies (except PDF, but I'm running :mobi specifically).
Edit: Ran it in my Ubuntu VM and it worked fine. Windows still does not work.

Thanks for the report.
Can you try the following in your console:
 irb
2.4.1 :001 > require './methods'
 => true
2.4.1 :002 > command? 'ebook-convert'
 => "/usr/bin/ebook-convert"

This was the output:
λ irb
irb(main):001:0> require './methods'
=> true
irb(main):002:0> command? 'ebook-convert'
=> nil
irb(main):003:0>


Query button does not complete once the table row limit has been reached for an query

I have a bunch of test queries that I use for performance testing that return 100k rows then terminate.
in the latest release, although 100k rows are returned the big green query button does not halt once 100k rows have been returned.
Server tasks show no activity for the search.

Queries appear to complete eventually, but timescales indicate it may be continuing to search


Handled missing data

NA values of X in execution block 15 had to be removed.

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

Thanks @prateekmantha! Merging


Fixed the crono job overflowing the log column

Before this commit, the crono job kept on adding the log into the log column
from the crono_jobs table. This is, of course, a bad thing. What I did to fix
this is to simply remove this columns from the DB, and crono is ok with that.
Running crono again with this patch runs in the very same way as it used to be,
but without adding the log all the time.
Moreover, the log is supposed to go to the stdout, as envisioned by the
Twelve-Factor App manifesto: http://12factor.net. Docker follows this too, and
by doing so then the log of this job blends in with docker-compose logs
command. This has two main consequences:

The user can decide how to manage logs in an easier way, so there's no way
that we run out of disk (an issue we were having).
supervisor is no longer needed. Instead, we take advantage of the
compose-setup.sh script to do it properly. Before this patch, for some
reason the catalog job did not reach the db container.

Fixes #479
Fixes #505
Signed-off-by: Miquel Sabaté Solà<EMAIL_ADDRESS>

This should be backported to the v2.0.0 branch when merged.

I cherrypicked the fix into the v2.0 branch


Keptn CLI: support of 'add secret', 'start evaluation', 'get evaluation-results'

The Keptn CLI needs to support:

keptn add secret
E.g.: keptn add secret secret.yaml

Creates a Kubernetes secret based on the credentials stored in secret.yaml.

keptn start evaluation
E.g.: keptn start evaluation --project PROJECTNAME --service SERVICENAME --reference test-run-A --start 2019-07-24T10:17:12 --period 5m

The start-evaluation command, as shown above, will evaluate the service level objects of the specified service in the specified project over the last 5 minutes and will save the results under the reference test-run-A. This command will return a KeptnContext ID that you will need for querying the results of the evaluation.

keptn get evaluation-results
E.g.:

keptn get evaluation-results --project PROJECTNAME --service SERVICENAME --reference test-run-A
keptn get evaluation-results --keptnContext 1234-5678-90

Returns the results of the same Keptn quality gates evaluation. The results come in the form of the evaluation-done event, that is specified here.

Satus:

[ ] keptn add secret secret.yaml
[x] keptn send event evaluation.start
[x] keptn get event evaluation.done
[ ] check args for keptn send event

About the add secret command: @bacherfl and myself are using kubectl as follows to add the relevant secrets within the keptn namespace:
kubectl create secret -n keptn generic dynatrace-credentials-sockshop --from-file=dynatrace-credentials=./my-dynatrace-credentials.yaml
kubectl create secret -n keptn generic prometheus-credentials-sockshop --from-file=prometheus-credentials=./my-prometheus-credentials.yaml

The secret contains the API URL as well as username/password or a token.
I think for now this is sufficient, but I'd like to see a keptn create secret command looking something like this (in accordance if the keptn add-resource command):
keptn add-secret --project=sockshop --name=dynatrace-credentials --resource=./my-dynatrace-credentials.yaml

Where as the file provided in resource gets uploaded to the REST API, and the REST API then adds this to the current kubernetes cluster as a secret.


Add www.paramountnetwork.it/

Hi, is to add https://www.paramountnetwork.it/ for example https://www.paramountnetwork.it/film/218i3r/agatha-christie-le-due-verita-parte-1
thank you

Sorry, I didn't get your question :
Do you ask how to download it ?
or
Do you ask to add this functionality ?


Parse imports using the GHC api

There is a call getImports in the ghc api which seems to return all the information that himportscan produces.
https://gitlab.haskell.org/ghc/ghc/-/blob/ghc-8.10.7-release/compiler/main/HeaderInfo.hs#L56-67
-- | Parse the imports of a source file.
--
-- Throws a 'SourceError' if parsing fails.
getImports :: DynFlags
           -> StringBuffer -- ^ Parse this.
           -> FilePath     -- ^ Filename the buffer came from.  Used for
                           --   reporting parse error locations.
           -> FilePath     -- ^ The original source filename (used for locations
                           --   in the function result)
           -> IO (Either
               ErrorMessages
               ([(Maybe FastString, Located ModuleName)],
                [(Maybe FastString, Located ModuleName)],
                Located ModuleName))
              -- ^ The source imports, normal imports, and the module name.

Calling this is probably going to be preferable to maintaining our custom parser in
https://github.com/tweag/gazelle_haskell_modules/blob/4b43a2038fdc3d2b7f2aca6d80fcc680a2d11be7/himportscan/src/HImportScan/ImportScanner.hs#L132

I'll investigate this.

This would be much easier on newer ghcs as we wouldn't have to deal with DynFlags. getImports uses only ParserOpts (a much smaller subset of the "current" DynFlags) on ghc >=9.2.


Adds ability to set where composer is located

Since my app is on shared hosting, I use a phar file instead of actual composer. Ensemble shouldn't care where composer is located, it should pick a sensible default but allow the user to override it.

Thinking about it, it might be easier to just add composer as a dependency to your project https://packagist.org/packages/composer/composer
Then you get the composer executable inside of vendor/bin!

Closing in favour of #5


feat: url parser

Codecov Report
Attention: Patch coverage is 95.45455% with 1 line in your changes missing coverage. Please review.

Project coverage is 92.75%. Comparing base (060295f) to head (fd88893).

Files with missing lines
Patch %
Lines

src/Didot.Core/SourceParsers/UrlSource.cs
95.00%
0 Missing and 1 partial :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #42      +/-   ##
==========================================
+ Coverage   92.63%   92.75%   +0.11%
==========================================
  Files          20       21       +1
  Lines         448      469      +21
  Branches       61       65       +4
==========================================
+ Hits          415      435      +20
  Misses         13       13
- Partials       20       21       +1

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


Detecting the OS that Parabeac is running on and extracting the current directory

Request Type:  New Feature Proposal.
Description
This would allow for Parabeac Core to detect the OS that it is being run in and then based on that information identify the current directory it is in as well. This would be very helpful in helping to support Parabeac Core outside of just Mac and Linux environments as well as help set the groundwork for automatic path usage within Parabeac Core.
Files Affected:

main.dart
parabeac.dart

Additional Notes:

Hey @Ihuds577, can I take this?

This should've been closed.


[cli] Delete all files if cli fails

@danstepanov Re-opening this -- the refactor happened to support it (we now have projectName available within the } catch (error) { block) but the TODO is still there.
It's possible just uncommentting that line fixes it, but there may be edge cases. Will make this "good first issue".

@sammoore why was the delete files thing commented out rather than implemented?

@sammoore why was the delete files thing commented out rather than implemented?

No reason other than the fact that I was already testing the refactor with all it's edge cases, and wanted to get that merged in without also testing deleting files.

Word, I'll try to test this out today


Android elevation value doesn't put effect after upgrading to 0.64.2

Description
Elevation value doesn't put effect even if it is increased to a large value. I just upgraded from 0.61 to 0.64, no code change, it suddenly stopped working.
Here is the change compared:

React Native version:
0.64.2 Latest version
Steps To Reproduce
Expected Results
It should stay like before, as you can see in my screenshot
Snack, code example, screenshot, or link to a repository:
Screenshot attached above

It seems elevation property now gets overridden by other shadow properties you probably initially aimed for iOS only. I am utilizing styled-components and after making box-shadow iOS specific, elevation started working again as before 👍
 Platform.select({
      ios: css`
        box-shadow: ${({ theme }) => theme.boxShadow[boxShadow]};
      `,

I guess it is linked to the new shadow color support on Android?

Reading @AronBe  's comment, I found that elevation works if I remove shadowColor property.
Thanks!

Reading @AronBe 's comment, I found that elevation works if I remove shadowColor property.
Thanks!

Dear Madcoderme, it using rn 0.64.2 and elevation not work for android. Please help me. Thanks

Reading @AronBe 's comment, I found that elevation works if I remove shadowColor property.
Thanks!

Dear Madcoderme, it using rn 0.64.2 and elevation not work for android. Please help me. Thanks

Did you try what solved for me? Removing shadowColor?

I removed but not work. I found but not solution.

@thainm80 maybe you are using any of these properties?
https://reactnative.dev/docs/shadow-props
anyway, you should share your element code/styles if still not finding a help

I removed but not work. I found but not solution.

As @AronBe said, please share your code so we can check for possible solutions

 navigation.navigate('Contact')} />
                  Liên Hệ

const styles = StyleSheet.create({
navBarButton: {
flex: 1,
flexDirection: "column",
alignItems:"center",
marginLeft: MisoSize(10),
marginRight: MisoSize(10)
},
navBarButtonIcon: {
borderColor: "#50b848",
backgroundColor: "#fafafa",
color: "#50b848",
borderWidth: 0,
shadowColor: "#999999",
shadowOffset: {
width: 0,
height: 2
},
shadowOpacity: 0.25,
shadowRadius: 4,
elevation: 5
},
navBarButtonText: {
alignSelf: "center",
fontSize:MisoSize(13),
fontWeight: "normal",
color: "#686f74",
alignSelf:"center"
},
})
I run on RN 0.61 normally. After upgrading to 0.64.2, the shadow is lost. Please help me.

You didn't remove these shadow props from navBarButtonIcon style @thainm80
shadowColor: "#999999",
shadowOffset: {
width: 0,
height: 2
},
shadowOpacity: 0.25,
shadowRadius: 4,
elevation: 5

If you only target android, remove them directly.
(RECOMMENDED) If you target IOS too, use platform specific code. Read about it here: https://reactnative.dev/docs/platform-specific-code

I found the cause of the error.
In Android->app->Androidmanifest.xml I added "android:hardwareAccelerated="false" to prevent the app from crashing.If I remove it, Shadow is normal.But if I remove "android:hardwareAccelerated="false" the app crashes.

Is there a way to replace android:hardwareAccelerated="false" . Please help guide me

"

"

I am quite confused at this point.
When does it crash?
Did you check adb log?

I use @react-navigation/bottom-tabs, when I open the details page and -> scroll to the middle of the page -> back it crashes

I use @react-navigation/bottom-tabs, when I open the details page and -> scroll to the middle of the page -> back it crashes

This is really weird, can you check adb log?
You need to run adb logcat in terminal for this

I run adb with logcat error:
"Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x1c in tid 1022 (RenderThread), pid 979"

Are you using a real device?

I using simulator Nexux X5. It also crash on real devices. In IOS is not Crash

Can you try putting back the settings of hardwareaccelerated value and removing shadow props entirely?
I am not an experienced android developer but if it happened to me I would try that too

Can you give me an example here?
"removing shadow props(except elevation) entirely"

From
shadowColor: "#999999",
shadowOffset: {
width: 0,
height: 2
},
shadowOpacity: 0.25,
shadowRadius: 4,
elevation: 5

To
elevation:5

(for testing)

I have also tried this, but it still doesn't work.

No shadow appears?

If the shadow doesn't appear (with hardwareaccelerated prop set), i can't find any other solution rn.
You can create another issue or possibly reopen this issue.
Another hacky solution is to use a circular icon component instead of view component. Icons support all text shadow props.

That's right. I tried many ways without showing shadow if hardwareaccelerated prop set

Thanks everyone. I fixed this error (Crash by Webview and navigation)
Just add attribute androidHardwareAccelerationDisabled={true} to webview


Alhamdulillah no issue whatsoever 🥰

Really great project...keep up the good work fam.💥💯💝

Really great project...keep up the good work fam.💥💯💝

Thanks for trying!!! 🤍🤍🤍


Does pinpoint support statistics of transaction volume per second？

Hi, I want to call http GET request  getServerMapData.pinpoint to get the call volume per second for my app, but the results were depressing.
I want to known does pinpoint support statistics of transaction volume per second？
Analysis the data ， i think pinpoint has stroed the data into hbase.
Can you give me some advice？
Thanks !

@emeroad

Unfortunately, ServerMap do not support seconds precision.


pod is stuck on a "bootloop"

Chart Name
homarr
Chart Version
1.2.6
Problem
I'm getting liveness-prob failures, although the service for some time is up, and it is stuck in this loop.
(in the screenshot below from lens IDE, I tried to downgrade the homarr image version to 0.15.3, but nothing changed)

values.yaml
image:
  tag: "0.15.4"
env:
  TZ: "Europe/Athens"
imagePullSecrets:
- name: regcred
ingress:
  enabled: true
  ingressClassName: "nginx"
  annotations:
  # Add any additional annotations as needed
  hosts:
    - host: homarr.d2-services.home.local
      paths:
        - path: /
          pathType: ImplementationSpecific
  tls:
    - hosts:
        - "homarr.d2-services.home.local"
persistence:
- name: homarr-config
  enabled: true
  storageClassName: "vsphere-csi-sc"
  accessMode: "ReadWriteOnce"
  size: "512Mi"
  mountPath: "/app/data/configs"
- name: homarr-database
  enabled: true
  storageClassName: "vsphere-csi-sc"
  accessMode: "ReadWriteOnce"
  size: "512Mi"
  mountPath: "/app/database"
- name: homarr-icons
  enabled: true
  storageClassName: "vsphere-csi-sc"
  accessMode: "ReadWriteOnce"
  size: "512Mi"
  mountPath: "/app/public/icons"

Relevant log output
Exporting hostname...
Migrating database...
yarn run v1.22.19
$ ts-node ./migrate.ts
Done in 9.56s.
Starting production server...
Listening on port 7575 url: http://homarr-7fdf4cdfbb-wml77:7575
ℹ Instance is using a database on the file system. Checking if file '/data/db.sqlite' is writable...
ℹ Instance is using a database on the file system. Checking if file '/data/db.sqlite' is writable...
ℹ Instance is using a database on the file system. Checking if file '/data/db.sqlite' is writable...
ℹ Database is writeable
ℹ Database is writeable
ℹ Database is writeable
ℹ Instance is using a database on the file system. Checking if file '/data/db.sqlite' is writable...
ℹ Database is writeable
ℹ Instance is using a database on the file system. Checking if file '/data/db.sqlite' is writable...
ℹ Instance is using a database on the file system. Checking if file '/data/db.sqlite' is writable...
ℹ Instance is using a database on the file system. Checking if file '/data/db.sqlite' is writable...
ℹ Database is writeable

Kalimera @athamour1,
Thank you for reporting the issue. I deployed the latest chart with your provided values on a kind cluster and was unable to reproduce the problem. Could you please share more details about your cluster setup?
FYI: The current version of Homarr doesn't include dedicated liveness/readiness endpoints, so the URL is temporarily set to /.
Additionally, this chart will soon be moved to the official repository. You can check out the draft chart here: https://github.com/homarr-labs/charts/pull/2

I was stuck with the same problem just a few hours.
Logs were similar to @athamour1 ones.
I had to leave for a while and when i came back homarr was back online.
One possible problem might be homarr page loading times. I have noticed that Homarr page can take a while to load on the browser sometimes. If this were to happen with the liveness probe then it would probably exceed the timeout time for the probe.
If i ever come across this error again i will try to change the timeoutSeconds to a bigger value and check if thats the problem.

@eivarin Thank you for your feedback! I've now added the option to configure the readinessProbe and livenessProbe settings. Let me know if this resolves any issues.


Cookie parsing is a breaking issue for porting to asp.net core

Cookie parsing logic is breaking!
To Reproduce
Steps to reproduce the behavior:

Set a string as cookie value which has double quotes in it.
Try to read it using HttpContext.Request.Cookies
See cookie cannot be read in asp.net 2.2 while it works on a 4.7.2 app

Detailed repo.
I have some Javascript code which writes cookie value
setCookie('a','{"m":"en-gb"}',1);
setCookie('c','en|us',1);

Cookies are set and you can see in chrome dev tools.

The first cookies value is a JSON string version of a JS object. Now try to read this in 4.7.2 app
var allKeys = this.HttpContext.Request.Cookies.AllKeys;
Here you will get both a and c
Now try the same in asp.net core 2.2 app
var allKeys = this.HttpContext.Request.Cookies.Keys;
You will get only c!
When you access this.HttpContext.Request.Headers["Cookie"], you will see the below value
{a={"m":"en-gb"}; c=en|us}
This is a breaking issue as we have legacy app which has this cookie value and we are trying to port it to asp.net core 2.2 and we will not be able to read this cookie value using HttpContext.Request.Cookies. We will be running both versions of the app (4.72 and 2.2 and the proxy sends traffic to either one instance based on configured rules (ex: running A/B tests)
I see some strict character checking here. Is there a recommended solution to address this issue ?

Let me know if you need a repro solution for the above.

Related: https://github.com/aspnet/AspNetCore/issues/5685#issuecomment-448763553
Summary: JSON syntax is not valid in cookies. In this example it's the quotes " that are prohibited.

Closing as this isn't something we plan to support. If you need to store cookies like this, you could try base64-encoding first.

Thanks @Tratcher


refactor Reduce prepare overhead (PART II)

Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


No search function

A good search function is what I miss most so far.
Without the option to look for a specific entry searchin lots of posts is exhausting.

Hi, yes I know.. It's on the todoList http://forum.bludit.com/viewtopic.php?f=13&t=28

I know ;)
Just trying to push it a little. No offense meant.
Cheers
Nick
On 5. Nov. 2015, 04:03 +0100, Diego<EMAIL_ADDRESS>wrote:

Hi, yes I know.. It's on the todoListhttp://forum.bludit.com/viewtopic.php?f=13&t=28
—
Reply to this email directly orview it on GitHub(https://github.com/dignajar/bludit/issues/82#issuecomment-153941065).

Yes I agree. As far as I can remember even Nibbleblog lacked a default search option. A search query which can search through all the posts, posts titles, pages, page titles and tags would be awesome!
Temporarily I am using Google to search through my blog(after its crawled once) with this query
site:domain.com search_query_here

as a workaround.

Any news on the search function yet?

I am also looking forwarding to a search function.

I am also looking forwarding to a search function.

I am also looking forward to a search function.

I'm well aware that searching inside posts is not a trivial task when it comes to performance.
So in a first step, I would consider only searching in post titles, tags and so on.
And I think we really need an internal search function. Bludit is technically so cool - you can carry it around on a usb stick, use old PHP version with only the internal server to run it. Having an external dependency for searching does not feel right to me.

While maintaining our internal news system with bludit, it is now getting increasingly difficult to navigate between hundreds of blog entries without a proper search function.

Anything new regarding an internal search function yet?

Hi guys, I wrote a small search script for personal use. https://github.com/anaggh/Bludit-Search Maybe someone could improve it/convert it to a plugin.

Hey nice. That's definetely a start.
Do you search through all content or only the title and tags?

Searches all content and title. Tags are not searched.
Here's a screenshot:

I think you should have two search modes.
Rather than content and title you should either search content+tags+title, or (quicksearch) title+tags.

Hey Diego, can you integrate this into bludit so that the search can be covered by this routine?

Hi, I have rewrote the search script from scratch. Now there is only one search box and button.

Fixed "Child Page" search results not being displayed.
Now it searches - titles, tags, username, description, content of both pages and posts.
It ranks them according to relevance now.

type
score

title
+30 points

tags
+15 points

description
+10 points

username
+5 points

content
+1 point each line

You can add it to your theme after copying search.php by including this snippet in your sidebar.
<!-- Search -->
<form role="search" action="<?php echo $Site->url() . 'search.php';?>" target="_blank">
    <input type="text" name="q" placeholder="Search...">
</form>

Only thing left now is pagination. If someone can convert this to a plugin or add the pending pagination, please send a pull request.

Fantastic !!! Thanks

Anyone here who is experienced enough to be able to create a real plugin for us based on this?
I think it's time to include this into the bludit code base.

Anaggh's search works great on https://github.com/bludit/bludit/commit/8cfd7df062f373dcbc2a272cd60270d9b4b76bd6 .
Can't it be included in the v3.0 core as a plugin?

Implemented in Bludit v3.1.0. Thanks!


support nwb format in all widgets

@bendichter
A next crucial step will be to have all the widgets support other input formats, including nwb. SpikeInterface is already set up to do this, but there is some trickiness regarding directories vs files as input parameters. I want to try to avoid a lot of if statements outside of SpikeInterface code because spikeextractors is supposed to handle it. I'm thinking about how to do that now.

ok that makes sense!

you might be interested to know about the NwbSortingExtractor currently under development here


Consider adding field type "bool"

Description
It may be useful to support a field type bool. This field would basically maintain two rows: 0 = false, 1 = true.
This field type would support a Set() query on the bool field vip like:
Set(100, vip=true)

Internally, Pilosa would do the equivalent of:
// vip=true
Clear(100, vip=0)  // clear the false bit
Set(100, vip=1)  // set the true bit

// vip=false
Set(100, vip=0)  // set the false bit
Clear(100, vip=1)  // clear the true bit

// query for vip=true
Row(vip=1)

// query for vip=false
Row(vip=0)

Alternatively, the bool field could maintain only a true row along with a not-null row. That would look like this:
// vip=true
Set(100, vip=0)  // set the not-null
Set(100, vip=1)  // set the true bit

// vip=false
Set(100, vip=0)  // set the not-null bit
Clear(100, vip=1)  // clear the true bit

// query for vip=true
Row(vip=1)

// query for vip=false
Difference(Row(vip=0), Row(vip=1))

As an additional thought, the bool field is really a sub-set of a mutually exclusive enum field, so we may consider how the implementation of an enum field and/or a mutually exclusive field fits in as well.

Old but related: https://github.com/pilosa/pilosa/issues/434

Isn't Set(vip=100) equivalent to Set(100, vip=0) and Clear(vip=100) to Set(100, vip=0) ? Having a single row would eliminate the need for a mutex field.

@yuce if you use a single row (in your example, row=0) to indicate true/false, then you don't know which columns are actually false, and which just have never had a value set. So in your example, if the use case allows for the two conditions "true" and "false or not set", then your example definitely works.


build a "Tutorials" top-level index page

This page should have a list of tutorials, with a short description of each tutorial.
The first tutorial is going to be the "Get Started Tutorial", which is the most detailed one and full of comments, explanations, and links to other resources.
The other tutorials are links to interactive Katacoda tutorials.
Maybe we can also list some tutorials that are explained on external blog pages.

By the way, I am planning to merge this: https://dvc.org/doc/get-started/example-pipeline
and this: https://dvc.org/doc/tutorial and to make an interactive tutorial based on them (which is going to be something like this: https://katacoda.com/dvc/courses/tutorials/versioning).
This implies that the the two pages mentioned above, as well as this one: https://dvc.org/doc/get-started/example-versioning are going to be removed from the structure of the docs, since they will be replaced by interactive tutorials.

By the way, I am planning to merge this: https://dvc.org/doc/get-started/example-pipeline
and this: https://dvc.org/doc/tutorial

I think there is a ticket to consolidate NLP example and tutorial (by simplifying tutorial). Again, I don't see how this can be replaced by Katacoda. I would expect it to have a link to Katacoda for those who want to run. Similar to Pytorch's Run in Colab, etc.

are going to be removed from the structure of the docs, since they will be replaced by interactive tutorials.

I consider online tutorials complementary but not as a replacement for text based docs. There are a lot of reasons for this, major are:

we can't depend on a third party service for the core flows - no guarantees they will stay and work, no SEO, we don't control quality (highlighters, links to commands, diagrams), most likely limited in terms what can be done
interactive vs text - is a matter of taste and there no reason to not have both

@jorgeorpinel could you please, link the related consolidation tickets here please? and other related issues that come to your mind.

Sure:

I think #425 unbundle "Understanding DVC" docs is the oldest one.
No, actually this one is older: #340 config: split up cmd ref into user guide + cmd ref
This would be a new section: #463 document DVC API
Another new section: #550 new "Basic Concepts" doc(s)
➡ This one specifically relates to tutorials: #564 reorganize get-started examples into tutorials
Finally, #566 use-cases: extract them into actual articles?

I consider online tutorials complementary but not as a replacement for text based docs.

We can have them both. I don't see any problems with this.

we can't depend on a third party service for the core flows - no guarantees they will stay and work

This is a valid concern. I have been thinking about it myself as well.
However notice that the code of the interactive lessons is just markdown (with small extensions), for example: https://github.com/iterative/katacoda-scenarios/blob/master/basics/pipelines/step1.md
It is possible to convert them automatically to pure markdown (or to extend our engine to display them properly). Then to try these commands, all you need is an ubuntu-18.04 docker container.
So, in case that Katacoda somehow perishes, not everything is lost. We can publish ourselves the content of the lessons, and the users will have to use a docker container to try them, which is not a big inconvenience.

I think there is a ticket to consolidate NLP example and tutorial (by simplifying tutorial).

I have just finished an attempt of consolidating these two tutorials (https://dvc.org/doc/get-started/example-pipeline and https://dvc.org/doc/tutorial).
The resulting online tutorial is here: https://katacoda.com/dvc/courses/tutorials/pipelines
This part has not been included yet: https://dvc.org/doc/tutorial/sharing-data
I am going to list this one as well on the Tutorials index page.

@dashohoxha
We still need to decide what should we do with the lengthy one. It includes a lot of information. May be put some of those explanations as expandable sections into the former example-pipelines? I also, don't know what should we do with sharing-data and other info about DVC that overlaps with basics, get-started, etc. @jorgeorpinel what are your thoughts about this?
Some feedback on the new tutorial:

It looks like this new interactive tutorial is purely based on the example-pipeline? If it's the case, I would just modify example-pipeline to have a link to the interactive version. Not sure if it makes sense to include it as an item in the Tutorials section - we'll have three versions of the same thing that way.
It feels that it lacks some explanations (like you do cat or a tree and I don't know what should I be paying attention to). It might fine if it comes as a complimentary to the text/wordy version.
Do you know if Katacoda has hot keys to execute commands with? It's annoying that I have to click every code line to get the final result.
 Or may be I'm missing it somewhere in the interface?

Btw, https://kubernetes.io/docs/tutorials/ - is a good example on how can we organize and integrate interactive tutorials and text versions.

We still need to decide what should we do with the lengthy one. It includes a lot of information. May be put some of those explanations as expandable sections into the former example-pipelines?

It seem to me that the explanations on the Long Tutorial are replicated all over the rest of the docs. So, if we just drop it, I think we are not going to loose much (especially considering that it is a bit outdated and seems to be broken).
Besides this, on the Community Tutorials section, the first blog is this one: https://blog.dataversioncontrol.com/data-version-control-tutorial-9146715eda46 which is exactly the same as the Long Tutorial.

I also, don't know what should we do with sharing-data

I didn't include it in the interactive tutorial (https://katacoda.com/dvc/courses/tutorials/pipelines) because I don't see how to make this part interactive. However I am sure that there are similar examples about sharing data elsewhere in the docs.

It looks like this new interactive tutorial is purely based on the example-pipeline? If it's the case, I would just modify example-pipeline to have a link to the interactive version. Not sure if it makes sense to include it as an item in the Tutorials section - we'll have three versions of the same thing that way.

I think that it is better to keep them as separate items (as they are now). Also they are not exactly the same. The interactive tutorial covers more scenarios than the native one.

It feels that it lacks some explanations (like you do cat or a tree and I don't know what should I be paying attention to). It might fine if it comes as a complimentary to the text/wordy version.

It is so because some things have been explained previously. In particular, it is assumed that at least the Basics and Get-Started have been finished before starting a ML tutorial. Those cat and tree are just to track what is happening. The user could normally do them himself, but I am putting them there just as a reminder and as a convenience.

Do you know if Katacoda has hot keys to execute commands with? It's annoying that I have to click every code line to get the final result.

I don't know. But the student is assumed to type the commands on the terminal, because this way he can benefit most from the tutorial. Clicking the command (which makes an automatic copy/paste) is just a convenience. It is useful for example for me, when I go through the tutorial to check it.

 Or may be I'm missing it somewhere in the interface?

Katacoda does not have such a feature, but it allows you to upload scripts in the virtual machine. Then you can instruct users to run those scripts, or you can tell Katacoda to run them automatically at the beginning of the step.

Btw, https://kubernetes.io/docs/tutorials/ - is a good example on how can we organize and integrate interactive tutorials and text versions.

The kubernetes page seems to be an exemplary page for all the docs, not just for the interactive tutorials :) We can try our best, but I am not sure whether we can match their quality.
But honestly, I think that each software has its own specifics, so something that works well for one of them may not work so well for another. We see this for example when we try to compare DVC and Git.
I also don't like that they embed Katacoda scenarios on their doc pages. This makes it less comfortable to work with them.


Update yaml2text documentation (blog post and yaml2text documentation)

metanorma/metanorma-standoc#327, #331 documentation for yaml2text liquid support. @opoudjis @ronaldtse i have mentioned metnorma-standoc new version as 1.5.3, fell free to change it for the actual one after the release.

@w00lf The examples inside the page haven't been updated to Liquid yet. Can you please help update them too? e.g.

Thanks!

@w00lf The examples inside the page haven't been updated to Liquid yet. Can you please help update them too? e.g.

Thanks!

Done, added

@w00lf thanks, but we still have the remaining examples in yaml_to_text.adoc file that use the old syntax. Can you help convert all of those to the new syntax? Thanks!

@w00lf thanks, but we still have the remaining examples in yaml_to_text.adoc file that use the old syntax. Can you help convert all of those to the new syntax? Thanks!

yaml_to_text.adoc

I need to convert all old examples to liquid?

Yes we want to drop the old syntax, so we want to convert all the examples.

Yes we want to drop the old syntax, so we want to convert all the examples.

Should i only leave block defining syntax, e.g. [yaml2text,strings.yaml,arr] and omit all other features? E.g. instead of using {arr.*,item,EOS} for iteration we now will use liquid iteration syntax, should we drop support for *.# special characters from docs?

Should i only leave block defining syntax, e.g. [yaml2text,strings.yaml,arr] and omit all other features? E.g. instead of using {arr.*,item,EOS} for iteration we now will use liquid iteration syntax, should we drop support for *.# special characters from docs?

I think we should drop support for *.# also because it can be done using Liquid with filter xxx | size.

Should i only leave block defining syntax, e.g. [yaml2text,strings.yaml,arr] and omit all other features? E.g. instead of using {arr.*,item,EOS} for iteration we now will use liquid iteration syntax, should we drop support for *.# special characters from docs?

I think we should drop support for *.# also because it can be done using Liquid with filter xxx | size.

@ronaldtse updated all examples to use liquid syntax instead, gave refs to the official docs.

Thanks @w00lf !


Can't run any trials

When I run the NNI example mnist in a Linux environment, it seems like everything is ok. However, it can't run any trials and the experiment has been over. Could you give me some suggestions?
Notation that the environment which I can't manage is a Cloud Platform controlled by someone, and any python script is run by sbatch, python x.py is prohibited.

nni Environment:

nni version:
nni mode(local|pai|remote): local ( I upload all of dataset and code)
OS: Linux
python version: 3.6
is conda or virtualenv used?: conda
is running in docker?: No
It seems everything is ok unless it can't run any trials.

Can you share your config.yml? Did you use sbatch to launch trial? As far as I know, sbatch will return immediately when the job gets queued.

Can you share your config.yml? Did you use sbatch to launch trial? As far as I know, sbatch will return immediately when the job gets queued.

This is my config.yml. And I don't know how to run a trial by sbatch. I can run a experiment by sbatch only.

So you run nnictl with sbatch right? It's like sbatch nnictl ...?
Assuming you are using slurm, did you check squeue for your job status? Does the job complete very quickly in seconds (or minutes)?

So you run nnictl with sbatch right? It's like sbatch nnictl ...?
Assuming you are using slurm, did you check squeue for your job status? Does the job complete very quickly in seconds (or minutes)?

I checked squeue. The job finishes quickly ( about two or three munites ).
I modify my sbatch file, according to your advice

Then I find it doesn't still work. And NNI's log file is empty.

So you modify your file to be sbatch nnictl? So what did you do previously? Where did you use sbatch?
To run nni on slurm, a simple workaround is to try to add sleep 30000000 after nnictl. Because nnictl exits immediately after it launches the experiment, and slurm believes your job has finished and will release your resources. That's why your experiment exists quickly.

Thanks for your help !!!
How to add sleep 30000000 after nnitcl ?
modify the config file?

@cjissmart You can follow the practice of sbatch, which writes a script containing nnictl and sleep. I'm sure it's mentioned in your manual.

So you modify your file to be sbatch nnictl? So what did you do previously? Where did you use sbatch?
To run nni on slurm, a simple workaround is to try to add sleep 30000000 after nnictl. Because nnictl exits immediately after it launches the experiment, and slurm believes your job has finished and will release your resources. That's why your experiment exists quickly.

Thanks for your help !!!
How to add sleep 30000000 after nnitcl ?
modify the config file?

Seems the "can't run trials" problem is resolved closing the issue. thanks for the feedback, feel free to open issue for new questions or reopen the issue if the problem occur again.


ROS2: ff_msgs and ff_hw_msgs

As in the title, porting ff_msgs and ff_hw_msgs. Moreover, the few changes were added:

Colcon Ignore to all packages except astrobee and communications
Deleted deprecated nodes

Can we hold on deleting dds_msgs and dds_ros_bridge for now? At least until we test that the new comms work on the robot, Katie is looking into it

It's good to see some forward progress!
I agree with @marinagmoreira that, in general, we should try to be very conservative about changes that aren't 100% required to get things to build and run properly under ROS2. ("If it ain't broke, don't fix it.")
For example, it seems risky to change field names from camelCase to snake_case, even if it gets us closer to the usual ROS style conventions, because that change will affect lots of code throughout the repo, and even likely cause hassles with migrating legacy telemetry bags recorded on ISS. (Using ROS2 doesn't require snake_case, does it?)

At least until we test that the new comms work on the robot, Katie is looking into it

I'll take a stab at what conditions would need to be met before dds_ros_bridge is removed:

We are past end-of-life for Astrobee ROS1 support (the ROS2 migration is fully complete for all legacy guest science on-orbit activities).
AND we have some other solution for conveying ROS2-dialect DDS messages to the Astrobee control station, which currently speaks the NASA RAPID dialect of DDS.

Because of DDS dialects issue, it's quite possible that we'll continue using something analogous to dds_ros_bridge after the ROS2 transition, but that its job will change from bridging ROS1-TCPROS -> RAPID-DDS to bridging ROS2-DDS -> RAPID-DDS. And even if we find a workaround for the issue of different DDS dialects, a simpler bridge may still be worthwhile to help manage bandwidth on the space-to-ground link, for example by throttling message frequency on some topics.

trey0

Unfortunately it does @trey0, otherwise I would have skipped it. It errors out during the stage.
Regarding dds_ros_bridge, sounds good, I can keep it and let it be ignored for nowaybe?

(Using ROS2 doesn't require snake_case, does it?)

Unfortunately it does @trey0, otherwise I would have skipped it. It errors out during the build stage.

I see. Then that's one more place to think about the best way to capture different versions.

Regarding dds_ros_bridge, sounds good, I can keep it and let it be ignored for now maybe?

Well, it's already tracked separately in the task list at a lower priority, so I think it's the team consensus that it can wait.

I see. Then that's one more place to think about the best way to capture different versions.

Trey, I'm not completely sure if I agree with going back to camelCase definitions if the ROS and Cpp best practice is lower case. I agree it is a breaking change, but maybe enforcing this would be a good way forward? I leave it to the team in any case https://google.github.io/styleguide/cppguide.html#Variable_Names

Trey, I'm not completely sure if I agree with going back to camelCase definitions if the ROS and Cpp best practice is lower case. I agree it is a breaking change, but maybe enforcing this would be a good way forward? I leave it to the team in any case https://google.github.io/styleguide/cppguide.html#Variable_Names

I'm not sure I understand exactly what you're proposing. We can discuss tomorrow.
My thinking was this: If we are able to figure out universal packages (ROS1+ROS2) I was assuming that the ROS1 version of the universal package would keep the legacy field names to avoid a breaking change in the guest science API, and the ROS2 version would grudgingly make whatever field name changes are required for ROS2 compatibility.
Code that uses the messages with modified field names could be well served by a definition like this:
#if ROS_VERSION == 1
#define FF_ROS_my_field_name myFieldName
#else
#define FF_ROS_my_field_name my_field_name
#endif

So then you could write msg.FF_ROS_my_field_name when you want to use the field, and it would work under both ROS versions. Annoying, but practical. And when ROS1 support goes end-of-life, we could more or less do a search-and-replace to get rid of the FF_ROS_ prefix.


Missing alternate 'return' mnemonic in context evaluator in class CallDepthChangeInfo

In the embedded ContextEvaluator instance of class CallDepthChangeInfo the method evaluateContext(...) limits some changes to stackPurge to terminals using mnemonic 'ret'.  Shouldn't this also occur for those called 'retf'?

The code secction:
https://github.com/NationalSecurityAgency/ghidra/blob/7a30cefebb91ddb25a6c4030e67001202fd20936/Ghidra/Features/Base/src/main/java/ghidra/app/cmd/function/CallDepthChangeInfo.java#L526-L544

You are right, it should set the purge specially for RETF as well.


Created set_pos_msec in CVFile.

Moved the same logic in IkaLog.py to CVFile.

The goal is to enable to specify the actual start and end times to stat.ink. The current implementation sends the time of IkaLog.py worked, but sending the actual game time might be better.
The whole change to achieve it is here:
hiroyuki-komatsu@c686f85
Here's a sample result:
https://stat.ink/u/hirok_dev/1065469


support for ngx_wasm_module

NGINX has a new  ngx_wasm_module, which aims to implement proxy-wasm ABI.   I did try out coraza-proxy-wasm with the module and found that it doesn't work. here is an linked issue to track:  https://github.com/Kong/ngx_wasm_module/issues/454

Bump this, any new developments since upstream closed that issue?


Added Providers To Sidebar

Thanks for doing this!
Not sure why the build has failed with that error, I tested it locally and it's fine so merging it in (and will check it deploys okay).


Add new descriptions to IAssetLoader and IAssetManager

@Crisspl maybe merge it and correct what @AnastaZIuk got wrong/went about a really long way to describe obscurely.


Bluetooth improvements

Motivation for this change
More work on using upstream systemd units where possible. This also introduces new systemd unit option, aliases. You can use it to make several symlinks to one "main" service. It's needed for systemd activation of Bluez to properly work.
Also reintroduced Bluez 4. It wasn't really removed from nixpkgs, just unreferenced and unloved. It's still needed for KDE4 so I've restored it.
Things done

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

[x] NixOS
[ ] macOS
[ ] Linux

[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

BTW with this Bluetooth actually started to work properly for me -- before I had troubles with sending and receiving files.

Perhaps @edolstra would be interested to review aliases-for-systemd patch?

OTOH aliases change is small and hopefully okay, so waiting for @edolstra to find time to look may be excess (No grudge! I understand you're busy and don't want to add even more tasks to the tasklist ^_^). Bluetooth part seems good so I'll merge in few days unless someone objects.


Suggestion: new @provides param

Sometimes, there are methods, that should not be called by client code directly. Instead, they "provide" some property or a method.
For example, here's a Laravel model I'm trying to "properly" document:
/**
 * // Scopes
 * @method \Illuminate\Database\Eloquent\Builder active() Add "Account is active and not expired" scope to the query builder
 *
 * // Accessors
 * @property-read boolean $is_active Account is active and not expired
 */
class Account extends Model
{
    /**
     * Laravel Scope. Don't call in client code!
     * @ignore
     * @see \App\Account::active()
     */
    public function scopeActive($query)
    {
        return $query->where('active', true)
            ->where(function ($query) {
                $query->whereNull('expires_at')
                    ->orWhere('expires_at', '>=', date('Y-m-d', time()));
            });
    }

    /**
     * Laravel Accessor. Don't call in client code!
     * @ignore
     * @see \App\Account::$is_active
     */
    public function getIsActiveAttribute()
    {
        return $this->active && ! $this->is_expired;
    }
}

It would be of great help If I could use one of these syntaxes instead:
/**
 * // Scopes
 * @method \Illuminate\Database\Eloquent\Builder active() Add "Account is active and not expired" scope to the query builder
 *
 * // Accessors
 * @property-read boolean $is_active Account is active and not expired
 */
class Account extends Model
{
    /**
     * @provides \App\Account::active()
     */
    public function scopeActive($query)
    {
        return $query->where('active', true)
            ->where(function ($query) {
                $query->whereNull('expires_at')
                    ->orWhere('expires_at', '>=', date('Y-m-d', time()));
            });
    }

    /**
     * @provides \App\Account::$is_active
     */
    public function getIsActiveAttribute()
    {
        return $this->active && ! $this->is_expired;
    }
}

--OR-- shorter (or, "inline") form:
class Account extends Model
{
    /**
     * @provides \Illuminate\Database\Eloquent\Builder active() Add "Account is active and not expired" scope to the query builder
     */
    public function scopeActive($query)
    {
        return $query->where('active', true)
            ->where(function ($query) {
                $query->whereNull('expires_at')
                    ->orWhere('expires_at', '>=', date('Y-m-d', time()));
            });
    }

    /**
     * @provides boolean $is_active Account is active and not expired
     */
    public function getIsActiveAttribute()
    {
        return $this->active && ! $this->is_expired;
    }
}

Expected behavior for @provides:

Documentor doesn't document the method/property itself. Only the property it refers to..

Intellisense does not suggest such methods/properties outside the class itself (i.e., in client code). O, it suggests them, but marking as "providing", with the explanation on what this method provides.

I don't really get your suggestion. We do have a @method tag which is the way to go to define magic methods on a certain object.
Without any knowledge of laravel and its way to implement this, this feels like a lot of magic. Which is hidden by some obscure docblock to make your editor aware of the magic you are trying to do.
Beside that if we would add such a tag in phpdocumentor the editors wouldn't support it automatically.

The goal is to suggest/document $model->is_active, while not suggesting $model->getIsActiveAttribute(). Another goal: to simplify the "markup" (see the latest "inline" code snippet).

Beside that if we would add such a tag in phpdocumentor the editors wouldn't support it automatically.

I know, I know… But they definitely won't support anything that's not supported by phpdocumentor in the first place :-(

发自我的华为手机-------- 原始邮件 --------主题：[phpDocumentor/phpDocumentor2] Suggestion: new @provides param (#2087)发件人：Vladimir Mityukov 收件人：phpDocumentor/phpDocumentor2 抄送：Subscribed Sometimes, there are methods, that should not be called by client code directly. Instead, they "provide" some property or a method.
For example, here's a Laravel model I'm trying to "properly" document:
/**

// Accessors

@property-read boolean $is_active Account is active and not expired

// Scopes

@method \Illuminate\Database\Eloquent\Builder active() Add "Account is active and not expired" scope to the query builder
/
class Account extends Model
{
/*

Laravel Scope. Don't call in client code!
@ignore
@see \App\Account::active()
*/
public function scopeActive($query)
{
return $query->where('active', true)
->where(function ($query) {
$query->whereNull('expires_at')
->orWhere('expires_at', '>=', date('Y-m-d', time()));
});
}

/**

Laravel Accessor. Don't call in client code!
@ignore
@see \App\Account::$is_active
/
public function getIsActiveAttribute()
{
return $this->active && ! $this->is_expired;
}
}
It would be of great help If I could use one of these syntaxes instead:
/*

// Accessors

@property-read boolean $is_active Account is active and not expired

// Scopes

@method \Illuminate\Database\Eloquent\Builder active() Add "Account is active and not expired" scope to the query builder
/
class Account extends Model
{
/*

@provides \App\Account::active()
*/
public function scopeActive($query)
{
return $query->where('active', true)
->where(function ($query) {
$query->whereNull('expires_at')
->orWhere('expires_at', '>=', date('Y-m-d', time()));
});
}

/**

@provides \App\Account::$is_active
/
public function getIsActiveAttribute()
{
return $this->active && ! $this->is_expired;
}
}
--OR-- shorter (or, "inline") form:
class Account extends Model
{
/*
@provides \Illuminate\Database\Eloquent\Builder active() Add "Account is active and not expired" scope to the query builder
*/
public function scopeActive($query)
{
return $query->where('active', true)
->where(function ($query) {
$query->whereNull('expires_at')
->orWhere('expires_at', '>=', date('Y-m-d', time()));
});
}

/**

@provides boolean $is_active Account is active and not expired
\App\Account::active()
*/
public function getIsActiveAttribute()
{
return $this->active && ! $this->is_expired;
}
}
Expected behavior for @provides:

Documentor doesn't document the method/property itself. Only the property it refers to..
Intellisense does not suggest such methods/properties outside the class itself (i.e., in client code). O, it suggests them, but marking as "providing", with the explanation on what this method provides.
—You are receiving this because you are subscribed to this thread.Reply to this email directly, view it on GitHub, or mute the thread.


Radius-Size change button

is the any possible way to maximise the size of radius-size change button.Sometimes , While altering the radius ,the annotation is dragged and pointed to some other location.

@bharathi91  found any solution for radius size change button?


Fabula Ultima bugfix (sheet.json update to fix CSS)

Submission Checklist
Required

[X] The pull request title clearly contains the name of the sheet I am editing.
[X] The pull request title clearly states the type of change I am submitting (New Sheet/New Feature/Bugfix/etc.).
[X] The pull request makes changes to files in only one sub-folder.
[X] The pull request does not contain changes to any json files in the translations folder (translation.json is permitted)

New Sheet Details

The name of this game is: <   >  (i.e. Dungeons & Dragons 5th Edition, The Dresden Files RPG)

The publisher of this game is: <   > (i.e. Wizards of the Coast, Evil Hat)

The name of this game system/family is: <   > (i.e. Dungeons & Dragons, FATE)

[ ] I have followed the Character Sheets Standards when building this sheet.

[ ] This sheet has been made on behalf of, or by, the game's publisher.
[ ] This game is not a traditionally published game, but a copy of the game rules can be purchased/downloaded/found at: <   >
[ ] This sheet is for an unofficial fan game, modification to an existing game, or a homebrew system.

Changes / Description

Names in the sheet.json have been updated on the request of the devs.
CSS was not made in Legacy, so sheet.json have been updated to fix the error
Template has been added on Initiative roll

Character Sheet Info Roll20 Internal Use only.


Add liveness and readiness probes

Add liveness and readiness probes using the available URLs in the app and default values for thresholds and durations.

Looks good, thanks for the PR @sebastien-prudhomme!
/lgtm
/approve


Update Ziglua to support the latest commit of Zig master

Apparently Zig changed the behaviour of anonymous structs, so some of the tricks used to unify the addSharedLibrary and addStaticLibrary code will not work anymore.

Thank you for fixing this and keeping ziglua building on the latest Zig master


[SPARK-42581][CONNECT] Add SQLImplicits.

What changes were proposed in this pull request?
This PR adds the SQLImplicits class to Spark Connect. This makes it easier for end users to work with Connect Datasets.
The current implementation only contains the column conversions, we will add the encoder implicits in a follow-up.
Why are the changes needed?
API Parity.
Does this PR introduce any user-facing change?
Yes.
How was this patch tested?
I added a new test suite: SQLImplicitTestSuite.

Merging.


Connecting from another machine does not save session data

Connect from one machine to remote
Now connect from another machine
First machine gets

But that doesn't save the workspace. I'd expect my workspace remains available or I get prompt to reload RData

Cleaning up backlog


fix broken Python IO API docs

Description
Fixes #12854

This PR manually specifies members of the IO module so that the docs will render as expected. This is workaround in the docs to deal with a bug introduced in the Python code/structure since v1.3.0. See the comments for more info.

This PR also fixes another issue that may or may not be related. Cross references to same-named entities like name, shape, or type are confusing Sphinx and it seems to just link to whatever it last dealt with that has the same name, and not the current module. To fix this you have to be very specific. Don't use type, use np.type if that's what you want. Otherwise you might end up with mxnet.kvstore.KVStore.type. This is a known Sphinx issue, so it might be something we have to deal with for the time being.

I mapped these to aliases, so the docs still have a shorthand reference.
.. _name: mxnet.symbol.Symbol.name
.. _shape: mxnet.ndarray.NDArray.shape

So you will see me use name_ in the docstring, and that will link up to the _name alias for mxnet.symbol.Symbol.name that is defined at the end of the documentation page's rst code. This pattern is specified by restructured text syntax.
This is important for any future modules - that they recognize this issue and make efforts to map the params and other elements.
Checklist
Essentials
Please feel free to remove inapplicable items for your PR.

[x] Changes are complete (i.e. I finished coding on this PR)
[x] Code is well-documented
[x] To the my best knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

Preview
To see the APIs populated:
Go to the 1.3.0 docs: http://mxnet.incubator.apache.org/versions/1.3.0/api/python/io/io.html#data-iterators
Then switch to master. See how links are not there, and down in the API Reference none of those things are present.
Now go to my preview: http://<IP_ADDRESS>/versions/1.3.1/api/python/io/io.html
To see the parameter mapping:
It's broken on master and not even visible, but you can look at 1.3.0.
http://mxnet.incubator.apache.org/versions/1.3.0/api/python/io/io.html#mxnet.io.DataDesc.get_list
Note that the mappings pretty much work, but type seems messed up because I doubt it is intended to be from kvstore. Now look at my preview:
http://<IP_ADDRESS>/versions/1.3.1/api/python/io/io.html#mxnet.io.DataDesc.get_list
Comments
Changes that have come in since v1.3.0 have caused some havoc with Sphinx. This could be a bug in the Python code or maybe Sphinx needs things to be a certain way to function properly.

It can't distinguish between methods of the same name
It can't use automodule to fetch all members automatically
This means a lot of the docs are currently broken! I ask that some more people take a look because it could be a minor change in the Python versus having to go through and update every single bit of docs and doc strings in each module.

You can see in this PR what had to be done just for one module. Note the recordio hasn't been touched and Sphinx renders the docs just fine.
https://github.com/apache/incubator-mxnet/pull/12871/files#diff-4381272fd8fa032905b0785473077f5bL157
Follow up
There are 3 remaining docs build errors related to io.py:
/home/ubuntu/incubator-mxnet/python/mxnet/io/__init__.py:docstring of mxnet.io.NDArrayIter:5: WARNING: Title underline too short.

Example usage:
----------
/home/ubuntu/incubator-mxnet/python/mxnet/io/__init__.py:docstring of mxnet.io.NDArrayIter:5: SEVERE: Unexpected section title.

Example usage:
----------
/home/ubuntu/incubator-mxnet/docs/api/python/io/io.md:154: SEVERE: Duplicate ID: "module-mxnet.io".

I think that when folks work on the Python files and move them around like in subfolders like this, they must fix the docs prior to merging. That would have dealt with the first error WARNING and the second error SEVERE. As for the third error SEVERE, I think that the page structure of the docs must be changed to fix this. I tried a variety of workarounds like adding :noindex: but this just breaks the site. One solution would be to put these API outputs on separate pages. I'd like to eliminate all SEVERE errors so that we can put the docs build as part of CI, so that moving forward, people don't inadvertently break the docs with their PRs.

@anirudhacharya
@thomelane - this approach can probably fix #12829 LMK what you think... but also I'd like to know if there's not an easier way to fix what's going here...

@mxnet-label-bot [pr-awaiting-review, Doc]

@zhreshold can you please review this PR and merge it. Thanks


signup impossible with email address containing +

the received opt-in url gives 'Ungültiger Aktivierungslink' ('invalid activation link').
Happened today 11:51 CET

Ugh. My sincere apologies for the problem. It should work.
Would you please forward to me the email with the activation link, preferably as an attachment? Send it to dwheeler @ linuxfoundation . org or dwheeler @ dwheeler . com (I'm adding spaces to counter the spammers). Also, please let me know what the email address is in the email.

I need more information. I can't find this email address in the database. The activation link, or what the email address actually is, and/or the user id would all help me here.
Thanks!!

David, if you have a gmail account, you also have an infinite number of email addresses that include a "+". "+" introduces what is known as a "subaddress", so<EMAIL_ADDRESS>is a perfectly valid email address, but is delivered to the<EMAIL_ADDRESS>account's mailbox.

@TonyLHansen : I know that, but that shouldn't matter. To verify an email address, we just send the verification email to whatever email was claimed. If it's delivered, and the person selects it, it proves that the user controls that email address. I'ts true that<EMAIL_ADDRESS>will be delivered to<EMAIL_ADDRESS>on gmail, but that should be just fine.
My guess is that we're not properly escaping "+" somewhere. But I need the email address to check on it.

I'll follow up in 14h.

I did a test using a + subaddress on gmail using the staging platform, and the active email looked like this:
Hello,
Welcome to the Badging Program! Click on the link below to activate your account:
Activate
where "Activate" had this link:
https://staging.bestpractices.coreinfrastructure.org/account_activations/uDoKxXa8isIRnGSLYx_YSw/edit?email=xyz%2Bstaging%40gmail.com
(I changed my id to "xyz".)
The %2B is the representation of the "+" in the email address, and it definitely worked when I clicked the link.
So I could not reproduce the reported issue.

@TonyLHansen - thank you so much for testing this.
I want to fix problems, but I have to know what the problem is :-).

I just could log in with the back then created user that gave the error. I try a new one to confirm or cancel this issue here…

worked now with https://bestpractices.coreinfrastructure.org/account_activations/VxBMUntFQJBFmkB1DzMZjg/edit?email=me%2Bissue-1626%40mro.name

That's a really hostile, being blocked from login and not told for how long:

Leider können Sie sich noch nicht anmelden. Als Anti-Spam-Maßnahme müssen Sie nach der Aktivierung einige Zeit warten, bevor Sie sich anmelden können.

It's the hostility the spammers deserve applied to all – the light users also.

We certainly only want to be hostile to confirmed spammers. I'm not sure what the issue was here.

https://www.deepl.com/translator#de/en/Leider können Sie sich noch nicht anmelden. Als Anti-Spam-Maßnahme müssen Sie nach der Aktivierung einige Zeit warten%2C bevor Sie sich anmelden können.

a delay between clicking the activation link and 1st login – didn't work within the first 15 minutes. Am not talking about the Microsoft login, naturally.


Failed to upload

fixed this

08050c14607f2a20: Failed to upload - /app/downloads)/6be8095e-f5c9-4b1f-9bc7-4a70fcbb98f5/videoplayback: Uploaded and got invalid id for file videoplayback

Check if any of the possible solutions in #70 helps

THANKS FOR REPLYING !
No, I checked all issues but did not get the solution !

6ea9c0e287587185: Started. Dir: 34b9766d-cef6-45ad-8050-3fc5bb030d38.
6ea9c0e287587185: Completed. Filename: index.html. Starting upload.
Got file id null
6ea9c0e287587185: Failed to upload - /sdcard/downloads/dir/34b9766d-cef6-45ad-8050-3fc5bb030d38/index.html: Uploaded and got invalid id for file index.html
cleanup: Deleted 34b9766d-cef6-45ad-8050-3fc5bb030d38```

@out386 Help Please bro what's the solution?

Yes. faced the same issue. Was pulling my hair for like 2-3 hours. Then finally get it worked.
You see, files get uploaded but msg error. After this error, try /list boys and see it will show results of the same upload with embedded TD link.
So basically this error is because In your TD, outside sharing is disabled. So files get uploaded but bot faces errors while generating shareable links and thus this error msg
I enabled outside sharing in my TD and it worked fine afterwards.
Hope it helps :)


0.4 release

Feels like it's about time again. Improvements since last time #144 are significant enough to warrant a new release.
Hissp has mostly stabilized. I rarely need to touch the .py files in the Hissp package proper. The bundled macros have had some recent volatility, but #154 and the associated wiki page has helped me to select and implement a set balanced between minimalism and utility.
Most of the recent volatility has been in the docs. Rather than adding anything new right now, I want what's already there to be as accurate as possible before the release, which means a lot of proofreading. That gets to be tedious, so it's taking time.
I'm not totally satisfied with how reader macros handle extras, but don't have a better idea right now. The release will have to happen before any deeper changes there. I might want to address some of the parsing quirks #149 though, at least where I have a clear idea of how it should work.
I don't think the next release can be the 1.0, although it feels like that's getting close now. Maybe the one after that. I may need to write some bigger applications in Hissp 0.4 to see where the pain points are. This would, of course, take time. More examples from the community would also be helpful here.

Diataxis has influenced my thinking about writing docs. I'm renaming some things. The tutorial is now the primer. I'm moving a lot of the Whirlwind Tour examples to the API docs where possible. Should be the last quarter or so. That means putting them in the source docstrings, which will have to get longer. The end of the Tour will then refer to those, perhaps using Python's help() builtin. Changing context like that isn't trivial. Parts may have to be rewritten/reformatted. It will take time.
I think at least some of the macro tutorial should be in a "cookbook" section (with the remainder perhaps renamed "macro primer"), along with some ideas from the old FAQ and the wiki, although I wonder if some of that wouldn't be a better fit for the discussions here on GitHub. Discussions are easier to get started, but harder to maintain as the language evolves. Probably outdated entries there will be marked outdated and abandoned rather than fixed. Maybe short ones start out in discussions, and important longer ones get moved to the cookbook.

I feel like I should have released months ago, but the docs were not ready. I think I'm at the feature-freeze point and won't add anything besides fixing bugs before the release. This goes for docs as well, which (hopefully) is about all that's left. I'll scan for and correct errors, but I'm not going to add things or do any major rewrites. I might be able to get it done this weekend, but surprises happen.

Didn't happen, but made good progress on docs. Easily another day or two there, and another one (at least) for final release checks, assuming no surprises.

Oh, we're getting close now. One more parsing quirk popped up. Once I fix that, I should be ready to start on the release branch. That will mainly correct version references, which will not remain on master, although I will cherry-pick any permanent changes if needed. I also remember that deploying to PyPI was a pain. There's just no forgiveness for any missteps, so I have to check everything very, very carefully. Hopefully I took detailed enough notes last time.

OK, I've hit all the milestone tasks but this one, i.e., the release branch and the release itself. Maybe I can get 0.4.0 out tonight.

Released for realsies on PyPI, no takebacks no refunds. Based on directions from #144. No obvious problems. Did test PyPI first and found a broken link in the README.

Also released on GitHub. And I kept the fixes from the RC branch: #235 .
It is done.


(Fix) Whitelist per tier && Display whitelist in Dutch Auction

Closes #812
Closes #906

Whitelist as a property of tier in deployment step
Display whitelists in Dutch Auction
Fix in the display of transactions window when whitelist is enabled for some tier

@dennis00010011b please take a look at e2e tests for this PR. I have changed the location of "whitelist enabled" radio input. It is the property of a tier now.


cloud_firestore: prevent crash DocumentSnapshot is null

Apps will crash if a FirebaseFirestoreException happened (e.g. if user logged out during request) because the plugin still want's to access the DocumentSnapshot:
E/AndroidRuntime(24141): java.lang.NullPointerException: Attempt to invoke virtual method 'boolean com.google.firebase.firestore.DocumentSnapshot.exists()' on a null object reference
E/AndroidRuntime(24141): 	at io.flutter.plugins.firebase.cloudfirestore.CloudFirestorePlugin$DocumentObserver.onEvent(CloudFirestorePlugin.java:199)
E/AndroidRuntime(24141): 	at io.flutter.plugins.firebase.cloudfirestore.CloudFirestorePlugin$DocumentObserver.onEvent(CloudFirestorePlugin.java:188)

I signed it!
Am 6. Mai 2018 um 14:29:06, googlebot<EMAIL_ADDRESS>schrieb:
Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).
📝 Please visit https://cla.developers.google.com/ to sign.
Once you've signed (or fixed any issues), please reply here (e.g. I signed it!) and we'll verify it.
What to do if you already signed the CLA
Individual signers
It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.
Corporate signers
Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.


plex-media-player: <IP_ADDRESS>8 -> <IP_ADDRESS>7

Motivation for this change
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"
[x] 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)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Notify maintainers
cc @kylewlacy

@GrahamcOfBorg build plex-media-player


Check of CSIRO tests

I am reviewing the CSIRO coded tests to see if we have everything covered. I'm making note here of things I need to check.
Missing (or maybe not explicit in the existing tests):
Spike test: spikes greater than 1degC are identified and in original tests, interpolated
Statistical screening tests: these should be implemented after the initial QC tests. When checking new data, it is compared to datasets that are accepted as good, ie, qc'd. How can these tests be benchmarked? I'm not sure if it can be done, as it is part of a process that may not apply to this exercise.
Quota_Paper.pdf

Closing as no longer relevant.


Updated P2P certificate section

After talking to Dev Reg SMEs and PG got clarification that User P2P cert is not persistent and is valid for 1 hour instead of 24 hours like the Device one.

@secherka : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@MicrosoftGuyJFlo
Can you review the proposed changes? IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#sign-off

Resolves https://github.com/MicrosoftDocs/azure-docs/pull/93201


Create a gmsh_io.get_bounding_box function to be used in STEM

Connected to https://github.com/StemVibrations/STEM/issues/245


Move benchmarks config to icc-only - [merged]

In GitLab by @perarnau on Jul 26, 2018, 09:15
Merges icc-benchs -> master
Since we only want to test those benchmarks on KNL+icc, let's just do that.
Also changes the knl CI to compile with icc.

In GitLab by @perarnau on Jul 26, 2018, 09:26
merged
By Swann Perarnau on 2018-07-26T14:26:35 (imported from GitLab project)

In GitLab by @perarnau on Jul 26, 2018, 09:16
added 1 commit
d56842d9 - [refactor] Move benchmarks to icc+mkl
Compare with previous version
By Swann Perarnau on 2018-07-26T14:16:22 (imported from GitLab project)

In GitLab by @perarnau on Jul 26, 2018, 09:19
enabled an automatic merge when the pipeline for d56842d98625d06f8779d609cd0643e2fca81114 succeeds
By Swann Perarnau on 2018-07-26T14:19:47 (imported from GitLab project)


How to setup dynamic Alert manager in prometheus ??

Hi Team,
I have installed kube-prometheus-stack for monitoring k8s . But In the Alert manager I configured smtp for sending mails its working fine and sending emails also . But I am unable to send alerts in dynamic way in alert manager.
Dynamic alert means
reference: https://www.robustperception.io/using-labels-to-direct-email-notifications
I'm going to presume you already have a working email notification setup, such as was shown previously with Gmail.
We start at Prometheus. We'll need to get the target email address into an alert label. Let's say you have constructed time series looking like:
mymetric{job="myjob",email_to="foo@example.org",instance="host1"}
mymetric{job="myjob",email_to="bar@example.org",instance="host2"}
Then you can write an alert which propagates this email_to label such as:
groups:
name: test.rules
rules:
alert: MyAlert
expr: mymetric > 1
route:
group_by: [email_to]
receiver: email_router
receivers:
name: email_router
email_configs:
to: "{{ .GroupLabels.email_to }}"
from: XXXXXXX
Add whatever other settings you need to talk to your SMTP server
headers:
subject: "You have {{ .Alerts.Firing | len }} firing alerts"
html: |
Hi {{ .GroupLabels.email_to }},
You have the following firing alerts:
{{ range .Alerts }}
{{.Labels.alertname}} on {{ .Labels.instance }}
{{ end }}

please suggest me how can I achieve this in kube-prometheus-stack ??

This seems a configuration question about alertmanager. Does it relate to kube-prometheus?


feat(cli): add update command

Summary
Related Issue

https://github.com/web-infra-dev/rspress/issues/509
Checklist

[x] I have added changeset via pnpm run change.
[x] I have updated the documentation.
[ ] I have added tests to cover my changes.

Awesome!


Support local custom plugin

Is there no other more convenient way except for submitting the code to the Knip repository to create a new plugin (which may be very time-consuming)?
It would be convenient if knip could support local plugins like:
// knip.config.js
{
  "my-plugin": {
      title:xxx,
      enablers: xxx,
      isEnabled: xxx,
      config:xxx,
      resolveConfig: xxx
  },
}

Unfortunately, there is not. Sorry to hear building new plugins for Knip is time-consuming for you. Supporting this means it'll be more time-consuming for me, and I currently don't fancy this idea.

An use case: I have a few private libraries which are used across my work and would be great to have a way to add a local plugin to it. Currently the workaround is to either ignore files or add a @public comment