400-InvalidParameter for node image

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform Version and Provider Version
Terraform 0.14.10
hashicorp/oci v4.22.0
oracle-terraform-modules/oke/oci 3.1.0
Affected Resource(s)
on .terraform/modules/oke/modules/oke/nodepools.tf line 4, in resource "oci_containerengine_node_pool" "nodepools":
4: resource "oci_containerengine_node_pool" "nodepools" {
Terraform Configuration Files
https://github.com/verrazzano/verrazzano/blob/master/tests/e2e/config/scripts/terraform/cluster/VM.Standard2.4-2.tfvars
node_pools = {
"np1" = {
shape = "VM.Standard2.4",
node_pool_size = 4,
boot_volume_size = 50
}
}
Debug Output
Error: 400-InvalidParameter
Provider version: 4.22.0, released on 2021-04-14.
Service: Containerengine Node Pool
Error Message: the image ocid1.image.oc1.iad.aaaaaaaahukmiw6fbgy7p7ger755tzyxiwnr53thtsczgmdb4aceogfmn3cq may not exist or you are not authorized to access it, or nodeShape VM.Standard2.4 is not compatible with image ocid1.image.oc1.iad.aaaaaaaahukmiw6fbgy7p7ger755tzyxiwnr53thtsczgmdb4aceogfmn3cq
OPC request ID: 68d828bcea93966a7fad3fd56d725033/198FFFB6A7F9A0F40C2DDD342C933F02/1FD2A2EA464B4F758ECF903AAD86AF5F
Suggestion: Please update the parameter(s) in the Terraform config as per error message the image ocid1.image.oc1.iad.aaaaaaaahukmiw6fbgy7p7ger755tzyxiwnr53thtsczgmdb4aceogfmn3cq may not exist or you are not authorized to access it, or nodeShape VM.Standard2.4 is not compatible with image ocid1.image.oc1.iad.aaaaaaaahukmiw6fbgy7p7ger755tzyxiwnr53thtsczgmdb4aceogfmn3cq
on .terraform/modules/oke/modules/oke/nodepools.tf line 4, in resource "oci_containerengine_node_pool" "nodepools":
4: resource "oci_containerengine_node_pool" "nodepools" {
Panic Output
Expected Behavior
The OKE cluster provisioned.
Actual Behavior
The OKE cluster creation failed.
Steps to Reproduce
The terraform configuration files are located here https://github.com/verrazzano/verrazzano/tree/master/tests/e2e/config/scripts/terraform/cluster.
Important Factoids
This error only occurs in us-ashburn-1 region when creating v1.18.10 OKE cluster.  We had no problem terraforming with exactly same configuration in regions like eu-frankfurt-1, eu-zurich-1, ap-melbourne-1 , ca-montreal-1, ap-sydney-1 etc.
We specify the shape (VM.Standard2.4) in the node pool, but not the image.
References

@guoyongzhang Could you please change the node_pool_os_version variable to 7.9 instead of  "7.8" and see that solves the issue.

Had a discussion with GZ it seems in ashburn region the top listed image is for ARM  which is different from other region.

@guoyongzhang , have you been able to use the node_pool_image_id instead? Please let us know if this is still an issue

The root cause https://jira.oci.oraclecorp.com/browse/OKE-15061 is marked 'done'.  I am testing it.

us-ashburn-1 is working again.

Reopening this issue as the node_pool_image is taking GPU image id instead of standard vm shape image id

This issue only affects v1.19.7.  v1.18.10 still works.

Starting just now, v1.18.10 stopped working at ap-seoul-1, ca-montreal-1.  It probably true for all regions.  node-pool-options list the image like "Oracle-Linux-7.9-aarch64-2021.05.17-0" as the first one.

I think this could be due to Arm just being GAed for OKE too: https://blogs.oracle.com/cloud-infrastructure/oracle-container-engine-for-kubernetes-oke-support-for-arm-based-instances-is-now-generally-available

I'm assuming a last resort workaround would be to limiting our OKE region usage to 1 region and specifying an exact image OCID to use until things are resolved.
Is there a better way that we can workaround this for now that will work with multiple regions?
thanks

we worked around this for now by providing the exact image ocid for every region

You already have the option of specifying a specific image id: node_pool_image_id
The problem, as you rightly pointed out, is that this will vary by region. We have a fix (see https://github.com/oracle-terraform-modules/terraform-oci-oke/pull/302) but the code has become substantially more complex due to the need to also support ARM shapes as well. It would be great if you can test this fix and let us know how you go.
We also plan on doing the following:

immediate: accept the fix in the PR
future: obtain an enhancement to have a 1st class data source for OKE node pool images similar to core images with the ability to filter by a number of parameters

Please upvote the need for a ds here: https://github.com/terraform-providers/terraform-provider-oci/issues/1285


Windows fixes for dynamic linking

Cheers I've been trying to build luv against pre-built libuv/luajit libraries in Windows using both MSVC and MinGW:
cmake -G (...) -DCMAKE_INSTALL_PREFIX=(...) -DLUA_BUILD_TYPE=System -DWITH_SHARED_LIBUV=ON ..

But ran into some issues with linking, and finding the dependencies, mostly naming related.
That last commit is a fix for MinGW, but there is still something failing with linking, when BUILD_MODULE=ON.

Is this ready to merge?  It looks good to me, but I'm not expert in windows build systems.

@creationix from my end it seems ready, I wasn't able to fix the MinGW builds with BUILD_MODULE=ON, but thats ok. Let me know if you want me to change anything.

Thanks, ping https://github.com/neovim/neovim/pull/4398


Does vue have more event directives as it does in angular js 1

I have worked in angular js , and found that there are many directives in it. There were many event directive as well e.g: ng-click, ng-dblclick etc and many more. Does vuejs has all or more directives like angular. If you can bring them all, it will be a nice and exciting addition I guess.
List of directives on angular
https://www.w3schools.com/angular/angular_ref_directives.asp

Vue supports all standard DOM events: https://vuejs.org/v2/guide/events.html


Add deprecation decorator, deprecate TimeSeriesDataFrame.iter_items

Issue #, if available:
Description of changes:
This PR

Adds a deprecation decorator to ag.core
deprecates TimeSeriesDataFrame.iter_items as it shadows the superclass's iteritems method.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Another thing to potentially discuss related to this PR: Should we do a review of the API of the TimeSeriesDataFrame to make sure that we are consistent with the naming (e.g., we always use item to refer to a single time series, timestep to refer to the value of a timeseries at a specific time, etc.), and also describe this terminology in the documentation / tutorials?

Another thing to potentially discuss related to this PR: Should we do a review of the API of the TimeSeriesDataFrame to make sure that we are consistent with the naming (e.g., we always use item to refer to a single time series, timestep to refer to the value of a timeseries at a specific time, etc.), and also describe this terminology in the documentation / tutorials?

I looked things over pretty quick and I think we look good overall.


Cillium doesn't start in distro-full bundle

Hi
I've installed cozystack 0.15.0 with distro-full configuration.
Problem 1
Cillium doesn't start with default parameters because of error:
level=fatal msg="auto-direct-node-routes cannot be used with tunneling. Packets must be routed through the tunnel device." subsys=daemon

I don't understand why auto-direct-node-routes set to true, but it appears here
packages/core/platform/bundles/distro-full.yaml
31:      autoDirectNodeRoutes: true

Problem 2
so I want to change this parameter via cozystack configmap, but it can't be done - merging autoDirectNodeRoutes: true from distro-full.yaml with custom parameter autoDirectNodeRoutes: false from values-cilium in cozystack configmap results in autoDirectNodeRoutes: true because this is how merge function works
I will appreciate your answer for the question "why does it done like this"?

Hmm, can you please routingMode: native?

Thank you, it works, cilium starts, pod to pod connectivity works

Thank you for the report, this options will be enabled by default since the next release


Cannot automatically update mouse cursor shape or visibility

Operating system or device - Godot version:
Linux/X11 and Windows, Godot 2.1-stable
Issue description (what happened, and what was expected):
Mouse cursor shape and visibility behaves differently in X11 and Windows - cannot automatically update cursor shape or visibility without user interaction.
Steps to reproduce:
X11:

download Mousetest project and run, assume that mouse cursor is inside the window when it starts,
the mouse cursor has busy icon, but it should automatically switch to pointer arrow (it does it after mouse move),
place mouse cursor inside the window and wait 2 seconds; don't move the mouse cursor,
mouse cursor disappears - OK,
move mouse to show the cursor - the mouse cursor automatically changes its shape from Godot theme to system theme (sometimes it happens after second cursor visibility change). And why it doesn't have system theme on X11 as default?

Windows:

download Mousetest project and run,
place mouse cursor inside the window and wait 2 seconds; don't move the mouse cursor,
mouse cursor doesn't disappear automatically, so you must click and don't move the mouse to achieve this (normally you can also move the mouse to hide the mouse cursor, but the script will show it).

Link to minimal example project (optional but very welcome):
Mousetest.zip

First of all thank you for your report and sorry for the delay.
We released Godot 3.0 in January 2018 after 18 months of work, fixing many old issues either directly, or by obsoleting/replacing the features they were referring to.
We still have hundreds of issues whose relevance/reproducibility needs to be checked against the current stable version, and that's where you can help us.
Could you check if the issue that you described initially is still relevant/reproducible in Godot 3.0 or any newer version, and comment about it here?
For bug reports, please also make sure that the issue contains detailed steps to reproduce the bug and, if possible, a zipped project that can be used to reproduce it right away. This greatly speeds up debugging and bugfixing tasks for our contributors.
Our Bugsquad will review this issue more in-depth in 15 days, and potentially close it if its relevance could not be confirmed.
Thanks in advance.
Note: This message is being copy-pasted to many "stale" issues (90+ days without activity). It might happen that it is not meaningful for this specific issue or appears oblivious of the issue's context, if so please comment to notify the Bugsquad about it.

As there was no answer to the above request, we're closing this issue as inactive.
If you can still reproduce it, please open a new issue against a currently supported release of Godot.


[RR2] Push RR2 to the #the-benchmarker and #TEB

Push RR2 beta version to the:

https://github.com/TechEmpower/FrameworkBenchmarks
https://github.com/the-benchmarker

RR2 can't be pushed as a standalone application. Instead, the Spiral app should be updated. Closing this issue.

RR2 can't be pushed as a standalone application. Instead, the Spiral app should be updated. Closing this issue.


Identify opportunities for Self-Service features in the Sender Onboarding Process

Problem statement
Research exists for the Intake/Interest and Kickoff processes on the Sender Onboarding lifecycle. We would like to identify areas of those processes that can be "self-served" to eliminate the need for hands-on interaction with ReportStream engineers and support staff.
What you need to know
Background Materials

Kickoff SOP
Original Service Blueprint
WIP New Service Blueprint
Existing Sender Settings and Okta Mural

Working Link

Interest & intake phase self-service opportunities Mural

Acceptance criteria

[x] Opportunities for self-service on the Interest/Intake and Kickoff phases are clearly identified and ready for discussion
[x] Review with Jillian and Chris

To do

[x] Desk research: review all of the existing documents
[x] Set up a scratchpad Mural to copy paste the existing flows
[x] Annotate opportunities as stickies on top of the flow

On 05/11 met with @jillian-hammer to discuss the ticket and get some context about the work. @chris-kuryak and Jillian helped define the scope for this ticket prior. The work as defined is using existing research to define areas of opportunity. During our meeting, we aligned on:

Start reviewing existing documents
Jillian will start a mural board for us

Note: There is interest to collaborate on identifying opportunities from the Engagement designers despite this ticket being scoped as only reviewing existing research/documents. See thread here on that discussion that @audreykwr helped start. During the existing weekly design sync on 05/15 (held twice weekly Mon & Thurs), there will be a discussion with the design team on identifying some of these opportunities.

hi, two updates for you @yudonoodles:

I set up the Mural workspace. I will continue to refine it this afternoon, but feel free to pop in if you make a note of anything as you review the SOP
I gave this ticket 3pts, but let me know if that feels inaccurate and we can adjust!

Thanks @jillian-hammer for setting up the mural board. 3 pts sounds good to me.
Note: During the usual design crit on Thursday, engagement designers will present some research that they have done on summarizing pain points or potential opportunities.

@jillian-hammer & Tshering met with @chris-kuryak on 05/19, presented flow diagram based on kickoff SOP doc and tiered (low, mid, high) measure of opportunities. Based on feedback from Chris, I updated the following on the mural board:
* Clearly segmented sticky notes to specific legends
* Added swim lanes and content for: 1. Specific artifacts and 2. Who's responsible for those artifacts
* Included images and links where applicable
* Followed up on “Informational meeting” step in onboarding with Dylan and Jessica: That step seems STLT facing and isn’t a standard step in onboarding a sender, removing the step from mural as a result.
* Organized and cleaned up mural board

Ticket is closed, but want to log follow-up meetings:
05/23 Meeting with Chris, Jillian, Tshering and Lizzie on 05/23 discuss next steps and alignment:

Discussion surrounding opportunity to improve sender intake form, if by improving that small piece, there could be an opportunity to help senders onboard without help from RS team.
During that discussion, I brought up an addition to the mural where I laid out three tiers of matching that might be happening: light, medium and heavy and at each of these checkpoints, we are checking if the sender and RS is the right fit, that way there is a robust system that doesn't move forward unless it passes the matching at those points, and critically making sure the early light matching is being considered and thinking about how to improve that so that down the line, the senders who we don't match with does not go through to the next step, and instead there is an opportunity to redirect them to other resources. Potentially this could be a future line of discovery.

05/24 Meeting with Chris, Tshering and Sharon, Customer Service Lead to discuss Smartsheet Service Request Forms and an opportunity to update them.

Meeting notes and some takeaways were already captured here. In general, found it super helpful to understand challenges in getting senders to fill out the form, how data from those forms are managed and also got some validation on issues surrounding matching with senders and moving them forward to a kickoff call despite not meeting the requirements in order to connect with RS.

Want to note two big takeaways from this research for future exploration/possible tickets:

Sender specific approach: An opportunity to create a step by step process for users to move forward during onboarding prior to meeting with the RS team where they can clearly move forward on their own via the ui/site. A medium tier lift opportunity could be to experiment with connecting existing disparate pages, such as file validator or public key tool and api programmer's guide, into a streamlined and linear manner and adding clarity on what's needed to be done at each stage before they move to the next. The first stage of this work could cover the ground of supporting the customer service team with creating a better way to match a sender to RS.

Internal team approach: On the internal side of onboarding, this research also noted the need to centralize data/information internally, and a future line of work could be to streamline artifacts in a manner where they feed a centralized "source of truth" tracker automatically without the need for manual updates.

In both cases, further discovery is needed, however we could explore the first opportunity since some of those pages that senders are being asked to use already exists, and we could explore how to connect or centralized them in a given location without needing to be directed by a person. Goal would be to make it intuitive and user-friendly.
cc: @lizzieamanning @chris-kuryak


AttributeError: module 'jax' has no attribute 'xla'

Run the code with jax-0.4.14,but AttributeError: module 'jax' has no attribute 'xla'.What's the matter?

Thanks for asking. Released code is developed with jax==0.2.12 and jaxlib==0.1.65+cuda102. Jax-0.4 will leads to unexpected issues.


ORC-831: Do Not Copy String When Flushing Dictionary

What changes were proposed in this pull request?
The code to flush first loads (copies) the data into a Text object and then writes it to the direct stream. Instead, pass the directStream to the dictionary and have it write directly to the stream instead of an intermediate Text object.
Why are the changes needed?
Performance.
How was this patch tested?
No change in behavior so using existing unit tests.

Sorry for adding last-minute comments after approval. Please consider the above comments.

Sorry for adding last-minute comments after approval.

No worries at all. Thanks for being engaged and helping me get these PRs reviewed.  You are very generous with your time.
I'll address your comments.

Thank you, @belugabehr and @pgaref


Submit pull request

Requirement was considered unreasonable. Fix of decent quality is not achievable, and submitting subpar work would bring public shame to the team and waste the time of the original project's developers.
Course staff has been informed about the issue.

Pull request submitted against main branch on our main repository. SonarCloud quality gate passed.


Syncing with upstream ipfs-service-provider

:tada: This PR is included in version 3.2.2 :tada:
Your semantic-release bot :package::rocket:


[Bug] Cisco parser views for hyperglass user not working with v1.0.0-beta.78

Hello,
it seems that parser views for locking-down the hyperglass user on Cisco IOS-XE are currently not working with the latest hyperglass beta.  I configured the looking glass user according to https://hyperglass.readthedocs.io/en/latest/extras/securing-router-access/ like the following:
username hyperglass privilege 15 view looking-glass secret 9 xxx
!
parser view looking-glass
 secret 9 xxx
 commands exec include all traceroute
 commands exec include all ping
 commands exec include all terminal width
 commands exec include all terminal length
 commands exec include terminal
 commands exec include all show bgp
 commands exec include show
!

From the hyperglass logs:
[INFO] 20210216 22:55:20 | scrapli.driver.async_driver:100 | open → Opening connection to router1.evilcorp.local
[INFO] 20210216 22:55:20 | scrapli.driver.base_network_driver:318 | _pre_acquire_priv → Attempting to acquire `privilege_exec` privilege level
[INFO] 20210216 22:55:20 | scrapli.driver.base_network_driver:389 | _process_acquire_priv → Attempting to escalate from exec to privilege_exec
[CRITICAL] 20210216 22:55:49 | hyperglass.exceptions:40 | __init__ → [DANGER] Error connecting to router1.evilcorp.local: Request timed out.
/usr/local/lib/python3.8/dist-packages/scrapli/driver/base_network_driver.py:300: UserWarning:
***** Privilege escalation generally requires an `auth_secondary` password, but none is set!
scrapli will try to escalate privilege without entering a password but may fail.
Set an `auth_secondary` password if your device requires a password to increase privilege, otherwise ignore this message.
***** Privilege escalation generally requires an `auth_secondary` password, but none is set!
  warnings.warn(warning)
Exception in callback Loop._read_from_self
handle: <Handle Loop._read_from_self>
Traceback (most recent call last):
  File "uvloop/cbhandles.pyx", line 73, in uvloop.loop.Handle._run
  File "uvloop/loop.pyx", line 359, in uvloop.loop.Loop._read_from_self
  File "uvloop/loop.pyx", line 364, in uvloop.loop.Loop._invoke_signals
  File "uvloop/loop.pyx", line 339, in uvloop.loop.Loop._ceval_process_signals
  File "/usr/local/lib/python3.8/dist-packages/hyperglass/execution/main.py", line 34, in handler
    raise DeviceTimeout(**exc_args)
hyperglass.exceptions.DeviceTimeout: Error connecting to router1.evilcorp.local: Request timed out.
[ERROR] 20210216 22:55:50 | hyperglass.execution.drivers.ssh_scrapli:126 | collect → Timed out sending input to device.
[CRITICAL] 20210216 22:55:50 | hyperglass.exceptions:40 | __init__ → [DANGER] Error connecting to None: Request timed out.

After removing the parser view from the user it works as expected.
Why hyperglass needs to escalate privileges anyways?
Thanks

Just as an FYI, the docs you linked are for the original or v0 version of hyperglass - not the beta. I'm still leaving those docs up (with a warning), since v0 is still technically available. That being said, the parser view config is still correct and works just fine for me on a production Cisco IOS-XE router in my organization. This is directly off my router, secrets excluded:
username lg privilege 15 view lg secret <secret>

parser view lg
 secret <secret>
 commands exec include all traceroute
 commands exec include all ping
 commands exec include all terminal width
 commands exec include all terminal length
 commands exec include terminal
 commands exec include all show bgp
 commands exec include show

It looks like your router requires an enable password - this may be a key difference between your router and mine. The best way to test/verify this would be to log in to the router as the hyperglass user (with the parser view enabled) and try to run the commands manually. For Cisco IOS, see here for the defaults.
I, personally, find requiring an enable password to be obtuse, and so generally my AAA config for local auth is something like:
aaa new-model
aaa authentication login default local
aaa authentication enable default enable
aaa authorization console
aaa authorization exec default local

The result is that any user logging in is at an exec prompt, not an enable prompt. Then, to lock down any accounts, the parser-view works perfectly. That may or may not be "correct", and may or may not fit your org's security policies, but it's worked for me for many years.
All of that said, I could add the ability to specify an enable password (which would map to the auth_secondary password Scrapli is referring to in your log output), if it's really necessary. I will throw out there - hyperglass has been available one way or another for nearly 2 years and this is the first time it's come up :) But, if it's needed, I can add it.

Thank you very much @checktheroads for the detailed response! I can confirm that after disabling the enable password it works as expected. I've just adapted your AAA config and this works fine.
Thank you again very much - also for developing this awesome tool!


Update google-cloud-daos version from v0.4.0 to v0.4.1

google-cloud-daos v0.4.1 was released to fix 2 bugs.
See https://github.com/daos-stack/google-cloud-daos/releases/tag/v0.4.1
This change updates the version number referenced in the community/examples/intel/*-daos.yaml blueprints.
Made a few minor updates in the community/examples/intel/README.md
Submission Checklist
Please take the following actions before submitting this pull request.

Fork your PR branch from the Toolkit "develop" branch (not main)
Test all changes with pre-commit in a local branch #
Confirm that "make tests" passes all tests
Add or modify unit tests to cover code changes
Ensure that unit test coverage remains above 80%
Update all applicable documentation
Follow Cloud HPC Toolkit Contribution guidelines #

/gcbrun

/gcbrun


opentitantool: Rustfmt fix

Rustfmt insisted on putting a semicolon after the return statement in the custom bail!()
macro.  However, having that semicolon caused the Rust compiler to emit a warning, when the macro
was used in an expression context (as in match ... { _ => bail!(...), }.  Adding an extra level
of curly brackets seems to satisfy both rustfmt and the Rust compiler.
Signed-off-by: Jes B. Klinke<EMAIL_ADDRESS>Change-Id: I6735dc3ad40ac943347ddb8dc55cb6148f10e43f

This sounds like a bug in rustfmt. Can you also file a bug against them where formatting causes warnings to be emitted?


Python scripts for fuzzing

Hi there,
Erik Imgrund, a friend of mine, recently wrote a python program to simplify the usage of AFLGo. It's an alternative to bash scripts that - at least in our opinion - are very powerful but sometimes quite frightening and not easy to understand/adapt/play around with.
Pros and Cons
I'd like to adapt the Python program and incorporate it into AFLGo (this is cleared with Erik Imgrund) as I feel other users would benefit from it. Python has a nice syntax, is easy to learn and widespread. It's heavily used in the fields of machine learning which would simplify the process to use AFLGo. Cons are that we have duplicate scripts, so there are two places to adapt if the API is changing some day. Yet, that's also the case right now with the sample shell scripts.
I'd like to open a pull request to AFLGo if the general idea described here is welcome. If so, it'd be great to know where a good place would be to place the scripts.
All the best,
Dominic

Hi Dominic and Eric, Absolutely! Your help is much appreciated. Looking forward to your PR!

Ok great, I'm probably going to prepare it during this or next week...


Create suppress key for xslt streaming warning

Closes #2775

Could you provide a backport to 7.7 too?


@broskoski: use correct properties

Another one. This is the microgravity equivalent for https://github.com/artsy/force/pull/719

👍


Restore command

Change Overview
bash-4.4# kopia restore --help
usage: kopia restore <root-id> <target-path>

Commands to restore snapshots.

Flags:
      --help                  Show context-sensitive help (also try --help-long and --help-man).
      --help-full             Show help for all commands, including hidden
      --trace-object-manager  Enables tracing of object manager operations.
      --trace-localfs         Enables tracing of local filesystem operations
      --config-file="/Users/pdevaraj/Library/Application Support/kopia/repository.config"
                              Specify the config file to use.
  -p, --password=PASSWORD     Repository password.
      --use-keychain          Use macOS Keychain for storing repository password.
      --log-file=LOG-FILE     Log file name.
      --log-dir="/Users/pdevaraj/Library/Logs/kopia"
                              Directory where log files should be written.
      --log-level=info        Console log level
      --file-log-level=info   File log level
      --version               Show application version.

Args:
  <root-id>      Snapshot Root ID from which to restore.
  <target-path>  Path to which the snapshot must be restored.

Walks through all the entries for the given root ID and restores all the files/directories recursively.
Yet to address: symlinks
Pull request type

[x] 🌻 Feature

Test Plan
🚀 Manually backed up and restored a directory structure successfully.
Added checks to prevent override of existing files.
pdevaraj @ ~/Work/Kasten/kopia - [restore_test] $ ./kopia restore ke01a036be699f043a5677ed7c8858af8 ./tmp
pdevaraj @ ~/Work/Kasten/kopia - [restore_cmd] $ kopia restore ke01a036be699f043a5677ed7c8858af8 ./tmp
kopia: error: unable to create a new file, tmp/d1/f4.txt already exists, try --help

Sorry for creating a new PR, the local copy was messed up as well.

Here is a summary of the modifications I made to the initial PR:

[x] Added restore of file attributes => mod time, mode, owner info
[x] Consolidated code for restoring file attributes (both for files and directories)
[x] Added ability create top directory on restore, otherwise the user would need to pre-create it
[x] Added ability to restore in the root folder. This is a special case where the top directory is not created.
[x] Renamed functions and moved copy functionality to localfs package. The functionality is relatively general and does not depend on the snapshotfs package. Any implementation of the corresponding fs interfaces can be used as the source. The target is the local file system.
[x] Fixed nits for error formatting

Pending:

[ ] Fail when a target directory already exists. In general, this should not happen when restoring to a new top directory, but it could happen when restoring to the root directory, or due to a race condition with an external tool that manages to create a directory to be restored before Kopia creates that directory. Currently, the copy functionality errs on the conservative side, but we may want to add a flag to override this behavior. Imagine when trying to restore something in a rush, or restarting a restore, one may want to simply overwrite everything without having to remove it first. Anyway, needs additional thought.
[ ] log when restoring a symlink, currently not implemented.

Not currently implemented:

Restoring the attributes of the top directory. Needs additional support in snapshotfs to get the appropriate top-level entry. And it may not be possible in all cases. TODO: open an upstream issue for this.
Restoring symlinks. Need digging into additional details about how to consistently handle file/link attributes. Also, should not restore symlinks that point to files outside of the tree being restored. Rsync has a feature that restores symlinks in a separate shadow directory.
Flags to overwrite target.
Flags to ignore errors or choose whether or not to restore file attributes.

@redgoat650 Can you take a look at the additional changes?
There is a separate PR (#7) with the end-to-end test for this, which is currently up-to-date.

Merging into the restore branch in order to open an upstream PR.


Taxi program from codeforces

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
I want to add the solution of taxi problem from code forces.
Problem link-https://codeforces.com/problemset/problem/158/B
Programming language

[ ] C
[x] C++
[ ] Java
[ ] Python
Please assign it to me under lgmsoc @Ayush7614 @Amit366

you can work on it @Khushi-agarwal


chore: bump mlserver-xgboost for Seldon version 1.15.x -> 1.17.1

Update ROCK according to upstream changes but also:

introduce parts that we missed in the ROCK
use ubuntu 20.04 as base due to https://github.com/canonical/seldonio-rocks/issues/39
refactor tox.ini according to https://github.com/canonical/oidc-authservice-rock/pull/14 and https://github.com/canonical/bundle-kubeflow/issues/763
update test_rock.py according to latest changes in chisme https://github.com/canonical/charmed-kubeflow-chisme/pull/81

Details for changes in https://github.com/canonical/seldonio-rocks/issues/37.
Closes https://github.com/canonical/seldonio-rocks/issues/52

Rebased on top of main to bring new CI changes needed to run tests, plus pushed a new commit due to https://github.com/canonical/seldonio-rocks/issues/70


Page layout assignment through the Metadata Api is not properly working

I am using the following code to try and automate pagelayout assignment for a given profile.  It runs fine without any errors.  When I go into setup/profiles/ view assignment, it appears to be assigned to the correct page layout.
However, when I try to open up a record an view it, it is still using the prior page layout.  If I go back into settings/profiles/ and edit/save the assignment (make no changes, just edit/save) it appears to work.  So I must be missing a step when I am setting the Page Layout Assignment?  I'm stumped.  Any help would be very much appreciated!
`
public static void editPageLayoutAssignmentsForProfile(string profileName, ListpageLayoutNames) {
if (!String.isBlank(profileName)) {
MetadataService.MetadataPort service = createService();
MetadataService.IReadResult readResult =
service.readMetadata('Profile', new String[]{
profileName
});
MetadataService.Metadata[] records = readResult.getRecords();
        MetadataService.Profile p = (MetadataService.Profile) records[0];
        System.Debug('Found Profile:' + p.fullName);
        p.tabVisibilities = new MetadataService.ProfileTabVisibility[]{}; // this line of code is required to get around some bogus tab error:  "You can't edit tab settings for WorkRewardFund, as it's not a valid tab.

        for (String pageLayout : pageLayoutNames) {

            Boolean isClassEnabled = false;

            MetadataService.ProfileLayoutAssignment pl = new MetadataService.ProfileLayoutAssignment();

            //Remove existing layout
            Integer intIndex = 0;
            for(MetadataService.ProfileLayoutAssignment pa : p.layoutAssignments) {
                if(pa.layout.substring(0,25) == pageLayout.substring(0,25)) {
                    p.layoutAssignments.remove(intIndex);
                    System.Debug('Removed Assignment: ' + pa.layout);
                    break;
                }
                intIndex++ ;
            }

            pl.layout = pageLayout;

            pl.recordType = null;

            p.layoutAssignments.add(pl);
        }

        MetadataService.SaveResult[] sr = service.updateMetadata(new MetadataService.Metadata[]{p
        });
        if (sr != null) {
            System.debug('editPageLayoutAssignmentsForProfile error ' + sr[0].errors);
        }

    }
}

`

Hmmm this could be some kind of caching thing i suspect. If you use something like Force.com or Developer Workbench to pull down the profile metadata (you will need to include your object and tab in the package manifest), does the profile xml differ before and after you resave it in the UI?

Nope, the profile xml is the same before/after I resave in the UI.  How do you flush the cache?

As far as i know there is no way to programatically flush the cache. It seems like this is being done by reading the profile from the UI. I wonder if doing this via SOQL might do it?

@CraigHoneyfieldIS please comment further if you are still having issues here.

Just come across the exactly the same problem, using C# and wsdl/soap 44.0.  Only clicking Edit on a profile, then Save without any changes, gets the page layout changes available.  I found the same behaviour with Tab Settings - I set to DefaultOn rather than Hidden and the tab remains hidden until Edit/Save on the profile is carried out.
Incidentally I don't read any metadata in the program, simply pull together a new Profile object and apply it to existing profiles in Salesforce with UpdateMetadata(Metadata[]).
I have only a dozen profiles, and one database, to apply this to, so manual update/save is ok.  But as everything else I do works just fine programmatically (creating new objects, fields, page layouts, tabs) it's a niggle.

@CraigHoneyfieldIS @jingramcamfed I'm running into this issue as well.
Did you ever got the Profile Layout Assignments to work without using the UI to save the new assignments?

Hi fjgalesloot
No I never did get it working.  That said, I've not touched the metadata api since my comment so can't add anything else I'm afraid.


NullPointerException on Terrastore

I am presently encountering a NullPointerException when attempting to do any
predicate search operations on a specific bucket (the issue does not occur on
other buckets).  The following are the top several frames from a stack trace.
I am attaching the full stack trace.

Terrastore Server 0.8.1 - 16:35:07.931 - null
java.lang.NullPointerException: null
at org.msgpack.Packer.packString(Packer.java:335) ~[msgpack-0.4.3-devel.jar:na]
at terrastore.util.io.MsgPackUtils.packString(MsgPackUtils.java:60)
~[terrastore-0.8.1.jar:na]
at terrastore.common.ErrorMessage.messagePack(ErrorMessage.java:67)
~[terrastore-0.8.1.jar:na]
at org.msgpack.Packer.pack(Packer.java:447) ~[msgpack-0.4.3-devel.jar:na]
at terrastore.util.io.MsgPackUtils.packErrorMessage(MsgPackUtils.java:81)
~[terrastore-0.8.1.jar:na]
at
terrastore.communication.protocol.AbstractResponse.messagePack(AbstractResponse.
java:62) ~[terrastore-0.8.1.jar:na]
at org.msgpack.template.ClassTemplate.pack(ClassTemplate.java:53)
~[msgpack-0.4.3-devel.jar:na]
at org.msgpack.template.AnyTemplate.pack(AnyTemplate.java:30)
~[msgpack-0.4.3-devel.jar:na]
at org.msgpack.Packer.pack(Packer.java:452) ~[msgpack-0.4.3-devel.jar:na]
at terrastore.util.io.MsgPackSerializer.doSerialize(MsgPackSerializer.java:79)
[terrastore-0.8.1.jar:na]
at terrastore.util.io.MsgPackSerializer.serialize(MsgPackSerializer.java:52)
[terrastore-0.8.1.jar:na]
at
terrastore.communication.remote.SerializerEncoder.encode(SerializerEncoder.java:
38) [terrastore-0.8.1.jar:na]
at
org.jboss.netty.handler.codec.oneone.OneToOneEncoder.handleDownstream(OneToOneEn
coder.java:66) [netty-3.2.2.Final.jar:na]
at
org.jboss.netty.channel.StaticChannelPipeline.sendDownstream(StaticChannelPipeli
ne.java:385) [netty-3.2.2.Final.jar:na]
at
org.jboss.netty.channel.StaticChannelPipeline.sendDownstream(StaticChannelPipeli
ne.java:380) [netty-3.2.2.Final.jar:na]
at org.jboss.netty.channel.Channels.write(Channels.java:611)
[netty-3.2.2.Final.jar:na]

Original issue reported on code.google.com by<EMAIL_ADDRESS>on 19 Mar 2011 at 11:53
Attachments:

ts-npe-exception.txt

I've not yet seen it come up again since.  I'll update to the new version soon
and aim to be able to get you something more useful if/when it occurs next.

Original comment by<EMAIL_ADDRESS>on 21 Mar 2011 at 6:10

Do you get the same exception with the Java Client or Curl too?
Which bucket and predicate are you using?

Original comment by<EMAIL_ADDRESS>on 20 Mar 2011 at 9:47

Changed state: Accepted
Added labels: Type-Defect, Project-Terrastore, Priority-High

I've made some investigations: to make a long story short, the exception you
see there is caused by a null error message, so a minor problem; the real
problem is *what* caused that exception, but I don't have enough information
there to determine that.

So, if you can't provide a way to reproduce the problem, the best I can do is
to improve the exception logging so that the next time we will see the original
exception.

Original comment by<EMAIL_ADDRESS>on 21 Mar 2011 at 10:11

Changed title: NullPointerException on Terrastore
Changed state: Started
Added labels: Milestone-0.8.2

Sorry, I've already reset the bucket to continue getting work done (the issue
was preventing my application from working correctly).

I was using the js predicate but didn't try jxpath or any others.  I should
point out that perhaps the issue wasn't so much the use of a predicate as an
issue fetching a specific document.  This occurred during a programmatic
bulk-load operation, where rapid calls to PUT and GET were running in sequence.

However, fetching all documents -was- working.

If it's useful, the following trace is from the second Terrastore node a few
seconds later:

Terrastore Server 0.8.1 - 16:35:17.930 - Communication timeout!
terrastore.communication.CommunicationException: Communication timeout!
at
terrastore.communication.remote.RemoteNode.send(RemoteNode.java:153)~[terrastore
-0.8.1.jar:na]
at
terrastore.service.impl.DefaultQueryService$5.map(DefaultQueryService.java:204)
~[terrastore-0.8.1.jar:na]
at
terrastore.service.impl.DefaultQueryService$5.map(DefaultQueryService.java:196)
~[terrastore-0.8.1.jar:na]
at terrastore.util.collect.parallel.ParallelUtils$1.call(ParallelUtils.java:53)
~[terrastore-0.8.1.jar:na]
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
~[na:1.6.0_23]
at java.util.concurrent.FutureTask.run(FutureTask.java:138) ~[na:1.6.0_23]
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:8
86) ~[na:1.6.0_23]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
~[na:1.6.0_23]
at java.lang.Thread.run(Thread.java:662) ~[na:1.6.0_23]

Original comment by<EMAIL_ADDRESS>on 20 Mar 2011 at 5:04

I think I have uncovered the root of the problem--or if not this problem
specifically, then a related problem.  It appears that calls to
bucket(name).clear() do not take effect immediately, and it's probably my fault
for assuming they do.

Namely, if I call:

client.bucket("test").clear()
client.bucket("test").key("1").get(...);

I may in fact still retrieve 1.  Alternatively, if I attempt to put "1" with an
"if:absent" predicate, that predicate may fail because key "1" may still exist
immediately following a clear() call.

In my usage, the situation is more likely to occur if the server has been
moderately busy with a rapid-fire sequence of puts and gets.  (In my scenario,
it's a bulk-load script that more or less resets my data store to a default
state for development and testing.)

For the time being, I've simply added some pauses in the script after each
clear() method.

Original comment by<EMAIL_ADDRESS>on 23 Apr 2011 at 12:15

Fixed ErrorMessage to avoid failing with NPE on null message.

Original comment by<EMAIL_ADDRESS>on 26 Mar 2011 at 3:23

Changed state: Fixed

Yes, the "clear" operation isn't synchronous, meaning it takes time to
propagate in the cluster, and is a rather heavy one.

Unfortunately, as of now I don't have a solution for your problem: can you
tolerate it?

Thanks for the feedback!

Sergio B.

Original comment by<EMAIL_ADDRESS>on 26 Apr 2011 at 10:12


Speedup CI by bootstrapping PowerShell module installations in background and in parallel, whilst the .NET SDK is being installed

PR Summary
Most of the time is spent bootstrapping the .NET SDK, meaning the installation of other required PowerShell modules can be done in the background and in parallel. This reduces the build time by around 20 seconds. Due to indentation shift, please use a white-space ignoring diff.
PR Checklist

[x] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[x] Summarized changes
[x] Change is not breaking
[x] Make sure all .cs, .ps1 and .psm1 files have the correct copyright header
[x] Make sure you've added a new test if existing tests do not effectively test the code changed and/or updated documentation
[x] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: to the beginning of the title and remove the prefix when the PR is ready.

@JamesWTruher need you to review this one


Fix: edge cases in the Karabina cyclotomic square decompression

Description

Fixes #858
TODO:

[x] Emulated BW6-671
[x] Native BLS12-377
[x] Native BLS24-315

Type of change

[x] Bug fix (non-breaking change which fixes an issue)

How has this been tested?

The multi-pairing computation e(P,Q)*e(-P,Q) returns 1. In this case the g3 == g2 == 0 edge case is triggered. The function PairingCheck() and corresponding test were added to emulated bw6-761 and 2-chains.
How has this been benchmarked?

1 pairing
BW6-761
BLS12-377
BLS24-315

R1CS
2,764,966
11,842
29,033

SCS
28,191,311
52,843
14,1870

The edge case fix introduces some constraints counting regression.
Checklist:

[x] I have performed a self-review of my code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] I have added tests that prove my fix is effective or that my feature works
[x] I did not modify files generated from templates
[x] golangci-lint does not output errors locally
[x] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged and published in downstream modules

I'm not sure if g4=0 is relevant for two-chains. But otherwise looks good.

It is covered implicitly to save some constraints. When g3==g2==0 we should return 1 but we do nothing because the result in 2-chains happen to be 1 implicitly. First, g4 is set to 0becauseg4=e.C1.B1.DivUnchecked(api, t[0], t[1])usesE2Inverse which is afp.ElementInverse which returns conventionally 0 when denominator is 0. Then the remaining computation returnsE * (2 * g4² + g3 * g5 - 3 * g2 * g1) + 1which is exactly 1 becauseg2==g3==g4==0`. We cannot do the same implicit trick in emulated BW6-761 because there the hinted division use big.Int ModInverse. There is a comment explaining this here: https://github.com/Consensys/gnark/blob/baaf4ba836f8bfb7c468b7e46c101f3c8f436269/std/algebra/native/fields_bls12377/e12.go#L295

I'm not sure if g4=0 is relevant for two-chains. But otherwise looks good.

It is covered implicitly to save some constraints. When g3==g2==0 we should return 1 but we do nothing because the result, in 2-chains, happen to be 1 implicitly. First, g4 is set to 0 because g4=e.C1.B1.DivUnchecked(api, t[0], t[1]) uses E2 Inverse which is a fp.Element Inverse which returns conventionally 0 when denominator is 0. Then the remaining computation returns E * (2 * g4² + g3 * g5 - 3 * g2 * g1) + 1 which is exactly 1 because g2==g3==g4==0. We cannot do the same implicit trick in emulated BW6-761 because there the hinted division uses big.Int ModInverse. There is a comment explaining this here:
https://github.com/Consensys/gnark/blob/baaf4ba836f8bfb7c468b7e46c101f3c8f436269/std/algebra/native/fields_bls12377/e12.go#L295

Makes sense!


Installing nokogiri on docker SOMETIMES fails for various gems

When installing on a docker container any gem that depends on nokogiri seems to have a chance to fail to install nokogiri despite libxml2 being installed:
root@8d13f6c18f81:/usr/src/application# apt-get install libxml2-dev
Reading package lists... Done
Building dependency tree
Reading state information... Done
libxml2-dev is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

This is a log of me installing: https://gist.github.com/krainboltgreene/a9263dcf3d2f18165405
The contents of /usr/src/application/gems/ruby/2.1.0/extensions/x86_64-linux/2.1.0-static/nokogiri-<IP_ADDRESS>/gem_make.out: https://gist.github.com/krainboltgreene/7c8cbcc794f10616147b
The contents of /usr/src/application/gems/ruby/2.1.0/gems/nokogiri-<IP_ADDRESS>/ext/nokogiri/tmp/x86_64-pc-linux-gnu/ports/libxml2/2.9.2/compile.log: https://gist.github.com/krainboltgreene/9b02bac88fb461e34774

Hi @krainboltgreene,
Thanks for asking this question. Nokogiri <IP_ADDRESS> vendors a version of libxml2 and libxslt, so you shouldn't need to apt-get install them (and, in fact, without using --use-system-libraries nokogiri's installation process will ignore them).
In your compile.log I spot this line:

virtual memory exhausted: Cannot allocate memory

My guess is that you need to bump up the amount of memory allocated to your Docker container so that the linker can run.
If you have followup questions, please ask them on the mailing list, as requested at http://www.nokogiri.org/tutorials/getting_help.html so that other people will be able to easily find our conversation in the future.
Thanks!

Awww yesh. You rock!
On Sep 10, 2015 5:18 AM, "Mike Dalessio"<EMAIL_ADDRESS>wrote:

Hi @krainboltgreene https://github.com/krainboltgreene,
Thanks for asking this question. Nokogiri <IP_ADDRESS> vendors a version of
libxml2 and libxslt, so you shouldn't need to apt-get install them (and, in
fact, without using --use-system-libraries nokogiri's installation
process will ignore them).
In your compile.log I spot this line:
virtual memory exhausted: Cannot allocate memory
My guess is that you need to bump up the amount of memory allocated to
your Docker container so that the linker can run.
If you have followup questions, please ask them on the mailing list, as
requested at http://www.nokogiri.org/tutorials/getting_help.html so that
other people will be able to easily find our conversation in the future.
Thanks!
—
Reply to this email directly or view it on GitHub
https://github.com/sparklemotion/nokogiri/issues/1347#issuecomment-139217215
.

BOOM. Virtual high-five.


EntryTest.java:54-56: Tests to produce-consume data....

The puzzle 81-60413ccb from #81 has to be resolved:
https://github.com/eo-cqrs/eo-kafka/blob/d5135f5697fcaf3d2e442dd79874afd06a5a1c76/src/it/producer-consumer-api/src/test/java/EntryTest.java#L54-L56
The puzzle was created by @l3r8yJ on 06-Apr-23.
role: DEV.
If you have any technical questions, don't ask me, submit new tickets instead. The task will be "done" when the problem is fixed and the text of the puzzle is removed from the source code. Here is more about PDD and about me.

@l3r8yJ 0.1.3

@h1alexbel yes, it's from #81, still don't know what's wrong

I'm investigating what's wrong with producer

I bet it's a network problem

@l3r8yJ problem gone

@h1alexbel nice!

@l3r8yJ our API has few bugs, I tested all of the stuff on vanilla Kafka API, succeeded.
For now I can submit it with vanilla API and create a ticket to refactor it with EO-Kafka API

@h1alexbel sure, we need to fix them all, waiting to your puzzles

@0pdd 4 puzzles #287, #288, #289, #290 are still not solved.

@0pdd 3 puzzles #304, #305, #306 are still not solved; solved: #287, #288, #289, #290.

@0pdd 2 puzzles #304, #306 are still not solved; solved: #287, #288, #289, #290, #305.

@0pdd the puzzle #304 is still not solved; solved: #287, #288, #289, #290, #305, #306.

@0pdd all 7 puzzles are solved here: #287, #288, #289, #290, #304, #305, #306.


Explain adding slackbot

Note that you need an open integration

Explain how to add an integration

Custom integrations:
-- yourteam.slack.com/apps/manage/custom-integrations
-- go to "bots"
-- Click "add configuration"
-- Fill in with "@carebot"
-- Click "Add integration
-- That will give you an API token
-- NB: we should supply an icon for this screen

You might want to create a private channel for testing the bot

You'll have to invite the bot to the channels you want

note to people that once you make a channel private it can't be made public later.

@livlab Can you drop the Carebot png icon in this issue?

https://github.com/thecarebot/thecarebot.github.io/blob/master/images/Carebot.png


[TEST] Fail the linter

@wsipak somehow the review comments don't show up. https://github.com/lowRISC/ibex/runs/3620371102?check_suite_focus=true has the log, which says at the beginning:

fatal: couldn't find remote ref lint-test-failing
error: pathspec 'lint-test-failing' did not match any file(s) known to git
the PR branch is lint-test-failing

Do you have an idea what's going on? I don't see a similar error in the runs you've done in your branch (but that doesn't need to mean anything).

Or do I need to configure reviewdog manually?

@imphil Thank you so much for creating this test PR. Surely there's no need for you to configure anything. I'm going to prepare a fix for this and will update here when I figure it out.

@wsipak a quick update: https://github.com/lowRISC/ibex/pull/1435 was opened recently and has seen messages from the bot, unfortunately they aren't the right messages or in the right lines (the lines mentioned don't exceed 100 characters).

@imphil Thank you for letting me know. I've run Verible locally on the branch in the PR and it looks like the messages are reported for wrong lines (lines 163-168, 175-177, 180, 197 exceed the limit, not the ones that are reported).
I'm working on this, thanks a lot.

Thanks @wsipak! And no worries or pressure, it's not blocking anything on our side.

Hm. https://github.com/lowRISC/ibex/runs/3665088172?check_suite_focus=true shows that the the new version runs, but doesn't produce any output. Running the same command the CI shows locally shows a huge amount of lint violations. Do you have an idea what's going on @wsipak?

Close/reopen to see how the updated action copes.

The verible lint action is now in active use, no need to keep this TEST PR open any longer.


Not working for Ruby 3.0.0.

Following is a screenshot, thank you.

Should be fixed in 0.30.0. Sorry for taking so long to respond and feel free to reopen the issue if the problem persists.

it works, thank you!


Use version_pk to trigger builds

Currently we are using a mix of project_pk and version_pk.
But we only need a version_pk, the project
can be obtained from the version.
The default version is set at https://github.com/stsewd/readthedocs.org/blob/90211a2828dd874d4209caa4204eec806fdbc431/readthedocs/core/utils/init.py#L93-L95

And I just checked the .com site, no changes are needed there.

@stsewd Also, if you haven't already, i believe this could require changes in readthedocsinc

I check, no changes are needed, we call the top-level function only


Create Spring.NET DI Integration

[ ]  Implement Spring.TypeRegistrar.
[ ]  Implement Spring.TypeResolver.
[ ]  Unit tests for classes.
[ ]  Implement CommandAppBuilder extension method for Spring.
[ ]  Extension method unit tests.
[ ]  Sample project for Spring integration.
[ ]  Update docs: readme, release notes.
[ ]  Release.

This integration was cut as Spring.NET no longer looks like a viable option.


Allow files with explicit .js suffix to be importet as .ts, if found

In a small web project, I prefer not to use a package tool but only compile Typescript into Javascript. To not confuse web servers with requests for non-suffixed files, I use the explicit .js suffix in imports which the Typescript compiler happily maps to the respective .ts. file for import
I patched ts_dependency_graph accordingly and provide the patch attached. Let me know if you prefer a merge request, but since it is such a small change, the whole procedure with forking and so on seems overkill. (Sorry for the silly .txt suffix of the patch, .patch can't be uploaded :-)
allow_js_suffix_imports.txt
Thanks for the nice tool btw.

Thanks for the diff, I applied it and pushed it to master.  I will soon release it. Sorry for the late response


Update CI and README

Pull request
Please confirm that this pull request has done the following:

[ ] Tests added
[ ] Documentation added (where applicable)
[ ] Example added (either to an existing notebook or as a new notebook, where applicable)
[ ] Description in CHANGELOG.rst added

Adding to CHANGELOG.rst
Please add a single line in the changelog notes similar to one of the following:
- (`#XX <http://link-to-pr.com>`_) Added feature which does something
- (`#XX <http://link-to-pr.com>`_) Fixed bug identified in (`#XX <http://link-to-issue.com>`_)

@rgieseke my attempt to get CI going again. Now appears to be a single notebook failing on windows. Thoughts?

What do the skips for 3.7 on Windows mean?
-- Docs: https://docs.pytest.org/en/latest/warnings.html
=========================== short test summary info ===========================
SKIPPED [13] c:\hostedtoolcache\windows\python\3.7.6\x64\lib\site-packages\nbval\plugin.py:556: <Skipped instance>
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! KeyboardInterrupt !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
zmq\backend\cython\checkrc.pxd:13: KeyboardInterrupt
(to show a full traceback on KeyboardInterrupt use --fulltrace)
============= 79 passed, 13 skipped, 1 warnings in 111.98 seconds =============
##[error]The operation was canceled.

Otherwise, don't test the notebooks on Windows at all :man_shrugging: ?

What do the skips for 3.7 on Windows mean?

For the io tests, some of the files are checked to make sure what is written is identical to what we expect. That doesn't work on windows because I wrote the files on linux so all the line endings are different, hence we skip those tests. For the notebooks, we can't test the widget or MAGICC7 notebook so they're just skipped instead (that happens on all os).
Makes sense?

Here it says, the Windows tests were "cancelled":
https://github.com/openscm/pymagicc/pull/293/checks?check_run_id=632562969

Here it says, the Windows tests were "cancelled"

yep so this one failed (https://github.com/openscm/pymagicc/pull/293/checks?check_run_id=632563006) and hence all the others are immediately cancelled

Is the 3.8 image somehow different from the others? Some problem with magicc6.exe being an 32 bit binary?

Is the 3.8 image somehow different from the others? Some problem with magicc6.exe being an 32 bit binary?

I'm not sure, was going to try and find out tomorrow with @lewisjared and his windows machine

Since the others are cancelled, it's probably the same for all Windows runs. In principle Windows has 32bit support by default: https://www.techsupportalert.com/content/how-windows7-vista64-support-32bit-applications.htm

Since the others are cancelled, it's probably the same for all Windows runs. In principle Windows has 32bit support by default: https://www.techsupportalert.com/content/how-windows7-vista64-support-32bit-applications.htm

And the other tests run fine ... so it must somehow be the call from the notebook. Security thing?

And the other tests run fine ... so it must somehow be the call from the notebook. Security thing?

Could be, could also be that running with zeros is exploding for a reason I haven't fully thought through...

Ah, right -- most of the tests are passing!

yep it's good! any other thoughts?

Now a different error, and on Ubuntu:

from functools import lru_cache

plt.style.use("ggplot")

Traceback:
Unexpected output fields from running code: {'stderr'}

=============================== warnings summary ===============================
notebooks/Building-Scenarios.ipynb::Cell 0
  /opt/hostedtoolcache/Python/3.7.6/x64/lib/python3.7/site-packages/jupyter_client/manager.py:63: DeprecationWarning: KernelManager._kernel_spec_manager_changed is deprecated in traitlets 4.1: use @observe and @unobserve instead.
    def _kernel_spec_manager_changed(self):

-- Docs: https://docs.pytest.org/en/latest/warnings.html
=========================== short test summary info ============================
SKIPPED [13] /opt/hostedtoolcache/Python/3.7.6/x64/lib/python3.7/site-packages/nbval/plugin.py:556: <Skipped instance>
FAILED notebooks/Demo.ipynb::Cell 0
======== 1 failed, 109 passed, 13 skipped, 1 warnings in 182.57 seconds ========
##[error]Process completed with exit code 1.
``

That’s good (kind of), I’d ignore output of that cell given its just
imports...
On Thu, 30 Apr 2020 at 9:10 pm, Robert Gieseke<EMAIL_ADDRESS>wrote:

Now a different error, and on Ubuntu:
from functools import lru_cache
plt.style.use("ggplot")
Traceback:
Unexpected output fields from running code: {'stderr'}
=============================== warnings summary ===============================
notebooks/Building-Scenarios.ipynb::Cell 0
/opt/hostedtoolcache/Python/3.7.6/x64/lib/python3.7/site-packages/jupyter_client/manager.py:63: DeprecationWarning: KernelManager._kernel_spec_manager_changed is deprecated in traitlets 4.1: use @observe and @unobserve instead.
def _kernel_spec_manager_changed(self):
-- Docs: https://docs.pytest.org/en/latest/warnings.html
=========================== short test summary info ============================
SKIPPED [13] /opt/hostedtoolcache/Python/3.7.6/x64/lib/python3.7/site-packages/nbval/plugin.py:556:
FAILED notebooks/Demo.ipynb::Cell 0
======== 1 failed, 109 passed, 13 skipped, 1 warnings in 182.57 seconds ========
##[error]Process completed with exit code 1.
``
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/openscm/pymagicc/pull/293#issuecomment-621767152, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AFUH5G53TAM2PA7YCZMTMK3RPFMCDANCNFSM4MTKUCFA
.

I'm wondering, what is the benefit of doing the test-pypi install -- it's different in some ways, as dependencies have to be installed manually. What changes would it catch and if one were working with setup.py wouldn't one run them manually during local development?

What changes would it catch and if one were working with setup.py wouldn't one run them manually during local development?

Not many, I'm not sure it's worth having either. I guess it's just a sanity check that your uploaded package will somewhat work. However maybe it's better to have simply for local development instead and we remove from the pipeline?

ping @rgieseke

The Demo.ipynb shouldn't be tested, right?

The Demo.ipynb shouldn't be tested, right?

May as well make sure it runs

but the ping was about this comment https://github.com/openscm/pymagicc/pull/293#issuecomment-623409909

Not many, I'm not sure it's worth having either. I guess it's just a sanity check that your uploaded package will somewhat work. However maybe it's better to have simply for local development instead and we remove from the pipeline?

Ye, i'd be for removing! The finicky requirements of installing dependencies makes this something to have local only, i think!

Beauty over to you to merge!

Except ... the notebook broke again :-/

Except ... the notebook broke again :-/

lol damn it ok will fix tomorrow

Hm, works locally for me :man_shrugging:

Hm, works locally for me

scmdata 0.5.0, oops

:rocket:


Allow the passing of props and bumped dependency versions

Why
props
Originally had to pass data object and call it via this.props.data.myProp which seems unnecessary.
dependencies
If you had a recent version of react-native, you would get errors when running npm start
Unable to resolve module ./base64-vlq from /Users/mikaelcarpenter/gears-native/node_modules/react-native-router/node_modules/react-native/Libraries/JavaScriptAppEngine/Initialization/SourceMap.js

{so on and so on}

What
props
Instead of passing data in your route, you can now pass passProps which takes in an object, and then creates a prop for each key: value pair in the object.
dependencies
Updated the version numbers in package.json dependencies.
This is also an update to a previous PR (#47) by wenkesj
Issue
Props #39
Dependencies #53
Example
_initialRoute = {
    name: 'Title'
    component: Home
    passProps: {
        prop1: 'hi'
        prop2: 'bye'
    }
}

App = React.createClass({
    render: function() {
        return (
            <Router firstRoute={_initialRoute} />
        )
    }
})

module.exports = App

Your Home component can now use this.props.prop1 and this.props.prop2

@t4t5 :D
also for anyone wanting to make these changes manually to their project. After updating the dependencies: cd node_modules/react-native-router and npm update to apply the changes

@jhabdas I haven't checked it out yet, but would you want to use it for the nav bar transitions rather than the opacity from tween-state?


Multi select component

Looks like there are some template lint errors:
20:49:16 > ember-template-lint .
20:49:16
20:49:17 addon/components/denali-multi-select.hbs
20:49:17   1:0  error  template cannot end with newline  eol-last
20:49:17
20:49:17 tests/dummy/app/templates/denali-multi-select.hbs
20:49:17   1:0  error  template cannot end with newline  eol-last
20:49:17

@ldkge updated the repo with the latest ember and fixed the failing ember-canary test. Can you please rebase?

Closing for now due to multi-select redesign


Gtabedit command in fugitive breaks lsp #31

Not entirely sure what's happening here. But this fixes the issue.

c2e8d7e is the real fix. No need to be defensive in this part here.


Release Compiled Binaries With Each Release

It would be wonderful if you could release compiled binaries along with your version tags at https://github.com/derekparker/delve/releases.
There are multiple editor packages that make use of Delve, and there is a desire to automatically install a binary in a user's $GOPATH/bin or somewhere else on their $PATH to obviate the need for the user to build from source (which has varying degrees of complexity depending on the platform).
In essence, we would like to provide a "it just works" getting started experience for users on some subset of platforms.
Jetbrains currently maintains this: https://bintray.com/jetbrains/golang/delve/view , which provides a short term fix.
It would be ideal if the binaries were produced by the CI associated with this repo itself and were released as part of your normal process for cutting releases.
This entire issue is predicated on the assumption that there are no immediate plans to make delve go gettable on all of: OS X / Windows / Linux (acknowledging it is go gettable on Linux currently).
/cc @dlsniper @lloiser
Please answer the following before submitting your issue:
Note: Please include any substantial examples (debug session output,
stacktraces, etc) as linked gists.
1. What version of Delve are you using (dlv version)?
2. What version of Go are you using? (go version)?
3. What operating system and processor architecture are you using?
4. What did you do?
5. What did you expect to see?
6. What did you see instead?

@joefitzgerald I completely agree. I hope to have this in place before cutting the next release. This will be one of a few improvements to the release process that I have planned.

@derekparker Wonderful news - thank you! Any idea on timeframe for the next release (don't want to hold you to anything, just want to determine if we should write code to download from https://bintray.com/jetbrains/golang/delve/view in the interim).

@joefitzgerald the plan is to cut a release this week, but no hard time frame at the moment. However, following this release we will start cutting releases at a specified cadence. I will keep this thread updated on progress.

@derekparker Out of curiosity - is your plan to publish signed binaries for OS/X?

@lukehoban that would be ideal, however I haven't looked into it and am unsure of what all would be involved. Definitely something I will look into before next release is cut.

I'll ping @ignatov for this to track as well.

Just wanted to update folks who are following this thread: was not able to get everything in for a release last week, so I'm aiming for cutting a release today or tomorrow. The plan is to include pre-compiled binaries along with that release.

@derekparker thanks for the update! Had a chance to investigate signing the OS X binary?

BTW, we're at JetBrains use our developer certificate for signing Delve Mac OS binaries.

@joefitzgerald @ignatov yeah I think the only solution is to cough up $99 to enroll in their developer program and get a developer cert I can sign the binaries with.

@derekparker got anywhere we can send you some cash?

@joefitzgerald thanks for asking. Not currently, but that would be very helpful. I will look into getting something set up, and post some information regarding explicitly what the funds are used for.

This entire issue is predicated on the assumption that there are no immediate plans to make delve go gettable on all of: OS X / Windows / Linux (acknowledging it is go gettable on Linux currently).

go get works for me fine on Windows.
C:\>go get github.com/derekparker/delve/cmd/dlv

C:\>%GOPATH%\bin\dlv
Delve is a source level debugger for Go programs.

Delve enables you to interact with your program by controlling the execution of the process,
evaluating variables, and providing information of thread / goroutine state, CPU register state and more.

The goal of this tool is to provide a simple yet powerful interface for debugging Go programs.

Usage:
  dlv [command]

Available Commands:
  version     Prints version.
  run         Deprecated command. Use 'debug' instead.
  debug       Compile and begin debugging program.
  exec        Runs precompiled binary, attaches and begins debug session.
  trace       Compile and begin tracing program.
  test        Compile test binary and begin debugging program.
  attach      Attach to running process and begin debugging.
  connect     Connect to a headless debug server.

Flags:
      --accept-multiclient[=false]: Allows a headless server to accept multiple client connections. Note that the server API is not reentrant and clients will have to coordinate
      --api-version=1: Selects API version when headless
      --build-flags="-ldflags=-linkmode internal": Build flags, to be passed to the compiler.
      --headless[=false]: Run debug server only, in headless mode.
  -h, --help[=false]: help for dlv
      --init="": Init file, executed by the terminal client.
  -l, --listen="localhost:0": Debugging server listen address.
      --log[=false]: Enable debugging server logging.

Use "dlv [command] --help" for more information about a command.

C:\>

Alex

Another update on this thread:
It's looking like I will not be cutting a new release this week. However, on the bright side, it's because I'm working on some major changes, including a pretty significant refactor, and I'm hopeful that the next release will essentially be either 1.0.0.rc1 or very close to that. The plan is for the next release to include the new API changes @aarzilli has been working on, as well as a bunch of code cleanup, stability improvements (especially on OSX), and build artifacts attached to the release.
The plan is to finish up all of the more intense refactoring I'm doing over the weekend, and (fingers crossed) have a release out by middle/late next week. Thanks for everyone's patience on this, but the next release will be a pretty big one.

If you'll need help with testing the changes, feel free to ping me. Thank you for your work!

Anything we can do to unblock things @derekparker?

@joefitzgerald nothing in particular, unfortunately. The next release is blocked on an ambitious refactor I'm playing on top of some OSX fixes, and it's just a matter of me getting it over the finish line. I'm nearly there, and the next release should be out within the next few days.

@derekparker, just curious if this coming release will include 32bit support?

@joegrasse no, next release will not, but we should be set up to get that feature added within the next 2 releases. The next release will focus on all patches already merged, plus OSX stability fixes and code cleanup.

Update: making great progress on refactor. Spoke with @aarzilli and we are planning on cutting a new release this week, so stay tuned.

@derekparker is there some way to just cut a release (manually) based on the most recently released version (January) that has signed OS X binaries? I totally understand the desire to cut one based on the latest bits, but it feels like a moving target that may still be weeks or months away?

@joefitzgerald sorry for the late response, I have been swamped lately. With the homebrew installation method we have now, which will self-sign the binary upon installation, is there still a lot of benefit for shipping signed binaries? For example, would it still be too much to ask to have a user run brew install go-delve/delve/delve?
Just putting that out there, not ruling out shipping signed binaries.

@derekparker no I don't think homebrew will supplant the need for signed release binaries as many OSX users (rightly or wrongly) don't use homebrew.
And I totally understand - you don't have to apologize. I also do this on the side, and am making no demands :)

Maybe using the BinTray repo JetBrains has is an option? But ask them first as I don't speak for them :)

That's already happening, but the releases belong here.

@derekparker any updates on releasing binaries in Github releases?

I truly recommend goreleaser to automate the creation of binaries and  godownloader for automated generation of install scripts.
For inspiration on the integration you can look into the awesome golangci-lint
Also, Thank you for developing delve!!

@joefitzgerald could you describe why this issue is closed? why delve can't be distributed as precompiled binary?

@Slach 5 years on, this issue seems stale. I don’t see it being prioritized, so I closed it as the original requester. I’m fine if the delve maintainers want to reopen the issue.


Analytics are being sent to a third party

We were debugging issues with our pipeline and noticed decK was sending analytics to a third party domain, is it possible to disable this by default or send them over to a Kong owned domain?
https://github.com/Kong/deck/blob/main/cmd/analytics.go#L30

We have to move this to a Kong owned demo but hasn't been prioritized in a while.

resolved by https://github.com/Kong/deck/pull/301


[Bug]: replaceRules do not take effect on frontmatter of object structure type

Version
-

Details
https://github.com/web-infra-dev/rspress/blob/a854fc3d9f3493f416afc282298c0d0ae7bf7337/packages/core/src/node/runtimeModule/siteData/extractPageData.ts#L50-L55
We only deal with string type now and the hero frontmatter is an object.

Reproduce link

Reproduce Steps
We should deal with object type.

We should also add replaceRules options to our doc. #1048


Make it easy to dump ast-language text for queries

This will get used, in the end, for testing other parts of the system.

Opened in the wrong repo


AUR Package

Good evening, I made a package for this program on the Arch User Repository, thought you might want to add it to the README as an alternate installation method for users of Arch Linux:
https://aur.archlinux.org/packages/sptlrx-bin/

Awesome, thanks a lot!


Remove CruiseControl

@chessbyte Please review.  We no longer use it, so let's remove it.
Built on top of #3746

:+1: LGTM

@Fryguy Now that https://github.com/ManageIQ/manageiq/pull/3746 is merged, should this PR be rebased before merging?

@chessbyte Updated


Inconsistent indentation errors, 'NoneType' object is not iterable

When I install the plugin, beets complains about inconsistent indentation on line 56. I was able to make it stop complaining about the indentation errors by reindenting various lines, but then I got this other error when running an import:
Traceback (most recent call last):
File "/usr/local/bin/beet", line 11, in
sys.exit(main())
File "/usr/local/lib/python3.5/site-packages/beets/ui/init.py", line 1209, in main
_raw_main(args)
File "/usr/local/lib/python3.5/site-packages/beets/ui/init.py", line 1196, in _raw_main
subcommand.func(lib, suboptions, subargs)
File "/usr/local/lib/python3.5/site-packages/beets/ui/commands.py", line 930, in import_func
import_files(lib, paths, query)
File "/usr/local/lib/python3.5/site-packages/beets/ui/commands.py", line 907, in import_files
session.run()
File "/usr/local/lib/python3.5/site-packages/beets/importer.py", line 319, in run
pl.run_parallel(QUEUE_SIZE)
File "/usr/local/lib/python3.5/site-packages/beets/util/pipeline.py", line 445, in run_parallel
six.reraise(exc_info[0], exc_info[1], exc_info[2])
File "/usr/local/lib/python3.5/site-packages/six.py", line 686, in reraise
raise value
File "/usr/local/lib/python3.5/site-packages/beets/util/pipeline.py", line 312, in run
out = self.coro.send(msg)
File "/usr/local/lib/python3.5/site-packages/beets/util/pipeline.py", line 194, in coro
func(*(args + (task,)))
File "/usr/local/lib/python3.5/site-packages/beets/importer.py", line 1261, in lookup_candidates
task.lookup_candidates()
File "/usr/local/lib/python3.5/site-packages/beets/importer.py", line 589, in lookup_candidates
autotag.tag_album(self.items, search_ids=self.search_ids)
File "/usr/local/lib/python3.5/site-packages/beets/autotag/match.py", line 457, in tag_album
va_likely):
File "/usr/local/lib/python3.5/site-packages/beets/plugins.py", line 496, in decorated
for v in generator(*args, **kwargs):
File "/usr/local/lib/python3.5/site-packages/beets/autotag/hooks.py", line 596, in album_candidates
for candidate in plugins.candidates(items, artist, album, va_likely):
File "/usr/local/lib/python3.5/site-packages/beets/plugins.py", line 355, in candidates
for candidate in plugin.candidates(items, artist, album, va_likely):
TypeError: 'NoneType' object is not iterable

Ah the tabs thing is embarrassing, not sure how I missed those. I just pushed a fix for that. I kinda just threw this plugin together in about a day so try not to expect too much of it. I was able to use it for about 300 album imports without issue though so I don't exactly think its that bad.
As for your traceback, I'm not super sure whats wrong since it's not really tracing back to my plugin (though it could be related) and I cannot reproduce this. Also are you running this with Python 3.5 or is that some kind of compatibility thing? Beets does not yet support Python 3.0 and above so I can't help but ask.
This is my beets --version output if it helps at all:
beets version 1.4.0
python version 2.7.12
plugins: discogs, duplicates, edit, embedart, fetchart, fromfilename, fuzzy, importadded, info, inline, lastgenre, mbsync, missing, replaygain, vgmdb

No worries, I figured this was WIP. It's possible I messed something up
when I was fixing your indentation. Let me try again tonight. Thanks for
the quick response!
On Tue, Jan 31, 2017, 11:14 AM Ethan Larkham<EMAIL_ADDRESS>wrote:

Ah the tabs thing is embarrassing, not sure how I missed those. I just
pushed a fix for that. I kinda just threw this plugin together in about a
day so try not to expect too much of it. I was able to use it for about 300
album imports without issue though so I don't exactly think its that bad
.
As for your traceback, I'm not super sure whats wrong since it's not
really tracing back to my plugin (though it could be related) and I cannot
reproduce this. Also are you running this with Python 3.5 or is that some
kind of compatibility thing? Beets does not yet support Python 3.0 and
above so I can't help but ask.
This is my beets --version output if it helps at all:
beets version 1.4.0
python version 2.7.12
plugins: discogs, duplicates, edit, embedart, fetchart, fromfilename,
fuzzy, importadded, info, inline, lastgenre, mbsync, missing, replaygain,
vgmdb
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/elarkham/VGMdb-BeetsPlug/issues/1#issuecomment-276461558,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFhG2IhBOThJ_S7QrFZ70utcZN3VP0xXks5rX4gJgaJpZM4LyWZl
.

Hmm ok so I don't get that error anymore, but I'm not seeing any vgmdb results show up when I try to import releases that I know exist there (using the exact album name). Would the python version really be a problem? I am on python 3.5.2 but I thought that was ok since the beets install instructions say "You will need Python. Beets works on Python 2.7 and Python 3.4 or later."

Huh, didn't know it worked with Python 3.4+ until now, this blog post made me think otherwise but I see now that it's actually 5 years old... This wiki post shows they are working on actually getting a full port done, figures they made this only 8 days after I made the dang thing. Would have written it in Python 3 had I known.
That being said, I'm not 100% sure this is even related to Python 3, but if it is then you can fix it by running beets with Python 2 instead of Python 3.
What OS/Distro are you using?

Well I just went through the long, confusing and tiring process of installing and configuring pyenv, then getting beets on 2.7.13 and your plugin now works. So apparently it is incompatible with 3.5. I might take a stab at figuring out what API updates are necessary but for now it works. Closing this issue, but you might want to note the compatibility issue in the readme. Thanks for your help!


no thumbs on Android device

Hi @Sharcoux,
I experimented some more and found that, if I pick trackHeight > thumbSize, the circular shape of the thumb becomes clearly visible. It seems like some zIndex problem: the thumb is not an overlay with respect to the track.
The performance issue I was talking about here, was caused by the thumb and track touchable area not being large enough, I guess. Maybe, you could add some padding which is touchable?
Thanks for the great work

@avlonder Thanks for the feedback!
Can you provide me the exact parameters you are using so that I can replicate the issues? I should be able to provide a solution quickly.

@avlonder Thanks for the feedback!
Can you provide me the exact parameters you are using so that I can replicate the issues? I should be able to provide a solution quickly.

I upgraded to 5.0.3 and for some reason it works exactly as expected. Now, I can just increase the thumbs without having to increase the track, such that both problems are resolved at once. Sorry for the inconvenience. Earlier, I must have installed an older version or something. I cannot replicate the original problem stated above. So, I'm closing the issue.

I upgraded to 5.0.3 and for some reason it works exactly as expected. Now, I can just increase the thumbs without having to increase the track, such that both problems are resolved at once. Sorry for the inconvenience. Earlier, I must have installed an older version or something. I cannot replicate the original problem stated above. So, I'm closing the issue.


Ability to pass chromedriver path to BrowserStartMode.ChromeWith...

Hi,
I was wondering if such an overload makes sense. I would rather not put my chromedriver.exe to C:\ but a more manageable location. The silly thing is that the path is not part of the options but the ChromeDriver constructor *
Would you like this posiiblity, too?
If nobody has time I can also see if I get that in myself - then my hope would be that it lands on NuGet soon, but let?s see how it goes.
*)Why you would make an arguments object and then leave an argument out is beyond me. :-1:

I just found this place in the source and I am wondering where chromeDir comes from?

https://github.com/lefthandedgoat/canopy/blob/master/src/canopy/configuration.fs#L9
You can change the dirt by doing
canopy.configuration.chromeDir <- @"c:\path\to\chrome"

Ah, was really wondering where chromeDir comes from, it's a member of an imported module. My f#reading skills are still lacking. Thanks!


[do-not-merge] Bump collector version to tag using the C++17 compiled binary

Description
This is a test PR, meant to just run the tests on the image created by stackrox/collector#1038
Checklist

[ ] Investigated and inspected CI test results
[ ] Unit test and regression tests added
[ ] Evaluated and added CHANGELOG entry if required
[ ] Determined and documented upgrade steps
[ ] Documented user facing changes (create PR based on openshift/openshift-docs and merge into rhacs-docs)

If any of these don't apply, please comment below.
Testing Performed
TODO(replace-me)
Use this space to explain how you tested your PR, or, if you didn't test it, why
you did not do so. Valid reasons include, for example, "CI is sufficient",
"No testable changes". Feel free to attach JSON snippets, curl commands,
screenshots.
In addition to reviewing your code, reviewers must also review your testing
instructions and make sure they are sufficient.

/test all
/test gke-kernel-qa-e2e-tests
/test openshift-newest-qa-e2e-tests
/test openshift-oldest-qa-e2e-tests

/test all
/test gke-kernel-qa-e2e-tests
/test openshift-newest-qa-e2e-tests
/test openshift-oldest-qa-e2e-tests


Support hoisting react-scripts and add require.resolve() to loaders

Our resolveLoader config is the only thing I found causing https://github.com/facebookincubator/create-react-app/issues/556 to fail.
We probably already fixed the other issues.
I don't think we need it anyway because it was mostly necessary for npm 2 which we’re dropping.
As a followup I decided to add require.resolve() to all loaders and configs.  Webpacks resolves them relatively to the source, but I don’t think this is what makes sense in most cases.
I hope this doesn’t break some obscure linking scenario. In fact I think it might fix some of the more obscure ones. But I’m not 100% sure.

Looks like it passes CI. Good luck to me.

LGTM. IMO this is better.


Cannot generate masks by using SamAutomaticMaskGenerator

Hi!
I'm using the code from automatic_mask_generator_example.ipynb to process my own image, but I cannot get any masks by using SamAutomaticMaskGenerator. However, when I use the code from predictor_example.ipynb, it works well. Do you have any idea about why is that? and how can I revise my code to generate masks automatically? Following are my code, hope that will be clear enough.
"
import modules part. Same as example code.
import ...
def show_ functions. Same as example code.
def show_anns(anns):
def show_mask(mask, ax, random_color=False):
def show_points(coords, labels, ax, marker_size=375):
def show_box(box, ax):
load model and finetuned checkpoint
args = Namespace()
device = torch.device("cuda" if torch.cuda.is_available() else "cpu")
args.image_size = 256
args.encoder_adapter = True
args.sam_checkpoint = "/workdir/models/epoch30_sam.pth"
sam = sam_model_registry"vit_b".to(device)
load image. Successfully loaded
image = cv2.imread('/home/zhangzhibo/SAM/SAM_demo_result.png')
image = cv2.cvtColor(image, cv2.COLOR_BGR2RGB)
plt.figure(figsize=(20,20))
plt.imshow(image)
plt.axis('off')
plt.show()
Generate masks
mask_generator = SamAutomaticMaskGenerator(sam)
masks = mask_generator.generate(image)
print(len(masks))
print(masks[0].keys())
plt.figure(figsize=(10,10))
plt.imshow(image)
show_anns(masks)
plt.axis('on')
plt.show()
"
The outputs are: len(masks) = 0, and show_anns(masks) actually add no masks on the image. I tried define mask_generator as this:
"mask_generator = SamAutomaticMaskGenerator(
model=sam,
points_per_side=32,
pred_iou_thresh=0.85,
stability_score_thresh=0.9,
)"
and that make no difference.
Would you mind to help me and check about this code? Looking forward to your reply, Thanks!

It seems like I should set the pred_iou_thresh and stability_score_thresh smaller...

I meet the same question when running the demo “automatic_mask_generator_example.ipynb“  given by official. Have you fixed it?

@Lylain @mura94 I don't certainly know the reason, but it seems like when you set a smaller value to these 2 parameters "pred_iou_thresh" and "stability_score_thresh"(within the function of SamAutomaticMaskGenerator, their default value is 0.85 and 0.9, respectively) the model could generate some masks. These 2 parameters seem defined how strict the model should be when it judges whether a region should be treated as a mask or not. So smaller value means looser standard, and then you can get more masks.

I meet the same question by the func "SamAutomaticMaskGenerator" with "device:cuda".
But, when the "device" changed from 'cuda' to 'cpu', the masks‘s length is not zero, it works well !!!
I do not know the reason, but i am sure it's not caused by parameters "pred_iou_thresh" and "stability_score_thresh".


Scaling-up SwarmMode cluster - nodes won't show up on master server

I created small cluster using acs-engine in SwarmMode. Everything gets created correctly and I can see all initial agent nodes by running docker node ls on master node.
Then I scaled virtual-machine-scale-set instances up. No errors too.
How are the new node added to the swarm? I cannot see them on master nodes list.

@srigi , can you share the following logs from the node that does not show up when you list:

/var/log/azure/cluster-bootstrap-postinstall.log
/var/log/azure/cluster-bootstrap.log

Also, does Portal show that the new VMSS instance was provisioned successfully?

Hello @amanohar, thanks for reply.
I must apologize, nodes indeed showed up, I just have to wait little longer. I cannot express how awesome this is, I was thinking that after scaling virtual-machine-scale-set there is some provisioning work to do from my side. But this automation of including new nodes into the swarm is great.
Once again sorry for false warning.

Remove bug label, and close it, as it is false alarm.


Support colons in MultiSelect option values

Problem:
The previous implementation of MultiSelect component's option splitting logic did not allow colons (:) in the values. For an option like "foo:bar:baz", the label would be "foo" and the value would incorrectly be set as "bar" instead of "bar:baz".
Solution:
This PR modifies the option splitting logic to treat everything after the first colon as the value. Now, for an option like "foo:bar:baz", the label is "foo" and the value is "bar:baz".
Changes:

Updated the option splitting logic in the MultiSelect component.
Added comments to clarify the behavior for future developers.

@Zaydme could you review this PR? thanks

Thank you @yuku !


fix: show transaction amount above Increase Fee, closes #5826

Building Leather at commit ea0c379

This PR makes a change so we always show the transaction amount above Increase fee as per

I'm awaiting feedback on the visuals of this https://github.com/leather-io/extension/issues/5826#issuecomment-2326016958

I've assigned @fabric-8 and @mica000 so one of them can sign off on this from a design perspective.

I've assigned @fabric-8 and @mica000 so one of them can sign off on this from a design perspective.
FWIW this looks good to me, and I expect we'll improve this further as we redesign activity UX in general soon for mobile.
It may be worth double checking how it looks in the action popup as well.

Here it is in the action popup for reference:

Thanks for working on this! Any chance we could align the vertical spacing so the text baseline aligns between left & right side?

Yeah something definitely off here. Pressable was designed with pseudo elements so hover goes outside bounds and it'll be default align.

Yeah something definitely off here. Pressable was implemented with pseudo elements so hover goes outside bounds and it'll be aligned by default.

I was just not using it properly and not putting the button into captionRight 🤦

Thanks for working on this! Any chance we could align the vertical spacing so the text baseline aligns between left & right side? You see the figma mock here

Thanks @fabric-8 . I've updated it now.
In those designs we don't have a placeholder for the label text e.g. Pending / Today etc. Those are positioned using a top margin now but if  you want to add them in the design I can make it more precise 📏

@fabric-8 @kyranjamie : I adjusted the styling here so it's looking better. Let me know if I need to adjust it further
https://github.com/user-attachments/assets/b8741f7f-39f9-4f2f-a637-c3ea6f8838d1

Can see the Pending header has smaller margin than the Today & Yesterday ones. These should match.

Other than padding fix needed, code LGTM

Other than padding fix needed, code LGTM

Thanks. I fixed the padding here


Performance Update & Tests

Object Key/Value was found to be more efficient than string indexing, especially at scale.
Tests written thanks to @elenatorro
'read' and 'convert' no longer exposed as they are internal functions
Other minor performance efficiencies

Read here: https://github.com/Nonemoticoner/braille/issues/4#issuecomment-418553117


Add redshift specific coefficient return function

Redshift doesn't include the same functionality with the numeric data type as postgres; returning unintended integers. This specific adapter for redshift allows continuous variables to be returned.

LGTM. Thank you for your contribution! I'll release it in a few minutes.


GROUP BY backports

Fixes #6180.

This change is

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/c7c975f586dc83aa3c9ecb8ff2a45c32945ff653/
Edited pages:

v19.2/known-limitations.md
v19.2/select-clause.md


"File not cached" - Unable to identify reason for this issue

The cache directory /srv/REDACTED/www/wp-content/cache/ is writeable. However, the wp-rocket directory is never created.
Reading through previous issues I saw someone resolved their issue by placing the rocket-nginx include inside the php block, this did not make a difference for me.
I am using Cloudflare, however I have set it to Maintenance Mode.
I do not have a .maintenance file.
I am not logged in, tried different browsers as well as online http header checkers.
Checked as a mobile and desktop user.
Unable to figure this one out.
cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
content-encoding: br
content-type: text/html; charset=UTF-8
date: Mon, 09 Apr 2018 09:38:48 GMT
expires: Thu, 19 Nov 1981 08:52:00 GMT
link: <https://wp.me/P6CQF5-rh>; rel=shortlink
link: <https://REDACTED.pl/wp-json/>; rel="https://api.w.org/"
pragma: no-cache
server: nginx
status: 200
vary: Accept-Encoding
x-rocket-nginx-file: /srv/REDACTED.pl/www/wp-content/cache/wp-rocket/REDACTED.pl///index-https.html
x-rocket-nginx-reason: File not cached
x-rocket-nginx-serving-static: No
x-ua-compatible: IE=edge

nginx.conf: https://hastebin.com/vowasakeze.nginx
default.conf: https://hastebin.com/ucilirizag.nginx

Rocket-Nginx does not create any file or directory.  If nothing is created, it is because of a problem with WP-Rocket or your web hosting configuration. I suggest you contact WP-Rocket for that.


'Process scraped data with Python' has two titles

The page Process scraped data with Python has two titles rendered, but the source has just one. How to fix this? Summoning @TC-MO for help.

Seems this is due to the comment being the first thing below front matter, once comment is removed only H1 renders


Manage tendril repo with Homu

@bors-servo: r+

:pushpin: Commit 457e7a5 has been approved by larsbergstrom

:hourglass: Testing commit 457e7a5 with merge 92d82fe...

:sunny: Test successful - travis


Update version from 0.0.154 to 0.0.155

This is an automated version-update on pyproject.toml.
The workflow was triggered by a succesfull pull request from branch:
With push event SHA of: 676738b12b2ffd9dad62548619d5c723a231781c
This action is performed by the Github Action: publish.yml after every accepted pull request. When finished,
this will have published the latest patch of the Extractable codebase to Pypi so it can be pip installed.
DO NOT DO ANYTHING WITH THIS PULL REQUEST
This pull request should resolve itself within 1 minute.
If its older than 5 minutes and still not resolved you may check the github workflow actions to see where it went wrong.
And in that case it is safe to delete this pull request

updated version in pyproject.toml from 0.0.154 to 0.0.155


text to cad not opening model on accept

i thought there was a test for this???
https://github.com/user-attachments/assets/b4e43c26-7c34-4bd3-befb-fc9cc5bbe9a0

from @Irev-Dev "I think maybe the generated code has a error in it, I can replicate it not responding to clicks with the following code"
but i still think if this does happen even tho the model shouldnt give us erroredd code we should still open the file... def still a bug

so perhaps the bug is files don't open if code has bugs which i also thought we had a test for...?

greg is also going to start intentionally giving us the failed kcl versus good kcl if its that or nothing, so like copilot you can fix it yourself, so like we def need to support this

https://github.com/user-attachments/assets/b450910b-6e8c-4862-a896-9fc100baa287
i.e. how this got through with our tests.

oh gotcha that makes sense

Nice, thank you for your debugging @Irev-Dev, I'm able to easily reproduce that issue with a minimal example here: gh-3803.zip

Working on the text-to-cad issues currently, so unassigning myself for now

Fixed some time but I'm not sure which PR did it. I just tried it and the scene clears as expected.


Set Health and Fill Energy doesn't work and Unlock Items shows inactivity dialog

It shows an error when applying fill energy and set health on js console
The Unlock Items work but after a while it will show error 418 forcing you to sign out
I thought it was going to fill my energy and health
Windows 10
Chrome 102

You can’t fix error 418.


Added better de-duplication routines for both voter email addresses and voter sms phone numbers.

Added better de-duplication routines for both voter email addresses and voter sms phone numbers.

👍


Give EBS endpoint precedence over region

If a user has configured an endpoint to use for AWS, always use it,
rather than deferring to an auto-generated endpoint based on the region.

@akutz would like you to review this one. This makes it so that if a user sets ebs.endpoint, that endpoint is actually used, always. Previously, even if it was set, it would be ignored if there was a region set, or if there was a region in the context, which for REX-Ray is pretty much always true since it is part of the IID metadata.
I contend that if a user sets the endpoint, we should use that endpoint no matter way.

This should fix #1118 (really really this time)

Codecov Report

Merging #1134 into master will decrease coverage by 0.46%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           master   #1134      +/-   ##
=========================================
- Coverage   34.67%   34.2%   -0.47%
=========================================
  Files          36      36
  Lines        2362    2362
=========================================
- Hits          819     808      -11
- Misses       1440    1451      +11
  Partials      103     103

Impacted Files
Coverage Δ

...storage/drivers/storage/vfs/storage/vfs_storage.go
39.54% <0%> (-3.6%)
:arrow_down:

Continue to review full report at Codecov.

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