Consider using Bun for development.

https://bun.sh/guides/ecosystem/sveltekit
I'm curious if the package.lock file equivalent is more readable. That is one thing I think pnpm does that interests me.

More info on the lockfile: https://bun.sh/docs/install/lockfile

I'm going to keep this open for now, but I think as I start to stand up the SvelteKit side of things, I will probably keep using node but may try pnpm to get a diff-able lock file.
https://pnpm.io/


Two planets have the wrong names

Using this map as an example: https://conclave.mistake-not.net/#WyJeICIsIn46diIsMSwifjp0IiwiMTggNzggMjkgNDYgMzggNDggNjUgMjMgNDcgNDIgMjEgNDkgNzMgMzAgMzkgNjQgMzcgMzYgNjcgMjQgNzAgNjEgUDIgMzEgMzQgUDMgMzUgNDQgUDQgNzcgNjYgNjAgUDUgODAgNzYgMjIgUDEiXQ==
System tile 61 at coordinates 2, 1, -3 is mislabelled as containing the planet "Perimeter" in the bottom right of the screen while hovering:

Looking at the tile image, this planet should be called Ang. This is also the case for system tile 73, where Cealdri is misidentified as Lisis.

Thanks - incidentally, do you have some brief notes on how to run a local copy of this? I'm interested in adding another couple of bits and pieces if I find the time.

Sure I can write some up. Are you familiar with clojure or clojurescript at all? What would you be thinking of adding?

I'm afraid I'm totally new to the Clojue ecosystem, though snooping around your other repos I've found your Codenames project, which does seem to include some documentation. If that's relevant to Conclave, I can give that a shot?
Because of the number of friends I have, I usually play 5 player games, so was hoping to add in definitions for the 5-player notch and flat maps:

Looking at your definitions in data/layouts.cljc, though, it looks like it'd be fairly straightforward to add them. The layouts are available on other map generators, but Derek Peterson's generator doesn't support PoK, while  Keeganw's tends to produce fairly unbalanced notch maps - I often find that the players on the "horns" only have one "safe" planet next to their home system, while the other players have three solid, immediately useful systems to start colonising. I'm hoping that your balancing algorithm will do a better job!

Sorry for the late response, busy weekend!
Cool you want to add those maps! Adding new layouts was one of the things I was aiming at when I wrote the app, so it should just be a matter of adding to layouts.cljc. I also wrote the balancing algorithm to be as layout-agnostic as possible, so hopefully it'll give you decent results - can't promise that obviously, but if you do notice problems/persistent biases please let me know.
I'm gonna write up a quick readme for it now. The instructions you mention for the codenames app are basically just gesturing at other people's documentation, so I reckon they could be tough to follow.

Added a readme just now,  hopefully it's clear, let me know what you think!


[Feature][plugin] Datax can submit to YARN

close https://github.com/apache/dolphinscheduler/issues/11488
Instructions:
Configure the environment variables DATAX_ON_YARN_JAR and YARN_BIN to run DATAX ON YARN
Parameter explanation:
DATAX_ON_YARN_JAR:
https://github.com/duhanmin/datax-on-yarn Compile and package
YARN_BIN:
The default value is yarn, which is used to limit the memory of yarn submission to the client
DATAX_HOME:
datax decompression directory, or s3/hdfs compression package directory
DATAX_HOME=/Users/duhanmin/IdeaProjects/daima/DataX/target/datax/datax
YARN_BIN=HADOOP_OPTS="-Xms32m -Xmx128m" /usr/bin/yarn
DATAX_ON_YARN_JAR=/opt/soft/datax/datax-on-yarn-1.0.0.jar

Codecov Report

Merging #13939 (2b2590b) into dev (bae8df6) will decrease coverage by 0.07%.
The diff coverage is 21.19%.

:exclamation: Current head 2b2590b differs from pull request most recent head 2704370. Consider uploading reports for the commit 2704370 to get more accurate results

@@             Coverage Diff              @@
##                dev   #13939      +/-   ##
============================================
- Coverage     38.87%   38.81%   -0.07%
+ Complexity     4461     4454       -7
============================================
  Files          1158     1158
  Lines         42429    42459      +30
  Branches       4772     4767       -5
============================================
- Hits          16496    16479      -17
- Misses        24118    24158      +40
- Partials       1815     1822       +7

Impacted Files
Coverage Δ

...inscheduler/alert/registry/AlertHeartbeatTask.java
0.00% <0.00%> (ø)

...nscheduler/api/controller/ResourcesController.java
53.70% <0.00%> (-1.02%)
:arrow_down:

...api/service/impl/ProcessDefinitionServiceImpl.java
35.07% <0.00%> (-0.03%)
:arrow_down:

...inscheduler/server/master/config/MasterConfig.java
1.88% <0.00%> (-0.08%)
:arrow_down:

...eduler/server/master/task/MasterHeartBeatTask.java
4.34% <0.00%> (+0.34%)
:arrow_up:

...pache/dolphinscheduler/spi/enums/ResourceType.java
0.00% <0.00%> (ø)

...heduler/plugin/storage/gcs/GcsStorageOperator.java
35.24% <0.00%> (-0.16%)
:arrow_down:

...heduler/plugin/storage/oss/OssStorageOperator.java
35.34% <0.00%> (-0.15%)
:arrow_down:

...scheduler/plugin/storage/s3/S3StorageOperator.java
33.07% <0.00%> (ø)

...duler/plugin/task/api/AbstractCommandExecutor.java
0.00% <0.00%> (ø)

... and 13 more

... and 27 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Add MarkovChainSequenceGenerator

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 100.00%. Comparing base (6fa3c5a) to head (15a5733).

Additional details and impacted files
@@            Coverage Diff            @@
##              main      #405   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files          113       114    +1
  Lines         3545      3568   +23
  Branches       258       260    +2
=========================================
+ Hits          3545      3568   +23

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


更改样式增加了头像

Codecov Report

Merging #30 into dev will increase coverage by 0.13%.
The diff coverage is 16.66%.

@@            Coverage Diff             @@
##              dev      #30      +/-   ##
==========================================
+ Coverage   11.98%   12.11%   +0.13%
==========================================
  Files          30       30
  Lines         484      487       +3
  Branches       59       60       +1
==========================================
+ Hits           58       59       +1
- Misses        426      428       +2

Impacted Files
Coverage Δ

src/components/Content/index.tsx
0% <0%> (ø)
:arrow_up:

src/components/IndexContent/index.tsx
0% <0%> (ø)
:arrow_up:

src/components/Partner/index.tsx
0% <0%> (ø)
:arrow_up:

src/components/RoundImage/index.tsx
0% <0%> (ø)
:arrow_up:

src/config/index.ts
90% <100%> (+1.11%)
:arrow_up:

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 f2919b8...a7ca2ce. Read the comment docs.


[Core] Prevent infinite recursion when printing errors

Supersedes: https://github.com/godotengine/godot/pull/85137

Thank you!

Cherry-picked for 4.2.1.

Cherry-picked for 4.1.4.


Census Docker build fails

Describe the bug
I want to reproduce a local Census instance with private data. I'm following the steps of creating a new release (https://github.com/chanzuckerberg/cellxgene-census/tree/main/tools/cellxgene_census_builder). Nonetheless, I'm stuck at the point of building a Docker image.
To Reproduce
Working on main commit 281ffdf53cb1c68a4017fbe40100cef3f759ec05
./cellxgene-census/tools/cellxgene_census_builder/
make image

Added console logging (include error) in console.log
Expected behavior
Successful docker image build :)
Environment

macOS Monterey
Apple M1

Software versions:

Docker desktop 4.17.0

Additional context
Would it ever be possible to reproduce Census platform within my own environment (following the data schema's as suggested) from a utilities and platform perspective? For now I downloaded some h5ad's directly from the Census S3 to make sure I can reproduce the platform as such, independent of h5ad formatting. Much appreciated!

Thanks for raising this @MatthiasBeyens. I will get back to you on this shortly.

Hi @MatthiasBeyens apologies for the delay we have a few conversations internally about this and we have made the decision to not support the builder code for external use. However we are interested in learning about why you wish to build a Census of you own as we may be able to point you in the right direction to accomplish your goals.
For example we or our partners at TileDB may be able to offer you support to use TileDB-SOMA for your ends (which is what the Census utilizes)


Update velocity, 1.2.2 > 1.2.3 || 1.4.2

Although 1.4.2 would be better, even the 1.2.3 release has a useful new method, called finishAll.
According to https://github.com/Dogfalo/materialize/pull/2252 , 1.2.3 should already be there, but I guess it has been rolled back some day.

Refering to this line:
https://github.com/julianshapiro/velocity/blob/1.2.3/velocity.js#L2077

Pull requests are always welcome

Updated to 1.4.2 in v1-dev


Add vulnerability scanner as Cron task

https://github.com/GeoscienceAustralia/dea-sandbox/commit/a1068ecabe790cff118a4fe84b861c41fa0bed12#diff-f606a50abc4d0674f87194646274af3f removed in main CI pipeline vulnerability scanner. Add back as scheduled task.

Hey @Kirill888 can you please remind me why the vulnerability scanner was removed from CI?

Hey @Kirill888 can you please remind me why the vulnerability scanner was removed from CI?

I believe the CVE signature server is flaky ( since it is free) and sometimes times out. We can keep it and mark this step and continue on failure. There seems to be want for something like that as a feature in GHA : https://github.community/t/continue-on-error-allow-failure-ui-indication/16773


Addison

Adding a method to send an observation to fhir. Returns 201 if successful or the error message from fhir.
The method expects an integer value of the number of minutes the user exercised and a user object with an attribute id. The id should correspond to the id of the patient in fhir.

So much for not knowing Python!


Make code build on nightly

Though with a lot of warnings.  All tests pass and benchmarks run.

Thanks! Any reason you didn't do use std::old_io as io to minimize changes?

No strong reason.  It'd minimize the changes, but there isn't much of a point in leaving them as io:: since whatever replaces the io module will likely be rather different anyway.  It wasn't any real effort to rename all occurrences of io:: to old_io::

Thanks!


[colab] Fix setup script link.

Using the http link seems to produce the following error sometimes:

Using the httpS link is more reliable and should always work.

Thanks, change has already been pushed!


impl function blink.indent.{enable,disable,toggle}

Closes #3.
This provides three clear API functions:

blink.indent.enable
blink.indent.disable
blink.indent.toggle

Each function returns a boolean indicating either the success of the operation (for enable/disable) or the new state (for toggle). This allows plugin users to write conditional logic based on the operation's outcome.
Summary of changes, by file:
lua/blink/indent/config.lua

add visibility state

lua/blink/indent/init.lua

make decoration provider respect visibility state
clear all indent markers when disabling

This looks great, thank you! I'm surprised you found this repo :smile: Out of curiosity, what do you prefer about blink.indent over indent-blankline.nvim?

Really insightful, and that rainbow-delimiters replacement is a great idea. I've also spent far too much time trying to make it quick. If you're feeling adventurous, I threw something together: https://github.com/Saghen/blink.nvim/tree/main/readmes/delimiters
I'll slowly add more languages and markdown injected languages support, but if you end up giving it a shot, adding new languages is quite easy: https://github.com/Saghen/blink.nvim/tree/main/lua/blink/delimiters/langs


Assets modifications detection for typst watch

Description
When doing typst watch on a typst document that includes images via #figure, typst actually doesn't recompile the document when the included image is modified.
A simple test to notice this is to create a simple Typst document with a #figure(image("...") and to typst watch it. You will notice that when modifying the image file, typst won't recompile the document.
It would be in my opinion a great feature to get typst recompiling the document when one of its included asset is modified.
Use Case
Watching assets with typst watch would be, I believe, a good enhancement for the global Typst experience.

I'm on Archlinux. Here's the typst --version output:
typst 0.8.0 (360cc9b9)

I installed it via pacman repository, and it says my typst is up-to-date.

I cannot reproduce this on typst 0.8.0 (360cc9b9) installed using pacman on 6.5.7-arch1-1.
When I run /usr/bin/typst watch main.typ with a given file and run touch image.jpg to update its access time, it recompiles.

Well, I maybe made an mistake when I assumed typst watch was the problem, I encounter this problem with the Typst extension for Visual Studio Code. I did a small recording of what happens and uploaded it here. Note that when the image change it's because I force-saved the .typ file.

The Typst LSP extension isn't official. You can report bugs about it here: https://github.com/nvarner/typst-lsp

Sorry to have made you losing your time, will be more careful next time.

No worries.


'highland' object is no longer added to the global scope in the browser.

adding <script src="https://cdn.rawgit.com/caolan/highland/master/dist/highland.js" type="text/javascript"></script> doesn't seem to add the highand object to the global scope any more, where as <script src="https://cdn.rawgit.com/caolan/highland/2.5.1/dist/highland.js" type="text/javascript"></script> does

That's possibly related to our recent upgrade of Browserify. I'll take a look.

Should there be a minified version of the code in dist too?

@svozza I don't think we've ever provided a minified dist.

Yeah, that's what I thought but should we add one? Won't be much effort, I can do it now...

Hmmm, slight problem. How can I run the unit tests against the minified code? If I try to run them against dist/highland.js on its own - never mind the minified version of that file - they fail.

Oh, yes. Adding a minified highland.js would be great.
Running browser tests: https://github.com/caolan/highland/blob/master/Contributing.md#running-the-tests
I don't see any errors. You have to make sure to rebuild test/bundle.js though. The version that comes with the repo is never updated.

Yeah, that runs fine but technically we're not testing dist/highland.js with those tests (there's a TODO in browser.html about fixing this). I tried to get something working using rewireify but no luck. I guess it doesn't matter that much because Browserifying the unit tests is close enough in the dist/highland.js case but I'd be less confident about the minified version of the code.


Update sbt to 1.5.0

Updates org.scala-sbt:sbt from 1.4.9 to 1.5.0.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scala-sbt", artifactId = "sbt" } ]

labels: library-update, semver-minor

Codecov Report

Merging #1710 (3b9a8be) into master (ffc6476) will decrease coverage by 0.18%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1710      +/-   ##
==========================================
- Coverage   87.08%   86.90%   -0.19%
==========================================
  Files          59       58       -1
  Lines        2392     2382      -10
  Branches      136      142       +6
==========================================
- Hits         2083     2070      -13
- Misses        309      312       +3

Impacted Files
Coverage Δ

...re/shared/src/main/scala/io/circe/KeyDecoder.scala
97.29% <0.00%> (-2.71%)
:arrow_down:

...rc/main/scala/io/circe/numbers/BiggerDecimal.scala
86.54% <0.00%> (-2.34%)
:arrow_down:

...core/shared/src/main/scala/io/circe/CursorOp.scala
54.16% <0.00%> (-1.39%)
:arrow_down:

...es/core/shared/src/main/scala/io/circe/Error.scala
62.06% <0.00%> (-0.44%)
:arrow_down:

.../core/shared/src/main/scala/io/circe/Decoder.scala
85.82% <0.00%> (-0.31%)
:arrow_down:

...nter/src/main/scala/io/circe/pointer/Pointer.scala
89.34% <0.00%> (-0.13%)
:arrow_down:

...in/scala/io/circe/pointer/PointerSyntaxError.scala

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 ffc6476...3b9a8be. Read the comment docs.


Allow partial parse for SamplingOpts

As mentioned in comments for PR #124
Currently we insist on a full parse for a SamplingOpts object to be considered successfully deserialized. Going forward it will likely be more resilient and flexible to populate any missing values with defaults instead.

In particular, this issue should be considered a blocker for adding any new entries to SamplingOptions. Before that point, it's just a "nice to have"


Listeners don't work on Web

Session events are not coming if I use mobile linking in Web App.
Web doesn't support websocket in background. Is there any workaround?

I don't see to have any problems on my web dapp example: https://sooq.art.
Can you elaborate a bit more? Is this only on ios? (there's a lot of background restrictions issues over there)

Yes, this happens on iOS only, mostly issue in Safari. Chrome works time to time.
So when you open wallet and confirm signature it send response back, and if it happens when browser in background, when you return to browser the response from wallet never comes. Works on android app and web

We also have been seeing a similar issue on web in iOS Safari, with iOS Chrome working sometimes!
In the case of iOS Safari, following instructions such as these have worked to keep the WebSocket connection open. But of course this is only a workaround for now.
It seems the issue starts with iOS 15 and up. A different device I have tried on with iOS 12 works fine without changing any default settings.


[Makefile] Fix docker documentation install and generation

The final versions of the documentation has been shifted from docs/ to
docs/build/man. Most of the Makefile has been changed accordingly, but
the docker documentation generation was not.
Introduced by #4354
Signed-off-by: Morten Linderud<EMAIL_ADDRESS>

Seems like there was some sections forgotten while doing the restructure. Unsure if this is everything or if there are more stuff missing from #4354

/ok-to-test

The changes look reasonable to me, but I'd like @baude to weigh in.

/approve

LGTM

I'll add an official LGTM as @baude is hip with these changes.

Thanks @Foxboron
/lgtm

Should be noted that make install.docker is currently broken in the 1.6.3 release.

Why wasn't this included in 1.6.4? make install.docker is still broken.

1.6.4 is a backports-only long term support release. The next proper mainline release will be 1.7.0 - the first RC is out, the final tag should be pushed later today or tomorrow.

(The timing here worked out to be very confusing - sorry for that. Ideally 1.7.0 final would be out before we did a backports release for 1.6.x)

I don't quite see how this patch would be excluded from backports. But that means make install.docker is not expected to work on the LTS release?

Right now, we're only adding critical-severity bugfixes. We should do a better job of marking these releases, though, we don't intend on them being consumed by most distros. The intention was to get 1.7.0 out soon enough that most people would go straight from 1.6.3 to 1.7.0.

Ack. I'll just not bother with 1.6.4 then :) Thanks for the explanation!


⚠ Spryr has degraded performance

In d642636, Spryr (https://spryr.com) experienced degraded performance:

HTTP code: 200
Response time: 3942 ms

Resolved: Spryr performance has improved in eb299bb after 10 minutes.


Blank page when i try to open index.html

i tried the minting dapp and did everything like the tutorial and when i tried to build and open the index.html the page opens blank without the dapp itself, someone pls help

If anyone knows this, help would be great.  I get the same.  All the steps, then nothing shows.  Works locally just great, but once I try to get it up on github, the page is blank.  I even had the hashlips readme page show as the front page.  Then when I dump all the files from build into that folder, the page is blank.  Source code shows it's all there, but no page.

I have the same issue. Sucks. Can't deploy.

Same here...

you have to launch from terminal using npm run start but only after you've built it... that's what he does in the video tutorial

If you try open the index file you can't see your website. We can say index is a template. You should open with npm start command in terminal. This is how the React works.

Hey guys, I've just found a solution.
The dapp only works when all the files are in the root. However, you can move the index.html file to another folder and leave the configuration files in their place.
You just have to change the access to the html file by modifying the file: asset-manifest.json and change the path of index.html


Do not forget message to ack if we send out "just" a Standalone ack

When we send out a Standalone Ack because of a Duplicate (or close) we should not "forget" the message which is still in transit and waits to be acked officially, so not clear it.

Ok, was produce weird side effects ,... need to dig deeper

I open again ... the issues came because Alexa did strange things and tried to commission the device from two echo devices in parallel but then stopped responding on one of em, so in fact errors I saw in log were correct. i will test further but it still seems to be right


Support for parsing scientific notation.

Hey there,
So i hit upon a bug in my API recently, where i'm accepting values of money using symfony's MoneyType.
Now, during some testing i managed to trigger an error in Money by submiting a large value to my API, specifically:
Uncaught PHP Exception InvalidArgumentException:
"Invalid fractional part 0E+17. Invalid digit E found" at /.../vendor/moneyphp/money/src/Number.php line 219

What is happing here is:

I submit a value of<PHONE_NUMBER>000000 to my API.
That is transformed to a float 1.0E+15 by NumberToLocalizedStringTransformer (and then 1.0E+17 by MoneyToLocalizedStringTransformer.
1.0E+17 is given to the Money constructor, and fails in Number as above.

So the questions are:

Does anyone know how I can get this number though symfony forms without being converted to float in scientific notation.
Can Number add support for scientific notation?

Cheers

How about we convert the float back to a string with sprintf?
https://3v4l.org/H0FVj

I guess you can try to parse value from symfony object before you put it to money.
https://github.com/moneyphp/money/issues/406#issuecomment-332131006

I have fixed it in my forms MoneyTransformer at the moment:
return new Money(\sprintf('%.0f', $value['amount']), new Currency($value['currency']));

I've just noticed Number::fromFloat, so my Money is now constructed as
return new Money(Number::fromFloat($value['amount']), new Currency($value['currency']));
This can probably be closed.


LocalizedDateTimeField DeprecationWarning

Just making note of this deprecation warning under Django 1.3
python2.7/site-packages/timezones/fields.py:55: DeprecationWarning: A Field class whose get_db_prep_save method hasn't been updated to take a connection argument.
class LocalizedDateTimeField(models.DateTimeField):

I'm hitting this issue too. Running Django 1.3.1. Any updates?

Sorry, updated the requirement spec to include 0.2dev2. This fixed the issues. Cheers Brian.


Rewrite README with a clear overview of what the cookiecutter does and how to get started.

Rewrite the README to include:

A high-level overview of the project
Architecture of a target project
Concise usage instructions and what options are available

Remove the list of Python packages.

I wouldn't mind taking that one on.
I would use section titles as questions such as "What is the architecture?" and HowTo such as "How to set up your local environment for development".
I find that these help create focus and clarify the purpose of the section for both the writer and the reader.
Example in Beck's README

Oh also, what about the use of emojis for section titles?
I find them quite helpful when scrolling through a large single-page README.

Since I logged this ticket, I have already made a few updates to the README:

https://github.com/sixfeetup/scaf/pull/158/files#diff-b335630551682c19a781afebcf4d07bf978fb1f8ac04c6bf87428ed5106870f5
https://github.com/sixfeetup/scaf/pull/158/files#diff-a3114d707f7bb6efd153cfbe0266a64148252b8f82a443312b214c34a4b99f42

Note that the README for Scaf differs from the README for the generated project.
There is a PR of an architecture diagram, but it is outdated now:
https://github.com/sixfeetup/scaf/pull/126/files
I think we can close this issue and re-open more specific issues for updates to the README since the Scaf README provides a workable general overview, and the instructions for the generated project are mostly accurate.


Update Install.sh Script to support Fedora Release 23

Current tools/install.sh script currently only supports Fedora Release 21-22. Need to update script to support Fedora 23, and run test cases.

Pull Request #58 will correct this issue. Fedora Releases supported now will be 22-23 as Fedora 21 has reached end-of-life.

Pull Request #58 landed thank you @zeroSteiner.


Rudimentary implementation of "uptime" filter

Per #366 - supports:

uptime: > xxx
uptime: < yyy
uptime: between xxx and yyy
uptime: xxx-yyy

Uptime is in hours, and is only really applicable for EC2 instances.  For RDS instances, it currently uses the "time since create", since that's all that's available.

This isn't going to work. Sure, if you add an "uptime>1" requirement to a filter, it won't match until the resource has been up for an hour, but it also won't match when it's stopped (so the resource won't get started).

OK, so if the "uptime" filter returns True if the resource is anything but "running", and only in that state compares the actual uptime to the configured value.  This would mean that, when stopped (or starting) the filter continues to match.


Annotate assorted sqlalchemy.orm.query.Query methods

Adds annotations to the following Query methods:

filter
filter_by
order_by
offset
all
first
one_or_none
one
count

Ahh, this is a bit more crude than #81. Maybe we want that instead? I handwave a bit about return values being Query instead of a potentially overridden custom query class (which #81 accounts for).


feat: Allow piping from term into new buffer

Still testing and working out some odd behavior but this feature should come online in the next few days :) feel free to try the branch if you don't feel like waiting - it works, I just want to get some more testing in and update the docs before I merge.


Run CLI integration tests against DC/OS OSS

This adds support for running integration tests against DC/OS open.
In order to be enabled, we should create a new Jenkins job using the
integration-tests-open.groovy script.
https://jira.mesosphere.com/browse/DCOS_OSS-4035

@mesosphere-ci run integration tests

@mesosphere-ci run integration tests

@mesosphere-ci run integration tests


Git workflow (fixes #12)

I added support for a git-based workflow based on commit hashes.
There is a versioned test file: test/git_workflow/simple_transitive_change.atd
Essentially, commit ff9920b0 is v1 and b1a63837 (HEAD) is v2.
So you can generate a migration like this:
esy x stork gen -o <output_prefix> --git test/git_workflow/simple_transitive_change.atd 1:ff9920b0 2
A couple of things we need to discuss:
The command-line invocation is not really compatible with the file-based workflow. I couldn't come up with a better idea than
--git
and all the version:commit pairs instead of files. But then we lose the file check provided by Cmdliner.
Suggestion if we want to demote the file-based workflow to second-class:
add a flag --files for the list of files with a "file exists" check
The other thing is I chose to checkout the commits into the same location where the versioned file is found. That might be nice, or it might be accidentally destructive. Maybe a better location is "output_prefix" or even just a temporary directory (Filename.get_temp_dir_name etc.). Initially I wanted to just put them in temp files with random names provided by Filename.temp_file, but there is a lot of logic around inferring versions from the filenames that I didn't want to mess with :(

I also didn't write a proper test, maybe someone can help me out there?

Suggestion if we want to demote the file-based workflow to second-class:
add a flag --files for the list of files with a "file exists" check

Agreed, I think the git based workflow should be the default, and the file based workflow should use the --files option.

The other thing is I chose to checkout the commits into the same location where the versioned file is found. That might be nice, or it might be accidentally destructive. Maybe a better location is "output_prefix" or even just a temporary directory (Filename.get_temp_dir_name etc.). Initially I wanted to just put them in temp files with random names provided by Filename.temp_file, but there is a lot of logic around inferring versions from the filenames that I didn't want to mess with :(

That's a good question, I would probably use the output location, but inside .stork/ is also a possibility, what's your take on that @wokalski?

I also didn't write a proper test, maybe someone can help me out there?
My "test" was to diff the migration generated by "simple_transitive_change" file-based and git-based workflow.

I can definitely help you with the tests, we might struggle at first because we'll have to edit the commit sha every time we make a rebase but this will be stable once merged to master.

Both temporary directory, .stork, any other configurable location, make sense to me. Checking the files next to the input might be a bit annoying when you create a commit. .stork/any other configurable location are kind of useful because of easy debugging. However, if we look at problems one or another solves it's hard for me to point out if there's any real problem solved by providing visibility into the files from given commits.

Both temporary directory, .stork, any other configurable location, make sense to me. Checking the files next to the input might be a bit annoying when you create a commit. .stork/any other configurable location are kind of useful because of easy debugging. However, if we look at problems one or another solves it's hard for me to point out if there's any real problem solved by providing visibility into the files from given commits.

Could we use cache_dir, i.e. ~/.cache/stork unless STORK_CACHE_DIR is set? It doesn't seem to be used for anything yet. I'm wondering if we should clean up after ourselves and delete the checked out files.

I changed the location of the git checkouts, using Config.cache_dir now, it can easily be changed.


Open & Close Calendar By DatePicker Ref

I want to open datepicker manually and here is my code:
const datePickerRef = useRef();
...
<DatePicker ref={datePickerRef} >
...
</DatePicker>
<IonButton onClick={() => datePickerRef.current.openCalendar()}>
Click
</IonButton >
The problem is that I get this error on datePickerRef.current : "Object is possibly 'undefined'"

If you are using typescript replace const datePickerRef = useRef(); with const datePickerRef = useRef<any>(); and if you want to make sure that the object isn't undefined, put datePickerRef.current.openCalendar() in an if statement.
if(datePickerRef.current){
   datePickerRef.current.openCalendar()
}

Thank you for your help.
There is another problem!
I have a component called MyDatepicker.tsx and I attached it here, my
problem is that when I change date without pressing confirm button, and
after that I press today button, today button won't work but if I change
date and press confirm and open datepicker again, today button will work.
Actually I'm not sure if it's today button that is not working or the
onChange event!
Please look at this image
[image: Untitled.jpg]
The value in console_log is the date value before and after pressing today
and confirm buttons.
As you can see I changed the date and confirmed but the value (console_log)
is still the same. It should be "Tue Nov 30 2021 ....".
I hope you get my problem :)
On Tue, Nov 16, 2021 at 2:38 PM Shahab @.***> wrote:

If you are using typescript replace const datePickerRef = useRef(); with const
datePickerRef = useRef(); and if you want to make sure that the
object isn't undefined, put datePickerRef.current.openCalendar() in an if
statement.
if(datePickerRef.current){
datePickerRef.current.openCalendar()}
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/shahabyazdi/react-multi-date-picker/issues/80#issuecomment-970163836,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKWQLS3WJAQ4T4VCDV4A3RLUMI3RVANCNFSM5IDSQK7Q
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Thank you for your help.
There is another problem!
I have a component called MyDatepicker.tsx, my problem is that when I change date without pressing confirm button, and after that I press today button, today button won't work but if I change date and press confirm and reopen datepicker, today button will work.
Actually I'm not sure if it's today button that is not working or the onChange event!
Please look at this image

The value in console_log is the date value before and after pressing today and confirm buttons.
As you can see I changed the date and confirmed but the value (console_log) is still the same. It should be "Tue Nov 30 2021 ....".
I hope you get my problem :)
Here is MyDatepicker.tsx.
import React, { useState } from 'react';
import { IonIcon } from '@ionic/react';
import { calendarOutline } from 'ionicons/icons';
import './MyDatepicker.css';
import DatePicker from "react-multi-date-picker";
import gregorian from "react-date-object/calendars/gregorian";
import gregorian_en from "react-date-object/locales/gregorian_en";
import persian from "react-date-object/calendars/persian";
import persian_fa from "react-date-object/locales/persian_fa";
import "react-multi-date-picker/styles/layouts/mobile.css";
const MyDatepicker: React.FC<{ isRange: boolean }> = props => {
const [state, setState] = useState({
dateValue: new Date(),
calendar: persian,
locale: persian_fa,
switchLabel: 'میلادی',
todayLabel: 'امروز',
fontClass: '',
toggle: true
})
const SwitchCalendar = () => {
state.toggle ?
setState({ ...state, calendar: gregorian, locale: gregorian_en, switchLabel: 'شمسی', todayLabel: 'Today', fontClass: 'font-tahoma', toggle: false })
:
setState({ ...state, calendar: persian, locale: persian_fa, switchLabel: 'میلادی', todayLabel: 'امروز', fontClass: '', toggle: true });
}
// console.log(state.dateValue);
return (

<DatePicker
value={state.dateValue}
onChange={() => setState({...state, dateValue: state.dateValue})}
calendar={state.calendar}
locale={state.locale}
minDate={new Date()}
className={"rmdp-mobile " + state.fontClass}
inputMode="none"
range={props.isRange}
>

<button className="datepicker-switch-btn font-iranyekan" onClick={SwitchCalendar}>
{state.switchLabel}
</button>
<button className="datepicker-today-btn" onClick={() => setState({...state, dateValue: new Date()})}>
{state.todayLabel}
</button>

</DatePicker>
<IonIcon icon={calendarOutline} className="datepicker-icon" />

);
};
export default MyDatepicker;

It seems to be a bug and needs to be fixed.
But unfortunately, it is not possible for me to fix this bug for another 8 days.

OK, no problem!
Fortunately, I'm not in a hurry so let us now when you fixed it :)

I have published a new version (3.3.0) and I hope your issue has been solved by installing it.


Enable solve python dependency by using cmake command.

In your instructions, we have to install extra modules by ourselves.
So, I solve this problem by using add_custom_target cmake command.

I split requirements.txt in #38.

dependency definition will be included in #25


markdown didn't want parse in the first line

Can you try to figure this up? I am using version 1.1.4
here my markdown source
#Bio Under Construction

#Genexea RP

Genexea RP terfokus pada Organisasi Exousires di Pulau Lacrimoxea. Terdiri atas Perkantoran Exousires, Sekolah Exousires, dan Manor Exousires serta penduduk di pulau Lacrimoxea.

There needs to be a space between the #s and the text. This is dictated by the CommonMark specification.


Use threads for baking navigation mesh inside editor

Enables threaded navigation mesh baking inside the editor.
Closes https://github.com/godotengine/godot/issues/90120
The baking with threads inside the editor was disabled because especially the SceneTree caused crashes in the past.
Now that the problematic parsing step and the baking step are split and a few new guards exist the baking can run on a thread again.
Note that there are still editor freezes from the parsing process with this as that needs to stay on the main-thread due to the SceneTree and nodes.
Longer freezes are primarily caused by the RenderingServer when visual meshes are parsed because the RenderingServer needs to shuffle all that Mesh data from the GPU back to the CPU.
Use collision shapes as source geometry instead of visual meshes to avoid most issues!

Thanks!


Update sbt-scoverage to 1.9.2

Updates org.scoverage:sbt-scoverage from 1.9.1 to 1.9.2.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scoverage", artifactId = "sbt-scoverage" } ]

labels: sbt-plugin-update, early-semver-patch, semver-spec-patch

Codecov Report

Merging #195 (405458a) into master (9ba18bf) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #195   +/-   ##
=======================================
  Coverage   87.30%   87.30%
=======================================
  Files          28       28
  Lines         843      843
  Branches       39       39
=======================================
  Hits          736      736
  Misses        107      107

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 9ba18bf...405458a. Read the comment docs.


Theming Form Fields

Select one ...  (check one with "x")
[ ] bug
[ ] feature request
[ ] enhancement
[x] question

Expected behavior

Reproduction of behavior
I attempted to follow theming guide in wiki documentation in both plunker and stackblitz to no avail. Importing dependencies.clarity, importing my theme, and then importing components.clarity with the ~@, which succeeded there, but blew up trying to load bootstrap variables (because reference was incompatible)
Essentially from a purely usability standpoint, I disagree with the idea inputs are just the underline, and wanted to just change border-bottom... in @mixin clr-form-fields-appearance to be border: so that I could have an entire textbox for my theme. I must not have a super clear understanding of scss, but didn't seem like defining my version of that mixin before/after or inbetween the dependencies.clarity.scss import and the components.clarity imports, really allowed changing the actual appearance of those fields.
I was wondering if I'm missing something, or if anyone has any ideas there.
Environment details

Angular version: 5.x.x

Clarity version:.11

OS and version: Windows 10

Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]

@ronnyek: If I am understanding your question correctly, your issue is more wrt the form border width and not the color. For forms we use border-bottom: 1px solid #9a9a9a;. This is what our UX recommends. If you override the variables, all you would be able to change is the color #9a9a9a. If you want borders on all sides, then you would have to add the style in your CSS to override the clarity border-bottom style altogether - For eg: border: 1px solid black but please note that this is not what our UX recommends.
Please let me know if this helps and please correct me if I didn't understand your question correctly.
I will keep this issue open until you respond but if my understanding is correct, then you would have to override clarity styles at your end. Theming will only help you change the border bottom color.

Well I was trying to make it bordered on all sides, but I am going to just try and get clarity in place as is,
and then see if it is really is problematic. I appreciate the input

No worries. I will close this issue as the question was answered but please feel free to reopen the issue and let us know if you have any more questions or feedback.


WIP: Remove redundant switch in get_resource

Probably not valid anymore but I wanted to capture this.
https://github.com/ARMmbed/mbed-client/pull/505

@maclobdell

@teetak01 Any comment on this? Looks like other refactors might be doable in m2mFirmware.cpp as well.

Looks ok, although this code is not used by Device Management client as its old implementation for mbed-client library.

I had a feeling that was the case.
Any efforts underway to refactor unused stuff out?

@teetak01 bump^^^

We have nothing active on this area. It is always possible that someone external might be using some of those features, but PDMC does not use those.

@40Grit  - the release process we have - is a not 100% open source compatible in the way one might want (for various reasons I won't go into). the contribution is OK from my point of view, too. It also removes codelines (which is always a plus). Question is, how do you want this credited - as 40Grit or you true name (or both)? The commit itself will not be visible in our history, as we do a code drop via a few steps to this repository and commit history gets squashed fully.

So, the mention of the credits will be in changelog (and a new file CONTRIBUTORS.md).
You also have to explicitly answer and agree, that your contribution is OK legally as Apache 2.0 contribution (in and outgoing license for us is the same).

@JanneKiiskila @teetak01
I don't need the credit, but if this helps to open the gates for community contributions then I'll do whatever it takes.
I'll make the changes from @40Grit and also explicitly type that I agree to the license.
I'd like to hear the various reasons why the release process "is not open source compatible"
Feel free to contact me out of band about it.
Till then, I'm assuming it's too closely tied to the LWM2M server sources.
This code-base is a work of art; our team would be honored to contribute.

Any thing more I need to do besides say I agree the code I have contributed through this PR is made under Apache 2.0 license?
I will make the requested changes shortly.

One more thing, under which identity do you want to be credited for?

This will require rebase I assume?
@JanneKiiskila
Also, rereading your comments sounds like i just need to say how i want to be credited and you will handle the rest?
Just put Garrett LoVerde (@40Grit ) in the contributors.md.

I agree the code I have contributed through this PR is made under Apache 2.0 license.

Internal PR #1667 filed. It needs to pass our CI Testing + code reviews etc. It was easyily applied with git format patch and git am, no merge conflicts.

Status?

PR should likely go in and come out via Pelion Device Management Client version 3.5.0 release.

Closing. This was part of #53
thanks for the contribution!


ChatVectorDBChain and map_reduce qa chain does not seem to work

I'm trying to use map_reduce qa chain together with chat vector and it does not work.
            question_generator = LLMChain(llm=llm, prompt=CONDENSE_QUESTION_PROMPT)
            doc_chain = load_qa_chain(llm, chain_type="map_reduce", verbose=True)

            chain = ChatVectorDBChain(
                vectorstore=self.main_context.index,
                question_generator=question_generator,
                combine_docs_chain=doc_chain,
            )

           print(self.chain({
                'question': message,
                'chat_history': [],
            })['answer'])

It keeps throwing KeyError: {'chat_history'} when I tried to run the feed in the input. Do you guys have any idea?

From my debugging, the issue is as following:

When chatvectordb chain wants to get the answer, it will call combine_docs chain (which is MapReduceDocumentsChain), when it calls it passed  question & history as an input
MapReduceDocumentsChains use the prompt_length from StuffDocumentsChain to calculate number of tokens
HOWEVER, the prompt template of StuffDocumentsChain does not have the chat_history variable so it will throw error from there

I think since we don't need the chat_history in the combine_docs chain, we can remove it.


Adding a Value and Location displaying toolbar

@godber
The x/y/value display works exactly like merview:

when you click the mouse the values update
When you click, hold, and move the values update with the mouse
The values do not update when the mouse is just moving around without being clicked.

I can make it so the values update with the mouse whenever it moves if you want.

Here are a couple of examples of what it looks like right now:

What does it do for color image?

Shows 0 for three band images.

Make it should show the R, G, and B values.

Also, command+drag no longer permits panning the image.  This could probably peacefully coexist with the click for value and click and drag for value functionality.

Can we add this image to the core set of planetary_test_data so we can test functionality with a 3 band colored image?

I have to reset the contrast/rotation/etc. after switching images

Yes, ALL of the display parameters should be stored with the image.  They are NOT independant global parameters but attributes of displaying a specific image.  :)

Compare this with merview zoomed in closely.  I find two issues on Linux, see if you can reproduce them on Mac.

Zooming in really close (like 50x), moving the cursor around INSIDE a single pixel, the value changes.
switching X11 desktops results in the x,y,value info ceasing to update.


Add secio

I'm currently working on this, work can be tracked here

https://github.com/ipfs/js-libp2p-crypto
https://github.com/ipfs/js-libp2p-secio

🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉


Allow HashSet to be used in "any", "all"

It would be nice if a HashSet could be used instead of Vec in the any and all functions (and eq_any etc. but I don't know if a HashSet is allowed here already). HashSets are obviously not strictly speaking arrays or even ordered collections but none of the SQL functions care about the order in the given array anyway (to my knowledge), so using an unordered collection instead of an ordered one should be totally fine.
This would reduce the verbosity as you currently have to convert to a Vec (unless there is some other way to use HashSets that I am missing).

This issue sounds probably like a trivial problem, but you touched at least two completely different problems here.
expr.eq_any(array) results in the following sql expr IN ($1, … $n) where a bind parameter is used for each item in array. This means this expression implies that the array item type needs to implement ToSql<SqlTypeOf<expr>, DB>.
expr.eq(all(array)) (and expr.eq(any(array))) results in the following sql: expr = ANY($1) where a bind parameter is used for the complete array. This implies that the array type itself needs to implement ToSql<Array<SqlTypeOf<expr>, DB>.
So adding support for HashSet in all of this 2 cases requires completely different code changes. From looking at the relevant code it seems like the first case is already supported, as HashSet<T> already implements IntoIterator<Item = T>. The second case is not covered as we normally only provide ToSql in combination with a corresponding FromSql impl. In my opinion having a FromSql<Array<ST>, DB> for HashSet<T> impl does not make much sense, therefore there is no existing impl here. I may change my mind if someone provides a really good use case for this, but till then this is a wont fix.


python3Packages.pysoma: init at 0.0.10

Motivation for this change
Python wrapper for the HTTP API provided by SOMA Connect.
https://pypi.org/project/pysoma
This is a Home Assistant dependency.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
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)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch)
If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 109454 run on x86_64-darwin 1

3 packages built:

python37Packages.pysoma
python38Packages.pysoma
python39Packages.pysoma

This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch)
If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 109454 run on x86_64-darwin 1

3 packages built:

python37Packages.pysoma
python38Packages.pysoma
python39Packages.pysoma

This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch)
If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 109454 run on x86_64-linux 1

3 packages built:

python37Packages.pysoma
python38Packages.pysoma
python39Packages.pysoma

This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch)
If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 109454 run on x86_64-linux 1

3 packages built:

python37Packages.pysoma
python38Packages.pysoma
python39Packages.pysoma


Optimize resizing scratch allocator

When allocating a new block, make it twice as large as the current largest block
When resetting the frame, use the largest block as the new buffer

Currently the scratch allocator "merges" all blocks when it gets reset and create a mega-block with a size equal to the sum of all current blocks like this https://github.com/NotAPenguin0/phobos-rs/blob/2a1e539611bb3ede5c2d7978300353630c7c553b/src/allocator/scratch_allocator.rs#L223
Would we allow users to switch between this and the proposed method or should we just implement the proposed method as new default behavior?
Imo I think we should since it would simplify the reset function (since we wouldn't need to allocate a new buffer, just re-use the largest existing one) but it could cause issues when something like this happens (for example):

Allocate 1024 (creates block with size of 1048 or chunk_size)
Allocate 1000 (creates block with size of 1048 (for alignment maybe?) or chunk_size)
Reset (uses block of 1024 as new buffer)
Does 1. and 2. again, which would cause the second allocation to actually need to actually allocate a new buffer for it (unless buffers do not get deallocated, in which case idk why even bother)

In your example, the second block allocated would be 2096 bytes large and that would be the one used next frame (allocate the new block with 2x the size of the previous largest block)


Merge branch 2.4.0-release

Update to the new version

Codecov Report

Merging #1897 (85bd38b) into master (841fc73) will decrease coverage by 0.50%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master    #1897      +/-   ##
============================================
- Coverage     67.85%   67.35%   -0.51%
+ Complexity     2799     2788      -11
============================================
  Files           501      501
  Lines         11574    11571       -3
  Branches       1118     1116       -2
============================================
- Hits           7854     7794      -60
- Misses         3156     3208      +52
- Partials        564      569       +5

Impacted Files
Coverage Δ

...ache/shenyu/client/tars/common/dto/TarsRpcExt.java
0.00% <0.00%> (-30.77%)
:arrow_down:

...ache/shenyu/plugin/grpc/cache/GrpcClientCache.java
64.70% <0.00%> (-29.42%)
:arrow_down:

...enyu/client/tars/TarsServiceBeanPostProcessor.java
36.76% <0.00%> (-19.12%)
:arrow_down:

...che/shenyu/sync/data/http/HttpSyncDataService.java
63.10% <0.00%> (-18.45%)
:arrow_down:

...che/shenyu/admin/model/vo/SelectorConditionVO.java
71.42% <0.00%> (-14.29%)
:arrow_down:

...a/org/apache/shenyu/common/utils/VersionUtils.java
67.85% <0.00%> (-10.72%)
:arrow_down:

...henyu/plugin/grpc/resolver/ShenyuNameResolver.java
56.84% <0.00%> (-6.32%)
:arrow_down:

...henyu/plugin/httpclient/NettyHttpClientPlugin.java
58.00% <0.00%> (-2.00%)
:arrow_down:

...shenyu/sync/data/consul/ConsulSyncDataService.java
66.10% <0.00%> (-1.70%)
:arrow_down:

...elimiter/handler/RateLimiterPluginDataHandler.java
69.69% <0.00%> (-1.52%)
:arrow_down:

... and 3 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 841fc73...85bd38b. Read the comment docs.


Fix mismatch NS forest

Fixes #243
When looking at why L5 IT_1 doesn’t have NS forest, Renee noticed that L5 IT_1 in her sheet corresponds to CS202002013_250 (in ours this is L6 IT_C2) this explains why it doesn’t have NS forest.
I have asked her if we can implement checks back to nomenclature file to ensure the pref label lines up with taxonomy ID.
I’m hoping this is the only mistake (I’ve take a look at others in the screenshot she sent and they seem alright - checks should tell us.
Renee said she is pretty sure that’s just a one off mismatch - I’ve asked to double check that the NS forest markers are right.
@hkir-dev could you help me refresh the NS-forest stuff please? - Happy for you to fix it on this branch then merge it into master. Thanks :)

updated

@hkir-dev thanks! looks good! I'll merge it after the checks have passed :)


OptimizationBase v2.0 plan

The current AD implementation here (at least) lacks these features/suffers from these issues -

MOAR!! oracles: #10, jvp and vjp for constraints, #61, #50
Redundant function evaluations: #22
Consistent support for exotic array types: #14 #7
Some more backends: #21 #32 and FastDifferentiation
Defaults
Mixing AD backends when it makes sense

The reason these are outstanding has been lower priority and tediousness due to having to do it for multiple backends all the time.
So my aim with #54 has been to start fleshing out some of the ideas of how these would look, we obviously can't expect DI to be the solution for everything but some of these are right up in its alley and it gives an excuse to spend time rethinking the implementation.
I plan to address #10, jvp and vjp for constraints, points 2, 3, #21 and FastDifferentiation, 5, and 6 in #54. I am hopeful to get this in by (at the absolute maximum) end of summer.

It might also make sense to do a v2.0 branch and start doing incremental PRs for these that build off #54 to that

From my perspective, it would make sense to integrate DifferentiationInterface as early as possible, even if it doesn't do everything yet. The reason is that a large stress test like this would be great to spot bugs and inefficiencies.

[!WARNING]
Not everything is gonna be perfect in DI from the start. But at least if we start using it, we can optimize every implementation in just one place instead of several.

MOAR!! oracles

The Lagrangian hessian is a recurrent concern, a possible solution is https://github.com/gdalle/DifferentiationInterface.jl/issues/206 but I think it's a bit overkill. https://github.com/gdalle/DifferentiationInterface.jl/issues/311 is more reasonable to allow passing the multipliers as a constant parameters.

jvp and vjp for constraints

DI has pushforward and pullback

Redundant function evaluations

DI has value_and_gradient and now value_gradient_and_hessian

Consistent support for exotic array types

DITest has a battery of scenarios involving static arrays for testing. Non-mutating operators are written so that even SArray will work (but more testing won't hurt).
As for sparsity, what you really need is SparseConnectivityTracer + DifferentiationInterface. Our sparsity detection is 10-100x faster than Symbolics, our coloring seems on par with the C++ ColPack. Last thing I need to do is benchmark against SparseDiffTools.

https://gdalle.github.io/SparsityDetectionComparison/
https://gdalle.github.io/MatrixColoringComparison/

Some more backends

DI does all the work for you there.

Mixing AD backends when it makes sense

DI has SecondOrder


Tower of HANOI in using C++

Type
Algorithm
Directory
Algorithm =>Tower of HANOI in using C++=>Tower of HANOI in using C++.extension
Description
The Tower of Hanoi is a mathematical puzzle invented by the French mathematician Edouard Lucas in 1883.
There are three pegs, source(A), Auxiliary (B) and Destination(C). Peg A contains a set of disks stacked to resemble a tower, with the largest disk at the bottom and the smallest disk at the top. figure 1 Illustrate the initial configuration of the pegs for 3 disks. The objective is to transfer the entire tower of disks in peg A to peg C maintaining the same order of the disks.
Programming Language

[X] c++
[X] c
[ ] python
[ ] java
[ ] kotlin
[ ] javascript
[ ] typescript
[X] c#
[ ] swift
[ ] ruby
[ ] scala
[ ] go
[ ] php
[ ] haskell
[ ] bash

yasss

Assign this to me

@andianiputri  Assign this to me in C++,C.

duplicate of #697


[GEN-1910]: init workflow for UI E2E tests (using Cypress)

This pull request includes several changes to improve the Cypress testing setup and streamline the end-to-end (E2E) testing workflow. The most important changes include adding new Cypress configurations, updating the package.json scripts, and creating a comprehensive script for managing the Odigos UI.
Improvements to Cypress Testing Setup:

frontend/webapp/cypress.config.ts: Refactored Cypress configuration to use Cypress.ConfigOptions and updated settings such as baseUrl, supportFile, and waitForAnimations.
frontend/webapp/package.json: Added new scripts for opening and running Cypress tests (cy:open and cy:run) and updated the Cypress dependency version. [1] [2]
frontend/webapp/cypress/e2e/spec.cy.ts: Added a new template spec file for Cypress tests.

Streamlining E2E Testing Workflow:

.github/workflows/e2e.yaml: Added 'ui' to the test scenarios and removed the installation step for the frontend that was not run in every scenario. [1] [2]
tests/common/odigos_ui.sh: Created a comprehensive script to manage the Odigos UI, including starting, testing, and ending the UI processes.
tests/e2e/ui/cypress-test.yaml: Added a new YAML configuration file to run E2E Cypress tests against the Odigos UI.

Additional Changes:

tests/common/.gitignore: Added patterns to ignore .pid and .log files.
tests/e2e/cli-upgrade/odigos-ui.pid: Removed an old PID file for the Odigos UI.

This workflow has been tested:

Purposely failing Cypress tests: https://github.com/odigos-io/odigos/actions/runs/12166333848/job/33932585490?pr=1912
Successful case of Cypress test: https://github.com/odigos-io/odigos/actions/runs/12166511160/job/33933366914?pr=1912
Confirmation of Front + Back connection in Cypress test: https://github.com/odigos-io/odigos/actions/runs/12166791144/job/33934129822?pr=1912


How to invalidate token programmatically

if the cognito session (namely the accesstoken/idtoken) is not valid (_session.isValid()) I get a new token in exchange for the refreshtoken by calling _cognitoUser.getSession(). This is working.
Once in a while I would like to invalidate the session and retrieve a new accesstoken/idtoken in exchange for the refreshtoken.
Something like _session.invalidateToken()
so that the next attempt to retrieve the token results in refreshing the token from cognito-server:
Future<String> retrieveToken() async {     if (_session.isValid()) return _session.getIdToken().getJwtToken();     this._session = await _cognitoUser.getSession();     return _session.getIdToken().getJwtToken();   }
Is this possible somehow already? If not can this implemented into the library?

Will look into it @mikes222

Is this similar to Use Case 32 in amazon-cognito-identity-js?

Unfortunately not. #uc32 describes the behavior if the refresh token is expired.
In my usecase none of the tokens are expired. I just want to get a new id token from cognito server without forcing the user to logon manually by entering its credentials.
What i want to do is forcing your library to refresh the token. Something like session.invalidatetoken() so that the next call to session.isvalid() returns false and cognitouser.getsession() retrieves new tokens from cognito server by using the refresh token.
On June 5, 2018 11:22:21 AM GMT+02:00, Jon Saw<EMAIL_ADDRESS>wrote:

Is this similar to Use Case 32 in
amazon-cognito-identity-js?
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
https://github.com/jonsaw/amazon-cognito-identity-dart/issues/12#issuecomment-394642137

--
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Thanks @mikes222 will take a look at the PR!

Deployed to v0.0.17


Merge main into dev-1.29

Merging main into dev-1.29 to maintain branch sync

No conflicts on this branch sync.
cc: @reylejano @natalisucks @tengqm @sftim

/lgtm

/approve


PubSub Slow Subscriber.  Pooling?

Hi,
We just ran a quick test.  A 4 core VM (in GCP) running a .Net client with 4 threads can consume PubSub at about 200Mbps.  A similar 16core VM (running 16 threads) can consume at 300Mbps... not a drastic improvement.
However in the second example if we fire up the application 3 times we consume at 900Mbps.  This indicated the bottle neck is not in the VM or the network, but inside the .Net subscriber code.  We create a separate subscriber per thread, but I note the library seems to use pooling for its 'channel's.
Is it possible to create PubSub subscribers that don't pool connections, have the connection pool scale for performance, or any other technique to increase throughput?
Thanks!

@NPSF3000 Are you using the SimpleSubscriber class? This is most suitable class to use.  Please can you show the code where you create the subscriber class, and start the subscription? Thanks.

@chrisdunelm A rough overview of the code is the following:
`for (int i = 0; i < Environment.ProcessorCount * 3; i++)
{
Task.Run(async () =>
{
try
{
var subscriber = SubscriberClient.Create();
while (true)
{
var response = await subscriber.PullAsync(devmainsubscriptionName, returnImmediately: true, maxMessages: 1000);
var messages = response.ReceivedMessages.Select(m => m.Message.Data.ToStringUtf8());
                        if (!messages.Any())
                            continue;

                        // Acknowledge the message so we don't see it again.
                        var ackIds = new string[response.ReceivedMessages.Count];
                        for (int j = 0; j < response.ReceivedMessages.Count; ++j)
                            ackIds[j] = response.ReceivedMessages[j].AckId;
                        await subscriber.AcknowledgeAsync(devmainsubscriptionName, ackIds);
                    }
                }
                catch (Exception e)
                {
                    //...
                }
            });`

Looks like we might be creating 3 tasks per core.

@NPSF3000 Thanks for the code.
Please use the SimpleSubscriber instead. It will automatically create multiple channels to the pubsub service, ensuring there is no network/channel bottleneck.
There is a simple example here: https://github.com/GoogleCloudPlatform/google-cloud-dotnet/blob/master/apis/Google.Cloud.PubSub.V1/Google.Cloud.PubSub.V1.Snippets/SubscriberClientSnippets.cs#L120

@chrisdunelm thanks.  We'll take a look and comment back if any issue arise.  Much appreciated.

Closing, please re-open if this doesn't work as expected.

Hi @chrisdunelm,
We are facing a different issue with the message not being acknowledged using the SimpleSubscriber. (Note: we did not have this issue with SubscriberClient before)
We tried with around 500k records residing in the subscription and it was accurate and same number of items were inserted into the buffer (READMAINLOGCOUNTER value was accurate too)
but as soon as we tried with around 20 Million records we got the random number of items inserted into the buffer and READMAINLOGCOUNTER was off by millions (it was 25M, 28M, 30M completely random on various tests). This means it was not properly acknowledging the message after reading it.
The buffer is a ConcurrentQueue.
Task.Run(async () =>
           {
               SimpleSubscriber simpleSubscriber = await SimpleSubscriber.CreateAsync(devmainsubscriptionName);
               await simpleSubscriber.StartAsync((msg, cancellationToken) =>
               {
                   if (msg != null)
                   {
                       buffer.Add(msg.Data.ToStringUtf8());
                       Interlocked.Add(ref READMAINLOGCOUNTER, 1);
                       // Return Reply.Ack to indicate this message has been handled.
                       return Task.FromResult(SimpleSubscriber.Reply.Ack);
                   }
                   return Task.FromResult(SimpleSubscriber.Reply.Nack);
               });
           });

// add method of buffer
public void Add(T item)
{
           if (addFinished) throw new Exception("Buffer was set to add finished!");
           queue.Enqueue(item);
}

As mentioned, please let us know what could be the reason it worked completely fine with fewer records and completely off with more and any improvement/suggestion for the code above.
Thanks,
Bibek


Event Details: Organizer information floats when scrolled

fixed na ni :D

https://github.com/ploidddddd/purplekeep/issues/103


bluez5: install patches for all rpi models

This is required to make rpi0-wireless bluetooth work.

Can one of the admins verify this patch?

I think this PR raises a problem - RaspberryPi Zero WiFi doesn't include all the bits needed for bluetooth. We can:

Add the patches and firmware for any rpi (which will mean rpi2 will include stuff it doesn't need but I see it as a tiny side effect)
Use a new SOC_FAMILY rpiwifi for example in witch rpi3 and rpi0wifi will be included and these bluez5 modifications will be done based on it.

@betafive @kraj What do you guys think?

If this is contained to "bluez5_%.bbappend" then there should be no impact on rpi devices which don't install bluez5 and a minor waste on those that do install bluez5 but don't need that firmware. So if it's contained to that file then I'd just apply the changes for all rpi devices.

It is indeed contained right now in bluez5 package. That's why I consider it as a good compromise.

@michal-mazurek could you push a change to this which uses _rpi so that we apply these change to all the rpi machines?

@kraj :) see the comments above.


fix(tower-plugin): change invalid name for policy (not allow upper case)

Codecov Report

Merging #331 (a523f23) into main (9695d0e) will decrease coverage by 0.20%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #331      +/-   ##
==========================================
- Coverage   63.96%   63.75%   -0.21%
==========================================
  Files          41       41
  Lines        7171     7171
==========================================
- Hits         4587     4572      -15
- Misses       2203     2216      +13
- Partials      381      383       +2

Impacted Files
Coverage Δ

plugin/tower/pkg/controller/policy/controller.go
83.17% <ø> (-0.36%)
:arrow_down:

pkg/controller/group/group_controller.go
69.85% <0.00%> (-1.63%)
:arrow_down:

pkg/agent/datapath/multiBridgeDatapath.go
59.89% <0.00%> (-0.53%)
:arrow_down:

pkg/agent/controller/policy/policy_controller.go
78.78% <0.00%> (ø)


First page does not display when firstPageIsStarted is true

Are you requesting a feature, reporting a bug or asking a question?
Reporting a bug.
What is the current behavior?
Starting with version v1.0.60, when the attribute firstPageIsStarted is set to true, the first page is simply ignored. Only the start button is shown, but not the first question.
What is the expected behavior?
The first question is shown completely above to "start" button. This was working up to v1.0.59 and is even used at a demonstration for a history quiz officially by surveyJS.
How would you reproduce the current behavior (if this is a bug)?
Use surveyJS 1.0.60.
Create at least two pages with content and set firstPageIsStarted to true. You'll notice the first page will magically disappear. Then set firstPageIsStarted to false, and you'll notice the first page isn't gone.
Provide the test code and the tested page URL (if applicable)
Tested page URL:
v1.0.60 (not working): https://jsfiddle.net/hs67nfzy/2/
v1.0.59 (working): https://jsfiddle.net/2up6tbck/2/
Test code

Survey.Survey.cssType = "bootstrap";

var json = {
    firstPageIsStarted: true,
    pages: [
        {
            questions: [
                {
                    type: "html",
                    html: "This HTML should be displayed."
                }
            ]
        }, {
            questions: [
                {
                    type: "radiogroup",
                    title: "How are you?",
                    choices: [
                        "Great"
                    ]
                }
            ]
        }
    ]
};

var survey = new Survey.Model(json);

$("#surveyElement").Survey({
  model: survey
});

Specify your

surveyjs platform: jQuery
surveyjs version: 1.0.60

@reclaimingmytime The bug has been fixed, a unit test has been modified to reproduce the issue.
The issue was introduced due perfomance optimization.
Thank you,
Andrew


refactor(generic): standardize reading package.json files

Have you read the section in CONTRIBUTING.md about pull requests?
Yes
Are your changes appropriately documented?
N/A
Do your changes have sufficient test coverage?
Yes
Does the testsuite pass successfully on your local machine?
Yes
Summarize your changes:
This is an experiment to standardize reading/parsing package.json files.

I restarted the AppVeyor build because I don't think the errors in https://ci.appveyor.com/project/electron-userland/electron-forge/build/1.0.56 was related to my changes.

@malept That failure happened yesterday as well, I though it was an AppVeyor issue and just reran.  Maybe it is still an AppVeyor issues but 50% failure rate is not good for CI.  I'll switch out that native package again 😆

gyp ERR! stack Error: EBUSY: resource busy or locked, open 'C:\Users\appveyor.node-gyp\6.9.2\Release\node.lib'


bug: ApisixIngress synced failed, with error: not found

Current Behavior
When use ApisixUpstream with apisix ingress controller 1.7
It show this status:
apiVersion: apisix.apache.org/v2
kind: ApisixUpstream
...
status:
  conditions:
  - message: not found
    observedGeneration: 1
    reason: ResourceSyncAborted
    status: "False"
    type: ResourcesAvailable

event log:
  Normal   ResourcesSynced      18m (x2 over 18m)     ApisixIngress  ApisixIngress synced successfully
  Normal   ResourcesSynced      15m                   ApisixIngress  ApisixIngress synced successfully
  Warning  ResourceSyncAborted  11m (x7 over 14m)     ApisixIngress  ApisixIngress synced failed, with error: not found
  Warning  ResourceSyncAborted  16s (x13 over 10m)    ApisixIngress  ApisixIngress synced failed, with error: not found

But when I change image to 1.6.1, it was successful
apiVersion: apisix.apache.org/v2
kind: ApisixUpstream
...
status:
  conditions:
  - message: Sync Successfully
    observedGeneration: 1
    reason: ResourcesSynced
    status: "True"
    type: ResourcesAvailable

If I change back to 1.7.0, it show not found again
Expected Behavior
It should be successful like before version
Error Logs
2023-10-06T11:52:36+08:00    debug    apisix/upstream.go:43    try to look up upstream    {"name": "<NAMESPACE>_<SERVICENAME>_8088", "url": "http://apisix-admin.ingress-apisix.svc.cluster.local:9180/apisix/admin/upstreams", "cluster": "default"}
2023-10-06T11:52:36+08:00    debug    apisix/apisix_upstream.go:351    updating upstream since ApisixUpstream changed    {"upstream": {"id":"ad53b4e6","name":"<NAMESPACE>_<SERVICENAME>_8088","desc":"Created by apisix-ingress-controller, DO NOT modify it manually","labels":{"managed-by":"apisix-ingress-controller"},"type":"roundrobin","nodes":[{"host":"<IP_ADDRESS>","port":8088,"weight":100}],"scheme":"http"}, "ApisixUpstream name": "<NAMESPACE>_<SERVICENAME>_8088"}
2023-10-06T11:52:36+08:00    debug    apisix/upstream.go:189    try to update upstream    {"id": "ad53b4e6", "name": "<NAMESPACE>_<SERVICENAME>_8088", "cluster": "default", "url": "http://apisix-admin.ingress-apisix.svc.cluster.local:9180/apisix/admin/upstreams"}
2023-10-06T11:52:36+08:00    debug    apisix/upstreamservicerelation.go:91    try to create upstreamService in cache    {"cluster": "default"}
2023-10-06T11:52:36+08:00    debug    apisix/upstreamservicerelation.go:47    try to get upstreamService in cache    {"service_name": "<NAMESPACE>_<SERVICENAME>", "cluster": "default"}
2023-10-06T11:52:36+08:00    debug    apisix/cluster.go:798    updating resource in cluster    {"cluster_name": "default", "name": "upstream", "url": "http://apisix-admin.ingress-apisix.svc.cluster.local:9180/apisix/admin/upstreams/ad53b4e6", "body": "{\"id\":\"ad53b4e6\",\"name\":\"<NAMESPACE>_<SERVICENAME>_8088\",\"desc\":\"Created by apisix-ingress-controller, DO NOT modify it manually\",\"labels\":{\"managed-by\":\"apisix-ingress-controller\"},\"type\":\"roundrobin\",\"nodes\":[{\"host\":\"<IP_ADDRESS>\",\"port\":8088,\"weight\":100}],\"scheme\":\"http\"}"}
2023-10-06T11:52:36+08:00    debug    apisix/resource.go:135    got upstream: {"desc":"Created by apisix-ingress-controller, DO NOT modify it manually","labels":{"managed-by":"apisix-ingress-controller"},"create_time":1696389535,"scheme":"http","pass_host":"pass","type":"roundrobin","id":"ad53b4e6","name":"<NAMESPACE>_<SERVICENAME>_8088","update_time":1696564356,"nodes":[{"host":"<IP_ADDRESS>","weight":100,"priority":0,"port":8088}],"hash_on":"vars"}
2023-10-06T11:52:36+08:00    debug    apisix/upstream.go:43    try to look up upstream    {"name": "<NAMESPACE>_<SERVICENAME>_8088_service", "url": "http://apisix-admin.ingress-apisix.svc.cluster.local:9180/apisix/admin/upstreams", "cluster": "default"}
2023-10-06T11:52:36+08:00    debug    apisix/upstream.go:59    failed to find upstream in cache, will try to lookup from APISIX    {"name": "<NAMESPACE>_<SERVICENAME>_8088_service", "error": "not found"}
2023-10-06T11:52:36+08:00    debug    apisix/cluster.go:645    get resource in cluster    {"cluster_name": "default", "name": "upstream", "url": "http://apisix-admin.ingress-apisix.svc.cluster.local:9180/apisix/admin/upstreams/6fd1d84"}
2023-10-06T11:52:36+08:00    warn    apisix/cluster.go:1164    upstream not found    {"id": "6fd1d84", "url": "http://apisix-admin.ingress-apisix.svc.cluster.local:9180/apisix/admin/upstreams/6fd1d84", "cluster": "default"}
2023-10-06T11:52:36+08:00    error    apisix/apisix_upstream.go:332    failed to get upstream <NAMESPACE>_<SERVICENAME>_8088_service: not found
2023-10-06T11:52:36+08:00    warn    apisix/apisix_upstream.go:488    sync ApisixUpstream failed, will retry    {"object": {"Type":1,"Object":{"Key":"<NAMESPACE>/<SERVICENAME>","OldObject":null,"GroupVersion":"apisix.apache.org/v2"},"OldObject":null,"Tombstone":null}, "error": "not found"}

Steps to Reproduce

Install apisix helm chart
Create any ApisixIngress with ApisixUpstream

Environment
Docker image: apache/apisix-ingress-controller:1.7.0
Version: 1.7.0
Git SHA: no-git-module
Go Version: go1.20.8
Building OS/Arch: linux/amd64
Running OS/Arch: linux/amd64

Can you provide the complete ApisixUpstream configuration? And is it referenced by any ApisixRoute resources? Does it include the service that it contains?

Moreover, has the CRD used by APISIX Ingress been updated?

@tulequ Any updates here?

We have this error when trying to use this with a translated Ingress.
The docs make it seem like adding an ApisixUpstream is transparent, by simply having the same name as the service.

I do have the same problem.  I added a route which is linked to Upstream to reach an external service, basically like described here https://apisix.apache.org/docs/ingress-controller/tutorials/external-service/, but it doesn't work.
In the Ingress Controller I do get the following errors
2024-02-14T15:08:40+08:00    error    apisix/apisix_route.go:379    failed to sync ApisixRoute to apisix    {"error": "1 error occurred:\n\t* unexpected status code 400; error message: {\"error_msg\":\"failed to fetch upstream info by upstream id [53af2afe], response code: 404\"}\n\n\n"}
2024-02-14T15:08:40+08:00    warn    apisix/apisix_route.go:481    sync ApisixRoute failed, will retry    {"object": {"Type":4,"Object":{"Key":"tracs-dev/tracs-dev-notifications-route","OldObject":null,"GroupVersion":"apisix.apache.org/v2"},"OldObject":null,"Tombstone":null}, "error": "1 error occurred:\n\t* unexpected status code 400; error message: {\"error_msg\":\"failed to fetch upstream info by upstream id [53af2afe], response code: 404\"}\n\n\n"}
2024-02-14T15:08:40+08:00    warn    apisix/cluster.go:1164    upstream not found    {"id": "53af2afe", "url": "http://tracs-dev-apisix-admin.tracs-dev.svc.cluster.local:9180/apisix/admin/upstreams/53af2afe", "cluster": "default"}
2024-02-14T15:08:40+08:00    error    apisix/apisix_upstream.go:375    failed to get upstream tracs-dev_tracs-dev-notification-upstream: not found
2024-02-14T15:08:40+08:00    warn    apisix/apisix_upstream.go:488    sync ApisixUpstream failed, will retry    {"object": {"Type":4,"Object":{"Key":"tracs-dev/tracs-dev-notification-upstream","OldObject":null,"GroupVersion":"apisix.apache.org/v2"},"OldObject":null,"Tombstone":null}, "error": "not found"}
2024-02-14T15:08:40+08:00    error    translation/apisix_route.go:236    failed to translate ApisixUpstream at Upstream[0]    {"error": "ApisixUpstream tracs-dev/tracs-dev-notification-upstream ExternalNodes[0]'s name  as Domain must match lowercase RFC 1123 subdomain.  a lowercase RFC 1123 subdomain must consist of lower case alphanumeric characters, '-' or '.', and must start and end with an alphanumeric character", "apisix_upstream": "tracs-dev/tracs-dev-notification-upstream"}
2024-02-14T15:08:40+08:00    error    apisix/route.go:138    failed to create route: unexpected status code 400; error message: {"error_msg":"failed to fetch upstream info by upstream id [53af2afe], response code: 404"}

and this is the status of the Upstream
Status:
  Conditions:
    Message:              not found
    Observed Generation:  3
    Reason:               ResourceSyncAborted
    Status:               False
    Type:                 ResourcesAvailable
Events:
  Type     Reason               Age                    From           Message
  ----     ------               ----                   ----           -------
  Warning  ResourceSyncAborted  66s (x25052 over 18h)  ApisixIngress  ApisixIngress synced failed, with error: not found

Used versions:
tracs-dev-apisix-745b4b89b6 | OK | apisix: apache/apisix:3.5.0-debian
tracs-dev-ingress-controller-7fcd8d7bf8 | OK | ingress-controller: apache/apisix-ingress-controller:1.7.0

Any update on this problem? I am facing the same issue.

I am facing the same issue.
apache/apisix-ingress-controller:1.7.1

version 1.8.0(latest) the same issue on AKS : ApisixIngress synced failed, with error: not found

I'm also having the same issue. when will this be solved?


Package still does not comply with psr-4 autoloading standard.

Same problem as in https://github.com/liberu-genealogy/laravel-gedcom/issues/2
During installation of the package ( composer require familytree365/laravel-gedcom ) in a fresh LARAVEL 10 project, the following warnings occure:
Class FamilyTree365\LaravelGedcom\Utils\Exporter\Addr located in D:/LARAGON/www/laravel-gedcom/vendor/familytree365/laravel-gedcom/src\Utils\exporter\Addr.php does not comply with psr-4 autoloading standard. Skipping.                                                                                Class FamilyTree365\LaravelGedcom\Utils\Exporter\Fam\Caln located in D:/LARAGON/www/laravel-gedcom/vendor/familytree365/laravel-gedcom/src\Utils\exporter\Caln.php does not comply with psr-4 autoloading standard. Skipping.                                                                                Class FamilyTree365\LaravelGedcom\Utils\Exporter\Chan located in D:/LARAGON/www/laravel-gedcom/vendor/familytree365/laravel-gedcom/src\Utils\exporter\Chan.php does not comply with psr-4 autoloading standard. Skipping.                                                                                Class FamilyTree365\LaravelGedcom\Utils\Exporter\Date located in D:/LARAGON/www/laravel-gedcom/vendor/familytree365/laravel-gedcom/src\Utils\exporter\Date.php does not comply with psr-4 autoloading standard. Skipping.                                                                                Class FamilyTree365\LaravelGedcom\Utils\Exporter\Fam\Even located in D:/LARAGON/www/laravel-gedcom/vendor/familytree365/laravel-gedcom/src\Utils\exporter\Fam\Even.php does not comply with psr-4 autoloading standard. Skipping.                                                                                Class FamilyTree365\LaravelGedcom\Utils\Exporter\Fam\Slgs located in D:/LARAGON/www/laravel-gedcom/vendor/familytree365/laravel-gedcom/src\Utils\exporter\Fam\Slgs.php does not comply with psr-4 autoloading standard. Skipping.                                                                                Class FamilyTree365\LaravelGedcom\Utils\Exporter\Indi\Alia located in D:/LARAGON/www/laravel-gedcom/vendor/familytree365/laravel-gedcom/src\Utils\exporter\Indi\Alia.php does not comply with psr-4 autoloading standard. Skipping.                                                                                Class FamilyTree365\LaravelGedcom\Utils\Exporter\Indi\Anci located in D:/LARAGON/www/laravel-gedcom/vendor/familytree365/laravel-gedcom/src\Utils\exporter\Indi\Anci.php does not comply with psr-4 autoloading standard. Skipping.                                                                                Class FamilyTree365\LaravelGedcom\Utils\Exporter\Indi\Asso located in D:/LARAGON/www/laravel-gedcom/vendor/familytree365/laravel-gedcom/src\Utils\exporter\Indi\Asso.php does not comply with psr-4 autoloading standard. Skipping.                                                                                Class FamilyTree365\LaravelGedcom\Utils\Exporter\Indi\Desi located in D:/LARAGON/www/laravel-gedcom/vendor/familytree365/laravel-gedcom/src\Utils\exporter\Indi\Desi.php does not comply with psr-4 autoloading standard. Skipping.                                                                                Class FamilyTree365\LaravelGedcom\Utils\Exporter\Indi\Even\Plac located in D:/LARAGON/www/laravel-gedcom/vendor/familytree365/laravel-gedcom/src\Utils\exporter\Indi\Even\Plac.php does not comply with psr-4 autoloading standard. Skipping.                                                                                Class FamilyTree365\LaravelGedcom\Utils\Exporter\Indi\Even located in D:/LARAGON/www/laravel-gedcom/vendor/familytree365/laravel-gedcom/src\Utils\exporter\Indi\Even.php does not comply with psr-4 autoloading standard. Skipping.                                                                                Class FamilyTree365\LaravelGedcom\Utils\Exporter\Indi\Lds located in D:/LARAGON/www/laravel-gedcom/vendor/familytree365/laravel-gedcom/src\Utils\exporter\Indi\Lds.php does not comply with psr-4 autoloading standard. Skipping.                                                                                Class FamilyTree365\LaravelGedcom\Utils\Exporter\Indi\Name\Fone located in D:/LARAGON/www/laravel-gedcom/vendor/familytree365/laravel-gedcom/src\Utils\exporter\Indi\Name\Fone.php does not comply with psr-4 autoloading standard. Skipping.                                                                                Class FamilyTree365\LaravelGedcom\Utils\Exporter\Indi\Name\Romn located in D:/LARAGON/www/laravel-gedcom/vendor/familytree365/laravel-gedcom/src\Utils\exporter\Indi\Name\Romn.php does not comply with psr-4 autoloading standard. Skipping.                                                                                Class FamilyTree365\LaravelGedcom\Utils\Exporter\Indi\Name located in D:/LARAGON/www/laravel-gedcom/vendor/familytree365/laravel-gedcom/src\Utils\exporter\Indi\Name.php does not comply with psr-4 autoloading standard. Skipping.                                                                                Class FamilyTree365\LaravelGedcom\Utils\Exporter\Indi\Subm located in D:/LARAGON/www/laravel-gedcom/vendor/familytree365/laravel-gedcom/src\Utils\exporter\Indi\Subm.php does not comply with psr-4 autoloading standard. Skipping.                                                                                Class FamilyTree365\LaravelGedcom\Utils\Exporter\Note located in D:/LARAGON/www/laravel-gedcom/vendor/familytree365/laravel-gedcom/src\Utils\exporter\Note.php does not comply with psr-4 autoloading standard. Skipping.                                                                                Class FamilyTree365\LaravelGedcom\Utils\Exporter\NoteRef located in D:/LARAGON/www/laravel-gedcom/vendor/familytree365/laravel-gedcom/src\Utils\exporter\NoteRef.php does not comply with psr-4 autoloading standard. Skipping.                                                                                Class FamilyTree365\LaravelGedcom\Utils\Exporter\Obje located in D:/LARAGON/www/laravel-gedcom/vendor/familytree365/laravel-gedcom/src\Utils\exporter\Obje.php does not comply with psr-4 autoloading standard. Skipping.                                                                                Class FamilyTree365\LaravelGedcom\Utils\Exporter\ObjeRef\File located in D:/LARAGON/www/laravel-gedcom/vendor/familytree365/laravel-gedcom/src\Utils\exporter\ObjeRef\File.php does not comply with psr-4 autoloading standard. Skipping.                                                                                Class FamilyTree365\LaravelGedcom\Utils\Exporter\ObjeRef located in D:/LARAGON/www/laravel-gedcom/vendor/familytree365/laravel-gedcom/src\Utils\exporter\ObjeRef.php does not comply with psr-4 autoloading standard. Skipping.                                                                                Class FamilyTree365\LaravelGedcom\Utils\Exporter\Phon located in D:/LARAGON/www/laravel-gedcom/vendor/familytree365/laravel-gedcom/src\Utils\exporter\Phon.php does not comply with psr-4 autoloading standard. Skipping.                                                                                Class FamilyTree365\LaravelGedcom\Utils\Exporter\Refn located in D:/LARAGON/www/laravel-gedcom/vendor/familytree365/laravel-gedcom/src\Utils\exporter\Refn.php does not comply with psr-4 autoloading standard. Skipping.                                                                                Class FamilyTree365\LaravelGedcom\Utils\Exporter\Repo located in D:/LARAGON/www/laravel-gedcom/vendor/familytree365/laravel-gedcom/src\Utils\exporter\Repo.php does not comply with psr-4 autoloading standard. Skipping.                                                                                Class FamilyTree365\LaravelGedcom\Utils\Exporter\RepoRef located in D:/LARAGON/www/laravel-gedcom/vendor/familytree365/laravel-gedcom/src\Utils\exporter\RepoRef.php does not comply with psr-4 autoloading standard. Skipping.                                                                                Class FamilyTree365\LaravelGedcom\Utils\Exporter\Sour\Data\Even located in D:/LARAGON/www/laravel-gedcom/vendor/familytree365/laravel-gedcom/src\Utils\exporter\Sour\Data\Even.php does not comply with psr-4 autoloading standard. Skipping.                                                                                Class FamilyTree365\LaravelGedcom\Utils\Exporter\Sour\Data located in D:/LARAGON/www/laravel-gedcom/vendor/familytree365/laravel-gedcom/src\Utils\exporter\Sour\Data.php does not comply with psr-4 autoloading standard. Skipping.                                                                                Class FamilyTree365\LaravelGedcom\Utils\Exporter\Sour\Repo located in D:/LARAGON/www/laravel-gedcom/vendor/familytree365/laravel-gedcom/src\Utils\exporter\Sour\Repo.php does not comply with psr-4 autoloading standard. Skipping.                                                                                Class FamilyTree365\LaravelGedcom\Utils\Exporter\Sour located in D:/LARAGON/www/laravel-gedcom/vendor/familytree365/laravel-gedcom/src\Utils\exporter\Sour.php does not comply with psr-4 autoloading standard. Skipping.                                                                                Class FamilyTree365\LaravelGedcom\Utils\Exporter\SourRef\Even located in D:/LARAGON/www/laravel-gedcom/vendor/familytree365/laravel-gedcom/src\Utils\exporter\SourRef\Even.php does not comply with psr-4 autoloading standard. Skipping.                                                                                Class FamilyTree365\LaravelGedcom\Utils\Exporter\SourRef located in D:/LARAGON/www/laravel-gedcom/vendor/familytree365/laravel-gedcom/src\Utils\exporter\SourRef.php does not comply with psr-4 autoloading standard. Skipping.                                                                                Class FamilyTree365\LaravelGedcom\Utils\Exporter\Subm located in D:/LARAGON/www/laravel-gedcom/vendor/familytree365/laravel-gedcom/src\Utils\exporter\Subm.php does not comply with psr-4 autoloading standard. Skipping.                                                                                Class FamilyTree365\LaravelGedcom\Utils\Exporter\Subn located in D:/LARAGON/www/laravel-gedcom/vendor/familytree365/laravel-gedcom/src\Utils\exporter\Subn.php does not comply with psr-4 autoloading standard. Skipping.

Same problem as in https://github.com/liberu-genealogy/laravel-gedcom/issues/2

We forgot to update README.md
composer require laravel-liberu/laravel-gedcom


Add field to ValidatorInfo

Codecov Report

Merging #439 (f967f3e) into main (e0008e9) will decrease coverage by 0.22%.
The diff coverage is 75.75%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #439      +/-   ##
==========================================
- Coverage   95.50%   95.28%   -0.22%
==========================================
  Files          90       90
  Lines       10735    10663      -72
  Branches       10       22      +12
==========================================
- Hits        10252    10160      -92
- Misses        482      500      +18
- Partials        1        3       +2

Impacted Files
Coverage Δ

src/validators/typed_dict.rs
98.22% <ø> (-0.73%)
:arrow_down:

pydantic_core/core_schema.py
96.54% <74.19%> (-2.79%)
:arrow_down:

src/validators/function.rs
99.43% <100.00%> (+<0.01%)
:arrow_up:

src/validators/generator.rs
91.90% <100.00%> (+0.04%)
:arrow_up:

src/validators/mod.rs
98.73% <100.00%> (+<0.01%)
:arrow_up:

... and 1 file with indirect coverage changes

Continue to review full report in Codecov by Sentry.

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

please review


patternize specification.yml and openapi-validator.yml

so that properties can be overwritten by the values.yml

 patternize specification.yml and openapi-validator.yml light-rest-4j master


requirements.txt

Hello, may I ask why this file "requirements.txt" is not exist?

@Vanilla99
Hi!
Thank you for this issue! Of course, I forgot about this file because I use conda and for some reason I decided that environment.yml file would be enough. I will add requirements.txt soon
Regards

And here it is:
https://github.com/VladimirSinitsin/person_reid_yolo/commit/effe0bc229dc85bf27f7bf9b5dbdb5018cf97a36
Please check if everything is all right. If there are problems, please resume this issue. At this point, I'm closing it down.


Activating scene in Clip V2 API

Question:
How do you activate a scene using the Clip v2 API?
In the v1 API, I know you can activate a scene by using:
var command = new SceneCommand {Scene = "xxxxxxxx"}
await _client.SendGroupCommandAsync(command, groupId)

You can do this:
UpdateScene req = new UpdateScene()
{
  Recall = new Recall() {  Action = "active"}
};
var result = await localHueClient.UpdateSceneAsync(id, req);

In the next update this will be made more typesafe:
Recall = new Recall() {  Action =  SceneRecallAction.active }

You can use the Hue Migration Guide to see how things work with the V2 API: https://developers.meethue.com/develop/hue-api-v2/migration-guide-to-the-new-hue-api/#Scenes


Fix workdir cache invalidation

fixes #29950
@justincormack @yongtang
Signed-off-by: Tonis Tiigi<EMAIL_ADDRESS>

LGTM if janky is happy

LGTM

Thanks @tonistiigi. It looks that when b.commit() is invoked, it actually used the Cmd from the container (associated with the container.ID), which is from b.docker.ContainerCreate(). While searching for the cache use the other one. I think the PR fix addressed the issue.
On a separate note, I feel like the context of the workdir has been changed. Maybe in the future we could think about if there are other ways for workdir?

@yongtang Yes, definitely not obvious. There is ContainerConfig and Config. For builder case they only seem to differ by Cmd. Cache is based on ContainerConfig (needs to match the command of current command) but the parameter for b.commit() is Config.Cmd.


Remove Manifest

Could you release a new version with this?

https://github.com/JuliaRegistries/General/pull/103791 needs a merge


generic.mo missing

build fails with the following message
Building qr...
Build failed.  Glad to see this repo getting some attention, but I have not yet finished my implementation! :)


Ft/load needed cards (WIP)

Title

Changes 👷♀

- item 1
How to test 🧪

- step 1 ...

Closing old PR (cleaning up PR tab).


DS-3689 Addition of facet dates to DiscoverQuery

JIRA ticket
https://jira.duraspace.org/projects/DS/issues/DS-3689
The addition of date facets can be done similarly to "normal" facet fields

To illustrate the purpose of the type of facet, maybe we should rewrite the processing of the current date facets? E.g. https://github.com/DSpace/DSpace/blob/dspace-6.2/dspace-xmlui/src/main/java/org/dspace/app/xmlui/aspect/discovery/SidebarFacetsTransformer.java#L350


Make smaller publish version

Need to think and try something to get ready application with less files.

Fixed and done in latest release v1.15