binding error on internal comms socket

I'm unable to create a new broker in an interactive session repeatedly.
# broker.py
import time
import helics as h

def main():
    initstring = "2 --name=mainbroker"
    # Create broker #
    print("Creating Broker")
    broker = h.helicsCreateBroker("zmq", "", initstring)
    print("Created Broker")

    print("Checking if Broker is connected")
    isconnected = h.helicsBrokerIsConnected(broker)
    print("Checked if Broker is connected")

    if isconnected == 1:
        print("Broker created and connected")

    try:

        while (h.helicsBrokerIsConnected(broker)):
            time.sleep(1)

    except KeyboardInterrupt:
        h.helicsCloseLibrary()

If I Ctrl+C this process, this results in the following the next time I try to call the main function.
In [2]: from broker import main
In [3]: main()
Creating Broker
binding error on internal comms socket
Created Broker
Checking if Broker is connected
Checked if Broker is connected

cc @bpalmintier

If you wait longer does it work again?  or is it permanently blocked (until python is terminated)?

Have you tried this on Windows and does it behave in the same way?

I am having similar issues under MATLAB, using OSX. (Also seeing binding error on internal comms socket errors on the command prompt used to start MATLAB's GUI, so likely coming from underlying C library?
Still working on fully repeatable sequence, but it might be something related to not unbinding from the port in ZMQ. See this Stack Overflow Post which though Python based, may hint at some of the same issue.

This post suggests killing the process
$ lsof -i :23405
COMMAND     PID     USER   FD   TYPE             DEVICE SIZE/OFF NODE NAME
python3.6 98590 $USER   34u  IPv4 0x83961aa5794b40cb      0t0  TCP localhost:23405 (LISTEN)

There must be a way to close the port in ZeroMQ, or if we are already doing it we have to make sure we catch these edge cases.

If I try to close the library it hangs the process the next time I run main.
In [7]: main()
Creating Broker
binding error on internal comms socket
Created Broker
Checking if Broker is connected
Checked if Broker is connected

In [8]: import helics as h

In [9]: h.helicsCleanupHelicsLibrary()

In [10]: h.helicsCloseLibrary()

In [11]: main()
Creating Broker
binding error on internal comms socket
^C^C^C^C^C^C^C^C^C^C^Z
[1]  + 98590 suspended  ipython

On Windows I get the same error. And it hangs on calling main, similar to the example above with the same binding error on internal comms socket.

Can you try the same test with a tcp and udp broker?

TCP
$ ipython
Python 3.6.4 |Anaconda, Inc.| (default, Jan 16 2018, 12:04:33)
Type 'copyright', 'credits' or 'license' for more information
IPython 6.3.1 -- An enhanced Interactive Python. Type '?' for help.

In [1]: from broker import main

In [2]: main()
Creating Broker
Created Broker
Checking if Broker is connected
Checked if Broker is connected
Broker created and connected
^C
In [3]: main()
Creating Broker
libc++abi.dylib: terminating with uncaught exception of type boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::system::system_error> >: bind: Address already in use
[1]    19847 abort      ipython

tcp: segfaults.
UDP
Python 3.6.4 |Anaconda, Inc.| (default, Jan 16 2018, 12:04:33)
Type 'copyright', 'credits' or 'license' for more information
IPython 6.3.1 -- An enhanced Interactive Python. Type '?' for help.

In [1]: from broker import main

In [2]: main()
Creating Broker
Created Broker
Checking if Broker is connected
Checked if Broker is connected
Broker created and connected
^C
In [3]: main()
Creating Broker
bind error on UDP socket bind: Address already in use
Unable to bind socket bind: Address already in use
Created Broker
Checking if Broker is connected
Checked if Broker is connected

In [4]: main()
Creating Broker
bind error on UDP socket bind: Address already in use
Unable to bind socket bind: Address already in use
Created Broker
Checking if Broker is connected
Checked if Broker is connected

In [5]: main()
Creating Broker
bind error on UDP socket bind: Address already in use
Unable to bind socket bind: Address already in use
Created Broker
Checking if Broker is connected
Checked if Broker is connected

In [6]:

udp: Waits between bind error on UDP socket bind: Address already in use and Unable to bind socket bind: Address already in use for a few seconds before proceeding and giving the user control back of the REPL.

Obviously the segfault is bad and needs to be fixed

I had to kill the process and start it again to get it to work.

Which process,  python or one of the python processes that it started?

The Python process that started the broker. And that's the only process
here.
On Wed, Aug 8, 2018, 11:08 AM Philip Top<EMAIL_ADDRESS>wrote:

Which process, python or one of the python processes that it started?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/GMLC-TDC/HELICS-src/issues/427#issuecomment-411499745,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABuqgdqMHpS-7wg0lonu6B1CeE4chiHLks5uOykOgaJpZM4VzR_E
.

When you Ctrl-C does it abort or does it jump into that except clause?

Ctrl+C raises a KeyboardException when the program is in the try block, and
results in the code in the except block being run.
On Wed, Aug 8, 2018, 12:03 PM Philip Top<EMAIL_ADDRESS>wrote:

When you Ctrl-C does it abort or does it jump into that except clause?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/GMLC-TDC/HELICS-src/issues/427#issuecomment-411516818,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABuqgb5zxQCoRhxKmq2BBZJcIYRmeCSkks5uOzYIgaJpZM4VzR_E
.

ok,  assuming you want to terminate a broker like that helicsBrokerDisconnect() should be called in that block.  It would seem there is some underlying issues exposed by this but you are bypassing the entire shutdown sequence for the brokers here.    The close library call should probably also do that so I will look into a few things.

Connected with #296

I have been trying to fix this and think I have but ran into a few oddities with the way cores/subbrokers terminated, and is leading to some issues in the TCP core, so I am slowly chasing those down.  Once that is all working again, I will add a PR that will include some of the fixes for these issues.

@kdheepak  would you mind checking some of this again with the latest develop branch.  I want to see if anything I did for the latest PR's helped fix the issues you were running into.

I can check this in a couple of hours.

@kdheepak  have you been able to check this issue?

Works great! I think we can close this!

Great!


useCheckBox is not working

this.treeOptions = {
animateExpand: true,
scrollOnActivate: true,
animateSpeed: 30,
animateAcceleration: 1.2,
useCheckbox: true
};
these are my options, useCheckbox is not working

need help ASAP

I just checked, it is working on firefox and not on chrome


Show number of commits ahead/behind in branch overview

Like #5326, but in the branch overview, like this:

This would be massively useful for deleting old branches, to check if they happen to have commits that aren't merged to develop yet (so you can't accidentally delete work).

Do we want to close this issue? Seems to me that feature requests like these should not be marked stale and be closed after a few months.

Stumbled into the same use case yesterday (after finally switching to wonderful gitea). It would be nice. Discussion here or in #5326 ?

I'll try to implement this feature.


propagate errors from dcproxy to cimi response

duplicated in https://github.com/mF2C/dataClay/issues/20


Support retry for discovery scan with ping probe option

For more context, the issue is that the discovery scan, which uses nmap, fails due to the machines blocking the ping probes. To resolve this, Cameradar should retry with the -Pn option.


[dvsim] Make sure odir is of type Path

I ran into the error below when cancelling a Dvsim run.
Making sure that odir is of type path will fix this.
INFO: [FlowCfg] [scratch_path]: [chip] [/workspaces/repo/scratch/master/chip_earlgrey_asic-sim-vcs]
Traceback (most recent call last):
  File "util/dvsim/dvsim.py", line 750, in <module>
    main()
  File "util/dvsim/dvsim.py", line 733, in main
    cfg.gen_results(results)
  File "/workspaces/repo/util/dvsim/FlowCfg.py", line 416, in gen_results
    item.write_results_html(self.results_html_name, item.results_md)
  File "/workspaces/repo/util/dvsim/FlowCfg.py", line 435, in write_results_html
    clean_odirs(odir=self.results_dir, max_odirs=89)
  File "/workspaces/repo/util/dvsim/utils.py", line 603, in clean_odirs
    shutil.move(odir, Path(odir).with_name(ts))
  File "/usr/lib64/python3.6/shutil.py", line 546, in move
    real_dst = os.path.join(dst, _basename(src))
  File "/usr/lib64/python3.6/shutil.py", line 510, in _basename
    return os.path.basename(path.rstrip(sep))
AttributeError: 'PosixPath' object has no attribute 'rstrip'

util/fix_trailing_whitespace.py util/dvsim/utils.py

Addendum: it seems like shutil  had a bug prior to version 3.9 where it falls over in case the src/dst arguments is a Path object (although the docs says it can accept path-like objects).
This may explain why this is working on some machines and GitHub CI, but not in the nightlies or some of our cloud runners.
See here for more context: https://bugs.python.org/issue32689
We may have to work around here and just cast the paths to strings before passing to shutil. I will investigate a follow-up fix for this.


"Jegălia" is listed in the drop-down menu

Description:
"Jegălia" is listed in the drop-down menu alongside its corresponding county and commune, according to the law
Precondition:
The website is up an running.

Step 1
Type "Jegălia" in the search bar.

Expected results
The location is listed in the drop-down menu as "Comuna Jegălia, CĂLĂRAȘI".


v4.9.3

Description
Fixes # (issue)

https://github.com/yoopta-editor/Yoopta-Editor/issues/416 by @Darginec05
https://github.com/yoopta-editor/Yoopta-Editor/issues/388 by @5andu
added deserializer for images in markdown  by @Waishnav
added selection of current block in editor.path by @Darginec05

Does this version has solved, depth issue with li element

Has this version resolved the depth issue with the li element?

Unfortunately no
It's planned for next patch release


Update munit to 0.7.28

Updates org.scalameta:munit from 0.7.27 to 0.7.28.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scalameta", artifactId = "munit" } ]

labels: test-library-update, semver-patch

Codecov Report

Merging #164 (0475a3b) into develop (6473e59) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop     #164   +/-   ##
========================================
  Coverage    50.00%   50.00%
========================================
  Files            5        5
  Lines           84       84
========================================
  Hits            42       42
  Misses          42       42

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 6473e59...0475a3b. Read the comment docs.


Create an Endpoint for Enquiring All Documents Issued from a Certain User ID to a Certain User ID

Create an Endpoint for Enquiring All Documents Issued from a Certain User ID to a Certain User ID
Feature Request: API Endpoint for Document Enquiry
Problem Statement
Currently, there is no functionality to query documents issued between specific users. This limitation hinders the ability to track document ownership transfers and verify document transactions effectively.

Proposed Solution
Develop a new REST API endpoint that retrieves documents issued between two specific users, providing:

Comprehensive document transaction tracking
Transparent ownership transfer mechanism
Easy verification of inter-user document exchanges

Endpoint Details
Method: GET
Endpoint: /api/documents/issued
Query Parameters:

fromUserId (required): The ID of the user issuing the documents.
toUserId (required): The ID of the user receiving the documents.

Response Example:
{
  "success": true,
  "data": [
    {
      "docId": "12345",
      "issuer": "user001",
      "recipient": "user002",
      "timestamps": {
        "issuedAt": "2024-11-27T12:00:00Z",
        "transferredAt": "2024-11-28T15:00:00Z"
      }
    },
    {
      "docId": "67890",
      "issuer": "user001",
      "recipient": "user002",
      "timestamps": {
        "issuedAt": "2024-10-15T09:30:00Z",
        "transferredAt": "2024-10-16T10:00:00Z"
      }
    }
  ]
}

Tasks Checklist

[x] Define the endpoint in the backend router.
[x] Create a service or query function to fetch the data from the database.
[x] Validate the fromUserId and toUserId query parameters.
[x] Ensure proper error handling for:

Missing or invalid user IDs.
No documents found for the given users.

[x] Write unit and integration tests for the endpoint.
[x] Update API documentation to include this endpoint.

Expected Benefits

Enables users to track document transactions between specific parties.
Improves transparency and auditability of document ownership.

References

Express.js Routing Documentation
Node.js Best Practices

📄 Document Search API Endpoint
🎯 Overview
The Document Search API provides a robust mechanism for retrieving document metadata based on issuer and recipient addresses, addressing the need for transparent document transaction tracking.
🚀 Endpoint Details
Endpoint Specification

Method: POST
Route: /api/documents/search
Content-Type: application/json

Request Payload
{
  "issuerAddress": "0x1234...",
  "recipientAddress": "0x5678..."
}

🔍 Request Parameters
Issuer Address

Type: Ethereum Address
Format: 0x prefixed hexadecimal string
Validation: Must be a valid 40-character hex address
Required: Optional (but at least one address must be provided)

Recipient Address

Type: Ethereum Address
Format: 0x prefixed hexadecimal string
Validation: Must be a valid 40-character hex address
Required: Optional (but at least one address must be provided)

📦 Response Structure
Successful Response
{
  "documents": [
    {
      "docId": "unique_document_identifier",
      "issuer": "0x_issuer_address",
      "recipient": "0x_recipient_address",
      "createdAt": "2024-01-01T00:00:00.000Z",
      "updatedAt": "2024-01-02T00:00:00.000Z"
    }
  ],
  "totalCount": 1,
  "processingTime": 50,
  "searchCriteria": {
    "issuerAddress": "0x1234...",
    "recipientAddress": "0x5678..."
  }
}

🛡 Validation Rules

At least one address (issuer or recipient) must be provided
Addresses must be valid Ethereum format (0x + 40 hex characters)
Empty or malformed addresses will trigger a 400 Bad Request

🚨 Error Scenarios
No Search Criteria

Status: 400 Bad Request
Message: Please provide either issuer or recipient address

Invalid Address Format

Status: 400 Bad Request
Message: Invalid issuer address format or Invalid recipient address format

Server Error

Status: 500 Internal Server Error
Response: Includes detailed error information

🔒 Security Considerations

Validates Ethereum address format
Logs all search attempts
Prevents potential injection or malicious queries
Returns minimal document metadata

📊 Performance Metrics

Designed for efficient querying
Minimal payload transmission
Rapid document metadata retrieval

🔗 Related Issue
Issue #5: Create an Endpoint for Enquiring All Documents Issued from a Certain User ID to a Certain User ID
✅ Implementation Status

[x] Endpoint developed
[x] Address validation implemented
[x] Comprehensive logging added
[x] Error handling established
[x] Metadata-only response created

💡 Usage Examples
Example 1: Search by Issuer
curl -X POST /api/documents/search \
     -H "Content-Type: application/json" \
     -d '{"issuerAddress": "0x1234..."}'

Example 2: Search by Recipient
curl -X POST /api/documents/search \
     -H "Content-Type: application/json" \
     -d '{"recipientAddress": "0x5678..."}'

Example 3: Search by Both Addresses
curl -X POST /api/documents/search \
     -H "Content-Type: application/json" \
     -d '{
         "issuerAddress": "0x1234...",
         "recipientAddress": "0x5678..."
     }'

🔮 Future Enhancements

Implement pagination for large result sets
Add more granular filtering options
Enhance performance with indexing

📝 Notes

Timestamps use ISO 8601 format
Processing time in milliseconds
Designed for scalability and efficiency


Can't compile: fail detect attributes

DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

[X] I understand that I will be blocked if I intentionally remove or skip any mandatory* field

Checklist

[X] I'm reporting a bug unrelated to a specific site
[X] I've verified that I'm running yt-dlp version 2023.02.17 (update instructions) or later (specify commit)
[X] I've checked that all provided URLs are playable in a browser with the same IP and same login details
[X] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[X] I've searched known issues and the bugtracker for similar issues including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue

Provide a description that is worded well enough to be understood
can't compile even with a package installed
package: python-pycryptodomex
Provide verbose output that clearly demonstrates the problem

[X] Run your yt-dlp command with -vU flag added (yt-dlp -vU <your command line>)
[X] Copy the WHOLE output (starting with [debug] Command-line config) and insert it below

Complete Verbose Output
$ python3 devscripts/make_lazy_extractors.py
Traceback (most recent call last):
  File "/home/basura/yt-dlp/yt_dlp/compat/compat_utils.py", line 36, in __getattribute__
    ret = super().__getattribute__(attr)
  File "/home/basura/yt-dlp/yt_dlp/compat/compat_utils.py", line 56, in __getattr__
    raise AttributeError(f'module {parent.__name__} has no attribute {attr}')
AttributeError: module yt_dlp.dependencies.Cryptodome has no attribute Cipher

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/basura/yt-dlp/devscripts/make_lazy_extractors.py", line 132, in <module>
    main()
  File "/home/basura/yt-dlp/devscripts/make_lazy_extractors.py", line 41, in main
    _ALL_CLASSES = get_all_ies()  # Must be before import
  File "/home/basura/yt-dlp/devscripts/make_lazy_extractors.py", line 68, in get_all_ies
    from yt_dlp.extractor.extractors import _ALL_CLASSES
  File "/home/basura/yt-dlp/yt_dlp/__init__.py", line 18, in <module>
    from .cookies import SUPPORTED_BROWSERS, SUPPORTED_KEYRINGS
  File "/home/basura/yt-dlp/yt_dlp/cookies.py", line 18, in <module>
    from .aes import (
  File "/home/basura/yt-dlp/yt_dlp/aes.py", line 5, in <module>
    from .dependencies import Cryptodome
  File "/home/basura/yt-dlp/yt_dlp/dependencies/__init__.py", line 76, in <module>
    Cryptodome_AES = Cryptodome.Cipher.AES if Cryptodome else None
  File "/home/basura/yt-dlp/yt_dlp/compat/compat_utils.py", line 43, in __getattribute__
    ret = getter(attr)
  File "/home/basura/yt-dlp/yt_dlp/compat/compat_utils.py", line 56, in __getattr__
    raise AttributeError(f'module {parent.__name__} has no attribute {attr}')
AttributeError: module yt_dlp.dependencies.Cryptodome has no attribute Cipher

Pls share these details https://github.com/yt-dlp/yt-dlp/issues/6272#issuecomment-1435433009

$ python3 -c "from Cryptodome.Cipher import AES; print(AES)"
Traceback (most recent call last):
  File "<string>", line 1, in <module>
ModuleNotFoundError: No module named 'Cryptodome.Cipher'

$ python3 -c "from Crypto.Cipher import AES; print(AES)"
Traceback (most recent call last):
  File "<string>", line 1, in <module>
ModuleNotFoundError: No module named 'Crypto'

$ pip install cffi
Defaulting to user installation because normal site-packages is not writeable
Collecting cffi
  Downloading cffi-1.15.1-cp310-cp310-manylinux_2_12_i686.manylinux2010_i686.manylinux_2_17_i686.manylinux2014_i686.whl (421 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 421.7/421.7 kB 2.0 MB/s eta 0:00:00
Collecting pycparser
  Downloading pycparser-2.21-py2.py3-none-any.whl (118 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 118.7/118.7 kB 1.4 MB/s eta 0:00:00
Installing collected packages: pycparser, cffi
Successfully installed cffi-1.15.1 pycparser-2.21

$ python3 -c "from Cryptodome.Cipher import AES; print(AES)"
Traceback (most recent call last):
  File "<string>", line 1, in <module>
ModuleNotFoundError: No module named 'Cryptodome.Cipher'

$ python3 -c "from Crypto.Cipher import AES; print(AES)"
Traceback (most recent call last):
  File "<string>", line 1, in <module>
ModuleNotFoundError: No module named 'Crypto'

Thx. I'll push a fix soon


New Fuel APIs for Store

Fixes: #7255
I've implemented the APIs as documented in the strawman there, but I used Option<NonZeroU64> for the yield interval instead of trying to figure out what to do if the yield interval is 0.
I also took a stab in the second commit in being able to support the full range of u64 so that you can set_fuel(u64::MAX) then get_fuel() == u64::MAX. This makes accounting externally less tricky since we're removing that functionality from wasmtime directly.
prtest:full

I'm happy to drop the second commit and not try to fix the full resolution if there is a desire to keep the same semantics there (I'm assuming it's OK if there no async support to still return Ok from the out_of_gas function in Store).

I'll take a look once CI is green, so feel free to ping me when that comes up. I'll check in every now and then as well.

@alexcrichton test are passing (no rush on a review, I wont be able to make updates until Monday anyways)

oops sorry queued up for merge a bit too soon there


Potential Typos and Incorrect Variable Use in Prompts

Thank you for your great research. I appreciate that you are sharing your research code as open source, which has allowed me to run the code myself and deepen my understanding. I noticed a few things in the t2ebm/prompts.py while running the code.
1. Typos in Prompt

There is a typo in the summarize_ebm prompt where "importaces" should be corrected to "importances".
There is a typo in the describe_graph_cot prompt where "suprising" should be corrected to "surprising".

2. Logic Error
https://github.com/interpretml/TalkToEBM/blob/34ed6528a4e37d2b95664a7452f341fe83deb7af/t2ebm/prompts.py#L92-L93
In the if statement of summarize_ebm that checks for a non-empty dataset_description, the code appears to be using graph_descriptions instead of dataset_description when adding the dataset information to the message. This could lead to incorrect information being passed to the LLM.
Thank you for your time and consideration!

Hi @IkokObi . Thanks for reporting these bugs! I updated the package to version 0.1.1, which should fix the reported bugs. Let me know if you encounter any other problems with the package.

I will close this issue for now, but feel free to open a new issue should you find any more bugs in the code :)


Wish: Determine activity type

Is there a way to have findWorkouts() return activityType associated with each activity? i.e. walking, running...etc.

Working on this.. it will return the iOS activityTypes (HKWorkoutActivityTypeClimbing, etc).

Great!! Please keep me posted. Looking forward to this. It may also be useful to provide the calories too for each workout object

Hi, you can now use v 0.3.1 which returns the activityType in the findWorkouts response.
I've added a TODO in the code for the totalEnergyBurned property. Will add it later probably.

Thanks! I'll give it a shot


Array type property translation wrong

The array type property needs to be translated to a property first, then based on its items to see whether needs to create more shapes, but the current translation directly creates a node shape which is not correct.
For example, if we have
"P":{
			"type": "array",
			"items": {"type": "string"}},

what we need to create is just
PS a sh:PropertyShape ;
    sh:path :P  .

@xuemduan @dachafra I've fixed both issues. Whenever you can, please check if it's alright now.

@xuemduan @dachafra I've fixed both issues. Whenever you can, please check if it's alright now.

It works well now:)

Thank you very much @osm0512


Toggle Scene with non-intensity channels

I've set up a sample scene in which I want to only modify the Maintenance & Speed channels of a fixture. Whilst I can create a Flash Function Button, The Toggle Function Button doesn't behave properly - When the button is clicked it will set the values as per the scene (as long as the Reset Universe button has been clicked in the Simple Desk - Issue #20), however it doesn't remain pushed, and the scene can't be stopped.
In my test case I have a single Stairville PAR56 with the following channels - Mode (Maintenance), RGB (Intensity) & Speed (Speed).
Function - Set Mode = 192, RGB = 0, Speed = 11

Actually, sometimes the Flash Function Button doesn't work either:
Simple Desk Bug.qxc

Load sample qxc
Switch to operate mode
Show Fixture Monitor
Hold "3 Colour Change - Fast" flash button - Channels change as expected
Now click "3 Colour Change - Fast" toggle button - Channels remain on.
Toggle "White" on and then off to reset all channels.
"3 Colour Change - Fast" flash button now doesn't operate properly (the Simple Desk sliders now have had the Mode & Speed values set)

I'm putting it down to the fact that the Simple Desk picks up the changes, and due to the channels being LTP (Latest Takes Preference) it is overriding the values being set by the Virtual Desk. This is also noticeable as sometimes the sliders can't set the the Mode & Speed (the slider moves, and the Fixture Monitor shows the change, but then the value is immediately set to the value chosen in Simple Desk)
As useful as the simple desk is, it's causing quite a few issues as it likes to take precedence - it'd be nice to optionally disable it. In fact I'm looking through the source for a way to disable it and recompile.
Quick video on how to reproduce

No feedbacks from the submitter.
Closing now.


Refreshing the results page should hydrate state

Currently, refreshing after a successful display of results leads to Something went wrong being displayed and the header shows no locations and Invalid Date.

After a bit of digging, it works nicely in dev environment, and when deploying it as a static application on Netlify, it breaks.
First answers to be found in that thread:
https://github.com/zeit/next.js/issues/4663


Command line terminal: Chinese display error

We have written the needed data into your clip

board because it was too large to send. Please paste.

@windyflying This one can help you #60717


design is a major part of front-end development.

While coding is an important part of front-end development, it is only one aspect of it. A large portion of front-end development is indeed centered around design and creativity.

Please add content in the specified format!

@devjayswal refer contribution.md file or other files

I'm closing this PR, try to update changes in required format, and make sure where you are trying to upload your changes.


Break out discord admin commands into module

This module depends on the discord module to function

this module should not be discord-specific


SC Alliance for Mobile Infrastructure  Excellence in Innovation Award

That sneaky @greenlinktransit submitted our trolley tracker project for the Excellence in Innovation Award for the SC Alliance for Mobile Infrastructure Conference and we won!
http://www.scltap.org/alliance/
They had to submit a name for the award and they used mine. I didn't know about that ahead of time, but I certainly consider this a group award. Congrats to everyone who's worked on the project. Hooray!

Hip hip hooray! Gonna take a trip down to Isle of Palms to accept it? ;)
rough living down there
On Wed, Feb 17, 2016 at 1:11 PM, Adam Gautsch<EMAIL_ADDRESS>wrote:

That sneaky @greenlinktransit https://github.com/greenlinktransit
submitted our trolley tracker project for the Excellence in Innovation
Award for the SC Alliance for Mobile Infrastructure Conference and we won!
http://www.scltap.org/alliance/
They had to submit a name for the award and they used mine. I didn't know
about that ahead of time, but I certainly consider this a group award.
Congrats to everyone who's worked on the project. Hooray!
[image: image]
https://cloud.githubusercontent.com/assets/1761333/13119570/d7e54550-d577-11e5-9891-ea1e911d1409.png
—
Reply to this email directly or view it on GitHub
https://github.com/codeforgreenville/trolley-tracker/issues/131.

You guys deserve it!!

Wow awesome!
On Wednesday, February 17, 2016, greenlinktransit<EMAIL_ADDRESS>wrote:

You guys deserve it!!
—
Reply to this email directly or view it on GitHub
https://github.com/codeforgreenville/trolley-tracker/issues/131#issuecomment-185340153
.


[BUG] Can't create VMs

Describe the bug

When you try to create a VM you get an error and a 500 response
To Reproduce
Steps to reproduce the behavior:

Create a new VM

Expected behavior

You should be able to create a VM
Support bundle

supportbundle_d8c81821-1508-4c07-9ea6-eb3af635b671_2022-10-14T18-41-32Z.zip
Environment

Harvester ISO version: master-5149fc95-head
Underlying Infrastructure (e.g. Baremetal with Dell PowerEdge R630): ipxe-examples Vagrant 3 node

Additional context
Add any other context about the problem here.
When creating a VM it seems to be getting a 500 error. The actual response to the POST request is this
{"type":"error","links":{},"code":"InternalError","message":"Internal error occurred: failed calling webhook \"virtualmachines.kubevirt.io-tmp-validator\": failed to call webhook: Post \"https://fake-validation-service.harvester-system.svc:443/fake-path/virtualmachines.kubevirt.io?timeout=10s\": service \"fake-validation-service\" not found","status":500,"type":"error"}

This seems to happen with both raw image template and ISO template VMs

I am also running into this. I found this issue but I don't see anywhere we use the Hyperconverged Cluster Operator.

on version 1.1.0-rc1, there are virt- pods running that aren't running on 1.1.0-rc3:
1.1.0-rc1
> kubectl -n harvester-system get po | grep virt
virt-api-bdc94b6d9-mwlr9                                    1/1     Running            1 (11m ago)     17d
virt-controller-744978949c-5pmqv                            1/1     Running            2 (11m ago)     17d
virt-controller-744978949c-5zv2c                            1/1     Running            1 (11m ago)     17d
virt-handler-fcdmc                                          1/1     Running            1 (11m ago)     17d
virt-operator-894555c9-ccpd8                                1/1     Running            2 (11m ago)     17d

1.1.0-rc3
> kubectl -n harvester-system get po | grep virt
virt-operator-7f6497cb97-x5ss4

Errors in virt-operator pod : customresourcedefinitions.apiextensions.k8s.io \"virtualmachineinstances.kubevirt.io\" already exists

Already verified by @noahgildersleeve. Closing this one. Feel free to reopen if you see this again.


Feature: Forgot password

Description
This PR adds the functionality to reset password for a user by email.

8 Global settings:

Category
Type
Name
Default value
Description
Dynamic

Advanced
Long
password.reset.ttl
30
Password reset ttl in minutes
Yes

Advanced
String
password.reset.email.sender
null
Password reset email sender
Yes

Advanced
String
password.reset.smtp.host
null
Password reset smtp host
No

Advanced
Integer
password.reset.smtp.port
25
Password reset smtp port
No

Advanced
Boolean
password.reset.smtp.useAuth
False
Use auth for smtp in Password reset
No

Advanced
String
password.reset.smtp.username
null
Password reset smtp username
No

Secure
String
password.reset.smtp.password
null
Password reset smtp password
No

Advanced
String
password.reset.mail.template
Hello {{username}}!\nYou have requested to reset your password. Please click the following link to reset your password:\n{{{reset_link}}}\nIf you did not request a password reset, please ignore this email.\n\nRegards,\nThe CloudStack Team
Password reset mail template. This uses mustache template engine. Available variables are: username, firstName, lastName, resetLink, token
Yes

2 new APIs:

Command: forgotPassword
Params: username, domain
Details: Sends an email to the user with a token which can be used to reset the password using resetPassword command.
Command: resetPassword
Params: username, domain, token, password
Details: Resets the password for the user using the token generated via forgotPassword command.

Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[x] New feature (non-breaking change which adds functionality)
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] Enhancement (improves an existing feature and functionality)
[ ] Cleanup (Code refactoring and cleanup, that may add test cases)
[ ] build/CI
[ ] test (unit or integration test code)

Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale

[ ] Major
[x] Minor

Screenshots (if appropriate):
How Has This Been Tested?

How did you try to break this feature and the system with this change?

@blueorangutan package

@vishesh92 a [SL] Jenkins job has been kicked to build packages. It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

@blueorangutan package

@vishesh92 a [SL] Jenkins job has been kicked to build packages. It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

Packaging result [SF]: ✖ el8 ✖ el9 ✖ debian ✖ suse15. SL-JID 10607

@blueorangutan package

@vishesh92 a [SL] Jenkins job has been kicked to build packages. It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

Packaging result [SF]: ✖ el8 ✖ el9 ✖ debian ✖ suse15. SL-JID 10608

@blueorangutan package

@vishesh92 a [SL] Jenkins job has been kicked to build packages. It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

Packaging result [SF]: ✖ el8 ✖ el9 ✖ debian ✖ suse15. SL-JID 10625

@blueorangutan package

@vishesh92 a [SL] Jenkins job has been kicked to build packages. It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

@blueorangutan test

@vishesh92 a [SL] Trillian-Jenkins test job (ol8 mgmt + kvm-ol8) has been kicked to run smoke tests

[SF] Trillian test result (tid-11068)
Environment: kvm-ol8 (x2), Advanced Networking with Mgmt server ol8
Total time taken: 53619 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr9509-t11068-kvm-ol8.zip
Smoke tests completed. 138 look OK, 1 have errors, 0 did not run
Only failed and skipped tests results shown below:

Test
Result
Time (s)
Test File

test_01_redundant_vpc_site2site_vpn
Failure
457.46
test_vpc_vpn.py

test_01_vpc_site2site_vpn
Failure
320.12
test_vpc_vpn.py

@blueorangutan package

@vishesh92 a [SL] Jenkins job has been kicked to build packages. It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

Packaging result [SF]: ✔ el8 ✔ el9 ✔ debian ✔ suse15. SL-JID 10773

@blueorangutan package

@vishesh92 a [SL] Jenkins job has been kicked to build packages. It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

Packaging result [SF]: ✔ el8 ✔ el9 ✔ debian ✔ suse15. SL-JID 10828

@blueorangutan package

@vishesh92 a [SL] Jenkins job has been kicked to build packages. It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

Packaging result [SF]: ✔ el8 ✔ el9 ✔ debian ✔ suse15. SL-JID 10878

@blueorangutan package

@vishesh92 a [SL] Jenkins job has been kicked to build packages. It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

@vishesh92 a [SL] Jenkins job has been kicked to build packages. It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

Packaging result [SF]: ✔ el8 ✔ el9 ✔ debian ✔ suse15. SL-JID 10963

@blueorangutan package

@vishesh92 a [SL] Jenkins job has been kicked to build packages. It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

Packaging result [SF]: ✔ el8 ✔ el9 ✔ debian ✔ suse15. SL-JID 10966

@blueorangutan package

@vishesh92 a [SL] Jenkins job has been kicked to build packages. It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

Packaging result [SF]: ✔ el8 ✔ el9 ✔ debian ✔ suse15. SL-JID 10970

@blueorangutan package

@vishesh92 a [SL] Jenkins job has been kicked to build packages. It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

Packaging result [SF]: ✔ el8 ✔ el9 ✔ debian ✔ suse15. SL-JID 10996

@blueorangutan package

@borisstoyanov a [SL] Jenkins job has been kicked to build packages. It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

Packaging result [SF]: ✖ el8 ✖ el9 ✖ debian ✖ suse15. SL-JID 11004

@vishesh92 a [SL] Jenkins job has been kicked to build packages. It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

Packaging result [SF]: ✔ el8 ✔ el9 ✔ debian ✔ suse15. SL-JID 11008

@blueorangutan package

@vishesh92 a [SL] Jenkins job has been kicked to build packages. It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

Packaging result [SF]: ✔ el8 ✔ el9 ✔ debian ✔ suse15. SL-JID 11028

@JoaoJandre This feature is behind a flag to enable or disable the password recovery workflow. By default, it's disabled. Can we include this PR in 4.20 release as well?

@blueorangutan test

@vishesh92 a [SL] Trillian-Jenkins test job (ol8 mgmt + kvm-ol8) has been kicked to run smoke tests

@JoaoJandre This feature is behind a flag to enable or disable the password recovery workflow. By default, it's disabled. Can we include this PR in 4.20 release as well?

@vishesh92 same as https://github.com/apache/cloudstack/pull/9633#issuecomment-2333927794 :)

[SF] Trillian Build Failed (tid-11418)

[SF] Trillian Build Failed (tid-11420)

@blueorangutan test

@vishesh92 a [SL] Trillian-Jenkins test job (ol8 mgmt + kvm-ol8) has been kicked to run smoke tests

[SF] Trillian Build Failed (tid-11421)

@blueorangutan package

Packaging result [SF]: ✔ el8 ✔ el9 ✔ debian ✔ suse15. SL-JID 11050

@blueorangutan test

@vishesh92 a [SL] Trillian-Jenkins test job (ol8 mgmt + kvm-ol8) has been kicked to run smoke tests

@blueorangutan help

@borisstoyanov [SL] I understand these words: "help", "hello", "thanks", "package", "test"
Test command usage: test [mgmt os] [hypervisor] [keepEnv] [qemuEv] [basicZone|securityGroups]
Mgmt OS options: ['ol8', 'ol9', 'alma8', 'alma9', 'suse15', 'centos7', 'centos6', 'rocky8', 'ubuntu18', 'ubuntu22', 'ubuntu20', 'ubuntu24']
Hypervisor options: ['kvm-centos6', 'kvm-centos7', 'kvm-rocky8', 'kvm-ol8', 'kvm-ol9', 'kvm-alma8', 'kvm-alma9', 'kvm-ubuntu18', 'kvm-ubuntu20', 'kvm-ubuntu22', 'kvm-ubuntu24', 'kvm-suse15', 'vmware-55u3', 'vmware-60u2', 'vmware-65u2', 'vmware-67u3', 'vmware-70u1', 'vmware-70u2', 'vmware-70u3', 'vmware-80', 'vmware-80u1', 'vmware-80u2', 'vmware-80u3', 'xenserver-65sp1', 'xenserver-71', 'xenserver-74', 'xcpng74', 'xcpng76', 'xcpng80', 'xcpng81', 'xcpng82']
Note: when keepEnv is passed, you need to specify mgmt server os and hypervisor or use the matrix command.
when qemuEv is passed, it will deploy KVM hyperviosr hosts with qemu-kvm-ev, else it will default to stock qemu.
When basicZone and/or securityGroups are passed it will create a zone of the last type specified (default is Advanced)
Package command usage: package [all(default value),kvm,xen,vmware,hyperv,ovm] - a comma separated list can be passed with package command to bundle the required hypervisor's systemVM templates. Not passing any argument will bundle all - kvm,xen and vmware templates.
Blessed contributors for kicking Trillian test jobs: ['rohityadavcloud', 'shwstppr', 'vishesh92', 'Pearl1594', 'harikrishna-patnala', 'nvazquez', 'DaanHoogland', 'weizhouapache', 'borisstoyanov', 'vladimirpetrov', 'kiranchavala', 'andrijapanicsb', 'NuxRo', 'rajujith', 'alexandremattioli', 'sureshanaparti', 'abh1sar']

[SF] Trillian test result (tid-11422)
Environment: kvm-ol8 (x2), Advanced Networking with Mgmt server ol8
Total time taken: 52163 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr9509-t11422-kvm-ol8.zip
Smoke tests completed. 140 look OK, 1 have errors, 0 did not run
Only failed and skipped tests results shown below:

Test
Result
Time (s)
Test File

test_01_secure_vm_migration
Error
134.18
test_vm_life_cycle.py

test_01_secure_vm_migration
Error
134.18
test_vm_life_cycle.py

@JoaoJandre @DaanHoogland are we accepting feature PRs now? This is ready for merging and has been reviewed & manually tested.

sure @JoaoJandre, both positive/negative scenarios, as well with different sub-domains accounts. Also verified the token cannot be used to change other users pass and basic user discovery prevention where prompts a generic response either having matching user or not. Also there were some polishing comments for the email, it now uses html format and there is a text with hyperlink rather than raw hyperlink as before. I didn't see any issues, have you experienced any?

sure @JoaoJandre, both positive/negative scenarios, as well with different sub-domains accounts. Also verified the token cannot be used to change other users pass and basic user discovery prevention where prompts a generic response either having matching user or not. Also there were some polishing comments for the email, it now uses html format and there is a text with hyperlink rather than raw hyperlink as before. I didn't see any issues, have you experienced any?

@borisstoyanov I have not tested the PR. But it is generally good practice to list the tests done and their steps. Like the PR description does.


BME280 | bme280isConnected turns false after the first reading

Hi @kmetz,
thanks a lot for the great instructions. Everything works beautifully over here.
The only small issue i have is, that bme280isConnected changes to false after the first reading of the BME280 sensor.
I can't seem to solve it... any pointers?
Thanks much in advance!

Thanks! I will lok into this ASAP.

Ok, with the much appreciated help and feedback of @htor-j I was able to fix this, BME280 has to run in MODE_NORMAL instead of MODE_FORCED, the latter requires to re-set forced mode before each reading (it goes into sleep mode afterwards). Normal mode will update readings internally periodically and is also recommended when using filters (see datasheet).

Please use 71cc1216 / v1.2.2 +.

It's working now. Thanks for the fix, @kmetz!


eslint upgrades to latest versions

Codecov Report

Merging #53 (8660887) into main (040a758) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main       #53   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           15        15
  Lines          346       346
  Branches        50        50
=========================================
  Hits           346       346

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 040a758...8660887. Read the comment docs.


Remove unnecessary reducer call

Nice catch!
Would you mind adding a regression test in the store enhancer spec that asserts that the reducer is only called once?

No problem, I've created a cleaner PR for you here:
https://github.com/FormidableLabs/redux-little-router/pull/66
So please disregard this one.


No OnVideoEnd event?

Describe the issue
I have OnVideoStart, but I can't seem to see OnVideoEnd, and my video just loops back to the start.
How can I get the video end event?
Unity version
2019.4.4
Operating system
Android, iOS, WebGL

Hello rankorn, I have the same problem. Did you find a solution?

No.. and actually had a more severe problem where this plugin crashes my iOS app when I go to the background..
So I currently do not use this.


[HACKTOBERFEST 2024] - localStorage and CRUD Quiz

[!IMPORTANT]
This issue is part of our 2024 Hacktoberfest initiative. If you are interested in working on this issue, refer to our top-level tasks to see if this issue is claimed, or to claim it if it is not.

This issue is to create the localStorage and CRUD quiz.
The file you should be working on is found in /curriculum/challenges/english/25-front-end-development/quiz-localstorage-and-crud.
All quiz questions need to relate to one of these topics:

What is CRUD, how do Create, Read, Update, Delete work
localStorage and Web Storage API
sessionStorage
JSON and property access
JSON.parse() and JSON.stringify()
cookies
cache API
client-side storage negative patterns (e.g. tracking/fingerprinting)
using cookies to store arbitrary data
IndexedDB
Cache/Service workers and Progressive Web Apps

[!CAUTION]
Questions which do not fall under these topics will be rejected.

You are welcome to include code blocks in your questions, but please keep them short (four lines or less).
Please do NOT open a pull request until you have completed all questions. Your quiz should have exactly 20 questions.

Thank you for your interest in contributing. This issue will be opened for contribution when Hacktoberfest starts on October 1st.

[!CAUTION]
Pull requests which are created before October 1st will not be eligible for Hacktoberfest. We appreciate enthusiasm, but encourage you to hold off on contributing to this issue until the event has begun.

If you wish to be notified when this issue is opened for contribution, subscribe to notifications:

This issue is now open
If you would like to work on this issue, please leave a comment so we can assign it to you.
Be sure to read our contributing guidelines.

I would like to work on the localStorage and CRUD quiz for Hacktoberfest.

O would like to work on this issue

Hello @naomi-lgbt,
I'm interested in working on this quiz. With practical experience in localStorage, CRUD operations, and client-side storage, I feel confident in covering all the listed topics effectively. Could you please assign this issue to me?
Thank you!

This issue has been assigned a contributor. To prevent extraneous notifications, the issue is now locked. If you have any questions, please reach out to me in our Discord community.


Do you die? we need you to improve Nameko Library

Do you die? we need you to improve Nameko Library

I agree, great potential it has but seems like author doesn;t have a time for it :(
I'm using it in work now intensively, so I gonna start improving it myself. If anyone is interested in help or use my fixes/improvements I welcome to this repo:
https://github.com/krzysiekfonal/nameko.
Those are points I gonna improve/fix first:

switch master to 3.0 version
allow debugging
fix standalone clients
timeouts
use Kombu instead rabbitmq directly to make it independent
better events support (receiver doesn’t have to know the source)
newer dependencies

@krzysiekfonal Are you still working on it? On GitHub I dont see any progress from you, developing it internally?

Looks like @mattbennett came back to accept a PR. I really hope nameko receives the due attention.

Hello, yes I am back. A change of circumstance means I have more time available for Nameko now.
My immediate priority is release 3.0 as a stable version, including updated docs on how to actually use 3.0. I'll get that done first, and then we can start conversations about the next most important things to improve.

@mattbennett Hows it going?


CSV export won't add quotes

System information:

Ubuntu 18.04
DBeaver version <IP_ADDRESS>.xxxxx
Java version
openjdk version "10.0.2" 2018-07-17
OpenJDK Runtime Environment (build 10.0.2+13-Ubuntu-1ubuntu<IP_ADDRESS>)
OpenJDK 64-Bit Server VM (build 10.0.2+13-Ubuntu-1ubuntu<IP_ADDRESS>, mixed mode)
Additional extensions

Connection specification:

Database name and version : HSQLDB / Embedded
Driver name : HSQLDB / Embedded
Do you use tunnels or proxies (SSH, SOCKS, etc)?  ??

Describe the problem you're observing:
I have some tables I've loaded up from another database that I've been tasked to convert.  I right click table and do the following:

Export Data
CSV
Single Query / Open New Connections (ticked) / Select Row Count (ticked)
Binaries (set to NULL)
File Extension (CSV) / Delimiter (,) / Header (top) / Characters escape (escape and also tried quotes) / Quote Character (") / Quote Always (ticked) / Quote Never (unticked) / NULL Strings (empty) / Format Numbers (unticked)
Either Save to a file OR copy to clipboard

This is an example of the data that is exported as copied to clipboard and pasted here:
14814,Description, 60,134,160
Now I would have expected it to be:
"14814","Description", "60","134","160"
I've tried many things, is this a bug?
Steps to reproduce, if exist:
Include any warning/errors/backtraces from the logs
There were no errors in the logs when looking

Can't reproduce.
Please post screenshot of CSV export configuration page.

Hi and thanks for looking.
Here are the screenshots:  https://imgur.com/a/yfjN5ds
Please note you'll see I try both quotes and escape and I get the same result each time (no quoted cells when I open the CSV".
Also I try copy to clipboard and save file but still the same.

UPDATE:  Tried with the very latest build and still the same problem.  To confirm I loaded the same dataset with the same drivers in SQLRazor and it exported with quotes surrounding data that has a delimiter in it, so it eliminates the data source as the issue.

As I see from screenshot you have wrong configuration for quote character. It is  " i.e. space + quote character. Just reset this property value to default or change it manually.


[ui-chassis-spring] remove zuul dependencies

#4549

We also need to add documentation, as removal of zuul affects how a user would deploy the UI if they are setting up themselves.

This PR is incomplete, check this one for the complete removal of Zuul Module: https://github.com/odpi/egeria/pull/4922


stream frame should not be process futher when connection error be detected

https://github.com/litespeedtech/lsquic/blob/d9b2c378376468a2aa2a75b24b2c3b9a3f82dc48/src/liblsquic/lsquic_stream.c#L1538

readf may found connection error, like HEC_QPACK_DECOMPRESSION_FAILED
If connection error happen, I think stream frame should not be process again. Otherwise it may assert some unexpected action.

qdec_process_blocked_headers may access nullptr after conn encounter HEC_QPACK_DECOMPRESSION_FAILED.

By the way, I have not find how to reproduce it, but it happen twice in our quic_server(develop base on lsquic).

coredump has been fixed by: https://github.com/litespeedtech/ls-qpack/commit/b97e714470a01c7c8b1999cb42f267b34265fcae


Build failed on fee issue in wallet.py

Describe the issue
https://travis-ci.org/drivechain-project/bitcoin/jobs/248532545
It looks we like we have some sort of rounding error inside of wallet.py. I'm not sure if this is a change we have introduced or a bug upstream. If it is a problem upstream we need to report it eventually.

It looks like this was fixed in https://github.com/drivechain-project/bitcoin/pull/15 by properly surrounding the wallet code which I added in
#ifdef WALLET_ENABLED blocks.
Since https://github.com/drivechain-project/bitcoin/pull/13 is passing on Travis CI now, I think we can close this issue. I didn't touch any Python code, so it must have been a bitcoind compilation issue in the test runner or something? I'm not really familiar with the Python part of the testing system but nothing else really makes sense as a reason that the C++ code made the Python tests fail like that.


onPressIn not working in android for drag immediately

Hello, I want to use a TouchableOpacity as drag handler. in Android when FlatList doesn't need to scroll, drag works with onPressIn but when size of data increases and FlatList needs to scroll, onPressIn not working and when I touch drag zone, flatList scroll avoid me to drag immediately without LongPress.
in iOS, everything is working good.
and my code is like below:
const Item = ({title, drag, onDragHandlerPressIn, onDragHandlerPressOut}): Node => {
  return (
    <View style={{flexDirection: 'row'}}>
      <Text>{title}</Text>
      <TouchableOpacity
        style={{height: 70}}
        onPressIn={() => {
          onDragHandlerPressIn();
          drag();
        }}
        onPressOut={onDragHandlerPressOut}
        activeOpacity={1}>
        <Text>Drag Me</Text>
      </TouchableOpacity>
    </View>
  );
};

<DraggableFlatList
        scrollEnabled={scrollEnabled}
        data={data}
        keyExtractor={(item, index) => `key::${index}`}
        onDragEnd={(newData) => {
          setScrollEnabled(true);
          if (newData.from === newData.to)
            return;
          setData(newData.data);
        }}
        renderItem={({item, drag}) => (
          <ScaleDecorator>
            <OpacityDecorator activeOpacity={1}>
              <ShadowDecorator>
                <Item
                  drag={drag}
                  onDragHandlerPressIn={() => setScrollEnabled(false)}
                  onDragHandlerPressOut={() => setScrollEnabled(true)}
                  title={item}
                />
              </ShadowDecorator>
            </OpacityDecorator>
          </ScaleDecorator>
        )}
      />

Platform & Dependencies
"react": "17.0.2",
"react-native": "0.66.3",
"react-native-draggable-flatlist": "^3.0.3",
"react-native-gesture-handler": "^1.10.3",
"react-native-reanimated": "^2.2.4"

I don't fully understand the problem, can you post a snack?
onPressIn on android seems to be working as expected in the snack I created here: https://snack.expo.dev/@computerjazz/rndfl-onpressin

I am testing it using expo. I don't know if my issue is the same as @oneHamidreza's, but both Android and iOS have issues when I press on a number immediately after scrolling the list down/up.
On Android, I can't select the item on press, so I have to long press the item. Also the selected item sometimes goes behind the other items, instead of above.
https://user-images.githubusercontent.com/7089140/144453277-a8fd5117-c6f5-48d7-860d-a525ed7ab345.mp4
On iOS, same issue happens sometimes. Moreover, sometimes the selected item only moves a few pixels and after moving my finger away from the screen, the item is still in the moved position and the next touch, everywhere in the screen, moves the previously selected item.
https://user-images.githubusercontent.com/7089140/144456590-48baac8a-4190-4c0c-9084-9e3acb8c4c7c.MP4

I don't fully understand the problem, can you post a snack? onPressIn on android seems to be working as expected in the snack I created here: https://snack.expo.dev/@computerjazz/rndfl-onpressin

I tried this sample on Real Android Device in 2 ways :
1- Run with Expo Go => Everything is working as expected.
2- Run in a bare react native project by npx react-native init  => it has issue (with or without GestureHandlerRootView)
when I want to start drag by pressing the item, the scroll of Flatlist will be started and drag state is canceled. In two condition depends on usage of GestureHandlerRootView  from react-native-gesture-handler that is described here :
without GestureHandlerRootView :
even I press item for long item, the drag state is not activated.
with GestureHandlerRootView :
when I press item for long item, the drag state has been activated, I can drag item successfully. but I want to activate drag state by onPress only.


Better commit messages

Thanks for providing a maintained alternative to chrono-english. I found this crate from https://rustsec.org/advisories/RUSTSEC-2024-0395. To make people more confident in the project, I think it needs better commit messages. Commit messages saying no more than "stuff" (649ed32) or "time" (3ae5756) should not be allowed to make it into the main branch IMO. "fix timezone support" (de3973d) is slightly better but it really should explain what was broken. The reason I noticed was that I was trying to find a commit that changed something about time zones (to figure out why my tests started failing after switching from chrono-english). See https://cbea.ms/git-commit/ for more detailed suggestions.
Thanks for considering. I hope the above doesn't sound too harsh.

I think quite the opposite actually. Such commit messages make you look into the changes and actually evaluate the code yourself.

To make people more confident in the project, I think it needs better commit messages.

This project was effectively born as a side project to rewrite and improve the code. I did rush through the commits and it wasn't originally intended to go beyond something that only I was using.

The reason I noticed was that I was trying to find a commit that changed something about time zones (to figure out why my tests started failing after switching from chrono-english).

This project is effectively a complete rewrite. I would wager that the commits would not be of value here. Could you open a new issue for this discrepancy?

I think quite the opposite actually. Such commit messages make you look into the changes and actually evaluate the code yourself.

I suspect not many people feel that way.  You can even create a git alias for git log --pretty=<something> that just shows the first line (or nothing at all) if you prefer.
Also, even if it's possible to look at the patch and figure out what it does, you lose the record of why it was done.

This project was effectively born as a side project to rewrite and improve the code. I did rush through the commits and it wasn't originally intended to go beyond something that only I was using.

That's fair. (Well, kind of :) I would still recommend including a bit more context, but I work on source control stuff, so...)

This project is effectively a complete rewrite. I would wager that the commits would not be of value here. Could you open a new issue for this discrepancy?

I filed #12 for that. Thanks.

Thanks @conradludgate for making this!
@erin-desu , there are plenty of reasons why a project might have unhelpful commit descriptions, but there's something particularly dispiriting about trying to claim that it's a good thing.
True, it's possible to write commit descriptions that would be worse than no description, but that would be a different problem. If you feel like you don't know how to write a better commit description than no description, that's a fair reason to not write them, and you are under no obligation to change that (unless you work with people for whom it's a problem and who might obligate you), but claiming that it is impossible feels like a step too far.


Consider moving src/vs/server/cli.js and src/vs/server/main.js to src/

ref https://github.com/microsoft/vscode/issues/140874
src/vs/server/cli.js and src/vs/server/main.js are entry points to vscode-server. We added them in the src/vs/server folder because that made it easier to have the server sources not be open source.
We could consider moving them to src/server-cli.js and src/server-main.js, which would better align with how the source is structured for vscode.
Thoughts or concerns @bpasero @aeschli ?

Yes, 👍

Makes sense!


Add shortcuts for fetching GitHub repositories

Usage:
Metacello new
	baseline: 'Metacello';
	githubUser: 'LinqLover' project: 'metacello' path: 'repository';
	get.

Open questions:

[ ] Should we maybe also default path to 'repository' or isn't this convention?
[x] How can I fill in the id tag in the monticello.meta/version file below manually?
[x] Should I add another test for the new convenience method?

@dalehenrich Please see the questions above, CI fails probably because of point 2 :)

CI passed on my fork, still running for this repository. @dalehenrich Sorry for paging, but it would be great if you could give me a short answer on whether you would like to see additional changes on this PR (see above) or whether this can be merged! :-)

@dalehenrich Hey, how do you think about this PR? Should we add other convenience buttons or can I just press the Merge button? :-)

sorry to have missed your earlier ping, do I read this correctly that you are changing the behavior such that the default committish is no longer 'master'? Perhaps not specifying the comittish in the url results in 'master' being defaulted elsewhere? If so then I'm comfortable with this change ... as it reduces the number of places where the default committish is hard coded ...
I have a sorta rule that behavior cannot be changed, because you never know who might depend upon that behavior and there's nothing worse than updating a project only to have things stop working ....
I think adding a test is a good idea, to "keep things honest" moving forward ...
So thumbs up and I appreciate your contributions

you are changing the behavior such that the default committish is no longer 'master'? Perhaps not specifying the comittish in the url results in 'master' being defaulted elsewhere?

Exactly, the decision about the default commitish is now totally up to GitHub. See also MC[Fetch]GitHubRepository>>projectZipUrlFor:versionString: and the GitHub API docs about the zipball/tarball endpoints.

I have a sorta rule that behavior cannot be changed, because you never know who might depend upon that behavior and there's nothing worse than updating a project only to have things stop working ....

I totally agree with this strategy in general, but if we took this literally in this example, it hypothetically might be possible that someone set up a GitHub repository with both a master and a main branch and configured the main branch as the default in the repository settings. In this case, if they did not explicitly specify the commitish, in the past, it would have fallen back to master but now to main ... But personally, I think this would be a too speculative apprehension, what do you think?

I think adding a test is a good idea, to "keep things honest" moving forward ...

On it

I totally agree with this strategy in general, but if we took this literally in this example, it hypothetically might be possible that someone set up a GitHub repository with both a master and a main branch and configured the main branch as the default in the repository settings. In this case, if they did not explicitly specify the commitish, in the past, it would have fallen back to master but now to main ... But personally, I think this would be a too speculative apprehension, what do you think?

Haha, when the underlying system changes, you have to adapt, so I am in favor of your changes ...

Alright, then we should be done! New smoke tests exist and I did not find any regressions in the CI, so I'm going to merge this now. Thanks for your support!

you are changing the behavior such that the default committish is no longer 'master'? Perhaps not specifying the comittish in the url results in 'master' being defaulted elsewhere?

Exactly, the decision about the default commitish is now totally up to GitHub. See also MC[Fetch]GitHubRepository>>projectZipUrlFor:versionString: and the GitHub API docs about the zipball/tarball endpoints.

Argh, I need to correct myself. 'master' is still hard-coded somewhere else so currently the default branch name will still be replaced by master. This is not a regression but nevertheless not so convenient ...


SASS-2050 - Removing an employment iteration.

Description
Please include a brief summary of the change you've made and the issue that it fixes.
Add a link to the relevant story in Jira
SASS-2050
Checklist PR Reviewer
Before Reviewing

[ ]  Have you pulled the branch down?
[ ]  Have you assigned yourself to the PR?
[ ]  Have you moved the task to “in review” on JIRA?
[ ]  Have you checked to ensure all dependencies are up to date?
[ ] Have you checked to ensure its been rebased against the current version of main?

Whilst Reviewing

[ ]  Have you run the journey tests?
[ ]  Have you looked at the JIRA story to make sure all Acceptance Criteria has been met?

After Reviewing

[ ] Have you checked for merge conflicts or any changes in the current main that may affect the current pull request? i.e. does it need another rebase?
the current pull request?
[ ]  Have you checked to make sure there are no builds in the pipeline before you merge?
[ ]  Have you moved the task to “in pipeline” on Jira?

[x]  Have you addressed warnings where appropriate?
[x]  Have you rebased against the current version of main?

Needs to be merged with: https://github.com/hmrc/income-tax-employment-frontend/pull/276


ARROW-9933: [Developer] Add drone as a CI provider

@kszucs I need this for https://github.com/apache/arrow/pull/8127, is there an easy way to test this?

There are no unit tests set up for crossbow yet, but you can check the rendered template by running submit with --dry-run option.
I don't think you need a separate PR for adding support for drone templates, we can just set up #8127 and test it there.


Is IdentityServer4 GDPR compliant?

Question
I don't see an official document for GDPR compliance. Is IdentityServer4 is GDPR compliant?
Is there any guidelines for the GDPR in IdentityServer4?

I think you are misunderstanding the purpose of IdentityServer. It's an OAuth/OIDC protocol implementation. All the user data handling is done by whoever implements the hosts.


IE11 support for pointer-events

IE11 does not support "pointer-events: none" for , as can be demonstrated here: http://jsfiddle.net/mqpcY/5/ (in all other browser with pointer-events support the  is not clickable, in IE11 it is)

Thanks, added as known issue.


Stops counter recursion when timer is done

When timer is done, the counter recursion is stopped, fixing bugs with the done function being called upon every "tick".

Hi @paulkass
I'm super busy for the next few days so getting some time is pretty grim.
I'm not sure what your trying to fix here - From memory the unit tests show that done only get's fired once?
Is this related to he reset issue?

Yes it is. So when the timer fires the done callback, the code that sets the interval to execute the count function again still fires. So this fix puts a flag that prevents this bug, because if the timer is done, the done callback should be called only once right?

I am hitting the same issue. +1 for the PR
Here is how to reproduce the bug I am seeing:
var Stopwatch = require("timer-stopwatch")
var time = 5000;
var timer = new Stopwatch(time, { refreshRateMS: 200 });
timer.on('time', function (time) {
    console.log(time.ms);
});

timer.on('done', function() {
    console.log('done');
    this.stop();
    this.reset(time);
    this.start();
});

timer.start();

The console will show numerous other times being spawned and counting down.

Forgot about this,Thanks @MarkHerhold for the reminder and thanks @paulkass for the pr.
Stay tuned in the next while for a bit of a re-write to make the code more efficient and much easier to follow

Awesome! @MickCrozier

On Dec 1, 2015, at 2:29 PM, Mick Crozier<EMAIL_ADDRESS>wrote:
Forgot about this,Thanks @MarkHerhold https://github.com/MarkHerhold for the reminder and thanks @paulkass https://github.com/paulkass for the pr.
Stay tuned in the next while for a bit of a re-write to make the code more efficient and much easier to follow
—
Reply to this email directly or view it on GitHub https://github.com/MickCrozier/timer-stopwatch/pull/7#issuecomment-161116932.


dsc_script does not accept a flag of type Chef::Util::Powershell::PSCredential when used with command

Description
'Invalid argument type' error is returned when the dsc_script resource is used with the 'command' property & a 'flags' property that contains a Chef::Util::Powershell::PSCredential type.
/lib/chef/util/powershell/cmdlet.rb is what is disallowing this.
There are 2 workarounds I'm aware of, both of which aren't very desirable for how I'm using chef/dsc:

Don't use a .ps1 as a command.  I prefer to keep my DSC resources in external .ps1 files that I keep in \files\default in my cookbook for portability reasons (I use these in other environments not currently being managed by chef).
Pass the userid/password as strings to flags.  For now I'm storing creds encrypted in a vault & decrypting them in my recipe, setting PSDscAllowPlainTextPassword = $true in configuration data, but this isn't secure & the password ends up appearing in the logs if dsc_script fails & in the temp mof files.

Chef Version
Chef 12.16.42
Platform Version
Tested on Server 2012R2 & Server 2016
Replication Case
Sample recipe:
creds_pso = ps_credential('domain\user', 'password')
dsc_script 'doathing' do
 command "C:\dscscripts\doathing.ps1"
 flags ({:cred => creds_pso})
 configuration_data <<-EOH
  @{
   AllNodes = @(
    @{
    NodeName = "localhost";
    PSDscAllowDomainUser = $true
    })
   }
   EOH
end

doathing.ps1:
Configuration doathing {
 param (
  [System.Management.Automation.PSCredential] $cred
 )
 Import-DscResource -ModuleName PSDesiredStateConfiguration

 Node $AllNodes.Nodename {
  Group AddDomainUserToLocalGroup {
   GroupName = 'AGroup'
   MembersToInclude = 'domain\anotheruser'
   Credential = $cred
  }
 }
}

Client Output
[2016-12-09T15:01:41-05:00] INFO: Processing dsc_script[doathing] action run (mycookbook::default line 37)
[2016-12-09T15:01:41-05:00] ERROR: DSC operation failed: Invalid argument type `Chef::Util::Powershell::PSCredential` specified for PowerShell switch `:admincreds`. Arguments to PowerShell must be of type `String`, `Numeric`, `Float`, `FalseClass`, or `TrueClass`

Stacktrace
attached
chef-stacktrace.zip
NOTE: CHEF CLIENT BUGS ONLY
This issue tracker is for the code contained within this repo -- chef-client, base knife functionality (not
plugins), chef-apply, chef-solo, chef-client -z, etc.

Server issues
ChefDK issues
Cookbook Issues (see the https://github.com/chef-cookbooks repos or search Supermarket or GitHub/Google)

You will want to use the ps_credential helper to embed a ps credential: https://docs.chef.io/resource_dsc_script.html#ps-credential-helper
Please reopen if that does not work for you!

I'm using the ps_credential helper, its the first line of the sample recipe I posted.
I haven't tested embedding a variable created by a ps_credential object into the 'code' property, as I prefer keeping my DSC in external PS1 files.


Events not firing on RN 0.39

Hey,
I'm using react-native 0.39 and no events are firing on IOS (onReady, onChangeState,...)
I didn't see any issues on it, am I the only one?
I fixed it by using sendAppEventWithName instead of sendInputEventWithName  to dispatch events from React Native to JS. Btw it seems that sendInputEventWithName is deprecated.
It might be the same issue as #108?
If anyone is having the same issue, I will do a PR ;)

same issue +1

It's duplicate of #108

@iDams i replaced sendInputEventWithName with sendAppEventWithName in Libraries > RCTYoutube.xcodeproj > RCTYoutube > RCTYoutube.m, but it still isn't working. Am i missing something?

@jonwu You also need to change the way you listen to events in YouTube.ios.js. You have to use NativeAppEventEmitter.addListener() now
You can check the changes I made on my fork:
https://github.com/iDams/react-native-youtube/commit/3eb3344bd48379b67266dcfc759aeb034010d20f#diff-20f3ec9d61e7a9aa3d583adf9e66d4ffR62
Here is the doc related: https://facebook.github.io/react-native/docs/native-modules-ios.html#sending-events-to-javascript

@iDams can you create PR with this changes?

@iDams I would love to see this commit merged, I will try to test it on an integration branch that also contains the build fix for react native 0.4.0 currently in master.

@iDams @max-mykhailenko I made an integration branch that works great for my project! 🎉  I will try to make a clean PR for you now.

@wcandillon nice! Sorry for the late responses, I didn't have time to do the PR yet.

@iDams @max-mykhailenko  ready at https://github.com/inProgress-team/react-native-youtube/pull/113. I use it in my own react native project and it works great. Thank you for such great component and for your support guys.


rubush code for  all

this code is a rubbish, very diffuiclt to run and dataset preparation is very complex.

not to run, it watse your time to go


Opportunity type = contract type, + separate "how to bid" instructions

Commodity opportunities should have separate bidding instructions. This requires a model change and new content.

[ ] change model so that opportunity type = contract type
[ ] Write instructions for "how to bid?" section for commodity i.e. bidnet submissions

Text for how to bid section:
`Submit your proposal electronically at the Pennsylvania Purchasing Group website. Hardcopies of proposals will not be accepted. Follow these directions to find the submission page for this opportunity:

From the  Pennsylvania Purchasing Group home page, click on Solicitations & Awards
Select Allegheny County - Division of Purchasing and Supplies
Select this opportunity from the list.
Click on "Send Pricing" to start your submission.

If this is your first time using the Pennsylvania Purchasing Group's site, register your business on the site in order to submit your proposal.`


The cargo maker doesn't mark warnings as warnings

Expected behavior
The cargo marker doesn't mark warnings as warnings.

Because of this let g:neomake_warning_sign won't be used.
Steps to reproduce
log file
Output from (verbose) NeomakeInfo
Neomake debug information
Async support: 1
Current filetype: rust
Windows: 0
[shell, shellcmdflag, shellslash]:['/usr/bin/fish', '-c', 0]
Enabled makers
For the current filetype ("rust", used with :Neomake):

cargo

append_file: 0
args: ['check', '--message-format=json', '--quiet']
auto_enabled: 1
cwd: '/home/maik/projects/sm'
exe: 'cargo'
process_output: function('neomake#makers#ft#rust#CargoProcessOutput')
NOTE: you can define g:neomake_rust_enabled_makers to configure it (or b:neomake_rust_enabled_makers).

Default maker settings:

output_stream: 'both'
remove_invalid_entries: 0
buffer_output: 1

For the project (used with :Neomake!):
None.
NOTE: you can define g:neomake_enabled_makers to configure it.
Settings
New-style (dict, overrides old-style)
g:neomake: {
  'automake': {
    'ignore_filetypes': ['startify'],
    'events': {
      'BufWritePost': {
        'delay': 0,
      },
    },
  },
}
b:neomake: unset

Old-style
g:neomake_error_sign = {'texthl': 'NeomakeErrorMsg', 'text': '▶'}
g:neomake_highlight_columns = 0
g:neomake_info_sign = {'texthl': 'NeomakeWarningMsg', 'text': 'W'}
g:neomake_logfile = '/tmp/neomake.log'
g:neomake_message_sign = {'texthl': 'NeomakeWarningMsg', 'text': 'W'}
g:neomake_place_signs = 1
g:neomake_warning_sign = {'texthl': 'NeomakeWarningMsg', 'text': 'W'}

makeprg=make
:version
NVIM v0.2.2
Build type: Release
LuaJIT 2.0.5
Compilation: /usr/bin/cc -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong -fno-plt -Wconversion -DNVIM_MSGPACK_HAS_FLOAT32 -DNVIM_UNIBI_HAS_VAR_FROM -O2 -DNDEBUG -DMIN_LOG_LEVEL=3 -Wall -Wextra -pedantic -Wno-unused-parameter -Wstrict-prototypes -std=gnu99 -Wimplicit-fallthrough -Wvla -fstack-protector-strong -fdiagnostics-color=auto -DINCLUDE_GENERATED_DECLARATIONS -D_GNU_SOURCE -I/build/neovim/src/build/config -I/build/neovim/src/neovim-0.2.2/src -I/usr/include -I/usr/include -I/usr/include -I/usr/include -I/usr/include -I/usr/include -I/usr/include -I/build/neovim/src/build/src/nvim/auto -I/build/neovim/src/build/include
Compiled by builduser

Features: +acl +iconv +jemalloc +tui
See ":help feature-compile"

   system vimrc file: "$VIM/sysinit.vim"
  fall-back for $VIM: "/usr/share/nvim"

Run :checkhealth for more info

:messages
"src/lib.rs" 1907L, 63158C
"src/lib.rs" 1907L, 63158C written

-->

Is your problem that marker signs don't show up at all, or that they are displayed as errors? Because the latter is my problem, and I'm wondering whether I should make a separate issue for that.

@Ploppz The second because they are not marked as warnings and I think neomake falls back to error. Also I wish I could prioritize errors over warnings.

@Ploppz
Is it about unused imports for you, too?
What cargo version are you using?

@blueyed Every warning I have seen lately. When I ran neomake in a project just now, also 'field is never used' and 'struct is never used' (there were no more warnings).
cargo version: cargo 0.26.0 (41480f5cc 2018-02-26).
Active toolchain:
stable-x86_64-unknown-linux-gnu (default)
rustc 1.25.0 (84203cac6 2018-03-25)

Same issue here. Warnings are displayed as errors

Same problem here: every warning produced by cargo check is displayed as an error.  The output of cargo check --message=format=json in this case can be found here:  cargo.txt

I found the reason for this problem: neomake#makers#ft#rust#CargoProcessOutput use decoded['message']['code']['code'][0] as error.type.
Here is part of a warning, the error.type for this will be 'u':
{
    "reason": "compiler-message",
    "package_id": "rust-test 0.1.0 (path+file:///Users/luffbee/code/rust-test)",
    "message": {
        "message": "unused `std::result::Result` that must be used",
        "code": {
            "code": "unused_must_use",
            "explanation": null
        },
        "level": "warning",
    }
}

@Luffbee
Thanks for the info.  Can you provide the full output (for a test), please?
(The previous comment has something in this regard already though, but just for completeness)

I pasted it here https://paste.ubuntu.com/p/pKRdt2zZwT/. @blueyed

@Luffbee
Went ahead and merged it - sorry for doing a PR already in parallel, and thanks again for providing a fix yourself.. :v:


Swift 2.0

Switch to Swift 2.0. Main changes are documentation and errors.
Would recommending making Swift 2.0 a separate branch until the GM seed.

Thanks for the pull request, Ross. I will be making a separate swift-2.0 branch and will be doing some refactoring to use some of the new Swift goodness.
Until Xcode gives us a way to generate first-class, stand-alone API documentation, I'm going to leave the documentation as-is, however; I'm using jazzy to generate the API documentation which takes a slightly different format. Or perhaps jazzy will be updated to use Xcode's new format, in which case I'll update these docs then.

FYI, the swift-2.0 branch is now available in this repo. It also automatically pulls in the swift-2.0 version of CleanroomASL.

👍

Closing this pull request now that Swift 2.0 support is provided as of the 1.4.x release line.


#MongoDB Tasks. Ilya Maylychko

https://travis-ci.org/github/juggler39/db-assignments/builds/716155381

Good work, the PR is accepted!


Scrape lobbyist data nightly

Add lobbyist data to the nightly scrape.

We're scraping independent expenditures nightly now thanks to #27. Is lobbyist_employer.csv the only other lobbyist file we need to scrape nightly?

Both lobbyist employer and lobbyist (if we aren't already pulling it nightly) @antidipyramid

Now that #34 is in, once the first nightly scrapes are in, I'll add downloads to the site like datamade/openness-project-nmid#211.

Lobbyist + lobbyist employer downloads have been added.


conda still installs 0.2.9

I am trying to install EPIC on an Ubuntu 16.04 using MiniConda and the conda method described in the README, and it seems it's pulling version 0.2.9.
Is there a conda-aware way of installing the newer 0.2.11 version, which seems important given the speed-up in the Changelog:
# 0.2.11 (01.08.18)
- Massive speedup with Cython
- Fix bugs added by 0.2.10

No, not yet. You can do pip install bioepic though :)
I'll get around to it eventually.
On Wed, Aug 22, 2018 at 11:31 AM Albert Vilella<EMAIL_ADDRESS>wrote:

I am trying to install EPIC on an Ubuntu 16.04 using MiniConda and the
conda method described in the README, and it seems it's pulling version
0.2.9.
Is there a conda-aware way of installing the newer 0.2.11 version, which
seems important given the speed-up in the Changelog:
0.2.11 (01.08.18)

Massive speedup with Cython
Fix bugs added by 0.2.10

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/biocore-ntnu/epic/issues/84, or mute the thread
https://github.com/notifications/unsubscribe-auth/AQ9I0hwFYV5ZDRwffg3E_JEn3mDF6d7jks5uTSUKgaJpZM4WHTxn
.

Thanks for reporting btw. I am presenting a poster at Genome Informatics in your neck of the woods in two weeks. If you are going I'd love to hear what you use epic for.

Added a PR: https://github.com/bioconda/bioconda-recipes/pull/10605
Will not be able to merge until tomorrow.

It seems like there is a build error in the PR. Trying again.
Ps. It is the "Clustering bins into islands." part which is affected by the
speedup. Has gone from taking a minute to less than a second on my data.
On Thu, Aug 23, 2018 at 9:20 AM Endre Bakken Stovner<EMAIL_ADDRESS>wrote:

I am happy to hear it.
The algorithm could be even faster/less mem-consuming if I did not store
much of the raw data to produce bigwigs/matrixes in the end.
On Wed, Aug 22, 2018 at 5:24 PM Albert Vilella<EMAIL_ADDRESS>wrote:

Thanks, we currently use EPIC as a complement of MACS2, for data that
looks
relatively narrow in peak shape but that has some areas were the peaks are
wider than, say, TFBS data.
EPIC is useful for us to give us an orthogonal set of peaks compared to
MACS2 narrow peaksets. You emailed with my colleague Louella a few days
ago
about our use case.
We use it on pairs of bams that have about 50M read pairs before
deduplication. We do this on cloud instances (DNAnexus), where we pay for
the instance type (memory/cpus) and where we pay for every second of
usage.
So if we can build the new version in a miniconda folder, tar.gz it, give
it to DNAnexus, test it and confirm that the newer version of EPIC gives
us
the same results but faster, it's an important time/cost consideration
that
makes us happy users of the software.
On Wed, Aug 22, 2018 at 2:09 PM, Endre Bakken Stovner <
<EMAIL_ADDRESS>wrote:

Added a PR: bioconda/bioconda-recipes#10605
https://github.com/bioconda/bioconda-recipes/pull/10605
Will not be able to merge until tomorrow.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://github.com/biocore-ntnu/epic/issues/84#issuecomment-415025699
,
or mute the thread
<
https://github.com/notifications/unsubscribe-auth/AAJpN6l4aiwlOtrnSqvXNAvXHOKFwtsNks5uTVf_gaJpZM4WHTxn
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/biocore-ntnu/epic/issues/84#issuecomment-415072131,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AQ9I0jR4Etm3ROcWaCswGorb_ornbcArks5uTXfJgaJpZM4WHTxn
.

Bioconda update now hinges on sb helping me with this: https://github.com/bioconda/bioconda-recipes/issues/10636

I was just able to update it to 0.2.12. Finding enriched islands now is down from a minute to a fraction of a second on my large datasets.

Feel free to reopen if it does not work :)

Just reporting back that I managed to build epic 0.2.12 via conda on an Ubuntu 16.04 workstation, create a .tar.gz of the whole miniconda2 folder, then transfer to a DNAnexus instance, build an app and execute. It completed successfully.


rename 6to5 to Babel

6to5 was recently renamed to Babel: https://github.com/babel/babel/issues/780
Note there is also a reference update list which we're listed under, this would take care of that :smile:

Won't this break existing usage if merged? I would think accord should have both 6to5 and babel simultaneously in order to maintain backwards compatibility for existing users

Technically yes, but considering 6to5 is officially babel (4.0.x has been released) it's already breaking everything using it

Not if people have pinned any version below 4.0 of 6to5. Or is the 6to5 package also being completely unpublished and babel released with all previous 6to5 versions?

Well if people are using anything below Babel 4.0 they could just lock Accord to 0.14.4 as well, I believe 6to5 will remain on npm for people using it... Otherwise it's just gonna become old and most people will upgrade or use Babel in the future

This is always the problem with these wrapper packages. Should accord increment the major version or not. I've had exactly the same dilemma in some other convenience wrapper tools. Anyway, now the potential problem has been highlighted. I just wanted to make sure this wasn't merged in without giving it a second thought

fixed in f78a6f136bcb10358f8ce543dd64dc325fed1cd3

Ah sorry didn't see this earlier! But yeah @Munter I agree, still trying to think about how to handle breaking changes. It's a pretty tough issue. For now we are just moving forward with the latest versions of everything...


Add hive 4.0 image

Build custom hive4 image with access to S3 by using plain apache hive4 image. Plain hive image offers an advantage of not having to tweak multiple configuration. However, currently created image doesn't include yarn services which will be required to run queries concurrently. We may need to build a new image to accommodate yarn services as we run different tests using Hive4.

Add appropriate description explaining why do we need to customize the vanilla apache hive 4 docker image.

@hashhar thanks for offering to take care of arm build. Would you please mergethis PR?

@mayankvadariya Could you fix Polaris failure? Otherwise, we can't release a new version.

@mayankvadariya Could you fix Polaris failure? Otherwise, we can't release a new version.

@ebyhr created https://github.com/trinodb/docker-images/pull/219. Please review.

Running a release workflow: https://github.com/trinodb/docker-images/actions/runs/12289019120


[P] spark_install uses cdh4 as default

Run spark_install(spark_version = "1.6.2"), currently CDH4 is installed; however, latest Hadoop version should be preffered.
See: https://github.com/rstudio/spark-install/blob/master/R/R/versions.R#L121-L125

Hi @javierluraschi - do you just want me to fix this to use Spark 2.1.1/Hadoop 2.7? That's the default based on versions.json

@drdarshan Up to you, not sure home much use the python installer is getting.


GPIO callback disable has no effect due to _gpio_fire_callbacks

Function _gpio_fire_callbacks triggers callbacks for pins present in mask passed as an argument.
This infrastructure will not work correctly when application disables callbacks for multiple pins from a currently handled callback.
E.g.
4 pin callbacks are registered (A...D). Let's assume 2 are fired (A and B) at the same time.
Interrupt handler is triggered in driver code. It sets bits corresponding for these two pins in the variable passed as an argument to _gpio_fire_callbacks and call the function.
As there are two pins callback will be triggered twice (once for pin A and second time for pin B).
The application gets first call (for pin A). In this call the application callback code disables callbacks for  all pins A...D. Application expects no more callbacks for any of the pins.
As _gpio_fire_callbacks is still in the loop, after first callback is done, it will trigger second callback for pin B. This happens even-though this callback was disabled.

We are still hit by this...

Fixing this is not trivial really. We changed the application to have one callback for all pins we use. This should do the trick.
I still believe it should be fixed but we will not be affected anymore. If somebody else is hit by that they can do what we did.


ConvertNotebookPreprocessor should take input_files

https://github.com/kubeflow/fairing/blob/08c81437fd9ed720cf4b780e25097fef9fa16cd6/fairing/preprocessors/converted_notebook.py#L28
Should ConvertNotebookPreprocessor currently take input_files as an argument?
I think as a work around you can just set input_files after constructing the preprocessor.

I think we also need to override the files returned
https://github.com/kubeflow/fairing/blob/08c81437fd9ed720cf4b780e25097fef9fa16cd6/fairing/preprocessors/converted_notebook.py#L57

Here's the preprocessor I created for my kubecon demos.
https://github.com/jlewi/kubecon-demo/blob/master/fairing_util.py
Should we get that checked into fairing?


This is not working with ionic 3.6.1

This is a very lovely work, but it doesn't seem to work with ionic 3.
This is the sample code
<virtual-scroll [items]="items" (update)="viewPortItems = $event">
<list-item *ngFor="let item of viewPortItems" [item]="item">

The  is causing error of unknown element in ionic and when i changed to  and excluding [item]="item" am just getting a blank list.
For what its worth. am using lazy loading of Components
Any help would be appreciated.
Thx

Not sure about that specific issue, but I don't think it is Ionic related, I use it with no problems at all.
Try removing [item]="item" from the list item (don't think it should be there), and try adding the [childHeight] property to the list. Missing that property could make the list appear blank.

Thanks for the reply.. I appreciate..
I did as you instructed. I added [childHeight] and also used  inside  here is the error i got.
Runtime Error Uncaught (in promise): Error: Template parse errors: 'list-item' is not a known element: 1. If 'list-item' is an Angular component, then verify that it is part of this module. 2. If 'list-item' is a Web Component then add 'CUSTOM_ELEMENTS_SCHEMA' to the<EMAIL_ADDRESS>of this component to suppress this message. ("tems]="items" (update)="viewPortItems = $event" [childWidth]="80" [childHeight]="230"> [ERROR ->]<list-item *ngFor="let item of viewPortItems; let i = index"> <ion-row ngClass="feed-content"):
And if i change  to  it would just show and empty list.
Ionic virtual scroll works *ngFor works, but ofcourse ionic virtual scroll is too buggy and *ngFor is not good for very long list..
So am kind of suspecting this piece doesn't not support Lazy Loading.

Please i still need help with this anyone at home?

do you have a component called "list-item"?

I finally implemented list-item element and the error message disappeared.
Thanks

@abel672 did you add to virtual-scroll a height style?
For example, in your ionic page.scss you should add something like this:
virtual-scroll {
       display: block;
       width: 100%;
       height: 700px;
   }

Posted my solution here :  #85

Closing. It appears the issue was due to incorrect usage of virtual-scorll & was resolved by the feedback given by other users. If the issue persists, please create a stackblitz to help with troubleshooting & re-open the issue. Thanks.


noopener alone not allowed

Hi,
I've been reading the discussion surrounding noopener / noreferrer, including what was done in #2043.
However, I still find the behaviour strange.
Here is my link:
Link
I'm getting a warning:
Using target="_blank" without rel="noreferrer" is a security risk: see https://html.spec.whatwg.org/multipage/links.html#link-type-noopener  react/jsx-no-target-blank
The html spec link redirects me to noopener documentation, and yet it is still requiring me to add noreferrer. As far as I understand, the use or noreferrer or noopener removes the security risk, so the rule should not be triggered if one of them is present (no matter which). In this case, since I'm using noopener (thus removing the security risk), the warning should not be shown, imho.
Why don't I use noreferrer? I think it's important for websites to know where their traffic is coming from, so I don't intend on hiding the referrer, and I don't think you should either. The referrer information helps bloggers and independent content creators properly monitor the traffic arriving to their websites.

See https://github.com/yannickcr/eslint-plugin-react/issues/2022#issuecomment-432032005:

Due to the fact that noreferrer predates noopener, there are cases where noopener is ignored (because the behavior is not implemented).

That information also violates the privacy of the user, and I don't think your opinion is the common one here about what people should do - referrers aren't reliable and anyone relying on that info is getting a very incomplete picture, no matter what you choose to do. You are welcome to disable the rule, of course.

Hi @ljharb,
I've read a lot of comments related to this here in the project, and it's not always obvious if the comments are referring to the use of noopener isolated, or in conjunction with noreferrer, like noreferrer noopener. That issue was initially opened because the linter was requiring both noreferrer noopener, which is not really needed since noreferrer implies noopener.
At the time, you even had an opinion which is compatible with mine: https://github.com/yannickcr/eslint-plugin-react/issues/2022#issuecomment-624339760:

Given that, it seems we should modify the rule - by default, even - to no longer require both (but, to continue to allow both).

I agree with this. Both noopener and noreferrer address the security constraint, so strictly speaking I don't think the rule should complain that the code is insecure if we are already using noopener. In other words, the rule should be satisfied with the use of noopener or noreferrer since, in modern browsers, this is enough to guarantee there is no security issue. Once again, I even highlight the fact that the rule mentions the use of noreferrer, but then the html.spec link is pointing to the noopener section of the page.
As for the privacy of the users, to be honest I think that is up for the developer and/or user to decide, together with the specific legal framework observed by the website owners. But even if that is up for discussion, I just don't think the rule is correct in saying there is a security risk even when noopener is being used.

The risk is as highlighted/referenced in my previous comment - that noopener isn't supported in as many browsers as noreferrer.

The thing is: this rule only applies to target="_blank" links.
If we really consider the Referer header to be dangerous (which it can be), then all external links should include noreferrer, regardless of target="_blank". If it's just the opener reference, then noopener on target="_blank" is enough.
However I understand that noopener is not supported on IE and if noreferrer has the same effect, then that is a good reason to still enforce noreferrer as a general precaution.
But I think the lint message should tell that noreferrer implies noopener and maybe even that it should be preferred because of wider support, as it currently only references noopener.
While looking though the source, I found that it's possible to set "allowReferrer": true which then will allow noopener, which might interest you @mauro1855.
{
  "extends": ["next", "next/core-web-vitals"],
  "rules": {
    "react/jsx-no-target-blank": ["error", {"allowReferrer": true}]
  }
}

While looking that up, I found that over the last 2 years, browsers started to imply noopener, which is nice.
There is also the much more granular Referrer-Policy header that can take care of it.
That header can even reduce the Referer to only include the Origin, which I really like as it can still give another server admin some idea where traffic is roughly coming from without potentially exposing url parameters.

@Nemo64 i'd be happy to review a PR that improves the error message, and points users to where they can read more about the nuance.


Bug: admin user new message push over

New message alert failed for admin user
Point to point session of admin user, APP interface will not be reminded of new messages

pnr_msgcache_dbinsert_v3<PHONE_NUMBER>]msg cache repeat, no add
there is a bug when user unread msgs over 10，the cache list over


[11.x] Fix handling exceptions thrown in eval()'d code

This fix issue #53203

What is the behavior after this fix?

Hello @taylorotwell, here is the error screen after this fix:


Improved spacing and color scheme of search

In continuation with #285, here are some improvements for how search looks.

I just merged #374, which seems to have a few conflicting changes.

@SpaceK33z  I've rebased with the latest develop branch. What happened to the search button?

@pastelsky gone? you might have to run an npm install to pick up the new loaders...

LGTM 👍


CLI: Implement color theme

To ensure the kusk theme will  be legible regardless of users terminal theme use foreground color as selected text.
See:
https://gookit.github.io/color/#/?id=cli-color
Implement theme as per Kusk CLI design:
https://www.figma.com/file/EkNk9tMEoAgYrwGP7N1dPm/Kusk-CLI?node-id=0%3A1

Deploy:

Deploy + watch


[TokenContract Review] Early exit on same sender and receiver

Issue:
[TokenContract Review] Early exit on same sender and receiver
Severity:
Minor
Description:
Check if recipient and sender are not same in execute_transfer to avoid unnecessary execution and early exit.
File Name:
contracts/token-contracts/cw-hub-bnusd/src/contract.rs Line No. 97

This is a built in function, id say we shouldn't change the standard behavior.