Kafka Consumer lag with high-throughput topics

Describe the bug
When using the Kafka Consumer lag script, if there is too much throughput, most of the data is discarded and the result is empty. The rest of Kafka stats work as usual.
The size of the data buffer in Pixie is currently limited to 1 megabyte per connection, but the perf tests are sending well over that amount of data, so most of it gets dropped. After bumping up the buffer_size and table_store_size_limit , the consumer_latency script should work.
To Reproduce
Launch the consumer-perf/producer-perf test and load the kafka_producer_consumer_latency script.
Expected behavior
We should be able to see the latency in the graphs.
App information (please complete the following information):

Pixie version: latest
K8s cluster version: GKE

This issue was resolved in 553967cb3500fcf.


Update Jekyll & Bulma

I was in the process of creating a very similar project, when I discovered you had created a Jekyll theme for Bulma. I intend to use the Bulma rails
However, if you would like I can update for Bulma 0.5.1 and Jekyll 3.5.2 before I do. Would you be interested in a PR if I do? I know the navbar has probably changed along with a few other minor changes.
Eventually, I'm going to use the bulma-rails gem to manage Bulma, but I can wait to do that until after updating the core files in my fork.
Thanks for the work getting this going!

Hello,
Of course I'll accept PR :+1: Thank you for interest

Thank you for Pull Request, its merged


DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-archive-test-target_71271667-2ef2-497f-b275-4fa39a298eb6/pull/1 is merged into live branch.
Auto archive content to https://github.com/opstest2/docs-archive-test-target_71271667-2ef2-497f-b275-4fa39a298eb6.git

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

File
Status
Preview URL
Details

:x:Error

Details

[Error: GitBranchDeletedOrForcePushed] Cannot sync git repo to specified commit because branch Release_Archive_main_2021-10-11-03-12-15 has been deleted or has been force pushed

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Adjust infrastructure view

add

EKS
Global Accellerator
Lambda

Hi @chrisfarms I made the edits suggested need to get this merged to master


Arrow border

Hi,
Thanks for this awesome plugin!
Now my issue : I'm trying to modify hint.css to add a border to the tooltip but I can't figure out how I should style the arrow. I'd like the whole tooltip to be white with a grey border. Can you help me out ?
Thanks in advance.

Tried doing it and this is the closest I am able to reach: http://codepen.io/chinchang/pen/jPmbdM
The issue in giving border to the arrow is that the arrow is itself made up of borders. Way in which we can have borders for the arrow is by having another arrow placed behind it which is slightly bigger in size. But even this won't work here because we have already consumed both after and before pseudo elements.

Yea, this is pretty much what I managed to come up with as well.

I think we should we improve the class names used to draw the border and arrow so they can be easily targeted, instead of writing cryptic [data-hint]:after overrides.

@joaocunha Arrows (and tooltip body) are made using pseudo elements which cannot have classnames as they are not actual elements one writes in the markup. I guess thats a sort of tradeoff we'll have against the advantage of not having to write extra html to use Hint.css.


Enable golangci linters

Enable following checks in .golangci.yml.
Every PR should fix one rule. There is a chance that some rules are already fixed and we only need to enable them.
After including new rule, please ensure make golangci-lint is passing if there are errors please fix them.
In case there are too many errors feel free to make smaller PRs and enable rules only for specific subdirs (example) or excluding tests (example).

[ ] dogsled
[ ] dupl
[ ] funlen
[ ] gocognit
[ ] goconst
[ ] gocyclo
[ ] godot
[ ] gomnd
[ ] goprintffuncname
[ ] lll
[ ] misspell
[ ] nakedret
[ ] nestif
[ ] prealloc
[ ] unconvert
[ ] unparam
[ ] unused
[ ] usestdlibvars
[ ] whitespace
[ ] wsl

Is there a priority or a preferred order for enabling linters listed above? Or should these just be enabled one by one in given order?

@pawiecz There is no priority. You can choose whatever you want. What's more some of the checks might be better to split into multiple PRs and enable directory by directory.


IOB test failing right after midnight UTC

@danamlewis committed some unrelated comments right before and after midnight UTC, and the no-op commit right after midnight UTC has a failing test: tests/iob.test.js:112:29 "IOB should calculate IOB with Temp Basals and a basal profile", with "expected 0.846 to be below 0.5"
This may indicate that our IOB calculations are somewhat incorrect right after midnight.
https://github.com/openaps/oref0/pull/291/commits/343e7b7a1e162e6ca8060e16d9716d5cdbf316d8
https://travis-ci.org/openaps/oref0/jobs/187101507
not ok 74 IOB should calculate IOB with Temp Basals and a basal profile
AssertionError: expected 0.846 to be below 0.5
at Assertion.fail (node_modules/should/lib/assertion.js:180:17)
at Assertion.prop.value (node_modules/should/lib/assertion.js:65:17)
at Context. (tests/iob.test.js:112:29)

The test is broken, #293 fixes it. The issue was with the with the IOB calculation overlapping midnight with the profile set by the test not extending to cover the end of the day in a determined fashion. The next test from this specifically tests for the midnight scenario and is working as expected. What I'm wondering though is, when committing 216ec855 I tested all the tests ran at midnight, so this should have failed as well.

Should we close this or do you want to validate the fix?


Feature Request: cargo-sqlx sqlite support

Not a dev of sqlx but I would like to start the conversation. cargo-sqlx is great and already my go to tool for migrations in rust but at present it only supports Postgres. What would be needed to add sqlite support?

It actually supports sqlite, we have just forgotten to update the readme. MySql support is on it's way as well.


Start timestamp for points in a cumulative timeseries

Continuing the discussion from this week's meeting. This is not restricted to COUNTER, since histograms can also be cumulative (which is another discussion -- there is a difference between "type" (int, histogram etc) and "kind" (gauge, cumulative) of a metric).
In this model a cumulative point is a tuple (t_start, t, v) where t is the time when value v was sampled and t_start is when the timeseries had value 0.
The motivation for the start timestamp is that it is completely describes the cumulative point and does not assume anything about when the last point was collected. This guards against various inaccuracies caused by the monitoring backend losing points or the source being monitored restarting (or clearing its metric state to save memory), and allows for pushing metrics to the monitoring backend.
For example, consider a source generating counter points at timestamp 0min, 10min, 20min, with values 5, 10, 15 and then it crashes, and finally restarts at 57m, and reports a point with value 17 at 60min. We don't want to incorrectly assume that the counter has increased from 15 to 17 over the interval [20m, 60m]. With a perfect failure detector (which of course doesn't exist) a backend could narrow that interval to  [50m, 60m] but it is still less accurate than the real t_start=57min, which is easy for the source to report.

I'm against this as I believe it's out of scope. This is a format for transferring metrics which are regularly sampled, and you're proposing here to allow for a form of event logging at an arbitrary timestamp not tied to that sampling.

The motivation for the start timestamp is that it is completely describes the cumulative point and does not assume anything about when the last point was collected.

This format is intended for metrics, so regular collection is a fundamental assumption of the format.

allows for pushing metrics to the monitoring backend.

I don't see how this has anything to do with push vs pull, it's the same bits on the wire. Can you expand?

We don't want to incorrectly assume that the counter has increased from 15 to 17 over the interval [20m, 60m].

This is indeed an inaccuracy, however this is rare in practice and I can't recall any Prometheus user ever bringing it up. I don't think we should be violating our status as a metric format for a largely theoretical concern.

This is not event logging, it simply provides a way to expose the creation timestamp of a new series.  This would solve a number of use cases, for example the problem with counters starting at 1 and functions like increase() not having a 0 sample to count that first increment.

We don't want to incorrectly assume that the counter has increased from 15 to 17 over the interval [20m, 60m].

This is indeed an inaccuracy, however this is rare in practice and I can't recall any Prometheus user ever bringing it up. I don't think we should be violating our status as a metric format for a largely theoretical concern.

While it's somewhat rare in practice that we miss counter resets, this has been discussed before.  This does not violate being a "metric format", it's just a slight variation on buffered samples.

This is not event logging, it simply provides a way to expose the creation timestamp of a new series.

We might be able to crowbar that into a metric, we have process start times as a standard thing after all.

This does not violate being a "metric format", it's just a slight variation on buffered samples.

Buffered samples would follow the regular sampling, which this is not doing. That's a different use case.

https://docs.google.com/document/d/1PjwV9h1KdhGotm3-kynLAf--BcaBT1ZOIxXclbbyOE8/edit# "HA pair P1/P2 can be spliced together with each other for eventual consistency" is relevant to this discussion.

I don't fully understand the doc, but being able to splice together data from multiple places that have collected it is similar to what monarch does with its replicated collection. Having a start timestamp is part of what allows this to happen: monarch also does push collection where the same point is pushed to all replicas, so merging these different replica timeseries doesn't involve doing any approximations (this was one of the big motivators for doing push) -- I'm guessing that these approximations are what the debate about "changing data" and "sources of truth" on that thread is about.

@sumeer that is a large part of what this is about, but not fully.
Are you able to point us to a more detailed doc on the considerations of merging TS?

there isn't a detailed doc but basically the design is such that each replica should receive some subset of the points of the timeseries generated by the entity being monitored. And each point should be self-contained so that unioning these sets of points can be done independent of considerations of what sampling period (if any -- there are also non-periodic sampling use cases) was being used (since the sampling period is a policy configuration that can change).

Consensus: Start time SHOULD be included where possible. Client implementations MUST offer this.

For "external long running" should it be recommended to have the exporter poll async and cache (defends against accidential high frequency polling) or should for more flexibility the scraping trigger the collection. (Possibly with a cache for rate limit). Also in that case should the metrics export the cache timestamp?

That's out of scope for openmetrics, and this issue is about something else. Timestamps for general data are to be avoided, as is caching - they cause artifacts and are tricky to deal with.


NIFI-6105: Fix handling of arrays of records/maps in record utilities

Thank you for submitting a contribution to Apache NiFi.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[x] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[x] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[x] Has your PR been rebased against the latest commit within the target branch (typically master)?

[x] Is your initial contribution a single, squashed commit?

For code changes:

[x] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
[x] Have you written or updated unit tests to verify your changes?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
[ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
[ ] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

[ ] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.

@mattyb149 Thanks for the fix! I reviewed and tested the PR, and wanted to discuss about the change a bit.
As a summary, here are the key points:

The reported issue at StackOverflow has been addressed by other changes since NiFI 1.9.0.
But the same flow doesn't work well with schema inference, conversion result has null elements.
To fix no.2 (I assume), this PR modifies DataTypeUtils.isCompatibleDataType. However, I suggest fixing DataTypeUtils.toRecord method instead. DataTypeUtils.toRecord converts Java Map to MapRecord before isCompatibleDataType is called, but it doesn't do so recursively. https://github.com/apache/nifi/blob/master/nifi-commons/nifi-record/src/main/java/org/apache/nifi/serialization/record/util/DataTypeUtils.java#L302

I may be wrong about above analysis.. How do you think?
Please refer followings for details.

Details:
I've tested the Stackoverflow questions flow with NiFi 1.8.0 and I got the reported exception:
2019-03-07 16:51:40,061 ERROR [Timer-Driven Process Thread-6] o.a.n.p.jolt.record.JoltTransformRecord JoltTransformRecord[id=72a28625-3c23-3bc6-73cd-c06d247bf8dc] Unable to write transformed records StandardFlowFileRecord[uuid=c8b59dad-ff78-4c49-898b-9ac6923eb94c,claim=StandardContentClaim [resourceClaim=StandardResourceClaim[id=1551945098069-1, container=default, section=1], offset=0, length=873],offset=0,name=c8b59dad-ff78-4c49-898b-9ac6923eb94c,size=873] due to org.apache.nifi.serialization.record.util.IllegalTypeConversionException: Cannot convert value of class [Ljava.lang.Object; because the type is not supported: org.apache.nifi.serialization.record.util.IllegalTypeConversionException: Cannot convert value of class [Ljava.lang.Object; because the type is not supported
org.apache.nifi.serialization.record.util.IllegalTypeConversionException: Cannot convert value of class [Ljava.lang.Object; because the type is not supported
        at org.apache.nifi.serialization.record.util.DataTypeUtils.convertRecordFieldtoObject(DataTypeUtils.java:460)
        at org.apache.nifi.serialization.record.util.DataTypeUtils.convertRecordMapToJavaMap(DataTypeUtils.java:472)
        at org.apache.nifi.serialization.record.util.DataTypeUtils.convertRecordFieldtoObject(DataTypeUtils.java:444)
        at org.apache.nifi.processors.jolt.record.JoltTransformRecord.onTrigger(JoltTransformRecord.java:318)

However, the flow works fine with NiFi 1.9.0 which has been released recently.
So, the reported issue at Stackoverflow has been fixed by different commit.
Further testing, I found that with NiFi 1.10.0 snapshot master branch, if I used schema inference, result becomes null like this:
Before applying this fix, conversion result was:
[{"DataItems":[null,null,null,null]}]

This happened because the output data type was not found for the inferred Choice[Record, Record] was not compatible with the Java Map type. I assume that's why you fixed isCompatibleDataType method.
https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-standard-services/nifi-record-serialization-services-bundle/nifi-record-serialization-services/src/main/java/org/apache/nifi/json/WriteJsonResult.java#L284
Although I got the expected result with this fix even with schema inference, I think it's more appropriate to fix DataTypeUtils.toRecord method, instead of isCompatibleDataType.
Specifically, following linked line should convert java Map type to MapRecord recursively. Then isCompatibleDataType didn't have to be modified.
https://github.com/apache/nifi/blob/master/nifi-commons/nifi-record/src/main/java/org/apache/nifi/serialization/record/util/DataTypeUtils.java#L302

Makes sense to me, I'll take a look at the toRecord() method, you are right that I fixed isCompatibleDataType because that's where I got to in the debugging where the record choice returned not compatible when given a Map.

@mattyb149 @ijokarumawak I ran this branch against the schemas and data in the stackoverflow questions and got the below error..

org.apache.nifi.serialization.record.util.IllegalTypeConversionException: Cannot convert value [{uuid=MFMS1-MC5, componentId=path1, eventType=Samples, type=PathFeedrate, dataItemId=pf, timestamp=2019-03-01T21:48:27.940558Z, sequence=68104, value=425.5333, name=Fact, subType=ACTUAL, sampleRate=null, statistic=null, duration=null, sampleCount=null, compositionId=null, resetTriggered=null}] of type class java.util.LinkedHashMap for field a to any of the following available Sub-Types for a Choice: [RECORD, RECORD]
	at org.apache.nifi.serialization.record.util.DataTypeUtils.convertType(DataTypeUtils.java:185)
	at org.apache.nifi.serialization.record.util.DataTypeUtils.convertType(DataTypeUtils.java:101)
	at org.apache.nifi.serialization.record.util.DataTypeUtils.convertType(DataTypeUtils.java:97)
	at org.apache.nifi.serialization.record.util.DataTypeUtils.convertType(DataTypeUtils.java:165)
	at org.apache.nifi.serialization.record.util.DataTypeUtils.convertType(DataTypeUtils.java:101)
	at org.apache.nifi.serialization.record.util.DataTypeUtils.toRecord(DataTypeUtils.java:388)
	at org.apache.nifi.serialization.record.util.DataTypeUtils.toRecord(DataTypeUtils.java:329)
	at org.apache.nifi.processors.jolt.record.JoltTransformRecord.transform(JoltTransformRecord.java:390)
	at org.apache.nifi.processors.jolt.record.JoltTransformRecord.onTrigger(JoltTransformRecord.java:333)
	at org.apache.nifi.processor.AbstractProcessor.onTrigger(AbstractProcessor.java:27)
	at org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1162)
	at org.apache.nifi.controller.tasks.ConnectableTask.invoke(ConnectableTask.java:205)
	at org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$1.run(TimerDrivenSchedulingAgent.java:117)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)

Seems like something is still not lining up.

Looks like we're still getting into the isCompatibleDataType() code, @ijokarumawak did I miss something in the toRecord() changes, or do I need to put the isCompatibleDataType() changes back in too? Seems like it shouldn't hurt by having it in there just in case, but I believe you were picturing something else with respect to the toRecord() changes.

Hi @mattyb149
Sorry, you were right with the 1st commit, and I was wrong.  Please check the comment on the PR for detail.


Add support for Extract Statements API

This will allow to execute multiple connections in a single go: https://duckdb.org/docs/api/c/api#extract-statements

Isn't it multiple commands in a single connection (and go)?

Yes, that's right.


Clear instructions on how to use the terminal

Ctrl-Shift-+ to increase the gnome-terminal font size (useful on HiDPI displays)
Command key (on macOS) is not needed at all
Ctrl-Shift-c to copy (e.g. URLs) in gnome-terminal
Ctrl-Shift-v to paste in gnome-terminal
Ctrl-c, Ctrl-v to copy and paste in graphical applications e.g. Firefox

Create repository and share with people
Need to push this to the RSE conference guys


ariaClick always setting tabindex to 0

Issue
Adding a listener via the ariaClick() method always sets the element's tabindex to 0, even if it had a bespoke value beforehand.  Source
This can lead to unexpected behavior such as:
$(`<button tabindex='-1'>`).ariaClick(...);
//tabindex is now 0

Suggestion
I feel the method should only set a value if it was undefined before.

The entire point of the .ariaClick() method is to make WAI-ARIA compatible clickables, which means keyboard navigable (tabbing) as well.
What purpose does disabling keyboard navigation but not mouse clicking serve?  Other than to disadvantage keyboard users?
What are you attempting to achieve?

In my case the buttons are inside a focusable wrapper which handles keyboard inputs and click them programmatically. Having the buttons be focusable made keyboard navigation very cumbersome (focus wrapper => button 1 => button 2 instead of tabbing directly to the next element).
But it surely is a niche, if not bad, example, my point is that this behaviour can be undesirable in more normal uses, for elements that start hidden or disabled.

You can just change the tab index attribute after the ariaClick call.

I can add a tabindex option.  E.g.,
$('<button>').ariaClick({ tabindex : -1 }, …);

Relevant info: https://webaim.org/techniques/keyboard/tabindex

I'm unsure what you believe the relevance to this issue is.

Mainly to let @MalifaciousGames know that setting the tab index to anything but -1 or 0 isn't advised for accessibility reasons.


List of features for eventual backporting

The current list of features that are planned for backporting. Suggest more in this thread.

[ ] Fence gates
[ ] Sprinting
[ ] Beef
[ ] Melons
[ ] Stair corner rendering
[ ] More stair and slab types
[ ] Stone bricks
[ ] Better lighting system
[ ] New button recipe, wooden buttons
[ ] Glass panes
[ ] Abandoned mine shafts
[ ] New bow mechanics
[ ] Arrows that stick out of entities
[ ] Prevent player-placed leaves from decaying
[ ] 3D chest model and animation
[ ] New inventory handling (painting, etc)
[ ] Breeding
[ ] Server browser
[ ] 256 max world height
[ ] Send biomes to clients
[ ] In-game list of online players

Taller max world height.

Taller max world height.

Agreed.

Make biome generation server-side.

Make biome generation server-side.

Yep.

Added In-game list of online players

All the redstone changes, like comparators, daylight sensors, slime blocks, etc.

All the redstone changes, like comparators, daylight sensors, slime blocks, etc.

Nope.

Daylight sensors?

Daylight sensors?

Nope.

Horses? (Not necessarily for riding)

Horses? (Not necessarily for riding)

No.

Upside-down stairs, really useful for decorating

Agreed on the former, and the latter is a feature that existed in beta 1.7.3 and is going to be added anyway.

can the 3D chest model be optional?

can the 3D chest model be optional?

I don't see why not. We'll probably turn it off for a high performance mode (along with transparent leaves and such).

please, please, please do not backport sprinting. sprinting broke combat completely, and monsters have not been a threat since sprinting was added. also make the beta 1.8 lighting optional. it is better in some ways, but worse in others. part of the charm of beta 1.7 was its lighting. same goes for bow mechanics. the old bows are completely different, and huge part of the old game. make the modern chest models optional as well. i like them, but i also like the old ones (this may mean having the 3d chests take up a full block, but they only recently changed that, so that shouldnt be a big deal).

Redstone block and lamp?
Pistons?
All the types of pressure plates?

Redstone block and lamp?

Block no, lamp maybe.

Pistons?

These are already present in beta 1.7.3.

All the types of pressure plates?

I'll do stone and wooden and maybe an original one.

@SirCmpwn consider implementing redstone block as a decorative block only?

Probably not.

@jleclanche make it a mod when the API is ready, if you really want it :wink:

All the redstone changes, like comparators, daylight sensors, slime blocks, etc.

I'd really like to see just comparators implemented, they implement the ability to use hex in redstone. Adding everything else would be annoying, though.

I'd really like to see just comparators implemented, they implement the ability to use hex in redstone. Adding everything else would be annoying, though.

Nope. The changes Mojang have made to redstone over the past few years are the worst of the changes they've made by far. The likelihood of them being backported is quite small.

the worst changes they've made by far.

Comparators are one of the only good changes they've made! It feels like a feature that should have been in the game for years.

Well, feel free to mod them into TrueCraft once we get modding support going.

What language will the modding be in? C#?

Any .NET language. There are a lot of them.

Friendly mobs flee from you if you attack them? But with a better pathfinding?

The behavior of mob AI is not really a "feature" per-se, so long as, you know, skeletons fire arrows and creepers explode and what-not.

exploding arrows.
just please for the love of god never backport exp or hunger. two of the most obnoxious things added to beta 1.8 aside from the "swamp" biome.
as for running, maybe we can make like a running shoes sort of item modification? idk how lenient you'd be on custom items.

exploding arrows.

...was this ever a thing?

just please for the love of god never backport exp or hunger. two of the most obnoxious things added to beta 1.8 aside from the "swamp" biome.

Agreed.

as for running, maybe we can make like a running shoes sort of item modification? idk how lenient you'd be on custom items.

I'm still inclined to add Mojang-style sprinting and give the ability to mobs as well to balance it out.

I like the swap biome :(
But yeah +1 on exp/hunger. What trash.

I don't mind the swap biome either, but I'm going to let you customize the biomes in use for your worlds.

...was this ever a thing?
no just light banter

I think as long as it's balanced it'll work out fine. Also biome customisation works out great too. Awesome!

"exploding arrows."

...was this ever a thing?

It's being added to 1.9, which is coming soon.

EDIT: What about strongholds/mineshafts? I actually personally don't mind those too much and feel like they add a little bit of flavour to the world. Even if it's a custom generation option.

Mineshafts sure, strongholds maybe.

It's being added to 1.9, which is coming soon.

Well, don't expect them in TrueCraft.

Can you add creative mode?

I will not support creative mode, if implemented. I'll probably make a mod to cut it out if it gets backported.
Also, please do not backport strongholds. They are boring, full of cheat-loot and don't feel natural at all. I wouldn't like mineshafts either, but I can't decide everything in this project.

Why? It would be good just for building
16 sie 2015 22:02 "Stian Furu Øverbye"<EMAIL_ADDRESS>napisał(a):

I will not support creative mode, if implemented. I'll probably make a mod
to cut it out if it gets backported.
Also, please do not backport strongholds. They are boring, full of
cheat-loot and don't feel natural at all. I wouldn't like mineshafts
either, but I can't decide everything in this project.
—
Reply to this email directly or view it on GitHub
https://github.com/SirCmpwn/TrueCraft/issues/27#issuecomment-131616440.

Gamemodes are a clutterf*ck, and if someone wants it then make a mod.

Some serious entitlement going on over here.

It's up to @SirCmpwn to decide to implement Creative mode, and strongholds. Personally, I think Creative should be added, but it should be a mod that is already included in TrueCraft's source, so you have to enable it if you want to use it.
Same with strongholds.

Creative mode - yes
Strongholds - no
Mineshafts - yes
Justification for mineshafts - they encourage exploring underground. We can deal with balance issues separately if it's a problem.

Minecraft's first game mode was creative, really; so it makes sense to back-port it. @SirCmpwn Did you manage to troubleshoot the previous issues with OpenGL, or are you fine with me resuming client development regardless?

I haven't spent any time on it, @mrpimpunicorn. I will get back to it soon, my focus at the moment is on other projects.

Can you add trees species from new version and biomes such as jungle?

No.

Could you add a method of legally obtaining ice blocks (without enchantments)? Or perhaps and new slippery block to be used soley for building purposes? I feel this was seriously missing from b1.7.3.

Probably, yes, but that falls under original features and is outside the scope of this issue.

Oh, my bad. Should we discuss this on the Subreddit?

I suppose. I'd prefer to discuss it once we reach feature parity with beta 1.7.3, since it's certainly happening no earlier than that.

May I ask why you want to backport beef? I think it was a better design choice back in 1.7.3 when each passive mob had their own unique drop: pigs for meat, cows for hide, sheep for wool and chickens for feathers. Having more than one mob drop food seems kinda superfluous, in my opinion.

Someone asked about beef, but I guess the comment was deleted? A greater variety of food is why I want beef, but also because it lines up with the vision by being both realistic and useful, as well as adding an interesting mechanic of cooking your food.

Are we still talking about minecraft?

Well, within a certain limit of "realism". One of my problems with modern MC is that it gets harder and harder to suspend your disbelief at the idea that you could wake up in the wilderness and manage to acquire all of the resources that modern MC lets you get. Beef doesn't hurt that.

I was making a joke. I'm hungry. :)

I was the guy who posted about beef. I redacted it because it felt kinda bitchy to me at the time.

May I ask why you want to backport beef? I think it was the better design choice back in 1.7.3 when each passive mob had their own unique drop: pigs for meat, cows for hide, sheep for wool and chickens for feathers. Having more than one mob drop food always seemed kinda superfluous, in my opinion.

Thanks for responding, SirCmpwn! I really appreciate it.

Last question: What is "Better lighting system"?

Doing day/night cycle lighting on the fly instead of the update-the-world approach beta 1.7.3 takes. The b1.7.3 strategy is actually so stupid that I'm just not implementing it at all and we're going straight to the "better" way.

Haha, okay. Thanks!

[ ] 256 max world height

Any particular reason why it's 256?

Originally it was a size "optimization". A limit of 256, (or at the time 128) allowed a y-position (vertical axis) to be stored as a single byte on disk (and in the 128 days, a single signed bit in memory, due to java not having unsigned types).

Due to restrictions imposed by Minecraft. At some point we may be able to drop the vertical limit entirely.

I always thought all animals should drop meat in Minecraft. Even sheep. But I'd expect non-pig animals would drop less meat, as to keep pigs useful.

Propose that in #211

I hope some form of spriting or fast transport is implemented, regardless of what it is. I absolutely hated how slow the player walks and remember being overjoyed when sprinting was implemented, the days of going agonizingly slow from place to place were over.
Since hunger isn't a thing, maybe you can make running (be it a natural ability or through some kind of item) take health away instead? That would also discourage using running to get away from mobs, since it would weaken you and make you more vulnerable. Perhaps you could also implement running speed in the armor types (like leather goes 0.2x speed and diamond would be maybe 2.5x speed). Though I'm not sure how good an idea that is considering it takes like 20 minutes to get diamonds.
Also, what about hoppers? Those are post-b.1.7 right? They're a little more convenient than mile-long ice streams that send items into unloaded chunks (to later cause immense lag when you load them all in for collection).

sprinting takes away health

No, but you will only be able to do it for a short amount of time

running speed with armor

Nah

hoopers

No


3.8.1 : collect + sort query issued through ArangoJS crashes server (sigsegv)

My Environment

ArangoDB Version:        3.8.1
Storage Engine:             RocksDB
Deployment Mode:       Single Server
Deployment Strategy:   systemd
Infrastructure:               own
Operating System:        Ubuntu 20.04
Total RAM in your machine:        64GB (machine 1) / 256 GB (machine 2)
Disks in use:        HDD (machine 1) / SSD (machine 2)
Used Package:             Ubuntu .deb

Component, Query & Data
Affected feature:
ArangoDB server stability / AQL query with ArangoJS driver
AQL query (if applicable):
let p = @p
collect project = p
sort project
return 1

with p a bind variable defined in Javascript code.
Dataset:
Not relevant: query does not read any collection data.
Steps to reproduce
3.8.1_crash_test.zip

unpack test program above
npm install
run the Nodejs/ArangoJS test program many times, for ex. using while true; do nodejs test.js ; done
after a random number of executions, one will eventually fail and make the server crash

ArangoJS version is 7.6.0 (latest) but bug already occurred with 7.5.0
ArangoDB version is 3.8.1
This bug is reproducible on another machine running ArangoDB v3.8.1 on Ubuntu 20.04 too
Problem:
Server crashes with an error like the following (strack trace is not always the same):
2021-10-21T10:18:31Z [132603] FATAL [a7902] {crash} 💥 ArangoDB 3.8.1 [linux], thread 4 [SchedWorker] caught unexpected signal 11 (SIGSEGV) accessing address 0x0000000000000000: signal handler invoked - image base address: 0x00007f03ee1bf000 - CPU context: rip: 0x00007f03ef50655f, rsp: 0x00007f03e61f75c0, efl: 0x0000000000010246, rbp: 0x00007f03e61f75d0, rsi: 0x00007f03e61f75e8, rdi: 0x00007f03e61f75f0, rax: 0x00007f03ef506510, rbx: 0x0000000000000000, rcx: 0x00007f02c10ae600, rdx: 0x0000000000000000, r8: 0x0000000000000003, r9: 0x0000000000000000, r10: 0x00000000000000b8, r11: 0x00007f03e61fab20, r12: 0x00007f03e61f75f0, r13: 0x00007f03e61f75e8, r14: 0x0000000000000000, r15: 0x00007f03e61f7be8
2021-10-21T10:18:31Z [132603] INFO [c962b] {crash} Backtrace of thread 4 [SchedWorker]
2021-10-21T10:18:31Z [132603] INFO [308c3] {crash} frame  1 [+0x0000000000806515] (anonymous namespace)::crashHandlerSignalHandler(int, siginfo_t*, void*) (+0x35)
2021-10-21T10:18:31Z [132603] INFO [308c3] {crash} frame  2 [+0x00000000039bf393] sigprocmask (+0x21)
2021-10-21T10:18:31Z [132603] INFO [308c3] {crash} frame  3 [+0x000000000134f81a] arangodb::aql::ExecutionPlan::findCollectionAccessVariables() (+0x6a)
2021-10-21T10:18:31Z [132603] INFO [308c3] {crash} frame  4 [+0x00000000013b49e5] arangodb::aql::ExecutionEngine::instantiateFromPlan(arangodb::aql::Query&, arangodb::aql::ExecutionPlan&, bool, arangodb::aql::SerializationFormat) (+0x4d5)
2021-10-21T10:18:31Z [132603] INFO [308c3] {crash} frame  5 [+0x00000000006ab9b7] arangodb::aql::Query::prepareQuery(arangodb::aql::SerializationFormat) [clone .constprop.0] (+0x7d7)
2021-10-21T10:18:31Z [132603] INFO [308c3] {crash} frame  6 [+0x00000000015c2235] arangodb::aql::Query::execute(arangodb::aql::QueryResult&) (+0xa95)
2021-10-21T10:18:31Z [132603] INFO [308c3] {crash} frame  7 [+0x00000000006d29cc] arangodb::RestCursorHandler::processQuery(bool) [clone .constprop.0] (+0x2c)
2021-10-21T10:18:31Z [132603] INFO [308c3] {crash} frame  8 [+0x0000000001952afe] arangodb::RestCursorHandler::registerQueryOrCursor(arangodb::velocypack::Slice const&) (+0x6fe)
2021-10-21T10:18:31Z [132603] INFO [308c3] {crash} frame  9 [+0x000000000195381b] arangodb::RestCursorHandler::execute() (+0x8fb)
2021-10-21T10:18:31Z [132603] INFO [308c3] {crash} frame 10 [+0x00000000019c01a6] arangodb::rest::RestHandler::executeEngine(bool) (+0xb6)
2021-10-21T10:18:31Z [132603] INFO [308c3] {crash} frame 11 [+0x00000000019ea72a] arangodb::rest::RestHandler::runHandlerStateMachine() (+0x36a)
2021-10-21T10:18:31Z [132603] INFO [308c3] {crash} frame 12 [+0x0000000001670b16] arangodb::Scheduler::WorkItem<arangodb::rest::CommTask::handleRequestSync(std::shared_ptr<arangodb::rest::RestHandler>)::{lambda()#1}>::invoke() (+0x126)
2021-10-21T10:18:31Z [132603] INFO [308c3] {crash} frame 13 [+0x0000000001859e2f] arangodb::SupervisedScheduler::runWorker() (+0x43f)
2021-10-21T10:18:31Z [132603] INFO [308c3] {crash} frame 14 [+0x000000000080d1a9] arangodb::Thread::startThread(void*) (+0x69)
2021-10-21T10:18:31Z [132603] INFO [308c3] {crash} frame 15 [+0x00000000007b135f] ThreadStarter(void*) [clone .lto_priv.0] (+0x8f)
2021-10-21T10:18:31Z [132603] INFO [308c3] {crash} frame 16 [+0x00000000039c6167] start (+0x70)
2021-10-21T10:18:31Z [132603] INFO [ded81] {crash} available physical memory:<PHONE_NUMBER>8, rss usage:<PHONE_NUMBER>, vsz usage:<PHONE_NUMBER>8, threads: 47

Client receives error:
Error: socket hang up
    at connResetException (node:internal/errors:683:14)
    at Socket.socketOnEnd (node:_http_client:471:23)
    at Socket.emit (node:events:406:35)
    at endReadableNT (node:internal/streams/readable:1329:12)
    at processTicksAndRejections (node:internal/process/task_queues:83:21) {
  code: 'ECONNRESET',

Expected result:
No crash :)
Maybe this bug is related to ArangoJS more than Arangodb server ?
Thanks a lot for your consideration.
Mathias

We can confirm that this is fixed in 3.8.3 : crash test program runs fine without crashing the server.

@matcho: Thanks for the confirmation! I am glad the issue is solved now, and sorry for the trouble!


Upgrade to Spring Native 0.12.0

Release notes for 0.12.0
This likely requires Spring Boot 2.7.0, which is being worked on in https://github.com/jhipster/generator-jhipster/pull/18511.

Specially looking forward to the devtools fix for gradle 🎉

@mraible @mshima Should be do a release with these changes (jh 7.9.2, latest spring native)?

Yes, I think we should!
/cc @alina-yur

@atomfrede @mraible yes please!:)

I will do 2 more adjusts and release.

Version 1.3.0 is published.


PowerToys Run shows black text on black background

Microsoft PowerToys version
0.87.0
Installation method
PowerToys auto-update
Running as admin
No
Area(s) with issue?
PowerToys Run
Steps to reproduce
When opening PowerToys Run (using Alt + Space) I get the input window, but I can't see my input or the results because everything is black except the application icons.
This occurs regardless of whether I have Windows set to Light or Dark mode. This started after the last update (to v 0.87.0), before that I got a light colored input with black text.
✔ Expected Behavior
I'm expecting the input to look like it used to, like on the PowerToys Run page
❌ Actual Behavior

Other Software
No response

What Windows version is this on?
We've switched back to the native .NET WPF release for 0.87.0 . Can you please try the WPF Preview Gallery to check if the same is happening there? https://apps.microsoft.com/detail/9ndlx60wx4kq
/needinfo

Thanks for the quick response!
This is on Windows 11 Enterprise 21H2 (os build 22000.3260).
I've downloaded the WPF Preview Gallery. Is there anything specific I need to check there? I've clicked around in the samples and things look good there.

I've also attached the generated PowerToys report in case it helps.
PowerToysReport_2024-12-18-11-27-10.zip

Wonder if this is a Windows 11 Enterprise 21H2 specific issue 🤔

I have the same problem on 0.87.0, when the selected app theme is a dark color it behaves normally, light colors will appear black on black.
Windows 11 21H2 22000.2538

I can confirm that the same thing happens for me. Windows is set to light mode. If I change the "App theme" setting in PowerToys Run to Dark, then I get the white text on black background.


Muzei Widget

Add a simple widget which allows the user to open the activity and skip the current artwork displayed.
A user of my Tumblr for Muzei extension sent the request so I thought I would take a crack at it.
http://jimmithy.tumblr.com/post/86502807543/hello-there-first-of-all-i-would-like-to
Design could probably do with some work, but what do you think?

Thanks so much for putting in this pull request: it has constantly reminded me that there's no widget for Muzei. While we didn't go with this design, I have added a widget with a 'Next Artwork' action in #347


customer cannot select desired spec folder for new service

If the service is new and needs a new spec folder, customer cannot select desired spec folder.

For new service, warn to onboard shift-left.
Get the RP folder from service team from PM, input to dataverse manually beforehand.

Remove this popup, but we need fill rp folder manually beforehand.


Upload fianl status file to artifacts

can you add some documentation on how to use that action? e.g. some sort of README or comment with an exemple.
(and ideally also explain why we do this, so that people will stop wondering...)

done :slightly_smiling_face:

LET'S GO FOR MERGE


S3 multipart upload subscriber hangs for smaller chunks < 5MB

There is a bug in the multipart upload implementation that makes the process to hang when the emitted chunks are smaller than the minimum configured chunk size. Since in this case it would enter into an infinite loop.
On the other hand, the implementation should require that the minimum configurable chunk size can not be smaller than 5MB, since if that happens, the upload of a single part would be triggered and it that's not allowed by the s3 service.

The fix will be covered as part of the next release 0.5.0.
In case someone is experiencing this issue please raise it up, and we'll release a hotfix.


Use mise ls --offline

mise ls can be slow now. I think this plugin should use the new --offline flag (https://github.com/jdx/mise/issues/2949)
https://github.com/134130/intellij-mise/blob/587b263c7ff40e59ca94734abb51c6b908785b07/modules/core/src/main/kotlin/com/github/l34130/mise/commands/MiseCmd.kt#L41

Thanks! I think it's what causing the IDE to freeze on startup with the latest version

@hverlin Hi, I've added this feature in v2.2.0. It will be available in JetBrains Marketplace soon. Thanks!


Update language server setup info for Helix

Summary
The info on Helix was out of date, version 23.10 has been out for 5 weeks+: https://helix-editor.com/news/release-23-10-highlights/. It now has the multiple language servers feature built in. You can see it is widely adopted here: https://github.com/helix-editor/helix#installation, and anyone can download the binary https://github.com/helix-editor/helix/releases/tag/23.10, so it is readily available for all users.
Another point of concern is the redundancy of keys in the current configuration. Many of the keys are unnecessary duplicates, as they are already inherited from the default configuration found at https://github.com/helix-editor/helix/blob/master/languages.toml. Users should only need to specify overrides or add new keys in their personal configuration files. I have not altered that as perhaps there was a reason behind this decision I might not be aware of?
Thank you for providing information about setting up Helix; it's truly appreciated!

I am testing some configs out and am getting unsupported method: textDocument/formatting in the Helix log. Is biome meant to offer LSP formatting? Helix can use something like the previous formatter = { command = "biome", args = ["format", "--stdin-file-path", "test.js"]} but it is only a fallback and might not even work unless biome can accept an argument to tell it what language to format, for example Prettier takes:
formatter = { command = 'prettier', args = ["--parser", "html"] }

I am testing some configs out and am getting unsupported method: textDocument/formatting in the Helix log. Is biome meant to offer LSP formatting?
Helix can use something like the previous formatter = { command = "biome", args = ["format", "--stdin-file-path", "test.js"]} but it is only a fallback and might not even work unless biome can accept an argument to tell it what language to format, for example Prettier takes:
formatter = { command = 'prettier', args = ["--parser", "html"] }

Formatting is enabled with dynamic capabilities, but we plan to revert this change and make the registration in standard way

@ematipico Thanks for the info! Do you have an idea when this change will happen? It will affect this pull request, so I could wait if it was expected soonish to avoid any attempts at hacky workarounds.

Formatting is enabled with dynamic capabilities, but we plan to revert this change and make the registration in standard way

Hi, I see https://github.com/biomejs/biome/pull/1104/files is merged, great! I assume this fixes the problem with Helix and LSP formatting... do you have an idea when a new version will be released, or a nightly with this feature on NPM?

I just published one

OK, I have made the changes I mentioned and it all seems great :) This should be ready to merge as soon as the new version of Biome is published.
@bugeats I see you made the last relevant change to these docs before me, does this look good to you?

@bugeats I see you made the last relevant change to these docs before me, does this look good to you?

Yep looks right to me but I haven't tested it verbatim in Helix.

We will merge this once the next release lands :)

The 1.5.0 release is out :)

The 1.5.0 release is out :)

Hi there. I already installed it but there is some errors:

This is an example of my config file:
        {
          name = "tsx";
          auto-format = true;
          language-servers = [
            {
              name = "typescript-language-server";
              except-features = ["format"];
            }
            "biome"
          ];
          auto-pairs = commonAutoPairs;
        }

@linuxmobile The warnings are fine and should not affect things working, they just reflect what Helix can do right now. The errors seem to come from type-script-language-server so seem to be an issue with that.
Is biome working for you? It works fine for me with the settings I provided in this pull request, at least with TypeScript. Here are the warnings and errors I get running a TypeScript project, biome linting and formatting are working fine:
2024-01-13T11:14:57.592 helix_term::application [WARN] Received unregistration request for unsupported method: workspace/didChangeConfiguration
2024-01-13T11:14:57.592 helix_term::application [WARN] Received unregistration request for unsupported method: textDocument/rangeFormatting
2024-01-13T11:14:57.592 helix_term::application [WARN] Received unregistration request for unsupported method: textDocument/onTypeFormatting
2024-01-13T11:14:57.592 helix_term::application [WARN] Received unregistration request for unsupported method: textDocument/rename
2024-01-13T11:14:57.592 helix_term::application [WARN] Received unregistration request for unsupported method: textDocument/formatting
2024-01-13T11:14:57.592 helix_term::application [WARN] Ignoring a client/registerCapability request because dynamic capability registration is not enabled. Please report this upstream to the language server
2024-01-13T11:14:57.592 helix_term::application [WARN] Ignoring a client/registerCapability request because dynamic capability registration is not enabled. Please report this upstream to the language server
2024-01-13T11:14:57.592 helix_term::application [WARN] Ignoring a client/registerCapability request because dynamic capability registration is not enabled. Please report this upstream to the language server
2024-01-13T11:14:57.639 helix_term::application [ERROR] received malformed notification from Language Server: Unhandled

You can see the biome lint in the top corner:

I am running the latest Helix master, if biome is not working as intended with the settings in this pull request, could you try the latest master? Cheers!

@linuxmobile The warnings are fine and should not affect things working, they just reflect what Helix can do right now. The errors seem to come from type-script-language-server so seem to be an issue with that.
Is biome working for you? It works fine for me with the settings I provided in this pull request, at least with TypeScript. Here are the warnings and errors I get running a TypeScript project, biome linting and formatting are working fine:
2024-01-13T11:14:57.592 helix_term::application [WARN] Received unregistration request for unsupported method: workspace/didChangeConfiguration
2024-01-13T11:14:57.592 helix_term::application [WARN] Received unregistration request for unsupported method: textDocument/rangeFormatting
2024-01-13T11:14:57.592 helix_term::application [WARN] Received unregistration request for unsupported method: textDocument/onTypeFormatting
2024-01-13T11:14:57.592 helix_term::application [WARN] Received unregistration request for unsupported method: textDocument/rename
2024-01-13T11:14:57.592 helix_term::application [WARN] Received unregistration request for unsupported method: textDocument/formatting
2024-01-13T11:14:57.592 helix_term::application [WARN] Ignoring a client/registerCapability request because dynamic capability registration is not enabled. Please report this upstream to the language server
2024-01-13T11:14:57.592 helix_term::application [WARN] Ignoring a client/registerCapability request because dynamic capability registration is not enabled. Please report this upstream to the language server
2024-01-13T11:14:57.592 helix_term::application [WARN] Ignoring a client/registerCapability request because dynamic capability registration is not enabled. Please report this upstream to the language server
2024-01-13T11:14:57.639 helix_term::application [ERROR] received malformed notification from Language Server: Unhandled

You can see the biome lint in the top corner:
I am running the latest Helix master, if biome is not working as intended with the settings in this pull request, could you try the latest master? Cheers!

I'm using the helix master branch. Biome linting is working perfect. The log error in Helix happens when I want to format the code, until then the error does not appear. (Obviously it doesn't format the code)

TypeScript seems to format fine, and here is my Helix log after the format:
2024-01-13T15:50:17.200 helix_term::application [WARN] Received unregistration request for unsupported method: workspace/didChangeConfiguration
2024-01-13T15:50:17.200 helix_term::application [WARN] Received unregistration request for unsupported method: textDocument/rangeFormatting
2024-01-13T15:50:17.200 helix_term::application [WARN] Received unregistration request for unsupported method: textDocument/onTypeFormatting
2024-01-13T15:50:17.200 helix_term::application [WARN] Received unregistration request for unsupported method: textDocument/rename
2024-01-13T15:50:17.200 helix_term::application [WARN] Received unregistration request for unsupported method: textDocument/formatting
2024-01-13T15:50:17.200 helix_term::application [WARN] Ignoring a client/registerCapability request because dynamic capability registration is not enabled. Please report this upstream to the language server
2024-01-13T15:50:17.200 helix_term::application [WARN] Ignoring a client/registerCapability request because dynamic capability registration is not enabled. Please report this upstream to the language server
2024-01-13T15:50:17.200 helix_term::application [WARN] Ignoring a client/registerCapability request because dynamic capability registration is not enabled. Please report this upstream to the language server
2024-01-13T15:50:17.212 helix_term::application [ERROR] received malformed notification from Language Server: Unhandled
2024-01-13T15:50:21.940 helix_lsp::util [WARN] LSP position Position { line: 95, character: 0 } out of range assuming EOF

Why not try and format the same file as me and see if it works: https://github.com/David-Else/zombie-attack-4/blob/main/src/index.ts
Here is my Helix config:
[language-server]
biome = { command = "biome", args = ["lsp-proxy"] }

[[language-server.vscode-json-language-server.config.json.schemas]]
fileMatch = ["tsconfig.json", "tsconfig.*.json"]
url = "https://json.schemastore.org/tsconfig.json"

[[language-server.vscode-json-language-server.config.json.schemas]]
fileMatch = [ "package.json" ]
url = "https://json.schemastore.org/package.json"

[language-server.rust-analyzer.config]
check.command = "clippy"
# check = {command = "clippy", extraArgs = ["--", "-W", "clippy::unwrap_used", "-W", "clippy::expect_used", "-W", "clippy::pedantic", "-W", "clippy::nursery"]}

[language-server.ltex-ls.config]
ltex.diagnosticSeverity = "warning"
ltex.disabledRules = { "en-US" = ["PROFANITY"], "en-GB" = ["PROFANITY"] }
ltex.dictionary = { "en-US" = ["builtin", "Lazygit", "chainable", "textobject", "textobjects", "togglable", "Deno"  ], "en-GB" = ["builtin", "Lazygit", "chainable", "textobject", "textobjects", "togglable", "Deno" ] }

[language-server.yaml-language-server.config.yaml]
schemas = { "https://raw.githubusercontent.com/ansible/ansible-lint/main/src/ansiblelint/schemas/ansible.json#/$defs/playbook" = "*play*.{yml,yaml}" }

[[language]]
name = "markdown"
text-width = 80
soft-wrap = { wrap-at-text-width = true }
language-servers = ["ltex-ls", "marksman"]
formatter = { command = 'prettier', args = [
  "--parser",
  "markdown",
  "--prose-wrap",
  "never", # <always|never|preserve>
] }
auto-format = true

[[language]]
name = "html"
language-servers = [ "vscode-html-language-server", "tailwindcss-ls" ]
formatter = { command = 'prettier', args = ["--parser", "html"] }

[[language]]
name = "json"
language-servers = [ { name = "vscode-json-language-server", except-features = [ "format" ] }, "biome"]

[[language]]
name = "css"
language-servers = [ "vscode-css-language-server", "tailwindcss-ls" ]
formatter = { command = 'prettier', args = ["--parser", "css"] }

[[language]]
name = "yaml"
formatter = { command = 'prettier', args = ["--parser", "yaml"] }
auto-format = true

[[language]]
name = "javascript"
language-servers = [ { name = "typescript-language-server", except-features = [ "format" ] }, "biome"]
auto-format = true

[[language]]
name = "typescript"
language-servers = [ { name = "typescript-language-server", except-features = [ "format" ] }, "biome"]
auto-format = true

[[language]]
name = "bash"
formatter = { command = 'shfmt', args = ["-i", "4"] }
auto-format = true

[[language]]
name = "git-commit"
language-servers = ["ltex-ls"]

[[language]]
name = "python"
formatter = { command = "black", args = ["--quiet", "-"] }
auto-format = true
language-servers = ["pyright"]
# pyproject.toml
# [tool.pyright]
# typeCheckingMode  = "strict"

@ematipico Do you think this is Biome or a Helix problem?

Why not try and format the same file as me and see if it works: https://github.com/David-Else/zombie-attack-4/blob/main/src/index.ts

I just tried this repo (bun i, just in case), and it doesn't work either.
I leave you my configuration, in case you need to check it:
https://github.com/linuxmobile/kaku/blob/main/home/editors/helix/languages.nix
2024-01-13T13:24:32.494 helix_term::application [WARN] Received unregistration request for unsupported method: workspace/didChangeConfiguration
2024-01-13T13:24:32.495 helix_term::application [WARN] Received unregistration request for unsupported method: textDocument/rangeFormatting
2024-01-13T13:24:32.495 helix_term::application [WARN] Received unregistration request for unsupported method: textDocument/onTypeFormatting
2024-01-13T13:24:32.495 helix_term::application [WARN] Received unregistration request for unsupported method: textDocument/rename
2024-01-13T13:24:32.495 helix_term::application [WARN] Received unregistration request for unsupported method: textDocument/formatting
2024-01-13T13:24:32.495 helix_term::application [WARN] Ignoring a client/registerCapability request because dynamic capability registration is not enabled. Please report this upstream to the language server
2024-01-13T13:24:32.495 helix_term::application [WARN] Ignoring a client/registerCapability request because dynamic capability registration is not enabled. Please report this upstream to the language server
2024-01-13T13:24:32.495 helix_term::application [WARN] Ignoring a client/registerCapability request because dynamic capability registration is not enabled. Please report this upstream to the language server
2024-01-13T13:24:32.591 helix_term::application [ERROR] received malformed notification from Language Server: Unhandled
2024-01-13T13:24:41.810 helix_lsp::transport [ERROR] err: <- Other(failed to send a message to server

It doesn't work for me either.

I am experiencing the same issue. How can I help in isolating this?

@linuxmobile

I leave you my configuration, in case you need to check it:
https://github.com/linuxmobile/kaku/blob/main/home/editors/helix/languages.nix

I had a look, and it is wrong and not the config provided in this pull request. Am I misunderstanding something? Please try disabling your current languages.toml and just using the provided one. If that works you can then build back your custom one from that. You don't need to be adding any format arguments when calling the Biome executable, all the formatting is handled automatically inside the language server.
    formatter = {
            command = "biome";
            args = ["format" "--stdin-file-path" "a.js"]; <<<< Not needed!

I had a look, and it is wrong and not the config provided in this pull request

In fact, the configuration I had was exactly what you provide, but it didn't work for me. If you look at the commit I added that yesterday. And now it works perfectly for me. I have no idea if the example you offer is wrong or what. But this way it is working for me

Hi, same problem, linter works but formatting does not.
hx --version
helix 23.10 (f6021dd0)

biome --version
Version: 1.5.3

 language.toml
[language-server]
biome = { command = "biome", args = ["lsp-proxy"] } # language server definition like in doc

[[language]]
name = "rust"
auto-format = true

[[language]]
name = "go"
auto-format = true

[[language]]
name = "html"
formatter = { command = 'prettier', args = ["--parser", "html"] }

[[language]]
name = "css"
formatter = { command = 'prettier', args = ["--parser", "css"] }

[[language]]
name = "javascript"
language-servers = [ { name = "typescript-language-server", except-features = [ "format" ] }, "biome" ]
auto-format = true

[[language]]
name = "typescript"
language-servers = [ { name = "typescript-language-server", except-features = [ "format" ] }, "biome"] # like in doc
auto-format = true

[[language]]
name = "json"
language-servers = [ { name = "vscode-json-language-server", except-features = [ "format" ] }, "biome" ]
auto-format = true

 helix logs
2024-01-23T17:06:27.151 helix_term::application [WARN] Received unregistration request for unsupported method: workspace/didChangeConfiguration
2024-01-23T17:06:27.151 helix_term::application [WARN] Received unregistration request for unsupported method: textDocument/rangeFormatting
2024-01-23T17:06:27.151 helix_term::application [WARN] Received unregistration request for unsupported method: textDocument/onTypeFormatting
2024-01-23T17:06:27.151 helix_term::application [WARN] Received unregistration request for unsupported method: textDocument/rename
2024-01-23T17:06:27.151 helix_term::application [WARN] Received unregistration request for unsupported method: textDocument/formatting
2024-01-23T17:06:27.153 helix_term::application [WARN] Ignoring a client/registerCapability request because dynamic capability registration is not enabled. Please report this upstream to the language server
2024-01-23T17:06:27.153 helix_term::application [WARN] Ignoring a client/registerCapability request because dynamic capability registration is not enabled. Please report this upstream to the language server
2024-01-23T17:06:27.153 helix_term::application [WARN] Ignoring a client/registerCapability request because dynamic capability registration is not enabled.  It works for now however :)

I just took some biome logs using biome rage --daemon-logs and they are right here: https://gist.github.com/Awesomerly/9e4eb89ab9b97254eb67fa310376d6ba

I'm still having this issue even with the latest version.
hx --version
helix 23.10 (f5d95de2)

biome --version
Version: 1.6.1

I followed the documentation here: https://github.com/biomejs/biome/blob/main/editors/helix/manual.md
How did the author of the demo video got it to work?

How did the author of the demo video got it to work?

I had to add this for it to work for me.
https://github.com/linuxmobile/kaku/blob/6af541c3db25d1dbf5fe258108fcccecb83bb93f/home/editors/helix/languages.nix#L60


Fixed spelling error of the word "previous" in the command palette.

Oh! It seems that my left hand could not wait for my right hand. Thanks!


Build uses esnext features

Hi, could you build this in a way that doesn't require special loaders to import the package? I'm getting an error like this:
ERROR in ./node_modules/dessert-box/dist/index.js 50:59
Module parse failed: Unexpected token (50:59)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
|     return /* @__PURE__ */ import_react.default.createElement(Element, {
|       ...otherProps,
>       className: hasAtomProps || className ? `${className ?? ""}${hasAtomProps && className ? " " : ""}${hasAtomProps ? atomsFn(atomProps) : ""}` : void 0
|     });
|   }

Seems to be due to the nullish coalescing operator in that line. Would be good to transpile that in the build. Imported modules should not need any extra handling.
Or am I doing something wrong?

Nope, you're totally correct 👍 thanks!


How to input complicated constraints in Bayesian Optimization that is not just lower and upper bound using Python?

Hi, I'm wondering is the package only capable of dealing with the simple lower and upper bound constraint? What if I have more complicated constraint (it is to do with calling another self-defined function), how do I input constraints like that?
Thanks!

Would anyone be interested if we tried to add additional sampling distributions other than a uniform?

It would be really great if self defined functions could be applied as constraints. I have been doing some reserach on Bayesian optimization packages but non of the packages that are still maintained offers such functionality.
Only spearmint(https://github.com/HIPS/Spearmint) is able to do so but still utlizes python 2.7 and can only be called via command line input.
Gpoptflow(https://gpflowopt.readthedocs.io/en/latest/notebooks/constrained_bo.html) implemented equality constraints but no inequality constraints. Also it dosent seem that there is any current development on the repository either.

@julian-belina Ax (unaffiliated) supports a variety of constraints out of the box. BoTorch (backbone of Ax, I'm also unaffiliated) supports equality, inequality, and nonlinear constraints (the last one has the caveat of requiring gradients, which can get tricky). Ax is on its way to getting the plumbing in order to support nonlinear constraints soon (again, you have to supply gradients).

Differentiable, nonlinear inequality constraints are now supported in Ax, though it can take some care to get these implemented since it requires applying some BoTorch transforms manually. See https://github.com/facebook/Ax/issues/769


Disable implicit offline caching

Prerequisite for: https://github.com/nhsuk/record-childrens-vaccinations/pull/198
Depends on https://github.com/nhsuk/record-childrens-vaccinations/pull/200 (roughly... it might be mergeable without, but because this piles on additional requests in the addAll, the test just becomes even flakier without it).
The key bit in this PR is removing the await put(request, networkResponse.clone()); call in the NetworkFirst strategy.
By doing this, pages are no longer cached implicitly, but instead have to be cached explicitly, via the "Save offline" button. The button is also updated to cache the JS and CSS alongside some other pages.
There's also a random "annotate" commit thrown in, I didn't want to split it off as its own PR, but it's harmless.
Disabling implicit offline caching is a necessary prerequisite to switching to using a user-provided password as the encryption key for the offline cache. We can't cache things before the user gives us that key.

#200 closed. Was that the wrong PR or is it irrelevant?

Yes, it's irrelevant in the end. The tests seem to pass without that and it should be replaced soon...


response not cached in case of 404

If service call returns response with http code 404 then response is not cached.
import requests
import requests_cache
requests_cache.install_cache()
requests_cache.clear()

r = requests.get('http://httpbin.org/ge')
r.from_cache

This returns False as expected but if i execute this again then
r = requests.get('http://httpbin.org/ge')
r.from_cache

This also returns False

hmm found 'allowable_codes=(200,404)' from implemenation


<IP_ADDRESS> delete schedule

Delete jobs and schedules by logic.

Coverage remained the same at 91.667% when pulling 1a6b0b934ee288b5145da33386fd11ad08537196 on <IP_ADDRESS>-DeleteSchedule into 51cf7ced98ae4d1063f692a817150749a53b3c7e on 0.1.1.


InfiniDex Alpha R1 - Market Overview Fields should not be editable

the symbols (e.g.  BTC-ETH) can be edited. If I edit them and click on them, the program crashes

fixed in release 3


The label of animatePlaceholder is not displayed when the initialValue is different from null

The label of animatePlaceholder is not displayed when the initialValue is different from null.

What version of MAFormViewController are you using?

Do not worry, this has been corrected!


create legacyIdPrefix parameter for maps and UUIDs

Merging multiple systems can involve overlapping identifier values and issues combining map files requiring preprocessing and awkward procedures
Propose legacyIdPrefix parameter for main config (ideally overwritable at the file level) that would be prepended to legacyId before generating UUID and hrid. The prefix should affect only the map, UUID, and hrid so remapping the value itself is unnecessary. This functionality is needed most for instance and holdings maps but may have other applications such as orders or anything that creates deterministic uuids.
Example:
legacyIdPrefix = myprefix
legacyBibId = b1234567
instance map = ["myprefixb1234567", "40785bac-f500-49f0-8aba-2bb19c04eeed", "inmyprefix0000000001"]

@banerjek Why would the prefix be in the hrid value?

That was a goof. It wouldn't be involved in hrid at all, only for creating deterministic uuid

I just remembered why -- I keep getting libraries that want to set hrid because of external integrations

@banerjek Does this solve that need, though? Wouldn't the prefix break them, as well?

There are two separate but connected issues here. One is if you're migrating from multiple systems with overlapping identifiers -- you have to prefix them to avoid collisions.
For the external integrations, they have to point to a new endpoint anyway -- but they have the numbers from the previous system stored (sometimes these are scattered across many systems). The prefix can be thought of as part of the endpoint

@banerjek Ok. That was what I thought. I guess I just wasn't clear on how they were going to subsequently use the HRID values if a prefix was applied. Are they able to distinguish the initial relationship by integration?

@banerjek Maybe we should have a call to discuss.


[BrokenLinksH2] Fixed the link path

Fixed the link path

Docs Build status updates of commit 0b6171d:
:warning: Validation status: warnings

File
Status
Preview URL
Details

Articles/FAQ.md
:warning:Warning

Details

Articles/FAQ.md

Line 1, Column 1: [Warning: title-missing - See documentation] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 119, Column 1: [Warning: sensitive-language-wl - See documentation] Term 'whitelisting' is sensitive and should not be used in content or code. Usage: 'You can load external content in your action by whitelisting the URL which contains the data. You can find steps for URL whitelisting [here](Actions/UrlWhitelis'
Line 119, Column 1: [Warning: sensitive-language-wl - See documentation] Term 'whitelisting' is sensitive and should not be used in content or code. Usage: ' content in your action by whitelisting the URL which contains the data. You can find steps for URL whitelisting [here](Actions/UrlWhitelisting.md).'
Line 1, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Global effort to fix broken links
@dstrome
The Content & Learning team is fixing broken links on docs.microsoft.com for the rest of H2. This effort will eliminate potential accessibility, security, and usability issues. This PR includes only link fixes and does not change other content. Please review within five business days and merge, or comment in the PR with any changes you'd like to see. Thanks!


Update index.html

Vaporean has already been added to the website, please add some other pokemon, thank you.


fix: do deepcopy before add finalizer

What type of PR is this?
add finalizer may be accidentally skipped
What this PR does / why we need it:
ensure
Which issue(s) this PR fixes:
Fixes #643
Special notes for your reviewer:
@dixudx

Codecov Report

Merging #644 (684572f) into main (e2ffa5f) will decrease coverage by 0.35%.
The diff coverage is n/a.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff             @@
##             main     #644      +/-   ##
==========================================
- Coverage   13.60%   13.25%   -0.35%
==========================================
  Files          66       71       +5
  Lines        7492     7806     +314
==========================================
+ Hits         1019     1035      +16
- Misses       6391     6687     +296
- Partials       82       84       +2

see 18 files with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Small grammar fix

I've noticed that "has" is used instead of "have" with plural "API resources".
Additionally, "which has status or scale subresource" is restrictive / defining clause, so "that" should be used instead of "which".
Links:

https://www.dictionary.com/e/that-vs-which/
https://www.grammarly.com/blog/which-vs-that/

/lgtm
/approve


add awesome to example

:star: PR built and available in a preview environment ripcitysoftware-spring-boot-http-gradle-pr-1 here

:star: PR built and available in a preview environment ripcitysoftware-spring-boot-http-gradle-pr-1 here


Add defaultForms feature for common types

Might be best to not save those props but use from web part?
Or have the choice to force certain settings vs saving to property pane

Would need to have something like PreConfigProps style forced and presets over-ride

Added framework for PreConfigProps, onPropPaneChanged etc... for MineCraft.
Just need to add individual ones as they come up


Alex b/employee history

Please check our work

Closing this one. Please try to be careful on which branch you are issuing a pull request.


Added cordova-diagnostic-plugin tool to readme.md

No, I mean actually implement the checking in this plugin.  It's not much code.

Oh, well I've never wrote any C# before, so I'm not sure how quick I'd be able to pick up on it. But I'll try.

It's not C#, it's Obj-c.


fix(node-wasm): require serving and providing worker script

I believe we can do better in future but for now it's the only way we got it to work with bundlers like webpack :see_no_evil:


[dlive] Add more useful error message

Please follow the guide below

You will be asked some questions, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your pull request (like that [x])
Use Preview tab to see how your pull request will actually look like

Before submitting a pull request make sure you have:

[x] At least skimmed through adding new extractor tutorial and youtube-dl coding conventions sections
[x] Searched the bugtracker for similar pull requests
[x] Checked the code with flake8

In order to be accepted and merged into youtube-dl each piece of code must be in public domain or released under Unlicense. Check one of the following options:

[x] I am the original author of this code and I am willing to release it under Unlicense
[ ] I am not the original author of this code but it is in public domain or released under Unlicense (provide reliable evidence)

What is the purpose of your pull request?

[ ] Bug fix
[x] Improvement
[ ] New extractor
[x] New feature

Description of your pull request and other information
Fix #22257
Now youtube-dl raises an ExtractorError with a more useful error message when it encounters an offline stream on dlive.

Read coding conventions.


Initial commmit of draft for 1.3 release blog, needs review and revisions

Also missing some quotes, but enough for a round of reviews.

The content introduction needs a redo, so Josh is going to do that in a gdoc intead of a PR, I'll reconvert it and re-PR it, closing this now!


Upgrade CAS overlays to 4.2

Upgrade both the cas overlay and the management overlay to 4.2 RC1, in prep for the release so that adopters have a chance to try out and test the new functionality.
Discussed with Dima. Handing over.

Brainstorming... perhaps master should be 4.2, with the 4.1 on the branch

I agree.

OK, upgraded both cas and management web app to 4.2.0-RC1 and pushed both to 4.2 branch. CAS server is just fine while management web app blows up with all sorts of nasty oauth and pacj4 things. Not usable locally at the moment. I'm giving up on the management web app for now... This is the branch: https://github.com/Jasig/cas-services-management-overlay/tree/4.2 .. if someone could make it work, that'd be great.
Cheers,
D.

Very disappointing as I thoroughfully tested the management webapp while replacing Spring Security by pac4j. I will check with the RC1.

I think it has something to do with Jackson and classloading when it tries to de-serialize the Oauth reg service back from JSON file which it created during bootstrap by this -> https://github.com/Jasig/cas/blob/v4.2.0-RC1/cas-server-support-oauth/src/main/java/org/jasig/cas/support/oauth/OAuthServletContextListener.java#L42

OK, we identified the problem. Happens when both CAS and managment app is deployed into the same servlet container. The web app is tightly coupled to the oauth module and creates the oauth registered service, but since they both share the same JSON service registry CAS server throws up when it tries to de-serialize that oauth service magically (by servlet listener) created by management web app.
Long story shor - we need to de-couple oauth module from management web app module. @mmoayyed will try to take care of that for 4.3 and if not drastic enough we could backport it to the upcoming 4.2 GA

Linked issue #1466

I am having a problem getting this to deploy to an external jetty setup.  The error in the logs is this
2016-01-21 18:16:20,975 WARN [org.springframework.web.context.support.XmlWebApplicationContext] - <Exception encountered during context initialization - cancelling refresh attempt
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter': Invocation of init method failed; nested exception is java.lang.NoSuchMethodError: org.springframework.web.accept.ContentNegotiationManager.getStrategies()Ljava/util/List;
This problem does not pop up until I add the LDAP authentication dependency.  Looking at the core pom and the ldap poms, I see that core is built with the latest Spring 4.2.3.  LDAP includes a dependency of spring-webflow with the latest tag of 2.4.2.  The issue is that weblfow-2.4.2 resolves to Spring verison 4.2.0.  This results in the cas.war being built with jars form both versions, and when it deploys we get the error above.
Does this mean core can not be moved past 4.2.0 until spring-webflow is updated?
Sorry if this is not the correct place to ask this
Travis

No it's the right place. We'll likely need to exclude the older spring dependency from webflow. Can you provide a dependency tree for us and paste it here?

Here are the dependencies in the pom I am using:
<dependencies>
    <dependency>
        <groupId>org.jasig.cas</groupId>
        <artifactId>cas-server-webapp</artifactId>
        <version>${cas.version}</version>
        <type>war</type>
        <scope>runtime</scope>
    </dependency>
    <dependency>
      <groupId>org.jasig.cas</groupId>
      <artifactId>cas-server-support-ldap</artifactId>
      <version>${cas.version}</version>
      </dependency>
</dependencies>

Is this what you needed?

So, then do a mvn dependency:tree and paste the output please.

[INFO] [dependency:tree {execution: default-cli}]
[INFO] org.jasig.cas:cas-overlay:war:1.0
[INFO] +- org.jasig.cas:cas-server-webapp:war:4.2.0-RC1:runtime
[INFO] - org.jasig.cas:cas-server-support-ldap:jar:4.2.0-RC1:compile
[INFO]    +- org.springframework.webflow:spring-webflow:jar:2.4.2.RELEASE:compile
[INFO]    |  +- commons-logging:commons-logging:jar:1.1.1:compile
[INFO]    |  +- opensymphony:ognl:jar:2.6.11:compile
[INFO]    |  +- org.springframework.webflow:spring-binding:jar:2.4.2.RELEASE:compile
[INFO]    |  +- org.springframework.webflow:spring-js:jar:2.4.2.RELEASE:compile
[INFO]    |  |  - org.springframework.webflow:spring-js-resources:jar:2.4.2.RELEASE:compile
[INFO]    |  +- org.springframework:spring-context:jar:4.2.0.RELEASE:compile
[INFO]    |  |  - org.springframework:spring-aop:jar:4.2.0.RELEASE:compile
[INFO]    |  +- org.springframework:spring-core:jar:4.2.0.RELEASE:compile
[INFO]    |  +- org.springframework:spring-web:jar:4.2.0.RELEASE:compile
[INFO]    |  - org.springframework:spring-webmvc:jar:4.2.0.RELEASE:compile
[INFO]    +- org.apache.logging.log4j:log4j-jcl:jar:2.5:runtime
[INFO]    +- org.jasig.inspektr:inspektr-aspects:jar:1.3.GA:compile
[INFO]    +- com.fasterxml.jackson.core:jackson-databind:jar:2.6.1:compile
[INFO]    |  +- com.fasterxml.jackson.core:jackson-annotations:jar:2.6.0:compile
[INFO]    |  - com.fasterxml.jackson.core:jackson-core:jar:2.6.1:compile
[INFO]    +- org.aspectj:aspectjweaver:jar:1.8.6:compile
[INFO]    +- org.apache.logging.log4j:log4j-core:jar:2.5:runtime
[INFO]    +- org.apache.logging.log4j:log4j-api:jar:2.5:runtime
[INFO]    +- org.jasig.cas:cas-server-core-authentication:jar:4.2.0-RC1:compile
[INFO]    |  +- org.jasig.cas:cas-server-core-api-ticket:jar:4.2.0-RC1:compile
[INFO]    |  +- org.jasig.inspektr:inspektr-audit:jar:1.3.GA:compile
[INFO]    |  |  - org.jasig.inspektr:inspektr-common:jar:1.3.GA:compile
[INFO]    |  +- org.jasig.service.persondir:person-directory-impl:jar:1.7.0:compile
[INFO]    |  |  +- aopalliance:aopalliance:jar:1.0:compile
[INFO]    |  |  +- com.sun.xml.bind:jaxb-impl:jar:2.2.7:compile
[INFO]    |  |  |  +- com.sun.xml.bind:jaxb-core:jar:2.2.7:compile
[INFO]    |  |  |  |  +- javax.xml.bind:jaxb-api:jar:2.2.7:compile
[INFO]    |  |  |  |  - com.sun.istack:istack-commons-runtime:jar:2.16:compile
[INFO]    |  |  |  - com.sun.xml.fastinfoset:FastInfoset:jar:1.2.12:compile
[INFO]    |  |  |     - javax.xml.bind:jsr173_api:jar:1.0:compile
[INFO]    |  |  +- org.apache.commons:commons-collections4:jar:4.0:compile
[INFO]    |  |  +- org.jasig.service.persondir:person-directory-api:jar:1.7.0:compile
[INFO]    |  |  - org.springframework:spring-tx:jar:4.1.6.RELEASE:compile
[INFO]    |  +- org.jasig.cas:cas-server-core-api-services:jar:4.2.0-RC1:compile
[INFO]    |  - io.dropwizard.metrics:metrics-annotation:jar:3.1.2:compile
[INFO]    +- org.ldaptive:ldaptive:jar:1.1.0:compile
[INFO]    |  - commons-cli:commons-cli:jar:1.3.1:compile
[INFO]    +- org.ldaptive:ldaptive-beans:jar:1.1.0:compile
[INFO]    +- org.springframework:spring-expression:jar:4.2.3.RELEASE:compile
[INFO]    +- org.pac4j:pac4j-core:jar:1.8.2:compile
[INFO]    +- org.glassfish.web:javax.el:jar:2.2.6:runtime
[INFO]    |  - javax.el:javax.el-api:jar:2.2.5:runtime
[INFO]    +- org.reflections:reflections:jar:0.9.10:compile
[INFO]    |  +- com.google.guava:guava:jar:15.0:compile
[INFO]    |  +- org.javassist:javassist:jar:3.19.0-GA:compile
[INFO]    |  - com.google.code.findbugs:annotations:jar:2.0.1:compile
[INFO]    +- org.hibernate:hibernate-validator:jar:5.2.2.Final:runtime
[INFO]    |  +- org.jboss.logging:jboss-logging:jar:3.2.1.Final:runtime
[INFO]    |  - com.fasterxml:classmate:jar:1.1.0:runtime
[INFO]    +- joda-time:joda-time:jar:2.9:compile
[INFO]    +- org.apache.logging.log4j:log4j-slf4j-impl:jar:2.5:runtime
[INFO]    +- org.jasig.cas:cas-server-core-util:jar:4.2.0-RC1:compile
[INFO]    |  +- org.springframework:spring-context-support:jar:4.2.3.RELEASE:compile
[INFO]    |  +- org.bitbucket.b_c:jose4j:jar:0.4.4:compile
[INFO]    |  +- commons-io:commons-io:jar:2.4:compile
[INFO]    |  +- org.jasig.cas:cas-server-core-api-util:jar:4.2.0-RC1:compile
[INFO]    |  +- commons-codec:commons-codec:jar:1.10:compile
[INFO]    |  +- org.jasig.cas:cas-server-core-api-authentication:jar:4.2.0-RC1:compile
[INFO]    |  |  - org.jasig.cas:cas-server-core-api-protocol:jar:4.2.0-RC1:compile
[INFO]    |  +- org.apache.commons:commons-lang3:jar:3.4:compile
[INFO]    |  +- org.apache.shiro:shiro-core:jar:1.2.4:compile
[INFO]    |  |  - commons-beanutils:commons-beanutils:jar:1.8.3:compile
[INFO]    |  +- org.apache.httpcomponents:httpclient:jar:4.5.1:compile
[INFO]    |  |  - org.apache.httpcomponents:httpcore:jar:4.4.3:compile
[INFO]    |  - org.quartz-scheduler:quartz:jar:2.2.1:compile
[INFO]    |     - c3p0:c3p0:jar:<IP_ADDRESS>:compile
[INFO]    +- org.springframework:spring-beans:jar:4.2.3.RELEASE:compile
[INFO]    +- org.aspectj:aspectjrt:jar:1.8.6:compile
[INFO]    +- org.slf4j:jul-to-slf4j:jar:1.7.12:runtime
[INFO]    +- org.slf4j:slf4j-api:jar:1.7.12:compile
[INFO]    - javax.validation:validation-api:jar:1.1.0.Final:compile
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL
[INFO] ------------------------------------------------------------------------

@dima767 You should be able to resume the upgrade by the way.

Well, it's done... Only on the branch, until GA comes out ;-)

And with the new mgmt app property placeholder config location externalized, we don't even need an overlay for it ;-)

So found a problem with the cas webapp of the 4.2. You are excluding log4j2 from the overlay, yet you don't configure it in cas.properties. Is that true on your end, or have I missed something?

We do need an overlay to show it can be built. We may not need any fancy config for it. That's what you meant right?

Well, both overlays are ready on the 4.2 branch. On the cas side wrt log4j config location I do have it in my local, externalized cas.properties

They both checkout per my testing. The only thing you likely need is
log4j.config.location=file:///etc/cas/log4j2.xml

in your etc/cas.properties file.

Sure, will add that momentarily

Excellent. I'll look into this dependency issue here, but we are good to go for the most part.

Done with log4j config location prop

Copy that.

@tsschmi I am not seeing this. You issue must stem from something else in the config.

For clarity, I did try with Jetty 9.3.6.v20151106 and Tomcat 8. no errors.

But I do see spring 4.2.0 creeping its way into the config. Just saying Jetty seems to have no issues with it, but that is an issue we should fix.

I am able to reproduce the error this way:

git clone https://github.com/Jasig/cas-overlay-template.git
cd cas-overlay-template
git checkout remotes/origin/4.2
edit pom.xml -
add dependency -

org.jasig.cas
cas-server-support-ldap
${cas.version}

mvn clean package
mvn jetty:run-war

This will cause the error I reported earlier for me.  I had a colleague try this on his machine and it ran without the issue.  The only difference we can find is I am running Ubuntu 15.10 and he has Red Hat.  If I do mvn jetty:run or mvn jetty:run-forked, the server comes up without the error.

Confirmed this morning that adding exclusions in the pom.xml for the spring 4.2.0 artifacts from the ldap dependency allows the war to be deployed now.  It is a complete mystery to me as to why not everyone has this class loading issue.

Classloaders work in mysterious ways. I am working on making sure all dangling transitive dependencies are excluded correctly. This will be fixed before the final GA.

Closing this as the work is done really for this issue. Thanks @dima767


Registration

@JuliaRegistrator register

@JuliaRegistrator register

Registration pull request created: JuliaRegistries/General/83931
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v1.0.0 -m "<description of version>" 31745305e379372faa5679a4ccc9161875285de2
git push origin v1.0.0

Registration pull request updated: JuliaRegistries/General/83931
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v1.0.0 -m "<description of version>" 31745305e379372faa5679a4ccc9161875285de2
git push origin v1.0.0

@JuliaRegistrator register

Registration pull request updated: JuliaRegistries/General/83931
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v1.0.0 -m "<description of version>" eed76a7d7fafeac5179fdf8cbe3e03329451ac9d
git push origin v1.0.0

@JuliaRegistrator register

Registration pull request created: JuliaRegistries/General/84091
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v1.0.1 -m "<description of version>" da58f71d42934b8e800eb133f46d11748fa79eec
git push origin v1.0.1

@JuliaRegistrator register

Registration pull request created: JuliaRegistries/General/84122
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v1.0.2 -m "<description of version>" 754513d8e1122afaf6e1c0196e7cd270eb5e9638
git push origin v1.0.2

@JuliaRegistrator register

Registration pull request created: JuliaRegistries/General/84578
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v1.1.0 -m "<description of version>" badc110ac565b2ce7ee2e61d8d4944e30b156378
git push origin v1.1.0


test more permutations

Fixes #4484

@valdrinkoshi @sorvell Still want to make progress on this?

@valdrinkoshi Would you mind updating the failing Polymer tests? If they are green, I think we can take this.

@sorvell tests fixed by moving the remove, append domif test to be executed after the clients persist/clients recreated ones, and taking into account the increment of uid at that spot. PTAL


Use .gitattributes to shrink the archive file produced by git archive

The AWS deployment scripts can send a local Git branch (of BigchainDB) to all remote servers. They do that by using the git archive command to archive the specified branch into a tar file. The git archive command ignores the files in .gitignore but there are many other files that don't need to be sent to the remote servers, e.g. all the documentation.
A .gitattributes file can be used to specify additonal files and directories to exclude when producing an archive. Some help:

https://feeding.cloud.geek.nz/posts/excluding-files-from-git-archive/
http://stackoverflow.com/questions/21832151/git-archive-export-ignore-ignoring-directories
https://git-scm.com/docs/gitattributes

:+1:


Remove ipu

Changelogs

Removing support for IPU
Removing custom to_dense_batch and to_sparse_batch specific to IPUs, and reverted to the pyg version
Removing all documentation regarding IPUs

discussion related to that PR

@DomInvivo, I have no concerns with the changes. The unit tests might need an overhaul though.
I resolved conflicts in order to run the env checks and they are failing (I believe due to issues with the installation of graphium_cpp).


Add IES El Rincon

Vocational School that gives several IT related stuff located in the Canary Islands
Their Websites:
http://www3.gobiernodecanarias.org/medusa/edublog/ieselrincon/           ( Oficial Government website )
http://www.ieselrincon.org/                                                                           ( Their Website )
They give the students emails in this format {name}<EMAIL_ADDRESS>

@Meganitrospeed Pull request merged. Thank you!


Create Nuget package

Would be good to have this as a nuget package that could be consumed in .Net projects

https://www.nuget.org/packages/DustyGhost.NGenerator/


chore: Added a tiny typo fix

Closes https://github.com/adobe/react-spectrum/issues/1965
✅ Pull Request Checklist:

[x] Included link to corresponding React Spectrum GitHub Issue.
[x] Added/updated unit tests and storybook for this change (for new code or code which already has tests).
[x] Filled out test instructions.
[x] Updated documentation (if it already exists for this component).
[x] Looked at the Accessibility Practices for this feature - Aria Practices

📝 Test Instructions:
No tests required

Thanks for spotting this @Robbie-Cook! Can you sign the CLA so we can merge? You might need to close and open the pr again to trigger it.

Thanks for spotting this @Robbie-Cook! Can you sign the CLA so we can merge? You might need to close and open the pr again to trigger it.

No worries, signed CLA, and am closing and re-opening. Thanks!


Download VS Code Insiders quick pick should be low priority

IMHO it's very unlikely that users install VS Code through the remote picker, so we probably want to move it down to the bottom.

It's still not at the bottom of the list, but has moved to be below the codespace option, so considering this verified.

Yeah that's the intended behavior, we still suffix the list with Install Additional Remote Extensions so that entry should always be last if it is shown.


Invalid certs on website

Hosted version of this has invalid certs.

Thanks @lumberj.  Looks like our letsencrypt auto renewal didn't work.  Updated this and re-deployed the hosted version.  Cert looks valid now.


Allow LeagueClient to be initlaized without credentials?

Since LeagueClient is being used to detect start/stop of LeagueClient, is there a reason we would not want to be able to initialize LeagueClient without credentials and allow onTick to generate an initial on connect event with credentials?

This seems like a reasonable request. Now that I think about it, I don't think there's anything that should prevent us from doing so. Would be happy to accept a patch for that.

I've implemented this under the next major version in #71
If you wish to try the new features before 6.0.0 is released, you can download 6.0.0-rc1 from npm


tsdb: update chunks format

https://github.com/prometheus/prometheus/blob/8744afdd1ea068bb6026a527983467952c7dbf5d/tsdb/chunks/chunks.go#L181-L190
there are 3 bytes padding after the format version.

Maybe you should rebase the code to pass CI :)

Thanks I noticed this padding too.


Expose platform.winglob to Intl.js to detect which i18n lib we are using in the native code.

@jackhorton,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

@jackhorton Looks like that EOL diff we saw is because your EOL settings are off. ChakraCore should have
ChakraCore>git config core.autocrlf
true

Its interesting, it looks like the latest gvfs update killed all of my settings, not just autocrlf.  I have fixed it now.

@jackhorton To improve our inner-loop speed (mainly reduce infra overhead), I'm going to create branch intlicu off release/1.7 and retarget this PR there. This shouldn't affect our workflow except that PRs should target that new branch instead. We will merge back to release/1.7 when the work is complete.

@dotnet-bot test this please

@dotnet-bot test this please

@dotnet-bot test this please

@jackhorton,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

@jackhorton You're good to merge!


Run from Ram

Is your feature request related to a problem? Please describe.
It would be great if probe-rs run supported directly loading an image into sram (or as much of it as possible) for fast testing and debugging. Flashing QSPI flash can be painfully slow, these parts often have plenty of ram to run the entire image out of them. It would be great to have very fast turn around times on running things.
Describe the solution you'd like
probe-rs given an image that loads into ram succeeds, and maybe better yet understands its doing something a bit special
Additional context
Building an image for sram only for imxrt1010 and trying to run it gets me...
probe-rs run --probe 0d28:0204 --chip MIMXRT1010 target/thumbv7em-none-eabihf/debug/examples/hal_clock_out
Error: Error while flashing

Caused by:
    No flash memory contains the entire requested memory range 0x20002000..0x20002400

Instead I wish it would simply load the image
pyocd does seem to at least load it successfully, though likely it gets vanquished on a reset.
pyocd load --format elf target/thumbv7em-none-eabihf/debug/examples/hal_clock_out
0000780 I Loading /home/spinfast/src/imxrt-hal/target/thumbv7em-none-eabihf/debug/examples/hal_clock_out [load_cmd]
[==================================================] 100%
0002659 I Erased 0 bytes (0 sectors), programmed 41228 bytes (0 pages), skipped 0 bytes (0 pages) at 21.56 kB/s [loader]

So I suppose in this case what I'd love to see is maybe a special mode that loads to ram by doing the equivalent of gdb's
monitor reset halt
load
c

This does work using pyocd's gdb server

That target does not contain the DTCM memory range that you expect as correctly told by the error message.
We can definitely improve the message to not mention flash and maybe print available ranges.
https://probe.rs/targets/master/MIMXRT1010 shows that there is only one RAM memory range.
file:///Users/yatekii/Downloads/IMXRT1010RM.pdf says there is more.
You could try and regenerate the target with https://github.com/probe-rs/probe-rs/tree/master/target-gen. Maybe there is a newer CMSIS-Pack that fixes the issue. Otherwise you can add it manually. Everything needs to land in this file at the end: https://github.com/probe-rs/probe-rs/blob/master/probe-rs/targets/MIMXRT1010.yaml


Fixed the .vscode not being ignored

Pull Request
Thank you for contributing to @toptal/gitignore and https://www.gitignore.io.
New or update
Select the appropriate check box for this pull request. This helps when merging to ensure there are no conflicts with other templates or misunderstandings of how thee template list works.
New

[ ] Template - New .gitignore template
[ ] Composition - Template made from smaller templates
[ ] Inheritance - Template similar to an existing template
[ ] Patch - Template extending functionality of existing template

Update

[x] Template - Update existing .gitignore template

Details
Files in the .vscode directory would still be added with the previous syntax.

Thank you contributing to gitignore.io, @tropicalraisel, but in this case, you have to submit this change to the original github/gitignore repository.