fix(ci): trigger upgrade tests when changing kong/templates files

Summary

Checklist

[ ] The Pull Request has tests
[ ] A changelog file has been created under changelog/unreleased/kong or skip-changelog label added on PR if changelog is unnecessary. README.md
[ ] There is a user-facing docs PR against https://github.com/Kong/docs.konghq.com - PUT DOCS PR HERE

Full changelog

[Implement ...]

Issue reference

Fix #[issue number]

Here is test run which triggered the migration test https://github.com/Kong/kong/actions/runs/6558380369/job/17811824375?pr=11782

Due to #11783, we should close this PR.


Missing check for NULL pointer

Avoid segmentation fault for interfaces without link.

Agreed to CLA

Blocked (missing CLA). Will attemp again.


Invalid Podfile file: cannot load such file -- /Users/trammbp/Downloads/react-native-develop/myproject/node_modules/@react-native-community/cli-platform-ios/native_modules.

I tried to build a project from an existing source.
I go to the project folder and run yarn install, it throws errors:
YN0001: │ HTTPError: @react-native-lightkits/android-keyboard-adjust@npm:^1.0.0: Response code 404 (Not Found)
at s. (/Users/trammbp/.yarn/releases/yarn-2.1.1.cjs:23:36333)
at processTicksAndRejections (internal/process/task_queues.js:93:5)
➤ YN0000: └ Completed in 1.61s
➤ YN0000: Failed with errors in 1.62s
To continue I run pod install, and get the error
[!] Invalid Podfile file: cannot load such file -- /Users/trammbp/Downloads/react-native-develop/myproject/node_modules/@react-native-community/cli-platform-ios/native_modules.
from /Users/trammbp/Downloads/react-native-develop/myproject/ios/Podfile:2
-------------------------------------------
platform :ios, '9.0'

require_relative '../node_modules/@react-native-community/cli-platform-ios/native_modules'

-------------------------------------------
Can anyone help me?

Hi @tramnguyengh could you fill out all the sections of the issue template? Thanks

It looks like @react-native-lightkits/android-keyboard-adjust package is not found. See error below.
YN0001: │ HTTPError: @react-native-lightkits/android-keyboard-adjust@npm:^1.0.0: Response code 404 (Not Found)

https://github.com/facebook/react-native/issues/29413
fixed using the command :  pod repo update


Do health request by calling Thorchain API (not Midgard)

Endpoint: /thorchain/ping

We check THORChain API before sending swap/deposit/withdraw etc. txs - no need for another check of ping endpoint.


New Feature: Event Level Permissions to Calendar

We got a request that to create a calendar where the "edit" and "delete" permissions for the events would only apply to those users who are owners of the events (who created them).
This would need two things from the Calendar functionality:

Ability to control permissions on the event level
Being able to set the default permissions for new events

Alternatively, this could also be implemented as follows:

Add a new pseudo user group (like "Guest") for "Owner" which would apply the calendar level permissions to the owners of the events (who created them)

+1

We've been reluctant to add event-level permissions because some calendars can have literally thousands of events in them, and checking them sounds like a significant performance degradation. However, I could see an "Event Creator" permission access entity being useful. I would be interested in performance testing a calendar with this turned on with thousands of events using this model.


Add support for uninstalling items installed with dever

Is your feature request related to a problem? Please describe.
When wanting to remove development environment necessary installations. It would be convenient with a uninstall command
Describe the solution you'd like
Create new groups for install options in dever-json.
install: [
  {
    "name": "test",
    "group": "test",
    "install": {
      "type": "chocolatey",
      "package": "git",
      "after": {
        "type": "powershell-command",
        "command": "docker container rm test"
      }
    },
    "uninstall": {
      "type": "powershell-script",
      "file": "development/delete-git.ps1",
      "before:" {
        "type": "powershell-command",
        "command": "choco uninstall git"
      }
    }
  },
  {
    "name": "test",
    "group": "test",
    "type": "chocolatey",
    "package": "git",
    "after": {
      "type": "powershell-command",
      "command": "docker container rm test"
    }
  }
]

Perhaps better names for the 'install' and 'uninstall' sections?
install and uninstall are optional.

Will somewhat implemented by  #75 as up/down instead of install/uninstall


Feature/ add token examples #706

Fixes #706
adds examples and tests for TokenTimelock and TokenVesting examples
🚀 Description

[x] 📘 I've reviewed the OpenZeppelin Contributor Guidelines
[x] ✅ I've added tests where applicable to test my new functionality.
[x] 📖 I've made sure that my contracts are well-documented.
[x] 🎨 I've run the JS/Solidity linters and fixed any issues (npm run lint:all:fix).

Hi @j-chimienti, thanks for your contribution! We already have something along these lines in progress (#991), would that suit these needs?

Hi @j-chimienti, thanks for your contribution!
I may be missing something, but from what I can tell, these samples don't actually extend the base contracts in any way, they simply delegate construction to them. In that sense, they are not really examples, but rather extra tests to the original contracts. Was that your intent with this PR?

Closing due to inactivity/intent not being clear (see above).


Python extension chooses non-Pixi interpreter

Testing #23674
This persists even after a reload

@baszalmstra @tdejager Is there a location or file we need to monitor to ensure that pixi environment gets selected?

Hi I would like to test this tomorrow, can I test with the released version of the extension?

You can do this with the pre-release version.


Update readme.md with shortlinks to help for LG\SM solutions in the Resources Section

@LindsayThomas  Changes have been made in the master branch.


This just gives you the link, you still need to goto the link and wait 15s right?

yes as it has a captcha, we currently dont bypass it.

and the id pass doesn't even works

and the id pass doesn't even works

thats not a problem from the generator, as the accounts are scraped from a website. if the website is outdated, it wont work, you have to add another website for it.


chore(storybook): configure storybook test runner

General summary
Configure storybook test runner

Dev use case: run storybook & run test:storybook --watch to code & test component in storybook interactions
CI use case: run stories storybook interactions tests (with fallback to smoke test)

Needs rework


Fix flaky tests for Bucket-Level Monitor

Signed-off-by: Mohammad Qureshi<EMAIL_ADDRESS>Issue #, if available: #298
Description of changes:
Monitor configurations are randomized during the plugin integration tests for the components that aren't being explicitly tested for specific scenarios so the test cases aren't overfit for a single situation. For Bucket-Level Monitors, this could lead to the Actions under a Trigger to sometimes be empty (0 Actions) or contain Actions in such a configuration that it no-ops (i.e. PerExecutionScope with no Alert categories configured). These types of configurations were rare but led to resulting Alerts to either be null (for new Alerts) or not updated (for existing Alerts) in some tests which failed assertions, making these tests flaky. This PR updates those tests to account for this scenario to ensure that these cases don't happen.
Commands used to reproduce the flaky tests (confirmed they passed after the changes):
./gradlew ':alerting:integTest' --tests "org.opensearch.alerting.MonitorRunnerIT.test bucket-level monitor with acknowledged alert" -Dtests.seed=39548DC170E2D9BD -Dtests.security.manager=false -Dtests.locale=hr-HR -Dtests.timezone=PNT -Druntime.java=14

./gradlew ':alerting:integTest' --tests "org.opensearch.alerting.MonitorRunnerIT.test bucket-level monitor alert creation and completion" -Dtests.seed=B2CAC72979FAC242 -Dtests.security.manager=false -Dtests.locale=ro-RO -Dtests.timezone=Europe/Lisbon -Druntime.java=14

Re-ran tests multiple times afterwards to check for any other flaky tests:
for i in {1..40}; do ./gradlew ':alerting:integTest' &> /dev/null || echo "Run $i failed"; done

CheckList:
[x] Commits are signed per the DCO using --signoff
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #318 (1424f72) into main (db0d59e) will increase coverage by 0.01%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##               main     #318      +/-   ##
============================================
+ Coverage     78.48%   78.49%   +0.01%
- Complexity      216      217       +1
============================================
  Files           173      173
  Lines          6975     6975
  Branches        916      916
============================================
+ Hits           5474     5475       +1
+ Misses         1009     1008       -1
  Partials        492      492

Impacted Files
Coverage Δ

.../kotlin/org/opensearch/alerting/core/JobSweeper.kt
69.50% <0.00%> (-0.50%)
:arrow_down:

...ain/kotlin/org/opensearch/alerting/AlertService.kt
78.53% <0.00%> (ø)

...ing/destination/client/DestinationEmailClient.java
77.50% <0.00%> (+5.00%)
:arrow_up:

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 db0d59e...1424f72. Read the comment docs.


Turn on the wit and wat features by default.

It's not entirely clear to me why we wouldn't want the wit and wat features on by default. I would suggest turning them on by default. The registry feature still might make sense to have off by default since registries are still quite new.

The wat feature is mostly for the tests, as users will rarely want to author a component in the text format to be used with the tool.
The thinking of having wit behind a feature is that eventually wit packages will be from the registry in most cases.
The intention behind both was simply to limit dependencies.
That said, we should probably be defaulting the wit feature on as the registry feature is defaulted off; we can then default it to off once registry is defaulted to on.
Feel free to make that change or I can do so when I'm back on Monday!


update snakemake profiles

Added default memory per cpu/thread and max-threads (which puts a cap on all rule-specific threads).
Resolves #90

If the "message" section of each rule is removed then the default output in the snakemake log file includes a list of all resources and wildcards. Default resources stemming from variables.env just display as the environment variable (i.e. $PARTITION and $ACCOUNT) but i tested that $PARTITION gets expanded properly and the correct $ACCOUNT is required for singularity to work I believe.

If the "message" section of each rule is removed then the default output in the snakemake log file includes a list of all resources and wildcards. Default resources stemming from variables.env just display as the environment variable (i.e. $PARTITION and $ACCOUNT) but i tested that $PARTITION gets expanded properly and the correct $ACCOUNT is required for singularity to work I believe.

The message directives aren't really useful.  Do we want to get rid of them?

Yeah, that makes sense. In this PR or a different one?


Aurora Development and Integration

This issue tracks the integration of Aurora into Bluefin.
https://github.com/NiHaiden/aurora
Discussion: https://universal-blue.discourse.group/t/aurora-announcement/767

This is blocked by cleaning up the containerfile, but will make this easier.

We'd like to just have Aurora building out of the bluefin repo instead of it's own: https://github.com/ublue-os/bluefin

https://github.com/ublue-os/bluefin/pull/1091

Aurora 39 is now building inside of bluefin.
Aurora 40 is currently not building due to some issues with akmods and some kernel skew.
Users that were on niklaus' build, will need to do a manual rebase.
We still have some loose threads that need to be accounted for. Users that encounter any are encouraged to report issues in the bluefin repo. We also need to get branding and announcements in place.

Alright, we've got things building: https://github.com/orgs/ublue-os/packages?tab=packages&q=aurora
I added a task list to the top message with what's left to do to finish it off. We have about a week to finish this off if we're going to make F40 release day, no pressure. 🌸

F40 has been building since we disabled devpod for F40 builds.

Alright, good enough!


Overlay add canvas can't accurate drawing

I through to openseadragon added a canvas layer, but the effect of the mouse coordinates and draw the canvas drawing coordinates, actual condition difference is very big, this is what causes, my code like the following this:
my code

var openSeadragon = new OpenSeadragon({
  id: "openSeadragon",
  prefixUrl: "images/",
  minZoomImageRatio: 1,
  maxZoomPixelRatio: 0,
  tileSources: {
    type: 'legacy-image-pyramid',
    levels: [{
      url: '1.png',
      height: 2000,
      width: 2000
    }]
  }
});
var overlay = false;

//create overlay div
var elt = document.createElement('div');
elt.id = 'overlays-div';
elt.style.opacity = "0.7";

openSeadragon.addOverlay({
  element: elt,
  location: new OpenSeadragon.Rect(0, 0, 1, 1),
  checkResize: false,
  placement: OpenSeadragon.OverlayPlacement.RIGHT

});
elt.innerHTML = "<canvas id='canvas' style='width: 100%;height: 100%; border: 1px solid `red;'></canvas>";

I recommend using the Canvas Overlay plugin:
https://github.com/altert/OpenSeadragonCanvasOverlay

@iangilman I try, thank you very much !!!


Feature request: Expand on autorun capabilities

Currently, the autorun functionality only runs one module. Asking empire to autorun another module means the first autorun is stomped. This is problematic for engagements where one is attempting to 'catch someone' who infrequently uses a machine and things need to happen the moment an agent phones home. Here is an example scenario
Target is an individual with multiple machines. One machine was left unattended and was subsequently backdoored. It is presumed that this individual is re-using passwords, so the intention is to extract credentials from one machine, then identify the other machine and attempt a connection - similar to how a typical virus/trojan/worm functions. In this case:

install persistence for 3-4 times during the day, so that a shell can be attempted at various times, or upon "awakening" (maybe there's better tradecraft here. I wonder if you can do "when  user unlocks workstation" or "when machine comes out of sleep")
sysinfo
attempt mimikatz
shell arp -a
attempt uac bypass, or otherwise gain system privileges, and run new agent with higher privs

With the intention of returning to the console at a later time and "finding all of this information waiting for you", because maybe the target got up at 3am to do some work, and the agent fired, and did a bunch of stuff for you while you were asleep and the target was awake.

Right now this just isn't possible with the current code base. Even with the 2.0 rewrite I don't know if we'll be able to integrate it, but will keep it in mind.

so I've solved part of it: the multi autorun - I've started using the rest api and scripting stuff with just simple bash scripts and making queries against empire. At the moment, I just have a while loop that goes and harvests screenshots, then moves them into another directory for review. What would be really cool, is to, somehow (and this is the part I don't know how to do) trigger an action based on an incoming shell. Perhaps a new module that is a 'linker' module, which can just spit something out via the api to an external script, which simply triggers all the appropriate modules I'd like to autorun..
 I just haven't noodled out the architecture for having a new module fire upon agent connect that tells the external script 'yo, you should run all your shit now'
Totally open to suggestions though :D

Unfortunately, I don't think we will be able to support this request at this time.


Add AVX2 support requirement

Added a note about the binaries requiring AVX2 support.

@Praetonus Does it look better now?

I'm going to merge the PR, and we can revert if we manage to sort out the general issue with Travis. Thanks.


Removed redundant h1 tags

As you can see the screenshot below, h1 tag is not straight in description field as expected.

@umitdincel I think the build/items.json file is generated by https://github.com/odota/dotaconstants/blob/master/tasks/updateconstants.js so any changes you make to it may just get overridden the next time updateconstants is run. You may need to add the logic to strip out the html there.
Although I don't see the h1 tags in the source of that file anymore, so maybe it was an issue that valve already fixed and we just need to run updateconstants again.

yeah, we can confirm with the next update

Thank you for the clarification @coreymaher


Can we bring back the pre-check for existing jmx agent in JmxAgent9?

JmxAgent9 removed the pre-checking for the JmxAgent status before starting it's own, which is different from JmxAgent8. This means if the agent has already started via command line properties passed to the jvm, JmxAgent9 will run into this exception when calling: virtualMachine.startManagementAgent(properties), which tends to cause confusion unnecessary.

This should be fixed by https://github.com/airlift/airlift/pull/733


Add push commits history comment on PR time-line

Add push commits history comment on PR time-line
Add notify by email and ui of this comment type also

view:

email

@a1012112796 didn't looked at the code jet ... so question: Do a ForcePush delete old comments to commits who are gone now?

@a1012112796 didn't looked at the code jet ... so question: Do a ForcePush delete old comments to commits who are gone now?

I haven't do it now. first I have no idea now, Then I think keep old commits  comment is usefull if you want find out previous commit that you has delted.
I will fix code lint and do some ui change this night.

The reason why this PR is marked as draft again is that I found the force-push judgment is wrong and I need to find other strategies. Thanks.

take your time :)

@guillep2k How about this way? ebde1d3

ebde1d3

Well, what I'd like to avoid is this kind of untranslated message:
{{printf "pushed %d commits to %s:" .Comment.Commits.Len .Comment.Issue.PullRequest.HeadBranch}}

We should use .Tr( .... ) and add the string to the en_US locale.

ebde1d3

Well, what I'd like to avoid is this kind of untranslated message:
{{printf "pushed %d commits to %s:" .Comment.Commits.Len .Comment.Issue.PullRequest.HeadBranch}}

We should use .Tr( .... ) and add the string to the en_US locale.

I see .It's an existing TODO  in here
https://github.com/go-gitea/gitea/blob/9f959ac0641821148e46d0899b74cc714c858879/services/mailer/mail_issue.go#L123-L127
To translate email , I think we have two things should be done firstly.

check each reciver main Language before send
do subjectTemplates.ExecuteTemplate() for each user,  because each user may have different language.  now it only run one time for each message. see
https://github.com/go-gitea/gitea/blob/9f959ac0641821148e46d0899b74cc714c858879/services/mailer/mail.go#L238-L245

But maybe this changes are far away form this PR's plan ...

ebde1d3

Well, what I'd like to avoid is this kind of untranslated message:
{{printf "pushed %d commits to %s:" .Comment.Commits.Len .Comment.Issue.PullRequest.HeadBranch}}

We should use .Tr( .... ) and add the string to the en_US locale.

maybe about this issue https://github.com/go-gitea/gitea/issues/3622

Well, what I'd like to avoid is this kind of untranslated message:

I see .It's an existing TODO in here
But maybe this changes are far away form this PR's plan ...

You are right about that! I really shouldn't check code at 2:00 AM. 😔
I'll give this PR a new look.

Does this pull hide/delete old comments when a force pull delete somme commits out of a pull now?

Does this pull hide/delete old comments when a force pull delete somme commits out of a pull now?
Just to be clear :)

Currently, old commits are not displayed on the UI when they are actually deleted by git gc .

@a1012112796 @lafriks for GetBranchName()
to strings.Split(strings.Split(strings.Split(string(data), " ")[1], "~")[0], "\n")[0]
the part:  strings.Split(var, "~")[0] will cut ~22 out of the responce ... so we should change the comment - or did I miss something?

I would actually prefer that json would be used to content so there would be no need for such parsing

JSON FTW!!

The break in the line looks very weird on dark theme. I would just remove that break, I see no purpose. If you still want to have breaks, add them before/after the icons on the timeline.

I guess you can just do this:
.timeline-item .badge-nobg {
    border-color: transparent !important;
    background: radial-gradient(#383c4a 50%, transparent 50%) !important;
}

This gives a nice commit icon with smaller break in the line:

383c4a is the arc-green background, use the white one for the light theme.

Please change to save content in json
Sounds great, I will try it.

I guess you can just do this:
.timeline-item .badge-nobg {
    border-color: transparent !important;
    background: radial-gradient(#383c4a 60%, transparent 60%) no-repeat !important;
}

This gives a nice commit icon with smaller break in the line:

#383c4a is the arc-green background, use the white one for the light theme. The 60% depends on icon dimensions, so maybe you want to rename .badge-nobg to .badge-commit so it does only gets used for those.

Sorry, I forget dark theme, I will try it and have more check, Thanks.

I would actually prefer that json would be used to content so there would be no need for such parsing

@lafriks  But I have no ideal about how to transform a commit into a json struct, It have many different type value and many sub struct .... 😢
https://github.com/go-gitea/gitea/blob/a1f11a05e900f3d1130729b2095dbf1b3037658e/modules/git/commit.go#L25-L39

so looking properly at this. I'm not actually sure where @lafriks meant for you to use JSON here. (My JSON FTW! comment was clearly not helpful.) @lafriks unfortunately we will have to do this parsing at some point.
The code I think everyone is most displeased about is:
https://github.com/go-gitea/gitea/blob/bcbc8b2e3e7e32f9dbce9abe8e642c6f903b7314/modules/git/commit.go#L469-L478
in particular L477. It doesn't take too much to see this is not maintainable - hell it's not even debuggable.
Split this line out with comments.

i.e.
// `git name-rev $REV` returns a line: SHA_COMMIT_40_BYTE DESCRIBED_NAME
// e.g. from https://git-scm.com/docs/git-name-rev#_examples
// % git name-rev 33db5f4d9027a10e477ccf054b2c1ab94f74c85a
// 33db5f4d9027a10e477ccf054b2c1ab94f74c85a tags/v0.99~940
// We know the SHA so we take the second portion
shaRevName := strings.TrimSpace(string(data))

index := strings.IndexOf(shaRevName, " ")
if index < 0 {
  log.Error("....")
  return ""
}
revName := shaRevName[index+1:]

// Now revName is "branch" or "branch~xxx" where xxx is a number of commits beyond the named branch point
// We only want the branch portion
index = strings.IndexOf(revName, "~")
if index >= 0 {
   return revName[:index]
}
return revName

@zeripath How about this syle? Thanks. 9001a4f

I would actually prefer that json would be used to content so there would be no need for such parsing

@lafriks But I have no ideal about how to transform a commit into a json struct, It have many different type value and many sub struct .... 😢
https://github.com/go-gitea/gitea/blob/a1f11a05e900f3d1130729b2095dbf1b3037658e/modules/git/commit.go#L25-L39

Need help about json, Thanks

What I meant about json it to have comment Content field value saved in json using structure like:
type PushActionContent struct {
    IsForcePush bool
    Commits     []string
}

this way IsForcePush would not need to be saved to database and no migration would be needed

@lafriks your review is required. 😁

Ping LG-TM

sadly I found a "bug" https://github.com/go-gitea/gitea/issues/11536


Adding capabilities to bypass SELinux Enabled Linux System

I don't have much knowledge about this till now. I will try to update this Issue when ever I get something important regarding this
Thanks to @Zibri for reminding this to me

"One is glad to be of service." :D

Any update? :)


Add many more options that can be read from the environment. Update u…

Add many more options that can be read from the environment. Update usage to mention environmental variables.
Fixes #372

Why weren't all the options updated?
Also, this needs some form of documentation :)

I left off the deprecated ones and the ones that seemed to be in the block listing command line arguments.
I added a line to the usage docs indicating most config file options are also available as environmental variables, in all caps.

We should have some tests for the new functionality too. Perhaps just ensure the core settings, and the settings for transports which already have tests are covered?

Ping @jhmartin , will you have chance to finish off this PR?

I should be able to submit the last of the env options, but my python knowledge and time isn't sufficient to add test cases for it.

Closing due to inactivity. Feel free to reopen!


Multiclass selfie segmentation

Can you please write a small code in which i can use multiclass selfie segmentation on my local machine?

Hey @m22cs058 - I'm not sure I understand the request. Multiclass selfie segmentation should already exist in the category_mask segmentation example. Here's a quick video from that sample: https://photos.app.goo.gl/ia24YF52t7ooHcak9

Hi @PaulTR Tested on Android 11T (21081111RG) works well with CPU delegate but catch "Batch size mismatch" error when modify to GPU. I use this device and use mediapipe studio demo, when selecting Multi-class Selfie Segmenter 256 and GPU it seems to have the same error, I think the problem is the GPU model on this device but when testing other models like Selfie Segmenter, Hair Segmenter and Deeplab V3 with the GPU delegate still working as expected
Log Details:
 E  Image segmenter failed to load model with error: invalid argument: CalculatorGraph::Run() failed in Run:
                                                                                Calculator::Open() for node "mediapipe_tasks_vision_image_segmenter_imagesegmentergraph__mediapipe_tasks_core_inferencesubgraph__inferencecalculator__mediapipe_tasks_vision_image_segmenter_imagesegmentergraph__mediapipe_tasks_core_inferencesubgraph__InferenceCalculator" failed: Batch size mismatch, expected 1 but got 8

Going to reopen this for tracking. Will be a bit before I'm back from leave and can look into it, but hopefully someone else from my team can check ti out.

Hi @PaulTR
I am trying to get separate masks using the SelfieMulticlass (256 x 256) model on python, similar to the demo on Mediapipe Studio. I am only able to segment the foreground at the moment and not the category mask.
Thanks

Hi @PaulTR, I'd like to know if there is any update on this?

Not yet. Just got back from leave not long ago and right in to Google IO so
it'll be a minute before I can find the time to catch back up :) it's
definitely on the to-do list though!
On Mon, Apr 29, 2024, 9:46 PM Kai Dao @.***> wrote:

Hi @PaulTR https://github.com/PaulTR, I'd like to know if there is any
update on this?
—
Reply to this email directly, view it on GitHub
https://github.com/googlesamples/mediapipe/issues/164#issuecomment-2084323193,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAR2C37VQ2ZZWTT6WGAU7ODY74HY5AVCNFSM6AAAAAAZEUBZKSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOBUGMZDGMJZGM
.
You are receiving this because you were mentioned.Message ID:
@.***>


Tree scroll bars issue after page import

Extra & unnecessary scroll bars appear on the tree section after importing pages (or glossary):

Looks like extra  are added by the system

Does #d2c4ed34fe6c93d06ec976f9b2f5c3aef48f9dd8 fix it for you @FayCross ?

Yes, thanks @JohnSmith-LT


Feature request: Publish AWS Lambda layers under /aws/service/list

Use case
I would like to be able to dynamically lookup the latest available AWS Lambda layer ARN.
Solution/User Experience
AWS has already been maintaining a list of public SSM parameters, please consider enlisting powertools-lambda-python too. Similar to ref. https://aws-sdk-pandas.readthedocs.io/en/latest/install.html#aws-lambda-layer
$ aws ssm get-parameters-by-path --path /aws/service/list
$ aws ssm describe-parameters --parameter-filters 'Key=Name, Option=BeginsWith, Values=/aws/service/aws-sdk-pandas/' --query 'sort_by(Parameters, &LastModifiedDate)'

Sample code
powertools_layer_arn = ssm.StringParameter.from_string_parameter_attributes(self, "MyValue",
  parameter_name="/aws/service/powertools-lambda-python/x.y.z/py3.xx/x86_64/layer-arn"
).string_value

Alternative solutions
Hardcoded Lambda layer ARN

Acknowledgment

[X] This feature request meets Powertools for AWS Lambda (Python) Tenets
[X] Should this be considered in other Powertools for AWS Lambda languages? i.e. Java, TypeScript, and .NET

Hello @avoidik! Thanks for opening this issue to add our Lambda layer in public parameters. This feature makes it easier to automate the use of the latest layer in customer's pipelines. However, we need to do some internal processes to add our layer to this list and I don't have an ETA for completing this as it involves other teams.
Starting tomorrow I will carry out these processes and as soon as I have an update I will let you know here.
Thank you.

We have nearly completed work on this and will be available shortly.


create_user not working in release 5.0.1

I am trying to call create_user as below
    from workos import WorkOSClient

    workos_client = WorkOSClient(
        client_id=settings.WORKOS_CLIENT_ID,
        api_key=settings.WORKOS_API_KEY,
    )

    test = workos_client.user_management.create_user(
<EMAIL_ADDRESS>    )

and I am getting a bad exception error:
BadRequestException

message=Validation failed, request_id=3dd335f4-a8c7-4548-9d6f-abf4f50e7061, code=invalid_request_parameters, errors=[{'code': 'email_string_required', 'message': 'Email must be a non-empty string.'}])

The logging shows that the data is being sent as query parameters:
INFO 2024-08-19 07:30:08,028 _client<PHONE_NUMBER>61516672 HTTP Request: POST https://api.workos.com/user_management/users?email=john%40example.com "HTTP/1.1 422 Unprocessable Entity"

If I call the api directly it works

Thanks for the report, we're looking into this and will have a fix up soon.

Hi @AbundantSalmon - this has been fixed in v5.0.2 along with some improved testing surrounding this issue.


Migrate from ListView to FlatList/SectionList

React Native 0.43 included new FlatList and SectionList components - ListView is deprecated.
Migrate to SectionList and FlatList as appropriate.

https://facebook.github.io/react-native/blog/2017/03/13/better-list-views.html
https://facebook.github.io/react-native/docs/sectionlist.html
https://facebook.github.io/react-native/docs/flatlist.html

https://github.com/calvinf/versesforlife-app/tree/flastlist

This issue is resolved - we're now using FlatList in the VerseList component in the relevant pack and topic scenes.


Support for animated collision boxes

Many sprite animation tools allow collision boxes that can be animated on a frame by frame basis.
http://www.youtube.com/watch?feature=player_embedded&v=FFQYUtAWZXs

Hey How are you doing?
I'm very interested on this project and probably use it to make the animations of a platformer game I'm making.
I was looking exactly for what this issue is pointing, are you planning on continuing this job? I'm a c# programmer and I could help you to build this functionality if it isnt done yet.
Regards!

Currently, I'm not working on Sprites And Bones. If you're interested in doing some work, feel free to do so.
Sprites And Bones is open source. The more people are working with it, the happier I am :).


Get-EnterprisePKIHealthStatus.ps1

The Get-EnterprisePKIHealthStatus.ps1 script doesn't seem to have been updated with the new SysadminsLV.PKI name space.

fixed in v4.2


Fix typo in browserslistrc file name

The proper name for the browserslist config file is .browserslistrc

Thanks for fixing the doc issue. Have removed it to target the ahead branch as I'm about to push some other small changes to this file as well (and don't want to risk yours being overwritten 😁)


Creating symlinks as update stage tasks

Feature Request
Creating symlinks as update stage tasks
Feature Information:
The ability to add the creation of symlinks as an update stage task
I confirm:

[x] that I have searched for an existing feature request matching the description.

Implemented. "UpdateSourceArgs" is the 'name' of the symlink and "UpdateSourceData" is the origin directory.


ISPN-5805 Allow forEach consumer to have a Cache Injected

ISPN-5845 Update local cache stream to allow for full wrapping
https://issues.jboss.org/browse/ISPN-5805
https://issues.jboss.org/browse/ISPN-5845

@wburns Getting closer to moving M/R over to streams?

@danberindei it isn't really possible to move them over at least with a full translation without M/R being quite a bit slower in many cases :( - I believe we will just remove M/R with 8.3, right @tristantarrant ?

Updated

@wburns @danberindei dropping in 9.0

Just a couple of comments. Looks good otherwise

Updated

Updated to add fail messages if no matching cache.  Also I consolidated quite a few of the methods to use a new supplier based one to get rid of all of the boilerplate creation of cache stuff I could.

@wburns I'm getting these failures almost every time I run the HotRod client tests on my machine:
ExpiryTest.testGlobalExpiryPutWithFlag:46->expectExpiryAfterRequest:99->expectCachedThenExpired:103 expected:<v1> but was:<null>
ClientListenerWithIndexingAndProtobufTest.testEventFilter:78 expected:<1> but was:<0>
RemoteListenerWithDslFilterTest.testEventFilter:135 expected:<3> but was:<0>

@danberindei thanks, will take a look :)

It doesn't seem that ExpiryTest is related.  It also failed on http://ci.infinispan.org/viewLog.html?buildId=31455, I wonder if it is because of reaper.  I am still looking at the others.

Okay I have rewritten the type converter part now to properly unwrap only after the iterator method is invoked.  This should clean up those failures.  I have tried to break this up into a few commits.  I know there is quite a bit.
Please let a test run go by first, it passed locally, so I am hoping it is all good here.

Tests all seem to be fine now.

I added some more questions, mostly about comments...

Updated from comments.

Integrated, thanks Will!


[WIP] Replace "/" with ""

Details here: https://metalsmith.slack.com/archives/general/p1448044526000600

Created a new pull request in #19


Fail to pull docker image of Apollo 6.0

OS Platform and Distribution (e.g., Linux Ubuntu 18.04): 18.04
Apollo version (3.5, 5.0, 5.5, 6.0): 6.0 / master

Steps to reproduce the issue:

git clone https://github.com/ApolloAuto/apollo.git
cd apollo
bash docker/scripts/dev_start.sh

I was working with the branch "pre6" and everything works fine, then I wanted to upgrade and work with the release 6.0 or upper. I have tried many times to install the master or the 6th release, but I cannot run Apollo. It always fails to pull the docker image:  apolloauto/apollo:dev-x86_64-18.04-20210517_1712 . Can you please help me to solve the issue?

I managed to solve the issue. It was irrelevant to Apollo itself. It was a problem with the synchronization of my system local time, universal time, and RTC time.

Could you share how to solve the synchronization  problem, I am encountering same issue as well.


[NuGet.org Bug]: Face 504/502 errors while Restore Packages on AWS eu-centasl-1 region

Impact
I'm unable to use NuGet.org
Describe the bug
while using dotnet cli restore we started to get 502 and 504 errors from Nuget
for test we run curl with this url: https://api.nuget.org/v3-flatcontainer/awssdk.core/index.json
we run it from a machines in aws eu-central-1a and eu-cenbtral-1b and fails most of the times (not always)
on eu-central-1c it worked every time we run the command
when we test it using curl command and it fails, instead of results we get the following message:
`

Our services aren't available right now
We're working to restore all services as soon as possible. Please check back soon.

20240111T122751Z-dp7f50w70h3shb2hut61khm0p400000003e000000000x5q3

`
Repro Steps
curl https://api.nuget.org/v3-flatcontainer/awssdk.core/index.json from AWS in regions eu-central-1a and eu-central-1b
repeat the same for region eu-centeral-1c and it works
Expected Behavior
should work on every region
Screenshots
No response
Additional Context and logs
No response

Our services aren't available right now
We're working to restore all services as soon as possible. Please check back soon.

20240111T122751Z-dp7f50w70h3shb2hut61khm0p400000003e000000000x5q3

we are also facing same issue in aws region eu-south-1
Retrying 'FindPackagesByIdAsync' for source 'https://api.nuget.org/v3-flatcontainer/microsoft.extensions.configuration.json/index.json'.
  Response status code does not indicate success: 502 (Bad Gateway).

Same here. I see it from yesterday, but today, it fails all the time and none of my builds runs can finish. The release pipeline is stuck on this.

There are some recent similar complains here and here.

My sincere apologies for the inconvenience! Our primary CDN provider is having an outage, and we have switched the traffic to the other CDN. Please let me know if you see that the issue is still ongoing.

It's working for us right now.

Why wasn't the CDN degradation issue posted on status.nuget.com?

Why wasn't the CDN degradation issue posted on status.nuget.com yesterday? Issues happen and things fall over but it would be great to see these updates/issues on the status page going forward

Yes, this is not good. We have a monitoring gap there, and the failover should have been executed hours ago, when the outage of our dependency just started happening.
We will enhance the monitoring system and consider a better strategy to update the status page in an effective and automatic way.
Thank you for sharing the concern!

Thank you @zhhyu. That's great to hear


Show and Restore archived playbooks

Summary
This PR allows users to see archived Playbooks in the backstage, and restore them.
TLDR:
Server:

The playbook listing API now accepts a with_archived query (values: true/false; default false)
The OpenAPI/Swagger file has been updated accordingly.

Webapp:

Adds a "With archived" filter
Adds a restore option for the archived playbooks
Show an icon+tooltip combo to indicate that a playbook is archived.

Screenshots:
Playbook list (new With archived filter + icon bellow archived playbooks)

Restore menu option on an archive playbook

Restore confirmation modal

edit: The broken e2e test (playbooks > overview > should copy playbook link) seems to be present on master too
Ticket Link
N/A
Checklist

- [ ] Telemetry updated
- [ ] Gated by experimental feature flag

[x] Unit tests updated
[x] e2e tests added

Hello @JulienTant,
Thanks for your pull request! A Core Committer will review your pull request soon. For code contributions, you can learn more about the review process here.

This PR has been automatically labelled "stale" because it hasn't had recent activity.
A core team member will check in on the status of the PR to help with questions.
Thank you for your contribution!
/cc @BenLloydPearson @aspleenic

Sorry for the long review cycle here. This kinda got dropped over the holidays.

No problem!

The PR looks good overall. It's going to need a bit of merging work given some of the changes. Feel free to reach out to me on community server if you need some help.
Feel free to wait until Monday to get started on this. Welcome BTW smile

Thank you Christopher! I did it now as I don't quite know yet what's coming for me next week - you probably know I've not been assigned to the Playbooks team but to the Growth team.
I replicated what has been done on the "archive" part (modal on a dedicated tsx file).
Note: Just confirmed with @cass.caplinger on the community server that the archive button does not refresh the page automatically. I remember hooking up on this to auto-refresh the list when a playbook was restored - so it's not working here anymore.

Hey @JulienTant, and welcome again! Sorry for the delay on reviewing this. Do you mind merging to master and addressing Cass's comment, then I'll take a look at it? (Let us know if you need help with the merge!)

Hey @JulienTant, and welcome again! Sorry for the delay on reviewing this. Do you mind merging to master and addressing Cass's comment, then I'll take a look at it? (Let us know if you need help with the merge!)

Hi @cpoile, thanks! The wording has been changed archive and master has been merged into the branch.

@JulienTant Sorry again, but it looks like things keep changing underneath this PR. 😅

@cpoile Fixed 😅


Service Line needs event OnAfterCheckItemAvailable in procedure CheckItemAvailable

Service Line needs event OnAfterCheckItemAvailable in procedure CheckItemAvailable

    //>>> event request
    OnAfterCheckItemAvailable(Rec, CalledByFieldNo);
    //<<<

Integration event
[IntegrationEvent(false, false)]
local procedure OnAfterCheckItemAvailable(var Rec: Record "TSRM Service Line"; CalledByFieldNo: Integer)
begin
end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 12553.


Refactor the whole library to v1.5

Progress:

[x] xdto
[x] xfiber
[x] xgin
[x] xrecovery
[x] xserverchan
[x] xtelebot
[x] xvalidator

Released.


No Sound Using  Windows 7 Pro 64

I have downloaded an tried to run chromecast-audio-stream on a Win 7 x64 computer. I get the icon and can connect to the Chromecast device (I get the connected sound), but the icon does not change and it will not stream any audio.
I have tried moving the application folder to C:/ and renaming it to Chromecast. I have also tried changing the ffmpeg file to an x64 version without success so I changed it back again to the 32 bit version.
This is the out when starting the program from CMD.
c:\Chromecast>audio-cast.exe

c:\Chromecast>
c:\Chromecast
Example app listening at http://<IP_ADDRESS>:49378
Selected Audio Device:
<IP_ADDRESS> Galactica Cast 1
Spawned Ffmpeg with command: ffmpeg -list_devices true -f dshow -i dummy pipe:1
An error occurred: ffmpeg exited with code 1: dummy: Immediate exit requested

c:\Chromecast\resources\bin\driver\win32\RegSvrEx.exe /c c:\Chromecast\resources
\bin\driver\win32\audio_sniffer.dll
stdout: Error occured registering server - The specified module could not be fou
nd.

stderr:
exec error: Error: Command failed: C:\Windows\system32\cmd.exe /s /c "c:\Chromec
ast\resources\bin\driver\win32\RegSvrEx.exe /c c:\Chromecast\resources\bin\drive
r\win32\audio_sniffer.dll"

The error messages just keeps repeating. This is what I get after connecting to the Chromecast device. Same as before the error messages at the end keeps repeating.
app "[object Object]" launched, loading media [object Object] ...
Spawned Ffmpeg with command: ffmpeg -list_devices true -f dshow -i dummy pipe:1
An error occurred: ffmpeg exited with code 1: dummy: Immediate exit requested

c:\Chromecast\resources\bin\driver\win32\RegSvrEx.exe /c c:\Chromecast\resources
\bin\driver\win32\audio_sniffer.dll
Device requested: /
Spawned Ffmpeg with command: ffmpeg -f dshow -i audio=virtual-audio-capturer -ac
odec libmp3lame -f mp3 pipe:1
stdout: Error occured registering server - The specified module could not be fou
nd.

stderr:
exec error: Error: Command failed: C:\Windows\system32\cmd.exe /s /c "c:\Chromec
ast\resources\bin\driver\win32\RegSvrEx.exe /c c:\Chromecast\resources\bin\drive
r\win32\audio_sniffer.dll"

Spawned Ffmpeg with command: ffmpeg -list_devices true -f dshow -i dummy pipe:1
An error occurred: ffmpeg exited with code 1: audio=virtual-audio-capturer: Inpu
t/output error

ffmpeg version N-69406-ga73c411 Copyright (c) 2000-2015 the FFmpeg developers
  built on Jan 29 2015 23:07:55 with gcc 4.9.2 (GCC)
  configuration: --arch=x86 --target-os=mingw32 --cross-prefix=/home/videostream
/Downloads/sandbox/mingw-w64-i686/bin/i686-w64-mingw32- --pkg-config=pkg-config
--enable-gpl --enable-libx264 --enable-avisynth --enable-libxvid --enable-libmp3
lame --enable-version3 --enable-zlib --enable-librtmp --enable-libvorbis --enabl
e-libtheora --enable-libspeex --enable-libopenjpeg --enable-gnutls --enable-libg
sm --enable-libfreetype --enable-libopus --disable-w32threads --enable-frei0r --
enable-filter=frei0r --enable-libvo-aacenc --enable-bzlib --enable-libxavs --ext
ra-cflags=-DPTW32_STATIC_LIB --enable-libopencore-amrnb --enable-libopencore-amr
wb --enable-libvo-amrwbenc --enable-libschroedinger --enable-libvpx --enable-lib
ilbc --prefix=/home/videostream/Downloads/sandbox/mingw-w64-i686/i686-w64-mingw3
2 --enable-static --disable-shared --enable-libsoxr --enable-fontconfig --enable
-libass --enable-libutvideo --enable-libbluray --enable-iconv --enable-libtwolam
e --extra-cflags=-DLIBTWOLAME_STATIC --enable-libzvbi --enable-libcaca --enable-
libmodplug --extra-libs=-lstdc++ --extra-libs=-lpng --enable-libvidstab --enable
-libx265 --enable-decklink --extra-libs=-loleaut32 --extra-cflags= --extra-cflag
s= --enable-nonfree --enable-libfdk-aac --disable-libfaac --disable-decoder=aac
--enable-runtime-cpudetect
  libavutil      54. 18.100 / 54. 18.100
  libavcodec     56. 21.101 / 56. 21.101
  libavformat    56. 19.100 / 56. 19.100
  libavdevice    56.  4.100 / 56.  4.100
  libavfilter     5.  9.101 /  5.  9.101
  libswscale      3.  1.101 /  3.  1.101
  libswresample   1.  1.100 /  1.  1.100
  libpostproc    53.  3.100 / 53.  3.100
[dshow @ 040fb9e0] Could not find audio only device with name [virtual-audio-cap
turer] among source devices of type audio.
[dshow @ 040fb9e0] Searching for audio device within video devices for virtual-a
udio-capturer
[dshow @ 040fb9e0] Could not enumerate audio only devices (or none found).
audio=virtual-audio-capturer: Input/output error

An error occurred: ffmpeg exited with code 1: dummy: Immediate exit requested

c:\Chromecast\resources\bin\driver\win32\RegSvrEx.exe /c c:\Chromecast\resources
\bin\driver\win32\audio_sniffer.dll
stdout: Error occured registering server - The specified module could not be fou
nd.

stderr:
exec error: Error: Command failed: C:\Windows\system32\cmd.exe /s /c "c:\Chromec
ast\resources\bin\driver\win32\RegSvrEx.exe /c c:\Chromecast\resources\bin\drive
r\win32\audio_sniffer.dll"

Spawned Ffmpeg with command: ffmpeg -list_devices true -f dshow -i dummy pipe:1
An error occurred: ffmpeg exited with code 1: dummy: Immediate exit requested
```

Try running this command manually?
c:\Chromec
ast\resources\bin\driver\win32\RegSvrEx.exe /c c:\Chromecast\resources\bin\drive
r\win32\audio_sniffer.dll

Tried running the command manually and got the error message:
The program can't start because MSVCR100.dll is missing from your computer.
I tried installing Microsoft Visual C++ 2010 x64 as suggested several places and also verified that msvcr100.dll is in fact in the C:\Windows\System32 folder, but I am still getting the same error message.

Fixed the issue! I needed to install Microsoft Visual C++ 2010 x86 even though my computer is x64. I guess it relates to the application, which i should have thought about. Have quite a lot of delay on the sound though (4+ seconds), but I guess that is to be expected :)


chore(README): add npm install hint

This change is a temporary fix for https://github.com/bpmn-io/dmn-testing-plugin/issues/15
Related to https://github.com/bpmn-io/dmn-testing-plugin/issues/17
Definition of Done

[ ] corresponds to the design principles
[ ] corresponds to the code standards
[ ] passes Continuous Integration checks
[ ] available as feature branch on GitHub

[ ] contains the cleaned up commit history
[ ] commit messages satisfy our commit message guidelines
[ ] a single commit closes the issue via Closes #issuenr

Good stuff! We should definetly add this hint


Select: Support subquery values when using plain map

This PR extends the select functionality to support subqueries.
subquery =
  from(c in "comments",
    where: c.post_id == parent_as(:post).id,
    select: count()
  )

from(p in "posts,
  as: :post,
  select: %{
    comment_count: subquery(subquery)
  }
)

This is extracted from the larger PR #3927.
All feedback welcome! 🙏

Your changes are great and correct. The change in builder is not ideal but it is because we were lazy in the past, so definitely not your fault. I will sleep on it and likely merge tomorrow. Thank you!

@arnodirlam the cleanest approach would be to explicitly pass subqueries as a parameter to escape, but this would be a hundreds LOC changes and I am thinking it is probably just better to keep the "hack" and drop a comment to why it exists.

All good, better to find long-term solutions than to rush things 🙂 That's great, looking forward to your plan!

:green_heart: :blue_heart: :purple_heart: :yellow_heart: :heart:

Addressed your recent comments, @josevalim. Thanks for the great guidance! 🙏

@arnodirlam I think the correct fix would be to change params_acc to, instead of a {list, term}, it should be a tuple of shape {list, map}. The map can have the optional keys :take or :subqueries. This should be a more doable change because we don't need to change the shape of params_acc altogether, only of the second element, and the map shape makes it easier to know when take and subqueries are supported.
Would you like to send a PR to tidy this up? It would be very welcome! You can start by changing the code modified in this PR to pass a map instead of {take, subquery} and, if it works, we generalize for other operations. WDYT?

Yes, happy to implement this! 👍 will have a first look later today.
I opened #3931 for the renaming of params_take that was still missing here. I can extend that PR with the refactoring, if you prefer fewer, bigger PRs, or you can merge it and I open a new one.


Fix _approx_count_distinct on non-clustered interface, optimize _stats

Overview
One bugfix and one enhancement here. The bugfix is that the finalize operation introduced for _approx_count_distinct was not being executed on view requests coming in through the non-clustered interface, so any attempt to use that reduce function there would crash.
The enhancement is to take advantage of that finalize operation to optimize the builtin _stats reduce function. Previously the reduce function would always write down an ejson form for the 5 statistical quantities to disk as it could never know whether the rereduce function was being called during indexing or during querying. Now that we have the finalize operation (which only runs at query time) we can store a more compact format on disk and avoid continuously translating back and forth between the compact and ejson formats during indexing. This should result in slightly more efficient builds and slightly smaller resulting indexes.
Testing recommendations
Run the _stats tests against clustered and non-clustered interfaces.
Checklist

[x] Code is written and works correctly;
[x] Changes are covered by tests;
[x] Documentation reflects the changes;

OK I think that's sorted now. Tested both _stats and _approx_count_distinct on both 5984 and 5986. Not the most elegant thing in the world but I think it's clear enough and won't be too brittle going forward if we should need to do other things around finalizing these reductions.

dare I ask for automated tests?

@wohali not 100% sure what you mean. Travis is running the automated tests for both of those and catching where I've missed something. In this case I missed the fact that _statsorama and _stats\nare\nawesome are apparently valid ways to invoke the _stats reduce function 🙄. Thanks JChris!
If you're saying I ought to run the full test suite locally before opening the PR ... yes OK I need to figure out how to do that. I futzed with the firewall on my laptop a bit and eventually gave up.
If you're saying we need to test both 5984 and 5986 as part of the test suite that's probably worth filing an issue.

My mistake - I thought this was a new feature (missed that that particular PR already landed) and was looking for tests specific for those new features. If the tests are already in place, no need to add any.
Yeah, that sounds like a useless feature we should remove.
make check should run the full test suite for you, at least on a single Erlang. No need to test against all the various erlangs, Travis can take care of that. Not sure what's up with your laptop if make check fails there.

Ah yeah @nickva added JS tests to my original PR for the feature.
When I run make check locally it hangs because 3 dialogs pop up asking me to allow incoming network access for the various beam.smp processes and then they disappear before I can address them. 🤷♂ I'm sure I'll sort it out eventually.

Ah, Little Snitch? Try adding blanket allow rules for it. The new Silent Mode stacks up the notifications so you can review them later, that might work for you.
https://help.obdev.at/littlesnitch/#/intro-opmodes

One more thing that needs to be done is to include the app in the app dependencies for couch:
https://github.com/apache/couchdb/blob/master/src/couch/src/couch.app.src#L50

PR to add hyper to app dependencies: https://github.com/apache/couchdb/pull/1379


Add a default url-loader configuration for common asset types

I have always needed this in my projects, and in the rare case it isn't needed it just silently sits there without impact.

Currently trying to achieve something similar. Not sure if its completely related.
I am using fontgen loader to generate an own icon font:
        merge(
          // { test: /\.font\.(js|json)$/ },
          { test: /\.font$/ },
          ifServer({
            loaders: [
              'fake-style-loader',
              'css',
              'fontgen'
            ]
          }),
          ifClient({
            loaders: [
              'style',
              'css',
              'fontgen'
            ]
          })
        ),

This works like a charm for actual building, but not in "development" due to the publicPath
      publicPath: ifDev(
        // As we run a seperate server for our client and server bundles we
        // need to use an absolute http path for our assets public path.
        `http://localhost:${process.env.CLIENT_DEVSERVER_PORT}/assets/`,
        // Otherwise we expect our bundled output to be served from this path.
        '/assets/'
      ),

This causes errors in webpack trying to load in development:
ERROR in ./~/css-loader!./~/fontgen-loader!./src/style/awesomecons.font
Module not found: Error: Can't resolve './http:/localhost:8006/assets/24f28e5640d6697dce825a7a13eb1a26-Awesomecons.eot' in '/Users/marc/Sites/react-universally/src/style'
 @ ./~/css-loader!./~/fontgen-loader!./src/style/awesomecons.font 6:88-177
 @ ./src/style/awesomecons.font
 @ ./src/components/App/App.js
 @ ./src/components/App/index.js
 @ ./src/routes/index.js
 @ ./src/index.js
 @ multi main

I am not 100% sure how to handle static assets such as fonts with universal rendering.

For font's I just use a straight up url-loader.
For example, in the loaders config:
     loaders: [
        // Images and Fonts
        {
          test: /\.(jpg|jpeg|png|eot|svg|ttf|woff|woff2)$/,
          loader: 'url-loader',
          query: {
            limit: 10000,
          },
        },

And then you can import fonts/images/etc in your components or CSS.  Webpack will convert them into URLs.  This works on the server too.
For example:
import myImage from './myImage.png';
import React from 'react';

function Foo() {
  return (
    <img src={myImage} />
  );
}

It works for fonts too, and within your CSS, for example:
.img {
  background: url('./myImage.png');
}

It's great as you can colocate your images/fonts with your css.
In my project I import my fonts manually in my CSS:
@font-face {
  font-family: 'YanoneKaffeesatz';
  src: url('./fonts/YanoneKaffeesatz.eot?#iefix') format('embedded-opentype'),  url('./fonts/YanoneKaffeesatz.woff') format('woff'), url('./fonts/YanoneKaffeesatz.ttf')  format('truetype'), url('./fonts/YanoneKaffeesatz.svg#YanoneKaffeesatz') format('svg');
  font-weight: normal;
  font-style: normal;
}

@ctrlplusb Quick question on this old thread: If my image is colocated in the same folder, should I expect the following to work in my CSS file without any imports, etc:
.img {
  background: url('./myImage.png');
}

And should I then expect it to be bundled in public folder?
I ask since I can't get this to work and I wasn't sure if I was misunderstanding the usage?


tests: Various helpers cleanups

What this PR does / why we need it:
Start cleaning the e2e tests helpers (mainly tests/utils.go):

Move 'VerifyDummyNicForBridgeNetwork' out of utils
serviceaccount: Remove the 'util2' import alias
Extract service-account helpers from utils
Move an istio const closer to its usage
Remove unused file test.go

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Release note:
NONE

/retest

/test pull-kubevirt-e2e-k8s-1.23-operator

/lgtm

change: Fixed a commit message type (per the review).

/retest

/retest

change: Rebase & remove serviceaccount changes (as they have now a dedicated PR #7446)

/retest

/retest


merge from arlac77/template-arlac77-github,arlac77/template-esm-only

package.json

chore(package): add ./ (exports../)

:tada: This PR is included in version 2.1.17 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


It doesn't compile

node_modules/node-apriori/dist/apriori.d.ts(16,22): error TS2420:
Class 'Apriori' incorrectly implements interface 'IAprioriEvents'.
Property 'on' is missing in type 'Apriori'.

Added Building from source README and runnable example


Would it be better not to be able to change email address based on password?

Reasons for why this is because if someone cracks a password to an account they can change the email address with no problem and leaving the original user no chance of accessing it again. If we don't allow email changing the original can reset their password if their password is breached. What i suggest is allow users closing their own account and with that it sends an email message that has a link to reopen their account if they change their mind. Usually it would last like a week before expiring the reopen link. If they user wants a account in a new email it should be in a new account. What are your thoughts?

Another thing that could be possible is allowing multiple email address to an account. Then make the registering email the master email and if the attacker adds his email you can still reset your password with their master email.

Thanks for sharing this idea!
If you supply both the username (or email address) and the correct password, you are considered authenticated by this library and in most other places. That makes sense, doesn’t it? Supplying the correct password is your way of authenticating after all.
Now you would want to disallow this?
Who would get to change an account’s email address if not the client who successfully authenticated with a correct password?
Only a client who can prove control of the old email address as well? That would ignore that the reason for changing one’s email address may often be that the old one does not exist anymore. This is especially true if users visit your site only rarely.
Finally, requiring a new account in order to use a new email address ignores all experience from practical usage in the real world, in which this would be a huge annoyance to many users.
Security is not binary, or black and white. You always want tradeoffs between security and usability.
In your own application, you may decide what features to offer, of course. So if you don’t want to allow for password resets, just don’t implement that feature.
And if you want to let users decide for themselves, this is possible as well:
https://github.com/delight-im/PHP-Auth#enabling-or-disabling-password-resets


Adding additional GPIO for 40 pin RPi

I wasn't sure how to directly ask the author a question so I just posted this here. Sorry in advance.
I assume this is able to run on the RPi3? And since there are 40 pins (24 IO) rather than the 26 pins (17 IO) this was written for; is it possible for me to easily add the additional gpio to the enumerations? I would like to use all 24 IO but you currently only have 17. Is there any reason why I shouldn't or couldn't use them? Thanks.

No problem to ask here. Yes you can just add them to the enumerations, then you can create create a pull request or send me the code if you wish to share your code with the community :)

Hello,
it would be nice to be able to handle both configurations from the code :)
A manager init or conditional build ?
// define 17 IOs enums
#if RPI3
// define 7 remaining IOs enums
#endif


.with() seems to modify the existing selector, rather than return a new one

What is your Test Scenario?

I have a function that will add .with({visibilityCheck: true}) to selectors at various times when needed.
What is the Current behavior?

If you save a selector to a variable, and then add that .with() to it, it will permanently alter the variable
What is the Expected behavior?

According to the documentation, it's supposed to return a new selector
What is your web application and your TestCafe test code?
Your complete test code (or attach your test files):

import { Selector } from "testcafe";

// Here's a function I wrote to help print out what a selector chain looks like
function printSelector(selector) {
console.log(selector[Object.getOwnPropertySymbols(selector)[0]].options.apiFnChain.join(""));
}

let mySelector = Selector('button').withText('foo');
printSelector(mySelector);
// prints Selector('button').withText('foo')

await mySelector.with({visibilityCheck: true});
printSelector(mySelector);
// prints Selector('button').withText('foo').with({ visibilityCheck: true })

await mySelector.with({visibilityCheck: true});
await mySelector.with({visibilityCheck: true});

printSelector(mySelector);
// prints Selector('button').withText('foo').with({ visibilityCheck: true }).with({ visibilityCheck: true }).with({ visibilityCheck: true })

In all three of those print statements, I would not expect to see it print the .with()
Steps to Reproduce:

Run the above test code in any testcafe file

Your Environment details:

testcafe version: 1.7.1
node.js version: 11.10.1

Hi @stephenryanlee
The phrase return a new selector means that changing public options of the initial selector doesn't affect public options of a new selector.
options.apiFnChain is an internal API and you should not use it for any purposes.
If you found an issue with the with method, please prepare an example that uses a public API. Feel free to reopen this issue and share it.


Add missing attributes

Found in initial development of some pre-commit hooks in #261

[ ] "Barretts Esophagus Goblet Cells Present" used in component "Follow Up" is not defined in the data model
[ ] "Pancreatitis Onset Year" used in component "Follow Up" is not defined in the data model
[ ] "Flow" used in component "Bulk RNA-seq Level 1" is not defined in the data model
[ ] "Cell Barcode" used in component "Bulk RNA-seq Level 1" is not defined in the data model
[ ] "Proportion" used in component "Bulk RNA-seq Level 2" is not defined in the data model
[ ] "Targets No Coverage" used in component "Bulk RNA-seq Level 2" is not defined in the data model
[ ] "Genomic" used in component "scATAC-seq Level 2" is not defined in the data model
[ ] "Reference URL" used in component "scATAC-seq Level 2" is not defined in the data model
[ ] "Object ID" used in component "scATAC-seq Level 3" is not defined in the data model
[ ] "nCount Peaks" used in component "scATAC-seq Level 3" is not defined in the data model
[ ] "nFeature Peaks" used in component "scATAC-seq Level 3" is not defined in the data model
[ ] "Single Nucleus Capture" used in component "scmC-seq Level 1" is not defined in the data model
[ ] "Median Percentage of Mitochondrial" used in component "scmC-seq Level 1" is not defined in the data model
[ ] "Reads per Nucleus" used in component "scmC-seq Level 1" is not defined in the data model
[ ] "Genomic" used in component "scmC-seq Level 2" is not defined in the data model
[ ] "Reference URL" used in component "scmC-seq Level 2" is not defined in the data model
[ ] "Proportion Coverage 10X" used in component "scDNA-seq Level 2" is not defined in the data model
[ ] "HTAN Parent Channel Metadata ID" used in component "Imaging Level 3 Image" is not defined in the data model
[ ] "Spots under tissue" used in component "10x Visium Spatial Transcriptomics - RNA-seq Level 3" is not defined in the data model
[ ] "HTAN Parent Channel Metadata ID" used in component "Imaging Level 4" is not defined in the data model
[ ] "UNIPROT Protein ID Target" used in component "HTAN RPPA Antibody Table" is not defined in the data model
[ ] "Internal Ab ID" used in component "HTAN RPPA Antibody Table" is not defined in the data model
[ ] "Notes" used in component "HTAN RPPA Antibody Table" is not defined in the data model
[ ] "Instrument Make and Model" used in component "Mass Spectrometry Level 1" is not defined in the data model
[ ] "Channel QC Faliure Type" used in component "No - Channel Failed QC" is not defined in the data model
[ ] "Time between Waking and First Smoke" used in component "Yes - Smoking Exposure" is not defined in the data model

FYI @clarisse-lau many of these are like that you spotted in #253

Many of these fixes are due to differences in capitalization between the DependsOn entry and the Attributes. Suggest we harmonize based on the entry in the DependsOn.

@elv-sb just checking in on this?

Blood Tube Type - not used anywhere --> Is it needed for Blood Biospecimen Type?
Spots Under Tissue - used in 10x Visium Spatial Transcriptomics - RNA-seq Level 3 (Spots under tissue)
Channel QC Failure Type - Typo
Workflow Type - not used anywhere
Workflow Parameters Description - not used anywhere
Antigen Retrieval - not used anywhere - was removed from RFC Biospecimen Tier 2
Biospecimen Slide Location - not used anywhere - was removed from RFC Biospecimen Tier 1
Staining markers - not used anywhere - was removed from RFC Imaging Level 1 - v1
Age at Index - not used anywhere
Time Between Waking and First Smoke  - used in Yes, Smoking Exposure (Time between Waking and First Smoke)
Anatomic Site - not used anywhere
UNIPROT Gene Symbol Target - not used anywhere --> Could it have been mixed up with UNIPROT Protein ID Target  - Yes, in Antibody Table RPPA
Internal Antibody ID - not used anywhere --> Typo for Internal Ab ID used in HTAN RPPA Antibody Table
Antibody Notes - not used anywhere --> should replace "Notes" in Antibody Table RPPA
Corresponding Author - not used anywhere --> Should be in Publication according to RFC Publication
Corresponding Author ORCID - not used anywhere --> Should be in Publication according to RFC Publication
Other Data Type Specified - not used anywhere - "Other Data Type" in RFC Publication
scATAC-seq Object ID - not used anywhere
nCount peaks - used in scATAC-seq Level 3 (nCount Peaks)
nFeature peaks - used in scATAC-seq Level 3 (nFeature Peaks)
MS Analyte Type - not used anywhere --> should replace "Analyte Type" in Mass Spec Level 1
MS Instrument Vendor and Model - not used anywhere --> should replace "Instrument Vendor and Model" in Mass Spec Level 1
MS Instrument Metadata File - not used anywhere - in RFC Mass Spec

@elv-sb thanks for looking into these. Let's discuss in our sprint close-out next week...I'm curious how some of these are happening. Anyway, I expect that efforts to tidy this will spill into our next sprint

@adamjtaylor could you please take a look at the ones below? I recommend removing them from the model

[ ]  Workflow Type - not used anywhere --> Required TRUE
[ ]  Workflow Parameters Description - not used anywhere --> Required TRUE
[ ]  Antigen Retrieval - not used anywhere - was removed from RFC Biospecimen Tier 2 --> Required FALSE
[ ]  Biospecimen Slide Location - not used anywhere - was removed from RFC Biospecimen Tier 1 --> Required FALSE
[ ]  Staining markers - not used anywhere - was removed from RFC Imaging Level 1 - v1 --> Required FALSE
[ ]  Age at Index - not used anywhere --> Required FALSE
[ ]  Anatomic Site - not used anywhere --> Required FALSE

@elv-sb happy for all of those to be removed from the model.


Configure test command is not registered when the extension activates

Repro:

Reload window
Run Python: Configure Tests

@Tyriar do you remember what your setup looked like when you got this notification? Was the python extension activated yet? Had you ever run / configured tests in this workspace before?

@eleanorjboyd I'm pretty sure it was happening because the python extension wasn't activated, meaning python.configureTests was not working properly as an activation event.

To follow up on this, would the desired outcome just be for the action to not show in the command palette until the extension has activated?

Because we have not heard back with the information we requested, we are closing this issue for now. If you are able to provide the info later on, then we will be happy to re-open this issue to pick up where we left off.

The user should never be able to see a message about a command missing. I think the right thing here is that all commands should be registered upon activation, otherwise there's a chance of this happening.

We register the command on activation. We do it as early as possible. So, without a consistent repro, this is hard to say where this problem is.

closing as we cannot get a consistent repro, please reopen if this changes. Thanks!

My guess is this happens because you activate the commands after you have awaited at least once in the activate command:
https://github.com/microsoft/vscode-python/blob/db6e15e2214629fb2c09b8bf82c39ab53ebd7c30/src/client/activation/activationManager.ts#L100
If so, the fix would be either:

Ensure command await an extension in vscode core (if this doesn't happen there is probably a good reason for it)
Move command registration before the first await in the activate code


Blaze client config should have a maximum number of waiters

If your connection pool is too small, and you burst too many requests, you get an indefinitely sized queue of waiters.

I believed this was by design. What do you want to occur at this limit? Internally we are not using Task Context so we'd lose referential transparency except to the caller.

I think tasks should fail here, as a sort of circuit breaker.  The alternative, if you're making requests far faster than you can provide connections to them, is unbounded growth in the wait queue.

We have this now.


Automaticly parse links in comment fields

RegExp to build href links for URI's in the comment field. (e.g Datasheet, ...)

Good idea :)


Initial encryption support

closes #31
Adds encryption with aes from golang stdlib, only enabled if encryption key is given. Actually all 3 backup providers supported.
TODO: tests

Why not placing encryption generic in backup.go after compression, before uploading?

good point, wait a second

unsure if we should use a cli which is available on linux instead of our homegrown implementation. At least we should implement a possibility into this application to decrypt downloaded backups locally, for debugging and testing purpose.
WDYT ?

Maybe a "no database" mode, where the files get downloaded, decrypted, and decompressed?

Yes, added a --download-only flag to the restore command.

Another option would be to implement support for SSE-C, or SSE-S3 as described https://docs.aws.amazon.com/AmazonS3/latest/dev/ServerSideEncryptionCustomerKeys.html
Ceph RGW does support this as well: https://docs.ceph.com/en/latest/radosgw/encryption/#customer-provided-keys

implemented with #97


Speed up link validation a bit to make this tool more effective.

Needs to be tested on Github Actions to check if this is now viable to run on each commit.
With time I get this result:
bundle exec rake validate:ping  7,40s user 11,03s system 38% cpu 48,337 total
Much quicker... only compromise is a 10 second timeout instead of default 30.
This is the output on my run.
404 for https://machinelearning.apple.com/feed.xml
404 for https://arielelkin.github.io/feed
404 for<EMAIL_ADDRESS>404 for<EMAIL_ADDRESS>404 for https://colindrake.me/post/
404 for https://colindrake.me/post/index.xml
404 for https://appmakers.dev/category/ios/
404 for https://appmakers.dev/category/ios/feed/
Socket Error for https://www.davenott.co.uk/
Socket Error for https://www.davenott.co.uk/feed/
404 for http://danielemargutti.com/atom.xml
SSL Error for https://microblog.dave256apps.com/feed.xml
SSL Error for https://microblog.dave256apps.com/
Socket Error for http://ausios.com/feed/
Socket Error for http://ausios.com
403 for http://ennioma.com/
403 for http://ennioma.com/rss
404 for https://rss.app/feeds/tPWkcHnpdDcjdOtB.xml
404 for http://etolstoy.com/feed.xml
SSL Error for https://getonthestore.com/feed/
SSL Error for https://getonthestore.com/
Timeout for https://blog.alltheflow.com
Timeout for https://blog.alltheflow.com/rss/
429 for https://www.ioscreator.com/tutorials?format=RSS
404 for http://jamesdempsey.net/feed/
SSL Error for http://jamesonquave.com/blog/
SSL Error for http://jamesonquave.com/blog/feed/
Timeout for http://bitsplitting.org
Timeout for http://bitsplitting.org/feed/
Errno::ECONNREFUSED Failed to open TCP connection to kayathomas.info:443 (Connection refused - connect(2) for "kayathomas.info" port 443) for https://kayathomas.info/feed/
Errno::ECONNREFUSED Failed to open TCP connection to kayathomas.info:443 (Connection refused - connect(2) for "kayathomas.info" port 443) for https://kayathomas.info
404 for https://www.latenightswift.com/feed.xml
404 for https://jsorge.net/rss/
404 for https://paraside.in/tags/swift/
404 for https://paraside.in/feed.rss
404 for https://mar.codes/feed
404 for http://www.marisibrothers.com/feeds/posts/default
404 for https://marcosantadev.com/rss
404 for https://marcosantadev.com/tag/ios/
Socket Error for https://glenngonda.com/blog
404 for https://medium.com/feed/@mobilefactory
404 for http://moraleda.info/atom.xml
404 for https://medium.com/@mobilefactory/
404 for https://www.morningswiftui.com/blog?format=RSS
404 for https://netsplit.com/feed/
404 for https://www.oliverbinns.co.uk/index.php/blog
404 for https://152percent.com/blog
404 for https://152percent.com/blog?format=RSS
404 for https://onmyway133.github.io/atom.xml
404 for https://www.pointfree.co/blog/feed/atom.xml
404 for https://www.pointfree.co/blog
Timeout for http://indiestack.com
Timeout for http://indiestack.com/feed/
Errno::ENETUNREACH Failed to open TCP connection to blog.mengto.com:80 (Network is unreachable - connect(2) for "blog.mengto.com" port 80) for http://blog.mengto.com
Errno::ENETUNREACH Failed to open TCP connection to blog.mengto.com:80 (Network is unreachable - connect(2) for "blog.mengto.com" port 80) for http://blog.mengto.com/feed/
Net::ReadTimeout Net::ReadTimeout for https://andrewking.ca/category/ios-development/feed/rss
Net::ReadTimeout Net::ReadTimeout for https://andrewking.ca/category/ios-development
Socket Error for http://www.russbishop.net
400 for https://pewpewthespells.com/
Timeout for https://crsantos.info/rss.xml
Timeout for https://crsantos.info
404 for http://sealedabstract.com/feed/
404 for https://ruiper.es/rss/
Errno::ENETUNREACH Failed to open TCP connection to www.natashatherobot.com:443 (Network is unreachable - connect(2) for "www.natashatherobot.com" port 443) for https://www.natashatherobot.com
Errno::ENETUNREACH Failed to open TCP connection to www.natashatherobot.com:443 (Network is unreachable - connect(2) for "www.natashatherobot.com" port 443) for https://www.natashatherobot.com/feed/
Socket Error for https://swiftdevjournal.com/
404 for https://swifting.io/feed/
429 for https://swiftramen.com/home?format=rss
SSL Error for https://swiftier.co
404 for https://tanaschita.com/feed.rss
SSL Error for https://swiftier.co/feed
404 for https://www.tanin.dev/tags/ios
404 for https://tanin.dev/tags/ios/index.xml
404 for https://whackylabs.com/feed.xml
Timeout for https://mobileinvader.com
Timeout for https://mobileinvader.com/feed/
429 for https://yonaskolb.com/
429 for http://www.elischiff.com/
404 for https://www.scotthurff.com/rss/
404 for https://appmanager.io/blog
404 for https://blog.adapty.io/feed
404 for http://bohemiancoders.tumblr.com/
404 for http://bohemiancoders.tumblr.com/rss
404 for https://badootech.badoo.com/feed/tagged/ios
429 for https://heyimakeapps.com/blog/
Timeout for https://parveenkaler.com/blog
Timeout for https://parveenkaler.com/feed
Net::ReadTimeout Net::ReadTimeout for https://icalvin.dev/
Net::ReadTimeout Net::ReadTimeout for https://icalvin.dev/posts/json
SSL Error for https://blog.quicktype.io/
404 for https://realm.io/feed.xml
SSL Error for https://blog.quicktype.io/rss/
HTTParty::RedirectionTooDeep HTTP redirects too deep for https://peripheryapp.com/blog/
HTTParty::RedirectionTooDeep HTTP redirects too deep for https://www.peripheryapp.com/blog/feed.xml
500 for https://blog.lemi.travel/category/technology/ios/feed/
404 for https://sudo.isl.co/atom.xml
404 for https://sudo.isl.co/
Socket Error for https://cmdswift.com/
404 for https://blog.zeplin.io/feed
Socket Error for http://sharedinstance.com
Timeout for http://stuartkhall.com/
SSL Error for https://waitingforreview.com/
404 for https://medium.com/feed/whoknows-swift
404 for https://medium.com/whoknows-swift
405 for https://sungdoo.dev
404 for http://www.alexruperez.com/entries

If I may chime in... this sort of validation is a bit tricky. I used to have this on iOSFeeds.com but disabled it, because it had a lot of false positives and I would end up excluding a few blogs due to temporary issues.

Agreed, this check is purely to trigger a follow-up. The number of 40x codes is interesting.

Yes, I had forgotten this tool was there, actually! It's been a long time since I used it.
My method for finding dead feeds is to manually check their history with my feed aggregator, Inoreader. For any feed that's showing a redirect or any kind of error, I go and click into the history and get something like this:

If it's been 404ing for a while, I go through a set of steps like checking if the domain is still active, if there's an RSS meta tag and if it's pointing at a new file (I wish people would set up redirects! 🙏) and various other things to see if I can find the new feed and update the metadata accordingly.
Of course, this takes a very long time to do for 800+ feeds. Subsequently, I put off doing it 😂
It's definitely due for a check though. I'll bump it up in my priorities.

It's currently showing more than 90 as completely dead, so definitely time for me to do a thorough check:

.

Feedly reports 46 broken sources.

Feedly reports 46 broken sources.

Across all of the OPML files, or a subset?

All of the OPML.

That's very strange. Inoreader doesn't usually give false positives for errors.
I'll look into doing the full check as soon as I have time.
I think I'll merge this PR as even though this tool is not ideal, this is an improvement to it. 👍 Thanks again for putting it together


React package

I wrote some documentation for the package:
Lucide React
Use the lucide icon library in you react app.
Installation
yarn add lucide-react

# or

npm install lucide-react

How to use
It's build with ESmodules so it's completely threeshakable.
Each icon can be imported as an react component.
Example
You can pass additional props to adjust the icon.
import { Camera } from 'lucide-react';
// Returns ReactComponent

// Usage
const App = () => {
  return <Camera color="red" size={48}/>
};

export default App;

Props

name
type
default

size
Number
24

color
String
currentColor

strokeWidth
Number
2

Custom props
You can also pass custom props that will be added in the svg as attributes.
// Usage
const App = () => {
  return <Camera fill="red"/>
};

One generic icon component
It is possible to create one generic icon component to load icons.

:warning: Example below importing all EsModules, caution  using this example, not recommended when you using bundlers.

Icon Component Example
import * as icons from 'lucide-react';

const Icon = ({name, color, size}) => {
  const LucideIcon = icons[name];

  return <LucideIcon color={color} size={size} />
};

export default Icon;


Paper Recruitment Pre Process Function

Looks good! Waiting for Celeste's feedback.

@celestemartinez can I merge this one?


Make Vim command for inserting and updating discussion links

Given content in the header of a Markdown document like:

---
title: Betting on the wrong horse
tags: 1password lastpass
fb: https://www.facebook.com/glh/posts/10153077211406307
hn: https://news.ycombinator.com/item?id=10718146
reddit: https://www.reddit.com/r/programming/comments/3we95k/betting_on_the_wrong_horse/
twitter: https://twitter.com/wincent/status/675356737134694400

---

Produce or update the markup down the bottom of the document:
Discuss: [Facebook](https://www.facebook.com/glh/posts/10153077211406307) - [Hacker News](https://news.ycombinator.com/item?id=10718146) - [Reddit](https://www.reddit.com/r/programming/comments/3we95k/betting_on_the_wrong_horse/) - [Twitter](https://twitter.com/wincent/status/675356737134694400)

Almost three years since I posted this issue, and I haven't really felt the absence of this feature at all, so I am going to close it.


extend create-user functionality

The create-user command works good so far.
The file mechanism is also nice to use.
But we need to set more options for an initial user then possible with the current version.
Because right now the new user has no permissions, where as the initial user should be the administrator of the organization.
Also login wasn't possible because is_active was not set.
So I tested around with curl. The following shows the fields needed to create a user with admin permissions for the orga + default committee + default meeting (using the committee, meeting and group id's defined in backend/initial-data.json)
curl localhost:9002/internal/handle_request \
  -X POST -H "Content-Type: application/json" -d '
    {
      "action": "user.create",
      "data": [
        {
          "username": "adrian",
          "default_password": "asdf",
          "first_name": "Adrian",
          "last_name": "Richter",
          "email"<EMAIL_ADDRESS>          "is_active": true,
          "organization_management_level": "can_manage_organization", /* orga permissions */
          "committee_$_management_level": { "1": "can_manage" }, /* committee permissions */
          "group_$_ids": { "1": [ 1, 2 ] } /* participant (1) and admin (2) groups for default meeting (1) */
        }
      ]
    }
  '

Though I am not sure how these should be passed.
Obviously the yaml file could look like this:
username: adrian
default_password: notweak
first_name: Adrian
last_name: Richter
email<EMAIL_ADDRESS>is_active: true,
organization_management_level: can_manage_organization,
committee_$_management_level: { "1": "can_manage" },
group_$_ids: { "1": [ 1, 2 ] }

This would assume that every value is interpreted as raw json.
A downfall is, that this is not intuitively readable.
Another option i had in mind is just having a flag create-user --admin which will insert the permission related fields. But this will break when the initial configuration gets changed.
So I think having it explicitly all in the file would be our best bet.
Open for other suggestions though @normanjaeckel and maybe @gsiv

Should be done. Please reopen, if not.


Report an error for inserting more values than table columns

Closes #62 .
Fixes to report an error TooManyValues if inserting more values than target columns of the specified table.

@silathdiir Oh, I just found I missed a feedback I had to leave.
https://github.com/gluesql/gluesql/commit/4c8d18d5b67bd6b982631a7ba1da5bca35e1881c
if values.len() > column_defs.len() {
...

This statement can be simply checked outside of iteration, I added a quick fix using the commit I mentioned above.

Hi @panarch , thanks. I will try to test if it works.
I doubted that outside values has another mean (so I added the test case as below in this PR).
INSERT INTO TableA VALUES (100), (100, 200);

outside values = (100), (100, 200)
inside values 1 = (100)
inside values 2 = (100, 200)
I could not confirm that. Will test again. Thanks.

@silathdiir  Oh!!! While I was stuck at other hard issue, I too rushed on this one.

Thanks so so much for the fast response.
I think it wasn't a good idea I set two different variable names using a same values.
I used same values for Vec of Vec and Vec, I was entirely confused of this at this point.
Your work is correct, I'll revert the commit I mentioned.

@silathdiir FYI. I did some supplementary work related to the mistake I made.
https://github.com/gluesql/gluesql/pull/90

Flatten nested value iteration
Remove reachable Unreachable error


Add a  new Renderer

hi ,
how to add a new renderer like violin plot or different types of plots which plotly supports .
Where I have to go and make the change ?
Thanks.

You'd have to make a pull request to the React component behind this Dash component, which lives here:
https://github.com/plotly/react-pivottable
For more on Dash's React-based component system:
https://dash.plotly.com/react-for-python-developers


added tag for subsort flattening in smt

@daejunpark please review

@andreistefanescu Could you please write a simple usage of this new tag?

lgtm


Empty environment variables passed to vscode are unset

This is a continuation of #174330 which is now locked and doesn't accept comments.
The original report was filed by our Go extension users who observed empty env vars were
not reflected when they run/debug tests using the extension's feature.
The issue was closed with #175682, which fixed env handling in the term env.
However, the Go extension features (run/debug tests) actually use extension host's process.env directly. So, the term environment fix doesn't help the original issue users are facing. (https://github.com/golang/vscode-go/issues/2745)
I prepared a repro in https://github.com/microsoft/vscode-extension-samples/compare/main...hyangah:vscode-extension-samples:main#diff-665767c0f91ad3e1e028cc5dd145783e8ecaef232aefdb222ba9590b6bd52ba1
Either use the launch config in the commit, or

cd getting-started-sample
vsce package
code-insiders --install-extension=getting-started-sample-0.0.1.vsix
EMPTY_VAR="" NONEMPTY_VAR="nonempty" code-insiders
Select "Getting Started Sample: Say Hello" from command palette. Check the console log, using "Developer: Toggle Developer Tools".

code-insiders (Version: 1.79.0-insider (Universal) Commit: 9084e081d4e89ed8ab67fce340d573c4e1378939) gives me

You can see that EMPTY_VAR is undefined.
Is there a recommended way for extensions to get the process environment other than process.env?
Does the node debugger avoid this issue in https://github.com/microsoft/vscode/issues/174330#issuecomment-1431541396 because the debugger/debugee is launched from a terminal?

Out of curiosity, are there any estimates on when this might be worked on? I would really like to move to a VSCode version newer than 1.73.1, but I can't do that while this issue is still outstanding. I'd be happy to try to look into the issue to see if I can fix it if that would be helpful. I'm not completely sure where process.env is being overwritten though since I did some testing and both node by itself and standard electron treat EMPTY_VAR="" as an empty string and not as undefined, so something somewhere in vscode is overwriting that.

@fedorareis it's currently on the backlog which means it doesn't have any estimated time. If you want to give it a shot here is where I'd start looking into it:
Environment code in CLI:
https://github.com/microsoft/vscode/blob/2d9cc42045edf3458acbddf3d645bba993f82696/src/vs/code/node/cli.ts#L182-L185
Where we resolve "development environment" on Linux and macOS when launched via the dock:
https://github.com/microsoft/vscode/blob/2d9cc42045edf3458acbddf3d645bba993f82696/src/vs/platform/shell/node/shellEnv.ts#L123
Starting the extension host:
https://github.com/microsoft/vscode/blob/2d9cc42045edf3458acbddf3d645bba993f82696/src/vs/platform/extensions/electron-main/extensionHostStarter.ts#L89-L98
Note also that changing process.env isn't considered public API which means it can have problems. There is this issue which is related to setting the environment on the extension host via EnvironmentVariableCollection: https://github.com/microsoft/vscode/issues/152806

I think this bug is in Electron or Chromium.
The release notes of 1.74 say that progress was made toward sandboxing VS Code, including the introduction of a new UtilityProcess API to support these changes. Since 1.73.1 is the last version where the bug doesn't exist, I think it was introduced by this change.
To confirm that the utility process fork is the thing removing the environment variable, we can log process.env at the place where the Extension Host is spawned and the entry point of the Extension Host itself:

Add "__A_EMPTY_VAR": "" and "__A_NONEMPTY_VAR": "" to the environment of the Launch VS Code Internal task:

https://github.com/microsoft/vscode/blob/3cd6f481266dcbd2ca2fcff43b4465d747c78e2f/.vscode/launch.json#L234-L237

Set a conditional breakpoint at line 237 with condition configuration.env to check the environment variables when the Extension Host gets spawned:

https://github.com/microsoft/vscode/blob/3cd6f481266dcbd2ca2fcff43b4465d747c78e2f/src/vs/platform/utilityProcess/electron-main/utilityProcess.ts#L236-L244

Add a console.log(process.env); somewhere at the top of bootstrap-fork.js to log the environment variables at the entry point of the Extension Host:

https://github.com/microsoft/vscode/blob/3cd6f481266dcbd2ca2fcff43b4465d747c78e2f/src/bootstrap-fork.js#L1-L9

Launch the VS Code task.

At the breakpoint, check the env variable. Confirm that __A_EMPTY_VAR and __A_NONEMPTY_VAR are both present with the values we put in.

Continue.

Switch to the Debug Console and the "Attach to Extension Host" task. Expand the Object that got logged and confirm that __A_EMPTY_VAR has disappeared, but __A_NONEMPTY_VAR is still there.

Hey folks, I found it, it's in Chromium.
I found a clue by accident:

Which led me to the cause of it all:

If you build Electron with this code in that for loop before the if statement, you can confirm that it's unsetting the variable when it launches the process:
if (i.first == "EMPTY_VAR") {
  LOG(INFO) << "It's unsetting the empty variable";
}

Dobby has found the cause of the bug. Dobby is free.

@deepak1556 this might be because of Chromium/Electron swallowing empty variables?

@NoelTautges findings are on point, thanks! but this is not a bug in chromium, the launch API was not intended for external use cases and their behavior cannot be changed in upstream. However we can tweak the behavior for utility process in Electron.

+1, just to add an additional datapoint, encountered the same behaviour with vscode-python extension as well. see https://github.com/microsoft/vscode-python/issues/22337


Add chunk type to html repr in Dask array

cc @pentschev

Woohoo! That looks nice! :)
IMO, good to merge.

Thanks for the review @pentschev


Distributor ID:	Ubuntu
Description:	Ubuntu 20.04 LTS
Release:	20.04
Codename:	focal

build output
using the latest commit
DOCKER_BUILDKIT=1  docker build -t ort .
=> ERROR [stage-1 6/6] RUN tar xf /opt/ort.tar -C /opt/ort --strip-comp  95.8s
------
 > [stage-1 6/6] RUN tar xf /opt/ort.tar -C /opt/ort --strip-components 1 &&     rm /opt/ort.tar &&     /opt/ort/bin/ort requirements:
#18 2.432 WARNING: An illegal reflective access operation has occurred
#18 2.432 WARNING: Illegal reflective access by retrofit2.Platform (file:/opt/ort/lib/retrofit-2.9.0.jar) to constructor java.lang.invoke.MethodHandles$Lookup(java.lang.Class,int)
#18 2.432 WARNING: Please consider reporting this to the maintainers of retrofit2.Platform
#18 2.432 WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
#18 2.432 WARNING: All illegal access operations will be denied in a future release
#18 2.856 ________ _____________________
#18 2.856 \_____  \\______   \__    ___/ the OSS Review Toolkit, version 0.1.0-SNAPSHOT.
#18 2.856  /   |   \|       _/ |    |    Running 'requirements' under Java 11.0.8 on Linux with
#18 2.856 /    |    \    |   \ |    |    ORT_CONFIG_DIR = /root/.ort/config
#18 2.856 \_______  /____|_  / |____|    ORT_DATA_DIR = /root/.ort
#18 2.856         \/       \/
#18 2.856 More environment variables:
#18 2.856 http_proxy = http://proxy.vmware.com:3128
#18 2.856 https_proxy = http://proxy.vmware.com:3128
#18 2.856 JAVA_HOME = /opt/java/openjdk
#18 2.856 ANDROID_HOME = /opt/android-sdk
#18 2.856 GOPATH = /go
#18 2.856
#18 3.245 Scanners:
#18 3.251 	- Askalono: Requires 'askalono' in version =0.4.3. Tool not found.
#18 3.252 	- BoyterLc: Requires 'lc' in version =1.3.1. Tool not found.
#18 3.252 	- Licensee: Requires 'licensee' in version =9.13.0. Tool not found.
#18 4.933 	* ScanCode: Requires 'scancode' in version =3.2.1-rc2. Found version 3.2.1-rc2.
#18 4.933
#18 4.933 PackageManagers:
#18 4.934 	- Bower: Requires 'bower' in version =1.8.8. Tool not found.
#18 5.169 	* Bundler: Requires 'bundle' in version >=1.16.0 <2.2.0. Found version 1.16.1.
#18 5.191 	* Cargo: Requires 'cargo' in no specific version. Found version 1.43.0.
#18 5.880 	* Conan: Requires 'conan' in version =1.18.0. Found version 1.18.0.
#18 5.887 	* GoDep: Requires 'dep' in no specific version. Found version 0.5.4.
#18 5.894 	* GoMod: Requires 'go' in no specific version. Found version 1.13.4.
#18 6.107 	* Npm: Requires 'npm' in version >=5.7.0 <6.15.0. Found version 6.14.8.
#18 6.258 	* PhpComposer: Requires 'composer' in version >=1.5.0. Found version 1.6.3.
#18 7.080 	* Pip: Requires 'pip' in no specific version. Found version 9.0.1.
#18 7.472 	* Pipenv: Requires 'pipenv' in version >=2018.10.9. Found version 2018.11.26.
#18 7.587 	* Pub: Requires 'pub' in version >=2.2.0. Found version 2.7.2.
#18 94.72 	* Sbt: Requires 'sbt' in version >=0.13.0. Found version 1.3.8.
#18 94.73 	* Stack: Requires 'stack' in version >=2.1.1. Found version 2.1.3.
#18 94.73 	- Yarn: Requires 'yarn' in version >=1.3.0 <1.23.0. Tool not found.
#18 94.73
#18 94.73 VersionControlSystems:
#18 94.74 	* Cvs: Requires 'cvs' in no specific version. Found version 1.12.13.
#18 94.75 	* Git: Requires 'git' in no specific version. Found version 2.17.1.
#18 94.92 	* GitRepo: Requires 'repo' in no specific version. Found version 2.8 (launcher).
#18 95.00 	* Mercurial: Requires 'hg' in no specific version. Found version 4.5.3.
#18 95.00
#18 95.00 Other tools:
#18 95.00 	* PythonVersion: Requires 'python3' in no specific version. Found version 3.6.9.
#18 95.05 	* VirtualEnv: Requires 'virtualenv' in version >=15.1.0 <20.1.0. Found version 15.1.0.
#18 95.05
#18 95.05 Prefix legend:
#18 95.05 	- The tool was not found in the PATH environment.
#18 95.05 	+ The tool was found in the PATH environment, but not in the required version.
#18 95.05 	* The tool was found in the PATH environment in the required version.
#18 95.05
#18 95.05 Not all tools were found in their required versions.
------
failed to solve with frontend dockerfile.v0: failed to solve with frontend gateway.v0: rpc error: code =
Unknown desc = failed to build LLB: executor failed running [/bin/sh -c tar xf /opt/ort.tar -C /opt/ort --strip-components 1 &&
   rm /opt/ort.tar &&     /opt/ort/bin/ort requirements]: runc did not terminate successfully
*[master][~/ort]$
*[master][~/ort]$

possible solution
During my investigation, the last command /opt/ort/bin/ort requirements will detect related environment setup. However in my test, this command will return non-zero exit code, so the docker daemon will assume this build as a failure.
From my understanding, does this above non-zero exit code means that ort may not work properly? And if the answer is yes, what may possibly cause this issue?
By the way, I did some more research. It appears the base image adoptopenjdk:11-jre-hotspot-bionic was Ubuntu 20:04 yesterday, and today it's Ubuntu 18:04, they correct the issue shortly.  So maybe it's related to upstream image? Maybe Canonical has changed something in package index?
Any insights on this issue would be extremely helpful. Thanks in advance!

From my understanding, does this above non-zero exit code means that ort may not work properly?

Yes.

And if the answer is yes, what may possibly cause this issue?

Some required external CLI tools failed to get installed.

So maybe it's related to upstream image?

Again, yes. The upstream AdoptOpenJdk Docker image was temporarily broken, but it should be fixed by now.

hi @sschuberth , many thanks for you real quick answer on this!
Seems previously I was in a bad luck for the upstream problem.
As you mentioned above, AdoptOpenJdk was broken for a while and it should be okay now. But I still get the same issue - /opt/ort/bin/ort requirements quits with non-zero exit code. I've prune all my images and I'm sure the adoptopenjdk:11-jre-hotspot-bionic was 18.04.
From my testing, some other  tools, such as Askalono, BoyterLc don't even exists in Dockerfile - maybe we need to add download and add these packages?

From the "Scanners" section only ScanCode is really required, and ort requirements would only fail if ScanCode is not present. But for all other tools you should see the * marker which denotes the tool was found in the required version in the Docker image.

Many thanks for your tips! It turns out it was my mistake that had cause yarn and bower failed to install.
I think I can close this issue now.