UnhandledPromiseRejectionWarning Error Occurred when 'npm run test:devtools'

After i clone this project, run eslint and tried run command 'npm run test:devtools', below error happened:
(node:67142) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'promise' of undefined
at TraceGatherer.onLoadEventFired (/Users/i065037/Documents/Innovation/wdio-mocha-typescript/node_modules/@wdio/devtools-service/build/gatherer/trace.js:117:67)
at /Users/i065037/Documents/Innovation/wdio-mocha-typescript/node_modules/puppeteer-core/lib/cjs/vendor/mitt/src/index.js:51:62
at Array.map ()
at Object.emit (/Users/i065037/Documents/Innovation/wdio-mocha-typescript/node_modules/puppeteer-core/lib/cjs/vendor/mitt/src/index.js:51:43)
at CDPSession.emit (/Users/i065037/Documents/Innovation/wdio-mocha-typescript/node_modules/puppeteer-core/lib/cjs/puppeteer/common/EventEmitter.js:72:22)
at CDPSession._onMessage (/Users/i065037/Documents/Innovation/wdio-mocha-typescript/node_modules/puppeteer-core/lib/cjs/puppeteer/common/Connection.js:225:18)
at Connection._onMessage (/Users/i065037/Documents/Innovation/wdio-mocha-typescript/node_modules/puppeteer-core/lib/cjs/puppeteer/common/Connection.js:101:25)
at WebSocket. (/Users/i065037/Documents/Innovation/wdio-mocha-typescript/node_modules/puppeteer-core/lib/cjs/puppeteer/common/WebSocketTransport.js:13:32)
at WebSocket.onMessage (/Users/i065037/Documents/Innovation/wdio-mocha-typescript/node_modules/ws/lib/event-target.js:125:16)
at WebSocket.emit (events.js:215:7)
[0-1] (node:67142) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 2)

thanks for submitting this issue.
it is caused by npm package updates.
i currently don't have the time to look into this issue - feel free to create a MR with the fix.

it is fixed now


Functionality of Popover.Group

Thanks for all the work you've put into this library! Excited to use it and see it grow. 😃

I want to use multiple Popovers to build a more complex site navigation header. Some pseudocode:
<script>
   const popover1 = createPopover({});
   const popover2 = createPopover({});
</script>

<button use:popover1.button ... />
<div use:popover1.panel ... />

<button use:popover2.button ... />
<div use:popover2.panel ... />

However, if I first click popover1.button, then click popover2.button (while popover1.panel is still "expanded") it will only close popover1.panel. I must click popover2.button a second time to open popover2.panel.
In headlessui, this action is supported with grouping related popovers (<Popover.Group />).
Is there a way to achieve that functionality?

I'll have to have a play around and see what the best way to support that - I'm picturing something a bit like Stripe's top-level nav, is that the right interpretation?

Yes, similar to Stripe's navigation. It would be an added bonus if it could support on-hover as well as on-click!

I was looking for the same functionality but have since realised I should be able to achieve it with a single popover being toggled from multiple nav items whilst switching out the content of the popover. I believe Stripe is the same though with more elaborate animations? Though I do not know if this would be enough for accessibility.
Thank you for the great library! Simple to use and I think an elegant solution to the headless UI problem.

I also wanted Popover Group functionality. I've since decided to implement a UI pattern found on rolex.com. Look at the Menu and Search buttons in the nav. When pressed, all other buttons fade away so no need for grouping even though there are multiple buttons opening the universal dropdown. Intuitively I feel this may be better for accessibility as well as there is only one focussed choice at a time - less opportunity for confusion.
Just wanted to share it as I now get to use this great library.


Implement color theming support

Alaska Airlines Pull Request
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Resolves: #121

Implement tier 3 tokens for color theming support
Update dependencies

Summary:
Please summarize the scope of the changes you have submitted, what the intent of the work is and anything that describes the before/after state of the project.
Type of change:
Please delete options that are not relevant.

[x] New capability
[x] Revision of an existing capability
[ ] Infrastructure change (automation, etc.)
[ ] Other (please elaborate)

Checklist:

[x] My update follows the CONTRIBUTING guidelines of this project
[x] I have performed a self-review of my own update

By submitting this Pull Request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
Pull Requests will be evaluated by their quality of update and whether it is consistent with the goals and values of this project. Any submission is to be considered a conversation between the submitter and the maintainers of this project and may require changes to your submission.
Thank you for your submission!
-- Auro Design System Team

Summary by Sourcery
Implement color theming support by introducing tier 3 tokens and updating component styles to use these tokens. Enhance documentation to include theme support details and refactor SCSS files for better maintainability.
New Features:

Introduce tier 3 tokens for color theming support, allowing components to be restyled using new SCSS variables.

Enhancements:

Refactor SCSS files to use shared styles for flight time elements, reducing code duplication.
Update component styles to utilize new color theming tokens for better customization.

Documentation:

Add documentation on theme support, including code samples for restyling components using new tokens.

Chores:

Remove outdated CSS custom property fallback documentation from README.

@sourcery-ai review

:tada: This PR is included in version 2.8.0-beta.1 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


net: TestDialerControl flake on darwin-amd64-race

https://build.golang.org/log/03a8960a27ab5e837fa3d57ae7b08f6ece4a4285:
--- FAIL: TestDialerControl (75.50s)
    --- FAIL: TestDialerControl/StreamDial (75.50s)
        dial_test.go:944: dial tcp6 [::1]:49570: connect: operation timed out
FAIL
FAIL	net	86.859s

Looks like the test was added about a year ago (in CL 72810). It's not obvious to me whether this is a recent regression or just a low-frequency flake.
CC @ianlancetaylor @mikioh

cc @bradfitz

No more failures in about a year. Possibly fixed (in the sense of no longer affected by a probable macOS kernel bug?) by #34920.
2019-08-30T17:07:53-9d480ed/darwin-amd64-race
2019-06-10T13:43:51-ec3ebf7/darwin-amd64-race


You are not authorized to access SendGrid, please contact Support.

Writing issue here as the support has no response for almost 2 weeks.

Hello @ErxrilOwl,
Thanks for submitting a GitHub issue! We are very sorry that you are running into this problem. In order to better serve you, as this does not present itself as a library specific issue, we would like to ask that you reach out to our support team at https://support.sendgrid.com.
Thank you!
SendGrid DX Team

It sounds like your account status might be under review. You should have received a notice in your e-mail with more details.
If you would like to discuss it, please respond to the email you received regarding the notice.
If you cannot find this e-mail, we ask our customers do the following:

Go to support.sendgrid.com
Click on Trouble Logging In
Click "I am having a different log in issue"

To reactivate your account, you may be prompted to outline your sending practices for support to vet and either reactivate or keep closed. Unfortunately, there is not a way around this since this vetting process is put in place by Compliance to prevent bad actors from misusing our product.

Support cannot assist in reactivation of banned accounts.
Hope this helps!
Twilio SendGrid Team

You are not authorized to access SendGrid, please contact Support...
This is terrible...i was depressed with this.....
I'm need of this in short time.. but facing signup issues.....it is too silly...
Could the team please resolve this quickly.....
like this image, i'm getting error.

Hi @Prakash07-er please follow the steps outlined in the comment above. If you are locked out from your account please open a new support request.


undefined method 'World'

I followed the instructions in the ReadMe and got the following error;
/home/gsimpson/.rvm/gems/ree-1.8.7-2011.03@myproject/gems/capybara-1.1.1/lib/capybara/cucumber.rb:6: undefined method `World' for main:Object (NoMethodError)

I'm using Rails 3.1.1 and all my gems are pretty up to date.
Cheers,
Graeme

Hi Simon
Not tested this with Rails 3.1, only Rails 3.
I will do an upgrade shortly and see if I can find the problem.
Matt

Works OK for me with rails 3.1.Are you using spork in your app?

I'm not using spork.

Can you show your Gemfile?

In this gist
https://gist.github.com/1342943

Can you provide the full stacktrace?

Hi Simmogs
I can't replicate this issue either.  See https://github.com/mattheworiordan/capybara-screenshot-test-rails-3.1 for a working version under Rails 3.1.  Can you provide some more information?
Matt

I've updated the gist to include the stacktrace. Hope that helps.
Cheers,
Graeme

Ah, I know exactly what the problem is Simmogs.
I wrote this for Cucumber & Capybara, not Capybara and RSpec, and you're using RSpec.
I'll work up a fix in the coming days, sorry about that, stupid mistake on my part really not to add that as a dependency.
Matt

I got this error too, I use neither cucumber nor spec, simple minitest. Hopefully your fix would address this too?

Hi metaskills
Could you post me a simple example of how you are using minitest?  Not used minitest before, so if you could provide a simple example I'll take a look into it.
Matt

Hey Matthew,
I can give you a few examples. Here are some canned resources. This is a demo Rails 3.1 project I had for a Capybara WebKit blog post I had never gotten around too. If you look at the demo integration test you will see a simple Test::Unit example or MiniTest::Unit example if you are running Ruby 1.9 since MT::U is the TU replacement in 1.9. So technically as is, that would be your example of TU or MT::U.
Going further, here is an article I had done on MiniTest::Spec with Rails which is just a spec DSL written on top of MiniTest::Unit. So if you wanted to, you could clone that project and add this to your Gemfile and that would add both mintiest and a make ActiveSupport::TestCase subclass a shim for MiniTest::Spec.
group :test do
  gem mini_specunit
end

Then that integration test could be written something like this.
class HolygrailTest < ActionDispatch::IntegrationTest

  it "should pass all things JS related" do
    visit demos_path
    page.has_selector?('h1#demoIndex').must_equal true
    find('h1#demoIndex').click
    page.has_selector?('h1#demoIndex').must_equal false
    visit goto_index_demos_path
    page.has_selector?('h1#demoIndex').must_equal true
    page.current_url.must_equal demos_url
  end

end

I have the same issue (using cucumber 1.1.1, cucumber-rails 1.2.0, capybara 1.1.1 and capybara-webkit 0.7.2).
As a workaround, I disabled auto-require of the gem in the gemfile:
gem "capybara-screenshot", :require => false

Then I added a file to features/support to require it explicitly:
require "capybara-screenshot"

That seems to fix it, so I guess it might be relying on cucumber being loaded when it might not be or something.

I've got this problem too with the same setup as @kerryb has. My guess is that this is related to the recent commit
https://github.com/mattheworiordan/capybara-screenshot/commit/0e7b4c6f8c3e7c0a4a027e1c16054f8a88ba024f
which manually requires 'capybara/cucumber'

Hi all
The problem was related to Cucumber World not being available, and me designing the gem with only Cucumber in mind. I've pushed up a fix which will remove the error, however automatic screen shots following an assertion failure in RSpec or Minitest won't happen as of now.  I'm not really sure how one can plug into RSpec or Minitest, catch a failure and then execute some action.  I'll look into it though and update this ticket when I've found a solution (or realised it's not possible).
Matt

Ryan (@zenspider), recently released a mintiest example plugin called mintiest-debugger. So following this example, you should be able to do what you need in a few lines of code.
https://github.com/seattlerb/minitest-debugger/blob/master/lib/minitest/debugger.rb#L24

Hi all
RSpec support is now working, introduced in this commit https://github.com/mattheworiordan/capybara-screenshot/commit/8ef64da29f5dfca7cd43a29fdbfa0dc5cc6a6b9e
I have bumped the Gem version to 0.1.2 so you will need to update.
However, I have not got MiniTest working as I'm pretty stumped just getting the MiniTest integration tests to run.  Can I ask someone to help me at least get my example Rails app running MiniTest integration tests, and I will take it from there.  If  you clone the app at https://github.com/mattheworiordan/capybara-screenshot-test-rails-3.1, and run rake test you will see that the tests fail each time saying /integration/basic_test.rb:1:in require': no such file to load -- test_helper (LoadError)`, and I can't seem to get around the issue.  I would appreciate someone's help with MiniTest so that I can add MiniTest support to the Gem.
Matt

I'll fork and take a look at the MiniTest stuff.

Thanks Metaskills, I used the first patch and that worked brilliantly.  Capybara-screenshot should now be working for Cucumber, RSpec and Minitest.
However, I did not use your second patch as it did not cover failures that were not caused by assert failures such as exceptions raised by Capybara.  As such, I rewrote this using teardown hooks, so a screen shot is captured if any error occurs now.
I've just seen you include name as part of the file name, I've not done this as I think in reality you typically only have one failing test, and also I'd need to get it working for Cucumber & RSpec too, that right now I don't have time for.
Feel free to fork and send a pull request though if you want to improve it.
Thanks,
Matt

However, I did not use your second patch as it did not cover failures that were
not caused by assert failures such as exceptions raised by Capybara

It should have, I tested it. That is what this code was for.
module Unit

  def self.included(base)
    base.class_eval do
      include InstanceMethods
      alias_method :puke_without_capybara_screenshot, :puke
      alias_method :puke, :puke_with_capybara_screenshot
    end
  end

  module InstanceMethods

    def puke_with_capybara_screenshot klass, meth, e
      if e.is_a?(Capybara::CapybaraError)
        Capybara::Screenshot::Saver.screen_shot_and_save_page Capybara, Capybara.body, meth
      end
      puke_without_capybara_screenshot klass, meth, e
    end

  end

end

Yes, that part of the code is right, but that code was predicated on it being called from your assert method.  The problem is that when a runtime error occurs, not as a result of an assert call, then assert never fails.  Hence I used the teardown hook which is executed at the end of each test regardless of whether assert was called.
module Assertions
     def assert test, msg = nil
       begin
         super
       rescue ::MiniTest::Assertion => e
         Capybara::Screenshot::Saver.screen_shot_and_save_page Capybara, Capybara.body, __name__
         raise e
       end
     end
end


added gird_pairs pair counter and tpcf code

compiles, passes tests, and runs on my machine.
Bolshoi like tpcf calcs take ~5 seconds.

The test suite passes on my machine as well. However, the sub-package does not import. In particular:
$ python setup.py build

from halotools import mock_observables

ImportError: No module named grid_pairs
@eteq - why would this be? The cython code seems to be compiling just fine after building it.

@duncandc - do you have this same problem? If you do the following:
$ git clean -dfx
$ python setup.py build

from halotools import mock_observables

Does your sub-package import?

This is because the setup_package.py script does not build it in place.  You have to either cd into the build directory, or go into mock_observables/pair_counters/grid_pairs/ and type: python setup_package.py build_ext --inplace

@eteq - is there not a workaround to this? That's kind of a pain in the neck to ask our users to do.

This is annoying...  Regular users wouldn't need to to this right?  When they install halotools, they will be working from a 'built' version.  Could we add a script to the setup.py file which builds the cython utilities in place?

Also, no need to merge this.  I already have an updated version.

Yup, agreed. This is too annoying to ask of regular users. It seems like the astropy package-template must have solved this compile problem, so let's just wait to hear what @eteq says.
I'll keep this PR open for discussion purposes only. We can close it when we get to the bottom of this.
Otherwise, the code looks pretty damn good - nice job.

Ok, @eteq - here is the summary of the status. From a clean version of the duncandc/mock_obs_devel branch (i.e., after running $ git clean -dfx), the code builds just fine with python setup.py build. And the test suite then runs just fine. However, when I attempt to import mock_observables, there is an ImportError.
I confirm the comment made by @duncandc above - if you just cd into mock_observables/pair_counters/grid_pairs and run $python setup_package.py build_ext --inplace, then that compiles just fine and the sub-package now imports.
How can we fix this so that the original, package-wide call to build the code from root correctly compiles all sub-package cython modules?

@aphearin and @eteq, so what's the deal?  I'm pretty bored over here, and could probably get something done...

Will check this out ASAP, hopefully tomorrow (for some reason this did trigger my notification e-mails like it normally does.  Probably something I did...)

@duncandc @aphearin - I can't reproduce the problem.  Here's what I do:

checkout a fresh testing branch
git reset --hard master - resets the branch to be exactly the same as master
git merge duncandc/mock_obs_devel - merges all of this branch's changes
python setup.py build
cd build/lib.macosx-10.10-x86_64-2.7
start python
from halotools import mock_observables
and it imports without any problem. This should reproduce exactly what users will see if they were to install using pip or python setup.py install, so if that probably the most important thing.

Alternatively, If I start from 4 and instead do  python setup.py build_ext --inplace and then run python and do from halotools import mock_observables it still imports without complaint.  I almost never use --inplace because it makes it easier to change the source code and then forget to re-compile (because the python code doesn't need to be recompiled), so I'm not 100% sure that's always reliable.  But definitely you should not use setup_package.py directly: if you're inside a sub-package it won't always know that something else has changed - you should always build from the root setup.py or else weird things can happen like stale linking at the C-level.

@eteq - great, thanks for checking on this.
First of all, I think all three of us confirm that your first sequence of operations works just fine. The problem was never something we were worried about for users, sorry if that wasn't clear. The problem was the nuisance of being a developer of a module that used cython.
So, suppose I was working on the pair-counting module, and I was making changes all the time, and with each change I was re-running the test suite. After each round of changes, what Duncan and I were doing was simply navigating to the root of the working directory, running $python setup.py build, and then opening up a python terminal from root and trying to import the mock_observables sub-package. This throws an error, because we were not using the --inplace flag. Neither of us knew about this. I think this solves the problem, though I will wait for @duncandc to confirm.
So now the question is just a matter of what workflow you recommend in such cases. When you're working on a section of Astropy in which you're heavily editing cython code, how do you like to operate? Do you just run $python setup.py build, and then cd into the build directory? Can you explain why you never use --inplace, I didn't quite follow your word of caution.
Anyway, I think now we know how to proceed, so @duncandc - just close this Issue if you agree that this is no longer a roadblock. But @eteq , it would be useful to get your advice on the day-to-day nuts and bolts developing a cython module since we'll be doing this a lot, and I assume that by now you must have an effective workflow for this.

Aha, I gotcha now, @aphearin.  My usual workflow when doing something cython-y where I want to play with it interactively is to have two terminals (or two tabs, usually): one is set to the root of the repo, and the other I cd into build/lib<whater> and start ipython.  When I make a change I want to see, I do python setup.py build in the first terminal and then do a reload(...) as necessary in the ipython session (or more often just exit and restart ipython because it's easier to be sure you didn't forget to reload something that way).
An alternative workflow is to use tests instead of an interactive session (if the particular work can be well-phrased as a quickly-running test). ``python setup.py test --args="-k test_function_name"  can be used to trigger a single test, and that way I don't have to come back and write a test later. I even wrote a sublime text build system to help automate that process.
As for why not to use --inplace, honestly I'm not sure it matters that much verses the first workflow I mentioned.  Occasionally --inplace gets confused and doesn't re-compile when you are jumping around between branches, or a few other situations I've not really entirely understood the cause of, requiring a git clean -dfx instead of an rm -rf build.  And if you're doing stuff with package data, using the source instead of the build directory might sometimes result in different paths or files not copied over to the build directory.  But none of that's really too big of a deal as long as your test suite checks these things.  I think I just like the "cleaness" of testing on the same thing the final resulting package will give, but it probably isn't really objectively that much better.

@aphearin I'm still working on an update to this module.  If needed, the this pull request can be merged and used, and I will update it ASAP.


These barely work

This list must be horrifically out of date.  Of all the proxy lists on GitHub, this is the one with the least working hits.
I got single digit hits with this list after checking over 10,000 entries.

Proxies are automatically checked every 5 minutes before posting. However, there's something you need to know. Most proxies are not installed on dedicated servers, so sometimes they may not be reachable. Proxies work on machines that connect from different locations, such as China, Pakistan, the USA, Vietnam, etc. Some ISP policies may cut off connection requests from different regions, so please consider peak times. Each proxy server has connection limitations, and most of them work on a first-in, first-out strategy.
Also, while working with proxies, I encountered too many strange things. Not every script configuration can connect to every proxy server.
If you don't mind, could you please share the purpose of your code or software configuration that you are using to reach the proxies?

https://checkerproxy.net/ You can use it to check the list


fix: npm i --save-dev eslint-config-next

updates eslint-config-next and seems to address the lint config issue?

It worked


docs: import sequence in the example

What this PR does is to import the sequence in the example that is mentions it

Thanks!


[sql error] infinite loading

I am stuck at the loading page. No pop up for signing in

Same issue for me. Posting by another user over here, too: https://aur.archlinux.org/packages/notion-app/#comment-838403

Same issue for me. Form mx19.4 , i try use form deb package and appimage

Isn't this the same issue as the autoupdater failing?

I'm not sure of this--and I'm not sure it's helpful, but it happened the other day right after I got an arch update of electron from the standard repos. Next boot, I lost the ability to access data from the desktop application. Online/ web access is fine, of course. It could have been another package update than electron I suppose.

I have the same issue, using this package via Arch AUR. Here is what I'm guessing the relevant error in text format:
Uncaught (in promise) SqliteSchemaMismatch: schema failed validation: schema.tables.notion.columns[0].type should be `"integer"`, instead was `"INTEGER"`.
    at h (notion://www.notion.so/app-52b0952….js:1:5138217)
    at te (notion://www.notion.so/app-52b0952….js:1:3525469)
    at Q (notion://www.notion.so/app-52b0952….js:1:3522551)
    at async se.ensureMigrated (notion://www.notion.so/app-52b0952….js:1:3526339)
    at async Module.ie (notion://www.notion.so/app-52b0952….js:1:331986)
    at async notion://www.notion.so/app-52b0952….js:1:3494439

2021-12-07T11:26:26.008Z [info] sqliteSchemaHelpers: attemptMigration:  Attempting migration from 19 to 20
2021-12-07T11:26:26.057Z [info] sqliteSchemaHelpers: successfulMigration:  Successfully migrated to 20 Object

It also logs this right before the error, possibly relevant.

I'm having the same issue with the AUR package and can confirm it's not the same issue as https://github.com/notion-enhancer/notion-repackaged/issues/37 . LMK if i can help with some logs / additional information

Same issue no activity in network tab also


go get github.com/tsuna/gohbase/region get error

github.com/go-logr/logr/funcr
/root/go/src/github.com/go-logr/logr/funcr/funcr.go:398:16: undefined: strconv.FormatComplex
/root/go/src/github.com/go-logr/logr/funcr/funcr.go:400:16: undefined: strconv.FormatComplex
/root/go/src/github.com/go-logr/logr/funcr/funcr.go:443:16: undefined: strconv.FormatComplex
/root/go/src/github.com/go-logr/logr/funcr/funcr.go:445:16: undefined: strconv.FormatComplex

strconv.FormatComplex was added in go1.15. Our go.mod file requires at least go1.13. May need to bump that up. But first I need to find where github.com/go-logr/logr is actually used.

Which version of go are you using?

Works as expected with go1.13 https://github.com/tsuna/gohbase/pull/184. You can also see in the build logs that github.com/go-logr/logr isn't imported. So not sure how you got that error.
Please send more reproducible step and information.

Closing for inactivity


logging errors as info wasn't working so upgrading it to a warning, especially this is mostly a serious issue that the user should know about

ref https://github.com/developmentseed/cogeo-mosaic/issues/35#issuecomment-593630485
closes #39

Thanks @andrewharvey this is really appreciated. Did you test this ?

Yeah I did test it, after changing this it logged the S3 error.

I'll take your work on this :D, I'll merge to master for now but I'll see if we can make other change before doing a release
Thanks a lot!


bower install fails on version 14.2 of angular-ui-select

I have the following entry in bower.json under dependencies which fails -
"angular-ui-select": "~0.14.2"
Tried changing the version to 14.1 and then to 13.2 but all fail to install. Finally version 13.1 worked. Any idea what's the issue?
The version of bower installed is 1.7.7

I think PR #812 might be relevant here too...

When I install versions 0.14.0 and upwards some unrelated controller karma test suddenly fails.
Using 0.13.2 all tests pass. But unfortunately keyboard navigation is broken.
Command:
bower cache clean
bower install angular-ui-select#0.14.2 --save

I realized my company has an internal Artifactory and hence 'bower install' was looking into the internal artifactory, not at Heroku's bower.io. Setting a proxy in Environmental variables resolved that issue for me.
@cmousset - That's a good suggestion too! Thanks.


Implement first version of GraphQL server

3975 RUB reward can be claimed by anyone who completes this task.
This task is continuation of https://github.com/Konard/LinksPlatform/issues/571

i took this task

https://hasura.io/docs/latest/graphql/core/guides/export-graphql-schema.html - tools for schema export

Rewards are:
6000 RUB for @FirstAfterGod2501
4000 RUB for @FreePhoenix888


Update react-windowed-select in order to solve "window is undefined" in Next.js

What:
This package cannot be used in Next.js projects because of error "window is undefined".
Why:
Closes #209

How:
Wave uses react-windowed-select, which uses react-select. "window is undefined" actually occurs in react-select, but was resolved and backported to react-windowed-select.
Currently, Wave uses react-windowed-select@2x which points to<EMAIL_ADDRESS>Meanwhile<EMAIL_ADDRESS>which fixed this problem  uses<EMAIL_ADDRESS>Despite major version has been increased, I believe that upgrade is seamless. Take a look at the release notes of<EMAIL_ADDRESS>The only breaking change is emotion related: "The NonceProvider component now requires a cacheKey prop that corresponds to the key for the Emotion cache.".
Another things that react-windowed-select@3x shipped are:

react-window patch version update
peer deps to add support for React 17
dev dep minor/patch versions

Also, I don't see some visual regression with SelectList component, and tests have passed.
Checklist:

[ ] Ready to be merged

Hmmm, it breaks documentation building (as here)

Converted to Draft since there are bundling issues in react-windowed-select that must be fixed before

Do you see any other option? The bundling issue is there for quite a long time and I was considering either to fix it or just migrate to something more supported

@nlopin I've created a pull request to the library that fixes this issue.
But of course we don't know when it will be merged.
Another reason is to publish your own package within @freenow/react-windowed-select with the fix until it will be merged in the upstream repository.

I have good news and bad news.
Good news is that my PR in react-windowed-select has been merged.
Bad news is that right after that PR with upgrading react-select to v5 has been also merged and both these changes have been released at once.
The problem is that v5 version of react-select came with a lot of changes:

Dropped IE11 support. As far as I know, Wave supports IE11.
Completely rewritten with TypeScript + some breaking changes. I've faced a lot of TS errors when tried to build Wave with the package. Of course that's not the problem, but I decided not to spent my time solving it without clarifying IE11 status.

The good news that author of react-windowed-select released 5.0.0 after 3.x, so it's possible to release only my fix as 4.0. I asked the author about that. Let's wait for his reponse.

I've got some news here!
The author of the react-windowed-select published intermediate version of the package (with my bundling fix, but before upgrading to react-select@5).
The package now works fine in Next.js (and other Node.js environments such as Gatsby or so) 🎉
But there are some additional problems, that I tried to fix:

disabledStyles.control(...) at src/components/SelectList/styles.ts:7 receives the only argument - SelectListProps, but it's called this way: disabledStyles.control({ isFocused: state.isFocused, ...state.selectProps }) - isFocused isn't used there and don't exist in argument's props. And therefore TypeScript shows error there because object literals can't have unknown fields. (Actually, I don't understand, how it worked before but anyway). So, I decided to remove isFocused in disabledStyles.control(...) and errorStyles.control(...) since it's not used.
What's more important - in src/components/SelectList/styles.ts type CSSObject picked from styled-components, but used widely as CSSObject from emotion. And their types now are slightly different (alignContent is string literal union in emotion, but in SC it's a just string). It's not a problem for functions that return result only for react-select (e.g. for emotion), but disabledStyles.label is used also in styled-components context at src/components/SelectList/components/Label.tsx:28.
Here, I can't just pass p variable to label(props...) as props variable. So I limited fields:  label: (props: Pick<SelectListProps, 'variant' | 'size'>): CSSObject => {. It's also more explicit, IMHO.
❗ Updated react-select now adds role="combobox" to input. I've updated tests, but I'm not sure, can this broke something in your projects (But it shouldn't - role="combobox" fits here well)
❗ Extending emotion component with styled-components conflicts at theme prop. (src/components/PhoneInput/PhoneInput.tsx:71, src/components/PhoneInput/components/Option.tsx and src/components/PhoneInput/components/SingleValue.tsx). Actually, I don't know how to solve this better, I just suppressed TS errors on that lines for now. I haven't noticed any differences in actual values, it seems that SC overrides the type of source component's theme prop but shouldn't.

I'm not sure how can I verify that, YOLO 😄

I've checked on a dummy next.js project and it worked well


IMAP: Remove unnecessary calls to RealImapFolder.open()

Change methods in RealImapFolder that perform a remote operation to never call open() themselves. It's up to the caller to make sure those methods are called on an open folder.
This doesn't significantly change the behavior of the app. In some cases we now avoid calling open() on an already open RealImapFolder, which triggered sending a NOOP command. So it removes a tiny bit of unnecessary network I/O, but not a lot.

I'll change it to requireOpen in a follow-up PR were the method also checks the required open mode. Some methods only require read access, others read-write access.


DiscussionWasViewed properties should be public

DiscussionWasViewed has private properties, so when I set listener on this event, I don't have any access to values.

Sorry for the delay here. I'll adjust this oversight in the upcoming beta 16 release. Thanks!


Add prefer-page-locator-fill

This rule detects where page.fill(loc, value) has been used and suggests the user uses a locator based fill as per the documentation for page.fill
https://github.com/microsoft/playwright/blob/d1926e2f9b91e31d73acfb87e564634f55b0dbb2/docs/src/api/class-page.md?plain=1#L2027

NOTE Use locator-based locator.fill(value[, options])
instead. Read more about locators.

This rule should be more generic for all page actions that are like it.  For example click is the same exact way

This rule should be more generic for all page actions that are like it. For example click is the same exact way

Looks like their a quite a few Page methods tagged with NOTE Use locator-based now that you mention it

click
dblclick
dispatchEvent
focus
getAttribute
hover
innerHTML
innerText
inputValue
isChecked
isDisabled
isEditable
isEnabled
isHidden
isVisible
press
selectOption
setChecked
setInputFiles
tap
textContent
uncheck

I'll extend it to those

This also closes https://github.com/playwright-community/eslint-plugin-playwright/issues/197


feature(Build): Add Automation for Github Releases Pages

Closes: #42

Test-Release: https://github.com/boschglobal/kuksa-android-sdk/releases


Readme documentations updates and additions

This change fixes a small typo around the shell prompt and adds
some futher tweaks based on my onw testing / run through
Note that line 81 requires the root namespace, e.g:
kubectl get taskrun.tekton.dev/taskrun home-is-set-rwhzs

Thanks!

/approve

/lgtm


Glasscat tests

Improve GlassCat test coverage and introduce wrappedalloc macro to avoid issues with counting allocations in global scope.

Codecov Report

Merging #152 (edf90a8) into main (3dbe82a) will increase coverage by 2.32%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #152      +/-   ##
==========================================
+ Coverage   49.85%   52.18%   +2.32%
==========================================
  Files          64       64
  Lines        6416     6268     -148
==========================================
+ Hits         3199     3271      +72
+ Misses       3217     2997     -220

Impacted Files
Coverage Δ

src/GlassCat/GlassTypes.jl
43.33% <ø> (+34.46%)
:arrow_up:

src/GlassCat/Air.jl
100.00% <0.00%> (+55.55%)
:arrow_up:

src/GlassCat/search.jl
65.51% <0.00%> (+65.51%)
:arrow_up:

Continue to review full report at Codecov.

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

@BrianGun I think these changes are ready for approval, if you're happy with them. The wrapped allocations fix is worth a read for future reference.


Fix gitattributes path in README

From this SO answer, the default user level gitattributes path should be ~/.config/git/attributes.

ugh, you're right- definitely typo'd that one. Thanks for picking up on it!
also cc @probablycorey


[FEATURE] Kyuubi Restful API Kerberos authentication support

Code of Conduct

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

Search before asking

[X] I have searched in the issues and found no similar issues.

Describe the feature
Support the kerberos authentication for restful front end server.
Motivation
No response
Describe the solution
No response
Additional context
No response
Are you willing to submit PR?

[X] Yes I am willing to submit a PR!

@turboFei 👍


Sandpack bundler connection issue

Bug report
Packages affected

[ ] sandpack-bundler

Unable to establish connection with the sandpack bundler. Make sure you are online or try again later.
Unable to view the output's in the code sandbox present in the documentation "react-beta"

Link to sandbox: link (optional)
Your Environment

Software
Name/Version

Sandpack-client version

Sandpack-react version

Browser

Operating System

Hey, could you please provide more information about this issue? Is there any link to reproduce this error or any other information?

@danilowoz It's possible that it was a hiccup due to some UNPKG issues, see https://github.com/codesandbox/sandpack/discussions/706
It would be nice to be able to detect such issues in order to handle them gracefully.


Trying to add foss to db.json

Changes proposed
Added the abbreviation for Free Open Source Software.

Check List (Check all the applicable boxes)

[x] My code follows the code style of this project.
[ ] My change requires changes to the documentation.
[x] I have updated the documentation accordingly.
[x] All new and existing tests passed.
[x] This PR does not contain plagiarized content.
[x] The title of my pull request is a short description of the requested changes.

Screenshots

Note to reviewers

Sigh, Sorry for the trouble.

Sigh, Sorry for the trouble.

No worries! BOOM. This one passed. No need to apologise.

Thank you for your support!!


Library Mode

Is your feature request related to a problem? Please describe.
Right now, Perla only tries to work with websites, i.e. the main entry point  is an index.html file, but if you want to develop a library this won't be that useful, you don't really need that index file, you only need an exported file and possibly a package.json file to deploy to npm afterwards
Describe the solution you'd like
Allow in the configuration to build/serve in library mode, where the index file is used as a mere demo and the entry point is built as is with esbuild, ideally we should also emit a package.json file with the dependencies and corresponding declarations about modules and esm sources.

For the moment there is no plan to continue this part, if someone feels like adding support for this I'm all in


Support mapping from a DTO to an object's factory create method

Domain Driven Design is becoming more and more popular and it's common to use a Create Factory method to create objects that have more validation requirements than can be added within just a contractor.
The proposal is to configure the mapping method to specify the factory method needed for object creation, such as in the below:
[Mapper]
public partial class CountryMapper
{
    [MapToFactoryMethod(typeof(Country), nameof(Country.Create))]
    public partial Country MapDtoToCountry(CountryDto dto);
}

Presently this must be performed as below, specifying all fields, which negates the use of a mapper.
[Mapper]
public partial class CountryMapper
{
    public partial Country MapDtoToCountry(CountryDto dto)
    {
        return Country.Create(dto.Code, dto.Name, dto.Continent);
    }
}

Mapster has this feature (albeit using reflection and not source generation) but Mapster is no longer maintained.  I feel this is the missing feature to make Mapperly the new defacto standard for dotnet.

This could be implemented but I think a simple property on the ObjectFactoryAttribute should do the job (bool MapToParameters). Feel free to contribute 😉


ContentMathML: too many empty elements are causing trouble in subscripts

From the User Group.
<math display="block">
    <msub>
        <ci>x</ci>
        <ci>
            <apply>
                <plus></plus>
                <ci>n</ci>
                <cn>1</cn>
            </apply>
        </ci>
    </msub>
</math>

gives
<math xmlns="http://www.w3.org/1998/Math/MathML" display="block">
  <msub>
    <mi>x</mi>
    <mi></mi>
    <mi></mi>
    <mrow>
      <mrow>
        <mi>n</mi>
        <mo>+</mo>
        <mn>1</mn>
      </mrow>
    </mrow>
  </msub>
</math>

I wonder where those  are coming from!

I think the <ci> around the <apply> is wrong - <ci> should be used to represent a single variable, but here it's enclosing an addition. If you get rid of it, the expression is rendered correctly.

Argh -- I did not check validity :-( Closing this.


ACT-W National Conference - April 2018 - (Advancing The Careers of Technical Women)

ACT-W National Conference - Presented by ChickTech, ACT-W National focuses on providing you with inspiring and actionable education in career development, leadership, technology, and diversity.

I already have added this reference to the list, so we can close this PR. Thank you for your contribution! 😄💖


Added support for app registration, keyvault certificates key & misc bug fixes

PR Checklist

[x] I have added example(s) inside the [./examples/] folder
[x] I have added the example(s) to the integration test list for normal (~30 minutes) or long runner >30 minutes
[x] I have checked the coding conventions as per the wiki
[x] I have checked to ensure there aren't other open Pull Requests for the same update/change?

Description

Added support for one application to be able to reference another application by key and its oath2_permission_scope_id
Added support for application certificate to be able to reference a keyvault certificate via remote_objects key
Added application support for a list of
a) oauth2_permission_scopes
b) app_roles
c) access_tokens
d) id_tokens
e) public_clients
f) required_resources_access & resources_access
Fixed & Enhanced examples/azuread_graph/107-azuread_applications
Added new examples/azuread_graph/109-azuread_application_certificates

Does this introduce a breaking change

[ ] YES
[x] NO

Testing
Execute examples/
a) azuread_graph/107-azuread_applications
b) azuread_graph/109-azuread_application_certificates

@arnaudlh , @LaurentLesle, I submitted this PR and wondered if you need more information about all the changes we introduced.
We are actively using those changes and hope they would make it to your branch and eventually to the main branch.  Please let us know if we can help to get this reviewed and hopefully merged soon.  Thanks, Janet.


Set up React and Express

Set up React and Express
Set up the relevant scripts in package.json (e.g. "start", "dev")

Initial thoughts is that this would be using concurrently so we can run both servers at the same time - do you agree @marwajomaa ?

@thejoefriel  yeah, I think we need both for client and server sides

PS, what is your suggested way of setting these up together in order that we can do testing and ensure codecov? Are you thinking setting it up in two repos within our main repo?

Great. How's it going? Will you be ok to push this up today or still need to work on this tomorrow
I'll try to prepare it by the end of the day, but it's may take me more time to make sure that everything is perfect, so I think tomorrow morning before the stand-up meeting it will ready.

PS, what is your suggested way of setting these up together in order that we can do testing and ensure codecov? Are you thinking setting it up in two repos within our main repo?

Yeah; I'll make a separate folder for each side then I'll join them together using proxy. Is that make sense for you?

Hey @marwajomaa you ok to tick the check boxes on this and close this issue please?
That will then move it to done here: https://github.com/techforbetter/connect5/projects/2

Ok done


test: fix cleanup ds in fixtures

SUMMARY
Remove datasource in cleanup section in world bank and birth names fixtures
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TEST PLAN

ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Changes UI
[ ] Requires DB Migration.
[ ] Confirm DB Migration upgrade and downgrade tested.
[ ] Introduces new feature or API
[ ] Removes existing feature or API

Codecov Report

Merging #12762 (f851229) into master (6bf5d2c) will decrease coverage by 25.37%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           master   #12762       +/-   ##
===========================================
- Coverage   66.93%   41.56%   -25.38%
===========================================
  Files        1022      438      -584
  Lines       50051    14665    -35386
  Branches     4915     3902     -1013
===========================================
- Hits        33500     6095    -27405
+ Misses      16426     8570     -7856
+ Partials      125        0      -125

Flag
Coverage Δ

cypress
41.56% <ø> (-9.32%)
:arrow_down:

javascript
?

python
?

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

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

Codecov Report

Merging #12762 (f851229) into master (6bf5d2c) will decrease coverage by 25.37%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           master   #12762       +/-   ##
===========================================
- Coverage   66.93%   41.56%   -25.38%
===========================================
  Files        1022      438      -584
  Lines       50051    14665    -35386
  Branches     4915     3902     -1013
===========================================
- Hits        33500     6095    -27405
+ Misses      16426     8570     -7856
+ Partials      125        0      -125

Flag
Coverage Δ

cypress
41.56% <ø> (-9.32%)
:arrow_down:

javascript
?

python
?

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

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

Hey! Could you look at it? @willbarrett @dpgaspar

Hey! Could you look at it? @willbarrett @dpgaspar

Looking good! Needs one more rebase then it'll be ready to merge.


Document requirements for "linkerd-compatible" services

For HTTP, that means forwarding L5d-* and Dtab-* headers.

FWIW I wouldn't call this "compatible". All services are linkerd compatible if they speak HTTP, thrift, mux, etc. It's only if you want extended capabilities like distributed tracing and per-request routing that you have to do header forwarding.
But I agree it should be documented.

https://linkerd.io/doc/0.7.0/linkerd/protocol-http/#http-headers - I think this can be closed now, if I've understood the ask correctly.

Yeah, I think so. Closing. (BTW we're changing some of these headers in the next release.)


option to serialize attributes as camelCase instead of kebab-case

Trying to incorporate Saule into an existing project with strict guidelines, including a convention of ID instead of Id.
API
public class VideoResource: ApiResource
{
    public VideoResource()
    {
        WithId(nameof(Video.ID));

        // problem 1 - AccountID translates to 'account-i-d' instead of 'account-id'
        Attribute(nameof(Video.AccountID));
    }
}

Response
{
  "data": [
    {
      "type": "video",
      "id": "385",
      "attributes": {
        "account-i-d": 9
      }
    }
  ]
}

I read somewhere that the JSON API spec calls for the use of kebab-case for attributes but kebab-case is difficult to consume and work with-in Javascript.  Is there a way that I can override the attribute serializer/deserializer to use camelCase instead of kebab-case?

I think this is really two issues:

You don't follow recommended C# naming conventions that Saule relies on.
Saule normalizes all names to make sure everything is consistent, but doesn't allow any customization of this process.

I am a bit reluctant to fix 1 in Saule, specifically because C# naming conventions are very typically followed by the community and enforced by tools like FxCop and Resharper. I suppose both could be addressed by allowing people to provide a "normalizer" on the JsonApiConfiguration object (similar to IUrlPathBuilder):
interface IPropertyNameConverter
{
    string ToModelPropertyName(string name);
    string ToJsonPropertyName(string name);
}

Note that this does not provide any context, because sometimes names must be normalized without that; for example properties provided in query parameters in the url.
The default implementation would looks something like this (probably would need some more things, like trimming whitespace):
class DefaultPropertyNameConverter : IPropertyNameConverter
{
    public virtual string ToModelPropertyName(string name)
    {
        return name.ToPascalCase();
    }

    public virtual string ToJsonPropertyName(string name)
    {
        return name.ToDashed();
    }
}

Internally Saule would always use this interface instead of the current extension methods. This is likely a big-ish refactor because the configuration object is not always available.


Discrepancies Between Genome Sequences from BED Coordinates and tfrecords in Basenji Dataset

I have identified discrepancies between the sequences extracted from the hg38.ml.fa reference genome using BED file coordinates and those stored in the tfrecords within the Basenji dataset hosted on Google Cloud (https://console.cloud.google.com/storage/browser/basenji_barnyard?pageState=("StorageObjectListTable":("f":"%255B%255D"). This inconsistency is concerning as it affects the reliability of our data used for genomic analyses.
Detailed Observations:

I retrieved sequences using the sequences.bed file from the hg38.ml.fa reference genome.

Upon comparing these sequences with those recorded in the tfrecords dataset, I discovered mismatches. For example, in the validation set for human data, only two samples had sequences that matched their coordinates.

Questions:

What could be causing these discrepancies between the retrieved sequences and those in the tfrecords?

How is the hg38.ml.fa genome processed, and how does it differ from the standard reference genome?

Any assistance or guidance on how to verify the consistency of the data in the Google Cloud repository would be greatly appreciated.

If it's convenient for you, could you please review the logic I used to test if the sequences are identical? My h5 files have all been converted from tfrecords, such that they should be exactly the same. I used the BED files and genome that you provided, but in the end, only two samples in the validation set had matching sequences.
import h5py
import torch
from torch.utils.data import Dataset
import numpy as np
from Bio import SeqIO
import pandas as pd
from tqdm import tqdm

ENFORMER_INPUT_LENGTH = 196_608
BASENJI_INPUT_LENGTH = 131_072

class H5Dataset(Dataset):
    def __init__(self, h5_file_path, genome_dict, df):
        self.h5_file = h5py.File(h5_file_path, 'r')
        self.sequences = self.h5_file['sequences']
        self.targets = self.h5_file['targets']
        self.genome_dict = genome_dict
        self.df = df

    def __del__(self):
        self.h5_file.close()

    @staticmethod
    def decode_one_hot(one_hot_encoded):
        """
        Decode one-hot encoded sequence to string.
        """
        mapping = np.array(['A', 'C', 'G', 'T', 'N'])
        indices = np.argmax(one_hot_encoded, axis=1)
        all_zeros = np.all(one_hot_encoded == 0, axis=1)
        indices[all_zeros] = 4
        return ''.join(mapping[indices])

    def __len__(self):
        return len(self.targets)

    def __getitem__(self, idx):

        # Directly read sequences provided by Basenji
        sequence_h5 = self.decode_one_hot(self.sequences[idx])
        target = torch.tensor(self.targets[idx], dtype=torch.float32)

        # Retrieve sequence from genome with coordinates provided by Basenji
        row = self.df.iloc[idx]
        chrom, start, end = row["chrom"], row["start"], row["end"]
        sequence = str(self.genome_dict[chrom].seq[start:end]).upper()

        if sequence == sequence_h5:
            self.equal_count += 1
        else:
            self.unequal_count += 1

        # Extend sequence to match Enformer input length
        median = (start + end) // 2
        enformer_start = median - ENFORMER_INPUT_LENGTH // 2
        enformer_end = median + ENFORMER_INPUT_LENGTH // 2
        enformer_sequence = str(self.genome_dict[chrom].seq[enformer_start:enformer_end]).upper()

        return {
            'sequence': enformer_sequence,
            'target': target,
        }

if __name__ == '__main__':
    # Dataset paths
    bed_path = "/blob/Data/human/sequences.bed"
    genome_path = "/blob/Data/DNA/Caduceus/hg38/hg38.ml.fa"
    train_h5_path = "/home/aiscuser/data/enformer_h5/basenji/human_train.h5"
    valid_h5_path = "/home/aiscuser/data/enformer_h5/basenji/human_valid.h5"
    test_h5_path = "/home/aiscuser/data/enformer_h5/basenji/human_test.h5"
    # Load genome
    genome_dict = SeqIO.to_dict(SeqIO.parse(genome_path, "fasta"))
    # Load bed file
    df = pd.read_csv(bed_path, sep="\t", header=None)
    df.columns = ["chrom", "start", "end", "split"]
    train_df = df[df["split"] == "train"].reset_index(drop=True)
    valid_df = df[df["split"] == "valid"].reset_index(drop=True)
    test_df = df[df["split"] == "test"].reset_index(drop=True)
    # Load datasets
    train_dataset = H5Dataset(train_h5_path, genome_dict, train_df)
    valid_dataset = H5Dataset(valid_h5_path, genome_dict, valid_df)
    test_dataset = H5Dataset(test_h5_path, genome_dict, test_df)
    # Check if sequences are equal
    for i, sample in enumerate(tqdm(test_dataset)):
        targets = sample["target"]
        max_value = targets.max().item()
        min_value = targets.min().item()
        test_max = max(test_max, max_value)
        test_min = min(test_min, min_value)
    print(f"Equal count: {test_dataset.equal_count}, Unequal count: {test_dataset.unequal_count}")

I'm not sure that I completely understand what you're doing here. But I can assure you the sequences in the tfrecords match the hg38/m10 reference genomes. My ".ml" versions only remove chromosomes that I don't want to train on. My best guess for why you're seeing a problem is that the tfrecords contain 131072 length sequences, but Ziga trained Enformer by further extending the sequences. If that's not it, I'd convert your sequences to DNA and blat via UCSC to track down the discrepancy.

I'm not sure that I completely understand what you're doing here. But I can assure you the sequences in the tfrecords match the hg38/m10 reference genomes. My ".ml" versions only remove chromosomes that I don't want to train on. My best guess for why you're seeing a problem is that the tfrecords contain 131072 length sequences, but Ziga trained Enformer by further extending the sequences. If that's not it, I'd convert your sequences to DNA and blat via UCSC to track down the discrepancy.

Thank you for your quick response. I would like to ask if the one-hot encoded sequences stored in your TFRecord are consistent with the encoding format described in the Enformer paper?
I am not sure if I am decoding these one-hot vectors correctly (I am using the 131k bed file and TFRecord you provided for comparison, so the lengths are consistent).

I may have found the issue. It appears that the order of the data in the bed file does not correspond with the order in the TFRecords. For example, the second training data entry in the TFRecords corresponds to the 256th line in the bed file.


⚠ T:Riza Roblox Proxy has degraded performance

In 3ab55d0, T:Riza Roblox Proxy (https://rprxy.triza.dev) experienced degraded performance:

HTTP code: 200
Response time: 2714 ms

Resolved: T:Riza Roblox Proxy performance has improved in de76189.


Can't decode reponse content by flow.response.get_content(False)

Problem Description
Try to add  addons script to get server response , then  failure to  decode the response content . But found the mitmweb page  can present the correct response , pls refer to the following  script and snapshot :
SCRIPT:
def response(self, flow: mitmproxy.http.HTTPFlow):
if  flow.request.path.startswith("xxxxxxxxx"):
data = flow.response.get_content(False)
print("############# THE RESPONSE : " + str(data))
response:

response content in mitmweb:

Steps to reproduce the behavior:

System Information
mitmproxy version : 6.0.2
python : 3.8.10
platform : macOS Catalina 10.15.5

This looks correct to me. What you are seeing in mitmweb is the pretty-printed version of a protobuf message. flow.response.get_content(False) just gets you the raw protobuf message. Does that clear up things?

Thanks to you quick reply .  Try to so much times  to decode the response , still cann't interpreter the content .

https://github.com/mitmproxy/mitmproxy/blob/main/mitmproxy/contentviews/protobuf.py should be the right place. :)


Why a vendor_id is associated with several different vendors.COUNT(trips)?

This question is for NYC Taxi 3 - Simple Featuretools.
I run this command:
feature_matrix.groupby(['vendor_id','vendors.COUNT(trips)']).size()

get the following output. Can you explain how FT comes up with these different counts for each vendor_id? Or this is a bug with FT?
vendor_id  vendors.COUNT(trips)
1          0                        52301
           52301                   181675
           233976                  196150
           430126                  195433
           625559                  191159
           816718                  138047
2          0                        61152
           61152                   211531
           272683                  226281
           498964                  223220
           722184                  217368
           939552                  155949

The reason you are getting multiple trip counts for a single vendor_id is because of the cutoff times that are being supplied to dfs. In short, by passing the cutoff time dataframe, we are telling dfs to calculate features at multiple points in time.
If you remove the cutoff time parameter from dfs, the current time will be used as a single cutoff time, and you will see a single COUNT returned for each vendor.
More on cutoff times from the Featuretools docs

Thanks for explanation!


net-cygwin crashes in megampi

Original issue: https://charm.cs.illinois.edu/redmine/issues/1289

No body.

Original date: 2017-02-14 21:44:29

The net-cygwin target is no longer relevant.


Resolved disallowed-html-tag build warnings

Docs Build status updates of commit a48f191:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

azps-0.10.0/Az.Network/Get-AzVirtualNetworkGatewaySupportedVpnDevice.md
:x:Error

Details

azps-7.5.0/Az.Network/Get-AzVirtualNetworkGatewaySupportedVpnDevice.md
:x:Error

Details

azps-8.0.0/Az.Network/Get-AzVirtualNetworkGatewaySupportedVpnDevice.md
:x:Error

Details

azps-0.10.0/Az.KeyVault/Backup-AzKeyVaultSecret.yml
:warning:Warning

Details

azps-0.10.0/Az.KeyVault/Get-AzKeyVaultSecret.yml
:warning:Warning

Details

azps-0.10.0/Az.KeyVault/Remove-AzKeyVaultSecret.yml
:warning:Warning

Details

azps-0.10.0/Az.KeyVault/Restore-AzKeyVaultSecret.yml
:warning:Warning

Details

azps-0.10.0/Az.KeyVault/Undo-AzKeyVaultKeyRemoval.yml
:warning:Warning

Details

azps-0.10.0/Az.Network/Add-AzApplicationGatewayAuthenticationCertificate.yml
:warning:Warning

Details

azps-0.10.0/Az.Network/Add-AzApplicationGatewayBackendAddressPool.yml
:warning:Warning

Details

azps-0.10.0/Az.Network/Add-AzApplicationGatewayFrontendIPConfig.yml
:warning:Warning

Details

azps-0.10.0/Az.Network/Add-AzApplicationGatewayFrontendPort.yml
:warning:Warning

Details

azps-0.10.0/Az.Network/Add-AzApplicationGatewaySslCertificate.yml
:warning:Warning

Details

azps-0.10.0/Az.Network/Add-AzExpressRouteCircuitAuthorization.yml
:warning:Warning

Details

azps-0.10.0/Az.Network/Add-AzLoadBalancerBackendAddressPoolConfig.yml
:warning:Warning

Details

azps-0.10.0/Az.Network/Add-AzNetworkInterfaceIpConfig.yml
:warning:Warning

Details

azps-0.10.0/Az.Network/Add-AzRouteConfig.yml
:warning:Warning

Details

azps-0.10.0/Az.Network/Add-AzVirtualNetworkGatewayIpConfig.yml
:warning:Warning

Details

azps-0.10.0/Az.Network/Add-AzVirtualNetworkSubnetConfig.yml
:warning:Warning

Details

azps-0.10.0/Az.Network/Get-AzApplicationGatewayAuthenticationCertificate.yml
:warning:Warning

Details

azps-0.10.0/Az.Network/Get-AzApplicationGatewayConnectionDraining.yml
:warning:Warning

Details

azps-0.10.0/Az.Network/Get-AzApplicationGatewayFrontendPort.yml
:warning:Warning

Details

azps-0.10.0/Az.Network/Get-AzApplicationGatewayHttpListener.yml
:warning:Warning

Details

azps-0.10.0/Az.Network/Get-AzApplicationGatewayIPConfiguration.yml
:warning:Warning

Details

azps-0.10.0/Az.Network/Get-AzApplicationGatewayRequestRoutingRule.yml
:warning:Warning

Details

This comment lists only the first 25 files in the pull request.

azps-0.10.0/Az.Network/Get-AzVirtualNetworkGatewaySupportedVpnDevice.md

Line 0, Column 0: [Error: MAML2Yaml_LoadFileFailed]

Failed to load file: C:/LocalRun/W/yovo-s/azps-0.10.0/Az.Network/Get-AzVirtualNetworkGatewaySupportedVpnDevice.md:31:(186) '```
<?xml version="1.0" encoding="utf-8"?>
<RpVp...'
 Expect Heading, please try to use PlatyPS validate the content

azps-7.5.0/Az.Network/Get-AzVirtualNetworkGatewaySupportedVpnDevice.md

Line 0, Column 0: [Error: MAML2Yaml_LoadFileFailed]

Failed to load file: C:/LocalRun/W/yovo-s/azps-7.5.0/Az.Network/Get-AzVirtualNetworkGatewaySupportedVpnDevice.md:37:(290) '```
<?xml version="1.0" encoding="utf-8"?>
<RpVp...'
 Expect Heading, please try to use PlatyPS validate the content

azps-8.0.0/Az.Network/Get-AzVirtualNetworkGatewaySupportedVpnDevice.md

Line 0, Column 0: [Error: MAML2Yaml_LoadFileFailed]

Failed to load file: C:/LocalRun/W/yovo-s/azps-8.0.0/Az.Network/Get-AzVirtualNetworkGatewaySupportedVpnDevice.md:34:(186) '```
<?xml version="1.0" encoding="utf-8"?>
<RpVp...'
 Expect Heading, please try to use PlatyPS validate the content

azps-0.10.0/Az.KeyVault/Backup-AzKeyVaultSecret.yml

Line 16, Column 9: [Warning: file-not-found - See documentation] Invalid file link: './Set-AzKeyVaultSecret.yml'.

azps-0.10.0/Az.KeyVault/Get-AzKeyVaultSecret.yml

Line 18, Column 9: [Warning: file-not-found - See documentation] Invalid file link: './Set-AzKeyVaultSecret.yml'.

azps-0.10.0/Az.KeyVault/Remove-AzKeyVaultSecret.yml

Line 17, Column 9: [Warning: file-not-found - See documentation] Invalid file link: './Set-AzKeyVaultSecret.yml'.

azps-0.10.0/Az.KeyVault/Restore-AzKeyVaultSecret.yml

Line 15, Column 9: [Warning: file-not-found - See documentation] Invalid file link: './Set-AzKeyVaultSecret.yml'.

azps-0.10.0/Az.KeyVault/Undo-AzKeyVaultKeyRemoval.yml

Line 16, Column 9: [Warning: file-not-found - See documentation] Invalid file link: './Set-AzKeyVaultSecret.yml'.

azps-0.10.0/Az.Network/Add-AzApplicationGatewayAuthenticationCertificate.yml

Line 17, Column 9: [Warning: file-not-found - See documentation] Invalid file link: './New-AzApplicationGatewayAuthenticationCertificate.yml'.
Line 19, Column 9: [Warning: file-not-found - See documentation] Invalid file link: './Remove-AzApplicationGatewayAuthenticationCertificate.yml'.
Line 21, Column 9: [Warning: file-not-found - See documentation] Invalid file link: './Set-AzApplicationGatewayAuthenticationCertificate.yml'.

azps-0.10.0/Az.Network/Add-AzApplicationGatewayBackendAddressPool.yml

Line 15, Column 9: [Warning: file-not-found - See documentation] Invalid file link: './Get-AzApplicationGatewayBackendAddressPool.yml'.
Line 17, Column 9: [Warning: file-not-found - See documentation] Invalid file link: './Get-AzApplicationGatewayBackendAddressPool.yml'.
Line 21, Column 9: [Warning: file-not-found - See documentation] Invalid file link: './Remove-AzApplicationGatewayBackendAddressPool.yml'.
Line 23, Column 9: [Warning: file-not-found - See documentation] Invalid file link: './Set-AzApplicationGatewayBackendAddressPool.yml'.

azps-0.10.0/Az.Network/Add-AzApplicationGatewayFrontendIPConfig.yml

Line 14, Column 9: [Warning: file-not-found - See documentation] Invalid file link: './Get-AzApplicationGatewayFrontendIPConfig.yml'.
Line 18, Column 9: [Warning: file-not-found - See documentation] Invalid file link: './Remove-AzApplicationGatewayFrontendIPConfig.yml'.
Line 20, Column 9: [Warning: file-not-found - See documentation] Invalid file link: './Set-AzApplicationGatewayFrontendIPConfig.yml'.

azps-0.10.0/Az.Network/Add-AzApplicationGatewayFrontendPort.yml

Line 16, Column 9: [Warning: file-not-found - See documentation] Invalid file link: './New-AzApplicationGatewayFrontendPort.yml'.
Line 18, Column 9: [Warning: file-not-found - See documentation] Invalid file link: './Remove-AzApplicationGatewayFrontendPort.yml'.
Line 20, Column 9: [Warning: file-not-found - See documentation] Invalid file link: './Set-AzApplicationGatewayFrontendPort.yml'.

azps-0.10.0/Az.Network/Add-AzApplicationGatewaySslCertificate.yml

Line 16, Column 9: [Warning: file-not-found - See documentation] Invalid file link: './New-AzApplicationGatewaySslCertificate.yml'.
Line 18, Column 9: [Warning: file-not-found - See documentation] Invalid file link: './Remove-AzApplicationGatewaySslCertificate.yml'.
Line 20, Column 9: [Warning: file-not-found - See documentation] Invalid file link: './Set-AzApplicationGatewaySslCertificate.yml'.

azps-0.10.0/Az.Network/Add-AzExpressRouteCircuitAuthorization.yml

Line 22, Column 9: [Warning: file-not-found - See documentation] Invalid file link: './New-AzExpressRouteCircuitAuthorization.yml'.

This comment lists only the first 25 errors (including error/warning/suggestion) in the pull request.
For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 89b7e5e:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

azps-0.10.0/Az.Network/Get-AzVirtualNetworkGatewaySupportedVpnDevice.md
:white_check_mark:Succeeded
View (azps-0.10.0)

azps-7.5.0/Az.FrontDoor/New-AzFrontDoorRoutingRuleObject.md
:white_check_mark:Succeeded
View (azps-7.5.0)

azps-7.5.0/Az.Network/Get-AzVirtualNetworkGatewaySupportedVpnDevice.md
:white_check_mark:Succeeded
View (azps-7.5.0)

azps-7.5.0/Az.Network/New-AzApplicationGatewayHttpListener.md
:white_check_mark:Succeeded
View (azps-7.5.0)

azps-8.0.0/Az.Network/Get-AzVirtualNetworkGatewaySupportedVpnDevice.md
:white_check_mark:Succeeded
View (azps-8.0.0)

azps-8.0.0/Az.Network/New-AzApplicationGatewayHttpListener.md
:white_check_mark:Succeeded
View (azps-8.0.0)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


My profile is fine

@edwardlubbe Thanks for the Pull Request
Dont forget to say hi sometime and grab a sticker


Invalid content for node bulletList: <listItem(paragraph("Excise comets from a guest li

RangeError: Invalid content for node bulletList: <listItem(paragraph("Excise comets from a guest li
    at eh.check (http://localhost:8080/apps/groups/assets/index.972692a0.js:68:57518)
    at http://localhost:8080/apps/groups/assets/index.972692a0.js:68:57866
    at Qe.forEach (http://localhost:8080/apps/groups/assets/index.972692a0.js:68:44012)
    at eh.check (http://localhost:8080/apps/groups/assets/index.972692a0.js:68:57853)
    at http://localhost:8080/apps/groups/assets/index.972692a0.js:168:5580
    at Array.forEach (<anonymous>)
    at http://localhost:8080/apps/groups/assets/index.972692a0.js:168:5566
    at Object.insertContentAt (http://localhost:8080/apps/groups/assets/index.972692a0.js:165:8054)
    at http://localhost:8080/apps/groups/assets/index.972692a0.js:168:4392
    at Object.insertContent (http://localhost:8080/apps/groups/assets/index.972692a0.js:165:7432)

@polrel-witter Thanks. Where did you encounter this error? In a notebook?

Yeah, it happens when I click "edit" on a note.
Sent from ProtonMail mobile
-------- Original Message --------
On Jan 1, 2023, 9:25 AM, james acklin wrote:

@.***(https://github.com/polrel-witter) Thanks. Where did you encounter this error? In a notebook?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>

A new note, but I pasted the text from a separate program (i think it was just Ubuntu's plain text editor) so it may be caused by some weird embedded formatting.
Sent from ProtonMail mobile
-------- Original Message --------
On Jan 5, 2023, 1:30 PM, patosullivan wrote:

Did this happen with a migrated note (from old Groups) or a note created in new Groups?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>

See #1646: this happens when editing a bulleted list within a bulleted list.


Switched strategies to bound based on min/max of the corrected values only

This eliminates the need to attempt to match the corrected values to the uncorrected values, which may have different timezones or be interpolated after downsampling.

Coverage decreased (-0.03%) to 87.127% when pulling 8e93e5e262ee3301381405f60394f58d13591a84 on ee-usgs:AQCU-736_Switch_to_min_max_of_primary into 456de5d98d21ebe70149e83d52bc7fb5bb089d4d on USGS-R:master.


Make Dhat constructor private

This avoids typos where a Dhat struct is constructed but doesn't actually do anything.
I have a doctest for this locally, but I don't think it adds much to the documentation. Let me know if I should add it.
diff --git a/src/lib.rs b/src/lib.rs
index 59408d0..c01413f 100644
--- a/src/lib.rs
+++ b/src/lib.rs
@@ -193,8 +193,12 @@ use thousands::Separable;
 /// When the first value of this type is dropped, profiling data is written to
 /// file. Only one value of this type should be created; if subsequent values
 /// of this type are created they will have no effect.
+///
+/// ```compile_fail,E0603
+/// let dhat = dhat::Dhat;
+/// ```

(this is a breaking change)

A couple of questions, because I am unfamiliar with this:

I can see it's a breaking change in that there is previously valid code that would no longer work. But that code would be mistaken/useless, so in practice it's unlikely to affect anyone. Right?
Does this really make the constructor private? Or would it be more accurate to say that it makes the arg-less constructor unusable? (This might be nit-picking, but I'm just trying to understand the change.)
The doctest, as written, would look strange in the rendered docs, right?

I can see it's a breaking change in that there is previously valid code that would no longer work. But that code would be mistaken/useless, so in practice it's unlikely to affect anyone. Right?

Correct, anyone using this already had broken code that wasn't doing anything.

Does this really make the constructor private? Or would it be more accurate to say that it makes the arg-less constructor unusable? (This might be nit-picking, but I'm just trying to understand the change.)

Pedantically, this removes the public 0-argument constructor and adds a private 1-argument constructor. The only argument is () so it has exactly the same information before (the two are isomorphic if that's a familiar term), but rust doesn't allow making zero-argument constructors private.

The doctest, as written, would look strange in the rendered docs, right?

I think so. Here's a screenshot:

I ended up having to add an argument to Dhat in #5, so this is no longer needed.


Lots of packages now getting: "failed dependency check."

This issue is similar to #108
I'm having a number of packages fail the dependency check and fail to be added to the repository. Below is an example with postfix-current. I commented out everything in make.conf to reduce the chance of that having any impact. I'm having this issue across systems and ports on FreeBSD 12.0-RELEASE-p3.
I've also learned that the upgrade functionality is dangerious in this scenario. I had one system lose a lot of installed ports. Ports will install fine if I don't rebuild the repository and install the port manually using pkg.
synth just-build mail/postfix-current && synth rebuild-repository
The task is complete.  Final tally:
Initial queue size: 1
packages built: 1
ignored: 0
skipped: 0
failed: 0
Duration: 00:02:03
The build logs can be found at: /var/log/synth
Stand by, prescanning existing packages.
Stand by, recursively scanning 184 ports serially.
Scanning existing packages.
postfix-current-3.4.20190106,5.txz failed dependency check.
Packages validated, rebuilding local repository.
Local repository successfully rebuilt
at the end of /var/log/synth/mail___postfix.log:

--  Phase: package
===>  Building package for postfix-3.3.3_1,1
actual-package-depends: dependency on /usr/lib/libkrb5.so not registered (normal if it belongs to base)
file sizes/checksums   [151]: .. done
packing files          [151]: .. done
packing directories     [19]: . done

--  Termination
Finished: Saturday, 30 MAR 2019 at 02:15:40 UTC
Duration: 00:01:59

I still encountered similar problems when I tried to update some packages with "synth just-build".
When I recreated the repository it deleted lots of packages due to dependencies errors...
How could we update some packages without breaking other packages dependencies ???
Is it a bug or I missed something?

If I had to guess, you've got the "pre-fetch suitable packages" option selected and there was a mismatch between the available packages and the downloaded metadata.
Also, the "synth upgrade" command is dangerous in that build failures can cause issues when the pkg upgrade command is used.  That's why I don't recommend it and recommend that local repositories are built and verified before *manual" running of "pkg upgrade" commands.
so nobody else is reporting an issue, so I'd start with a build list (as a file) and use that list to rebuild a local repository.  It's not a systematic issue, it's something limited to your setup.

Synth configuration profile: LiveSystem
[A] Ports directory            /usr/ports
[B] Packages directory         /var/synth/live_packages
[C] Distfiles directory        /usr/ports/distfiles
[D] Port options directory     /var/db/ports
[E] Build logs directory       /var/log/synth
[F] Build base directory       /usr/obj/synth-live
[G] System root directory      /
[H] Compiler cache directory   disabled
[I] Num. concurrent builders   2
[J] Max. jobs per builder      2
[K] Use tmpfs for work area    false
[L] Use tmpfs for localbase    false
[M] Display using ncurses      true
[N] Fetch prebuilt packages    false
[>]   Switch/create profiles
[RET] Exit
/usr/local/etc/pkg/repos/FreeBSD.conf:
FreeBSD: {
enabled: no
}
I've also done the build list as a file and a build list as a single port (like my example above) on multiple installs and have the same effect.
@Teetoow's comments also indicated one of the symptoms I noted in my first post. But you are correct, it could very well be configuration related as I'm the one managing these systems.

so nobody else is reporting an issue, so I'd start with a build list (as a file) and use that list to rebuild a local repository. It's not a systematic issue, it's something limited to your setup.

I'm not sure to understand what you meant. Do you mean that it's not possible to keep dependencies for all packages already built when ports have been updated and some packages have been requested to be rebuilt?
Thus there is no equivalent to portmaster  which keep valid all packages available in the repository?

all packages that are out of date are rebuilt.
When the repository is generated, all the out-of-date packages are deleted during the process.

@Teetoow I think you're having conceptual issues.  it sounds like synth is working correctly for you.
If you update the ports tree every day and run synth every day, it's going to rebuild hundreds of ports, every day.  That's just the nature of it.  Poudriere is the same.

@jrmarino several hours ago, I just updated my ports because of python 3.7 bug.. I performed synth just-build python37.
After that I performed synth rebuild-repository to recreate my repository and update the new python package on my machines. However this command deleted (without my acknowledgment) hundread of packages because a library (provided by python3.7 which was rebuilt because of a new port version) broke other packages dependencies (and these packages were not rebuilt..).
I don't know if it's clear. I just swapped from portmaster to synth...

Well, sounds perfectly normal.
The rebuild-repository deletes obsolete packages.  With the python37 update, everything that depended on previously version of python37 was instantly obsoleted.
When you provide synth the build list (the top level ports you want the repository to have) everything will be rebuilt with integrity.  It's how it works (and poudriere is almost identical in this behavior).

Ok I'm sorry I missed that part of how it works. But my other question: how to specify to synth to only build a specific package with its dependances (and all packages which depend on them) with the build list?
My problem is: I don't want to rebuild all the packages of the repository each time a package has a security issue fixed...

you can't.  it rebuilds everything that requires rebuilding by design.  Choosing to intentionally break library linkages is not supported by synth.  A single port can cause a massive rebuild and you can't tell synth "I want you to do the wrong thing here".
(A response along the lines of "portmaster allows that" won't cause a blink.   This is considered the wrong action by both synth and poudriere.)

Can you tell me why newly compiled ports would fail to be added to the repository? I was able to limit the cause to my original post above.
The below options (or no options set at all) will enable the package to be added to the repository without an issue. But as soon as I change the below to include OPTIONS_FILE_SET+=SASLKMIT (or simply include it in the make.conf), the above error of: 'postfix-current-3.4.20190106,5.txz failed dependency check.' ocurrs and the package is removed. The port will install fine if I don't rebuild-repository and install the port manually.
Is this a port issue or synth related? Do you have any recommendations for checks I could do to narrow it down?
This file is auto-generated by 'make config'.
Options for postfix-current-3.4.20190106,5
_OPTIONS_READ=postfix-current-3.4.20190106,5
_FILE_COMPLETE_OPTIONS_LIST=BDB BLACKLISTD CDB DOCS EAI INST_BASE LDAP LDAP_SASL LMDB MYSQL NIS PCRE PGSQL SASL SQLITE TEST TLS SASLKRB5 SASLKMIT
OPTIONS_FILE_UNSET+=BDB
OPTIONS_FILE_UNSET+=BLACKLISTD
OPTIONS_FILE_UNSET+=CDB
OPTIONS_FILE_UNSET+=DOCS
OPTIONS_FILE_SET+=EAI
OPTIONS_FILE_UNSET+=INST_BASE
OPTIONS_FILE_UNSET+=LDAP
OPTIONS_FILE_UNSET+=LDAP_SASL
OPTIONS_FILE_UNSET+=LMDB
OPTIONS_FILE_UNSET+=MYSQL
OPTIONS_FILE_UNSET+=NIS
OPTIONS_FILE_SET+=PCRE
OPTIONS_FILE_SET+=PGSQL
OPTIONS_FILE_SET+=SASL
OPTIONS_FILE_UNSET+=SQLITE
OPTIONS_FILE_UNSET+=TEST
OPTIONS_FILE_SET+=TLS
OPTIONS_FILE_UNSET+=SASLKRB5
OPTIONS_FILE_UNSET+=SASLKMIT

I guess I don't understand the confusion here.
See : https://www.freshports.org/mail/postfix/
particularly:
SASLKMIT=off: If your SASL req. MIT Kerberos5, select this

in makefile
SASLKMIT_LIB_DEPENDS=   libkrb5.so:security/krb5

By adding that line to the make.conf, you changed the dependencies of postfix.  Of course it will be obsoleted due to missing dependencies.   What I don't get is why this is unexpected by you.

I don't believe there is any confusion here. (Keep in mind, you're in two different discussion threads for the same issue #.) I completely understand how that would invalidate a port and require a rebuild.
My issue is I can run 'synth just-build mail/postfix-current' endlessly because it will always fail the dependency check, but this only occurs only when I have SASLKMIT set.
If you're able to compile this and run 'synth rebuild-repository' without it being flagged as missing dependencies, I apologize profusely as the issue is obviously mine.

It's because there's a bug in the postfix makefile.  (At least I consider it a bug, others may disagree).
The specification is "librkb5.so".  libkrb5.so is already on the base system, so this line "SASLKMIT_LIB_DEPENDS=   libkrb5.so:security/krb5" has NO effect on any freebsd system.  So if the port maintainer wants to use krb5 from base always, this line needs to be removed.  If he wants to use librk5 from the port, then the specification needs to be changed to libkrb5.so.X so that the dependency gets pulled in.
So the issue is synth is expected security/krb5 to be on the postfix dependency list, but the ports tree skips it because it finds it in base.  It's a common mistake port maintainers make.  They don't even realize it most of the time.

in other words, for you to fix it, either correct the SASLKMIT_LIB_DEPENDS line dependency, or comment the line out completely (if the base krb5 is fine).

Thank you for the detailed explanation.
I’ll ping the port maintainer and lookout for these errors in the future.
Thanks again!

On Apr 6, 2019, at 7:09 PM, jrmarino<EMAIL_ADDRESS>wrote:
in other words, for you to fix it, either correct the SASLKMIT_LIB_DEPENDS line dependency, or comment the line out completely (if the base krb5 is fine).
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

I'm so sorry about disturbing your discussion but I didn't found another way to contact you... If you have a mail address or something like that, i would appreciate to write to you there.
Moreover I think my english is so bad that you missunderstood what I said. Thus I will try to reexplain what happened two days ago.
Python3.7 had a security issue. Thus I updated ports and perform:
# synth just-build lang/python37
This action recreated 4 ou 5 packages which are needed by python and have been upgraded in ports.
This is the normal action and I'm totally agree with that.
However when I rebuilt the repository with:
# synth rebuild-repository
It wrotes hundred of lines like this:
<package name>.txz failed dependency check.
and just deleted them from my repository (around 150 packages!!)
(I'm sorry I forgot to save the output of this command thus I lost most of these messages..)
Before updating ports and rebuilding python3.7 the "rebuild-repository" had no errors like that. Thus my conclusion is that the rebuild of python (and the 4 other packages which were rebuild at the same time..) broke dependencies of these 150 other packages.. In that case, why synth did not rebuilt them?

you can't. it rebuilds everything that requires rebuilding by design. Choosing to intentionally break library linkages is not supported by synth. A single port can cause a massive rebuild and you can't tell synth "I want you to do the wrong thing here".

I'm totally agree with you and this is the way I want synth to work.

your english is fine, and I didn't misunderstand.
Let me try to explain.
The "rebuild-repository" command is manually issued when the administrator has successfully built all the required packages.  As part of the command, obsolete packages are removed.
So in your case, you didn't build your complete set of packages (which are determined by either having a text file with top level ports listed, or generating that list internally from synth upgrade-system).  So you issued the "rebuild-repository" command prematurely.  It correctly removed the obsolete packages but there weren't any valid packages there, so the new repository is much smaller than the first.
The "fix" is to tell synth to build an exact set of top-level ports (e.g. libreoffice, emacs, etc), and once that is complete, issue the "rebuild-repository" command again.  That will get in you the proper configuration wrt to your local repository.

Ok I got what you said. Unfortunately I guess there is no solution for what I want...
I need to upgrade ports when there is a security fix for a specific package but it also upgrade many other ports.. There is no problem for me if it upgrades the port and its dependencies.
I would like synth to also rebuild (or upgrade) other packages which depends on the rebuilt one.
But if I specify a list of top packages to synth it will upgrade ALL of them right? Even those who are not dependent of any package who have been rebuilt (the initial package and its dependences)...
Maybe with an example it will be easier to understand.
Lets assume I have (and want to keep!) 5 packages in my repository: A, B, C, D, E
"A" has a security issue thus I want to upgrade it. I upgrade my ports. But modifications have been done on the five ports.
"A" depends on "B" thus synth will upgrade both packages, OK.
However "C" also depends on "B".. If "B" is upgraded and not "C" it breaks the dependance and "C" will be removed and I don't want that.
If I specify a file with the name of the five packages, synth will upgrade all of them.. But I don't want "D" and "E" to be upgraded! They doesn't depend on "A" nor "B" nor "C", even if there ports have been updated, I don't want them to be rebuilt nor upgraded.
In the present case I would like to find the solution in order to synth rebuild "A", "B" and "C" only.
Thus what could be the solution?

I’m not the developer, but the only solution I can think of is synth on a virtual machine (or jail) per main port. Not really efficient, but that would address your use case.

On Apr 7, 2019, at 1:51 PM, Teetoow<EMAIL_ADDRESS>wrote:
Ok I got what you said. Unfortunately I guess there is no solution for what I want...
I need to upgrade ports when there is a security fix for a specific package but it also upgrade many other ports.. There is no problem for me if it upgrades the port and its dependencies.
I would like synth to also rebuild (or upgrade) other packages which depends on the rebuilt one.
But if I specify a list of top packages to synth it will upgrade ALL of them right? Even those who are not dependent of any package who have been rebuilt (the initial package and its dependences)...
Maybe with an example it will be easier to understand.
Lets assume I have (and want to keep!) 5 packages in my repository: A, B, C, D, E
"A" has a security issue thus I want to upgrade it. I upgrade my ports. But modifications have been done on the five ports.
"A" depends on "B" thus synth will upgrade both packages, OK.
However "C" also depends on "B".. If "B" is upgraded and not "C" it breaks the dependance and "C" will be removed and I don't want that.
If I specify a file with the name of the five packages, synth will upgrade all of them.. But I don't want "D" and "E" to be upgraded! They doesn't depend on "A" nor "B" nor "C", even if there ports have been updated, I don't want them to be rebuilt nor upgraded.
In the present case I would like to find the solution in order to synth rebuild "A", "B" and "C" only.
Thus what could be the solution?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

I’m not the developer, but the only solution I can think of is synth on a virtual machine (or jail) per main port. Not really efficient, but that would address your use case.

Thank you for your answer. Unfortunately, that's not realistic.. I have around 80 main ports. Splitting them would mean having multiple version of the same softwares and libraries (one per virtual machine...) that's unmaintainable for me :(

@Teetoow
I don't really see how your example is valid.
To refine it, say you have a build list of A,B,C,D,E
You don't tell synth to build A and B.  You tell synth to build the entire list.
If the existing packages are valid (dependencies match) then it only builds what it needs to (in other words, it ignores the build command on those).
In any case, after the build command, the repository is complete.  It might have obsolete packages in the repository directory, but when you issue the "rebuild repository" command, it removes them.
So I think you've got a misunderstanding of how to maintain repositories maybe?  Because your example is of somebody doing it incorrectly.  Done correctly, the repository is always complete.

In fact I don't want to recompile ALL packages just because one of them has security issue fixed..
I receive something like 1 ou 2 security issues per week. I don't want to recompile 400 packages twice a week just for that (it costs too much time, energy, money and is absolutly useless for my purpose..).. Moreover I don't want to use the latest version (except when there is a security issue) for each software.. It might create too much work (check that the new version of every package does not break configuration file, work as before etc.)..
Rebuilding everything could be a good thing for some uses but not for all..
With portmaster it knows the wanted top packages (pkg query -e '%a = 0' %o),  I ask it to rebuild one package, it rebuild it, its dependencies and all packages which are dependent of them depending on the wanted packages. And that's it.
I would really appreciate to have the same thing with synth. Let's imagine:
# synth build package --keep-packages listOfAllWantedPackages.txt
and synth could perform the exact same thing.
In my previous example:
# synth build A --keep-packages listOfAllWantedPackages.txt
And listOfAllWantedPackages.txt contains "A, B, C, D, E"
And this command will only rebuild A, B and C.
This technique also well maintains the repository.

it's not ALL.  It's ALL that require it.
The request is for all, but again, any request against a valid package is ignored.

it's not ALL. It's ALL that require it.
The request is for all, but again, any request against a valid package is ignored.

For sure but when I upgrade ports in order to get a security issue fixed, it also update many many other ports... and I don't care about these updates!

we're going in circles.   You don't get an option to do the wrong thing (partial builds).  Either you build everything required or nothing at all.   It's the nature of the beast.   It's also the same as poudriere.

Note that the freebsd ports tree is presented a unit.  It doesn't support having versions that aren't presented together.

Indeed I will stop my question after that and come back to portmaster which works perfectly since many years without absolutely any problem for me. The only bad thing is that it doesn't share packages like synth and poudriere do.
Three days ago python37 received a patch for a security issue, I wanted it. portsnap updated around 500 ports at the same time.
As an example one of them was postfix which absolutely does not depend on python nor any of its dependancies which were rebuilt. Postfix is one of the package I maintain. So you are explaining to me that it's crazy to not rebuild postfix because its port has been updated?
In that particular case, I'm obliged to compile each new port each time they are updated..
Why is it so evil to stay at a specific version of a specific package while there is no security issue and there is no need of a newer version for dependency question? If the answer is "there is no problem you can" why I would loose time and energy to compile newer version of it for.. nothing because I won't update it yet?
I'm not FreeBSD repository which try to have its package repository synchronized with their ports.. I'm just a very little administrator of two servers who don't want to build the same software on two different machine and prefer to compile it once and share the result. I though it was the purpose of synth..
I don't understand what's going wrong in my manner of administrating my machines.

2 thoughts:

400 packages is actually not impressive.   A decent machine should be able to rebuild 400 ports in 2 hours.   If twice a week is too much electricity, then update once a week or twice a month.
I don't get any bonus for users.  I'm no longer developing synth.  I only do support fixes (usually when freebsd ports developers change something drastic).  My new project is www.ravenports.com . so if portmaster does it for you, that's great.


Workflow API docs

Thank you for helping make the Dapr documentation better!
Please follow this checklist before submitting:

[ ] Commits are signed with Developer Certificate of Origin (DCO - learn more)
[ ] Read the contribution guide
[ ] Commands include options for Linux, MacOS, and Windows within codetabs
[ ] New file and folder names are globally unique
[ ] Page references use shortcodes instead of markdown or URL links
[ ] Images use HTML style and have alternative text
[ ] Places where multiple code/command options are given have codetabs

In addition, please fill out the following to help reviewers understand this pull request:
Description
Chalking out workflow API docs
Issue reference
PR will close: #2798

#2933


BUG Include joblib.load in wrapper function error handling

In the joblib backend remote runner script, the joblib.load call will fail if we try to load an object which refers to code that's not in our remote environment. That's an easy mistake to make, and we should make sure that users see an informative error from it. By moving the load call inside the try/finally block, we can record any exceptions from the load call and pass them back to the parent process.

LGTM (if you just don't want to wait! 😄 )

Tempting, but I think that code review is like experimentation in that you need to declare your end condition and stick with it. I'll ask you for review next time I have something like this. :-)

LGTM!


cordova plugin add @0.6.2: version not found

When running the command "cordova plugin add de.appplant.cordova.plugin.background-mode@
0.6.2", I get this result:
Fetching plugin<EMAIL_ADDRESS>via plugin registry
npm http GET http://registry.cordova.io/de.appplant.cordova.plugin.background-mode/0.6.2
npm http 404 http://registry.cordova.io/de.appplant.cordova.plugin.background-mode/0.6.2
Error: version not found: 0.6.2 : de.appplant.cordova.plugin.background-mode/0.6.2
Maybe some file is missing from the server? When installing without @0.6.2, version 0.6.1 is downloaded.

has been published now!

has been published now!