INSTALL error

❓ Questions and Help
I follow the INSTALL.md to install the cityscapesScripts, like that:
git clone https://github.com/mcordts/cityscapesScripts.git
cd cityscapesScripts/
python setup.py build_ext install
Then I get error

Traceback (most recent call last):
File "setup.py", line 27, in
readme = f.read()
File "/usr/lib/python3.6/encodings/ascii.py", line 26, in decode
return codecs.ascii_decode(input, self.errors)[0]
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 302: ordinal not in range(128)
So, how can solve it?

hello, @mrsempress  I meet the same problem as you, how do you solve it?

hello, @mrsempress I meet the same problem as you. Could you tell me how do you solve it?

I install pytorch1.1 using CUDA9.0.


Your remote version of WPGatsby is not within the accepted range (~0.4.14)

Hi,
I recently updated the WPGatsby plugin, in my headless setup, to 0.5.3.
After updating, my Netlify build fails with the error:
9:28:10 AM: error  gatsby-source-wordpress  Your remote version of WPGatsby is not within the accepted range (~0.4.14)
9:28:10 AM: 	Download v ~0.4.14 at https://github.com/TylerBarnes/using-gatsby-source-wordpress-experimental/tree/master/WordPress/plugins or update via https://headless.apsspecialistvehicles.co.uk/wp-admin/plugins.php
9:28:10 AM: Reasons:
9:28:10 AM: - WPGatsby 0.4.14 supports WPGraphQL 0.10.3. Version 0.4.13 and before had a bug where making a published post into a draft wouldn't delete the post in Gatsby.

I thought perhaps I needed to update the WPGraphQL plugin as well, so I updated that to 0.13.3.
However this also failed with the error:
10:17:27 AM: error  gatsby-source-wordpress  WPGatsby and WPGraphQL are both outside the accepted version ranges.
10:17:27 AM: visit https://github.com/TylerBarnes/using-gatsby-source-wordpress-experimental/tree/master/WordPress/plugins to download the latest versions.
10:17:27 AM: Reasons:
10:17:27 AM: - WPGraphQL 0.10.0 introduced a large number of changes that required internal source plugin code changes. A big feature is improved support for WordPress previews and improvements to how Menus are handled. 0.10.3 fixed a private post regression that could cause cold builds to fail.
10:17:27 AM:     V0.11.0 introduced breaking changes, but none that will affect Gatsby users. https://github.com/wp-graphql/wp-graphql/pull/1407
10:17:27 AM:     Head to https://github.com/wp-graphql/wp-graphql/releases/tag/v0.10.0 for more information on upgrading.
10:17:27 AM: - WPGatsby 0.4.14 supports WPGraphQL 0.10.3. Version 0.4.13 and before had a bug where making a published post into a draft wouldn't delete the post in Gatsby.

Is this latest version not functioning correctly or is there a later version of both WPGatsby and WPGraphQL that work together?
Currently WPGatsby 0.4.17 and WPGraphQL 0.10.3 work without error, so not an urgent issue but it prevents me keeping the plugin up-to-date.
Thanks,
Gary

Hi Gary, thanks for opening this issue. The error message is a bit confusing because there is another scenario which is that your source plugin needs to be updated. In later versions this error message was updated to include additional instructions about that. Please update your version of gatsby-source-wordpress-experimental and this error will go away :)
Thanks again


Update README.md

Description
What is the current behavior?

What is the new behavior?

Does this introduce a breaking change?
Checklist

[ ] Created tests which fail without the change (if possible)
[ ] Extended the README / documentation, if necessary

Note: this is a test PR to see if CI runs with forks or not

Awesome, looks like adding a label triggered integration tests.


Custom backend raises a TypeError

Hello,
I'm trying to integrate the groups present in my SAML response directly into Django groups. I saw in the docs that you can do this with a Custom User Model, except that I'm in the middle of a project, I don't want to change all my default model.
So instead I'm trying to create a backend that will allow me to do what I want. But i'm having a hard time with that error :
user = auth.authenticate(
  File "/var/www/html/api/venv/lib/python3.8/site-packages/django/views/decorators/debug.py", line 42, in sensitive_variables_wrapper
    return func(*func_args, **func_kwargs)
  File "/var/www/html/api/venv/lib/python3.8/site-packages/django/contrib/auth/__init__.py", line 76, in authenticate
    user = backend.authenticate(request, **credentials)
  File "/var/www/html/api/venv/lib/python3.8/site-packages/djangosaml2/backends.py", line 168, in authenticate
    user = self._update_user(
  File "/var/www/html/api/venv/lib/python3.8/site-packages/djangosaml2/backends.py", line 212, in _update_user
    modified = user_attr(attr_value_list)
TypeError: __call__() takes 1 positional argument but 2 were given

This is my backend empty for now :
from djangosaml2.backends import Saml2Backend

class CustomSaml2Backend(Saml2Backend):
    def update_user(self, user):
        user = super(CustomSaml2Backend, self).update_user(user)
        return user

All good I fix my error. Forgot to remove djangosaml2 default backend. Now it's working.
Also I created my backend like this.
def _update_user(self, user, attributes, attribute_mapping,
                   force_save=False):

       user = super(CustomSaml2Backend, self)._update_user(
           user, attributes, attribute_mapping, force_save=False
       )


Reduce compile times by removing dependencies

I measured the compile time of the blog_os project with the new -Z timings flag:

The x86_64 crate and especially its ux and array-init dependencies take very long to compile. Maybe it's possible to remove or replace these dependencies somehow.

I opened #91 to evaluate the compile times without ux. New timings:

Since  #116, array-init is also gone. Only three dependencies are left:

bit_field with no dependencies,
bitflags with no dependencies, and
cast with a build-dependencies: rustc_version -> semver -> semver_parser.

With cast removed in #124, I think we can close this issue given that the two remaining dependencies are fairly lightweight.


Last block of YAML is invalid

You define variables MAJOR_RUN and MINOR_RUN and refer to them as MAJOR and MINOR.
That doesn't work

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

ID: 77c58a78-a567-e99a-9eb7-62dddd1b90b6
Version Independent ID: 680a79bc-11de-39fc-43e3-e07dc762db18
Content: Expressions - Azure Pipelines
Content Source: docs/pipelines/process/expressions.md
Product: devops
Technology: devops-cicd-process
GitHub Login: @juliakm
Microsoft Alias: jukullam

@Fvdthillart Thanks for flagging this! An updated example is going up now.


Channel order

As of now channels are not given in any particular order:
    @property
    def channels(self):
        """
        The channels that has something on them
        """
        chans = [key for key in self._data.keys()]
        return chans

[key for key in self._data.keys()]  should be list(self._data.keys())?

I guess sorted(list(self._data.keys())) is what we are really after.


[W-10813715] improve visibility for hyperlinks

ref: W-10813715
update CSS to increase visibility of hyperlinks:

when not focused or hovered, hyperlinks are now in darker color to meet the minimum contrast ratio
when mouse-hovered, it has a light blue background, similar to the footer items in mulesoft.com
when keyboard-focused (use TAB key to cycle through elements), it shows a gray outline around the link
if visited, the font color is purple
when mouse-clicked, it has both the light blue background and the gray outline

Looks great so far, @cheungaryk .


chore: 🤖 bump remark version to v13 to fix vulnerability

Hi there. The current version of postcss-markdown includes<EMAIL_ADDRESS>which has a library called trim as dependency. trim itself has some vulnerabilities.
I went through the Changelog of remark and I think it should be okay to bump this version. Also, all tests are still passing. However, I don't know postcss-markdown enough to evaluate the impact of this change.

Cool. Do you already know when it will be released? Once released we should then also adjust stylelint.

I was planning to create an issue about releasing a new version of stylelint this week. We'll make sure a new release of this syntax is rolled into it.

Awesome. Thx for the response!


user settings - console options full screen mode should be supported for noVnc as well

This is a follow up  for https://github.com/oVirt/ovirt-web-ui/pull/1446.
Also referenced by bug: https://bugzilla.redhat.com/1667517 and also https://bugzilla.redhat.com/1752996
As part of user console options, if "VNC"-"full screen mode" option is enabled then only VNC consoles are opened on full screen.
We should enable opening noVnc on full screen mode for user settings as well.
This is already supported manually and works well:

So just need to enable that for user settings.

@rszwajko @sgratch So does this issue depend on https://github.com/oVirt/ovirt-web-ui/pull/1482 ? Thanks! :)

So does this issue depend on #1482 ?

IMHO yes. The refactoring changes the component significantly - it may help solving the problem but also may break the fix prepared for class-based component.


Update unit test to reflect an issue with filtering nullable nested object

I've run into an issue where if filtering by more than one field on a nullable nested object (where that object is null) then a null reference exception is thrown.
This PR is a replication of that bug in a unit test

/AzurePipelines run

/AzurePipelines run

/AzurePipelines run


various cleanup, and version bump alex/happy

LGTM, merging

Would it make sense to have something like this to make updates more predictable?
ENV \
    GHC_VERSION=7.10.1 \
    CABAL_INSTALL_VERSION=1.22 \
    ALEX_VERSION=3.1.4 \
    HAPPY_VERSION=1.19.5

This way someone can't accidentally miss updating the PATH variable or other places the version number is used.

@md5 absolutely.  I want to be able to do something like run a script to detect when there are updates in the upstream PPA and then generate Dockerfiles based on it.  This update was overdue and involved moving to a new install method, so getting it pushed out ASAP was higher priority than solving the update overhead properly.  I opened #22 along those lines.

:+1:


Setup project

In this branch I did:

The initial setup and early UI development for the project:

Creating the project structure
Setting up the website header with navigation
Initializing the "My Profile" page view component.

Hi @GhausAliKhan
STATUS: APPROVED! 🟢🟢

No errors detected in the project 👍
All project requirements met 🥇
Linters executed successfully ✔

Congratulations, your project has met all the requirements and is ready for merging! :shipit:
Best of luck moving forward! 🎉


Vertical Divider

It seems that on Google Chrome the vertical divider has a problem (check the image) ! On Firefox it works well !

Can you post working fiddle, so that we can tweak little things.

I'm afraid this is a known issue :(
Please continue the discussion in #4342.


Add 008-the-cal-command.md contents

What type of PR is this? (check all applicable)

[ ] ♻ Refactor
[ ] ✨ New Chapter
[ ] 🐛 Bug Fix/Typo
[ ] 👷 Optimization
[x] 📝 Documentation Update
[ ] 🚩 Other

Description
Related Tickets & Documents
Added to documentation?

[x] 📜 readme
[ ] 🙅 no documentation needed

[optional] What gif best describes this PR or how it makes you feel?

@bobbyiliev please review


Logs are delayed when doing .map when docker logs

Describe the bug
When I run my SD training in a Docker image and then listen to logs like docker logs train -f, the progress bar is delayed.
It's updating every few percent.
When you have a large dataset that has to be mapped (like 1+ million samples), it's crucial to see the updates in real-time, not every couple hours to make sure nothing got frozen or broken
Steps to reproduce the bug

Run any huge dataset processing as a Docker image
docker logs image_name to it

Expected behavior
...
Environment info
...

Hi! tqdm doesn't work well in non-interactive environments, so there isn't much we can do about this. It's best to disable it in such environments and instead use logging to track progress.


Feature Request: ping on finish/fail

An toogle-able option to ping the user by sound when a build is successful, a different one when it fails. Why? For large builds, it takes too long, perhaps an audible ping helps to keep track.

I'm wondering if it's possible to run a custom callback after a successful compile, but I don't seem to see anything like a "compile complete" event notification in the documentation?

Thank you for the feature idea. We may not be able to get to this immediately, but I'm tagging it for further discussion.


ERROR build: output 'tensorflow/core/kernels/_objs/crop_and_resize_op_gpu/tensorflow/core/kernels/crop_and_resize_op_gpu.cu.o' was not created

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): No
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Linux Ubuntu 18.04
TensorFlow installed from (source or binary): source (build error)
TensorFlow version (use command below): 1.8.0
Python version:  3.6.5
Bazel version (if compiling from source): 0.13.0
GCC/Compiler version (if compiling from source): 6.4.0-17ubuntu1
CUDA/cuDNN version: 9.1.85-3ubuntu1 / 7.0.5
GPU model and memory: GeForce 1080ti 11GB
Exact command to reproduce:

Describe the problem
Building with bazel fails with the error below, using the following build command:
bazel build --jobs=12 --config=opt --config=cuda //tensorflow/tools/pip_package:build_pip_package --verbose_failures

Source code / logs
Here's the error log from re-running the build with --verbose_failures https://gist.github.com/darthdeus/1596b20a326f4ca6d41cae4b09aaf87e

Ubuntu 18-- the future is now. @gunan , my guess is there is some incompatibility between the various versions here; any ideas?

It looks like NVIDIA reported that gcc 6.4 is not supported with cuda 9.1:
https://devtalk.nvidia.com/default/topic/1028112/cuda-setup-and-installation/nvcc-bug-related-to-gcc-6-lt-tuple-gt-header-/
Could you try upgrading cuda and gcc?

It has been 14 days with no activity and the awaiting response label was assigned. Is this still an issue?

It has been 29 days with no activity and the awaiting response label was assigned. Is this still an issue?


two rippled performance much different  read throughput

two rippled with the same config, running at 2 AWS ec2 with 3200 iops EBS,  one rippled is running smoothly with 1000 Ops/s read throughput, ledger without gap. but the other rippled with
2000+ Ops/s read throughput and  many gaps  can not backfill.
these two AWS ec2 with the same specification
please help

Unfortunately, this is not unexpected.
EBS uses a "credit-based" system to allocate/throttle I/O, so even slight differences in I/O patterns can result in dramatically different performance, depending on how many I/O credits the application has at any given time.
We experienced similar issues when operating instances on AWS: one instance would be fine, while another struggled. Ultimately, it was that experience that resulted in us diving through the EBS documentation to try and understand the EBS performance chracteristics and, finally, led to us not recommending using EBS as the backing store for a rippled instance's data store.
I'm happy to dive deeper, if you have additional questions; but if you feel that this post satisfactorily answers your questions, please go ahead close this issue.
Thanks and happy Thanksgiving! :turkey:

Unfortunately, this is not unexpected.
EBS uses a "credit-based" system to allocate/throttle I/O, so even slight differences in I/O patterns can result in dramatically different performance, depending on how many I/O credits the application has at any given time.
We experienced similar issues when operating instances on AWS: one instance would be fine, while another struggled. Ultimately, it was that experience that resulted in us diving through the EBS documentation to try and understand the EBS performance chracteristics and, finally, led to us not recommending using EBS as the backing store for a rippled instance's data store.
I'm happy to dive deeper, if you have additional questions; but if you feel that this post satisfactorily answers your questions, please go ahead close this issue.
Thanks and happy Thanksgiving! 🦃

ok, I will close this issue.
Thanks for your help and happy Thanksgiving!

It may help to reduce the amount of querying you allow other nodes to do to your node. Reducing the number of peer connections and reducing the fetch depth, for example, could help. Also, using RocksDB and as much RAM as possible can help reduce the amount of I/O needed, but you can't keep very much history that way.

It may help to reduce the amount of querying you allow other nodes to do to your node. Reducing the number of peer connections and reducing the fetch depth, for example, could help. Also, using RocksDB and as much RAM as possible can help reduce the amount of I/O needed, but you can't keep very much history that way.

thanks for your advice.
these three parameters have been tried to modify, did not work.
[overlay]
ip_limit=1
[peers_max]
10
[fetch_depth]
128

after that , I deleted all my history data and re-sync, read iops almost to 0 and work well by now.


Default to the same config file names that vitest looks for

vitest currently has a list of config file names that it supports which include both using both the vitest* and vite* prefix as well as several file extensions.
However it seems vitest-coverage-report only looks for vite.config.js unless otherwise specified in the vite-config-path option (default value here).
When looking through existing issues I found #51 in which the author seemed to experience a slight hiccup in regards to having to remember to configure the path because they used a different extension (ts instead of js), to quote:

Thanks so much! I was able to successfully test (after remembering I still needed to set Vite config path because we use .ts extension).

This struck me as a very similar experience to the oneI had so I think I'm not alone in subconsciously expecting vite.config.ts, vitest.config.ts and others to be supported by default.
While not a big issue at all, perhaps it would make for a nicer experience if this action checked for the same list as vitest if vite-config-path is not specified.
I'll gladly contribute a PR if you think this is an appropriate change 🙂

Hi @goibon ,
thank you very much for the suggestion - that's a great idea and I really like it.
I don't know when I will be able to actually develop this. So if you want to put up a PR to speed up things, I am more than happy to accept that! 🙂


Add xref links

Closes #11337
The file list doesn't help. Not interested now :(

Thanks, @NextTurn, for making the additional changes. I'll merge your PR now.


Analyze prebuilts for templating

The following prebuilt packages are included as dependencies in source-build by templating.  These need to be analyzed to determine how to avoid requiring packages that source-build doesn’t build.

Change to use the source-built version
Package is not critical to product and can be removed.  (i.e.test-specific, windows-specific, etc)
The package is used as reference only
The package should be built in source-build
Other – please elaborate on what you think should be done.

For more detailed usage information for these, please see the Usage Exploration tab of the SourceBuildPrebuiltReport.

PackageName
PackageVersion
SourceBuiltVersion
Category

Microsoft.DiaSymReader.Pdb2Pdb
1.1.0-beta1-62506-02

Microsoft.DotNet.Cli.CommandLine
0.1.1-alpha-167
1.0.0-dev.19127.1

Microsoft.DotNet.SignTool
1.0.0-beta.19067.6

Microsoft.Extensions.CommandLineUtils
1.1.0
1.0.1

Newtonsoft.Json
10.0.3
9.0.1

System.Diagnostics.Process
4.3.0

System.Runtime.Loader
4.3.0

sn
1.0.0

vswhere
2.5.2

@dseefeld - The above dependencies list was generated before the arcade. Can we re-run this to see what are the pending source build dependencies?

@vijayrkn We are currently not building templating with our 3.0 build.  I will update our source and get and new build and then update this issue.  For now, this will have to be on hold.  I'll notify you when done.

@vijayrkn The list has been updated from the current templating build in source-build.

@mlorbetske & @Seancpeters - FYI

Package
Version
Status

Microsoft.DotNet.Cli.CommandLine
0.1.1-alpha-167
https://github.com/dotnet/templating/issues/1908

Microsoft.Extensions.CommandLineUtils
1.1.0
Removed

System.Runtime.Loader
4.3.0
Reference Only


[executor] structured logging

Motivation
structured logging
Have you read the Contributing Guidelines on pull requests?
Y
Test Plan
n/a

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

@bors-libra land

:broken_heart: Test Failed - Build images and run cluster test

@bors-libra land


Support json output in changelog and status commands

As a semversioner user I would like to get the semversioner output for some commands in json so that it is easy to be parsed by tools like jq.
Idea:
$ sermversioner status --format=json

{"version":"0.1.0", "next_version":"0.2.0", "unreleased_changes":[{'type': 'minor', 'description': 'My description'}]}

Closing the issue as won't do.


Fix zap tests by retrieving the project's repository root from git

What does this PR do?
I've been using git worktrees recently to develop the datadog-agent. When using this feature, it is preferred to use a repo at a path that looks like "/path/to/worktrees/[repository-name]/[branch-name]". These zap tests expect the root of the project to be a path ending in "datadog-agent", so worktrees break this assumption. The fix is to invoke git to ask for the repo root instead, falling back to the original behavior if this fails.
Motivation
Having the zap tests pass when using git worktree
Additional Notes
Possible Drawbacks / Trade-offs
Describe how to test/QA your changes
Setup a local development environment, then run the tests from a worktree:
cd datadog-agent
mkdir -p ~/worktrees/datadog-agent/
git worktree add ~/worktrees/datadog-agent/qa-zap-tests
cd !$
ln -s [original-venv] venv
source venv/bin/activate
inv test --module=pkg/util/log/zap --targets=.

/merge

/merge


Best way to get current server time?

I need to send a message so that it has a very specific timestamp but I noticed that the server time seems to be around 8-12 seconds off from my computer time.
Is there way i can query for the current server time?  I realize I could send myself a message and check the timestamp, but that would create a lot of unwanted message history.  Is there a cleaner way?
Thanks

The easiest way is to make sure your system time is correct... have you tried just synchronising with some NTP server?

But if you can't (or don't want to) mess with system time, you can try to set reactions to messages, and listen for message_reaction event as it includes timestamp and you can easly remove that reaction later

Thanks, finally got this working using the timestamp from a test message then later deleted it.  Had to convert the functions to return promises for it work though.  Surprised the the api does not do this natively.

This seems resolved. Thanks all


Seed and Modifier can be used interchangeably in certain cases.

I've managed to find a mini-vulnerability where certain combinations of seeds and modifiers can be reversed and still end up with the same string.
Example:
String: Hello!
Seed: 3
Modifier: 7
Amplifier: 2005
Can be decrypted with:
String:
Seed: 7
Modifier: 3
Amplifier: 2005
Output: Hello!
Note that this doesn't work for all numbers.
Will fix asap.

Fixed in the latest commit :D


Change description eu dsgvo conform

For the consent text the german text for
non eu dsgvo should be change to: "Datenempfänger im Ausland mit Datenschutzniveau unterhalb EU DSGVO" vs.
eu dsgvo should be changed to:  "alle Datenempfänger in Ländern mit Datenschutzniveau konform zur EU DSGVO",

@mgebhardttmf , @kleinertp  - please add the english version for each text and double check if you really would like such a long text for the eu dgsvo vs non eu dsgvo

Data recipients from countries with data protection levels below the EU GDPR vs. All data recipients in countries with data protection levels compliant with the EU GDPR
I know it is long, but every shorter version, which I found doesn't explain, what needs to be explained. If it is too long a tooltip or something has to be added. I'm fine with the long version.


Control upper/lower casing of key words in scripts?

I am mostly using postgres, which lower cases things by default. I assume that is why when I write a query in a SQL Editor it is automatically lower cased, and that it might not do that if I was using a DB other than Postgres (?).
However, after testing my scripts I often want to move them into a file for later automatic execution, and I like to have the SQL key words upper cased so that they stand out:
"SELECT not_a_keyword FROM my_table WHERE..." kinda thing.
I see that there is a option to upper or lower case everything, but not exclusively the key words. Obviously, begin able to do this is no more than a mere convenience, but it would be nice.

Or maybe there is already a setting to control this, and I'm just not finding it?

Keyword case could be set in Preferences


Able to upload data as different user

Expected behavior
Without giving permission to a different user, that different user is not able to access a user's project or upload data.
Actual Behavior (please include screenshot if possible)
Different user can access primary user's data ad upload data.
Steps to reproduce the problem

Log in to the web application with a different github user account.
Set the token of that user
Upload data into the primary user's project

Optional infrastructural data (user, platform, browser, environment, ...)
http://dev.nexus.ocp.bbp.epfl.ch/v1, nexus-python-sdk commit 496830e

This is a configuration property of the environment, not a bug in the software. ACLs are considered when the API is invoked, having inappropriate ACLs is a matter of env configuration rather than an incorrect system behaviour.

@bogdanromanx So how can the access from a different user be tested?

You can try that with anonymous (No Authentorization header).
In practice is the same.


Clean up redundant fields and function parameters

Some types and methods store or receive redundant copies of the ControlRuntime struct. We also have multiple copies of the EtcdConfig struct in the Cluster type: https://github.com/k3s-io/k3s/blob/40a46e1412f5a0c92ce7572e188d108e8f530455/pkg/cluster/cluster.go#L18-L28

runtime is also available as config.Runtime
EtcdConfig is also available as config.Runtime.EtcdConfig

I am unable to find any compelling reason to keep these fields as they are; any current references to them can easily be refactored to reference another.
We should eliminate these duplicate fields and parameters, as they make the code harder to understand and maintain.

Closing; this is a code cleanup issue with nothing specific for QA to test.


Add metadata to channels

Useful for storing channel level configuration, for apps, logistics, languages, localization etc.

Duplicate of https://github.com/saleor/saleor/issues/13228


There’s an error in the example.

                WebView(configuration: viewState.configuration)
                    .uiDelegate(viewState)
                    .navigationDelegate(viewState)
                    .allowsInspectable(true)
                    .allowsBackForwardNavigationGestures(true)
                    .allowsLinkPreview(false)
                    .refreshable()
                    .border(Color.gray)

Incorrect argument label in call (have 'configuration:', expected 'webView:')
Cannot convert value of type 'WKWebViewConfiguration' to expected argument type 'WKWebView'
Value of type 'WebView' has no member 'uiDelegate'

Thank you for the report.
Could you confirm if you're referring to an issue with building the included Example project?
CI is passing, so the build is successful in the CI environment. Also, could you let me know the macOS, Xcode, and Swift versions where your error reproduces?

macos 15.0.1 ， xcode 16 ，swift 5 ， Normally, Xcode 16 corresponds to Swift 6, but I’ve changed the Swift version on my computer to Swift 5.

There may be an issue with the consistency between Xcode and toolchain versions.
Could you try setting the Swift version on your computer to 6 and see if that resolves the issue?

swift is ok

xcode 16 and swift 6  is not OK

When I paste the files AppDelegate, ContentView, ContentViewState, and ExamplesApp from your example into my own project, I get this error.

When I paste the files AppDelegate, ContentView, ContentViewState, and ExamplesApp from your example into my own project, I get this error.

From reading the warning below, it appears that there is another type with the same name as WebUI's WebView.
Incorrect argument label in call (have 'configuration:', expected 'webView:')
WebUI's WebView has never provided an initializer that takes WKWebView as an argument.


(feature) Make crossfilter dimensions even easier to use. Fixes #136

Coverage decreased (-0.74%) to 98.88% when pulling 68238e8d2bf9881a32b170561df8fe96f2c4142d on yago/crossfilter-easier-to-use into 79ba791d381da19e29f6b65053c2567222a296f6 on master.


HTML (altchunk) not supported/displayed when opening in LibreOffice

Wanted to use docx templates in our process to generate a pdf report. Just spotted that LibreOffice isn't displaying that HTML rendered with docx-templates altchunk at all.
Is it only me who is experiencing such problems? Is there any other option to render HTML that's gonna be opened by LibreOffice?

I expect this to be a LibreOffice thing. Leaving this open for others to comment.

yes that's totaly LibreOffice thing. Just wanted to ask if you're aware of any workaround.

i.e i see that https://docxtemplater.com/demo/#html is handling that perfectly. Embedded some HTML table and libre office displays it properly. hmmmm

So you mean that it should be possible? If you can find what exactly it does differently (i.e. does the HTML look different?)  we may be able to build a patch.

well I'm not sure if it should be possible, not an expert on that field. I've checked docxtemplater result and it seems that they are generating openxml based on provided HTML, so it's basically different approach.

HTML is not generated for me as well - like it "eats" all the HTML and all I get nothing in the places where HTML should have been.
I'm using version "docx-templates": "^4.5.4"

well I'm not sure if it should be possible, not an expert on that field. I've checked docxtemplater result and it seems that they are generating openxml based on provided HTML, so it's basically different approach.

what is the relationship between docxtemplater (which is commercial product) and this lib?

what is the relationship between docxtemplater (which is commercial product) and this lib?

There is none. Just a slightly inconvenient naming similarity ;)

FYI @all
partial solution (at least the one I opted for)
docx is basically .zip-ed xml so my plan is to directly edit xml so I don't have to use libraries (except some for XML manipulation but that is pretty straightforward)

FYI @ALL
partial solution (at least the one I opted for)
docx is basically .zip-ed xml so my plan is to directly edit xml so I don't have to use libraries (except some for XML manipulation but that is pretty straightforward)

Could you be more specific about your approach? I'm having the same issue.

Could you be more specific about your approach? I'm having the same issue.

unzip the .docx file and go to word/document.xml you can view and edit the file and that's it
look how current structure looks like and just imitate the elements you wish to add and that's it

I have the same issue. What I noticed is that LibreOffice can properly display html directly. In addition, if I open a html file (with html content) and save it as a docx, it still displays the content correctly. The problem seems to be the embedding of html in this library that it only renders properly in MS Word. It does not render on Libre Office, Open Office or Google Docs. At least in my case working on Mac.

So apparently this is due to lack of support for altchunk as it seems to be non-standard. Even MS Word re-formats/re-parses the files with altchunk if you "save as" the docx.

Please note that until a document that contains altChunk elements is opened and saved in Office, it still contains the altChunk parts, and not normal WordprocessingML markup of paragraphs, runs, and text elements.  The solution with SharePoint 2010 is that you can use Word Automation Services to update the documents that contain altChunk elements.  After Word Automation Services processes it, the document will contain paragraphs, runs, and text elements.
https://ankushbhatia.wordpress.com/2010/10/22/altchunk-an-interesting-scenario/?unapproved=4594&moderation-hash=4178e78d24528e1c1c061e585d38bdc8#comment-4594

Instead of relying on altchunks it could be done similar to what https://www.npmjs.com/package/html-to-docx does

Is there a solution for this? I have been using it to generate DOCX files and then convert them to PDF. Everything worked well on Windows, but when I moved to Linux and started using LibreOffice, the generated DOCX files do not display content from HTML. This also affects the generated PDF files.

hitting the same problem :(


[AutoPR dns/resource-manager] Py DNS 2018-05

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/3810

This PR has been merged into https://github.com/Azure/azure-sdk-for-python/pull/3272


Support for platform "linux/arm64/v8" requested to allow running Papermerge 3.0 on a Raspberry Pi

The docker images provided in the documentation do not support the platform linux/arm64/v8 at the moment. This causes the docker compose file to not work.
Reproduction steps:

Create a docker-compose.yml with the content shown in the installation guide:

  version: "3.9"

  x-backend: &common
    image: papermerge/papermerge:3.0.1
    environment:
        PAPERMERGE__SECURITY__SECRET_KEY: 12345
        PAPERMERGE__AUTH__USERNAME: john
        PAPERMERGE__AUTH__PASSWORD: hohoho
        PAPERMERGE__REDIS__URL: redis://redis:6379/0
    volumes:
        - data:/db
        - index_db:/core_app/index_db
        - media:/core_app/media
  services:
    web:
      <<: *common
      ports:
       - "12000:80"
      depends_on:
        - redis
    worker:
      <<: *common
      command: worker
    redis:
      image: redis:6
  volumes:
    data:
    index_db:
    media:

Call docker compose up -d web worker redis
Output is The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested ❌

Goal:
Add support for platform "linux/arm64/v8" please 😃

Here is docker file: https://github.com/papermerge/papermerge-core/blob/master/docker/prod/Dockerfile
Community if looking forward for your contributions!

Community if looking forward for your contributions!

@ciur I think the best is to build images using docker buildx, there is a Github-Action for it. Would you accept a PR for this or is this call for community work meant to be read as "provide images on your own"?

I don't know what to say here. First of all, PR - for which repository ? And secondly, build arm image when i.e. which event should trigger that images? And lastly, the build process will be where in the workflow chain?
To be clear:

this repo is not used for the building images (this one: https://github.com/papermerge/papermerge-core is used instead).
I build images when specific tag is pushed (e.g. 3.3.1)
The important point here is that ARM image should be outside of usual build image workflow because (as per 2022 state) it used to be slow (back in 2022).

Maybe you create a PR in https://github.com/papermerge/papermerge-core and let's start discussion from there.

@ciur Thank you for the reply!
I am sorry for picking the wrong place for the request. But before I can open a PR and do some work, it would be needed to have a discussion about what to do actually. So I think we should open the issue and eventually move it to the appropriate repository.

build arm image when i.e. which event should trigger that images

I'd say a new image should be built whenever a new version is release, eg a new tag created (however it fits into the current flow)

I build images when specific tag is pushed (e.g. 3.3.1)

Do you do this manually or is this already in Github Actions?

The important point here is that ARM image should be outside of usual build image workflow because (as per 2022 state) it used to be slow (back in 2022).

I'd prefer to built multiarch images, that basically work on all platforms we want to support. Building those is indeed slower, it takes time. In order to not disturb the usual development flow, we can limit the multi arch builds to release, even though this has the danger of missing issues until the release is made.

It took less than 2 min. Last time when I added ARM flag for docker images - instead of 2 min, the build took about 45 min!

Well, Github Actions usually makes intensive use of caching and if the first arm build is made, cache missed might increase the build time, too. We can probably invest in optimizations here, however the build time will always be slower with multiarch enabled than without. This is simply caused by the cross compilation. The alternative would be to build arm-only images with different tags, however I consider this to be not really a good solution.


Use correct quarkus-extension-maven-plugin in beanio extension

A clue here that the origin is probably back and forth between supported and not supported. Should we update the jvmSince version in this case ?

Should we update the jvmSince version in this case ?

Yes, I actually thought we had done that in the initial PR but I guess we missed it.
Latest commit updates it to 3.8.0.


SA-192 Implement show more/less feature with ExpandableContainer

Related to #192

Merging this, as the CSS columns weirdness is a separate issue which shouldn't block this PR.


refactor how map and call primitives are tagged

This seems a little less arcane. Includes the commit from #2828, but I figured I'd factor out this cleanup.

I'm not sure I like staged_out as a tag name here. I'm guessing it means "outer JaxprTraces will stage out instances of this primitive in their entirety, rather than partially-evaluating their bodies" (right?)—but it took me a while to realize that was what this probably referred to. Maybe always_staged_out or fully_stage_out?

I think it’s a property of the primitive, whether its impl executes in Python or if it’s staged out of Python. Nothing on its own to do with tracing. But those are the primitives for which we would hoist as much as possible into them, hence the interaction with StagingJaxprTrace.

OK, that makes sense! Thanks for explaining.

I had some follow-up changes in mind to try out, like either

factoring out xla_call_jaxpr/pmap_call_jaxpr primitives that work like the other initial-style higher-order primitives so that there's no need for a special case analysis in jaxpr interpreters, or else
cleaning up the representation / case analysis so that instead of relying on extract_call_jaxpr we have special JaxprCallEqn / JaxprMapEqn classes which have call_jaxpr and call_jaxpr/mapped_invars fields respectively.

I implemented 2 already (in an un-pushed commit), but want to try 1 as it now seems more promising.
Do you think we should merge this PR now-ish, and make more changes in follow-ups? Or fuse all such changes together? The latter might be slightly nicer for any jaxpr consumers, since they won't have to make multiple changes, but it also means making more changes at once (and increasing the chance I run out of fuel on this).
In any case, @gnecula if you have time I plan to wait for your review / LGTM, since I could really benefit from your advice here. Don't hold back: I'm happy to make changes!

I'm going to replace this with a fresh PR!


fix: optimistic db write batch

I am not completely sure of myself here. I was surprised you were using rocksdb_write instead of rocksdb_optimistictransactiondb_write, but I must admit I don't know much of the difference.

Thanks. I think rocksdb_optimistictransactiondb_write may not have been included in RocksDB release version when I wrote this code. That's probably why I missed it. I'll check the difference between the two interfaces later and merge this PR.

The difference between rocksdb_optimistictransactiondb_write and rocksdb_write is that rocksdb_optimistictransactiondb_write will check whether writebatch contains range delete or not. If write batch contains range delte, it will return error because optimistic transactiondb doesn't support range delete.
In rust-rocksdb, we don't provide delete range api for WriteBatchWithTransaction<true>. So using rocksdb_write didn't cause wrong results.


Username must be lowercase when version 1.38

Describe the bug
In version 1.38 access tokens are used instead of basic authentication. Getting the access token from the Artifactory API fails when the username is mixed case because the API expects lowercase usernames. On the other hand, the web UI of Artifactory accepts mixed case usernames. The behaviour should be identical. And the behaviour of jfrog-cli should not break with 1.38.
To Reproduce
Configure jfrog-cli using a mixed case username:
jfrog rt config --url rt.my-domain.com --username MyUser --password 'REDACTED'
jfrog rt search .

jfrog-cli fails with the following error:
[Error] Artifactory response: 400 Bad Request
{
  "error": "invalid_request",
  "error_description": "User myuser can only create user token(s) for themselves (requested: MyUser)"
}

Expected behavior
Search should work without error. Username should be converted to lowercase in request for access token.
Versions

JFrog CLI version: 1.38.0
JFrog CLI operating system: Linux Ubuntu 18.04
Artifactory Version: 6.17.0

Additional context
There is also a Jira issue for harmonizing the behaviour of the web UI and the API.

Thanks for reporting this issue @nicholasdille!
We're looking into it now.

Great work @@nicholasdille! figuring out the root cause of the issue. That really helped!
The above PR fixes the issue. We plan to release a patch soon.

@nicholasdille,
Version 1.38.1 was released and includes this fix.
Looking forward to your feedback for it.

Thanks for the update. I will test 1.38.1 in the morning and let you know.

@eyalbe4 The patch fixes the issue :-) It works for existing credentials as well as newly configured credentials.
Thanks a lot for fixing this so quickly!


Remove the accuracy calculation in evaluation of torch estimator

We don't need to calculate accuracy in the evaluation of torch estimator, since we have no idea whether it's a regression or a classification task.

close as stale


Can I use dino model to match images with pixels? Just like with the clip model you can match pixels with text.

What do you mean by 'matching images with pixels'? Aren't images actually pixels? Do you mean image hashing?


Opening hyprswitch has kind of a delay

When I open hyprswitch, by using hyprswitch --daemon it takes almost a full second to show up. Anyone experiencing the same behavior?

This is mostly the fault of the GTK window. I am currently searching for a solution but would appreciate some help.

Gets fixed in #42


Fix theming update in several editor classes

This makes the test project crash on CI in ConnectionsDock::update_tree(): https://github.com/godotengine/godot/runs/4831673583?check_suite_focus=true

That probably solves it, but we likely do want to update that tree at some point, as it does use several theme items. I guess the theme changed notification can happen before all the nodes there are available, or something similar to that.


[Question] Is it possible to write protobuf format from Java without storing the proto files on the CH node

Clickhouse-client supports converting Protobuf to TCP/native protocol without the use of .proto files on the Clickhouse node.
I was wondering if this is also possible from clickhouse-java? Not having to deploy .proto files on the clickhouse node when code changes would make the release process much easier.

Not possible. Clickhouse-client is the same binary as Clickhouse-server, it able to parse brotobufs using Clickhouse-server code. clickhouse-java has no this functionality.
You need to read/parse protobufs using usual java library https://www.baeldung.com/google-protocol-buffer.


Improving expression detection

Hi,
I noticed that ichiran will currently segment "どこから見ても" as three separate words "どこ", "から" and "見ても", rather than the expression which has a JMdict entry. Same is true for some other expressions as well, such as 負の遺産 or 取り留めも無い. Other expressions like どう見ても do get detected as such. I don't know how difficult it would be, but it would be great if ichiran was able to detect these expressions more reliably.

Related? If I search Ichiran/ichi.moe for 写真を撮る it finds the literal JMdict entry but 写真を撮りました doesn't recognize that this is a conjugation of the longer entry?


Extended IPFS link support is broken

It breaks on ipfs's github as it starts with /ipfs/....
On solution would be to push ipfs/notes#92 forward and resolve it in case of /ipfs/... or /ipns/... to confirm if redirection to local gateway should take place.

Yup, will need to stop doing regex-based rewrites due to false-positives like this one.


Font family parameter

Hello.
The library is awesome!
I just made some little adjustments to init.py and 2 of the .js files in resources folder (i.e. add_dot.js and add_note.js) to add a new parameter (fontfamily) to the related keywords to set also the font family (serif, sans-serif or other) of the text (also changed the default family to sans-serif).
I'm attaching here the zip with modified files, for your check/validation and inclusion in a new version of the library.
SeleniumScreenshots_Modifiedfiles.zip

Thanks! I am not able to immediately work on this, but when I do, I consider.
I believe, it is also possible to make custom keywords to achieve the same with any keyword that returns element id and then just use “Update element style” keyword to set the font-family.
On 12. May 2020, 17.46 +0300, axiom41<EMAIL_ADDRESS>wrote:

Hello.
The library is awesome!
I just made some little adjustments to init.py and 2 of the .js files in resources folder (i.e. add_dot.js and add_note.js) to add a new parameter (fontfamily) to the related keywords to set also the font family (serif, sans-serif or other) of the text (also changed the default family to sans-serif).
I'm attaching here the zip with modified files, for your check/validation and inclusion in a new version of the library.
SeleniumScreenshots_Modifiedfiles.zip
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.


Compatibility Issue with Node.js 16.18.1 on Expo Application Servers

Checklist

[X] I have looked into the Readme and have not found a suitable solution or answer.
[X] I have searched the issues and have not found a suitable solution or answer.
[X] I have searched the Auth0 Community forums and have not found a suitable solution or answer.
[X] I agree to the terms within the Auth0 Code of Conduct.

Description
I am  attempting to use the jwt-decode package within my Expo dev client project. However, during the installation of project dependencies, I encounter an error message that indicates a compatibility issue with Node.js. The error message looks like this:

error<EMAIL_ADDRESS>The engine "node" is incompatible with this module. Expected version ">=18". Got "16.18.1"

error Found incompatible module.

info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.

Error: Unknown error. See logs of the Install dependencies build phase for more information

Reproduction

Create an expo app
Add as part of your dependency jwt-decode version 3.1.2
Try to build the project on EAS

Additional context
My package.json file
{
"name": "rnt-ui",
"version": "1.0.0",
"main": "node_modules/expo/AppEntry.js",
"scripts": {
"lcl": "set APP_ENV=lcl && expo start --dev-client",
"dev": "set APP_ENV=dev && expo start --dev-client",
"stg": "set APP_ENV=stg && expo start --dev-client",
"start": "expo start",
"android": "expo start --android",
"ios": "expo start --ios",
"web": "expo start --web"
},
"dependencies": {
"@config-plugins/react-native-blob-util": "^6.0.0",
"@config-plugins/react-native-pdf": "^6.0.0",
"@gorhom/bottom-sheet": "^4.5.1",
"@react-native-async-storage/async-storage": "1.18.2",
"@react-native-firebase/app": "^18.6.1",
"@react-native-firebase/messaging": "^18.6.1",
"@react-navigation/bottom-tabs": "^6.5.10",
"@react-navigation/drawer": "^6.6.5",
"@react-navigation/native": "^6.1.8",
"@react-navigation/native-stack": "^6.9.14",
"@reduxjs/toolkit": "^1.9.6",
"async-mutex": "^0.4.0",
"expo": "~49.0.13",
"expo-application": "~5.3.0",
"expo-constants": "^14.4.2",
"expo-dev-client": "~2.4.11",
"expo-document-picker": "~11.5.4",
"expo-font": "~11.4.0",
"expo-image-picker": "~14.3.2",
"expo-linking": "~5.0.2",
"expo-print": "~12.4.2",
"expo-sharing": "~11.5.0",
"expo-status-bar": "~1.6.0",
"expo-web-browser": "~12.3.2",
"fbjs": "^3.0.5",
"jwt-decode": "^3.1.2",
"react": "18.2.0",
"react-native": "0.72.6",
"react-native-blob-util": "^0.19.1",
"react-native-dropdown-picker": "^5.4.6",
"react-native-gesture-handler": "~2.12.0",
"react-native-image-zoom-viewer": "^3.0.1",
"react-native-international-phone-number": "^0.6.0",
"react-native-localize": "^3.0.2",
"react-native-onboarding-swiper": "^1.2.0",
"react-native-pager-view": "6.2.0",
"react-native-paper": "^5.10.6",
"react-native-paper-dates": "^0.19.8",
"react-native-paper-dropdown": "^1.0.7",
"react-native-pdf": "^6.7.1",
"react-native-ratings": "^8.1.0",
"react-native-reanimated": "~3.3.0",
"react-native-safe-area-context": "4.6.3",
"react-native-screens": "~3.22.0",
"react-native-swipe-list-view": "^3.2.9",
"react-native-uuid": "^2.0.1",
"react-redux": "^8.1.3",
"redux-persist": "^6.0.0",
"socket.io-client": "^4.7.2"
},
"devDependencies": {
"@babel/core": "^7.20.0",
"@types/react": "~18.2.14",
"@types/react-native-onboarding-swiper": "^1.1.5",
"typescript": "^5.1.3"
},
"private": true,
"prettier": {
"arrowParens": "avoid",
"singleQuote": false,
"printWidth": 150
}
}
jwt-decode version
3.1.2
Which browsers have you tested in?
Other

As outlined in the release notes, support for Node.js 16 has been dropped. The minimal version of Node.js now supported is version 18 and up, this is the same range actively supported by the Node.js team.
I would recommend that you upgrade to a more recent version of Node.js like version 18 or 20, which are both LTS versions.

Yeah I fixed it by explicitly stating the node version to be used by EAS in my eas.json file


.lsp-symlink doesn't seem to work

Description
I use jupyter/tensorflow-notebook:python-3.10 with jupyterlab 3.6.5, jupyter_server 2.7.0 and jupyterlab_server 2.24.0.
Reproduce

ln -s / "${NB_HOME}/.lsp-symlink"
Open your ipynb notebook
Click on an external function call and navigate (ctrl-b)
Observer error

e.g. (for gc.enable())
[W 2023-08-08 07:23:10.018 ServerApp] wrote error: "file or directory does not exist: 'opt/conda/lib/python3.10/site-packages/jedi/third_party/typeshed/stdlib/3/gc.pyi'"
    Traceback (most recent call last):
      File "/opt/conda/lib/python3.10/site-packages/tornado/web.py", line 1786, in _execute
        result = await result
      File "/opt/conda/lib/python3.10/site-packages/jupyter_server/services/contents/handlers.py", line 122, in get
        self.contents_manager.get(
      File "/opt/conda/lib/python3.10/site-packages/jupytext/contentsmanager.py", line 199, in get
        return self.super.get(path, content, type, format)
      File "/opt/conda/lib/python3.10/site-packages/jupyter_server/services/contents/filemanager.py", line 415, in get
        raise web.HTTPError(404, four_o_four)
    tornado.web.HTTPError: HTTP 404: Not Found (file or directory does not exist: 'opt/conda/lib/python3.10/site-packages/jedi/third_party/typeshed/stdlib/3/gc.pyi')
[W 2023-08-08 07:23:10.019 ServerApp] 404 GET /api/contents/opt/conda/lib/python3.10/site-packages/jedi/third_party/typeshed/stdlib/3/gc.pyi?content=0&1691479390013<EMAIL_ADDRESS>1.84ms referer=http://<IP_ADDRESS>:48888/lab/tree/work/Notebook.ipynb
[W 2023-08-08 07:23:10.043 ServerApp] wrote error: "file or directory does not exist: '.lsp_symlink/opt/conda/lib/python3.10/site-packages/jedi/third_party/typeshed/stdlib/3/gc.pyi'"
    Traceback (most recent call last):
      File "/opt/conda/lib/python3.10/site-packages/tornado/web.py", line 1786, in _execute
        result = await result
      File "/opt/conda/lib/python3.10/site-packages/jupyter_server/services/contents/handlers.py", line 122, in get
        self.contents_manager.get(
      File "/opt/conda/lib/python3.10/site-packages/jupytext/contentsmanager.py", line 199, in get
        return self.super.get(path, content, type, format)
      File "/opt/conda/lib/python3.10/site-packages/jupyter_server/services/contents/filemanager.py", line 415, in get
        raise web.HTTPError(404, four_o_four)
    tornado.web.HTTPError: HTTP 404: Not Found (file or directory does not exist: '.lsp_symlink/opt/conda/lib/python3.10/site-packages/jedi/third_party/typeshed/stdlib/3/gc.pyi')
[W 2023-08-08 07:23:10.044 ServerApp] 404 GET /api/contents/.lsp_symlink/opt/conda/lib/python3.10/site-packages/jedi/third_party/typeshed/stdlib/3/gc.pyi?type=file&content=1&format=text&1691479390039<EMAIL_ADDRESS>1.31ms referer=http://<IP_ADDRESS>:48888/lab/tree/work/Notebook.ipynb

However, if I show hidden files and navigate to .lsp_symlink/opt/conda/lib/python3.10/site-packages/jedi/third_party/typeshed/stdlib/3/gc.pyi' I can open the file.
Context

Operating System and version: jupyter/tensorflow-notebook:python-3.10 with Podman under Gentoo Linux
Browser and version: Chrome v115.0.5790.170
JupyterLab version: JupterLab v3.6.5
Language server and version: jupyterlab-lsp v4.2.0 with jupyter-lsp-python 2.2.0

Required: installed server extensions

config dir: /opt/conda/etc/jupyter
    dask_labextension  enabled
    - Validating...
      dask_labextension 6.2.0 OK
    ipyparallel  enabled
    - Validating...
      ipyparallel 8.6.1 OK
    jupyter_lsp  enabled
    - Validating...
      jupyter_lsp 2.2.0 OK
    jupyter_server_proxy  enabled
    - Validating...
      jupyter_server_proxy  OK
    jupyter_server_ydoc  enabled
    - Validating...
      X is jupyter_server_ydoc importable?
    jupyterlab  enabled
    - Validating...
      jupyterlab 3.6.5 OK
    jupyterlab_git  enabled
    - Validating...
      jupyterlab_git 0.41.0 OK
    jupyterlab_latex  enabled
    - Validating...
      jupyterlab_latex 3.2.0 OK
    jupyterlab_rise  enabled
    - Validating...
      jupyterlab_rise 0.2.1 OK
    jupytext  enabled
    - Validating...
      jupytext 1.15.0 OK
    nbdime  enabled
    - Validating...
      nbdime 3.2.1 OK
    voila.server_extension  enabled
    - Validating...
      voila.server_extension  OK

Required: installed lab extensions

JupyterLab v3.6.5
/opt/conda/share/jupyter/labextensions
        jupyterlab-plotly v5.15.0 enabled OK
        jupyter-matplotlib v0.11.3 enabled OK
        jupyterlab-jupytext v1.3.9 enabled OK (python, jupytext)
        jupyterlab-quarto v0.1.45 enabled OK (python, jupyterlab-quarto)
        jupyterlab_pygments v0.2.2 enabled OK (python, jupyterlab_pygments)
        ipyparallel-labextension v8.6.1 enabled OK
        jupyterlab-rise v0.2.1 enabled OK (python, jupyterlab_rise)
        dask-labextension v6.2.0 enabled OK (python, dask_labextension)
        nbdime-jupyterlab v2.2.0 enabled OK
        @jupyterhub/jupyter-server-proxy v4.0.0 enabled OK
        @voila-dashboards/jupyterlab-preview v2.2.0 enabled OK (python, voila)
        @jupyterlab/git v0.41.0 enabled OK (python, jupyterlab-git)
        @jupyterlab/latex v3.2.0 enabled OK (python, jupyterlab-latex)
        @jupyter-widgets/jupyterlab-manager v5.0.8 enabled OK (python, jupyterlab_widgets)
        @jupyter-lsp/jupyterlab-lsp v4.2.0 enabled OK (python, jupyterlab-lsp)
Other labextensions (built into JupyterLab)
app dir: /opt/conda/share/jupyter/lab

On a side note. Navigating to functions in .py-files located in the current working directory doesn't work either. There it says that "No jump targets found". E.g.
import my_helper
my_helper.init()

where my_helper.py is located in the same directory as the notebook. Navigating to my_helper.init() doesn't work (and yes, the function exists). This is likely another problem.

@tsjk  hi, have you solved this error? I also met it.

@Mrfranken - no, I have not... :\


Wanted: download load curve for a whole year with quarterly values

In the beta version of ETMoses, it is possible to download the results of your LES, including the strategies, as load curves (.CSV file). When downloading the results of a week you get quarterly values (672 entries), however, if you download the file for a whole year, you get daily values (365 entries). Would it be possible to generate these output files for a whole year with quarterly values, so a more detailed analyses can be done?
And when will the download feature be available in the regular version of ETMoses?

@Stefan-87 Thank you for participating actively on Github! A few pointers:

Select one or more labels to indicate what type of ticket this is
Assign someone (when in doubt, assign me) so your ticket gets looked at
In the future, please search for similar issues than the one you are experiencing so you don't have to create a new issue each time you encounter an error or have a question. Let me know if you need help with the search functionality!

Closing as this is a duplicate of https://github.com/quintel/etmoses/issues/1296.


Feature Reguest: add option for a combined key and cert file

I have several servers (e.g. lighttpd) which are using a combined key and cert file. It is working if I perform this command:
cd /var/lib/lego/certificates/
cat fqdn.key fqdn.crt > fqdn.combined.pem

I would appreciate if one could ad an option which generates this file in addition to the other files. That would made my deployment way more easier. Thanks!

in the documentation you can see -pem parameter, which is actually generating your combined file, is that you are looking for?

Where is this documented? I didn't see any of this in README.md or releases.

@joker234 is it actually here: https://github.com/xenolf/lego/blob/master/cli.go#L178
you can run lego -help and it will show you all the parameters


Smelting blocks doesnt work.

The only block that works when I put in the furnace to smelt is cobblestone.
All nameblocks was check with /jobs blockinfo to get the correct name.
Theres no error in chat or console, it doesnt work (none bossbar and text etc)
Heres the job:
  Smelter:
    fullname: Smelter
    shortname: SL
    description: Ganhe derretendo coisas.
    ChatColour: GOLD
    chat-display: full
    max-level: 1000
    vip-max-level: 2000
    slots: 30
    leveling-progression-equation: 550*(joblevel)+(joblevel*joblevel*32)
    income-progression-equation: baseincome+(baseincome*(joblevel-1)*0.01)-((baseincome+(baseincome*(joblevel-1)*0.01))
      * ((numjobs-1)*0.05))
    points-progression-equation: basepoints+(basepoints*(joblevel-1)*0.01)-((basepoints+(basepoints*(joblevel-1)*0.01))
      * ((numjobs-1)*0.05))
    experience-progression-equation: baseexperience-(baseexperience*((numjobs-1) *0.01))
    rejoinCooldown: 259200
    maxDailyQuests: 1
    Quests:
      '1':
        Name: Comer here Iron Man!
        Objectives:
        - Smelt;sand;320
        - Smelt;cobblestone;800
        - Smelt;smooth_stone;600
        RewardCommands:
        - money give [playerName] 20
        - msg [playerName] Completed quest!
        RewardDesc:
        - Clean this server
        - Get 20 for this!
    Gui:
      Id: 62
      Data: 0
    cmd-on-join:
      - msg [name] Now start working and get money from [jobname] job!
    cmd-on-leave:
      - msg [name] See you soon!
    Smelt:
      sand:
        income: 0.0005
        points: 0.00010
        experience: 0.00010
      cobblestone:
        income: 0.0005
        points: 0.00010
        experience: 0.00010
      sandstone:
        income: 0.0005
        points: 0.00010
        experience: 0.00010
      stone:
        income: 0.0005
        points: 0.00010
        experience: 0.00010
      quartz:
        income: 0.0005
        points: 0.00010
        experience: 0.00010
      clay:
        income: 0.0005
        points: 0.00010
        experience: 0.00010
      netherrack:
        income: 0.0005
        points: 0.00010
        experience: 0.00010
      clay_ball:
        income: 0.0005
        points: 0.00010
        experience: 0.00010
      stone_bricks:
        income: 0.0005
        points: 0.00010
        experience: 0.00010
      black_terracotta:
        income: 0.0005
        points: 0.00010
        experience: 0.00010
      blue_terracotta:
        income: 0.0005
        points: 0.00010
        experience: 0.00010
      brown_terracotta:
        income: 0.0005
        points: 0.00010
        experience: 0.00010
      cyan_terracotta:
        income: 0.0005
        points: 0.00010
        experience: 0.00010
      gray_terracotta:
        income: 0.0005
        points: 0.00010
        experience: 0.00010
      green_terracotta:
        income: 0.0005
        points: 0.00010
        experience: 0.00010
      light_blue_terracotta:
        income: 0.0005
        points: 0.00010
        experience: 0.00010
      light_gray_terracotta:
        income: 0.0005
        points: 0.00010
        experience: 0.00010
      lime_terracotta:
        income: 0.0005
        points: 0.00010
        experience: 0.00010
      magenta_terracotta:
        income: 0.0005
        points: 0.00010
        experience: 0.00010
      orange_terracotta:
        income: 0.0005
        points: 0.00010
        experience: 0.00010
      pink_terracotta:
        income: 0.0005
        points: 0.00010
        experience: 0.00010
      purple_terracotta:
        income: 0.0005
        points: 0.00010
        experience: 0.00010
      red_terracotta:
        income: 0.0005
        points: 0.00010
        experience: 0.00010
      white_terracotta:
        income: 0.0005
        points: 0.00010
        experience: 0.00010
      yellow_terracotta:
        income: 0.0005
        points: 0.00010
        experience: 0.00010
      cactus:
        income: 0.0005
        points: 0.00010
        experience: 0.00010
      chorus_fruit:
        income: 0.0005
        points: 0.00010
        experience: 0.00010
      wet_sponge:
        income: 0.0005
        points: 0.00010
        experience: 0.00010
      sea_pickle:
        income: 0.0005
        points: 0.00010
        experience: 0.00010

You should add the result of the material not the melted material.
Eg:
sand replace to glass

you should put this on the wiki in spigot page or the #comment codes then.

Ask Zrips, I don't have permission to edit the spigot page.

ty

So...
I did a test with a wood,
insted of wood I put a charcoal like you said.
still doesnt work.

@montlikadani
I did another test, with glass and cobblestone. none work
Smelt:
      glass:
        income: 0.0005
        points: 0.00010
        experience: 0.00010
      cobblestone:
        income: 0.0005
        points: 0.00010
        experience: 0.00010


Do I need to install it first like DeepH or use it directly through the path

In DeepH，we should pip install it before use.But deepH-E3 doesn't have setup.py. So should I still write a coda myself to install it first? Or use it directly by specify the path

You can directly run the scripts in the top folder, like deephe3-train.py, deephe3-eval.py and so on.


Test Issue

Attempting to test smart sheets integration.
Issue is:
python: can't open file '/home/runner/work/shift-app-expo/shift-app-expo/post-issue-smartsheet.py': [Errno 2] No such file or directory
Error: Process completed with exit code 2.

Completed fix.
Solution: Creating a new issue after changes were made. Github actions run the code provided at the time it was run. If you try to re-run the failed job, it will run the same code and not the new code.


Improve interning in SQLMetadataSegmentManager

The segments that are stored in SQLMetadataSegmentManager.DATA_SEGMENT_INTERNER are the same as in SQLMetadataSegmentManager.dataSourcesRef, so we could effectively use the latter for interning. It allows to get rid of one large Map of weak references which are probably bad for GC themselves.
Also interning doesn't make sense in enableDatasource().
Originally interning was introduced in #3267.

Also related to #6358, that I intend to fix later.


[API-922] Add ATD Score to partner upload docs

Megha requested these docs to help convince partners to send more custom data. The bigger piece are mockups, which aren't in our court.
Anyhow, hidden in this PR is one question to ponder (see notes)

PTAL

As discussed this AM, we also had the question of URL parameter vs dictionary in the POST body for manual activity creation.  We could probably support both since URL parameters is more convenient if it's just one field, but unwieldy if it is many.

Discussed with @MateoAO to use the query string for manual uploads for now.  If there is enough extra data to need the post body, it's probably an indicator that the activity should use file upload instead of manual creation.


⚠ Bofrost.be has degraded performance

In 5e29059, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 2054 ms

Resolved: Bofrost.be performance has improved in ef0b9fd.


design a state space model

need some data which from running car to regress a matrix of state space


Edit Help

Add a "thing" on the Edit Song page which explains the Songdown syntax.

Oh, this got done. ^_^


Modify delta to have Bool storage

Description
Generically, having delta default to Float64 storage is causing problems with GPU (see #1143  and comment from @kmp5VT ) as well as converting previous codes to different types Float32/etc. One bandaid is to swap delta to have Bool storage so it can select the correct type when multiplying something later. However, there are some questionable uses of delta in the tests that now break, but I expect these won't be in many production codes.
However, this doesn't address the separate problem of matching an ITensor eltype, notably when GPU vs not GPU, so delta should probably be converted to something that only creates storage once a contraction is called
Minimal demonstration of previous behavior
ITensor ord=2 (dim=3|id=99) (dim=3|id=712)
NDTensors.Diag{Float64, Float64}

Minimal demonstration of new behavior
julia> i,j = Index.([3,3]); D1 = δ(i,j)
ITensor ord=2 (dim=3|id=427) (dim=3|id=721)
NDTensors.Diag{Bool, Bool}

How Has This Been Tested?

[x] Tests in test_diagitensor

Checklist:

[x] My code follows the style guidelines of this project. Please run using JuliaFormatter; format(".") in the base directory of the repository (~/.julia/dev/ITensors) to format your code according to our style guidelines.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] I have added tests that verify the behavior of the changes I made.
[ ] I have made corresponding changes to the documentation.
[ ] My changes generate no new warnings.
[x] Any dependent changes have been merged and published in downstream modules.

Thanks @ryanlevy. I'm hesitant to do this because it is definitely a band-aid and we are working on a full rewrite of NDTensors that will help fix these kinds of issues in a deeper way.
Can you share an example of where this was causing issues for you? A fix I have used for this kind of thing is to replace uses of δ(i, j, k) with δ(eltype(...), i, j, k) (where the element type is derived from some other tensors involved in the calculation), which we can either do inside the library or you can do in your own code. That isn't much different from how other constructors in Julia work, i.e. you shouldn't use a + randn(2, 2) if you want code to preserve the element type of a.

I can understand the hesitation. I would argue though that this helps catch strange uses of delta which shouldn't really be used, like in the hacked tests. Or we should just find a way to have a better gpu friendly dense(delta(i)) function.
As for the use case, I'm in the midst of making ITensorInfiniteMPS "type safe", and all the delta functions in the code are causing trouble, for example
subspace_expansion.jl
15:  δʳ(n) = δ(dag(r[n]), prime(r[n]))
16:  δˢ(n) = δ(dag(s[n]), prime(s[n]))
17:  δˡ(n) = δ(l[n], dag(prime(l[n])))
107:  δʳ(n) = δ(dag(r[n]), prime(r[n]))
108:  δˢ(n) = δ(dag(s[n]), prime(s[n]))
109:  δˡ(n) = δ(l[n], dag(prime(l[n])))
175:  δʳ(n) = δ(dag(r[n]), prime(r[n]))
176:  δˢ(n) = δ(dag(s[n]), prime(s[n]))
177:  δˡ(n) = δ(l[n], dag(prime(l[n])))

So for the immediate time I plan do as you suggest, but this would help make that code cleaner

I understand it is annoying to have to specify the element type, but since it is no more annoying than how other constructors in the Julia universe work I think we'll just have to live with this for now, and keep it in mind for our NDTensors rewrite.
I don't understand what you mean by:

I would argue though that this helps catch strange uses of delta which shouldn't really be used, like in the hacked tests.

I don't think we're going to do this at this point, it is not worth causing any breakages when we are working on a full rewrite anyway that will address issues like this. At worst, users (or ITensorInfiniteMPS.jl) can write delta(Bool, i, j) or delta(eltype(...), i, j) instead of delta(i, j).


Redesign trip overview

You can consider this Part I of the Detail Pages redesign. It's kind of more of a personal project because I always considered this the very ugliest part of the app (I particularly disliked how small and disconnected start and destination were: You'd probably never notice it at all since there are bigger, more colorful elements underneath - and if you did, you'd not get the connection right away).
I tried to fix that for the Drive Overview by making start and end bigger and bolder while making the times less bold and redesigning the rest of the info to be around, not strictly underneath that.
And yes, you heard correctly: There is now a Drive Overview, which means there is also a Ride Overview. The reason for the start-destination part of the overview not being a timeline is that we felt it looked weird on the Drive Detail Page (where there is a basically identical timeline underneath it, containing the stops and where to pick people up and drop them off). However, I split the Overviews because I still think it makes more sense on the Ride Detail Page to include a proper timeline, like you would see on the cards. If you don't like it, I can revert that. Also, I included the price in the Ride Overview.
Speaking of cards, I redesigned them just a smidge to make them consistent with the boldness and sizes of the start and destination texts of the Drive Overview. A side effect is that they now contain just a little less dead space, which was intentional.

Wow that text is insanely huge now.

When it already wraps after one word on the big emulator device I'm using - This might break complely on smaller devices.

Also, why is it "Date on the left - stuff - seats on the left"? Very asymmetrical and random

We already talked about this, but I don't like the visual inconsistency of having different designs for overviews... I guess there's no way around it if you hate the old one this strongly for some reason.
I assume recurring drives will use the DriveOverview? But have fun rebasing that.

The text is quite big on purpose. As I already talked about, this is to 1) make it stand out as the most important part of the page (which it is: Your eyes should first go to the overview and then to the detailed route plan) despite it not being as colorful or in the middle and 2) make the connection between the start and destination clearer: Before, the whole page looked like a row of columns because there were two elements that were near to each other on the left and on the right side and a big empty space in between. The bigger text size helps make the space smaller. (That is also why I put the date and seats on the left, because now it looks like a column with a row in it. I also tried to center date and seats and that looks bad.)
However, I admit that there isn't much room for long place names on your screen.  Because on my Pixel 6 emulator, I think things fit quite nicely. In any way, I don't think it's a huge problem because 1) As we have already noticed multiple times I think, the iPhone emulator screen which I suspect you're using is very small compared to even most screens out in the wild, 2) there aren't that many very long names and we can't make it look nice for every length, so I figure we should optimize the design for rather short ones (especially because the very long ones won't break the app, just look slightly worse), and 3) There is a huge gap between Flutter's built-in titleLarge, which I used, and titleMedium, which feels like half the size and isn't really bold and I would like to use standard designs because I deem them to have the highest longevity.

For the two overviews, maybe a little survey in the next meeting? I'm not hugely passionate about it, but I do think the timelines variant looks nicer for the Ride Overview.
Yes, for the Recurring Drives I think we could just use the DriveOverview with little adjustments.

However, I admit that there isn't much room for long place names on your screen.  Because on my Pixel 6 emulator, I think things fit quite nicely.

This is how it looks on a Pixel 5 which is still a relatively big phone compared to others that exist in the wild.

The text should not have to wrap into three lines for such a normal name. It just does not look good. I'm so paranoid because of the image that Felix sent me. I don't know exactly which device he has, but it is still a lot smaller than the Pixel 5 (I know that because I can see where it cut off the "Wir empfehlen deinen echten Namen" way earlier). We should not only design for big screen sizes, that would be an easy mistake to make.
I think the huge text is fine on the cards because there is more horizontal space. But in the DriveOverview there just isn't that kind of space.
I understand the huge gap, but I still think we should use the smaller font.

We can discuss that in a meeting.

i aggree with @fynsta the textsize is maybe a little bit to big, also the words a somtimes cut off at weird places. i had something where just the last letter was in a new line. I understand the idea that the overview should be the first thing you look at, but that's more important for the rides than for the drives. I think since there you have created it yourself and also have the timeline below with more information, it's okay if there the text is smaller.
For the RideOverview i agree with @Eddie-42, i like the timeline in think it's better that way because before the focus was to much on the Reviews. And i don't think the different design is a problem, after all rides and drives are different things


Backport: switch to https

Backport of https://github.com/apache/ant-ivy/commit/259d05439619d7c3aa9b028b49a561af41c2e163

Hi @bodewig,
Thank you for your contribution! We really value the time you've taken to put this together.
Before we proceed with reviewing this pull request, please sign the Lightbend Contributors License Agreement:
https://www.lightbend.com/contribute/cla


Init sets resources

In the past it left them empty, which caused problems.

  Generated by :no_entry_sign: Danger

Codecov Report

Merging #455 into master will increase coverage by 0.12%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #455      +/-   ##
==========================================
+ Coverage   68.54%   68.66%   +0.12%
==========================================
  Files         164      164
  Lines        9547     9553       +6
==========================================
+ Hits         6544     6560      +16
+ Misses       2498     2491       -7
+ Partials      505      502       -3

Impacted Files
Coverage Δ

lib/manifest.go
69.84% <ø> (ø)
:arrow_up:

lib/resolvefilter.go
84.04% <ø> (-0.34%)
:arrow_down:

lib/deployment.go
78.44% <100%> (+0.57%)
:arrow_up:

graph/targetmanifest.go
90.41% <100%> (+0.27%)
:arrow_up:

util/allfields/confirmtree.go
81.67% <100%> (-0.59%)
:arrow_down:

graph/otpldeploy.go
54.54% <100%> (+11.68%)
:arrow_up:

lib/startup.go
67.14% <0%> (+0.71%)
:arrow_up:

ext/docker/image_mapping.go
76.78% <0%> (+0.81%)
:arrow_up:

lib/resources.go
62.66% <0%> (+1.33%)
:arrow_up:

... and 2 more

Continue to review full report at Codecov.

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


Add First primitive

Add First aggregation primitive
The First primitive can be very useful, for example, to create features based on the first transaction done by a customer.

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


Is there an option that input can start with zero?

When I'm using that library and if the first number is 0, the zeros disappear. 🤔
Is there an option to control this?
If it doesn't have that option, it would be nice to add it.

It is designed for only number at the beginning.
Since it allows comma already, allowing only numbers doesn't really make sense any more.
I think it's a good idea to have that feature.
Would you be willing to help implement this feature?

Okay, I'll try


Apply EC420 11-ath10k-caldata changes supplied by TP-Link

Signed-off-by: Rick Sommerville<EMAIL_ADDRESS>

merged into pending, Thanks !


Restarting socket connection on foreground event

There is currently no indication to the user in the app whether or not they are connected to the socket. This can be frustrating as from their perspective they could be typing messages or controlling the bot but nothing will actually be happening despite the camera (powered by a web view) still updating.
We should add some form of message to the user when (re)connecting to the socket, and ensure when the app is brought into the foreground that the socket is connected.

Messages shown, looks like socket.io reconnects automagically


Need to create PURLs for UK admin units

We created and checked in OWL files (into development branch, at least) for United Kingdom admin levels 1-3 (and maybe even 4).  But now we need to update geo.yml file on OBO Library PURL GitHub with PURLs to these files.

Matt and I took care of this the week of 4/8


"A pull request already exists" error should show the url

When running hub pull-request, the "A pull request already exists for ..." error message should also show the URL, just like a successful attempt would do.

Good idea!
We'll need to make an extra HTTP request to fetch the existing PR ID, but it might be worth it. Will keep for consideration.

I would absolutely love this. We do a form of PR deploys instead of branch deploys (just naming semantics). It'd be nice to be able to run hub pull-request and get back either a URL I can parse or just the PR number that I can then use. Any of the following would be excellent:
fatal: pull request for branch `my-feature` already exists: #1652

https://github.com/org/repo/pull/1652

(this is nice because I can do hub pull-request | xargs open)
Your pull request already exists: https://github.com/org/repo/pull/1652

+1
I'm automating github pull requests and merges and this would be just a beautiful addition...
It would allow me to deploy fully without any manual interaction (saving me and other project maintainers so many precious hours each month)
If there is enough interest, I'll pull up the go documentation and write the thing myself. (just do +1 and tag me)

Alternatively, if you could see the branch names from hub issue or git issue then that would be a super-awesome feature.
We could check the exit status of hub pull-request, then based on that, see if a PR exists or not and take the appropriate action

i would like to see more an:
hub pull-request --check check if an exisiting pull request exists and display the id and/or name


generator: move test template to meta

This PR is the first in a series that will move all the pieces of an exercises generator under that exercise's .meta directory.
I'm striving to make each PR bite-sized.
The generator will now look for the tests_template in:

exercises/<problem>/.meta/test_template.erb
exercises/<problem>/example.tt <= temporary, until all templates are moved
lib/generator/test_template.erb <= default template

Tests added/updated and docs updated.
Part of the generator improvements: https://github.com/exercism/xruby/issues/485

Some suggestions: https://github.com/hilary/xruby/pull/5


#602 fix mapping of bundle to DTO

bundle symbolic name is not unique since multiple versions of a bundle can be installed.
Bundles without a symbolic name can now be mapped to a DTO

Fixes #602

Thanks a lot for fixing the issue 👍


 :-)  It would help not to mess (by accident) the repo and nobody should feel pain if he/she don't need it.

Hey @andreaspeters , there's already a gitignore file, in support/gitignore.
A link is created by the ./support/setup_dev.sh script:
cf@thinkpad:~/src/mesos$ ls -l .gitignore
lrwxrwxrwx 1 cf cf 17  8 avril  2020 .gitignore -> support/gitignore
cf@thinkpad:~/src/mesos$

You should run ./support/setup_dev.sh as recommended in the developer guide: https://github.com/apache/mesos/blob/master/docs/advanced-contribution.md#create-your-patch - it will add git hooks etc.

Ah perfect, works for me. Thanks Charles. :-)


fix: Only instantiate RawTable's reserve functions once

...per key-value.
Each of the previous closures would cause an entirely new reserve/resize
function to be instantiated. By using this trick (which std uses for
iterator adaptors), we always get a single instantiatiation per key
(modulo the insert_with_hasher method).

Thanks!
@bors r+

:pushpin: Commit 5e11d32570c1e0f708864a0285527dfb5f0ada44 has been approved by Amanieu

:hourglass: Testing commit 5e11d32570c1e0f708864a0285527dfb5f0ada44 with merge adf06c2e7f3371ffdbff04388d3894978fdf2bf4...

:sunny: Test successful - checks-travis
Approved by: Amanieu
Pushing adf06c2e7f3371ffdbff04388d3894978fdf2bf4 to master...


cmd/compile: spurious "cannot use reflect.Kind(9) … as type uint64 in assignment" on darwin-amd64-race builder

2020-03-01T21:02:40-e44cda3/darwin-amd64-race
# encoding/xml [encoding/xml.test]
/var/folders/9w/4l2_g3kx01x199n37fbmv3s80000gn/T/workdir-host-darwin-10_14/go/src/encoding/xml/marshal.go:849:62: cannot use reflect.Kind(9) (type reflect.Kind) as type uint64 in assignment
FAIL	encoding/xml [build failed]

CC @randall77 @josharian

This looks like either a race or memory corruption to me. I'm not sure which.

This comes from the serial part of the compiler, so I don't think this is a race.


Number Input - align width of horizontal stepper variant

Description / User story
The width of the stepper buttons in the stepper variant "horizontal" of the Number Input is not aligned between design and code.
In design the each stepper button should be squared (i.e. 32x32 in SM), but in code the width is smaller than it should be and even changes when the width of the wrapping container of the Number Input changes.
The width in code should be aligned with the width in design.
Requirements / Prerequisites

none

Acceptance Criteria

[ ] The width of the Stepper Buttons in the "horizontal" stepper variant of the Number Input is the same in code as in design (32 px in SM, 40 px in MD and 48 px in LG)

Additional information

...

Code of Conduct

[X] I agree to follow this project's Code of Conduct

I'd like to give this a try @thrbnhrtmnn.

Hey @AnukratiMehta , thanks for reaching out and for wanting to contribute to the project!
Unfortunately we are currently doing a massive update to our CSS, so I would highly recommend to wait a bit before starting this issue. We probably will finish it this week, maybe even today. I will let you know when this can be started :-)

Hello @AnukratiMehta , it took a bit longer, but we just finished the CSS update. If you still want to give this a try, please go ahead :-)


[release/v1.26] fips: fix Wasm extensions to comply with FIPS

Commit Message: Fixes a build issue with Wasm extensions triggering a non-FIPS mode when included into Envoy.
Risk Level: low
Testing: yes
Docs Changes: none
Release Notes: yes

/retest


Cancel Email (Old 242)

In gitlab by @A-Lawrence on Aug 31, 2015, 01:08
Allow users to cancel emails from the Queue::view page.
When doing this there are a few things to remember:

Get a reason from them.
Log the cancellation with the reason.
Check they have the right permission to perform this action.

In gitlab by @A-Lawrence on Aug 31, 2015, 01:14
Issue #488480 (262) was marked as a duplicate of this issue.
ALawrence66 - 2015-03-03T00:00:27.832629+00:00

In gitlab by @A-Lawrence on Jan 11, 2016, 00:48
No longer applicable.  We moved to using queues - chances of catching the emails are now slim.


escaping too much?

for some reason this:
$('div.input table tr.attachment-row .remove_row').click()
<% if @project.portfolio %>
portfolio_id = '<%=escape_javascript @project.portfolio_id.to_s %>'
portfolio_name = '<%=escape_javascript @project.portfolio.name %>'
portfolio = $('#project_portfolio_id')
option = portfolio.find('option[value='+portfolio_id+']')
if option.length is 0
  optionhtml = '<option value='+portfolio_id+'>'+portfolio_name+'</option>'
  portfolio.find('option').last().before(optionhtml)
portfolio.val(portfolio_id)
<% end %>

is rendering as this:
/*snip*/

if (option.length === 0) {
  optionhtml = '<option value=' + portfolio_id + '>' + portfolio_name + '</option>';
  portfolio.find('option').last().before(optionhtml);
}

/*snip*/

not the problematic <, > also if i use the rubyish string evaluations ("foo#{var}bar...") it escapes my double quotes and i end up with invalid syntax... why!? is this coffee beans' fault?

so ok, the issue i was having was a result of including coffeescript as a partial without escaping it. everything above was being htmlescaped because it was being included below
<%= render :partial => 'filefields'%>

changing it to this:
<%=raw render :partial => 'filefields'%>

perhaps the problem is that the containing file wasn't a .js.coffee, but a .js.erb it seems that the string returned by coffeebeans is not html_safe, so it might be easy to fix that in the gem.

I'll happily release a new version with html safe string if you want to send a pull request.

added a pull request