Python Tools Background Analyzer Automatically Starts Up

Whenever I start Visual Studio 2015 Community Edition, Python Tools Background Analyzer automatically starts up. Even when I am not working on a python project or the interactive window is not open. Is this a behavior I can change? Because it is a memory hog.

Sure, you'll find that option under Tools, Options, Python Tools, "Automatically generate completion DB on first use".
FWIW, it's only a temporary memory hog. Once it finishes running it saves the results and doesn't run again (unless you install new packages).

Actually, this is still an issue if you uncheck that option based on what I just saw. If you start an instance of VS2015, the CPU doesn't spike. If you start a 2nd instance, somehow it kicks off the completion DB population even if I'm not using python. This was with PTVS 2.2.5 and confirmed using the performance analyzer in VS.

Depending on the specific steps you followed, the option may not be turned off in all instances of Visual Studio. I'll see if I can reproduce it, but there's unlikely to be a fix for it in VS 2015.


FileSystemView and Timeline level changes to support Async Compaction

FileSystemView and Timeline level changes to support Async Compaction

@n3nash : Not ready for review but you can use the File Slice interface
Planning to add some unit-tests at file-group level and also complete the FileSystemView changes by tonight. This part will be reviewable around that time.

@n3nash , @vinothchandar : Updated. Please take a look.

@bvaradar left a few more comments.

@n3nash : Updated PR and also left some comments. Thanks

@bvaradar Looks okay to me.

@vinothchandar : @n3nash has reviewed this PR. Can you take a pass at this when you get a chance.

@vinothchandar : Can you take a pass. Thanks

Will do.. @n3nash can you also take a closer pass..
I went over the rest of the PRs for async compaction and this is by far the most critical..

@vinothchandar Took a pass, looks fine to me. @bvaradar left a couple of comments.

@n3nash : Replied to your comments.
This is good to be landed.

@vinothchandar We have run multiple tests with this diff and fixed some issues. I think at this point, this diff is ready to be landed. In case we hit a bug, we can tackle it on a one-off basis.

Closing this in favor of PR https://github.com/uber/hudi/pull/404


Check that there is at least one log number

Error case :
./log-download -s /dev/ttyACM0
Resulting in segfault if no log number is given. Handle the error by checking that optind is less than argc.

Merged, thanks!


add optional display_name parameter for the sns_topic resource

README.md was updated with terraform-docs 0.6.0

Thanks for the contribution! ;)


[Snyk] Upgrade org.graalvm.sdk:graal-sdk from 23.0.2 to 23.1.1

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade org.graalvm.sdk:graal-sdk from 23.0.2 to 23.1.1.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 2 versions ahead of your current version.
The recommended version was released 2 months ago, on 2023-10-19.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Snyk keeps submitting breaking changes due to sub-module API compatibility requirements with graal


Fix/revision history

full support for integer versioning, enable summary propagation, some fixes and more tests

Looking good now.
One thing I noticed: If the workflow state changes to Approved the current release date does not change. Same thing when we go back do Draft.

yes, that part was missing, I updated it


Add breadcrumbs instead of path

Should allow navigation. An icon next to them should still help by copying the full path.

Would be great to detail a bit more.
You suggest to replace the PathBar by a new component that works like breadcrumbs where each element is a folder name (except that last one that is the file name if it exists).
Clicking on such a crumb should then navigate to the respective resource in the resource tree and open the attribution column?

Yes, that is what I thought. When vetting I found it really dofficult to navigate back to the parent folder when in a folder with tens of subfolders.

In addition, we should provide an icon to copy the path then.
Further, how to handle very long paths? The solution should mirror the existing one.

In attribution wizzard we still want to keep the PathBar as it is. Also note that we already use breadcrumbs there.


Make arrays grow linear

It is very confusing for newcomers to see that normal arbitraries grow normally when handing an increased size parameter, but arrays seem not to: #205, https://github.com/cyclejs-community/create-cycle-app-flavors/issues/19#issuecomment-297482857
fixes #205
What do you think @phadej, is this reasonable?
If someone wants to have small arrays, they can use jsc.small

Ok, I see that travis runs out of memory for the JS heap. Maybe allow for specifying custom size pre-functions?

the function that is used to reduce the size. Currently the size of the array is log2(size). Instead of log the user could specify the function.

Ok, took me a while to get back to this.
This PR now allows to call the array arbitrary like this:
const myStringArray = jsc.array(jsc.string, x => x);

to allow for linear scaling of arrays

Would like to see this PR merged, scaling arrays by the log2 function is oddly constraining.


Upped the version on some packages and added extra dependencies

moved versions to properties for some dependencies
upped version to 1.0.6-SNAPSHOT
added extra dependencies

closing in favor of PR #8 which is a refactored version of this one with the comments applied


Json::matchesSchema()

Per conversation with @nikophil. Use justinrainbow/json-schema to validate schema.
I don't have any experience with json schema but is it common the include the schema files in some kind of resource directory in your project? If so, maybe a BROWSER_JSON_SCHEMA_DIR env variable could be used to set this dir, then with: $json->matchesSchema('post.json'), post.json would be loaded relative to this env variable?

Ok, probably just start with the same api as api-platform uses (pass array or json string).

Closed via #102


Adding Custom I18n setting

It would be very good if you would allow to set custom I18n text for whole dialog globaly. So that we would not need to set text in every error case each.

Hello. If you don't need to support multiple languages, you can set up a custom i18n instance globally by replacing the default ErrorWindowFactory. In order to do so, set up a VaadinServiceInitListener as follows:
@Component
public class ErrorWindowServiceInitListener
        implements VaadinServiceInitListener {

  @Override
  public void serviceInit(ServiceInitEvent event) {
    ErrorWindowI18n i18n = new ErrorWindowI18n();
    i18n.setCaption(...);
    i18n.setCaption(...);

    ErrorManager.setErrorWindowFactory(Throwable.class, details -> new ErrorWindow(details).open());
  }
}

Please let us know if that helped.

While my comment above allows customizing the texts globally, it does not allow to resolve them based on the locale of the current UI, which is a desirable feature.


Option list of ui-select does not work in ui-bootstrap modals

Bug description:
I have the problem that the dropdown with the options is not visible in a modal of the ui bootstrap directive. I tried to provide a plunker that is close to my usecase. Hope that it is not to confusing.
If i search for e.g. Berlin in the select of the modal, the options are visible. But not initialy when i click the dropdown. Outside the modal it works fine.
I am confused and found some issues that has the same problem but was closed in the past. But in my opinion it was never really a solution. Sometimes hacks and the z-index foo does not work for me.
Hope that someone can give me a hint or can confirm that it is a ui-select bug.
Link to minimally-working plunker that reproduces the issue:
https://plnkr.co/edit/7Wznx7
Version of Angular, UI-Select, and Bootstrap/Select2/Selectize CSS
Angular: 1.5.8
UI-Select:0.19.4
Bootstrap/Select2/Selectize CSS (if applicable): Bootstrap

I have run into this problem as well.  It appears mainly to deal with the ui-select when you are also using angular-animate.  I have created a plunker to demonstrate what I was able to find and a possible temporary workaround.
http://plnkr.co/edit/UaSWgr

@ironjb Great work around.
Has Little shorter version of writing instead of whole config object.
    var modalInstance = $uibModal.open({
        component: 'ModalComponent',
        appendTo: angular.element('#NgCtrlTag')
     });

@ironjb @Rakhmanov Thank you very much for such great workarounds.
Worked perfect for me :)

@ironjb Thanks for the fix. Maybe it is easier to completely remove ngAnimate if you don't use it.

I also met this problem while using ui-modal and I solve this using 'ng-class' condition to the ui-select-choices directive:
modal.html
<ui-select ng-model="person.selected" theme="bootstrap" on-select="onSelect($item)" ng-click="select_open = true">
    <ui-select-match placeholder="制作者">{{$select.selected.name}}</ui-select-match>
    <ui-select-choices repeat="item in people | propsFilter: {name: $select.search, email: $select.search}" ng-class="{ 'select_open': select_open }">

    </ui-select-choices>
    <ui-select-no-choice>
        一致するものは見つかりませんでした。
    </ui-select-no-choice>
</ui-select>

app.js
$scope.onSelect = function(item) {
    $scope.open_select = false;
	}

style.css
.select_open {
	opacity: 1 !important;
}

Hope it helps. 👍

I use css to override the opacity as a temporary fix.
.ui-select-container.open>.ui-select-choices{
opacity: 1 !important;
}


Bridge name conflict issue

This is what my Vagrantfile includes:
Vagrant.configure(2) do |config|
  config.vm.box = "centos/7"
  config.vm.network "private_network", type: "dhcp"
  config.vm.network "public_network", dev: "virbr0", mode: "bridge", type: "bridge"
  # …

With this vagrant up fails with this libvirt-vagrant error:
/home/elemoine/.vagrant.d/gems/gems/vagrant-libvirt-0.0.32/lib/vagrant-libvirt/action/prepare_nfs_settings.rb:58:in `read_machine_ip': undefined method `[]' for nil:NilClass (NoMethodError)

The full error output is provided at the end of the issue description.
If I edit my Vagrantfile and change "virbr0" to "virbr1" in the "public_network" definition, then things work as expected: vagrant up succeeds and I can vagrant ssh into the guest.
It seems to me that the problem is related to "virbr0" being used for the management network created by vagrant-libvirt, but I am not sure.
Is this problem known?
Thanks.

Full error output:
[elemoine vagrant (master u=)]$ vagrant up
Bringing machine 'operator' up with 'libvirt' provider...
==> operator: Creating image (snapshot of base box volume).
==> operator: Creating domain with the following settings...
==> operator:  -- Name:              vagrant_operator
==> operator:  -- Domain type:       kvm
==> operator:  -- Cpus:              4
==> operator:  -- Memory:            4096M
==> operator:  -- Management MAC:
==> operator:  -- Loader:
==> operator:  -- Base box:          centos/7
==> operator:  -- Storage pool:      default
==> operator:  -- Image:             /var/lib/libvirt/images/vagrant_operator.img (41G)
==> operator:  -- Volume Cache:      default
==> operator:  -- Kernel:
==> operator:  -- Initrd:
==> operator:  -- Graphics Type:     vnc
==> operator:  -- Graphics Port:     5900
==> operator:  -- Graphics IP:       <IP_ADDRESS>
==> operator:  -- Graphics Password: Not defined
==> operator:  -- Video Type:        cirrus
==> operator:  -- Video VRAM:        9216
==> operator:  -- Keymap:            en-us
==> operator:  -- INPUT:             type=mouse, bus=ps2
==> operator:  -- Command line :
==> operator: Creating shared folders metadata...
==> operator: Starting domain.
==> operator: Waiting for domain to get an IP address...
==> operator: Waiting for SSH to become available...
    operator:
    operator: Vagrant insecure key detected. Vagrant will automatically replace
    operator: this with a newly generated keypair for better security.
    operator:
    operator: Inserting generated public key within guest...
    operator: Removing insecure key from the guest if its present...
    operator: Key inserted! Disconnecting and reconnecting using new SSH key...
==> operator: Setting hostname...
==> operator: Configuring and enabling network interfaces...
==> operator: Removing domain...
==> operator: Running cleanup tasks for 'shell' provisioner...
==> operator: Running cleanup tasks for 'shell' provisioner...
/home/elemoine/.vagrant.d/gems/gems/vagrant-libvirt-0.0.32/lib/vagrant-libvirt/action/prepare_nfs_settings.rb:58:in `read_machine_ip': undefined method `[]' for nil:NilClass (NoMethodError)
	from /home/elemoine/.vagrant.d/gems/gems/vagrant-libvirt-0.0.32/lib/vagrant-libvirt/action/prepare_nfs_settings.rb:22:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.7.0/lib/vagrant/action/warden.rb:34:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.7.0/lib/vagrant/action/builtin/synced_folders.rb:84:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.7.0/lib/vagrant/action/warden.rb:34:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.7.0/lib/vagrant/action/builtin/synced_folder_cleanup.rb:28:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.7.0/lib/vagrant/action/warden.rb:34:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.7.0/plugins/synced_folders/nfs/action_cleanup.rb:25:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.7.0/lib/vagrant/action/warden.rb:34:in `call'
	from /home/elemoine/.vagrant.d/gems/gems/vagrant-libvirt-0.0.32/lib/vagrant-libvirt/action/prepare_nfs_valid_ids.rb:12:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.7.0/lib/vagrant/action/warden.rb:34:in `call'
	from /home/elemoine/.vagrant.d/gems/gems/vagrant-hostmanager-1.6.1/lib/vagrant-hostmanager/action/update_all.rb:27:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.7.0/lib/vagrant/action/warden.rb:34:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.7.0/lib/vagrant/action/builtin/config_validate.rb:25:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.7.0/lib/vagrant/action/warden.rb:34:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.7.0/lib/vagrant/action/builtin/provision.rb:80:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.7.0/lib/vagrant/action/warden.rb:34:in `call'
	from /home/elemoine/.vagrant.d/gems/gems/vagrant-libvirt-0.0.32/lib/vagrant-libvirt/action/create_domain.rb:201:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.7.0/lib/vagrant/action/warden.rb:34:in `call'
	from /home/elemoine/.vagrant.d/gems/gems/vagrant-libvirt-0.0.32/lib/vagrant-libvirt/action/create_domain_volume.rb:51:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.7.0/lib/vagrant/action/warden.rb:34:in `call'
	from /home/elemoine/.vagrant.d/gems/gems/vagrant-libvirt-0.0.32/lib/vagrant-libvirt/action/handle_box_image.rb:109:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.7.0/lib/vagrant/action/warden.rb:34:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.7.0/lib/vagrant/action/builtin/handle_box.rb:56:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.7.0/lib/vagrant/action/warden.rb:34:in `call'
	from /home/elemoine/.vagrant.d/gems/gems/vagrant-libvirt-0.0.32/lib/vagrant-libvirt/action/handle_storage_pool.rb:50:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.7.0/lib/vagrant/action/warden.rb:34:in `call'
	from /home/elemoine/.vagrant.d/gems/gems/vagrant-libvirt-0.0.32/lib/vagrant-libvirt/action/set_name_of_domain.rb:35:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.7.0/lib/vagrant/action/warden.rb:34:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.7.0/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.7.0/lib/vagrant/action/warden.rb:34:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.7.0/lib/vagrant/action/warden.rb:34:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.7.0/lib/vagrant/action/builder.rb:116:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.7.0/lib/vagrant/action/runner.rb:66:in `block in run'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.7.0/lib/vagrant/util/busy.rb:19:in `busy'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.7.0/lib/vagrant/action/runner.rb:66:in `run'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.7.0/lib/vagrant/action/builtin/call.rb:53:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.7.0/lib/vagrant/action/warden.rb:34:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.7.0/lib/vagrant/action/builtin/config_validate.rb:25:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.7.0/lib/vagrant/action/warden.rb:34:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.7.0/lib/vagrant/action/builder.rb:116:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.7.0/lib/vagrant/action/runner.rb:66:in `block in run'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.7.0/lib/vagrant/util/busy.rb:19:in `busy'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.7.0/lib/vagrant/action/runner.rb:66:in `run'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.7.0/lib/vagrant/machine.rb:212:in `action_raw'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.7.0/lib/vagrant/machine.rb:189:in `block in action'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.7.0/lib/vagrant/environment.rb:516:in `lock'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.7.0/lib/vagrant/machine.rb:176:in `call'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.7.0/lib/vagrant/machine.rb:176:in `action'
	from /opt/vagrant/embedded/gems/gems/vagrant-1.7.0/lib/vagrant/batch_action.rb:82:in `block (2 levels) in run'

I've tried to reproduce it in various ways by attaching the public_network bridge to the same bridge as the private_network but I did not succeed.
Can you upgrade to the latest version of Vagrant (1.8.1) and the vagrant-libvirt plugin and retry?
If the problem persists, can you additionally paste the output of ip addr, brctl show, virsh net-list and avirsh net-dumpxml foo, replacing foo with each of the listed libvirt networks?

I'll try to reproduce this. In the mean time, I think you can close this issue. I'll reopen it if I see the problem again. Thanks for getting back to me.

:+1:


Make sure that outdated prefab formats get unregistered.

A new EnvironmentSwitchHandler class has been introduced that has
now the job of switching the environment of the asset manager.
It ensures that oudated prefab formats gets unregistered
in time.
ApplyModulesUtil has been removed as it's job gets now done by
EnvironmentSwitchHandler.
This should fix #1815, but I haven't tested it yet.
@Josharias Can you please check if this fixes your issue?
@immortius I hope you are fine with that solution. If you don't agree I can give further arguments why I didn't go for the ClassFactory approach.

Refer to this link for build results (access rights to CI server needed):
http://jenkins.terasology.org/job/TerasologyPRs/171/
Hooray Jenkins reported success with all tests good!

Should comment here too...  this fixed my prefab delta issues from #1815.

Yeah, this is a reasonable solution. :)


Adding Central Account Management System gateway  (Credit Card)

This is looking pretty solid - see inline comments.

Thanks Nathaniel. Will review
On Wed, Apr 22, 2015 at 4:43 PM, Nathaniel Talbott<EMAIL_ADDRESS>
wrote:

This is looking pretty solid - see inline comments.
—
Reply to this email directly or view it on GitHub
https://github.com/Shopify/active_merchant/pull/1660#issuecomment-95368393
.

I completely missed that they had their own verify implementation.  Good work keeping me honest.  Thanks for maintaining ActiveMerchant.  Great repo.  Real pleasure to work in.


Fail to Reproduce the Performance on MMVP.

Hi, it is reported in Table 8 that Cambrian-1-8b achieves 51.3 on MMVP.
However, I downloaded your official checkpoint and evaluated by myself, the performance is only 39.3.
I provided the answers inference by Cambrian-1-8b, and I used GPT-4o to grade the answers.
cambrian-8b.json

you can use eval in eval/eval/mmvp/mmvp_eval.py. This will be more stable and I reproduce it successfully

Thanks for the reply! I have successfully reproduced the results.


Increase request timeout

Chef Zero is using WEBrick which by default has a request timeout limit of 30 seconds. I would like to propose that Chef Zero changes this limit to 300 seconds in order to match the default rest_timeout setting of chef-client and so that I can avoid having failed tests in my CI environment due to this timeout.
Why? Because I've encountered this timeout limit on a fairly regular basis when using chef-client -z on a Chef Provisioning recipe that creates 10 nodes and then initiates a converge on each of them. The timeout happens during cookbook synchronization before any recipe is actually executed. Each node fetches 18 recipes - a total of 4 Mb per node - which is not really a lot but for some reason that takes around 5 minutes and sometimes gives the following error:
    [83-back1] [2015-05-21T10:20:52+00:00] INFO: Storing updated cookbooks/yum-mysql-community/attributes/mysql-connectors-community.rb in the cache.
    [84-user1] [2015-05-21T10:20:52+00:00] INFO: Storing updated cookbooks/postgresql/files/default/tests/minitest/server_test.rb in the cache.
    [87-moni] [2015-05-21T10:20:53+00:00] INFO: Storing updated cookbooks/database/templates/default/ebs-db-restore.sh.erb in the cache.
                       - database
    [85-back2] [2015-05-21T10:20:53+00:00] INFO: Storing updated cookbooks/postgresql/recipes/server.rb in the cache.
    [83-back1] [2015-05-21T10:20:53+00:00] INFO: HTTP Request Returned 408 Request Timeout :
                                                ================================================================================
                        Error Syncing Cookbooks:
                        ================================================================================

                        Unexpected API Request Failure:
                        -------------------------------
                        <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">

                          <TITLE>Request Timeout</TITLE>

Request Timeout

                            WEBrick::HTTPStatus::RequestTimeout

                            <ADDRESS>
                             WEBrick/1.3.1 (Ruby/2.1.4/2014-10-27) OpenSSL/1.0.1m at
                             release-image:80
                            </ADDRESS>

                        Running handlers:
                      [2015-05-21T10:20:53+00:00] ERROR: Running exception handlers
                        [2015-05-21T10:20:53+00:00] INFO: Storing updated cookbooks/yum-mysql-community/attributes/mysql56-community.rb in the cache.
                      Running handlers complete
                      [2015-05-21T10:20:53+00:00] ERROR: Exception handlers complete
                      [2015-05-21T10:20:53+00:00] FATAL: Stacktrace dumped to /var/chef/cache/chef-stacktrace.out
                        Chef Client failed. 0 resources updated in<PHONE_NUMBER>68 seconds
                      [2015-05-21T10:20:53+00:00] ERROR: 408 "Request Timeout "
                      [2015-05-21T10:20:53+00:00] FATAL: Chef::Exceptions::ChildConvergeError: Chef run process exited unsuccessfully (exit code 1)

When increasing the timeout limit (by temporarily monkey patching chef-client) the issue disappears.
Setting the request timeout can be done like this:
@chef_zero_server.server.config[:RequestTimeout] = 300

It still takes around 5 minutes for cookbook synchronization to complete which is strangely slow but at least it completes without timeout errors.

:+1: we are hitting this issue as well.

@ghempton
We perform the monkey patching in our client.rb:
require_relative 'monkey_patch_request_timeout'

The monkey patch file, monkey_patch_request_timeout.rb, looks like this:
# Monkey patch /opt/chef/embedded/lib/ruby/gems/2.1.0/gems/chef-12.2.1/lib/chef/local_mode.rb
# Default timeout is 30.
class Chef
  module LocalMode
    def self.with_server_connectivity
      setup_server_connectivity
      @chef_zero_server.server.config[:RequestTimeout] = 300
      begin
        yield
      ensure
        destroy_server_connectivity
      end
    end
  end
end

I hope this helps.

Hmm a little cleaner than forking I suppose. Does chef every respond to these pull requests?


Upgrade to Storm 0.9.5 and Add worker name prefix

upgrade storm 0.9.5
add worker name prefix as config parameter for mesos task id.
Make the httpserver directory as config parameter

One more minor nitpick. Should have caught it the first round. I think we're good to go after.

Please don't merge it yet :)   I (or someone else) needs to figure out where exactly the assignmentId is originating from in Storm.  I don't think it can be assumed that the values are always of the format that parsing function is assuming.

Okay, makes sense. I'll hold off.

Any updates ?

@maverick2202 : nope, sorry, haven't had any time to look at it :(  Been wrestling with weird issues relating to zombie and uninterruptible processes... seeming to all come down to bugs in the kernel w.r.t. cgroup freezing and OOM killer.  We have some new hope, just acquired tonight:  turning on PID namespace isolation in the mesos-slave might save us.  Need to test it out.  I'm trying to get back to this PR], I just need a bit of breathing room.  I'm hopeful about this PID namespace workaround.

Thanks for the update.

@maverick2202 The PR says "Upgrade to Storm 0.9.5 and Add worker name prefix", but there are more changes than the title implies. It would be nice if you could update the PR with a description of all the changes. Also, it would be helpful if you could provide examples for some of the stuff you are doing.

At high level, I want to change the worker mesos TaskId prefix as a parameter that comes from storm yaml file. Currently, the issue is that the Mesos TaskId is overloaded with the nodeid:port.

             TaskID taskId = TaskID.newBuilder()
                    .setValue(MesosCommon.taskId(slot.getNodeId(), slot.getPort()))
                    .build();

Mesos supervisor, uses the taskId to get the port.

  public static int portFromTaskId(String taskId) {
    int last = taskId.lastIndexOf("-");
    String port = taskId.substring(last + 1);
    return Integer.parseInt(port);
  }

If host has "-" then my feature will break. Can I make the ".worker--" as the delimiter instead of "-"

  public static String idFromAssignmentId(String assignmentId) {
        int last = assignmentId.lastIndexOf(".worker_");
        String id = assignmentId.substring(last + 1);
        LOG.info("AssignMentId" + assignmentId + "Id: " + id);
        return id;
  }

Ideally, you want taskId and the nodeid:port information to be passed as different parameters. But as a quick fix, will adding ".worker_" delimitor (as hostname can't have underscore) work ?

@maverick2202 I am not sure if you already looked at https://github.com/mesos/storm/pull/59/files. @erikdw is making changes to the task names and ids that gives us more visibility into the task information in the mesos ui.
However, I think your idea of having a customizable worker prefix sounds good to me as long as you also make the delimiter also configurable. To be more specific, we shouldn't hardcode the delimiter to "-" or any specific character  taskId.lastIndexOf("-"); and we should make it configurable.

@erikdw  changes are in the task name. I wanted to change the taskId. Will make the delimitor configurable.

Added all the changes. Please accept the pull request.

Can you rebase on master? And maybe squash the changes into 2 separate commits (1 for the version change, 1 for everything else).
Also, it looks like Storm 0.9.6 was just released. Is it worth upgrading to that version?

rebased to the master. 0.9.6 is not released to maven central yet.

Closing this in favour of #65.

@maverick2202 :  as I just asked in the subsequent change that @brndnmtthws opened, I must have missed the explanation for why this assignmentId stuff is being changed.  There is a discussion above about some mechanics of what is being changed, but I still haven't been able to discern why this is needed.  Please explain so we can decide what to do about this.

This is needed so that we can have prefix to the mesos taskId prefix with the topology id and other namespace. "At high level, I want to change the worker mesos TaskId prefix as a parameter that comes from storm yaml file."
This is optional feature as by default nothing will change.

@maverick2202 : thanks for the quick response!
I saw that statement before about "wanting" to do it.  But can you please bear with me and let us take a step back and be very explicit here?  What is the problem you are trying to solve?  Why do you care about the Task ID?  What can we do to most nicely address the concerns you have and solve the problem?  I'm sure there's a reason behind the desire, but I'm failing to see the purpose for adding more code to this already over-complicated code base with its way-too-long functions and intimate interdependencies with other complicated distributed systems (Storm & Mesos).   I want us to be very explicit as we may deliberate changes that further complicate
this code.
If the desire is for a more human-readable and "namespaced" row in the Mesos UI for the task, then we can avoid these changes, since the Mesos Task Name already allows us to have better strings associated with the tasks in the Mesos UI.  And as Karthick pointed out earlier we already have a change proposed for making them way better:  https://github.com/mesos/storm/pull/59
Or maybe you are thinking about skimming the mesos logs for task information?  That seems more legitimate.
The Task ID is already guaranteed to be unique at a given moment, which is the 1 requirement of a Task ID.  That is because the Task ID is the combination of the worker host and worker port (foobarhostname-NNNNN (where NNNNN is the port)), which can only be assigned to 1 topology worker at a time.
Please do not misunderstand me, I'm not wholly opposed to this change, but I am opposed to change just for the sake of change.

Hey folks,
I'm happy to continue the discussion on this, but in the meantime I'll merge #65 (which includes these changes).
If we agree on a better plan for the task naming (perhaps as per #59), we can do that as well. I, for one, am not overly opinionated about either change.

Task name is free format that is changed by #59. We wanted taskid namespaced for various things we do on the cluster.
When we launched all our apps prefixed with env, cluster, team, service. We use this Mesos taskid for logging, monitoring, health check, Security, etc.
Like Karthik wanted  this has been used as configure parameters so should cause any issues if people don't want to use it.
I would have preferred having this discussion a month earlier instead of now after making changes requested by Karthik.

Also alerts are configured based on task. Which team gets paged when things go wrong.

@maverick2202 : thanks for explaining why you want the change, makes sense.
FYI, @brndnmtthws has merged (his port of your changes)[#65] (with some minor fixes, e.g., AssignMentId -> assignmentId).
BTW, from my perspective, this change was not sufficiently explained until yesterday.....

Thanks

Hi Eric,
@maverick2202 : nope, sorry, haven't had any time to look at it :( Been wrestling with weird issues relating to zombie and uninterruptible processes... seeming to all come down to bugs in the kernel w.r.t. cgroup freezing and OOM killer. We have some new hope, just acquired tonight: turning on PID namespace isolation in the mesos-slave might save us. Need to test it out. I'm trying to get back to this PR], I just need a bit of breathing room. I'm hopeful about this PID namespace workaround.

Can you give more details or web links ? We  are seeing our cgroup freeze causing mesos slave machine to get stuck in bad state  (not ssh'able) and we have to reboot the machines manually. Any pointers or links will be helpful.

@maverick2202 : heh... yeah, welcome to our world. ;-)
So we're pretty sure that mesos's PID namespaces isolator will prevent these problems, since it works by killing the "init" process of the container which causes the kernel to immediately kill all the other processes in the container.  It's been working ok for us in our test environments, but we haven't rolled it to production yet though.  To enable it, you just need to modify the mesos-slave configuration to add the isolator. e.g.,
--isolation="cgroups/cpu,cgroups/mem"
# -->
--isolation="cgroups/cpu,cgroups/mem,namespaces/pid"

The zombie problems seem to arise from bugs in the kernel w.r.t. interactions between OOM killer, cgroups and freezing.
https://mesos.apache.org/blog/mesos-0-21-0-released/

The Mesos Containerizer Launcher has been updated to use the pid namespace to terminate all processes when destroying a container. This avoids known kernel bugs and race conditions when using the freezer cgroup. If the container is not running inside a pid namespace (started with an earlier slave version), the launcher will fall back to the prior behavior and use the freezer cgroup.

BTW, I've discovered that using PID namespaces comes with its own caveats: various JVM debugging & introspection tools are broken by PID namespaces, such as jps, jstack, etc.  But the tradeoff seems worth it.

Thanks erik for the information.


Line Item extensions do not show in one-page checkout on mobile

Please list the package(s) involved in the issue, and include the version you are using
"@shopify/ui-extensions": "^2023.7.0",
"@shopify/ui-extensions-react": "^2023.7.0",

Describe the bug
When using the purchase.checkout.cart-line-item.render-after target with one-page checkout, the blocks do not reader in the dropdown on mobile
Steps to reproduce the behavior:

Add a line item extension
Load one-page checkout on mobile
Open the order summary dropdown and notice that no extensions load
Works fine on desktop

Expected behavior
The extension should display on mobile.
Screenshots
Desktop

Mobile

Additional context
It's important for some use-cases that the line item extensions load as they display regulatory information such as Prop 65, etc. Seems like a bug rather than intention omission.

No longer an issue


OpenVPN

Hi,
There appears to be conflicting information. In this page it mentioned that only IKEv2 and SSTP are supported protocol's. However on https://docs.microsoft.com/en-us/azure/vpn-gateway/point-to-site-about it references OpenVPN as well. I'm assuming this page is just missing OpenVPN references, if that is true could the page be updated to reflect the capability of OpenVPN for routing within Azure. Thanks

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

ID: 6860efb1-ddab-04a1-bf34-4e0a41844102
Version Independent ID: 2321ec49-4cb8-d477-3430-44af3790bcdd
Content: Azure VPN Gateway: About P2S routing
Content Source: articles/vpn-gateway/vpn-gateway-about-point-to-site-routing.md
Service: vpn-gateway
GitHub Login: @cherylmc
Microsoft Alias: anzaman

@Jlouden9 , We are looking into this query and will update you as soon as possible.

@Jlouden9 , Appreciate your patience. Azure supports OpenVPN protocol in Azure VPN gateways for P2S connectivity. Here is a doc for your reference in configuring OpenVPN for Azure point-to-site VPN gateway.
Also, We will work on updating this doc accordingly.
We are closing this issue for now. If there are further questions regarding this matter, please reply and we will gladly continue the discussion.


Data Table again ..

I'm sorry to asking again but @nolimits4web was closed my issue with no explanation so please could someone explain what Im doing wrong.
Here is what I see when I click on Data Table:
http://imgur.com/EeyUIIW
I'm using /dist/js/framework7.js dated 03/21/2017
Thank you.

See #1439


use RSA-PSS instead of RSA-PKCS#1 v1.5 signature scheme

PKCS#1 v1.5 has known attacks
Signed-off-by: Jake Sanders<EMAIL_ADDRESS>

/cc @dlorenc

Is this actually used anywhere?
Either way, LGTM.

Is this actually used anywhere?

Not afaik, just want there to be a sane default.

Not afaik, just want there to be a sane default.

Thanks!


Flask-SQLAlchemy 3 compatibility

Flask-SQLAlchemy 3 was just released, here's the changelog: https://flask-sqlalchemy.palletsprojects.com/en/3.0.x/changes/#version-3-0-0
Relevant changes for Flask-DebugToolbar are:

[ ] SQLALCHEMY_RECORD_QUERIES is disabled by default and not enabled automatically with debug mode. You might want to show a warning if it's not enabled when using the debug toolbar.
[ ] get_debug_queries is renamed to get_recorded_queries, and moved to from flask_sqlalchemy.record_queries import get_recorded_queries.
[ ] The query info is a dataclass instead of a tuple. The context property is renamed to location.

The renames/moves currently show deprecation warnings, but will be removed in 3.1.

Thanks a lot for the heads up David.
This would be a great first PR if someone wants to take this on. One thing to consider is we'd like to keep backwards compatibility with SQLAlchemy 2.X for quite some time before dropping it. An ideal solution would work with both.

Hi @nickjj, I openend pull request #186 to address this issue.

#186 has been merged, thanks a lot!


[release-1.3] watch/migration: prevent status updates for finalized migrations

Manual backport of #13426
/assign dasionov
Release note
bug-fix: prevent status update for finalized migrations

/cherrypick release-1.2
/cherrypick release-1.1
/cherrypick release-1.0

/close


[stable1.12] cherry-pick kiosk commits

@abchatra Once docs/kiosk-ref.json (included in this PR) is merged into stable, the backend will no longer serve docs/kiosk.html, even if it exists.


Ensure that configured dmlc/build_config.h is picked up by Rabit and XGBoost

When we run cmake .. in a build directory, CMake generates a header build/dmlc-core/dmlc/build_config.h (see here; note that the header is inside the build directory). Right now, only dmlc target uses this generated header. Neither rabit nor objxgboost uses this header.
Instead, rabit and objxgboost targets use dmlc-core/include/dmlc/build_config_default.h. This header was meant to be a fallback, to be used only when CMake is unavailable. The fallback header is good enough for common platforms like Linux but not so good for uncommon platforms such as Alpine Linux. See #5510.
Fix:

Explicitly declare dmlc as a dependency for the rabit and objxgboost targets. This way, all relevant flags get propagated from dmlc to the targets, including:

All header paths for dmlc, including build/dmlc-core/dmlc/build_config.h;
Macros for dmlc, including DMLC_CORE_USE_CMAKE.

Upgrade minimum CMake version to 3.13. See https://cmake.org/cmake/help/v3.13/policy/CMP0079.html.
Add a test in CI where we attempt to compile XGBoost with the fallback header removed.

Closes #5510.

I really don't like this fix. Ideally, I'd like to revise CMakeLists.txt of Rabit to link DMLC explicitly, to indicate that whoever that consumes Rabit also must consume DMLC too.

CI is fixed in #5506


load_resource_pack only works a limited number of times

Godot version:
v3.1.stable.official
OS:
Kubuntu 18.10
Issue description:
ProjectSettings.load_resource_pack stops working after calling it ~1000 times (in my case). It doesn't have to be different packs, just the same one over and over again will do. It seems to leave every pack file open, including multiple copies of the same pack. It therefore fails when the limit of open files per process is reached. I increased that limit on my machine and then it took more calls to fail.
That means every application that uses this call in a way that can be triggered by the user will stop working sooner or later.
Steps to reproduce:
Call ProjectSettings.load_resource_pack() on any pack over and over again

This might be enough to fix it (untested):
diff --git a/core/io/file_access_pack.cpp b/core/io/file_access_pack.cpp
index d38d09c6b..930162741 100644
--- a/core/io/file_access_pack.cpp
+++ b/core/io/file_access_pack.cpp
@@ -201,6 +201,7 @@ bool PackedSourcePCK::try_open_pack(const String &p_path) {
 		PackedData::get_singleton()->add_path(p_path, path, ofs, size, md5, this);
 	};

+	memdelete(f);
 	return true;
 };


rename Template to HelloWorld

I'm "iffy" on this. Having it names as "template" makes it pretty clear why it's there: it's a starter to use for building recipes. Changing it to HelloWorld makes this less obvious.
However, you pointed out earlier that it may be easier for someone to copy a different recipe, make a few modifications, and then push that recipe. So, the idea of a "template" recipe might not be as useful as I thought.
On another hand, "hello world" usually indicates the simplest way to do X. So, I guess we could refer to it as the "hello world" of writing recipes.

Let's present this as both a "hello world" for PureScript but also a "hello world" for recipe-writing.


BC Environment Issue 16.2

Hi Team,
I am getting a warning regarding upgrade as per new changes.
I have downloaded the new symbols and updated all the customized extensions with new solution and fix.
I have uploaded the app file with current version.
Still Getting same warning message. "Your environment can't be updated to Business central Wave 1 16.0 Because of incompatibility issue."
Shall I just wait for Next version or shall I use Next Minor Version?

If you are on 15.x version and getting errors while upgrading to 16.0 then you have to use "Next major" version.
If you are on 16.1 and getting errors while upgrading to 16.2 then you have to use "Next minor" version.

Current Version of environment is 16.1. So I'll have to use Next Minor Version For all the Customized Extension. Right?
So After that it will not show this kind of error.

But Microsoft is updating the version in all other Business central Environment.
Is it really required to do that? Its production. I hope there would not be any data loss.

Let's get the issue to a team who will fix and backport it, as this repository is only for issues related to the AL compiler in latest developer preview environment for Dynamics 365 Business Central. We suggest that you open a support case or file a bug in Collaborate, to ensure that all Business Central users benefit from your catch as soon as possible.
To open a support case, you can:

Open a support request to CSS through the PartnerSource portal
Contact your Service Account Manager (SAM) in your local subsidiary to understand what is included in your contract as of support incident and PAH (Partner Advisory Hours). Your SAM might also direct you "step by step" how to open a support request or how to get credentials, if this is the first time for you or your company

If you file the bug in Collaborate, remember to include steps to reproduce the issue, and the Business Central build number and country version you're using.


Create table only when needed

Can you fix the tabs of lines 256, 258, 300? That's the only problem I see.


Remove duplicate participants

Need
When a user has multiple roles on one edition, his name appears multiple times on the activity page.
Deliverables
Make list items unique.

Fixed in c5cf51a0a02f1b32baad3fe0bc169884eeacef41


Add Cheerlights example for Pico W / Pico Explorer

Maybe there's a better place to put network_manager.py so we don't have to copy it to every examples directory?

I hope to put network_manager.py into a pypi package, since I keep subtly changing it.


Pin sphinx to version 5.3.0

Sphinx must be pinned to enable the docs to built using python 3.7 following changes in sphinx release 6.
https://www.sphinx-doc.org/en/master/changes.html#release-6-0-0-released-dec-29-2022
This PR pins the version in the read-the-docs environment.
Successful read-the-docs build with this change: https://readthedocs.org/projects/bens-improver-fork/builds/19074227/
Testing:

[ ] Ran tests and they passed OK
[ ] Added new tests for the new feature(s)

We should probably update the sphinx versions in the improver environments to 5.3.0 as well, unless anyone has any objections?

We should probably update the sphinx versions in the improver environments to 5.3.0 as well, unless anyone has any objections?

TBH, for the improver (this) repository, I'm not sure why there is even a separate environment for explicitly building the improver documentation.  I wonder if sphinx could not just be added to the the conda-forge env. file and removed from the rest of them.  Then also remove the doc building environment file altogether.  Not looked at the actions themselves so I could be missing something but I'll leave that for another time/issue.  If you think there is something to this discussion, you fancy me/you opening an issue?


feat: add with_retries in src/storage/rpc.rs

Resolves https://github.com/risechain/pevm/pull/233#discussion_r1745013758
Avoid 429 Too Many Requests by allowing retries when making RPC requests.

Included in https://github.com/risechain/pevm/pull/332


Dependency Problem

Hi,
I'd really like to get this working as it would be great to use in my classroom as I could deploy a midi file for the class to practice each week. If I can manage to get it working, I'd like to help make a Google Drive storage option instead of Dropbox. :)
I'm getting a 'require is not defined' in line 2 of app.js. I've tried bringing in RequireJS but I'm just swinging blindly here.
Thanks!

I see your point. Well, I removed Dropbox and changed to http://nwjs.io/ so it acts more like an ordinary game than a webside. The advantage is that you know that Web Midi API will work because it is activated when Node-Webkit starts. Also I did not have to deal with Dropbox and how to make it work etc. :).
Here you can download the full program as I have it on my HDD with binaries etc. Just hit play32.bat or play64.bat to run the game.
https://dl.dropboxusercontent.com/u/4571/musicope.zip
I use Visual Studio and TypeScript to develop the game. If you comment out the require lines in the beginning of app.ts you will get compile errors in the Visual Studio. If you follow the errors it will show you all the places where the game reads songs from files or save settings to files. You can then change these places to point to you webserver etc. to make the distribution of your midi songs easier. I will probably move all the HDD file operations to a single class when I have time to do it.
The help window while playing a song is also missing right now - this window shows you which keyboard keys you can use to move in the song, stop play, switch hands etc. I will include it soon.
I will also soon make an official binary package to run the game.

Thank you very much :+1: Ill have a tinker!

Great, let me know if you run in to any issues. Just keep in mind that I wrote it in my spare time for my piano and needs :) So it is not by any means a professional product :)

I have updated the code and released the first win-32 version. It can be downloaded in the release section. I have also extracted all io operations into io.ts file to make the change for you easier.


ITMS-90809: UIWebView API is deprecated

Apple will stop accepting submissions of apps that use UIWebView APIs.
See https://developer.apple.com/documentation/uikit/uiwebview for more information.
ILPDKit is also using UIWebView

I was using the lower version of the library, UIWebview was changed to WKWebview in the version 1.1.4.
Sorry that I couldn't pick this. I had checked the release notes but was not updated.
I'm closing this ticket and once again sorry for opening this issue.


feat: add CreateX preinstall

External review at https://github.com/ethereum-optimism/optimism/pull/11618

Merged at https://github.com/ethereum-optimism/optimism/pull/11618


⚠ Bofrost.lu has degraded performance

In 929781f, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1742 ms

Resolved: Bofrost.lu performance has improved in 5e8968d after 6 minutes.


Fix search page export to new collection

Fixes #40
Exporting to new collection didn't work due to change in response
from backend when creating a new collection. New response is:
{
    "id": 5
}

old was: 3

 Export -> new collection -> create creates an empty collection. It should create a collection out of the selected entries.


test-osuosl-aix71-ppc64-1 only has an 18Gb disk, not enough to run some test suites

Some test suites create "dmp" files which can be very large. The minimum disk size really needs to be about 30Gb.
https://ci.adoptopenjdk.net/computer/test-osuosl-aix71-ppc64-1/
I've removed the ci.role.test label and taken offline

/home has been increased to 30G on the machine


python310Packages.protego: 0.2.1 -> 0.3.0

Diff: https://github.com/scrapy/protego/compare/0.2.1...0.3.0
Changelog: https://github.com/scrapy/protego/blob/0.3.0/CHANGELOG.rst
Description of changes

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[x] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Fix for scrapy-fake-useragent failure https://github.com/NixOS/nixpkgs/pull/248329


Make sure KotlinBuildScript does not apply to settings/init scripts

Currently, when opening settings.gradle.kts or my-plugin.settings.gradle.kts then IDEA shows that you can select the script definition:
Multiple script definitions are applicable for this script.

This can be fixed by changing the regular expression on KotlinBuildScript to exclude init and settings scripts.

Your PR is queued. See the queue page for details.


Enhance the HTTP server

Support file uploads and multipart request
Provide methods for parsing the body of a application/x-www-form-urlencoded or multipart/form-data content types. The method should return a Map<String,String[]> with the name of the parameter and the values of it, this is even if there is only one value for the parameter. The values should be url decoded before storing into the map.
Support query strings in the same way of body parameters but with a diferent method.
Support cookies

All the features were implemented in the http server.


Set build-main.sh To -ANSI -std=c89 For Testing

the issue #11 got canceled, and thus we cancel this PR.


feat(app): display tabs for labware offset data when set in config

Overview
draft while tests are updated/added
Adds a tabbed view to the three locations where labware offset data can be viewed/applied when the "Show Link to Get Labware Offset Data" that shows the table view of offset data as well as the Jupyter Notebook and CLI versions
https://user-images.githubusercontent.com/66637570/219122395-07af9fd7-68c8-4067-85e6-5d5b4117b7ce.mov

Test Plan
Turn on the "Show Link to Get Labware Offset Data" advanced setting and visit the 3 locations where labware offset data is shown and ensure the 3 tabbed view show up and show the correct data. (Note: the Jupyter and CLI tabs will be empty for now until follow up work on the snippets is complete)

Changelog

Adds a RoundTab component to molecules
Adds a LabwareOffsetTabs component to organisms
Some style and minor updates to PythonLabwareOffsetSnippet
adds the LabwareOffsetTabs component to the ResultsSummary, CurrentOffsetsModal, and ApplyHistoricOffsets components

Review requests
Verify the app behaves as described in the test plan and matches the designs

Risk assessment
Low

@b-cooper I skipped all the copy updates in the modals for now since you mentioned it was a bit of a moving target and just stuck purely to adding the tabs. Happy to go back in and touch up that aspect though if things are finalized now


Upgrade Grafana chart to latest (>= 6.48.0)

Is your feature request related to a problem? Please describe.
The new version would allow display of SVG maps
Describe the solution you'd like
Upgrade the version inside the Helm chart, checking if old Panels & the datasource work

Defer until https://github.com/united-manufacturing-hub/united-manufacturing-hub/issues/1353 is done


rucksack hangs on openssl s_client commands

Hi Anthony,
I love Rucksack! I have noticed an issue. One of the commandlets I have built is to check ssl expiry dates on remote hosts using openssl. When I execute the commandlet, rucksack hangs until I press , then it displays the output. The bash command is :
[david@localhost ~]$ openssl s_client -servername <HOSTNAME> -connect <HOST:PORT> 2>/dev/null | openssl x509 -noout -dates

The rucksack configuration looks like:
check-ssl-date:
  command: "openssl s_client -servername {{ server_name }} -connect {{ server_name }}:443 2>/dev/null | openssl x509 -noout -dates"
  args:
    - server_name:
        mandatory: True
        default: server1.domain.com
        values:
          - server1.domain.com
          - server2.domain.com
          - server3.domain.com
          - server4.domain.com

Output from rucksack looks like:
[david@localhost ~]$ ruck --host localhost
localhost> check-ssl-date server_name google.ca
Attempting to run openssl s_client -servername google.ca -connect google.ca:443 2>/dev/null | openssl x509 -noout -dates <Press Ctrl-c to continue here>
notBefore=Jan 17 03:48:17 2022 GMT
notAfter=Apr 11 03:48:16 2022 GMT

localhost>
Goodbye!
[david@localhost ~]$

OS: Fedora Linux 35 Server Edition
Python version: 3.10.2

Hi @str8edgedave! I'm very happy to hear that you like Rucksack. And this is actually one of the commands that I use frequently as well!
I don't think the problem here is Rucksack. I've run into this "issue" as well with OpenSSL, and the specifics are escaping me at the moment. However, if you pipe an echo into the openssl s_client and set the no_ign_eof flag, it should work. For reasons that I can't recall, s_client will keep the connection open.
I was able to reproduce your issue and resolve it like so:
check-ssl-date:
  command: "echo | openssl s_client -no_ign_eof -servername {{ server_name }} -connect {{ server_name }}:443 2>/dev/null | openssl x509 -noout -dates"
  args:
    - server_name:
        mandatory: True
        default: www.acritelli.com
        values:
          - www.acritelli.com
          - www.github.com

The presence of the echo here causes the s_client to immediately terminate. Thus the command returns, and rucksack is able to display the output to you:
❯ ruck --host localhost
localhost> check-ssl-date
Attempting to run echo | openssl s_client -no_ign_eof -servername www.acritelli.com -connect www.acritelli.com:443 2>/dev/null | openssl x509 -noout -dates
notBefore=Jan 20 02:33:51 2022 GMT
notAfter=Apr 20 02:33:50 2022 GMT

Please let me know if this resolves your issue!

I checked with a couple of other 'openssl s_client'  commands, and you're 100% correct. It's the s_client subcommand that is holding the session. I have updated my commandlet to use the echo and the -no_ign_eof option, and it works.


Added broken connection handling to libuv adapter

Libuv adapter hangs out when connection fails. This fix adds fake write event that handles this case

:umbrella: The latest upstream changes (presumably #367) made this pull request unmergeable. Please resolve the merge conflicts.

Error handling is fixed in 'unstable' branch. But issue with getting double (EV_READ and EV_WRITE) events on close is still up, isn't it?


incomplete get_operands

Hi, is it normal that instruction.get_operands() doesn't give me the same registers as instruction.get_output()?
Example to better explain:
If i execute print instruction.get_output() I get:
v0 ... v7, Landroid/database/sqlite/SQLiteDatabase;->query(Ljava/lang/String; [Ljava/lang/String; Ljava/lang/String; [Ljava/lang/String; Ljava/lang/String; Ljava/lang/String; Ljava/lang/String;)Landroid/database/Cursor;

If I execute print instruction.get_operands() I get:
[(0, 0), (0, 1), (0, 2), (0, 3), (0, 4), (0, 5), (0, 6), (256, 420, 'Landroid/database/sqlite/SQLiteDatabase;->query(Ljava/lang/String; [Ljava/lang/String; Ljava/lang/String; [Ljava/lang/String; Ljava/lang/String; Ljava/lang/String; Ljava/lang/String;)Landroid/database/Cursor;')]

The result of get_output() ranges from v0 to v7, while the result of get_operands() ranges from (0, 0) to (0, 6). Maybe I'm wrong, but I expected get_operands() to range from (0, 0) to (0, 7).
The instruction type in this example is <class 'androguard.core.bytecodes.dvm.Instruction3rc'>
Thanks

I think I see the problem here:
in get_operands it should be  range(self.CCCC, self.NNNN + 1), as NNNN is also a valid register


Issue

@bmanishreddy Your issue contains no text, should it be closed?

Yeah .. my bad it can be closed

No worries, please close it so it doesn't create clutter.  Thanks!


Use khash for Series.value_counts, add raw function to algorithms.py

Get better performance that way. Also optimize for case of known range (a la groupby)

punting on the known range issue for now


An option to show the timepicker after a date is selected

If this option is enabled, when the user clicks on a date, the time overlay then appears without the user needing to click on the time icon.  Basically, one click on a date selects the date and then also operates as a click on the time icon.
Another datepicker (Tempus Dominus) has options for this called 'promptTimeOnDateChange' and 'promptTimeOnDateChangeTransitionDelay'.
But the Vue-datepicker is much better for Vue applications, so it would be great if you could add this type of feature.
Thanks

You can use flow prop to automatically open time picker after date selection
Use :flow ="['calendar','time']"

That’s great, I’ll give a try!  Thanks!
On Fri, May 19, 2023 at 11:15 PM abumalekFayed @.***>
wrote:

You can use flow prop to automatically open time picker after date
selection
Use :flow ="['calendar','time']"
—
Reply to this email directly, view it on GitHub
https://github.com/Vuepic/vue-datepicker/issues/395#issuecomment-1555450165,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJGHZRYS46VGIOABTHQINOLXHAZNBANCNFSM6AAAAAAYINX7UI
.
You are receiving this because you authored the thread.Message ID:
@.***>


Clean up kubebuilder generated useless (or non-standard) code (or manifests)

[x] #67
[ ] Use proper names for things like namespace, service account, role name etc instead of system, controller-manager...
[x] Update the built binary name.
[x] Update the image name

done.


Snapshot libtensorflow-1.0.1-20170323.012702-1.jar cannot find packages

With your snapshot libtensorflow-1.0.1-20170323.012702-1.jar (Downloaded from https://oss.sonatype.org/content/repositories/snapshots/org/tensorflow/libtensorflow/1.0.1-SNAPSHOT/) get the errors like:
(command:
javac -cp ./libtensorflow-1.0.1-20170323.012702-1.jar:. HelloTensorFlowSnapshot.java
)
HelloTensorFlowSnapshot.java:4: error: package org.tensorflow.exceptions does not exist
import org.tensorflow.exceptions.TensorFlowException;
                                ^
HelloTensorFlowSnapshot.java:9: error: cannot find symbol
import org.tensorflow.GraphOperation;
                     ^
  symbol:   class GraphOperation
  location: package org.tensorflow
HelloTensorFlowSnapshot.java:10: error: package org.tensorflow.proto.framework does not exist
import org.tensorflow.proto.framework.SignatureDef;
                                     ^
HelloTensorFlowSnapshot.java:14: error: package org.tensorflow.proto.framework does not exist
import org.tensorflow.proto.framework.MetaGraphDef;
                                     ^
HelloTensorFlowSnapshot.java:16: error: package org.tensorflow.proto.framework does not exist
import org.tensorflow.proto.framework.TensorInfo;
                                     ^
HelloTensorFlowSnapshot.java:17: error: package org.tensorflow.types does not exist
import org.tensorflow.types.TFloat32;
                           ^
HelloTensorFlowSnapshot.java:18: error: package org.tensorflow.tools does not exist
import org.tensorflow.tools.Shape;
                           ^
HelloTensorFlowSnapshot.java:20: error: package org.tensorflow.tools.buffer does not exist
import org.tensorflow.tools.buffer.DataBuffers;
                                  ^
HelloTensorFlowSnapshot.java:21: error: package org.tensorflow.tools.ndarray does not exist
import org.tensorflow.tools.ndarray.FloatNdArray;
                                   ^
HelloTensorFlowSnapshot.java:22: error: package org.tensorflow.tools.ndarray does not exist
import org.tensorflow.tools.ndarray.StdArrays;
                                   ^
HelloTensorFlowSnapshot.java:23: error: package org.tensorflow.proto.framework does not exist
import org.tensorflow.proto.framework.TensorInfo;

I try to run the working code from https://stackoverflow.com/questions/61228372/tensorflow-2-0-java-api.
Thanks in advance,
Milan

Please use a build tool like Maven or Gradle. Don't try to use the JAR files manually.

Hi @MilanCugur ,
you are trying to use an old artifact from the 1.x generation of TFJava (org.tensorflow:libtensorflow is legacy stuff).
Please read carefully that readme page. Our artifact are now named org.tensorflow:tensorflow-core-* and we are now at version 0.2.0-SNAPSHOT.
Let me know if you still have any issue, thanks,
Karl

@karllessard
Karl, thank you a lot for such a fast and a detailed response.
I have successfully built your project, by using mentioned snapshots.
Are there any way to get libtensorflow and jni jars like the one on the official page: https://www.tensorflow.org/install/lang_java (that can be used via classpath forwarding, and not to use maven like includings into my projects?)

libtensorflow and jni are artifacts that were distributed during TensorFlow
1.x and are considered deprecated.
You can still use them if you want (no need to fetch snapshots in this case
as they have been released a long time ago) but you cannot mix them with
the artifacts that are distributed by this SIG based on TF2.x, which are
not compatible.

Karl

On Thu, Jul 16, 2020 at 2:27 PM Milan M. Cugurovic<EMAIL_ADDRESS>wrote:

@karllessard https://github.com/karllessard
Karl, thank you a lot for such a fast and a detailed response.
I have successfully built your project, by using mentioned snapshots.
Are there any way to get libtensorflow and jni jars like the one on
the official page: https://www.tensorflow.org/install/lang_java (that can
be used via classpath forwarding, and not to use maven like includings into
my projects?)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/java/issues/84#issuecomment-659590582, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ACNEEXXUIY3FEZU4XHQV3JLR35BAZANCNFSM4O4D4YJA
.

@karllessard
Karl,
Thank you once again.
I have successfully built up your project and integrate it into the my current environment.
Everything is working just perfect! Great job!
We can close this issue.
All the best,
Milan

@karllessard
Karl, thank you a lot for such a fast and a detailed response.
I have successfully built your project, by using mentioned snapshots.
Are there any way to get libtensorflow and jni jars like the one on the official page: https://www.tensorflow.org/install/lang_java (that can be used via classpath forwarding, and not to use maven like includings into my projects?)

Yes, of course it's possible. We just need to update these instructions to reflect the new names of the JAR files.
However, it's much easier to use a build tool like Maven or Gradle anyway...


[Feature]: V1.4.0 Planning

Plan

We decide add new component Tree or Table for the version.
Complete current Form component(some state API  maybe changes).

Performance

Currently , No performance issue for fect . If you find, please contact me.
Extract some component logic for easy use.
Optimize documentation to expose internal hooks.

Patches

This version, we only publish feature. bug will be fixed in 1.3.x.

Currently, We refacotr Select component , reduce side Effect and fix dom height collapse.
And we redesgin multiple mode select behavior.

At present, we found that the Tooltip component will flicker when the trigger event is hover, and we will fix it in subsequent versions if time permits.

The development of the form component at the current stage is completed


UI-templates for MEDYAN, Cytosim, SpringSaLaD, cellPACK

Use Case
As a developer of the viewer, I need a template for each converter that specifies how to create a UI to gather required input data.
Acceptance Criteria

Each converter has a template for constructing its UI, excluding ReaDDy, PhysiCell, and MCell.

Details
For auto-converting non-simularium files provided to the viewer, we'll need to collect some additional data from the user through a UI that will depend on the type of file they are converting. SimulariumIO is a good place to keep the specification for each converter so it can be updated with the converter.
ReaDDy, PhysiCell, and MCell don't currently accept opened file data, so they require more development work before we can support autoconversion for them.

@blairlyons should MD be included in this ticket too?

@blairlyons should MD be included in this ticket too?

No, MD requires providing Python objects so it will be a little more complicated


Add some container definition properties

Added following container configuration options as defined in http://docs.aws.amazon.com/AmazonECS/latest/developerguide/task_definition_parameters.html:

DisableNetworking
DnsSearchDomains
DnsServers
DockerSecurityOptions
ExtraHosts
Hostname
Privileged
ReadonlyRootFilesystem
User
ULimits
Workingdirectory

Just spotted an error

Realised a little too late that cloudformation doesn't yet support the new container properties. Damn


Fix date iso8601 tz parsing

I am surprised we (including I) did not notice that earlier. I think the commit messages lack a ticket number.

It would nice to have tests around midnight to confirm days, months, years are changed correctly.

@guyd tests added.

+1


I can't create a project in vscode

Alert: I'm a newbie.
The whole Internet says it's very simple. Just File > New > Project. Or there is a big button right on start page. But I don't have any of these buttons, I don't even have start page, only 'Welcome' page. And when I click on 'File' there is only 'New File' and 'New window'. So, I don't know what to do, please help.

Visual Studio (the documentation in this repo, and a paid product), and Visual Studio Code (docs over https://code.visualstudio.com/docs and a free product) are not the same thing

@Densfi Thank you for submitting your issue.
As per @nschonni response, VS Code does not support full IDE development.
You can either request the feature here or check out the Visual Studio downloads to get started.


feat(templates): add ecommerce template for v3

Closed in favour of https://github.com/payloadcms/payload/pull/8297


Docker running error

Docker is throwing an error
standard_init_linux.go:211: exec user process caused "no such file or directory"

Hello @PunitTailor55 I just ran though the docker build and run steps without issue. What operating system are you running this on? Windows?

Closing issue, due to no response. STALE


Laravel doesn't seem to support numeric $_POST keys in validation rules

Laravel Version: 5.8.21
PHP Version: 7.3.1-fpm
Database Driver & Version: No DB

Description:
Laravel doesn't seem to support numeric $_POST keys when trying to validate input, including when the numeric key is between quotes to be treated as a string.
Steps To Reproduce:
First, here is a working example:
$post = [
    'question1' => null
];
$validationRules = [
    'question1' => [
        'required'
    ]
];
$messages = [
    'question1.required' => 'Answer is null'
];

$validator = Validator::make($post, $validationRules, $messages);

if ($validator->fails()) {
    dd($validator->errors());
}
dd('all good');

Which displays:
    [messages:protected] => Array
        (
            [question1] => Array
                (
                    [0] => Answer is null
                )

        )

    [format:protected] => :message

Then a non-working example, if the $_POST key is only a number in a string:
$post = [
    '1' => null
];
$validationRules = [
    '1' => [
        'required'
    ]
];
$messages = [
    '1.required' => 'Answer is null'
];

Which displays:
    [messages:protected] => Array
        (
            [0] => Array
                (
                    [0] => The 0 field is required.
                )

        )

    [format:protected] => :message

As you can see, the custom message is not there, it added a non-existent index "0" validation message with the the default "required" error.

Please see #29116.

Ah damn.. I had searched before and found a similar bug report, but failed to see this one.
And I built all my system with numeric keys after some online research to verify if this was acceptable :/ Well thanks for the info, refactoring time!


Address need to duplicate pipeline parameters for time series pipelines in automl

Post #2091, we pass pipeline instances to allowed_pipelines for AutoMLSearch. For time series pipelines, we have to specify gap and max_delay. However, in AutoMLSearch, we also have a problem_configuration parameter where we expect max_delay and gap as well. This means that the user has to duplicate these parameters (when initializing pipelines to pass to allowed_pipelines and when passing to AutoMLSearch).
We should see if we can remove this redundancy. My guess is that we introduced problem_configuration before because we were working with pipeline classes and needed to store the parameters we wanted to use when creating our pipelines. Now that we're passing around pipeline instances, this should no longer be necessary, but we may need to verify this and change any logic that looks at problem_configuration to use the gap and max_delay of the input pipelines to allowed_pipelines instead.

@angela97lin will a combination of #2159 and #1637 fix this problem?

@freddyaboulton I agree that #2159 will fix this. Let's keep it open until that issue is resolved.


Typo in Patch_ApparelUtility_HasPartsToWear.cs

Nice catch, should be the reason for the issues with some specific jewelry.
Published in 17b7538


HOW TO: pass params from parent to child screens StackNavigator ?

I navigate to ADD screen ( ADD :  StackNavigator({ with screens}) )  with  params, how  can I pass that params to screens inside ADD .. if I  navigate to screen inside ADD  with params, that screen is open twice dont know why ? and yes params are dynamically.. so I cant use initialRouteParams
Thanks a lot

I can't quite figure out exactly what you're asking, but I can guess:

you have a nested navigator within another nested navigator
you are setting params on the parent navigator, but you want the child navigator to receive them
if you navigate a 2nd time within the nested navigator, the screen is opened twice (which is basically the expected behavior by the way--although I have a PR https://github.com/react-community/react-navigation/pull/1515 that should prevent that if the screen is duplicate [i.e. has the same routeName + params])

...Basically the solution may be as simple as dispatch/navigate just to the "screens inside ADD". For example if you have this:
TabNavigator({
    ADD: StackNavigator({
         FOO: { screen: FooScreen }
    }, options)
}, options)

Then what you want to do is the following from ANYWHERE in your navigator component tree:
navigation.navigate('FOO', { bar: 'baz })

or:
dispatch(NavigationActions.navigate({ routeName: 'FOO', params: { bar: 'baz } })

@faceyspacey your solution doesn't seem to work for me, my params are not being passed to my nested screens. This is my structure:
MAIN: {
    screen: TabNavigator({
        PROFILE: {
            screen: StackNavigator({
                FOO: { screen: FooScreen },
                BAR: { screen: BarScreen }
            }, options)
        }
    )}
}

FOO is expecting an object called user to be passed to it. Whether I call navigation.navigate('FOO', { user: user } or navigation.navigate('PROFILE', { user: user }, I am still getting an error saying that user is undefined

That's exactly how it's supposed to work. I don't know what to tell you. Run the examples in this repo, and use one of the examples nested in the same way. This whole system is made to allow you to dispatch to recursively through nested navigators to the deepest child that matches.
Why are you getting an error? Before the error occurs, try logging the params. Log the entire navigation object. Put logging everywhere until you find the problem.
...also keep in mind ur nested navigators must be nested with nothing in between. It must look like what u posted above. U can't break the chain by wrapping StackNavigator in another component. PROFILE.screen must equal StackNavigator, which itself has its router at: StackNavigator.router. ...I'm also not sure what MAIN is in your example.
Another thing to try: use Redux + the Redux Devtools and looks closely at the actions dispatched and the derived state. The clues are there if u have tools helping u with the observability of what's really going on.

sorry but how do you manage to access a screen in the child navigator, from a screen in the parent navigator?
For example, if I want to access FooScreen from some other screen in PROFILE

This doesn't seem to work correctly for me.
If you have a situation like this
StackNavigator({
  FOO: { screen: BarScreen },
  BAR: StackNavigator({
      BAZ: { screen: BazScreen }
  })
})

If I'm looking at FOO screen (state is [FOO]) and then call navigation.navigate('BAZ', { user: user }); then I end up with two BAZ screens in the stack (state is [FOO, BAR [BAZ BAZ]]). I just want [FOO, BAR [BAZ]] but it seems that the BAR stack is initializing and also navigating to BAZ
Am I doing something wrong?

Hi! In an effort to get the hundreds of issues on this repo under control I'm closing issues tagged as questions. Please don't take this personally - it's simply something we need to do to get the issues to a manageable point. If you still have a question I encourage you to re-read the docs, ask on StackOverflow, or ask on the #react-navigation Reactiflux channel. Thank you!

The same problem here.

+1

+1 The same problem here

Okay everyone, after a while I have finally found a hack around this, just add a check inside navigationOptions, something like this:
Medical: {
screen: Medical_Record_Screen,
navigationOptions: ({navigation}) => {
if(navigation.state.params) {
console.log(navigation)
return {
title: navigation.state.params.title,
headerLeft: <Drawer_Button nav={navigation} />
}
}
return {}
}
},
The reason is the react-navigation always has the main routes with an id, when passing a param, the packages doesn't override the main routes but add another routes with the same routeNames but diffrent id.

@zLoneWolf  do you know how can i pass params through react-navigation with redux? i mean
in my reducer i have
case LOGGED_IN:
nextState = AppNavigator.router.getStateForAction(
NavigationActions.navigate({ routeName: 'MainAppView', params: {'myParam': 'Helmer'} }),
state,
);
then i could extract props in the view im passing the params with this line of code
const { params } = this.props.navigation.state;
but the params are not been passed. do you have any idea? thanks!


Automated cherry pick of #9163: bugfix(region): fix list by srever type normal

Cherry pick of #9163 on release/3.4.
#9163: bugfix(region): fix list by srever type normal

Codecov Report

Merging #9166 (eba5bd8) into release/3.4 (fc16c37) will decrease coverage by 2.61%.
The diff coverage is 1.53%.

@@              Coverage Diff               @@
##           release/3.4   #9166      +/-   ##
==============================================
- Coverage         6.19%   3.57%   -2.62%
==============================================
  Files              761     304     -457
  Lines           118405   62754   -55651
==============================================
- Hits              7330    2244    -5086
+ Misses          110412   60355   -50057
+ Partials           663     155     -508

Flag
Coverage Δ

aFlag
3.57% <1.53%> (-2.62%)
:arrow_down:

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

Impacted Files
Coverage Δ

pkg/cloudcommon/notifyclient/notify.go
1.78% <0.00%> (-0.03%)
:arrow_down:

pkg/compute/models/cloudaccounts.go
0.47% <0.00%> (-0.02%)
:arrow_down:

pkg/compute/models/guestnetworks.go
0.00% <0.00%> (ø)

pkg/compute/models/guests.go
0.50% <0.00%> (-0.01%)
:arrow_down:

pkg/compute/models/initdb.go
0.00% <0.00%> (ø)

pkg/compute/models/networks.go
0.47% <0.00%> (+<0.01%)
:arrow_up:

pkg/compute/models/secgrouprules.go
3.18% <0.00%> (-0.02%)
:arrow_down:

pkg/compute/models/storagecachedimages.go
0.00% <0.00%> (ø)

pkg/compute/models/vpcresource.go
0.00% <0.00%> (ø)

pkg/compute/models/vpcs.go
1.02% <0.00%> (-0.01%)
:arrow_down:

... and 454 more

Continue to review full report at Codecov.

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


[Stepper] Simplify property name and update property docs

[x] PR has tests / docs demo, and is linted.
[x] Commit and PR titles begin with [ComponentName], and are in imperative form: "[Component] Fix leaky abstraction".
[x] Description explains the issue / use-case resolved, and auto-closes the related issue(s) (http://tr.im/vFqem).

Stepper.jsx:

Change prop name activeStepIndex to activeStep
Change prop name updateCompletedStatusOfStep to updateCompletedStatus (This could probably be simpler still, but I'm lacking imagination!)
Update property docs

HorizontalStep.jsx

Tiny change to one prop docs comment.

VerticalStep.jsx

Various prop docs updates.
Correctly close a

Examples:

Update to use changed prop names
Simplify state naming

let's add some spacing here

Just leaving a note here for reference: I've found a significant number of issues with the Stepper while discussing some of the changes here with @mbrookes . I'm going to open up an issue detailing my findings as we may want to reconsider including this in 0.15.0 (part of it at least).


Switch to prime-order subgroup

This branch switches the verifier to use a prime-order subgroup for exponents, as specified in the final version of the ElectionGuard spec.  (Current master instead uses the group mod p-1, as specified in a previous draft of the spec.)  The primes used in this branch are the same ones from the encryption SDK (specifically bignum.c).  This branch also adds some checks from the spec that were previously not implementable due to the exponent group having non-prime order.
To run the tests:
cargo test --lib --release --feature test-big-primes

The --feature test-big-primes causes tests to use the real, full-sized primes from the spec, instead of the small primes that allow for quick test runs.  When using the full-size primes, --release is highly recommended, since computing with such large values is quite slow in debug builds.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: spernsteiner sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

I believe this work is covered under our previous contract.  I've done some cleanup to allow rebasing against current master and switched out the primes, but the vast majority of this code is copied from this branch of the original development.  If you think the CLA is still necessary, please let me know and I'll check with our legal team.

@echumley-msft ping - not sure if you got the notification when I opened the PR.  This is the branch we discussed yesterday for updating the verifier to use the same parameters as the encryption SDK.

Hey @spernsteiner - would you mind signing the CLA agreement? (Linked in the PR above) I can't merge this in until that's complete. Thanks!

I'm currently waiting to hear back from our legal team on whether I can sign that CLA.  (Though, as mentioned above, I don't think it should be necessary in this case.)  I should have an update for you by Monday.


images tuples become opaque when loading images.viewer.prettyprint

Pretty printing image objects as images is nice (USE: images.viewer.prettyprint), but it should be possible to revert back to the string tuple representation. Maybe through a per-image right-click ->"show as tuple" ? Also add a way to globally revert for all images more convenient than [ M\ image pprint* forget ] with-compilation-unit ?

Fixed in c329631e259d19a9fa1ffd180dffb4a0e9635d06, for now default to not prettyprinting images this way (except XKCD, because @erg and its awesome).


Automatic update of LibGit2Sharp to 0.27.0-preview-0034

NuKeeper has generated a minor update of LibGit2Sharp to 0.27.0-preview-0034 from 0.26.2
LibGit2Sharp 0.27.0-preview-0034 was published at 2019-11-20T22:32:51Z, 9 months ago
1 project update:
Updated NuKeeper.Git\NuKeeper.Git.csproj to LibGit2Sharp 0.27.0-preview-0034 from 0.26.2
LibGit2Sharp 0.27.0-preview-0034 on NuGet.org
This is an automated update. Merge only if it passes tests
NuKeeper: https://github.com/NuKeeperDotNet/NuKeeper

Solves #1015 1015

Approve using a preview, when it is to fix an issue that we are being impacted by, and the release is not coming soon.


Convert Ref objects to ref string in OpenAPI YAML output

This issue fixes #1546 which reports that the OpenAPI emitter's new YAML output encodes $refs as a sub-object with a value property.  This change uses the replacer option of yaml.dump to ensure that Ref objects get written out correctly as a string path.

Yep, discriminator mapping:
https://cadlplayground.z22.web.core.windows.net/prs/1552/?c=aW1wb3J0ICJAY2FkbC1sYW5nL3Jlc3QiOw0KDQp1c2luZyBDYWRsLkh0dHA7DQpAc2VydmljZSh7DQogIHRpdGxlOiAiV2lkZ2V0IFPGHCIsxBx2ZXJzaW9uOiAiMS4wLjDEFX0pDQpuYW1lc3BhY2UgRGVtb8cyxW1AZGlzY3JpbWluYXRvcigia2luZCIpDQptb2RlbCBQIMVyxBU6IHN0cmluZzsNCn3EOcYhUSBleHRlbmRzzisiUeQAy8soUtcoUskob3AgdGVzdCgpOiBQOw0K

I think this just needs another regen-samples to fix the sample outputs that have discriminator mappings (hopefully just that).


Add operation_id for routes

FastAPI allows us to set a unique identifier for each route called operation_id. This operation_id is mainly used by third party libraries to identified each endpoint easily and to generate code from it.
Currently, running the following command to generate a Typescript client from your API specifications will result in some junky method names
// "openapi-typescript-codegen": "^0.20.1"

openapi --input https://overfast-api.tekrop.fr/openapi.json --output ./client --client axios

Setting the operation_id will allow the generated client to have more simpler name for each method

(I can share my whole config if you want to generate a Typescript client by yourself 😄)

Oh, very nice feature I didn't know about, thank you for the PR 😄 I took a look at the generated client, seems to be a very good start for making calls to the API, thank you for sharing 😛 I'll merge it right away and deploy it this evening along with another update 😄


{AKS} Fix aks upgrade, keep aad profile in upgrade request

This checklist is used to make sure that common guidelines for a pull request are followed.
Fix aks upgrade, keep aad profile in upgrade request.

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your PR is merged into master branch, a new PR will be created to update src/index.json automatically.
The precondition is to put your code inside this repo and upgrade the version in the PR but do not modify src/index.json.

AKS


foundation-sites-template doesn't contain menu-icons include needed by 6.2.0

How can we reproduce this bug?

I have created a new test foundation 6.2.0 sites test folder (foundation new -> sites -> basic template)
Simple test of a responsive menu showed up without hamburger menu
scss/app.scss doesn't contain the following line:
@import 'components/menu-icon';
included in scss/foundation.scss (line #36).

What did you expect to happen?
I expected the app.scss to contain all necessary includes.
What happened instead?
Hamburger menu doesn't show up in responsive menu
Test case:
It's not a sites per se problem - it's a foundation-sites-template problem. Use cli to create a blank new 6.2.0 site and check scss/app.scss file.

Fixed via zurb/foundation-sites-template@555e8f44c6ca97eeb51106df72a69e17e7b79843
Made the same fix to the ZURB Template as well: zurb/foundation-zurb-template@dfd63a823dea2624f10efce22e4c08524bfb559f


Set up reasonable steps and automation for running itest locally

TODO

[ ] Add npm itest. It should allow for the --slow option, and tell you when you haven't supplied the right env vars.
[ ] Make CI use npm itest.
[ ] Are AWS_DEFAULT_REGION and AWS_REGION both necessary? I think they are, because I think one is for the SDK. They are both set in CI.
[ ] Add a smoke test option to the itest app. Do this as part of it. This will take the place of https://github.com/douglasnaphas/madliberation/issues/311.

I think it's time for npm itest, and for Interaction with the project should be through npm run ..., that is, package.json should present the inerface for the project, and CI and local dev should interact with the project using that interface to be elevated to a Turnkey principle, or some other recommended guiding principle of development.

How about automating checks on the Turnkey principles, like AWS Well-Architected?

https://stackoverflow.com/questions/17319100/iterating-over-variable-name-in-bash-script
for v in REQVARNAME OTHER REQVARNAME ; do if [[ ! -n “${!v}” ]] ; then echo “need bar named ${!v}” ; exit 1 ; fi ; done

Done.


update datepicker.js

add international support for the following buttons :Today,Clear,Close

I am not sure if this is something we should do.
I am open for a discussion about supporting i18n in our library in a new issue.
Thanks.


refactor: switch to uuid.Must

Given that we're doing a deploy soon this can wait since it's a non essential change. Just thought I'd open the PR first

hmm i'm not sure if this is necessary or safe since uuid.Must will panic if the error is not nil

Hmm it shouldn't ever return a nil I think - see https://github.com/supabase/gotrue/pull/891#discussion_r1136624085
It'd cut back on code I guess but yeah if there's a significant chance that it'll ever panic let's close this PR

hmm ok that makes sense, i guess it's alright then


allow to use molior-deploy with installer.plugin on Ubuntu 20.04

@neolynx any progress on this?

This should work in the meantime, the only thing you need to set is the LINUX_IMAGE_NAME.
# vim: syntax=sh

DEPLOYMENT_TYPE=installer
ARCH=amd64

LINUX_IMAGE_NAME="linux-image-generic"
INSTALLER_EXTRA_MODULES="i915 nvme"


can we remove these warnings during build

would be nice to mitigate warnings
while yarn dev or yarn generate

@yangwao
there are 2 mitigation strategies here:

rename fragments in unique folder
disable this warning by invoking disableFragmentWarnings
which do you prefer?

But wait, is that issue with our queries? Removing warning isn't the best way tho as warning is there for reason? 😄
cc @vikiival maybe to shot his insight

disabling warning is not best, but acceptable approach.
What is Fragment?
Fragment is a reusable piece of grapghQL query, so instead of querying name, metadata, max, you can write ...collection`
The best approach would be to create reusable fragment (eg. baseCollection) and then extend fragment with baseCollection and other data

It doesn't effect our queries since we explicitly import the corresponding fragment correctly.
The library just checks globally if there are multiple fragments with the same name. This warning however doesn't imply that something is broken. It's just hinting at the fact that we could be importing the wrong fragment or even two fragments with the same name (which in fact would break the query).
I can of course implement it via extensions like @vikiival suggested

I can of course implement it via extensions like @vikiival suggested

Yup, rather try to fix warning by naturally solve the issue :)

@vikiival sadly it looks like we cannot just extend fragments of fragments like with classes and interfaces. i therefore split up the "extended" one into separate fragments. and then we just import them both like described here https://www.apollographql.com/docs/react/data/fragments/#creating-colocated-fragments

"Alexa play summertime sadness"


fix(deploy-private-endpoint-private-dns-zone-link): typo in

fix for #403
blob_secondary domain

@microsoft-github-policy-service agree company="adesso se"


remove os.path.normcase calls

Fixes #1854, I think
Adds a test case for uppercase model names and ref('UPPERCASE')

Do you remember why normcase was included here in the first place?

I think it was for test issues with docs generate. That's not necessary anymore because we do all comparisons in those test cases via normcase anyway.

ship it!


test: additional unit-tests for object

This PR will:

Add explicit testing of shape() method
Add explicit testing of extend() method, currently not covered
Update readme.md for deno (due to ad4385439d7c0d7a584052dee5aa578fde5a6efd)

@colinhacks let me know if this is redundant and I will close the PR.


Exclusion List Escape Observed

From j1939-84 created by ericthomasswenson: Equipment-and-Tool-Institute/j1939-84#1029
Exclusion List Escape Observed.
Was SP 12691 expected in exclusion list?  Or was 12691 added to DM24 in error, as there was to be one representative for all GHG?
DM24 from Engine #2 (1): [
D F T F
a r e F
t F s l
a r t n  SPN — SP Name
D F   2  SPN 27 - Engine EGR 1 Valve Position
...
D     4  SPN 12675 - NOx Tracking Engine Activity Lifetime Fuel Consumption Bin 1 (Total)
D     1  SPN 12691 - GHG Tracking Lifetime Active Technology Index
D     4  SPN 12730 - GHG Tracking Lifetime Engine Run Time
SPN 12675 is supported by Engine #2 (1) but will be omitted
SPN 12730 is supported by Engine #2 (1) but will be omitted
13:35:08.3803 DS Request for PGN 64257 to Engine #2 (1) for SPNs 12691
13:35:08.3818 18EA01F9 [3] 01 FB 00 (TX)
13:35:08.4743 18FB0101 [28] FA 00 00 00 00 00 00 00 00 F9 00 00 00 00 00 00 00 00 F8 00 00 00 00 00 00 00 00 00
Green House Gas Lifetime Active Technology Tracking  from Engine #2 (1):
SPN 12691, GHG Tracking Lifetime Active Technology Index: 11111010
SPN 12692, GHG Tracking Lifetime Active Technology Time: 0.000000 s
SPN 12693, GHG Tracking Lifetime Active Technology Vehicle Distance: 0.000000 m
Add 12691 and similar SPs to exclusion list. SP 12730 should trigger this query in the planned discrete tests.

See https://github.com/Equipment-and-Tool-Institute/j1939-84/issues/817 for the planned addition of SP 12691 into the exclusion list.  Perhaps we should provide the planned exclusion list in Task 1.
c. Omit the the following SPNs (588, 976, 1213, 1220, 12675, 12691, 12730, 12783, 12797) which are included in the list. Display the completed list noting those omitted SPNs, supported SPNs as ‘broadcast’ or ‘upon request’, and additions from Table A-1, such that the additions are distinct from the data in DM24.


Cannot find name 'Blob' when running typescript complier

When compiling my typescript project after installing this package (using tsc), it gave me the following errors:

stacktrace
node_modules/square/dist/apiResponse.d.ts:14:20 - error TS2304: Cannot find name 'Blob'.

14     body: string | Blob | NodeJS.ReadableStream;
                      ~~~~

node_modules/square/dist/errors/apiError.d.ts:17:20 - error TS2304: Cannot find name 'Blob'.

17     body: string | Blob | NodeJS.ReadableStream;
                      ~~~~

node_modules/square/dist/errors/responseValidationError.d.ts:13:20 - error TS2304: Cannot find name 'Blob'.

13     body: string | Blob | NodeJS.ReadableStream;
                      ~~~~

node_modules/square/dist/fileWrapper.d.ts:5:11 - error TS2304: Cannot find name 'Blob'.

5     file: Blob | import('stream').Readable;
            ~~~~

node_modules/square/dist/fileWrapper.d.ts:7:23 - error TS2304: Cannot find name 'Blob'.

7     constructor(file: Blob | import('stream').Readable, options?: FileWrapperOptions | undefined);
                        ~~~~

node_modules/square/dist/http/httpResponse.d.ts:9:20 - error TS2304: Cannot find name 'Blob'.

9     body: string | Blob | NodeJS.ReadableStream;
                     ~~~~

node_modules/square/dist/http/requestBuilder.d.ts:27:19 - error TS2304: Cannot find name 'AbortSignal'.

27     abortSignal?: AbortSignal;
                     ~~~~~~~~~~~

node_modules/square/dist/http/requestBuilder.d.ts:70:96 - error TS2304: Cannot find name 'Blob'.

70     callAsStream(requestOptions?: RequestOptions): Promise<ApiResponse<NodeJS.ReadableStream | Blob>>;
                                                                                ~~~~

node_modules/square/dist/http/requestBuilder.d.ts:128:96 - error TS2304: Cannot find name 'Blob'.

128     callAsStream(requestOptions?: RequestOptions): Promise<ApiResponse<NodeJS.ReadableStream | Blob>>;
                                                                                ~~~~

node_modules/square/dist/http/requestBuilder.d.ts:136:59 - error TS2304: Cannot find name 'Blob'.

136 export declare function convertToStream(content: string | Blob | NodeJS.ReadableStream): Blob | NodeJS.ReadableStream;
                                                              ~~~~

node_modules/square/dist/http/requestBuilder.d.ts:136:90 - error TS2304: Cannot find name 'Blob'.

136 export declare function convertToStream(content: string | Blob | NodeJS.ReadableStream): Blob | NodeJS.ReadableStream;

After some Googling, I found (in this issue) that I needed to add "dom" to complierOptions.lib array in my tsconfig.json.
I don't think this is an error in the package, but it may be smart to add it to the readme or at least have it documented in an issue in case someone else has the same issue 😄

Hello there, is your project browser based?

Nope running on Firebase Cloud Functions

Since this is now documented in this issue and the fix exists outside the SDK, I am closing this issue.