Fixed #28949 -- Fixed index name truncation for multibyte characters.

ticket-28949

buildbot, test on oracle.

buildbot, test on oracle.

I suspect that the code as-is handles chopping halfway through multibyte characters more correctly than just naively doing joined_column_names = joined_column_names.encode('utf-8')[0:other_length].decode('utf-8'), but I'm not sure I can tell from the tests, and because I'm only running the tests locally on SQLite I can't readily check the other backends...
I think my question is: what happens when the last glyph/grapheme/whatever in the trimming is a mb utf-8 char like an emoji? Does that get taken wholesale, or dropped (or chopped erroneously, like my back of the napkin thing above)? If it's taken wholesale, is that definitely always fine and never going to push over the limit (possibly, given it's tracking the working length)?
If the test is answering that and I'm just not grokking enough of it to understand that, well, sorry and my bad :)

Hey @kezabelle, thanks for digging in. Let me know if this sounds right.

I suspect that the code as-is handles chopping halfway through multibyte characters more correctly than just naively doing joined_column_names = joined_column_names.encode('utf-8')[0:other_length].decode('utf-8')

Indeed, no dice:
>>> mysql = 'I♥Django' * 4
>>> len(mysql)
32
>>> len(mysql.encode('utf-8'))
40
>>> mysql.encode('utf-8')[:12]
b'I\xe2\x99\xa5DjangoI\xe2'
>>> mysql.encode('utf-8')[:12].decode('utf-8')
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe2 in position 11: unexpected end of data

what happens when the last glyph/grapheme/whatever in the trimming is a mb utf-8 char like an emoji? Does that get taken wholesale, or dropped (or chopped erroneously, like my back of the napkin thing above)? If it's taken wholesale, is that definitely always fine and never going to push over the limit?

I'm intending the Oracle test to show that it gets dropped ("I" rather than "I♥D".) There the max length is 30, and it's at 28 without the three-byte heart. A comment might help?
>>> expected_result_for_oracle = 'indexes_a_c1_c2_I_67189ba7ix'
>>> len(expected_result_for_oracle)
28

because I'm only running the tests locally on SQLite I can't readily check the other backends...

I discovered it was simple to just temporarily fiddle with max_length a few lines above to mock the other constraints. But yes, this was finally the ticket to get me to clone django-docker-box 🤓

Edit: spitballing further, the following also passes on SQLite

OMG that snippet is so much simpler! I was so paranoid about checking the correct lengths (and indexing using the correct lengths) that I forgot that stripping from the right would just take care of things.

buildbot, test on oracle.

This might have other implications but have we investigated the possibility of normalizing the index names to drop multibyte characters?
# Taken from django.utils.slugify(allow_unicode=False)
index_name = unicodedata.normalize('NFKD', index_name).encode('ascii', 'ignore').decode('ascii')

Interesting, what do you think the backwards compatibility ramifications of that would be? I was thinking that only stripping from the right when exceeding the character limit on a backend would be alright because such an index could never have been created.

@jacobtylerwalls I think that there might some code that will expect the index name generation logic to remain stable at least there was in Django 1.7 addition of migrations where we changed the format from the one used by South.

I was thinking that only stripping from the right when exceeding the character limit on a backend would be alright because such an index could never have been created.

Right, your approach is fully backward compatible for this reason but the systematic unicode normalization of index names isn't as it changes the generated names of index containing multibyte characters but fitting the max allowed lenght.
Only performing the normalization when we detect overflow would be backward compatible but then you still need to determine whether or not an index name overflows.

Makes sense. I'm trying to think through whether one approach is better than the other. Both implementations seem low-complexity. My next thought is to wonder if users will find it unexpected that sometimes their index names contain multibyte characters and sometimes don't? (This would be avoided with the just-chop-the-right-end strategy.)

@jacobtylerwalls I have doubts about using encode() :confused: As far as I'm aware, identifier limits are express in chars not bytes, chars that can have 2, 3, 4 bytes. It may also depend on encoding of the operating system or database :exploding_head:, so this change is not fully backward compatible because it will truncate existing names in a different way. For example:
class żółćęśąźńżółćęśąźńżółćęśąźńżółćęśąźń(models.Model):
    żółćęśąźńżółćęśąźńżółćęśąźńżółćęśąźń = models.IntegerField(db_index=True)

Currently, the table name is truncated to backends_żółćęśąźńżółćęśąź3d64 and index name to backends_ż_żółćęśąźńż_bd4c8b2f, but with this patch all diacritic marks are counted as 2 chars and index name is truncated to backends__żółćę_bd4c8b2f.
I'm afraid that it may not be feasible to fix this without breaking backward compatibility (see also https://github.com/django/django/pull/9816#issuecomment-375731732).

3-byte chars are also affects, e.g.
class żółćęśąźńżółćęśąźńżółćęśąźńżółćęśąźń(models.Model):
    żółćęśąźńżółćęśąźńżółćęśąźńżółćęśąźń = models.IntegerField(db_index=True)

    class Meta:
        db_table="♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥♥"

Currently, the index name is truncated to ♥♥♥♥♥♥♥♥♥♥_żółćęśąźńż_9ba11e7f, but with this patch it is truncated to ♥♥♥_żółćę_9ba11e7f. It's worth mentioning that ♥♥♥♥♥♥♥♥♥♥_żółćęśąźńż_9ba11e7f works fine on Oracle.

Thanks for checking. Yes, this patch looks wrong-track and so do most of the premises in the original ticket.
I looked up MySQL (5.7 docs), and it looks like the following has worked since 4.1.5:

The sizes of the identifier string columns in the grant tables are measured in characters. You can use multibyte characters without reducing the number of characters permitted for values stored in these columns.

I know nothing about Oracle, but Oracle v. 21 docs say:

Oracle Database prior to version 12.2 limit identifier names, such as table names, column names, and primary key names, to 30 characters. Oracle Database 12.2 and higher have a default limit of 128 characters.

...

If the identifiers use multi-byte characters, the MaxIdentifierLength may need to be set with character expansion ratio in mind to assure that all identifiers can be created in the Oracle database. For example, if the Oracle database character set is UTF8, a single character may require up to 4 bytes. Thus, to guarantee that all identifiers can be created in an Oracle database that does not support long identifiers, the MaxIdentifierLength should be set to 7 characters (i.e. 30 characters divided by 4).

I found that a little hard to parse, but I think it's saying that the >12.2 limit of 128 "characters" is actually "bytes", so Django's 30 character limit would no longer cause any problems with even 30 * 4 < 128. Is that right?
Maybe the original reporter was on an Oracle version below 12.2 at the time of the report?
There is probably nothing to fix here. Could close as "needsinfo"? We would need to know how the "name error" mentioned in the report happened. Did the database do an auto-truncation? I doubt we have to provide a general solution for names teasing the upper limit (see ticket-33169). Thanks again for looking.

I found that a little hard to parse, ...

Yes, it's really confusing.

... but I think it's saying that the >12.2 limit of 128 "characters" is actually "bytes", so Django's 30 character limit would no longer cause any problems with even 30 * 4 < 128. Is that right?

 Any solution would be error-prone.


Introduces openh264.

@ibauersachs I just force pushed the last to commits with latest changes in jitsi-lgpl-deps.


fixes #175 - updated regex to find a signed package on /plugin_package page

fixes #175
the current implementation tries to parse a package's remote path from   on /plugin_package. that link is not always correct ( for example if you device has a sdcard installed )
/plugin_package page response always have var params = JSON.parse('......') line. And the actual link ( when you opens the page in the browser ) built from the following js
var pkgs = params.packages.filter(p => p.pkgPath !== "");
var hasPkgApp = pkgs.length > 0;
{
  var pkgDiv = document.createElement('div');
  if (hasPkgApp) {
    var package = pkgs[0];
    var pkgPath = package.pkgPath;
    var pkgName = package.pkgPath.substr(package.pkgPath.lastIndexOf('/') + 1);
    var size = package.size;

    pkgDiv.innerHTML = `Currently Packaged Application:

          ${pkgName}

 package file (${size} bytes)

`;
  }
  else {
    pkgDiv.innerHTML = `Currently Packaged Application:

          Application is not yet packaged

`;
  }
}

@TwitchBronBron yes, a fallback is a good idea.


How to handle dynamic variables in useQuery?

Started fiddeling with this package and it looks really awsome. I am trying to understand how to automatically refetch when variables changes in a useQuery hook. I don't know if i misunderstood something but this is what I have tried, and it only fetches once.`
On first render, it fetches correctly and logs correct data and variables. When setVariables it runs it updates those correctly, but no re-render is done and it logs new variables but same old data. Am i missing something here? There is no example for this.
function foo() {
  const [variables, setVariables] = useState({});
  const { data, loading } = useQuery(SOME_GRAPHQL_SCHEMA, {
    variables,
    suspend: false,
  });

  if(loading) return
Loading
;
  console.log(data, variables);
  return (...);
}
```

This seems to work, but I don't really know if its the right approach.
`
function foo() {
const [variables, setVariables] = useState({});
const { data, loading } = useQuery(SOME_GRAPHQL_SCHEMA, {
variables,
suspend: false,
});
useEffect(() => {
refetch(variables);
}, [variables]);
if(loading) return Loading;
console.log(data, variables);
return (...);
}
`

@rsjolundchas the first example should work. Please look at https://codesandbox.io/s/n4o02oz6jm - you should see different images for cats and dogs.

Thanks for your reply. I came up with a different approach to prevent having to set JSX based on loading props, which seems messy to me. I insted made a different hook to handle data fetching, mutations and variables which i hope works and is a bit cleaner :)

I'm having issues with this also:
const [sortOptions, openSortBottomSheet] = useSortOptions<CollectibleTypeSortOptions>('STORE_BROWSE')
  const {
    data,
    networkStatus,
    refetch,
    fetchMore,
    loading
  } = useQuery<StoreBrowseQuery, StoreBrowseQueryVariables>(QUERY, {
    notifyOnNetworkStatusChange: true,
    variables: sortOptions
  })

Event though the value of sortOptions changes the query never refetches. Seems like something is missing

I ended up giving up just using useApolloClient() (which actually makes more sense in my case),

I having the same problem. If the variables change the query is not re-executed. Any help would be appreciated

I ended up using useEffect and refetch() when variables change. Don't know if this is the right approach.

@rsjolundchas how did you use refetch() excatly?

@rsjolundchas how did you use refetch() excatly?

Like in my post above

This seems to work, but I don't really know if its the right approach.
function foo() {
  const [variables, setVariables] = useState({});
  const { data, loading } = useQuery(SOME_GRAPHQL_SCHEMA, {
    variables,
    suspend: false,
  });

  useEffect(() => {
    refetch(variables);
  }, [variables]);

  if(loading) return
Loading
;
  console.log(data, variables);
  return (...);
}

got it, idk how I missed this comment. Thanks.
Also, I have a completely unrelated doubt how are you comparing variables if they are an object. I am talking about how to actually deep compare the dependencies of useState, RN i run into an infinite loop. So, I used JSON.stringify.
@rsjolundchas

I think I ended up looking at parts of the object actually. I am at i new assignment right now so i can't check. But something like:
useEffect(() => {     refetch(variables);   }, [variables.limit, variables.order, variables.limit]);

Is there any traction on this issue?  Just started hitting it today...

Here's my hacky workaround:
/**
 * When the variables inside options changes dynamically, the query is NOT rerunning as of react-apollo beta.5
 * See https://github.com/trojanowski/react-apollo-hooks/issues/83
 *
 * We add a useEffect here to refetch the query if the underlying variables change
 * @param query
 * @param options
 */
export function useQueryDynamic<TData = any, TVariables = OperationVariables>(query: DocumentNode, options?: QueryHookOptions<TData, TVariables>): QueryResult<TData, TVariables> {
  const isFirstRun = useRef(true);
  const q          = useQuery(query, options)

  useEffect(() => {
    if (!isFirstRun.current) {
      q.refetch()
    } else isFirstRun.current = false
  }, [JSON.stringify(options.variables)])

  return q
}

I am hitting the same situation. I have a dialog that opens in either an edit state (has an item id) or a new state (doesn't have an item id) ...  I only want to execute the Query if id was passed in, if not then do not Query.
The dialog can be opened in different parts of the app so placing the query outside the dialog in the calling component doesn't feel like the clean solution either. This logic fits properly inside said Dialog.
I'm finding most "workarounds" to be somewhat "dirty" ...

Hitting this as well, and I hit the useEffect/refetch issue (infinite fetching), so this is a bug then? I thought I was going crazy

Hitting this as well, and I hit the useEffect/refetch issue (infinite fetching), so this is a bug then? I thought I was going crazy

How does your code look? I made the mistake of storing the variables in the function body and then check them in useEffect(). Since they where defined every re-render, the effect ran each re-render and created an infinite loop.

This works for me:
const { loading, error, data } = useQuery(QUERY_SCHEMA, {variables: {var1:value1}})

Hi,
Encountered this too.  Issue of setting the value of title did not cause a re-query of the API.
Here is the way I was able to resolve.
Before (not work):
const BOOKS_QUERY = gql`
  {
    books {
      author
      title
    }
  }
`;

// note, the below lines of code are in the React function
const [title, setTitle] = useState("");

const { loading, error, data } = useQuery(BOOKS_QUERY, {
    variables: { title }
  });

Resolution (works!) - modified the query:
const BOOKS_QUERY = gql`
  query getBooks($title: String) {
    books(title: $title) {
      author
      title
    }
  }
`;

And then was able to achieve the desired outcome.

Hey, I just ran in to this problem myself and noticed a similar issue to @EricGrudzien above. My variable name was wrong when passing in to the query:
 const { data, loading } = useQuery<SearchClientsResponse>(SEARCH, {     variables: {       keywords,       sort     },   });
But by query definition was:
query SearchClients($keywords: String, $sortBy: String) {
    searchClients(keywords: $keywords, sortBy: $sortBy) {
     id
    }

Still having this issue

@hyposlasher did you notice the part where this library is super deprecated? -- there are official react hooks for ApolloClient that you should really move to! https://www.npmjs.com/package/@apollo/react-hooks

I believe this is what you're looking for. You need to add those variables in the query key.

I believe this is what you're looking for. You need to add those variables in the query key.

The link your provided is for React Query, which has no relation to Apollo.


Update the dependency to core-java 0.10.80-SNAPSHOT.

Auto-generated PR to update core library dependency to the latest version.

@dmitrykuzmin PTAL. And feel free to merge.


Allow overriding the vic-go-au logo

What
Provide an API for overriding the vic.gov.au logo colour in the site header
Why
The vic.gov.au logo is fixed in Ripple to enforce the brand Vic requirement of having the logo. However there are some circumstances where this is problematic, for example when using on light coloured headers.
https://www.firstpeoplesrelations.vic.gov.au/ example

Other considerations
Should we consider if this should be completely optional? Eg https://salsadigital.com.au/

@MdNadimHossain relates to patch in https://github.com/dpc-sdp/schoolbuildings-vic-gov-au/pull/12

@duncanlegge example of a light weight feature proposal issue


CCE-528: Fix the underline on hover in IE and for pagination

Hi Jeremy,
Here are the changes I made:

no underline on hover and on focus for btn-link (appears mostly in IE)
no underline on hover for pagination (there is already a change of color)

Thank you,
Andreea

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

i was in master; so please ignore; will do it again from develop


RC test: Geometric Optics 1.0.0-rc.1

@KatieWoe @kathy-phet @arouinfar @ariel-phet, geometric-optics/1.0.0-rc.1 is ready for RC-lite testing.
Document issues in https://github.com/phetsims/geometric-optics/issues and link to this issue.
This is an RC-lite test, for an eventual prototype publication.  It is general only, no PhET-iO, no a11y.
Assigning to @kathy-phet and @KatieWoe for prioritization.

General RC Test

What to Test

Click every single button.
Test all possible forms of input.

Test all mouse/trackpad inputs.
Test all touchscreen inputs.

If there is sound, make sure it works.
Make sure you can't lose anything.
Play with the sim normally.
Try to break the sim.
Test all query parameters on all platforms. (See QA Book for a list of query parameters.)
Download HTML on Chrome and iOS.
Make sure the iFrame version of the simulation is working as intended on all platforms.
Make sure the XHTML version of the simulation is working as intended on all platforms.
Complete the test matrix.
Don't forget to make sure the sim works with Legends of Learning.
Test the Game Up harness on at least one platform.
Check this LoL spreadsheet and notify AR or AM if it not there.
If this is rc.1 please do a memory test.
When making an issue, check to see if it was in a previously published version.
Try to include version numbers for browsers.
If there is a console available, check for errors and include them in the Problem Description.
As an RC begins and ends, check the sim repo. If there is a maintenance issue, check it and notify developers if there is a problem.

Issues to Verify

[x] https://github.com/phetsims/geometric-optics/issues/146
[x] https://github.com/phetsims/geometric-optics/issues/230

For issues that have the "status:ready-for-qa" label.... Check these issues off and close them if they are fixed. Otherwise, post a comment in the issue saying that it wasn't fixed and link back to this issue.

Link(s)

Simulation
iFrame
XHTML
Test Matrix

FAQs for QA Members

There are multiple tests in this issue... Which test should I do first?
Test in order! Test the first thing first, the second thing second, and so on.

How should I format my issue?

We typically assign the developer who opened the issue in the QA repository.

My question isn't in here... What should I do?
You should:

Consult the QA Book.
Google it.
Ask Katie.
Ask a developer.
Google it again.
Cry.

Prototype 1.0.0 has been published.  Closing.


Ensure big log files don't slip through the cracks

In the chat.fhir.org server, the following files (at least) can get big but aren't covered by Zulip's default logrotate config:
/var/log/zulip# find . -type f -size +500M
./events-deliver_enqueued_emails.log
./tornado.log
./events-user-presence.log

This PR proposes covering all zulip logs with a *.log.

Thanks for working on this @jmandel!  But I think this change isn't required, as it would result in some files getting double-logrotated.  The events_ files are handled by supervisord, where we've adjusted the configuration to do properly in 6355f26b91a983610129926acef432e0688eb44d.  That will be in the 1.7 release, scheduled for early next week.

Thanks for the update @timabbott!


[FR] Relationships without included

Is your feature request related to a problem?
Is there a way to create relationships that only adds to the resource relationships object, so no additional documents are included at the top level? I don't see anything in the docs outlining how to do that.
Describe the solution you'd like
An option to turn included off
Additional context
The object I pass into the relator may look something like
{
  id: '1',
  name: 'thing',
  userId: '1'
}

I use this userId to lookup the entity to relate and include, I'd like an option to only relate. So I end up with
{
  data: {
    type: 'thing-model',
    id: '1',
    attributes: {
      name: 'thing'
    }.
    relationships: {
      user: {
        type: 'user',
        id: '1'
      }
    }
  }
}

instead of
{
  data: {
    type: 'thing-model',
    id: '1',
    attributes: {
      name: 'thing'
    }.
    relationships: {
      user: {
        type: 'user',
        id: '1'
      }
    }
  },
  included: [
    {
      type: 'user',
      id: '1',
      attributes: {
        something: 'here'
      }
    }
  ]
}

This way my client knows about the relationship and can decide if it wants to load it.

Realised I can do this by setting the depth to 0

Actually, a way to include some relationships and not others would be useful. Depth is all or nothing. So I guess I'd want to pass an option to the relator specifically, not the entire serializer.


Queue returns projects that were already processed.

In the #95 a common bug was the retry of already processed projects because they were given by the queue.

Probably an explanation:
RabbitMQ will redeliver a message if the client unexpectedly quits and did not acknowledge the first delivery. https://www.rabbitmq.com/tutorials/tutorial-two-python.html
Maybe, the client fails (e.g. with a HeapSpace Error) and then gets the same message over and over again, because it fails to process the already processed repo.

How do we always acknowledge the receive before processing the project? I thought this was done by the basicGet method already.


[2.0] Have a basic "doctor" command

A lot of people seem to get hung up because their environment is either a bit broken or isn't setting up really well for Feathers.
A good place to start might be to have a doctor command that inspects their env when they generate a project. This is what I'm thinking:
Basic
This is some of the basic stuff we probably should check.

[x] Check that node exists
[x] Check that npm exists
[x] Check for node v5.x+, prompt for upgrade if not
[x] Check for npm v.3.8.7+, prompt for upgrade if not

More Advanced
This is stuff that would be nice but definitely isn't crucial from day one.

[ ] Check that project name isn't the same as a dependency
[ ] Check that all the dependencies are installed
[ ] Check for node_gyp (ie. that we can compile binaries)
[ ] Check gcc version?
[ ] Check feathers.json is valid
[ ] Check/print out environment variables

Inspiration

Homebrew Doctor and it's checks
Yeoman doctor

This would be great. All I've done is install feathers-cli and run feathers generate and after answering the questions, it's just completely hung up, won't even create the initial files. I bet it has to do with my network setup at work with the proxy, but I have my NPM proxies set. How do I go about troubleshooting what to do, because I'm stuck on Step #1 of creating a FeathersJS app!


Stop writing empty files and improve EBI tests

Fix #1070

@adamrp it looks like there are legitimate test failures

Getting the same build failures that are over in #1175. Not sure exactly why this just started to be a problem, but the error message is related to pandas, which had an update on May 11, so I'm suspecting something there. The only thing I could find in the changelog related to this warning being raised is from an 8 Oct 2014 release (version 0.15).
Anyways, I think the issue is that because the warning we're looking for isn't the first warning, it's erroring (according to the nympy documentation on assert_warns), so we might have to take a different approach, perhaps something that borrows from this SO post.

Although less desirable, we could also just stick with an older version
of Pandas i.e. the one that was working just fine.
On (May-13-15|12:45), adamrp wrote:

Getting the same build failures that are over in #1175. Not sure exactly why this just started to be a problem, but the error message is related to pandas, which had an update on May 11, so I'm suspecting something there. The only thing I could find in the changelog related to this warning being raised is from an 8 Oct 2014 release (version 0.15).
Anyways, I think the issue is that because the warning we're looking for isn't the first warning, it's erroring (according to the nympy documentation on assert_warns), so we might have to take a different approach, perhaps something that borrows from this SO post.

Reply to this email directly or view it on GitHub:
https://github.com/biocore/qiita/pull/1172#issuecomment-101792632

I think I've traced the issue to here, but I don't know enough about Pandas to fix the issue.

Coverage decreased (-0.04%) to 79.24% when pulling 6f516ed197235cf0b12b817b22e4b23f6088f318 on adamrp:ebi_empty_files-issue-1070 into da407f650ce67619aaabf61d620e382f39621c22 on biocore:master.

Ready for review

Thanks @adamrp , just a small comment.

Thanks @josenavas, done!

Coverage decreased (-0.05%) to 79.23% when pulling dd99ee5ca4d87bc1a21f11c585b0202d0b48ca98 on adamrp:ebi_empty_files-issue-1070 into 2d71d7d2df35f050b77995a65e751340f1520532 on biocore:master.

:+1:


System.DllNotFoundException/e_sqlite3 In Self-Contained app on RHEL 6

I have developed an app that's intended to be published self-contained on a number of RHEL 6 servers (using the rhel.6-x64 RID) and I get an error indicating that it is unable to find the shared library e_sqlite3. If I publish it with the linux-x64 RID and run it on a RHEL 7 machine it works as expected.
I do really feel like I'm doing something wrong but Googling seems to have failed me.
To Reproduce
1 - Publish code (seen below) to RHEL 6 self-contained app
2 -  Execute
3- Receive error on start (line 3 in snip)
var dbContextFact = new DatabaseContextFactory();
  using(var dbContext = dbContextFact.CreateDbContext(null)) {
    if (dbContext.Database.GetPendingMigrations().Any())
     dbbContext.Database.Migrate();
  }

Additional context
Microsoft.Data.Sqlite version: 3.0.0-preview9.19423.4
Target framework: .NET Core 3.0
Operating system: RHEL 6.10

I realize a full stack trace might help...
Unhandled exception. System.TypeInitializationException: The type initializer for 'Microsoft.Data.Sqlite.SqliteConnection' threw an exception.
---> System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation.
---> System.DllNotFoundException: Unable to load shared library 'e_sqlite3' or one of its dependencies. In order to help diagnose loading problems, consider setting the LD_DEBUG environment variable: libe_sqlite3: cannot open shared object file: No such file or directory
at System.Runtime.InteropServices.NativeLibrary.LoadByName(String libraryName, QCallAssembly callingAssembly, Boolean hasDllImportSearchPathFlag, UInt32 dllImportSearchPathFlag, Boolean throwOnError)
at System.Runtime.InteropServices.NativeLibrary.LoadLibraryByName(String libraryName, Assembly assembly, Nullable1 searchPath, Boolean throwOnError)    at System.Runtime.InteropServices.NativeLibrary.Load(String libraryName, Assembly assembly, Nullable1 searchPath)
at SQLitePCL.NativeLibrary.Load(String libraryName, Assembly assy, Int32 flags)
at SQLitePCL.Batteries_V2.MakeDynamic(String name, Int32 flags)
at SQLitePCL.Batteries_V2.DoDynamic_cdecl(String name, Int32 flags)
at SQLitePCL.Batteries_V2.Init()
--- End of inner exception stack trace ---
at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor, Boolean wrapExceptions)
at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
at System.Reflection.MethodBase.Invoke(Object obj, Object[] parameters)
at Microsoft.Data.Sqlite.Utilities.BundleInitializer.Initialize()
at Microsoft.Data.Sqlite.SqliteConnection..cctor()
--- End of inner exception stack trace ---
at Microsoft.Data.Sqlite.SqliteConnection..ctor(String connectionString)
at Microsoft.EntityFrameworkCore.Sqlite.Storage.Internal.SqliteRelationalConnection.CreateDbConnection()
at Microsoft.EntityFrameworkCore.Storage.RelationalConnection.get_DbConnection()
at Microsoft.EntityFrameworkCore.Storage.RelationalConnection.Open(Boolean errorsExpected)
at Microsoft.EntityFrameworkCore.Sqlite.Storage.Internal.SqliteDatabaseCreator.Exists()
at Microsoft.EntityFrameworkCore.Migrations.HistoryRepository.Exists()
at Microsoft.EntityFrameworkCore.Migrations.HistoryRepository.GetAppliedMigrations()
at Microsoft.EntityFrameworkCore.RelationalDatabaseFacadeExtensions.GetAppliedMigrations(DatabaseFacade databaseFacade)
at Microsoft.EntityFrameworkCore.RelationalDatabaseFacadeExtensions.GetPendingMigrations(DatabaseFacade databaseFacade)
at dbmd.Program.Main(String[] args) in /home/ee925c/source/dbmd/Program.cs:line 21
at dbmd.Program.(String[] args)


Make changes to Docker Installation, including adding step by step in…

Steps to Confirm

Ran make docs-serve and checked changes locally

Pre-Merge Checklist

[ ] All CI Pipelines Succeeded
[X] Documentation Updated :)

Description Of Changes
I made some updates to the Docker Installation instructions. These include:

More information about Docker
Installing Docker, Docker Compose
Pulling the fidesctl container image
Next steps for setting up the database, using Docker Compose, and following the tutorial

I went back and forth on whether to put "Installation" or "Docker Hub Releases" first. I think most developers would come to the page for those directions first, but the Docker Hub Releases section has important information as well.
I added "Implementation is not finalized in mid-release versions." based on past experience developing, to offer developers a bit of guidance on whether the "dirty versions" are safe to integrate against. But it is an educated guess.

I decided to put the full Installation instruction in the Installation from Docker section. But it raises a similar question with the Release Cadence and Installation from before: what will the developer's path through the documentation be?
I see a few more options: move Quick Start below Installation and before Tutorial, combine Quick Start and Installation for Docker, or have those instructions in Quick Start since it will come first. The last would likely be the quickest, since I see the other two as larger refactors.
What are your thoughts here?


how to: server config, .htaccess, 404 page file, etc.

Noob question I'm sure, but on shared hosting services like BlueHost/GoDaddy/etc. the root directory has a bunch of files .htaccess, 404 and other error page files, etc. Wondering if I can use these and how? (Or maybe, alternately, if there's any way to use/access/edit a server config file?)
All I want to do is redirect 404 errors to a php template, which can't be that complex as I figure it!

This project connects with your PC's php-cli and not Apache. As such .htaccess files and such will not work and cannot be modified to work.

gotchya, thanks man!


Warning No. 3: V701 realloc() possible leak: when realloc() fails in …

Warning No. 3: V701 realloc() possible leak: when realloc() fails in allocating memory, original pointer 'elems' is lost. Consider assigning realloc() to a temporary pointer. compiler.cpp 2922
This code is potentially dangerous: we recommend using a separate variable to store the return result of function realloc(). The realloc() function is used to change the size of a memory block. If such change is impossible for the moment, it will return a null pointer. The problem is that pointer ptr, referring to this memory block, may get lost when using constructs like "ptr = realloc(ptr, ...)".

Forgot to free the temp variable


how to init select default value in ui select

here is my code:

ts
lists = [
{ "name": "Default 1", "value": { "id": 1, "taxName": "Default 1", "taxRate": 16, "isActive": true } },
{ "name": "Default 2", "value": { "id": 2, "taxName": "Default 2", "taxRate": 10, "isActive": true } },
{ "name": "Default 3", "value": { "id": 3, "taxName": "Default 3", "taxRate": 15, "isActive": true } },
];
selectedDefault: = { "name": "Default 2", "value": { "id": 2, "taxName": "Default 2", "taxRate": 10, "isActive": true } };

view
<sui-select class="selection"  #select
[(ngModel)]="selectedDefault"
(ngModelChange)="selectedTaxChange.emit($event)"
[options]="lists"  style="width:100%"  labelField="name"
valueField="value"  [isSearchable]="searchable" [isDisabled]="disabled">
<sui-select-option *ngFor="let option of select.filteredOptions" [value]="option">/sui-select-option>

@sokhomhuy: In case you haven't figured it out yet, you're setting 'selectedDefault' to something that's not a value for the control. If you want to set a default value, you can set on component init like so: this.selectedDefault = this.lists[1].value or 1) use just the value portion of 'selectedDefault' or 2) setup your structure in a different way if you want to set 'selectedDefault' in it's definition.

As @sokhomhuy, the initial value has to be something in the list, as within a select equality checks are done referentially, rather than structurally.


Can we only lint modified files?

Did some research regarding #1 and found a GitHub action that helps with annotation via a .json file: https://github.com/Attest/annotations-action.
They just released a new version of runner that helps with composite actions https://docs.github.com/en/actions/creating-actions/about-actions#composite-run-steps-actions
But it's not fully ready to support calling an action within another action yet (which I think is the main reason we need the composite action though lol https://github.com/actions/runner/issues/646#issuecomment-683160895
Here are the next steps for composite actions: https://github.com/actions/runner/issues/646
When expected action within action is released, we can leverage

file changes(conditional step, if to check for modified files or entire branch) https://github.com/trilom/file-changes-action
Run eslint and parse errors/warnings messages to follow https://github.com/Attest/annotations-action/blob/master/annotations.json (type definition: https://github.com/Attest/annotations-action/blob/master/src/annotation.ts)

Originally posted by @theoomoregbee in https://github.com/wearerequired/lint-action/issues/47#issuecomment-687804620
Is this issue this still relevant today? Are we still waiting for github to release the functionality that enables us to lint only modified files?

Would still love this feature


No remarks output to RTs!?

TWO THINGS:

Output remarks (not remark URLs, these are already output) to RDF/XML RTs, so that they end up in Sinopia
Output remarks to HTML RTs

Output RT-level remark to HTML RTs


Override environment sky option

Currently the environments force specific skybox colors if they are defined, overriding the menu option. This PR adds a checkbox to force the color selected in the menu instead.
It is selectively applied so that areas which need a specific skybox for game or quest design (such as black for empty space at the cosmic altar) can still force their values, but the vast majority of the game world will obey the menu if enabled.
Fixes #205

Committed, thx

https://streamable.com/p48kiy


missing python dependency in rule plot_stats

I got the following error running this workflow,
[Thu Oct 21 10:30:39 2021]
rule plot_stats:
    input: results/tables/calls.tsv.gz
    output: results/plots/depths.svg, results/plots/allele-freqs.svg
    log: logs/plot-stats.log
    jobid: 24
    resources: tmpdir=/tmp

Activating conda environment: /home/pedro/projects/sandbox/snake-gatk/.snakemake/conda/c8bc479b3ecf77c3e954eb4b0008039b
Activating conda environment: /home/pedro/projects/sandbox/snake-gatk/.snakemake/conda/c8bc479b3ecf77c3e954eb4b0008039b
[Thu Oct 21 10:30:40 2021]
Error in rule plot_stats:
    jobid: 24
    output: results/plots/depths.svg, results/plots/allele-freqs.svg
    log: logs/plot-stats.log (check log file(s) for error message)
    conda-env: /home/pedro/projects/sandbox/snake-gatk/.snakemake/conda/c8bc479b3ecf77c3e954eb4b0008039b

The log shows the following message,
Traceback (most recent call last):
  File "/home/pedro/projects/sandbox/snake-gatk/.snakemake/scripts/tmpjsez2vr4.plot-depths.py", line 8, in <module>
    import common
ModuleNotFoundError: No module named 'common'

I had the same issue. Seems like the pipeline does not download the file common.py it's supposed to use. I have tried to download (from github) and run the scripts manually, using the calls.tsv.gz (or calls.tsv) file as input. It generates very large svg files that fail to be converted to png when I tried to generate the reports using "snakemake --report report.zip".

I really struggle with this problem rn, have you solved it yet?


Solve local exposure, the server opens the token, and the client call fails

What is the purpose of the change
Solve local exposure, the server opens the token, and the client call fails.
see more detail from https://github.com/apache/dubbo/issues/7024
Brief changelog
XXXXX
Verifying this change
XXXXX
Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Make sure there is a GITHUB_issue field for the change (usually before you start working on it). Trivial changes like typos do not require a GITHUB issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[ ] Format the pull request title like [Dubbo-XXX] Fix UnknownException when host config not exist #XXX. Each commit in the pull request should have a meaningful subject line and body.
[ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add sample in dubbo samples project.
[ ] Run mvn clean install -DskipTests=false & mvn clean test-compile failsafe:integration-test to make sure unit-test and integration-test pass.
[ ] If this contribution is large, please follow the Software Donation Guide.

Codecov Report

Merging #7334 (a5ccaf4) into master (2062cdb) will decrease coverage by 0.22%.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##             master    #7334      +/-   ##
============================================
- Coverage     59.06%   58.84%   -0.23%
+ Complexity      463      461       -2
============================================
  Files          1044     1044
  Lines         42485    42445      -40
  Branches       6230     6200      -30
============================================
- Hits          25094    24976     -118
- Misses        14591    14654      +63
- Partials       2800     2815      +15

Impacted Files
Coverage Δ
Complexity Δ

.../apache/dubbo/rpc/protocol/injvm/InjvmInvoker.java
88.23% <100.00%> (+3.61%)
0.00 <0.00> (ø)

...va/org/apache/dubbo/remoting/TimeoutException.java
0.00% <0.00%> (-33.34%)
0.00% <0.00%> (ø%)

...ng/transport/dispatcher/all/AllChannelHandler.java
62.06% <0.00%> (-20.69%)
0.00% <0.00%> (ø%)

...bbo/common/bytecode/CustomizedLoaderClassPath.java
28.00% <0.00%> (-16.00%)
0.00% <0.00%> (ø%)

...va/org/apache/dubbo/remoting/exchange/Request.java
72.54% <0.00%> (-15.69%)
0.00% <0.00%> (ø%)

...rg/apache/dubbo/remoting/utils/PayloadDropper.java
76.92% <0.00%> (-15.39%)
0.00% <0.00%> (ø%)

...ng/transport/dispatcher/WrappedChannelHandler.java
47.82% <0.00%> (-15.22%)
0.00% <0.00%> (ø%)

...dubbo/remoting/exchange/support/DefaultFuture.java
75.22% <0.00%> (-12.82%)
0.00% <0.00%> (ø%)

...dubbo/common/status/support/LoadStatusChecker.java
50.00% <0.00%> (-11.54%)
0.00% <0.00%> (ø%)

...in/java/org/apache/dubbo/common/utils/JVMUtil.java
81.13% <0.00%> (-11.33%)
0.00% <0.00%> (ø%)

... and 43 more

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 2062cdb...a5ccaf4. Read the comment docs.


backslash escapes should not be highlighted in raw strings

via demo.odin:

Yes, it's VSCode.  Thanks!


Searching for new plugins issues

There are three issues (should I make 2-3 issues?) with searching for packages/themes to install from the settings menu.

Entering in a name does not result in an automatic search for what was typed. It only begins searching when I switch it from packages to themes and back.

Whenever I make a new search before the results from the old search are completed, under the search bar says searching for it failed and getaddrinfo ENOTFOUND.

Sometimes when I search for packages that exist like quippet, it says the same thing as above.

Atom Version: 0.186.0
System: linux 3.13.0-37-generic
OS: Linux Mint 17.1 Cinnamon 64-bit

Are you pressing enter after typing in what you want to search?

@50Wliu Yes.

Finally-can you replicate this behavior in safe mode (atom --safe)?  If so, I'll transfer this issue to the Tree View repo.

@50Wliu I couldn't replicate that behavior in safe mode.

All right, then it's a problem with one of your currently installed packages.  You might want to check out package-cop to find out exactly which one is the troublemaker.


Copyedit 2.0.65 release notes

Docs Build status updates of commit eb52b2c:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-ref-conceptual/release-notes-azure-cli.md
:white_check_mark:Succeeded
View (azure-cli-latest) View (azure-cli-2017-03-09-profile) View (azure-cli-2018-03-01-hybrid)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Traffic is blackholed when multihomed member withdraws an IP prefix from one of its border router

Suppose participant C has two BGP border routers C1 and C2, both announcing an IP prefix P. Participant A’s policy requires to send traffic with tcp_dst=4321 to C1 and traffic with tcp_dst=4322 to C2. The problem arises when C1 withdraws prefix P. In this case, the traffic continue to flow through C1 instead of flowing through any BGP border router announcing P. I guess the problem is that reachability information is at the per-participant level instead of the per-border-router level but I did not double-check it.

To reproduce the bug:

copy test1-mh-te.spec and its monitoring configuration file into test1-mh-te2.spec.
Update the build file to copy the gauge files into test*-mh-te2 as well.
uncomment these lines in test1-mh-te2.spec:

   #exec c1 ip -s -s neigh flush all
   #delay 2

   #test start_all_send_4321
   #test delay
   #test stop_all_send_4321

launch the script test and the Grafana dashboard (inbound_outbound_te_dashboard.py).


Bug: RxJS const state$ = from(interpreter) acts like a BehaviorObservable, does it designed for it or not?

Description
As the below source code shows:
https://github.com/statelyai/xstate/blob/c0b787d2a2334665af0ecb4ebc1ce5653fa3725c/packages/core/src/interpreter.ts#L431-L434
The subscribe() will always send the current state to the Observable, which will make it behave as a BehaviorSubject.
Expected result
I'm expected it only emits the future states at first but it doesn't.
So I have to use a share() then create a subscription to make it like a Hot Observable:
const state$ = from(interpreter).pipe(
  share()
)
// Make it never unsubscribed
state$.subscribe(() => {})

// wait for the next event:
const event = await fromFirstValue(state$.pipe(state => state.event)

Actual result
const state$ = from(interpreter)
const event = await fromFirstValue(state$.pipe(map(state => state.event)))

In the above code, the event will be the last event, instead of the future one.
So does the waitFor helper function.
Reproduction
https://codesandbox.io/s/reverent-ganguly-y4hrx4?file=/src/index.ts
Additional context
I'd like to treat it as a bug instead of a feature because when we want to wait for a future event, it seems the waitFor should be what we need. We expect to wait for the future values, instead of the past ones.

It's acting like a ReplaySubject and currently, it is designed like that.

Thank you very much for clarifying that the interpreter.subscribe() and the waitFor() behavior is acting like the ReplySubject! (To be precious, a ReplySubject with a buffer size of 1, which is the same behavior as a BehaviorSubject link)

If you want to ignore that replayed value then you can just use skip(1) and you will have exactly what you want.

Yes, that will solve my use case, appreciate your suggestion.
I think we can add 1-2 sentences in our docs to make it clear, and I'm good with this design now.
This issue can be closed. Thank you very much and have a great day!


Ixoswap

:tada: This PR is included in version 2.2.0-develop.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

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


 Possible related to #385 ?

We likely ran into this bug due to what I've fixed with https://github.com/apetavern/grubs/commit/f74ad68856f60cb4664f8eb34f228f57feab5ecf, however I also noticed an oversight in the turn logic that would lead to dead players being selected to play, which I've fixed with https://github.com/apetavern/grubs/commit/417bb9201f97462dcbf86ce00527aa27809d125a.


Update MyProjectService.kt

fix path for nx version 16 or above
/tools/workspace-plugin/src/generators
Current Behavior
After I update to NX 16.6.0 all Generators not display any more in Webstorm
I created PR with the fix https://github.com/etkachev/nx-webstorm/pull/113
I don't know how to upgrade the version
How to Reproduce

update to NX 16.6.0
open Generators menu in Webstorm

Expected Behavior
To show all Generators options

Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: macOS Catalina
Webstorm version 2023.1.3

The issue come from this file:
https://github.com/etkachev/nx-webstorm/blob/master/src/main/kotlin/com/github/etkachev/nxwebstorm/services/MyProjectService.kt
Lines 74-75
 val defaultCustomSchematicsLocation: String
    get() = if (this.isNx11OrAbove) "/tools/generators" else "/tools/schematics"

In NX version 16 the path to generators are /tools/workspace-plugin/src/generators

Hello! Thanks for mentioning the issue! I actually recently updated the plugin for new plugin support. You can see the changes here: https://github.com/etkachev/nx-webstorm/commit/ee56877f67037ae8da11282128f8cde8055dfb1a

Hello! Thanks for mentioning the issue! I actually recently updated the plugin for new plugin support. You can see the changes here: ee56877

But this looks under all generators under libs. I'll just have to add support to also search under tools

@etkachev
First I want to say Thanks as it awesome plugin and I love using it :)
Does your fix include the change of NX command ? as they are not using any more the @nx/cli .


Added missing palatal stops to Azerbaijani phonelist

[ɟ, c] were missing from the Azerbaijani phonelist (aze_narrow.phones). I added them in.
Closes #527

Submitting despite irrelevant test error (see #545).


Fix bug when casting empty array to class labels

Fix https://github.com/huggingface/datasets/issues/5520.

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


add flash attention

I try to add flash attention in the same way that fastchat and axolotl do.
However, I get this error message.
  File "/home/eric/miniconda3/envs/qlora/lib/python3.10/site-packages/transformers/models/llama/modeling_llama.py", line 340, in forward
    raise ValueError(
ValueError: Attention mask should be of size (1, 1, 513, 513), but is torch.Size([1, 513])

I wonder if you have any ideas?

transformers/models/llama/modeling_llama.py", line 340, in forward

this makes it seem like its still using the original forward method instead of the one that is patched in? wouldn't it say patch_flash_attn.py, in forward instead then?

yea it seems like one method is getting patched but not the other. that causes the mismatch and error:
https://github.com/huggingface/transformers/blob/05cda5df3405e6a2ee4ecf8f7e1b2300ebda472e/src/transformers/models/llama/modeling_llama.py#L580-L582
vs
https://github.com/artidoro/qlora/pull/235/files#diff-458bbbea97378409c55551005a82023f595014ec0ee5add98927d799aeed5d41R106-R107
so the question is why is the forward method not getting patched correctly.

here is full stack trace:
Traceback (most recent call last):
  File "/home/eric/git/qlora/qlora.py", line 845, in <module>
    train()
  File "/home/eric/git/qlora/qlora.py", line 807, in train
    train_result = trainer.train()
  File "/home/eric/miniconda3/envs/qlora/lib/python3.10/site-packages/transformers/trainer.py", line 1539, in train
    return inner_training_loop(
  File "/home/eric/miniconda3/envs/qlora/lib/python3.10/site-packages/transformers/trainer.py", line 1809, in _inner_training_loop
    tr_loss_step = self.training_step(model, inputs)
  File "/home/eric/miniconda3/envs/qlora/lib/python3.10/site-packages/transformers/trainer.py", line 2654, in training_step
    loss = self.compute_loss(model, inputs)
  File "/home/eric/miniconda3/envs/qlora/lib/python3.10/site-packages/transformers/trainer.py", line 2679, in compute_loss
    outputs = model(**inputs)
  File "/home/eric/miniconda3/envs/qlora/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1501, in _call_impl
    return forward_call(*args, **kwargs)
  File "/home/eric/miniconda3/envs/qlora/lib/python3.10/site-packages/torch/nn/parallel/distributed.py", line 1156, in forward
    output = self._run_ddp_forward(*inputs, **kwargs)
  File "/home/eric/miniconda3/envs/qlora/lib/python3.10/site-packages/torch/nn/parallel/distributed.py", line 1110, in _run_ddp_forward
    return module_to_run(*inputs[0], **kwargs[0])  # type: ignore[index]
  File "/home/eric/miniconda3/envs/qlora/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1501, in _call_impl
    return forward_call(*args, **kwargs)
  File "/home/eric/miniconda3/envs/qlora/lib/python3.10/site-packages/accelerate/utils/operations.py", line 581, in forward
    return model_forward(*args, **kwargs)
  File "/home/eric/miniconda3/envs/qlora/lib/python3.10/site-packages/accelerate/utils/operations.py", line 569, in __call__
    return convert_to_fp32(self.model_forward(*args, **kwargs))
  File "/home/eric/miniconda3/envs/qlora/lib/python3.10/site-packages/torch/amp/autocast_mode.py", line 14, in decorate_autocast
    return func(*args, **kwargs)
  File "/home/eric/miniconda3/envs/qlora/lib/python3.10/site-packages/peft/peft_model.py", line 922, in forward
    return self.base_model(
  File "/home/eric/miniconda3/envs/qlora/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1501, in _call_impl
    return forward_call(*args, **kwargs)
  File "/home/eric/miniconda3/envs/qlora/lib/python3.10/site-packages/accelerate/hooks.py", line 165, in new_forward
    output = old_forward(*args, **kwargs)
  File "/home/eric/miniconda3/envs/qlora/lib/python3.10/site-packages/transformers/models/llama/modeling_llama.py", line 806, in forward
    outputs = self.model(
  File "/home/eric/miniconda3/envs/qlora/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1501, in _call_impl
    return forward_call(*args, **kwargs)
  File "/home/eric/miniconda3/envs/qlora/lib/python3.10/site-packages/accelerate/hooks.py", line 165, in new_forward
    output = old_forward(*args, **kwargs)
  File "/home/eric/miniconda3/envs/qlora/lib/python3.10/site-packages/transformers/models/llama/modeling_llama.py", line 685, in forward
    layer_outputs = torch.utils.checkpoint.checkpoint(
  File "/home/eric/miniconda3/envs/qlora/lib/python3.10/site-packages/torch/utils/checkpoint.py", line 249, in checkpoint
    return CheckpointFunction.apply(function, preserve, *args)
  File "/home/eric/miniconda3/envs/qlora/lib/python3.10/site-packages/torch/autograd/function.py", line 506, in apply
Traceback (most recent call last):
  File "/home/eric/git/qlora/qlora.py", line 845, in <module>
    return super().apply(*args, **kwargs)  # type: ignore[misc]
  File "/home/eric/miniconda3/envs/qlora/lib/python3.10/site-packages/torch/utils/checkpoint.py", line 107, in forward
        train()
outputs = run_function(*args)  File "/home/eric/git/qlora/qlora.py", line 807, in train

  File "/home/eric/miniconda3/envs/qlora/lib/python3.10/site-packages/transformers/models/llama/modeling_llama.py", line 681, in custom_forward
    train_result = trainer.train()
  File "/home/eric/miniconda3/envs/qlora/lib/python3.10/site-packages/transformers/trainer.py", line 1539, in train
    return module(*inputs, output_attentions, None)    return inner_training_loop(

  File "/home/eric/miniconda3/envs/qlora/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1501, in _call_impl
  File "/home/eric/miniconda3/envs/qlora/lib/python3.10/site-packages/transformers/trainer.py", line 1809, in _inner_training_loop
    tr_loss_step = self.training_step(model, inputs)
  File "/home/eric/miniconda3/envs/qlora/lib/python3.10/site-packages/transformers/trainer.py", line 2654, in training_step
    return forward_call(*args, **kwargs)
  File "/home/eric/miniconda3/envs/qlora/lib/python3.10/site-packages/accelerate/hooks.py", line 165, in new_forward
    loss = self.compute_loss(model, inputs)
  File "/home/eric/miniconda3/envs/qlora/lib/python3.10/site-packages/transformers/trainer.py", line 2679, in compute_loss
    output = old_forward(*args, **kwargs)
  File "/home/eric/miniconda3/envs/qlora/lib/python3.10/site-packages/transformers/models/llama/modeling_llama.py", line 408, in forward
    outputs = model(**inputs)
  File "/home/eric/miniconda3/envs/qlora/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1501, in _call_impl
    hidden_states, self_attn_weights, present_key_value = self.self_attn(    return forward_call(*args, **kwargs)

  File "/home/eric/miniconda3/envs/qlora/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1501, in _call_impl
  File "/home/eric/miniconda3/envs/qlora/lib/python3.10/site-packages/torch/nn/parallel/distributed.py", line 1156, in forward
    output = self._run_ddp_forward(*inputs, **kwargs)
  File "/home/eric/miniconda3/envs/qlora/lib/python3.10/site-packages/torch/nn/parallel/distributed.py", line 1110, in _run_ddp_forward
    return module_to_run(*inputs[0], **kwargs[0])  # type: ignore[index]
  File "/home/eric/miniconda3/envs/qlora/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1501, in _call_impl
    return forward_call(*args, **kwargs)
      File "/home/eric/miniconda3/envs/qlora/lib/python3.10/site-packages/accelerate/hooks.py", line 165, in new_forward
return forward_call(*args, **kwargs)
  File "/home/eric/miniconda3/envs/qlora/lib/python3.10/site-packages/accelerate/utils/operations.py", line 581, in forward
        return model_forward(*args, **kwargs)
  File "/home/eric/miniconda3/envs/qlora/lib/python3.10/site-packages/accelerate/utils/operations.py", line 569, in __call__
output = old_forward(*args, **kwargs)
  File "/home/eric/miniconda3/envs/qlora/lib/python3.10/site-packages/transformers/models/llama/modeling_llama.py", line 340, in forward
    return convert_to_fp32(self.model_forward(*args, **kwargs))
  File "/home/eric/miniconda3/envs/qlora/lib/python3.10/site-packages/torch/amp/autocast_mode.py", line 14, in decorate_autocast
    return func(*args, **kwargs)
  File "/home/eric/miniconda3/envs/qlora/lib/python3.10/site-packages/peft/peft_model.py", line 922, in forward
    raise ValueError(    return self.base_model(

  File "/home/eric/miniconda3/envs/qlora/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1501, in _call_impl
ValueError: Attention mask should be of size (1, 1, 513, 513), but is torch.Size([1, 513])
    return forward_call(*args, **kwargs)
  File "/home/eric/miniconda3/envs/qlora/lib/python3.10/site-packages/accelerate/hooks.py", line 165, in new_forward
    output = old_forward(*args, **kwargs)
  File "/home/eric/miniconda3/envs/qlora/lib/python3.10/site-packages/transformers/models/llama/modeling_llama.py", line 806, in forward
    outputs = self.model(
  File "/home/eric/miniconda3/envs/qlora/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1501, in _call_impl
    return forward_call(*args, **kwargs)
  File "/home/eric/miniconda3/envs/qlora/lib/python3.10/site-packages/accelerate/hooks.py", line 165, in new_forward
    output = old_forward(*args, **kwargs)
  File "/home/eric/miniconda3/envs/qlora/lib/python3.10/site-packages/transformers/models/llama/modeling_llama.py", line 685, in forward
    layer_outputs = torch.utils.checkpoint.checkpoint(
  File "/home/eric/miniconda3/envs/qlora/lib/python3.10/site-packages/torch/utils/checkpoint.py", line 249, in checkpoint
    return CheckpointFunction.apply(function, preserve, *args)
  File "/home/eric/miniconda3/envs/qlora/lib/python3.10/site-packages/torch/autograd/function.py", line 506, in apply
    return super().apply(*args, **kwargs)  # type: ignore[misc]
  File "/home/eric/miniconda3/envs/qlora/lib/python3.10/site-packages/torch/utils/checkpoint.py", line 107, in forward
    outputs = run_function(*args)
  File "/home/eric/miniconda3/envs/qlora/lib/python3.10/site-packages/transformers/models/llama/modeling_llama.py", line 681, in custom_forward
    return module(*inputs, output_attentions, None)
  File "/home/eric/miniconda3/envs/qlora/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1501, in _call_impl
    return forward_call(*args, **kwargs)
  File "/home/eric/miniconda3/envs/qlora/lib/python3.10/site-packages/accelerate/hooks.py", line 165, in new_forward
    output = old_forward(*args, **kwargs)
  File "/home/eric/miniconda3/envs/qlora/lib/python3.10/site-packages/transformers/models/llama/modeling_llama.py", line 408, in forward
    hidden_states, self_attn_weights, present_key_value = self.self_attn(
  File "/home/eric/miniconda3/envs/qlora/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1501, in _call_impl
    return forward_call(*args, **kwargs)
  File "/home/eric/miniconda3/envs/qlora/lib/python3.10/site-packages/accelerate/hooks.py", line 165, in new_forward
    output = old_forward(*args, **kwargs)
  File "/home/eric/miniconda3/envs/qlora/lib/python3.10/site-packages/transformers/models/llama/modeling_llama.py", line 340, in forward
    raise ValueError(
ValueError: Attention mask should be of size (1, 1, 513, 513), but is torch.Size([1, 513])

could be possible that qlora patches it again after I patch it?

/accelerate/hooks.py", line 165, in new_forward
output = old_forward(*args, **kwargs)

this seems suspicious w/ old_forward and new_forward. maybe its grabbing the original method before we patch it with flash-attn

ah i think you need to call replace... method to monkey patch before the model is instantiated, i.e. before AutoModelForCausalLM.from_pretrained

try this? https://github.com/artidoro/qlora/commit/1b5641913914a48ad15eadb96a0dba6452aa0ac1

ok trying

RuntimeError: FlashAttention only support fp16 and bf16 data type

seems maybe FlashAttention needs to be modified to support this

Does this still work? I still get the same error of "RuntimeError: FlashAttention only support fp16 and bf16 data type"

try this: https://github.com/artidoro/qlora/issues/221#issuecomment-1711860999
replace_attn_with_flash_attn() followed by model = upcast_layer_for_flash_attention(model, torch.bfloat16) should fix this.


Vendors - Part 1 - Create signup and login functionality for vendors

Your task is to create a new table for vendors ( Just one possible solution) and write to it through a sign up page for these vendors. Also implement login functionality that authenticates vendors. Both the vendor signup and login option must be present in the corner dropdown menu for any user that is not logged in. In part 2 of this issue the add and delete options for categories and products will only be available to these vendors.

can you assign this to me

can you assign this to me

Assigned to @samarth777

can you please assign this to me?

can you assign this to me?

can you assign this to me

It's been 40 minutes the first person has assigned pls assigned to me

@samarth777 what is the update?

@samarth777 ??

where do i write it

can i please get assigned to this??

@DedLad you have been assigned this issue.

@DedLad updates??

@DedLad please update.

can i get assigned to this please??

can i work on this pls?

can i get assigned if this is still open?

@achyuthcodes30 wya man

can i get assigned to this please?

can i get assigned if this is still open?

can i get this issue signed?#19

can i get this issue assigned?#19


Flash screen in some case

Describe the bug
Version test: v1.0.2(158)
Devices test: IP 11

[x] Flash in case Attach watch-only account

https://github.com/Koniverse/SubWallet-Mobile/assets/117999489/8b656e34-48a1-46fb-91f1-1c3ea9690042

[x] Select account

https://github.com/Koniverse/SubWallet-Mobile/assets/117999489/46a2314a-203d-45dd-91b5-8a865cfabb30

Version test: v1.0.3(161)
Devices test: IP 11
Validation passed.


in old project

i have an issue i was working on old project use 0.5.0 version and now i run the code with flutter update  1.17.0 and it get error java.lang.RuntimeException: Methods marked with @UiThread must be executed on the main thread. Current thread: Binder:19486_3
and i upgrade the plugin 0.7.2 and get error in scan and the methods in plugin can you help me to run the code on 0.5.0 version or in the updated plugin

the code works will when i downgrade flutter to version year ago.


Properly close file descriptor after forking

mesos-command-modules still have a leak of file descriptors (type pipe).
Before this patch, 2 pipes were opened (4 file descriptors) before
forking:

child process was not closing fd (but that's ok because they are
released when process close)
parent process does not release 2 out of 4 fds

Change-Id: Ie223ab25f2130fab6c74af4871d0e6c0c133a7c1

I don't agree with the chnage you've made which modify much more the code, break the signature of popen2 and start using code path that were not used before.
Maybe we could merge my commit first (that works) and improve the code later (I don't really see the improvement btw)

LGTM for the 1st one


Prioritize local over remote leader

Please provide a description of this PR:
Followup to https://github.com/istio/istio/pull/36121#discussion_r756199020

Didn't closely look so will ask instead: do we handle the case where old Istios are used (locally or remote) which don't use > the new key?
And the inverse - do old versions handle the new key?

An old key will look like that of a locally-running istiod, even if it's actually remote, so a new local one won't steal the lock, where it could if the key indicated the old leader was remote.
If we run an old istiod (local or remote), in the prioritized case, and it's the default revision, it could steal the lock from a remote new istiod that is also for the default revision, because the key prefix will make it think the other leader is a different revision.
I think these are reasonable expected behavior and unlikely corner cases anyway.
Otherwise, I think old and new works as before, regardless of the previous leader.

If we run an old istiod (local or remote), in the prioritized case, and
it's the default revision, it could steal the lock from a remote new istiod
that is also for the default revision, because the key prefix will make it
think the other leader is a different revision.

If I understand right, this means 2 instances think they should steal the
lock. This will result in them both constantly stealing the lock from each
other endlessly? If so, that seems not great
On Fri, Apr 1, 2022 at 9:13 AM Frank Budinsky @.***>
wrote:

Didn't closely look so will ask instead: do we handle the case where old
Istios are used (locally or remote) which don't use > the new key?
And the inverse - do old versions handle the new key?
An old key will look like that of a locally-running istiod, even if it's
actually remote, so a new local one won't steal the lock, where it could if
the key indicated the old leader was remote.
If we run an old istiod (local or remote), in the prioritized case, and
it's the default revision, it could steal the lock from a remote new istiod
that is also for the default revision, because the key prefix will make it
think the other leader is a different revision.
I think these are reasonable expected behavior and unlikely corner cases
anyway.
Otherwise, I think old and new works as before, regardless of the previous
leader.
—
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/pull/38219#issuecomment-1086101258, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEYGXKRVDGNJC35D5DCPOTVC4OA7ANCNFSM5SIWFVLA
.
You are receiving this because your review was requested.Message ID:
@.***>

If I understand right, this means 2 instances think they should steal the
lock. This will result in them both constantly stealing the lock from each
other endlessly? If so, that seems not great

No. Once the old one steals the lock, it will look like a locally running istiod for the default revision, so nobody can steal it after that.

@frankbu: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-telemetry-mc_istio
76ba7110c29c19201d3b398344e0a48d81bb0af2
link
true
/test integ-telemetry-mc_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

No matter what, old revisions will steal the leader lock if l.revision != currentLeaderRevision && defaultRevision == l.revision (i.e. the current lock holder has a revision that isn't the default and we have a revision that is), that's a given.

It's also possible that an old revision will steal the lock if the current lock holder has a revision that IS the default. This happens when the current lock holder is a new remote holder with the "^" prefix, so the old code will think l.revision != currentLeaderRevision, even though it is the same revision.

Let's also notice that new revisions will always see old revisions as local since old revisions won't set the special key prefix.

Yes, this and the above are basically saying that old versions look and behave like they are local, regardless of where they are actually located. No thrashing will ever happen, just the old ones running remotely have higher priority than they deserve.

New remote revisions won't steal the lock if the current holder is local, so it never steals the lock except from newer remote revisions (since it sees all older ones as local). So IIUC with this change, even though a new remote instance is the default revision, it won't take the lock from any older revision. This seems wrong?

This is related to why I also set config.KeyComparison even if l.prioritized is false. I added the local/remote prioritization code with the assumption that it is unrelated to the prioritized leader election feature, i.e., it applies all the time. The prioritized feature only applies to the revision prioritization, after the location decision has been made. Bottom line is we always favor a local istiod over a remote one, even if there is a more appropriate revision running remotely.
I did it this way because I think location prioritization should always be enabled, and I wasn't sure when the current prioritized leader election is enabled or not, but I see it is true by default, so I think it would be fine to handle location in the prioritized case only. That actually simplifies the algorithm a bit, leaving only the old code running locally but behaving like a local as the odd behavior, but that will go away in a few months after a couple more Istio releases.
I'll update the code with this changed.

@frankbu: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
cd1ad03070fdaffefc11ae8d48e3ec027b4e3715
link
true
/test lint_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@frankbu: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-ipv6_istio
ec3f5aaca4613679609ba53892e3c2ad4d9c008e
link
true
/test integ-ipv6_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test integ-ipv6_istio


[AppService] Fix az webapp create - use hardcoded runtime stacks

Description
Fix az webapp create to use the updated hardcoded runtimes.
Closes #14281
A while back as part of issue #13261, az webapp list-runtimes was updated to a hardcoded list. az webapp create implementation wasn't updated to use this hardcoded list, so this PR fixes it
Testing Guide
az webapp create -n <webappname> -g <resource_group_name> -l -p <app_service_plan> -r "DOTNETCORE|3.1" should work, since DOTNETCORE|3.1 is a new runtime added in the hardcoded list-runtimes command
az webapp create -n <webappname> -g <resource_group_name> -l -p <app_service_plan> -r "node|6.6" should not work, since node|6.6 is a deprecated runtime

This checklist is used to make sure that common guidelines for a pull request are followed.

[x] The PR title and description has followed the guideline in Submitting Pull Requests.

[x] I adhere to the Command Guidelines.

AppService

@qwordy can we get a PR on this please would like to take it for the current release. Thanks!


Cannot start new project due to Ajv error

Is this a bug report?
Yes

Did you try recovering your dependencies?

No
Which terms did you search for in User Guide?

None
Environment

Environment Info:

  System:
    OS: macOS 10.14.2
    CPU: x64 Intel(R) Core(TM) i5-8259U CPU @ 2.30GHz
  Binaries:
    Node: 10.12.0 - /usr/local/bin/node
    npm: 6.7.0 - /usr/local/bin/npm
  Browsers:
    Chrome: 71.0.3578.98
    Safari: 12.0.2
  npmPackages:
    react: ^16.8.1 => 16.8.1
    react-dom: ^16.8.1 => 16.8.1
    react-scripts: 2.1.3 => 2.1.3
  npmGlobalPackages:
    create-react-app: Not Found

Steps to Reproduce

npx create-react-app my-app --typescript
cd my-app
npm start

Expected Behavior

Starting the development server
Actual Behavior

Build exits with status 1 and the following error appears:
><EMAIL_ADDRESS>start /Users/pawel/Projects/react-tutorial-app
> react-scripts start

/Users/pawel/Projects/react-tutorial-app/node_modules/ajv/lib/keyword.js:65
      throw new Error('custom keyword definition is invalid: '  + this.errorsText(validateDefinition.errors));
      ^

Error: custom keyword definition is invalid: data.errors should be boolean
    at Ajv.addKeyword (/Users/pawel/Projects/react-tutorial-app/node_modules/ajv/lib/keyword.js:65:13)
    at module.exports (/Users/pawel/Projects/react-tutorial-app/node_modules/ajv-errors/index.js:10:7)
    at Object.<anonymous> (/Users/pawel/Projects/react-tutorial-app/node_modules/schema-utils/src/validateOptions.js:22:1)
    at Module._compile (internal/modules/cjs/loader.js:688:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:699:10)
    at Module.load (internal/modules/cjs/loader.js:598:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:537:12)
    at Function.Module._load (internal/modules/cjs/loader.js:529:3)
    at Module.require (internal/modules/cjs/loader.js:636:17)
    at require (internal/modules/cjs/helpers.js:20:18)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>start: `react-scripts start`
npm ERR! Exit status 1

Reproducible Demo

Not available

AJV issue: https://github.com/epoberezkin/ajv/issues/941

placing this comment here as well since i see it referenced. this broke a fresh Nuxt project for me. Doing npm i -d<EMAIL_ADDRESS>resolved it for now.

workaround for yarn users:
add
  "resolutions": {
    "ajv": "6.5.5"
  }

to your package.json and re run yarn install

this issue drove me crazy!
@tetreault not working for me ):

just add
  "resolutions": {
    "ajv": "6.8.1"
  }

to your package.json
run yarn install if you use yarn
rm -rf node_modules
npx npm-force-resolutions
npm install

if you use npm.

@viankakrisna didn't manage to make it work using your fix on npm

Thanks guys!

@viankakrisna adding resolutions worked for me! Thanks

Last fix worked for me, although I would like to see a more general resolution.

As a short term adding "ajv": "6.8.1" to package.json deps should also work.

updated ajv version 6.7.0 -> 6.9.0
downgrade version
yarn add<EMAIL_ADDRESS>or npm install<EMAIL_ADDRESS>

<EMAIL_ADDRESS>is out and should fix this issue. Please let us know if you continue to have issues. Make sure to delete your node_modules and lock files to ensure you grab the latest package.


Emmet for Yandex BEM support in JSX

VSCode Version: 1.14.2
OS Version: 10.12.5

Steps to Reproduce:

typein .b_m1._m2|bem in a React Component render function
press tab
got

expected

Reproduces without extensions: Yes
FYI：Yandex BEM

Hello, @yujiaze,
You use the original Emmet or Emmet with emmet.useNewEmmet: true option?

Looks like the bem filter never worked for in jsx in VS Code.

Bem for jsx never worked before VS Code 1.15
In VS code 1.15, there is a broken experience for bem
Its too late in the game to push a fix for 1.15... We are just about to release 1.15
So I have fixed it for VS Code 1.16 and you should be able to see the fix in 1.16 insiders next week.
If there ever is a recovery build for 1.15, I'll try and get this in for 1.15.1

The fix for this made it to 1.15.1 already


Not all strings need to be translated

...fixes F-Droid build too
/LE: REtag 1.3.3 after merging to allow F-Droid to rebuild

Thanks!


Compilation Time Long when N > 50

Is the compilation time for the Tensor types expected to take order of minutes?
I tested:
 make_sym = (N) -> rand(Tensor{Tuple{@Symmetry{N,N,N}},Float32})
and it took about a minute to compile with N = 100.
@Mat rand(50,50) also took around a minute.
I was interested to benchmark the symmetry specific optimizations, but my use case is at least tensors that are 600x600x600 and the compilation time is making that impossible. Am I using something wrong or is this package only intended for small amounts of data?

Yes, this package is designed for handling only small-sized tensors, similar to SArray in StaticArrays.jl. I think you should take a look at TensorOperatios.jl and Tullio.jl.

Already using TensorOperations was just looking to see if this could be useful. I actually want something that does sparse contractions but I think I'll have to stick with my own code for that.
Package looks great for the smaller stuff though.

Thanks. I'm not familiar with sparse structures, but TensorKit.jl might be useful? Perhaps you've already looked into it, though.


Principle of least privilege for credential calling 'New-ADServiceAccount' and 'Add-ADComputerServiceAccount'

We wish to automate the deployment of SQL Services without exposing unnecessary permissions to the calling process, what are the least permissions required to enable the creation of a MSA object.

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

ID: b34e4807-4310-c1cd-5ae5-a4bba32cb532
Version Independent ID: a2739dc4-3ddd-34eb-1619-e2bffc6619c7
Content: What's New for Managed Service Accounts
Content Source: WindowsServerDocs/security/group-managed-service-accounts/what-s-new-for-managed-service-accounts.md
Product: windows-server-threshold
GitHub Login: @coreyp-at-msft
Microsoft Alias: coreyp

@SQLHorizons This topic says you need Create/Delete msDS-ManagedServiceAccount
https://docs.microsoft.com/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/dd548356(v=ws.10)
We will look at migrating that topic to the current library.

@Justinha  Thank you.
But to be complete we need Create/Delete on both msDS-ManagedServiceAccount and msDS-GroupManagedServiceAccount for this to work. (based on the test I've just completed on Windows 2016).  In addition you'll need Read\Write msDS-HostServiceAccount on dependent computer objects within the OU of the computer objects where you wish to assign the MSA.


Revert "use cli xml instead of xml tags"

Reverts fooelisa/pyiosxr#41 -- @thorko: you claimed that you are using this code. It cannot work properly, as it's syntax error.

@thorko I am reverting your changes, please push the requested changes in your branch, test on a real device and resubmit the pull request.

Coverage remained the same at 87.719% when pulling b8f277a52abee1ce68976f1d67a321b3b7631b87 on revert-41-master into b655292a2d17bb4eead85e6e629aee4a5f9806d4 on master.


[discussion] Consider adopting _macro naming convention for crates

          should we do this consistently across codebase? I thought the practice was to name proc-macro crates `derive`. Whether or not they had `derive` macros, `attribute` macros or `function-like` macros

Originally posted by @mversic in https://github.com/hyperledger/iroha/pull/4139#discussion_r1427552415

In my experience, _derive seems to be the more popular scheme


gomobile bind -target=ios : "could not import fmt"

What version of Go are you using (go version)?

$ go version
go version go1.12.5 darwin/amd64

gomobile version +32b2708 Thu May 9 16:48:39 2019

Does this issue reproduce with the latest release?
yes
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GOHOSTARCH="amd64"
GOHOSTOS="darwin"

What did you do?
gomobile bind -target=ios -tags="ios" -v mygoapp

What did you expect to see?
success
What did you see instead?

type-checking package "gomobileios" failed (/mygo/src/gomobileios/gomobileios.go:3:8:
could not import fmt (type-checking package "fmt" failed (/usr/local/go/src/fmt/print.go:9:2:
could not import internal/fmtsort (type-checking package "internal/fmtsort" failed (/usr/local/go/src/internal/fmtsort/sort.go:12:2:
could not import reflect (type-checking package "reflect" failed (/usr/local/go/src/reflect/type.go:19:2: could not import runtime (type-checking package "runtime" failed (/usr/local/go/src/runtime/mem_bsd.go:16:6: sysAlloc redeclared in this block)))))))))

gomobile:/mygo/bin/gobind -lang=go,objc -outdir=/tmp/gomobile-work-268473047 -tags=ios,ios gomobileios failed: exit status 1

The old gomobile didn't work. Updating it didn't work.
What worked was deleting it and installing again with:
go install golang.org/x/mobile/cmd/gomobile

Noe let see if my go code would be compiled with bitcode.


How to build and install locally

Hi,
great extension, thank you for your work.
I'd like to install it in a secure environment.
Would you generously add a brief section on local building/installing?
Coffee will be indeed bought as you suggest ☕☕
Cheers - V

Hello!
Added this section to the documentation explaining the manual installation. This is for Google Chrome, for other browsers different process might be required (or it might not be possible).
Let me know if you have any further questions regarding this.
Have a nice day!


Seems that the app is not working for Windows 11.

App won't open on my computer with Windows 11, but it works just fine on a different one with Windows 10.

#117
Last year's version won't work on windows 11. You need the 2023 beta. Closing as a duplicate. Feel free to re-open if its a problem with the beta.


NullPointerException in handshake

This is a report from end users, via Crashlytics. We do not have repro steps.
A few users complain that our app repeatedly crashes. From what I can tell, all affected users so far are using the same device (Meizu M5). From what I can tell, it happens every time our app attempts a network request.
OS version: 6.0
OkHttp version: 3.9.0
Device: Meizu M5
Is this a platform bug, or is there anything OkHttp (or we app authors!) can do to work around it?
Fatal Exception: java.lang.NullPointerException: ssl_session == null
       at com.android.org.conscrypt.NativeCrypto.SSL_SESSION_cipher(NativeCrypto.java)
       at com.android.org.conscrypt.OpenSSLSessionImpl.getCipherSuite(OpenSSLSessionImpl.java:320)
       at io.intercom.okhttp3.Handshake.get(Handshake.java:49)
       at io.intercom.okhttp3.internal.connection.RealConnection.connectTls(RealConnection.java:268)
       at io.intercom.okhttp3.internal.connection.RealConnection.establishProtocol(RealConnection.java:237)
       at io.intercom.okhttp3.internal.connection.RealConnection.connect(RealConnection.java:148)
       at io.intercom.okhttp3.internal.connection.StreamAllocation.findConnection(StreamAllocation.java:186)
       at io.intercom.okhttp3.internal.connection.StreamAllocation.findHealthyConnection(StreamAllocation.java:121)
       at io.intercom.okhttp3.internal.connection.StreamAllocation.newStream(StreamAllocation.java:100)
       at io.intercom.okhttp3.internal.connection.ConnectInterceptor.intercept(ConnectInterceptor.java:42)
       at io.intercom.okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:92)
       at io.intercom.okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:67)
       at io.intercom.okhttp3.internal.cache.CacheInterceptor.intercept(CacheInterceptor.java:93)
       at io.intercom.okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:92)
       at io.intercom.okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:67)
       at io.intercom.okhttp3.internal.http.BridgeInterceptor.intercept(BridgeInterceptor.java:93)
       at io.intercom.okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:92)
       at io.intercom.okhttp3.internal.http.RetryAndFollowUpInterceptor.intercept(RetryAndFollowUpInterceptor.java:120)
       at io.intercom.okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:92)
       at io.intercom.okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:67)
       at io.intercom.okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.java:179)
       at io.intercom.okhttp3.RealCall$AsyncCall.execute(RealCall.java:129)
       at io.intercom.okhttp3.internal.NamedRunnable.run(NamedRunnable.java:32)
       at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1113)
       at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:588)
       at java.lang.Thread.run(Thread.java:818)

Sounds like a device bug. Could you report it to the manufacturer?
I’m not sure what our workaround would look like; seems like this device isn't able to do SSL with whichever URL you're requesting.

Lets track this here:
https://github.com/square/okhttp/issues/3301


Annotations are not available in the exported SVG

 Issue by dilinisg
Thursday Aug 03, 2017 at 10:39 GMT
Originally opened as https://github.com/ballerina-lang/composer/issues/2660

Release 0.91
Following is the actual diagram (in left) and downloaded diagram as a SVG.

Issues

Annotations are not shown.
Alignment issues in the parameters of the function

 Comment by NipunaMarcus
Friday Aug 11, 2017 at 05:20 GMT

Diagram export is only considering the SVG element when exporting diagram as png and svg. Annotation details are drawn using HTML which will be excluded in this method as it is not SVG. To include annotations when exporting diagram either we have to implement them using SVG or convert them to SVG during exporting diagram.   This will be discuss further and try to find a solution.

 Comment by dilinisg
Saturday Nov 04, 2017 at 16:28 GMT

Can still observe in 0.95 release

Implementation has differed


Context detection module

Created context detection module and moved ambulation detection to it.

Can you update the rmd files in docs/ref? ie there is still an ambulation.rmd, and references to that probably need to be changed as well

yep, take a look now, all should be good.


Checkbox to exclude row on import

I am just wondering how hard it would be to add a checkbox on the import preview page to enable the user to select records to exclude from the import.
This would be useful where there is more than one record matching the import_id_fields as would allow user to select which record they want to include.
I am very new to python/django so a little beyond me, although I have just worked out how to override the "skip_row" function which I imagine is where we would test if recorded has been marked to exclude. I suppose the form and template would need to be updated and somehow passed to "skip_row" where decision on included/excluding would be made.

In #237 we allowed **kwargs to be passed to import_data so presumably we could add the checkbox to the form and use it to build an array of rows that should be skipped, and then check for them in skip_row.
I'm not sure that such an extension belongs in the core though. It would be difficult to know how to pass the array to skip rows:

if the PK is a single field and is in the import file, then it works great, but that situation won't be common
if the import_id_fields are in the row then we could build a tuple of them, but that doesn't help when there are multiple rows with identical import_id_fields but different other fields (the use case @alaw005   describes)
we could build a tuple of all fields, but that seems a bit of a hack
we could use the row_id, but that might not work if the user is doing any dataset manipulation in  before_import - I often need to un-crosstab data, or delete extra rows before the main header, etc. In theory, the datasets should be the same, but you could have problems if any of the dataset manipulation depends on the value of dry_run.

I had idea to move handling of uploaded data to some form  to make handling confirming and importing data pluggable with ConfirmImportForm (https://github.com/django-import-export/django-import-export/pull/133#issuecomment-69537699). I am not sure if this would work and there is already PR https://github.com/django-import-export/django-import-export/pull/264 that solves original problem of horizontal scaling.
On the other side I am not sure if this should go in core as overriding import_action should not be problem, there are less than 50 lines of code there:
https://github.com/django-import-export/django-import-export/blob/master/import_export/admin.py#L171-L229

I agree about it not going in core.
I think we should add extension points to enable these sorts of
customizations as we find them. The pluggable temporary storage is a good
example.
For example, we could:

change the call to input_format.create_dataset to go via a new
self.create_dataset which would allow people to customize the dataset
creation on a per admin basis.
separate the the import_template_name into confirm_import_tempate_name
and process_import_template_name so that people can customize the
confirm page separately if they want

On Thu, May 21, 2015 at 12:50 AM, Bojan Mihelac<EMAIL_ADDRESS>wrote:

I had idea to move handling of uploaded data to some form to make handling
confirming and importing data pluggable with ConfirmImportForm (#133
(comment)
https://github.com/django-import-export/django-import-export/pull/133#issuecomment-69537699).
I am not sure if this would work and there is already PR #264
https://github.com/django-import-export/django-import-export/pull/264
that solves original problem of horizontal scaling.
On the other side I am not sure if this should go in core as overriding
import_action should not be problem, there are less than 50 lines of code
there:
https://github.com/django-import-export/django-import-export/blob/master/import_export/admin.py#L171-L229
—
Reply to this email directly or view it on GitHub
https://github.com/django-import-export/django-import-export/issues/258#issuecomment-103992635
.

agree,. good points


Use Operations implementations for Expr

Pushed temporarily commits 394b1342796f8e9b1bdab275c8ac41779aa44630 and 052aa572de0f8a8c921112b64eb004351af51e88 to debug the failing CI.

Thanks @mrmr1993. I'm surprise that I couldn't reproduce locally it with the seed


Example serverclient.py fails with No module named platform on MacOS with Python 2.7.15

+python serverclient.py

Traceback (most recent call last):
  File "src/gevent/greenlet.py", line 718, in gevent._greenlet.Greenlet.run
  File "src/gevent/greenlet.py", line 700, in gevent._greenlet.Greenlet._report_error
  File "/usr/local/lib/python2.7/site-packages/gevent/_tblib.py", line 371, in g
  File "/usr/local/lib/python2.7/site-packages/gevent/_tblib.py", line 425, in dump_traceback
  File "/usr/local/lib/python2.7/site-packages/gevent/_tblib.py", line 402, in _init
ImportError: No module named platform
2018-09-29T12:37:06Z <callback at 0x10b708320 stopped> failed with ImportError

This happened with system Python on macOS. I have not seen that when building CPython (via pyenv).

Do we want to support system Python on macOS? First step: build a CI check dedicated to that. Could even be that this passes now with the recent workarounds for macOS.

We're testing with system Python now on Mac OS: https://github.com/jgehrcke/gipc/blob/c9fa60d234dc04a92f136274eb59539a33ec291b/.travis.yml#L112
It works. Closing.


[WIP] Support for CentOS8

This adds support for CentOS8 packaging. The first would be to support CentOS8 as KVM host, and then as mgmt+usage server host.
Tasks:

[ ] Create BO/docker container for packaging
[ ] Test/support packaging for management and usage server, on CentOS8 host
[ ] Test/support packaging for KVM agent, on CentOS8 KVM host
[x] Depends on #3601 (jdk changes, mysql dependency support/version)

Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[x] New feature (non-breaking change which adds functionality)
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] Enhancement (improves an existing feature and functionality)
[ ] Cleanup (Code refactoring and cleanup, that may add test cases)

@andrijapanicsb cc @DaanHoogland @PaulAngus @borisstoyanov - we won't have time, moved to the next 4.15 milestone.

It would be interesting to see how this goes as CentOS8 (like Ubuntu 20.04) has switched from iptables to nftables, though the command "iptables" is still present, it's just using nftables underneath. This might impact security group functionality.
If this is the case, it might be a good occasion to check whether SG functionality can be moved entirely into libvirt which supports (I think).
https://libvirt.org/firewall.html

Closed in favour of the new PR.


upgrade markdown-it dependency to 10.0.0 to remediate Regular Express…

…ion Denial of Service (ReDoS) attack vulnerability

A Regular Expression Denial of Service (ReDoS) attack vulnerability was identified in markdown-it for versions below 10.0.0. This PR updates the markdown-it dependency to ^10.0.0 in order to remediate the vulnerability.


Deletion of element in BST C_Cpp

Description 📜
I have added the documentation for deleting an element in Binary Search Tree along with its code in C.
Fixes #2474

Type of change 📝

[ ] Au#dio (Should be in mp3 format Includes speech clarity, Concise ,Low distortion)
[ ] Vi#deo (Animations, screen-recordings, presentations and regular explanatory films are all possibilties etc)
[x] Documentation (Content Creation in the form of codes or tutorials)
[ ] Other (If you choose other, Please mention changes below)

Domain of Contribution 📊

[ ] Android Dev #(Flutter)
[ ] Android Dev #(Java)
[ ] Android Dev #(Kotlin)
[ ] Backend Dev #(Java)
[ ] Backend Dev #(.NET)
[ ] Backend Dev #(PHP)
[ ] Backend Dev #(Python)
[x] C/CPP
[ ] Competitive #Programming
[ ] Cyber #Security
[ ] DS#A
[ ] Data#base
[ ] Datascience with #Python
[ ] Datascience with #R
[ ] Frontend Dev #HTML/CSS/JS
[ ] Frontend Dev #React/Angular/Vue
[ ] Go#lang
[ ] Interview #Prep
[ ] Java_#Domain
[ ] Java#Script
[ ] ME#RN
[ ] Machine #Learning
[ ] Open #Source
[ ] Python_#Domain
[ ] Ru#st
[ ] Statis#tics
[ ] UI/#UX

Checklist ✅

[x] I follow Contributing Guidelines & Code of conduct of this project.
[x] I have performed a self-review of my own code or work.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I'm GWOC'21 contributor

Screenshots / Gif (Optional) 📸

@Suvraneel Could you check this commit I have fixed the file path according the directory structure you fixed yesterday


Fix macOS install script: follow HTTP redirect when fetching binary

I noticed the macOS install script fails because the grep doesn't find a match anymore. My change fixes this by using the curl --location option, which I think is the recommended way to follow a HTTP redirect.

Great!


Mention CLI_TEST_MASTER_PROXY=1 in the README

When running integration tests from a machine which cannot reach all
nodes through the network, one would get this failure :
tests/integrations/test_node.py:257: AssertionError
------------------------------ Captured stdout call
-------------------------------
SSH COMMAND: ssh-agent /bin/bash -c "ssh-add
/home/bamarni/.ssh/mesosphere_shared 2> /dev/null && dcos node ssh
--option StrictHostKeyChecking=no --leader"
SSH STDOUT:
SSH STDERR: Running `ssh -t -o StrictHostKeyChecking=no<EMAIL_ADDRESS>
If you are running this command from a separate network than DC/OS,
consider using `--master-proxy` or `--proxy-ip`
ssh: connect to host <IP_ADDRESS> port 22: Network is unreachable

This is for example the case when running integration tests locally with
the default cloudformation template.
https://jira.mesosphere.com/browse/DCOS_OSS-1624

This was addressed during #1056


Issue with volume on postgres image.

When I am running docker-compose I get an Error: Encounter errors while bringing up the project. It is related to the postgres container. If the local path is not specifiend in docker-compose.yaml for novyl/jtl-reporter-db image everything works. I think there is a problem with the folder permissions or something simillar.

Hi @ipacbalaj , was this happening when you started the project for the first time or during upgrade?

Hi, it happend on first start.
On Wed, 10 Feb 2021 at 19:22, Ludek<EMAIL_ADDRESS>wrote:

Hi @ipacbalaj https://github.com/ipacbalaj , was this happening when
you started the project for the first time or during upgrade?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ludeknovy/jtl-reporter/issues/16#issuecomment-776876855,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACBM5AJQMRNJV5SVNVVM4V3S6K6G5ANCNFSM4XNDX7ZQ
.

Worth mentioning, I am running on a Windows machine
On Wed, 10 Feb 2021 at 20:41, Ionut Pac-Balaj<EMAIL_ADDRESS>wrote:

Hi, it happend on first start.
On Wed, 10 Feb 2021 at 19:22, Ludek<EMAIL_ADDRESS>wrote:

Hi @ipacbalaj https://github.com/ipacbalaj , was this happening when
you started the project for the first time or during upgrade?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ludeknovy/jtl-reporter/issues/16#issuecomment-776876855,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACBM5AJQMRNJV5SVNVVM4V3S6K6G5ANCNFSM4XNDX7ZQ
.

The only thing I can do is to create a droplet in Digital Ocean and try to run it. But they only offer unix based systems. And unfortunately I dont have Windows machine at my disposal, but when I used it in a past I had constantly issues with docker. Did you try Windows Subsystem for Linux ?

@ipacbalaj I tested it on fresh linux instance and it worked. That issue you reported must be  windows docker specific problem?

Yes it is windows docker specific. I tested on macos and it works there
On Wed, 10 Feb 2021 at 23:18, Ludek<EMAIL_ADDRESS>wrote:

@ipacbalaj https://github.com/ipacbalaj I tested it on fresh linux
instance and it worked. That issue you reported must be windows docker
specific problem?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ludeknovy/jtl-reporter/issues/16#issuecomment-777042305,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACBM5AKEC55QSDHB2KWJPZ3S6LZYXANCNFSM4XNDX7ZQ
.

@ipacbalaj I am afraid I wont be able to help with this one unfortunately.


REST client ignores order_side BUY/SELL filter

This line of code is returning BUY and SELL orders. Is there a reason or could this be a bug?
print(client.list_orders(order_status=["OPEN"], order_side="SELL"))

@LiteTite thanks for flagging this! We have identified the issue and will have a fix out in the next few days.