Doesn't this extension require lower case account names in all cases?

In the third bullet under "Continued sign in prompts", it is stated to: "make sure that you specify the UPN with the correct case-sensitivity at the SSH prompt." If I'm not mistaken, my personal account name in AAD is a mixed case account name. However, it seems that the extension will convert all account names to lowercase, and therefore only accepts all-lowercase usernames:
[root@vmtst-two ~]# getent passwd<EMAIL_ADDRESS>[root@vmtst-two ~]# getent passwd<EMAIL_ADDRESS>myaccount@example.com:*:4942823:4942823:myaccount:/home/myaccount:/bin/bash
It seems that the extension creates the Linux UID based on a hash of the account name, and that it only considers account names that are in all lowercase with an "@" somewhere in the middle:
[root@vmtst-two ~]# getent passwd sdfjowewer@ouhojhoiu
sdfjowewer@ouhojhoiu::12421113:12421113:sdfjowewer:/home/sdfjowewer:/bin/bash
[root@vmtst-two ~]# getent passwd kjhjkhGKJHGw@oKhgky
[root@vmtst-two ~]# getent passwd kjhjkhgkjhgw@okhgky
kjhjkhgkjhgw@okhgky::13079102:13079102:kjhjkhgkjhgw:/home/kjhjkhgkjhgw:/bin/bash
[root@vmtst-two ~]#
So it seems that the extension only works with all-lowercase account names, independent of how it is entered in AAD. If that is indeed the case, could the documentation be updated to state that fact?

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

ID: bb8e2623-1f79-aee3-bd97-8b5f647b6980
Version Independent ID: 6346b54d-cc8d-0b79-a6b8-f9144cfa2459
Content: Log in to a Linux VM with Azure Active Directory credentials
Content Source: articles/virtual-machines/linux/login-using-aad.md
Service: virtual-machines-linux
GitHub Login: @iainfoulds
Microsoft Alias: iainfou

Thanks for the feedback! We are currently investigating and will update you shortly.

@jurjenoskam I will assign this to the author to determine if we should add that information to the doc.
@iainfoulds can you take a look?

@MicahMcKittrick-MSFT Please reassign to @mahesh-unnikrishnan
@mahesh-unnikrishnan Can you comment on the behavior reported by the customer, please?

Is Windows on the roadmap for this?

any update on the case sensitivity issue?

For my organization, which is approx 100K employees, the case sensitivity issue makes this functionality unusable. AAD is federated to our global directory, and our global directory uses mixed case usernames. I know other large organizations that are in the same boat.  If you are looking for widespread adoption of this capability, we need the ability to use mixed case usernames.

@mahesh-unnikrishnan can you comment on this?
@Karishma-Tiwari-MSFT @iainfoulds looks like I can reassign to Mahesh again

Thanks, @MicahMcKittrick-MSFT. Not sure why @mahesh-unnikrishnan was unassigned. He's still best served to provide a response.
CC: @cynthn

@timnam Thanks for the update.
@mahesh-unnikrishnan Can you please take a look if this behavior is expected? Thanks :)

@iainfoulds I got to know that Mahesh is not at Microsoft anymore and Sandeep Deo is taking over.
@deosandeep Can you please help us confirm if this is the expected behavior. Thanks :)

Yes, we expect username to be entered in lowercase.

@deosandeep Thank you for confirming. Can you please update the doc with this information. Thanks :)

@iainfoulds We have got the confirmation from @deosandeep. Can you please make changes to the doc accordingly?

@Karishma-Tiwari-MSFT Iain isn't on VMs anymore, please assign it to me. Thanks!
@iainfoulds @zr-msft  - FYI

@jurjenoskam thank you for the feedback! I have added a line into the docs about entering the username in all lower case. Thanks again!
#please-close


Superfluous field "notification_filters"

I'm trying to change some triggers in a bunq slave, but I'm getting the following error:
<IP_ADDRESS> - - [26/Oct/2019 13:10:30] "GET / HTTP/1.1" 200 -
<IP_ADDRESS> - - [26/Oct/2019 13:10:30] "GET /static/bunq2ifttt.png HTTP/1.1" 304 -
GET v1/user/XXXX/monetary-account-joint/XXXX
New:  [{'notification_delivery_method': 'URL', 'notification_target': 'https://XXXX.appspot.com/bunq2ifttt_request', 'category': 'REQUEST'}]
PUT v1/user/XXXX/monetary-account-joint/XXXX
{'Error': [{'error_description': 'Superfluous field "notification_filters".', 'error_description_translated': 'Superfluous field "notification_filters".'}]}
Result:  {'Error': [{'error_description': 'Superfluous field "notification_filters".', 'error_description_translated': 'Superfluous field "notification_filters".'}]}
<IP_ADDRESS> - - [26/Oct/2019 13:10:34] "GET /account_change_request?iban=XXXX&value=true HTTP/1.1" 200 -
<IP_ADDRESS> - - [26/Oct/2019 13:10:35] "GET / HTTP/1.1" 200 -
GET v1/user/XXXX/monetary-account
<IP_ADDRESS> - - [26/Oct/2019 13:10:37] "GET /update_accounts HTTP/1.1" 200 -
<IP_ADDRESS> - - [26/Oct/2019 13:10:38] "GET / HTTP/1.1" 200 -

It doesn't work with any account, joint or not. The notification_filters object seems fine according to the documentation. Should another URL be used?

That seems to be the case: https://beta.doc.bunq.com/basics/changelog#october-8-2019

Thank you for the report. I was already working on this and already have a working version with the new API. My goal is to commit a new version this weekend.

Ok, great! I've changed the API endpoint in the current codebase, and it does work, although they keep being marked as "disabled". I'll wait for your new version.

Changes have been committed to the 'dev' branch. The new version no longer needs a slave and can set callbacks directly using OAuth.
I need to do some more testing and update the documentation before doing a new release, but feel free to try it.

I'm getting this error after deploying and setting a password:
2019-10-28 06:10:19 default[20191028t070621]  [2019-10-28 06:10:19,881] ERROR in app: Exception on / [GET]
2019-10-28 06:10:19 default[20191028t070621]  Traceback (most recent call last):    File "/env/lib/python3.7/site-packages/flask/app.py", line 2446, in wsgi_app      response = self.full_dispatch_request()    File "/env/lib/python3.7/site-packages/flask/app.py", line 1951, in full_dispatch_request      rv = self.handle_user_exception(e)    File "/env/lib/python3.7/site-packages/flask/app.py", line 1820, in handle_user_exception      reraise(exc_type, exc_value, tb)    File "/env/lib/python3.7/site-packages/flask/_compat.py", line 39, in reraise      raise value    File "/env/lib/python3.7/site-packages/flask/app.py", line 1949, in full_dispatch_request      rv = self.dispatch_request()    File "/env/lib/python3.7/site-packages/flask/app.py", line 1935, in dispatch_request      return self.view_functions[rule.endpoint](**req.view_args)    File "/srv/main.py", line 40, in home_get      accounts = util.get_bunq_accounts_with_permissions(config)    File "/srv/util.py", line 77, in get_bunq_accounts_with_permissions      for acc in config["accounts"]:  KeyError: 'accounts'

It seems like it expects accounts while I didn't add the OAuth key yet. Do I need to do something before deploying, or is this a bug?

I do apologize, this is indeed a bug which I didn't spot due to lack of testing. I'll fix it tonight or tomorrow.

I do apologize, this is indeed a bug which I didn't spot due to lack of testing. I'll fix it tonight or tomorrow.

Any news? Or is there an alternative way for enabling Mutation/Balance triggers?

I am very sorry for the delay. @makruiten @tcvdw1605
The issue has been fixed in version 2.0 that has just been released.


Cant open SAM

It asks to run steam although running

Did you run Steam as admin, while SAM as non-admin? Or Steam as non-admin and SAM as admin?
If so, you must run them with the same privilege level.
Otherwise, I'm told a reboot usually fixes this issue.

Ok, i will try

I  launched all as admin

And same as non-admin

Download latest build
Extract them to disk root (for example: D:\SAM)
Launch SAM.Picker.exe directly from folder

Also if you're using beta client of Steam you must try to revert it to stable version.

Oh failed to load SteamClient here is interesting. If this is actually an issue with the beta client I'll have to look into it.

I've confirmed the beta update has nothing to do with it.
@lBlackDreadl Your issue is either your Steam install is strange (registry information for install location is missing or invalid) or your Steam install is corrupt. The only thing I can suggest here is reinstalling Steam.

Ok, i will try to reinstall Steam but some later.

Sam.picker requires firewall access, loopback conections must be enabled


Updates the dispatch() event parameter order for Symfony 4.3+

This is something that goes along with this issue and pull request for FOSElasticaBundle. In Symfony 4.3, the order of the parameters changed for the dispatch() event.
I'm not good at all with PHPUnit, and I don't understand the tests they're running on FOSElasticaBundle, so the tests are failing there and they haven't been able to merge it yet. I'll have to do more work to get the tests updated properly before they'll merge I'd guess.

@boroth  Could you please remove symfony 3 from composer ?

https://github.com/php-enqueue/enqueue-elastica-bundle/pull/32

Sorry, didn't see this until now. Thanks for taking care of the composer dependency!


Allow configFile paramter in maven plugin to be load file from classpath

Using the maven plugin I would like to be able to pass a classpath file to the "configFile" parameter as well. Similar to the "locations" parameter which supports "filesystem" and "classpath".
The goal is to pack a jar file containing all sql scripts and db-settings for different target environments together and later be able to retrieve that archive and populate different databases with the same scripts (but different connection settings).

I have the same problem,
i have tow projects A and B. A is a dependency of B
i want to use flyway maven plugin in the process-test-resources phase to create a h2 database for the unit tests
in project A i have a file h2.properties who is the flyway configFile and sql files all located in src/test/ressources
i use maven-jar-plugin with the goal test-jar to package all the test resources in a jar and i want to use this ressources in project B by using a similar flyway maven plugin to the project A
but in project B i cant configure configFile to point in the h2.properties because it is in the class path

Closing for lack of interest. There is a workaround - before running a Flyway goal, use the dependency:unpack goal to unpack the config file, which you can then read from the disk.


bug: Problem when changing button's color and style

Short description of the problem:
When setting the color and style attributes of the button programmatically, the changes are not applied/visualized as expected.
What behavior are you expecting?
The changes to color and style attributes should be visualized as they are set in the code.
Steps to reproduce:

Open http://plnkr.co/edit/2fViim?p=preview
Click the button [Unify all buttons].
Observe that not all buttons are set to the default state.

Other information: (e.g. stacktraces, related issues, suggestions how to fix, stackoverflow links, forum links, etc)
Which Ionic Version? 2.x
Plunker that shows an example of your issue
http://plnkr.co/edit/2fViim?p=preview
Run ionic info from terminal/cmd prompt: (paste output below)
Your system information:

Cordova CLI: 6.1.1
Gulp version:  CLI version 1.2.1
Gulp local:   Local version 3.9.1
Ionic Framework Version: 2.0.0-beta.4
Ionic CLI Version: 2.0.0-beta.24
Ionic App Lib Version: 2.0.0-beta.14
OS: Windows 8.1
Node Version: v5.8.0

Quit your Ionic CLI and run again. Or restart the browser. It must be due to invalid reassignment of values to variables that alter the color of the buttons during Stack refresh.

If you create a dummy element, say a <h1>, attach a class to it and change a property via CSS. Do the changes apply?

Also, if you attach a class to the button, sometihng like button-assertive do the changes apply?

@RAMDdFLEET @Frightie Maybe I didn't write a good/clear description - the problem is when both color and style attributes are updated at once. You can observe it in this plunker demo following the repro-steps. Thank you for the suggestions, but I already implemented a fix that should resolve the issue.

Thank you @iignatov for the PR! This will be in the beta.7 release. :smile:

@brandyscarney Great, thanks for the update!


Fixing menu icon size for successful build with SDK v 4.1.4

Resize menu_icon.png to 25x25px.

Could you please merge that one? It's very minor, and I think it will break code for a lot of new developers.

Thanks once again!


Tiled Map loading throwing IllegalArgumentException: initialCapacity is too large.

Issue details
Basically my game is being played by few people at the moment and one of them sometimes get this exception when he moves from one map to the other -
Tiled Map loading throwing IllegalArgumentException: initialCapacity is too large.
I am not doing anything outside render thread. Even map is loaded on the render thread.
Reproduction steps/code
Sadly there is no way I could reproduce it, it just happens on one of my client's computer when a new map is loaded. Also this doesn't happen very often, the exception occurs rarely.
The way I load map is like this :
currentMap = new TmxMapLoader().load("maps/" + switchMapMessage.getMapId() + TMX_EXTENSION, mapParams);
Version of LibGDX and/or relevant dependencies
Libgdx Version 1.9.3
Stacktrace
LWJGL Application ERROR - A fatal error
com.badlogic.gdx.utils.SerializationException: Error parsing file: maps/1.tmx
    at com.badlogic.gdx.utils.XmlReader.parse(XmlReader.java:83)
    at com.badlogic.gdx.maps.tiled.TmxMapLoader.load(TmxMapLoader.java:78)
    at com.pbo.game.client.map.DefaultMapManager.setupNewMap(DefaultMapManager.java:158)
    at com.pbo.game.client.ui.screens.MainGameScreen.handleNetworkQueue(MainGameScreen.java:226)
    at com.pbo.game.client.ui.screens.MainGameScreen.render(MainGameScreen.java:156)
    at com.badlogic.gdx.Game.render(Game.java:46)
    at com.pbo.game.client.GameClient.render(GameClient.java:73)
    at com.badlogic.gdx.backends.lwjgl.LwjglApplication.mainLoop(LwjglApplication.java:223)
    at com.badlogic.gdx.backends.lwjgl.LwjglApplication$1.run(LwjglApplication.java:124)
Caused by: java.lang.IllegalArgumentException: initialCapacity is too large: 16
    at com.badlogic.gdx.utils.ObjectMap.<init>(ObjectMap.java:68)
    at com.badlogic.gdx.utils.ObjectMap.<init>(ObjectMap.java:59)
    at com.badlogic.gdx.utils.XmlReader$Element.setAttribute(XmlReader.java:487)
    at com.badlogic.gdx.utils.XmlReader.attribute(XmlReader.java:428)
    at com.badlogic.gdx.utils.XmlReader.parse(XmlReader.java:260)
    at com.badlogic.gdx.utils.XmlReader.parse(XmlReader.java:61)
    at com.badlogic.gdx.utils.XmlReader.parse(XmlReader.java:81)
    ... 8 common frames omitted

Please select the affected platforms
Windows
Also sometimes this Caused by: java.lang.IllegalArgumentException: initialCapacity is too large: 16 has 64 as initial capacity too.

This is most likely a threading issue, but either way we can't do anything without more info. Please supply a self contained test that reproduces your issue, and re-open this issue.

Same thing for me:
class java.lang.IllegalArgumentException: initialCapacity is too large: 64
com.badlogic.gdx.utils.ObjectIntMap.<init>(ObjectIntMap.java:68)
com.badlogic.gdx.utils.ObjectIntMap.<init>(ObjectIntMap.java:53)
com.badlogic.gdx.graphics.glutils.ShaderProgram.<init>(ShaderProgram.java:106)
com.badlogic.gdx.graphics.glutils.ShaderProgram.<init>(ShaderProgram.java:180)
It happen when I create simple shader, on one of my computers, on other - it's ok, I refered to same line:
if (initialCapacity > 1 << 30) throw new IllegalArgumentException("initialCapacity is too large: " + initialCapacity);
and yes - 1 << 30 ==<PHONE_NUMBER> on all of my tests, but still - sometimes this error just happens and crash everything.

Do you have more information e.g. java version and exact windows version

Hello.
Yes, actually I saw another topics with this issue - also without any details or steps to reproduce, but for my case - I found issue. It occurred only in one (from two) test computers. Actually what I tried to do - create Shaders dynamically on game loop. I have a one class - some shader manager, after I try to get from it one of ShaderProgram HashMap array - it check if it was created before, and if not - it create ShaderProgram right now (game loop - stage run - is in progress). Exactly this you can check from my log above - final point was on "com.badlogic.gdx.utils.ObjectIntMap.(ObjectIntMap.java:68)". Once I moved initialization of all required and possible shaders to the stage init - before it's draw circle begin - problem gone. Java and windows version is the same as on first machine (that didn't create such issues), processor with this issue is Intel Dual Core 2.42, processor o machine without issue - Intel Core i3. I think replacing "1 << 30" - for just hardcoded "1073741824" (not so cute, I know) - will solve issue.


Split public_key out of xmtp_envelope

Given that the public key stuff plays a role on its own in the contact topics and that the xmtp_envelope file is getting long and convoluted, I thought it might be a good idea to break it up in two.
This might require some updates in xmtp-js as some of the types will move into publicKey.* in the index.js. Other than that it should be pretty harmless. I ran the code generation steps for both go and ts, which seemed to have succeeded.

Given that this is a breaking change for importers of the library, I think we should include a semver commit comment that notes that and causes a major release. We got bit by this a couple weeks ago.
Side note: I previously pinned @xmtp/proto to the exact version in xmtp-js, but somehow that got reverted (probably by me).


Error when using attribute_driven recipe

Hi, I am getting this error when I use the attribute_driven recipe:
No resource or method named `collectd_plugin' for `Chef::Recipe "attribute_driven"'

I have noticed that collectd_plugin is not defined anywhere in this cookbook. Is it perhaps something defined in some other cookbook? Should a dependency be added if that's the case?
I am using version 1.2.0
thanks

Are you also including the collectd recipe along with attribute_driven?

Yes, I did include the collectd recipe before the attribute_driven one

Hm. The run_list for this cookbook's Test Kitchen definition includes both recipes and all tests pass on Ubuntu and CentOS. The Chef client version is 12.4.1.
Any more details around how you're pulling the cookbook in? What the run_list looks like?

I have declared the collectd cookbook dependency in the Berksfile like this
cookbook 'collectd-ng', '~> 1.2.0'

and, similarly, in the metadata.rb:
depends 'collectd-ng', '~> 1.2.0'

Then I defined a role in JSON format, referencing the two collectd recipes:
{
  "name": "collectd",
  "description": "Collectd basic configuration",
  "default_attributes": {
    "collectd": {
      "plugins": {
        "syslog": {
          "config": {"LogLevel": "Info"}
        },
        "disk": {},
        "swap": {},
        "memory": {},
        "cpu": {}
      }
    }
  },
  "override_attributes": {
  },
  "chef_type": "role",
  "run_list": [
    "recipe[collectd-ng]",
    "recipe[collectd-ng::attribute_driven]"
  ],
  "env_run_lists": {
  }
}

the .kitchen.yml file references the collectd role in this way:
    run_list:
      - role[collectd]

Ah, the name of the LWRP for the version of this cookbook that gets installed via Chef Supermarket is collectd_ng_plugin. Names have changed because of the Chef Supermarket namespacing. Some more details around the changes can be found in https://github.com/hectcastro/chef-collectd/issues/45.

I am running into this same error.  @hectcastro what does your reference to collectd_ng_plugin mean exactly?
For now I am skipping the use of the attribute_driven recipe and just providing my conf options in a template, but it would be nice to convert this to a role based set of attributes (I have multiple write_graphite prefixes depending on server role).

I am running into this same error. @hectcastro what does your reference to collectd_ng_plugin mean exactly?

Since there is already a collectd cookbook in the Chef Supermarket, I was only able to upload this cookbook as collectd_ng. The branch with those changes is feature/hmc/chef-supermarket. It has not been merged because it has the potential to break usage for everyone referencing this cookbook via Git in their Berksfile.


release(versioning): update version to 1.0.1

Automated PR to bump the version pre-release.

:tada: This PR is included in version 1.0.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Question about remote schema stitching performance

I test merge remote schema and extend thhat schema. but I find graphql document execution performance is very poor.

@luosong do you have a bit more information? Can you show what performance you were expecting, and what you ended up getting?

Maybe add some graphql tracing + network request info to see where the bottleneck actually is.

(Renamed the issue to avoid misleading people who are just scanning the issue list)

Closing since there isn't any more info.


[Error] truffle fails to build project consisting of only a contract and a test file

Checklist

[done ] installed truffle and testrpc

# npm install -g truffle
# npm install -g testrpc

Created a directory and ran initialized truffle:
mkdir test_project
cd test_project
truffle init

Cleared the pregenerated contracts and tests:
rm -r tests/* contracts/* build/*
Added a minimalist contract and test js file:
C.sol
contract C {

    string words = "Bla bla bla";

    uint256 lastVal;

    function math(uint256 a, uint256 b) returns (uint256) {
        lastVal = a + b;
        return lastVal;
    }

    function getWords() constant returns (string) {
        return words;
    }
}

c.js
contract('C', function(accounts) {
  it("Getting the words string from the contract", function() {
    var c = C.deployed();

    return c.getWords.call(accounts[0]).then(function(words) {
      assert.equal(words, "Bla bla bla", "[E] The contract should have said \"Bla bla bla\"");
    });
  });

  it(" 2 + 2 = 4 ", function(){
    var c = C.deployed();

    return c.math(2, 2).then(function(additionResult){
        assert.equal(additionResult, 4, "[E] 2 + 2 = 4 even in eth. contracts.");
    });
  });
});

and ran
truffle build
System/environment

OS: debian 8.3 Jessie x64, kernel version 3.16.0-4-amd64, virtual machine, running on VirtualBox, host machine Win7 x64, NAT network settings used

Expected behaviour
truffle should have generated build artifacts in the build directory but it didn't (the directory is empty).
Observed behaviour
There are no files added to the build directory.

You need to run truffle compile or truffle migrate for these artifacts to be generated. Did you run either of these commands after deleting the build directory? The reason truffle build doesn't generate these artifacts is that it's assumed you'll want to at least compile your contracts before building your frontend. We can add compilation as a dependency, however.
That said, if you only have a test and a solidity file, you wouldn't want to run truffle build anyway. I understand however that in other frameworks, build is synonymous with compile, so perhaps we should merge the two.

I have managed to build the contract (I ran truffle compile) but am still not able to launch the test cases. Can truffle launch test cases automatically?

You can launch the tests by running truffle test. Truffle will also recompile and migrate for you in this case.
You can use truffle compile/test/migrate without any requirement on the frontend code. If you don't want to deal with the frontend code, just remove the app directory, remove the build configuration from truffle.js, and don't call truffle build or truffle serve.
I'm going to close this for housekeeping purposes. Please let m know if you have another issue.

When i run truffle Migrate i am getting an error. I am not understanding this
Error: Invalid JSON RPC response: "Error: connect ECONNREFUSED <IP_ADDRESS>:8545\n    at Object.exports._errnoException (util.js:1026:11)\n    at exports._exceptionWithHostPort (util.js:1049:20)\n    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1081:14)"
at Object.InvalidResponse (/usr/local/lib/node_modules/truffle/node_modules/web3/lib/web3/errors.js:35:16)
at request.onreadystatechange (/usr/local/lib/node_modules/truffle/node_modules/web3/lib/web3/httpprovider.js:111:32)
at dispatchEvent (/usr/local/lib/node_modules/truffle/node_modules/xmlhttprequest/lib/XMLHttpRequest.js:591:25)
at setState (/usr/local/lib/node_modules/truffle/node_modules/xmlhttprequest/lib/XMLHttpRequest.js:610:14)
at handleError (/usr/local/lib/node_modules/truffle/node_modules/xmlhttprequest/lib/XMLHttpRequest.js:532:5)
at ClientRequest.errorHandler (/usr/local/lib/node_modules/truffle/node_modules/xmlhttprequest/lib/XMLHttpRequest.js:459:14)
at emitOne (events.js:96:13)
at ClientRequest.emit (events.js:188:7)
at Socket.socketErrorListener (_http_client.js:308:9)
at emitOne (events.js:96:13)
at Socket.emit (events.js:188:7)
at emitErrorNT (net.js:1272:8)
at _combinedTickCallback (internal/process/next_tick.js:74:11)
at process._tickDomainCallback (internal/process/next_tick.js:122:9)

@Akshay-agarwal That means Truffle couldn't connect to your Ethereum client. You need to have an Ethereum client running. Please take a look at the documentation: http://truffle.readthedocs.io/en/latest/getting_started/client/

when I write truffle compile/migrate/test I am having this error:
Compiling your contracts...
C:\Users\user.config\truffle\compilers\node_modules\soljson-v0.5.12+commit.7709ece9.js:16
function N7a(a,c,d,e,g,h){a=a|0;c=c|0;d=d|0;e=e|0;g=g|0;h=h|0;var i=0,j=0,k=0,l=0,m=0,n=0,o=0,p=0,q=0,r=0,s=0,u=0,w=0,x=0,y=0,z=0,A=0,B=0,C=0,D=0,E=0,F=0,G=0,H=0,I=0,J=0,K=0,L=0,M=0,N=0,O=0,P=0,Q=0,R=0,S=0,T=0,U=0,V=0,W=0,X=0,Y=0,Z=0,_=0,$=0,aa=0,ca=0,da=0,ea=0,ga=0,ia=0,ja=0,ka=0,la=0,ma=0,na=0,oa=0,pa=0,qa=0,ra=0,ta=0,wa=0,xa=0,ya=0,za=0,Aa=0,Ba=0,Ca=0,Da=0,Ea=0,Fa=0,Ga=0,Ha=0,Ia=0,Ja=0,Ka=0,La=0,Ma=0,Na=0,Oa=0,Pa=0,Qa=0,Ra=0,Sa=0,Ta=0,Ua=0,Va=0,Wa=0,Xa=0,Ya=0,Za=0,_a=0,$a=0,ab=0,bb=0,cb=0,db=0,eb=0,fb=0,gb=0,hb=0,ib=0,jb=0,kb=0,lb=0,mb=0,nb=0,ob=0,pb=0,qb=0,rb=0,sb=0,tb=0,wb=0,xb=0,yb=0,zb=0,Ab=0,Bb=0,Cb=0,Db=0,Eb=0,Fb=0,Hb=0,Ib=0,Jb=0,Kb=0,Lb=0,Mb=0,Nb=0,Ob=0,Pb=0,Qb=0,Rb=0,Sb=0,Tb=0,Ub=0,Vb=0,Wb=0,Xb=0,Yb=0,Zb=0,_b=0,$b=0,ac=0,bc=0,cc=0,dc=0,ec=0,fc=0,gc=0,hc=0,ic=0,jc=0,kc=0,lc=0,mc=0,nc=0,oc=0,pc=0,qc=0,rc=0,sc=0,tc=0,uc=0,vc=0,wc=0,xc=0,zc=0,Ac=0,Bc=0,Cc=0,Dc=0,Ec=0,Fc=0,Gc=0,Hc=0,Ic=0,Jc=0,Kc=0,Lc=0,Mc=0,Nc=0
SyntaxError: Unexpected end of input
at Module._compile (internal/modules/cjs/loader.js:892:18)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:973:10)
at Module.load (internal/modules/cjs/loader.js:812:32)
at Function.Module._load (internal/modules/cjs/loader.js:724:14)
at Module.require (internal/modules/cjs/loader.js:849:19)
at require (internal/modules/cjs/helpers.js:74:18)
at VersionRange.getCachedSolcByFileName (C:\Users\user\AppData\Roaming\npm\node_modules\truffle\build\webpack:\packages\compile-solidity\compilerSupplier\loadingStrategies\VersionRange.js:36:1)
at VersionRange.getCachedSolcByVersionRange (C:\Users\user\AppData\Roaming\npm\node_modules\truffle\build\webpack:\packages\compile-solidity\compilerSupplier\loadingStrategies\VersionRange.js:55:1)
at VersionRange.load (C:\Users\user\AppData\Roaming\npm\node_modules\truffle\build\webpack:\packages\compile-solidity\compilerSupplier\loadingStrategies\VersionRange.js:194:1)
at C:\Users\user\AppData\Roaming\npm\node_modules\truffle\build\webpack:\packages\compile-solidity\compilerSupplier\index.js:71:1
at new Promise ()
at CompilerSupplier.load (C:\Users\user\AppData\Roaming\npm\node_modules\truffle\build\webpack:\packages\compile-solidity\compilerSupplier\index.js:51:1)
at C:\Users\user\AppData\Roaming\npm\node_modules\truffle\build\webpack:\packages\compile-solidity\profiler\index.js:98:1
Truffle v5.1.7 (core: 5.1.7)
Node v12.13.0


dasel: 1.24.1 -> 1.24.3

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/TomWright/dasel/releases.
meta.description for dasel is: "Query and update data structures from the command line"
meta.homepage for dasel is: "https://github.com/TomWright/dasel"
meta.changelog for dasel is: "https://github.com/TomWright/dasel/blob/v1.24.3/CHANGELOG.md"
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.24.3 with grep in /nix/store/7bff01q5hd39m7fw7zbx9iglml7q1qik-dasel-1.24.3
found 1.24.3 in filename of file in /nix/store/7bff01q5hd39m7fw7zbx9iglml7q1qik-dasel-1.24.3

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 x86_64-darwin rebuild(s)

First fifty rebuilds by attrpath
dasel

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/7bff01q5hd39m7fw7zbx9iglml7q1qik-dasel-1.24.3 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A dasel https://github.com/r-ryantm/nixpkgs/archive/c98f0a46f3cdf70e885cf972d07823202d314b1b.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/7bff01q5hd39m7fw7zbx9iglml7q1qik-dasel-1.24.3
ls -la /nix/store/7bff01q5hd39m7fw7zbx9iglml7q1qik-dasel-1.24.3/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

dasel

Maintainer pings
cc @0x4A6F @kalbasit for testing.

Result of nixpkgs-review pr 170205 run on x86_64-linux 1

1 package built:

dasel


Hotfix BNORM interface to adopt nyquist mode changes in VMEC

As mentioned in #42 , the default value for lnyquist is now true and it has been removed from the input namelist.  Here is the fix to BNORM. (PPPL cluster module has been updated).
Here is a simple comparison using the half-Tesla NCSX LI383 configuration. It looks like the updates fix the issue for now.

lnyquist = .false.

lnyquist = .true. (inconsistent)

lnyquist = .false. with BNORM interface updated (consistent)

Shouldn't the third plot be labeled lnyquist=.true. if the problem is fixed?

Shouldn't the third plot be labeled lnyquist=.true. if the problem is fixed?

Yes, it is with lnyquist=.true.. I was using 'on/off' when generating the figures, which stands for "T/F".

I think terpsichore was turned on in this commit - I guess this will test the rest of the logic flags, but I don't think most people have terps by default.


SecurityTagLib.groovy @ 118

On one of our gsp files we render:
userSex: '<view:loggedInUserInfo field="sex"/>'
which might have values: 1 or 0 and later on we have some logic which utilizes this variable.
Somehowe for female users (sex = 0) our tests were failing. So we started invastigating:
Looks like here is the problem:
grails-spring-security-core/grails-app/taglib/grails/plugin/springsecurity/SecurityTagLib.groovy @ 118
namely:
if (source) {
when we changed it to:
if (source != null) {
all our tests passed.

Fixed in v3.0.4


cats 1.0.0-RC1

This updates Monocle to cats-1.0.0-RC1.
The only real change is Map → SortedMap everywhere, which is a hassle but is mostly mechanical. The other option would be to pull in alley-cats but personally I'd prefer to relegate those instances to a monocle-alleycats or something and keep the core lawful.
I deleted the aliased IList and IMap examples but left the rename imports like { Monoidal => Zip }. If you'd like to get rid of these and other scalaz cruft I can do it here or in another PR.

Updated the newts dep so we're green now.

I checked with Travis re: circe optics and removal of Map instance and I think we might be ok.

I think it might not be so bad since the At, Each, etc. for JSON objects uses our custom traverse on JsonObject
…which respects order

Thanks a lot Rob!

Cool. Can we get a milestone for this when it's convenient?

I just released 1.5.0-cats-M2


OPSEXP-2333 Refactor imagemagick package tests

OPSEXP-2333
• Implemented the test with the Dockerfile approach.
• Matrix approach has been changed to json file.

The test*and deploy* jobs looks like duplication of code. I think you need a composite action. Also the directory structure could be improved for better composition so test_debs => debs/tests & test_rpms=> rpms/tests

We agreed to tackle that in a different JIRA to not delay further the RHEL9 support

don't forget to create the follow up ijra

OPSEXP-2341


What happens when portfowarder loses connection

@bryanl commented on Tue Apr 16 2019
There should be some indication to the user that the port forward connection has been lost.

This can be handled using the new alerting code. Notifying the user that the port forwarding connection has been lost.

The best way to approach this is to create a port forward manager and move this into StateManager so that port forward connections will get access to an Alerter.
Pulling back on this issue for now due to prioritizing other features for kubecon

Pending PR will not have alerter included because it will not address cases where a port forward connection is lost outside of an action handler.


Blacklisting Components

Make sure you are running the latest version of Home Assistant before reporting an issue.
You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum:
Home Assistant release (hass --version):
0.23.1
Python release (python3 --version):
3.4
I wanted to start a bit of a conversation on a feature request. I'm in the process of updating Home Assistant since I was pretty outdated on my production server. The good news is that the Netgear router device tracker seems to be working a bit better. The bad news is that I don't want it and it auto-starts. I could care less that my Hue hub is home and I already use OwnTracks for presence detection. Now I have to go through and hide all the entities added by the Netgear component.
So, what I'm thinking, is that I should be able to blacklist components. I'm thinking it should be pretty easy to parse a list of blacklisted components when the request is made to load them. However, this could complicate dependency management. There also is the question of where this list should live. I'm thinking in the homeassistant block in the config. Or, possibly in the discovery component's config.
As I'm typing, I actually think that putting the blacklist in the discovery component would be ideal. That way you don't blacklist the component from being loaded if it is explicitly requested or implicitly requested as a dependency, but you don't allow it to automatically be registered from discovery.
Alternatively, discovery could also be disabled, but that feels a little totalitarian. Philosophically, automated actions should allow themselves to be restricted. Less we develop Skynet. And I don't want that on my conscience.

I think this really belongs in the feature requests instead of the bug list https://community.home-assistant.io/c/feature-requests - please refile there if you are still interested in this.
Honestly, my approach has been to turn off discovery in places I don't want it to provide a tuned list.


New iOS Release Fails to Read the True ETH Balance

The new update for iOS fails to read the ETH balance on the info page and also it doesn't allow send the token. Observe that the main page shows the balance in ETH but not the value in USD. I attach screenshots.

also it doesn't allow send the token

@Hoanib can you elaborate on how to reproduce this?

A bug! Resolved when I changed the wallet (address) and changed to the main wallet again.

also it doesn't allow send the token

@Hoanib can you elaborate on how to reproduce this?

When I updated my wallet and opened it quickly I saw that the ETH token didn't show the balance in USD on the right side. And when I click on the page info didn't show the balance like if someone stolen my assets. Then I analyzed that it would be a bug and change the wallet and the ETH came back but I just check and the issue persists.

Open the wallet app (try to check it  with an address with ETH balance) if it doesn't show the USD balance on the right side and the all balance on the info page change for another address and then change again to the main wallet, the balance will show but if you close the app and open it again it will not.

Yes the bug is presented when you open the app with a wallet address connected with ETH asset. If you change for another wallet and then change back to the main we are testing the balance will show but when you close the app and open it again the balance disappears.

The bug is presented when you open the app with a wallet address connected
with ETH asset. If you change for another wallet and then change back to
the main we are testing the balance will show but when you close the app
and open it again the balance disappears.
On Mon, Mar 21, 2022 at 02:21 Hwee-Boon Yar @.***>
wrote:

also it doesn't allow send the token
@Hoanib https://github.com/Hoanib can you elaborate on how to reproduce
this?
—
Reply to this email directly, view it on GitHub
https://github.com/AlphaWallet/alpha-wallet-ios/issues/4118#issuecomment-1073519476,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AYBLZ42LP7DDPWDDVO3RUJLVBAIOVANCNFSM5RGU6ALA
.
You are receiving this because you were mentioned.Message ID:
@.***>


Upgrade to 0.16

Hello could you please update example to the latest egui versions?
There were quite a bit of changes, like RepaintSignal moving to epi::backend. And FrameBuilder seems no longer exists.

Bump but this example seems to be out of date for:
egui_winit_platform = "0.14.0"
egui_wgpu_backend = "0.17.0"
now.


Error with ETL Parallel execution

###OrientDB Version: orientdb-community-2.2.16
###Java Version: Java 8 Update 91
###OS: Mac Os Sierra 10.12.3
###Expected behavior
error does not happen
###Actual behavior
Error in Pipeline execution: com.orientechnologies.orient.core.exception.ODatabaseException: Cannot execute the request because an asynchronous operation is in progress. Please use a different connection
oetl.sh actually completes, but not sure how well.
###Steps to reproduce
Archive.zip

Hi, sorry for the delay. My suggestion is to avoid parallel execution in this case, where you have lookups and merge. And to define an index on the property on which ETL is doing lookup.
This will speedup the operations a lot.

May I close this issue? Did you manage to solve it?

Can you add it as a bug/enhancement? This is a very powerful feature to have working correctly.

Are you talking about parallel execution? On 3.0.x it is improved a lot, but let me show some results on my laptop
Parallel vs remote db WITH index:
+ extracted 8,154 entries (0 entries/sec) - 8,154 entries -> loaded 8,148 vertices (629 vertices/sec) Total time: 14885ms [0 warnings, 6 errors]

Single thread vs remote db WITH index
+ extracted 8,154 entries (0 entries/sec) - 8,154 entries -> loaded 8,154 vertices (618 vertices/sec) Total time: 14447ms [0 warnings, 0 errors]

Single thread vs remote db WITHOUT index
+ extracted 8,154 entries (0 entries/sec) - 8,154 entries -> loaded 8,154 vertices (9 vertices/sec) Total time: 934899ms [0 warnings, 0 errors]

Parallel vs remote WOTHOUT index
+ extracted 8,154 entries (0 entries/sec) - 8,154 entries -> loaded 8,148 vertices (13 vertices/sec) Total time: 936480ms [0 warnings, 6 errors]

Conclusions
We have a problem at the startup with parallel, to be solved.
But there's no gain on performance going parallel vs single threaded.
THERE's a LOT of gain if the index is defined.
Because without the index, each lookup implies a full scan. An the full scan is proportional to the database size: the more record are inserted, the more time the db needs to scan.
I simply added this lines to the configuration:
,
      "indexes": [
        {
          "class": "Entity",
          "fields": [
            "id:string"
          ],
          "type": "UNIQUE"
        }
      ]

I have an etl defined like that:
{
  "config": {
    "haltOnError": false
  },
  "extractor": {
    "jdbc": {
      "driver": "org.apache.hive.jdbc.HiveDriver",
      "url": "jdbc:hive2://???:10000/????hive.resultset.use.unique.column.names=false",
      "query": "SELECT * FROM edges where relation_type = 'board member'"
    }
  },
  "transformers": [
    { "merge": { "joinFieldName":"from_identifier", "lookup":"Entity.identifier" } },
    { "vertex": {"class": "Entity", "skipDuplicates": true} },
    { "edge": {
        "class": "board_member",
        "joinFieldName": "to_identifier",
        "lookup": "Entity.identifier",
        "direction": "out",
        "targetVertexFields":{
          "identifier": "${input.to_identifier}"
        }
      }
    },
    { "field":
      { "fieldNames":
        [ "from_identifier", "to_identifier", "relation_type", "dt"],
        "operation": "remove"
      }
    }
  ],
  "loader": {
    "orientdb": {
       "dbURL": "remote:???/???",
       "dbUser": "???",
       "dbPassword": "???",
       "dbType": "graph",
       "useLightweightEdges": false,
       "serverUser": "???",
       "serverPassword": "???",
       "wal": false
    }
  }
}

I already use existing index here:
 { "merge": { "joinFieldName":"from_identifier", "lookup":"Entity.identifier" } },

Where am I supposed to add that section?
"indexes": [
        {
          "class": "Entity",
          "fields": [
            "id:string"
          ],
          "type": "UNIQUE"
        }
      ]

this is a new configuration, I guess. You need to add the index section section in the loader part, if you are creating the schema through ETL itself:
  "loader": {
    "orientdb": {
      "dbURL": "remote:",
      "serverUser": "",
      "serverPassword": "",
      "dbAutoDropIfExists": true,
      "dbAutoCreate": true,
      "standardElementConstraints": false,
      "tx": false,
      "wal": false,
      "batchCommit": 1000,
      "dbType": "graph",
      "classes": [
        {
          "name": "Entity",
          "extends": "V"
        },
        {
          "name": "Containment",
          "extends": "E"
        },
        {
          "name": "Connection",
          "extends": "E"
        },
        {
          "name": "Inheritance",
          "extends": "E"
        }
      ],
      "indexes": [
        {
          "class": "Entity",
          "fields": [
            "id:string"
          ],
          "type": "UNIQUE"
        }
      ]
    }

take a look at the documentation and to the example:
http://orientdb.com/docs/last/Loader.html#examples
hope this helps

@robfrank  Thanks for answer. The etl configuration is for existing schema and indexes. Vertices with their indexes are already created and filled. With that etl configuration I need to connect some of them. Here is my configuration after applying your suggestions:
{
  "config": {
    "haltOnError": false
  },
  "extractor": {
    "jdbc": {
      "driver": "org.apache.hive.jdbc.HiveDriver",
      "url": "jdbc:hive2://???:10000/????hive.resultset.use.unique.column.names=false",
      "query": "SELECT * FROM edges where relation_type = 'liquidator'"
    }
  },
  "transformers": [
    { "merge": { "joinFieldName":"from_identifier", "lookup":"Entity.identifier" } },
    { "vertex": {"class": "Entity", "skipDuplicates": true} },
    { "edge": {
        "class": "liquidator",
        "joinFieldName": "to_identifier",
        "lookup": "Entity.identifier",
        "direction": "out",
        "targetVertexFields":{
          "identifier": "${input.to_identifier}"
        }
      }
    },
    { "field":
      { "fieldNames":
        [ "from_identifier", "to_identifier", "relation_type", "dt"],
        "operation": "remove"
      }
    }
  ],
  "loader": {
    "orientdb": {
       "dbURL": "???",
       "dbUser": "???",
       "dbPassword": "???",
       "dbType": "graph",
       "useLightweightEdges": false,
       "serverUser": "???",
       "serverPassword": "???",
       "wal": false,
       "tx": false,
       "batchCommit": 1000,
       "classes": [
         {
           "name": "Entity",
           "extends": "V"
         },
         {
           "name": "liquidator",
           "extends": "E"
         }
       ],
       "indexes": [
         {
           "class": "Entity",
           "fields": [
             "identifier:string"
           ],
           "type": "UNIQUE_HASH_INDEX"
         }
       ]
    }
  }
}

Here is performance for a small portion after changes.
BEGIN ETL PROCESSOR
+ extracted 0 records (0 records/sec) - 0 records -> loaded 0 vertices (0 vertices/sec) Total time: 1000ms [0 warnings, 0 errors]
+ extracted 164 records (164 records/sec) - 164 records -> loaded 81 vertices (81 vertices/sec) Total time: 2s [0 warnings, 0 errors]
+ extracted 716 records (544 records/sec) - 716 records -> loaded 357 vertices (272 vertices/sec) Total time: 3014ms [0 warnings, 0 errors]
+ extracted 1,388 records (672 records/sec) - 1,388 records -> loaded 693 vertices (336 vertices/sec) Total time: 4014ms [0 warnings, 0 errors]
+ extracted 2,070 records (682 records/sec) - 2,070 records -> loaded 1,034 vertices (341 vertices/sec) Total time: 5014ms [0 warnings, 0 errors]
+ extracted 2,718 records (648 records/sec) - 2,718 records -> loaded 1,358 vertices (324 vertices/sec) Total time: 6014ms [0 warnings, 0 errors]
...
+ extracted 23,972 records (524 records/sec) - 23,972 records -> loaded 11,985 vertices (262 vertices/sec) Total time: 53025ms [0 warnings, 0 errors]
+ extracted 24,310 records (338 records/sec) - 24,310 records -> loaded 12,154 vertices (169 vertices/sec) Total time: 54025ms [0 warnings, 0 errors]
+ extracted 24,594 records (284 records/sec) - 24,594 records -> loaded 12,296 vertices (142 vertices/sec) Total time: 55025ms [0 warnings, 0 errors]
END ETL PROCESSOR
+ extracted 24,599 records (25 records/sec) - 24,599 records -> loaded 12,299 vertices (15 vertices/sec) Total time: 55225ms [0 warnings, 0 errors]

Unfortunately, there is no difference. I have to load millions of edges and for now it would take hours, which is not acceptable in my use case.

@robfrank Hi, do you have any suggestions to my configuration from previous post to speed up loading edges?

 If you need a "one shot" import, you can switch off the server, import in plocal, and the re-start the server.

did you manage to load your datasets? May  I close this issue?

Hi, I have been on holidays for several weeks, so I can't try loading in plocal mode. The soonest I can check it is 15th of May, so please, wait at least one week from now. Thank you.

hi, did you check? may I close? in the meanwhile we released 2.2.21

Hi, thank you for your patience. Unfortunately, switching off the server and importing in plocal mode cannot be performed in my use case, I have to have it alive all the time. I think we have to close that issue and wait for 3.0 to be released. Has 2.2.21 improved parallel execution because it's not mentioned in release notes (or maybe I'm blind)?


github: Add security header

Tying in with #1389, this will add a new section
to the 'create new issue' and also be visible in the
'security' tab on GitHub
It's been left intentionally generic.
examples:
https://github.com/Zarthus/monolog/security/policy
https://github.com/Zarthus/monolog/issues/new/choose
in an established project: https://github.com/symfony/symfony/issues/new/choose

Thanks


Catch  \Throwable in PHP 7 so that fatal errors do not halt test execution (how?)

I would like to contribute a patch for this, but I have a few questions before I can do that.
Now PHP 7 is out, fatal errors no longer need to halt test execution. It looks like appropriate place in  makeCall method in  in the CallCenter class
public function makeCall(Call $call)
{
    try {
        $filteredCall = $this->filterCall($call);
        $result = $this->handleCall($filteredCall);
        $filteredResult = $this->filterResult($result);
    } catch (Exception $e) {
        return new CallResult($call, null, $e, null);
    } catch (\Throwable $e) {
        // Cast \Throwable to \Exception?
        $e = throwableToException($e);
        return new CallResult($call, null, $e, null);
    }

    return $filteredResult;
}

I have something along these lines working however I am not sure how to handle the cast of Throwable to Exception in the context of Behat.  Symfony handles it via  FatalThrowableException but to be frank I don't fully understand the constructor of that class, why is ErrorException instantiated but not assigned for example?
I would appreciate any pointers to getting a PR open (or a PR would be great too)

why is ErrorException instantiated but not assigned for example?

it is not instantiated. The ErrorException constructor is called because we want its behavior without having the behavior of the FatalErrorException constructor (which is in between in the class hierarchy)

@stof what does calling ErrorException::__construct do in this circumstance?

@peterjmit it applies the logic of the ErrorException constructor (we would write it as parent::__construct if ErrorException was the direct parent in the class hierarchy)

@stof ah, I wasn't aware you could do that (effectively skip constructors up the class hierarchy if I am now understanding correctly) - you learn something new every day: thanks!

@peterjmit that would be awesome if you could PR this one!


Bug: lexical/table $insertTableRow__EXPERIMENTAL does not properly handle th-element on a row

If you use the function while making table from scratch, it works fine.
However, if you save the html and then later create a new editor state from it by doing something like
const parser = new DOMParser()
let dom = parser.parseFromString('html goes here', 'text/html')
const nodes = $generateNodesFromDOM(editor, dom)
const root = $getRoot()
root.clear()
root.append(nodes)
if you then do
console.log(JSON.stringify(editorState.toJSON()))
you can see all the th-elements in tables have __headerState 1. Even ones that are row headers.
As far as I can see when you then add a new row using $insertTableRow__EXPERIMENTAL, it checks if the __headerState is 2 (https://github.com/facebook/lexical/blob/07e300c60c4f1d7a5f63dd9ac983c1a0cf7133f0/packages/lexical-table/src/LexicalTableUtils.ts#L305)
The check then fails.
Lexical version: 1.19.0
Steps To Reproduce

Create a table containing th at the start of each row in editor. Serialize it and deserialize it
Insert a new row using $insertTableRow__EXPERIMENTAL
The new row has a td instead of th

The current behavior
Row heading cell is always created as td element
The expected behavior
Row heading element is created as a th element, if the focus row has a th element
Impact of fix
Problem happens every time an existing table is edited and annoys people who use the tool daily

These instructions are not clear enough to reproduce the issue.


miniflux: 2.0.23 -> 2.0.27

Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[x] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

This is a semi-automatic executed nixpkgs-review with nixpkgs-review-checks extension. It is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
If you have any questions or problems please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 111465 run on x86_64-darwin 1

1 package built:

miniflux

This is a semi-automatic executed nixpkgs-review with nixpkgs-review-checks extension. It is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
If you have any questions or problems please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 111465 run on x86_64-darwin 1

1 package built:

miniflux

Looks good to me - I wonder if there is a way to get the client tests running within the sandbox environment, presumably they only require loopback network access?

Unfortunately they it seems to require external network connections -- it connects to httpbin https://github.com/miniflux/v2/blob/2cf9bde1af259bd3a2a82471ea5885853e367f53/http/client/client_test.go#L12


Native look

Is it possible, or does someone already made some styles to make it look more native like this package does?

It's definitely possible to style it to look more native by supplying custom styling under the styles prop (you could make it look similar to both the native iOS and Android looks). We'll see if someone might be able to help you out with some examples?
There's currently no way to achieve the 'squished' look of the numbers above and below the picker, as in the screenshot you shared. To achieve that, we'd need use the React Native Animated API and scale each item in the picker based on its position in the viewport. It's possible but isn't on the roadmap right now.

Hey @andredewaard, there hasn't been any activity on this issue for a while. If there are no further updates or discussions in the next 2 weeks, I'll close this issue to keep the repository tidy. Please let me know if this is still relevant or if there are any updates. Thanks!


Rancher webhook issue

I have some issues with Webhook, maybe someone can help me out with this...
In Rancher 2.5.12 user permissions can not be changed or new user can not be created, Rancher upgrade is also not possible,
tried to upgrade Kubernetes successfully to v1.19.16, but issue still exist.
Error: Error deleting
Internal error occurred: failed calling webhook "rancherauth.cattle.io": Post "https://rancher-webhook.cattle-system.svc:443/v1/webhook/validation?timeout=10s": context deadline exceeded
In some clusters the cluster agent is not able to connect to proxy randomly. ( one time it's connect one time it's not )

Same problem

This solved the problem for me.
https://stackoverflow.com/questions/72499287/error-creating-new-user-or-granting-for-user-permissions-on-rancher/73196918#73196918


Declaration expanded from macro is not visible in scope

Description

The declaration expanded from the following minimal macro example is not visible in the scope of the expansion:
// in module "ExampleMacro":

import SwiftCompilerPlugin
import SwiftSyntax
import SwiftSyntaxBuilder
import SwiftSyntaxMacros

public struct DefineEmptyStructMacro: DeclarationMacro {
	public static func expansion(
		of node: some FreestandingMacroExpansionSyntax,
		in context: some MacroExpansionContext
	) throws -> [DeclSyntax] {
		return ["struct Empty {}"]
	}
}

@main
struct MacroTestPlugin: CompilerPlugin {
	let providingMacros: [Macro.Type] = [
		DefineEmptyStructMacro.self,
	]
}

// in a different module that depends on "ExampleMacro":

@freestanding(declaration, names: named(Empty))
macro empty() = #externalMacro(module: "ExampleMacro", type: "DefineEmptyStructMacro")

#empty()

extension Empty: Equatable {} // error: cannot find type 'Empty' in scope

By my understanding, when Empty is looked up, #empty is requested to expand because it declares a new Empty. So, when the name lookup finishes, Empty should be visible to the extension declaration.
Steps to reproduce

Create a package that contain the 2 modules above.

Build it.

Expected behavior

Declarations expanded from macro should be visible in the same scope.

Environment

Swift

Bundled in Xcode 15.0 beta (15A5160n): swift-driver version: 1.82.2 Apple Swift version 5.9 (swiftlang-<IP_ADDRESS>.6 clang-15<IP_ADDRESS>)
2023-06-07 trunk snapshot: Apple Swift version 5.9-dev (LLVM 677d82daa6d87d2, Swift 291fe21d5020234)

Xcode 15.0 beta (15A5160n)
macOS 13.4 x86_64

Additional context
Relevant forums post that contains more or less the same information: https://forums.swift.org/t/declaration-expanded-from-macro-is-not-visible-in-scope/65516

I'm running into the same issue, and I have the same expectation that we should be able to extend a type generated by a macro.
From what i'm seeing, the type is accessible at the scope you're demonstrating, but its not visible to be extended.


choreadd one option to skip build be when running ut

Proposed changes
Issue Number: close #xxx
Previously when we run be ut, it would always run building the whole binary. But sometimes I just change one conf in be.conf to test the UT, I think it would help when we just wanna run one UT without building it.
Problem summary
Describe your changes.
Checklist(Required)

Does it affect the original behavior:

[ ] Yes
[x] No
[ ] I don't know

Has unit tests been added:

[ ] Yes
[x] No
[ ] No Need

Has document been added or modified:

[ ] Yes
[ ] No
[x] No Need

Does it need to update dependencies:

[ ] Yes
[x] No

Are there any changes that cannot be rolled back:

[ ] Yes (If Yes, please explain WHY)
[x] No

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

If we didn't modify the source code, the build for BE should be skipped by running the command ./run-be-ut.sh --run. Would you like to provide some steps to describe the scenario you mentioned.

Would you like to provide some steps to describe the scenario you mentioned.

Hi there, I was trying to deploy the ut binary from compile machine to another machine in another region in another cloud vendor to test some feature like downloading object storage file from the corresponding cloud platform using different threads nums which is configured by be.conf.
And i ran into such scenario where the logic would try to find related CMake build files each time I type bash run-be-ut.sh --run --filter=MyTest.*. And unfortunately it failed cause there is no such thing. I think maybe it would help if we can manually choose to skip the related build steps when i just need to deploy only the binary to another machine to test the effects brought by another environment.

Would you like to provide some steps to describe the scenario you mentioned.

Hi there, I was trying to deploy the ut binary from compile machine to another machine in another region in another cloud vendor to test some feature like downloading object storage file from the corresponding cloud platform using different threads nums which is configured by be.conf. And i ran into such scenario where the logic would try to find related CMake build files each time I type bash run-be-ut.sh --run --filter=MyTest.*. And unfortunately it failed cause there is no such thing. I think maybe it would help if we can manually choose to skip the related build steps when i just need to deploy only the binary to another machine to test the effects brought by another environment.

Maybe you can run binary ut directly, there is a exaple:
/be/ut_build_RELEASE/test/doris_be_test
--gtest_filter=GeoFunctionsTest.st_polygon
--gtest_output=xml:/mnt/disk1/xx/incubator-doris/be/ut_build_ASAN/gtest_output/doris_be_test.xml
--gtest_print_time=true

Would you like to provide some steps to describe the scenario you mentioned.

Hi there, I was trying to deploy the ut binary from compile machine to another machine in another region in another cloud vendor to test some feature like downloading object storage file from the corresponding cloud platform using different threads nums which is configured by be.conf. And i ran into such scenario where the logic would try to find related CMake build files each time I type bash run-be-ut.sh --run --filter=MyTest.*. And unfortunately it failed cause there is no such thing. I think maybe it would help if we can manually choose to skip the related build steps when i just need to deploy only the binary to another machine to test the effects brought by another environment.

Maybe you can run binary ut directly, there is a example:
/be/ut_build_RELEASE/test/doris_be_test
--gtest_filter=GeoFunctionsTest.st_polygon
--gtest_output=xml:/mnt/disk1/xx/incubator-doris/be/ut_build_ASAN/gtest_output/doris_be_test.xml
--gtest_print_time=true

It works well, i'll close this pr soon.


Docker version

I have a quite some big channel plus I can use some aws resources.
For this docker image would be ideal

Can work on this, the change should be trivial.

would be nice to have threadcount/enableproxy options.
I plan to run them outside Ukraine

here is a headless version + docker https://github.com/sviatoslav-lebediev/uashield
docker run -it --init --rm   \
-e SITE_FILE="https://raw.githubusercontent.com/opengs/uashieldtargets/master/sites.json" \
-e PROXY_FILE="https://raw.githubusercontent.com/opengs/uashieldtargets/master/proxy.json" \
-e WORKERS_COUNT=50 moro/uashield-cli:latest

docker run -it --init --rm  -e SITE_FILE="https://raw.githubusercontent.com/opengs/uashieldtargets/master/sites.json" -e PROXY_FILE="https://raw.githubusercontent.com/opengs/uashieldtargets/master/proxy.json" -e WORKERS_COUNT=50 moro/uashield-cli:latest

clone or download repository. It is better cloning. We will be able to use updates faster and suit!
Win+R "cmd"
cd /D "path to the folder with Dockerfile"
docker build -t uashield .

I've synced https://github.com/sviatoslav-lebediev/uashield-cli with last changes + updated moro/uashield-cli:latest image you can pass -e NON_VERBOSE_ERROR=true and the output will be less noisy.
docker run -it --init --rm -e SITE_FILE="https://raw.githubusercontent.com/opengs/uashieldtargets/master/sites.json" -e PROXY_FILE="https://raw.githubusercontent.com/opengs/uashieldtargets/master/proxy.json" -e NON_VERBOSE_ERROR=true -e WORKERS_COUNT=50 moro/uashield-cli:latest

Hmm docker version is now available here
https://github.com/opengs/uashield/pkgs/container/uashield
Sorry @sviatoslav-lebediev i didn't checked that you already made amazon work :(
maybe we can somehow use something from your project?
im preety sure that we can improve headless version

@Razikus yep, it would be great to have just one repo instead of 2
I've created a PR https://github.com/opengs/uashield/pull/57, it reduces a docker image in  4 times :)
As you could see my version supports custom SITE_FILE/PROXY_FILE/NON_VERBOSE_ERROR env variables. if you want I can create a PR for these features.

Docker version in 0.0.9 release


api-docs: Fix endpoint formatting in API changelog and feature levels 11 and 12 changes/entries.

Specific changes:

Updates the last remaining reference to "private messages" in the API changelog to be "direct messages", which was in the feature level 11 entry for POST /typing.
Adds a Changes note to is_owner in the POST /register response for when it was added in feature level 11.
Fixes the feature level for when the GET /users/{user_id}/subscriptions/{stream_id} endpoint was added from feature level 11 to feature level 12.
Does a sweep of the formatting for endpoints in the API changelog for missing backslashes and a few other inconsistencies.

Addresses feature level 11 and 12 points in #22102.

Screenshots:

Updated feature level 11 and 12 entries
Current documentation

Self-review checklist

[ ] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[ ] Explains differences from previous plans (e.g., issue description).
[ ] Highlights technical choices and bugs encountered.
[ ] Calls out remaining decisions and concerns.
[ ] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[ ] Each commit is a coherent idea.
[ ] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[ ] Visual appearance of the changes.
[ ] Responsiveness and internationalization.
[ ] Strings and tooltips.
[ ] End-to-end functionality of buttons, interactions and flows.
[ ] Corner cases, error conditions, and easily imagined bugs.

Merged, thanks @laurynmm!


tls_process_server_hello: Disallow repeated HRR

Repeated HRR must be rejected.
Fixes #17934
Checklist

[x] tests are added or updated

I'd like to add a test.
@mattcaswell Is there a way how to test this via TLS Proxy?
Otherwise I'd just do something with the fuzz data and create a test code similar to the client fuzzer.

@mattcaswell Is there a way how to test this via TLS Proxy?

Yes. Here is an example of a TLSProxy test injecting a custom ClientHello into the communication. That particular test injects it in an SSLv2 record - but that's a simple flag that you wouldn't use in your test. The same principles should be applicable to injecting an extra HRR.
https://github.com/openssl/openssl/blob/9e1a54f4a187195fc417ad0f90e84d208d478968/test/recipes/70-test_sslrecords.t#L336-L406

@mattcaswell do you have any idea why the test fails? Basically the alert is sent by the client much later than expected - in flight 4 and not in flight 2.

I will try and take a look later today.

It is interesting that sometimes it is sent in flight 2 and sometimes in flight 4. Perhaps depends on timing?

Flight 4 seems correct?
Client                                        Server
-------                                       ------
Initial Client Hello (flight 0)
                                              HRR1 (flight 1)
Second Client Hello (flight 2)
                                              HRR2 (flight 3)
Alert (flight 4)

But flight 2 does not seem right.

Ping? What's happening with this?

Yeah, this looks better now. @tmshort please reconfirm.

This pull request is ready to merge

Merged to master, 3.0, and 1.1.1 branches. Thank you for your reviews.

Need to include:
#include "statem.h"
for SSLfatal macro usage.


Fix load memory from file to work with binary

Passed in hexOrBinary parameter to ChiselLoadMemoryAnnotation
Test included
Fixes #1582
API Impact
No change in API
Backend Code Generation Impact
Allows $readmemb to be generated when the user specifies MemoryLoadFileType.Binary.
Desired Merge Strategy
Squash
Release Notes
Fixed bug in loadMemoryFromFile that caused the hexOrBinary parameter to be ignored.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.0 out of 2 committers have signed the CLA.:x: Tony Wu:x: HappyQuarkTony Wu seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Release 2.2

Was wondering what the status was on releasing 2.2. There seem to be several things scheduled for 2.2, but am unsure if they are all required. Are there things you need help with?

Any thoughts on this @alimanfoo?

Thank you for the offer, apologies I'm under a deadline and have had to put OSS on hold for the moment.
FWIW The next thing I wanted to do for the 2.2 release was to set up a data fixture (#138) which would provide some protection against any regressions that accidentally break backwards compatibility with the data format. That would then allow safe merging of the numcodecs refactoring work (#139, #74).
Apart from that, the following I would classify as high priority for 2.2. These are mostly boring but important bug fixes, except for the tree printing which is very exciting :-) ...

Group print hierarchy (#140, #82)
Index with numpy int64 #143
Various repr tweaks (#132, #115, #83)
Specification for datetime dtypes is ambiguous #85
Don't include partial files when counting initialized chunks #97

The following would be nice to have but could live without for this release:

Usability tweaks to zarr.open (https://github.com/alimanfoo/zarr/issues/141, https://github.com/alimanfoo/zarr/issues/105)
Adding attrs arg to create_group and create_dataset #121
Add a save() function similar to numpy.save/numpy.savez #104
Tweak and doc chunks kwarg (#106, #107)
Copy method #113
Group.put() #81
Compute hash of array #98
Key encoding for dbm-style databases #133
Some doc improvements (#103, #91, #131)

There are also a set of issues relating to indexing (#89, #93, #78, #116, #119). It would be nice to resolve all these together with some reworking of the indexing code. The code you have in kenjutsu is nice and I'd really like to draw on that, but I think there are some performance bottlenecks in there which could manifest in Zarr if we just depend on kenjutsu as-is, and I wanted to explore some options. This may all be best left for a subsequent release, it's not a small piece of work.

Tracking release 2.2 via: https://github.com/alimanfoo/zarr/milestone/5


Mod fill visualizer on resize throws error

I tried the ModFill visualizer with default options on A006769, and when resizing the window produced this console error:
P5Visualizer.ts:112 Uncaught RangeError: Cached: Index 301 not in 0..300.
    at Proxy.getElement (Cached.ts:112:19)
    at Proxy.drawNew (ModFill.ts:55:27)
    at Proxy.draw (ModFill.ts:76:14)
    at sketch.draw (P5Visualizer.ts:106:26)
    at o.default.redraw (p5.js?v=1eaac891:11599:22)
    at l.default.resizeCanvas (p5.js?v=1eaac891:11226:24)
    at Proxy.windowResized (P5Visualizer.ts:177:22)
    at o.default._onresize (p5.js?v=1eaac891:9912:73)

This is occurring because draw is called again automatically by p5 when the canvas resizes, and the ModFill code just goes ahead and increments the index again even though it already got to the limit. (To be fair, the original author of ModFill did not realize it was possible for draw() to be called again after it had called noLoop().) Anyhow, we need to make visualizers in general resilient to draw being called again after the visualizer thinks it is "done".

[Should be resolved by ui2; I guess we should come through the whole issue list thereafter.]

Indeed, this is working fine in ui2, so closing.


Login fails using Puppeteer on Debian9 VM (headless) under HyperV

I am running Puppeteer under Node.js on a VM image of Debian 9 (headless). Several puppeteer scripts run correctly on that image. However, in one case Puppeteer does not work. The site requires a login before I can get to the data. Here is the js code snippet that works on a GUI install version of OpenSUSE 42.3, but fails on Debian.
(async() => {
const browser = await puppeteer.launch({
headless: true,
args:['--no-sandbox', '--disable-setuid-sandbox']
});
const page = await browser.newPage();
await page.goto(
'http://mysite', {
waitUntil: 'networkidle2'
});
await page.click(UNAMEFIELD);
await page.keyboard.type("USERNAME");
await page.click(PWDFIELDNAME);
await page.keyboard.type("SUPERSECRETPWD");
await page.click(PWDFIELDNAME);
await page.screenshot({ path: 'screenshots0.png' });
await page.click(LOGINBUTTON);
await page.waitForNavigation();
I can verify the user name is entered and I can verify (by manually logging in) that the pwd is good. The identical script runs on full GUI openSUSE installs. I can see that the site rejects the login based on the username/password. Beyond that, I am also seeing this error with casperjs/phantomjs scripts (on the same Debian9 instance). There would seem to be some common dependency that hamstrings both sets of tool.  I am out of ideas, any help would be greatly appreciated!

This was a bug in user code which generated improper credential. Mea culpa!


[completion] Filter completions on the server side

Implement server-side code-completion filtering and limit the number of completion items to 200 results by default. This radically improves the performance of code-completion when there are a large number of results by avoiding the cost of serialization of lower priority results. We take advantage of LSP's isIncomplete flag to inform the editor that as the user types more characters it should re-query SourceKit-LSP for completions in case there are results that were previously filtered out that are now relevant to the new filter text.
I verified that server-side filtering is working in VSCode, Sublime Text, and vim (with coc.nvim).  If any editors do not support isIncomplete yet, it is possible to disable server-side filtering.
Configuration

By default, server-side filtering is enabled, and the maximum number of results is 200.
You can override this using command-line options to sourcekit-lsp

sourcekit-lsp -completion-server-side-filtering=true -completion-max-results=200

Alternatively, you can override this by passing initializationOptions to SourceKit-LSP during the initialize request:

"initializationOptions": {
    "completion": {
        "serverSideFiltering": true,
        "maxResults": 200
    }
}

As an LSP extension, we also support passing completion options directly in the textDocument/completion request using the new parameter sourcekitlspOptions. This is intended mostly as a tool for experimentation and debugging.

Note: In the initial implementation, setting maxResults to unlimited (0 or nil) will have worse performance than if you disabled server-side filtering.  We should be able to close that gap, but for now I don't recommend using large values for maxResults.
Implementation
When using server-side filtering, we keep track of a code-completion "session" for a given source file and completion location.
foo.barB|
    ^   ^
    |    ` cursor location
     ` start of identifier

In the above example, the completion session will be for the location after "." at the start of the identifier, and the completion location (usually the cursor location) determines what the "filter text" for the completion will be, in this case "barB".
Once we open a session, any subsequent completion requests that have the same location and use triggerKind == triggerFromIncompleteCompletions will efficiently re-filter the existing completions.  If the new completion location is not compatible with the session, we return an error rather than recompute completions so that editors can rely on triggerFromIncompleteCompletions always being really fast.  Currently, any other trigger kind (manual or trigger character) will open a new completion session, although we could improve that in the future to reuse the session if no other changes have been made to the document.
The underlying filtering uses sourcekitd's complete.open, complete.update and complete.close requests.

@swift-ci please test


Sticky blog posts

The option of making one or more blog (child) pages sticky, and always being displayed at the top of a list page could be quite useful. For example, a course site that uses blog pages for weekly class content, and having announcements and/or preparations as sticky posts which are always listed before regular posts. I think that this option would bring a lot of new possibilities to Grav list pages.
In addition, it would be very useful to be able to assign a custom twig template for these sticky posts.

I did something similar to this in the mediator theme by having a featured taxonomy type.  These 'featured' posts are displayed at the top of the collection (no matter what page you are on).  See it in action here:
https://github.com/getgrav/grav-theme-mediator/blob/develop/templates/default.html.twig#L37

Amazing and simple! Just for completeness. What would be better for the end user: use powerful TWIG extensions or provide an option in the core like what you have already done in the mediator theme?

I really don't see the need to put something so specific in the core when this can be achieved already with taxonomy or another collection query and Twig.


Test001_gt，Please help me

i want to konw Test001_gt is a folder（there is amat file or a txt file in it） or a txt file or a mat file？
Thank you！

@LiUzHiAn

please download the ped2 dataset here. http://www.svcl.ucsd.edu/projects/anomaly/UCSD_Anomaly_Dataset.tar.gz

@LiUzHiAn Thank you so much！


setting a custom provider on IdentityServerBearerTokenAuthenticationOptions doesn't work

As noted here setting a custom provider or setting a custom function to the OnRequestToken of the default provider does not work.  Here are my examples
    app.UseIdentityServerBearerTokenAuthentication(new IdentityServerBearerTokenAuthenticationOptions
    {
        Authority = "https://localhost:44300/identity",
        RequiredScopes = new[] {"csRA"},
        Provider = new CustomOAuthBearerProvider("access_token")
    });

or here
    var options = new IdentityServerBearerTokenAuthenticationOptions
        {
            Authority = "https://login.codysoft.net/identity",
            RequiredScopes = new[] {"csRA"},
            Provider = new OAuthBearerAuthenticationProvider
            {
                OnRequestToken = context =>
                {
                    var request = context.Request;
                    if (request.Headers.ContainsKey("Authorization"))
                        context.Token = request.Headers["Authorization"];
                    else if (request.Cookies["access_token"] != null)
                        context.Token = request.Cookies["access_token"];
                    else
                    {
                        var value = request.Query.Get("access_token");
                        if (!string.IsNullOrEmpty(value))
                        {
                            context.Token = value;
                        }
                    }
                    return Task.FromResult<object>(null);
                }
            },
        };

        app.UseIdentityServerBearerTokenAuthentication(options);

no break point is hit in either sample.  It appears to be ignored completely.

I just tried it - and can't repro. Are you on the latest version?

ugh! no.  This is one of the ones I missed the update to when you guys switched names.  It never showed up in my updated package list.  Sorry for the confusion.  Perhaps it's even the reason I'm having problems with SuppressDefaultHostAuthentication.  Thank you.


Change runner to tarpaulin

Extracted just the change to tarpaulin.

Coverage: 85.214% (-3.4%) from 88.589% when pulling 1e945ba62b3aa28c3331d289d7b6a1d45b0614c3 on Czocher:change-coverage-runner into f3c45cd7d288eaaf80810e59aba48594553d170e on cljoly:master.

@cljoly branch ready to review/merge. I'm not sure why the source doesn't appear in the report, maybe it's due to the fact it's on my fork, but I'm not sure.

I'm not sure why the source doesn't appear in the report, maybe it's due to the fact it's on my fork, but I'm not sure.

It does that sometimes on feature branches, even for me. But it might also be the same issue as cargo llvm-cov when using doc-test coverage. We can merge and revert if it we still don’t have the sources.

Ah it does work, needed to be signed it since it's on my own repo :D.

The relevant part of the CI takes a reasonable amount of time (less than a minute, when other take 1-2 minutes) and it is about the same as cargo llvm-cov afaik:

So that’s acceptable. I think it’s the local development experience that is worse:
time cargo tarpaulin --verbose --all-features --run-types AllTargets --workspace --timeout 120 --out Lcov
…
________________________________________________________
Executed in   79.93 secs    fish           external
   usr time  192.16 secs    0.00 millis  192.16 secs
   sys time   34.47 secs    2.60 millis   34.46 secs

vs
time cargo llvm-cov --workspace --all-features --lcov
…
________________________________________________________
Executed in    7.42 secs    fish           external
   usr time   16.33 secs    0.00 millis   16.33 secs
   sys time    3.94 secs    1.71 millis    3.94 secs


ERROR: failed to build: executing lifecycle. This may be the result of using an untrusted builder: failed with status code: 51

ERROR: failed to build: executing lifecycle. This may be the result of using an untrusted builder: failed with status code: 51

This is while trying to test a python cloud function

@gsolorza can you give some more information and steps to reproduce? How are you building the application? locally with pack ? with Cloud Build?

Hi James,
I was testing cloud functions.
When I try to test the function before deploying it gives me the following
error. Apparently is complaining about the version of Python (which I am
selecting from a dropdown).
If I try with an older version of Python, this does not happen.
[image: image.png]
George SolórzanoNetwork Consulting Engineer
CCIE # 45634 (SP)
*+56 958164514 *
On Fri, Jan 26, 2024 at 1:53 PM James Ma @.***> wrote:

@gsolorza https://github.com/gsolorza can you give some more
information and steps to reproduce? How are you building the application?
locally with pack ? with Cloud Build?
—
Reply to this email directly, view it on GitHub
https://github.com/GoogleCloudPlatform/buildpacks/issues/376#issuecomment-1912375127,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHPHBAQOJZQOKDIDGCNDMHTYQPNQVAVCNFSM6AAAAABCA2YGT6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMJSGM3TKMJSG4
.
You are receiving this because you were mentioned.Message ID:
@.***>

Thanks for the clarification! I managed to reproduce it on my side. I'll dig into it.
In general, this issue tracker shouldn't be used to report GCP-specific issues, but in this case I'll allow it 😄

Fix just went live earlier today.

Awesome, thanks !!

I'm still getting this error. Can anyone help


Empty policy files exit with error code of 1

I'm experiencing an issue with custodian returning an error if you try to run a yml file with zero policies. This behavior in <IP_ADDRESS> is a depature from previous version where it would return an exit code of 0.
2017-02-17 14:05:03,027: custodian.commands:DEBUG Loaded file /custodian/policy.yml. Contains 0 policies (after filtering)
Error: empty policy file(s).  Nothing to do.

Where in the code the error is coming from:
https://github.com/capitalone/cloud-custodian/blob/6304ba2167ff2dbbaf2a9724ca8aa803667f4918/c7n/commands.py#L86-L101

so i think if the policy file is empty we can exit 0, if we get to an empty list as a result of filtering  (name, or type) i think we should continue to exit 1

@kapilt - I am happy to fix this if you aren't on it already - I wrote that code.

@mandeepbal @kapilt
The behavior I fixed when I touched this code last was that specifying an empty config file resulted in a huge schema dump, not a sensible error message.  This was an issue I filed - #859.  But I did not change the exit code as far as I can tell.
I just checked out releases dating back six months, but they all have exit code 1 if the policy file is empty (both if the file is totally empty, and also if it has a policies: line, but no policies specified).
What is your input that is causing this @mandeepbal, and what version was it zero?

i believe the input was
policies: []

@kapilt : Yeah - using that policy I am able to replicate what @mandeepbal is saying wrt the run subcommand.  But historically, the report and logs subcommands would both exit 1 if there were no policies supplied.
Those work a little different than run because they want one - and only one - policy while run accepts any number.  But which behavior do we want?  Should they match how run works and exit 0?  Or should they behave differently on that edge case?

Hey Everyone. I've been getting the same error for literally every code I've been trying implement.

Is this an spacing issue?

@cjsandeep - the issue from this was fixed a long time ago.  Can you show the policy you are trying along with the error it is returning?

policies:

name: tag-compliance
resource: ec2
description: |
Identify resources that does not meet tag compliance policies to be notified via email
filters:

tag:Contact : absent
tag:Service : absent
tag:Environment : absent
actions:
type: notify
template: default
priority_header: '2'
subject : Test8 with default
to:
-
transport:
type: sqs
queue:

Getting the same error on this policy


Switch building system from IntelliJ to Gradle

What
This PR changes the building system from IntelliJ to Gradle, allowing for easier dependency management and distribution.
It also changes dependencies whether possible to download from the maven central repository instead of having it on the github repository to avoid future license conflicts.
The biggest change is that libraries are not embed anymore into Raylib itself, this should avoid future license conflicts as well but I can revert that if needed. I'm also not sure whether an inclusion of libraries will prevent a publication on maven Central.
Closes #44

Awesome work! Thanks for taking care of that.

@CreedVI Is there an Discord or something in that direction where it's possible to talk about Raylib-J?

@Irgendwer01 you can always find me in the #Raylib-JVM channel of the Taylor discord https://discord.com/invite/raylib

Hi! I am trying to contribute to the project but I am not able to figure out how to build it properly with Gradle. Could you provide some basic instructions? I am using IntelliJ IDEA and have all of these options, but no matter what I do I can't seem to run a hello world when compiling from source.

I have tried sticking a main function in the Raylib.java file, I have tried compiling to .jar and including it in a seperate project, nothing seems to work. I have never used Gradle before so please excuse my noobishness! :)
@Irgendwer01 @CreedVI

@ejenk0
You use the "build" task under the build folder in your gradle tasks to build the .jar
From there you have to include the .jar you compiled in your new project. What are the errors you're receiving from the fresh project? Feel free to reach out in the Raylib discord if you need help


cmd-forwarder-vpp started reaching memory limits during basic, heal tests on packet with new VPP

Expected Behavior
cmd-forwarder-vpp shouldn't reach memory limit during tests.
Current Behavior
cmd-forwarder-vpp reaches current memory limit (400Mi) during basic, heal tests on packet after VPP upgrade.
Steps to Reproduce
Run basic, heal tests on packet.
Context
Tested on deployments commits:

with old VPP : ce003f5d821c761aaafd195cf51e8b359a6652d3
with new VPP : 692b0865a7ea7dda5f6ab31e1490169f8f142dae

@edwarnicke This is not reproducing with https://github.com/networkservicemesh/deployments-k8s/pull/2793
I think we need to consider why do we need now 500Mi  this after release


Add validation error code to API

I want to merge this change because it adds error codes to API.
Example:
mutation {
  categoryUpdate(id:"Q2F0ZWdvcnk6Ng==", input:{slug:"a b"}) {
    errors{
      field
      message
      code
    }
  }
}

outputs
{
  "data": {
    "categoryUpdate": {
      "errors": [
        {
          "field": "slug",
          "message": "Wpisz poprawną uproszczoną nazwę zawierającą jedynie litery, cyfry, podkreślenia i myślniki.",
          "code": "invalid"
        }
      ]
    }
  }
}

TODO:

[ ] Use enum as code instead of string
[ ] Ensure that all custom errors in various mutations have code property

It allows front end to format its own messages instead of relying on API output.

Pull Request Checklist

[ ] Privileged views and APIs are guarded by proper permission checks.
[ ] All visible strings are translated with proper context.
[ ] All data-formatting is locale-aware (dates, numbers, and so on).
[ ] Database queries are optimized and the number of queries is constant.
[ ] The changes are tested.
[ ] The code is documented (docstrings, project documentation).
[ ] GraphQL schema and type definitions are up to date.

I like the idea and would love to see that implemented in entire API. I agree that we should use enums for codes, but I'm also fine with introducing changes gradually :)

Adding error codes to API is something that we have to definitly work on, but I'd do that in a new PR. There is a PR (#3891 ) that reworks error handling in API and it will be much easier to add statuses once it's merged.


feat: add new learning events for course grades and badges

Description:
This is a prerequisite work for the new Badges with Credly integration feature.
Changes

Adds a new dependency:

edx-ccx-keys

Implements new custom serializer:

CcxCourseLocatorAvroSerializer

Implements new data classes:

CcxCourseData (CCX specific course data)
CoursePassingStatusData (current course grade passing status for user)
CcxCoursePassingStatusData (current CCX course grade passing status for user)
BadgeTemplateData (badge template credential type)
BadgeData (badge user credential)

Adds new public signals:

COURSE_PASSING_STATUS_UPDATED (course grade update with passing status)
CCX_COURSE_PASSING_STATUS_UPDATED  (CCX course grade update with passing status)
BADGE_AWARDED (new badge awarding for user)
BADGE_REVOKED (existing badge revocation for user)

ISSUE: https://github.com/openedx/platform-roadmap/issues/280
Dependencies: this PR itself is a blocker for 2 PRs (LMS, Credentials) which are work in progress.
Merge deadline: ASAP when possible.
Installation instructions: nothing special.
Testing instructions: noting special.
Reviewers:

[ ] @mariajgrimaldi
[ ] @justinhynes

Merge checklist:

[ ] All reviewers approved
[ ] CI build is green
[ ] Version bumped
[ ] Changelog record added
[ ] Documentation updated (not only docstrings)
[ ] Commits are squashed

Post merge:

[ ] Create a tag
[ ] Check new version is pushed to PyPI after tag-triggered build is
finished.
[ ] Delete working branch (if not needed anymore)

Author concerns:
This PR is a blocker for further LMS/Credentials contribution, since both services depend on the future openedx-events version that includes these signals/data.

Thanks for the pull request, @kyrylo-kh! Please note that it may take us up to several weeks or months to complete a review and merge your PR.
Feel free to add as much of the following information to the ticket as you can:

supporting documentation
Open edX discussion forum threads
timeline information ("this must be merged by XX date", and why that is)
partner information ("this is a course on edx.org")
any other information that can help Product understand the context for the PR

All technical communication about the code itself will be done via the GitHub pull request interface. As a reminder, our process documentation is here.
This is currently a draft pull request. When it is ready for our review and all tests are green, click "Ready for Review", or remove "WIP" from the title, as appropriate.

:warning: We can't start reviewing your pull request until you've submitted a     signed contributor agreement     or indicated your institutional affiliation. Please see the CONTRIBUTING     file for more information.     If you've signed an agreement in the past, you may need to re-sign.  See     The New Home of the Open edX Codebase     for details.
Once you've signed the CLA, please allow 1 business day for it to be processed.  After this time, you can re-run the     CLA check by adding a comment here that you have signed it.  If the problem persists, you can tag the @openedx/cla-problems team in a     comment on your PR for further assistance.

Hi @kyrylo-kh! Thanks for this contribution. It looks like you're contributing on behalf of Raccoon Gang. In order to get you added to Raccoon Gang's entity CLA agreement, please have your manager reach out to<EMAIL_ADDRESS>Thank you!

Context: Credentials Badges (+Credly integration).
This is a WIP PR to make possible early feedback. We have started from the bare minimum, but the details are still a matter of shaping.

@kyrylo-kh pls update the description as well.

Thank you for the contribution! Could you remove the --index-url http://edx.devstack.devpi:3141/root/pypi/+simple/ so we can run the workflows? Thanks!

@mariajgrimaldi requirements are clean now.

@mariajgrimaldi For some reason documentation CI cannot find the latest alabaster==0.7.16.
Should we bother with it?

@wowkalucky: I'll be looking into it. Thank you!

Do you folks have a draft PR in the service from where these events will be sent?

@mariajgrimaldi here related Platform draft PR.

I like the suggestion of refactoring the status property with constants to is_passing = <bool> as a more explicit option.

@mariajgrimaldi This is ready for the final review, it'll be good if we could bump version and merge related edx-platform PR  after requirements update before Redwood cut 😊

@wowkalucky: could you please address this last comment? Thank you. I'll merge once that's done.

@kyrylo-kh 🎉 Your pull request was merged!  Please take a moment  to answer a two question survey so we can improve your experience in the future.

v9.10.0 released! Thank you all.


安装mosdns，菜单也没出现，

update list
过滤mosdns 发现没有luci，
查看启动  发现mosdns 有启动  同时还发现adgardhome 也启动了，同时没有安装 也没显示
想起nicholas-opensource说过
“
AdguardHome：无存在意义，一个enable=1就可以运行
”
请教在哪修改enable=1，
有多少个插件跟adgardhome 一样修改配置enable 就能启动
查看
Issue template:

Please make sure that the issue subject starts with <package-name>:
Issues related to end of life (EOL) releases are not supported or maintained and will be closed
Remove lines from top till here and fill in the following questions

Steps to reproduce:
Example: Replace the following lines and remove this

go to: Network → Interfaces → LAN (an interface with a static address) → DHCP server tab → IPv6 RA settings tab
set RA MTU and RA Hop Limit to arbitrary non-default value
Save & Apply
go to: IPv6 RA settings tab again

Actual behavior:
Example: Replace the following lines and remove this

option ra_mtu '1500' is set correctly in /etc/config/dhcp
In LuCI though, RA MTU and RA Hop Limit are still displaying the default values in light gray font color.

Expected behavior:
Example: Replace the following lines and remove this
RA MTU and RA Hop Limit are displaying the correct values found in /etc/config/dhcp in black font color.

Additional Information:
OpenWrt version information from system /etc/openwrt_release
Example: Replace the following lines and remove this
DISTRIB_ID='OpenWrt'
DISTRIB_RELEASE='21.02.0-rc4'
DISTRIB_REVISION='r16256-2d5ee43dc6'
DISTRIB_TARGET='x86/64'
DISTRIB_ARCH='x86_64'
DISTRIB_DESCRIPTION='OpenWrt 21.02.0-rc4 r16256-2d5ee43dc6'
DISTRIB_TAINTS=''

请教在哪修改enable=1

uci set adguardhome.config.enabled='1'
uci commit adguardhome
/etc/init.d/adguardhome restart

或者直接编辑 /etc/config/adguardhome 并重启 adguardhome

报错了，
uci：entry not found

报错后adguardhome是显示没安装，安装后再运行你给的命令可以了能。访问后台了


how to download the new version

Head  here . And stop creating new issues for the same problem. Download the last version (currently it's 2.4.3)

oh thanks

@Arwwaaa  btw , if you can, close the issues you brought up .


Flashing Chips with TrustZone

It seems like the target yaml files that correspond to TrustZone enabled chips contain flashing algorithms for both secure world and non-secure world. But it seems like there is no support in probe-rs to flash to the respective region based on the the binary's .text section's address or some other indicator.
I don't know how to implement such support or even if probe-rs is the right place for that.
What do you think?

In the target description file, you can see that every flash algorithm has a memory range attached. probe-rs determines for every sector in flash in that range it fits and which flash algorithm it has to use :) So the user doesn't have to configure anything, other than properly linking such that the sections are at the right memory locations :)

Does it matter that the targets only have a single Flash entry at 08000000, even though they have two algorithms for the two ranges?

Hmm this is actually a good question. I think so far we have not really tested this with non contiguos memory locations. So I am pretty sure this would fail if there is two different flashes, which I guess is the case for TrustZone based things?
So we would need all flashes there is :)

I think the device has one flash region, but it is aliased at both 0x0800_0000 and 0x0C00_0000, with one alias for nonsecure access only and one access which may be secure. I think the linker script and ELF have to contain the right alias, so probe-rs would end up trying to write to one or the other, but I'm not totally sure of the details.

Oh, I see. Well, if we only have a flash region from N to O and the ELF section is not contained in that, no matter the list of flash algorithms, probe-rs will complain. So we definitely have to include all regions for that :)