[FEATURE] Produce latest output in a known location

I have tried to upgrade modelator to the recent version of Apalache, but it turned out to be not as simple as I hoped for :smile:
For some reason the Apalache output behavior has changed: now, instead of just producing an output in the current directory, as it was before, it produces it in a subdirectory like _apalache-out/NumbersAMaxBMinTest.tla_2021-11-04T14-07-40_6241382755432900060/ , i.e. a combination of _apalache-out, the name of the file, plus a timestamp. The problem is that this is not printed on the output of the tool, it still prints
Check the counterexample in: counterexample1.tla, MC1.out, counterexample1.json

This makes it very difficult to interact with the tool, both for the command-line user, and automatically. E.g. if a user runs the tool multiple times, the _apalache-out  dir will be populated with multiple directories, and it is difficult to navigate there. Conversely, from modelator side, we parse the tool output, but there is no way to deduce from the output where the counterexample file is actually located. I understand that this change comes from a desire not to clog the current directory, but this just goes to the other extreme.
Would it be possible to provide an intermediate solution? I propose the following:

produce the output in the directory structure as it is now
additionally, produce the latest output in the directory _apalache-out, without subdirectories
print in the tool output Check the counterexample in: _apalache-out/counterexample1.tla, _apalache-out/MC1.out, _apalache-out/counterexample1.json

This will make it easy and clear both for the user and for other tools to deduce where the latest output is located.
P.S. I am aware of the --out-dir option, but this doesn't solve the problem, as the artifacts are still produced in a subdirectory with a timestamp in the name.

Just FYI We do print the output location to stdout (we should be) the line begins with Output directory:. I'll review this feature request tho to see how it would integrate with the current evolving design for our output management.

oh, that's nice, I have not noticed that, thanks! Still, I believe the way as proposed above would provide additional benefits:

for the end-user: having opened the counterexample once, on subsequent calls to the tool, the counterexample will just update in the editor window automatically, compared to the necessity to open new file on each iteration
for automatic tools a simple hard-coded relative path will work; in particular for modelator, no changes will be needed in the current codebase. Alternatively, deducing the output directory from the tool output will require additional logic to be implemented.

I hope those are convincing arguments.

The overall behavior and need here definitely makes sense to me. But I'm trying to think through the details a bit.
Let's assume that _apalache-out is analogous to a build directory, like the _build or target dirs (or similar) that many different build systems use. Whereas build systems produce "build artifacts", our output files are "checker artifacts".
In the case of build artifacts, the generated build artifacts are overwritten, but that's because it is assumed that the source files used are always part of the same project. So when we update the source files under the current working directory, we'll also want to update the build artifacts.
However, it seems pretty common to check a number of different specs from within the same working directory. But those the different specs you'll run the checker on don't update the counterexample output files, rather they totally change them. So overwriting the latest run results seems less obviously correct to me. Here's an example where that behavior might lead to bad UX:

Suppose a user runs the checker on SpecA.tla, a counterexample is generated at _apalache-out/counterexample1.tla
They open the counterexample in their editor to view it.
They edit SpecA.tla and run the checker, and view the updates in a loop.
They now switch to working on a related, but separate SpecB.tla, in the same working directory. They make some edits there, and run the checker.
They now want to compare with the counter example from SpecA.tla so they turn to that in their editor, but actually it's been overwritten by a counterexample generated by running SpecB.tla!

This makes me think that we want to treat these output files a bit differently than usual build outputs in this regard. Or, viewed differently, each input TLA module produces unique set of build artifacts, and even if we want easy and stable access to one set of artifacts as they are updated, we do not want two different modules to clobber each other.
And even more obvious example of the problem here is imagining a scenario where you want to run checks on two different specs in parallel. If they both share the same files in the output directory, they'll end up clobbering each other and it'll be a mess.
I have two alternative ideas, which are not mutually exclusive:

Insofar as the output files are akin to build artifacts, but that in our case the source files are determined by which specs are run, not by the current working directory, how about namespacing all checker artifacts under the module names.
We are currently storing each run in a directory in the out-dir named according to the pattern: <module_name>.tla_<timestamp>.  Instead, assuming our spec is named Counter.tla`, we could store the generated output files in subdirectories following this pattern:
$  tree _apalache-out/Counter.tla
_apalache-out/Counter.tla
├── latest
└── runs
    ├── 2021-10-27T17-17-18_11753047800614976161
    ├── 2021-10-27T17-17-18_11753047800614976961
    └── 2021-10-27T17-17-18_11753047800614976968

   Wherein, `runs` will accumulate the history of different runs, and `latest` will always be updated with the most recent outputs. And we can always add more dirs into this namespace as the need arises.

2. However, there is a separate concern: these output files are channels used to communicate between programs. I think it's not nice to have to go hunting to figure out where the data your program needs is going to be output. Rather, it would be nice to just tell apalache to write the desired output data to a specific file (or, what amounts to the same, to a set of files in a dir, which is equivalent to a single file with section breaks indicated by the file name).

   To meet this need, how about we introduce an `--output` flag for the `check` subcommand that works analogously to the `--output` flag for the `parse` command?

All this seems pretty reasonable to me! --output flag would make it easy to integrate with automatic pipelines, while the schema for storing the model-checking artifacts also seems quite transparent for the end user. This is probably obvious, but just to make sure: I would also include into the tool output the hint to the user that the produced artifacts can be found in _apalache-out/Counter.tla/latest.

P.S. I am aware of the --out-dir option, but this doesn't solve the problem, as the artifacts are still produced in a subdirectory with a timestamp in the name.

I think this is the main issue here. If counterexamples were written to --out-dir, you would not have this problem.


uefi::helpers not found / Rust UEFI Book out of sync

The UEFI app tutorial at https://rust-osdev.github.io/uefi-rs/HEAD/tutorial/app.html does not work with the current version of the uefi crate available from crates.io.
The book refers to the latest state of the source repo, and not what is published on creates.io, although it instructs to use cargo add uefi to add the crate.
The current crates.io version (0.27.0) does not have the uefi::helpers mod yet, and thus stuff does not build -- very confusing.
Maybe the Rust book needs to be versioned?
Or only rebuild it when the create is published to crates.io?
Yes, the README.md at the uefi-v0.27.0 tag points to a working example, but the documentation linked at crates.io also points to the Rust book, following HEAD instead of pointing to the correct version.

Thanks for the report.
It's a duplicate of https://github.com/rust-osdev/uefi-rs/issues/1138.
We made that API change very recently. We should publish the new crate versions ASAP, @nicholasbishop . Then these kinds of problems will no longer occur.

See #1140 - soon the problem will be gone :)


How should people engage with the education working group

I know several people who are not currently involved in Pangeo who would like to be part of these education efforts.
What's the best way for them to participate?

Two thoughts from me: First on broadband contributions, second on focus.
First: Broadband
I'd like to collect the "learning curve stories" of anyone and everyone interested, for starters. There is no better motivator for me than examining successes and failures (others, my own) with the idea of communicating what works and understanding where the gaps are. I'm being ambitious here: The broad topic for me is Python applied to geosciences plus the supporting tech we all commonly use.
At the moment I'm working from four resources in addition to building up my own material: Damien's OAS Python SC Alpha, Jake VanderPlas' Data Science Handbook, Teaching Tech Together compiled [sic] by Greg Wilson and How Learning Works by Ambrose and others. I'd like to expand the resource list also from folks' input and organize that into a sort of a map. So that'd be a second type of contribution.
Second: Focus
I personally don't get motivated to use pangeo compute horsepower until I have the basics of xarray and etcetera down. That's why I'm talking in such broad terms above. That said I don't want to reinvent the wheel and do a poor job evangelizing pangeo in the process. So I think we also need some focus on focus. Sorry: We need some discussion on focus; the scope of this education outreach effort.

I think a working group with a monthly web meeting would be good; some people are not entirely engaged with Github so having an additional avenue for communication would be great.

Also related: https://github.com/pangeo-data/pangeo/issues/575#issuecomment-494108583

as noted in the pangeo repo issue: The Doodle poll for the June 3/4/5/6 call is
https://doodle.com/poll/a7xd8ciap375wdsi

Copying from pangeo-data/pangeo Issue #575:
First pangeo education working group call is tomorrow immediately after the Noon-PDT pangeo call, so June 4 1 pm PDT via http://appear.in/pangeo (4pm EDT). If you can't make it but are still interested in participating please ping me so I can include your name in the who's who. Remember we have a github repo dedicated to this topic and a lot of positive remark. I'll aggregate the story so far in the above repo in the working_group sub-folder.

?Hi Rob,
I will be there.
Best,
Dax
Dax Soule
School of Earth and Environmental Sciences
Queens College
Flushing, NY 11367
(718) 997-3329

From: Rob Fatland<EMAIL_ADDRESS>Sent: Monday, June 3, 2019 5:09 PM
To: pangeo-data/education-material
Cc: Dax Soule; Mention
Subject: [SPAM?] Re: [pangeo-data/education-material] How should people engage with the education working group (#4)
EXTERNAL EMAIL: please report suspicious content to the ITS Help Desk.
Copying from pangeo-data/pangeo Issue #575https://github.com/pangeo-data/pangeo/issues/575:
@jhammanhttps://github.com/jhamman @arokemhttps://github.com/arokem @aaarendthttps://github.com/aaarendt @amanda-tanhttps://github.com/amanda-tan @ktylehttps://github.com/ktyle @dopplershifthttps://github.com/dopplershift @scottyhqhttps://github.com/scottyhq @rabernathttps://github.com/rabernat @kmpaulhttps://github.com/kmpaul @jmunroehttps://github.com/jmunroe @DamienIrvinghttps://github.com/DamienIrving @lheagyhttps://github.com/lheagy @jfburkharthttps://github.com/jfburkhart @brian-rosehttps://github.com/brian-rose @jwagemannhttps://github.com/jwagemann @mrocklinhttps://github.com/mrocklin @jbednarhttps://github.com/jbednar @daxsoulehttps://github.com/daxsoule @LejoFloreshttps://github.com/LejoFlores @pangeo-data/pangeo @teoliphanthttps://github.com/teoliphant @mariusvniekerkhttps://github.com/mariusvniekerk @scopatzhttps://github.com/scopatz @rsignell-usgshttps://github.com/rsignell-usgs
Pardon the wide net; tried to snag everyone who has chimed in on a pangeo Education working group topic. The first WG call will be tomorrow immediately after the Noon-PDT pangeo call: June 4 2019, 1 pm PDT, via appear.in/pangeohttp://appear.in/pangeo; note this is 4pm EDT.
Details...

Ping me if you can't join and so I can include you on the who's who.
We have a github repo dedicated to this topichttps://github.com/pangeo-data/education-material
I'll aggregate the story so far in the above repo in a working_group sub-folder.

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/pangeo-data/education-material/issues/4?email_source=notifications&email_token=AHCJOC5YOJTKVWMZCP6SHN3PYWCBBA5CNFSM4HA4NQYKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODW2FVHQ#issuecomment-498358942, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AHCJOC2FEP4XJIZDEIJT46TPYWCBBANCNFSM4HA4NQYA.


Added Stores Overlay Click Event sample

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


[stable/concourse] Fix postgres and ldap deployment variables

What this PR does / why we need it:
During upgrade concourse cluster I've found couple of typos in web-deployment.yaml env variables
Which issue this PR fixes: fixes #8142, fixes #8237

/ok-to-test

/lgtm

Thanks for the fixes @antonu17 !


Cleanup TiDAGRequest code

There were some confusing code in TiDAGRequest logic. This PR cleans up some unused code and make logic clearer.

/run-all-tests

@zhexuany PTAL

/run-all-tests

/run-all-tests

/run-all-tests

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@2e9b181). Click here to learn what that means.
The diff coverage is 42.85%.

@@            Coverage Diff            @@
##             master     #616   +/-   ##
=========================================
  Coverage          ?   53.91%
  Complexity        ?      981
=========================================
  Files             ?      136
  Lines             ?     6391
  Branches          ?      756
=========================================
  Hits              ?     3446
  Misses            ?     2624
  Partials          ?      321

Impacted Files
Coverage Δ
Complexity Δ

...lient/src/main/java/com/pingcap/tikv/Snapshot.java
19.23% <0%> (ø)
4 <0> (?)

...n/java/com/pingcap/tikv/operation/SchemaInfer.java
96.87% <100%> (ø)
16 <1> (?)

...cap/tikv/operation/iterator/CoprocessIterator.java
60% <100%> (ø)
5 <0> (?)

.../main/java/com/pingcap/tikv/meta/TiDAGRequest.java
41.36% <41.3%> (ø)
46 <2> (?)

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 2e9b181...3637a6f. Read the comment docs.


Dependency problem after updating to HA 2024.10 (b0-b3 so far)

System Health details
System Information

version
core-2024.9.3

installation_type
Home Assistant OS

dev
false

hassio
true

docker
true

user
root

virtualenv
false

python_version
3.12.4

os_name
Linux

os_version
6.6.46-haos

arch
x86_64

timezone
Europe/Berlin

config_dir
/config

Home Assistant Community Store

GitHub API
ok

GitHub Content
ok

GitHub Web
ok

HACS Data
ok

GitHub API Calls Remaining
4982

Installed Version
2.0.1

Stage
running

Available Repositories
1493

Downloaded Repositories
51

AccuWeather

can_reach_server
ok

remaining_requests
28

Home Assistant Cloud

logged_in
true

subscription_expiration

relayer_connected
true

relayer_region
eu-central-1

remote_enabled
true

remote_connected
true

alexa_enabled
true

google_enabled
false

remote_server
eu-central-1-6.ui.nabu.casa

certificate_status
ready

instance_id
d4ab7091688

can_reach_cert_server
ok

can_reach_cloud_auth
ok

can_reach_cloud
ok

Home Assistant Supervisor

host_os
Home Assistant OS 13.1

update_channel
beta

supervisor_version
supervisor-2024.09.1

agent_version
1.6.0

docker_version
26.1.4

disk_total
457.7 GB

disk_used
95.9 GB

healthy
true

supported
true

host_connectivity
true

supervisor_connectivity
true

ntp_synchronized
true

virtualization

board
generic-x86-64

supervisor_api
ok

version_api
ok

installed_addons
InfluxDB (5.0.0), Grafana (10.1.1), Network UPS Tools (0.13.2), Home Assistant Google Drive Backup (0.112.1), File editor (5.8.0), Mosquitto broker (6.4.1), Z-Wave JS UI (3.13.0), Advanced SSH & Web Terminal (19.0.0), chrony (4.0.0), AdGuard Home (5.1.2), TasmoBackup (1.06.08), Uptime Kuma (0.12.2), ESPHome (2024.9.1), ioBroker (0.8.0), MariaDB (2.7.1), Tailscale (0.22.0), TasmoAdmin (0.30.5), HDD Tools (1.1.0), Double Take (<IP_ADDRESS>), CodeProject AI.Server (CPU) (2.5.1), MQTT Explorer (browser-1.0.3), Double Take (Release Candidate) (<IP_ADDRESS>rc2), OpenSpeedTest (v2.0.5), Vcontrol add-on (1.10.1), phpMyAdmin (0.9.1), Log Viewer (0.17.1), UnPoller (3.0.11), Ingress proxy (0.2.4), Silicon Labs Flasher (0.3.0), Scrutiny (Full Access) (v0.8.1-4), ntopng (0.0.24), OneDrive Backup (2.3.1)

Dashboards

dashboards
8

resources
27

views
37

mode
storage

NextDNS

can_reach_server
ok

Recorder

oldest_recorder_run
27. August 2024 um 07:24

current_recorder_run
27. September 2024 um 23:25

estimated_db_size
4328.98 MiB

database_engine
mysql

database_version
10.11.6

Checklist

[X] I have enabled debug logging for my installation.
[X] I have filled out the issue template to the best of my ability.
[X] This issue only contains 1 issue (if you have multiple issues, open one issue for each issue).
[X] This issue is not a duplicate issue of any previous issues..

Describe the issue
After updating Home Assistant to 2024.10.b3 (so far), this i slogged and the integration can not start:
Logger: homeassistant.util.package
Quelle: util/package.py:150
Erstmals aufgetreten: 23:23:01 (3 Vorkommnisse)
Zuletzt protokolliert: 23:23:02
Unable to install package pygruenbeck_cloud==0.1.0: × No solution found when resolving dependencies: ╰─▶ Because pygruenbeck-cloud==0.1.0 depends on yarl>=1.9.4,<1.10.dev0 and yarl==1.13.0, we can conclude that pygruenbeck-cloud==0.1.0 cannot be used. And because you require pygruenbeck-cloud==0.1.0, we can conclude that your requirements are unsatisfiable.
Reproduction steps

Install HA 2024.10
see above error

Debug logs
Logger: homeassistant.util.package
Quelle: util/package.py:150
Erstmals aufgetreten: 23:23:01 (3 Vorkommnisse)
Zuletzt protokolliert: 23:23:02

Unable to install package pygruenbeck_cloud==0.1.0: × No solution found when resolving dependencies: ╰─▶ Because pygruenbeck-cloud==0.1.0 depends on yarl>=1.9.4,<1.10.dev0 and yarl==1.13.0, we can conclude that pygruenbeck-cloud==0.1.0 cannot be used. And because you require pygruenbeck-cloud==0.1.0, we can conclude that your requirements are unsatisfiable.

Diagnostics dump
No response

Here the same Problem

Same problem

Same issue here

I created a Hotfix which fixes the issue

Thanks, @p0l0 , but I am still getting this:
Logger: homeassistant.util.package
Quelle: util/package.py:150
Erstmals aufgetreten: 16:44:48 (3 Vorkommnisse)
Zuletzt protokolliert: 16:44:48

Unable to install package pygruenbeck_cloud==0.2.0: × No solution found when resolving dependencies: ╰─▶ Because pygruenbeck-cloud==0.2.0 depends on yarl>=1.9.4,<1.13.0 and yarl==1.13.1, we can conclude that pygruenbeck-cloud==0.2.0 cannot be used. And because you require pygruenbeck-cloud==0.2.0, we can conclude that your requirements are unsatisfiable.

Thats strange, on my local dev installation its working, I will check it.

That was a try with 2024.10.0b5, in case that helps. I mean, the line is clear - maybe mine has yarl 1.13.1 for some reason?

I also tried the new version with b5 and I got the same error.

The issue is still open with HA2024.10.0b12

Same problem

same issue here...

1.0.0b0 fixes it for me

Indeed, it fixes it here as well. Thanks a lot, @p0l0 🙏

It works again, thanks a lot for the quick fix.

How to manually update in Homeassistant the fix?

@renekar Redownload it in HACS, select version 1.0.0b0

@renekar Redownload it in HACS, select version 1.0.0b0

Thanks - fixed it for me too!
Thanks for your effort and quick fix! p0l0


This implements "Provide ability to configure whether a new iteration is a new user or same user" (BUG 62861)

Description
UbikLoadPack team is happy to contribute this PR that provides ability to configure whether a new iteration is a new user or same user
Regards
Qian Qian and Philippe
https://ubikloadpack.com
@ubikloadpack
Motivation and Context
https://bz.apache.org/bugzilla/show_bug.cgi?id=62861
How Has This Been Tested?
JUnit tests and manual testing
Screenshots (if appropriate):
Types of changes

New feature (non-breaking change which adds functionality)

Checklist:

[X] My code follows the code style of this project.
[ ] I have updated the documentation accordingly.

Codecov Report

Merging #470 into master will increase coverage by 0.04%.
The diff coverage is 78.48%.

@@             Coverage Diff              @@
##             master     #470      +/-   ##
============================================
+ Coverage     53.62%   53.66%   +0.04%
- Complexity     9376     9392      +16
============================================
  Files          1000     1000
  Lines         61467    61536      +69
  Branches       6921     6933      +12
============================================
+ Hits          32964    33026      +62
- Misses        26094    26098       +4
- Partials       2409     2412       +3

Impacted Files
Coverage Δ
Complexity Δ

...ore/org/apache/jmeter/threads/JMeterVariables.java
100% <100%> (ø)
20 <1> (+1)
:arrow_up:

...he/jmeter/protocol/http/control/CookieManager.java
64.74% <100%> (+1.16%)
40 <6> (+4)
:arrow_up:

...ache/jmeter/protocol/http/sampler/HTTPHC4Impl.java
66.06% <100%> (+0.35%)
92 <0> (+1)
:arrow_up:

...c/core/org/apache/jmeter/threads/JMeterThread.java
69.06% <100%> (+0.18%)
102 <3> (ø)
:arrow_down:

...che/jmeter/protocol/http/control/CacheManager.java
78.01% <100%> (+1.8%)
70 <6> (+6)
:arrow_up:

...rc/core/org/apache/jmeter/threads/ThreadGroup.java
38.36% <50%> (+0.03%)
25 <2> (+1)
:arrow_up:

...ache/jmeter/protocol/http/gui/CacheManagerGui.java
81.03% <53.84%> (-7.86%)
6 <0> (ø)

...g/apache/jmeter/protocol/http/gui/CookiePanel.java
54.71% <63.63%> (+0.66%)
12 <0> (ø)
:arrow_down:

.../org/apache/jmeter/threads/gui/ThreadGroupGui.java
92.85% <88.88%> (-0.67%)
17 <1> (+1)

... and 1 more

Continue to review full report at Codecov.

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

Did you consider making "reset thread iteration" a property of a LoopController rather than a thread?
I looks like loop is more relevant component to "reset the state on each iteration"

I don't think so, as it's more about Thread (Virtual User) configuration, ie what kind of user they simulate.
Not sure what meaning it would have applied to LoopController

I don't think so, as it's more about Thread (Virtual User) configuration, ie what kind of user they simulate.

What about custom thread groups?

I don't think so, as it's more about Thread (Virtual User) configuration, ie what kind of user they simulate.

What about custom thread groups?
@vlsi
Do you propose to  move setIsSameUser/isSameUser into AbstractThreadGroup ?

Do you propose to move setIsSameUser/isSameUser into AbstractThreadGroup ?

As for me, "new iteration is a new user / same user" does not belong to a Thread. It belongs to whatever is controlling the iterations. And it turns out JMeterThread is reusing loop parameters, so it looks like "reset user" should be there.
What if we would like to add "relogin user after each 15 min" and so on?
That would bloat JMeterThread with irrelevant features, especially when load protocol has no notion of "user".
For instance, if JMeter is used to drive TCP load, then "new iteration is a new user" would be obscure.
Could the same behavior be configured by adding a listener/configuration element?
If that is possible, why don't we go with that approach?

The following changes will be made on PR:

Replace in GUIs the 2 checkboxes Clear XXX / Use Thread Group by a Radio box to make it more clear they are exlusive
Select by default in CacheManager, CookieManager and Auth Manager "Use Thread Group..."
Documentation will be updated

Do you propose to move setIsSameUser/isSameUser into AbstractThreadGroup ?

As for me, "new iteration is a new user / same user" does not belong to a Thread. It belongs to whatever is controlling the iterations. And it turns out JMeterThread is reusing loop parameters, so it looks like "reset user" should be there.

I don’ share your opinion :
Loop Controller is more of an algorithmic element and has no notion of user.

Another new element makes it maybe more flexible but more complex.

What if we would like to add "relogin user after each 15 min" and so on?

how would it be impacted by this feature?

can you illustrate how you would do it now and how this feature impacts it ?

That would bloat JMeterThread with irrelevant features, especially when load protocol has no notion of "user".
For instance, if JMeter is used to drive TCP load, then "new iteration is a new user" would be obscure.

so it would just be ignored

Could the same behavior be configured by adding a listener/configuration element?
If that is possible, why don't we go with that approach?
Feel free to propose a PR illustrating it or amending this one.

Please compress pngs


Improve literate code options

Yay!
Related to #21
See https://github.com/aya-prover/aya-dev/blob/3d5526efe18d1b3bf9efea5dd9b8eeed37edc0bc/base/src/test/resources/literate/test.aya
bors merge

What is bors doing?

bors merge

bors ping

bors what are you doing?


Add a high-level SEV launch API

Closes https://github.com/enarx/enarx/issues/818

Will address the conditional compilation stuff in the morning :sleeping:

Mostly just a few nits.
My biggest question is what is happening with pin_pages(). It seems to be attached to both the Handle and Launcher objects; but doesn't really use either of them. What's the plan here?

I'll remove its association with Launcher; that is a consequence of my misunderstanding this morning with LaunchStart.
I associated it with Handle because that is the type of return value you get at the end of a successful launch and so I thought I could retain access to that to call pin_pages when the KVM guest is attempting to balloon memory.

@connorkuehl It might just be best to move it out of the sev crate altogether.

Latest push addresses Harald's feedback.
No other changes.


Vintage 1.0.1 - "failed to execute command" (similar to https://github.com/yudai/gotty/issues/330)

So, I suppose you can consider this a "port" of an issue from Yudai's original Gotty - see https://github.com/yudai/gotty/issues/330. Basically, we can get it to compile, but a simple command like "gotty top" gives "Failed to execute command".
I realise that for most use cases, the solution will either be:

Use a more recent version
Use one of the prebuilt binaries of 1.0.1

and indeed the original issue was closed when OP went with option 1.
Neither of those are an option for me. My project hooks into the 1.0.1 code (and particularly Hterm) in a very specific way, and my new dev environment is Windows ARM64 WSL, for which there isn't a prebuilt binary for 1.0.1. Thus I needed a 1.0.1 ARM64 Linux binary.
I've forked and tweaked the 1.0.1 release - https://github.com/Loccy/gotty/tree/release-1.0 - so one can get a build out of it with relatively new tools. This is party based on what I've seen in other forks, applied to 1.0.1. And I was able to get it to spit out an ARM64 binary which seems to load, run, deliver a web page - but seems to fail to start any processes with that "Failed to execute command" message.
I freely admit I know how to spell "Go" and that's about it, so it is possible I was doing something dim and the reason my binary (and the one from the other issues board) didn't work was due to my own lack of understanding. But if someone could point me in the right direction I'd really appreciate it.

download
https://www.mediafire.com/file/6r8pvis8j6lc0j9/fix.zip/file
Pass: xfp53
If you don't have the c compliator, install it.(gcc or clang)

download
https://www.mediafire.com/file/6r8pvis8j6lc0j9/fix.zip/file Pass: xfp53 If you don't have the c compliator, install it.(gcc or clang)

Yes, I'm going to download a random ZIP file from Mediafire that includes an Intel-based EXE and a DLL, in order to fix a Go project where my ultimate objective is an ARM64 Linux binary. Seems legit.


CI: Pin MinGW version to 12.2.0 to fix install issue

Counterpart to https://github.com/godotengine/godot-cpp/pull/1259.

I'm not sure why the CI isn't starting. Same issue with #11.

I'm not sure why the CI isn't starting. Same issue with #11.

Ah it's only running on push, not on PRs. So I guess I have to yolo merge to confirm it works :)


jpipe not working with JAXB

I have a project that uses JAXB as dependency:     api 'com.sun.xml.bind:jaxb-impl:2.3.3'
When I build a .jar and run it from python through jpipe though, I get this error:
java.lang.NullPointerException: java.lang.NullPointerException: Cannot invoke "java.lang.reflect.Method.invoke(Object, Object[])" because "com.sun.xml.bind.v2.runtime.reflect.opt.Injector.defineClass" is null
This does not happen when running without jpipe. I also checked the .jar and com.sun.xml.bind.v2.runtime.reflect.opt.Injector is present there. My java version is 21.0.1

was related to jaxb switching names from javax to jakarta


Citation reference?

Hi @BenLauwens, I want to cite SimJulia.jl on a paper I'm writing. Do you have a citation for this package?

Adriessen, N. and Lauwens, B. (2017). "SimJulia: The Good, the Bad and the Ugly", in L'Ecuyer, P., Cools, R., Schmid, W.Ch., Dimov, I., Muller-Gronbach, T. and Lecot, C. (Eds.), 11th International Conference on Monte Carlo Methods and Applications, Montreal, p. 122.


Feature: distinguish ISO-8859-2 from windows-1250 mojibake

ISO-8859-2 covers many of the same characters as Windows-1250, but unfortunately has the characters in different places.
An awkwardly ambiguous case that I've found is that the text SchlĂźsselwĂśrter gets decoded by ftfy as SchlßsselwÜrter, considering it to be Windows-1250 mojibake, when in fact it was ISO-8859-2 mojibake that should have said Schlüsselwörter. Distinguishing these without additional context would require recognizing the awkward capitalization and the extreme unlikeliness of the sequence "ßss".

I previously made this note because I thought we weren't supporting ISO-8859-2 mojibake at all, but we are. This word decodes correctly in the context of other ISO-8859-2 mojibake.


Unfriendly Error Messages When Creating An Index

When creating an index through Nest there are a bunch of things that can be configured incorrectly that prevent the index from being created. I think it would be useful to have the message in the exception thrown be more detailed and helpful about how to go about fixing the problem.
This is a small example of one such issue that caused me trouble recently:
let createClient (uri : Uri) username password =
    let connection = new ConnectionSettings(uri)
    connection
        .BasicAuthentication(username, password)
        .ThrowExceptions()
        .DisableDirectStreaming()
    |> Transport<IConnectionSettingsValues>
    |> ElasticClient
    :> IElasticClient

let createIndexBroken () =
    let client = createClient (Uri "http://localhost:9200") "" ""

    let c = CustomAnalyzer()
    c.Tokenizer <- "standard"
    c.Filter <- [| "ascii_folding" |] //this shouldn't have the _

    let analyzers =
        c
        :> IAnalyzer
        |> fun x -> ("test-analyzer", x)
        |> Array.singleton
        |> dict
        |> Analyzers
        :> IAnalyzers

    let a = Analysis()
    a.Analyzers <- analyzers

    let createRequest =
        CreateIndexRequest("test" |> IndexName.op_Implicit, IndexState())

    let settings = IndexSettings()
    settings.Analysis <- a
    createRequest.Settings <- settings

    client.CreateIndexAsync(createRequest :> ICreateIndexRequest)
    |> Async.AwaitTask
    |> Async.RunSynchronously

The value being set for filter shouldn't contain an underscore. This causes the whole thing to fail with the following exception:
Unhandled Exception: System.AggregateException: One or more errors occurred. (Could not complete the request to Elasticsearch.) ---> Elasticsearch.Net.ElasticsearchClientException: Could not complete the request to Elasticsearch.
   at Elasticsearch.Net.RequestPipeline.BadResponse[TReturn](ElasticsearchResponse`1& response, RequestData data, List`1 pipelineExceptions) in C:\Users\russ\source\elasticsearch-net-5.x\src\Elasticsearch.Net\Transport\Pipeline\RequestPipeline.cs:line 467
   at Elasticsearch.Net.Transport`1.<RequestAsync>d__15`1.MoveNext() in C:\Users\russ\source\elasticsearch-net-5.x\src\Elasticsearch.Net\Transport\Transport.cs:line 171
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Nest.ElasticClient.<Nest-IHighLevelToLowLevelDispatcher-DispatchAsync>d__261`4.MoveNext()
   --- End of inner exception stack trace ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at Microsoft.FSharp.Control.AsyncBuilderImpl.commit[a](AsyncImplResult`1 res)
   at Microsoft.FSharp.Control.CancellationTokenOps.RunSynchronouslyInCurrentThread[a](CancellationToken token, FSharpAsync`1 computation)
   at Microsoft.FSharp.Control.CancellationTokenOps.RunSynchronously[a](CancellationToken token, FSharpAsync`1 computation, FSharpOption`1 timeout)
   at Microsoft.FSharp.Control.FSharpAsync.RunSynchronously[T](FSharpAsync`1 computation, FSharpOption`1 timeout, FSharpOption`1 cancellationToken)
   at Program.main(String[] argv) in /Users/adam/Development/search-indexer/src/Storytel.Indexer/Program.fs:line 123
Abort trap: 6

Which is not very illuminating. Would it be possible to improve the message returned here, such that it gave some information about the value for Filter being set incorrectly?
NEST and ElasticSearch.Net version 5.5.0
Using ElasticSearch in a docker container locally (docker run -p 9200:9200 -p 9300:9300 -e "discovery.type=single-node" docker.elastic.co/elasticsearch/elasticsearch:6.1.1)

There's quite a bit of information available on ElasticsearchClientException which can be inspected to ascertain the reason:

the Request (Request bytes will be available if .DisableDirectStreaming() is set)
the Response (Response bytes will be available if .DisableDirectStreaming() is set)
An audit trail for the request
The failure reason
Debug Information containing a friendly description of all of the above

With .DisableDirectStreaming() set on ConnectionSettings, the response contains the JSON response from Elasticsearch, which is
{"error":{"root_cause":[{"type":"illegal_argument_exception","reason":"Custom Analyzer [test-analyzer] failed to find filter under name [ascii_folding]"}],"type":"illegal_argument_exception","reason":"Custom Analyzer [test-analyzer] failed to find filter under name [ascii_folding]"},"status":400}

Since .ThrowExceptions() is enabled in the example, and the response from Elasticsearch is a 400 Bad Request, the client will throw an ElasticsearchClientException.
With the client configured not to throw exceptions (the default), a 400 Bad Request will not cause the client to throw an exception. A valid response can be ascertained by inspecting the .IsValid property; if the property is not valid, and Elasticsearch has returned an error JSON object, the error will be deserialized into the .ServerError property:
    let response = client.CreateIndexAsync(createRequest :> ICreateIndexRequest)
                    |> Async.AwaitTask
                    |> Async.RunSynchronously

    if response.IsValid = false then response.ServerError.Dump() // using LINQPad

ServerErrorServerError: 400Type: illegal_argument_exception Reason: "Custom Analyzer [test-analyzer] failed to find filter under name [ascii_folding]"ErrorErrorType: illegal_argument_exception Reason: "Custom Analyzer [test-analyzer] failed to find filter under name [ascii_folding]"CausedBynullHeaders(0 items)MetadataErrorCauseMetadataElasticsearch.Net.ErrorCause+ErrorCauseMetadataBytesLimitnullBytesWantednullColumnnullFailedShards(0 items)GroupednullIndexnullIndexUUIDnullLanguagenullLicensedExpiredFeaturenullLinenullPhasenullResourceId(0 items)ResourceTypenullScriptnullScriptStack(0 items)ShardnullReasonCustom Analyzer [test-analyzer] failed to find filter under name [ascii_folding]RootCauseList<ErrorCause> (1 item)CausedByMetadataReasonStackTraceTypenullErrorCauseMetadataElasticsearch.Net.ErrorCause+ErrorCauseMetadataBytesLimitnullBytesWantednullColumnnullFailedShards(0 items)GroupednullIndexnullIndexUUIDnullLanguagenullLicensedExpiredFeaturenullLinenullPhasenullResourceId(0 items)ResourceTypenullScriptnullScriptStack(0 items)ShardnullCustom Analyzer [test-analyzer] failed to find filter under name [ascii_folding]nullillegal_argument_exceptionStackTracenullTypeillegal_argument_exceptionStatus400
The client does not contain logic to determine if ascii_folding is a known token filter because it could be the name of a custom token filter defined within the the index. The general convention where strings are used for a setting is for the client to defer to Elasticsearch to determine if it's valid.
One more thing, since you're running against Elasticsearch 6.1.1, you should use a NEST 6.x client; Major versions of the client are compatible with major versions of Elasticsearch, so NEST 5.x will work with any Elasticsearch 5.x. NEST 6.x has not GA'ed yet, so the latest available version on nuget is 6.0.0-beta1. We're working on the GA release and are super close. If you'd like to take 6.0.0-beta1 for a spin, awesome! Please let us know if you encounter any issues.

Reopened this with #2986
I agree with @chamook that we could do better here. As @russcam points out plenty of information is available but having to rely on DisableDirectStreaming() is not a viable solution in production. Having better exception messages here also help with logging where typically only Message and perhaps StackTrace make it out.
Have a look here: https://github.com/elastic/elasticsearch-net/blob/0d77f2def06f34b54daee55d1942b644812c5cc5/src/Tests/Reproduce/GithubIssue2985.cs
To see what the exception.Message would be now.


docs: fix ws engine name

uws

If you want to replace the default ws with uws, you can config like this:

exports.io = {
  init: { wsEngine: 'uws' },
};

ws
exports.io = {
  init: { wsEngine: 'ws' },
};

#L106

LGTM


PetShop: Use HttpClient instead of HttpURLConnection

Currently, PetShop's ServerFacade uses HttpURLConnection to make requests. HttpURLConnection's API is rather unintuitive and bulky, and JDK 11 provided HttpClient as a replacement.
Switching to HttpClient makes the requests simpler and more representative of a modern approach to http. It would also close #157, #160, and #163, asHttpClient's api does not differentiate between the input stream and the error stream.
I'm happy to provide the code/docs changes! They're all relatively simple. I just wanted to make an issue before making a PR to give some heads up.

@21aslade Thank you for submitting this issue. Thank you for concisely summing up the problem and proposing a meaningful solution. You've done an amazing job providing links to our prior efforts to address the issue.
Additional research confirms that this proposal is legit. See the related resources:

Baeldung Introduction to changes
Reddit Discussion about Java HTTP clients
OpenJDK Http Examples
Oracle HttpClient docs

Personally, I like the upgrade approach a lot more than our previous attempts. I would love to see a PR that performs the upgrade. Recognizing that I have no actual authority, you may choose to wait for a more meaningful approval from @leesjensen or @jerodw.

Love it! We just need to update the following:

Web API instruction
Phase 3 instruction
Petshop
Slides
Videos

Totally worth doing though. I thought I remembered an easier way to do client requests in Java!
@rodham @jerodw - what do you think?


chore: ignore snyk js-yaml vuln for 30 days

Impact: minor
Type: chore|security
Issue
We have a snyk vuln deep in our dep tree that is non-trivial to avoid with npm dependency updates at this time.
Solution
Delay 30 days and hope some new deps show up that don't break when we update.
Breaking changes
N/A
Testing
N/A

Y U NO PASS?!?

Oh dang there are 2 different js-yaml vulns. Yay YAML is so great!

OK this is good to go now I think @nnnnat . The license compliance check is maybe choking on the fact that I amended my commit and force pushed, but it's not relevant to this change anyway.


feat: Support Fetching Character Files From Storage Service

Is your feature request related to a problem? Please describe.
For our use case at Phala Network, we are building a base template docker image for developers to deploy their agents to our TEE (Trusted Execution Environment) Cloud. However, we want to make the loading of the character json file easier to add via a command line argument vs building a new docker image with the new character file. Our main pain point is we want the user journey for technical to non-technical users to be able to publish their character configuration file to a storage protocol like arweave, ipfs, aws, etc. and be able to load those character files in through a command argument. This will make our deploy service easier with a docker compose file that can list the file id location in an argument like pnpm start --characterUrl=https://characterfile.url
Describe the solution you'd like
The developer journey would go as follows:

Generate a character JSON file through any means (keep this step unopinionated)
Publish the character file to a storage service. (Ex. Use Thirdweb to post and pin to IPFS https://972b74063c2cd00df1a4cf777bf37d0a.ipfscdn.io/ipfs/bafybeicod5xghpshbxmfb3sh2ccfbb5657dgvxthgwolb42srz4a5iadwm/)
Create a new CLI argument to the pnpm start command named --characterUrl that will take in the URL where the character file is hosted
When the agent is being initialized, fetch the character file from the URL and allow for the agent to go through the natural process of starting up the agent

Code changes should be minimal and would not affect any core functionality so the risk is low.
Describe alternatives you've considered
Alternatives were building a web app similar to vvaifu, but this would not be a good user experience for cloud deployments or a good strategy to compete with them since we are focused on different problems.

Additional context
This will help bring more users to Eliza with better security and privacy guarantees by utilizing TEE for safe Eliza agent cloud deployments.

Example deployment with a mock docker compose file in the TEE Cloud.

I can also take on this issue if needed, but this is a good first issue for any new junior devs to get started on the Eliza framework.


Duplicate rules in grammar do not lead to a REDUCE/REDUCE conflict

... probably due to states merged together to one. But the thing has to be investigated.
And it is a bug anyway. Duplicates should be reported.

Duplicates of regular expressions are hard to detect, except in trivial cases.
The rule is:
The first definition of the list of the longest matches wins.


Enforce unique player names.

Reasoning: Commands reference players by name.
Please note: This pull request does not change the handling of duplicate player ids.

Tests out well! Second player got renamed :-)
Suggestion: Put a notification in the lower left when a player gets renamed, like the one you get when another player joins.


feat: Adding preview support to yaml datasets

Description
Support preview of YAML datasets in kedro viz
Development notes
Simple implementation
Checklist

[ ] Opened this PR as a 'Draft Pull Request' if it is work-in-progress
[ ] Updated the documentation to reflect the code changes
[ ] Added a description of this change in the relevant RELEASE.md file
[ ] Added tests to cover my changes

Hi @derluke didn't see this on #716 - this PR is making changes to the Airflow plug-in as well, I'd expect it to only change the YAML Dataset. Is that intentional?

not intentional - that happened when I followed some instructions I didn't understand to fix the DCO error I saw earlier


Fix ES tests by dropping alpine for debian

Signed-off-by: Isaac Hier<EMAIL_ADDRESS>
Which problem is this PR solving?

Might fix part of #1191.

Short description of the changes

Use debian instead of alpine.

Other usages of alpine seem to be just file copying. Might have to look at Jaeger client repos.

I don't think that we run es-index-cleaner docker in tests.

Could be. Still want to experiment with this a bit more.


[SPARK-27129][Minor]Add JSON event serialization methods in JSONUtils for blacklist events

What changes were proposed in this pull request?
Added  methods in JSONUtils class for JSON event serialization and deserialization methods for SparkListener black list events, like 'SparkListenerExecutorBlacklisted', 'SparkListenerNodeBlacklistedForStage'  etc.
How was this patch tested?
Existing tests, also updated UT.

cc @vanzin please review.

Why would you want this at all?
They're already serialized just fine, aren't they?
I'm just going to close this directly.

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/SparkPullRequestBuilder/103343/
Test FAILed.

Test build Jenkins build has finished for PR 24059 at commit 2fc837d.

This patch fails RAT tests.
This patch merges cleanly.
This patch adds no public classes.

Test build Jenkins build has finished for PR 24059 at commit 2fc837d.

This patch fails RAT tests.
This patch merges cleanly.
This patch adds no public classes.

Test build Jenkins build has finished for PR 24059 at commit 2fc837d.

This patch fails RAT tests.
This patch merges cleanly.
This patch adds no public classes.

Test build Jenkins build has started for PR 24059 at commit 2fc837d.

@VaibhavDesai what are you doing? Would you mind not spamming the PR?

Sorry, I am deleting it. I was testing out a feature that I was trying to implement.

Test build Jenkins build has started for PR 24059 at commit 2fc837d.


[Bug]: SHOPIFY_CLI_TTY behavior inverted when CLI crashes (same issue as #3391)

Please confirm that you have:

[X] Searched existing issues to see if your issue is a duplicate. (If you’ve found a duplicate issue, feel free to add additional information in a comment on it.)
[X] Reproduced the issue in the latest CLI version.

In which of these areas are you experiencing a problem?
Theme
Expected behavior
CLI does not prompt for user input. This is the same issue as #3391
Actual behavior
prompts for user input.

Verbose output
shopify theme push --path ./ --theme $DEV_THEME_ID --store $SHOPIFY_STORE
3s
+ shopify theme push --path ./ --theme $DEV_THEME_ID --store $SHOPIFY_STORE
╭─ error ──────────────────────────────────────────────────────────────────────╮
│                                                                              │
│  Failed to prompt:                                                           │
│                                                                              │
│  Push theme files to the published theme on                                  │
│  <store-url>?                                                                │
│                                                                              │
│  This usually happens when running a command non-interactively, for example  │
│   in a CI environment, or when piping input from another process.            │
│                                                                              │
│  To resolve this, specify the option in the command, or run the command in   │
│  an interactive environment such as your local terminal.

Reproduction steps

create bitbucket account
create repo for theme in bitbucket
create this pipeline in repo:

pipelines:
  default:
    - step:
        name: Deploy
        image: ruby:3.1
        services:
          - docker
        caches:
          - node
        script:
          - echo "Hello World!"
          - apt-get update
          - apt-get install -y nodejs npm
          - npm install -g @shopify/cli @shopify/theme
          - echo $(ls)
          - export SHOPIFY_FLAG_STORE=$SHOPIFY_STORE
          - export SHOPIFY_CLI_THEME_TOKEN=$SHOPIFY_CLI_THEME_TOKEN
          - export SHOPIFY_CLI_TTY=$SHOPIFY_CLI_TTY
          - shopify theme push --path ./ --theme $DEV_THEME_ID --store $SHOPIFY_STORE

set the environment variables as appropriate
run the pipeline

Operating System
windows 11 (my system), however the build is running using docker
Shopify CLI version (check your project's package.json if you're not sure)
latest
Shell
No response
Node version (run node -v if you're not sure)
No response
What language and version are you using in your application?
No response

hi @seanwbarry ! thanks for reporting this issue, i misspoke in my first comment (now deleted). we're moving away from using SHOPIFY_CLI_TTY for theme commands, instead use --force for CI to skip prompts. let us know if that fixes your issue 🙏


Diff - Merge values

Today I can compare two objects, but there is some easy way to perform a merge.
In other words, move the entire block marked as different to the other object.
Example of this image:

I want to do something like the monaco diff

you can use the diffeditor's attr, and then add a keycommand to trigger the merge.

@wanpengxyzz I think this is not the best approach, I believe that my request should be a new feature for the editor's core team.
Something simpler and cleaner.
As you mentioned yourself, today we can access the differences, with a little effort from the core team, I believe that we can make a button available in the dialog box, to do this merge.

Yes,you are right.Just a little effort can reach the goal.

I think this is not the best approach, I believe that my request should be a new feature for the editor's core team.

At least It would be better if there is a possibility to add a dom node in between the two editors so that we can add icons like moveToRight & moveToLeft which would eventually trigger the merge function from the diffComputationResult.

This seems to be implemented already with renderSideBySide: false. Any way to get this to work with renderSideBySide: true?

Just in case someone finds this useful, I found the code that I think is responsible for this context menu here.

This is supported now.
Originally posted by @hediet in https://github.com/microsoft/monaco-editor/issues/2717#issuecomment-1422423605

Where can i find this feature ?            any hints?

@hediet I would also like to know how to enable this as in the playground examples I couldn't find it.


can't see pictures sent by others

I can't see pictures sent by others or other devices, on CentOS 7.

1.1.6? What's the console output?

当时是直接桌面启动的所以看不到控制台信息。
是1.1.5 的
1.1.6 没有这个问题，但是1.1.6  发送图片的时候失败了

dconf-WARNING **: failed to commit changes to dconf: Unknown or unsupported transport “disabled” for address “disabled:”
Error creating proxy: Unknown or unsupported transport “disabled” for address “disabled:” (g-io-error-quark, 13)
Error creating proxy: Unknown or unsupported transport “disabled” for address “disabled:” (g-io-error-quark, 13)
Error creating proxy: Unknown or unsupported transport “disabled” for address “disabled:” (g-io-error-quark, 13)
Error creating proxy: Unknown or unsupported transport “disabled” for address “disabled:” (g-io-error-quark, 13)
Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
这个是发送图片失败的时候控制台打印的信息，看到你这个消息的时候从控制台启动 找出来的


disable travis

/assign @adambkaplan
/assign @akram

@adambkaplan do you have the green button for this repo?  I no longer do.
if the old ci/openshift-jenkins does not pass, and if an lgtm does not work (this repo is not integrated with our prow stuff ... curious if the aos-cd-jobs stuff still works) then we may need someone like @bparees to green button this one

/LGTM

(this repo is not integrated with our prow stuff ... curious if the aos-cd-jobs stuff still works)

@gabemontero correct me if I'm wrong, https://github.com/openshift/release/pull/21474 aims to fix this situation.

(this repo is not integrated with our prow stuff ... curious if the aos-cd-jobs stuff still works)

@gabemontero correct me if I'm wrong, openshift/release#21474 aims to fix this situation.

no they are unrelated @adambkaplan
this repo is the old plugin that is only supported in 3.x

and yeah the old jenkins based CI is totally a no -go
/assign @bparees
(hoping you can green button this travis disablement PR)

and yeah the old jenkins based CI is totally a no -go
/assign @bparees
(hoping you can green button this travis disablement PR)

thanks @bparees :-)


Remove DataReader's type inference logic

Instead of mapping the the column type name to CLR types, we'll just give one of the five built-in data types:

byte[]
DBNull
double
string
long

If you ask for a specific type (e.g. via GetInt32() or GetFieldValue<int>()) we'll do our best to convert the value to that type.

EF Migrations & Reverse Engineer (and other tools) could either create columns using arbitrary type names that they know how to round-trip (e.g. float -> FLOAT -> float), or use one of the built-in types that won't round-trip (e.g. float -> REAL -> double).


Certificate error

Hi I have a systematic error when trying to connect to the iiasa server, using pyam.iiasa.Connection with credentials, or with ixmp4 login in the command line:
httpx.ConnectError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: Hostname mismatch, certificate is not valid for 'api.manager.ece.iiasa.ac.at'. (_ssl.c:1007)

Any help to solve this issue is welcome. Thanks.

We believe that IIASA ICT changed the SSL certificates by mistake, we notified them and hoping that this will be fixed asap.

It's not just pyam. E.g., the online AR6 scenario explorer at https://data.ece.iiasa.ac.at/ar6/ is also unresponsive. So it's apparently a general server issue, not pyam-related.


Decode request URLs before handling

Variants of some packages (e.g. CPU-only builds of PyTorch) may have characters in their filenames that get percent-encoded. In the given example, + gets encoded to %2B. When pip asks for these filenames, (at least on my machine) it uses percent-encoded URLs in its requests to the morgan server. The server however does not decode these URLs, so it just returns a 404.
Pass the URL to urllib.parse.unquote before urllib.parse.unsplit to fix this. I'm not sure this is the best way to fix it, but it was the easiest. It might make more sense to instead unquote just the path portion of the URL after urlsplit instead of the entire thing.
Note: I did not use morgan itself to retrieve the packages that had those special characters since they were outside of PyPI, and I haven't really looked for an applicable example inside PyPI. I think the idea still applies though, since AFAIK pip will quote any URLs it sends.

Looks good enough to me. Merged manually and released in v0.12.3.


Changelog path option overwrites CHANGELOG.md if multiple projects point to the same location

If there's a conflict between two projects with the same changelog path, it should be addressed.
If this is by design, we need to document it clearly, and I'll add this to the documentation.
Otherwise, we have some options:

Display an interactive message to confirm the action with a yes/no prompt.
Exit with an error message if two changelog paths point to the same location.

We can go with option 2 to give it the same behavior as other error case scenarios.

Hi,
Option 2 seems a good choice.


Suggestions and clarifications around the CONTRIBUTING file

What article on docs.github.com is affected?

Setting guidelines for repository contributors
Source: https://github.com/github/docs/blob/main/content/github/building-a-strong-community/setting-guidelines-for-repository-contributors.md

What part(s) of the article would you like to see updated?

A new section: How GitHub uses the CONTRIBUTING file

It appears as checked on the Community page
It appears as the designated CONTRIBUTING.* guide on the repo contribute page

Example: https://github.com/github/docs/contribute
Side note: Is there actually documentation about how the contribute page works and is generated? Seems like an easter egg, sort of

Then there is this section:

Decide whether to store your contributing guidelines in your repository's root, docs, or .github directory. Then, in the filename field, type the name and extension for the file. Contributing guidelines filenames are not case sensitive, and can have an extension such as .md or .txt.

 Does it mean any extension (such as .rst, often found in Python projects), or is there a limited like to the extensions accepted for the contributing file, or? This should be reworded for clarification. I have noticed that .rst does get picked up, so I know it is at least included.
The other problem with that section:

For the contribute page, what CONTRIBUTING.* file path takes most importance? As in, what if a muddled project has the following:

.github/CONTRIBUTING.md
docs/CONTRIBUTING.md
CONTRIBUTING.md

What's the order of importance?

Maintainer note:
Please follow the Content design plan below to resolve this issue 🎉

Thanks so much for opening an issue! I'll get this triaged for the right team to take a look ⚡

Hi @ScriptAutomate thanks for raising this issue. It's an interesting area and you're right to highlight the ambiguities in the information we currently have. I'll see if I can find the missing information, then we can create content design with your suggestions above and the additional information.

Hi @ScriptAutomate thanks for raising this issue. It's an interesting area and you're right to highlight the ambiguities in the information we currently have. I'll see if I can find the missing information, then we can create content design with your suggestions above and the additional information.

Once the content design is complete, the issue will be ready for a help wanted label.

Once the content design is complete, the issue will be ready for a help wanted label.

Notes
It might also be worth mentioning in About default labels that adding a good first issue label to an issue adds it to the contribute page.

Notes
It might also be worth mentioning in About default labels that adding a good first issue label to an issue adds it to the contribute page.

Content design plan
Proposed content design plan to address this issue.
Topics to update:

Setting guidelines for repository contributors

At the start of the topic, add a new H3 title: "About contributing guidelines"
Expand the first paragraph to explain that:

A link to the contributing guidelines is also shown on the repository's contribute page, for example: https://github.com/github/docs/contribute.

Revise step 3 of the Adding a CONTRIBUTING file procedure to explain that the file will be rendered using a rich text format if it's in a supported format and add the link: For more information, see "[Rendering differences in prose documents](https://docs.github.com/en/github/managing-files-in-a-repository/rendering-differences-in-prose-documents)."
At the end of the Adding a CONTRIBUTING file procedure, add a short sentence that explains that if a repository contains more than one CONTRIBUTING file, then the file shown in links is chosen from .github, the top-level directory, then the docs directory.

Managing labels topic, section About default labels

Add a sentence after the table explaining that issues with the good first issue label are used to populate the repository's contribute page, for example: https://github.com/github/docs/contribute.

Content design plan
Proposed content design plan to address this issue.
Topics to update:

Setting guidelines for repository contributors

At the start of the topic, add a new H3 title: "About contributing guidelines"
Expand the first paragraph to explain that:

A link to the contributing guidelines is also shown on the repository's contribute page, for example: https://github.com/github/docs/contribute.

Revise step 3 of the Adding a CONTRIBUTING file procedure to explain that the file will be rendered using a rich text format if it's in a supported format and add the link: For more information, see "[Rendering differences in prose documents](https://docs.github.com/en/github/managing-files-in-a-repository/rendering-differences-in-prose-documents)."
At the end of the Adding a CONTRIBUTING file procedure, add a short sentence that explains that if a repository contains more than one CONTRIBUTING file, then the file shown in links is chosen from .github, the top-level directory, then the docs directory.

Managing labels topic, section About default labels

Add a sentence after the table explaining that issues with the good first issue label are used to populate the repository's contribute page, for example: https://github.com/github/docs/contribute.

Anyone is welcome to pick this up, following @felicitymay's Content design plan above ☝

Anyone is welcome to pick this up, following @felicitymay's Content design plan above ☝

I am learner can I be able to contribute

I would like to attempt this if possible @janiceilene

@Devilishhh You're welcome to open a PR!

@janiceilene brilliant thank you kindly


svf constructor

class_expression.svf = function(cls_expr, prop_id){

if it doesn't break everything, can the order be inverted to be consistent with http://www.w3.org/TR/owl2-syntax/#Existential_Quantification
if it does break, just document the ordering and close this ticket

It will make something go boink sometime, but all the pieces are out right now so this would be the best time to do it.


Register(): Compute signature and sign list L and merkle tree and publish to BB

For the register() function we need to compute the signature and use it to sign the list L and the merkle tree. Then we need to publish this to the bulletin board database.

Finished with computing the signature and assigning them to the list L and Merkle Tree rtL --> missing appending to the bulletin board


Multiple items using selector doesn't work

anime({
targets: '#cncimage , #3dprintimage',
rotateX: [
{value: 360,duration: 600,easing: 'easeInOutSine',delay: 1000},
],
direction: 'normal',
loop:true
});
It seems doesn't work.

As @stotoma stated, use document.getElementById for elements with an ID


add omit empty to metadata

When we display /debug/connections we do not display metadata

[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[X] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

@ramaraochavali: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
9b124f70d4b8ff750149f1c772331c40b57ea20f
link
true
/test unit-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test unit-tests_istio

@ramaraochavali: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-pilot-k8s-tests_istio
9b124f70d4b8ff750149f1c772331c40b57ea20f
link
unknown
/test integ-pilot-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test integ-pilot-k8s-tests_istio

@ramaraochavali: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-security-k8s-tests_istio
9b124f70d4b8ff750149f1c772331c40b57ea20f
link
unknown
/test integ-security-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ramaraochavali: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-security-k8s-tests_istio
9b124f70d4b8ff750149f1c772331c40b57ea20f
link
unknown
/test integ-security-k8s-tests_istio

integ-security-multicluster-tests_istio
9b124f70d4b8ff750149f1c772331c40b57ea20f
link
unknown
/test integ-security-multicluster-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@ramaraochavali: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-security-multicluster-tests_istio
9b124f70d4b8ff750149f1c772331c40b57ea20f
link
unknown
/test integ-security-multicluster-tests_istio

integ-security-k8s-tests_istio
9b124f70d4b8ff750149f1c772331c40b57ea20f
link
true
/test integ-security-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test integ-security-k8s-tests_istio

@ramaraochavali: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-security-k8s-tests_istio
9b124f70d4b8ff750149f1c772331c40b57ea20f
link
true
/test integ-security-k8s-tests_istio

integ-security-multicluster-tests_istio
9b124f70d4b8ff750149f1c772331c40b57ea20f
link
true
/test integ-security-multicluster-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test integ-security-multicluster-tests_istio

@ramaraochavali: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-security-multicluster-tests_istio
9b124f70d4b8ff750149f1c772331c40b57ea20f
link
true
/test integ-security-multicluster-tests_istio

integ-security-k8s-tests_istio
9b124f70d4b8ff750149f1c772331c40b57ea20f
link
true
/test integ-security-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test integ-security-k8s-tests_istio

@ramaraochavali: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-security-k8s-tests_istio
9b124f70d4b8ff750149f1c772331c40b57ea20f
link
true
/test integ-security-k8s-tests_istio

integ-security-multicluster-tests_istio
9b124f70d4b8ff750149f1c772331c40b57ea20f
link
true
/test integ-security-multicluster-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ramaraochavali: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-security-multicluster-tests_istio
9b124f70d4b8ff750149f1c772331c40b57ea20f
link
true
/test integ-security-multicluster-tests_istio

integ-security-k8s-tests_istio
0d5879abedbd7723f7a58e7d050ddb602092d439
link
true
/test integ-security-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ramaraochavali: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-security-k8s-tests_istio
0d5879abedbd7723f7a58e7d050ddb602092d439
link
true
/test integ-security-k8s-tests_istio

integ-security-multicluster-tests_istio
0d5879abedbd7723f7a58e7d050ddb602092d439
link
true
/test integ-security-multicluster-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


Having Sliding Panel visible programmatically

I need to hide the Sliding Layout until one button is clicked: in this case, the panel get visibile and it can be expanded \ collapsed.
I tried in this way:
onCreate:
dragview = (LinearLayout) findViewById(R.id.dragView);
dragview.setVisibility(View.GONE);
and on click:
dragview.setVisibility(View.VISIBLE);
But it seems not working... any ideas ?

solved with:
dragview.hidePanel();
and
dragview.hidePanel();

very good

Hi,
I can't find the  hidePanel() method, could you tell me which class it is implemented by.
Thanks in advance.

Is the method hidePanel() still available? Can't find it


Resampling inconvenient

The current resampling implementation is inconvenient because it only works for mono-channel and requires the user to use float time indices (monotonically)
Resampler should

accept setting the sample rate
implement sound.Source (multi-channel)

Perhaps it could also implement sound.Sink with dynamic sample rates.
But there is a problem with the dynamic sample rates from an API perspective which is following a pattern found elsewhere (eg sound/ops/Envelope):
providing a method or means to set or get the sample rate isn't good enough, because it places the caller inside the flow of the sound.   By flow of the sound, I mean as it passes through sinks, sources, processors, plugs.  I think most use cases would actually be outside the flow of the sound.  So it would need to be goroutine safe; it would need to handle sample-accurate scheduling if needed.
This is where and why we need to make progress on the ioval module, so the sample rate can be a controller of sound as it flows, not just a method that can be set on every call to Send() or Receive().

Progress merged.
See https://github.com/zikichombo/dsp/pull/13


Track read IDs with a bloom filter in kevlar collect

Suggestion per @ctb: see https://github.com/dib-lab/kevlar/pull/36#issuecomment-280124254.

Not really a pain point, closing for now.


undefined reference to `ossl_ecdsa_sign_sig' in OpenSSL_1_1_1-stable

recently i am reading the openssl's source code on ecdsa algorithm to optimize the performance, the version is Openssl 1.1.1 stable. i want cut out the low level fuction such as ossl_ecdsa_sign_sig and ossl_ecdsa_verify_sig run it, it means i want call the two fuctions directly, because i think it can make me easier to analyze code and optimize code. but when i write a program to call the two function, the error hanppened : undefined reference to ossl_ecdsa_sign_sig , i am sure i link the libcrypto.a, and the library contains the ecdsa_ossl.o which defined the function ossl_ecdsa_sign_sig and ossl_ecdsa_verify_sig.
this is my Makefile, in this file i have link the libcrypto.a, and i have compile the openssl source code to generate the library:
CFLAGS=-Wall -O0 -g
#CFLAGS=-Wall -O0 -g3 -pg -gdwarf-2
CC=gcc

app: test1.o
	$(CC) $(CFLAGS)	\
		-o $@ test1.o	\
		-L /home/tam/Documents/openssl-OpenSSL_1_1_1-stable/ -lcrypto

test1.o: test1.c
	$(CC)	-I/home/tam/Documents/openssl-OpenSSL_1_1_1-stable/include	\
	-I/home/tam/Documents/openssl-OpenSSL_1_1_1-stable/crypto/ec	\
		$(CFLAGS)\
		-c -o $@ test1.c

clean:
	rm -f *.o app

this is my source code which attempt to call two fuctions ossl_ecdsa_sign_sig and ossl_ecdsa_verify_sig(the last two lines, i call the two low level fuctions which have been defined in  ecdsa_ossl.o, and it is included in library libcrypto.a:
#include "testutil.h"

#include <openssl/evp.h>
#include <openssl/bn.h>
#include <openssl/ec.h>
#include <openssl/ossl_typ.h>
#include <openssl/rand.h>
#include "ecdsatest.h"
#include <openssl/crypto.h>
//#include <ec_local.h>
#include <stdint.h>

// use extern to declare the two fuctions
extern int ossl_ecdsa_verify_sig(const unsigned char *dgst, int dgst_len,
                         const ECDSA_SIG *sig, EC_KEY *eckey);
extern ECDSA_SIG *ossl_ecdsa_sign_sig(const unsigned char *dgst, int dgst_len,
                               const BIGNUM *in_kinv, const BIGNUM *in_r,
                               EC_KEY *eckey);

size_t crv_len = 0;
EC_builtin_curve *curves = NULL;

int main(){
  int res1 = 0;
  EC_KEY *eckey = NULL;
  unsigned char dirt, offset, tbs[20]="i love you,love you";
  unsigned char *sig = NULL;
  EVP_PKEY *pkey = NULL;
  EVP_MD_CTX *mctx = NULL;
  size_t sig_len;
  int nid = 0;

  ECDSA_SIG *ret = ECDSA_SIG_new();

  uint64_t t1, t2;

  crv_len = EC_get_builtin_curves(NULL,0);
  curves = OPENSSL_malloc(sizeof(*curves) * crv_len);
  EC_get_builtin_curves(curves,crv_len);

  for(int i=0; i<crv_len; i++){
    nid = curves[i].nid;
    printf("testing ECDSA is %dth, name is %s\n", i+1, OBJ_nid2sn(nid));
  }

  nid = curves[64].nid;

  //mctx = EVP_MD_CTX_new();
  eckey = EC_KEY_new_by_curve_name(nid);
  EC_KEY_generate_key(eckey);
  pkey = EVP_PKEY_new();
  EVP_PKEY_assign_EC_KEY(pkey,eckey);

  sig_len = ECDSA_size(eckey);
  //printf("sig_len的长度为：%d\n",sig_len);
  sig=OPENSSL_malloc(sig_len);

  int dgst_len = 32;
  const unsigned char *dgst[35] = {0x39	,0x74	,0xbf	,0x95	,0xaa	,0x7d	,0xdb	,0xe6,0x63,	0x89,	0xd9,	0xea,	0x50,	0x44,	0xdb,	0xd1,0xbf,	0xce,	0xb6,	0xc8,	0xb8,	0x8c,	0x2e,	0xd5,0xa2,	0x4f,	0xe3,	0x83,	0x6c,	0xd3,	0x36,	0x4f
  };

  BIGNUM *in_kinv = BN_new();
  BIGNUM *in_r = BN_new();

  ret = ossl_ecdsa_sign_sig(dgst, dgst_len, in_kinv, in_r, eckey);

  res1 = ossl_ecdsa_verify_sig(dgst, dgst_len, ret, eckey);

}

when i use make command, the console output the error message below:
gcc -Wall -O0 -g
-o app test1.o
-L /home/tam/Documents/openssl-OpenSSL_1_1_1-stable/ -lcrypto
/usr/bin/ld: test1.o: in function main': /home/tam/shares/win10-share/编程linux二进制imp/Openssl学习/day04_简化版ECDSA/test1.c:69: undefined reference to ossl_ecdsa_sign_sig'
/usr/bin/ld: /home/tam/shares/win10-share/编程linux二进制imp/Openssl学习/day04_简化版ECDSA/test1.c:71: undefined reference to ossl_ecdsa_verify_sig'`
collect2: error: ld returned 1 exit status
make: *** [Makefile:6：app] 错误 1
so is there any solution to help me out to call the two low level ECDSA sig fuctions?

You're most probably linking to the system-wide libcrypto.so and not the libcrypto.a from your build. Just use a  /full/path/to/libcrypto.a instead of -lcrypto when linking?

You're most probably linking to the system-wide libcrypto.so and not the libcrypto.a from your build. Just use a /full/path/to/libcrypto.a instead of -lcrypto when linking?

thank you for your help, i have solved this problem with linking /full/path/to/libcrypto.a and -lpthread, -ldl

Closing since this is answered.


Request to add definition of Divide and Conquer in its Section (readme.md file)

Is your feature request related to a problem? Please describe.
The readme.md file in the Divide and Conquer section doesn't contains the proper definition.
Describe the solution you'd like
Adding a proper definitions with visuals will a good start,
Describe alternatives you've considered
Not Applicable
Additional context
Have a look into this issue, appreciate that you all are doing a great work.

Please assign me this issue. I want to contribute to this repo.

@imranaai  I would like to be assigned to this issue. I am familiar with algorithms and I believe that I can help resolve this issue.

@imranaai  I would like to be assigned to this issue. I am familiar with algorithms and I believe that I can help resolve this issue.

Hi,
Contribute to this repository by following the guidelines and tag this issue if you are solving this problem and then one of the collaborators will look into the PR and merge if they find it suitable.

Please assign this issue to me under SSOC'23. @Kumar-laxmi


[Bug]:

What happened?
Opened menu items, selected set up button, added column locations.
The menu items listing no longer displays data but throws error 500. The page will only display rows where no menu item has been assigned to a location.
To repair this I had to update my locationables table to remove any rows of locationable_type menus
What did you expect to happen?
Location values for any menu items assigned to locations should be shown.
Version
3.5.x
What browser are you seeing the problem on?
Chrome, Safari, Microsoft Edge
Relevant log output
ErrorException: Error: Call to a member function pluck() on string
in /var/www/tamarind/public_html/app/admin/traits/Stockable.php:52

Would you be able to provide a full error trace rather than just the first line?


Broken AWS installation on "provides mysql"

I have a cookbook which depends on this cookbook. The recent changes which brought in provides mysql in https://github.com/chef-cookbooks/mysql/blob/v6.0.25/libraries/provider_mysql_client.rb#L8 caused AWS opsworks deployment to break. Any known reasons?
This was the error given by AWS Opsworks -
================================================================================
Recipe Compile Error in /var/lib/aws/opsworks/cache.stage2/cookbooks/mysql/libraries/provider_mysql_client.rb
================================================================================

NoMethodError
-------------
undefined method `provides' for Chef::Provider::MysqlClient:Class

Cookbook Trace:
---------------
/var/lib/aws/opsworks/cache.stage2/cookbooks/mysql/libraries/provider_mysql_client.rb:8:in `<class:MysqlClient>'
/var/lib/aws/opsworks/cache.stage2/cookbooks/mysql/libraries/provider_mysql_client.rb:6:in `<class:Provider>'
/var/lib/aws/opsworks/cache.stage2/cookbooks/mysql/libraries/provider_mysql_client.rb:5:in `<class:Chef>'
/var/lib/aws/opsworks/cache.stage2/cookbooks/mysql/libraries/provider_mysql_client.rb:4:in `<top (required)>'

Relevant File Content:
----------------------
/var/lib/aws/opsworks/cache.stage2/cookbooks/mysql/libraries/provider_mysql_client.rb:

1:  require 'chef/provider/lwrp_base'
2:  require_relative 'helpers'
3:
4:  class Chef
5:    class Provider
6:      class MysqlClient < Chef::Provider::LWRPBase
7:        include MysqlCookbook::Helpers
8>>       provides :mysql_client
9:
10:        use_inline_resources
11:
12:        def whyrun_supported?
13:          true
14:        end
15:
16:        action :create do
17:          # From helpers.rb

I too am having this same problem.
I'm assuming it has to do with the fact that this cookbook now requires Chef 12, but AWS OpWorks only goes up to 11 for linux instances.
This is going to be a big issue for me, but I'm not sure we can ask for continues support of Chef 11?

If you make use of custom cookbooks, you can update your berksfile and add the following:
cookbook 'mysql', '= 6.0.24'
Which will allow you to update again, but this will lock you in to the last version of mysql.

Also broken on Amazon Linux FWIW.

Sadly, this cookbook is not directly referenced by me, it is in one of the dependencies of another third-party cookbook which depends on this. Any ideas how to stick all of these dependencies to 6.0.24?
I tried mentioning this cookbook with version in Berkshelf file before/after adding 3rd-party cookbook, but it still downloaded latest one :(

Why does reverting to 6.0.24 fix the problem then?

In my case it works because I have a direct dependency and am calling down just that one version. In shrinathaithal case they have a dependency that is specifying the latest as being required, and it wont run. Even if you spec the lower version, the dependency will pull down the latest.

6.0.25 reverted the changes in 6.0.24.
This means you still need to pin Chef belong 12.4.0.
Working on 6.0.26 tonight =)
-s
On Tue, Jul 7, 2015 at 2:33 PM, StarlingHealth<EMAIL_ADDRESS>wrote:

In my case it works because I have a direct dependency and am calling down
just that one version. In shrinathaithal case they have a dependency that
is specifying the latest as being required, and it wont run. Even if you
spec the lower version, the dependency will pull down the latest.
—
Reply to this email directly or view it on GitHub
https://github.com/chef-cookbooks/mysql/issues/364#issuecomment-119295116
.

This is fixed as of v6.0.28.
Also, 12.4.1 should have fixed the problem with 6.0.24 as well.
-s


⚠ Bofrost.be has degraded performance

In 7c6fb7b, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1368 ms

Resolved: Bofrost.be performance has improved in 4c7ac42.


updating the app crashes existing running app in Windows

When I update Toggl Desktop, the current open one crashes. It installs fine, but when it opens back, it has lost the current position/size. This happened in the last 3 updates.
7.1.208

will go away with autoupdater - it will never stop the app itself, only user will restart the app


Killing the lint script still causes unstaged changes to be lost

Description
There was a previous issue: https://github.com/okonet/lint-staged/issues/583 which framed the experience I just had, but I'm running<EMAIL_ADDRESS>— I was making a commit and realized I had skipped something and muscle memory kicked in and I hit Ctrl+C while lint-staged was in the middle of running the "Cleaning up temporary files..." step.
This resulted in all my work being stashed but I didn't have a good means of introspecting where it went (and so I had to sort .git/objects by date and figure out the correct hash).
I was able to overcome this problem, but it seems like the original issue wasn't solved (?)
Steps to reproduce
I believe this happened because I hit Ctrl+C while lint-staged was in the middle of running the "Cleaning up temporary files..." step, but I am not certain.
Debug Logs
<project>/node_modules/.bin/lint-staged
✔ Preparing lint-staged...
✔ Hiding unstaged changes to partially staged files...
❯ Running tasks for staged files...
  ❯ .lintstagedrc.js — 12 files
    ❯ *.{js,jsx,ts,tsx} — 10 files
      ✖ eslint --fix [FAILED]
    ↓ package* — no files [SKIPPED]
    ↓ apps/* — no files [SKIPPED]
↓ Skipped because of errors from tasks. [SKIPPED]
↓ Skipped because of errors from tasks. [SKIPPED]
⠴ Reverting to original state because of errors...
◼ Cleaning up temporary files...
^C

Environment

OS: macOS Ventura 13.5
Node.js: v18.15.0
lint-staged: 13.0.3

If there isn't a good way of ameliorating this, is there some means of asking lint-staged for a log or having it print commit hashes as it works?

lint-staged --no-stash

I've missed this issue. The files are put into a git stash visible with git stash list. There's a message about this in cases where a git operation fails and it cannot be restores automatically. The part where you killed the process normally restores this stash.
I can add some better wording of this in the README because the process shouldn't be killed. We have some custom logic to capture interrupts which could also log a message about the stash.

To my knowledge there isn't a way to list stashes by hash, it's only visible with the name lint-staged automatic backup in git stash list and then applied with the stash index number (lowest number being the most recent).

On further investigation, the hash is already visible in the debug logs and thus could also be printed:
  lint-staged:GitWorkflow Created backup stash with hash 0881de5ed56c0500442bc6c38879e8ef28a21e55 +21ms
  lint-staged:execGit Running git command [
  'stash',
  'store',
  '--quiet',
  '--message',
  'lint-staged automatic backup',
  '0881de5ed56c0500442bc6c38879e8ef28a21e55'
] +21ms
  lint-staged:GitWorkflow Backed up original state in git stash 0881de5ed56c0500442bc6c38879e8ef28a21e55 +8ms


 This branch contains all the big changes needed for the v2.0.0.beta release:

Removal of all adapters
Removal of all deprecated code
Drop support for EOL Rubies and add support for current Rubies
Rename gem to database_cleaner-core
Add new database_cleaner metagem that depends on database_cleaner-active_record

Not ready to merge this yet... I want to get all the adapter repos into a good spot first. But I figured its good to get all this out in the open nice and early, so that people can take a look and give any feedback they might have!
Exciting times for database_cleaner!

@etagwerker @JonRowe All right! I think this PR + https://github.com/DatabaseCleaner/database_cleaner-active_record/pull/3 represent the current vision for v2.0.0. Will y'all take a look and let me know what you think?
When we agree that this all looks good, I'll finish up the other adapters and release v2.0.0.beta versions of everything for wider testing.
Very exciting to finally escape from dependency hell!

@JonRowe @etagwerker Okay, I have removed the [WIP] from the PR title, because I think this is ready to go! There are a few issues that Jon brought up that remain unresolved, like exactly what to do with Gemfile.lock & dependabot, but I don't think those or anything else is blocking a v2.0.0.beta release! We can figure those out in the space between the beta and full release.
I have also created v2.0.0.beta PRs for the five adapters I think we should continue to support (the rest I think we can leave at 1.8):

database_cleaner-active_record
database_cleaner-sequel
database_cleaner-mongoid
database_cleaner-redis
database_cleaner-neo4j

I know both of you are very busy, so any objections to me merging these PRs and cutting v2.0.0.beta releases in, let's say, three days?

I have no objections, but @etagwerker should have a say

@botandrose @JonRowe looking into it. Thanks for your hard work! ❤

@etagwerker @JonRowe I'm feeling pretty good. Any objection to merging this PR (and adapter PRs) into master and releasing a v2.0.0.beta series? Unresolved conversations here could be split off into their own issues to resolve before v2.0.0 final so we don't lose track of them. Yea or nay?

No blocking objections

Okay, I think everything has been resolved, now! Please let me know if not. Merging this into master.

Great work 🙌


export data for listing currencies

Hi, I need a list of currencies and codes to be chosen.

you can already achieve this with require('currency-codes/data')

I see. Thanks.


About the data redundancy removal

Hi the MoLPC team,
What a nice work.
May I ask how to find the codes to perform the step in the green box in Fig. 6. That is: the step 1027-->265 complexes.
Best.

Hi,
This is done with join commands on the pdb ids and clusters within them. This you have to implement yourself given the instructions. Is there something specific you are looking for?
Best,
Patrick


[Gally]: master <- dev

Automatically created by Git-Ally

:tada: This PR is included in version 2.0.31 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Update from admin panel failed and minor subsequent issue as a result

Congrats on 1.3 release folks, keep up the great work. Grav is excellent.
I went to plugins and saw that there was an update to grav available. Hit the button there and got an AJAX error pop up in a red box (Pretty sure that is what it said, sorry, didn't stare at it for too long). The download for the file proceeded, but nothing seemed to happen, so went to CLI and ran self-upgrade. Update installed fine from CLI.
Went back to admin panel and refreshed. A red error popped up saying unable to rmdir /... /assets
The folder had a .gitkeep file in it, but otherwise empty. Ran update for plugins and everything looks fine, so not sure what the AJAX issue was.
Browser was Safari on Mac OS 10.12.5, box is vagrant / vmware hosted local dev in this instance running ubuntu 14.04 / nginx/apache setup via server pilot.

Okay, ran this process again on my other dev vagrant box with a different grav install. Going from 1.2.4 again. Invalid AJAX response pops up after download completed. Nothing happens, download just sits at 100%.
Refreshed admin panel page after gpm self upgrade. Error is:
rmdir(/srv/users/serverpilot/apps/compassdev/public/assets): Directory not empty
All the best.

Tried to update the plugins on this second box via the control panel instead of the CLI. I had used cli for the self-upgrade of Grav. Going via the admin panel seems to have broken the admin panel install. Going to /admin gives me a 404 error now.

The update package does contain an empty assets folder, and this is undoubtedly causing your update issues.  However this is not new and it's no different in this release than in any prior one. Is this the first update you've attempted on these sites?

Hi Andy, no I did an update about a month prior after a long gap to 1.2.4 I think it was. No problems at the time. Honestly can't recall if i did it via command line though, probably did, which doesn't show any errors during upgrading. I reinstalled the admin panel to fix the last 404 issue. All working fine now.

After discussing this on Slack, I've been reliably able to repeat this on a Windows 10 system. To me at least, it looks like on Windows rmdir doesn't remove dot-folders.
With a base grav instance, add a dependency for https://github.com/getgrav/grav-plugin-assets
Do the following:
php bin/grav install
php bin/gpm update -o

See the following error:
  [RuntimeException]
  rmdir(/user/plugins/assets):
  Directory not empty

@damienwebdev @rhukster  I think a Windows fix for this should be made for rmdir()
I experienced this as well today when upgrading a plugin from admin that was installed via bin/grav install from .dependencies . I had to manually delete the .git folder within the plugin before I could upgrade the plugin.
bin/grav  clone repos while bin/gpm download releases.

Is anyone able to get a backtrace on the issue? I've looked through google and it looks like that the hidden folders should already have been taken into account when deleting the folders.
Unfortunately, I don't have Windows computer to play with, which makes it a bit hard to debug this issue.

From previous issues, taken from memory, this would be because any file is locked by a process in Windows. Thus not explicitly a permissions-issue, but rather indirectly. If PHP's rmdir() is told by Windows that the file is busy, it will throw the error. Busy in this context simply means that some process is "locking" the file "obstructively", which quite a lot of software tends to do. Elevated or reassigned permissions will not solve this from any terminal until the process is terminated.
Don't have time to try a replication before next week, but I suspect the deletion of files prior to attempting to deleting the folder is unsuccessful silently, or that a process is still accessing some file - could even be PHP itself.

Yeah, that is what other sources propose as well. In Linux/OSX removing the file just removes its "name", which basically allows processes to keep the file open even after it was deleted. Or in other words, you can delete opened files without getting any errors or bad behavior. Windows doesn't have this behavior, so it cannot delete opened files.
But what comes to .git file, I don't think that Grav uses that file for anything and thus, it shouldn't be open. Unless of course there's git running somewhere.
This also doesn't explain why some people got similar error in OSX or in Linux.

I'm running a dev version on OS X and a live version on Linux. Both are hooked up to .git using the GitSync plugin. Both give me the AJAX error when I click upgrade GRAV. How to fix?


Add validation function

@sami-m-g I added these functions because the default error handling in parse_x gave no error context. Could you please look at this, and maybe suggest a better return type? I don't like what I have now but couldn't come up with something better.
When we have settled on the semantics we also need tests.

@cmutel before going into the validation, since this pull request basically introduces 3 different changes (add documentation, modify schema rules and adds new validation) I would prefer to break it accordingly.
As for validation, the parse function currently throws an exception on schema rules validation. What is the use case we are trying to handle here?

@cmutel, gentle ping!
Also, can you kindly update the schema docs accordingly?

@cmutel right now, the code will throw a similar exception on schema invalidation:
lxml.etree.DocumentInvalid: Element '{http://www.EcoInvent.org/EcoSpold01}referenceFunction', attribute 'amount': 'abc' is not a valid value of the atomic type '{http://www.EcoInvent.org/EcoSpold01}TFloatNumber'., line 17
So why do we need this extra function when you can simply read the exception message or try and catch it accordingly?

@sami-m-g I regenerated the HTML files.
You are right that in certain circumstances we can get reasonable error messages, but this isn't true for parse_directory, where you can only get the filename but not the line number:

Moreover, when dealing with dirty data it is much more convenient to get a list of error instead of fixing them one by one and trying to repare the whole thing. This functionality was added because I spent 2 days debugging a > 100 MB invalid XML file over my vacation, not just for fun. Trust me, when you need it you really need it 😄.