Missing SameSite header in CDN

Describe the bug
All the modern browsers have started to enforce the SameSite header for security reasons. Previously, None used to be the default value, but recent browser versions made Lax the default value to have reasonably robust defense against some classes of cross-site request forgery (CSRF) attacks.
FCC doesn't specify the SameSite header and the current browsers default to None
but in the near future this will change. Browsers in the near future will default to Lax, so to ensure the expected behaviour, we need to add the SameSite header with the Secure header.
To Reproduce
Steps to reproduce the behavior:

Open any page or resurce that uses the CDN
Open the console (in Chrome) and see the warning

Expected behavior
The expected behaviour is to see no warning and the CDN should work as normal.
Screenshots
Here's a screenshot of the warning ->

Desktop (please complete the following information):

OS: Windows 10 (64 Bit)
Browser: Chrome
Version: 83.0.4103.61 (Official Build) (64-bit)

I have made a PR that fixes this issue, it can found here -
https://github.com/freeCodeCamp/cdn/pull/51

I can confirm the presence of the bug.

OS: Windows 10 (64 Bit)
Browser: Chrome
Version: 83.0.4103.97 (Official Build) (64-bit)

https://blog.chromium.org/2020/05/resuming-samesite-cookie-changes-in-july.html?m=1 Google's planning on rolling this out by the 14th of July, so we have a deadline.

Is there a quick way of auditing the site to see if any other resources need this header specifying?

Hi @Twaha-Rahman
Thanks a lot for the report.
Please note while we are scincerely grateful for the report and the PR. We highly recommend reporting security issues to our dedicated email for these. You would have been presented with this template when opening an issue:

This gives us a chance to brace ourselves quickly :)
I have left review comments on the PR.

Is there a quick way of auditing the site to see if any other resources need this header specifying?

Yes, we would have public deploy-previews. It would not be matched to the domain though.

@raisedadead I've updated the PR accordingly!

@Twaha-Rahman @nhcarrigan which pages did you see the warning on?

I get the warning on all of the /news pages, it seems.

@Twaha-Rahman @nhcarrigan which pages did you see the warning on?

I can see the warning on the Test Suite.

The issue seems to be resolved.
I would appreciate it if you could test, confirm, and close this issue accordingly. Thank you.

Hey @ahmadabdolsaheb,
Is the fix deployed on the live site? Because I am still seeing the error on the /news page.
Or was there somewhere else I should test the fix?

@nhcarrigan, thanks for looking into this.
There is similar issue with http://runkit.com/ which is a script injected in ghost.
It seems the issue with the freecodecamp.dev cookie has been resolved. can you confirm that?

On the dev/news page, I get the runkit cookie but also show a freecodecamp.org cookie.

I see, how about freecodecamp.org/news?

That one appears to have been fixed now.

It is still there on /news

Shouldn't the warning appear in any site that uses the CDN? From my understanding, the CDN is missing header which show the warning. So, any FCC site (even the Test Suite) will show the warning cause it uses the CDN


Improve menu

This PR fixes a couple of minor UI & UX issues:

Badges are centered now (before, some browsers had big issues). Did not test on Windows or Linux, though!
When hovering the badge, a title text appears to explain what the badge is trying to say (e.g. "Difficulty: Intermediate").
Renamed "Misc" category to "General usage" – looks and feels better than just "Misc".
Moved "Contribute on GitHub" below "Introduction" (fixes #142).

I'd also put "Cache then network" into the "General usage" category. Let me know if I should push another commit for that.

I'd also put "Cache then network" into the "General usage" category. Let me know if I should push another commit for that.

Let's leave it in the Performance category for now.


Implement soft recursion limit

To prevent apps hanging and crashing with infinite recursion, check
the limit manually and throw custom Error when it is reached. Error provides
stack of last symbols checked to track recursion reason faster.

Updated with formattedWrite, now trying to get Travis confirmation..

Green, I'll consider @mathias-lang-sociomantic last comment as LGTM

Late Good To Me


Patch version number is missing in Ubuntu package file name

Patch version number is missing in Ubuntu package file name. For example https://packagecloud.io/linz/test/packages/ubuntu/bionic/linz-bde-schema_1.12-start-linz~bionic_all.deb

That's a tag which should teoretically NOT produce an upload. The problem is that the code that SKIPS the upload will always be committed after the tagged commit, which results in such upload. I think we should just manually delete those packages from packagecloud and be done. I'll proceed in this way.

I see the package was removed, so I'm closing this.


test: expand apphash test with all state machine msgs

Overview
Resolves #3540 & Resolves #3626
Expected AppHash generated from https://github.com/celestiaorg/celestia-app/pull/3665

since we need to add to this test over time, it might be worthwhile to add some docs for the standard way of adding to it. For example, if we add a new message type, how can we add it here and create a new app hash? what do we need to do when we get v3?

Good idea! Exporting this into an issue.


Changing DC?

In order to download something from telegram servers, I sometimes need to change datacenter (error "mtproto RPC error: 303 FILE_MIGRATE_2 " if you are interested why). How can I do it with your lib? As far as I understand I have no option to get "dcOptions" field from Session struct which contains all the information about available DCs, because it is a private field and apiDcOption(...) is private too.
Can you please provide any way either to get "dcOptions" or to reconnect to the specific DC? The second way is a little bit harder because it will require to first call AuthExportAuthorization, reconnect to new dc and then call AuthImportAuthorization.
P.S. Thanks for the project and really great support. I can do a merge request if you are busy

Can you try this commit? it is in migrate_session branch

It looks like that this branch works. Can you merge it into master?


Can't Debug Tests: '${MODULES_USE_COMPAT_VERSION:-0}'

Environment data

VS Code version: XXX

Extension version (available under the Extensions sidebar):

OS and version: Fedora 30

Python version (& distribution if applicable, e.g. Anaconda): Various

Type of virtual environment used (N/A | venv | virtualenv | conda | ...): XXX

Relevant/affected Python packages and their versions: XXX

Jedi or Language Server? (i.e. what is "python.jediEnabled" set to; more info #3977): XXX

Expected behaviour
A debugging session would open for the given test(s)
Actual behaviour
This popup appears:

Steps to reproduce:

Click on the debug icon , either for individual tests or for all the tests

Logs
No relevant logs found in output.

Seeing similar error when clicking on Debug Test adornment above test method. Run Test adornment works fine. Noted similar issue in the go project: https://github.com/microsoft/vscode-go/issues/2831

Version: 1.39.0
Commit: 9df03c6d6ce97c6645c5846f6dfa2a6a7d276515
Date: 2019-10-09T06:57:43.593Z
Electron: 4.2.10
Chrome: 69.0.3497.128
Node.js: 10.11.0
V8: 6.9.427.31-electron.0
OS: Darwin x64 18.7.0

@karthiknadig there's an upstream issue https://github.com/microsoft/vscode/issues/82611
Most likely caused by something in VSC

Looks like this has to be addressed in VS Code. See this comment for potential workaround: https://github.com/microsoft/vscode/issues/82611#issuecomment-542765582


When the select2-container is off the visible area, wrong options are selected

Hi,
When I scroll the page and the select2-container is off the browser visible area, wrong options are selected when clicked.
It's easier to reproduce when we have a select2-results with high max-height or with max-height: none;
It's almost impossible to select the options that are in the bottom of the list.
Examples:
Max-height none: https://jsfiddle.net/bg5es49k/
Max-height 1000px: https://jsfiddle.net/bg5es49k/1/
Try to select Option 16, you'll get Option ~6.
Try to select Option 21, you'll get Option ~10.
Tested on a 1366x768 monitor.
How can I avoid this behaviour?
Thanks!

Try Select2 4.0, there were quite a few bugs in how the highlighting worked that should have been fixed.

Hi @kevin-brown,
It´s really fixed: https://jsfiddle.net/x2c5s7e1/
Thanks for the feedback and for this great plugin.


adding support for vmware's esx server

added support for detecting esxi server. NO os_release or lsb_release file present. So only option is to go with uname. Doesn't come under linux or unix kernel. They have their own vmware proprietary kernel called VMKernel.

Thank you @Anirudh-Gupta !! Awesome to see ESX in here :+1: :smile:


Test execution is not getting stop when something fails in beforeEach() or beforeAll()

💬 Test execution is not getting stop when something fails in beforeEach() or beforeAll()
I am performing integration testing with Jest and planning to develop some 1000+ test cases. This functionality is really effecting me.
For Example if my codes looks  like below:
describe(' SAMPLE TEST RUN ', () => {
beforeAll(() => {  expect(1+2).toBe(5)});
beforeEach(() => { expect(1+2).toBe(5)});
test('', () => console.log("TestExecuted"))
});
Output :

Why beforeEach() and test() are getting executed if beforeAll() is failing? Is there any solution i can stop further execution if something get fails in beforeAll() or beforeEach()?

Basically, we have to execute the rest of the tests and especially after hooks, because there might be important cleanup inside of them. It's kind of a try-finally.
Ideally, we would have an API that colocates setup with cleanup (e.g. aroundEach(() => {/* set things up */; return () => {/* clean things up */;}})) so that when a setup fails we can run only the cleanup for that one, but unfortunately that's not how the API was designed years ago.
As for stopping further execution I think the only way is to implement it yourself, roughly
let failed = false;
const myBeforeEach = (hook) => beforeEach(() => {
  if (failed) return;
  try {
    return hook()
  } catch(err) {
    failed = true;
    throw err;
  }
})
const myTest = (name, fn) => test(name, () => {
  if (failed) throw new Error('Skipping due to setup failure');
  return fn();
})

@jeysal : that seems like an anti-patten. No other test fw (testNG, PyTest, Cucumber etc...) behaves this way.
Request you to consider reopen the issue and provide a fix.


Expose service inactivity

The service will not expose service inactivity if kernels are detected not to be running.

https://github.com/ITISFoundation/osparc-issues/issues/1153

Will not make a new release at this time. We need more testing for that.

We are in agreement not to merge this PR. Will be keeping it here as a reference


Add new Raytac MDBT53-DB-40 and MDBT53V-DB-40 board

Adds support for Raytac MDBT53-DB-40 and MDBT53V-DB-40 demo board. These two boards pull out all the GPIOs of the module and connect them with pins without additional peripherals. It is very convenient for the development of various project programs.

@joerchan @anangl could you review please?

Is there anything else that needs to be modified?

@anangl, Could you review, please?

ping @anangl


fix client event documentation

The documentation on Client events in lib.rs erroneously says "To send specific events from server to client". I swapped server and client for accuracy.

Thanks!


Test and Handle OTAA

Last step of the the first Sprint, the implementation of the Over-The-Air-Activation process. This will require to strengthen the responsibility of the Broker and its Network Controller.
Nothing is settled yet about the way a handler is supposed to confirm a registration to an application.

Hi @KtorZ !
I was wondering if anything has been moving in this issue ? We are developing a custom handler for our special use-case, but waiting for the protocol definitions of the join sequence :)
Thanks!

Hey, I am on it, this week.
What you can expect for the protocol between broker and handler is gRPC and protocol buffers such that everything is language independent.
For the OTAA, you can expect the following message:
message JoinRequest {
    bytes       AppEUI          = 1; // 8-bytes long
    bytes       DevEUI          = 2; // 8-bytes long
    bytes       DevNonce        = 3; // 2-bytes long
    bytes       AppNonce        = 4; // 3-bytes long
}

This is not completely settled already however, it will be really close to that. I hope it helps.

Yep, that's exactly what I wanted to know! thank you for fast reaction!


*: remove quorum algorithm

What is changed and how it works?
What's Changed:
We use label based commit algorithm now, the settings are from PD, so
settings in TiKV side is stale.
Related changes

#7097

Check List
Tests

Unit test
Integration test

Side effects

Breaking backward compatibility of 4.0-rc.

/merge


ArcticDB 3.0.0

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

@poodlewars: can we close this PR in preference of #53?


Comment here to be added as a collaborator

Comment below - you can say anything
We will all be using this repository today. Even though it's public right now, you will not be able to make changes until you're given the correct permissions. We've automated this process via the GitHub API and some fancy chatops. Once you comment, we will add you as a collaborator.
You'll also start to receive a lot of emails. (:exclamation:) You can slow these down immediately by clicking the 'unsubscribe' button.

test

Comment

Hello

Adding comment.

I was asked to leave a comment here! 🌮

Hello

Comment

test

Hi Hi Hi

Aloha

Welcome to Git and Github

Hello!!!

Test Success

Hello !

yo

Hi

test comment for chris

this is mannan


[WIP] [tf.learn] API restructure

API restructure to unify pieces and support a wider variety of models (such as multi head, unsupervised, etc)
Done:

Estimator now uses (features, targets, mode) -> (prediction, loss, train_op). Moved optimize_loss into TensorFlowEstimator (it's now a "simple" Estimator).
Removed classification flag from Estimator.

Todo:

Integrate BaseEstimator and Estimator.
Add Classifier and Regressor subclasses.
Make sure TensorFlowEstimator supports multi-feature.
Integrate TensorFlowDNN/Linear with DNN/Linear Classifiers and Regressors.

CC @terrytangyuan @ispirmustafa @martinwicke

Pulling in.

See 123527855.

Awesome! So this will be included as part of internal branch merge later instead, right? @martinwicke

Yes. I will close this PR then. The skflow examples have to be adapted to
use the new DNNClassifier and DNNRegressor. If someone wants to do that on
top of this PR it will continue working when the internal code is merged
(hopefully later today). That's one of the major impediments to removing
the TensorFlowDNNEstimator,Regressor classes. As far as I can see at least,
Illia may know more.
On Sun, May 29, 2016 at 12:00 Yuan (Terry) Tang<EMAIL_ADDRESS>wrote:

Awesome! So this will be included as part of internal branch merge later
instead, right? @martinwicke https://github.com/martinwicke
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/tensorflow/pull/2551#issuecomment-222376773,
or mute the thread
https://github.com/notifications/unsubscribe/AAjO_fZ-El4vJkoEmd0QWttp9DqrvNqQks5qGeJPgaJpZM4IpAVb
.


dlb: update the link to dlb driver

Signed-off-by: Hyeongju Johannes Lee<EMAIL_ADDRESS>

The demo Dockerfiles could be updated too


Add a share API so non-web clients can upload.

Sorry, I thought I created a PR when I linked this diff in #meta-metapolis.
In theory, this shouldn't affect the existing endpoints, it just makes a new endpoint. I wasn't able to run it locally to test yet but I can figure it out later if you want me to before this gets merged.

Can merge when I'm home

Gah, sorry I dropped this. Merged now!


An error occurred during the push operation: The specified bucket does not exist error after amplify auth update

Yesterday, after a lot of poking in the dark,  I thought everything was ok with my vue+auth+graphql+hosted zone domain. trial project:
www.romuxis.com
Went to bed happy.
This morning tried the vue/amplify login on my site, got:
User pool client 4kg9ptbanodfdondtn02kb4flp does not exist.
In an attempt to fix that I run:
"amplify auth update"
And then
"amplify push"
and I got "The specified bucket does not exist" error.
After googling I figured that team-provide-info.json pointed to amplify-romuxisvue-dev-160005-deployment which did not exist.
So I create that.
Now I get:
"An error occurred during the push operation: The specified key does not exist."
After two weeks of struggling with AWS and amplify I'm sort of getting discouraged and frustrated.
Is it just me or what?
Lots of 'follow this path  and magic happens' documentation but nowhere really explained the concepts so that I could actually learn how things work so that I could solve the problems myself by debugging like the pro I am supposed to be.
Everywhere you get these terms like in this example "User pool client" , never seen that concept in two weeks of "learning".
And the error messages could do with improving.
"specified key does not exist."
or
"The specified bucket does not exist"
What key? What bucket? Where was it specified? Where did it not exist?
Error reporting 101...
Leaves me feeling that the web technology is developing at break neck speed and devs are just hacking and patching things up to keep up with the competition...
Ok, enough of that, but help would be appreciated to get me further.

Hi @nyholku  😄 - thanks for raising this!  To get a bit more context, do you mind porting this to one of the formatted templates listed here:

bug report or usage question

Those have all the required information to help the team determine the best approach to take.
Also, if it's helpful, there is an Amplify Community Discord server that may be helpful to bounce ideas and meet some folks. It's a really active community and community members are usually always online.

I tried to figure out how to make my bitbucket public. No luck so far. Should not be that difficult. Almost ready to wipe everything out at this point and try N:th time from scratch....

Hi @nyholku, Closing for now since this has taken a different direction.
If you run in a specific issue regarding the CLI, please open a new issue and list out the specific reproduction steps and supporting information.  That will help the team isolate the potential issue.


Feat. Request: getKeys()

Hi there
Any chances to have something like getMousePos() but for keyboard events.
Getting the dispatched key or even only the trigger event could be very useful.
Thanks and keep this sw up!

Second this feature request. It would be helpful to get a key's toggle state such as up or down.

This issue has been closed because it has been inactive for > 240 days.
You may reopen this issue if it has been closed in error.

If it possible, add this feature.

Yes please. Are there any alternatives to this? Anyone up to forking & modifying the robot.js code w/ me to accomplish this?
@saint739 @abusedmedia @xywang68

Yes please. Are there any alternatives to this? Anyone up to forking & modifying the robot.js code w/ me to accomplish this?
@saint739 @abusedmedia @xywang68


 I have not yet found out why.
  Tone.Transport.loop = true;
  Tone.Transport.loopEnd = "1:0:0";
  Tone.Transport.schedule(time => {
    metal.triggerAttack(time);
    metal.triggerAttack(time + Tone.Time("0:1:0"));
    metal.triggerRelease(time + Tone.Time("0:2:0"));
    metal.triggerRelease(time + Tone.Time("0:3:0"));
  }, 0);

Here's a Codepen that demonstrates the issue:
https://codepen.io/fabb64/pen/ebjJZq
(switch between scheduleDuoSynthNotes and scheduleMetalSynthNotes to listen to the two respectively)
Here are audio recordings of the problems (generated by just playing back the Codepen from above on the latest Chrome 71):
weird_synths.zip

Thanks for this test case! helped me find a very hard to reproduce bug which ended up being a floating-point error. The underlying oscillators are scheduled to stop, and then in the next Transport Loop restarted with nearly the same time. In the timeline class when two values are the same, the event is pushed onto the end which is what should have happened, but because of the floating point math, the second start was very very slightly less than the previous stopped time.
The solution here was to introduce comparisons with some epsilon threshold in the Timeline class. Seems to have fixed this issue.
Here's your code with the latest changes: https://jsfiddle.net/yotammann/L48zhgnp/

Awesome that you found it!


Fix: update install all_in_one.yaml

What type of PR is this?

Uncomment only one  /kind <> line, hit enter to put that in a new line, and remove leading whitespace from that line:
/kind bug
/kind documentation
/kind enhancement
/kind good-first-issue
/kind feature
/kind question
/kind design
/sig ai
/sig iot
/sig network
/sig storage
/sig storage

What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes # https://github.com/openyurtio/yurt-app-manager/issues/90
Special notes for your reviewer:

Does this PR introduce a user-facing change?

other Note

/assign @rambohe-ch

we can run make gen-all-in-one to get the newest all_in_one.yaml file.

/lgtm
/approve


Task 394-396: PersianQA

Based on the: https://github.com/sajjjadayobi/PersianQA

Since this is a non-English task, please add the appropriate fields based on #113.
@Palipoor wondering if you can review this PR?

In most of the cases, the output language is Persian, but there are some questions asking about a scientific term, etc, and their answer is in English. Is it okay to have two output languages?

I think we should go with the single dominant language, which in this case is "fa".

Thanks!

The tasks look good to me!
I'm not sure about the descriptions though. Should they be in English? (Just asking to know for future tasks)

Thanks! Yes, descriptions and explanations should be in English.

Thanks! Merging!


remove anti pattern

remove yield* next in lib/application, which caused annoy A promise was converted into a generator … message.
benchmark result:

when bench with native Promise, it has no impact for both stable and
experimental ones.
when bench with Bluebird, it’s about 5-10% faster than original for
both stable and experimental ones.

nice!


Height and width calculation taken from the container results in back panels affecting the DOM flow

Background
We have a component to capture an address (front) and provide look-up functionality. On supplying look-up details we search for matching addresses. This flips the address to display matching addresses (back). Selecting an address flips you back to the address input (front) with the selected address details populated.
Example markup

    Address capture

    Address look-up results

Issue
The front is not a fixed height and neither is the back. Based on the background I mocked up results in the back panel and configured flip using the manual trigger.
$( '#address' ).flip( { trigger:'manual' } );

As it stands the output is a container with a height that includes the front and back resulting in a large blank space due to the back now being hidden as shown in the image below.

Analysis
It would appear that the height and width is driven by the element you are performing the flip on (#address in this case). As this has no fixed height or width and the content is not hidden, you get the full height and width of the front and back components.
58  width: $dom.outerWidth(),
59  height: $dom.outerHeight()

These values are then also applied to the front and back panels.
69  $dom.find(".front, .back").outerHeight($dom.height());
70  $dom.find(".front, .back").outerWidth($dom.width());

Suggestion
Shouldn't the height and width be based on the front panel only. The back panel is hidden and it seems reasonable that the UI should only take up the necessary space required by the front panel. I would imagine something like this;
var height = $( '.front', $dom ).outerHeight();
var width = $( '.front', $dom ).outerWidth();

If you agree that this is an issue I more than happy to create a pull request to include the proposed suggestion.

+1

When I created this plugin, it was made for the content having the same size. I agree with you that the issue that you reported should be fixed. My concern is that I am quire not sure how animation during the flip will look when back and front is not the same size. You are more than welcome to contribute.
Cheers!

With different sizes the flip effect is kind of lost, not entirely, but it does not feel the same. Anyway if you comment the height assign operations, then the front and back child adjusts automatically, but the flip container, while not visible, will still take the whole space.

I think this can be fixed. We don't change the size while the content is flipping but once the flip is done then we can adjust the size.

Imho, this can now be easily worked around using new options autoSize, forceWidth and forceHeight. The force* options are false by default and if you set autoSize to false as well than Flip won't touch anything and you are free to style the front and back faces any way you want from CSS.
@michaelanfield  Please reopen this if you still have issues.


Added support of building using the deps fetched from pkg-config.

Hi @KOLANICH thank you. A couple of questions/notes:

This compiles an old version of the library, so it won't work with headers from fastpfor. Some work would be needed to link the original code by having it as, e.g., a submodule.
What's the distribution mode of pkgconfig? Is it like pip or conda? One would need to upload source code somewhere? Sorry, I don't know anything: I haven't used it before.

This compiles an old version of the library, so it won't work with headers from fastpfor.

It works, the test has returned no error. BTW, the test itself is done wrong. One needs to use unittest module and assertEqual instead of just a func and asserts.

Some work would be needed to link the original code by having it as, e.g., a submodule.

It would require changes in the original library code. The dir with the headers has incorrect layout.

What's the distribution mode of pkgconfig? Is it like pip or conda? One would need to upload source code somewhere? Sorry, I don't know anything: I haven't used it before.

It is a kind of a standard. Just text files of a certain format in specifjc location. Can be distributed by any package manager and even without them, but to distribute them one has to generate them.
Their main use is on nix systems, but they can also be used on other systems, if there is a preaggreed location where pkgconfig gonna search them (it is likely hardcoded into the binary).
The original library CMake scripts generate them and install them (but I don't recommend to use cmake install , make install, ninja install and stuff like this, instead generate packages with CPack and install them).
BTW, it may be possible to get rid of a cext and use ctypes. It would allow using the lib in other implementations of python without recompilaion, and also would elimjnate any need in compilation of the cext, so users without compilers in their system (Visual Studio is shit, though for lot of packages MinGW-w64 works fine even on pythons compiled with VS) would be able to install the lib.

Ohh, there's a fastpfor header link, so it's ok.
Regarding pkgconfig: how does it interact with pip install?
The library isn't particular popular, so I wouldn't bother about shipping a windows version.

Regarding pkgconfig: how does it interact with pip install?

First one builds and installs libfastpfor-dev (debian) or libfastpfor-devel (ubuntu). For windows one can also build packages, i.e. using NSIS, or Qt IFW, or WiX.
There exist pkg-config impls for Windows: https://cygwin.com/packages/summary/pkg-config.html , https://packages.msys2.org/package/pkg-config .
Then one can build a wheel, and then install it with pip. The in Windows the shared library should be available in PATH though, but installers can take care about it, and CMake has a pref for that, CPACK_NSIS_MODIFY_PATH , but it is only for NSIS backend, for IFW backend there is no such a pref.

Ok, I will need to come back to this a bit later. BTW, I am not really eager to support Windows for this project unless it (for some reason) becomes popular.


Remove Buffer dependency

That browserifies into heavy bundle. Interesting, is there a way to convert to Buffer w/o Buffer dependency?

@dy interesting. I think browserify includes the buffer module regardless because browserify is meant to compile for the browser

I just saw this via the linked issue. If you want to prevent buffer being sucked in on the browser-side you can do this in the package.json:
{
  "browser": {
    "buffer": false
  }
}

And then code that uses buffer might need to sniff the methods before use. E.g.
if (typeof Buffer.from === 'function') {
  // Buffer available
}

@casr just tried that - it does not work this way.
 "buffer" : false

just blocks Buffer for that package even if the external packages require that. Related with https://github.com/browserify/browserify/issues/1881 I guess.

@casr yes. I want arraybuffer-to-buffer to include buffer only when the parent/sibling packages include that, and avoid otherwise.
Same situation is for the typedarray-pool, btw. People just opt out from using buffer at all, just because it bloats that small package.
There are also people forcing bundling buffer in small packages.

There is still one thing I don't understand is why this should arraybuffer-to-buffer need to decide this? Surely the person bundling for the browser can either opt-out of Buffer by either providing a simple shim or just putting false on that key like before.

We can delve into a lot of use scenarios, but generally speaking a package ideally should not cause unnecessary bloat of dependent packages - especially considering that likely arraybuffer-to-buffer is second/third-level dependency. Besides, not always that is possible to disable buffer globally - that can just break code, in particular this one.


Follow you splash scrren blog to do,but have a problem(Android)

Flutter : Splash Screen
In Android，from step 1 to 4,I did these, but have a problem is that:
/Users/happyphper/workspace/rrcp_flutter/android/app/src/main/java/com/example/rrcp_flutter/MainActivity.java:17: error: incompatible types: MainActivity cannot be converted to FlutterEngine
    GeneratedPluginRegistrant.registerWith(this);
                                           ^
Note: Some messages have been simplified; recompile with -Xdiags:verbose to get full output
1 error

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':app:compileDebugJavaWithJavac'.
> Compilation failed; see the compiler error output for details.
...

I clone you project to local and All is right.
So I compare android your directory to my directory,
I find a android/app/src/main/AndroidManifest.xml and   android/app/build.gradle are different, the difference is that
# AndroidManifest.xml
...
        <!-- Don't delete the meta-data below.
             This is used by the Flutter tool to generate GeneratedPluginRegistrant.java -->
        <meta-data
            android:name="flutterEmbedding"
            android:value="2" />
...

# build.gradle
...
...
apply plugin: 'com.android.application'
+ apply plugin: 'kotlin-android'
apply from: "$flutterRoot/packages/flutter_tools/gradle/flutter.gradle"
...
dependencies {
+ implementation "org.jetbrains.kotlin:kotlin-stdlib-jdk7:$kotlin_version"
    ...
}
...

this is flutter auto created, maybe the result is different version.

put this code to your project, and the error occurred.
I can't solve this problem, Could you have any solution?
My Flutter version.
[✓] Flutter (Channel master, v1.15.4-pre.82, on Mac OS X 10.15.3 19D76, locale en-CN)
    • Flutter version 1.15.4-pre.82 at /usr/local/flutter
    • Framework revision e481fcae52 (32 hours ago), 2020-02-14 22:34:30 -0800
    • Engine revision d60f298d9e
    • Dart version 2.8.0 (build 2.8.0-dev.9.0 edd64e6d5c)

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
    • Android SDK at /Users/wangbaolong/Library/Android/sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-29, build-tools 29.0.2
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b49-5587405)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 11.3.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.3.1, Build version 11C504
    • CocoaPods version 1.8.4

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 3.5)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 41.0.2
    • Dart plugin version 191.8593
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b49-5587405)

[✓] VS Code (version 1.42.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.8.1

[✓] Connected device (3 available)
    • Android SDK built for x86 64 • emulator-5556 • android-x64    • Android 10 (API 29) (emulator)
    • Chrome                       • chrome        • web-javascript • Google Chrome 79.0.3945.130
    • Web Server                   • web-server    • web-javascript • Flutter Tools

what's the code of your MainActivity.java ?

@diegoveloper The MainActivity.java is not auto created. So I copy your code the android/app/src/main/java/com/example/rrcp_flutter/MainActivity.java. code is same. like this
package com.example.rrcp_flutter;

import android.os.Bundle;
import io.flutter.app.FlutterActivity;
import io.flutter.plugins.GeneratedPluginRegistrant;

import android.view.ViewTreeObserver;
import android.view.WindowManager;

public class MainActivity extends FlutterActivity {
  @Override
  protected void onCreate(Bundle savedInstanceState) {
    super.onCreate(savedInstanceState);
    //make transparent status bar
    getWindow().setStatusBarColor(0x00000000);
    GeneratedPluginRegistrant.registerWith(this);
    //Remove full screen flag after load
    ViewTreeObserver vto = getFlutterView().getViewTreeObserver();
    vto.addOnGlobalLayoutListener(new ViewTreeObserver.OnGlobalLayoutListener() {
      @Override
      public void onGlobalLayout() {
        getFlutterView().getViewTreeObserver().removeOnGlobalLayoutListener(this);
        getWindow().clearFlags(WindowManager.LayoutParams.FLAG_FULLSCREEN);
      }
    });
  }
}

Actually, you don't need to modify the MainActivity ,  remove that class, just use the classes generated using flutter create .

Thanks a lot.
I create a new project, and use the flutter_native_splash to create android native splash.
I found there are something differences between new project and  old project. then compare with these, I solved this problem.
and for IOS, I used xcode to adjust the size.
Use Xcode To Adjust Native Splash Screen


Add zh-HK and zh-TW translations

Some other translations have been added in #154, would you mind to include them here?

Some other translations have been added in https://github.com/simple-icons/simple-icons-website/pull/154, would you mind to include them here?

No problem. Let me add them.
I'm encountering a CSS issue, so I mark this PR to draft. Will update it later (my bedtime is up ✌).

Thank you, great addition 🎆


How do I set the cursor's position?

hello
how can i set the cursor to the last position of the text
this method doesn't exist
(val editText = findViewById(R.id.edittext_id) as EditText)
editText.setSelection(editText.text.length)
thanks

同问

focusEditor()；can move to the end


Difference With Theme Check Plugin?

Hi there,
Wordpress Theme Review Requirement encouraged theme developers run their theme through Theme Check.
I'm confused whether to use Theme Sniffer or the Theme Check.
What's the difference between those two ?

Theme Check runs on theme upload, while Theme Sniffer is a recommended tool that will run PHP_CodeSniffer against your theme. It's a help for theme authors and reviewers to check the themes 🙂

Theme Sniffer is newer, so it's not mentioned there yet. And the goal is to replace Theme Check on upload with Theme Sniffer. But the first plugin release was recent and it's not ready for that yet.


Implement CMP (Cookie Management Platform)

For our customers to comply with ePrivacy law, they need to ask for consent for installing cookies/local storage on their customers' machines.
The YAML should for every external resource (e.g. iframe embedding) support adding Cookie-consent and ONLY load that external resource if consent is given in the CMP. Attributes needed to support with example of Doubleclick:

Name: IDE
Hostname: .doubleclick.net
Path: /
Expiry: 730 days
Description: Use byd Google's DoubleClick to serve...

Good looking implementation: https://www.legalmonster.com/features/cookie-consent/


Add support for Custom query parameters

Is your feature request related to a problem? Please describe.
Please add support for the setting: "Custom query parameters" (customQueryParameters) into the datasource.
Describe the solution you'd like
It would be great if the Operator considers the datasource setting customQueryParameters.
Currently, you can set it in the CRD, but it does not end up in the ConfigMap nor in Grafana.
Additional context
I am trying to leverage OpenShift's user-defined monitoring to bring custom metrics into Grafana dashboards. The datasource is configured to talk to "thanos-querier" to find all required data.
In OpenShift there are two services for the thanos-querier.
One is listening on port 9091... everything fine here, I can see data. The problem is, I see too many.
The serviceaccount requires cluster permissions for monitoring (cluster-monitoring-view).
This means you will see ALL metrics. You can create a dashboard, for example, which is displaying all pods from the system.
Therefore, thanos-querier has a service on a second port: 9092.
Here, all you need are project view permissions in order to display metrics from one project only. However, this port requires, that you send the URL parameter "namespace=yournamespace" with the query.
(Thats actually the same, the Developer UI of OpenShift does.)
In Grafana you can configure this, by setting "Custom query parameters" (customQueryParamters) ... the problem is that this parameter will be lost after the grafana Pods restart or a new configuration is done.
Now I have to admit that this setting is not heavily documented inside Grafana documentation, but when you configure it manually on Grafana UI it ends up in the database like this:
sqlite> select * from data_source;
1|1|2|prometheus|Prometheus|proxy|https://thanos-querier.openshift-monitoring.svc.cluster.local:9092||||0|||1|{"customQueryParameters":"namespace=ns1","httpHeaderName1":"Authorization" ...

So, it seems to be part of the struct: jsonData.

Closed by #350


please disable/delete https://github.com/pivpn/easy-rsa git-repo

as pivpn does seem to use upstream repo/release now

@james-lasersoft can you please fix this?
Perhaps can you raise my permissions within the repo?
Kind Regards.

This has been done.
Deleted pivpn/easy-rsa.
Closing.


Added https://dis.gd/studenthubs

I've added a new link (https://dis.gd/studenthubs) from lines 1608 to 1614, which is a blog post about Student Hubs.

Looks great! Thanks for the addition to the list!
Sorry it took so long - I'll probably add some more shortlinks in a bit, missed quite a few haha.

Hero


Update year to 2021

Codecov Report

Merging #85 (762392b) into master (f509bd1) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #85   +/-   ##
=======================================
  Coverage   44.89%   44.89%
=======================================
  Files           9        9
  Lines         147      147
=======================================
  Hits           66       66
  Misses         73       73
  Partials        8        8

Continue to review full report at Codecov.

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

Codecov Report

Merging #85 (762392b) into master (f509bd1) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #85   +/-   ##
=======================================
  Coverage   44.89%   44.89%
=======================================
  Files           9        9
  Lines         147      147
=======================================
  Hits           66       66
  Misses         73       73
  Partials        8        8

Continue to review full report at Codecov.

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


[Addition] 4. K-means: Clustering Stability

In lecture 4 we also discussed clustering stability, including:

Distance between clusters
Calculation of stability
Normalization of stability

We could consider adding those formulas to the summary, but I am not sure if this is relevant or if we have enough space. I can make a pull request if there is nothing more important we can add.

Thanks, that is definitely something to consider.
Let us wait and see if more important topics arise and include it later if the space remains unneeded.

I think we should include this, I'll add it later.


Not support dynamic slot names

Environment

Operating System: Darwin
Node Version:     v18.12.1
Nuxt Version:     3.0.0
Nitro Version:    1.0.0
Package Manager<EMAIL_ADDRESS>Builder:          vite
User Config:      runtimeConfig, build, modules, hooks, proxy, vue, components, typescript, vite, plugins, css
Runtime Modules<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Build Modules:

Reproduction
https://stackblitz.com/edit/github-xbmezj?file=components/custom-button.vue
Describe the bug
According to the Vue3 documentation dynamic slot names section, I wrote the following line:
<template v-slot:[slot[0]]>
But I got some error:
[vite] Internal server error: Codegen node is missing for element/if/for node. Apply appropriate transforms first.
Additional context
No response
Logs
No response

This is not a nuxt issue, but wrong syntax, see https://github.com/vuejs/core/issues/5748. Can be closed.

@madebyfabian Could you briefly explain your reasoning? I don't see the connection between the linked issue an this one yet, as no v-if is in use here.


Allowing compilation of a static library in lucet

Context
This is part of a series of bugs that I spoke to @tyler @pchickey about. We are currently using  Lucet to sandbox libraries in C++ applications. The idea behind this is that using a wasm sandboxed version of the library allows ensuring that a memory safety issue in the library does not automatically result in a memory safety vulnerability in the full application. One of the  consumers of this work is the Firefox web browser.
Problem
Currently lucet applications are compiled as shared object files that must have a main function. However, these restrictions make static linking of libraries very challenging. I thus wanted to start a discussion about how to allow static linking of binaries produces by lucet.
The most obvious changes that come to mind are

Removing the requirement of having a main function
Symbol name collisions - when linking multiple binaries generated via lucet, both modules would have a lucet_module_data symbol which would collide.

Actions
Any thoughts on the feasibility of this request or whether would be fantastic. Additionally, if we can land on a design, I would be happy to contribute a patch implementing the same.

Removing the requirement of having a main function

I don't believe this is currently a requirement, except that lucet-wasi defaults to running _start. You can use lucet-wasi --entrypoint foo to pick a different entrypoint.

Symbol name collisions - when linking multiple binaries generated via lucet, both modules would have a lucet_module_data symbol which would collide.

Yeah, we definitely would need to configure lucetc to emit different symbol names for these. There also will probably be some issues with the relocations for initial table values; @awortman-fastly knows much more about that than I do, though.

Symbol name collisions - when linking multiple binaries generated via lucet, both modules would have a lucet_module_data symbol which would collide.

Ooh, statically linking multiple lucet modules! That's a cool problem :)

Yeah, we definitely would need to configure lucetc to emit different symbol names for these.

I think something like a user-supplied prefix (or use the name of the input .wasm) to namespace the symbols we add would work well. That should be pretty easy to teach lucetc. I think the harder part would be indicating a non-default symbol for the module's metadata to anything runtime-side - which table to look into to resolve exports, things like that.

I don't believe this is currently a requirement, except that lucet-wasi defaults to running _start. You can use lucet-wasi --entrypoint foo to pick a different entrypoint.

Oh good to know. It feels a bit weird to pick an entry point for a library, but I guess I can just pick one of the existing library functions at random without repercussions?

I think something like a user-supplied prefix (or use the name of the input .wasm) to namespace the symbols we add would work well. That should be pretty easy to teach lucetc.

yay! :smiley:

I think the harder part would be indicating a non-default symbol for the module's metadata to anything runtime-side - which table to look into to resolve exports, things like that.

Umm, sorry I think I didn't follow this completely... I followed that the runtime has to be aware of the modified symbols i.e. user_prefix_lucet_module_data, user_prefix_guest_table_0, user_prefix_guest_table_0_len (I've been playing with the version released on crates, so these names may be dated)
This means there probably needs to be an extra API/some API modifications to allow the embedder to specify this prefix during module load.
Was this what you meant or are there additional concerns/considerations apart from this?

Oh good to know. It feels a bit weird to pick an entry point for a library, but I guess I can just pick one of the existing library functions at random without repercussions?

Well, the lucet-wasi binary (as opposed to library) is meant for running executables. It just happens to also work for any library functions that take no arguments, if you wanted to specify a different entrypoint.

@awortman-fastly @acfoltzer - Just following up on this. Is the ability to link multiple lucet modules something you could reasonably consider? If so, is this something that would be handled internally or is this something I should try to contribute a patch for? In the interest of next steps, should I try to implement the user supplied prefix for symbols?
@awortman-fastly - Also just a gentle reminder about the clarification question above? :smiley:

Oops, yes. Regarding user-supplied prefixes, you understood me entirely. The only symbols you should have to change are where we use LUCET_MODULE_SYM in lucetc and in lucet-runtime. Externally visible function names would need the user-supplied prefix prepended too, and local functions should get the same treatment for consistency.
I'm not too sure how symbols other than those will pan out, because I think our other symbols at this point are all local and shouldn't need to be changed. So if that all works, great! If not, hopefully that still gets you pretty close. The symbol tweaking will conflict a bit with #295, but shouldn't be hard to resolve - just a question of who gets which changes in first.
I can't think of a reason we would want to not support this, but I also don't think I'll be able to get around to this soon, so I'd be happy to review a patch :D


Update documentation

Description

Closes #363

Checklist

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] My changes generate no new warnings
[ ] Any dependent changes have been merged and published in downstream modules

If applicable:

[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass with my changes (locally and CI/CD build)
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have noted that this is a breaking change for a major release (fix or feature that would cause existing functionality to not work as expected)

Hey @tomvothecoder, E3SM output mostly follows CF-convention and we strive to convert non-compliant items when possible.  I think we can rephrase it as:  "Support for CF compliant, non-CF compliant but common metadata"?

Hey @tomvothecoder, E3SM output mostly follows CF-convention and we strive to convert non-compliant items when possible. I think we can rephrase it as: "Support for CF compliant, non-CF compliant but common metadata"?

This sounds good to me. We might re-phrase to something like: "xcdat supports CF compliant datasets, but will also strive to support datasets with common non-CF compliant metadata."

I like the way @pochedls rephrased!

Thanks for the feedback everyone! I followed Steve's rephrased description.


iOS 13.3.1 dyld: Library not loaded

I'm getting this error when trying to run my app with Alamofire 5.0.0-rc3:
dyld: Library not loaded: @rpath/Alamofire.framework/Alamofire
Referenced from: /private/var/containers/Bundle/Application/CC8FF01F-CB03-4D92-ADDE-8B458EDF3D74/SupremeYou.app/SupremeYou
Reason: no suitable image found.  Did find:
/private/var/containers/Bundle/Application/CC8FF01F-CB03-4D92-ADDE-8B458EDF3D74/SupremeYou.app/Frameworks/Alamofire.framework/Alamofire: code signature invalid for '/private/var/containers/Bundle/Application/CC8FF01F-CB03-4D92-ADDE-8B458EDF3D74/SupremeYou.app/Frameworks/Alamofire.framework/Alamofire'
/private/var/containers/Bundle/Application/CC8FF01F-CB03-4D92-ADDE-8B458EDF3D74/SupremeYou.app/Frameworks/Alamofire.framework/Alamofire: stat() failed with errno=25
/private/var/containers/Bundle/Application/CC8FF01F-CB03-4D92-ADDE-8B458EDF3D74/SupremeYou.app/Frameworks/Alamofire.framework/Alamofire: code signature invalid for '/private/var/containers/Bundle/Application/CC8FF01F-CB03-4D92-ADDE-8B458EDF3D74/SupremeYou.app/Frameworks/Alamofire.framework/Alamofire'

I've been tested my app on an iPhone 11 Pro 13.3 and it was working fine until I decided to update the phone. So I update the iPhone 11 to the 13.3.1 version, and the error started to appear.
it works fine on an iPhone 8 Plus with iOS version 13.3.
Also it doesn't work on an iPhone 6s with iOS 13.3.1.

What fixed this issue in my case was to delete the Apple Development profile from my device and then let Xcode install it again when I ran the app on the device.
General > Device Management > Apple Development ... > tap on it then tap on Delete App. Then when you run again the app one your device the profile will be installed again and you'll be asked to Trust it again.

In my case it also required to reinstall provisioning profiles on my device

rileyestut, Yes, for now I am using a non-developer Apple-ID. And if I remove the use_frameworks! then I have problems with FirebaseAuth. And yes the problem occurs in others frameworks as i see now.

I am using SQLite.swift with free developer account and experiencing the same trouble using iOS 13.3.1. Apple seems to be preventing unpaid accounts use frameworks in their applications in iOS 13.3.1.
None of the workarounds worked for me by the way...

Are you using a non-developer Apple ID to install the app to your phone? It looks like iOS 13.3.1 has broken apps installed with free Apple IDs, but only if they contain embedded frameworks. If it's possible to link all your dependencies as static libraries rather than frameworks (for example, if you're using Cocoapods you can remove use_frameworks! from your Podfile), that should fix the issue for now.

Thank you so much Riley! I was about to smash my keyboard in frustration haha.

I had same issue with Alamofire, and solved it by removing use_frameworks! from pod file and adding use_modular_headers! then in console pod deintegrate, pod update and pod install
Now everything works fine.

Commenting out use_frameworks and adding use_modular_headers! to the Pod file. Then going to console pod update and pod install; after that Clean Build Folder and running made the trick! Thank you!

Can confirm; it has to do with a free account. Paid for an account [had to call up Apple to get them to process my order quicker] and my app is back up and running.
Disclaimer: my app has nothing to do with Alamofire but I came across this thread when looking for answers to my issues.

Getting seem problem but I don't want paid account yet any other solutions

It worked for me after a pods update and deleted the developer profile from the iPhone(General > Management...)

I had same issue with Alamofire, and solved it by removing use_frameworks! from pod file and adding use_modular_headers! then in console pod deintegrate, pod update and pod install
Now everything works fine.

That was the solution which worked for me, thank you!
Unfortunately, in another project I use Alamofire. If I try it on that project too but I get the linker error "framework not found Alamofire". It seems like it needs the use_framwork! ... a doom loop

lost 2 days for searching and found this ! unbelievable apple 😑

@rfcj I forgot to mention that I added use_modular_headers!. In my case, I'm using Realm and that pod keep throwing me error until I added the line I said.
Try that, maybe it will help with your pods.

That works, you save my life

Who can help me, after I commented "use_frameworks!", I got this fatal error: "module map file '/Users/admin/Desktop/Projects/Fairbase 0.1/Pods/Headers/Private/openssl_grpc/BoringSSL-GRPC.modulemap' not found"

I had same issue with Alamofire, and solved it by removing use_frameworks! from pod file and adding use_modular_headers! then in console pod deintegrate, pod update and pod install
Now everything works fine.

This has worked for me!

@rileytestut removing use_frameworks! and using use_modular_headers! didn't work for my various Firebase pods. But does this mean swapping to a paid developer ID will resolve this error?

I'm figuring out the same error and, after have payed the Apple Developer account, nothing change...

I would suggest everyone who is hitting this issue report a bug to Apple using the Feedback Assistant so that it can get fixed sooner rather than later. Additionally, anyone needing addition help fixing it should use StackOverflow or the Apple Developer Forums. Alamofire's GitHub issues is not the right place, if only because the audience here is very limited.

I have a issue with non-paid Apple Developer account. use_modular_headers! solve my problem.

Does anyone know if this was fixed in the iOS 13.4 beta?

removing use_frameworks! worked for me. I didn't need use_modular_headers!
I had a this issue and fixed it. I would like to add one process. pod update if you use pod after changing above line.

thanks to avoid spending time.

Does anyone know if this was fixed in the iOS 13.4 beta?

not according to this.

I had this problem, but it was due to the fact that I had Alamofire and CodableAlamofire in the project. CodableAlamofire on its own brings over Alamofire, so for some reason it was causing this same issue. Removed Alamofire from the Podfile and just kept CodableAlamofire and worked like a charm.

Hi the problem is in iOS version 13.1.3 eu tested in device different e is ok

@rfcj I forgot to mention that I added use_modular_headers!. In my case, I'm using Realm and that pod keep throwing me error until I added the line I said.
Try that, maybe it will help with your pods.

I'm getting some issues with realm and i do everything you mentioned, delete use_framworks! line and add use_modular_headers! clean and rebuild and now it shows me Realm need framework @Wasa22 you dont have that problem?

Could it be this thing?

"Apple blocked utilizing external frameworks on free accounts with 13.3.1 upgrade. Try downgrading to 13.3."

https://stackoverflow.com/a/60101963/8574785

Yeah it looks like the problem is the free Apple ID provisional profile.
Another people are mentioning this behavior like here:
ionic-team/capacitor#2383
And they said that the issue is solved with a paid developer Apple ID.

Apple just wants our money to run our apps lol.

I comment

use_frameworks!
and update pods then run my project on iphone 8plus  version 13.3.1  it's  working
Thanks ^^

This issue seems to be fixed on the latest beta for iOS 13.4 🎉

Can confirm, apps containing embedded frameworks installed with free Apple IDs are now working for me on iOS 13.4 beta 3 😄 Hope it stays fixed for GM!

The beta solved for me as well.

I updated my iPhone to iOS 13.4 beta 3 but when I went to run my app on my iPhone I got this error "Could not locate device support files. This iPhone X (Model A1865, A1901, A1902, A1903) is running iOS 13.4 (17E5241d), which may not be supported by this version of Xcode. An updated version of Xcode may be found on the App Store or at developer.apple.com."

You should update you Xcode to the version that support iOS beta version
On Sun, 1 Mar 2563 at 23:32 Rachel<EMAIL_ADDRESS>wrote:

I updated my iPhone to iOS 13.4 beta 3 but when I went to run my app on my
iPhone I got this error "Could not locate device support files. This iPhone
X (Model A1865, A1901, A1902, A1903) is running iOS 13.4 (17E5241d), which
may not be supported by this version of Xcode. An updated version of Xcode
may be found on the App Store or at developer.apple.com."
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Alamofire/Alamofire/issues/3051?email_source=notifications&email_token=ADKYITNMR7SSDV7STLVBYO3RFKEZPA5CNFSM4KM5O4VKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOENNDZTQ#issuecomment-593116366,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADKYITLOMMN6WB7TITWVS5DRFKEZPANCNFSM4KM5O4VA
.

You should update you Xcode to the version that support iOS beta version
…
On Sun, 1 Mar 2563 at 23:32 Rachel @.***> wrote: I updated my iPhone to iOS 13.4 beta 3 but when I went to run my app on my iPhone I got this error "Could not locate device support files. This iPhone X (Model A1865, A1901, A1902, A1903) is running iOS 13.4 (17E5241d), which may not be supported by this version of Xcode. An updated version of Xcode may be found on the App Store or at developer.apple.com." — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#3051?email_source=notifications&email_token=ADKYITNMR7SSDV7STLVBYO3RFKEZPA5CNFSM4KM5O4VKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOENNDZTQ#issuecomment-593116366>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADKYITLOMMN6WB7TITWVS5DRFKEZPANCNFSM4KM5O4VA .

It says Xcodes up to date.

I am having the same issue with my app while deploying it into iPad .. I am using cocoa and Mqtt to connect my app to my pi . it works on the virtual iPad . is it something related with privacy guys ? I mean the  iPad is not letting use the Mqtt server or something >>?

You should update you Xcode to the version that support iOS beta version
…
On Sun, 1 Mar 2563 at 23:32 Rachel @.***> wrote: I updated my iPhone to iOS 13.4 beta 3 but when I went to run my app on my iPhone I got this error "Could not locate device support files. This iPhone X (Model A1865, A1901, A1902, A1903) is running iOS 13.4 (17E5241d), which may not be supported by this version of Xcode. An updated version of Xcode may be found on the App Store or at developer.apple.com." — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#3051?email_source=notifications&email_token=ADKYITNMR7SSDV7STLVBYO3RFKEZPA5CNFSM4KM5O4VKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOENNDZTQ#issuecomment-593116366>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADKYITLOMMN6WB7TITWVS5DRFKEZPANCNFSM4KM5O4VA .

It says Xcodes up to date.

What's your Xcode version?
for newest beta version is 11.4 beta 2
Did you enroll apple developer program?

It seems this issue has run its course and is fixed in the 13.4 betas. I'm going to leave it open until 13.4 is officially released (probably sometime in March) and see if it's still fixed. However, I'm locking it for now as it's getting quite off topic. Anyone needing other support is encouraged to search online or move to StackOverflow.

Now that Xcode 11.4 and iOS 13.4 has shipped, can anyone confirm that the fix for this issue made it into the release?

It's finally working again on the new Xcode and iOS releases.

Yes i can confirm it is working right now. You dont understand how relieved i am feeling..

Great! Thanks for the help everyone, I'm happy to finally close this issue.

Are you using a non-developer Apple ID to install the app to your phone? It looks like iOS 13.3.1 has broken apps installed with free Apple IDs, but only if they contain embedded frameworks. If it's possible to link all your dependencies as static libraries rather than frameworks (for example, if you're using Cocoapods you can remove use_frameworks! from your Podfile), that should fix the issue for now.

Hi when I comment out use_frameworks! from your Podfile, I get vibration/vibration-Swift.h file not found. Please help !
Refer to this for the error log: https://github.com/benjamindean/flutter_vibration/issues/1

Sorry, this thread isn't for long term support.


sel module not working for iDRAC7 and iDRAC8.

Hey there,
Great project and thanks for making it. I was trying to deploy it in my homelab where I have a R430 (iDRAC 8) and an R420 (iDRAC 7). I was super interested in the sel module so that I could pull logs off of it and into Prometheus. Unfortunately I keep getting the following errors:
2023-06-10T23:35:31.141 INFO  Server listening on <IP_ADDRESS>:9348
panic: interface conversion: interface {} is nil, not string
goroutine 40 [running]:
github.com/mrlhansen/idrac_exporter/internal/collector.(*xstring).UnmarshalJSON(0xc0002f6370, {0xc0002d18a2, 0x11, 0x255e})
	/app/src/internal/collector/unmarshal.go:35 +0x196
encoding/json.(*decodeState).array(0xc00025e3e8, {0x83ba80?, 0xc0002f6370?, 0x257b?})
	/usr/local/go/src/encoding/json/decode.go:507 +0x431
encoding/json.(*decodeState).value(0xc00025e3e8, {0x83ba80?, 0xc0002f6370?, 0x9?})
	/usr/local/go/src/encoding/json/decode.go:364 +0x7e
encoding/json.(*decodeState).object(0xc00025e3e8, {0x8bac40?, 0xc0002f6328?, 0xb?})
	/usr/local/go/src/encoding/json/decode.go:775 +0xd45
encoding/json.(*decodeState).value(0xc00025e3e8, {0x8bac40?, 0xc0002f6328?, 0x2e?})
	/usr/local/go/src/encoding/json/decode.go:374 +0x45
encoding/json.(*decodeState).array(0xc00025e3e8, {0x834320?, 0xc0001e5020?, 0x7d2e?})
	/usr/local/go/src/encoding/json/decode.go:562 +0x65b
encoding/json.(*decodeState).value(0xc00025e3e8, {0x834320?, 0xc0001e5020?, 0x7?})
	/usr/local/go/src/encoding/json/decode.go:364 +0x7e
encoding/json.(*decodeState).object(0xc00025e3e8, {0x8295c0?, 0xc0001e5000?, 0xc0001b7b90?})
	/usr/local/go/src/encoding/json/decode.go:775 +0xd45
encoding/json.(*decodeState).value(0xc00025e3e8, {0x8295c0?, 0xc0001e5000?, 0xc0001b7be0?})
	/usr/local/go/src/encoding/json/decode.go:374 +0x45
encoding/json.(*decodeState).unmarshal(0xc00025e3e8, {0x8295c0?, 0xc0001e5000?})
	/usr/local/go/src/encoding/json/decode.go:181 +0x1de
encoding/json.(*Decoder).Decode(0xc00025e3c0, {0x8295c0, 0xc0001e5000})
	/usr/local/go/src/encoding/json/stream.go:73 +0x191
github.com/mrlhansen/idrac_exporter/internal/collector.(*Client).redfishGet(0xc000128380, {0x8ea174?, 0x0?}, {0x8295c0, 0xc0001e5000})
	/app/src/internal/collector/client.go:301 +0x4f0
github.com/mrlhansen/idrac_exporter/internal/collector.(*Client).RefreshIdracSel(0xc000180600?, 0x0?, 0x0?)
	/app/src/internal/collector/client.go:202 +0x75
github.com/mrlhansen/idrac_exporter/internal/collector.(*Collector).Collect(0xc000104480, 0xc000051f60?)
	/app/src/internal/collector/collector.go:264 +0xad
github.com/prometheus/client_golang/prometheus.(*Registry).Gather.func1()
	/go/pkg/mod/github.com/prometheus/client_golang@v1.15.1/prometheus/registry.go:455 +0x10d
created by github.com/prometheus/client_golang/prometheus.(*Registry).Gather
	/go/pkg/mod/github.com/prometheus/client_golang@v1.15.1/prometheus/registry.go:466 +0x55d

This was running in a container container using the provided Dockerfile.
When running the command:
curl -k https://idrac-metz.network/redfish/v1/Managers/iDRAC.Embedded.1/Logs/Sel -u root | jq

I get the following back:
{
<EMAIL_ADDRESS>"/redfish/v1/$metadata#LogEntryCollection.LogEntryCollection",
<EMAIL_ADDRESS>"/redfish/v1/Managers/iDRAC.Embedded.1/Logs/Sel",
<EMAIL_ADDRESS>"#LogEntryCollection.LogEntryCollection",
  "Description": "System Event Logs for this manager",
  "Members": [
    {
<EMAIL_ADDRESS>"/redfish/v1/Managers/iDRAC.Embedded.1/Logs/Sel/34",
<EMAIL_ADDRESS>"#LogEntry.v1_3_0.LogEntry",
      "Created": "2023-05-23T06:22:59-05:00",
      "Description": " Log Entry 34",
      "EntryCode": [
        {
          "Member": "Transition to Non-Critical from OK"
        }
      ],
      "EntryType": "SEL",
      "Id": "34",
      "Links": {},
      "Message": "Correctable memory error rate exceeded for DIMM_A4.",
      "MessageArgs": [],
<EMAIL_ADDRESS>0,
      "MessageId": "a1908",
      "Name": " Log Entry 34",
      "SensorNumber": 27,
      "SensorType": [
        {
          "Member": "Memory"
        }
      ],
      "Severity": "Warning"
    },
    {
<EMAIL_ADDRESS>"/redfish/v1/Managers/iDRAC.Embedded.1/Logs/Sel/33",
<EMAIL_ADDRESS>"#LogEntry.v1_3_0.LogEntry",
      "Created": "2023-04-10T00:47:37-05:00",
      "Description": " Log Entry 33",
      "EntryCode": [
        {
          "Member": "Deassert"
        }
      ],
      "EntryType": "SEL",
      "Id": "33",
      "Links": {},
      "Message": "The PERC1 battery is operating normally.",
      "MessageArgs": [],
<EMAIL_ADDRESS>0,
      "MessageId": "0ffff",
      "Name": " Log Entry 33",
      "SensorNumber": 104,
      "SensorType": [
        {
          "Member": "Battery"
        }
      ],
      "Severity": "OK"
    },
    {
<EMAIL_ADDRESS>"/redfish/v1/Managers/iDRAC.Embedded.1/Logs/Sel/32",
<EMAIL_ADDRESS>"#LogEntry.v1_3_0.LogEntry",
      "Created": "2023-04-10T00:25:58-05:00",
      "Description": " Log Entry 32",
      "EntryCode": [
        {
          "Member": "Assert"
        }
      ],
      "EntryType": "SEL",
      "Id": "32",
      "Links": {},
      "Message": "The PERC1 battery is low.",
      "MessageArgs": [],
<EMAIL_ADDRESS>0,
      "MessageId": "0ffff",
      "Name": " Log Entry 32",
      "SensorNumber": 104,
      "SensorType": [
        {
          "Member": "Battery"
        }
      ],
      "Severity": "Warning"
    },
    {
<EMAIL_ADDRESS>"/redfish/v1/Managers/iDRAC.Embedded.1/Logs/Sel/31",
<EMAIL_ADDRESS>"#LogEntry.v1_3_0.LogEntry",
      "Created": "2023-01-09T20:10:54-06:00",
      "Description": " Log Entry 31",
      "EntryCode": [
        {
          "Member": "Deassert"
        }
      ],
      "EntryType": "SEL",
      "Id": "31",
      "Links": {},
      "Message": "The PERC1 battery is operating normally.",
      "MessageArgs": [],
<EMAIL_ADDRESS>0,
      "MessageId": "0ffff",
      "Name": " Log Entry 31",
      "SensorNumber": 104,
      "SensorType": [
        {
          "Member": "Battery"
        }
      ],
      "Severity": "OK"
    },
    {
<EMAIL_ADDRESS>"/redfish/v1/Managers/iDRAC.Embedded.1/Logs/Sel/30",
<EMAIL_ADDRESS>"#LogEntry.v1_3_0.LogEntry",
      "Created": "2023-01-09T20:02:15-06:00",
      "Description": " Log Entry 30",
      "EntryCode": [
        {
          "Member": "Assert"
        }
      ],
      "EntryType": "SEL",
      "Id": "30",
      "Links": {},
      "Message": "The PERC1 battery is low.",
      "MessageArgs": [],
<EMAIL_ADDRESS>0,
      "MessageId": "0ffff",
      "Name": " Log Entry 30",
      "SensorNumber": 104,
      "SensorType": [
        {
          "Member": "Battery"
        }
      ],
      "Severity": "Warning"
    },
    {
<EMAIL_ADDRESS>"/redfish/v1/Managers/iDRAC.Embedded.1/Logs/Sel/29",
<EMAIL_ADDRESS>"#LogEntry.v1_3_0.LogEntry",
      "Created": "2022-10-11T19:40:35-05:00",
      "Description": " Log Entry 29",
      "EntryCode": [
        {
          "Member": "Deassert"
        }
      ],
      "EntryType": "SEL",
      "Id": "29",
      "Links": {},
      "Message": "The PERC1 battery is operating normally.",
      "MessageArgs": [],
<EMAIL_ADDRESS>0,
      "MessageId": "0ffff",
      "Name": " Log Entry 29",
      "SensorNumber": 104,
      "SensorType": [
        {
          "Member": "Battery"
        }
      ],
      "Severity": "OK"
    },
    {
<EMAIL_ADDRESS>"/redfish/v1/Managers/iDRAC.Embedded.1/Logs/Sel/28",
<EMAIL_ADDRESS>"#LogEntry.v1_3_0.LogEntry",
      "Created": "2022-10-11T19:07:05-05:00",
      "Description": " Log Entry 28",
      "EntryCode": [
        {
          "Member": "Assert"
        }
      ],
      "EntryType": "SEL",
      "Id": "28",
      "Links": {},
      "Message": "The PERC1 battery is low.",
      "MessageArgs": [],
<EMAIL_ADDRESS>0,
      "MessageId": "0ffff",
      "Name": " Log Entry 28",
      "SensorNumber": 104,
      "SensorType": [
        {
          "Member": "Battery"
        }
      ],
      "Severity": "Warning"
    },
    {
<EMAIL_ADDRESS>"/redfish/v1/Managers/iDRAC.Embedded.1/Logs/Sel/27",
<EMAIL_ADDRESS>"#LogEntry.v1_3_0.LogEntry",
      "Created": "2022-06-17T18:40:21-05:00",
      "Description": " Log Entry 27",
      "EntryCode": [
        {
          "Member": "Deassert"
        }
      ],
      "EntryType": "SEL",
      "Id": "27",
      "Links": {},
      "Message": "The chassis is closed while the power is off.",
      "MessageArgs": [],
<EMAIL_ADDRESS>0,
      "MessageId": "802ff",
      "Name": " Log Entry 27",
      "SensorNumber": 115,
      "SensorType": [
        {
          "Member": "Physical Chassis Security"
        }
      ],
      "Severity": "OK"
    },
    {
<EMAIL_ADDRESS>"/redfish/v1/Managers/iDRAC.Embedded.1/Logs/Sel/26",
<EMAIL_ADDRESS>"#LogEntry.v1_3_0.LogEntry",
      "Created": "2022-06-17T18:40:16-05:00",
      "Description": " Log Entry 26",
      "EntryCode": [
        {
          "Member": "Assert"
        }
      ],
      "EntryType": "SEL",
      "Id": "26",
      "Links": {},
      "Message": "The chassis is open while the power is off.",
      "MessageArgs": [],
<EMAIL_ADDRESS>0,
      "MessageId": "802ff",
      "Name": " Log Entry 26",
      "SensorNumber": 115,
      "SensorType": [
        {
          "Member": "Physical Chassis Security"
        }
      ],
      "Severity": "Critical"
    },
    {
<EMAIL_ADDRESS>"/redfish/v1/Managers/iDRAC.Embedded.1/Logs/Sel/25",
<EMAIL_ADDRESS>"#LogEntry.v1_3_0.LogEntry",
      "Created": "2022-04-07T15:23:51-05:00",
      "Description": " Log Entry 25",
      "EntryCode": [
        {
          "Member": "Transition to Critical from less severe"
        }
      ],
      "EntryType": "SEL",
      "Id": "25",
      "Links": {},
      "Message": "Correctable memory error rate exceeded for DIMM_A4.",
      "MessageArgs": [],
<EMAIL_ADDRESS>0,
      "MessageId": "a2908",
      "Name": " Log Entry 25",
      "SensorNumber": 27,
      "SensorType": [
        {
          "Member": "Memory"
        }
      ],
      "Severity": "Critical"
    },
    {
<EMAIL_ADDRESS>"/redfish/v1/Managers/iDRAC.Embedded.1/Logs/Sel/24",
<EMAIL_ADDRESS>"#LogEntry.v1_3_0.LogEntry",
      "Created": "2022-03-18T16:26:58-05:00",
      "Description": " Log Entry 24",
      "EntryCode": [
        {
          "Member": "Transition to Non-Critical from OK"
        }
      ],
      "EntryType": "SEL",
      "Id": "24",
      "Links": {},
      "Message": "Correctable memory error rate exceeded for DIMM_A4.",
      "MessageArgs": [],
<EMAIL_ADDRESS>0,
      "MessageId": "a1908",
      "Name": " Log Entry 24",
      "SensorNumber": 27,
      "SensorType": [
        {
          "Member": "Memory"
        }
      ],
      "Severity": "Warning"
    },
    {
<EMAIL_ADDRESS>"/redfish/v1/Managers/iDRAC.Embedded.1/Logs/Sel/23",
<EMAIL_ADDRESS>"#LogEntry.v1_3_0.LogEntry",
      "Created": "2022-01-14T06:48:24-06:00",
      "Description": " Log Entry 23",
      "EntryCode": [
        {
          "Member": "Deassert"
        }
      ],
      "EntryType": "SEL",
      "Id": "23",
      "Links": {},
      "Message": "The PERC1 battery is operating normally.",
      "MessageArgs": [],
<EMAIL_ADDRESS>0,
      "MessageId": "0ffff",
      "Name": " Log Entry 23",
      "SensorNumber": 104,
      "SensorType": [
        {
          "Member": "Battery"
        }
      ],
      "Severity": "OK"
    },
    {
<EMAIL_ADDRESS>"/redfish/v1/Managers/iDRAC.Embedded.1/Logs/Sel/22",
<EMAIL_ADDRESS>"#LogEntry.v1_3_0.LogEntry",
      "Created": "2022-01-14T06:27:53-06:00",
      "Description": " Log Entry 22",
      "EntryCode": [
        {
          "Member": "Assert"
        }
      ],
      "EntryType": "SEL",
      "Id": "22",
      "Links": {},
      "Message": "The PERC1 battery is low.",
      "MessageArgs": [],
<EMAIL_ADDRESS>0,
      "MessageId": "0ffff",
      "Name": " Log Entry 22",
      "SensorNumber": 104,
      "SensorType": [
        {
          "Member": "Battery"
        }
      ],
      "Severity": "Warning"
    },
    {
<EMAIL_ADDRESS>"/redfish/v1/Managers/iDRAC.Embedded.1/Logs/Sel/21",
<EMAIL_ADDRESS>"#LogEntry.v1_3_0.LogEntry",
      "Created": "2021-10-16T05:18:36-05:00",
      "Description": " Log Entry 21",
      "EntryCode": [
        {
          "Member": "Deassert"
        }
      ],
      "EntryType": "SEL",
      "Id": "21",
      "Links": {},
      "Message": "The PERC1 battery is operating normally.",
      "MessageArgs": [],
<EMAIL_ADDRESS>0,
      "MessageId": "0ffff",
      "Name": " Log Entry 21",
      "SensorNumber": 104,
      "SensorType": [
        {
          "Member": "Battery"
        }
      ],
      "Severity": "OK"
    },
    {
<EMAIL_ADDRESS>"/redfish/v1/Managers/iDRAC.Embedded.1/Logs/Sel/20",
<EMAIL_ADDRESS>"#LogEntry.v1_3_0.LogEntry",
      "Created": "2021-10-16T04:34:14-05:00",
      "Description": " Log Entry 20",
      "EntryCode": [
        {
          "Member": "Assert"
        }
      ],
      "EntryType": "SEL",
      "Id": "20",
      "Links": {},
      "Message": "The PERC1 battery is low.",
      "MessageArgs": [],
<EMAIL_ADDRESS>0,
      "MessageId": "0ffff",
      "Name": " Log Entry 20",
      "SensorNumber": 104,
      "SensorType": [
        {
          "Member": "Battery"
        }
      ],
      "Severity": "Warning"
    },
    {
<EMAIL_ADDRESS>"/redfish/v1/Managers/iDRAC.Embedded.1/Logs/Sel/19",
<EMAIL_ADDRESS>"#LogEntry.v1_3_0.LogEntry",
      "Created": "2021-07-18T02:39:30-05:00",
      "Description": " Log Entry 19",
      "EntryCode": [
        {
          "Member": "Deassert"
        }
      ],
      "EntryType": "SEL",
      "Id": "19",
      "Links": {},
      "Message": "The PERC1 battery is operating normally.",
      "MessageArgs": [],
<EMAIL_ADDRESS>0,
      "MessageId": "0ffff",
      "Name": " Log Entry 19",
      "SensorNumber": 104,
      "SensorType": [
        {
          "Member": "Battery"
        }
      ],
      "Severity": "OK"
    },
    {
<EMAIL_ADDRESS>"/redfish/v1/Managers/iDRAC.Embedded.1/Logs/Sel/18",
<EMAIL_ADDRESS>"#LogEntry.v1_3_0.LogEntry",
      "Created": "2021-07-18T01:48:37-05:00",
      "Description": " Log Entry 18",
      "EntryCode": [
        {
          "Member": "Assert"
        }
      ],
      "EntryType": "SEL",
      "Id": "18",
      "Links": {},
      "Message": "The PERC1 battery is low.",
      "MessageArgs": [],
<EMAIL_ADDRESS>0,
      "MessageId": "0ffff",
      "Name": " Log Entry 18",
      "SensorNumber": 104,
      "SensorType": [
        {
          "Member": "Battery"
        }
      ],
      "Severity": "Warning"
    },
    {
<EMAIL_ADDRESS>"/redfish/v1/Managers/iDRAC.Embedded.1/Logs/Sel/17",
<EMAIL_ADDRESS>"#LogEntry.v1_3_0.LogEntry",
      "Created": "2021-03-12T02:59:23-06:00",
      "Description": " Log Entry 17",
      "EntryCode": [
        {
          "Member": "Deassert"
        }
      ],
      "EntryType": "SEL",
      "Id": "17",
      "Links": {},
      "Message": "The chassis is closed while the power is off.",
      "MessageArgs": [],
<EMAIL_ADDRESS>0,
      "MessageId": "802ff",
      "Name": " Log Entry 17",
      "SensorNumber": 115,
      "SensorType": [
        {
          "Member": "Physical Chassis Security"
        }
      ],
      "Severity": "OK"
    },
    {
<EMAIL_ADDRESS>"/redfish/v1/Managers/iDRAC.Embedded.1/Logs/Sel/16",
<EMAIL_ADDRESS>"#LogEntry.v1_3_0.LogEntry",
      "Created": "2021-03-12T02:59:18-06:00",
      "Description": " Log Entry 16",
      "EntryCode": [
        {
          "Member": "Assert"
        }
      ],
      "EntryType": "SEL",
      "Id": "16",
      "Links": {},
      "Message": "The chassis is open while the power is off.",
      "MessageArgs": [],
<EMAIL_ADDRESS>0,
      "MessageId": "802ff",
      "Name": " Log Entry 16",
      "SensorNumber": 115,
      "SensorType": [
        {
          "Member": "Physical Chassis Security"
        }
      ],
      "Severity": "Critical"
    },
    {
<EMAIL_ADDRESS>"/redfish/v1/Managers/iDRAC.Embedded.1/Logs/Sel/15",
<EMAIL_ADDRESS>"#LogEntry.v1_3_0.LogEntry",
      "Created": "2020-10-19T18:05:25-05:00",
      "Description": " Log Entry 15",
      "EntryCode": [
        {
          "Member": "Transition to Non-Critical from OK"
        }
      ],
      "EntryType": "SEL",
      "Id": "15",
      "Links": {},
      "Message": "Correctable memory error rate exceeded for DIMM_A4.",
      "MessageArgs": [],
<EMAIL_ADDRESS>0,
      "MessageId": "a1908",
      "Name": " Log Entry 15",
      "SensorNumber": 27,
      "SensorType": [
        {
          "Member": "Memory"
        }
      ],
      "Severity": "Warning"
    },
    {
<EMAIL_ADDRESS>"/redfish/v1/Managers/iDRAC.Embedded.1/Logs/Sel/14",
<EMAIL_ADDRESS>"#LogEntry.v1_3_0.LogEntry",
      "Created": "2020-07-13T17:27:03-05:00",
      "Description": " Log Entry 14",
      "EntryCode": [
        {
          "Member": "Deassert"
        }
      ],
      "EntryType": "SEL",
      "Id": "14",
      "Links": {},
      "Message": "The chassis is closed while the power is off.",
      "MessageArgs": [],
<EMAIL_ADDRESS>0,
      "MessageId": "802ff",
      "Name": " Log Entry 14",
      "SensorNumber": 115,
      "SensorType": [
        {
          "Member": "Physical Chassis Security"
        }
      ],
      "Severity": "OK"
    },
    {
<EMAIL_ADDRESS>"/redfish/v1/Managers/iDRAC.Embedded.1/Logs/Sel/13",
<EMAIL_ADDRESS>"#LogEntry.v1_3_0.LogEntry",
      "Created": "2020-07-13T17:26:58-05:00",
      "Description": " Log Entry 13",
      "EntryCode": [
        {
          "Member": "Assert"
        }
      ],
      "EntryType": "SEL",
      "Id": "13",
      "Links": {},
      "Message": "The chassis is open while the power is off.",
      "MessageArgs": [],
<EMAIL_ADDRESS>0,
      "MessageId": "802ff",
      "Name": " Log Entry 13",
      "SensorNumber": 115,
      "SensorType": [
        {
          "Member": "Physical Chassis Security"
        }
      ],
      "Severity": "Critical"
    },
    {
<EMAIL_ADDRESS>"/redfish/v1/Managers/iDRAC.Embedded.1/Logs/Sel/12",
<EMAIL_ADDRESS>"#LogEntry.v1_3_0.LogEntry",
      "Created": "2020-07-08T14:33:38-05:00",
      "Description": " Log Entry 12",
      "EntryCode": [
        {
          "Member": "Deassert"
        }
      ],
      "EntryType": "SEL",
      "Id": "12",
      "Links": {},
      "Message": "Power supply 1 is absent.",
      "MessageArgs": [],
<EMAIL_ADDRESS>0,
      "MessageId": "0ffff",
      "Name": " Log Entry 12",
      "SensorNumber": 98,
      "SensorType": [
        {
          "Member": "Power Supply / Converter"
        }
      ],
      "Severity": "Critical"
    },
    {
<EMAIL_ADDRESS>"/redfish/v1/Managers/iDRAC.Embedded.1/Logs/Sel/11",
<EMAIL_ADDRESS>"#LogEntry.v1_3_0.LogEntry",
      "Created": "2020-07-08T06:50:48-05:00",
      "Description": " Log Entry 11",
      "EntryCode": [
        {
          "Member": "Assert"
        }
      ],
      "EntryType": "SEL",
      "Id": "11",
      "Links": {},
      "Message": "The power input for power supply 1 is lost.",
      "MessageArgs": [],
<EMAIL_ADDRESS>0,
      "MessageId": "3ffff",
      "Name": " Log Entry 11",
      "SensorNumber": 98,
      "SensorType": [
        {
          "Member": "Power Supply / Converter"
        }
      ],
      "Severity": "Critical"
    },
    {
<EMAIL_ADDRESS>"/redfish/v1/Managers/iDRAC.Embedded.1/Logs/Sel/10",
<EMAIL_ADDRESS>"#LogEntry.v1_3_0.LogEntry",
      "Created": "2020-07-08T05:13:30-05:00",
      "Description": " Log Entry 10",
      "EntryCode": [
        {
          "Member": "Assert"
        }
      ],
      "EntryType": "SEL",
      "Id": "10",
      "Links": {},
      "Message": "The power input for power supply 1 is lost.",
      "MessageArgs": [],
<EMAIL_ADDRESS>0,
      "MessageId": "3ffff",
      "Name": " Log Entry 10",
      "SensorNumber": 98,
      "SensorType": [
        {
          "Member": "Power Supply / Converter"
        }
      ],
      "Severity": "Critical"
    },
    {
<EMAIL_ADDRESS>"/redfish/v1/Managers/iDRAC.Embedded.1/Logs/Sel/9",
<EMAIL_ADDRESS>"#LogEntry.v1_3_0.LogEntry",
      "Created": "2020-07-08T05:13:25-05:00",
      "Description": " Log Entry 9",
      "EntryCode": [
        {
          "Member": "Deassert"
        }
      ],
      "EntryType": "SEL",
      "Id": "9",
      "Links": {},
      "Message": "The chassis is closed while the power is off.",
      "MessageArgs": [],
<EMAIL_ADDRESS>0,
      "MessageId": "802ff",
      "Name": " Log Entry 9",
      "SensorNumber": 115,
      "SensorType": [
        {
          "Member": "Physical Chassis Security"
        }
      ],
      "Severity": "OK"
    },
    {
<EMAIL_ADDRESS>"/redfish/v1/Managers/iDRAC.Embedded.1/Logs/Sel/8",
<EMAIL_ADDRESS>"#LogEntry.v1_3_0.LogEntry",
      "Created": "2020-07-08T05:13:20-05:00",
      "Description": " Log Entry 8",
      "EntryCode": [
        {
          "Member": "Assert"
        }
      ],
      "EntryType": "SEL",
      "Id": "8",
      "Links": {},
      "Message": "The chassis is open while the power is off.",
      "MessageArgs": [],
<EMAIL_ADDRESS>0,
      "MessageId": "802ff",
      "Name": " Log Entry 8",
      "SensorNumber": 115,
      "SensorType": [
        {
          "Member": "Physical Chassis Security"
        }
      ],
      "Severity": "Critical"
    },
    {
<EMAIL_ADDRESS>"/redfish/v1/Managers/iDRAC.Embedded.1/Logs/Sel/7",
<EMAIL_ADDRESS>"#LogEntry.v1_3_0.LogEntry",
      "Created": "2020-06-29T21:34:18-05:00",
      "Description": " Log Entry 7",
      "EntryCode": [
        {
          "Member": null
        }
      ],
      "EntryType": "SEL",
      "Id": "7",
      "Links": {},
      "Message": "OEM software event.",
      "MessageArgs": [],
<EMAIL_ADDRESS>0,
      "MessageId": "2800",
      "Name": " Log Entry 7",
      "SensorNumber": 3,
      "SensorType": [
        {
          "Member": null
        }
      ],
      "Severity": "OK"
    },
    {
<EMAIL_ADDRESS>"/redfish/v1/Managers/iDRAC.Embedded.1/Logs/Sel/6",
<EMAIL_ADDRESS>"#LogEntry.v1_3_0.LogEntry",
      "Created": "2020-06-29T21:34:18-05:00",
      "Description": " Log Entry 6",
      "EntryCode": [
        {
          "Member": "Assert"
        }
      ],
      "EntryType": "SEL",
      "Id": "6",
      "Links": {},
      "Message": "An OS graceful shut-down occurred.",
      "MessageArgs": [],
<EMAIL_ADDRESS>0,
      "MessageId": "3ffff",
      "Name": " Log Entry 6",
      "SensorNumber": 0,
      "SensorType": [
        {
          "Member": "OS Stop/Shutdown"
        }
      ],
      "Severity": "OK"
    },
    {
<EMAIL_ADDRESS>"/redfish/v1/Managers/iDRAC.Embedded.1/Logs/Sel/5",
<EMAIL_ADDRESS>"#LogEntry.v1_3_0.LogEntry",
      "Created": "2020-06-29T21:33:00-05:00",
      "Description": " Log Entry 5",
      "EntryCode": [
        {
          "Member": "Assert"
        }
      ],
      "EntryType": "SEL",
      "Id": "5",
      "Links": {},
      "Message": "OEM software event.",
      "MessageArgs": [],
<EMAIL_ADDRESS>0,
      "MessageId": "fa5e0",
      "Name": " Log Entry 5",
      "SensorNumber": 255,
      "SensorType": [
        {
          "Member": null
        }
      ],
      "Severity": "OK"
    },
    {
<EMAIL_ADDRESS>"/redfish/v1/Managers/iDRAC.Embedded.1/Logs/Sel/4",
<EMAIL_ADDRESS>"#LogEntry.v1_3_0.LogEntry",
      "Created": "2020-06-29T21:33:00-05:00",
      "Description": " Log Entry 4",
      "EntryCode": [
        {
          "Member": "Assert"
        }
      ],
      "EntryType": "SEL",
      "Id": "4",
      "Links": {},
      "Message": "C: boot completed.",
      "MessageArgs": [],
<EMAIL_ADDRESS>0,
      "MessageId": "1ffff",
      "Name": " Log Entry 4",
      "SensorNumber": 0,
      "SensorType": [
        {
          "Member": "BaseOSBoot/InstallationStatus"
        }
      ],
      "Severity": "OK"
    },
    {
<EMAIL_ADDRESS>"/redfish/v1/Managers/iDRAC.Embedded.1/Logs/Sel/3",
<EMAIL_ADDRESS>"#LogEntry.v1_3_0.LogEntry",
      "Created": "2020-06-29T21:17:27-05:00",
      "Description": " Log Entry 3",
      "EntryCode": [
        {
          "Member": "Assert"
        }
      ],
      "EntryType": "SEL",
      "Id": "3",
      "Links": {},
      "Message": "OEM software event.",
      "MessageArgs": [],
<EMAIL_ADDRESS>0,
      "MessageId": "fa5e0",
      "Name": " Log Entry 3",
      "SensorNumber": 98,
      "SensorType": [
        {
          "Member": null
        }
      ],
      "Severity": "OK"
    },
    {
<EMAIL_ADDRESS>"/redfish/v1/Managers/iDRAC.Embedded.1/Logs/Sel/2",
<EMAIL_ADDRESS>"#LogEntry.v1_3_0.LogEntry",
      "Created": "2020-06-29T21:17:27-05:00",
      "Description": " Log Entry 2",
      "EntryCode": [
        {
          "Member": "Assert"
        }
      ],
      "EntryType": "SEL",
      "Id": "2",
      "Links": {},
      "Message": "C: boot completed.",
      "MessageArgs": [],
<EMAIL_ADDRESS>0,
      "MessageId": "1ffff",
      "Name": " Log Entry 2",
      "SensorNumber": 0,
      "SensorType": [
        {
          "Member": "BaseOSBoot/InstallationStatus"
        }
      ],
      "Severity": "OK"
    },
    {
<EMAIL_ADDRESS>"/redfish/v1/Managers/iDRAC.Embedded.1/Logs/Sel/1",
<EMAIL_ADDRESS>"#LogEntry.v1_3_0.LogEntry",
      "Created": "2020-06-29T20:57:59-05:00",
      "Description": " Log Entry 1",
      "EntryCode": [
        {
          "Member": "Assert"
        }
      ],
      "EntryType": "SEL",
      "Id": "1",
      "Links": {},
      "Message": "Log cleared.",
      "MessageArgs": [],
<EMAIL_ADDRESS>0,
      "MessageId": "2ffff",
      "Name": " Log Entry 1",
      "SensorNumber": 114,
      "SensorType": [
        {
          "Member": "Event Logging Disabled"
        }
      ],
      "Severity": "OK"
    }
  ],
<EMAIL_ADDRESS>34,
  "Name": "Log Entry Collection"
}

I wish I could help more, but I am absolute dogwater with Golang. Let me know if I can run any helpful cURL commands, or provide any additional. Hopefully this helps you resolve the issue, and thanks again for making this!

Hi @perfectra1n
Thanks for the very detailed report - I can see what the problem is. I will try to push a fix later today.

I pushed a small fix. Let me know if it works now :)

Awesome, it works perfectly now. Thanks so much! Now I can get those sweet, sweet logs into Prometheus 😆


[7.x] Default value for optionals

This will allow default values to be defined for optional() objects' methods or properties. Such as:

optional(null)->default([])->posts() will return []
optional(null)->default(5)->count will return 5

instead of null which is the existing behavior.
This will cause BC break for the existing objects that already have default() method so it should probably go to the 7.x if it is approved.

I think it would be nicer to be like this...
optional(null, [])->posts() // returns []

optional(null, 5))->count // returns 5

Just my 2 cents

What about the 'optionable' has a method called 'default'?

I think it would be nicer to be like this, similar to the old() helper...
optional(null, [])->posts() // returns []

optional(null, 5)->count // returns 5

Just my 2 cents

This would be great actually. However the existing optional() function's second argument is the callback to be called over the existing object. Changing the role of the second argument will probably cause confusion. Adding the third one is the option but in this case the second one needs to be passed every single time default is needed.

What about the 'optionable' has a method called 'default'?

This is the part where the BC break happens. User needs to be aware of the optional()'s behavior

This can go to 6.x branch. It isn't breaking.

This would be great actually. However the existing optional() function's second argument is the callback to be called over the existing object. Changing the role of the second argument will probably cause confusion.

Could check the second argument is an instance of Closure and if not, return the specified value.


nixosTests.netbird: fix after module update

Description of changes
Fixes test failure after https://github.com/NixOS/nixpkgs/pull/246055

Things done

Built on platform(s)

[X] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[X] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[X] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

@ofborg test netbird


can't reach claimed performance on LLaMA 7b

Hi I'm running LLaMA 7b using python script in benchmark folder on H100-SXM and got the following result:

[BENCHMARK] model_name llama_7b world_size 1 num_heads 32 num_kv_heads 32 num_layers 32 hidden_size 4096 vocab_size 32000 precision float16 batch_size 64 input_length 2048 output_length 128 gpu_peak_mem(gb) 74.34 build_time(s) 208.28 tokens_per_sec 1857.9 percentile95(ms) 4412.048 percentile99(ms) 4412.048 latency(ms) 4409.291 compute_cap sm90

throughput is 1857.9, but in performance.md, it's 2,058 tokens/s.  about 10% gap
My running command is:
python benchmark.py  --enable_fp8 --fp8_kv_cache --max_input_len 2048 --output_dir engines/llama_7b \     -m llama_7b \     --mode plugin \     --batch_size "64" \     --input_output_len  "2048,128"
GPU utilization:

Thanks for reporting this, and we are confirming with our internal team doing the benchmark for the reported perf number.
When we get more details, we will reply here.
June

Hi @HikariTJU we have published explicit doc / repro for our benchmarks here. Can you please take a look at those & give them a try?
Note that the python runtime currently isn't up to par with C++ performance. We are working on a "best practices" doc to help with benchmarking.

Hi @ncomly-nvidia @juney-nvidia
I noticed build args in the doc doesn't use gemm plugin, can you explain what that is and why it's enabled here?
In my test it will make a lot difference on final perf

TensorRT-LLM is built on TensorRT, which is a general purpose compiler that supports arbitrary layers. It also allows users to specify a kernel to execute for a given layer - these are called plugins. TensorRT-LLM lets the user choose if they want to use a plugin or the default TRT implementation for a layer based on these flag. In general, we only provide a plugin if it is faster than TRT's default, but TRT is constantly improving performance.
Script above is an explicit reproduction for our results, & a general best practice. You're welcome to experiment with the plugins & see for yourself which implementation is faster for your networks!
Closing this for now - feel free to reopen if you'd like!


More transaction metadata

/transactions/:id currently reports the inflow, outflow, and feePerByte in addition to the raw transaction. Those things are nice, but having the block height, block id, and timestamp would be far more useful.
This shouldn't be too tough to implement. wallet.ProcessedConsensusChange turns a consensus change into a flat []types.Transaction, so that type would just need to be changed to include the block-specific metadata. Then the implementers of wallet.ChainStore would need to store this extra information.
The tricky part is handling future changes. It's not hard to imagine that we'll want to add additional metadata later. When we do, will all the existing stores need to run some upgrade code? Will some of their transactions end up with missing metadata? Not sure how best to handle this.

Implemented in https://github.com/lukechampine/us/commit/f35d97a677d6f91052f3f642d10db6f52e18ccf2 and https://github.com/lukechampine/walrus/commit/6625a86126d0cc42ff65b9cc0badd14cac144b4d


Add inverse transformation into predict method of pipelines

Before submitting (must do checklist)

[x] Did you read the contribution guide?
[x] Did you update the docs? We use Numpy format for all the methods and classes.
[x] Did you write any new necessary tests?
[x] Did you update the CHANGELOG?

Proposed Changes
Look at #1295.
Closing issues
Closes #1295.

Codecov Report

Merging #1314 (ec536bb) into master (7e54706) will decrease coverage by 82.14%.
The diff coverage is 0.00%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@            Coverage Diff             @@
##           master   #1314       +/-   ##
==========================================
- Coverage   88.83%   6.69%   -82.14%
==========================================
  Files         192     203       +11
  Lines       12188   12499      +311
==========================================
- Hits        10827     837     -9990
- Misses       1361   11662    +10301

Impacted Files
Coverage Δ

etna/pipeline/mixins.py
0.00% <0.00%> (-99.16%)
:arrow_down:

... and 196 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Code coverage support in binaries

Description
Code coverage support in binaries
Fixes https://issues.redhat.com/browse/CCXDEV-10585
Type of change

New feature (non-breaking change which adds functionality)
This change requires a documentation update
Documentation update

Testing steps
Use the new Makefile target make build-cover
Checklist

[ ] make before_commit passes
[ ] updated documentation wherever necessary
[ ] added or modified tests if necessary
[ ] updated schemas and validators in insights-data-schemas in case of input/output change

Codecov Report
Patch and project coverage have no change.

Comparison is base (9015637) 67.59% compared to head (93056a4) 67.59%.

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #1020   +/-   ##
=======================================
  Coverage   67.59%   67.59%
=======================================
  Files          24       24
  Lines        3336     3336
=======================================
  Hits         2255     2255
  Misses        838      838
  Partials      243      243

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Lodolfo's pull request

Attempting the challenge to create a pull request to the RW/rwTODOs project. Oh my!

I could not add Sam as the reviewer, since the options were not available to me. Perhaps there were changes to GitHub since the video was recorded?

Hey @lodolfo—congrats on submitting a PR at the end of the git course. Sorry you were unable to add me as a reviewer—I didn't realise when I recorded it that it's not possible to select a specific reviewer unless you're part of the organisation. I hope that you enjoyed completing the course and learnt a few things along the way.
If you weren't already using git for your code, hopefully this has inspired you to do so. I hope that you enjoy the "Mastering Git" video course as well—you'll soon be able to get git to bend to your will :)
You can now wear this #GitWarrior badge with pride—and Tweet your historic victory!

sam