Docs on how to use with React

Hi,
The project looks interesting. I think it'd add up if you add an example of how would one use this within React, whether it can be enough to implement the Flux architecture or what else would be needed.
I imagine this in the README and/or an examples folder.

Hi @flesler
Thanks for your interest, there is a JSON editor example where you can see it working:
http://jsbin.com/hugusi/1/edit?js,output
And here the article that talks about how it:
http://arqex.com/991/json-editor-react-immutable-data
Probably I should add it to the readme file.

I think both are too technical and complex. I'm thinking more a code snippet that shows Freezer in action in the simplest case.

Immutable data shines in complex examples, but you are right I need to add some example that people can understand at first sight. I will thing about it. If you have some example in mind just tell me.
Thanks for your feedback.

just wanted to say thanks! this library is insanely great for React, I am surprised it hasn't caught on like wildfire yet, I first tried Baobab but like you didn't like the idea of tying cursors to components, this library really helps with thinking in the "reactive" way with React. cheers~

Hey @hampsterx
Thanks for your kind words, I am glad you liked freezer. Certainly I believe it is a great project that makes working with react really easy, I would love that it was used by many more developers.
But it is difficult to promote freezer, immutable.js is backed by facebook and it is everywhere, and freezer is only used by developers that likes to investigate.
I have thought that if I could make a product that everybody can use ( not only geeks who like immutable structures like us :smile: ) that works with freezer, maybe it can be known by more developers this way. So I have started to work in a customizable form creator that uses freezer:
https://github.com/arqex/react-json
The idea is getting rid of all the code boilerplate needed to create and handle inputs in react, and create them in a declarative way using json.
It would be possible to create customized field types, so other outstanding form components like http://jedwatson.github.io/react-select/ can be used inside react-json.
I hope you like it too :)

re: customizable form creator
Not sure whether you intend this to be used for form builders (ie end users) or for developers as a scaffold for server generated json api/form specification. We are pondering the later case.
In both cases it gets challenging thinking about nested formsets, layout, etc, one earlier attempt at json form builder is https://github.com/jdorn/json-editor, you only need to look at the issue count (~150) to see how the complexity can spiral, however I think delegating the data to widgets avoids at least having to handle low level widget issues but the more it gets used the more people are going to want a consistent interface otherwise it will become spaghetti mess of options to create a form.
Few notes below from a recent poke at the subject, probably not helpful but might give you some ideas, no idea..

api doc generators

apiary, raml, swagger, api blueprint, etc *1
some are yaml based, some markdown, most cater firstly for manually created docs via builder tools * 2

form builders

mostly based around JSON Schema * 3

There appears to be some cross over with JSON Schema support in these
api doc generators *4

*1
Ask HN: What's the best way to write an API spec?
https://news.ycombinator.com/item?id=8912897
There have been an explosion of API specification formats in the last
few years. No clear winner has emerged.
JSON Schema and JSON Hyperschema are JSON-based formats for describing
JSON and REST (hypermedia-driven) APIs. The formats make decent sense
and can be used to generate docs, validators, client libraries, UIs,
and more.http://json-schema.org/
API Blueprint is another emerging format for API description. It's
written in Markdown, so it is very human-readable and -writable. It is
not yet suitable for hypermedia APIs. Like JSON Schema, its tooling
includes validators, client library generators, mock server
generators, docs generators, etc. http://apiblueprint.org/
Swagger is a YAML-based format for specifying JSON APIs. It is meant
to be created using the Swagger UI, rather than handwritten. It
generates pretty docs, client software, etc. but is not suited to
describing hypermedia APIs. http://swagger.io
Slate is an API documentation framework/template, designed to generate
very handsome documentation pages. Its concern is more documentation
than specification, and therefore doesn't concern itself with things
like library or mock generation.https://github.com/tripit/slate
WADL is an API description language which describes API interactions
in an XML format. It resembles WSDL. Not many people use it.
http://en.wikipedia.org/wiki/Web_Application_Description_Lan...
Which of these is the best? Good question. I like JSON Hyperschema,
but I am writing hypermedia APIs and the other formats here are
lacking in their hypermedia support. API Blueprint is a nice format to
write in a text editor and is easily read as-is or rendered from
Markdown; no separate docs generator is necessary.

2

http://apievangelist.com/2014/11/21/there-are-four-api-design-editors-to-choose-from-now/
Apiary.io - Collaborative design, instant API mock, generated
documentation, integrated code samples, debugging and automated
testing using the API Blueprint API definition format.
API Designer - Enables the ability to design APIs in the RAML API
definition format, and mock, preview and save API designs into a
notebook
Swagger Editor - Allows the designing APIs in the Swagger format in
both YAML and JSON, allowing you to import, edit, preview, and export
API design docs.
Restlet Studio - Allows you to create, and load API designs in Swagger
and RAML formats, save, and generate server side scaffolding, and
client side SDKs in multiple languages.

3

http://programmers.stackexchange.com/questions/267309/does-a-form-describing-json-standard-exist
I think the standard you are looking for is JSON Schema. It's not
specific to forms, it's a more general specification for defining what
a particular JSON format looks like (like an XML schema). There are a
few solutions for creating forms with JSON Schema, like
joshfire/jsonform.
https://github.com/Textalk/angular-schema-form
Generate forms from JSON schemas using AngularJS. Schema Form is
inspired by the nice JSON Form library and aims to be roughly
compatible with it, especially its form definition.
http://appliedmathematicsanu.github.io/plexus-form/
A dynamic form component for React using a specification format based
on JSON-Schema.

4

http://support.apiary.io/knowledgebase/articles/147279-json-schema-validation
In API Blueprint you can associate a JSON Schema
(http://json-schema.org) with any JSON-represented resource. If a JSON
Schema is specified, every Content-Type: application/json request to
an endpoint is validated against it. Validation results can be found
under the "Inspector" tab or in endpoint documentation's debugger.
https://github.com/apiaryio/Amanda
Amanda is aiming to be a universal schema validation library.
Currently it supports only the JSON Schema Internet Draft

Hi @hampsterx
I suppose you want to help me with react-json, and that's why you sent me all that info :)
Thanks. From my point of view, all the libraries that are using JSON schema for form definitions are not in the right way. JSON schema is too verbose, you need to write a lot to define your forms, and lacks of some properties to make form creation easy. Lib authors add those missing properties to the schema but, is it a proper JSON schema anymore?
JSON schema was never thought to build forms, so I prefered to define them using a handcrafted form definition, inspired in some way by JSON schema. I think it won't scare developers because it is concise, and it is easy to understand because it talks form language ( fields instead of properties, labels instead of titles... ).
Apart from the ease of use, I think the key part of creating a nice form builder is that it needs to be completely customizable. If somebody has created a awesome file upload library, or a beautiful color picker, why I wouldn't use them inside my form builder? The idea behind react-json is having completely independent form fields that can communicate changes to react-json, so people can create new form fields or use whatever component they would like inside the form.
It is still work in progress, I was looking for a datetime picker to handle Date objects but I couldn't find a nice one, I need to improve CSS customization, lock up the API, add tests, improve validation, add docs... But I think it won't take long to release a beta :)
Anyways, it alredy works nicely https://github.com/arqex/react-json

yeah, fair point. I guess my perspective is more from being able to generate a form definition from the server side which would require a defined set of widgets and consistent structure for form errors, etc, the client can then render the default form or use the definition as a starting point for a partially or completely custom form (ie using the structure merely for reference).
As you say, a work in progress but functional at present, a couple of moderately complex form examples (rather than 2 fields at present) would probably go a long way :)
Regarding the origin of this issue:

.. add an example of how would one use this within React, whether it can be enough to implement the Flux architecture or what else would be needed... I think both are too technical and complex. I'm thinking more a code snippet that shows Freezer in action in the simplest case.

I think your blog post is fantastic at explaining how to use freezer with React. However, the big question that remains is how it plays with Flux which is a larger issue than just freezer.js as IMHO many React developers (myself included) are confused on how immutable libraries fit with Flux, eg

state. Even without immutable library the idea of using state is confusing, should you keep it in the view component, or move to store, should it be in a sub store or a completely different store

store. How to handle multiple instances of same component, singleton passing in id of instance or one store per instance

immutable data. Should private component state live in the data structure.  If an immutable structure can be updated by a view which triggers a top down cascade then does it make sense to have the view update itself if it's only handling internal state. In this case should a child component first call the parent (via say flux-reactions) so it's updating the node a bit higher up.

Some articles of interest:
http://blog.risingstack.com/the-react-js-way-flux-architecture-with-immutable-js/
http://www.thomasboyt.com/2014/09/15/no-fit-state.html
https://groups.google.com/forum/m/#!topic/reactjs/olCk8zdmb5c
http://blog.elsdoerfer.name/2014/12/25/react-js-flux-om-i-am-trying-to-think-it-through/
https://medium.com/@dan_abramov/the-evolution-of-flux-frameworks-6c16ad26bb31
http://omniscientjs.github.io//guides/01-simpler-ui-reasoning-with-unidirectional/
http://blog.siftscience.com/blog/2015/best-practices-for-building-large-react-applications

Me again, more pondering..
I am basically at the point where I have build 2x pieces of isolated functionality on an existing project with React (using freezer.js, no flux, nor dispatcher, view updates data directly). Shortly I will need to make a choice on how the M/C parts (er "flux" aka unidirectional data flow pattern) works before we begin a Single Page App redesign.
In Om/Clojure land the benefits of a global atom containing all the local state is promoted as an effective way to snapshot and debug an app. Eg
-[Simpler UI Reasoning with Unidirectional Dataflow and Immutable Data(]http://omniscientjs.github.io//guides/01-simpler-ui-reasoning-with-unidirectional/)

local state global concerns
better flux dom events

So..

single data structure
stateless components (UI state in global data structure)
top down rendering (props all the way down)

vs the spectrum of flux implementations that range from

UI state in components, app state in stores, to UI state also in stores
views updated from stores
tight coupling (as you say) with the flux framework you choose

I think the confusing bit is the flux frameworks that are using an immutable library for store data (mostly for the benefit of using PureRenderer). Eg Fluxy, NuclearJS for example. I think this is where I ended up going around in a circle with my prior comment :(
Another example is this ticket on flux, flux with immutable data #134

Depending on your needs, you may or may not need flux if you are using global immutable state and > passing things via cursors. You might still want to use flux or events so that the global app state is
mutated in the proper way before the cursor triggers a render, but you might not need as many
listeners on the render side (just passing cursors to props and use efficient shouldComponentUpdate).

So yeah I guess that is my question. A reactive approach handles the rendering strategy but it still leaves some questions about dispatching and managing the global state.

dispatch. Should everything run through a dispatch or only those things that may have dependencies (eg the equivalent of store waitFor)?
should you still use singleton store like objects for the M part? Eg fetching data from remote sources

I really haven't seen any flux, pure dispatcher or otherwise library that is really designed for the global state immutable data pattern you and others are advocating. I am weary of paving my own way here as I am still heavily learning this stuff.
Cheers~

Hey @hampsterx
It is true that is difficult to choose the right tools when there are so many! Well, I have been busy these days and that's why I couldn't reply to your previous message.
What I think it is important from flux is the concept of unidirectional data flow, everything else is really subjective. Using dispatchers, action creators, reducers... it is a matter of a personal taste, so you can choose the implementation that you like the most.
The stores in flux for example, they are meant to update and access to the state of a specific domain, but that does not make them own the data. I mean, the data doesn't need to be in the store, you can use any other library to keep it. That way you can have stores (helpers to get and update the current state) and use immutable structures ( to have the data ).
It is what @gaearon try to explain in https://medium.com/@dan_abramov/the-evolution-of-flux-frameworks-6c16ad26bb31, and the stores not owning the data is one of the strong points of his flux library https://github.com/gaearon/redux IMHO.
That way you can have your data in a single data structure, and the stores can work with its part of the structure. Communication among stores is far more easy this way than using waitFor.

Finally I had time to create a sample of the TodoMVC app that work just with React and Freezer. No frameworks leads to a very clean code:
Todo MVC using Freezer. Code & Demo.
And an article explaining it: How to use React and Freezer together.
Cheers,
Javi


🐛 Bug: content_scripts is injected only when page is refreshed

Bug Report Checklist

[X] I have tried restarting my IDE and the issue persists.
[X] I have pulled the latest main branch of the repository.
[X] I have searched for related issues and found none that matched my issue.

Expected
When the URL is NOT https://github.com/*/*/issues/ then changes to https://github.com/*/*/issues/*, I expect content_scripts to be injected.
Actual
When navigating through github links, and eventually landing on the https://github.com/*/*/issues/* pattern, content_scripts is NOT injected.
content_scripts only runs when https://github.com/*/*/issues/* page is refreshed.
Additional Info
This behavior is consistent in firefox (using main branch) and chrome (using extension from chrome web store)
NOTE: Need to test other situations like navigating from other domains to git

Between #154's title and this issue's body, we have a full bug report! 😄
And it's an interesting one. Thanks for filing! I'm confidently guessing it's because GitHub overrides page navigation to only partially update the page, for performance. Fun benefit of modern web architectures is that the page doesn't go through a whole traditional lifecycle between URL changes.
We'll have to re-run some logic every time the URL changes from a not-issue/PR to an issue/PR.


LWJGL3 switch to fullscreen slow + unpredictable results

Issue details
I'm testing out the LWJGL3 backend to see if the basics are usable yet, and I'm still running into issues with fullscreen mode. Specifically, if the game starts in windowed mode and switches to fullscreen mode, it takes 5+ seconds and also does not position the fullscreen window correctly. The previous LWJGL3 backend I tested was libGDX 1.9.4, and while other game-breaking issues occurred I don't remember this specific issue ever occurring.

Expected result: The window should be all red and cover the entire desktop.
Current result: The window is misplaced and you can see my desktop and taskbar.
Switching between windowed and fullscreen repeatedly sometimes fixes it, but it's not consistent.
Graphics info: Radeon RX 580 + Radeon R9 200
Reproduction steps/code
This is reproducible with a barebones project. In the following code, the game will start with a windowed resolution of 640x480. After about 3 seconds (assuming a 60Hz refresh rate), it will attempt to switch to fullscreen mode using whatever is reported by Gdx.graphics.getDisplayMode().
DesktopLauncher.java:
package com.mygdx.game.desktop;

import com.badlogic.gdx.backends.lwjgl3.Lwjgl3Application;
import com.badlogic.gdx.backends.lwjgl3.Lwjgl3ApplicationConfiguration;
import com.mygdx.game.MyGdxGame;

public class DesktopLauncher {
	public static void main (String[] arg) {
		Lwjgl3ApplicationConfiguration config = new Lwjgl3ApplicationConfiguration();
		config.useVsync(true);
		config.setWindowedMode(640, 480); //start in windowed mode
		new Lwjgl3Application(new MyGdxGame(), config);
	}
}

MyGdxGame.java:
package com.mygdx.game;

import com.badlogic.gdx.ApplicationAdapter;
import com.badlogic.gdx.Gdx;
import com.badlogic.gdx.graphics.GL20;

public class MyGdxGame extends ApplicationAdapter {
	int n = 0;

	@Override
	public void create () {

	}

	@Override
	public void render () {
		Gdx.gl.glClearColor(1, 0, 0, 1);
		Gdx.gl.glClear(GL20.GL_COLOR_BUFFER_BIT);

		n++;

		//after about 3 seconds at 60 FPS, change to fullscreen
		if(n == 180) {
			Gdx.graphics.setFullscreenMode(Gdx.graphics.getDisplayMode());
		}
	}

	@Override
	public void dispose () {

	}
}

Version of LibGDX and/or relevant dependencies
1.9.9
Please select the affected platforms

[ ] Android
[ ] iOS (robovm)
[ ] iOS (MOE)
[ ] HTML/GWT
[X] Windows
[ ] Linux
[ ] MacOS

I can't reproduce this. What is your monitor setup? What GPU driver are you running?

Was running Radeon driver version <IP_ADDRESS> (23.20.150173010 as reported by Windows device manager).
Updated today to the latest version (19.4.1 as reported by Radeon Settings) to see if that would resolve the issue, and it did! Closing as I can no longer reproduce the issue.

Nice :)


:Exampls:Movies -> :Examples:UIExplorer

Motivation (required)
When i run the android example with the command in README.md build failed because of the example app name is changed.
Test Plan (required)
no test needed.

Needs CLA.

We can't look at this PR until the CLA is signed (even for README updates - our tooling will not allow PRs to be merged without a CLA on file).


[MINOR][DOCS][PYTHON] Fix the truncation of API reference in several DataTypes

What changes were proposed in this pull request?
The documentation under https://spark.apache.org/docs/latest/api/python/reference/pyspark.sql/data_types.html chops off the stubs on periods with a subsequent space. This leads to weird stubs when "i.e." is used. This PR escapes the subsequent spaces.

Why are the changes needed?
see above.
Does this PR introduce any user-facing change?
This changes the documentation under https://spark.apache.org/docs/latest/api/python/reference/pyspark.sql/data_types.html
How was this patch tested?
manual build

Can one of the admins verify this patch?


Fix typo in opentelemetry.adoc

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Thanks for the contribution!


Layercontrol bundle is very big

dist/eox-layercontrol.js  954.39 kB │ gzip: 178.57 kB
dist/eox-layercontrol.umd.cjs  690.15 kB │ gzip: 155.66 kB

After #590 stats look like this:
dist/eox-layercontrol.js  547.90 kB │ gzip: 119.85 kB
dist/eox-layercontrol.umd.cjs  421.72 kB │ gzip: 102.76 kB

still a bit bulky. :thinking:
This is the result of npx -w @eox/layercontrol vite-bundle-visualizer -o layercontrol-stats.html: layercontrol-stats.zip

We can see that we bundle all theme providers (bootstrap<n>.js...), while we probably don't want to bundle all of them.

We should probably move jsonform into it's own chunk because in many cases it will not be used by the downstream application.

Possibly we can use https://rollupjs.org/configuration-options/#output-manualchunks, but I found this to conflict with the UMD bundle.


Dependencies for Pillow (Debian stretch)

I was having trouble installing Pillow using buildout. FYI, here I found libs that are required:
https://github.com/python-pillow/docker-images/blob/master/debian-stretch-x86/Dockerfile
apt-get -y
install xvfb sudo
git wget python-numpy python-scipy netpbm
python-qt4 ghostscript libffi-dev libjpeg-turbo-progs
python-setuptools python-virtualenv
python-dev python3-dev cmake
libtiff5-dev libjpeg62-turbo-dev zlib1g-dev
libfreetype6-dev liblcms2-dev libwebp-dev tcl8.6-dev tk8.6-dev
python-tk python3-tk

Sorry I don't understand the issue. Pillow is preinstalled in the image, what's your problem?

Just pointing out, that in case that you plan to upgrade to Debian Stretch, there were issues with Pillow.

Oh thanks, once it hits stable we'll update. I'll keep this open until then.


Connect JID with custom username

Hello,
I have a web app with chat feature. JID are all numeric, to be sure that they are unique.
I want to show an alphabetic username and not show the numeric one in the candy interface.
Can i replace the shown username by it's property, or, are there a connect method to show a new username.
Thx

The "username" displayed, to be accurate, is the room nickname. There is nothing in Candy currently to rewrite this globally, though you may have some luck with handling events. Take a look at the event documentation and try using event handlers to replace it. This will be a development effort.


Improve the text at the top of the home pageFeature/home page text

Received the latest home page text from the product team.

@microsoft-github-policy-service agree

@microsoft-github-policy-service agree


feat(map): Add the ability to map over elements of a collection inside a reactor.

This is the first working version of the map step, making use of iterex.  Works in my local tests with quite complicated async reactors, so I give it the 👍.

looks great :)


No Intellisense with package.json

I have created a package.json file using npm. When opening it in VS Code I don't get any Intellisense whatsoever.
What's wrong?

fix delivered

Excellent :clap:


Adding limit for API connectors

We got an incident and a customer is asking for the limit of API connectors.

Learn Build status updates of commit 92f0f4f:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/active-directory-b2c/service-limits.md
:white_check_mark:Succeeded

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

@kengaderdus,
Can you review the proposed changes?
IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#sign-off


Adding Socket.IO to the Advanced Seed

I don't want to sound as if the Advanced Seed needs anything to be better, because is already a great blessing for us developer.
But, have you considered to include Socket.IO and can that works across multi platforms.
for example, on a CRM app, User A who is running the CRM on an IPhone, updates the "Customer Information" , and at the same time the information is also updated "Socket.IO Real time" for User B   who is running the CRM on a windows 10 device and looking at the same "Customer Information" screen for the same customer.
Obviously if a third person User C comes after the update operation described above, Socket.IO will not be involved with User C, because this third user will update the screen from the database.

Currently, we achieve the above using the Microsoft Stack on the backed and of course Angular 1.5 (could be lower) on the front end.
By using AngularJs $emit in conjunction with the SignalR jQuery plugin proxy.invoke on the front end to send messages to the SignalR server Hub, do some server stuff here if we need to, then the server broadcasts back to the specified clients on the front end (could be a group, one particular user, to others or to all). the signalR jquery plugin is listening to the server, captures the message sent by the server with proxy.on  at that time yields at the angular $emit method, which talks to the angular $on listening somewhere in the angular app. Pretty simple workflow yet powerful.
So i was wondering if your awesome seed that already uses Electron for 3 desktops and NativeScript for mobiles; could make use of Socket.IO to rule the world on all devices from one code base.

Hi @OscarAgreda I'd be open to this. Would you want to try a PR?

Have you all considered PubNub?
https://www.pubnub.com/docs/web-javascript/pubnub-javascript-sdk

You should consider primus instead. This way, everybody will use their favorite websocket technology.

@mrgoos primus is not a bad choice as a client-side library, though it requires us developers to host our own websocket server. In the case of PubNub, they host the server (with cdn) for us.

@khuongduybui - you can host it where you like without being forced to use a freemium service.

@mrgoos uhm, you're right, I can write a PubNub engine for primus if I need to. That's more convenient.

No need to write anything related to PubNub. Just to use primus on the server side.
It's free and works great with ANY websockets technology.

PubNub would be interesting. PR's are definitely welcome!

@NathanWalker - Things like this start getting into the realm of opinion. Would it not be a better approach to not "muddy the waters" and just go the route of the base seed which runs extended forks & docs?
IMO You have crossed from "example of extending the seed" to a repo that people are forking to extend.
Implementing technologies that have numerous options ends up limiting peoples options or making them gut a bunch of stuff thus complicating pulling from upstream. So while the same could be said for NativeScript, it's more like the "Angular" of hybrid mobile.
You quickly end up with something like ...
Let's add socket.io! But what about deepstream.io but I want PubNub .... the list goes on.
Just my $0.02

^^Exactly my thoughts.
This is why I suggested primus so user could use whatever websocket technology that he/she wishes like socket.io, engine.io etc.

I agree with @d3viant0ne here. It's definitely leaning towards a heavy opinion based implementation. May be best to do something like this on a branch perhaps? If anyone wanted to submit a PR, I'd be happy to place on a branch and mention it.

@NathanWalker - I was trying to get Minko to go that route. Pick a few "supported extensions" and then run them as branches thus simplifying the validation process for things landing in #master.
Just rebase them up and the CI takes care of the rest.

Agree 100%.
While for me asp.net core 1.0 is where the sun shines right now, and where i will push entity framework core with LinQ under the webapi controllers. For other people mongo and mongoose make more sense .
So i guess for me the route is signalR 3 (coming soon).
nevertheless all of the server stuff is nothing compared to the awesome angular2 advanced seed. because of the outstanding angular2 best Code Practices.

I'm going to close this, thanks again for the suggestion and kind words @OscarAgreda, just to conclude if a PR were submitted with such functionality, it could be merged to a feature branch for future reference.

What about using Angular Firebase 2
literally can build a chat for no more than 200 lines of code.
I think realtime applications are part of modern apps, and the Angular Firebase 2 is an example of it.
https://github.com/angular/angularfire2


WMCore v2.2.4 Validation

Impact of the new feature
WMCore central services
Is your feature request related to a problem? Please describe.
Monthly task
Describe the solution you'd like
Validate central services in cmsweb-testbed and provide the final feedback by the June deadline.
It also includes the creation of the service release notes and the validation check-list twiki.
Describe alternatives you've considered
None
Additional context
None

This validation is starting with 2.2.4rc6 and the plan is to deploy it to production by the end of the week, Sept 29.
We will likely get yet another WMCore tag, based on https://github.com/dmwm/WMCore/pull/11680 and https://github.com/dmwm/WMCore/pull/11726, but I think it's important to separate tests before 11680 goes in.
Here is a list of DMWM test workflows and how it was injected:
python3 inject-test-wfs.py -u https://cmsweb-testbed.cern.ch -m DMWM -c HG2309_Val -r HG2309_Val -t testbed-vocms0192 -a DMWM_Test -p HG2309_Val_Alanv1

amaltaro_DQMHarvest_RunWhitelist_HG2309_Val_230925_195138_8394
amaltaro_ReReco_failCase_HG2309_Val_230925_195151_6135
amaltaro_ReReco_failCase_Nvidia_HG2309_Val_230925_195148_4344
amaltaro_ReReco_Run2022C_LumiMask_HG2309_Val_230925_195140_4264
amaltaro_ReReco_RunBlockWhite_HG2309_Val_230925_195214_8857
amaltaro_ReReco_RunBlockWhite_Nvidia_HG2309_Val_230925_195227_7289
amaltaro_SC_6Steps_PU_HG2309_Val_230925_195248_4632
amaltaro_SC_EL8_HG2309_Val_230925_195240_8775
amaltaro_SC_EL8_JSON_Nvidia_HG2309_Val_230925_195207_9723
amaltaro_TaskChain_ProdMinBias_HG2309_Val_230925_195218_6036
amaltaro_TaskChain_ProdMinBias_Nvidia_HG2309_Val_230925_195143_1252
amaltaro_TC_6Tasks_PU_HG2309_Val_230925_195159_2952
amaltaro_TC_EL8_HG2309_Val_230925_195230_3323
amaltaro_TC_EL8_JSON_HG2309_Val_230925_195153_3922
amaltaro_TC_LHE_PFN_HG2309_Val_230925_195226_2497
amaltaro_TC_Nano_HG2309_Val_230925_195223_3242
amaltaro_TC_PY3_ProdPsi_HG2309_Val_230925_195234_7311

and the list of integration test workflows is:
python3 inject-test-wfs.py -u https://cmsweb-testbed.cern.ch -m Integration -c HG2309_Val -r HG2309_Val -t testbed-vocms0192 -a Integ_Test -p HG2309_Val_Alanv11

amaltaro_DQMHarvesting_HG2309_Val_230925_200647_6667
amaltaro_DQMHarvesting_MultiRun_HG2309_Val_230925_200648_7103
amaltaro_ReReco_LumiMask_HG2309_Val_230925_200621_6260
amaltaro_ReReco_Parents_HG2309_Val_230925_200639_2694
amaltaro_SC_LHE_Ext_HG2309_Val_230925_200626_7584
amaltaro_SC_LumiMask_Rules_HG2309_Val_230925_200653_4329
amaltaro_SC_MultiPU_HG2309_Val_230925_200649_8490
amaltaro_SC_PY3_PURecyc_HG2309_Val_230925_200655_9463
amaltaro_SC_ReDigi_Harvest_Prod_HG2309_Val_230925_200630_8075
amaltaro_TaskChain_LumiMask_multiRun_HG2309_Val_230925_200618_4428
amaltaro_TaskChain_MC_HG2309_Val_230925_200701_5477
amaltaro_TaskChain_Prod_HG2309_Val_230925_200705_4402
amaltaro_TaskChain_PUMCRecyc_HG2309_Val_230925_200644_9255
amaltaro_TC_Data_Harv_HG2309_Val_230925_200641_4391
amaltaro_TC_Drop_Rules_Ext_HG2309_Val_230925_200622_7183
amaltaro_TC_PY3_Data_LumiList_HG2309_Val_230925_200636_4634
amaltaro_TC_PY3_TTbarPU_HG2309_Val_230925_200711_8572

I also redeployed vocms0192 with a clean <IP_ADDRESS> version.

Thanks for injecting those workflows @amaltaro  We still have not merged #11680. Should I reinject a full scale validation set of workflows with the new tag?

Review of that PR is next in my todo list, but it would be great if you/others could review it as well.
That change is deep down into ReqMgr2, so we would likely have to re-run a good fraction of this validation.
It is important though to identify whether there are any issues with the current release candidate rc6, such that we can properly isolate issues, if needed.

And here is the new set of injected validation workflows:

DMWM

tivanov_DQMHarvest_RunWhitelist_Sept2023_Val_230927_062729_7564
tivanov_ReReco_failCase_Nvidia_Sept2023_Val_230927_062737_6672
tivanov_ReReco_failCase_Sept2023_Val_230927_062735_2317
tivanov_ReReco_Run2022C_LumiMask_Sept2023_Val_230927_062805_2346
tivanov_ReReco_RunBlockWhite_Nvidia_Sept2023_Val_230927_062732_7831
tivanov_ReReco_RunBlockWhite_Sept2023_Val_230927_062731_2603
tivanov_SC_6Steps_PU_Sept2023_Val_230927_062740_1736
tivanov_SC_EL8_JSON_Nvidia_Sept2023_Val_230927_062826_1581
tivanov_SC_EL8_Sept2023_Val_230927_062748_1976
tivanov_TaskChain_ProdMinBias_Nvidia_Sept2023_Val_230927_062822_1203
tivanov_TaskChain_ProdMinBias_Sept2023_Val_230927_062817_8860
tivanov_TC_6Tasks_PU_Sept2023_Val_230927_062757_3458
tivanov_TC_EL8_JSON_Sept2023_Val_230927_062831_9203
tivanov_TC_EL8_Sept2023_Val_230927_062807_196
tivanov_TC_LHE_PFN_Sept2023_Val_230927_062811_6593
tivanov_TC_Nano_Sept2023_Val_230927_062836_662
tivanov_TC_PY3_ProdPsi_Sept2023_Val_230927_062813_883

Integration:

tivanov_DQMHarvesting_MultiRun_Sept2023_Val_230927_062845_311
tivanov_DQMHarvesting_Sept2023_Val_230927_062842_9873
tivanov_ReReco_LumiMask_Sept2023_Val_230927_062846_1760
tivanov_ReReco_Parents_Sept2023_Val_230927_062848_4792
tivanov_SC_LHE_Ext_Sept2023_Val_230927_062850_8302
tivanov_SC_LumiMask_Rules_Sept2023_Val_230927_062857_6008
tivanov_SC_MultiPU_Sept2023_Val_230927_062902_1122
tivanov_SC_PY3_PURecyc_Sept2023_Val_230927_062911_4065
tivanov_SC_ReDigi_Harvest_Prod_Sept2023_Val_230927_062917_3655
tivanov_TaskChain_LumiMask_multiRun_Sept2023_Val_230927_062933_7065
tivanov_TaskChain_MC_Sept2023_Val_230927_062936_4430
tivanov_TaskChain_Prod_Sept2023_Val_230927_062946_6308
tivanov_TaskChain_PUMCRecyc_Sept2023_Val_230927_062941_9734
tivanov_TC_Drop_Rules_Ext_Sept2023_Val_230927_062955_5333
tivanov_TC_PY3_Data_LumiList_Sept2023_Val_230927_062925_4347
tivanov_TC_PY3_TTbarPU_Sept2023_Val_230927_062927_9607

@todor-ivanov as this cycle brings in changes to the workflow spec files, it is especially important to run older workflows to make sure that everything is backward compatible. Please run at least 1 TaskChain and 1 StepChain that dates 2 months back or more.

@amaltaro , what do you mean by:

run at least 1 TaskChain and 1 StepChain that dates 2 months back or more

can you point to a speciffic workflow spec

Any workflow that is sitting in the system in assignment-approved and matches the other 2 criteria that I pointed out.

here are the two old workflows I assigned  for this validation:

https://cmsweb-testbed.cern.ch/reqmgr2/fetch?rid=amaltaro_TC_EL8_July2022_Val_220803_141434_8111
https://cmsweb-testbed.cern.ch/reqmgr2/fetch?rid=amaltaro_SC_MultiPU_July2022_Val_220803_141615_450

Upgrade schedule
* 28th Sept (Thu): Deadline for sending material to be included in the
release; * 28th Sept (Thu): Pre-production deployment, and validation
phase starts; * 2nd Oct (Mon): Deadline for validation results
confirmation; * 3th Oct (Tue): Production deployment. * Validation
results: #11632
Services and release notes<br />

Full release notes:
https://github.com/dmwm/WMCore/releases/tag/2.2.4
WMAgent used: vocms0192.cern.ch (<IP_ADDRESS>)
Central services: WMCore v2.2.4rc6

Problems
| Test | Status | Comments |
Latest changes
| Test | Status | Comments |
Changes from the previous release

Test
Status
Comments

Standard tests

Test
Status
Comments

High Scale Test

MSTransferor: creation of input rules and moving workflows to staging
OK

MSMonitor: monitoring of input rules and moving workflows to staged
OK

MSOutput: creation of output data rules
OK

MSRuleCleaner: cleanup of input and output rules
OK

MSRuleCleaner: archival of workflows
OK

MSPileup: create PU input dataplacement rules for workflows

ACDC with trust flags enabled

ACDC for a Merge job with trust flags enabled

ACDC via script with some override

ACDC of ACDC somehow

Proper archival of rejected workflows

Proper archival of aborted workflows

Proper archival of announced workflows

Run old requests

ACDC old requests

Old request moved from completed to closed-out and announced
OK
---

Old request moved from completed to rejected
OK
---

Old request moved from assignment-approved to rejected
OK
---

Old request moved from running-closed to force-completed

---

Aborting or rejecting an old ReDigi workflow

Aborting or rejecting an old MonteCarlo workflow

Aborting or rejecting an old MonteCarloFromGEN workflow

Request moved from failed to rejected
OK
---

Request moved from new to rejected
OK
---

Request moved from assignment-approved to rejected
OK

Request moved from assigned to aborted
OK

Request moved from staging to aborted

Request moved from staged to aborted

Request moved from acquired to aborted

Request moved from running-open to aborted
OK
---

Request moved from running-closed to aborted
OK
---

Request moved from running-closed to force-complete
OK
---

Request moved from completed to closed-out and announced
OK
---

Request moved from completed to rejected
OK
---

Request moved from closed-out to rejected
OK
---

Request moved from announced to rejected
OK
---

Automatic retry of jobs

Write logs to EOS HTTP
OK

Record unprocessable blocks to LogDB

Record in LogDB reason for workflows going into failed status

Correct EventBased splitting
OK

Correct EventAwareLumiBased splitting
OK

Correct LumiBased splitting
OK

Rucio generic data placement against Disk
OK

Rucio data placement skipped for MSS
OK

ReReco workflow
OK

ReReco+skim workflow

ReReco with IncludeParents
OK

ReReco with Run whitelist
OK

ReReco multicore

ReReco with lumiMask input
OK

ReReco with growing dataset
OK

ReReco with TrustSitelists enabled

ReReco ACDC workflow

ReReco ACDC Merge

ReReco harvesting
OK

StepChain: MC from scratch
OK

StepChain: with input + PU

StepChain: with dup outputModule

StepChain: MC reading LHE files
OK

StepChain: MC extension
OK

StepChain: harvesting

StepChain: EL8 workflows
OK

StepChain: relying on storage.json

StepChain: with multiple PU datasets
OK

StepChain: with PrimaryDataset overwriten
OK

StepChain: with different AcqEra/ProcStr/ProcVer

StepChain: with different CMSSW/ScramArch and PrepID

StepChain: request with lumiMask
OK

StepChain: with IncludeParents

StepChain: with KeepOutput False

StepChain: with TrustPUSitelists enabled
OK

StepChain: multicore/eventStreams

StepChain: ACDC workflow from scratch
OK

StepChain: ACDC workflow with input
OK

StepChain: ACDC merge

DQMHarvest workflow

DQMHarvest real data

DQMHarvest EL8

DQMHarvest run whitelist

DQMHarvest multirun

DQMHarvest with lumiMask input

TaskChain: MC reading LHE files
OK

TaskChain: MC extension
OK

TaskChain: MC recycling

TaskChain: MC from scratch
OK

TaskChain: harvesting

TaskChain: EL8 workflows
OK

TaskChain: relying on storage.json

TaskChain: with dup outputModule

TaskChain: Data workflow

TaskChain: Pileup workflow by recycling

TaskChain: Pileup workflow from scratch

TaskChain: Pileup Pyquen workflow (PrimaryDataset override)

TaskChain: data automatic harvesting

TaskChain: mc automatic harvesting

TaskChain: MaxPSS task based

TaskChain: with KeepOutput False
OK

TaskChain: with transient output modules

TaskChain: Multicore, Memory and EventStreams
OK

TaskChain: different AcqEra/ProcStr/ProcVer/PrepID/CMSSW for each task
OK

TaskChain: with lumiMask input

TaskChain: with IncludeParents

TaskChain: reading input data with events per lumi info

TaskChain: with growing dataset

TaskChain: ACDC workflow
OK

TaskChain: ACDC workflow for a merge task

hi @amaltaro
Let's shoot :)

@amaltaro  deployed the tag in production. Closing the issue here.


Forbole X Airdrop Campaign

Eligible users should be able to claim certain amount of airdrop from Forbole X. Below need to be consider:

DSM airdrop banner
DSM airdrop calculation and result page
DSM airdrop eligibility page
a. Create Desmos Profile
b. Connect profile to wallet account
DSM airdrop claimed result : successful/failure

@kwunyeung Please review


Trying to use for "interactive session" to a piece of equipment

I am trying to use NMSSH to connect to a piece of network gear that supports SSH.
In terminal on OSX:

Jeremys-Mac-Pro:~ jeremylaurenson$ ssh<EMAIL_ADDRESS>Password:
Welcome to Jeremy Laurenson Home SX10 AMER
Cisco Codec Release ce 8.1.0 Final b8c0ca3 2016-04-05
SW Release Date: 2016-04-05
*r Login successful
OK
whom
sales
Roles: ADMIN USER AUDIT
Remote address: <IP_ADDRESS>
OK

However if I try use this code:

[SSHsession initWithHost:@"<IP_ADDRESS>:22" andUsername:@"sales"];
[SSHsession setDelegate:self];
[SSHsession connect];

if (SSHsession.isConnected) {
    NSLog(@"Connected and Authing...");
    if([SSHsession authenticateByPassword:@"colab"])NSLog(@"Auth"); else NSLog(@"No auth");
    error=[SSHsession lastError];
    NSLog(@"%@",[SSHsession lastError]);

    if (SSHsession.isAuthorized) {
        NSLog(@"Authentication succeeded");
    } else NSLog(@"Unath");
} else NSLog(@"Unable to connect!");

I am unable to auth:

2016-04-09 11:05:19.356 PiPMonitor[48121:6150825] NMSSH: libssh2 (v1.6.0) initialized
2016-04-09 11:05:19.356 PiPMonitor[48121:6150825] NMSSH: Start <IP_ADDRESS> resolution
2016-04-09 11:05:19.357 PiPMonitor[48121:6150810] NMSSH: Socket connection to <IP_ADDRESS> on port 22 successful
2016-04-09 11:05:19.985 PiPMonitor[48121:6150825] NMSSH: Remote host banner is SSH-2.0-X
2016-04-09 11:05:19.985 PiPMonitor[48121:6150776] Should connect...
2016-04-09 11:05:19.985 PiPMonitor[48121:6150825] NMSSH: The host's fingerprint is 41:4E:97:A6:DC:92:6A:A5:75:60:5C:1D:02:12:20:23
2016-04-09 11:05:19.985 PiPMonitor[48121:6150776] Connected and Authing...
2016-04-09 11:05:19.985 PiPMonitor[48121:6150825] NMSSH: SSH session started
2016-04-09 11:05:20.006 PiPMonitor[48121:6150825] NMSSH: User auth list: publickey,keyboard-interactive
2016-04-09 11:05:20.006 PiPMonitor[48121:6150776] No auth
2016-04-09 11:05:20.006 PiPMonitor[48121:6150776] Error Domain=libssh2 Code=0 "" UserInfo={NSLocalizedDescription=}
2016-04-09 11:05:24.655 PiPMonitor[48121:6150776] Unath

How should I be using NMSSH in order to connect and then essentially watch the log of the remote box?

I have managed to auth by using [SSHsession authenticateByKeyboardInteractive]; but now need to know how I can proceed with more interactive session.
I'd like to basically get callbacks when data is output from the remote and also be able to send commands.

To open a shell take a look NMSSHChannel and NMSSHChannelDelegate to get the response.

Hello Jeremy!
How were you able to authenticateByKeyboardInteractive? My app crashes before it gives me a chance to enter in the password. It says "Keyboard interactive requires a delegate that responds to session:keyboardInteractiveRequest: or a block!"  Any help will be greatly appreciated!


Staging-Dashboard is connected with Prod's API

Issue Description
The Staging-dashboard is connected with prod's api.
Expected Behavior
It should ideally be connecting with https://staging-api.realdevsquad.com instead of https://api.realdevsquad.com
Current Behavior
As staging-dashboard is connected with prod-api there is no way to test staging-dashboard.
Screenshots

Reproducibility

[x] This issue is reproducible
[ ] This issue is not reproducible

Steps to Reproduce

Visit https://staging-dashboard.realdevsquad.com/
Open the network tab and notice

Severity/Priority

[ ] Critical
[x] High
[ ] Medium
[ ] Low

Additional Information
Basic features can be tested out but one cannot test those features which requires role=super_user

Checklist

[x] I have read and followed the project's code of conduct.
[x] I have searched for similar issues before creating this one.
[x] I have provided all the necessary information to understand and reproduce the issue.
[ ] I am willing to contribute to the resolution of this issue.

found one here: https://github.com/Real-Dev-Squad/website-dashboard/issues/676


fix: reorder arithmetic in SendBuffer::available to prevent overflow

available overflows in send.rs since the add for the offset is done after (I verified this testing local and this fixing it).
superedes https://github.com/ethereum/utp/pull/66 since the review process never got resolved, it has been 2 weeks without a response from pr 66's author, and this overflow bug is an annoying distraction well testing other problems so it would be nice to get it merged.

have you been able to demonstrate that this overflows? #66 description reads "there is no need to panic when more values are pending than the buffer capacity", but due to the check here, that situation should not be possible. in other words, the overflow should not occur because the total size of elements of pending should not exceed the buffer size N.

If you want to reproduce it pull this branch https://github.com/KolbyML/utp/tree/failing-code
cd into the utp-client-interop folder
Test ethereum/utp  send to bittorrent/libutp
Terminal 1
make rcrecv

Terminal 2
make rrsend

After you run this ethereum/utp outputs
1738Z DEBUG uTP{send=10826 recv=10825}: utp_rs::conn: uTP conn starting...
thread 'tokio-runtime-worker' panicked at 'attempt to subtract with overflow', /home/kolby/.cargo/registry/src/index.crates.io-6f17d22bba15001f/utp-rs-0.1.0-alpha.5/src/send.rs:32:9
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
thread 'tokio-runtime-worker' panicked at 'called `Result::unwrap()` on an `Err` value: Custom { kind: Other, error: "RecvError(())" }', src/main.rs:62:47

After I reordered the calculation to N  + offset - pending instead of N  - pending + offset it stopped panicing

You can replicate it with for i in 1..x I know x can be as low as 4k or 3k I was just using 30000 to test with

okay I see what's going on. nice!


UnitTest fail: ApiBackEndOpenCL::SetUp - clCreateKernelsInProgram return 0 kernels

Running the UnitTest project on Windows 10 in Visual Studio 2017 Debug/x64 shows this CL_BUILD_ERROR:
clCreateKernelsInProgram returns 0
It happens in ApiBackEndOpenC::SetUp() while trying to build:
../RadeonRays/src/kernels/CL/intersect_bvh2_skiplinks.cl
Here is the output in the console at the point of failure (all tests up to this point have passed):
[----------] 17 tests from ApiBackendOpenCL
[ RUN      ] ApiBackendOpenCL.DeviceEnum
unknown file: error: Unknown C++ exception thrown in SetUp().
[  FAILED  ] ApiBackendOpenCL.DeviceEnum (1876780 ms)
[ RUN      ] ApiBackendOpenCL.SingleDevice

It's possible I've mis-configured something but I was hoping to get a clean set of unit tests before going any deeper. Any suggestions?
OpenCL can find 3 platforms on my machine in this order:
1. Platform
1.1 Name       : Intel(R) OpenCL
1.2 Vendor     : Intel(R) Corporation
1.3 Version    : OpenCL 2.0
1.4 Profile    : FULL_PROFILE
1.5 Extensions : cl_intel_dx9_media_sharing cl_khr_3d_image_writes cl_khr_byte_addressable_store cl_khr_d3d11_sharing cl_khr_depth_images cl_khr_dx9_media_sharing cl_khr_gl_sharing cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_icd cl_khr_image2d_from_buffer cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_spir
2. Platform
2.1 Name       : NVIDIA CUDA
2.2 Vendor     : NVIDIA Corporation
2.3 Version    : OpenCL 1.2 CUDA 8.0.0
2.4 Profile    : FULL_PROFILE
2.5 Extensions : cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_fp64 cl_khr_byte_addressable_store cl_khr_icd cl_khr_gl_sharing cl_nv_compiler_options cl_nv_device_attribute_query cl_nv_pragma_unroll cl_nv_d3d10_sharing cl_khr_d3d10_sharing cl_nv_d3d11_sharing cl_nv_copy_opts
3. Platform
3.1 Name       : AMD Accelerated Parallel Processing
3.2 Vendor     : Advanced Micro Devices, Inc.
3.3 Version    : OpenCL 2.0 AMD-APP (1800.8)
3.4 Profile    : FULL_PROFILE
3.5 Extensions : cl_khr_icd cl_khr_d3d10_sharing cl_khr_d3d11_sharing cl_khr_dx9_media_sharing cl_amd_event_callback cl_amd_offline_devices
For those platforms it finds 4 devices (2 for Intel, 1 for NVidia and 1 for AMD):
1. Device: Intel(R) HD Graphics 5600
1.1 Hardware version: OpenCL 2.0
1.2 Software version: <IP_ADDRESS>31
1.3 OpenCL C version: OpenCL C 2.0
1.4 Parallel compute units: 24
2. Device: Intel(R) Core(TM) i7-5700HQ CPU @ 2.70GHz
2.1 Hardware version: OpenCL 2.0 (Build 10094)
2.2 Software version: <IP_ADDRESS>94
2.3 OpenCL C version: OpenCL C 2.0
2.4 Parallel compute units: 8
1. Device: GeForce GTX 970M
1.1 Hardware version: OpenCL 1.2 CUDA
1.2 Software version: 378.66
1.3 OpenCL C version: OpenCL C 1.2
1.4 Parallel compute units: 10
1. Device: Intel(R) Core(TM) i7-5700HQ CPU @ 2.70GHz
1.1 Hardware version: OpenCL 1.2 AMD-APP (1800.8)
1.2 Software version: 1800.8 (sse2,avx)
1.3 OpenCL C version: OpenCL C 1.2
1.4 Parallel compute units: 8

i also get a crash when i set like this "api->SetOption("acc.type", "hlbvh");
api->SetOption("bvh.builder", "median");
api->SetOption("bvh.force2level", 0.f);" if set acc.type==other type ,it work well .. the crash happen when executing function SortRadixInt32 ,opencl error code is -4 . can any one tell me why this happen,or any one encounter this issue..my platform is win8 64bit,and
display card info is
"Device Version is OpenCL 1.2 CUDA",
"Device Vender is NVIDIA Corporation",
"Device Type is GPU",
"Device Total Memory is 2048MB",
"Device Max Alloc Memory is 512MB",
"Device Total ComputeUnits Number is 2",
"Max Workitem in each dimension is {1024,0,1024}
IDE is vs2015 ,mode is debug .btw  the project is   \RadeonRays_SDK-master.zip\RadeonRays_SDK-master\Tutorials\Triangle has one geometry .

@Arlorean , it is picking IntelCL plarform to run unit tests. Are you using the latest Intel runtime?

I was at the time I ran the tests although I see there has been an update to <IP_ADDRESS>24 since I did that.

Device: Intel(R) HD Graphics 5600
1.1 Hardware version: OpenCL 2.0
1.2 Software version: <IP_ADDRESS>31
1.3 OpenCL C version: OpenCL C 2.0
1.4 Parallel compute units: 24

I'll see if I can run the tests again with this new driver version in place.

Me too！！！Also in Windows 10 & Visual Studio 2017 Debug/x64.
Get same error.
Who can help us?   T_T


Fix possible spec failure due to array ordering

Introduced in bf66236a6db960c8cab4225182a6bee80697bcf2
Example failure: https://travis-ci.org/ManageIQ/manageiq/jobs/431577113
  1) EvmApplication.queue_status groups zone together
     Failure/Error:
       expect(described_class.queue_status).to eq(
         [
           {
             "Zone"   => zone1.name,
             "Queue"  => "generic",
             "Role"   => nil,
             "method" => "X.x",
             "oldest" => tgt_time.strftime("%Y-%m-%d"),
             "count"  => 1,
           },
       expected: [{"Zone"=>"Zone 9", "Queue"=>"generic", "Role"=>nil, "method"=>"X.x", "oldest"=>"2018-09-21", "count"..."=>"Zone 10", "Queue"=>"generic", "Role"=>nil, "method"=>"X.x", "oldest"=>"2018-09-21", "count"=>1}]
            got: [{"Zone"=>"Zone 10", "Queue"=>"generic", "Role"=>nil, "method"=>"X.x", "oldest"=>"2018-09-21", "count...e"=>"Zone 9", "Queue"=>"generic", "Role"=>nil, "method"=>"X.x", "oldest"=>"2018-09-21", "count"=>1}]
       (compared using ==)
       Diff:
       @@ -1,10 +1,10 @@
       -[{"Zone"=>"Zone 9",
       +[{"Zone"=>"Zone 10",
          "Queue"=>"generic",
          "Role"=>nil,
          "method"=>"X.x",
          "oldest"=>"2018-09-21",
          "count"=>1},
       - {"Zone"=>"Zone 10",
       + {"Zone"=>"Zone 9",
          "Queue"=>"generic",
          "Role"=>nil,
          "method"=>"X.x",
     # ./spec/lib/tasks/evm_application_spec.rb:233:in `block (3 levels) in <top (required)>'

Backport status will be the same as https://github.com/ManageIQ/manageiq/pull/17987

Although, it was introduced by the way strings with numbers are sorted

Ah. I see. Because "Zone 10" is sorted before "Zone 9" ...
Is the array from the method supposed to be sorted? Should that be part of the test? I'm sure we could come up with another way to fix spec so that we continue to test that aspect of the method as well ...

Is the array from the method supposed to be sorted?

I'm not sure, maybe @kbrock knows?

Okay, pushed another commit for ordering that actually makes the spec closer to the original by creating the zones with the names they had before @bdunne 's change. That should make the ordering consistent.

Merged for now since it's the same as it used to be (and removes the random test failures).  It would still be good to know if it's supposed to be sorted or if the string sorting is good enough and we can switch to match_array in the future.

Oh, yeah, forgot to actually link the line that does the sorting. It's definitely supposed to be sorted by zone name.

ugh. late to the game - this looks great

@carbonin We're backporting ManageIQ/manageiq#17987 to Gaprindashvili. Please add gaprindashvili/yes if this can be backported to Gaprindashvili as is.

Turned out this test doesn't exist in Gaprindashvili, removing gaprindashvilil/yes


[Rancher2] quickstart - workload - documentation steps reference things not in UI

Request Summary:

Things on the page direct the user to take actions that are not possible and elements of the page reference things that are named differently in the UI
URL: https://rancher.com/docs/rancher/v2.6/en/quick-start-guide/workload/quickstart-deploy-workload-ingress/
Details:

See screenshots for things that are inaccurate. They're annotated in the images. These are examples on the page, but probably are not the only things that need fixing or adjusting
In the second example (see arrow in image), it includes a reference to Resources>Workloads>Load Balancing and a Load Balancing tab. On the page in question, there is no Resources and there are no tabs

Seconded this, having issues testing workload deployment. What's the actual workflow to deploy a workload and expose it with a lb?

Closed via https://github.com/rancher/docs/pull/3711


gcs/builder: Omit all OP_RETURN scripts from basic filter.

Agree on clarification in the BIP, I actually have a commit that spells it out. Will make PR to the BIP repo for that, thanks for this anyway!


Transform feedback example

This example currently produces:
V_Type: INTERLEAVED_ATTRIBS   V_Length:  2   Max Length:  0
Setup, Update_Program Link failed
ERROR: Could not find transform feedback binding for 'position_out.'
ERROR: Could not find transform feedback binding for 'velocity_out.'

An exception occurred in Main_Loop.Setup.
An exception occurred in Main_Loop.
An exception occurred in Transform_Feedback.
raised GL.ERRORS.INVALID_OPERATION_ERROR : gl-raise_exception_on_opengl_error.adb:10

I have left in debug Put_Line messages which would need to be removed eventually.
I have commented out Get_Transform_Feedback_Varying associated code as this causes an exception on detecting  Max Length:  0 associated with the V_Type attributes. This exception occurs  prior to the Update_Program Link failed message being activated.
I'll add the  C version shortly after confirming that it still works.

I tried removing  the link step removed from Program_From.
The same failure messages occurred.

I think I had the wrapper code working OK on another example.

Can you PR that other example?

Another similar example I checked produces the same problem.
I was looking at a more complex example that uses Transform_Feedback_Varyings  but couldn't complete compilation as GL.Objects.Buffers.Draw_Elements_Base_Vertex  (glDrawElementsBaseVertex ) seems to have disappeared from GL.Objects.Buffers.

I got the more complex example working by commenting out GL.Objects.Buffers.Draw_Elements_Base_Vertex
I don't think I can PR it as it contains quite a lot of new functionality including Assimp and ImageMagick routines.
Also very much a work in progress, so probably a bit of a mess!
This example that I'm trying to implement is from http://ogldev.atspace.co.uk/www/tutorial28/tutorial28.html
The following initialisation code seems to link the varyings OK as it generates the PS_Update_Technique.Init, Update_Program Link for Varyings ok message.
procedure Init (theTechnique : in out Update_Technique) is
      use GL.Objects.Programs;
      use GL.Objects.Shaders;
      use Program_Loader;
      Varyings       : constant String := "Type1,Position1,Velocity1,Age1";
      OK             : Boolean;
   begin
      --  Program_From includes linking
      theTechnique.Update_Program := Program_From
        ((Src ("src/shaders/ps_update.vs", Vertex_Shader),
         Src ("src/shaders/ps_update.gs", Geometry_Shader),
         Src ("src/shaders/ps_update.fs", Fragment_Shader)));

      OK := GL.Objects.Programs.Link_Status (theTechnique.Update_Program);
      if not OK then
         Put_Line ("PS_Update_Technique.Init, Update_Program Link failed");
         Put_Line (GL.Objects.Programs.Info_Log (theTechnique.Update_Program));
      else
         Put_Line ("PS_Update_Technique.Init, Update_Program Link ok");
      end if;

      Use_Program (theTechnique.Update_Program);
      Transform_Feedback_Varyings (theTechnique.Update_Program, Varyings,
                                   Interleaved_Attribs);
      theTechnique.Update_Program.Link;
      OK := GL.Objects.Programs.Link_Status (theTechnique.Update_Program);
      if not OK then
         Put_Line ("PS_Update_Technique.Init, Update_Program Link for Varyings failed");
         Put_Line (GL.Objects.Programs.Info_Log (theTechnique.Update_Program));
      else
         Put_Line ("PS_Update_Technique.Init, Update_Program Link for Varyings ok");
      end if;

      Utilities.Set_Uniform_Location (theTechnique.Update_Program, "gDeltaTimeMillis",
                                      theTechnique.Delta_Millisec_Location);
      Utilities.Set_Uniform_Location (theTechnique.Update_Program, "gRandomTexture",
                                      theTechnique.Random_Texture_Location);
      Utilities.Set_Uniform_Location (theTechnique.Update_Program, "gTime",
                                      theTechnique.Time_Location);
      Utilities.Set_Uniform_Location (theTechnique.Update_Program, "gLauncherLifetime",
                                      theTechnique.Launcher_Lifetime_Location);
      Utilities.Set_Uniform_Location (theTechnique.Update_Program, "gShellLifetime",
                                      theTechnique.Shell_Lifetime_Location);
      Utilities.Set_Uniform_Location (theTechnique.Update_Program, "gSecondaryShellLifetime",
                                      theTechnique.Secondary_Shell_Lifetime_Location);
   exception
      when  others =>
         Put_Line ("An exception occurred in PS_Update_Technique.Init.");
         raise;
   end Init;

Unless you spot a blunder in my Init procedure, perhaps I should write a short varyings test program based on it?

I  added some tests:
      V_Size := Transform_Feedback_Varyings (Update_Program);
      V_Max_Length := Transform_Feedback_Varying_Max_Length (Update_Program);
      V_Type := Transform_Feedback_Buffer_Mode (Update_Program);
      Put_Line ("Transform_Feedback_Buffer_Mode: " & Buffer_Mode'Image (V_Type));
      Put_Line ("Transform_Feedback_Size: " & Size'Image (V_Size));
      Put_Line ("Transform_Feedback_Max_Length: " & Size'Image (V_Max_Length));

This seems to produce correct results, at least for Mode and Size:
Transform_Feedback_Buffer_Mode: INTERLEAVED_ATTRIBS
Transform_Feedback_Size:  4
Transform_Feedback_Max_Length:  10

I also tried Get_Transform_Feedback_Varying but it failed because some parameters need to be declared out.
I'll have a go at fixing this next.
Also, Transform_Feedback_Varyings doesn't seem to correspond to  the glTransformFeedbackVaryings specification.
I'll investigate this later.

I  added some tests:
      V_Size := Transform_Feedback_Varyings (Update_Program);
      V_Max_Length := Transform_Feedback_Varying_Max_Length (Update_Program);
      V_Type := Transform_Feedback_Buffer_Mode (Update_Program);
      Put_Line ("Transform_Feedback_Buffer_Mode: " & Buffer_Mode'Image (V_Type));
      Put_Line ("Transform_Feedback_Size: " & Size'Image (V_Size));
      Put_Line ("Transform_Feedback_Max_Length: " & Size'Image (V_Max_Length));

This seems to produce correct results, at least for Mode and Size:
Transform_Feedback_Buffer_Mode: INTERLEAVED_ATTRIBS
Transform_Feedback_Size:  4
Transform_Feedback_Max_Length:  10

I also tried Get_Transform_Feedback_Varying but it failed because some parameters need to be declared out.
Also, Transform_Feedback_Varyings doesn't seem to correspond to glTransformFeedbackVaryings
I'll have a go at fixing this next.

Changed  Transform_Feedback_Varyings to  Transform_Feedback_Varyings_Size as it doesn't call glTransformFeedbackVaryings  but actually returns Program_Size_Param (Object, Enums.Transform_Feedback_Varyings)

I'll have a look at this somewhen in the next week.

I just realised that these may have been fixed in my transform_feedback_example so I'll check there.

Weird result!
   Varyings       : constant String := "Type1,Position1,Velocity1,Age1";
is accepted.
But if I delete "1" from any of the names, it fails.
For example, Velocity instead of Velocity1 produces:
Update_Program Link for Varyings failed ERROR: Could not find transform feedback binding for 'Velocity.'

I have Get_Transform_Feedback_Varying working.
     GL.Objects.Programs.Get_Transform_Feedback_Varying
        (Update_Program, 0, Buffer_Size, Name_Length, Vertices_Length, V_Type, Varyings_Name);
      Put_Line ("Varying name: " & Varyings_Name (1 .. Integer (Name_Length)));

etc. produces:
Varying name: Type1
Varying name: Position1
Varying name: Velocity1
Varying name: Age1

Although I got the test program to work, changing position_out,velocity_out to position1,velocity1
in the original redbook Feedback project still results in failure:
Setup, Update_Program Link failed
ERROR: Could not find transform feedback binding for 'position1.'
ERROR: Could not find transform feedback binding for 'velocity1.'

Transform feedback example now runs OK after changing varying names to end with "1":
`   Varyings       : constant String := "position1,velocity1";
Yet to test fully.
Cosmetic problem: Space missing in Set_Vertex_Attrib_Pointer error message:
Use the otherSet_Vertex_Attrib_Pointer, Set_Vertex_Integer_Attrib_Pointer ...

I'm having a problem with Get_Transform_Feedback_Varying in that V_Type is returning an invalid value.
Transform_Feedback_Buffer_Mode works correctly so I'm wondering if some sort of conversion is needed in Get_Transform_Feedback_Varying?

Transform feedback example now runs OK.
Ready to merge?


Initial feedback from user testing

Numbering of the questions : either make disabled or have numbering consistent?
Scoring: review all questions and panels names to ensure scoring adds properly (question with images and text was a Y/N question and had scoring added)

Need to add a landing page and have the comments linked to it rather than the survey app itself

Comments: Ashley and Noel to deal with it.

During survey, need to add:

Score: need to add current level (1-4)

Results page

Need to add current level (1-4)
Need to break out the sections on last page
Need to add more information about the final level
Need to be able to save as PDF
Need to be able to save as *CSV/JSON

CSV preferred for proactive disclosure: however needs to have a continuous structure of the data

Can they save their AIA and reload later? Not sure
Add Canada.ca headers and footers + breadcrumbs
Need a list of what they see the tool being able to do. Might be beyond the library itself

Open Gov is working with SCMA for blogging site

Need to break out in manageable issues.

So with some of these changes we'll need to find a different hosting solution then GitHub Pages.
Saving as PDF might be a bit difficult to sort out without a server to handle the processing.
We should be able to do some sort of import/export since SurveyJS already has that functionality.
Export as JSON should be easy, but as CSV might be a bit more work.

OK, i think we can skip PDF for view and aim for the JSON for now.
Regarding the CSV, I'm pretty sure there's some library available from JSON
I'll continue creating the issues but I'll also prioritize them.

Also, just talked to team at Open Government and they're going to be able
to setup a Drupal page on the website so we'll have better hosting options
Le ven. 29 mars 2019 16 h 56, Calvin Rodo<EMAIL_ADDRESS>a
écrit :

So with some of these changes we'll need to find a different hosting
solution then GitHub Pages.
Saving as PDF might be a bit difficult to sort out without a server to
handle the processing.
We should be able to do some sort of import/export since SurveyJS already
has that functionality.
Export as JSON should be easy, but as CSV might be a bit more work.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/canada-ca/aia-eia-js/issues/26#issuecomment-478147100,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABnJ5dZHqjvj1A4ecm6c8ZVdQ_CviVCXks5vbn39gaJpZM4cS_Un
.

Just understood what you meant by hosting, please disregard previous comments about export to PDF 😉

Might be interesting for PDF generation:
https://github.com/MrRio/jsPDF


Maybe need to add more detailed metadata for io.netty:netty-*

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

I'm not sure if https://github.com/oracle/graalvm-reachability-metadata/issues/10 is missing some metadata about Netty.

Describe the solution you'd like
A clear and concise description of what you want to happen.

When I'm using GraalVM 23.0 CE Dev For JDK17 and NBT 0.9.16 to build a GraalVM Native Image related to Netty 4.1.84.Final, https://github.com/apache/shardingsphere/actions/runs/3303870293/jobs/5452309095 's logs have been seen some Netty related logs, I'm not sure if that means I need to add some extra GraalVM reachability metadata.

Warning: Properties file at 'jar:file:///home/runner/.m2/repository/io/netty/netty-codec-http2/4.1.84.Final/netty-codec-http2-4.1.84.Final.jar!/META-INF/native-image/io.netty/codec-http2/native-image.properties' does not match the recommended 'META-INF/native-image/io.netty/netty-codec-http2/native-image.properties' layout.
Warning:  Properties file at 'jar:file:///home/runner/.m2/repository/io/netty/netty-resolver-dns/4.1.84.Final/netty-resolver-dns-4.1.84.Final.jar!/META-INF/native-image/io.netty/resolver-dns/native-image.properties' does not match the recommended 'META-INF/native-image/io.netty/netty-resolver-dns/native-image.properties' layout.
Warning:  Properties file at 'jar:file:///home/runner/.m2/repository/io/netty/netty-transport/4.1.84.Final/netty-transport-4.1.84.Final.jar!/META-INF/native-image/io.netty/transport/native-image.properties' does not match the recommended 'META-INF/native-image/io.netty/netty-transport/native-image.properties' layout.
Warning: Properties file at 'jar:file:///home/runner/.m2/repository/io/netty/netty-common/4.1.84.Final/netty-common-4.1.84.Final.jar!/META-INF/native-image/io.netty/common/native-image.properties' does not match the recommended 'META-INF/native-image/io.netty/netty-common/native-image.properties' layout.
Warning:  Properties file at 'jar:file:///home/runner/.m2/repository/io/netty/netty-codec/4.1.84.Final/netty-codec-4.1.84.Final.jar!/META-INF/native-image/codec-handlers/native-image.properties' does not match the recommended 'META-INF/native-image/io.netty/netty-codec/native-image.properties' layout.
Warning:  Properties file at 'jar:file:///home/runner/.m2/repository/io/netty/netty-handler/4.1.84.Final/netty-handler-4.1.84.Final.jar!/META-INF/native-image/io.netty/handler/native-image.properties' does not match the recommended 'META-INF/native-image/io.netty/netty-handler/native-image.properties' layout.
Warning:  Properties file at 'jar:file:///home/runner/.m2/repository/io/netty/netty-codec-http/4.1.84.Final/netty-codec-http-4.1.84.Final.jar!/META-INF/native-image/io.netty/codec-http/native-image.properties' does not match the recommended 'META-INF/native-image/io.netty/netty-codec-http/native-image.properties' layout.
Warning:  Properties file at 'jar:file:///home/runner/.m2/repository/io/netty/netty-buffer/4.1.84.Final/netty-buffer-4.1.84.Final.jar!/META-INF/native-image/io.netty/buffer/native-image.properties' does not match the recommended 'META-INF/native-image/io.netty/netty-buffer/native-image.properties' layout.
Warning: Could not register io.netty.handler.codec.compression.Lz4FrameDecoder: queryAllPublicMethods for reflection. Reason: java.lang.NoClassDefFoundError: net/jpountz/lz4/LZ4Exception.
Warning: Could not register io.netty.handler.codec.compression.Lz4FrameEncoder: queryAllPublicMethods for reflection. Reason: java.lang.NoClassDefFoundError: net/jpountz/lz4/LZ4Exception.
Warning: Could not register io.netty.handler.codec.marshalling.CompatibleMarshallingDecoder: queryAllPublicMethods for reflection. Reason: java.lang.NoClassDefFoundError: org/jboss/marshalling/ByteInput.
Warning: Could not register io.netty.handler.codec.marshalling.CompatibleMarshallingEncoder: queryAllPublicMethods for reflection. Reason: java.lang.NoClassDefFoundError: org/jboss/marshalling/ByteOutput.
Warning: Could not register io.netty.handler.codec.marshalling.MarshallingDecoder: queryAllPublicMethods for reflection. Reason: java.lang.NoClassDefFoundError: org/jboss/marshalling/ByteInput.
Warning: Could not register io.netty.handler.codec.marshalling.MarshallingEncoder: queryAllPublicMethods for reflection. Reason: java.lang.NoClassDefFoundError: org/jboss/marshalling/ByteOutput.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

I noticed https://github.com/oracle/graalvm-reachability-metadata/tree/master/metadata%2Fio.netty%2Fnetty-handler  and https://github.com/oracle/graalvm-reachability-metadata/tree/master/metadata%2Fio.netty%2Fnetty-codec-http2 , such metadata is actually empty. Should this mean waiting for more metadata to be added?

Additional context
Add any other context or screenshots about the feature request here.

Some early context is at https://github.com/apache/shardingsphere/issues/21347#issuecomment-1287861777 .

I think the empty metadata are ok because those entries are just here to specify the exclude flag on metadata side and should not translate to concrete native-image.properties visible by the native image compiler. Maybe the builtin Netty files in https://github.com/netty/netty should be moved to proper io.netty/netty-* directories to not print those warnings.
Also native-image should not print those warnings on excluded dependencies.
@gradinac Any thoughts?

I think you are right, we should create the recommended metadata directory structure in Netty and move the metadata there, I'll create a Netty PR for that

Looks like nothing needs to be done in this repository, I will close this issue.


Update security policy

Objective
I need to update the policy to put as not maintained the previous versions, versions to add to not supported:

4.1.2
4.2.2

And the new version supported will be:

4.2.3

Done


Improve theme error informations

I couldn't figure out why my local changes to the theme colors definition were not being picked up, so I went to the source.
Turned out my yaml file was using some improper fields.
This PR does:

print a specific warning if in the config color.theme was set to custom and no colors.yaml (or colors.yml) was found
print a specific warning if a color theme was found, but the parsing failed, and why it failed.

Contrary to before, if a color file definition exists and it cannot be parsed we immediately switch to the default (plus a warning). The previous logic was hiding format errors if there were other file extensions to try.
Some examples of the output (before regular lsd output):
if color.y(a)ml is found, but contains wrong data
Warning: cannot load custom theme. Theme file format invalid. date: unknown field `days-old`, expected one of `hour-old`, `day-old`, `older` at line 18 column 3.

if color.theme is set to "custom" in the config file, but no color.y(a)ml is present
Warning: cannot load custom theme. Cannot read theme file. No such file or directory (os error 2).

Sidenotes:

warning output bleed into cargo test. This was already happening with Warning: the 'themes' directory is deprecated, use 'colors.yaml' instead., I made it slightly worse. Perhaps in general warnings should be behind #[cfg(not(test))] or similar, didn't investigate in print_error either, considered it out of scope.
imho we should accept a specific extension for color.yml and the others. Iterating over extensions produces subtle bugs like this and there are no particular benefits (if the documentation tells you to create <filename.yml>, you create <filename.yml> - now you also get a warning)

TODO

[x] Use cargo fmt
[x] Add necessary tests
[ ] Update default config/theme in README (if applicable)
[ ] Update man page at lsd/doc/lsd.md (if applicable)

Is there anything I need to do to improve this PR?


Configure registry to update search indexes independently

part of: https://github.com/pulumi/docs/issues/9829
The docs repo produces a search index with all the pages in the site including registry. In order for us to stop building registry here, we need registry to update its objects independently of docs.

https://github.com/pulumi/registry/pull/3215
https://github.com/pulumi/docs/pull/9928


Fix for nick change during voting.

Fix for this nonsense.
devhost> Hayt: vote yes
devhost> NICK devhost_work
devhost_work> Hayt: vote yes

Closing because of upstream :rage: delete


Add privileged attribute

I need to add 'privileged: true' to securityContext when running my task or workflow. but couldn't find where i can add privileged attiribute. so i add it to BaseSecurityContext
securityContext:
capabilities:
add:
- SYS_ADMIN
privileged: true

@flaviuvadan  Added some tests for this. Check it out😊


Update simple script documentation with Allegra time locking scripts

bors r+

bors r+

bors r+

bors r+

bors r

bors merge


zero_copy accounts are not working properly on aarch64-apple-darwin

Problem
There might be something incompatible in zero_copy with anchor slicing of the account and aarch64-apple-darwin
Repro with this branch cd tests/zero_copy/programs/zero_copy && cargo test-sbf
https://github.com/Arrowana/anchor/commit/64d8ac663da210a6c78d193d99a48b05a89f5c23
---- test_repro_zc_bug stdout ----
thread 'test_repro_zc_bug' panicked at 'from_bytes>TargetAlignmentGreaterAndInputNotAligned', /Users/arowana/.cargo/registry/src/index.crates.io-6f17d22bba15001f/bytemuck-1.14.0/src/internal.rs:32:3
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

caused by
let zc_bug_account = banks_client
        .get_account(zc_bug_pubkey)
        .await
        .unwrap()
        .unwrap();
    let zc_bug = zero_copy::ZcBug::try_deserialize(&mut zc_bug_account.data.as_slice()).unwrap();

The ZcBug account struct itself is aligned, a single u128
https://github.com/Lokathor/bytemuck/blob/ff0b14dae9a4f0650f17c15c16acbd75df1cc4b5/src/internal.rs#L185
is_aligned_to(s.as_ptr() as *const (), align_of::<T>()) is false
Which seems to be caused by try_deserialize_unchecked doing data[8..], the original account data is obviously not aligned on aarch64-apple-darwin due to the 8 bytes discriminator.
Interestingly there has been a PR on this exact line last month, but it looks like it was for an optimization rather than anything else. I tried to build with feature align_offset but it doesn't change the outcome.
Quite an inconvenience that this build fine but blows up later, unclear how it could be fixed.
Workaround

Build client binary with --target x86_64-apple-darwin

Doing this on client instead makes it work, this can be added to the test

    let data = zc_bug_account.data;
    let mut data_without_discriminator = data[8..].to_vec();
    let zc_bug_again: &mut zero_copy::ZcBug =
        bytemuck::from_bytes_mut(&mut data_without_discriminator);
    println!("{}", zc_bug_again.a);

Wow, thanks.
This is really helpful for me.
❤

Could you share an example of the memory address of the account data and the alignment of the zero_copy::ZcBug type when it fails?
Related: https://github.com/coral-xyz/anchor/issues/2614

Running into this issue now, and i'm not able to successfully move forward
using --target x86_64-apple-darwin to fix the issue but it still persists
adding .cargo.config.toml
[build]
target = "x86_64-apple-darwin"

also does not fix the issue, any suggestions?

This is actually not related to M1,2,3 arm chips at all, i tried it on my intel machine and confirmed the same behavior
I'm using Anchor 0.30.0 and solana-program 1.18.11
you can create a new anchor program, and then add this to the program
#[account(zero_copy)]
#[repr(C)]
pub struct ZeroCopyWithError {
    pub var1: u64,  // 8 bytes
    pub var2: u128, // 16 bytes
}

You will encounter this error:
cannot transmute between types of different sizes, or dependently-sized types
source type: `ZeroCopyWithError` (256 bits)
target type: `TypeWithoutPadding` (192 bits)rustc[Click for full compiler diagnostic](rust-analyzer-diagnostics-view:/diagnostic%20message%20%5B0%5D?0#file%3A%2F%2F%2FUsers%2Fdiyahircampos%2FFiles%2FGithub%2Ftic-tac-toe%2Fprograms%2Ftic-tac-toe%2Fsrc%2Flib.rs)


AWS Env variables not loaded at build time

Environment
I'm developing a Nuxt App that uses the Sentry Vite Plugin. I use AWS and Github Actions for the CI/CD.
On a Nuxt project, we don't have a vite.config.js file since all the configurations are inside a nuxt.config.ts
You can check it out :
Steps to Reproduce
Package.json
{
  "name": "nuxt-app",
  "private": true,
  "engines": {
    "node": "18",
    "npm": "9"
  },
  "scripts": {
    "build": "nuxt build",
    "dev": "nuxt dev",
    "start": "nuxt start",
    "generate": "nuxt generate",
    "preview": "nuxt preview",
    "postinstall": "nuxt prepare",
    "test": "jest",
    "test:coverage": "jest --coverage --detectOpenHandles",
    "test:debug": "jest --debug",
    "test:watch": "npm run test -- --watch",
    "translate": "./.sh/update_translations.sh"
  },
  "devDependencies": {
    "@nuxtjs/eslint-config-typescript": "^12.0.0",
    "@nuxtjs/eslint-module": "^4.0.2",
    "@nuxtjs/tailwindcss": "^6.6.8",
    "@pinia-plugin-persistedstate/nuxt": "^1.1.1",
    "@pinia/testing": "^0.1.2",
    "@types/jest": "^29.5.2",
    "@types/lodash": "^4.14.195",
    "@types/luxon": "^3.3.0",
    "@types/node": "^18",
    "@vue-leaflet/vue-leaflet": "^0.10.1",
    "@vue/test-utils": "^2.3.2",
    "@vue/vue3-jest": "^29.2.5",
    "autoprefixer": "^10.4.14",
    "babel-jest": "^29.5.0",
    "eslint": "^8.40.0",
    "eslint-config-airbnb-base": "^15.0.0",
    "eslint-config-prettier": "^8.8.0",
    "eslint-plugin-import": "^2.27.5",
    "eslint-plugin-nuxt": "^4.0.0",
    "eslint-plugin-prettier": "^4.2.1",
    "eslint-plugin-vue": "^9.11.1",
    "jest": "^29.6.2",
    "jest-canvas-mock": "^2.5.0",
    "jest-transform-stub": "^2.0.0",
    "lodash": "^4.17.21",
    "nuxt": "^3.7.3",
    "postcss": "^8.4.23",
    "prettier": "^2.8.8",
    "sass-loader": "^13.2.2",
    "ts-jest": "^29.1.0",
    "typescript": "^5.0.4",
    "vue-tsc": "^1.8.8"
  },
  "dependencies": {
    "@babel/preset-env": "^7.22.5",
    "@pinia/nuxt": "^0.4.11",
    "@sentry/browser": "^7.59.3",
    "@sentry/vite-plugin": "^2.7.0",
    "@sentry/vue": "^7.66.0",
    "jest-environment-jsdom": "^29.5.0",
    "sass": "^1.62.1",
  },
  "overrides": {
    "vue": "latest",
    "@babel/core": "7.17.9",
    "@babel/generator": "7.17.9",
    "istanbul-lib-instrument": "5.2.0"
  }
}

nuxt.config.ts
import { sentryVitePlugin } from '@sentry/vite-plugin'

export default defineNuxtConfig({
    ssr: false,
    app: {
        head: {
            title: 'XX XX',
            meta: [
                { charset: 'utf-8' },
                {
                    name: 'viewport',
                    content: 'width=device-width, initial-scale=1'
                },
                { hid: 'description', name: 'description', content: '' }
            ],
            link: [{ rel: 'icon', type: 'image/png', href: '/favicon.svg' }]
        }
    },
    css: [
        '~/assets/styles/main.scss',
    ],
    postcss: {
        plugins: {
            'postcss-import': {},
            'tailwindcss/nesting': 'postcss-nesting',
            tailwindcss: {},
            autoprefixer: {}
        }
    },
    typescript: {
        typeCheck: true
    },
    runtimeConfig: {
        SENTRY_AUTH_TOKEN: process.env.NUXT_SENTRY_AUTH_TOKEN,
        public: {
            PUBLIC_KEY_CAPTCHA: process.env.NUXT_PUBLIC_PUBLIC_KEY_CAPTCHA,
            CAPTCHA_ENABLED: process.env.NUXT_PUBLIC_CAPTCHA_ENABLED,
            NODE_ENV: process.env.NUXT_PUBLIC_NODE_ENV,
            SENTRY_DSN: process.env.NUXT_PUBLIC_SENTRY_DSN,
            SENTRY_AUTH_TOKEN: process.env.NUXT_PUBLIC_SENTRY_AUTH_TOKEN // I tried on server and public sides
        }
    },
    sourcemap: true,
    vite: { // Here are located the vite.config.js lines
        optimizeDeps: {
            include: ['lottie-web', 'vue3-lottie'],
            exclude: ['fsevents']
        },
        build: {
            sourcemap: true
        },
        plugins: [
            sentryVitePlugin({
                authToken: process.env.NUXT_SENTRY_AUTH_TOKEN,
                org: 'X',
                project: 'X'
            })
        ]
    }
})

Expected Result
Sentry well configured
Actual Result
The Sentry Vite plugin doesn't read my NUXT_SENTRY_AUTH_TOKEN env variable. So I get these errors on build :
[sentry-vite-plugin] Warning: No auth token provided. Will not create release. Please set the authToken option. You can find information on how to generate a Sentry auth token here: https://docs.sentry.io/api/auth/
[sentry-vite-plugin] Warning: No auth token provided. Will not upload source maps. Please set the authToken option. You can find information on how to generate a Sentry auth token here: https://docs.sentry.io/api/auth/

I have no problem on a local build (with a .env file) it reads my NUXT_SENTRY_AUTH_TOKEN well but not on CI/CD build time although I can display the token on a page after the build (to check if it's not empty or something).
So this is a problem of runtimeConfig but I don't know how to fix it.
My other env variables are perfectly read. The Sentry Auth Token env variable is the only variable that is not working.
Any ideas ?

The plugin doesn't read NUXT_SENTRY_AUTH_TOKEN but SENTRY_AUTH_TOKEN. Can you try that instead? Thanks!

Hello! Thx for the reply
So I tried to rename my env variable to SENTRY_AUTH_TOKEN but it still didn't work
I still got the errors in the build logs

Did you provide the auth token at build time? I am like 99.99999% sure this is not an issue in the plugin but rather in your setup because the logic is stupidly simple:
https://github.com/getsentry/sentry-javascript-bundler-plugins/blob/58271f1af2ade6b3e64d393d70376ae53bc5bd2f/packages/bundler-plugin-core/src/options-mapping.ts#L13


include options to remove -e backup files in release.sh

@dmitrig01

let's rm -f so if they don't exist for wahtever reason, it doesn't fail

you can also rm multiple things in one statmeent :-)
rm -f bower.json-e  CHANGELOG.md-e package.json-e plugin.xml-e src/0_config.js-e test/web-config.js-e

ha, I learned something new :)

both done!


Add new methods and options to ArchethicRPCClient and TransactionBuilder

This pull request adds new functionality to the ArchethicRPCClient and TransactionBuilder classes.
ArchethicRPCClient

Added a new method refreshCurrentAccount() to refresh the current account.

TransactionBuilder

Added a new option generateEncryptedSeedSC to allow the generation of an encrypted seed for smart contracts.

Added a new method setGenerateEncryptedSeedSC() to set the generateEncryptedSeedSC option.

Fixes #160

Thank you, I took the liberty to forward it to the TransactionRPC struct used by the send_transaction function.


whatever ⚫ means, it's unreadable

High Wood Ninja spawn has black_circle as part of its preemptive (blind I guess?)
maybe we can use :blind_orb: instead

We will use this


chore(NX-3492): change support links from ZD to Salesforce

The type of this PR is: Chore

This PR solves NX-3492
Description

Changes Support links from Zendesk to Salesforce.

2 of the links added in this PR are not working as expected. These URLs are matching the ones we have in the spreadsheet. I'll share this on #zendesk-sf-migration channel

https://support.artsy.net/s/article/What-Counts-as-an-Artworks-Proof-of-Authenticity
https://support.artsy.net/s/article/How-are-taxes-customs-VAT-and-import-fees-handled-on-works-listed-with-secure-checkout
https://support.artsy.net/s/article/How-do-I-place-a-bid-in-an-auction
https://support.artsy.net/s/topic/0TO3b000000UesxGAC/sell
https://support.artsy.net/s/article/Im-an-artist-Can-I-submit-my-own-work-to-sell
https://support.artsy.net/s/topic/s/topic/0TO3b000000UevEGAS/contacting-a-gallery ❌
https://support.artsy.net/s/article/How-to-Complete-Identity-Verification
https://support.artsy.net/s/topic/s/topic/0TO3b000000UevOGAS/sell-with-artsy ❌
https://support.artsy.net/s/article/The-Artsy-Guarantee
https://support.artsy.net/s/topic/0TO3b000000UessGAC/buy
https://support.artsy.net/s/article/The-Complete-Guide-to-Auctions-on-Artsy

Thanks @lidimayra, changed the broken links in https://github.com/artsy/force/pull/12274/commits/cb0c350f9ad46aed6071cfc3e6d80d2b441823d1


About Pre-trained models

Hello！Can I directly use the pre training parameters of resnet50 instead of the pre training parameters you provide?

Hello！Can I directly use the pre training parameters of resnet50 instead of the pre training parameters you provide?

The same ask

@duduzai2019 did you find the solution?


file details

Thank you for sharing these data.
I have a few questions regarding the details:

Could you kindly clarify on what does the first line number represent in the 'graph*.txt' file?

5 1 2
2 3
2 3
3 2
4 3
4 1

As per my understanding, 'main.json' appears to be similar to 'train.json' and 'test.json' in the context of supervised fine-tuning setting?

Q1: Generally, the first number means the number of nodes and the the second number means the number of edges. This example seems to belong to the connectivity task, which is slightly different from other data: here the third number means the number of queries for each type (i.e. connected and not connected). The number pairs following the edges are the queries.
Q2: Main splits are split into train splits and test splits.


[DOCS] add additional dev/contributor documentation about running tests

Which page or section is this issue related to?
There is no clear instruction on running tests.
N.A.

@davidberenstein1957 I would like to work on this task. Can I get started?

@hjain5164 You can pick this up:) Do you need any help to get started?


.net core error

Will the author support the .net core in the future, I use the .net core project and find that there is no msg:Could not load file or assembly 'System.Drawing.Common, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51 '.
I looked for the entire project ImageDefinition, TextStyle and AciColor used the System.Drawing package, and I found no such packages in .net core2.2, so when I was new DxfDocument, I reported the above error.
Or, after I deleted these three classes and used them in the .net core, would it be risky?

At the moment no, you will see a Mono release before a .net core; what happens in the future I don't know I cannot make promises. Check this and this it might help you.
You cannot just delete classes without raising problems.


added template sag-mws-applatform and sag-designer-applatform

I have added below templates for review
template sag-mws-applatform which will install Application Platform on MWS
template sag-designer-applatform which will install Application Platform perspective on designer

Please see my inline comments for the changed files.
You need to add the README.md for designer template
And please update the sag-is-applatform template as well
Thanks
Sergei

I have added the README.md file for designer template and also updated the sag-is-appplatform template

Change in the spelling of template folder. sag-is-appplatform to sag-is-applatform


经常崩溃

有时同时开启两个项目，vscoode显示oom崩溃，无反应，或者在ng build -prod进行一半时，vscode崩溃重启

解决了吗？ 我是win7，ram 8g，只开一个项目莫名崩溃

还没有解决
------------------ 原始邮件 ------------------
发件人:                                                                                "microsoft/vscode"                                                                                @.>;
发送时间: 2022年3月31日(星期四) 下午4:22
@.>;
<EMAIL_ADDRESS>主题: Re: [microsoft/vscode] 经常崩溃 (Issue #146235)
解决了吗？ 我是win7，ram 8g，只开一个项目莫名崩溃
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

Hey @Tyriar, this issue might need further attention.
@Juatina629, you can help us out by closing this issue if the problem no longer exists, or adding more information.

This isn't enough info to investigate unfortunately, see https://github.com/microsoft/vscode/wiki/Native-Crash-Issues for reporting actionable crash issues.


[FEATURE] Add requires on multiple argument functions to ensure proper cardinal compatibility

To day, if we call pow(x,y) with x and y being of different cardinals, the error message is atrocious.
I sugegst we :

[ ] Write a has_compatible_cardinals<Ts...> helper that checks that all cardinals are the same for non-scalar types in Ts...
[ ] Add a rersuires on this in all 2+ parametrs functions using the new dispatch system

For reference
code
auto x = eve::pow( wide<float,fixed<4>>{}, wide<float,fixed<8>>{});

clang output :
<source>:8:12: error: no matching function for call to object of type 'const detail::callable_object<tag::pow_>'
  auto x = eve::pow( wide<float,fixed<4>>{}, wide<float,fixed<8>>{});
           ^~~~~~~~
/home/falcou/dev/eve/include/eve/module/math/regular/pow.hpp:95:1: note: candidate template ignored: constraints not satisfied [with Args = <eve::wide<float, eve::fixed<4>>, eve::wide<float, eve::fixed<8>>>]
EVE_MAKE_CALLABLE(pow_, pow);
^
/home/falcou/dev/eve/include/eve/detail/overload.hpp:137:3: note: expanded from macro 'EVE_MAKE_CALLABLE'
  EVE_IMPLEMENT_CALLABLE(TAG,NAME)                                                                  \
  ^
/home/falcou/dev/eve/include/eve/detail/overload.hpp:127:3: note: expanded from macro 'EVE_IMPLEMENT_CALLABLE'
  EVE_DECLARE_CALLABLE(TAG,NAME)                                                                    \
  ^
/home/falcou/dev/eve/include/eve/detail/overload.hpp:79:48: note: expanded from macro 'EVE_DECLARE_CALLABLE'
      EVE_FORCEINLINE constexpr decltype(auto) operator()(Args &&... args) const noexcept          \
                                               ^
/home/falcou/dev/eve/include/eve/module/math/regular/pow.hpp:95:1: note: because 'tag_dispatchable<eve::detail::callable_object<eve::tag::pow_, type-parameter-0-0>::tag_type, eve::wide<float, eve::fixed<4> >, eve::wide<float, eve::fixed<8> > >' evaluated to false
/home/falcou/dev/eve/include/eve/detail/overload.hpp:137:3: note: expanded from macro 'EVE_MAKE_CALLABLE'
  EVE_IMPLEMENT_CALLABLE(TAG,NAME)                                                                  \
  ^
/home/falcou/dev/eve/include/eve/detail/overload.hpp:127:3: note: expanded from macro 'EVE_IMPLEMENT_CALLABLE'
  EVE_DECLARE_CALLABLE(TAG,NAME)                                                                    \
  ^
/home/falcou/dev/eve/include/eve/detail/overload.hpp:76:21: note: expanded from macro 'EVE_DECLARE_CALLABLE'
      requires  (   tag_dispatchable<tag_type,Args...>                                             \
                    ^
/home/falcou/dev/eve/include/eve/detail/overload.hpp:227:9: note: because 'tagged_dispatch(tag, static_cast<decltype(args) &&>(args)...)' would be invalid: use of undeclared identifier 'tagged_dispatch'
      { tagged_dispatch(tag, EVE_FWD(args)...) };
        ^
/home/falcou/dev/eve/include/eve/module/math/regular/pow.hpp:95:1: note: and 'supports_pow_<eve::wide<float, eve::fixed<4> >, eve::wide<float, eve::fixed<8> > >' evaluated to false
EVE_MAKE_CALLABLE(pow_, pow);
^
/home/falcou/dev/eve/include/eve/detail/overload.hpp:137:3: note: expanded from macro 'EVE_MAKE_CALLABLE'
  EVE_IMPLEMENT_CALLABLE(TAG,NAME)                                                                  \
  ^
/home/falcou/dev/eve/include/eve/detail/overload.hpp:127:3: note: expanded from macro 'EVE_IMPLEMENT_CALLABLE'
  EVE_DECLARE_CALLABLE(TAG,NAME)                                                                    \
  ^
/home/falcou/dev/eve/include/eve/detail/overload.hpp:77:21: note: expanded from macro 'EVE_DECLARE_CALLABLE'
                ||  supports_ ## TAG<Args...>                                                      \
                    ^
<scratch space>:277:1: note: expanded from here
supports_pow_
^
/home/falcou/dev/eve/include/eve/module/math/regular/pow.hpp:95:19: note: because 'pow_(eve::detail::delay_t{}, eve::current_api, static_cast<decltype(args) &&>(args)...)' would be invalid: no matching function for call to 'pow_'
EVE_MAKE_CALLABLE(pow_, pow);
                  ^
1 error generated.
Compiler returned: 1

we expect to get a simple
no such function eve::pow(wide<float,fixed<4>,wide<float,fixed<8>)

Sounds good for me

Completed and also added on top of tuple callables


Library: Fix: RP2040 xtal and test_en connections in pinmap

Library: Fix: RP2040 xtal and test_en connections in pinmap
Description
Found out the hard(ware) way :smiling_face_with_tear:
Checklist
Please read and execute the following:

[ ] My code follows the coding guidelines of this project
[ ] My PR title is following the contribution guidelines
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation (if applicable)
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works (if applicable)
[ ] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules
[ ] I ran Black to format my code

Code of Conduct
By submitting this issue, you agree to follow our Code of Conduct:

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

@ruben-iteng Thanks for the PR! If you're sure about this, I'll mash that merge. Any reason it's still in draft state


Random clippy changes

To check if clippy pedantic rules from #666 are helpful
I only changes clippy rules, that were easy to change(some are quite problematic)

superseded by #695


soc/riscv/sifive-freedom/fe310: use correct SYS_CLOCK_HW_CYCLES_PER_SEC

This PR introduces several changes that allow the SYS_CLOCK_HW_CYCLES_PER_SEC value to revert back to its correct value, as reported by #44432 and #44856, while making tests still pass on the HiFive1 board. The previously-failing tests were:

tests/kernel/sleep/kernel.common.timing
tests/kernel/tickless/tickless_concept/kernel.tickless.concept
tests/kernel/workq/work_queue/kernel.workqueue

The first change is related to the simulation itself and reduces the CLINT frequency in Renode model down to 16 MHz to correspond with the oscillator frequency given by the FE310's datasheet and the HiFive1 board schematic. This fixes the first two tests.
The second change is reducing the MIN_DELAY define to 100. This causes the RISC-V machine timer driver to update the mtimecmp register more often, which in turn addresses the work_queue/kernel.workqueue problem with work items finishing prematurely, causing the above-mentioned test to fail.

I've recreated this behavior locally, it seems that I've been using the docker image wrongly. Bumping Renode version solved the issue for me and all tests are passing with Renode 1.13.0.
I've created https://github.com/zephyrproject-rtos/docker-image/pull/102 to address this problem and bump Renode version.

I've created zephyrproject-rtos/docker-image#102 to address this problem and bump Renode version.

I'll re-run the pipeline as soon as #45668 (which bumps the container used by the CI) is merged.

@edersondisouza Hi, all tests are now passing. Could you reapprove this PR?


Generate {hot: module.hot} for a 'module' local

As of RC4, Webpack 2 disallows use of a bare module identifier in ES2015 modules.
This fixes the following error with the common React HMRE setup when your components are ES2015 module syntax:
module is not allowed in EcmaScript module: This module was detected as EcmaScript module (import or export syntax was used). In such a module using 'module' is not allowed.
Are there any existing transforms which use module properties other than hot?

See https://github.com/webpack/webpack/issues/3917 for discussion on the Webpack side of things.

Are there any existing transforms which use module properties other than hot?

Maybe module.id?

This is no longer needed as of Webpack 2 RC5