(Re-)Added SetCoreTime() to TTigressData.h

I've re-added a SetCoreTime function to TTigressData.h, it seems to have been commented out for some reason during the recent tweaks.

This was changed because you can likely build a time from a timestamp and this should be done on the fly. When you were complaining about huge memory consumption a while ago, this is the fix for it. We are also planning on removing the data in the next couple of days, but Vinzenz is still hard at work doing this. I'll merge but this is an FYI for upcoming changes.

Sure that makes sense.

Just to clarify: I had to do this to get the current form of TIGRESS not to give an out of range error (it was looking for the time which hadn't been filled).

I had never seen Tigress in action. I was writing < 7000 events per second. With our new updates, I can push 100 k on my laptop (SSD) and 80 k on our higher performance HDD computer. So you can expect 10x the speed with 10x less disk usage. I think you guys will be happy with these upgrades in the end. Just need to squish the bugs first.

On Oct 22, 2015, at 1:29 PM, jhenderson88<EMAIL_ADDRESS>wrote:
Just to clarify: I had to do this to get the current form of TIGRESS not to give an out of range error (it was looking for the time which hadn't been filled).
—
Reply to this email directly or view it on GitHub https://github.com/GRIFFINCollaboration/GRSISort/pull/536#issuecomment-150298080.


[error]: Missing 'commonmarker ' gem for Markdown formatting. Install it with gem install commonmarker

I have commonmarker installed, and in my Gemfile.  I am running latest yard, commonmarker, rubygems, bundler, and ruby (3.3.5).
In my Rakefile, I have:
  require "yard"

  YARD::Rake::YardocTask.new do |t|
    t.files = ["lib/**/*.rb"]
    t.options = ["--debug", "--markup", "markdown", "--markup-provider", "commonmarker"]
  end

Steps to reproduce
git clone https://github.com/oauth-xx/ruby-openid2.git
cd ruby-openid2
bundle install
bundle exec rake yard

Actual Output
❯ bundle exec rake yard
[error]: Missing 'commonmarker' gem for Markdown formatting. Install it with `gem install commonmarker`

Expected Output
I expected yard to generate documentation.
Environment details:

OS: MacOS Sonoma 14.6.1
Ruby version (ruby -v): ruby 3.3.5 (2024-09-03 revision ef084cc8f4) [arm64-darwin23]
Rubygems version (gem -v): 3.5.20
Bundler version (bundle -v): Bundler version 2.5.20
YARD version (yard -v): yard 0.9.37
Relevant software dependency/versions:

commonmarker

❯ bundle info commonmarker
Running `bundle info commonmarker` with bundler 2.5.20
Found no changes, using resolution from the lockfile
  * commonmarker (1.1.5)
        Summary: CommonMark parser and renderer. Written in Rust, wrapped in Ruby.
        Homepage: https://github.com/gjtorikian/commonmarker
        Source Code: https://github.com/gjtorikian/commonmarker
        Funding: https://github.com/sponsors/gjtorikian/
        Path: /Users/pboling/.asdf/installs/ruby/3.3.5/lib/ruby/gems/3.3.0/gems/commonmarker-1.1.5-arm64-darwin

I have read the Contributing Guide.

Unfortunately, you have to use an older (< 1.0) version of Commonmarker: https://github.com/lsegal/yard/issues/1528


Hangs when given a for loop with only the initial condition and an opening curly brace

Version of JSHint being used: only 2.9.5 (2.9.4 and previous throw an exception, which is far preferable)

Input source code (simplified to only contain details necessary to demonstrate the problem):
for(var i=1){

Configuration values: Defaults

Description of expected behavior: Linting completes with a failing result

Description of actual behavior: Linting hangs indefinitely, never returning a result and locking up the interpreter

Thanks for the report! Confirmed for JSHint at version 2.9.5 and master (badc7a4). Sorry you had to downgrade; we'll try to get this fixed for 2.9.6.

Just took a quick look into this. I guess it is coming from https://github.com/jshint/jshint/commit/c083866... the previous implementation threw a TypeError because we were trying to check null.type on the return value. Now, we end up in an infinite loop in the peek(p) function because j never gets incremented in this case. I think we may be able to fix it by incrementing j before the return lookahead[j - 1];?

If you think that seems feasible @jugglinmike, I can submit a PR for this.

@jugglinmike I can work on a PR here unless you have context for an easy fix.

@johnmryan I do have that context:
It looks like we've already got this bug licked in the feature branch for the
next minor release (2.10.0). But we don't have a firm plan for that release, so
I've implemented a different fix that's suitable for our next patch
release--see gh-3231.
Sorry if this obviated any of your work, Jack. I usually try to be a little
more vocal about my work, but I've been offline since my last reply (and my
fix) in celebration of the Christmas holiday.


Using LLD

Hi, I am trying to send a Low Levewl Discovery message (data message not status). Is this possible using this library

Yes, your JSON message has to contain everything. It's pretty generic.


Few Instances stuck in "starting" state in "post-network" state forever when trying to start a service with scale=100.

Rancher Version: Build from master
Setup - 3 hosts
Rancher server and hosts have 1 vCPU, 3.75 GB.
Tried to start a service with scale 100.
About 15 instances get stuck in "starting" state in "Post-network" stage .
Instances are in this state for a very long time now - about 20 minutes.
mysql> select id,name,state,created from instance where name like "%hello%" and state="starting";
+------+---------------------+----------+---------------------+
| id   | name                | state    | created             |
+------+---------------------+----------+---------------------+
| 1664 | test216824_hello_29 | starting | 2016-03-10 16:53:34 |
| 1670 | test216824_hello_35 | starting | 2016-03-10 16:53:39 |
| 1672 | test216824_hello_37 | starting | 2016-03-10 16:53:41 |
| 1674 | test216824_hello_39 | starting | 2016-03-10 16:53:42 |
| 1675 | test216824_hello_40 | starting | 2016-03-10 16:53:42 |
| 1676 | test216824_hello_41 | starting | 2016-03-10 16:53:43 |
| 1678 | test216824_hello_43 | starting | 2016-03-10 16:53:45 |
| 1679 | test216824_hello_44 | starting | 2016-03-10 16:53:45 |
| 1680 | test216824_hello_45 | starting | 2016-03-10 16:53:46 |
| 1683 | test216824_hello_48 | starting | 2016-03-10 16:53:49 |
| 1684 | test216824_hello_49 | starting | 2016-03-10 16:53:50 |
| 1685 | test216824_hello_50 | starting | 2016-03-10 16:53:51 |
| 1687 | test216824_hello_52 | starting | 2016-03-10 16:53:53 |
| 1689 | test216824_hello_54 | starting | 2016-03-10 16:53:54 |
+------+---------------------+----------+---------------------+
14 rows in set (0.00 sec)

Repeated attempts to create instance with exit reason - "DELEGATE"

logs for one of the instance that is stuck in "starting" state -
instancelog.zip

The instances did finally get to "running" state eventually.

Tested with latest build from master.
Was able to start a service with scale 100 successfully.
No instance was stuck in "starting" state for a long time.
Also able to delete this service successfully. All the instances of the service were deleted and purged. No instance was stuck in "stopping" state for a long time.


Fix examples/gpt2_notepad.rb

Hello. @AndyObtiva
Thank you for maintaining Glimmer DSL LibUI.
I removed unnecessary sorting in the gpt2_notebook.rb example.
Thank you as always.

Thank you


Fix photo view/comments JS crash

Still need to figure out what the underlying problem is with the redux state viewingPhoto going undefined for some reason. Where the UI used to go white, please keep an eye out for other strange behavior (some part of the UI going blank or flashing, for example).

I checked to make sure the code that handles tapping a native notification and navigating to the photo view or comments view is intact... I looks good. Let's keep an eye on that once this fix is in.

Na, it's code I wrote recently. Didn't feel good about it, but hoped it wouldn't be an issue.


introduce eslint-plugin-import

Codecov Report

Merging #74 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #74   +/-   ##
=======================================
  Coverage   98.33%   98.33%
=======================================
  Files          15       15
  Lines         903      903
  Branches      182      182
=======================================
  Hits          888      888
  Misses         15       15

Continue to review full report at Codecov.

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


Switch from supervisord to systemd

Closes #73 by switching to Amazon Linux 2 and changing to systemd.
The vault.service configuration was based off of the configuration listed at the Vault Deployment Guide.
Also, I've updated README.md to indicate that its been updated to Amazon Linux 2, but there is a link to the latest public AMIs.  That list will need to be updated with new Amazon Linux 2 AMIs if this PR is accepted.
I've also updated one of the examples to also install pip as it's still required by the terraform-aws-consul modules to install supervisord.  I'm looking into updating those modules to use systemd as well, so will remove the reference to pip once I have an PR in for those modules.
update: I submitted hashicorp/terraform-aws-consul#130, but it seems like pip and boto3 is needed for the auth signing script example.  Thus, I've updated the PR to install them on Amazon Linux 2 as it seems like they're not already included.

Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement
Learn more about why HashiCorp requires a CLA and what the CLA includes
Have you signed the CLA already but the status is still pending? Recheck it.

Thanks for the PR! Im going to run the test suite

I've made the suggested changes, and also removed the creation of the /opt/vault/log folder in install-vault.

Tests are failing to fetch logs (test/vault_helpers.go:134), I'll try to have a look at that, but let me know if you have any insights

It might be because I removed /opt/vault/log in install-vault.  I'll get the tests set up on my machine this week and can look into it further.

Ok, thanks!

Oh I see, thanks!  Since the logs are using journalctl now, I'll look into updating the tests to look there instead.

I've updated the tests so that it writes out the Vault logs to a file.  I ran the TestVaultPrivateCluster example locally and it passed for both the Ubuntu and Amazon Linux 2 images.  Note that the same logs are in the syslogs, but it might be more convenient for debugging purposes to still have the separate Vault logs.

@Etiene Could you take over getting this PR passing tests and merged from here?


Error

It opens PowerShell and tries to run and then it just closes. closes. I run as Administration.  I have used this tool for a long time and just started experiencing this issue. I tried a different tool with the same concept and it works.

I think I was able to reproduce a similar issue to what you described. Here is what I did:
Running on Windows 11 24H2, latest release on IntuneWinAppUtil.exe and Win32ContentPrepTool.exe. ]

Create test.txt file with contents of "this is a test", store at D:\test.txt
Open Win32ContentPrepTool.exe (administrator does not seem to matter, issue occurred for me regardless of permissions)
Select IntuneWinAppUtil.exe (stored at C:\IWAU\IntuneWinAppUtil.exe)
Select setup file (D:\test.txt)
Select setup and output folders (both set to D:\)
Generate D:\test.intunewin
Change the setup file from D:\test.txt to D:\test.intunewin and leave all other fields unchanged
Generate Intunewin again and select Y when prompted to delete test.intunewin
powershell crashes, the only way to package a new app is to shut the app down and start a new process

Can you confirm if this sounds like the same issue you are having? A list of steps you performed and the version of windows and apps you are running with would be helpful as well.

This is not the same issue I was having. Here is a better explanation of what was happening:
After picking the setup file, folder, and output. Clicking the generate button, a PowerShell window will pop up and then close. An intunewin file would not generate and an error would not be displayed.
I just fixed my issue. I loaded up a VM and tried the tool there and it prompted me to install Windows Runtime v6.0.32. The software worked on said VM. That prompted me to run that setup on my machine which I already had, but somehow was not working. After installation, your program WORKED AGAIN!
Thank you for your help and timely response.

Good to know. I guess there was an issue with the dotnet runtime that was previously installed on your machine? Regardless, I found an unrelated bug I now need to fix lol. Thanks for letting me know.

Well, I was wrong. The issue is back. Even after doing a repair and reinstall of the.NET Runtime.

After further testing, If a folder is named "Package" as the source folder, that's where the issue lies. I even renamed it "Package1" and it still does seem to work.

I'm not sure what the issue iis having anymore. After I think I have it narrowed down, it stops working. Here is the error that is showing up.

There's a lot going on here, here's what comes to my mind:
You said earlier that the v1.0 folder is missing from your WindowsPowerShell folder, which sounds like there is an issue with the version of powershell installed on your computer.
This app is currently set to run powershell.exe through a Process.Start command. As I understand it, powershell.exe is supposed to be located at C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe, and the directory C:\WINDOWS\System32\WindowsPowerShell\v1.0\ is supposed to be in the Windows PATH variable. Does a fresh VM still seem to fix the issue?
As for the 0-error code, I believe that's an issue with the IntuneWinAppUtil.exe not being able to access the file. Is the file saved in a location that requires administrative permissions to access it? I'm not sure what permissions look like in your environment, but I save my packages in the following directory on my own pc: C:\IWAU\deploy and then I have a folder for each app deployment, like C:\IWAU\deploy\Chrome, or C:\IWAU\deploy\Zoom. I've always been able to access these folders without explicitly running the app as an Administrator, but my account is an admin so that might be something to take into account.
This is another issue I should look into, falling back to cmd if powershell fails. Both systems should be installed by default in a windows environment, but it sounds like something is different with your system that causes powershell to not launch from the C:\WINDOWS\System32\WindowsPowerShell\v1.0\ directory.

OK, i honestly do not know where to start now or how to troubleshoot this issue. I just did a complete re-install of Windows on my PC. I have administrative rights on my PC. I was using a folder that I have always used with this tool. I have used over 100 times. After a fresh install and trying the tool again, I am encountering the same issue. I tried it on the VM and am now getting the same issue.
If i just create a folder with test.txt and make that my setup and pick the folder its in, everything works. I don't know what it is about this package I am trying to setup. But it is driving me insane!

Do you think there might be a problem with specific files you are trying to package? If the setup file if corrupted or has a weird permission issue on it, that might cause an odd error to be thrown. It looks like the IntuneWinAppUtil.exe is unable to do anything with the file.
"The setup file you specified cannot be accessed." sounds like either a read/write error, a file permission issue, or a mic of the two.
Maybe check the properties of the setup file.

Make sure there aren't any wonky things going on in the permissions.


How do I Save a GridFunction created by GetSerialGridFunction?

Hi all,
I was answering a question in https://github.com/mfem/mfem/issues/3960. Initially, I thought one can use GetSerialGridFunction
and GetSerialMesh. But I am getting an wired segfault. It looks to me that GridFunction returned from GetSerialMesh does not
have a proper FESpace set.  (I got None from x.FESpace() in Python).
Looking more this, the same seems happening in c++. Below, a sample to demonstrate how I am trying to use GetSerialMesh.
Am I missing something?
#include "mfem.hpp"
#include <fstream>
#include <iostream>

using namespace std;
using namespace mfem;

int main(int argc, char *argv[])
{
   // 1. Initialize MPI and HYPRE.
   Mpi::Init();

   int num_procs = Mpi::WorldSize();
   int myid = Mpi::WorldRank();
   Mesh mesh = Mesh::MakeCartesian2D(3, 3, Element::QUADRILATERAL);
   int dim = mesh.Dimension();
   ParMesh pmesh(MPI_COMM_WORLD, mesh);

   FiniteElementCollection *fec;
   fec = new H1_FECollection(1, dim);

   ParFiniteElementSpace fespace(&pmesh, fec);

   ParGridFunction x(&fespace);
   x = 3.0;

   Mesh smesh;
   smesh = pmesh.GetSerialMesh(0);

   GridFunction sx;
   sx = x.GetSerialGridFunction(0, smesh);
   smesh.Save("serial.mesh");
   if (myid == 0){
      std::cout << myid << " : saving\n";
      std::cout << sx.Size() <<"\n"
      sx.Save("serial.gf");  // <---- segfault here
   }
   std::cout << myid << " : waiting\n";
   MPI_Barrier(MPI_COMM_WORLD);
}

One issue is that you probably should call Save just from rank 0 and similarly for saving the serial mesh. On other ranks the serial objects are just empty, I think.

@v-dobrev, calling sx.Save only from rank 0 does not help. I modified the example above, and it still segfault as follows.
It seems that FESpace is indeed destroyed (I checked by adding print statement) too early.
1 : waiting
0 : saving
16 : saving
[sshiraiw-pc:2483462:0:2483462] Caught signal 11 (Segmentation fault: address not mapped to object at address 0x180)
==== backtrace (tid:2483462) ====
 0  /lib64/libucs.so.0(ucs_handle_error+0x2a4) [0x7f5034264a54]
 1  /lib64/libucs.so.0(+0x26c2c) [0x7f5034264c2c]
 2  /lib64/libucs.so.0(+0x26dfa) [0x7f5034264dfa]
 3  /home/sshiraiw/venvs/env20220831/lib/python3.8/site-packages/mfem/external/par/lib/libmfem.so.4.6.0(_ZNK4mfem18FiniteElementSpace4SaveERSo+0x17) [0x7f5049e6e467]
 4  /home/sshiraiw/venvs/env20220831/lib/python3.8/site-packages/mfem/external/par/lib/libmfem.so.4.6.0(_ZNK4mfem12GridFunction4SaveEPKci+0x126) [0x7f5049e92056]
 5  a.out() [0x40af78]
 6  /lib64/libc.so.6(__libc_start_main+0xf3) [0x7f5047708cf3]
 7  a.out() [0x40b11e]
=================================
[sshiraiw-pc:2483462] *** Process received signal ***
[sshiraiw-pc:2483462] Signal: Segmentation fault (11)
[sshiraiw-pc:2483462] Signal code:  (-6)
[sshiraiw-pc:2483462] Failing at address: 0xa28a0025e506
[sshiraiw-pc:2483462] [ 0] /lib64/libpthread.so.0(+0x12ce0)[0x7f5047aa5ce0]
[sshiraiw-pc:2483462] [ 1] /home/sshiraiw/venvs/env20220831/lib/python3.8/site-packages/mfem/external/par/lib/libmfem.so.4.6.0(_ZNK4mfem18FiniteElementSpace4SaveERSo+0x17)[0x7f5049e6e467]
[sshiraiw-pc:2483462] [ 2] /home/sshiraiw/venvs/env20220831/lib/python3.8/site-packages/mfem/external/par/lib/libmfem.so.4.6.0(_ZNK4mfem12GridFunction4SaveEPKci+0x126)[0x7f5049e92056]
[sshiraiw-pc:2483462] [ 3] a.out[0x40af78]
[sshiraiw-pc:2483462] [ 4] /lib64/libc.so.6(__libc_start_main+0xf3)[0x7f5047708cf3]
[sshiraiw-pc:2483462] [ 5] a.out[0x40b11e]
[sshiraiw-pc:2483462] *** End of error message ***
--------------------------------------------------------------------------
Primary job  terminated normally, but 1 process returned
a non-zero exit code. Per user-direction, the job has been aborted.
--------------------------------------------------------------------------
--------------------------------------------------------------------------
mpirun noticed that process rank 0 with PID 0 on node sshiraiw-pc exited on signal 11 (Segmentation fault).
--------------------------------------------------------------------------

@kmittal2, I believe this is from https://github.com/mfem/mfem/pull/3588.
Since ParGridFunction::GetSerialGridFunction returns an object instead of a pointer, wouldn't the fespace_serial indeed be deleted at the end of https://github.com/mfem/mfem/pull/3588/files#diff-a1c11c4eae3e906589bdec42c41e2ed446e92bf76bb92e6f3ef35b5581875b8aR961-R1042?

I guess it depends on what copy constructor gets called.
If we use GridFunction sx = x.GetSerialGridFunction(0, smesh); the fespace gets copied as well.
But if we use:
GridFunction sx;
sx = x.GetSerialGridFunction(0, smesh)

only the base vector gets copied.
I feel that this behavior is bug prone.. Should we modify the method to return a pointer instead?
cc: @sshiraiwa @tzanio

Here's a summary of the issue: the code
   // ...
   GridFunction sx;
   sx = x.GetSerialGridFunction(0, smesh);
   // ...

invokes the copy-assignment operator with the r.h.s. being the temporary object returned by x.GetSerialGridFunction(0, smesh). This fails because of how we define the copy-assignment for GridFunction: https://github.com/mfem/mfem/blob/60c8f8adbfebae9beeb8c013ee11cc10407cf6b6/fem/gridfunc.hpp#L110-L117 i.e. we simply call the method: https://github.com/mfem/mfem/blob/60c8f8adbfebae9beeb8c013ee11cc10407cf6b6/fem/gridfunc.cpp#L3620-L3625 Since fes is NULL we trigger the assert (in debug mode). In non-debug mode, the Vector copy-assignment will initialize and copy the Vector sub-object of the GridFunction but any other data members will remain as initialized by the default constructor of GridFunction -- the problem then will be in the call to sx.Save: https://github.com/mfem/mfem/blob/60c8f8adbfebae9beeb8c013ee11cc10407cf6b6/fem/gridfunc.cpp#L3629 which will cause a segfault since fes is NULL.
The simplest solution is to use this code:
   GridFunction sx = x.GetSerialGridFunction(0, smesh);

In this case, the compiler is required to simply construct the object returned by x.GetSerialGridFunction(0, smesh) directly in the variable sx -- copy-assignment is not invoked. Another option is to use
   GridFunction sx(x.GetSerialGridFunction(0, smesh));

where the compiler is now required to elide the copy-constructor and construct the result of x.GetSerialGridFunction(0, smesh) directly in sx.
If I'm readying this copy-elision description correctly, the mandatory part is new in C++17 but I think even in C++11 it is still applied by compilers.
We should discuss how we want to address the issue with the GridFunction copy-assignment. If we modify the copy-assignment to do what copy-construction does (in particular, copy the fes pointer from the r.h.s.) then the code
   GridFunction sx;
   sx = x.GetSerialGridFunction(0, smesh);

will still have an issue since the fes is owned by the temporary returned by x.GetSerialGridFunction(0, smesh) which will be destroyed after the copy-assignment and that means sx.fes will point to a destroyed object.

The simplest solution may be for GetSerialGridFunction to return a pointer instead of an object. Besides backward compatibility are any other objections to it?

I will create a PR for this shortly.

One small drawback of returning a pointer to a dynamically allocated GridFunction is that users need to remember to delete the pointer when done with it.
Returning an object is also what is done in the closely related method pmesh.GetSerialMesh(0), so returning a pointer in x.GetSerialGridFunction(0, smesh) will create inconsistency.
Recently, we've had some methods/functions added to MFEM that return objects, e.g. Mesh::MakeCartesian3D (and the lower dimensional versions) and Mesh::MakeRefined. I think using this type of construction is a bit more inline with what's currently considered a better practice. Maybe @pazner can chime in, as he added the Mesh methods I mentioned.

I'm just catching up on this… I think the solution is to write move constructors and assignment operators for GridFunction. That will guarantee that in the case of
sx = x.GetSerialGridFunction(0, smesh);

the move assignment operator is called (and not the copy assignment). The move assignment operator should then transfer ownership of the collection and space to the moved-to grid function.
Maybe we can do a bit of an overhaul on the ownership semantics here. Here is a prototype branch that uses "rule of zero" for GridFunction. The idea is to avoid defining destructors and copy/move constructor/assignment operators, and instead relying on the default defined ones to do the right thing. I believe this branch should fix the issue mentioned here (but it is not 100% the same as current behavior in MFEM: for example, in this version, t_vec will be copied, where as currently it is not — this can be fine-tuned if needed).


Override isSameFile to fix Java compilation

Fixes https://github.com/sbt/zinc/issues/832
When calling compile task from sbt on a Java-only project it currently fails with
[error] java.lang.IllegalArgumentException: Not supported: WrappedJavaFileObject[${BASE}/testing/agent/src/main/java/sbt/FrameworkWrapper.java]

Not sure why scripted doesn't catc this.
This commit fixes the problem.

To validate this pull request against other sbt modules, please visit this link.


Some assets are not shown in explorer

Asset id between 1.3.128 to 1.3.319 is not shown asset explorer. (mostly start with C and D)

has anybody looked into this? is this issue still present?

Yea it's simply due to the asset lookup api call limiting us to 100 assets at a time, we either need to add some logic to fetch assets alphabetically until we've got them or all, or instead we could simply not show all assets and only present the user with a search field and then let them "bookmark" assets if desired for example.


Adding DOBA Fakultet

@predra6 Thank you for your patience while waiting for a review and processing your request. Pull request merged. Thank you!


Strange effect

Bit of a weird set of errors. Not sure it is anything to do with this integration (probably not) but more due to the crappy VW software:
If I change the charging mode, immediately, the integration gets unavailable data
to resolve this, I have to log into the ID site again (on a PC - not the ID app), change some contact details in the profile, delete the integration and re-load it. all is working then
Secondly, the switch to charge the car (when the car is set to timer) doesn't work. Again, I'm not sure that this is a VW thing as their logic is that if the car is set to timer, then you shouldn't be able to start charging manually.
There is no option with the API to switch from timer to manual as far as I can see.

Changed my Charging Settings via App. Integration comes unavailable.
Reloded Integration several times (~10 until 15 Minutes) and its working now again.


Add support for Laravel 9

Laravel 9 requires
illuminate/support ^9.0
php ^8.0
Updated the composer.json file

Hi, this would be fantastic if it can be merged!

@orobogenius thank you very much!


Revert "Refactored sidenav css to accommodate btns better"

Proposed changes

This PR reverts commit bafde665e7b600fc273d0b00596aa52860109206 because it breaks sidenav style.
It is better to understand the motivation for his change, but I don't have any way because this commit doesn't associated to any issues or pull requests, so I decided to simply revert.
Screenshots (if appropriate) or codepen:
In https://materializecss.com

Current

After this change

Types of changes

[x] Bug fix (non-breaking change which fixes an issue).
[ ] New feature (non-breaking change which adds functionality).
[ ] Breaking change (fix or feature that would cause existing functionality to change).

Checklist:

[x] I have read the CONTRIBUTING document.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.

on the other story, Forms > Chips also have weird underline on the input field, while on the materializecss.com not... 😟

Ugh... it seems to come from this change.
https://github.com/Dogfalo/materialize/pull/6313/files
I'm appreciate if you create this issue.

@Smankusors I created the PR now! 🎉 https://github.com/materializecss/materialize/pull/34

This looks great! Very appreciated <3

This looks great! Very appreciated <3

Thanks for the feedback. Keep in mind that you can also do a review as member of the members group.


Please, add our emails next to our names, mine is<EMAIL_ADDRESS>Due to problems with Yttan's GitHub account, please, add his information:
a. Database: Participación de deportistas en eventos deportivos internacionales autorizados por el IPD.
b. Information: The data corresponds to the list of participations of athletes from the different National Sports Federations and Sports Associations, in international sporting events authorized by the IPD.
c. Interest:I would like to know the Peruvian participants in international tournaments, measure their performance in the competitions and analyze factors of each federation that explain these results.
s. Link: https://www.datosabiertos.gob.pe/dataset/participación-de-deportistas-en-eventos-deportivos-internacionales-autorizados-por-el-ipd


Remove engine image dependency of v2 volumes

https://github.com/longhorn/longhorn/issues/7157

Closed and reviewed in https://github.com/longhorn/longhorn-manager/pull/2371/commits


Topic link in search results should always go to "near:" narrow

Currently, clicking on the search result topic (or the recipients in a PM thread) takes you to the message if it's been read. However, if it's unread, it takes you to the latest read message, which can be very confusing.
Instead, the topic/PM recipients link in search results should just be a "near" link to the message, same as the timestamp. From a technical perspective, we should:

Change the recipient bar links when in a search view (!filter.supports_collapsing_recipients(), specifically) to be the same as the timestamp link.
Apply the same change to the S ("Narrow to topic or PM conversation") keyboard shortcut as well.

Note that "near" views don't mark messages as read, and we show a banner explaining this and allowing the user to mark messages as read.
CZO discussion
Blockers for integration:

[x] https://github.com/zulip/zulip/issues/24226

@zulipbot claim

still working on it :)

We how changed clicking on the message body in search results to go to the near: link (instead of opening the compose box), which may address the UX issue here.

Closing for now; we can reopen if this comes up again.


[Coverage] Issues with upgraded solidity versions and solidity-coverage

Before you start work
Please read our contribution guidelines and if there is a bounty involved  please also see here
If you have ongoing work from other bounties with us where funding has not been released, please do not pick up a new issue.  We would like to involve as many contributors as possible and parallelize the work flow as much as possible.
Please make sure to comment in the issue here immediately after starting work so we know your plans for implementation and a timeline.
Please also note that in order for work to be accepted, all code must be accompanied by test cases as well.
User Story
As a developer I would like to be able to easily see any changes in coverage from my commits
Why Is this Needed?
Summary:  After upgrading to newer version of solidity-coverage and solidity our coverage environment is failing tests that are passing otherwise.
Description
Type: Bug
Current Behavior
Coverage environment fails tests that pass in test environment
Expected Behavior
Coverage and tests to line up
Reproduction
See https://travis-ci.org/MARKETProtocol/MARKETProtocol/builds/379755479
Definition of Done

[ ] Revert errors resolved in coverage run

Additional Information
failing with coverage network
Running: node --max-old-space-size=4096 ../node_modules/.bin/truffle test --network coverage
Contract: OrderLib
19) Orders are signed correctly
> No events were emitted

Contract: OrderLib Orders are signed correctly:
Error: VM Exception while processing transaction: revert
at Object.InvalidResponse (/app/node_modules/truffle/build/webpack:/~/web3/lib/web3/errors.js:38:1)
at /app/node_modules/truffle/build/webpack:/~/web3/lib/web3/requestmanager.js:86:1
at /app/node_modules/truffle/build/webpack:/~/truffle-provider/wrapper.js:134:1
at XMLHttpRequest.request.onreadystatechange (/app/node_modules/truffle/build/webpack:/~/web3/lib/web3/httpprovider.js:128:1)
at XMLHttpRequestEventTarget.dispatchEvent (/app/node_modules/truffle/build/webpack:/~/xhr2/lib/xhr2.js:64:1)
at XMLHttpRequest._setReadyState (/app/node_modules/truffle/build/webpack:/~/xhr2/lib/xhr2.js:354:1)
at XMLHttpRequest._onHttpResponseEnd (/app/node_modules/truffle/build/webpack:/~/xhr2/lib/xhr2.js:509:1)
at IncomingMessage. (/app/node_modules/truffle/build/webpack:/~/xhr2/lib/xhr2.js:469:1)
at endReadableNT (_stream_readable.js:1054:12)
at _combinedTickCallback (internal/process/next_tick.js:138:11)
at process._tickCallback (internal/process/next_tick.js:180:9)

Passing in same CI run
docker-compose exec truffle truffle test
Contract: OrderLib
✓ Orders are signed correctly (254ms)

Hey Phil, is this issue still open? I'm an experienced solidity dev currently working in LA but from Boulder. I have some work I've done on Liquid Democracy on Github, but most of my recent work has been in private repos. Hoping you might have an open issue where I can demonstrate skills.

@captnseagraves -- Hello 👋
Thanks for your interest in MARKET Protocol. Looks like this issue is still open, so feel free to jump onto it.
BTW this issue also has 0.15 ETH bounty attached to it. You can use Gitcoin in order to claim the bounty in case you aren't familiar with it. I'd recommend clicking Start Work before actually working on it, so that the bounty is reserved for you, as long as you deliver.
Feel free to join our Discord channel. You can always reach out to either me or @pelsasser in case you ever have any questions :)

Hey Phil, is this bounty still open? It appears tests are passing on Travis CI (or perhaps I misunderstand what I'm looking at). I'm an experienced solidity dev currently working in LA, but originally from Boulder. I have some work I've done on Liquid Democracy on Github, but most of my recent work has been in private repos. Hoping you might have an open issue where I can demonstrate skills.

@captnseagraves - thanks for wanting to lend a hand! your photo profile pic looks very familiar.
Please LMK if you need more help, looks like @cryptomental gave you a pretty good run down on the issue via discord, so if you still have questions feel free to reach out.

@pelsasser The issue seems to be a versioning issue with solidity-coverage which requires contract compilation with solc >= 0.4.21.

I'm happy to go through your contracts and revise the pragma to get the issue resolved, but I'm guessing you upgraded solidity versions to get the new revert messaging and array benefits and will want to think about your next move. Let me know how you would like to proceed!
Also, I'm the original organizer of EthBoulder and attended pretty much all of the Denver/Boulder meetups before moving to LA for my current role. So we've probably seen each other around :)

Yea, we recently upgraded to 0.4.23 - I think we can downgrade for the time being until solidity-coverage catches up if that solves the issues.
Let me know if that does solve the issues and we can make the call.
re: EthBoulder, awesome, I am helping Kevin and Mike organize Boulder Blockchain these days.   Hope you stick around MARKET Protocol and lend a hand!

Aha, they confirmed the issue, mocks must be used instead.

Ok

This will be fixed with #88 .


ondatra.go:56] PushConfig unimplemented

Hi,
I did git pull today morning and unable to run scripts now due to error "ondatra.go:56] PushConfig unimplemented".
It was working before the git pull.
I have debugged the issue further and it shows getting error at below point. It looks like we are trying to execute reset on dut instead of ate.
Is this due to changes pushed in  topologies/binding/binding.go ??? (https://github.com/openconfig/featureprofiles/pull/206)

Error:
F0607 11:51:04.651470  544968 ondatra.go:56] PushConfig unimplemented
Thanks,
Prabha

Hi @cprabha Thanks for the heads up! Didn't realize PushConfig() is unimplemented. You can still run the scripts by setting the pushConfig variable to false in staticBind: https://github.com/openconfig/featureprofiles/blob/main/topologies/binding/binding.go#L44

Hi @Ankur19
Thank you. I have topology where dut and ate both are present. If I disable pushconfig will it work for ate ?
Please suggest.

Yes! @cprabha the staticBind.pushConfig variable is only for DUTs and not for ATEs.

Thank you @Ankur19 .
I will try with pushConfig flag set to false.

This should be fixed by #225 . Let @Ankur19 know if it's still not fixed.


Smarter metrics caching

LXD servers keep a cached copy of the metrics for 15s to handle multiple scrapers. Since prometheus scrapes every ~15s by default, one risks getting the same results twice because the scrape interval has some jitter added to spread the load.
To mitigate that issue, our doc recommends overriding the job's scrape interval to be 30s. The problem with that is the resulting LXD metrics are then harder to correlate with metrics from other jobs using the default 15s. Because of that, I think it would be desirable to slightly modify the caching behavior of LXD's metrics. I'd propose:

when the cache is (re-)populated, note who's the "initial requestor" (either the IP, Unix UID or TLS fingerprint)
cache the resulting metrics as normal
when a cached copy is about to be used, check if:
3a) "requestor" == "initial requestor": build a new cache, overwrite the old one and serve the fresh copy
3b) "requestor" != "initial requestor": serve the cached entry

This way, a returning scraper will always have fresh data but multiple scrapers won't cause new metrics to be collected unless the data is actually stale (>15s).
Another way to put it, is that any prometheus scrape interval will work and for the multiple scrapers scenario, they will have up to 15s old metrics.

I'm not sure that I like that so much, a prometheus gone wild can hit LXD in a loop and create a massive amount of load which doesn't seem desirable.
If our concern is compatibility with the 15s scrape interval, then reducing our cache to 12s or so is likely the better option here.

I've seen recommendations on using a scrape interval between 10-60s as recommended (and a maximum to avoid going above of 2m) so I think if are to lower the duration we should go with ~8s, what do you think?


Sync with latest version of the upstream lib

Current version is 0.6.0. See https://pkg.go.dev/golang.org/x/sync/singleflight?tab=versions.

ping

btw why do you reimplement the whole thing instead of "just" wrapping sync/singleflight? I think that would be easier?

@karelbilek Thank you for your suggestion. The current implementation suits my purposes better.


WebUI: 'pre' as variable name not allowed in script test environment

If the following ReGa script is executed in the WebUI "Skript testen" environment no valid reply is returned:
WriteLine("before");
string pre = "pre is not allowed";
WriteLine(pre);
WriteLine("after");

Replacing the pre variable name with something else (e.g. pre2) will make the script running properly.
Reference:
https://homematic-forum.de/forum/viewtopic.php?f=26&t=37971&start=60#p372559

Please note, that after some investigation, it seems that the issue is related to the tclrega.so TCL<>ReGa interface. Somehoe, the following tcl script results in the same error being returned if directly executed on a CCU:
#!/bin/tclsh
load tclrega.so

if { ![catch {array set result [rega_script {
  string pre="Hello";
  WriteLine(pre);
}]}] } then {
  puts $result(STDOUT)
  return
} else {
  puts "ERROR returned"
}

As soon as the variable is chaned from pre to pre2 this perfectly returns Hello as a valid output.

After more investigation, I think I found the root cause of the issue. It it located in the used xmlparser library tclrega.so is using (libxmlparser.so). In this library a minor bug resulted in returning an error in case a small letter <pre> tag was used since it expected it to end with an uppercase </PRE>. After having fixed that issue the WebUI is able to perfectly use string pre in a homematic script.


HmrState decorator does not accept new value during set operation

Given component below:
export default class AppComponent implements OnInit {
  @HmrState() state = {
    counter: 1
  };

  // when object's property is mutated, updated value is persisted
  mutateInPlace() {
    this.state.counter = this.state.counter + 1;
    // at this point this.state.counter equals to 2; hmr works
  }

  // when variable is reassigned with new value (in favor of immutability), it's being discarded
  assignNewInstance() {
    this.state = {
       counter: this.state.counter + 1;
    };
    // at this point this.state.counter is still 1; weird; hmr does not work
  }
}

Most likely the issue comes from HmrDecorator.ts.
if (!currentValue) {
  HmrStore._initialValues[key] = newValue;
} else {
  newValue = Object.assign(newValue, currentValue); // << overwrites new value with old one??
}
return HmrStore.set(key, newValue);

I guess, it should have been as follows:
newValue = Object.assign({}, currentValue, newValue);

I removed this and exposed the api. here's an example
https://github.com/AngularClass/angular2-seed/blob/e5c2c3c2b8d8a96420d59d21f8e040a8f9d634c1/src/main.browser.ts#L34...L51


Filehandler ui integration

The problem relating path should be fixed, as long as main.py is launched from within the ddh directory.

Good job, go ahead and merge.


Fix the bug in executing aggregate queries

Description
Fixes the bug in the connector in executing Aggregate SOQL queries happened due to error in data binding
Fixes https://github.com/ballerina-platform/ballerina-extended-library/issues/542
One line release note:

Fix the bug in executing aggregate SOQL queries

Type of change
Please delete options that are not relevant.

[x] Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[ ] testQueryWithAggregateFunction

Test Configuration:

Ballerina Version: 2201.7.1
Operating System: Ubuntu 22.04
Java SDK: Java 11

Checklist:
Security checks

[x] Followed secure coding standards in http://wso2.com/technical-reports/wso2-secure-engineering-guidelines?
[x] Confirmed that this PR doesn't commit any keys, passwords, tokens, usernames, or other secrets?

@sachinira Shall we do the connector version bump also with this PR?


How remap [

I'm using a Swedish keyboard where [ is mapped to AltGr-8 by default and I would like to map it to some easier key combo.
Trying [ = G-8 for example to just map it to the å-char, but it does nothing. How can I map this?

Darn, this works, but not in gnome-terminal for some reason.

Please see the unicode section in the man page.

Hmm, not sure I follow. I do not have a unicode char at the right hand side. It does not matter if I try to remap some other key to G-8, it will just print 8 and not [.
For example: u = G-8 works, but not in gnome-terminal, what could be different about that app?

Does this work if you hit altgt manually? My advice would be to use keyd's unicode mechanism to bypass the X keymap altogether.
E.G
[ = å

though you will need to symlink the shipped XCompose file.

I think I have found out why gnome-terminal does things differently, it's because I run Wayland.

If I press AltGr-8 normally it prints [

To clarify, pressing rightalt (altgr) + 8 works in gnome terminal, but pressing u (bound to G-8 in keyd) doesn't? If so, I am inclined to considered this a bug. It may be related to a similar race condition in gnome found in #184.
How are you setting the keymap? Using setxkbmap? My understanding is that gnome does weird things and doesn't properly obey the likes of xkbmap across all applications.

Closing due to inactivity. Feel free to reopen it.


Provide metrics for top N package storage "hogs"

What's the problem this feature will solve?
Miroring PyPI currently takes > 2TB of storage, and that is continuing to grow, some mirroring tools have the ability to blacklist projects from being mirrored, but it's difficult to know which projects should be targeted for blacklisting without insight into which packages take up the most space.
Additionally, as operators it can be useful to see if particular packages are consuming more or less of the total space used by PyPI.
Describe the solution you'd like
Add metrics that indicate the top N packages by total space used.

Maybe we should go the generic https://pypi.org/stats/ and add more over time starting with this one.
Lets start with:

Estimated total size of all projects
Top 100 projects
-- Example query: https://www.irccloud.com/pastebin/VVMUqkIc/

I would be highly appreciative of a blacklist that has the biggest 100 projects. This would probably save a ton of space.

This is live - Just tweaking some cache config:
https://pypi.org/stats/

Is there anything left to do for this issue or shall we announce it on distutils-sig and close the issue?

@brainwane I think this is done!

Yeah the initial stuff is all done here. I may add more stats one day.

https://pypi.org/stats/

hmmm I guess there is an open question. do we want to commit to keeping this around by documenting it? both where to find it and the alternate JSON representation available when sending Accept: application/json?

The question basically boils down to if we want this to be an interim/internal solution for bandersnatch users... or "own it" until we create a better replacement endpoint.

I'm happy to document it.

Where should it go?
Which API documentation should I model this off?

What does "own it" mean? I don't have preference where the API endpoint is. This was @dstufft's suggestion as to where to put it. What are the alternatives you're thinking?

The endpoint is useful primarily for bandersnatch users and other mirror clients. If we document it and "publicize it" we'll want to ensure that it continues working until we begin and complete the process of deprecating it. Additionally changes to this endpoint will have to remain backward compatible.

@cooperlees adding a page similar to https://github.com/pypa/warehouse/blob/master/docs/api-reference/json.rst is probably good!

Resolved by #5072.


[BUG] - TimeSet event issue from NgxMatTimepickerComponent

Describe the bug
I'm using inside my app the time-picker widget set to 12h format . And I'm trying to get use of (timeSet) event but it doesn't work accordingly. Every time the event is triggered, the emitted value is always set to 'AM' even if I set it to be 'PM'.
Screenshots

Desktop (if execution):

Browser:  Chrome

** Versions

ngx-mat-timepicker version: ^14.0.5
@angular/core: ^14.2.6
@angular/material: ^14.2.5
typescript: ~4.8.4

Can you set up a repo or StackBlitz demonstrating the issue, @ManuBucaciuc?

I guess there's something wrong in your code. I tried this and it logs correctly.
As LayZeeDK suggest, you should create a Blitz to reproduce the issue and post here.
I'll reopen this issue if necessary.

@LayZeeDK @tonysamperi you can find the repo which demonstrates the issue exists here https://github.com/ManuBucaciuc/Time-Picker-Issue. Thanks!

@ManuBucaciuc mate, the example got to be a playable one, as already said you should put the code on a Blitz (stackblitz.com).
Cheers

@tonysamperi and here is the Blitz: https://stackblitz.com/edit/angular-ivy-sfjkm8?file=package.json,src%2Findex.html,src%2Fapp%2Fapp.component.ts,src%2Fapp%2Fapp.component.html,src%2Fapp%2Fapp.module.ts
All the best.

@ManuBucaciuc mmm interesting, I made the same test and it worked. I'll investigate further!

You're missing the binding on the input.
If you don't link an input, the picker doesn't have the model reference...

@tonysamperi let me give you the full picture. I'm trying to implement a custom component inside my app that gives my clients the possibility of both typing (by adding a pattern validator for my control: this.control.addValidators(Validators.pattern(RegexPatterns.AM_PM_TIME_FORMAT)); and also using mask="00:00 SS") and time selection using <ngx-mat-timepicker> dialog (opens at matSuffix icon click). The thing is, once I bind the ngxMatTimepicker to input, I lose the typing ability (or at least, reading the documentation I didn't find any useful properties that helps me achieving the wanted behavior -- I did use disableClick property but with no effect).
Also, by binding both mask and ngxMatTimepicker to the input I'm facing the following error More than one custom value accessor matches form control with unspecified name attribute..
So, in order to make my wanted behavior work I just had to add one new extra input that is binded to my timePicker and if value changes I just update my control (my custom timepicker component also extends an ValueAccessorBase abstract class that implements ControlValueAccessor).
Even my solution works as wanted, I'm not 100% percent sure if it's the right approach. Any recommendation will be much appreciated.
Is there any specific reason why we must bind the timePicker to an input in order to work accordingly? While testing without my timePicker being  bind to an input, the value emitted by (timeSet) has the correct hours and minutes and only the AM/PM format is not set accordingly.

@ManuBucaciuc this library was born to prevent the users from typing, especially for mobile. If you want your users to type, why bothering adding an extra dependency?
I don't see the point in having 2 input modes.
ANYWAY
I understand what you're trying to do, but this library simply wasn't born in a way that allows what you're looking for (and btw I didn't design the base architecture, I simply improved some parts).
FINALLY
I spent 30 seconds thinking about your use case and had a very easy workaround.
But since this is not stackoverflow I don't want to take from you the pleasure of finding the solution.
Cheers

Hi @ManuBucaciuc
TL;DR you can bypass the issue by adding the "format" parameter on the picker
<ngx-mat-timepicker (timeSet)="updateTime($event, 'selectedTimeFreeInput')"
                                    #pickerH></ngx-mat-timepicker>

LONG STORY IF YOU'RE INTERESTED
I was digging into your problem, because after thinking about it, the error didn't make sense.
And actually the event doesn't work as I thought (it actually works with observables). I assumed that your blitz started working after linking the picker but it actually wasn't that.
There's a fundamental problem, which is the ability to set options both on the input and on the picker itself.
BUT.
While on the directive you get defaults, you don't get them on the picker.
And that is a big african pine cone in the arse (this is a quote from some cartoon I saw, don't worry if it doesn't make sense to you 😂).
So I'll need to actually fix this...and then I'm quite inclined to remove all the params from the directive side of the moon.
But for now I'll just find the missing initializer and fix it.
Cheers

Fixed in v14.0.6

@tonysamperi Thank you mate. For discussions, investigations, solution and fix.
Take care


plugins/prometheus.md: fix typo

Hi @bbigras, thanks for fixing 🙂

You're welcome. I :heart: kubenav.


__popcnt not declared with mingw-w64 in bitops.hpp (line_descriptor modul)

Hi,
building with mingw-w64 leads to the error:
__popcnt is not declared in this scope

The error seems to be in the ifdef block in bitops.hpp:
#include "precomp.hpp"
#ifdef _WIN32
# include <intrin.h>
# define popcnt __popcnt
# pragma warning( disable : 4267 )
#else
# define popcnt __builtin_popcount
#endif

#define popcnt __builtin_popcount after the last #endifsolves the problem.
Possible solution:
#if defined _WIN32 && !defined __MINGW32__
# include <intrin.h>
# define popcnt __popcnt
# pragma warning( disable : 4267 )
#else
# define popcnt __builtin_popcount
#endif

I had the same problem. It is because I do not have Visual Studio installed.
This fixed the problem for me:
#ifdef _WIN32
// # include <intrin.h>
# define popcnt __builtin_popcount
// # pragma warning( disable : 4267 )
#else
# define popcnt __builtin_popcount
#endif

Or remove it in total and just use:
# define popcnt __builtin_popcount

#if _MSC_VER >= 1600

To check if using Visual Studio compiler:
https://msdn.microsoft.com/en-us/library/b0084kay.aspx

Should be fixed in #370


SST NextJs deploy fails while creating server bundle

Hey guys, so I want to deploy a NextJS app but when I do, I get the following error:
Building server function: default...
node:fs:2982
  handleErrorFromBinding(ctx);
  ^
Error: ENOENT: no such file or directory, copyfile 'app/.next/standalone/apps/nextjs/.next/server/pages/404.js' -> 'app/.open-next/server-functions/default/apps/nextjs/.next/server/pages/404.js'
    at copyFileSync (node:fs:2982:3)
    at file:///Users/philip/.npm/_npx/f49d1554d84e9da9/node_modules/open-next/dist/build/copyTracedFiles.js:123:13
    at Map.forEach (<anonymous>)
    at copyTracedFiles (file:///Users/philip/.npm/_npx/f49d1554d84e9da9/node_modules/open-next/dist/build/copyTracedFiles.js:94:17)
    at generateBundle (file:///Users/philip/.npm/_npx/f49d1554d84e9da9/node_modules/open-next/dist/build/createServerBundle.js:100:5)
    at createServerBundle (file:///Users/philip/.npm/_npx/f49d1554d84e9da9/node_modules/open-next/dist/build/createServerBundle.js:66:11)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async build (file:///Users/philip/.npm/_npx/f49d1554d84e9da9/node_modules/open-next/dist/build.js:49:5) {
  errno: -2,
  syscall: 'copyfile',
  code: 'ENOENT',
  path: 'app/.next/standalone/apps/nextjs/.next/server/pages/404.js',
  dest: 'app/.open-next/server-functions/default/apps/nextjs/.next/server/pages/404.js'
}
Node.js v18.19.1

I looked into app/.next/standalone/apps/nextjs/.next/server/pages and this is the directory tree I have:
├── 401.html
├── 401.js.nft.json
├── 404.html
├── 404.js.nft.json
├── 500.html
├── 500.js.nft.json
├── _app.js
├── _app.js.nft.json
├── _document.js
├── _document.js.nft.json
├── _error.js
├── _error.js.nft.json
├── acl.html
├── acl.js.nft.json

Let me know if you need any more info
Any help is appreciated thanks!

So I found the solution, by adding the latest version of OpenNext:
const nextJS = new sst.aws.Nextjs("MyApp", {
            openNextVersion: ["3.0.5"],
            link: [database],
        })

Hope this helps someone out!


batch-response duplicates Resource.id in Bundle.entry.response.id

Describe the bug
When I create a number of resources at once via the "batch" endpoint, I notice that the responses have the corresponding resource ids in the response.id
This is mostly fine, but I believe there is a chance for these ids to conflict if you create two different resources with different types but the same ids.
I'm not sure what value there is in setting this field to begin with, so my recommendation is to remove it from the response.
Alternatively, we could set these to the internal resource id of the specific version of that particular resource (like we do in the history API).
Environment
Which version of LinuxForHealth FHIR Server?
To Reproduce
Steps to reproduce the behavior:

create a bundle of type batch with PUT entries for multiple resources with the same id
post the bundle to the server
note that the response contains multiple entries that each have the same response.id

Expected behavior
Element.id values are supposed to be unique within the resource
Additional context
transaction-response may have the same issue; not sure
we used to do this in a number of other spots as well (e.g. search response bundles and history response bundles), but those have been fixed:

in the search-response case, this element has been removed
in the history-response case, I believe that the ids are still present but they are set to the internal resource id (which is always unique to a particular version of a particular resource)

Robin supports adding the internal resource id to these entries.  That sort of makes these part of our public contract, but we already went there with our 'nextId` and 'previousId' paging parameters.


chore: remove js dep and added wasm build ci

fix https://github.com/media-kit/media-kit/issues/853 and added ci to ensure its working
now it doesnt work since full screen and clear are not found, nor can i figure out the blob new syntax

I'm waiting on this.  Please fix.

I don't know the migration for the mentioned problems I left the pr for other people to fix the rest of the problems and if I got time to fix it myself, but no promises.

i cant figure how to migrate media_kit/lib/src/player/web sadly

I don't know the migration for the mentioned problems I left the pr for other people to fix the rest of the problems and if I got time to fix it myself, but no promises.
will wait for dart-lang/web#259 (comment) for fullscreen part, for the rest of the stuff research is still needed

that item fixed on web 1.0.0

I don't know the migration for the mentioned problems I left the pr for other people to fix the rest of the problems and if I got time to fix it myself, but no promises.
will wait for dart-lang/web#259 (comment) for fullscreen part, for the rest of the stuff research is still needed

that item fixed on web 1.0.0

i already did the full screen part and blob in the last commits

hello? what is taking so long?

The migration for the web player is not easy @alexmercerind if you can help with that that will be awesome

Honestly, you would be one of the few with wasm support. A lot of packages have no support for this yet, so it seems.

Honestly, you would be one of the few with wasm support. A lot of packages have no support for this yet, so it seems.

The migration is not the same for every package, so yeah it will take a while to migrate the web player correctly and accurately

@TheComputerM i reverted the changes for the player and fixed merge conflicts, this pr now only includes changes for the video player controller and the other files leaving the backend for the player for you

@TheComputerM i reverted the changes for the player and fixed merge conflicts, this pr now only includes changes for the video player controller and the other files leaving the backend for the player for you

Alright, I'll make the changes required after this PR gets merged.

I tested the changes on
https://pub.dev/packages/universal_video_controls/
And it works correctly there I can test again to be sure, but it should work anyway

I tested the changes on https://pub.dev/packages/universal_video_controls/ And it works correctly there I can test again to be sure, but it should work anyway

Can you credit media_kit more appropriately in the package e.g. hyperlinks etc.

I tested the changes on https://pub.dev/packages/universal_video_controls/ And it works correctly there I can test again to be sure, but it should work anyway

Can you credit media_kit more appropriately in the package e.g. hyperlinks etc. ?

Will do, sorry

I tested the changes on https://pub.dev/packages/universal_video_controls/ And it works correctly there I can test again to be sure, but it should work anyway

Can you credit media_kit more appropriately in the package e.g. hyperlinks etc. ?

i made it a hyper link if you think of any other changes let me know

@alexmercerind should we leave the wasm ci? since it will always fail?

I was able to complete the migration to a compilable state based on this fork. How should I try and get my changes under review? I can fork the main repo and implement my changes directory, or just PR to https://github.com/abdelaziz-mahdy/media_kit/. I haven't ran the test CI but it seems to be running okay. It includes player/web, as well as HLS, etc.
@alexmercerind

I was able to complete the migration to a compilable state based on this fork. How should I try and get my changes under review? I can fork the main repo and implement my changes directly, or just PR to https://github.com/abdelaziz-mahdy/media_kit/. I haven't ran the test CI but it seems to be running okay. It includes player/web, as well as HLS, etc.
@alexmercerind

I think you can open a pr into my branch and I don't mind reviewing it and merging it to this pr, which will make full migration to wasm and will run the ci

I apologize- there might be a delay on that. I tried the test and for some reason, while the video player example appears to work, the media_kit_test project is having issues when initializing the controller. Don't wait on me for this, worse comes to worst I just PR after this is through.

I apologize- there might be a delay on that. I tried the test and for some reason, while the video player example appears to work, the media_kit_test project is having issues when initializing the controller. Don't wait on me for this, worse comes to worst I just PR after this is through.

ok will merge this pr then and you can open a new pr when you finish the migration


 My previous patch fixed the GUI crash, but also blocked the GUI ;-)
The main problem is that only the main thread can touch the GUI. Other threads must pass the calls using things like wx.CallAfter()
We needed some mechanism to notify the end of the KiCost work.
The trick used to redirect log messages wasn't enough. In fact it just redirected print because the default stream for logging is stderr, which is currently used by the progress bar. And what is worst, once you initialized a logger changing sys.stderr does nothing, because the logger has its own copy. So I delayed the logger initialization so the GUI code can use the fake stream for the logger.

I will merger this since this fix a lot of GUI issues. But GUI still needing some work.


Simplify data model

Remove Test subjects, the point of this app is not to have a complex business logic, it's just a sample to test several technologies

Canceled


Fix bug when adding errors in insert_docs.

Also, fix default values in pydantic models
WHY
When running insert_docs, errors in any document would be appended to a list of errors as a new dict {doc_id: error}. Hence the format of errors is expected to be a List[Dict[str, str]]. However, when calling _get_request_blocks, accumulated errors in older documents were appended to errors like this
if doc.status != CompassDocumentStatus.Success:
    logger.error(f"[Thread {threading.get_native_id()}] Document #{num_doc} has errors: {doc.errors}")
    errors.append(doc)

This means that errors may end up containing either Dict[str, str] or CompassDocument. Downstream, in North, they were expecting the first, and hence they would do something like error.keys() for error in errors, leading to an error like CompassDocument has no attribute 'keys'.
This PR ensures that accumulated doc errors are added in Dict[str, str] format.

LGTM too - though +1 on the test suggestion.
I have DM'ed Javi with a manual process to trigger e2e tests in compass with this change too, should serve as a good manual validation until we can find some better automated tests on this repo.

Tests are green @ankush-cohere @benrules3
https://github.com/cohere-ai/compass/pull/525


doc: build: snippets: application required snippets

Document how an application can automatically include snippets when being built.

@tejlmand Please review.

No need for @tejlmand's review here, this is only documentation and @nordicjm has already approved.


No tests for Elixir builds

There are no test for the Elixir build tool

Closing this, should be moved to a plugin per #139


Error in Node v6 after updating eslint-config-prettier to v3.1.0

After updating from v3.0.1 to v3.1.0, I see the following behavior in Node v6 with its bundled npm (v3.10.10):
echo '{"rules": {}}' | ./node_modules/.bin/eslint-config-prettier-check

Unexpected error TypeError: Cannot read property 'filter' of undefined
    at processString (/opt/code/demo/node_modules/eslint-config-prettier/bin/cli.js:78:7)
    at getStdin.then.string (/opt/code/demo/node_modules/eslint-config-prettier/bin/cli.js:37:22)
    at process._tickCallback (internal/process/next_tick.js:109:7)

Updating npm and reinstalling eslint-config-prettier-check resolves the problem. For project's using Travis CI, adding the following to .travis.yml does the trick:
before_install:
- npm install -g npm@latest

The problem doesn't occur in Node v8 or v10 (which come bundled with newer versions of npm). The problem also doesn't occur with v3.0.1 or earlier of eslint-config-prettier, even when using Node v6 and its bundled npm v3.10.10.
The root of the problem is that the metadata for v3.1.0 in https://registry.npmjs.org/eslint-config-prettier doesn't include the files key, whereas the metadata for previous versions do. The exclusion of the files key from registry metadata is consistent across other projects starting in late August. I created an npm support topic asking if this change was intentional, but it didn't receive any responses.
The reason the lack of the files key in the registry metadata results in an error when eslint-config-prettier is installed via npm v3.10.10 is because older versions of npm generate node_modules/<package>/package.json based on the metadata from https://registry.npmjs.org/eslint-config-prettier (which is missing the files key). Newer versions of npm instead create that file based on the package.json inside of https://registry.npmjs.org/eslint-config-prettier/-/eslint-config-prettier-3.1.0.tgz (which includes the files key).
Note that this problem only presents itself when eslint-config-prettier is installed as a dependency inside of another project. That's why this project's Travis build for Node v6 isn't failing.

Thanks for the thorough investigation!
It feels like npm should fix this since it's breaking change. But perhaps there aren't that many packages that read "files" from their own package.json so they don't consider it much of an issue.
I guess we can switch to a fs.readdirSync-based approach instead in the CLI as a workaround.

Do you think npm will fix it? Or is there anything we can do, like publishing a new version or something?
Would you be interested in making a PR that works around the issue?

I agree that this is something that npm should either fix or document, but I can't even make an educated guess if they'll do so. I haven't come across any mention of the registry change in docs, change logs, issue trackers, or commit histories. I'm assuming the change hasn't had any impact on most projects.
I don't think publishing a new version will fix it, and I'm not aware of any other solutions that don't involve changing code. Personally, I'm fine with just updating my project's Travis config to update npm. Maybe that workaround combined with this issue documenting the problem is a sufficient response? If not, I'm happy to submit a PR switching to fs.readdirSync.

I’ve released 3.2.0. Hopefully it fixes the problem!


Add RFS to utility API

In https://github.com/twbs/bootstrap/pull/29152, I tried combining too many things in one PR.
In this PR I just enabled the possibility to use RFS in the utility API. We 'll' see how we'll deal with the responsive font size and responsive spacing classes afterwards.

Rebased & retested this


Update to FontAwesome v5

Hello,
Thanks for creating this module, it's really useful and pretty straightforward to use.
One thing I've noticed is that the module currently uses FontAwesome v4.7.0, with the latest version of FA being v5.5.0. It'd be nice to be able to use the latest set of icons and updating the equivalence should be relatively straightforward through the cheatsheet they provide, but the download is now (I believe since 5.0) split into three .otf files - "solid", "regular" and "brands". I see there being two ways to deal with this:

Pick one of the new three to have as the main reference. The "regular" is I think meant to be the most similar to the old icons, but the "solid" is the most complete.
Keep all three and either:

Add an extra parameter to choose which of the three icon sets to use (e.g. icon_set as a string).
Rename the icon lookups to include which set they come from, and ensure the user only uses icons from one set.

I am happy to work on a PR for this based on your preference. I think 2i would work best (and might start looking at implementing it), but will defer to your judgement. There may also be some compatibility issues with name changes, but I think it's worth it for the wider set of icons available.
Thanks,
Adam

Above is a PR based around 2i from the above suggestions. It seems to work fairly well though I haven't been able to check it extensively. Here's a chart based on one of the examples given for the module and the new icon set

Generated using:
fig = plt.figure(
    FigureClass=Waffle,
    rows=5,
    values=data,
    colors=("#232066", "#983D3D", "#DCB732"),
    legend={'loc': 'upper left', 'bbox_to_anchor': (1, 1)},
    icons=['democrat', 'republican', 'person-booth'], icon_size=12,
    icon_legend=True
)


Update reset.css

Added new font for some good looks.

The reset is not here to set the font family.


Cert-manager 0.7 deprecation by lets-encrypt

I'm not sure if this is being enforced right now - but it was announced by Let's Encrypt that they would block cert renewals from cert-manager versions below 0.8 from November 1 due to potential spamming issues during retries. Kubeprod is currently on 0.7.2. I did get a renewal of a cert by kubeprod 0.7.2 in November, so perhaps the version header is different in bitnami's image leading them to still accept them.
In any event - perhaps a short term bump of cert-manager to a supported version would be a good idea (I know the most recent version 0.12.0 probably is more involved due to the introduction of CRDs).
https://community.letsencrypt.org/t/blocking-old-cert-manager-versions/98753

@EamonKeane thanks for letting us know. We will work on updating the version and resolve the issue

@EamonKeane I've just tagged BKPR 1.3.6 with cert-manager 0.12.0. The release should be up in a while. Please refer to the migration guide for pre-upgrade instructions.

great, thanks @sameersbn !

@EamonKeane I've just tagged BKPR 1.3.6 with cert-manager 0.12.0. The release should be up in a while. Please refer to the migration guide for pre-upgrade instructions.

@sameersbn
Be careful that cert-manager 0.10+ comes with a slew of changes: https://cert-manager.io/docs/installation/upgrading/upgrading-0.10-0.11/, modifying both their own manifests (CRDs, deployments, etc) and ingress annotations.
If it was for LE compatibility, latest 0.10 would be a much safer choice.


fix: esbuild use config file to ensure tsconfig

PR Details

Description

Related Issue

Motivation and Context

How Has This Been Tested

Types of changes

[ ] Docs change / refactoring / dependency upgrade
[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist

[ ] My code follows the code style of this project.
[ ] I have updated changeset
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

Good news: esbuild v0.18.0 no longer reads the jsx option from tsconfig.json.
https://github.com/evanw/esbuild/releases/tag/v0.18.0


Make a comparison of duplicate observations

Sanders informs me that there are stars with the same APOGEE_ID but different ASPCAP_ID values. We stacked and analysed everything based on ASPCAP_ID. That means we can identify duplicates of APOGEE_ID values and also use them to estimate internal precision (and covariances, as Sanders is doing for distance determination).

Clarification: It seems the APOGEE_ID and ASPCAP_ID values are different, but some stars are duplications. These can be identified by the EXTRATARG bitmask (decimal 4 value) and then internally cross-matching stars based on their positions.

Closing this since the duplicate observations are not bonafide giant stars according to our criteria in the paper.


Crash on View in Web of Trust

As a not accepted user when i click on "View in Web of Trust" for a user on the identities users list, i've a crash.
Traceback (most recent call last):
File "/Users/charles/tmp/cutecoin/cutecoin/src/cutecoin/gui/community_tab.py", line 158, in view_wot
self.wot_tab.draw_graph({'text': person.uid, 'id': person.pubkey})
File "/Users/charles/tmp/cutecoin/cutecoin/src/cutecoin/gui/wot_tab.py", line 92, in draw_graph
path = graph.get_shortest_path_between_members(person, person_account)
File "/Users/charles/tmp/cutecoin/cutecoin/src/cutecoin/core/graph.py", line 61, in get_shortest_path_between_members
path = self.find_shortest_path(self._graph[from_person.pubkey], self._graph[to_person.pubkey])
KeyError: '3fhkwCegXZKxtYb8gzgeLoALZjGRLDeNMApwcpQnC3Ff'
[1]    61568 abort
The KeyError is my public key.
Platform: Mac Os
Version: the master branch

This is probably a crash due to pyqt 5.5. Before it was not crashing so some exception were missed. Since 5.5 any exception in the qt environment will abort python..
Can you try with the dev branch ? Not so much devs and fixes will be done on master branch now since they will be most probably lost development, due to major code change between 0.10 and 0.11...

 Please can you describe step by step all the process to install cutecoin on a mac OS on the forum?
http://forum.ucoin.io
We will include this in our wiki.
Furthermore, could you try to build a binary for mac os ?

I confirm the bug. May be the asynchronous behavior of the get_certified/certifiers need to refactor the code using it...

It is still happening after last night commits ?

No. No more crash. But now, browsing in the wot display a loading circle, and it takes at least 15 seconds to update the wot...

Yes this is the time to request the network with all the data. Once data are refreshed, it's way faster, thought. (Data are downloaded only once, when the block just changed).

Is this bug fixed ? I never encountered it again for some time...

It happened again :
ERROR:main:async_exception_handler:Task exception was never retrieved
future: <Task finished coro=<draw_graph() done, defined at /home/inso/code/ucoin/cutecoin/src/cutecoin/gui/wot_tab.py:185> exception=KeyError('8Fi1VSTbjkXguwThF4v2ZxC5whK7pwG2vcGTkPUPjPGU',)>
Traceback (most recent call last):
  File "/home/inso/.pyenv/versions/3.4.3/lib/python3.4/asyncio/tasks.py", line 238, in _step
    result = next(coro)
  File "/home/inso/code/ucoin/cutecoin/src/cutecoin/gui/wot_tab.py", line 234, in draw_graph
    path = yield from graph.get_shortest_path_between_members(identity, identity_account)
  File "/home/inso/code/ucoin/cutecoin/src/cutecoin/core/graph.py", line 91, in get_shortest_path_between_members
    self._graph[to_identity.pubkey])
KeyError: '8Fi1VSTbjkXguwThF4v2ZxC5whK7pwG2vcGTkPUPjPGU'

Everytime, the user pubkey is the key missing from the dictionary.


openbsd: core dump when launching

Hi All,
Simply running gopass with the latest master, causes the app to give a coredump.
I don't have go symbols enabled, so the backtrace is useless for you.
$ gopass
Abort trap (core dumped)
$

I don't seem to have this problem on an ubuntu like system.

Are you installing via ports? Also what version of OpenBSD?

Installing via go get -u github.com/justwatchcom/gopass

OpenBSD 6.2-current (GENERIC.MP) #220: Fri Nov 17 11:47:01 MST 2017

Looks like I was a bit aggressive with the pledging. Diff shortly

@jungle-boogie can you try with this diff #473

@qbit, That's good! It works and doesn't coredump.

Should be fixed by #473


[WIP/Help] Backend/feature/user hiding/make community group tests explicit

Reopened #1094.
GitHub closed that one since I renamed the branch. I had to rename the branch, there were problems because it started with a string that was the same name as another branch.

To add more details:
I'm attempting to explicitly test hidden users in groups and communities. In the base branch (user hiding), I just added an invisible user to each group and community and assumed that if all tests are passing, everything must be OK. Less than ideal approach. However, the proximity stuff in communities has me beat. Adding users changes the results of all the tests. And then I couldn't figure out how to test GetNearbyUsers. So I figured the base branch will do for now and someone who understands this better can fix it up at some point if they feel like it.

Should we close this one too and work instead on top of the new PR?

Yes, I was going to just rebase it

@ShmuelTreiger: I'll close this PR, feel free to re-open. It's better that way so it doesn't get confusing about who the author is, etc.


[MM-38280] Fixing doc link for permalinks

Summary
Fixing link for docs
Ticket Link
https://mattermost.atlassian.net/browse/MM-38280
Screenshots

Release Note

NONE

Cherry pick is scheduled.


Multi-value aggregates

Some general remark: Could we please keep the PR's small. I know a lot of this is mechanical changes and Tests. However, it also mixes several distinct work packages. Quantiles, StreamingHist, and more. It is a lot more efficient to review functionally related packages.

LGTM high level. 👍  Were you looking to merge this to test quantiles in swoop and do a regression? Can't we do that with an artefact of this branch?

@AndreasKostler, yes will try to keep things more manageable going forward. A word of warning though, the next PR will likely be much worse than this one. We'll need to come up with a way to better manage changes in this repository. Any changes here are likely going to be quite significant due to the state of what's there.
@sujeshchirackkal, yes was hoping to merge this to evaluate new functionality. Could you email me instructions how I could do that with an artefact of this branch? Thanks.


Fix query enum error

This should fix #327. I have done limited testing with my own project locally. Enum fields can now be read in queries.

Thanks @iherger! Will take a look at this tomorrow night.

The tests are no passing on next for me, which I feel must be fixed before merging more changes in. Will be looking at this next.

@iherger Could you add a regression test? Will work toward that myself meanwhile too.


some annotation conflict with java build-in package

Hi,
I find some annotations used in jacpfx such as  @PostConstruct and @PreDestory is in the package org.jacpfx.api.annotations, but in the package  javax.annotation it also contain the @PostConstruct annotation. So I want to know what's the difference between these two annotations.
I want to integrate jacpfx into my springboot framework project. So I want to know how to operate these same name but in different package annotations.
In addition，I find a issue about springboot titled "Spring Boot support" , It's ok?
Thank you!

Hi, I had to introduce org.jacpfx.api.annotations since you can use JacpFX with many different DI containers and I wanted to avoid unwanted behavior. According to spring boot... I don't use it but there are many  people using it with JacpFX.

Sorry,I can't find your introduce about org.jacpfx.api.annotations,could you give me a link? Thank you!!!

Hi... I ment "I created org.jacpfx.api.annotations" to avoid conflicts with other DI containers. The reason is, that you can use JacpFX without Spring or with Guice,.... see documentation here: http://jacpfx.org/documentation_main.html#Annotations overview19

....Oh,But,when I want to use jacpFx in my springboot project,I will face the problem that many same named annotations but different means.How could I solve this problem.Thank you!!!

Hi, I'm not sure what you want to do... org.jacpfx.api.annotations.PostConstruct defines a Postconstruct for the JacpFX component (when it is ready to use)... If this JacpFX component is also a Spring bean (if you use it together with Spring) the javax.annotation.PostConstruct will be called when the Spring initialization is ready.... BUT you still have to wait until org.jacpfx.api.annotations.PostConstruct is called .... that are two different things. You are free to use both annotations in you component at the same time (@org.jacpfx.api.annotations.PostConstruct & @javax.annotation.PostConstruct), but they are triggered at different phases (first will be the Spring PostConstruct and than the JacpFX Postconstruct)... normally it would be enough to use the JacpFX PostConstruct...

So,I think I get it,Thank you very much.I con't find any framework for javafx in china. Thank you!!!

Have fune ;-)


Error compiling

Im using Intel MacOS Sonoma.
/Users/filipedelgado/Documents/minecraft-weekend/lib/cglm/src/vec4.c:127:25: error: argument 'v' of type 'vec4' (aka 'float[4]') with mismatched bound [-Werror,-Warray-parameter]
glmc_vec4_scale_as(vec4 v, float s, vec4 dest) {
                        ^
/Users/filipedelgado/Documents/minecraft-weekend/lib/cglm/src/../include/cglm/call/vec4.h:102:25: note: previously declared as 'vec3' (aka 'float[3]') here
glmc_vec4_scale_as(vec3 v, float s, vec3 dest);
                        ^
/Users/filipedelgado/Documents/minecraft-weekend/lib/cglm/src/vec4.c:127:42: error: argument 'dest' of type 'vec4' (aka 'float[4]') with mismatched bound [-Werror,-Warray-parameter]
glmc_vec4_scale_as(vec4 v, float s, vec4 dest) {
                                         ^
/Users/filipedelgado/Documents/minecraft-weekend/lib/cglm/src/../include/cglm/call/vec4.h:102:42: note: previously declared as 'vec3' (aka 'float[3]') here
glmc_vec4_scale_as(vec3 v, float s, vec3 dest);
                                         ^
2 errors generated.
make[3]: *** [CMakeFiles/cglm.dir/src/vec4.c.o] Error 1
make[2]: *** [CMakeFiles/cglm.dir/all] Error 2
make[1]: *** [all] Error 2
make: *** [libs] Error 2

Its some sort of cmake error, in the repository only make is supported so its a linking error where cglm has been linked multiple times prob

Any updates on this issue? I have ran into the same error and am stuck.
Running Sonoma as well.
Does anyone know what is meant by mismatched bound?

Removing -Werror from line 36 of the /lib/cglm/CMakeLists.txt file and re-running cmake on it seems to have allowed me to compile the game, though I doubt it's a best practice.

For everyony who wants to compile on Arch Linux in 2024/4:

modify the file ./Makefile:

diff --git a/Makefile b/Makefile
index 21fba7c..37775f2 100644
--- a/Makefile
+++ b/Makefile
@@ -5,6 +5,7 @@ CFLAGS = -std=c11 -O3 -g -Wall -Wextra -Wpedantic -Wstrict-aliasing
 CFLAGS += -Wno-pointer-arith -Wno-newline-eof -Wno-unused-parameter -Wno-gnu-statement-expression
 CFLAGS += -Wno-gnu-compound-literal-initializer -Wno-gnu-zero-variadic-macro-arguments
 CFLAGS += -Ilib/cglm/include -Ilib/glad/include -Ilib/glfw/include -Ilib/stb -Ilib/noise -fbracket-depth=1024
+CFLAGS += -Wno-error=implicit-function-declaration
 LDFLAGS = lib/glad/src/glad.o lib/cglm/libcglm.a lib/glfw/src/libglfw3.a lib/noise/libnoise.a -lm

Modify the file ./lib/cglm/CMakeLists.txt

diff --git a/CMakeLists.txt b/CMakeLists.txt
index 378332b..2bd0b8e 100644
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -33,7 +33,7 @@ if(MSVC)
     string(REGEX REPLACE "/RTC(su|[1su])" "" ${flag_var} "${${flag_var}}")
   endforeach(flag_var)
 else()
-  add_compile_options(-Wall -Werror -O3)
+  add_compile_options(-Wall -Werror -Wno-error=array-bounds -Wno-error=stringop-overflow -Wno-error=array-parameter -O3)
 endif()

modify the file ./lib/cglm/include/cglm/call/vec4.h:

glmc_vec4_scale_as(float v[4],  float s,  float dest[4]);

I am getting these error and many warnings while running "make". I have modified ./Makefile and ./lib/cglm/CMakeLists.txt as mentioned above.
src/block/../util/ivec2s.h:61:15: error: redefinition of 'ivec2s'
typedef union ivec2s {
              ^
lib/cglm/include/cglm/types-struct.h:85:15: note: previous definition is here
typedef union ivec2s {
              ^
In file included from src/block/air.c:1:
In file included from src/block/block.h:4:
In file included from src/block/../util/util.h:25:
src/block/../util/ivec2s.h:69:3: error: typedef redefinition with different types ('union (unnamed union at src/block/../util/ivec2s.h:61:15)' vs 'union ivec2s')
} ivec2s;
  ^
lib/cglm/include/cglm/types-struct.h:108:3: note: previous definition is here
} ivec2s;
  ^

and there are many warnings like :
src/block/../util/ivec3s.h:341:3: warning: call to undeclared function 'glm_ivec3_divs'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
  glm_ivec3_divs(a.raw, s, r.raw);


Drop Identifier#generate usage

In this PR I have dropped usage of the Identifier#generate method and replaced it with the new generated UuidValue methods introduced in base#357.
Now we should be ready to remove it completely.

@alexander-aleksandrov PTAL.


Added discord-listings

BTW thank you for suggestion. It's very good that you suggest people some ways, love you!

I've adjusted the description a bit. Thanks for the PR and thanks for the kind comment, much appreciated! :blush:


Add a user guide to run the demo of a prototype of Istio CA Vault integration

Add a user guide to run the demo of a prototype of Istio CA Vault integration.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: lei-tang
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: wattli
If they are not already assigned, you can assign the PR to them by writing /assign @wattli in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Implemented TodoModel Class for creation of 'todo' task objects

Added TodoModel class for creation of 'todo' task object.
Optimized CmakeLists.txt in src\, by removing redundant members

Can you fix the merge conflicts?

Hey, I've resolved all the requested changes except one. I hope you can explain why the method I implemented for the unique ID isnt up to par.

The commit history looks clumsy too.


Not an Issue But Just a message

I really like the concept of focusing on DX and the work. I could not find any convey this message to you guys , so writing this in an issue 😄 .
Initially I wanted to create a web page using m3 and came across https://material-web.dev/about/intro/ . Later after a bit research googling i found your amazing Osome page https://www.beercss.com/ . I initially felt like its similar to bootstarp library but following m3 design . But when i was developing my project I felt i am wrong and much more powerful than i thought .
Also like the way in which you are sharing the raw Html instead of packing it in a React Component and exposing options as props .
Once my works are done will try to contribute back here .
Few Notes :-

Your Code pin collection (https://codepen.io/collection/XydYMB?cursor=eyJwYWdlIjoxfQ==) is not that visible to the world , i was able to find this helpful resource after 2 hrs long trying to understand how to use beercss .
I think this repo could be more visible to the world by implementing other web components which the m3 doesnt provide / will not provide for web. such as Nav Bar (https://m3.material.io/)

There are many components which Google doesnt share for web and for now they are not even developing and went under maintaince so i feel that this project has the potential to fill the gap.

Feel free to close this issue after you read this . Its not an issue 😄  .
Thanks for the project .
Cheers .

Hi @UdayKiranPadhy
Thanks for the feedback, we are trying to deliver the best experience on code, mixing semantic html with some global helpers.
I guess we can combine some elements and helpers to achieve this component too (and publish this on our homepage).
All best 🍻


runtime: unexpected nil pointer dereferences since map dynamic entry changes

I wasn't sure if this belonged in runtime, cmd/go, or somewhere else -- please retitle as appropriate.
What version of Go are you using (go version)?

$ go version
go version devel +b098c0f467 Wed May 1 15:12:53 2019 +0000 darwin/amd64

Does this issue reproduce with the latest release?
This does not reproduce with go version go1.12.3 darwin/amd64.
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GOARCH="amd64"
GOBIN=""
GOCACHE="/Users/mr/Library/Caches/go-build"
GOENV="/Users/mr/Library/Preferences/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GONOPROXY=""
GONOSUMDB=""
GOOS="darwin"
GOPATH="/Users/mr/go"
GOPROXY="direct"
GOROOT="/Users/mr/gotip/src/github.com/golang/go"
GOSUMDB="off"
GOTMPDIR=""
GOTOOLDIR="/Users/mr/gotip/src/github.com/golang/go/pkg/tool/darwin_amd64"
GCCGO="gccgo"
AR="ar"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD="/Users/mr/go/src/github.com/influxdata/flux/go.mod"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/ct/bl4_z3g51ks8239_r2k07v_40000gn/T/go-build385871975=/tmp/go-build -gno-record-gcc-switches -fno-common"

What did you do?

I ran the tests for github.com/influxdata/flux:
$ cd $GOPATH/src/github.com/influxdata/flux
$ git checkout v0.28.3
$ go test ./stdlib/

What did you expect to see?
Tests passing like with go 1.12.3.
What did you see instead?
A panic:
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x20 pc=0x11d5f12]

goroutine 1 [running]:
github.com/influxdata/flux/semantic.function.MonoType(0x0, 0x20be9c8, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x203000, 0x203000, ...)
	/Users/mr/go/src/github.com/influxdata/flux/semantic/poly_types.go:498 +0x42
github.com/influxdata/flux/values.(*function).Type(0xc000181ef0, 0xc000181f20, 0x17c5edb)
	/Users/mr/go/src/github.com/influxdata/flux/values/function.go:43 +0x34
github.com/influxdata/flux/values.(*object).Set(0xc00018a9c0, 0x17c5edb, 0x4, 0x1a56d20, 0xc000181ef0)
	/Users/mr/go/src/github.com/influxdata/flux/values/object.go:105 +0x19c
github.com/influxdata/flux/interpreter.(*Package).Set(...)
	/Users/mr/go/src/github.com/influxdata/flux/interpreter/package.go:59
github.com/influxdata/flux.registerPackageValue(0x17c6f71, 0x6, 0x17c5edb, 0x4, 0x1a56d20, 0xc000181ef0, 0x2091900)
	/Users/mr/go/src/github.com/influxdata/flux/compile.go:204 +0x129
github.com/influxdata/flux.RegisterPackageValue(...)
	/Users/mr/go/src/github.com/influxdata/flux/compile.go:182
github.com/influxdata/flux/stdlib/system.init.1()
	/Users/mr/go/src/github.com/influxdata/flux/stdlib/system/time.go:14 +0x6b
FAIL	github.com/influxdata/flux/stdlib	0.027s

I bisected go to 85387aa364f5ebb8c1c10ee2de78ae8ded5a80dd as the first build where this panics. Using its parent commit, 70b890ce3b72fdab528ee1f93b1950173e9a0992, the tests pass.
Then I noticed https://github.com/golang/go/issues/31777, a separate issue filed related to that bisected commit. I tried checking out master of go (b098c0f467e5ce70b936381c439a0cbafc3316d3) and locally applying the change in https://golang.org/cl/174777, but the panic still occurred.
Unfortunately I do not have time right now to come up with a more minimal repro case.
/cc @randall77

Yes, this is a dup of #31777. I'll close this one, but the test case should be very useful.

Sounds like the proposed fix to #31777 may not handle this. Reopening until we have confirmed that this is fixed and has a test.

@randall77 @josharian the problem seems to be this line in OMAPLIT order:
as := nod(OAS, nod(OINDEX, n, r.Left), r.Right)

The old code requires a temp, so that mapassign1 can have addressable key, elem:
// Build list of var[c] = expr.
	// Use temporaries so that mapassign1 can have addressable key, elem.
	// TODO(josharian): avoid map key temporaries for mapfast_* assignments with literal keys.
	tmpkey := temp(m.Type.Key())
	tmpelem := temp(m.Type.Elem())

	for _, r := range entries {
		index, elem := r.Left, r.Right

		setlineno(index)
		a := nod(OAS, tmpkey, index)
		a = typecheck(a, ctxStmt)
		a = walkstmt(a)
		init.Append(a)

		setlineno(elem)
		a = nod(OAS, tmpelem, elem)
		a = typecheck(a, ctxStmt)
		a = walkstmt(a)
		init.Append(a)

		setlineno(tmpelem)
		a = nod(OAS, nod(OINDEX, m, tmpkey), tmpelem)
		a = typecheck(a, ctxStmt)
		a = walkstmt(a)
		init.Append(a)
	}

How can we archive the same behavior for order?

Hmmm, order.go should allocate those temporaries, the OINDEXMAP case in expr.
It should occur when we call o.stmt on the results of nod(OAS, nod(OINDEX, n, r.Left), r.Right).

@randall77 I think my CL above will fix the issue, still need a minimal example to reproduce this.

Not yet minimized, but here's some progress:
package main

import (
	"fmt"

	"github.com/influxdata/flux/semantic"
)

func main() {
        fmt.Println(semantic.NewFunctionPolyType(semantic.FunctionPolySignature{
                Return: semantic.Time,
        }))
}

This used to print () -> time, but at master it currently prints () -> <nil>.

Standalone test file:
package main

import "fmt"

type Nature int

const Time Nature = 0

var natureNames = []string{
	"time",
}

func (n Nature) String() string {
	return natureNames[n]
}

type function struct {
	ret interface{}
}

type FunctionPolySignature struct {
	Required []string
	Return   interface{}
}

func NewFunctionPolyType2(sig FunctionPolySignature) interface{} {
	return function{
		ret: sig.Return,
	}
}

func (f function) String() string {
	return fmt.Sprint(f.ret)
}

func main() {
	fmt.Println(NewFunctionPolyType2(FunctionPolySignature{
		Return: Time,
	}))
}

Used to print time; now prints <nil>.

More minimal:
package main

import "fmt"

type one struct {
	i interface{}
}

type two struct {
	i interface{}
	s []string
}

func F(x two) interface{} {
	return one{
		i: x.i,
	}
}

func main() {
	o := F(two{
		i: 42,
	})
	fmt.Println(o)
}

Should print {42}, but currently prints {<nil>}.

That's about as far as I think I have time to dig into this.
@randall77 or @cuonglm , do you mind investigating further?

@mdempsky will take a look shortly.
Sounds like it due changes in isStaticCompositeLiteral.

Just slightly more reduced:
package main

type foo struct {
	i interface{}
	_, _ interface{}
}

func main() {
	z := foo{i: 42}.i
	println(z.(int))
}

Playing with the other fields in foo seems to trigger the bug. A single anonymous interface field doesn't cause it, but two fields do. _ [1]int doesn't cause it, but _ [2]int does. It happens whether the other fields are before or after i.

@maksadbek @mark-rushakoff I'm running dist test before submit the patch.
I think my assumption is right.
The ONAME case in isStaticCompositeLiteral reports the second i: in o := one{i: two{i: 42}.i} as compile-time constant, why it shouldn't.

@mark-rushakoff with newest patch in CL, I can run the test and both examples run without panic.

Confirmed that the behavior is fixed on tip. Thank you!