beforePersist event payload (recording) is missing queryString values.

Description
beforePersist event payload (recording) is missing queryString values.
This is potentially a security issue.
I am relying on the recording payload to sanitize it from secrets, before storing the recordings. But a secret (API key) had leaked out in the query string in the CI environment.
Shareable Source
// Avoid posting hundreds of lines of source code.
// Edit to just the relevant portions.

Error Message & Stack Trace
N/A
Config
Polly.register(NodeHttpAdapter)
Polly.register(FSPersister)

Dump recording payload values:
  polly.server
    .any()
    .on('beforePersist', (request, recording) => {
      console.log(JSON.stringify(recording, undefined, 2))
    })

I am seeing:
"queryString": [],

Inspect the recording stored on disk:
I'm seeing:
          "queryString": [
            {
              "name": "foo",
              "value": "foobarbaz"
            }
          ],

Dependencies
Copy the @pollyjs dependencies from package.json:
{
    "@pollyjs/adapter-node-http": "5.0.0",
    "@pollyjs/core": "5.0.0",
    "@pollyjs/persister-fs": "5.0.0",
}

Relevant Links
N/A
Environment
Node.js v12.16.0
darwin 19.4.0
npm: 6.14.5

Apologies for the delay on this @moltar. I'll investigate this issue this week to see whats going on.

I am so sorry.  It was totally a bug in my code that I overlooked. I am sorry for wasting your time, @offirgolan.

No worries!


Issue with create_iso.sh: "cp: cannot stat 'kernel.elf': No such file or directory"

Description:
I encountered an issue while running the scripts/create_iso.sh. The error message:
[INFO] copying kernel.elf to iso/boot/...
cp: cannot stat 'kernel.elf': No such file or directory
also Installation Guide is giving 404 - page not found

Hi @moussacodes thank you for great information.
The issue you faced is caused because you haven't create the elf file yet by compiling the source code of Artilerry OS. All you have to do is:
1: make clean
2. make iso
when you run these commands, the make iso command will create a bootable ISO image for you by using scripts/create_iso.sh.
And thank you for the feedback, we will create the Installation guide for new comers. Thank you for your interest! I hope this solution will work for you, if you face up a issue still you can always write up here.


Allow for customized sudo env vaiables

Whether or not this is a good idea, I want to do:
halyard::allowed_env_variables:
  - DEBUG
  - PUPPET_ENV
  - PROFILE
  - SSH_AUTH_SOCK

This let's me do that
❯ halyard
Repo is unclean: /opt/halyard/repo
2018-05-15 19:50:48 Jareds-MacBook-Pro.local STARTING RUN
2018-05-15 19:50:54 Jareds-MacBook-Pro.local Notice: Compiled catalog for jareds-macbook-pro.local in environment production in 0.55 seconds
2018-05-15 19:50:55 Jareds-MacBook-Pro.local Notice: /Stage[main]/Halyard/Sudoers::Allowed_command[halyard_puppet]/File[/etc/sudoers.d/halyard_puppet]/content: content changed '{md5}8fd6def48b20bcf4bd829ac382b6dc46' to '{md5}7a6862829d4223eb8e6baf25c2f6f289'
2018-05-15 19:50:57 Jareds-MacBook-Pro.local Notice: Applied catalog in 2.74 seconds
2018-05-15 19:50:57 Jareds-MacBook-Pro.local ENDING RUN

❯ sudo cat /etc/sudoers.d/halyard_puppet
# Allows halyard user to run puppet

Cmnd_Alias HALYARD_PUPPET = /opt/halyard/repo/meta/halyard,/bin/sh -c /opt/halyard/repo/meta/halyard

Defaults!HALYARD_PUPPET secure_path = /sbin:/bin:/usr/sbin:/usr/bin
Defaults!HALYARD_PUPPET env_keep+=DEBUG
Defaults!HALYARD_PUPPET env_keep+=PUPPET_ENV
Defaults!HALYARD_PUPPET env_keep+=PROFILE
Defaults!HALYARD_PUPPET env_keep+=SSH_AUTH_SOCK

jaredledvina ALL=(root) NOPASSWD: HALYARD_PUPPET

As for the 'why?', because I have my github SSH key on my yubikey, and my remote for halyard is my fork using ssh :)

So the goal here is that when running puppet-run it'll run with your SSH agent so it can chat w/ github?

@akerl - Yep, passing through SSH_AUTH_SOCK let's haylard, git pull successfully in my configuration.


[HBASE-25092]RSGroupBalancer#assignments lost some regionPlans

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

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

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

_ Prechecks _

_ branch-2 Compile Tests _

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

+1 :green_heart:
compile
0m 26s
branch-2 passed

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

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

_ Patch Compile Tests _

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

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

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

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

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

_ Other Tests _

+1 :green_heart:
unit
3m  1s
hbase-rsgroup in the patch passed.

28m  8s

Subsystem
Report/Notes

Docker
Client=19.03.13 Server=19.03.13 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2509/1/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

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

JIRA Issue
HBASE-25092

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 7cf13f0dfbdf 4.15.0-60-generic #67-Ubuntu SMP Thu Aug 22 16:55:30 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / ee5988a983

Default Java
2020-01-14

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

Max. process+thread count
3876 (vs. ulimit of 12500)

modules
C: hbase-rsgroup U: hbase-rsgroup

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

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

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

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

_ Prechecks _

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
3m 53s
branch-2 passed

+1 :green_heart:
compile
0m 23s
branch-2 passed

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

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

_ Patch Compile Tests _

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

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

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

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

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

_ Other Tests _

+1 :green_heart:
unit
4m 44s
hbase-rsgroup in the patch passed.

28m 51s

Subsystem
Report/Notes

Docker
Client=19.03.13 Server=19.03.13 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2509/1/artifact/yetus-jdk8-hadoop2-check/output/Dockerfile

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

JIRA Issue
HBASE-25092

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux c14e17b7bb36 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / ee5988a983

Default Java
1.8.0_232

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

Max. process+thread count
2270 (vs. ulimit of 12500)

modules
C: hbase-rsgroup U: hbase-rsgroup

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

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

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

_ Prechecks _

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

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

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

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
3m 46s
branch-2 passed

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

+1 :green_heart:
spotbugs
0m 46s
branch-2 passed

_ Patch Compile Tests _

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

-0 :warning:
checkstyle
0m 12s
hbase-rsgroup: The patch generated 1 new + 0 unchanged - 0 fixed = 1 total (was 0)

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

+1 :green_heart:
hadoopcheck
11m 39s
Patch does not cause any errors with Hadoop 3.1.2 3.2.1.

+1 :green_heart:
spotbugs
0m 53s
the patch passed

_ Other Tests _

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

29m 12s

Subsystem
Report/Notes

Docker
Client=19.03.13 Server=19.03.13 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2509/1/artifact/yetus-general-check/output/Dockerfile

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

JIRA Issue
HBASE-25092

Optional Tests
dupname asflicense spotbugs hadoopcheck hbaseanti checkstyle

uname
Linux 9c764ef2b3e1 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / ee5988a983

checkstyle
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2509/1/artifact/yetus-general-check/output/diff-checkstyle-hbase-rsgroup.txt

Max. process+thread count
94 (vs. ulimit of 12500)

modules
C: hbase-rsgroup U: hbase-rsgroup

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

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f) spotbugs=3.1.12

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

This message was automatically generated.


The problem on Go To Definition with special words (Given When And Then)

The "Go To Definition" feature does not support the statements with "Given", "When", "And" and "Then" keyword. For example,
Verify leave all input to blank
    Given admin want to create a product
    When admin leave all input to blank
    And admin click save button
    Then warning message will be displayed

However, when removing these special keywords from the statements, The Go To Definition works fine.

Thank you for filing an issue. Test cases written in behavior-driven style (Given-When-Then) are not yet supported, but it's something that shouldn't be too hard to implement.

Is Given-When-Then on the roadmap for upcoming releases

I just installed this extension. It seems great except I cannot use without the Gherkin support. Would really be the icing on the cake.

Just wondering on creating a PR for something like this? It looks like if we attempted to match the keyword ignoring a list of given cucumber keywords it might do the job?

I haven't personally been using the behavior-driven style, so this hasn't been on the top of my list.  I'm just thinking if the Given-When-Then etc. should always be parsed as special labels or if this is something that should be configurable..?

I'm also interested in using this VSCode extension but the lack of Gherkin support is a blocker. I wouldn't mind implementing Gherkin support myself. However I have absolutely no experience in coding VSCode extensions, so I would probably just mess up if I tried ;-)

I'm happy to announce that this feature is included the newest release 2.4.0 :)


Update decision template

#3048
Use this repo to record decisions for the upcoming JavaScript improvements. Also updated the decision template for review.

@domoscargin agree that we'd have to do some work to surface this repo given it's been so long since we've used it! I did consider a project board but given this repo already existed I thought it was worth trialling keeping a decision log here (we can always move it if it's not working - I'm happy to do the grunt work to move everything 😆).
Re: making sure we update it - it will be our collective responsibility but there are things we can do to remind ourselves eg always including a done when on cards to add to the log. It's also worth us periodically reviewing the log to note outcomes like you mentioned.


#131 Kotlin Standart Function

Added a extension fuction for filtered a list and set up direclty into the adapters. Also I've used of kotlin iterators. The avoid the boilerplate, make use of kotlin standart function, mostly apply. once that is very useful to setup property values.

@victorvicari can you resolve merge conflicts. Also, there is some UI issue in the media details page (recycler views) after your previous PR merge. Can you have a look into it?

At uploads, some items are missing... but I touched only in the items_layouts, not the recycler_view itself. This is what you are talking about it?

@victorvicari  I will create a separate issue for that.

Nice Job !


add plots for accuracy and loss over all epochs in a separate view (always visible)

IMO we should actually replace the timeline with a plot of the loss- and accuracy-curves that can be also used for filtering

good idea. would look similar to what we have in ThermalPlot.

@mstreit Just that we talking about the same thing, you mean this timeline?

we cannot keep the curves in the same location as the range on the y-axis would be too small --> plot dimension should be classic 4:3 ratio (matplotlib has a default of 8:6)

@gfrogat Can you please post a sketch or screenshot of the matplotlib?

should look somewhat like this, because that's what the ML-folks are used to


HHH-3555 : Extend the Envers query system with the ability to traverse associations

I've cherry-picked the commit from https://github.com/hibernate/hibernate-orm/pull/847 into current master, resolved numerous conflicts, and squashed a commit to fix a bug I introduced while resolving conflicts. All tests pass, but I'm not sure I resolved all the conflicts properly.
I'm sorry I missed pushing this for 5.0. If this pull request doesn't change any Envers APIs/SPIs, I would still like to do that.
@adamw, @ffeisst, could you take a look and see if it looks OK to you, and let me know if any Envers APIs/SPIs were changed (that could break an existing application)?
@ffeisst, I saw in your pull request that you were stuck on outer joins. Is there any more work that needs to be done for inner join to *-to-one associations?

Superseded by https://github.com/hibernate/hibernate-orm/pull/1258

This PR should be closed in favor of #1258


Falco unit testing

What type of proposal is this?
/kind issue
Details about the discussion
With https://github.com/falcosecurity/falco/issues/686 - we introduced the
usage of the Catch2 to write tests for existing code and start going towards a more test driven style for future features.
We also have a reference PR containing some initial tests: https://github.com/falcosecurity/falco/pull/692
We would like to discuss about contributing opportunities to test Falco features and on how to get onboard new features with this style.

Discussed in: https://github.com/falcosecurity/office-hours/blob/master/meeting-notes/2019-Jul-04.md


Udemy (Independent Publisher)

[x] I attest that the connector works and I verified by deploying and testing all the operations.
[x] I attest that I have added detailed descriptions for all operations and parameters in the swagger file.
[x] I attest that I have added response schemas to my actions, unless the response schema is dynamic.
[x] I validated the swagger file, apiDefinition.swagger.json, by running paconn validate command.
[x] If this is a certified connector, I confirm that apiProperties.json has a valid brand color and doesn't use an invalid brand color, #007ee5 or #ffffff. If this is an independent publisher connector, I confirm that I am not submitting a connector icon.

If you are an Independent Publisher, you must also attest to the following to ensure a smooth publishing process:

[x] I have named this PR after the pattern of "Connector Name (Independent Publisher)" ex: HubSpot Marketing (Independent Publisher)
[x] Within this PR markdown file, I have pasted screenshots that show: 3 unique operations (actions/triggers) working within a Flow. This can be in one flow or part of multiple flows. For each one of those flows, I have pasted in screenshots of the Flow succeeding.

[x] Within this PR markdown file, I have pasted in a screenshot from the Test operations section within the Custom Connector UI.

[x] If the connector uses OAuth, I have provided detailed steps on how to create an app in the readme.md.
Connector uses Basic Auth, not OAuth.

Hi @nanddeepn Thank you so much for submitting a connector to the Power Platform! We will review your submission within the next 2 weeks.

[[certify-connector]]

[[certify-connector]]

@nanddeepn Congratulations! The deployment of your connector and documentation page is now complete, We have a short survey on the connector certification process that we would like for you to complete. Your feedback is appreciated and will help us improve the program, Thanks.

Thank you @natalie-pienkowska, @sriyen-msft, and everyone for your guidance. 🙏


fix(core): use require implementation written in Lua

Summary
Some of the libraries that we use perform socket functions while they are being required().  This causes problems if the initial require() of the module is done from running code (instead of on the module global level) as require is implemented in C, and yielding is not possible across the boundaries of a FFI invocation.
This commit replaces the require() implementation by one that is written in Lua so that yielding is possible on the module global level.
Checklist

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

Issue reference
KAG-2595

I have a question: what is the performance of "lua require"? Is it slower or faster than "C require"?

I have a question: what is the performance of "lua require"? Is it slower or faster than "C require"?

I would expect it to be slower, but as the number of modules that we require is bounded and we don't require repeatedly in the hot path, it is better to have a robust solution that is a little slower than a fast one that can break in very obscure ways.

There is no immediate need for this at the moment. I feel we may want to discuss more about this. The ”resty.signal” LUA_CPATH parsing issue made it clear that it is quite essy to get things wrong or different compared to native. I think it is better to hold this, and not try to rush it in. Perhaps we don’t even want it. Yield across C boundary is in genaral good infication to refactor the code so that it won’t happen, in my opinion.

Yield across C boundary error is in genaral good indication to refactor the code so that it won’t happen

I generally agree that top-level module code should not require.  The issue with the "Yield across C boundary" error is that it can leave back the heap in a corrupted state from which there is no recovery, and we have seen situations where the error has not even been printed to a log file.  Given the risk that customers see segmentation violations, even during plugin development time, I think that it is better to merge this PR and see if there are any issues during testing.  If there are none, we can still write our code so that require does not perform yielding operations.
Another alternative would be to make the "Yield across C boundary" error exit the process instead of reporting it as a normal error.  This would require a patch to LuaJIT, however, and that seems to be more risky a change.

I suggest we do not do on this change. There has been 0 reports of this bug previously and it seems that we are making a rather large change to address a very remote possibility. Yes it could be bad when it does happen, but at the same time this shows people are doing weird things in the init routine where they shouldn't be doing.
Also, having require do yield is generally very weird.. It does not seems to be reasonable use case. Even if we want to fix the crash, we should consider if this should even be supported in the first place.


allow copying system files to RAM

With 16GB and more installed, /var and even /usr should easily fit into RAM.
To support this the startup scripts would just have to run really soon (initramfs even?), and the shutdown scripts really late, in the up/down sequence.

I had /var/log included in my WHATTOSYNC array and had the problem that pacman would give me the following error when updating packages that included /var/log in them (like cups or systemd): error: failed to commit transaction (conflicting files) This was due to /var/log being a symlink instead of a dir.
Maybe I did something wrong there, but as soon as I stopped asd I could update the packages all fine.  See also this thread in the Arch forums.

https://github.com/graysky2/anything-sync-daemon/issues/19

Hey, I now found USE_OVERLAYFS (mentioned above) in the wiki. :-)
If asd configures the overlayfs in the fstab, all is good, because sync/unsync happen at the right time without any additional risk of files beeing alredy open on creation or still open on shutdown.
Does it get configured in fstab?

No need for fstab modification.  Asd does it instead of symlinking if your system supports it and if you enable it.

It leaves open a time window with another fs mounted to that path.
Only if asd is started imediately after, and stoped only imediately before fstab is handled would there be no risk. Don't know if systemd can ensure that.

I just had a simple idea that could get rid of all the start/stop contingencies:
Add an option to anything-sync-daemon to only do the aditional frequent syncs for overlay filesystems that the user (or some other tool) has set up in fstab.

Thanks for the hint! I found this issue via google and didn't bother checking the other open issues in here. My bad!

I have no immediate plans to begin to think about how to implement... since systemd runs at such a low level, I think doing so will be troublesome.


Potential bug in binary_operator

From my best reading of the paper, my understanding was that a_j.real * kv_i + kv_j should be a_j * kv_i + kv_j in binary_operator, and then in the output step, you take kv.real. In a few places there is the following code:
    def binary_operator(a, b):
        a_i, kv_i = a
        a_j, kv_j = b
        return a_j * a_i, a_j.real * kv_i + kv_j

but then in other places it's just  return a_j * a_i, a_j * kv_i + kv_j. I don't think these are equivalent (but maybe i'm wrong)

@cnapun ah shoot! they aren't equivalent, just tested it
let me rerun the experiment 🤞

hmm, still not seeing it
at least the implementation is now faithful. thanks!


Optionnal type NSURL

Hi, When I tried to implement your example, I got an error saying
Value of optional type 'NSURL?' not unwrapped; did you mean to use '!' or '?'?
If I add '!' I must also add it to csv!.colums['my_column_name'] then I got csv doesn't have a member colums.
If I use ? I got NSURL not unwrapped did you mean '!' or '?'
I'm using xcode 6.1.1 and cocoapods 0.36.0.beta.2
Here is my code :
    let csvURL = NSURL(string: "test.csv")
    var error: NSErrorPointer = nil
    let csv = CSV(contentsOfURL: csvURL, error: error)
    let testValues = csv.colums["name_test"]

I suggest that you update your example to match what should be done.
I'm a little new to swift.

@mathlarocque You should use optional binding, if let csvURL = NSURL(string: "test.csv"). I will modify the sample code soon.

@mathlarocque I have modified the sample codes by ac1559971068595e6d0e161dcd0e81abffabc816.


Migrate to annotations cleanup

Merge after #3255
Removes OSGi XML files and pom Service-Component section.

[ ] have a concise title
[ ] close an accompanying issue if one exists
[ ] be against the correct branch
[ ] include migration scripts and documentation, if appropriate
[ ] pass automated tests
[ ] have a clean commit history
[ ] have proper commit messages (title and body) for all commits

Considering that #3255 isn't merged yet, and I'd only review them both together anyway, why don't you squash 'em both into one PR or the other?

I thought it would be easier to review if 300 files less were changed, and it's some kind of documentation if the XML files still exist. If you prefer, I can squash them.

Nah, I got through the first PR today, so lets just leave them separately now.

@geichelberger #3255 merged, can take a look at this tomorrow if you've got time to fix conflicts


Mesh plot does not show appropriate lines for polyhedral mesh.

I received the following email: we have discovered another bug when visualizing GMV data with VisIt (we reported the last one 2.5 years ago, which you have fixed for version 2.7). Find attached a GMV geometry file with 6x2 cells and two screenshots how it looks like in the original GMV viewer. In VisIt, it looks weird around the shaved cells (1st layer in z-direction). Do you see any way to fix that? Thanks in advance! The cause is probably polyhedral cells. Fix the mesh plot so it shows the edges that come from the original polyhedral cell edges.
-----------------------REDMINE MIGRATION-----------------------
This ticket was migrated from Redmine. As such, not all
information was able to be captured in the transition. Below is
a complete record of the original redmine ticket.
Ticket number: 2483
Status: Pending
Project: VisIt
Tracker: Bug
Priority: Normal
Subject: Mesh plot does not show appropriate lines for polyhedral mesh.
Assigned to: -
Category: -
Target version: -
Author: Brad Whitlock
Start: 12/16/2015
Due date:
% Done: 0%
Estimated time:
Created: 12/16/2015 12:25 pm
Updated: 03/29/2016 06:33 pm
Likelihood: 3 - Occasional
Severity: 2 - Minor Irritation
Found in version: 2.10.0
Impact:
Expected Use:
OS: All
Support Group: Any
Description:
I received the following email: we have discovered another bug when visualizing GMV data with VisIt (we reported the last one 2.5 years ago, which you have fixed for version 2.7). Find attached a GMV geometry file with 6x2 cells and two screenshots how it looks like in the original GMV viewer. In VisIt, it looks weird around the shaved cells (1st layer in z-direction). Do you see any way to fix that? Thanks in advance! The cause is probably polyhedral cells. Fix the mesh plot so it shows the edges that come from the original polyhedral cell edges.
Comments:

2487_Agnesi2D.out.gmvG.zip


Issue on state authorization

When a state is found to be authorized, the code that allows the state to continue and broadcasts the success message.
However, we are getting an error '$$hashKey' not defined on state change. We traced it back to angular-permission line 49. In the source, you said this is a hacky fix that should be fixed in later versions on UI-router. Could this be the culprit?
Permission.defineRole('projectmanager', function(stateParams) {
       var deferred = $q.defer();

       $http.get('/api/managers').then(function(data) {
           var isPM = false;
           for (var i = 0; i < data.data.length; i++) {
               if (data.data[i].projectMgr == $rootScope.session.projectMgr) {
                   isPM = true;
                   break;
               }
           }
           if (isPM) {
               deferred.resolve();
           } else {
               deferred.reject();
           }
       }, function() {
           deferred.reject();
       });
       return deferred.promise;
   });

I am also getting the same issue. Any workaround for the moment?
if (!$rootScope.$broadcast('$stateChangeStart', toState, toParams, fromState, fromParams).defaultPrevented) {

This error seems to have emerged out of nowhere, could it be the ui-router version?
What version are you guys using

After further investigation I found this was only an issue when using both ui-router-extras and angular-permission. Seems like both libraries are catching the "stateChangeStart" event. I'm not exactly sure who is at fault here but [ platdesign] (https://github.com/platdesign) made a fix for the ui-router-extras library. After implementing this one line fix the error went away. For those interested see this link.
Here are the versions I am currently using:

ui-router 0.2.15
ct-ui-router-extras 0.0.14
angular-permission  0.3.1

This would not be our problem as we are not using ct-ui-router-extras currently in our project.

express -> 4.1.1
express-ui0router -> 0.2.15

Not sure if it is correct but according to what was said in that link the core of the problem is with angular-permission. I'll quote here what was said:

"angular-permission is also capturing the $stateChangeStart event and it has logic that prevents further propagation of as well as (re)transmitting the $stateChangeStart event."

...

UI Router broadcast a $stateChangeStart
UI-Router-Extras capture the $stateChangeStart event. All fine.
angular permission capture the $stateChangeStart event, blocks propagation and then does a retransmit (i.e. broadcast)
UI-Router-Extras capture the $stateChangeStart event again. Code breaks.

Might be worth at least looking into.

Hi, ui-router-extras guy here.  Extras has code which keeps track of every transitionTo call, then matches that up with the $stateChangeStart event.  The problem here is that angular-permission is firing fake $stateChangeStart events, and that's causing the Extras code to bomb.
I can add some logic in Extras that will work around the problem, but these two features ($transition$ and Previous States) will be incompatible with angular-permission, as long as it relies on fake ui-router events.
Note that in 1.0 we've substantially improved the ui-router integration hooks making things like angular-permission much easier.

Will have a look at the 1.0 version, The fake state emission is the source
of many issues with angular-permission. If anyone figures out an
alternative way to do this without having to stop/re-emit stateChange
events that would help a bunch
On Fri, Oct 9, 2015 at 5:03 PM Chris Thielen<EMAIL_ADDRESS>wrote:

Hi, ui-router-extras guy here. Extras has code which keeps track of every
transitionTo call, then matches that up with the $stateChangeStart event.
The problem here is that angular-permission is firing fake
$stateChangeStart events, and that's causing the Extras code to bomb.
I can add some logic in Extras that will work around the problem, but
these two features ($transition$ and Previous States) will be incompatible
with angular-permission, as long as it relies on fake ui-router events.
Note that in 1.0 we've substantially improved the ui-router integration
hooks making things like angular-permission much easier.
—
Reply to this email directly or view it on GitHub
https://github.com/Narzerus/angular-permission/issues/81#issuecomment-146974279
.

@Narzerus 1.0 is close to an alpha release, but hasn't gotten much testing besides our own unit tests.  Would love to get some feedback on it.
you'll do something like so:
// gets permissions config from a state
let getPermissions = (state) => state.permissions || state.data && state.data.permissions

app.run(($transitions) => {
  // When a transition starts, and getPermissions returns truthy for
  // the "to" state, run the checkPermissionsHook
  $transitions.onStart({ to: getPermissions }, checkPermissionsHook);
}

// $transition$ has data about the current transition, including the "to state"
checkPermissionsHook.$inject = ['$transition$'];
function checkPermissionsHook($transition$) {
  let to = $transition$.to();
  let permissions = getPermissions(to);
  let toParams = $transition$.params();

  // do $stateChangePermissionStart eventing here
  return Permission.authorize(permissions, toParams)
    .then(() => /* do $stateChangePermissionAccepted eventing here /*)
    .catch((error) => {
      // do $stateChangePermissionDenied eventing
      if (permissions.redirectTo) {
        state = // get redirect to state
        var targetState = $state.targetState(state);
        // asynchronously returning a redirect from the hook
        return $transition$.redirect(targetState);
      }
    });
}

Is there a complete solution for ui-router-extras and angular-permission?
@christopherthielen can you help please with your previous code.

How to cancel transitions stack?
$transition$.redirect(targetState) make with $state.go ...?
$transitions.onStart is equals $rootScope.$on("$transitionStart", ...)? What does it mean in this context { to: getPermissions }
Is $previous functionality saved if i transition cancels?

@temka1234 the code I wrote is for the currently unreleased feature-1.0 branch of ui-router

Any updates on this issue? Would love to use angular-permission and ui-router-extras together.

Here simple plunker example of angular-permission with ui-router 1.0alpha http://plnkr.co/edit/AuScw1?p=preview. redirectTo option not working now, wait for this issue https://github.com/angular-ui/ui-router/issues/2450

Create "ui-router-1.0" branch, fix tests. redirectTo option now worked.
@masterspambot, can you make review?

:0 awesome!
On Sun, Feb 28, 2016, 1:43 PM Błażej Krysiak<EMAIL_ADDRESS>wrote:

@temka1234 https://github.com/temka1234 The code itself looks great,
but as long as ui-router guys don't make official release we can not rely
on this code. But! But i got idea how to make it work in 0.2.x I just need
to refactor ParmissionMap and release 2.1.0 that will solve the history
messing problem.
—
Reply to this email directly or view it on GitHub
https://github.com/Narzerus/angular-permission/issues/81#issuecomment-189900524
.


Attribute #[allow(non_camel_case_types)] for enums

My graphql scheme contains enums with capital letters values and graphql-client cli generates such code:
#[derive(Eq, PartialEq)]
pub enum PagesSortType {
    #[doc = ""]
    ID_ASC,
    #[doc = ""]
    ID_DESC,
    #[doc = ""]
    MODIFIED_AT_ASC,
    #[doc = ""]
    MODIFIED_AT_DESC,
    Other(String),
}

Rust compiler throws warnings:
warning: variant `MODIFIED_AT_DESC` should have an upper camel case name
   --> src/services/pages.rs:417:9
    |
417 |         MODIFIED_AT_DESC,
    |         ^^^^^^^^^^^^^^^^ help: convert the identifier to upper camel case: `ModifiedAtDesc`

Perhaps it’s worth adding an #[allow(non_camel_case_types)] attribute for all enums or making it possible to specify which attributes you want to add yourself via cli argument --variables-attributes for example.

Sounds like a useful improvement — let's think about how to expose this in this issue.


"New Window" opens DOM browser

Atom 1.9.3 on Macintosh, when I select "New Window" from the menu bar, hot key, or from the Dock menu, the DOM browser window opens.

This is a regression in 1.9.3.  A patch release (1.9.4) will be out shortly to address this.  Sorry for the inconvenience.


Add sharding constraint for the output tensor in the model

This will be used for sharding the intermediate state (eg activations).
Updates to the API:

keras.distribute.relayout for relayout/set sharding constraint for a tensor value.
LayoutMap are used to support layer name as the key for the output layout of the layer.

Unit test has been updated for JAX as a demonstration.

Codecov Report
All modified lines are covered by tests :white_check_mark:

Comparison is base (5536dc5) 77.58% compared to head (9025681) 72.80%.

Additional details and impacted files
@@            Coverage Diff             @@
##           master   #18536      +/-   ##
==========================================
- Coverage   77.58%   72.80%   -4.79%
==========================================
  Files         334      334
  Lines       32211    32234      +23
  Branches     6286     6290       +4
==========================================
- Hits        24992    23468    -1524
- Misses       5635     7236    +1601
+ Partials     1584     1530      -54

Flag
Coverage Δ

keras
72.74% <100.00%> (-4.75%)
:arrow_down:

keras-jax
63.32% <100.00%> (+0.02%)
:arrow_up:

keras-numpy
57.28% <52.17%> (-0.01%)
:arrow_down:

keras-tensorflow
?

keras-torch
64.03% <47.82%> (-0.02%)
:arrow_down:

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

Files
Coverage Δ

keras/backend/jax/distribution_lib.py
93.75% <100.00%> (+0.89%)
:arrow_up:

keras/distribution/distribution_lib.py
95.37% <100.00%> (+0.31%)
:arrow_up:

keras/layers/layer.py
87.28% <100.00%> (-0.96%)
:arrow_down:

... and 41 files with indirect coverage changes

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

@mattdangerw

PTAL again.


Prepare for v5.10.0

Feedback on the release info text is very much appreciated:

Thanks @nikku. i updated it!

@smbea Could we mark this PR as fixes for fixed upstream dependencies?

@smbea Could we mark this PR as fixes for fixed upstream dependencies?

Done. I added "closes #issue" for the fixed upstream issues. I think that's what you meant


Publish to GitHub workflow is failing

See, e.g. https://github.com/amazon-ion/ion-java/actions/runs/4693102316/jobs/8319648393
Error text in case the above ages out:
Run gh release upload "v$(<project.version)" "build/libs/ion-java-$(<project.version).jar"
  gh release upload "v$(<project.version)" "build/libs/ion-java-$(<project.version).jar"
  gh release upload "v$(<project.version)" "build/reports/bom.json"
  shell: /usr/bin/bash -e {0}
  env:
    GRADLE_BUILD_ACTION_SETUP_COMPLETED: true
    GRADLE_BUILD_ACTION_CACHE_RESTORED: true
    GITHUB_TOKEN: ***
HTTP 403: Resource not accessible by integration (https://uploads.github.com/repos/amazon-ion/ion-java/releases/99452171/assets?label=&name=ion-java-1.9.6.jar)
Error: Process completed with exit code 1.

Might be caused by this: https://github.blog/changelog/2023-02-02-github-actions-updating-the-default-github_token-permissions-to-read-only/

You're right! It is fixed :D
The most recent run succeeded: https://github.com/amazon-ion/ion-java/actions/runs/5616560261
Thanks @popematt for fixing this, and thanks @gliptak for noticing it.


[infra] Fix CSS deprecation warnings for HSL usage

The following deprecation warnings currently occur, we should probably fix them.
transforming (1) .svelte-kit\build\app.jsDeprecation Warning: Using / for division is deprecated and will be removed in Dart Sass 2.0.0.

Recommendation: math.div(0%, 3%)

More info and automated migrator: https://sass-lang.com/d/slash-div

   ╷
47 │         box-shadow: 0 2.74416px 2.74416px hsl(0, 0%, 0% / 3%),
   │                                                      ^^^^^^^
   ╵
    src\styles\pages\blog.scss 47:48  @use
    src\routes\blog\index.svelte 2:2  root stylesheet

Deprecation Warning: $lightness: Passing a number without unit % (0) is deprecated.

To preserve current behavior: $lightness * 1%

[...]

Yep, that's a problem with Sass's conflict between / as a division operator and a CSS separator.


There is issue while using timepicker using range and step

const TimePicker = tui.TimePicker;
timepicker1 = new TimePicker('#timepicker-spinbox1', {
inputType: 'selectbox',
showMeridiem: true,
minuteStep: 15,
});
var begin = { hour: 6, minute: 15 };
var end = { hour: 11, minute: 15 };
timepicker1.setRange(begin, end);
while selecting time from beginning, all the minutes are disabled

timepicker1.getHour() also does not show the current hour

@shyamsamtan
Thank you for raising the issue.
It seems to be a problem caused by not considering the step in the code that disable the minute.
I'll fix it ASAP.


iOS doesn't record location even if the application is running in foreground.

The first two points were logged, nothing afterwards.
Devices

iPhone11 - 13.3

I am looking into backgroundgeolocation api and what mode of collection would be best. This also ties up with #89 as well.


Formation of Pose matrix and then votes

Hi,
I would like to know
(1) the intuition behind the pose matrix, how is it formulated for each capsule based on the Relu ofmaps  ?
(2) I am trying to evaluate the CapNet expensive operations, is the reshaping after each output is necessary for the next stage?


[TypeScript SDK] Generate TypeDoc

Generated docs: http://typescript-sdk-docs.s3-website-us-east-1.amazonaws.com/
TODO:

use a custom URL instead of the s3 URL and link it on the dev portal

Hi Chris,
Sorry to get to this late. I recall you saying we should eventually link to the typescript docs from docs.sui.io. Is it time? Thanks!

@Clay-Mysten sorry for missing this comment. Yes it's time to link them from docs.sui.io

@Clay-Mysten sorry for missing this comment. Yes it's time to link them from docs.sui.io

No worries, @666lcz! May I ask for your guidance on how/where to reference this content? Also see my related comment on Tuesday's deliverable about contributions. Thanks!


BeyondHD ratio rules change

One of BHD's recruiters posted this in another tracker 2 years and 7 months ago:

We used to be a ratio free tracker but due to abuse we set a global minimum ratio of 0.1, but we are still willing to make exceptions for long term seeders.

I assume BHD is no longer a ratioless tracker but I'm not a member there so I don't know if it has any futher changes.
BeyondHD (BHD) in Private Trackers
BHD's link is dead too.

Why this was removed?
Site is not dead: https://beyond-hd.me


path/filepath: EvalSymlinks fails when target is file

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

go version devel +d459962967 Fri Dec 28 22:14:11 2018 +0000 windows/amd64

Does this issue reproduce with the latest release?
No. This bug is not present in go1.11.
What operating system and processor architecture are you using (go env)?
go env Output
set GOARCH=amd64
set GOBIN=
set GOCACHE=C:\Users\Alex\AppData\Local\go-build
set GOEXE=.exe
set GOFLAGS=
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOOS=windows
set GOPATH=c:\users\alex\dev
set GOPROXY=
set GORACE=
set GOROOT=c:\users\alex\dev\go
set GOTMPDIR=
set GOTOOLDIR=c:\users\alex\dev\go\pkg\tool\windows_amd64
set GCCGO=gccgo
set CC=gcc
set CXX=g++
set CGO_ENABLED=1
set GOMOD=
set CGO_CFLAGS=-g -O2
set CGO_CPPFLAGS=
set CGO_CXXFLAGS=-g -O2
set CGO_FFLAGS=-g -O2
set CGO_LDFLAGS=-g -O2
set PKG_CONFIG=pkg-config
set GOGCCFLAGS=-m64 -mthreads -fmessage-length=0 -fdebug-prefix-map=C:\Users\Alex\AppData\Local\Temp\go-build894807034=/tmp/go-build -gno-record-gcc-switches

What did you do?
I run this test
package main_test

import (
	"io/ioutil"
	"os"
	"os/exec"
	"path/filepath"
	"strings"
	"testing"
)

func TestNTNamespaceSymlink(t *testing.T) {
	tmpdir, err := ioutil.TempDir("", "TestNTNamespaceSymlink")
	if err != nil {
		t.Fatal(err)
	}
	defer os.RemoveAll(tmpdir)

	tmpfile := filepath.Join(tmpdir, "file")
	err = ioutil.WriteFile(tmpfile, []byte(""), 0666)
	if err != nil {
		t.Fatal(err)
	}

	vol := filepath.VolumeName(tmpdir)
	output, err := exec.Command("cmd", "/c", "mountvol", vol, "/L").CombinedOutput()
	if err != nil {
		t.Fatalf("failed to run mountvol %v /L: %v %q", vol, err, output)
	}
	target := strings.Trim(string(output), " \n\r")
	target = target + tmpfile[3:]

	link := filepath.Join(tmpdir, "link")
	output, err = exec.Command("cmd", "/c", "mklink", link, target).CombinedOutput()
	if err != nil {
		t.Fatalf("failed to run mklink %v %v: %v %q", link, target, err, output)
	}

	got, err := filepath.EvalSymlinks(link)
	if err != nil {
		t.Fatal(err)
	}
	if want := tmpfile; got != want {
		t.Errorf(`EvalSymlinks(%q): got %q, want %q`, link, got, want)
	}
}

What did you expect to see?
I expect the test to PASS.
What did you see instead?
=== RUN   TestNTNamespaceSymlink
--- FAIL: TestNTNamespaceSymlink (0.08s)
    a_test.go:41: The system cannot find the path specified.
FAIL

I can make the test pass, if I use commit before b32ee0a3c004d4ef79d92bd63200008456da50f3.
/cc @Gnouc and @ianlancetaylor
Alex

Can you make sure mklink created a valid link?

Oh, it looks like link to me. If I remove defer os.RemoveAll(tmpdir) line, then I can look around and everything:
C:\>cd %TMP%

C:\Users\Alex\AppData\Local\Temp>dir
 Volume in drive C has no label.
 Volume Serial Number is 9012-A870

 Directory of C:\Users\Alex\AppData\Local\Temp

29/12/2018  05:43 PM    <DIR>          .
29/12/2018  05:43 PM    <DIR>          ..
29/12/2018  10:16 AM    <DIR>          3548C99F-693C-4805-99DA-8F47DEEEC977
               0 File(s)              0 bytes
               3 Dir(s)  299,225,292,800 bytes free

C:\Users\Alex\AppData\Local\Temp>u:\test
--- FAIL: TestNTNamespaceSymlink (0.09s)
    a_test.go:41: The system cannot find the path specified.
FAIL

C:\Users\Alex\AppData\Local\Temp>dir TestNTNamespaceSymlink535467779
 Volume in drive C has no label.
 Volume Serial Number is 9012-A870

 Directory of C:\Users\Alex\AppData\Local\Temp\TestNTNamespaceSymlink535467779

29/12/2018  05:43 PM    <DIR>          .
29/12/2018  05:43 PM    <DIR>          ..
29/12/2018  05:43 PM                 0 file
29/12/2018  05:43 PM    <SYMLINK>      link [\\?\Volume{ea961e77-0000-0000-0000-501f00000000}\Users\Alex\AppData\Local\Temp\TestNTNamespaceSymlink535467779\file]
               2 File(s)              0 bytes
               2 Dir(s)  299,224,088,576 bytes free

C:\Users\Alex\AppData\Local\Temp>type TestNTNamespaceSymlink535467779\link

C:\Users\Alex\AppData\Local\Temp>

The error message indicate that the error is not syscall.ENOTDIR

The error message is syscall.ENOTDIR.
If you look in $GOPATH/src/syscall/zerrors_windows.go file, you will see that syscall.ENOTDIR is actually Windows ERROR_PATH_NOT_FOUND. And ERROR_PATH_NOT_FOUND error text is The system cannot find the path specified. Search for ERROR_PATH_NOT_FOUND in https://docs.microsoft.com/en-us/windows/desktop/debug/system-error-codes--0-499-
Alex

@alexbrainman I tested myself, and as I said above, the link generated is invalid. I don't have Go setup environment on Windows, so I build this file and run on VM:
package main

import (
	"io/ioutil"
	"log"
	"os/exec"
	"path/filepath"
	"strings"
)

func main() {
	tmpdir, err := ioutil.TempDir("", "TestNTNamespaceSymlink")
	if err != nil {
		log.Fatal(err)
	}
	println(tmpdir)

	tmpfile := filepath.Join(tmpdir, "file")
	err = ioutil.WriteFile(tmpfile, []byte(""), 0666)
	if err != nil {
		log.Fatal(err)
	}

	vol := filepath.VolumeName(tmpdir)
	output, err := exec.Command("cmd", "/c", "mountvol", vol, "/L").CombinedOutput()
	if err != nil {
		log.Fatalf("failed to run mountvol %v /L: %v %q", vol, err, output)
	}
	target := strings.Trim(string(output), " \n\r")
	println(tmpfile)
	target = target + tmpfile[3:]

	link := filepath.Join(tmpdir, "link")
	output, err = exec.Command("cmd", "/c", "mklink", link, target).CombinedOutput()
	if err != nil {
		log.Fatalf("failed to run mklink %v %v: %v %q", link, target, err, output)
	}

	got, err := filepath.EvalSymlinks(link)
	if err != nil {
		log.Fatal(err)
	}
	if want := tmpfile; got != want {
		log.Fatalf(`EvalSymlinks(%q): got %q, want %q`, link, got, want)
	}
}

When open explorer, double click to the link, a popup shown, said that missing shortcut.

@alexbrainman I think the best way is fixing evalSymlinksUsingGetFinalPathNameByHandle to return an error with path like C;\path\to\existing_file\. So we can remove symlinkOrDir hack.

If yes, then if we remove symlinkOrDir checking, how can we solve problem with C:\path\to\existing_file\ case?

I don't have solution at this moment. Maybe leave Windows out of your https://go-review.googlesource.com/c/go/+/155597 altogether. Maybe revert CL 155597 symlink_windows.go changes and move TestIssue29372 into non Windows test file.
I think we should just revert CL 155597 for now.
Alex

@alexbrainman I did it in CL 155997, builder failed due to timeout problem

@ianlancetaylor gentle ping

@ianlancetaylor With a path like /path/to/existing_file/, walkSymlinks will process each component of the path, first from /path, then /path/to and so on.
If any component of the part [is not symlink or directory],(https://github.com/golang/go/blob/master/src/path/filepath/symlink.go#L81) then the part is broken.
Now, on Windows, if walkSymlinks return an error, then evalSymlinksUsingGetFinalPathNameByHandle is used to check the path again. I'm not sure why we do that (I'm not familiar with Windows), but internally, evalSymlinksUsingGetFinalPathNameByHandle uses GetFinalPathNameByHandle, which somehow normalize /path/to/existing_file/ to become /path/to/existing_file, and return success.
I just check from cmd and Powershell on Windows, if you did:
C:\ ls C:\existing_dir\existing_file\

You will get path not found error.
The point is if walkSymlinks return syscall.ENOTDIR, then nothing to be done anymore. In case of other errors, using evalSymlinksUsingGetFinalPathNameByHandle as before.

@Gnouc OK, thanks.
Is there some way that we can fix 155997 so that we don't have to add more special cases for Windows?  If we need a special test for "/." (and perhaps "/..") then let's do that.

@ianlancetaylor

Is there some way that we can fix 155997 so that we don't have to add more special cases for Windows?

I don't think there's any other ways, except for checking walkSymlinks returns syscall.ENOTDIR or not.
If we don't want special cases for Windows, then just left the Windows behavior as before 155597. If we went that way, we must except that EvalSymlinks("/path/to/existing_file/") returns error on *nix, but EvalSymlinks("C:\path\to\existing_file\") success on Windows.

Can we simply check explicitly for the cases that make a difference?  Like check for a trailing slash and see whether it is a file?

Can we simply check explicitly for the cases that make a difference? Like check for a trailing slash and see whether it is a file?

Good idea. Here is my attempt https://go-review.googlesource.com/c/go/+/156398
Alex

@alexbrainman Your CL does the same thing with mine: If error from walkSymlinks is syscall.ENOTDIR, just return, other error is passed to evalSymlinksUsingGetFinalPathNameByHandle as before.
Also why named slashAfterFilePathError instead of plain syscall.ENOTDIR?
Because slashAfterFilePathError error for path like /path/to/existing_file/foo/bar looks weird.


Replace WorkQueue replication filter by selector function

Fixes #11192
Status
ready (1st commit)
Description
As the title says, stop using a JavaScript filter function in favor of a native Erlang selector function.
In addition, make it configurable in the component, in case tweaks are necessary.
Is it backward compatible (if not, which system it affects?)
YES
Related PRs
None
External dependencies / deployment changes
None

I think the current testbed rules are making the validation of this patch very hard (with wrong ingress rules), so I decided to apply it to the fresh new agent running in vocms0255 and, even though the replication managed to go through within the frontend 5min limit, I don't see any of the expected documents replicated to the agent, unfortunately!
My suspicious is that the selector field 'WMCore.WorkQueue.DataStructs.WorkQueueElement.WorkQueueElement' is actually getting expanded to a nested data structure. So, instead of matching against that specific field in a workqueue element, it is expanding it to a nested structure like:
{"WMCore":
    "WorkQueue":
        "DataStructs": ...
    }

which of course won't ever match any documents.

I finally managed to get it working and it has been deployed to vocms0255 for now (as condor pressure was really bad over the past few days). All commits have been squashed in only 1, but further work is still necessary for:

remove the workqueue filter function, if no longer needed
migrate the wmstats replication filter to selector mode as well.

After verifying vocms0255, everything seems to be fine with this patch. So I went ahead and applied it to submit11 as well.
Replication went through and the agent is already creating work for the WQEs that were pending replication since last week.

I still have to converge on the wmstats replication, but any feedback on the already implemented feature for workqueue would be appreciated.
Note that I have most of the replication logic in the component configuration. If people prefer, I can move to the previous logic, which is creating the parent/child queue logic in the component source code.

I ran a bunch of DMWM tests in vocms0261 and I can now confirm that all the 3 replications are working well (wmagent_summary and the bidirectional workqueue one).
@LinaresToine we are likely cutting a new release today, then I will ask you to also validate this new selector function for the agent (I think it is the tier0_request replication).


next/server Build Issue

Creating this issue to follow up on a post made in Discord.
Hi, I'm running into an issue during my builds using Nextjs on Pages. This seems rather strange since the example on the next-on-pages repo shows next/server being used in middleware. Thanks for any pointers/suggestions!
My next.config.js is of course configured to include experimental: {runtime: "experimental-edge",} And I've included the log and my middleware below.
Logs:

16:23:50.927	▲ Build Completed in .vercel/output [31s]
16:23:50.927	▲
16:23:51.080	⚡
16:23:51.081	⚡
16:23:51.081	⚡ Completed 'npx vercel build'.
16:23:51.081	⚡
16:23:51.429	✘ [ERROR] Could not resolve "next/server"
16:23:51.429
16:23:51.430	    ../../../tmp/iy1gcmczsgf/middleware.func.js:1:27:
16:23:51.430	      1 │ import {NextResponse} from 'next/server';
16:23:51.430	        ╵                            ~~~~~~~~~~~~~
16:23:51.430
16:23:51.431	  You can mark the path "next/server" as external to exclude it from the bundle, which will remove this error.
16:23:51.431
16:23:51.468	/opt/buildhome/.npm/_npx/39e2fd552b408994/node_modules/esbuild/lib/main.js:1575
16:23:51.468	  let error = new Error(`${text}${summary}`);
16:23:51.469	              ^
16:23:51.469
16:23:51.469	Error: Build failed with 1 error:
16:23:51.469	../../../tmp/iy1gcmczsgf/middleware.func.js:1:27: ERROR: Could not resolve "next/server"
16:23:51.470	    at failureErrorWithLog (/opt/buildhome/.npm/_npx/39e2fd552b408994/node_modules/esbuild/lib/main.js:1575:15)
16:23:51.470	    at /opt/buildhome/.npm/_npx/39e2fd552b408994/node_modules/esbuild/lib/main.js:1033:28
16:23:51.470	    at /opt/buildhome/.npm/_npx/39e2fd552b408994/node_modules/esbuild/lib/main.js:978:67
16:23:51.470	    at buildResponseToResult (/opt/buildhome/.npm/_npx/39e2fd552b408994/node_modules/esbuild/lib/main.js:1031:7)
16:23:51.470	    at /opt/buildhome/.npm/_npx/39e2fd552b408994/node_modules/esbuild/lib/main.js:1143:14
16:23:51.471	    at responseCallbacks. (/opt/buildhome/.npm/_npx/39e2fd552b408994/node_modules/esbuild/lib/main.js:680:9)
16:23:51.471	    at handleIncomingPacket (/opt/buildhome/.npm/_npx/39e2fd552b408994/node_modules/esbuild/lib/main.js:735:9)
16:23:51.471	    at Socket.readFromStdout (/opt/buildhome/.npm/_npx/39e2fd552b408994/node_modules/esbuild/lib/main.js:656:7)
16:23:51.471	    at Socket.emit (node:events:527:28)
16:23:51.471	    at addChunk (node:internal/streams/readable:324:12) {
16:23:51.471	  errors: [
16:23:51.471	    {
16:23:51.471	      detail: undefined,
16:23:51.472	      id: '',
16:23:51.472	      location: {
16:23:51.472	        column: 27,
16:23:51.472	        file: '../../../tmp/iy1gcmczsgf/middleware.func.js',
16:23:51.472	        length: 13,
16:23:51.472	        line: 1,
16:23:51.472	        lineText: "import {NextResponse} from 'next/server';",
16:23:51.472	        namespace: '',
16:23:51.472	        suggestion: ''
16:23:51.473	      },
16:23:51.473	      notes: [
16:23:51.473	        {
16:23:51.473	          location: null,
16:23:51.473	          text: 'You can mark the path "next/server" as external to exclude it from the bundle, which will remove this error.'
16:23:51.473	        }
16:23:51.473	      ],
16:23:51.473	      pluginName: '',
16:23:51.474	      text: 'Could not resolve "next/server"'
16:23:51.474	    }
16:23:51.474	  ],
16:23:51.474	  warnings: []
16:23:51.474	}
16:23:51.474
16:23:51.474	Node.js v17.9.1
16:23:51.496	Failed: build command exited with code: 1
16:23:52.452	Failed: error occurred while running build command

Middleware Code:

import { NextResponse } from 'next/server';
import type { NextRequest } from 'next/server';
export const config = {
matcher: ['/', '/index'],
}
export function middleware(request: NextRequest) {
const basicAuth = request.headers.get('authorization')
const url = request.nextUrl
if (basicAuth) {
const authValue = basicAuth.split(' ')[1]
const [user, pwd] = atob(authValue).split(':')
if (user === process.env.NEXT_PUBLIC_USERNAME && pwd === process.env.NEXT_PUBLIC_PASSWORD) {
  return NextResponse.next()
}

}
url.pathname = '/api/auth'
return NextResponse.rewrite(url)
}

For reference, the starter I'm using: https://github.com/vercel/examples/tree/main/edge-middleware/basic-auth-password

I would theorise that at first glance this could have something to do with how the Vercel build output treats middleware. It appears that they build middleware as their own independent project, with its own node_modules in the build output, for some reason.
Please do note that I have not tested this theory, it was just something that I happened to notice when I was generating different configs a few days ago.

@mackenly this issue has likely been fixed by https://github.com/cloudflare/next-on-pages/pull/206 (see https://github.com/cloudflare/next-on-pages/issues/129#issuecomment-1496149575)
Could you please check if with the latest beta release everything works as expected?

@dario-piotrowicz @james-elicx
Tested with the vercel example project and all builds good using the<EMAIL_ADDRESS>beta version. There are some compatibility differences with the Vercel functions and Workers in the API route so didn't fully test the example, but it builds okay which should be a good sign. Thanks!

@mackenly great! :smiley:
Thank you so very much for checking!


the url for data download can't work

I execute the command "python ./dataprep.py --save_path data --download --user USERNAME --password PASSWORD" with my own username and password but got the response below. And I also try to open the url in person ,it fail
--2023-03-18 15:59:52--  http://cnode01.mm.kaist.ac.kr/voxceleb/vox1a/vox1_dev_wav_partaa
Resolving cnode01.mm.kaist.ac.kr (cnode01.mm.kaist.ac.kr)... <IP_ADDRESS>
Connecting to cnode01.mm.kaist.ac.kr (cnode01.mm.kaist.ac.kr)|<IP_ADDRESS>|:80... connected.
HTTP request sent, awaiting response... No data received.
Retrying.

--2023-03-18 15:59:54--  (try: 2)  http://cnode01.mm.kaist.ac.kr/voxceleb/vox1a/vox1_dev_wav_partaa
Connecting to cnode01.mm.kaist.ac.kr (cnode01.mm.kaist.ac.kr)|<IP_ADDRESS>|:80... connected.
HTTP request sent, awaiting response... No data received.
Retrying.

--2023-03-18 15:59:56--  (try: 3)  http://cnode01.mm.kaist.ac.kr/voxceleb/vox1a/vox1_dev_wav_partaa
Connecting to cnode01.mm.kaist.ac.kr (cnode01.mm.kaist.ac.kr)|<IP_ADDRESS>|:80... connected.
HTTP request sent, awaiting response... No data received.
Retrying.

--2023-03-18 15:59:59--  (try: 4)  http://cnode01.mm.kaist.ac.kr/voxceleb/vox1a/vox1_dev_wav_partaa
Connecting to cnode01.mm.kaist.ac.kr (cnode01.mm.kaist.ac.kr)|<IP_ADDRESS>|:80... connected.
HTTP request sent, awaiting response... No data received.
Retrying.

--2023-03-18 16:00:04--  (try: 5)  http://cnode01.mm.kaist.ac.kr/voxceleb/vox1a/vox1_dev_wav_partaa
Connecting to cnode01.mm.kaist.ac.kr (cnode01.mm.kaist.ac.kr)|<IP_ADDRESS>|:80... connected.
HTTP request sent, awaiting response... No data received.
Retrying.

--2023-03-18 16:00:09--  (try: 6)  http://cnode01.mm.kaist.ac.kr/voxceleb/vox1a/vox1_dev_wav_partaa
Connecting to cnode01.mm.kaist.ac.kr (cnode01.mm.kaist.ac.kr)|<IP_ADDRESS>|:80... connected.
HTTP request sent, awaiting response... No data received.
Retrying.

Same issue, just wondering if anyone has solved it

Same issue, any fix?

Same issue, any fix?

+1

Same issue, any fix?

+1

Try to download from here: https://mm.kaist.ac.kr/datasets/voxceleb/

Try to downlaod from https://github.com/alibaba-damo-academy/3D-Speaker/blob/main/egs/voxceleb/sv-eres2net/local/download_data.sh

The dataset is available from https://mm.kaist.ac.kr/datasets/voxceleb/
The download tool in dataprep.py has not yet been updated to reflect this change.


image.derivatives(width,height,[background]).url() just returns the original image URL

When the results of the derivatives() function are piped into url(), we just get the original image URL instead of a URL for the cached, resized image.

This is because the .url() function/chain is still preserved for the original image, whereas .derivates().html() will return the HTML-structure. Derivatives generates the images and the srcset-attribute, which has no meaning without the HTML-tag. Therefore you'd commonly use image.derivates().html() to generate the responsive IMG-tag - including its generated images - and  image.derivates().url() to link to the fullsize image, for example as a part of a lightbox feature.

Okay, I see what you mean. But I feel like the logical thing would be for derivatives().url() to return the URL of the appropriate resized image for the user's device. Is this not possible on the server side? I thought it must be - for example, it looks like mod_pagespeed can do this even though it's running on the server side. Please correct me if I'm wrong.

derivatives().url() is unable to return the device-specific URL, because Twig renders - like PHP - server-side, ie. before any client input is returned. That, however, is not the function of the srcset-attribute. In the IMG-tag, we set a default src-attribute - typically a medium size image for fallback - and populate the srcset-attribute with alternatives. When the browser loads the site, it is already aware of the size of the viewport on render, and thus the browser will replace the src-attribute with the most appropriate image available in the srcset-attribute.
That is to say, rather than waiting on the client (browser) to report back what device is used (often through JS), we have a predefined list of available images that the browser can choose from to render to the client. It really is a question of what is more efficient: Waiting for input before selecting a source, or giving a preset menu of alternatives that are applied beforehand. In essence, srcset and derivatives does all this server-side, and waits for no input before giving the client optimized alternatives. PageSpeed does the same, but on the server-level rather than programming-interface-level.

I understand that generally server-side languages cannot get information like this about the user. But then how does mod_pagespeed do it? Does it grab the information from the request header? And could derivatives() be set up to do something similar?
I understand that derivatives() basically exists to generate a srcset HTML tag with a call to derivatives().html(). But I feel like it could be used for so much more. For example, it would be amazing if we could use derivatives().url() to get the URL of the appropriate resized image for the user's device. Could this be possible? If it worked, we would have a very cutting-edge way to do image optimization!

Mod_pagespeed and srcset deliver virtually the same thing; information is grabbed from the browser on render, determining the size of the viewport, then the browser selects the most appropriate image. Derivates() could presumably be extended to allow targeting the generated image-sizes from cache, but cache should be able to deliver the URL of it by using image.resize.url().
With mod_pagespeed or srcset you are already delivering optimized sizes for the set device-sizes, what would you want to optimize further?

To answer your question, an example of where I would use derivatives().url() would be in the CSS background-image property. It would be a super-cool cutting edge way to display optimized background images. What do you think?

You could achieve that with pseudo-CSS, ie. render it in <style> so Twig can generate it in a template.

Could you give an example of how I would code that?

This is where the derivatives()-function comes short, as it currently cannot pass paths to generated images back into Twig other than to output the full IMG-tag. That is, to my knowledge, one of the core devs might be aware of any changes to it that allows this.
Last I did this, I passed images to a macro, like this:
{% macro css(file, base, id) %}
	{% set filename = file|split('.') %}
	{% set filenameext = "." ~ filename|last %}
	{% set file = file|replace({(filenameext): ""}) %}
	#{{ id }} {
		background-image: url("{{ base }}/{{ file }}-2240{{ filenameext }}");
	}
	@media (min-width: 30em) {
		#{{ id }} {
			background-image: url("{{ base }}/{{ file }}-640{{ filenameext }}");
		}
	}
	@media (min-width: 34em) {
		#{{ id }} {
			background-image: url("{{ base }}/{{ file }}-960{{ filenameext }}");
		}
	}
	@media (min-width: 48em) {
		#{{ id }} {
			background-image: url("{{ base }}/{{ file }}-1280{{ filenameext }}");
		}
	}
	@media (min-width: 62em) {
		#{{ id }} {
			background-image: url("{{ base }}/{{ file }}-1600{{ filenameext }}");
		}
	}
	@media (min-width: 75em) {
		#{{ id }} {
			background-image: url("{{ base }}/{{ file }}-1920{{ filenameext }}");
		}
	}
	@media (min-width: 125em) {
		#{{ id }} {
			background-image: url("{{ base }}/{{ file }}-2240{{ filenameext }}");
		}
	}
{% endmacro %}

This, in conjunction with this script, to generate the responsive-sized images. Used, for example, for header images:
{{ srcset.img(page.header.header_image, page.url, "article-header-image") }}


chore(linter): Improve TSLint configuration

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Iihjj

Hhhh is

Thank you, I appreciate it.

On Nov 3, 2019 at 4:56 pm,  <Amyparker2401 (mailto:notifications@github.com)>  wrote:
Hhhh is
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly,   view it on GitHub (https://github.com/lee-dohm/atom-style-tweaks/issues/557?email_source=notifications&email_token=AL6ASJY3UNDYCYFEX44S3MLQR37EXA5CNFSM4JIMECR2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEC5XRJY#issuecomment-549157031), or   unsubscribe (https://github.com/notifications/unsubscribe-auth/AL6ASJ2FLVQPMT2SMRG4HALQR37EXANCNFSM4JIMECRQ).


Open up the TtlUpdate Offline code path.

Codecov Report
Patch coverage: 17.24% and project coverage change: -39.78% :warning:

Comparison is base (6622e11) 72.51% compared to head (d394eda) 32.74%.

Additional details and impacted files
@@              Coverage Diff              @@
##             master    #2580       +/-   ##
=============================================
- Coverage     72.51%   32.74%   -39.78%
+ Complexity    11375     4463     -6912
=============================================
  Files           803      803
  Lines         64660    64686       +26
  Branches       7897     7903        +6
=============================================
- Hits          46890    21180    -25710
- Misses        15203    41274    +26071
+ Partials       2567     2232      -335

Files Changed
Coverage Δ

...om/github/ambry/router/SimpleOperationTracker.java
53.49% <0.00%> (-42.31%)
:arrow_down:

...va/com/github/ambry/router/TtlUpdateOperation.java
38.26% <4.16%> (-53.09%)
:arrow_down:

.../github/ambry/router/NonBlockingRouterMetrics.java
72.88% <100.00%> (-17.16%)
:arrow_down:

... and 538 files with indirect coverage changes

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


Update stale issues and PRs workflow

Changed the default 60/7 days of inactivity to 14/14.
Plus messages to convey the stale'ing and closing of the issues.

I'd like to hear from you all regarding the following:

I believe that default 60 days is way too much, but not certain if 14 is a reasonable value either. What you think?
How do you like the wording of the messages? Are they concise and make the point clear?

14/14 seems reasonable.  I guess that could always be adjusted in the future if there's issues with that timeframe.
The close message might be more clear if rearranged slightly:  "This issue has been automatically closed as sufficient information hasn't been provided on the issue for further actions to be taken."

I would just like to add that 2 weeks is nothing when people are busy with their lives (e.g. work, family, etc.). I've experienced this myself in different projects, when sometimes it may take months for someone to come back with the requested information.
Also, it's super annoying having to bump up the issue every few weeks just because it's been marked as "stale" by some bot, even though the issue itself hasn't been solved, and no developer has even had time to start working on it yet.

I would just like to add that 2 weeks is nothing

After stale'ing there are another 2 weeks before closing. This is actually why I want to gather more feedback on the timings proposed. We may make it 30/7 for example.

Also, it's super annoying having to bump up the issue every few weeks just because it's been marked as "stale" by some bot, even though the issue itself hasn't been solved, and no developer has even had time to start working on it yet.

The intention here is to stale only those issues, which are marked with need info label, which should signify, that not enough information is available to proceed. If enough information is gathered, the label should be removed and a new one attached, like enhancement or bug etc. You may see, that this bot acts only on need info issues and ignores the rest.

The close message might be more clear if rearranged slightly: "This issue has been automatically closed as sufficient information hasn't been provided on the issue for further actions to be taken."

Looks even better!

I think 30/7 is a reasonable value. 14 is too short IMO.

I've squashed everything and put 30/7.

so that we can re-open the issue

I would be very-very-very cautious about promising anything anyone, that's why I intentionally omitted this phrase ;) :D

The it's better left out the entire sentence if there is no intention to do anything, otherwise it is confusing I think.

there is no intention to do anything

Quite the opposite! If the information is sufficient for re-opening - why not! In case it is a mere "bump" thing — sorry, no way.

there is no intention to do anything

Quite the opposite! If the information is sufficient for re-opening - why not! In case it is a mere "bump" thing — sorry, no way.

Without explanation I think people cannot read into all these in that one sentence, but let's keep it the way you put it for now.


Error when calling a method that takes keyword arguments with MultiTenant.wrap_methods

Starting with Ruby 3.0, argument delegation using (*args) will no longer work with keyword arguments.
def hoge(a:)
  "a is #{a}"
end

def foo(*args)
  hoge(*args)
end

pp foo(a: 1)
# Ruby 2.7 => "a is 1"
# Ruby 3.0 => error: wrong number of arguments (given 1, expected 0; required keyword: a) (ArgumentError)

This will cause an error if you wrap a method that takes keyword arguments with MultiTenant.wrap_methods.
class User < ActiveRecord::Base
  # ...
end

user = User.create(name: "homu", age: 14)

# OK: keyword arguments can be passed
user.touch(time: Time.current)

MultiTenant.wrap_methods(User, "self", :touch)

# NG: keyword arguments cannot be passed to wrapped methods.
# error: write unknown attribute `{:time=>2022-10-27 21:08:52.020778708 +0900}` (ActiveModel::MissingAttributeError)
user.touch(time: Time.current)

To solve this problem, you can use the forwarding arguments (...) , which was added in Ruby 2.7.
def hoge(a:)
  "a is #{a}"
end

def foo(...)
  hoge(...)
end

pp foo(a: 1)
# Ruby 2.7 => "a is 1"
# Ruby 3.0 => "a is 1"

NOTE: Forwarding arguments do not work in Ruby 2.6.
Add supported Ruby 2.6  or lower.

Thanks :)


Commit for upgrade

📝 Changed routes:

/
/

(view full size)
(view full size)

Commit 37d00efa39ca8fb4ba9db362372e2bb2c9ac2bd0 (https://ui-l4sb3lokp-cosmo-au.vercel.app).


server-reflection.md: fix markdown

The table isn't rendered correctly.
Supersedes https://github.com/grpc/grpc/pull/16093 (which doesn't have CLA signed, so I recreated the fix).

Objective-C binary sizes
*****************STATIC******************
  New size                      Old size
 1,964,792      Total (=)      1,964,792

 No significant differences in binary sizes

***************FRAMEWORKS****************
  New size                      Old size
10,887,060      Total (<)     10,887,069

 No significant differences in binary sizes


dat sync -v: Maximum call stack size exceeded

dat version: 13.7.0
os version: ubuntu 17.04
summary
dc@dcpos:~/rotonde-client$ dat sync -v
dat v13.7.0
Downloading dat: 18 files (451 KB)
                 28 files (475 KB)
2 connections | Download 0 B/s Upload 0 B/s
0 connections | Download 0 B/s Upload 0 B/s
dat synced, waiting for updates.
Downloading updates...
                   ======================--] 96.77%
Ctrl+C to Exit

/usr/lib/node_modules/dat/node_modules/debug/src/debug.js:65
  function debug() {
                ^

RangeError: Maximum call stack size exceeded
    at debug (/usr/lib/node_modules/dat/node_modules/debug/src/debug.js:65:17)
    at Hyperdrive.<anonymous> (/usr/lib/node_modules/dat/src/lib/download.js:33:7)
    at emitNone (events.js:86:13)
    at Hyperdrive.emit (events.js:188:7)
    at /usr/lib/node_modules/dat/node_modules/hyperdrive/index.js:138:14
    at kick (/usr/lib/node_modules/dat/node_modules/hyperdrive/index.js:233:5)
    at Object.callback (/usr/lib/node_modules/dat/node_modules/hyperdrive/index.js:220:7)
    at Peer._downloadRange (/usr/lib/node_modules/dat/node_modules/hypercore/lib/replicate.js:368:13)
    at Peer.update (/usr/lib/node_modules/dat/node_modules/hypercore/lib/replicate.js:299:12)
    at Peer.update (/usr/lib/node_modules/dat/node_modules/hypercore/lib/replicate.js:300:51)

i ran dat sync -v in a screen session on my server, to make sure that my fork of Rotonde stays seeded
after a few days (i think), i got the mysterious error above
looks like it's happening here: https://github.com/datproject/dat/blob/master/src/lib/download.js#L33
maybe state.stats.get() has a circular reference that debug() is trying to follow, or something like that

Can you check the installed dat version and hypercore/hyperdrive? We fixed
a v similar bug a few months ago
On Fri, Dec 22, 2017, 12:05 DC<EMAIL_ADDRESS>wrote:

dat version: 13.7.0
os version: ubuntu 16.04
summary
dc@dcpos:~/rotonde-client$ dat sync -v
dat v13.7.0
Downloading dat: 18 files (451 KB)
28 files (475 KB)
2 connections | Download 0 B/s Upload 0 B/s
0 connections | Download 0 B/s Upload 0 B/s
dat synced, waiting for updates.
Downloading updates...
======================--] 96.77%
Ctrl+C to Exit
/usr/lib/node_modules/dat/node_modules/debug/src/debug.js:65
function debug() {
^
RangeError: Maximum call stack size exceeded
at debug (/usr/lib/node_modules/dat/node_modules/debug/src/debug.js:65:17)
at Hyperdrive. (/usr/lib/node_modules/dat/src/lib/download.js:33:7)
at emitNone (events.js:86:13)
at Hyperdrive.emit (events.js:188:7)
at /usr/lib/node_modules/dat/node_modules/hyperdrive/index.js:138:14
at kick (/usr/lib/node_modules/dat/node_modules/hyperdrive/index.js:233:5)
at Object.callback (/usr/lib/node_modules/dat/node_modules/hyperdrive/index.js:220:7)
at Peer._downloadRange (/usr/lib/node_modules/dat/node_modules/hypercore/lib/replicate.js:368:13)
at Peer.update (/usr/lib/node_modules/dat/node_modules/hypercore/lib/replicate.js:299:12)
at Peer.update (/usr/lib/node_modules/dat/node_modules/hypercore/lib/replicate.js:300:51)
i ran dat sync -v to make sure my fork of Rotonde stays seeded
after a few days (i think), i got the mysterious error above
looks like it's happening here:
https://github.com/datproject/dat/blob/master/src/lib/download.js#L33
maybe state.stats.get() has a circular reference that debug() is trying
to follow, or something like that
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/datproject/dat/issues/908, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAW_VREpnsSjo8FoE2g5Y2LN5cD-yt3Rks5tC4zngaJpZM4RK6zr
.

@mafintosh
dat: 13.7.0
hypercore: 6.6.6
hyperdrive: 9.4.8


Installation instructions for NUKE

Hi everyone! I'm basically following up on another recent proposal to extend the installation instruction tabs.
Proposal
NUKE provides a nuke :add-package <package-id> [package-version] command via our global tool, which allows installing packages to the build project. The command works from any directory of a repository built with NUKE, thus covering more situations compared to the conventional dotnet add command. More importantly, though, it automatically determines how a package should be installed, which is either as PackageReference (regular libraries) or PackageDownload (tool packages). The latter is a great feature (thanks once more @nkolev92), because it allows a build to reference tools without messing with references (implicit ExcludeAssets), and works with tools in different versions (PackageReference wouldn't allow that even with ExcludeAssets).
We would like to display this command as installation instructions under a separate "NUKE" tab. Today, users naturally use PackageReference instead of PackageDownload, which often completely breaks the compilation of the build project, and overall is a sub-optimal approach.
Listing Criteria
Regarding if we meet the criteria, here are my comments:

Signification adoption in .NET community: currently at 1.4M total downloads and around 1k downloads per day for the main package
Actively maintained and updated: the project is continuously maintained for the last 4 years (since its creation), and as mentioned below used by a wide range of companies and projects
Security compliance: We have repeatable builds. Publish signed packages. Have a package prefix reservation. And 2FA for NuGet.org!

Background
NUKE is a build automation system, which is created with the idea to integrate with other .NET tools natively. That means it uses regular C# projects for the build implementation and thus comes with IDE integration out-of-the-box, including navigation, refactoring, and debugging. It is well adopted with almost 1k downloads per day, and many companies and projects are actively using or transitioning to it (e.g. OctopusDeploy, JetBrains, AvaloniaUI, ASP.NET Boilerplate, CsvHelper, FluentAssertions, HotChocolate).

We and our users would really appreciate if this proposal would be accepted! 🙏

Visual proposal
Here is an example of how that could look like

Hey everyone,
First off, thanks so much for writing a proposal to add the NUKE DSL instructions to NuGet.org! From an initial review, we believe that NUKE meets majority of the requirements set via https://github.com/NuGet/NuGetGallery/issues/4510#issuecomment-324422213. There is one requirement that we aren't too sure of given the unfamiliarity of NUKE, and that's the presence of a User Agent in the client tooling to understand package download usage from NUKE compared to other client tooling. We are hopeful that it's possible to add a custom NUKE user agent to the NuGet APIs you're using such as:

UserAgent.CreateUserAgentString()
UserAgent.SetUserAgentString()

Examples: https://github.com/NuGet/NuGet.Client/search?q=useragent
(We can help further if there's good places to hook into)
This would help us understand what client is downloading a package & would help in the long-term with the ecosystem being more data-driven! You can see this example of what I mean by that:
https://www.nuget.org/stats/packages/Microsoft.EntityFrameworkCore?groupby=Version&groupby=ClientName
Additionally we look at the usage of the tooling in various .NET projects. I think that is mostly covered by your proposal with an expanded list here: https://github.com/nuke-build/nuke#users.
We'd ask that before we can approve a contribution from the NUKE project to add these instructions, that a custom user agent is added to the tooling. Once that is completed(if it's feasible), we can move forward with a contribution to add the instructions & merge when initial data comes in.
In the meantime, we are also encouraging the use of our new proposal process. This helps us go through the rounds of the various considerations made & gives people in the community an opportunity to bring up questions & feedback prior to it being accepted. If there's time to create a quick proposal & send a PR to nuget/home, that would be wonderful.
In short:

Significant adoption in .NET community ✔⚠(Addition of user agent for long-term ecosystem data)
Actively maintained and updated ✔
Security compliance ✔

Action Items for NUKE project maintainers 📋:

Investigate the inclusion of custom user agent into NUKE tooling to report the NUKE client in package statistics.
Creation of a NuGet proposal to provide the community a place to discuss & be accepted if no major objections/considerations.
Consideration for NUKE tab instruction contribution for NuGet packages & .NET tools (If applicable) - See: https://github.com/NuGet/NuGetGallery/pull/8434 & https://github.com/NuGet/NuGetGallery/pull/8440 for recent examples.

If this all sounds reasonable, then we'll review the proposal in the next couple weeks while awaiting the investigation of the user agent inclusion. Please let me know if there are any questions, comments, or feedback to these initial considerations. We're trying to make these considerations as transparent as possible & still have a ways to formally document them.
Note: We're trying our best to not change any requirements, but rather to improve our processes. As you may imagine, the requirements list in 2017 still reflects the considerations, but we want to ensure the long-term success by being data-driven and learning from recent contributions as well.

@JonDouglas generally speaking NUKE doesn't act as a dedicated NuGet client. It fully operates on either dotnet CLI or the Microsoft.Build package, which makes it transparent, up-to-date, and most of all integrated with all the developer tools that exist. If you need a user agent, it probably could be added in some way, but I'm gonna say it would be rather artificial:

At design-time, a build author can add a package with the mentioned command nuke :add-package <package-id>. This simply adds the PackageReference item to the csproj file using Microsoft.Build infrastructure, and then performs a dotnet restore on the build project which triggers the download to the global NuGet cache. It is only converted to PackageDownload if the package contains a ./tools directory. Providing a user-agent would require replacing the dotnet CLI call, which implies more maintenance, but – yes – doable.
At build-time, the build project is restored and built with dotnet build. I'm afraid requiring a user-agent at this moment could imply breaking the minimal bootstrapping mechanism of NUKE, which is particularly something that users have benefited from because it is resilient to any upstream changes and hence less fragile. It could be possible by making a second roundtrip to NuGet.org, but I guess it's not in the interest of anyone to download packages twice.

Is it possible by any chance to set a different user-agent from outside? For instance with an MSBuild property /p:NuGetUserAgent=.. or as an environment variable NUGET_USER_AGENT ? From a quick glance there is no such thing, but maybe it could be added? A similar approach already exists with NUGET_PACKAGES for instance.
I hope it's clear that this proposal is laid out for more efficient and correct package consumption, and I'd appreciate it if we can find a solution to this without degrading the existing native integration with .NET tools.

Thanks for the quick response!
We figured that might be the situation, but wanted to bring it up for feasibility & consideration. To my knowledge, no such property or ENV variable exists but could be something we break-off separate to this proposal to be considered for the future to not disrupt the native integration while also reporting the client use.
Let's move forward with the other action items to keep the momentum.
Thanks!

Just to clarify, the only other action you need me to approach is to create the proposal according to the new process ?

@matkoch Yes that's correct. The contribution PR can wait until the proposal PR is reviewed & accepted by the community & NuGet.

I think we can close this. Follow-up is linked above.

reopening as per this comment: https://github.com/NuGet/Home/issues/10784#issuecomment-824239843

@zivkan sorry i did not know :) should i update my original post maybe to only link the new spec?

@matkoch, this change is now live on PROD. Thanks again for your hard work here!

@joelverhagen wasn't hard actually :) Thanks for your assistance!


api products error: Value cannot be null. (Parameter 'value')

Hello everyone. I can get categories without problem via api. But when i try to get products i get an error.(First i called with default swagger parameters and then i set it null like i used in to get categories)
{
"error": "Value cannot be null. (Parameter 'value')"
}

Hi, method parameters decorated with FromQueryJson attribute must be url encoded json string. Therefore the default swagger parameters will fail. Try "{}" instead (including quotes).

Hi @stepanbenes
I have just encountered the same issue. It works if I wrap the parameters in double quotes:
"{\"fields\": \"Name\"}"
Is there a reason for that? Some endpoints like Category don't require this approach.

Hi @Tripplefix, there is no reason for that. You are right, the query parameters should be unified across all controllers. I added FromQueryJson parameters type to allow easier implementation of api client source generator (project ApiBindingsGenerator). I will remove query json parameters as soon as I will come with a suitable implementation.

Related to https://github.com/domaindrivendev/Swashbuckle.AspNetCore/issues/66

Fixed in 561bfc87cbf0612466d9959f2af8a212949a4a9b. All FromQueryJson parameters were removed. Swagger UI should work correctly now.


Typo

Checked for duplicates
No - I haven't checked
🐛 Describe the bug
https://ipda.jpl.nasa.gov/meetings/
says
The IPDA 17th Steering Committee meeting was held at ESCA (Madrid, Spain) in September 2022.
ESCA -> ESAC
🕵 Expected behavior
I expected [...]
📜 To Reproduce

...
🖥 Environment Info

Version of this software [e.g. vX.Y.Z]
Operating System: [e.g. MacOSX with Docker Desktop vX.Y]
...

📚 Version of Software Used
No response
🩺 Test Data / Additional context
No response
🦄 Related requirements
🦄 #xyz
⚙ Engineering Details
No response
🎉 Integration & Test
No response

Skipping I&T. Very simple fix. No additional testing needed.


Aggregate rewrite

Coverage decreased (-0.1%) to 80.251% when pulling d4dcf9e0093a850ae82705673e362d70df91a89a on agg-rewrite into 06b130cbb1e6631be313cada0255f42fed98bdcd on master.


Set add code to set indention style to something other than default

I think I like Java best.

Moot for now.


Example

I tried to include your .js file in my browser but I get the error:
ReferenceError: exports is not defined

On line 3 in the ckeditor.js

Hi,
What packages manager/bundler do you use ?
Thanks !

Hey bro!
I'm using webpack. It seemed to load the component but not the necessary JS file. Do you have a example how to include it?

I'll try to make a sample repo based on angular2-seed !

You can find a sample with webpack here : https://github.com/chymz/angular2-seed-ckeditor

Hey man, thank you a lot :) now it works!

Can be closed

I can't access this link:  https://github.com/chymz/angular2-seed/tree/ng2-ckeditor
I got the same error: Uncaught ReferenceError: exports is not defined

got the same error: Uncaught ReferenceError: exports is not defined
I can't access this link: https://github.com/chymz/angular2-seed/tree/ng2-ckeditor


gpg backend: document gpg-agent's auto-expand-secmem option

Summary
gopass with GPG backend may fail in case of a large number of concurrent requests. GPG will return exit status 2 and an error message "gpg: decryption failed: No secret key".
The reason is that gpg-agent has insufficient secret memory for processing many concurrent requests. There is an option auto-expand-secmem, which fixes this behavior by auto increasing the secret memory as needed. The option needs to be set in ~/.gnupg/gpg-agent.conf and followed by the gpg-agent restart (killall gpg-agent will suffice).
Please document this somewhere. This was the only major blocking issue we've had with gopass.

Thanks a lot for providing this hint. I wasn't aware of this option. We'll put it in the documentation.

I was just lucky to find a couple of similar bug reports:
https://dev.gnupg.org/T4146
https://dev.gnupg.org/T3530

I'll add a note to the FAQ. Unfortunately I don't see an easy way to do runtime checks, as this option is not available for all versions of GnuPG and checking it would be noisy and/or error prone.

Good enough for me, thanks a lot! :)

@tagirb you saved many years of my life, thanks a lot! ❤


Add badges

Was raised on the BOF session.
It could be good to encourage badges like this one:
![Static Badge](https://img.shields.io/badge/SPEC-0%2C1%2C4-brightgreen)

(OC you can make this clickable so that it goes to the SPEC's website.)

I assume the numbers reference the endorsed SPECs? That list might get too long at some point. What do you think about providing two kinds of badges:

A badge referencing a specific SPEC. And instead of a number we would encourage a short keyword, e.g. "SPEC | 0 - Minimum Version". Projects are free to add one or multiple ones.
A summary badge, with a count of SPECs that a project aims to follow, e.g. "SPEC | 3 supported" or "SPEC | 3 adopted"

I am skeptical about displaying a count, because it might imply that more is better, even though projects might have good reasons not to adopt a SPEC. So the badge should definitely be an affirmative green always.

Yeah so I was thinking about just not showing any number at all too. It could just read SPEC|compliant. Or something like that.

What determines if a discussion happens on github versus discourse?

And more meta stuff like this will likely happen in GH.

BTW, happy to see you here @aterrel 😃

Linked to that, or I can convert that comment into an issue.
On top of badges, what if we provided some sort of card?
I was looking at this (on Apple for an App you have these sorts of cards):

I imagine the same design but for SPECs. I am a bit lazy to do the mockup right now 😅, but replace the logo with our logo, instead of Data ... put the number of the SPEC and a short description. And then for the items bellow you write the implementation details. e.g. if you support SPEC 0 you say things like Support x years etc. You could either have such a card per SPEC, or just one cart which lists all endorsed SPECs with sections for all SPECs to give the implementation details.

I think cards would make sens once we have a bit more specs in the pipeline.  +1 for badge. I think we could also suggest a github topic, so that it's easier to search for project using a spec.

Good idea for the GitHub topic +1

Re the badge in the opening: what about having one separate one for each SPECs rather than a joint? Then their link could point to the actual SPEC's page.

(and based on today's discussion, I suppose these badges should not mean "endorsed" but rather "implemented" or "follow" or whatever the right term will be. (maybe "SPEC 0 powered", though that's a bit too much I suppose )

Yeah not sure because that could quickly lead to Christmas trees in the readme. Projects like NetworkX already support a bunch so they would need to add multiple badges.
I think leaving this up to the projects is also ok. So we say: either make one badge per SPEC following this template, or have a single badge with this other template.

they would need to add multiple badges.

I don't think the need to add, but the could add the badges.
My main motivation with the one per spec is that it could easily link back to, while the one above is a bit more misleading if the badge would look almost the same, just a different combination of numbers on it (which could then of course also lead to a Christmas tree appearance for projects that adopted a lot of them)

I've added spec-0000 topic to IPython. We can add description to a topic only once there are enough repos with it.

I think leaving this up to the projects is also ok. So we say: either make one badge per SPEC following this template, or have a single badge with this other template.

+1 on this. This fits with the philosophy of projects having agency with which SPECs they want to endorse. For the case were projects want to collect endorsed SPECs in a single badge, we could just offer two flavors: one that lists all endorsed ones, and one that just says something like "SPECs endorsed".
Can we make it so that the badge has a white Scientific Python tree inside? That might make it more distinct and professional looking. :)

I've added spec-0000 topic to IPython. We can add description to a topic only once there are enough repos with it.

Should it be https://github.com/topics/spec-0 or https://github.com/topics/SPEC-0 instead of https://github.com/topics/spec-0000? The 0000 was mainly just so things would sort properly when I use ls at the command-line in the spec repository on my laptop. Everywhere else we just refer to it as SPEC 0.

Since no one commented, I've taken it as tacit endorsement of https://github.com/topics/spec-0000. So I added the following topics to the scientific-python/specs repo:
https://github.com/topics/spec-0000
https://github.com/topics/spec-0001
https://github.com/topics/spec-0004

Should the above be edited, I think everything was changed to removed the leading zeroes.
And sorry I was (trying to). take time off until a few hours ago.


Replace {group} with the full group name.

Kubeconform expects {{ .Group }} to be the full group name, e.g. cert-manager.io. But openapi2jsonschema.py replaces {group} with the abbreviated group name, e.g. cert-manager. Since the only purpose of the script is to make schema files for consumption by kubeconform, it seems like the script should use the full group name.

<3 kubeconform, BTW


Integration with travis

Hi.
It will be interesting to have a way to pass arguments to the shell file to be able to use Travis.
For example
./42FileChecker --path=/home/travis/libft --project=libft --tests=all --no-norminette

will launch 42FileChecker for the libft, pass moulitest and libftunit-test, doesn't check norminette and the libft is in /home/travis/libft directory.

Interesting idea as I told you on Slack :-)
It's on my TODO list

In progress :-)
https://github.com/jgigault/42FileChecker/pull/48