FastHttpLocust bug...

I'm unable to open new issue in geventhttpclient repo.
Reporting it here instead:
Describe the bug
Getting tons of errors like this during locust run:
UnboundLocalError: local variable 'e' referenced before assignment
Expected behavior
No error (i.e. same as HttpLocust)
Actual behavior
Error log has messages like this:
[2019-11-06 00:57:24,812] WIN/ERROR/stderr: Traceback (most recent call last):
  File "c:\users\user\.conda\envs\locust\lib\site-packages\locust\core.py", line 374, in run
    self.execute_next_task()
  File "c:\users\user\.conda\envs\locust\lib\site-packages\locust\core.py", line 400, in execute_next_task
    self.execute_task(task["callable"], *task["args"], **task["kwargs"])
  File "c:\users\user\.conda\envs\locust\lib\site-packages\locust\core.py", line 412, in execute_task
    task(self, *args, **kwargs)
  File "C:\netsh\Locust\HealthCheck\HealthCheck.py", line 9, in favicon
    l.client.get("/ImgSmall/pkp264d-img.jpg")
  File "c:\users\user\.conda\envs\locust\lib\site-packages\locust\contrib\fasthttp.py", line 207, in get
    return self.request("GET", path, **kwargs)
  File "c:\users\user\.conda\envs\locust\lib\site-packages\locust\contrib\fasthttp.py", line 166, in request
    response = self._send_request_safe_mode(method, url, payload=data, headers=headers, **kwargs)
  File "c:\users\user\.conda\envs\locust\lib\site-packages\locust\contrib\fasthttp.py", line 113, in _send_request_safe_mode
    return self.client.urlopen(url, method=method, **kwargs)
  File "c:\users\user\.conda\envs\locust\lib\site-packages\geventhttpclient\useragent.py", line 397, in urlopen
    return self._handle_retries_exceeded(url, last_error=e)
UnboundLocalError: local variable 'e' referenced before assignment

Steps to reproduce
A basic locustfile.py with small values for:
	min_wait = 50
	max_wait = 75

or
	min_wait = 0
	max_wait = 0

Environment settings
Windows server 2019 with following conda env:
# packages in environment at C:\Users\user\.conda\envs\locust:
#
# Name                    Version                   Build  Channel
ca-certificates           2019.10.16                    0
certifi                   2019.9.11                py37_0
click                     7.0                      pypi_0    pypi
flask                     1.1.1                    pypi_0    pypi
gevent                    1.4.0                    pypi_0    pypi
geventhttpclient          1.3.1                    pypi_0    pypi
geventhttpclient-wheels   1.3.1.dev2               pypi_0    pypi
greenlet                  0.4.15                   pypi_0    pypi
itsdangerous              1.1.0                    pypi_0    pypi
jinja2                    2.10.3                   pypi_0    pypi
locust                    0.0                      pypi_0    pypi
locustio                  0.12.2                   pypi_0    pypi
msgpack-python            0.5.6                    pypi_0    pypi
openssl                   1.1.1d               he774522_3
pip                       19.3.1                   py37_0
python                    3.7.5                h8c8aaf0_0
setuptools                41.6.0                   py37_0
six                       1.13.0                   pypi_0    pypi
sqlite                    3.30.1               he774522_0
urllib3                   1.23                     pypi_0    pypi
vc                        14.1                 h0510ff6_4
vs2015_runtime            14.16.27012          hf0eaf9b_0
werkzeug                  0.16.0                   pypi_0    pypi
wheel                     0.33.6                   py37_0
wincertstore              0.2                      py37_0

You seem to have both the geventhttpclient and geventhttpclient-wheels packages installed. That seems odd, so you could try re-creating a new virtualenv.
It seems more likely that this is an issue that should be reported to the geventhttpclient project: https://github.com/gwik/geventhttpclient
The FastHttpClient is somewhat experimental and AFAIK it hasn't been tested in windows at all.

Jonatan,
It was minimal install with:
conda create --name locust -y python=3.7
conda activate locust
pip install locust
pip install geventhttpclient

I’m pretty sure, the error like:
UnboundLocalError: local variable 'e' referenced before assignment
has nothing to do with installed packages.
I’ll re-report it in : https://github.com/gwik/geventhttpclient repo as you suggested,
Thanks!

There's no need to manually install geventhttpclient using pip install geventhttpclient (I've now removed that outdated info from the docs).

I’m pretty sure, the error like: ... has nothing to do with installed packages.

Well, the stacktrace refers to an error in that specific package, so I want to exclude that the reason could be that you're running code some other code. I believe that the PyPI-released version of geventhttpclient is old and outdated.

Jonatan,

I believe that the PyPI-released version of geventhttpclient is old and outdated.

Installed from github, got same major version 1.3.1...
I’ve re-created fresh conda env with:
pip install git+git://github.com/gwik/geventhttpclient@master
The only difference is geventhttpclient 1.3.1.dev0 instead of 1.3.1:
New conda env:
gevent                    1.4.0                    pypi_0    pypi
geventhttpclient          1.3.1.dev0               pypi_0    pypi
geventhttpclient-wheels   1.3.1.dev2               pypi_0    pypi
greenlet                  0.4.15                   pypi_0    pypi

Old conda env:
gevent                    1.4.0                    pypi_0    pypi
geventhttpclient          1.3.1                    pypi_0    pypi
geventhttpclient-wheels   1.3.1.dev2               pypi_0    pypi
greenlet                  0.4.15                   pypi_0    pypi

Jonatan,
You were right, it’s fixed in geventhttpclient 1.3.1.dev0
I’ve rerun Locust 1.3.1.dev0, no errors this time!
Thanks!

Should we update this page and recommend to install geventhttpclient from github instead?

The documentation is already updated in master:
https://docs.locust.io/en/latest/increase-performance.html
You don't need to install the geventhttpclient package manually at all, since the package is provided by the geventhttpclient-wheels which is included in Locust's default dependencies.

Jonatan,

You don't need to install the geventhttpclient package manually at all, since the package is provided by the geventhttpclient-wheels which is included in Locust's default dependencies.

You are absolutely right, my bad...

Very understandable though, since the documentation contained outdated info!


Docker container doesn't start

I'm running HA on Ubuntu 22.04 using docker. I've installed several other addons successfully, however when I try to install the onedrive backup add on it installs, I can click "start" but when I then try to go to the UI it says "Add-onn is not running. Please start it first"
In system log it shows this:
May 15 22:51:03 server kernel: [123242.008009] audit: type=1400 audit(1684187463.186:76): apparmor="DENIED" operation="create" class="net" profile="de91e161_hassio_onedrive_backup" pid=292057 comm=2E4E455420546872656164506F6F6C family="inet6" sock_type="dgram" protocol=0 requested_mask="create" denied_mask="create"
May 15 22:51:03 server kernel: [123242.008014] audit: type=1400 audit(1684187463.186:77): apparmor="DENIED" operation="create" class="net" profile="de91e161_hassio_onedrive_backup" pid=292057 comm=2E4E455420546872656164506F6F6C family="inet" sock_type="dgram" protocol=0 requested_mask="create" denied_mask="create"
May 15 22:51:03 server kernel: [123242.010307] audit: type=1400 audit(1684187463.186:78): apparmor="DENIED" operation="create" class="net" profile="de91e161_hassio_onedrive_backup" pid=292057 comm=2E4E455420546872656164506F6F6C family="inet6" sock_type="stream" protocol=6 requested_mask="create" denied_mask="create"

These are conflicting permissions with the apparmor profile defined for the addon. This doesn't present any issues though when running on HassOS or Supervised to my knowledge.
You are running with Supervisor right ?

This is what I'm running, technically it's an unsupported setup as the OS is too new:
Version | core-2023.5.3
Installation Type | Home Assistant Supervised
Development | false
Supervisor | true
Docker | true
User | root
Virtual Environment | false
Python Version | 3.10.11
Operating System Family | Linux
Operating System Version | 5.19.0-41-generic
CPU Architecture | x86_64
Timezone | Europe/London
Configuration Directory | /config
Home Assistant Supervisor
Host Operating System | Ubuntu 22.04.2 LTS
Update Channel | stable
Supervisor Version | supervisor-2023.04.1
Agent Version | 1.5.1
Docker Version | 23.0.6
Disk Total | 233.2 GB
Disk Used | 80.5 GB
Healthy | true
Supported | Unsupported
Supervisor API | ok
Version API | ok

Adding this to the apparmor file for the add-on does allow it to work, but I don't know enough about the architecture to know if this is the correct solution
network,
deny network raw,

I'm not sure either. If this was applicable to all supervised installations it might shed more light on why the profile is failing but I'm not aware of issues with other Supervised installations.
You're saying updating the apparmor file resolved this for you ?

Yes, updating that apparmor file with those two lines fixed it for me.
I'm running another 10 add-ons and don't have any other apparmor files in /usr/share/hassio/apparmor other than the hassio-supervisor one and the one I edited for onedrive backup

This also solves my issue #84

This also solves my issue #2

Great! I will make modifications to the packaged apparmor file to accomodate the needed permissiosn for supervised installs.

This should now be resolved in 2.1.2


Fix #271: [trader bot] baseline trader bot doesn't actually trade yet

Fixes #271
Note: Roberto had created the branch. I simply created the PR so that I could give comments on the code. It's still Roberto's work:)

[MEXC API + Predictoor Feed Challenges]

Most USDT pairs (BTC, ETH, XRP) are not available to trade via their API/[UI-Allow-List].
Their [UI-Allow-List] offers BTC/USDC, however this market does not get listed in the CCXT library
To verify the CCXT implementation is working, I need a test/real market to validate. Searching...
MEXC python lib may offer perps/USDC :shrug: however I'm hoping to wrap this with a CCXT implementation, so it should hopefully work with BNB.

-> Bot is trading w/ MEXC.
-> Will run black/pylint and get the tests passing.
-> Additional work has been branched into Agent2, and pushed as a draft PR.

Let's see what happens...

I have now:

Created a different file for test_ccxt_exchanges
Created new test coverage for test_trader_agent1.py, which includes async tests which were not passing
Fixed existing test coverage inside test_trader_agent.py that was being skipped by CICD, such that it's now executed correctly and passing
Updated setup.y so pytest-asyncio is now being installed


Create a Room page

Issue
There is no room page right now.
Task
Frame a room page in order to make it easier later.
To-do

[x] Create a new branch
[x] Follow Clara's Mid Fi design to make all the room page information
[x] Do not include the Your Reservation window yet. NavBar not necessary.
[x] Pass in the following props and display them

Building Name
Room Number
Img source
Location
Capacity
Amenities

[x] Make a pull request

Need to method to display image on the room page. App.tsx was modified with a Room object to hardcode the Room page.

Resolved for now. Issue will be reopened at a later date.


Windows security recognizes pixivutil2 as Malware

Prerequisites

[x] Did you read FAQ section in readme.md?
[x] Did you test with the latest releases or commit ?
[x] Did you search for existing issues in Issues?

Description
Windows security recognizes pixivutil2 as Zpevdo.B
Steps to Reproduce

execute Pixuvutil2
Windows security takes action

Expected behavior:
normal execution
Actual behavior:
windows security blocked internet access and i had to "unquarantine" the "severe" threat
Versions
2021-07-02

pls run from source code if you are not sure, no changes will be provided on the exe (or rather I cannot do anything).

Oh, i know you did nothing and that your program does nothing wrong.
I am just warning you that as of this morning it gets recognized as such, so you can take steps to avoid it.

Fyi, I tried to scan locally and it didn't detect anything.

Also I tried to download the file in https://github.com/Nandaka/PixivUtil2/releases/tag/v20210702 = it didn't detect anything.

that contrasts my experience this morning (a couple of hours ago)

Virus Total confirms Microsoft detects it, along with eight other antiviruses.
https://www.virustotal.com/gui/file/fd67f71e83e00d5baf325ba983da38a4787f38602e90e58e5b85e79cf4dffcb4/detection

Weird, what is the SHA256?

10FAB3245175FCE17D6D15C6E766AD6027F74F49BC9FEF78FB2AA5AAF0C28F58

Here is the result from virus total, but I don't see Zpevdo.B

The scan I linked was of PixivUtil.exe, not the release zip.
Also the SHA256 of the zip is the same as yours.

10fab3245175fce17d6d15c6e766ad6027f74f49bc9fef78fb2aa5aaf0c28f58

I guess if you want to avoid this, you can run it from source code, which have better compat, see https://github.com/Nandaka/PixivUtil2/wiki/IDE-Enviroment-(Windows)

i get a virus sresult from MSE

Same problem. Switched to previous version.

run from source is recommended: https://github.com/Nandaka/PixivUtil2/wiki/IDE-Enviroment-(Windows)

it says you need to "download the required library:" but does not say which. Will try later if there actually is anything to add or if it is all handled by the "requirements.txt" once i have time to exist.

pip install -r c:\pixivutil\requirements.txt

This will add the required library.

i tried that... all i got was to get pixivutil2.py removed by windows as "being remotely controlled by an agent"

the heck, then I have no idea anymore...

probably misidentifies some component as a "remote agent" and actions are taken to prevent it taking control.
That said for now i went under:
settings>update and security>windows security>virus and threat protection>virus and threat protection settings>exclusions>add exclusions
and added PixivUtil2.exe and .py as exclusions

Was PyInstaller used for the exe?

I went ahead and submitted it to microsoft, so hopefully they'll clear it and windows defender doesn't keep quarantining it.

Do you use the precompiled bootloader? If you do, recompiling your own might get the false positive detections to go down, but after that there's not much else to do other than reporting it to the companies.

I'm using pip to install/update the library, so I don't think it re-compile anything. I assume it just use the packaged whl file.

I went ahead and submitted it to microsoft, so hopefully they'll clear it and windows defender doesn't keep quarantining it.

Thanks 😄

Alright Microsoft got back and said it was cleared, just checked virustotal, it's no longer showing it as detected under Microsoft-
https://www.virustotal.com/gui/file/fd67f71e83e00d5baf325ba983da38a4787f38602e90e58e5b85e79cf4dffcb4/detection
If someone can test if defender still quarantining that'd be great

@Nandaka
Looks like this is happening again with v20210822, but it's detecting Trojan:Win32/Wacatac.B!ml instead. Didn't want to open a new issue because it's basically the same thing as this one.

It seems to flag the zip but nothing inside the zip.  I unpacked it and had no further detections from it.

weird. I also try to compress it as 7z and it still show as virus in virustotal...

recompile with py3.8.10 got slightly different result.

Windows Defender decided it's something new today.

3 detections in 1 day

run from source is recommended: https://github.com/Nandaka/PixivUtil2/wiki/IDE-Enviroment-(Windows)

This is my first time I'm running it from source. Is this going to detect the old database file, settings, etc. or do I need to do something to else to restore them?

Avast recognizes 'PixivUtil2.exe' in 'pixivutil20220924-64bit.zip' as malware.
Even if an exception is handled, the command prompt window is immediately closed.


better switch-case/switch-when compilation

Fallthrough cases should be compiled to when A, B, not
when A
when B

This is also #76, which has been fixed.


support CREATE TAG privilege

Is your feature request related to a problem? Please describe.
│ Error: expected privilege to be one of [CREATE PROCEDURE CREATE MATERIALIZED VIEW CREATE STAGE CREATE TABLE CREATE FILE FORMAT CREATE TASK CREATE SEQUENCE MONITOR CREATE VIEW CREATE PIPE CREATE FUNCTION CREATE EXTERNAL TABLE CREATE TEMPORARY TABLE ADD SEARCH OPTIMIZATION USAGE OWNERSHIP CREATE STREAM CREATE ROW ACCESS POLICY CREATE MASKING POLICY MODIFY], got CREATE TAG
│
│   with module.databases["PROD_JAFFLES"].snowflake_schema_grant.additional_admin_privileges["CREATE TAG"],
│   on modules/database/grants.tf line 100, in resource "snowflake_schema_grant" "additional_admin_privileges":
│  100:   privilege     = each.key

Describe the solution you'd like
The schema grant can apply the CREATE TAG privilege.
Additional context
Not supported in v0.25.23

@tekumara this change is merged in and should be included in the next release.


feat: use vue history mode

Type of modification

[ ] Breaking change
[X] New Feature
[ ] Bug Fix
[ ] Chore (refactor, documentation, tests... all the changes with no impact on ARA functionalities.)

Changes description
closes #23
Add some quick description about what your PullRequest change in
ARA's feature/behavior
Technical description
Add a quick description about what your PullRequest change in
ARA's code. (example: add a processor check in...)
PR CheckList
Please make sure your PullRequest respect all those items :

[ ] Your PR's title has the prefix : feat:, fix: or chore:
[ ] You have asked a review from one of the ARA maintainer in your PR.
[ ] If your PR is related to an issue, add the issue's number in it.
[ ] All the code you added is documented.
[ ] All the code you added is tested and the  tests are in success.
[ ] You already signed the Contributor License Agreement and give us the document

:tada: This PR is included in version ara-client-v1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Updates draw method scale parameter: SamplePulse, Schedule

Summary

Adjust scaling parameter in Schedule.draw to ensure consistent zooming behaviour with SamplePulse.draw function
Deprecate scaling parameter in Schedule.draw use scale_factor instead.
Deprecate scaling parameter in SamplePulse.draw, use scale_factor instead.

Details and comments
Fixes 3420

@tobeyOguney Thanks for handling this issue! the word scale may refer to the format of axis, I prefer the words such as magnification or scale_factor.
instead of converting scale value, you can replace this line by -1/scaling, 1/scaling to align with current schedule drawer interface (scaling=magnification).
https://github.com/Qiskit/qiskit-terra/blob/86103724cb53b5cc64a672c86510de3706e98d30/qiskit/visualization/pulse/matplotlib.py#L263-L264

Hi nkanazawa1989!
I've tested inverting the scaling methods just like you suggested and it fixes this.
Also, I guess scale_factor will be a better replacement for scale.
Thank you.

@tobeyOguney Looks great! I think this can be merged!

Issue #3420 regards the printed output of schedule drawing. In the issue, you showed a solution for improving the output. As is, this PR should not close that issue. Is there another PR with the rest of the changes?
A note for the future: please give your branches more descriptive names next time:) for this PR, something likerename-scaling-to-scale_factor could have been a better choice than staging.

Hi @lcapelluto,
I originally commited the changes I showed in the issue,
However, @nkanazawa1989 suggested a neater change for the printed output,

@tobeyOguney Thanks for handling this issue! the word scale may refer to the format of axis, I prefer the words such as magnification or scale_factor.
instead of converting scale value, you can replace this line by -1/scaling, 1/scaling to align with current schedule drawer interface (scaling=magnification).
https://github.com/Qiskit/qiskit-terra/blob/86103724cb53b5cc64a672c86510de3706e98d30/qiskit/visualization/pulse/matplotlib.py#L263-L264

So I implemented and commited that instead.
Thanks for the note. (I recently just started contributing to open source).

@tobeyOguney ah, wonderful! That one line was the line I wasn't noticing, thank you for pointing it out.
We really appreciate your contribution! 😄

This looks good. In the issue, @ajavadia thought scale would be better than scaling in order to keep the args the same between pulse and circuits. If the parameter was called scale_factor, then we don't get that benefit, and then I would prefer to avoid deprecation. @ajavadia, can you give the final say on this?

Yes I brought up the argument change for consistency with other visualization functions. Otherwise there is no point going through a deprecation of scaling.
I understand the confusion with the term 'log-scale' or 'linear-scale', but I think the context makes it clear. Those are for axis, here we are using it to mean 'large-scale' or 'small-scale'.
Maybe zoom is a good choice of word (https://matplotlib.org/gallery/api/axes_margins.html).
But I really would like the visualizers to be consistent. So can we call it scale here and then deprecate them all if so desired, to replace with another word?

@nkanazawa1989 What do you think?

I agree with @ajavadia . We can use scale for consistency, with sufficient description of behavior in docstring (see circuit one). Please update arg names and dosctrings of methods as well.
https://github.com/Qiskit/qiskit-terra/blob/debbd39f417370d43994695bd2ed9519056454c6/qiskit/pulse/schedule.py#L359-L375
https://github.com/Qiskit/qiskit-terra/blob/debbd39f417370d43994695bd2ed9519056454c6/qiskit/pulse/commands/sample_pulse.py#L108-L121

Okay, I've commited the changes as recommended.

@tobeyOguney Thank you! This is great. I think it's ready, but we should include a reno note (the release notes).
You will have to pip install reno and then run reno new <short-description>, e.g. reno new update-scaling-draw-option. This will generate a file, which you should edit. Keep the section that says deprecations and other. Under deprecations, you'll want to say that scaling was deprecated in favor of scale for consistency with circuit drawing. An example is usually nice. Under other, explain the change in how it's used (that one liner).
Thanks again!! almost there:))

Thanks a lot for the guide @lcapelluto, it was very helpful.
I'm done adding the reno note.

Are there tests that used scaling that could be migrated?

It doesn't seem like any do. I've created an issue here to track #3568.

can this be merged?


Generated vega-lite spec does not render when NL4DV is initialized using a .tsv dataset file

ToDo/Solution: Based on the input file-extension (e.g., csv, tsv), determine the appropriate value in the vega-lite spec:
"data": {
    "format": {
      "type": "csv"
    },


Add better ok tracking, masking bad data in plots, bin warnings, and more?

Eep, I think I glumped too many things into one pull request here. The key changes include:

Make better use of .ok to allow tracking of data that are not OK, to mask in visualizations, calculations, or fits. The .ok property will live-calculate a 2D array of "OK-ness" from .fluxlike['ok'] (this point is bad), .timelike['ok'] (all wavelengths at this time are bad), and .wavelike['ok'] (all times at this wavelength are bad).
Add .get_for_wavelength and .get_for_time helpers to grab 1D arrays either from 2D or (appropriate) 1D arrays.
Add .get_ok_data_for_wavelength and .get_ok_data_for_time helpers to grab three parallel arrays for the good data associated with a particular wavelength/time. Defaults will be x, y, sigma = get_ok_data_for_[wavelength/time](i_wavelength) gives x as [time/wavelength], y as flux, and sigma as flux uncertainty, but they're flexible to allow you to select different quantities for any of x, y, or sigma.
plot, imshow, pcolormesh, animate_* will by default mask out bad data, as tracked by .ok. A few other changes needed to be made to these visualizations to accommodate the ok tracking, but hopefully they should still work out of the box.
Add option to animate_[lightcurves/spectra] to allow quantities besides flux.
Some improvements were made to the default .rainbow.fits writer to give some more informative comments in the FITS header for how to interpret the file.
Fix a bug where uncertainty wasn't getting set for SimulatedRainbow; hopefully this will ease the transition into the new .inject_noise() way of operating (see #119 ).

All 66 tests pass. Updated version to 0.2.0.

There are probably some documentation updates that should accompany this, but I think I need to give those a close look soon anyway. I don't think I broke anything in there, but there are definitely some missing features that should ultimately be explained.


Preview image next to file list (similar to ranger)

Would it be possible to have an option to have something like this?

I am pretty sure this is possible because neofetch is able to show an image next to the text.

I just installed fff and thought this would be nice - or the ability to press I to preview image and then use up/down for next/prev image. Pressing i j j i for next image is kinda overkill. Or am I missing something?
Btw. fff is great!


Status update and potential move

Hey @nickcowle!
Do you intend to continue working on this?
Gregor Beyerle is interested in trying to experiment with FSharp implementation of Alga:
https://twitter.com/GBeyerle/status/971093746665353221
I thought he might look here first.
Note: there are experimental implementations in Agda and Scala here: https://github.com/algebraic-graphs. Perhaps we could move this repository there as well to make it easier to discover?

Hey @snowleopard,
Apologies for the radio silence – I’ve only just managed to find the time to work on this. I didn’t think the library was really worth moving to https://github.com/algebraic-graphs before, but now I’ve done more work on it, I’d be happy for it to move.
Thanks,
Nick

Many thanks @nickcowle! I've invited you to join the algebraic-graphs organisation. I believe that once you are in, you will be able to transfer the repository. I suggest we call it algebraic-graphs/fsharp for consistency with other implementations.

Hey @snowleopard,
Thanks for the invite to algebraic-graphs! I've transferred the repo across, but seem to have lost perms to change the repo name in the process - would you be able to rename it to fsharp as you suggested?

Thanks @nickcowle! Done. I've also made you an Admin in this repository -- you should be able to do everything you like with it :)
I think this issue can now be closed.
P.S.: I hope to play with your library next week, after Haskell eXchange :)


Demo fails on DateTime search.

Run demo project.
Try to search for 2012 in Start Date column.
See error message "DataTables warning: table id=fingers10 - Internal Server Error"
"Loading Data" spinner gets stuck forever.

Hi @dbychkov ,
You need to search the full date. Not the year part alone. Please try searching the full date.
Thanks,
Abdul Rahman

Yes, I understand that but it crashes the whole thing if the user types
part of the date and table becomes unusable, it becomes stuck in the
loading data phase. The same thing happens if I try to search for text data
in a numerical column.
===
Thanks.
Dmitriy Bychkov
On Tue, Dec 3, 2019 at 12:46 PM Abdul Rahman<EMAIL_ADDRESS>wrote:

Hi @dbychkov https://github.com/dbychkov ,
You need to search the full date. Not the year part alone. Please try
searching the full date.
Thanks,
Abdul Rahman
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/fingers10/JqueryDataTablesServerSideDemo/issues/5?email_source=notifications&email_token=ABAYYBB37DNTBAECGEKIXITQW2LQLA5CNFSM4JU3CCC2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEF2HHPI#issuecomment-561279933,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABAYYBBROGOBZ57QELAZWWTQW2LQLANCNFSM4JU3CCCQ
.

sorry for the delayed response. Jquery DataTables have a regex option for searching. Does that help you in any ways?
Thanks,
Abdul Rahman

I'm closing this as I don't get any response.


Adds mean of transport (bus, boat, etc.) option in the TR

adapt the SDK / GUI to allow TR searches for specific means of transport (i.e. bus)

@AndreasAtSBB @TO-mdv can we get a TR request XML example with a triprequest for boat or bus only?

I attache an example for ships (water). Same princip works for bus, tram, train etc.
TR for ships only.txt

Deployed to PROD


name 解析错误

当js内存在 name字段的json就会解析错误

get it.    In the second half of the year we will look at how to optimize vuese as a whole

get it. In the second half of the year we will look at how to optimize vuese as a whole

能简述一下你们关于as a whole的计划么？很感兴趣，谢谢。

这个bug还没解决吗


export { type <ident> } does not result in <ident> being marked as a type

Describe the bug
export { type <ident> } does not result in <ident> being marked as a type, and as such does not get stripped out unless declared with type in the import.
Additionally export {} is omitted with export { type <ident> } even though it should not be. This is the distinguishing factor between export { type <ident> } and export type { <ident> }
Input code
import { A } from "./a.ts";
export { type A };

Config
No response
Playground link
https://play.swc.rs/?version=1.3.39&code=H4sIAAAAAAAAA8vMLcgvKlGoVnBUqFVIK8rPVVDS00%2FUKylWsuZKrYDKlVQWpIIUWAMAXodgqi4AAAA%3D&config=H4sIAAAAAAAAA0WNSwrDMAxE76J1ts0id%2BghjKsEF%2F%2FQKBBjfPfawSU7aebpqdIXlrZK2QhYxoQS1Vy0kZbMsOKy0kKKHu3Gg1tfjBysHWG8eudTAs92oeCi28sw2RSyMPBUJh7%2BT7YuCulzjqDez27hSu1xzDuH9wRVTm4%2FOkwQUrUAAAA%3D
Expected behavior
export {};

Actual behavior
import { A } from "./a.ts";

Version
<EMAIL_ADDRESS>Additional context
TSC behaviour with isolated modules: https://www.typescriptlang.org/play?isolatedModules=true#code/PTAECMDoBcGcCgCWBbADgewE7VAb1AIKgC+oAZpusqAESTACGkAVrDQNzwCmAHhtnlDQAnqi6ES7IA
Babel bug: https://github.com/babel/babel/issues/15493

Thanks!


Paket managed references brings Visual Studio in trouble

We changed our dependency management to Paket.
The build runs fine, everything is OK.
But in case we open such a project in Visual Studio it is marked with the yellow exclamation mark. Again, build is possible without any issues.
Unfortunately, we also use DevExpress and during design time we cannot use it anymore, because the types from these packages are unknown then.
But this behavior is not the same for different machines. We have one machine without that issue and two with it. All are more or less identical from the setup. We use the same baseline (hardware, software) for them.
One slight difference: the machine where it works has VS2019 only, the second one only VS2017 and the last one VS2017 and VS2019.
In the screenshot, you can see the point.
We have the bundled the Microsoft.VisualBasic assembly in an own NuGet package named StepAhead.Microsoft.VisualBasic.
Also interesting, at the machine where it works the package is not visible, only the DLL. Here the other screenshot.
What's the trick to get it run?

Are you using dotnet cli?
Marko Apfel<EMAIL_ADDRESS>schrieb am Fr., 3. Mai 2019, 15:06:

We changed our dependency management to Paket.
The build runs fine, everything is OK.
But in case we open such a project in Visual Studio it is marked with the
yellow exclamation mark. Again, build is possible without any issues.
Unfortunately, we also use DevExpress and during design time we cannot use
it anymore, because the types from these packages are unknown then.
But this behavior is not the same for different machines. We have one
machine without that issue and two with it. All are more or less identical
from the setup. We use the same baseline (hardware, software) for them.
One slight difference: the machine where it works has VS2019 only, the
second one only VS2017 and the last one VS2017 and VS2019.
In the screenshot https://paste.pics/5GDEY, you can see the point.
We have the bundled the Microsoft.VisualBasic assembly in an own NuGet
package named StepAhead.Microsoft.VisualBasic.
Also interesting, at the machine where it works the package is not
visible, only the DLL. Here the other screenshot
https://paste.pics/5GDKI.
What's the trick to get it run?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/fsprojects/Paket/issues/3565, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAOANFI7EUWPLGLW2KSZMTPTQ2D7ANCNFSM4HKTYSUA
.

Paket installed as described here.
Then used with
paket init
paket convert-from-nuget --force
paket install --force
...

current version:
PS C:\...\WindowsFormsApp1\.paket> .\paket.exe --version
Paket version 5.203.2

No I meant your projects. Is it new dotnet sdk based?
Marko Apfel<EMAIL_ADDRESS>schrieb am Fr., 3. Mai 2019, 15:43:

Paket installed as described here
https://fsprojects.github.io/Paket/installation.html#Installation-per-repository
.
Then used with
paket init
paket convert-from-nuget --force
paket install --force
...
current version:
PS C:...\WindowsFormsApp1.paket> .\paket.exe --version
Paket version 5.203.2
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/fsprojects/Paket/issues/3565#issuecomment-489100019,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAOANBIPYEZBBB3RMQIVOTPTQ6RRANCNFSM4HKTYSUA
.

The screenshots are from a project which is a simple NETFX WinForms app.
Inside the (classic) csproj file are some conditions which look fine and seems to be fine because compilation works also inside VS.

After additional investigations, the issue is solved.
In the obj folders, Visual Studio caches some Package knowledge. Notably with packages from our private NuGet feed that cache gets into conflict during/after migration to Paket.
Deleting the obj folders fixes that issue.
Maybe content for a troubleshooting guideline?

We fixed couple of other issues around obj today. maybe this would help...


Potential Race Condition or Garbage Collection Issue during JNI Environment Usage

Description
The issue arises when a JVM exception is thrown before invoking JNI code, leading to a garbage collection and race condition problem. This results in the env variable not existing in the following line:
let obj = env.new_object_unchecked(cls, constructor, &offsets_vec[..]).unwrap();

Expected Behavior
The expected behavior is for the environment object to be properly accessible. It would be nice if an exception were thrown instead of the JVM being crashed.
Error Message
thread '<unnamed>' panicked at src/lib.rs:442:22:
called `Result::unwrap()` on an `Err` value: JavaException
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
fatal runtime error: failed to initiate panic, error 5
rlwrap: warning: clojure crashed, killed by SIGABRT (core dumped).
rlwrap itself has not crashed, but for transparency,
it will now kill itself with the same signal

How to Reproduce?
The error can most effectively be replicated by employing infinite recursion to generate tokens. I not providing a specific example because we use Clojure, which has too many parentheses to fit into an example.
Steps to reproduce
Like above.
What have you tried to solve it?

Reviewing the rust/JNI code

Environment Info
Since the issue is related to JNI and JVM interaction, rather than a problem specific to the DJL framework, running ./gradlew debugEnv as suggested might not provide the relevant environmental information needed to debug this issue.

In JNI, if a java exception is thrown, it will continue to execute the next line of JNI code until the function returns. Handling java exception in JNI code is quite cumbersome.
trying to understand if the cause of the exception is a common case, or an user error. Do you have a minimal reproduce code?


allow broker name to be specified for remote brokers

The broker name should be allowed to be specified without erroring out, with a fallback of looking in the default location for the named broker.
This came up with the example programs.

The mechanics of this have been added,  probably needs some further work to really make full use of it however, but that is not something for the Beta


Check stride tooltip dispose

the stride profiler shows the readback still being rendered when tooltip is closed.

fixed in latest.


update FAQ's

[ ] How to claim funds for hours worked on project

I'd be interested in the methodology. I don't envy you the task but if you can come up with a fair and equitable system, which either dispenses with the need for self-reporting, or makes self-reporting verifiable then I will be extremely impressed. Best wishes with your self assignment :).

done


feat(*): add layers widgets

:warning: BREAKING CHANGES

No more layer options definition (REMOVED)
No more plugin API (REMOVED)

:fire: All layers become flutter widgets !

Add shared mapState widget
Improve rebuild layers
mapState API available on your custom widget with var mapState = MapStateInheritedWidget.of(context).mapState;
Update example with new strategy
Add simultation of user location

@johnpryan @synw
Can close :

https://github.com/johnpryan/flutter_map/issues/535
https://github.com/johnpryan/flutter_map/issues/459
https://github.com/johnpryan/flutter_map/issues/482

This seems very interesting, will be watching this!

Hi @ibrierley
Moving your plugin to this new logic can take much time ?
https://github.com/ibrierley/flutter_map_dragmarker

This should do it I think...
https://github.com/ibrierley/flutter_map_dragmarker/blob/master/lib/dragmarker_widget_layer.dart
There's 2 files in there, dragmarker.dart for the old plugin format, and dragmarker_widget_layer.dart for the referenced one here.
It would be good to hear whether this format will likely become the new standard, as I'll convert my tile layer code as well to it at some point if so.

I would use that

@lehno I'm rebasing on master ! Updated PR today :)

@johnpryan I updated file names on my PR, that's why the build failed

First of all - I love using Widgets instead of declarative options for the layers. Great job.
I think MapStateInheritedWidget is a mouthful and it can be moved to MapState class itself, so you can do MapState.of(context) and get the state instance. Because of that this static method should directly lookup the inherited widget, then return the mapState instead of the widget itself:
My suggestion:
class MapState {
  ...
  static MapState of(BuildContext context, {bool nullOk = false}) {
    assert(context != null);
    assert(nullOk != null);
    final widget = context.dependOnInheritedWidgetOfExactType<MapStateInheritedWidget>();
    if (nullOk || widget != null) {
      return widget?.mapState;
    }
    throw FlutterError('MapState.of() called with a context that does not contain a FlutterMap.');
  }
}

Not necessary, but given this InheritedWidget won't be useful by itself it can become a hidden widget - _MapStateInheritedWidget.
Second suggestion - to get this to be even considered to be merged with flutter_map there should be a way for the two approaches to coexist (at least initially):

layers should remain a list of declarative options;
introduce children to the FlutterMap which can use the widgets;
ensure layers or children is null - less complexity is better;
if the layers are present and children are null - then create the children automatically;
I think plugins can only work with layers, but am not 100% sure.

Thanks @avioli !
I'll change my PR to take care about your return. 🔥

Any update on this PR?
The proposed approach to work with widget is way more efficient and easier to use

@Sly2024 I need to finish my last update
Build pipeline is blocked because I've updated file names !


env and docker-compose.yml

I've been using laradock for a long time, but I don't understand how the configuration in env affects docker-comopse.yml.
How env and docker-compose.yml interact.

Read this https://docs.docker.com/compose/environment-variables/

You can set default values for environment variables using a .env file, which Compose automatically looks for in project directory (parent folder of your Compose file). Values set in the shell environment override those set in the .env file.

@duchymor Think you!


Method that returns latest data version

Given we've split code and data, it's not not obvious what you should download for a release
We can read the latest releases easily via REST: https://api.github.com/repos/SACGF/cdot/releases
We could then look for "data" release that is most recent for our major version

See methods in cdot.data_release


Responses not completing

Describe the bug
Getting a bug response "This message didnt complete its response" with continued loading.
Link to the Bolt URL that caused the error
https://bolt.new/~/sb1-mcrppf
Steps to reproduce
Input a prompt
Expected behavior
Complete tasks laid out in message response.
Screen Recording / Screenshot
No response
Platform
Browser name = Chrome
Full version = <IP_ADDRESS>
Major version = 131
navigator.appName = Netscape
navigator.userAgent = Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36
performance.memory = {
  "totalJSHeapSize": 162084997,
  "usedJSHeapSize": 148004973,
  "jsHeapSizeLimit":<PHONE_NUMBER>
}
Username = DervinEvolve
Chat ID = 38e21156ef6d

Additional context
The prompt output isnt completing its response, happened three times straight.

Appreciate the feedback! This is a known issue that is being tracked here: #1073.

same issue.

happening again and again today.

Same. I'm burning tokens, but not getting very far.


Resolving #2285 UI: Fixed renderer stats [manual reset].

UI stats: Fixed number of DrawCalls in stats panel [when H is pressed].
Problem: Cause of Post-processing renderer was rendering frame with one draw call and 'reseting' internal stats info.
Fix: Fixed by manually reseting renderer info before each frame render.

ps: There was missing skeleton update for head part of the character [and without this manual update it has issues].

This seems to be working fine. Previously, There's was only one draw call being shown in stats panel. Now its being continuously updated.

ps: There was missing skeleton update for head part of the character [and without this manual update it has issues].

This should be another PR.

Looks like this PR has been abandoned. If there is progress, please re-open.

There was no progress cause I was waiting for your reply.
In any case, I removed the fix for the missing head in the mirror in case of first-person mode.
Will create for this second PR as you requested.
As for now this PR fixes the draw calls number,
but brings the issue like this

Which was fixed by updating skeleton in the useBeforeRender function.

Ok if this breaks the functionality then we can't ship it.

Updated the Mirror app with renderer.info.render.frame ++
To ask the renderer to update skeleton.
Removed extra skeleton update in useAfterRender.
So now it's more performance optimized.
And all issues are resolved.

No correct solution could be found by the author in THREE.js.
It needs a THREE.js expert.


DRAFT:Changing meta-package deps. to major version ranges to avoid collisions

Q: Does this change make sense? ..probably needs some invoke running to get the poetry.lock up dated..?

We should be able to internally work inside semver..?
Also updating the authors for the package

It's missing the poetry lock command to update poetry deps according to the new range.
I'm not sure. The downside here (especially with the rcc caches) is:

User installs robo==1.2.5 and gets a set of dependencies
We release a new robocorp-log bugfix/feature release (no breaking changes)
robo is not released since it already covers that version given the current range

Result: user never gets the new robocorp-log bugfix because rcc caches are always bound to the versions used when robo==1.2.5 was released (unless he manually pins robocorp-log, which kind of defeats the purpose of the robo meta-package).

Result: user never gets the new robocorp-log bugfix because rcc caches are always bound to the versions used when robo==1.2.5 was released (unless he manually pins robocorp-log, which kind of defeats the purpose of the robo meta-package).

True, this is the problem with the meta-packages...
Basically whenever we update a sub-package, we really should bump up the meta-package version as well.
With versions locked to specifics like now using the meta-package basically prevents us from using any other library that requires different versions.. or we need to keep all the sub-packages and the meta-package aligned with the packages that are not in the meta-package.

Well, if other libraries don't pin specific internal versions it shouldn't be a problem in general (i.e.: having just major versions is a problem for the meta-package, but it's not a problem for other packages which depend on the internal versions).

I was thinking a bit more and I think that this is reasonable (then at new bugfix versions we can bump the minors here and do a new release of the meta package).
As a note, the robo/meta/tasks.py (used in invoke) has some utilities to deal with those that probably should be updated to deal with that syntax (i.e.: inv update may need to be updated to deal with the ^ for versions now).

Done in other branches


Making middleware pattern matching different health checks URIs

With pattern containing middleware in our company we have problem that your defined health check '/health' is not matched. This small change in pattern should make all of the URIs work.

What is the problem you are attempting to fix with this pull request? (I don't understand the necessity of this change - please show a worked example, preferably as a test that fails with my existing code, but works with your changes).

@ianheggie with this new pattern you've introduced 'middleware' word in URI which is mandatory. IMHO this is not the best idea as you expose the underneath implementation in URI (if I use controller or middleware it should be transparent). With this 'middleware' word, existing checks in our company stopped to work as we have just simple '/health' URI - no 'middleware' word inside it. I've liked that you changed this pattern to be very precise and with the small update I propose this should work also for existing  checks. I've tried to fix the tests.

The alternative is to have middleware as a different uri, which would be cleaner. There definitely needs to be some differentiator as using middleware disables the full stack test. I would be happy with a config.url (default 'health_check' and config.middleware_uri (default 'health_check_middleware') and you reconfigure the middleware uri as appropriate.

@ianheggie may I suggest another approach: https://github.com/ianheggie/health_check/pull/52/
It catches exceptions that @filiphaftek wanted but is using full rails stack to perform all checks.
Thus no need to separate endpoint is needed.

lowang - your suggestion ( #52 ) has merit for other reasons, but conflicts with the original intent of adding middleware (to allow a success response when the later part of the stack is not working (eg because of DB connection issue)).

I am going a slightly different direction - which I believe will satisfy what filiphaftek wants - extract from README:
=== Installing As Middleware
Install health_check as middleware if you want to sometimes ignore exceptions from later parts of the Rails middleware stack,
eg DB connection errors from QueryCache. The "middleware" check will fail if you have not installed health_check as middleware.
To install health_check as middleware add the following line to the config/application.rb:
config.middleware.insert_after "Rails::Rack::Logger", HealthCheck::MiddlewareHealthcheck
Note: health_check is installed as a full rails engine even if it has been installed as middleware. This is so the
remaining checks continue to run through the complete rails stack.
You can also adjust what checks are run from middleware, eg if you want to exclude the checking of the database etc, then set
config.middleware_checks = ['middleware', 'standard', 'custom']
config.standard_checks = ['middleware', 'custom']
Middleware checks are run first, and then full stack checks.

I have implemented a slightly different approach - adjust the list of checks to be done in middleware (eg in your case, add 'standard') and adjust the standard check to make sure you only run the checks you want to from middleware. Thanks for the input (The delay was in updating the tests and making middleware handle the enhancements already in the full stack test).


fix(ldap/create): create mad dir fail while update_or_create_sync_tasks

#777
原因: 首次创建目录的时候, 目录配置还没被初始化, 此时config_provider是拿不到任何东西的; 默认是None

request failed, please check api log of bk-user! Traceback (most recent call last):
  File "/usr/local/lib/python3.6/site-packages/rest_framework/views.py", line 506, in dispatch
    response = handler(request, *args, **kwargs)
  File "/app/bkuser_core/api/web/category/views.py", line 166, in post
    extra_values={"request": request},
  File "/usr/local/lib/python3.6/site-packages/django/dispatch/dispatcher.py", line 182, in send
    for receiver in self._live_receivers(sender)
  File "/usr/local/lib/python3.6/site-packages/django/dispatch/dispatcher.py", line 182, in <listcomp>
    for receiver in self._live_receivers(sender)
  File "/app/bkuser_core/categories/plugins/ldap/handlers.py", line 100, in update_sync_tasks
    update_or_create_sync_tasks(instance, operator)
  File "/app/bkuser_core/categories/plugins/ldap/handlers.py", line 51, in update_or_create_sync_tasks
    elif cycle_value < min_sync_period:
TypeError: '<' not supported between instances of 'int' and 'NoneType'


Is there a way to get the current dragged element?

Hi!
I would like to get the sourceModel and the sourceIndex of the current element being dragged but on the drag start action. There is a dropModel Observable which has these values but it is fired on drop event. Is there any way to get them on drag event?
I noticed the removeModel which provides these values but even if the element is being removed from the list on dragStart, this event is not fired. It gets fired when a element is spilled out from a list.
Can I achieve this in some way or maybe a change to be implemented to fire some event with these values on the drag start? It would be extremely useful!
Thank you a lot!!

https://github.com/bevacqua/dragula#drakeon-events
On drag


Item size- sum of attachment and email body

Size of emails will be - sum of - size of attachment and size of email body
In case of contacts and events, since mostly everything is data we will check the size as - total serialised bytes
Does this PR need a docs update or release note?

[ ] :white_check_mark: Yes, it's included
[ ] :clock1: Yes, but in a later PR
[x] :no_entry: No

Type of change

[ ] :bug: Bugfix

Issue(s)

#

Test Plan

[ ] :muscle: Manual
[ ] :zap: Unit test
[ ] :green_heart: E2E

I am not merging it yet to keep the discussion on comments going.


Example of using attribute store

This page would be much more helpful if it included an example of using a SQL Server attribute store.

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

ID: 54d73e9d-e08d-9184-e357-65b9f5a19bc1
Version Independent ID: 8c60d2ba-8fe4-cabf-0dda-72dbf58f1b73
Content: Add an Attribute Store
Content Source: WindowsServerDocs/identity/ad-fs/operations/Add-an-Attribute-Store.md
Service: unspecified
Product: windows-server-threshold
GitHub Login: @billmath
Microsoft Alias: billmath

Exactly, this article is close to 0 regarding usefulness, nothing in this page helps in any way to add an Attribute Store in AD FS !

There's an example at
Active Directory Federation Services – SQL Attribute Store | Journey Of The Geek
https://journeyofthegeek.com/2017/05/28/active-directory-federation-services-sql-attribute-store/

the documentation keeps saying "SQL", without providing any more information.
From what I can tell, it means "OLE DB provider".  Adding this one piece of information would be MASSIVELY helpful!
Also suggest adding an optional (but HIGHLY RECOMMENDED step) test connectivity using the steps at
https://blogs.technet.microsoft.com/michaelgriswold/2014/01/06/the-easy-way-to-test-sql-connectivity/

not "OLE DB provider", but "OLE DB connection using any OLE DB provider"

ignore my comments about OLE DB provider.  Add a link to...
Attribute stores that are supported by AD FS
https://docs.microsoft.com/en-us/windows-server/identity/ad-fs/technical-reference/the-role-of-attribute-stores#attribute-stores-that-are-supported-by-ad-fs
https://docs.microsoft.com/en-us/windows-server/identity/ad-fs/technical-reference/the-role-of-attribute-stores

Why was this closed? My last suggestion would have improved this article.
Change...
Data from the attribute stores is then projected as claims.
You can use the following procedure to add an attribute store to the Federation Service.
To...
Data from the attribute stores is then projected as claims.
Attribute stores that are supported by AD FS
https://docs.microsoft.com/en-us/windows-server/identity/ad-fs/technical-reference/the-role-of-attribute-stores#attribute-stores-that-are-supported-by-ad-fs
You can use the following procedure to add an attribute store to the Federation Service.


compiler compat

https://github.com/tyfkda/xcc/blob/33a7f10290e2a16111e2f367aad05b62243544e5/src/cc/backend/ssa.c#L17
clang 19.1.1 apparently needs "static inline" here instead.

@pmp-p Thank you to report the error. I've fixed it.


THRIFT-4578 Move TAsyncProtocolProcessor into main thrift library

Updated CMake and automake files for C++.

The build failures are unrelated to the change.


Flair-TDM Model setup?

Hi! Thanks for this great work!
I am trying to replicate some of your results for my own publication. Do you still have the code for the Flair model?
As you know, there are many ways to configure the model embeddings. I'm just curious what your setup was.
Thanks!

Hi @logan-markewich, for the embeddings, the combination of glove + news-forward + news-backward should give you a decent performance. Other parameters are the same as your setup except that I use 150 for max_epochs.
-- Yufang

I will give that a shot, thanks so much!
And thanks for getting back to me, even though the project is a little older 🙏🏻


Docs: Improve documentation with regards to running tests locally

This PR aims to add the following:

Add a github actions test workflow status badge (see image on of README.md).
Document how to run the frontend and backend tests locally.
Separate the frontend and backend tests in the github actions workflow so that it will be easier to see which one fails (see image below or here).
Run test workflow on both push and pull_request events.

Btw, I'm thinking about the idea of not using docker run but docker exec to run the tests locally as docker run creates a new container instance. This is now clogging up my container list in the GUI (see screenshot). What would you think of that idea?

As the name of the container is not the same across all users, I prefer docker-compose run over docker exec (otherwise the instruction would become: "run docker ps, find name of container, then run docker exec {container_name}, a bit more wordy and nothing users can copy-paste). I now attach the --rm flag across all documentation in the wiki, which makes sure the containers will be removed after the tests finish.
As with #620, I'd also request that documentation on how to run the tests be moved to the wiki, so as not to clutter the README.

As the name of the container is not the same across all users, I prefer docker-compose run over docker exec (otherwise the instruction would become: "run docker ps, find name of container, then run docker exec {container_name}, a bit more wordy and nothing users can copy-paste). I now attach the --rm flag across all documentation in the wiki, which makes sure the containers will be removed after the tests finish.
As with #620, I'd also request that documentation on how to run the tests be moved to the wiki, so as not to clutter the README.

Ah yes, with the --rm it wouldn't clog up my list of containers. By the way, you mention here (and in #620) that "the name of the container is not the same across all users". Has this been an issue you are running into or was this a conscious decision? I believe (from the top of my head) that the container name is configurable in the docker-compose.yml file.

Ah, I never realized you could set the container name. So no, no conscious decision. But what would happen if somebody spins up multiple containers? You would then still get server_1, server_2 and so on? I think that last bit is what Docker attaches nonetheless, and I noticed that it can differ whether the index is slapped on with hyphen or underscore. Perhaps there's a setting for that, too.


[v5] Pass error to parent for errorListener

This was recently reworked as part of https://github.com/statelyai/xstate/pull/4145 . I also included tests cases similar to what we have here in https://github.com/statelyai/xstate/pull/4517


[WIP] docs/spec: catalog V2 API specification proposal

This contains a proposal for a catalog API, provided access to the internal
contents of a registry instance. The API endpoint is prefixed with an
underscore, which is illegal in images names, to prevent collisions with
repositories names. To avoid issues with large result sets, a paginated version
of the API is proposed. We make an addition to the tags API to support
pagination to ensure the specification is consistent.
Closes #441, #382.
Signed-off-by: Stephen J Day<EMAIL_ADDRESS>cc @dmp42 @dmcgowan @ncdc @pdevine

On Mon, Jun 01, 2015 at 07:15:23PM -0700, Stephen Day wrote:

To avoid issues with large result sets, a paginated version of the
API is proposed.

To reduce load on the server from unlimited requests on large sets, it
might make sense to allow the server to set a default and maximum
value for n.  That means clients will have to support pagination,
but it allows to server to put an upper bound on the amount of work
required to fill a single request.
You likely also want to return an envelope or header parameter with a
count for the full result, so paginators can say “page $i of $count”
in their results (or know what fraction they've already worked
through).  That count may change in subsequent calls, but that's ok.
The decision to use ‘last’ instead of an integer offset (like
Elasticsearch and Redis, see [1,2]) means that the task of tracking a
consistent location in the face of mutating backing data is up to the
server (e.g., you need to figure out the appropriate offset for ‘last’
in your results, even if the key referenced by ‘last’ no longer
exists).  Personally, I'm in favor of integer offsets and leaving the
robustness in the face of mutating lists up to the client, but without
clear external constraints it's probably just personal preference.

To reduce load on the server from unlimited requests on large sets, it
might make sense to allow the server to set a default and maximum
value for n.  That means clients will have to support pagination,
but it allows to server to put an upper bound on the amount of work
required to fill a single request.

This specification leaves that to the server and client. A server can always refuse a client without support. Please note that catalog listing will always be hidden by admin privileges (or maybe a listing scope), since it may expose registry wide data.

You likely also want to return an envelope or header parameter with a
count for the full result, so paginators can say “page $i of $count”
in their results (or know what fraction they've already worked
through).  That count may change in subsequent calls, but that's ok.

How would one implement this efficiently with the current backend layout and storage driver system? Perhaps, this is something we specify and don't implement.

The decision to use ‘last’ instead of an integer offset (like
Elasticsearch and Redis, see [1,2]) means that the task of tracking a
consistent location in the face of mutating backing data is up to the
server (e.g., you need to figure out the appropriate offset for ‘last’
in your results, even if the key referenced by ‘last’ no longer
exists).  Personally, I'm in favor of integer offsets and leaving the
robustness in the face of mutating lists up to the client, but without
clear external constraints it's probably just personal preference.

The issue with an integer index is that it requires the server assign rank to the results. In the face of a changing data set, rank is always changing where as a "pivot" is a property of the data. Forcing this problem on the client just moves it some where it cannot be addressed. The registry may not even have a full few of its dataset to calculate the rank properly.

Looks good. +1

On Tue, Jun 02, 2015 at 04:00:38PM -0700, Stephen Day wrote:

To reduce load on the server from unlimited requests on large
sets, it might make sense to allow the server to set a default and
maximum value for n.  That means clients will have to support
pagination, but it allows to server to put an upper bound on the
amount of work required to fill a single request.

This specification leaves that to the server and client. A server
can always refuse a client without support.

If server implementations can optionally not support the unlimited
endpoint (and still claim to satisfy the spec) and can also enforce
limits on n (and still claim to satisfy the spec), it's probably worth
mentioning that explicitly in the spec.  From reading it now, I'd
consider a server that 400ed my large-n request to be nonconformant.

Please note that catalog listing will always be hidden by admin
privileges (or maybe a listing scope), since it may expose registry
wide data.

Ah, good point.  So I guess relying on well-behaved clients to not
abuse expensive, unlimited calls isn't that unreasonable.

You likely also want to return an envelope or header parameter
with a count for the full result, so paginators can say “page $i
of $count” in their results (or know what fraction they've already
worked through).  That count may change in subsequent calls, but
that's ok.

How would one implement this efficiently with the current backend
layout and storage driver system? Perhaps, this is something we
specify and don't implement.

The current filesystem driver already has a len(fileNames) call 1,
but yeah, that would be harder with S3.  I feel like this is a common
feature of paginated results though, so we should either figure out
how to support it with drivers like S3 (I've suggested separating
transactional mutable storage from content-addressable storage before,
docker/docker-registry#704), or explain why our clients won't need
this common feature.

The decision to use ‘last’ instead of an integer offset (like
Elasticsearch and Redis, see [1,2]) means that the task of
tracking a consistent location in the face of mutating backing
data is up to the server (e.g., you need to figure out the
appropriate offset for ‘last’ in your results, even if the key
referenced by ‘last’ no longer exists).  Personally, I'm in favor
of integer offsets and leaving the robustness in the face of
mutating lists up to the client, but without clear external
constraints it's probably just personal preference.

The issue with an integer index is that it requires the server
assign rank to the results.

Yeah.  I guess the issue is how you expect storage backends to scale
internally.  If they shard out lexically, then it's easier for them to
lookup an offset using a ‘last’ entry.  If they shard out into counted
bins, then it's easier for them to lookup by an interger offset.
Lexical sharding works pretty well for cryptographic hashes, but some
of our key sets (tags and image names) are user-supplied text, so I
expect storage backends will have to figure out a non-lexical sharding
scheme anyway, and attaching ancestor counts to entries in that tree
doesn't seem to hard.  Once they have ancestor-counting sharding for
the unhashed keys, I think they might as well use the same scheme for
all keysets.  We're unlikely to extend the storage API to allow
flagging of crypto-hashed keysets, so the storage driver will probably
have to use the same scheme for all keysets.

If server implementations can optionally not support the unlimited
endpoint (and still claim to satisfy the spec) and can also enforce
limits on n (and still claim to satisfy the spec), it's probably worth
mentioning that explicitly in the spec.  From reading it now, I'd
consider a server that 400ed my large-n request to be nonconformant.

I added this to cover that. This endpoint can be protected by access control or just return an empty result.

On Wed, Jun 03, 2015 at 06:27:47PM -0700, Stephen Day wrote:

If server implementations can optionally not support the unlimited
endpoint (and still claim to satisfy the spec) and can also
enforce limits on n (and still claim to satisfy the spec), it's
probably worth mentioning that explicitly in the spec.  From
reading it now, I'd consider a server that 400ed my large-n
request to be nonconformant.

I added
this
to cover that. This endpoint can be protected by access control or
just return an empty result.

That helps, but it only mentions authorization an upstream concerns.
For those cases, there's no reason for a client to perform a follow-up
request.  I'd like to see it also mention the case where a client asks
for $n results, but we only return $m < $n for efficiency reasons.  In
that case, the client is welcome to perform a follow-up request with
an increased last/offset.

@wking I'm not sure that belongs in the specification. Please provide updated language for that part if you believe it should be changed. Perhaps, we can have an option to redirect to the paginated version but that is not really the same resource.
No matter what, this is an inefficient endpoint. Most applications would be better served by accessing the storage backend directly, but no one seems willing to do this. It's unfortunate, since we took measures to make the layout very approachable. Clearly, this was a poor trade off.

On Thu, Jun 04, 2015 at 11:30:15AM -0700, Stephen Day wrote:

@wking I'm not sure that belongs in the specification. Please
provide updated language for that part if you believe it should be
changed. Perhaps, we can have an option to redirect to the paginated
version but that is not really the same resource.

Yeah, I guess I'd just only have the paginated version in the spec.
Since you pointed out the admin scoping 1, having a potentially
expensive API isn't really a big deal.  If both the registry and
admin-client devs think the registry is up to serving unpaginated
results, then I guess they're welcome to do that.

No matter what, this is an inefficient endpoint. Most applications
would be better served by accessing the storage backend directly,
but no one seems willing to do this.

It seems worthwile to have a way to write backend-agnostic admin
tooling, and let folks go directly to the backend if they have
performance issues via the backend-agnostic API.  So I think having
both options available is a good thing.
Of course, you could also get the backend-agnostic API by making the
backends independent processes that listen on their own socket.  Then
both the registry and admin tools could talk to the backend directly
via the same storage-driver API, instead of proxying the calls through
the registry here:
(registry-client) →{registry API}→ (registry) →{storage-API}↘
(admin-client) →{storage API}→ (stand-alone-storage-driver-process) → (storage)
But for storage-drivers built on sufficiently atomic drivers/storage,
you can probably just run have parallel processes with in-process
drivers:
(registry-client) →{registry API}→ (registry →{storage API}→ storage-driver) ↘
(admin-client) →{storage API}→ (stand-alone-storage-driver-process) → (storage)
with both storage-drivers running on the same backing storage.

Label/Metadata inspection
(formerly #600)
This proposal adds metadata inspection into the catalog API.
While labels provide the most specific information, it might also be viable to inspect other parts of image metadata and manifest itself.
The functionality could be modelled after PROPFIND in WebDAV aka RFC4918 with the exception of using JSON documents instead of XML.
The endpoint could be like:
/v2/_catalog/metadata?repo=my/repo
The body of the request would contain specification which metadata to return, as well as the pagination information specified above.
The metadata specification could possible be in any of the following formats:

MongoDB query
jq
JPath

The catalogue would return one record per each tag in the repository:
Request: (jq examplet)
.[] {version: .labels.acme.version, options: .labels.acme.provides, id: .v1Compatibility.[0].Id}
Response:
{
    "tag": "latest",
    "digest": "sha256:...",
    "result": {
       "version": "1.0.0-1",
       "options": "journald,Xsocket",
       "id": "654d2ca2aaa2f1244ea40d8290883c5964a7f971f778e230414b7830e3829867"
    }
}

Since the filtering could possibly end up with large amounts of data, I think that it would be sane to limit the response size to, say, 8kb per record (or some empiric ratio between average manifest size).
What do you think? @stevvooe @ncdc

@shaded-enmity This is completely outside of the scope and context of this proposal. As stated in #600, the registry provides access to data. It has no facilities for indexing and collating data except under its primary key (tag, name, digest, etc.). Adding such functionality is a massive departure from those design goals.
@ncdc

Closed in favor of #653.


Gsmartcontrol 0.8.7 -> 1.1.3 version bump needed, current package broken.

Issue description
True issue: gsmartcontrol package needs version bump. Current version in 18.03 is from 2012 and does not support policykit/pkexec, hence failing to launch if none of the old gui "sudo" methods are installed.

Original header for the record: "Gsmartcontrol must implement pkexec method instead, currently requires legacy packages."
Original issue for the record:
Currently gsmartcontrol is installed with a desktop file,  that launches it with user priviledges.
However root access for smartcontrol (smartmontools) to access hardware readouts like SMART table.
The desktop file in (/run/current-system/sw/share/applications/gsmartcontrol.desktop) calls the "/nix/store/0bk3hs34mwa8ss1q8w31cn2a6q5zj999-gsmartcontrol-0.8.7/bin/gsmartcontrol-root", which is a script that tries to guess the graphical "sudo" method.
However, the correct way is to invoke "pkexec" as its present by default and is current preferred way(?). Thus this application will need policykit custom action  and either gsmartcontrol-root should be modified with additional pkexec method (i think its a more flexible way), or completely replaced with pkexec method.
There is third way - to add requirement for gui-based sudo as dependency.
Steps to reproduce
$ nix-env -i gsmartcontrol
launch gsmartcontrol from gui menu.
Technical details

system: "x86_64-linux"
host os: Linux 4.14.27, NixOS, 18.03pre131327.0e7c9b32817 (Impala)
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.0
channels(root): "nixos-18.03pre131327.0e7c9b32817, nixos17.09-17.09.3159.c665fcca9e7"
nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs

Polkit should be supported with GSmartControl 1.1.0, look at https://gsmartcontrol.sourceforge.io/home/

@jtojnar Oh, wow! The current package is from 2012!

@jtojnar Could I request backport of your fix to 18.03, when you have time, please? Its still 0.8.7 as of now.

Done.


[Packaging] Separate builds for trusty/xenial on TravisCI

I can't quite do the PPA uploads yet (blocked by https://github.com/travis-ci/travis.rb/issues/448). But I'd still like to merge this to double-check my Travis envvar logic.

Looks good:

Uploading to "dev" PPA ...
https://travis-ci.org/NVIDIA/DIGITS/jobs/171521551


[Event Change] Codeunit::"Create Pick" - Function SetWhseShipment - OnAfterSetWhseShipment

We like to request the following Event:
Object: Codeunit::"Create Pick"
Function: SetWhseShipment
Publisher Event: OnAfterSetWhseShipment
Reason: add an extra Parameter
Where is the event placed:
Event Code:
[IntegrationEvent(false, false)]
local procedure OnAfterSetWhseShipment(var WarehouseShipmentLine: Record "Warehouse Shipment Line"; TempNo2: Integer; ShippingAgentCode2: Code[10]; ShippingAgentServiceCode2: Code[10]; ShipmentMethodCode2: Code[10])
begin
end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.


Pass the JSON as value inside the template

Hey guys,
is there any way to insert some pre-generated JSON?
I.e. I have a JSON like the following:
{
  "id": 137290203,
  "name": "Hello",
  "items": [{
    "id": 4783934,
    "url": "http://some-domain.com/some/resource"
  }, ... here are more items maybe]
}

Is there any way to write it like this?
{
  "id": 137290203,
  "name": "Hello",
  "items": {{items}}
}

And have the items pregenerated using custom helpers?

It depends on where your pre-generated JSON comes from. I'm going to assume it's available as a native JS object for this example.
Imagine this is your template:
{
  "id": 137290203,
  "name": "Hello",
  "items": {{{items}}}
}

(Note the triple brackets around {{{items}}}, this prevents Handlebars from HTML escaping characters, especially the " character which will become ")
Now the code:
var items = [
  { "id": 4783934, "url": "http://some-domain.com/some/resource" },
  { "id": 1234567, "url": "http://other-domain.com/other/resource" }
];

var customMockdata = {
  items: JSON.stringify(items)
};

var output = dummyjson.parse(template, { mockdata: customMockdata });

We're using custom mockdata, which is described in more detail here https://github.com/webroo/dummy-json#using-other-data
Handlebars only deals with strings (and casts objects that are not) which is why we have to convert the items JS object using JSON.stringify. If we didn't do this Handlebars would just generate [Object object].
The only downside to this approach is that the formatting of the output doesn't look so nice, eg:
{
  "id": 137290203,
  "name": "Hello",
  "items": [{"id":4783934,"url":"http://some-domain.com/some/resource"},{"id":1234567,"url":"http://other-domain.com/other/resource"}]
}

An alternative is to keep the template and items in separate files, then load both at runtime, like so:
var template = fs.readFileSync('./template.hbs', {encoding: 'utf8'});
var items = fs.readFileSync('./items.hbs', {encoding: 'utf8'});

var customMockdata = {
  items: items,
};

var output = dummyjson.parse(template, { mockdata: customMockdata });

Again the formatting/whitespace might not look so nice, but at least it will be valid JSON.


Search result is blank when there are more than 1 filter label.

Is this a bug?

This isn't a bug, simply there isn't any manga created by both saigado and sasamori tomoe, if you search on NHentai it will also say that there aren't results


Packit: Get the current Fedora Rawhide specfile

Using the fork is not needed anymore,
since Rawhide was updated to 2.5.0 and no longer has patches.

Codecov Report

Merging #1145 (1ba608b) into master (9764cc7) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master    #1145   +/-   ##
=======================================
  Coverage   97.28%   97.28%
=======================================
  Files          67       67
  Lines        4235     4235
=======================================
  Hits         4120     4120
  Misses        115      115

Impacted Files
Coverage Δ

httpie/__init__.py
100.00% <100.00%> (ø)

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 4eaa4d6...1ba608b. Read the comment docs.

The rawhide build failure is transient.

/packit build

Oh OK, so let'se merge it now :+1:

Does that happen often? If so, we could revert https://github.com/httpie/httpie/pull/1119

Thank you @hroncok :pie:

No, it is quite reliable actually.


comparison to trpc

Especially for the server, we should have a comparison that shows the strengths and drawbacks of using feTS instead of tRPC.

@n1ru4l  For me, it is a great way to validate request and response, but rewrite whole thing to native fetch at the end to reduce the bundle size.
Basically for me it is only dev dependency. I have met some issues with building gatsby.js project with feTS, but rewriting it to fetch fixes issues.

Wanted to +1 this. Took me a long time to find out about feTS. I was looking for a way to make OpenAPI compliant APIs and looked into hono with openapi middleware, trpc-openapi etc, but feTS is the most lightweight, integrated solution I've found so far :)  The only drawback is using TypeBox instead of Zod but i understand why it is necessary!


Start collecting information about Lines of Code in samples

During evaluation, compute the following features:

how many classes each sample has,
how many LoC each of the classes has,
total # LoC in the sample

Total # LoC in the sample is to be collected with postprocessing.


Learn: Need of Anchors on specific pages that has F1 connection from SuperOffice UI.

After merge of a lot of pages, there is a need of new anchors to make the F1 functionality in SuperOffice to work smoothly.
Chapter where a new anchor is needed:

#
Line User/Admin
Dispatcher url
Need anchor

69
u69
search-options/selection/learn/update/add-remove-members-static.html

70
u70
search-options/selection/learn/update/add-remove-members-static.html#remove-members-using-search-criteria
Yes

74
u74
search-options/selection/learn/howto/export.html#export-to-file
Yes

83
u83
reports/learn/labels/index.html#add-label-format
Yes

111
u111
search-options/learn/find-screen.html#example-1-search-for-profitable-customers
Yes

112
u112
search-options/learn/find-screen.html#example-4-search-for-projects-you-have-participated-in-during-the-last-year
Yes

115
u115
search-options/learn/find-screen.html#example-3-search-for-sold-sales
Yes

119
u119
search-options/learn/find-screen.html#example-2-search-for-customers-in-denmark-who-you-are-responsible-for
Yes

120
u120
search-options/learn/find-screen.html#example-4-search-for-projects-you-have-participated-in-during-the-last-year
Yes

123
u123
search-options/learn/find-screen.html#example-3-search-for-sold-sales
Yes

126
u126
search-options/learn/find-screen.html#work-with-search-results
Yes

153
u153
learn/section-tabs/index.html#sort-lists
Yes

159
u159
learn/section-tabs/index.html#sort-lists
Yes

167
u167
quote/learn/create.html#is-the-select-erp-connection-dialog-displayed
Yes

199
u199
marketing/learn/editor.html#editor-old
Yes

201
u201
marketing/learn/editor.html#editor-old
Yes

209
u209
marketing/learn/editor.html#editor-old
Yes

217
u217
marketing/learn/editor.html#editor-old
Yes

268
a6
admin/preferences/learn/update-preferences.html#edit-preference-setting
Yes

319
a57
admin/user-management/learn/screen/index.html#other-users-onsite
Yes

320
a58
admin/user-management/learn/screen/index.html#our-companies
Yes

360
a98
admin/user-management/learn/screen/index.html#the-associate-list
Yes

The list in one line:
search-options/selection/learn/update/add-remove-members-static.html
search-options/selection/learn/update/add-remove-members-static.html#remove-members-using-search-criteria
search-options/selection/learn/howto/export.html#export-to-file
reports/learn/labels/index.html#add-label-format
search-options/learn/find-screen.html#example-1-search-for-profitable-customers
search-options/learn/find-screen.html#example-4-search-for-projects-you-have-participated-in-during-the-last-year
search-options/learn/find-screen.html#example-3-search-for-sold-sales
search-options/learn/find-screen.html#example-2-search-for-customers-in-denmark-who-you-are-responsible-for
search-options/learn/find-screen.html#example-4-search-for-projects-you-have-participated-in-during-the-last-year
search-options/learn/find-screen.html#example-3-search-for-sold-sales
search-options/learn/find-screen.html#work-with-search-results
learn/section-tabs/index.html#sort-lists
learn/section-tabs/index.html#sort-lists
quote/learn/create.html#is-the-select-erp-connection-dialog-displayed
marketing/learn/editor.html#editor-old
marketing/learn/editor.html#editor-old
marketing/learn/editor.html#editor-old
marketing/learn/editor.html#editor-old
admin/preferences/learn/update-preferences.html#edit-preference-setting
admin/user-management/learn/screen/index.html#other-users-onsite
admin/user-management/learn/screen/index.html#our-companies
admin/user-management/learn/screen/index.html#the-associate-list

admin/preferences/learn/update-preferences.md #edit
admin/user-management/learn/screen/index.md #associates, #other-users, #our-companies
learn/section-tabs/index.md #sort
marketing/learn/editor.md #old
quote/learn/create.md #erp
reports/learn/labels/index.md #add-format
search-options/selection/learn/howto/export.md #to-file
search-options/selection/learn/update/add-remove-members-static.md #remove

Please use the existing anchors in find-screen.md: results, ex1, ex2, ex3, ex4, ex5
Added anchor to editor.md. However, that section is only 1 screenshot + 1 sentence linking to 10.1 help. Think the dispatcher should link directly to that page rather than ask a confused user to click two links.

@digitaldiina
As for the marketing and old editor:
Would it be possible to add anchor on this url?
https://docs.superoffice.com/en/marketing/learn/editor.html#two-different-editors
I think it's important that the user will get the correct help. By confusing them with the info about Drag&Drop editor, they might not scroll down to see the relevant info + the link to help.superoffice.com and the old editor help.

Yes, it's possible. But please clarify. Do you want to replace the anchor #old that sends them directly to the initially requested section, or do you want a second anchor in the same file? Linking to #two-different-editors if they should go to #old seems more confusing, but I might have misunderstood the use case.

There are 4 places in the UI (so-protocol) where they ask for a help url:

emarketing.www.spm.document.step3.oldeditor
emarketing.www.spm.email.step3.oldeditor
emarketing.www.spm.listTemplates.oldeditor
emarketing.www.spm.form.step3.oldeditor

As you can see, all these shows the Old editor in the UI.
For this we need a help to give them a good solution when the New editor is not what they need.
So, if you think it's better to anchor the chapter above, we can do that.
It's due to the comment you had, @digitaldiina , I asked yesterday about a different way to anchor this:
< Added anchor to editor.md. However, that section is only 1 screenshot + 1 sentence linking to 10.1 help. Think the dispatcher should link directly to that page rather than ask a confused user to click two links.
So maybe I misunderstood what you asked/said...?

My suggestion was that instead of linking to editor.md#old on docs, the dispatcher should link directly to the page on help.superoffice.docs (like we do for Service). Sorry if that wasn't clear.
If that is not technically possible, editor.md#old is the best (most precise) option.


skipUndeclared on react/prop-types doesn't skip components with undeclared propTypes

In https://github.com/yannickcr/eslint-plugin-react/blob/master/docs/rules/prop-types.md, it mentions a skipUndeclared attribute for the propTypes rule. However, there is no example of how to use it in the doc.
react/prop-types": [2, {customValidators: ["skipUndeclared"] }], does not seem to skip components with no declared propTypes. (Said component that is erroring is an ES6 style class MyComponent extends React.Component { type component. propTypes is mentioned nowhere in the file.)
"react/prop-types": [2, { skipUndeclared: true }], gives me Error: /Users/ktolva/Code/planweb/.eslintrc: 	Configuration for rule "react/prop-types" is invalid: 	Value "data["0"].skipUndeclared" has additional properties.
Is there a different syntax for skipUndeclared that I have failed to guess?

The second example is what I'd expect, per https://github.com/yannickcr/eslint-plugin-react/blob/master/lib/rules/prop-types.js#L50-L52
What version of eslint-plugin-react and elsint do you have installed?

Thanks for the quick response!
My eslint-plugin-react version is 5.2.2 and eslint version is 2.11.1.

Oh, I see. In that version of the docs (https://github.com/yannickcr/eslint-plugin-react/blob/v5.2.2/docs/rules/prop-types.md) there is no skipUndeclared option! I guess I better upgrade. :)

Yup, v5 is pretty old; we're on v7.4 now.


Fix error panels focusing on DS examples

What is the context of this PR?
This is to stop error panels focusing on page load in Design System examples
How to review

Check errors do focus on page load if DSExample isnt set
Check that DS pages with error panels on no longer focus on page load

 Issue #995: Any page with an Error Panel on focuses on that panel


Add proper "netgo" compiling, thanks to rsc ♥

See https://github.com/golang/go/issues/9369#issuecomment-69864440!

Tested locally. Works.

How do I check if it works?
If it's just about compiling, it works on my machine.

It should compile without warnings and should produce a working binary that is 100% statically compiled (ie, ldd bundles/$(cat VERSION)/docker-$(cat VERSION) produces not a dynamic executable)

Build succeeded on drone - LGTM

works locally LGTM

ugh test-integration doesn't like it, but everything else does :(
On Wed, Jan 14, 2015 at 8:43 AM, Alexander Morozov<EMAIL_ADDRESS>
wrote:

Build succeeded on drone - LGTM
—
Reply to this email directly or view it on GitHub
https://github.com/docker/docker/pull/10087#issuecomment-69946807.


Add java-devel as base layer for builder stages

Description
Images build successfully: https://github.com/stackabletech/docker-images/actions/runs/9065581172
Remove the java development tools from final images.
Some notes on the implications:

the openjdk-headless only installs a JRE
the openjdk-devel package is needed to build products from source (duh!) but also for log4shell checks
the openjdk-devel package brings in a lot of dependencies with known CVEs like (X11 libs)

Definition of Done Checklist

Not all of these items are applicable to all PRs, the author should update this template to only leave the boxes in that are relevant
Please make sure all these things are done and tick the boxes

- [x] Changes are OpenShift compatible
- [ ] All added packages (via microdnf or otherwise) have a comment on why they are added
- [x] Things not downloaded from Red Hat repositories should be mirrored in the Stackable repository and downloaded from there
- [x] All packages should have (if available) signatures/hashes verified
- [ ] Does your change affect an SBOM? Make sure to update all SBOMs
- [x] Add an entry to the CHANGELOG.md file
- [ ] Integration tests ran successfully

TIP: Running integration tests with a new product image
The image can be built and uploaded to the kind cluster with the following commands:
bake --product <product> --image-version <stackable-image-version>
kind load docker-image <image-tagged-with-the-major-version> --name=<name-of-your-test-cluster>

See the output of bake to retrieve the image tag for <image-tagged-with-the-major-version>.

To be honest I'm not really sure what I should think of this.

(+) It simplifies the development
(+) It should decrease the build time locally
(-) It increases the build time across the board in the CI (we currently already struggle with the few ARM runners)
(-) I think in the past @lfrancke told me to reduce the number of packages not only in the final but also in the builder image. Not sure if this is still the case though

Back in the days I would have brought it up in the Arch meeting, WDYT of throwing this on the Decisions board instead?

Thanks for giving this a try! To be honest I'm not really sure what I should think of this.

Yes, I'm not sure what to make of it either. But if we want to exclude devel packages from the final images and have no  duplication, it's the only way,
A big improvement in performance would be if we used published images of java-devel and java-base.

Back in the days I would have brought it up in the Arch meeting, WDYT of throwing this on the Decisions board instead?

ok

AFAIK we need java-xxx-openjdk-devel to build Java programs.
After we (together) fiddled around with java-xxx-openjdk-devel I think this actually LGTM

Only thing I can say is that build time vulnerabilities still have the potential for affecting the resulting artifact. So we will still need to deal with the devel CVEs in some way, but perhaps the scope is reduced?

Haven't reviewed the PR contents, but conceptually :+1:.

(-) I think in the past @lfrancke told me to reduce the number of packages not only in the final but also in the builder image. Not sure if this is still the case though

Don't think this changes much? Still the same build-time deps, fewer runtime deps is a win.

A big improvement in performance would be if we used published images of java-devel and java-base.

Really not keen on going back to "use whatever java-devel is published" (or worse, "use whatever java-devel you have cached locally"). It would be nice if Docker had a way to notice that our java-devel-to-be-built matches a prebuilt java-devel exactly (... like Nix), but that's not practical as long as Dockerfiles expect to be able to download anything they want from the internet.

Only thing I can say is that build time vulnerabilities still have the potential to affect the resulting artifact. So we will still need to deal with the devel CVEs in some way, but perhaps the scope is reduced?

Yeah, but there's a pretty huge difference between "build process could potentially have been backdoored if we knew about a discovered-far-in-the-future vulnerability" and "can be exploited by anyone until patched". Especially if the build is reproducible so that we (and others) can determine in the future whether or not such a build-time exploit actually happened (... not that we are atm, but a girl can dream right?).

We had a meeting (with 8 people) and there was no big discussion, no one objected


[Security - high] Spring4Shell zap alert

Risk: High
https://pass.local/data/publication?class.module.classLoader.DefaultAssertionStatus=nonsense
The application appears to be vulnerable to CVE-2022-22965 (otherwise known as Spring4Shell) - remote code execution (RCE) via data binding.
Upgrade Spring Framework to versions 5.3.18, 5.2.20, or newer.

From what I see in pass-core, I think this is a false positive.  pass-core using using springframework 5.3.23 which has the fix.  I will spend a bit more time investigating though to be sure.
https://spring.io/security/cve-2022-22965

Based on the prerequisites for the exploit, pass-core does not appear to be vulnerable to spring4shell.  See this link for the prerequisites and versions for the security vulnerability: https://github.com/advisories/GHSA-36p3-wjmg-h94x
pass-core dependency versions for the packages at risk:

org.springframework.boot:spring-boot-starter-web:2.7.5
org.springframework:spring-beans:5.3.23
org.springframework:spring-webmvc:5.3.23

All versions are greater than affected version.
pass-core does not have webflux deps.
Moreover, pass-core does not run in a tomcat container or as a war.  It runs as a spring boot jar with jetty.
Based on these points, I conclude pass-core is safe from the known spring4shell exploit.

@rpoet-jh
Agreed, pass-core does not meet the prerequisites.


Problems with emphasis inside code blocks.

I don't get my @-surrounded emphasis to work, instead it just writes the @thing@ to the pdf.
Same problem for html.
Same problem with both __ and ** use .
Here is a sample code block that doesn't work for me, the intent is to boldface the word typename, but instead it just outputs the @** and **@ sequences as is:
class MyClass {
    operator int() { return 0; }
    operator double() { return 1; }
};

auto conv = &MyClass::operator @**typename**@;

MyClass c;

int a = (c.*conv)();
double a = (c.*conv)();

Well you have to check the source code obviously.

I noted now that this only happens on one of my upcoming proposals, not the other. As this is rather strange, I attach the input and output file of the failing conversion for you to ponder over.
ost.md
ost.pdf

Hi @BengtGustafsson, this is due to the processing only being done on codeblocks with cpp as the language, rather than C++. Are you using cpp in the cases that work currently?

Thanks for this explanation. It seems I use C++ a lot so that's why then. Unfortunately I didn't see your reply before the paper deadline so now I removed all those annotations...


Fixing deployment_name conflict

Fixing conflict when working with multiple blueprints by given it a unique deployment_name.
Submission Checklist

[x] Have you installed and run this change against pre-commit? (pre-commit install)
[x] Are all tests passing? (make tests)
[ ] Have you written unit tests to cover this change?
[x] Is unit test coverage still above 80%?
[x] Have you updated all applicable documentation?
[x] Have you followed the guidelines in our Contributing document?

/gcbrun

Does that really work? I believe deployment name gets shortened to the first 8 characters for the slurm resources and this change only differs at the end of the deployment name. Did you deploy both simultaneously?

Did you test if this really work deploying the two at the same time? I believe deployment name gets shortened to the first 8 characters for the slurm resources and this change only differs at the end of the deployment name. Did you deploy both simultaneously?

You are right. I changed the name again in order to differ when the name is shorted and this time I tested deploying both simultaneously. Thank you!

I talked with the team internally and we believe there is no good solution here. We will talk to SchedMD and try to remove this limitation of 10 characters in the future.
Let's close this PR now and accept that these two deployments will temporarily clash until we fix this in a better way.


Specify a list of allowed folders/files to be archived

This PR adds a configuration to the archiver service in order to specify a list of folders (as regex) that can be archived.

I propose we keep it like that for time being, it should work. If we want to simplify we can do it later.


Bug Fix to rsyslog config

Fixes #
missed removing # in two lines in rsyslog.conf

Hi @NoamLandress - Please review and close on this one - it's changes to the CEF file so want to ensure these are ok. This is a very old PR so trying to clear these out. Thanks.

Very old PR, closing


Reconstruct README.md

It was accidentally deleted during merge but was outdated anyway, so we need to re-create it.

Fixed.