Insert & Update Return Model

PR Info

Resolve #289

Breaking Changes

insert, update and save return Model instead of ActiveModel
ActiveModelBehavior::after_save takes <Self::Entity as EntityTrait>::Model instead of ActiveModel

Still drafting?

I planned to merge those for 0.4.1

#348
#347

Then, moving on to merge PRs for 0.5.0

#340
#339 (this PR)

(PR mentioned in tentative merge sequence)

Please open a new PR to address the above suggestions.


initial airr-js package

[ ] finish I/O routines
[x] add tests
[x] API documentation?
[ ] npm account, publish, update release procedures
[ ] consolidate test/data into common area

@schristley , we're wrapping up for a release right now. Is this something that will be ready to go or should we push it to v2.0?

@javh Note that schema fixes like #697 are needed for validation to work.

Ah, okay. So close, but maybe not quite there yet. Hrm. Maybe v2 then? Even though it is close.

@schristley Is this close to complete?

@schristley Is this close to complete?

It is. I'll work on the last bits this month and get it merged.


Using CLI tool does not pick up SchemaFilters

Using version 5.0.0-rc5.
When I am using dotnet swagger tofile command line tool, it doesn't seem to pick up on any schema filters that I have applied to the SwaggerGenOptions.

This works for me. Please create a minimum application that repro's your issue and post to github so I can pull it down and investigate.

Closing due to inactivity

Closing due to inactivity


fixed width of search bar and removed bottom margins

I fixed the width of search bar for mobiles devices and then removed the extra unwanted bottom margins.

Can you please share a screenshot of search page


Using fine-tuned model with deep_river

Is it possible to use fine-tuned model with PyTorch and deep_river?

Hi @alpcansoydas
yes you should be able to use fine tuned models. Just load them before you pass them to the river wrapper :-).
Best
Cedric


cmake: added option to not build tests

In case libuv is included via add_subdirectory, its tests are always
built and executed. This cannot be skipped currently, because switching
BUILD_TESTING to false would also switch off all other tests in the
parent project.
This commit adds a switch "libuv_buildtests" which can individually
switch of the compilation and execution of libuv's tests. It is ON by
default, so the default behavior does not change. However, projects
that include libuv via add_subdirectory can not set libuv_buildtests to
OFF if they are not interested in its tests.

That is fine with me.

CI: https://ci.nodejs.org/view/libuv/job/libuv-test-commit/1388/

Rerun of the CI: https://ci.nodejs.org/view/libuv/job/libuv-test-commit/1389/
@nlohmann it seems like the windows cmake failures are legit.

This PR is still pending. Anything I can do to help?

@nlohmann could you just rebase your branch on the latest v1.x and push it to this PR.

@cjihrig I honestly never did a rebase before... I tried to follow https://github.com/edx/edx-platform/wiki/How-to-Rebase-a-Pull-Request - let me know if I messed anything up.

Thanks @nlohmann. I reran the CI (https://ci.nodejs.org/view/libuv/job/libuv-test-commit/1432/) and there was some red, but I don't believe any of it is related to this change.

I had a brief look at the build logs, and I agree that this should not be from the CMake flag I introduced.

Landed in https://github.com/libuv/libuv/commit/f8cab71872fcbc4b96e4998a896f9fa8a60989e8. Thanks!


Upgrade NET Core RC1 to NET Core 1.1

Fix with this pull request: https://github.com/Zywave/OctopusDeploy-Kraken/pull/64


Cleanup logging in etc3

etc3 currently seems to be using at least four types of log providers -- zap logging in main.go, go-logr (as seen from the go.mod file), "sigs.k8s.io/controller-runtime/pkg/log" in experiment_test.go, and util.Logger (because, this is where we want to control everything related to logging -- centrally).
I didn't look carefully, it is possible I missed other log providers here.
etc3 codebase needs to be cleaned up so that there is a single way to setup logging (in util) and use it everywhere, including controller setup, reconcile loop, and tests.

setLogger function can be invoked once in util's init() function.
getLogger function can be provided by util and used in every other part of etc3.

I have reviewed the code and see only references to 2 logging libraries.  The main.go and the suite_test.go files use ("sigs.k8s.io/controller-runtime/pkg/log/zap") zap.New() to create a ("github.com/go-logr/logr") logr.Logger.  Everywhere else uses github.com/go-logr/logr.
zap is used only to create and configure a new Logger. It is introduced as the method of preference by the kubebuilder code generation. I see no reason to replace it.  The logr.Logger that is created is a property of the controllers.ExperimentReconciler created in main.go and is used everywhere else. It is passed to all methods via a context (util.go provides a method to extract it from the context).
I'm closing this as nothing to do.

Looks like "sigs.k8s.io/controller-runtime/pkg/log" is now gone. Which is good.
However, using two different loggers in the same project is one logger too many. Reopening the issue. I can handle it as part of #908

The controller requires us to set a logger; it tasks a logr.Logger as in input for this. logr.Logger is an interface. An implementation is provided by zap. One needs only use it to set the logger; thereafter one uses the interface methods. We are not using 2 different loggers at different times with different formats. We are using one.
It appears that you prefer logrus. Unfortunately, it is not suitable for the controller; it does not provide an implementation of logr.Logger.
I still believe this should be closed.

Thanks for that explanation.
I see "sigs.k8s.io/controller-runtime/pkg/log/zap" imported in main.go.
I also see github.com/go-logr/logr v0.3.0 imported in go.mod.
Aren't these different logger implementations?
You are setting the logger in the manager as zap (which makes sense). So why is the second implementation showing up in go.mod?

This issue is not related to logrus.

I also see github.com/go-logr/logr defines the interface logr.Logger.  The methods of this interface are used to do the actual logging everywhere in the controller.  zap  is only used in main.go to create an instance of a logger that satisfies the definition of the interface logr.Logger (the interface type).

Thanks @kalantar again for this explanation.
I understand now. I agree there is no issue here. Closing.


Licensing

It should be updated that the "trusted ips" section is not available unless you have Azure AD P1.  This prevents all of the business standard tenants from even using this.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 84b26750-880c-8f14-1628-436293de915e
Version Independent ID: 518b727f-79e8-b5c2-bcb3-ff4de3444c6f
Content: Configure Azure AD Multi-Factor Authentication - Azure Active Directory
Content Source: articles/active-directory/authentication/howto-mfa-mfasettings.md
Service: active-directory
Sub-service: authentication
GitHub Login: @Justinha
Microsoft Alias: justinha

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

@danmyhre
Thanks for your feedback! I have assigned this issue to the author who will investigate and update as appropriate.

@danmyhre thanks for the suggestion and sorry for delay. This has been added.

#please-close


feat(autoware_pointcloud_preprocessor): expansion for single lidar system

Description
In this PR, I added the callback function to pointcloud_preprocessor for single lidar system.
https://github.com/orgs/autowarefoundation/discussions/4700
Related links
Tests performed
I have checked that the /sensing/lidar/concatenated/pointcloud topic is published even if the number of input_topic is 1 on the LSIM.
Notes for reviewers
Interface changes
None
ROS Topic Changes

ROS Parameter Changes

Effects on system behavior

Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[x] I've confirmed the contribution guidelines.
[ ] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.
[ ] The PR has been properly tested.
[ ] The PR has been reviewed by the code owners.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.
[ ] The PR is ready for merge.

After all checkboxes are checked, anyone who has write access can merge the PR.

@shtokuda As we had a discussion, perhaps the time synchronize side is also needed to be fixed.

We tested the feature provided by this PR with @shtokuda and found it worked with minor fix in the time synchronize side. The video is as follows and we can see it is working only with a front single lidar.
Screencast.webm

I know that this is still in draft mode but I would want to avoid people investing their time in vain if we can help it.
@vividf @drwnz @badai-nguyen
Concatenation in itself should be for more than one node. If you have only one, you can delete it from the launcher. Using this node with one lidar would waste computational resources and increase latency.
Seeing the code changes, even if we go with this approach of adding single pointcloud compatibility, it should be solved with a better design rather just patching. @vividf if working on a redesign right now so if adopted it could be implemented there.
As @badai-nguyen mentioned, other nodes already need the pointcloud to be in the base frame (notably the undistortion) so there is not need to use this node for that purpose

Thanks for your comment!
The purpose of this PR was to improve convenience by allowing users to configure a single lidar system without having to rewire nodes.
To avoid conflicts with other changes, we will table this change for now.

Thank you for investigating this.
I agree with @knzo25 and @badai-nguyen, there should be no need to use the concat node with a single LiDAR.
While changing the system from multiple to one LiDAR then does require modification of your launch and node configuration, I believe that this is the correct process. Attempting to support a single LiDAR in a node designed specifically to handle multiple LiDARs could introduce more bugs and maintenance issues.


Unexpected syntax error in preload expression (nested queries)

Environment

Elixir version (elixir -v): 1.3.2
Database and version (PostgreSQL 9.4, MongoDB 3.2, etc.): MySQL 5.6
Ecto version (mix deps): 2.0.3 (master: 8f649b7)
Operating system: OSX Sierra

Current behavior
elevations_query = from elevation in Shield.Elevation

from user in Shield.User,
preload: [elevations: {^elevations_query, :right}]

Raises:
** (Ecto.Query.CompileError) `{^elevations_query, :right}` is not a valid preload expression. preload expects an atom, a (nested) list of atoms or a (nested) keyword list with a binding, atoms or lists as values. Use ^ if you want to interpolate a value

But:
elevations_query = from elevation in Shield.Elevation

from user in Shield.User,
preload: [elevations: ^{elevations_query, :right}]

Works as expected :)
Expected behavior
The syntax checker is probably confused since this is possible. I expect the first syntax to work.

Bug confirmed. Thank you.

I will take this :+1: If no rejections

Please go ahead!
--
José Valimwww.plataformatec.com.br
http://www.plataformatec.com.br/Founder and Director of R&D

@Troush ping.

Given that supporting this will add a lot of code complexity for little gain, I have improved the error message to make clear that ^ must be added to the outermost preload. Thank you!

@josevalim Sorry, totally forget about me taking this issue. My bad :(


PendingDispatch can be dispatched manually

The PendingDispatch was dispatched when it was destroyed, and it was not possible to retrieve the generated job ID (when using queues). This change allows dispatching the job like this, obtaining the new job ID:
$job_id = ProcessPodcast::dispatch()->onQueue('emails')->now();
It should be backwards-compatible. The dispatch logic in the __destruct method has been moved to the new dispatch method, which executes the previous statements if the new property dispatched is false, the default value.
This property will only be changed to true when dispatched to ensure the job is not dispatched twice.
I have not found any other way to obtain the queued job ID without having to extend large parts of the framework, but there might be another way. If that is the case, please forgive me and close the request.
Thanks!

now to me sounds like it will use the sync queue.
You can just pass a job directly to Bus::dispatch if you really need the job ID?
$jobId = Bus::dispatch(new Job);

Thanks for your response @taylorotwell, with this approach I can also send it to a specific queue, no caveats.


The problem with depth calculation

Thank you a lot for the tutorial!
But I noticed that the cuve is rendered twice. The problem disappears if I remove the albedo and emisson multiplication by ALPHA (but water depth will be lost). It also works if use constant value for ALPHA It looks like the problem in depth calculation.

I solved it in my low poly water by dividing refraction UV by PROJECTION_MATRIX[2][2] and VERTEX.z.

Glad to hear you found what was wrong :)


Added link for Python simulated device quickstart

The list was missing a link for the article about sending telemetry from a simulated device using Python. This change adds that link to the list.
As a side note, the diff says it's +2-1 but it's only +1, something about git diff seems to be measuring it improperly.

@asasine : Thanks for your contribution! The author, @, has been notified to review your proposed change.

@asasine : Thanks for your contribution! The author, @, has been notified to review your proposed change.

@dominicbetts - Would you review the proposed changes? Thanks

Hi @asasine - changes look good - thanks for taking the time to submit this PR.
Regards
Dominic
#sign-off

@dominicbetts: I'm sorry - only the author of this article, @, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.


Dataset: Global Trends in Mental Health Disorder

Data analysis of this dataset
https://data.world/vizzup/mental-health-depression-disorder-data/workspace/file?filename=Mental+health+Depression+disorder+Data.xlsx
https://www.kaggle.com/datasets/thedevastator/uncover-global-trends-in-mental-health-disorder
Global Trends in Mental Health Disorder from 1990 to 2017 by countries with some features (Education, Age, Gender, Suicide)
Similar dataset:
https://www.kaggle.com/datasets/imtkaggleteam/mental-health?select=1-+mental-illnesses-prevalence.csv
but for 1990 - 2019 (better, but! can be sythetic data)
Deliverables - Jupiter notebook

We need to add the data from this datasets (with Daily Users By Years data) from this datasets
https://www.businessofapps.com/data/facebook-statistics/
https://www.businessofapps.com/data/twitter-statistics/
https://www.businessofapps.com/data/instagram-statistics/ (edited)
This could be interesting too:
https://www.businessofapps.com/data/ai-app-market/


Do some configuration at run-time

Arduino libraries do not include files from the application sketch directory, and touching library configuration files in the libraries directory changes the configuration for all applications. Try instead to do at least some configuration at run-time. See https://github.com/rppicomidi/usb_midi_host/issues/13 for example

In order to use the run-time changes to the usb_midi_host library, I had to change the API for this library. Version 2.0.0 made the class libraries C++ templates. You can now subclass the default settings structure to override the settings you are most likely to need to change. See the documentation for more details.
@VocasoGK Please test version 2.0.0 of the EZ_USB_MIDI_HOST library. As I understand it, your project is using this library. I believe I fixed rppicomidi/usb_midihost#13  in an Arduino friendly way. Please open a new issue in EZ_USB_MIDI_HOST if you have problems.

Sure do! Will update when I have the time!


How to Add Datepicker and Refresh button in place of add button

How can i add a daterangepicker and a refresh button which can re-populate the data in grid.

You can use getQuickFilters like such:
     protected getQuickFilters(): Serenity.QuickFilter<Serenity.Widget<any>, any>[] {

        let filters = super.getQuickFilters();

        let fld = YourRow.Fields;

        Q.first(filters, x => x.field == fld.YourDateField).init = w => {

            (w as Serenity.DateEditor).valueAsDate = new Date(Date.now());

            let endDate = w.element.nextAll(".s-DateEditor").getWidget(Serenity.DateEditor);
            endDate.valueAsDate = new Date(Date.now());
            this.refresh();
        };

        return filters;
    }

Think your problem is resolved with stored proc sample.

yes it is solved.
thanks.


New version: LAIPIC.Perfoo version v1.0.2

ARP entries are correct.
Auto-updated by vedantmgoyal2009/winget-pkgs-automation in workflow run 800
Microsoft Reviewers: Open in CodeFlow

/azp run


[Intermittent] Unable to reach own service IP

Seen multiple times in local runs of 06-lb.sh, when running it it a loop:
ID    Frontend        Backend
222   [f00d::1:1]:0   1 => [f00d::a0f:0:0:dc06]:0
223   <IP_ADDRESS>:0       1 => <IP_ADDRESS>:0
224   [f00d::1:2]:0   1 => [fd02:1:1:1:1:1:1:1]:0
225   <IP_ADDRESS>:0       1 => <IP_ADDRESS>:0
----- 06-lb.sh: main: testing that server1 can reach its own service IP (IPv6)
PING f00d::1:1 (f00d::1:1): 56 data bytes
64 bytes from server1.cilium: icmp_seq=0 ttl=64 time=0.359 ms
64 bytes from server1.cilium: icmp_seq=1 ttl=64 time=1.359 ms
64 bytes from server1.cilium: icmp_seq=2 ttl=64 time=0.817 ms
64 bytes from server1.cilium: icmp_seq=3 ttl=64 time=0.458 ms
--- f00d::1:1 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max/stddev = 0.359/0.748/1.359/0.392 ms
----- 06-lb.sh: main: testing that server1 can reach its own service IP (IPv4)
PING <IP_ADDRESS> (<IP_ADDRESS>): 56 data bytes
--- <IP_ADDRESS> ping statistics ---
4 packets transmitted, 0 packets received, 100% packet loss
------------------------------------------------------------------------
                            Test Failed
Error: Unable to reach own service IP

------------------------------------------------------------------------

If I attempt to ping the IPv4 service IP from server1, the ping continues to fail.
cilium monitor output:
<- endpoint 56326, identity 311: <IP_ADDRESS> -> <IP_ADDRESS> EchoRequest
-> forward (Established connection), at To endpoint, to endpoint 56326, identity 311->311: <IP_ADDRESS> -> <IP_ADDRESS> EchoRequest
<- endpoint 56326, identity 311: <IP_ADDRESS> -> <IP_ADDRESS> EchoReply
<- overlay 10: <IP_ADDRESS> -> <IP_ADDRESS> EchoReply
xx drop (Not a local target address), to endpoint 0, identity 0->0: <IP_ADDRESS> -> <IP_ADDRESS> EchoReply

BPF LB:
 $ cilium bpf lb list
Service Address      Backend Address
------------------------------------
<IP_ADDRESS>:0            <IP_ADDRESS>:0 (223)
<IP_ADDRESS>:0            <IP_ADDRESS>:0 (225)
[f00d::1:2]:0        [fd02:1:1:1:1:1:1:1]:0 (224)
[f00d::1:1]:0        [f00d::a0f:0:0:dc06]:0 (222)

BPF services:
$ cilium service list
ID    Frontend        Backend
222   [f00d::1:1]:0   1 => [f00d::a0f:0:0:dc06]:0
223   <IP_ADDRESS>:0       1 => <IP_ADDRESS>:0
224   [f00d::1:2]:0   1 => [fd02:1:1:1:1:1:1:1]:0
225   <IP_ADDRESS>:0       1 => <IP_ADDRESS>:0

As far as I understand it, this is a bit of a weird case, because we can't just NAT the <IP_ADDRESS> service address into the backend address, because then you'll end up with a packet with identical source and destination, and the kernel will automatically drop it. I suspect that's why we're getting this <IP_ADDRESS> address. However, we should know on the way back what this address is and perform the reverse NAT for it.
 $ ip route
default via <IP_ADDRESS> dev enp0s3
<IP_ADDRESS> via <IP_ADDRESS> dev lbtest1
<IP_ADDRESS> dev lbtest1 scope link
<IP_ADDRESS>/24 dev enp0s3 proto kernel scope link src <IP_ADDRESS>
<IP_ADDRESS>/16 via <IP_ADDRESS> dev cilium_host src <IP_ADDRESS>
<IP_ADDRESS> dev cilium_host scope link
<IP_ADDRESS>/16 dev docker0 proto kernel scope link src <IP_ADDRESS>
<IP_ADDRESS>/24 dev enp0s8 proto kernel scope link src <IP_ADDRESS>
<IP_ADDRESS>/24 dev enp0s9 proto kernel scope link src <IP_ADDRESS>

$ iptables-save  | grep 10.11
-A CILIUM_POST ! -s <IP_ADDRESS>/32 -o cilium_host -m comment --comment "cilium host->cluster masquerade" -j SNAT --to-source <IP_ADDRESS>
-A CILIUM_POST -s <IP_ADDRESS>/16 ! -d <IP_ADDRESS>/16 ! -o cilium_+ -m comment --comment "cilium masquerade non-cluster" -j MASQUERADE

$ cilium status | grep  <IP_ADDRESS>
 <IP_ADDRESS>

This issue is fairly reliable, but is intermittent so may/may not occur on a given run of the test. I have a suspicion that there may be some cleanup not being performed after running 06-lb.sh, so it's plausible this is just an issue where the test is not idempotent, rather than an underlying bug. (That said, what happens if we restart cilium? Could we end up in the same situation?)

No longer observing this since CT changes were merged. Closing.


`doom/help-modules': C-u -> browse directory

If called with a C-u prefix, doom/help-modules now browses the module's
directory instead of opening its documentation. This exposes the VISIT-DIR
argument to interactive use.

As a side note, in latest develop, magit seems to no longer work like it did previously: I am now in evil-emacs-state in the magit status buffer and V is no longer bound to evil-visual-state; evil-visual-state also no longer has magit commands available, which is annoying since I use it for magit-spinout quite a lot.

I found the issue: 6665d2b6c235d80f5126bb328123cf4188527d43. evil-collection needs to be bumped, because evil-collection-magit is too old.

I found the issue: 6665d2b. evil-collection needs to be bumped, because evil-collection-magit is too old.

Sounds like were either git pulling instead of doom upgradeing. Update your local packages with doom sync -u. evil-collection has been bumped several times since your linked commit, and none of the commits since touch evil-collection-magit.


AGOL update from SGIDWebMercator data

The layers will now be managed in an ArcPro project on HNAS by @MichaelAGRC.

This look super cool. Do you want it to run tomorrow or can you show it to me monday?

We're in no hurry. I'll show it to you on Monday.


Please use HTTP protocol specs

The firmware currently always returns HTTP 200 (unless it is not responsive, in that case, nothing of course).
This is weird and incorrect IMHO. If there is something wrong with the request, the returned HTTP status code should reflect that.
Right now, one has to build custom error handling because of this, while normally one should be able to rely on HTTP specs.
For example:

This is a non-existing URL, while the API throws an error 422 in the response JSON; it should have thrown an HTTP 404 status code (since it does not exists).
Same for invalid data and other things once would expect a 400 or higher HTTP response code.

Sonoff will correct this in the next firmware

Great! 👍

issue has been fixed in the new firmware

Awesome! Thanks 👍


Add daisy ui component library

Description
Setup daisy ui component library migrating current tailwind configurations.

Description
Doned in the issue #27


Value of type 'SpotlightViewController' has no member 'spotlight'

var spotlight: SpotlightType? is defined without the public access modifier, which means it's not accessible from outside its own target. Even trying to build the basic usage example (showSpotlight()) fails.

fixed! 3fd6d16


Game crashes to launcher when starting world with Create Fabric active due to corrupting mob data

Game crashes to launcher when starting world with Create Fabric active. Appears to be due to setting a gravity attribute of a mob to null.
https://www.curseforge.com/minecraft/mc-mods/create-fabric
Minecraft Version: 1.18.2
Data Attributes: 1.1.6
Fabric API Version: 0.56.1
Create Fabric version: 0.4.11 Patch 11
Launch done through Curse client. Verified on my more heavily modded profile and a blank profile created to test if any other config settings were causing the issue. New world was created with base settings and cheats turned on. No other settings were touched before created the world. No other mods were installed or had been installed at time of crash.
Based on my limited knowledge of Minecraft modding and looking at several error reports before reporting, it appears that the issue occurs after the world has finished generating and is spawning initial mobs. Some return value is null, corrupting the mob and causing a ticking entity error when trying to call modifyGravity. The issue appears to occur on the first mob to be affected, as the entity in the entity details changes crash by crash.
Internal Server Log:
latest.log
Crash Report:
crash-2022-06-23_18.16.22-server.txt

Hi there,
Thank you for the detailed report, I'll look into it.

hi,
getting this exact issue as well, also narrowed it down to the create fabric mod. error mentions modifyGravity

bump with response from Create devs
https://github.com/Fabricators-of-Create/Create/issues/400

Hi there @udidifier,
I can confirm this; I had an interaction earlier on #16 (duplicate) and briefly discussed this. The crash has been mitigated with a null check, but I still need to fix the bug that caused the issue to begin with. I know why the error is happening so progress should not be too slow.
Thanks again for the alert, I'm closing this issue now as it is duplicate.


Add remark about adjustment made by AdjustWindowRect

@peterix : Thanks for your contribution! The author(s) have been notified to review your proposed change.


Fix percent to avoid get a null value

When the stop button pressed stream is over(it checks isActive boolean value) and percent value gets a null value. So the program goes crash.

Output error
NoSuchMethodError: The getter 'percent' was called on null.
Receiver: null
Tried calling: percent
See also: https://flutter.dev/docs/testing/errors


"Quail Hatching": myTile should be named coop in block "on [sprite] of kind [Player] overlaps [] at [location]"

Describe the bug
"Quail Hatching": myTile should be named coop in block "on [sprite] of kind [Player] overlaps [] at [location]"
Steps to reproduce the behavior

Navigate to https://arcade.makecode.com/--skillmap#zoo
Quail Hatching---->Start
Click step6
Drag block "on [sprite] of kind [Player] overlaps [] at [location]"
Click grey box on block and mouse hover the first tile

Actual behavior
There is no coop tile in block "on [sprite] of kind [Player] overlaps [] at [location]"
Expect behavior
myTile should be named coop in block "on [sprite] of kind [Player] overlaps [] at [location]"
Screenshot

Additional context
1.OS: Windows11
2.arcade version: 1.13.5
3.Microsoft MakeCode version: 8.6.4

Fixed in next PR

Still not fixed. Test version:
arcade version:  [1.12.30]
Microsoft MakeCode version:  [8.5.41]

Re-fixed and will upload with this PR


black lines in background when using midnight commander or neovim

Environment
Windows build number: 10.0.18363.476
Windows Terminal version (if applicable): 0.6.2951.0

Steps to reproduce

Run midnight commander mc with fontSize equal to 12 and with cascadia code or consolas font.
It is worth noting that with fontSize 14 or 10 the background renders correctly without black lines.

I don't think it's a duplicate. Although that bug also has two screenshots equivalent to the one here, one of them also showing mc in particular, that bug talks about the line drawing characters (i.e. the foreground) not touching each other.
This bug is here talks about the background color (blue) not filling the entire cell, leaving a gap.
In this screenshot over here, the period (from the top of a black line to the top of the next black line) is 57 pixels. Also if you magnify and look closely at some repeated piece of text (e.g. all those "4096"s), you'll see that antialiasing goes differently in every second row. In the upper row of each blackline-separated area, horizontal lines (e.g. the ones of digits 2, 4, the serif of 1, i, r etc.) are 2 pixels tall and super crispy. In every lower row these are uglier 1 pixel half-blue-half-white antialiased + 1 pixel white + 1 pixel half-blue-half-white antialiased.
So a row's height is 28.5 pixels, each text row is presumably 28.5 pixels below the previous one, and here and there (e.g. when rendering the background) rounding to integers kicks in.
Totally sounds like a HiDPI related story.

... although the screenshot of the entire desktop is 1920x1080, which is not HiDPI, unless the screenshot taking software downscaled it in which case who knows what other nasty things it did :) @ducaale What's your monitor's resolution?
A few other things to note:
Those black lines aren't really black, just something darker than desired. It depends based on the neighboring two background colors. It's different between cyan and blue (under "Command Options Right"), between blue and cyan (under "Name Size Modify time") [yup the order of colors also seems to matter], cyan and white (under "Left File Command") etc.
There are some such vertical lines, too, namely either before or after(*) the vertical line drawing chars. (*)Presumably according to the parity, I haven't verified.

You can see the same sort of DPI scaling issues in #2496, #2779, and #2790, all of which were marked as duplicates of #455. I think the title of #455 is a bit misleading, and isn't necessarily a good indication of the underlying cause of the problem.

@egmontkob yes the resolution is 1920x1080 with 150% scaling

You can see the same sort of DPI scaling issues in #2496, #2779, and #2790

Indeed those three bugs are the same as this one.

I think the title of #455 is a bit misleading

Or rather let's say: #455 is two technically different issues squeezed into one.

with 150% scaling

How does 150% scaling result in every second row being different? I have no idea :D

I'm guessing that this is one of those classic D2D 0.5-pixel offset issues :grin:

I have the same issue, workaround - press "ctrl -" one time (decrease font size), and this issue is getting fixed.
Also font size by default looks too big, for instance on Ubuntu it's usually smaller.

Scaling via ctrl + or ctrl - does not affect line issue for me.

I have the same issue, workaround - press "ctrl -" one time (decrease font size), and this issue is getting fixed.
Also font size by default looks too big, for instance on Ubuntu it's usually smaller.

Scaling via ctrl + or ctrl - does not affect line issue for me.

@phelps-matthew have tried fontSize of 10 or 14.

@ducaale Yes I've tried a large range of sizes. There is one particular font and size combination (Delugia Nerd Font at size 10) that did not result in lines, but this would seem to be a special case.

Same exact issue here. Changing fonts and font size does nothing. What DOES fix this (for me) is to ensure your 'Scale and Layout' setting under Settings/Display is at 100%. Not really a solution, but perhaps someone brighter than I can fix this. This is pretty much the one issue keeping me from leaving mintty/wsltty and solely using WT.

Lol! Black lines goes out but font's still have line breaks. Tried to change to different fonts - it still breaks vertical lines with space lines

Same here.From: Roman PapushaSent: Friday, April 24, 2020 7:51 AMTo: microsoft/terminalCc: PhilDim1; CommentSubject: Re: [microsoft/terminal] black lines in background when using midnight commander or neovim (#3626) Lol! Black lines goes out but font's still have line breaks. Tried to change to different fonts - it still breaks vertical lines with space lines—You are receiving this because you commented.Reply to this email directly, view it on GitHub, or unsubscribe.


Does the hopfield neural network can work correctly on MNIST?

I'm a tensorflow user instead of a scikit-learn user. Could you please tell me whether your implementation of hopfield neural network can work correctly on MNIST?

can work properly. Nice guide!


Add locale switcher to header

Adds a button to the header which also displays the current locale. When clicked triggers sidebar drawer to slide out with locale switcher inside.
Some possible outstanding tasks (need to decide whether these are within scope of MVP and, if so,  are within scope of this issue):

[ ] Should localeSwitcherOpen reducer/store state & openLocaleSwitcher() actions be bundled in with rest of locale actions/state or be put alongside other general application UI state?
[ ] Add "Need help" button to header (seems unrelated & not sure if it made it into MVP?)
[ ] Keep drawer open through application restart (do we want this? I suspect it's more important to persist user's current page)
[ ] Short-hand and/or localized names for locales (eg: 'EN' instead of 'English')
[x] Make sure header button icons correctly mirror in RTL
[ ] ... what else?

This looks good. I think we probably want to group our UI related state together but that's just my opinion. I think we don't want to persist the drawer being open (page is important I agree) although for it to feel consistent would be nice. I would almost lean towards the LTR language switching to work like the RTL switch meaning the drawer closes when you select a language. I'm not sure how hard that is or if it goes too far against how people expect the drawer to work (I personally think closing is a sorta unintuitive).  Finally I'm not sure if this is meant to mirror the designs but it could def. use some love in Android.

I think we probably want to group our UI related state together but that's just my initial thought.

Yes, I think so too but I get stuck trying to define what constitutes UI state and what is not. I can see a scenario where we create a userInterfaceStore for all things UI that it just becomes a
dumping ground for a bunch of unrelated state. :-\ In the meantime, I think our current state grouping/organization is sufficient.

I would almost lean towards the LTR language switching to work like the RTL switch meaning the drawer closes when you select a language.

My concern was that it might be disorientating to have the drawer disappear. But I actually think that this is the best approach.

Finally I'm not sure if this is meant to mirror the designs but it could def. use some love on Android.

I assume you're referring to the fact that it sits under the OS's status/notification bar. This is currently a problem application-wide (it's even worse with an iPhone X's 'notch'). It needs to be addressed with a top-level style.

Did you notice there is a story #106? All work to get to the MVP should be covered in stories under #104, unless there's something we've overlooked. Please check #104 carefully before writing new stories.

No I did not, this is in response to #100 (which I did not create, it was assigned to me during the last sprint planning meeting).

I assume you're referring to the fact that it sits under the OS's status/notification bar. This is currently a problem application-wide (it's even worse with an iPhone X's 'notch'). It needs to be addressed with a top-level style.

I just tried it on Android the and the buttons are square and blue and it generally does not match designs provided.

"Need help" button is out of scope as per https://docs.google.com/document/d/1130BnFQS0T4SrE7lA12bZjjTZuY8Fr7xzObunFxNkJE/edit#

@tnightingale totally my bad, I thought I was looking at a story, not a PR.

Good points @bensinjin I will update styling to match mocks (#118).

localeSwitcherOpen is not part of the locale store, it's either part of some localeSwitcher store or just stored in the component. I'm interested in exploring when component state should just live in the component. To be clear, I'm not a redux-store-for-everything-no-class-based-components zealot.

I would not expect the drawer to remain open after app restart ... I don't think. Do whatever is easier for now.

Localized names (English) for locales in the menu, definitely.

I would not expect the drawer to remain open after app restart ... I don't think. Do whatever is easier for now.

But should it remain open after a same-layout language is selected?
It seems like the consensus is trending towards "no" which means that we can move the localeSwitcherOpen state into component state.

Yeah, I think the drawer closes when you select a language, so we don't need an additional click to confirm the selection..

Localized names (English) for locales in the menu, definitely.

So, to clarify: locale names should be in English, eg:

English
Arabic
Chinese

Not:

English
عربى
中文

For the store organization, really pay attention to the structure that makes the components easy to test, that will typically be the best design. I anticipate that this will likely move us more towards a fooComponentStore and barComponentStore as opposed to allUIStore.foo and allUIStore.bar.

Locale names should be in the current locale, so "English" or "Anglais" depending,

Hang on a second, I spoke too soon. We should not go against the mocks so easily, I'm guessing Cherry put thought into this. And this is what the mockis have looked like all along. I think we should proceed according to the mocks.

Yup, confirmed with Cherry, follow the mocks, my bad.

Actually, I don't think you're done. Will not merge yet. Bug me if anything is unclear around this.

Ok, I have:

moved the drawer logic into component state
tidied up styling using proper React Native and Native Base components (FYI Native Base's <List /> is deprecated in favour of RN's <FlatList /> and <SectionList /> components)
updated the locale labels to be their localized (per-language) versions

I have implemented this with RN's <SectionList /> as it's supposed to give us "sticky-headers" but it doesn't seem to work. I'm interested to hear if anyone knows what's up with that?
There's currently a bunch of dummy locales registered (A, B, C, D, ..., etc) to demonstrate the list scrolling (and supposed to show "sticky-headers").
Please review :)

Change the commit messages to reference #106 rather than #100, sorry for the confusion on that.

I like the UX of the drawer closing immediately on selecting a language, it's consistent whether the app switches directionality or not, which is good.

There's an arrow on each entry in the select language menu which is not there in the mocks, is that a side effect of the SecitonList?

Rebased and removed the extra locales


fixed the issue about compilation. CPU_SET needs a pointer parameter

I am working on Fedora. My gcc version is "gcc version 5.3.1 20160406 (Red Hat 5.3.1-6) (GCC)"
There is a compiling error.
./src/Multicore.h:39:2: error: base operand of ‘->’ has non-pointer type ‘cpu_set_t’
  CPU_SET(threadId, mask);

Fixes #2


[translate v3, 2.17.0]: CredentialsProvider is called only once

Environment details

OS type and version: Ubuntu 22.04
Java version: 17
Version(s): 2.17.0

Steps to reproduce

Get a short lived oauth2 token
Pass it to the TranslateServiceClient
Call translateText once
Wait for token to expire
Call translateText another time

Expected
getCredentials() is either called every time a request is made or an expired token error is received
Code example

class TokenBasedGoogleCredentialsProvider(val token: String)
) : CredentialsProvider {
    override fun getCredentials(): Credentials {
        return GoogleCredentials.create(token)
    }
}

val credentials = TokenBasedGoogleCredentialsProvider("SOME_TOKEN_GENERATED_BY_OTHER_MEANS")
val translationServiceSettingsBuilder = TranslationServiceSettings.newBuilder()
translationServiceSettingsBuilder.setCredentialsProvider(credentialsProvider)
val client = TranslationServiceClient.create(translationServiceSettingsBuilder.build())

client.translateText("project/some-project", "cs", listOf("Hello"))
# Wait until token expires
client.translateText("project/some-project", "cs", listOf("Hello"))

Stack trace
Caused by: io.grpc.StatusRuntimeException: UNAUTHENTICATED: Failed computing credential metadata
	at io.grpc.Status.asRuntimeException(Status.java:539)
	... 14 common frames omitted
Caused by: java.lang.IllegalStateException: OAuth2Credentials instance does not support refreshing the access token. An instance with a new access token should be used, or a derived type that supports refreshing.
	at com.google.auth.oauth2.OAuth2Credentials.refreshAccessToken(OAuth2Credentials.java:366)
	at com.google.auth.oauth2.OAuth2Credentials$1.call(OAuth2Credentials.java:269)
	at com.google.auth.oauth2.OAuth2Credentials$1.call(OAuth2Credentials.java:266)
	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
	at com.google.auth.oauth2.OAuth2Credentials$RefreshTask.run(OAuth2Credentials.java:633)

Also Storage and BigQuery clients seem to behave that way, so I have no issues with expiring tokens, because the provider refreshes it by other means instead of a refresh token.

@deejay1 Would you share your observation on Storage and BigQuery clients? (such as error messages)

Also Storage and BigQuery clients seem to behave that way

@deejay1 Can you provide some references to documentation that informed your expectation for when getCredentials() is supposed to be called?
cc: @TimurSadykov

Closing due to lack of updates from the OP.


mod_h2 and MPM

Hello,
I have spent the last few days tracking down an issue with mod_h2 0.5.6 running with Apache 2.4.12 and nghttp2 0.7.14 on CentOS 6. I think I have found the cause of the issue (use of mpm_prefork_module, explained further below) but I would like to improve my understanding of the area.
To start with a little background, we are building httpd, mod_ssl, libnghttp2 and mod_h2 using a customised build process parameters and. We diverge somewhat from the documented source builds or sandbox builds.
In deployment, the issue manifests when making a HTTP/2 request for both cleartext or encrypted.
In cleartext, the client makes a request with HTTP/1.1 upgrade, we see the server respond with a 101 switching protocols, some SETTINGS frame but no data is ever sent and the response never completes. The server logs at debug level with some sanitisation are:
[h2:debug] h2_h2c.c: seeing h2c-14 upgrade invitation
[h2:debug] h2_conn.c h2_conn_process start
[h2:debug] h2_session.c: upgrading h2c session with HTTP2-Settings: AAMAABkAAQAAP__ -> (0)
[h2:debug] h2_stream.c: h2_stream(1-1): created
[h2:debug] h2_session.c: h2_session(1-1): opened
[h2:debug] h2_request.c: h2_request(1-1): created
[h2:debug] h2_request.c: h2_request(1): written request GET /index.html, host=[server IP]
[h2:debug] h2_workers.c: h2_workers: scheduling task(1-1)
[h2:debug] h2_stream.c: h2_stream(1-1): closing input
[h2:debug] h2_stream.c: h2_stream(1-1): end header, task GET /index.html
[h2:debug] h2_conn.c: h2_session(1): starting on :80
[h2:debug] h2_mplx.c: h2_mplx(1): trywait on data for 0.010000 ms)
[h2:debug] h2_mplx.c: h2_mplx(1): trywait on data for 0.020000 ms)
[h2:debug] h2_mplx.c: h2_mplx(1): trywait on data for 0.030000 ms)
[h2:debug] h2_mplx.c: h2_mplx(1): trywait on data for 0.040000 ms)
[snip]
[h2:debug] h2_mplx.c: h2_mplx(1): trywait on data for 200.000000 ms)
[repeats until client quits]

In encrypted, the client makes a request with h2-14 APLN ID, we see the server respond with h2-14 ALPN ID. Some SETTINGS frame but no data is ever sent and the response never completes. The server logs at debug level with some sanitisation are:
[ssl:debug] ssl_engine_io.c: SSL negotiated protocol: 'h2-14'
[h2:debug] h2_h2.c: protocol set va ALPN to h2-14
[ssl:debug] ssl_engine_io.c SSL NPN negotiated protocol '(null)'
[h2:debug] h2_conn.c h2_conn_main start
[h2:debug] h2_conn.c: h2_session(1): starting on :443
[h2:debug] h2_stream.c: h2_stream(1-1): created
[h2:debug] h2_session.c: h2_session: stream(1-1): opened
[h2:debug] h2_stream.c: h2_stream(1-1): closing input
[h2:debug] h2_stream.c: h2_stream(1-1): end header, task GET /index.html
[h2:debug] h2_stream.c: h2_stream(1-1): closing input
[h2:debug] h2_session.c: h2_stream(1-1): input closed
[h2:debug] h2_mplx.c: h2_mplx(1): trywait on data for 0.010000 ms)
[h2:debug] h2_mplx.c: h2_mplx(1): trywait on data for 0.020000 ms)
[h2:debug] h2_mplx.c: h2_mplx(1): trywait on data for 0.030000 ms)
[h2:debug] h2_mplx.c: h2_mplx(1): trywait on data for 0.040000 ms)
[snip]
[h2:debug] h2_mplx.c: h2_mplx(1): trywait on data for 200.000000 ms)
[repeats until client quits]

After some investigation, we found that httpd was configured to use mpm_prefork_module. Changing to mpm_worker_module prevented the issue from reoccurring, allowing both cleartext and encrypted HTTP/2 to work.
Checking the commit logs I can see that there has been some activity around MPM but no mention of mpm_prefork_module. Is it unsupported? Or would you have expected it to work? Is there perhaps some other factor that is combining to cause this issue?
Regards
Lucas

As soon as this issue is raised I then find the Known Issues section that talks about prefork, added in eee59bc880e8d91500dfd0d2ccabdb0ab2adb4fa.
It seems our version pre-dates this, so we were unfortunate not to have received the warning. Can you possibly provide any insight into the background that lead up to this becoming a known issue?

Hi Lucas,
thanks for the detailed description. I had so far simply not looked deeper into why prefork being such a blocker, but will put this on my todo list now. Any fix will come on the latest version which requires a 1.0.x nghttp2. I hope that is not an issue.
cheers, Stefan

Am 24.06.2015 um 21:40 schrieb Lucas Pardue<EMAIL_ADDRESS>As soon as this issue is raised I then find the Known Issues section that talks about prefork, added in eee59bc.
It seems our version pre-dates this, so we were unfortunate not to have received the warning. Can you possibly provide any insight into the background that lead up to this becoming a known issue?
—
Reply to this email directly or view it on GitHub.

Hi Stefan,
Thanks for the feedback. There is no issue with a fix coming into a later version, we will keep an eye open for future developments.
In the meantime we will proceed with using mpm_worker so I am going to close this issue.
Regards
Lucas

I had a rework of the scheduling / thread sync parts due to some concurrency issues. I ran the test suite with mpm_prefork afterwards and all is fine on my OS X and Ubuntu 14.04 LTS image. Perhaps you might want to give this version a test drive. Feedback welcome.

Am 25.06.2015 um 12:45 schrieb Lucas Pardue<EMAIL_ADDRESS>Closed #30.
—
Reply to this email directly or view it on GitHub.

bytes GmbH
Hafenweg 16, 48155 Münster, Germany
Phone: +49<PHONE_NUMBER>. Amtsgericht Münster: HRB5782

Hi Stefan,
Thanks for looking into this. I'll try and test your changes in out environment next week.

Hi,
one thing I found in the meantime: without further config, mod_h2 only has 1 worker thread in prefork per connection. you might want to raise this by H2WorkersMax (look up the spelling :)

Am 26.06.2015 um 18:37 schrieb Lucas Pardue<EMAIL_ADDRESS>Hi Stefan,
Thanks for looking into this. I'll try and test your changes in out environment next week.
—
Reply to this email directly or view it on GitHub.

Hi Stefan,
I've tested setting H2MaxWorkers with our mod_h2 0.5.6 install when using mpm_prefork. I can confirm that setting a value >= 1 results in the server responding correctly. Setting a value of 0causes the stalling behaviour described before.  Should 0 be allowed/supported?)

Hi Lucas,
thanks for the test. I agree that a value of 0 makes no sense here and should be a config error.
I will add also some advice on how this config value relates to the chosen mpm and make the default more gracious.

Am 29.06.2015 um 12:13 schrieb Lucas Pardue<EMAIL_ADDRESS>Hi Stefan,
I've tested setting H2MaxWorkers with our mod_h2 0.5.6 install when using mpm_prefork. I can confirm that setting a value >= 1 results in the server responding correctly. Setting a value of 0causes the stalling behaviour described before. Should 0 be allowed/supported?)
—
Reply to this email directly or view it on GitHub.

bytes GmbH
Hafenweg 16, 48155 Münster, Germany
Phone: +49<PHONE_NUMBER>. Amtsgericht Münster: HRB5782


Open Source Workshop page

Finally putting together the homepage for the Open Source workshop, as described here:
https://docs.google.com/document/d/1xyYIkeZ_htZ76tmrA06UakSvkOX7ghWL4RG7Gr6oIbE/edit
Note that the RSVP mechanics very closely resemble the "Bonus Round" on http://18f.github.io/hourofcode/ that @leahbannon and I put together.
Open questions

Does the description make sense – and do the instructions work – for someone without any context?
What information am I forgetting?
Do we need to know people's skill levels and/or preferred programming languages in advance?
Do people need to RSVP through Meetup as well?

Feels a bit redundant, but would be nice to have a way to email attendees before/after the event. I suppose we could just leave comments on all the PRs if we need to...

What's a better name for the event?

TODOs

[ ] Create event on Meetup (even if RSVPs aren't done there)
[ ] Announce to Hacker Hours mailing list

/cc @gabekneisley @melodykramer @wslack @ultrasaurus @jdaudier

I think the instructions are fantastic. Clear and unambiguous, assuming you have an understanding of what github is (which I think is an appropriate baseline for this event).
The only thing missing, IMO, is that the event description presupposes that you know what open source is, want to be part of it, and can help. I don't think we want to take those things for granted. I don't know how to explain this succinctly yet, but if others agree that we should explain this, I'll be happy to write a draft. Something like:
Open Source Workshop
Did you know you can make meaningful contributions to the code powering thousands of websites, and running on millions of browsers? Absolutely! You can improve your coding, technical writing and collaboration skills, expand your professional network, and help move the art of software engineering forward all in one fun way—contribute to open source! It looks good on your resume, teaches you how to be thorough and work within teams, and gives you inside access to some of the coolest projects being built. etc

FYI @afeld - another event with similar cause: http://www.meetup.com/Developers-for-Good/events/221704410

might be interesting to ask attendees to create an issue with what they would like to learn in this workshop

I thought this OS project might be good one to practice against: https://github.com/illacceptanything/illacceptanything
Not as final contribution since it's kind of a joke. But might be fun to use for demo purposes.

the event description presupposes that you know what open source is, want to be part of it, and can help

Mmmm, good observation.

Something like

Perfect – added!

another event with similar cause: http://www.meetup.com/Developers-for-Good/events/221704410

Haha @courte @dbness we should talk.

Past one

Yeah, this is definitely not a new idea. Have a bunch of examples linked at the top of the Google Doc.

might be interesting to ask attendees to create an issue with what they would like to learn in this workshop

Good call – added to the page!

I thought this OS project might be good one to practice against

Good idea! Added to the Google Doc.

Going to quietly merge, and will start working on the email. Still open to iterate on the page, obvs. #metaopensource


NadekoBot self-host Offline

Simple question, is it possible to self-host it offline or through a platform that can keep the bot up even if my computer is offline ?
If so, any advice on which and how to do it ?
Thanks.

Yes, check "Linux hosting guide". It shows you how to setup your bot on digitalocean VPS which runs 24/7


prompt_style

I don't want to use the dataset styles listed in prompt styles: Dict. I want to use my own defined dataset style. How can I build my own dataset style to use finetune/ora，my datasets style is
{
"conversation": [
{
"system": "This is like an instruction",
"input": "",
"output": ""
}]
}

because i want use Multi round conversation data

I think the easiest way here would be to use on of the existing datasets as templates. I remember that deita had multi turn questions in the dataset, so I added this as an option. Maybe this is helpful as a template for building your own datset:
https://github.com/Lightning-AI/litgpt/blob/cbbe9cda9f0ad535c471460236cfdb0b4f50e2bd/litgpt/data/deita.py#L29
But note that LitGTP otherwise doesn't do anything special for multi turn. It basically treat the data multiturn example as another regular input example during training.

Thank you very much for your reply，I've read your explanation about Dora, it's excellent. Thank you.

Glad to hear you found it useful! There are currently so many todos, but yeah, adding DoRA to LitGPT some time would be great.


feat(ENG-1637): start new sessions from a session

this adds the start syscall to python

do we really need this capability?
does the UI knows how to handle multi session stuff ?
can't we just trigger a different webhook and let it run as any other workflow ?
do we have any relation between this sessions ? how do we handle replay ? how do we handle error in the child sessions ?


Lenient Stack Size 1.19 ETA?

I just wanted to drop a line and see if you had an idea about when / if you plan to update LSS to 1.19. If you'd be open to a pull request, I am happy to give it a shot.
Thanks!

Hey there. I wanted to check in and see if you have an update on whether you plan to update Lenient Stack Size to 1.19. If you're busy, I'd be more than happy to take a stab at updating it for you and submitting a pull request. Alternatively, if you don't plan to update past 1.18 and don't mind my doing so, I can also fork it to keep it alive.
Thanks!


Quest Tracker cannot be closed [BUG]

Module Version: v0.7.9
Describe the bug
Once the quest tracker is opened, the window cannot be closed. I tried deactivating and the reactivating the module, but the window stays and is still impossible to close.
To Reproduce
Steps to reproduce the behavior:

Open Quest Tracker from the left pane.
Try to close the Quest Tracker by clicking the X.
See error.

Expected behavior
The window should close.
Screenshots
If applicable, add screenshots to help explain your problem.
Browser:

Brave

Foundry Version:
0.8.9
Game System:
Old-School Essentials
Additional context
Hosted on The Forge
Active Modules:
Chat Message Accessibility Indicators v1.0.0;
Chat Portrait v0.5.27;
Combat Tracker Effect Icon Tooltips v2.0.0;
Compendium Folders v2.3.64;
DF Chat Enhancements v3.5.1;
DF Quality of Life v1.6.1;
DFreds Droppables v1.4.0;
DF Scene Enhancement v3.4.2;
Dice So Nice! v4.2.2;
Dice Tray v1.3.2;
Drag Ruler v1.9.0;
Forien's Quest Log v0.7.9;
GM Notes v0.4.1;
GM Screen v2.9.0;
Illandril's Chat Enhancements v1.2.3;
Illandril's Token HUD scaler v1.4.2;
Inline Table Rolls v0.0.4;
Keybind Lib v0.3.4;
Less Fog v0.9.0;
lib - Color Settings v2.8.1;
Library: Chat Commands v1.4.0;
libWrapper v<IP_ADDRESS>;
Multilevel Tokens v1.5.2;
Perfect Vision v2.10.8;
Permission Viewer v0.8.14;
Pin Cushion v1.5.0;
Pings v1.2.12+0.8.6;
Quick Insert - Search Widget v2.5.3;
Scene Defaults v1.0.4;
Settings Extender v1.2.0;
Simple Calendar vv1.3.75;
SmallTime v1.13.7;
Smart Target v0.6.7;
socketlib v1.0.9;
Tidy UI - Game Settings v0.1.28;
Tokenizer v3.5.0;
TorchLight v0.10.0;
Window Controls v1.5.3;
Inactive Modules:
About Time v1.0.6;
Babele v2.1.3;
Better Roofs v1.3.6;
Cautious Gamemaster's Pack v0.5.1;
Deepflame's Chat Cards v1.2.2;
DF User Logger v1.6.4;
Find the culprit v1.4.0;
Fog Manager v1.0.4;
FoundryVTT Arms Reach v2.1.6;
fr-FR - Core Game v<IP_ADDRESS>;
Levels v<IP_ADDRESS>;
Old School Essentials OGL Content v0.5.1;
PDFoundry v0.8.10;
Polyglot v1.7.28;
Token Mold v2.14.0;
Trigger Happy v0.8.25;
Wall Height v<IP_ADDRESS>;

Hi @JordanRR; thanks for posting an issue. Check that Window Controls is working as intended and not pinning the quest tracker. Someone else just recently wrote the exact same issue essentially on Forien's defunct / old repo for FQL. This is the correct repo for the maintained version of FQL, but review that issue here:
You are running a lot of modules, so whenever you find an issue especially with FQL since it is in a rather solid place right now try disabling all modules except FQL or whatever module you need to verify that is working.

Thank you for the very quick response. It looks like Windows Control is the culprit, si I will notify them.
I wish you a happy new year!


Now nginx-rtmp-module will support fMP4 format

I've release a pre-release version to support fMP4.
Please use and give me your ideas/contributes.
Thanks,
https://github.com/dalmatele/nginx-rtmp-module/releases/tag/<IP_ADDRESS>

Does this work with fmp4 low latency CMAF container? @dalmatele
BTW, awesome find, haven't tested yet, is there any documentation on how to make this work with fmp4??

@bijanmmarkes : you can follow bellow link to know how to config:
https://github.com/uizaio/nginx-rtmp-module/wiki/Prerelease-now-support-fMP4-format

@dalmatele, links are broken. why your repo is hidden or deleted?


[feature request] Open problem description in a separate split

Currently, the problem description along with the template code(based on the programming language configured) opens up in a single split. Due to this, when we run LeetCodeTest, and errors which leetcode api sends back does not match with the buffer line number. This causes trouble in debugging. It would be great if we could open the problem split in a separate split, and the code template in another split. Configuration options, if provided, to configure the split would be an added bonus.
Thanks,

It's a good idea!
I'll see what we can do.


HBASE-28598 Fixes NPE for writer object access in AsyncFSWAL#closeWriter

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m  3s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
4m 36s
branch-2 passed

+1 :green_heart:
compile
4m  1s
branch-2 passed

+1 :green_heart:
checkstyle
0m 47s
branch-2 passed

+1 :green_heart:
spotless
1m 11s
branch has no errors when running spotless:check.

+1 :green_heart:
spotbugs
2m 25s
branch-2 passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
4m 20s
the patch passed

+1 :green_heart:
compile
4m  3s
the patch passed

+1 :green_heart:
javac
4m  3s
the patch passed

+1 :green_heart:
checkstyle
0m 49s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
hadoopcheck
12m 34s
Patch does not cause any errors with Hadoop 2.10.2 or 3.3.6.

+1 :green_heart:
spotless
1m  3s
patch has no errors when running spotless:check.

+1 :green_heart:
spotbugs
2m 44s
the patch passed

_ Other Tests _

+1 :green_heart:
asflicense
0m 18s
The patch does not generate ASF License warnings.

42m  2s

Subsystem
Report/Notes

Docker
ClientAPI=1.45 ServerAPI=1.45 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5909/1/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/5909

Optional Tests
dupname asflicense javac spotbugs hadoopcheck hbaseanti spotless checkstyle compile

uname
Linux 96efd5497e0b 5.4.0-174-generic #193-Ubuntu SMP Thu Mar 7 14:29:28 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 3165e385a4

Default Java
Eclipse Adoptium-11.0.17+8

Max. process+thread count
77 (vs. ulimit of 30000)

modules
C: hbase-server U: hbase-server

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5909/1/console

versions
git=2.34.1 maven=3.8.6 spotbugs=4.7.3

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 44s
Docker mode activated.

-0 :warning:
yetus
0m  5s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
4m 11s
branch-2 passed

+1 :green_heart:
compile
1m 12s
branch-2 passed

+1 :green_heart:
shadedjars
7m  4s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 36s
branch-2 passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
3m 38s
the patch passed

+1 :green_heart:
compile
0m 57s
the patch passed

+1 :green_heart:
javac
0m 57s
the patch passed

+1 :green_heart:
shadedjars
6m 31s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 23s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
221m 58s
hbase-server in the patch passed.

252m  8s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5909/1/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/5909

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux f506506a0b7a 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 3165e385a4

Default Java
Eclipse Adoptium-11.0.17+8

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5909/1/testReport/

Max. process+thread count
4411 (vs. ulimit of 30000)

modules
C: hbase-server U: hbase-server

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5909/1/console

versions
git=2.34.1 maven=3.8.6

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 58s
Docker mode activated.

-0 :warning:
yetus
0m  6s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
4m  8s
branch-2 passed

+1 :green_heart:
compile
1m  3s
branch-2 passed

+1 :green_heart:
shadedjars
6m 45s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 41s
branch-2 passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
3m 47s
the patch passed

+1 :green_heart:
compile
1m 11s
the patch passed

+1 :green_heart:
javac
1m 11s
the patch passed

+1 :green_heart:
shadedjars
7m  6s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 29s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
282m 16s
hbase-server in the patch passed.

313m 35s

Subsystem
Report/Notes

Docker
ClientAPI=1.45 ServerAPI=1.45 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5909/1/artifact/yetus-jdk8-hadoop2-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/5909

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 2092f775449e 5.4.0-174-generic #193-Ubuntu SMP Thu Mar 7 14:29:28 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 3165e385a4

Default Java
Temurin-1.8.0_352-b08

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5909/1/testReport/

Max. process+thread count
4554 (vs. ulimit of 30000)

modules
C: hbase-server U: hbase-server

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5909/1/console

versions
git=2.34.1 maven=3.8.6

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

Could you please provide more details about how it could be null when calling doShutdown?

Could you please provide more details about how it could be null when calling doShutdown?
In the test execution,
During MasterRegion#createWAL, if WAL creation fails, then writer is not created, and then close is being called in AbstractFSWALProvider#getWAL. This then throws NPE in AsyncFSWAL#closeWriter.


Add FR spell checker by default

My Setup

Operating System: Fedora 33
App Version: Last
Installation type: Flatpak

[X] I have tested with the latest version
[x] I can simulate the issue easily

Description
FR spell checker is not available.
Current Behavior
User need to install spell checker manually (after creating dictionnaries directory manually).
Expected Behavior
Spell checker works out of the box

Please test if the latest release did solve this. If not please reopen the issue or create a new one and tell us. I will be closing this one for now.
Thank you!


1 year = 12 months + 5 days ?

What can be improved?
I have a datetime : DateTime (2025-08-08 22:00:00.000)
I calculate the duration between now and a datetime
DateTime.fromMillisecondsSinceEpoch(farmLockUserInfos.end! * 1000,).difference(DateTime.now().toUtc()).toDurationString()
The lib returns 12 months and 5 days
Ideas on implementing the enhancement?
Is it possible to return 12 months ?
Thx

Hello there!
You can try changing the format to month only with .toDurationString(format: DurationFormat([DurationUnit.month])).
If above still doesn't help your use case, please provide enough detail so I can reproduce the issue above. (e.g., replace now with ISO 8601 string)
There is something that might be not very well documented about how months are calculated in durations, I will try to document it better.
When calculating durations, months are 30 days, flat. Meaning, Moment.parse("2025-02-28").difference(Moment.parse("2025-03-31")).toDurationString() will result in a month and a day.
It's understandable people may expect a month and 3 days, but it's unnecessarily complicated, and isn't supported in moment_dart at this time.

Closing this as it seems to be about unsupported feature/function. You can still reply to this thread for more information :D :D


Part 2 of generic generators

revert some of the refactoring of the generator

'current' versus 'sent' - use sent, to match what we've been using in XDS and the actual semantics
grouping version and nonce doesn't make sense.

added a generic mechanism to register generators and match against the metadata.
By default the new code should be off and not affect any existing code path

continue to use "./" instead of "/" for default paths, so testing and running as non-root is possible.

See PR#22897 for context - including tests. Tests need to be merged last, since they use the
2 new generators ( grpc and api ).

This also makes the 'standard' generator implement the new interface, for consistency.
When we start working on 'better transport' and v3 it will be useful to allow a consistent way
for workloads to request a specific generator type.

@costinm: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-test_istio
2ef80329adc2d69c7c8979c6c9c60abd7760ce29
link
/test release-test_istio

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

@costinm: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-test_istio
2ef80329adc2d69c7c8979c6c9c60abd7760ce29
link
/test release-test_istio

integ-local-tests_istio
2ef80329adc2d69c7c8979c6c9c60abd7760ce29
link
/test integ-local-tests_istio

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

@costinm: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-test_istio
2ef80329adc2d69c7c8979c6c9c60abd7760ce29
link
/test release-test_istio

integ-local-tests_istio
2ef80329adc2d69c7c8979c6c9c60abd7760ce29
link
/test integ-local-tests_istio

unit-tests_istio
2ef80329adc2d69c7c8979c6c9c60abd7760ce29
link
/test unit-tests_istio

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

@costinm: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-test_istio
2ef80329adc2d69c7c8979c6c9c60abd7760ce29
link
/test release-test_istio

integ-local-tests_istio
2ef80329adc2d69c7c8979c6c9c60abd7760ce29
link
/test integ-local-tests_istio

unit-tests_istio
2ef80329adc2d69c7c8979c6c9c60abd7760ce29
link
/test unit-tests_istio

integ-distroless-k8s-tests_istio
2ef80329adc2d69c7c8979c6c9c60abd7760ce29
link
/test integ-distroless-k8s-tests_istio

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

@costinm: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-test_istio
2ef80329adc2d69c7c8979c6c9c60abd7760ce29
link
/test release-test_istio

integ-local-tests_istio
2ef80329adc2d69c7c8979c6c9c60abd7760ce29
link
/test integ-local-tests_istio

unit-tests_istio
2ef80329adc2d69c7c8979c6c9c60abd7760ce29
link
/test unit-tests_istio

integ-distroless-k8s-tests_istio
2ef80329adc2d69c7c8979c6c9c60abd7760ce29
link
/test integ-distroless-k8s-tests_istio

integ-security-k8s-tests_istio
2ef80329adc2d69c7c8979c6c9c60abd7760ce29
link
/test integ-security-k8s-tests_istio

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

@costinm: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-test_istio
2ef80329adc2d69c7c8979c6c9c60abd7760ce29
link
/test release-test_istio

integ-local-tests_istio
2ef80329adc2d69c7c8979c6c9c60abd7760ce29
link
/test integ-local-tests_istio

unit-tests_istio
2ef80329adc2d69c7c8979c6c9c60abd7760ce29
link
/test unit-tests_istio

integ-distroless-k8s-tests_istio
2ef80329adc2d69c7c8979c6c9c60abd7760ce29
link
/test integ-distroless-k8s-tests_istio

integ-security-k8s-tests_istio
2ef80329adc2d69c7c8979c6c9c60abd7760ce29
link
/test integ-security-k8s-tests_istio

lint_istio
2ef80329adc2d69c7c8979c6c9c60abd7760ce29
link
/test lint_istio

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

@costinm: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-test_istio
2ef80329adc2d69c7c8979c6c9c60abd7760ce29
link
/test release-test_istio

integ-local-tests_istio
2ef80329adc2d69c7c8979c6c9c60abd7760ce29
link
/test integ-local-tests_istio

unit-tests_istio
2ef80329adc2d69c7c8979c6c9c60abd7760ce29
link
/test unit-tests_istio

integ-distroless-k8s-tests_istio
2ef80329adc2d69c7c8979c6c9c60abd7760ce29
link
/test integ-distroless-k8s-tests_istio

integ-security-k8s-tests_istio
2ef80329adc2d69c7c8979c6c9c60abd7760ce29
link
/test integ-security-k8s-tests_istio

lint_istio
2ef80329adc2d69c7c8979c6c9c60abd7760ce29
link
/test lint_istio

integ-conformance-k8s-tests_istio
2ef80329adc2d69c7c8979c6c9c60abd7760ce29
link
/test integ-conformance-k8s-tests_istio

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

@costinm: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-test_istio
2ef80329adc2d69c7c8979c6c9c60abd7760ce29
link
/test release-test_istio

integ-local-tests_istio
2ef80329adc2d69c7c8979c6c9c60abd7760ce29
link
/test integ-local-tests_istio

unit-tests_istio
2ef80329adc2d69c7c8979c6c9c60abd7760ce29
link
/test unit-tests_istio

integ-distroless-k8s-tests_istio
2ef80329adc2d69c7c8979c6c9c60abd7760ce29
link
/test integ-distroless-k8s-tests_istio

integ-security-k8s-tests_istio
2ef80329adc2d69c7c8979c6c9c60abd7760ce29
link
/test integ-security-k8s-tests_istio

lint_istio
2ef80329adc2d69c7c8979c6c9c60abd7760ce29
link
/test lint_istio

integ-conformance-k8s-tests_istio
2ef80329adc2d69c7c8979c6c9c60abd7760ce29
link
/test integ-conformance-k8s-tests_istio

integ-galley-k8s-tests_istio
2ef80329adc2d69c7c8979c6c9c60abd7760ce29
link
/test integ-galley-k8s-tests_istio

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

@costinm: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-test_istio
2ef80329adc2d69c7c8979c6c9c60abd7760ce29
link
/test release-test_istio

integ-local-tests_istio
2ef80329adc2d69c7c8979c6c9c60abd7760ce29
link
/test integ-local-tests_istio

unit-tests_istio
2ef80329adc2d69c7c8979c6c9c60abd7760ce29
link
/test unit-tests_istio

integ-distroless-k8s-tests_istio
2ef80329adc2d69c7c8979c6c9c60abd7760ce29
link
/test integ-distroless-k8s-tests_istio

integ-security-k8s-tests_istio
2ef80329adc2d69c7c8979c6c9c60abd7760ce29
link
/test integ-security-k8s-tests_istio

lint_istio
2ef80329adc2d69c7c8979c6c9c60abd7760ce29
link
/test lint_istio

integ-conformance-k8s-tests_istio
2ef80329adc2d69c7c8979c6c9c60abd7760ce29
link
/test integ-conformance-k8s-tests_istio

integ-galley-k8s-tests_istio
2ef80329adc2d69c7c8979c6c9c60abd7760ce29
link
/test integ-galley-k8s-tests_istio

integ-pilot-k8s-tests_istio
2ef80329adc2d69c7c8979c6c9c60abd7760ce29
link
/test integ-pilot-k8s-tests_istio

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

@costinm: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-test_istio
2ef80329adc2d69c7c8979c6c9c60abd7760ce29
link
/test release-test_istio

integ-local-tests_istio
2ef80329adc2d69c7c8979c6c9c60abd7760ce29
link
/test integ-local-tests_istio

unit-tests_istio
2ef80329adc2d69c7c8979c6c9c60abd7760ce29
link
/test unit-tests_istio

integ-distroless-k8s-tests_istio
2ef80329adc2d69c7c8979c6c9c60abd7760ce29
link
/test integ-distroless-k8s-tests_istio

integ-security-k8s-tests_istio
2ef80329adc2d69c7c8979c6c9c60abd7760ce29
link
/test integ-security-k8s-tests_istio

lint_istio
2ef80329adc2d69c7c8979c6c9c60abd7760ce29
link
/test lint_istio

integ-conformance-k8s-tests_istio
2ef80329adc2d69c7c8979c6c9c60abd7760ce29
link
/test integ-conformance-k8s-tests_istio

integ-galley-k8s-tests_istio
2ef80329adc2d69c7c8979c6c9c60abd7760ce29
link
/test integ-galley-k8s-tests_istio

integ-pilot-k8s-tests_istio
2ef80329adc2d69c7c8979c6c9c60abd7760ce29
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
2ef80329adc2d69c7c8979c6c9c60abd7760ce29
link
/test integ-telemetry-k8s-tests_istio

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

@costinm: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-test_istio
2ef80329adc2d69c7c8979c6c9c60abd7760ce29
link
/test release-test_istio

integ-local-tests_istio
2ef80329adc2d69c7c8979c6c9c60abd7760ce29
link
/test integ-local-tests_istio

unit-tests_istio
2ef80329adc2d69c7c8979c6c9c60abd7760ce29
link
/test unit-tests_istio

integ-distroless-k8s-tests_istio
2ef80329adc2d69c7c8979c6c9c60abd7760ce29
link
/test integ-distroless-k8s-tests_istio

integ-security-k8s-tests_istio
2ef80329adc2d69c7c8979c6c9c60abd7760ce29
link
/test integ-security-k8s-tests_istio

lint_istio
2ef80329adc2d69c7c8979c6c9c60abd7760ce29
link
/test lint_istio

integ-conformance-k8s-tests_istio
2ef80329adc2d69c7c8979c6c9c60abd7760ce29
link
/test integ-conformance-k8s-tests_istio

integ-galley-k8s-tests_istio
2ef80329adc2d69c7c8979c6c9c60abd7760ce29
link
/test integ-galley-k8s-tests_istio

integ-pilot-k8s-tests_istio
2ef80329adc2d69c7c8979c6c9c60abd7760ce29
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
2ef80329adc2d69c7c8979c6c9c60abd7760ce29
link
/test integ-telemetry-k8s-tests_istio

integ-mixer-k8s-tests_istio
2ef80329adc2d69c7c8979c6c9c60abd7760ce29
link
/test integ-mixer-k8s-tests_istio

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

@costinm: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-test_istio
2ef80329adc2d69c7c8979c6c9c60abd7760ce29
link
/test release-test_istio

integ-local-tests_istio
2ef80329adc2d69c7c8979c6c9c60abd7760ce29
link
/test integ-local-tests_istio

unit-tests_istio
2ef80329adc2d69c7c8979c6c9c60abd7760ce29
link
/test unit-tests_istio

integ-distroless-k8s-tests_istio
2ef80329adc2d69c7c8979c6c9c60abd7760ce29
link
/test integ-distroless-k8s-tests_istio

integ-security-k8s-tests_istio
2ef80329adc2d69c7c8979c6c9c60abd7760ce29
link
/test integ-security-k8s-tests_istio

lint_istio
2ef80329adc2d69c7c8979c6c9c60abd7760ce29
link
/test lint_istio

integ-conformance-k8s-tests_istio
2ef80329adc2d69c7c8979c6c9c60abd7760ce29
link
/test integ-conformance-k8s-tests_istio

integ-galley-k8s-tests_istio
2ef80329adc2d69c7c8979c6c9c60abd7760ce29
link
/test integ-galley-k8s-tests_istio

integ-pilot-k8s-tests_istio
2ef80329adc2d69c7c8979c6c9c60abd7760ce29
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
2ef80329adc2d69c7c8979c6c9c60abd7760ce29
link
/test integ-telemetry-k8s-tests_istio

integ-mixer-k8s-tests_istio
2ef80329adc2d69c7c8979c6c9c60abd7760ce29
link
/test integ-mixer-k8s-tests_istio

integ-multicluster-k8s-tests_istio
2ef80329adc2d69c7c8979c6c9c60abd7760ce29
link
/test integ-multicluster-k8s-tests_istio

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

@costinm: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-test_istio
2ef80329adc2d69c7c8979c6c9c60abd7760ce29
link
/test release-test_istio

integ-local-tests_istio
2ef80329adc2d69c7c8979c6c9c60abd7760ce29
link
/test integ-local-tests_istio

unit-tests_istio
2ef80329adc2d69c7c8979c6c9c60abd7760ce29
link
/test unit-tests_istio

integ-distroless-k8s-tests_istio
2ef80329adc2d69c7c8979c6c9c60abd7760ce29
link
/test integ-distroless-k8s-tests_istio

integ-security-k8s-tests_istio
2ef80329adc2d69c7c8979c6c9c60abd7760ce29
link
/test integ-security-k8s-tests_istio

integ-conformance-k8s-tests_istio
2ef80329adc2d69c7c8979c6c9c60abd7760ce29
link
/test integ-conformance-k8s-tests_istio

integ-galley-k8s-tests_istio
2ef80329adc2d69c7c8979c6c9c60abd7760ce29
link
/test integ-galley-k8s-tests_istio

integ-pilot-k8s-tests_istio
2ef80329adc2d69c7c8979c6c9c60abd7760ce29
link
/test integ-pilot-k8s-tests_istio

integ-telemetry-k8s-tests_istio
2ef80329adc2d69c7c8979c6c9c60abd7760ce29
link
/test integ-telemetry-k8s-tests_istio

integ-mixer-k8s-tests_istio
2ef80329adc2d69c7c8979c6c9c60abd7760ce29
link
/test integ-mixer-k8s-tests_istio

integ-multicluster-k8s-tests_istio
2ef80329adc2d69c7c8979c6c9c60abd7760ce29
link
/test integ-multicluster-k8s-tests_istio

lint_istio
67909248b06bd476c4532195a8d72b6f116323b8
link
/test lint_istio

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

@costinm: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
2ef80329adc2d69c7c8979c6c9c60abd7760ce29
link
/test integ-security-k8s-tests_istio

integ-telemetry-k8s-tests_istio
2ef80329adc2d69c7c8979c6c9c60abd7760ce29
link
/test integ-telemetry-k8s-tests_istio

integ-mixer-k8s-tests_istio
2ef80329adc2d69c7c8979c6c9c60abd7760ce29
link
/test integ-mixer-k8s-tests_istio

lint_istio
67909248b06bd476c4532195a8d72b6f116323b8
link
/test lint_istio

integ-local-tests_istio
67909248b06bd476c4532195a8d72b6f116323b8
link
/test integ-local-tests_istio

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

@costinm: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-local-tests_istio
67909248b06bd476c4532195a8d72b6f116323b8
link
/test integ-local-tests_istio

gencheck_istio
b5e73bbb0d1beb60f0ee77b66e1c5bbf734b6b37
link
/test gencheck_istio

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

@costinm: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

gencheck_istio
b5e73bbb0d1beb60f0ee77b66e1c5bbf734b6b37
link
/test gencheck_istio

integ-local-tests_istio
b5e73bbb0d1beb60f0ee77b66e1c5bbf734b6b37
link
/test integ-local-tests_istio

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

@costinm: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-local-tests_istio
0d6e6857dc9341817ad35a4b2837d79b8868ef2e
link
/test integ-local-tests_istio

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

/test integ-local-tests_istio


Fixes an infinite running spinner

The ApplicationRef propagates never a stable state, when in cinema mode. This is, because in the cinema.component.ts asynchronous requests are made, before the app was getting stable.
Also, interval, timeout and similar actions have the same result.

@GabrielInTheWorld Thanks.

@GabrielInTheWorld This needs some fixes.


Cannot add to ionic project

Hi,
I am trying to add this library to my ionic project, but the result of command
ionic add angular-localforage
is
Failed to find the bower component "angular-localforage".
Are you sure it exists? (CLI v1.3.21)

Your system information:

OS: Windows 8
Node Version: v0.10.33
Cordova CLI: 4.2.0
Ionic CLI Version: 1.3.21

add [name] ................................  Add an Ion, bower component, or addon to the project
                                             [name] The name of the ion, bower component, or addon you wish to install

If I run
bower install angular-localforage
I get:
bower angular-localforage#*     cached git://github.com/ocombe/angular-localForage.git#1.2.2
bower angular-localforage#*   validate 1.2.2 against git://github.com/ocombe/angular-localForage.git#*
bower localforage#1.2.0         cached git://github.com/mozilla/localForage.git#1.2.0
bower localforage#1.2.0       validate 1.2.0 against git://github.com/mozilla/localForage.git#1.2.0

Unable to find a suitable version for localforage, please choose one:
    1) localforage#1.2.0 which resolved to 1.2.0 and is required by angular-localforage#1.2.2
    2) localforage#~1.2.2 which resolved to 1.2.2 and is required by iPushPullPrefix the choice with ! to persist it to bower.json

Seems like the latest version is incompatible with latest version of localforage?

It should be, it's just that the bower.json files from this lib references localforage 1.2.0 and not ~1.2.0, which means that bower is unsure if it could work with 1.2.2. You can choose !2 to persist to ~1.2.2
And I'm not really sure why ionic add doesn't work...

Anyone from ionic interested looking into this? @perrygovier ?

Check this: https://github.com/ocombe/angular-localForage/issues/61 :)


Starting GWToolbox makes all in-game players look the same

When standing in town, all players look normal. As soon as I launch GWToolbox, all players change to looking exactly the same.
https://imgur.com/a/t0JB1
When I leave town, my character looks normal again -- but when I zone back in, I'm back to seeing everyone (including myself) look the same.
When I turn GWToolbox off while in-game, people continue to look the same, but when I zone out of town and back in, this fixes the issue.
As I am new to using this tool, is this intended functionality? Or is there a setting somewhere to turn this off? Thanks for the help.

Happy April Fools' Day!
Note: this was done in the spirit of GW's April Fools events in 2008/2009. Everything will return to normal tomorrow.

Oh geez, I feel so silly posting this then.
Thanks for the really quick response. :)


fix(python): import semantic_tokens from basedpyright

Fixes Issue #256. Initial testing shows that produces a favorable change but is difficult for me to know if it bothers any other languages other than the 4 I looked at (Python, R, SQL, Lua).

We recently set @lsp.type.variable in https://github.com/rose-pine/neovim/pull/240 to solve other issues so if we can only add the python changes I'd accept that :)

:( It will still be broke if we do just that, will need to research more and figure out a way to make it work both ways. I don't know rust but is there a correct vs incorrect example from Tom's issue that I could use while trying to work this out?

Hmm, I'd try svelte if you're familiar with starting node-related apps.

In that example, site or perhaps {site} should be coloured differently than the rest of the string which would be gold.

Also, I assume<EMAIL_ADDRESS>= {}, wouldn't fix this?

I just tested your latest suggestion and that does not work :\ I am not much of a color scheme expert. I am trying to look at other color scheme repos that are not having this issue for reference to see but there is just so many different variables and tokens that I don't know what to think anymore. Catppuccin and Tokyonight are both not facing this issue if their code makes anymore sense to you?

This local override solves the issue for me,
    require("rose-pine").setup({
      highlight_groups = {
<EMAIL_ADDRESS>= {},
<EMAIL_ADDRESS>= { link = "@variable" },
      },
    })

Latest commit fixes that single item you brought up regarding the svelte variable within string highlight but I was not sure if there were other problems/issues in svelte or other languages that created the need for the previous change(s)?

Ah that's a good solution. I'll have to double check and make sure svelte was the only outlier here this week. Appreciate the update :)

wow, none of this would have been needed if we had waited for this, sorry. https://github.com/DetachHead/basedpyright/pull/229 If you need to make any regressions because issues caused from this, just know it won't impact the python and the python type could be stripped out as unnecessary at this point.

Eh, might remove the code in the future but thank you for bringing this information back to us :)


Support MinGW-w64

This issue is mostly documenting the easiest way to build the projects in its current state on 64-bit Windows for usage on the same machine using MinGW-w64. The maintainer of this repo may want to integrate the stuff from this issue, but IMHO the right way is not to rely on makefiles, but use CMake.
To build using MinGW-w64 one needs:

a proper version of MinGW-w64. I recommend using the ones with posix threading model, otherwise C++ 11 threads won't work.
A cygwin-based environment with unix tools. You can use git-bash, which is a part of git distributions for Windows.
You need to apply the following patch for Makefile. -march=native is for building on 64-bit machines for an own machine. It was the easiest way to make it compile for x86-64 without remembering the exact arg. It doesn't necessarily imply the best performance, I have done some kind of micro-researh, it has showed that sometimes the best performance is achieved when one compiles for an ancient CPUs of the same vendor.
Also some small changes in the sources  are needed, the compiler will say you what to do in the error messages.

diff --git a/Makefile b/Makefile
index 58ece5f..14d028a 100644
--- a/Makefile
+++ b/Makefile
@@ -5,20 +5,27 @@ MANDIR ?= $(PREFIX)/share/man
 CC ?= gcc
 CXX ?= g++

-CFLAGS ?= -O2
+CFLAGS ?= -march=native
 CXXFLAGS ?= $(CFLAGS)

 LIBS ?= libuv liblz4 zlib

-SRC_CFLAGS += -W -Wall -Wextra -Wno-implicit-function-declaration -DNDEBUG=1
-SRC_CXXFLAGS += -W -Wall -Wextra -std=c++11 -Izopfli/src -I7zip -DNDEBUG=1 \
-	-Ilibdeflate -Wno-unused-parameter -Wno-unused-variable -pthread \
-	`pkg-config --cflags $(LIBS)`
+SRC_CFLAGS += -W -Wall -Wextra -Wno-implicit-function-declaration -Ilibuv/include -Ilibuv/src -Ilibdeflate/lib -Ilibdeflate -Ilibdeflate/lib/x86 -DNDEBUG=1
+SRC_CXXFLAGS += -W -Wall -Wextra -std=c++11 -Izopfli/src -I7zip -Ilibuv/include -Ilz4/lib -DNDEBUG=1 \
+	-Ilibdeflate -Wno-unused-parameter -Wno-unused-variable -pthread

 SRC_CXX_SRC = $(wildcard src/*.cpp)
 SRC_CXX_OBJ = $(SRC_CXX_SRC:.cpp=.o)
 CLI_CXX_SRC = $(wildcard cli/*.cpp)
 CLI_CXX_OBJ = $(CLI_CXX_SRC:.cpp=.o)
+DFL_CC_SRC = $(wildcard libdeflate/lib/*.c libdeflate/lib/x86/*.c )
+DFL_CC_OBJ = $(DFL_CC_SRC:.c=.o)
+ZL_CC_SRC = $(wildcard zlib/*.c)
+ZL_CC_OBJ = $(ZL_CC_SRC:.c=.o)
+LZ4_CC_SRC = $(wildcard lz4/lib/*.c)
+LZ4_CC_OBJ = $(LZ4_CC_SRC:.c=.o)
+UV_CC_SRC = $(wildcard libuv/src/*.c libuv/src/win/*.c)
+UV_CC_OBJ = $(UV_CC_SRC:.c=.o)
 ZOPFLI_C_SRC = zopfli/src/zopfli/blocksplitter.c zopfli/src/zopfli/cache.c \
                zopfli/src/zopfli/deflate.c zopfli/src/zopfli/gzip_container.c \
                zopfli/src/zopfli/hash.c zopfli/src/zopfli/katajainen.c \
@@ -34,14 +41,14 @@ ZOPFLI_C_OBJ = $(ZOPFLI_C_SRC:.c=.o)
 	$(CC) -c $(SRC_CFLAGS) $(CFLAGS) -o $@ $<

 # TODO: Perhaps detect and use system libdeflate if available.
-maxcso: $(SRC_CXX_OBJ) $(CLI_CXX_OBJ) $(ZOPFLI_C_OBJ) 7zip/7zip.a libdeflate/libdeflate.a
-	$(CXX) -o $@ $(SRC_CXXFLAGS) $(CXXFLAGS) $^ `pkg-config --libs $(LIBS)`
+maxcso: $(SRC_CXX_OBJ) $(CLI_CXX_OBJ) $(ZOPFLI_C_OBJ) $(UV_CC_OBJ) $(DFL_CC_OBJ) $(ZL_CC_OBJ) $(LZ4_CC_OBJ) 7zip/7zip.a libdeflate/libdeflate.dll
+	$(CXX) -o $@ $(SRC_CXXFLAGS) $(CXXFLAGS) $^ -lwsock32 -lws2_32 -lwininet -lpsapi -liphlpapi -lUserEnv -luuid

 7zip/7zip.a:
 	$(MAKE) -C 7zip 7zip.a

-libdeflate/libdeflate.a:
-	$(MAKE) -C libdeflate libdeflate.a

 install: all
 	mkdir -p $(DESTDIR)$(BINDIR)

I went ahead and fixed mingw support in 16d2a25.  Just use msys2 or something, similar procedure to building something like FFmpeg.  Install libraries via pacman, there's no need to compile libdeflate as a dll or similar.  Select your compiler using the shortcuts or using CC/CXX and keep -O2.
Of course, you can also use msys2 or just msvc.  I wouldn't expect better performance from mingw64.
-[Unknown]


Messenger to Discord stopped working after running a while

Two nights in a row the Messenger to Discord bridge has stopped working, while the Discord to Messenger is working just fine. I pulled your most recent update yesterday and followed up with npm install.
Error log:
info login Launching Miscord v2.6.10
info login Logging in...
info login Log level: info
info updateNotifier Checking for updates...
New version 2.6.9 available!
Changelog:
- Added switch to disable auto-renaming channels
info login Logging in to Discord...
info login Logged in to Discord
info login Got Discord channels list
info login Logging in to Facebook...
info login Logged in
(node:1340) UnhandledPromiseRejectionWarning: DiscordAPIError: Unknown Message
    at item.request.gen.end (/home/pi/miscord/node_modules/discord.js/src/client/rest/RequestHandlers/Sequential.js:71:65)
    at then (/home/pi/miscord/node_modules/snekfetch/src/index.js:213:21)
    at <anonymous>
    at process._tickCallback (internal/process/next_tick.js:118:7)
(node:1340) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 2)
(node:1340) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
ERR! listen Error: getaddrinfo ENOTFOUND 0-edge-chat.facebook.com 0-edge-chat.facebook.com:443
ERR! listen     at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:67:26)
ERR! listen  { Error: getaddrinfo ENOTFOUND 0-edge-chat.facebook.com 0-edge-chat.facebook.com:443
ERR! listen     at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:67:26)
ERR! listen   cause:
ERR! listen    { Error: getaddrinfo ENOTFOUND 0-edge-chat.facebook.com 0-edge-chat.facebook.com:443
ERR! listen     at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:67:26)
ERR! listen      message: 'getaddrinfo ENOTFOUND 0-edge-chat.facebook.com 0-edge-chat.facebook.com:443',
ERR! listen      errno: 'ENOTFOUND',
ERR! listen      code: 'ENOTFOUND',
ERR! listen      syscall: 'getaddrinfo',
ERR! listen      hostname: '0-edge-chat.facebook.com',
ERR! listen      host: '0-edge-chat.facebook.com',
ERR! listen      port: 443 },
ERR! listen   isOperational: true,
ERR! listen   errno: 'ENOTFOUND',
ERR! listen   code: 'ENOTFOUND',
ERR! listen   syscall: 'getaddrinfo',
ERR! listen   hostname: '0-edge-chat.facebook.com',
ERR! listen   host: '0-edge-chat.facebook.com',
ERR! listen   port: 443 }
Unhandled rejection TypeError: Cannot read property 'threadID' of undefined
    at module.exports.opts (/home/pi/miscord/lib/listeners/facebook.js:19:48)
    at config.facebook.client.listen (/home/pi/miscord/index.js:12:51)
    at /home/pi/miscord/node_modules/facebook-chat-api/src/listen.js:443:11
    at tryCatcher (/home/pi/miscord/node_modules/bluebird/js/main/util.js:26:23)
    at Promise._settlePromiseFromHandler (/home/pi/miscord/node_modules/bluebird/js/main/promise.js:510:31)
    at Promise._settlePromiseAt (/home/pi/miscord/node_modules/bluebird/js/main/promise.js:584:18)
    at Promise._settlePromises (/home/pi/miscord/node_modules/bluebird/js/main/promise.js:700:14)
    at Async._drainQueue (/home/pi/miscord/node_modules/bluebird/js/main/async.js:123:16)
    at Async._drainQueues (/home/pi/miscord/node_modules/bluebird/js/main/async.js:133:10)
    at Immediate.Async.drainQueues [as _onImmediate] (/home/pi/miscord/node_modules/bluebird/js/main/async.js:15:14)
    at runCallback (timers.js:763:18)
    at tryOnImmediate (timers.js:734:5)
    at processImmediate (timers.js:716:5)

EDIT: It happened again now after running for about 2 hours. A message from messenger to discord went through at 11:05, but the next message from messenger to discord at 11:20 did not. Messages from discord to messenger are still operational

It seems like your internet connection is unstable

But the Unknown Message error seems weird, can you change log level to silly?

It happened again with log set to silly now
putty.log

Damn, 12MB of logs? But again, seems like unstable internet connection.

I just took the log straight from putty after running for 9 hours.
The connection does seem to be the issue, currently using a wifi dongle as I am out of free spots in my router, will get that sorted and report back if it happens again with a wired connection.


Added power support for the travis.yml file with ppc64le.

Added power support for the travis.yml file with ppc64le. This is part of the Ubuntu distribution for ppc64le.
This helps us simplify testing later when distributions are re-building and re-releasing.

@sreekanth370 the same applies here as in https://github.com/browserify/commonjs-assert/pull/51, no?

both  applies same , kindly  merge the code with power support  architecture .

What is the purpose? This module is pure JavaScript.
This PR also removes many Node.js versions from CI which does not make sense to me.
IMO all of these ppc64le PRs are submitted with way too little explanation of what they do and why they do it.

Hey , Not sure how familiar you are with the Power architecture - primarily the bigger enterprise class systems from IBM for banking/insurance/retail/etc.etc but this ensures that your code and all dependencies are tested on the Power architecture. Debian/Ubuntu, and Fedora/RHEL/CentOS have ppc64le (Power) distributions and this code goes into those distributions. This ensures that top of tree is always validated on ppc64le using (free) Power servers at Travis CI.

There’s no value in ensuring it’s validated on that architecture when the code can’t behave differently on it,

For more info tag @gerrith3