Next pass in StandardMaterial3D is not working

Godot version
4.0.3.rc1.mono
System information
Windows 11, Vulkan, Nvidia GeForce RTX 3070 Ti Laptop
Issue description
I have trouble using "Next pass" in the StandardMaterial3D:
I have set it to a material with a shader that just outputs a color to ALBEDO, but the color is not rendered. Only the albedo color from the StandardMaterial3D.
Steps to reproduce
Create an empty project.
Create a ShaderMaterial and a shader that outputs some color to ALBEDO.
Create a StandardMaterial3D and set some different albedo color, then set the ShaderMaterial in the "Next pass".
Create a MeshInstance3D and a PlaneMesh, and set "Surface Material Override" to the StandardMaterial3D.
The color from the shader is not rendered.
Minimal reproduction project
SecondTestGodot4.zip

Tested a little more:
It seems to work if I create new materials (and shader) that I apply to the MeshInstance.
But only in the editor. And if I run the sample or restart the project, it shows wrong again.

This is because the second pass is drawn at the same coordinates, which will cause only one of the two passes to be visible.
If you enable Grow and change its Amount on the original material, notice how the planes become separated:

This also occurs on the running project:

Closing, as this is not a bug but a configuration issue.

Also note for future readers, using rendering_priority will change the order in which the passes are rendered


"(more topics)" link does not display any topic

The "(more topics)" link displayed below the most recent topics of a stream in the stream view on the left doesn't work: clicking on it brings you to an empty list of topics.

I thinks it's working as expected.

Closing until more info given.

Yeah, it's working in some cases and not in others -- maybe I was mistaken and there weren't anymore topics. I'll reopen when/if I find more info.

Sometimes I get the same behaviour on web(browser) as well. I think this might be issue with Zulip  not the app.

A bug of this form is very likely to be a Zulip webapp bug that we should track in the zulip/zulip project; I don't see a mechanism for the desktop app to cause that.

Yes, I think the problem with the Zulip webapp. Although I am not able to reproduce it. It occurs very rarely.


How to build  rmw_connextdds on Raspberry Pi 4b ?

Hi, I am trying to use RTI DDS with ROS2.
System Info
OS
Ubuntu20.04
ROS version and installation type
foxy
RTI Connext DDS version and installation type
6.1.1

In desktop environment, I succeed with installing RTI DDS 6.1.1 with rmw_connextdds repository.
Now I am trying to install RTI DDS on Raspberry Pi 4b (armv8 architecture).
I Downloaded "rti_connext_dds-6.1.1-lm-target-armv8Linux4gcc7.3.0.rtipkg" and “rti_connext_dds-6.1.1-lm-x64Linux4gcc7.3.0.run”,and
I installed the armv8Linux package on a Linux host machine(PC) using the RTI Launcher as described in the RTI document.
Then I copied the whole installation(/opt/rti_connext_dds-6.1.1/) to the Raspberry Pi 4b and to build rmw_connextdds  refer to #10 ,
but  I got following errors:
lly@lly:~/ros2_connextdds$ colcon build
Starting >>> rti_connext_dds_cmake_module
-- The C compiler identification is GNU 9.4.0
-- The CXX compiler identification is GNU 9.4.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Found ament_cmake: 0.9.9 (/opt/ros/foxy/share/ament_cmake/cmake)
-- Found PythonInterp: /usr/bin/python3 (found suitable version "3.8.10", minimum required is "3")
-- Using PYTHON_EXECUTABLE: /usr/bin/python3
-- Detected CONNEXTDDS_DIR = '/opt/rti_connext_dds-6.1.1'
-- CONNEXTDDS_ARCH not provided, trying to guess it...
-- Guessed CONNEXTDDS_ARCH ('5gcc9.4.0') not available.
-- Pick first from /opt/rti_connext_dds-6.1.1/lib/[armv8Linux4gcc7.3.0;java;x64Linux4gcc7.3.0]
-- unsupported CMAKE_HOST_SYSTEM_NAME (Linux) or CMAKE_HOST_SYSTEM_PROCESSOR (aarch64). Using architecture armv8Linux4gcc7.3.0 anyway.
-- Selected CONNEXTDDS_ARCH: armv8Linux4gcc7.3.0
-- RTI Connext DDS installation directory: /opt/rti_connext_dds-6.1.1
-- RTI Connext DDS architecture: armv8Linux4gcc7.3.0
  CMake Error at /opt/rti_connext_dds-6.1.1/resource/cmake/FindRTIConnextDDS.cmake:1102 (message):
  Linux-5.4.0-1066-raspi is not supported as host architecture
  Call Stack (most recent call first):
  cmake/rti_build_helper.cmake:572 (find_package)
  CMakeLists.txt:25 (rti_find_connextpro)

-- Configuring incomplete, errors occurred!
See also "/home/lly/ros2_connextdds/build/rti_connext_dds_cmake_module/CMakeFiles/CMakeOutput.log".
Failed   <<< rti_connext_dds_cmake_module [3.10s, exited with code 1]
lly@lly:~/ros2_connextdds$

Is there any suggestion???
Thank you !!!!!

Hi there, do you have any update regarding this issue? I am facing the same error.

The issue stems from script resource/cmake/FindRTIConnextDDS.cmake included with Connext 6.1.1, which unfortunately does not support armv8 "host" environments.
I tried replacing it with the latest version (available from the rticommunity/rticonnextdds-cmake-utils repository) and I was able to build rmw_connextdds successfully. I suggest downloading this version (e.g. from the "raw" link) and replacing the one included by default.
Note that if you have more than one set of "target libraries" installed under $CONNEXTDDS_DIR/lib, you will have to specify which "architecture" to use  by passing CONNEXTDDS_ARCH to cmake (e.g. colcon build --cmake-args -DCONNEXTDDS_ARCH=armv8Linux4gcc7.3.0).
As I mentioned in #10, if you are using Connext only to support rmw_connextdds, you could also copy just the required subset of files from the x64 Linux installation in order to reduce the size of the installation on the Raspberry Pi.
You can achieve this with a command like:
tar czf rti_connext_dds-6.1.1-armv8Linux4gcc7.3.0-ros-runtime.tar.gz \
        rti_connext_dds-6.1.1/include \
        rti_connext_dds-6.1.1/lib/armv8Linux4gcc7.3.0 \
        rti_connext_dds-6.1.1/resource/cmake \
        rti_connext_dds-6.1.1/resource/scripts \
        rti_connext_dds-6.1.1/rti_versions.xml

Then copy rti_connext_dds-6.1.1-armv8Linux4gcc7.3.0-ros-runtime.tar.gz and extract it on the Raspberry Pi.


Fix termtables dependency

Updating to the latest version of this repo doesn't work without the module proxy, as it depends on the apcera/termtables package, which doesn't exist. A previous PR appears to have switched to another repo for this package, but the version it depended on appears to rely on doesn't exist (no tag on that repo?), and also depends back on the missing package, probably due to the version being in the middle of a rename.
Update the dependency to the latest version (fetched with go get -d github.com/scylladb/termtables@master) and go mod tidy to ensure this module does not refer to a package that cannot be fetched.

Codecov Report

Merging #112 into master will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##            master      #112   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            1         1
  Lines          935       935
=========================================
  Hits           935       935

Continue to review full report at Codecov.

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

Perfect, thank you, i saw this yesterday and spent some time trying to fix it but didn't get it done so thank you so much!


Wrong url is returned from Create if UserRef.UserLogin is incorrect

Describe the bug
UserRepositories().Create() returns a different URL from the created repository (when the wrong string is set as UserLogin. This is because it makes a create request to the API (which doesn't need the UserLogin) and it succeeds. It then uses what's set as UserLogin to construct the URL string which is different from what is returned from the API (edited)
This causes this issue https://github.com/fluxcd/flux2/issues/3867 in flux2 when a user sets the personal flag when creating an org repository. While this is a user error, the output from Flux isn't helpful since it creates a repository and tries to clone a different one.
To Reproduce
Call UserRepositories().Create() and pass a UserRef.UserLogin that is wrong.
Expected behavior
Create should return the URL of the repository that it created.
Additional context

Go version: go1.19
Git provider: GitHub/ GitLab

We should be able to get regression tests in place for this behaviour.


Fetch branches as well

I find this library very handy and it can be improved by adding branches too. It is bad practice to depend on branch because it simple unstable. But unfortunately there might be repos without any tags and only "tagging" on particular commit hash can help.

We also have this "problem". Our private library depends on a library which does not have any tags (only master branch) nor a composer.json. Of course we know that this is risky but at the moment we cannot change this.
In our satis.json we added the github repository:
    {
      "type": "package",
      "package": {
        "name": "jquery-archive/jquery-metadata",
        "version": "master",
        "source": {
          "url": "https://github.com/jquery-archive/jquery-metadata",
          "type": "git",
          "reference": "master"
        }
      }
    }

When building the satis.json with satisfy and after that build satis the library gets shown on the satis browser page with version "master".
In our libraries composer.json we have
"require": {
    "jquery-archive/jquery-metadata": "master"
}

But when updating composer it errors that version *@dev cannot be found. When we put the repository in the composer.json itself, it works.
But as written above we want to use this private library on another project and composer cannot load repositories recursively. That is why I would like a add this tag-less repository to Satis so the new project can require our private library.


[ST] Unexpected delays on Arbitrum transactions

Describe the bug
Transactions involving Arbitrum (either as origin or destination) are getting unexpected delays and it looks like they're going through the slow path.
https://connextscan.io/tx/0xfe684c502069390c90be567ce666836ce1acb34f4f7cd6630d6ea568d8a7f431
https://connextscan.io/tx/0x57596015e363910adca7f42ca35172f50f47c1e492875b97f49cc2aa475c9fd7?source=search
https://connextscan.io/tx/0x5494d215e41dfc9e042602c02b1c3caf51bafa5a8d83fe426f288182f3c8be93
https://connextscan.io/tx/0x27ef6b952f142e5b381ccd725798bba375214b75bb1441e17583eb01360651ac?source=search
Link to ticket in discord
https://discord.com/channels/454734546869551114/1194201414172430336/1194201541389856790
https://discord.com/channels/454734546869551114/1194223677663879249/1194223998465220638
https://discord.com/channels/454734546869551114/1194234704199688234/1194235686270795826
https://discord.com/channels/454734546869551114/1194236490214015076/1194236590172688475

https://connextscan.io/tx/0x7a005f9da2afb696e88c676125e7ec0d9bbd44ed12912afdb4c053a5c605c2d2
https://discord.com/channels/454734546869551114/1194240488149098576/1194241598880481290

It looks like the main issue is for transactions going to Arbitrum. The few transactions originating on arbitrum and getting stuck on xcalled are for going to WETH on mainnet and it's possible that they aren't completing due to the router not bidding bug


TrackMe bug report - DateParserVerbose Warnings logged

Description:
Some TrackMe scheduled reports generate DateParserVerbose Warnings. Cause of these warnings seems to be a missing timestamp in the *_search_telemetry.json files.
To Reproduce
Steps to reproduce the behavior:

Install TrackMe and prerequisites
wait at least 5 minutes for TrackMe scheduled reports to execute
Search index=_internal sourcetype=splunkd error OR warn DateParserVerbose "*_trackme_*" returns results
Search index=_introspection sourcetype="search_telemetry" | where isnull(timestamp) returns results

Expected behavior
No DateParserVerbose Warnings are logged
Splunk version and deployment:

Splunk 8.1.2, 8.1.3
TrackMe 1.2.20, 1.2.38
occurs on both Splunk single searchhead and searchhead cluster

Additional context
Sample search_telemetry.json:
search_telemetry.json.txt

Thanks @steffu3123
Interesting, Splunk telemetry, wondering what's causing the timestamp to be missing.
Telemetry is a Splunk internal thing, surely some stuff in TrackMe is linked to this.
Will investigate

@steffu3123
This is not clear to me why this happens and I believe this to be a Splunk core bug in the telemetry generation.
In a single JSON file generated, we can see two well formed JSON payloads, one has a timestamp and this other does not.
I do nothtink this to be related with TrackMe at any direct level, thus this can be workaround from a TrackMe only point of view by including the following props source stanza in the app:
# search_telemetry
# Splunk generates date time parsing erros with the search telemetry due to a timestamp missing in the second json payload of a same json generated
# This seems to be a Splunk core issue with telemetry and the root cause was not idenfitied
# however, this can be workaround with a source based stanza forcing the a date time config

[source::.../var/run/splunk/search_telemetry/...trackme...telemetry.json]
TRUNCATE = 99999
DATETIME_CONFIG = CURRENT

This will be included in next release.

Thanks @guilhemmarchand
I've configured the workaround inlocal/props.conf and I haven't seen any DateParserVerbose warnings so far.

thanks @steffu3123 for confirming, will be part of next release.


Add "json_merge_patch" dependency

I confirmed that json-merge-patch with - not _ is the canonical spelling on PyPI. (PyPI does redirects for _ versus -.) I sorted all the deps to reduce the chance of confusion.


Customized access rights

It will be possible for a dictionary administrator to limit a user's access to only a subset of entries, or to only some locations in an entry. For example, some users may only be allowed to add translations to entries but cannot change anything else.
Requested by Carole Tiberius of IVDNT and by K Dictionaries.

We need to blue-sky think about how we want to group entries into subsets and "give" them users. This overlaps with the topic of workflow management, #41.
As far as limiting access to only some locations inside entries, this is kind-of doable already through custom editing widgets and through selecting hiding/read-onlying of XML elements – although this always applies to all users.


Revert move of legal.html and post_download.html to zowe.org

Change made in this commit.. https://github.com/zowe/zowe.github.io/commit/26975a50914ba278f8207f4ccf4ea05645cf7b09#diff-82918ac012d2f41b1522d18cfd6b03f9d76a57662e88cb7707627d7d2eb91efc
We need to revert this as we cannot host those files from zowe.org due to legal concerns.

Any updates @nannanli and @MarkAckert ?

Any updates here?

Hi! Can we get this prioritized? @MarkAckert @balhar-jakub

I am a bit lost. The artifactory is the server where we host all the Zowe related artifacts.
I was going through the downloads page and what it does is that it takes you to the legal page where you state I agree and then all the files are downloaded from the actual Artifactory at least the binaries.
Is there something I am missing?

It's more of an appearance issue - the URL makes it look like it's coming right from Zowe versus a seperate place. This is why before we had it all served from Artifactory; technically it's not owned by the project.
Before we had an S3 bucket the project used for hosting those pages, but it was a PITA to deal with.

Ok, John, let's bring it to TSC in January to understand what the appearance should look like and why and then we can actually make some change.

We will resolve in zowe/community#1790 as discussed today - closing


faf-client: update openjdk from 17 to 21

two legacy package names are used here, which break build - okio instead of okio-jvm, and kotlin-stdlib-common instead of kotlin-stdlib, I'll try to find a way to fix it


Animbits: Tween pose custom context

This is an idea brainstorm: tween machine without UI. just hotkey and drag to trigger
References:
http://justinsbarrett.com/tweenmachine/
https://vimeo.com/119641189

This issue was moved to mgear-dev/animbits#4


add support for rdb v9 (redis 5.0) and memory analysis of streams

Great, thanks for the reminder!

@sripathikrishnan @oranagra Is this complete. Based on the PR you have it is.
I am trying to import which I believe is redis 5.0.3 with a file header REDIS0009. I just get an empty json object.
Does the library have support for it? Also do you have documentation on DEBUG or TRACE flag for the  tool?

@jerrygb the streams support at the moment is just in the memory analyzing aspects.
no support in the json and other features, since we didn't implement listpack decoding yes.
PRs are welcome 8-)

Thank you for the update @oranagra

@oranagra Weird enough, I am also not able generate a memory report/analysis with the v9 file. Are there specific breakpoints or traces within the code you can point me to before I dig deeper into the source?
Thanks in advance.

@jerrygb what do you mean? are you getting any error? if so, please post it.
what version of redis-rdb-tools are you using? what command line did you use?

@oranagra  i am not able to generate json from rdb which contains streams. Is it supported ?

@akshayvijapur no that's not supported yet. see https://github.com/sripathikrishnan/redis-rdb-tools/issues/128#issuecomment-464348680


[Load Balancer] Support pattern matching

Add pattern matching on advanced routing option.
Like HAProxy 1.5 flag -m.

@bcaudesaygues
Does the wildcard ability solve what you were looking for?
https://github.com/rancher/rancher/issues/1787
http://docs.rancher.com/rancher/rancher-compose/rancher-services/#syntax-of-the-combination-of-all-optional-fields
Scroll down to Wildcards.

@deniseschannon : The wildcard ability works only for host name maching.
@bcaudesaygues was in fact asking to have the ability to use regexp matching for path.
As I see it, it could be a selection list in the UI to indicate the type of tge desired match for the path. HAproxy supports those :

If you prefer that we made a new issue rather than reopening this one, please tell us.


Perpetual tasks

Closes #467 by introducing the duration field on task type and task templates to be optional.
Documentation
There are a couple of consequences, which first are documented here but have to also be documented in a wiki page:
Semantics of Task (Type / Template) Duration
The duration is now optional, resulting in the semantic that if no duration is provided, the task will run perpetually, even after a restart of DRES.
Consequences
Syncrhonous Run
For perpetual tasks in a synchronous setting, administrators have to manually close (abort) the task.
Asynchronous Run
For perpetual tasks in an asynchronous setting, participants are free to skip the task, which might affect the scoring.
Other Changes
There is a new NOOP scorer, the non-operational scorer simply does not calculate a score, yet feedback regarding the submisison is provided.

Converted to a draft since the proposed KIS handling for perpetual tasks is not yet implemented.


Suggest not to format the traling formatting arugment if it's the only one

for example logger.Warnf("Riding the storm at %v", time.Now()) is just
as good as logger.Warn("Riding the storm at ", time.Now()), but costs
much less at runtime.
/assign mattmoor

cc @n3wscott

Sample run is here: https://github.com/knative/serving/pull/9599/files
Looks pretty legit, very cool.
/lgtm
/approve

/hold

/unhold


No type completion support for components in a Nuxt layer

Environment

Operating System: Darwin
Node Version:     v18.16.0
Nuxt Version:     3.6.1
Nitro Version:    2.5.2
Package Manager<EMAIL_ADDRESS>Builder:          vite
User Config:      extends, devtools
Runtime Modules:  -
Build Modules:    -

Reproduction
Impossible to reproduce online due to the nature of CodeSandbox/StackBlitz.
Need to run the project in VS Code w/ Volar.
Describe the bug
When extending a Nuxt layer that's a npm package with a component inside of it, I don't get any type completion for props.
I do, in fact, have everything working fine If I extend the layer in the .playground folder directly inside the same project.
Let's say I create a simple MyButton component that accepts a variant prop that could be "solid" or "ghost": I get variant autocompleted then it suggests solid or ghost as possible values.
Now, If I install the package and extend it in nuxt.config.ts and try to replicate this behavior, it doesn't work. Component works fine though.
Plugins I provide are working fine. Example: $toast is suggested, the success property pops up if I try $toast.s and I get every available hint inside of it. Same thing for composables (custom one or imported from layer dependencies).
Is it a Volar issue? Should I do something in my tsconfig file?
I tried with my work project layer as well as other random layers available on npmjs and got the same outcome.
Additional context
VS Code 1.79.2 w/ Volar 1.8.3.
Logs
No response

I'm not sure what actually happens due to lack or reproduction (could you provide a GitHub repository instead of StackBlitz by which I can see the code in VSCode in my local?).
But, as far as I see your description, it might be related to Volar's breaking change as of v1.8.2.
That is, Vue files that are not listed up in include option in tsconfig.json are no longer parsed by Volar.
It would be worth trying to add path(s) to your components in include option.
https://github.com/vuejs/language-tools/blob/master/CHANGELOG.md#182-2023627

@danielroe Do you think it should be mentioned somewhere in the documentation, either in the Volar part or the authoring layers section? I'm down to suggest something if necessary.

Yes, I think that's a reasonable solution :+1:

This should be resolved in the edge channel, or in the next release.
Let me know if not and I'll reopen.


feat(jest-core, jest-watcher)!: move TestWatcher class to jest-watcher

Summary
As a TODO comment in jest-runner mentioned, it seems to be good idea to move TestWatcher class to jest-watcher. Noticed it while working on #12646 and just could not leave it.
Test plan
Green CI.

Ur deleting s*** like I am not watching for years

I just heard ur phone too 😜😂


Update init file

#38

I was about to merge this update locally and check out the functionality. I'm seeing something weird.
#Reading in a larger orientation file:
ori = Orientation_file.parse_from_file("/Users/ckierans/Software/COSItools/COSItools/intro_cosipy/test_data/miniDC_GRB_20280301.ori")
#defining the time differences:
Timemin = Time(3433.0,format = 'unix')
Timemax = Time(3435.0,format = 'unix')
grbori = ori.source_interval(Timemin, Timemax)
#And defining the inputs for the spacecraft frame
x,y,z = grbori.get_attitude().as_axes()
dts = grbori.get_time_delta()
src_movement = SCPosition.sc_frame(x_pointings = x[:], y_pointings = y[:], z_pointings = z[:])
#And then making a dwell time map based on Yong's SCPosition code:
dwell_time_map = SCPosition.get_dwell_map(response = response_path, dts = dts, src_path = src_movement[:-1])
#But then calculating the sum of the exposure in the dwell time map gets me only 1.2 s
sum(dwell_time_map)
However the sum of the dts array gives the expected 2 second total duration.
Not sure if this is an issue with the orientation class interpolation or Yong's dwell time map.
@saurabhmittal23 @Yong2Sheng


TODO

noborder -> removebrder, or disable it.
compare with my dwm commits.

keep update with upstream

showhideclient? Is this for awesomebar show hide ?

bar_wintitleactions_patch, togglewin, showhideclient, might relative to awesomebar's showhide.

compare with my dwm commits.
525d3f50
9daf06dd

systray cfw icon not show.


Add chart v1.4.1

Note on DCO:
If the DCO action in the integration test fails, one or more of your commits are not signed off. Please click on the Details link next to the DCO action for instructions on how to resolve this.
Checklist:

[ ] I have bumped the chart version according to versioning
[ ] I have updated the chart changelog with all the changes that come with this pull request according to changelog.
[ ] Any new values are backwards compatible and/or have sensible default.
[ ] I have signed off all my commits as required by DCO.

Changes are automatically published when merged to master. They are not published on branches.
ChangeLog

Fork v1.4.0 chart, and rename versions of chart and images as v1.4.1.
RBAC: Add csidrivers read role for koord-scheduler.
CRD: Fix nodeslo YAML.

/hold for release v1.4.1 at https://github.com/koordinator-sh/koordinator/releases.

/hold for release v1.4.1 at https://github.com/koordinator-sh/koordinator/releases.

/unhold
v1.4.1 images are built.


SSL: CERTIFICATE_VERIFY_FAILED

Is there a way per-chance to ignore SSL certificate verification?
When running a kpm deploy ... https://kpm.sh I'm getting an error like so:
[openshift@test-cluster-master-0 stackanetes]$ kpm deploy coreos/kpm-registry --namespace kpm -H https://kpm.sh
Traceback (most recent call last):
  File "/usr/bin/kpm", line 8, in <module>
    args.func(args)
  File "/usr/lib/python2.7/site-packages/kpm/command.py", line 49, in install
    variables=variables)
  File "/usr/lib/python2.7/site-packages/kpm/deploy.py", line 83, in deploy
    return _process(*args, **kwargs)
  File "/usr/lib/python2.7/site-packages/kpm/deploy.py", line 31, in _process
    packages = registry.generate(package_name, namespace=namespace, version=version, variables=variables)
  File "/usr/lib/python2.7/site-packages/kpm/registry.py", line 73, in generate
    r = requests.get(self._url(path), data=json.dumps(body), params=params, headers=self.headers)
  File "/usr/lib/python2.7/site-packages/requests/api.py", line 70, in get
    return request('get', url, params=params, **kwargs)
  File "/usr/lib/python2.7/site-packages/requests/api.py", line 56, in request
    return session.request(method=method, url=url, **kwargs)
  File "/usr/lib/python2.7/site-packages/requests/sessions.py", line 488, in request
    resp = self.send(prep, **send_kwargs)
  File "/usr/lib/python2.7/site-packages/requests/sessions.py", line 609, in send
    r = adapter.send(request, **kwargs)
  File "/usr/lib/python2.7/site-packages/requests/adapters.py", line 497, in send
    raise SSLError(e, request=request)
requests.exceptions.SSLError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:765)

I couldn't find in the documentation anything about ignoring cert verification. e.g. with
[openshift@test-cluster-master-0 stackanetes]$ kpm -h
[openshift@test-cluster-master-0 stackanetes]$ kpm deploy -h

KPM installed like:
sudo pip install kpm -U

Here's my KPM version:
[root@test-cluster-master-0 stackanetes]# pip show kpm | grep Version
Metadata-Version: 1.1
Version: 0.16.1

This may be likely due to the version being out of date. Once updated to 0.21.1rc2 -- I didn't have the error anymore and I could deploy a kpm registry locally using:
kpm deploy coreos/kpm-registry --namespace kpm -H https://kpm.sh

Hi,
fyi, the plan is to remove the -H option and having a command line closer to docker:
kpm deploy kpm.sh/coreos/kpm-registry
kpm deploy localhost:5000/ns/myapp

and add the option --allow-insecure  to accept self-signed or try in http:// too
is kpm.sh an alias? it should be https://beta.kpm.sh or api.kpm.sh

Thanks @ant31 for the update!
Looks like I had a copy-paste mistake from my history in the above. I believe the actual command that works is pointed @ beta.kpm.sh -- and not just kpm.sh a la:
kpm deploy coreos/kpm-registry --namespace kpmtester -H https://beta.kpm.sh


Show dialog from dialog

I have two dialog method. If the user press the button in first dialog (from Gravity.TOP) i want show the next dialog (Gravity.Bottom). But the second dialog not present on view. In debug i see the dialog.create() and show() run. The two dialog born from MainActivity.
I need some clear someWhere before show the second dialog?
First dialog:
public void shareButtonClickced()
{
	ShareNoConnectionAdapter shAdapter = new ShareNoConnectionAdapter(this);
	DialogPlus dialog = new DialogPlus.Builder(this)
		.setAdapter(shAdapter)
        .setGravity(DialogPlus.Gravity.TOP)
        .setHeader(R.layout.dialog_share_header)
		.setOnItemClickListener(new OnItemClickListener() {

             @Override
             public void onItemClick(DialogPlus dialog, Object item, View view, final int position) {
                dialog.dismiss();
                showLoginDialog();
             }
         })
	.create();
	dialog.show();
}

Second dialog:
public void showLoginDialog()
{
    ExitViewAdapter lgAdapter = new ExitViewAdapter(this);
	DialogPlus dialog = new DialogPlus.Builder(this)
        .setAdapter(lgAdapter)
        .setGravity(DialogPlus.Gravity.BOTTOM)
        .setOnItemClickListener(new OnItemClickListener() {
        	@Override
        	public void onItemClick(DialogPlus dialog, Object item, View view, final int position) {
            	dialog.dismiss();
            	//my rest of code
        	}
        })
        .create();
	dialog.show();
}

Thank you in advance for your help

Unfortunately, current structure does not support 2 instance at the same time, while you call dismiss(), it is not dismissed immediately since there is animation. You need to call the other dialog after completely dismissed. You can use dismiss listener to solve this issue.
public void shareButtonClickced()
{
    ShareNoConnectionAdapter shAdapter = new ShareNoConnectionAdapter(this);
    DialogPlus dialog = new DialogPlus.Builder(this)
        .setAdapter(shAdapter)
        .setGravity(DialogPlus.Gravity.TOP)
        .setHeader(R.layout.dialog_share_header)
        .setOnDismissListener(new OnDismissListener() {
          @Override
          public void onDismiss(DialogPlus dialog) {
              showLoginDialog();
          }
        })
        .setOnItemClickListener(new OnItemClickListener() {

             @Override
             public void onItemClick(DialogPlus dialog, Object item, View view, final int position) {
                dialog.dismiss();
             }
         })
    .create();
    dialog.show();
}

Thank you very much!

:+1:


Fix response handling in tenant

Response object from requests doesn't have status attribute,
some code path will hit this:
AttributeError: 'Response' object has no attribute 'status'
Signed-off-by: Kaifeng Wang<EMAIL_ADDRESS>

I'd say GHA is pretty fast, no queuing :)

I'd say GHA is pretty fast, no queuing :)


Handle batch input inference for MoD Infini-Former more gracefully

Currently, the token sampling for MoD Infini-Former at inference time can result in different length sequences for each observation in the batch. The current workaround is to force the batch size to one and loop through the observations in the batch, which is highly inefficient.
There are two main options for handling this efficiently:

Pad the sampled sequences to the longest sequence length in such a way that the additional tokens contribute nothing to downstream calculations.
Wait for PyTorch to implement a ragged tensor type

I'm likely to pursue the first because there's no telling how long it'll be before the PyTorch devs add ragged tensors.

I worked on this issue #15.

Should this issue be closed, or do you need any more changes? Please let me know if you have any further questions.

Unfortunately, the fix you introduced assumes that calling .forward_() produces a valid result when called on the original input. What needs to happen during inference is for .forward() to use sample_mask_seg to pad the samples along the token dimension until they all have the same length. The part I haven't gotten around to is going through the math to determine a choice of padding token that doesn't affect downstream calculations.
For the moment, I'm going to revert the change, just to maintain functionality (slow as it is). I really appreciate your putting in time on this though!


resizeMode.cover and resizeMode.center work inverted on some Samsung devices.

Describe the bug
By a strange reason, some Samsung devices has an issue with resize mode. So they looks like be using resizeMode.center while the already has resizeMode.cover as a props, and if you switch and set resizeMode.center, they will work like they have resizeMode.cover as props.
To Reproduce
Steps to reproduce the behavior if possible, or a link to a reproduction repo:

Search an Samsung aXX device
Set coverMode as FastImage.resizeMode.cover
If Image looks like it be centered, here is your issue.

Expected behavior
Expected an image covered on image area.
What I got
Image centered and with zoom.
Screenshots
resizeMode={FastImage.resizeMode.cocer}
Expected:

Current:

resizeMode={FastImage.resizeMode.center}
Expected:

Current:

Dependency versions

React Native version: 0.61.2
React version: 16.9.0
React Native Fast Image version: discovered on 7.0.0, still happening on 7.0.2

@dann1609 I seem to be encountering this too! Did you have any luck with fixing it?


MessageSender abstraction is broken for Path when Send-Via is used

Actual Behavior
MessageSender supports Send-Via feature. Send-Via is using a transfer queue to route message to their final destination when using transactional processing. The abstraction is represented by a public overload of MessageSender that takes in two paths

entitytPath
viaEntityPath
https://github.com/Azure/azure-service-bus-dotnet/blob/e278f87b0b3aa563ab055918e988baec9ec155a3/src/Microsoft.Azure.ServiceBus/Core/MessageSender.cs#L127-L135

The abstraction has been copied from the old client and works, but it's broken when Path and TransferDestinationPath are queried back. That's because all public overloads are invoking an internal overload, swapping the two paths:
https://github.com/Azure/azure-service-bus-dotnet/blob/e278f87b0b3aa563ab055918e988baec9ec155a3/src/Microsoft.Azure.ServiceBus/Core/MessageSender.cs#L132
where internal overload is
https://github.com/Azure/azure-service-bus-dotnet/blob/e278f87b0b3aa563ab055918e988baec9ec155a3/src/Microsoft.Azure.ServiceBus/Core/MessageSender.cs#L137-L144
assigning viaEntityPath to this.Path and entityPath to this.TransferDestinationPath. Which is inverted.
Expected Behavior
Path and Send-Via/TransferDestinationPath after MessageSender constructor is invoked should be identical to the values passed in.
Repro
LinqPad repro script attached.
var sender1 = new MessageSender(connection, "path");
sender1.Path.Dump("Should be 'path'");
Assert.IsNull(sender1.TransferDestinationPath); // green

var sender2 = new MessageSender(connection, "path", "intermediate");
Assert.AreEqual("path", sender2.Path); // red, equals to "intermediate"
Assert.AreEqual("intermediate", sender2.TransferDestinationPath); // red, equals to "path"

Recommendations
The fix should be released as a major version for the following reasons:

This is a breaking change. While a fix will restore the correct behaviour, it will affect any existing solution relying on the incorrect implementation.
Anyone implementing a workaround will be broken if they update to a patch/minor.

@jsquire @AlexGhiondea have you had a chance to triage this one? This is a client bug.

@SeanFeldman we will consider this for the next release of the Service Bus client. We currently do not have a release date for when that is going to be.

@AlexGhiondea note that this will be a breaking change and will require a new major.
In that case, you might want to introduce other breaking changes, such as https://github.com/Azure/azure-sdk-for-net/pull/6037.

@AlexGhiondea any updates about next (major) release and when this will be addressed?

@AlexGhiondea @jsquire would be nice to label this issue as bug to indicate what it is. Thank you.

/cc @binzy @nemakam

Closed in #6941

Needs to be a minor with the change made in PR.
https://github.com/Azure/azure-sdk-for-net/pull/6941#issuecomment-512110678


Task - Source from Citation - Serials

When created source from a citation. Add serial if it has match in the database.

[ ]  Add serials filter
[ ] Add dynamic check for exact match in new source task


Create 0000-01-02-jayam26.md

create file in branch slide and commit to main branch

Merge the branch

Delete slide branch


add hover and focus effect on navbar and hamburger menu links

Description
I have made the following changes:

Added an animate on hover and focus effect to navbar links and hamburger menu links.
Implemented an underline effect on active navbar links and hamburger menu links.
Added cursor-pointer to the hamburger menu icon.

This pull request addresses the issue #210
Type of change
Please delete options that are not relevant.

Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

My code follows the style guidelines of this project
I have performed a self-review of my code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
My changes generate no new warnings
[ ] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules

Before
https://github.com/UBA-GCOEN/StichHub/assets/56599943/94a544b1-6d96-4f15-99b4-0b923dee3c7a
After
https://github.com/UBA-GCOEN/StichHub/assets/56599943/89a38302-a768-4b9b-83c9-3d86c0f50823

Hello @Amitavpanda!
Thank you for submitting this pull request Your pull request will be reviewed by maintainers shortly. Meanwhile make sure you have referenced the respected issue in this pr Your pr will not be merged if it does not refer respected pr and please read our Contributing Guidelines https://github.com/UBA-GCOEN/StichHub/blob/main/CONTRIBUTING.md And Code of Conduct https://github.com/UBA-GCOEN/StichHub/blob/main/CODE_OF_CONDUCT.md

@vishal10kesharwani I made the changes according to the guidelines provided, please give it a review.

@Amitavpanda will the underline of the sections will not update as we scroll ??

@Amitavpanda ??

@Amitavpanda what's the status?

@Siddhant-Patil0203 Due to some issues, I would not be able to work upon it and Sorry for late response.

@Naresh-chandanbatve you can assign this issue to someone else.

Your changes will not be lost @Amitavpanda
Thank you for your time and contribution to project ❤❤.
You can contribute to this project even after the end of program.


Bunch of impressions and suggestions from the Hacker News Publication.

If you ask yourself this huge lot of stars on the repo, We got quite a bit of attention on Hacker News.

This is a nice idea, but the one thing I haven't been able to divorce myself from is YouTube. I really hate how Google has allowed such a wealth of constant information that completely dwarfs alternative video hosting sites. As censorious as Google can be(now "up next" is always some video from CNN or Fox), blocking YouTube from my network would mean cutting myself off from a large portion of the world.

I will test once again if adding all the list, except the youtube one let you access and use it. For myself, I´ve had no issues since when using it with invidio.us. Maybe that person didn´t noticed that we have separate lists.

The problem is that JS Fonts and other CDNed stuff won't load and websites will hang or work weird - particularly Stackoverflow. Bc it's all over https you can't MITM it and inject your own with OpenWRT/piholes. Decentraleyes (a Firefox browser extension) fixes some of this, but not all. If anyone has any additional suggestions, please let me know (it makes life bearable in China without a VPN)

If we can extract some specific domains from those, this can be useful indeed. I mainly block all the JS fonts, and mostly other CDN´s, But i do aggree that sometimes, You can´t even have a slight usage of the website. So, possibly for an another list.

Does the author mention avoiding using Google as a third party DNS service.[?] In the beginning, PiHole, i.e., preconfigured dnsmasq, was pointed at some third party DNS service, maybe Google. Not sure what the default configuration is today. If it was Google, then is there any irony in that a project designed to blocks ads is by default having its users send their IP and ISP location to an advertising company probably hundreds if not thousands of times over in a single day of web use.

Nice idea, even if we do block their DNS servers itselves, it might be great to suggest people to directly think of using an alternate one, or a way to bypass it if they are on some android phones for example.

I find Google Container to be an excellent plugin to segregate my Google account from the rest of my browsing. It's not an official plugin from Mozilla, but it is forked from the Facebook container plugin.

Maybe create some sorts of ¨Other things that we recommend to use with pihole-google¨ on the read-me page.

GAFAM
Never seen it listed out like that, I thought it was FAANG. Or is FAANG only used in reference to top salaries in the Bay Area?
GAFA(M) omits Netflix but not Amazon, since it stands for Google Amazon Facebook Apple (Microsoft)

Well, That´s due to me being french obviously. Should i remove or ¨rename¨ all of that ? Also, I could also add some of the new little ones, but they still have a much smaller importance compared to the principal ones, so i don´t think Netflix could be useful.

Nice idea, but you're better off accomplishing it with TLD wildcards or AXFR transfers than a hosts list, since new sub-domains are always being created and rotated.

Suggestion for creating some wildcards lists.

Hosted by Microsoft, suggests blocking Microsoft, too.

If you care about that detail, we can move that project elsewhere, or host a backup/copy on a local gitea instance. I think i can do that on my raspberry pi without much issues.

I´ve created an throwaway account just for this post, (https://news.ycombinator.com/user?id=CreatedForThis) if you want to answer to some of them despite having an account, just pm me @nickspaargaren


undefined is not a function after ember-cli 2.9.1 upgrade

using ember-notify 5.1.6
undefined is not a function
TypeError: undefined is not a function
    at Class.module.exports.included (/Users/robert/dev/stud-ember/node_modules/ember-notify/index.js:8:26)
    at Class.superWrapper [as included] (/Users/robert/dev/stud-ember/node_modules/ember-cli/node_modules/core-object/lib/assign-properties.js:32:18)
    at EmberApp.<anonymous> (/Users/robert/dev/stud-ember/node_modules/ember-cli/lib/broccoli/ember-app.js:470:15)
    at Array.filter (native)
    at EmberApp._notifyAddonIncluded (/Users/robert/dev/stud-ember/node_modules/ember-cli/lib/broccoli/ember-app.js:465:45)
    at new EmberApp (/Users/robert/dev/stud-ember/node_modules/ember-cli/lib/broccoli/ember-app.js:138:8)
    at module.exports (/Users/robert/dev/stud-ember/ember-cli-build.js:31:15)
    at CoreObject.module.exports.Task.extend.setupBroccoliBuilder (/Users/robert/dev/stud-ember/node_modules/ember-cli/lib/models/builder.js:70:19)
    at CoreObject.module.exports.Task.extend.init (/Users/robert/dev/stud-ember/node_modules/ember-cli/lib/models/builder.js:50:10)
    at CoreObject.superWrapper [as init] (/Users/robert/dev/stud-ember/node_modules/ember-cli/node_modules/core-object/lib/assign-properties.js:32:18)

The problem was Object.assign, downgrading to ember-notify v5.1.5, and adding the object-assign dependency resolved this for me

Okay thanks. Have pushed v5.1.7 with a polyfill for this.

Closing this as solved.


fix disable join reorder in bucket shuffle join test (#27930)

pick from master
PR #27930
commit c80807a5c7f9454bd4ec8d5a2c829ed986efa653
Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


A wallet with a blank string imageUrl (or invalid url) creates a connection invitation that cannot be received

I don't think this is a Traction-specific issue (see below), and it might be indented behaviour, but raising this for any thoughts and to bring to attention.
If I set my tenant's wallet image_url to a blank string (or any invalid URL) then invitations that are created with /connections/create-invitation end up with a invitation like this:
{"@type": "https://didcomm.org/connections/1.0/invitation", "@id": "a62296a8-a453-4f15-b562-598cf7082b00", "imageUrl": "", "label": "TenantName", "recipientKeys": ["2euwDSvaRw6QzrjBAPCWiqE3iA6YdwPeELW1XgCDZuVi"], "serviceEndpoint": "https://traction-acapy-dev.apps.silver.devops.gov.bc.ca"}

Attempting to receive-invitation that connection invite then throws a 422 with
{"imageUrl": ["Not a valid URL."]}
If using it as an invitation QR code, the BC Wallet generically fails.

So it appears to be any invalid non-formatted URL, but the blank string is a little worse I think as then if you clear it by blanking out the string it still won't work.
Note: in Traction we can probably control this at input validation (at the plugin API, and in the Tenant UI both)
see this issue https://github.com/bcgov/traction/issues/641
but still raising this for any acapy systems not using Traction plugins.

Not sure what a good solution to this would be if required. Assuming a bad image_url gets in there what should happen with these connections? Prevent create-invitation from proceeding? Handle receiving the invitation anyways?

Closing as stale -- reopen if needed.


we use cv2.VideoCapture(1) open D415, which can not work on Jetson Xavier NX

we use realsense-viewer can open D415 camera very well, but we use cv2.VideoCapture(1) to open D415, which can not work well on Jetson Xavier NX. And the screen is green.

Hi @sunbin1357   My research suggests that having a green screen when using cv2.VideoCapture is not a problem that is exclusive to  The link below is an example case of this phenomenon from the Nvidia forum:
https://forums.developer.nvidia.com/t/how-to-slove-opencv-green-screen/82803
Aside from the green screen, what other problems are you having with using the D415 on an Xavier NX, please?

when I use your suggested method, the screen is not green, but is the
following result.
[image: image.png]
MartyG-RealSense<EMAIL_ADDRESS>于2020年7月20日周一 下午10:02写道：

Hi @sunbin1357 https://github.com/sunbin1357 My research suggests that
having a green screen when using cv2.VideoCapture is not a problem that is
exclusive to The link below is an example case of this phenomenon from the
Nvidia forum:
https://forums.developer.nvidia.com/t/how-to-slove-opencv-green-screen/82803
Aside from the green screen, what other problems are you having with using
the D415 on an Xavier NX, please?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/IntelRealSense/librealsense/issues/6867#issuecomment-661059257,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALNJVR2OPOAWFAQN3435ESDR4RFAPANCNFSM4PCJF5XA
.

Can you check that the gstreamer source is valid please?
https://forums.developer.nvidia.com/t/opencv-video-capture-with-gstreamer-doesnt-work-on-ros-melodic/113147/2

[image: image.png]
MartyG-RealSense<EMAIL_ADDRESS>于2020年7月21日周二 下午2:24写道：

Can you check that the gstreamer source is valid please?
https://forums.developer.nvidia.com/t/opencv-video-capture-with-gstreamer-doesnt-work-on-ros-melodic/113147/2
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/IntelRealSense/librealsense/issues/6867#issuecomment-661660528,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALNJVR5WABCLCIIRZZDIGH3R4UYC5ANCNFSM4PCJF5XA
.

There is a gstreamer plugin for RealSense 400 Series cameras.  It may be worth looking at if you are having problems.
https://github.com/WKDSMRT/realsense-gstreamer

Can you provide a way to call the RealSense camera via OpenCV in python？
MartyG-RealSense<EMAIL_ADDRESS>于2020年7月21日周二 下午4:02写道：

There is a gstreamer plugin for RealSense 400 Series cameras. It may be
worth looking at if you are having problems.
https://github.com/WKDSMRT/realsense-gstreamer
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/IntelRealSense/librealsense/issues/6867#issuecomment-661701714,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALNJVRZRLGYODOGFN5AHXS3R4VDRLANCNFSM4PCJF5XA
.

The librealsense Python wrapper's examples page has some OpenCV examples.  If you do a find search in the browser for opencv on that page then it will highlight all the examples that useOpenCV.
https://github.com/IntelRealSense/librealsense/tree/master/wrappers/python/examples

Case closed due to no further comments received.


xschem: 3.0.0 -> 3.1.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/xschem/versions.
meta.description for xschem is: "Schematic capture and netlisting EDA tool"
meta.homepage for xschem is: "https://xschem.sourceforge.io/stefan/"
meta.changelog for xschem is: ""
Updates performed

Version update

To inspect upstream changes

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 3.1.0 with grep in /nix/store/v4pi0d18sbvvkggargjdyhx2sljrzqsr-xschem-3.1.0
found 3.1.0 in filename of file in /nix/store/v4pi0d18sbvvkggargjdyhx2sljrzqsr-xschem-3.1.0

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
xschem

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/v4pi0d18sbvvkggargjdyhx2sljrzqsr-xschem-3.1.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A xschem https://github.com/r-ryantm/nixpkgs/archive/ea5014439245b43bc37d4dad23a64ec79e8c4955.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/v4pi0d18sbvvkggargjdyhx2sljrzqsr-xschem-3.1.0
ls -la /nix/store/v4pi0d18sbvvkggargjdyhx2sljrzqsr-xschem-3.1.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

xschem

Maintainer pings
cc @fedeinthemix for testing.

@fedeinthemix Thank you for reviewing. LGTM


chore(dist): Removed dist/ from git index

Build files should not be in the index.  This will avoid massive diffs in future PRs

There are many different opinions on this. I'm in the "keep dist in source control" camp. The main reasons I think this is valuable:

Easier for people to find the distribution file - there are a lot of reasons this is useful
Less complex releases

I don't have a problem including the dist as long as we make commits to it as simple as: 'Release 1.3.1'
I've done this with several of my libraries and it's never been a problem from me.

The trouble I was running into is that dist/hint.js is auto-generated by gulp, so anytime I make changes to a watched file, we get a identical changes in dist.
dist/hint.js is also tracking all of our require'd files, so that could cause problems in the future if things get out of sync.  (i.e. issues being opened because a bug that was fixed in a patch version of angular-hint was not reflected in latest dist).  It almost becomes the poor man's shrinkwrap.
None of these are insurmountable - thoughts?

I may be misunderstanding, but as long as you don't actually commit the changes until a release comes up then you should be fine, right?

That could work, but the changes will still be in git status and git diff.

Some additional thoughts:

We don't check in node_modules and binaries, so why a compiled file?
This was helpful in me reasoning around the code

At this point, I'm in favor of keeping dist around until we have clear and up-to-date instructions on running the build (i.e. anyone can generate a dist and it'll always be the same).


Implement AE 8.4.0-beta support

A new branch should be started in order to prepare for 8.4.0 AE API changes

No, it will only be done when it's at least beta or stable, I simply don't have the time to track every version.

Can this issue can be reopened now that 8.4 is in beta and quite stable?

better

I don't know if this can be usefull for you, but here's my crashlog when I try to start with the latest current release from AE2 (v.8.4.0):
https://gist.github.com/Fireztonez/75fe5ba5ed71d30ec83970b90952f35a


Remove the action 'Auto-Resolve behavior…' during the download with no conflicts

Storage Explorer Version: 1.5.0
Platform/OS Version: Windows 10/ MacOS High Sierra/ Linux Ubuntu 16.04
Architecture: ia32
Build Number: 20181025.6
Commit: a287009c
Regression From: Not a regression
Steps to Reproduce:

Open one file share which contains one file/directory at least.
Create a new folder on local file system -> Try to download the file/directory to the new folder.
Check the log message during the download.

Expected Experience:
'Auto-Resolve behavior…' doesn't show next to the log message since there are no conflicts.
Actual Experience:
'Auto-Resolve behavior…' shows next to the log message.

Verified on the latest build 20190618.3. This issue still reproduces.


Make it easy to delete agents with memgpt delete

Is your feature request related to a problem? Please describe.
Currently if the user wants to delete an agent (eg to reduce clutter) they have to manually delete folders in ~/.memgpt/agents.
Describe the solution you'd like
Provide a memgpt delete command.

With no args, pulls up a selector
With args, targets the agent name provided
Should ask for confirmation before deleting (default to No)

if the args supported tab completed & ability to do multiple deletions at once would be very nice, doing via api would also be good to specify via an array of names ?


CategoricalIndex + and - should not be set operations?

Related with the issue I just opened (#10038), I relooked at the set operation deprecation issues we had before (xref #8227, #9095, #9630).
To make a summary:

in 0.15.0 we deprecated set operations, only for new TimedeltaIndex it is already numeric operation
in 0.15.1, for numeric indexes this was by accident converted to numeric operation
in 0.16.0, explicit deprecation added for DatetimeIndex
in a future release we want to have it all numeric operations (or TypeErrors if the dtype does not support that operation)

But now, for the CategoricalIndex added, it is a set operation again (but with a warning):
In [1]: idx = pd.Index(pd.Categorical(['a', 'b']))

In [2]: idx
Out[2]:
CategoricalIndex([u'a', u'b'],
                 categories=[u'a', u'b'],
                 ordered=False,
                 name=None)

In [3]: idx - idx
c:\users\vdbosscj\scipy\pandas-joris\pandas\core\index.py:1191: FutureWarning: u
sing '-' to provide set differences with Indexes is deprecated, use .difference(
)
  "use .difference()", FutureWarning)
Out[3]: Index([], dtype='object')

As this is a new index, we should at once use the correct behaviour?
(Which is raising a TypeError I think?)

yep, these are not defined so they get behavior from super-class. Ok, will whip something up. I agree TypeError is correct


ProductCategory->ProductsShowable fails if no BasePrice BUT has Variations with prices

Line 109
if (self::$must_have_price) $filter[] = '"BasePrice" > 0';
does not take in to account if a product has variations with prices but no BasePrice on the parent product

Closed via #513


Merge sbt/zinc and typesafehub/zinc

This ticket is for discussion and planning of merging functionality of sbt/zinc (known before as sbt/incrementalcompiler) and typesafehub/zinc. The end goal of the merge process is to retire typesafehub/zinc into an attic and have sbt/zinc be the place for incremental compilation for Scala.
An initial list of tasks with owners in parenthesis:

[x] publish zinc artifacts to Maven 2
[x] merge class-based-dependencies branch described in sbt/sbt#1104 (@gkossakowski)
[ ] stable and documented Scala API that sbt 1.0 can use
[ ] stable and documented Java API that Gradle/Maven and other build tools written in Java can use
[ ] command line interface and nailgun integration

Any plans to work on this or is this just a "would be nice to have" thing right now?

@sschaef Some of the work is under way. Inputs on any of these parts are welcome while it's jello solid.

@sschaef, I'm working on merging class-based-dependencies branch into sbt/zinc. This means, the best implementation of incremental compilation will be available from this repo.
I added publishing to Maven as a task to show that some work has been already done. The rest is looking for people willing to work on it.

I should add, that turning sbt/zinc into a module that sbt 1.0-M1 can use is the priority.

Great to see some action over here!
About a year ago, github.com/pantsbuild/pants forked zinc in order to apply a few performance, usability, and release-lifecycle improvements. If there is going to be a revival of zinc, we'd love to get unforked and help out there.
Some relevant reviews; some will not cherry-pick cleanly, so it will likely be on us to try and upstream those. Others would likely be easy/useful to patch in.

[perf] https://rbcommons.com/s/twitter/r/2827/
[perf] https://rbcommons.com/s/twitter/r/2190/
[perf] https://rbcommons.com/s/twitter/r/2178/
[correctness] https://rbcommons.com/s/twitter/r/2867/
[feature] https://rbcommons.com/s/twitter/r/2656/ & https://rbcommons.com/s/twitter/r/2666/

The primary reason for the perf reviews is that we have a lot of modules (on the order of ~2000 in some cases) so we run with fairly large analysis caches, and need laziness/soft-references there. Also, pants does its own maintenance of the various working directories (as most other caller would be likely to do: IDEs in particular), and so the analysis hashing that was being done in order to hit the analysis cache was a real bottleneck.

Update: I just finished updating the zinc fork for the most recent APIs... unsure where that's helpful for you all, but it seems that zinc (as it existed a year ago) now requires access to a lot of private APIs: https://rbcommons.com/s/twitter/r/3658/

Thanks for chiming in. Zinc is revived now in the form of sbt/zinc and it's a good time now to contribute; you have many eyeballs available for reviews and discussions.
I scanned the patches you linked:

[perf] https://rbcommons.com/s/twitter/r/2827/

The direction of this patch is very good and overlaps with sbt/sbt#2525. The sbt/sbt#2525 takes it further because it skips the entire classpath lookup part of Analysis look. This is relevant for builds with a large classpath. I already applied some of the changes described in the ticket so looking up Analysis is a bit different now compared to what you see in the old zinc or sbt 0.13 and closer to what you have in your patch.

[perf] https://rbcommons.com/s/twitter/r/2190/

I have no opinion to offer; I'm not familiar with this part of the old zinc. I don't think this patch would be problematic to reapply, though.

[perf] https://rbcommons.com/s/twitter/r/2178/

It looks like it's also related to sbt/sbt#2525

[correctness] https://rbcommons.com/s/twitter/r/2867/

No opinion here as I don't know this part of the old zinc.

[feature] https://rbcommons.com/s/twitter/r/2656/ & https://rbcommons.com/s/twitter/r/2666/

These two look fine to me.

And regarding cherry-picking from either the old zinc or your fork: I'm fine with you bringing over whatever you need to unfork yourself. I hope there won't be too many pantsosims.

Sounds good. The sooner this ticket results in a binary that we can potentially switch to, the sooner it makes sense for us to begin contributing!
re: sbt/sbt#2525: It certainly looks related to the optimization from https://rbcommons.com/s/twitter/r/2178/ ... the most important part there was eliminating classpath (ie filesystem) lookups in cases where we had analysis.

Did you already publish an artifact or can I publish this locally? I would like to test what happens if we throw away the sbt dependency in Scala IDE and instead depend only on zinc.

I'm planning to get something out in a few days.


shared/build/images.go: add go1.4 tag

Noticed there is a Go 1.4 image available on Docker hub but that image is not listed yet in images.go.

thanks!


Incorrect calculation in "Remote user connectivity calculation" section

Under the section, "Remote user connectivity calculation",
It is mentioned we have 2 connection units, but in calculation and diagram, we have only 1 connection unit.

Please update the document as required.

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

ID: 202e9400-44a2-a670-6c8b-4767123427f1
Version Independent ID: cc3ac778-ad09-5243-903e-99222f1bb0d2
Content: About Virtual WAN pricing - Azure Virtual WAN
Content Source: articles/virtual-wan/pricing-concepts.md
Service: virtual-wan
GitHub Login: @cherylmc
Microsoft Alias: cherylmc

@KapilAnanth-MSFT , thank you for your feedback. We'll review this and get back to you shortly!

@cherylmc,
The section "Remote user connectivity calculation" says "(2 scale units + 2 connection units + 2 hub deployments) "
The diagram only depicts "only one connection unit"
The cost calculation features, "1 ER scale unit + 1 connection unit"
Please update the correct number of scale units and connection units in this section.

#reassign:cfields475

Thank you for you dedication to our documentation.
Unfortunately, we have been unable to review this issue in a timely manner. We sincerely apologize for the delayed response. We will create an internal tracking work item to address this issue. For now, we are closing this issue. If you have any additional information you would like to provide, please respond to this issue with any additional details.
Please continue to provide feedback about the documentation. We appreciate your contributions to our community.
#please-close


source code

Hello, I am very much looking forward to the open-source release of your work and am eager to engage in academic discussions with you.

Thank you for your interest in our work. The code is now open source.


chore: Handle both well-known label compatibility for v1alpha5 and v1beta1

Fixes #N/A
Description
This change collapses the Compatible and StrictlyCompatible check into a single command that takes in a variadic list of options that currently allows you to specify values that can be allowed to be undefined in the requirement set. By default, we have AllowUndefinedWellKnownLabelsV1Alpha5 and AllowUndefinedWellKnownLabelsV1Beta1 options which allow the compatibility checks to ignore well-known labels for each API version.
How was this change tested?
make presubmit
Before PR (Scheduling Benchmarking)
=== RUN   TestSchedulingProfile
scheduled 7610 against 21 nodes in total in 2.776334936s 2741.0237508893993 pods/sec
400 instances 10 pods    1 nodes  1.75316ms per scheduling     175.316µs per pod
400 instances 100 pods   1 nodes  17.786427ms per scheduling   177.864µs per pod
400 instances 500 pods   1 nodes  85.996651ms per scheduling   171.993µs per pod
400 instances 1000 pods  3 nodes  190.301ms per scheduling     190.301µs per pod
400 instances 1500 pods  4 nodes  299.967896ms per scheduling  199.978µs per pod
400 instances 2000 pods  5 nodes  412.911611ms per scheduling  206.455µs per pod
400 instances 2500 pods  6 nodes  482.912916ms per scheduling  193.165µs per pod
--- PASS: TestSchedulingProfile (13.82s)
PASS

After PR (Scheduling Benchmarking)
=== RUN   TestSchedulingProfile
scheduled 7610 against 21 nodes in total in 2.790164606s 2727.437651397116 pods/sec
400 instances 10 pods    1 nodes  1.755514ms per scheduling    175.551µs per pod
400 instances 100 pods   1 nodes  17.707346ms per scheduling   177.073µs per pod
400 instances 500 pods   1 nodes  90.669413ms per scheduling   181.338µs per pod
400 instances 1000 pods  3 nodes  195.117416ms per scheduling  195.117µs per pod
400 instances 1500 pods  4 nodes  309.345593ms per scheduling  206.23µs per pod
400 instances 2000 pods  5 nodes  405.330403ms per scheduling  202.665µs per pod
400 instances 2500 pods  6 nodes  468.279694ms per scheduling  187.311µs per pod
--- PASS: TestSchedulingProfile (13.90s)
PASS

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Benchmarking just the function shows that the function runs slightly slower but this is a reasonable trade-off given code readability and simplicity
func BenchmarkRequirementsOld(b *testing.B) {
	reqs := scheduling.NewRequirements()
	reqs2 := scheduling.NewRequirements()
	for i := 0; i < 100; i++ {
		reqs.Add(scheduling.NewRequirement(fmt.Sprintf("key%d", i), v1.NodeSelectorOpIn, "value"))
		reqs2.Add(scheduling.NewRequirement(fmt.Sprintf("key%d", i), v1.NodeSelectorOpIn, "value"))
	}
	b.ResetTimer()
	for i := 0; i < b.N; i++ {
		reqs.CompatibleOld(reqs2)
	}
}

func BenchmarkRequirementsNew(b *testing.B) {
	reqs := scheduling.NewRequirements()
	reqs2 := scheduling.NewRequirements()
	for i := 0; i < 100; i++ {
		reqs.Add(scheduling.NewRequirement(fmt.Sprintf("key%d", i), v1.NodeSelectorOpIn, "value"))
		reqs2.Add(scheduling.NewRequirement(fmt.Sprintf("key%d", i), v1.NodeSelectorOpIn, "value"))
	}
	b.ResetTimer()
	for i := 0; i < b.N; i++ {
		reqs.Compatible(reqs2, scheduling.AllowUndefinedWellKnownLabelsV1Alpha5)
	}
}

BenchmarkRequirementsOld
BenchmarkRequirementsOld-10    	   12974	     92027 ns/op
PASS

BenchmarkRequirementsNew
BenchmarkRequirementsNew-10    	   12880	     93375 ns/op
PASS


Long running test

This is still somewhat flaky and more work needs to be done, but I'd like some preliminary reviews on it.

I believe this test is now finalized, using a Small server we don't encounter the kernel issue anymore.
Added the notebooks suggested by @LaVLaS as additional workloads and now the run time in my PSI cluster is ~20 minutes give or take a few seconds.
I will need to open a PR to add warning suppression in those notebooks, otherwise our own tests gets tripped up by the warning and thinks that the execution has failed at some point. I would hold off on merging until then.
@vasukulkarni

LGTM in general

Updated to pull notebooks from my own fork
PR test will be at https://opendatascience-jenkins-csb-rhods.apps.ocp4.prod.psi.redhat.com/job/rhods-ci-pr-test/78/

Unexpected failures in previous run, started another one: https://opendatascience-jenkins-csb-rhods.apps.ocp4.prod.psi.redhat.com/job/rhods-ci-pr-test/79/

There are quite a bit of failed test cases in the PR , need to check for infra or test issues.

Latest Jenkins run at https://opendatascience-jenkins-csb-rhods.apps.ocp4.prod.psi.redhat.com/job/rhods-ci-pr-test/90/


Can't ADD things to /var/www/laravel/ in the workspace

I need to dynamically ADD a few files to the workspace container.  For some reason, I can ADD a file from Dockerfile to certain directories, but not others.
Near the bottom of workspace/Dockerfile (around "Final Touch"), I've added the following:
#
#--------------------------------------------------------------------------
# Final Touch
#--------------------------------------------------------------------------
#

COPY ./FOO.txt /var/www/laravel/
ADD ./FOO.txt /usr/local/etc/

When I do docker-compose up -d and go into the container, I see FOO.txt in /usr/local/etc/, but not in /var/www/laravel/.
Is /var/www/laravel/ somehow locked?  What is the best way to ADD files to this directory?

@markdev The directory /var/www/laravel/ is where the volume for your laravel app gets mounted by docker-compose. Since docker-compose mounts happen after building the containers, your FOO.txt is probably getting overwritten.
I suggest adding your files in the same directory as your laravel project on your host machine, you'll see the file along with the rest of your project in /var/www/laravel/ in workspace.
Let me know if this fixes your problem :)

@philtrep Thanks for the prompt response!
I can and do do this now; currently I am running a shell script to cp the .env and docker-compose.yml files.  But that is a bad practice; it relies on the environment outside of the containers.  I'd like to be able to do this within the docker ecosystem, like with a RUN command or a command: in the .yml file.  All these attempts run into the same problem.
Is there a way to run this in docker after the volumes are mounted?

@markdev Glad to hear it.
I am closing this issue since your problem is resolved.
About your follow-up, I am not exactly sure what it is you are trying to do. Everything in your project folder should already be available from within your containers.
I suggest going over to Gitter for project specific questions, the other contributors might be able to give you better answers.


Add openapi for verison 22

title says it all

done https://github.com/dahag-ag/keycloak-openapi/releases/tag/v22.0.1-0


Set the website of this GitHub repo to the demo

http://daemonite.github.io/material/
Example:

Thanks for that, good catch.


Exported ONNX model uses wrong size for index tensors

When exporting to ONNX, dlrm_s_pytorch.py passes the dynamic_axes parameter to torch.onnx.export() and sets the size of the index tensors to batch_size:
https://github.com/facebookresearch/dlrm/blob/78d70458e71a62a8e0161fc657c7a5e24b4ff24d/dlrm_s_pytorch.py#L1307-L1320
However, the index tensor for each embedding table has a length of batch_size * num_indices_per_lookup:
$ python3 -m pdb ./dlrm_s_pytorch.py --save-onnx --mini-batch-size=3 --num-batches=10 --data-generation=random --
arch-mlp-bot=256-128-32 --arch-mlp-top=512-256-1 --arch-sparse-feature-size=32 --arch-embedding-size=100000-100000-100000-100000 --num-indices-per-loo
kup=5 --num-indices-per-lookup-fixed=True --arch-interaction-op=dot
(Pdb) b 1318
Breakpoint 2 at /home/mneilly/Esperanto/dlrm-fork/dlrm_s_pytorch.py:1318
(Pdb) r
...
(Pdb) dynamic_axes
{'dense_x': {0: 'batch_size'}, 'pred': {0: 'batch_size'}, 'offsets': {1: 'batch_size'}, 'indices_0': {0: 'batch_size'}, 'indices_1': {0: 'batch_size'}, 'indices_2': {0: 'batch_size'}, 'indices_3': {0: 'batch_size'}}
(Pdb) [x.shape for x in lS_i_onnx]
[torch.Size([15]), torch.Size([15]), torch.Size([15]), torch.Size([15])]
(Pdb)

Let me consult with a colleague. We will get back to you shortly.

We have used dynamic_axis parameter to allow the ONNX model saved by this code to run with variable batch size during inference. However, we have only tested this code in the context of MLPerf inference ONNX runtime backend, where one-hot lookups are used and therefore num_indices_per_lookup=1. So, it's possible we have missed something. Is this run crashing?

In the provided output, num-indices-per-lookup=5 and mini-batch-size=3 resulting in each tensor in lS_i_onnx having a shape of 15 as shown. When num-indices-per-lookup != 1 use of batch_size for these inputs seems clearly incorrect to me since their shape is mini-batch-size * num-indices-per-lookup, i.e. - not batch_size....
When exporting an ONNX model with:
python3 -m pdb ./dlrm_s_pytorch.py --save-onnx --mini-batch-size=3 --num-batches=10 --data-generation=random --arch-mlp-bot=256-128-32 --arch-mlp-top=512-256-1 --arch-sparse-feature-size=32 --arch-embedding-size=100000-100000-100000-100000 --num-indices-per-lookup=5 --num-indices-per-lookup-fixed=True --arch-interaction-op=dot --save-onnx

And attempting to load it into onnxruntime, I see the following shape inference error regardless of mini-batch-size=1 or 3:
root@b73d7e7986ec:/dlrm# python
Python 3.7.3 (default, Jul 25 2020, 13:03:44)
[GCC 8.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import onnxruntime as rt
>>> sess = rt.InferenceSession('dlrm_s_pytorch.onnx', rt.SessionOptions())
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/local/lib/python3.7/dist-packages/onnxruntime/capi/session.py", line 158, in __init__
    self._load_model(providers or [])
  File "/usr/local/lib/python3.7/dist-packages/onnxruntime/capi/session.py", line 177, in _load_model
    self._sess.load_model(providers)
onnxruntime.capi.onnxruntime_pybind11_state.Fail: [ONNXRuntimeError] : 1 : FAIL : Node (Concat_114) Op (Concat) [ShapeInferenceError] All inputs to Concat must have same rank

This was run with the following Dockerfile using nightly PT and nightly ORT:
FROM debian:latest

RUN DEBIAN_FRONTEND=noninteractive apt update && apt install -y python3 python3-pip git cmake protobuf-compiler libprotoc-dev
RUN update-alternatives --install /usr/bin/python python3 /usr/bin/python3 100

RUN pip3 install numpy
RUN pip3 install --pre torch torchvision torchaudio -f https://download.pytorch.org/whl/nightly/cpu/torch_nightly.html

RUN git clone https://github.com/facebookresearch/dlrm.git
RUN cd dlrm && pip3 install -r requirements.txt
RUN pip3 uninstall -y onnx

RUN git clone --recursive https://github.com/onnx/onnx.git \
        && cd onnx \
        && python3 setup.py install

RUN pip3 install ort-nightly

If I look at the PyTorch ONNX documentation (search for first and fifth occurrence of "dynamic_axes" in https://pytorch.org/docs/stable/onnx.html#id18), I see that the dictionary specified for dynamic_axes specifies the dimension in which the batch is growing and its name, but it does not necessarily specify the size of the batch.
Let me know if I'm missing something? and where exactly do you think the batch size should be specified?

Looks like this is resolved as much as possible. Closing.


CON-4938: added Exception catch if media entity was deleted

theres no cascade delete for media and image entity.
problem was that an exception was thrown
replaced an if try ... catch

Somehow the failing test somehow depends on the ImageImporterTest
befor the ImageImporterTest was running before the LegacyLifecycleTest
after i moved it to Integration it runs after the LegacyLifecycleTest
At the moment the LifecycleTest receives just one change
That one is an insert change and the price in the payload is 123.99
that is the price set in LifecycleTest::insertVariants()

Coverage increased (+0.3%) to 38.527% when pulling 6aa655a0eb6e1b03ffee1e21e19b9a56e87ce095 on CON-4938 into a86692540e89ddf78e7e08ae528f441df495bc21 on master.

Coverage increased (+0.3%) to 38.527% when pulling 6aa655a0eb6e1b03ffee1e21e19b9a56e87ce095 on CON-4938 into a86692540e89ddf78e7e08ae528f441df495bc21 on master.

Coverage decreased (-0.3%) to 37.914% when pulling 01752dbe0fe17e9e7809d9f0cb88ac06b9f36657 on CON-4938 into a86692540e89ddf78e7e08ae528f441df495bc21 on master.

Coverage increased (+0.6%) to 38.802% when pulling 37d8919f9d6ed945066f226d38fade638b73d8ee on CON-4938 into a86692540e89ddf78e7e08ae528f441df495bc21 on master.

Coverage increased (+0.6%) to 38.802% when pulling 37d8919f9d6ed945066f226d38fade638b73d8ee on CON-4938 into a86692540e89ddf78e7e08ae528f441df495bc21 on master.

Coverage increased (+0.6%) to 38.802% when pulling 2aa122ee9c760b49487f19dc16eeff9283fa13d4 on CON-4938 into a86692540e89ddf78e7e08ae528f441df495bc21 on master.

Coverage increased (+0.6%) to 38.804% when pulling b16b15b64b9a3f58031c5f22a88c94f068aff5bc on CON-4938 into a86692540e89ddf78e7e08ae528f441df495bc21 on master.


Overwrite validation error message

I would like to overwrite the way the error message is handled. I want to use the id of the field to select it and them use the placeholder attribute to show the error message.
How do I overwrite the default validation error?
This is what I have:
$('#generator').isHappy({
        errorTemplate: function( el ) {
            if(el && typeof(el) !== 'undefined') {
                console.log( el );
            }
        },
        fields: {
          // but you could certainly do $('[name=name]') as well.
          '#first-sleeper-first-name': {
            required: true,
            message: 'Might we inquire your name'
          },
          '#first-sleeper-last-name': {
            required: true,
            message: 'How are we to reach you sans email??',
            test: happy.email // this can be *any* function that returns true or false
          }
        }
  });

I keep getting these error on validation error:

Any help?

Custom error messages have been added as of v0.9.
To change the error message, return an instance of Error. For example:
$('#form').isHappy({
    fields: {
        '#birthday': {
            required: true,
            test: function() {
                if(isEmpty) {
                    return false;
                }
                if(isFuture) {
                    return new Error(‘Your birthday must have already happened.’);
                }
                if (isWednesday) {
                    return new Error(‘Your birthday cannot have happened on a Wednesday.’);
                }
                return true;
            },
            message: ‘Please provide a valid birth date.'
        }
    }
});


materialboxed inside of Tabs, weird interaction with the overlay

Hi. Been working on my personal site and I'm trying to put images inside my Tab sections.
Getting some weird interactions:

Only the tabs section gets covered by the overlay
When the image expands, it hides beneath images (also 'materialboxed') that are outside the tab section

I just want the images within my tab section to behave like it should. The overlay to cover the full screen with a caption where it sits on top of everything else. What should I do?
Thanks!
Screenshots of whats happening

Can you post some code samples?

Closed due inactivity, feel free to reopen it if it is still necessary.


feat: Set input PSK to sensitive = true. Validate length of PSKs

Description
Setting the tunnel PSK inputs to sensitive = true so that if Terraform errors out on a plan (for example, a PSK longer than 64 characters), the error message does not contain the PSK. Also, validate the length of the PSKs
Motivation and Context
This complements PR#86, but it didn't cover the case for an erroneous plan.
Breaking Changes
None.
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

Some minor cleaning is needed. :)

Wonderful, thank you for the review! I've addressed your points 😄

Almost. Please remove another validation block, and we are good to go.

Whoopsie, that one went past me 😄


pull request for e2e test at 01/17/2017 07:15:10

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


safe direct access to underlying CBCentral and CBPeripheral

@tehjord Here is a safer solution to adding direct access to the underlying central and peripherals.
By default, the framework won't support access, but if the user adds a configuration file, SwiftyBluetoothConfiguration.xcconfig to their root directory for the project with SWIFT_ACTIVE_COMPILATION_CONDITIONS= $(inherited) DIRECT_ACCESS, it will allow direct access.
If you like this, I can add a more detailed description to the README for anyone who does want to enable direct access.

@tehjord I realized that your solution with using the retrievePeripherals method that you made available works well for our purposes 😄, as calling the underlying retrievePeripherals method twice is not a big inefficiency ding. However, we still would need something like the solution I proposed here to gain underlying access to the CoreBluetooth central and peripherals if we want to avoid keeping our own fork up to date (which would be preferable haha). What are your thoughts on this solution?

Hi Jake,
Frankly I don't know about giving access to the CoreBluetooth central. Even though your solution is as non-disruptive as possible, I'd rather avoid having this kind of stuff in the project to keep it as simple as possible, less maintenance and less wondering (by other people) about why these macros are there and whats not meaning the barrier to modifying the code is lower.
What I would need is very hard convincing that what you need to do cannot instead be done by extending the library's functionalities. Most importantly, I need to be convinced that having access to the underlying central, which I have worked kinda hard to hide away by having a CentralProxy in the first place, that having access to that central is something other folks who use the library would need, and not just you and your team in particular.

Definitely can understand the hesitation. For people using this library to manage Bluetooth for an application that communicates with a Nordic Semiconductor nRF51 or nRF52, not being able to access the underlying CBCentral and CBPeripheral makes this framework incompatible with Nordic's SDK framework, which requires these underlying CoreBluetooth objects to be initiated:
let initiator = DFUServiceInitiator(centralManager: centralManager, target: peripheral).with(firmware: selectedFirmware)
I'm not sure if this is compelling enough for you, but it would be essential for anyone using this SDK or other frameworks like it.

I see, humm, how about an initializer for Central where you can pass in your own CBCentralManager? You could then use that Central instance instead of the sharedInstance.

Hmm, that's an interesting solution, but it then requires that one initialize a CBCentralManager and uses it to initialize Central before ever using the library, otherwise you will not be able to later gain access. Also I feel like that may be prone to the error of creating multiple CBCentralManagers, which is contrary to the singleton model used here.

Technically, you can also create multiple CBCentralManager instance, wouldn't that fix your problem?

Hmm, this is something we could do, but it really seems like an unideal solution as its generally recommended to avoid that as much as possible: https://forums.developer.apple.com/thread/20810

Also @jordanebelanger looping back about this, is this still something you would like to avoid incorporating into the project? I can fix the outstanding conflicts but if the intent of this PR is definitely something you don't to support I can go ahead and just close this.

Hey @jakerockland nice to hear from you.
I've been looking at this PR for a good 10 minutes and, yea, I don't know about this still. I get this feeling it sort of doesn't fit the theme of the library.
I've added a sharedInstance "setter" if you will to support a peripheral restore identifier. I still think the cleanest solution for something like this would be for the user to be able to pass in his own CBCentralManager instance and calling SwiftyBluetooth.setSharedCentralInstanceWith(cbCentralManager or something similar.
An other avenue perhaps, I haven't done objective-C much recently but it might be cleaner in the end to Swizzle the CBCentralManager and CBPeripheral delegate methods so that this Library is omniscient as far as CoreBluetooth is concerned. This would cause some other probably fixable issues, but at least you wouldn't run into the risk of users kamikazing the library by desetting the CBCentralManager's delegate.

Hey @jordanebelanger, definitely understand how this PR is not necessarily in the spirit of this library. I think for now it makes sense for me to keep maintaining our fork and keeping it up to date with your library here, because its the path of least resistance for our purposes right now. I'd rather that to exploring other more nuanced solutions as there are other things higher up on our development priority list for now. Will close this PR though! 👍


Edited test to allow for lowercase hex code

Pre-Submission Checklist

[x] Your pull request targets the staging branch of freeCodeCamp.
[x] Branch starts with either fix/, feature/, or translate/ (e.g. fix/signin-issue)
[x] You have only one commit (if not, squash them into one commit).
[x] All new and existing tests pass the command npm test. Use git commit --amend to amend any fixes.

Type of Change

[x] Small bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds new functionality)
[ ] Breaking change (fix or feature that would change existing functionality)
[ ] Add new translation (feature adding new translations)

Checklist:

[x] Tested changes locally.
[x] Closes currently open issue (replace XXXX with an issue no): Closes #13535

Description

Changed the tests to allow for uppercase or lowercase hex code values. Ex: #ff7d00 or #FF7D00 as per issue.

Assuming we have no problem with uppercase CSS properties, I might recommend that we add the i flag to the end of the Regex instead of an 'or' test case. It will allow for the case insensitivity needed both for the Hex codes and for the CSS properties. I will ask if there is any reason not to use the i flag and get back to you.

Adding the i flag would be problematic in this challenge, as class names are case-sensitive. Demo: http://codepen.io/systimotic/pen/ryLVLG?editors=1100

@dhcodes: Yes, I pondered that case as well. Funnily enough, I also had to do a quick fiddle just to make sure. I decided on the or because I  don't think there's any sense in mixing the the cases of the hex code values,  therefore my belief that campers should adopt using either full lowercase (#ff7d00) or full uppercase (#FF7D00), not an amalgam of both. Alas, I am not an authority on this matter, so I will leave it up to you. Thanks.

@systimotic thanks friend, hadn't thought of that. LGTM @cdrainxv Thanks for contributing! 👍 💯 🌮


Setting up WiFi Credentials via Temporary Access Point

I've previously used the serial CLI to configure my WiFi settings on the HomeSpan ESPs.
I thought I would try out the Access Point method.
I was not successful.
My SSID contains spaces and the "connecting to" message shows my SSID with + replacing the spaces.
Say my SSID is "My Wifi Access", the connecting page shows "My+Wifi+Access".
I tried with a temporary SSID without spaces and was successful.

Thanks for catching this.  Bug has been fixed in the dev branch --- please give it a try.  The fix will also be included in the next release.

No problem!
I will try it again soon.

HomeSpan 1.4.0 has just been released and includes this bug fix.


iOS support request (Pythonista, iOS  App)

Would be nice to be able to pip install hug on iOS, most notably Pythonista 3 iOS app.  Unfortunately I don't know much about this process.  However after some talks on the Pythonista forum it seems that hug should be able to run in Pythonista given the correct install options. As it appears that hug and falcon can be installed as pure python Libs. Pythonista supports py2.7 as well as 3.5.
I tried installing hug using pip install hug, I think it's hanging at the point it's trying to install the cmd line launcher.  I am sorry that I am vague on the details as I don't really understand the process.  But I am hoping it's pretty evident  why the pip install would fail on this os.
Maybe there are some switches that exist already that would do the job.
Anyway, seems like a great lib.  We can use other microframe works in Pythonista such as flask , bottle etc.  would be great to be able to use hug also.

I did not try this myself but here are the steps to replicate:

Launch the Pythonista app on iOS (http://omz-software.com/pythonista/)
Install StaSH (https://github.com/ywangd/stash) to provide a terminal, pip, etc.
Launch StaSH and type pip install falconto make sure that prereq is properly installed

Note: requests version 2.9.1 is pre-installed in Pythonista.

In StaSH, type pip install hug.


Fix error no such file README.md

Fixes  FileNotFoundError: [Errno 2] No such file or directory: 'README.md'

Good catch!

my bad!

it's also in MANIFEST.in

Coverage remained the same at 78.127% when pulling 00ed72e8b135ed6443c9c0c8c1164d65f254ddd7 on robmoorman:patch-1 into fedec87070e4bb14e49687b3ff2e248bec7506df on CityOfZion:development.


Migrations not created for column type change (default number to double precision)

Hi,
I am still running 4.5.9 and have seen that when changing the columnType to double precision from the default value for number (which is integer for postgres in MikroORM), it does not generate a migration.
Changing the code from
  @Property({ type: 'number', nullable: true })
  @Field({
    description: 'Fee for the job.',
    nullable: true,
  })
  public fee?: number;

to
  @Property({ type: Number, columnType: 'double precision', nullable: true })
  @Field({
    description: 'Fee for the job.',
    nullable: true,
  })
  public fee?: number;

should generate a migration when running migration create.
    this.addSql(
      'alter table "job" alter column "free" type double precision;',
    );

Please upgrade to v5, schema diffing is completely rewritten, no plans to backport any changes to v4. Will be happy to reopen if it does not work in v5, but I am sure it will.

Thank you for your prompt reponses! This might perhaps be the greatest node open source project on github with amazing support :D


Deadlock condition at v0.1.0

If you create an actor like:
func (a *UActor) Fun() {
    msg := <- a.Receive
    switch msg.(type) {
    case msgWithFrom:
        m := msg.(msgWithFrom)
        m.from <- m.message
        a.Fun()
    }
}

It is correct, but if you do not get the result from the channel send in the message.
You will receive a deadlock. Because you will create the second get from Receive channel.
And first already blocking, obviously you will create another block. Then program deadlock

We can meet more confusing if you code like:
type EchoServer struct {
    Actor
}

func (echo *EchoServer) Fun() {
    msg <- echo.Receive
    if v, ok := msg.(msgWithClient); ok {
        v.client <- v.content
        echo.Fun()
    } else if _, ok := msg.(closing); ok {
        close(echo.Receive)
    }
}

func main() {
    // Create echo server
    self := make(chan string, 2)
    defer close(self)

    echoServer <- msgWithClient{self, "Hello"}
    echoServer <- msgWithClient{self, "World"}
    <- self
    <- self
}

Can be fine.

So I think this library is totally out of value, I will close it.

I finally got reason:
也就是說，如果你沒有幫channel 設定好buffer (也就是 make(chan int, 1))先給他個預設空間的話． channel <- value 會一直等到…. <- channel 才會順利結束． 這也是如果你直接使用channel 而沒有進入goroutine或是給予buffer就會deadlock
package main

import "fmt"

func main() {

	messages := make(chan string)

	messages <- "buffered" //會有deadlock，因為會停到直到跑到 <-messages
	messages <- "channel"  //會有deadlock，因為會停到直到跑到 <-messages

	fmt.Println(<-messages)
	fmt.Println(<-messages)
}


Add Ansis JavaScript library

Hello @donatj,
Tne JavaScript library ansis for colorise terminal outputs supports environment variables FORCE_COLOR NO_COLOR and flags --no-color --color.
Can you please add this library to the list on force-color.org.
Thanks!

Thanks for the submission!


Improve lists kartlag infobox

Changed the close/open button on the layer menu (kartlag)
Adjusting icon size in layer menu so they look better
Icons on infobox are the same as the layer
Center the circular progress in infobox
Add badge with exclamation mark in infobox when GetFeatureInfo API returns error

I have now made changes based on your comments:

Remove duplicated code.
Made "layers" icon larges and moved so it fits with the other icons.
List element is not changed to white background if there is no "faktaark".


Dependabot + Terraform ecosystem

Hi @cujarrett,
Dependabot supports the Terraform ecosystem, in case this is of interest? It will keep the Terraform providers up-to-date.

Thanks @case , I should add this to my other terraform projects too.

:tada: This PR is included in version 1.46.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Add one-arg method Duplicated(x)

Instead of writing
x = some_constructor(params...)
dx = make_zero(x)
xdx = Duplicated(x, dx)

this wants to make it easy to just look after one thing,
xdx = Duplicated(some_constructor(params...))

and later get dx = xdx.dval out when you need it. Or not... add methods which consume the gradient like update!(::Duplicated) instead of unpacking.
Should there also be DuplicatedNoNeed(x), and perhaps BatchDuplicated(x, n::Int)? Or [edit] perhaps MixedDuplicated(x) is the closest other struct here.

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 89.63%. Comparing base (037dfed) to head (9e26b67).
Report is 238 commits behind head on main.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@             Coverage Diff             @@
##             main    #2118       +/-   ##
===========================================
+ Coverage   67.50%   89.63%   +22.12%
===========================================
  Files          31        9       -22
  Lines       12668      463    -12205
===========================================
- Hits         8552      415     -8137
+ Misses       4116       48     -4068

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

🚨 Try these New Features:

Flaky Tests Detection - Detect and resolve failed and flaky tests

My only concern about this is that it's rather reverse-mode centric. On the other hand, since there's no universally obvious candidate for what to put in there for forward mode, I guess it's fine to make this method favour reverse mode?

Yeah, I don't see any obvious use for it for enzyme so it's probably fine.

Oh no, now I'm worried this PR will turn into a punching bag for API / documentation complaints.
From a human UI perspective, it does seem a bit odd to re-use the exact same struct for forward & reverse. Especially since the forward mode case where you might plausibly construct Dual(pi, 1) with your bare hands is precisely the case where Duplicated is useless, perhaps even misleading, in reverse mode:
julia> xdx = Duplicated(3.0, 100.0);

julia> autodiff(Forward, abs2, xdx)  # ok, like dual numbers
(600.0,)

julia> autodiff(Reverse, abs2, Active, xdx)  # maybe this should be an error?
((nothing,),)

julia> xdx  # Duplicated{Float64} is never a useful container for reverse mode
Duplicated{Float64}(3.0, 100.0)

julia> y = (array = [1.0, 2.0], float = 3.0);

julia> ydy = Duplicated(y, make_zero(y));

julia> autodiff(Reverse, y -> sum(y.array .* y.float), Active, ydy)
((nothing,),)

julia> ydy.dval  # this isn't useless, but does require some understanding
(array = [3.0, 3.0], float = 0.0)

You need ydy = MixedDuplicated(y, Ref(make_zero(y))) to match the result of the friendly gradient(Reverse, y -> sum(y.array .* y.float), y) here.
Anyway, this PR changes nothing at all about forward mode.
Please make a separate issue to discuss changing from Duplicated to some new Dual for forward mode. (Or to discuss more clearly documenting things.)
The one thing that is on-topic for this PR is that we could make Duplicated(x) give a helpful error on x::Float64, maybe all isbits(x) or something. That's non-breaking, and would improve friendliness compared to the present methoderror.  Duplicated(1.0, 0.0) is entirely useless for reverse mode (you may as well make Const(1.0)) as far as I can tell. And should occur only accidentally in forward mode (i.e. you get the dx from somewhere which could plausibly give you a nonzero value) hence you never want the one-argument constructor.

I'm very down to make/enforce the use of a separate Dual type for forward mode (which the Rust Enzyme stuff does), but yeah that's separate from here, if you want to open a different issue/PR on that.
Obviously that would be quite breaking [and need corresponding checks throughout enzyme].
Part of the reason for the one duplicated for both is that from the implementation (as opposed to the user side) they are very much the same, in the sense that a separate shadow data structure is created and maintained (hence the very literal name "duplicated" as in we duplicated the data structure from primal to shadow)

Oh no, now I'm worried this PR will turn into a punching bag for API / documentation complaints.

Anyway, this PR changes nothing at all about forward mode.

Please make a separate issue to discuss changing from Duplicated to some new Dual for forward mode. (Or to discuss more clearly documenting things.)

I don't think that's a fair response. Like it or not, Duplicated is a fundamental part of the API for Forward mode, so IMO it is quite relevant to talk about how changes to Duplicated can make the (already highly confusing and second-class) Forward mode API feel even more confusing and second-class.
If we did disentangle the APIs so Forward mode didn't use Duplicated then I think this'd be a valid dismissal, but since they share it I think it's valid to worry about this making the API even more confusing / hard to teach.