Connecting 2nd monitor not working

Hello.
I just reinstalled MacOS with your 0.6.5 OC but im having issues with my 2nd monitor.
if i use the normal config.plist, the 2nd monitor is not detected and is like is not there
if i use the Config-4720HQ.plist, as soon as i connect the hdmi cable, it reboot my laptop.
I have a FullHD Lenovo y50-70.
I installed first 15.0.1 then updated to 15.1, and thats all the changes i made.
i also did setup GenSMBIOS stuff
Thanks in advance

Hello @ezesolares , the 4720hq config might not work properly, because my cpu is 4710hq, and I can't test.
Your 2nd monitor was working fine before the update?

Hello @ezesolares , the 4720hq config might not work properly, because my cpu is 4710hq, and I can't test.
Your 2nd monitor was working fine before the update?

it was working fine on the 0.6.3 version of your EFI but i decided to reinstall everything for the 0.6.5.... i didn't try my 2nd monitor before updating from 15.0.1 to 15.1 tho.

@ezesolares Please grab the newest EFI and generate new SMBIOS or keep your config.plist just change SMBIOS to MacBookPro11,4 and generate a new SMBIOS.

@ezesolares Please grab the newest EFI and generate new SMBIOS or keep your config.plist just change SMBIOS to MacBookPro11,4 and generate a new SMBIOS.


Use for archiving?

Thank you for that. It's very helpful. Could we consider a system that allows you to periodically "download" annotations and comments to an "org" file... to build up a kind of archive ?
By the way, why is it limited to 50 ?

Hi! Yes downloading new annotations and appending them to (or perhaps adding to the front of) an existing file seems like a useful feature.
50 is just a number I picked. If I remember correctly the web-API standard is 20 (if no argument is given) and the max is 200.

Yes. And I can see the use for an integration in org-brain ;-)
50 annotations is enough if you can periodically store them offline in a file... but after a day of working on different documents you may have exceeded them.

I've added hypothesis-to-archive (see the README). I've also set the limit of imports to the max (200). Seems to work well for me :)

It works for me too ! Thanks.


[backport] Prioritize FlexCI daemon in Windows CI

Backport of #4916

[automatic post] Jenkins, test this please.

Jenkins CI test (for commit 2fce3f83fd9cf2eeec9d07de79d8579f9e247857, target branch v8) failed with status FAILURE.

Ignore jenkins message above.

00:00:08.427039 STDOUT 3796] | Prioritizing FlexCI daemon process... |
-- | -- | --
00:00:08.552125 STDOUT 3796] | Executing (\\WINSERVER2016-G\ROOT\CIMV2:Win32_Process.Handle="4016")->setpriority() |
00:00:08.572264 STDOUT 3796] | Method execution successful. |
00:00:08.572264 STDOUT 3796] | Out Parameters:

Let's merge it manually as Jenkins did not run :)


Tensorflow model.fit fails on test_step: 'NoneType' object has no attribute 'items'

I am using tf.data module to load my datasets. Although the training and validation data modules are almost the same. The train_step works properly and the training on the first epoch continues till the last batch, but in the test_step I get the following error:
    353     val_logs = {
--> 354         "val_" + name: val for name, val in val_logs.items()
    355     }
    356     epoch_logs.update(val_logs)
    358 callbacks.on_epoch_end(epoch, epoch_logs)

AttributeError: 'NoneType' object has no attribute 'items'

Here is the code for fitting the model:
results = auto_encoder.fit(
    train_data,
    epochs=config['epochs'],
    steps_per_epoch=(num_train // config['batch_size']),
    validation_data=valid_data,
    validation_steps=(num_valid // config['batch_size'])-1,
    callbacks=callbacks
)

I should mention that I have used .repeat() on both train_data and valid_data, so the problem is not with not having enough samples.

Hi @JVD9kh96 -
Can you help me with full code with dummy dataset to reproduce error ?


dashboard.js guild.members.cache.get not working

With the recent changes to discord.js, this will need to be changed from:
const member = guild.members.cache.get(req.user.id);
to
const member = await guild.members.fetch(req.user.id);

May you create a pull request with the required updates?

I've done that but not sure how to link that pull request to this issue

To solve this issue as quickly as possible I made the pull request https://github.com/MrAugu/simple-discordjs-dashboard/pull/17 .

@m0ri-wk
I did test it with const member = guild.members.cache.get(req.user.id);
and it works perfetly fine.
Therefore i closed https://github.com/MrAugu/simple-discordjs-dashboard/pull/17 .

mmm not for me tho

Ok, I was seeing the issue in a large member server. Check this https://discord.com/channels/222078108977594368/222078108977594368/771434053244944494 for where I found out about it. If the Discord.js Official server.

If this issue persists, please bring conclusive information which we can make decisions of and fix any issues. As there is nothing I can do from this little information considering it works for other people I will close this issue.


Using forced alignement

Hello , If I have an original transcript ( txt file ) , is there anyway to improve the timestamps generated using forced alignement or any other technique ? I tried playing with the inital prompt parameter but I can see any real improvement.
Thanks for any help !

You can try to use whisper.timing.find_alignment().

@jianfch  do you have some example code ? I'm not sure which params work best for the tokenizer and text_tokens

Try https://github.com/jianfch/stable-ts#alignment with the new update.

Is there an ability to use alignment via CLI? If so, where can I find the commands?

Is there an ability to use alignment via CLI? If so, where can I find the commands?

It was added in c90ff06bc55694034994010e05b5fc2f50070b03.
stable-ts audio.mp3 --align text.txt --language en


NMS on categories

Thanks for your share. I run you code on my dataset, and inferece it, i find that there maybe several predicted boxes on a target with different categories. The cfgs about NMS is :
NMS = True
NMS_IOU_THRESHOLD = 0.05
MAXIMUM_DETECTIONS = 40
FILTERED_SCORE = 0.5
VIS_SCORE = 0.5

I guess that you didn't do NMS between different categroies, but it's what I need. So where should I fix?

NMS is not required between different categroies. You should first observe whether the confidence threshold is too small. If the confidence between the categories is similar, it means that the model recognition ability is not good. @rai-ss

NMS is not required between different categroies. You should first observe whether the confidence threshold is too small. If the confidence between the categories is similar, it means that the model recognition ability is not good. @rai-ss

What if the two different categories has similar shape but I still want to distinguish them. Is it nms an alternative way?
Besides, I want to ask that what's 'FILTERED_SCORE' used in your code. Is it the confidence threshold?

FILTERED_SCORE is confidence threshold for visualization. If you do nms between classes, the result may be worse. You may need to improve the classification capabilities of the model to solve your problem.


Generate list of blocking upstream dependencies?

I'm trying to update past a critical severity alert, but got the message Dependabot cannot create a pull request as one or more other dependencies require a version that is incompatible with this update.
That makes sense, and I can look through yarn.lock to see what dependencies must be updated to allow dependabot to create the PR, but it's laborious and error-prone to do this manually. I was wondering if there could be a feature to somehow list out which dependencies are blocking the critical severity one, and offer to open PRs for those too, to make a kind of tree of pre-dependencies (for lack of a better term). This could fast-track a course of action which addresses critical severity alerts.
Right now, we have a lot of dependabot PRs which we work through as we're able to, but we're not aware of if we're making progress towards the critical severity ones.
Thanks, we :heart: dependabot!

I would love a fix for this.  Recently encountered this on a default project generated for the popular Express framework: https://github.com/expressjs/generator/issues/258  I'm sure Dependabot knows what the conflict is...it'd be super helpful to have it share the details!  :)

We shipped a lot of improvements for this behavior with the NPM ecosystem:

https://github.blog/changelog/2022-09-07-dependabot-unlocks-transitive-dependencies-for-npm-projects/
https://github.blog/2023-01-19-unlocking-security-updates-for-transitive-dependencies-with-npm/

It's not a complete fix, but it addresses many of the scenarios that resulted in blocked updates.
While this issue makes sense in theory, it's not very actionable. It doesn't specify which ecosystem... much of this unlocking logic is custom per-ecosystem, so we need to know where it's being hit. And generally Dependabot doesn't know what is blocking--if it did, it'd include it in the PR. Instead, what may be happening is we may get a log message that Dependabot hasn't been taught how to parse, so it's simply treating it as a wall of text that we expose in the job logs.
So I'm going to close this, and if you do hit this in specific situations, please file a new bug and include more specifics so we can figure out the actual blocking bug for that particular scenario.


install missing host cli via bind-utils

strange that test is failing

@rimusz  failure has nothing to do with your change, so the other potential cause I see here is terraform-dcos not being compatible with the newest version of terraform, because this test always pulls latest terraform version

I'm going to merge this one then, as it is breaking kubernetes framework work


Improve the performance of the HTTP API for getting all regions (#1970)

What problem does this PR solve?
cherry-pick #1970 to release-3.0
What is changed and how it works?
Optimize convertToAPIRegions and h.rd.JSON
Check List
Tests

Unit test

Related changes

Need to be included in the release notes

Codecov Report

:exclamation: No coverage uploaded for pull request base (release-3.0@7a5909e). Click here to learn what that means.
The diff coverage is 100%.

@@              Coverage Diff               @@
##             release-3.0    #1986   +/-   ##
==============================================
  Coverage               ?   69.42%
==============================================
  Files                  ?      170
  Lines                  ?    16757
  Branches               ?        0
==============================================
  Hits                   ?    11634
  Misses                 ?     4144
  Partials               ?      979

Impacted Files
Coverage Δ

server/core/region.go
93.47% <100%> (ø)

server/api/router.go
100% <100%> (ø)

server/api/region.go
68.8% <100%> (ø)

Continue to review full report at Codecov.

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

/run-all-tests


Add token metadata service documentation to docs

Token metadata service docs

Add a brief description
What problem it solves/the reason for introducing this service
Add a link to the service. (Currently, this link is under References in the top nav)

Question/Thought:

Sounds more like a feature guide than a how-to document?
stacks-blockchain-api/feature-guides/ would be a good place?

Content already exists here - https://github.com/hirosystems/token-metadata-service/blob/develop/README.md". Reach out to Rafael for any further questions/details.

https://github.com/hirosystems/token-metadata-service/pull/89


chore: remove async-trait

Checklist

[ ] I have linked to any relevant issues.
[ ] I have updated the documentation.
[ ] I have added tests that prove my fix is effective or that my feature works.
[x] I have added necessary labels.
[x] I have done my best to ensure that my PR adheres to the Fuel Labs Code Review Standards.
[x] I have requested a review from the relevant team or maintainers.

@MujkicA Any update?
@hal3e did you sort out the object safety issues with @MujkicA ?

Because of lack of support for dynamic dispatch, it was agreed that we stick to the async-trait crate for now.
There is no indication that we need the performance gain from not Boxing futures at trait boundaries (e.g. TransactionBuilder).
We might still want to consider sealing some of our more complex traits to minimise breaking changes.

Because of lack of support for dynamic dispatch, it was agreed that we stick to the async-trait crate for now.
There is no indication that we need the performance gain from not Boxing futures at trait boundaries (e.g. TransactionBuilder).
We might still want to consider sealing some of our more complex traits to minimise breaking changes.


Improve T29 test case

Improve T29 test case: https://issues.redhat.com/browse/OSSM-3031

Change reviewed and approved on https://github.com/maistra/maistra-test-tool/pull/360


Update instructions to re-lock conda-lock.yml file

Remove the --platform linux-64 flag since unified lockfile is for linux-64, osx-64 and osx-arm64 as of #164. Also re-locking the conda-lock.yml file after 2a9ef9d6d73bd0c20b0ce04d32b6f1cfac8bd5cf/#193.
Patches #164, resolves https://github.com/Clay-foundation/model/pull/193#issuecomment-2066410721.

Merging directly to fix broken tests on main branch.


Sending notification via swagger-ui for openapi fails with 415, same notification via swagger suceeds

Describe the bug
Tried to send
{
  "message": "We will have downtime on Thursday August 13th around 12:30 PM PST or 3:30pm EST for a new minor release of Dockstore.",
  "expiration": "2020-08-14T20:20:02.221Z",
  "type": "SITEWIDE",
  "priority": "LOW"
}

When using https://dockstore.org/api/static/swagger-ui/index.html#/curation/createNotification
It died with
{
  "code": 415,
  "message": "HTTP 415 Unsupported Media Type"
}

Pointed swagger-ui at https://dockstore.org/api/swagger.yaml
The same thing succeeded
Additional context

Webservice version: [e.g. 1.9.0]

┆Issue is synchronized with this Jira Story
┆Issue Type: Story
┆Sprint: Backlog
┆Issue Number: DOCK-1530

Confirmed that I was able to create and delete a notification via OpenAPI on dev


Setup a licence

get input form @JimCircadian

@scotthosking MIT is fine. If you're up for it, I can show you how to rewrite the git history to include the license in all revisions. It does rewrite the history, but it's probably worth doing

Hi @JimCircadian, only just saw this message - would be great to look at this at some point as the repo is having a new burst of life thanks to @magnusross

I'll stick it in the list for next week and ping you a slack message. Shouldn't take long!

I've just added the MIT licence - no rush on the history revision update

I was also wondering the same - just leaving it and using the licence from here on. Thanks for looking into this


BREAKING enable aks nodepool to set os_disk_type

The default nodepool OS disk type is Ephemeral in AKS. But terraform has not
changed this, to avoid breaking changes. The Ephemeral disk type
will decrease boot time.

Getting funny errors:
│ Error: creating/updating Managed Kubernetes Cluster Node Pool "standard" (Resource Group "rg-dev-we-aks"): containerservice.AgentPoolsClient#CreateOrUpdate: Failure sending request: StatusCode=400 -- Original Error: Code="VMCacheSizeTooSmall" Message="The virtual machine size Standard_D2ds_v5 has a cache size of 0 bytes, but the OS disk requires<PHONE_NUMBER>0 bytes. Use a VM size with larger cache or disable ephemeral OS."
│
│   with module.aks1.azurerm_kubernetes_cluster_node_pool.this["standard"],
│   on .terraform/modules/aks1/modules/azure/aks/aks.tf line 74, in resource "azurerm_kubernetes_cluster_node_pool" "this":
│   74: resource "azurerm_kubernetes_cluster_node_pool" "this" {

This is how it looks if you try to add to much os disk compared to what the node type supports.
│ Error: creating/updating Managed Kubernetes Cluster Node Pool "standard" (Resource Group "rg-dev-we-aks"): containerservice.AgentPoolsClient#CreateOrUpdate: Failure sending request: StatusCode=400 -- Original Error: Code="VMCacheSizeTooSmall" Message="The virtual machine size Standard_D2ds_v4 has a cache size of<PHONE_NUMBER>0 bytes, but the OS disk requires<PHONE_NUMBER>0 bytes. Use a VM size with larger cache or disable ephemeral OS."
│
│   with module.aks1.azurerm_kubernetes_cluster_node_pool.this["standard"],
│   on .terraform/modules/aks1/modules/azure/aks/aks.tf line 74, in resource "azurerm_kubernetes_cluster_node_pool" "this":
│   74: resource "azurerm_kubernetes_cluster_node_pool" "this" {
│
╵
make: *** [Makefile:80: apply] Error 1

Below you can find examples of how to keep on using the module without changing any of your node pools.
This by setting os_disk_type =  "Managed" and os_disk_size_gb = null
You will also find a example on how to use Ephemeral disk.
  additional_node_pools = [
    {
      name                 = "standard2"
      orchestrator_version = "1.21.2"
      vm_size              = "Standard_D2s_v5"
      min_count            = 1
      max_count            = 3
      node_labels          = {}
      node_taints          = []
      os_disk_type         = "Managed"
      os_disk_size_gb      = null
      spot_enabled         = false
      spot_max_price       = null
    },
    {
      name                 = "standard"
      orchestrator_version = "1.21.2"
      vm_size              = "Standard_D2ds_v4"
      min_count            = 1
      max_count            = 3
      node_labels          = {}
      node_taints          = []
      os_disk_type         = "Ephemeral"
      os_disk_size_gb      = 60
      spot_enabled         = false
      spot_max_price       = null
    },

We will provide more documentation around this during the coming week.


asdf validation error

The purpose of this PR is to illustrate a failing example. The schema is included here although for the example to work it should be placed under asdf-standard/schema/.../transform. The error I get is
ValidationError: mismatched tags, wanted 'tag:stsci.edu:jwst_pipeline/test_fail-1.1.0', got 'tag:stsci.edu:asdf/transform/test_fail-1.1.0'

The example to trigger the error:
from astropy.modeling import models as astmodels
from asdf import AsdfFile
from asdf.tags.transform import test_fail
fa=AsdfFile()
m=test_fail.TestFail(astmodels.Shift(1))
fa.tree['model']=m
 fa.write_to('test_fail.asdf')

If I don't specify version='1.1.0' in TestFailType, it defaults to version 1.0.0 and the error is
ValidationError: mismatched tags, wanted 'tag:stsci.edu:jwst_pipeline/test_fail-1.1.0', got 'tag:stsci.edu:asdf/transform/test_fail-1.0.0'

This only happens when a specific transform is defined in the schema, like shift-1.1.0 here. If instead the schema requires transform-1.1.0, it works. Since all schemas we have in JWST sofar need a general transform and not a specific one this error just surfaced now.
This is a simplified version of the real use case. @drdavella Do you see anything wrong with the example? If not, is this sufficient information to debug it?

Coverage decreased (-0.1%) to 94.27% when pulling 350b49a8cc11f80e120c514aeb9abba172d8b66b on nden:issue-versioning into 6956b2baf82784056cd8075f37cd1a8453e7e93c on spacetelescope:master.

@nden, I think the problem is that by default the standard field for an AsdfType object is asdf unless it is redefined in the child class. In this case, I believe that if you add standard = 'jwst_pipeline' to the definition of TestFailType, it should work.

@drdavella I was trying to make a simple example showing the problem and forgot to change the standard. However, the example here is supposed to run/work within asdf and changing the standard in the schema definition to asdf does not help. I updated the schema to use standard=asdf. It only fails if a specific model is defined in the schema (in this example shift). If I specify transform instead it works. Any other concrete transform fails.

@nden, sorry I guess I skimmed the description of your issue a little too quickly. Is the error you get still the same? The error you pasted above seems to be related to the difference in values for standard, so I'm not sure if that was the original issue or just a side effect.
The current version of the code fails because the tag is under asdf/test_fail-1.1.0 but the relative schema path is to ../asdf/transform/shift-1.1.0. which doesn't make sense. Is the tag supposed to be asdf/transform/test_fail-1.10?
If I change the tag, then I get a different failure which is maybe what is actually wrong.

@nden I think I might actually know what the problem is. The version field of TransformType was never bumped to 1.1.0 when the associated schemas were updated. Since ShiftType inherits from TransformType, it is also pegged at the older version 1.0.0, so the library can't find the right version of the schema.
This has been fixed on #294 and can be merged. That PR is based on #284 though, and that will need to be merged as well. I'm not sure if you want to review them quickly or whether I should just go ahead and pull them in.

@drdavella You are right. Bumping the version field of TransformType fixed it. I'll take a look at the PRs now.

@nden if it's easier we can just do a quick patch for the version now. I would like to get those PRs merged at some point though.


version change to 0.5.1

Close application on authorisation failure

This change is

r? @ustulation
(maidsafe_highfive has picked a reviewer for you, use r? to override)


Differentiation between metric and resource attributes

This PR only includes some refactors but does not yet do any effective change.
It is an incremental PR for later moving to the resource level some attributes that are wrongly put in the metrics-level.

Codecov Report
Attention: Patch coverage is 94.21488% with 7 lines in your changes missing coverage. Please review.

Project coverage is 50.56%. Comparing base (9c0a4aa) to head (b469657).

Files
Patch %
Lines

pkg/internal/export/attributes/attr_selector.go
92.98%
2 Missing and 2 partials :warning:

pkg/internal/export/otel/traces.go
0.00%
1 Missing and 2 partials :warning:

Additional details and impacted files
@@             Coverage Diff             @@
##             main     #984       +/-   ##
===========================================
+ Coverage   36.32%   50.56%   +14.23%
===========================================
  Files         133      134        +1
  Lines       10642    10688       +46
===========================================
+ Hits         3866     5404     +1538
+ Misses       6363     4922     -1441
+ Partials      413      362       -51

Flag
Coverage Δ

oats-test
?

unittests
50.56% <94.21%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Responsive work done

#105
Proposed Changes
Made Landing Page Responsive.
Navbar made sticky
Display Campaign cards aligned.
Some changes done in other pages to look good in smaller devices.
Check List (Check all the applicable boxes)

[ ] Bug(s) fixed
[ x] Enhancement done
[ ] New Feature(s) added
[ ] Documentation changed
[ ] All new and existing tests passed.
[x ] My code follows the code style of this project.

Screenshots (if any)

Hamburger icon already added for small devices and it's work fine so I didn't change it.
@LakshaySK106 Please review it.

Thank you for your contributions!


Option to disable automatic removal

Hello and thanks for this very necessary plugin !
I enabled "Only update if frontmatter property exists" because I don't want to use plugin vault-wide; but only in some files.
So I created a template with a null "cover" property, so i can add an image after I created the note.
After the note creation, when I add an image , the cover property doesn't get updated.
So I've tried adding a placeholder value as cover: "![[coverimage.png]]" to my template. But this time, the property is automatically removed because there isn't a ![[coverimage.png]]present.
Can we please have the option to disable auto removal of the featured image property?
This is also necessary because, a user may delete and add another image to a note while note-making. And if the featured-image-property gets removed during that, a lot of manual work is needed again...

Alternatively, an option for "Included Folders" list can work. So a user can only adress a few selected folders rather than excluding a lot of folders/subfolders.
Thanks again for everything .

Hi, thanks for the positive feedback! I just published 1.1.4 it has a new setting "Keep empty property". 👍

Thank you for your quick reply and fix :)
Now it allows for an empty property  but it doesn't update the (empty)  property value when I add an image into the note.
The property value stays at "" or just blank.

Here's a demo:
https://github.com/user-attachments/assets/69256a12-547d-4d1b-bab3-d32e69bc8c0b

Hi, I just published 1.1.5 it should fix this issue, thanks a lot for the video! 👍

Awesome, thank you 🍫


IDEM-44

#44

update .env
update readme
handle digital surge error message
generate password on proxy instead

Seems we should merge #57 first?


ops::Index now takes index by value

update for rustc 1.0.0-nightly (123a754cb 2015-03-24) (built 2015-03-25)

Thanks for the PR. I fixed this myself before seeing this. Commit: 8f526231d84b6b5afa03a0ca5607cf73df271889


Extension breaks otherwise working site

I'm working on a beat production app. You can see it in progress here:
http://bb.upchicago.org
I was really excited to try this chrome extension, but as you can see if you visit the site with the extension installed, you get a node connecting error of some sort:
Uncaught Error: error connecting to node: [object DynamicsCompressorNode]
Uninstall the extension and the site immediately works again.
Any ideas? Happy to change my code to make this work, just not sure where to begin.
Thanks!

Thanks for the report. That exception cloaks the underlying one:
DOMException: Failed to execute 'postMessage' on 'Window': An object could not be cloned.
    at C (<anonymous>:1:305)
    at GainNode.<anonymous> (<anonymous>:10:30)
    at GainNode._nativeConnect (<anonymous>:9:56)
    at GainNode.AudioNode.connect (http://bb.upchicago.org/static/js/app.891adfaa3720a4a3f3a3.js:7:1598)
    at GainNode.AudioNode.connect (http://bb.upchicago.org/static/js/app.891adfaa3720a4a3f3a3.js:7:1540)
    at t.Gain.n.connect (http://bb.upchicago.org/static/js/app.891adfaa3720a4a3f3a3.js:7:4231)
    at t.Volume.n.connect (http://bb.upchicago.org/static/js/app.891adfaa3720a4a3f3a3.js:7:4231)
    at t.MembraneSynth.n.connect (http://bb.upchicago.org/static/js/app.891adfaa3720a4a3f3a3.js:7:4231)
    at new e (http://bb.upchicago.org/static/js/app.891adfaa3720a4a3f3a3.js:14:22232)
    at R (http://bb.upchicago.org/static/js/app.891adfaa3720a4a3f3a3.js:14:6194)

WAI can't JSON-serialize a message (noting that a connection was made) being sent to the extension. That's because the 2nd argument to connect is a t.Distortion object (probably from tone JS) instead of a number. That may be a bug you want to fix.
That being said, the Web Audio API behaves gracefully in that case and defaults to 0, so I think WAI should too. This change prevents WAI from breaking your app.
https://github.com/google/audion/commit/7c9b3c924cf994a6eea60b42f9a2624fe3d713a7
I will tag a new release within this week.
Unfortunately, we still can't see the graph even after the fix because I think the app has a draw loop that is adding a bunch of nodes on every redraw - at a pace too fast for WAI to keep up with. Basically, the graph is expanding too rapidly, so the page freezes :(

Thanks for the quick and detailed response! there was indeed a Tone.js connect() that should have been a chain; fixing that allows the extension to load, so that's cool. I'm glad we could each help each other find a bug :)
And you're right that when I load it up I see the graph, but then I run out of memory in chrome real quick. I didn't think my draw loop added nodes, but I'll have to do a deep dive and see what's going on - certainly once the app loads, no new nodes should be getting added for a while. This tells me there may be some significant performance improvements should I be able to fix this, which is potentially a very good thing - so audion is already helping :)

Yes! I am glad as well. Also, I think the Chrome timeline recordings (flame charts) are great for culling work that is scheduled by calls to requestAnimationFrame.
Keep us posted, and let me know any issues / feature requests!

@chihuahua in case you're curious, it looks like the problem we're seeing happens in tone.js, since it's easy to see in the tone.js examples as well, for instance here.
I'm going to investigate and get in touch with the maintainer if I can't figure it out.
cheers!

Thank you for delving deeper! We want to support popular libraries like Tone.js, so this is important to know. I can repro what you said. I can see the graph loading, but the panel freezes relatively soon.

Yeah Tone.js is just the coolest thing.
I think it plays hard and heavy with the web audio API tho - it's kind of like original jquery played pretty hard with javascript and the dom, and for a while browsers were struggling to keep up - in my experience, tone is rough with the web audio API even in modern chrome, and you can really start to see that when you try to eg graph the nodes.
I'm about to be funemployed for a while, and I'm very interested in getting involved with OSS web audio. I'll be opensourcing my little project as well.
So I'm happy to help in any way I can!

That is good to hear because we certainly have much work to do. I'll soon file a few substantive issues (varying in scope) that want help. Bear in mind that I am not sure how influential this project will ultimately be or where it is exactly heading. Feedback supports how this extension addresses a key need, but I think the extent of its impact is in the air. We'll do whatever we can to confer upon you due credit though.

I posted a few issues and marked them with "help wanted". Feel free of course to propose your own ideas as well!

cool. I will dive into the codebase a bit now but I won't really be free until next week.

Sure thing! No rush at all.


Fix for conditional single gate plotting using mpl

Summary
Fixes #7017.  Minor bug fix involving plotting of QuantumCircuit object when using conditional single gates like circuit.h(0).c_if(0, True).

This is an unexpectedly short fix :)
Does it make sense @TharrmashasthaPV and @enavarro51 ?

Probably need @TharrmashasthaPV to weigh in, but isn't this what #6259 fixes? (Which got stuck in CI, by the way).

@paniash do you mind adding a test?

Hey. I am just not sure if this is a complete fix. Because for one, the circuit
q = QuantumRegister(1,'q')
c = ClassicalRegister(2,'c')
circuit = QuantumCircuit(q, c)
circuit.h(0).c_if(1, True)
circuit.h(0).c_if(0, True)
circuit.draw('mpl')

outputs

The label is 0x1 irrespective of the bit the gate is conditioned on. Also, circuit.draw('mpl', cregbundle=False) breaks and if a gate is conditioned on a complete register like circuit.x(0).c_if(c,1), the drawer breaks.

@TharrmashasthaPV Thanks for pointing it out. Can you confirm if this issue is fixed in #6259? If so, then I'll close this PR.

Which got stuck in CI, by the way

Ups.. unstacking this.

https://github.com/Qiskit/qiskit-terra/pull/6259 merged. That seems to solve #7017. If #6259 is incomplete and this PR is the way to go, please reopen it.


Implement features taken from Dating Sim

Implement features taken from Dating Sim Engine (very old repo):
https://github.com/renpy/dse

There is nothing inside especially compared to the current design


New created columns inside @mutate is not immediately available within the call

Suppose the df does not have column x1 initially.
@chain df begin
    @mutate(
        x1 = 1,
        x2 = x1 + 1
    )
end

This works in dplyr but does work in TidierData. I wonder if it is possible to call the newly created column with the same call? Many thanks.

This is not yet supported due to how the underlying Dataframes.jl transform function behaves.
A more in depth discussion is available here


HBASE-27920:Skipping compact for this region if the table disable compaction

Details see: HBASE-27920

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

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

Jira says it affects 2.3 and 2.4, but this PR is intended to master. Can you clarify which actual versions are affected and make sure we target the correct branches?

Sorry for this.  What I described here is inaccurate.
I found this issue exists both 2.3 , 2.4 and master after analysing code, and I only submit pr for master in here

Please add UT for this extra condition.

I think it is difficult,beacause I just skip early for avoiding useless loop later.
We can get information whether the table enable compaction by calling r.getTableDescriptor().isCompactionEnabled(),  and if false, we really do not need to foreach region.stores in the next.

Please add more comments to say that this is just for skipping compaction earlier, and we also have other checks in other places.

Is this a bug, or are we actually skipping compaction later on?

It is not a bug and would skip compaction later. see code in here: Skipping compaction if we donot need it
In here, I mean we only skip early before we foreach region.stores if the table disable compaction.

Thanks for explaining it. Makes sense to me, approved this, just had a suggestion to "reword" the comment.

Is this a bug, or are we actually skipping compaction later on?

It is not a bug and would skip compaction later. see code in here: Skipping compaction if we donot need it
In here, I mean we only skip early before we foreach region.stores if the table disable compaction.

Thanks for explaining it. Makes sense to me, approved this, just had a suggestion to "reword" the comment.

Thanks for your comments, I will update later

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

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

The failed UT is not related. Let me merge.


Unable to get Gist to render in markdown files.

After following the docs and reading through the issues the closest issue I was able to find was "Issue with Gist". When I add the plugin and requirements I'm unable to get the Gist to render in any markdown file.
gridsome.config.js:
module.exports = {
  templates: {
    Doc: '/:slug'
  },
  plugins: [
    {
      use: '@gridsome/source-filesystem',
      options: {
        path: 'docs/**/*.md',
        typeName: 'Doc',
        remark: {
          externalLinksTarget: '_blank',
          externalLinksRel: ['nofollow', 'noopener', 'noreferrer'],
          anchorClassName: 'icon icon-link',
          plugins: [
            '@gridsome/remark-prismjs',
            'gridsome-plugin-remark-container',
            '@noxify/gridsome-plugin-remark-embed',
            {
              enabledProviders: ['Youtube', 'Codepen', 'JSFiddle', 'Gist'],
              Gist: {
                secureConnection: true
              }
            }
          ]
        }
      }
    },
    {
      use: '@gridsome/plugin-google-analytics',
      options: {
        id: process.env.GA_ID ? process.env.GA_ID : 'XX-999999999-9'
      }
    },
    {
      use: '@gridsome/plugin-sitemap',
      options: {
        cacheTime: 600000
      }
    }
  ],
  chainWebpack: (config) => {
    const types = ['vue-modules', 'vue', 'normal-modules', 'normal']
    types.forEach((type) => addStyleResource(config.module.rule('scss').oneOf(type)))
  }
}

main.js:
export default function (Vue, { router, head, isClient, appOptions }) {
  Vue.use(Vuex)

  // Set default layout as a global component
  Vue.component('Layout', DefaultLayout)

  // Add attributes to HTML tag
  head.htmlAttrs = { lang: 'en' }

  head.link.push({
    rel: 'stylesheet',
    href: 'https://github.githubassets.com/assets/gist-embed-d89dc96f3ab6372bb73ee45cafdd0711.css'
  })

  head.link.push({
    rel: 'manifest',
    href: '/manifest.json'
  })

  head.meta.push({
    name: 'theme-color',
    content: '#10c186'
  })

  head.meta.push({
    name: 'google-site-verification',
    content: process.env.GSV_META
  })

  head.meta.push({
    name: 'apple-mobile-web-app-status-bar-style',
    content: 'default'
  })

  head.meta.push({
    name: 'keywords',
    content: 'ePub, validation, OPF, CSS, XHTML, TOC, NCX'
  })

  // State
  appOptions.store = new Vuex.Store({
    state: {
      sidebarOpen: false
    },
    mutations: {
      toggleSidebar(state) {
        state.sidebarOpen = !state.sidebarOpen
      },
      closeSidebar(state) {
        state.sidebarOpen = false
      },
      openSidebar(state) {
        state.sidebarOpen = true
      }
    }
  })
}

foobar.md:
---
title: Foobar
slug: foobar
date: 2020-11-17
---

Bacon ipsum dolor amet alcatra pork turkey pork loin, short loin ground round pastrami t-bone. Jerky venison filet mignon bresaola leberkas tail t-bone sirloin.  Beef ribs bacon buffalo beef ground round short loin. Jowl ribeye ham tenderloin.   Burgdoggen tenderloin shank corned beef ham. Tail biltong capicola, meatball short loin ham hock sausage andouille ball tip.

when I run npm run develop and check http://localhost:8080/foobar I get:

https://gist.github.com/noxify/4663ce9b7bee433c125a2fc12150a043#file-file1-js

https://www.youtube.com/watch?v=dQw4w9WgXcQ

dependancies:
  "dependencies": {
    "@gridsome/plugin-google-analytics": "^0.1.0",
    "@gridsome/plugin-sitemap": "^0.2.1",
    "@gridsome/remark-prismjs": "0.0.6",
    "@gridsome/source-filesystem": "^0.6.0",
    "@gridsome/transformer-remark": "^0.3.4",
    "@noxify/gridsome-plugin-remark-embed": "^1.3.1",
    "graphql-playground-html": "^1.6.22",
    "gridsome": "^0.7.0",
    "gridsome-plugin-algolia": "^2.1.1",
    "gridsome-plugin-remark-container": "^0.1.3",
    "kind-of": "^6.0.3",
    "minimist": "^1.2.3",
    "serialize-javascript": "^3.1.0",
    "typeface-source-sans-pro": "^0.0.54",
    "vue": "^2.6.12",
    "vue-feather-icons": "^4.22.0",
    "vuex": "^3.1.1",
    "websocket-extensions": "^0.1.4"
  },
  "devDependencies": {
    "node-sass": "^4.13.1",
    "prettier": "^2.1.2",
    "sass-loader": "^7.1.0",
    "style-resources-loader": "^1.2.1"
  }

Is there something I am missing or do I have a conflict with my plugins? When I reference Gridsome Preview it would appear my structure is correct.

Hi @codingChewie
it seems your plugin configuration is not correct.
Can you please test it with the following remark definition:
remark: {
          plugins: [
            ['@gridsome/remark-prismjs'],
            ['gridsome-plugin-remark-container'],
            ['@noxify/gridsome-plugin-remark-embed', {
              'enabledProviders': [
                'Youtube',
                'Gist',
                'Codepen',
                'JSFiddle'
              ],
              'Gist' : {
                secureConnection: true
              }
            }]
          ]
        }

Let me know if it's not working, then i will setup a test project with your definition ( or will use your repo, if it's public ).
Regards,
Marcus

That resolved the issue.


What version of Avalonia are you using? Will have a look at this shortly. Only the current master has changes related to rectangle drawings.

@Gillibald  I use 0.9.0-preview9

This is only happening when an opacity other than 1 is used to render a stroked rectangle.

So, what does this mean from a practical point of view? I upgraded the version of Avalonia to 0.9.0-rc.1, however everything remains as before. Moreover, if I remove BorderThickness and BorderBrush, even though this removes the problem of blue button corners I get invisible border on disable button

and visible grey border on enabled button

This is the code of style:
<!-- login button style -->
  <Style Selector="Button.login /template/ ContentPresenter">
    <Setter Property="CornerRadius" Value="4" />
  </Style>
  <Style Selector="Button.login">
    <Setter Property="FontFamily" Value="Segoe UI, Ubuntu"/>
    <Setter Property="Background" Value="#002171"/>
    <Setter Property="Foreground" Value="#ffffff"/>
    <!--<Setter Property="BorderThickness" Value="2" />
    <Setter Property="BorderBrush" Value="#FF0000" />-->
  </Style>
  <Style Selector="Button.login:pressed /template/ ContentPresenter">
    <Setter Property="Background" Value="#001261"/>
  </Style>

To fix the problem I set BorderThickness property to 0. Pay attention that I got the same sizes as TextBox higher.
Disabled button:

Enabled button:

Style code:
<!-- login button style -->
  <Style Selector="Button.login /template/ ContentPresenter">
    <Setter Property="CornerRadius" Value="4" />
  </Style>
  <Style Selector="Button.login">
    <Setter Property="FontFamily" Value="Segoe UI, Ubuntu"/>
    <Setter Property="Background" Value="#002171"/>
    <Setter Property="Foreground" Value="#ffffff"/>
    <Setter Property="BorderThickness" Value="0" />
    <Setter Property="BorderBrush" Value="#002171" />
  </Style>
  <Style Selector="Button.login:pressed /template/ ContentPresenter">
    <Setter Property="Background" Value="#001261"/>
  </Style>

The issue is that the background brush and the pen's brush both get a multiplied value of the current opacity. So in the end one brush gets 50% opacity and the the second 0.5 * 0.5

To fix this you have to remove the opacity change on disabled state and instead apply brushes that have a fixed color. I am not sure how to fix this. Opacity should be applied once all drawing operations are executed and not in between. Thus needs further investigation.


modulesFromList: allow for import customization

I have plans to try and export devshell modules, this is part of that plan.

Looks good to me tho shall we add this while we are at it https://github.com/divnix/digga/blob/c162f5f46206346f431f3905642a8a9f17d42217/src/importers.nix#L3-L12
basically what I'm thinking of is function which accepts:

[ /path/to/file.nix ]
{ paths = [ /path/to/file.nix ]; }
{ paths = [ /path/to/file.nix ]; _import = customImporter; }
{ dir = /path/to/directory; }
{ dir = /path/to/directory; _import = customImporter; }

And probably assert is required so users could not define both paths and dir

Is it ok to merge this for now as an incremental improvement?
I like your idea a lot, I will probably get around to implementing it soon, but it will make things a little more complicated.


Add proxy support for endpoint Oauth security

Endpoint template changes related to [1].
[1] https://github.com/wso2/api-manager/issues/3259

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Update docs for K8s TaskRunner Dynamic Config

Description
Mostly a refactor of the docs added in #16510
While writing these docs, I realized that the use of a defaultKey in the dynamic config (that I suggested in the original patch) is not actually that helpful, so I removed it from the docs and the code.

This PR has:

[x] been self-reviewed.
[x] added documentation for new or modified features or behaviors.

@YongGang fyi

thanks for the reviews @vtlim @asdf2014 and @YongGang I believe this patch should have addressed all the comments

Overruling CI because the k8s extension is not tested in these integration tests


reactNative crashes indeterminately in Android 13 production

Description
reactNative crashes indeterminately in Android 13 production
{
  "name": "atms",
  "version": "1.7.5",
  "private": true,
  "scripts": {
    "android": "react-native run-android",
    "ios": "react-native run-ios",
    "start": "react-native start",
    "build": "cd android && ./gradlew assembleRelease",
    "build-win": "cd android && gradlew assembleRelease",
    "test": "jest",
    "lint": "eslint . --ext .js,.jsx,.ts,.tsx",
    "prettier": "prettier . --ext --write .js,.jsx,.ts,.tsx"
  },
  "dependencies": {
    "@ant-design/icons-react-native": "^2.3.1",
    "@react-native-async-storage/async-storage": "^1.15.5",
    "@react-native-community/masked-view": "^0.1.11",
    "@react-navigation/bottom-tabs": "^5.11.11",
    "@react-navigation/native": "^5.9.4",
    "@react-navigation/stack": "^5.14.5",
    "axios": "0.26.1",
    "jotai": "^2.2.1",
    "native-base": "^3.3.0",
    "react": "^17.0.1",
    "react-hook-form": "^7.11.1",
    "react-native": "^0.64.4",
    "react-native-device-info": "^8.1.7",
    "react-native-gesture-handler": "^1.10.3",
    "react-native-mmkv": "2.5.1",
    "react-native-pager-view": "^5.2.1",
    "react-native-reanimated": "^2.2.0",
    "react-native-safe-area-context": "^3.2.0",
    "react-native-screens": "^3.4.0",
    "react-native-svg": "^12.1.1",
    "react-native-tab-view": "^3.0.1",
    "react-native-webview": "^11.14.2",
    "react-qr-code": "^2.0.3",
    "styled-components": "^5.3.0",
    "styled-system": "^5.1.5",
    "swr": "1.2.0"
  },
  "devDependencies": {
    "@babel/core": "^7.12.9",
    "@babel/runtime": "^7.12.5",
    "@react-native-community/eslint-config": "^2.0.0",
    "@types/jest": "^26.0.23",
    "@types/react-native": "^0.64.5",
    "@types/react-test-renderer": "^16.9.2",
    "babel-jest": "^26.6.3",
    "babel-plugin-module-resolver": "^5.0.0",
    "eslint": "^7.14.0",
    "jest": "^26.6.3",
    "metro-react-native-babel-preset": "^0.64.0",
    "react-native-bundle-visualizer": "^2.2.1",
    "react-test-renderer": "17.0.1",
    "typescript": "^3.8.3"
  },
  "resolutions": {
    "@types/react": "^17"
  },
  "jest": {
    "preset": "react-native",
    "moduleFileExtensions": [
      "ts",
      "tsx",
      "js",
      "jsx",
      "json",
      "node"
    ]
  }
}

Steps to reproduce

React Native Version
0.64.4
Affected Platforms
Runtime - Android
Output of npx react-native info
windows 10

Stacktrace or Logs
![1728894593432](https://github.com/user-attachments/assets/567cf667-ac6c-4b1a-9cca-c2b362b475d9)

Reproducer

Screenshots and Videos
No response

@maxfrees We need a proper reproducer in order to debug this further. You can use this template.

@shubhamguptadream11  https://github.com/maxfrees/test-mobile  thank you

@maxfrees What are the steps to reproduce this crash?

@maxfrees What are the steps to reproduce this crash?

It will naturally collapse from time to time in production

@maxfrees
It seems that your React Native version is quite old. Please try updating to a newer version.
Additionally, without exact reproduction steps, it's very challenging for us to investigate the issue. The zip file you provided contains many other packages; it would be helpful if you could trim down the scope to just the relevant parts.
Thank you!


Allow jitter buffer to be implemented in GDScript

I think the current use of a jitter buffer obfuscates what should be a fairly transparent process that would allow for synchronicity with animations, events and visemes.
Capturing:
If you expose the VOIPInputCapture::_sample_buf_to_packet() function to GDScript then we can use a base AudioEffectCapture object and feed the VOIPInput object that wraps the Opus library like so:
while voipinputcapture.get_frames_available() >= 441:
    var samples = voipinputcapture.get_buffer(441)
    var opuspacket = voipinputcapture._sample_buf_to_packet(samples)
    transmit(opuspacket) # or packets.append(opuspacket)

For a bonus, _sample_buf_to_packet() could Repacketize multiple opus frames into a single opus packet when the length of samples is a multiple of 441.  (By the way, 441 audio frames is 10ms of sound at 44100Hz, which is resampled up to 480 audio frames at 48000Hz required by the Opus library.)
The reason the current design of send_test_packets -> emit signal packet_ready is unsatisfying is that we lose track of which packet corresponds to which time window since it's going out to a different callback function instead of returning to the caller.
The output Opus stream stutters for the very simple reason that there is a mismatch between _process() frame rate (60fps) and audio encoding rate (100fps).
Playback
I exposed a copy of the push_packet() function that returned the uncompressed samples:
PackedVector2Array AudioStreamVOIP::spush_packet(const PackedByteArray& packet)
The GDScript code for managing and playing the incoming stream is:
setup:

var staticvoipaudiostream = ClassDB.instantiate("AudioStreamVOIP")
$AudioStreamPlayer.stream = ClassDB.instantiate("AudioStreamGenerator")
$AudioStreamPlayer.play()
var playbackthing = $AudioStreamPlayer.get_stream_playback()

processing:

opuspacketsbuffer = [ ... ]  # filled from the networkthat
while playbackthing.get_frames_available() > 441 and len(opuspacketsbuffer):
    var frames = staticvoipaudiostream.spush_packet(opuspacketsbuffer.pop(0))
    playbackthing.push_buffer(frames)

Ther docs warn that AudioStreamGeneratorPlayback.push_buffer() is slow in GDScript, so the implementation of AudioStreamVOIP is probably good, if we also have the a get_opus_frames_available() to tell us how many empty slots are left in the jitter buffer.
It would also be a good idea to know how many frames are left in the buffer so we don't get the "NOT ENOUGH SAMPLES - frames:" error.  However I can't see a good function in the Godot libraries to base it on, other than float _get_playback_position().
Additionally, features like Forward Error Encoding (where it can fill in for missing opus packets) have to be managed outside of this library since the opus packets don't contain sequence numbers, so you have to tell the library when a packet is missing.
There's also a DTX (Discontinuous Transmission) feature that puts out 400ms long frames when there is silence.  Otherwise the Opus library assumes that everyone is talking all the time everywhere like it's a video conference where the only purpose of being online is to talk.  This is not how we play networked games, where there something other than just talking as an activity, and a VOX (Voice operated push to talk) system would be more appropriate, as well as being kinder on the bandwidth, and considerably more scalable.

I'm worried about this making the interface a lot more complicated than it needs to be - send_test_packets is a temporary function that i was going to replace at some point with a voip handling thread (almost) completely hidden from the user
I am not against extensibility, but something as high level as swapping out the jitter buffer could probably require a recompile, while I was hoping the actual godot interface would just be the most frictionless way for someone with an online FPS to get people talking to each other without having to figure out any of this

just to make it easier for me to understand:
imagine if all test packets were sent by a thread automatically that checked for new packets dependent on the sample rate, e.g. 100 times per second, and all you have to do is tell the voip instance which connection and channel to send the packets over
Imagine if the test packets are received by an ok sounding jitter buffer like discord's in case there's packet loss for a few seconds
What use case do custom gdscript jitter buffers solve that the above design doesn't? When would someone want this?


AWS: tags are generated in wrong way for security groups

Software versions:
$ terraform version
Terraform v0.12.2
+ provider.aws v2.16.0

$ terraformer version
Terraformer v0.7.5

(installed with brew)
Steps to reproduce:
terraformer \
    import  \
    aws \
    --resources=sg \
    --regions=some-region

Actual result:
  tags  {
    Name = "<some name here>"
  }

Expected result according to the terraform  documentation (https://www.terraform.io/docs/providers/aws/r/security_group.html)
  tags = {
    Name = "<some nema here>"
  }

Workaround:
replace with sed or other tool tags { --> tags = {

it's terraform 0.12 issue.
I tested terraform 0.12 in beta version with old provide(before 2.7) but now it's not working.
Need more changes for 0.12
https://github.com/GoogleCloudPlatform/terraformer/commit/43cef73abf2698ea8e10e4aa3139b7b7d4a1cab9

@sergeylanzman Are there any plans on adding a fix for this? If so, is there anything I could help with? If you point me in the right direction I might be able to open a PR

@fbongiovanni29
It's not an easy thing as just making a quick hack, the issue is related with move to Terraform 0.12, which introduces a lot of internal Terraform changes as well as hacks. I still try to work on https://github.com/meshuga/terraformer/tree/tf_12 to provide move to TF 0.12 but had to remove several providers in order to make the solution working. I managed to provide workable solution for AWS (at least hope so) although all other providers must be rechecked to verify they are working as expected + some of them must be reintroduced.

Thanks for the update!

Merged to master support 0.12 include support aws tags


Adaptive Card by using Nodemailer SMPT, but unable to open that card in email, need help..

Platform
I m doing a project in which we need to send adaptive card email with dynamic content and dynamic recipient but only all the member received but only open for who are in organization, is it required domain configuration with office.com account? what kind of provider we need, test user/organization/global or any other?
What platform is your issue or question related to? (Delete other platforms).

NodeJS

For support on Outlook Actionable Messages, please post a question on the Office Addins Dev site. If you need further help more specifically about Adaptive Cards, please let us know.
Thanks!


The docker compose runtime config for Redis

          > Could you please put the docker compose file like this PR #2858 ?

I don't think the docker compose file in the fixture directory is a good idea.
Normally, the misc file like dockerfile for developer, util script will be put into a split directory. FYI https://github.com/apache/zookeeper/tree/master/dev/docker
https://github.com/blockscout/blockscout/tree/master/docker-compose
Originally posted by @Zheaoli in https://github.com/apache/incubator-opendal/issues/2864#issuecomment-1677717447

Beside, in #2858, https://github.com/apache/incubator-opendal/pull/2858/files#diff-66d31d862c59877b8e265e0b23baea97975bbcfa336076b0eeaf24711d9b9c5dR6-R13
What it the container's IP CIDR is not <IP_ADDRESS>/24? the docker-compose file would not useable

What if the container's IP CIDR is not <IP_ADDRESS>/24?

Makes sense. Maybe we can generate a tls cert that using domain, for example: redis-node-1.local?

Makes sense. Maybe we can generate a tls cert that using domain, for example: redis-node-1.local?

emmm, should we ask the people to change their DNS?

I don't think the docker compose file in the fixture directory is a good idea.

Good enough for now. Contributors should only be aware of these files when they are ready to work on a specific service.

The main idea here is to avoid burdening our contributors with additional tasks. Since using docker-compose is already complex, I prefer not to require our contributors to generate certificates as well.

The cert would be expired in 300 days, we may need an auto bot to update the cert if we put the cert in the repo.

The cert would be expired in 300 days, we may need an auto bot to update the cert if we put the cert in the repo.

Not a big issue. We can generate a cert which expired after 100 years.


Removing the recursive check

There is no harm in having a canonical tag that says the current page
is the authoritative url.  By always rendering it, it is easier to test
for any problems, and there are some SEO experts that say  there is
benefit in always having it.

Thank for this, but please remove the whole renderCanonical method and just echo the tag if the canonical URL is set.

done.

Thanks.


FINERACT-1989: Add Spring Modulith

Automatic dependency diagram generation via Spring Modulith. Add module documentation stubs.

Still working on this.


version update 3.9.15

Checklist for Pull Requests

[ ] Have you signed the Contributor License Agreement?
[ ] Is there a linked Issue?

Manifests

[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?
[ ] This PR only modifies one (1) manifest
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.6 schema?

Note: <path> is the directory's name containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

Updated hash

Close with reason: Merge Conflicts;


Find a way to run the bot with GPU, as performance is currently not great

This seems to be the solution. I'm trying this right now:
https://stackoverflow.com/a/59952803/3919195

Ok, the link about does make it work. Performance is difficult to judge. It seems, that training might be faster, but


Upgrade to MediaWiki 1.39

MediaWiki 1.39 is the current LTS release.

[x] Rebase mudkipme/mediawiki to 1.39.0
[x] Rebase mudkipme/mediawiki-extensions-EventBus to REL1_39
[x] Upgrade all extensions to REL1_39 branch
[x] Upgrade Elasticsearch-52w to 7.x
[x] Upgrade docker base to PHP 8.1
[x] Switch to vector-2022 skin
[x] Update 52W:层叠样式表 to match vector-2022 skin
[x] Design new logo text (Simplified Chinese and Traditional Chinese) to match vector-2022 skin
[ ] Update Lazyload extension to use native loading=lazy
[x] Test parsing, editing, searching & performance
[x] Test compatibility with timburr
[x] Test compatibility with klinklang
[x] Test compatibility with existing Gadgets
[x] Deploy to 52Poké production
[x] Reset Elasticsearch data

Upgrade completed!


fix spelling error in comment of ResponderEventPlugin.js file

fix a spelling error in comment of ResponderEventPlugin.js file

this is likely intentional; iff = if and only if

@ide Thanks, good to know that


Error order in line chart

In datasourse 4 line where primary with a pass date. In a dataset, dates are in order, but with a pass date.

after rendering some line has error primary order date

Data before build datasourse has not a complete set for all primary and lines

You need to make a CodeSandBox for this otherwise I can’t debug it.


Update cardano-base dependency and make required changes

Update the cardano-base dependency and make the required changes.
Depends on https://github.com/input-output-hk/cardano-ledger-specs/pull/1887 (edit: now merged).

Looks like @mrBliss handled this in https://github.com/input-output-hk/ouroboros-network/pull/2664.


refactor: use async function

Checklist

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

Affected core subsystem(s)

Description of change

use async function instead of generator.
update dependencies to lastest, support Egg 2.

BREAKING CHANGE:
need node >= 8 due to async function.

2.0.0


Max fanout violation

Description
I have encountered a warning indicating the presence of maximum fanout violations within the design at the Typical corner. I am seeking assistance in resolving this issue. Does anyone have insights or suggestions on how to address this matter effectively?
the warning look like:
[WARNING]: There are max fanout violations in the design at the Typical corner.
Expected Behavior
Solve fanout violation
Environment report
open_pdks cd1748bb197f9b7af62a54507de6624e30363943
WARNING: issue-survey appears to be running inside the OpenLane
container.

This makes it difficult to rule out issues with your
environment.

Unless instructed specifically to do so, please run this command
outside the OpenLane container.
---

Kernel: Linux v6.5.0-21-generic
Distribution: centos 7
Python: v3.6.8 (OK)
OpenLane Git Version: 9dbd8b5ea2bd891bed4dcc97df5c7439083f0368
python-venv: INSTALLED
---
PDK Version Verification Status: OK
---
Git Log (Last 3 Commits)

9dbd8b5e 2024-01-11T15:26:56+02:00 Fix `-synth_explore` crash (#2085) - Kareem Farid -  (HEAD -> master, tag: 2024.01.12, origin/master, origin/HEAD)
a005df1f 2024-01-08T10:51:06+02:00 Updated link to newer version of spanish docs (#2082) - Laboratorio de Investigación en Microelectrónica y Arquitectura de Computadoras, EIE -- UCR -  (tag: 2024.01.09)
8bea8c51 2023-12-26T13:17:21+02:00 Update `OpenROAD` (#2062) - Kareem Farid -  (tag: 2023.12.27)
---
Git Remotes

origin	https://github.com/The-OpenROAD-Project/OpenLane (fetch)
origin	https://github.com/The-OpenROAD-Project/OpenLane (push)

Reproduction material
config.json
dff_8x72.txt
dff.txt
Relevant log output
[WARNING]: There are max fanout violations in the design at the Typical corner. Please refer to 'designs/ram_8x72/runs/first_run/reports/signoff/33-sta-rcx_nom/multi_corner_sta.checks.rpt'.

Should be safe to ignore as long as there are no max capacitance violations.


Use codecov action instead of gem

Adds codecov action at end of test run
Adds simplecov-cobertura gem
Remove codecov gem
No need to require simplecov, at least according to this

Closes #949 since it obsoletes the need to upgrade the codecov gem

Looks right, nice work @colindean!


Cannot read property 'id' of null

(node:11304) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'id' of null
    at values.map.value (file:///Users/mmandlis/arcs/arcs/runtime/ts-build/storage/in-memory-storage.js:229:35)
    at Array.map (<anonymous>)
    at InMemoryCollection.storeMultiple (file:///Users/mmandlis/arcs/arcs/runtime/ts-build/storage/in-memory-storage.js:225:16)
    at InMemoryVariable.cloneFrom (file:///Users/mmandlis/arcs/arcs/runtime/ts-build/storage/in-memory-storage.js:314:41)
    at <anonymous>
    at process._tickCallback (internal/process/next_tick.js:160:7)

The entity in a Person, and the backing store is firebase-storage, and
const underlying = await handle.backingStore.getMultiple(literal.model.map(({id}) => id));

in in-memory-storage.ts ln 361 return an array with one element null.
@sjmiles I think you were seeing this error too, is it still happening?

Do you have any repro steps? I'm looking at the code in question now..

I reproduce it with remote planning.  The exact steps are:

in arcs-live, create an arc with 'find restaurants near ...'
run ./serve.sh (under shell/apps/remote-planning/) and you get the exception (you can debug it with ./debug.sh)

NOTE: if you want to use user Myk, you need to set a user id in shell/apps/remote-planning/index.js (Myk is -LMtek9Od_C2Fv1Z_l0-)

I tried serve.sh and don't see any errors. It produces two "plans" blocks with lists of (I presume) suggestion texts, and then just sits there.

It's running with user Cletus.

Did you create the "restaurants" arc on arcs-live?
I don't have a good explanation, but i think it might have been fixed with https://github.com/PolymerLabs/arcs/pull/2001 - because it only happens for me with arcs that are created on live, but not on the newer version. Let's wait until it gets pushed to verify.
Thanks for looking!

Dammit, brainfart, didn't do the arcs-live step. :roll_eyes:

that's the best strategy, possibly, it's already fixed :)

Guess not, I just got the error

... or not? Looks like my local changes for the music demo were interfering. Trying to do too many things at once...

let's leave this for now, and I'll let you know, if this happen again with ToT. sorry for the extra distraction.

lots and lots of debugging. more or less consistently happening to me with restaurants demo.
what I found is that during planning, the arc's store holding the Person is changing.
This is the arc's active recipe:
  use '!315148350750948:-LNXeIzlmfPSZ1_sDXgJ:26' as handle0 // GeoCoordinates Thing {...}
  **use '!315148350750948:-LNXeIzlmfPSZ1_sDXgJ:27' as handle1 // Person Thing {...}**
  use '!315148350750948:-LNXeIzlmfPSZ1_sDXgJ:29' #nosync #restaurants as handle2 // [Restaurant Thing {...}]
  use '!315148350750948:-LNXeIzlmfPSZ1_sDXgJ:30' as handle3 // Restaurant Thing {...}
  map 'PROFILE_avatar' as handle4 // [Avatar {...}]
  map 'PROFILE_userName' as handle5 // [UserName {...}]
  map 'SYSTEM_user' as handle6 // User {...}
  slot 'slotid-!315148350750948:-LNXeIzlmfPSZ1_sDXgJ:20' as slot0
  slot 'slotid-!315148350750948:-LNXeIzlmfPSZ1_sDXgJ:21' as slot1
  slot 'slotid-!315148350750948:-LNXeIzlmfPSZ1_sDXgJ:22' as slot2
  slot 'slotid-!315148350750948:-LNXeIzlmfPSZ1_sDXgJ:23' as slot3
  slot 'slotid-!315148350750948:-LNXeIzlmfPSZ1_sDXgJ:24' as slot4
  slot 'slotid-!315148350750948:-LNXeIzlmfPSZ1_sDXgJ:25' as slot5
  slot 'rootslotid-root' #root as slot6
  ExtractLocation as particle0
    location -> handle0
    person <- handle1
  FindRestaurants as particle1
    location <- handle0
    restaurants = handle2
    consume root as slot6
      provide masterdetail as slot5
  RestaurantDetail as particle2
    selected <- handle3
    consume detail as slot0
      provide action as slot1
  RestaurantList as particle3
    list <- handle2
    selected = handle3
    consume master as slot2
      provide annotation as slot3
      provide modifier as slot4
  RestaurantMasterDetail as particle4
    list <- handle2
    selected = handle3
    consume masterdetail as slot5
      provide detail as slot0
      provide master as slot2
  UserPerson as particle5
    avatars <- handle4
    names <- handle5
    person -> handle1
    user <- handle6

several cloneForSpeculative executions run in parallel, but during the first couple
store !315148350750948:-LNXeIzlmfPSZ1_sDXgJ:27
has value id !1055911603951819:-LNXeIzlmfPSZ1_sDXgJ:0:inner:1:0 and this works fine
but at some point it is updated to the next version with value id !1055911603951819:-LNXeIzlmfPSZ1_sDXgJ:0:inner:1:2 and then the exception is triggered.
I tried clone a shared speculative arc and to pass that to the speculator to clone from, but it only seemed to help if planning is done for a single arc.
Also, I don't completely understand why the Person backing store wouldn't have the newer version of the user, so I need someone more knowledgeable to look at it with me... (


Make shoot domain gardener parameter as optional

Changes proposed in this pull request:

Make shoot domain gardener parameter optional, because Gardener config is used by two application and only one of them require this parameter.

/test pre-master-control-plane-gke-integration

/test pre-master-control-plane-gke-integration

/test pre-master-control-plane-integration

/test pre-master-control-plane-integration


$each function throws NullPointer exception when input is null

This JSONata expression is working fine in JSONata Exerciser -
{      "severity":     $exists(         $severity:=$filter(             $each(                 $sift(                     attributes                     ,function($v, $k){$contains($k,/.*level$/) and $uppercase($v) in ["ALL", "TRACE", "DEBUG", "INFO", "WARN", "ERROR", "FATAL", "OFF"]}                 )                 , function($v, $k){$uppercase($v)}             )             , function($v, $i){$i = 0}         )     )     ?         $severity         :"UNKNOWN" }
Here is JSONata Exerciser link with input - https://try.jsonata.org/QSgpuVagm
But the library is throwing NullPointerException
The reason that there is a bug in $each function,
for the given input
output of $sift is null
when $each receives null as input, it throws the exception.

Refactored the expression to debug step by step - maybe it's useful:
(
    $LEVELS := ["ALL", "TRACE", "DEBUG", "INFO", "WARN", "ERROR", "FATAL", "OFF"];
    $kv := $sift(attributes, function($v, $k) { $contains($k, /.*level$/) } );
    $level:= $each($kv, $uppercase)[0];
    $severity := $level in $LEVELS ? $level : "UNKNOWN";

    {  "severity": $severity }
)

https://try.jsonata.org/oL90QIlhs


Snow can by bypassed with Prototype Pollution

It seems that const target = new Object(null);  in https://github.com/LavaMoat/snow/blob/1c8faa81291e6f6dffe62b7106eff2492213375d/src/proxy.js#L17 was supposed to be Object.create(null). Because of that bug, it's possible to get to all the prototypes.
var proxy = open('#asd', '_top');
proxy.constructor.getPrototypeOf.call = () => null;
var iframe = document.createElement('iframe');
document.body.appendChild(iframe);
iframe.contentWindow.alert(1337);

Thanks for contributing. The main maintainer of this project is temporary unavailable, but we'll definitely get back to this.
The plan is to tighten some limitations on DOM usage that Snow already introduces and fixing the missing overrides where possible. Some of the work has started (see PR tab)
Meanwhile we're also working with W3C to propose a basic building block of Snow getting introduced into the browser so that all of the monkey-patching can be eliminated in the future. https://www.w3.org/2023/03/secure-the-web-forward/talks/realms.html
Feel free to update this issue with comments on how you think it should be addressed. We may reach out with questions later.


New clock - Mountain Pass Clock

A clock that changes scenes depending on weather conditions and time of day.

This looks awesome, thanks!


Build fail Manjaro Linux Swift 5.2.3

Hi I cannot build this repo via buildscript.sh. Would you consider to update this app for Swift 5.2? Thank you very much

Fixed.


feat(vite-plugin-angular): add support for JIT mode

PR Checklist
Please check if your PR fulfills the following requirements:

[x] The commit message follows our guidelines: https://github.com/analogjs/analog/blob/main/CONTRIBUTING.md#-commit-message-guidelines
[x] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Other... Please describe:

Which package are you modifying?

[x] vite-plugin-angular
[ ] vite-plugin-nitro
[ ] astro-angular
[ ] create-analog
[ ] router
[ ] platform
[ ] content
[ ] nx-plugin
[ ] trpc

What is the current behavior?

Closes #368
What is the new behavior?
Enabling JIT mode through the Analog Platform and Vite Angular Plugin is an option.
/// <reference types="vitest" />

import { defineConfig } from 'vite';
import { offsetFromRoot } from '@nx/devkit';
import angular from '@analogjs/vite-plugin-angular';

// https://vitejs.dev/config/
export default defineConfig(({ mode }) => {
  return {
    root: 'src',
    plugins: [
      angular({ jit: boolean }), // enabled automatically when running tests with Vitest
    ],
    test: {
      globals: true,
      environment: 'jsdom',
      setupFiles: ['src/test-setup.ts'],
      include: ['**/*.spec.ts'],
    },
    define: {
      'import.meta.vitest': mode !== 'production',
    },
  };
});

When running tests, JIT mode is used instead of AOT which provides faster compilation of files, while still supporting internal and external styles and templates. This will speed up compilation time with libraries such as Vitest, Playwright, Storybook, etc.
Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information

@sand4rt this should help with Playwright compilation speed also.

@brandonroberts thanks! Gonna try this asap!

@brandonroberts thought the templateUrl would still work with angular({ jit: true }) somehow but unfortunately that is not the case. I wonder if this is still a useful feature for testing because of this?

@sand4rt it supports templateUrl and styleUrls with Vitests. I'll have to check and see what the issue is with Playwright. Will you open a new issue with a sample repo?

After some tests I came with these weirdly conclusions:

@KlausEverWalkingDev this is the same as disabling jit mode altogether. The vite object overrides the analog plugin options for the Vite plugin.

Oh, thanks. I added it while fiddling with analog source file, but I admit I didn't understand the real meaning of it. By the way, what's the difference between analog and angular plugin? I didn't get when to use only one of them or both.

Oh, thanks. I added it while reading the analog source files, but I admit I didn't understand the real meaning of it. By the way, what's the difference between analog and angular plugin? I didn't get when to use only one of them or both.

The analog plugin is the "glue" between the analog packages.
The angular plugin is what handles connecting Angular compilation to Vite. It can be used on its own and is used for Astro, Qwik, and other Vite integration


tunneling socket could not be established, cause=Parse Error

npm info install<EMAIL_ADDRESS>
><EMAIL_ADDRESS>install /app/app/2014 12 27 carcass/node_modules/node-sass
> node scripts/install.js

tunneling socket could not be established, cause=Parse Error
tunneling socket could not be established, cause=Parse Error
fs.js:75
      throw err;  // Forgot a callback but don't know where? Use NODE_DEBUG=fs
            ^
Error: ENOENT, unlink '/app/app/2014 12 27 carcass/node_modules/node-sass/vendor/linux-x64/binding.node'
    at Error (native)

npm info<EMAIL_ADDRESS>Failed to exec install script
npm ERR! Linux 3.10.0-123.el7.x86_64
npm ERR! argv "/usr/local/node/node-v0.11.14/bin/node" "/usr/local/node/node-default/bin/npm" "install" "node-sass"
npm ERR! node v0.11.14
npm ERR! npm  v2.0.0
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>install: `node scripts/install.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script.
npm ERR! This is most likely a problem with the node-sass package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node scripts/install.js
npm ERR! You can get their info via:
npm ERR!     npm owner ls node-sass
npm ERR! There is likely additional logging output above.
npm info preuninstall<EMAIL_ADDRESS>npm info uninstall<EMAIL_ADDRESS>npm info postuninstall<EMAIL_ADDRESS>

Hello,
This seems like misconfigured npm.
Does this help? I would start with the one which says set registry and then proxy.

I am not using a proxy.
My registry is set to the default
I have updated to the latest version of NPM

npm info install<EMAIL_ADDRESS>
><EMAIL_ADDRESS>install /app/app/2014 12 27 carcass/node_modules/gulp-sass/node_modules/node-sass
> node scripts/install.js

tunneling socket could not be established, cause=Parse Error
tunneling socket could not be established, cause=Parse Error
fs.js:75
      throw err;  // Forgot a callback but don't know where? Use NODE_DEBUG=fs
            ^
Error: ENOENT, unlink '/app/app/2014 12 27 carcass/node_modules/gulp-sass/node_modules/node-sass/vendor/linux-x64/binding.node'
    at Error (native)
npm info<EMAIL_ADDRESS>Failed to exec install script
npm ERR! Linux 2.6.32-431.el6.x86_64
npm ERR! argv "node" "/usr/local/node/node-default/bin/npm" "install" "gulp-sass" "--save-dev"
npm ERR! node v0.11.14
npm ERR! npm  v2.1.17
npm ERR! code ELIFECYCLE

npm ERR<EMAIL_ADDRESS>install: `node scripts/install.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script 'node scripts/install.js'.
npm ERR! This is most likely a problem with the node-sass package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node scripts/install.js
npm ERR! You can get their info via:
npm ERR!     npm owner ls node-sass
npm ERR! There is likely additional logging output above.
npm info preuninstall<EMAIL_ADDRESS>npm info uninstall<EMAIL_ADDRESS>npm info postuninstall<EMAIL_ADDRESS>npm info preuninstall<EMAIL_ADDRESS>npm info uninstall<EMAIL_ADDRESS>npm info postuninstall<EMAIL_ADDRESS>
npm ERR! Please include the following file with any support request:
npm ERR!     /app/app/2014 12 27 carcass/npm-debug.log

Do you get the same result, if you try the following:
mkdir /temp; cd /temp
npm install node-sass
# it should install node-sass latest version: v2.0.0-beta

I did that and I get the exact same result:
npm info linkStuff<EMAIL_ADDRESS>npm info install<EMAIL_ADDRESS>
><EMAIL_ADDRESS>install /test/node_modules/node-sass
> node scripts/install.js

tunneling socket could not be established, cause=Parse Error
tunneling socket could not be established, cause=Parse Error
fs: missing callback Error: ENOENT, unlink '/test/node_modules/node-sass/vendor/linux-x64/binding.node'
npm info postinstall<EMAIL_ADDRESS>
><EMAIL_ADDRESS>postinstall /test/node_modules/node-sass
> node scripts/build.js

<EMAIL_ADDRESS>node_modules/node-sass
├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>└──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>npm info ok
[root@localhost test]#

@kevva, any ideas what's going wrong?
I tried and succeeded. Here is the log:
vagrant@precise64:/temp/test-install$ uname -r
3.11.0-15-generic

vagrant@precise64:/temp/test-install$ cat /etc/issue
Ubuntu 12.04.5 LTS \n \l

vagrant@precise64:/temp/test-install$ node -p process.versions
{ http_parser: '1.0',
  node: '0.10.32',
  v8: '<IP_ADDRESS>',
  ares: '1.9.0-DEV',
  uv: '0.10.28',
  zlib: '1.2.3',
  modules: '11',
  openssl: '1.0.1i' }

vagrant@precise64:/temp/test-install$ npm install node-sass
|
><EMAIL_ADDRESS>install /temp/test-install/node_modules/node-sass
> node scripts/install.js

Binary downloaded and installed at /temp/test-install/node_modules/node-sass/vendor/linux-x64/binding.node

><EMAIL_ADDRESS>postinstall /temp/test-install/node_modules/node-sass
> node scripts/build.js

<EMAIL_ADDRESS>node_modules/node-sass
├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>tou
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>└──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>6.3)

vagrant@precise64:/temp/test-install$ node node_modules/.bin/node-sass --help

  Wrapper around libsass

  node-sass version: 2.0.0-beta
  libsass version: 3.1.0-beta

  Usage
    node-sass [options] <input.scss> [output.css]
    cat <input.scss> | node-sass > output.css

  Example
    node-sass --output-style compressed foobar.scss foobar.css
    cat foobar.scss | node-sass --output-style compressed > foobar.css

  Options
    -w, --watch                Watch a directory or file
    -r, --recursive            Recursively watch directories or files
    -o, --output               Output directory
    -x, --omit-source-map-url  Omit source map URL comment from output
    -i, --indented-syntax      Treat data from stdin as sass code (versus scss)
    --output-style             CSS output style (nested|expanded|compact|compressed)
    --source-comments          Include debug info in output
    --source-map               Emit source map
    --source-map-embed         Embed sourceMappingUrl as data URI
    --source-map-contents      Embed include contents in map
    --include-path             Path to look for imported files
    --image-path               Path to prepend when using the `image-url()` helper
    --precision                The amount of precision allowed in decimal numbers
    --stdout                   Print the resulting CSS to stdout
    --importer                 Path to custom importer
    --help                     Print usage info

vagrant@precise64:/temp/test-install$

Just to be clear, I am doing this on CentOS:
[vagrant@localhost test]$ cat /etc/issue
CentOS release 6.6 (Final)
Kernel \r on an \m

I've just into this myself. The issue is on this line https://github.com/sass/node-sass/blob/master/scripts/install.js#L50.
npm config get xx sometimes returns npm info it worked if it ends with ok with proxy.code === 0. This results in result being set to npm info it worked if it ends with ok.

Thanks a bunch @xzyfer! I have pushed the fix based on your commit. :+1:

i am still experiencing the same issue on openshift...
remote: make: Entering directory '/var/lib/openshift/xxxxxxxxxxxxxxxxxxxxxxxx/app-root/runtime/repo/node_modules/node-sass/build'
remote:   CXX(target) Release/obj.target/binding/src/binding.o
remote: In file included from ../src/binding.cpp:3:
remote: ../src/sass_context_wrapper.h:2:34: error: libsass/sass_context.h: No such file or directory
remote: In file included from ../src/binding.cpp:3:
remote: ../src/sass_context_wrapper.h:26: error: ISO C++ forbids declaration of 'Sass_Import' with no type
remote: ../src/sass_context_wrapper.h:26: error: expected ';' before '*' token
remote: ../src/binding.cpp: In function 'void prepare_import_results(v8::Local<v8::Value>, sass_context_wrapper*)':
remote: ../src/binding.cpp:24: error: 'struct sass_context_wrapper' has no member named 'imports'
remote: ../src/binding.cpp:24: error: 'sass_make_import_list' was not declared in this scope
remote: ../src/binding.cpp:36: error: 'struct sass_context_wrapper' has no member named 'imports'
remote: ../src/binding.cpp:36: error: 'sass_make_import_entry' was not declared in this scope
remote: ../src/binding.cpp:40: error: 'struct sass_context_wrapper' has no member named 'imports'
remote: ../src/binding.cpp:40: error: 'sass_make_import_list' was not declared in this scope
remote: ../src/binding.cpp:45: error: 'struct sass_context_wrapper' has no member named 'imports'
remote: ../src/binding.cpp:45: error: 'sass_make_import_entry' was not declared in this scope
remote: ../src/binding.cpp:48: error: 'struct sass_context_wrapper' has no member named 'imports'
remote: ../src/binding.cpp:48: error: 'sass_make_import_list' was not declared in this scope
remote: ../src/binding.cpp:49: error: 'struct sass_context_wrapper' has no member named 'imports'
remote: ../src/binding.cpp:49: error: 'sass_make_import_entry' was not declared in this scope
remote: ../src/binding.cpp: In function 'Sass_Import** sass_importer(const char*, const char*, void*)':
remote: ../src/binding.cpp:104: error: 'struct sass_context_wrapper' has no member named 'imports'
remote: ../src/binding.cpp: In function 'void ExtractOptions(v8::Local<v8::Object>, void*, sass_context_wrapper*, bool, bool)':
remote: ../src/binding.cpp:116: error: 'sass_file_context_get_context' was not declared in this scope
remote: ../src/binding.cpp:120: error: 'sass_data_context_get_context' was not declared in this scope
remote: ../src/binding.cpp:123: error: 'sass_context_get_options' was not declared in this scope
remote: ../src/binding.cpp:144: error: 'sass_make_importer' was not declared in this scope
remote: ../src/binding.cpp:144: error: 'sass_option_set_importer' was not declared in this scope
remote: ../src/binding.cpp:148: error: 'sass_option_set_input_path' was not declared in this scope
remote: ../src/binding.cpp:151: error: 'sass_option_set_output_path' was not declared in this scope
remote: ../src/binding.cpp:152: error: 'sass_option_set_image_path' was not declared in this scope
remote: ../src/binding.cpp:153: error: 'Sass_Output_Style' was not declared in this scope
remote: ../src/binding.cpp:153: error: 'sass_option_set_output_style' was not declared in this scope
remote: ../src/binding.cpp:154: error: 'sass_option_set_is_indented_syntax_src' was not declared in this scope
remote: ../src/binding.cpp:155: error: 'sass_option_set_source_comments' was not declared in this scope
remote: ../src/binding.cpp:156: error: 'sass_option_set_omit_source_map_url' was not declared in this scope
remote: ../src/binding.cpp:157: error: 'sass_option_set_source_map_embed' was not declared in this scope
remote: ../src/binding.cpp:158: error: 'sass_option_set_source_map_contents' was not declared in this scope
remote: ../src/binding.cpp:159: error: 'sass_option_set_source_map_file' was not declared in this scope
remote: ../src/binding.cpp:160: error: 'sass_option_set_include_path' was not declared in this scope
remote: ../src/binding.cpp:161: error: 'sass_option_set_precision' was not declared in this scope
remote: ../src/binding.cpp: At global scope:
remote: ../src/binding.cpp:164: error: 'Sass_Context' has not been declared
remote: ../src/binding.cpp: In function 'void GetStats(sass_context_wrapper*, int*)':
remote: ../src/binding.cpp:167: error: 'sass_context_get_included_files' was not declared in this scope
remote: ../src/binding.cpp:171: error: 'nullptr' was not declared in this scope
remote: ../src/binding.cpp: At global scope:
remote: ../src/binding.cpp:179: error: 'Sass_Context' has not been declared
remote: ../src/binding.cpp: In function 'void GetSourceMap(sass_context_wrapper*, int*)':
remote: ../src/binding.cpp:184: error: 'sass_context_get_error_status' was not declared in this scope
remote: ../src/binding.cpp:188: error: 'sass_context_get_source_map_string' was not declared in this scope
remote: ../src/binding.cpp: At global scope:
remote: ../src/binding.cpp:198: error: 'Sass_Context' has not been declared
remote: ../src/binding.cpp: In function 'int GetResult(sass_context_wrapper*, int*)':
remote: ../src/binding.cpp:201: error: 'sass_context_get_error_status' was not declared in this scope
remote: ../src/binding.cpp:204: error: 'sass_context_get_output_string' was not declared in this scope
remote: ../src/binding.cpp: In function 'void make_callback(uv_work_t*)':
remote: ../src/binding.cpp:221: error: 'sass_data_context_get_context' was not declared in this scope
remote: ../src/binding.cpp:224: error: 'sass_file_context_get_context' was not declared in this scope
remote: ../src/binding.cpp:227: error: cannot convert 'Sass_Context*' to 'int*' for argument '2' to 'int GetResult(sass_context_wrapper*, int*)'
remote: ../src/binding.cpp:235: error: 'sass_context_get_error_json' was not declared in this scope
remote: ../src/binding.cpp: In function 'v8::Handle<v8::Value> Render(const v8::Arguments&)':
remote: ../src/binding.cpp:258: error: 'sass_make_data_context' was not declared in this scope
remote: ../src/binding.cpp: In function 'v8::Handle<v8::Value> RenderSync(const v8::Arguments&)':
remote: ../src/binding.cpp:275: error: 'sass_make_data_context' was not declared in this scope
remote: ../src/binding.cpp:276: error: 'sass_data_context_get_context' was not declared in this scope
remote: ../src/binding.cpp:283: error: cannot convert 'Sass_Context*' to 'int*' for argument '2' to 'int GetResult(sass_context_wrapper*, int*)'
remote: ../src/binding.cpp:287: error: 'sass_context_get_error_json' was not declared in this scope
remote: ../src/binding.cpp: In function 'v8::Handle<v8::Value> RenderFile(const v8::Arguments&)':
remote: ../src/binding.cpp:304: error: 'sass_make_file_context' was not declared in this scope
remote: ../src/binding.cpp: In function 'v8::Handle<v8::Value> RenderFileSync(const v8::Arguments&)':
remote: ../src/binding.cpp:321: error: 'sass_make_file_context' was not declared in this scope
remote: ../src/binding.cpp:322: error: 'sass_file_context_get_context' was not declared in this scope
remote: ../src/binding.cpp:328: error: cannot convert 'Sass_Context*' to 'int*' for argument '2' to 'int GetResult(sass_context_wrapper*, int*)'
remote: ../src/binding.cpp:332: error: 'sass_context_get_error_json' was not declared in this scope
remote: make: *** [Release/obj.target/binding/src/binding.o] Error 1
remote: make: Leaving directory '/var/lib/openshift/xxxxxxxxxxxxxxxxxxxxxxxx/app-root/runtime/repo/node_modules/node-sass/build'
remote: gyp ERR! build error
remote: gyp ERR! stack Error: 'make' failed with exit code: 2
remote: gyp ERR! stack     at ChildProcess.onExit (/opt/rh/nodejs010/root/usr/lib/node_modules/node-gyp/lib/build.js:267:23)
remote: gyp ERR! stack     at ChildProcess.EventEmitter.emit (events.js:98:17)
remote: gyp ERR! stack     at Process.ChildProcess._handle.onexit (child_process.js:797:12)
remote: gyp ERR! System Linux 2.6.32-504.3.3.el6.x86_64
remote: gyp ERR! command "node" "/opt/rh/nodejs010/root/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
remote: gyp ERR! cwd /var/lib/openshift/xxxxxxxxxxxxxxxxxxxxxxxx/app-root/runtime/repo/node_modules/node-sass
remote: gyp ERR! node -v v0.10.25
remote: gyp ERR! node-gyp -v v0.12.2
remote: gyp ERR! not ok

@aschmid that is not a tunneling issue which is described here and https://github.com/sass/node-sass/issues/604, but the issue you are reporting is due to the reason you have older gcc (libsass needs gcc 5+ to compile). Also we haven't released the next version yet after fixing the tunneling issue.
Besides what command are you running to install node-sass? Normally it is npm install node-sass, which downloads the readymade binary and doesn't require gcc, Python and other tools to build node-sass on target system.

@am11 i am just pushing the openshift repo with node-sass  in the package.json as a dependency without specifying a version. what i posted is the remotes log output.

npm install<EMAIL_ADDRESS>is released!
Checkout the release notes: https://github.com/sass/node-sass/releases/tag/v2.0.0


Update to latest procfs

By turning off procfs's default features, the chrono and time crates are removed from the dependency tree.  flate2 is also removed.
Closes #7

Thanks! :D


Small updates to contributing.rst

I'm not sure if people really use this? If they do, it could use another run through. Potentially some of our explanations could become links to better maintained docs; e.g. how to use git / pytest
This makes a couple of small tweaks, in pursuit of incrementalism :)

Looks good to me, thanks


Limitations while using WIP

Hello,
Seems new EDGE browser not supported/integrated in WIP, files saved from new EDGE not protected by WIP.

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

ID: 6f23c9b6-81aa-b06d-5c19-196ac933b6ff
Version Independent ID: 0c7eb396-4274-c546-6063-6d38382b956d
Content: Limitations while using Windows Information Protection (WIP) (Windows 10) - Microsoft 365 Security
Content Source: windows/security/information-protection/windows-information-protection/limitations-with-wip.md
Product: w10
Technology: windows
GitHub Login: @DulceMontemayor
Microsoft Alias: dansimp

Hello @lightupdifire,
Edge is supported by WIP (source)
Are you sure that Edge is in the list of allowed apps? Was the file downloaded from WIP-enabled resource?
Thank you

Hello @MaratMussabekov,
It is about a new Edge browser, that was released recently. If you install it on already enrolled and WIP-working protected device, then files saved from WIP-enabled resource not protected...

Hello @lightupdifire ,
sorry for misunderstanding, you were right, chromium-based edge (new edge) still has WIP disabled by default, you can see more here
I will create a PR to add information in the article.
Thank you!

@lightupdifire - Thank you for submitting feedback.
From our understanding, the issue has been resolved based on this merged commit https://github.com/MicrosoftDocs/windows-itpro-docs/commit/8691efd90870ddf13ffe4e49378c0e1668712b63.
Thank you for your contribution to make the docs better! Much appreciated!


Allow to open encrypted archives

Add the password string parameter in the method ExtractAll
Add the private method OpenArchive which calls the native method zip_fopen_index_encrypted if the password parameter is filled. Otherwise, use the zip_fopen_index

@Fniz thanks for the PR, it is fine as soon as you rebase on the current master, if you don't mind! :) Also, while at it, would you mind reformatting the changes to be in line with the rest of the code? Unless you don't mind me reformatting after merging :) Thanks again!

Hi @grendello thanks for your feedbacks and sorry for newbie skill in github. I close this PR and reopen one from master (without this mix of white space / tabs)

@grendello, Thank you very much for the information ! Really precious :)
Yours sincerely,
Florian
On Wed, Dec 5, 2018 at 5:29 PM Marek Habersack<EMAIL_ADDRESS>wrote:

@Fniz https://github.com/Fniz no problem :) FYI, you don't need to
close the PR to fix it up. All you need to do is rebase your branch on
master using these commands in your fork:
git checkout master
git pull origin
git checkout OpenZipArchiveWithPwd
git rebase master
git push -f fork OpenZipArchiveWithPwd
The git rebase master will show you conflicts, at this point you edit
each file that's marked (see git status) as modified by both and resolve
the conflicts. After that you git add that file. Then you make other
changes you have to, add the modified files as well and follow up with git
rebase --continue which will finish the process and let you issue the
last command from the above set. This will automatically update the PR.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/grendello/LibZipSharp/pull/28#issuecomment-444549411,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABcyRbI_eIsDaYW2HbrLjv0QZtiLvaWaks5u1_RcgaJpZM4ZCL2D
.

@grendello, Thank you very much for the information ! Really precious :)
Yours sincerely,
Florian
On Thu, Dec 6, 2018 at 9:36 AM Florian Nouri<EMAIL_ADDRESS>wrote:

@grendello, Thank you very much for the information ! Really precious :)
Yours sincerely,
Florian
On Wed, Dec 5, 2018 at 5:29 PM Marek Habersack<EMAIL_ADDRESS>wrote:

@Fniz https://github.com/Fniz no problem :) FYI, you don't need to
close the PR to fix it up. All you need to do is rebase your branch on
master using these commands in your fork:
git checkout master
git pull origin
git checkout OpenZipArchiveWithPwd
git rebase master
git push -f fork OpenZipArchiveWithPwd
The git rebase master will show you conflicts, at this point you edit
each file that's marked (see git status) as modified by both and resolve
the conflicts. After that you git add that file. Then you make other
changes you have to, add the modified files as well and follow up with git
rebase --continue which will finish the process and let you issue the
last command from the above set. This will automatically update the PR.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/grendello/LibZipSharp/pull/28#issuecomment-444549411,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABcyRbI_eIsDaYW2HbrLjv0QZtiLvaWaks5u1_RcgaJpZM4ZCL2D
.


Minor fixes

Minor bug fixes, such as read more button redirect to projectDetails page. Apart from this, deleted NavMenu.razor and css.

👍


skip synchronizing materialized view

If I have a materialized view by creating manually and define the model, it will cause error when synchronizing. I want to skip it.
It's better to support define materialized view by cequel, but I think we can skip and prevent error for now.

I tried to cached which keyspace refreshed, but it won't work if schema changed. This can not pass unit tests. I will try other methods later.

@emn178, i hope you find time to get the tests passing. This is a good change, over all, and i'd like to include it.

@emn178, this looks good. If you rebase it i'll merge it.

merge as #346. Thanks for the improvement.,

Released in 2.0.3. Thanks, again, for the improvement.


Jenkins automation

Create a script to trigger Jenkins automation tasks whenever a file is pushed into the source repository.

@NishkarshRaj, I would like to pick up this issue, could you please elaborate? Does this mean trigger build/deploy pipeline whenever a code is pushed to this repository?
Is it okay if we achieve this using github actions? or any other CI then jenkins?

@navyakanu Thank you for reaching out and showing interest on this repository.
Yes, I want an automated pipeline via script or any other means to generate build of the master branch code base whenever a new change is merged with it.
Sure, we can work on GitHub Actions or any other CI like Travis etc, if you want.

please assign this to me

@acodebreaker sorry brother, its already done! I forgot to close the issue. 👍


Update _helpers.tpl

Changed namespace from default to monitoring

@shahid430, thanks for the PR but it's indeed not clear what this fix is for: unless specified, namespace will be %v-system as is defined here:
https://github.com/grafana/k6-operator/blob/main/charts/k6-operator/templates/_helpers.tpl#L93
@illrill Thanks for helping out :smile:

@shahid430 I'm closing this PR due to reasons stated above. Please feel free to re-open / open a new one if there's something else!


module 'utils.utils' has no attribute 'k_largest_index_argpartition'

Traceback (most recent call last):
File "/usr/lib/python3.6/threading.py", line 916, in _bootstrap_inner
self.run()
File "/usr/lib/python3.6/threading.py", line 864, in run
self._target(*self._args, **self._kwargs)
File "main.py", line 191, in agent
self.policy()
File "main.py", line 165, in policy
self.compute_action(explore_actions, self.grasp_predictions)
File "main.py", line 177, in compute_action
maximas = utils.k_largest_index_argpartition(predictions, k=10)
AttributeError: module 'utils.utils' has no attribute 'k_largest_index_argpartition'

The repository only provide .dylib, which can not be used in Linux, can you provide .so?
The pretrained model can also be provided?