Setting storage type based on compatibility

Is it possible in an angular config block to check whether the current storagetype is supported and otherwise fallback or disable the service?

At the moment that is not possible. That check is done using the $window service that is only available after the config phase.
Unfortunately this repo is not being maintained as actively as I would like so I have forked it and I'm rolling out my own version.
So far on my repo I have two version available. One with the old code, that I have converted to TypeScript, but transpiles to JS.

@ealves-pt
I didn't know that this repository wasn't actively maintained. I suppose after enough time when your fork diverges from this you should consider breaking the fork off into its own repository.
For one, it's good to know what's supported before being locked to the storage type. I.e., it would be good to be able to know what is supported at the provider level.
I'm not sure if this is how you do it but I would go for using the Adapter pattern to abstract the storage mechanism to polymorphic storage types so that when I refer to the injected service ngWebStorageService, I am referring to my instance of the service based on the storage type. That would mean that for the most part the localStorage and the sessionStorage (for example) mechanisms would have the same functions and implement the same interface (which you can manipulate more visually with typescript's interfaces). You could go one step further and expose the storage adapter interface to allow other developers to extend the module by adding their own storage adapter.
I am not sure if this repository handles it, but have you considered collision resolution? What happens if you try to put a key value pair with a key that already exists in storage?
I would also add an efficient 'has' function to the interface to be able to quickly if a specified key exists in the storage mechanism.
If I can help in any way, please let me know.

@g2graman
Perhaps this repo will go back to life anytime soon, but in the meantime I need some features that it didn't have so I went ahead and I'm building my own. Eventually I will break the fork in the near future.
I'm doing almost everything you said on my new code. I have a ngSessionWebStorageService and a ngLocalWebStorageService and they share the exact same API. That way it will be easy to abstract further more if needed. (For now I have kept it simple). Yes, it is a good idea to expose the AbstractStorageService as you suggested. I will keep that in mind as an improvement for the future.
Regarding collision resolution, this repo will always override existing keys.
The has function might be a good addition to the AbstractStorageService.
I still have some functionalities missing in my code. For example:

fallback mechanism when a specific storage is not available
change key prefix at run time

And some other stuff I don't remember right now. So, PR are always welcome. :smile:

I'm actually looking for help maintaining this repo. So many issues and
PRs. I am looking for Collaborators.
Greg
On Tue, Feb 16, 2016 at 1:43 PM, Francesco<EMAIL_ADDRESS>wrote:

@ealves-pt https://github.com/ealves-pt
I didn't know that this repository wasn't actively maintained. I suppose
after enough time when your fork diverges from this you should consider
breaking the fork off into its own repository.
For one, it's good to know what's supported before being locked to the
storage type. I.e., it would be good to be able to know what is supported
at the provider level.
I'm not sure if this is how you do it but I would go for using the Adapter
pattern to abstract the storage mechanism to polymorphic storage types so
that when I refer to the injected service ngWebStorageService, I am
referring to my instance of the service based on the storage type. That
would mean that for the most part the localStorage and the sessionStorage
(for example) mechanisms would have the same functions and implement the
same interface (which you can manipulate more visually with typescript's
interfaces). You could go one step further and expose the storage adapter
interface to allow other developers to extend the module by adding their
own storage adapter.
I am not sure if this repository handles it, but have you considered
collision resolution? What happens if you try to put a key value pair with
a key that already exists in storage?
I would also add an efficient 'has' function to the interface to be able
to quickly if a specified key exists in the storage mechanism.
If I can help in any way, please let me know.
—
Reply to this email directly or view it on GitHub
https://github.com/grevory/angular-local-storage/issues/281#issuecomment-184777504
.

@grevory
At the moment I have a PR, #279, open with small updates and fixes for minor issues.
If you want we can try to come up with a way to merge my fork into this repo. Even though I have migrated the entire code to TypeScript the API is still the same and all the tests are accepted.
Besides that, I'm rolling out my own version with some core changes and if you find it interesting we can also access the possibility to integrate them.

@grevory If possible, I would like to help maintain the repository as well by submitting my own PRs to have reviewed by other collaborators, reviewing other people's PR and approval.
I would very much like to work with you, @ealves-pt
Otherwise I'll stop adding to the current issue until I submit a PR to fix it.

Nice, for me it's perfect. :+1:
I suggest taking a look to all the PR open at the moment and also the issues to see where to start first. Regarding my fork of this repository I will create a discussion issue so we can decide if it makes sense, or not, some of the stuff that I did.

Yea, there are so many PRs that they can't just be accepted. There will be a lot of conflicts to work through and I greatly appreciate the help guys.

Thank you so much!
On Feb 17, 2016 7:34 PM, "Eduardo Alves"<EMAIL_ADDRESS>wrote:

Nice, for me it's perfect. [image: :+1:]
I suggest taking a look to all the PR open at the moment and also the
issues to see where to start first. Regarding my fork of this repository I
will create a discussion issue so we can decide if it makes sense, or not,
some of the stuff that I did.
—
Reply to this email directly or view it on GitHub
https://github.com/grevory/angular-local-storage/issues/281#issuecomment-185397392
.

As you guys should have noticed I did some "spring cleaning" to the issues yesterday. Today I will go through the PR to see what is hanging around there. I will also create a new issue with a task list and mark it as RFC so we can discuss the next steps to take.
Regarding the subject of this issue I will mark it as a duplicate but I will leave it open for now.
Duplicate of #181

I use this repository a lot in my applications and I'm surprised it is not maintained. I will like to help maintain it and add the needed features especially the ones discussed in the last few days.

Perfect :+1:

Let's continue this discussion on #151


Move facter from Extended to Core

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

[x] The toolchain has been rebuilt successfully (or no changes were made to it)
[x] The toolchain/worker package manifests are up-to-date
[x] Any updated packages successfully build (or no packages were changed)
[x] Packages depending on static components modified in this PR (Golang,  subpackages, etc.) have had their  tag incremented.
[ ] Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
[x] All package sources are available
[x] cgmanifest files are up-to-date and sorted (, , )
[x] LICENSE-MAP files are up-to-date (, , )
[x] All source files have up-to-date hashes in the  files
[x]  and  pass
[x] Documentation has been updated to match any changes to the build system
[ ] Ready to merge

Summary

What does the PR accomplish, why was it needed?
The PR moves package  from Extended to Core.
The package is required to build "puppet" package.
Change Log

Promote package to Mariner Base repo

Does this affect the toolchain?

NO
Associated issues

#xxxx

Links to CVEs

https://nvd.nist.gov/vuln/detail/CVE-YYYY-XXXX

Test Methodology

Pipeline build id: xxxx

Well, our .gitattributes looks to be set correctly to override every *.spec so linguist uses the RPM-Spec (#4510)
And this bizarre syntax highlighting behavior seems to be only an issue on the PR diff render. If I look at the spec in the GitHub tree, the syntax highlighting is as expected.
Very curious.... 🤔🤔

Similar curiosity with this spec's syntax highlighting like the one in #7099 Maybe it has something to do with the spec starting with ## at the top of the file and GitHub's autodetection is mis-detecting the file type? 🤔 https://github.com/github-linguist/linguist https://github.com/github-linguist/linguist/blob/master/docs/overrides.md

I was suspecting the ## at the start of the spec too.


Added fixes for graph broadcast csharp sample

@Prithvi-MSFT - Kindly run build pipeline.

Run Build pipeline and merge this.

Build status - All builds passed
https://github.com/OfficeDev/Microsoft-Teams-Samples/actions/runs/6295345550

Executed build pipeline: https://github.com/OfficeDev/Microsoft-Teams-Samples/actions/runs/6298484186


Unity Config with .unityweb extensions

Hi Jeffrey,
My unity build for WebGL / Assembly outputs files with .unityweb extensions.
Does your library support this?
Do I need to add some sort of web.config to my react client to parse the .unityweb files?
Here is what I attempted, where the build folder is in the public folder:
function App() {
  let unityContext = new UnityContext({
    loaderUrl: "build/UnityLoader.js",
    dataUrl: "build/Builds.data.unityweb",
    frameworkUrl: "build/Builds.wasm.framework.unityweb",
    codeUrl: "build/Builds.wasm.code.unityweb",
  });

  return <Unity unityContext={unityContext} />;
}

All I can see is a warning:
unity.ts:80 Something went wrong while mouting the UnityInstance TypeError: window.createUnityInstance is not a function
at Unity. (unity.ts:73)
at step (PropTypes.js:11)
at Object.next (PropTypes.js:11)
at fulfilled (PropTypes.js:11)
Appreciate any help you could provide.
Thanks
Damian

Hi. Which version of Unity did you use to create this build?

2019.4.12f1
I initially tried version @7.* and got this error:
TypeError: react_unity_webgl__WEBPACK_IMPORTED_MODULE_4__.UnityContext is not a constructor
Then I tried upgrading to @8.* and got what I mentioned above.

I recommend using TypeScript for type-safe auto completion and validation.
Also see the Readme for 7.x, UnityContext was refactored to UnityContent.
Here is some example code from the old Wiki.
When possible try upgrading your project to Unity 2020 for the best WebGL support.

That is working now, thanks for your help!

Hi there! I'm having this issue, too, and I don't quite understand the resolution.  Is there a setting in the Unity build that should be changed? Or is it something in React? (Sorry I'm more of a React dev on my team with extremely little Unity experience)

Disregard! We were on Unity 2019 (I thought it was 2020). Changing the React component that renders the game to Typescript and switching to version 7.x using the instructions in the README you mentioned was all I needed.  @jeffreylanters I suspect I'll be using this project quite a bit, if there's any (relatively easy) bug fixes, changes, or improvements that need to be made I'm more than willing to help.

Not yet though. I'm kinda hard for me to solve it because it's not my
forte. I have experience with react but not in unity, Sorry about that.
Please message or email me if you already solved it. Thank you!
On Wed, Nov 11, 2020 at 1:20 AM Dave Van Fleet<EMAIL_ADDRESS>wrote:

Disregard! We were on Unity 2019 (I thought it was 2020). Changing the
React component that renders the game to Typescript and switching to
version 7.x using the instructions in the README you mentioned was all I
needed. @jeffreylanters https://github.com/jeffreylanters I suspect
I'll be using this project quite a bit, if there's any (relatively easy)
bug fixes, changes, or improvements that need to be made I'm more than
willing to help.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/elraccoone/react-unity-webgl/issues/127#issuecomment-724846099,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALYOOBFEXHPWN4DZTM3S5JTSPFY57ANCNFSM4S4DVBUQ
.


Add --puppetfile option to the cli

Bundler can do bundle install --gemfile=/path/to/Gemfile (and also responds to the BUNDLER_GEMFILE environment variable). It might be nice to have similar functionality in librarian-puppet so that one may install dependencies without having to change into the directory that contains the Puppetfile.
I run my Puppets master-less, and use cron to apply updates, so this would help me a bunch. If this seems reasonable and is a change that should be made on this repository, I'd be happy to work on a pull request (but figured I'd ask first). Until then, I'll just have my cron task cd into the directory.

this issue has no bee touched in awhile, but thoughts on something like the following?
diff --git a/lib/librarian/puppet/cli.rb b/lib/librarian/puppet/cli.rb
index afb8e88..de864e4 100644
--- a/lib/librarian/puppet/cli.rb
+++ b/lib/librarian/puppet/cli.rb
@@ -47,6 +47,7 @@ module Librarian
       option "destructive", :type => :boolean, :default => false
       option "local", :type => :boolean, :default => false
       option "use-v1-api", :type => :boolean, :default => true
+      option "puppetfile", :type => :string
       def install

         ensure!
@@ -61,6 +62,9 @@ module Librarian
         if options.include?("path")
           environment.config_db.local["path"] = options["path"]
         end
+        if options.include?("puppetfile")
+          ENV["PUPPETFILE"] = options["puppetfile"]
+        end

         environment.config_db.local['use-v1-api'] = options['use-v1-api'] ? '1' : nil
         environment.config_db.local['mode'] = options['local'] ? 'local' : nil
diff --git a/lib/librarian/puppet/environment.rb b/lib/librarian/puppet/environment.rb
index d502415..73cdd30 100644
--- a/lib/librarian/puppet/environment.rb
+++ b/lib/librarian/puppet/environment.rb
@@ -11,6 +11,17 @@ module Librarian
         "puppet"
       end

+      def default_specfile_name
+        @default_specfile_name ||= begin
+          if ENV["PUPPETFILE"]
+            ENV["PUPPETFILE"]
+          else
+            capped = adapter_name.capitalize
+            "#{capped}file"
+          end
+        end
+      end
+
       def lockfile
         Lockfile.new(self, lockfile_path)
       end


Provide a sample K8s yaml for stateless container.

https://github.com/openebs/openebs/tree/master/k8s/demo/specs includes an helloworld yaml..


Unsupported URL at oe1.orf.at

Checklist

[x] I'm reporting a broken site support
[x] I've verified that I'm running youtube-dl version 2<IP_ADDRESS>
[x] I've checked that all provided URLs are alive and playable in a browser
[x] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[x] I've searched the bugtracker for similar issues including closed ones

Verbose log

$ youtube-dl -v 'https://oe1.orf.at/artikel/444507/Der-Fall-Moritz-Schlick'
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: [u'-v', u'https://oe1.orf.at/artikel/444507/Der-Fall-Moritz-Schlick']
[debug] Encodings: locale UTF-8, fs UTF-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2<IP_ADDRESS>
[debug] Python version 2.7.16 (CPython) - Linux-4.19.0-9-686-pae-i686-with-debian-10.4
[debug] exe versions: ffmpeg 4.1.6-1, ffprobe 4.1.6-1
[debug] Proxy map: {}
[generic] Der-Fall-Moritz-Schlick: Requesting header
WARNING: Falling back on generic information extractor.
[generic] Der-Fall-Moritz-Schlick: Downloading webpage
[generic] Der-Fall-Moritz-Schlick: Extracting information
ERROR: Unsupported URL: https://oe1.orf.at/artikel/444507/Der-Fall-Moritz-Schlick
Traceback (most recent call last):
  File "/usr/local/lib/python2.7/dist-packages/youtube_dl/extractor/generic.py", line 2387, in _real_extract
    doc = compat_etree_fromstring(webpage.encode('utf-8'))
  File "/usr/local/lib/python2.7/dist-packages/youtube_dl/compat.py", line 2562, in compat_etree_fromstring
    doc = _XML(text, parser=etree.XMLParser(target=_TreeBuilder(element_factory=_element_factory)))
  File "/usr/local/lib/python2.7/dist-packages/youtube_dl/compat.py", line 2551, in _XML
    parser.feed(text)
  File "/usr/lib/python2.7/xml/etree/ElementTree.py", line 1659, in feed
    self._raiseerror(v)
  File "/usr/lib/python2.7/xml/etree/ElementTree.py", line 1523, in _raiseerror
    raise err
ParseError: mismatched tag: line 57, column 4
Traceback (most recent call last):
  File "/usr/local/lib/python2.7/dist-packages/youtube_dl/YoutubeDL.py", line 797, in extract_info
    ie_result = ie.extract(url)
  File "/usr/local/lib/python2.7/dist-packages/youtube_dl/extractor/common.py", line 530, in extract
    ie_result = self._real_extract(url)
  File "/usr/local/lib/python2.7/dist-packages/youtube_dl/extractor/generic.py", line 3382, in _real_extract
    raise UnsupportedError(url)
UnsupportedError: Unsupported URL: https://oe1.orf.at/artikel/444507/Der-Fall-Moritz-Schlick

Description

"https://oe1.orf.at/player..."  --> these URLs work fine
"https://oe1.orf.at/artikel..."  --> return UnsupportedError (tried some of these)

The source of the page (https://oe1.orf.at/artikel/444507/Der-Fall-Moritz-Schlick) contains a link to the data and says autoplay=false. Downloading the data-url works fine. Is it possible to adapt youtube-dl to download directly without looking into to source of the page?
Part of the source:
...
  |
  |
  |
  | <div class="oon-audio"
  | data-url="https://apasfftp1.sf.apa.at/oe1/internat/0001D050.MP3"
  | data-autoplay="false"
  | data-width="100%"
  |
  | >
  |
  |
  |
  |
  |
  |
...

JFTR: the https://oe1.orf.at/artikel... URLs come from here: https://oe1.orf.at/archiv. I also think it would be very useful to have youtube-dl support these kind of links.
The same goes for https://radiothek.orf.at/. These URLs are also not supported.
E.g. https://oe1.orf.at/player/20210415/635229 works but https://radiothek.orf.at/oe1/20210415/635229 does not. Also https://radiothek.orf.at/oe1/highlights/124047 + https://oe1.orf.at/programm/20210415/635229/Gesund-bis-ins-hohe-Alter have the same content but do not work.

Superseded by #29394.


Question : build subset of modules

Looking at the configure script, you have options:
--disable-FEATURE and --enable-FEATURE
Is there a way to list the features?
Is there a way to disable all of them and then re-enable a subset of them?
For example, how do i build the forward error correction feature only?

I think you can run ./configure --help for options but this won't build subsets of the modules. Some of them (such as FEC) don't have other internal dependencies but many of them do. For example, framing depends on dotprod, filter, fec, fft, modem, math, multicarrier and a few others.


[Enhancement]: make user can view the schedule tasks that failed to startup

What would you like to be added?
a schedule task will not be viewed when it is failed to be executed, for example

I create a partition plan task and make it executed every day.

I change the table'd ddl which make partition plan task not be executed normally

I can get the alert message normally

I can not view the record at the odc:

Why is this needed?
make odc better

It will be resolved in version 4.3.4


chore: light node size optimization

Delete data from trx_period, pbft_block_period and final_chain_log_blooms_index columns older than light node history
dag_block_period column was not correctly deleted, fixed

With these changes size of the db snapshot columns with 7 days history:
period_data 3.2GB
final_chain_receipt_by_trx_hash 413MB
trx_period 371MB
All other columns smaller than 100MB

prnet cleaned-up successfully


[CXF-7638] Only register provider if it implements specified contracts

Per JAX-RS javadoc, all registered components must implement the
contracts specified in the passed in array of Classes or the map of
contracts to priorities.  CXF should also log a warning when an invalid
contract is passed in to alert the user that the call to register has
been ignored.
Since ServerProviderFactory and CdiServerConfigurableFactory also used
this same registration mechanism (passing in server side filters/
interceptors, these parts also needed changes.
Looking for a review because I'm not 100% certain what the supportedContracts flow was really doing or if there are any negative effects from removing it.

This can be quite sensitive as users are also registering MBRs/MBWs and indeed all other standard interfaces now via the feature

@sberyozkin Right, I'm not worried about the cases where they register via Feature or without specifying a contract interface.  I'm more concerned about the case where ServerProviderFactory was creating the ConfigurableImpl with a List of built-in interfaces - then that List was used to register providers - even if those providers didn't implement the interfaces in the List.  Do you know what the point of that List was?  If it is essential, then I'll need to come up with an alternate fix, because this fix just gets rid of the List altogether.  Thanks, Andy

Hi, I was referring to a case where a provider implementing multiple interfaces has to be registered under a specific contract(s) only... May be I'm missing what the problem is. Can you please type the code showing where the issue for me to look at the master code with the better focus :-) ?  Thanks

Sorry, looking at the test in this PR which explains the issue...

OK, I've debugged the test and recall a bit better now what I was trying to do with these supported types. FYI, I found implementing all of these Configuration/Configurable very challenging, I recall typing and thinking I was not really sure if I was on the wrong or right path :-) as the original docs were quite compact, and the interpretation of some signatures can vary even today.
My own initial understanding was that it was primarily about supporting new filters/interceptors, given that in 2.0 (and in 2.1 for the most non-filter/non-interceptor interfaces) no priorities existed for MBR/MBW (and today for ex for ExceptionMapper or ParamConverterProvider) while many register methods accept the priorities or have the default priorities which have no any processing reqs for the last 2 intterfaces and in 2.0 - for MBR/MBW as well.  Hence those supported types lists (for client/server) only included the new 2.0 filter/interceptors and only later I started adding the support for the wider set of standard types.
But  anyway, the patch looks fine, except that the supported contracts still need to be passed in, this is to protect Server-side Configuration from accepting ClientRequest/ResponseFilter and the client side Configuration - from ContainerRequest/ResponseFilter.   These supported types lists may need to be expanded for the client and server (to include all other standard types which make sense on the client and the server) such that a provider can not be registered under SomeNonJaxrsContract - which should be rejected
Thanks

Hmm...May be the registration of the unknown types should not be blocked as I suspect this is how many users are already registering CXF specific providers with register(...) without the base implementation having any knowledge of the scope of such providers.
So IMHO it should only be limited to blocking the well-known server interfaces in the client scope and vice versa.

Hi @sberyozkin - that makes sense.  I'll update with a new commit shortly.  Thanks!

@sberyozkin I updated the code with your suggestions.  Do you want to take another look?
I also fixed the isEnabled behavior - we also ran into a couple of TCK/CTS failures with that method.

One failure - org.apache.cxf.systest.ws.rm.SequenceTest.testOnewayAnonymousAcksSuppressedAsyncExecutor - which I've seen fail in other builds (like from #380) that are unrelated to these changes, so I think it should be safe to merge.


Feature Request: Set-AzLabUser Additional Usage Quota

The ability to change a user's individual quota would be very helpful when managing class of students.
Example: Set-AzLabUser -User $user -AdditionalUsageQuota PT2H

This should be addressed when we merge in changes recently made from private repo.  @petehauge  - please  #confirm this once merge is done.

This change has been added in commit 1e8a527f1a648e44ab3e296b7989b1f267c5454c


run Gratipay 160

159

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/23053646-run-gratipay-160?utm_campaign=plugin&utm_content=tracker%2F85909&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F85909&utm_medium=issues&utm_source=github).

Onit.

Reviewed teams in https://github.com/gratipay/inside.gratipay.com/issues/272.

No users to review.

I changed the paypal address for https://gratipay.com/~sudoroom/, because they added a different address and it's obviously the one they want to use for paypal, but they didn't actually set it for paypal.

Backup taken and verified.

Script started and canceled.

[gratipay] $ heroku config -s | run_dammit /dev/stdin -c ./env/bin/python ./bin/migrate-tips.py
'introtopython' already migrated.
'duo' already migrated.
'Gratipay' already migrated.
'sudo-room' already migrated.
'nuvola-player' already migrated.
'cyberpipe' already migrated.
'mojolicious' already migrated.
'pageres' already migrated.
'sublimelinter' already migrated.
'citizens-cooperative' already migrated.
'catapultpgh' already migrated.
'sudomesh' already migrated.
'perl-maven' already migrated.
'exercism' already migrated.
'devdocs' already migrated.
'weblate' already migrated.
'pillow' already migrated.
'simplytest-me' already migrated.
'json-resume' already migrated.
'encommuns' already migrated.
'perlweekly' already migrated.
'cuberite' already migrated.
'totalism-hackbase' already migrated.
'bevry' already migrated.
Migrated tips for 'cpan-io'
Migrated tips for 'shields'
Migrated tips for 'kivy'
'gammu' already migrated.
Migrated tips for 'knopproject'
'the-charis-project' already migrated.
'northern-plains-athletics' already migrated.
Migrated tips for 'libravatar'
'debian-lts-by-freexian' already migrated.
'doit' already migrated.
'the-mountain-spirit' already migrated.
'jshttp' already migrated.
'aegirproject' already migrated.
'survivejs' already migrated.
'nanoc' already migrated.
Migrated tips for 'sailor'
Migrated tips for 'cider'
Migrated tips for 'wdrl'
Migrated tips for 'cpan-book'
'ucoin' already migrated.
Migrated tips for 'act'
Done.
[gratipay] $

Cleared a couple users for Gratipay 1.0 payouts.

Bah. :-(
When I canceled payday at , I simply canceled the tail. :-(

Migrated tips didn't take effect, nor 1.0 payouts. :-(

Script ran for a minute (0:01:53.025820).

Did payout for 10 participants.

Those failed. They'll be included in MassPay, right?

MassPay fee cap errors ...

Got it.

MassPay done and posted back for 31 users. One still pending.

Escrow shuffled. Leaving money in Balanced since we'll need it there to issue refunds in August (#3539).

Logs uploaded in https://github.com/gratipay/logs/commit/d5c45706329516f8e4e81c08f41fe056a176440b.


video streaming not working while coming to forground

My video calling app working good using the OpenWebRTC, But while going to back ground in the middle of the video call , and came back  i can here the voice but not screens are blank. I think camera is not working.
Any help will be appreciated.

@sibineshMc Hello, did you find a solution for this problem? I am facing the same issue. Any help will be appreciated


Client is connected and says "Session started" but server is silent

https://www.dropbox.com/s/uqyssvae6f4k5np/Screenshot 2015-07-15 16.30.10.png?dl=0
I'm starting a server in a vagrant box (with port forwarding 8888 => 8888), maybe that could be related?
My server code is almost identical to the example in the README.md:
var flo = require('fb-flo'),
    fs = require('fs'),
    path = require('path'),
    exec = require('child_process').exec;

var server = flo('./client/', {
  // host: 'localhost',
  port: 8888,
  dir: './client/',
  glob: ['./client/**/*.js', './client/**/*.css', './client/**/*.html']
}, resolver);

server.once('ready', function() {
  console.log('Server is ready!');
});

server.on('connection', function (stream) {
  console.log('Ah, we have a user!');
});

function resolver(filepath, callback) {
  exec('grunt debug', function (err) {
    if (err) {
      throw err;
    }
    console.log('executed lightdebug', filepath);
    callback({
      resourceURL: 'static/' + path.extname(filepath),
      contents: fs.readFileSync('static/' + path.extname(filepath)).toString(),
      update: function(_window, _resourceURL) {
        // this function is executed in the browser, immediately after the resource has been updated with new content
        // perform additional steps here to reinitialize your application so it would take advantage of the new resource
        console.log("Resource " + _resourceURL + " has just been updated with new content");
      }
    });
  });
}

ok, turns out I was missing verbose: true config option in my var server = flo( ... ) call.


Debug Console render newlines unnecessary

Version: 1.33.0 (system setup)
Commit: 0dd516dd412d42323fc3464531b1c715d51c4c1a
Date: 2019-04-04T15:14:28.026Z
Electron: 3.1.6
Chrome: 66.0.3359.181
Node.js: 10.2.0
V8: 6.6.346.32
OS: Windows_NT x64 10.0.17763
Run the following the Java program multiple times, DEBUG CONSOLE sometimes add some newlines unnecessary.
PrintfTest.java:
import java.util.stream.IntStream;

public class PrintfTest {
    public static void main(String[] args) {
        IntStream.range(0, 10).forEach(it ->
            System.out.format("This is iteration %d. Hello VS Code! Hello RedHat!%n", it));
    }
}

DEBUG CONSOLE output:
This is iteration  <- Unnecessary newline here.
0. Hello VS Code! Hello RedHat!
This is iteration 1. Hello VS Code! Hello RedHat!
This is iteration 2. Hello VS Code! Hello RedHat!
This is iteration 3. Hello VS Code! Hello RedHat!
This is iteration 4. Hello VS Code! Hello RedHat!
This is iteration 5. Hello VS Code! Hello RedHat!
This is iteration 6. Hello VS Code! Hello RedHat!
This is iteration 7. Hello VS Code! Hello RedHat!
This is iteration 8. Hello VS Code! Hello RedHat!
This is iteration 9. Hello VS Code! Hello RedHat!

Dump the DAP event:
{"event":"output","body":{"category":"stdout","output":"This is iteration ","type":"output"},"seq":12,"type":"event"}
{"event":"output","body":{"category":"stdout","output":"0. Hello VS Code! Hello RedHat!\r\nThis is iteration 1. Hello VS Code! Hello RedHat!\r\nThis is iteration 2. Hello VS Code! Hello RedHat!\r\nThis is iteration 3. Hello VS Code! Hello RedHat!\r\nThis is iteration 4. Hello VS Code! Hello RedHat!\r\nThis is iteration 5. Hello VS Code! Hello RedHat!\r\nThis is iteration 6. Hello VS Code! Hello RedHat!\r\nThis is iteration 7. Hello VS Code! Hello RedHat!\r\nThis is iteration 8. Hello VS Code! Hello RedHat!\r\nThis is iteration 9. Hello VS Code! Hello RedHat!\r\n","type":"output"},"seq":13,"type":"event"}

It looks like vscode debug console renders an extra newline for each outputEvent even if it doesn't end with CRLF.

Please try it out in vscode insiders tomorrow and let us know if the fix fixed the issue for you (it should)

Thanks, the issue disappeared in 2019-04-12 insider version.

Great, adding verified label. Thanks for letting us know.

I Had same problem and it solved with this issue.
Thanks


Add "GreenShop" prefix for each namespace

To preserve similarity for each project in the solution, I think we need to add "GreenShop" prefix for each namespace.

Should be started after #64 is closed - this necessary refactoring will change a major part of the codebase.


generic_associated_types stabilized

The generic_associated_types is not only no longer marked incomplete but has in fact been stabilized and is no longer necessary to specify.
Please also consider updating the README accordingly.
Also, adding a return_position_impl_trait_in_trait mode, enabled via optional feature on this crate, would be absolutely hilarious.

I might look into it, but AFAICT it's only a matter of time before rustc itself finishes async_fn_in_traits. That said, PRs are welcome though.


add const generic numeric compact deserialization helpers

Clippy no problem, as for types - I added const generics available as of now in stable: meaning String and f32 is not implemented yet

Hi again, and thank you for the contribution! Sorry, I forgot to re-review it again after we last spoke.


New function to create: float_source/.mat file

At this point, the python software still relies on Matlab or user own function to create the crucial float_source/<WMO>.mat file file.
For users who want to try or use the Python software, we need to provide a function that read the netcdf file and produce that OWC specific file !
This should not be too complicated, I see that the file the test "3901960.mat" file has the following arrays:
__header__ : b'MATLAB 5.0 MAT-file, Platform: GLNXA64, Created on: Mon Feb 25 13:18:03 2019'
__version__ : 1.0
__globals__ : []
PROFILE_NO : [[ 1  2  3  4  5  6  7  8  9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24
  25 26 27 35 36 37 38 39 40 41 42]]
LAT : (1, 35)
LONG : (1, 35)
DATES : (1, 35)
PRES : (205, 35)
TEMP : (205, 35)
PTMP : (205, 35)
SAL : (205, 35)

@kamwal @cabanesc should the Python function create_float_source be similar to the matlab one here: https://github.com/cabanesc/DM_FLOATS/blob/684e723b856dcf6a27c9e4910439d1bac2899a7d/LPO_CODES_ATLN_NEW/create_float_source.m

I see from the Matlab code that raw data could be fetched using argopy and then processed by pyowc

List of tasks for this function:

[ ] fetcher netcdf data
[ ] recalculates salinity from the adjusted pressure if necessary.
[ ] calculates potential temperature
[ ] converts the dates (juld> year with decimals)
[ ] converts longitudes
[ ] harmonizes QC (pres, temp, psal), excludes outliers
[ ] ensures that data which are at about the same pressure have the same vertical index for all cycles (which is not necessarily the case if there are changes in resolution from one cycle to the other, incomplete profiles ...)

Here is one proposition:
Raw data fetching is done with https://github.com/euroargodev/argopy
import os
import argopy
import gsw

def add_teos10_pt(this):
    """ Add PTEMP to a xr.Dataset"""

    # Get variables as numpy arrays:
    psal = this['PSAL'].values
    temp = this['TEMP'].values
    pres = this['PRES'].values
    lon = this['LONGITUDE'].values
    lat = this['LATITUDE'].values
    f = lat

    # Coriolis
    f = gsw.f(lat)

    # Depth:
    depth = gsw.z_from_p(pres, lat)

    # Absolute salinity
    sa = gsw.SA_from_SP(psal, pres, lon, lat)

    # Conservative temperature
    ct = gsw.CT_from_t(sa, temp, depth)

    # Potential Temperature
    pt = gsw.pt_from_CT(sa, ct)

    # Back to the dataset:
    this['PTEMP'] = xr.DataArray(pt, coords=this['TEMP'].coords)
    this['PTEMP'].attrs['standard_name'] = 'Potential Temperature'
    this['PTEMP'].attrs['unit'] = 'degC'

    return this

def create_float_source(this, file_name):
    """ Create a Matlab file to start the OWC analysis workflow

        From an Argo xarray dataset (as returned by argopy), create a Matlab file to start the OWC analysis workflow.

        Matlab file will have the following variables:
            DATES (1xn, in decimal year, e.g. 10 Dec 2000 = 2000.939726)
            LAT   (1xn, in decimal degrees, -ve means south of the equator, e.g. 20.5S = -20.5)
            LONG  (1xn, in decimal degrees, from 0 to 360, e.g. 98.5W in the eastern Pacific = 261.5E)
            PRES  (mxn, dbar, from shallow to deep, e.g. 10, 20, 30 ... These have to line up aLONG a fixed nominal depth axis.)
            TEMP  (mxn, in-situ IPTS-90)
            SAL   (mxn, PSS-78)
            PTMP  (mxn, potential temperature referenced to zero pressure, use SAL in PSS-78 and in-situ TEMP in IPTS-90 for calculation, e.g. sw_ptmp.m)
            PROFILE_NO (1xn, this goes from 1 to n. PROFILE_NO is the same as CYCLE_NO in the Argo files.)
    """
    # Add potential temperature:
    if 'PTEMP' not in this:
        this = add_teos10_pt(this)

    # Transform to a collection of profiles:
    dsp = this.argo.point2profile()

    # Read coordinates:
    DATES = np.array([toYearFraction(d) for d in pd.to_datetime(dsp['TIME'].values)])[np.newaxis,:]
    LAT = dsp['LATITUDE'].values[np.newaxis,:]
    LONG = owc.utilities.wrap_longitude(dsp['LONGITUDE'].values)[np.newaxis,:]
    PROFILE_NO = dsp['CYCLE_NUMBER'].values[np.newaxis,:]

    # Read measurements:
    PRES = dsp['PRES'].values.T # (mxn)
    TEMP = dsp['TEMP'].values.T # (mxn)
    PTMP = dsp['PTEMP'].values.T # (mxn)
    SAL = dsp['PSAL'].values.T # (mxn)

    # Create Matlab dictionnary to save:
    mdata = {}
    mdata['PROFILE_NO'] = PROFILE_NO.astype('uint8')
    mdata['DATES'] = DATES
    mdata['LAT'] = LAT
    mdata['LONG'] = LONG
    mdata['PRES'] = PRES
    mdata['TEMP'] = TEMP
    mdata['PTMP'] = PTMP
    mdata['SAL'] = SAL

    # Save it
    savemat(file_name, mdata)

    #
    return mdata

Usage:
# Fetch float data with argopy:
wmo, cyc = 6902746, np.arange(1, 16)
loader = ArgoDataFetcher(cache=1, mode='standard').profile(wmo, cyc)
ds = loader.to_xarray()

# And create OWC matlab file:
fname = os.path.sep.join(["/", "float_source", "%i.mat" % wmo])
mdata = create_float_source(ds, fname)

closing because this method was implemented at argopy by https://github.com/euroargodev/argopy/pull/142

It's all explained here: https://argopy.readthedocs.io/en/latest/data_quality_control.html#salinity-calibration


Fix formatting, grammar, and style in Yo integration docs.

A few improvements to https://zulip.com/integrations/#yo-app .

Automated message from Dropbox CLA bot
@brainwane, thanks for the pull request! It looks like you haven't yet signed the Dropbox CLA. Please sign it here.

Merged!  Thanks @brainwane!

Automated message from Dropbox CLA bot
@brainwane, thanks for signing the CLA!


Improvement of specimen description

This PR introduces the following changes:

Additional checks to ensure that processing_type and processing_procedure match
Support for staining substances specified as text
New SpecimenProcessing class to describe specimen processing

Very unfamiliar with this part of the standard, but why does the processing_type even need to be passed if it's determined by the type of the processing_procedure?

You are right, it's not really required. I realized that having the two parameters (processing_type and processing_procedure) is error prone and therefore added checks to ensure that the arguments match. We could now deprecate processing_type. However, since it's currently the first parameter, we would break the API even if we would make it optional for the purpose of deprecation (since we would need to move the parameter). Thoughts?

Hmm, I'd be tempted to deprecate as gracefully as we can as we are still pre 1.0 but I defer to your judgement

@CPBridge I deprecated the parameter and added a paragraph to the release notes (f8ddb989aa039c2944b2746eff46f4f84660eae7).


Add permissions to read pods

The controller needs to read pods, add permissions.
Fix #39

:+1:

👍

:+1:

:+1:


semanticdb-scalac silently disables scalamacros/paradise

Minimized repro https://github.com/olafurpg/inThisBuild/commit/56371fac9f2f24316c9002eb9d3a17274c62112f
Execute sbt a/run
[error] [E2] a/src/main/scala/a/A.scala
[error]      not enough arguments for method asJson: (implicit encoder: io.circe.Encoder[a.Bar])io.circe.Json.
[error]      Unspecified value parameter encoder.
[error]      L10:  println(Bar(13, "Qux").asJson)
[error]      L10:                         ^
[error] [E1] a/src/main/scala/a/A.scala
[error]      could not find implicit value for parameter encoder: io.circe.Encoder[a.Bar]
[error]      L10:  println(Bar(13, "Qux").asJson)
[error]      L10:                         ^
[error] a/src/main/scala/a/A.scala: L10 [E1], L10 [E2]
[error] (a/compile:compileIncremental) Compilation failed

Commenting out addCompilerPlugin(semanticdb) makes the program compile and run.
Originally reported by @ngbinh in https://gitter.im/scalacenter/scalafix?at=59e5e2d9b20c64242911e7d3

Possibly related https://github.com/scalameta/scalameta/issues/1072

Wondering if there is a work around for this? It is blocking me from using scalafix :(

There's no workaround for this issue yet @ngbinh :/ I will try to take a look later this week, it is indeed blocking many from using scalafix!

It seems that it matters in which order the plugins are loaded, if -Xplugin:semanticdb-scalac  comes before -Xplugin:paradise then I'm unable to reproduce the problem. I can only reproduce the problem when -Xplugin:paradise comes before -Xplugin:semanticdb-scalac. A workaround for this problem might be to reorder the addCompilerPlugin(paradise) statement so that it is evaluated latest. I have an idea how to fix this problem permanently.

ok, will try it out

Let me know if that helps @ngbinh You can validate the order of the plugins with show compile:scalacOptions

I have a pending fix for this problem 🎉

It would be a bit complicated for me because we add addCompilerPlugin(paradise) through an in house sbt plugin (so it's applied to all our projects) and sbt-scalafix through addSbtPlugin("ch.epfl.scala" % "sbt-scalafix" % "0.5.3") so not sure how I can control the order

Something like this should do the trick
scalafixEnabled := false // sbt-scalafix does addCompilerPlugin behind the scenes if set to true
 addCompilerPlugin("org.scalameta" % "semanticdb-scalac" % "2.0.1" cross CrossVersion.full)
addCompilerPlugin(paradise)
scalacOptions += "-Yrangepos"

I plan to remove the automatic setup of addCompilerPlugin in sbt-scalafix and let users do it in 0.6 onwards https://github.com/scalacenter/scalafix/pull/419

ok, will try it out

Pending PR to fix this issue in #1143

Opps, I am blocked because we already upgraded to scala 2.12.4. Will downgrade and try this out

I'm working on adding 2.12.4 support, it's not an easy upgrade for us since many things have changed in typer since 2.12.3.

Pending PR adding 2.12.4 support https://github.com/scalameta/scalameta/pull/1144


[VL] Refactor getMetrics to decrease metrics related redundant code

What changes were proposed in this pull request?
It seems to be a better way to use enum, it makes adding a new metric item easier and the code is also simpler.
(Please fill in changes proposed in this fix)
(Fixes: #ISSUE-ID)
How was this patch tested?
(Please explain how this patch was tested.


[SPARK-48433][BUILD] Upgrade checkstyle to 10.17.0

What changes were proposed in this pull request?
The pr aims to

upgrade checkstyle from 10.15.0 to 10.17.0.
clean some outdated comments.

Why are the changes needed?
https://github.com/checkstyle/checkstyle/releases/tag/checkstyle-10.17.0
https://github.com/checkstyle/checkstyle/releases/tag/checkstyle-10.16.0
Does this PR introduce any user-facing change?
No.
How was this patch tested?

Manually test:

sh dev/lint-java

Pass GA.

Was this patch authored or co-authored using generative AI tooling?
No.

Merged into master for Spark 4.0. Thanks @panbingkun


Manually test interoperability with JS implementation

https://github.com/relaycorp/vera-js

IT ALL WORKS!!! 💪🏾 🚀 🎉


Cannot set maximum up/down speed in v2.0

Good afternoon everyone,
Maybe it is just me being silly, but it seems like I cannot find the way of setting maximum up/down speed in v2.0. However, that was possible in v1.6.
Waiting for any suggestions and help.
Kind regards,
Anton Aleksandrov

Thanks, mate.
When you are done, make comment here and I will close this issue


Update add.phtml

If element has no label don't create "label" tag, eg. for csrf element.
Now for csrf element PHP show warning like this Warning: Illegal offset type in .../vendor/zendframework/zendframework/library/Zend/I18n/Translator/Translator.php on line 441

The change was applied to the repo history.


Added Linear,Binary Search & Shell sort in Python and Palindrome in JAVA

Added Linear,Binary Search & Shell sort in Python and Palindrome in JAVA

@codingCapricorn thanks for your contribution but this issue is been already assigned to someone else. you can check up other issues .


Workflow release ?

Hi,
I think the release workflow is not working well.
In Github Actions, there is "Galaxy-NG Roles Import"  workflow in Green Status but :
With this requirements.yaml :
---
roles:
- name: l3d.gitea
  version: v3.4.1

And this command installation : ansible-galaxy role install -r requirements.yaml , I have this issue :
ansible-galaxy role install -r requirements.yaml --force
Starting galaxy role install process
- downloading role 'gitea', owned by l3d
[WARNING]: - l3d.gitea was NOT installed successfully: - the specified version (v3.4.1) of l3d.gitea was not found in the list of available versions ([{'id':
'9686e825-fe2e-4e3e-bfc1-1ec7ce9e1b14', 'name': 'v1.0.0', 'version': '1.0.0', 'created': '2021-03-20T23:13:20.993880Z', 'modified': '2021-03-20T23:13:20.993907Z', 'commit_date':
'2021-03-20T19:08:49-04:00', 'commit_sha': '216088b15f6bc83f14d08f278127491d5c81dfb1', 'download_url': 'https://github.com/roles-ansible/ansible_role_gitea/archive/v1.0.0.tar.gz'},
{'id': 'd7521006-a46f-4826-9011-bd59ec601743', 'name': 'v1.1.0', 'version': '1.1.0', 'created': '2021-03-21T01:37:51.331318Z', 'modified': '2021-03-21T01:37:51.331345Z',
'commit_date': '2021-03-20T21:35:40-04:00', 'commit_sha': '8ed69febc11e1cbfee490fb488f350d8653e98de', 'download_url': 'https://github.com/roles-
ansible/ansible_role_gitea/archive/v1.1.0.tar.gz'},
[...]
{'id': '16d6d717-63cc-49df-80da-d2d130b463b4', 'name': 'v3.3.0', 'version': '3.3.0',
'created': '2023-08-29T23:14:27.594283Z', 'modified': '2023-08-29T23:14:27.594311Z', 'commit_date': '2023-08-29T19:10:12-04:00', 'commit_sha':
'20d8a17f84eb3e23de3402467d0fe344c75da86d', 'download_url': 'https://github.com/roles-ansible/ansible_role_gitea/archive/v3.3.0.tar.gz'}]).
ERROR! - you can use --ignore-errors to skip failed roles and finish processing the list.

This error shows that the release v3.3.0 is the last on ansible-galaxy (that can be verified here :https://galaxy.ansible.com/ui/standalone/roles/l3d/gitea/versions ) .
Do you have an idea why ? And how use the latest version with galaxy ?
Thanks :)

Hi !
I just change l3d.gitea to ansible-roles.gitea and that works well ! :)
Is the workflow's will is to push at ansible-roles.gitea AND l3d.gitea ? May be close / archive l3d.gitea repo and redirect to the "real" main repo ?


Added topic configuation, API support for logging, further tests, extra documentation

This became something of a full rewrite due to our requirements and I could not see any other way to get in touch.
If you would rather cherry-pick changes, I am happy to work with you and carve out what you are insterested in.

sorry its been an intense few weeks, will get to this, just din't want to leave it in radio silence


Users want a way to configure Mappings generated from K8s Ingress resources

Describe the bug
When using Ingress + Mapping annotation  together to

get ExternalDNS to create the required DNS records
set grpc: True to support HTTP/2-only upstreams

Ambassador sets up two Envoy clusters for the given DNS record, effectively creating a 50/50 traffic split. This breaks in our use-case as the Ingress-driven route isn't configured for HTTP/2-only upstream, causing 50% of the connections to fail.
Based on my reading of the relevant docs it sounds like this scenario should be supported.
To Reproduce
Steps to reproduce the behavior:

Apply the following Ingress with Mapping annotation:

kind: Ingress
apiVersion: networking.k8s.io/v1beta1
metadata:
  name: test-browser
  namespace: test
  annotations:
    kubernetes.io/ingress.class: ambassador
    getambassador.io/config: |
      ---
      apiVersion: ambassador/v1
      kind: Mapping
      name: test-browser
      service: http://test-browser.test:8000
      host: test-browser.foo.com
      grpc: True
      prefix: /
      rewrite: /
spec:
  rules:
    - host: test-browser.foo.com
      http:
        paths:
          - backend:
              serviceName: test-browser
              servicePort: 8000

Check that Ambassador sets up a 50/50 traffic split instead of merging Ingress and Mapping
Send traffic through, observe ~50% of traffic failing.

Expected behavior
Ambassador merges Ingress and Mapping definition into a single Envoy cluster.
Versions (please complete the following information):

Ambassador: 1.5.5
Kubernetes environment: EKS
Version: 1.16.8

Additional context
We're currently using a work-around and annotating the Ambassador K8S service with the external-dns.alpha.kubernetes.io/hostname: key listing all the DNS names we want pointed to Ambassador, but this effectively means all the DNS configuration needs to be done at the Ambassador service level, which isn't sustainable long term.

Yeah, I see what's happening here. Hmm. @concaf, any thoughts? Could we notice that a Mapping is defined in the Ingress annotation and then not create a new one? Is that a terrible idea for other reasons? 🤷♂

Not stale.

I dont think it is stale.
Like if you want to bypass_auth or any other setting on ingress how would you do that?

Not stale.

@kflynn @concaf would it be possible to look into this again?
My use case is that I want to create an external-dns entry from the host value in my Mapping, but that isn't currently supported. There is a PR to support Ambassador Host as a external-dns source but not a Mapping: https://github.com/kubernetes-sigs/external-dns/pull/1642
If that isn't supported my idea would be to create both a Kubernetes Ingress and an Ambassador Mapping but like stated above, they are currently canary-ing.


Batch date edit should close when all weeks are unchecked an no events are left to edit

Reassigning to @Coenego for review.

Coverage remained the same at 100.0% when pulling e4aa27881ec394f5f6ab811865011a2cafb1c5c1 on bp323:issue-180 into 506fb37a5d18c0eb0329906e97591d18d204e8a0 on CUL-DigitalServices:master.


Add typing_extensions to package requirements

It's a requirement for backporting to older python versions, but we
didn't include it, and it wasn't caught in CI because mypy, a dev
dependency, includes it as a requirement.

[X] Have you added to CHANGELOG.md for this PR?

Codecov Report

Merging #50 (5a747a0) into main (7b184b1) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main       #50   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            6         6
  Lines          134       134
=========================================
  Hits           134       134

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 7b184b1...5a747a0. Read the comment docs.


Develop admin page

I believe salasks is working on a mock-up. Based off this mock-up, develop a admin template to edit a single (or multiple?) location

What do you need to close this issue? If you give me a detailed instruction, I will see if I could take.


write digest section in vr spec

This section is under review. Expanded writeup to follow decision in #58.


fix(@embark/rpc-manager): implement missing RPC modifier for eth_sign

This is actually not a WIP but a fix.
Let's wait for #2050 to land first. This one then needs rebase.
Thanks @michaelsbradleyjr for helping implementing this!

I update the commit message and PR title; but since we're waiting on #2050 before merging this one, I applied the don't merge yet label.

Thanks @emizzle! I'll make all those needed changes post #2050 being merged and prior to this PR being merged.

It does work correctly in dapps/tests/app.
In the case of the demo, there's just the one dev "node account", embark isn't managing any accounts.
https://github.com/embark-framework/embark/blob/5edcc42799888e578a987f5e3090f3bd0a293d38/packages/plugins/rpc-manager/src/lib/eth_signData.ts#L37
That check is too simple, I think. Either there or in a related section of code we need to consider whether the account is a "node account" and if so allow the request to pass through to the ethereum node.

@PascalPrecht I just pushed a WIP commit that fixes the problem. If you're happy with it, please squash it into the conventional commit; at that point (assuming CI lights are green), we can remove the don't merge yet label and land this in master.

Squashed, rebased and updated. Waiting for CI to be green.


TestPlan status update task to set the appropriate states to TestPlans

Description:
Currently, when someone aborts a jenkins pipeline job, the created test-plans, test-scenarios and testcases will be in invalid states (running/pending ect) forever. Thus, we need a way to set appropriate states to testplans, test-scenarios and testcases as it affects the user experience in such cases.
Affected Product Version:
0.9.0-m16

Fixed in PR #592


Error handling could be improved

When translating "error" from 3 to 4 is kind of broken. It works fine as long as you do not something like the URL or the Hostname. I.e. in vcl_recv:

   error 404 "Not Found";

   return (synth(404, "Not Found"));

but, this example does not work (req.http.host would not work either):

   error 751 "http://" + req.url;

   return (synth(751, "http://")) + req.url;

as we should expect:

   return (synth(751, "http://" + req.url));

We understand this as a syntax error that can easily be fixed. Would you welcome such an addition?

I thought I fixed this. 😞
Feel free to submit a PR if it's still happening.

PR: https://github.com/fgsch/varnish3to4/pull/7


Upgrading to 3.3.0 from 3.3.0-next.62 breaks proxied ws connections

Describe the bug
For the past week I've been working with<EMAIL_ADDRESS>to use typescript 3.7 features. I just upgraded to 3.3.0 as it was just released. (EDIT: Upgrading to 3.3.0-next.80 causes the same issue as 3.3.0)
My application uses the package.json proxy setting to proxy both http and ws connections. This has been working fine, but upgrading to 3.3.0 causes the socket connections to break. Downgrading to 3.3.0-next.62 causes it to start working again.
Did you try recovering your dependencies?
Yes - I deleted node_modules and package-lock.json and reinstalled. The same result was encountered. I am also on the latest npm version (which still works with 3.3.0-next.62
Which terms did you search for in User Guide?

I searched for websocket proxy issues - the closest I found was issue 6497 but this does not seem to be the same.
Environment
System:
    OS: Windows 10 10.0.18362
    CPU: (8) x64 Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz
  Binaries:
    Node: 13.3.0 - C:\Program Files\nodejs\node.EXE
    Yarn: Not Found
    npm: 6.13.2 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Edge: 44.18362.449.0
    Internet Explorer: 11.0.18362.1
  npmPackages:
    react: ^16.12.0 => 16.12.0
    react-dom: ^16.12.0 => 16.12.0
    react-scripts: ^3.3.0 => 3.3.0
  npmGlobalPackages:
    create-react-app: Not Found

^ as a note to the above, I was on node 12 when I first encountered this error, but checked if an upgrade would resolve the problem.
Steps to reproduce

Upgrade react-scripts with npm install --save-dev<EMAIL_ADDRESS>Add a proxy value in package.json to match a local service that serves http and ws (eg. "proxy": "http://localhost:8080/")
Ensure your web app makes some connection to the proxied websocket
Run the app with npm start and view the app

Expected behavior
The proxied websocket connection should behave normally.
Actual behavior
Console logs output the following:
The connection to ws://localhost:3000/subscriptions was interrupted while the page was loading.
Firefox can’t establish a connection to the server at ws://localhost:3000/subscriptions.

in Chrome, a similar log is output:
WebSocket connection to 'ws://localhost:3000/subscriptions' failed: Error during WebSocket handshake: Unexpected response code: 400

Can reproduce on Chrome without proxy.  Tried to visit dev server and got an error like this.

I have similar problems, 3.3.0-next.62 worked while 3.3.0 does not.
For the websocket connection I am using vertx3-eventbus-client client-side and the java-implementation of vertx is used server-side.
When trying to make a connection the upgrade request fails with HTTP-400.
One obvious difference in the commandline output of npm start is that the output of the broken version contains new entries from the WebpackDevServer at the beginning ([WDS] ...) .

Same problem here, it works fine with 3.2.0 and breaks with 3.3.0 with an WebSocket connection to 'ws://localhost:3000/socket.io/?EIO=3&transport=websocket&sid=ZuPVIkaei-I3cSozAAAH' failed: Error during WebSocket handshake: Unexpected response code: 400 error.
I'm using Socket.io, but it seems this breaks on all websocket implementations.

I'm seeing somewhat different symptoms, however it seems likely to be related - on 3.2.0 proxying worked perfectly, however on 3.3.0 proxied websocket connections sit in pending for over a minute on chrome before the connection is established. Interestingly, Firefox is somewhat faster, around 20s before the connection is established.

When launching in HTTPS, the client tries to connect to the dev server with ws (and the browser app doesn't start) instead of wss.
Downgrading to CRA 3.2.0 fixed this.

Got the same issue
SecurityError: Failed to construct 'WebSocket': An insecure WebSocket connection may not be initiated from a page loaded over HTTPS

webpackHotDevClient.js:60 Mixed Content: The page at 'https://local.smth.com:3000/' was loaded over HTTPS, but attempted to connect to the insecure WebSocket endpoint 'ws://local.smth.com:3000/sockjs-node'. This request has been blocked; this endpoint must be available over WSS.
Uncaught DOMException: Failed to construct 'WebSocket': An insecure WebSocket connection may not be initiated from a page loaded over HTTPS.
    at Object../node_modules/react-dev-utils/webpackHotDevClient.js

@Lowgain can you put Downgrading back to<EMAIL_ADDRESS>fixes this.  It will be fixed soon. at the top of the issue for anybody new coming in here?

@Lowgain can you put Downgrading back to<EMAIL_ADDRESS>fixes this. It will be fixed soon. at the top of the issue for anybody new coming in here?

Sure - all done!

Thanks :)

Oh my God....
I spent over 12H straight surfing the internet , wondering what could be the issue...
Am just gonna downgrade for now..
already wasted too much time on this...

I  also downgraded to 3.2.0, but my builds are now  red because of the security vulnerability @3.2.0

                       === npm audit security report ===

# Run  npm install<EMAIL_ADDRESS>to resolve 1 vulnerability
┌───────────────┬──────────────────────────────────────────────────────────────┐
│ Moderate      │ Cross-Site Scripting                                         │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Package       │ serialize-javascript                                         │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Dependency of │ react-scripts                                                │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Path          │ react-scripts > terser-webpack-plugin > serialize-javascript │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ More info     │ https://npmjs.com/advisories/1426                            │
└───────────────┴──────────────────────────────────────────────────────────────┘

We are also affected but we didn't downgrade, instead we connect to the websocket server directly in development, you don't have to deal with cors with ws so it's okay. However you have to change your ws endpoint url if you want to test it on somewhere else than localhost.

We are also affected but we didn't downgrade, instead we connect to the websocket server directly in development, you don't have to deal with cors with ws so it's okay. However you have to change your ws endpoint url if you want to test it on somewhere else than localhost.

So, can you please share some code of your fix? Im not really sure where to change this ws endpoint..

We run api server on port 4000 and cra on 3000. We have setupProxy.js:
const proxy = require('http-proxy-middleware');

const target = process.env.REACT_APP_API_URL || 'http://localhost:4000/';

module.exports = function(app) {
  app.use(
    proxy('/api', {
      ws: true,
      changeOrigin: true,
      target,
    }),
  );
};

But because of this issue we cannot connect websockets to /api/ws but instead we can connect to ws://localhost:4000/api/ws directly from browser. You lose the benefit of proxy but don't have to downgrade.
const getCorrectProtocol = () =>
  window.location.protocol === 'http:' ? 'ws' : 'wss';

const getWsUri = (path: string) => {
  // Because of https://github.com/facebook/create-react-app/issues/8094 in development we have to connect to API directly
  // websockets don't adhere to same-site policy so no cors necessary
  if (process.env.NODE_ENV === 'development') {
    const apiUrl = process.env.REACT_APP_API_URL?.replace(
      'https',
      'wss',
    )?.replace('http', 'ws');
    return `${apiUrl}${path}`;
  }
  // safari incorrectly implement CSP self keyword for websockets
  // https://github.com/w3c/webappsec-csp/issues/7
  return `${getCorrectProtocol()}://${window.location.host}${path}`;
};

const wsLink = new WebSocketLink({
  uri: getWsUri(GRAPHQL_URI),
  // ...
});

The key is REACT_APP_API_URL env variable that tells browser where our api server is.

Related to webpack/webpack-dev-server#2310
Manually upgrading to webpack-dev-server 3.10.1 fixed it for me.

@OzySky how did you update webpack-dev-server using CRA?

This obviously is not ideal, but at least it fixes it in the mean time.

Install webpack-dev-server@latest
Edit react-script's package.json to<EMAIL_ADDRESS>Delete webpack-dev-server from react-script's node_modules

I don't think suggesting ejecting is a very good idea in this case.  Just wait for the minor release.

When can we expect a release that fixes this issue?

Guys, this just broke our app.. Don't push broken code, please and thank you.

@dankolesnikov You have never pushed broken code right? If you are that great, good for you, but others are just humans that do mistakes.
You can be also more proactive with your brilliant mind and fix the problem instead of waiting for others to do it, you know?

@ianschmitz ws proxying still appears to be broken in our app after having upgraded to 3.3.1 unfortunately.


Add trio[300], async functions should not have a timeout parameter

Easy check, only question mark is if *timeout or **timeout is worthy of raising a problem.
Have not incremented version number, and 300 is a temporary error code until we've sorted out what to do with #17

fixed all :+1:


Test for #9619: "to_python not called when fetching data with .values(...)"

ref.: https://code.djangoproject.com/ticket/9619
#9619 is fixed with Django v1.8 and the change from to_python() to from_db_value()
But there is no unittest for it.
Here i add a test. But i must also add from_db_value() to test existing test model field.

The place to add the test would be tests/from_db_value/tests.py. There's a test for values_list() - I guess one for values() wouldn't hurt.

The place to add the test would be tests/from_db_value/tests.py.

I "moved" it with: https://github.com/django/django/commit/f1e2a12a37e6433c1047066b31f95eb4aa51ec80

no ticket reference needed
chop blank line

changed with https://github.com/jedie/django/commit/a7608b91b75b6353c242debd1a3bf8eaa1dc1178

Newline shouldn't be removed at the end of this line.

Oh, sorry. Fixed with https://github.com/django/django/commit/bc8e8ff8a92e277d806e1a7b0e05cfacb7f846b8

buildbot, test this please.

merged in 9aac99e96d100b34b6daa3a137531eff4f17076e, thanks.


[bug]Embeds Form field not working when inserting data

Laravel Version: 5.5.*
PHP Version: 7.1.*
Laravel-admin: 1.5-dev

Description:
If I set Embeds fields
return Admin::form(ExModel::class, function (Form $form) {
            $form->embeds('value', function (Form\EmbeddedForm $form) {
                $form->text('extra1')->rules('required');
                //$form->email('extra2')->rules('required');
                //$form->mobile('extra3');
                //$form->datetime('extra4');
            });
            $form->display('created_at', 'Created At');
            $form->display('updated_at', 'Updated At');
        });

When I saved as creating, column "value" is null, but when I saved as updating, column "value" is saveing as json.
I investigated "Form.php", and I found the function "isHasOneRelation" in "prepareInsert" is true.
I think the function "isHasOneRelation" is for relationship "hasOne", but using embed, it's true. so, the "value" array converts to flatten dotted string, it's wrong.
How to reslove this?
--
Steps To Reproduce:

@gozhhu
Thanks a comment.
What you say the mean is adding a column before "$form->embeds"?
ex.
return Admin::form(ExModel::class, function (Form $form) {
            $form->hidden('foobar'); // ←add.
            $form->embeds('value', function (Form\EmbeddedForm $form) {
                $form->text('extra1')->rules('required');
                //$form->email('extra2')->rules('required');
                //$form->mobile('extra3');
                //$form->datetime('extra4');
            });
            $form->display('created_at', 'Created At');
            $form->display('updated_at', 'Updated At');
        });

Yes something like that, I added another field before embeds, I have not
tested hidden, I added a text or select field.
On Mon, May 14, 2018 at 11:49 AM, hirossyi73<EMAIL_ADDRESS>wrote:

@gozhhu https://github.com/gozhhu
Thanks a comment.
What you say the mean is adding a column before "$form->embeds"?
ex.
return Admin::form(ExModel::class, function (Form $form) {
$form->hidden('foobar'); // ←add.
$form->embeds('value', function (Form\EmbeddedForm $form) {
$form->text('extra1')->rules('required');
//$form->email('extra2')->rules('required');
//$form->mobile('extra3');
//$form->datetime('extra4');
});
$form->display('created_at', 'Created At');
$form->display('updated_at', 'Updated At');
});
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/z-song/laravel-admin/issues/1998#issuecomment-388689219,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAJVMA7oZRhYmKDmnFAnO4GmVhzEb4krks5tyP6zgaJpZM4TttRl
.


dev: update requirements to avoid snyk vulnerabilities

This definitely won't pass; just a checkpoint until Lasse and I have a conversation with Andreas/Søren.

Will look at this next week.


Function bibtex() doesn't work

I've tested this function with a publication fill and without it and it doesnt work in any way.
Output data give me a KEYERROR: 'ENTRYTYPE'
I dont know if I'm using the function correctly. I'm calling it 'scholarly.bibtex(author['publications'][0]'.
Thanks!

Please provide example code that generated the issue

Please provide example code that generated the issue

author = scholarly.fill(next(search_query))

pub = author['publications'][0]

print(scholarly.bibtex(pub)

I tried it with the publications filled too.
pub = scholarly.fill(author['publications'][0])

print(scholarly.bibtex(pub)

author = scholarly.fill(next(search_query))

pub = author['publications'][0]

print(scholarly.bibtex(pub)

I tried it with the publications filled too.
pub = scholarly.fill(author['publications'][0])

print(scholarly.bibtex(pub)

I was just testing with search_pubs. I had not viewed the page and how it give the information.
If i wanted to take bibtex of a publication of an author, i should take name from author['publications'[n]['bib']['title'] and make a search_pubs of it.
That was my error. Sorry for waste your time.
Closing.

I was just testing with search_pubs. I had not viewed the page and how it give the information.
If i wanted to take bibtex of a publication of an author, i should take name from author['publications'[n]['bib']['title'] and make a search_pubs of it.
That was my error. Sorry for waste your time.
Closing.


Drag and Drop Tree

Hi guys,
Im building a POC for use this library on a project. I was using the Example that is on the github site, and works perfectly fine, but how we can disable the drag and drop of the draw on the div that contains the tree? There is a way to keep it in the center and static?
I have a rootlayout component that draws other things into my page and I want to disable that drag and drop thing.
There is a way to do that?
class TreePocPage extends Component {   render() {     return (       <RootLayout>
           <Tree data={myTreeData} orientation={'vertical'} pathFunc={'step'} />
       </RootLayout>     );   } } export default TreePocPage;
Thanks!

Just discovered, that if you set the zoomable prop as false, that disabled the drag and drop functionality,
But now the tree get draw on a corner of my container div, how do I make the tree get draw on the center?
Thanks!

Never midnd.
Found it at the very bottom of the documentation!
https://codesandbox.io/s/vvz51w5n63
Thanks!

Hi guys,
Im building a POC for use this library on a project. I was using the Example that is on the github site, and works perfectly fine, but how we can disable the drag and drop of the draw on the div that contains the tree? There is a way to keep it in the center and static?
I have a rootlayout component that draws other things into my page and I want to disable that drag and drop thing.
There is a way to do that?
class TreePocPage extends Component { render() { return ( <RootLayout>
 <Tree data={myTreeData} orientation={'vertical'} pathFunc={'step'} />
 </RootLayout> ); } } export default TreePocPage;
Thanks!

Just discovered, that if you set the zoomable prop as false, that disabled the drag and drop functionality,
But now the tree get draw on a corner of my container div, how do I make the tree get draw on the center?
Thanks!

Hallo! I had the same problem and I tried to disable the zoomable prop, but my tree is still dragable somehow.... Did you solve this problem with disable the zoomable prop?
Thanks!


Non projected enums / delegates shouldn't provide IPropertyValue QI

See for repro

Fix is a WindowsRuntimeTypeAttribute check here, but it probably should be combined with optimizations for interfaces for a type as GetCustomAttribute was seen to be expensive in previous profiling.


Change methods that can return null to nullable!

With '?' you can specify that a method or property can return null. Rider indicates a possible null return when calling the method or property.
EXAMPLE:

public string? DoSomething()
{
   // do stuff

   return null;
}

To be honest, on this one I don't have a strong opinion and I guess we should first have a discussion here. The main problem with all nullable warnings are also due to the nullable reference types supported by default in .NET 6. I personally don't like the fact that now we're supposed to just put ? everywhere: method return types, properties and so on. I am thinking of disabling this warning in Rider/VS. We can disable this via an entry in the csproj file. I'm curios to hear other opinions on this matter. You can start extrapolating your thoughts on that.

I disagree. I really like this feature. It will prevent you walking in to NullReferenceExceptions.
If you still want to disable a property and so on you can use ‘!’. It will tell the compiler that this call will never return null even if it still returns null or you can initialise a property with ‘= default!’ or ‘=null!’.
For me the ‘?’ is something like a reminder.
Have a good weekend mate :)

Von: Dan Patrascu-Baba @.>
Gesendet: Sunday, January 23, 2022 1:31:39 AM
An: danpdc/CwkSocial @.>
Cc: Johannes-Max Sorge @.>; Author @.>
Betreff: Re: [danpdc/CwkSocial] Change methods that can return null to nullable! (Issue #8)
To be honest, on this one I don't have a strong opinion and I guess we should first have a discussion here. The main problem with all nullable warnings are also due to the nullable reference types supported by default in .NET 6. I personally don't like the fact that now we're supposed to just put ? everywhere: method return types, properties and so on. I am thinking of disabling this warning in Rider/VS. We can disable this via an entry in the csproj file. I'm curios to hear other opinions on this matter. You can start extrapolating your thoughts on that.
—
Reply to this email directly, view it on GitHubhttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fdanpdc%2FCwkSocial%2Fissues%2F8%23issuecomment-1019384097&data=04|01||e4b532277f594ccfaa6a08d9de07b944|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637784947011162487|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=DynA%2F14vM40LaGk8oXB4E3LukqiitD%2F8XrwpybL5bcA%3D&reserved=0, or unsubscribehttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FANLBICKMXFTA6PVAIBYB7X3UXND6XANCNFSM5MSSXS2A&data=04|01||e4b532277f594ccfaa6a08d9de07b944|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637784947011162487|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=nBMPJ2S%2F0DDntpi26wg3sekdp2MHbxbDQzzNQkHjUOo%3D&reserved=0.
You are receiving this because you authored the thread.Message ID: @.***>

Still coming back to this. I fully agree with you. But I have a more general problem with this approach. In virtually all full OOP languages, reference types are nullable. Every developer should now this and understand the consequences that derive from here. Namely, that you might have to deal with null reference exceptions. And there are very easy ways to deal with that by coalescing for example.
I really have a problem nowadays with all syntactic sugar that theoretically "makes our live easier" but in most cases it ends up by already complicating a lot. And I think your explanation, even though highly accurate just proves my point:

If you still want to disable a property and so on you can use ‘!’. It will tell the compiler that this call will never return null even if it still returns null or you can initialise a property with ‘= default!’ or ‘=null!’.

If you need so many words to explain a new language feature that should theoretically "make our live easier" then, in my opinion, something is fishy with that new feature.
But I also have another point. I feel it's easier to maintain an application that throws a NullReferenceException (and of course that exception is logged properly), then simply now knowing exactly where to look for problems if you don't have expected results in your application.


Updater 2.0 ERROR 'Download request failed with status: 404 Not Found'

I checked the official documentation version 2.0 of the updater update module on October 17, 2024, and found that everything was configured according to the official documentation. However, the error message was ERROR 'Download request failed with status: 404 Not Found', and the configuration was written in both TS and Rust

Next, I will post the core code
Rust：

TS：

I don't know where to start troubleshooting this error from

What's the download url? If you can't share it, can you make sure it works in a private browser tab?
Also, could a proxy be the issue here?

UnexpectedKeyId means something's wrong with the private key / public key / signature - what exactly is a bit hard to say so start by double checking that the private and public keys are set correctly and belong to each other, and that the sig field is the content of the .sig file of the shipped updater artifact.


Update current versions & remove topcat snapshot

Self explanatory. I was primarily meant to be updating the topcat version number, but I noticed some other components were out of date as well.

looks good to me, thanks @louise-davies


Replaced threadId from event with the one from message.

Fixes a bug with cresting drafts for emails sent to self

Bug fix for creating drafts for emails sent to self


Geo commands

Added GeoCommandsMixin for support Redis geo commands since redis 3.2.0

Current coverage is 96.41% (diff: 74.28%)

Merging #177 into master will decrease coverage by 0.52%

@@             master       #177   diff @@
==========================================
  Files            49         51     +2
  Lines          5933       6073   +140
  Methods           0          0
  Messages          0          0
  Branches        445        472    +27
==========================================
+ Hits           5751       5855   +104
- Misses          139        162    +23
- Partials         43         56    +13

Powered by Codecov. Last update 6941cee...34e3e31

build is still failing, please fix flake errors.

Manual run result http://joxi.ru/aD2PGWpiNld9m3

Good job! Thanks

You are welcome


Pass tenantId parameter to PhoenixRDD when reading tables

Added corresponding tests
Cleaned up some test code

Already merged.


[Feature] add new string array encoding

maybe except for NONE 、RC4 、 Base64. we can add "hex" to encrypt strings
like that:
var _0x3628 = [
    '63746F72285C78323272657475',
    '685955655A',
    '7B7D2E636F6E73747275',
    '416C4E4776',
    '7063787768',
    '73706C6974',
    '64684E534B',
    '7461626C65',
    '6E6374696F6E28295C783230',
    '726E5C783230746869735C7832322928',
    '7472616365',
    '6C6F67',
    '6E4B556449',
    '6C656E677468',
    '6170706C79',
    '636F6E736F6C65',
    '746F537472696E67',
    '72657475726E5C783230286675',
    '6944685649',
    '327C317C357C307C337C',
    '6F684D4C46',
    '7759596771',
    ......
];

HEX is too easy for transform to utf-8 text. Maybe we shouldn't do that?
Idk what about RC4. Base64 also the same like HEX (easy transform back)

Best encrypting is that where you use keys.

I think sometimes the easiest way is the most effective routine ヾ(o◕∀◕)ﾉヾ


[atip] Add new steps for searching element by specified attribute

Add new steps to find element by given attribute
Modify the related feature files
Impacted tests(approved):new 0,update 4,delete 0
Unit test platform:[Android]
Unit test result summary:pass 4,fail 0,block 0

LGTM
@cicili please take a review.


I've added an entry for future exe files. However, I'll need to rewrite history to fix this blunder.
Which MUST be done during team synchronization.
The following page covers the procedure, I've done it before but can never remember the syntax.
https://help.github.com/articles/remove-sensitive-data/

Fixed on master


fix: need to provide a table as input

nfnl.config.default now takes a table as input so the docs should show this.

Ah good catch! I think I'll make it so you can just skip the table entirely and also have it set some sensible defaults. This will invalidate this PR but still be related to it.
It's actually a little tricky because I need the user to pass in the path to the current config files containing directory. It's so that certain paths get set up correctly for them using absolute paths to avoid any sort of confusion when editing a file from the wrong directory tree.
So if your nvim is in /foo/bar and you're editing /foo/baz/quuz.fnl and you have a .nfnl.fnl file in /foo/bar AND in /foo/baz then we need to make sure it's the /foo/baz one that's used and all paths are relative to that because THAT's the project you're editing.
It's all about the file you're editing, not the directory Neovim is currently in, which means when you build the config object you need to pass the project directory into it like (config.default {:root-dir "/foo/baz"}) so it can set up the paths correctly.
I need to make that easy for the user to do correctly. Just thinking about that now.

Makes sense!

Alright fixed in a roundabout way! You can now call (config.default) again and it finds the right dir and Just Does The Right Thing on your behalf. So it'll return default config with absolute paths based on the closest parent of a .nfnl.fnl file, i.e. your project root. Thus eliminating all sorts of weird relative path logic. Success! I think!

Running it for myself in nfnl's own repo with no args now gives me:
; eval (current-form): (config.default)
{:compiler-options {}
 :fennel-macro-path "/home/olical/repos/Olical/nfnl/?.fnl;/home/olical/repos/Olical/nfnl/?/init-macros.fnl;/home/olical/repos/Olical/nfnl/?/init.fnl;/home/olical/repos/Olical/nfnl/fnl/?.fnl;/home/olical/repos/Olical/nfnl/fnl/?/init-macros.fnl;/home/olical/repos/Olical/nfnl/fnl/?/init.fnl"
 :fennel-path "/home/olical/repos/Olical/nfnl/?.fnl;/home/olical/repos/Olical/nfnl/?/init.fnl;/home/olical/repos/Olical/nfnl/fnl/?.fnl;/home/olical/repos/Olical/nfnl/fnl/?/init.fnl"
 :fnl-path->lua-path #<function: 0x7f0ef95b3b58>
 :source-file-patterns ["*.fnl" "**/*.fnl"]}

So I'm happy with that, closing this PR but thank for you spotting it and providing an immediate fix to the error. Hope this all makes sense and helps!


"ESP-IDF in Custom CMake Projects" CMake example doesn't build  (IDFGH-4731)

Environment

Development Kit: esp32-s2-saola-1
IDF version: v4.3-dev-2586-g526f68239
Build System: CMake
Operating System: macOS
Using an IDE?: VSCode

Problem Description
The following example doesn't build out of the box:
https://docs.espressif.com/projects/esp-idf/en/latest/esp32/api-guides/build-system.html#using-esp-idf-in-custom-cmake-projects
When running idf.py build, CMake will attempt to build the files with system compiler instead of a cross compiler. The reason is a missing call to __target_set_toolchain.
I had to add the following lines before calling project():
set(IDF_TARGET esp32s2)
set(CMAKE_TOOLCHAIN_FILE $ENV{IDF_PATH}/tools/cmake/toolchain-${IDF_TARGET}.cmake)

project(myprojectname C CXX)

Hi @resetnow,
Thanks for reporting this. Just to check: you mean the "idf_as_lib" example in the code, not the sample CMakeLists.txt file shown in the documentation page?
When building the idf_as_lib example, we provide two wrapper scripts - build.sh and build-esp32.sh. build.sh is intended to build on the host, and build-esp32.sh builds for the embedded target. build-esp32.sh passes the CMAKE_TOOLCHAIN_FILE to the cmake command line and also sets the target.
You're right that it's possible to move these settings into the CMakeLists.txt file, however if doing this then you lose one of the benefits of using "normal" CMake - reusing the same cmake files on multiple target platforms. This is why in the example we demonstrate it with the wrappers.
Is there something else in the examples or the docs that's unclear and should be changed?

Alright, thank you @projectgus, I understand the idea now. Yes, it would be great to mention it in documentation - just the fact that the CMake file is targeted for multiple platforms and thus toolchain need to be specified explicitly, as it is not immediately obvious there's a difference between overridden project() and idf_build_process().
Another difference is the lack of project_description.json generation - it would be good if it was exported in a public API, so that users could write something like:
if (CMAKE_CROSSCOMPILING)
    idf_generate_project_json(OUTPUT ${CMAKE_BINARY_DIR})
endif()

As far as I understand, "monitor mode" needs this file (at least when launched from VS Code).
Thank you for your help :)

closing as an old issue and already explained by @projectgus


Left side disappears on small window width

Thanks for this nice plugin. Would it be possible to provide a possibility to adjust which side (left or right) will disappear / overlap the other?
Cheers,
Andreas

Please refer to README.md, Can I trim the file format and encoding information on narrow windows?.

Hi @itchyny, thanks for the quick response. I have seen that yesterday scanning the README.md and :help lightline section. As I work a lot with diffs and prefer to have long file names shown, I would prefer a solutation that the right part would simple get smaller and smaller (now the left part does). But the left part contains the more important information for me, especially the mode.
Maybe this is not possible but maybe this is only a setting which things are drawn first and second. I haven't had a look into the code but the default statuslines behavior is exactly like that.
It is ok, if you will mark this as "won't fix" but maybe you have a hint for me where to have a look into your code such that I can do some research ;-)

Maybe you can hide the right components (line counts or the percentage) with a little extension with the example config.  A screenshot will help me figure out what's happening and how narrow your terminal is.

To create a customization which will hide some components is of course an option which I already considered doing but I think it is valuable to have a closer look to my problem as hiding would just be a workaround in my opinion.
However, I found the solution myself. Looking again to :help statusline I found the following on item meaning section:
	< -   Where to truncate line if too long.  Default is at the start.
	      No width fields allowed.

So the solution is adding and using following component:
let g:lightline.component = { 'truncateEnd': '%<' }

Thanks anyway for listening and repsonding. You can close the issue if you don't need it anymore. Maybe this is a usecase for the documentation or even a provided option ;-)

@aaschmid Thanks for that.
I added two other settings to make sure the component doesn't show until it's actually needed.
let g:lightline.component = {
			\ 'truncate_here': '%<',
			\ }
let g:lightline.component_visible_condition = {
			\ 'truncate_here': 0,
			\ }
let g:lightline.component_type = {
			\ 'truncate_here': 'raw',
			\ }

With visible_condition always false you can add that component in the regular configuration and it won't ever show a sub-separator. The raw type eliminates any extra spaces between that component and others.


new liquibase baseline

Create a new liquibase baseline and gut the migrations. Switch to test containers for integration-y tests, and disable them at cloud build.
closes #35

As well as building here, the same code is deployed to beta. There are 35 tests (of 195) skipped at cloud build due to test containers not working.


Sequence for cartodb_id incorrectly initialized when importing via gdal CartoDB driver

Importing this way:
ogr2ogr2 \
>   --config CARTODB_API_URL https://rtorre2.cartodb.com/api/v2/sql \
>   --config CARTODB_API_KEY mysecretkey  \
>   -s_srs EPSG:4326 \
>   -t_srs EPSG:4326 \
>   -f CartoDB "CartoDB:rtorre" \
>   -oo X_POSSIBLE_NAMES=lon\* \
>   -oo Y_POSSIBLE_NAMES=lat\* \
>   -overwrite \
>   -dim 2 \
>   country_lat_long.csv

The country_lat_long.csv input file.
then when adding rows I got this error:
{"errors":["PG::Error: ERROR:  duplicate key value violates unique constraint \"country_lat_long_pkey\"\nDETAIL:  Key (cartodb_id)=(1) already exists.\n"]}

it seems like the created sequence is not set to max(cartodb_id) for some reason.

Taking a closer look: the parameter -f CartoDB:rtorre did not match the URL nor the API_KEY (look at the bug desc) so there's something wrong, such as creating the table and/or sequence in the wrong schema.
I tested again with the correct combination and went fine.

What should be done with this ticket then?


Downloads: update GUI/CLI title and description

Most users don't know that GUI means graphical user interface and CLI means command line interface.
The wallet names are "Monero GUI (wallet)" and "Monero CLI (wallet)" and not just "GUI wallet" or "CLI wallet".
It's not stated anywhere in Downloads page that Monero GUI and Monero CLI are free open-source software developed by the community, that anyone can participate in the development (unlike commercial wallets).


[Bug] Datepicker does not the allow null as the default date

Description
Datepicker does not the allow null as the default date
Steps to reproduce the behaviour:

Add a date-picker widget to the canvas
Try setting the default date as {{null}}
It fails the field validation

@vicky-primathon the value should be optional and should display an empty state in the date picker


Support Scala.js ESModule on Bloop

Update Bloop to 1.4.6

@lefou If you want to give a look, this PR is ready for review :-)

@lefou If you want to give a look, this PR is ready for review :-)

@lefou Can this be merged?
There are any blocker left.

@lefou Can this be merged?
There are any blocker left.

Yeah, I will merge it, when CI is green as I needed to fix a merge conflict. Thanky!

Yeah, I will merge it, when CI is green as I needed to fix a merge conflict. Thanky!

I restarted tests multiple times but no luck. Meanwhile, I fixed the CI build issues, see #1117 .
@lolgab Can you rebase this PR on latest master?

I restarted tests multiple times but no luck. Meanwhile, I fixed the CI build issues, see #1117 .
@lolgab Can you rebase this PR on latest master?

@lefou Rebasing worked :-)

@lefou Rebasing worked :-)

Ergh, I had missed this. this line triggers compilation during bloop config generation, that's why I hadn't used the compileClasspath task in the initial implementation, as it drastically slows down the whole thing.
I'll work on a fix.


Fixed schema name matching for schema auth filter

Issue: https://github.com/Sunbird-RC/community/issues/777

@holashchand  build is failing please resolve.


HDDS-5865. Made read retry max attempts and interval configurable.

What changes were proposed in this pull request?
Retry policy when reading keys is hardcoded. Made the read retry max attempts and retry interval configurable in client configuration ozone.client.max.read.retries and ozone.client.max.read.retries
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-5865
How was this patch tested?
Existing UT and integration tests should run as is.

@SaketaChalamchala I recommend resetting master branch in your fork from apache/ozone to avoid more and more Merge branch 'apache:master' into master commits in your PRs.  This can be done in Github UI (Sync fork drop-down button in https://github.com/SaketaChalamchala/ozone/tree/master, choose Discard ... commits), or via CLI.

Thanks for the feedback @adoroszlai . Closing this PR and opened another one https://github.com/apache/ozone/pull/6408 with updated changes. Please review those as well.

@SaketaChalamchala I recommend resetting master branch in your fork from apache/ozone to avoid more and more Merge branch 'apache:master' into master commits in your PRs. This can be done in Github UI (Sync fork drop-down button in https://github.com/SaketaChalamchala/ozone/tree/master, choose Discard ... commits), or via CLI.

Also, will do this from next time. Thanks


Guice injects fields even when injection has not been requested

The following code:
public static class OuterClass {
    @Inject
    protected MiddleClass middleClass;
}

public static class MiddleClass {
    @Inject
    protected InnerClass innerClass;
}

public static class InnerClass {
    private final int number;

    public InnerClass(int number) {
        this.number = number;
    }
}

@Test
public void testGuiceNoRequestInjection() throws Exception {
    Guice.createInjector(new AbstractModule() {
        @Override
        protected void configure() {
            MiddleClass middleClass = new MiddleClass();
            bind(MiddleClass.class).toInstance(middleClass);
            requestInjection(middleClass);
        }
    }).getInstance(OuterClass.class);

}

produces the error "Could not find a suitable constructor in InnerClass" (expected).
Remove the line requestInjection(middleClass).
Expected behavior:
Test passes with no errors, since a binding has been provided for MiddleClass.
Actual behavior:
The same error "Could not find a suitable constructor in InnerClass" is produced, even though injection of MiddleClass has not been requested.

The bug can be worked around by creating a @Provides method:
@Test
public void testGuiceNoRequestInjection() throws Exception {
    Guice.createInjector(new AbstractModule() {
        @Override
        protected void configure() {
        }

        @Provides
        @Singleton
        protected MiddleClass provideMiddleClass() {
            return new MiddleClass();
        }
    }).getInstance(OuterClass.class);

}

The bug can also be worked around by binding to a provider:
bind(MiddleClass.class).toProvider(Providers.of(middleClass));

This is working as intended. @Inject fields are injected when binding using toInstance.  If you don't want the fields injected, bind toProvider(Providers.of(instance))


Add Match Expression completion support

Purpose

With this add the support for Match Expression completion as well as completion inside the match expression.
Resolves #8418

Approach

I noticed that in the recommendation, it is giving you an absolute list of the types in the match completion. What if a user wants to only match one type and then catch the rest with an any? Is there any way to offer both types of completion?

@TylerJewell, What if we follow the same flow we used for annotation attachments? You get individual options, all option filler as well as in this case any type?

Yeah, I think that would be consistent and a good option.

@TylerJewell updated the PR with the suggestions and you can see the working demo in the description


The function does not work

WiFi deauther does not work.
He can't see the network

Only works on 2.4 ghz. Just tested last night, it works.


Display uncertainy values for each match

Summary
This PR adds in the uncertainty and uncertainty_change values to the match rating table so that players can know what their uncertainty was and how much each match impacted their uncertainty values.
I've chosen to not highlight the change values red/green because uncertainty changes aren't inherently good/bad, and the value should only really go down over time.
relates to #255 (and might close it if this is deemed sufficient to resolve the confusion)
Test Evidence

@Jordan-Cottle sorry I updated the ticket as you were working on it. Can you do it as a hover over tooltip? Show people the skill-uncertainty
Keep the columns the same. The main purpose is for people who have match rating 0.0 so it's not useful information except for those people.

The idea is so that this person here could hover over their 0.0 number and see what the skill-uncertainty is. Not sure exactly would the tooltip should say. It could show 3 numbers or just 1. I'll need to see.

I'd need to figure out how to do a tooltip, but I'm guessing fontawesome might have a css class for it already?
Happy to make the change to a tooltip if needed, but I actually kind of like the additional column.
I use this page myself a lot, and often felt like it didn't answer the "What is my uncertainty though?" question very well. So I know I'd personally be interested in having the uncertainty for each match displayed here and I'm not a player with a negative match rating.

Also, I don't think negative match rating is a thing. It looks like everywhere match rating is calculated teiserver is pinning the min at 0.
Example: https://github.com/beyond-all-reason/teiserver/blob/324ba2b0a0e50c82feb3f86eeffbd7db626a2d37/lib/teiserver/battle/libs/balance_lib.ex#L505

Negative match rating is not a thing. So the tooltip is showing skill-uncertainty. Not their match rating. It's useful so that someone can see this value changing rather than staying at 0.
For the uncertainty column, if you really want it, can you change the diff column to be colour coded like the others?

Yup, I had the diff column color coded at first. But since up/down of uncertainty isn't obviously good (green) or bad (red) I thought the colors might be misleading. If I make down red, then players might think they're doing something wrong if their uncertainty keeps decreasing.
Also, if uncertainty never goes up due to a match, the other color would never show up and the red color would effectively just be an additional highlight to distract from the more important numbers.
What if I just add the up/down icon and not the color coding?

Can I see what it looks like colored and with arrows? For me the colors just let me know that it's a delta not an absolute value. But maybe if you show me what it looks like I'll have a better idea.
Also for some reason the arrows disappeared on the other columns. If it's due to FontAwesome, try and find a free arrow since Marek wanted us to not depend on paid version.

Sure!
I've added in the color code and arrows to the uncertainty change column. I also updated the icon to use a free version of the up/down arrows.

If you like it, I'll update the test evidence in the initial PR description to show this version

And this is what it looks like with the arrows, but not colored


DSTU2, read on StructureDefinition doesn't work right

ServerProfileProvider looks in the resource map for Patient, but the resource map has StructureDefinition/Patient, so it never finds anything

Crap. I got #130 and #131 mixed up.


Not getting audio/video call when app not running or background mode

Currently I am using Agora SDK for Audio/Video call. I am not getting call when app is not running. What I need to added to get audio/video call in background or app not running.

you will need to add voip/push notification capabilities yourself in this case.

@plutoless  I tried with VOIP push notification but my app crashed when I accepted the call.
my app crashed here, showing empty lastIncomingInvitation, as I got call from VOIP push notification.
guard let last = rtm.lastIncomingInvitation else {
fatalError("rtm lastIncomingInvitation")
}
code:
func accpetLastIncomingInvitation(fail: ErrorCompletion = nil) {
let rtm = AgoraRtm.shared()
    guard let last = rtm.lastIncomingInvitation else {
        fatalError("rtm lastIncomingInvitation")
    }

    accept(last) {(errorCode) in
        guard errorCode == AgoraRtmInvitationApiCallErrorCode.ok else {
            if let fail = fail {
                fail(AGEError(type: .fail("rtm refuse invitation fail: \(errorCode.rawValue)")))
            }
            return
        }
    }
}

please help me on this