@note annotation causes error from Doctrine

Among the changes in this commit are some annotations in the PhpDoc comments. The @note annotation is throwing errors during configure:
With:
/**
 * Create many entities with persisting them to the database.
 *
 * @param bool|null $cleanHeap Clean the heap after creating entities.
 *
 * @note To change the default value use {@see static::$cleanHeap} property.
 */

produces:
[Spiral\Attributes\Exception\SemanticAttributeException]
[Semantical Error] The annotation "@note" in method Spiral\DatabaseSeeder\Factory\AbstractFactory::create() was never imported. Did you maybe forget to add a "use" statement for this annotation?
in vendor/spiral/attributes/src/Internal/DoctrineAnnotationReader.php:87

Previous: [Doctrine\Common\Annotations\AnnotationException]
[Semantical Error] The annotation "@note" in method Spiral\DatabaseSeeder\Factory\AbstractFactory::create() was never imported. Did you maybe forget to add a "use" statement for this annotation?
in vendor/doctrine/annotations/lib/Doctrine/Common/Annotations/AnnotationException.php:36

Removing @note:
/**
 * Create many entities with persisting them to the database.
 *
 * @param bool|null $cleanHeap Clean the heap after creating entities.
 *
 * To change the default value use {@see static::$cleanHeap} property.
 */

stops the error from occurring.

i presume the same will be true of the createOne() method.
i'm happy to submit a change for these, if someone wants to offer an alternate annotation, or make the call to just remove @note from the remark...
Suggestions?

(FWIW, my opinion is remove the annotation and combine the description with the method description:
/**
 * Create many entities with persisting them to the database.
 * To change the default value use {@see static::$cleanHeap} property.
 *
 * @param bool|null $cleanHeap Clean the heap after creating entities.
 */

It's not a valid annotation anyway, as far as i can tell.

Exceptions stemming from Doctrine annotations are a common issue. The optimal solution involves configuring Doctrine to ignore specific annotations.
This can be achieved with the following line of code:
\Doctrine\Common\Annotations\AnnotationReader::addGlobalIgnoredName('note');

This code snippet should be inserted into a bootloader to guarantee its execution at an early stage in the application's lifecycle. Ensure that this bootloader is positioned at the beginning of the system's bootloader section for optimal effectiveness.

Good to know, thanks for that!
Obviously, comments shouldn't have to be scrutinized for functional impact, but here we are.
It seems to me that if the code involved (AbstractFactory) must be parsed by Doctrine, then complying with supported PHPDoc syntax/tags is preferable to adding the functional overhead of a workaround.


Update p5 sound documentation information

Changes:

Mostly adding a capital letter to the start of the sentence.

Adding some extra information to params and/or return values.

Remove additional 'optional' texts

Remove repeated words in the same sentence

[x] npm run lint passes

[x] [Inline documentation] is included / updated

[x] [Unit tests] are included / updated

@davepagurek this PR is approved by @therewasaguy, can you please look into this and merge this PR

Thanks for pointing this one out @Abhijay007, and @Dmkk01 for the changes!


STM32F429Z Discovery STM32F429I-DISC1 with discovery guide

Hello,
Is it possible to use STM32F429Z Discovery STM32F429I-DISC1 with https://docs.rust-embedded.org/discovery/ guide?

Unfortunately not really. The generic parts do apply but the more detailed sections need some intricate adaptions.


8bitdo M30 and SF30 d-pad up direction always pressed

Flashed 1.3.7 firmware and tested on Dreamcast, PS1 and PS2. DualShock 4 works great. With 8bitdo M30 and SF30, d-pad up direction registering as pressed when it isn't. Very similar to this issue: https://github.com/godotengine/godot/issues/44721.

Did you pair it in Xinput mode? I got the sf30 and it should work in Xinput mode.

Did you pair it in Xinput mode? I got the sf30 and it should work in Xinput mode.

Yes. X + Start. Recorded:
https://www.youtube.com/watch?v=2kpEshhRn2o

Same with SF30. Japanese Dreamcast VA1.
https://www.youtube.com/watch?v=cDZyaNnHtzU

Got the same result with both my M30

Internet say the M30 as various dpad mode, you need to switch it to true dpad mode:
SELECT + DPAD UP for 5 seconds
I don't have the controller so please refer to 8bitdo instruction.


Document System.DisplayFPS

https://github.com/adventuregamestudio/ags-manual/wiki/System
  /// Gets/sets whether the engine displays the FPS counter
  import static attribute bool DisplayFPS;

Mention it is ignored if the command line flag that forces it is passed, and will always return true in the case.
mention use cases.
From PR https://github.com/adventuregamestudio/ags/pull/2608

documented in https://github.com/adventuregamestudio/ags-manual/wiki/_compare/d8f919a8217f1f95209d8f94b7f08f128fc3d95d...e0e25e77ad955e0cce070f6ed8bee585666692de
still would be nice to also link to GetEngineInteger, see https://github.com/adventuregamestudio/ags-manual/issues/260


Fix transaction attempts counter for sqlsrv

This brings back transactions attempts for sqlsrv driver

When was it removed and why?

First introduced in #1883 (well not precisely, because at that time there wasn't $attempts implemented yet, but that was the initial version of this sqlsrv condition) , then during some bug fixing in f4588f8851aab1129f77d87b7dc1097c842390db, for some reason the $attempts was omitted. For me it look like mistake, because there is no reason not to re-run transactions for (pdo) sqlsrv driver.
This is interesting because during all that time nobody noticed this (I must admit that driver is not as popular, but still..)
maybe  @GrahamCampbell can help here?

The commit you reference does not remove the parameter, but it's possible that not adding it at that point was a mistake.

I think we could go-ahead and merge this, and see if anyone complains.


Dev server middleware?

Spin off of https://github.com/modernweb-dev/web/issues/471
/cc @LarsDenBakker @benmccann
Since Snowpack's dev server is implemented directly on top of the http server, it wouldn't be too hard to expose our Dev Server as a middleware function for Express and Koa.
This is interesting because it's not about "adding dev-server functionality to Snowpack" (the previous lens we've looked at this from) but instead about "I want to build a dev server on top of Snowpack." Could Sapper, Next.js, [FAVORITE SSR METAFRAMEWORK™] build on top of Snowpack if we provided middleware for their server?

Sapper povides a middleware for Express (or Polka, etc.) that the user includes in their server. Sapper runs a process that includes Rollup as a library and runs a Rollup file watcher. Then when you change a file it creates a couple files such as your router (based off the layout of components on your filesystem), and finally bundles the client and server.
I think the biggest question for Sapper is how to create the application files such as the routing manifest. Right now that's in the Sapper dev server process. I'm not sure whether that's the best place to do it and also think it's a bit slow / inefficient at the moment.
I guess I haven't really answered your question, but thought it would be useful to share some background about how it works today and where the largest priorities are. I'm pretty time-constrained and haven't gotten to look at the dev server story much. I think @rixo and @dionysiusmarquis have perhaps investigated it a bit

That's super helpful! Interesting that you all provide a middleware as well, feels like +1 point for that being a good idea for us as well.

@FredKSchott This is actually something I was planning on trying to accomplish with the dev server testing too. I'm +1 to middleware

When I started the Sapper/Snowpack POC I started a middleware implementation for Snowpack which can be found here: https://github.com/pikapkg/snowpack/pull/430

Hi. Just to add my penny's-worth, Webpack's dev server middleware is what's keeping me with Webpack rather than switching to Snowpack (which I would otherwise be keen to do).

@overlookmotel just to be clear, do you mean this: https://webpack.js.org/guides/development/#using-webpack-dev-middleware ?

@FredKSchott Yes, that's what I meant.
While I know you can ask Snowpack to proxy API requests to another server, I prefer to run one process which (1) serves the API natively and (2) passes requests for front end assets to a dev middleware - rather than the other way around with the dev server "at the front".
For a bit more context, this is what I'm doing:
My app dynamically creates some of the modules which comprise the front end code for the front end. For example, in a React app, the components for all the pages are files on disc, but the app dynamically creates a component for the router (much like NextJS, but in my case using react-router-dom).
So, in dev mode, my app needs to be able to inject this dynamically-created router "file" (which is actually not a file on disc but in memory) into the dev server.
This is possible with Webpack as you can run the dev server in process and dynamically inject modules into Webpack's input pipeline using webpack-virtual-modules.
Apologies if I'm misunderstanding, but I don't think this is possible at present with Snowpack.
I know that a dev middleware wouldn't be the whole story to make this possible, but if Snowpack was running in my app's process, I imagine I could hack my way to "virtual modules" by shimming Node's fs module with something like memfs so the "virtual" files appear as real files to Snowpack's watcher.
Perhaps this use case is a bit niche so not worth supporting, but I just thought I'd let you know of this other possible use for a dev middleware, since you're scoping it out.

Yes! snowpack build --watch is exactly what this is for.

@FredKSchott @stramel Thanks guys! That was exactly what I was after.
We have a custom  ws connection and file watcher that reloads app on changes atm, but I was hoping to see if I can get snowpack build --watch to run the HMR server as mentioned in https://github.com/pikapkg/snowpack/pull/782#issuecomment-673719430. But I am entirely new to the codebase, so I am not sure the level of effort involved there yet.

This has been requested by enough people that I think it's clearly a useful task to prioritize. Will spin up an official issue to see if anyone is interested in tackling!

Spun off in https://github.com/pikapkg/snowpack/issues/1002

/cc @jeberly build --watch --hmr was just merged in #1002


Show report attendee positions at engagement date

Show the position that report attendees held at the engagement date (instead of at the current date), making the report as shown more historically accurate.
Closes AB#1188
User changes

Report attendees are now shown with the position they held at the engagement date of the report.

Superuser changes

None.

Admin changes

None.

System admin changes

[ ] anet.yml or anet-dictionary.yml needs change
[ ] db needs migration
[ ] documentation has changed
[ ] graphql schema has changed

Checklist

[x] Described the user behavior in PR body
[x] Referenced/updated all related issues
[x] commits follow a repo#issue: Title title format and these 7 rules
[x] commits have a clean history, otherwise PR may be squash-merged
[x] Added and/or updated unit tests
[x] Added and/or updated e2e tests
[ ] Added and/or updated data migrations
[ ] Updated documentation
[x] Resolved all build errors and warnings
[ ] Opened debt issues for anything not resolved here

Works great, if we can have the hisotrical view as well in the report summary, that would be helpful and consistent:

You report is missing an advisor organization (field is empty in the database).


Chat message.

Wondering if this message is from Panilla and if so, is there a way to disable it?

Hi, this would not happen to come from Panilla. Sorry


Add some PBC overview and PBC SCF section to user guide

My fear is that non-Gamma-point requires complex support, which I'm not
sure all molecular methods have.
On Mon, Mar 22, 2021 at 12:35 PM gkc1000 @.***> wrote:

@.**** commented on this pull request.
In source/user/pbc.rst
https://github.com/pyscf/pyscf-doc/pull/24#discussion_r598886085:

+All electronic structure methods can be applied with periodic
+boundary conditions at the Gamma point of the Brillouin zone, :math:k=(0,0,0),
+as described in :ref:mix_mol.  Converging to the thermodynamic limit
Should we say that we can use molecular methods at any point of the
Brillouin zone? Although only k=(0,0,0) corresponds to PBC. If we have a
twist averaging example in the examples directory, could link to that.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/pyscf/pyscf-doc/pull/24#pullrequestreview-617740796,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADGAJC2JO5OP72MO2X6UPTTTE5WUTANCNFSM4ZTOKM6A
.

I think almost all methods do. But we should probably have a list
somewhere. I'll put that on the todo on slack.
On Mon, Mar 22, 2021 at 9:37 AM Timothy Berkelbach @.***>
wrote:

My fear is that non-Gamma-point requires complex support, which I'm not
sure all molecular methods have.
On Mon, Mar 22, 2021 at 12:35 PM gkc1000 @.***> wrote:

@.**** commented on this pull request.
In source/user/pbc.rst
https://github.com/pyscf/pyscf-doc/pull/24#discussion_r598886085:

+All electronic structure methods can be applied with periodic
+boundary conditions at the Gamma point of the Brillouin zone,
:math:k=(0,0,0),
+as described in :ref:mix_mol. Converging to the thermodynamic limit
Should we say that we can use molecular methods at any point of the
Brillouin zone? Although only k=(0,0,0) corresponds to PBC. If we have a
twist averaging example in the examples directory, could link to that.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://github.com/pyscf/pyscf-doc/pull/24#pullrequestreview-617740796
,
or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/ADGAJC2JO5OP72MO2X6UPTTTE5WUTANCNFSM4ZTOKM6A
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/pyscf/pyscf-doc/pull/24#issuecomment-804214017, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAN5NRAILSHNFCI5KIRNV4DTE5W4FANCNFSM4ZTOKM6A
.

complex values were explicitly considered in mp2, cisd, ccsd only
On Mon, Mar 22, 2021 at 09:37:22AM -0700, Timothy Berkelbach wrote:

My fear is that non-Gamma-point requires complex support, which I'm not
sure all molecular methods have.


refactor(specs): new predict segment condition syntax

🧭 What and Why
Changing the Predict segment syntax from a string to an object that follows the proposed specification.
🎟 JIRA Ticket: PRED-921
https://algolia.atlassian.net/browse/DI-764
Changes included:

Add version to segment object
Add new conditions format to segment object

Dependencies
Do not merge until the API supports the new format. Even if the PR below is merged the changes may not have been deployed to production.
https://github.com/algolia/predict-api/pull/63

Do not merge yet. See 'Dependencies' heading in the PR description


Fix deprecated uses of Redis#pipelined

Context: https://github.com/redis/redis-rb/pull/1059
The following is deprecated
redis.pipelined do
  redis.get(key)
end

And should be rewritten as:
redis.pipelined do |pipeline|
  pipeline.get(key)
end

Functionally it makes no difference.

@casperisfine lgtm, I've made you a collaborator. What's your rubygems email?
Also full permission to move this to shopify/... it's not really used elsewhere

progressrus $ gem owner progressrus --add "<email>"
You have enabled multi-factor authentication. Please enter OTP code.
Code:   <2fa>
Adding <email>: User has already been taken

wth

Ah, I think something did happen

Accepted, thank you!


net-tools, specifically netstat is missing from Ubuntu 20.04 image

Description
Ubuntu-18.04 had the net-tools package installed. Ubuntu-20.04 does not. This is a regression in command line tools available. I'm specifically needing the netstat command for a unit test to validate that a fresh connection isn't created under certain conditions.
Area for Triage:

Question, Bug, or Feature?:  Bug

Virtual environments affected

[ ] Ubuntu 16.04
[ ] Ubuntu 18.04
[x] Ubuntu 20.04
[ ] macOS 10.15
[ ] macOS 11.0
[ ] Windows Server 2016 R2
[ ] Windows Server 2019

Image version
20210302.0
Expected behavior
netstat to be available to execute on the path
Actual behavior
netstat is missing
Repro steps
The tests for https://github.com/CoreWCF/CoreWCF execute the process "netstat -a -n" which provides a compatible parse-able output for Windows and Linux. It is expected that the netstat executable is available on the path. Note, the path of netstat has changed between Ubuntu 20.04 (/usr/bin/netstat) and Ubunutu 18.04 (/bin/netstat).

Hello @mconnew , thank you for your proposal!
Yes, the list of tool is different on Ubuntu 20.04. As for this particular tool, we don't have concerns to pre-install it on Ubuntu 20.04. Moved to backlog

Hello, @mconnew
The https://github.com/actions/virtual-environments/pull/2838 PR is merge. Awaiting for new image deployment in a week or two.

I presume this issue will be closed once it's deployed?

I presume this issue will be closed once it's deployed?

Yep, that's right.

Hello, @mconnew
The new images with net-tools package have been deployed.


Fixed modifiers causing sf::Keyboard::Unknown being returned

Fixes #1012.

Can someone else on Linux test this as well?

Bump.

Works for me: :+1: I added another patch on top of this to fix RAlt detection. Might want to merge: bugfix/unix_keyevents_ralt

I already considered this in #922, but came to the conclusion that this is a user configuration option.

It's indeed a configuration option, but we should really go with the defaults here. I asked several people on IRC to show their xmodmap output, and it has been consistent with this:
% xmodmap
xmodmap:  up to 4 keys per modifier, (keycodes in parentheses):

shift       Shift_L (0x32),  Shift_R (0x3e)
lock        Caps_Lock (0x42)
control     Control_L (0x25),  Control_R (0x69)
mod1        Alt_L (0x40),  Meta_L (0xcd)
mod2        Num_Lock (0x4d)
mod3
mod4        Super_L (0x85),  Super_R (0x86),  Super_L (0xce),  Hyper_L (0xcf)
mod5        ISO_Level3_Shift (0x5c),  Mode_switch (0xcb)

Alt_R is never mapped, so that key doesn't work at all.

My xmodmap output looks like this:
xmodmap:  up to 4 keys per modifier, (keycodes in parentheses):

shift       Shift_L (0x32),  Shift_R (0x3e)
lock        Caps_Lock (0x42)
control     Control_L (0x25),  Control_R (0x69)
mod1        Alt_L (0x40),  Alt_R (0x6c),  Meta_L (0xcd)
mod2        Num_Lock (0x4d)
mod3
mod4        Super_L (0x85),  Super_R (0x86),  Super_L (0xce),  Hyper_L (0xcf)
mod5        ISO_Level3_Shift (0x5c),  Mode_switch (0xcb)

Like I said, this depends on the user's mapping. Using English mappings will also map Alt_R because the key isn't used as a modifier. Because AltGr is a key modifier on e.g. German mappings and is used to shift keysyms, it isn't mapped on those, with reason. Switching between mappings will also add/remove the Alt_R mapping depending on the target layout. If a user really wanted to use a key that is intended to be used as a keysym shift as a "normal" non-modifier key, they would be better off configuring it to behave as such. This keeps SFML consistent with other libraries who also decided that handling Alt_R is up to the user if they have more than 1 option. Applications that aim to be "international friendly" should not endorse use of Alt_R anyway.

US keyboards don't have AltGr, but they still have an Alt key there, which is also mapped by SFML, to sf::Keyboard::Key::RAlt. On my system, it's mapped to ::Unknown, because in the same place I have AltGr, which is not mapped by SFML.
The simple question is: Why is Alt_R mapped, but ISO_Shift_Level_3 and Mode_Switch are not? All 3 symbols are triggered by the same key on the proper keyboard layouts. Even if AltGr acts as a modifier key on non-US layouts, what's the problem? Shift, Control and (L)Alt are also modifier keys, yet we map them (for good reasons).

Simple... because Shift, Control and LAlt are also present on all keyboards. If SFML were designed from the beginning to be e.g. German-centric, I could imagine there also being an sf::Keyboard::Key::Oe and sf::Keyboard::Key::Ae or similar keys, because those have to be made accessible to people who want to check for those keystrokes. However, besides being of use to people who use German keyboards (or other keyboards where they are present) they are pretty useless. If you are using a German keyboard, there is no direct, single keystroke way of triggering a e.g. sf::Keyboard::Key::LBracket keystroke either, because there is no unmodified way to get this.
The reason why you don't get RAlt using a German layout is well.... because Germans don't have an RAlt key. :stuck_out_tongue: They have an AltGr key, and that is not the same as RAlt even though some might consider it as such (if it would have been named something completely different like "Right Shift" or something there would probably be less confusion). That is one of the disadvantages of having an English-centric API, but like I said, other libraries don't do much different either.

Ä/Ö/Ü etc. are mapped to their US counterparts. The implementation is not ideal, because there are indeed many differences (this is also what's being discussed...more or less ;)), but at least I can detect key presses.
While there's no Key::Ue, I can still check for the English counterpart, and that's good enough. I can just get an image of the default US layout and can work with that. There's one key that I can't simply map, and that's less-than, because on the US keyboard they have a larger shift key there.
However, the point is: I can use the keys. But I can't use AltGr, it's completely dead. And that makes no sense, because it's at the exact same location as on the US keyboard, just without "Gr". I really don't see a practical reason why this can't/shouldn't be supported. Not being able to map keys makes me go crazy when it's technically possible, even without a keyboard layout rewrite in SFML.

I personally don't really mind if AltGr gets mapped or not, the only reason as I already mentioned why I closed my initial PR was because it diverted from what other libraries did. If consistency with other libraries in this regard is not a concern I don't have anything against your change.
@TankOs Feel free to open a PR for bugfix/unix_keyevents_ralt and/or feature/more_keys and close this PR as superseded.

So is this PR obsolete (once @TankOs implements the other bits)?

Yes.

Until the Windows and OS X implementations for #1045 are ready, this will have to take its place in order to fix #1012 for 2.4. #1045 will be rebased onto master in 2.5.

This PR has been added to my merge list, meaning it will be merged soon, unless someone raises any concerns.


Add in-scope/out-scope subsections to SECURITY-INSIGHTS.yml

#SecuritySlam
What would you like to be cleaned:
When the SECURITY-INSIGHTS.yml file was initially created in https://github.com/kubernetes-sigs/kueue/pull/1469, the in-scope / out-scope subsections of the vulnerability-reporting section were omitted, as it was not entirely clear which of the OWASP Top 10 were in/out of scope. Someone with more knowledge of the project should update the SECURITY-INSIGHTS.yml file to include this section.
Why is this needed:
Adding this section will improve the project's score on the CLOMonitor site.
/sig release

/remove-lifecycle stale

/remove-lifecycle stale

/remove-lifecycle stale
/help


[faucet] fix cors validation to allow cross domain call in browser

Overview
Adds CORS so partners can call testnet faucet from browser (e.g. website to demo javascript client). Similar to what was done for JSON-RPC https://github.com/libra/libra/pull/6558
Test

Deploy single validator locally using the provided docker-compose, which spins up on localhost:8080
Then run the faucet using the provided mint.key

$  cargo run -p libra-faucet -- -a <IP_ADDRESS> -p 8081 -c TESTING -m mint.key -s http://<IP_ADDRESS>:8080

Then use http://test-cors.org to make a mint request to my localhost from the browser:

@mgorven can I cherry pick this into release-1.0? When can we expect testnet upgrade with this?

I think a cherry-pick is fine since it doesn't affect prod.

/land

:broken_heart: Test Failed - Build images and run cluster test

/land

:broken_heart: Test Failed - Build images and run cluster test

/land

:broken_heart: Test Failed - Build images and run cluster test

/land


<EMAIL_ADDRESS>failure

Describe the bug
i am using a gcloud run deploy with source as code. it fails build step with below issue
Step #1: === Java - Maven<EMAIL_ADDRESS>===
Step #1: Installing Maven v3.6.3
Step #1: Failure: (ID: 86a1af80) Maven version 3.6.3 does not exist at https://downloads.apache.org/maven/maven-3/3.6.3/binaries/apache-maven-3.6.3-bin.tar.gz (status 404).
If you have a general question about how to use buildpacks, we encourage you to open a discussion topic instead
Additional context
How are you using GCP buildpacks?
Cloud Run
Did this used to work?
Yes
Was this working before? When did you start noticing these errors?
It was working till 8-June-2023.. and started failing June 9
What language is your project primarily written in?
(Java)
Steps To Reproduce
Steps to reproduce the behavior:

gcloud run --project="project-first" deploy test-source --source .

Expected behavior
Build and deploy the service to cloud run
Actual behavior
Build failed
If applicable, add screenshots / logs / error messages
Step #1: ===> DETECTING
Step #1: 4 of 5 buildpacks participating
Step #1: google.java.runtime      0.9.1
Step #1: google.java.maven        0.9.0
Step #1: google.java.entrypoint   0.9.0
Step #1: google.utils.label-image 0.0.2
Step #1: ===> RESTORING
Step #1: ===> BUILDING
Step #1: === Java - Runtime<EMAIL_ADDRESS>===
Step #1: Using latest Java 11 runtime version. You can specify a different version with GOOGLE_RUNTIME_VERSION: https://github.com/GoogleCloudPlatform/buildpacks#configuration
Step #1: 2023/06/09 08:05:29 [DEBUG] GET https://dl.google.com/runtimes/ubuntu1804/openjdk/version.json
Step #1: Installing  v11.0.19+7.
Step #1: 2023/06/09 08:05:29 [DEBUG] GET https://dl.google.com/runtimes/ubuntu1804/openjdk/openjdk-11.0.19_7.tar.gz
Step #1: Warning: BOM table is deprecated in this buildpack api version, though it remains supported for backwards compatibility. Buildpack authors should write BOM information to .sbom., launch.sbom., or build.sbom..
Step #1: Warning: BOM table is deprecated in this buildpack api version, though it remains supported for backwards compatibility. Buildpack authors should write BOM information to .sbom., launch.sbom., or build.sbom..
Step #1: Warning: BOM table is deprecated in this buildpack api version, though it remains supported for backwards compatibility. Buildpack authors should write BOM information to .sbom., launch.sbom., or build.sbom..
Step #1: === Java - Maven<EMAIL_ADDRESS>===
Step #1: Installing Maven v3.6.3
Step #1: Failure: (ID: 86a1af80) Maven version 3.6.3 does not exist at https://downloads.apache.org/maven/maven-3/3.6.3/binaries/apache-maven-3.6.3-bin.tar.gz (status 404).

We are working on updating the maven version to the latest and that should fix the issue with the maven buildpack.

We are working on updating the maven version to the latest and that should fix the issue with the maven buildpack.

Thank you for the reply @kappratiksha : Any ETA on this? Our customer critical production deploys are blocked. If any other alternative steps of the same, please provide steps

@juturumanoj  The issue has been fixed now. Can you try redeploying again.

Working now.. thank you..


adjust color and size of search hint

Adjust color of search hint (currently the hint is not seen) and adjust size

Change vector_tchap_primary_color_light impacts primary_color_light, which is used as application bar background color, whereas we only want to update here primary_hint_text_color_light.
In conclusion, I approve the initial changes


WIP: Treasury reference docs

This work in progress makes the SRML's Treasury reference documentation conform to the template.
It still needs

A working example? I'm really struggling on that. I think because all of the dispatchable methods are private.
Clarity on what the OnDilution stuff is about. I'm not yet stuck on this. Done

Here's where I'm stuck on the example. Help would be much appreciated
This is an attempt that I understand and is as close as I've gotten to something working.
# use srml_treasury as treasury;
# use runtime_primitives::traits::As;
# use srml_support::traits::Currency;
# type BalanceOf<T> = <<T as Trait>::Currency as Currency<<T as system::Trait>::AccountId>>::Balance;
# use treasury::Trait as Trait;
//!
# fn not_executed<T: treasury::Trait>() {
let new_pot = <BalanceOf<T> as As<u64>>::sa(200);
<treasury::Module<T>>::set_pot(new_pot);
# }
# fn main() {}

After some help I got to this which I also don't understand, but may be closer. This also does not compile.
# use srml_treasury as treasury;
# use runtime_primitives::traits::As;
# use srml_support::traits::Currency;
# type BalanceOf<T> = <<T as Trait>::Currency as Currency<<T as system::Trait>::AccountId>>::Balance;
# use treasury::Trait as Trait;
//!
# fn not_executed<T: treasury::Trait>() {
let call : treasury::Call = treasury::Call::set_pot(new_pot);
let new_pot = <BalanceOf<T> as As<u64>>::sa(200);
call.dispatch(new_pot);
# fn main() {}

I think the docs I've added represent a positive change. I hope they get merged. I'm stuck on the following and won't likely be able to proceed without some guidance.

I'm not clear why the build is failing.
I can't figure out how to write an example that actually compiles. See my previous comment for two attempts.


Firebase Phone Number Authentication

There was a request to the firebase-talk@ list about using Firebase Phone Number Authentication with Flutter.
Docs:

https://firebase.google.com/docs/auth/ios/phone-auth
https://firebase.google.com/docs/auth/android/phone-auth

Having this available will be great for emerging markets as Android is the more dominant OS and phone numbers have more penetration when compared with emails.

Our roadmap is build around this feature. A lot of mobile application now rely on this.

Flutter's firebase_auth is just a wrapper around the Firebase SDKs themselves:
https://github.com/flutter/plugins/tree/master/packages/firebase_auth
patches are certainly welcome.  @collinjackson wrote the existing wrappers.  I don't know how much work it would be to add these additional apis.

I think this would be straightforward to add, and I'd be happy to do it. But I'm doing a lot of things, so pull requests are welcome if anyone feels blocked on this.

Any Updates on this ?

+1

I would like to use this feature too. Is there a progress ?

I am needing this for a new app... Some progress?

+1

I want to build this. Is anyone available to help?

This is my attempt to add support for Firebase phone number authentication on the Android platform: https://github.com/flutter/plugins/pull/329
Feel free to provide any feedback regarding the design and implementation.

@PrimeNexes I've implemented SmartLock support in the firebase_auth_android_smartlock branch , however I couldn't test it as the hint is not coming back for the Google account I tested with.
As the Firebase UI docs mentions, I think I need to store the user's credentials in SmartLock after a successful authentication and then it'll work, as the phone number cannot be retrieved automatically by other means.

@alibitek I just want to implement phone auth it's basic feature. The current google sign in is not something that I can build upon for my app, phone auth will help me to at least have a base to built my app on.
You think this will at least give me something to work with ? Or I have to work more when the official build comes by  ?

Friendly ping :smile:

Is there any update on this?

How to do Phone authentication in Flutter using Firebase? Can anyone tell me? I need the code snippet very badly. I'm doing an App for my college. It needs the user to be verified using the phone number.

Work in progress

flutter/plugins#329
flutter/plugins#484

need it asap for more than project ,

+1

+1

Friendly ping.

Is phone Authentication can now be done in flutter ?? Is PR submitted? I want to use it

https://github.com/flutter/plugins/pull/606 is the current work and it's still work-in-progress.

Any update on Firebase Phone Auth using flutter? Is there any ETA on the horizon?

@saltpetreca flutter/plugins#606 PR is currently in review. The phone auth feature in the example provided works for me. If interested, u can test the PR by adding the following to your pubspec.yaml:
  firebase_auth:
    git:
      url: git@github.com:flutter/plugins.git
      path: packages/firebase_auth
      ref: 075897e

Thanks will take a look.
On Jul 3, 2018, at 11:42 AM, Maurice McCabe<EMAIL_ADDRESS>wrote:
@saltpetreca flutter/plugins#606 PR is currently in review. The phone auth feature in the example provided works for me. If interested, u can test the PR by adding the following to your pubspec.yaml:
firebase_auth:
git:
url: git@github.com:flutter/plugins.git
path: packages/firebase_auth
ref: 075897e
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

go to this link
https://stackoverflow.com/questions/50181000/how-to-do-phone-authentication-in-flutter-using-firebase/56823147#56823147

@sethladd
This issue has been moved to https://github.com/FirebaseExtended/flutterfire/issues/1006. Any further collaboration will be done there.

how send code in PhoneVerificationCompleted method
cuase varify the phone again


better json debug print

when error happens env,pre,alloc files are printed as json but in one line. better to print it as pretty json for readability from console log
this is how it is printed right now:
self = <evm_transition_tool.EvmTransitionTool object at 0x7fcceccd8fd0>
alloc = {'0x0000000000000000000000000000000000000100': {'balance': '0x00', 'code': '0x6000496000556001496001556002496002556003...e': '0x600049600055600149600155600249600255600349600355600449600455600549600555', 'nonce': '0x00', 'storage': {}}, ...}
txs = []
env = {'currentBaseFee': '7', 'currentCoinbase': '0x0000000000000000000000000000000000000000', 'currentDifficulty': '0x0', 'currentGasLimit': '0x0', ...}
fork = Cancun, chain_id = 1, reward = -1, eips = None

it is even shortened so I try to investigate env contents and I don't see which fields are provided

I think this is standard pytest output that just includes the local variables in the context of a test failure. Is that right?
If so, I will have a look to see if we can modify this standard behavior.
However, you can drop into a debugger directly in the terminal upon a test fail by specifying --pdb -nauto and inspect these elements.
To get a nice print in the console you can execute:
(Pdb) import json
(Pdb) print(json.dumps(alloc, indent=2))

If the object is not already a json string, you can use to_json. For example:
(Pdb) import json
(Pdb) from ethereum_test_tools.common import to_json
(Pdb) print(json.dumps(to_json(txs[0]), indent=2))

will print:
{
  "type": "0x0",
  "chainId": "0x1",
  "nonce": "0x0",
  "gasPrice": "0xa",
  "gas": "0x7a120",
  "value": "0x0",
  "input": "0x",
  "to": "0x0000000000000000000000000000000000000100",
  "sender": "0xa94f5374fce5edbc8e2a8697c15331677e6ebf0b",
  "v": "0x1c",
  "r": "0xf73b923883495dc2174285c8fa4176de3d45accfb11cc8034ea1dd09831a4ddf",
  "s": "0x1c6bccbcd655b4022bcc27de4b9d5cee9ce999cdb8459b0afec4f5054ea02243"
}

We can't display all variables within the current scope upon fail, but we can try and improve error reporting, closing in favor of #320.


useTemplateRefs falsely returns boolean

Vue - Official extension or vue-tsc version
v2.1.6
VSCode version
1.89.1
Vue version
3.5.3
TypeScript version
Not installed. When I create and open a .ts file and run TypeScript: Select TypeScript Version..., I get offered 5.4.5. Not sure if this is what you're asking for since it wasn't retrievable without the ts file.
System Info
System:
    OS: Linux 6.1 Manjaro Linux
    CPU: (4) x64 Intel(R) Core(TM) i3-7100U CPU @ 2.40GHz
    Memory: 12.27 GB / 19.43 GB
    Container: Yes
    Shell: 5.2.32 - /bin/bash
  Binaries:
    Node: 18.20.4 - ~/.nvm/versions/node/v18.20.4/bin/node
    Yarn: 1.22.22 - /usr/bin/yarn
    npm: 10.7.0 - ~/.nvm/versions/node/v18.20.4/bin/npm
  Browsers:
    Chromium: 128.0.6613.119

package.json dependencies
"dependencies": {
    "@vscode/codicons": "^0.0.36",
    "@vueuse/core": "^10.1.2",
    "vue": "^3.2.13",
    "vue-virtual-scroller": "^2.0.0-alpha.1"
  },
  "devDependencies": {
    "@vue/cli": "^5.0.4",
    "@vue/cli-service": "~5.0.0"
  }

Steps to reproduce
I pasted the official example from https://vuejs.org/guide/essentials/template-refs.html#accessing-the-refs ("Accessing the refs") into VSCode;
<script setup>
import { useTemplateRef, onMounted } from 'vue'

// the first argument must match the ref value in the template
const input = useTemplateRef('my-input')

onMounted(() => {
  input.value.focus()
})
</script>

<template>
  <input ref="my-input" />
</template>

What is expected?
No error
What is actually happening?
Property 'value' does not exist on type 'boolean'. because input is in fact shown as boolean.
Link to minimal reproduction
No response
Any additional comments?
The sample is not using lang="ts" and the link says

When using TypeScript, Vue's IDE support and vue-tsc will automatically infer the type of inputRef.value based on what element or component the matching ref attribute is used on.

So I guess for some reason it could be expected that things don't work perfectly (it would be great if you could clarify that), but type boolean surely is a bug here?! I also don't understand where it comes from as hovering over useTemplateRefs reveals a Readonly<ShallowRef> return type.

Another problem:

Trying to fix the boolean value by making a type cast using JSDoc. The typing is one thing, but ts-plugin(1005) complaining about a missing ; here as if there were a syntax error (which there isn't) looks like another bug.

You can use lang="ts" to alleviate this problem.

I encounter exactly the same problem when writing useTemplateRef inside a


TypeError: init() got an unexpected keyword argument 'model_name' when trying to train

Dear Foodseg Teams,
thank you for providing the resources for this great food segmentation tool.
I have a question. I am trying out the training on my system. However, I ran into a problem and would like to ask for assistance.
This is the exact command I am using:
CUDA_VISIBLE_DEVICES=0  python -m torch.distributed.launch --nproc_per_node=1 --master_port=12901 tools/train.py --config configs/foodnet/SETR_Naive_768x768_80k_base.py  --work-dir  checkpoints_dir/SETR_Naive  --launcher pytorch
This is what I get:
/home/cszsolnai/anaconda3/envs/open-mmlab2/lib/python3.7/site-packages/mmseg/models/builder.py:42: UserWarning: train_cfg and test_cfg is deprecated, please specify them in model
'please specify them in model', UserWarning)
Traceback (most recent call last):
File "/home/cszsolnai/anaconda3/envs/open-mmlab2/lib/python3.7/site-packages/mmcv/utils/registry.py", line 51, in build_from_cfg
return obj_cls(**args)
TypeError: init() got an unexpected keyword argument 'model_name'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/home/cszsolnai/anaconda3/envs/open-mmlab2/lib/python3.7/site-packages/mmcv/utils/registry.py", line 51, in build_from_cfg
return obj_cls(**args)
File "/home/cszsolnai/anaconda3/envs/open-mmlab2/lib/python3.7/site-packages/mmseg/models/segmentors/encoder_decoder.py", line 35, in init
self.backbone = builder.build_backbone(backbone)
File "/home/cszsolnai/anaconda3/envs/open-mmlab2/lib/python3.7/site-packages/mmseg/models/builder.py", line 19, in build_backbone
return BACKBONES.build(cfg)
File "/home/cszsolnai/anaconda3/envs/open-mmlab2/lib/python3.7/site-packages/mmcv/utils/registry.py", line 210, in build
return self.build_func(*args, **kwargs, registry=self)
File "/home/cszsolnai/anaconda3/envs/open-mmlab2/lib/python3.7/site-packages/mmcv/cnn/builder.py", line 26, in build_model_from_cfg
return build_from_cfg(cfg, registry, default_args)
File "/home/cszsolnai/anaconda3/envs/open-mmlab2/lib/python3.7/site-packages/mmcv/utils/registry.py", line 54, in build_from_cfg
raise type(e)(f'{obj_cls.name}: {e}')
TypeError: VisionTransformer: init() got an unexpected keyword argument 'model_name'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "tools/train.py", line 167, in
main()
File "tools/train.py", line 136, in main
test_cfg=cfg.get('test_cfg'))
File "/home/cszsolnai/anaconda3/envs/open-mmlab2/lib/python3.7/site-packages/mmseg/models/builder.py", line 48, in build_segmentor
cfg, default_args=dict(train_cfg=train_cfg, test_cfg=test_cfg))
File "/home/cszsolnai/anaconda3/envs/open-mmlab2/lib/python3.7/site-packages/mmcv/utils/registry.py", line 210, in build
return self.build_func(*args, **kwargs, registry=self)
File "/home/cszsolnai/anaconda3/envs/open-mmlab2/lib/python3.7/site-packages/mmcv/cnn/builder.py", line 26, in build_model_from_cfg
return build_from_cfg(cfg, registry, default_args)
File "/home/cszsolnai/anaconda3/envs/open-mmlab2/lib/python3.7/site-packages/mmcv/utils/registry.py", line 54, in build_from_cfg
raise type(e)(f'{obj_cls.name}: {e}')
TypeError: EncoderDecoder: VisionTransformer: init() got an unexpected keyword argument 'model_name'
Traceback (most recent call last):
File "/home/cszsolnai/anaconda3/envs/open-mmlab2/lib/python3.7/runpy.py", line 193, in _run_module_as_main
"main", mod_spec)
File "/home/cszsolnai/anaconda3/envs/open-mmlab2/lib/python3.7/runpy.py", line 85, in _run_code
exec(code, run_globals)
File "/home/cszsolnai/anaconda3/envs/open-mmlab2/lib/python3.7/site-packages/torch/distributed/launch.py", line 261, in
main()
File "/home/cszsolnai/anaconda3/envs/open-mmlab2/lib/python3.7/site-packages/torch/distributed/launch.py", line 257, in main
cmd=cmd)
subprocess.CalledProcessError: Command '['/home/cszsolnai/anaconda3/envs/open-mmlab2/bin/python', '-u', 'tools/train.py', '--local_rank=0', '--config', 'configs/foodnet/SETR_Naive_768x768_80k_base.py', '--work-dir', 'checkpoints_dir/SETR_Naive', '--launcher', 'pytorch']' returned non-zero exit status 1.
It looks maybe like some of the packages have incompatible versions? I am not sure.
Here are details of my platform:
Python: 3.7.11 (default, Jul 27 2021, 14:32:16) [GCC 7.5.0]
CUDA available: True
GPU 0: NVIDIA GeForce GTX 1080
CUDA_HOME: /usr/local/cuda-10.1
NVCC: Cuda compilation tools, release 10.1, V10.1.243
GCC: gcc (Ubuntu 7.5.0-3ubuntu1~18.04) 7.5.0
PyTorch: 1.6.0
PyTorch compiling details: PyTorch built with:

GCC 7.3
C++ Version: 201402
Intel(R) oneAPI Math Kernel Library Version 2021.3-Product Build 20210617 for Intel(R) 64 architecture applications
Intel(R) MKL-DNN v1.5.0 (Git Hash e2ac1fac44c5078ca927cb9b90e1b3066a0b2ed0)
OpenMP 201511 (a.k.a. OpenMP 4.5)
NNPACK is enabled
CPU capability usage: AVX2
CUDA Runtime 10.1
NVCC architecture flags: -gencode;arch=compute_37,code=sm_37;-gencode;arch=compute_50,code=sm_50;-gencode;arch=compute_60,code=sm_60;-gencode;arch=compute_61,code=sm_61;-gencode;arch=compute_70,code=sm_70;-gencode;arch=compute_75,code=sm_75;-gencode;arch=compute_37,code=compute_37
CuDNN 7.6.3
Magma 2.5.2

Package versions:
mmcv-full=1.3.10
cudatoolkit=10.1

@kanesoban Sorry for replying late. The mmcv-full version I use is 1.2.6, and it will raise error with 1.3.10. This is because the official repo of mmcv has been updated, and I will refine the instruction. BTW,  can u check whether you have successfully installed software by running:
from mmseg.apis import inference_segmentor, init_segmentor
and install all dependencies in requirements.txt?


Creating github action badges

When a beginner starts to contribute they are given a specific badge on their first successful merge. As they continue contributing, they get different badges to encourage them to contribute more🔰 and they also get personalized emails 💌 with their GitHub profile pic.

Love this idea so much 👍
Could we have a counter that increments each time someone performs an action, then later on we can decide on what badges are for each amount: For example

1: Started badge
10: On a role badge
...

This is super awesomeee, great idea @muchirijane ! @eddiejaoude do you think this Github Action could write some of this data on the database of EddieBot and EddieBotUI? If we have something like this:
{
      username: "Eddie",
      badges: [{
         name: "first-contribution",
         emoji: "🔰", // associated emoji to the badge perhaps??
         description: "This badge is achieved by making a PR and getting a successful merge"
      }]
}

then we can display this info on the UI, and show off cool badge UIs 😄.

Yes we could do that in a custom Action with javascript quite easily 👍
I think we save the statistics against the user, then in another collection or config file, map what it refers to, so we can update that more easily.
For example
Database
{
   username: "eddiejaoude"
   // ...
   statistics: {
      issue: {
          created: 10,
          comments: 15
      },
      pullRequest: {
          created: 10,
          comments: 15
       }
   }
}

Config
{
   badges: {
      pullrequest: {
          1:  {
                name: "first-contribution",
                emoji: "🔰", // associated emoji to the badge perhaps??
                description: "This badge is achieved by making a PR and getting a successful merge"
      } ,
      issues: {
          1:  {
                name: "first-contribution",
                emoji: "🔰", // associated emoji to the badge perhaps??
                description: "This badge is achieved by making an issue"
      }
   }
}

What do you all think? (ok they dont quite align, but something like that, structure needs a bit more thinking)

That's awesome @eddiejaoude and @BOLT04 . From there, different badges can be created for different levels of successful merges.

Where is this badge being displaced?

@mikeysan I was thinking we could have a markdown badge available for people to use in their custom GitHub profiles, and also on our web app (I will kick off the EddieBotUI next month)
Something like this...

I have started saving the data with a GitHub Action today 🎉 , data from GitHub in Firestore...
{
   // GitHub User
   author: {avatar_url: "https://avat...},
   id: "624760",
   issue_comment: 8,
   issues: 4,
   push: 3
}

https://github.com/EddieJaoudeCommunity/gh-action-community

I think this is still a great idea github-actions bot

Yep I agree 👍 . I will remove the label so the bot doesn't close the issue

Looks like it disobeyed you @eddiejaoude so I have removed the label again. Please revert if that was not your intention.

Looks like it disobeyed you @eddiejaoude so I have removed the label again. Please revert if that was not your intention.

Thank you @mikeysan 👍

Thank you @mikeysan 👍

Thanks @schmelto for reopening 👍

Should we transfer this issue to the api / eddiebot?

@schmelto not sure if this would be implemented in either of those repos. It could be a separate GitHub action like Eddie mentioned here.
Not sure if a discord bot could implement this, simply because of this requirement: When a beginner starts to contribute they are given a specific badge on their first successful merge.. This requires the bot to know when someone contributed, so using GitHub WebHooks (where the endpoint would be in the API) is a better use case than the bot. Perhaps there is a way to send these GitHub events through WebSockets, so the bot could react to them but I don't know about it.
How about we define a plan on how to do this and then decide where to transfer the issue? What does everyone think?

I am still keen to do this 👍 it might end up in the LinkFree repo but powered by the API

Awesome! Looking forward to it!


add some more type exports

hello again! i'm taking another shot at updating these types, as of today, the request api objects aren't exported, so if you want to get them you gotta do illegal stuff like this:
import { AppendBlockChildrenParameters } from '@notionhq/client/build/src/api-endpoints';

type Unarray<T> = T extends Array<infer U> ? U : T;

export type DerivedBlockRequest = Unarray<AppendBlockChildrenParameters["children"]>

i'd really like to just export these in the same way that BlockObjectResponse is

Hi! This will get fixed with #366, hopefully we'll be able to merge that soon.
Closing for now but thanks for the report!


remove provider admin from new heat task

Can one of the admins verify this patch?

"ok to test" to accept this pull request for testing
"test this please" for a one time test run
"add to whitelist" to add the author to the whitelist

ok to test

https://github.com/blueboxgroup/ursula/commit/08dccbe7e9407b3029eb0922d7b58dd4b98e9a55 uncommented a use or provider_admin i must've missed when i removed it originally.

:+1: It works for me. We should probably merge this as soon as possible since all other PRs are likely to fail the Jenkins build until this is in.


Run i-Code-v3 on CPU, Solve GPU VRAM problem!

I will appreciate it to provide the support or apply the following changes to be able run the i-Code-v3 on CPU.
the following changes need to apply:
/core/common/utils.py --> change np.int to np.int32
in the following files:
/core/models/model_module_infer.py
/core/models/ddim/ddim.py
/core/models/latent_diffusion/diffusion_unet.py
should add the following code:
device = torch.device("cuda") if torch.cuda.is_available() else torch.device("cpu")
and change ".cuda( )" to ".to(device)"
by applying the above changes I could run the i-Code-V3 on the CPU, but fp16 was not supported yet (on CPU mode). I appreciate it to support Running FP32 and FP16 on CPU.

Thanks! We will work on adding fp16 support on CPU.
Currerntly the model can run on fp16 GPU but can't on fp16 CPU?

Thanks! We will work on adding fp16 support on CPU. Currerntly the model can run on fp16 GPU but can't on fp16 CPU?

The code worked well on fp16 GPU (RTX 3090).
For the CPU the code does not work. because in the files that I mensioned before, "model_module_infer.py", "ddim.py", and "diffusion_unet.py", the variables set to GPU by ".cuda()" command.
To fix it I suggested to change it to ".to(device)" and define device variable by either checking 'cuda' if it is available (if not "CPU") or by user decision to run on cpu/cuda.
I already made those changes locally and code worked on my CPU without problem in normal mode (fp32).
But when I switch to fp16 and run on CPU, the code does not work.


8 axes header

This builds on the prior PR in an attempt to close #8, but might not be the best approach.

This is just a draft but wanted a second pair of eyes before I go any further -- I gave the two ths a respective class, then used select on the class to get the axes in the right place...
This made the text a little smaller and looks a little crammed, and I'm not sure it's quite scaling properly, but I'm curious on your thoughts to taking this approach...

The issue here is I used DataTable to scale the columns to the width we want, but now it looks like the axes and plots are on different scales... I think we need the scaleLinear to use the width of the DT th? Or we need to apply some appropriate transform to the plots? Curious to get your thoughts.

Yeah, like I said on the phone - this is a pain. A few thoughts:

I think that using DT to scale the widths is probably going to cause hassles. You'd almost definitely need to pull the width of the td/th element whenever the page resizes and then make the svg charts and the axes reactive. There are SO posts about doing that, but it's definitely not trivial.
I think another issue is that the padding and margin css on the  and  is different, so that is causing some mis-alignment. Probably fixable with custom css rules, but I spent an hour on it and just got annoyed and gave up. 🤯
One option would be to just disable/remove the datatables css and start from scratch. Not sure it'd help or hurt with the reactivity, but i think it'd make it easier to have a static width table with aligned headers for the plots.
Minor point - I'd delete the ranges in the header and just leave the labels (since the range data is shown in the axis).

OK - that's all I've got unfortunately. Like I said this is a bit of a pain.


click house issue

hardiks-macbook-pro.local :) cat output.csv | clickhouse-local --structure "date Datetime, tx String, points Int32, amount Float32" --Query "SELECT SUM(amount) FROM table WHERE amount < 0" --input-format CSV
Syntax error: failed at position 1 ('cat'):
cat output.csv | clickhouse-local --structure "date Datetime, tx String, points Int32, amount Float32" --Query "SELECT SUM(amount) FROM table WHERE amount < 0" --input-format CSV
Expected one of: Query, Query with output, EXPLAIN, SELECT query, possibly with UNION, list of union elements, SELECT query, subquery, possibly with UNION, SELECT subquery, SELECT query, WITH, FROM, SELECT, SHOW CREATE QUOTA query, SHOW CREATE, SHOW [FULL] [TEMPORARY] TABLES|DATABASES|CLUSTERS|CLUSTER 'name' [[NOT] [I]LIKE 'str'] [LIMIT expr], SHOW, SHOW ENGINES query, SHOW ENGINES, EXISTS or SHOW CREATE query, EXISTS, DESCRIBE FILESYSTEM CACHE query, DESCRIBE, DESC, DESCRIBE query, SHOW PROCESSLIST query, SHOW PROCESSLIST, CREATE TABLE or ATTACH TABLE query, CREATE, ATTACH, REPLACE, CREATE DATABASE query, CREATE VIEW query, CREATE DICTIONARY, CREATE LIVE VIEW query, CREATE WINDOW VIEW query, ALTER query, ALTER TABLE, ALTER LIVE VIEW, ALTER DATABASE, RENAME query, RENAME TABLE, EXCHANGE TABLES, RENAME DICTIONARY, EXCHANGE DICTIONARIES, RENAME DATABASE, DROP query, DROP, DETACH, TRUNCATE, CHECK TABLE, KILL QUERY query, KILL, OPTIMIZE query, OPTIMIZE TABLE, WATCH query, WATCH, SHOW ACCESS query, SHOW ACCESS, ShowAccessEntitiesQuery, SHOW GRANTS query, SHOW GRANTS, SHOW PRIVILEGES query, SHOW PRIVILEGES, INSERT query, INSERT INTO, USE query, USE, SET ROLE or SET DEFAULT ROLE query, SET ROLE DEFAULT, SET ROLE, SET DEFAULT ROLE, SET query, SET, SYSTEM query, SYSTEM, CREATE USER or ALTER USER query, ALTER USER, CREATE USER, CREATE ROLE or ALTER ROLE query, ALTER ROLE, CREATE ROLE, CREATE QUOTA or ALTER QUOTA query, ALTER QUOTA, CREATE QUOTA, CREATE ROW POLICY or ALTER ROW POLICY query, ALTER POLICY, ALTER ROW POLICY, CREATE POLICY, CREATE ROW POLICY, CREATE SETTINGS PROFILE or ALTER SETTINGS PROFILE query, ALTER SETTINGS PROFILE, ALTER PROFILE, CREATE SETTINGS PROFILE, CREATE PROFILE, CREATE FUNCTION query, DROP FUNCTION query, CREATE NAMED COLLECTION, DROP NAMED COLLECTION query, Alter NAMED COLLECTION query, ALTER, CREATE INDEX query, DROP INDEX query, DROP access entity query, GRANT or REVOKE query, REVOKE, GRANT, EXTERNAL DDL query, EXTERNAL DDL FROM, TCL query, BEGIN TRANSACTION, COMMIT, ROLLBACK, SET TRANSACTION SNAPSHOT, Delete query, DELETE, BACKUP or RESTORE query, BACKUP, RESTORE
I  have locally installed click house but when quering , Its giving this error

It should be --query instead of --Query

Still Its same error only.

You can try running examples from here once https://clickhouse.com/docs/en/operations/utilities/clickhouse-local


Create setup docs

Add some instructions on how to set up the app from scratch.

@frapontillo all yours


webpack_exports_info incorrect for default

Bug report

What is the current behavior?
incorrect info, default is used
If the current behavior is a bug, please provide the steps to reproduce.
https://github.com/vankop/webpack/commit/03c85918b4084b0d241cc7804c290eec1dc8d533

What is the expected behavior?
test should pass

Aditional information
If change __webpack_exports_info__.mod to __webpack_exports_info__.default all works as expected
Other relevant information:
webpack version:  master 3b700e710ddac77677fffbf4991ac123560eac73
Node.js version:
Operating System:
Additional tools:

The test is wrong:
__webpack_exports_info__.maxCount.used -> `webpack_exports_info.default.used


Fix geolocation entry in browser-platform.md

Geolocation is working for me on the browser platform, though not because of the plugin.

P.S. Thanks for your attention to the browser discussion in the PhoneGap forum and on Stack Overflow.


Remove usages of unsafe lifecycle methods

Namely willReceiveProps and willMount. These throw deprecation warnings, will be deprecated in a future version of react, and typically can be replaced by other lifecycle methods.

Also facing this problem, so would be really appreciated if someone smart can help to get this PR completed and merged!!


Remove habit tracker and pros from HomeViewController

Remove these cells from the HomeViewController and revert to look like current production version. Will have to:

remove the relevant sections (habit tracker + pros), but keep the code in a separate folder
revert to old format for "ALL GYMS", disregarding favorites for now
add back "I'M LOOKING FOR..." section

For reference:
Old HomeController before the new changes here: https://github.com/cuappdev/uplift-ios/blob/d4a2fdd0398dc28bf533e8c3c8560d936d8eafd3/Fitness/Controllers/HomeController.swift

Fixed in #157.


[CCR-124] chore: add data-testids to various elements

Proposed Changes

CCR-124: Cypress tests

add testIds to some virtuoso elements for testing

Checklist

[ ] I have added or updated unit tests
[ ] I have added or updated integration tests (if appropriate)
[ ] I have added or updated documentation / readme (if appropriate)
[X] I have verified that my changes have not introduced new lint errors
[X] I have updated the change log

Testing Instructions
Load locally and see that various table and chart related elements now have data-testids prefixed with VDS

:rocket: PR was released in v1.18.3 :rocket:


Create a grouped navigation

As our recipe book grows, we should group the recipes by tag, maybe by breakfast/lunch/dinner/snack with an expandable tree structure

Good evening, can i get guidance on how to fix this?

Good evening, can i get guidance on how to fix this?

hi @OmoBolarinwaye - we'd have to read through the VuePress docs. It's probably a manual fix to config.js


First attempt at GH Action updates

@d3r3kk FYI - the Better security practice is now to reference the hash commits of GH actions (as vX is an alias that can be updated under the hood) and comment on the side, Dependabot has been updated to cope with this new practice.

@d3r3kk FYI - the Better security practice is now to reference the hash commits of GH actions (as vX is an alias that can be updated under the hood) and comment on the side, Dependabot has been updated to cope with this new practice.

Oh interesting. Then I rescind all comments to that effect.


nRF5 platform makefile is not building all source code

Problem
The following files are not being built, as they are heavily dependent on removed code (as part of #104 )
ConfigurationManagerImpl.cpp
ThreadStackManagerImpl.cpp
GroupKeyStoreImpl.cpp
SoftwareUpdateManagerImpl.cpp
Entropy.cpp
Removed from src/platform/Makefile.am
Proposed Solution
Fix the code, and add to makefile.

ConfigurationManagerImpl.cpp was fixed by 9267c5b136d68428b3524e4f1d80b60fafbd4a0a.
Thread stack is already built and up.
Group key store, Entropy and SoftwareUpdateManager seems not used on any platform.
I don't think this is a blocking issue for project nRF5 platform.


How to pass message.reply_channel to background worker like Celery?

Let's say I have a long running process in a Celery task that is started by Channels websockets. I want to use message.reply_channel to send a message back to the browser client that the long running process has completed.
Or put another way, I want to be able to save the reply address so that I can do something and later still send a message to the client that requested the work. Printing out message.reply_channel gives me this:
websocket.send!hYQTrNNbMQpA
I assume that is the unique identifier for the browser client that is suppose to receive the response but I'm having trouble figuring out how to send the message back to him.

Right - just pass that string along to a background task, and then use this to send messages to it:
from channels import Channel

def some_task(...):
    Channel(reply_channel_name).send(text=your_content_here)

You can treat Channel(name_of_reply_channel) exactly the same as message.reply_channel.

Thanks. That solved it. :)


Added $ to mask Root...

If you are not running on a RPI och a ATB the "grep /" will not give the correct values.
If you add the "$" to the grep it will only pull the line that "ends" with a "/" and that's usually the Root disk. :)
Works for me on my NUC at least. :)

Thanks for contribution.


Add The Huffington Post to fakenews extension.

The Huffington Post is about as fake as Breitbart, which is included in the list. It should be included for consistency.
Alternative to #249

Thanks for the PR.
Fake news is curated here:  https://github.com/marktron/fakenew
Closing.

Sorry about that, thanks for the pointer.


Clarifying polyfill setup

Hi folks! Quick question - it seems like we use polyfill.io on one hand and also have babel-polyfill package on the other hand? I'd love to understand the how's and why's!
Also, would happy to PR to the docs if we so feel the need!
Thank you!

Looks like babel-polyfill is included in the dev deps, but isnt actually used anywhere.

I'm also having this doubt

@sergiokopplin @strues So safe to take it out?

Not sure. I'm having a doubt about the use of both

I think it is used by Jest... but worthwhile checking :)

Quick check shows babel-polyfill is only used by babel-cli, which installs the polyfill automatically and behind the scenes.
info Has been hoisted to "babel-polyfill"
info Reasons this module exists
   - "babel-cli" depends on it
   - Specified in "devDependencies"

It's save to remove from the devDeps IMO.

Closing this issue since the PR is in next.


Missing order of CaseStatements in SwitchStatements (fall through)

Currently, there is no way to determine the order of the CaseStatements in a SwitchStatement, other than traversing the EOG and tracking if we reach another CaseStatement or a BreakStatement. I would suggest to wrap the content of a CaseStatement/DefaultStatment in a CompoundStatement, and to include a next edge for every CaseStatement to the one that is defined afterwards. The order of the CaseStatements is required when performing the control flow sensitive pass on the DFG, in order to be able to combine two cases, if a fall though is detected.
Considering the following snippet, the possible values for the print would be 0 and 12.
public class ControlFlowSesitiveDFGSwitch {
  void func3() {
    int swithVal = 3;
    int a = 0;

    switch (swithVal) {
      case 1:
        a = 10;
        break;
      case 2:
        a = 11;
        break;
      case 3:
        a = 12; // Fall through, as no break
      default:
        System.out.println(a);
        break;
    }

    int b = a;
  }
}

Suggested graph:

After discussion with @konradweiss  we decided that this issue is not necessary for the implementation of the Control Flow Sensitive DFG when handling SwitchStatements with Fallthrough.


change:flexdatalist not fired if replacing one character

When binding to the "change:flexdatalist" event then this event is only fired if adding or removing charecters.
Eg:
If the input has the following text "abc" and I select the character "c" and then hit "d" then there is no "change" event fired.

Maybe you can try adding "data-min-length" in your input field.
<input type="text" class="flexdatalist" data-min-length="1" list="listName" />


refactor(main-nav.tsx): remove unused import of Badge component

The import statement for the Badge component was removed as it was not being used in the MainNav component. This improves code cleanliness and removes unnecessary dependencies.

👍


doesn't easily install on Mac OS

I had trouble installing this on Mac OS (10.14.6) due to Apple clang not supporting OpenMP by default, so I got the error message when I ran 'make':
clang: error: unsupported option '-fopenmp'
So a more Mac-friendly installer or a pre-compiled binary would be appreciated.
Regards, Eric

Eric,
Thanks for the interest, and sorry about the difficulties.  Unfortunately, NGmerge is supported on Linux only.  I do not have a Mac and so cannot assist at all.
John Gaspar

I was able to get this working by installing libomp from homebrew:
brew install libomp
Then modifying makefile's CFLAGS:
CFLAGS?=-Xpreprocessor -fopenmp -lomp


bond on aarch64 is failing with unsupported LLVM

Hi,
I have setup LLVM to clang version 15.0.6,
but on compilation of bond i get error saying it only supports llvm 6
base-orphans        > [1 of 2] Compiling Data.Orphans
base-orphans        > You are using an unsupported version of LLVM!

What is the plan to add support for later clang versions, or any specific reason to keep it at 6.0
Also, if i have to compile bond in cross-platform model (Host-> x86_64 and target -> aarch64) is it currently supported, if yes what are the required steps  over it?

Bond doesn't have good support for cross-compilation, and this isn't something that we plan to invest in at present. The architectures we target with full support are only x86 and x64 only.
Given this, we have no plans to improve the support for ARM or other versions of LLVM.

Bond doesn't have good support for cross-compilation, and this isn't something that we plan to invest in at present. The architectures we target with full support are only x86 and x64 only.
Given this, we have no plans to improve the support for ARM or other versions of LLVM.


Contributing guide line

thank you thank you thank you! This is awesome mashallah :)

i fix this soon, thanks for review 😊

@mmahalwy : i rebased the project, so U will see much difference in files.

@mahboob-awan hmmm... seems like something happened there and shouldnt commit so many files. Can you either try rebasing again (git pull --rebase origin develop) or create another branch off of develop with just the CONTRIBUTING.md file?

@mmahalwy : sure, i create a new branch.


Verbosity header

added step 14 demonstrating the usage of the accept-verbosity header

the dataview id was changed to prevent conflicts in OCS with the python sample. I believe this is the cause of some of our recent pipeline failures when it tries to find "ambient_temp" but only sees "AmbientTemperature". The C# and Python naming conventions produce each of those, and if the sample runs aren't cleaned up properly then the samples will fail when encountering each other. Rather than make the samples non-standard naming (snake_case in C# or PascalCase in python), changing this data view ID to not be the same as the python sample should resolve any future problems.


feat: sponsor - page redesigned (contact us component uncompleted

feat:sponsor - redesigned (contactUs component uncompleted)

feat: sponsor - redesigned (ContactUs component uncompleted)

fix: sponsor page contact us section and begin section modified


Feature Req: Add Option to remove/flatten all clipPath and all mask elements

SVGs exported from Adobe Illustrator make often extensive use of clipPath and mask elements. Sometimes those clipped or masked elements are as big as the image even if the part displayed in the end is very small. Those are very slow because of multiple layers redraw and also tend to bloat the code. A clipPath applied on a closed curve or a polygon can be easily replaced by a single curve with a simple boolean operation.
In my tests with Inkscape I've found that an svg file with 5-6 layers of complex closed curves + clipPaths exported from Adobe Illustrator can be flattened with boolean operations and resulting in a single merged element made of closed paths with no loss of quality.
Masks can be also transformed in flat shapes using alpha colors and bezier curves.
The result is identical to the original svg image, only flattened and with reduced overdraw.

Path merging and computation is a complex topic. Can you suggest an effective algorithm (i.e. better then O(n²))?

I have this problem as well when trying to optimize an SVG that has the world map in vector format, and only part of it is shown by masking... Any solutions for optimizing such SVG with Sketch or Illustrator (or other but those I mainly use)?

Any update on this?

No update and unlikely there will be in the near future. I have no idea how to do this effectively. It's better to do such thinks in an image editor.

How about this: https://gist.github.com/timo22345/9413158 ?

Seems like it's just converting to shapes applying transforms and applying transform. Nothing to do with clip-paths.

https://github.com/w8r/martinez/ is a very good tool to compute intersections between polygons. Might be a good approach.

This would be a very nice feature. I work frequently with SVGs converted from other formats like DWG and these files also contain a lot of layers and invisible (clipped) paths. Removing them would greatly reduce the file size.

This would be a very nice feature. I work frequently with SVGs converted from other formats like DWG and these files also contain a lot of layers and invisible (clipped) paths. Removing them would greatly reduce the file size.

A work in progress implementation of such clipping: https://github.com/ACTIVmap/svg-to-stl

A work in progress implementation of such clipping: https://github.com/ACTIVmap/svg-to-stl

Any news on this?

Any news on this? This appears to be a useful functionality for SVGO.

For anyone stuck on this, check out this StackOverflow answer: https://stackoverflow.com/a/70278985
I'd love to see this incorporated into svgo - looks like a pretty straightforward use of paper.js's intersect function.

Anything on this yet?

I wrote a gist that might help: https://gist.github.com/akre54/4d9ace17fb27d0507a6c790be5047e3d

I wrote a gist that might help: https://gist.github.com/akre54/4d9ace17fb27d0507a6c790be5047e3d
@akre54 I've been looking for a tool to replace the use of masks and clipping paths in some SVG files by "flattening" them... would this be the thing to do it?

@aetinx it's been a while but that code should point you in the right direction. It uses paper.js and the intersect function to remove clipping paths and masks, just outputting a path that is the intersection with the clipping path.

@aetinx it's been a while but that code should point you in the right direction. It uses paper.js and the intersect function to remove clipping paths and masks, just outputting a path that is the intersection with the clipping path.

@akre54 I sure hope someone with a bit more knowledge would be able to help make a proper tool for this down the line... or add it to SVGO.
Some of my pain points:

Files in question:


Unable to deploy HA cluster using ECKO internal load balancer using automation tooling

hi
I'm working on an automated Replicated deployment using Kurl and orchestrating it with Ansible. Our goal is to have a fully automated deployment of Replicated HA cluster and applications without requiring any human intervention.
I want to use the EKCO internal load balancer capabilities for the control plane HA but when trying to deploy it using Ansible I'm getting the following error:
kubernetes.loadBalancerAddress required

I'm using the ha advanced flag to enable the HA capabilities and I have tried enabling the EKCO internal load balancer both via the command line ekco-enable-internal-load-balancer option and the enableInternalLoadBalancer entry in the installer specs.
When executing the command interactively, I'm getting the following output that I can just press enter and continue, but that prevents a fully automated deployment:
If you would like to bring your own load balancer to route external and internal traffic to the API servers, please enter a load balancer address
HAProxy will be used to perform this load balancing internally if you do not provide a load balancer address.
Load balancer address:

I have seen at https://github.com/replicatedhq/kURL/blob/a5dc3abda6f78804d68e1c82ba4def3d79df6171/scripts/common/prompts.sh#L212 that the installer will bail if no interactive shell exists. However I have not been able to find how to tell installer to use the internal load balancer using non-interactive means. How could I this?
More generally, I have noticed several call to the prompts_can_prompt function in https://github.com/replicatedhq/kURL/blob/main/scripts/common/prompts.sh shouldn't all the locations where prompts might be required have non-interactive means to avoid the prompt?
Thanks!

Please try running the script without the ha flag and only the ekco-enable-internal-load-balancer or ekco.enableInternalLoadBalancer property. This is a quirk that should be fixed.
curl https://kurl.sh/latest | sudo bash -s ekco-enable-internal-load-balancer

https://kurl.sh/docs/add-ons/ekco#internal-load-balancer

Hi @madrover,
I am closing this one as sorted out based in the above comment.
However, feel free to re-open if you think that is required.
Thank you for your attention.


Checking the possibility of a one-poll-functionality

I want to ask for a litte "reprogramming". Our little one is said to go to child care. The nurses want to use your uploader in combination with the Contour Next Link. But they will not be near our child at all times. So they will not stand next to him until the next poll is done. They would like to stand next to him, push a button and read out the data immediately.
I know, that there is a "read out data" function in the menu.
But, and this is a question, would you be so kind to program it that way, the a "bigger" button is on the main screen of your uploader (there where the logging is collected), please?

Lennart answered:
There used to be a button there, and it was moved to the menu by request, and to match Material Design patterns (as it is generally an infrequently used button).
So it’s possible to add a button, but I don’t think I’d want to add that as a UI element that’s always there for everyone.
And then there’s the question of whether to add it to the main logging area, or as part of the menu bar at the top.
Are you open a ticket on GitHub so that we can further the discussion?

Dear Lennart,
thanks for reply!
You are absolutely right. The suggestion I made is just an individual one. We want to use your Uploader as a "non-stinging glucometer". Our child is not willing to wear a mobile connected to the Contour Next Link all the time ... he is just too small.
May be there should be an entry in the menu that allows to decide where the poll-button is located? ;)
Kind regards.

@er0780 This is a 'curious' request for your use case. Why not just have the care person look at the pump screen as the live SG reading will always be shown there?
The uploader device just needs to be close and if it's generally in the same room and not overly blocked it should be picking up data whenever in range.

@Pogman
No, it is not. ;)

The persons in the child care are child care nurses without any medical background. By law they do not have to do anything with a child having Diabetes. If they have a look on the blood sugar values it is just a personal kindness. So we cannot demand, we have to ask for.

The child care cares for about 100 children. They have a common dining room. And the group of our child is located in 2 room which they can use at any time. Each of this rooms has about 30 m^2.

Ok but just the very nature of bringing the device into the same room as the child will likely have done the reading automatically without needing interaction. A manual poll will sometimes be deferred, sometimes up to 60 seconds, to avoid pump/sensor radio clashes and a reading may take some time to complete anyhow.
I'm still on the curious end here :) as I would be wary of leaving a T1 child with any carers that did not understand their needs and being able to do finger bg's, boluses, deal with hypos etc.

I forgot an additional tip for use when a device is often in/out of range: In the uploader settings enable the 'double polling if pump is away' - this will attempt to poll every 2.5 minutes and reduce the need to wait even more.

Actually have a potential solution to this without the need for any UI mods:
If the uploader has not gotten a reading at the last poll time (greater then 5 minutes passed) and the device is picked up and the app opened, it will automatically engage a poll at that moment without any delay ie. will not wait until the next scheduled poll time . No button pressing required.

Both comments / ideas are interesting. I will check this!
But I will be open for further discussions.
As a comment: Child care nurses care for the children. For medical issues we have medical nurses. The are independent of the child care and self-reliant. They come around for the meals, handle blood glucose sugars, calculations and bolus.
This is our system. We have to accept or ... nothing.

Fedback:
Both opportunites you mentioned work, but they are not always working. So it is fine but not perfect.

The last item I mentioned is only a proposed enhancement and is not currently part of the uploader.
RE: If the uploader has not gotten a reading at the last poll time (greater then 5 minutes passed) and the device is picked up and the app opened, it will automatically engage a poll at that moment without any delay ie. will not wait until the next scheduled poll time . No button pressing required.

Ah. But sometimes it works.
I tried again ... It is only working when running the app and connecting the Contour Next Link to the mobile.

It does, when cnl is reconnected or app has been started from being fully closed or phone is restarted.

Exact.

Will resolve this by running "Get Data now" on app open. This seems like a reasonable generic implementation, since when anyone opens the app, they would want to see the most recent data.

Closed - completed and available in 0.7.0 release


Posting BOOL serializes differently between 32-bit and 64-bit devices

I am posting BOOLs for a service call and it's mapping differently between 32-bit and 64-bit devices.  On 32-bit devices, BOOLs are of type NSNumber and so they map to 0 and 1.  On 64-bit devices, BOOLs are recognized as __NSCFBoolean and are mapped to true and false.
32-bit:

64-bit:

I tried using a custom value transformer but those aren't called at the serialization layer.  For now, I have changed the bool properties on the model object to be lowercase c-type bools but I would like to get a value transformer working so that this issue is resolved globally for my app.

This should be fixed with RKValueTransformers v1.1.2

@segiddins I have the latest and it's still an issue.

Please share a reproducible test case?

@segiddins Can you direct me to the serialization mapping test cases within the Restkit project?  I couldn't locate them.

RKObjectParameterizationTest.m

Object parameterization does not really use the transformers, since there is no destination class.  So I don't think the transformer change affects this (that was a separate bug). It's a difference of what -valueForKey returns for BOOL properties between 32 and 64 bit.  On the latter system, the CFGetTypeID() returns the CFBooleanGetTypeID(), and NSJSONSerialization always converts those to JSON true/false (which makes sense).  It's just that BOOL properties had mapped to 0/1 before.  I'm not sure this is definitely a bug, since true/false would seem to be the better JSON values, but... the question would be consistency.
The following is something of a test case, if you want to enforce always 0/1:
@interface BoolValueTest : NSObject
@property (nonatomic) BOOL boolValue;
@end
@implementation BoolValueTest
@end
[...]

- (void)testWriteJSONBooleanMapping
{
    RKObjectMapping *mapping = [RKObjectMapping requestMapping];
    RKAttributeMapping *attributeMapping = [RKAttributeMapping attributeMappingFromKeyPath:@"boolValue" toKeyPath:@"boolean-value"];
    [mapping addPropertyMapping:attributeMapping];

    NSError *error = nil;
    RKRequestDescriptor *requestDescriptor = [RKRequestDescriptor requestDescriptorWithMapping:mapping objectClass:[BoolValueTest class] rootKeyPath:nil method:RKRequestMethodAny];
    BoolValueTest *object = [BoolValueTest new];
    object.boolValue = YES;
    NSDictionary *parameters = [RKObjectParameterization parametersWithObject:object requestDescriptor:requestDescriptor error:&error];
    NSData *data = [RKMIMETypeSerialization dataFromObject:parameters MIMEType:RKMIMETypeJSON error:&error];
    NSString *string = [[[NSString alloc] initWithData:data encoding:NSUTF8StringEncoding] stringByReplacingPercentEscapesUsingEncoding:NSUTF8StringEncoding];

    XCTAssertNil(error);
    XCTAssertEqualObjects(string, @"{\"boolean-value\":1}");
}

Any update on this issue?


how to use onnxruntime-gpu？

On window platform, CPU usage will be above 80%.
So I want to change onnxruntime to onnxruntime-gpu
But I have the following problems：
Traceback (most recent call last):
File "demo_webcam_smooth.py", line 124, in
main(args)
File "demo_webcam_smooth.py", line 29, in main
from FaceBoxes.FaceBoxes_ONNX import FaceBoxes_ONNX
File "d:\Python\3DDFA_V2-master\FaceBoxes\FaceBoxes_ONNX.py", line 16, in
import onnxruntime
File "D:\anaconda3\envs\Vtuber\lib\site-packages\onnxruntime_init_.py", line 13, in
from onnxruntime.capi._pybind_state import get_all_providers, get_available_providers, get_device, set_seed,
ImportError: cannot import name 'get_all_providers' from 'onnxruntime.capi._pybind_state'
Can anyone point me in the direction of using onnxruntime-gpu?

Hi, when i run demo.py ,the error :Error in `python': double free or corruption (out): ?do you occur to the problem?

This repo is not tested for onnxruntime-gpu, so there may be some workloads to implement it but the code change maybe small.
Sorry for that I have no time for this feature now. BTW, welcome for related PRs : )

TKS for your help. when I not use the onnx,
python demo.py -f examples/inputs/emma.jpg
*** Error in `python': munmap_chunk(): invalid pointer: 0x00007f7a39596ce0 ***?
would you like help me solve the error? TKS very much


Skip prereleases of readable.css in the CI workflow

Until now the algorithm would assume that the latest release on Codeberg is always a final release.
There is the very real possibility of prereleases, which we've learned today, but we can easily use jq to filter these out.
This relates to #19 and fixes #20.

Woohoo! 🎉
To be fair to y'all, I'd never given a prerelease a thought either until today when my internal monologue said "You've done the work, but… this doesn't feel like it's been fully tested. Maybe get more eyes on it."
;)

Question—why use sed to remove the surrounding quotes when you can use the -r/--raw-output flag to get the raw value? Looks like that's what you used to do.

(ignore the post I just deleted, if you saw it; I misread the diff)

(ignore the post I just deleted, if you saw it; I misread the diff)

I will not, good Sir! 🤣
sed is my workaround for when I forget about the -r|--raw option in jq. I would have forgotten it today, if I hadn't looked at a StackOverflow answer for how to select array entries based on a condition. 😅

Sounds like we're all tooling up our jq skills today. I used it to update my universal comic downloading script (~/.local/bin/ucd in my dotfiles repo on codeberg) to store settings as json rather than my custom pipe-separated list, so that I can add more options and optional settings.
The most complicated jq command I've constructed was for my bash-based web crawler:
jq -rn \
	--arg title "$title" \
	--arg description "$description" \
	--arg author "$author" \
	--arg url "$url" \
	--arg generator "$generator" \
	--arg language "$language" \
	--arg icon "$icon" \
	--arg feeds "$feeds" \
	--arg meLinks "$meLinks" \
	--arg keywords "$keywords" \
	--arg usesJavascript "$usesJavascript" \
	--arg adsDetected "$hasAds" \
	--arg trackingDetected "$hasTracking" \
	'{url: $ARGS.named.url, title: $ARGS.named.title, description: $ARGS.named.description, author: $ARGS.named.author, generator: $ARGS.named.generator, language: $ARGS.named.language, icon: $ARGS.named.icon, javascript: {uses: $ARGS.named.usesJavascript | inside("true"), adsDetected: $ARGS.named.adsDetected | inside("true"), trackingDetected: $ARGS.named.adsDetected | inside("true")}, meLinks: ($ARGS.named.meLinks | split("\n")), feeds: ($ARGS.named.feeds | split("\n") | map(split("\t")) | map({type: .[0], title: .[1], href: .[2]})), keywords: ($ARGS.named.keywords | split("\n") | map(split(" ")) | map({keyword: .[1], weight: .[0] | tonumber}))} | tostring'

There is no 🤯 emoji as a quick response.

A clear oversight on GitHub's part. ;)
Yeah, I learned a ton of crazy terminal tricks during that effort to code a web crawler in bash. I'm glad I did it, even though I ended up switching to python. Great learning experience.

@rluetzner Apologies for the delay on just now getting back to this.  I trust that this works but do you have any way to test it locally just in case? I forget what we did to test initial setup but I think we did something...
Either way I'm fine with just merging this as it wouldn't be a breaking change if it fails but would prefer it tested first if at all possible.

No worries. 🙂
I did not go through the whole process again (the last time I manually set an older version in the .css files), but I did verify the small part I changed.
The logic is more or less the same, except that we no longer grab the tag_version of the first element in the json response we get from Codeberg. Instead, we look for the first entry that is not marked as a prerelease.
Everything else remains the same. We take the tag_version, compare it to what we have and if it's changed, we'll get a new pull request with the changes.
Just as a sanity check, I also ran through the whole thing once it was done, to make sure that it changes nothing.
Do you think that's enough?

From my end it should be enough; if there's ever a release you shouldn't update to, I'll be marking it as a pre-release.


Fix arrayLowercase

Closes #316

[x] Running yarn lint does not trigger any linter errors
[x] The test of the method you have fixed is passing
[x] You have written a new skeleton method for someone else to work on!
[x] You have written tests to accompany your skeleton method

Added new method called symmetricDifference.

Bingo! Thanks for the contribution. If you could open an issue for your new function it would be very helpful.

Sure, I'll do that.


InputActionEvent propagated only one time

Godot version:
3.2.1 stable
OS/device including version:
Linux Mint 19.3, Firefox, Chrome, Android
Issue description:
I'm trying to emit custom event action to my game in order to deal with multitouch. So I create an action named "touch" and try to pass it to the tree like this :
var action = InputEventAction.new()
action.pressed = true
action.action = "touch"
Input.parse_input_event(action)

The code above is the one recommended in docs and is triggered when a button is pressed.
However, when I try to receive this event in the rest of the tree like this :
func _process(delta):
	if Input.is_action_just_pressed("touch"):
                print("touched")

The event is only received once, even if a emit it multiple times (by spamming the button)
Two things I noted :

the problem concerns Input.is_action_* methods only. Nothing wrong with methods such as _input()
when I use Input.is_action_pressed() instead of Input.is_action_just_pressed(), sometimse the action is received, and sometimes it's not.

Steps to reproduce:
Just add a button to a scene and create a custom action (using the code above) when the button is pressed.
Try to use Input.is_action_pressed("name_of_the_action") and see if the action is triggered.
Minimal reproduction project:
InputActionIssue.zip

I believe it's because you're generating a "pressed" event, but never create a "released" event. So, if you click 10 times in the button, it's the equivalent of having 10 fingers on the screen at the same time.
Maybe you should instead connect to the bottom_up and bottom_down signals, and generate the respective events, to fix this:
func _on_Button_button_down():
	var action = InputEventAction.new()
	action.pressed = true
	action.action = "touch"
	Input.parse_input_event(action)

func _on_Button_button_up():
	var action = InputEventAction.new()
	action.pressed = false
	action.action = "touch"
	Input.parse_input_event(action)

Ooh, Now, it actually make sense. I didn't get that an action had to be created for both state (pressed and not pressed). But this seems perfectly consistent. And the snippet you sent works great. Thank you so so much !

Closing as not a bug.


Fix the inconsistent use of the DROP keyword in DDL

Currently, we use DROP in DDL somewhat inconsistently and confusingly to:

Revert to the default or inherited value  (DROP default).
In specific cases, like DROP REQUIRED, to set the field to a falsy value.
To actually delete a schema object, such as DROP PROPERTY.

To fix this we:

Introduce the RESET <field> syntax instead of DROP <field> to revert
the field to the default or inherited value.

Replace uses like DROP REQURIED with appropriate SET syntax using a
complement, specifically:

DROP ABSTRACT replaced with SET CONCRETE
DROP FINAL replaced with SET NONFINAL
DROP DELEGATED replaced with SET NONDELEGATED
DROP OWNED replaced with SET INHERITED

The remaining use of DROP denoting an object deletion is thus consistent
and unambiguous.
Fixes: #2031

DROP ABSTRACT replaced with SET CONCRETE
DROP FINAL replaced with SET NONFINAL
DROP DELEGATED replaced with SET NONDELEGATED
DROP OWNED replaced with SET INHERITED

Maybe instead of CONCRETE / NONFINAL / NONDELEGATED we use NOT ABSTRACT, NOT FINAL, and NOT DELEGATED?
I know it's less "english-like", but it's also fewer unreserved keywords and things to remember.

Maybe instead of CONCRETE / NONFINAL / NONDELEGATED we use NOT ABSTRACT, NOT FINAL, and NOT DELEGATED?

Yeah, that works too.

The trio of SET REQUIRED, SET OPTIONAL and RESET REQUIREDseems odd. Why RESET REQUIRED as opposed to RESET OPTIONAL? It seems that this kind of situation should be more like SET REQUIRED := True, SET REQUIRED := False and RESET REQUIRED. I think that this would be ultimately less confusing and easier to understand and remember.
DDL is a low level language, but it's still something a regular user might need to look at when inspecting proposed migration steps for SDL migrations. So seeing SET OPTIONAL vs RESET REQUIRED may be more confusing than SET REQUIRED := False vs. RESET REQUIRED.

The trio of SET REQUIRED, SET OPTIONAL and RESET REQUIREDseems odd. Why RESET REQUIRED as opposed to RESET OPTIONAL

There's no reason not to offer RESET OPTIONAL too.

It seems that this kind of situation should be more like SET REQUIRED := True

Which makes ALTER inconsistent with CREATE, where qualifiers are specified as keywords as opposed to SET <field> := <value>.
Fundamentally, qualifiers are essentially a bitmask.  SET <bit> and RESET <bit> make sense.  Yes, some of the bits are complementary to each other and "reset" the other bit, and I don't see a problem with this.

There's no reason not to offer RESET OPTIONAL too.

Well, ease of reading would be a good reason. Also parsing and then code-genning user DLL. Are we actually going to keep 2 separate AST nodes for RESET REQUIRED and RESET OPTIONAL? This is even more confusing... remember that this is already a bit of obscure DDL and what we're doing is creating a distinction without a difference which will make end-users wonder whether there's some subtle effect of RESET REQUIRED that's different from RESET OPTIONAL.
This just seems like an invitation to write less consistent DDL for no actual benefit, but also making it slightly harder to read/skim.
Regarding consistency, I think comparing SET REQUIRED/OPTIONAL and RESET REQUIRED should really be compared to whatever the equivalent of those 3 is going to be for default as you mentioned on the call. These 2 have the benefit of being in the same category that needs those 3 options: set value, set explicit "nothing", set to inherited. On the other hand the data type is different and default normally appears with a :=, so re-using it in the SET/RESET scenario is not so great. My point is that if syntactic consistency is what we're after we should make sure that the syntax rules work well enough for both required and default as good representatives of the kinds of fields that we need to tinker with.

Are we actually going to keep 2 separate AST nodes for RESET REQUIRED and RESET OPTIONAL?

No.  In fact, the production is RESET <ident>, and there's only one AST node for everything.

but also making it slightly harder to read/skim.

Hm.  So you think the inconsistency between CREATE REQUIRED LINK and ALTER LINK SET OPTIONALITY := false doesn't make it harder to read DDL?

Are we actually going to keep 2 separate AST nodes for RESET REQUIRED and RESET OPTIONAL?

No. In fact, the production is RESET <ident>, and there's only one AST node for everything.

Perhaps I worded it wrong, but what I mean is whether we would generate different ASTs (with different values) for these two: RESET REQUIRED and RESET OPTIONAL.
If yes, then this seems like begging for more compiler hacks (or duplication) that still needs to treat them exactly identically.
If no, then user says: RESET OPTIONAL you potentially echo RESET REQUIRED in your migration commands and this is ever so slightly confusing. Not much, but this is not user brainpower well-spent.

but also making it slightly harder to read/skim.

Hm. So you think the inconsistency between CREATE REQUIRED LINK and ALTER LINK SET OPTIONALITY := false doesn't make it harder to read DDL?

Not quite. Since REQUIRED is the non-default keyword I would go with:
CREATE REQUIRED LINK and ALTER LINK SET REQUIRED := true. I do understand that it also means that I'm OK with this: CREATE OPTIONAL LINK and ALTER LINK SET REQUIRED := false
But I do think this is less confusing than having:
CREATE TYPE Foo {CREATE REQUIRED PROPERTY bar -> str};
CREATE TYPE Bar {CREATE OPTIONAL PROPERTY baz -> str};
...
ALTER TYPE Foo {ALTER PROPERTY bar {RESET REQUIRED}};
ALTER TYPE Bar {ALTER PROPERTY baz {RESET OPTIONAL}};

...and weirder still, someone could also write
ALTER TYPE Foo {ALTER PROPERTY bar {RESET OPTIONAL}};
ALTER TYPE Bar {ALTER PROPERTY baz {RESET REQUIRED}};

And it would have the same effect but be a bit confusing when reading. Did the person forget? Did they mean a different type? Is this outdated?
I'm basically putting myself in the shoes of a user who doesn't do DDL very often, so they might view DDL commands once in a while, perhaps to track some other issue. It seems that making it possible to write RESET REQUIRED/OPTIONAL both ways will just make the task of looking though the DDL a bit harder.

How would you go about cardinality in your approach?  SET MULTI := false?

How would you go about cardinality in your approach? SET MULTI := false?

Either that or even using the enum we have. So either SET MULTI := false or SET CARDINALITY := <schema::Cardinality>'One'. I realize that we drifted to where we are now in part while trying to get away from the bulky cardinality cast expression, so I'm not a big fan of the cast.

I've updated the PR to use the NOT <FOO> keywords and done a few more cleanups and generalizations.