Add additional libraries needed to link heimdall

I needed to add jasper and libwebp as I was getting linker errors:
$ make
[...]
../x86_64-w64-mingw32/bin/ld.exe: cannot find -ljasper
../x86_64-w64-mingw32/bin/ld.exe: cannot find -lwebp

This seems very peculiar. Heimdall definitely doesn't depend on video or image codecs - at least not directly.
The only way they could be getting pulled in is if Qt5 has those dependencies, in which case Pacman should be resolving Qt5's dependencies.

Likely, that is exactly what is requiring those dependencies. A viable workaround is installing the following packages:
pacman -S mingw-w64-x86_64-jasper mingw-w64-x86_64-libwebp

Also, for posterity:
$ make
[  6%] Built target pit
[ 53%] Built target heimdall
[ 56%] Automatic moc for target heimdall-frontend
[ 56%] Built target heimdall-frontend_autogen
[ 60%] Linking CXX executable ../bin/heimdall-frontend.exe
C:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/5.2.0/../../../../x86_64-w64 -mingw32/bin/ld.exe: cannot find -ljasper
C:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/5.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe: cannot find -lwebp
C:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/5.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe: cannot find -lwebp
collect2.exe: error: ld returned 1 exit status
heimdall-frontend/CMakeFiles/heimdall-frontend.dir/build.make:338: recipe for target 'bin/heimdall-frontend.exe' failed
make[2]: *** [bin/heimdall-frontend.exe] Error 1
CMakeFiles/Makefile2:198: recipe for target 'heimdall-frontend/CMakeFiles/heimdall-frontend.dir/all' failed
make[1]: *** [heimdall-frontend/CMakeFiles/heimdall-frontend.dir/all] Error 2
Makefile:83: recipe for target 'all' failed
make: *** [all] Error 2


add publicNetworkAccess property to datafactory

add publicNetworkAccess property to datafactory
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[x] I commit to follow the Breaking Change Policy of “no breaking changes
[x] I have reviewed the documentation for the workflow.
[x] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

[ ] Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.

Adding new API(s)
Adding a new API version
Adding a new service

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If there are following updates in the PR, ensure to request an approval from API Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in stable version
[ ] Removing properties in stable version
[ ] Removing API version(s) in stable version
[ ] Updating API in stable version with Breaking Change Validation errors
[ ] Updating API(s) in preview over 1 year

Please follow the link to find more details on PR review process.

/azp run automation - sdk

@akning-ms
Hi,
we are adding a new property for data factory: publicNetworkAccess, this is expected change. Can you please help to approve?

In python SDK breaking change, the compression_type rename is approved by breaking change review board in PR: https://github.com/Azure/azure-rest-api-specs/pull/10815


Unresolved dependencies

Hi everyone,
I'm struggling with an error and come to see if somebody has the same :
I did the installation on a Mac and on a Ubuntu machine, I get the same error
I did the installation of every dependency, did the npm packages installation, started the api server and when I post a request with a pdf document and the config file under I get this error :
Error: Module regex-matcher has unresolved dependencies (lines-to-paragraph).
Is there somebody with the same problem or knowing how to resolve it ? Thank you !
Edit : I tried with several modules and I always get the same error with all the dependencies of the module I called in my config...
Config :
{
"version": 0.9,
"extractor": {
"pdf": "pdfminer",
"ocr": "tesseract",
"language": ["eng", "fra"]
},
"cleaner": [
[
"regex-matcher",
{
"queries": [
{
"label": "Something 1",
"regex": "Test"
},
{
"label": "Something 2",
"regex": "Salut"
}
]
}
]
],
"output": {
"granularity": "word",
"includeMarginals": false,
"includeDrawings": false,
"formats": {
"json": true,
"text": false,
"csv": false,
"markdown": false
}
}
}

Hello!
It's not related to Node dependencies but rather to your pipeline configuration.
It means you need to have more modules in your "cleaner" section.
"cleaner": [
    "words-to-line", { "maximumSpaceBetweenWords": 100 }],
    "lines-to-paragraph",
    [
        "regex-matcher",
        {
            "queries": [
                {
                    "label": "Something 1",
                    "regex": "Test"
                },
                {
                    "label": "Something 2",
                    "regex": "Salut"
                }
            ]
        }
    ]
]

https://github.com/axa-group/Parsr/blob/master/docs/configuration.md#5-exempli-gratia


fix: upgrade to vpc module v7.5.0

Description
Upgrade to terraform-ibm-landing-zone-vpc module to v7.5.0, which includes a change to clean (empty) the default VPC Security Group and ACL so that they will not have any rules.
Release required?

[ ] No release
[x] Patch release (x.x.X)
[ ] Minor release (x.X.x)
[ ] Major release (X.x.x)

Release notes content
This release includes an upgrade to the terraform-ibm-landing-zone-vpc module (v7.5.0) which changed how the default VPC Security Group and ACL can be cleaned of rules (less permissive).
terraform-ibm-landing-zone-vpc v7.5.0
The VPC module upgrade has changed the inputs required to clean the sg/acl and this release of landing zone also incorporates the following changes:

REMOVED: clean_default_security_group and clean_default_acl from VPC configuration
ADDED: clean_default_sg_acl to VPC configuration

Upgrade Notes:
After upgrade to this version, you may notice the following resources are marked for destroy during your next terraform plan phase. This is expected, as we have retired the scripts that were executed by these null_resource blocks and they are not needed.
module.landing_zone.module.vpc["management"].null_resource.clean_default_acl[0] will be destroyed
module.landing_zone.module.vpc["management"].null_resource.clean_default_security_group[0] will be destroyed

Run the pipeline
If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.
Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:
/run pipeline

Checklist for reviewers

[ ] If relevant, a test for the change is included or updated with this PR.
[ ] If relevant, documentation for the change is included or updated with this PR.

Merge actions for mergers

When merging, use a relevant conventional commit message that is based on the PR contents and any release notes provided by the PR author. The commit message determines whether a new version of the module is needed, and if so, which semver increment to use (major, minor, or patch).
Merge by using "Squash and merge".

/run pipeline

@toddgiguere upgrade tests failing but I think they are expected. I'll let you take a look to confirm

Upgrade tests for all 4 patterns has failed, which was expected due to changes in the VPC module.
Each pattern test upgrade had the same 4 resources marked for destroy after upgrade:

module.landing_zone.module.landing_zone.module.vpc["management"].null_resource.clean_default_security_group[0] Actions: [delete]
module.landing_zone.module.landing_zone.module.vpc["management"].null_resource.clean_default_acl[0] Actions: [delete]
module.landing_zone.module.landing_zone.module.vpc["workload"].null_resource.clean_default_security_group[0] Actions: [delete]
module.landing_zone.module.landing_zone.module.vpc["workload"].null_resource.clean_default_acl[0] Actions: [delete]

All four of these null_resource blocks were retired in the new version of the vpc module, which is why they are marked for destroy in this upgrade.
We will skip upgrade test for this PR.

/run pipeline

:tada: This PR is included in version 4.10.0 :tada:
The release is available on:

GitHub release
v4.10.0

Your semantic-release bot :package::rocket:


Rudimentary handling of empty facets for HistogramVisualization only

This is one way to do it, but it's not ideal.
GEMS1 filter country=India

An improvement would be for FacetedPlot to render the facet title outside of Plotly (this would give us more control over styling and things like overflow/ellipsis handling).  FacetedPlot could also render a large "No data for this facet" for individual facets where facet.data == null.  Thoughts?
Note that the back end doesn't return empty data for empty facets, but it's easy for the client to put in an undefined where needed (I'll add an annotation to the PR).

Thanks - yes I have just made it: https://github.com/VEuPathDB/web-eda/issues/681


Channels with capital letters are sorted at the top

When I connect to a znc bouncer, the channels with capital letters are autosorted to the top. Obviously this shouldn't be the case.

Yeah, this is basically down to how characters are ordered.
Example:

"Z" < "a"
true
"a" < "b"
true

So, basically it goes through A-Z and then a-z.

Poking around from my phone, I'm having trouble finding where the channel sorting occurs. But surely there is a way to substitute a case insensitive sorting function?

@dgw, it's... awkward to say the least. I looks like this is a place where we would do channel sorting, but to be honest I'm not entirely sure that function does any sorting at all.
I don't use ZNC so I'm not too sure but is there any chance ZNC itself could be providing us with a list of channels to join already sorted that way?

I don't believe that's the case, it sorts them correctly on my phones client (AndroIRC) and HexChat

ZNC actually has its own issue(s) open for channel join order/sorting (znc/znc#104, znc/znc#238).

Unless I am mistaken, lounge does not do any alphabetical sorting on channels. When channels are joined, they are appended to the bottom of the list. The client.sort method is for manual sorting (e.g. dragging channels). Since you use znc, I believe that's where sorting issue comes from. However, I think lounge user's sorting should persist even on top of znc connections (it does for me on master).


Might I suggest that you add more example projects, so we can review them and understand how this new API works?

Thank you!

Nothing is stable yet, that will happen later

Okay! Please close this issue when that does happen so I can be notified. Thank you!


As a company I want to have the option to configure notice boards for public access

Acceptance criteria:

[ ] Notice boards can be configured as public
[ ] The configuration generates a link
[ ] The link to the public notice board links to an isolated location
[ ] Public notice boards can be accessed from outside the company

Security issues about confidential information.


MAC-275 - SQL Timeouts

no need to release these changes to PROD as they were just to diagnose the issue which eventually got fixed by increasing DTUs in Azure


Use Streetmix logo.

We'd been using this very simple text mark for a little while now, this just brings it into the application.
Old:

New:

Are we going to change logo?  Putting it in the application will hopefully be better for consistency.


[TS-2157] Replace addr with src_addr and dst_addr

This is largely a renaming of existing conventions--there are a few areas I've highlighted w/ comments.
merge of two commits:
initial commit
update http transact

https://issues.apache.org/jira/browse/TS-2157

This looks basically OK but I think we might want to change dst and src to local and remote.  I think that's less ambiguous. I can do that as part of working on the pull request if it seems reasonable.

@SolidWallOfCode. I think there was some discussion of that on the JIRA, actually (toward the top). I was of the mindset that that made more sense too at first.


Improve e2e test coverage of services

What's currently included in the services e2e test:
https://github.com/GoogleCloudPlatform/kubernetes/blob/master/test/e2e/service.go

Services should serve a basic endpoint from pods
Services should serve multiport endpoints from pods
Services should be able to create a functioning external load balancer
Services should be able to create a functioning NodePort service
Services should be able to change the type and nodeport settings of a service
Services should release the load balancer when Type goes from LoadBalancer -> NodePort
Services should prevent NodePort collisions
Services should check NodePort out-of-range
Services should release NodePorts on delete
Services should correctly serve identically named services in different namespaces on different external IP addresses

What's not yet covered (and there are surely more than what's in the following list):

Multiport TCP services (this seems false given item 2 above - update the comments).  https://github.com/GoogleCloudPlatform/kubernetes/blob/master/test/e2e/service.go#L67
Spreading of traffic across backends appropriately (round robin etc).  @satnam6502 had an indirect test somewhere for this AFAIK, but we should perhaps factor it into a narrow service-specific test.
LiveNessProbes (perhaps belongs in Kubelet e2e tests, but it would be good to make sure that they are usable and work properly in the use case of providing a highly available service).
ReadynessProbes (comments as above)
General high availability of services in the presence of pod or network failure. Inject pod, node and network failures, and verify that the service remains available, within the published specs.
More... ??

@cjcullen @dchen1107 @justinsb @a-robinson  purely FYI

@quinton-hoole Great to see tracking issues like this.  Presumably we have other gaps in our e2e testing -- are there similar ones for ensuring other cluster invariants hold?  What do we need to do to have 100% coverage as part of API compliance testing?

I have not yet managed to figure out a good answer to your last question yet.  It turns out to be challenging to accurately measure e2e test coverage.  I have some code to analyse API server logs to determine what percentage of the (objects x operations x response_codes) landscape has been exercised by a given test run, but given the number of optional aspects of many API object types (Does this service have an external load balancer?  Does it have liveness probes?  Does it have an underlying replication controller? etc, etc to name just a few), it seems inevitable that a human will need to make some subjective judgement of how much of this landscape can and should be reasonably tested.  And of course that landscape is constantly changing as we evolve the system.
It's near the top of my post-v1.0 priority list though ;-)

I will work on a couple of these if no one else is.

Thanks @mikedanese, that would be great!

Spreading of traffic across backends appropriately (round robin etc). @satnam6502 had an indirect test somewhere for this AFAIK, but we should perhaps factor it into a narrow service-specific test.
This is covered in shell tests - see https://github.com/GoogleCloudPlatform/kubernetes/blob/master/hack/e2e-suite/services.sh
We should also migrate the shell test to Go - I've created #10980, but this should be post 1.0 work.

Indeed, my test sprays lots of requests via service to pods and then checks that there is a response from each pod and reports the distribution of responses.

As discussed over lunch, lets move this to an e2e test @satnam6502, to improve CI test coverage as well as prevent bit rot of the test code.

I don't understand this comment - this shall script is also running as e2e test. I've just fixed this today and will be moving it out of flaky suite.

Oh, apologies for the confusion.  I'm referring to Satnam's test referred
to above.
On Thu, Jul 9, 2015 at 1:17 PM, Wojciech Tyczynski<EMAIL_ADDRESS>
wrote:

I don't understand this comment - this shall script is also running as e2e
test. I've just fixed this today and will be moving it out of flaky suite.
—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/issues/10268#issuecomment-120133936
.

This is marked 1.1 and P2 and hasn't been touched in over three months. Writing more e2e tests sounds like a great idea but not really a 1.1 blocker. @quinton-hoole can we punt this to 1.2?

Not strictly true that this has not been touched in over three months.  Both @mikedanese and @ArtfulCoder have been working on improving service test coverage, as discussed in the linked #11067 and associated PR's.  We're still missing some e2e coverage of services, IMO.  I'll assign this to @artfulcoder and team/cluster to decide what they want to do with it.

@kubernetes/goog-cluster @thockin FYI

Several of these points are covered in the kube-proxy test.  There's a very grey area between services and kube-proxy where the tests overlap

I moved this to 1.2 - there's always more we can do.

Oops, very sorry, somehow I didn't realize that the date on a reference to an issue/PR that Github inserts is the date the issue/PR was initially mentioned, not the date it was last updated. Kinda makes sense, but for some reason I was assuming Github did the "cooler" thing (last update) and I didn't click through to the thread, hence my confusion about when #11067 was last touched.

I'm closing this for now because Services E2Es have made a lot of progress in the past few months.

Spreading of traffic across backends appropriately (round robin etc). @satnam6502 had an indirect test somewhere for this AFAIK, but we should perhaps factor it into a narrow service-specific test.

The services test checks that we reach all backends, which sort-of validates rr. I don't think we have anything for client affinity, filed: https://github.com/kubernetes/kubernetes/issues/21329

LiveNessProbes (perhaps belongs in Kubelet e2e tests, but it would be good to make sure that they are usable and work properly in the use case of providing a highly available service).
ReadinessProbes (comments as above)

We have both these in various kubelet tests.

General high availability of services in the presence of pod or network failure. Inject pod, node and network failures, and verify that the service remains available, within the published specs.

https://github.com/kubernetes/kubernetes/pull/19731 was one step toward this.

More... ??

I think these should take the form of individual issues.


Move Tolerance Stops Scroll

Issue:
When you make use of the new moveTolerance setting in ol.Map (https://openlayers.org/en/latest/apidoc/ol.Map.html) then scrolling will freeze if you move your finger back over the original position you put your finger down.
The bigger the moveTolerance the easier this is to see - we have had to set ours to 5px as some android devices were really struggling with the click bug.
Related PR:
https://github.com/openlayers/openlayers/pull/6778
https://github.com/openlayers/openlayers/pull/6834
Fix:
It looks like it should be a relatively easy fix; we could just check whether dragging is true in the isMovingFunction: https://github.com/openlayers/openlayers/blob/e0e9c2677d5e108d4093006449c5f340f25ccb0e/src/ol/MapBrowserEventHandler.js#L303
I'm at work at the moment but I can have a look when I get home :)

Confirm the issue! @JackFrostStudios did you eventually get home :-D ?
Any confirmation from OpenLayers team that that could be the way to go to solve it?

Hello, I'm experiencing this issue in OL 4.2, is it already fixed in last stable version?
Thank you!

Thanks @ahocevar ...
any plan to fix this nevertheless? Do you consider it as a bug?
It becomes more apparent when the tolerance size is large, and it is quite disturbing to see the scrolling freeze when going over the initial 'click' position...

Sure! Not even worth a codePen:

Take any map example
Set tolerance to a higher value (very large, like 50, will help you identify the issue better, but the behaviour obviously happens at any value).
Start dragging to move the map. At first, the map won't move until you have dragged more than 50 pixels. That's expected
Keep dragging farther, then while still dragging, go back over the same are you started the drag; there, the map will STOP moving again, until you quit that the tolerance zone. That's definitely not expected!

For touchscreen usage it's usually better to set an higher tolerance; and that makes the problem very apparent.
As @JackFrostStudios suggests, a solution would be to always return true in that function (or in the one calling it) once moving has started.
Hope this is clear!


Testing the new site

Play around with the new JDA website and see what bugs or improvements it might have/need.

When adding the new items to a collection, the user drags the entire bar containing the item. It would be better to have the user drag a small icon to the collection rather than the entire bar.

On Microsoft Edge, if I refresh the page, it shows code instantly but then renders to the appropriate content.

When I switch from English to Japanese (and vice versa) I am redirected to the home page instead of the page that I was originally on. It might be better to simply render the Japanese version of the page the user is just on.

When I try to use the bookmarklet, some view source tag moves along with my text. It doesn't have any sort of functionality from what I can see. Is this intentional?

@jcuanm Thank you for testing the new site. These are all good comments that the developer should be aware of. I just sent you an invitation to our renewal project's BaseCamp site and you can post your comments in there instead of GitHub from now on. Thanks!


Create a new release is documented as Draft a new release for GHE 2.21

What article on docs.github.com is affected?

What part(s) of the article would you like to see updated?
Currently docs show this:

But our GHE Server 2.2.1 shows this:

Additional information
Have a great day!

@peteraritchie - thanks for letting us know about this discrepancy.
It looks as if you're referring to step 3 in "Creating a release" in this topic: Managing releases in a repository - GitHub Docs.

@peteraritchie - thanks for letting us know about this discrepancy.
It looks as if you're referring to step 3 in "Creating a release" in this topic: Managing releases in a repository - GitHub Docs.

Ah - just realized that you have a pull request open for this issue and that the discussion is ongoing there.
Thanks 😄 I'll add a link from the PR to this issue to make it clearer that this is in progress.

Ah - just realized that you have a pull request open for this issue and that the discussion is ongoing there.
Thanks 😄 I'll add a link from the PR to this issue to make it clearer that this is in progress.

After looking at the suggested changes, unfortunately I have to say that the process to update images for previous versions of GitHub Enterprise Server requires us to log into some internal tools, so we'll need to take care of this one.

After looking at the suggested changes, unfortunately I have to say that the process to update images for previous versions of GitHub Enterprise Server requires us to log into some internal tools, so we'll need to take care of this one.

Closing in favor of an internal issue.

Closing in favor of an internal issue.


About the configuration of waypoints_nav program

@DaikiMaekawa Hello,Mr. DaikiMaekawa, after running the waypoints_nav program, do I still need to run move_base?

At the same time, I use the handle to control the robot to build the map, so how do I need to modify my handle program to match this package? Below is my handle program and launch file：
`
#!/usr/bin/python
#coding=utf-8
import time
import rospy
from sensor_msgs.msg import Joy
from geometry_msgs.msg import Twist
class Joy360:
def init(self):
self.__line_x = 0
self.__angle_z = 0
self.__pub_cmd_vel = None #:
self.__pub_can_vel = None
self.__start = False
rospy.init_node("joy")
rospy.Subscriber("joy",Joy,self.joy_callback)
#self.__pub_cmd_vel = rospy.Publisher("/cmd_vel",Twist,queue_size=100)
self.__pub_cmd_vel = rospy.Publisher("/joy/cmd_vel",Twist,queue_size=100)
def joy_callback(self,data):
    if data.buttons[10] == 1:
        self.__start = not self.__start
    self.__line_x = data.axes[1]*0.3
    self.__angle_z = data.axes[3]*0.3

def start(self):
    rospy.loginfo("init node ok!!")
    try:
        while not rospy.is_shutdown():
            #time.sleep(0.01)
            cmd= Twist()
            cmd.linear.x=self.__line_x
            cmd.angular.z=self.__angle_z
            if self.__start:
               self.__pub_cmd_vel.publish(cmd)
    except KeyboardInterrupt as e:
         rospy.loginfo("quit by user " + str(e))

if name=="main":
joy_ins = Joy360()
joy_ins.start()`

@ju-mingyue Yep, you need to run move_base as waypoints_nav internally calls it unless your robot's system already provides a compatible interface.

@DaikiMaekawa  Hello, how does my controller post topics to the waypoints_saver file? Do I need to post a topic of handle buttons in the program?


[FLINK-14114] [client] Shift down ClusterClient#timeout to RestClusterClient

What is the purpose of the change
*ClusterClient#timeout is only used in RestClusterClient. Shifting it down to RestClusterClient could be a right step towards an interface-ized ClusterClient. *
Brief change log

timeout field is moved from ClusterClient to RestClusterClient

Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:

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

Documentation

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

@flinkbot run travis

resolved conflict on master. Merged once travis gives green.

Sorry for the late response which cause this PR should be rebased onto 949776bb8a8c326368bf7773becb8200610d5379. Could you please update @zhuzhurk?

Sorry for the late response which cause this PR should be rebased onto 949776b. Could you please update @zhuzhurk?

Thanks for the reminding!
I have just rebased this PR onto master and resolved the conflicts, which are caused by the scala Duration replacing.


Openmemories tweak not working on sony A7 m1.

Hi I have seen a few posts about the openmemories tweak not working on certain cameras but there is no resolution to them, so i hope someone can give me a solution to this problem.. thank you.. i have checked to disable time limit for recording but the camera still stops recording at the 29 minute.

same here.


Spurious nans found when using jax_debug_nans.

I am currently trying to figure out why the gradient of an energy minimization routine in jax-md returns nans by using jax_debug_nans but I am getting some funny errors when doing that.
This scan includes evaluating a force which is the gradient of an energy function.
force_fn = grad(energy_fn)

Now force_fn(x) produces nans if and only if jax_debug_nans is set to True.  jit(force_fn)(x) on the other hand always works out fine.
I have tried to extract the relevant parts from jax-md into a colab notebook.
https://colab.research.google.com/drive/1CYtaYI7N0vOcLN_O1RrnrspOKvlKK9Z2?usp=sharing
I believe the nans I am getting in my scan are unrelated to this issue here.

It appears that force_fn is producing NaNs internally, but not in a way that affects the final output. I didn't look at your computation in detail to figure out how exactly this is the case, so not sure if this is expected or not, or if the internal NaN is affecting your scan.
Maybe it'd be useful in this case to log all NaNs without halting execution? You'll probably get a lot of logging, but if you start at the top maybe you can figure out what's going on. Probably the quickest way to do this is to install jax from github and make the modification yourself.
To install from github:
git clone https://github.com/google/jax
cd jax
pip install --upgrade -e .

Then modify xla.py:385 to print instead of raising an exception, something like:
    if FLAGS.jax_debug_nans and np.any(np.isnan(buf.to_py())):
      print(f"invalid value (nan) encountered in {name}")
      import traceback; traceback.print_stack()
      return

Hope this helps!

If I do that I get the following traceback, which doesn't seem to tell me where the issue lies.
invalid value (nan) encountered in mul
  File "/Users/Maxi/IST/maxi/nan.py", line 69, in <module>
    print("force: ", force_fn(R))
  File "/Users/Maxi/IST/maxi/jax/jax/_src/traceback_util.py", line 139, in reraise_with_filtered_traceback
    return fun(*args, **kwargs)
  File "/Users/Maxi/IST/maxi/jax/jax/api.py", line 742, in grad_f
    _, g = value_and_grad_f(*args, **kwargs)
  File "/Users/Maxi/IST/maxi/jax/jax/_src/traceback_util.py", line 139, in reraise_with_filtered_traceback
    return fun(*args, **kwargs)
  File "/Users/Maxi/IST/maxi/jax/jax/api.py", line 811, in value_and_grad_f
    g = vjp_py(np.ones((), dtype=dtype))
  File "/Users/Maxi/IST/maxi/jax/jax/api.py", line 1798, in _vjp_pullback_wrapper
    ans = fun(*args)
  File "/Users/Maxi/IST/maxi/jax/jax/interpreters/ad.py", line 121, in unbound_vjp
    arg_cts = backward_pass(jaxpr, consts, dummy_args, cts)
  File "/Users/Maxi/IST/maxi/jax/jax/interpreters/ad.py", line 228, in backward_pass
    **eqn.params)
  File "/Users/Maxi/IST/maxi/jax/jax/interpreters/ad.py", line 497, in bilinear_transpose
    out = lhs_rule(cotangent, y, **kwargs)
  File "/Users/Maxi/IST/maxi/jax/jax/_src/lax/lax.py", line 349, in mul
    return mul_p.bind(x, y)
  File "/Users/Maxi/IST/maxi/jax/jax/core.py", line 282, in bind
    out = top_trace.process_primitive(self, tracers, params)
  File "/Users/Maxi/IST/maxi/jax/jax/core.py", line 628, in process_primitive
    return primitive.impl(*tracers, **params)
  File "/Users/Maxi/IST/maxi/jax/jax/interpreters/xla.py", line 319, in apply_primitive
    return compiled_fun(*args)
  File "/Users/Maxi/IST/maxi/jax/jax/interpreters/xla.py", line 462, in _execute_compiled_primitive
    check_special(prim, out_bufs)
  File "/Users/Maxi/IST/maxi/jax/jax/interpreters/xla.py", line 485, in check_special
    _check_special(prim.name, buf.xla_shape(), buf)
  File "/Users/Maxi/IST/maxi/jax/jax/interpreters/xla.py", line 495, in _check_special
    traceback.print_stack()

I have taken another look at it and I am pretty sure that the issue is caused by either the distance function, or more likely the safe_mask function because if I jit either of them no nans are found. There is a long thread here #1052 about the perils of differentiating jnp.where but my safe_mask function should prevent exactly that.
Having said that I am always going to jit my energy and my force function so this should not be an issue in practice. I am simply wondering what exactly is going wrong.

@mattjj do you have any ideas?

I'd guess this is working as intended. jax_debug_nans reports if any NaNs are produced as outputs from a computation. It doesn't have a way to distinguish between benign NaNs that you later mask out and NaNs that are dangerous. It's a debugging tool, and has its limitations!
Since the nan-debugging only ever looks at the outputs of a computation, if you use a jit to "enclose" the NaNs and their masking, then the NaN debugging tool won't detect them.

Thanks for the quick answer.


Adds a settle argument to tTestWidgets.

Fixes #272
Adds a flag to tTestWidgets to control whether pumpAndSettle() or pump() is called.

@all-contributors please add @ronba for code


Versioning differences podman v/s python-podman

Continuing IRC discussion here..
python-podman has its own version. This will be painful as far as distro packaging goes, so I suggest any code with its own version be an independent upstream and thus an independent distro package.
@rhatdan @jwhonce @baude @mheon thoughts? ^

If they are going to be independent then fine. But why are they going to have different versions?  Seems simpler to keep them the same?

@jwhonce would prefer they be separate, given that the Python bindings could be changed independently of Podman and libpod (multiple releases for a single release of Podman for example)

If we do that I think they should move to totally different Repos then.  My concern is we end up with  a test matrix.  If I update podman and there is no new version of python3-podman, will python3-podman break?

My concern was version #  gaps if we start pushing content to places like pypi.  We can state that all versions are pushed even if the client content doesn't change.  Then having one version number won't confuse people.

Right now, we're just doing timed releases, with no guarantees of any sort of stability...

From the SemVer spec:

Major version zero (0.y.z) is for initial development. Anything may change at any time. The public API should not be considered stable.

So you can adopt SemVer, stick to 0.x.y as long as you like, and basically do whatever you want (although personally I like to use the minor release number to mark pre-1.0 breaking changes).  Once you're comfortable with stability, you can cut a 1.0.0 and start being more careful.

we have agreement on how this works. ... versioning change/split when we cut podman-1.0.  at that time, the python code will also go to a different repo.


tui editor  printed at table td tag

hi, guys.
i like tui editor
but.

content

how to br remove?

@pogus55 Thanks for the issue. But why are you using the table? If you used it for layout, it is better to use div instead of table.

So, Is there a way not showing br at tui editor in table when initialValue is empty ??
I have same case, sorry but can't change tags.


Fix file missing for php8

Fixes #5324
Because the version compatible with php 5.3 (1.19.0) require a file with a .php8 extension
https://github.com/symfony/polyfill/blob/ac41071c7ef43e26e1231100fa9a316cebecdec7/src/Mbstring/bootstrap.php#L115

Thank you @jderusse.

For anyone else stumbling upon this issue, this particular file with .php8 extension was removed in https://github.com/symfony/polyfill/commit/3880341374e890a909d53fd22df874683fcbba77, but it no longer supports PHP <7.1. Therefore there isn't an other way to do it than like here.


Chef16 fix

This fixes https://github.com/bmhatfield/chef-ulimit/issues/73 - it seems the instance_eval interface changed.... unstably.  Solve this by falling back to the old one if it fails.
It also adds the required provides entries

@tas50 I see you've merged the last few PRs to this repo. Any chance we can get some eyes on this? Thanks!


Type diagnostics on hover are wrong

It seems like the type diagnostics on hover are assuming my mouse to be on top of a completely different expression.
In the following screenshot I am hovering over the addEventListener but the type diagnostics say that i am hovering over Belt.Option. (Which is 5 rows above and to the right of where I am actually hovering).

Can you send a snippet or a repository so I can reproduce this?

I checked on a different pc and it seems to be working there.
I will close this for now and investigate a bit more, if i can consistently reproduce this.


OBT /UTC drift problem in an_downsample

Downsampling low frequency measurements
Error at loop step 28 or  foutarr{}(2701), file /data/rosetta/LAP_ARCHIVE/RO-C-RPCLAP-5-1601-DERIV-V0.9/2016/JAN/D19/RPCLAP_20160119_120205_914_I1L.TAB
ans =
'MATLAB:badsubscript'

ans =
'Index in position 1 exceeds array bounds (must not exceed 2700).'

an_downsample, 330,analysis, 93,rerunlapdog_test, 399,macrono1=802, 2=802

between OBT:
411825648.12102  and  411868717.38633
and UTC
'2016-01-19T12:02:10.598014'    '2016-01-19T23:59:59.992035'
an interval of 11.9637 hours,
there is a drift between UTC & OBT of 0.0108 seconds. There is simply a larger span of seconds in the OBT than an_downsample expects.
Because of this, several measurements in RO-C-RPCLAP-5-1601-DERIV-V0.9/2016/JAN/D19/RPCLAP_20160119_120205_914_I1L.TAB
end up on the wrong side of intervals, and more importantly, one or two measurements end up on the next day, triggering the error.
I guess fixing this error should be by converting OBT or UTC to ET via SPICE, and then doing the "inter" interval finding algorithm with this new time-vector.

Is still unresolved?

yep


UUID/ID of the security control

Will you add UUID/ID of the security control ? I would like to use it in MISP and CyCAT.org. Thank you very much.

Hi @adulau ,
Thanks for reaching out.  In regards to the UUID/ID, are there existing UUID/ID assignments for the controls (released by Microsoft), I performed a quick search and wasn't able to find any?  Or are you proposing, as part of this project, that we generate unique identifiers for the controls that we have mapped?
Thanks

Hi @nickamon Thanks for the feedback. Yes I would propose that your project generates unique identifiers. That would be awesome and also help you in case of renaming.

That's a good idea, we'll discuss it internally and triage.  Thanks!


Make sure the function vtables are initialized before use

From IRC:
[08:33]	hkaiser: K-ballo: could you review #2945, pls?
[08:34]	hkaiser: shouldn't take long
[08:38]	K-ballo: hkaiser: looks good
[08:39]	hkaiser: I was not sure if your intention was to make everything constexpr, which this patch would not allow
[08:40]	K-ballo: it can't be, because of the function registration
[08:41]	K-ballo: the non serializable vtables are constexpr, so that's a regression on them, but I don't know how to split the cases easily
[08:41]	hkaiser: right


[ccm] Use clusterName in generated cloud-config

If the entry in the cloud-config file doesn't match the name of the cluster, then CCM fails to start and throws an error.  To fix this, we use clusterName if specified, otherwise fall back to the previous default of openstack.

@yankcrime
I don't think .Values.clusterName is the right thing to use here. It is intended to match the actual name of the Cluster API cluster and is passed to the OCCM/CSI Cinder to allow it to tag OS resources as belonging to the cluster. This needs to work even if every credential uses openstack in the clouds.yaml.
I think we need a new field under .Values.openstack, e.g. .Values.openstack.cloudName, that can be used to control this.

I think I conflated a couple of things here since we're using a different Helm chart to deploy our clusters and I completely overlooked where this value originally came from.
I do think this should be configurable in this Helm chart though and not hardcoded as openstack, so I'll update this PR with your suggestion 👍


DuckDuckGo/OmniBar.swift: Use the Query in the Omnibar on DuckDuckGo.

Reviewer: @brindy
Asana: https://app.asana.com/0/193817002363848/462295454364963
CC:
Description:
Use the query in the omnibar when on DuckDuckGo instead of the URL.
Steps to test this PR:

open app
make search
see just the query!

Reviewer Checklist:

[x] Ensure the PR solves the problem
[x] Review every line of code
[x] Ensure the PR does no harm by testing the changes thoroughly
[x] Get help if you're uncomfortable with any of the above!
[ ] Determine if there are any quick wins that improve the implementation

PR DRI Checklist:

[ ] Get advice or leverage existing code
[ ] Agree on technical approach with reviewer (if the changes are nuanced)
[ ] Ensure that there is a testing strategy (and documented non-automated tests)
[ ] Ensure there is a documented monitoring strategy (if necessary)
[ ] Consider systems implications (Database connections, Grafana stats, CPU)

@brindy done, thanks. I started there, and unwrapped it :smile:.

Looks good, thanks :)


[sil] Move PostOrderFunctionInfo from SILOptimizer/Analysis/PostOrderAnalysis => SIL/PostOrder.h.

[sil] Move PostOrderFunctionInfo from SILOptimizer/Analysis/PostOrderAnalysis => SIL/PostOrder.h.
There is already precedence for doing this via DominanceInfo. The reason I am
doing this is that I need the ownership verifier to be able to be run in Raw SIL
before no return folding has run. This means I need to be able to ignore
unreachable code resulting from SILGen not inserting unreachables after no
return functions.
The reason why SILGen does this is to preserve the source information of the
unreachable code so that we can emit nice errors about unreachable code.
rdar://29791263

@swift-ci Please smoke test and merge

The test failure was due to the ownership verifier commit.

@swift-ci Please smoke test and merge

@swift-ci Please smoke test and merge

@swift-ci Please smoke test and merge

@swift-ci Please smoke test and merge


Notes about 1.0.0-beta.30

Adding notes about async vs. sync mode.
Adding placeholder for mocking transitions section.

I think we could also document wrapper.vm.$nextTick() as an interchangeable option to Vue.nextTick.

@JessicaSachs a bit about mocking transitions, 99% of the work was done by @hiendv , I hope you don't mind I used your example and sneaky transitionStub helper.
I'm excited to learn how Vue's <transition> works under the hood (have not used it much), and how we can let it work correctly in VTU as well.

@lmiller1990 It would be my honor. I've been using VTU for years but never had a chance (or time :rofl: ) to contribute back to the library. Glad you took my snippet which, to be honest, is kinda a skimmed version of the original by @eddyerburgh. I think the old component stubs could be a good start for you.

These docs will help provide guidance for 1.0.0-beta.30 migration-related issues

These docs will help provide guidance for 1.0.0-beta.30 migration-related issues


Add diagram snapshot tests for BBEs

Fixed with https://github.com/ballerina-platform/ballerina-lang/pull/14624

Need to verify each snapshot by viewing diagram for each BBE

Need to fix snapshot tests with gradle build

BBE verifications are done and found issues are reported to github

gradle build issue is tracked in https://github.com/ballerina-platform/ballerina-lang/issues/15344.
Hence, closing this issue.


Error pushing to registry: Authentication is required.

I am getting this error in docker automated build: https://registry.hub.docker.com/u/ronin/fstools/build_id/59112/code/bjwj8cryp2sc9ruzwhsdzmm/  - though it looks intermittent since a previous build was successful.
I see an older issue marked fixed https://github.com/docker/docker-registry/issues/995 (also noted at https://status.docker.com/pages/incident/533c6539221ae15e3f000031/554293d934de855a3800061b) but it seems like it is happening again but with docker registry automated builds.

I am also seeing this error in my automated build repository: https://registry.hub.docker.com/u/foodlogiq/api/build_id/37077/code/bklej8f97kynzupskwfysmq/
I will give it some time and try it again to see if I also see intermittent success.

@dmp42 I'm also hitting this error with one of my automated build repositories: https://registry.hub.docker.com/u/kaggle/r/build_id/53243/code/bvep6hoqrvyqyy69zmr2cx8/

Hi @ronin13 @ventres @benhamner
Automated builds is not the open-source python registry - it's a Hub feature.
I'm sorry to close this, but really there is nothing I can do here - this is definitely a Hub issue, that you should report directly to the support over here: https://support.docker.com


time: document that Local and UTC must not be modified

What version of Go are you using (go version)?

$ go version
go version go1.13.1 darwin/amd64

Does this issue reproduce with the latest release?
It's not reproducible every time.

Seems to be reproducible with MAX_PROCS > 2
What did you expect to see?
Nothing
What did you see instead?

WARNING: DATA RACE
Read at 0x000004186410 by goroutine 36:
  time.Now()
      /usr/local/Cellar/go/1.13.1/libexec/src/time/time.go:1100 +0xf5
  time.sendTime()
      /usr/local/Cellar/go/1.13.1/libexec/src/time/sleep.go:137 +0x44

Previous write at 0x000004186410 by main goroutine:
  [failed to restore the stack]

Goroutine 36 (running) created at:
  runtime.(*timersBucket).addtimerLocked()
      /usr/local/Cellar/go/1.13.1/libexec/src/runtime/time.go:169 +0x10d
  github.com/globalsign/mgo.newcoarseTimeProvider.func1()
      $HOME/go/pkg/mod/github.com/globalsign/mgo@v0.0.0-20181015135952-eeefdecb41b8/coarse_time.go:49 +0x50

or

WARNING: DATA RACE
Read at 0x000004186410 by goroutine 13:
  time.Now()
      /usr/local/Cellar/go/1.13.1/libexec/src/time/time.go:1100 +0xf5
  time.sendTime()
      /usr/local/Cellar/go/1.13.1/libexec/src/time/sleep.go:137 +0x44

Previous write at 0x000004186410 by main goroutine:
  [failed to restore the stack]

Goroutine 13 (running) created at:
  runtime.(*timersBucket).addtimerLocked()
      /usr/local/Cellar/go/1.13.1/libexec/src/runtime/time.go:169 +0x10d
  crypto/rand.(*devReader).Read()
      /usr/local/Cellar/go/1.13.1/libexec/src/crypto/rand/rand_unix.go:54 +0x884
  io.ReadAtLeast()
      /usr/local/Cellar/go/1.13.1/libexec/src/io/io.go:310 +0x98
  go.mongodb.org/mongo-driver/bson/primitive.readRandomUint32()
      /usr/local/Cellar/go/1.13.1/libexec/src/io/io.go:329 +0xc7
  go.mongodb.org/mongo-driver/bson/primitive.init()
      $HOME/go/pkg/mod/go.mongodb.org/mongo-driver@v1.1.1/bson/primitive/objectid.go:34 +0x95

and

WARNING: DATA RACE
Read at 0x00000417df90 by goroutine 12:
  time.Now()
      /usr/local/Cellar/go/1.13.1/libexec/src/time/time.go:1100 +0xf5
  time.sendTime()
      /usr/local/Cellar/go/1.13.1/libexec/src/time/sleep.go:137 +0x44

Previous write at 0x00000417df90 by main goroutine:
  [failed to restore the stack]

Goroutine 12 (running) created at:
  runtime.(*timersBucket).addtimerLocked()
      /usr/local/Cellar/go/1.13.1/libexec/src/runtime/time.go:169 +0x10d
  github.com/golang/glog.(*loggingT).flushDaemon()
      $HOME/go/pkg/mod/github.com/golang/glog@v0.0.0-20160126235308-23def4e6c14b/glog.go:882 +0x41

We can't provide the source code but a compiled go test -c binary for inspections. Downloadable on a private URL.

After figuring out how to bring back the main routine stack, the write occurs in an init function that sets the time.Local to the current location.

@urandom, is anything in your program mutating the time.Local variable?

@bcmills
As mentioned in the previous comment, an init function mutates time.Local.

@bcmills, while the doc change would be useful, actually mentioning the TZ env anywhere in the time package would have a greater effect. As it currently stands, even if you mention that one should not modify Local, a user will have no idea what to do to actually change the local TZ.

Sure, it seems reasonable to mention the use of TZ as part of the doc fix. 🙂

Hi I'm submitting a CL to improve the documentation as is requested in the issue.
However, I'm wondering if Local and UTC should not be changed, and also they are a copy of localLoc and utcLoc, respectively, to protect them from misbehaved clients. Wouldn't be better to have them as functions returning localLoc and utcLoc?
I know, right now it would break the compatibility rule. Nevertheless I'd like to raise this idea. Maybe create another function and recommend to use it instead of Local/UTC

I agree that it would be nice if there were a way to prevent these variables from being changed.  But language style is generally to use variables rather than functions where appropriate.  Given that we already have variables, and they do work, I don't see a strong justification for changing to functions.


[doc] Update CHANGELOG

In this PR, update CHANGELOG.md with the major changes covered in WasmEdge Rust SDK 0.10.0.

Hello, I am a code review bot on flows.network.
It could take a few minutes for me to analyze this PR. Relax, grab a cup of coffee and check back later. Thanks!

@L-jasmine Could you please review this PR? Thanks a lot!

@L-jasmine Thanks for the review!


Two feature ideas

1. AFK prevents phantom spawning.
2. New command like /noafk, which prevents to turn the player into auto-AFK mode.
Optional with custom tag next to the player name, as it is with AFK.

the /noafk is more interesting, but the "no phantom spawning" would be a bit more complicated.

And I'll get to this later; because I am currently hard at work on malilib & masa's other mods for the new snapshot's networking code.

Thanks for informing me, you got all the time 😄

When I use the /afk command, it shows 4 messages, the first two irritates me a bit.
Maybe you could remove that? I have OP rights, if that's matters.

In regards to your image, if you want to cut down on the messages you can disable features via your config, ie "resetOnMovement", or if you want to disable the "Invulnerable" announcers, set them to "" .

Check out the 1.4.6 release.

Let me know if there are additional issues.

Thanks for the detailed answer. Resetting the config was a good idea.
It's nice that you were able to add the phantom rule,
it is said to have happened that I stood AFK a little longer and was very surprised 😂😂😂

Your mod is super helpful - big THANKS! 😊


Create a mocking mechanism to VS Code Extension

As a Developer, I want to add a mocking mechanism to VS Code Extension so SDET can use it to mock responses running a plugin command.
Use case:  Running taq init command inside VS Code opens the dialogue box to select the folder that the automation test cannot bypass.  Need a solution to return a different response (skip opening dialogue box) to be able to test it. As a result, the test will focus on verifying mocked responses.

@michaelkernaghan for context


Added Frequently Asked Questions section to explain the repository language

Fix #29

Ich mag das! ❤


Token icon not always displayed

Description
Sometimes it happens that a token icon is not displayed even so we have an asset for it.
when you open an app we fetch tokens from relay service, but at the same time the balance tab tries to display tokens. It doesn’t find any -> fetches the data directly from blockchain without an icon.
We can fix it in a different ways:

The broad way - we need to improve how we fetch the data required for app to start initially. There are some improvements, because sometime we fetch data multiple times that can be fetched only once (for example last safe master contract version fetched everytime safe is fetched)
The fast way - we just fix this bug

Screenshots

SNX and GNO icons were available when the screenshot was taken

link to relevant discussion which touches a little bit how we load data in our app that should be required: https://gnosisinc.slack.com/archives/CQB729LLF/p1592168087016500

Looks good in prod. The tokens reported now have icons.
Also in the "Manage list" the vast majority of tokens have Icons (I've only seen 1 token without icon)


MasterDetailRelation

Hello, How many levels MasterDetailRelation work, at 3 level stop insert new entities for me, existe a way tha work on more levels?
Thanks...

Theorically it should work N levels, there is no limit, but as there is no actual record on DB, and you don't have an actual ID, there might be issues, i don't know.


Localization repos differ from main repo

Removed comment for repository url because it would require more localization effort

To be merged after 5pm

@SyntaxC4 - I was tagged, but you don't need me to sign off or anything, right?

@erhopf It's likely the code owners file.


Added Search Criteria Summary component

Added Search Criteria Summary component
Closed #75

This pull request introduces 1 alert when merging 0782f60fa81cf8d340a851032f5b086b3bff240c into 98b5d593a767818735bd65fe3855dae624cf7409 - view on LGTM.com
new alerts:

1 for Unused variable, import, function or class

Comment posted by LGTM.com

This pull request introduces 1 alert when merging bf109ce68116113525a19133063166ab5eacf50e into f0be4555be6b9d8b57a3caff3a6adb1bdd193f97 - view on LGTM.com
new alerts:

1 for Unused variable, import, function or class

Comment posted by LGTM.com

@JacOng17  I was a bit premature in approving this, the screen shot looked so good it blinded me, this is missing the file pages/index.js


F embedding

My apologies, this was created by accident. As I'm not able to remove this, I've removed all changed files and forced push the original version.


access log: added support to flush tcp access log periodically

Signed-off-by: wbpcode<EMAIL_ADDRESS>Commit Message: access log: added support to flush tcp access log periodically
Additional Description:
To close #23579
Risk Level: mid.
Testing: waiting.
Docs Changes: n/a.
Release Notes: n/a
Platform Specific Features: n/a.

I think this is what you want. And it should work and is compatible with exist implementation. cc @wu-sheng

cc @dio A draft is completed. 😸 I test it locally and it works. But may more detailed unit tests are necessary.

Yes, I think this would fix the gap. SkyWalking could run topology analysis with metrics using rate, as metrics are counter from the connection established.

Hi, @lizan, could you check the API again when you have free time? Thanks.

@lizan could you give this another look
/retest

/wait
This generally in the right track, will address #23838 first and then use that for stream id.

friendly ping @lizan

Added the substitution formatter for the stream id in this PR to avoid creating a separated PR for it.

/retest

friendly ping cc @lizan


[WIP] Change host from heroku to fly.io

Heroku seems to block an updated deploy through the datasette publish tool. Fly may be a better option trainingdata.securityforcemonitor.org.
Positives:

datasette publish fly subcommand Just Works
we already have the db and metadata established
test deploy was very simple, and the flyctl cli tools is nicely made

Unknowns:

not sure how to pass a few datasette variables (like query time limit and so on) thorugh the datasette publish fly subcommand
use and billing feel a bit opaque for fly and I'd like to know the likely monthly bill before committing (but highly likely not much)
DNS propagation of the CNAME record seems quite slow at this point

Fly woulnd't map to a CNAME cleanly
workaround for datasette publish heroku not supporting the --team flag is to set a default team. This resolved the deploy issue I was having
result: keep Heroku for now.


Restrict placing buildings (respect game rules)

depends on #9
Acceptance Criteria:

[x] Player clicks building it wants to place
[x] Player sees visual representation of building to be placed (can be anything) and gets feedback if it is ok to build there or not
[x] Player can place structure when terrain is rock or concrete
[x] Player can place structure nearby other (friendly) structures only
[x] Player cannot place structure on sand, walls, mountains, spice, hills, spice hills
[x] Player cannot place when too far away from other (friendly) buildings
[x] Prohibit placing buildings on top of existing buildings & units
[x] when units move beneath the structure to place, the state should reflect the unit movement

fixed by #135


update request version

fixes https://github.com/Mashape/unirest-nodejs/issues/93

Can we get this vulnerability closed? It's cascading into modules I depend on from this module.
@nijikokun maybe?

Can't wait.

:+1:

0.5.1 has been released :)


opae-sdk: (CP) update installation guide (#2650)

Signed-off-by: anandaravuri<EMAIL_ADDRESS>

Merging for Ananda


removeAllListeners does not remove listeners added with onAny

Unless I'm missing something, I expect that .removeAllListeners removes all listeners added with .onAny.
const ee = new EventEmitter2()

ee.onAny(() => console.log('hello was fired'))
setInterval(() => ee.emit('hello'), 500)

setTimeout(() => {
  ee.removeAllListeners()
  console.log('removed all listeners')
}, 1500)

Here's a "working" JSFiddle of the above code.
The above example continues to listen to hello events indefinitely, even though removeAllListeners is called after 1500ms.

Yeah, I think this is more of a documentation issue.
onAny acts as a special type of listener, and you need to use offAny in order to remove them.
If you want to remove everything you need to invoke ee.removeAllListeners() and ee.offAny().
Chaning this would be pretty breaking to existing codebases so I'd rather not modify the behaviour unless it was preventing you from doing something.
A PR to modify the README to talk mention that removeAllListeners doesn't work for onAny listeners and that you should use offAny with no arguments would be very welcome!

@RangerMauve I'm guessing adding an additional method that combines those 2 together would make the API convoluted?
Perhaps, offAll()?

Hmm, I'm not sure. One one hand it isn't strictly necessary, but it would be nice to have.
I think I'd rather wait for more input from other people before deciding. In the meantime, you could patch the prototype within your own projects if you want the feature.
EventEmitter.prototype.offAll = function () {
  this.removeAllListeners();
  this.offAny()
};


I extended your work to make a more generic version...

I saw your post in https://elixirforum.com/t/asdf-erlang-plugins-with-precompiled-erlang-for-ubuntu/40124 and realized that it could be adapted to support ARM builds which beam still doesn't support.
https://github.com/erlef/setup-beam/issues/179
I am happy to transfer https://github.com/cranksecurity/asdf-erlang-prebuilt-ubuntu to you if you would like to take it as its pretty much entirely based on your examples. I am not an active member of the ASDF, erlang or elixir community so have no plans to publicizes my extension of your work.
The biggest downside with what I did is that it won't handle non LTS releases - e.g. 23.04, etc - but at least you can specify your own version via an env flag.

Hey, very cool, thank you for sharing! I do not necessarily need it myself but can take in the repo to my account if you prefer that.


feat: Add support for creating cloudwatch log groups

Description
Add cloudwatch log group management.
Motivation and Context
Relates to: https://github.com/terraform-aws-modules/terraform-aws-redshift/issues/91
Breaking Changes
No.
How Has This Been Tested?

[x] I have updated at least one of the examples/* to demonstrate and validate my change(s)
[x] I have tested and validated these changes using one or more of the provided examples/* projects

[x] I have executed pre-commit run -a on my pull request

This PR is included in version 5.3.0 :tada:


using hololens-ex-60--loss-2.76.h5 to object detection error occurred

the code i want to run as follow:
from imageai.Detection import ObjectDetection

detector = ObjectDetection()
detector.setModelTypeAsYOLOv3()
detector.setModelPath('./model/hololens-ex-60--loss-2.76.h5')
detector.loadModel()

then consle show this
ValueError: Dimension 0 in both shapes must be equal, but are 1 and 18. Shapes are [1,1,1024,255] and [18,1024,1,1]. for 'Assign_360' (op: 'Assign') with input shapes: [1,1,1024,255], [18,1024,1,1].

how can i solve this problem?

The Hololens detection model is a custom model. There fore you should use
from imageai.Detection.Custom import CustomObjectDetection detector = CustomObjectDetection()
and not
from imageai.Detection import ObjectDetection detector = ObjectDetection() in your code.

See the  full code here.
https://gist.github.com/OlafenwaMoses/d399e61386fc4adb4e67e834cde50c00#file-custom_hololens_detection-py

The Hololens detection model is a custom model. There fore you should use
from imageai.Detection.Custom import CustomObjectDetection and detector = CustomObjectDetection()
and not
from imageai.Detection import ObjectDetection and detector = ObjectDetection() in your code.

thank you for your answer


Suspicious variable reference to stride

I keep getting the pictured error:

Upon investigation, I see that stride is referenced here but isn't defined prior in the method.  Can you please explain if this is intended or a bug?
Thanks

Hmm, weird --- what's the context? Are you running out of GPU memory by any chance?
Also, stride happens to indeed be defined.
            buffers[device] = [torch.zeros(max_bsize, stride, self.dim, dtype=dtype,                                           device=device, pin_memory=(device == 'cpu'))                               for stride in self.strides]

It's the for stride in self.strides.

Sorry about that, my mistake :)
But regarding the error, I'm definitely not running out of gpu memory, because these tests are being run on a very small index.

No worries! Could you share more info, like commands or data details?
Also I just pushed a minor change. See if that makes a difference!

Also, your error says line 57 but is around line 52. Is the code changed?

I added some print statements for debugging purposes, which is why the line number is different.
I made a small index for the purpose of testing the full reranker against my own reranker, since the two are giving different results and I am trying to debug.  Technically, my official code does not use the IndexRanker at all, but this issue is still relevant for my debugging and the work of others.  Weirdly, this issue only arises like half the time.  You can see below that a first instantiation of IndexPart works, while the second identical instantiation throws the error.

Is this the first time you use this code? Or did it work before?

No, I have used score_by_range several times, which uses IndexPart

To your point, I never got this error until I started testing by instantiating an IndexRanker directly.  Do you think there's some environment variable or something that goes awry when I do this?

Oh! You're using the API directly, not the command line?
Isn't that something that deserves to be mentioned upfront in the post haha? Certainly this is connected to the error yes.

Could you show me how you create the object, etc.? Also can you check for no errors if you use the standard way?

Sorry, I should've been more explicit.  See the above error for an example of how I create an IndexPart object, which throws the error about 50% of the time.
For a bit of feedback, I don't find the command line scripts particularly useful for use of the repo as part of a larger task.  The scripts are useful for building the index itself, but I would prefer to call retrieval and reranking from python code.  In general, this repo seems to be written in such a way that the end user is merely observing that ColBERT works, not for extending ColBERT into a stack that does retrieval and then uses the retrieved results to do other things.  I wish it was written more like an API, where the retrieval and reranking scripts were transformed into, say, python classes, where you can instantiate a retriever-reranker, then call .retrieve(query_text: str, n_docs: int) to get n_docs relevant pids given the query.  That would be perfect for my use case.

I wish it was written more like an API, where the retrieval and reranking scripts were transformed into, say, python classes, where you can instantiate a retriever-reranker, then call .retrieve(query_text: str, n_docs: int) to get n_docs relevant pids given the query.

Indeed, that's a goal of mine too!  I think you can do this now but it's challenging.  I know of a few cases where people are doing this currently.
That said, if you want to help contribute to changing up the API, I'd love to collaborate on that.
In the meanwhile, happy to help as you try to use the current setup. You should start from colbert/ranking/retrieve.py and just tweak the loop linked from the README so it uses your own queries. That works for people!

Regarding whether I get no errors the standard way, I have been running the standard way all day with no error that I can recall.

That said, if you want to help contribute to changing up the API, I'd love to collaborate on that.

I think I would be up for contributing, assuming we decide to stick with ColBERT (I think we will)

In the meanwhile, happy to help as you try to use the current setup. You should start from colbert/ranking/retrieve.py and just tweak the loop linked from the README so it uses your own queries. That works for people!

Yes, I'm doing something fairly similar currently, which works end-to-end.  That said, I often want to query once at a time, which inspired a separate issue I submitted last week.  This isn't very feasible given I can't load the data into memory.  Because of that, I ended up having to implement a second reranking task, for reranking not-en-masse, that largely doesn't rely on this repo (which I am currently testing against the repo's reranking, leading to this current thread).

I have narrowed down the problem a lot:
I get the error in the following situation:

You can see that the error doesn't arise when pin_memory=False, so it seems pin_memory can't be true on my machine for a tensor of that size.  (note: I have verified that pin_memory=True runs successfully for a smaller first dimension size)
I'm not sure it's necessary to set that first dimension to 1<<14.  It seems like overkill in many cases.  Do you agree?

This isn't very feasible given I can't load the data into memory.

That seems to be the root of your problems. Have you checkout our quantization stuff?
One recent thing (inspired by BPR paper, to appear at ACL'21) is that we found the ColBERT vectors to retain almost all of their quality if you just keep the sign of each dimension without any other changes. Basically, for each vector, keep 128 bits with +1 if positive and -1 [not zero] if negative. Do this just for the document side, and keep the query side as usual. Do this after you have already constructed the FAISS index from uncompressed embeddings. Interestingly, you will preserve almost all of the quality of ColBERT but the index is 16x smaller.

I'm not sure it's necessary to set that first dimension to 1<<14. It seems like overkill in many cases. Do you agree?

Yes, it's overkill for most! Smaller would be fine!

I have things working properly now, so thank you for your help!  The only remaining issue is that my fast single-query retrieval-reranking method uses .reconstruct(id), which gives an approximate vector.  This means my scores are slightly off from what the repo returns.  This is only the case because of the product quantization, which I guess is something I have to live with (or maybe we can add handling for it in the api).
A couple more things that would be good in the interfacing class for the api (i am probably happy to help):
(1) ability to turn off those print statements, or perhaps connect them to upstream logging level
(2) fast single-query retrieval, like the one i implemented
(2) like i said above, ability to use regular ivf instead of ivfpq so that the fast single method can be exact


Build release app ios be struct.

Description
Build IOS Archive bi error warning in here...
React Native version: 0.63.1, 0.63.2
Steps To Reproduce
Provide a detailed list of steps that reproduce the issue.

Product > Archive

It'd be helpful if you provided more context, eg. the env info, the actual build command, some more of the build output etc..

This is the reason:
https://github.com/facebook/react-native/pull/29477
Pr is raised for this, we need to merge it ASAP


Is this library still maintained?

if not, can you reccomend another library?

@skynet unfortunately no as I haven't been using it myself for quite a few years now. Did you try it though and found any issues? Can you please report those and hopefully someone can jump in and contribute. Thank you

Haven't started yet, but will do. I was just searching for a good library. Are there all Feedly methods available with this library? Thanks again.

@skynet Unfortunately, I don't really remember. You can check the README file to see the available methods. Please do at least give it a try and let us know what you have found.

I'll definitely give it a try. Closing this for now.


Use extract-zip instead of decompress-zip

not maintained anymore (https://github.com/bower/decompress-zip/pull/53)
extract-zip has less dependencies.

What do you think? I can prepare pull request if you don't mind.
It is important for me since asar uses mksnapshot.

Is there something broken in decompress-zip? Something it isn't doing that it should?

My concern is only mentioned https://github.com/bower/decompress-zip/pull/53
electron-builder uses electron-packager,
electron-packager uses asar,
asar uses mksnapshot,
mksnapshot uses decompress-zip
decompress-zip maintainers don't publish new version and ignore PR https://github.com/bower/decompress-zip/pull/53
As result, users of electron-packager/electron-builder get warning "graceful-fs version 3 and before will fail on newer node releases. Please update to<EMAIL_ADDRESS>as soon as possible." (and increased number of node dependencies).

Yes. I encounter this problem also whereby I will get the warnning "graceful-fs version 3 and before will fail on newer node releases. Please update to<EMAIL_ADDRESS>as soon as possible." (and increased number of node dependencies)"
When I type "npm run pack" I got an error saying:
C:\node_modules\electron-builder\out\build-cli.js:5
const builder_1 = require("./builder");
^^^^^
SyntaxError: Use of const in strict mode.
at exports.runInThisContext (vm.js:73:16)
at Module._compile (module.js:443:25)
at Object.Module._extensions..js (module.js:478:10)
at Module.load (module.js:355:32)
at Function.Module._load (module.js:310:12)
at Function.Module.runMain (module.js:501:10)
at startup (node.js:129:16)
at node.js:814:3
Does this error related to the graceful-fs not update?

@ahgan84 Your issue is different, please ensure that you use NodeJS version 4+.

Since https://github.com/bower/decompress-zip/pull/53 was merged, can you please upgrade to decompress-zip 0.3.0?

Fixed by #4


texlive: generate fmtutil.cnf

Motivation for this change
This is a necessary piece towards fixing #101405: we need an accurate fmtutil.cnf to ensure texlinks generates links only for the installed formats (see https://github.com/NixOS/nixpkgs/issues/101405#issuecomment-714838611).
Bonus side effect: we can drop || true from the fmtutil call in texlive.combine (this also works as test that the file is generated correctly).
To fix #101405, one should also remove the symlinks from texlive.bin.core but I don't know how to do that.
For good measure, I have added a test that we do not miss any format in fmtutil.cnf.
Cc @veprbl
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[X] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Relase 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

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 130041 at e40614da run on x86_64-linux 1

1 package marked as broken and skipped:

spark

56 packages skipped due to time constraints:

adapta-gtk-theme
asymptote
autofs5
bibletime
ccache
ccacheStdenv
ccacheWrapper
clevis
denemo
digikam
...

56 packages built successfully:

R
apostrophe
asciidoc-full
asciidoc-full-with-plugins
auctex
btrbk
cddlib
chrome-gnome-shell
dblatex
dblatexFull
diffoscope
disorderfs
dot2tex (python38Packages.dot2tex)
dwarf-therapist (dwarf-fortress-packages.dwarf-therapist)
dwarf-fortress-packages.dwarf-therapist-original
frescobaldi
gnome.gnome-session (gnome.gnome_session)
gnome.gnome-shell (gnome.gnome_shell)
gnome.gnome-tweaks (gnome.gnome-tweak-tool)
gnomeExtensions.easyScreenCast
gnomeExtensions.gsconnect
gnomeExtensions.night-theme-switcher
gp2c
rep (kakounePlugins.rep)
lcalc
lilypond
luksmeta
manim
modem-manager-gui
ne
nuweb
paperwork
pari
perl532Packages.Po4a
postgresqlPackages.plr (postgresql11Packages.plr)
python38Packages.cnvkit
python38Packages.cysignals
python38Packages.pypandoc
python38Packages.sphinxcontrib-bayesnet
python38Packages.sphinxcontrib-tikz
python39Packages.cysignals
python39Packages.dot2tex
python39Packages.pypandoc
python39Packages.sphinxcontrib-bayesnet
python39Packages.sphinxcontrib-tikz
solfege
tang
texlive.combined.scheme-basic
texlive.combined.scheme-context
texlive.combined.scheme-full
texlive.combined.scheme-infraonly
texlive.combined.scheme-medium
texlive.combined.scheme-minimal
texlive.combined.scheme-small
udiskie
zettlr

@GrahamcOfBorg build tests.texlive


Added support for autocomplete in Zsh and clink solving #142 and #190

Added support for autocomplete in Zsh and clink solving #142 and #190

Coverage remained the same at 100.0% when pulling 786b75eed75a31996a0360bfc0ae915bec1a2c7a on waldekmastykarz:completion-lua into a0b98c7d24b6b33b1644fc7aa43fca014c97a5f8 on SharePoint:dev.


Linking to cloud does not work using Firefox

I just started using draw.io, and I can't get it to link with my google account on Firefox. It works for me using Chrome. If it matters, my gmail account has 2fa. Thanks.
System info
OS: Ubuntu
Browser: Firefox 58.0.1

Could I get you to post on https://groups.google.com/forum/#!forum/drawio please? This is for dev questions, thanks.


Redirect feature

With gen3 devices is mandatory to use port 80...
so i have to use a different port for my webserver for example port 8080.
with this mod if add after the line:
fauxmo.setPort(80); // This is required for gen3 devices
this one
fauxmo.setRedirect(8080); //redirect everything not found to port 8080
all calls to fauxmoesp that is not processed will be redirected to port 8080

This looks good, and is a great idea!
I'll try to do a test tonight or tomorrow and merge it.
Thanks!

Sorry i found a error in file src/templates.h
line 43 correct is:
""

I think that the best solution is using redirect HTTP status code and Location header
https://developer.mozilla.org/en-US/docs/Web/HTTP/Redirections


mj-body isn't stylable but the style manager still contains options for it.

I am trying to remove the decorations tab from the style manager. Is there a default set that I have to override? I used the unstylabe and stylable properties in the component. It had no effect. Am I missing something?

same issue

Only the width/backgroud color is stylable for mj-body since that is was is supported by mjml, could you try the latest version and reopen an issue if this is still happening?


Replace dot with comma

Between two "á" you have the dot (.) but there should be a comma (,):
YOU HAVE  : Consider the string instances "a", "á". "á", and "👩🏽🚒".
SHOULD BE: Consider the string instances "a", "á", "á", and "👩🏽🚒".

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

ID: a6cf7421-fbd2-0ca0-7385-4df65531fd66
Version Independent ID: d53a0764-9f27-16b3-c40a-9627dd1bcc0d
Content: Introduction to character encoding in .NET
Content Source: docs/standard/base-types/character-encoding-introduction.md
Product: dotnet
GitHub Login: @adegeo
Microsoft Alias: adegeo

Do you want to submit a PR to fix this? Here is how.

I just did pull request. Never done it before for Microsoft documentation, thank you for your suggestion!


Compile the benchmark suite with swift version 5

@swift-ci Please smoke benchmark

@swift-ci Please smoke test

Performance: -O

TEST
OLD
NEW
DELTA
RATIO

Regression

DataAppendDataLargeToLarge
37200
50800
+36.6%
0.73x (?)

Improvement

RangeIterationSigned
200
171
-14.5%
1.17x

Added

BinaryFloatingPointConversionFromBinaryInteger
22
23
22
—

RangeIterationSigned64
171
172
171
—

RangeIterationUnsigned
171
173
172
—

Code size: -O

TEST
OLD
NEW
DELTA
RATIO

Regression

RangeIteration.o
1700
3206
+88.6%
0.53x

BinaryFloatingPointConversionFromBinaryInteger.o
26502
30043
+13.4%
0.88x

Performance: -Osize

TEST
OLD
NEW
DELTA
RATIO

Regression

CharacterLiteralsLarge
100
111
+11.0%
0.90x (?)

Added

BinaryFloatingPointConversionFromBinaryInteger
27
28
27
—

RangeIterationSigned64
171
174
173
—

RangeIterationUnsigned
171
173
172
—

Code size: -Osize

TEST
OLD
NEW
DELTA
RATIO

Regression

RangeIteration.o
1770
3068
+73.3%
0.58x

BinaryFloatingPointConversionFromBinaryInteger.o
25846
29363
+13.6%
0.88x

Performance: -Onone

TEST
OLD
NEW
DELTA
RATIO

Regression

ObjectiveCBridgeStubToNSDate2
1234
1336
+8.3%
0.92x (?)

Improvement

ExclusivityIndependent
84
73
-13.1%
1.15x (?)

Added

BinaryFloatingPointConversionFromBinaryInteger
3856
4493
4070
—

RangeIterationSigned64
78266
78665
78408
—

RangeIterationUnsigned
75184
76186
75708
—

✅
Benchmark Check Report

⚠🔤
BinaryFloatingPointConversionFromBinaryInteger name is composed of 7 words.  Split BinaryFloatingPointConversionFromBinaryInteger name into dot-separated groups and variants. See http://bit.ly/BenchmarkNaming

⛔🔤
BinaryFloatingPointConversionFromBinaryInteger name is 46 characters long.  Benchmark name should not be longer than 40 characters.

How to read the data
The tables contain differences in performance which are larger than 8% and
differences in code size which are larger than 1%.
If you see any unexpected regressions, you should consider fixing the
regressions before you merge the PR.
Noise: Sometimes the performance results (not code size!) contain false
alarms. Unexpected regressions which are marked with '(?)' are probably noise.
If you see regressions which you cannot explain you can try to run the
benchmarks again. If regressions still show up, please consult with the
performance team (@eeckstein).

Hardware Overview
  Model Name: Mac Pro
  Model Identifier: MacPro6,1
  Processor Name: 12-Core Intel Xeon E5
  Processor Speed: 2.7 GHz
  Number of Processors: 1
  Total Number of Cores: 12
  L2 Cache (per Core): 256 KB
  L3 Cache: 30 MB
  Memory: 64 GB

Can one of the admins verify this patch?

Please update the base branch to main by Oct 5th otherwise the pull request will be closed automatically.

How to change the base branch: (Link)
More detail about the branch update: (Link)


move stuff to Details namespace

@vhvb1989 This test case is unstable, can you please take a look?
71: [  FAILED  ] TransportAdapter.connectionPoolTest (191604 ms)
71: [----------] 1 test from TransportAdapter (191604 ms total)
71:
71: [----------] Global test environment tear-down
71: [==========] 1 test from 1 test suite ran. (191604 ms total)
71: [  PASSED  ] 0 tests.
71: [  FAILED  ] 1 test, listed below:
71: [  FAILED  ] TransportAdapter.connectionPoolTest
71:
71:  1 FAILED TEST
 71/114 Test  #71: azure-core.TransportAdapter.connectionPoolTest ...........................***Failed  191.64 sec

@vhvb1989 - why is the connection pool test failing?
https://dev.azure.com/azure-sdk/public/_build/results?buildId=611333&view=logs&j=5f43df56-f144-584b-8cac-2916b6897a0a&t=a63c70f6-59e4-531a-efba-82f28f72650d&l=2067
71: Test command: D:\a\1\s\build\sdk\core\azure-core\test\ut\Debug\azure-core-test.exe "--gtest_filter=TransportAdapter.connectionPoolTest"
71: Test timeout computed to be: 10000000
71: Note: Google Test filter = TransportAdapter.connectionPoolTest
71: [==========] Running 1 test from 1 test suite.
71: [----------] Global test environment set-up.
71: [----------] 1 test from TransportAdapter
71: [ RUN      ] TransportAdapter.connectionPoolTest
71: Running Connection Pool Cleaner Test. This test takes more than 3 minutes to complete.
71: Add compiler option -DRUN_LONG_UNIT_TESTS=OFF when building if you want to skip this test.
71: First wait time done. Validating state.
71: D:\a\1\s\sdk\core\azure-core\test\ut\transport_adapter.cpp(98): error: Expected equality of these values:
71:   Http::CurlConnectionPool::ConnectionsOnPool("httpbin.org")
71:     Which is: 1
71:   2
71: [  FAILED  ] TransportAdapter.connectionPoolTest (191604 ms)
71: [----------] 1 test from TransportAdapter (191604 ms total
...
The following tests FAILED:
	 71 - azure-core.TransportAdapter.connectionPoolTest (Failed)

/azp run cpp - storage

/azp run cpp - storage

@Jinming-Hu - pull from master to get CI to be green. It is currently failing because one of the links had their cert expire and now is invalid. @vhvb1989 removed it here: https://github.com/Azure/azure-sdk-for-cpp/pull/935

@Jinming-Hu - pull from master to get CI to be green. It is currently failing because one of the links had their cert expire and now is invalid. @vhvb1989 removed it here: #935

customers still want to use base64 encoding/decoding functions for MD5/CRC64


remove pyDOE package from contrib and install it instead

Pull Request Description
What issue does this change request address?
#2294
What are the significant changes in functionality due to this change request?
Remove pyDOE contrib, and adds it as a dependency.

For Change Control Board: Change Request Review
The following review must be completed by an authorized member of the Change Control Board.

[x] 1. Review all computer code.
[x] 2. If any changes occur to the input syntax, there must be an accompanying change to the user manual and xsd schema. If the input syntax change deprecates existing input files, a conversion script needs to be added (see Conversion Scripts).
[x] 3. Make sure the Python code and commenting standards are respected (camelBack, etc.) - See on the wiki for details.
[x] 4. Automated Tests should pass, including run_tests, pylint, manual building and xsd tests. If there are changes to Simulation.py or JobHandler.py the qsub tests must pass.
[x] 5. If significant functionality is added, there must  be tests added to check this. Tests should cover all possible options.  Multiple short tests are preferred over one large test. If new development on the internal JobHandler parallel system is performed, a cluster test must be added setting, in  XML block, the node <internalParallel> to True.
[x] 6. If the change modifies or adds a requirement or a requirement based test case, the Change Control Board's Chair or designee also needs to approve the change.  The requirements and the requirements test shall be in sync.
[x] 7. The merge request must reference an issue.  If the issue is closed, the issue close checklist shall be done.
[x] 8. If an analytic test is changed/added is the the analytic documentation updated/added?
[x] 9. If any test used as a basis for documentation examples (currently found in raven/tests/framework/user_guide and raven/docs/workshop) have been changed, the associated documentation must be reviewed and assured the text matches the example.

Job Mingw Test on 84ae328 : invalidated by @joshua-cogliati-inl
Failed fetch and branch

Job Test qsubs sawtooth on 84ae328 : invalidated by @joshua-cogliati-inl
FAILED: Diff tests/cluster_tests/AdaptiveSobol/test_parallel_adaptive_sobol

@joshua-cogliati-inl: Please draft an email about the library update to raven users.

@joshua-cogliati-inl: Please draft an email about the library update to raven users.

Email sent.

[like]  Congjian Wang reacted to your message:

From: Joshua J. Cogliati @.>
Sent: Tuesday, April 16, 2024 3:02:50 PM
To: idaholab/raven @.>
Cc: Congjian Wang @.>; State change @.>
Subject: [EXTERNAL] Re: [idaholab/raven] remove pyDOE package from contrib and install it instead (PR #2298)
@joshua-cogliati-inlhttps://github.com/joshua-cogliati-inl: Please draft an email about the library update to raven users.
Email sent.
—
Reply to this email directly, view it on GitHubhttps://github.com/idaholab/raven/pull/2298#issuecomment-2059311310, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABX3L34RL64NMDUBIF57THLY5U4RVAVCNFSM6AAAAABGHUTC36VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANJZGMYTCMZRGA.
You are receiving this because you modified the open/close state.Message ID: @.***>


cool project, but ...

yanyiwu@yanyiwudeMacBook-Air /Users/yanyiwu/code/blog/_posts                                                             master
⚡ go version
go version go1.5.1 darwin/amd64

yanyiwu@yanyiwudeMacBook-Air /Users/yanyiwu/code/blog/_posts                                                             master
⚡ go get -u github.com/miguelmota/cointop

# github.com/gizak/termui
../../../golang/src/github.com/gizak/termui/render.go:107: not enough arguments in call to stack.ParseDump
../../../golang/src/github.com/gizak/termui/render.go:112: undefined: stack.Palette
../../../golang/src/github.com/gizak/termui/render.go:113: undefined: stack.SortBuckets
../../../golang/src/github.com/gizak/termui/render.go:113: undefined: stack.Bucketize
../../../golang/src/github.com/gizak/termui/render.go:114: undefined: stack.CalcLengths

@yanyiwu try upgrading to go version 1.9+

This is related to gizak/termui#177

@abhisingh192 I added cointop to the snap store to make it easier to install. http://snapcraft.io/cointop
snap install cointop
Works on any supported Ubuntu release (all the way back to 14.04) and on many other distros too.
@miguelmota Happy to hand the snap over to you if you'd rather own it. :)

@miguelmota will do!


[Feature request ] Support tsv

As in the title, it would be great if the plugin supported tsv as well.

Added support for tsv in v1.1.0


Allow fast null checks in no-unused-expression rule

This PR adds allow-fast-null-checks option for no-unused-expression rule which allows to use logical operators && and || to perform fast check for null(falsy) values and than call methods on non-null values or functions for side effects (e.g. e && e.preventDefault() in event handlers that for some reasons might be called without event object).
New functionality implemented as option to allow teams forbid fast null checks in their code in favor of more verbose implementations.
Implementation allows expression statements with && and || operators (may be nested or in parentheses) which has call expression in right most position , but doesn't checks if this call has side effects (it is developers duty).

I'm a little uncomfortable with letting this syntax to creep into TypeScript, but I totally get how it's so much easier and that it's optional. @adidahiya?

@nchen63 seems ok if the behavior is is hidden behind a rule option. We probably won't enable it in the recommended config.

PR waiting for review for 8 months. pity

It was merged half year ago. Only label left.

This is documented to allow things like e && e.preventDefault(). But what about fn && fn()? It does not seem to allow that to pass. Is it intentional? I'd propose that that should be added too if it's not supported so far.

@gnapse could you create an issue to track that? would welcome a PR for that!

@suchanlee I created the issue (#4021) as requested. I'd love to work on a PR myself, but I'm totally new not just to tslint but to typescript in general. That's no reason to back off, but a hint on where to look for how to work on this would be greatly needed and appreciated. Would love to help!


docker-compose support?

i want docker-compose deploy.
disable mysql SSL Mode.

Any one help?
version: "3.7"

# Service
services:
  # Database MySQL
  MySQLDocker:
    image: mysql:8.0.19
    container_name: EyeBlueTankDB
    #restart: always
    volumes:
      - ./data/mysql:/var/lib/mysql
    environment:
      MYSQL_ROOT_PASSWORD: 123456
      MYSQL_DATABASE: tank
      MYSQL_USER: tank
      MYSQL_PASSWORD: 123456
      MYSQL_OPT_SSL_MODE: SSL_MODE_DISABLED
    ports:
      - "3306:3306"
    networks:
      - app-server-network
  # Tank Server
  app-server:
    depends_on:
      - MySQLDocker
    image: eyeblue/tank:3.0.6
    volumes:
      - ./data/tank:/data/build/matter
    ports:
      - "6010:6010"
    networks:
      - app-server-network

# Network
networks:
  app-server-network:

We do not provide docker-compose any more. You may use simple docker mode.  https://tank-doc.eyeblue.cn/en/basic/install.html#docker


Submissions by Kanishk(2023BCY0003)

I am merging your PR but you need to prepare a readme.md file explaining your algorithm and the mathematics behind it.


Code of conduct in Spanish

Code of conduct in Spanish

It worked! Not sure why alphabetization is not enforce in the comparable pages, but some volunteers are looking at the linter #5031
Thanks, and welcome to free-programming-books!

Great eshellman !!, It was my first colaboration !


false vs. null bug

There's a bug where null is not treated the same as false when it comes to deciding if a template should be shown, per the docs.
    <div>
        Test: {{ foo }}
        {{ #bar }}*{{ bar }}*{{ /bar }}
    </div>

data source:
TESTING_DATA = [
    {
        'foo': 'foo1',
        'bar': null
    },
    {
        'foo': 'foo2',
        'bar': false,
    },
    {
        'foo': 'foo3',
        'bar': 'bar1'
    }
];

Gets rendered as:
Test: foo1 **
Test: foo2
Test: foo3 *bar1*

Instead of the expected:
Test: foo1
Test: foo2
Test: foo3 *bar1*

Specifically the mustache.js docs say "If the person key exists and has a value of null, undefined, or false, or is an empty list, the block will not be rendered."
However, it seems that null is not being treated correctly like false is.

This might have been fixed recently... ( see https://github.com/andyet/ICanHaz.js/issues/42#issuecomment-3640039 )

The link is a 404. Can you confirm that this is still an issue? And if yes, provide a pull request with a failing test case?


CFFL

CFFL

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_ce3p8as43g/clone/recipe/meta.yaml:50: http_url: http://gcovr.com is not https
ERROR: /tmp/abs_ce3p8as43g/clone/recipe/meta.yaml:50: http_url: http://gcovr.com/guide.html is not https
Errors were found


force reinstall configuration options

configuration changes needed for https://github.com/isaacs/npm/pull/4010
this PR is meant to replace a previous pull request https://github.com/isaacs/npmconf/pull/7 which was meant for @rvagg's --skip-installed flag

This project is deprecated, as the relevant code has been directly included in npm once more. Therefore, no new patches on npmconf will be landed. Apologies for letting this PR languish for so long, and thanks for your time!


Add Missing Documentation

Many of the headers are missing Doxygen comments for the functions. This should be resolved and any functions which are not thoroughly explained should also be documented.

Merged in #79


Getting "ERROR: An error ocurred: javax.script.ScriptException: TypeError: [object global] is not an Object in  at line number 4" error

Hello,
Not sure if this is an issue or bad use on my part. I'm trying to into Nashorn a Node.js package, json-rules-enign, located here.
public static void main( String[] args ) { 		App app = new App(); 		String moduleFolder = "node_modules/json-rules-engine/dist/"; 		String filePath =  moduleFolder + "index.js"; 		//String filePath = "index.js"; 		try { 			ScriptEngineManager engineManager = new ScriptEngineManager(); 			ScriptEngine engine = engineManager.getEngineByName(ID_SCRIPT_ENGINE); 			Folder nodeJsModFolder = ResourceFolder.create(app.getClass().getClassLoader(), moduleFolder, "UTF-8"); 			Require.enable((NashornScriptEngine) engine, nodeJsModFolder); 			logDebug("Folder is " + nodeJsModFolder.getPath()); 			engine.eval(new FileReader(app.loadFile(filePath))); 		} catch (FileNotFoundException e) { 			logError(e); 		} catch (ScriptException e) { 			logError(e); 		} 	}
But when I run it, getting this error on the line "engine.eval(new FileReader(app.loadFile(filePath)));", which is trying to load file "node_modules/json-rules-engine/dist/index.js" from the JSON rules engine Node.js package:

ERROR: An error ocurred: javax.script.ScriptException: TypeError: [object global] is not an Object in  at line number 4

In the JavaScript, the error seems to be coming from this line in file "node_modules/json-rules-engine/dist/json-rules-engine.js":
Object.defineProperty(exports, "__esModule", {   value: true });
I'm using Java 1.8.0_121, and version 1.0.6 of nashorn-commonjs-modules. Any idea what I might be doing wrong? Thanks.

I fixed issue in the source code by replacing the line below in "Module com.coveo.nashorn_modules.Module.compileJavaScriptModule(Folder parent, String fullPath, String code) throws ScriptException":
			//exports = engine.createBindings(); 			exports = engine.getBindings(ScriptContext.ENGINE_SCOPE);
This is similar to issue reported here. The original line results in ScriptObjectError type object, which Nashorn does not like, where as the new code creates ScriptObject, which goes through fine. If you have a patch for that let me know. In the mean time I'l run with my update.
Thanks!

I had a look and I could easily reproduce your issue. Sadly, I don't think the fix you suggest is appropriate because this would mean that all modules would use the global scope for their exports. This really seems to be an issue similar to the one you linked... but sadly you get it on a recent version of the JRE. I'll look for a workaround.

Thanks to the tip & PR from @kipz that issue should be fixed once https://github.com/coveo/nashorn-commonjs-modules/pull/17 is merged.

New 1.0.7 release contains this fix.


Factor local error handling

Replace the abstract function with an exhaustive when, which makes it easy to see at a glance how we handle errors in the various states.
Changes in behavior:

removed useless ProcessLocalError
do not force close in Closing if a mutual close has been published (consistent with the Negotiating case)
do not go to Aborted in WaitForRemotePublishFutureCommitment

Rebased.


corex.ssh_start client

start ssh server which has pub SSH keys of user

We should take a ssh pub key (check if there are severals, we can use ssh-add -L) from and send it for corex to start a ssh server


Adding external authentication capability when using oracledb driver

Adding external authentication capability as mentioned in https://github.com/oracle/node-oracledb/blob/master/doc/api.md#extauth

What does it take to merge these changes upstream ?

Hi, I did the changes you mentioned in the previous comment.
And the tests are failing at the "npm run babel" step, and mysql part.

Thanks. Yeah, all builds has been annoyingly semi-random-pretty-much-always failing for some time. I'll look to the random fails and afterwards I'll review this one again.

Looks good now, thanks! I added separate issue to documentation branch about documenting all the supported oracledb driver parameters.


Closing out of an Item opens the Item Palette instead of going back to the Shop...

Minecraft version
1.18.1
Plugin version
3.5.0
Describe the bug
When you edit an item in the Shop, but instead of saving it, close it, it opens the item palette instead of closing and going back to the Shop you were before
To Reproduce
/\
Expected behavior
/\

It was intentional when I first made it, but now it is inconvenient. It would be better to just go back to the store page.

https://github.com/7sat/DShop3/commit/08762a98a8db8fd13805f9c84e72c058c8df65f3

Thanks👍