Wrong FBSDK version fetched with pod install

Here is a simple Podfile which I created for testing purposes on a clean project:
# Uncomment the next line to define a global platform for your project
platform :ios, '9.0'

target 'testSticker' do
  use_frameworks!
  pod 'FirebaseUI', '~> 5.0'

end

When I run pod install I see the following output:
Installing Bolts (1.9.0)
Installing BoringSSL (10.0.6)
Installing FBSDKCoreKit (4.39.0)
Installing FBSDKLoginKit (4.39.0)
Installing Firebase (5.14.0)
Installing FirebaseAuth (5.1.0)
Installing FirebaseAuthInterop (1.0.0)
Installing FirebaseCore (5.1.9)
Installing FirebaseDatabase (5.0.4)
Installing FirebaseFirestore (0.16.0)
Installing FirebaseStorage (3.0.3)
Installing FirebaseUI (5.2.2)
Installing GTMSessionFetcher (1.2.1)
Installing GoogleSignIn (4.4.0)
Installing GoogleToolboxForMac (2.2.0)
Installing GoogleUtilities (5.3.6)
Installing Protobuf (3.6.1)
Installing SDWebImage (4.4.3)
Installing TwitterCore (3.2.0)
Installing TwitterKit (3.4.2)
Installing gRPC-C++ (0.0.5)
Installing gRPC-Core (1.14.0)
Installing leveldb-library (1.20)
Installing nanopb (0.3.901)
Generating Pods project

As you can see, it fetches FBSDKCoreKit 4.39.0 even though in the FirebaseUI Podfile it states that the version should be 4.35.0.
I only noticed it now because 4.39.0 has a bug which broke the FB login functionality. However, I am also worried that in the future I might run into similar issues.
Am I doing something wrong?
My pod --version is 1.5.3

Thanks for pointing this out - just wondering why I can't login anymore...

@mwawrusch yes, it is really frustrating. Especially the fact that the guys at FB still haven't submitted a new release which fixes the issue even though they already have a commit which addresses it in their repo! So, we are stuck with Firebase pod not processing correctly and fetching the latest version of FBSDK instead of 4.35.0 + FB not releasing an urgent patch :(

Sorry about this all. Restricting the dependency version of the Facebook SDK in our podspec is technically a breaking change, so we haven't done so yet. Our next change is a major version bump, though, so this fix will be released with 6.0.

@morganchen12 thanks for the update.

 inherit! :search_paths
 # Pods for Facebook Auth
 # These are pinned to 4.35.0 to work around this bug:
 # https://developers.facebook.com/support/bugs/242258916492125/?disable_redirect=0
 pod 'FBSDKLoginKit', '= 4.35.0'
 pod 'FBSDKCoreKit', '= 4.35.0'```

I thought this was included to restrict the version of FBSDK to 4.35.0?

Do you know approximate timeframe when 6.0 will be released\\\/

It's in our Podfile so that this project doesn't break, but it's not in our Podspec so the change isn't propagated to projects depending on FirebaseUI. I'm aiming to release FirebaseUI 6 by the end of the month.

You can pin the version in your own Podfile by copy-pasting the same lines from the Podfile in this project.

@morganchen12 thank you for the suggestion, it works!

This helped me too. Thanks!

Hey all, the release didn't happen at end-of-month as planned. It'll take at least another week--some of our testing infrastructure broke that I haven't gotten around to fixing. Sorry for the delay.

This issue has seemingly reappeared. I installed the pod FirebaseUI/Facebook which pulls in the firebaseloginkit 4.4.1 (I'm recalling the version from memory since I am at work and my project is at home); after which I opened the project via the firebase workspace file, and I get "arc semantic" errors in one of the facebook header files.
So this indicated to me that something was completely broken. After reading this thread I figured I try and manually install the facebookloginkit pod and remove the FirebaseUI/Facebook pod. The version for facebookloginkit was now 5.0 and my errors in the library headers are now gone.
any workaround for this if you still want to leverage the FirebaseUI pod? Or any updates if there is a current fix for this would be great? Or if I am taking crazy pills and somehow this is user error, let me know.

See https://github.com/firebase/FirebaseUI-iOS/issues/673 -- FBSDKLoginKit isn't correctly restricting the version of FBSDKCoreKit.


Add field for faction to cards

Most strategems and similar cards are often locked to a faction, and tend to include this in their text (a la "FACTION - Battle Tactic Stratagem"), and this doesn't currently fit neatly into the template but would be very useful.

For the cards I've created, I've used the Card Header input for this.
Could you show me an example of what you would like?


Where do I find settings so I can customize breaks, etc?

Prerequisites

[x] I'm using latest version: v
[x] I've checked Known issues

Description
I have tried right-clicking on the Stretchly icon in my system tray and in the start menu and on the desktop, but there is nothing other than "Stretchly" and "Open" as options that might allow me to change break durations, types, etc. When I right click either of those, nothing happens. Reminders do appear every few minutes, but I would love to customize them a little. :-) I have v21.1 or similar (not v20 ish) and am using Windows 7 on a laptop. Can you help me?
Operating system:
Steps to Reproduce
I have tried right-clicking on the Stretchly icon in my system tray and in the start menu and on the desktop, but there is nothing other than "Stretchly" and "Open" as options that might allow me to change break durations, types, etc. When I right click either of those, nothing happens. Reminders do appear every few minutes, but I would love to customize them a little. :-) I have v21.1 or similar (not v20 ish) and am using Windows 7 on a laptop. Can you help me?
Expected behavior: [What you expect to happe]
Actual behavior: [What actually happens]
Reproduces how often: [What percentage of the time does it reproduce?]
Additional Information
Any additional information, configuration or data that might be necessary to reproduce the issue.

I have tried right-clicking on the Stretchly icon in my system tray and in the start menu and on the desktop, but there is nothing other than "Stretchly" and "Open" as options that might allow me to change break durations, types, etc. When I right click either of those, nothing happens. Reminders do appear every few minutes, but I would love to customize them a little.  :-) I have v21.1 or similar (not v20 ish). Can you help me?

Hi, you should look for the Stretchly icon in your tray area. Then, depending on your platform you can right/left-click to open Menu:

Then click on "Settings"

OHHHHHHH!! I tried to do that on every icon EXCEPT the one in that darn system tray before! Thank you for your help and your quick reply!! I found the system tray icon and got to the settings by right-clicking on THAT one! YAY!

Awesome, glad that helped :)


Fixed issue undefined not found in Flyfile

Problem with isPlainObject method that was set to negative. Also made a bit "safe" type checking as Object.prototype.toString could be easy rewritten

Seems like lots of features depend on that kind of typo, that's why test fails
For example

Fly.prototype.source = function () {
	var globs = flatten([].slice.call(arguments))
	var options = globs.pop()

	// if options is not object push back
	if (isPlainObject(options)) { // this not really object checking, what it's actually
// expect is an opposite value
		globs.push(options)
		options = {}
	}

	var files = globs.map(function (glob) {
		return expand(glob, options)
	})

	assign(this, {
		_: {
			filters: [],
			globs: globs,
			files: Promise.all(files)
		}
	})

	this._.cat = undefined
	_('source %o', this._.globs)
	return this
}

And so on. Im going to look on this tomorrow

@hzlmn I just got home. I'm taking a look now :)
Btw, tests are failing because of linter rules.

@hzlmn I've got a handle on it. I'll accept the PR right now to get you in here, but changes to come.
Thanks!


Refactored knockout components

Previous Knockout component registration code was complicated since union types did not exist in TypeScript prior to v1.4.
The current knockout.d.ts file has already had changes for union types added, so I have refactored my original changes for components to use this. Also amended version for KO mentioned since v3.2 is no longer beta.

@borisyankov @Igorbek @moonpyk @mariusschulz could you review this PR?

Great job @conficient ! Looks very good.


README: Editor integration: Vim section, add Neomake

A bit of an overview. Neomake's Go support supports running and reporting errors from Go compiler, go vet and golint. Recently https://github.com/neomake/neomake/pull/795 was merged to support gometalinter.
By default, it only runs a small subset of linters, --disable-all --enable=errcheck --enable=gosimple --enable=staticcheck --enable=unused. This can be customised in your .vimrc:
let g:neomake_go_gometalinter_args = ['--disable-all', '--enable=gosimple', '--enable=unused', '--enable=misspell', '--enable=staticcheck', '--enable=interfacer']

To run Neomake on save:
autocmd! BufWritePost * Neomake

So, Neomake will report compiler errors, vet errors, golint issues and anything you want from gometalinter. But if there's a compiler error, I've found it more useful to just report those before running the linters. You can do this with:
let g:neomake_serialize = 1
let g:neomake_serialize_abort_on_error = 1

As gometalinter will still run its checks in parallel, running them serially has only a very small cost but the benefit of just seeing the compile errors only and ignore the sometimes superfluous errors reported by the linters when there's a compile error.
Neomake can also report the error count in Airline which is useful too.

Thanks!

JFI: you could use the following already (to make Neomake's go maker (go test -c) abort the following makers (which includes gometalinter) in case it fails:
let g:neomake_go_go_serialize = 1
let g:neomake_go_go_serialize_abort_on_error = 1

https://github.com/neomake/neomake/pull/1213 is about enabling this by default.


Method for obtaining the Alpha value with more decimals

Hi! I'm currently trying to implement this library in a visual studio code extension. It works pretty well, the only issue that I found is that when you parse a HEXA color, and then format it back to HEXA, due to the rounding to the Alpha value, #11223350 turns into #1122334F
Example code:
const colorRaw = '#11223350'
const color = new ColorTranslator(colorRaw);
console.log(color.HEXA);                       // #1122334F

Relevant code:
// Public alpha property
public get A(): number {
  return round(this.hsl.a, 2);
}

I would like to know if you know any roadblocks in order to fix this. I'm willing to contribute if necessary

Hi @jeronimoek,
Thanks for reaching out. I will take a look as soon as I can.
Of course, contributions are always welcomed!
Regards.

Ok, nice! Later I'll give it a try.
Regards.

Hi @jeronimoek,
The issue is solved, you can try the version 1.10.2 of the package.
Regards and thanks one more time for reaching out to fix an issue.


Oracle Java: No source code found for Java class

System information:

Windows 10
DBeaver 7.0.4

Connection specification:

Oracle <IP_ADDRESS>.0
Oracle
No tunnels or proxies

Describe the problem you're observing:
I can see all Java classes in the tree. But when I open some of them I only see: "No source code found for Java class"
Steps to reproduce, if exist:
Open tha Java node and click on a Java class
Include any warning/errors/backtraces from the logs
No warnings or errors in the logs

The problem seem to be the name of the Java code.
For example "ch/demo/Rtf2Image"

The problem is that you are using SOURCE column of *_JAVA_CLASSES but you must use NAME instead. That's the name you use when selecting the data from *_SOURCE

Thanks for the bug report and the details

Fixed by #8725

verified


Label value near bar ( on top if the bar are vertical, right if they are horizontal ): how?

Label value near bar ( on top if the bar are vertical, right if they are horizontal ): how?

I started out with this issue: https://github.com/gionkunz/chartist-js/issues/281
And made a plug-in out of it: https://codepen.io/martino/pen/mVgyOZ

Actually I prefer getting the prefix and suffix from the html placement, in a data-attribute like data-chart-prefix. But that has nothing to do with the label placement, although it mixes because labels use those prefixes. Even better would be something like a whole dynamic label as a data-attribute.

There's also this plugin: https://github.com/Remco75/chartist-plugin-barlabels

@Martinomagnifico you should make it into a plugin.
@gionkunz That doesn't work properly versus the one @Martinomagnifico posted.

I leave it up to you guys, use @Martinomagnifico s snippet or make it into a plugin


CHANGELOG missing

Hi,
as a true fan of this gem I welcome noticing the regular updates. What do you think of adding a CHANGELOG to the file so people can keep track of all the changes.
Tracking changes is a little complicated right now, you bascially have to check the git log. My update process currently includes just updating blindly and checking if anything is broken (additions of new checks etc).
A good starting point of how to organize / work with a CHANGELOG is expained at http://keepachangelog.com/.
WDYT?

@nTraum I do agree, just added :-)

:+1:


Visualization of deformable attention reference points

Could you please publish the code for visualizations like in Figure 6 in the paper, if you still have this snippet?
Thank you!

have you gotten results?

I've found an obscure repo with an example of this https://github.com/duongnv0499/Explain-Deformable-DETR/, but haven't tried it yet

Have you figure out how to draw this attention map correctly? Thanks @vadimkantorov

I've found an obscure repo with an example of this https://github.com/duongnv0499/Explain-Deformable-DETR/, but haven't tried it yet
Have you figure out how to draw this attention map correctly? Thanks @vadimkantorov

Have you figure out how to draw this attention map correctly? Thanks

Waiting for an update!

Hey,
did you manage it in the end?
I am trying to do it for a DINO which uses the attention mechanism swell :)

Have you figure out how to draw this attention map correctly? Thanks @vadimkantorov  @GivanTsai

Hey, did you manage it in the end? I am trying to do it for a DINO which uses the attention mechanism swell :)

Can you do it? I'm also stuck on the Attention visualisation!

I did it like this, but it's kinda hacky: If you want to visualise it you'll need the reference points, where the model is attending to.
Simple hooks in the PyTorch model were not sufficient, as they only extracted the layer weights.
Therefore I modified the layer attention and pushed the locations into a global list (make sure to detach them from your gpu). This list, I then visualised. Depending on the model you'd also have to export the indizes of the top k points that were mapped to the actual detections. Otherwise, the attention is visualised for the wrong objects.
I hope this helps, feel free to ask tho.

I did it like this, but it's kinda hacky: If you want to visualise it you'll need the reference points, where the model is attending to.
Simple hooks in the PyTorch model were not sufficient, as they only extracted the layer weights.
Therefore I modified the layer attention and pushed the locations into a global list (make sure to detach them from your gpu). This list, I then visualised. Depending on the model you'd also have to export the indizes of the top k points that were mapped to the actual detections. Otherwise, the attention is visualised for the wrong objects.
I hope this helps, feel free to ask tho.
Thank you for your reply.
I also have some questions for you, I am using the dino detection model in the mmdetection framework, and I would like to use this to visualise it, I can now get the reference_points and sampling_locations, but it is a bit difficult to visualise this, what do you mean by the locations and indizes in your reply, and if possible, can you provide the code for your visualisation, thank you very much. What do you mean by locations and indizes in your reply, and if possible, could you provide me with the code for your visualisation, thank you very much!

If you look at dino architecture, you will find a top k query selection as not all 900 queries are outputted on decoder side, but only 300. (https://arxiv.org/abs/2203.03605) Based on your confidence threshold you are probably going to output less than 20 or so.
Further, try to plot it separately first and then try to match colours with the respective objects. I can't provide you code, since I don't have repo access anymore and also I used detectron2.


Adding an argument to gettz()

Hi! I was going through some patches for zoo that are present in pkgsrc, to see if they are still needed or not. Many changes relate to removing duplicate declarations of standard functions, and including the appropriate standard header instead. Many of those seem to be left. But of course I got stuck in the third file or so that I looked at with a less trivial change.
There was a patch that changes the body of tzadj() to
void tzadj(direntry)
struct direntry *direntry;
{
	long diff_tz;
	long longtime;
	long t;

	if (direntry->tz == NO_TZ)	 /* none stored */
		return;

	t = mstonix (direntry->date, direntry->time);
	diff_tz = (long) direntry->tz * (3600/4) - gettz(t); /* diff. in seconds */
	longtime = t + diff_tz; /* adj tz */
	mstime(longtime, &direntry->date, &direntry->time);
}

The main difference is that gettz() gets an argument. Presumably so that it can calculate the time zone offset related to that particular time, and not that of the current time. That sounds sensible to me.
However in the same patch set I didn't find anything to add this argument to the existing gettz() functions... which is a bit weird.
Since I didn't want to invent new things with this effort, but just contribute still sensible existing patches, I'm bouncing this one to you. It probably makes sense to incorporate this change and create the properly changed gettz() too. And it also likely makes sense to remove the duplicate versions of that function and just settle on one version that simply works for all variants...

Another patch related to this:
$NetBSD: patch-ag,v 1.2 2009/04/25 23:46:47 gdt Exp $

--- zooadd2.c.orig	1991-07-20 01:38:10.000000000 +0200
+++ zooadd2.c
@@ -258,12 +258,15 @@ void newdir (direntry)
 register struct direntry *direntry;
 {
 #ifdef GETTZ
+	long mstonix();
 	long gettz();
+	long t;
 #endif
    direntry->zoo_tag = ZOO_TAG;
    direntry->type = 2;                  /* type is now 2 */
 #ifdef GETTZ
-	direntry->tz = gettz() / (15 * 60); /* seconds => 15-min units */
+	t = mstonix (direntry->date, direntry->time);
+	direntry->tz = gettz(t) / (15 * 60); /* seconds => 15-min units */
 #else
    direntry->tz = NO_TZ;                /* timezone unknown */
 #endif


docs: correct typo and fix phrasing in docs

Motivation
I found a typo and awkward phrasing in docs.
Modifications

Correct typo in the word.
Fix pharsing in the sentence.

Commit Convention Rule

Please commit your modification based by conventional commit:

Commit type
Description

feat
New Feature

fix
Fix bug

docs
Documentation only changed

ci
Change CI configuration

refactor
Not a bug fix or add feature, just refactoring code

test
Add Test case or fix wrong test case

style
Only change the code style(ex. white-space, formatting)

chore
It refers to minor tasks such as library version upgrade, typo correction, etc.

If you want to add some more commit type please describe it on the Pull Request

Result

It doesn't affect others.

Closes

#{issue number} (If this PR resolves an issue.)

제가 한국어 Document에 신경을 많이 못 썼네요. 😢 확인해주셔서 감사합니다!


Add script to build and push docker images

woops, copied the wrong file! Updated with version that actually works.


[SPARK-17199] Use CatalystConf.resolver for case-sensitivity comparison

What changes were proposed in this pull request?
Use CatalystConf.resolver consistently for case-sensitivity comparison (removed dups).
How was this patch tested?
Local build. Waiting for Jenkins to ensure clean build and test.

Test build #64284 has started for PR 14771 at commit 7d86c57.

Test build #64284 has finished for PR 14771 at commit 7d86c57.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/64284/
Test PASSed.

LGTM - merging to master. Thanks!


Use require.resolve() to locate livereload

Should fix problems with npm@3 and its "flat" node_modules.

Thanks!

Thanks for this @benelsen!
This should probably get a release before npm@3 will become default and livereload gets broken.

FYI, npm@3 is now the default and this fix still hasn't been released.

@shama / @mklabs ...as per @Rowno's comment, could the patch please be published for npm?

:+1:


Issue: Jamf Pro Policy Install - Passed Parameter API Creds Plain Text Exposed in Policy

Using Jamf Pro here.
Passing paramaters in thescript to deploy super is great, however exposes the API creds in the policy.
And at present, due to another issue (API permission requires Computers > Create/Read) is somewhat of a security hole.
Issue: API - Computers Create and Read Removed - Super doesnt run
https://github.com/Macjutsu/super/issues/36

I added a piece to the script to use the encrypted strings to pass an encrypted version of the password. It might be useful if we could get this functional permanently added to the script to be more secure.

It's my understanding that the create and read permissions are needed to acquire the computer's jamf pro ID. Couldn't we avoid needing to reach out to the jamf pro API to get that information by piping the jamf recon binary into awk to grab the ID that gets printed at the end?
something like:
jamf recon | awk -F ">" '{print $2}' | awk -F "<" '{print $1}'
should return the computers jamf pro ID and avoid the need to do an API call for that info.

@blakeusblade @iDrewbs I am not a fan of encrypted strings, as it adds complexity without providing any real security value. You either have a secret visible in Jamf Pro (where arguably only your trusted administrators should have access) or you put different clear text secrets (hash/salt) hard-coded in to the super script. Remember, the super script is "permanently" installed on the local Mac drive, thus your hash/salt secrets will literally be knowable by anyone with super installed.
@rchase254 I am aware this is likely a better method, but at this point for super v3.0 I'm focused on support for full upgrades. That being said, I do plan to implement this in a future version of super but I need to make sure it's backwards compatible with the current method to provide the JSSID in the Config Profile.


Listing just sits there on 'Submitting', after the tx was signed

I used unisat on taproot. I signed the transaction and the signed version appeared in the box. Then I clicked the 'List inscription for sale' button, and it just sits there on 'Submitting'. I saw bug https://github.com/orenyomtov/openordex/issues/82 so I then tried PW2PKH but I got the same problem that's in that bug.

I just fixed the nostr relay, it had an expired SSL certificate, does it work now?


create submission of B5

rejected:B5
reason:account address not submitted, cannot verify on-chain baker update transactions

rejected:B5
reason:account address not submitted, cannot verify on-chain baker update transactions


Improve timing messages

Could the timing messages be made more human-readable? For example:
18:31:40.369 INFO eynollah - Enhancing took<PHONE_NUMBER>660736s
19:01:28.031 INFO eynollah - Textregion detection took 1787.6620445251465s
19:01:36.604 INFO eynollah - Graphics detection took 8.571088552474976s
19:08:15.645 INFO eynollah - textline detection took<PHONE_NUMBER>6735535s
19:26:32.451 INFO eynollah - deskewing took 1096.8060252666473s
19:26:33.040 INFO eynollah - detection of marginals took 0.5885534286499023s

All those only need 1 digit precision after the decimal point.

#64 should improve this

Example output now:
17:07:38.678 INFO eynollah - Enhancing took 20.6s
[...]
17:20:56.378 INFO eynollah - Textregion detection took 797.7s
17:21:11.233 INFO eynollah - Graphics detection took 14.9s


ParseError

is the parse error you were referring to in your description "ParseError: header -- expected b'HEADER RECORD*******LIBRARY HEADER RECORD!!!!!!!', got b'\xd0\xcf\x11\xe0\xa1\xb1\x1a\xe1\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00>\x00\x03\x00\xfe\xff\t\x00\x06\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x01\x00\x00\x00'"
Potentially with custom bytes on the end there? If so, this library could use updating.

What kind of file are you parsing? Might it be a CPORT file?

it has the extension .xpt so no

It's strange that the header would be empty like that. Have you checked the nearby lines?
You could be using a SAS v8 or v9 XPT file, which is a different format. No one has asked for support yet, but you could be the first.

I assumed it was probably v8 (you could’ve had a v8... support) or v9. Support would be nice. I could help if you want. Do you know where the v8/v9 specs are?
Jason Owens
<EMAIL_ADDRESS>
On Oct 16, 2018, at 4:30 PM, Michael Selik<EMAIL_ADDRESS>wrote:
It's strange that the header would be empty like that. Have you checked the nearby lines?
You could be using a SAS v8 or v9 XPT file, which is a different format. No one has asked for support yet, but you could be the first.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

I found the differences somewhere a while back. It looks like I jotted them down in the v89.py file https://github.com/selik/xport/blob/master/xport/v89.py

BTW, I'm still toying with the project design. It's not set in stone if you think there's something better.

I'm going to close this as a duplicate of #10.


The default location for storing mdf local database files

In ASP.NET Core, the default location for storing mdf files is C:/users/username. But in ASP.NET, the mdf file is located in the App_Data folder under the project directory. I like this behaviour, because we can copy the entire project folder to another computer, and the project can still run. This is especially convenient when we ask students to submit their ASP.NET projects for marking. We just ask them to zip their entire project folders for submission. Then, we can then download their zip files and unzip and run.
However, with the new location at c:/users/username, the above method of asking students to submit their projects and then marking their projects will no longer work. So I strongly suggest to restore the default location to the App_Data under the project directory. This will provide great convenience to educators in teaching ASP.NET Core. Moreover, this maintains the consistency with previous ASP.NET.  Please advise. Thanks.

+1 for this issue. We also teach students ASP.NET Core at my organisation and require them to submit their work to a grading website with a ZIP of their website folder. This will be far easier if all files are located in the same directory for local websites. So far this has been a limiting factor in effectively and efficiently teaching the students using this method.

The .mdf files are part of LocalDB, which is is a SQL Server feature, not ASP.NET Core specifically. The Entity Framework team may know how to change the default location SQL Server uses (cc @divega @ajcvickers), but I'm not sure such an option is easy to find.
@ws4u @KevinGrieveDesign  your scenarios actually seems like a really good candidate for using SQLite instead of SQL Server. SQLite is a serverless database provider which works on macOS, Linux, and Windows unlike SQL Server which is Windows only. SQLite databases are stored in a file, and unlike LocalDB, it's easy to control the file location of the SQLite database files. See https://docs.microsoft.com/en-us/ef/core/get-started/netcore/new-db-sqlite for samples on using SQLite.

As far as I remember the way this worked in past versions of ASP.NET relied on connection strings with AttachDbFileName and |DataDirectory|. I can’t remember right now if |DataDirectory| is used in SqlClient for .NET Core, of if ASP.NET Core sets it.
Cc @bricelam who may remember.
Anyway, that caused a number of issues related to expectation that LocalDB would work as an embedded database, when it actually isn’t one. For example, directly deleting the files would cause errors hard to recover from.
Using a real embedded database like SQLite as @natemcmaster suggest might be a better solution for this scenarios.
PS: SQL Server isn’t for Windows-only anymore (and Nate knows it very well :smile:).

As far as I remember the way this worked in past versions of ASP.NET relied on connection strings with AttachDbFileName and |DataDirectory|. I can’t remember right now if |DataDirectory| is used in SqlClient for .NET Core, of if ASP.NET Core sets it.

#throwback https://referencesource.microsoft.com/#System.Web/HttpRuntime.cs,346
ASP.NET Core does not set this.

PS: SQL Server isn’t for Windows-only anymore

@divega good point, I should have been clearer. Microsoft SQL Server runs on Linux and Windows, but LocalDB is a feature of SQL Server which only runs on Windows. For educators that want to teach students to use a "real" database server, Docker is a good way to run SQL Server on Linux. But for the purposes of submitting assignments with an embedded database, SQLite is seems like the most viable option here.

Thanks for pointing out SQLite.
For educators, we really need convenience. Otherwise, the passion of
students will decrease.
In the current Visual Studio 2017, when we create a database, the
default is an Express LocalDB. Also, when we teach ASP.NET Identity,
it also uses an Express LocalDB by default. Do we have an easy way to
modify these default behaviour to use SQLite instead?
I actually prefer that we can have a simple way to specify that the
location of the mdf file is App_Data. Is this achievable in VS 2017?
This is really a headache when we switch to teach ASP.NET Core. Please
do help fix this problem.
--

Best regards,
Weisheng

We periodically close 'discussion' issues that have not been updated in a long period of time.
We apologize if this causes any inconvenience. We ask that if you are still encountering an issue, please log a new issue with updated information and we will investigate.


V3 - Promise API, lots of bugfixes, iOS deprecation fix, API moves to react-native-localize

Related issue tracking things: #307
Commits have the description as things happen

I won't merge this yet, but I will publish a react-native-device-info@next build from it
I expect there are bugs, as I have it running on android and iOS now but I haven't checked the output of certain APIs yet (like memory size etc) to make certain everything is the same
This let's people review though
All review / thoughts are welcome

This is released.
If anyone wants to try v3.0.0-beta.1 of react-native-device-info  is up tagged on npm as @latest - it's a big ol' breaking change because instead of making your app startup really slow (like .6 seconds slower than it would otherwise) by loading everything in constants in init, it's all Promises now. It also evicts the deprecated WebView stuff that causes App Store warnings. I would especially love a Windows tester, I don't even have a test environment there so I just hacked it and prayed https://github.com/react-native-community/react-native-device-info/releases/tag/v3.0.0-beta.1

Pulled 3.0.0-rc.1 into my app– after adjusting the few places I'm using it to expect promises everything is working as intended. 🙂👍

Excellent! Thanks for reporting in @chrisheninger I really appreciate it. I'm having much the same experience - seems to be working fine but I have a bit of app-bootstrapping re-organization to do in order to handle the Promise's async-ness vs my need for concrete answers. That's to be expected though
Unless I hear from anyone else I will likely publish rc.1 either as-is or just with documentation changes within a day or two, just want to finish fully integrating in my work project and triple-verifying everything first
Cheers

Not sure where it belongs (maybe just in this PR is sufficient)– but it might be a good idea to leave some documentation/examples on how to use the library now that it's promise-based.
I initially ran my project after updating (without changing any of my existing code) and some of the render errors that threw as a result were a bit confusing/cryptic. 😅
Below are a couple examples I threw together– I didn't run them but I think they're correct.
Example using hooks:
import React, { useState } from "react";
import DeviceInfo from "react-native-device-info";

const App = () => {
  const [versionNumber, setVersionNumber] = useState("");

  useEffect(() => {
    DeviceInfo.getVersion()
      .then((version) => {
        setVersionNumnber(version);
      })
      .catch((err) => console.error(err));
  }, []);

  return (
    <View>
      <Text>Your app is running version {versionNumber}</Text>
    </View>
  );
};

export default App;

Example using class component:
import React, { useState } from "react";
import DeviceInfo from "react-native-device-info";

class App extends Component {
  constructor(props) {
    super(props);

    this.state = {
      versionNumber: "",
    };
  }

  componentDidMount() {
    DeviceInfo.getVersion()
      .then((version) => {
        this.setState({ versionNumber: version });
      })
      .catch((err) => console.error(err));
  }

  render() {
    const { versionNumber } = this.state;
    return (
      <View>
        <Text>Your app is running version {versionNumber}</Text>
      </View>
    );
  }
}

export default App;

It's important to note that with both of these examples– since we're now promise-based– will first render with empty string and then with the version number once the promise has been resolved. To prevent this from happening, the developer would need to have some sort of loading indicator rendering in place of the text if the versionNumber has not been set in state yet.
Hope that helps someone out. 🙂
Thanks for all the work you've done on this lib as well as jetifier @mikehardy– that upgrade from RN 0.59->0.60 was a bit rough and your explanations in various issues made everything much smoother. 👍

Good points all...most of my change is in my bootstrapper, sounds similar.
I already have an example App.js that shows general usage, if you wanted to do a quick PR that showed some alternate styles like you pasted here (clearly flagged as such like "hey, you might use it this way..." to get some of the info in App.js that would be great. Also, I just started a wiki page to document the transition: https://github.com/react-native-community/react-native-device-info/wiki/V2-to-V3-Migration-Guide
Finally, for bootstrapper example I think the right thing is to alter the index.js in the example here https://github.com/react-native-community/react-native-device-info/blob/v3/example/index.js#L9 so that prior to doing the AppRegistry.registerComponent it did the required DeviceInfo stuff and only did registerComponent in a .then() hanging off it - as I think that is the heart of bootstrapping in react-native apps? (that being: don't registerComponent until you have all your must-haves set up?)

and you're welcome :-), nice to hear the effort helped others. rn60 was a very tough upgrade...but pods and auto-linking - so much better!

I didn't see you had an example App.js– what you have in async componentDidMount is much more in-depth and does the job perfectly. 👍

3.0.0-rc.2 is out, with a huge addition - I broke down and added a xxxSync() version of each API.
While ingesting the v3 changes into my work project (which is partially synchronous, and depends on device info during bootstrap) it was very difficult to handle the fully asynchronous API. I was near to having it all working but it was a real mess and I thought I probably wouldn't be the only one having this difficulty.
 Use responsibly.
I expect this will be the final release candidate unless someone discovers a bug.
I am also still uncertain about Windows support. I have done my best there but I have no react-native-windows toolchains set up, so I was coding blind and haven't even attempted to compile it. Any help appreciated.

Just waiting on https://github.com/react-native-community/react-native-localize/pull/65 to merge now - once that's merged I'll release

The react-native-localize PR is merged, just waiting for release now


Added AGBChange as a processing option. Parameters are hardcoded and …

…need to be added to parameters

Could you please move your changes to develop branch instead of PR to master?


This library will stop working on June 21, 2024

Is this library still maintained? If so, Google deprecated https://fcm.googleapis.com/fcm/connect/subscribe (/send too), which is slated for full removal on June 21, 2024.
The reference library quoted in the README has a discussion about this at https://github.com/MatthieuLemoine/push-receiver/issues/68.
Official deprecation announcement: https://firebase.google.com/docs/cloud-messaging/migrate-v1

@coreybutler Thank you so much for the report, you saved me! :) In a few hours I'll release a new version using the new API.
If you want, there's a working version on branch I created called api_deprecation. I still need to update the usage example and add some parameters checks, and fix conventions and namings, but it generally works.
Now instead of SenderId, you need to provide a AppId, ProjectID, and the ApiKey (All can be obtained from sources (most likely strings.xml) of every android app).

@morhaviv I'll check out the branch if I can, but I suspect you'll have the new version released before I have a chance to. I'm looking forward to trying it out though!

@coreybutler I've released it :) I would appreciate it if you could try it and let me know if it works properly!


add gps support and gps feeder container

fixes https://github.com/eclipse-leda/leda-distro/issues/20

@d-s-e Could you please sync with the meta-leda upstream first?

@d-s-e Could you please sync with the meta-leda upstream first?

done.

GPSD related concerns have been addressed, things can stay as-is in the PR. Only thing left is: https://github.com/eclipse-leda/meta-leda/pull/178#discussion_r1303881633

LGTM


Uncaught (in promise) Error: Pica: cannot use getImageData on canvas, make sure fingerprinting protection isn't enabled

Hi!
I just tried the example found at https://example-pets.jazz.tools/ and did not even succeed to run it locally - see the following error log from my browser:
Uncaught (in promise) Error: Pica: cannot use getImageData on canvas, make sure fingerprinting protection isn't enabled

Additionally, I also could not open a websocket connection to your server(s) (as described in my previous issue).
Any idea how to proceed?

Hi @rozek, thanks for trying! Which browser/OS are you using?

Hello,
thanks for your response!
I am using macOS Ventura 13.6 with the latest Brave Browser Version 1.66.110 Chromium: 125.0.6422.60 (Offizieller Build) (arm64)

Are you by chance using Brave's "Strict fingerprinting protection mode"?

Similar to the other issue I mentioned above, I tried the example again today - and it worked now.
Could it be that the error I reported was just a consequence of the missing websocket connection?

I'd be surprised, because the image resizing is a completely local operation and should work/not work the same regardless of if you have a working connection to the sync server.
You didn't by chance update Brave in the meantime? (it sounded like they were working on exactly the fingerprinting strictness)

well, it could be that I updated Brave (as that happens quite often) but I can't tell you for sure.
Anyway, thanks a lot for your effort!


Add isort configuration file

Description
It seems there are a couple of potential conflicts between black and isort. Having is a .isort.cfg is one way we can resolve these conflicts easily.
How has this been tested?
I tested this with our new pre-commit hook and my own editor.
Checklist

[ ] I have followed the Contribution Guidelines and Code of Conduct
[ ] I have commented my code following the OpenMined Styleguide
[ ] I have labeled this PR with the relevant Type labels
[ ] My changes are covered by tests

Can't we do it like how they have it in PySyft?

Yes! We could. Good point actually! I'll change it.

Can't we do it like how they have it in PySyft?

Done


Python Interactive Restart Kernal moves working directory

VSCode Version: 1.47.0
OS Version: Windows 10.0.18362

Steps to Reproduce:

Open a python interactive terminal by Shift + Enter on a line of python code.
Import os and os.getcwd() displays the current location of current working directory

Restart the python kernal using the restart button at the top of the page and this changes the location of the current working directory back to 'C:\Users\USERNAME\AppData\Local\Programs\Microsoft VS Code'

I would think that people would prefer to stay in the current working directory. so that you can import modules.  This doesn't affect a workflow where you are constantly running code from the python file your working from.  But I was testing to load modules and check they were working and expected a restart of the kernal to keep me in the same working directory I was in.

Does this issue occur when all extensions are disabled?: No because it requires the python extension to run the python Interactive window

/extPython


validation is slower than it could be

Currently validation takes ~5-10 seconds before the site loads the geneset page after inputting or editing the geneset.
Move the data files needed for geneset validation into the web app local disk, which will be much faster than reading from cloud file share
Add a process in the deployment script to move these files from central  storage to the web app service local storage and set a configuration value pointing to the location for geneset validation files.

even after moving validation files to local disk, still at least 5 seconds.  So I added a spinner to the form to let the user know they have to wait a bit.


tensorflow TypeError when applying the GPU conv3p operator

I'm trying to use the GPU version of the conv3p operator, so I set the parameter "use_gpu" to true in the file "param.json". However, the following issue occurred when running the Python code "train_modelnet40_acsd.py":
/python3.5/site-packages/tensorflow/python/framework/ops.py TypeError: Using a tf.Tensoras a Pythonboolis not allowed. Useif t is not None:instead ofif t: to test if a tensor is defined, and use TensorFlow ops such as tf.cond to execute subgraphs conditioned on the value of a tensor.
It seems that this may not be a problem in the Python codes. Is there anything wrong with the GPU compilation, or I'm incorrectly use the codes?

When compiling the custom convolution operator, did you execute
./tf_conv3p_compile.sh -a
with the -a flag to activate atrous convolution?
The signature of the non-atrous and atrous convolution are different.
By default, the network model in train_modelnet40_acsd assumes atrous convolution.

Thanks!!! My neglicence.
Very interesting project and nice idea. I learn a lot from the CUDA codes.
👍


Fix tests

The current test always fails because it assumes that amfora -v returns only Amfora vx.x.x. That was the case with <1.4 I think.
Now I use a regex to check that Amfora, Commit and Built by are populated and the executable is present. It is less reliable (because I can't hard code the version) but works also on head.

The v prefix can be assumed actually, but thanks for the other parts of the test, I had noticed it failed on HEAD. Added this in #10.


Refactor Gateway Settings View(s)

Fixes https://github.com/subconsciousnetwork/subconscious/issues/677
This PR simplifies the experience of dealing with the gateway. If you do not have a gateway configured we show the provision section (with invite code input). If you do have a gateway configured we show the sync section.

@gordonbrander hmmm good point. I've been playing around for a bit and landed on this:

Which doesn't remove the initial error message from failing to sync with the default gateway, but it puts it one level deeper in the menu so you'll only encounter it if you go looking. You can't edit it while gateway provisioning is in progress, so on the expected onboarding journey you'd avoid seeing the error state.


Bug/fix share earnings

Depends on branch task/use-gnosisjs-estimations

Oops. I think I did the wrong branch again 😄 Next time you can create the PR with the dependant branch as the base. That way I only see the changes you did in your branch in relation to the depedant branch


Update examples with Extended

Gotta learn how to set up Documenter.jl and Literate.jl

[ ] Set up docs/ and build a skeleton website
[ ] Write Tutorials and a section of likelihood fit
[ ] Write extended likelihood fit
[ ] Put it on GitHub and share it with JuliaHEP and NTUHEP

These have been quite helpful:

https://stackoverflow.com/questions/41513597/how-do-i-access-the-wsl-linux-file-system-from-windows#:~:text=With Windows 10 version 1903 and later%2C WSL,may find that the \wsl%24 mount doesn't work.
https://stackoverflow.com/questions/49835559/access-a-web-server-which-is-running-on-wsl-windows-subsystem-for-linux-from-l

And this is a good example, in terms of simplicity: https://github.com/KristofferC/OhMyREPL.jl/tree/master/docs

Stuck by https://julialang.slack.com/archives/C66L48G1X/p1676122658091259

I'm not that interested in writing tutorials, actually. I will drop this aside after the docs generated by Literate.jl is good.


79-fix-the-link-errors-with-in-the-name

Fix "java.lang.IllegalArgumentException"
replace "/" with "%2F"

closing because this is integrated into one combined PR


Enum map without getting keys first in Guardian.Utils

The pull request did two things:

[*] Avoid fetching keys from map before enumerating map( map is enumerable)

[*] Do not stringify a map that has been stringified.

Thanks @secretworry!  It looks like Credo is failing, could you take a look at that?

@doomspork My fault. Removed an underscore by mistake. It works now:)

Thank you @secretworry 👍

@doomspork :)


Unreachable Code Preventing Short Circuit

While helping Montek with an error:

I discovered that this error which should be triggering when there's no commands in the README.md is unreachable:
https://github.com/davidtai/cli/blob/04a93c00750eb73bb35cd60a220ef42ffdcfe46a/src/app.exec.ts#L117
a check for } else if (args.length == 0) { is nested inside a check for if (env && args.length) { and therefore can never execute.  Enabling this error makes Montek's scenario fail gracefully, however it breaks other common scenarios.  More research is needed for a fix.

Here's a somewhat concerning scenario
# Getting Started

# sh

## hello

If you type in tea . then tea tries to execute . because # Getting Started is empty and triggers a os 13 error.  If you type in tea sh, it will execute sh as the # sh block has no command.

yeah tea . is possibly not sensible.
Maybe we need a character to indicate “target” since we are being a little too magical here. In theory there's some badness that can happen because we pass things through to the underlying shell but also interpret commands differently if they happen to be in a README.
It's a shame that tea #foo cannot work.

I'll intercept tea . and error if no exe/md region is found.

Possibly we should require tea . foo

That should address this.
On the extended conversation about how this feature should work.  I'm not opposed to magic so I think the signature is fine.  But I think it might be a good idea to add a simple preview prompt that displays what commands were found by tea and let the user pick what gets executed.
Not all getting starteds will be one liners.  For example it is common for node projects to have both npm, npx, and yarn commands:
https://github.com/facebook/create-react-app

we removed exe/md


feat(helm): add *.ingress.pathType to helm/values.yaml

:id: Reference related issue.
:pencil2: A description of the changes proposed in the pull request
:memo: Test scenarios
:computer: Add screenshots for UI
:books: Any other comments that will help with documentation
:man: :woman:@mentions of the person or team responsible for reviewing proposed changes
This is a nice example: https://github.com/gravitee-io/gravitee-access-management/pull/1822

@gutek9 PING

Hi @lucasfcnunes ,
Sorry for the late answer, can you please resolve conflict so we will be able to merge this PR ?
Thanks


Beginning should be spelt correctly.

It looks like beginning was spelt incorrectly.
/cc @nimbinatus

Is beginingoftext correct or should it be beginningoftext

@Mergifyio rebase


hack luoo.net using Google

Hello Peter,
I use Google-Search-API to hack luoo.net, because Xiami's built-in search engine doesn't work well in our case.
Best,
Yanmao

@Harry1993 Thank you for contribution.
Google services are always fail because google has been not accessible at China.
Your code works at China when using a proxy. people who use a proxy are few.
In my opinion, solving the xiami cookie authentication is the right way.


Consider supporting R.swift in dynamic frameworks.

As I understand it, R.swift can only be used in a project containing a target app, and doesn't support use in dynamic frameworks linked to a target app.
If I'm correct I believe this would be usefully described in the readme and I would be prepared to create a PR for this.
Long term: perhaps a move to using an R protocol and protocol extensions, or other strategies could be employed in supporting this feature.
Thanks.

You can use R.swift in multiple projects, by setting up a build phase for each project.
In my current setup, I have an iOS app with a R.generated.swift file. That project links to a different project that is a separate Cocoa Touch Framework.
The framework has its own R.generated.swift file, for its own resources.
Is this what you're referring to, or do you mean something else?

Although I can't use the library's resources from the app, because the R struct is internal.
If the generated code would be public, the app could simply refer to OtherFramework.R.image.someImage()

@tomlokhorst : thanks for this reply - it is what I mean.
I have experimented with a modified VIPER architecture with each part built in its own dynamic framework and all referenced by a seperate top-level target and project app. View/ViewController/Main.storyboard is in an AppnameView dynamic framework that is referenced by an seperate AppnameApp project. Setting the rootViewController in the AppDelegate becomes impossible using the Rswift R struct. Having the R struct made fully public would allow loading dynamic framework resources in the app and in playgrounds.
I do need to think a bit more about this, but perhaps making the R struct public may be all that is needed.

To play around with this, you can use this as a build phase. It replaces strings to add public modifiers:
"$PODS_ROOT/R.swift/rswift" "$SRCROOT/SomeProject"
sed -i -e 's/struct /public struct /g' "$SRCROOT/SomeProject/R.generated.swift"
sed -i -e 's/func /public func /g' "$SRCROOT/SomeProject/R.generated.swift"
sed -i -e 's/static let /static public let /g' "$SRCROOT/SomeProject/R.generated.swift"

If this works, it can be added it to the code generator. We'll have to investigate to see if there are unintended side effects for changing this previous internal struct to be public.

@tomlokhorst thanks for this workaround. The script is ingenious! It didn't quite work first time requiring the following (in the context of a Carthage + manual installation):
"$SRCROOT/rswift" "$SRCROOT"
sed -i -e 's/private //g' "$SRCROOT/R.generated.swift"
sed -i -e 's/struct /public struct /g' "$SRCROOT/R.generated.swift"
sed -i -e 's/func /public func /g' "$SRCROOT/R.generated.swift"
sed -i -e 's/static let /static public let /g' "$SRCROOT/R.generated.swift"
sed -i -e 's/let bundle /public let bundle /g' "$SRCROOT/R.generated.swift"
sed -i -e 's/let name /public let name /g' "$SRCROOT/R.generated.swift"

I'll play around with this and report back.

Allowing public access to the R struct looks like providing the necessary support for this use case. The script I'm using, however, does not scale, as I have to add individual items to the storyboard struct (e.g. sed -i -e 's/let storyPageController /public let storyPageController /g' "$SRCROOT/R.generated.swift"). This is because of the impossibility of replacing let with public let globally.
Adding this facility to the code generator would be awesome!

Note to self:
When we add this feature, we need to double check if we correctly load all resources via the hosting bundle.
For example, before https://github.com/mac-cain13/R.swift/pull/238 we didn't do that for Strings, maybe there's other resources that also rely on the default bundle.

I decided to start out with everything in the R struct internal, because it didn't feel right to make it public by default. The this is that if you create a library with a public resource you can't change any resource without potentially breaking depending projects. That didn't feel as a correct default.
That said, I think your use case @DanielAsher is a valid one, but I'm not sure if it is so common that it should change the default visibility of resources. I'm interested in what you all think about this;
Should the default visibility be changed to public or should this be some kind of setting? Or is there another option that we could explore?

I strongly believe that refactoring to use dynamic frameworks and the use
of playgrounds for REPL-based development are powerful techniques and
growing trends.
Could an alternative could be a command-line flag to Rswift, perhaps
--public? This would allow for the default internal to be maintained,
while allowing for these use cases.
On Wed, 24 Aug 2016 at 09:46, Mathijs Kadijk<EMAIL_ADDRESS>wrote:

I decided to start out with everything in the R struct internal, because
it didn't feel right to make it public by default. The this is that if you
create a library with a public resource you can't change any resource
without potentially breaking depending projects. That didn't feel as a
correct default.
That said, I think your use case @DanielAsher
https://github.com/DanielAsher is a valid one, but I'm not sure if it
is so common that it should change the default visibility of resources. I'm
interested in what you all think about this;
Should the default visibility be changed to public or should this be some
kind of setting? Or is there another option that we could explore?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/mac-cain13/R.swift/issues/245#issuecomment-241983739,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHjIIeNr3TrNXEGafT6TeqHsnZGieEdYks5qi_a9gaJpZM4JY_Hc
.

I agree that dynamic frameworks are the way to go, the only thing is not every dynamic framework is going to expose their resources to the outside world. :)
A --public flag could be an option. That keeps the default on internal. That is nice, it would be even nicer if we could come up with a solution that gives you control on what resources are public and what are internal. Not sure how that would look like, maybe a name convention or something else I'm not yet thinking about.

I've merged this feature into master and it will be available in the next R.swift release. Thanks for reporting your needs and thinking with us.
You can specify the access level you want the R struct and its nested structs/properties/methods generated on by passing the rswift binary the --accessLevel public flag. (You can also specify internal, fileprivate or private.)

very much looking forward to this!


CVE reported for netty-3.2.2.Final.jar in  conductor version v2.30.1

CVE reported for netty-3.2.2.Final.jar in  conductor version v2.30.1. (conductor-zookeeper-lock & test-harness)
Can you please provide the fix for CVE issue.?
CVE  detail -

CVE-2014-3488
The SslHandler in Netty before  3.9.2 allows remote attackers to cause a denial of service (infinite loop and   CPU consumption) via a crafted SSLv2Hello message.

CVE-2015-2156
Netty before 3.9.8.Final, 3.10.x  before 3.10.3.Final, 4.0.x before 4.0.28.Final, and 4.1.x before 4.1.0.Beta5   and Play Framework 2.x before 2.3.9 might allow remote attackers to bypass   the httpOnly flag on cookies and obtain sensitive information by leveraging   improper validation of cookie name and value characters.

--
--

CVE-2019-16869
Netty before 4.1.42.Final   mishandles whitespace before the colon in HTTP headers (such as a   "Transfer-Encoding : chunked" line), which leads to HTTP request   smuggling.

--
--

CVE-2019-20444
HttpObjectDecoder.java in Netty   before 4.1.44 allows an HTTP header that lacks a colon, which might be   interpreted as a separate header with an incorrect syntax, or might be   interpreted as an "invalid fold."

--
--

CVE-2019-20445
HttpObjectDecoder.java in Netty   before 4.1.44 allows a Content-Length header to be accompanied by a second   Content-Length header, or by a Transfer-Encoding header.

POODLE vulnerability in SSLv3.0   support
The SSLv3 support is vulnerable   to a POODLE attack. SSLv3 should be disabled pending implementation of   TLS_FALLBACK_SCSV by Oracle.

--
--

Please report security vulnerabilities through the Netflix Bugcrowd program.


Latex() writes class name in each variable

@whoburg when I call print M.latex() where M is a model, it prints out the name of the class as well, like this:
In [3]: print M.latex()
\begin{array}{ll}
\text{}
\text{minimize}
    & {W}_{GasPoweredHALE}\mathrm{~\left[ lbf \right]} \\
\text{subject to}
    & {P_{shaft}}_{GasPoweredHALE} = \frac{{C_D}_{GasPoweredHALE} {V}_{GasPoweredHALE} {W}_{GasPoweredHALE}}{{C_L}_{GasPoweredHALE} {\eta_{prop}}_{GasPoweredHALE}} \\

How can I get it to just print out the variables without the class name attached?

Have you tried adding
import gpkit
gpkit.settings['latex_modelname'] = False

to the top of the file defining M?
Also, minor note: future issues like this should probably be raised at gpkit not gpkit-models.

Yep that would fix it.  And yes I will be this in a gpkit next time.  Thanks!


Finite State Machine doesn't enter Walk state after Attacking

I'm submitting a bug probably. I am maybe wrong, but I tried using the fine state machine in my project and I got a bug where the walk animation wouldn't play if you held down walk keys before attack is finished. That didn't seem right and I thought i changed something poorly. But after I tested it in your example as well it is the same. It's hard to spot without actual animations.

[ x] Bug report.
[ ] Feature request.

What is the current behavior?
You never enter walk animation but you are able to move. So the walk animation is never played.
What is the expected behavior?
You will enter walk state after finishing the attack.
Tell us the steps to reproduce the bug, and if possible share a minimal demo of the problem.
Add print() to Walk state enter and to sword animation finished

The animation is bugged for me even after jumping is finished. The character just floats around in the jumping animation until I change state from Idle to move or the other way around. I would really appreciate it if someone would be able to fix that as I don't how.

I recommend checking these new demos. There's an updated state machine there, for which we also wrote a free guide:

Godot design pattern demos
Godot finite state machine guide

Thank you, your guides are the only thing that prevents me from falling my programing finals. I downloaded your demo from Godot itself (through templates) and I realized that in your code, you never actually enter the previous state after deleting "previous" from states_stack. So instead of this:
func _change_state(state_name):
	if state_name == "previous":
		states_stack.pop_front()
	else:
		states_stack[0] = states_map[state_name]

	current_state = states_stack[0]
	emit_signal("state_changed", current_state)

	if state_name != "previous":
		current_state.enter()

You need this:
func _change_state(state_name):
        if state_name == "previous":
		states_stack.pop_front()

	else:
		states_stack[0] = states_map[state_name]

	current_state = states_stack[0]
	emit_signal("state_changed", current_state)
	current_state.enter()

It works for your demo because, as said above, your animation stays always the same.


sudo yabai --load-sa not work on macos 13

Hi. I had the same problem. koekeishiya told me in a neighboring issue that when you write the command "brew install yabai", it installs the 5.0.1 release.
koekeishiya made changes to the master branch and hasn't done a release yet. So you have to install yabai with brew install yabai --HEAD to make it work correctly. But before that you need to create a certificate. Instructions: https://github.com/koekeishiya/yabai/wiki/Installing-yabai-(from-HEAD)
It didn't work right the first time but it worked. I combined the commands:
sudo yabai --load-sa
brew services restart yabai
Translated with www.DeepL.com/Translator (free version)

Getting this error on Ventura: "cannot focus space due to an error with the scripting-addition."

Get this error on mac os 13 Ventura,

I'm struggling with installing --HEAD. Without it, the scripting additions dont allow me to move windows to different desktops and follow them there, but with it, I'm seeing an Accessibility Access popup about every 20 seconds:

But its already enabled...

Did you manually add the yabai executable using the '+' button after installation, as per the instructions on installing from HEAD? That's what seemed to work for me (I say seemed as I also did not create a certificate using Certificate Assistant when I had your issue).

@wdylanbibb Thank you for your response. I hadn't followed those originally, but I just followed them and it resulted in the same issues, the Accessibility Access settings popping up every 8 seconds.
I'm also installing Yabai via Homebrew, if that matters?

Thank @wdylanbibb , I follow your suggestion to add yabai to grant list manually then start it. It works.

install the latest version (v5.0.2) and make sure you have followed the wiki instructions exactly as written.
If you still have issues read this comment for instructions on how to debug your setup: https://github.com/koekeishiya/yabai/issues/1515#issuecomment-1344070256

Working for me with v5.0.2. Thank you so much for the time you have invested in this project.