[Strategic Goal] Audit existing documentation and look for missing information

Audit existing documentation from TODO resources and look for missing information (e.g set up a standard roadmap when someone creates a new use case)

Adding resources to TODO Website
OSPO Case Study Submission Guidelines
TODO Guides Contributing Guidelines
TODO Whitepaper Guidelines

Action items

[x] Submit PRs for each of the documents to update the info
[x] Create new documentation for other content that is missing

New documentation/onboarding guides added in https://todogroup.org/community/
If a new audit is needed for 2023. please open a new issue.


fix: Explore quick links followup

Thank you for your contribution to the KodaDot - One Stop Shop for Polkadot NFTs.
👇 __ Let's make a quick check before the contribution.
PR Type

[x] Bugfix
[x] Feature
[ ] Refactoring

Needs Design check

@exezbcz please review

Context

[x] Closes #7003
[ ] Requires deployment <snek/rubick/worker>

Did your issue had any of the "$" label on it?

[x] My DOT address: Payout

Screenshot 📸

[x] My fix has changed UI

Copilot Summary

🤖 Generated by Copilot at 9b6e3d0
Improved the navbar explore options by adding more spacing, disabling unused features, and showing chain names with labels. Added new classes to global and main navigation styles to support the labels. Modified components/navbar/NavbarExploreOptions.vue, styles/global.scss, and styles/layouts/_main-navigation.scss.

🤖 Generated by Copilot at 9b6e3d0

We are the rebels of the web, we defy the status quo
We explore the chains of doom, with the beta labels on
We align the signs of fate, with the k-shade of our soul
We close the gates of hell, when the mobile nav is gone

@prury for mobile bug master 👀


Web Automation sample not working

I tried this running this sample code:
r.init()
r.url('https://www.google.com')
r.type('//*[@name="q"]', 'decentralization[enter]')
print(r.read('result-stats'))
r.close()
It only works up to typing decentralization(not including [enter])

Have exactly the same problem. Get the output:
[RPA][ERROR] - following happens when starting TagUI...

[RPA][ERROR] - use init() before using url()
[RPA][ERROR] - use init() before using type()
[RPA][ERROR] - use init() before using read()

[RPA][ERROR] - use init() before using snap()
[RPA][ERROR] - use init() before using close()

False

Have exactly the same problem. Get the output:
[RPA][ERROR] - following happens when starting TagUI...

[RPA][ERROR] - use init() before using url()
[RPA][ERROR] - use init() before using type()
[RPA][ERROR] - use init() before using read()

[RPA][ERROR] - use init() before using snap()
[RPA][ERROR] - use init() before using close()

False

Hi RPA for Python users, 🅗🅐🅟🅟🅨 ②⓪②①!
It has been many months since I last worked on this personal side project. Just want to shout out that this project is very much alive, and I hope to look into the 30+ issues raised since July (and bug-fixes if required) soon when I get a moment again.
Below are details if you are interested, why I'm away past few months and why I believe my darkest days are over 🍀🤞🏻🙏🏻

Since May last year, I've stopped all work to juggle with my mum's critical illness, taking care of my toddler, and doing housework chores like cleaning and cooking. TBH, my wife and I felt that taking care of a baby and giving her the best nutrition (nursing and home-cooked organic food) and care requires at least 1.5 full-time headcount. There is no life to speak of, other than trying to stay afloat with baby care needs, and keep finding alternative ways to treat my mum, where there're some wins.
Eg importing soy-based tube feeds from Netherlands / Germany / Australia --> after switching away from milk-based tube feeds for 2 weeks she stops requiring dialysis. She started requiring 3x a week dialysis for more than 3 months, after admitting to the hospital. Also, applying herbs like mashed garlic or diced onions to her feet somehow consistently improve her breathing and lung function. Have to keep trying alternative healing methods when her recovery keeps hitting plateau in hospital.
She has been discharged from the hospital a month ago and recovering at home, though very slowly. A longterm medication seems to be one of the contributing causes for her condition. After stopping it, there seems to be improvement to her breathing capacity. She is still bed-bound, but over the course of the year I hope she'll regain strength to move about, and hopefully lungs to recover sufficiently to not require oxygen tank support through a tracheal mask (a hole through her throat).

Since November, I've gone back to work at AI Singapore, a government-funded programme to accelerate AI in Singapore. I'm with Product Engineering team, focusing on RPA and TagUI (open-source RPA tool), which RPA for Python is a wrapper for. There are pretty interesting stuffs on TagUI 2021 roadmap. 2020 was the year which my family was going to move to the UK and work, after I receive its tier 1 exceptional tech talent visa. Then everything changed with the virus outbreak, and my mum's illness. The best thing that happened to me in 2020 was being able to go back to work at AI Singapore - I'm grateful.
I've just hired someone to help with housework, cooking and supporting my wife with baby care. I hope this new arrangement will allow me to deliver on my work at AI Singapore, and soon be able to reply countless friends' messages which circumstances leave me with no choice but go missing for months, and then look into the issues raised here!
Eg of the cost of best-in-class nutrition standard researched and set by wife. Baby just felt restless and broke her plate. Even Corelle's break-resistant plate breaks. Why not use plastic plate? Cuz plastic can leech toxins to the food on it. Why not use Silicon plate? Cuz there is no white silicon materials for plate. Why white? Cuz that helps to improve visibility of the food instead of contrasting against some pink colour or some other colours. I would be spending much time clearing up the mess of 70 over pieces of plate fragments, while baby gets nursed to calm down, if not for our newfound helper.
That's why I feel like my darkest days are over and now seeing glimpses of light at the end of the tunnel.

My vision for RPA for Python remains - I would like it to be the go-to Python package for RPA.
A best-in-class tool in Python users toolbox which you combine with other cool packages to build amazing stuffs.

Hi RPA for Python users, 🅗🅐🅟🅟🅨 ②⓪②①!
It has been many months since I last worked on this personal side project. Just want to shout out that this project is very much alive, and I hope to look into the 30+ issues raised since July (and bug-fixes if required) soon when I get a moment again.
Below are details if you are interested, why I'm away past few months and why I believe my darkest days are over 🍀🤞🏻🙏🏻

Since May last year, I've stopped all work to juggle with my mum's critical illness, taking care of my toddler, and doing housework chores like cleaning and cooking. TBH, my wife and I felt that taking care of a baby and giving her the best nutrition (nursing and home-cooked organic food) and care requires at least 1.5 full-time headcount. There is no life to speak of, other than trying to stay afloat with baby care needs, and keep finding alternative ways to treat my mum, where there're some wins.
Eg importing soy-based tube feeds from Netherlands / Germany / Australia --> after switching away from milk-based tube feeds for 2 weeks she stops requiring dialysis. She started requiring 3x a week dialysis for more than 3 months, after admitting to the hospital. Also, applying herbs like mashed garlic or diced onions to her feet somehow consistently improve her breathing and lung function. Have to keep trying alternative healing methods when her recovery keeps hitting plateau in hospital.
She has been discharged from the hospital a month ago and recovering at home, though very slowly. A longterm medication seems to be one of the contributing causes for her condition. After stopping it, there seems to be improvement to her breathing capacity. She is still bed-bound, but over the course of the year I hope she'll regain strength to move about, and hopefully lungs to recover sufficiently to not require oxygen tank support through a tracheal mask (a hole through her throat).

Since November, I've gone back to work at AI Singapore, a government-funded programme to accelerate AI in Singapore. I'm with Product Engineering team, focusing on RPA and TagUI (open-source RPA tool), which RPA for Python is a wrapper for. There are pretty interesting stuffs on TagUI 2021 roadmap. 2020 was the year which my family was going to move to the UK and work, after I receive its tier 1 exceptional tech talent visa. Then everything changed with the virus outbreak, and my mum's illness. The best thing that happened to me in 2020 was being able to go back to work at AI Singapore - I'm grateful.
I've just hired someone to help with housework, cooking and supporting my wife with baby care. I hope this new arrangement will allow me to deliver on my work at AI Singapore, and soon be able to reply countless friends' messages which circumstances leave me with no choice but go missing for months, and then look into the issues raised here!
Eg of the cost of best-in-class nutrition standard researched and set by wife. Baby just felt restless and broke her plate. Even Corelle's break-resistant plate breaks. Why not use plastic plate? Cuz plastic can leech toxins to the food on it. Why not use Silicon plate? Cuz there is no white silicon materials for plate. Why white? Cuz that helps to improve visibility of the food instead of contrasting against some pink colour or some other colours. I would be spending much time clearing up the mess of 70 over pieces of plate fragments, while baby gets nursed to calm down, if not for our newfound helper.
That's why I feel like my darkest days are over and now seeing glimpses of light at the end of the tunnel.

My vision for RPA for Python remains - I would like it to be the go-to Python package for RPA.
A best-in-class tool in Python users toolbox which you combine with other cool packages to build amazing stuffs.

Have exactly the same problem. Get the output:
[RPA][ERROR] - following happens when starting TagUI...

[RPA][ERROR] - use init() before using url()
[RPA][ERROR] - use init() before using type()
[RPA][ERROR] - use init() before using read()

[RPA][ERROR] - use init() before using snap()
[RPA][ERROR] - use init() before using close()

False

I didn't encounter this issue, maybe you forgot r.init()? The issue I've raised is more focused on the '[enter]' part. In the sample it should have typed decentralized and press enter to search, it doesn't work like that in my experience. It only does the typing then nothing else happened.

Have exactly the same problem. Get the output:
[RPA][ERROR] - following happens when starting TagUI...

[RPA][ERROR] - use init() before using url()
[RPA][ERROR] - use init() before using type()
[RPA][ERROR] - use init() before using read()

[RPA][ERROR] - use init() before using snap()
[RPA][ERROR] - use init() before using close()

False

I didn't encounter this issue, maybe you forgot r.init()? The issue I've raised is more focused on the '[enter]' part. In the sample it should have typed decentralized and press enter to search, it doesn't work like that in my experience. It only does the typing then nothing else happened.

Hi @Gureeeenn and @Thinkcrafter, I've made some new updates to this package over the weekend.
Can you try if the errors still persist after upgrading to v1.31 with pip install rpa --upgrade?


⚠ Jenkins Plugins Artifactory has degraded performance

In 10c294b, Jenkins Plugins Artifactory (https://get.jenkins.io/plugins/artifactory/) experienced degraded performance:

HTTP code: 200
Response time: 1189 ms

Resolved: Jenkins Plugins Artifactory performance has improved in 3736b49 after 25 minutes.


Upgrade to Vuetify 3

Due to EOL of Vue 2 an upgrade of Vue to version 3 will come up. This would force us to switch to Vuetify 3 even tough its LTS period is a bit longer (January 23rd, 2025) than for Vue 2.
Should be done after or in combination with #350.

Hi team,
As explained in #350, I'd personally tackle this one after it as Vuetify3 still lacks some of the functionalities that were present inside Vuetify2. It even seems that some people changed their mind and used, for example, Quasar instead of Vuetify because of that. (For example, see this discussion on official Vuetify Github

meanwhile Vuetify3 re-adds more and more components, that were present in Vuetify2 and were currently marked as experimental (see 3.4 release https://vuetifyjs.com/en/getting-started/release-notes/#user-content-release-notes)


Reloading of nif modules

After a nif module is reloaded, all the nif functions are overwritten by elixir placeholders.
defmodule test_nif do

  require Logger

  @on_load :init

  def init() do
    :erlang.load_nif("./priv/test_nif", 0)
    :ok
  end

  def test_a() do
    Logger.error "NIF library not loaded"
  end

end

After reloading test_a.beam, test_nif.test_a() will call the placeholder instead of nif functions.
One way I can think of to solve the glitch is to add an _on_reprise_reload() function to test_nif:
def _on_reprise_reload() do
  init()
end

And have reprise call the function after reloading the module
But there might be better ways.

Hi!
I never worked with NIFs. So what I say is a good practice which comes to mind when handling corner cases like this one - assuming that there might be more similar corner cases around :)
More elegant solution would be to call some configured function on a reloaded NIF module (if it's exported). Name of such function - like _on_reprise_reload would go to your app config.exs.
The question is: how to detect that a module contains NIFs?
Are you able to come up with a prototype PR?
cheers,
W.

Hi, Thanks for your advice!
I've come up with a simple fix to support a "general reload hook", not made for NIFs. In that case people can do all the things in the hook function, I think it's more general and useful than targeting NIF use cases specifically.
Didn't come up with a unit test yet but I already use it in my project and it worked great.

Hi, turns out there is a built-in reload feature for erlang nifs.
Just implement the 'load', 'upgrade', 'unload' callbacks for ERL_NIF_INIT macro and erlang handles nif reload for you when the module is reloaded, there is no need to call load_nif() again in _reprise_on_reload()
That said, maybe there are other aspects people can use a _reprise_on_reload() callback on reprise. I kept reload mechanism in my project and worked fine.

Hello!
I hope you don't mind this project evolving rather slowly.. :)
I think you're right that _reprise_on_reload() can be useful. I see no reason in blocking this going to master which then gets "hexified" with all good implications of it.
Still I'm tempted to have a simple regression test for this, as I said previously in the pull request comment. Do you have an idea or a skeleton of how such test for a callback might work?
cheers,
W.

Hi,
Sorry for the late reply! I was busy with the day jobs.
I've written a simple test to test calling hooks, not a very comprehensive one but I think it's better than nothing.
cheers,
Lei


SPECS: Update qemu to 5.2.0

The current version 4.2.0 seems broken. Qemu can not
boot any image and gives the following error message.
"SeaBIOS (version rel-1.12.0-59-gc9ba5276e321-
prebuilt.qemu.orgqemu-system-x86_64:
/usr/src/mariner/BUILD/qemu-4.2.0/include/qemu/int128.h:22:
int128_get64: Assert. Aborted"
This patch updates the version to 5.2.0
which is the default in CentOS 8.
Signed-off-by: Muminul Islam<EMAIL_ADDRESS>
Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

[x] The toolchain has been rebuilt successfully (or no changes were made to it)
[x] The toolchain/worker package manifests are up-to-date
[x] Any updated packages successfully build (or no packages were changed)
[x] Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
[x] All package sources are available
[x] cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/tools/cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
[x] LICENSE-MAP files are up-to-date (./SPECS/LICENSES-AND-NOTICES/data/licenses.json, ./SPECS/LICENSES-AND-NOTICES/LICENSES-MAP.md, ./SPECS/LICENSES-AND-NOTICES/LICENSE-EXCEPTIONS.PHOTON)
[x] All source files have up-to-date hashes in the *.signatures.json files
[x] sudo make go-tidy-all and sudo make go-test-coverage pass
[x] Documentation has been updated to match any changes to the build system
[x] Ready to merge

Summary

What does the PR accomplish, why was it needed?

This version upgrade was necessary for Qemu based mariner host that is planned for customer use. Previous version 4.2.0
was buggy. This version is the default for Centos 8 that does not break the qemu functionality

Change Log

No CVE fixes in this PR. Kept some CVE fixes from the older version that are still applicable

Does this affect the toolchain?

NO
Associated issues

N/A

Links to CVEs

N/A

Test Methodology

Pipeline build id:  PR Build
Built locally using  the following command
sudo make build-packages -j$(nproc) CONFIG_FILE= REBUILD_TOOLS=y PACKAGE_IGNORE_LIST="openjdk8" RUN_CHECK=y  PACKAGE_BUILD_LIST="qemu-kvm" PACKAGE_REBUILD_LIST="qemu-kvm"
sudo make go-tidy-all
sudo make go-test-coverage

Please fill out the PR template and indicate how you've checked the package builds. Usually it's a local build of the package with the RUN_CHECK=y argument. The tests should still be passing - you can check that by looking for the execution of the %check section in the build logs. The build itself will succeed if only the tests fail.

How do I test? using rpmbuild? Could you please share the details?

Please fill out the PR template and indicate how you've checked the package builds. Usually it's a local build of the package with the RUN_CHECK=y argument. The tests should still be passing - you can check that by looking for the execution of the %check section in the build logs. The build itself will succeed if only the tests fail.

How do I test? using rpmbuild? Could you please share the details?

You just need to run the build with RUN_CHECK=y: make build-packages [other_args] RUN_CHECK=y. Then check the package build logs under build/logs/pkggen/rpmbuilding for the results from the %check section.

time="2021-09-20T13:15:38-07:00" level=debug msg="Interrupting job (failfast)."
time="2021-09-20T13:15:38-07:00" level=debug msg="RESULTS    : PASS 15 | ERROR 1 | FAIL 0 | SKIP 19 | WARN 0 | INTERRUPT 0 | CANCEL 4"
time="2021-09-20T13:15:38-07:00" level=debug msg="JOB TIME   : 41.97 s"
time="2021-09-20T13:15:38-07:00" level=debug msg="make[1]: *** [/usr/src/mariner/BUILD/qemu-5.2.0/tests/Makefile.include:125: check-acceptance] Error 9"
time="2021-09-20T13:15:38-07:00" level=debug msg="make[1]: Leaving directory '/usr/src/mariner/BUILD/qemu-5.2.0/build'"
time="2021-09-20T13:15:38-07:00" level=debug msg="make: *** [GNUmakefile:11: check-acceptance] Error 2"
time="2021-09-20T13:15:38-07:00" level=debug msg="One (or more) tests failed. Check log for further details"
time="2021-09-20T13:15:38-07:00" level=debug msg="+ '[' 2 -ne 0 ']'"
time="2021-09-20T13:15:38-07:00" level=debug msg="+ testsPassed=false"
time="2021-09-20T13:15:38-07:00" level=debug msg="+ '[' false = false ']'"
time="2021-09-20T13:15:38-07:00" level=debug msg="+ echo 'One (or more) tests failed. Check log for further details'"
time="2021-09-20T13:15:38-07:00" level=debug msg="+ exit 1"

make check-tcg failed
time="2021-09-20T13:14:46-07:00" level=debug msg="+ make check-tcg" time="2021-09-20T13:14:46-07:00" level=debug msg="changing dir to build for make \"check-tcg\"..." time="2021-09-20T13:14:46-07:00" level=debug msg="make[1]: Entering directory '/usr/src/mariner/BUILD/qemu-5.2.0/build'" time="2021-09-20T13:14:46-07:00" level=debug msg="  BUILD   TCG tests for x86_64-softmmu" time="2021-09-20T13:14:46-07:00" level=debug msg="  BUILD   x86_64-softmmu guest-tests with cc" time="2021-09-20T13:14:46-07:00" level=debug msg="/usr/bin/ld: memory: warning: allocated section.notes' not in segment"
time="2021-09-20T13:14:46-07:00" level=debug msg="/usr/bin/ld: hello: warning: allocated section .notes' not in segment" time="2021-09-20T13:14:46-07:00" level=debug msg="  RUN     TCG tests for x86_64-softmmu" time="2021-09-20T13:14:46-07:00" level=debug msg="  BUILD   x86_64-softmmu guest-tests with cc" time="2021-09-20T13:14:46-07:00" level=debug msg="  RUN     tests for x86_64" time="2021-09-20T13:14:46-07:00" level=debug msg="  TEST    memory on x86_64" time="2021-09-20T13:14:46-07:00" level=debug msg="qemu-system-x86_64: Error loading uncompressed kernel without PVH ELF Note" time="2021-09-20T13:14:46-07:00" level=debug msg="make[3]: *** [../Makefile.target:162: run-memory] Error 1" time="2021-09-20T13:14:46-07:00" level=debug msg="make[2]: *** [/usr/src/mariner/BUILD/qemu-5.2.0/tests/tcg/Makefile.qemu:85: run-guest-tests] Error 2" time="2021-09-20T13:14:46-07:00" level=debug msg="make[1]: *** [/usr/src/mariner/BUILD/qemu-5.2.0/tests/Makefile.include:61: run-tcg-tests-x86_64-softmmu] Error 2" time="2021-09-20T13:14:46-07:00" level=debug msg="make[1]: Leaving directory '/usr/src/mariner/BUILD/qemu-5.2.0/build'" time="2021-09-20T13:14:46-07:00" level=debug msg="make: *** [GNUmakefile:11: check-tcg] Error 2"

make check-tcg failed
time="2021-09-20T13:14:46-07:00" level=debug msg="+ make check-tcg"
time="2021-09-20T13:14:46-07:00" level=debug msg="changing dir to build for make "check-tcg"..."
time="2021-09-20T13:14:46-07:00" level=debug msg="make[1]: Entering directory '/usr/src/mariner/BUILD/qemu-5.2.0/build'"
time="2021-09-20T13:14:46-07:00" level=debug msg=" BUILD TCG tests for x86_64-softmmu"
time="2021-09-20T13:14:46-07:00" level=debug msg=" BUILD x86_64-softmmu guest-tests with cc"
time="2021-09-20T13:14:46-07:00" level=debug msg="/usr/bin/ld: memory: warning: allocated section .notes' not in segment" time="2021-09-20T13:14:46-07:00" level=debug msg="/usr/bin/ld: hello: warning: allocated section .notes' not in segment"
time="2021-09-20T13:14:46-07:00" level=debug msg=" RUN TCG tests for x86_64-softmmu"
time="2021-09-20T13:14:46-07:00" level=debug msg=" BUILD x86_64-softmmu guest-tests with cc"
time="2021-09-20T13:14:46-07:00" level=debug msg=" RUN tests for x86_64"
time="2021-09-20T13:14:46-07:00" level=debug msg=" TEST memory on x86_64"
time="2021-09-20T13:14:46-07:00" level=debug msg="qemu-system-x86_64: Error loading uncompressed kernel without PVH ELF Note"
time="2021-09-20T13:14:46-07:00" level=debug msg="make[3]: *** [../Makefile.target:162: run-memory] Error 1"
time="2021-09-20T13:14:46-07:00" level=debug msg="make[2]: *** [/usr/src/mariner/BUILD/qemu-5.2.0/tests/tcg/Makefile.qemu:85: run-guest-tests] Error 2"
time="2021-09-20T13:14:46-07:00" level=debug msg="make[1]: *** [/usr/src/mariner/BUILD/qemu-5.2.0/tests/Makefile.include:61: run-tcg-tests-x86_64-softmmu] Error 2"
time="2021-09-20T13:14:46-07:00" level=debug msg="make[1]: Leaving directory '/usr/src/mariner/BUILD/qemu-5.2.0/build'"
time="2021-09-20T13:14:46-07:00" level=debug msg="make: *** [GNUmakefile:11: check-tcg] Error 2"

It looks like the tests have failed. Please check if it's a regression. If not, fixing the failure is out of scope for this PR. If the tests used to pass, then please check what's wrong and fix them, if possible. If it's going to turn out that the test has no chances of passing due to how we want Mariner to be configured, or due to how our build environment is set up (and there's no easy way to remedy that), then please disable that particular test.

@PawelWMS fixed now.

QEMU was upgraded to a more recent version in main/2.0.  Closing this PR


nlmg MySQLIntegrityConstraintViolationException

2015-05-28 12:18:37 [INFO] ABC issued server command: /nlmg G1 G2
2015-05-28 12:18:37 [WARN] com.mysql.jdbc.exceptions.jdbc4.MySQLIntegrityConstraintViolationException: Duplicate entry 'UUID_BCD' for key 'uq_meber_faction'
2015-05-28 12:18:37 [WARN]      at sun.reflect.GeneratedConstructorAccessor191.newInstance(Unknown Source)
2015-05-28 12:18:37 [WARN]      at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
2015-05-28 12:18:37 [WARN]      at java.lang.reflect.Constructor.newInstance(Constructor.java:422)
2015-05-28 12:18:37 [WARN]      at com.mysql.jdbc.Util.handleNewInstance(Util.java:407)
2015-05-28 12:18:37 [WARN]      at com.mysql.jdbc.Util.getInstance(Util.java:382)
2015-05-28 12:18:37 [WARN]      at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1039)
2015-05-28 12:18:37 [WARN]      at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3593)
2015-05-28 12:18:37 [WARN]      at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3525)
2015-05-28 12:18:37 [WARN]      at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1986)
2015-05-28 12:18:37 [WARN]      at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2140)
2015-05-28 12:18:37 [WARN]      at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2626)
2015-05-28 12:18:37 [WARN]      at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:2111)
2015-05-28 12:18:37 [WARN]      at com.mysql.jdbc.PreparedStatement.execute(PreparedStatement.java:1362)
2015-05-28 12:18:37 [WARN]      at vg.civcraft.mc.namelayer.database.GroupManagerDao.addMember(GroupManagerDao.java:488)
2015-05-28 12:18:37 [WARN]      at vg.civcraft.mc.namelayer.group.groups.PrivateGroup.addMember(PrivateGroup.java:31)
2015-05-28 12:18:37 [WARN]      at vg.civcraft.mc.namelayer.GroupManager$1.run(GroupManager.java:98)
2015-05-28 12:18:37 [WARN]      at org.bukkit.craftbukkit.v1_8_R2.scheduler.CraftTask.run(CraftTask.java:71)
2015-05-28 12:18:37 [WARN]      at org.bukkit.craftbukkit.v1_8_R2.scheduler.CraftAsyncTask.run(CraftAsyncTask.java:53)
2015-05-28 12:18:37 [WARN]      at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
2015-05-28 12:18:37 [WARN]      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
2015-05-28 12:18:37 [WARN]      at java.lang.Thread.run(Thread.java:745)
There was about 50 of these that triggered in a row.

weird bug.  I have it if the player is on the group then remove them first and readd them.  Not sure why it didnt work this time.  Might be possible this group was messed up from citadel 2.0.  Was this the only time this has happened?

The player tried it twice today and both times lit the console up with a
ton of this exception spew, one for each player.
On Thu, May 28, 2015 at 5:10 PM, rourke750<EMAIL_ADDRESS>wrote:

weird bug. I have it if the player is on the group then remove them first
and readd them. Not sure why it didnt work this time. Might be possible
this group was messed up from citadel 2.0. Was this the only time this has
happened?
—
Reply to this email directly or view it on GitHub
https://github.com/Civcraft/NameLayer/issues/108#issuecomment-106636906.

Can you check and see if both groups exist.  If the player merged the group
then he shouldnt have been able to do it twice.
On Thu, May 28, 2015 at 9:24 PM, erocs<EMAIL_ADDRESS>wrote:

The player tried it twice today and both times lit the console up with a
ton of this exception spew, one for each player.
On Thu, May 28, 2015 at 5:10 PM, rourke750<EMAIL_ADDRESS>wrote:

weird bug. I have it if the player is on the group then remove them first
and readd them. Not sure why it didnt work this time. Might be possible
this group was messed up from citadel 2.0. Was this the only time this
has
happened?
—
Reply to this email directly or view it on GitHub
<https://github.com/Civcraft/NameLayer/issues/108#issuecomment-106636906
.

—
Reply to this email directly or view it on GitHub
https://github.com/Civcraft/NameLayer/issues/108#issuecomment-106648271.

staged for tomorrow.
On Thu, May 28, 2015 at 8:29 PM rourke750<EMAIL_ADDRESS>wrote:

Can you check and see if both groups exist. If the player merged the group
then he shouldnt have been able to do it twice.
On Thu, May 28, 2015 at 9:24 PM, erocs<EMAIL_ADDRESS>wrote:

The player tried it twice today and both times lit the console up with a
ton of this exception spew, one for each player.
On Thu, May 28, 2015 at 5:10 PM, rourke750<EMAIL_ADDRESS>wrote:

weird bug. I have it if the player is on the group then remove them
first
and readd them. Not sure why it didnt work this time. Might be possible
this group was messed up from citadel 2.0. Was this the only time this
has
happened?
—
Reply to this email directly or view it on GitHub
<
https://github.com/Civcraft/NameLayer/issues/108#issuecomment-106636906
.

—
Reply to this email directly or view it on GitHub
<https://github.com/Civcraft/NameLayer/issues/108#issuecomment-106648271
.

—
Reply to this email directly or view it on GitHub
https://github.com/Civcraft/NameLayer/issues/108#issuecomment-106648980.

Status of this?

Status of this? I think #128 is related as well

seems resolved.

It may seem resolved, but really how often is /nlmg used?

very true, think we shoudl reopen adn try to reproduce?


Typo: it should be "an exception" instead of "a exception"

I believe the words "You can also use a exception filter ..." should have been written as "You can also use an exception filter ...".

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

ID: f8cde2a6-1c92-8b1e-a795-4b1e04510575
Version Independent ID: 3b8f6b0d-08a9-0730-3241-da241f8444b4
Content: try-catch (C# Reference)
Content Source: docs/csharp/language-reference/keywords/try-catch.md
Product: dotnet-csharp
GitHub Login: @BillWagner
Microsoft Alias: wiwagn

Thanks for the feedback @jwatkin. Yes, you're right! Would you like to submit a pull request to fix this? Our contributor guide has instructions on how to make quick fixes like that: https://docs.microsoft.com/en-us/contribute/#quick-edits-to-existing-documents.


Queue: make sure tasks are hidden and all actions make sense in the table

As we discussed during the planning, I don't think exposing tasks in the table, quick pick makes sense. E.g. remove action - we should be (at least first) be able to remove any experiment including queued, failed in the queue, etc, etc.
From the user perspective- they don't care about tasks, celery, etc ... how it's implemented etc. All that stuff should be hidden by the experiments table and actions on experiments.

[ ] Make sure that we show all experiments in the table
[ ] Make sure that same actions can be applied seamlessly to all of those experiments. E.g. I can pick a failed and successful experiment + a queued experiments and delete them (do we need DVC support for this)
[ ] DVC should be providing the same experience I think (cc @dberenbaum )
[ ] Review quick picks, etc - don't expose extra actions on the queue for now (e.g. we don't want to have two removes, etc).
[ ] Discuss why would we actually want to expose this information as an advanced scenario, etc and do a followup after that

LGTM!

Make sure that same actions can be applied seamlessly to all of those experiments. E.g. I can pick a failed and successful experiment + a queued experiments and delete them (do we need DVC support for this)

VS Code should only need to pass the experiment names to dvc exp remove and it should work:
$ dvc queue status
Task     Name        Created       Status
be372c8  taboo-trey  08:47 AM      Queued
f285967  sworn-cuss  08:47 AM      Failed
63ea1ab  regal-weft  Jan 06, 2023  Success

Worker status: 0 active, 0 idle

$ dvc exp remove taboo-trey sworn-cuss regal-weft
Removed experiments: taboo-trey,sworn-cuss,regal-weft

[Q] Do we want to hide dvc queue kill <exp>? Seems like we would want to provide two options with dvc queue stop:

Stop the current queue workers and leave the experiments currently being processed running.
Kill anything that is running and stop the queue workers.

@mattseddon are those two different questions? or one? I'm trying to better understand it, sorry .. :)

Things that are currently implemented

queue start (start queue workers)
queue stop (stop queue workers -> leaves any currently running queue tasks to complete)
queue kill (stop currently processing queue tasks, i.e experiments running in the queue - user is given all executing queue tasks as options)
remove queue tasks (remove groups of queue tasks, e.g success, failed, queued or all)

From OP: 4 will be removed.
Questions

should dvc queue stop --kill be added as an option to stop queue workers and any currently running queue tasks?
should 3 be removed or can it be left and renamed to dvc.killExperimentsRunningInQueue or dvc. stopExperimentsRunningInQueue?
should 3 be an all-or-nothing option to stop all currently executing queue tasks?

My take:

queue stop name is not clear. We should come up with an explicit name for this - Experiments: complete running and stop (or pause?)?
Queue start - Experiments: run queued
should 3 be an all-or-nothing option to stop all currently executing queue tasks? - I think yes, we should have "Experiments: stop all" and "Experiments: stop" (not only tasks, it means all running experiments - queued, temp dir, workspace). Later we can differentiate if there is a need. How is it different from delete / drop / remove though?
Means 1 is not needed, 3 - yes, can be removed (or replaced)
stop / remove / etc actions - there should be a way to select multiple exps and apply (via table and via quick pick (?))

Overall, it seems intimidating, even semantics of this.

My take:

queue stop name is not clear. We should come up with an explicit name for this - Experiments: complete running and stop (or pause?)?
Queue start - Experiments: run queued

User facing names are currently Stop the Experiments Queue & Start the Experiments Queue. Do we really want to try and hide the concept of the queue/queue workers?

should 3 be an all-or-nothing option to stop all currently executing queue tasks? - I think yes, we should have "Experiments: stop all" and "Experiments: stop" (not only tasks, it means all running experiments - queued, temp dir, workspace). Later we can differentiate if there is a need. How is it different from delete / drop / remove though?

There is currently no way to stop an experiment that is being run inside the workspace outside of the VS Code context (i.e user runs it through the terminal). There is also currently no link between the ID of the experiment running in the workspace and the process that we can stop to stop that experiment, we could try to proxy the process if there is 1 running experiment and 1 process but that could go horribly wrong. This will make mashing these two concepts together problematic.

stop / remove / etc actions - there should be a way to select multiple exps and apply (via table and via quick pick (?))

Remove action is implemented in both the table and a quick pick. The quick pick is about to be updated here: #3093. For stop we have a quick pick under the kill name for experiments running in/from the queue. We could add this functionality to the table. For previously stated reasons this will be more difficult for experiments not running in the queue.

Overall, it seems intimidating, even semantics of this.

I personally don't think that the concept the DVC team has put forwards/implemented for the queue is overly complicated or different from what I've seen elsewhere. I don't think we need to diverge too far from the semantics. I don't think we should go much further than integrating kill into the table and tweaking the name slightly to reflect stopping the experiment.

User facing names are currently Stop the Experiments Queue & Start the Experiments Queue. Do we really want to try and hide the concept of the queue/queue workers?

My main concern that atm it requires an explanation Stop the Experiments Queue is not self descriptive (I can't understand the semantics of it w/o reading the docs). It would be fine if we can add a description for example. Start the queue is better, but would it be even better to say "Run queued experiments" ... or Just have run all button / action?
I'm not trying to hide the queue as a term. Since we are queueing experiments it's fine that we use it in some ways and forms. What I'm trying to think about and optimize is that users immediately understand what each action does, they are not overwhelmed by the number of actions, etc.

There is currently no way to stop an experiment that is being run inside the workspace outside of the VS Code context (i.e user runs it through the terminal). There is also currently no link between the ID of the experiment running in the workspace and the process that we can stop to stop that experiment, we could try to proxy the process if there is 1 running experiment and 1 process but that could go horribly wrong. This will make mashing these two concepts together problematic.

Means that stop button doesn't work for these cases at all, even though we can show that experiment in the table? I thought that we had pid from DVC (and probably we can add it if needed)?
Anyways, even there are some limitations, we should strive for semantic generalization and simplicity I think.

There is currently no way to stop an experiment that is being run inside the workspace outside of the VS Code context (i.e user runs it through the terminal). There is also currently no link between the ID of the experiment running in the workspace and the process that we can stop to stop that experiment, we could try to proxy the process if there is 1 running experiment and 1 process but that could go horribly wrong. This will make mashing these two concepts together problematic.

Means that stop button doesn't work for these cases at all, even though we can show that experiment in the table? I thought that we had pid from DVC (and probably we can add it if needed)?

Yes, the stop button will not work under those circumstances. That is why I started hiding it for these cases in https://github.com/iterative/vscode-dvc/pull/3027. Whilst I was working on that change I tried to find a place where the PID for the process running experiments is exposed by DVC but I couldn't find one.

Should be ready for the next round of review


Add product bug and and remove flaky test from operator test

Signed-off-by: Tarun Kumar<EMAIL_ADDRESS>

Jenkins job failed due to product bug


So sad to see this, Bankex team. 😢
Hope you will do better with this code. Please don't drop it. It makes confusion in the community.

As a founder of this project, I would like to highly recommend to leave reference to up-to-date repo https://github.com/matter-labs/web3swift

It's a shame, guys. By deleting all the references and conversation you are confusing community.


Add support for the PostgreSQL 'empty' range that's distinct from the (,) infinite range

When mapping PostgreSQL empty range we are creating Range objects which is actually unbounded from both sides. The created range has exact internal structure that Range.integerRange("(infinity,infinity)") would have.
Here is the quote from documentation:

...
Notice that the final pattern is empty, which represents an empty range (a range that contains no points).

So it'll be sensible to align with this semantics in Java as well.
Currently following test case test case fails:
    @Test
    public void emptyRangeWithEmptyKeyword() {
        Range<LocalDate> empty = Range.localDateRange("empty");

        assertFalse(empty.contains(LocalDate.MIN));
        assertFalse(empty.contains(LocalDate.now()));
        assertFalse(empty.contains(LocalDate.MAX));

        assertNull(empty.upper());
        assertNull(empty.lower());
    }

@vladmihalcea can you please assign this issue to me? I've already started working this.

Fixed.


Changing the lower bound on a requirement without being asked to do so is rude

Is there an existing issue for this?

[X] I have searched the existing issues

Package ecosystem
python
Package manager version
No response
Language version
No response
Manifest location and content before the Dependabot update
No response
dependabot.yml content
No response
Updated dependency
No response
What you expected to see, versus what you actually saw
This test demonstrate exactly the old good and the new (at least by us) unwanted behaviour:
-              its([:requirement]) { is_expected.to eq(">=1.3.0,<1.6") }
+              its([:requirement]) { is_expected.to eq(">=1.5.0,<1.6") }

https://github.com/dependabot/dependabot-core/commit/47cd8fdfbf84307826e0d0085e675874c958494c#diff-2c26ae287011b080cc4582ed4ed3b3dbb2381d8790e58016abbc4a295c1a07b1L149-R149
Native package manager behavior
No response
Images of the diff or a link to the PR, issue, or logs
This commit broke it:
https://github.com/dependabot/dependabot-core/commit/47cd8fdfbf84307826e0d0085e675874c958494c
Smallest manifest that reproduces the issue
No response

Thank you for bringing this to our attention. We are currently looking into the issue and will address it as soon as possible.

Hi @mdellweg
Just need to confirm a few details to better understand the issue:

Are you using the increase strategy for dependencies?
Do you have a lower bound specified for the library (e.g., ">=...")?

We made these changes following our guidelines. If you are using the increase strategy and have specified a lower bound for the library, we are currently updating it to the latest installed version as mentioned in our versioning strategy. Note that the changes are applied because this functionality wasn't working properly.

We do not have a strategy configured, and the feature was working perfectly until last week.
For library like projects, you really want the broadest possible statements about compatibility you can safely provide. And bumping the lower bound of a dependency is a breaking change. If that was needed for a new feature, or an important bugfix, it'd better be done by hand.
If you work on an app that will always be deployed in isolation, go use ~= or == depending on your relative requirements of security and lazy.
And BTW, yes we run tests with the lower bound of dependencies.

@mdellweg ,
We did make changes for the lower bound with the increase strategy. Currently, we are reviewing the rules and will come up with a better solution . However, if you don't have a strategy configured and the current lower bound is not working as expected, I believe the widening strategy should work well since it doesn't make changes to the lower bound if the new version higher than lower bound and only increases the upper bound to up one major version.

Here is the document how to set strategy
https://docs.github.com/en/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file

imo the issue is that now it uses the increase strategy instead of widening which was automatically used before

Now python (pip) does not seem to allow the "widen" strategy. (I'm almost sure i saw it in the docs two days ago, but not anymore.)
What am I supposed to do now?

The changes of this PR are reverted in #10194. The versioning strategy needs to be re-planned, and a solution will be implemented according to the new plan.


porcelain2.ex needed to have a module name change

when compiling in my project I recieved the following error:
==> expect_ex
Compiling 6 files (.ex)
== Compilation error in file lib/expect/driver/porcelain2.ex ==
** (CompileError) lib/expect/driver/porcelain2.ex:5: cannot define module Expect.Driver.Porcelain because it is currently being defined in lib/expect/driver/porcelain.ex:5
(stdlib) erl_eval.erl:677: :erl_eval.do_apply/6
Renamed the porcelain2.ex module and added the alias, same behavior as expect.ex vs expect2.ex.

Oops... Thanks for the catch! I'll have to determine why CI didn't show this.
I believe you'll find the alias you added is counterproductive, as the bare Porcelain module is referring to the library dependency. I'll investigate further and make certain everything is in order now.
Thanks again!


Return object on decorators

This makes the decorators compatible with Babel's Typescript converter.

This looks like a fair enough change in order for us to support the babel toolchain but I'd like to read more about this issue if possible. Is this difference from TypeScript decorators documented somewhere?

@koddsson This is also an issue for us as well where we use babel and webpack to transpile our coce.
If I make the change, from the PR, the target decorator starts to work again and we dont need to setup our own manual getters.

Confirmed this behaviour in the Babel repl
function without_return(proto, key) {
  Object.defineProperty(proto, key, { get() { return 1 } })
}

function with_return(proto, key) {
  return Object.defineProperty(proto, key, { get() { return 1 } })
}
class Foo {
  @without_return foo
  @with_return bar
}

console.log(new Foo().foo, new Foo().bar)
// Logs `undefined, 1`.

The same code in the TypeScript playground logs 1, 1.

@keithamus Thanks a bunch for getting this one in!
One thought I had was around if we needed to update the return type on these functions now :thinking: .
https://github.com/github/catalyst/blob/main/src/target.ts#L10
defineProperty(o: any, p: PropertyKey, attributes: PropertyDescriptor & ThisType<any>): any;
Given we are returning the result from the defineProperty call now but I am not 100% sure of this :grin: .

Changing the signature effects TypeScript as it expects property decorators to return void.


In  clarity 1.0 input box  tooltip  feature  deprecated  reason

Summary
Summary the request and address the questions as appropriate.

What is the change?
Why should it go in Clarity?
Does this change impact existing behaviors? If so how?
If this change introduces a new behavior, is this behavior accessible?

Use case
Provide some specific details about how this change would improve your application and use case.
Examples
Are there any examples in other projects that demonstrate this feature or enhancement?
Workarounds
Is there a workaround for this feature at the moment, even if it is less than ideal?

We already used the older  12.0  based  all the forms used the tooltips  approach ,when see the version 1.0 ,we are seeing different approach  for  form validation error message shows.Documentation says tooltips  form validation deprecated .In my client request each form field required the tool tip  error meeage ,Let me tell how to use the version 1.0 with form validation  tooltip use with clarity feature breaking .also attached snapshot  older form   with tooltip error

This is no longer planned to be supported (hence the deprecation), particularly due to the UX challenges faced with hiding error messages inside of tooltips. There are also issues with the tooltips positioning and if they are properly visible in tight spaces (like modals). The new UX patterns are more accessible and functional, as well, because they show errors and are good for both sighted users and users with a screenreader.
We realize that the change in format is a major change, but our research shows it is for the better of all users. I'm going to close this as a question.


Add "looking for" filter

Similar to #235 but for the "looking for" field on the developer profile.

@joemasilotti after merging of #251 I would like to take on this one.

Thank you! Let's get that one merged in first before we move on to this. I just posted a review with some change requests.

@themudassarhassan all yours! Thanks again for the other PR.
I think we can use "Search status" as the title of the dropdown to match the developer form.

@joemasilotti sure will work on this in the coming weekend. It is really great working with you!

Closed via #268.


Use custom build directory

Instead of using the build directory defined by Xcode, we can override it
and build in the current directory. The benefit here is that in the
future, we can use this command to build the project and then use
simctl to load the app in the iOS simulator. That's not something we can
do using the default build location (AFAIK).
In addition, we can let users customize this location with a global
variable. By default, we'll build in ./build, but if users want to send
the build to a different location, they can do that easily.
This feels like it might be a little weird. But the pros here are that this
disconnects us entirely from Xcode's build artifacts, and it means that
creating a command like :XRun will be easier, because we'll know exactly
where the build app is.

This seems good to me, although this default may be unexpected for users transitioning from Xcode. Specifically worried about people not having build in their gitignores because they're not used to this pattern.

yeah, that was kind of my concern as well. GitHub's default gitignore for both Swift and Obj-C specify build I'm not sure how big of an issue it will end up being.

Liftoff has build in it's default gitignore as well, for the record.

I'm going to merge this, and if it's an actual issue for people, we can reevaluate


e1s: 1.0.39 -> 1.0.41

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/keidarcy/e1s/releases.
meta.description for e1s is: Easily Manage AWS ECS Resources in Terminal 🐱
meta.homepage for e1s is: https://github.com/keidarcy/e1s
meta.changelog for e1s is: https://github.com/derailed/e1s/releases/tag/v1.0.40
Updates performed

Golang update

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.0.40 with grep in /nix/store/pd0hkv9kfbsr7larig5c4ydcicjwyyiq-e1s-1.0.40
found 1.0.40 in filename of file in /nix/store/pd0hkv9kfbsr7larig5c4ydcicjwyyiq-e1s-1.0.40

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

e1s

Instructions to test this update (click to expand)

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

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

Or:
nix build github:r-ryantm/nixpkgs/9e6d2d97028f0bfd280876f8e83ac80ff3042755#e1s

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

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

1 package built:

e1s

Maintainer pings
cc @zelkourban for testing.

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

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

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/keidarcy/e1s/releases.
meta.description for e1s is: Easily Manage AWS ECS Resources in Terminal 🐱
meta.homepage for e1s is: https://github.com/keidarcy/e1s
meta.changelog for e1s is: https://github.com/derailed/e1s/releases/tag/v1.0.41
Updates performed

Golang update

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.0.41 with grep in /nix/store/j1aa1d3j4qbgr1a647c73fgrxgqvqf6y-e1s-1.0.41
found 1.0.41 in filename of file in /nix/store/j1aa1d3j4qbgr1a647c73fgrxgqvqf6y-e1s-1.0.41

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

e1s

Instructions to test this update (click to expand)

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

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

Or:
nix build github:r-ryantm/nixpkgs/1abe16b74d28dac4d1f33a43e774d46e5be16cae#e1s

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

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

1 package built:

e1s

Maintainer pings
cc @zelkourban for testing.

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

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


Unable to read non-public environment variables with Vite (Astro) - SSR deployments (specification)

Before opening, please confirm:

[X] I have checked to see if my question is addressed in the FAQ.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting questions.
[X] I have removed any sensitive information from my code snippets and submission.

App Id
d2lbl6s4po2urj
AWS Region
us-east-1
Amplify Hosting feature
SSR
Question
Hi I have a Vite based Astro site that I can't get to read a serverside environment variable - the site is built with the SSR specification (/.amplify-hosting).
Something like this works for PUBLIC starting variables I've set in Amplify's environment variables:
build:
  commands:
    - env | grep -e PUBLIC_ >> .env
    - pnpm run build

But I can't read non-public variables server-side e.g.:
build:
  commands:
    - env | grep -e API_KEY >> .env
    - pnpm run build

Everything works fine locally. Appreciate any assistance with this.

With a little further testing, it seems I don't need to manually copy PUBLIC environment variables in the build spec actually - any variables starting with PUBLIC_ (Astro renames this from the default VITE_) work by default.
E.g. add the PUBLIC_ environment variable to Amplify and re-deploy the app.

Passing the environment variables at runtime to the build also does not work on Amplify (but works locally - npm run build and then node entry.mjs in the default folder) e.g. with:
env | grep -e API_KEY >> .env
export $(cat .env) && pnpm run build

The values aren't working at build time at all, whether it's from the .env file (default behaviour) or passed at runtime. I guess the Amplify environment is doing something differently when it comes to building the project with the SSR spec - I can deploy a static site and it works with any serverside variables (without PUBLIC_) just fine.
I think another thing to try would be passing it directly to the node command to run the server (which works locally also), but I can't modify this from the deploy manifest e.g. with entrypoint: "API_KEY=value entry.mjs, it gives an error of the entrypoint can't be found. I'm guessing this configuration isn't used like node ${entrypoint} when Amplify runs the server. I don't see any other way to change this in the docs.
I have a minimal repo here if you would like to check things and deploy on your end.


RTL Support Request

Hello
is there any where to add rtl support in this useful library?

Sorry to say that I don't have the time to do that currently as it would be a bit difficult, the code became a bit too complex with all the new features.


Error with Modpack Server ATM9

Describe the problem
When trying to run a Minecraft Server with the ATM9 Modpack i get the following error. A similar error i had before was fixed by updating to the newest image, but now i have the newest image and it is downloading some modpacks, as seen in the logs, but at some point it gets this error.
Thanks
Marco
Container definition
version: "3.8"
services:
mc:
image: itzg/minecraft-server
ports:
- "25569:25565"
environment:
EULA: "true"
MOD_PLATFORM: AUTO_CURSEFORGE
CF_API_KEY: "$2a$10$...."
CF_PAGE_URL: https://www.curseforge.com/minecraft/modpacks/all-the-mods-9
MEMORY: 16G
volumes:
- /minecraft/ATM9/data:/data
volumes:
mc-data: {}
Container logs
[+] Running 1/0
✔ Container atm9-mc-1  Created                                                                                0.0s
Attaching to atm9-mc-1
atm9-mc-1  | [init] Running as uid=1000 gid=1000 with /data as 'drwxrwxr-x 10 1000 1003 4096 Oct  1 16:24 /data'
atm9-mc-1  | [mc-image-helper] 19:13:42.641 INFO  : Processing modpack 'All the Mods 9-0.1.11' (all-the-mods-9) @ 715572:4776759
atm9-mc-1  | [mc-image-helper] 19:13:43.597 INFO  : Excluding mod file 'Controlling' (controlling) due to configuration
atm9-mc-1  | [mc-image-helper] 19:13:43.741 INFO  : Mod file mods/useful_railroads-forge-1.20.1-<IP_ADDRESS>.jar already exists
atm9-mc-1  | [mc-image-helper] 19:13:43.741 INFO  : Mod file mods/flickerfix-1.20.1-4.0.1.jar already exists
atm9-mc-1  | [mc-image-helper] 19:13:43.746 INFO  : Mod file mods/cupboard-1.20.1-2.0.jar already exists
atm9-mc-1  | [mc-image-helper] 19:13:43.748 INFO  : Mod file mods/crashutilities-8.1.4.jar already exists
atm9-mc-1  | [mc-image-helper] 19:13:43.757 INFO  : Mod file mods/rsrequestify-1.20.1-2.3.2.jar already exists
atm9-mc-1  | [mc-image-helper] 19:13:43.758 INFO  : Mod file mods/ftb-essentials-forge-2001.2.0.jar already exists
atm9-mc-1  | [mc-image-helper] 19:13:43.891 INFO  : Mod file mods/baubley-heart-canisters-1.20.1-1.0.3.jar already exists
atm9-mc-1  | [mc-image-helper] 19:13:43.898 INFO  : Mod file mods/trashcans-1.0.18b-forge-mc1.20.jar already exists
atm9-mc-1  | [mc-image-helper] 19:13:43.903 INFO  : Mod file mods/alltheores-1.20-46.0.2-2.1.1.jar already exists
atm9-mc-1  | [mc-image-helper] 19:13:44.223 INFO  : Mod file mods/sophisticatedbackpacks-1.20.1-<IP_ADDRESS>9.jar already exists
atm9-mc-1  | [mc-image-helper] 19:13:44.348 INFO  : Excluding mod file 'Entity Culling Fabric/Forge' (entityculling) due to configuration
atm9-mc-1  | [mc-image-helper] 19:13:44.352 INFO  : Mod file mods/BetterAdvancements-1.20.1-<IP_ADDRESS>.jar already exists
atm9-mc-1  | [mc-image-helper] 19:13:44.356 INFO  : Mod file mods/MysticalAgriculture-1.20.1-7.0.2.jar already exists
atm9-mc-1  | [mc-image-helper] 19:13:44.357 INFO  : Mod file mods/durabilitytooltip-1.1.5-forge-mc1.20.jar already exists
atm9-mc-1  | [mc-image-helper] 19:13:44.370 INFO  : Mod file mods/IntegratedDynamics-1.20.1-1.19.1.jar already exists
atm9-mc-1  | [mc-image-helper] 19:13:44.370 INFO  : Mod file mods/create-stuff-additions1.20.1_v2.0.4a.jar already exists
atm9-mc-1  | [mc-image-helper] 19:13:44.371 INFO  : Mod file mods/kubejs-forge-2001.6.3-build.52.jar already exists
atm9-mc-1  | [mc-image-helper] 19:13:44.374 INFO  : Mod file mods/AttributeFix-Forge-1.20.1-21.0.2.jar already exists
atm9-mc-1  | [mc-image-helper] 19:13:44.379 INFO  : Mod file mods/multipiston-1.20-1.2.31-ALPHA.jar already exists
atm9-mc-1  | [mc-image-helper] 19:13:44.379 INFO  : Mod file mods/trashslot-forge-1.20-15.1.0.jar already exists
atm9-mc-1  | [mc-image-helper] 19:13:44.388 INFO  : Mod file mods/ToastControl-1.20.1-8.0.3.jar already exists
atm9-mc-1  | [mc-image-helper] 19:13:44.430 ERROR : 'install-curseforge' command failed. Version is 1.35.3
atm9-mc-1  | me.itzg.helpers.errors.GenericException: Failed to parse response body into class me.itzg.helpers.curseforge.model.GetModFileResponse: Cannot deserialize value of type me.itzg.helpers.curseforge.model.FileStatus from String "18": not one of the values accepted for Enum class: [11, 12, 13, 14, 15, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10]
atm9-mc-1  |  at [Source: (reactor.netty.ByteBufMono$ReleasingInputStream); line: 1, column: 194] (through reference chain: me.itzg.helpers.curseforge.model.GetModFileResponse["data"]->me.itzg.helpers.curseforge.model.CurseForgeFile["fileStatus"])
atm9-mc-1  |    at me.itzg.helpers.http.ObjectFetchBuilder.lambda$handleResponse$1(ObjectFetchBuilder.java:89)
atm9-mc-1  |    at reactor.core.publisher.MonoFlatMap$FlatMapMain.onNext(MonoFlatMap.java:132)
atm9-mc-1  |    at reactor.core.publisher.MonoPublishOn$PublishOnSubscriber.run(MonoPublishOn.java:181)
atm9-mc-1  |    at reactor.core.scheduler.SchedulerTask.call(SchedulerTask.java:68)
atm9-mc-1  |    at reactor.core.scheduler.SchedulerTask.call(SchedulerTask.java:28)
atm9-mc-1  |    at java.base/java.util.concurrent.FutureTask.run(Unknown Source)
atm9-mc-1  |    at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
atm9-mc-1  |    at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
atm9-mc-1  |    at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
atm9-mc-1  |    at java.base/java.lang.Thread.run(Unknown Source)
atm9-mc-1  |    Suppressed: java.lang.Exception: #block terminated with an error
atm9-mc-1  |            at reactor.core.publisher.BlockingSingleSubscriber.blockingGet(BlockingSingleSubscriber.java:103)
atm9-mc-1  |            at reactor.core.publisher.Mono.block(Mono.java:1712)
atm9-mc-1  |            at me.itzg.helpers.curseforge.CurseForgeInstaller.processModpack(CurseForgeInstaller.java:540)
atm9-mc-1  |            at me.itzg.helpers.curseforge.CurseForgeInstaller.resolveModpackFileAndProcess(CurseForgeInstaller.java:361)
atm9-mc-1  |            at me.itzg.helpers.curseforge.CurseForgeInstaller.installByRetrievingModpackZip(CurseForgeInstaller.java:229)
atm9-mc-1  |            at me.itzg.helpers.curseforge.CurseForgeInstaller.lambda$install$4(CurseForgeInstaller.java:159)
atm9-mc-1  |            at me.itzg.helpers.curseforge.CurseForgeInstaller.install(CurseForgeInstaller.java:195)
atm9-mc-1  |            at me.itzg.helpers.curseforge.CurseForgeInstaller.install(CurseForgeInstaller.java:158)
atm9-mc-1  |            at me.itzg.helpers.curseforge.InstallCurseForgeCommand.call(InstallCurseForgeCommand.java:202)
atm9-mc-1  |            at me.itzg.helpers.curseforge.InstallCurseForgeCommand.call(InstallCurseForgeCommand.java:27)
atm9-mc-1  |            at picocli.CommandLine.executeUserObject(CommandLine.java:2041)
atm9-mc-1  |            at picocli.CommandLine.access$1500(CommandLine.java:148)
atm9-mc-1  |            at picocli.CommandLine$RunLast.executeUserObjectOfLastSubcommandWithSameParent(CommandLine.java:2461)
atm9-mc-1  |            at picocli.CommandLine$RunLast.handle(CommandLine.java:2453)
atm9-mc-1  |            at picocli.CommandLine$RunLast.handle(CommandLine.java:2415)
atm9-mc-1  |            at picocli.CommandLine$AbstractParseResultHandler.execute(CommandLine.java:2273)
atm9-mc-1  |            at picocli.CommandLine$RunLast.execute(CommandLine.java:2417)
atm9-mc-1  |            at picocli.CommandLine.execute(CommandLine.java:2170)
atm9-mc-1  |            at me.itzg.helpers.McImageHelper.main(McImageHelper.java:155)
atm9-mc-1  | Caused by: com.fasterxml.jackson.databind.exc.InvalidFormatException: Cannot deserialize value of type me.itzg.helpers.curseforge.model.FileStatus from String "18": not one of the values accepted for Enum class: [11, 12, 13, 14, 15, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10]
atm9-mc-1  |  at [Source: (reactor.netty.ByteBufMono$ReleasingInputStream); line: 1, column: 194] (through reference chain: me.itzg.helpers.curseforge.model.GetModFileResponse["data"]->me.itzg.helpers.curseforge.model.CurseForgeFile["fileStatus"])
atm9-mc-1  |    at com.fasterxml.jackson.databind.exc.InvalidFormatException.from(InvalidFormatException.java:67)
atm9-mc-1  |    at com.fasterxml.jackson.databind.DeserializationContext.weirdStringException(DeserializationContext.java:2002)
atm9-mc-1  |    at com.fasterxml.jackson.databind.DeserializationContext.handleWeirdStringValue(DeserializationContext.java:1230)
atm9-mc-1  |    at com.fasterxml.jackson.databind.deser.std.EnumDeserializer._deserializeAltString(EnumDeserializer.java:415)
atm9-mc-1  |    at com.fasterxml.jackson.databind.deser.std.EnumDeserializer._fromString(EnumDeserializer.java:279)
atm9-mc-1  |    at com.fasterxml.jackson.databind.deser.std.EnumDeserializer.deserialize(EnumDeserializer.java:258)
atm9-mc-1  |    at com.fasterxml.jackson.databind.deser.impl.MethodProperty.deserializeAndSet(MethodProperty.java:129)
atm9-mc-1  |    at com.fasterxml.jackson.databind.deser.BeanDeserializer.vanillaDeserialize(BeanDeserializer.java:314)
atm9-mc-1  |    at com.fasterxml.jackson.databind.deser.BeanDeserializer.deserialize(BeanDeserializer.java:177)
atm9-mc-1  |    at com.fasterxml.jackson.databind.deser.impl.MethodProperty.deserializeAndSet(MethodProperty.java:129)
atm9-mc-1  |    at com.fasterxml.jackson.databind.deser.BeanDeserializer.vanillaDeserialize(BeanDeserializer.java:314)
atm9-mc-1  |    at com.fasterxml.jackson.databind.deser.BeanDeserializer.deserialize(BeanDeserializer.java:177)
atm9-mc-1  |    at com.fasterxml.jackson.databind.deser.DefaultDeserializationContext.readRootValue(DefaultDeserializationContext.java:323)
atm9-mc-1  |    at com.fasterxml.jackson.databind.ObjectReader._bindAndClose(ObjectReader.java:2105)
atm9-mc-1  |    at com.fasterxml.jackson.databind.ObjectReader.readValue(ObjectReader.java:1481)
atm9-mc-1  |    at me.itzg.helpers.http.ObjectFetchBuilder.lambda$handleResponse$1(ObjectFetchBuilder.java:85)
atm9-mc-1  |    ... 9 common frames omitted
atm9-mc-1  | [init] ERROR failed to auto-install CurseForge modpack
atm9-mc-1 exited with code 1

Thanks for reporting this. There must be an update to the API that will need to be handled.

Dev note
That FileStatus ordinal is not documented, nor is values 16 or 17: https://docs.curseforge.com/#tocS_FileStatus

I am not able to recreate this issue. I suspect the offending mod file had its file status changed since you originally observed the issue. I am going to add a little more information to the error stack trace for future debugging, but otherwise am unable to address the original issue exactly.

Thank you for dealing with my problem so fast, even tough it fixed itself 😂


Use the atom-workspace tag instead of the workspace class.

In keymaps\markdown-toc.cson: Use the atom-workspace tag instead of the workspace class.

Fixed by https://github.com/nok/markdown-toc/pull/3.


version on https://vmware.github.io/harbor/

you might update that page to reflect to 0.5.0 instead of linking to 0.3.5rc.tar.gz prominently...

Already updated with latest changes. Thanks!


Typename checks on release

if(obj.type.name !== 'TabAndroid' || obj.type.__proto__.name !== 'Tab')
When generating a release APK these checks do not pass and the control does not behave correctly

Could you please show some logs ? And be more accurate concerning "the control does not behave correctly" ?

Hi @ayoubdev,
Great tab control by the way.
The problem I faced, was that I created a release APK (./gradlew assembleRelease) and the control did not show the tabs text and neither the tab content. Those were both blank.
On the app's logs, I got a TabLayoutAndroid View must only have TabAndroid as direct children
I added some logs to the containMixViews method in your component and found out that on runtime with the release APK obj.type.name returned t and obj.type.__proto__.name returned just r
Then, I tested a debug APK (``./gradlew assembleDebug) and there, those properties returned the correct TabAndroidandTab` respectevely.
I believe it has to do with React Native minifying code when creating a release APK and the name of the types not matching

Thanks for precisions :+1:
It should be fixed on v1.1.2 (just released), can you check please?

Just tested and it's working fine. Thanks!


Changed wording on core versions, added some clarification

This PR slightly rephrases the introductory chapter for the Vulkan version and adds an explanation at what promotion to core means.

Thanks for improving this!


Terminal Plus

Hi,
it is installed successfully but when I'm trying to run it. then just cursor is blinking nothing else it's blank unable to type anything there.
Thank you!

I have the same problem...
Atom version 1.47.0 x64 on Ubuntu 18.04.4

i think it has some version problem..

thanks buddy.. :)

I have same problem,  and already upgrade to lastest version

This package is no longer maintained. Please uninstall platformio-ide-terminal and install either terminus or x-terminal


Setup integration tests

Creates a framework for writing Trustee integration tests in Rust.
Put your tests in integration-tests/tests/integration.rs (or a similar file) and they will run when you do cargo test at the top level.
I've added two simple integration tests. They aren't anything beyond what we already have in other tests, but they add a structure that should help us to create a lot more. Before I get too carried away, please take a look at the setup.
Note that running the KBS in the background was trickier than expected. I think I found a pretty good way to do it in the end.

Looks great! One question before getting into the code:
why not we directly have an tests directory under kbs to have these integration tests, like what we do in image-rs
A quick glance is that way we need to add kbs_client to kbs's [dev-dependencies] section in Cargo.toml.
This way, we could avoid another sub crate.

why not we directly have an tests directory under kbs to have these integration tests, like what we do in image-rs

I think this would work. I see the integration tests as having a broader scope than just the KBS, so I made a new package, but if that adds overhead I could move it. Generally I think that since the repo merge, we've had  some stuff in individual packages that should really be in the top of the repo (like docs, perhaps).

@Xynnn007

Do we need to delete some duplicated ones?

Since these integration tests use the crate directly, they don't test the binaries or the docker-compose configuration or the k8s configuration. I think it's fine to keep some simple tests around that make sure that those interfaces still work. We should do a little bit of cleanup and organization with our existing tests, but I think that's for another PR.


PATCH should have its own linkable section

Right now it's inside https://postgrest.org/en/stable/api.html#insertions-updates.
Also mention that it's possible to update rows with different data through UPSERT.
Ref: https://github.com/PostgREST/postgrest/issues/1816

Already on https://postgrest.org/en/stable/references/api/tables_views.html#update


I add check cof score negative and nms.

I fixed conf score negative but still had stack bounding boxes, so I still add nms in to function. Thanks.

ok, this is first pull request for me, I will doing. Thanks.


is there any  way to disable this materialchipsinput view?

i'm having difficulty in disabling this view i also tried to diable parent view still it is not working.

Hi,
I personally used such hack.
final RecyclerView recyclerView = (RecyclerView) chipsInput.findViewById(R.id.chips_recycler);
recyclerView.addOnChildAttachStateChangeListener(new RecyclerView.OnChildAttachStateChangeListener(){

	public void onChildViewAttachedToWindow(View view) {
		View v = recyclerView.getLayoutManager().findViewByPosition(tagsInput.getFilterableList().size()+1);
		if (v != null && v.getVisibility() == View.VISIBLE && v instanceof ChipsInputEditText) {
			ChipsInputEditText editor = (ChipsInputEditText) v;
			editor.setFocusable(false);
			editor.setVisibility(View.GONE);
		} else {
			if (view instanceof ChipsInputEditText) {
				ChipsInputEditText editor = (ChipsInputEditText) view;
				editor.setFocusable(false);
				editor.setVisibility(View.GONE);
			}
		}
	}

	public void onChildViewDetachedFromWindow(View view) {}
});

I will test it as well.
Sorry for the late response

its ok plz test it.


The app no longer works, needs to support API v16.

The app reports: "This API version is o longer supported. Please upgrade your software: https://telegra.ph/API-v15-to-v16-migration-guide-05-17"
Any plans to update the app?

Duplicate of #87


Via tenting check doesn't work correctly when blind or buried vias are used (it reports buried ends of vias as not tented).

Nice, these are awesome scripts. -Lee

Thanks! Glad you like them :-)


offline for maintenance

i have been getting the error message this ap is offline for maintenance for a while now when i try to exess the link. so i don't get to the google authenticate account screen. is this only temporary? if so, when will the aplication be back online?

I've brought the app back online at https://youtube-shuffle.fly.dev
Assuming usage doesn't exceed the free tier, I can keep it running there.


⚠ Bofrost.de has degraded performance

In f11031e, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1220 ms

Resolved: Bofrost.de performance has improved in c8643ad.


Block viewer: overlapping blocks issue resolved

Fixes #3709
Before changes
Classic UI

New UI

After changes
New UI
Now each block is clickable/selectable.

The latest commit checks for every possible case that might occur (as far as I've tested), do let me know if you find any case of overlapping blocks. Thanks.
PS: I shall run the make assets after the final approval of the changes.
cc: @prmsrswt

The latest commit checks for every possible case that might occur (as far as I've tested), do let me know if you find any case of overlapping blocks. Thanks.
PS: I shall run the make assets after the final approval of the changes.
cc: @prmsrswt

Created a new isOverlapping function and added unit tests for the following scenario:

Thanks for the good work! @Namanl2001


🚧  Add a11y test for Search

Resolves #2027

It seems like the suggested fix does remove the warning
  it('Should pass a11y test', async () => {     const { getComputedStyle } = window     window.getComputedStyle = (elt) => getComputedStyle(elt)     const { container } = render(<Search />)     await act(async () => {       const result = await axe(container)       expect(result).toHaveNoViolations()     })   })


Missing #include

I think there's an #include <optional> missing here:
https://github.com/joboccara/pipes/blob/56f7e335deb89236918f16e60526bbc0702f6b80/include/pipes/helpers/optional.hpp#L5
My compiler told me.

+1
https://godbolt.org/z/PsM9Yf
see here


Add a bit of non-clickable space between the "Add feedback" options on MS reports

While reviewing posts on mobile, I (and others) often misclick, causing temporary confusion. I wonder if a bit of non-clickable space between the "Add feedback" icons would help our aim?

I was wondering if you know the real name of this Individual? : https://stackoverflow.com/users/1014587/mast?tab=profile
He claimed hes part of the charcoal project, It's been a week and I still haven't cool down after what this guy said to me in a stackoverflow question. So it would be awesome if you could tell me the real name and address of this guy I've been burning resources and been to a lot of forum just trying to find who this guy is. Please let me know you would help me a lot, thank you.


Add CORS middleware

Fixes
This PR re-adds the accidentally removed CORS middleware. The absence of this middleware prevents cross-origin requests which consequently prevents using the local API as the server for the frontend.
This was reported by @AetherUnbound.
Description

This PR

adds corsheaders.middleware.CorsMiddleware to MIDDLEWARE
prevents duplication of INSTALLED_APPS and middleware when inheriting between settings files

Testing Instructions

Check out this PR and run the dev server: just api/up

Check that the CORS headers are applied.
$ curl -v -H "Origin: http://localhost:50280/" "http://localhost:50280/"

Checklist

[x] My pull request has a descriptive title (not a vague title likeUpdate index.md).
[x] My pull request targets the default branch of the repository (main) or a parent feature branch.
[x] My commit messages follow best practices.
[x] My code follows the established code style of the repository.
[ ] I added or updated tests for the changes I made (if applicable).
[ ] I added or updated documentation (if applicable).
[x] I tried running the project locally and verified that there are no visible errors.
[ ] I ran the DAG documentation generator (if applicable).

Developer Certificate of Origin

Developer Certificate of Origin
Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

@dhruvkb Could you explain the motivation of these changes since there is no issue linked?

@krysal good point, sorry about that. I updated the description with the problem this PR is aiming to fix.


[stable/traefik]: fix service monitor scrape port

What this PR does / why we need it:
Fix the traefik ServiceMonitor scrape port
Which issue this PR fixes
Special notes for your reviewer:
As by the doc, the correct is to use the port instead of the targetPort, because the port refers to the service name created.

port | Name of the service port this endpoint refers to. Mutually exclusive with targetPort.
https://coreos.com/operators/prometheus/docs/latest/api.html#endpoint

Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[ ] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/chart])

/assign @errm

/ok-to-test

/lgtm


Merge new design of training namespace into master

Based on changes in PR https://github.com/Azure/azure-sdk-for-net/pull/11048

Part1: https://github.com/Azure/azure-sdk-for-net/pull/11159

Part 2: https://github.com/Azure/azure-sdk-for-net/pull/11187

I think that is it. I will keep the issue open until we finish the other models

Last PR https://github.com/Azure/azure-sdk-for-net/pull/11248 merged


Type '()' cannot conform to 'Publisher'

I have tried to copy exactly what you recommend (as part of producing a small reproducible error):
let tmdbClient = APIClient(
	baseURL: URL(string: "https://api.themoviedb.org/3")!,
	configuration: APIClientConfiguration(
		additionalParameters: [
			"api_key": "20495f041a8caac8752afc86",
			"language": "es",
		]
	)
)

struct Status: Decodable {
	var code: Int
	var message: String

	enum CodingKeys: String, CodingKey {
		case code = "status_code"
		case message = "status_message"
	}
}

struct Genre: Decodable {
	var id: Int
	var name: String
}

struct GenreList: Decodable {
	var genres: [Genre]
}

let movieGenresRequest = APIRequest<GenreList, Status>.get("/genre/movie/list")

tmdbClient.response(for: movieGenresRequest).catch({ error in
	print(error)
})

But the errors I get are:
Instance method 'catch' requires the types 'GenreList' and '().Output' be equivalent
Type '()' cannot conform to 'Publisher'; only struct/enum/class types can conform to protocols

Do you have any ideas what I am doing wrong?

User error, ignore me :D


Update cache-overview.md

Based on the reference link documentation :  https://azure.microsoft.com/en-us/pricing/details/bandwidth/
It states "*Starting from July 1, 2022, Data transfer billing between Virtual machines across availability zones will begin. Please see FAQ for additional details."
However the REDIS doc points to 2021.
Hence proposing this change to ensure both documents are in sync.  Kindly review

#label:"aq-pr-triaged"

#sign-off


Install POW as Elixir app in Umbrella - not as Phoenix app

Ok forgive me, totally new at Phoenix and app dev in general so the obvious is not very obvious.
I have an Umbrella app with a db elixir app managing my repo.
I  do not understand the ELixir/Phoenix relationship well enough yet and suffer major OCD - I am using Phoenix apps in my umbrella for an admin UI and my REST API and understand the sorta the need for 2 folders in a Phoenix app lib for App(business logic) and App_Web (presentation).  Where my OCD kicks in overdrive is having to use a Phoenix app in my umbrella for an app that  does not require a UI and therefore that App_Web folder Phoenix provides.
In my mind, Auth (POW)  supports access through the phoenix rest api app to the business logic in all my umbrella apps and should stand alone.  So I am trying to setup POW as an Elixir only app in the umbrella with mix new auth --module Auth --sup.  I do not want Auth to be a Phoenix app that requires me to stare at the damn App-Web folder all day.
Maybe (likely) I am just plain wrong and do not get it yet.
In any case, reading what I can find in DuckDuckGo about POW and of course your git repo you mention using a plug instead of Phoenix but sadly only provide a getting started with a Phoenix app.
Can you help a brother out and provide an example of using POW in an umbrella Elixir app using a Plug?  I am going to keep digging and will probably hack it out but will likely be wrong, wrong, wrong.
FWIW I am also using Triplex (multi-tenant by schema) in my elixir dbapp  and have the following umbrella setup I am reasoning through:

accounts:  (Elixir app managing business logic for all accounts ie Persons, Companies, Patients, Doctors - Triplex tenant logic lives here)
api_rest:  (Phoenix app manages api connections)
api_graphql (Phoenix/Absinthe app manages gql connections)
auth (Elixir app manages all authentication using POW I hope)
db (Elixir app managing migrations and schemas for all persisted entities)
inventory (Elixir app managing the business logic for inventory control)
... (other Elixir apps managing the different business contexts in my app)

Thanks in advance for any help, updates or references to anything that may help me get on track...

If you'll only have a REST api with e.g. bearer token then it's much easier to go without Pow. What makes Pow useful is when you need user authentication, user registration, and session management. For API's, Plug/Phoenix pretty much have everything you need. You can write an bearer authentication plug method in few lines of code. Alternatively, there's plenty of token based auth libraries, e.g. Guardian.
Pow can indeed be used with solely Plug, but it will be your responsibility to handle all action calls and responses. It's an option in case you prefer using Raxx instead of Phoenix.
The acme_bank module is pretty cool, and it would be cool if it included Pow. But it may not be what @wojtekmach has in mind, he probably want to highlight how you can roll your own auth in Elixir/Phoenix 😄

Thanks for the reply Dan,
I am going to have an admin and possible UI for my app on server with Phoenix/React - the REST API available for 3rd party apps and my mobile.
Weighing session tokens across the board with an electron client app involved as well.  I understand you are busy and congratulations on a great package.  I’ll figure it out.
Sorry if I broke protocol on suggesting an enhancement on available apps - outside of my personal desire to see Pow implemented without Phoenix I thought (my business/marketing hat on) it would be a great way to raise interest for POW with a working implementation on a highly referenced and regarded app in the community.
Closing issue with my best regards and wishes for your success.

No worries, all feedback is most welcome, and these use cases helps me to get Pow moving in the right direction. If you have any questions do not hesitate to open or comment on a issue! It's what helps me ensure that the documentation is clear, and Pow easy to use.
And yeah, I would love to see Pow included in public sample apps 😄
If you're going to have a web front with admin and possible user login, then Pow will definitely help you out. For the API, I would advice to just write a simple bearer token authentication plug. It's super easy with Phoenix.


Cannot sample texture that was passed to shader.

Used Parameters.Set to get the texture into the shader.
In the shader texture.Sample(Sampler, float2(x,y)) does not seem to have any effect.

Sure.
ShaderTextureSample.zip

It seems to be an issue with parameters.set setting the texture somewhere, but it's not being uploaded to the shader. You can use parameters.get to get the texture after setting it, which returns the expected texture. Yet, it's not actually accessible in the shader field.

Solved by putting the shader's texture2d field inside of rgroup PerMaterial {}.


openpilot: new models and onnx ops

some onnx ops changes
update to new openpilot supercombo model

Is this is issue you were seeing on master that you mentioned?

Yes


Update README.md

Add soundbank as requested in #57.

@amilajack there's also this pull request. It had a merge conflict that I fixed just now.


can't find teambeefInstaller.exe

I did what it said on the "how to install" page and it didn't work. I downloaded the "bendyVR" file, I extracted it, but I don't see the teambeefInstaller.exe did I miss something?

Did you properly extract it?
Here's the content of the RAR file:

I downloaded WinRAR and it finally worked! thank you so much 👍


3.11.1 unupgradeable via npm

I've been upgrading other global packages with npm today, and this problem seems to be exclusive to 3.11.1 - when you attempt to upgrade to that version through npm, the installation never completes, and reloading the terminal dumps you into prompt (since that's what's being used to autoload spaceship). This was true of two machines, not just one.
I ended up going back to installing through git and symlinking, but it looks as if installing fresh via npm works, as well. Not sure why upgrading fails but installing fresh works, but just letting you know in case there's something weird with npm's copy of the package, or whether something can't be overwritten and then hangs (though I don't get any permissions errors).
If you need me to downgrade and give it another go, to provide logs, I can ... thanks for this, it's a pleasure to use and gorgeous to look at.

Thank you @colinhowells for the report. Would it possible to share the logs ? I did have small hiccup during publishing that version. If issue persists, We could release a patch version.

Be glad to – I can downgrade back to 3.11.0, then run the same upgrade process again, and send you whatever you'd like if you can tell me where and what to find for you. I'm not sure where I'd find useful info at the time the upgrade attempt's being made.

That would be great, Please share whatever log you get.

Yeah, I was asking where I'd look for that information – Console isn't telling me anything germane, and as far as npm is concerned everything is fine; it's not going to create an error log for this, and isn't reporting anything while the upgrade is hanging. It's hanging right now, if you'd like me to look somewhere specific ...

Alternatively we can chalk it up to weirdness, I'll fresh install 3.11.1, and then when you release the next version I can let you know how that upgrade process goes. It's interesting because the upgrade doesn't fail, it just never completes – but at the same time, it doesn't give up or throw an error.
This might not have anything to do with npm or spaceship but an underlying dependency? Meaning that the upgrade process is fine up until the point where prompt or something has to write to a configuration file but can't? Just a guess. Not sure in that case why a fresh install would work, though.

4.x is released. Please reopen if the issue is present.


Reverse ordering for SortedListField

Added param 'reverse' for SortedListFields to allow collections to be sorted in descending order instead of the default ascending.

Hi @stephenyoung - thanks for the patch.  Whats your use case for this?  Also can you provide a testcase?

I'm using capped collections for managing lists of top occurrences of various datapoints, and need them to be sorted from most to least occurrence - to simplify dealing with data output, it makes more sense to store the data in descending order instead of having to sort afterwards.

ok thanks I will look into the patch.
Not sure if this will cause issues with delta'ing / saving could
potentially be some pitfalls there.
Ross
On Tue, Nov 22, 2011 at 3:17 PM, Stephen Young <
<EMAIL_ADDRESS>
wrote:

I'm using capped collections for managing lists of top occurrences of
various datapoints, and need them to be sorted from most to least
occurrence - to simplify dealing with data output, it makes more sense to
store the data in descending order instead of having to sort afterwards.

Reply to this email directly or view it on GitHub:
https://github.com/hmarr/mongoengine/pull/364#issuecomment-2835482

Thanks! I'm using my version in an application I'm developing and will let you know if I come across any issues it causes.

Thanks @stephenyoung - added it to the dev branch


Add missing contracts in System.Linq.Expressions.Expression and derived types

This addresses #170. Adds contracts for:

static methods in the Expression class
Update methods in specific expression classes
methods and properties in new classes added in .NET 4

@fedotovalex This is great! :smile: Note that I'm hand reviewing every added contract for accuracy, so please do not rebase, squash, or amend any commits in this pull request (doing so will force me to start over). I have not found any mistakes yet, but even if I do please just correct them as new commits.

Questions from Expression.cs:

:bulb: The requires lines in DebugInfo(SymbolDocumentInfo, int, int, int, int) might be improved by using startLine >= 1 instead of startLine > 0. In the editor extensions this drives home the fact that these are 1-based indexes. (All assuming of course that the editor extensions actually use the requirement in string form.)
:question: In Default(Type), what happens if type is null? It won't fail there, but will it fail when you try to compile the IL?
:bulb: Expression.Parameter (two overloads) can each require type != typeof(void).
:exclamation: The requirement in Expression.Property(Expression, PropertyInfo, IEnumerable<Expression>) that instance != null is incorrect.
:exclamation: The requirement in Expression.Property(Expression, Type, string) that expression != null is incorrect.
:exclamation: The requirement in Expression.Property(Expression, PropertyInfo, Expression[]) that instance != null is incorrect.
:exclamation: The requirement in Expression.Property(Expression, string, Expression[]) that instance != null is incorrect.
:bulb: Expression.Switch (6 overloads) can include a requirement that cases != null (could also require non-empty and non-null items if we are doing that)
:bulb: Expression.SwitchCase (2 overloads) can include a requirement that testValues != null (could also require non-empty and non-null items if we are doing that)
:bulb: Expression.TryCatch(Expression, CatchBlock[]) can require handlers != null (could also require non-empty and non-null if we are doing that)
:bulb: Expression.TryCatchFinally(Expression, Expression, CatchBlock[]) can require finally != null || handlers != null (could also require items in handlers to be non-null when handlers itself is not null)
:bulb: Expression.TryFault(Expression, Expression) can require fault != null
:bulb: Expression.TryFinally(Expression, Expression) can require finally != null

Outstanding work overall @fedotovalex. You'll definitely need to update the items marked with :exclamation: since they are incorrect and the documentation explicitly covers the case. Let me know if you have any questions.

@sharwell, thanks for the thorough review.
Most of the items from the Expression.cs list are done. Here are some comments:

An attempt to compile an expression with Default(null) results in ArgumentNullException deep in the code when it tries to insert a null type value into a dictionary, so I added a precondition for type != null. Perhaps Microsoft guys can file an internal ticket to have it checked at runtime.

I did not include a precondition for type != typeof(void) in Parameter overloads because it cannot be proven by the static checker in the simplest cases.

Contract.Assert(typeof(string) != typeof(void));  // CodeContracts: assert unproven

In Expression.Property(Expression, string, Expression[]), expression != null is actually required as the expression is the only source of type information (http://referencesource.microsoft.com/#System.Core/Microsoft/Scripting/Ast/IndexExpression.cs,214, RequiresCanRead implies non-null).

Everything else on the list should be addressed.

Can we use PEX or similar to automatically generate tests for the framework, watch for exceptions and autogenerate contracts based on these?
We are trying to use ReviewBot internally to similar effect (but in our case, generating contracts in our own code).
From: Alex Fedotov<EMAIL_ADDRESS>Sent: Saturday, 25 July 2015 7:26 PM
To: Microsoft/CodeContracts
Subject: Re: [CodeContracts] Add missing contracts in System.Linq.Expressions.Expression and derived types (#171)
@sharwellhttps://github.com/sharwell, thanks for the thorough review.
Most of the items from the Expression.cs list are done. Here are some comments:
·         An attempt to compile an expression with Default(null) results in ArgumentNullException deep in the code when it tries to insert a null type value into a dictionary, so I added a precondition for type != null. Perhaps Microsoft guys can file an internal ticket to have it checked at runtime.
·         I did not include a precondition for type != typeof(void) in Parameter overloads because it cannot be proven by the static checker in the simplest cases.
Contract.Assert(typeof(string) != typeof(void)); // CodeContracts: assert unproven

In Expression.Property(Expression, string, Expression[]), expression != null is actually required as the expression is the only source of type information (http://referencesource.microsoft.com/#System.Core/Microsoft/Scripting/Ast/IndexExpression.cs,214, RequiresCanRead implies non-null).

Everything else on the list should be addressed.
—
Reply to this email directly or view it on GitHubhttps://github.com/Microsoft/CodeContracts/pull/171#issuecomment-124825756.

In Expression.Property(Expression, string, Expression[]), expression != null is actually required as the expression is the only source of type information (http://referencesource.microsoft.com/#System.Core/Microsoft/Scripting/Ast/IndexExpression.cs,214, RequiresCanRead implies non-null).

I was referring to Expression.Property(Expression, Type, string).

For the overload you mentioned, the documentation for the parameter is incorrect. It should probably be updated to remove the suggestion that instance could be null.

Okay, I updated the comment in the code and also submitted feedback on the corresponding MSDN page.
Let me know if there are any other issues I need to address before this PR can move forward.

I think everything is looking good and feature is ready for merging.
Any objections? @fedotovalex, @sharwell?

:+1:

Merged. Thanks a lot, @sharwell, @fedotovalex!


[stable-4.3] backport Workflows: Fix dev-release asset upload, switch to github cli (#550)

Backports #550 to stable-4.3 - use gh for github releases.
(Part of https://github.com/ansible/ansible-hub-ui/pull/548 for stable-4.2, and no other branches are doing stable releases.)

TODO: update for https://github.com/ansible/ansible-hub-ui/pull/565 changes