Unable to install mediapipe-model-maker==<IP_ADDRESS> on iMac

OS Platform and Distribution
macos Ventura 13.3.1 (a) (22E772610a
Compiler version
pip --version 23.3.1
Programming Language and version
python3 --version 3.9.0
Installed using virtualenv? pip? Conda?(if python)
virtualenv
MediaPipe version
ERROR: No matching distribution found for mediapipe>=0.10.0
Bazel version
Build label: 6.4.0-homebrew
Describe the problem
Can not install 0.10.0 mediaPipe
No matching distribution found for mediapipe>=0.10.0
Complete Logs
python -m pip install mediapipe-model-maker==<IP_ADDRESS>
Collecting mediapipe-model-maker==<IP_ADDRESS>
Using cached mediapipe_model_maker-<IP_ADDRESS>-py3-none-any.whl.metadata (1.6 kB)
Requirement already satisfied: absl-py in ./venv/lib/python3.9/site-packages (from mediapipe-model-maker==<IP_ADDRESS>) (1.4.0)
INFO: pip is looking at multiple versions of mediapipe-model-maker to determine which version is compatible with other requirements. This could take a while.
ERROR: Could not find a version that satisfies the requirement mediapipe>=0.10.0 (from mediapipe-model-maker) (from versions: <IP_ADDRESS>, 0.8.5, <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>, 0.8.10, <IP_ADDRESS>, 0.8.11, 0.9.0, <IP_ADDRESS>, <IP_ADDRESS>)
ERROR: No matching distribution found for mediapipe>=0.10.0

Mac os version  is newest ,thank you

Hi @AnyLifeZLB,
Could you please try out this below command and let us know if this work for you:
pip3 install mediapipe-model-maker
Thank you

Default  installed mediapipe-model-maker-<IP_ADDRESS>, Still can not install the newest version <IP_ADDRESS>  @kuaashish

Hi @schmidt-sebastian,
Could you please have look into this issue? Thank you

@joezoug

Our Team want use MediaPipe customize Object detection model run on Android App .
Unfortunately, neither of our 2 iMacs can install the latest version of MediaPipe

I've solved it.  https://github.com/AnyLifeZLB/FaceVerificationSDK/blob/main/install_newest_mediapipe_on_macos.md
SYSTEM_VERSION_COMPAT ERROR ！！

mosaic


Test Execution Time is summed up from suite, test and methods in Eclipse Plugin

When I run a simple test class with the Eclipse PlugIn I get this report:
Test: 1/1 Methods: 2 (22s)
Default suite (2/0/0/0) (7s)
Default test (7s)
com.....
test1 (2s)
test2 (5s)
I'm shure the execution time "22 s" is just an addition of the other values below- what's not right from my point of view

Migrated to https://github.com/cbeust/testng-eclipse/issues/449


The github project is not complete !

It does not have the following classes that are presented in the tutorial: https://www.baeldung.com/spring-aws-kinesis
public AmazonKinesis
private void buildShardIterator
public class IpProcessor
public class IpProcessorFactory
public class IpConsumer
public class IpProducer
It only has:
public class KinesisApplication

Hey, @JoseRFJuniorBigData.
Thanks for pointing that out, we'll look into it.

The missing code snippets are added and consumers and producers for different libraries are now present in their respective packages


removed webpack attribute

Since it's breaking the webpack build.

What issue does this pull request resolve?
What changes did you make?
Is there anything that requires more attention while reviewing?

in 5.0.1-beta.3


Support Reset To Defaults on MSI (or platforms with serial disabled by default, in general)

Test environment version

Branch:  develop
Commit:  540916c508f3b11e3123c42c21125d4c388c1a9d

Dasharo version (if applicable)
 v1.1.4-rc1 for MSI zz690 DDR5
Dasharo variant (if applicable)

Affected component(s) or functionality (if applicable)
 CPU tests
Brief summary

CPU tests use Reset To Defaults kwd.
Resting firmware options causes the serial to be disabled (it is disabled by default on MSI), breaking further tests.
We have disabled CPU tests for now on these boards, but we need to see how to bring them back, if possible.
Some attempt have been made here: https://github.com/Dasharo/open-source-firmware-validation/pull/530/files#r1805154721
Additional context

If I understand correctly, the tricky part of this issue is that the Resets To Defaults KW can be called from any place in the setup tree, but the Serial Redirections requires us to move to a specific submenu. This could be easily solved by just rebooting the platform, but that would stop the serial redirection, so we need to check the option without reboots.
Jan tried to solve that by creating a crawler that will try to understand where it is in the tree by scanning what is sent via serial when pressing an arrow key.  With this information it could traverse to the main menu and then update the update the SerialRedirection as usual. This approach might be difficult, have a lot of corner cases and be sensitive to changes in the setup menus.
I think a much easier approach could be to reboot the platform before resetting to the defaults, doing the reset in the main menu, and then, knowing we didn't leave it, check the SerialRedirection as usual.

UEFI has a mechanism for multiple default stores:
Default Stores
There are three standard default stores:
Standard Defaults — These are the defaults used to prepare the system/device for normal operation.
Manufacturing Defaults — These are the defaults used to prepare the system/device for manufacturing.
Safe Defaults — These are the defaults used to boot the system in a “safe” or low-risk mode.

Maybe add an option to reset to manufacturing defaults and ensure that the manuf default for serial redirection is TRUE?

That would require actually configuring these stores, right? If we are not doing it already in the release binaries then that would be a pretty invasive change. If we do then there's still the issue how to access them. I haven't seen anything like that in the UEFI Setup menu. The DCU does not expose variables related to this either. Wouldn't it require rebuilding the FW? Maybe you meant to add an option to reset do manuf defaults to edk2?
That might be the best, but much more complex option. This would require updating all the devices which support the CPU tests or determining if the manuf settings are available during the test case...

The argument against always performing a reboot before restoring to the defaults is that the  reset to defaults changes the options in setup menu immediately. To commit them a reboot is needed but the defaults can be read by traversing the setup menu.
Some tests rely on this by entering a submenu, changing an option, performing a restore to defaults and checking if the option has changed immediately, knowing that the option tested is still visible. Performing a reboot before this would might break these tests.

I wonder if just pressing "ESC" repeatedly, like 10 times, won't be enough to return to the main Setup menu. One place where it would surely fail is when there is an error in applying a form and the user is asked to, if I remember correctly, either press "d" to revert the changes or something else to return to the form. Although in this case any automated test in Setup menu would fail as it is an unexpected situation.

I wonder if just pressing "ESC" repeatedly, like 10 times, won't be enough to return to the main Setup menu.

It would get to top level menu, but it wouldn't move the cursor. This problem can be handled by pressing Page Up, it always moves to first entry because there is no scrolling on the front page (at least currently).
It may be possible to add a new hotkey to return to top level immediately in edk2. Alternatively we may modify F9 to return to top as well. Both options would require changes to edk2 code and this may be an overkill.

One place where it would surely fail is when there is an error in applying a form and the user is asked to, if I remember correctly, either press "d" to revert the changes or something else to return to the form. Although in this case any automated test in Setup menu would fail as it is an unexpected situation.

Agree, tests should be written to catch errors, not to work around them.

The Reset To Defaults Tianocore keyword is always used before Save Changes And Reset.
There was an argument against performing a reboot to get back to the main setup screen

Some tests rely on this by entering a submenu, changing an option, performing a restore to defaults and checking if the option has changed immediately, knowing that the option tested is still visible. Performing a reboot before this would might break these tests.

But it's not true. The Reset To Defaults Tianocore keyword could easily be changed so that it reboots, performs the edk2 reset to defaults and restores the serial redirection from there without caring about traversing the setup menu.
What do you think @miczyg1

https://github.com/Dasharo/open-source-firmware-validation/pull/601
I have modified the Reset To Defaults Tianocore keyword to always set the serial redirection to Enabled after resetting as suggested in https://github.com/Dasharo/open-source-firmware-validation/pull/530/files#r1805158430
Running the CCC test on MSI Z690 DDR5 with i5 13600k shows that  the platform still has the serial redirection enabled after restoring to deefaults. After CCC007 the platform became unresponsive though and required a hard reset which I don't think could be caused by the change. It could use a rerun but I don't know if that's in the scope of this issue.
cpu-cores-count.robot_log.zip

The Reset To Defaults Tianocore keyword is always used before Save Changes And Reset. There was an argument against performing a reboot to get back to the main setup screen

Some tests rely on this by entering a submenu, changing an option, performing a restore to defaults and checking if the option has changed immediately, knowing that the option tested is still visible. Performing a reboot before this would might break these tests.

But it's not true. The Reset To Defaults Tianocore keyword could easily be changed so that it reboots, performs the edk2 reset to defaults and restores the serial redirection from there without caring about traversing the setup menu.

Okay, I might have remembered some old test version. However, I'm no convinced it is that easy to change. All tests perform reset to defaults then reset a platform. So before platform reset happens, you would have to navigate to Dasharo System Features -> Serial Console Redirection submenu. However, you don't know which submenu you are currently in. You would have to traverse the menu back to main page and then to  Dasharo System Features -> Serial Console Redirection. I heard many times that going forward in menus is not a problem, but going backwards is not trivial. As long as you can implement it reliably, I'm fine with that.

All tests perform reset to defaults then reset a platform. So before platform reset happens, you would have to navigate to Dasharo System Features -> Serial Console Redirection submenu.

I think that would only be the case if resetting the serial redirection option was tested, but it is not. Are there any test cases that depend on the Reset To Defaults Tianocore to return from an invalid configuration, booting which should be avoided?

The reason for the failures in the CCC test suite was indeed the Power On keyword. After increasing the sleep durations in it the CCC test suite passes perfectly
cpu-cores-count.robot_log.zip

I think that would only be the case if resetting the serial redirection option was tested, but it is not. Are there any test cases that depend on the Reset To Defaults Tianocore to return from an invalid configuration, booting which should be avoided?

Resetting to default causes all settings to be reset. On the example of MSI, resetting to defautls will disabel serial consoel access, because the default is disabled.  So Reset To Defaults Tianocore does the job right, btu the test are unable to handle the loss of serial output. Is that more clear now?


Certificates appear to use ORGANIZATION_NAME as 'issuer'

Possibly related to #1645 in that, if source import accepted these missing fields, it may be implicitly fixed.  Regardless, the 'issuer' column is set to, and remains, the org name even after update
While looking at how certificate data is initially wrong upon import from a source, we noticed that the 'issuer' field in the DB is set to a slugified string value of the cert's x509 ORGANIZATION_NAME CN.
In the UI, prior to the next sync job running, and while the cert data is incomplete, this renders the "Issuer" column as that org name slug.
After a sync job runs, authority_id is updated and the UI now displays the issuer name (i.e. a sub-CA CN) rather than the org name.    We presume this is related to authority_id because this is what the DB looks like at the two different stages:
After import from source, before sync runs, UI displaying the org name as issuer
lemur_prod=# select name,issuer,external_id,authority_id from certificates where name like 'C%';
                       name                        |       issuer       | external_id | authority_id
---------------------------------------------------+--------------------+-------------+--------------
 CertCN-OrgName-20180823-20190823                  | OrgName            |             |
 CertCN-OrgName-20190828-20190823                  | OrgName            |             |
 CertCN-OrgName-20180828-20190828                  | OrgName            |             |
 CertCN-OrgName-20180829-20190829                  | OrgName            |             |

After the sync job runs, fields are updated,  and with authority_id set, the UI displays the correct issuer name
lemur_prod=# select name,issuer,external_id,authority_id from certificates where name like 'C%';
                       name                        |       issuer       |     external_id     | authority_id
---------------------------------------------------+--------------------+---------------------+--------------
  CertCN-OrgName-20180823-20190823                 | OrgName            | XXXXXXXXXXXXXXXXX   |            4
  CertCN-OrgName-20180828-20190828                 | OrgName            | XXXXXXXXXXXXXXXXX   |            4
  CertCN-OrgName-20180829-20190829                 | OrgName            | XXXXXXXXXXXXXXXXX   |            4
  CertCN-OrgName-20180828-20190828                 | OrgName            | XXXXXXXXXXXXXXXXX   |            4

This seems to come from here, where the org name is preferred over the issuer CN:
https://github.com/Netflix/lemur/blob/acd473683e9e010e11966b05843477a71d7f01c5/lemur/common/defaults.py#L235
The expected behavior is that the issuer column would contain the issuer CN rather than the org name.

This should also be fixed in https://github.com/Netflix/lemur/pull/1691 but note the issuer name is taken directly from the certificate, so it may differ from the authority name as defined in Lemur.

Hey, danger on this one.  I was going to provide an alembic migration that updated existing certs to use the issuer name rather than org name but after talking to @kevgliss about naming/cert uniqueness, I'm concerned that this might break the AWS plugin.
Generally, because cert names from AWS have at least some association to the ARN, and specifically because in sync_endpoints, the AWS API calls return cert data that only include the ARN, from which the certificate name is derived like this
https://github.com/explody/lemur/blob/318527223baff171a18db0a336bf259de5bc5dc6/lemur/plugins/lemur_aws/plugin.py#L104
Then searched for by name here
https://github.com/explody/lemur/blob/318527223baff171a18db0a336bf259de5bc5dc6/lemur/sources/service.py#L77-L79
If imported or lemur-created certs are created with the "proper" issuer name in the cert name, will this cease to match the name that is derived from the ARN? We don't have an AWS instance set up to test this with...


Release please  branches  main  components  node gyp  release notes

Checklist

[ ] npm install && npm run lint && npm test passes
[ ] tests are included
[ ] documentation is changed or added
[ ] commit message follows commit guidelines

Description of change

@cclauss please correct me if I'm getting wrong, but I don't think this PR is valid, also https://github.com/nodejs/node-gyp/pull/3037 from the same author.
If by any chance this PR is by good intent, please clearly state your motivation of the change in the PR description. Thank you.
Closing.


Fix alignment loading

Codecov Report

Merging #179 into master will decrease coverage by 0.13%.
The diff coverage is 0.00%.

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


Adds getters for View classes

Description of the Change
This adds 5 get functions for access to the 4 view classes and the metricsReporter so that other plugins can have easier access to construct their own instances of the 4 view classes.
Alternate Designs
Some alternate options were covered in #390
Benefits
This doesn't change the existing functionality, and still maintains the lazy-load requires() style used in the createX() functions.
Possible Drawbacks
I would think we'd want to expose the metricsReporter here, but if not I can instead add checks in the other view classes to special-case the metricsReporter being undefined.
Applicable Issues
This is one of the ideas from #390

As stated in https://github.com/atom/fuzzy-finder/issues/390#issuecomment-494558400, we believe that services are the proper way to create such a system. Additionally, any pull request would require tests to be included in order to be reviewed and accepted.
Thanks very much for your contribution and your effort!


Please publish to npm

Would be easier to depend on/upgrade if it were hosted on npm than solely on GitHub.

Agree. Will publish when I get some spare minutes.

Done: npm install sticky-table-headers


Images

Images are displayed with a btex-func tag. We need to intercept that and turn in into images.

#24 uses an alternative syntax for images.


Add an exception to naming convention for names beginning with commonly used abbrevations

The Naming section advises

Properties should be camel-case with the leading word being lowercase.

When it makes sense for a symbol name to begin with a commonly used abbreviation, then the abbreviation should be capitalized according to common convention.  In other words, the common naming convention takes precedence.
Examples appear scattered through Apple's class references:

NSData *HTTPBody
NSURL *URL
const char *UTF8String
[UIColor RedColor].CGColor

@mpkeefe I think a PR for this would still be great idea.


-5 to skills at level 4

When a character is leveled up to level 4, all skills have their totals reduced by 5.  I tested up to level 8 and it did not happen again.  I attempted to use use Bug Report but it did not look like it worked.

Did this character fall into Dishonorable honor in the process? The penalty for being in dishonor is a -5 to all skills and a -1 to all other roles, which the system implements. If this is the case, then you should see everything go back to normal after adding honor to get the character out of Dishonor.

That was the problem.  Sorry about that, didn't mean to waste your time.  Thanks for the quick reply.

No, not a waste of time at all, I promise! I appreciate that you took the time to write the issue. Glad it worked out!


Update the FOCUS dataset example

⚠ Problem
FOCUS dataset example available is labeled as (1.0-preview(v1)) and doesn't reflect the changes made recently.
The latest version of FOCUS introduces additional columns and removes others.
🛠 Solution
Update the dataset to reflect the latest FOCUS version
🙋♀ Ask for the community

We could use your help:

Please vote this issue up (👍) to prioritize it.
Leave comments to help us solidify the vision.

@tiagobalabuch We actually have 2 datasets. We have 1.0 and 1.0-preview. Where are you seeing only the preview dataset?

#needs-info

I see we don't mention we have FOCUS 1.0 data on the open data doc. Is that where you saw this?

Confirmed with the requestor that this is now working.


Modify WaitForDelay for WA Primary

Tested locally

@jesseandersonumd I'm going to merge this, but in future could you spread the overseerscript out into multiple lines? Thanks!


"Exported" Projects with submissions stuck in submitted and wrangling status reverted to In Progress

I have identified 2 projects that in theory were exported for Release 26 (1st) and Release 27 (2nd) (have import forms filled out and in theory did not raise any issues or flags with the Import Team).
However, when I was updating the Bionetwork spreadsheet I realised that two projects had a status Reverted to In Progress.
Looking into detail those two projects have submissions stuck in "Submitted" instead of being exported or Complete.
https://contribute.data.humancellatlas.org/projects/detail?uuid=c5b475f2-76b3-4a8e-8465-f3b69828fec3&tab=project
Zenhub ticket
https://contribute.data.humancellatlas.org/projects/detail?uuid=aa55000c-0168-48d8-9026-2d3a76ec8af3&tab=project
Wrangled by UCSC - Import form says EBI and UCSC
There is an old project I also could not edit today because of a submission also stuck in Submitted (stretch. Only if time allows)
https://contribute.data.humancellatlas.org/projects/detail?uuid=f6133d2a-9f3d-4ef9-9c19-c23d6c7e6cc0&tab=project
There are some guidelines on how to investigate here

[ ] Check if there are any issues
[ ] Resolve issues (if any)
[ ] Make sure the submission goes to exported
[ ] This should (without manual intervention) automatically revert the wrangling status to "Submitted" first and eventually to Published in DCP once they are in DCP already

@ESapenaVentura in the end the status was submitted so you probably already covered it on your search. But tagging you on the ticket as it was already recorded here

c5b475f2-76b3-4a8e-8465-f3b69828fec3 is now in state Published on DCP
aa55000c-0168-48d8-9026-2d3a76ec8af3 AND f6133d2a-9f3d-4ef9-9c19-c23d6c7e6cc0 are listed in the #1220 issue with submissions stuck in intermediate state (here both are in state Exporting)

We can close the ticket as both projects' problem is described in ticket #1220.


blacksmith.sh

https://blacksmith.sh/

How many GHA provider companies will YC fund? :D
They are hosted at Hetzner, same as Buildjet and Ubicloud.

Too many... but it's a winner-takes-all kind of market, so lower quality providers will exit the race pretty soon, is my guess.

Or until Hetzner runs out of gaming CPUs

To be fair to Buildjet and Blacksmith, when you do end up on the high-end CPU runners, they are the fastest (for purely CPU-constraint builds like this nodejs example)

Yeah, but my team consistently has to wait around 20secs-5mins for Buildjet runners with 8+ cores. It's not very nice. That's one one of the main reasons why I put them lower on the list a while ago; the experience is decent but they refuse to do anything about the bandwidth situation and runner availability.

Another run showing the random part of getting a fast runner at buildjet. Also using RunsOn with twice the CPU count to get ahead everyone else, and still cheaper.

@neysofu Hey Filippo, I'm one of the founders of blacksmith.sh. We love this list you're maintaining, and would love to be a part of it. I created a PR here https://github.com/neysofu/awesome-github-actions-runners/pull/21. Thanks!

Thanks for the PR @adijp! I've responded to the PR with some suggestions. 💪


remove body-parser

In express >= 4.16.0, body parser has been re-added under the methods express.json() and express.urlencoded()

tnx also rm bodyParser.json()

Sorry, that's not true.


variable as argument to console.log after await is wrongly set as type and primitive

and therefor, monokai will paint it blue :(
this started in the latest version (2.77.0), if i go back to prev version, its fine.

Can you try 2.77.1

Yes, it works. Great! Thx for very fast response.


imsave is transposing my data

Hi,
I'm attempting to save out png images with imsave, but am noticing that my data seems to be getting transposed and I'm unsure why. Here is an example:
>>> print mydata.shape
(182, 218)
>>> imsave(filename.png, mydat.astype('float32'))

Then, when I do the following in terminal, this is what I get:
$ identify filename.png
filename.png PNG 218x182 218x182+0+0 8-bit PseudoClass 256c 9.75KB 0.000u 0:00.000

Any ideas why this is happening? Thanks!

The shape of a 2-d numpy array is (num_rows, num_cols), or, in other words, (height, width).  Imagemagick reports image sizes as width x height.

That makes sense - I should've looked closer at the documentation. Thank you!


feat: allow globs in node_modules when pattern is explicit

Description
Currently, we cannot use import.meta.glob for files in node_modules. This can be useful sometimes in development environments, especially considering that Vite treats relative and absolute paths differently.
This PR prevents ignoring node_modules in globs when the pattern is explicitly checking it.
Additional context

What is the purpose of this pull request?

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

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

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

@frandiox is this something that is blocking your team at Hydrogen? We can check with the team tomorrow, but as @bluwy said, it would help to have a detailed use case to justify the feat

@patak-dev @bluwy Thanks for checking!
So this came up when creating a separate Vite plugin for React Server Components (source here). Not sure if you are familiar with that but basically we need to use globs to find all the components that end in *.client.js. The problem is that some of these components might not be located in the user's src, but might come from a library in node_modules (like Hydrogen).
On top of that, in Hydrogen we use Yarn v1 workspaces (monorepo) and we are hoisting components to the root node_modules for local development. However, the importer file (the file that contains the import.meta.glob code) is located in a non-hoisted node_modules/.vite cache directory. Therefore, at some point we are trying to do<EMAIL_ADDRESS>and this returns nothing without the change in this PR 😅
This is not blocking us right now but it will if that PR I linked is merged/released -- so feel free to take time to ask the team or suggest other ideas 👍

@frandiox could you resolve the conflicts? We talked with the team and we can merge the PR 👍🏼

@patak-dev Done, thanks!


Add send_timeout property to fastcgi directive

See #1094.
This update adds the send_timeout property to the fastcgi directive.
fastcgi / <IP_ADDRESS>:9000 {
	send_timeout 10s
}

Like the connect_timeout and read_timeout properties, send_timeout has a default value of 60 seconds.
I added/refactored some tests along the way.

@ericdreeves Can you clarify for me (I'm writing the docs) -- does read_timeout and send_timeout count against reading or sending the whole response/request or is it just each successive read/send call (like nginx)?

@mholt They count against the request/response.

@ericdreeves Thanks. Could you suggest a better way to word this than I have, then, in the docs?

@mholt Sorry about the delay. Busy week! How about:
read_timeout is the time allowed to read a response from the backend.
send_timeout is the time allowed to send a request to the backend.

Works for me. Updating now, thanks!


Orca Error -  sh: orca: command not found

Is plotly-orca part of your conda list output?

Thank you for your response! Yes, it is:
$ conda list
plotly-orca               1.1.0                         1    plotly
Plus, I can do this ….
$ orca --help
Plotly's image-exporting utilities
Usage: orca [--version] [--help]  []
Available commands:

graph [or plotly-graph, plotly_graph]

However, my error has now changed when I run the following command:
json <- plotly:::to_JSON(p)
cmd <- sprintf("orca graph '%s' -o r-export-test.pdf", json)
system(cmd)
/usr/local/bin/orca: line 2: /Applications/orca.app/Contents/MacOS/orca: No such file or directory
/usr/local/bin/orca: line 2: exec: /Applications/orca.app/Contents/MacOS/orca: cannot execute: No such file or directory
So, I did the following:
$ cd /usr/local/bin
$ cat orca
#!/bin/bash
exec "/Applications/orca.app/Contents/MacOS/orca" "$@“
I think the 2nd line it cannot execute for some reason. I went to my /Applications and there is no Applications/orca.app
Is there supposed to be?
Many thanks!

On Aug 15, 2018, at 11:27 AM, Étienne Tétreault-Pinard<EMAIL_ADDRESS>wrote:
Is plotly-orca part of your conda list output?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub https://github.com/plotly/orca/issues/120#issuecomment-413233858, or mute the thread https://github.com/notifications/unsubscribe-auth/ALKJht-oA6-M_pXJvuZqSFqyG2JhqAAIks5uRD3-gaJpZM4V9fvf.

I think this might a case of conflicting installations. Have you tried installing orca by other means than conda?

Getting the same error as @Transmystical after using the system(cmd) prompt
Downloaded the standalone Orca binaries for Mac

Just wanted to ask if this issue has been resolved, and if so what the current fix is. I tried exporting a plot using orca in R (R 3.5.1 and plotly 4.8.0) today (9/9/2018) after installing orca using conda . Running orca(p, "test.png") gave the following error

Error: The orca command-line utility is required to use the orca() function
Follow the installation instructions here -- https://github.com/plotly/orca#installation

I can run help(orca) with no errors

I can run help(orca) with no errors

That gives no errors, but does it output anything?

I'm having the same problem as @CavinWard. I just installed orca using on my Mac using this command:
conda install -c plotly plotly-orca

I can see orca:
$ which orca
/anaconda3/bin/orca
$ orca --version
1.1.1

But when I try to save an image from RStudio:
> orca(p, "my-plot.png")
Error: The orca command-line utility is required to use the `orca()` function.

Follow the installation instructions here -- https://github.com/plotly/orca#installation

You'l need to either start RStudio from the command-line or manually edit R's PATH environment variable:
Sys.setenv("PATH" = paste(Sys.getenv("PATH"), "/anaconda3/bin", sep = .Platform$path.sep))

If you prefer the latter approach, you could put that code in your .Rprofile so you don't have to run that code everytime to restart R

Closing due to inactivity. Thanks @cpsievert!

You'l need to either start RStudio from the command-line or manually edit R's PATH environment variable:
Sys.setenv("PATH" = paste(Sys.getenv("PATH"), "/anaconda3/bin", sep = .Platform$path.sep))

If you prefer the latter approach, you could put that code in your .Rprofile so you don't have to run that code everytime to restart R

Hey @cpsievert , for me it works when I start RStudio from the command-line, but editing R's PATH doesn't work. (I checked that 'which orca' returns plotly-graph as an available command). Do you have a fix?

I solved the problem adapting the solution of @jonmmease : I found the orca file in /anaconda3/bin/, renamed it, and installed orca manually as a standalone library. Now it works fine.


Odd numerical instability in solving a nonlinear damped pendulum BVP collocation problem

I notice an odd numerical instability in solving a simple nonlinear collocation problem. So the problem is taken from Toby Driscoll's book on numerical methods, chap 10, example 10.4.2. The equation is:
$θ'' + 0.05θ' + sinθ = 0$ with $θ(0) = 2.5, θ(8.0) = -2.0$.
The code is below. The problem is that the NonLinearSolve results are really inconsistent. I discretize the problem, but
sometimes the solver will give me the result, and other times the solver gives a Singular Matrix error. For example I might
discretize with 50 points and it gives me a Singular Matrix error, but with 49 points it gives me a solution. The numbers 49 and 50 are just make up for explanatory purposes. And the other odd thing is that sometimes at a given n, it will give a result and at other times it will either give the Singular Matrix error or just return a vector if Inf. So not sure what the issue is.
Here is the code.
using NonlinearSolve, BandedMatrices, ComponentArrays, Plots

function first_derivative_matrix(n, h)
    D = BandedMatrix{Float64}(undef, (n,n), (2,2))
    D[band(0)] .= 0
    D[band(1)] .= 0.5
    D[band(-1)] .= -0.5
    D[1, 1:3] = [-1.5, 2.0, -0.5]
    D[n, end-2:end] = [0.5, -2.0, 1.5]
    D = D/h
end

function second_derivative_matrix(n, h)
    D = BandedMatrix{Float64}(undef, (n,n), (4,4))
    D[band(0)] .= -2.0
    D[band(1)] .= 1.0
    D[band(-1)] .= 1.0
    D[1, 1:4] = [2, -5, 4, -1]
    D[n, end-3:end] = [-1, 4, -5, 2]
    D = D/h^2
end

function make_discrete(tspan, n)
    x = LinRange(tspan[1], tspan[2], n)
    h = (tspan[2] - tspan[1])/n
    return (x, h)
end

function objective(u, p)
    Dxx, Dx, h = p.Dxx, p.Dx, p.h
    f = Dxx*u .+ 0.05*Dx*u .+ sin.(u)
    f[1] = (u[1] - 2.5)/h^2
    f[end] = (u[end] + 2.0)/h^2
    return f
end

n = 100
tspan = (0.0, 8.0)
Θ,h = make_discrete(tspan, n)
Dx = first_derivative_matrix(n, h)
Dxx = second_derivative_matrix(n, h)

p = ComponentArray(Dx = Dx, Dxx = Dxx, h = h)

u0 = ones(n)
prob = NonlinearProblem{false}(objective, u0, p)
solver = solve(prob, NewtonRaphson(), tol=1e-8)

plot(Θ, solver)

Try n from a list of [10, 20, 30, 40], and at least one of them should give a solution and one of them should give Singular Matrix errors. Could this be a conditioning problem? In the objective function I divided f[1], f[end] the boundary condition by h^2 to improve the conditioning.

The issue just seems to be that Newton methods can diverge. So the solutions are to use a smaller time-step or h. Or you can use methods like trust-region newton or linesearch, according to @ChrisRackauckas .


Updated MAINTAINERS.md format.

Coming from https://github.com/opensearch-project/.github/issues/121, updated MAINTAINERS.md to match opensearch-project recommended format.

Need a skip-changelog label with support... let's ignore that one here?


Include broker ID with its status

This PR surfaces the ID of the broker being checked in the status response.

Hi @nichegriffy , cool idea! Could you please also update the readme to reflect the change in the output this introduces?

@andreas-schroeder Good catch. I updated the README with the new broker field in the examples, and I also decided to pretty print the JSON and fix up the usage section to match the output of -h. Hope that's okay; let me know if I should do anything else. And thanks for the awesome tool!


Package Request: Chocolatey

Package Requested

[x] I would like someone else to build the manifest.
[ ] I would like help so I can submit the manifest.
[x] I have performed a search and couldn't find this package.
[ ] I think there is a new version available and I have provided the URL.

Please provide the following information if you can:
Publisher: Chocolatey Software, Inc.
Publisher Url: https://chocolatey.org/
Package Name: Chocolatey
Package Url: https://chocolatey.org/
Description: Chocolatey is a machine-level, command-line package manager and installer for Windows software. It uses the NuGet packaging infrastructure and Windows PowerShell to simplify the process of downloading and installing software.
Package Version:
Installer URL: https://community.chocolatey.org/install.ps1
For new versions:
Current Package Identifier:

WinGet doesn't support .ps1 files yet.
I believe it's being tracked by https://github.com/microsoft/winget-cli/issues/298.

Maybe Chocolatey have some packages that are not on WinGet.

Also Chocolatey is not moderated

Chocolatey is moderated. One of my packages is currently waiting for moderation.

I think there would be no point to this since we have winget. Also Chocolatey is not moderated and managed by anyone so it is not reliable and safe like winget.

A classic ms entltiled attitude.  That's one reason users must shy away from big corps on core tools like package managers.  They relesed this half-baked tool that can't install softwares that a typical developer would use ... I wasted my time .. now have to go back to choco...

As part of the Chocolatey Team, how do we go about getting Chocolatey published to Winget and ensure that only our team / automation can push updates?
We currently have two products we would push to Winget.

Also Chocolatey is not moderated and managed by anyone so it is not reliable and safe like winget.

That shows a complete misunderstanding of Chocolatey is a wholly incorrect statement. I'll leave it at that.

As part of the Chocolatey Team, how do we go about getting Chocolatey published to Winget and ensure that only our team / automation can push updates?

Installation methods that WinGet currently supports:

Download .exe/.msi installer and execute
Download single .exe executable and create symbolic link (user scope)

Installation methods that WinGet would support:

Download and extract .zip, execute .exe/.msi inside
Download and extract .zip, extract files and link executable(s) (user scope?)

AFAIK none of the above methods is known to be able to run .ps1 script at present. And it is not feasible to install choco as a .zip package since choco is usually working in machine scope (administrator) but WinGet can only install it in user scope (No idea if WinGet would add this feature in the future). So it is recommended to build a .exe/.msi installer, just like ChocolateyGUI.😉

ensure that only our team / automation can push updates

Yes. You can call moderaters when needed. Once verified, you can add agreements to the manifest, which cannot be added by others.

We currently have two products we would push to Winget.

ChocolateyGUI already exists here. I'm curious that what another product is? 🤔

We're looking to add Chocolatey CLI and I understand the caveats about installation method above. We would also like to take over 'official maintenance' of ChocolateyGUI.

As part of the Chocolatey Team, how do we go about getting Chocolatey published to Winget and ensure that only our team / automation can push updates?
We currently have two products we would push to Winget.

As someone who just tried to install chocolatey via winget I greatly appreciate your efforts! I'm looking for the bitwarden-cli specifically which Chocolatey has but winget does not, unless I'm mistaken.

@pauby any updates on chocolatey cli on winget?

Yes and no. There is an MSI installer in testing. We should have everything wrapped up (which is not just testing) soon.

@pauby, we're working on a "verified developer" feature to restrict changes to packages to a GitHub user. The business process is the long-lead issue. We've got a PowerShell script in PR to help until all of the wiring and business process are in place.
The script is to help our moderators track PRs. It's certainly not foolproof, but it's a start.

@ohkeenan is winget install Bitwarden.Bitwarden not the same bitwarden-cli you are referring to?

choco upgrade chocolatey worked for me

Chocolatey CLI 2.0.0 has just been approved. Just waiting on the updating of the community repository.
Note that this is being pushed manually currently until we are happy that our customers and community are happy with it.
I think this can be closed?

@denelon I think it likely is but installing the entire package wasn't what I was looking to do.
@pauby having Chocolatey on winget is going to be lovely thank you.


GHA release workflow: fix permissions

Our new repo does not give write permissions by default. This is a good thing.

sigh I think you're right; it's per-workflow or per-job.

I don't think per-job is too bad ^^


Release Preparation - February 2023

this ticket tracks activities needed for the February 2023 release.
Estimated release date 9 Feb 2023

I think that this can be closed right @jsilvela  ?

Right! Thanks


[Tech] - Check security and quality code

Recent test of this end-to-end librairy : Playwright . To be continued.
See to add jest to add first unit test.
Add check code quality in the CI

done. But we added cypress for e-to-e librairy


Model: Add support for Hackintosh

Description
This PR adds support for detecting if the macOS is running on a PC (Hackintosh)
Since FakeSMC.kext is a mandatory kernel extension for Hackintosh to boot, this PR checks if FakeSMC is loaded.
More about Hackintosh: Wikipedia: OSx86
Features

Detect if the current macOS is a Hackintosh

TODO
Maybe text rearrangement? "Model" line is a little bit too long (though still less than 80 chars)
ScreenShot

Also in regards to the line length, MacBookProXX,Y is the longest SMBIOS name, so if it's fitting in 80 chars then don't worry

Thanks :+1:

https://github.com/dylanaraps/neofetch/pull/734
Please fix the failing build and open a new PR.

The failing build was because of shellcheck, and the failing lines weren't related to the PR. I can't remember off the top of my head what the failing lines were but I checked it before I merged this.

@dylanaraps Hi, sorry I did not notice the CI after pushing. I'll open a new PR after I can pass shellcheck.
The shellcheck output was:
In neofetch line 246:
            if [[ "$(kextstat | grep "FakeSMC")" ]]; then
                  ^-- SC2143: Use grep -q instead of comparing output with [ -n .. ].

But there is no -n in the code and I didn't quite get what it wanted me to do.
Any advice on how I can eliminate this warning?

Is there any way to detect the presence of FakeSMC.kext directly (as in the FakeSMC.kext) instead of checking through kextstat? You can do
[[ -f "/path/to/FakeSMC.kext" ]]

and shellcheck will give you the clear.

@konimex I'm afraid there isn't. When using Clover EFI for booting Hackintosh, the FakeSMC.kext is not in /System/Library/Extensions, but outside of the main boot disk, which is really hard to detect its presence.

Yeah I don't think mounting the EFI partition just to check for Clover is a good idea (especially as we can't tell which disk it's on). We could check for the presence of the Clover preference pane (as a file), but this wouldn't cover all cases (different bootloaders (Ozmosis or Chameleon (pre-Yosemite))) or if they don't have the preference pane installed

Since SC is complaining about -n. Maybe we can use [[ -z "$(...)" ]] instead.

@iandrewt Maybe I should keep the !=""? The SC2143 went away after I put back the empty check.


How to obtain the groundtruth boundary for ADE20K dataset?

Hi @wangchi95 ;
As we know, ADE20K dataset is for semantic segmentation. How to obtain the labeled groundtruth boundary?
Thanks.

Hello whubxb,
Since we have semantic segmentation annotations, the semantic boundary labels can be obtained by compasring each pixel individually for equality with surrounding pixels (2-neighborhood in the implementation). For more details, you can refer to the Phase I chapter in our paper and the following code: https://github.com/wangchi95/active-boundary-loss/blob/958218d2d677ac9970d3e949049a672461d3c3de/abl.py#L89

@wangchi95
Thanks a lot.


Add gruvbox truecolor colorscheme

The included gruvbox colorscheme was a bit bland, so I decided to write a truecolor colorscheme for my favorite syntax theme.
My one complaint is that 'local', 'function', etc. and +-/* etc. are all statements. I would have liked to have used the red for local, function, if, then else, etc. And used another color for operators such as +=-/*. But as far as I'm aware, this is not possible in Micro?
EDIT: Now that I'm testing this with more languages, it seems results are mixed. Lua uses the statement color for =<>+- etc. Bash uses the special color for =<>+- etc. And C++ uses the default color for =<>+- etc. Perhaps we need some standardizing for the syntax highlighting in Micro.

I've gone ahead and added a second commit, which adds an operator type for colorschemes. I've made the necessary change in lua.gruvbox so that it can use a separate color for operators and statements.
It can be added to other languages fairly easily as well, but I just did it for my most used language.

Added operator type to the remaining default themes, giving it the value of the statement color for that theme. This all themes will render the same as before my changes, until the authors decide to set a new operator value (or stick with the current value if they'd prefer).

Hopefully this will be my last commit on the matter. Sorry, I should have tested more before making the pull request.
I have changed the group name from operator to symbol due to an apparent naming conflict. Not sure exactly what it was conflicting with, but Micro refused to recognize a color group named operator, but symbol worked fine. I'm not too familiar with Go, so perhaps operator is a reserved name in Go?
Anyway, the Gruvbox-tc colorscheme is finished, and looks beautiful with the differently colored symbols. All other colorschemes have had a 'symbol' group added, but retains the value of 'statement', so that the appearance will not change unless the colorscheme maintainers decide to change it in the future.

And where are the screenshots for comparison?

Screenshot for comparison:

Which one is the new one? Because I prefer the left one way more. The right one has less contrast and the red doesn't look good with the background, it has the same kind of effect as red on blue, it kind of becomes fuzzy (at least on my monitor, high gamut).

Left is the new one. Right is the original 256 color scheme.

Oh awesome, you did a nice job then!

Just went back through the entire diff to make sure everything was okay. And realized I had accidentally removed the statement group instead of the operator groups. This is fixed now.


flat (unmodified) buttons don't have a "hover" animation

As can be seen on the button sample page, a flat button (md-button="flat: true;") doesn't have a hover animation. A large button has that animation.
In addition to that, a disabled flat button gets the "focus" style when clicked on. A disabled raised button does not. Also, regular and large buttons (not flat) are animated differently on hover,
This may be a Materialize issue or may be caused by mixing Bootstrap and Materialize. Will have to check again when Bootstrap can be removed.

Most likely a Materialize bug. It's fixable by using this css:
.btn-flat:hover {
    background-color: #2bbbad;
    transition: .2s ease-out;
}

If we did #9 this would already be solved. :smile:


[3.2] [iOS] Additional 'linker_flags' plugin parameter

Extends iOS plugin .gdip config files to provide linker flags values with linker_flags field.
This allows to specify specific linker flags that plugin might require to function properly.
For example .xcframework plugins that extend GodotAppDelegate in any way require -ObjC flag to be added.
Will allow to remove manual setup or Xcode project for Godot's push notification plugin: https://github.com/godotengine/godot-ios-plugins/tree/master/plugins/apn

Thanks!


rhythmbox: does not display generic player

Describe the bug
I have an iPod classic flashed with Rockbox that I'm wanting to use with Rythmbox. On NixOS when I mount my iPod with Dolphin Rythmbox doesn't display under a "Devices" tab. As a sanity check I tested this on Arch Linux and it works without problem, so I suspect something is wrong in Nix-land.
Steps To Reproduce
Steps to reproduce the behavior:

Plug in and mount an iPod classic
Observe Rythmbox

Expected behavior
The iPod's partition should appear in Rythmbox.
Screenshots
How it appears on Arch Linux:

Additional context
N/A
Metadata
 - system: `"x86_64-linux"`
 - host os: `Linux 6.11.7, NixOS, 24.11 (Vicuna), 24.11.20241111.dc460ec`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.24.10`
 - channels(dacio): `"home-manager-22.05.tar.gz"`
 - nixpkgs: `/nix/store/4r8s42c9mwfvgdlxv0izb1cmlzrsb5nz-source`

Notify maintainers
@rasendubi

Note for maintainers: Please tag this issue in your PR.

Add a :+1: reaction to issues you find important.

The maintainer of this package may not be available if their GitHub status is anything to go by


[stable/kiam] Adding step to annotate namespace

What this PR does / why we need it: This PR updates note with the helm chart to require user to annotate their namespace without which kiam will not allow pods to assume role.
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes # Documentation fix
Special notes for your reviewer: Let me know if you want me to bump up the chart version.

@ewbankkit Please review this PR and let me know if any modifications are needed.

Yes, LGTM.

/ok-to-test


Resolve pylint issues

Codecov Report

Merging #504 into master will decrease coverage by 0.1%.
The diff coverage is 95.01%.

@@            Coverage Diff            @@
##           master     #504     +/-   ##
=========================================
- Coverage   96.36%   96.26%   -0.1%
=========================================
  Files          36       35      -1
  Lines       12890    12406    -484
=========================================
- Hits        12421    11942    -479
+ Misses        469      464      -5


PR checks failing as testng-7.2.0.jar no longer exists on repo.jenkins-ci.org

The Groovy checks on PRs are failing as they can no longer download test-ng 7.2.0 from jenkins-ci.org.
Passing log: https://github.com/adoptium/ci-jenkins-pipelines/actions/runs/7213899246/job/19654797971?pr=836 (Seemed to pull correctly: Downloading https://repo.jenkins-ci.org/public/org/testng/testng/7.2.0/testng-7.2.0.jar to /tmp/gradle_download7089325946772859694bin
Failing log: https://github.com/adoptium/ci-jenkins-pipelines/actions/runs/7213899246/job/19863065107
FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':test'.
> Could not resolve all files for configuration ':testRuntimeClasspath'.
   > Could not find org.testng:testng:7.2.0.
     Searched in the following locations:
       - https://repo.maven.apache.org/maven2/org/testng/testng/7.2.0/testng-7.2.0.pom
       - https://repo.jenkins-ci.org/releases/org/testng/testng/7.2.0/testng-7.2.0.pom
       - https://repo.jenkins-ci.org/public/org/testng/testng/7.2.0/testng-7.2.0.pom
     Required by:
         project : > org.codehaus.groovy:groovy-all:3.0.4 > org.codehaus.groovy:groovy-testng:3.0.4

* Try:
Run with --stacktrace option to get the stack trace. Run with --debug option to get more log output. Run with --scan to get full insights.

Found as part of https://github.com/adoptium/ci-jenkins-pipelines/pull/864#issuecomment-1866250659 and ignored for the purposes of merging that PR.

#871 fixes this


⚠ wakapi has degraded performance

In 708718d, wakapi (https://waka.mcha.cloud/api/health) experienced degraded performance:

HTTP code: 0
Response time: 0 ms

Resolved: wakapi performance has improved in dae30fd after 55 minutes.


ASP application

The current ASP application is basically a souped up MediaPipe example running our custom MediaPipe Perception Pipeline.
We need to make it reliably run on the ASP for many hours/days at a time, in the background, always available to receive a connection and/or requests from the ASG.
TODO

[x] get app editing/building in Android studio - not essential but will help development speed
[x] get current MediaPipe inferencing and ASG socket stuff running in an Android Service - determine the best type of service (Background, Foreground, Bound, etc.) to do the job. Likely needs a Foreground service like here
[x] start saving incoming images/video stream from ASG into a file structure that makes sense
[x] setup database on Android with SqlLite or Realm
[x] save image data (file location, timestamp, metadata) in database
[x] setup a WebSocket connection on ASP that will run always in background - this will accept sensor data, function requests, and push data to the ASG
[x] stream audio data from ASG to ASP - either over raw TCP socket or over the new WebSocket above

All done. We have moved all of the main components to ASP. Still need to implement a web system so we don't lose previous features that GLBOX handled - need to make GLBOX an HTTP server we occasionally hit for those things. Continuing this in other issues.


[SHB] Integrate scraper with database

We should also have a component in the scraper that updates the database with newly scraped data.

Il iau eu !!

Also should start form EnascutaRazvan:main


[fix][txn] Catch and log runtime exceptions in async operations

Motivation
In the transaction coordinator code, most of the async execution doesn't properly runtime exceptions that might happens.
The exception is not logged and the CompletableFuture is not completed.
Similar changes in past https://github.com/apache/pulsar/pull/17484
Modifications

New utility method FutureUtil#safeRunAsync(Runnable runnable, Executor executor, CompletableFuture completableFuture) that completes exceptionally the completablefuture if an error has been caught in the runnable
Added in MLTransactionMetadataStore and  TxnLogBufferedWriter

Verifying this change

[x] Make sure that the change passes the CI checks.

Documentation

[ ] doc
[ ] doc-required
[x] doc-not-needed
[ ] doc-complete

Matching PR in forked repository
PR in forked repository:

/pulsarbot rerun-failure-checks

Codecov Report

Merging #19258 (5327fc2) into master (299bd70) will increase coverage by 1.51%.
The diff coverage is 81.57%.

@@             Coverage Diff              @@
##             master   #19258      +/-   ##
============================================
+ Coverage     46.37%   47.88%   +1.51%
- Complexity    18221    18501     +280
============================================
  Files          1599     1609      +10
  Lines        130054   126294    -3760
  Branches      14317    13728     -589
============================================
+ Hits          60310    60474     +164
+ Misses        63630    59554    -4076
- Partials       6114     6266     +152

Flag
Coverage Δ

inttests
20.22% <51.31%> (?)

unittests
45.18% <76.31%> (-1.19%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...java/org/apache/pulsar/common/util/FutureUtil.java
54.32% <66.66%> (+6.32%)
:arrow_up:

...saction/coordinator/impl/TxnLogBufferedWriter.java
81.85% <80.76%> (+0.84%)
:arrow_up:

...n/coordinator/impl/MLTransactionMetadataStore.java
67.09% <84.09%> (+0.32%)
:arrow_up:

...pache/pulsar/client/impl/CompactionReaderImpl.java
0.00% <0.00%> (-90.00%)
:arrow_down:

...g/apache/pulsar/client/impl/RawBatchConverter.java
3.12% <0.00%> (-89.07%)
:arrow_down:

.../pulsar/compaction/StrategicTwoPhaseCompactor.java
0.00% <0.00%> (-76.20%)
:arrow_down:

...lsar/client/impl/RawBatchMessageContainerImpl.java
0.00% <0.00%> (-73.14%)
:arrow_down:

...ava/org/apache/pulsar/io/core/BatchPushSource.java
0.00% <0.00%> (-61.54%)
:arrow_down:

...lsar/broker/service/StickyKeyConsumerSelector.java
50.00% <0.00%> (-50.00%)
:arrow_down:

...ion/buffer/metadata/TransactionBufferSnapshot.java
42.85% <0.00%> (-42.86%)
:arrow_down:

... and 757 more

I notice that safeRun method in PR https://github.com/apache/pulsar/pull/17484 is implemented by try/catch block, which is different from here.
    public static SafeRunnable safeRun(Runnable runnable, Consumer<Throwable> exceptionHandler) {
        return new SafeRunnable() {
            @Override
            public void safeRun() {
                try {
                    runnable.run();
                } catch (Throwable t) {
                    exceptionHandler.accept(t);
                    throw t;
                }
            }
        };
    }

And I write some test code to test safeRunAsync method.
    public static void safeRunAsync(Runnable runnable,
                                    Executor executor,
                                    CompletableFuture completableFuture) {
        CompletableFuture
                .runAsync(runnable, executor)
                .exceptionally((throwable) -> {
                    completableFuture.completeExceptionally(throwable);
                    return null;
                });
    }

    @Test
    public void test() throws ExecutionException, InterruptedException {
        CompletableFuture<String> future = new CompletableFuture<>();
        ExecutorService executorService = Executors.newSingleThreadExecutor();
        executorService.shutdown();
        safeRunAsync(() -> {
            try {
                Thread.sleep(2000);
            } catch (InterruptedException e) {
                throw new RuntimeException(e);
            }
            future.completeExceptionally(new RuntimeException("test"));
        }, executorService, future);
        future.exceptionally(throwable -> {
            System.out.println(throwable.getMessage());
            return null;
        }).get();
    }

The test is failed, we can't catch the error thrown by thread pool itself.


Anyone else using this plugin on Hoobs?

https://plugins.hoobs.org/plugin/homebridge-lutron-caseta-leap
Hoobs pulled this exact plugin into their library and continues to update it, including beta releases.
It's working fairly well for my 30+ picos, except the recent version that introduced double and long click was causing slower response, even when those options are set to disabled.  So I downgraded back to the earlier v2.3.9 with only single click.
Anyone else using this setup?

There has been occasional discussion of HOOBS over time. I think this thread may be of interest to you.
I am interested in the downgrade due to delay. It's been a while since I looked at the code, but I recall designing things so that disabling the double- and long-click function should make it work immediately as it did before. If it's not, that's definitely a bug (or at least, I think it's a bug).

Fully understand you do not officially support Hoobs.
And my feedback is limited because I'm using this in production in my home.
It's possible the delay or issues with Hoobs were because the picos were previously 'upgraded' to appear in HomeKit with long and double, so just setting to disabled in your plugin (in Hoobs) might not have been sufficient, I may have also needed to clear some cache.
That said - Hoobs or not, even the behavior of single click seems to be triggered on button Release.  It appeared that way from logs and I can confirm from real use that button Pressing does nothing... until the button is Released.  If you have no need for double and long, can the responsiveness of single be improved by initiating on button Press?


Replace keep-while cond reverse index with a prefix tree

When handling a deletion, khepri_tree:eval_keep_while_conditions/2 folded over the reverse index of keep while conditions and evaluated any for which the removed path was a prefix. This meant folding over each non-leaf node in the tree. We can eliminate nodes very quickly though to limit the impact of this search by using a prefix tree instead.
This change switches out the keep_while_conds_revidx field in #khepri_tree{} to a new khepri_prefix_tree type when the Khepri cluster reaches the new effective machine version of 2.

Dialyzer looks to get stuck in recursion on the Ubuntu + Erlang/OTP 27 runner, I can reproduce locally


Avoid too many calls to get host ec2 tags

This call is expensive on environments with a lot of hosts. For detecting indefinitely spinning hosts, it should be enough with the added staleness check (15 mins) to provisioning hosts and the ip is not None check on provisioned/active hosts.
Test Plan:
Verified this endpoint is not called anymore

For detecting indefinitely spinning hosts, it should be enough with the added staleness check (15 mins) to provisioning hosts and the ip is not None check on provisioned/active hosts.

@gzpcho how will you test that detecting indefinitely spinning hosts will work after these changes? Can you please include  proofs of tests that after these changes detecting indefinitely spinning hosts wasn't broken?

Please include steps to reproduce test plan

@vitalii-honchar Added the following elasticsearch snapshot. You can see calls to this endpoint stop occuring shortly after deploy.
https://search-visibility-es4-yzk3lo6prv6qkda3oetn7zcm5a.us-east-1.es.amazonaws.com/_plugin/kibana/goto/3400b541adfea405bf3d76be582ac4c2?security_tenant=global

For detecting indefinitely spinning hosts, it should be enough with the added staleness check (15 mins) to provisioning hosts and the ip is not None check on provisioned/active hosts.

@gzpcho how will you test that detecting indefinitely spinning hosts will work after these changes? Can you please include proofs of tests that after these changes detecting indefinitely spinning hosts wasn't broken?

Added more validation to the test plan


Plans to publish 0.13.0?

Would love to see the latest batch of PRs released to crates.io. What help might be needed to make that happen?

Dependencies:

[x] https://github.com/georust/gdal/pull/279
[x] https://github.com/georust/gdal/pull/281
[x] https://github.com/georust/gdal/pull/284
[x] https://github.com/georust/gdal/pull/285
[x] https://github.com/georust/gdal/pull/289
[x] https://github.com/georust/gdal/pull/291

i guess we should merge
#279
#281
#284
and
#285
then i can create a new release. I guess it is possible to do that this week.

Can https://github.com/georust/gdal/pull/289 and https://github.com/georust/gdal/pull/291 maybe be part of it as well?

@jdroenner Do we want to hold back the release for #289 and #291 to get merged, or do we prefer a "release now and soon after" approach?

I think it would make sense to merge them (I'll take another look at them in the next few days), but also fix #290.

all the PRs i wanted to see in the release are merged now. I will prepare a new release now :)

What about #290?

I might have a quick fix for it, if you want to wait.

yes i can wait

@here Thanks to everyone for making this release happen! I very much appreciate it, as I assume others will! 🥇


[release-v1.15] Remove finalizer when trigger is deleted

Backport from upstream.

/test 415-test-reconciler-keda-aws-415


Fix Menu navigation with keyboard and focus handling

blocked by #1186
We should check if we can solve the focus bug without having the state hook in #1186 finished.
Describe the bug
When using arrowkeys (up/down) i should be able to navigate the menu items.
Steps to reproduce the bug

Trigger open Menu
Use prop first to trigger focus on first/last element

Expected behavior

First or last menu item should have been focused depending on wether user presses down or up
MenuItem are not focused when opened by mouseclick

Specifications

Version:
Browser:
OS:

Additional context
Thorough testing shows that the usage of useContext in combination with useEffect is somehow screwing up the update and render cycle for the focusedIndex prop.

Fixed by #1671


Added Binary Tree Algorithm for Generating Mazes

Changes Made

Created src/algorithm.py and moved the current depth first search algorithm to it.
Added binary tree algorithm for maze generation in src/algorithm.py.
Added code to show generation path for maze generated using binary tree algorithm.
Added unittests for algorithm.py in tests/algorithm_tests.py.
Added sample code in examples/quick_start.py.
Added demo script in examples/generate_binary_tree_algorithm.py

Why?
There are a lot of different algorithms for creating mazes and solving them and each of these algorithms have their pros and cons. To make this repository complete, it is necessary to include as many of these algorithms as possible.
How?

To make the code more intuitive to read and understand, the present algorithm for generating maze has been removed from src/maze.py and moved to src/algorithm.py as a separate function.
In addition to that, an optional parameter algorithm has been given to the constructor of Maze. The default value for this parameter is dfs_backtrack and uses the depth first search method to generate the maze. This way, any code relying on previous versions of the repo can still function.
If the user wants to use some other method for generating their maze, they can give a different value for this parameter.
For using the Binary Tree Method, the value to be passed to the constructor is bin_tree.

The Binary Tree Algorithm
The binary tree algorithm is very simple and involves looping through all cells in the maze only once.

We visit each cell in the maze serially.
For each cell randomly choose between removing the top wall or right wall.
For cells in the topmost row, we cannot remove the top wall as that would open the maze. So we remove only right walls for these cells.
For cells in the rightmost column, we do the same with right walls.
Since there is no correct order for visiting the cells, we visit them serially using 2 for loops.

The Generation Path Algorithm
In this algorithm, we are visiting the cells serially, row by row. But for showing the path generation animation, we cannot use this path, because it generates the wrong results.
Instead, we use a hack that generates the correct maze and sheds some light on why the algorithm is called binary tree algorithm.
The Binary Tree Algorithm is called so because, the maze generated can be represented as a binary tree.
To understand this better, consider the following maze generated using the binary tree method.

This maze can be represented as a binary tree as follows,

The cell in top right corner is the head of the tree.
This cell has two children, one on the left and one on the bottom.
So, if we visit the head cell first, then its children and so on, we are left with a binary tree.
Since at each cell we choose between the top wall and right, each cell has at most 2 children.

So, in the generation algorithm, I have used this concept and traversed the maze using dfs as can be seen using the show_generation_algorithm.
Unittests
Unittests have been added for algorithm.py in tests/algorithm_tests.py.
To make testing of new algorithms easier, I have created a list of all maze generation algorithms in algorithm.py.
In algorithm_tests.py, each test is run for all the algorithms in this list.
This way, when a new maze generation algorithm is added, there is no need to write unittests for it separately.
The following tests have been added,

test that the generation path is not an empty list
test that entry and exit points have been added for the maze
test that after generating maze, all cells have been marked as unvisited
tests that all cells have been processed and no cell has walls on all four sides.

@jostbr It's been a long time since I opened this PR. Yet you haven't responded. If this is a dead project, tell me right away so that I can stop wasting my time.

@AshishS-1123 My apologies for being AWOL! Thank you for your contributions. I merged #35, this means #36 have conlfict in src/maze.py. Are you able to see what that is and then I can proceed to merge #36.

@jostbr I have fixed the merge conflict. I modified the generate_maze function in src/maze.py to include the conditional statements that call the different generation algorithms. Branch can now be merged.


Moving between VS Code and VS 2022 causes rebuild

Hi, I am running Visual Studio 2022 17.2.0 Preview 2.1 and VS Code 1.65.2 with vscode-cmake-tools 1.10.5.
I am using a CMake Preset to build on Windows using msbuild.  The preset works fine in both editors but I find that when I switch from one editor to the other (VS Code to VS 2022 and vice-versa) a build command results in a rebuild. This may be to do with the CMake cache getting regenerated?
Is there any way to stop this behaviour?  It would be nice to be able to move seamlessly between the two tools.
(I also notice a rebuild when moving between two versions of Visual Studio).

I think the first thing to check here is whether the configuration commands generated by the two IDEs are identical or not.  We print out the full cmake command in the Output window when running the "CMake: Configure" command.  VS 2022 will also print out the command in their Output window if you check the box for "Enable verbose CMake output" in the "CMake -> General" settings page.

However, I made a few changes and the cache regeneration is now no longer happening.

Is it anything that we should be doing for you?  Or just project specific configuration?


Improvements for Python 3 compatibility

@JordanReiter I am closing this PR, ended up refactoring the code a lot, adding Python3 compatibility as well as context managers etc. I don't want to include UNO support, but did add support for OOo files via pure python means.
I am preparing this library for a new release, If you still use it, please feel free to review my recent changes and let me know if they are suitable for you.
https://github.com/btimby/fulltext/pull/8


No options on association to self entity

When entity is referencing itself select has no options.
It should show all entities but one that is editing at the moment

TC:

Create entity with association 1-1 with itself
Create Frontend component entity management for this entity
Start backend app
Start frontend app
Create new instance of the entity
Create another one instance
Open association attribute combobox

AR:
list is empty:

after entity is saved and reopened for editing, list is not empty:

TC 2:

Create entity with association 1-1 with itself
Create Frontend component entity management for this entity
Select attribute with association in GraphQL constructor -> Finish editing

AR:
extra query was added to EntityList:

@owlet1997
https://github.com/Haulmont/jmix-frontend/issues/719#issuecomment-958949133 - this is Studio issue


DeployURL is not updated in AppHarness tests.

Describe the bug
rx.get_config().deploy_url always returns http://localhost:3000.
To Reproduce
Create an AppHarness test.
Expected behavior
rx.get_config().deploy_url returns the correct URL for the test environment.
Specifics (please complete the following information):

Python Version: 3.12.2
Reflex Version: 0.4.2
OS: arch

Just for reference: AppHarness tests currently store the correct frontend url in the frontend_url attribute of the AppHarness class but do not update rx.config accordingly. It would be awesome to have one api (f.e. rx.get_config().deploy_url) which always returns the correct url.

I.e. these two tests fail.
"""Integration tests for deploy_url."""

from __future__ import annotations

from typing import Generator
from selenium.webdriver.common.by import By
import pytest
from selenium.webdriver.remote.webdriver import WebDriver
from selenium.webdriver.support.ui import WebDriverWait
from reflex.testing import AppHarness

def DeployUrlSample():
    """Sample app for testing config deploy_url is correct (in tests)."""
    import reflex as rx

    class State(rx.State):
        def goto_self(self):
            return rx.redirect(rx.config.get_config().deploy_url)

    def index():
        return rx.fragment(
            rx.button("GOTO SELF", on_click=State.goto_self, id="goto_self")
        )

    app = rx.App(state=rx.State)
    app.add_page(index)

@pytest.fixture(scope="module")
def deploy_url_sample(tmp_path_factory) -> Generator[AppHarness, None, None]:
    with AppHarness.create(
        root=tmp_path_factory.mktemp("deploy_url_sample"),
        app_source=DeployUrlSample,  # type: ignore
    ) as harness:
        yield harness

@pytest.fixture()
def driver(deploy_url_sample: AppHarness) -> Generator[WebDriver, None, None]:
    assert deploy_url_sample.app_instance is not None, "app is not running"
    driver = deploy_url_sample.frontend()
    try:
        yield driver
    finally:
        driver.quit()

def test_deploy_url(deploy_url_sample: AppHarness, driver: WebDriver):
    import reflex as rx

    assert rx.config.get_config().deploy_url != "http://localhost:3000"
    assert rx.config.get_config().deploy_url == deploy_url_sample.frontend_url
    driver.get(rx.config.get_config().deploy_url)
    assert driver.current_url == rx.config.get_config().deploy_url

def test_deploy_url_in_app(deploy_url_sample: AppHarness, driver: WebDriver):
    driver.implicitly_wait(10)
    driver.find_element(By.ID, "goto_self").click()

    WebDriverWait(driver, 10).until(
        lambda driver: driver.current_url == deploy_url_sample.frontend_url
    )

Nobody wants to do a red2green :adhesive_bandage:  with given tests? What's up :smiley_cat: ? It's like a task from advent of code.

https://github.com/reflex-dev/reflex/pull/3359


use sample name as run id

Cellranger has an input option for a run id which is used to generate the running directory and is used as an identifier in some of the output files. Initially we had a generic cellranger_ouput id to simplify parsing  and consistency across runs. That makes it difficult to easily determine the sample from the result files. This PR helps to fix that.

+1 looks good!

https://xkcd.com/327/


⚠ Processors has degraded performance

In 749162c, Processors ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 84 ms

Resolved: Processors performance has improved in 5610f98.

Resolved: Processors performance has improved in 5610f98.


Compatibility update for CloudScraper 1.2.40

Motivation for changes:
Solving dependency conflict between Flexget and CloudScraper
Detailed changes:

Updated pyparsing==2.2.0 to pyparsing==2.4.7 on requirements.in and requirements.txt

Addressed issues:

Fixes #2666 .

LGTM, thanks!


[FLINK-9394] [e2e] Test rescaling when resuming from externalized checkpoints

What is the purpose of the change
This PR further extends the test_resume_externalized_checkpoints.sh e2e test to cover rescaling cases.
Brief change log

Allow specifying old / new parallelism and state backend configuration for the test script
Modify nightly test script

Verifying this change
This is a simple extension to existing tests.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (yes / no)
The serializers: (yes / no / don't know)
The runtime per-record code paths (performance sensitive): (yes / no / don't know)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (yes / no / don't know)
The S3 file system connector: (yes / no / don't know)

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

r: @StefanRRichter

Oh this is great! @StefanRRichter Is this means that flink plan to make checkpoint support rescaling officially in the near future?

@tzulitai thanks for this additional test. LGTM 👍

@StefanRRichter thanks for the review, will merge this.


[Feature request] Be able to put trough a CFD order.

Hi,
I am having issues finding out a way to do an order on CFD. I know it's not fully worked out, but I am trying to get it to work just for testing purposes.
Right now I have the following, which doesn't work:

Do you have any suggestions what to use for the 'trading212 = ' line and the 'buy_order = ' line?
Thanks!

Yes, the CFD are not supported yet but I  work on it asap.
As a first suggestion, try to add '#' before the instrument_code, so it will become instrument_code='#EURUSD'

Thanks for the suggestion, sadly still an InternalError. Do note I also removed , trading=CFD out of the 'trading212 = ' line (line 20).

Sadly didn't work out. Thanks for the suggestion though, I look forward to when it is fixed!

From a quick look it seems to me that you are using the API incorrectly, as soon as I can I will try to post a snippet of a working CFD order.
Unfortunately this was my shortcoming as when I started writing the API the CFD support was not considered as I did not need it.
Now that interest in CFD support has increased I am planning to rewrite some of the code to make it clearer with almost full CFD support. Probably in a new major release.

From a quick look it seems to me that you are using the API incorrectly, as soon as I can I will try to post a snippet of a working CFD order. Unfortunately this was my shortcoming as when I started writing the API the CFD support was not considered as I did not need it. Now that interest in CFD support has increased I am planning to rewrite some of the code to make it clearer with almost full CFD support. Probably in a new major release.

On the first line: yes, you are probably right that I am not using it the right way!
On the rest: No poblem, I really like the work you're doing and hope you can continue to improve it forward with more CFD support.
Can't wait for the new major release 💯

Hi, sorry for the late response but i found a bug and fixed it, i've also added an example of CFD order execution.
As i just told you, unfortunately the API usage is slightly different in respect to EQUITY trading, but i'm working to fix it in a future release, for now you can use this snippet. I wrote this snippet very quickly so maybe rename the variable's names for better reading.
import sys

from selenium import webdriver

from pytrading212 import *

if __name__ == "__main__":
    email = sys.argv[1]
    password = sys.argv[2]
    driver = webdriver.Chrome(executable_path='chromedriver.exe')

    cfd = CFD(email, password, driver, mode=Mode.DEMO)
    order = CFDMarketOrder(instrument_code='EURGBP', target_price=10.0, quantity=500)
    cfd_order_outcome = cfd.execute_order(order)
    print(cfd_order_outcome)

I've received this message, so the order worked for me, even if it was not executed because i exceeded the max buy of 500 units
{'code': 'BusinessException', 'context': {'max': 0, 'type': 'MaxBuyQuantityExceeded'}, 'message': 'can open at most0'}
As a last remainder, but i think that you already now, i'm not able to get the current price of CFD, so if you want to buy in target_price you have to set a bigger value than the current price, the same for sell but with a lower value.

Hi, sorry for the late response but i found a bug and fixed it, i've also added an example of CFD order execution. As i just told you, unfortunately the API usage is slightly different in respect to EQUITY trading, but i'm working to fix it in a future release, for now you can use this snippet. I wrote this snippet very quickly so maybe rename the variable's names for better reading.

Thanks for the reply!
I tried this out but sadly got this error now using your code (filename is different because I tried changing things in the original to make it work, but I am using your latest update):

If i try to run example.py (while being in CFD) I get this output (ofcourse I do not expect it to work, but I get more output than on the cfd_example.py:

Thanks for the feedback, i need to add some checks when the page is fully loaded, maybe sometimes selenium doesn't found the element because T212 is still loading. I will fix it asap maybe tomorrow, I don't want to put a lot of effort because I'm planning to rewrite better (also with CFD support) a big part of the code but unfortunately in this period the time is not my friend. I will work on a solution for you asap, but look at it as a temporary solution, waiting for the full support.
Maybe you should try to open the code with an IDE, put some breakpoints inside Trading212 class in the init method, in the cookie section and wait until the trading212 page is fully loaded

Maybe you should try to open the code with an IDE, put some breakpoints inside Trading212 class in the init method, in the cookie section and wait until the trading212 page is fully loaded

That worked! I just added 2 time.sleep(10) (so sleep 10 seconds) into the code before the cookie, which made the order go trough!
also added import time, because trading212.py didn't have that imported yet.

It might be that, because I am using a VM, my system is just a little too slow

As a last remainder, but i think that you already now, i'm not able to get the current price of CFD, so if you want to buy in target_price you have to set a bigger value than the current price, the same for sell but with a lower value.

This part doesn't seem to work for me. I only am able to buy right now: (the argument is the target_price)

Maybe you should try to open the code with an IDE, put some breakpoints inside Trading212 class in the init method, in the cookie section and wait until the trading212 page is fully loaded

That worked! I just added 2 time.sleep(10) (so sleep 10 seconds) into the code before the cookie, which made the order go trough! also added import time, because trading212.py didn't have that imported yet.

edit: 3 seconds also worked

I'm happy that worked and you fixed it yourself, there a lot of better solution but for now keep that as a workaround waiting for the new API.
Sometimes T212 is very slow to load.

As a last remainder, but i think that you already now, i'm not able to get the current price of CFD, so if you want to buy in target_price you have to set a bigger value than the current price, the same for sell but with a lower value.

This part doesn't seem to work for me. I only am able to buy right now: (the argument is the target_price)

Because you put a MARKET BUY order but with a lower price than the current, as you can see "operation=buy".

As a last remainder, but i think that you already now, i'm not able to get the current price of CFD, so if you want to buy in target_price you have to set a bigger value than the current price, the same for sell but with a lower value.

This part doesn't seem to work for me. I only am able to buy right now: (the argument is the target_price)

Because you put a MARKET BUY order but with a lower price than the current, as you can see "operation=buy".

Yeah I noticed, but I can't find a place where it should be changed.
order.py:

Maybe the T212 Post request is changed since i wrote the API a lot of time ago. I will investigate on this and let you now asap. Thanks for you patience and for the support to improve this API.

Maybe the T212 Post request is changed since i wrote the API a lot of time ago. I will investigate on this and let you now asap. Thanks for you patience and for the support to improve this API.

Sounds good!
Let me know when you've got an update :D

I'd love to know if there is a working API, is there any update?

For CFD not yet, i was very busy. I will try to work on CFD in the next weeks.

I'd love to know if there is a working API, is there any update?

Thanks for the reply! Ill be on the lookout

I'm working right now on it. Look at dev branch to know the progress


ReactXP/ReSub support/templates

I know that there are hundreds of frameworks for which templates could be build, however since ReactXP and ReSub are both developed by Microsoft, I wonder if there are any plans to include a template and maybe support for SSR?

Interesting thought. At the moment we don't have any specific plans for that. If you want to publish your own template along those lines, we can definitely link to it from the wiki.


Estimators of H, I

(Possibly) add some estimators of entropy, mutual information, etc.
See for example:
Jean Hausser, Korbinian Strimmer, "Entropy inference and the James-Stein estimator, with application to nonlinear gene association networks". http://arxiv.org/abs/0811.3579
Also see DeDeo's recent papers:
http://dx.doi.org/10.3390/e15114668
http://dx.doi.org/10.3390/e15062246
and THOTH.  We'll have to think more about how dit should interact with THOTH.

also: http://arxiv.org/abs/1503.05911

several have been added to dit.inference.

however, some fancier ones, like those linked by @chebee7i, are still needed.


Adds Role resource to enable list and retrieve actions

I would like to add this to the gem. I updated the VCR recordings with some valid templates.

Thank you @gealgaro and sorry for the late reply.


No Panda Issue

Describe the bug
My Comma 3x turns on when starting the vehicle, but says "No Panda." When I was switching over to the 3X from the 3, I accidentally disconnected a grey cable from the harness, which I was afraid might affect it. However, it didn't seem to effect anything (noticable). It seemed to work just fine for a week or two, but now doesn't work at all. Could the harness be why it's not reading the panda?
Provide a route where the issue occurs
1c05783affe6641f|2023-01-20--19-06-44
openpilot version
0.9.4
Additional info
I uploaded the most recent video I had, but I'm unsure if the issue was displayed in the video.

I've repaired the harness wire, but it's still not functioning.

Can you try the release3-staging branch? You can install it with this URL: openpilot-test.comma.ai.

Hey, that worked!
Get Outlook for Androidhttps://aka.ms/AAb9ysg

From: Adeeb Shihadeh @.>
Sent: Sunday, November 12, 2023 1:24:03 PM
To: commaai/openpilot @.>
Cc: tglevrie @.>; Author @.>
Subject: Re: [commaai/openpilot] No Panda Issue (Issue #30446)
Can you try the release3-staging branch? You can install it with this URL: openpilot-test.comma.ai.
—
Reply to this email directly, view it on GitHubhttps://github.com/commaai/openpilot/issues/30446#issuecomment-1807216227, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AURF3KAI2S27X6VDT2I2Q3DYEEO5HAVCNFSM6AAAAAA7HX3EOCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMBXGIYTMMRSG4.
You are receiving this because you authored the thread.Message ID: @.***>


CI: don't run GitHub Actions on fork or in cron job

Closes gh-12917
From reading the docs this is the right invocation. Seems like every step needs skipping individually. Looks like a poor design, but there's no way currently to skip the whole action.

I was able to put the conditional a level up when developing #8779 and it seemed to work on my local fork

(feel free to take the entire conditional from #8779 and put it here and just add this extra condition to it, and I can rebase #8779 )

Thanks Eric, let me give that a try.

I think that the wasteful part here is mainly the schedule line. Can we just get rid of that to start with? I think it can be valuable retaining the ability to run ci on personal forks. Sometimes when I'm making a PR with a lot of changes I use the ci run on my personal fork to fix most of the issues before submitting a PR. Personal ci runs will only occur if people are making commits to their fork, which isnt a large number of people.

It happens each time you push to master though, which happens (a) for people like me who keep their forks up to date, and (b) for newbies who develop on master.
You can also run TravisCI or other CI on your own fork, but it's all opt-in. I'm not sure why we'd want this to be opt-out instead.

I still get two emails with failures every night, so merging this. Thanks for the feedback all. As another follow-up we may document how to run CI on a fork. I'd think TravisCI or Azure would be most useful in catching issues, because of platform support.

Nice one.
GitHub actions runs Linux, windows, macOS, but not arm at the moment.

The GH Actions workflows we have just run macOS though, plus a now-unnecessary build against python3.9-dev?

The point I was trying to make is that gh actions  has as many platforms as the others.
3.10-dev might be possible now.

The point I was trying to make is that gh actions has as many platforms as the others.

It does (almost), but we're not using it. I think if there's really value in running CI on a fork to catch failures, it would be good to make that easy/efficient, so it actually catches the most common issues without running a ton of tests (because then you may as well open a PR straight away). I think a reasonable subset would be:

the lint job
the doc build
one Windows build
one aarch64 build

3.10-dev might be possible now.

We should probably leave that alone for at least 9 months, it's very early in the release cycle so failures are most likely going to be Python or NumPy bugs or changes that will be reverted.


Add experimental cache_selected_only config

resolves #4688
rebased version of #4860
more tracking + testing to come in https://github.com/dbt-labs/dbt-core/issues/4961
Only other changes:

--cache-selected-only (kebab case) instead of --cached_selected_only (snake case)
Add a breaking change note for the internal adapter method (Python code) with a change in its signature. Among our plugins, only dbt-postgres reimplements this method; all the others inherit the base version.

I'd love to include this as "experimental" functionality in v1.1 if possible. We would document it as such: https://github.com/dbt-labs/docs.getdbt.com/pull/1327
Checklist

[x] I have signed the CLA
[x] I have run this code in development and it appears to resolve the stated issue
[x] This PR includes tests, or tests are not required/relevant for this PR
[x] I have added information about my change to be included in the CHANGELOG.

I realized this is a comment on an old PR, but I was experimenting today with cache_selected_only to speed up start up time on our test execution pipelines which run as part of Airflow orchestration. It seems that cache_selected_only only seems to affect dbt run but not dbt test --select "test_name"? From what I've traced, it seems get_model_schemas(...) will return an empty set when one of the selected uids is a test resource, which will result in the entire set of schemas being pulled into the cache. Is this expected?


Firmware v3.0.0a11 broke something

Sorry, I now this is not a proper bug report but I cannot send the whole script I am currently using:
I am using the Droid Commander elements for a robot MOC - Move Hub, the 2 internal motors (A and B) and the external motor (port C) and the ColorDistanceSensor (port D). The robot detects one of 6 custom colors (pre-set with detectable_color() ) and moves motors according to the color.
Also using getchar() so I can order same actions from my laptop and print() to show the detected color or 'Unsure' when not.
I had a script running OK with 3.0.0.a10
After flashing a11 I sent an action that just uses motor in port B
for i in range(0, 5):
     rightFoot.run_angle(900, 120  then=Stop.COAST, wait=True)
     rightFoot.run_angle(900, -120, then=Stop.COAST, wait=True)

It run much faster and never ended. Also couldn't force the Hub to stop or power off, had to remove batteries.
Then I tried just an action just with the color detection - it fail to detect and crashed several times.
Also got an error after entering the main loop:
Traceback (most recent call last):
  File "main.py", in <module>
OSError: [Errno 19] ENODEV

I am going to try to reduce my script to the essential so I can reproduce the error

OK:
With this script motor on Port B spins once then the Hub powers off. It spins once it one direction only so it just executes the first 'run_angle' command. It does the same also with the ColorDistance Sensor unattached.
If I remove the comments, the Hub doesn't power off (either by itself or by pressing the power button, have to remove batteries). And the motor spins forever always in same direction (so the it also just executes the firs 'run_angle' command).
But now the ColorDistance Sensor seems to  be in a  loop through several modes, showing different colors.
from pybricks.hubs import MoveHub
from pybricks.pupdevices import Motor #, ColorDistanceSensor
from pybricks.parameters import Port, Color, Stop, Direction

# Initialize the hub.
hub = MoveHub()

rightFoot = Motor(Port.B)
leftFoot = Motor(Port.A, Direction.COUNTERCLOCKWISE)

#cSensor = ColorDistanceSensor(Port.D)

#my_cyan = Color(h=180, s= 95, v=9, name='MY_CYAN')
#my_white = Color(h=300, s=25, v=20, name='MY_WHITE')
#my_red = Color(h=0, s=90, v=7, name='MY_RED')
#my_green = Color(h=130, s=90, v=9, name='MY_GREEN')
#my_black = Color(h=0, s=0, v=1, name='MY_BLACK')
#my_grey = Color(h=165, s= 31, v=17, name='MY_GREY')
#my_colors = (my_cyan, my_white, my_red, my_green, my_black, my_grey, None)
#cSensor.detectable_colors(my_colors)

def rightfoot():
    for i in range(0, 5):
        rightFoot.run_angle(900, 120, then=Stop.COAST, wait=True)
        rightFoot.run_angle(900, -120, then=Stop.COAST, wait=True)

print("Running...")
rightfoot()


Release candidate 4.2.1

Coverage remained the same at 100.0% when pulling 5b8ca9fd09e0a6c6e8d30c42519ab496c3c16829 on ReleaseCandidate-4.2.1 into d89141bb91f767878049f62e569983ff9f676171 on master.

Coverage remained the same at 100.0% when pulling 18fa1845e37e60630ae06eff80382befb108e508 on ReleaseCandidate-4.2.1 into d89141bb91f767878049f62e569983ff9f676171 on master.


How to simulate 'if debug' without changing source code (using gulp&webpack)

Hi,
So i'm trying to use this GREAT tool but I don't want to change the source code, and I want it to work only in debug mode.  I'm using gulp and webpack to build.
Any ideas, recommendations, examples?
Thanks!

@ron23 you could use webpack.DefinePlugin to create a condition that will be allowed for the debug build but unreachable in the production build.
// webpack.config.js
var webpack = require('webpack');
module.exports = {
  // ...
  plugins: [
    new webpack.DefinePlugin({
      __DEV__: JSON.stringify(process.env.NODE_ENV !== 'production')
    })
  ],
};

In your source you'd have something like this...
// index.js
var immutable = require('immutable');
if (__DEV__) {
  var installDevTools = require('immutable-devtools');
  installDevTools(immutable);
}

Which when you set NODE_ENV=production, __DEV__ will be replaced with false.
NODE_ENV=production webpack index.js dist/index.min.js

generates
var immutable = require('immutable');
if (false) {
  var installDevTools = require('immutable-devtools');
  installDevTools(immutable);
}
// ...

And then by adding the -p shortcut to webpack for production mode which enables dead code elimination, the condition that requires immutable-devtools will be removed.
NODE_ENV=production webpack -p index.js

var immutable = require('immutable');
// ...

Nice! I thought about everything you said but I didn't know the magic -p !!! Thanks a lot!

@ron23 you're welcome! You can also get dead code elimination by adding the uglifyjs plugin new webpack.optimize.UglifyJsPlugin() to the plugins array in your webpack.config.js if you want to tune your production build.

Already using it, just didn't know about the dead code removal feature. Thanks a bunch!

Hi everybody!
This is something that Wiki is interested in :-)
Can anybody write shot paragraph about this in project wiki?

@ron23 Thanks! I've added section Using with webpack in Readme based on your comment


No such file or directory errors after package or make

[x] I have read the contribution documentation for this project.
[x] I agree to follow the code of conduct that this project follows, as appropriate.
[x] I have searched the issue tracker for an issue that matches the one I want to file, without success.

App can access files ( .sh ) inside src/example_folder when running "electron-forge start" but when I "make" or "package" app I get multiple "no such file or directory" errors from shell commands ran with child_process exec.
-Might be unrelated but I get devtools window using start, make , and package. React works fine otherwise.
Where or how should I add files to my project?
Is there a path variable I should be using?
Do I have to set project to production somehow?

Folder structure:
|-src
|---Components
|---actions
|---assets
|-----apks
|-----css
|-----platform-tools
Using<EMAIL_ADDRESS>I have the following packages, all but 'react-desktop' and 'react-icons' are what came with the forge react template. Only BrowserWindow width and height have been edited in index.js.
"dependencies": {
"electron-compile": "^6.4.3",
"electron-devtools-installer": "^2.1.0",
"electron-squirrel-startup": "^1.0.0",
"react": "^15.4.1",
"react-desktop": "^0.3.7",
"react-dom": "^15.4.1",
"react-hot-loader": "^3.0.0-beta.6",
"react-icons": "^3.1.0"
},
"devDependencies": {
"babel-plugin-transform-async-to-generator": "^6.24.1",
"babel-plugin-transform-es2015-classes": "^6.24.1",
"babel-preset-env": "^1.7.0",
"babel-preset-react": "^6.24.1",
"electron-forge": "^5.2.2",
"electron-prebuilt-compile": "3.0.0",
"eslint": "^3",
"eslint-config-airbnb": "^15",
"eslint-plugin-import": "^2",
"eslint-plugin-jsx-a11y": "^5",
"eslint-plugin-react": "^7"
}

This is an Electron thing, once your script is in the asar "exec" doesn't know where to run it from.
https://github.com/electron/electron/issues/3512#issuecomment-158263808


I found that in some testcases   str.toLowerCase(); isn't' working

Challenge Check for Palindromes has an issue.
User Agent is: Mozilla/5.0 (Windows NT 10.0; rv:54.0) Gecko/20100101 Firefox/54.0.
Please describe how to reproduce this issue, and include links to screenshots if possible.
My code:

function palindrome(str)
{

  str.toLowerCase();
  alert(str);
  str=str.replace(/\s+/g,'');
  str=str.replace('-','');
  str=str.replace('_','');
  str=str.replace('.','');
  str=str.replace(')','');
  str=str.replace('(','');
  str=str.replace(':','');
  str=str.replace('/','');
  str=str.replace(',','');
  var a=str.split('');
  a.reverse();
  var b=a.join('');
       if(str==b)
  return true;
  else
  return false;
}

palindrome("0_0 (: /-\ :) 0-0");

I believe you need to assign str to a var. You can assign it to str like so:
str = str.toLowerCase();
I would also recommend using regular expressions to do your replacing process

can  you tell me  best place  to  learn about regex

Dear Sir,
TFYEST me.
[image: --]
Md Xedia
[image: https://]about.me/mxedia
https://about.me/mxedia?promo=email_sig&utm_source=product&utm_medium=email_sig&utm_campaign=chrome_ext
On Thu, Jun 22, 2017 at 3:34 AM, a7n007<EMAIL_ADDRESS>wrote:

can you tell me best place to learn about regex
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/freeCodeCamp/freeCodeCamp/issues/15458#issuecomment-310182238,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ALc8XOMm_Ww_daT0Yhwq38diOyaJgGLWks5sGXBXgaJpZM4OAKv1
.


Attempting to save playground gives 500 internal server error

When trying to save any snippet in the playground a 500 internal server error response is returned from POST https://babylonjs-api2.azurewebsites.net/snippets. The ui displays Unable to save your code. It may be too long. which is unlikely to be the issue (I'm trying to save the default demo)

Hi,
Thanks, just noticed that as well. We are investigating and will repair that asap

Fixed