⚠ Bofrost.de has degraded performance

In d243da0, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1325 ms

Resolved: Bofrost.de performance has improved in d6eba41.


XrResult failure [XR_ERROR_PATH_UNSUPPORTED]

When running the BasicXrApp on the HP Reverb G2 an exception is raised:
  ERROR (OpenXR) : [xrSuggestInteractionProfileBindings] Suggested binding '/user/hand/right/input/trigger/value' is not supported by interaction profile '/interaction_profiles/hp/mixed_reality_controller'.
  Ausnahme ausgelöst bei 0x00007FFFD9624ED9 in BasicXrApp_win32.exe: Microsoft C++-Ausnahme: msxr::XrResultException bei Speicherort 0x000000D5D54FE268.
  Ausnahme ausgelöst bei 0x00007FFFD9624ED9 in BasicXrApp_win32.exe: Microsoft C++-Ausnahme: std::logic_error bei Speicherort 0x000000D5D54FE940.

I commented out the following block, then the application works:
            if (m_optionalExtensions.HPMRControllerSupported)
            {
                std::vector<XrActionSuggestedBinding> bindings;
                bindings.push_back({m_placeAction.Get(), GetXrPath("/user/hand/right/input/trigger/value")});
                bindings.push_back({m_placeAction.Get(), GetXrPath("/user/hand/left/input/trigger/value")});
                bindings.push_back({m_poseAction.Get(), GetXrPath("/user/hand/right/input/grip/pose")});
                bindings.push_back({m_poseAction.Get(), GetXrPath("/user/hand/left/input/grip/pose")});
                bindings.push_back({m_vibrateAction.Get(), GetXrPath("/user/hand/right/output/haptic")});
                bindings.push_back({m_vibrateAction.Get(), GetXrPath("/user/hand/left/output/haptic")});
                bindings.push_back({m_exitAction.Get(), GetXrPath("/user/hand/right/input/squeeze/value")});
                bindings.push_back({m_exitAction.Get(), GetXrPath("/user/hand/left/input/squeeze/value")});

                XrInteractionProfileSuggestedBinding suggestedBindings{XR_TYPE_INTERACTION_PROFILE_SUGGESTED_BINDING};
                suggestedBindings.interactionProfile = GetXrPath("/interaction_profiles/hp/mixed_reality_controller");
                suggestedBindings.suggestedBindings = bindings.data();
                suggestedBindings.countSuggestedBindings = (uint32_t)bindings.size();
                CHECK_XRCMD(xrSuggestInteractionProfileBindings(m_instance.Get(), &suggestedBindings));
            }

            // Set up suggested bindings for the microsoft/hand_interaction profile.
            if (m_optionalExtensions.MsftHandInteractionSupported)
            {
                std::vector<XrActionSuggestedBinding> bindings;
                bindings.push_back({m_placeAction.Get(), GetXrPath("/user/hand/right/input/select/value")});
                bindings.push_back({m_placeAction.Get(), GetXrPath("/user/hand/left/input/select/value")});
                bindings.push_back({m_poseAction.Get(), GetXrPath("/user/hand/right/input/grip/pose")});
                bindings.push_back({m_poseAction.Get(), GetXrPath("/user/hand/left/input/grip/pose")});
                bindings.push_back({m_exitAction.Get(), GetXrPath("/user/hand/right/input/squeeze/value")});
                bindings.push_back({m_exitAction.Get(), GetXrPath("/user/hand/left/input/squeeze/value")});

                XrInteractionProfileSuggestedBinding suggestedBindings{XR_TYPE_INTERACTION_PROFILE_SUGGESTED_BINDING};
                suggestedBindings.interactionProfile = GetXrPath("/interaction_profiles/microsoft/hand_interaction");
                suggestedBindings.suggestedBindings = bindings.data();
                suggestedBindings.countSuggestedBindings = (uint32_t)bindings.size();
                CHECK_XRCMD(xrSuggestInteractionProfileBindings(m_instance.Get(), &suggestedBindings));
            }

Are these controls supposed to be supported by the HP Reverb G2? In case not, the code should check for the device and probably not call the functions.

There's a fix recently addressed this problem in our 108 runtime release.   Could you please try the 108 preview runtime to see if this works here?

The sample code here were correct.  It was our API runtime didn't behave correctly when the user doesn't have any G2 controller turned on when launching the app.  The mentioned fix above is to address this issue.

I confirm, the fix works for me. Thanks!


ProblemSolver create method

Problem
There is an incompatibility between the ubuntu-12.04 and ubuntu-14.04 versions:

In Ubuntu-12.04 version: in class, hpp::core::ProblemSolver, "create" member function does not exist and the constructor is public
In Ubuntu-14.04 version: the member function "create" exists and the constructor is protected.

This means that package with a dependency to hpp-core needs 2 versions, for a very tiny issue.
Possible fix

Let the constructor "public with a warning.
Put the method create also in 12.04 version.

Thank you for reporting this issue.
The rationale is the following

ubuntu-12.04 branches are frozen to a working version compatible all across the various packages,
master is a stable version working under ubuntu-14.04,
devel is the development branch with latest modifications, but with possible temporary compatibility loss between packages.
ubuntu-14.04 is a deprecated branch that should disappear.
Does this clarify the issue ?
Of course the rationale exposed above can be suject to discussion.


Make unable to create workflowteam with OrgAdmin role

Purpose
ROLE_ORGANIZATION_ADMIN cannot be use as WorkflowTeams role.
Approach
Validation added to check WorkFlowTeam.role is not  ROLE_ORGANIZATION_ADMIN.
_Related ticket: #1075

Coverage increased (+0.04%) to 49.9% when pulling 4905fccb07bcc98e25df3914b8f2340d564e3ca6 on yilmazbekdemir:prevent-role-organization-admin-on-workflowteam into 31a046acc40b319d7e33f9fb7776ba48f0b62c62 on toladata:dev.


Evolved Enderman causing overlay effect on items

If you look at one EvoEnderman while items or XP orbs are around, these items and orbs overlay become opaque. It can be better seen on the screenshot.
https://imgur.com/X2LBMqz
I like the current EvoEnderman effect, if to fix it you might have to change it, then I would prefer to keep it as it is.
Minecraft 1.12.2 - Single Player
Forge <IP_ADDRESS>17
Enderman Evolution 1.0.9

eh..i don't feel like forgetting..i pushed to curse..everyone can deal with it lol


Adding script to create powervs cluster in either lon,tok,mon or syd

@gitsridhar Made changes to the script to perform end to end operation right from creating OCP by selecting the region automatically,  deploying ODF and then running tier tests. Please let me know if you have any other suggestions


OracleDatabase 19.3.0 ERROR [stage-2 2/3]  11/17  orainstRoot.sh: No such file or directory given enough storage

Hello, when execute  sudo ./buildContainerImage.sh -v 19.3.0 -e, during the execution of the creation of the image...
> [stage-2 2/3] RUN /opt/oracle/oraInventory/orainstRoot.sh &&     /opt/oracle/product/19c/dbhome_1/root.sh:                                                                                #13 0.925 /bin/sh: /opt/oracle/oraInventory/orainstRoot.sh: No such file or directory
I'm not sure if it might due to insufficient space because it seems the storage is more than enough.
/ # df -B 1G / Filesystem           1G-blocks      Used Available Use% Mounted on overlay                    126        70        49  59% /

Please take a look at this @Mahi0911

Your build has not created all files with necessary permissions . Run the build again .
Also , can you  run " df -B 1G / " inside the container and post the output, please?

/ # df -B 1G / Filesystem 1G-blocks Used Available Use% Mounted on overlay 126 70 49 59% /

/ # df -B 1G / Filesystem 1G-blocks Used Available Use% Mounted on overlay
126       70        49             59% /

could you please post the docker file you are using @tsvirs

I mean "Dockerfile"
OracleDatabase/SingleInstance/dockerfiles/19.3.0/Dockerfile

LICENSE UPL 1.0

Copyright (c) 2018, 2020 Oracle and/or its affiliates.

ORACLE DOCKERFILES PROJECT
--------------------------
This is the Dockerfile for Oracle Database 19c

REQUIRED FILES TO BUILD THIS IMAGE
----------------------------------
(1) db_home.zip
Download Oracle Database 19c Enterprise Edition or Standard Edition 2 for Linux x64
from http://www.oracle.com/technetwork/database/enterprise-edition/downloads/index.html

HOW TO BUILD THIS IMAGE
-----------------------
Put all downloaded files in the same directory as this Dockerfile
Run:
$ docker build -t oracle/database:19.3.0-${EDITION} .

Pull base image
---------------
FROM oraclelinux:7-slim as base
Labels
------
LABEL "provider"="Oracle"
"issues"="https://github.com/oracle/docker-images/issues"
"volume.data"="/opt/oracle/oradata"
"volume.setup.location1"="/opt/oracle/scripts/setup"
"volume.setup.location2"="/docker-entrypoint-initdb.d/setup"
"volume.startup.location1"="/opt/oracle/scripts/startup"
"volume.startup.location2"="/docker-entrypoint-initdb.d/startup"
"port.listener"="1521"
"port.oemexpress"="5500"
Argument to control removal of components not needed after db software installation
ARG SLIMMING=true
Environment variables required for this build (do NOT change)
-------------------------------------------------------------
ENV ORACLE_BASE=/opt/oracle
ORACLE_HOME=/opt/oracle/product/19c/dbhome_1
INSTALL_DIR=/opt/install
INSTALL_FILE_1="LINUX.X64_193000_db_home.zip"
INSTALL_RSP="db_inst.rsp"
CONFIG_RSP="dbca.rsp.tmpl"
PWD_FILE="setPassword.sh"
RUN_FILE="runOracle.sh"
START_FILE="startDB.sh"
CREATE_DB_FILE="createDB.sh"
SETUP_LINUX_FILE="setupLinuxEnv.sh"
CHECK_SPACE_FILE="checkSpace.sh"
CHECK_DB_FILE="checkDBStatus.sh"
USER_SCRIPTS_FILE="runUserScripts.sh"
INSTALL_DB_BINARIES_FILE="installDBBinaries.sh"
RELINK_BINARY_FILE="relinkOracleBinary.sh"
SLIMMING=$SLIMMING
Use second ENV so that variable get substituted
ENV PATH=$ORACLE_HOME/bin:$ORACLE_HOME/OPatch/:/usr/sbin:$PATH
LD_LIBRARY_PATH=$ORACLE_HOME/lib:/usr/lib
CLASSPATH=$ORACLE_HOME/jlib:$ORACLE_HOME/rdbms/jlib
Copy files needed during both installation and runtime
-------------
COPY $SETUP_LINUX_FILE $CHECK_SPACE_FILE $INSTALL_DIR/
COPY $RUN_FILE $START_FILE $CREATE_DB_FILE $CONFIG_RSP $PWD_FILE $CHECK_DB_FILE $USER_SCRIPTS_FILE $RELINK_BINARY_FILE $ORACLE_BASE/
RUN chmod ug+x $INSTALL_DIR/*.sh &&
sync &&
$INSTALL_DIR/$CHECK_SPACE_FILE &&
$INSTALL_DIR/$SETUP_LINUX_FILE &&
rm -rf $INSTALL_DIR
#############################################
-------------------------------------------
Start new stage for installing the database
-------------------------------------------
#############################################
FROM base AS builder
ARG DB_EDITION
Copy DB install file
COPY --chown=oracle:dba $INSTALL_FILE_1 $INSTALL_RSP $INSTALL_DB_BINARIES_FILE $INSTALL_DIR/
Install DB software binaries
USER oracle
RUN chmod ug+x $INSTALL_DIR/*.sh &&
sync &&
$INSTALL_DIR/$INSTALL_DB_BINARIES_FILE $DB_EDITION
#############################################
-------------------------------------------
Start new layer for database runtime
-------------------------------------------
#############################################
FROM base
USER oracle
COPY --chown=oracle:dba --from=builder $ORACLE_BASE $ORACLE_BASE
USER root
RUN $ORACLE_BASE/oraInventory/orainstRoot.sh &&
$ORACLE_HOME/root.sh
USER oracle
WORKDIR /home/oracle
HEALTHCHECK --interval=1m --start-period=5m
CMD "$ORACLE_BASE/$CHECK_DB_FILE" >/dev/null || exit 1
Define default command to start Oracle Database.
CMD exec $ORACLE_BASE/$RUN_FILE

Dockerfile

Dockerfile.zip

Still, no idea how to get through it.

it should not have happened on a clean install. The orainstRoot.sh script is only not created if an oraInventory is already present.
Is there any cached/dangling image ?

=> [builder 2/2] RUN chmod ug+x /opt/install/*.sh &&     sync &&     /opt/install/installDBBinaries.sh ee                      85.7s
=> [stage-2 1/3] COPY --chown=oracle:dba --from=builder /opt/oracle /opt/oracle                                               100.7s
=> ERROR [stage-2 2/3] RUN /opt/oracle/oraInventory/orainstRoot.sh &&     /opt/oracle/product/19c/dbhome_1/root.sh
Would you think it might be a permission problem? Because when in [stage-2 1/3], there were not any /opt/oracle directories have been created in my /opt/  .

$ docker builder prune
This removes build cache . Run this command and try building the image again

WARNING! This will remove all dangling build cache. Are you sure you want to continue? [y/N] y
Deleted build cache objects:
Total reclaimed space: 87.99GB
=> [builder 2/2] RUN chmod ug+x /opt/install/*.sh &&     sync &&     /opt/install/installDBBinaries.sh ee                                                                      70.5s
=> [stage-2 1/3] COPY --chown=oracle:dba --from=builder /opt/oracle /opt/oracle                                                                                65.1s
=> ERROR [stage-2 2/3] RUN /opt/oracle/oraInventory/orainstRoot.sh &&     /opt/oracle/product/19c/dbhome_1/root.sh                                                              0.8s

=> ERROR [stage-2 2/3] RUN /opt/oracle/oraInventory/orainstRoot.sh &&     /opt/oracle/product/19c/dbhome_1/root.sh                                                              0.8s

[stage-2 2/3] RUN /opt/oracle/oraInventory/orainstRoot.sh &&     /opt/oracle/product/19c/dbhome_1/root.sh:
#13 0.715 /bin/sh: /opt/oracle/oraInventory/orainstRoot.sh: No such file or directory

executor failed running [/bin/sh -c $ORACLE_BASE/oraInventory/orainstRoot.sh &&     $ORACLE_HOME/root.sh]: exit code: 127
ERROR: Oracle Database container image was NOT successfully created.
ERROR: Check the output and correct any reported problems with the build operation.

Are you available for a call on zoom ?

check the size of  " LINUX.X64_193000_db_home.zip " file and make sure the file is properly downloaded .
could you post the md5 sum .

Same here.
The file's checksum seems alright:
$ sha256sum dockerfiles/19.3.0/LINUX.X64_193000_db_home.zip
ba8329c757133da313ed3b6d7f86c5ac42cd9970a28bf2e6233f3235233aa8d8  dockerfiles/19.3.0/LINUX.X64_193000_db_home.zip

It does seem like the installer crashes:
+ /opt/oracle/product/19c/dbhome_1/runInstaller -silent -force -waitforcompletion -responsefile /opt/install/db_inst.rsp -ignorePrereqFailure
Launching Oracle Database Setup Wizard...

[FATAL] [INS-32038] The operating system group (dba), specified for central inventory (oraInventory) ownership, is invalid.
   CAUSE: The user performing the installation (oracle) is not a member of the operating system group (dba).
   ACTION: Specify an operating system group that the installing user (oracle) is a member of. All the members of this operating system group will have write permission to the central inventory directory (oraInventory).
[WARNING] [INS-32055] The Central Inventory is located in the Oracle base.
   ACTION: Oracle recommends placing this Central Inventory in a location outside the Oracle base directory.

Here's the log of the build attempt: ./buildContainerImage.sh -e -v 19.3.0 2>&1 | tee build.log
build.log.gz
Changes against d648e8a915da1a72983c6dcbfd6280e81bb42762 to get more info from the installer and force it to use a larger volume (--tmpdir / TMPDIR):
localchanges.diff.gz

I'm having the same issue.

I had the same problem.
I used podman instead of docker and ran buildContainerImage.sh as a non-root user.
However, when I ran buildContainerImage.sh as root user, it terminated normally.

Cleared docker image cache as above.
Disabled Safari unzipping or "opening" downloads automatically.
Downloaded the zip file again
it worked with ./buildContainerImage.sh -v 19.3.0 -s

Re-zipping the folder after Safari unzipped it automatically broke it for me with this issue.
Not sure if it helps someone else on macOS or might help troubleshoot underlying issue.

@tsvirs  I am unable to reproduce this. This happens mostly because of the corrupted LINUX.X64_193000_db_home.zip. Please download this zip file again from the OTN. The buildContainerImage.sh script does the md5 checksum verification of the zip file automatically. The sample command is as follows:
./buildContainerImage.sh -e -v 19.3.0
Please update if the same problem persists. Thanks.

Closing this issue for now. Please reopen if this issue is encountered again.


Muon features

This is a new PR with basically the same features as in #171, please refer to there for the first results tested on LST Mono MC data.
This only adds more docs and moved the functions to the image module.
We now have to methods to perform the kundu_chaudhuri fit and two to estimate optical efficiency.

Hi Max,
I already merged your pull request so that your code is in the branch; however, you will need to modify your code slightly into a format consistent with the base classes "intensity_fitter.py" and "ring_fitter.py". Parameter outputs of the ring and intensity fitting procedures should fill the "MuonRingParameter" and "MuonIntensityParameter" container classes in io/containers.py
This is due to the efforts last week to ensure that all muon algorithms developed can be tested in a common way within the muonmaster branch, before we decide what should be merged to the master branch. There will be an email soon explaining all this.
Thanks!

I do not think that code related stuff should be discussed in emails.
You should create an issue and give it the 'Muon' label.

I think you misunderstood - the email is for the cta muon mailing list, as information for all muon code developers, informing them how this will take place. All specific code discussions will of course take place on github.

Ah, OK. Perfect.


Missing abstracts in dataset

There are some missing abstracts in the dataset. Is this a dataset collection issue or an issue with the released dataset?
Example where @cite_0 is missing abstract field
{
'aid': 'cs9903008',
'mid': '2949261815',
'abstract': "Recent technological advances have made it possible to build real-time, interactive spoken dialogue systems for a wide variety of applications. However, when users do not respect the limitations of such systems, performance typically degrades. Although users differ with respect to their knowledge of system limitations, and although different dialogue strategies make system limitations more apparent to users, most current systems do not try to improve performance by adapting dialogue behavior to individual users. This paper presents an empirical evaluation of TOOT, an adaptable spoken dialogue system for retrieving train schedules on the web. We conduct an experiment in which 20 users carry out 4 tasks with both adaptable and non-adaptable versions of TOOT, resulting in a corpus of 80 dialogues. The values for a wide range of evaluation measures are then extracted from this corpus. Our results show that adaptable TOOT generally outperforms non-adaptable TOOT, and that the utility of adaptation depends on TOOT's initial dialogue strategies.",
'related_work': "In the area of spoken dialogue, @cite_2 has proposed a method for adapting initiative in form-filling dialogues. Whenever the system rejects a user's utterance, the system takes more initiative; whenever the user gives an over-informative answer, the system yields some initiative. While this method has the potential of being automated, the method has been neither fully implemented nor empirically evaluated. @cite_3 has evaluated strategies for dynamically deciding whether to confirm each user utterance during a task-oriented dialogue. Simulation results suggest that context-dependent adaptation strategies can improve performance, especially when the system has greater initiative. @cite_1 and @cite_0 have used reinforcement learning to adapt dialogue behavior over time such that system performance improves. We have instead focused on optimizing performance during a single dialogue.",
'ref_abstract': {
   '@cite_0': {'mid': '200223693', 'abstract': ''},
   '@cite_1': {'mid': '2141839844', 'abstract': "This paper describes a novel method by which a dialogue agent can learn to choose an optimal dialogue strategy. While it is widely agreed that dialogue strategies should be formulated in terms of communicative intentions, there has been little work on automatically optimizing an agent's choices when there are multiple ways to realize a communicative intention. Our method is based on a combination of learning algorithms and empirical evaluation techniques. The learning component of our method is based on algorithms for reinforcement learning, such as dynamic programming and Q-learning. The empirical component uses the PARADISE evaluation framework (, 1997) to identify the important performance factors and to provide the performance function needed by the learning algorithm. We illustrate our method with a dialogue agent named ELVIS (EmaiL Voice Interactive System), that supports access to email over the phone. We show how ELVIS can learn to choose among alternate strategies for agent initiative, for reading messages, and for summarizing email folders."},
   '@cite_3': {'mid': '2063157598', 'abstract': 'As with human?human interaction, spoken human?computer dialog will contain situations where there is miscommunication. One natural strategy for reducing the impact of miscommunication is selective verification of the user utterance meanings. This paper reports on both context-independent and context-dependent strategies for utterance verification that show that the use of dialog context can be very helpful in selecting which utterances to verify. Simulations with data collected during experimental trials with the Circuit Fix-It Shop spoken natural language dialog system are used in the analysis. In addition, the performance of various selection strategies is measured separately for computer-controlled and user-controlled dialogs and general guidelines for selecting an appropriate strategy are presented.'},
   '@cite_2': {'mid': '1882353391', 'abstract': 'While user modelling has become a mature field with demonstrable research systems of great power, comparatively little progress has been made in the development of user modelling components for commercial software systems. The development of minimalist user modelling components, simplified to provide just enough assistance to a user through a pragmatic adaptive user interface, is seen by many as an important step toward this goal. This paper describes the development, implementation, and empirical evaluation of a minimalist user modelling component for TIMS, a complex commercial software system for financial management. The experimental results demonstrate that a minimalist user modelling component does improve the subjective measure of user satisfaction. Important issues and considerations for the development of user modelling components for commercial software systems are also discussed.'}
}
}

I found the following number of missing abstracts (from the ref_abstract field):
Val: 3383
Test: 3403
Train: 20023

This was due to the incompleteness of the academic web graph. Some paper abstracts were missing from the original MAG datasets.


fix gated builds due to getargspec deprecation

Gated builds seem to be failing due to error when calling inspect.getargspec in tests:
2023-07-18T22:15:32.9356507Z         if kwonlyargs or ann:
2023-07-18T22:15:32.9356904Z >           raise ValueError("Function has keyword-only parameters or annotations"
2023-07-18T22:15:32.9357273Z                              ", use inspect.signature() API which can support them")
2023-07-18T22:15:32.9358074Z E           ValueError: Function has keyword-only parameters or annotations, use inspect.signature() API which can support them

See build:
https://pipelines.actions.githubusercontent.com/serviceHosts/c1806717-186f-43d1-b5bb-864035754060/_apis/pipelines/1/runs/1655/signedlogcontent/3?urlExpires=2023-07-19T13%3A49%3A56.8756087Z&urlSigningMethod=HMACV1&urlSignature=n7yT0tLu9c5kxVKqapcs71ABVMRu34O077hYnZORsVs%3D
According to similar issue:
https://github.com/treethought/flask-assistant/issues/89
The reason for this is that [inspect.getargspec](https://docs.python.org/3/library/inspect.html#classes-and-functions) can't handle type annotations and is deprecated in favor of inspect.getfullargspec. According to the documentation the latter should be a drop-in replacement, but this should probably be tested.

Hence, using inspect.getfullargspec as a drop-in replacement for the previous method to resolve the build errors.

Codecov Report
Patch coverage: 100.00% and no project coverage change.

Comparison is base (3d67671) 87.70% compared to head (cd840bd) 87.70%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@           Coverage Diff           @@
##             main     #570   +/-   ##
=======================================
  Coverage   87.70%   87.70%
=======================================
  Files          62       62
  Lines        4075     4075
=======================================
  Hits         3574     3574
  Misses        501      501

Flag
Coverage Δ

unittests
87.70% <100.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...interpret_community/mimic/models/lightgbm_model.py
86.51% <100.00%> (+0.56%)
:arrow_up:

... and 1 file with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


enable back going

When I switch between the tabs from navigation menu and then click on back button how it the implementation to back track the navigations of the side menu

nomore reqquired


{ [Error: read ECONNRESET] code: 'ECONNRESET', errno: 'ECONNRESET', syscall: 'read' }

Sails v11.2
Node v12.4
When attempting to send over 500 json records as a post to a blueprint the connection is reset. Everything works perfect if I send less than 20 records.
Here is my controller:
var Promise = require('bluebird');

module.exports = {

newRecord: function (req, res) {
	console.log(req)
	Agent.findOneById(req.query[0].agentId, function(err, agent) {
		var promises = [];
		_.forEach(req.query, function(record) {
			console.log(record);
			promises.push(Record.findOrCreate({userDN: record.userDN}, {
				name: record.name,
				faxPhone: record.faxPhone,
				email: record.email,
				cellPhone: record.cellPhone,
				guiLoginName: record.guiLoginName,
				userDN: record.userDN,
				location: record.location,
				did: record.did,
				owner: agent.id
			}));
		});
		Promise.all(promises)
		.then(function(records) {
			res.json(records);
		})
		.catch(function(err) {
			return res.negotiate(err);
		})
	});
},

Here is how I am sending the POST:
var postUsers = function(Users) {
  request.post({
    headers: {'content-type' : 'application/json', 'Content-Length': Buffer.byteLength(Users)},
    url: 'http://localhost:8000/api/record/newRecord',
    qs: Users
  }, function(err, res, body) {
    if (err) console.log(err);
  })
}

You are sending it in the query string. The maximum url length is around 2000 characters.
You need to send that as a post body rather than a query string. Also best practices would say this endpoint should probably be paginated to prevent memory issues but start with the post body.


render to html output changed in v3

Previously using v2.9.1 and moving to v3.0.0, the output from render(...).html() has changed.
Previously, the following test would pass:
it('should render html', () => {
    const Test = () =>
test

    expect(render(<Test />).html()).to.equal("
test
")
})

In v3, I get the following error:
AssertionError: expected 'test' to equal '
test
'
+ expected - actual

-test
+
test

I have checked the migration guide and change log for both enzyme and cheerio, but could not find reference to this being intentional.

We upgraded from cheerio v0.22 to v1, so breaking changes are expected - https://github.com/airbnb/enzyme/blob/master/docs/guides/migration-from-2-to-3.md#cheerio-has-been-updated-thus-render-has-been-updated-as-well - in this case, it's due to https://github.com/cheeriojs/cheerio/blob/48eae25c93702a29b8cd0d09c4a2dce2f912d1f4/History.md#migrating-from-version-0x.
In other words, the render wrapper is now around what the component renders, so .html() is now the HTML of its contents.
You can, however, import cheerio from 'cheerio'; cheerio.html(render(<Test />)) and you'll get the result you expect.
(cc @jugglinmike)

@ljharb i'd like to understand this better, but this feels wrong to me still... I think the above test probably shouldn't have broken in this release :/

It would have been ideal, but the breaking changes in cheerio are such that it was unavoidable - they no longer have the concept of "root", and .html() has always been innerHTML, not outerHTML.

I can confirm, cheerio.html(render(<Test />)) gives the expected output.
Given that, would it be possible to return a wrapper around cheerio for the html call.  Something like (based on render.js):
import cheerio from 'cheerio';
import { getAdapter } from './Utils';

export default function render(node, options = {}) {
  const adapter = getAdapter(options);
  const renderer = adapter.createRenderer({ mode: 'string', ...options });
  const html = renderer.render(node, options.context);
  const cheerioInstance = cheerio.load('')(html);

  return {
    ...cheerioInstance,
    html: () => cheerio.html(cheerioInstance)
  }
}

@mpeyper 1) that would make the .html() output different than all the other methods on cheerioInstance, 2) that would be incorrect because cheerioInstance isn't a plain object, and object spread makes it one, 3) html also can take an argument.

Obviously you know the cheerio api better than I do so I'll leave the actual implementation up to you guys.  All I was suggesting was that if the cheerio api isn't ideal anymore, perhaps you could provide your own that uses cheerio under the hood.

This breaking change is really a bummer, and a step backwards IMHO. I understand your concerns with cheerio, but to my mind this is an implementation detail that enzyme should solve to keep BC. I use enzyme, not cheerio.
If html() isn't updated to give the same result as in previous enzyme versions, I recommend to:

change the ShallowWrapper.html() documentation, because it still shows the previous behavior and is misleading
add a new method reproducing the old html() feature, because how do I test attributes of the enclosing tag otherwise?

it('should render a large paragraph', () => {
    const Test = () =>
test

    expect(render(<Test />).html()).to.equal('
test
');
})

Also, writing tests like the following really doesn't make sense:
it('should render html', () => {
    const Test = () =>
test

    expect(render(<Test />).html()).to.equal("test")
});

it('should render a large paragraph', () => {
    const Test = () =>
test
;
    const wrapper = render(<Test />);
    expect(wrapper.is('p')).to.equal(true);
    expect(wrapper.attr('style')).to.equal('font-size: 13px;');
    expect(render(<Test />).html()).to.equal('test');
});

Indeed, the docs should be updated.
In order to make a change here, something would have to change inside cheerio itself.

After those new changes the whole render API became useless for me. The pattern I was using with enzyme was:
expect(render(<Test/>).html()).to.equal('
test
');

Now I have to use 'render' API for that which is an overkill in 80% of cases.
It would be nice if you could bring the outer HTML back at some form.

I use render().html() for snapshot, And it would be nice if you could bring the outer HTML back at some form~~~

In cheerio, it looks like had this discussion back in 2012 and came up with $.html() https://github.com/cheeriojs/cheerio/issues/16#issuecomment-3841206 - not sure how much that helps in this case since I don't want to be importing $...
there'a slso prop(outHTML)` - that may look confusing given that it mixes browser and react props... haven't tested it yet but it's theoretically in 1.0 https://github.com/cheeriojs/cheerio/pull/945

This has the unintended consequence that it makes .html() wildly inconsistent between mount() and render(). This test, despite of the looks of it, is PASSING:
const base =
important
;

it('sanity test', () => {
  expect( mount(base).html()).toEqual('
important
');
  expect(render(base).html()).toEqual('important');
});

Which is... very confusing for someone getting started with Enzyme, and adds a lot of extra sanity checks along the way 😢

@franciscop-invast If you are using jest as a test runner you have an option to make snapshots which gives you more flexible and clean way to test your HTML output.

I am actually not rendering the .html() for testing, just for debugging purposes, and was really confused with this. My main issue though was the difference between .shallow() and .render() in the way that .shallow() will only put the components, while .render() will show the underlying html (which is what I wanted). But trying to use .html() to debug why my selectors were not found ({ length: 0 }) was made extra difficult due to these inconsistencies.

@franciscop-invast I think .debug() method should have worked better for this case, as .html() purpose is a bit different.
And as for snapshot testing, I have used it for a while and it's not strict at all :) And if you want to scale your assertions in one day (I mean test a bit more than a few things) you already have a solution in place.

enzyme doesn't support snapshots, but .debug() is a far superior method for doing that than .html() is, unrelated to the differences documented in this thread.

I'm going to close this - however if anyone in the future can provide a PR that would address the inconsistencies with render vs shallow/mount, I'd be happy to review it.


History graphs no longer uodate after a few hours (need to restart tydom2mqtt to fix)

Every few hours the logger for my delta dore temperature graphs hangs as a straight line with no more data received.
The logs in tydom2mqtt show thus : 2023-07-19 05:00:51,102 - main - WARNING - Unable to handle message: no close frame received or sent
Any ideas where this is coming from?
Thanks
Jon

It's likely the same issue as #107; I close is as duplicated.
In the meantime, a 3.3.0 version has just been released and contains an attempt to fix it; if you can give it a try 🤞 .


chore: Move Spoon snapshot repo into a profile

We shouldn't declare the snapshot repository willy-nilly in the pom-file, see discussion over at inria/spoon#3216. This PR puts the snapshot repo in a profile, such that we can still easily access it when we want like so:
$ mvn -P spoonSnapshot ...

Thanks @slarse.


btn-link no longer has an outline when clicked

Prerequisites

[X] I have searched for duplicate or closed issues
[X] I have validated any HTML to avoid common problems
[X] I have read the contributing guidelines

Describe the issue
When using .btn-link in v5.2.0 Beta 1, the button looks like a normal link instead of having the blue button outline when clicked (this worked in v5.1.3).
Reduced test cases
<button class="btn btn-sm btn-link">Text</button>

What operating system(s) are you seeing the problem on?
Windows, Android
What browser(s) are you seeing the problem on?
Chrome
What version of Bootstrap are you using?
5.2.0

Thanks for reporting this issue @imaperson1060. Confirm this regression that happened with https://github.com/twbs/bootstrap/commit/ef9d8538a06f43f74f49d6829cbf301773381488. The outline is no more displayed when active and the text becomes black.

Sooooo 5.2.1 kinda broke this again lol.
If it helps here's the only difference I found in inspect elements:
5.2.1:

5.2.0 (stable):

Sorry for bothering you again!😅

@imaperson1060 In v5.2.1, in https://github.com/twbs/bootstrap/pull/37026, this behavior has been voluntarily changed:

for all .btns, it changes the :focus styling to :focus-visible - this way, the focus style doesn't take effect and "stick" (until you click somewhere else) for mouse/touch users


Operation comment_options fail with extensions

Expected behavior
Broadcast a comment_options operation with beneficiaries.
Actual behavior
It's failing with this error:
transaction.operations = comment,[object Object],comment_options,[object Object]	 cause: comment_options.extensions = 0,[object Object]	 cause: (void) undefined type
 stack: Error: (void) undefined type

It seem the type void for comment_payout_beneficiaries is not working here: https://github.com/steemit/steem-js/blob/comment-options-test/src/auth/serializer/src/operations.js#L53
I tried a custom type like this:

But there is an error from the blockchain:
Error: 4 parse_error_exception: Parse Error
Couldn't parse uint64_t {}
    th_a  string.cpp:113 to_uint64
    {"i":"comment_payout_beneficiaries"}
    th_a  string.cpp:116 to_uint64

If you change comment_payout_benificiaries to
const comment_payout_beneficiaries = new Serializer(0, {
   beneficiaries: set(beneficiaries)
});

it should parse correctly, though I am getting
"3030000 tx_missing_posting_auth: missing required posting authority
Missing Posting Authority good-karma
    {"id":"good-karma","posting":{"weight_threshold":1,"account_auths":[["streemian",1]],"key_auths":[["STM89kBiwpi5R8CBrgAFWd5p5uayTvvS7B6Zb4oBenWx8ChjeLMTf",1]]},"active":{"weight_threshold":1,"account_auths":[],"key_auths":[["STM5DiwrKfp4ngW7fWcDej1Kd3efogYSGxsMKfkz3xi4AsNGYWU2D",1]]},"owner":{"weight_threshold":1,"account_auths":[],"key_auths":[["STM7iTj8quuiqX7aUHZWrYXfAqqTDbpL8FwxoCUzEeKE745mvBY41",1]]}}
    th_a  transaction.cpp:129 verify_authority

    {"ops":[["comment",{"parent_author":"good-karma","parent_permlink":"explore-tipping-on-steem-2017414t101419332z","author":"good-karma","permlink":"re-good-karma-explore-tipping-on-steem-2017414t101419332z-2017415t952376z","title":"","body":"test","json_metadata":"{\"tags\":\"tipping\",\"app\":\"esteem/1.4.1\",\"format\":\"markdown+html\"}"}],["comment_options",{"author":"good-karma","permlink":"re-good-karma-explore-tipping-on-steem-2017414t101419332z-2017415t952376z","max_accepted_payout":"1000000.000 SBD","percent_steem_dollars":10000,"allow_votes":true,"allow_curation_rewards":true,"extensions":[[0,{"beneficiaries":[{"account":"esteemapp","weight":100}]}]]}]],"sigs":["STM7wrsXFDs6Qor8htn4rmwdtVRAFrhiuYgRxnoYF8snCdRNUZUaq"]}
    th_a  transaction.cpp:172 verify_authority

    {"*this":{"ref_block_num":4390,"ref_block_prefix":2819398218,"expiration":"2017-04-15T06:52:53","operations":[["comment",{"parent_author":"good-karma","parent_permlink":"explore-tipping-on-steem-2017414t101419332z","author":"good-karma","permlink":"re-good-karma-explore-tipping-on-steem-2017414t101419332z-2017415t952376z","title":"","body":"test","json_metadata":"{\"tags\":\"tipping\",\"app\":\"esteem/1.4.1\",\"format\":\"markdown+html\"}"}],["comment_options",{"author":"good-karma","permlink":"re-good-karma-explore-tipping-on-steem-2017414t101419332z-2017415t952376z","max_accepted_payout":"1000000.000 SBD","percent_steem_dollars":10000,"allow_votes":true,"allow_curation_rewards":true,"extensions":[[0,{"beneficiaries":[{"account":"esteemapp","weight":100}]}]]}]],"extensions":[],"signatures":["1f0cb76bd7ae1d48c051ef33b3055c2dfd67051b7b77cf848b70ab1e0fcd2825827e50e53bbdb3c62083e3a623fc245f0982e0aa1bcf27f97c2538dfc464a04b4a"]}}
    th_a  transaction.cpp:285 verify_authority

    {"trx":{"ref_block_num":4390,"ref_block_prefix":2819398218,"expiration":"2017-04-15T06:52:53","operations":[["comment",{"parent_author":"good-karma","parent_permlink":"explore-tipping-on-steem-2017414t101419332z","author":"good-karma","permlink":"re-good-karma-explore-tipping-on-steem-2017414t101419332z-2017415t952376z","title":"","body":"test","json_metadata":"{\"tags\":\"tipping\",\"app\":\"esteem/1.4.1\",\"format\":\"markdown+html\"}"}],["comment_options",{"author":"good-karma","permlink":"re-good-karma-explore-tipping-on-steem-2017414t101419332z-2017415t952376z","max_accepted_payout":"1000000.000 SBD","percent_steem_dollars":10000,"allow_votes":true,"allow_curation_rewards":true,"extensions":[[0,{"beneficiaries":[{"account":"esteemapp","weight":100}]}]]}]],"extensions":[],"signatures":["1f0cb76bd7ae1d48c051ef33b3055c2dfd67051b7b77cf848b70ab1e0fcd2825827e50e53bbdb3c62083e3a623fc245f0982e0aa1bcf27f97c2538dfc464a04b4a"]}}
    th_a  database.cpp:2994 _apply_transaction

    {"trx":{"ref_block_num":4390,"ref_block_prefix":2819398218,"expiration":"2017-04-15T06:52:53","operations":[["comment",{"parent_author":"good-karma","parent_permlink":"explore-tipping-on-steem-2017414t101419332z","author":"good-karma","permlink":"re-good-karma-explore-tipping-on-steem-2017414t101419332z-2017415t952376z","title":"","body":"test","json_metadata":"{\"tags\":\"tipping\",\"app\":\"esteem/1.4.1\",\"format\":\"markdown+html\"}"}],["comment_options",{"author":"good-karma","permlink":"re-good-karma-explore-tipping-on-steem-2017414t101419332z-2017415t952376z","max_accepted_payout":"1000000.000 SBD","percent_steem_dollars":10000,"allow_votes":true,"allow_curation_rewards":true,"extensions":[[0,{"beneficiaries":[{"account":"esteemapp","weight":100}]}]]}]],"extensions":[],"signatures":["1f0cb76bd7ae1d48c051ef33b3055c2dfd67051b7b77cf848b70ab1e0fcd2825827e50e53bbdb3c62083e3a623fc245f0982e0aa1bcf27f97c2538dfc464a04b4a"]}}
    th_a  database.cpp:735 push_transaction

    {"call.method":"call","call.params":[3,"broadcast_transaction_with_callback",[null,{"ref_block_num":4390,"ref_block_prefix":2819398218,"expiration":"2017-04-15T06:52:53","operations":[["comment",{"parent_author":"good-karma","parent_permlink":"explore-tipping-on-steem-2017414t101419332z","author":"good-karma","permlink":"re-good-karma-explore-tipping-on-steem-2017414t101419332z-2017415t952376z","title":"","body":"test","json_metadata":"{\"tags\":\"tipping\",\"app\":\"esteem/1.4.1\",\"format\":\"markdown+html\"}"}],["comment_options",{"author":"good-karma","permlink":"re-good-karma-explore-tipping-on-steem-2017414t101419332z-2017415t952376z","max_accepted_payout":"1000000.000 SBD","percent_steem_dollars":10000,"allow_votes":true,"allow_curation_rewards":true,"extensions":[[0,{"beneficiaries":[{"account":"esteemapp","weight":"100"}]}]]}]],"extensions":[],"signatures":["1f0cb76bd7ae1d48c051ef33b3055c2dfd67051b7b77cf848b70ab1e0fcd2825827e50e53bbdb3c62083e3a623fc245f0982e0aa1bcf27f97c2538dfc464a04b4a"]}]]}
    th_a  websocket_api.cpp:124 on_message"

Hey well done! It's working good for me if i change "comment_payout_beneficiaries" to "0". See here: https://steemd.com/tx/dd8afed13f9fe3652274ac3f6f025f06399e5e3e .
I dont think streemian account has something to do with your error. In my case i used @guest132 account which give posting authorities to @busy.app: https://steemjs.com/@guest123/permissions .

great, in that case... it is likely, esteem-lib need some testing ;)

This is not fixed, I am getting this exact error
 stack: Error: (void) undefined type```

I have checked and the formatting is all correct. If I stringify the object I get this error instead

```Error: transaction.operations = comment_options,[object Object]	 cause: comment_options.extensions = [[0,{"beneficiaries":[{"account":"user1","weight":3333},{"account":"user2","weight":3333}]}]]	 cause: duplicate (set)
 stack: Error: duplicate (set)```


where is the api key ?

Hey !
I do not find the apy key, some one can help me please?

You have found the API key from the stake page


[roi] Make ROI style settable

Make linestyle/linewidth of ROIs settable as well as font size.

PR #2306 makes line and symbol style settable...
It still remains the question of setting the font size... but this is overall not settable for the whole plot items API (so not for v0.10).


Add OPA External Authorization #191

Title

Summary

Type
[] Bug fix
[] Feature request
[] Enhancement
[] Docs
Why?

Requirements

How to try it?

Documentation

Additional Information

Checklist:

[ ] My change requires a change to the documentation or CHANGELOG.
[ ] I have updated the documentation/CHANGELOG accordingly.

Holy cow, I am so interested in trying this out! Will probably take a while till I find enough time for that. Thank you so much for integrating this!
I wish this project was better known and had more maintainers. The project is even pretty hard to find via Google, even if you use very specific keywords. I only found this project from a comment at louketo-proxy. I will do my part by recommend this project whenever I get the opportunity 👍


Use stylelint rather than sass-lint for scss linting

Sass-lint is unmaintained

Sass-lint rules I cannot currently replicate in stylelint:

no-misspelled-properties
bem-depth
border-zero
property-sort-order (disabled anyway)
shorthand-values (shorthand-property-no-redundant-values is stricter than the setting we were using)

Sass-lint rules I have partially replicated in stylelint:

pseudo-element (sass-lint rule prevents single-colon classes)
space-around-operator (in most places but not in all functions)

Rules I think I have successfully replicated, but am not entirely sure

brace-style

This is done now we've migrated to GitHub Actions, right? Should we close this? 🙌

This is done now we've migrated to GitHub Actions, right? Should we close this? raised_hands

We're still using sass-lint and -- I think on codeclimate? I do have the reviewdog PR in here though I think yes

Oh, oops, I think I misread where we had the stylelint check and thought it was already merged! If we rebase this maybe it can merge? I don't remember if this was blocked on something (since it's marked as Draft).

About rules we can't replicate:

no-misspelled-properties - should be possible with property-no-unknown
bem-depth - BEM seems to be a special way of writing selectors, which we don't use, so I'm fine ignoring this
border-zero - don't personally mind about this
property-sort-order (disabled anyway) - seems fine to ignore
shorthand-values - I don't mind what we do here!

I think given the property-no-unknown lint we should be good? We could add it to the config and see how it goes!


Simplify getting a curies.Converter from a prefixmaps.Context

This PR introduces curies as a core requirement and simplifies the usage in many examples in the README for generating a curies.Converter object from a prefixmaps.Context object down to a single line:
from prefixmaps import load_multi_context
from curies import Converter

context = load_multi_context(["obo", "bioregistry.upper", "linked_data", "prefixcc"])
converter: Converter = context.as_converter()

@sierra-moxon now that a new release has been made, can we get this in?


Support for loading more subtitle format files through the network

v0.69 supports loading subtitles over the network, but only .srt subtitles are supported.
Please support .ass, .ssa, .vtt subtitle format files.

I was waiting whatever someone will actually request this. So you actually use these types of subtitles in your use case? Do you know if any other video player support loading of such subtitle formats over network.


hyprland/workspaces: Auto rename lost active information

I'm on the latest git commit of both waybar and Hyprland.
When I rename the active workspace, waybar correctly updates the name/icon, but while the workspace was correctly styled as active before, it no longer is after the rename. I have to switch to another workspace and back to force an update.

@foonathan Can you try with the PR https://github.com/Alexays/Waybar/pull/2485 ?

I can confirm it's fixed. Thank you.


Setup Teams/Slack channels

People are using the Issues list to ask for more detail on the project roadmap and implementation questions.
I propose we do three things:

Move design and roadmap discussions to a specific chat channel (Teams or Slack). We could repurpose the "General" Teams channel for this.

Create a separate channel for people to post questions.

Only use issues to file bug requests, feature requests, etc.

@mspiekermann, I assigned this to you so we can discuss it in the next committers meeting.

what about https://docs.github.com/en/discussions ?

It has advantages for the community to have the information in one single location.  Github discussions are perfect for this, that's why we just activated the Discussions-Tab (https://github.com/eclipse-dataspaceconnector/DataSpaceConnector/discussions).
Ofc we are happy to receive suggestions for more categories etc.


chore(master): release 0.19.2

:robot: I have created a release beep boop
0.19.2 (2023-02-27)

upgrade to bee 1.12.0 (#321) (969feeb)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/ethersphere/swarm-desktop/releases/tag/untagged-3518a98ed9047aa732a2 :sunflower:


[BUG] Storage blob delete 403 wrong signature with okhttp

Describe the bug
When using azure-storage-blob:12.1.0 with azure-core-http-okhttp:1.1.0 and when we delete a blob, it fails with a mismatched signature error.
Exception or Stack Trace
Caused by: com.azure.storage.blob.models.BlobStorageException: Status code 403, "<?xml version="1.0" encoding="utf-8"?><Error>AuthenticationFailed<Message>Server failed to authenticate the request. Make sure the value of Authorization header is formed correctly including the signature.
RequestId:7502f416-401e-0027-5282-XXXXXXXX
Time:2020-01-07T17:47:36.8721923Z</Message><AuthenticationErrorDetail>The MAC signature found in the HTTP request 'XXXXXXX=' is not the same as any computed signature. Server used following string to sign: 'DELETE

application/octet-stream
Tue, 07 Jan 2020 17:47:36 GMT

x-ms-client-request-id:XXXXX
x-ms-version:2019-02-02
/XXXX.xls'.</AuthenticationErrorDetail></Error>"
	at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
	at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:490)
	at com.azure.core.http.rest.RestProxy.instantiateUnexpectedException(RestProxy.java:357)
	at com.azure.core.http.rest.RestProxy.lambda$ensureExpectedStatus$3(RestProxy.java:400)
	at reactor.core.publisher.MonoFlatMap$FlatMapMain.onNext(MonoFlatMap.java:118)
	at reactor.core.publisher.Operators$MonoSubscriber.complete(Operators.java:1630)
	at reactor.core.publisher.MonoProcessor.onNext(MonoProcessor.java:317)
	at reactor.core.publisher.Operators$MonoSubscriber.complete(Operators.java:1630)
	at reactor.core.publisher.MonoFlatMap$FlatMapMain.onNext(MonoFlatMap.java:144)
	at reactor.core.publisher.FluxMapFuseable$MapFuseableSubscriber.onNext(FluxMapFuseable.java:121)
	at reactor.core.publisher.FluxMapFuseable$MapFuseableSubscriber.onNext(FluxMapFuseable.java:121)
	at reactor.core.publisher.Operators$MonoSubscriber.complete(Operators.java:1630)
	at reactor.core.publisher.MonoCollect$CollectSubscriber.onComplete(MonoCollect.java:145)
	at reactor.core.publisher.FluxMapFuseable$MapFuseableSubscriber.onComplete(FluxMapFuseable.java:144)
	at reactor.core.publisher.FluxReplay$UnboundedReplayBuffer.replayNormal(FluxReplay.java:551)
	at reactor.core.publisher.FluxReplay$UnboundedReplayBuffer.replay(FluxReplay.java:654)
	at reactor.core.publisher.FluxReplay.subscribeOrReturn(FluxReplay.java:1096)
	at reactor.core.publisher.FluxReplay.subscribe(FluxReplay.java:1064)
	at reactor.core.publisher.FluxAutoConnectFuseable.subscribe(FluxAutoConnectFuseable.java:60)
	at reactor.core.publisher.InternalMonoOperator.subscribe(InternalMonoOperator.java:55)
	at reactor.core.publisher.MonoDefer.subscribe(MonoDefer.java:52)
	at reactor.core.publisher.Mono.subscribe(Mono.java:4105)
	at reactor.core.publisher.MonoProcessor.add(MonoProcessor.java:457)
	at reactor.core.publisher.MonoProcessor.subscribe(MonoProcessor.java:370)
	at reactor.core.publisher.InternalMonoOperator.subscribe(InternalMonoOperator.java:55)
	at reactor.core.publisher.MonoFlatMap$FlatMapMain.onNext(MonoFlatMap.java:150)
	at reactor.core.publisher.FluxMapFuseable$MapFuseableSubscriber.onNext(FluxMapFuseable.java:121)
	at reactor.core.publisher.FluxMapFuseable$MapFuseableSubscriber.onNext(FluxMapFuseable.java:121)
	at reactor.core.publisher.Operators$MonoSubscriber.complete(Operators.java:1630)
	at reactor.core.publisher.MonoCollect$CollectSubscriber.onComplete(MonoCollect.java:145)
	at reactor.core.publisher.FluxMapFuseable$MapFuseableSubscriber.onComplete(FluxMapFuseable.java:144)
	at reactor.core.publisher.FluxReplay$UnboundedReplayBuffer.replayNormal(FluxReplay.java:551)
	at reactor.core.publisher.FluxReplay$UnboundedReplayBuffer.replay(FluxReplay.java:654)
	at reactor.core.publisher.FluxReplay$ReplaySubscriber.onComplete(FluxReplay.java:1218)
	at reactor.core.publisher.MonoFlatMapMany$FlatMapManyInner.onComplete(MonoFlatMapMany.java:252)
	at reactor.core.publisher.FluxMap$MapSubscriber.onComplete(FluxMap.java:136)
	at reactor.core.publisher.FluxFilter$FilterSubscriber.onComplete(FluxFilter.java:160)
	at reactor.core.publisher.FluxTakeUntil$TakeUntilPredicateSubscriber.onComplete(FluxTakeUntil.java:114)
	at reactor.core.publisher.FluxTakeUntil$TakeUntilPredicateSubscriber.onNext(FluxTakeUntil.java:92)
	at reactor.core.publisher.FluxMap$MapSubscriber.onNext(FluxMap.java:114)
	at reactor.core.publisher.FluxRepeatPredicate$RepeatPredicateSubscriber.onNext(FluxRepeatPredicate.java:79)
	at reactor.core.publisher.FluxJust$WeakScalarSubscription.request(FluxJust.java:99)
	at reactor.core.publisher.Operators$MultiSubscriptionSubscriber.set(Operators.java:1994)
	at reactor.core.publisher.Operators$MultiSubscriptionSubscriber.onSubscribe(Operators.java:1868)
	at reactor.core.publisher.FluxJust.subscribe(FluxJust.java:70)
	at reactor.core.publisher.FluxRepeatPredicate$RepeatPredicateSubscriber.resubscribe(FluxRepeatPredicate.java:113)
	at reactor.core.publisher.FluxRepeatPredicate.subscribeOrReturn(FluxRepeatPredicate.java:49)
	at reactor.core.publisher.Flux.subscribe(Flux.java:8129)
	at reactor.core.publisher.MonoFlatMapMany$FlatMapManyMain.onNext(MonoFlatMapMany.java:188)
	at reactor.core.publisher.MonoUsing$MonoUsingSubscriber.onNext(MonoUsing.java:229)
	at reactor.core.publisher.Operators$ScalarSubscription.request(Operators.java:2186)
	at reactor.core.publisher.MonoUsing$MonoUsingSubscriber.request(MonoUsing.java:175)
	at reactor.core.publisher.MonoFlatMapMany$FlatMapManyMain.onSubscribe(MonoFlatMapMany.java:134)
	at reactor.core.publisher.MonoUsing$MonoUsingSubscriber.onSubscribe(MonoUsing.java:205)
	at reactor.core.publisher.MonoJust.subscribe(MonoJust.java:54)
	at reactor.core.publisher.MonoUsing.subscribe(MonoUsing.java:102)
	at reactor.core.publisher.FluxFromMonoOperator.subscribe(FluxFromMonoOperator.java:73)
	at reactor.core.publisher.FluxReplay.connect(FluxReplay.java:1057)
	at reactor.core.publisher.FluxAutoConnectFuseable.subscribe(FluxAutoConnectFuseable.java:62)
	at reactor.core.publisher.InternalMonoOperator.subscribe(InternalMonoOperator.java:55)
	at reactor.core.publisher.MonoFlatMap$FlatMapMain.onNext(MonoFlatMap.java:150)
	at reactor.core.publisher.FluxMap$MapSubscriber.onNext(FluxMap.java:114)
	at reactor.core.publisher.FluxOnErrorResume$ResumeSubscriber.onNext(FluxOnErrorResume.java:73)
	at reactor.core.publisher.Operators$MonoSubscriber.complete(Operators.java:1630)
	at reactor.core.publisher.MonoFlatMap$FlatMapMain.onNext(MonoFlatMap.java:144)
	at reactor.core.publisher.FluxDelaySubscription$DelaySubscriptionMainSubscriber.onNext(FluxDelaySubscription.java:180)
	at reactor.core.publisher.SerializedSubscriber.onNext(SerializedSubscriber.java:89)
	at reactor.core.publisher.FluxTimeout$TimeoutMainSubscriber.onNext(FluxTimeout.java:173)
	at reactor.core.publisher.FluxMapFuseable$MapFuseableSubscriber.onNext(FluxMapFuseable.java:121)
	at reactor.core.publisher.FluxMapFuseable$MapFuseableSubscriber.onNext(FluxMapFuseable.java:121)
	at reactor.core.publisher.Operators$MonoSubscriber.complete(Operators.java:1630)
	at reactor.core.publisher.MonoFlatMap$FlatMapMain.onNext(MonoFlatMap.java:144)
	at reactor.core.publisher.MonoCreate$DefaultMonoSink.success(MonoCreate.java:156)
	at com.azure.core.http.okhttp.OkHttpAsyncHttpClient$OkHttpCallback.onResponse(OkHttpAsyncHttpClient.java:172)
	at okhttp3.RealCall$AsyncCall.run(RealCall.kt:138)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
	at java.base/java.lang.Thread.run(Thread.java:834)
	Suppressed: java.lang.Exception: #block terminated with an error
		at reactor.core.publisher.BlockingSingleSubscriber.blockingGet(BlockingSingleSubscriber.java:93)
		at reactor.core.publisher.Mono.block(Mono.java:1663)
		at com.azure.storage.common.implementation.StorageImplUtils.blockWithOptionalTimeout(StorageImplUtils.java:94)
		at com.azure.storage.blob.specialized.BlobClientBase.deleteWithResponse(BlobClientBase.java:521)
		at com.azure.storage.blob.specialized.BlobClientBase.delete(BlobClientBase.java:495)

To Reproduce
 blobContainerClient.getBlobClient(blob).delete();

@Tetradeus thank you for reporting this issue. Can you please clarify a couple points:

Are you specifying ok-http in your issue because it works with the netty client but fails with the ok-http client?
Are you authenticating with a shared key or with a sas token?

Hello @rickle-msft ,

To be honest, I have not tested it with the netty client yet. I tried to use this library with netty in an azure function, and because of an older netty lib version in azure function java, it cannot even be used ... So yes, for the moment I had this issue only with okhttp client.

I am authenticating with a shared key. It worked for creation and reading.

@joshfree FYI the dependency issue with azure function. Perhaps we should in some way try to get the two products on the same version so they can be used together?
Thank you for that information. It is quite curious that a shared key would be hitting an auth failure at all, let alone in a specific method like this. Can you please set a break point in the buildStringToSign method in StorageSharedKeyCredential type and capture the string to sign the client is generating. We need to compare that to the value you already shared and see what's going wrong.

Thanks a lot, the Azure SDK policy trick saved my day :+1:

I am going to close this issue because it looks like the fix has been merged.


"TypeError: (0 , _stringify2.default) is not a function"

When upgrading to 6.0.0 from 6.0.0-beta.9, my tests using fetch-mock are failing due to the error mentioned in the title. I tried to simplify one of the tests to provide some context, but let me know if more information is needed. I've seen this issue with other issues regarding babel/webpack, but I'm not sure if it's related, as the issues I've come across (and this) appear to be dealing with a webpack build or how imports are being called.
export function getFooInfo(fooId) {
    const init = {
        credentials: "include",
        method: "GET"
     };
    return async () => {
            // in 6.0.0-beta.9 this is fine. In 6.0.0 this throws "TypeError: (0 , _stringify2.default) is not a function"
            const request = await fetch(API_URL + "/foo/basic?fooId=" + fooId, init);
            if (request.ok) {
                return await request.json();
            }
            else {
                throw new Error(request.status + "- " + request.statusText);
            }
    };
}

import * as fetchMock from "fetch-mock";
import configureStore from "redux-mock-store"; // version 1.4.0
import thunk from "redux-thunk"; // version 2.2.0

describe("get foo info", () => {
    it("should handle successful get basic foo info", () => {
        const fakeFoo = {
            displayName: "Chris",
            fooId: "ValidID",
        };
        // calling this method will fail due to the type error in the title
        fetchMock.mock(TEST_API_URL + "foo/basic?fooId=ValidID", Promise.resolve({
            body: {
                displayName: fakeFoo.displayName,
                fooId: fakeFoo.id
            },
            status: 200
        }));

        const mockStore = configureStore([thunk]);
        const store = mockStore({});
        return store.dispatch(actions.getBasicFooInfo("ValidID")).then(() => {
            const storedActions = store.getActions();
            const lastAction = storedActions[storedActions.length - 1];
            expect(lastAction.type).to.eql(actionTypes.UPDATE);
            expect(lastAction.payload).to.eql(fakeFoo);
        });
    });
});

which environment is this running in? It probably needs a tweak of my babel config

Coulde you try with 6.1.0-beta.1 please

I'm not certain that version exists, but if I update to 6.0.1, everything breaks and V8 is running out of memory.
Node: 8.9.4
Karma:  2.0.0
Webpack: 3.11.0
Karma-Webpack: 2.0.13
Babel:  6.26.0 (I'm fairly certain)

Actually, ignore the new error mentioned, but updated to the latest version of fetch-mock is still producing the original issue.

Also, the call stack. a lot of it might not be helpful, but I figured I would add it as well.
at ResponseBuilder.constructResponseBody (http://localhost:9878/base/test/data-models/student/student-actions-spec.tsx?ae287ec9c1b1b56e6f9a0d6a9a280ce470d3280a:113553:36)
    at ResponseBuilder.exec (http://localhost:9878/base/test/data-models/student/student-actions-spec.tsx?ae287ec9c1b1b56e6f9a0d6a9a280ce470d3280a:113476:9)
    at Object._callee$ (http://localhost:9878/base/test/data-models/student/student-actions-spec.tsx?ae287ec9c1b1b56e6f9a0d6a9a280ce470d3280a:112038:81)
    at tryCatch (http://localhost:9878/base/test/data-models/student/student-actions-spec.tsx?ae287ec9c1b1b56e6f9a0d6a9a280ce470d3280a:112194:40)
    at Generator.invoke [as _invoke] (http://localhost:9878/base/test/data-models/student/student-actions-spec.tsx?ae287ec9c1b1b56e6f9a0d6a9a280ce470d3280a:112428:22)
    at Generator.prototype.(anonymous function) [as next] (http://localhost:9878/base/test/data-models/student/student-actions-spec.tsx?ae287ec9c1b1b56e6f9a0d6a9a280ce470d3280a:112246:21)
    at step (http://localhost:9878/base/test/data-models/student/student-actions-spec.tsx?ae287ec9c1b1b56e6f9a0d6a9a280ce470d3280a:112883:30)
    at http://localhost:9878/base/test/data-models/student/student-actions-spec.tsx?ae287ec9c1b1b56e6f9a0d6a9a280ce470d3280a:112894:13'

Can you try v6.1.0-beta.2 please. Finally managed to get a new release out

This is now fixed in the latest release. In node6 and below you will also need to install babel-polyfill (I decided not to add it as an explicit dependency as it increases the dependency footprint of fetch-mock from 3 to 10's, and isn't needed in modern environments). On the client side you shouldn't need to do that

It appears this is potentially fixed, but now there is a new error when running the same test, but updating to latest fetch-mock.
ERROR in ./node_modules/fetch-mock/es5/client.js
Module not found: Error: Can't resolve 'core-js/modules/es7.string.pad-end' in '/Users/cbaker/dev/app/app.UI/node_modules/fetch-mock/es5'
 @ ./node_modules/fetch-mock/es5/client.js 193:0-45
 @ ./test/data-models/tester/tester-actions-spec.tsx

Did something between those minor releases change as far as how to use fetch-mock?


A small question

If engine prediction is added will it have any benefits to legit cheaters or mainly for hvh

There have already been many issues opened about this. Please close this duplicate, Thank you.

It improves aimbot accuracy


[inclubator/kafka]  Accessing Kafka outside kubernetes not working

Is this a request for help?:
Yes

Is this a BUG REPORT or FEATURE REQUEST? (choose one):
Bug

Version of Helm and Kubernetes:
Helm version
Client: &version.Version{SemVer:"v2.9.1", GitCommit:"20adb27c7c5868466912eebdf6664e7390ebe710", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.9.1", GitCommit:"20adb27c7c5868466912eebdf6664e7390ebe710", GitTreeState:"clean"}
Kubernetes version
Client Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.6", GitCommit:"9f8ebd171479bec0ada837d7ee641dec2f8c6dd1", GitTreeState:"clean", BuildDate:"2018-03-21T15:21:50Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.6", GitCommit:"9f8ebd171479bec0ada837d7ee641dec2f8c6dd1", GitTreeState:"clean", BuildDate:"2018-03-21T15:13:31Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}
Which chart:
[inclubator/kafka]
What happened:
Accessing kafka from outside note working as expected.
What you expected to happen:
Kafka broker should be accessible at kafka.k8s.cluster.vpc:31091
How to reproduce it (as minimally and precisely as possible):
Follwed the given steps for helm chart setup of kafka. with external enabled
external:
  enabled: true
  domain: 'k8s.cluster.vpc'

Anything else we need to know:
No issue of connectivity between the instances. Similarly the Route53 A records are getting created properly.
kc describe svc kafka-1-external -n test-kafka
Name:                     kafka-1-external
Namespace:                test-kafka
Labels:                   app=kafka
                          chart=kafka-0.8.3
                          heritage=Tiller
                          pod=kafka-1
                          release=kafka
Annotations:              dns.alpha.kubernetes.io/internal=kafka.k8s.groupplatform.vpc
Selector:                 app=kafka,pod=kafka-1,release=kafka
Type:                     NodePort
IP:                       <IP_ADDRESS>
Port:                     external-broker  19092/TCP
TargetPort:               31091/TCP
NodePort:                 external-broker  31091/TCP
Endpoints:                <IP_ADDRESS>:31091
Session Affinity:         None
External Traffic Policy:  Cluster
Events:                   <none>

Since the target port is 31091, the port should be exposed from the pod. But when i do telnet to the corresponding port connection refused.
When I exec inside the kafka-0 pod, and check the /etc/kafka/kafka.properties, it has the listeners as
advertised.listeners=PLAINTEXT://<IP_ADDRESS>:9092
listeners=PLAINTEXT://<IP_ADDRESS>:9092

Hi @vidhy
I believe you must also specify configurationOverrides.advertised.listeners.  Guessing for your example it would be this...
configurationOverrides:
  advertised.listeners: '&& export KAFKA_ADVERTISED_LISTENERS=EXTERNAL://k8s.cluster.vpc:$((31090
    + ${KAFKA_BROKER_ID})),PLAINTEXT://${POD_IP}:9092'

@drekle  I dont think that fixes the issue. These are the properties I have inside the pod.
advertised.listeners=EXTERNAL://k8s.groupplatform.vpc:31090,PLAINTEXT://<IP_ADDRESS>:9092
listener.security.protocol.map=PLAINTEXT:PLAINTEXT,EXTERNAL:PLAINTEXT
listeners=EXTERNAL://<IP_ADDRESS>:31090,PLAINTEXT://<IP_ADDRESS>:9092

When i do
bin/kafka-console-producer.sh     --broker-list test-kafka.k8s.groupplatform.vpc:31090     --topic my-topic
I am getting

[2018-07-25 10:37:26,561] ERROR Error when sending message to topic my-topic with key: null, value: 2 bytes with error: (org.apache.kafka.clients.producer.internals.ErrorLoggingCallback)
org.apache.kafka.common.errors.TimeoutException: Expiring 1 record(s) for my-topic-0: 1549 ms has passed since batch creation plus linger time

I am able to produce and consume properly inside the kubernetes cluster and access broker via "test-kafka.test-kafka.svc.cluster.local:9092". So the issue is with external access of kafka alone.

@vidhy I told you wrong above.  The advertised listener should be the FQDN.  You are calling it with test-kafka.k8s.groupplatform.vpc:31090 yet it is listening to k8s.groupplatform.vpc:31090.  This was my mistake in my mention.  Can you try changing it to test-kafka.k8s.groupplatform.vpc:31090?

that worked like a charm. thanks @drekle

@vidhy I told you wrong above. The advertised listener should be the FQDN. You are calling it with test-kafka.k8s.groupplatform.vpc:31090 yet it is listening to k8s.groupplatform.vpc:31090. This was my mistake in my mention. Can you try changing it to test-kafka.k8s.groupplatform.vpc:31090?
configurationOverrides:
  advertised.listeners: '&& export KAFKA_ADVERTISED_LISTENERS=EXTERNAL://test-kafka.k8s.groupplatform.vpc:$((31090
    + ${KAFKA_BROKER_ID})),PLAINTEXT://${POD_IP}:9092'

OMG .. thank you thank you so much!
I've been troubleshooting all day to find this answer, works like a charm now!

Hi @drekle,
We configured Kafka using incubator Helm charts on rancher Kubernetes cluster by updating values.yml with below properties and using helm install --name test-kafka -f values.yml incubator/kafka --namespace test

enabled:true
advertised.listeners: '&& export KAFKA_ADVERTISED_LISTENERS=EXTERNAL://test-kafka.cluster.local:$((31090

${KAFKA_BROKER_ID})),PLAINTEXT://${POD_IP}:9092'

uncommented listener.security.protocol.map

We are able to successfully create topics within cluster. But we still have issues in exposing Kafka outside cluster. Can you please help

Hi @drekle , @vidhy
I have following config for external
replicas: 3
zookeeper:
  replicaCount: 3
external:
  enabled: true
  type: NodePort
  servicePort: 9092
  firstListenerPort: 30101
configurationOverrides:
  listeners: "PLAINTEXT://:9092"
  "advertised.listeners": '&& export KAFKA_ADVERTISED_LISTENERS=PLAINTEXT://<IP_ADDRESS>:$((30101 + ${KAFKA_BROKER_ID}))'
  "listener.security.protocol.map": "PLAINTEXT:PLAINTEXT"

Then all containers are up, but brokers can't communicate each other:
java.io.IOException: Connection to <IP_ADDRESS>:30101 (id: 0 rack: null) failed.
at org.apache.kafka.clients.NetworkClientUtils.awaitReady(NetworkClientUtils.java:70)
at kafka.controller.RequestSendThread.brokerReady(ControllerChannelManager.scala:279)
at kafka.controller.RequestSendThread.doWork(ControllerChannelManager.scala:233)
at kafka.utils.ShutdownableThread.run(ShutdownableThread.scala:82)
[2019-09-03 10:45:09,155] WARN [Controller id=2, targetBrokerId=1] Connection to node 1 could not be established. Broker may not be available. (org.apache.kafka.clients.NetworkClient)
[2019-09-03 10:45:09,155] WARN [RequestSendThread controllerId=2] Controller 2's connection to broker <IP_ADDRESS>:30102 (id: 1 rack: null) was unsuccessful (kafka.controller.RequestSendThread)
java.io.IOException: Connection to <IP_ADDRESS>:30102 (id: 1 rack: null) failed.
at org.apache.kafka.clients.NetworkClientUtils.awaitReady(NetworkClientUtils.java:70)
at kafka.controller.RequestSendThread.brokerReady(ControllerChannelManager.scala:279)
at kafka.controller.RequestSendThread.doWork(ControllerChannelManager.scala:233)
at kafka.utils.ShutdownableThread.run(ShutdownableThread.scala:82)

Can you help me?


Electronic chapter problem

How to deal with the electronic seal does not show

Hi,
what do you mean with the electronic seal? Can you provide more information please?

Hi,
Does that make sense? The names are in red. The electronic signature.
thanks.

Hi,
The names are in red. The electronic signature.
The circled part does not show.
Does that make sense?
thanks.

PDF's electronic signature disappeared.

Ok. I see.
This issue is similar to #29. There are certain items that seems not to display when loading a page in a PdfRenderer. I suggest that if you need a more advanced rendering of the PDF document, you should try a more specific SDK like PSPDFKit. PdfRenderer is a very basic widget and its features are limited.


Remove AssemblyInfo From HelpWriter

Would it be possible to add some boolean option in order to display/remove the assembly info when usage is printed ?

Hi digination,
but I think that this can be controlled outside the parser code (in your program). If I'm wrong, please explain more.
Thank you for choosing our OSS!


Assignments is TestCase::setUp should be used to infer property types

PHPStorm is able to infer property types based on assignments happening in the constructor.
It would be great if the same behavior could be provided for assignments happening in the setUp method of test cases, as it is the initializer for the test case.

setUp and setUpBeforeClass is supported here


Feature request: Clear button for keyword searches

Clearing the results of a "Find" operation are a bit awkward, requiring a second "empty" search.  It would be nice to have a "Clear" button that would clear any search results.

Closing. New release should solve any issues.
https://github.com/Beercow/OneDriveExplorer/releases/tag/v2023.03.10


Add Plugin 'Vineyard Helper'

Vineyard Helper highlights tiles containing pickable grapevines in Aldarin vineyard. In addition, it the highlight changes colour depending on whether or not the Grape barrel is full. Currently the animation which indicates pickable grapevines is extremely hard to see. This plugin increases the accessibility of the Aldarin vineyard content and greatly improves the experience, which is useful to interested players and, in particular, snowflake accounts.

Any particular reason objectIds is defined in the config when it shouldn't be changed?

Any particular reason objectIds is defined in the config when it shouldn't be changed?

Obsolete feature from early versions/debugging. Has been fixed in newest commit.

Accidentally closed pull request briefly, sorry, not familiar with GitHub.


Artist spotlight

I guess Art creation is not a contest or competition and we would like to give the spotlight to great artists around.
In this issue, we would like to have an array of artist's addresses, let's start with 10 of them(?) and it should show three gallery items from their recent mints, each row should be one artist.
We would make (bi)weekly voting rounds on Discord on artists spotlights in KodaDot Spotlight

[ ] https://nft.kodadot.xyz/leaderboard rename route to spotlight
[ ] array of artist where we can easily change who is showed up
[ ] create subquery grapql to show particular artists 3 last mints
[ ] links to artist profile and show their on-chain identity in the /spotlight for their particular row

I'd suggest to write articles something like interviews to give the artists the best spotlight.
Hosting discussions on discord with artist could be cool too, something like community call but with artist as host.
Probably relates to have on the front page art - recent mints maybe ?


Feature/favorite from recipe page

This pull request adds functionality to be able to "favorite" recipes on the home page and individual recipe pages
please review changes to CSS, and the createRecipePageHTML function

Great job adding hearting to the landing page and the individual recipe page. I took some of your code that you already made and moved them into individual functions to make it cleaner. I also applied some of the innovations you made to createRecipePageHTML to createRecipeHTML


Correct Plugin Config Section in README

In Readme the XML was ending in Python instead of Plugin Tag

Oops! Thanks for this


"if" clauses inside inline JavaScript on XHTML document formatting issue

The using the beautify feature on inline JavaScript I get some strange effects.
This is the HTML section with JS inside (manually beautified):
<script type="text/javascript">
    $(document).ready(function ()  {
        if (mythema == '...') {
            foo();
            bar();
        }
    });
</script>

This is what I get after:
<script type="text/javascript">
    $(document).ready(function ()  {
        if (mythema == '...') {foo();
            bar();}
    });
</script>

It doesn't make any sense to me.

XHTML files should be handled more as XML than HTML type documents.  While XHTML documents contain the same vocabulary and rules as HTML they carry the syntax and well-formedness requirements of XML.  I have opened a pull request to resolve this issue.
This is not really an atom-beautify file defect, perhaps more of a missing feature (associating .xhtml files as XML documents).  I would also request you open an issue with the JS Beautify project as that is the default beautifier for HTML: https://github.com/beautify-web/js-beautify/issues

@prettydiff thanks for explanation.
Unluckily the file I'm editing is not even a XHTML because it's a template of the Zope application server (an XML syntax compatible language)
Maybe a way to disable prettifying in a section of the file can help? I can live with a not-well-indented section in my template, but not with a compressed mess on JavaScript.

@keul Just select "XML" from the grammar list for this file (Edit, Select Grammar) and then when you beautify the problem will be resolved.

Also, I don't know how you're getting the output you say you're getting.   I don't know of any condition under which the output you're showing would happen.

@keul Would you mind posting a gist of a complete sample template file so that we can attempt to reproduce this error?

@bitwiseman @prettydiff I'll try to gives you all details I can in next few days (I'm out of office until end of the week).
Thanks

@keul  - any update?

@bitwiseman I'm sorry, busy days and I totally forgot the pending issue.
Unluckily the issue... disappeared.
I copied the template file apart to perform additional tests and today it simply works, it's nicely beautified.
I'm not sure if recently the atom-beautify plugin has been updated so something fixed the issue or not.
Sorry to all for the noise.
@prettydiff: the text format was already XML also last time I checked.

No problem, thanks for getting back to us on it.  Please continue to report any issues. :smile:


firing a trigger with no rules will return an activaiton id but no activation record will be written

recent changes and refactoring in the trigger handler will cause an activation id to be returned but no activation record to be created if the trigger has no matching rules.

Fix is here https://github.com/apache/incubator-openwhisk/pull/3262


New project generation failing from Bourbon dependency

Just tried to start a new project today and running into problems with the bourbon dependency.
Fetching version metadata from https://rubygems.org/..
Fetching dependency metadata from https://rubygems.org/.
Resolving dependencies...
Using rake 11.3.0
Using concurrent-ruby 1.0.2
Using i18n 0.7.0
Using minitest 5.9.1
Using thread_safe 0.3.5
Using builder 3.2.2
Using erubis 2.7.0
Using mini_portile2 2.1.0
Using rack 2.0.1
Using nio4r 1.2.1
Using websocket-extensions 0.1.2
Using mime-types-data 3.2016.0521
Using arel 7.1.4
Using addressable 2.4.0
Using execjs 2.7.0
Using awesome_print 1.7.0
Using babel-source 5.8.35
Using sass 3.4.22
Using thor 0.19.1
Using uniform_notifier 1.10.0
Using bundler 1.13.6
Using byebug 9.0.6
Using json 2.0.2
Using coderay 1.1.1
Using safe_yaml 1.0.4
Using database_cleaner 1.5.3
Using debug_inspector 0.0.2
Using diff-lcs 1.2.5
Using docile 1.1.5
Using dotenv 2.1.1
Using method_source 0.8.2
Using ffi 1.9.14
Using flutie 2.0.0
Using hashdiff 0.3.0
Using honeybadger 2.7.0
Using rb-fsevent 0.9.8
Using ruby_dep 1.5.0
Using normalize-rails 3.0.3
Using pg 0.19.0
Using slop 3.6.0
Using puma 3.6.0
Using rack-timeout 0.4.2
Using rails_stdout_logging 0.0.5
Using rspec-support 3.5.0
Using tilt 2.0.5
Using simplecov-html 0.10.0
Using timecop 0.8.1
Using tzinfo 1.2.2
Using nokogiri <IP_ADDRESS>
Using rack-test 0.6.3
Using rack-mini-profiler 0.10.1
Using sprockets 3.7.0
Using websocket-driver 0.6.4
Using mime-types 3.1
Using launchy 2.4.3
Using rack-canonical-host 0.2.2
Using autoprefixer-rails <IP_ADDRESS>
Using uglifier 3.0.3
Using babel-transpiler 0.7.0
Using bourbon 5.0.0.beta.7
Using bundler-audit 0.5.0
Using crack 0.4.3
Using rb-inotify 0.9.7
Using pry 0.10.4
Using rspec-core 3.5.4
Using rspec-expectations 3.5.0
Using rspec-mocks 3.5.0
Using simplecov 0.12.0
Using activesupport <IP_ADDRESS>
Using loofah 2.0.3
Using xpath 2.0.0
Using mail 2.6.4
Using sprockets-es6 0.9.2
Using bitters 1.4.0
Using webmock 2.1.0
Using listen 3.1.5
Using pry-byebug 3.4.0
Using pry-rails 0.3.4
Using rails-dom-testing 2.0.1
Using globalid 0.3.7
Using activemodel <IP_ADDRESS>
Using bullet 5.4.2
Using delayed_job 4.1.2
Using factory_girl 4.7.0
Using shoulda-matchers 3.1.1
Using skylight 1.0.0
Using spring 2.0.0
Using rails-html-sanitizer 1.0.3
Using capybara 2.7.1
Using recipient_interceptor 0.1.2
Using activejob <IP_ADDRESS>
Using activerecord <IP_ADDRESS>
Using spring-commands-rspec 1.0.4
Using actionview <IP_ADDRESS>
Using capybara-webkit 1.11.1
Using formulaic 0.3.0
Using delayed_job_active_record 4.1.1
Using actionpack <IP_ADDRESS>
Using actioncable <IP_ADDRESS>
Using actionmailer <IP_ADDRESS>
Using railties <IP_ADDRESS>
Using sprockets-rails 3.2.0
Using simple_form 3.3.1
Using dotenv-rails 2.1.1
Using factory_girl_rails 4.7.0
Using jquery-rails 4.2.1
Using rspec-rails 3.5.2
Using web-console 3.4.0
Using rails <IP_ADDRESS>
Using sass-rails 5.0.6
Using suspenders 1.42.0
Using title 0.0.7
Bundle complete! 42 Gemfile dependencies, 112 gems now installed.
Use `bundle show [gemname]` to see where a bundled gem is installed.
         run  bundle exec rails generate simple_form:install
W, [2016-11-04T08:45:44.143052 #62979]  WARN -- : [SKYLIGHT] [1.0.0] Running Skylight in development mode. No data will be reported until you deploy your app.
(To disable this message for all local apps, run `skylight disable_dev_warning`.)
[Simple Form] Simple Form is not configured in the application and will use the default values. Use `rails generate simple_form:install` to generate the Simple Form configuration.
SimpleForm 3 supports Bootstrap and Zurb Foundation 5. If you want a configuration that is compatible with one of these frameworks, then please re-run this generator with --bootstrap or --foundation as an option.
      create  config/initializers/simple_form.rb
       exist  config/locales
      create  config/locales/simple_form.en.yml
      create  lib/templates/erb/scaffold/_form.html.erb
Setting up the development environment
      insert  config/environments/test.rb
      insert  config/environments/development.rb
      insert  config/environments/development.rb
      insert  config/application.rb
       force  bin/setup
         run  chmod a+x bin/setup from "."
      create  lib/tasks/dev.rake
      insert  config/application.rb
        gsub  config/environments/development.rb
        gsub  config/environments/test.rb
      insert  config/application.rb
Setting up the test environment
      create  spec/support/factory_girl.rb
      create  spec/factories.rb
      create  .hound.yml
    generate  rspec:install
W, [2016-11-04T08:45:46.752678 #62995]  WARN -- : [SKYLIGHT] [1.0.0] Running Skylight in development mode. No data will be reported until you deploy your app.
(To disable this message for all local apps, run `skylight disable_dev_warning`.)
      create  .rspec
       exist  spec
      create  spec/spec_helper.rb
      create  spec/rails_helper.rb
      remove  spec/rails_helper.rb
      remove  spec/spec_helper.rb
      create  spec/rails_helper.rb
      create  spec/spec_helper.rb
         run  rails g delayed_job:active_record from "."
W, [2016-11-04T08:45:49.481019 #63018]  WARN -- : [SKYLIGHT] [1.0.0] Running Skylight in development mode. No data will be reported until you deploy your app.

Initialized empty Git repository in /private/tmp/projectname/.git/
Setting up database
       force  config/database.yml
         run  bundle exec rake db:create db:migrate
Created database 'projectname_development'
Created database 'projectname_test'
W, [2016-11-04T08:45:52.765987 #63043]  WARN -- : [SKYLIGHT] [1.0.0] Running Skylight in development mode. No data will be reported until you deploy your app.
(To disable this message for all local apps, run `skylight disable_dev_warning`.)
==<PHONE_NUMBER>4549 CreateDelayedJobs: migrating ================================
-- create_table(:delayed_jobs, {:force=>true})
   -> 0.0057s
-- add_index(:delayed_jobs, [:priority, :run_at], {:name=>"delayed_jobs_priority"})
   -> 0.0022s
==<PHONE_NUMBER>4549 CreateDelayedJobs: migrated (0.0081s) =======================

Creating local Heroku setup
      create  bin/setup_review_app
         run  chmod a+x bin/setup_review_app from "."
      create  bin/deploy
      append  README.md
         run  chmod a+x bin/deploy from "."
      create  app.json
Setting up Segment
      create  app/views/application/_analytics.html.erb
Setting up bundler-audit
      create  lib/tasks/bundler_audit.rake
      append  Rakefile
Springifying binstubs
         run  bundle exec spring binstub --all
* bin/rake: spring inserted
* bin/rspec: generated with spring
* bin/rails: spring inserted
         run  spring stop from "."
Spring is not running
    generate  suspenders:static
W, [2016-11-04T08:45:56.571491 #63073]  WARN -- : [SKYLIGHT] [1.0.0] Running Skylight in development mode. No data will be reported until you deploy your app.
(To disable this message for all local apps, run `skylight disable_dev_warning`.)
Running via Spring preloader in process 63094
     gemfile  high_voltage
         run  bundle install from "."
Resolving dependencies...
Using rake 11.3.0
Using concurrent-ruby 1.0.2
Using i18n 0.7.0
Using minitest 5.9.1
Using thread_safe 0.3.5
Using builder 3.2.2
Using erubis 2.7.0
Using mini_portile2 2.1.0
Using rack 2.0.1
Using nio4r 1.2.1
Using websocket-extensions 0.1.2
Using mime-types-data 3.2016.0521
Using arel 7.1.4
Using addressable 2.4.0
Using execjs 2.7.0
Using awesome_print 1.7.0
Using babel-source 5.8.35
Using sass 3.4.22
Using thor 0.19.1
Using uniform_notifier 1.10.0
Using bundler 1.13.6
Using byebug 9.0.6
Using json 2.0.2
Using coderay 1.1.1
Using safe_yaml 1.0.4
Using database_cleaner 1.5.3
Using debug_inspector 0.0.2
Using diff-lcs 1.2.5
Using docile 1.1.5
Using dotenv 2.1.1
Using method_source 0.8.2
Using ffi 1.9.14
Using flutie 2.0.0
Using hashdiff 0.3.0
Using high_voltage 3.0.0
Using honeybadger 2.7.0
Using rb-fsevent 0.9.8
Using ruby_dep 1.5.0
Using normalize-rails 3.0.3
Using pg 0.19.0
Using slop 3.6.0
Using puma 3.6.0
Using rack-timeout 0.4.2
Using rails_stdout_logging 0.0.5
Using rspec-support 3.5.0
Using tilt 2.0.5
Using simplecov-html 0.10.0
Using timecop 0.8.1
Using tzinfo 1.2.2
Using nokogiri <IP_ADDRESS>
Using rack-test 0.6.3
Using rack-mini-profiler 0.10.1
Using sprockets 3.7.0
Using websocket-driver 0.6.4
Using mime-types 3.1
Using launchy 2.4.3
Using rack-canonical-host 0.2.2
Using autoprefixer-rails <IP_ADDRESS>
Using uglifier 3.0.3
Using babel-transpiler 0.7.0
Using bourbon 5.0.0.beta.7
Using bundler-audit 0.5.0
Using crack 0.4.3
Using rb-inotify 0.9.7
Using pry 0.10.4
Using rspec-core 3.5.4
Using rspec-expectations 3.5.0
Using rspec-mocks 3.5.0
Using simplecov 0.12.0
Using activesupport <IP_ADDRESS>
Using loofah 2.0.3
Using xpath 2.0.0
Using mail 2.6.4
Using sprockets-es6 0.9.2
Using bitters 1.4.0
Using webmock 2.1.0
Using listen 3.1.5
Using pry-byebug 3.4.0
Using pry-rails 0.3.4
Using rails-dom-testing 2.0.1
Using globalid 0.3.7
Using activemodel <IP_ADDRESS>
Using bullet 5.4.2
Using delayed_job 4.1.2
Using factory_girl 4.7.0
Using shoulda-matchers 3.1.1
Using skylight 1.0.0
Using spring 2.0.0
Using rails-html-sanitizer 1.0.3
Using capybara 2.7.1
Using recipient_interceptor 0.1.2
Using activejob <IP_ADDRESS>
Using activerecord <IP_ADDRESS>
Using spring-commands-rspec 1.0.4
Using actionview <IP_ADDRESS>
Using capybara-webkit 1.11.1
Using formulaic 0.3.0
Using delayed_job_active_record 4.1.1
Using actionpack <IP_ADDRESS>
Using actioncable <IP_ADDRESS>
Using actionmailer <IP_ADDRESS>
Using railties <IP_ADDRESS>
Using sprockets-rails 3.2.0
Using simple_form 3.3.1
Using dotenv-rails 2.1.1
Using factory_girl_rails 4.7.0
Using jquery-rails 4.2.1
Using rspec-rails 3.5.2
Using web-console 3.4.0
Using rails <IP_ADDRESS>
Using sass-rails 5.0.6
Using suspenders 1.42.0
Using title 0.0.7
Bundle complete! 43 Gemfile dependencies, 113 gems now installed.
Use `bundle show [gemname]` to see where a bundled gem is installed.
    generate  suspenders:stylesheet_base
Running via Spring preloader in process 63121
     gemfile  bourbon (5.0.0.beta.6)
     gemfile  neat (~> 1.8.0)
     gemfile  refills
         run  bundle install from "."
Fetching gem metadata from https://rubygems.org/...........
Fetching version metadata from https://rubygems.org/..
Fetching dependency metadata from https://rubygems.org/.
You have requested:
  bourbon = 5.0.0.beta.6

The bundle currently has bourbon locked at 5.0.0.beta.7.
Try running `bundle update bourbon`

If you are updating multiple gems in your Gemfile at once,
try passing them all to `bundle update`
      create  app/assets/stylesheets/application.scss
      remove  app/assets/stylesheets/application.css
    generate  refills:import
You have requested:
  bourbon = 5.0.0.beta.6

The bundle currently has bourbon locked at 5.0.0.beta.7.
Try running `bundle update bourbon`

If you are updating multiple gems in your Gemfile at once,
try passing them all to `bundle update`
Run `bundle install` to install missing gems.
      remove  app/views/refills
         run  bitters install --path app/assets/stylesheets from "."
You have requested:
  bourbon = 5.0.0.beta.6

The bundle currently has bourbon locked at 5.0.0.beta.7.
Try running `bundle update bourbon`

If you are updating multiple gems in your Gemfile at once,
try passing them all to `bundle update`
Run `bundle install` to install missing gems.
Congratulations! You just pulled our suspenders.
Run 'bundle exec honeybadger heroku install' with your API key.
         run  bundle install
Fetching gem metadata from https://rubygems.org/...........
Fetching version metadata from https://rubygems.org/..
Fetching dependency metadata from https://rubygems.org/.
You have requested:
  bourbon = 5.0.0.beta.6

The bundle currently has bourbon locked at 5.0.0.beta.7.
Try running `bundle update bourbon`

If you are updating multiple gems in your Gemfile at once,
try passing them all to `bundle update`
         run  bundle exec spring binstub --all
You have requested:
  bourbon = 5.0.0.beta.6

The bundle currently has bourbon locked at 5.0.0.beta.7.
Try running `bundle update bourbon`

If you are updating multiple gems in your Gemfile at once,
try passing them all to `bundle update`
Run `bundle install` to install missing gems.

Any ideas?

Relevant error message:
You have requested:
  bourbon = 5.0.0.beta.6

The bundle currently has bourbon locked at 5.0.0.beta.7.
Try running `bundle update bourbon`

cc @tysongach

@jakecraige Is this from Suspenders master? Or 1.42.0?
Teo and I were just experiencing this.

@tysongach 1.42.0

I believe I’ve tracked down the issue, with the help of @teoljungberg.

Bitters is a dependency in the Suspenders gem.
Before Suspenders runs its stylesheet_base generator, Bitters gets installed, and it is currently installing 1.4.
Bitters 1.4 specifies Bourbon as a dependency.
With its current spec ("bourbon", ">= 5.0.0.beta.6"), Bitters 1.4 is coming with Bourbon 5.0.0.beta.7.
The problem is the stylesheet_base generator gets runs later in the Suspenders build process, and **in version 1.42.0 it is specifying a hard lock on Bourbon 5.0.0.beta.6.
Since Beta 7 is already packaged with Bitters, the stylesheet_base generator then fails.

So two things to fix:

I’ve already merged into master (yesterday) an upgrade to Bourbon 5.0.0.beta.7 for Suspenders, so we should cut that release.
I will also put a PR to Bitters to lock down the Beta version, instead of mapping to a >= version specifier. We can then better coordinate our releases in the future.

Or…should loosen the version specifier is Suspenders?
So, gem "bourbon", "5.0.0.beta.6" in the stylesheet_base generator matches what Bitters specifies (gem "bourbon", ">= 5.0.0.beta.6")?

Ping @tute. Any thoughts on the above?

I am not deep into the details of how our frontend pieces fit together or their release timelines yet to provide a definitive answer yet. In general, loosening dependency version requirements makes for easier to setup projects.
Two questions: Would >= work after we release 5.0? Does this problem arise because we are using beta versions, that don't play along with each other nicely?
We can chat in person too! :)

I’ve put up a PR to Bitters to loosen the version specifier: https://github.com/thoughtbot/bitters/pull/264
And done the same here on Suspenders: https://github.com/thoughtbot/suspenders/pull/806

@jakecraige Do you want to try v1.43 and see if your issue is indeed fixed?

@tysongach looks good! 👍


Command Line Python Interface

Since the CLI already backs the Python interface, we should make it so that you can invoke PSL using the installed python package.
We can just blind pass all the arguments to the CLI.
So something like:
python -m pslpython.cli --model ...

Complete in a38cffe5866f070f7db9665b5fa94f4f9d957a44.
(By Eriq and Vihang)


Parse file size in get_hf_file_metadata

Resolve https://github.com/huggingface/huggingface_hub/issues/1158.
This PR adds a size attribute to the output of get_hf_file_metadata.
RepoFile and HfFileMetadata are still 2 different objects doing related stuff (getting file info from API or from HEAD request on the file itself) but this PR is not meant to harmonize this.
(cc @Narsil who were requesting it)

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


fixup build-release.sh mix deps.get

mix deps.get is required before npm install otherwise the latter fails:
npm ERR! Could not install from "../deps/phoenix" as it does not contain a package.json file.
because ../deps/ doesn't exist.

Thanks!


Websocker server TLS cert expired

The LetsEncrypt cert used on https://royalur.net:9113/ has expired. I'm guessing it's the same actual cert as the main site but the app handling websockets hasn't been reloaded in 90 days.

Thanks for the heads up! I have restarted the server now, is that all that is needed to fix the TLS certificate?

Looks good now! Expiration Date: February 13, 2022. If you would like help setting up some basic monitoring, I want walk you through doing a free Uptime Robot account :)

That would be great! I've now created a free account on Uptime Robot

I'll jump in Discord and can help you with the setup :)


Additional factors to consider when moving away from github to the new docs feedback system

Since I'm unable to comment on Announcing a new way to give feedback on Microsoft Learn, here are some additional factors to be considered while moving the new feedback system. My concern is that making the feedback private, one way, customer to Microsoft but not back to the customer, may result in a reduced quality of the Azure documentation. Please take these points into account when designing the new private feedback system, so it does not inherit, or even aggravate these problems

Changes to documentation are delayed (possibly even lost) https://github.com/MicrosoftDocs/azure-docs/issues/121656
The customer waiting for a documentation update does not know when or if the update will happen. On github, there was a chance that the documentation maintainers would provide an answer directly in the github issue, so the customer was unblocked even before the documentation change was officially live https://github.com/MicrosoftDocs/azure-docs/issues/119982. There is also the github "Subscribe" button which allowed the customer to track the progress of the issue.
The requested documentation changes are denied https://github.com/MicrosoftDocs/azure-docs/issues/121010 and there is no further response from the maintainer
Documentation issues are assigned to inactive maintainers, or even these no longer employed at Microsoft https://github.com/MicrosoftDocs/azure-docs/issues/120405
Documentation issues discovered when working with commercial Azure support do not result in documentation updates https://techcommunity.microsoft.com/t5/azure/idea-require-support-agents-to-request-changes-to-the-public/m-p/3897405

@marcindulak
Thanks for your feedback! We will investigate and update as appropriate.


improve "exhausted attempts" diagnostics

motivation: better diagnostics when depdendcy graph fails to resolve. the "exhausted attempts" error message should normally not be encountered, other than in edge cases where the graph is not resolvable. nevertheless, it should be readable by users
changes:

conslidate the formatting of the "exhausted attempts" error message
format the "exhausted attempts" more clearly so it is more readable
update test

rdar://112134269

@swift-ci smoke test

@swift-ci smoke test

the test code has it

@swift-ci test

@swift-ci test