Add memory DIMM status in dashboard

Is your feature request related to a problem? Please describe.
I'm missing the status for memory dimm information
Describe the solution you'd like
I would like to have information about the status of memory dimm and adding this info to the node dashboard or maybe create a general dashboard with the whole hardware information separate in different sections in the same dashboards. For example the FAN, Power, Memory,
Additional context
Example of a current similar situation

hi @faguayot not sure if you've seen the Power dashboard, but it has the fan, power, temperature information you're looking for. Would adding memory to that dashboard work for you?
We took a look and so far we haven't been able to find a ZAPI or REST endpoint that returns DIMM information. None of the system-node ZAPIs, storage-shelf-info-get-iter or environment-sensors-get-iter returns what we need.
environment-sensors-get-iter returns something like this
{
      "discrete-sensor-state": "normal",
      "discrete-sensor-value": "NORMAL",
      "node-name": "umeng-aff300-06",
      "sensor-name": "Memory0 Hot",
      "sensor-type": "discrete",
      "threshold-sensor-state": "normal"
},

but I think this is for hot swapable RAM, not the status of current memory. The response above only returns a single sensor named Memory0 Hot even though that node has four DIMMs
system controller fru show -node umeng-aff300-06 -subsystem Memory
Node               FRU Name                     Subsystem          Status
------------------ ---------------------------- ------------------ -----------
umeng-aff300-06    DIMM-4                       Memory             ok
umeng-aff300-06    DIMM-1                       Memory             ok
umeng-aff300-06    DIMM-3                       Memory             ok
umeng-aff300-06    DIMM-2                       Memory             ok
4 entries were displayed.

Memory status is a good idea and seems natural to add to the Power dashboard.
The only way to expose this information to Harvest may be to use the private cli pass through like so:
Similar to your query1
curl -k 'https://<IP_ADDRESS>/api/private/cli/system/controller/memory/dimm?fields=node,slotname,status,alt-cecc-dimm'

and similar to your query2
curl -k 'https://<IP_ADDRESS>/api/private/cli/system/controller/fru?subsystem=Memory&fields=node,fru-name,status'

Harvest's REST collector is still in beta, but supports the private cli pass through. We use it in a few templates already to close gaps between REST and ZAPI.

Hello @cgrinds,
Yes I saw the new dashboards for the version that you released this week (I think they are great, I am still checking the new info, many thanks for your improvements and new features) and related with that version and the problem we have with the memory I thought it would be a good idea to have this information in some panel, maybe a panel focus with the physical components. If you add this in the power it is OK for me or if you give a different name to that panel focus in the HW is good too.
Here the output to our cluster now for the command that you put in the end of your response (query1, query2). In the last record appears as OK because we change the module **DIMM 13** in the node snes1p301_01  but I think this could be a good idea add in a panel.
{
  "records": [
    {
      "node": "snes1p301_01",
      "subsystem": "memory",
      "serial_number": "CE-03-1923-1227A76D",
      "fru_name": "DIMM-5",
      "status": "ok"
    },
    {
      "node": "snes1p301_01",
      "subsystem": "memory",
      "serial_number": "CE-03-1923-1227A7E0",
      "fru_name": "DIMM-1",
      "status": "ok"
    },
    {
      "node": "snes1p301_01",
      "subsystem": "memory",
      "serial_number": "CE-03-1923-1227A7E6",
      "fru_name": "DIMM-13",
      "status": "ok"
    },
    {
      "node": "snes1p301_01",
      "subsystem": "memory",
      "serial_number": "CE-03-1923-1227A8BF",
      "fru_name": "DIMM-4",
      "status": "ok"
    },
    {
      "node": "snes1p301_01",
      "subsystem": "memory",
      "serial_number": "CE-03-1923-1227A8EE",
      "fru_name": "DIMM-8",
      "status": "ok"
    },
    {
      "node": "snes1p301_01",
      "subsystem": "memory",
      "serial_number": "CE-03-1923-1227A8F2",
      "fru_name": "DIMM-6",
      "status": "ok"
    },
    {
      "node": "snes1p301_01",
      "subsystem": "memory",
      "serial_number": "CE-03-1923-1227A952",
      "fru_name": "DIMM-3",
      "status": "ok"
    },
    {
      "node": "snes1p301_01",
      "subsystem": "memory",
      "serial_number": "CE-03-1923-1227BCDD",
      "fru_name": "DIMM-14",
      "status": "ok"
    },
    {
      "node": "snes1p301_01",
      "subsystem": "memory",
      "serial_number": "CE-03-1923-1227BD79",
      "fru_name": "DIMM-12",
      "status": "ok"
    },
    {
      "node": "snes1p301_01",
      "subsystem": "memory",
      "serial_number": "CE-03-1923-1227BDF6",
      "fru_name": "DIMM-11",
      "status": "ok"
    },
    {
      "node": "snes1p301_01",
      "subsystem": "memory",
      "serial_number": "CE-03-1923-1227BDF8",
      "fru_name": "DIMM-10",
      "status": "ok"
    },
    {
      "node": "snes1p301_01",
      "subsystem": "memory",
      "serial_number": "CE-03-1923-1227C0F2",
      "fru_name": "DIMM-15",
      "status": "ok"
    },
    {
      "node": "snes1p301_01",
      "subsystem": "memory",
      "serial_number": "CE-03-1923-1227C0FA",
      "fru_name": "DIMM-7",
      "status": "ok"
    },
    {
      "node": "snes1p301_01",
      "subsystem": "memory",
      "serial_number": "CE-03-1923-1227C1CE",
      "fru_name": "DIMM-16",
      "status": "ok"
    },
    {
      "node": "snes1p301_01",
      "subsystem": "memory",
      "serial_number": "CE-03-1923-1227C1D6",
      "fru_name": "DIMM-2",
      "status": "ok"
    },
    {
      "node": "snes1p301_01",
      "subsystem": "memory",
      "serial_number": "CE-03-1923-1227C1D7",
      "fru_name": "DIMM-9",
      "status": "ok"
    },
    {
      "node": "snes1p301_02",
      "subsystem": "memory",
      "serial_number": "CE-03-1925-1252E9C6",
      "fru_name": "DIMM-8",
      "status": "ok"
    },
    {
      "node": "snes1p301_02",
      "subsystem": "memory",
      "serial_number": "CE-03-1925-1252EDC8",
      "fru_name": "DIMM-16",
      "status": "ok"
    },
    {
      "node": "snes1p301_02",
      "subsystem": "memory",
      "serial_number": "CE-03-1925-1252F6B3",
      "fru_name": "DIMM-15",
      "status": "ok"
    },
    {
      "node": "snes1p301_02",
      "subsystem": "memory",
      "serial_number": "CE-03-1925-1252F709",
      "fru_name": "DIMM-7",
      "status": "ok"
    },
    {
      "node": "snes1p301_02",
      "subsystem": "memory",
      "serial_number": "CE-03-1925-1252FF4B",
      "fru_name": "DIMM-14",
      "status": "ok"
    },
    {
      "node": "snes1p301_02",
      "subsystem": "memory",
      "serial_number": "CE-03-1925-12530118",
      "fru_name": "DIMM-5",
      "status": "ok"
    },
    {
      "node": "snes1p301_02",
      "subsystem": "memory",
      "serial_number": "CE-03-1925-12530261",
      "fru_name": "DIMM-6",
      "status": "ok"
    },
    {
      "node": "snes1p301_02",
      "subsystem": "memory",
      "serial_number": "CE-03-1925-1254E9F3",
      "fru_name": "DIMM-1",
      "status": "ok"
    },
    {
      "node": "snes1p301_02",
      "subsystem": "memory",
      "serial_number": "CE-03-1925-12551305",
      "fru_name": "DIMM-4",
      "status": "ok"
    },
    {
      "node": "snes1p301_02",
      "subsystem": "memory",
      "serial_number": "CE-03-1925-1255133C",
      "fru_name": "DIMM-2",
      "status": "ok"
    },
    {
      "node": "snes1p301_02",
      "subsystem": "memory",
      "serial_number": "CE-03-1925-12551B7F",
      "fru_name": "DIMM-9",
      "status": "ok"
    },
    {
      "node": "snes1p301_02",
      "subsystem": "memory",
      "serial_number": "CE-03-1925-12551BA9",
      "fru_name": "DIMM-11",
      "status": "ok"
    },
    {
      "node": "snes1p301_02",
      "subsystem": "memory",
      "serial_number": "CE-03-1925-12551BDF",
      "fru_name": "DIMM-10",
      "status": "ok"
    },
    {
      "node": "snes1p301_02",
      "subsystem": "memory",
      "serial_number": "CE-03-1925-12551C0A",
      "fru_name": "DIMM-12",
      "status": "ok"
    },
    {
      "node": "snes1p301_02",
      "subsystem": "memory",
      "serial_number": "CE-03-1925-12551C70",
      "fru_name": "DIMM-3",
      "status": "ok"
    },
    {
      "node": "snes1p301_02",
      "subsystem": "memory",
      "serial_number": "CE-04-2049-449DA75E",
      "fru_name": "DIMM-13",
      "status": "ok"
    }
  ],
  "num_records": 32
}

Thanks for your great work.

We'll document how to add memory panels to the cluster dashboard and check if the EMS collector is a better fit for detecting this problem too.

Hello @rahulguptajss
I've updated the configuration following the steps that you shared and I've created a new dashboard with the code that you shared too.
This is the result for the DIMM panel.

Why don't you plan to add this panel to the harvest version yet? Don't you think if it will be useful? Or there are other implications that I don't know? Maybe it is because is part of rest plugin?
Thanks.
Best regards.

@rahulguptajss I was looking for the change in this nightly build for adding filtering support in the private cli but I couldn't find any change. My custom_dimm.yaml has the same code https://github.com/NetApp/harvest/discussions/1187

I have the latest release version in my production environment.
harvest version 22.05.0-1 (commit 2bc2942) (build date 2022-05-11T07:56:11-0400) linux/amd64

I only can try the nightly build in a test environment but until the new feature doesn't come in a release, I'll never have this functionality in my production env.
I imagined that you will release a new version during this month since it seems you usually do every 3 months. But the problem is you don't plan to add this in the new version, right? Or I am confused with the memory information with the REST API. Sorry if I am mixing different concepts.

Perfect, thanks for the clarification. In that case, when you will release the new version we will update our current version to that.


Add key_identify_strategy to allow different keys for JWK validation

Add key_identify_strategy
Allow the following options:

kid (default)
x5t
kid_x5t
Implemented memory cacher to allow caching JWK according to strategy
Expanded JWKClient to allow JWT key extraction according to strategy
Signed-off-by: Neta.Peleg<EMAIL_ADDRESS>

closes #43

License notice from Oracle looks good to me
Ready to merge if technical validation is good @kpacha


⚠ Bofrost.lu has degraded performance

In 7043d46, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1255 ms

Resolved: Bofrost.lu performance has improved in 75078ab after 20 minutes.


Scratch org pool should not be deleted if "postDependencyInstallationScript" fails

Referring to Slack post by @ruslan-kurchenko:
"Hello, community! Is there a way to prevent a "postDeploymentScriptPath" script from deleting a scratch org if it fails? "
When a team messes up with package dependencies (caused mainly by a source type), our prepare phase fails, but a post-install script executes anyways. It depends on metadata that is not in the org, and obviously - it fails.
So, can we either not execute the post-install script if all packages were not installed or prevent the script from enforcing the job to delete orgs?
Slack Message

However, is the pool deleted if package checkpoints are used, succeedOnDeploymentErrors = false and postDependencyInstallationScript fails?


Ability to start/stop service by name

I can help with implementation if you like?

I did not implement this because this is possible via the ServiceController.Start() method which is available on .netstandard / .net core through this nuget package.
But I'm open to suggestions. I suppose it would be a cleaner method call (the MSDN sample doesn't work if I read that correctly because the ServiceName property is readonly so you'd have to call the static GetServices() method and find the one you're looking for).

Since this is pretty straightforward to do, I'll include it in the next release (hopefully this year).
It will probably look like:
class Win32ServiceManager {
    Task StartService(string serviceName, params string[] arguments);
    Task StopService(string serviceName);
}

Thoughts?

Thanks for pointing me to System.ServiceProcess.ServiceController nuget package, I didn't know that it is available from "netstandard1.6" already . Only issue was that I had to update to .net 461 otherwise it wouldn't install.
I see your point - probably no need to duplicate functionality. Like me, people might looking for service start/stop in your lib when they are using it, so maybe it is still worth?
BTW MSDN example is probably just out of date. You need to pass service name in constructor. I tried it and it works.

Not doing this for now since there isn't really an added value over System.ServiceProcess.ServiceController (other than maybe doing it async)


proali Error:deNovoGenomeVariantCallingMultipleThreads.cpp:204

Error code: Exited with exit code 134.
Error info :
anchorwave: /share/home/zhangsan/software/AnchorWave/AnchorWave/src/impl/deNovoGenomeVariantCallingMultipleThreads.cpp:204: void genomeAlignmentSingleThread(std::vector<AlignmentMatch>, bool, bool, std::ofstream&, std::ofstream&, std::__cxx11::string, std::__cxx11::string, std::__cxx11::string, std::__cxx11::string, int, std::__cxx11::string, std::__cxx11::string, int32_t, int32_t, int32_t, int32_t, int32_t, int32_t, int32_t, int32_t, int32_t, int32_t, int32_t, std::atomic_int&, std::map<std::__cxx11::basic_string<char>, std::__cxx11::basic_string<char> >): Assertion `temp.compare(queryGenomerSequence)==0' failed.
A1_A2.bash: line 34: 347874 Aborted                 (core dumped)

I am use anchorwave  v1.0.1  AVX512 is enabled
my running script is
anchorwave proali -i ${ref_gff} -as ${ref_abbr}.cds.fa -r ${ref_genome} -a ${query_abbr}.sam -ar ${ref_abbr}.sam -s ${query_genome} -n ${ref_abbr}_${query_abbr}.anchors -R 1 -Q 2 -t 4 -o ${ref_abbr}_${query_abbr}.alignment.maf -f ${ref_abbr}_${query_abbr}.alignment.f.maf

And the output file XXX.alignment.maf have been correct output of  29 lines, and then the above error occurs.
I allocated 230G memory and 4 cpus to this script.

Thanks for trying AnchorWanve. Could you provide enough information, so that I could repeat this error, please?
Including input data, every command, minimap2 version, etc.

I regenerated the sam file and ran it again afterwards. The program runs successfully, which may be caused by the incomplete sam file generated when I run it for the first time.

Hi,Baoxing Song,
I got the above error again core dumped.I used 4 cpus to allocate 230G of memory to the program at the same time, but the program still reported an error. I queried that the error was caused by insufficient memory allocated to C++.
What I want to ask is, do you have any plans to support the continued analysis of breakpoints, such as this interruption caused by insufficient memory, can you support proali to continue the analysis in the future? You know it takes a long time to rerun proali every time.

Thanks. This is a good suggestion. I will try to implement this feature.


Why are we not allowed to open giant .txt files?

VSCode Version: 1.7.1
OS Version: Windows 10 Home 14393.447

Steps to Reproduce:

Open large text file
Crash

Seriously, why is this not allowed? I can use the inferior Notepad or Notepad++ and not have any issues whatsoever.

Because vscode has multiple plugins that do more then just display characters on screen. Imagine a plugin that is doing parsing, analyzing, syntax checking autocomplete etc, and then give it a 1gb file... not going to happen is it? unless you have 2000$ workstation or something. Consider it as a fail save for people who accidentally open a bin file or movie file. Happens allot more then you think :)

I meant .txt in general, which doesn't bog down the system even on a RPi3 with the text file open in Chrome.

vscode nature is to always try to do deep analysing on it. Don't know if there is a option to go in notepad mode and disable all parsing even on a txt file for example spelling check plugins etcetera. If you really feel like some files need to be handled with vscode try to make a more specific use case for it. But keep in mind vscode is ment for app development, for example if you want to edit a huge csv file then excel is going to work better for you.
Last time I got into trouble with a 4gb csv file i wrote something to put it in a sql database and edited it that way. Anyway in short I don't think vscode is the right tool to handle something large even if it is just txt.
But feel free to convince the vscode developers with a more specific example use case, thanks.

@rogersachan How big is your file? Is it with a .txt file extension?

From @ilovesusu

Generate a 50mb file, about 2000000 lines

$:bash
$:i= 0
$:while [ $i -le 3000000 ]; do echo "asdfghjjklooiyerqwuhgsdjg" >>hello; i=$(($i + 1)); done

Open a 50mb file

Maybe a switch could be added to settings.json that would allow overriding the message?

Let's track in #9832 . Generating a file with the provided script (translated to nodejs):
var fs = require('fs');

var str = '';
for (var i = 0; i < 3000000; i++) {
	str += 'asdfghjjklooiyerqwuhgsdjg\n';
}
fs.writeFileSync('hello', str);

yields a 70MB file which is above our large file threshold


Add toggles to XP Orb hovered line items display

Just added conditionals to control what is displayed inside the tooltip box.
Closes #9497

I'll fix it later tonight

Done

Additionally, "Xp/hr left" isn't a thing and has no meaning

Oopsies

All of the third config item should be "showXpHour"


#224 Add config in .env.example from frontend

This is just a helper, to identify whenever a version is deployed in backend/frontend, we can identify the actual released version.


Make lxd-images work nicer-ly with proxies

Thanks to Scott Moser for the patch.
Signed-off-by: Tycho Andersen<EMAIL_ADDRESS>

Nice, this works on my machine behind proxy.

Hmm, wait, why is that needed?
That patch is identical to what I first gave smoser but we then figured that using p80 every time would work too and would let us drop the if statement.

So before we merge that, I'd like to see proof of a case where our current code (which uses proxy-friendly gpg over port 80) fails in some cases and understand exactly what those cases are.

I don't know, I just added it because rharper told me too :)

So we agreed with @raharper that this patch does nothing, closing the pull request.


Add archetypes repository and config

Repository is json file with archetypes list.
Places to keep repository by priority

in user home directory, file .config/charmix/archetypes.json
in package directory (may be flushed after update version)

Before this task we have to done https://github.com/vitonsky/charmix/issues/6

Done. Archetypes now stored in ~/.charmix/archetypes.json


[Question] Does this support AWS Kinesis Video Signalling Client for Javascript v3

Hi,
We are working on migrating from AWS Kinesis Video Signalling Client v2 to v3, and we are noticing issues with this version of WebRTC SDK such as viewer not getting any video etc., I tried looking online for a WebRTC SDK version which could support v3 but, could not find any.
Could you confirm whether, this SDK can work with v3?

@tejaschandra911 ,
I would recommend using what our SDK is tested with (https://github.com/aws/aws-sdk-js). I am still unclear on the changes between the 2 versions, but we do not have a version that is tested with v3 today.

@disa6302 We have managed to migrate to v3 version in November. The issues were mostly due to webpack. Now, it has been resolved.


I cannot see the installation pages on spanish

Please comment on https://github.com/reactjs/es.react.dev/issues/500.


why ObjectPaste had about 1map improvement for camera_only branch?

Hey thanks for great repo first,
I noticed that the config in the camera branch training process still retains lidar-related operations such as ObjectPaste. Although no point cloud information is used in the camera training, the addition of gt_boxes and gt_labels by ObjectPaste still has some impact on the training. In my experiments, I found that the map could reach 36.2 when ObjectPaste was present, and dropped to 35.2 without ObjectPaste. However, theoretically, the ObjectPaste operation added extra meaningless target boxes to the images, which could not be matched with the image features. But why such a result occurs and could u please explain this? Btw why u keep ObjectPaste in camera only branch?
Best
Rui

one more question: why change center_int to center_int[[1,0]] in camera only branch https://github.com/mit-han-lab/bevfusion/blob/db75150717a9462cb60241e36ba28d65f6908607/mmdet3d/models/heads/bbox/centerpoint.py#L548

one more question: why change center_int to center_int[[1,0]] in camera only branch
https://github.com/mit-han-lab/bevfusion/blob/db75150717a9462cb60241e36ba28d65f6908607/mmdet3d/models/heads/bbox/centerpoint.py#L548

this problem i figure it out. could u pls the first question explain? ty

Unfortunately, I don't have an explanation for this phenomenon. It may be due to fluctuations during training.


add badge for docker registry

https://circleci.com/gh/jumanjihouse/puppet-on-coreos/19 is clean
:ship:


refactor Alert/Confirm and update test case

Coverage increased (+1.4%) to 71.628% when pulling fb0cf80b1f8e2effdfd5653325d870297846f400 on edison-hm:dev into 059b532261b7feec703b00193d2ea5aab22a1be9 on ZhonganTechENG:dev.


Added deduplication and sorting for displayed accounts in the dropdown menu

Context
Added deduplication and sorting for displayed accounts in the dropdown menu. Fixes an issue when Teletraan receives duplicates of accounts with the same id for different cells. (But that accounts contains different configs as well, that's why we need them to store in Rodimus)
Tests
Before these changes

After these changes

it should show the account only without binding with the region, we have a separate dropdown for region.

@ntascii it will not show region as we discussed yesterday on the call.


Fix CUDF's Column.from_column_view by copying it and adjusting.

Description

Closes https://github.com/nv-morpheus/Morpheus/issues/1934
By Submitting this PR I confirm:

I am familiar with the Contributing Guidelines.
When the PR is ready for review, new or existing tests cover these changes.
When the PR is ready for review, the documentation is up to date with these changes.

/merge


Use TypeDoc API to eliminate 'command line too long' error

Credit to gulp-typedoc

Please accept this pull request. It fixed my problems.

+1


Embedded Exercise video examples

When looking at the randomized workout that's provided in the randomizer, I would like to have a youtube video embedded that can show you exactly an example of the exercise.

Example code to help get videos embedded:
Embedding youtube videos


»Recent entries" for water are NOT unique

Hi (again) 😁😇,
while working on #2 / #6 I realised that the distinct(:amount)-call in WaterEntry
https://github.com/joemasilotti/daily-log/blob/510e142358fa49d1470826f7c38ed17be396ebf4/rails/app/models/water_entry.rb#L8
does not actually do anything. Here's a link to the documentation: https://api.rubyonrails.org/classes/ActiveRecord/QueryMethods.html#method-i-distinct. The method signature of distinct is very misleading I think 😅.
How to reproduce
Add a couple of WaterEntry-items with the same value:

Idea 4 a Fix
IMHO the simplest thing would be do take care of uniqueness (and sorting - #2) after loading the latest three items into the application, i.e.
scope :recent, -> { order(created_at: :desc).limit(3).to_a.uniq(&:amount_value) }

or
scope :recent, -> { order(created_at: :desc).limit(3).to_a.uniq { |wi| wi.amount.value } }

Then, #2 could be solved by appending .sort_by(:amount).

Ha, I should have read this first before addressing your other PR! 😆
This still won't work if the last 2 entries are the same because we are querying for 3 before grabbing unique entries.
I'm going to close this in favor of the PR you opened since that now has a failing test.


Windows 10 with Bluetooth Dongle failed to find bluetooth

I have been setting up the service and everything is to your spec. I have installed the dongle, and it is uses the supplied drivers (not the Win 10 default). It is working with every other device that I pair with it. When I have it activated and run the service get the following report:
bluetooth_get_host_address - Failed to find a bluetooth radio
All of the unit tests that are included in the package work. The Move controllers respond and the video links are up and working. I just can seem to connect the move controllers. What am I missing?
I also tried the last two alphas just to make sure that the service update had not impacted the setup.
[2017-02-15 23:07:58.389]: bluetooth_get_host_address - Failed to find a bluetooth radio
I am also getting- I have two PS3 cameras in my setup. I assume this is all of the times I connected/installed the cameras.
\AppData\Roaming\PSMoveService\TrackerManagerConfig.json"
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
[2017-02-15 23:07:58.421]: PS3EyeTracker::open - Opening PS3EyeTracker(USB\VID_1415&PID_2000\b1_p9, camera_index=0)
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
ps3eye::PS3EYECam::getDevices() found 2 devices.
Thank you for your time. I am excited about this project and hope to use it if I can make it past this one.

Sorry for the trouble and thanks for the detailed logs and the investigation.
Which bluetooth adapter do you have?
If it's the Asus BT-400 (the one recommended in the hardware wiki) you actually DON'T want to use the supplied driver and DO want to use the Win10 default ones. Using the supplied drivers has led to exactly this problem. Why using the supplied drivers breaks the windows find bluetooth radio API is unknown to me.
Also the following error:
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
.. actually isn't important. It's effectively log spam from libusb that unrelated to the PS3Eye camera, but is unavoidable if we want other useful libusb logs.
Also for future reference, when asking troubleshooting questions, please post to the PSMoveService google group first: https://groups.google.com/forum/#!forum/psmoveservice. If we determine there that there is an actual bug, then we'll file an issue. We have to be militant about routing issues to the google group because otherwise the issues list quickly gets unmanageable.
I'm going to close this issue for tracking purposes, but please feel free to continue the conversation here.

Thank you for the response. I will remove the drivers and attempt the Windows 10 defaults. I will report back asap. Wish me luck.
Anthony Shumate

On Feb 16, 2017, at 2:13 AM, Guido Sanchez<EMAIL_ADDRESS>wrote:
Sorry for the trouble and thanks for the detailed logs and the investigation.
Which bluetooth adapter do you have?
If it's the Asus BT-400 (the one recommended in the hardware wiki) you actually DON'T want to use the supplied driver and DO want to use the Win10 default ones. Using the supplied drivers has led to exactly this problem. Why using the supplied drivers breaks the windows find bluetooth radio API is unknown to me.
Also the following error:
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
.. actually isn't important. It's effectively log spam from libusb that unrelated to the PS3Eye camera, but is unavoidable if we want other useful libusb logs.
Also for future reference, when asking troubleshooting questions, please post to the PSMoveService google group first: https://groups.google.com/forum/#!forum/psmoveservice https://groups.google.com/forum/#!forum/psmoveservice. If we determine there that there is an actual bug, then we'll file an issue. We have to be militant about routing issues to the google group because otherwise the issues list quickly gets unmanageable.
I'm going to close this issue for tracking purposes, but please feel free to continue the conversation here.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/cboulay/PSMoveService/issues/361#issuecomment-280262173, or mute the thread https://github.com/notifications/unsubscribe-auth/AAbVLZ2rJfbG2opxrplJsLBX5rhgyg6fks5rdAUagaJpZM4MCl9r.

Whoops, forgot to close issue like I said I would before...

The based Windows drive did get me to the next step. I am working on the sampling section. Everything is tuned with the mask being seen, but I can only get it to sample station one. Do you have a trouble shooting section about this process? Thank you again.
A

On Feb 16, 2017, at 10:31 AM, Anthony Shumate<EMAIL_ADDRESS>wrote:
Thank you for the response. I will remove the drivers and attempt the Windows 10 defaults. I will report back asap. Wish me luck.
Anthony Shumate

On Feb 16, 2017, at 2:13 AM, Guido Sanchez<EMAIL_ADDRESS><EMAIL_ADDRESS>wrote:
Sorry for the trouble and thanks for the detailed logs and the investigation.
Which bluetooth adapter do you have?
If it's the Asus BT-400 (the one recommended in the hardware wiki) you actually DON'T want to use the supplied driver and DO want to use the Win10 default ones. Using the supplied drivers has led to exactly this problem. Why using the supplied drivers breaks the windows find bluetooth radio API is unknown to me.
Also the following error:
libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
.. actually isn't important. It's effectively log spam from libusb that unrelated to the PS3Eye camera, but is unavoidable if we want other useful libusb logs.
Also for future reference, when asking troubleshooting questions, please post to the PSMoveService google group first: https://groups.google.com/forum/#!forum/psmoveservice https://groups.google.com/forum/#!forum/psmoveservice. If we determine there that there is an actual bug, then we'll file an issue. We have to be militant about routing issues to the google group because otherwise the issues list quickly gets unmanageable.
I'm going to close this issue for tracking purposes, but please feel free to continue the conversation here.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/cboulay/PSMoveService/issues/361#issuecomment-280262173, or mute the thread https://github.com/notifications/unsubscribe-auth/AAbVLZ2rJfbG2opxrplJsLBX5rhgyg6fks5rdAUagaJpZM4MCl9r.

By "sampling section" I assume you mean the tracking pose calibration?
-Are you sure the color calibration is set right? Sometimes if the exposure or gain are set too high you can get patches of light  that get confused for your tracking bulb.
-You might also try assigning a different tracking color for the controller.
-Finally it's also possible that the surface you have place the controller on isn't flat. The tracking pose calibration tool tries to use the accelerometer in the controller to tell if the controller is pointed straight upward. If you are certain it's pointed upward and the sampling timer keeps resetting, go ahead and hit the "trust me, it's stable" button for force sampling at that location.


Failed to reuse a Session file with my own FileStream

File created WTelegram.session from verification_code
string Config(string what)
            {
                if (what == "api_id") return "*****3268";
                if (what == "api_hash") return "***********e4213cc42e2197db5de67";
                if (what == "phone_number") return "******8892884";
                if (what == "verification_code") return null; // let WTelegramClient ask the user with a console prompt
                if (what == "first_name") return "John";      // if sign-up is required
                if (what == "last_name") return "Doe";        // if sign-up is required
                if (what == "password") return null;     // if user has enabled 2FA
                return null;
            }
var stream = new MemoryStream(
                  Uteis.GetFile(Uteis.RootPath() +Path.DirectorySeparatorChar+"WTelegram.session"));
var client = new WTelegram.Client(Config,stream);

WTelegram.WTException: 'Exception while reading session file: The input data is not a complete block.
Use the correct api_hash/id/key, or delete the file to start a new session'

The default WTelegramClient session store (when you leave it null in constructor) doesn't generate session files in a format compatible with the stream of data expected when you give your own session store
If you want to pass your own (custom) file stream in constructor, start with an empty file and generate a new session (with verification code)

Hello Please Provide Example I Have Exactly Same This Error !
I Create Session with this method
clienttelegram = new WTelegram.Client(12XXX,"bXXXX",HttpContext.Current.Server.MapPath("~/tempkey.session"));
Create File Session Successfully And Logon Ok !
But Afte Reuse Session Exception throw
static string Config(string what)
{
switch (what)
{
case "api_id": return "12XXXXX";
case "api_hash": return "bd4XXXXXX";
case "phone_number": return "+9891XXXX";
case "verification_code": return "";
case "first_name": return "";
case "last_name": return "";
case "password": return "";
default: return null;
}
}
clienttelegram = new WTelegram.Client(Config, File.Open(HttpContext.Current.Server.MapPath("~/tempkey.session"), FileMode.Open));
Please Help Me Thx

Yes, it's the same issue as OP
In one case you pass just the pathname

HttpContext.Current.Server.MapPath

and in the other case, you pass a FileStream

File.Open(HttpContext.Current.Server.MapPath

Those leads to different file storage formats that are incompatible.
Either use only pathnames, or only FileStreams, but don't mix both to resume sessions.
When dealing with files, I recommend you only use pathnames (not FileStream), the format is optimized for performance.
To use a pathname with the Config callback constructor, have the Config method reply to "session_pathname".

hello thx for reply .
but when reuse session second contructor of WTelegram Accept Only Session
Can not pass string to second contructor of new Wtelegram
Second Time for resuse call :
clienttelegram = new WTelegram.Client(Config, File.Open(HttpContext.Current.Server.MapPath("/tempkey.session"),


Specify language for data schema specification

The central functionality of Coulomb is to allow generation of user interfaces for entry of structured data.
By structured data we mean data model and/or schemas. Coulomb’s goal is to accept a data schema and it allows generating interfaces that can accept user input that writes data according to that data schema.
In terms of data model definition languages, ISO 10303-11 specifies EXPRESS, OMG has UML and SysML, YAML and JSON Schema are also data mode definition languages.
According to ISO 8000-110, there is the concepts of “data requirement”, “portable data set” and data features. A portable data set is a data set that all of its values satisfy given data requirements (eg. a schema). The requirements can specify needs on data values, eg the units they use are as specified, if data value sources are specified, if the data values are accurate with some given statement.
Data relationships also need to be considered here. For example, the IEC CDD contains values that specify units, eg “the screw has a height in mm”, where the “mm” is another data model specified in the CDD. This means a data set that conforms to the “CDD screw data model” must contain the “height” attribute using the unit “mm”.
We can can consider coulomb as the generic processor of “taking data requirements” => “generates a UI for entry of data that conforms to those requirements” => “writes the inputted data according to the desired data structure”.
This task is to find-modify/develop a specification language that can be used to “specify data requirements” (the input to coulomb).

For the record, the current course of action is set to bundle more data-focused components with Coulomb (for object browsing, editing, revision management, etc.), and to extend app configuration to tie those components to data models.
We may be able to configure component widgets by peeking data model interfaces, which would require using a custom TS transformer. If it works, generic data entry components can be zero-input with data models properly defined as interfaces.
If we can’t do that or if it proves to be insufficient (so, most likely), we may be able to support a spec for easy configuration of widgets for data operation. Based on the spec Coulomb should be able to understand, e.g. (for object edit view), the order and grouping of fields, field types, constraints, etc.


Sprint 7 - Test Automation Research Ticket

Obtain access to the “Performance Environment”.
Start creating sample automation scripts for ECMPS.
Troubleshoot scripting issues/ continue research on BlazeMeter.

Test development tickets have been added for Sprint 8
#6320
#6321
#6322
#6323


Workshop: DeFi Concepts - AMM, liquidity pools, token swaps and flash loans

General Information

Field name
Description
Field value

Title
Official name of the community call
Hand-on coding defi smart contract

Host
Name of the main host

Partners
Are there any external partners?

Spakers
List of speaker names

Description

Language
Which is the delivered language of the community call?

Date
When will it happen?

Mode
Offline or Online

Agenda
Provide the overall agenda of the community calls here

Pre activities

[ ] Section Required

Main activities

[x] Section Required

List of deliverables

[ ] Slides
[ ] Codes

Detailed plan

Section name
Description
Speaker / Guest

Post activities

[ ] Section Required

Here the slide for this one: https://docs.google.com/presentation/d/1xTjMyR5gNbBDFJi7rRnP83YFiXHwaZ7IKroRBe5XRtk/edit?usp=sharing


Provide example for druid-kubernetes-overlord-extensions basePodSpec.yaml

Hey all,
I'm struggling with the setup of druid-kubernetes-overlord-extensions with the customTemplateAdapter with the following setting snippet:
druid.indexer.runner.k8s.adapter.type=customTemplateAdapter
druid.indexer.runner.k8s.podTemplate.base=/druid/taskSpecTemplates/basePodSpec.yaml
druid.indexer.runner.k8s.podTemplate.index_parallel=/druid/taskSpecTemplates/basePodSpec.yaml

Basically I have no idea how the basePodSpec.yaml shall look like.
Is it just a "normal" Kubernetes PodSpec with kind: Pod or is it a kind: PodTemplate?
Can somebody maybe post a basePodSpec.yaml here as an first example?

I got this working using the druid operator with the following template
pod-template.yaml
 apiVersion: "v1" kind: "PodTemplate" template:   metadata:     annotations:       custom-annotation: "hello"     labels:       custom-label: "hello"   spec:     affinity: {}     containers:     - command:         - sh         - -c         - |           /peon.sh /druid/data 1           sleep 30       env:       - name: CUSTOM_ENV_VARIABLE         value: "hello"       image: apache/druid:26.0.0       name: main       ports:       - containerPort: 8091         name: druid-tls-port         protocol: TCP       - containerPort: 8100         name: druid-port         protocol: TCP       resources:         limits:           cpu: "1"           memory: 2400M         requests:           cpu: "1"           memory: 2400M       volumeMounts:       - mountPath: /opt/druid/conf/druid/cluster/_common         name: common-config-volume         readOnly: true       - mountPath: /opt/druid/conf/druid/cluster/master/coordinator-overlord # this is still mounted in this location because that's where peon.sh looks         name: nodetype-config-volume         readOnly: true       - mountPath: /druid/data         name: data-volume       - mountPath: /druid/deepstorage         name: deepstorage-volume     restartPolicy: "Never"     securityContext:       fsGroup: 1000       runAsGroup: 1000       runAsUser: 1000     tolerations:     - effect: NoExecute       key: node.kubernetes.io/not-ready       operator: Exists       tolerationSeconds: 300     - effect: NoExecute       key: node.kubernetes.io/unreachable       operator: Exists       tolerationSeconds: 300     volumes:     - configMap:         defaultMode: 420         name: tiny-cluster-druid-common-config       name: common-config-volume     - configMap:         defaultMode: 420         name: druid-tiny-cluster-peons-config       name: nodetype-config-volume     - emptyDir: {}       name: data-volume     - emptyDir: {}       name: deepstorage-volume
I created a configMap with the above template and mounted it to the overlord at
`

mountPath: /opt/druid/conf/druid/cluster
name: "peon-pod-template-volume"
readOnly: true
`

I set this on the overlord
druid.indexer.runner.type=k8s druid.indexer.runner.k8s.podTemplate.base=/opt/druid/conf/druid/cluster/pod-template.yaml druid.indexer.runner.k8s.adapter.type=customTemplateAdapter druid.indexer.runner.javaOptsArray=[] druid.indexer.runner.namespace=default
I also had to add these two things to the peon runtime properties as well (otherwise the pod fails to start due to issues finding some files.
druid.indexer.task.baseTaskDir=/druid/data druid.indexer.runner.type=k8s
I can try to put up a PR with more detailed startup instruction later.

Thanks a lot!


Added test data with 365 and 360 calendars

Are you still working off of this branch or am I good to merge and delete?

still using my branch .. just thought i'd push the test data to the master

Got side tracked away from my precip index with the resampling stuff :/

Pull Request Test Coverage Report for Build 107

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 52.632%

Totals

Change from base Build 106:
0.0%

Covered Lines:
150

Relevant Lines:
285

💛  - Coveralls


test: use unified github action yml

https://github.com/ant-design/ant-design/issues/50461

@afc163 CR~


Fix Storage Path Not Resolving ~ as Home Directory.

@timoman @skuehn @ericchang: Here's the bug that @timoman's "friend" ran into a while back. It was with some other tool but with the same underlying issue.
In this case, if someone was using something like ~/botstorage/, the resulting files would get created as ./~/botstorage instead of resolving the ~ as the home directory.
This fixes it so that no more evil ~ get inadvertently created.

~squirrel~

needs more awk
#recycledjokes

:shipit:

@timoman is being very serious about this. I think he wants his "friend" to not experience this awkward bug again.


Error : Failed to compute packing, pod did not fit in instance type option even though matching provisioner exists

Version
Karpenter: v0.52
Kubernetes: EKS v1.21
Expected Behavior
The pod should be scheduled via the new custom provisioner
Actual Behavior
Getting error,
2022-01-03T09:33:44.695Z        ERROR   controller.provisioning Failed to compute packing, pod(s) [default/pause-57d7bf4ddb-5kcnk] did not fit in instance type option(s) [] {"commit": "870e2f6", "provisioner": "default"}
Steps to Reproduce the Problem

Create new custom provisioner with the default provisioner kept intact.
Create a deployment with all contraints mentioned in customer provisioner.

Resource Specs and Logs

"default" provisioner kept untouched.

Create a new provisioner with the following specs,

Spec:
  Limits:
  Provider:
    API Version:       extensions.karpenter.sh/v1alpha1
    Instance Profile:  KarpenterNodeInstanceProfile
    Kind:              AWS
    Security Group Selector:
      kubernetes.io/cluster/support-dev:  *
    Subnet Selector:
      kubernetes.io/cluster/support-dev:  *
  Requirements:
    Key:       node.kubernetes.io/instance-type
    Operator:  In
    Values:
      t4g.nano
      t4g.micro
      t4g.small
      t4g.medium
      t4g.large
      t4g.xlarge
      t4g.2xlarge
    Key:       karpenter.sh/capacity-type
    Operator:  In
    Values:
      spot
    Key:       kubernetes.io/arch
    Operator:  In
    Values:
      amd64
  Ttl Seconds After Empty:  30

Create a deployment with following constraints,

      nodeSelector:
        node.kubernetes.io/instance-type: t4g.micro
        karpenter.sh/capacity-type: spot
        kubernetes.io/arch: amd64

Logs show the following and seem to not try with custom provisioner

2022-01-03T09:33:37.559Z        INFO    controller.provisioning Waiting for unschedulable pods  {"commit": "870e2f6", "provisioner": "just"}
2022-01-03T09:33:44.689Z        INFO    controller.provisioning Batched 1 pods in 1.000423516s  {"commit": "870e2f6", "provisioner": "default"}
2022-01-03T09:33:44.695Z        ERROR   controller.provisioning Failed to compute packing, pod(s) [default/pause-57d7bf4ddb-5kcnk] did not fit in instance type option(s) [] {"commit": "870e2f6", "provisioner": "default"}
2022-01-03T09:33:44.695Z        INFO    controller.provisioning Waiting for unschedulable pods  {"commit": "870e2f6", "provisioner": "default"}
2022-01-03T09:45:29.163Z        INFO    controller.provisioning Waiting for unschedulable pods  {"commit": "870e2f6", "provisioner": "default"}

Enable debug logging: kubectl patch configmap config-logging -n karpenter --patch '{"data":{"loglevel.controller":"debug"}}'. My guess is that t4g.micro was excluded due to kube system overhead.

Hey @shirish-qub !
Your deployment nodeSelector will never match any instances as defined because t4g.* instance types are arm64 architecture not amd64. If you change your nodeSelector to:
      nodeSelector:
        node.kubernetes.io/instance-type: t4g.micro
        karpenter.sh/capacity-type: spot
        kubernetes.io/arch: arm64

it should provision the node if the pod can fit on the t4g.micro w/ the kubelet overhead and any daemonset overhead.


feat: validation for @amplienceExtension

More validation for @amplienceExtension:

must be of Nullable Object type (eg not String! or String or ObjectType!)
must not reference an object type annotated with @amplienceContentType

Can you run pnpm changeset? This should generate a file and please add that to this PR.
(I'll add this instruction in the README later ;) )


Remove unused code

What type of PR is this?
/kind cleanup
What this PR does / why we need it:
The previous code and directory also made me feel confused. I saw that #107 had not been updated for a long time, so I submitted this PR.
Which issue(s) this PR fixes:
Fixes #107
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

none

/cc @warjiang

/assign

thks~

/lgtm
/approve


Develop documentation

Fixed online hosting of documentation with PkgTemplates.jl . Added codecov, tagbot, compathelper, and dependabot into github actions

Welcome to Codecov :tada:
Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests.
Thanks for integrating Codecov - We've got you covered :open_umbrella:

Strålende!


VisibilityNotifier2D not emitting signals when child of PathFollow2D

Godot version:
3.2.rc3, 3.2.rc4
OS/device including version:
Windows 10, MacOS10.15.2 Catalina
Issue description:
I have enemies structured like so:

I create the PathFollow2D in code and add it to a Path2D.
When an enemy moves off the screen the VisibilityNotifier2D never emits screen_exited or viewport_exited. I suspect it is because its parent node's (The Area2D) position never changes from (0, 0).
To test this I changed the Area2D's position manually via the Local tree editor once it had moved offscreen and the VisibilityNotifier2D immediately emitted the correct signal.
I've been using this same code which has worked since 3.0, the regression seems to have occurred in 3.2 somewhere (I think it occurred in 3.2.rc2 as well.)

Alright, I figured out what was causing this, and I am fairly sure it is a regression in 3.2 (I tried an older build of my game and confirmed it didn't happen in it.)

I made the Rect size of the VisibilityNotifier2D bigger to better match the size of my enemy - I'm not sure if this is a relevant detail or not.
If the PathFollow2D containing the VisibilityNotifier does not go far enough off the screen then the signals mentioned above do not emit. I'm positive the VisibilityNotifier is completely off the screen, but it doesn't trigger until it goes much further off the screen.
I added some points to my paths to make them go way off the screen to make sure it triggered which fixed my game.

From the docs:

Note: For performance reasons, VisibilityNotifier2D uses an approximate heuristic with precision determined by ProjectSettings.world/2d/cell_size. If you need exact visibility checking, use another method such as adding an Area2D node as a child of a Camera2D node.

so, having to go a bit further out of the screen for it to signal is expected and normal.
Minimal reproduction project: 35634.zip
This is based on the given screenshot/description. Main.tscn has the nodes in the scene, Main2.tscn makes them in code.
@benbishopnz is this issue resolved for you?

The issue still exists in the sense that something changed between versions (ie. something used to work, I upgraded version and it stopped working.)
That said, the problem I was having in my project has been resolved, so I will close this issue.


fix(sourcemaps): fix vue style source maps

API

fix(api): change default source maps type to inline-source-map

CSS

fix(css): add sourceMap option for css loaders

Vue

fix(vue): replace style-loader to vue-style-loader

Sorry for the delay, but I don't think any of this is needed anymore. Sourcemaps are applied automatically based on the devtool setting, which we already configured based on whether the user wants sourcemap support.


When calling system call that quark container doesn't support yet

What happens if I call a system call that is not currently supported by the quark container?
Is the system call of the host kernel bypassed to be called?
Or is it impossible to be called?

If QKernel doesn't the syscall, it will return error. For example, for qkernel doesn't support syscall sys_get_kernel_syms, it will return error code SysErr::ENOSYS. The source doe is as below: https://github.com/QuarkContainer/Quark/blob/c19ea5ec6cc27781ca4ba7f67464dcc6aa7ed2ad/qkernel/src/syscalls/syscalls.rs#L315


Delayed jobs are not being run

Greetings,
I am running resque-scheduler (4.0.0), resque (1.25.2), ruby (2.2.0p0)
I run the resque-scheduler standalone job via
LOGFILE=/[censored]/resque-scheduler.log VERBOSE=true bundle exec resque-scheduler -B
And, my Resque.enqueue_at() jobs are not being executed when they should be:

Do you have any thoughts on how to go about debugging why my jobs are not being executed.
I've tried restarting resque-scheduler several times, but it hasn't executed the new jobs.  I have no "cron" like scheduled jobs.
(The first block of jobs, were removed and manually executed)
-daniel

It looks like the "Job count" column is 0 for times in the past; for some reason that isn't getting cleaned up, but the jobs are getting removed from the delayed queue; looking at the code, I see that error handling in enqueueing a job happens after the job is popped from the delayed queue, and that exceptions raised here are squashed & logged. Do your logs indicate that anything is amiss?
The command-line utility less can be used to inspect your log file; the '+G' flag will cause it to start showing the end-of-file, which may be where the interesting stuff is happening, but you can scroll with the arrow keys:
$ less +G /[censored]/resque-scheduler.log

It's possible that your scheduler process doesn't have access to the job's class, which would cause it to raise an exception, or that something in the job class' before_enqueue_* hook is raising an exception; the logs will tell you more.
Your command above doesn't include --initializer-path or --environment flags, so I assume the process just doesn't know enough about the work to be able to put it on a queue (it needs the class definition for that). If this is the case, you'll need to point it to a ruby script that can load your application (without starting any server processes), at least far enough to have all the relevant job classes loaded.
Can you verify that the jobs are getting placed on their queues?

Ah!  That was was the problem
There wasn't an initializer-path.
I like to store individual "types" of data in different redis databases, and resque work is stored in database #5.
Since there wasn't an initializing piece of code, resque-scheduler never knew to look in the right database.


feature(i18n): implement xi18n command

Implement i18n messages extractor. Contrary to @angular/complier-cli's command it will not throw an error if a resource is not found.

Replaced acceptance tests by e2e tests. Let me know if they satisfy your requirements.

Could you rebase on the latest master? I think those e2e tests are failing because of an old error.

Sure, I'll do it tomorrow.
Op di 6 dec. 2016 om 19:44 schreef Hans<EMAIL_ADDRESS>
Could you rebase on the latest master? I think those e2e tests are failing
because of an old error.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/angular/angular-cli/pull/3340#issuecomment-265235287,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AF0oW0W1a6i9s3xjrEyKFWfGGCgEsO4dks5rFa0GgaJpZM4LBScU
.

Done!

Pushed a new version that throws an error if format argument is none of allowed.
However, since 2.3.0-rc.0 compiler's Extractor no longer accepts a resourceLoader function as a parameter which changes completely this implementation. I'll have to take a look to new i18n extracting API.

@vicb Did we change the interface of the Extractor?

The Serializer interface has changed in 2.3

@vicb How new Serializer's interface affects to resource loading?

Hi @cladera
Hi @vicb
what is the current state of this pull request? How would you have to rewrite the extractor call ...
Thank you so much!

@cladera Many changes came in 2.4.0. This PR basically needs to be redone, but it's not that big of a deal. We added a private API in Angular that can be used to extract stuff, without worrying about changes to the Extractor class.
We probably wants to run through a full webpack build while doing the extraction so that we have a compilation and can build sass/less/pug files. Do you know how to do that? I can help you finish this PR.

Thank you so much, @cladera. This is great!

ng i18n is avalailable in @angular/cli: 1.0.0-beta.31
but i don't see any entry for this in the changelog?
anyway, thanks! very convenient! :+1:


Bug 1986311: SRO crashes when an incorrect chart is applied

This PR cherry-picks the latest bugfixes from upstream, including a fix to BZ1986311, as well as the following issues:

Make the pullsecret field optional in the CRD
Move the helm related structs out of helmer.go and into the api folder, in order to avoid the import of the whole helm package when using the SRO api.
do not delete NS if not owned
updated charts to adhere to the new API

/bugzilla refresh

/cc @zvonkok @SchSeba

/lgtm

/bugzilla refresh


Tons of Optimizations

Removed a lot clutter and comments
Removed lyrics generator thing
Changed wyg.mp3 with original Want You Gone
Better WantYouGone.py

Thats a lil wierd, i still want the generator to be here because i want other people to make their own creations with my project. currently seeing what you did there, but thank you a lot for supporting my code

reviewed most of the changes, not sure if i should merge, theres good and bad features added like the lyrics.txt changes, i dont like them, as they dont give credit to the original creators, and WYGgenerator being removed..

why were the code comments removed?

thats better, but please. dont remove code parts that seems "unessesary" like os.environ['PYGAME_HIDE_SUPPORT_PROMPT'] = "hide", this WILL break the gui version.

why were the code comments removed?

thats the point btw

but then its less readable 😭

Currently testing the code, can refine or remake the part that explained people can make their own lyrics with this project?


Warning line 36

When I run the example, show me a warning (line 36) "LaTeX Font Warning: Font shape `T1/ClearSans-LF/m/sc' undefined".

It is possible that depends on your LaTex configuration.... could you add more details?


[Question] Where is the text for ytsa.thecodeblog.net located? Is it on GitHub?

Is the full version of docs placed on GitHub? If yes, please tell where it is. If no, maybe place it on GH so everyone can change and review it after adding new features.

the source code of the documentation is right here: Docs Source Code
Feel free to make changes to it. The documentation will update automatically because I'm using the hosting service from ReadTheDocs. And for the description of each function and property, the content is right there inside the source code. Feel free to make them better as well.


Tabs for Phases section

Refactor Phases section on homepage to a tab-style element

Before

After

@davidrnovak At full screen browser width on my 14" macbook pro the items wrap:

I think this is a reasonable browser width, so we probably want to tighten this up?

Could a potential quick fix strategy be to not include Planning and potentially Analyize in the list with the same way as the others?

I think its a bit of an issue on mobile that when you click on an item, because the other tab being shown closes, what is in your viewport switches and the content for the item you clicked on is no longer visible.
To replicate this, on mobile click on Analyze. The Analyze content is mostly off my screen when I do that.

@cpytel I think removing Planning and Analyze currently is the best option. The phase overview does say 5 phases (I just overlooked it), so having the 5 phases makes sense for consistency.
For the mobile issue I just want to make sure I'm understanding it correctly. Are we wanting the tab, when clicked, to snap the content to the top of the viewport?


Can not mint on beta

What happened?
When I click "create" it sends me to create collection by default, I think it should be the other way arounda
Please reproduce in steps
https://beta.kodadot.xyz/rmrk/create
Expected Behavior
Mint stuff
What browsers are you seeing the problem on?
No response
Are you logged in?
Yes
At which address did you encounter bug?
beta.kodadot.xyz
Screenshots

Relevant log output
Thank to ClownWorldHouse !
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Should be fine now since redeploy.
API seems to be working

meanwhile working


Add an include-tracing interface for data arbiter decoding

While doing this we should implement: https://github.com/vkottler/vcorelib/issues/127.

Adding on https://github.com/vkottler/vcorelib/pull/132.


Permissions needed to create and manage Managed Private Endpoints is not on this page

Permissions needed to create and manage Managed Private Endpoints is not on this page

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

ID: 1bb9ad75-5aa1-af3d-9f59-073015190950
Version Independent ID: 467433dd-ade8-5109-eaa5-a2198146b769
Content: Understand access and permissions in the Microsoft Purview governance portal - Microsoft Purview
Content Source: articles/purview/catalog-permissions.md
Service: purview
GitHub Login: @viseshag
Microsoft Alias: viseshag

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

Hi @viseshag
Could you please review add comments on this, update as appropriate.

Hi @tifischer
The link below discusses the predefined roles of control on the Microsoft Purview governance portal and their categories.
https://learn.microsoft.com/en-us/azure/purview/catalog-permissions#roles:~:text=Purview Data Map.-,Roles,a collection to be able to access the Purview governance portal.,-Note
Here mentioned about Microsoft Purview private endpoint deployment scenarios.  could you please go through the below link for your referance. It might be helpful.
https://learn.microsoft.com/en-us/azure/purview/catalog-private-link#:~:text=not have one.-,Microsoft Purview private endpoint deployment scenarios,endpoint for Microsoft Purview%2C managed storage account and Azure data sources).,-Support%20matrix%20for
Please add your ideas in below link, so our production team can review it and update the same.
Ideas · Community (azure.com)

@tifischer
We are going to close this thread, if there are any further questions regarding the documentation, please tag me in your reply and we will be happy to continue the conversation.

@tifischer -
To create managed PE you need data source admin.
To approve the PE in Azure, you need Azure RBAC: network contributor role or custom role (including relevant actions to approve the PE).
I'm adding this to our documentation....


cmd/go: PWD not honored in "go list -m" with explicit GOWORK

What version of Go are you using (go version)?

$ go version
go version devel go1.19-4d2da99 Sun Mar 20 03:01:15 2022 +0000 darwin/arm64
$ go1.18 version
go version go1.18 darwin/arm64

Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
N/A

What did you do?
A simple reproducable is to create a workspace within the temporary directory on darwin:
cd $(mktemp -d) && txtar-x <<<'
-- go.work --
go 1.19

use ./mymod
-- mymod/go.mod --
module mymod

go 1.19
-- mymod/main.go --
package main
'

The temp dir on macOS is a symlink where the real path has a /private prefix, e.g.:
$ pwd
/var/folders/cz/31br911566l_bbx72cs_pgs40000gn/T/tmp.gRKXUCNX
$ pwd -P
/private/var/folders/cz/31br911566l_bbx72cs_pgs40000gn/T/tmp.gRKXUCNX

x/tools relies on cmd/go returning resolved paths as per: https://github.com/golang/tools/blob/5ea13d0d89f92d5ca5468e282dd4ba2ad7503564/internal/gocommand/invoke.go#L216-L221
	// On darwin the cwd gets resolved to the real path, which breaks anything that
	// expects the working directory to keep the original path, including the
	// go command when dealing with modules.
	// The Go stdlib has a special feature where if the cwd and the PWD are the
	// same node then it trusts the PWD, so by setting it in the env for the child
	// process we fix up all the paths returned by the go command.

When running go list, the directories works as expected:
$ go list -json mymod/... | grep $(pwd)
	"Dir": "/var/folders/cz/31br911566l_bbx72cs_pgs40000gn/T/tmp.gRKXUCNX/mymod",
	"Root": "/var/folders/cz/31br911566l_bbx72cs_pgs40000gn/T/tmp.gRKXUCNX/mymod",
		"Dir": "/var/folders/cz/31br911566l_bbx72cs_pgs40000gn/T/tmp.gRKXUCNX/mymod",
		"GoMod": "/var/folders/cz/31br911566l_bbx72cs_pgs40000gn/T/tmp.gRKXUCNX/mymod/go.mod",
$ PWD=$(pwd -P) go list -json mymod/... | grep $(pwd)
	"Dir": "/private/var/folders/cz/31br911566l_bbx72cs_pgs40000gn/T/tmp.gRKXUCNX/mymod",
	"Root": "/private/var/folders/cz/31br911566l_bbx72cs_pgs40000gn/T/tmp.gRKXUCNX/mymod",
		"Dir": "/private/var/folders/cz/31br911566l_bbx72cs_pgs40000gn/T/tmp.gRKXUCNX/mymod",
		"GoMod": "/private/var/folders/cz/31br911566l_bbx72cs_pgs40000gn/T/tmp.gRKXUCNX/mymod/go.mod",

Until I explicitly set GOWORK (before PWD since go env otherwise picks up the resolved dir):
$ GOWORK=$(go env GOWORK) PWD=$(pwd -P) go list -json mymod/... | grep $(pwd)
	"Dir": "/var/folders/cz/31br911566l_bbx72cs_pgs40000gn/T/tmp.gRKXUCNX/mymod",
	"Root": "/var/folders/cz/31br911566l_bbx72cs_pgs40000gn/T/tmp.gRKXUCNX/mymod",
		"Dir": "/var/folders/cz/31br911566l_bbx72cs_pgs40000gn/T/tmp.gRKXUCNX/mymod",
		"GoMod": "/var/folders/cz/31br911566l_bbx72cs_pgs40000gn/T/tmp.gRKXUCNX/mymod/go.mod",

What did you expect to see?
I would expect that PWD is honored when running go list regardless of if GOWORK is set or not. Essentially I would expect GOWORK=$(go env GOWORK) here to be a no-op without side effects.
What did you see instead?
go list returning non-resolved paths when PWD is set.

//cc @bcmills @matloob

I would expect GOWORK=$(go env GOWORK) here to be a no-op without side effects.

It should be, provided that you run go env GOWORK with the same value of PWD. If you set GOWORK and PWD to use two different names for the same directory, then one of them has to win out.
This doesn't look like a cmd/go bug to me.

Apologies, I should have explained that better. Another example (in linux, for readability):
$ cd /tmp && mkdir -p real/mymod
$ ln -s real symlink
$ cd symlink/mymod && go mod init mymod
$ pushd .. && go work init mymod/ && popd

Now from /tmp/symlink:
Plain go list uses /tmp/symlink (as I expected)
$ go list -json mymod/... | jq .Module
{
  "Path": "mymod",
  "Main": true,
  "Dir": "/tmp/symlink/mymod",
  "GoMod": "/tmp/symlink/mymod/go.mod",
  "GoVersion": "1.19"
}

Setting PWD to the real path makes go list use /tmp/real (also expected):
$ PWD=/tmp/real/mymod go list -json mymod/... | jq .Module
{
  "Path": "mymod",
  "Main": true,
  "Dir": "/tmp/real/mymod",
  "GoMod": "/tmp/real/mymod/go.mod",
  "GoVersion": "1.19"
}

Setting both PWD to the real path and an explicit GOMOD (to the symlink) also makes go list use PWD (expected):
$ PWD=/tmp/real/mymod GOMOD=/tmp/symlink/mymod/go.mod go list -json mymod/... | jq .Module
{
  "Path": "mymod",
  "Main": true,
  "Dir": "/tmp/real/mymod",
  "GoMod": "/tmp/real/mymod/go.mod",
  "GoVersion": "1.19"
}

But setting GOWORK changes the behavior and PWD is ignored. When you say that:

one of them has to win out.

I would expect PWD to win, as it does when I set GOMOD explicitly in the example above.
$ PWD=/tmp/real/mymod GOWORK=/tmp/symlink/go.work go list -json mymod/... | jq .Module
{
  "Path": "mymod",
  "Main": true,
  "Dir": "/tmp/symlink/mymod",
  "GoMod": "/tmp/symlink/mymod/go.mod",
  "GoVersion": "1.19"
}

Setting GOMOD has no effect at all; see #51217.

Gotcha, I incorrectly assumed that you could set GOMOD. Regardless of that I still expect PWD to have the same effect on module/package file paths even when GOWORK is explicitly set.
The current situation, if I understand it correctly, is that paths is shown based on the use-directive in "go.work-mode". And that path can be relative such as the example above use ./mymod.
The difference between setting GOWORK explicitly and letting cmd/go infer GOWORK is that in one case PWD will affect the result, while in the other case it won't.

The difference you're seeing is that when PWD is set, the inferred value of GOWORK reflects that setting. If you explicitly set GOWORK=$(PWD=… go env GOWORK), you should find that the result is consistent with setting PWD to that value for other commands.

Yeah, I understand that the inferred value of GOWORK depends on PWD.
The part that seems odd is that directories provided by go list -json depends on PWD unless GOWORK is set.
Ok, just to make sure I understand how this suppose to work:

Directories returned by go list -json is evaluated by looking at the use-directive in go.work (in go.work-mode obviously).
If the use-directive is a relative path then the absolute path will be evaluated by looking at the directory part of GOWORK.
Setting PWD will alter how GOWORK is inferred, unless is explicitly set.

Am I missing something?

Yes, that's exactly it. When you set PWD without GOWORK, it changes the inferred GOWORK, which in turn changes all of the paths computed relative to that.
When you set GOWORK explicitly, you override the inferred GOWORK, which changes all of the paths derived from it.

Adding this to the Go 1.19 milestone until we can understand what the desired behavior is and what we should do about it (I didn't fully follow the conversation, but I also only skimmed it). Feel free to move it.

I don't think there is anything to change here. The go command is correctly interpreting the current directory per PWD, and is correctly interpolating GOWORK relative to PWD.
If GOWORK is correctly set to a value that matches PWD, then everything lines up. If PWD is changed to no longer match GOWORK, then GOWORK must win, or else the command would fail entirely because the requested packages aren't lexically inside the workspace. (The latter seems strictly worse than the former.)
Overall, my advice is: keep PWD consistent with whatever the user set it to, and don't mess with it otherwise. (When changing to a relative directory, set PWD relative to the previous PWD.)


Merge multipart uploads

I implemented the multipart uploads in tinys3, I currently use them in my application and they work well.
A quick tour on how to use them if you would like to test:

Create a multipart upload:

co = tinys3.Connection('key', 'secret', 'bucket', tls=True)
mp_upload = co.initiate_multipart_upload(key='test', bucket='bucket')  # bucket is optional

initiate_multipart_upload returns a MultipartUpload object bound to the connection it comes from, and it works quite like the Boto one.

Upload a part:

resp = mp_upload.upload_part_from_file(fp, 1)

upload_part_from_file returns the requests response. It can take a length and md5 parameters that will be put in the request's Content-Length and Content-MD5 headers, and also the file handling parameters (close, rewind) UploadRequest already takes and that do the same thing.

Complete the upload:

resp = mp_upload.complete_upload()

complete_upload returns the requests response.

Abort the upload:

mp_upload.cancel_upload()

cancel_upload returns the requests response.

List a bucket's multipart uploads:

for mp in co.list_multipart_uploads(bucket='bucket'):
    print mp.bucket, mp.key, mp.uploadId

list_multipart_uploads can also take a prefix parameter to list only multipart uploads that concern files under a specified directory.

List a multipart upload's already uploaded parts:

for p in mp.list_parts():
    print p['part_number'], p['last_modified'], p['size'], p['etag']

However, I also made a number of changes in the rest of the project, here are some notes :

Since I tried as much as possible to comply to PEP8, a lot of formatting has changed. I hope it won't bother (but PEP8 compliance is cool)

I updated of the AWS_QUERY_PARAMS for multipart upload requests to work

It turned out that sorting the query string keys in low-level request signature method was necessary

I changed all the format strings from the "str % format" version to string.format version

Since I need to use the GET request's Range header, I added an headers param to S3Connection.get()

Also added some parameters to the list function (This was removed because it was making the tests fail, I don't use it, and I'm a bit lazy.)

Created the XML_PARSE_STRING global as it is used at a lot of places in the code (more maintainable)

Changed the request URL in bucket_url from region-based to virtual-hosting style

I added the DeleteRequest and HeadRequest classes.

So i guess this is never going to be merged?

Hi, sorry dude, I had an issue with my notifications so I never saw that :-/
Going over it right now...

Wow, this was quite a long time ago indeed.
It passed fine back then, but now there are merge conflicts. Plus, I just realized I didn't include tests for the new features...
Shlomi, I'm sorry this is a rather big PR, but as soon as you're finished overviewing it, just share your impressions and I'll do the fix ASAP. I'll also add tests to it.

If I can help in anyway, I'd love to. I'll be using this quite a bit to manage large hprof files. I am about to write my own library as I need to make some traction.

Hello,
so I finally got to finish this... Now with tests !
I also removed a dependency on the MultipartUpload object from some of the requests to keep a similar interface between all requests, along other minor changes.
I also tried to be as PEP8 compliant as possible.


Refactored modal css

Refactored common modal css out to main beeline.scss
Override default $modal-inset-mode-break-point so that it fixes bug where ios modals would have extra padding at the top
Make modal styling consistent across the whole app

Re-opening after discussion with Swee Chin on styling modals across the whole app


Add a stream API for zstd

Without a stream API the squash command tries to allocate a buffer as big as the input file which isn't a very good idea with big files.

Thanks!  You even signed the CLA, which is awesome.
Unfortunately it looks like this causes some tests to fail; see Travis and AppVeyor.  Note that if you target a branch other than "master", like "staging", the tests should run automatically when you file or update the PR.

Without a stream API the squash command tries to allocate a buffer as big as the input file which isn't a very good idea with big files.

FWIW, we do usually mmap the file instead of just mallocing a huge buffer, so unless you're on 32-bit it's probably not that bad.  That said, streams are definitely preferred as even on 64-bit platforms we can't always use mmap.

I'm not sure if cff90b2 is correct but it seams logical to me.

Sorry it took so long for me to get to this.

I'm not sure if cff90b2 is correct but it seams logical to me.

No, something else is going on here.
Looking at how the return value for decompression is determined in squash_zstd_process_stream, it doesn't really match the documentation in zstd.  zstd says that a return value of 0 means "a frame is completely decoded and fully flushed", but you're returning SQUASH_END_OF_STREAM there.  Frame != stream; unless I'm mistaken (i.e., assuming zstd is similar to other codecs), streams can contain multiple frames, so it's quite possible that there is more data.  AFAICT there is no way to know whether we have actually reached the end of stream or the end of a frame.
Unfortunately, zstd's API is a bit weird.  If we try to flush the decompression by passing 0 input bytes to ZSTD_decompressStream after it previously returned 0 (indicating the end of a frame), it returns an error code instead of 0.  So, we can either keep track of the previous value (in the SquashZstdStream struct) or handle the error code.
I squashed most of the commits and added a patch so the tests all pass (as well as fixing a warning from ICC).  Everything should be working now.
Thanks for the patches.  Streaming support for zstd is very nice to have :)

Thanks for adding, but:

it doesn't really match the documentation in zstd. zstd says that a return value of 0 means "a frame is completely decoded and fully flushed", but you're returning SQUASH_END_OF_STREAM there. Frame != stream;

The documentation says: ZSTD_endStream() instructs to finish a frame.
So I would say the words frame and stream are interchangeable.
Additionally after flushing a frame in ZSTD_decompressStream set its state to zdss_read which set its state to to zdss_init if the frame has ended which does a return ERROR(init_missing);
This means after reaching a end of frame the ZSTD_DStreamis unusable after a end of frame another sign zstd's end of frame is really a end of compressed stream

@Cyan4973, could you confirm that (we're talking about ZSTD_decompressStream)?

I would rather lean towards @nemequ definition : a stream may contain multiple frames.
The confusion is quite understandable, as generally, a stream consists of a single frame. If you compress a long file with zstd, you will get a single frame as a result.
But if you compress it with pzstd, you would get multiples frames, all stored into a same file, and interleaved with skippable frames containing metadata (multiple threaded decompression). Such file can still be decoded by zstd : it simply decodes each frame one by one, skip over skippable ones, and regenerate original data faithfully. It's a good example showing a stream consisting of multiple appended frames.
Another potential source of confusion is the difference between compression and decompression.
Compression is in charge. Compression decides when a frame ends. That's the point of ZSTD_endStream(). Compression could also decide to create multiple frames and append them in a single file or stream.
Decompression read and execute. It doesn't decide when a frame ends, nor if there is any other data to follow. It just gets the job done.
Decompression still knows when a frame ends, even in the middle of a stream. That's why it returns a code 0. It allows the decoder to be informed that a frame was just completed, which could be a relevant signal.
After finishing a frame, there might be some more input data left to decode.
The current API model requires to re-init the decoder context, between each frame, using ZSTD_initDStream(). If data is pushed without init, the decoder context is considered uninitialized, which triggers an error. The benefit is that it makes an "end-of-frame" a compulsory signal. The downside is that it requires logic to insert init call.
Other logics could have been implemented.
For example, ZSTD_decompressStream() could simply accept more data, transparently issuing an init in the background.
The downside is that it's easy to miss the "end of frame" signal.
Or it could also refuse to read more data, and just output 0, saying "current frame is completed, please start a new one with init". The downside is that it's easy to stay stuck in an infinite loop, re-presenting the same data again and again without it being consumed.
All 3 behaviors are acceptable. It's mostly a matter a selecting one.

If we try to flush the decompression by passing 0 input bytes to ZSTD_decompressStream after it previously returned 0 (indicating the end of a frame)

When ZSTD_decompressStream() returns 0, it means both that input has reached the end of a frame, but also that the decoded frame has been entirely flushed. So there is nothing left to flush.

Interesting.  It seems like re-initializing the decoder would be the best way to go as that will let us interoperate with pzstd (as well as anything else that does something similar).

The benefit is that it makes an "end-of-frame" a compulsory signal. The downside is that it requires logic to insert init call.

Why is it important that people see the end of frame signal?
If it is a requirement it would be great if the documentation could be changed to reflect that; I doubt I'll be the only person who will be a bit confused with the current documentation.

Other logics could have been implemented.
For example, ZSTD_decompressStream() could simply accept more data, transparently issuing an init in the background.
The downside is that it's easy to miss the "end of frame" signal.

I'm not familiar enough with zstd's internals to offer a strong opinion, but it seems to me it would be better to optimize the API for the simple case (which people are more likely to use) as long as it's still possible to write a parallelized decoder (which, I assume, needs that end of frame signal?).
Does flushing during compression (ZSTD_flushStream) cause a frame to end as well?
I see examples/screaming_decompression.c doesn't handle streams with multiple frames; it might be nice to tweak it to do so.

Does flushing during compression (ZSTD_flushStream) cause a frame to end as well?

No, it causes a block to end, so that data can be flushed immediately.
A frame consists of multiple appended blocks.
It takes ZSTD_endStream() to end a frame.
Btw : and now I realize that the naming, ZSTD_endStream(), implies that it's ending a stream .... meh ....

I see examples/screaming_decompression.c doesn't handle streams with multiple frames; it might be nice to tweak it to do so.

Good point

Why is it important that people see the end of frame signal?

It depends on the application.
In our case, it's an important signal in situations where we have to route frames from different formats. Typically, within just Zstandard, we have several legacy formats to support (v0.4.x, v0.5.x, v0.6.x, v0.7.x). This is now handled transparently in the streaming API, but it used to be manual.
Now, the zlib wrapper API goes even farther, and is able to decode zstd and zlib frames mixed within a single file (or stream).
pzstd also needs to actually read and decode some skippable frames in order to exploit the metadata it contains.
This is all rather advanced stuff, and I guess most casual users won't need that.
Still, the capability to detect and stops at end of frame boundaries is an important feature for advanced scenarios to be possible.

OK, here is a potential follow up.
If I do remember correctly, an important problem when selecting an API behavior is a lack of feedback, especially when it's about advanced stuff that few people will ever need.
Consequently, regarding this specific end-of-frame signal, I selected the most conservative solution, knowing that if it needed to be changed later, it would still be possible. That is, if I relax conditions to start new frames, that's still compatible with a strict initialization at new frame policy. The other direction would have broken existing user codes.
So here is a tentative behavior which seems simpler for "normal" usages, and remains compatible with existing codes :
ZSTD_decompressStream() would still stop at end of frame, providing a 0 return code,
but after that stage, it is possible to provide even more input data, without requiring to ZSTD_initDStream() first.
It effectively makes ZSTD_initDStream() completely optional.
There is still a problem though, when associated with dictionaries.
Requiring to init at the beginning of each new frame makes it very clear which dictionary must be used to decode the new frame. So, what now ?
I believe the most sensible solution is to re-use previous parameters, hence re-use dictionary previously selected.
In effect, it means the API would trigger a ZSTD_resetDStream() transparently in the background.

@Cyan4973, that all sounds quite reasonable to me.
Sorry, I should have added streaming support to Squash a long time ago, before zstd's API was stable.

This change of Streaming API behavior will probably be introduced in Zstandard v1.2

Great, thanks :).  I'll probably throw together a patch for Squash to call resetDStream manually soon; no reason not to be compatible with 1.0 if we can.

For information :
in latest dev branch update, the init policy regarding streaming decompression API has been softened.
Now, providing more data to ZSTD_decompressStream() after a completed frame will trigger an implicit ZSTD_resetDStream(). It effectively means users can continue feeding more data as long as wanted without any need to init/reset at the end of each frame.
This change will be present in next release.


Update staking rates on frontend

@shahthepro LGTM. Added a small fix so on local the stake widget rate is aligned with the stake action box rate. To fix this problem - rate 197b vs 1.5m:


feat: update apiVersions for later k8s versions

Coverage remained the same at 33.347% when pulling 2457a91acf977d55b98bb2bbec1a3890796945b4 on support-1-13 into 17ef520d23e4e0155b6dd3eb139556bddbecf85e on master.


jwm does not update its panel position when the screen size changes

Version: Debian stable's v2.4.4. Possibly this is just that version, I've not gone delving into the source. Sorry!
Context: I'm running jwm via xrdp. This allows me to resize the X11 screen (Remmina calls it "dynamic resolution update"). However, the details don't matter so much: this is probably going to happen with VMs over Spice or VNC or whatever, too.
What I expect: Resizing my remote desktop window causes jwm to resize and redraw its panel.
What I see: If I do that, jwm's panel stays where it is. It's annoying, and can cause the panel to go out of view, if it's at the bottom.
There are a couple of configurable workarounds, which I'll post in the thread. It would be nice if jwm didn't need them, however.

Quick workaround
Make your <RootMenu> contain something like
<Restart label="Restart JWM" icon="reload"/>

and run it when things get funky.
Hacky workaround
Make your jwmrc contain
<StartupCommand>jwm-randr-autoresize &</StartupCommand>

And put that shell script somewhere on your $PATH:
#!/bin/bash
# Handle the screen size changing by restarting jwm.

set -e

SCRIPT=$(basename "$0" .sh)
FLAGFILE="/tmp/.${SCRIPT}.$$.${USER:-unknown}"
TIMEOUT_SECONDS=2
INITIAL_DELAY_SECONDS=5

process_line () {
	# Lines matching a given fixed string
	if [ "$1" != "${1%RRScreenChangeNotify*}" ]; then
		touch "$FLAGFILE"
	fi
}

process_timeout () {
	if [ -f "$FLAGFILE" ]; then
        xrandr --auto || true
		jwm -restart || true
        sleep 5
		rm -f "$FLAGFILE"
	fi
}

do_cleanup () {
	rm -f "$FLAGFILE"
}

watch_root_window () {
	# The -1 flag isn't supported everywhere yet.
	stdbuf -oL xev -root -event randr -1 || \
	stdbuf -oL xev -root -event randr
}

do_cleanup
sleep "$INITIAL_DELAY_SECONDS"
trap do_cleanup exit
watch_root_window 2>/dev/null | while true; do
	IFS= read -r line
	process_line "$line"
	while IFS= read -t "$TIMEOUT_SECONDS" -r line; do
		process_line "$line"
	done
	process_timeout
done


Bug: Git Information column are empty

Description
It's working in <IP_ADDRESS>

Steps To Reproduce

Open a git repo
See no content loaded from git information

Requirements

Load Git Information

Files Version
<IP_ADDRESS>
Windows Version
10.022631.4169
Log File
debug.log

@Josh65-2201 thank you for the timely catch! I discovered the cause was incorrect logic introduced in #16141 and I've pushed a commit to resolve this issue.


[Help] All available commands

Can you share all available commands so the new comer can understand how to use it.

hi, do you mean key maps? Cause there're plenty commands that I don't know in neovim and plugins.

Yes, I mean the same
Some commands for getting started with tree view and command line would be helpful.

Thanks this is very useful.


v.0.21.13

Version 0.21.13
Released March 15, 2023

Refactor NYSE holidays, #1018 (@KJhellico)
Fix distribution build, #1028 (@arkid15r)
Fix the documentation build warning, #1026 (@arkid15r)
Optimize TestAllInSameYear::test_all_countries test, #1001 (@arkid15r)
Update Canada localization: fr, #1015 (@KJhellico)
Update Denmark holidays: remove "Store bededag" starting 2024, #1013 (@malthe)
Update PR template, #1019 (@arkid15r)
Update Portugal holidays, #1011 (@PPsyrius)
Update Ukraine holidays, #1014 (@KJhellico)
Update package build process, #1020 (@arkid15r)
Add multiple countries localization: en_US, es, uk, #1012 (@KJhellico)
Unify country imports order, #1003 (@arkid15r)
Use native apostrophe for uk locale holiday names, #1004 (@arkid15r)

Coverage: 99.961% (+8.0e-06%) from 99.961% when pulling f740404a205058ac68918f0dcf43ff8fe02251e1 on beta into 80927d6110889b26ae3ccd198198b7f4a32e7f61 on master.


Render Failure: Cannot read properties of undefined (reading 'match')

Expected Behavior
After update i can't open the app.
Render Failure: Cannot read properties of undefined (reading 'match')
Actual Behavior
After update i can't open the app.
Render Failure: Cannot read properties of undefined (reading 'match')
Reproduction Steps
No response
Is there an existing issue for this?

[X] I have searched the issue tracker for this problem.

Additional Information
No response
Insomnia Version
latest
What operating system are you using?
macOS
Operating System Version
sonoma 14.0 (23A344)
Installation method
download site
Last Known Working Insomnia version
No response

Same here. Started happening after updating to 8.4.1

Just got the same issue on 8.4.1

Got the same as well. Reinstalling doesn't work

Each week I regret more and more sticking to insomnia now ...

Seeing this as well immediately after updating today - can't try reinstalling as the Google OpenID and Login By Email Code are both dumping me to error screens!
Anyone got a short term workaround to get back to usability until a fix is in place?

Same here

+1

same here

I reinstalled 8.4.0 to get back up on macOS

same here

I was able to fix the issue by downloading the latest version from the github releases folder and overrode the update manually.

I seem it was some kind of server error.

I was able to fix the issue by downloading the latest version from the github releases folder and overriding the update manually. Not sure why that would make a difference though.

What are the steps to do this?

I reinstalled 8.4.0 to get back up on macOS

Same. Download from https://github.com/Kong/insomnia/releases/tag/core%408.4.0

Yeah -- I think this is a pretty serious issue.  What happens if my internet connection goes down, but I still want to do testing on internal servers?  Will this tool no longer work?

Is this error still happening?

Is this error still happening?

no, working now.

i get this error today right after update to 8.4.2.

Fresh install worked: https://github.com/Kong/insomnia/releases/tag/lib%408.4.2

Same issue here, right after update stuck on this error

Same

same here

This should not be closed as the latest update/install pack isn't working.
Downloaded the windows version, starting it: nothing happens.
If i unistall to reinstall completely, will i loose my local collections ?

same here - macos 14.0 with Insomnia 8.4.2
    at yI (file:///Applications/Insomnia.app/Contents/Resources/app.asar/index-09030ac4.js:659:7762)
    at eJ (file:///Applications/Insomnia.app/Contents/Resources/app.asar/index-09030ac4.js:707:774)
    at Ck (file:///Applications/Insomnia.app/Contents/Resources/app.asar/index-09030ac4.js:116:19553)
    at Hj (file:///Applications/Insomnia.app/Contents/Resources/app.asar/index-09030ac4.js:118:44101)
    at Nj (file:///Applications/Insomnia.app/Contents/Resources/app.asar/index-09030ac4.js:118:39819)
    at Uxe (file:///Applications/Insomnia.app/Contents/Resources/app.asar/index-09030ac4.js:118:39745)
    at cp (file:///Applications/Insomnia.app/Contents/Resources/app.asar/index-09030ac4.js:118:39596)
    at ow (file:///Applications/Insomnia.app/Contents/Resources/app.asar/index-09030ac4.js:118:35959)
    at zj (file:///Applications/Insomnia.app/Contents/Resources/app.asar/index-09030ac4.js:118:34906)
    at N (file:///Applications/Insomnia.app/Contents/Resources/app.asar/index-09030ac4.js:103:1615)
    at Immediate.me [as _onImmediate] (file:///Applications/Insomnia.app/Contents/Resources/app.asar/index-09030ac4.js:103:1987)
    at process.processImmediate (node:internal/timers:476:21)

Same here

Downgrading to previous versions didn't work for me.
Switching to Postman ¯_(ツ)_/¯
...and hoping I get my saved queries somehow in the future.

I got this as well with today's upgrade to 8.4.2.
My about window shows:
Version: Insomnia 8.4.2
Build date: 11/15/2023
OS: Windows_NT x64 10.0.22631
Electron: 27.0.3
Node: 18.17.1
Node ABI: 118
V8: <IP_ADDRESS>-electron.0
Architecture: x64

Same here
Version: Insomnia 8.4.2
Build date: 11/15/2023
OS: Darwin arm64 22.4.0
Electron: 27.0.3
Node: 18.17.1
Node ABI: 118
V8: <IP_ADDRESS>-electron.0
Architecture: arm64

I'm experiencing this issue after upgrading as well. I tried removing the app, then reinstalling, this seeing the error.
Version: Insomnia 8.4.2
Build date: 11/15/2023
OS: Darwin arm64 23.1.0
Electron: 27.0.3
Node: 18.17.1
Node ABI: 118
V8: <IP_ADDRESS>-electron.0
Architecture: arm64

Are these errors happening going from 8.4.1 to 8.4.2, or are these errors happening going from 8.3.x to 8.4.x ?

Like everyone else, I've been freaking out on the sudden loss of Insomnia since permitting the update to 8.4.2. I was about to try deleting local storage (suggested above by Dammien as a possible fix), but was able to get my functionality back instead by simply using File > New Window. I hope that trick works for others.

@subnetmarco I was on 8.4.1 going to 8.4.2.

99.9% sure this was a temporary server-side error that didn't get handled properly by the front-end. Everything is back to normal now.

We have identified the problem on our end. Restarting the application will resolve this problem.
We will be shipping better error handling in 8.4.3 next week to handle this scenario, which absolutely should not be sending the application in this panicking state.
I will keep this ticket open until the error handling is put in place.

Hello 👋 Insomnia 8.4.3 has been shipped with important performance improvements that brings back a ton of speed in the UI. This issue has also been resolved.
You can wait for the auto-updater to download it for you, or you can manually download it here.


add Unity.gitattributes

I think the previous version is better. Git lfs is more useful for most unity projects, this pull request shouldn't be merged.

@ZhengzhongSun The only problem here is that Git LFS does not ship with Git and the external Git hosting provider needs to support it.

OK. This should be more general. Is it better to add the Git LFS part to comment in the Unity.gitattributes? So the people who need it can easily uncomment them and use it.

@ZhengzhongSun Since it would essentially double the file size in order to add commented code, I'll just add instructions to the file.

@ZhengzhongSun Fixed in https://github.com/alexkaratarakis/gitattributes/commit/29e644640454f1fab454a5fcd5c5a40e3e90aee5.

@ZhengzhongSun OK. But I usually see it should be "filter=lfs diff=lfs merge=lfs -text". I'm not sure if it will have problems only use diff=lfs merge=lfs.

@ZhengzhongSun -text is part of a shorthand for binary. It should be fine.


output flannel vars as docker command line options

Add two new options:
-docker-fmt=false
-docker-fmt-prefix=DOCKER_NETWORK_OPTIONS
These will switch from
FLANNEL_SUBNET=<IP_ADDRESS>/8
FLANNEL_MTU=1450

to:
DOCKER_NETWORK_OPTIONS="--bip=<IP_ADDRESS>/8 --mtu=1450"

So the docker unit file can import the env file and use it as docker
command line options.

ExecStartPost is not necessarily finished before system considers a service 'ready'.
I tried to fix it cleanly using only systemd.  uggh.  I still think this pr is the better solution.
http://pkgs.fedoraproject.org/cgit/flannel.git/commit/?id=8d0e6c275d6eb3c779d4f3f5e29b84dd865796b2
Tell me that's not horrific!  I need a new 2 new unit files and a generator...

@eparis I recently retested ExecStartPost (with a long sleep) and it waited for it to complete before marking the service ready. At command line, systemctl start foo.service would not return until ExecStartPost finishes. Of course, there's a timeout on the whole service starting but that's pretty long.

I just retested and it worked as well.  Liar   :)

Replaced with https://github.com/coreos/flannel/issues/93


Blockchain catchup progress

The main change here is the third commit, 8c7d368ee, which improves the reporting of the remaining number of blocks needed to catchup to the blockchain.
There are a handful of other cleanups in here, mostly styling and improved logging.
This is needed for https://github.com/lbryio/lbry/pull/450

This also fixes https://app.asana.com/0/198587529699250/251594103872284

lgtm


Add Jekyll 4.x support

Just updated the dependency because it seems to work fine with the latest Jekyll version.

Huh!? How on earth did I not know about this PR? Sorry about this. I'll get CI fixed and merge this this week.

Huh!? How on earth did I not know about this PR? Sorry about this. I'll get CI fixed and merge this this week.


Opening workflow created in 2024.5.1-rc2 in 2024.4.2 breaks layout

All of my layout gets broken when I open a 2024.5.1-rc2 workflow in 2024.4.2

Notes from standup discussion:

The proper fix would be to add metadata versions, and handle them properly (or warn user that the format is too new and any edit would break it).

If the older version cannot handle it, we cannot do much except making 2024.4.3.

There is a solution:

necessary: turn stored metadata into a comment so that last release IDE ignores the comment and does not try to parse it as metadata as that would fail
future proof - add version to the metadata and if it is new than expected (produced by some future IDE) then don't read it at all - tracked as #11479


Allow all of Sequelize options in config.sequelize

http://docs.sequelizejs.com/en/v3/api/sequelize/#new-sequelizedatabase-usernamenull-passwordnull-options
Issue from: eggjs/egg#341
for example:
exports.sequelize = {
  port: '3306',
  host: 'localhost',
  username: 'root',
  password: '',
  database: 'test',
  dialect: 'mysql',
  pool: {
    max: 5,
    min: 0,
    idle: 10000,
  },
  storage: 'db/test-foo.sqlite',
  timezone: '+08:01',
};

Do not assert config.host, password, port config, let them has default value.
Do not assert config.database, because SQLite case is not needs it.

Checklist

[ ] npm test passes
[ ] tests and/or benchmarks are included
[ ] documentation is changed or added
[ ] commit message follows commit guidelines

Affected core subsystem(s)

Description of change

我发 patch

@jtyjty99999 我发不了，只能你来发。

npm owner 加一下我们吧

修改 Changelog

@huacnlee  changelog 在 release 的时候用命令生成的

adamsdeMacBook-Pro:egg-sequelize adams$ npm publish
+<EMAIL_ADDRESS>adamsdeMacBook-Pro:egg-sequelize adams$ npm owner add fengmk2
+ fengmk2 (egg-sequelize)


Update icon for installer/helper (macos)

Updates icon for the installer/helper (copied from media/Keybase.iconset).

@cecileboucheron
cc @keybase/react-hackers

Looks good to me