Icons all appear in same workspace on yabai v4

I've discussed this with koekeishiya here: https://github.com/koekeishiya/yabai/issues/1131
Whenever I go to a workspace, the icons for apps in that workspace will be added along with all others previously seen.

This issue appears at HEAD, but not at 297156c. I know that v4 is still unreleased so a new change must have been made to the query output that the latest release of simple-bar hasn't addressed yet.
My temporary solution is rolling back to that older yabai commit where simple-bar works, hopefully it'll be fixed soon.

Hi, thank you for reporting this! It seems that I've missed something while adding yabai v4 support, I'll look into it soon :)

This should be fixed on the latest yabai commit. :)


ConditionalHandler: delete value when no-longer-true-but-dependant-choosen

// issue stub
Delete a maybe-choosen value - like at #53 - when conditionals are failing, e.g. after they where true one time and the user choose a now visible dependant value but then removes the dependency again.
Should be for if, and their then/else and dependencies and dependantSchemas.
Should maybe rely on #63
Maybe build in logical conjunction with keywords, like:

additionalProperties: false deletes any then-non-existing-schema-key in the store, after conditional eval

Should support at least these use cases, configurable with schema:

delete value(s) when an evaluation is no longer valid
restore value(s) when an evaluation is valid again, only if it had transitioned to invalid before (to suppress e.g. default)

We're looking to build this out for our use case, any guidance on approach? Especially what kind of directives to use regarding the delete value(s) when an evaluation is no longer valid schema key. deleteOnInvalid?
We're looking to hit all of those points though for sure.

[ ] additionalProperties: false deletes any then-non-existing-schema-key in the store, after conditional eval
[ ] delete value(s) when an evaluation is no longer valid
[ ] restore value(s) when an evaluation is valid again, only if it had transitioned to invalid before (to suppress e.g. default)

An interesting pairing here we thought of is that since "not": { "required": ["title"] } results in a "this particular property is not allowed" which could then be deleted https://www.jsonschemavalidator.net/s/HK5LIn7t
That would allow you to switch between subschemas and forbid a certain property in a shared schema.


Revert "Return listenbuffer behavior"

This reverts commit 281a48d092fa84500c63b984ad45c59a06f301c4.
Fixes https://github.com/docker/docker/issues/18212.

Please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "18212-fix-api-server" git@github.com:crawford/docker.git somewhere
$ cd somewhere
$ git commit --amend -s --no-edit
$ git push -f

Ammending updates the existing PR. You DO NOT need to open a new one.

/cc @LK4D4 @calavera because changes here were introduced in https://github.com/docker/docker/pull/16825 and https://github.com/docker/docker/pull/16539

@crawford I still don't get issue :/ Why systemd starts serving before call of
SdNotify("READY=1")

@LK4D4 systemd starts listening as soon as the socket unit is started. It then hands this listening socket off to the daemon once someone connects. When Docker gets the listening socket, it starts serving immediately, before the routers have been initialized. The end result is a 404 from the daemon.

@crawford Yup, thank you, I wonder what is SdNotify at all :D

@LK4D4 systemd-notify is a mechanism for passing arbitrary information to PID 1. It is most commonly used with notify service types to indicate that a service is started.

@crawford thanks for explanation. I think about wrapping systemd sockets to listenbuffer as well, then there will be guarantee about daemon readiness. What do you think?

I don't think the listenbuffer is a good idea. As I said in https://github.com/docker/docker/issues/18212#issuecomment-159686537, the listenbuffer doesn't actually create an infinite queue. You are still limited by the socket backlog. The backlog is set to SOMAXCONN (usually 128) by default with socket units. You aren't going to do any better unless the listen buffer starts accepting connections and then stalling (which is a bad idea for many reasons).
Have you had trouble with the backlog limit in practice?

@crawford nope, I had no trouble, just tried to preserve previous behavior. I actually at one time wanted to remove listenbuffer, but then decided that it was there forever maybe for a reason.

I think it's better to remove it.
LGTM

Huge +1 to removing listenbuffer. In the long term, I would prefer that change to this one.

@crawford Yeah, but this change makes code little simpler. And it fixes particular issue with side-effect of making listenbuffer no-op, we'll remove it in next PR.

@LK4D4 Awesome, thank you.

LGTM


ci: remove elasticsearch from docker dependencies

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


Horizon v2.31.0 and RPC v21.4.0 changes

Please add support to your SDK for the following API changes.
Horizon Changes
Horizon v2.31.0 made the following changes:

New endpoint: POST /transactions_async allows asynchronous transaction submission (code: stellar/go#5188).
Error schema change: POST /transactions now includes a the hash in its timeout response, which may or may not require code changes depending on how your SDK handles transaction submission errors (code: stellar/go#5328).

Soroban RPC Changes
RPC v21.4.0 added the following endpoints:

getTransactions, which returns pages of transaction details (code: stellar/soroban-rpc#174).
getFeeStats, which returns aggregated fee statistics over a few ledgers (code: stellar/soroban-rpc#172).
getVersionInfo, which returns detailed information about the software versions the RPC server is running (code: stellar/soroban-rpc#132). Please keep in mind that this endpoint accidentally used snake_case for response fields and it will be updated to camelCase (see soroban-rpc#164) as part of Protocol 22's breaking changes when the time comes.

Reference

RPC documentation for getFeeStats.
RPC documentation for getTransactions.
RPC documentation for getVersionInfo.
Horizon documentation for /async_transactions.
JavaScript implementations: stellar-sdk#989 (/transactions_async) and stellar-sdk#1006 (/getFeeStats), both included in v12.2.0.

Hi @Shaptic, thanks for raising the issue. We've will look into this.

Support for new endpoint POST /transactions_async added in https://github.com/Beans-BV/dotnet-stellar-sdk/pull/28.
The rest added in https://github.com/Beans-BV/dotnet-stellar-sdk/pull/22.


Add SameIntervalMergeTask for easier usage of MergeTask

We generate several small segments each hour in realtime node, and want to merge all yesterday"s segments to only 1 segment.
MergeTask needs DataSegment list to be provided, which is painful in actual use.

@kaijianding, this generally looks good to me. Could you include a test, ideally one for behavior and one for serde of the task itself?

ut added, @gianm

still 👍  after latest changes. thanks for identifying and removing the unneeded code.

@kaijianding  you removed overriding of isReady(..) as well ... i thought it was good because segment list is automatically figured out so no need to fetch segment list again and match as is done in MergeTaskBase.isReady(..) ?

SubTask.run() is called directly inside SameIntervalMergeTask.run() after SameIntervalMergeTask.isReady() called.
In this way, I think SubTask is not submitted to task queue, so the isReady is not going to be called, that's why I removed isReady from SubTask. @himanshug

@kaijianding yeah, its fine then.


DBZ-6197 Remove duplicated createDdlFilter method from historized connector config

https://issues.redhat.com/browse/DBZ-6197

@harveyyue Applied, thanks!


Can't send messages from multiple (virtual) devices

OS and version used: Ubuntu 16.04.3 LTS

Python runtime used: 2.7.12

SDK version used:  2017_12_01

Description of the issue:

Introduction:
We're planning to implement monitoring solution with Azure IoT platform which is going to have a lot of devices running. As I understand, each device ("hardware") needs a name/key pair to be successfully recognized by IoT Hub and be able to send/receive messages. To that point, I see no problem to specify same pair for all devices, which could be as many as thousands (otherwise it would be quite hard to register each device individually, i.e. providing unique name/key pair).
Issue description:
Of course, before deploying solution on real devices, I want to experiment with virtual ones. I tried to create two virtual clients sharing same name/key pair and sending data to Hub asynchronously. What I see is only one of them actually sending data while another shows up with errors for each message. I didn't proceed with experimenting on "thousands" of devices as I'm sure I would face the same issue. For now, I'm not sure if that's problem of that specific SDK, but I could successfully emulate desired behaviour with 2 Node.js virtual devices (I can provide sample code if needed). Now, questions that do worry me:
-- is it possible to fix this issue and be able to emulate multiple virtual devices sharing same name/key pair?
-- won't we face the same problem when we start to deploy implemented solution with real devices?
Code sample exhibiting the issue:

from time import sleep
from iothub_client import IoTHubClient, IoTHubMessage, IoTHubTransportProvider

def callback(msg, res, context):
    pass

conn_string = ''  # my device connection string
protocol = IoTHubTransportProvider.MQTT
client = IoTHubClient(conn_string, protocol)
client2 = IoTHubClient(conn_string, protocol)
msg = IoTHubMessage(bytearray('hello'))  # one that doesn't come to Hub
msg2 = IoTHubMessage(bytearray('goodbye'))  # one that comes to Hub
while True:
    client.send_event_async(msg, callback, 0)
    # sleep(5)  # uncommenting that line won't help
    client2.send_event_async(msg2, callback, 0)
    sleep(5)

Console log of the issue:

Error: Time:Tue Dec 12 15:16:27 2017 File:/home/railsuleymanov/azure-iot-sdk-python/c/c-utility/adapters/socketio_berkeley.c Func:socketio_send Line:814 Failure: sending socket failed. errno=32 (Broken pipe).
Error: Time:Tue Dec 12 15:16:27 2017 File:/home/railsuleymanov/azure-iot-sdk-python/c/c-utility/src/tlsio_openssl.c Func:write_outgoing_bytes Line:628 Error in xio_send.
Error: Time:Tue Dec 12 15:16:27 2017 File:/home/railsuleymanov/azure-iot-sdk-python/c/c-utility/src/tlsio_openssl.c Func:tlsio_openssl_send Line:1357 Error in write_outgoing_bytes.
Error: Time:Tue Dec 12 15:16:27 2017 File:/home/railsuleymanov/azure-iot-sdk-python/c/umqtt/src/mqtt_client.c Func:sendPacketItem Line:332 1358: Failure sending control packet data
Error: Time:Tue Dec 12 15:16:27 2017 File:/home/railsuleymanov/azure-iot-sdk-python/c/umqtt/src/mqtt_client.c Func:mqtt_client_publish Line:1030 Error: mqtt_client_publish send failed
Error: Time:Tue Dec 12 15:16:27 2017 File:/home/railsuleymanov/azure-iot-sdk-python/c/iothub_client/src/iothubtransport_mqtt_common.c Func:publish_mqtt_telemetry_msg Line:777 Failed attempting to publish mqtt message

@suleymanov
Multiple devices cannot share the same name/key. Each device has to be a unique device registered on IoTHub. When you created all those devices on IoTHub you can run multiple software client (even on the same machine) and send message from each client to IoTHub.
Best Regards,
Zoltan


Running Empire under Mac OS X

Trying to install Empire under MacOSX v10.10.4
read the install.sh script to see what the dependencies are
installed what was missing.
when I launch empire I get:
MANDIANT> ../empire
Traceback (most recent call last):
File "../empire", line 6, in
from lib.common import empire
File "/Applications/GITLIST-PACKAGES/Empire/lib/common/empire.py", line 22, in
import http
File "/Applications/GITLIST-PACKAGES/Empire/lib/common/http.py", line 18, in
import encryption
File "/Applications/GITLIST-PACKAGES/Empire/lib/common/encryption.py", line 12, in
import base64, hashlib, hmac, string, M2Crypto
File "build/bdist.macosx-10.10-intel/egg/M2Crypto/init.py", line 24, in
File "build/bdist.macosx-10.10-intel/egg/M2Crypto/ASN1.py", line 12, in
File "build/bdist.macosx-10.10-intel/egg/M2Crypto/BIO.py", line 221, in
File "build/bdist.macosx-10.10-intel/egg/M2Crypto/BIO.py", line 227, in CipherStream
AttributeError: 'module' object has no attribute 'PKCS5_SALT_LEN'
was hoping you could smack me in the head and tell me what stupid thing I've done (other than trying to run it under MacOSX of course ;-)

We have only tested Empire under Ubuntu 14.04 LTS and Kali Linux. We will get OSX tested shortly

Hi,
Just for the record I have Empire running on Arch Linux :)
Dave
On 14 August 2015 at 13:53, enigma0x3<EMAIL_ADDRESS>wrote:

We have only tested Empire under Ubuntu 14.04 LTS and Kali Linux. We will
get OSX tested shortly
—
Reply to this email directly or view it on GitHub
https://github.com/PowerShellEmpire/Empire/issues/15#issuecomment-131096677
.

--
Best Regards
David Hardy
Follow Me on Twitter @davehardy20 http://twitter.com/davehardy20 LinkedIn
Profile http://uk.linkedin.com/pub/david-hardy/6/388/2a2 pentest-N00b Blog
http://pentestn00b.wordpress.com/

Awesome! no issues?

Nope, just added the dependencies and it ran first time, only issue I've
had is the one with the DLL payload and Metasploit, but that's not an
empire issue.
Dave
On 14 August 2015 at 14:03, enigma0x3<EMAIL_ADDRESS>wrote:

Awesome! no issues?
—
Reply to this email directly or view it on GitHub
https://github.com/PowerShellEmpire/Empire/issues/15#issuecomment-131098925
.

--
Best Regards
David Hardy
Follow Me on Twitter @davehardy20 http://twitter.com/davehardy20 LinkedIn
Profile http://uk.linkedin.com/pub/david-hardy/6/388/2a2 pentest-N00b Blog
http://pentestn00b.wordpress.com/

Thanks @davehardy20!
@macubergeek,
We have decided that for the time being, version 1.0 will only support Kali Linux. This is due to development and testing time. Once Empire becomes aged and stable, we will revisit multi-platform support.

@enigma0x3 @macubergeek hey guys, just FYI the reason for that error is that the m2crypto bindings break when using swig > 3.0.4, the only solution at the moment seems to be downgrading, I'm running into this error myself running Arch linux

see https://github.com/swig/swig/issues/344 as reference

after more digging it seems that a pull request was submitted to fix this but it hasn't been merged yet https://github.com/martinpaljak/M2Crypto/pull/75

FWIW i got Empire launching (not fully tested) on OSX 10.10 with swig 3.0.4 (you can download from their archives page) and pip install M2Crypto==0.21.1 - both older versions that work around this bug.

Good to hear!


[autochunk] support diffusion for autochunk

📌 Checklist before creating the PR

[x] I have created an issue for this PR for traceability
[x] The title follows the standard format: [doc/gemini/tensor/...]: A concise description
[x] I have added relevant tags if possible for us to better distinguish different PRs

🚨 Issue number

Link this PR to your issue with words like fixed to automatically close the linked issue upon merge
e.g. fixed #1234, closed #1234, resolved #1234

#2620
📝 What does this PR do?

Summarize your work here.
if you have any plots/diagrams/screenshots/tables, please attach them here.

Support diffusion for autochunk. Reduce over 70% memory.

support some ops for diffusion, such as groupnorm, interpolate and conv.
refact some logic to fit diffusion
update test for diffsuion

💥 Checklist before requesting a review

[x] I have linked my PR to an issue (instruction)
[x] My issue clearly describes the problem/feature/proposal, with diagrams/charts/table/code if possible
[x] I have performed a self-review of my code
[x] I have added thorough tests.
[x] I have added docstrings for all the functions/methods I implemented


Traits

Adds the ability to filter the test list based on the traits attached to test cases.
This is my first real venture into WPF based MVVM.  I followed the existing patterns where applicable and consulted tutorials for the new ones I needed to establish (in particular how to communicate selection information).  Let me know if there is anything I got wrong here.
closes #7

Closing because it's getting too hard to mange this and #22.  Just going to let #22 hold both of the features.  All the feedback will be addressed in that PR.


Insert/Edit documents with JSON editor vs Inline table edit vs Data explorer

This is something that was always missing for many people. though the Data explorer is very nice and powerful tool, it is not very intuitive or handy if you just want to insert/edit/delete some documents without writing complex ReQL queries.
Robo 3T has it:

Fauxton (CouchDB admin) has it:

ReQL pro got both editor and inline table editing:

I Think we should support both the current Data Explorer, Editable table view and Document editor.

These is defiantly nice to have, I think it's a low priority.
https://github.com/neumino/chateau lets you easily do all this and it's pretty easy to set up and it's code is pretty solid. I think we should bring it into the org and find ways to promote it.


docs: include README.md

Description
Include README.md in documentation.

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


Update to v6.54.0 - upstream provider to v4.61.0

What's the deal with the Firebase revert? Is that something to watch out for in future upgrades?

Yes - it, similar to reverts in the previous version, are due to the GCP TF provider moving to plugin framework for some resources / data sources.


Save final checkpoint (and final model?) also in output folder

Otherwise they risk being overwritten by other runs

Another options would be to backup the files
model.pt -> model.pt.1
model.ckpt -> model.ckpt.1

and if there is already a backed up file we can do something like
model.pt.1 -> model.pt.2
model.ckpt.1 -> model.ckpt.2

We should then also display a message in the log like Backed up model.pt to ./model.pt.1
I think @ceriottm is doing something like this in i-PI by overwriting some default Python operations...

Yes this is how it's done in ipi


mark.js builds very large and invalid regex when UTF-8 header is not present

When used in Electron, and when no UTF-8 header is present, Mark.js builds very strange regular expressions that fail to find the requested keywords.
Steps to reproduce
Unfortunately I cannot replicate it in jsFiddle but it always happens in Electron. The web page I'm trying to render originally didn't have a <meta charset="UTF-8"> in  the headers and when I was trying mark.js would mark some words but not others. Eventually I found that for words that include vowels, mark.js would generate a massive regular expressions that would fail to match the required keyword.
For example for "table", mark.js would generate this regular expression:
https://gist.github.com/laurent22/3c4a141f926a4b4483a55c380166470e
However, if I add the <meta charset="UTF-8"> header, it would build the correct regex (again, for "table"):
()([tťțţTŤȚŢ][aàáảãạăằắẳẵặâầấẩẫậäåāąAÀÁẢÃẠĂẰẮẲẴẶÂẦẤẨẪẬÄÅĀĄ]b[lłLŁ][eèéẻẽẹêềếểễệëěēęEÈÉẺẼẸÊỀẾỂỄỆËĚĒĘ])
The initialisation code I'm using is this:
mark_ = new Mark(document.getElementById('content'), {
	exclude: ['img'],
	acrossElements: true,
});

If I can help fixing this or do more tests, please let me know.
Environment

Electron 1.7.11
mark.js v8.11.1

Hi @laurent22,
Thanks for submitting.
This behavior is as expected, diacritics require UTF8. There's also a hint in the documentation:

Note: mark.js requires UTF-8 encoding. If your server or environment serves files with ASCII, you can workaround this behavior by using the charset attribute on above named


Buying jutsu from shop doesn't check if jutsu is already owned, wasting money if page is reloaded

Bounty: $10

Looks like this is caused by only checking if the jutsu is learned and not for jutsu scroll in inventory.
store.php line 126:
// check if already owned
if($player->hasJutsu($jutsu_id)) {
	throw new Exception("You have already learned this jutsu!");
}

Possible fix by first adding helper function to user.php:
public function hasJutsuScroll(int $jutsu_id): bool {
	return isset($this->jutsu_scrolls[$jutsu_id]);
}

Then adding additional check to store.php
// check if jutsu scroll owned
if($player->hasJutsuScroll($jutsu_id)) {
	throw new Exception("You already own this jutsu scroll!");
}

Will test when I have time to set up dev.


Fix: avoid double-rendering sql_header in dbt show

resolves #8739

Problem

Solution

Checklist

[x] I have read the contributing guide and understand what's expected of me
[x] I have run this code in development and it appears to resolve the stated issue
[x] This PR includes tests, or tests are not required/relevant for this PR
[x] This PR has no interface changes (e.g. macros, cli, logs, json artifacts, config files, adapter interface, etc) or this PR has already received feedback and approval from Product or DX
[x] This PR includes type annotations for new and modified functions

Updated BQ test: https://github.com/dbt-labs/dbt-bigquery/pull/927

Updated redshift test: https://github.com/dbt-labs/dbt-redshift/pull/611

Updated snowflake test: https://github.com/dbt-labs/dbt-snowflake/pull/779


Unknown ODBC error. Mac OS. r-exasol

I am trying to connect exasol with R with the following code. The problem occurs with Mac OS.
library(RODBC)
library(exasol)

con <- dbConnect("exasol", **)
 # removed the connection credentials

df1 <- dbGetQuery(con,paste("query", sep=""))
 # removed the query

Error in try(.Call(C_asyncRODBCQueryFinish, slot, 1)) :
  Unknown ODBC error
Error in exa.readData(conn, statement, ...) :
  Could not allocate SQLAllocHandle (-2)
Error in exa.readData(conn, statement, ...) : Unknown ODBC error`

My system is Mac OS "x86_64" .  Please can you help resolving this. ?

I'm also facing the same issue, I believe it is duplicate of https://github.com/exasol/r-exasol/issues/32
Tried both libiodbc and unixodbc

Hey all,
I am going to close this ticket. Please try out with the updated versions.
Please open another ticket if the issue still persists.

Root cause seems to be some binary incompatibilty of RODBC package of the MacOsX version on CRAN.
Reinstalling with install.packages("RODBC", type="source")" resolves the issue.


bump BSK for<EMAIL_ADDRESS>

Task/Issue URL:
Tech Design URL:
CC:
Description:
Steps to test this PR:
1.

Definition of Done:

[ ] Does this PR satisfy our Definition of Done?

Internal references:
Pull Request Review Checklist
Software Engineering Expectations
Technical Design Template
Pull Request Documentation

#3136  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @shakyShane and the rest of your teammates on  Graphite


Error 'cannot find NIC starting with name 'eth'

Farmer wants to migrate his node to v2, has a Windows laptop but has set up a VM with Ubuntu on top. From there, executing the script, launched kosmos but got error with j.tools.threebot.init_my_threebot :

Set priority to 'major' as it happened to a farmer that wants to migrate his farm to zOSv2 using instructions


Feature Request:  Simplify creating and maintaining renv.lock

Feature Idea
Manually updating the renv.lock is tedious because it is not clear if an entry is required by admiral core or the extension package.
I would propose

to add a package.lock file which contains only those packages which are required by the extension package but not by admiral core (or other admiral extension packages) and
to implement a function in admiral or admiraldev which collates the packages from package.lock and the renv.lock files of all admiral packages the extension package is depending on and writes the renv.lock file.

Open question: Should the renv.lock contain other admiral packages?
Relevant Input
No response
Relevant Output
No response
Reproducible Example/Pseudo Code
No response

I prefer to keep all dependencies in the lock file but in that case the staged_dependencies will not be used.
I do not get this idea for having the multiple lock file. I understand the possibility for optimization  but in that case, we can try with profiles.
For easy generating renv.lock file you probably would like to use explicit option.
The explicit option will collect the packages but omit Suggest one and it's mainly correct behaviour.
package.dependency.fields: Imports, Depends, LinkingTo

We can not add Suggests packages to discover as we only want to get the Suggests packages from admiraldev.
Solution:

Create custom field in admiraldev e.g. SuggestsAdmiral - not nice duplicate record in DESCRIPTION
Use custom method for renv discovery

.get_dependencies <- function(project_dir) {
  admdev_loc <- find.package("admiraldev", lib.loc = .libPaths(), quiet = TRUE)
  adm_dev_suggests <- renv:::renv_dependencies_discover_description(admdev_loc, fields = "Suggests")

  names(renv:::renv_package_dependencies(c(project_dir, adm_dev_suggests[["Package"]])))
}

options(renv.snapshot.filter = .get_dependencies)

The snapshot type should be set to customsnapshot.type: custom in renv/settings.dcf.
Summary:
We can collect packages

"explicit" - Only capture packages which are explicitly listed in the project DESCRIPTION file.  [1]

and add as extra packages Suggest packages from admiraldev.
The packages scope is a little bit bigger as now renv iterating  on packages from DESCRIPTIONs not doing renv::dependency discovery.
@bundfussr please check if this solution fits your need. It's really simple to implementation and can be part of .Rprofile.

@galachad , thanks for the feedback. I think this issue is not up to date. Meanwhile we decided to use a single lock file for all admiral repositories.
The lock file should contain all packages which are imported or suggested by any of the admiral packages. The version of the packages should be the one which was  available when the R version we are using for development was released. At the moment we use R 4.0. I.e., we would store the version in the lock which was available when R 4.0 was released.
There should be an option to use newer versions for some packages. For example, we use a newer version of pkgdown.
The admiral packages should not be in the lock file because these are handled by staged_dependencies.

Can we close this issue?

@bms63 , yes, I think we should create an issue for the renv.lock generation in admiralci.

I have created https://github.com/pharmaverse/admiralci/issues/51 for further discussion.


CLI compilation error using command

When compiling the rust source code using command: cargo build -p typst-cli --release
the following error occurred:
error: Permission denied (os error 13) at path "/home/alistair/typst/typst-22-03-21-2/targetdjGuyy"
I had just updated my rust installation to rustc 1.68.0 (2c8cc3432 2023-03-06)

Did this issue persist? Can you provide more information on your configuration, i.e. what permissions your file has and which command you ran?

Seems like a problem with your local file system, not Typst itself.


Exception for diagnostic scope is added.

Because we are adding the scope in the protocol method if an exception happens in the convenience method no diagnostic scope is created.  In order to work with our test framework we either need to add ForwardsClientCallsAttribute or add the scope creation to the convenience method and conditionally add the scope in the protocol if it wasn't added in the convenience method.

Hi @m-nash do we still need to do this? if so could you please provide more information on this?

We did not get feedback about what this is for, therefore temporarily closed this. Feel free to reopen or open a new one if we still need to fix this in the future


Unable to install python-dev

Problem/Motivation
Many Python packages require python3-dev to install, however I seem to be unable to install it. I think it could be argued that it should be included by default. However, some guidance on how to install it would be appreciated.
Apologies, this could be more of a question than a bug depending how you look at it.
I do think this is a regression, as installing python3-dev did work previously. I am not sure which release caused the issue as I have not been paying enough attention, but possibly either v0.2.0 or v0.2.1 (Sorry, I would normally pay more attention but I have a 5 day old!)
Expected behavior
The following config to install python3-dev
system_packages:
  - python3-dev

Actual behavior
ERROR: unsatisfiable constraints:
  python3-3.8.1-r0:
    breaks: python3-dev-3.8.2-r0[python3=3.8.2-r0]
    satisfies: world[python3=3.8.1-r0]
[14:20:02] FATAL: Failed installing package python3-dev

My guess would be that it is related to the change in the base image in 0.2.0?

The python version and dev version don't match. If you want to ensure that, you need to install both python & python-dev.

Aha, that worked! So just to be clear, for anyone that finds this, you need to do this;
system_packages:
  - python3
  - python3-dev

Thanks for that, I am not too familiar with apk.

I've just pushed an update to dev to upgrade Python & AppDaemon to the latest versions. Will do a release later today.


Enhance the robustness of the program

Enhance the robustness of the program, flip the equals method, and prevent NPE.
eg:
field.defaultString().equals("null")  -> "null".equals(field.defaultString())

Hey @likeyoukang
Thank you for your first contribution. Could you please rebase this PR from trunk? And also change the title of the PR to "MINOR: Use "constant equals object" instead of "object equals Constant""


Include license file in the distributed files

Use MANIFEST.in to include LICENSE in the generated source distribution.
The wheel package format supports including the license file. This is done using the [metadata] section in the setup.cfg file. For additional information on this feature, see:
https://wheel.readthedocs.io/en/stable/index.html#including-the-license-in-the-generated-wheel-file
Fixes #12

Rebased to fix Travis failures

@gsnedders, looks like no release has happened after this. Can you tag a release, or otherwise cause the LICENSE file to propagate to wpt?


fix(nuxt): Nuxt 3 throws error on build & dev

🔗 Linked issue
closes #1135

❓ Type of change

[ ] 📖 Documentation (updates to the documentation or readme)
[ ] 🐞 Bug fix (a non-breaking change that fixes an issue)
[ ] 👌 Enhancement (improving an existing functionality like performance)
[ ] ✨ New feature (a non-breaking change that adds functionality)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

📝 Checklist

[ ] I have linked an issue or discussion.
[ ] I have updated the documentation accordingly.

unfortunately still the same error, no change
updated about module pinia-orm and @pinia-orm/nuxt


about the Version of keras and tensorflow

python train_full.py --img_file=data/images-128.npy --mask_file=data/masks-128.npy

... ...
File "/home/.local/lib/python2.7/site-packages/tensorflow/python/layers/base.py", line 1376, in init
layer.outbound_nodes.append(self)
AttributeError: 'Activation' object has no attribute 'outbound_nodes'

hi， I run the training code above，got an error，could tell me the version of keras and tensorflow ？Thank you!
My Version:  Keras:2.2.0   Tensorflow:1.8.0

Hi,
I had the same issue. Not sure why this is happening but downgrading to 2.1.1 solved this issue for me. PS:- I am also using tensorflow 1.8.0

Hi, I have rewrite code using PyTorch 0.4.1. It's much simpler than before.


Make efivarfs read-only by default

I have become aware of https://github.com/systemd/systemd/issues/2402. It sounds very concerning that someone can brick his motherboard simply by running rm as root, so I propose we add some protection against that. My idea is as follows:

Make efivarfs read-only via fstab, as was proposed in the upstream issue.
Patch software that needs access to it to clone a new filesystem namespace and remount efivarfs read-write there. Namespace ensures that it will be read-write only for that process and that it will be cleant up automatically.

So far I can think of very few software that needs such patching:

systemctl --firmware-setup reboot(I have no idea what this does)
efibootmgr
grub-install, but if I remember correctly it works through efibootmgr

The patch would consist of only three consecutive syscalls (I did things like that in our userspace FHS chroot).
I'm willing to implement necessary changes, but I want to know if the community agrees with my concern first, as the issue is somewhat controversial.
Note that I'm very much against discussing whether upstream did the right thing here! Please, let's not continue the flame war and instead agree on whether we want this or not.

I understand what is being proposed as an issue completely. And I do not agree that anything needs to be done in response.

I'm :+1: on making it read-only.

Am I correct in understanding that your proposal is to prevent people who have purchased hardware which claims to have EFI but which does not have an EFI implementation as per the official specification (of which there are very few) from deleting efivarfs as pid 1?

Yes. My arguments are:

Vendors don't provide any information on whether their hardware actually implements the spec good enough (who would say that their hardware is shitty?), so you likely won't know you have broken firmware until it's too late;
rm -rf / is more likely that you think. For example, I've run that to destroy my system before a system reinstall (because why not, I thought, I'll get to see what happens to the system and it's doomed anyway), and also inside our FHS chroot during debugging (which has /sys mounted). If I would have had broken hardware, I would have used another laptop now ~_^. rm shouldn't be able to brick a motherboard just like that, in my opinion;
Steps required to protect people from that are trivial (add a line to fstab and patches to several pieces of software which actually write something to it, see above);
Steps required to bypass this are also trivial (mount -o rw,remount).

Overall, I think effort and inconvenience for us would be low, while possible gratitude of people whose hardware we would save is priceless.

You could even make wrappers for those programs which create a namespace
and remount inside the namespace, run the application, then tear down. That
should be easier than to maintain software specific code.
On Sat, Jan 30, 2016 at 10:37 AM Nikolay Amiantov<EMAIL_ADDRESS>wrote:

Yes. My arguments are:

Vendors don't provide any information on whether their hardware
actually implements the spec good enough (who would say that their hardware
is shitty?), so you likely won't know you have broken firmware until it's
too late;
rm -rf / is more likely that you think. For example, I've run that
to destroy my system before a system reinstall (because why not, I thought,
I'll get to see what happens to the system and it's doomed anyway), and
also inside our FHS chroot during debugging (which has /sys mounted).
If I would have had broken hardware, I would have used another laptop now
~_^. rm shouldn't be able to brick a motherboard just like that, in my
opinion;
Steps required to protect people from that are trivial (add a line
to fstab and patches to several pieces of software which actually
write something to it, see above);
Steps required to bypass this are also trivial (mount -o rw,remount).

Overall, I think effort and inconvenience for us would be low, while
possible gratitude of people whose hardware we would save is priceless.
—
Reply to this email directly or view it on GitHub
https://github.com/NixOS/nixpkgs/issues/12697#issuecomment-177268783.

:+1:

:+1:

@abbradar I am still not seeing a case for preventing anyone doing anything accidentally as pid 1.
You can tell if your system is effected by testing it by long pressing the power button to boot until you hear the beeps from the speaker and or reading the manual which came with your system or main board to confirm. It should provide you with the hard reset method.
The number of systems that are effected is very low.
Where possible hardware vendors have released firmware updates to address the problem.

@heydojo the question is what's the cost/benefit ratio? How many people even know about the bug linked in the topic, first of all? Are the people who don't know going to know to press the long power button to test if their EFI is implemented properly? Furthermore, what is the benefit of having it be RW by default? To make a couple of rarely used programs a little more convenient? Given the potential downsides, the difficulty of discovering the problem in the first place, and the dubious benefits of keeping RW turned on by default, it seems weird to me to advocate keeping it RW by default. It feels like a violation of least-privilege that could be fairly costly in (admittedly very few, but not zero) real scenarios.
What are your reasons for wanting it on by default?

What are your reasons for wanting it on by default?

If it ain't broke. Don't fix it. As pid 1 you are supposed to be able to be able to do everything.
I don't object to the proposal.
I just disagree that it is necessary.

As pid 1 you are supposed to be able to be able to do everything

I don't generally expect to be able to brick the computer via regular file operations without jumping through some serious hoops, even as root.

The number of machines effected by incorrect efi implementation in this respect is too low to generally expect to be able to brick your efi system.
Turning off a machine and turning it on again and or reading a manual is not what I would consider jumping through hoops.
I can only assume that this reaction by people is the result of a misunderstanding and a forming of bad habits using pid 1. I could just sit here and keep re-iterating that I know that this proposal is unnecessary but it appears that it would also be a waste of all our time.
So I'm going to leave the thread now because I think that the whole "issue" is quite funny and if it makes people feel safer when they are deleting things as pid 1 please go ahead with the proposal.
It is not my place to tell people to drop their bad habits. I have better things to do.

@heydojo Sorry for summoning you again but I'm interested in your argument about turning the machine off and on (let's agree we disagree on the general "safety net for uid 1" thing, UID 1 nowadays is misunderstood widely and people indeed have a lot of bad habits). If I understand correctly, the issue is that there are some things exposed as EFI variables, that are (a) not expected to be touched at all by the vendor, (b) are not touched by Windows, Linux (in normal circumstances) and other OSes, (c) persist through hard reset and are linked to some place in EEPROM instead of normal CMOS memory and (d) render system unusable if removed. One purely hypothetical example I can come up with is firmware checksums. Why do you think this can be found out by resetting the machine or reading manuals? I must admit I have not fully read original Arch thread about the issue so I may have misunderstood something.

@abbradar this is the last time I am jumping in on this thread because of the nature of it and your response is actually a good question.
The variables are there to be changed if you want. Some are important. If they are deleted accidentally because someone thought that logging in as pid 1 and deleting things they do not understand would be fun then a person who does such a thing probably won't stop at deleting efi variables by accident and there is nothing anyone can do for that person. They stand to destroy their entire operating system on their own anyway, if they do not learn the error of their ways.
The reason to hard reset or read the manual for the machine or board is purely to find out if the machine has an efi reset. Not if that reset restores the variables. But it should.
The issue is that some vendors did not provide a reset method. It is just unfortunate for the very small number of people who bought hardware which claimed efi support but did not follow the spec and add a hard reset to their efi implementation.
I was a very early adopter of efi on the desktop (it has existed in servers way before) the machine I built for personal use at the time, I actually deliberately chose an Intel main board to base the system from not only for quality and reliability reasons but because it was one of the first commercially available desktop boards advertising efi.
I read the efi spec at the time. I also worked as a hardware engineer the last seven years.
So I am saying this is a non-issue.

@heydojo Thanks for your detailed answer! Interesting -- indeed, this way one can find out some level of conformance to the standard.
I still respectfully disagree with your views on PID 1 and safety nets around it, but indeed let's not reiterate now (though I love a good dispute ~_^). Thanks again!

For more information on the topic: https://twitter.com/mjg59/status/693494314941288448
Led to this:
https://gist.github.com/mjg59/8d9d494da56fbe6d8992

triage: I guess this can be closed?

@Profpatsch (from triage too) On a (18.03) machine efivarfs appears to still be mounted read-write, so I'd guess this isn't solved yet? Unless the gist posted by @copumpkin was actually a commit to the linux kernel, but I can't find either 3f5e3bdb or “Block most UEFI” in my local clone.
So I'd say this is still an ongoing issue, that has seen rough consensus in favor of making efivarfs read-only (to which I adhere)?


Error while cross-compiling...

In file included from /home/user/ALPHABOX/alpha-app/app/recorder/main.cpp:27:0:
/home/user/ALPHABOX/alpha-app/app/recorder/backward.hpp:1938:3: warning: #warning ":/ sorry, ain't know no nothing none not of your architecture!"
/home/user/ALPHABOX/alpha-app/app/recorder/backward.hpp: In static member function 'static void backward::SignalHandling::sig_handler(int, siginfo_t*, void*)':
/home/user/ALPHABOX/alpha-app/app/recorder/backward.hpp:1929:15: warning: unused variable 'uctx'
In file included from /home/user/SDK/linux/linux-current/ti-sdk-am335x-evm-<IP_ADDRESS>/linux-devkit/bin/../lib/gcc/arm-arago-linux-gnueabi/4.5.3/../../../../arm-arago-linux-gnueabi/include/c++/4.5.3/bits/move.h:38:0,
from /home/user/SDK/linux/linux-current/ti-sdk-am335x-evm-<IP_ADDRESS>/linux-devkit/bin/../lib/gcc/arm-arago-linux-gnueabi/4.5.3/../../../../arm-arago-linux-gnueabi/include/c++/4.5.3/bits/stl_pair.h:60,
from /home/user/SDK/linux/linux-current/ti-sdk-am335x-evm-<IP_ADDRESS>/linux-devkit/bin/../lib/gcc/arm-arago-linux-gnueabi/4.5.3/../../../../arm-arago-linux-gnueabi/include/c++/4.5.3/bits/stl_algobase.h:66,
from /home/user/SDK/linux/linux-current/ti-sdk-am335x-evm-<IP_ADDRESS>/linux-devkit/bin/../lib/gcc/arm-arago-linux-gnueabi/4.5.3/../../../../arm-arago-linux-gnueabi/include/c++/4.5.3/bits/char_traits.h:41,
from /home/user/SDK/linux/linux-current/ti-sdk-am335x-evm-<IP_ADDRESS>/linux-devkit/bin/../lib/gcc/arm-arago-linux-gnueabi/4.5.3/../../../../arm-arago-linux-gnueabi/include/c++/4.5.3/ios:41,
from /home/user/SDK/linux/linux-current/ti-sdk-am335x-evm-<IP_ADDRESS>/linux-devkit/bin/../lib/gcc/arm-arago-linux-gnueabi/4.5.3/../../../../arm-arago-linux-gnueabi/include/c++/4.5.3/ostream:40,
from /home/user/SDK/linux/linux-current/ti-sdk-am335x-evm-<IP_ADDRESS>/linux-devkit/bin/../lib/gcc/arm-arago-linux-gnueabi/4.5.3/../../../../arm-arago-linux-gnueabi/include/c++/4.5.3/iostream:40,
from /home/user/ALPHABOX/alpha-app/app/recorder/main.cpp:4:
/home/user/SDK/linux/linux-current/ti-sdk-am335x-evm-<IP_ADDRESS>/linux-devkit/bin/../lib/gcc/arm-arago-linux-gnueabi/4.5.3/../../../../arm-arago-linux-gnueabi/include/c++/4.5.3/type_traits: At global scope:
/home/user/SDK/linux/linux-current/ti-sdk-am335x-evm-<IP_ADDRESS>/linux-devkit/bin/../lib/gcc/arm-arago-linux-gnueabi/4.5.3/../../../../arm-arago-linux-gnueabi/include/c++/4.5.3/type_traits: In instantiation of 'const bool std::__is_convertible_helper<backward::SourceFile, backward::SourceFile, false>::__value':
/home/user/SDK/linux/linux-current/ti-sdk-am335x-evm-<IP_ADDRESS>/linux-devkit/bin/../lib/gcc/arm-arago-linux-gnueabi/4.5.3/../../../../arm-arago-linux-gnueabi/include/c++/4.5.3/type_traits:312:5:   instantiated from 'std::is_convertible<backward::SourceFile, backward::SourceFile>'
/home/user/SDK/linux/linux-current/ti-sdk-am335x-evm-<IP_ADDRESS>/linux-devkit/bin/../lib/gcc/arm-arago-linux-gnueabi/4.5.3/../../../../arm-arago-linux-gnueabi/include/c++/4.5.3/bits/stl_map.h:451:11:   instantiated from 'mapped_type& std::map<_Key, _Tp, _Compare, _Alloc>::operator[](const key_type&) [with _Key = std::basic_string, _Tp = backward::SourceFile, _Compare = std::less<std::basic_string >, _Alloc = std::allocator<std::pair<const std::basic_string, backward::SourceFile> >, mapped_type = backward::SourceFile, key_type = std::basic_string]'
/home/user/ALPHABOX/alpha-app/app/recorder/backward.hpp:1647:49:   instantiated from here
/home/user/SDK/linux/linux-current/ti-sdk-am335x-evm-<IP_ADDRESS>/linux-devkit/bin/../lib/gcc/arm-arago-linux-gnueabi/4.5.3/../../../../arm-arago-linux-gnueabi/include/c++/4.5.3/type_traits:302:71: error: no matching function for call to 'backward::SourceFile::SourceFile(backward::SourceFile)'
/home/user/ALPHABOX/alpha-app/app/recorder/backward.hpp:1481:2: note: candidates are: backward::SourceFile::SourceFile(const std::string&)
/home/user/ALPHABOX/alpha-app/app/recorder/backward.hpp:1480:2: note:                 backward::SourceFile::SourceFile()
/home/user/SDK/linux/linux-current/ti-sdk-am335x-evm-<IP_ADDRESS>/linux-devkit/bin/../lib/gcc/arm-arago-linux-gnueabi/4.5.3/../../../../arm-arago-linux-gnueabi/include/c++/4.5.3/type_traits:302:71: error:   initializing argument 1 of 'static std::__sfinae_types::__one std::__is_convertible_helper<_From, _To, false>::__test(_To) [with _From = backward::SourceFile, _To = backward::SourceFile, std::__sfinae_types::__one = char]'
/home/user/SDK/linux/linux-current/ti-sdk-am335x-evm-<IP_ADDRESS>/linux-devkit/bin/../lib/gcc/arm-arago-linux-gnueabi/4.5.3/../../../../arm-arago-linux-gnueabi/include/c++/4.5.3/type_traits: In instantiation of 'std::is_convertible<backward::SourceFile, backward::SourceFile>':
/home/user/SDK/linux/linux-current/ti-sdk-am335x-evm-<IP_ADDRESS>/linux-devkit/bin/../lib/gcc/arm-arago-linux-gnueabi/4.5.3/../../../../arm-arago-linux-gnueabi/include/c++/4.5.3/bits/stl_map.h:451:11:   instantiated from 'mapped_type& std::map<_Key, _Tp, _Compare, _Alloc>::operator[](const key_type&) [with _Key = std::basic_string, _Tp = backward::SourceFile, _Compare = std::less<std::basic_string >, _Alloc = std::allocator<std::pair<const std::basic_string, backward::SourceFile> >, mapped_type = backward::SourceFile, key_type = std::basic_string]'
/home/user/ALPHABOX/alpha-app/app/recorder/backward.hpp:1647:49:   instantiated from here
/home/user/SDK/linux/linux-current/ti-sdk-am335x-evm-<IP_ADDRESS>/linux-devkit/bin/../lib/gcc/arm-arago-linux-gnueabi/4.5.3/../../../../arm-arago-linux-gnueabi/include/c++/4.5.3/type_traits:312:5: error: 'std::__is_convertible_helper<backward::SourceFile, backward::SourceFile, false>::__value' is not a valid template argument for type 'bool' because it is a non-constant expression

By the way... this warning message is written in a very strange type of English =) :
warning: #warning ":/ sorry, ain't know no nothing none not of your architecture!"

Ahah I was having fun writing this message ^^
You can probably set the defines that are used to select the destination
architecture yourself.
If you know of a more standardized way to detect cross-compiling let me
know!
On Mon, Mar 14, 2016, 11:14 mmmint<EMAIL_ADDRESS>wrote:

By the way... this warning message is written in a very strange type of
English =) :
warning: #warning ":/ sorry, ain't know no nothing none not of your
architecture!"
—
Reply to this email directly or view it on GitHub
https://github.com/bombela/backward-cpp/issues/29#issuecomment-196450510
.


Add a non-interactive function to use softioc in deamon mode

I propose this modification, following the initial request #155
Reminder of the initial proposal:
I propose adding the non_interactive_ioc function to allow the use of softioc in daemon mode. This mode can, for example, be used with systemd. It is compatible with asyncio and cothread.
To ensure that information is correctly logged in the journal, it is recommended to execute the Python script with the -u option or to set the environment variable PYTHONUNBUFFERED=TRUE.
Here is an example of a service:
[Unit]
Description=IOC
After=network.target

[Service]
User=root
Group=root
WorkingDirectory=/opt
ExecStart=/opt/softioc/bin/python -u /opt/example.py
Environment="PATH=/opt/softioc/bin"
Restart=always

[Install]
WantedBy=multi-user.target

And an example of a script:
# Import the basic framework components.
from softioc import softioc, builder
import cothread

# Set the record prefix
builder.SetDeviceName("MY-DEVICE-PREFIX")

# Create some records
ai = builder.aIn('AI', initial_value=5)
ao = builder.aOut('AO', initial_value=12.45, on_update=lambda v: ai.set(v))

# Boilerplate to get the IOC started
builder.LoadDatabase()
softioc.iocInit()

# Start processes required to be run after iocInit
def update():
    while True:
        ai.set(ai.get() + 1)
        print(ai.get())
        cothread.Sleep(1)

cothread.Spawn(update)

if __name__ == "__main__":
    softioc.non_interactive_ioc()

Hello, @AlexanderWells-diamond
I've made the requested changes and also reduced the number of commits.
Is there anything else I can do ?

I have squashed this work into a single commit, fixed a couple of trivial whitespace issues, and pushed to master.  This is now accepted (the "conflicts" are just my whitespace fixes), so will close this PR as completed.
Thank you for this.


Using cut in first line of a script file does not remove the line

Godot version:
9abc0ad8a5cf400d848fd25a33bd562db08d1046
Issue description:
When using Cut in the first line of a script file (without any selection) the cut operation is executed, but an empty line remains.
Steps to reproduce:

Place cursor anywhere in the first line
Press Ctrl + X or use the context menu to execute Cut
See that the content of the line is cut, but the line still remains

Similar to #34212.


MINOR: Implicit conversion from Long to SessionWindows

Some syntactic sugar on the Scala Streams API with an implicit conversion from Long to Session Windows to use the windowedBy(SessionWindows) function this way:
stream
  .groupBy((_, _) => something)
  .windowedBy(5l)

Thanks for the PR. Implicit conversions from primitive types are quite dangerous and generally best avoided.

Thanks for the PR. Implicit conversions from primitive types are quite dangerous and generally best avoided.

+1.


Gorga, Q3 interviewing

Interviewees: Vice President at International Society of Automation  from Singapore and collegues
Total 5 people
5 x half-hour interviews, total 2.5 hours
$125

Gorga will need a bit longer to complete the work.
So - provisional completion date is Fri 8th Nov -
and we'll check in with him in week commencing 21st Oct to confirm whether this date is to be final, or if it needs to be later.

3 interviews completed. Two more scheduled for later .
First Interview:
Time: 15:37 mins
Interviewee: Student of Electrical Engineering

Second Interview:
Time: 21:37 mins
 Interviewee: Student of Informatics

Third Interview:
Time: 17:51 mins
Fullstack Developer

Google Drive Link: https://drive.google.com/drive/u/1/folders/1lcYHGHQmdsaPy-Vq5jvegWiitxqErXEL


Implement set iterators in terms of limited API

I'll do a PR adding the benchmark to master, then we compare performance between teh two.

Are there instructions on running benchmarks?

cargo +nightly bench should do it - though great point, should add this to contributing.md

The measurements are a bit noisy, because I'm running on a laptop, but bench_set from #1168 is 10-15% slower. Is that so much of a slowdown that it needs 2x the impls? My instinct is that it's not worth it unless someone has a specific use case.

How about making the current set iterator #[cfg(not(Py_LIMITED_API))]?
We can do the same thing by PyIterator::from_object as the new implementation.

+1 - I think that as we've already got both implementations written, and a single test will cover both APIs depending on the features, it's easy for us to support both.
10-15% may not be huge, but for some people the choice of Rust is for everything to be as fast as possible, so they will still appreciate this.

I meant 'probably we don't need PySetIterator for #[cfg(Py_LIMITED_API)]'.

@kngwyu we do -- it needs to PyIterator is an iterator of PyResult, not an iterator of PyAny. You need PySetIterator to unwrap the PyResult (which is fine because in reality PySet's iterator can never error).

OK, that makes sense.


Modify the challenge submit page (form submission)

Changes proposed in this pull request:

Only form submission is included in this PR, docker based submission will be in the upcoming PR.

Link to live demo: http://pr-147-evalai.surge.sh

Screenshot 1:

Screenshot 2:

Codecov Report

Merging #147 into master will decrease coverage by 0.48%.
The diff coverage is 25.37%.

@@            Coverage Diff             @@
##           master     #147      +/-   ##
==========================================
- Coverage    54.5%   54.01%   -0.49%
==========================================
  Files          56       56
  Lines        2666     2701      +35
  Branches      295      298       +3
==========================================
+ Hits         1453     1459       +6
- Misses       1135     1164      +29
  Partials       78       78

Impacted Files
Coverage Δ

src/app/services/challenge.service.ts
44.72% <0%> (-1.2%)
:arrow_down:

...nents/utility/selectphase/selectphase.component.ts
88.88% <100%> (+26.03%)
:arrow_up:

...lenge/challengesubmit/challengesubmit.component.ts
46% <20.93%> (-10.07%)
:arrow_down:

src/app/services/endpoints.service.ts
70.58% <50%> (ø)
:arrow_up:

...rc/app/components/utility/input/input.component.ts
58.69% <75%> (+0.74%)
:arrow_up:

src/app/services/global.service.ts
38.6% <8.33%> (-1.79%)
:arrow_down:

Impacted Files
Coverage Δ

src/app/services/challenge.service.ts
44.72% <0%> (-1.2%)
:arrow_down:

...nents/utility/selectphase/selectphase.component.ts
88.88% <100%> (+26.03%)
:arrow_up:

...lenge/challengesubmit/challengesubmit.component.ts
46% <20.93%> (-10.07%)
:arrow_down:

src/app/services/endpoints.service.ts
70.58% <50%> (ø)
:arrow_up:

...rc/app/components/utility/input/input.component.ts
58.69% <75%> (+0.74%)
:arrow_up:

src/app/services/global.service.ts
38.6% <8.33%> (-1.79%)
:arrow_down:

Continue to review full report at Codecov.

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

@lunayach @RishabhJain2018 @galipremsagar @Shekharrajak
Please review.

LGTM for functionality. Though there are some UI glitches here and there, but we can handle them separately in one PR, once PR's for all these components are merged.


Duplicate filters on history nav

There is a bug in which index page filters are duplicated when navigating back or forward in browser history. It's not a total show-stopper, but it's been bothering some of my users. And it is obviously incorrect/buggy behavior.
Repro steps:

Navigate to a RailsAdmin resource index.
Filter the index by some criteria (ex: 'Created At' => 'Is present')
Click "refresh" to apply the filter
Navigate somewhere within RailsAdmin (ex: click to "edit" a record in the index)
Navigate "back" via your browsers back button to the index.

Notice that there are now two "Created At" filters. Navigate forward and back again, now there are three... yikes!
This is because when navigating back the previously rendered filters are still on the page, but the inline script to append new filters gets run again.
The fix that I've come up with is to create an alternative function, $.filters.init, which is called inline instead. init simply checks whether any filters have been rendered already, and only builds filters for the array of options it is passed if they have not.
I've updated specs that test the view helper construction of the inline script. However, I found no tests anywhere that cover the behavior of $.filters, so I did not add tests for $.filters.init.

This build is failing during gem installation - but clearly the diff shouldn't affect this. It looks like builds for other recent and unrelated pull requests are failing for the same reason - leading me to believe that my diff does not introduce the issue. Does master still successfully build? Has your CI settings/config changed since its last successful build?

I can confirm the reported issue, which many of our users are finding to be troublesome.
@mshibuya @bbenezech  I apologize for the direct mention as I know that u guys are very busy, but I'd like to know if u plan to address this and possibly backport it to earlier versions of the gem

Fixed by #2998.


Master

Docs Build status updates of commit e8b73e3:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/MicrosoftDocs/DocsLegal-pr.en-ZA, working directory: W:\vgof-s, target branch: HEAD, target branch commit: 106b0480ec03dc94e9e6ae2a1218e0d7f79e4bc1, source commit: e8b73e3dee4d7c33febcf6798118b055dcea6628.

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


feat: added mlflow server

added mlflow server to the existing helm charts
following assumptions have been made:

the helm chart in addition to deploying a ray cluster also deploys monitoring infrastructure
creates mlflow server and runs it on 9080 port
creates a service to expose the port over custerIP
no docker build for mlflow existed. had to manually create an image and push it out.

possible additions

use persistent storage and/or database for mlflow
use s3 artificatory for storing models
templatize the chart more
add tensorboard to the list as well

here is the content of the dockerfile to build the mlflow server
FROM python:3.8.2-slim

RUN pip install mlflow[extras]

CMD mlflow server \
    --backend-store-uri /mnt/mlflow-disk \
    #--default-artifact-root s3://my-mlflow-bucket/ \
    --host <IP_ADDRESS> --port=9080

docker build -t mlflow  .
docker push guidebooks/mlflow

super seeded by this https://github.com/guidebooks/ray/pull/2


Async memcpy for DtoD

Use HipMemcpyDtoDAsync (on the default stream) instead of HipMemcpyDtoD to avoid unnecessary host blocking. I noticed this in the profiler and after reading some documentation it seems like cuda and hip have different behavior for synchronous DtoD memcpys.
The cuda docs specifically say that "for transfers from device memory to device memory, no host-side synchronization is performed," for synchronous memcpy (see the cuda docs), while for hip every synchronous memcpy will:

wait for all previous commands to complete.
will not return control back to host until the command completes.
(see the rocm/hip docs)

I've only tested this for the Umpire device memory space and we see a performance improvement resulting from better kernel packing in a iterative routine with a few kernels followed by a DtoD transfer followed by a few kernels followed by a DtoD transfer followed by ... .
From what I understand this change is okay because the default stream waits for "tasks" on other streams to complete before running so this will be synchronous wrt other device tasks on non-default streams (if we ever add support for that in mfem). Hard to find this in the docs but someone from amd mentioned it here.
I am happy to make this change for other hip device memory spaces if desired.

PR
Author
Editor
Reviewers
Assignment
Approval
Merge

#2780
@tomstitt
@tzanio
@artv3 + @camierjs + @v-dobrev
01/21/22
⌛due 02/04/22
⌛due 02/11/22

I think we should to use the async D2D copy in class HipDeviceMemorySpace too.
Also, it will be nice to have a short comment at those calls to explain why we do that (and maybe mention this PR in the comment too.)

I think we should use the async D2D copy in class HipDeviceMemorySpace too.

I added it there too

Also, it will be nice to have a short comment at those calls to explain why we do that (and maybe mention this PR in the comment too.)

I added a short comment in both spots and also linked this PR

Merged in next for testing...


Image Caption

Is there a way to input a caption for uploaded images?

I just added a pull request #181 which supports image captions for images.


Use build function may be better

I think better to use static function instead of constructor

Thanks! :)

Why us thing static function better?
Why build method does not return anything?
Why use specific classname instead of new static, what will allow use inheritance?


Optimise spacy memory consumption

Optimise use of memory in SpacyClassifier by

deleting the passed data X, Y which then become X_train, Y_train, X_test, Y_test
creating a generator that yields the transformed data that spacy needs on demand instead of materialising them in memory
moves shuffling into X_train, Y_train since the data that spacy received are not in memory to be shuffled

Will merge for now as I wait to hear @jdu thoughts on it. I know from using it that it resolves the problem I had but how effective is del vs the other changes is an open question.


[API] fit, predict and other functions should accept X,y,smaple_weight as first parameters by default

In order to stay compatible with skleranAPI we want all estimatoer (and Adapters) to have functions that accept unnamed sample_weightby defalult.
For the moment we have for Adapter and DAEstimator:
    @abstractmethod
    def fit(self, X, y=None, sample_domain=None, *, sample_weight=None):
        """Fit adaptation parameters"""

I suggest we change it to
    @abstractmethod
    def fit(self, X, y=None, sample_weight=None sample_domain=None, *):
        """Fit adaptation parameters"""

that will allow to do things like
   model.fit( X, y, sample_weight, sample_domain):

the named sample_domain will still be necessary for pipelines

Hi,
I'd like to start contributing to skada and it seems this issue could be a good start. Is there a consensus on @rflamary 's suggestion? If yes, is it OK if I start a PR on this?

Let's make 'sample_domain' parameter named-only (as it previously was). I know recall that the change was made to have ability to call
fit(X, y, sample_domain)

(no names, just ordering). If we put 'sample_weight' third, the ability to do
fit(X, y, None, sample_domain)

would be frustrating. To avoid this, we just need to declare
    @abstractmethod
    def fit(self, X, y=None, sample_weight=None, *, sample_domain=None, **params):
        """Fit adaptation parameters"""

WDYT?


Bump asm up to 4.9.0

Migrate to ASM API version 9.
Now, supports recording for class instances built with a higher language level.
Make groovy script engine delegates instrumentation to JavaDCRInstrumenter.

Space and Tab indentation is mixed

Space and Tab indentation is mixed

Space and Tab indentation is mixed

reformat and rebase for this PR has done

Space and Tab indentation is mixed

reformat and rebase for this PR has done


How to search from a particular database?

Suppose I have more than one db "Users" and "Admin", how does db.find() work in this case ?

So you want to search in multiple datastores (NeDB files) at the same time? Or what are you trying to achieve?

Yup..

That does not work out of the box, as multiple datastores are multiple JavaScript objects. You can do the following though:

Write a function that takes a datastore object, runs the search on it and returns a promise that gets the results after NeDB has found the data.
Use Promise.all to call a function after both datastores have completed the find operation.
Merge the results.

If you need any specific code, don't hesitate to ask.

Thanks, Lukas. Closing this as not a bug nor feature requesT.

Thank you.. I guess I got it. I was wondering if there was anyway to do it with in-built functions..


Support fine grained Send message serialization

Use case:

Currently if the bus uses a JSON serializer there's no easy way to send XML without doing the serialization yourself and sending it as a byte array.
There is currently a way to register a handler using a different serializer (to consume messages from outside systems).
The messages assembly should remain free of any NsqSharp dependencies, so we can't and don't want to directly wire up an association between Topic and serialization method.

Needs more thought.


improve AbstractFileSystem.listStatus(Path path) method for exception process

https://alluxio.atlassian.net/browse/ALLUXIO-2025
if there is a FileDoesNotExistException throw FileNotFoundException ,so the user like hbase can handle
exception more accurate.

ok to test

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/10402/
Test PASSed.

I have changed the program like calvin suggested , and rebuild alluxio, also have a test with hbase running on it.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/10441/
Test PASSed.

a new change for resolve https://alluxio.atlassian.net/browse/ALLUXIO-2031

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/10442/Failed Tests: 1org.alluxio:alluxio-tests: 1alluxio.worker.block.BlockWorkerClientRestApiTest.cacheBlockTest
Test FAILed.

I roll back the shell change to make suer the change for ALLUXIO-2025 is ok.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/10443/
Test PASSed.

@lordk911 Thanks for the update, looks good overall. One minor comment.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/10470/Build result: FAILURE[...truncated 3462 lines...][JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/keyvalue/client/target/alluxio-keyvalue-client-1.2.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-keyvalue-client/1.2.0-SNAPSHOT/alluxio-keyvalue-client-1.2.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/underfs/hdfs/pom.xml to org.alluxio/alluxio-underfs-hdfs/1.2.0-SNAPSHOT/alluxio-underfs-hdfs-1.2.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/underfs/hdfs/target/alluxio-underfs-hdfs-1.2.0-SNAPSHOT.jar to org.alluxio/alluxio-underfs-hdfs/1.2.0-SNAPSHOT/alluxio-underfs-hdfs-1.2.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/underfs/hdfs/target/alluxio-underfs-hdfs-1.2.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-underfs-hdfs/1.2.0-SNAPSHOT/alluxio-underfs-hdfs-1.2.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/underfs/swift/pom.xml to org.alluxio/alluxio-underfs-swift/1.2.0-SNAPSHOT/alluxio-underfs-swift-1.2.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/underfs/swift/target/alluxio-underfs-swift-1.2.0-SNAPSHOT.jar to org.alluxio/alluxio-underfs-swift/1.2.0-SNAPSHOT/alluxio-underfs-swift-1.2.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/underfs/swift/target/alluxio-underfs-swift-1.2.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-underfs-swift/1.2.0-SNAPSHOT/alluxio-underfs-swift-1.2.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/examples/pom.xml to org.alluxio/alluxio-examples/1.2.0-SNAPSHOT/alluxio-examples-1.2.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/examples/target/alluxio-examples-1.2.0-SNAPSHOT.jar to org.alluxio/alluxio-examples/1.2.0-SNAPSHOT/alluxio-examples-1.2.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/examples/target/alluxio-examples-1.2.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-examples/1.2.0-SNAPSHOT/alluxio-examples-1.2.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/server/pom.xml to org.alluxio/alluxio-core-server/1.2.0-SNAPSHOT/alluxio-core-server-1.2.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/server/target/alluxio-core-server-1.2.0-SNAPSHOT.jar to org.alluxio/alluxio-core-server/1.2.0-SNAPSHOT/alluxio-core-server-1.2.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/server/target/alluxio-core-server-1.2.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-core-server/1.2.0-SNAPSHOT/alluxio-core-server-1.2.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/server/target/alluxio-core-server-1.2.0-SNAPSHOT-tests.jar to org.alluxio/alluxio-core-server/1.2.0-SNAPSHOT/alluxio-core-server-1.2.0-SNAPSHOT-tests.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/keyvalue/common/pom.xml to org.alluxio/alluxio-keyvalue-common/1.2.0-SNAPSHOT/alluxio-keyvalue-common-1.2.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/keyvalue/common/target/alluxio-keyvalue-common-1.2.0-SNAPSHOT.jar to org.alluxio/alluxio-keyvalue-common/1.2.0-SNAPSHOT/alluxio-keyvalue-common-1.2.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/keyvalue/common/target/alluxio-keyvalue-common-1.2.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-keyvalue-common/1.2.0-SNAPSHOT/alluxio-keyvalue-common-1.2.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/underfs/pom.xml to org.alluxio/alluxio-underfs/1.2.0-SNAPSHOT/alluxio-underfs-1.2.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/underfs/glusterfs/pom.xml to org.alluxio/alluxio-underfs-glusterfs/1.2.0-SNAPSHOT/alluxio-underfs-glusterfs-1.2.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/underfs/glusterfs/target/alluxio-underfs-glusterfs-1.2.0-SNAPSHOT.jar to org.alluxio/alluxio-underfs-glusterfs/1.2.0-SNAPSHOT/alluxio-underfs-glusterfs-1.2.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/underfs/glusterfs/target/alluxio-underfs-glusterfs-1.2.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-underfs-glusterfs/1.2.0-SNAPSHOT/alluxio-underfs-glusterfs-1.2.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/integration/pom.xml to org.alluxio/alluxio-integration/1.2.0-SNAPSHOT/alluxio-integration-1.2.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/keyvalue/pom.xml to org.alluxio/alluxio-keyvalue/1.2.0-SNAPSHOT/alluxio-keyvalue-1.2.0-SNAPSHOT.pomchannel stopped
Test FAILed.

Jenkins, test this please.

@lordk911
LGTM, thanks.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/10482/
Test PASSed.

@lordk911 Thanks for the contribution. As a follow up, would you mind adding a unit test to validate this behavior? I've assigned this JIRA ticket to you: https://alluxio.atlassian.net/browse/ALLUXIO-2036

@calvinjia OK.I will have a try.

@lordk911 This PR has already been merged, so it is effectively closed. You can directly open a new pull request to master which already has your changes.


Can’t use promisifyAll on AWS Lambda

The official JavaScript SDK for the API exposed by AWS Lambda exposes both an invoke method and an invokeAsync method. When using promisifyAll, Bluebird detects this and bails out. It should be noted, however, that the invokeAsync method is officially deprecated.
I don’t know that it’s appropriate for Bluebird to do something in this special case, but this seemed like a common enough library that the request to open an issue applied.

You can do:
Bluebird.promisifyAll(object, {suffix: 'Bsync'});

Excellent point, @rkoberg. That seems like a sufficient solution.

Or, if you want:
Promise.promisifyAll(
    new AWS.Lambda(),
    {filter: (name, func, target, passesDefaultFilter) =>
        passesDefaultFilter && name !== 'invokeAsync'});


There no way to get actual error line

Hello
How can I get actual error line of the Swagger input file? Right now the error message is really useless:

PLUGIN FAILURE: Missing operation id?, Error: Missing operation id?

The same files correctly handled by NSwag.

You need operationId fields on all the operations in order for AutoRest to infer an appropriate name for the cmdlet.
(better errors are coming soon)

@fearthecowboy sure, I know that, same for NSwag. But as I already wrote, it works in NSwag, so all operationIds are set correctly (and I've double checked this with PowerShell script).
Sorry, I can't share publicly the Swagger definition of our API.

Closed since no further update from the reporter for a long time


⚠ Bofrost.at has degraded performance

In 8920be6, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 2797 ms

Resolved: Bofrost.at performance has improved in d0d0d19 after 52 minutes.


Add vec3, point3, color, ray classes

Credit: https://raytracing.github.io/books/RayTracingInOneWeekend.html#rays,asimplecamera,andbackground


feat: Added more terms to spelling & heading rules

This PR removes false positives that are flagged in recent Quarkus content:
- Added the following items to the Spelling rule:

Kogito
Knative
Netty
pregenerated
ruleset
Vert.x

- Added the following items to the Headings rule:

Camel
IBM Cloud
Eclipse
Kogito
Knative
Netty
Proof Key for Code Exchange (More information about this one...)
Vert.x

- Added the following items to the Case-sensitive rule:

Proof Key for Code Exchange

@rolfedh - Thank you! Merging now ...


[hw,sysrst_ctrl] Add test for combo detect with precondition

Add new sequence randomizing all of combo detect configuration registers as listed in #17278
Move common tasks and functions from combo detect sequences to base sequence of sysrst_ctrl
Update randomize_combo_input task to prevent randomizing input signals that have activated precondition logic
Update get_combo_input function to optionally take an input argument, specifying the input inversion setting

est covers #17173

code coverage with nightly regression including the new test

UVM_ERROR @<PHONE_NUMBER>9 ps: (sysrst_ctrl_combo_detect_with_pre_cond_vseq.sv:188) [uvm_test_top.env.virtual_sequencer.sysrst_ctrl_combo_detect_with_pre_cond_vseq] Check failed (inactive_cycles inside {[exp_cycles - 4 : exp_cycles + 4]}) inact(0) vs exp(10) +/-4

Issue was with timing check in sequence, for cases where more than one combo detection channels assert same output. Fixed with change https://github.com/lowRISC/opentitan/commit/1398d2f24d08e9ea0c04a826e15a07ac0db289e6

rebased change with PR https://github.com/lowRISC/opentitan/pull/17337


WFLY-18065 Distributed @SessionScoped @Stateful EJBs require excessive cache transactions per invocation

https://issues.redhat.com/browse/WFLY-18065

@bstansberry @pferraro this PR breaks one of Weld's tests as it makes it unable to determine if the bean reference was removed or not in time.
The test can be seen here - https://github.com/weld/core/blob/master/tests-arquillian/src/test/java/org/jboss/weld/tests/enterprise/weld1234/Weld1234Test.java
With the original backing issue here - https://issues.redhat.com/browse/WELD-1234
The short of it is that if you have a stateful bean whose method throws an exception, such bean should be removed and any subsequent method invocation on that bean should be able to detect that via org.jboss.weld.ejb.api.SessionObjectReference.
The above linked Weld test shows that's not the case.
Weld has a special case handling for invocations of toString on a removed EJB in which case it won't throw NoSuchEJBException - looking at the forum reference from Weld issue, this is because of logging.
Can we revert this or look for another way of handling it?

@manovotn Thanks for pointing this out.  I will revisit this today and modify the fix accordingly.

Looking into this further, it is my opinion that the original fix for WELD-1234 was not ideal - as it made the assumption that SessionObjectReference.isRemoved() is inexpensive and thus requires that it be called on every stateful ejb invocation.  As I see it, the best way forward would be to modify weld in one of the following ways:

Leave this PR in place, and instead remove the isRemoved() check per invocation and instead catch a possible NoSuchEjbException during method invocation and return a fabricated value if the method was toString().
e.g.

    try {
        Object returnValue = Reflections.invokeAndUnwrap(proxiedInstance, method, args);
        BeanLogger.LOG.callProxiedMethod(method, proxiedInstance, args, returnValue);
        return returnValue;
    } catch (NoSuchEjbException e) {
        if (isToStringMethod(method)) {
            return businessInterface.getName() + " [REMOVED]";
        }
        throw e;
    }

Revert this PR and modify EnterpriseBeanProxyMethodHandler.invoke(...) to first test whether the method is toString() before calling isRemoved(), and thus short-circuit the condition before calling the potentially expensive operation.
e.g.

        if (isToStringMethod(method) && reference.isRemoved()) {
            return businessInterface.getName() + " [REMOVED]";
        }

IMO, #1 is preferable.  Thoughts @manovotn ?

IMO, the former is the better option. Thoughts @manovotn ?

I agree and I basically arrived at the same conclusion after browsing Weld code some more.
This really seems to be an edge case for logging when the bean was removed but you don't want to blow up.
I'll create a Weld issue and send a PR tomorrow, thanks for your help @pferraro.

Great.  I had already prepared https://github.com/weld/core/pull/2862 just in case...


⚠ Bofrost.be has degraded performance

In 86b367a, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 818 ms

Resolved: Bofrost.be performance has improved in bd04beb after 6 minutes.


Print stack trace

It would be helpful to print the function stack in times I forget where I am in the current goroutine.

implementation note: debug.PrintStack() prints the stack for you.

http://stackoverflow.com/questions/19094099/how-to-dump-goroutine-stacktraces
Also I see the docs for debug.Stack() say it is deprecated in favor of runtime.Stack(). Not sure which is called by debug.PrintStack() these days.

The full default stack trace with arg values is probably too noisy. Perhaps even just the function names are enough, but I could see how file/line could be helpful too.
If there's ever a feature to examine other stack frames (move up/down the stack), this feature could be reused for that navigation.

Perhaps the goroutine number would be useful too.

Here's the stack trace you get from runtime.Stack(): http://play.golang.org/p/TzttmeRRD0
The runtime package also exports a Func type that we could use to build a cleaner trace.

Here's an example of using runtime.Func to make a cleaner stack trace: http://play.golang.org/p/3BiuMP_ocl

I assume that additional information is to allow those debugging the generated assembly to do so. Hence it is valuable (perhaps essential) to some.  I don't find it distracting; I would leave it "uncleaned".


Including "canUsePlaceholder" property in worker.config

Part of #1951 fix
Including canUsePlaceholder property in worker.config. This property will be used by native placeholder to determine whether the function app payload uses a new version of worker package or not.
We will be publishing a new version with this change and update our docs suggesting customers to use this version as the minimum version to get placeholder support.
Native placeholder changes to read this property is in #1955
Pull request checklist

[x] My changes do not require documentation changes - I will work with @mattchenderson to update the docs once our changes are out and validated.

[ ] Otherwise: Documentation issue linked to PR

[ ] My changes should not be added to the release notes for the next release

[x] Otherwise: I've added my notes to release_notes.md

[x] My changes do not need to be backported to a previous version

[ ] Otherwise: Backport tracked by issue/PR #issue_or_pr

[ ] I have added all required tests (Unit tests, E2E tests)

Additional information
Additional PR information

Would be good to have a documentation issue created and linked for tracking. Also, any plans to add details about these changes (in host and worker) in engineering docs?

Would be good to have a documentation issue created and linked for tracking. Also, any plans to add details about these changes (in host and worker) in engineering docs?

For this specific change, there won't be docs update as this is not something customers needs to be aware of. No plans to update eng docs for the related host change at this point. but may consider including this in the placeholder wiki thing I am planning.


all contributors responds to bot comments that are from 'user' accounts

Is your feature request related to a problem? Please describe.
Bot responds to other apparent bots
Describe the solution you'd like
Should not respond to bots
Additional context
See example here https://github.com/callstack/react-native-paper/pull/827

how to check a accout is bot? name end with string bot?

@sinchang I'm not sure of the best way to move forward here. Thoughts?
Another example: https://github.com/callstack/linaria/pull/316#issuecomment-466024056


Clean build-script by adding subcommands

Based on this comment: https://github.com/apple/swift-syntax/pull/381#discussion_r881655025

Also: Since build-script-helper.py now does so many things, we should probably migrate it to using argparse subcommands. But that’s something for a completely standalone PR.

I tried to come with an example on how it could be structured. A command could look like: python3 ./build-script.py degyb --degyb-only --verbose
What do you think @ahoppen ?
Then we don't need to pass the --toolchain etc if it's not needed

Yes, that’s pretty much what I was thinking as well.
I think the possible subcommands could be

build: Similar to ./build-script.py without any arguments
test: Similar to ./build-script.py --test
generate-xcodeproj: Similar to ./build-script.py --generate-xcodeproj
degyb: Similar to ./build-script.py --degyb-only
run-swiftsyntaxbuilder-generation: Similar to ./build-script.py --run-swiftsyntaxbuilder-generation

We should be able to get rid of the options I mentioned in the “Similar to ” commands once we move to sub parsers.

Okay.
I've tried to add the commands.
There is some arguments that are duplicated.
Should we add them to the parser so all sub-commands can use them?

I just took a look at the actions that are currently supported by build-script.py and think it would make sense to provide the following sub-parser actions, with these options. Given that we now have gyb and SwiftSyntaxBuilderGeneration, I think it also makes sense to combine the two generation steps into one sub-command and decouple code-generation from building.
Actions:

generate-xcodeproj  Generate an Xcode project for SwiftSyntax.
  -v, --verbose         Enable verbose logging.
  --xcconfig-path XCCONFIG_PATH

generate-source-code    Generate source code using gyb and SwiftSyntaxBuilderGeneration
  -v, --verbose         Enable verbose logging.
  --add-source-locations
  --gyb-exec GYB_EXEC   Path to the gyb tool
  -v, --verbose         Enable verbose logging.
  -r, --release         Build in release mode.
  --build-dir BUILD_DIR
  --disable-sandbox     Disable sandboxes when building with SwiftPM
  --multiroot-data-file MULTIROOT_DATA_FILE
  --toolchain TOOLCHAIN
  --verify              Instead of writing the newly generated files to the source directory, assert that the generated files match the ones currently in the source directory

build                   Build all SwiftSyntax modules (does not re-generate source code - this is a change from the current behavior)
  -v, --verbose         Enable verbose logging.
  -r, --release         Build in release mode.
  --build-dir BUILD_DIR
  --disable-sandbox     Disable sandboxes when building with SwiftPM
  --multiroot-data-file MULTIROOT_DATA_FILE
  --toolchain TOOLCHAIN

test                    Run tests (does not re-generate source code - this is a change from the current behavior)
  -v, --verbose         Enable verbose logging.
  -r, --release         Build in release mode.
  --build-dir BUILD_DIR
  --disable-sandbox     Disable sandboxes when building with SwiftPM
  --multiroot-data-file MULTIROOT_DATA_FILE
  --toolchain TOOLCHAIN
  --skip-lit-tests      Don't run lit-based tests
  --filecheck-exec FILECHECK_EXEC

Regarding the common args, I think it makes sense to have two functions that add these common args (one for --verbose and one for all the build flags), similar to https://github.com/apple/sourcekit-lsp/blob/472a06c88af97135b6faa450c5854e8f1a0ab8de/Utilities/build-script-helper.py#L169-L181

@ahoppen I added your suggestions on groups.
Made it a bit more clean.

@ahoppen I have fixed all the comments.
How do we setup the CI?
I'm not sure it knows about the new sub-commands?

https://github.com/apple/swift/pull/59651
@swift-ci please test

https://github.com/apple/swift/pull/59651
@swift-ci please test

https://github.com/apple/swift/pull/59651
@swift-ci please test

Failed because it didn't recognise --verbose.
It need to come before the build argument, as it is in the root parser.
This syntax seems a bit strange @ahoppen ?

https://github.com/apple/swift/pull/59651
@swift-ci please test

Failed because it didn't recognise --verbose. It need to come before the build argument, as it is in the root parser.
This syntax seems a bit strange @ahoppen ?

Ah, I remember. This is because --verbose is an argument to the top level parser. We probably want to add --verbose as an option to every sub parser.

https://github.com/apple/swift/pull/59651
@swift-ci please test

https://github.com/apple/swift/pull/59651
@swift-ci please test

https://github.com/apple/swift/pull/59651
@swift-ci please test

@ahoppen should https://github.com/apple/swift/pull/59651 also be rebuild?

No, I mixed up the PRs. I thought this was about making matching Swift files for the Python definitions. No need to re-build swift if you just changed CONTRIBUTING.md


Prompt correction

The recent gpt-4 versions (in particular gpt-4o and gpt-4o-mini) don't have the same restrictions on PII asgpt-4-vision-preview had. So we can remove the "fake data" clause from the prompt for the API calls. This PR removes this clause from the relevant function and also eliminates some of the outputs of the notebook. Also we replace gpt-4o with gpt-4o-mini to save on processing costs.
Main changes

Remove "fake data" clause from prompt
Remove certain outputs in notebook
Replace gpt-4o with gpt-4o-mini

Looks good. I'm not sure if there's a way for people to still be able to see this people data through looking at previous commit history?

There is. To completely eliminate the data, we would have to create a new repo.

Saw this too late, but there is the git repo restore option. We could pull out the notebook with repo restore, then add the current version of the notebook to a new commit. It would look like every commit had been committed again, but once it was merged it would just be the new commit history.


docs: update

Sup @gucovip, for DuckDuckGPT & BraveGPT, they are actually chatbots now (the screenshot/demo are outdated):

But they are also userscripts, so that begs the question which is better category.
But also, in the future, they will be added to Chrome/Edge store as extensions, so they will also be browser extensions!
So if a tool belongs to multiple categories, should they be listed in all of them? Or if only one, what should be the rule to pick which one category? (We should consider the reader and how it best serves them)

So if a tool belongs to multiple categories, should they be listed in all of them?

yes.

@edison1105 ok, and can you install duckduckgpt, then visit duckduckgpt.com to confirm it is indeed also a chatbot that uses OpenAI to reply to you and remembers your previous messages?

@adamlui added them to chatbot category via e304fd9cf3a641a48ae338667490acbf569e1c7c


Updated validations.py to include all tests.

Fixed the validations.py script.
Fixes #<issue_number_goes_here>

It's a good idea to open an issue first for discussion.

[ ] Tests pass
[ ] Appropriate changes to README are included in PR

@googlebot I signed it!


installing wget in the docker to be able to get the ip via command line

installing wget in the docker image so that we can use it to get the external ip via command line

@mo-c4t please rebase this branch


Unable to specify custom citation keys

I am using the newest edition but failed to specify custom citation keys.
I set [shorttitle][year], but the output always be [auth][shorttitle][year].
Why?

You have to select your references, right-click, and select "refresh".

does this resolve your problem?

closing for inactivity


Need some help setting up

Hey I think I mucked up the setup cause it says
ERROR for site owner:
Invalid domain for site key
But the key I put in is correct.
And than on replit it says Cannot GET /

It will say Cannot GET / on replit, but you may be using the incorrect site key. Check on your reCAPTCHA dashboard to make sure you are using the right keys.

Its all correct, I added you on discord

Ok


Add ROR identifier for organizations

What is the motivation for your change request?
ROR is becoming the most widely used PID for organizations. A lot of VIVOs already have implemented it locally.
Describe the solution you'd like
Add a ROR identifier with the domain for organizations.
Additional context

https://ror.org/about/

Investigation needed if existing properties from other ontologies could be used, decision from https://wiki.lyrasis.org/display/VIVO/2024-11-20+Ontology+Interest+Group+Call.

Search protocol:

LOV: no candidates

https://lov.linkeddata.es/dataset/lov/terms?q=Research+Organization+Registry
https://lov.linkeddata.es/dataset/lov/terms?q=ROR

TIB TS

https://terminology.tib.eu/ts/search?and=false&sortedBy=title&page=1&size=10&q=ror+OR+"Research+organization+Registry"

http://purl.obolibrary.org/obo/AEON_0000020

has curation status: to be replaced with external ontology term

http://purl.enanomapper.org/onto/ENM_8000313

<owl:Class rdf:about="http://purl.enanomapper.org/onto/ENM_8000313">      <rdfs:subClassOf rdf:resource="http://purl.obolibrary.org/obo/IAO_0000030"/>        <rdfs:label xml:lang="en">research organisation registry identifier</rdfs:label>   </owl:Class>
-   <http://w3id.org/nfdi4ing/metadata4ing#hasRorId>

    -   has super-properties: [has identifier](https://nfdi4ing.pages.rwth-aachen.de/metadata4ing/metadata4ing/index.html#identifier "http://w3id.org/nfdi4ing/metadata4ing#identifier")\
        has domain: [organization](https://nfdi4ing.pages.rwth-aachen.de/metadata4ing/metadata4ing/index.html#http://www.w3.org/ns/prov#Organization "http://www.w3.org/ns/prov#Organization") ^c^

Ontobee

https://ontobee.org/search?ontology=&keywords=research+organization+registry&submit=Search+terms
https://ontobee.org/ontology/GAZ?iri=http://purl.obolibrary.org/obo/GAZ_00381810 → probably not related
https://ontobee.org/ontology/OGG-Dm?iri=http://purl.obolibrary.org/obo/OGG_3000034367 → not related

EBI

https://www.ebi.ac.uk/ols4/search?q=ROR+OR+"Research+organization+registry"


refactor: use versions.json determine latest version

Checklist

[x] the contributor license agreement is signed
[x] commit message follows commit guidelines
[x] tests are included
[ ] screenshots are included showing significant UI changes
[ ] documentation is changed or added

Description of change
Rework versioncheck.js to consume new versions.json from openequella.github.io.

Might need some tweaks, waiting for https://github.com/openequella/openequella.github.io/pull/108


Some DNS zone functionality was missing

Hey,
some functionality wasn't implemented yet, so I've added those, with tests.
I also found two classes with the same functionality: DomainZoneServiceEnum and ZoneServiceEnum, I've opted for usage of the enum and removed the DomainZoneServiceEnum class

Has been merged in https://github.com/sandwave-io/realtimeregister-php/releases/tag/1.0.0